Re: [netmod] [Editorial Errata Reported] RFC8407 (7791)

[[e-mail]]

Hi all, 

Here is an update on the initial comments from Dale:

> > 1) It would be helpful if the beginning of the template contained a
> > reference to RFC 8407 to provide a pointer back to where the
> templated
> > section of Yang module definitions was instantiated from.  Perhaps
> > starting the template with "[Instantiated from the template of
> > [RFC8407] section 3.7.1.]"
> >

After discussion with Dale, this PR is created: https://github.com/boucadair/rfc8407bis/pull/36/files. This will be merged into the next iteration of i-d.rfc8407bis. 

> > 2) While the URL given in RFC 8407 works, the URL given in the
> online
> > template only goes to a generic page, "Welcome to the IETF Community
> > Wiki".  Presumably the URL in the online template should be the URL
> of
> > that page itself.

The secretariat helped fixing the broken link. 

With these actions, I think that the erratum can be safely rejected.

Cheers,
Med

> -----Message d'origine-----
> De : BOUCADAIR Mohamed INNOV/NET
> Envoyé : mardi 30 janvier 2024 18:53
> À : 'RFC Errata System' <[e-mail]>;
> [e-mail]
> Cc : [e-mail]
> Objet : RE: [netmod] [Editorial Errata Reported] RFC8407 (7791)
> 
> Hi Dale, all,
> 
> I don't think filling an erratum is appropriate here given that the
> original text is not broken (including the URL). I suggest to reject
> it.
> 
> However, text enhancements can be considered as part of
> https://datatracker.ietf.org/doc/draft-ietf-netmod-rfc8407bis/. Let's
> have that discussion. Thanks.
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : netmod <[e-mail]> De la part de RFC Errata
> System
> > Envoyé : mardi 30 janvier 2024 18:01 À : [e-mail]
> Cc
> > : [e-mail]; [e-mail] Objet : [netmod] [Editorial
> > Errata Reported] RFC8407 (7791)
> >
> > The following errata report has been submitted for RFC8407,
> > "Guidelines for Authors and Reviewers of Documents Containing YANG
> > Data Models".
> >
> > --------------------------------------
> > You may review the report below and at:
> >
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> > rfc-
> >
> editor.org%2Ferrata%2Feid7791&data=05%7C02%7Cmohamed.boucadair%40orang
> >
> e.com%7C2cb3e186d23d4eac917208dc21b511f8%7C90c7a20af34b40bfbc48b9253b6
> >
> f5d20%7C0%7C0%7C638422308774178382%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4
> >
> wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&s
> > data=6Qi9sKVPa44FCI8dW984szRS1EZso%2FpPr%2BRDnsGkobE%3D&reserved=0
> >
> > --------------------------------------
> > Type: Editorial
> > Reported by: Dale R. Worley <[e-mail]>
> >
> > Section: GLOBAL
> >
> > Original Text
> > -------------
> > There are two related items.
> >
> > 1) Section 3.7.1 "Security Considerations Section Template" begins
> >
> >    X.  Security Considerations
> >
> >    The YANG module specified in this document defines a schema for
> > data
> >    that is designed to be accessed via network management protocols
> > such
> >    as NETCONF [RFC6241] or RESTCONF [RFC8040].  The lowest NETCONF
> > layer
> >    is the secure transport layer, and the mandatory-to-implement
> > secure
> >    transport is Secure Shell (SSH) [RFC6242].  The lowest RESTCONF
> > layer
> >    is HTTPS, and the mandatory-to-implement secure transport is TLS
> >    [RFC8446].
> >
> > 2) RFC 8470 says "the latest approved template (available at
> <https://trac.ietf.org/trac/ops/wiki/yang-security-guidelines>)".  But
> the template at that URL says "the latest approved template (available
> at http://trac.tools.ietf.org/area/ops/trac/wiki/yang-security-
> guidelines).">
> >
> > Corrected Text
> > --------------
> > 1) It would be helpful if the beginning of the template contained a
> > reference to RFC 8407 to provide a pointer back to where the
> templated
> > section of Yang module definitions was instantiated from.  Perhaps
> > starting the template with "[Instantiated from the template of
> > [RFC8407] section 3.7.1.]"
> >
> > 2) While the URL given in RFC 8407 works, the URL given in the
> online
> > template only goes to a generic page, "Welcome to the IETF Community
> > Wiki".  Presumably the URL in the online template should be the URL
> of
> > that page itself.
> >
> >
> >
> > Notes
> > -----
> > Item (2) is a straightforward correction.  Item (1) is in service to
> > having better pointers/references in our documents.
> >
> > Instructions:
> > -------------
> > This erratum is currently posted as "Reported". (If it is spam, it
> > will be removed shortly by the RFC Production Center.) Please use
> > "Reply All" to discuss whether it should be verified or rejected.
> When
> > a decision is reached, the verifying party will log in to change the
> > status and edit the report, if necessary.
> >
> > --------------------------------------
> > RFC8407 (draft-ietf-netmod-rfc6087bis-20)
> > --------------------------------------
> > Title               : Guidelines for Authors and Reviewers of
> > Documents Containing YANG Data Models
> > Publication Date    : October 2018
> > Author(s)           : A. Bierman
> > Category            : BEST CURRENT PRACTICE
> > Source              : Network Modeling
> > Area                : Operations and Management
> > Stream              : IETF
> > Verifying Party     : IESG
> >
> > _______________________________________________
> > netmod mailing list
> > [e-mail]
> >
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> >
> ietf.org%2Fmailman%2Flistinfo%2Fnetmod&data=05%7C02%7Cmohamed.boucadai
> >
> r%40orange.com%7C2cb3e186d23d4eac917208dc21b511f8%7C90c7a20af34b40bfbc
> >
> 48b9253b6f5d20%7C0%7C0%7C638422308774195518%7CUnknown%7CTWFpbGZsb3d8ey
> >
> JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7
> >
> C%7C%7C&sdata=leytvbSQ1TP9MT8wI1X5ZmoVMlpuC8k6UCRs40pfXv8%3D&reserved=
> > 0
____________________________________________________________________________________________________________
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.