[netconf] Re: I-D Action: draft-ietf-netconf-over-quic-00.txt

[戴锦友 <[e-mail]>]

Hi, Mohamed,
We'll improve the darft based on comments from experts as 
soon as posiible.
With the help of NETCONF chairs and other colleagues, I think
it is sure that we can generate a high-quality document.
Anyhow, not only a good document but also wide and 
benificial applications are expected.
Thank you very much!
Best regards! 




David Dai
Fiberhome Technologies/CICT
Addr: Gaoxin Road 6#, Wuhan, Hubei, China
Tel:  [phone]-8318
MObile: [phone]
Fax:  [phone]
E-mail: [e-mail]
 
From: mohamed.boucadair
Date: 2024-09-25 20:37
To: [e-mail]
Subject: [netconf] Re: I-D Action: draft-ietf-netconf-over-quic-00.txt
Hi authors, all,
 
Now that the document is adopted as a WG item, I think that some serious clean-up is needed to better focus on the key spec :-)
 
I understand that given that the doc was out there since 2019, it cumulates text that might not valid (stale) to motivate the need for a new NETCONF transport. However, parts of that text is questionable and will be a distraction. This actually starts with the abstract with mentions such as TCP or statements such as "QUIC provides useful semantics for Network management" or "difficult  environments". Likewise, no need to mention in the introduction the constrained environments as there are other more suitable solutions such as CoAP, coreconf, etc. Also, text such as the following cites RFCs that are historic since a while:
 
CURRENT:
   The NETCONF protocol is not bound to any particular transport
   protocol, but allows a mapping to define how it can be implemented
   over any specific protocol.  At present, some secure transport
   protocols are defined to carry NETCONF: Secure SHell(SSH)[RFC6242],
   Transport Layer Security(TLS)[RFC7589], Simple Object Access
   Protocol(SOAP)[RFC4743] and Blocks Extensible Exchange
   Protocol(BEEP)[RFC4744].
 
I would also avoid repeating parts of specs that are already in the base NETCONF and QUIC. For example, there is no need to repeat all the same details about the Stream ID types, etc. 
 
Although I expect the mapping to be less complex, I encourage the authors to look into RFC 9250 and leverage it as much as appropriate.
 
Hope this helps.
 
Cheers,
Med
 
> -----Message d'origine-----
> De : [e-mail] <[e-mail]>
> Envoyé : mercredi 25 septembre 2024 03:01
> À : [e-mail]
> Cc : [e-mail]
> Objet : I-D Action: draft-ietf-netconf-over-quic-00.txt
> 
> 
> Internet-Draft draft-ietf-netconf-over-quic-00.txt is now
> available. It is a work item of the Network Configuration
> (NETCONF) WG of the IETF.
> 
>    Title:   NETCONF over QUIC
>    Authors: Jinyou Dai
>             Shaohua Yu
>             Weiqiang Cheng
>             Marc Blanchet
>             Per Andersson
>    Name:    draft-ietf-netconf-over-quic-00.txt
>    Pages:   10
>    Dates:   2024-09-24
> 
> Abstract:
> 
>    The Network Configuration Protocol (NETCONF) provides
> mechanisms to
>    install, manipulate, and delete the configuration of network
> devices.
>    NETCONF can be carried over various transports such as TCP,
> SSH or
>    else.  QUIC provides useful semantics for Network management
> and
>    NETCONF in particular as a single connection can carry
> multiple
>    requests over streams, enabling much better efficiency and
>    performance for both peers.  QUIC provides shorter handshake
> and
>    includes TLS.  QUIC is also more adaptable to more difficult
>    environments such as those with long delays.  This document
> describes
>    how to use NETCONF over the QUIC transport protocol, named
>    NETCONFoQUIC.
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
> Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-netconf-over-
> quic%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C772ad3751
> 5874f6c462c08dcdcfdaec4%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C
> 0%7C638628229336810622%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD
> AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sda
> ta=8WD7bI1kE6HVXl2aWoRBxVxPtTccNpC7iuOU7TOrBRI%3D&reserved=0
> 
> There is also an HTML version available at:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
> Fwww.ietf.org%2Farchive%2Fid%2Fdraft-ietf-netconf-over-quic-
> 00.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C772ad3751
> 5874f6c462c08dcdcfdaec4%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C
> 0%7C638628229336832488%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD
> AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sda
> ta=brX2qWBCKnLl8TVaizHDs6DIYo102OY4J5mMG7wXGDI%3D&reserved=0
> 
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
> 
> 
> _______________________________________________
> I-D-Announce mailing list -- [e-mail] To unsubscribe
> send an email to [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]
To unsubscribe send an email to [e-mail]