Last Call: <draft-ietf-bess-rfc5549revision-04.txt> (Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Tue, 07 July 2020 18:35 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 526C93A142A; Tue, 7 Jul 2020 11:35:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-bess-rfc5549revision-04.txt> (Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 7.7.0
Auto-Submitted: auto-generated
Precedence: bulk
CC: Matthew Bocci <matthew.bocci@nokia.com>, martin.vigoureux@nokia.com, matthew.bocci@nokia.com, bess-chairs@ietf.org, draft-ietf-bess-rfc5549revision@ietf.org, bess@ietf.org
Reply-To: last-call@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <159414694272.4451.2372906265801739292@ietfa.amsl.com>
Date: Tue, 07 Jul 2020 11:35:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/FgbzTqdghiAif5aep2FCXl72jKU>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jul 2020 18:35:49 -0000

The IESG has received a request from the BGP Enabled ServiceS WG (bess) to
consider the following document: - 'Advertising IPv4 Network Layer
Reachability Information with an IPv6
   Next Hop'
  <draft-ietf-bess-rfc5549revision-04.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2020-07-21. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   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).  The current
   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 Network Layer Reachability Information (NLRI)
   or VPN-IPv4 NLRI.  This document 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, 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. This
   document obsoletes RFC5549.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-bess-rfc5549revision/



No IPR declarations have been submitted directly on this I-D.