Softwire Hub and Spoke Deployment Framework with Layer Two Tunneling Protocol Version 2 (L2TPv2)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 41
- Abstract
- 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]
- Publication Date
- 2009-06-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC5571- Link
- https://doi.org/10.17487/RFC5571
- Author(s)
- Bill StorerCarlos PignataroMaria SantosBruno StevantLaurent ToutainJean-Francois Tremblay
- Keyword(s)
- Softwire, L2TP, 4over6, 6over4
Latest version of IETF RFC 5571
Document Versions — IETF RFC 5571
-
▶ IETF RFC 5571 (2009-06-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 1332 [Active*]
- IETF RFC 1661 [Active*]
- IETF RFC 1918 [Active*]
- IETF RFC 1994 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 2661 [Active*]
- IETF RFC 2865 [Active*]
- IETF RFC 3162 [Active*]
- IETF RFC 3193 [Active*]
- IETF RFC 3315 [Superseded*]
- RFC3371 — RFC3371 EXTERNAL
- IETF RFC 3633 [Superseded*]
- IETF RFC 3736 [Superseded*]
- IETF RFC 3947 [Active*]
- IETF RFC 3948 [Active*]
- IETF RFC 4818 [Active*]
- IETF RFC 4862 [Active*]
- IETF RFC 5072 [Active*]
Bibliographic Reference(s)
- Johnson, R., Kumarasamy, J., Kinnear, K., and M. Stapp, "Subnet Allocation Option", Work in Progress, March 2009. EXTERNAL
- Lau, W., "DHCPv6 Relay agent RADIUS Attribute Option" , Work in Progress, February 2006. EXTERNAL
- Stevant, B., Toutain, L., Dupont, F., and D. Binet, "Accounting on Softwires", Work in Progress, April 2009. EXTERNAL
- Yamamoto, S., Williams, C., Parent, F., and H. Yokota, "Softwire Security Analysis and Requirements", Work in Progress, May 2009. EXTERNAL
- IETF RFC 1471 [Active*]
- IETF RFC 1473 [Active*]
- IETF RFC 1877 [Active*]
- IETF RFC 2131 [Active*]
- IETF RFC 2132 [Active*]
- IETF RFC 2433 [Active*]
- IETF RFC 2867 [Active*]
- IETF RFC 2868 [Active*]
- IETF RFC 3022 [Active*]
- IETF RFC 3575 [Active*]
- IETF RFC 3646 [Active*]
- IETF RFC 3748 [Active*]
- IETF RFC 3931 [Active*]
- IETF RFC 4087 [Active*]
- IETF RFC 4193 [Active*]
- IETF RFC 4293 [Active*]
- IETF RFC 4623 [Active*]
- IETF RFC 4787 [Active*]
- IETF RFC 4861 [Active*]
- IETF RFC 4925 [Active*]
- IETF RFC 4941 [Superseded*]
- IETF RFC 5080 [Active*]
- IETF RFC 5405 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5571.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5571, Softwire Hub and Spoke Deployment Framework with Layer Two Tunneling Protocol Version 2 (L2TPv2). Available at https://doi.org/10.17487/RFC5571
Snippet:
IETF RFC 5571, Softwire Hub and Spoke Deployment Framework with Layer Two Tunneling Protocol Version 2 (L2TPv2). Available at https://doi.org/10.17487/RFC5571
HTML (ISO 690 compliant)
Preview:
IETF RFC 5571, Softwire Hub and Spoke Deployment Framework with Layer Two Tunneling Protocol Version 2 (L2TPv2). Available at https://doi.org/10.17487/RFC5571
Snippet:
<span class="citation"><cite>IETF RFC 5571</cite>, Softwire Hub and Spoke Deployment Framework with Layer Two Tunneling Protocol Version 2 (L2TPv2). Available at <a href="https://doi.org/10.17487/RFC5571" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5571</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5571, Softwire Hub and Spoke Deployment Framework with Layer Two Tunneling Protocol Version 2 (L2TPv2)
doi: 10.17487/RFC5571
url: https://doi.org/10.17487/RFC5571
doi: 10.17487/RFC5571
url: https://doi.org/10.17487/RFC5571
Snippet:
<li> <cite id="bib-rfc5571">IETF RFC 5571</cite>, Softwire Hub and Spoke Deployment Framework with Layer Two Tunneling Protocol Version 2 (L2TPv2) <span class="doi">10.17487/RFC5571</span> </li>
Referenced By
- IETF RFC 5619 [Active*]
- IETF RFC 6333 [Active*]
- IETF RFC 6343 [Active*]