1 <?xml version="1.0" encoding="UTF-8"?>
2 <!DOCTYPE dictionary SYSTEM "dictionary.dtd" [
3 <!ENTITY nasreq SYSTEM "nasreq.xml">
4 <!ENTITY mobileipv4 SYSTEM "mobileipv4.xml">
5 <!ENTITY sunping SYSTEM "sunping.xml">
8 <base uri="ftp://ftp.ietf.org/internet-drafts/draft-ietf-aaa-diameter-07.txt">
10 $Log: dictionary.xml,v $
11 Revision 1.1 2001/11/01 21:52:44 guy
12 From David Frascone: duUpdate to Diameter dissector to load the
13 dictionary as an XML file rather than building it in, and various
16 Revision 1.7 2001/08/24 18:03:24 chaos
19 Revision 1.6 2001/07/31 19:13:55 chaos
20 Missed a couple of MIP AVPs
22 Revision 1.5 2001/07/31 19:09:22 chaos
23 Added Mobile-Ip and Sun Ping Extension
25 Revision 1.4 2001/07/31 17:43:25 chaos
26 Oops, forgot to turn on validity checking. Fixed some errors found with validity checking turned on
28 Revision 1.3 2001/07/31 16:56:31 chaos
29 Added commands, and validated with xmllint
31 Revision 1.2 2001/07/31 16:29:34 chaos
32 Checking in some changes to verify log and ident strings
35 <!-- *********************** Commands ***************************** -->
36 <!-- Diameter Base Protocol Command Codes -->
37 <command name="Abort-Session" code="274" vendor-id="None">
38 <!-- Maybe some avp stuff here one day -->
40 <command name="Accounting" code="271" vendor-id="None"/>
41 <command name="Capabilities-Exchange" code="257" vendor-id="None"/>
42 <command name="Device-Watchdog" code="280" vendor-id="None"/>
43 <command name="Disconnect-Peer" code="282" vendor-id="None"/>
44 <command name="Re-Auth" code="258" vendor-id="None"/>
45 <command name="Session-Termination" code="275" vendor-id="None"/>
46 <!-- ********************** End Commands ************************** -->
48 <!-- ************************* Vendors **************************** -->
49 <vendor vendor-id="None" code="0" name="None"/>
50 <vendor vendor-id="Merit" code="61" name="Merit Networks"/>
51 <vendor vendor-id="Sun" code="42" name="Sun Microsystems, Inc."/>
52 <vendor vendor-id="USR" code="429" name="US Robotics Corp."/>
53 <!-- *********************** End Vendors ************************** -->
55 <!-- ************************ typedefn's ************************** -->
56 <typedefn type-name="OctetString"/>
58 The data contains arbitrary data of variable length. Unless
59 otherwise noted, the AVP Length field MUST be set to at least 9
60 (13 if the 'V' bit is enabled). Data used to transmit (human
61 readable) character string data uses the UTF-8 [24] character
62 set and is NOT NULL-terminated. The minimum Length field MUST
63 be 9, but can be set to any value up to 65504 bytes. AVP Values
64 of this type that do not align on a 32-bit boundary MUST have
65 the necessary padding.
67 <typedefn type-name="UTF8String" type-parent="OctetString"/>
69 The UTF8String format is derived from the OctetString AVP Base
70 Format. This is a human readable string represented using the
71 ISO/IEC IS 10646-1 character set, encoded as an OctetString
72 using the UTF-8 [29] transformation format described in RFC
75 Since additional code points are added by amendments to the
76 10646 standard from time to time, implementations MUST be
77 prepared to encounter any code point from 0x00000001 to
78 0x7fffffff. Byte sequences that do not correspond to the valid
79 UTF-8 encoding of a code point or are outside this range are
80 prohibited. Note that since a code point of 0x00000000 is
81 prohibited, no octet will contain a value of 0x00.
83 The use of control codes SHOULD be avoided. When it is
84 necessary to represent a newline, the control code sequence CR
87 The use of leading or trailing white space SHOULD be avoided.
89 For code points not directly supported by user interface
90 hardware or software, an alternative means of entry and
91 display, such as hexadecimal, MAY be provided.
93 For information encoded in 7-bit US-ASCII, the UTF-8 encoding
94 is identical to the US-ASCII encoding.
96 UTF-8 may require multiple bytes to represent a single
97 character / code point; thus the length of a UTF8String in
98 octets may be different from the number of characters encoded.
100 Note that the size of an UTF8String is measured in octets, not
103 The UTF8String MUST not contain any octets with a value of
106 <typedefn type-name="IPAddress" type-parent="OctetString"/>
108 The IPAddress format is derived from the OctetString AVP Base
109 Format. It represents 32 bit (IPv4) [17] or 128 bit (IPv6) [16]
110 address, most significant octet first. The format of the
111 address (IPv4 or IPv6) is determined by the length. If the
112 attribute value is an IPv4 address, the AVP Length field MUST
113 be 12 (16 if 'V' bit is enabled), otherwise the AVP Length
114 field MUST be set to 24 (28 if the 'V' bit is enabled) for IPv6
117 <typedefn type-name="DiameterIdentity" type-parent="OctetString"/>
119 The DiameterIdentity format is derived from the OctetString AVP
120 Base Format. It uses the UTF-8 encoding and has the same
121 requirements as the UTF8String. In addition, it must follow
122 the Uniform Resource Identifiers (URI) syntax [29] rules
125 Diameter-Identity = fqdn [ port ] [ transport ]
128 aaa-protocol = ( "diameter" | "radius" | "tacacs+" )
130 protocol = ";protocol=" aaa-protocol
131 ; If absent, the default AAA protocol
134 fqdn = Fully Qualified Host Name
137 ; One of the ports used to listen for
138 ; incoming connections. ; If absent,
139 ; the default Diameter port (TBD) is
142 transport-protocol = ( "tcp" | "sctp" | "udp" )
144 transport = ";transport=" transport-protocol
146 ; One of the transports used to listen
147 ; for incoming connections. If absent,
148 ; the default SCTP [26] protocol is
149 ; assumed. UDP MUST NOT be used when
150 ; the aaa-protocol field is set to
153 The following are examples of valid Diameter host
156 host.abc.com;transport=tcp
157 host.abc.com:6666;transport=tcp
158 aaa://host.abc.com;protocol=diameter
159 aaa://host.abc.com:6666;protocol=diameter
160 aaa://host.abc.com:6666;transport=tcp;protocol=diameter
161 aaa://host.abc.com:1813;transport=udp;protocol=radius
163 Since multiple Diameter processes on a single host cannot
164 listen for incoming connections on the same port on a given
165 protocol, the DiameterIdentity is guaranteed to be unique per
168 A Diameter node MAY advertise different identities on each
169 connection, via the CER and CEA's Origin-Host AVP, but the same
170 identity MUST be used throughout the duration of a connection.
172 When comparing AVPs of this format, it is necessary to add any
173 absent fields with the default values prior to the comparison.
174 For example, diameter-host.abc.com would be expanded to
175 aaa://diameter/diameter-host.abc.com:TBD;protocol=sctp.
177 <typedefn type-name="IPFilterRule" type-parent="OctetString"/>
179 The IPFilterRule format is derived from the OctetString AVP
180 Base Format. It uses the UTF-8 encoding and has the same
181 requirements as the UTF8String. Packets may be filtered based
182 on the following information that is associated with it:
184 Direction (in or out)
185 Source and destination IP address (possibly masked)
187 Source and destination port (lists or ranges)
193 Rules for the appropriate direction are evaluated in order,
194 with the first matched rule terminating the evaluation. Each
195 packet is evaluated once. If no rule matches, the packet is
196 dropped if the last rule evaluated was a permit, and passed if
197 the last rule was a deny.
199 IPFilterRule filters MUST follow the format:
201 action dir proto from src to dst [options]
203 action permit - Allow packets that match the rule.
204 deny - Drop packets that match the rule.
206 dir "in" is from the terminal, "out" is to the
209 proto An IP protocol specified by number. The "ip"
210 keyword means any protocol will match.
212 src and dst <address/mask> [ports]
214 The <address/mask> may be specified as:
215 ipno An IPv4 or IPv6 number in dotted-
216 quad or canonical IPv6 form. Only
217 this exact IP number will match the
219 ipno/bits An IP number as above with a mask
220 width of the form 1.2.3.4/24. In
221 this case all IP numbers from
222 1.2.3.0 to 1.2.3.255 will match.
223 The bit width MUST be valid for the
224 IP version and the IP number MUST
225 NOT have bits set beyond the mask.
227 The sense of the match can be inverted by
228 preceding an address with the not modifier,
229 causing all other addresses to be matched
230 instead. This does not affect the selection of
233 The keyword "any" is 0.0.0.0/0 or the IPv6
234 equivalent. The keyword "assigned" is the
235 address or set of addresses assigned to the
236 terminal. The first rule SHOULD be "deny in
239 With the TCP, UDP and SCTP protocols, optional
240 ports may be specified as:
242 {port|port-port}[,port[,...]]
244 The `-' notation specifies a range of ports
245 (including boundaries).
247 Fragmented packets which have a non-zero offset
248 (i.e. not the first fragment) will never match
249 a rule which has one or more port
250 specifications. See the frag option for
251 details on matching fragmented packets.
254 frag Match if the packet is a fragment and this is not
255 the first fragment of the datagram. frag may not
256 be used in conjunction with either tcpflags or
257 TCP/UDP port specifications.
260 Match if the IP header contains the comma
261 separated list of options specified in spec. The
262 supported IP options are:
264 ssrr (strict source route), lsrr (loose source
265 route), rr (record packet route) and ts
266 (timestamp). The absence of a particular option
267 may be denoted with a `!'.
270 Match if the TCP header contains the comma
271 separated list of options specified in spec. The
272 supported TCP options are:
274 mss (maximum segment size), window (tcp window
275 advertisement), sack (selective ack), ts (rfc1323
276 timestamp) and cc (rfc1644 t/tcp connection
277 count). The absence of a particular option may
278 be denoted with a `!'.
281 TCP packets only. Match packets that have the RST
284 setup TCP packets only. Match packets that have the SYN
285 bit set but no ACK bit.
288 TCP packets only. Match if the TCP header
289 contains the comma separated list of flags
290 specified in spec. The supported TCP flags are:
292 fin, syn, rst, psh, ack and urg. The absence of a
293 particular flag may be denoted with a `!'. A rule
294 which contains a tcpflags specification can never
295 match a fragmented packet which has a non-zero
296 offset. See the frag option for details on
297 matching fragmented packets.
300 ICMP packets only. Match if the ICMP type is in
301 the list types. The list may be specified as any
302 combination of ranges or individual types
303 separated by commas. The supported ICMP types
306 echo reply (0), destination unreachable (3),
307 source quench (4), redirect (5), echo request
308 (8), router advertisement (9), router
309 solicitation (10), time-to-live exceeded (11), IP
310 header bad (12), timestamp request (13),
311 timestamp reply (14), information request (15),
312 information reply (16), address mask request (17)
313 and address mask reply (18).
315 There is one kind of packet that the access device MUST always
316 discard, that is an IP fragment with a fragment offset of one.
317 This is a valid packet, but it only has one use, to try to
318 circumvent firewalls.
320 An access device that is unable to interpret or apply a deny
321 rule MUST terminate the session. An access device that is
322 unable to interpret or apply a permit rule MAY apply a more
323 restrictive rule. An access device MAY apply deny rules of
324 its own before the supplied rules, for example to protect
325 the access device owner's infrastructure.
327 The rule syntax is a modified subset of ipfw(8) from FreeBSD,
328 and the ipfw.c code may provide a useful base for
331 <typedefn type-name="QOSFilterRule" type-parent="OctetString"/>
333 The QosFilterRule format is derived from the OctetString AVP
334 Base Format. It uses the UTF-8 encoding and has the same
335 requirements as the UTF8String. Packets may be marked or
336 metered based on the following information that is associated
339 Direction (in or out)
340 Source and destination IP address (possibly masked)
342 Source and destination port (lists or ranges)
343 DSCP values (no mask or range)
345 Rules for the appropriate direction are evaluated in order,
346 with the first matched rule terminating the evaluation. Each
347 packet is evaluated once. If no rule matches, the packet is
348 treated as best effort.
350 QoSFilterRule filters MUST follow the format:
352 action dir proto from src to dst [options]
354 tag - Mark packet with a specific DSCP [49].
355 The DSCP option MUST be included.
357 meter - Meter traffic. The metering options
360 dir "in" is from the terminal, "out" is to the
363 proto An IP protocol specified by number. The "ip"
364 keyword means any protocol will match.
366 src and dst <address/mask> [ports]
368 The <address/mask> may be specified as:
369 ipno An IPv4 or IPv6 number in dotted-
370 quad or canonical IPv6 form. Only
371 this exact IP number will match the
373 ipno/bits An IP number as above with a mask
374 width of the form 1.2.3.4/24. In
375 this case all IP numbers from
376 1.2.3.0 to 1.2.3.255 will match.
377 The bit width MUST be valid for the
378 IP version and the IP number MUST
379 NOT have bits set beyond the mask.
381 The sense of the match can be inverted by
382 preceding an address with the not modifier,
383 causing all other addresses to be matched
384 instead. This does not affect the selection of
387 The keyword "any" is 0.0.0.0/0 or the IPv6
388 equivalent. The keyword "assigned" is the
389 address or set of addresses assigned to the
390 terminal. The first rule SHOULD be "deny in
393 With the TCP, UDP and SCTP protocols, optional
394 ports may be specified as:
396 {port|port-port}[,port[,...]]
398 The `-' notation specifies a range of ports
399 (including boundaries).
404 color values as defined in [49]. Exact matching
405 of DSCP values is required (no masks or ranges).
406 the "deny" can replace the color_under or
407 color_over values in the meter action for rate-
408 dependent packet drop.
410 metering <rate> <color_under> <color_over>
411 The metering option provides Assured Forwarding,
412 as defined in [50], and MUST be present if the
413 action is set to meter. The rate option is the
414 throughput, in bits per second, which is used by
415 the access device to mark packets. Traffic above
416 the rate is marked with the color_over codepoint,
417 while traffic under the rate is marked with the
418 color_under codepoint. The color_under and
419 color_over options contain the drop preferences,
420 and MUST conform to the recommended codepoint
421 keywords described in [50] (e.g. AF13).
423 The metering option also supports the strict
424 limit on traffic required by Expedited
425 Forwarding, as defined in [51]. The color_over
426 option may contain the keyword "drop" to prevent
427 forwarding of traffic that exceeds the rate
430 The rule syntax is a modified subset of ipfw(8) from FreeBSD,
431 and the ipfw.c code may provide a useful base for
435 <typedefn type-name="MIPRegistrationRequest" type-parent="OctetString"/>
437 <typedefn type-name="Integer32"/>
439 32 bit signed value, in network byte order. The AVP Length
440 field MUST be set to 12 (16 if the 'V' bit is enabled).
442 <typedefn type-name="VendorId" type-parent="Integer32"/>
443 <typedefn type-name="AppId" type-parent="Integer32"/>
444 <typedefn type-name="Integer64"/>
446 64 bit signed value, in network byte order. The AVP Length
447 field MUST be set to 16 (20 if the 'V' bit is enabled).
449 <typedefn type-name="Unsigned32"/>
451 32 bit unsigned value, in network byte order. The AVP Length
452 field MUST be set to 12 (16 if the 'V' bit is enabled).
453 Unsigned32 values used to transmit time data contains the four
454 most significant octets returned from NTP [18], in network byte
457 <typedefn type-name="Time"/>
459 The Time format is derived from the Unsigned32 AVP Base Format.
460 This is 32 bit unsigned value containing the four most
461 significant octets returned from NTP [18], in network byte
464 This represent the number of seconds since 0h on 1 January 1900
465 with respect to the Coordinated Universal Time (UTC).
467 On 6h 28m 16s UTC, 7 February 2036 the time value will
468 overflow. NTP [18] describes a procedure to extend the time to
471 <typedefn type-name="Unsigned64"/>
473 64 bit unsigned value, in network byte order. The AVP Length
474 field MUST be set to 16 (20 if the 'V' bit is enabled).
476 <!-- ************************* End Typedefns ************************ -->
477 <!-- ******************* DIAMETER BASE PROTOCOL AVPS ************************ -->
478 <avp name="Accounting-Interim-Interval" code="482" mandatory="must" may-encrypt="yes" vendor-bit="mustnot">
479 <type type-name="Unsigned32"/>
481 <avp name="Accounting-Multi-Session-Id" code="50" mandatory="must" protected="may" may-encrypt="yes" vendor-bit="mustnot">
482 <type type-name="Unsigned32"/>
484 <avp name="Accounting-Record-Number" code="485" mandatory="must" may-encrypt="yes" vendor-bit="mustnot">
485 <type type-name="Unsigned32"/>
487 <avp name="Accounting-Record-Type" code="480" mandatory="must" may-encrypt="yes" vendor-bit="mustnot">
488 <type type-name="Unsigned32"/>
489 <enum name="Event Record" code="1"/>
490 <enum name="Start Record" code="2"/>
491 <enum name="Interim Record" code="3"/>
492 <enum name="Stop Record" code="4"/>
494 <avp name="Accounting-Session-Id" code="44" mandatory="must" protected="may" may-encrypt="yes" vendor-bit="mustnot">
495 <type type-name="Unsigned32"/>
497 <avp name="Acct-Application-Id" code="259" mandatory="must" protected="mustnot" may-encrypt="no" vendor-bit="mustnot">
498 <type type-name="AppId"/>
500 <avp name="Alternate-Peer" code="275" mandatory="must" protected="mustnot" may-encrypt="no" vendor-bit="mustnot">
501 <type type-name="DiameterIdentity"/>
503 <avp name="Auth-Application-Id" code="258" mandatory="must" protected="mustnot" may-encrypt="no" vendor-bit="mustnot">
504 <type type-name="AppId"/>
506 <avp name="Auth-Request-Type" code="274" mandatory="must" protected="mustnot" may-encrypt="no" vendor-bit="mustnot">
507 <type type-name="Unsigned32"/>
508 <enum name="Authenticate Only" code="1"/>
509 <enum name="Authorize Only" code="2"/>
510 <enum name="Authorize Authenticate" code="3"/>
512 <avp name="Authorization-Lifetime" code="291" mandatory="must" may-encrypt="no" vendor-bit="mustnot">
513 <type type-name="Integer32"/>
515 <avp name="Auth-Grace-Period" code="276" mandatory="must" may-encrypt="no" vendor-bit="mustnot">
516 <type type-name="Unsigned32"/>
518 <avp name="Auth-Session-State" code="277" mandatory="must" may-encrypt="no" vendor-bit="mustnot">
519 <type type-name="Unsigned32"/>
520 <enum name="State Maintained" code="0"/>
521 <enum name="No State Maintained" code="0"/>
523 <avp name="Re-Auth-Request-Type" code="285" mandatory="must" may-encrypt="no" vendor-bit="mustnot">
524 <type type-name="Unsigned32"/>
525 <enum name="Authorize Only" code="0"/>
526 <enum name="Authorize Authenticate" code="1"/>
528 <avp name="Destination-Host" code="293" mandatory="must" protected="mustnot" may-encrypt="no" vendor-bit="mustnot">
529 <type type-name="DiameterIdentity"/>
531 <avp name="Destination-Realm" code="283" mandatory="must" protected="mustnot" may-encrypt="no" vendor-bit="mustnot">
532 <type type-name="UTF8String"/>
534 <avp name="Disconnect-Cause" code="273" mandatory="must" protected="mustnot" may-encrypt="no" vendor-bit="mustnot">
535 <type type-name="Unsigned32"/>
536 <enum name="Rebooting" code="0"/>
537 <enum name="Busy" code="2"/>
538 <enum name="Do not want to talk to you" code="2"/>
540 <avp name="Error-Message" code="281" mandatory="must" protected="mustnot" may-encrypt="no" vendor-bit="mustnot">
541 <type type-name="UTF8String"/>
543 <avp name="Error-Reporting-Host" code="294" mandatory="must" protected="mustnot" may-encrypt="no" vendor-bit="mustnot">
544 <type type-name="DiameterIdentity"/>
546 <avp name="Failed-AVP" code="279" mandatory="must" may-encrypt="no" vendor-bit="mustnot">
547 <type type-name="OctetString"/>
549 <avp name="Firmware-Revision" code="267" mandatory="must" protected="mustnot" may-encrypt="no" vendor-bit="mustnot">
550 <type type-name="Unsigned32"/>
552 <avp name="Host-IP-Address" code="257" mandatory="must" protected="mustnot" may-encrypt="no" vendor-bit="mustnot">
553 <type type-name="IPAddress"/>
555 <avp name="Multi-Round-Time-Out" code="272" mandatory="must" may-encrypt="yes" vendor-bit="mustnot">
556 <type type-name="Unsigned32"/>
558 <avp name="Origin-Host" code="264" mandatory="must" may-encrypt="no" protected="mustnot" vendor-bit="mustnot">
559 <type type-name="DiameterIdentity"/>
561 <avp name="Origin-Realm" code="296" mandatory="must" may-encrypt="no" protected="mustnot" vendor-bit="mustnot">
562 <type type-name="UTF8String"/>
564 <avp name="Origin-State-Id" code="278" mandatory="must" protected="mustnot" vendor-bit="mustnot">
565 <type type-name="Unsigned32"/>
567 <avp name="Product-Name" code="269" mandatory="mustnot" may-encrypt="no" protected="mustnot" vendor-bit="mustnot">
568 <type type-name="UTF8String"/>
570 <avp name="Proxy-Host" code="280" mandatory="must" may-encrypt="no" protected="mustnot" vendor-bit="mustnot">
571 <type type-name="DiameterIdentity"/>
573 <avp name="Proxy-Info" code="284" mandatory="must" may-encrypt="no" protected="mustnot" vendor-bit="mustnot">
574 <type type-name="OctetString"/>
576 <avp name="Redirect-Host" code="292" mandatory="must" may-encrypt="no" protected="mustnot" vendor-bit="mustnot">
577 <type type-name="DiameterIdentity"/>
579 <avp name="Redirect-Host-Usage" code="261" mandatory="must" may-encrypt="no" protected="mustnot" vendor-bit="mustnot">
580 <type type-name="Unsigned32"/>
581 <enum name="Don't Care" code="0"/>
582 <enum name="All Session" code="1"/>
583 <enum name="All Realm" code="2"/>
584 <enum name="Realm and Application" code="3"/>
585 <enum name="All Application" code="4"/>
586 <enum name="All Host" code="5"/>
588 <avp name="Redirect-Max-Cache-Time" code="262" mandatory="must" may-encrypt="no" protected="mustnot" vendor-bit="mustnot">
589 <type type-name="Unsigned32"/>
591 <avp name="Result-Code" code="268" mandatory="must" may-encrypt="no" protected="mustnot" vendor-bit="mustnot">
592 <type type-name="Unsigned32"/>
594 <avp name="Route-Record" code="282" mandatory="must" may-encrypt="no" protected="mustnot" vendor-bit="mustnot">
595 <type type-name="DiameterIdentity"/>
597 <avp name="Session-Id" code="263" mandatory="must" protected="mustnot" vendor-bit="mustnot">
598 <type type-name="UTF8String"/>
600 <avp name="Session-Binding" code="270" mandatory="must" protected="mustnot" vendor-bit="mustnot">
601 <type type-name="Unsigned32"/>
603 <avp name="Session-Server-Failover" code="271" mandatory="must" protected="mustnot" vendor-bit="mustnot">
604 <type type-name="Unsigned32"/>
605 <enum name="Refuse Service" code="0"/>
606 <enum name="Try Again" code="1"/>
607 <enum name="Allow Service" code="2"/>
608 <enum name="Try Again / Allow Service" code="3"/>
610 <avp name="Source-Route" code="286" mandatory="must" may-encrypt="no" protected="mustnot" vendor-bit="mustnot">
611 <type type-name="DiameterIdentity"/>
613 <avp name="Supported-Vendor-Id" code="265" mandatory="must" may-encrypt="no" protected="mustnot" vendor-bit="mustnot">
614 <type type-name="VendorId"/>
616 <avp name="Termination-Cause" code="295" mandatory="must" may-encrypt="no" protected="mustnot" vendor-bit="mustnot">
617 <type type-name="Unsigned32"/>
618 <enum name="Logout" code="1"/>
619 <enum name="Service Not Provided" code="2"/>
620 <enum name="Bad Answer" code="3"/>
621 <enum name="Administrative" code="4"/>
622 <enum name="Link Broken" code="5"/>
624 <avp name="Vendor-Id" code="266" mandatory="must" may-encrypt="no" protected="mustnot" vendor-bit="mustnot">
625 <type type-name="VendorId"/>
627 <avp name="Vendor-Specific-Application-Id" code="260" mandatory="must" may-encrypt="no" protected="mustnot" vendor-bit="mustnot">
629 <gavp name="Vendor-Id"/>
630 <gavp name="Auth-Application-Id"/>
631 <gavp name="Acct-Application-Id"/>
634 <avp name="Example-AVP" code="999999" mandatory="mustnot" vendor-bit="may">
636 <gavp name="Origin-Host"/>
637 <gavp name="Host-IP-Address"/>
640 <!-- ************************ END DIAMETER BASE PROTOCOL AVPS ******************* -->