Re: [I2nsf] draft-ietf-i2nsf-nsf-monitoring-data-model

supjps-ietf@jpshallow.com Wed, 01 June 2022 13:31 UTC

Return-Path: <jon.shallow@jpshallow.com>
X-Original-To: i2nsf@ietfa.amsl.com
Delivered-To: i2nsf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 467DFC14CF04 for <i2nsf@ietfa.amsl.com>; Wed, 1 Jun 2022 06:31:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 EDl14B5RNmsG for <i2nsf@ietfa.amsl.com>; Wed, 1 Jun 2022 06:31:35 -0700 (PDT)
Received: from mail.jpshallow.com (mail.jpshallow.com [31.22.13.189]) (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 1DDE4C14CF0C for <i2nsf@ietf.org>; Wed, 1 Jun 2022 06:31:34 -0700 (PDT)
Received: from n01332.jpshallow.com ([192.168.0.78] helo=N01332) by mail.jpshallow.com with esmtp (Exim 4.92.3) (envelope-from <jon.shallow@jpshallow.com>) id 1nwORf-00052F-Lt; Wed, 01 Jun 2022 14:31:31 +0100
From: supjps-ietf@jpshallow.com
To: "'Mr. Jaehoon Paul Jeong'" <jaehoon.paul@gmail.com>
Cc: draft-ietf-i2nsf-nsf-monitoring-data-model@ietf.org, i2nsf-chairs@ietf.org, i2nsf@ietf.org, 'Patrick Lingga' <patricklink888@gmail.com>, "'Mr. Jaehoon Paul Jeong'" <jaehoon.paul@gmail.com>
References: <04bd01d875b2$3e7d7ef0$bb787cd0$@jpshallow.com> <CAPK2DezZfz=FsKAweT=_T21gz1PUur=EG0pNtqGKkNO+pFtQTw@mail.gmail.com>
In-Reply-To: <CAPK2DezZfz=FsKAweT=_T21gz1PUur=EG0pNtqGKkNO+pFtQTw@mail.gmail.com>
Date: Wed, 01 Jun 2022 14:31:29 +0100
Message-ID: <04fd01d875bb$e6b7a9c0$b426fd40$@jpshallow.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_04FE_01D875C4.487E82C0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFCKcJDTCaitHtpb7iOpHwomP/NXQLLokSWrlDEPPA=
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/5DTJ5DT0TFc_TPdyY7P8RFfBhE0>
Subject: Re: [I2nsf] draft-ietf-i2nsf-nsf-monitoring-data-model
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: "*I2NSF: Interface to Network Security Functions mailing list*" <i2nsf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2nsf/>
List-Post: <mailto:i2nsf@ietf.org>
List-Help: <mailto:i2nsf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2022 13:31:39 -0000

Hi Paul,

 

Thanks.  It is worth though someone else doing a sanity check on my proposed corrections!

 

It is frustrating though that http://www.w3.org/TR/2004/REC-xmlschema-2-20041028 (as per https://datatracker.ietf.org/doc/html/rfc7950#section-9.4.5) does not define how to do match things case insensitively (that I can find) which would make this pattern much more readable for all of the regular and irregular branches.

 

Regards

 

Jon

 

From: Mr. Jaehoon Paul Jeong [mailto: jaehoon.paul@gmail.com] 
Sent: 01 June 2022 14:13
To: jon@jpshallow.com
Cc: draft-ietf-i2nsf-nsf-monitoring-data-model@ietf.org; i2nsf-chairs@ietf.org; i2nsf@ietf.org; Patrick Lingga; Mr. Jaehoon Paul Jeong
Subject: Re: [I2nsf] draft-ietf-i2nsf-nsf-monitoring-data-model

 

Hi Jon,

Thanks for these two corrections about the YANG language pattern match below.

 

We authors will reflect your comments on the following two I2NSF drafts under RFC Ed Queue, and 

submit the revisions:

https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-nsf-monitoring-data-model-19

https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-nsf-facing-interface-dm-28

 

Thanks.

 

Best Regards,

Paul

 

 

 

On Wed, Jun 1, 2022 at 9:49 PM <supjps-ietf@jpshallow.com> wrote:

Hi there,

 

I appreciate that this may be a bit late in the day, but I have found a couple of issues with the YANG language pattern match when doing a check against draft-ietf-dots-telemetry-25.txt, currently in AUTH48.  What I have reported against that draft is:-

 

During testing of the horrendous pattern provided for pattern matching 

against description-lang, I have found an alternate branch error which needs 

correcting.

 

OLD:

         leaf description-lang {

           type string {

             pattern '(([A-Za-z]{2,3}(-[A-Za-z]{3}(-[A-Za-z]{3})'

                   + '{0,2})?|[A-Za-z]{4}|[A-Za-z]{5,8})(-[A-Za-z]{4})?'

NEW:

         leaf description-lang {

           type string {

             pattern '((([A-Za-z]{2,3}(-[A-Za-z]{3}(-[A-Za-z]{3})'

                   + '{0,2})?)|[A-Za-z]{4}|[A-Za-z]{5,8})(-[A-Za-z]{4})?'

 

I.e, additional () around A-Za-z]{2,3}(-[A-Za-z]{3}(-[A-Za-z]{3})'

                   + '{0,2})?

 

Reasoning - RFC5646 2.1

language      = 2*3ALPHA            ; shortest ISO 639 code

                 ["-" extlang]       ; sometimes followed by

                                     ; extended language subtags

               / 4ALPHA              ; or reserved for future use

               / 5*8ALPHA            ; or registered language subtag

 

The additional () contain the 2*3ALPHA ["-" extlang] as a branch alternative 

to 4*ALPHA or 5*ALPHA.

 

There also is an unneeded character range, namely

 

OLD:

                 + '|([0-9][A-Za-z0-9]{3})))*(-[0-9A-WY-Za-wy-z]'

NEW:

                 + '|([0-9][A-Za-z0-9]{3})))*(-[0-9A-WYZa-wyz]'

 

As y is alphabetically adjacent to z ([0-9A-WYZa-wyz] is the singleton 

definition).

 

Regards

 

Jon

_______________________________________________
I2nsf mailing list
I2nsf@ietf.org
https://www.ietf.org/mailman/listinfo/i2nsf