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

Document Type Active Internet-Draft (bess WG)
Last updated 2020-01-17
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
BESS Working Group                                          S. Litkowski
Internet-Draft                                                S. Agrawal
Intended status: Standards Track                        K. Ananthamurthy
Expires: July 20, 2020                                             Cisco
                                                                K. Patel
                                                                  Arrcus
                                                        January 17, 2020

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

Abstract

   Multiprotocol BGP (MP-BGP) [RFC4760] 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.

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

   This Internet-Draft will expire on July 20, 2020.

Litkowski, et al.         Expires July 20, 2020                 [Page 1]
Internet-Draft               rfc5549revision                January 2020

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.  Requirements Language . . . . . . . . . . . . . . . . . . . .   4
   3.  Extension of AFI/SAFI Definitions for the IPv4 Address Family   4
   4.  Use of BGP Capability Advertisement . . . . . . . . . . . . .   6
   5.  Operations  . . . . . . . . . . . . . . . . . . . . . . . . .   8
   6.  Usage Examples  . . . . . . . . . . . . . . . . . . . . . . .   8
     6.1.  IPv4 over IPv6 Core . . . . . . . . . . . . . . . . . . .   8
     6.2.  IPv4 VPN unicast over IPv6 Core . . . . . . . . . . . . .   9
     6.3.  IPv4 VPN multicast over IPv6 Core . . . . . . . . . . . .   9
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  10
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     10.2.  Informative References . . . . . . . . . . . . . . . . .  11
   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
   different address family than the Network Layer Reachability
Show full document text