Use of Per-Flow Explicit Tracking and IP Lookup for Segmented MVPN
draft-xie-bess-mvpn-segmented-updates-00

Document Type Active Internet-Draft (individual)
Last updated 2019-01-08
Replaces draft-xie-bier-mvpn-segmented
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                                             J. Xie
Internet-Draft                                       Huawei Technologies
Intended status: Standards Track                                Z. Zhang
Expires: July 12, 2019                                  Juniper Networks
                                                                 L. Geng
                                                            China Mobile
                                                              M. McBride
                                                                  G. Yan
                                                                  Huawei
                                                         January 8, 2019

   Use of Per-Flow Explicit Tracking and IP Lookup for Segmented MVPN
                draft-xie-bess-mvpn-segmented-updates-00

Abstract

   This document specifies an alternative of the control plane and data
   plane procedures that allow segmented MVPN using the more efficient
   LIR-pF explicit-tracking when BIER is used as the upstream or
   downstream or both segments.  It requires a segmentation point BFR
   doing an IP header lookup, which is common for the forwarding
   procedure on BFER, or the forwarding procedure on ABR with local VPN
   CEs connected.  This document updates [I-D.ietf-bier-mvpn].

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

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 12, 2019.

Xie, et al.               Expires July 12, 2019                 [Page 1]
Internet-Draft       Segmented MVPN Using IP Lookup         January 2019

Copyright Notice

   Copyright (c) 2019 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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Problem Statement and Considerations  . . . . . . . . . . . .   4
     3.1.  Problem Statement . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Considerations  . . . . . . . . . . . . . . . . . . . . .   5
   4.  Upstream BIER and Downstream BIER (BIER-BIER) . . . . . . . .   6
     4.1.  Explicit Tracking using LIR-pF  . . . . . . . . . . . . .   6
     4.2.  Forwarding using IP lookup on Segmentation Point  . . . .   8
   5.  Upstream P2MP and Downstream BIER (P2MP-BIER) . . . . . . . .   9
     5.1.  Explicit Tracking using LIR-pF  . . . . . . . . . . . . .   9
     5.2.  Forwarding using IP lookup on Segmentation Point  . . . .  10
   6.  Upstream BIER and Downstream P2MP (BIER-P2MP) . . . . . . . .  10
     6.1.  Explicit Tracking using LIR-pF  . . . . . . . . . . . . .  10
     6.2.  Forwarding on Segmentation Point  . . . . . . . . . . . .  11
   7.  Summary and Recommendations . . . . . . . . . . . . . . . . .  12
   8.  Appendix A - Comparison of Solutions  . . . . . . . . . . . .  13
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  15
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  16
     12.2.  Informative References . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   When using BIER to transport an MVPN data packet through a BIER
   domain, an ingress PE functions as a BFIR (see [RFC8279]).  The BFIR
Show full document text