RFC 4923: Quality of Service (QoS) Signaling in a Nested Virtual Private Network
In plain English — editorial summary, not part of the RFC
Some networks require communication between an interior and exterior portion of a Virtual Private Network (VPN) or through a concatenation of such networks resulting in a nested VPN, but have sensitivities about what information is communicated across the boundary, especially while providing quality of service to communications with different precedence. This note seeks to outline the issues and the nature of the proposed solutions based on the framework for Integrated Services operation over Diffserv networks as described in RFC 2998. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4923
- Published
- August 2007
- Authors
- F. Baker; P. Bose
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 38
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9484Proxying IP in HTTPCurrent
October 2023
- RFC 4883Benchmarking Terminology for Resource Reservation Capable RoutersCurrent
July 2007
- RFC 4834Requirements for Multicast in Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs)Current
April 2007
- RFC 4555IKEv2 Mobility and Multihoming Protocol (MOBIKE)Current
June 2006
- RFC 5501Requirements for Multicast Support in Virtual Private LAN ServicesCurrent
March 2009
- RFC 4031Service Requirements for Layer 3 Provider Provisioned Virtual Private Networks (PPVPNs)Current
April 2005
- RFC 6517Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN SolutionCurrent
February 2012
- RFC 6565OSPFv3 as a Provider Edge to Customer Edge (PE-CE) Routing ProtocolCurrent
June 2012
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?