Re: [netconf] Virtual hum for the question on "https-notif" draft

Martin Björklund <mbj+ietf@4668.se> Wed, 29 April 2020 18:38 UTC

Return-Path: <mbj+ietf@4668.se>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 673003A1153 for <netconf@ietfa.amsl.com>; Wed, 29 Apr 2020 11:38:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level:
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, PDS_NAKED_TO_NUMERO=1.999, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=4668.se header.b=YnLDSBOS; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=KR3HAONJ
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 J8ZlEG046U32 for <netconf@ietfa.amsl.com>; Wed, 29 Apr 2020 11:38:42 -0700 (PDT)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B38C13A114C for <netconf@ietf.org>; Wed, 29 Apr 2020 11:38:42 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id D1E7A710; Wed, 29 Apr 2020 14:38:41 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Wed, 29 Apr 2020 14:38:42 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=4668.se; h=date :message-id:to:cc:subject:from:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=fm1; bh= 3NVAKkcsevQYRWM/4KIh+bBkiowQxM6UlzLWRsJA3hc=; b=YnLDSBOSgJMrkW0W lO/yrzzuDIfLCKISkTcqXKjwHNNZUzKQP8CIvqZtaXUslzI5bx/FE6mNlvddJ8+X pKI0Kwi+L4rukl7Nw9fTtOvWxfZcgKY/sa44pCAcf21GxulvypBVziBc9X6+1N5W CjDzkBf0MRIEhFgYf811rOsBD4uDadopCeuC5NWdYofZSBl1snObe6UQWUfd6Wgi o8620EE1fon14kxTQryos6xEORMXVz5gaDG7cNswDoEzsKGVcg6jhEQNPU4FIaSI aPw/GQJ0xXEukI45bB4i9PDURoWS+2Uemr3ooxlEKZuIMEQgRgjHDGZYhe0We4Dp 7dhc4A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=3NVAKkcsevQYRWM/4KIh+bBkiowQxM6UlzLWRsJA3 hc=; b=KR3HAONJyzcBqbUQMsD+NqPMtQqfCUxIiNzBf85fOsHPhc2A/qEMMXbC9 fFR9oR5hUfNgGgLrYcvxyicEqs0ixzHBx/pWDs3PywefuBCkvPYh/6v0GnbvrEZd l1qVY6bgdftKFGZXJ1wqZ69b0Aa9LDB5fDPnfuLi8nNTyn4Bp9VPfFL6vF37Yaju jotqEJLmr0nqYef6QaAcOsfr8gaC9yBIUzu+5sypAJIRQIbW2jbE4RVrfDCYCvk8 5VF1LltQXF7lX3uGU3snj8/ZChtnIZ/lZQpF3b0gi6NZi3tmefVAwzGksGw1eqOS JOM/+Ykyip7BqiATSLTLOSU3mRmow==
X-ME-Sender: <xms:sMmpXu0dPyv-FJuE5RInhybnLYVGbkoFy6eXokT-OQKBs7hcySqV5Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrieefgdduvdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffkffvuffhjghfofggtgfgsehtsg ertdertdejnecuhfhrohhmpeforghrthhinhcuuehjnphrkhhluhhnugcuoehmsghjodhi vghtfhesgeeiieekrdhsvgeqnecuggftrfgrthhtvghrnhepheetgedtfffggeffkedvje ekveelteeuuddttdffhfelgfetvdevhedvgeeutddunecukfhppeduheekrddujeegrdeg rdeggeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hmsghjodhivghtfhesgeeiieekrdhsvg
X-ME-Proxy: <xmx:sMmpXiWN7DieDIvGnQONXph7jvAjOZw0vu49U7IYMIWMDnewfPPGyw> <xmx:sMmpXvypxjQuw0bD0X-zuWvOsKEbiC0c9aU5JXPAgVZpr5GLj3SCvw> <xmx:sMmpXm2yWRbN3hSg6kD78FPtjMyznhZxMIOQ_5qWVfvyKKfyHr0yIQ> <xmx:scmpXuCQJapA38Go0QAFwT_SD1EEwP7K9IkVry7Gkh8Zv5bKeAhNcg>
Received: from localhost (unknown [158.174.4.44]) by mail.messagingengine.com (Postfix) with ESMTPA id 4DDB93065EE3; Wed, 29 Apr 2020 14:38:40 -0400 (EDT)
Date: Wed, 29 Apr 2020 20:38:38 +0200
Message-Id: <20200429.203838.1829077676409702830.id@4668.se>
To: evoit=40cisco.com@dmarc.ietf.org
Cc: kent+ietf@watsen.net, rwilton=40cisco.com@dmarc.ietf.org, netconf@ietf.org
From: Martin Björklund <mbj+ietf@4668.se>
In-Reply-To: <BL0PR11MB312212D6F955DF26188D0901A1AD0@BL0PR11MB3122.namprd11.prod.outlook.com>
References: <MN2PR11MB4366FC94F18140F1BB153A1FB5AF0@MN2PR11MB4366.namprd11.prod.outlook.com> <01000171bc405640-6e173d84-f921-4f6f-929a-6431410051c8-000000@email.amazonses.com> <BL0PR11MB312212D6F955DF26188D0901A1AD0@BL0PR11MB3122.namprd11.prod.outlook.com>
X-Mailer: Mew version 6.8 on Emacs 25.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset="utf-8"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/XoMjoA_bkHc5GtcrcWXFHz8Jdl0>
Subject: Re: [netconf] Virtual hum for the question on "https-notif" draft
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Apr 2020 18:38:45 -0000

Hi,

"Eric Voit \(evoit\)" <evoit=40cisco.com@dmarc.ietf.org> wrote:
> From: Kent Watsen, April 27, 2020 11:28 AM
> 
>  On Apr 27, 2020, at 8:08 AM, Rob Wilton (rwilton) <rwilton=40cisco.com@dmarc.ietf.org>
>  wrote:
> 
>  [As an individual contributor]
> 
>  Changing my stance somewhat from the NETCONF meeting …
> 
>  After looking into the details a bit more, section 7 of rfc8639 states:
> 
>  A specification for a transport MUST identify any encodings that are
> 
>  supported. If a configured subscription's transport allows different
> 
>  encodings, the specification MUST identify the default encoding.
> 
>  Does this imply that the http-notif draft either must state a default encoding (or otherwise
>  update rfc8639)?
> 
> It seems that way...at least when https-notif is being used for RFC 8639 (it doesn’t have to be).
> 
> Looking at the hum-results so far, 70% picked "Let the market decide” (with the remaining 30%
> all picking "Publisher MUST implement JSON encoding”).
> 
> In light of the RFC 8639 text quoted above, we might question the validity of the hum…or, given
> the strong preference from the hum, we might question the validity of that constraint in RFC
> 8639. If questioning RFC 8639, a better question to ask might be why the configurable “encoding”
> leaf isn’t mandatory (also eliminating this issue and seemingly cleaner)?

RFC 8639 explains that if the "encoding" leaf isn't configured, the
transport-default is used.  RFC 8639 also says that a transport must
have a transport-default.

That's the answer to the question: "why is 'encoding' optional?".


/martin


> 
> <eric> The WG feedback during RFC-8639 development was that encoding was often implied from
> transport. Therefore mandating exposure of this information in the model was overly verbose,
> and could result in misconfiguration.
> 
> Adding Martin to the thread as he was previosuly involved with this discussion.
> 
> Eric
> 
> <...>
> 
> Kent // contributor
> 
>  I’ve also filled in the virtual hum.
> 
>  Regards,
>  Rob
>