Re: [netconf] Adoption poll for tcp-client-server and http-client-server draft

Kent Watsen <kent+ietf@watsen.net> Mon, 08 April 2019 19:11 UTC

Return-Path: <01000169fe5c5e14-63eba328-51f5-4ba3-ac17-311909f5bd86-000000@amazonses.watsen.net>
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 8292712032F for <netconf@ietfa.amsl.com>; Mon, 8 Apr 2019 12:11:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 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_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.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 14nvbK4W1Mwh for <netconf@ietfa.amsl.com>; Mon, 8 Apr 2019 12:11:01 -0700 (PDT)
Received: from a8-64.smtp-out.amazonses.com (a8-64.smtp-out.amazonses.com [54.240.8.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8156312032C for <netconf@ietf.org>; Mon, 8 Apr 2019 12:11:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1554750660; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=m6U5haUNyymaJvrWgAMw6QXvxqA8PbELUkqPcx595z8=; b=gOmJYNyavCRsk7njlP7sdMa12oNx3Wmd/aMnCCw3lOKh2RehCJFvkTdHZhdaWYAB cu85sYTGBvq0Vf+ShCWMj1KI8jPmlsU463PxzJ8NPgu9glWlOs6QRPgXFwczxj8ewFC tJ5nh+yyOsv4bTqPF4XLSpXNePPEuRwBpH5yKs8g=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <01000169fe5c5e14-63eba328-51f5-4ba3-ac17-311909f5bd86-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7198D22E-2350-47E2-AC24-CEC3CCC7768A"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Mon, 8 Apr 2019 19:11:00 +0000
In-Reply-To: <BD6D193629F47C479266C0985F16AAC7011EA6336B@ex-mb1.corp.adtran.com>
Cc: Mahesh Jethanandani <mjethanandani@gmail.com>, "netconf@ietf.org" <netconf@ietf.org>
To: NICK HANCOCK <nick.hancock@adtran.com>
References: <ED12BA39-09E6-4436-B759-625434D197D6@gmail.com> <BD6D193629F47C479266C0985F16AAC7011EA6336B@ex-mb1.corp.adtran.com>
X-Mailer: Apple Mail (2.3445.102.3)
X-SES-Outgoing: 2019.04.08-54.240.8.64
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/fowAkc4m7pAzKTBMdG05jQ5hsBk>
Subject: Re: [netconf] Adoption poll for tcp-client-server and http-client-server 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: Mon, 08 Apr 2019 19:11:04 -0000

Hi Nick,

You will notice in the latest tcp-client-server update [1] that there is now a "presence" statement on the "keepalives" containers.  Do you think any more "mandatory true" statements are needed?

I don't understand your last comment or, rather, I think it is the case already that the TCP keepalives configuration is outside the SSH/TLS configuration.  Note the "keepalives" configuration inside the SSH/TLS configuration is actually to separately configure keepalives at the SSH/TLS levels - makes sense?

[1] https://tools.ietf.org/html/draft-kwatsen-netconf-tcp-client-server-01 <https://tools.ietf.org/html/draft-kwatsen-netconf-tcp-client-server-01>

Kent // contributor


> On Mar 26, 2019, at 10:30 AM, NICK HANCOCK <nick.hancock@adtran.com> wrote:
> 
> I support this work to provide the ability to configure TCP keepalives for NETCONF connections as we need this support in our implementations and support the adoption of these drafts.
>  
> I also have the following comments on the actual YANG implementation and usage within the client/server model.
>  
> The leafs within the “tcp-keepalives” container are optional. Given that a server supports the feature “tcp-client-keepalives”, TCP keepalives would be disabled per default through missing configuration, which I believe is desirable behavior. However, there is currently nothing to prevent a client configuring, say, just ‘max-probes’ only resulting in an incomplete but valid configuration. Would not adding a ‘presence’ statement to the container “tcp-keepalives” and making its child nodes mandatory or adding default values be a more practical solution that defines a predictable behavior?
>  
> Since TCP is a layer below the security layer and independent of the choice of security protocol, I was wondering what the motivation was for locating the TCP keepalives configuration within the SSH/TLS configuration. Wouldn’t this be better located as a sibling nod to the choice “transport”?
>  
> Nick
>  
>  <>From: netconf <netconf-bounces@ietf.org <mailto:netconf-bounces@ietf.org>> On Behalf Of Mahesh Jethanandani
> Sent: 26 March 2019 12:17
> To: Netconf <netconf@ietf.org <mailto:netconf@ietf.org>>
> Subject: [netconf] Adoption poll for tcp-client-server and http-client-server draft
>  
> This is the start of a two week poll for WG adoption of the two drafts:
> 
> https://tools.ietf.org/html/draft-kwatsen-netconf-tcp-client-server-00 <https://tools.ietf.org/html/draft-kwatsen-netconf-tcp-client-server-00>
> https://tools.ietf.org/html/draft-kwatsen-netconf-http-client-server-00 <https://tools.ietf.org/html/draft-kwatsen-netconf-http-client-server-00>
> 
> Please indicate your support for or any objections you might have for adopting the two drafts as WG items by April 9.
> 
> Mahesh Jethanandani
> mjethanandani@gmail.com <mailto:mjethanandani@gmail.com>
> 
> 
> 
> _______________________________________________
> netconf mailing list
> netconf@ietf.org <mailto:netconf@ietf.org>
> https://www.ietf.org/mailman/listinfo/netconf <https://www.ietf.org/mailman/listinfo/netconf>_______________________________________________
> netconf mailing list
> netconf@ietf.org <mailto:netconf@ietf.org>
> https://www.ietf.org/mailman/listinfo/netconf <https://www.ietf.org/mailman/listinfo/netconf>