Softwire Mesh Framework

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.

[1]  Stephen T. Kent,et al.  IP Encapsulating Security Payload (ESP) , 1995, RFC.

[2]  Eric C. Rosen,et al.  BGP IPsec Tunnel Encapsulation Attribute , 2009, RFC.

[3]  Stephen E. Deering,et al.  IP Version 6 Addressing Architecture , 1995, RFC.

[4]  Charlie Kaufman,et al.  Internet Key Exchange (IKEv2) Protocol , 2005, RFC.

[5]  Vijay Srinivasan,et al.  RSVP-TE: Extensions to RSVP for LSP Tunnels , 2001, RFC.

[6]  Arjen Boers,et al.  The Reverse Path Forwarding (RPF) Vector TLV , 2009, RFC.

[7]  Eric C. Rosen,et al.  Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop , 2009, RFC.

[8]  Kireeti Kompella,et al.  Label Distribution Protocol Extensions for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths , 2011, RFC.

[9]  Dino Farinacci,et al.  Generic Routing Encapsulation (GRE) , 2000, RFC.

[10]  Scott O. Bradner,et al.  Key words for use in RFCs to Indicate Requirement Levels , 1997, RFC.

[11]  Ina Minei,et al.  LDP Specification , 2007, RFC.

[12]  John Moy,et al.  OSPF Version 2 , 1998, RFC.

[13]  Pekka Savola,et al.  MTU and Fragmentation Issues with In-the-Network Tunneling , 2006, RFC.

[14]  Stephen T. Kent,et al.  IP Authentication Header , 1995, RFC.

[15]  Jeremy De Clercq,et al.  Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE) , 2007, RFC.

[16]  Yakov Rekhter,et al.  BGP/MPLS IP Virtual Private Networks (VPNs) , 2006, RFC.

[17]  Eric C. Rosen,et al.  The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute", RFC 5512 , 2009 .

[18]  Hugo Krawczyk,et al.  A Security Architecture for the Internet Protocol , 1999, IBM Syst. J..

[19]  Yakov Rekhter,et al.  Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE) , 2005, RFC.

[20]  David Ward,et al.  Softwire Problem Statement , 2007, RFC.

[21]  Arnaud Gonguet,et al.  Framework for Layer 3 Virtual Private Networks (L3VPN) Operations and Management , 2005, RFC.

[22]  Ross W. Callon,et al.  Use of OSI IS-IS for routing in TCP/IP and dual environments , 1990, RFC.

[23]  Dino Farinacci,et al.  MPLS Label Stack Encoding , 2001, RFC.

[24]  Thomas D. Nadeau,et al.  A Framework for Multi-Protocol Label Switching (MPLS) Operations and Management (OAM) , 2006, RFC.

[25]  Andy Heffernan,et al.  Protection of BGP Sessions via the TCP MD5 Signature Option , 1998, RFC.

[26]  Ignacio Goyret,et al.  Layer Two Tunneling Protocol - Version 3 (L2TPv3) , 2005, RFC.

[27]  Eric C. Rosen,et al.  Multiprotocol Label Switching Architecture , 2001, RFC.

[28]  Charles E. Perkins,et al.  IP Encapsulation within IP , 1996, RFC.