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

"Aissaoui, Mustapha (Nokia - CA)" <mustapha.aissaoui@nokia.com> Fri, 25 November 2016 16:29 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 190AB12951B for <mpls@ietfa.amsl.com>; Fri, 25 Nov 2016 08:29:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level:
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 s3VNVnq_76ou for <mpls@ietfa.amsl.com>; Fri, 25 Nov 2016 08:29:19 -0800 (PST)
Received: from smtp-us.alcatel-lucent.com (us-hpswa-esg-01.alcatel-lucent.com [135.245.18.29]) (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 EBD3D1294EE for <mpls@ietf.org>; Fri, 25 Nov 2016 08:29:18 -0800 (PST)
Received: from us70uumx3.dmz.alcatel-lucent.com (unknown [135.245.18.15]) by Websense Email Security Gateway with ESMTPS id DFBF8927AB5DE; Fri, 25 Nov 2016 16:29:15 +0000 (GMT)
Received: from us70uusmtp3.zam.alcatel-lucent.com (us70uusmtp3.zam.alcatel-lucent.com [135.5.2.65]) by us70uumx3.dmz.alcatel-lucent.com (GMO) with ESMTP id uAPGTHdK016490 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 25 Nov 2016 16:29:17 GMT
Received: from US70UWXCHHUB02.zam.alcatel-lucent.com (us70uwxchhub02.zam.alcatel-lucent.com [135.5.2.49]) by us70uusmtp3.zam.alcatel-lucent.com (GMO) with ESMTP id uAPGRsbO012884 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 25 Nov 2016 16:29:17 GMT
Received: from US70UWXCHMBA01.zam.alcatel-lucent.com ([169.254.7.176]) by US70UWXCHHUB02.zam.alcatel-lucent.com ([135.5.2.49]) with mapi id 14.03.0301.000; Fri, 25 Nov 2016 11:28:34 -0500
From: "Aissaoui, Mustapha (Nokia - CA)" <mustapha.aissaoui@nokia.com>
To: "t.petch" <ietfc@btconnect.com>, "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: [mpls] Question on draft-ietf-mpls-rfc4379bis-09.txt
Thread-Index: AdJGnV7er03UlZ6JRUi/8+DkE/AdkAAccqn6AAo02wA=
Date: Fri, 25 Nov 2016 16:28:33 +0000
Message-ID: <4A79394211F1AF4EB57D998426C9340DD4AED1C0@US70UWXCHMBA01.zam.alcatel-lucent.com>
References: <4A79394211F1AF4EB57D998426C9340DD4AEC84F@US70UWXCHMBA01.zam.alcatel-lucent.com> <010201d2470e$9f762500$4001a8c0@gateway.2wire.net>
In-Reply-To: <010201d2470e$9f762500$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.5.27.16]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/8WPHQOqI_8EyqkO-g4nFkH-61D4>
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: Fri, 25 Nov 2016 16:29:22 -0000

Thanks Tom. 

So, draft-ietf-mpls-spring-lsp-ping when it becomes RFC should state that it is updating the RFC which will come out of draft-ietf-mpls-rfc4379bis-09.txt.

Mustapha.

> -----Original Message-----
> From: t.petch [mailto:ietfc@btconnect.com]
> Sent: Friday, November 25, 2016 6:25 AM
> To: Aissaoui, Mustapha (Nokia - CA) <mustapha.aissaoui@nokia.com>;
> mpls@ietf.org
> Subject: Re: [mpls] Question on draft-ietf-mpls-rfc4379bis-09.txt
> 
> ----- Original Message -----
> From: "Aissaoui, Mustapha (Nokia - CA)" <mustapha.aissaoui@nokia.com>
> To: <mpls@ietf.org>
> Sent: Thursday, November 24, 2016 10:05 PM
> 
> 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.
> 
> <tp>
> 
> My reading would be that there is no such registry.  The new sub-TLV appear at
> http://www.iana.org/assignments/mpls-lsp-ping-parameters/mpls-lsp-ping-p
> arameters.xml#sub-tlv-1-16-21
> where for e.g. 34 the reference is to the I-D that you cite, with no more details.
> 
> Not all names and numbers appear in an IANA registry; setting up and maintaining
> a registry takes work and sometimes it is not worth it.  If the only use is local to the
> one field and only in the one RFC, then it may not be worth it.
> 
> Tom Petch
> 
> Regards,
> Mustapha.
> 
> 
> 
> ------------------------------------------------------------------------
> --------
> 
> 
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls
> >