Use of PIM Address List Hello across address families
draft-ietf-pim-ipv4-prefix-over-ipv6-nh-02

Document Type Active Internet-Draft (pim WG)
Last updated 2018-05-01
Replaces draft-pim-with-ipv4-prefix-over-ipv6-nh
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html 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)
Network Working Group                                           A. Gupta
Internet-Draft                                              Avi Networks
Intended status: Informational                                 S. Venaas
Expires: November 2, 2018                                  Cisco Systems
                                                             May 1, 2018

         Use of PIM Address List Hello across address families
             draft-ietf-pim-ipv4-prefix-over-ipv6-nh-02.txt

Abstract

   In the PIM Sparse Mode standard there is an Address List Hello option
   used to list secondary addresses of an interface.  Usually the
   addresses would be of the same address family as the primary address.
   In this document we provide a use case for listing secondary
   addresses that are from a different family.  In particular, Multi-
   Protocol BGP (MP-BGP) has support for distributing next-hop
   information for multiple address families using one AFI/SAFI Network
   Layer Reachability Information (NLRI).  When using this combined with
   PIM, the Address List Hello option can be used to determine which PIM
   neighbor to use as RPF neighbor.

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 November 2, 2018.

Copyright Notice

   Copyright (c) 2018 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

Gupta & Venaas          Expires November 2, 2018                [Page 1]
Internet-Draft  PIM Address List across address families        May 2018

   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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Solution  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     5.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The PIM Sparse Mode standard [RFC7761] defines an Address List Hello
   option used to list secondary addresses of an interface.  It
   specifies that the addresses listed SHOULD be of the same address
   family as the primary address.  It was not anticipated that it could
   be useful to list addresses of a different address family.  This
   document describes a use-case for listing different address families.

   While use of MP-BGP along with [RFC5549] enables one routing protocol
   session to exchange next-hop info for both IPv4 and IPv6 prefixes,
   forwarding plane needs additional procedures to enable forwarding in
   data-plane.  For example, when a IPv4 prefix is learnt over IPv6
   next-hop, forwarding plane resolves the MAC-Address (L2-Adjacency)
   for IPv6 next-hop and uses it as destination-mac while doing inter-
   subnet forwarding.  While it's simple to find the required
   information for unicast forwarding, multicast forwarding in same
Show full document text