Hi Sean,

We have noted your approval on the AUTH48 status page for this document 
(https://www.rfc-editor.org/auth48/rfc9712).

We now have all necessary approvals and will move this document forward in the 
publication process.

Thank you for your time!

Best regards,
RFC Editor/kc

> On Jan 22, 2025, at 6:27 PM, Sean Turner <s...@sn3rd.com> wrote:
> 
> I approve the document in its current form.
> 
> spt
> 
>> On Jan 22, 2025, at 5:42 PM, Karen Moore <kmo...@staff.rfc-editor.org> wrote:
>> 
>> Hi Sean and Jay,
>> 
>> Thank you for your replies. We have updated our files accordingly. Sean, 
>> please review and let us know if you have any further changes or if you 
>> approve the document in its current form.
>> 
>> —Files (please refresh)—
>> 
>> The updated XML file is here:
>> https://www.rfc-editor.org/authors/rfc9712.xml
>> 
>> The updated output files are here:
>> https://www.rfc-editor.org/authors/rfc9712.txt
>> https://www.rfc-editor.org/authors/rfc9712.pdf
>> https://www.rfc-editor.org/authors/rfc9712.html
>> 
>> This diff file shows all changes made during AUTH48:
>> https://www.rfc-editor.org/authors/rfc9712-auth48diff.html
>> 
>> This diff file shows all changes made to date:
>> https://www.rfc-editor.org/authors/rfc9712-diff.html
>> 
>> For the AUTH48 status of this document, please see:
>> https://www.rfc-editor.org/auth48/rfc9712
>> 
>> Best regards,
>> RFC Editor/kc
>> 
>>> On Jan 22, 2025, at 2:07 PM, Sean Turner <s...@sn3rd.com> wrote:
>>> 
>>> Just one question:
>>> 
>>> Could this:
>>> 
>>> The choice of a main hotel and negotiation of the network for that hotel 
>>> are more complicated
>>> 
>>> be this:
>>> 
>>> The choice of a main hotel and negotiation for the network at that hotel 
>>> are more complicated
>>> 
>>> spt
>>> 
>>>> On Jan 21, 2025, at 2:55 PM, Karen Moore <kmo...@staff.rfc-editor.org> 
>>>> wrote:
>>>> 
>>>> Hi Jay,
>>>> 
>>>> We have updated both addresses to reflect “Wilmington” and have noted your 
>>>> approval on the AUTH48 status page 
>>>> (https://www.rfc-editor.org/auth48/rfc9712).
>>>> 
>>>> We now await approval from Sean prior to moving forward with publication. 
>>>> 
>>>> The updated XML file is here:
>>>> https://www.rfc-editor.org/authors/rfc9712.xml
>>>> 
>>>> The updated output files are here:
>>>> https://www.rfc-editor.org/authors/rfc9712.txt
>>>> https://www.rfc-editor.org/authors/rfc9712.pdf
>>>> https://www.rfc-editor.org/authors/rfc9712.html
>>>> 
>>>> This diff file shows all changes made during AUTH48:
>>>> https://www.rfc-editor.org/authors/rfc9712-auth48diff.html
>>>> 
>>>> This diff file shows all changes made to date:
>>>> https://www.rfc-editor.org/authors/rfc9712-diff.html
>>>> 
>>>> For the AUTH48 status of this document, please see:
>>>> https://www.rfc-editor.org/auth48/rfc9712
>>>> 
>>>> Best regards,
>>>> RFC Editor/kc
>>>> 
>>>>> On Jan 21, 2025, at 11:18 AM, Jay Daley <j...@staff.ietf.org> wrote:
>>>>> 
>>>>> Hi Karen
>>>>> 
>>>>> I have reviewed everything and I am happy for this to move to publication.
>>>>> 
>>>>> Jay
>>>>> 
>>>>>> On 22 Jan 2025, at 07:47, Karen Moore <kmo...@staff.rfc-editor.org> 
>>>>>> wrote:
>>>>>> 
>>>>>> Dear Jay and Sean,
>>>>>> 
>>>>>> We do not believe we have heard from you regarding this document's 
>>>>>> readiness for publication.  Please review the files below and let us 
>>>>>> know if any further updates are needed or if the document is ready for 
>>>>>> publication. 
>>>>>> 
>>>>>> The updated XML file is here:
>>>>>> https://www.rfc-editor.org/authors/rfc9712.xml
>>>>>> 
>>>>>> The updated output files are here:
>>>>>> https://www.rfc-editor.org/authors/rfc9712.txt
>>>>>> https://www.rfc-editor.org/authors/rfc9712.pdf
>>>>>> https://www.rfc-editor.org/authors/rfc9712.html
>>>>>> 
>>>>>> This diff file shows all changes made during AUTH48:
>>>>>> https://www.rfc-editor.org/authors/rfc9712-auth48diff.html
>>>>>> 
>>>>>> This diff file shows all changes made to date:
>>>>>> https://www.rfc-editor.org/authors/rfc9712-diff.html
>>>>>> 
>>>>>> For the AUTH48 status of this document, please see:
>>>>>> https://www.rfc-editor.org/auth48/rfc9712
>>>>>> 
>>>>>> Best regards,
>>>>>> RFC Editor/kc
>>>>>> 
>>>>>> 
>>>>>>> On Jan 13, 2025, at 1:51 PM, Karen Moore <kmo...@staff.rfc-editor.org> 
>>>>>>> wrote:
>>>>>>> 
>>>>>>> Jay,
>>>>>>> 
>>>>>>> Our files now reflect 'bringing in additional hallway seating’ (Section 
>>>>>>> 4.4.2). Please review and let us know if any further changes are needed 
>>>>>>> or if you approve the document in its current form.
>>>>>>> 
>>>>>>> —FILES (please refresh)— 
>>>>>>> 
>>>>>>> The updated XML file is here:
>>>>>>> https://www.rfc-editor.org/authors/rfc9712.xml
>>>>>>> 
>>>>>>> The updated output files are here:
>>>>>>> https://www.rfc-editor.org/authors/rfc9712.txt
>>>>>>> https://www.rfc-editor.org/authors/rfc9712.pdf
>>>>>>> https://www.rfc-editor.org/authors/rfc9712.html
>>>>>>> 
>>>>>>> This diff file shows all changes made during AUTH48:
>>>>>>> https://www.rfc-editor.org/authors/rfc9712-auth48diff.html
>>>>>>> 
>>>>>>> This diff file shows all changes made to date:
>>>>>>> https://www.rfc-editor.org/authors/rfc9712-diff.html
>>>>>>> 
>>>>>>> Please 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.
>>>>>>> 
>>>>>>> For the AUTH48 status of this document, please see:
>>>>>>> https://www.rfc-editor.org/auth48/rfc9712
>>>>>>> 
>>>>>>> Thank you,
>>>>>>> RFC Editor/kc
>>>>>>> 
>>>>>>> 
>>>>>>>> On Jan 13, 2025, at 1:40 PM, Jay Daley <j...@staff.ietf.org> wrote:
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>>> On 14 Jan 2025, at 10:32, Karen Moore <kmo...@staff.rfc-editor.org> 
>>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>> Hi Jay,
>>>>>>>>> 
>>>>>>>>> We have updated our files based on your feedback (note that "BCP 226" 
>>>>>>>>> will be added during the publication process).
>>>>>>>> 
>>>>>>>> 
>>>>>>>> Thanks
>>>>>>>> 
>>>>>>>>> We have an additional question.
>>>>>>>>> 
>>>>>>>>> 1) Regarding the following text, would option A or B perhaps be 
>>>>>>>>> better than using ‘hiring’ or ‘renting’? 
>>>>>>>>> 
>>>>>>>>> Original:
>>>>>>>>> The IASA has responded to this feedback by adopting
>>>>>>>>> a new practice of hiring in hallway seating whenever 
>>>>>>>>> that provided by the venue is insufficient.
>>>>>>>>> 
>>>>>>>>> Perhaps:
>>>>>>>>> A) The IASA has responded to this feedback by adopting
>>>>>>>>> a new practice of supplying in hallway seating whenever 
>>>>>>>>> that provided by the venue is insufficient.
>>>>>>>>> or 
>>>>>>>>> 
>>>>>>>>> B) The IASA has responded to this feedback by adopting
>>>>>>>>> a new practice of making in hallway seating available 
>>>>>>>>> whenever that provided by the venue is insufficient.
>>>>>>>> 
>>>>>>>> To avoid hiring or renting, my preference is:
>>>>>>>> 
>>>>>>>> The IASA has responded to this feedback by adopting 
>>>>>>>> a new practice of bringing in additional hallway seating
>>>>>>>> whenever that provided by the venue is insufficient.
>>>>>>>> 
>>>>>>>> Let me know if that works for you.
>>>>>>>> 
>>>>>>>> Jay
>>>>>>>> 
>>>>>>>> 
>>>>>>>> -- 
>>>>>>>> Jay Daley
>>>>>>>> IETF Executive Director
>>>>>>>> exec-direc...@ietf.org
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>>> -- 
>>>>> Jay Daley
>>>>> IETF Executive Director
>>>>> exec-direc...@ietf.org
>>>>> 
>>>> 
>>> 
>> 
> 

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

Reply via email to