Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop
draft-ietf-bess-rfc5549revision-06

Document Type Active Internet-Draft (bess WG)
Last updated 2020-09-15 (latest revision 2020-09-01)
Replaces draft-litkowski-bess-rfc5549revision
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Matthew Bocci
Shepherd write-up Show (last changed 2020-07-07)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Martin Vigoureux
Send notices to Matthew Bocci <matthew.bocci@nokia.com>
IANA IANA review state Version Changed - Review Needed
IANA action state Waiting on Authors
RFC Editor RFC Editor state RFC-EDITOR
Details
BESS Working Group                                          S. Litkowski
Internet-Draft                                                S. Agrawal
Obsoletes: RFC5549 (if approved)                        K. Ananthamurthy
Intended status: Standards Track                                   Cisco
Expires: March 5, 2021                                          K. Patel
                                                                  Arrcus
                                                       September 1, 2020

  Advertising IPv4 Network Layer Reachability Information with an IPv6
                                Next Hop
                   draft-ietf-bess-rfc5549revision-06

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 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 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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Litkowski, et al.         Expires March 5, 2021                 [Page 1]
Internet-Draft               rfc5549revision              September 2020

   This Internet-Draft will expire on March 5, 2021.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Changes compared to RFC5549 . . . . . . . . . . . . . . . . .   4
   3.  Requirements Language . . . . . . . . . . . . . . . . . . . .   5
   4.  Extension of AFI/SAFI Definitions for the IPv4 Address Family   5
   5.  Use of BGP Capability Advertisement . . . . . . . . . . . . .   6
   6.  Operations  . . . . . . . . . . . . . . . . . . . . . . . . .   8
   7.  Usage Examples  . . . . . . . . . . . . . . . . . . . . . . .   9
     7.1.  IPv4 over IPv6 Core . . . . . . . . . . . . . . . . . . .   9
     7.2.  IPv4 VPN unicast over IPv6 Core . . . . . . . . . . . . .   9
     7.3.  IPv4 VPN multicast over IPv6 Core . . . . . . . . . . . .  10
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  11
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     11.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   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).  A number of
   existing AFI/SAFIs allow the Next Hop address to belong to a
Show full document text