Softwire Mesh Framework
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 31
- Abstract
- The Internet needs to be able to handle both IPv4 and IPv6 packets. However, it is expected that some constituent networks of the Internet will be "single-protocol" networks. One kind of single-protocol network can parse only IPv4 packets and can process only IPv4 routing information; another kind can parse only IPv6 packets and can process only IPv6 routing information. It is nevertheless required that either kind of single-protocol network be able to provide transit service for the "other" protocol. This is done by passing the "other kind" of routing information from one edge of the single-protocol network to the other, and by tunneling the "other kind" of data packet from one edge to the other. The tunnels are known as "softwires". This framework document explains how the routing information and the data packets of one protocol are passed through a single-protocol network of the other protocol. The document is careful to specify when this can be done with existing technology and when it requires the development of new or modified technology. [STANDARDS-TRACK]
- Publication Date
- 2009-06-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC5565- Link
- https://doi.org/10.17487/RFC5565
- Author(s)
- Jianping WuYong CuiChris MetzEric C. Rosen
Latest version of IETF RFC 5565
Document Versions — IETF RFC 5565
-
▶ IETF RFC 5565 (2009-06-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2003 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 2784 [Active*]
- IETF RFC 3031 [Active*]
- IETF RFC 3032 [Active*]
- IETF RFC 3209 [Active*]
- IETF RFC 3931 [Active*]
- IETF RFC 4023 [Active*]
- IETF RFC 4798 [Active*]
- IETF RFC 5512 [Superseded*]
- IETF RFC 5549 [Superseded*]
- IETF RFC 5566 [Superseded*]
Bibliographic Reference(s)
- Katz, D. and D. Ward, "Bidirectional Forwarding Detection", Work in Progress, February 2009. EXTERNAL
- Aggarwal, R., Rosen, E., Morin, T. and Y. Rekhter, "BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs", Work in Progress, April 2009. EXTERNAL
- Rosen, E., Ed., and R. Aggarwal, Ed., "Multicast in MPLS/BGP IP VPNs", Work in Progress, March 2009. EXTERNAL
- Minei, I., Ed., Kompella, K., Wijnands, IJ., Ed., and B. Thomas, "Label Distribution Protocol Extensions for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths", Work in Progress, April 2009. EXTERNAL
- IETF RFC 1195 [Active*]
- IETF RFC 2328 [Active*]
- IETF RFC 2385 [Superseded*]
- RFC4176 — RFC4176 EXTERNAL
- IETF RFC 4271 [Active*]
- IETF RFC 4291 [Active*]
- IETF RFC 4301 [Active, Amended*]
- IETF RFC 4302 [Active*]
- IETF RFC 4303 [Active*]
- IETF RFC 4306 [Superseded*]
- IETF RFC 4364 [Active*]
- IETF RFC 4378 [Active*]
- IETF RFC 4459 [Active*]
- IETF RFC 4925 [Active*]
- IETF RFC 5036 [Active*]
- RFC5496 — RFC5496 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5565.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 5565, Softwire Mesh Framework. Available at https://doi.org/10.17487/RFC5565
Snippet:
IETF RFC 5565, Softwire Mesh Framework. Available at https://doi.org/10.17487/RFC5565
HTML (ISO 690 compliant)
Preview:
IETF RFC 5565, Softwire Mesh Framework. Available at https://doi.org/10.17487/RFC5565
Snippet:
<span class="citation"><cite>IETF RFC 5565</cite>, Softwire Mesh Framework. Available at <a href="https://doi.org/10.17487/RFC5565" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5565</a></span>
SMPTE's HTML Pub
Preview:
Snippet:
<li> <cite id="bib-rfc5565">IETF RFC 5565</cite>, Softwire Mesh Framework <span class="doi">10.17487/RFC5565</span> </li>
Referenced By
- IETF RFC 5566 [Superseded*]
- IETF RFC 5619 [Active*]
- IETF RFC 6180 [Active*]