RFC 4265: Definition of Textual Conventions for Virtual Private Network (VPN) Management
In plain English — editorial summary, not part of the RFC
This document describes Textual Conventions used for managing Virtual Private Networks (VPNs). [STANDARDS-TRACK]
Document record
- Document ID
- RFC4265
- Published
- November 2005
- Authors
- B. Schliesser; T. Nadeau
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3291Textual Conventions for Internet Network AddressesObsoleted
May 2002
- RFC 4271A Border Gateway Protocol 4 (BGP-4)Updated
January 2006
- RFC 4258Requirements for Generalized Multi-Protocol Label Switching (GMPLS) Routing for the Automatically Switched Optical Network (ASON)Current
November 2005
- RFC 4272BGP Security Vulnerabilities AnalysisCurrent
January 2006
- RFC 4257Framework for Generalized Multi-Protocol Label Switching (GMPLS)-based Control of Synchronous Digital Hierarchy/Synchronous Optical Networking (SDH/SONET) NetworksCurrent
December 2005
- RFC 4273Definitions of Managed Objects for BGP-4Current
January 2006
- RFC 4274BGP-4 Protocol AnalysisCurrent
January 2006
- RFC 4275BGP-4 MIB Implementation SurveyCurrent
January 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?