[netconf] comments on Re: I-D Action: draft-ietf-netconf-tcp-client-server-15.txt

[tom petch <[e-mail]>]

From: netconf <[e-mail]> on behalf of [e-mail] <[e-mail]>
Sent: 12 December 2022 18:49

My last attempts to comment on the tcp-client-server got mixed up with those on tls so I send them again with a few additions.

Should there be a name string for the local/remote configuration of client and server?  I expect to see one in a design document.

The language for me is not quite right in several places in e.g. the choice of verb or preposition and we have   had ADs who are rather keen on this, but this is late in the process so I am inclined to let it ride.

s1.1
   Hyperlinks to each RFC are provided below the diagram.

Well, it depends on the format and they are absent in mine.  URL yes, hyperlink no.

Examples  could do with IPv6, again something that some ADs are keen on.

s.3,3
YANG  features could (always) do with references.  I do not know what proxy-connect is and cannot find it in a TCP RFC.  Ditto local binding.  Keepalives are in RFC793 and its replacement and should be referenced since that is a more authoritative source than s.2.1.5 of this I-D IMHO

         username/password when initiating TCP connections via
          and SOCKS Version 5 proxy server.";
I cannot parse this

            (instead of 'mandatory true') so that as application
ditto

          "The local IP address/interface (VRF?) to bind to for when
ditto twice

    <local-address>10.20.30.40</local-address>
should be  documentation address
     <local-port>7777</local-port>
should be a private port 49152-
no ports are reserved for documentation

s.5.1
 Both of these protocols
   have mandatory-to-implement secure transport layers (e.g., SSH, TLS)
   with mutual authentication.
Well the mutual authentication is optional so I think you need something like
 Both of these protocols
   have mandatory-to-implement secure transport layers (e.g., SSH, TLS);
  mutual (client?) authentication is optional and SHOULD be configured.

crypto-types is an import so should be  a Normative reference in the I-D.

Tom Petch

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Network Configuration WG of the IETF.

        Title           : YANG Groupings for TCP Clients and TCP Servers
        Authors         : Kent Watsen
                          Michael Scharf
  Filename        : draft-ietf-netconf-tcp-client-server-15.txt
  Pages           : 34
  Date            : 2022-12-12

Abstract:
   This document defines three YANG 1.1 modules to support the
   configuration of TCP clients and TCP servers.  The modules include
   basic parameters of a TCP connection relevant for client or server
   applications, as well as client configuration required for traversing
   proxies.  The modules can be used either standalone or in conjunction
   with configuration of other stack protocol layers.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-netconf-tcp-client-server/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-netconf-tcp-client-server-15.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-netconf-tcp-client-server-15


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts


_______________________________________________
netconf mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/netconf