Re: [Netconf] [Technical Errata Reported] RFC6536 (3862)
Martin Bjorklund <mbj@tail-f.com> Fri, 10 January 2014 13:40 UTC
Return-Path: <mbj@tail-f.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A615B1AE012 for <netconf@ietfa.amsl.com>; Fri, 10 Jan 2014 05:40:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level:
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
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 FgfW1NZXgzeW for <netconf@ietfa.amsl.com>; Fri, 10 Jan 2014 05:40:49 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [109.74.15.94]) by ietfa.amsl.com (Postfix) with ESMTP id EF6D61ADE72 for <netconf@ietf.org>; Fri, 10 Jan 2014 05:40:48 -0800 (PST)
Received: from localhost (138.162.241.83.in-addr.dgcsystems.net [83.241.162.138]) by mail.tail-f.com (Postfix) with ESMTPSA id 4C476240C11A; Fri, 10 Jan 2014 14:40:38 +0100 (CET)
Date: Fri, 10 Jan 2014 14:40:38 +0100
Message-Id: <20140110.144038.1958728126349068530.mbj@tail-f.com>
To: rfc-editor@rfc-editor.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <20140110133233.926097FC394@rfc-editor.org>
References: <20140110133233.926097FC394@rfc-editor.org>
X-Mailer: Mew version 6.5rc2 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: joelja@bogus.com, netconf@ietf.org, jernej.tuljak@mg-soft.com
Subject: Re: [Netconf] [Technical Errata Reported] RFC6536 (3862)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 13:40:50 -0000
Hi, This errata should be rejected. "\*" is equvalent to '\*'. \* in a double quoted string is not an escape sequence, which means that the characters are interpreted literally, i.e. the two characters \ followed by *. The same goes for errata 3863. /martin RFC Errata System <rfc-editor@rfc-editor.org> wrote: > The following errata report has been submitted for RFC6536, > "Network Configuration Protocol (NETCONF) Access Control Model". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata_search.php?rfc=6536&eid=3862 > > -------------------------------------- > Type: Technical > Reported by: Jernej Tuljak <jernej.tuljak@mg-soft.com> > > Section: 3.5.2. > > Original Text > ------------- > typedef matchall-string-type { > type string { > pattern "\*"; > } > description > "The string containing a single asterisk '*' is used > to conceptually represent all possible values > for the particular leaf using this data type."; > } > > Corrected Text > -------------- > typedef matchall-string-type { > type string { > pattern '\*'; > } > description > "The string containing a single asterisk '*' is used > to conceptually represent all possible values > for the particular leaf using this data type."; > } > > Notes > ----- > As per RFC6020, Section 6.1.3., a backslash within a double-quoted > string introduces a special character. The only valid escape sequences > inside a double-quoted YANG string are: \n, \t, \" and \. As \* is not > a valid escape sequence, a single quoted string should be used to > specify the offending pattern statement's argument. The quotes could > also be omitted. > > Instructions: > ------------- > This errata is currently posted as "Reported". If necessary, please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party (IESG) > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC6536 (draft-ietf-netconf-access-control-07) > -------------------------------------- > Title : Network Configuration Protocol (NETCONF) Access Control Model > Publication Date : March 2012 > Author(s) : A. Bierman, M. Bjorklund > Category : PROPOSED STANDARD > Source : Network Configuration > Area : Operations and Management > Stream : IETF > Verifying Party : IESG >
- [Netconf] [Technical Errata Reported] RFC6536 (38… RFC Errata System
- Re: [Netconf] [Technical Errata Reported] RFC6536… Martin Bjorklund
- Re: [Netconf] [Technical Errata Reported] RFC6536… Jernej Tuljak
- [Netconf] [Errata Verified] RFC6536 (3862) RFC Errata System