[netconf] Yangdoctors last call review of draft-ietf-netconf-tls-client-server-24
Andy Bierman via Datatracker <noreply@ietf.org> Tue, 25 May 2021 19:22 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: netconf@ietf.org
Delivered-To: netconf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 269CE3A1A44; Tue, 25 May 2021 12:22:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Andy Bierman via Datatracker <noreply@ietf.org>
To: yang-doctors@ietf.org
Cc: draft-ietf-netconf-tls-client-server.all@ietf.org, last-call@ietf.org, netconf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.30.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <162197056513.1767.16350161534776831688@ietfa.amsl.com>
Reply-To: Andy Bierman <andy@yumaworks.com>
Date: Tue, 25 May 2021 12:22:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/f9spHsKXDyUQBtZsrx5LnHiaFtw>
Subject: [netconf] Yangdoctors last call review of draft-ietf-netconf-tls-client-server-24
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 25 May 2021 19:22:45 -0000
Reviewer: Andy Bierman Review result: Ready Comments: I am not commenting on the TLS 1.0 and 1.3 onging discussions. The WG decision does not impact the YANG module review. 1) Measuring Interoperability for groupings and identities [same comment for SSH and TLS drafts] These modules are intentionally abstract. There are no protocol-accessible objects defined at all. Interoperability is usually measured in the context of a specific protocol (e.g., NETCONF). There is an assumption that interoperability will be achieved by some other RFCs that will have "uses" statements to create protocol-accessible or otherwise implementable objects. There is also an assumption that the groupings will be used the same everywhere, and the only difference will be the path from root to the objects in these groupings. In fact, the "refine" statement allows each usage to be different. Perhaps the drafts should mention these interoperability issues. 2) mandatory choice of only optional-to-implement cases The choice /ietf-tls-client:client-identity/auth-type is mandatory but all cases have if-feature-stmts. Does draft mention 1 of the 4 features MUST be implemented?
- [netconf] Yangdoctors last call review of draft-i… Andy Bierman via Datatracker
- Re: [netconf] [Last-Call] Yangdoctors last call r… Kent Watsen
- Re: [netconf] [Last-Call] Yangdoctors last call r… Andy Bierman
- Re: [netconf] [Last-Call] Yangdoctors last call r… Andy Bierman
- Re: [netconf] [Last-Call] Yangdoctors last call r… Kent Watsen
- Re: [netconf] [Last-Call] Yangdoctors last call r… Andy Bierman