Re: WG Adoption for "RIB YANG Data Model" - draft-acee-rtgwg-yang-rib-extend
tom petch <ietfa@btconnect.com> Thu, 07 March 2019 12:48 UTC
Return-Path: <ietfa@btconnect.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D70413139D; Thu, 7 Mar 2019 04:48:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.247
X-Spam-Level:
X-Spam-Status: No, score=0.247 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RATWARE_MS_HASH=2.148, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 sWNAaWuBd-hC; Thu, 7 Mar 2019 04:48:32 -0800 (PST)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-eopbgr130133.outbound.protection.outlook.com [40.107.13.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D395131382; Thu, 7 Mar 2019 04:48:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=05vIK+VawlUwvtSz/IqNH/xuVIbweLb/P+2J327/f4U=; b=LUXb65Xxr+6g86og0mIsOidST0w/EVBtXehoMhJoRFU6YGpbS4EtTwTcCKUrQVDqaCLVC9VS2Lhn7NWMveL+w5GvCMKQj0uTUVqr2ZHhUCP2uae75310l90EjEx1WwWASseYmxlAlldCE9UQRaws4oU2JrMKFL+2V51On14RMpU=
Received: from DB6PR0701MB2885.eurprd07.prod.outlook.com (10.168.83.18) by DB6PR0701MB2437.eurprd07.prod.outlook.com (10.168.75.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1686.12; Thu, 7 Mar 2019 12:48:27 +0000
Received: from DB6PR0701MB2885.eurprd07.prod.outlook.com ([fe80::9d52:abd1:d9a0:3a18]) by DB6PR0701MB2885.eurprd07.prod.outlook.com ([fe80::9d52:abd1:d9a0:3a18%10]) with mapi id 15.20.1686.018; Thu, 7 Mar 2019 12:48:27 +0000
From: tom petch <ietfa@btconnect.com>
To: Yingzhen Qu <yingzhen.qu@huawei.com>, RTGWG <rtgwg@ietf.org>, Routing WG <rtgwg-chairs@ietf.org>, "draft-acee-rtgwg-yang-rib-extend@ietf.org" <draft-acee-rtgwg-yang-rib-extend@ietf.org>
Subject: Re: WG Adoption for "RIB YANG Data Model" - draft-acee-rtgwg-yang-rib-extend
Thread-Topic: WG Adoption for "RIB YANG Data Model" - draft-acee-rtgwg-yang-rib-extend
Thread-Index: AQHUyE5cvVjixJaHhEes1yA2EJbLnA==
Date: Thu, 07 Mar 2019 12:48:27 +0000
Message-ID: <068301d4d4e3$c4c693c0$4001a8c0@gateway.2wire.net>
References: <d352c810-1b50-4843-b86d-45f1e9d08257@Spark> <a95eb664-4a20-458d-a894-93693c9e31eb@Spark> <062101d4c84e$203a8f60$4001a8c0@gateway.2wire.net> <665E12AB-4872-4903-907F-C956E6568094@huawei.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: LO2P265CA0134.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:9f::26) To DB6PR0701MB2885.eurprd07.prod.outlook.com (2603:10a6:4:70::18)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfa@btconnect.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-mailer: Microsoft Outlook Express 6.00.2800.1106
x-originating-ip: [86.156.84.54]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b3dc39a9-4349-45b4-e8bf-08d6a2fb31b2
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7193020); SRVR:DB6PR0701MB2437;
x-ms-traffictypediagnostic: DB6PR0701MB2437:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <DB6PR0701MB243757E1346CAB6394C6549AA24C0@DB6PR0701MB2437.eurprd07.prod.outlook.com>
x-forefront-prvs: 096943F07A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(39860400002)(136003)(396003)(366004)(376002)(199004)(189003)(13464003)(102836004)(53546011)(7736002)(3846002)(97736004)(6246003)(26005)(25786009)(84392002)(81686011)(6506007)(476003)(52116002)(186003)(386003)(68736007)(76176011)(81816011)(1556002)(966005)(6116002)(62236002)(305945005)(2906002)(4720700003)(446003)(2501003)(486006)(99286004)(105586002)(106356001)(93886005)(110136005)(86362001)(71190400001)(8936002)(44736005)(66066001)(81156014)(50226002)(61296003)(6486002)(14454004)(5660300002)(9686003)(6306002)(86152003)(81166006)(229853002)(6512007)(8676002)(6436002)(256004)(14496001)(44716002)(53936002)(71200400001)(316002)(478600001)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB6PR0701MB2437; H:DB6PR0701MB2885.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1;
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-microsoft-exchange-diagnostics: 1;DB6PR0701MB2437;23:4i1ugh7lN6fyXFd561a/iEHHS+gu9boRimBpdhUENrFg8iQkOWytOKnZ+cgB2+b1Krmao1O23MwK6sx2t/ejF8uWFmRZSL0wGCqnEL37Q8ybEG8+r/CcWJhTbAPCmM07J+HyHFdRomxHupXdTpQimuOHfbLsJ0k9PArWjohSwelgx0yTgQBrLg9F/z2cC6hg8doazoG4yiUUzcopf3O9hMZ1q99vbVKebqJIwD/iXcsaHEr2QYw3VwyEVwwt4Ipu45NuJkpuNMhFiAg6B16ef/DkiaPjhZQzxLw2HdcQ29NgNJesLeIKsw2eFx6b8+y45tFZIpnWiI8So4KfcyodYGR72n/e1u8TPt5NWO7eBNw0vN51caEd1ii8s5idjmdcQvGKY1mwrlAfTZVCh6PrS4H4QQu79IUShngZWMMMkNAWqa6HVE/byWyFW3g0FNvVH9pp6Z7BRIpPhoP5UFPBDHUEPjU2Bfno2IjWQHOcsFrqW2cqNj14K4W15RHFZDXgR8KDExEhteA2WiaJaTI86o3n6oPML/nFRUSXVO8K6hdhLpR4oGqRuhvGay+aJb5rBbXnJh29w6/+ujUaYO2dxqGW6xk7Wz9ZMm6jXPlv8EHVb6NM/hGrM2OVOgMYRWpsL4toJCJo5GL4iRU4d07+SH56Q2a7lHImUzA3ONorPpvveGvTuL1N/u+ZVVrsrtKejtBwe2zFFGnfBnnEdZJ2+pxplZ3x89GFWuzRbklu0Cy6QSB/eYXh0WR9cwLMfW9ZFwfb8MbP+d2F04bfvL1tpRtYOEeIIgdBvChxPwS/nyDEPef5VPb057J1jdzMqQtgxuZIsca/mWsUYMaikxYrTzSvxeWdFNm4kp8b3Hqw7vus2GyhzQPIx925zg8VYVstTtzOQHfZVP5Fhe706rQZhW8U+mvfmBVannqHjZ+pr/migoV9D1H/zyVYGsP8sL4M8IMaZPSZuxvNre73OJ2hNLY1mEzjjkFilzM/SLnymUtIQ/a/ZmqAJPNI0ijWYZJKDwMjCqziILBQw3qQDiVjYyl6A7iegoJnUvvQbtD5QHHpWvobBop9v8JmGbfx6SR93tGEEjLAWCLEQ8zWVNJe54qptuxaQVrcVKnJuzemVwO6fTlsJf28WCoblM3odEN+sWvK/DHGEbojUVTGeLMejpoAhfdFPLglOJ8KeoKGHFLUN5dqcUw88XS+18edZQ/AjBj9EyKnAMT/rCO77i9GG4LwoKO9mltWmj1cBgeRkoJviBCpPaHr8Ocqx3vOi6RdfSI5RzweWl4kTlYNJ0iXG4HD9MycnIQvSgyzMb9evQZ118n/+v5ObGZosLs4/MA58n9I/BzTzc4qLt9xtvsJbXMWL7GGdOfLdinl7O/Mvw1ZSG//Kt818GM34pHgUYWq25haf3uO7e9CidNg6DJkb+wKs9XGzA/GQtQmhYTAPNE1XRVRUxsuSrP1Druoqe4brLxDPCHRLpiDL5yDcWPxM3UEv23h99HN05roNYJCOZf/j6TAZLunCsh0frrV0dmNqUf9OOpPR2k4qGLZvg4htg==
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: d5jJClL5kg74vqIdrfD0MO/jeZWNO32FfOhW76Yu0rrKHYasQ8NeSJbByZtV9R7YWuToyF4MGWhz7Cc3eTRjoULlQS2tPUY8cr3LjiWs5or4Jxjp/dM0Dz3Rr7MuarYqBH6NdbwCzar2b0YT1+Mpn0QimJ2gwwzhvMVbYDLskIjPhWGMy6YfRhjxgr44TrDMJO4pKdYug1oUpklmGlCMhydi+5dHJuYbJDeOxX7XwicasKe9xDx7kUpFk5iS+qoJe6GNUFNWMQ/TAw3jy11QgapdT5JpfWHUAkwYhmFsy7NR2nlgXaw24YmGM9bYtvkM/1v5NZnLGVlCje4G5DXfjEAUzxY7Aq0PKp+CmvaMUFfz7VSy1Yw9hoqQ6PW2zAH0Dc91jwFY4IERQlZSylH99Gc21mjfkiF0ro2SbTjyfUA=
Content-Type: text/plain; charset="utf-8"
Content-ID: <DF30D3AA714D284699CFFE5154EE8226@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b3dc39a9-4349-45b4-e8bf-08d6a2fb31b2
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Mar 2019 12:48:27.6485 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0701MB2437
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/hrlggJadFkU0Ayso_fhQ0wAFYdM>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Mar 2019 12:48:33 -0000
Yimgzhen Looking at draft-ietf-rtgwg-yang-rib-extend I would like a reference for FRR since the current text confused me; I have also responded to Acee about this. I would like a reference for description "Additional Application-Specific Route tag"; as I do not know what you mean:-( The YANG import statements need reference clauses e.g. import ietf-inet-types { prefix inet; reference "RFC6991: Common YANG Data Types"; } /Ipv4/IPv4/ name: ietf-acl namespace: urn:ietf:params:xml:ns:yang:ietf-rib- extension prefix: ietf-rib-ext reference: RFC XXXX puzzles me Tom Petch ----- Original Message ----- From: "Yingzhen Qu" <yingzhen.qu@huawei.com> Sent: Monday, March 04, 2019 9:09 PM > Hi Tom, > > Thanks for your review and comments. We have submitted version -10 to address your comments, please see my detailed response below starting with [YQ]. > > Thanks, > Yingzhen > > On 2/19/19, 4:26 AM, "tom petch" <ietfa@btconnect.com> wrote: > > Two uncertainties strike me. > > One is terminology, which caused some discussion in the production of > the original YANG routing module. When I see the terminology used, e.g. > admin distance, I immediately think of one manufacturer so I wonder how > other manufacturers see it and would like to see their agreement that > the terminology makes sense for them (even if everyone here is of > course contributing as an individual). > [YQ]: We're still using "preference" consistent with RFC 8349. The term, "admin distance", is only included parenthetically for explanation. > > > More technically, I wonder at the specification of repair routes. One > thought is placement, it is described as > "Augment a route with a list of repair-paths."; > which is not strictly true since it augments > augment "/rt:routing/rt:ribs/rt:rib/" + "rt:routes" > i.e. the container and not a route therein (which is the case for the > augmentation with a tag). I am unsure where a list of repair routes > belongs in the schema - it seems to me that it could be anywhere. > [YQ]: this was done based on WG's suggestion (sorry, forgot who made it) to make the model "slim". The list of repair paths is at "routes" level with an "id", at each "route" level, a repair path is reference this "id". By doing so, if a bunch of routes are using the same repair path, so they can just reference the same id instead of repeating the whole repair path multiple times. > See below tree diagram for an example: > augment /rt:routing/rt:ribs/rt:rib/rt:routes: > +--ro repair-route* [id] > +--ro id string <--------- "id" is defined here. > +--ro next-hop > | +--ro outgoing-interface? if:interface-state-ref > | +--ro next-hop-address? inet:ip-address > +--ro metric? uint32 > augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route > /rt:next-hop/rt:next-hop-options/rt:simple-next-hop: > +--ro repair-path? > -> /rt:routing/ribs/rib/routes/repair-route/id <-------------------referenced here. > > Related to this, is there any requirement for repair routes to exist or > be valid i.e.is this missing a few 'must' or such like statements? > [YQ]: repair path is optional, so no "must" statement is needed. > > While I am at it, the reference in the YANG module to RFC8242 should be > RFC8342 IMHO. And the YANG module is version 1.1 so the reference in > the Introduction must be RFC7950; I cannot understand this I-D using > only RFC6020. > [YQ]: fixed. > > Tom Petch > > > ----- Original Message ----- > From: "Jeff Tantsura" <jefftant.ietf@gmail.com> > To: "RTGWG" <rtgwg@ietf.org>; "Routing WG" <rtgwg-chairs@ietf.org>; > <draft-acee-rtgwg-yang-rib-extend@ietf.org> > Sent: Friday, February 15, 2019 7:18 PM > Subject: WG Adoption for "RIB YANG Data Model" - > draft-acee-rtgwg-yang-rib-extend > > > > Dear RTGWG, > > > > The authors have requested the RTGWG to adopt > draft-acee-rtgwg-yang-rib-extend > > as the working group documents. > > > > The authors have addressed the comments raised. > > > > Please indicate support or no-support by March 3rd, 2019. > > > > If you are listed as a document author or contributor please > > respond to this email stating of whether or not you are aware of > > any relevant IPR. The response needs to be sent to the RTGWG > > mailing list. The document will not advance to the next stage > > until a response has been received from each author and each > > individual that has contributed to the document. > > > > Cheers, > > Jeff > > > > > ------------------------------------------------------------------ ------ > -------- > > > > _______________________________________________ > > rtgwg mailing list > > rtgwg@ietf.org > > https://www.ietf.org/mailman/listinfo/rtgwg > > > > > >
- WG Adoption for "RIB YANG Data Model" - draft-ace… Jeff Tantsura
- Re: WG Adoption for "RIB YANG Data Model" - draft… Yingzhen Qu
- Re: WG Adoption for "RIB YANG Data Model" - draft… Acee Lindem (acee)
- Re: WG Adoption for "RIB YANG Data Model" - draft… Robert Wilton
- Re: WG Adoption for "RIB YANG Data Model" - draft… Acee Lindem (acee)
- Re: WG Adoption for "RIB YANG Data Model" - draft… tom petch
- Re: WG Adoption for "RIB YANG Data Model" - draft… Xufeng Liu
- Re: WG Adoption for "RIB YANG Data Model" - draft… Jeff Tantsura
- Re: WG Adoption for "RIB YANG Data Model" - draft… Yingzhen Qu
- Re: WG Adoption for "RIB YANG Data Model" - draft… tom petch
- Re: WG Adoption for "RIB YANG Data Model" - draft… Acee Lindem (acee)
- Re: WG Adoption for "RIB YANG Data Model" - draft… tom petch
- Re: WG Adoption for "RIB YANG Data Model" - draft… tom petch