Re: [i2rs] Benoit Claise's Discuss on draft-ietf-i2rs-yang-l3-topology-14: (with DISCUSS)
Benoit Claise <bclaise@cisco.com> Thu, 14 December 2017 17:52 UTC
Return-Path: <bclaise@cisco.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73046128616; Thu, 14 Dec 2017 09:52:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 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, SPF_PASS=-0.001, URIBL_BLOCKED=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 WMfkSMDaDSkK; Thu, 14 Dec 2017 09:52:45 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF7D612704A; Thu, 14 Dec 2017 09:52:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15230; q=dns/txt; s=iport; t=1513273964; x=1514483564; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=5+GnoQ3QxIY5Fmb5AyWyYpYC6i/ie8GHBUHJs5a24VA=; b=Oj3GLB3bY1Axqp1r8wcCEFFZnejjfN4IXKDsvQ7wYfzJvTHEi38x/tMq HR+swElxqfffLvHdVZ5H1IW1ff8hUJOOggZSNU7D/443NWROaHHi/Ys7i +hmZKcNY2qMr2g1aM8zItEv+bRmKdYhaaTo3GTiLKe4t3fPiEQd1YYhks Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BCAwBiuTJa/xbLJq1DGhkBAQEBAQEBAQEBAQEHAQEBAQGEJHQnhAKLFY9gL36QSoVOFIIBChgBDIUWAoU4FgEBAQEBAQEBAWsohSMBAQEBAwEBIUsLDAQLDgMEAQEBJwMCAicfCQgGAQwGAgEBiiYQNKhvgicmijcBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYNlg2SBaSmCTDaDLgEBF4EjARIBgzSCYwWKS4dKkRCHfY0tghaGEoNsh1iNFYFXiAGBOyYBMRFPVgIWMhoIGxU6gimCUxwZgU9ANwGIHII5AQEB
X-IronPort-AV: E=Sophos;i="5.45,400,1508803200"; d="scan'208,217";a="862723"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Dec 2017 17:52:41 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id vBEHqeJs024255; Thu, 14 Dec 2017 17:52:41 GMT
To: Martin Bjorklund <mbj@tail-f.com>, ludwig@clemm.org
Cc: iesg@ietf.org, draft-ietf-i2rs-yang-l3-topology@ietf.org, i2rs@ietf.org, i2rs-chairs@ietf.org, shares@ndzh.com
References: <151325119823.6222.15937797893027104434.idtracker@ietfa.amsl.com> <037301d374fb$321cfc10$9656f430$@clemm.org> <20171214.184217.2108989131786731949.mbj@tail-f.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <75ac9315-3e6b-949a-28c1-80b6001710ce@cisco.com>
Date: Thu, 14 Dec 2017 18:52:40 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <20171214.184217.2108989131786731949.mbj@tail-f.com>
Content-Type: multipart/alternative; boundary="------------65907D33C333C0CA06D4C99D"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/BiCBsGMYGIFTNQO-GAU4fY-s9rI>
Subject: Re: [i2rs] Benoit Claise's Discuss on draft-ietf-i2rs-yang-l3-topology-14: (with DISCUSS)
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 17:52:47 -0000
On 12/14/2017 6:42 PM, Martin Bjorklund wrote: > Hi, > > "Alexander Clemm" <ludwig@clemm.org> wrote: >> Hi Benoit, >> >> I am not sure I understand your comment? > I think the issue is that the leaf-list router-id should be of type > yang:dotted-quad, and not inet:ip-address. Right, imported from ietf-routing-types, in https://tools.ietf.org/html/draft-ietf-rtgwg-routing-types-17 typedef router-id { type yang:dotted-quad; description "A 32-bit number in the dotted quad format assigned to each router. This number uniquely identifies the router within an Autonomous System."; } Regards, Benoit > >> I was referring to the typedef >> router-id, which we define in example-ospf-topology. > There is no such typedef. There's an area-id though. > > > /martin > > > We made many changes >> to make it clear that this is just an example, not a part of the actual >> model, reflected in the description, naming, removal of contact and revision >> information, etc. >> >> The tree diagram in section 5 is for the ietf-l3-unicast-topology module. >> It is not part of an example. The same is true for the grouping >> l3-node-attributes. It is part of the model. >> >> The example-ospf-topology model serves as an example as to how the model >> might be refined/extended for other topologies. As stated: "This module is >> intended to serve as an example that illustrates how the general topology >> model can be refined across multiple levels." The sentence at the top of >> the section "Extending the model - Example OSPF Topology - Model Overview" >> states (slightly rephrased with inserted ", in this case") to "The following >> model shows how the Layer 3 Unicast topology model can be extended, in this >> case to cover OSFP topologies." >> >> Does this clarify or did you mean something else? >> >> Thanks >> --- Alex >> >> -----Original Message----- >> From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Benoit Claise >> Sent: Thursday, December 14, 2017 3:33 AM >> To: The IESG <iesg@ietf.org> >> Cc: draft-ietf-i2rs-yang-l3-topology@ietf.org; i2rs@ietf.org; >> i2rs-chairs@ietf.org; shares@ndzh.com >> Subject: [i2rs] Benoit Claise's Discuss on >> draft-ietf-i2rs-yang-l3-topology-14: (with DISCUSS) >> >> Benoit Claise has entered the following ballot position for >> draft-ietf-i2rs-yang-l3-topology-14: Discuss >> >> 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/statement/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-i2rs-yang-l3-topology/ >> >> >> >> ---------------------------------------------------------------------- >> DISCUSS: >> ---------------------------------------------------------------------- >> >> We're making progress. Thanks. >> >>>> 4. >>>> >>>> leaf-list router-id { >>>> type inet:ip-address; >>>> description >>>> "Router-id for the node"; >>>> } >>>> >>>> My initial DISCUSS was: We don't want to wait for >>>> https://tools.ietf.org/html/draft-ietf-rtgwg-routing-types-00 (btw, >>>> we should expedite this publication), but any good reason why this is >>>> aligned with its definition? >>>> typedef router-id { >>>> type yang:dotted-quad; >>>> description >>>> "A 32-bit number in the dotted quad format assigned to each >>>> router. This number uniquely identifies the router within an >>>> Autonomous System."; >>>> } >>>> >>>> My NEW DISCUSS: since is in IETF LC and on the telechat on Oct 12th, >>>> it makes sense to import its router-id >>> <ALEX> This is only used in the example. The point of the example is >>> to show how the model can be extended, not to define something >>> normative, hence I don't think there is a need to introduce a >>> dependency here which would only be distracting. >>> </ALEX> >> Can you help me understand how this is an example? >> Section 5 >> >> module: ietf-l3-unicast-topology >> augment /nw:networks/nw:network/nw:network-types: >> +--rw l3-unicast-topology! >> augment /nw:networks/nw:network: >> +--rw l3-topology-attributes >> +--rw name? string >> +--rw flag* l3-flag-type >> augment /nw:networks/nw:network/nw:node: >> +--rw l3-node-attributes >> +--rw name? inet:domain-name >> +--rw flag* node-flag-type >> +--rw router-id* inet:ip-address >> +--rw prefix* [prefix] >> +--rw prefix inet:ip-prefix >> +--rw metric? uint32 >> +--rw flag* prefix-flag-type >> >> And section 6: >> >> grouping l3-node-attributes { >> description "L3 node scope attributes"; >> container l3-node-attributes { >> description >> "Containing node attributes"; >> leaf name { >> type inet:domain-name; >> description >> "Node name"; >> } >> leaf-list flag { >> type node-flag-type; >> description >> "Node flags"; >> } >> leaf-list router-id { >> type inet:ip-address; >> description >> "Router-id for the node"; >> } >> list prefix { >> key "prefix"; >> description >> "A list of prefixes along with their attributes"; >> uses l3-prefix-attributes; >> } >> } >> } >> >> A different view at >> https://www.yangcatalog.org/yang-search/yang_tree.php?module=ietf-l3-unicast >> -topology# >> >> >> >> >> _______________________________________________ >> i2rs mailing list >> i2rs@ietf.org >> https://www.ietf.org/mailman/listinfo/i2rs >> >> _______________________________________________ >> i2rs mailing list >> i2rs@ietf.org >> https://www.ietf.org/mailman/listinfo/i2rs >> > . >
- [i2rs] Benoit Claise's Discuss on draft-ietf-i2rs… Benoit Claise
- Re: [i2rs] Benoit Claise's Discuss on draft-ietf-… Alexander Clemm
- Re: [i2rs] Benoit Claise's Discuss on draft-ietf-… Martin Bjorklund
- Re: [i2rs] Benoit Claise's Discuss on draft-ietf-… Benoit Claise
- Re: [i2rs] Benoit Claise's Discuss on draft-ietf-… Alexander Clemm
- Re: [i2rs] Benoit Claise's Discuss on draft-ietf-… Alexander Clemm
- Re: [i2rs] Benoit Claise's Discuss on draft-ietf-… Benoit Claise