Re: [mpls] short wgap confirmation poll on draft-sitaraman-mpls-rsvp-shared-labels-02

"Dongjie (Jimmy)" <> Wed, 13 December 2017 06:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 19A90126DFB; Tue, 12 Dec 2017 22:50:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id npXN63-PB2jl; Tue, 12 Dec 2017 22:50:05 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0AE38126CD6; Tue, 12 Dec 2017 22:50:05 -0800 (PST)
Received: from (unknown []) by Forcepoint Email with ESMTP id 5D81C4290E28D; Wed, 13 Dec 2017 06:50:01 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.361.1; Wed, 13 Dec 2017 06:50:01 +0000
Received: from ([]) by ([]) with mapi id 14.03.0361.001; Wed, 13 Dec 2017 14:49:56 +0800
From: "Dongjie (Jimmy)" <>
To: Vishnu Pavan Beeram <>, Loa Andersson <>
CC: "" <>, "" <>, "" <>
Thread-Topic: [mpls] short wgap confirmation poll on draft-sitaraman-mpls-rsvp-shared-labels-02
Thread-Index: AQHTcLprr5UOXl0p50m9KamgnDbF/KM6LumAgAal6UA=
Date: Wed, 13 Dec 2017 06:49:56 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_76CD132C3ADEF848BD84D028D243C927981D7FD8NKGEML515MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [mpls] short wgap confirmation poll on draft-sitaraman-mpls-rsvp-shared-labels-02
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-Protocol Label Switching WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 13 Dec 2017 06:50:08 -0000

Hi Pavan,

I have reviewed the changes in the updated version, and think my previous comments have been solved. Thanks.

Best regards,

From: mpls [] On Behalf Of Vishnu Pavan Beeram
Sent: Saturday, December 09, 2017 4:54 PM
To: Loa Andersson <>
Subject: Re: [mpls] short wgap confirmation poll on draft-sitaraman-mpls-rsvp-shared-labels-02

Folks, Hi!

As Loa mentioned, we published a new version (-03) to address relevant comments/questions that were raised during the RT-review process and the WG adoption poll. Please do go through the diffs ( and let us know if there are any concerns with these changes.

The following is a high-level summary of the changes introduced in this new version:

(1) Terminology:
There were some concerns raised regarding some of the terminology used to aid the narrative in the -02 version. Based on the feedback received, we replaced the terms ‘Pop label’, ‘Pop and forward data plane’ and ‘RSVP-TE pop and forward tunnel” with ‘TE link label’, ‘Shared MPLS forwarding plane’ and ‘Segment Routed RSVP-TE tunnel’ respectively. We got rid of the term ‘swap label’ altogether. We simply use ‘regular label’ in places where there is a need to refer to the traditional label.

(2) Does this draft update MPLS Architecture?
There was a question raised on whether the functionality discussed in this draft updates the base MPLS architecture (RFC3031). The answer is “No”. We added the following sentence to stress this point:

   This forwarding plane behavior fits in the MPLS architecture
   [RFC3031] and is same as that exhibited by Segment Routing (SR)
   [I-D.ietf-spring-segment-routing] when using an MPLS forwarding plane
   and a series of adjacency segments.

(3) Does this apply to P2MP Tunnels?
There was a question raised on the applicability of this functionality to RSVP-TE P2MP tunnels. The current focus is only on P2P tunnels. We added the following statement in the draft to make this obvious:

   The signaling procedures and extensions discussed in this document do
   not apply to Point to Multipoint (P2MP) RSVP-TE Tunnels.

(4) How does the notion of ’TE link labels’ impact implementations that maintain per label bandwidth accounting?
We added the following statement in the draft to address this:

   Implementations that maintain per label bandwidth accounting at each
   hop must aggregate the reservations made for all the LSPs using the
   shared TE link label.

(5) Is there any impact on the behavior of PHP LSRs?
There is no impact. We added the following statement:

   There is no change in the behavior of a
   penultimate hop popping (PHP) LSR [RFC3031].

-Pavan (on behalf of the authors)

On Sat, Dec 9, 2017 at 1:52 AM, Loa Andersson <<>> wrote:
Working Group,

draft-sitaraman-mpls-rsvp-shared-labels-02 did go through a poll
to see if we had consensus to adopt it as as a MPLS working group

The outcome of the wgap was that there were changes that we wanted¨to do before adoption of the document

This is to start a short (one week) poll to see if the comments from the
earlier wgap has been correctly addressed in draft-sitaraman-mpls-rsvp-shared-labels-03.

Due to the nature of the poll silence will be considered to be consent,
however it would be appreciated if those of you that made the comments
we are now addressing can confirm that tou are comfortable with how
they have been addressed.

Please send your comments (support/not support) to the mpls working
group mailing list (<>). Please give a technical
motivation for your support/not support, especially if you think that
the document should not be adopted as a working group document.

There are three IPR disclosures (though one disclosure seems to be an
update) against this document.

All the authors have stated on the MPLS wg mailing list that they are
unaware of any other IPRs that those that has been disclosed

The working group adoption poll ends Decembet 19, 2017.

mpls wg co-chair

Loa Andersson                        email:<>
Senior MPLS Expert
Huawei Technologies (consultant)     phone: +46 739 81 21 64

mpls mailing list<>