[netconf] Re: I-D Action: draft-ietf-netconf-udp-client-server-05.txt

[Alex Huang Feng <[e-mail]>]

Dear Med,

My concern here is which ones should be defined if we move these groupings to udp-client-server draft as there might be a multitude of possibilities:
- udp client with tls 1.2 only
- udp client with tls 1.3 only
- udp client with both tls 1.2/1.3
- … same 3 for servers

Having 6 more groupings seems unreasonable for a draft focused on UDP.

Another thing we can do is just adding the tls 1.3 ones on udp but seems a bit strange leaving the others out.
So I’d rather let the consumer define them as they use it (such as I did in udp-notif).

I share the same concern on having the quic draft just defining the groupings below, but I was expecting some QUIC-dependent parameters on top of these, no?

Cheers,
Alex

> On 22 Oct 2024, at 07:33, [e-mail] wrote:
> 
> Hi Mahesh,
>  
> My concern is to better structure the documents we are producing. I was initially concerned with producing another yet RFC that would simply include the following, while the document where udpc:udp-client and udps:udp-server is still under development:
>  
> ==
>   grouping quic-client:
>     +---u tlsc:tls-client-grouping
>     |       {tlscmn:tls13 and not tlscmn:tls12}?
>     +---u udpc:udp-client
>  
>  
>   grouping quic-server:
>     +---u tlss:tls-server-grouping
>     |       {tlscmn:tls13 and not tlscmn:tls12}?
>     +---u udps:udp-server
> ==
>  
> Having done something in the past is not a reason per to do that same path :-)
>  
> Cheers,
> Med
>  
> De : Mahesh Jethanandani <[e-mail]> 
> Envoyé : lundi 21 octobre 2024 22:23
> À : BOUCADAIR Mohamed INNOV/NET <[e-mail]>
> Cc : Kent Watsen <[e-mail]>; Alex Huang Feng <[e-mail]>; NETCONF WG <[e-mail]>
> Objet : Re: [netconf] I-D Action: draft-ietf-netconf-udp-client-server-05.txt
>  
> 
> Speaking as a contributor again. 
>  
> I agree with Kent that the UDP draft does not imply QUIC or DTLS for that matter. If that was the case, we would not have defined draft-ietf-netconf-http-client-server separate from draft-ietf-netconf-tcp-client-server, which in turn would not have separated out draft-ietf-netconf-tls-client-server.
>  
> Cheers.
> 
> 
> On Oct 21, 2024, at 8:58 AM, [e-mail] <mailto:[e-mail]> wrote:
>  
> Hi Kent,
>  
> Still QUIC requires UDP and it seems straightforward to cover these two in one single document, especially that these are very simple and related modules.
>  
> Cheers,
> Med
>  
> De : Kent Watsen <[e-mail] <mailto:[e-mail]>> 
> Envoyé : jeudi 17 octobre 2024 23:54
> À : Alex Huang Feng <[e-mail] <mailto:[e-mail]>>
> Cc : BOUCADAIR Mohamed INNOV/NET <[e-mail] <mailto:[e-mail]>>; [e-mail] <mailto:[e-mail]>
> Objet : Re: [netconf] I-D Action: draft-ietf-netconf-udp-client-server-05.txt
>  
>  
> Also since UDP doesn’t imply QUIC (or DTLS), neither should be included in a UDP-focused draft.
>  
> K.  // contributor
>  
> 
> 
> 
> On Oct 17, 2024, at 12:50 PM, Alex Huang Feng <[e-mail] <mailto:[e-mail]>> wrote:
>  
> Dear Med,
>  
> I missed that one. Yes, there is a current discussion on whether the groupings from draft-andersson-netconf-quic-client-server should be moved to the draft-ietf-netconf-udp-client-server.
> My opinion is that groupings that simply use other groupings are not interesting enough to be defined in a RFC.
>  
> Regards,
> Alex
> 
> 
> 
> On 17 Oct 2024, at 18:26, [e-mail] <mailto:[e-mail]> wrote:
>  
> Hi Alex, 
> 
> 
> 
> There are no remaining issues on the draft.
> 
> I think there is still a pending issue about including the genetic quic groupings into this draft. 
> 
> Thank you.
> 
> Cheers,
> Med
> 
> 
> 
> -----Message d'origine-----
> De : Alex Huang Feng <[e-mail] <mailto:[e-mail]>>
> Envoyé : jeudi 17 octobre 2024 16:19
> À : Netconf <[e-mail] <mailto:[e-mail]>>
> Objet : [netconf] Re: I-D Action: draft-ietf-netconf-udp-client-
> server-05.txt
> 
> 
> Dear NETCONF,
> 
> This iteration addresses the comments from Med and William
> removing the "-grouping" from the groupings and the "-supported"
> from the feature.
> 
> There are no remaining issues on the draft.
> 
> Regards,
> Alex
> 
> 
> 
> On 17 Oct 2024, at 15:51, [e-mail] <mailto:[e-mail]> wrote:
> 
> Internet-Draft draft-ietf-netconf-udp-client-server-05.txt is
> now available.
> 
> 
> It is a work item of the Network Configuration (NETCONF) WG of
> the IETF.
> 
> 
> 
>  Title:   YANG Groupings for UDP Clients and UDP Servers
>  Authors: Alex Huang Feng
>           Pierre Francois
>           Kent Watsen
>  Name:    draft-ietf-netconf-udp-client-server-05.txt
>  Pages:   13
>  Dates:   2024-10-17
> 
> Abstract:
> 
>  This document defines two YANG 1.1 modules to support the
>  configuration of UDP clients and UDP servers.
> 
> The IETF datatracker status page for this Internet-Draft is:
> 
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> data
> 
> 
> tracker.ietf.org <http://tracker.ietf.org/>%2Fdoc%2Fdraft-ietf-netconf-udp-client-
> server%2F&data=
> 
> 
>  
> 05%7C02%7Cmohamed.boucadair%40orange.com <http://40orange.com/>%7Cd4a9704e1d364f28a3e608d
> ceeb
> 
> 
>  
> 6b7d1%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638647715744761
> 808%
> 
> 
>  
> 7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTi
> I6Ik
> 
> 
>  
> 1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=Lcd5QtS7RtXirz7WgnqPyjEUzw
> %2Ff
> 
> 
> 1SBKhJbMQzYQrxc%3D&reserved=0
> 
> There is also an HTMLized version available at:
> 
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> data
> 
> 
> tracker.ietf.org <http://tracker.ietf.org/>%2Fdoc%2Fhtml%2Fdraft-ietf-netconf-udp-client-
> server-0
> 
> 
>  
> 5&data=05%7C02%7Cmohamed.boucadair%40orange.com <http://40orange.com/>%7Cd4a9704e1d364f28
> a3e6
> 
> 
>  
> 08dceeb6b7d1%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C63864771
> 5744
> 
> 
>  
> 802649%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzI
> iLCJ
> 
> 
>  
> BTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=OtM%2BpaPqviWwJ3ZLc
> 3xBc
> 
> 
> 9rfbl%2FY7wOvpOyp9pCNd4w%3D&reserved=0
> 
> A diff from the previous version is available at:
> 
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> auth
> 
> 
> or-tools.ietf.org <http://or-tools.ietf.org/>%2Fiddiff%3Furl2%3Ddraft-ietf-netconf-udp-
> client-serv
> 
> 
> er-
> 05&data=05%7C02%7Cmohamed.boucadair%40orange.com <http://40orange.com/>%7Cd4a9704e1d364f2
> 8
> 
> 
>  
> a3e608dceeb6b7d1%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6386
> 4771
> 
> 
>  
> 5744834065%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2l
> uMzI
> 
> 
>  
> iLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=qdt%2Fq%2B3jv4h
> mqGQ
> 
> 
> w4eCnWk3f2%2BqCW0Ti8kEpfhp96YU%3D&reserved=0
> 
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org <http://rsync.ietf.org/>::internet-drafts
> 
> 
> _______________________________________________
> netconf mailing list -- [e-mail] <mailto:[e-mail]> To unsubscribe send an
> email
> 
> 
> to [e-mail] <mailto:[e-mail]>
> 
> _______________________________________________
> netconf mailing list -- [e-mail] <mailto:[e-mail]> To unsubscribe send an
> email to [e-mail] <mailto:[e-mail]>
> ____________________________________________________________________________________________________________
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>  
> _______________________________________________
> netconf mailing list -- [e-mail] <mailto:[e-mail]>
> To unsubscribe send an email to [e-mail] <mailto:[e-mail]>
>  
> ____________________________________________________________________________________________________________
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>  
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
> _______________________________________________
> netconf mailing list -- [e-mail] <mailto:[e-mail]>
> To unsubscribe send an email to [e-mail] <mailto:[e-mail]>
>  
> Mahesh Jethanandani
> [e-mail] <mailto:[e-mail]>
>  
>  
>  
> ____________________________________________________________________________________________________________
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.