Re: [bess] I-D Action: draft-ietf-bess-mvpn-expl-track-12.txt

Xiejingrong <> Tue, 16 October 2018 03:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1C52F128D0C for <>; Mon, 15 Oct 2018 20:53:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id QGV-clRREDHW for <>; Mon, 15 Oct 2018 20:53:41 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2804A127333 for <>; Mon, 15 Oct 2018 20:53:40 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id 8BD5A889FFD53 for <>; Tue, 16 Oct 2018 11:53:29 +0800 (CST)
Received: from ([fe80::40a8:f0d:c0f3:2ca5]) by ([]) with mapi id 14.03.0399.000; Tue, 16 Oct 2018 11:53:21 +0800
From: Xiejingrong <>
To: "" <>
Thread-Topic: [bess] I-D Action: draft-ietf-bess-mvpn-expl-track-12.txt
Thread-Index: AQHUX/CrV9At05CSckWnfUAgcUxwyqUhRc6w
Date: Tue, 16 Oct 2018 03:53:20 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [bess] I-D Action: draft-ietf-bess-mvpn-expl-track-12.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 16 Oct 2018 03:53:44 -0000


Had the IANA ack'ed the request of adding the value 2 (Name LIR-PF) ?

I have not seen it in


-----Original Message-----
From: BESS [] On Behalf Of
Sent: Wednesday, October 10, 2018 12:53 AM
Subject: [bess] I-D Action: draft-ietf-bess-mvpn-expl-track-12.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the BGP Enabled ServiceS WG 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-12.txt
	Pages           : 18
	Date            : 2018-10-09

   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 RFCs
   6514, 6625, and 7524.

The IETF datatracker status page for this draft is:

There are also htmlized versions available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at

Internet-Drafts are also available by anonymous FTP at:

BESS mailing list