Re: [mpls] Question on draft-ietf-mpls-rfc4379bis-09.txt

"Carlos Pignataro (cpignata)" <> Thu, 01 December 2016 23:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3F3E81299BC for <>; Thu, 1 Dec 2016 15:06:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -17.417
X-Spam-Status: No, score=-17.417 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.896, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id deRCJYJCIGu6 for <>; Thu, 1 Dec 2016 15:06:53 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1AAD012007C for <>; Thu, 1 Dec 2016 15:06:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=19684; q=dns/txt; s=iport; t=1480633612; x=1481843212; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=xbgxtRMMMthLd4Y9DdxYa0mWAce6BTG1R7SVOK18Nv8=; b=S5emxX/g8uvzql+QvQjmBV7VynnGhw9YBKgjRGZq+h83CLRseWO7a0SJ wghn0y+Imno3zFYKQO0jHcch78nXuWEe7akOZHHWir5NZsePMHReuGPVY s/ffztpmvKHoeFS6qeC9XJAG0Z6TwINzSw+8w0pruaoY/VAVCM772bGuK o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.33,284,1477958400"; d="scan'208,217";a="181269230"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-SHA; 01 Dec 2016 23:06:51 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id uB1N6pDN004438 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 1 Dec 2016 23:06:51 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 1 Dec 2016 18:06:51 -0500
Received: from ([]) by ([]) with mapi id 15.00.1210.000; Thu, 1 Dec 2016 18:06:50 -0500
From: "Carlos Pignataro (cpignata)" <>
To: "Aissaoui, Mustapha (Nokia - CA)" <>
Thread-Topic: [mpls] Question on draft-ietf-mpls-rfc4379bis-09.txt
Thread-Index: AdJGnV7er03UlZ6JRUi/8+DkE/AdkADC2LQAACFvgpwAAPDD1ABBo80AAEYr8gA=
Date: Thu, 01 Dec 2016 23:06:50 +0000
Message-ID: <>
References: <> <> <021301d24a2d$fea3d820$> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_97E59960004C4887BD174052755FFB70ciscocom_"
MIME-Version: 1.0
Archived-At: <>
Cc: "" <>
Subject: Re: [mpls] Question on draft-ietf-mpls-rfc4379bis-09.txt
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-Protocol Label Switching WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 01 Dec 2016 23:06:56 -0000

Mustapha, Tom,

The new revision should address all these issues, and fix a couple additional editorials.

Could you please review?

Name: draft-ietf-mpls-spring-lsp-ping
Revision: 02
Title: Label Switched Path (LSP) Ping/Trace for Segment Routing Networks Using MPLS Dataplane
Document date: 2016-12-01
Group: mpls
Pages: 18


Carlos Pignataro,<>

“Sometimes I use big words that I do not fully understand, to make myself sound more photosynthesis."

On Nov 30, 2016, at 8:37 AM, Aissaoui, Mustapha (Nokia - CA) <<>> wrote:

Tom and Carlos,
Thanks. It seems we are in sync.


-----Original Message-----
From: Carlos Pignataro (cpignata) []
Sent: Tuesday, November 29, 2016 6:18 AM
To: t.petch <<>>
Cc: Aissaoui, Mustapha (Nokia - CA) <<>>;<>
Subject: Re: [mpls] Question on draft-ietf-mpls-rfc4379bis-09.txt

Hi Tom,

Indeed. My reply implied (although it didn't spell out) that this is specified for the
DDMAP (and not the deprecated DSMAP). That's why the protocol field definition
happens in a sub-TLV.

Let us make the changes in the doc and then we can discuss over something more


Thumb typed by Carlos Pignataro.
Excuze typofraphicak errows

On Nov 29, 2016, at 05:51, t.petch <<>> wrote:


One other point I raised was that spring-lsp refers throughout to
Downstream Mapping TLV and not to Downstream Detailed Mapping TLV

Mustapha assumed that these should all be changed.  I am unsure about
this - is spring-lsp expected to work with Downstream Mapping TLV as
specified in RFC4379?  If not, then I think that spring-lsp should
spell that out.

Either way, the wording changes to spring-lsp need some thought since
Downstream Mapping TLV does not have subTLVs and Downstream Detailed
Mapping TLV does.

Tom Petch

----- Original Message -----
From: "Carlos Pignataro (cpignata)" <<>>
To: "Aissaoui, Mustapha (Nokia - CA)" <<>>
Cc: <<>>
Sent: Monday, November 28, 2016 1:53 PM

Thank you Mustapha for catching these, and Tom and Mach for the

There are three changes needed to draft-ietf-mpls-spring-lsp-ping
based based on this discussion:

1.  In Section 10.1, update the references to {Section 4.1, Section
4.2, Section 4.1} -> {Section 5.1, Section 5.2, Section 5.1}
2.  Create a Section 10.2, create a registry for the "Protocol field
of the Label Stack Sub-TLV of the Downstream Detailed Mapping TLV",
registering values 0-4, and asking for TBD5 and TBD6. If this happens
in this draft instead of 4379bis, I believe it is OK.
3.  Create a Section 10.3, requesting error code TBD.


Carlos Pignataro,<><>

"Sometimes I use big words that I do not fully understand, to make
myself sound more photosynthesis."

On Nov 24, 2016, at 5:05 PM, Aissaoui, Mustapha (Nokia - CA)

Dear all,
Can someone point me to where are held the IANA allocation for the
values in the 'protocol' field of the Label Stack Sub-TLV of the
Downstream Detailed Mapping TLV?

There is draft-ietf-mpls-spring-lsp-ping-01 which is adding IS-IS and
OSPF as new values into this field but I fail to find where these are