All, I have updated the draft and have added Jeff Tantsura as co-author to the draft.
Thank you Gyan ---------- Forwarded message --------- From: Mishra, Gyan S <gyan.s.mis...@verizon.com> Date: Sat, Aug 22, 2020 at 2:22 AM Subject: Fwd: [E] New Version Notification for draft-mishra-bess-ipv4nlri-ipv6nh-use-cases-03.txt To: Hayabusanew <hayabusa...@gmail.com> ---------- Forwarded message --------- From: <internet-dra...@ietf.org> Date: Sat, Aug 22, 2020 at 2:20 AM Subject: [E] New Version Notification for draft-mishra-bess-ipv4nlri-ipv6nh-use-cases-03.txt To: Jeff Tantsura <jefftant.i...@gmail.com>, Gyan Mishra < gyan.s.mis...@verizon.com>, Mankamana Mishra <manka...@cisco.com> A new version of I-D, draft-mishra-bess-ipv4nlri-ipv6nh-use-cases-03.txt has been successfully submitted by Gyan Mishra and posted to the IETF repository. Name: draft-mishra-bess-ipv4nlri-ipv6nh-use-cases Revision: 03 Title: IPv4 NLRI with IPv6 Next Hop Use Cases Document date: 2020-08-21 Group: Individual Submission Pages: 15 URL: https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_internet-2Ddrafts_draft-2Dmishra-2Dbess-2Dipv4nlri-2Dipv6nh-2Duse-2Dcases-2D03.txt&d=DwICaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=DnUkF34wu4mqq0UY8nn2rxBBO7qOW_D-RfNVLML28ZU&m=aWje99Rrn3WKT4Qc9NcmmSd_s9vit3Ti3o0HFP1F2dg&s=D-6ItcXmkYQaLt8aM9I3dN1ZBk_7dl9q0bQ9JNTHbnA&e= Status: https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dmishra-2Dbess-2Dipv4nlri-2Dipv6nh-2Duse-2Dcases_&d=DwICaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=DnUkF34wu4mqq0UY8nn2rxBBO7qOW_D-RfNVLML28ZU&m=aWje99Rrn3WKT4Qc9NcmmSd_s9vit3Ti3o0HFP1F2dg&s=uQd-jOaYTNKWI0p2SXx-xlhWUblHOB7rnM55aFASJ3A&e= Htmlized: https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dmishra-2Dbess-2Dipv4nlri-2Dipv6nh-2Duse-2Dcases-2D03&d=DwICaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=DnUkF34wu4mqq0UY8nn2rxBBO7qOW_D-RfNVLML28ZU&m=aWje99Rrn3WKT4Qc9NcmmSd_s9vit3Ti3o0HFP1F2dg&s=B5R9D_ZCHfSZQKNX4e2wEfwAsXKSyv30XB7VB2udujY&e= Htmlized: https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_html_draft-2Dmishra-2Dbess-2Dipv4nlri-2Dipv6nh-2Duse-2Dcases&d=DwICaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=DnUkF34wu4mqq0UY8nn2rxBBO7qOW_D-RfNVLML28ZU&m=aWje99Rrn3WKT4Qc9NcmmSd_s9vit3Ti3o0HFP1F2dg&s=Ttp_BIk0m896tAt7NwN1xHhPiWrPUuTKU1H6K97eDVk&e= Diff: https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_rfcdiff-3Furl2-3Ddraft-2Dmishra-2Dbess-2Dipv4nlri-2Dipv6nh-2Duse-2Dcases-2D03&d=DwICaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=DnUkF34wu4mqq0UY8nn2rxBBO7qOW_D-RfNVLML28ZU&m=aWje99Rrn3WKT4Qc9NcmmSd_s9vit3Ti3o0HFP1F2dg&s=BNK1a24K2lqmUnFEyUtD_o-h_vtXlhnmD7ptDHVN1x8&e= Abstract: As Enterprises and Service Providers upgrade their brown field or green field MPLS/SR core to an IPv6 transport such as MPLS LDPv6, SR- MPLSv6 or SRv6, Multiprotocol BGP (MP-BGP)now plays an important role in the transition of the core from IPv4 to IPv6 being able to continue to support legacy IPv4, VPN-IPv4, and Multicast VPN IPv4 customers. Multiprotocol BGP (MP-BGP) specifies that the set of usable next-hop address families is determined by the Address Family Identifier (AFI) and the Subsequent Address Family Identifier (SAFI). Historically the AFI/SAFI definitions for the IPv4 address family only have provisions for advertising a Next Hop address that belongs to the IPv4 protocol when advertising IPv4 or VPN-IPv4 Network Layer Reachability Information (NLRI). [RFC5549] specifies the extensions necessary to allow advertising IPv4 NLRI or VPN-IPv4 NLRI with a Next Hop address that belongs to the IPv6 protocol. This comprises an extension of the AFI/SAFI definitions to allow the address of the Next Hop for IPv4 NLRI or VPN-IPv4 NLRI to also belong to the IPv6 Protocol. [RFC5549] defines the encoding of the Next Hop to determine which of the protocols the address actually belongs to, and a new BGP Capability allowing MP-BGP Peers to dynamically discover whether they can exchange IPv4 NLRI and VPN-IPv4 NLRI with an IPv6 Next Hop. With this new MP-BGP capability exchange allows the BGP peering session to act as a pure transport to allow the session to carry Address Family Identifier (AFI) and the Subsequent Address Family Identifier (SAFI) for both IPv4 and IPv6. This document describes the critical use case and OPEX savings of being able to leverage the MP-BGP capability exchange usage as a pure transport allowing both IPv4 and IPv6 to be carried over the same BGP TCP session. By doing so, allows for the elimination of Dual Stacking on the PE-CE connections making the peering IPv6-ONLY to now carry both IPv4 and IPv6 Network Layer Reachability Information (NLRI). This document also provides a possible solution for IXPs (Internet Exchange points) that are facing IPv4 address depletion at these peering points to use BGP-MP capability exchange defined in [RFC5549] to carry IPv4 (Network Layer Reachability Information) NLRI in an IPv6 next hop using the [RFC5565] softwire mesh framework. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect & SME* *Data Center Planning | Common Core | Development & Engineering Lab ServicesGlobal Technology Services | ITNUC* *O 240 970-6287M 301 502-134713101 Columbia Pike Rm 304-D*Silver Spring, MD 20904 *IETF & ISOC Member since 2015* https://www.ietf.org/ https://www.internetsociety.org/ -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *M 301 502-134713101 Columbia Pike *Silver Spring, MD
_______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess