draft-ietf-bess-mvpn-expl-track-04.txt   draft-ietf-bess-mvpn-expl-track-05.txt 
BESS WG A. Dolganow BESS WG A. Dolganow
Internet-Draft J. Kotalwar Internet-Draft J. Kotalwar
Updates: 6625 (if approved) Nokia Updates: 6625 (if approved) Nokia
Intended status: Standards Track E. Rosen, Ed. Intended status: Standards Track E. Rosen, Ed.
Expires: July 20, 2018 Z. Zhang Expires: August 4, 2018 Z. Zhang
Juniper Networks, Inc. Juniper Networks, Inc.
January 16, 2018 January 31, 2018
Explicit Tracking with Wild Card Routes in Multicast VPN Explicit Tracking with Wild Card Routes in Multicast VPN
draft-ietf-bess-mvpn-expl-track-04 draft-ietf-bess-mvpn-expl-track-05
Abstract Abstract
The MVPN specifications provide procedures to allow a multicast The MVPN specifications provide procedures to allow a multicast
ingress node to invoke "explicit tracking" for a multicast flow or ingress node to invoke "explicit tracking" for a multicast flow or
set of flows, thus learning the egress nodes for that flow or set of set of flows, thus learning the egress nodes for that flow or set of
flows. However, the specifications are not completely clear about flows. However, the specifications are not completely clear about
how the explicit tracking procedures work in certain scenarios. This how the explicit tracking procedures work in certain scenarios. This
document provides the necessary clarifications. It also specifies a document provides the necessary clarifications. It also specifies a
new, optimized explicit tracking procedure. This new procedure new, optimized explicit tracking procedure. This new procedure
skipping to change at page 1, line 43 skipping to change at page 1, line 43
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 20, 2018. This Internet-Draft will expire on August 4, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 5, line 5 skipping to change at page 5, line 5
a number of "segmentation domains". In each segmentation domain, a number of "segmentation domains". In each segmentation domain,
a given P-tunnel has an ingress node and a set of egress nodes. a given P-tunnel has an ingress node and a set of egress nodes.
The explicit tracking procedures allow an ingress node of a The explicit tracking procedures allow an ingress node of a
particular segmentation domain to determine, for a particular flow particular segmentation domain to determine, for a particular flow
or set of flows, the egress nodes of that segmentation domain. or set of flows, the egress nodes of that segmentation domain.
This has given rise to two further problems: This has given rise to two further problems:
* The explicit tracking procedures do not allow an ingress node * The explicit tracking procedures do not allow an ingress node
to "see" past the boundaries of the segmentation domain. to "see" past the boundaries of the segmentation domain.
This document does not address this problem.
* The prior specifications do not make it very clear whether a * The prior specifications do not make it very clear whether a
segmented tunnel egress node, upon receiving an S-PMSI A-D segmented tunnel egress node, upon receiving an S-PMSI A-D
route whose PTA specifies "no tunnel information", is expected route whose PTA specifies "no tunnel information", is expected
to forward the S-PMSI A-D route, with the same PTA, to the next to forward the S-PMSI A-D route, with the same PTA, to the next
segmentation domain. segmentation domain.
These problems are resolved in Section 5.3. This problem is resolved in Section 5.3.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL", when and only when appearing in all capital letters, are "OPTIONAL", when and only when appearing in all capital letters, are
to be interpreted as described in [RFC2119]. to be interpreted as described in [RFC2119].
2. The Explicit Tracking Flags 2. The Explicit Tracking Flags
[RFC6514] defines one flag in the PTA, the "Leaf Info Required" (LIR) [RFC6514] defines one flag in the PTA, the "Leaf Info Required" (LIR)
flag, that is used for explicit tracking. flag, that is used for explicit tracking.
 End of changes. 6 change blocks. 
5 lines changed or deleted 7 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/