Re: [i2rs] Kathleen Moriarty's No Objection on draft-ietf-i2rs-yang-l3-topology-08: (with COMMENT)

"Susan Hares" <shares@ndzh.com> Mon, 23 January 2017 22:11 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35B011298CE; Mon, 23 Jan 2017 14:11:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Level:
X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845] autolearn=no autolearn_force=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 sNg_nINDmVKF; Mon, 23 Jan 2017 14:11:12 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1180126579; Mon, 23 Jan 2017 14:11:11 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.36.161.15;
From: Susan Hares <shares@ndzh.com>
To: 'Robert Varga' <nite@hq.sk>, 'Martin Bjorklund' <mbj@tail-f.com>
References: <000701d27594$28d12350$7a7369f0$@ndzh.com> <20170123.194721.1193117831378217486.mbj@tail-f.com> <010a01d275b0$183d7360$48b85a20$@ndzh.com> <20170123.212621.119545616051737472.mbj@tail-f.com> <afdfb4d3-0901-2ee0-8d87-f8f1aeeff37e@hq.sk>
In-Reply-To: <afdfb4d3-0901-2ee0-8d87-f8f1aeeff37e@hq.sk>
Date: Mon, 23 Jan 2017 17:06:04 -0500
Message-ID: <019c01d275c4$edf51f30$c9df5d90$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGvtLYzrkxhP8mTK1eafm2axwyjOwK6rYpQAgVFSKQCceLYywFHvL5+oUhObIA=
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/DWy0OcPV5bQif9ydPhL--2N4Opk>
Cc: i2rs@ietf.org, draft-ietf-i2rs-yang-l3-topology@ietf.org, j.schoenwaelder@jacobs-university.de, i2rs-chairs@ietf.org, Kathleen.Moriarty.ietf@gmail.com, iesg@ietf.org
Subject: Re: [i2rs] Kathleen Moriarty's No Objection on draft-ietf-i2rs-yang-l3-topology-08: (with COMMENT)
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jan 2017 22:11:13 -0000

Robert and Martin: 

I agree with Robert that the current implementations of the ODL topology
models are handled as part of the configuration data store with ephemeral
state.   I will point out that these implementation are pre-standards
implementations of the I2RS YANG Data model.  

While standardizing the topology data models, the I2RS WG have been asked to
align with the draft-ietf-netmod-revised-datastores-00.txt NETMOD WG
document.  This NETMOD WG document moves the I2RS ephemeral data store from
configuration data store to a Control Plane data store.   If we follow this
draft, the I2RS Topology models are part of the I2RS ephemeral data store.
If you disagree with the placement of the Topology data models, please
indicate this to the NETMOD WG and to Benoit.  Could you propose a way that
you would see the ephemeral state working with the configuration data store
to the NETMOD WG?   

Quite frankly, I feel a bit of whip-lash on this topic.   NETMOD WG asks for
Control Plane Data store.  You ask for configuration data store (which was
the I2RS initial proposal).   It is possible for either one to work for I2RS
Topology models - if the right details are taken care of.   How do we make
progress on choosing one method so we can write the I2RS Topology Models
security considerations.? 

Sue 
  
-----Original Message-----
From: Robert Varga [mailto:nite@hq.sk] 
Sent: Monday, January 23, 2017 4:11 PM
To: Martin Bjorklund; shares@ndzh.com
Cc: i2rs@ietf.org; draft-ietf-i2rs-yang-l3-topology@ietf.org;
j.schoenwaelder@jacobs-university.de; i2rs-chairs@ietf.org;
Kathleen.Moriarty.ietf@gmail.com; iesg@ietf.org
Subject: Re: [i2rs] Kathleen Moriarty's No Objection on
draft-ietf-i2rs-yang-l3-topology-08: (with COMMENT)

On 01/23/2017 09:26 PM, Martin Bjorklund wrote:
>> I'm pulling your questions to the top of this email. 
>>
>>  
>>
>> Question 1: Ok.  Just to make sure I understand this correctly - 
>> these topology models are intended to be I2RS-specific, and they 
>> cannot be used for any other purpose.  If anyone needs a general 
>> topology model outside of the I2RS protocol, they will have to design 
>> their own model.  Is this correct?
>>
>>  
>>
>> Response 1:  Not really.  
> Ok, so are you saying that the models are in fact generic, and can be 
> used outside of I2RS?  I.e., they *can* be used with the normal 
> configuration datastores?
> 

>From implementation experience, yes, they can be used for storing
configuration. OpenDaylight uses (an ancient predecessor of)
yang-network-topo to store configure details about devices in its managed
networks.

Regards,
Robert