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

"Aissaoui, Mustapha (Nokia - CA)" <mustapha.aissaoui@nokia.com> Mon, 28 November 2016 14:55 UTC

Return-Path: <mustapha.aissaoui@nokia.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 2701C129F19 for <mpls@ietfa.amsl.com>; Mon, 28 Nov 2016 06:55:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 8GpUPOi6dUrx for <mpls@ietfa.amsl.com>; Mon, 28 Nov 2016 06:55:41 -0800 (PST)
Received: from smtp-us.alcatel-lucent.com (us-hpatc-esg-01.alcatel-lucent.com [135.245.18.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A4C91295FF for <mpls@ietf.org>; Mon, 28 Nov 2016 06:55:41 -0800 (PST)
Received: from us70tumx1.dmz.alcatel-lucent.com (unknown [135.245.18.13]) by Websense Email Security Gateway with ESMTPS id BD06B2709F049; Mon, 28 Nov 2016 14:55:37 +0000 (GMT)
Received: from us70tusmtp1.zam.alcatel-lucent.com (us70tusmtp1.zam.alcatel-lucent.com [135.5.2.63]) by us70tumx1.dmz.alcatel-lucent.com (GMO) with ESMTP id uASEtelO017910 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 28 Nov 2016 14:55:40 GMT
Received: from US70TWXCHHUB04.zam.alcatel-lucent.com (us70twxchhub04.zam.alcatel-lucent.com [135.5.2.36]) by us70tusmtp1.zam.alcatel-lucent.com (GMO) with ESMTP id uASEtHel006972 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 28 Nov 2016 14:55:40 GMT
Received: from US70UWXCHMBA01.zam.alcatel-lucent.com ([169.254.7.176]) by US70TWXCHHUB04.zam.alcatel-lucent.com ([135.5.2.36]) with mapi id 14.03.0301.000; Mon, 28 Nov 2016 09:55:35 -0500
From: "Aissaoui, Mustapha (Nokia - CA)" <mustapha.aissaoui@nokia.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Thread-Topic: [mpls] Question on draft-ietf-mpls-rfc4379bis-09.txt
Thread-Index: AdJGnV7er03UlZ6JRUi/8+DkE/AdkADC2LQAAAi2+rA=
Date: Mon, 28 Nov 2016 14:55:33 +0000
Message-ID: <4A79394211F1AF4EB57D998426C9340DD4AEF5DD@US70UWXCHMBA01.zam.alcatel-lucent.com>
References: <4A79394211F1AF4EB57D998426C9340DD4AEC84F@US70UWXCHMBA01.zam.alcatel-lucent.com> <65916DBD-057B-4030-8028-35209556BB8D@cisco.com>
In-Reply-To: <65916DBD-057B-4030-8028-35209556BB8D@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.5.27.18]
Content-Type: multipart/alternative; boundary="_000_4A79394211F1AF4EB57D998426C9340DD4AEF5DDUS70UWXCHMBA01z_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/rIngeo6KEZApwtSq2jSNjKFh1IU>
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: Mon, 28 Nov 2016 14:55:43 -0000

Hi Carlos,
You meant: {Section 5.1, Section 5.2, Section 5.*3*} .

Also, you need to reference draft-ietf-mpls-rfc4379bis-09.txt instead of RFC 4379 throughout the document and replace DSMAP TLV with DDMAP TLV (RFC 6424).

I have a few more comments on draft-ietf-mpls-spring-lsp-ping-01 which I will be sending in a separate message.

Regards,
Mustapha.

From: Carlos Pignataro (cpignata) [mailto:cpignata@cisco.com]
Sent: Monday, November 28, 2016 8:54 AM
To: Aissaoui, Mustapha (Nokia - CA) <mustapha.aissaoui@nokia.com>
Cc: mpls@ietf.org
Subject: Re: [mpls] Question on draft-ietf-mpls-rfc4379bis-09.txt

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.
_______________________________________________
mpls mailing list
mpls@ietf.org<mailto:mpls@ietf.org>
https://www.ietf.org/mailman/listinfo/mpls