Re: I-D Action: draft-rtgyangdt-rtgwg-device-model-02.txt
Christian Hopps <chopps@chopps.org> Fri, 26 February 2016 19:30 UTC
Return-Path: <chopps@chopps.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80DDD1B2EE9 for <rtgwg@ietfa.amsl.com>; Fri, 26 Feb 2016 11:30:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.305
X-Spam-Level:
X-Spam-Status: No, score=-1.305 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, RP_MATCHES_RCVD=-0.006] autolearn=no
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 SRZ6O6eYtsV5 for <rtgwg@ietfa.amsl.com>; Fri, 26 Feb 2016 11:30:56 -0800 (PST)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 29ED51A6F3C for <rtgwg@ietf.org>; Fri, 26 Feb 2016 11:30:56 -0800 (PST)
Received: from [192.168.1.5] (24-247-68-31.dhcp.trcy.mi.charter.com [24.247.68.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 2C0E4609CF; Fri, 26 Feb 2016 19:30:55 +0000 (UTC)
Subject: Re: I-D Action: draft-rtgyangdt-rtgwg-device-model-02.txt
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Content-Type: multipart/signed; boundary="Apple-Mail=_E37D053B-3763-4E79-A802-14CC9D7F89EF"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail 2.6b2
From: Christian Hopps <chopps@chopps.org>
X-Priority: 3
In-Reply-To: <02f401d170bc$9d829b80$4001a8c0@gateway.2wire.net>
Date: Fri, 26 Feb 2016 14:30:54 -0500
Message-Id: <5E231DE4-2C34-49AD-81F5-C7243721C288@chopps.org>
References: <20160122131607.8074.21335.idtracker@ietfa.amsl.com> <56C1E7B7.6020100@labn.net> <013701d1708e$d4804ca0$4001a8c0@gateway.2wire.net> <1531d87dec8.2818.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <02f401d170bc$9d829b80$4001a8c0@gateway.2wire.net>
To: "t.petch" <ietfa@btconnect.com>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/zPdQCZFo4xCH3ZJpOzLTG72adHk>
Cc: Routing WG <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 26 Feb 2016 19:30:59 -0000
> On Feb 26, 2016, at 12:29 PM, t.petch <ietfa@btconnect.com> wrote: > > ----- Original Message ----- > From: "Lou Berger" <lberger@labn.net <mailto:lberger@labn.net>> > To: "t.petch" <ietfa@btconnect.com <mailto:ietfa@btconnect.com>>; "Routing WG" <rtgwg@ietf.org <mailto:rtgwg@ietf.org>> > Sent: Friday, February 26, 2016 12:22 PM > >> Tom, >> >> I understand your comment wrt mount . I think it is fair to suggest > that >> having a net mod working group document on the topic be a gating item. > Stay >> tuned. This sad, I hope that we can continue the discussion and > identify >> any other possible issues for this working group. >> >> I don't understand how the opstate discussion ties in. Can you > elaborate? > > Lou > > section 1 > " The top open issues are: > > 1. The use of YSDL vs Structural Mount, i.e., a Netmod defined > Schema Mount solution, needs to be resolved as does ensuring that > the selected approach has the needed capabilities. This actually doesn't feel contentious to me. The 2 solutions are very similar, and in fact good progress was made at the most recent interim with the 2 authors agreeing to work together. I don't believe I've seen anyone objecting to the concept of a mount whichever form it takes on the mailing list either. > 2. This document will need to match the evolution and > standardization of [OC-OPSTATE] or [NETMOD-OPSTATE] by > the Netmod WG. We are simply stating the document needs to track the evolution of this. I don't believe there's anything in this draft that requires an opstate solution be chosen in order to review it. In fact if this were the case since op-state is targeted at *all* yang models, we would have to stop working on all models by this logic. :) Thanks, Chris. > ............. > " > Sounds like a Normative Reference to me (and as I said before, I still > see divergent views expressed on the Netmod WG list). > > Tom Petch > >> Thanks, >> Lou >> >> >> On February 26, 2016 7:15:36 AM t.petch <ietfa@btconnect.com> wrote: >> >>> Lou >>> >>> I think that it is difficult, perhaps impossible, to review this I-D >>> until the foundations on which it is based, mount and op-state, > become >>> firmer. >>> >>> I track the discussions on the netmod WG list (and have done so > since >>> before it existed!) and do not expect either of those two issues to >>> settle down in the immediate future. Some aspects of YANG get > agreed >>> quickly, others do not, and I see these two in the latter camp. >>> >>> So for me, the way to progress this I-D would be to join the netmod >>> list and advance those two topics. >>> >>> Tom Petch >>> >>> >>> ----- Original Message ----- >>> From: "Lou Berger" <lberger@labn.net> >>> To: "Routing WG" <rtgwg@ietf.org> >>> Sent: Monday, February 15, 2016 2:59 PM >>> >>> >>>> FYI - This has been out a little bit, but haven't seen any > comments. >>>> We'd definitely like to hear from the WG on this. >>>> >>>> quoting the draft: >>>> This version is a major >>>> change from the prior version and this change was enabled by the >>> work >>>> on the previously mentioned Structural Mount/YSDL. >>>> >>>> Note that an interim on Structural Mount/YSDL (which I think of >>>> generally as 'schema mount') has been scheduled by the netmod WG -- >>> see >>>> http://www.ietf.org/mail-archive/web/netmod/current/msg15257.html > and >>>> http://www.ietf.org/mail-archive/web/netmod/current/msg15260.html >>>> >>>> Lou >>>> >>>> -------- Forwarded Message -------- >>>> Subject: I-D Action: draft-rtgyangdt-rtgwg-device-model-02.txt >>>> Date: Fri, 22 Jan 2016 05:16:07 -0800 >>>> From: internet-drafts@ietf.org >>>> Reply-To: internet-drafts@ietf.org >>>> To: i-d-announce@ietf.org >>>> >>>> >>>> A New Internet-Draft is available from the on-line Internet-Drafts >>>> directories. >>>> >>>> >>>> Title : Network Device YANG Organizational Models >>>> Authors : Acee Lindem >>>> Lou Berger >>>> Dean Bogdanovic >>>> Christan Hopps >>>> Filename : draft-rtgyangdt-rtgwg-device-model-02.txt >>>> Pages : 36 >>>> Date : 2016-01-22 >>>> >>>> Abstract: >>>> This document presents an approach for organizing YANG models in > a >>>> comprehensive structure that may be used to configure and > operate >>>> network devices. The structure is itself represented as a YANG >>>> model, with all of the related component models logically > organized >>>> in a way that is operationally intuitive, but this model is not >>>> expected to be implemented. The identified component modules > are >>>> expected to be defined and implemented on common network > devices. >>>> >>>> This document also defines two modules that can be used to model >>> the >>>> logical and virtual resource representations that may be present > on >>> a >>>> network device. Examples of common industry terms for logical >>>> resource representations are Logical Systems or Routers. > Examples >>> of >>>> of common industry terms for virtual resource representations > are >>>> Virtual Routing and Forwarding (VRF) instances and Virtual > Switch >>>> Instances (VSIs). >>>> >>>> This document is derived from work submitted to the IETF by > members >>>> of the informal OpenConfig working group of network operators > and >>> is >>>> a product of the Routing Area YANG Architecture design team. >>>> >>>> >>>> The IETF datatracker status page for this draft is: >>>> > https://datatracker.ietf.org/doc/draft-rtgyangdt-rtgwg-device-model/ >>>> >>>> There's also a htmlized version available at: >>>> https://tools.ietf.org/html/draft-rtgyangdt-rtgwg-device-model-02 >>>> >>>> A diff from the previous version is available at: >>>> >>> > https://www.ietf.org/rfcdiff?url2=draft-rtgyangdt-rtgwg-device-model-02 >>>> >>>> >>>> Please note that it may take a couple of minutes from the time of >>> submission >>>> until the htmlized version and diff are available at > tools.ietf.org. >>>> >>>> Internet-Drafts are also available by anonymous FTP at: >>>> ftp://ftp.ietf.org/internet-drafts/ >>>> >>>> _______________________________________________ >>>> I-D-Announce mailing list >>>> I-D-Announce@ietf.org >>>> https://www.ietf.org/mailman/listinfo/i-d-announce >>>> Internet-Draft directories: http://www.ietf.org/shadow.html >>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt >>>> >>>> >>>> >>>> _______________________________________________ >>>> rtgwg mailing list >>>> rtgwg@ietf.org >>>> https://www.ietf.org/mailman/listinfo/rtgwg >>> >>> >> >> > > _______________________________________________ > rtgwg mailing list > rtgwg@ietf.org > https://www.ietf.org/mailman/listinfo/rtgwg
- Fwd: I-D Action: draft-rtgyangdt-rtgwg-device-mod… Lou Berger
- Re: I-D Action: draft-rtgyangdt-rtgwg-device-mode… t.petch
- Re: I-D Action: draft-rtgyangdt-rtgwg-device-mode… Lou Berger
- Re: I-D Action: draft-rtgyangdt-rtgwg-device-mode… t.petch
- Re: I-D Action: draft-rtgyangdt-rtgwg-device-mode… Christian Hopps
- Re: I-D Action: draft-rtgyangdt-rtgwg-device-mode… t.petch