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

IANA rules for PANA are relaxed to add IESG Approval as an additional allocation path alongside existing mechanisms. This enables the IESG to consider allocation requests (e.g., for experimental protocol extensions from reserved bits) that do not fulfill the default rule, provided sufficient bits remain and the PANA community concurs.

registry, process

No guarantee of interoperability is made for experimental message types (65,520–65,535) between a PANA Client (PaC) and PANA Authentication Agent (PAA), as these codes are intended only for experimental and testing purposes per RFC 3692.

registry, security

PANA Message Types range 65,520–65,535 (0xfff0–0xffff) is reserved for experimental messages. The same Message Type value is used for both request and answer messages (except type 1); the Request bit distinguishes the two.

registry

AVP Flags registry for the 16-bit AVP Flags field is updated to allow allocation of remaining bits via Standards Action or IESG Approval. Previously only Standards Action was permitted. Bit 0 ('V') is already assigned by RFC 5191.

registry

Message Flags registry for the 16-bit Flags field in the PANA message header is updated to allow allocation of remaining free bits via Standards Action or IESG Approval. Previously only Standards Action was permitted. Bits 0–5 are already assigned by RFC 5191.

registry

Message Types registry for PANA (values 1–65,519) is updated to allow allocation by IETF Review or IESG Approval. Previously only IETF Review was permitted. Value 0 is unassigned; values 65,520–65,535 are reserved for experimental use.

registry

Result-Code AVP Values registry (AVP Code 7) is updated to allow assignment of remaining values via IETF Review or IESG Approval. Previously only IETF Review was permitted. Values 0–2 are defined by RFC 5191.

registry

Termination-Cause AVP Values registry (AVP Code 9) is updated to allow assignment of remaining values via IETF Review or IESG Approval. Previously only IETF Review was permitted. Values 1, 4, and 8 are defined by RFC 5191.

registry

This specification does not change the security properties of PANA. However, experimental code points (65,520–65,535) carry risk: potentially harmful side effects must be carefully evaluated before deploying experiments across networks not entirely controlled by the experimenter, following guidance in RFC 3692.

security