[Rtg-yang-coord] LIME connection-less draft-rtgyangdt-rtgwg-routing-types

Benoit Claise <bclaise@cisco.com> Mon, 14 November 2016 03:08 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: rtg-yang-coord@ietfa.amsl.com
Delivered-To: rtg-yang-coord@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABD5B129481; Sun, 13 Nov 2016 19:08:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.998
X-Spam-Level:
X-Spam-Status: No, score=-15.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 q0JkAv7Io9IO; Sun, 13 Nov 2016 19:08:40 -0800 (PST)
Received: from bgl-iport-1.cisco.com (bgl-iport-1.cisco.com [72.163.197.25]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DB5F1296B0; Sun, 13 Nov 2016 19:08:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6825; q=dns/txt; s=iport; t=1479092919; x=1480302519; h=to:subject:cc:from:message-id:date:mime-version; bh=vZbFfmkMvIirgZbgpu542xw7KEphZgXfj2+T6FFmEzY=; b=hGytFPH6zFPMOiB3+bM3+daX/X6GH81Q76ElkjmYTcj9f29/OFKTxrVk pwMv7y+Hm9miD1x5lSe1AtfiRc+Bi6g6cvkWW+s6MPAMYMnnqN2vWradD muxRlImFrj6ZLIxyFsygSD/OK3ewfaF5tu0Wc3dvDAbYar5PdIHe90JLG A=;
X-IronPort-AV: E=Sophos; i="5.31,488,1473120000"; d="scan'208,217"; a="65172031"
Received: from vla196-nat.cisco.com (HELO bgl-core-4.cisco.com) ([72.163.197.24]) by bgl-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Nov 2016 03:08:35 +0000
Received: from [10.79.99.134] ([10.79.99.134]) by bgl-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id uAE38WkF019111; Mon, 14 Nov 2016 03:08:33 GMT
To: draft-rtgyangdt-rtgwg-routing-types@ietf.org, "lime@ietf.org" <lime@ietf.org>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <7c9884b6-f786-22af-0ab1-5b410ae5237d@cisco.com>
Date: Mon, 14 Nov 2016 12:08:31 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------D8B6605389A02F29A7604FC0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-yang-coord/c4VyjkieMRJUX4gJo7J5-Yl6MIY>
Cc: "<rtg-ads@ietf.org>" <rtg-ads@ietf.org>, "Rtg-yang-coord@ietf.org" <rtg-yang-coord@ietf.org>, "Joe Clarke \(jclarke\)" <jclarke@cisco.com>
Subject: [Rtg-yang-coord] LIME connection-less draft-rtgyangdt-rtgwg-routing-types
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "\"List to discuss coordination between the Routing related YANG models\"" <rtg-yang-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-yang-coord/>
List-Post: <mailto:rtg-yang-coord@ietf.org>
List-Help: <mailto:rtg-yang-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2016 03:08:41 -0000

draft-rtgyangdt-rtgwg-routing-types authors,

I see the following typedef in draft-ietf-lime-yang-connectionless-oam

      typedef IPv4-Multicast-Group-Address {
             type string {
              pattern '(2((2[4-9])|(3[0-9]))\.)'
                          +'(([0-9]|[1-9][0-9]|1[0-9][0-9]|'
                          +'2[0-4][0-9]|25[0-5])\.){2}'
                          +'([0-9]|[1-9][0-9]|1[0-9][0-9]'
                          +'|2[0-4][0-9]|25[0-5])';
             }
             description
               "The IPv4-Multicast-Group-Address type
                represents an IPv4 multicast address
                in dotted-quad notation.";
             reference "RFC4607 <https://tools.ietf.org/html/rfc4607>";;
       } // typedef IPv4-Multicast-Group-Address
       typedef IPv6-Multicast-Group-Address {
             type string {
             pattern
                         '(((FF|ff)[0-9a-fA-F]{2}):)([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])))';
             pattern
             '(([^:]+:){6}(([^:]+:[^:]+)|'
                         +'(.*\..*)))|((([^:]+:)*[^:]+)'
                         +'?::(([^:]+:)*[^:]+)?)';
              }
             description
                         "The IPv6-Multicast-Group-Address
                         type represents an IPv6 address in full,
                         mixed, shortened, and shortened-mixed
                         notation.";
             reference "RFC4291 <https://tools.ietf.org/html/rfc4291>  2.7.
             ietf-inet-types:ipv6-address";
       }
       typedef IP-Multicast-Group-Address {
             type union {
               type IPv4-Multicast-Group-Address;
               type IPv6-Multicast-Group-Address;
             }

             description
              "The IP-Multicast-Group-Address type
               represents an IP multicast address and
               is IP version neutral. The format of the
               textual representations implies the IP version.";
       } // typedef IP-Multicast-Group-Address


It's probably a good idea to introduce those typedefs in your draft, for 
everybody's interest.
Now, hopefully, your draft will be published very soon. We can't delay 
other doc publications.

Also, look at this new tool, developed during this hackathon (new tool, 
so bare with us): http://yangcatalog.org/yang-search/yang-search.php
You should do a couple of searches with specific keywords.
For example, I searched on "multicast" and typedef.
     Note: we get some hits from YANG modules generated from MIB. Not 
sure how useful that is.
We want to make sure there are no discrepancies in the typedef, and that 
the typedef definitions are not spread around in too many documents.

Regards, Benoit