Re: [auth48] AUTH48: RFC-to-be 9536 <draft-ietf-regext-rdap-reverse-search-25> for your review

[Mario Loffredo <[e-mail]>]

Hi Alanna,

thanks a lot for informing us.


Best,

Mario

Il 12/03/2024 20:52, Alanna Paloma ha scritto:
> Hi Mario and Maurizio,
>
> You approvals have been noted on the AUTH48 status page:
> https://www.rfc-editor.org/auth48/rfc9536
>
> Once we have received Murray’s approval, we will move this document forward in the publication process.
>
> Thank you,
> RFC Editor/ap
>
>> On Mar 12, 2024, at 5:08 AM, Maurizio Martinelli <maurizio.martinelli=[e-mail]> wrote:
>>
>> Me too.
>>
>> Best,
>> Maurizio
>>
>>
>>> Il giorno 12 mar 2024, alle ore 09:13, Mario Loffredo <[e-mail]> ha scritto:
>>>
>>> I approve this RFC for publication.
>>> Mario
>>> Il 08/03/2024 23:01, [e-mail] ha scritto:
>>>> *****IMPORTANT*****
>>>>
>>>> Updated 2024/03/08
>>>>
>>>> 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://www.rfc-editor.org/faq/).
>>>>
>>>> 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://trustee.ietf.org/license-info/).
>>>>
>>>> * 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://authors.ietf.org/rfcxml-vocabulary>.
>>>>
>>>> * 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
>>>>
>>>> * [e-mail] (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).
>>>>
>>>> * [e-mail], which is a new archival mailing list
>>>> to preserve AUTH48 conversations; it is not an active discussion
>>>> list:
>>>>
>>>> * More info:
>>>> https://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc
>>>>
>>>> * The archive itself:
>>>> https://mailarchive.ietf.org/arch/browse/auth48archive/
>>>>
>>>> * 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,
>>>> [e-mail] 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://www.rfc-editor.org/authors/rfc9536.xml
>>>> https://www.rfc-editor.org/authors/rfc9536.html
>>>> https://www.rfc-editor.org/authors/rfc9536.pdf
>>>> https://www.rfc-editor.org/authors/rfc9536.txt
>>>>
>>>> Diff file of the text:
>>>> https://www.rfc-editor.org/authors/rfc9536-diff.html
>>>> https://www.rfc-editor.org/authors/rfc9536-rfcdiff.html (side by side)
>>>>
>>>> Diff of the XML:
>>>> https://www.rfc-editor.org/authors/rfc9536-xmldiff1.html
>>>>
>>>> The following files are provided to facilitate creation of your own
>>>> diff files of the XML.
>>>>
>>>> Initial XMLv3 created using XMLv2 as input:
>>>> https://www.rfc-editor.org/authors/rfc9536.original.v2v3.xml
>>>>
>>>> XMLv3 file that is a best effort to capture v3-related format updates
>>>> only:
>>>> https://www.rfc-editor.org/authors/rfc9536.form.xml
>>>>
>>>>
>>>> Tracking progress
>>>> -----------------
>>>>
>>>> The details of the AUTH48 status of your document are here:
>>>> https://www.rfc-editor.org/auth48/rfc9536
>>>>
>>>> Please let us know if you have any questions.
>>>>
>>>> Thank you for your cooperation,
>>>>
>>>> RFC Editor
>>>>
>>>> --------------------------------------
>>>> RFC9536 (draft-ietf-regext-rdap-reverse-search-25)
>>>>
>>>> Title : Registration Data Access Protocol (RDAP) Reverse Search
>>>> Author(s) : M. Loffredo, M. Martinelli
>>>> WG Chair(s) : James Galvin, Antoin Verschuren
>>>>
>>>> Area Director(s) : Murray Kucherawy, Francesca Palombini
>>>>
>>>>
>>>>
>>> -- 
>>> Dott. Mario Loffredo
>>> Senior Technologist
>>> Technological Unit “Digital Innovation”
>>> Institute of Informatics and Telematics (IIT)
>>> National Research Council (CNR)
>>> via G. Moruzzi 1, I-56124 PISA, Italy
>>> Phone: [phone]
>>> Web: http://www.iit.cnr.it/mario.loffredo
>> ----
>> Dr. Maurizio Martinelli
>> Dirigente Tecnologo
>> Responsabile Unità Tecnologica Innovazione Digitale
>> CNR - Istituto di Informatica e Telematica
>> via G. Moruzzi 1, 56124 PISA, Italy
>> E-Mail: [e-mail]
>> Phone: [phone]
>> Web: http://www.iit.cnr.it/maurizio.martinelli
>>
-- 
Dott. Mario Loffredo
Senior Technologist
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: [phone]
Web: http://www.iit.cnr.it/mario.loffredo