Re: [Rtg-yang-coord] [netmod] draft-ietf-netmod-routing-cfg

"Acee Lindem (acee)" <acee@cisco.com> Tue, 24 November 2015 20:30 UTC

Return-Path: <acee@cisco.com>
X-Original-To: rtg-yang-coord@ietfa.amsl.com
Delivered-To: rtg-yang-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33F6D1A8979; Tue, 24 Nov 2015 12:30:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.086
X-Spam-Level:
X-Spam-Status: No, score=-15.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 Q2lHb58WI1EV; Tue, 24 Nov 2015 12:30:47 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74CAE1A8953; Tue, 24 Nov 2015 12:30:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2718; q=dns/txt; s=iport; t=1448397047; x=1449606647; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=FdBGIfQ4KqvDpNYeQ+bkgpMEwNouci+L+3hAWKnPJF0=; b=mkwLrlbVSF99RORM//ZHM96DmDuqEx5RDSRaXbvgVUFbwP15ydKo7guD 91AwIn0tYbEsvmNAG8ww/gNewClZCZ3HwxrqCaAeUad5hz2RhApebu21C tC1ANKx+9tJkgUjiWgUuHPy5tv0fjV6Ka1cFgMfBL+jCMmSrD4UOHhbEM c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D7AQCvx1RW/4cNJK1egztTbwa+OAENg?= =?us-ascii?q?WcXCoUkSgIcgSc4FAEBAQEBAQGBCoQ1AQEEAQEBIBE6CxACAQgOCgICJgICAiU?= =?us-ascii?q?LFRACBA4FiC4NrXKQJgEBAQEBAQEBAQEBAQEBAQEBAQEBARQEgQGKUYRZgxyBR?= =?us-ascii?q?AWNIYk0AYUkiA2cVwEfAQFChARyAYQkgQcBAQE?=
X-IronPort-AV: E=Sophos;i="5.20,339,1444694400"; d="scan'208";a="53587896"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 24 Nov 2015 20:30:46 +0000
Received: from XCH-RTP-014.cisco.com (xch-rtp-014.cisco.com [64.101.220.154]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id tAOKUkue015243 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 24 Nov 2015 20:30:46 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-014.cisco.com (64.101.220.154) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 24 Nov 2015 15:30:46 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1104.000; Tue, 24 Nov 2015 15:30:45 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Martin Bjorklund <mbj@tail-f.com>
Thread-Topic: [netmod] draft-ietf-netmod-routing-cfg
Thread-Index: AQHRJpn047JQ40dIlkSrKyodTLwzgp6roMYA
Date: Tue, 24 Nov 2015 20:30:45 +0000
Message-ID: <D27A2EC8.3F0A6%acee@cisco.com>
References: <D278C312.3EDF3%acee@cisco.com> <20151124.102441.1278595679799542000.mbj@tail-f.com>
In-Reply-To: <20151124.102441.1278595679799542000.mbj@tail-f.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.196]
Content-Type: text/plain; charset="utf-8"
Content-ID: <11BA6BE841045740A60A50539C8EF341@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/--F7JDoYzB6vuUrS7tltPkhw4zU>
Cc: "rtg-yang-coord@ietf.org" <rtg-yang-coord@ietf.org>, "rtg-dt-yang-arch@ietf.org" <rtg-dt-yang-arch@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
Subject: Re: [Rtg-yang-coord] [netmod] draft-ietf-netmod-routing-cfg
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 24 Nov 2015 20:30:49 -0000

Hi Martin,
 
I think using the more generic term, “networking”, at the top would be
preferable. What we need is an instance abstraction that covers L3 (e.g.,
virtual router or VRF), L2 (e.g., Virtual Switch Instance), or a
combination (some EVPN, TRILL, etc). This could be used in lieu of each L2
model creating their own top separate list of instances. For example, the
networking-instance could be augmented with both the VPLS and VPWS
instances in https://tools.ietf.org/html/draft-shah-bess-l2vpn-yang-00.

Some YANG models ascribe greatness from the start, others achieve
greatness through refinement, while still others have greatness thrust
upon them. routing-cfg would fall into the last category…

Thanks,
Acee 

On 11/24/15, 4:24 AM, "Martin Bjorklund" <mbj@tail-f.com>; wrote:

>Hi,
>
>"Acee Lindem (acee)" <acee@cisco.com>; wrote:
>> We had a lot of good discussions at IETF 94 with respect to the
>> ietf-routing and how it could be augmented in the future to support
>>I2RS.
>> These discussions are ongoing.
>> 
>> One current change that I would like to propose is to change the base
>> instance container from routing-instance to networking-instance.
>
>Is the idea to simply rename the "routing-instance" container to
>"networking-instance"?
>
>Then we would have:
>
>   +--rw routing
>      +--rw networking-instance
>
>Would you keep the top-level name "routing"?
>
>
>
>
>/martin
>
>
>
>
>> This
>> would provide an instance definition that could be augmented for L2
>> protocols and service functionality as well as L3. It is also consistent
>> with the term used in both
>> https://www.ietf.org/id/draft-rtgyangdt-rtgwg-device-model-01.txt and
>> https://www.ietf.org/id/draft-openconfig-rtgwg-network-instance-01.txt.
>> 
>> Thanks,
>> Acee 
>> 
>> _______________________________________________
>> netmod mailing list
>> netmod@ietf.org
>> https://www.ietf.org/mailman/listinfo/netmod
>>