Re: [Gen-art] Review: draft-ietf-netmod-rfc6021-bis-01
Andy Bierman <andy@yumaworks.com> Fri, 10 May 2013 16:33 UTC
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81CD121F8F62 for <ietf@ietfa.amsl.com>; Fri, 10 May 2013 09:33:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.264
X-Spam-Level:
X-Spam-Status: No, score=0.264 tagged_above=-999 required=5 tests=[AWL=0.575, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_HTML_USL_OBFU=1.666]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z6P7y+40pkjU for <ietf@ietfa.amsl.com>; Fri, 10 May 2013 09:33:44 -0700 (PDT)
Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 91E7421F856D for <ietf@ietf.org>; Fri, 10 May 2013 09:33:43 -0700 (PDT)
Received: by mail-ie0-f169.google.com with SMTP id u16so8576206iet.28 for <ietf@ietf.org>; Fri, 10 May 2013 09:33:31 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=pZKSWoo6ZlL907/aB8fuu8COapNRykruAgrygBuWtvQ=; b=GKXH2BhpfVh0OxKKJMCWtnTZnr2bwVQ2o9aHYA/ugvrhLeS9Y3rXANpgCI5d8EXHgc +TnoXuLU4x8w6hntUYa5fMlBbquZ8cwfAxkjZ9mbf0Srs4MMyBpxGspK9qm57xqXoy1N lbY59nVMbXyUjQCzUfb0xojAxFH2CvwrvLtvjC8mNIUWqu6mgHQBdQ+Ut3+M2DDsvAsi yBB0o4+OJnEgIHnIS4UDXfCPqukEfpp3EiPpteuzq2ndCCe5Da7UaxwpPzioNJzMljM9 ZrSDSA2XQPLv/LMElMOm30NMKoXJCjl5XJuQMyNbM4B38Df7jJyX7nmgKnGOFInAQX7G uFRQ==
MIME-Version: 1.0
X-Received: by 10.50.120.4 with SMTP id ky4mr2430121igb.86.1368203611391; Fri, 10 May 2013 09:33:31 -0700 (PDT)
Received: by 10.231.125.202 with HTTP; Fri, 10 May 2013 09:33:31 -0700 (PDT)
In-Reply-To: <518D0635.7040301@joelhalpern.com>
References: <5170722E.2070401@nostrum.com> <5171C416.5070105@joelhalpern.com> <518D0635.7040301@joelhalpern.com>
Date: Fri, 10 May 2013 09:33:31 -0700
Message-ID: <CABCOCHT_YLzcNeo36yZA==JA+J0LzD1F0zfqnaTGgvixF47+MQ@mail.gmail.com>
Subject: Re: [Gen-art] Review: draft-ietf-netmod-rfc6021-bis-01
From: Andy Bierman <andy@yumaworks.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: multipart/alternative; boundary="047d7b8746d43ce00a04dc5fba57"
X-Gm-Message-State: ALoCoQn79PFzlBRvfJEb1wBzBH+rGXTZ97fIC+ltRuwVv3oCAx807vVJNo8zlrraNbxNmVOH3TCE
X-Mailman-Approved-At: Mon, 13 May 2013 07:02:22 -0700
Cc: gen-art@ietf.org, "A. Jean Mahoney" <mahoney@nostrum.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 May 2013 16:33:45 -0000
On Fri, May 10, 2013 at 7:37 AM, Joel M. Halpern <jmh@joelhalpern.com>wrote: > I am guessing that the authors intended the addition of the text > emphasizing that the no-zone typedefs are derived general typedef addresses > the difference in the patterns. > > Is there a YANG rule that says tat if typedef X is derived from typedef Y > then the string for X must match the pattern for X and the pattern for Y? > If so, then my concern below is misplaced. (The fact that I find the > vague pattern for the child misleading is not a fault with the document, > but rather in my head, under that requirement.) > Yes. RFC 6020, sec. 9.4.6. All the patterns are ANDed together. > > Yours, > Joel > > Andy > On 4/19/2013 6:24 PM, Joel M. Halpern wrote: > >> I am the assigned Gen-ART reviewer for this draft. For background on >> Gen-ART, please see the FAQ at >> >> <http://wiki.tools.ietf.org/**area/gen/trac/wiki/GenArtfaq<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq> >> >. >> >> Please resolve these comments along with any other Last Call comments >> you may receive. >> >> Document: draft-ietf-netmod-rfc6021-bis-**01 >> Common YANG Data Types >> Reviewer: Joel M. Halpern >> Review Date: 19-April-2013 >> IETF LC End Date: 1-May-2013 >> IESG Telechat date: N/A >> >> Summary: This document is nearly ready for publication as a Standards >> Track RFC >> >> Major issues: >> (The following may well be a non-issue.) >> In the revision of the ietf-inet-types, the patterns for the new >> ip4-address-no-zone and ipv6-address-no-zone are drastically simplified >> from the ipv4-address and ipv6-address patterns. The new >> ipv4-address-no-zone allows any sequence of decimal digits an periods, >> while the original was carefully defined as dotted quads of 0..255. >> Similarly, te ipv6-address-no-zone allows any arbitrary sequence of hex >> digits and colons. The original patterns were very careful to match >> rules for validity. Is there a reason for the change. >> >> Minor issues: >> >> Nits/editorial comments: >> ______________________________**_________________ >> Gen-art mailing list >> Gen-art@ietf.org >> https://www.ietf.org/mailman/**listinfo/gen-art<https://www.ietf.org/mailman/listinfo/gen-art> >> >>
- [Gen-art] Review: draft-ietf-netmod-rfc6021-bis-01 Joel M. Halpern
- Re: [Gen-art] Review: draft-ietf-netmod-rfc6021-b… Joel M. Halpern
- Re: [Gen-art] Review: draft-ietf-netmod-rfc6021-b… Benoit Claise
- Re: [Gen-art] Review: draft-ietf-netmod-rfc6021-b… Benoit Claise
- Re: [Gen-art] Review: draft-ietf-netmod-rfc6021-b… Juergen Schoenwaelder
- Re: [Gen-art] Review: draft-ietf-netmod-rfc6021-b… Joel M. Halpern
- Re: [Gen-art] Review: draft-ietf-netmod-rfc6021-b… Andy Bierman