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

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Tue, 29 November 2016 11:18 UTC

Return-Path: <cpignata@cisco.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61FE11296BC for <mpls@ietfa.amsl.com>; Tue, 29 Nov 2016 03:18:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.019
X-Spam-Level:
X-Spam-Status: No, score=-16.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YWUH_-nQFULY for <mpls@ietfa.amsl.com>; Tue, 29 Nov 2016 03:18:09 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD5D61296BE for <mpls@ietf.org>; Tue, 29 Nov 2016 03:18:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2747; q=dns/txt; s=iport; t=1480418289; x=1481627889; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=+5VqkzjaE8bMDwu0qyl52LRHctcz62w6onCAlOUre/I=; b=l8+A63cjUunFTOqrGhdExF7NV5HYikQs42lOHvXFSG5AloPWtDQj6LZQ M0mwX5ReIn5blWrWGl9RvvixwQ2Hfm1gJWZuwGHjbVx1HAOOcrxByZBbL eUQrIRO0PCct3iOz2kSM0NyaviwAATGf/joUdWhKdF0/w6+LexsquULE1 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AkAQCpYz1Y/4sNJK1dGQEBAQEBAQEBAQEBBwEBAQEBgzgBAQEBAR+BW41DlyGUdYIGhiICgWs/FAECAQEBAQEBAWIohGgBAQEDASdSBQcEAgEIFQECJwcyFBEBAQQOBYhlCK5WPYtGAQEBAQEBAQEBAQEBAQEBAQEBAQEBHIY+gX2CXoRJgzGCMAEEiEyMH4VpAZEFgXKOQIdXHIV+hAsBHjeBFC8BAYUgcogNAQEB
X-IronPort-AV: E=Sophos;i="5.31,568,1473120000"; d="scan'208";a="353523263"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 Nov 2016 11:18:08 +0000
Received: from XCH-RTP-019.cisco.com (xch-rtp-019.cisco.com [64.101.220.159]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id uATBI8Is016620 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 29 Nov 2016 11:18:08 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-019.cisco.com (64.101.220.159) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 29 Nov 2016 06:18:07 -0500
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1210.000; Tue, 29 Nov 2016 06:18:07 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: "t.petch" <ietfc@btconnect.com>
Thread-Topic: [mpls] Question on draft-ietf-mpls-rfc4379bis-09.txt
Thread-Index: AdJGnV7er03UlZ6JRUi/8+DkE/AdkADC2LQAACFvgpwAAPDD1A==
Date: Tue, 29 Nov 2016 11:18:07 +0000
Message-ID: <29FC922A-38D5-4D21-8D07-07A5C956D6A2@cisco.com>
References: <4A79394211F1AF4EB57D998426C9340DD4AEC84F@US70UWXCHMBA01.zam.alcatel-lucent.com> <65916DBD-057B-4030-8028-35209556BB8D@cisco.com>, <021301d24a2d$fea3d820$4001a8c0@gateway.2wire.net>
In-Reply-To: <021301d24a2d$fea3d820$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="windows-1253"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/cKPiuceJ9wV1RU1lVfv72ehafSk>
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Question on draft-ietf-mpls-rfc4379bis-09.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Nov 2016 11:18:12 -0000

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 concrete. 

Thanks!

Thumb typed by Carlos Pignataro.
Excuze typofraphicak errows

> On Nov 29, 2016, at 05:51, t.petch <ietfc@btconnect.com> wrote:
> 
> Carlos
> 
> 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)" <cpignata@cisco.com>
> To: "Aissaoui, Mustapha (Nokia - CA)" <mustapha.aissaoui@nokia.com>
> Cc: <mpls@ietf.org>
> Sent: Monday, November 28, 2016 1:53 PM
> 
>> Thank you Mustapha for catching these, and Tom and Mach for the
> follow-ups.
>> 
>> 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.
>> 
>> Thanks!
>> 
>> ―
>> Carlos Pignataro, carlos@cisco.com<mailto:carlos@cisco.com>
>> 
>> “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)
> <mustapha.aissaoui@nokia.com<mailto:mustapha.aissaoui@nokia.com>> wrote:
>> 
>> 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
> maintained.
>> 
>> Regards,
>> Mustapha.
>