Re: [Netconf] YANG Doctor question: empty mandatory choice?

"Eric Voit (evoit)" <evoit@cisco.com> Wed, 01 August 2018 16:03 UTC

Return-Path: <evoit@cisco.com>
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 D7A8E130E44 for <netconf@ietfa.amsl.com>; Wed, 1 Aug 2018 09:03:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
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_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 qHnTAg_jjPbZ for <netconf@ietfa.amsl.com>; Wed, 1 Aug 2018 09:03:58 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10835130E2E for <netconf@ietf.org>; Wed, 1 Aug 2018 09:03:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3688; q=dns/txt; s=iport; t=1533139437; x=1534349037; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=/UhqNVtvu+IXZgHiH84vq7UmMhjy6//jFxq6E2RLaqA=; b=iOQNWIbHaInVFmfiPhBuuWX1cdbZ2l1FbOnapw3mBy8vwO3lw8dBiMcs 3gbuCXv1qwdJVdstGsBEWLYywD1q/lIxB9G2LrDR7r8iMDBF5xw8Tkk+p HTr/H7I0NELUh0DGnobX6sjGebizoxOEES1AJNfT83mwfG+gJkIqiwpvP Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AyAgAK2WFb/51dJa1bGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYNOY38yg3SIBow/gg2DPJIcgXoLhGwCF4MsITQYAQIBAQI?= =?us-ascii?q?BAQJtKIU2AQEBAwEjEUUFCwIBCA4HBQImAgICMBUQAgQBDQ2DGYF3CLEugS6?= =?us-ascii?q?KWIELh30XgUE/hCSEaIMXgjUgAoxwhSaICAkCjzKBUIxJiBOKCAIRFIEkHTi?= =?us-ascii?q?BUnAVO4JqkFKPQYEbAQE?=
X-IronPort-AV: E=Sophos;i="5.51,432,1526342400"; d="scan'208";a="432106407"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Aug 2018 16:03:57 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id w71G3uk0026373 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 1 Aug 2018 16:03:57 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 1 Aug 2018 12:03:56 -0400
Received: from xch-rtp-013.cisco.com ([64.101.220.153]) by XCH-RTP-013.cisco.com ([64.101.220.153]) with mapi id 15.00.1320.000; Wed, 1 Aug 2018 12:03:56 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Kent Watsen <kwatsen@juniper.net>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
CC: Martin Bjorklund <mbj@tail-f.com>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] YANG Doctor question: empty mandatory choice?
Thread-Index: AQHUKEYUmUSBX283/kCJ9HawSKyfbKSp4eIAgABmOICAAMa8kA==
Date: Wed, 1 Aug 2018 16:03:56 +0000
Message-ID: <d7e314189f804eab97d5a836462f4925@XCH-RTP-013.cisco.com>
References: <44B0A74E-CCF0-4E9B-846A-1F46E90AEB5E@juniper.net> <20180731175538.tsdcuea4lbdl7fui@anna.jacobs.jacobs-university.de> <0291FEFB-B0BE-4CA2-8EAB-B1736549B763@juniper.net>
In-Reply-To: <0291FEFB-B0BE-4CA2-8EAB-B1736549B763@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.56.234]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.153, xch-rtp-013.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/0Eju5TP-uuBCAVsNDBk6UDVi36M>
Subject: Re: [Netconf] YANG Doctor question: empty mandatory choice?
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Network Configuration WG mailing 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, 01 Aug 2018 16:04:00 -0000

> From: Kent Watsen, July 31, 2018 8:01 PM
> 
> 
> >> In the case of RESTCONF, we could update the ietf-restconf-client and
> >> ietf-restconf-server models to include an "encodings" leaf-list, to
> >> configure the RESTCONF server which encodings it should support.
> >
> > RESTCONF uses SSE for notification delivery. What you have in mind is
> > likely the HTTP/2 push transport defined in
> > draft-ietf-netconf-restconf-notif
> 
> Not really.  The thought extends beyond the notifications work.  In general,
> servers are able to be tuned as to which protocols, algorithms, etc. are
> supported.  For instance, NGINX has a parameter for if HTTP2 is enabled.
> Similarly, it seems that a server may be configured, for local policy reasons, to
> support just xml or just json.  The idea is that, if we add these tuning params to
> the ietf-restconf-[client|server] models, then those tuning params might be
> used to enable the encoding selection for *configured* restconf-notif
> subscriptions. Just an idea.
> Really, this is an open restconf-client-server draft issue, and only a restconf-
> notif draft issue when we do the bis on that draft.
> 
> 
> 
> > which I think should not be called
> > RESTCONF just because it uses some version of HTTP.
> 
> Agreed.  The "restconf-notif" draft should really only speak about the
> RESTCONF protocol.

The current RESTCONF-notif draft includes dynamic and configured subscriptions.    The draft likely should be split, one for dynamic (RESTCONF) and configured (HTTP2).   

>  That the YANG module in the draft is called "ietf-http-
> subscribed-notifications" surprises me.

The augmentations in the model are only relevant for configured, so HTTP seemed more applicable.
 
> Actually, the names of the YANG "notif" modules in general seem less than
> ideal.  I appreciate that RFC 6470 took the name "ietf-netconf-notifications",
> and these drafts are trying to follow that naming convention, but maybe we
> should choose a more concise pattern like ietf-notifications-<transport>:
> 
>   ietf-notifications-netconf
>   ietf-notifications-restconf
>   ietf-notifications-coap
>   ietf-notifications-http2

This works for me.
 
> or maybe ietf-notifications-<transport>[-<encoding>]:
> 
>   ietf-notifications-netconf
>   ietf-notifications-restconf-xml
>   ietf-notifications-restconf-json
>   ietf-notifications-coap
>   ietf-notifications-http2-xml
>   ietf-notifications-http2-json

I think creating different identities for XML & JSON encodings which are themselves dependent on a  specific transport would be confusing.

Eric

> > /js
> 
> Kent // contributor
> 
>