[bess] Fwd: [E] New Version Notification for draft-mishra-bess-deployment-guide-ipv4nlri-ipv6nh-04.txt
Gyan Mishra <hayabusagsm@gmail.com> Tue, 27 April 2021 06:23 UTC
Return-Path: <hayabusagsm@gmail.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 462443A1116; Mon, 26 Apr 2021 23:23:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y5Hcd8XlE-rQ; Mon, 26 Apr 2021 23:23:03 -0700 (PDT)
Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C8623A1107; Mon, 26 Apr 2021 23:23:02 -0700 (PDT)
Received: by mail-pl1-x62e.google.com with SMTP id h20so30294063plr.4; Mon, 26 Apr 2021 23:23:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=NPPgDiVMIj7TPBfJqBY5JEjLYuGNI/m0VnZfz4UU4vo=; b=nc4W9l6C815nB7YiqkJLRw17kkuI4vS2qaexC7JpDOf1pCkqjiXWC9Fd0oYbzppj7O fXd4SnheCdjarUFh6/g3c4gtYQLoUbSnmTqJLvG1qOh628aPaADONbHlgs7V41yevE7P 6jAcKTlS6zcTovoKecCPUwR1v7HsXnq6wy97O8rui0xsLMX3iTP5bd4m4FOR0UquAPWG 6ehC0mnNhEcD3mq7mYN3eG6ePDLDUp75csehYYUsFe2Q2AS8VKuk9HbVpvB68GCBuFHI dAaCu23ZGOWyVVj1Sxbk/oRPY/zD6VJjTdQ2ZuxDqmyn6bfb8UjH26qjnszN9+JjWWEw 8YoA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=NPPgDiVMIj7TPBfJqBY5JEjLYuGNI/m0VnZfz4UU4vo=; b=aXS8SHzgDsKioqKOj2mlJ24KIUACVEqSj7k8CB+rw97P6i0Om88Ly9WbIdSblQF2FZ kqStC10cmzRmAs5EFZ+CbheY9HDHOzjaRpfZm2XfxxTvBxlmDEREHHzLVPZAwK8+aMOo pg2zyKpwdReoqNnXtZCV4LPtW5F3ysWdhYQGrktDLEUPAQBATwo2eKZ+uFGw2R/4zGat n6t9vTe4QE2qFKduKpzXA5xTW2rpTnGtff4ezKKB/9DZUH8e6kj4HZEK1nBvm9C9ULD9 Ym3wPikI4wQiXMQ4uYacdWT+YSr9TYdXkgjUV90dD2kNOCmNCfUQeTTbxPEB+fX5Rmg8 S/lw==
X-Gm-Message-State: AOAM5308xok5X0nktUoi4P+yhdSycKIeVgzurzYDUFPSN7zljYkLe/lC gCVePutyETSii7FQ9nMffIp0Q/2cKZdEco7ruyx1YZhQhtpO+Q==
X-Google-Smtp-Source: ABdhPJzxKmsVT8yI1CrBwbUul/VP7Y9lYAcZ9Lmv09Zrm5l18vsrH2d9BlMOiNzWjzqn9F/WIBOeNxTW5Phd9b9Dj64=
X-Received: by 2002:a17:90a:2ac8:: with SMTP id i8mr24340297pjg.112.1619504579941; Mon, 26 Apr 2021 23:22:59 -0700 (PDT)
MIME-Version: 1.0
References: <161950416335.30905.12687913563025342843@ietfa.amsl.com> <CAJhXr999L154ky_4hwMa9d0toFTKeBuwkuFRSA9HcwsuE8X4oQ@mail.gmail.com>
In-Reply-To: <CAJhXr999L154ky_4hwMa9d0toFTKeBuwkuFRSA9HcwsuE8X4oQ@mail.gmail.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Tue, 27 Apr 2021 00:25:27 -0400
Message-ID: <CABNhwV0qc21DvPeHUw9+gVXBjWePwogUcGyHpm4dmL4CWw-hgA@mail.gmail.com>
To: BESS <bess@ietf.org>, draft-mishra-bess-deployment-guide-ipv4nlri-ipv6nh@ietf.org, "Mankamana Mishra (mankamis)" <mankamis@cisco.com>, Jeff Tantsura <jefftant.ietf@gmail.com>, Lili Wang <liliw@juniper.net>, Chenshuanglong <chenshuanglong@huawei.com>, "Simpson, Adam 1. (Nokia - US/Mountain View)" <adam.1.simpson@nokia.com>, Qing Yang <qyang@arista.com>, bess-chairs@ietf.org, "Bocci, Matthew (Nokia - GB)" <matthew.bocci@nokia.com>, "Stephane Litkowski (slitkows)" <slitkows@cisco.com>
Content-Type: multipart/alternative; boundary="00000000000033172e05c0ee4bc5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/4kVMje90HdAXgb2sgnGq0tCpntg>
X-Mailman-Approved-At: Tue, 27 Apr 2021 07:02:37 -0700
Subject: [bess] Fwd: [E] New Version Notification for draft-mishra-bess-deployment-guide-ipv4nlri-ipv6nh-04.txt
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Apr 2021 06:23:08 -0000
Dear BESS, I have updated the draft in revision 4 from comments during the WG Adoption poll. https://datatracker.ietf.org/doc/draft-mishra-bess-deployment-guide-ipv4nlri-ipv6nh/04/ Please review. Thank you Gyan ---------- Forwarded message --------- From: Mishra, Gyan S <gyan.s.mishra@verizon.com> Date: Tue, Apr 27, 2021 at 2:16 AM Subject: Fwd: [E] New Version Notification for draft-mishra-bess-deployment-guide-ipv4nlri-ipv6nh-04.txt To: Hayabusanew <hayabusagsm@gmail.com> ---------- Forwarded message --------- From: <internet-drafts@ietf.org> Date: Tue, Apr 27, 2021 at 2:16 AM Subject: [E] New Version Notification for draft-mishra-bess-deployment-guide-ipv4nlri-ipv6nh-04.txt To: Adam Simpson <adam.1.simpson@nokia.com>, Gyan Mishra < gyan.s.mishra@verizon.com>, Jeff Tantsura <jefftant.ietf@gmail.com>, Lili Wang <liliw@juniper.net>, Mankamana Mishra <mankamis@cisco.com>, Qing Yang < qyang@arista.com>, Shuanglong Chen <chenshuanglong@huawei.com> A new version of I-D, draft-mishra-bess-deployment-guide-ipv4nlri-ipv6nh-04.txt has been successfully submitted by Gyan Mishra and posted to the IETF repository. Name: draft-mishra-bess-deployment-guide-ipv4nlri-ipv6nh Revision: 04 Title: Deployment Guidelines for Edge Peering IPv4-NLRI with IPv6-NH Document date: 2021-04-26 Group: Individual Submission Pages: 21 URL: https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_archive_id_draft-2Dmishra-2Dbess-2Ddeployment-2Dguide-2Dipv4nlri-2Dipv6nh-2D04.txt&d=DwICaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=DnUkF34wu4mqq0UY8nn2rxBBO7qOW_D-RfNVLML28ZU&m=bGS9O5KFA11j2hd9og9I-N5eBH-Xsiq62Ubp3ky1Kak&s=GplhN6pbPFCDnWAFF0tqeVZjBX1nnF-nL6H8tLNAnsM&e= Status: https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dmishra-2Dbess-2Ddeployment-2Dguide-2Dipv4nlri-2Dipv6nh_&d=DwICaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=DnUkF34wu4mqq0UY8nn2rxBBO7qOW_D-RfNVLML28ZU&m=bGS9O5KFA11j2hd9og9I-N5eBH-Xsiq62Ubp3ky1Kak&s=D9OyhTMLCDz9ZQc1mYku6nCUBg3VEiBBB_vSdfKR3Iw&e= Htmlized: https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_html_draft-2Dmishra-2Dbess-2Ddeployment-2Dguide-2Dipv4nlri-2Dipv6nh&d=DwICaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=DnUkF34wu4mqq0UY8nn2rxBBO7qOW_D-RfNVLML28ZU&m=bGS9O5KFA11j2hd9og9I-N5eBH-Xsiq62Ubp3ky1Kak&s=FKPcDJ5syMhYkZ55Xrx3JbK7hHhzHGzEtOTNimEwwRk&e= Htmlized: https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dmishra-2Dbess-2Ddeployment-2Dguide-2Dipv4nlri-2Dipv6nh-2D04&d=DwICaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=DnUkF34wu4mqq0UY8nn2rxBBO7qOW_D-RfNVLML28ZU&m=bGS9O5KFA11j2hd9og9I-N5eBH-Xsiq62Ubp3ky1Kak&s=HfbldNQkr40Wa4XsQ_E9e4HD0mLu7Sidk35DT6yG5fM&e= Diff: https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_rfcdiff-3Furl2-3Ddraft-2Dmishra-2Dbess-2Ddeployment-2Dguide-2Dipv4nlri-2Dipv6nh-2D04&d=DwICaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=DnUkF34wu4mqq0UY8nn2rxBBO7qOW_D-RfNVLML28ZU&m=bGS9O5KFA11j2hd9og9I-N5eBH-Xsiq62Ubp3ky1Kak&s=Cho5i64yzsLbzTY75c5YIA7OGt1Vo03FteXhvw1XLJA&e= Abstract: As Enterprises and Service Providers upgrade their brown field or green field MPLS/SR core to an IPv6 transport, Multiprotocol BGP (MP- BGP)now plays an important role in the transition of their Provider (P) core network as well as Provider Edge (PE) Edge network from IPv4 to IPv6. Operators must be able to continue to support IPv4 customers when both the Core and Edge networks are IPv6-Only. This document details an important External BGP (eBGP) PE-CE Edge IPv6-Only peering design that leverages the MP-BGP capability exchange by using IPv6 peering as pure transport, allowing both IPv4 Network Layer Reachability Information (NLRI) and IPv6 Network Layer Reachability Information (NLRI)to be carried over the same (Border Gateway Protocol) BGP TCP session. The design change provides the same Dual Stacking functionality that exists today with separate IPv4 and IPv6 BGP sessions as we have today. With this design change from a control plane perspective a single IPv6 is required for both IPv4 and IPv6 routing updates and from a data plane forwarindg perspective an IPv6 address need only be configured on the PE and CE interface for both IPv4 and IPv6 packet forwarding. This document provides a much needed solution for Internet Exchange Point (IXP) that are facing IPv4 address depletion at large peering points. With this design, IXP can now deploy PE-CE IPv6-Only eBGP Edge peering design to eliminate IPv4 provisioning at the Edge. This core and edge IPv6-Only peering design paradigm change can apply to any eBGP peering, public internet or private, which can be either Core networks, Data Center networks, Access networks or can be any eBGP peering scenario. This document provides interoperability test cases for the IPv6-Only peering design as well as test results between five major vendors stakeholders in the routing and switching indusrty, Cisco, Juniper, Arista, Nokia and Huawei. With the test results provided for the IPv6-Only Edge peering design, the goal is that all other vendors around the world that have not been tested will begin to adopt and implement this new Best Current Practice for eBGP IPv6-Only Edge peering. As this issue with IXP IPv4 address depletion is a critical issue around the world, it is imperative for an immediate solution that can be implemented quickly. This Best Current Practice IPv6-only eBGP peering design specification will help proliferate IPv6-Only deployments at the eBGP Edge network peering points to starting immediately at a minimum with operators around the world using Cisco, Juniper, Arista, Nokia and Huawei. As other vendors start to implement this Best Current Practice, the IXP IPv4 address depletion gap will eventually be eliminated. 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 & Protocol Design Expert* *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 * *Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>* *M 301 502-1347*
- [bess] Fwd: [E] New Version Notification for draf… Gyan Mishra
- Re: [bess] [E] New Version Notification for draft… Bocci, Matthew (Nokia - GB)
- Re: [bess] [E] New Version Notification for draft… Simpson, Adam 1. (Nokia - US/Mountain View)