RFC 5571: Softwire Hub and Spoke Deployment Framework with Layer Two Tunneling Protocol Version 2 (L2TPv2)
In plain English — editorial summary, not part of the RFC
This document describes the framework of the Softwire "Hub and Spoke" solution with the Layer Two Tunneling Protocol version 2 (L2TPv2). The implementation details specified in this document should be followed to achieve interoperability among different vendor implementations. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5571
- Published
- June 2009
- Authors
- B. Storer; C. Pignataro; M. Dos Santos; B. Stevant; L. Toutain; J. Tremblay
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 41
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5512The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation AttributeObsoleted
April 2009
- RFC 5619Softwire Security Analysis and RequirementsCurrent
August 2009
- RFC 6334Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual-Stack LiteCurrent
August 2011
- RFC 7341DHCPv4-over-DHCPv6 (DHCP 4o6) TransportCurrent
August 2014
- RFC 8026Unified IPv4-in-IPv6 Softwire Customer Premises Equipment (CPE): A DHCPv6-Based Prioritization MechanismCurrent
November 2016
- RFC 2661Layer Two Tunneling Protocol "L2TP"Updated
August 1999
- RFC 8539Softwire Provisioning Using DHCPv4 over DHCPv6Current
March 2019
- RFC 8675A YANG Data Model for Tunnel Interface TypesCurrent
November 2019
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?