[bess] I-D Action: draft-ietf-bess-mvpn-expl-track-00.txt
internet-drafts@ietf.org Mon, 20 June 2016 13:43 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: bess@ietf.org
Delivered-To: bess@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 79C8912D5C4; Mon, 20 Jun 2016 06:43:14 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.23.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160620134314.30146.84030.idtracker@ietfa.amsl.com>
Date: Mon, 20 Jun 2016 06:43:14 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/Lmx7AM_c09DZdndQz8VG-FX0zNc>
Cc: bess@ietf.org
Subject: [bess] I-D Action: draft-ietf-bess-mvpn-expl-track-00.txt
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.17
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2016 13:43:14 -0000
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the BGP Enabled ServiceS of the IETF. Title : Explicit Tracking with Wild Card Routes in Multicast VPN Authors : Andrew Dolganow Jayant Kotalwar Eric C. Rosen Zhaohui Zhang Filename : draft-ietf-bess-mvpn-expl-track-00.txt Pages : 15 Date : 2016-06-20 Abstract: The MVPN specifications provide procedures to allow a multicast 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 flows. However, the specifications are not completely clear about how the explicit tracking procedures work in certain scenarios. This document provides the necessary clarifications. It also specifies a new, optimized explicit tracking procedure. This new procedure allows an ingress node, by sending a single message, to request explicit tracking of each of a set of flows, where the set of flows is specified using a wildcard mechanism. This document updates RFC6625. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-bess-mvpn-expl-track/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-bess-mvpn-expl-track-00 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/
- [bess] I-D Action: draft-ietf-bess-mvpn-expl-trac… internet-drafts