Hi Rich, Thank you for your reply! The markdown looks great.
Sincerely, Sarah Tarrant RFC Production Center > On Jun 6, 2026, at 6:58 PM, Salz, Rich <[email protected]> > wrote: > > >1) As there may have been multiple updates made to the document during Last > >Call, > >please review the current version of the document: > >* Is the text in the Abstract still accurate? > >* Are the Authors' Addresses, Contributors, and Acknowledgments > >sections current? > > Yes they are accurate. > > >2) Please share any style information that could help us with editing your > >document. For example: > >* Is your document's format or its terminology based on another document, > >WG style guide, etc.? > > No. > > >* Is there a general pattern of capitalization or formatting of terms that > >editors can follow (e.g., "Field names should have initial capitalization."? > > No. > > >3) Please carefully review the entries and their URLs in the > >References section with the following in mind. Note that we will > >update as follows unless we hear otherwise at this time: > > They should all be current. > > >4) Is there any text that requires special handling? > > No. > > >5) Would you like to participate in the RPC Pilot Test for editing in > >kramdown-rfc? > > Yes, source is attached. > > >6) Would you like to participate in the RPC Pilot Test for completing Final > >Review > >in GitHub? If so, please let us know and provide all author, AD, and/or > >document > >shepherd GitHub usernames. For more information about this experiment, see: > >https://www.rfc-editor.org/rpc/wiki/doku.php?id=rpc-github-phase-0-pilot-test$ > > . > > Authors: > Rich Salz richsalz > Mike Bishop MikeBishop > Marius Kleidl acconut > AD: > Gorry Fairhurst gorryfair > Shepherd: > Darrel Miller darrelmiller > > >7) Is there anything else that the RPC should be aware of while editing this > >document? > > Nope. > <draft-ietf-httpapi-privacy.md> -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
