Hello Giri, Per your request, we have removed "Mediatek USA". Please see the updated file.
We will proceed with the publication process. The updated XML file is here: https://www.rfc-editor.org/authors/rfc9711.xml The updated output files are here: https://www.rfc-editor.org/authors/rfc9711.txt https://www.rfc-editor.org/authors/rfc9711.pdf https://www.rfc-editor.org/authors/rfc9711.html These diff files show all changes made during AUTH48: https://www.rfc-editor.org/authors/rfc9711-auth48diff.html https://www.rfc-editor.org/authors/rfc9711-auth48rfcdiff.html (side by side) These diff files show all changes made to date: https://www.rfc-editor.org/authors/rfc9711-diff.html https://www.rfc-editor.org/authors/rfc9711-rfcdiff.html (side by side) Thank you! RFC Editor/kc > On Apr 28, 2025, at 1:23 PM, Giridhar Mandyam <giridhar.mand...@gmail.com> > wrote: > > Sorry for the last minute request, but please remove my affiliation from the > final copy (Mediatek). I am no longer with this company, and my new company > has not confirmed approval for adding their names to the RFC. > > Thanks, > -Giri > > On Mon, Apr 28, 2025, 12:43 PM Karen Moore <kmo...@staff.rfc-editor.org> > wrote: > Dear Laurence, Giri, Jeremy, and Carl, > > IANA has completed the requested updates to their registries. As all actions > are complete and we have all necessary approvals, I’m pleased to announce > that the AUTH48 process has concluded for this document. We will now move the > document through the publication process, and we will reach out if we have > any further questions. > > Thank you to all for your time and for working closely with us to finalize > this sizable document! > > Best regards, > RFC Editor/kc > > > > On Apr 23, 2025, at 11:53 AM, Karen Moore <kmo...@staff.rfc-editor.org> > > wrote: > > > > Hi Roman! > > > > Thank you for providing your approval of the changes; we have updated the > > AUTH48 page at "https://www.rfc-editor.org/auth48/rfc9767"; to reflect the > > status. > > > > We will now ask IANA to update their registries to match the edited > > document. Once they have completed the process, we will inform the authors. > > > > Best regards, > > RFC Editor/kc > > > >> On Apr 23, 2025, at 11:02 AM, Roman Danyliw via auth48archive > >> <auth48archive@rfc-editor.org> wrote: > >> > >> Hi Karen! > >> > >> I confirmed with the WG. I approved these changes. > >> > >> Roman > >> > >> -----Original Message----- > >> From: Karen Moore <kmo...@staff.rfc-editor.org> > >> Sent: Wednesday, April 23, 2025 1:19 PM > >> To: Roman Danyliw <r...@cert.org>; lgl securitytheory.com > >> <l...@securitytheory.com>; Giridhar Mandyam <giridhar.mand...@gmail.com>; > >> Jeremy O'Donoghue <jodon...@qti.qualcomm.com>; Carl Wallace > >> <c...@redhoundsoftware.com> > >> Cc: RFC Editor <rfc-edi...@rfc-editor.org>; rats-...@ietf.org; rats-chairs > >> <rats-cha...@ietf.org>; Smith, Ned <ned.sm...@intel.com>; auth48archive > >> <auth48archive@rfc-editor.org> > >> Subject: AD [auth48] AUTH48: RFC-to-be 9711 <draft-ietf-rats-eat-31> for > >> your review > >> > >> Warning: External Sender - do not click links or open attachments unless > >> you recognize the sender and know the content is safe. > >> > >> > >> Hi Laurence and *Roman (AD), > >> > >> Thank you for your reply. > >> > >> *Roman, please let us know the status of this document. Note that we await > >> your approval of the following, which can be viewed at > >> https://www.rfc-editor.org/authors/rfc9711-auth48diff.html: > >> > >> Sections 3, 4.1, 4.2.3.2, 4.2.3.3, 4.2.10, 4.2.18, 5, 6.3.6, 7.3, 7.3.1, > >> 7.3.2, and 9.1 Appendices A.1.7, A.2.2, A.2.3, B.2, and D > >> > >> —Files (please refresh)— > >> > >> The updated XML file is here: > >> https://www.rfc-editor.org/authors/rfc9711.xml > >> > >> The updated output files are here: > >> https://www.rfc-editor.org/authors/rfc9711.txt > >> https://www.rfc-editor.org/authors/rfc9711.pdf > >> https://www.rfc-editor.org/authors/rfc9711.html > >> > >> These diff files show all changes made during AUTH48: > >> https://www.rfc-editor.org/authors/rfc9711-auth48diff.html > >> https://www.rfc-editor.org/authors/rfc9711-auth48rfcdiff.html (side by > >> side) > >> > >> These diff files show only the change made during the last editing round: > >> https://www.rfc-editor.org/authors/rfc9711-lastdiff.html > >> https://www.rfc-editor.org/authors/rfc9711-lastrfcdiff.html (side by side) > >> > >> These diff files show all changes made to date: > >> https://www.rfc-editor.org/authors/rfc9711-diff.html > >> https://www.rfc-editor.org/authors/rfc9711-rfcdiff.html (side by side) > >> > >> Thank you, > >> RFC Editor/kc > >> > >>> On Apr 21, 2025, at 9:43 AM, Laurence Lundblade via auth48archive > >>> <auth48archive@rfc-editor.org> wrote: > >>> > >>> Hi Karen, > >>> > >>> I went through and checked all 19 instances (7 I asked for, plus 12 you > >>> found). They all look good. Thank you for taking the initiative and > >>> fixing them all to make the document consistent! > >>> > >>> LL > >>> > >>> > >>>> On Apr 18, 2025, at 4:56 PM, Karen Moore <kmo...@staff.rfc-editor.org> > >>>> wrote: > >>>> > >>>> Hello Laurence, > >>>> > >>>> We believe the request is to make “Section X of [RFCXXX]” all one > >>>> clickable link; however, that format is not currently used in the RFC > >>>> series. Note that there are 19 instances of “Section X of [RFCXXX]”, so > >>>> only updating the 7 instances that were outlined in GitHub would > >>>> introduce inconsistency within the document (as well as within the RFC > >>>> series). > >>>> > >>>> Note that we did find one reference that was not clickable; we updated > >>>> the format as follows: > >>>> > >>>> OLD: > >>>> When COSE protection is used, the profile should specify whether COSE > >>>> tags are used or not. > >>>> Note that RFC 8392 requires COSE tags be used in a CWT tag. > >>>> > >>>> NEW: > >>>> When COSE protection is used, the profile should specify whether COSE > >>>> tags are used or not. > >>>> Note that [RFC8392] requires COSE tags be used in a CWT tag. > >>>> > >>>> —Files (please refresh)— > >>>> > >>>> The updated XML file is here: > >>>> https://www.rfc-editor.org/authors/rfc9711.xml > >>>> > >>>> The updated output files are here: > >>>> https://www.rfc-editor.org/authors/rfc9711.txt > >>>> https://www.rfc-editor.org/authors/rfc9711.pdf > >>>> https://www.rfc-editor.org/authors/rfc9711.html > >>>> > >>>> These diff files show all changes made during AUTH48: > >>>> https://www.rfc-editor.org/authors/rfc9711-auth48diff.html > >>>> https://www.rfc-editor.org/authors/rfc9711-auth48rfcdiff.html (side > >>>> by side) > >>>> > >>>> These diff files show only the change made during the last editing round: > >>>> https://www.rfc-editor.org/authors/rfc9711-lastdiff.html > >>>> https://www.rfc-editor.org/authors/rfc9711-lastrfcdiff.html (side by > >>>> side) > >>>> > >>>> These diff files show all changes made to date: > >>>> https://www.rfc-editor.org/authors/rfc9711-diff.html > >>>> https://www.rfc-editor.org/authors/rfc9711-rfcdiff.html (side by > >>>> side) > >>>> > >>>> Best regards, > >>>> RFC Editor/kc > >>>> > >>>>> On Apr 18, 2025, at 10:03 AM, Laurence Lundblade > >>>>> <l...@securitytheory.com> wrote: > >>>>> > >>>>> Hi RFC Editor, > >>>>> > >>>>> As part of the review Roman conducted on the Location NULL/NaN issue a > >>>>> suggestion was made to improve the references to sections of referenced > >>>>> RFCs. The EAT authors would like to request the following changes. The > >>>>> change is only to make the “Section X” a clickable link. > >>>>> > >>>>> Old: > >>>>> Section X of {{RFCYYYY}} > >>>>> > >>>>> New: > >>>>> {{Section X of RFCYYYY}} > >>>>> > >>>>> There are 7 occurrences of this. > >>>>> > >>>>> You can see the change in the EAT GitHub repo here: > >>>>> https://github.com/ietf-rats-wg/eat/commit/462fbba8cf1449bbd648f3ec3 > >>>>> f4f10af02b07ae4 > >>>>> > >>>>> Thank you! > >>>>> > >>>>> LL > >>>> > >>> > >>> -- > >>> auth48archive mailing list -- auth48archive@rfc-editor.org To > >>> unsubscribe send an email to auth48archive-le...@rfc-editor.org > >> > >> -- > >> auth48archive mailing list -- auth48archive@rfc-editor.org > >> To unsubscribe send an email to auth48archive-le...@rfc-editor.org > > > -- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
