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

Andy Bierman <andy@yumaworks.com> Wed, 07 March 2018 22:22 UTC

Return-Path: <andy@yumaworks.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 64BB3127419 for <netmod@ietfa.amsl.com>; Wed, 7 Mar 2018 14:22:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 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_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-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 daSEh6ukX3Fu for <netmod@ietfa.amsl.com>; Wed, 7 Mar 2018 14:22:25 -0800 (PST)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (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 8556E12D95B for <netmod@ietf.org>; Wed, 7 Mar 2018 14:22:22 -0800 (PST)
Received: by mail-lf0-x22f.google.com with SMTP id f75-v6so5555674lfg.6 for <netmod@ietf.org>; Wed, 07 Mar 2018 14:22:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Q/NKGI9PDl0ZiXfiVos3z7ig6znAbkk1HQPmtiwZ2Fg=; b=VPLfmRRpfNDa6CP9RQkJsQnbfxBNnM9rf8C/GwEKQNClV81NdLs4n2tmfy/VPxkxd6 6dAQYQNsInnR00dVr6DF/vdMD7MoyXNyK2TD6ftP+dHY9ppzJxOe8DVPdDzOvVWwIYZp iVU9roAKrUDc5OgNIVrL2YUszAqk2s8Eq7f7zXwDz4L12EiHhbsXs4ay7R1eTcS+ejcU /4SlehGBgY7IEmXZOR9ugD5s9EAjpLRMfqOZeh4LSXBRc38MgfS9kMVuGM0RzZz1bTFy BSDnfT9TU8Xr4nE82v+EgoaGBHn4UjgnzzYQ2bSOROhX3g9UQ6ORhmLsmP+9eXhbhbHo j1Kw==
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=Q/NKGI9PDl0ZiXfiVos3z7ig6znAbkk1HQPmtiwZ2Fg=; b=RF59FZM9HKWXww7y4W5m7EbNY86jWz1Ej8SqIk0wBNmOStP2jIRcU2ubK5wXXDbPr7 LtQJuAHmv5eKbEZbMk9lHVSRh/SY9fhhLA8o6u8hPcm6ARef0e8DwfJeorshgmvblNyo ze4bTBaPJQBE0nsZt2ziGmgaSvGu4BKse7Ol1q18hA0SsLy+57YXLx2KFy6wgu7qqKlY n1br8n3eIirFjsaht2djchSg65+CSjQWG+K5FT8mjZEchpDa4Z/AGP8oGfsUcRKUfg+h IO2VRfYBXFZ/yJQs19Ppboy7XQzavgKVZJcR0gNgDHGVYavzT/ODlX21abTNr+pU7GQa x3gg==
X-Gm-Message-State: AElRT7FRiTwuX7/blTl6F19Gy6q5g4aEd6q/klwZPgD61TaLnGUqjnEm 2ZkvM6Imhs87e7xe/yEcsIEzG2do9vuSAanihhKBVw==
X-Google-Smtp-Source: AG47ELu9FMbnybDVoEmk4Xx8OMEs9LbQFKY1CFR6domVAuqXcKLqXxUoETOFXnLsrANflgvLv2p/leRDdxMGynk+cDU=
X-Received: by 10.46.2.11 with SMTP id 11mr17522679ljc.0.1520461340725; Wed, 07 Mar 2018 14:22:20 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.21.210 with HTTP; Wed, 7 Mar 2018 14:22:19 -0800 (PST)
In-Reply-To: <CABcZeBM5zvwYHCAEUi+Sg7zjLk5pFwTANXidHkZwstnpjHLezA@mail.gmail.com>
References: <152045215867.17597.99576332554022377.idtracker@ietfa.amsl.com> <CABCOCHTY0kkfvLT9AjM+9-rtoU30j1ijg8bkKG=iNJOzAH9nhw@mail.gmail.com> <CABcZeBM5zvwYHCAEUi+Sg7zjLk5pFwTANXidHkZwstnpjHLezA@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Wed, 7 Mar 2018 14:22:19 -0800
Message-ID: <CABCOCHTXy9HudR3XKS2u6fbi2Lyfr5WmTxMAn4P7cg=p6s+RnA@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.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="94eb2c1a67a81c09070566d9fe32"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/5PrM6DiyCCILSXEmD3mbATuQcw0>
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 22:22:26 -0000

On Wed, Mar 7, 2018 at 1:56 PM, Eric Rescorla <ekr@rtfm.com>; wrote:

>
>
> 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/stat
>>> ement/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?
>
>
I will add the period charater to the list



> -Ekr
>
>

Andy


>
>>
>>
>>>
>>>    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
>>
>>
>>
>