Fwd: I-D Action: draft-rtgyangdt-rtgwg-device-model-03.txt

Lou Berger <lberger@labn.net> Wed, 24 February 2016 02:40 UTC

Return-Path: <lberger@labn.net>
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 9CB811B3AF6 for <rtgwg@ietfa.amsl.com>; Tue, 23 Feb 2016 18:40:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.666
X-Spam-Level:
X-Spam-Status: No, score=-1.666 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, WEIRD_PORT=0.001] 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 iKVoYfqZK-Cr for <rtgwg@ietfa.amsl.com>; Tue, 23 Feb 2016 18:40:38 -0800 (PST)
Received: from gproxy6-pub.mail.unifiedlayer.com (gproxy6-pub.mail.unifiedlayer.com [67.222.39.168]) by ietfa.amsl.com (Postfix) with SMTP id 367921B3A58 for <rtgwg@ietf.org>; Tue, 23 Feb 2016 18:40:38 -0800 (PST)
Received: (qmail 30791 invoked by uid 0); 24 Feb 2016 02:40:36 -0000
Received: from unknown (HELO cmgw3) (10.0.90.84) by gproxy6.mail.unifiedlayer.com with SMTP; 24 Feb 2016 02:40:36 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw3 with id N9gV1s00j2SSUrH019gYjW; Wed, 24 Feb 2016 02:40:33 -0700
X-Authority-Analysis: v=2.1 cv=GOWbTI9K c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=N659UExz7-8A:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=jFJIQSaiL_oA:10 a=48vgC7mUAAAA:8 a=vxtsQUyxHT8Nuch2A6IA:9 a=4gg4L7XzfoXcKXWJ:21 a=_-FwKM5Wv9Nzml_x:21 a=pILNOxqGKmIA:10 a=jO5m9I1TzjoA:10 a=jM_x9b4JT8QA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:To:References:Subject; bh=VgcCccBH+zwswgMeZtydTpn6k9ZOYOAbvTKqRJb2JKk=; b=iS+2Rc7gjWlHb72B1IjmIdgAxQkjo7Ha0w1VfzlBsD6PpzYjfqaNM40BESN4CxA3/cUS4D+lgrktLwTGyChGfPvcwz2lNUXaQhQ3nvfxdKAIRKgRDddI04aVSZedH1Y4;
Received: from box313.bluehost.com ([69.89.31.113]:41549 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1aYPNQ-0003NB-4k; Tue, 23 Feb 2016 19:40:32 -0700
Subject: Fwd: I-D Action: draft-rtgyangdt-rtgwg-device-model-03.txt
References: <20160224022951.24025.69591.idtracker@ietfa.amsl.com>
To: Routing WG <rtgwg@ietf.org>
From: Lou Berger <lberger@labn.net>
X-Enigmail-Draft-Status: N1110
X-Forwarded-Message-Id: <20160224022951.24025.69591.idtracker@ietfa.amsl.com>
Message-ID: <56CD181B.3040307@labn.net>
Date: Tue, 23 Feb 2016 21:40:27 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <20160224022951.24025.69591.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/FoGZGD4G7c2Nz6KAsS7LiGrK8Vc>
Cc: Routing Area YANG Architecture DT <rtg-dt-yang-arch@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: Wed, 24 Feb 2016 02:40:39 -0000

Hello,
    This draft has been updated to use an emerging yang  capability
called 'schema-mount' [1] which translates to a significant
simplification.  To quote the draft:

   Schema Mount enables a dramatic simplification of the presented
   device model, particularly for "lower-end" devices which are unlikely
   to support multiple network instances or logical network elements.
   Should structural-mount/YSDL not be available, the more explicit tree
   structure presented in earlier versions of this document will need to
   be utilized.

As it looks like there will soon be a netmod WG draft on schema mount,
we think it's time to ask the WG to consider adopting our draft as a RTG
WG draft.

[1] There was a netmod interim on schema mount on Monday, see
http://etherpad.tools.ietf.org:9000/p/netmod-interim-20160222

Our slides from that meeting are available at
https://www.ietf.org/proceedings/interim/2016/02/22/netmod/slides/slides-interim-2016-netmod-1-1.pptx 
and it gives a brief overview of the current draft.

Lou (and co-authors)
-------- Forwarded Message --------
Subject: 	I-D Action: draft-rtgyangdt-rtgwg-device-model-03.txt
Date: 	Tue, 23 Feb 2016 18:29:51 -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-03.txt
	Pages           : 36
	Date            : 2016-02-23

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-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-rtgyangdt-rtgwg-device-model-03


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