Re: [netconf] Benjamin Kaduk's Discuss on draft-ietf-netconf-yang-push-23: (with DISCUSS and COMMENT)

"Eric Voit (evoit)" <> Wed, 15 May 2019 19:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B64F11207EF; Wed, 15 May 2019 12:24:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 3DccFRvLCOhl; Wed, 15 May 2019 12:24:28 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id F08B11207D6; Wed, 15 May 2019 12:24:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=3135; q=dns/txt; s=iport; t=1557948268; x=1559157868; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=BA+Pm5bARE4Lw36rqVqC6x/n8/RJdHLubDG1JkX0A/c=; b=HZ5ezXa5yyeBWsTew6C1/5S1VEwU1Jk10xT0TdM+TEZuKmBPdfsyVbMN +fF1iDiQJXx5mVHF+MHuIgW3CEF5LkW3yf5u28ziOp9bLjAgJix3oyj7A UAIeEZM53dFTWmsB/DKNtyLO/mEV1w/ctqyRYL6LcwXq+DC4Kv93HkL5M Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.60,473,1549929600"; d="scan'208";a="273219198"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-SEED-SHA; 15 May 2019 19:24:26 +0000
Received: from ( []) by (8.15.2/8.15.2) with ESMTPS id x4FJOQZA001492 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 15 May 2019 19:24:26 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 15 May 2019 15:24:25 -0400
Received: from ([]) by ([]) with mapi id 15.00.1473.003; Wed, 15 May 2019 15:24:25 -0400
From: "Eric Voit (evoit)" <>
To: Alexander Clemm <>, 'Benjamin Kaduk' <>
CC: 'The IESG' <>, "" <>, "" <>, "" <>
Thread-Topic: [netconf] Benjamin Kaduk's Discuss on draft-ietf-netconf-yang-push-23: (with DISCUSS and COMMENT)
Thread-Index: AQJ3PF2dFB47j2Iq/ZH31Feu7eo0twH9HjRjAiM3vTWlBxuWYIAADRrQ
Date: Wed, 15 May 2019 19:24:25 +0000
Message-ID: <>
References: <> <043c01d50ac9$7099a780$51ccf680$> <> <052101d50b50$49cbf450$dd63dcf0$>
In-Reply-To: <052101d50b50$49cbf450$dd63dcf0$>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [netconf] Benjamin Kaduk's Discuss on draft-ietf-netconf-yang-push-23: (with DISCUSS and COMMENT)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 15 May 2019 19:24:37 -0000

> From: Alexander Clemm, May 15, 2019 2:59 PM
> > Section 3.3 states:
> >
> >             In order for a subscriber to determine whether objects
> >    support on-change subscriptions, objects are marked accordingly on a
> >    publisher.  Accordingly, when subscribing, it is the responsibility
> >    of the subscriber to ensure it is aware of which objects support on-
> >    change and which do not.  For more on how objects are so marked, see
> >    Section 3.10.
> >
> > Chasing the reference, we see that this marking is left for future
> > work or implementation-specific usage.  I'm not very comfortable with
> > the way we are describing this situation, as it seems pretty fragile
> > in the face of different implementations trying to interoperate.
> >
> > <ALEX> The working group decided to pull this item out of this draft.
> > It is being addressed in draft-ietf-netconf-notification-capabilities
> > (
> > biliti
> > es/) </ALEX>
> I guess I'll see what the -24 looks like, but I'm not sure yet whether "pull this
> item out of the draft" is describing a previous decision that left it in this state or
> a current decision starting from this state.  (The latter would seem to make
> more sense to me, but I can wait and see.)
> <ALEX2> To give a bit of history, in a set of earlier revisions we did describe a
> mechanism for this.  There was quite a bit of discussion around this and various
> options were considered, from introducing a YANG extension (see e.g. rev 12
> section 3.10) to the mechanism that is now described in the separate draft.
> There were also discussions whether such mechanism should be generalized
> further - for example, what if you wanted to express not only whether an item
> supports on-change subscriptions, but wants to give an indication of the "size"
> of the change?  The WG ultimately decided to not overburden the draft and slow
> progress down further and address this item separately.  There was also at some
> point discussion about keeping it simpler and take an all-or-nothing approach
> (require a server to either support on-change for all objects or none), which
> however was deemed to be too restrictive and we did want to allow for the
> possibility of a differentiated approach.
> Bottom line, I would like to ask please accept the previous decision.
> </ALEX2>

To summarize how this played out in the WG
- there was a section dedicated to the solution within YANG push
- several WG members asked extract this solution in order to postpone finalization of the solution
- we extracted the section at the WG request
- a new draft with the solution was adopted by the WG.  See draft-ietf-netconf-notification-capabilities
- implementers would be wise to use this draft

To get a brief glimpse on some of the details in the discussion history, you can look at 
There was also quite a bit on the mailing list.