Re: [netmod] upcoming adoptions

Andy Bierman <andy@yumaworks.com> Tue, 05 September 2017 23:05 UTC

Return-Path: <andy@yumaworks.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6E8A132E37 for <netmod@ietfa.amsl.com>; Tue, 5 Sep 2017 16:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 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, URIBL_BLOCKED=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 jFibt6loZZYk for <netmod@ietfa.amsl.com>; Tue, 5 Sep 2017 16:05:30 -0700 (PDT)
Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (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 55E63132195 for <netmod@ietf.org>; Tue, 5 Sep 2017 16:05:30 -0700 (PDT)
Received: by mail-io0-x22a.google.com with SMTP id j141so16472880ioj.4 for <netmod@ietf.org>; Tue, 05 Sep 2017 16:05:30 -0700 (PDT)
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=GQ5KlCW6HztpEY1biCieqnyj7ksLswGa79wqFd9vDmM=; b=s6hDmzwQajK2oRpnpYq8zlswPKgUcWuOeAwwapkYYa6gVTWGzJ+kKGCqCo11ed+n0B KMFTuSg8FvTvrg6ARhAg26bAvbuWPGY72m/Agl0r+mnfG2RGHZBLMcsuXA1SNLCR4cpu J+H+CeH0KILkU5b2BGTKN7u+8nP9cZyn1eglaw2EMM1Z0atFa0N/Jes+BvdCln0z73B6 j185RHSkoIMZvZWjjrQo7lrFySvUaV2x18onJmF3DnKVR0ROTJh/NeL7nc2pqZTWYw+x snc0LnnrrDU1A0+8AEXSy6/Ml9/fDhhL4rq2dliVsSPnq+6VhEMIlPhRfQ8iXGx4dVdg j+Pg==
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=GQ5KlCW6HztpEY1biCieqnyj7ksLswGa79wqFd9vDmM=; b=MzJwvTNFOk6fyntSbwwwADsGbDJdaHIkeF8XwB6Rvzg/22xHdPKqNLUHq0xj3l21P6 es9GvDdI/4amc8UCB+5H6Z2xQq87HAcbAGOs4EuIn2eZg+gQMxED6u40CVJ26hT6hdyg s9V10y8gqZ06E8v8w1+KTZGmaq5Cf8UZAJBKJpKGFFuvBhfL6hoWMdtHpKnqTbvZjlIk C6ns1MoOROWrSM6pQsDm/YOEIBlef1LiSt8VfA6jjAeXwJpyADBNBd4SlJ9I+cjAKuv/ 5yVDCMqwDjjTB82+POue7GgAxUd/NSGP/KQExr22ok+VYj+22pac8SxDESewSUCnq876 Dj3g==
X-Gm-Message-State: AHPjjUigu9C0Q+ANbAhS56gmYFJOGd1SqeHuZjNW1zjaozEd3eykHW21 g6xb1BnZJU8jZ05PEeT5Xu/YijA86i+R
X-Google-Smtp-Source: AOwi7QD6vH6ksHaVWsERHBf1tT3bppyOIwY1adaeMs0h/74IsV7Ocbw0roR1/s6oZLy4T1sabc4BgVltTC3xbTFzSPs=
X-Received: by 10.107.190.134 with SMTP id o128mr739573iof.10.1504652729519; Tue, 05 Sep 2017 16:05:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.6.206 with HTTP; Tue, 5 Sep 2017 16:05:28 -0700 (PDT)
In-Reply-To: <20170905.095949.1829098658779783521.mbj@tail-f.com>
References: <14299503-509D-43BE-A938-0B7B88C3B249@juniper.net> <3620aafe-bc72-cc54-9dbd-b687a0178df2@cisco.com> <20170905.095949.1829098658779783521.mbj@tail-f.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Tue, 5 Sep 2017 16:05:28 -0700
Message-ID: <CABCOCHRmNT=v9ivztzPh3OGmo-AeheHDct2XY9zbk_-FjEytmg@mail.gmail.com>
To: Martin Bjorklund <mbj@tail-f.com>
Cc: Benoit Claise <bclaise@cisco.com>, NETCONF Working Group <netconf-chairs@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
Content-Type: multipart/alternative; boundary="001a114f364474416f055879438e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/smtLnJWnS09vbDvYaIcpkHxUuOo>
Subject: Re: [netmod] upcoming adoptions
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 23:05:33 -0000

On Tue, Sep 5, 2017 at 12:59 AM, Martin Bjorklund <mbj@tail-f.com> wrote:

> Benoit Claise <bclaise@cisco.com> wrote:
> > Kent,
> > > Hey folks,
> > >
> > > As discussed at the last meeting, we are heading to revising existing
> > > RFCs to align them with NMDA.  The first batch have been published as
> > > individual drafts:
> > >
> > > 1. https://tools.ietf.org/html/draft-bjorklund-netmod-rfc7223bis-00
> > > 2. https://tools.ietf.org/html/draft-bjorklund-netmod-rfc7277bis-00
> > > 3. https://tools.ietf.org/html/draft-acee-netmod-rfc8022bis-00
> > Good. And there is one more in for NETMOD, as discussed in
> > https://datatracker.ietf.org/meeting/99/materials/slides-
> 99-netmod-sessa-nmda-qa:
> > RFC 7317
> > In NETCONF, we have also:
> >     RFC 6022, no I-D submitted yet
>
> I don't think this one requires an update at this time.  *If* it is
> changed, it might be worthwhile to remove definitions already covered
> by yang-library, and probably align with the netconf server model.
>
> >     RFC 7895, already adopted
> >     RFC 8040, no I-D submitted yet. No immediate plan to update?
>
> We have draft-ietf-netconf-nmda-restconf-00 which "Updates: 8040".
>
>

This draft does not address ietf-restconf-monitoring.

   YANG tree diagram for the "ietf-restconf-monitoring" module:

      +--ro restconf-state
         +--ro capabilities
         |  +--ro capability*   inet:uri
         +--ro streams
            +--ro stream* [name]
               +--ro name                        string
               +--ro description?                string
               +--ro replay-support?             boolean
               +--ro replay-log-creation-time?   yang:date-and-time
               +--ro access* [encoding]
                  +--ro encoding  string
                  +--ro location  inet:uri


I guess the NMDA transition plan to move the child nodes to a config=true
node
name /restconf that has only config=false nodes in it.  This seems quite
disruptive
and not a productive use of engineering resources, or support and customer
re-training.
The /netconf-state container is the same, and many more just like it.

NEW:

     +--rw restconf
         +--ro capabilities
         |  +--ro capability*   inet:uri
         +--ro streams
            +--ro stream* [name]
               +--ro name                        string
               +--ro description?                string
               +--ro replay-support?             boolean
               +--ro replay-log-creation-time?   yang:date-and-time
               +--ro access* [encoding]
                  +--ro encoding  string
                  +--ro location  inet:uri

    (+ old tree, but deprecated)

I doubt vendors will prioritize this high-impact/low-value upgrade, so
the deprecated foo-state trees will be needed for many years.


> /martin
>

Andy


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