Definition of Textual Conventions for Virtual Private Network (VPN) Management
Extracted elements (6)
The VPN-ID structure (3-octet OUI + 4-octet index) is adopted directly from RFC 2685, which defined the Global VPN Identifier format. Reusing an existing identifier scheme allows interoperability across VPN management frameworks without introducing a new naming authority.
A VPN-ID MUST be 7 octets in length, and SHOULD be comprised of a 3-octet OUI followed by a 4-octet VPN index.
The VPNId Textual Convention defines a 7-octet OCTET STRING to uniquely identify a VPN. It consists of a 3-octet Organizationally Unique Identifier (OUI) identifying the VPN Authority, followed by a 4-octet value assigned by the VPN Authority that uniquely identifies the VPN within the context of that OUI.
The VPNIdOrZero Textual Convention extends VPNId by also permitting a zero-length OCTET STRING (SIZE (0 | 7)). The zero-length value's semantics are object-specific and must be defined in the description of each object that uses this syntax, covering use cases such as referencing no VPN or all VPNs.
IANA assigned the OID { mib-2 129 } to the VPN-TC-STD-MIB module defined in this document.
This module defines only Textual Conventions and no management objects; meaningful security considerations must be written in the MIB modules that use these TCs to define actual management objects. Therefore this document has no direct impact on the security of the Internet.