ietf-corpus

rfc-7892

IANA Allocation Procedures for the GMPLS OTN Signal Type Registry

Z. Ali, A. Bonfanti, M. Hartley, F. Zhang
date2016-05 streamIETF areartg wgccamp statusPROPOSED STANDARD pages4 canonicalhttps://www.rfc-editor.org/rfc/rfc7892 doi10.17487/RFC7892
IANA defined the "OTN Signal Type" subregistry of the "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Parameters" registry in RFC 7139. This document updates the "OTN Signal Type" subregistry to allow registration via Specification Required.

updates

Extracted elements (4)

design-rationale §1

The registration policy for the OTN Signal Type subregistry was expanded from Standards Action only to also include Specification Required, enabling registration by documents outside the Standards Track. This change facilitates broader use and registration of OTN signal types without requiring full IETF Standards Track progression.

registry, mpls, routing, process

normative-requirement §3 REQUIRED

IANA must apply 'Standards Action' registration policy for Standards Track documents and 'Specification Required' registration policy for other documents when processing registrations in the 'OTN Signal Type' subregistry.

registry, mpls, routing, process

registry §3

The 'OTN Signal Type' subregistry of the 'Generalized Multi-Protocol Label Switching (GMPLS) Signaling Parameters' registry is updated to allow two registration policies: 'Standards Action' for Standards Track documents and 'Specification Required' for other documents. Previously, only Standards Action was permitted.

registry, mpls, routing

security-consideration §2

This document does not introduce any new security considerations to the existing GMPLS signaling protocols. Implementers should refer to RFC 7139 for security measures and RFC 5920 for an overview of security vulnerabilities and protection mechanisms for the GMPLS control plane.

security, mpls, routing