Hi, Following our fruitful discussion during BESS meeting yesterday, I have published a draft to revise RFC5549.
Brgds, Stephane -----Original Message----- From: [email protected] <[email protected]> Sent: mercredi 20 novembre 2019 13:39 To: Swadesh Agrawal <[email protected]>; Stephane Litkowski (slitkows) <[email protected]>; Krishna Muddenahally Ananthamurthy (kriswamy) <[email protected]>; Krishna Muddenahally Ananthamurthy (kriswamy) <[email protected]>; Keyur Patel <[email protected]> Subject: New Version Notification for draft-litkowski-bess-rfc5549revision-00.txt A new version of I-D, draft-litkowski-bess-rfc5549revision-00.txt has been successfully submitted by Stephane Litkowski and posted to the IETF repository. Name: draft-litkowski-bess-rfc5549revision Revision: 00 Title: Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop Document date: 2019-11-19 Group: Individual Submission Pages: 13 URL: https://www.ietf.org/internet-drafts/draft-litkowski-bess-rfc5549revision-00.txt Status: https://datatracker.ietf.org/doc/draft-litkowski-bess-rfc5549revision/ Htmlized: https://tools.ietf.org/html/draft-litkowski-bess-rfc5549revision-00 Htmlized: https://datatracker.ietf.org/doc/html/draft-litkowski-bess-rfc5549revision Abstract: Multiprotocol BGP (MP-BGP) [RFC4760] specifies that the set of network-layer protocols to which the address carried in the Next Hop field may belong 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 in order 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. 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 _______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
