
Protocol for Carrying Authentication for Network Access (PANA) Parameters

(last updated 2008-05-12)

Registries included below:
- Message Types
- Message Flags 
- AVP Codes 
  - Result-Code (AVP Code 7) AVP Values 
  - Termination-Cause (AVP Code 9) AVP Values
- AVP Flags


Registry Name: Message Types
Reference: [RFC5191]
Range         Registration Procedures        Notes
------------  -----------------------------  ----------------------   
1-65519       IETF Consensus
65520-65535   IANA does not assign           Outlined in [RFC3692]

Registry:
Value         Req/Ans  Abbrev  Name                          Reference
------------  -------  ------  ----------------------------  ---------
0                              Reserved                      [RFC5191]
1             Req      PCI     PANA-Client-Initiation        [RFC5191]
2             Req      PAR     PANA-Auth-Request             [RFC5191]
2             Ans      PAN     PANA-Auth-Answer              [RFC5191]
3             Req      PTR     PANA-Termination-Request      [RFC5191]
3             Ans      PTA     PANA-Termination-Answer       [RFC5191]
4             Req      PNR     PANA-Notification-Request     [RFC5191]
4             Ans      PNA     PANA-Notification-Answer      [RFC5191]
5-65519                        Unassigned                    [RFC5191]
65520-65535                    Reserved (Experimental)       [RFC5191]


Registry Name: Message Flags 
Reference: [RFC5191]
Registration Procedures: Standards Action

Registry:
Bit   Code  Description             Reference
----  ----  ----------------------  ---------
0     R     Request                 [RFC5191]
1     S     Start                   [RFC5191]
2     C     Complete                [RFC5191]
3     A     re-Authentication       [RFC5191]
4     P     Ping                    [RFC5191]
5     I     IP Reconfiguration      [RFC5191]
6-15        Unassigned 


Registry Name: AVP Codes 
Reference: [RFC5191]
Registration Procedures: Expert Review with Specification Required, or Standards Action

Registry:
Code       Attribute Name              Reference
---------  --------------------------  ---------
0          Reserved                    [RFC5191]
1          AUTH                        [RFC5191]
2          EAP-Payload                 [RFC5191]
3          Integrity-Algorithm         [RFC5191]
4          Key-Id                      [RFC5191]
5          Nonce                       [RFC5191]
6          PRF-Algorithm               [RFC5191]
7          Result-Code                 [RFC5191] 
8          Session-Lifetime            [RFC5191]
9          Termination-Cause           [RFC5191] 
10-65535   Unassigned                  [RFC5191]

Sub-registry: Result-Code (AVP Code 7) AVP Values 
Reference: [RFC5191]
Registration Procedures: IETF Consensus

Registry:
Value          Meaning                            Reference
-------------  ---------------------------------  ---------
0              PANA_SUCCESS                       [RFC5191]
1              PANA_AUTHENTICATION_REJECTED       [RFC5191]
2              PANA_AUTHORIZAZTION_REJECTED       [RFC5191]
3-4294967295   Unassigned                         [RFC5191]

Sub-registry: Termination-Cause (AVP Code 9) AVP Values 
Reference: [RFC5191]
Registration Procedures: IETF Consensus

Registry:
Value           Meaning                          Reference
--------------  -------------------------------  ---------
0               Unassigned                       [RFC5191]
1               LOGOUT                           [RFC5191]
2-3             Unassigned                       [RFC5191]
4               ADMINISTRATIVE                   [RFC5191]
5-7             Unassigned                       [RFC5191]
8               SESSION_TIMEOUT                  [RFC5191]
9-4294967295    Unassigned                       [RFC5191]


Registry Name: AVP Flags 
Reference: [RFC5191]
Registration Procedures: Standards Action

Registry:
Bit    Code  Description      Reference
-----  ----  ---------------  ---------
0      V     Vendor           [RFC5191]
1-15         Unassigned       [RFC5191]


References
----------
[RFC3692]  T. Narten, "Assigning Experimental and Testing Numbers Considered 
           Useful", RFC 3692, January 2004

[RFC5191]  D. Forsberg, Y. Ohba (Ed.), B. Patil, H. Tschofenig and A. Yegin,
           "Protocol for Carrying Authentication for Network Access (PANA)",
           RFC 5191, May 2008.


(created 2007-10-08)

[]
