Re: [ippm] WGLC for draft-ietf-ippm-ioam-yang

Tianran Zhou <zhoutianran@huawei.com> Mon, 15 August 2022 10:09 UTC

Return-Path: <zhoutianran@huawei.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97471C1522AB for <ippm@ietfa.amsl.com>; Mon, 15 Aug 2022 03:09:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O_fzTLletxkl for <ippm@ietfa.amsl.com>; Mon, 15 Aug 2022 03:09:41 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56CFCC1522AC for <ippm@ietf.org>; Mon, 15 Aug 2022 03:09:41 -0700 (PDT)
Received: from fraeml705-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4M5qkx05Zxz67VpW for <ippm@ietf.org>; Mon, 15 Aug 2022 18:09:29 +0800 (CST)
Received: from kwepemi100009.china.huawei.com (7.221.188.242) by fraeml705-chm.china.huawei.com (10.206.15.54) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2375.24; Mon, 15 Aug 2022 12:09:39 +0200
Received: from kwepemi500009.china.huawei.com (7.221.188.199) by kwepemi100009.china.huawei.com (7.221.188.242) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Mon, 15 Aug 2022 18:09:37 +0800
Received: from kwepemi500009.china.huawei.com ([7.221.188.199]) by kwepemi500009.china.huawei.com ([7.221.188.199]) with mapi id 15.01.2375.024; Mon, 15 Aug 2022 18:09:37 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: t petch <ietfa@btconnect.com>, Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>, IETF IPPM WG <ippm@ietf.org>
Thread-Topic: [ippm] WGLC for draft-ietf-ippm-ioam-yang
Thread-Index: AQHYrAtfJXmzYLq0O0CFzBtc4doyDa2pCJGAgAGbPBCAAENSAIAEShSQgAAEXACAAJBf8A==
Date: Mon, 15 Aug 2022 10:09:37 +0000
Message-ID: <d358286647064d549f6ff91782639436@huawei.com>
References: <AB392216-E345-4274-9236-B5BEC9DF2BAB@apple.com> <62F4E459.2030908@btconnect.com> <caf32586b9404998a015d38f7aeb67ac@huawei.com> <62F675CA.2030501@btconnect.com> <547d4f8c5fd7483c9186d2656958e687@huawei.com> <62FA1294.6000205@btconnect.com>
In-Reply-To: <62FA1294.6000205@btconnect.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.41.183]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/XALW2gvih20w5tn9tSBDvYwY7PA>
Subject: Re: [ippm] WGLC for draft-ietf-ippm-ioam-yang
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2022 10:09:45 -0000

Hi Tom,

Thanks. Then, let's make it 300 at present. And see what happens. :-)

Best,
Tianran

-----Original Message-----
From: t petch [mailto:ietfa@btconnect.com] 
Sent: Monday, August 15, 2022 5:32 PM
To: Tianran Zhou <zhoutianran@huawei.com>; Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>; IETF IPPM WG <ippm@ietf.org>
Subject: Re: [ippm] WGLC for draft-ietf-ippm-ioam-yang

On 15/08/2022 02:30, Tianran Zhou wrote:
> Hi Tom,
>
> Thanks again. Please see in line.
>
> Tianran
>
> -----------------------------
> Well yes, but RFC9197 (needs adding to the I-D references and to the
> YANG) has a MUST for e.g. support of the default namespace so having a lower case 'must' to me downgrades that requirement whereever it appears.  It is common for YANG modules to have RFC8174 language with the disclaimer therefrom next to the Copyright of the module.
>
> ZTR> OK. I will update.
>
> In passing, the spelling of 'namespace' is inconsistent.
> ZTR> Thanks.
>
> I wonder if there is a security exposure such as a buffer overflow when a string is 18446744073709551615 characters long.
> ZTR> I believe we do not need such a long name. I think various devices may have different constraints. Maybe we can make it 300 characters long? Any suggestion?

That value is the one in RFC7950 that implementations are expected to support!  I always think that there should be a lower constraint but have no logic to support any given figure in this case. A profile seems to be internal to the node, name unique within the node and so likely to be a quite short string unless it contains a node identifier or some such.  Whatever value you put in, someone (IESG!) will say why, to which the answer is why not?.

Tom Petch

> Tom Petch
>
>> Tom Petch
>>
>>>
>>> The last call will go until Wednesday, August 31.
>>>
>>> Best,
>>> Tommy & Marcus
>>>
>>>
> .
>