[netconf] Re: I-D Action: draft-ietf-netconf-udp-notif-13.txt

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

Dear Med,

Thanks for the review and proposals.

I rollbacked and removed the default port from UDP-Notif.
I will submit this iteration before cutoff: https://author-tools.ietf.org/diff?doc_1=draft-ietf-netconf-udp-notif-13&url_2=https://raw.githubusercontent.com/network-analytics/draft-ietf-netconf-udp-notif/main/draft-ietf-netconf-udp-notif-14.txt

Cheers,
Alex

> On 28 Jun 2024, at 08:44, [e-mail] wrote:
> 
> Hi Alex, all,
>  
> I’m afraid that the arguments to get assigned a well-known port number are lacking or weak if you will. This is even exacerbated in this specific context as you already need to know the IP address! The same “channel” used to retrieve/discover that IP address can be used to also supply the port number.
>  
> Please check rfc6335#section-7.2 and also rfc7605#section-7.
>  
> I suggest to fix draft-ietf-netconf-udp-client-server.
>  
> As I’m there, I think that you should also update your DTLS container with these refines
>  
>       refine "hello-params/tls-versions/min" {
>         must "not(derived-from-or-self(current(), "
>            + "'tlscmn:tls12'))" {
>           error-message
>                 "TLS 1.2 is not supported as min TLS version";
>         }
>       }
>       refine "hello-params/tls-versions/max" {
>         must "not(derived-from-or-self(current(), "
>            + "'tlscmn:tls12'))" {
>           error-message
>                 "TLS 1.2 is not supported as max TLS version";
>         }
>       }
>  
> Cheers,
> Med
>  
> De : Alex Huang Feng <[e-mail] <mailto:[e-mail]>> 
> Envoyé : jeudi 27 juin 2024 15:34
> À : netconf <[e-mail] <mailto:[e-mail]>>
> Objet : [netconf] Re: I-D Action: draft-ietf-netconf-udp-notif-13.txt
>  
> 
> Dear NETCONF,
>  
> We submitted a new iteration of UDP-Notif with minor changes.
>  
> The YANG is using the generic UDP client groupings from draft-ietf-netconf-udp-client-server.
> The impact is that now, we can configure a node to send UDP-notif notifications to a inet:host rather than only to inet:ip-address-no-zone and can set local addresses.
>  
> Given that in draft-ietf-netconf-udp-client-server the port is defined as a default port in the grouping, we had to ask IANA a default port for UDP-notif.
> Note that there is an open thread on whether the generic udp-client-server-grouping should mandate a default port or not.
> 
> 
> We welcome any new comments on the draft.
> 
> 
> Regards,
> Alex
> 
> 
> 
> On 27 Jun 2024, at 15:06, [e-mail] <mailto:[e-mail]> wrote:
>  
> Internet-Draft draft-ietf-netconf-udp-notif-13.txt is now available. It is a
> work item of the Network Configuration (NETCONF) WG of the IETF.
> 
>   Title:   UDP-based Transport for Configured Subscriptions
>   Authors: Guangying Zheng
>            Tianran Zhou
>            Thomas Graf
>            Pierre Francois
>            Alex Huang Feng
>            Paolo Lucente
>   Name:    draft-ietf-netconf-udp-notif-13.txt
>   Pages:   32
>   Dates:   2024-06-27
> 
> Abstract:
> 
>   This document describes a UDP-based protocol for YANG notifications
>   to collect data from network nodes.  A shim header is proposed to
>   facilitate the data streaming directly from the publishing process on
>   network processor of line cards to receivers.  The objective is to
>   provide a lightweight approach to enable higher frequency and less
>   performance impact on publisher and receiver processes compared to
>   already established notification mechanisms.
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-netconf-udp-notif/
> 
> There is also an HTMLized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-netconf-udp-notif-13
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-netconf-udp-notif-13
> 
> 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]>
>  
> ____________________________________________________________________________________________________________
> 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.