Hi, Dan.  Thank you for checking in.  We'll look forward to hearing from you 
after you finish the review.

RFC Editor/lb

> On Jul 24, 2025, at 4:15 AM, Dan Garcia Carrillo <garcia...@uniovi.es> wrote:
> 
> Dear RFC Editor,
> 
> We are working on the review and we will send it soon.
> 
> Thank you.
> 
> Best regards,
> 
> Dan.
> 
> 
> El 18/7/25 a las 19:46, rfc-edi...@rfc-editor.org escribió:
>> *****IMPORTANT*****
>> 
>> Updated 2025/07/18
>> 
>> RFC Author(s):
>> --------------
>> 
>> Instructions for Completing AUTH48
>> 
>> Your document has now entered AUTH48.  Once it has been reviewed and
>> approved by you and all coauthors, it will be published as an RFC.
>> If an author is no longer available, there are several remedies
>> available as listed in the FAQ 
>> (https://urldefense.com/v3/__https://www.rfc-editor.org/faq/__;!!D9dNQwwGXtA!Q-4UZn__cRAzgmY_tfr7GpktB04QugRj8OtKJrbYZ-Wm9UAKb6HmMPbfYOX325c8fp_uDB4bVUdOlnNz4pc5zXZt3A$
>>  ).
>> 
>> You and you coauthors are responsible for engaging other parties
>> (e.g., Contributors or Working Group) as necessary before providing
>> your approval.
>> 
>> Planning your review
>> ---------------------
>> 
>> Please review the following aspects of your document:
>> 
>> *  RFC Editor questions
>> 
>>    Please review and resolve any questions raised by the RFC Editor
>>    that have been included in the XML file as comments marked as
>>    follows:
>> 
>>    <!-- [rfced] ... -->
>> 
>>    These questions will also be sent in a subsequent email.
>> 
>> *  Changes submitted by coauthors
>> 
>>    Please ensure that you review any changes submitted by your
>>    coauthors.  We assume that if you do not speak up that you
>>    agree to changes submitted by your coauthors.
>> 
>> *  Content
>> 
>>    Please review the full content of the document, as this cannot
>>    change once the RFC is published.  Please pay particular attention to:
>>    - IANA considerations updates (if applicable)
>>    - contact information
>>    - references
>> 
>> *  Copyright notices and legends
>> 
>>    Please review the copyright notice and legends as defined in
>>    RFC 5378 and the Trust Legal Provisions
>>    (TLP – 
>> https://urldefense.com/v3/__https://trustee.ietf.org/license-info__;!!D9dNQwwGXtA!Q-4UZn__cRAzgmY_tfr7GpktB04QugRj8OtKJrbYZ-Wm9UAKb6HmMPbfYOX325c8fp_uDB4bVUdOlnNz4peoFu6aZQ$
>>  ).
>> 
>> *  Semantic markup
>> 
>>    Please review the markup in the XML file to ensure that elements of
>>    content are correctly tagged.  For example, ensure that <sourcecode>
>>    and <artwork> are set correctly.  See details at
>>    
>> <https://urldefense.com/v3/__https://authors.ietf.org/rfcxml-vocabulary__;!!D9dNQwwGXtA!Q-4UZn__cRAzgmY_tfr7GpktB04QugRj8OtKJrbYZ-Wm9UAKb6HmMPbfYOX325c8fp_uDB4bVUdOlnNz4peVCUtEng$
>>  >.
>> 
>> *  Formatted output
>> 
>>    Please review the PDF, HTML, and TXT files to ensure that the
>>    formatted output, as generated from the markup in the XML file, is
>>    reasonable.  Please note that the TXT will have formatting
>>    limitations compared to the PDF and HTML.
>> 
>> 
>> Submitting changes
>> ------------------
>> 
>> To submit changes, please reply to this email using ‘REPLY ALL’ as all
>> the parties CCed on this message need to see your changes. The parties
>> include:
>> 
>>    *  your coauthors
>>        *  rfc-edi...@rfc-editor.org (the RPC team)
>> 
>>    *  other document participants, depending on the stream (e.g.,
>>       IETF Stream participants are your working group chairs, the
>>       responsible ADs, and the document shepherd).
>>          *  auth48archive@rfc-editor.org, which is a new archival mailing 
>> list
>>       to preserve AUTH48 conversations; it is not an active discussion
>>       list:
>>            *  More info:
>>         
>> https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc__;!!D9dNQwwGXtA!Q-4UZn__cRAzgmY_tfr7GpktB04QugRj8OtKJrbYZ-Wm9UAKb6HmMPbfYOX325c8fp_uDB4bVUdOlnNz4peccNc_Lg$
>>            *  The archive itself:
>>         
>> https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/browse/auth48archive/__;!!D9dNQwwGXtA!Q-4UZn__cRAzgmY_tfr7GpktB04QugRj8OtKJrbYZ-Wm9UAKb6HmMPbfYOX325c8fp_uDB4bVUdOlnNz4pctP0UtqQ$
>> 
>>      *  Note: If only absolutely necessary, you may temporarily opt out
>>         of the archiving of messages (e.g., to discuss a sensitive matter).
>>         If needed, please add a note at the top of the message that you
>>         have dropped the address. When the discussion is concluded,
>>         auth48archive@rfc-editor.org will be re-added to the CC list and
>>         its addition will be noted at the top of the message.
>> 
>> You may submit your changes in one of two ways:
>> 
>> An update to the provided XML file
>>  — OR —
>> An explicit list of changes in this format
>> 
>> Section # (or indicate Global)
>> 
>> OLD:
>> old text
>> 
>> NEW:
>> new text
>> 
>> You do not need to reply with both an updated XML file and an explicit
>> list of changes, as either form is sufficient.
>> 
>> We will ask a stream manager to review and approve any changes that seem
>> beyond editorial in nature, e.g., addition of new text, deletion of text,
>> and technical changes.  Information about stream managers can be found in
>> the FAQ.  Editorial changes do not require approval from a stream manager.
>> 
>> 
>> Approving for publication
>> --------------------------
>> 
>> To approve your RFC for publication, please reply to this email stating
>> that you approve this RFC for publication.  Please use ‘REPLY ALL’,
>> as all the parties CCed on this message need to see your approval.
>> 
>> 
>> Files
>> -----
>> 
>> The files are available here:
>>    
>> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9820.xml__;!!D9dNQwwGXtA!Q-4UZn__cRAzgmY_tfr7GpktB04QugRj8OtKJrbYZ-Wm9UAKb6HmMPbfYOX325c8fp_uDB4bVUdOlnNz4pcF_D8abA$
>>    
>> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9820.html__;!!D9dNQwwGXtA!Q-4UZn__cRAzgmY_tfr7GpktB04QugRj8OtKJrbYZ-Wm9UAKb6HmMPbfYOX325c8fp_uDB4bVUdOlnNz4pemNRAYPw$
>>    
>> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9820.pdf__;!!D9dNQwwGXtA!Q-4UZn__cRAzgmY_tfr7GpktB04QugRj8OtKJrbYZ-Wm9UAKb6HmMPbfYOX325c8fp_uDB4bVUdOlnNz4pfbwFhUiQ$
>>    
>> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9820.txt__;!!D9dNQwwGXtA!Q-4UZn__cRAzgmY_tfr7GpktB04QugRj8OtKJrbYZ-Wm9UAKb6HmMPbfYOX325c8fp_uDB4bVUdOlnNz4peNhMebQQ$
>> 
>> Diff file of the text:
>>    
>> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9820-diff.html__;!!D9dNQwwGXtA!Q-4UZn__cRAzgmY_tfr7GpktB04QugRj8OtKJrbYZ-Wm9UAKb6HmMPbfYOX325c8fp_uDB4bVUdOlnNz4pdPHMgdUQ$
>>    
>> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9820-rfcdiff.html__;!!D9dNQwwGXtA!Q-4UZn__cRAzgmY_tfr7GpktB04QugRj8OtKJrbYZ-Wm9UAKb6HmMPbfYOX325c8fp_uDB4bVUdOlnNz4pdAEEenow$
>>   (side by side)
>> 
>> Diff of the XML:
>>    
>> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9820-xmldiff1.html__;!!D9dNQwwGXtA!Q-4UZn__cRAzgmY_tfr7GpktB04QugRj8OtKJrbYZ-Wm9UAKb6HmMPbfYOX325c8fp_uDB4bVUdOlnNz4pfMV4SnqA$
>> 
>> 
>> Tracking progress
>> -----------------
>> 
>> The details of the AUTH48 status of your document are here:
>>    
>> https://urldefense.com/v3/__https://www.rfc-editor.org/auth48/rfc9820__;!!D9dNQwwGXtA!Q-4UZn__cRAzgmY_tfr7GpktB04QugRj8OtKJrbYZ-Wm9UAKb6HmMPbfYOX325c8fp_uDB4bVUdOlnNz4peKJ6bRiw$
>> 
>> Please let us know if you have any questions.
>> 
>> Thank you for your cooperation,
>> 
>> RFC Editor
>> 
>> --------------------------------------
>> RFC9820 (draft-ietf-ace-wg-coap-eap-15)
>> 
>> Title            : EAP-based Authentication Service for CoAP
>> Author(s)        : R. Marin-Lopez, D. Garcia-Carrillo
>> WG Chair(s)      : Loganaden Velvindron, Tim Hollebeek
>> 
>> Area Director(s) : Deb Cooley, Paul Wouters
>> 
>> 
> 

-- 
auth48archive mailing list -- auth48archive@rfc-editor.org
To unsubscribe send an email to auth48archive-le...@rfc-editor.org

Reply via email to