IETF Logo Mail Archive

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

Andy Bierman <andy@yumaworks.com> Mon, 23 January 2017 21:40 UTC

Return-Path: <andy@yumaworks.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 EA03F1204D9 for <i2rs@ietfa.amsl.com>; Mon, 23 Jan 2017 13:40:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.com
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 LUI6YeEtdQaW for <i2rs@ietfa.amsl.com>; Mon, 23 Jan 2017 13:40:29 -0800 (PST)
Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::231]) (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 11DEB1298CC for <i2rs@ietf.org>; Mon, 23 Jan 2017 13:40:27 -0800 (PST)
Received: by mail-qk0-x231.google.com with SMTP id s140so56722514qke.0 for <i2rs@ietf.org>; Mon, 23 Jan 2017 13:40:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xObSJbfAnHGpzgJY0XHT2t3cl2FbgHw/56+TsB9YIMI=; b=dIcMwL++WGeTXxqNyjGDvBI5JyCdbpElaPYRHdm0xoU+ezsz/FMFCtF/BbCgHCsGFO 6548iaZvL7dz22r7bKRNbMoNRBUgACWh6Lx/Famva8vwrvxrKcTuU8Owmng8bx3ZWNcP FqZryb6BV48hEA5BSlzqN0Y1imthuBpQlki3o9YY3nMSPWSH6ZmMXkF7i4ixbjWWXKju c9Z+S6ZuVz9w3AYYIm1vINz4X8/c/uZ1aTT3esNnoDDmrM0w4JEvAtXxa9YyDt/xfDKp BWJWUZaQbZq75VdQ5H31j21Gjyqw/cAl7ju/AI4WT3HfZ9rGUoyGkHvSxGRlLHoZ5Nob kAVw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xObSJbfAnHGpzgJY0XHT2t3cl2FbgHw/56+TsB9YIMI=; b=opFAHGtdJzUZYCJub8ROExlZAXqjo8bRmVrRayAwbXxhs7dKli1QRdOdzODh54YT97 6Kw8ARIic8cSeYGZ4ebkIWgCo/wfcIxDkYJv+qVsL+9S8tDRVnXxxZ9CleXyC36QM4kN aFQlFF0vW13T60DByuHgG49AHXXhUyE941RDo03FNgIqhnlBeC1hw3WJS+1sJ4vtVbcp 30E3JmghjtD3havdeETDGg1gb1zIh+QZrzIxpePRRo79OsLwl4WKiL+trROTE0J6N+YU DM6j+AgNoPZWPXn3KjO9u/6bYe/TULQMbb+4vngLUkvG09U26vz34RoAcpALxJT1dUsj g2bw==
X-Gm-Message-State: AIkVDXIBE2naI44goblyls+B109rwzT7RaqKK9WZMWT6KPygq7WgB2QK1L3W1E7ydjNpvfpYUwNI4Aq0afi/Ow==
X-Received: by 10.55.135.197 with SMTP id j188mr26768877qkd.71.1485207626106; Mon, 23 Jan 2017 13:40:26 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.145.66 with HTTP; Mon, 23 Jan 2017 13:40:25 -0800 (PST)
In-Reply-To: <20170123.221951.1538450846109848280.mbj@tail-f.com>
References: <010a01d275b0$183d7360$48b85a20$@ndzh.com> <20170123.212621.119545616051737472.mbj@tail-f.com> <afdfb4d3-0901-2ee0-8d87-f8f1aeeff37e@hq.sk> <20170123.221951.1538450846109848280.mbj@tail-f.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Mon, 23 Jan 2017 13:40:25 -0800
Message-ID: <CABCOCHQG0LJXeX1-7m9ZD5=tU1bWofdDNE6NgOrWb+htXSsgqA@mail.gmail.com>
To: Martin Bjorklund <mbj@tail-f.com>
Content-Type: multipart/alternative; boundary="94eb2c0777e6f925c40546c9d888"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/8Ho2aZ1bipScNRQlFe-JAK8jO7k>
Cc: "i2rs@ietf.org" <i2rs@ietf.org>, draft-ietf-i2rs-yang-l3-topology@ietf.org, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, i2rs-chairs@ietf.org, Robert Varga <nite@hq.sk>, Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>, The IESG <iesg@ietf.org>, Susan Hares <shares@ndzh.com>
Subject: Re: [i2rs] Kathleen Moriarty's No Objection on draft-ietf-i2rs-yang-l3-topology-08: (with COMMENT), Re: 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 21:40:31 -0000

On Mon, Jan 23, 2017 at 1:19 PM, Martin Bjorklund <mbj@tail-f.com> wrote:

> Robert Varga <nite@hq.sk> wrote:
> > 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.
>
> Robert, this sub-thread started with Susan's statement:
>
>    1) I2RS Data models do not utilize the configuration data store,
>
> i.e., despite the fact that the data model is config true, it cannot
> be edited via running etc in NETCONF (or normal edit in RESTCONF).
>
> My comment on this was that *if* this is true, it should be noted in
> the document.  At this point, I am not sure if it is true or not.
>
>
Agreed.

But a larger issue is the balkanization of YANG.
To every YANG reader, the YANG data-def-stmts look exactly
like those that would be interpreted as configuration and state data nodes.

I little note that says "This is not regular YANG that is intended for
NETCONF or RESTCONF servers" is not really a solution.
RFC 7950 says YANG is for NETCONF, which is extra confusing.



> /martin
>
>
Andy


>
> _______________________________________________
> i2rs mailing list
> i2rs@ietf.org
> https://www.ietf.org/mailman/listinfo/i2rs
>

v2.23.0 | Report a Bug | By Email