Hi Kent, Please see inline.
Cheers, Med De : Kent Watsen <kent+i...@watsen.net> Envoyé : jeudi 12 septembre 2024 13:04 À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com> Cc : Mahesh Jethanandani <mjethanand...@gmail.com>; netmod@ietf.org Objet : Re: [netmod] AD - Re: AUTH48: RFC-to-be 9644 <draft-ietf-netconf-ssh-client-server-40> for your review Hi Med, On Sep 12, 2024, at 3:14 AM, mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com> wrote: Hi Mahesh, Please see inline. Cheers, Med De : Mahesh Jethanandani <mjethanand...@gmail.com<mailto:mjethanand...@gmail.com>> Envoyé : jeudi 12 septembre 2024 00:49 À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>> Cc : Kent Watsen <kent+i...@watsen.net<mailto:kent+i...@watsen.net>>; netmod@ietf.org<mailto:netmod@ietf.org> Objet : Re: [netmod] AD - Re: AUTH48: RFC-to-be 9644 <draft-ietf-netconf-ssh-client-server-40> for your review Hi Med, The reference of QUIC is to the protocol, RFC 9000, not NETCONF over QUIC, an I-D as you note; just as the reference is to SSH protocol, RFC 4252, not NETCONF over SSH, RFC 6242. [Med] I understand the intent is to cite the transport themselves, but the text refers to MTI of these “YANG-based management protocols”. I don’t think we can make any claim about QUIC here as we don’t have an authoritative spec for that. If we want to cite QUIC, some further tweaking to the text is needed, IMO. RESTCONF already supports QUIC. [Med] Yes, RETCONF does not require a specific version of HTTP but still TLS is what is indicated as MTI for RC per rfc8040#section-2.1. No transport-binding document will be written to enable QUIC for RC. [Med] Isn’t rfc9114 that is applicable for RC, rather than 9000? On Sep 11, 2024, at 2:57 AM, mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com> wrote: Hi Kent, I like the NEWER better compared to the initial NEW you shared, however I think some more tweaking is needed. I understand why you cited QUIC as well, but we don’t have formally a spec for mapping with QUIC (I know there is an individual I-D). We actually don’t need to be exhaustive here and cite every transport option. The proposed NEWER changes a little bit the approach from the **recommending the use of MTI** to simply listing available MTI. [mj] Why do you say that? The statement says the protocols have mandatory-to-implement … [Med] Having an MTI does not mean that MTI is actually used/enabled. Touché :) One could process “implement” to be at the runtime-level or code-level. I meant the former, and see that you’re interpreting the later, which is fair. First, I wonder if there isn’t a formal definition for MTI that disambiguates the two cases. Looking, I see MTI used in the context of algorithms, which lends itself to the “code level” interpretation. Fine. [Med] Thanks Then either s/implement/use/ or s/-to-implement// ? [Med] « have to use » would be better, IMO. Separately, I see your update is different in a couple ways. Please see below for details… Cheers, Med De : Kent Watsen <kent+i...@watsen.net<mailto:kent+i...@watsen.net>> Envoyé : mercredi 11 septembre 2024 00:10 À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>> Cc : netmod@ietf.org<mailto:netmod@ietf.org> Objet : Re: [netmod] AD - Re: AUTH48: RFC-to-be 9644 <draft-ietf-netconf-ssh-client-server-40> for your review Hi Med, NEWER (this is what I’m asking RFC Editor to do for the suite of client-server drafts) This section is modeled after the template described in Section 3.7 of [RFCAAAA]. This first line wasn’t picked up. Note that the word “modeled” gives an authors a little flexibility, as is needed sometimes. To point, the RFC Editor takes the words literally and raise issues when things aren’t exactly same…until this word was changed. Honestly, the same should be done to all of the templates defined in the document. [Med] This is fair. Please see: https://github.com/netmod-wg/rfc8407bis/commit/972970ce16c050d8420f50f07637f4e00770cdd5 The "<module-name>" YANG module defines a data model that is designed to be accessed via YANG- IIRC, you use different words than “data model”. I’m trying to use sufficiently ambiguous language that includes also modules that only define identities, or only enumerations, or only typedefs, etc. I was going to write “data model, or parts of data models,” but it seemed unnecessary wordy and obscures the main point of the sentence. I don’t deny that my text could be improved, but your take didn’t seem right either. FWIW, I only know about your changes to my text because I received GitHub notifications. Was a link for the PR sent? In any case, it would’ve been nice if you’d stated that changes had been made, rather than me having to discover them on my own. [Med] I didn’t share the PR because that wasn’t ready yet and I was waiting for the discussion to converge to have something I’m more happy with it. Now that you are on it, feel free to propose your edits directly there :-) Thanks. Kent // contributor ____________________________________________________________________________________________________________ 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.
_______________________________________________ netmod mailing list -- netmod@ietf.org To unsubscribe send an email to netmod-le...@ietf.org
