Thanks, Madison!  I read through the doc and looked through your diffs again.  
I think it looks fine.

Joe

From: Madison Church <[email protected]>
Date: Monday, March 17, 2025 at 15:24
To: Joe Clarke (jclarke) <[email protected]>, Mahesh Jethanandani 
<[email protected]>, [email protected] <[email protected]>, 
[email protected] 
<[email protected]>
Cc: RFC Editor <[email protected]>, [email protected] 
<[email protected]>, [email protected] <[email protected]>, 
[email protected] <[email protected]>, Warren Kumari <[email protected]>, 
[email protected] <[email protected]>
Subject: Re: AUTH48: RFC-to-be 9742 <draft-ietf-netmod-syslog-model-33> for 
your review
Hi Authors,

Joe - Thank you for the confirmation!

All - Now that our questions have been addressed, please review the document 
carefully to ensure satisfaction as we do not make changes once it has been 
published as an RFC. Contact us with any further updates or with your approval 
of the document in its current form. We will await approvals from each author 
prior to moving forward in the publication process.

Updated files have been posted here (please refresh):
  https://www.rfc-editor.org/authors/rfc9742.txt
  https://www.rfc-editor.org/authors/rfc9742.pdf
  https://www.rfc-editor.org/authors/rfc9742.html
  https://www.rfc-editor.org/authors/rfc9742.xml

Updated diff files:
  https://www.rfc-editor.org/authors/rfc9742-diff.html (comprehensive edits)
  https://www.rfc-editor.org/authors/rfc9742-rfcdiff.html (side by side)
  https://www.rfc-editor.org/authors/rfc9742-auth48diff.html (AUTH48 changes 
only)
  https://www.rfc-editor.org/authors/rfc9742-auth48rfcdiff.html (side by side)

For the AUTH48 status page, see:
  https://www.rfc-editor.org/auth48/rfc9742

Thank you,
RFC Editor/mc

> On Mar 14, 2025, at 1:53 AM, Joe Clarke (jclarke) <[email protected]> wrote:
>
>
> [rfced] Thank you for pointing this out (and apologies for missing this 
> earlier). We have updated the Security Considerations section to match what 
> appears in 8407bis [1].
>
> Additionally, please note that we have removed the following text from the 
> Security Considerations to match 8407bis. If this text should be re-added to 
> the paragraph (or if there are any further updates needed), please let us 
> know.
> [JMC] You know, I don’t think it’s needed in light of the boilerplate text 
> indicating an impact to operations if these data nodes are not protected.  
> I’m good with the sec considerations as they read now.
> Joe
-- 
auth48archive mailing list -- [email protected]
To unsubscribe send an email to [email protected]
  • [auth48] Re: AUTH48: ... RFC Editor via auth48archive
    • [auth48] Re: AUT... Joe Clarke (jclarke) via auth48archive
      • [auth48] Re:... Mahesh Jethanandani via auth48archive
        • [auth48]... Madison Church via auth48archive
          • [aut... Joe Clarke (jclarke) via auth48archive
            • ... Madison Church via auth48archive
              • ... Joe Clarke (jclarke) via auth48archive
                • ... Madison Church via auth48archive
                • ... Joe Clarke (jclarke) via auth48archive
                • ... Joe Clarke (jclarke) via auth48archive
                • ... Madison Church via auth48archive
                • ... Joe Clarke (jclarke) via auth48archive
                • ... Madison Church via auth48archive
                • ... Mahesh Jethanandani via auth48archive
                • ... Madison Church via auth48archive
                • ... Madison Church via auth48archive
                • ... Joe Clarke (jclarke) via auth48archive
                • ... Mahesh Jethanandani via auth48archive
                • ... Agrahara Sreenivasa, Kiran Koushik via auth48archive

Reply via email to