Re: [netmod] Alexey Melnikov's Discuss on draft-ietf-netmod-module-tags-07: (with DISCUSS)

"Rob Wilton (rwilton)" <rwilton@cisco.com> Fri, 14 February 2020 12:35 UTC

Return-Path: <rwilton@cisco.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F8191200DE; Fri, 14 Feb 2020 04:35:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=WqGIuStJ; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=bGZYKw4j
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 JYo56N48gq9E; Fri, 14 Feb 2020 04:35:08 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D46C120043; Fri, 14 Feb 2020 04:35:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5407; q=dns/txt; s=iport; t=1581683708; x=1582893308; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=uns2mieqftMFmOOr4pukjRclVZ24Y1xntY/NzrEr5ZA=; b=WqGIuStJQ79cpJtbE1o8UL3pKx2y7JoF0Mn8FvmE98b6u4fR/xTBjQ/V CG1NtftHk/Fu/r2NyiJlb5iTkoT6dbh5640F4BbbRGvmaZEW+wWoPciP1 ZLx0HcPrk0iurSeRxPo6ePs8h6zv8AEOrTIdOpSsCast86Uktdm9Z2m1V I=;
IronPort-PHdr: 9a23:onoJKB8GmZW8Ef9uRHGN82YQeigqvan1NQcJ650hzqhDabmn44+8ZB7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfk0jgZdYBUERoMiMEYhQslVdSaCEnnK/jCZC0hF8MEX1hgrDm2
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CuBQBYk0Ze/4YNJK1mHAEBAQEBBwEBEQEEBAEBgXuBVFAFbFggBAsqCodQA4p3gl+JYo4vgUKBEANUCQEBAQwBASMKAgQBAYRAAoIBJDgTAgMNAQEFAQEBAgEFBG2FNwyFZgEBAQEDEigGAQElEgELBAIBCA4DBAEBAR4QIREdCAIEDgUIGoMFgkoDLgECAQuiPgKBOYhigieCfwEBBYFDQYMeDQuCDAMGgTiMJBqBQT+BEUeBTn4+ghtJAgECAYEsARIBCRowgxCCLI1LHYI6nmYyRAqCOodNilQEgWKCZoJJiBSQO5dWgiqQFgIEAgQFAg4BAQWBaSJnWBEIcBU7gmxQGA2OHTiDO4UUhT90AoEnjH2BIgGBDwEB
X-IronPort-AV: E=Sophos;i="5.70,440,1574121600"; d="scan'208";a="439879214"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 14 Feb 2020 12:35:06 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id 01ECZ5ln019801 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 14 Feb 2020 12:35:06 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 14 Feb 2020 06:35:04 -0600
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 14 Feb 2020 07:35:04 -0500
Received: from NAM10-BN7-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 14 Feb 2020 07:35:04 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=III03AeS1f2JsnirWqHhAjuVt98BEHKUHhXxiLfnqT3lBUkjEnCOBUImEKjTwL6uFZaXDFqKYVPAwFFh9h7kP98bqErdwZl+LNuPmEs9+GU/hH0oLUc2HuuB3aZ7EbQFxnkdxLtliANVpNatw/puuw2kN9lrkDW31Efd7ljxKjgSZYDQSG1m+hd7U4WvcSqz6fmjbBCXHg+7xeGreXEgg1Zg5dhiLYRJdvUOGz5OQchozxumQ5oHR/8mZI6Hy9JuJ7ymt3l7CVpj15H3ylQujH6EX4SPFBO6g7B0IJo360kGxmwx3+r2crWLTLLRBjBVmKxV9boFcEW/87xEYpREMQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vLzT270NSDwOHfMYHs7lzNnN10adfxZZFZkL7mCRml4=; b=QR3zG2Bi+eV0knBS+uHrsQgwamT72wuTtzA8CLgrkpck9cEHBUOBZZ6AWE+dGkrkGRCVzQhrRHhsax/gtOfoxrG439uGgWwdg1BEdZsbl3KlsP0SFsWyhelhZGaPnM97vSlOUD7R2NVpsxuq+EZEPaSKqNsjenkIRR2kPh5bn04F9Sll/+DdQxtMUzFbjDj3sV9GhcEIxsmBC0l1pIzDX2cTuGxfiViXMak+04sHi4ab+YYSQIhzRCTxDOxM3Dk6Xk01h7GEfi3GOoyygzzwqewFrcvSFYRfsYiwfpbQfbCMkyjJSRmHJ7KlG2F/kxWX9FrbheyHfnyHN7fivEUI/g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vLzT270NSDwOHfMYHs7lzNnN10adfxZZFZkL7mCRml4=; b=bGZYKw4jRgdxaai6L5SLoR2TeP7owp6lCisRw4HY5bA2Vl1gt0sq5Ns+hMeGb9ewdM4cpAH3imvGqPL/PGbqsYqy3WBBOgrYXXc+SdTDEut3z7xw3FYc44eyAO8KW9qSxFt9Th7TP0yM+cJVNyiI7g7w0VuIsAkmG3g1WQbsa0c=
Received: from MN2PR11MB4366.namprd11.prod.outlook.com (52.135.38.209) by MN2PR11MB3598.namprd11.prod.outlook.com (20.178.252.28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2729.25; Fri, 14 Feb 2020 12:35:03 +0000
Received: from MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::b9ce:1058:5fa6:44a1]) by MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::b9ce:1058:5fa6:44a1%7]) with mapi id 15.20.2707.031; Fri, 14 Feb 2020 12:35:03 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Christian Hopps <chopps@chopps.org>
CC: Alexey Melnikov <aamelnikov@fastmail.fm>, "netmod-chairs@ietf.org" <netmod-chairs@ietf.org>, Joel Jaeggli <joelja@gmail.com>, The IESG <iesg@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>, "draft-ietf-netmod-module-tags@ietf.org" <draft-ietf-netmod-module-tags@ietf.org>
Thread-Topic: Alexey Melnikov's Discuss on draft-ietf-netmod-module-tags-07: (with DISCUSS)
Thread-Index: AQHV4m8DGI058sprvkKdYtaQYpu786gaftpggAAIeQCAAAFigIAABDQAgAATlSA=
Date: Fri, 14 Feb 2020 12:35:02 +0000
Message-ID: <MN2PR11MB4366EB74886415CD1097BC85B5150@MN2PR11MB4366.namprd11.prod.outlook.com>
References: <155499006434.22705.5858614581630974980.idtracker@ietfa.amsl.com> <7F3B9E7F-6AD8-4801-AE60-9F2D704DC69B@chopps.org> <2ee6b71c-bd2c-4676-9e14-cb240c6845c9@www.fastmail.com> <MN2PR11MB43668E4C0863B8A61857CE0CB5150@MN2PR11MB4366.namprd11.prod.outlook.com> <714842CF-A65A-40FD-A62D-6FA7E1A6801F@chopps.org> <C1446662-2320-4158-B34B-3E2D67369F48@chopps.org> <9FECF49A-65E5-436F-973A-7538CFC974E8@chopps.org>
In-Reply-To: <9FECF49A-65E5-436F-973A-7538CFC974E8@chopps.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rwilton@cisco.com;
x-originating-ip: [82.15.79.32]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ad4e3ff5-a74f-42b8-ed75-08d7b14a5076
x-ms-traffictypediagnostic: MN2PR11MB3598:
x-microsoft-antispam-prvs: <MN2PR11MB3598ED190B46AD229F3CC7EEB5150@MN2PR11MB3598.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 03137AC81E
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(366004)(39860400002)(376002)(136003)(346002)(199004)(189003)(5660300002)(52536014)(8676002)(86362001)(81156014)(81166006)(8936002)(2906002)(66556008)(66446008)(64756008)(66476007)(66946007)(55016002)(478600001)(966005)(7696005)(33656002)(26005)(9686003)(6916009)(76116006)(186003)(54906003)(316002)(53546011)(6506007)(4326008)(71200400001); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3598; H:MN2PR11MB4366.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Wlpz4Bvu+Nka8FnKDz76zlvg8ANV+cQVvZYhAnjZF7Sp/OTEI68LylcQM/T2nUefEXiSXlWxjlsudP+K8TKfQBQblH83Kz1wdsL9PA1XTg3N+C0cCOR+h8CbFAEVOQAXt2hVFWqF9c8wE6ed74wBEuTjvrM4Z8kwMbb71ejlpyzkuCWvts6wNBqPH9SwmNuzd1CL2h1HS+rkgWH9mGNZQ9PbY6zY6PsDGSNuPCdb/ToQ95/jYlN8rrhk5oFrFbhMoBsWUmNObwQBoIuQYKfkw06UpfisbIx5OQAr8ws6PzJ5rZ53k3uFsMXDiMY9FE93WUhZLxoO+Xx3WC6sztmD3iuyVzwLfeU679IyNZBn2uhc8YMF2CcDc+j/msh6IbqFULJQsnQC9qatfDuS/nOAAJ9+4G9pS/WmrLSxlFtK7qlVbOJNRIoEAbyOzK5FRxDIVkWRdDGQVRvmr2Zi/GqlWivbwOzqu5gFbTsg9iJ2cgztxM1VjoN2SBIgWqVTHYm/huuIT/6bOzOzgL6CpBOdUA==
x-ms-exchange-antispam-messagedata: 3D/Lzx0PPR4KXt4k2b+wUJZla8EJ7Zs+djHpBRFQIplWXX6ErrMd07OZibx2iOUeOUpXYxFaHe2fePPNGJqgiX3wF6szqJvZgT7lwCTQqnU+MzqWGlgyuyW6JePXqed2G9UvJiK07/6srBGVH2izXg==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: ad4e3ff5-a74f-42b8-ed75-08d7b14a5076
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Feb 2020 12:35:03.0362 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 1zcXI6vU380pQCufYUOKT4f5hL3VuiVzluAjcyPZmgJJUQ73KeMchc9PIlk1NGjjdQUHzqIKwD/8N9lzb03rQg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3598
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.13, xch-aln-003.cisco.com
X-Outbound-Node: alln-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/Wy6CZwBb_5MJIuYXXgfzXHh9FIw>
Subject: Re: [netmod] Alexey Melnikov's Discuss on draft-ietf-netmod-module-tags-07: (with DISCUSS)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2020 12:35:10 -0000

Hi Chris,

I think that would be okay, although perhaps using SHOULD rather than "should" might be better, given that SHOULD NOT is used elsewhere in the description.

Thanks,
Rob


> -----Original Message-----
> From: Christian Hopps <chopps@chopps.org>
> Sent: 14 February 2020 11:21
> To: Rob Wilton (rwilton) <rwilton@cisco.com>
> Cc: Christian Hopps <chopps@chopps.org>; Alexey Melnikov
> <aamelnikov@fastmail.fm>; netmod-chairs@ietf.org; Joel Jaeggli
> <joelja@gmail.com>; The IESG <iesg@ietf.org>; netmod@ietf.org; draft-ietf-
> netmod-module-tags@ietf.org
> Subject: Re: Alexey Melnikov's Discuss on draft-ietf-netmod-module-tags-
> 07: (with DISCUSS)
> 
> How about I add this to the description of "typedef tag" in the module:
> 
>        description
>          "A tag is a type 'string' value that does not include carriage
>           return, newline or tab characters. It SHOULD begin with a
>           registered prefix; however, tags without a registered prefix
> -         SHOULD NOT be treated as invalid.";
> +         SHOULD NOT be treated as invalid. For the purposes of comparison
> +         non-ascii strings should use 'NFC' (RFC5198) normalization";
>      }
> 
> Thanks,
> Chris.
> 
> > On Feb 14, 2020, at 6:06 AM, Christian Hopps <chopps@chopps.org> wrote:
> >
> > For the record this one is 3 years and counting. For a list of tags.
> >
> >> On Feb 14, 2020, at 6:01 AM, Christian Hopps <chopps@chopps.org> wrote:
> >>
> >> I was not approaching this discuss with this level of change in mind.
> How many years does it take to get a YANG model even one as simple as this
> completed?
> >>
> >> Thanks,
> >> Chris.
> >>
> >>> On Feb 14, 2020, at 5:43 AM, Rob Wilton (rwilton) <rwilton@cisco.com>
> wrote:
> >>>
> >>> Hi Alexey, Christian,
> >>>
> >>> Allowing Unicode but requiring normalization as per RFC 5198 for IANA
> managed tags makes sense to me.
> >>>
> >>> But does the server also need to normalize any configured tags?  I.e.
> should the description for the tag typedef also specify that tags SHOULD
> be normalized, and specify a normalization method that SHOULD be used?  Or
> is the onus on the client to use sensible (i.e. already normalized)
> values, and if so, does that need to be stated?
> >>>
> >>> Thanks,
> >>> Rob
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: iesg <iesg-bounces@ietf.org> On Behalf Of Alexey Melnikov
> >>>> Sent: 13 February 2020 13:10
> >>>> To: Christian Hopps <chopps@chopps.org>
> >>>> Cc: netmod-chairs@ietf.org; Joel Jaeggli <joelja@gmail.com>; The
> >>>> IESG <iesg@ietf.org>; netmod@ietf.org;
> >>>> draft-ietf-netmod-module-tags@ietf.org
> >>>> Subject: Re: Alexey Melnikov's Discuss on
> >>>> draft-ietf-netmod-module-tags-
> >>>> 07: (with DISCUSS)
> >>>>
> >>>> Hi Christian,
> >>>>
> >>>> On Thu, Feb 13, 2020, at 12:30 AM, Christian Hopps wrote:
> >>>>> The intent in the document is to place as few restrictions on tags
> >>>>> as possible to allow for future-proofing and organic growth of use
> >>>>> both within and outside of SDOs. For standard tags we trust IANA
> >>>>> (and the human behind the process) to make the call on whether a
> >>>>> tag is already present. :)
> >>>>
> >>>> And the problem with that is that because there might be multiple
> >>>> ways to encode in Unicode visually indistinguishable tags IANA
> >>>> would end up asking IESG for help.
> >>>>
> >>>> So you need to at minimum specify a Unicode normalization form to
> >>>> use. I suggest you normatively reference RFC 5198 here.
> >>>>
> >>>>> Having worked for a company where a lot of XML string data was
> >>>>> non-ascii I find limiting to ascii to be rather restrictive.
> >>>>
> >>>> Best Regards,
> >>>> Alexey
> >>>>
> >>>>>
> >>>>> Thanks,
> >>>>> Chris.
> >>>>>
> >>>>>> On Apr 11, 2019, at 9:41 AM, Alexey Melnikov via Datatracker
> >>>> <noreply@ietf.org> wrote:
> >>>>>>
> >>>>>> Alexey Melnikov has entered the following ballot position for
> >>>>>> draft-ietf-netmod-module-tags-07: Discuss
> >>>>>>
> >>>>>> When responding, please keep the subject line intact and reply to
> >>>>>> all email addresses included in the To and CC lines. (Feel free
> >>>>>> to cut this introductory paragraph, however.)
> >>>>>>
> >>>>>>
> >>>>>> Please refer to
> >>>>>> https://www.ietf.org/iesg/statement/discuss-criteria.html
> >>>>>> for more information about IESG DISCUSS and COMMENT positions.
> >>>>>>
> >>>>>>
> >>>>>> The document, along with other ballot positions, can be found here:
> >>>>>> https://datatracker.ietf.org/doc/draft-ietf-netmod-module-tags/
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> -----------------------------------------------------------------
> >>>>>> ---
> >>>>>> --
> >>>>>> DISCUSS:
> >>>>>> -----------------------------------------------------------------
> >>>>>> ---
> >>>>>> --
> >>>>>>
> >>>>>> This is generally a fine document, but after checking RFC 7950
> >>>>>> syntax for strings I question why you think you need non ASCII
> tags.
> >>>>>> There are so many problems that can arise from that. For example,
> >>>>>> how would IANA be able to enforce uniqueness of Unicode tags
> >>>>>> written in different Unicode canonicalisation forms?
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>
> >>
> >