Skip to main content

11.3. AVP Values

11.3. AVP Values​

For AVP values, the Experimental-Result-Code AVP value allocation has been added; see Section 11.3.1. The old AVP value allocation rule, IETF Consensus, has been updated to IETF Review as per [RFC5226], and affected AVPs are listed as reminders.

11.3.1. Experimental-Result-Code AVP​

Values for this AVP are purely local to the indicated vendor, and no IANA registry is maintained for them.

11.3.2. Result-Code AVP Values​

New values are available for assignment via IETF Review [RFC5226].

11.3.3. Accounting-Record-Type AVP Values​

New values are available for assignment via IETF Review [RFC5226].

11.3.4. Termination-Cause AVP Values​

New values are available for assignment via IETF Review [RFC5226].

11.3.5. Redirect-Host-Usage AVP Values​

New values are available for assignment via IETF Review [RFC5226].

11.3.6. Session-Server-Failover AVP Values​

New values are available for assignment via IETF Review [RFC5226].

11.3.7. Session-Binding AVP Values​

New values are available for assignment via IETF Review [RFC5226].

11.3.8. Disconnect-Cause AVP Values​

New values are available for assignment via IETF Review [RFC5226].

11.3.9. Auth-Request-Type AVP Values​

New values are available for assignment via IETF Review [RFC5226].

11.3.10. Auth-Session-State AVP Values​

New values are available for assignment via IETF Review [RFC5226].

11.3.11. Re-Auth-Request-Type AVP Values​

New values are available for assignment via IETF Review [RFC5226].

11.3.12. Accounting-Realtime-Required AVP Values​

New values are available for assignment via IETF Review [RFC5226].

11.3.13. Inband-Security-Id AVP (code 299)​

The use of this AVP has been deprecated.

Last updated on