PIM Encoding and Procedures for Unicast IPv4 prefixes with IPV6 next-hop
draft-pim-with-ipv4-prefix-over-ipv6-nh-00

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           A. Gupta
Internet-Draft                                                 S. Venaas
Intended status: Experimental                              Cisco Systems
Expires: September 14, 2017                               March 13, 2017

PIM Encoding and Procedures for Unicast IPv4 prefixes with IPV6 next-hop
             draft-pim-with-ipv4-prefix-over-ipv6-nh-00.txt

Abstract

   Multiprotocol BGP (MP-BGP) has support for distributing next-hop
   information for multiple address families using one AFI/SAFI Network
   Layer Reachability Information (NLRI).  [RFC5549] specifies the
   extensions necessary to allow advertising IPv4 NLRI or VPN-IPv4 NLRI
   with a Next Hop address that belongs to the IPv6 protocol.  While the
   next-hop info is learnt via MP-BGP, certain procedures are needed to
   enable traffic forwarding.  This document describes PIM extentions
   and the use-cases for multicast forwarding in various scenarios.

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 http://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 September 14, 2017.

Copyright Notice

   Copyright (c) 2017 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
   (http://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

Gupta & Venaas         Expires September 14, 2017               [Page 1]
Internet-Draft   PIM with Unicast IPv4 nlri with IPV6 nh      March 2017

   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
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Solution  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Networks with both PIMv4 and PIMv6 sessions . . . . . . .   3
     2.2.  Networks with Either PIMv4 or PIMv6 session . . . . . . .   4
       2.2.1.  Using secondary neighbor list option  . . . . . . . .   4
       2.2.2.  Using MAC-Address option  . . . . . . . . . . . . . .   4
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Figure 1: Example Topology

             +-------------+                   +-------------+
             |             |                   |             |
             | Router1   1::1/64          1::2/64 Router2    |
10.1.1.1/32--+             +--------Intf1------|             +-+PIM receiver
             |         1.1.1.1/24         1.1.1.2/24         |
             |             +                   +             |
             |             |                   |             |
Show full document text