Re: Blog: YANG Really Takes Off in the Industry

t.p. <daedulus@btconnect.com> Wed, 10 December 2014 10:11 UTC

Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2DF51A6F04 for <ietf@ietfa.amsl.com>; Wed, 10 Dec 2014 02:11:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001] 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 ZuxzAOPHSvdT for <ietf@ietfa.amsl.com>; Wed, 10 Dec 2014 02:11:46 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0767.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::767]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73AB71A1A54 for <ietf@ietf.org>; Wed, 10 Dec 2014 02:11:46 -0800 (PST)
Received: from pc6 (86.184.63.126) by AM3PR07MB243.eurprd07.prod.outlook.com (10.242.18.142) with Microsoft SMTP Server (TLS) id 15.1.31.17; Wed, 10 Dec 2014 10:07:59 +0000
Message-ID: <014101d01461$292ad300$4001a8c0@gateway.2wire.net>
From: "t.p." <daedulus@btconnect.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <54770BA5.5060603@cisco.com> <809EFD2B-A845-46B7-A394-A9C9E5393CD5@piuha.net> <547874D6.1090001@cisco.com> <7890AE32-F7A9-4C32-9C3D-8251E70B1F29@lucidvision.com> <m2sigyhpxc.wl%randy@psg.com> <8BBBDF7F-00A0-44BD-AA64-DA7044D35012@lucidvision.com> <C51AC247-C16D-4452-874E-0D97BDB009EB@juniper.net> <547D0AEA.4020309@gmail.com> <0BFD0B22-EC45-473F-8E7A-7FB608B60E6F@juniper.net> <139D837E-F131-4791-A026-234699A7E617@nominum.com> <01f901d00ee4$3c077b40$4001a8c0@gateway.2wire.net> <FF42158A-AC42-4EBF-9FCB-1A3EF4162027@nominum.com> <00f601d013bd$a1d23900$4001a8c0@gateway.2wire.net> <822FFCEB-7848-484E-9231-9BFDA4B97672@nominum.com> <54874FFD.4010506@gmail.com>
Subject: Re: Blog: YANG Really Takes Off in the Industry
Date: Wed, 10 Dec 2014 10:07:44 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [86.184.63.126]
X-ClientProxiedBy: DB3PR05CA0025.eurprd05.prod.outlook.com (25.160.41.153) To AM3PR07MB243.eurprd07.prod.outlook.com (10.242.18.142)
X-Microsoft-Antispam: UriScan:;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:AM3PR07MB243;
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:AM3PR07MB243;
X-Forefront-PRVS: 0421BF7135
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(189002)(24454002)(13464003)(479174003)(377454003)(199003)(51704005)(1456003)(31966008)(77096005)(68736005)(77156002)(40100003)(62966003)(122386002)(97736003)(81816999)(99396003)(46102003)(50466002)(101416001)(92566001)(86362001)(21056001)(76176999)(81686999)(50986999)(89996001)(61296003)(62236002)(42186005)(44716002)(116806002)(47776003)(20776003)(4396001)(87976001)(106356001)(105586002)(1556002)(84392001)(64706001)(50226001)(66066001)(44736004)(33646002)(107046002)(14496001)(120916001)(23676002)(93886004)(110136001)(19580395003)(19580405001)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:AM3PR07MB243; H:pc6; FPR:; SPF:None; MLV:sfv; PTR:InfoNoRecords; MX:1; A:0; LANG:en;
X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:AM3PR07MB243;
X-OriginatorOrg: btconnect.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/mX20ICYYSGBGI-tXIxX7SZ0VwaI
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 10 Dec 2014 10:11:49 -0000

----- Original Message -----
From: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
To: "Ted Lemon" <Ted.Lemon@nominum.com>
Cc: "t.p." <daedulus@btconnect.com>; "IETF-Discussion list"
<ietf@ietf.org>
Sent: Tuesday, December 09, 2014 7:39 PM
> On 10/12/2014 03:54, Ted Lemon wrote:
> > On Dec 9, 2014, at 9:31 AM, t.p. <daedulus@btconnect.com> wrote:
> >> The expression that controls the permissible format of IPv6
addresses in
> >> yang-types is of this ilk.
> >> "       type string {
> >>         pattern '((:|[0-9a-fA-F]{0,4}):)([0-9a-fA-F]{0,4}:){0,5}'
> >>               + '((([0-9a-fA-F]{0,4}:)?(:|[0-9a-fA-F]{0,4}))|'
> >>               + '(((25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])\.){3}'
> >>               + '(25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])))'
> >>               + '(/(([0-9])|([0-9]{2})|(1[0-1][0-9])|(12[0-8])))';
> >>         pattern '(([^:]+:){6}(([^:]+:[^:]+)|(.*\..*)))|'
> >>               + '((([^:]+:)*[^:]+)?::(([^:]+:)*[^:]+)?)'
> >>               + '(/.+)'; "
> >> which was got wrong several times before it became what it is now
(which
> >> rings alarm bells for me).
> >
> > Wow, so there's no way to do this ABNF-style?
>
> In fairness, it took numerous attempts to get the ABNF for the text
> representation of IPv6 addresses right, with RFC 6874 being the latest
> twist (which, if I am not mistaken, is not covered by the above
> gobbledygook; at least, I don't see anything in there that seems
> equivalent to '"%25" ZoneID', but maybe I missed it).

Brian

The question of zone index did come up and it appears in RFC6991 which
has the

" ipv6-address type represents an IPv6 address in full, mixed,
shortened, and shortened-mixed notation.  The IPv6 address may include a
zone index, separated by a % sign."

as well as

"ipv6-address-no-zone ...
An IPv6 address without a zone index "

but whether we should be using a language to achieve such precise
control in the general case I am less sure of.

Tom Petch
>
>     Brian
>