Hi Mahesh, Thanks for catching it. I updated the ISIS draft. Each case has a unique case number. Each case might include more than one file (i.e., both OSPF and ISIS models), but I must have submitted one case for each draft to get two different case numbers.
Thanks, Helen From: Mahesh Jethanandani <mjethanand...@gmail.com> Date: Tuesday, April 1, 2025 at 4:28 PM To: Dr. Helen Chen <ingwherc...@mitre.org> Cc: Acee Lindem <acee.i...@gmail.com>, r...@cert.org <r...@cert.org>, The IESG <i...@ietf.org>, draft-ietf-ospf-sr-y...@ietf.org <draft-ietf-ospf-sr-y...@ietf.org>, lsr-chairs <lsr-cha...@ietf.org>, lsr <lsr@ietf.org>, Christian Hopps <cho...@chopps.org> Subject: Re: [EXT] Roman Danyliw's No Objection on draft-ietf-ospf-sr-yang-37: (with COMMENT) Hi Helen, That statement might appear in full in the OSPF draft, but in the ISIS draft, in Section 6, only the following appears: MITRE has approved this document for Public Release, Distribution Unlimited, with Public Release Case Number 19-3033. Hi Helen, That statement might appear in full in the OSPF draft, but in the ISIS draft, in Section 6, only the following appears: MITRE has approved this document for Public Release, Distribution Unlimited, with Public Release Case Number 19-3033. You might want to update it with the complete statement. And does each approval have its own case number? On Mar 31, 2025, at 11:05 AM, Dr. Helen Chen <ingwherc...@mitre.org<mailto:ingwherc...@mitre.org>> wrote: Hello, Thank you to Acee for responding to Roman’s comment about the text in Section 5. The paragraph in its entirety is below, and I would argue that it implicitly denies authority over the approval for publication of the document. “Author affiliation with The MITRE Corporation is provided for identification purposes only, and is not intended to convey or imply MITRE's concurrence with, or support for, the positions, opinions or viewpoints expressed. MITRE has approved this document for Public Release, Distribution Unlimited, with Public Release Case Number 18-3281.” Thanks, Helen P.S. There are other RFCs with this same statement… https://datatracker.ietf.org/doc/rfc8177/<https://urldefense.us/v2/url?u=https-3A__datatracker.ietf.org_doc_rfc8177_&d=DwMFaQ&c=Al8V6E3U0yBSSEuVtdZbGtsvjPA49U3WmtZAsdW0D_Q&r=WVXMYcDyzkUrp4AGAc8mPk-Nx7f5__4hGRNuy7YcFvc&m=vPRBrln3XXzkqaGrLB49sBIULRDnk5WEVwkJq4BfOfR-z0uXTHoo0YX_BrkOnMxl&s=EqMRuqYdY8xfZX3nyxgftBN8_0aoQTAzO62jckt8lOI&e=> https://datatracker.ietf.org/doc/rfc9129/<https://urldefense.us/v2/url?u=https-3A__datatracker.ietf.org_doc_rfc9129_&d=DwMFaQ&c=Al8V6E3U0yBSSEuVtdZbGtsvjPA49U3WmtZAsdW0D_Q&r=WVXMYcDyzkUrp4AGAc8mPk-Nx7f5__4hGRNuy7YcFvc&m=vPRBrln3XXzkqaGrLB49sBIULRDnk5WEVwkJq4BfOfR-z0uXTHoo0YX_BrkOnMxl&s=VT7nhOkM02CzyPveQRuiPGVDosIlUYcoaK3FezkeKIA&e=> From: Acee Lindem <acee.i...@gmail.com<mailto:acee.i...@gmail.com>> Date: Monday, March 31, 2025 at 1:18 PM To: r...@cert.org<mailto:r...@cert.org> <r...@cert.org<mailto:r...@cert.org>> Cc: The IESG <i...@ietf.org<mailto:i...@ietf.org>>, draft-ietf-ospf-sr-y...@ietf.org<mailto:draft-ietf-ospf-sr-y...@ietf.org> <draft-ietf-ospf-sr-y...@ietf.org<mailto:draft-ietf-ospf-sr-y...@ietf.org>>, lsr-chairs <lsr-cha...@ietf.org<mailto:lsr-cha...@ietf.org>>, lsr <lsr@ietf.org<mailto:lsr@ietf.org>>, Christian Hopps <cho...@chopps.org<mailto:cho...@chopps.org>> Subject: [EXT] Re: Roman Danyliw's No Objection on draft-ietf-ospf-sr-yang-37: (with COMMENT) > On Mar 31, 2025, at 12: 55 PM, Roman Danyliw via Datatracker <noreply@ ietf. > org> wrote: > > Roman Danyliw has entered the following ballot position for > > draft-ietf-ospf-sr-yang-37: No Objection > > When responding, please > On Mar 31, 2025, at 12:55 PM, Roman Danyliw via Datatracker > <nore...@ietf.org<mailto:nore...@ietf.org>> wrote: > > Roman Danyliw has entered the following ballot position for > draft-ietf-ospf-sr-yang-37: No Objection > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > Please refer to > https://urldefense.us/v2/url?u=https-3A__www.ietf.org_about_groups_iesg_statements_handling-2Dballot-2Dpositions_&d=DwIFaQ&c=Al8V6E3U0yBSSEuVtdZbGtsvjPA49U3WmtZAsdW0D_Q&r=WVXMYcDyzkUrp4AGAc8mPk-Nx7f5__4hGRNuy7YcFvc&m=rswRuEZ2QztIG1Dg50Ni6me-AfgWrdv4jlz0rQ9U4TtfQdeQCQAhYw3NWCUjYabm&s=AS90HK1kh-yCkZwj_S-tDsa4vfqKc_7do0sYoL_dihA&e= > for more information about how to handle DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > https://urldefense.us/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Dospf-2Dsr-2Dyang_&d=DwIFaQ&c=Al8V6E3U0yBSSEuVtdZbGtsvjPA49U3WmtZAsdW0D_Q&r=WVXMYcDyzkUrp4AGAc8mPk-Nx7f5__4hGRNuy7YcFvc&m=rswRuEZ2QztIG1Dg50Ni6me-AfgWrdv4jlz0rQ9U4TtfQdeQCQAhYw3NWCUjYabm&s=6JrBJn2PLRI2bT5RVOC-DxxJz_u9KbRPtzZIrOGI_4A&e= > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Thank you to Gyan Mishra for the GENART review. > > ** Section 5. > MITRE has approved this document for Public > Release, Distribution Unlimited, with Public Release Case Number > 18-3281. > > While I appreciate the need to acknowledge those that fund an author’s time, > and that some employers have strict release review requirements, is the above > text necessary or can it be removed? It implies that the named entity has > authority to approve the publication of the RFC once the content is in an I-D > (which it does not). This was a requirement for the author to participate with an affiliation. It would be difficult to remove this at this point. Thanks, Acee > > > Mahesh Jethanandani mjethanand...@gmail.com<mailto:mjethanand...@gmail.com>
_______________________________________________ Lsr mailing list -- lsr@ietf.org To unsubscribe send an email to lsr-le...@ietf.org
