[netconf] Re: YANG Groupings for QUIC clients and QUIC servers

[Per Andersson <[e-mail]>]

Dear Med,

On Tue, Jul 2, 2024 at 1:44 PM <[e-mail]> wrote:
>
> > -----Message d'origine-----
> > De : Per Andersson <[e-mail]>
> > Envoyé : mardi 2 juillet 2024 15:28
> > À : BOUCADAIR Mohamed INNOV/NET <[e-mail]>
> > Cc : [e-mail]
> > Objet : Re: [netconf] YANG Groupings for QUIC clients and QUIC
> > servers
> >
> >
> > Hi Med,
> >
> > On Tue, Jul 2, 2024 at 6:43 AM <[e-mail]>
> > wrote:
(...)
> > For instance the following are specific to QUIC, but could be
> > benefitial for NETCONF, RESTCONF, https-notif, if they opt to use
> > QUIC or HTTP/3 as a transport: supported QUIC version, max idle
> > timeout, initial max data, various flow control parameters, max
> > incoming streams, various other QUIC transport parameters and
> > possible extensions.
>
> [Med] These falls more under the spirit of draft-ietf-tcpm-yang-tcp. Other candidate specifics are: PMTU, manage features related to DATAGRAM/STREAM, CID control for load-balancing purposes, CID renewal policy, multipath support, proxing, etc. Not all of these will need to be covered, though.

Noted.


> > I think there are enough QUIC specifics to warrant another
> > client-server document with reusable groupings for configuring
> > QUIC clients and servers, instead of adding them to udp-client-
> > server.
>
> [Med] I was not suggesting to add QUIC specifics to the udp-client-server :-) My proposal was specific to the current groupings in -00 which are not specific to QUIC and can be used for UDP/DTLS schemes as well.

I understand. Perhaps there is room (or need) for both?


--
Per