UNLIMITED FREE
ACCESS
TO THE WORLD'S BEST IDEAS

SUBMIT
Already a GlobalSpec user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your GlobalSpec Experience

Finish!
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

IETF RFC 5872

IANA Rules for the Protocol for Carrying Authentication for Network Access (PANA)

active, Most Current
Buy Now
Organization: IETF
Publication Date: 1 May 2010
Status: active
Page Count: 5
scope:

Introduction

This document relaxes the IANA rules for the Protocol for Carrying Authentication for Network Access (PANA) [RFC5191]. Rules for the following protocol fields, all defined in [RFC5191], are affected:

o Message Types

o Message Flags

o Attribute-Value Pair (AVP) Flags

o Result-Code AVP Values

o Termination-Cause AVP Values

The rationale for this update is that there can be situations in which it makes sense to grant an allocation under special circumstances. At the time of this writing, the IETF is in the process of approving one such allocation. By changing the current IANA rules to allow for IESG Approval [RFC5226] as well, it has become possible for the Internet Engineering Steering Group (IESG) to consider an allocation request, even if it does not fulfill the default rule. For instance, an experimental protocol extension could perhaps deserve an allocation from a field of reserved bits, as long as a sufficient number of bits still remain for other purposes, and the PANA community is happy with such allocation.

Document History

IETF RFC 5872
May 1, 2010
IANA Rules for the Protocol for Carrying Authentication for Network Access (PANA)
Introduction This document relaxes the IANA rules for the Protocol for Carrying Authentication for Network Access (PANA) [RFC5191]. Rules for the following protocol fields, all defined in [RFC5191],...

References

Advertisement