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

"Acee Lindem (acee)" <acee@cisco.com> Mon, 23 November 2015 18:20 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 8B8461ACD10; Mon, 23 Nov 2015 10:20:26 -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 4GXx5cfeS6oS; Mon, 23 Nov 2015 10:20:23 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C9181ACD08; Mon, 23 Nov 2015 10:20:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=892; q=dns/txt; s=iport; t=1448302823; x=1449512423; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=B71y949k/FXuMkLGtJkhT2HQdZfkbrpPVXGzf/b9T34=; b=YvuoR+vfrdILs60k/VC/ADNi1qrAom2pNAd9bL4DqNq21jrdAnILFADS /p/3+ylqpKiFuayCblCamEEkiETU/G/82ffs4KYzQoeu/9sOtoDGwJYgi da5VIabOz94mUPSo9vQ+s0nooZBHuZvkvePBty5WgITPHcNQ8udLxG2Zh s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D8AQCLV1NW/4sNJK1egztTbwa/GAENgWUhhW4egSs4FAEBAQEBAQGBCoQ3BCMRRRIBIgImAgQwFRIEDogzDa8AkA0BAQEBAQEBAQEBAQEBAQEBAQEXBIEBkkaBRAWWUAGNMJxKAR8BAUKEBHIBhCOBBwEBAQ
X-IronPort-AV: E=Sophos;i="5.20,338,1444694400"; d="scan'208";a="49514341"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 23 Nov 2015 18:20:22 +0000
Received: from XCH-RTP-014.cisco.com (xch-rtp-014.cisco.com [64.101.220.154]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id tANIKLKF031350 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 23 Nov 2015 18:20:22 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; Mon, 23 Nov 2015 13:20:21 -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; Mon, 23 Nov 2015 13:20:21 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: NETMOD WG <netmod@ietf.org>
Thread-Topic: draft-ietf-netmod-routing-cfg
Thread-Index: AQHRJhudyOc8SOAKk0S6HrhFMaX1uw==
Date: Mon, 23 Nov 2015 18:20:21 +0000
Message-ID: <D278C312.3EDF3%acee@cisco.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: <2245822C6243A145B8F426F7E8A4F84F@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/bnnGK15TNz9U3XsLzol8BF18YJQ>
Cc: Routing YANG <rtg-yang-coord@ietf.org>, RTG YANG Design Team <rtg-dt-yang-arch@ietf.org>
Subject: [Rtg-yang-coord] 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: Mon, 23 Nov 2015 18:20:26 -0000

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