Re: [netmod] Eric Rescorla's No Objection on draft-ietf-netmod-rfc6087bis-18: (with COMMENT)

Eric Rescorla <ekr@rtfm.com> Wed, 07 March 2018 21:57 UTC

Return-Path: <ekr@rtfm.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 5669B12D952 for <netmod@ietfa.amsl.com>; Wed, 7 Mar 2018 13:57:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
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 3YikQ2Ui4xlH for <netmod@ietfa.amsl.com>; Wed, 7 Mar 2018 13:57:06 -0800 (PST)
Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29FD912D7EF for <netmod@ietf.org>; Wed, 7 Mar 2018 13:57:04 -0800 (PST)
Received: by mail-qt0-x229.google.com with SMTP id c7so4511099qtn.3 for <netmod@ietf.org>; Wed, 07 Mar 2018 13:57:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=mpg/V8dSQfNs9Fna19fWddsQxSFpB53y5o+SoT8Oaok=; b=MJJEK96cllYzkP3uMJTDLOs5nU+VJQndbUFAmCUo3UlTpR2Q+AWjSF+fVFqlrVJGNw wURChAVHftje8/GqACPwl42Ikowrq3aHd7nyGob1GpcSaQwgiS9STb5ZFnwzLSrGLvQN AV1gtlE44VFCuzpjV7Q0P6CEYcniGlP9th/4kefNOfegLsRLtxx075CdV2ifhwJCH/kG iJom0Ew4T5PqLJBbzmndFnf9jKMr+2cf+9P6eE2sMZ8EYyuJ5oA0/FHQaOLqhXtFM2qC 3kfdma4IQtxfECRCSgPB8ruaRyYDJRE9SVwAJdN2CBnUwHdMOKbqOhRgsOspyjzrjbwA /r8w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=mpg/V8dSQfNs9Fna19fWddsQxSFpB53y5o+SoT8Oaok=; b=KJa3Gr0a/ouiXnX3keAkKt1PzJG5+PZwo3f1d/k/sC4V3nWhWWisJ71xccU3hrkLna gdkHx5CJeR+m0QOB54qY5YnCIWiKm6daeFmDlx4NfV37IzjxuuinDfSSoDF+sAMKSDiQ J8S1Sxc6sMbkmop4fZMQISEfLcs9VSiNKsP81qZ5ZShq5NFgPWGxvrhwSB4GjaD8GHAd XXF0pBNK+ImqcDc5b4bvYzhFRcpmoUK7WOgI0Pqcj8x+7iPMwdJ9GEuFLXGWoi+4m4dD g+lLQgiqbKF30+ezo1SYh96H7vTiwRNctrAnbD7c87YDYYxBKf6WkwH75pc9VgsTqm7H 3vUg==
X-Gm-Message-State: AElRT7F5lQ1Jj/lt5PNbkEbVN2LzmJCTIGIgFw1dWEo2ujAE915sUphA 6ke+csV0H6kUqmFiLjWsMj5G9K0tZHq/8cnZkiNW4A==
X-Google-Smtp-Source: AG47ELtazJgxO12H9l+nNzRaxkEcGSn/4P5+2a0jmNsKJctLjsnyn/nvi88Txb/ausYormZwsaFQphm+/JBYxYoj8mM=
X-Received: by 10.200.7.77 with SMTP id k13mr36344572qth.165.1520459823197; Wed, 07 Mar 2018 13:57:03 -0800 (PST)
MIME-Version: 1.0
Received: by 10.200.37.176 with HTTP; Wed, 7 Mar 2018 13:56:22 -0800 (PST)
In-Reply-To: <CABCOCHTY0kkfvLT9AjM+9-rtoU30j1ijg8bkKG=iNJOzAH9nhw@mail.gmail.com>
References: <152045215867.17597.99576332554022377.idtracker@ietfa.amsl.com> <CABCOCHTY0kkfvLT9AjM+9-rtoU30j1ijg8bkKG=iNJOzAH9nhw@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 7 Mar 2018 13:56:22 -0800
Message-ID: <CABcZeBM5zvwYHCAEUi+Sg7zjLk5pFwTANXidHkZwstnpjHLezA@mail.gmail.com>
To: Andy Bierman <andy@yumaworks.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-netmod-rfc6087bis@ietf.org, NetMod WG Chairs <netmod-chairs@ietf.org>, Kent Watsen <kwatsen@juniper.net>, NetMod WG <netmod@ietf.org>
Content-Type: multipart/alternative; boundary="f403043a8c74a8447b0566d9a32a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/Rsi5-MJbYgq6kC-4AksElO0-yu4>
Subject: Re: [netmod] Eric Rescorla's No Objection on draft-ietf-netmod-rfc6087bis-18: (with COMMENT)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 07 Mar 2018 21:57:08 -0000

On Wed, Mar 7, 2018 at 1:44 PM, Andy Bierman <andy@yumaworks.com>; wrote:

>
>
> On Wed, Mar 7, 2018 at 11:49 AM, Eric Rescorla <ekr@rtfm.com>; wrote:
>
>> Eric Rescorla has entered the following ballot position for
>> draft-ietf-netmod-rfc6087bis-18: No Objection
>>
>> 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-rfc6087bis/
>>
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> draft-ietf-netmod-rfc6087bis.txt:500
>>    normative, if the module itself is considered normative, and not an
>>    example module or example YANG fragment.  The use of keywords defined
>>    in [RFC2119] apply to YANG description statements in normative
>> I think you probably want to rewrite this as:
>>
>> "Note that if the module itself is considered normative and not an example
>> module or example YANG fragment, then all YANG statements..."
>>
>>
> OK
>
>
>
>>    o  Prefixes are never allowed for built in data types and YANG
>>       keywords.
>> I'm not sure I understand what this means. Is the idea that I can't use
>> "example-import" somewhere?
>>
>>
>
> The external keyword "example:import" is not the same as the YANG keyword
> "import"
> YANG keywords are not allowed to have prefixes.
>

>
>
>
>>    character MAY be used if the identifier represents a well-known value
>>    that uses these characters.
>> Is this text saying that only characters in these two subsets are allowed
>> and
>> therefore, for instance "." is forbidden
>>
>
>
> This text is suggesting the characters that SHOULD be used.
> The dot and dash chars are not included. The text specifies which
> characters are included.
>

I'm sorry, I am still confused. Here's the original text:

   Identifiers SHOULD follow a consistent naming pattern throughout the
   module.  Only lower-case letters, numbers, and dashes SHOULD be used
   in identifier names.  Upper-case characters and the underscore
   character MAY be used if the identifier represents a well-known value
   that uses these characters.

There are other characters that are not in either of these sets. Are you
saying
that they can't be used under any conditions?

-Ekr


>
>
>>
>>    It is RECOMMENDED that only valid YANG modules be included in
>>    documents, whether or not they are published yet.  This allows:
>> For clarify, I assume you mean "the modules are published yet"
>>
>>
> OK
>
>
>>    The NETCONF Access Control Model (NACM) [I-D.ietf-netconf-rfc6536bis]
>>    does not support parameter access control for RPC operations.  The
>>    user is given permission (or not) to invoke the RPC operation with
>> This might be slightly clearer if you said "parameter-based access
>> control"
>>
>>
>>
> OK
>
> Andy
>
>
>