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

Internet Engineering Task Force (IETF)                          J. Arkko
Request for Comments: 5872                                      Ericsson
Updates: <a href="./rfc5191">5191</a>                                                   A. Yegin
Category: Standards Track                                        Samsung
ISSN: 2070-1721                                                 May 2010


                           <span class="h1">IANA Rules for the</span>
     <span class="h1">Protocol for Carrying Authentication for Network Access (PANA)</span>

Abstract

   This document relaxes the IANA rules for the Protocol for Carrying
   Authentication for Network Access (PANA).

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="https://www.rfc-editor.org/info/rfc5872">http://www.rfc-editor.org/info/rfc5872</a>.

Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.








<span class="grey">Arkko & Yegin                Standards Track                    [Page 1]</span>

<span id="page-2" ></span>
<span class="grey"><a href="./rfc5872">RFC 5872</a>                     PANA IANA Rules                    May 2010</span>


<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   This document relaxes the IANA rules for the Protocol for Carrying
   Authentication for Network Access (PANA) [<a href="./rfc5191" title=""Protocol for Carrying Authentication for Network Access (PANA)"">RFC5191</a>].  Rules for the
   following protocol fields, all defined in [<a href="./rfc5191" title=""Protocol for Carrying Authentication for Network Access (PANA)"">RFC5191</a>], 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 [<a href="./rfc5226" title="">RFC5226</a>] 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.

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  IANA Considerations</span>

   IANA has updated the registries related to PANA Message Types,
   Message Flags, AVP Flags, Result-Code AVP Values, and Termination-
   Cause AVP Values, as specified below.  All other PANA IANA registries
   are to remain unchanged.

<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>.  Message Types</span>

   The Message Types namespace is used to identify PANA messages.  Value
   0 is not used and is not assigned by IANA.  The range of values from
   1 - 65,519 are for permanent, standard Message Types, allocated by
   IETF Review or IESG Approval [<a href="./rfc5226" title="">RFC5226</a>].  Previously, the rule for
   this range was allocation by IETF Review only.  [<a href="./rfc5191" title=""Protocol for Carrying Authentication for Network Access (PANA)"">RFC5191</a>] defined the
   range of values from 1 - 4.  The same Message Type is used for both
   the request and the answer messages, except for type 1.  The Request
   bit distinguishes requests from answers.






<span class="grey">Arkko & Yegin                Standards Track                    [Page 2]</span>

<span id="page-3" ></span>
<span class="grey"><a href="./rfc5872">RFC 5872</a>                     PANA IANA Rules                    May 2010</span>


   The range of values from 65,520 - 65,535 (hexadecimal values 0xfff0 -
   0xffff) is reserved for experimental messages.  As these codes are
   only for experimental and testing purposes, no guarantee is made for
   interoperability between the communicating PANA Client (PaC) and PANA
   Authentication Agent (PAA) using experimental commands, as outlined
   in [<a href="./rfc3692" title=""Assigning Experimental and Testing Numbers Considered Useful"">RFC3692</a>].

<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>.  Message Flags</span>

   There are 16 bits in the Flags field of the PANA message header.
   <a href="./rfc5191#section-6.2">Section 6.2 of [RFC5191]</a> assigned bit 0 ('R'), 1 ('S'), 2 ('C'), 3
   ('A'), 4 ('P'), and 5 ('I').  Allocations from the remaining free
   bits in the PANA header Flag field are made via Standards Action or
   IESG Approval [<a href="./rfc5226" title="">RFC5226</a>].  Previously, the rule for these bits was
   allocation by Standards Action only.

<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>.  AVP Flags</span>

   There are 16 bits in the AVP Flags field of the AVP header, defined
   in <a href="./rfc5191#section-6.3">Section 6.3 of [RFC5191]</a>.  That RFC also assigned bit 0 ('V').
   The remaining bits are assigned via Standards Action or IESG Approval
   [<a href="./rfc5226" title="">RFC5226</a>].  Previously, the rule for these bits was allocation by
   Standards Action only.

<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>.  Result-Code AVP Values</span>

   As defined in <a href="./rfc5191#section-8.7">Section 8.7 of [RFC5191]</a>, the Result-Code AVP (AVP
   Code 7) defines the values from 0 - 2.

   All remaining values are available for assignment via IETF Review or
   IESG Approval [<a href="./rfc5226" title="">RFC5226</a>].  Previously, the rule for these values was
   allocation by IETF Review only.

<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>.  Termination-Cause AVP Values</span>

   As defined in <a href="./rfc5191#section-8.9">Section 8.9 of [RFC5191]</a>, the Termination-Cause AVP
   (AVP Code 9) defines the values 1, 4, and 8.

   All remaining values are available for assignment via IETF Review or
   IESG Approval [<a href="./rfc5226" title="">RFC5226</a>].  Previously, the rule for these values was
   allocation by IETF Review only.










<span class="grey">Arkko & Yegin                Standards Track                    [Page 3]</span>

<span id="page-4" ></span>
<span class="grey"><a href="./rfc5872">RFC 5872</a>                     PANA IANA Rules                    May 2010</span>


<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Security Considerations</span>

   This specification does not change the security properties of PANA.

   However, a few words are necessary about the use of the experimental
   code points defined in <a href="#section-2.1">Section 2.1</a>.  Potentially harmful side effects
   from the use of the experimental values need to be carefully
   evaluated before deploying any experiment across networks that the
   owner of the experiment does not entirely control.  Guidance given in
   [<a href="./rfc3692" title=""Assigning Experimental and Testing Numbers Considered Useful"">RFC3692</a>] about the use of experimental values needs to be followed.

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  References</span>

<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>.  Normative References</span>

   [<a id="ref-RFC5191">RFC5191</a>]  Forsberg, D., Ohba, Y., Patil, B., Tschofenig, H., and A.
              Yegin, "Protocol for Carrying Authentication for Network
              Access (PANA)", <a href="./rfc5191">RFC 5191</a>, May 2008.

   [<a id="ref-RFC5226">RFC5226</a>]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
              May 2008.

<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>.  Informative References</span>

   [<a id="ref-RFC3692">RFC3692</a>]  Narten, T., "Assigning Experimental and Testing Numbers
              Considered Useful", <a href="https://www.rfc-editor.org/bcp/bcp82">BCP 82</a>, <a href="./rfc3692">RFC 3692</a>, January 2004.
























<span class="grey">Arkko & Yegin                Standards Track                    [Page 4]</span>

<span id="page-5" ></span>
<span class="grey"><a href="./rfc5872">RFC 5872</a>                     PANA IANA Rules                    May 2010</span>


<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>.  Changes from <a href="./rfc5191">RFC 5191</a></span>

   This document changes the IANA rules for: Message Types, Message
   Flags, AVP Flags, Result-Code AVP Values, and Termination-Cause AVP
   Values.

<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>.  Acknowledgments</span>

   The authors would like to thank Yoshihiro Ohba, Ralph Droms,
   Magnus Westerlund, and Alfred Hoenes for reviews and comments on this
   topic.

Authors' Addresses

   Jari Arkko
   Ericsson
   Jorvas  02420
   Finland

   EMail: [email protected]


   Alper Yegin
   Samsung
   Istanbul
   Turkey

   EMail: [email protected]























Arkko & Yegin                Standards Track                    [Page 5]