Re: [Pce] Alexey Melnikov's No Objection on draft-ietf-pce-wson-rwa-ext-11: (with COMMENT)

Leeyoung <leeyoung@huawei.com> Wed, 13 February 2019 22:20 UTC

Return-Path: <leeyoung@huawei.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 7A299130DBE; Wed, 13 Feb 2019 14:20:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 hfs6aVdIQenU; Wed, 13 Feb 2019 14:20:47 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 C9D18130DC0; Wed, 13 Feb 2019 14:20:46 -0800 (PST)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id E2159B90830D8D8E03CD; Wed, 13 Feb 2019 22:20:44 +0000 (GMT)
Received: from SJCEML701-CHM.china.huawei.com (10.208.112.40) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 13 Feb 2019 22:20:44 +0000
Received: from SJCEML521-MBX.china.huawei.com ([169.254.1.95]) by SJCEML701-CHM.china.huawei.com ([169.254.3.144]) with mapi id 14.03.0415.000; Wed, 13 Feb 2019 14:20:39 -0800
From: Leeyoung <leeyoung@huawei.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>, The IESG <iesg@ietf.org>
CC: "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>
Thread-Topic: Alexey Melnikov's No Objection on draft-ietf-pce-wson-rwa-ext-11: (with COMMENT)
Thread-Index: AQHUvVDKoKseyTliy0WGMIDP1cCrnaXTj74ggAEc/4CACagcMA==
Date: Wed, 13 Feb 2019 22:20:38 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E173D0D5ABC@sjceml521-mbx.china.huawei.com>
References: <154937076957.32255.7634791989083733613.idtracker@ietfa.amsl.com> <7AEB3D6833318045B4AE71C2C87E8E173D0D3E3A@sjceml521-mbx.china.huawei.com> <1549535637.3741510.1652799144.505C9E47@webmail.messagingengine.com>
In-Reply-To: <1549535637.3741510.1652799144.505C9E47@webmail.messagingengine.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.192.11.123]
Content-Type: multipart/mixed; boundary="_004_7AEB3D6833318045B4AE71C2C87E8E173D0D5ABCsjceml521mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/WXTcGjITJSxjSIXO6Wahr55_nhk>
Subject: Re: [Pce] Alexey Melnikov's No Objection on draft-ietf-pce-wson-rwa-ext-11: (with 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: Wed, 13 Feb 2019 22:20:51 -0000

Hi Alexey,

My apology for the delay in responding to your comment. Please see inline for my response.

Thanks.
young

From: Alexey Melnikov [mailto:aamelnikov@fastmail.fm]
Sent: Thursday, February 7, 2019 4:34 AM
To: Leeyoung <leeyoung@huawei.com>; The IESG <iesg@ietf.org>
Cc: draft-ietf-pce-wson-rwa-ext@ietf.org; Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>; pce-chairs@ietf.org; pce@ietf.org
Subject: Re: Alexey Melnikov's No Objection on draft-ietf-pce-wson-rwa-ext-11: (with COMMENT)

Hi,

On Thu, Feb 7, 2019, at 1:44 AM, Leeyoung wrote:

In Section 4.3:



   o  Link Identifiers: Identifies each link ID for which restriction

   is applied. The length is dependent on the link format and the Count

   field.



Is the type field extensible?



YL>> Yes.

In this case the document is problematic, because length depends on the particular link type, so if a receiver doesn't recognize a particular link type, it wouldn't be able to parse the structure. (If this is by design, you might want to be more explicit about this.)

You also need an IANA registry for link format types.

YL>> What I meant extensible is that there are reserved field for the future use. We did not ask for IANA for this; instead, the PCE co-chair (please the attached email from Julien on this matter) suggested to re-use the existing registry defined in LMP. Please see the revised text in the last paragraph of Section 4.3.1:

  “The Type field is extensible. Please refer to the IANA registry
   allocated for Link Management Protocol (LMP) [RFC4204]:
   https://www.iana.org/assignments/lmp-parameters/lmp-
   parameters.xhtml#lmp-parameters-15.”

Do you think we still need IANA registry for link format types explicitly in this document?

Best Regards,
Alexey



--- Begin Message ---
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). 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.
--- End Message ---