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

Martin Bjorklund <mbj@tail-f.com> Tue, 24 January 2017 12:35 UTC

Return-Path: <mbj@tail-f.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 F1EED1295D5; Tue, 24 Jan 2017 04:35:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.1
X-Spam-Level:
X-Spam-Status: No, score=-5.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham 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 easFANpG4YdW; Tue, 24 Jan 2017 04:35:32 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 65DC11295D1; Tue, 24 Jan 2017 04:35:32 -0800 (PST)
Received: from localhost (unknown [173.38.220.36]) by mail.tail-f.com (Postfix) with ESMTPSA id 149761AE0402; Tue, 24 Jan 2017 13:35:31 +0100 (CET)
Date: Tue, 24 Jan 2017 13:35:29 +0100
Message-Id: <20170124.133529.2274781221200613254.mbj@tail-f.com>
To: shares@ndzh.com
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <029501d27637$456c9af0$d045d0d0$@ndzh.com>
References: <019c01d275c4$edf51f30$c9df5d90$@ndzh.com> <20170123.232555.71314888595817367.mbj@tail-f.com> <029501d27637$456c9af0$d045d0d0$@ndzh.com>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/zM2BOX3iqGcfaNg2QxhgSJkSiaE>
X-Mailman-Approved-At: Tue, 24 Jan 2017 09:42:14 -0800
Cc: i2rs@ietf.org, kwatsen@juniper.net, draft-ietf-i2rs-yang-l3-topology@ietf.org, j.schoenwaelder@jacobs-university.de, i2rs-chairs@ietf.org, nite@hq.sk, Kathleen.Moriarty.ietf@gmail.com, iesg@ietf.org, lberger@labn.net
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: Tue, 24 Jan 2017 12:35:34 -0000

"Susan Hares" <shares@ndzh.com> wrote:
> Martin: 
> 
> Your statement "One problem is that relying on the solution in
> draft-ietf-netmod-revised-datastores-00 is a bit premature - in fact, that
> document does not yet provide any details at all on the I2RS ephemeral data
> store." This statement is not what I understood from IETF 98 or the netmod
> ADs.   I guess your objection to this data model falls into Benoit Claise
> (AD) and the NETMOD folks to answer. 

Why do you think that I have any objection to
draft-ietf-netmod-revised-datastores-00.  Please re-read what I
wrote.

My objection regards your statement:

   1) I2RS Data models do not utilize the configuration data store, 

If this is true it needs to be clarified in the document.

After all these emails back and forth, it is still not clear whether
this statement is true or not.


/martin





> 
> Sue Hares 
> 
> -----Original Message-----
> From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Martin Bjorklund
> Sent: Monday, January 23, 2017 5:26 PM
> To: shares@ndzh.com
> Cc: i2rs@ietf.org; draft-ietf-i2rs-yang-l3-topology@ietf.org;
> j.schoenwaelder@jacobs-university.de; i2rs-chairs@ietf.org; nite@hq.sk;
> 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)
> 
> "Susan Hares" <shares@ndzh.com> wrote:
> > 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).
> 
> Not really; I ask for clarification.
> 
> > 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.?
> 
> One problem is that relying on the solution in
> draft-ietf-netmod-revised-datastores-00 is a bit premature - in fact, that
> document does not yet provide any details at all on the I2RS ephemeral
> datastore.
> 
> So I see two alternatives.  Either wait with these documents, or publish
> them with their datamodels as is (i.e., no new additional notes), for the
> existing protocols and architecure.  This would allow them to be implemented
> just like any other YANG data model.  This would mean that the normal YANG
> security considerations guidelines should be followed.
> 
> 
> 
> /martin
> 
> > 
> > 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
> > 
> > 
> 
> _______________________________________________
> i2rs mailing list
> i2rs@ietf.org
> https://www.ietf.org/mailman/listinfo/i2rs
>