Dear RFC Editor,
Thank you for your efforts.
Please see inline my responses with [XM]>>>.
Original
From: rfc-edi...@rfc-editor.org
To: chengweiqi...@chinamobile.com
;wangrui...@chinamobile.com
;肖敏10093570;res...@yahoo.com
;rche...@juniper.net ;
Cc: rfc-edi...@rfc-editor.org ;bfd-...@ietf.or
Daniel,
While reviewing this document during AUTH48, please resolve (as necessary) the
following questions, which are also in the XML file.
1)
2)
3)
4)
5)
6)
7)
8)
9)
10)
11)
12)
13)
Thank you.
RFC Editor/rv
On Mar 5, 2025, at 5:17 PM, rfc-edi...@rfc-edi
I approve the publication of this document
-Original Message-
From: Alanna Paloma [mailto:apal...@staff.rfc-editor.org]
Sent: Wednesday, March 5, 2025 8:26 AM
To: John Scudder ; Aijun Wang
; bhassa...@yahoo.com; Fangsheng
; Tanren ; zhu.ch...@zte.com.cn
Cc: RFC Editor ; pce-ads ;
p
*IMPORTANT*
Updated 2025/03/05
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 sever
Hi Tony,
Thank you for your review and reply. The files have been updated accordingly,
and we have noted your approval.
FYI - To reflect your suggested update to similar text, we have also updated
the text below. Please let us know of any objections.
Previous:
then CLEANUP, PUSH UpdateZTPOffe
Hi Ali, Gunter, and Matthew,
Thank you for your replies.
Ali - Thank you for the new proposed text.
Gunter - Thank you for your approval of Ali's proposed text.
Matthew - Are there any objections to Ali's proposed text and document updates?
We ask because Ali wrote:
> Hi Sarah, if no objecti
Thanks Gunter!
Sarah, can you please update the draft based on the proposed text.
Thanks very much,
Ali
From: Gunter van de Velde (Nokia)
Date: Wednesday, March 5, 2025 at 12:09 AM
To: Ali Sajassi (sajassi) , Matthew Bocci (Nokia)
, Sarah Tarrant , Ali
Sajassi (sajassi)
Cc: rfc-edi...@rfc-ed
Hi Gorry,
Thanks for sending this along. We have added this change to our versions of
the files
(see below).
Please review our update (as your description of the update was to change one
word but
the “New” text actually changed more than one word) and let us know if any
further updates
are
Hi Authors,
Thank you to Dhruv for confirming the AUTH48 changes.
We have now received all necessary approvals and consider AUTH48 complete:
https://www.rfc-editor.org/auth48/rfc9756
Thank you for your attention and guidance during the AUTH48 process.
We will move this document forward in the p
Hi Aijun and John,
Thank you for your replies. The files have been updated accordingly.
> On Mar 4, 2025, at 6:37 PM, Aijun Wang wrote:
>
> One minor question, should the table 4 in
> https://www.rfc-editor.org/authors/rfc9757.html#section-13.4add another
> column, to point also to RFC 9757?
Thanks, Joe, for working through all the comments.
There is one item that was missed, and a couple of updates. See inline.
> On Mar 5, 2025, at 5:45 AM, Joe Clarke (jclarke) wrote:
>
> Thank you for the attention, RFC Ed! Let me go through your comments below.
>
> 1)
>
> [JMC] I do not thi
I was performing a final check and noted one mistake by me that needs to
be corrected (so sorry).
ORIGINAL (as sent to RFC-Ed):
A congestion control algorithm shouldtry to avoid causing
excessively high rates of packet loss.
CURRENT (as suggested by me):
A congestion control algorithm ought
Thank you for the attention, RFC Ed! Let me go through your comments below.
1)
[JMC] I do not think we need any additional keywords. What we have in terms of
“syslog” and “yang data model” seem descriptive enough to find this.
2)
[JMC] Good with this.
3)
[JMC] I did not see anything
*IMPORTANT*
Updated 2025/03/04
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 sever
Hi Alanna,
I have verified the AUTH48 changes and it is ready to be published!
Thanks!
Dhruv
On Wed, Mar 5, 2025 at 4:04 AM Alanna Paloma
wrote:
> Hi Adrian and Dhruv,
>
> Thank you for your replies. We have updated the files accordingly. We
> note that you have both sent your approvals; howe
On 20.02.2025 22:18, ENRICO FRANCESCONI wrote:
Dear Madison and Eliot,
we were preparing an answer to the previous message, when we
received two new emails of yours.
We report in the following our reply which partially addresses the
issue on Hebrew characters you underline in your message.
Sounds good. See you there!
On Wed, Mar 5, 2025, at 7:33 AM, Eric Vyncke (evyncke) wrote:
> Ted,
>
> The next steps sound logical to me. Let’s check at IETF-122 for the WG
> consensus about the last changes, but until now: no reactions on the DNSSD
> mailing list.
>
> Regards
>
> -éric
>
Ali,
Thanks. This sounds good to me, and approved. It describes the failure impacts
more accurately.
G/
From: Ali Sajassi (sajassi)
Sent: Wednesday, March 5, 2025 4:44 AM
To: Matthew Bocci (Nokia) ; Gunter van de Velde
(Nokia) ; Sarah Tarrant
; Ali Sajassi (sajassi)
Cc: rfc-edi...@rfc-edit
18 matches
Mail list logo
