diff options
| author | Guy Harris <guy@alum.mit.edu> | 2005-09-29 02:20:29 +0000 |
|---|---|---|
| committer | Guy Harris <guy@alum.mit.edu> | 2005-09-29 02:20:29 +0000 |
| commit | a275cd2495144bf5bf00d26c3cf5d26c5f69fbd8 (patch) | |
| tree | 0072cf00502222c5aa6fe2b0fc7debb4326c71b2 /diameter/mobileipv4.xml | |
| parent | 7aa4b4ffe1f575bbb50f03e012b6f77dd5ab02f0 (diff) | |
| download | wireshark-a275cd2495144bf5bf00d26c3cf5d26c5f69fbd8.tar.gz | |
Move the Diameter dictionary files to a "diameter" subdirectory, along
the lines of what's done for RADIUS. That keeps them together (and
separate from other files), and makes the layout of the top-level source
directory closer to the layout of the installation directory, so that if
you run Ethereal or Tethereal from the top-level directory on Windows
it'll pick up the Diameter dictionary files (if it supports loading
them), and can do so on UN*X if we support a mechanism to let it find
its control files in the directory in which the binary resides.
Use the diameter_DATA, dtds_DATA, and radius_DATA macros in the
EXTRA_DIST macro, so you only have to change the lists of Diameter, DTD,
and RADIUS files in one place if you add or remove a file.
svn path=/trunk/; revision=16050
Diffstat (limited to 'diameter/mobileipv4.xml')
| -rw-r--r-- | diameter/mobileipv4.xml | 62 |
1 files changed, 62 insertions, 0 deletions
diff --git a/diameter/mobileipv4.xml b/diameter/mobileipv4.xml new file mode 100644 index 0000000000..37566a8c57 --- /dev/null +++ b/diameter/mobileipv4.xml @@ -0,0 +1,62 @@ +<?xml version="1.0" encoding="UTF-8"?> + + <application id="4" name="Mobile IPv4 Application" uri="ftp://ftp.ietf.org/internet-drafts/draft-ietf-aaa-diameter-mobileip-07.txt"> + + <!-- Mobile-IPv4 Application --> + <command name="AA-Mobile-Node" code="260" vendor-id="None"/> + <command name="Home-Agent-MIP" code="262" vendor-id="None"/> + + <!-- ************************** Mobile-IPv4 AVPS ********************* --> + <avp name="MIP-Filter-Rule" code="347" mandatory="must" vendor-bit="mustnot" may-encrypt="yes"> + <type type-name="IPFilterRule"/> + </avp> + <avp name="MIP-Auth-Input-Data-Length" code="338" mandatory="must" vendor-bit="mustnot" may-encrypt="yes"> + <type type-name="Unsigned32"/> + </avp> + <avp name="MIP-Authenticator-Length" code="339" mandatory="must" vendor-bit="mustnot" may-encrypt="yes"> + <type type-name="Unsigned32"/> + </avp> + <avp name="MIP-Authenticator-Offset" code="340" mandatory="must" vendor-bit="mustnot" may-encrypt="yes"> + <type type-name="Unsigned32"/> + </avp> + <avp name="MIP-FA-Challenge" code="344" mandatory="must" vendor-bit="mustnot" may-encrypt="yes"> + <type type-name="OctetString"/> + </avp> + <avp name="MIP-Feature-Vector" code="337" mandatory="must" vendor-bit="mustnot" may-encrypt="yes"> + <type type-name="Unsigned32"/> + </avp> + <avp name="MIP-Foreign-Agent-Host" code="330" mandatory="must" vendor-bit="mustnot" may-encrypt="yes"> + <type type-name="DiameterIdentity"/> + </avp> + <avp name="MIP-Home-Agent-Address" code="334" mandatory="must" vendor-bit="mustnot" may-encrypt="yes"> + <type type-name="IPAddress"/> + </avp> + <avp name="MIP-MN-AAA-Auth" code="322" mandatory="must" vendor-bit="mustnot" may-encrypt="yes"> + <grouped> + <gavp name="MIP-MN-AAA-SPI"/> + <gavp name="MIP-Auth-Input-Data-Length"/> + <gavp name="MIP-Authenticator-Length"/> + <gavp name="MIP-Authenticator-Offset"/> + </grouped> + </avp> + <avp name="MIP-MN-AAA-SPI" code="341" mandatory="must" vendor-bit="mustnot" may-encrypt="yes"> + <type type-name="Unsigned32"/> + </avp> + <avp name="MIP-Mobile-Node-Address" code="333" mandatory="must" vendor-bit="mustnot" may-encrypt="yes"> + <type type-name="IPAddress"/> + </avp> + <avp name="MIP-Previous-FA-Addr" code="336" mandatory="must" vendor-bit="mustnot" may-encrypt="yes"> + <type type-name="IPAddress"/> + </avp> + <avp name="MIP-Previous-FA-Host" code="335" mandatory="must" vendor-bit="mustnot" may-encrypt="yes"> + <type type-name="DiameterIdentity"/> + </avp> + <avp name="MIP-Reg-Request" code="320" mandatory="must" vendor-bit="mustnot" may-encrypt="yes"> + <type type-name="MIPRegistrationRequest"/> + </avp> + <avp name="MIP-Reg-Reply" code="321" mandatory="must" vendor-bit="mustnot" may-encrypt="yes"> + <type type-name="OctetString"/> + </avp> + <!-- ************************ END Mobile-IPv4 AVPS ******************* --> + + </application> |