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

Martin Bjorklund <mbj@tail-f.com> Tue, 24 November 2015 09:24 UTC

Return-Path: <mbj@tail-f.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 315881ACDCD; Tue, 24 Nov 2015 01:24:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level:
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001] 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 Nio71seakEIk; Tue, 24 Nov 2015 01:24:43 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id CD5FD1A9142; Tue, 24 Nov 2015 01:24:42 -0800 (PST)
Received: from localhost (unknown [173.38.220.62]) by mail.tail-f.com (Postfix) with ESMTPSA id D64961AE0987; Tue, 24 Nov 2015 10:24:41 +0100 (CET)
Date: Tue, 24 Nov 2015 10:24:41 +0100 (CET)
Message-Id: <20151124.102441.1278595679799542000.mbj@tail-f.com>
To: acee@cisco.com
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <D278C312.3EDF3%acee@cisco.com>
References: <D278C312.3EDF3%acee@cisco.com>
X-Mailer: Mew version 6.5 on Emacs 24.3 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/o_dJ-K-j9I-J_tI4eo9jjF2RdtQ>
Cc: rtg-yang-coord@ietf.org, rtg-dt-yang-arch@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 09:24:44 -0000

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
>