Re: [Pce] Benjamin Kaduk's Discuss on draft-ietf-pce-wson-rwa-ext-11: (with DISCUSS and COMMENT)

<julien.meuric@orange.com> Thu, 07 February 2019 11:24 UTC

Return-Path: <julien.meuric@orange.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18B2D13110B; Thu, 7 Feb 2019 03:24:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.434
X-Spam-Level:
X-Spam-Status: No, score=0.434 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 4pXHSBtA47I3; Thu, 7 Feb 2019 03:24:40 -0800 (PST)
Received: from orange.com (mta240.mail.business.static.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B93EC1310F7; Thu, 7 Feb 2019 03:24:39 -0800 (PST)
Received: from opfedar06.francetelecom.fr (unknown [xx.xx.xx.8]) by opfedar22.francetelecom.fr (ESMTP service) with ESMTP id 43wGDk0791z2xYD; Thu, 7 Feb 2019 12:24:38 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.43]) by opfedar06.francetelecom.fr (ESMTP service) with ESMTP id 43wGDj6D3Dz3wbB; Thu, 7 Feb 2019 12:24:37 +0100 (CET)
Received: from [10.193.71.125] (10.168.234.4) by OPEXCLILM5F.corporate.adroot.infra.ftgroup (10.114.31.43) with Microsoft SMTP Server (TLS) id 14.3.435.0; Thu, 7 Feb 2019 12:24:37 +0100
To: Benjamin Kaduk <kaduk@mit.edu>
CC: Leeyoung <leeyoung@huawei.com>, The IESG <iesg@ietf.org>, "draft-ietf-pce-wson-rwa-ext@ietf.org" <draft-ietf-pce-wson-rwa-ext@ietf.org>, Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, "pce-chairs@ietf.org" <pce-chairs@ietf.org>, "pce@ietf.org" <pce@ietf.org>, Alexey Melnikov <aamelnikov@fastmail.fm>
References: <154916511174.18400.15146609335810321774.idtracker@ietfa.amsl.com> <7AEB3D6833318045B4AE71C2C87E8E173D0D3DF2@sjceml521-mbx.china.huawei.com>
From: julien.meuric@orange.com
Organization: Orange
Message-ID: <9209_1549538677_5C5C1575_9209_228_7_81fca766-6735-fb4a-06cc-96de45924ef8@orange.com>
Date: Thu, 07 Feb 2019 12:24:36 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <7AEB3D6833318045B4AE71C2C87E8E173D0D3DF2@sjceml521-mbx.china.huawei.com>
Content-Type: text/html; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Originating-IP: [10.168.234.4]
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/bVU_UEAWd39p-pebbI7tCKqCXUw>
Subject: Re: [Pce] Benjamin Kaduk's Discuss on draft-ietf-pce-wson-rwa-ext-11: (with DISCUSS and COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Feb 2019 11:24:41 -0000

Hi Young,

FWIW, the IANA already manages several similar registries with the same 3 entries (e.g., https://www.iana.org/assignments/lmp-parameters/lmp-parameters.xhtml#lmp-parameters-15" rel="nofollow">https://www.iana.org/assignments/lmp-parameters/lmp-parameters.xhtml#lmp-parameters-15). Creating one will help addressing this concern raised by Alexey and Benjamin.

Thanks,

Julien


On 07/02/2019 02:27, Leeyoung wrote:

What is the mechanism for extensibility of future Link Identifier sub-TLV types?  Should there be a registry?

 

YL>>  I am not sure if we need reserve for future interface type. Typical PCEP/GMPLS RFCs do not go beyond this three types and the unnumbered type is flexible enough to accommodate other types than IPv4 and IPv6.


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.