Hi Roland,
Thank you for addressing my comments.
The resolutions look good to me.
Cheers,
Xiao Min
Original
From: R.Jesske@xxxxxxxxxx <R.Jesske@xxxxxxxxxx>
To: 肖敏10093570;ops-dir@xxxxxxxx <ops-dir@xxxxxxxx>;
Cc: draft-ietf-sipcore-rfc7976bis.all@xxxxxxxx <draft-ietf-sipcore-rfc7976bis.all@xxxxxxxx>;last-call@xxxxxxxx <last-call@xxxxxxxx>;sipcore@xxxxxxxx <sipcore@xxxxxxxx>;
Date: 2025年06月23日 15:41
Subject: AW: draft-ietf-sipcore-rfc7976bis-02 ietf last call Opsdir review
Hi,
I have incoperated the comments as follows. See below.
Best Regards
Roland
-----Ursprüngliche Nachricht-----
Von: Xiao Min via Datatracker <noreply@xxxxxxxx>
Gesendet: Dienstag, 27. Mai 2025 11:06
An: ops-dir@xxxxxxxx
Cc: draft-ietf-sipcore-rfc7976bis.all@xxxxxxxx; last-call@xxxxxxxx; sipcore@xxxxxxxx
Betreff: draft-ietf-sipcore-rfc7976bis-02 ietf last call Opsdir review
Document: draft-ietf-sipcore-rfc7976bis
Title: Updates to Private Header (P-Header) Extension Usage in Session Initiation Protocol (SIP) Requests and Responses Reviewer: Xiao Min Review
result: Has Nits
Summary: I have been asked to review this draft on behalf of the OPS directorate. I think this document is READY with Nits.
I have a few comments for the authors to consider.
Abstract, it says "...when RFC 3455 was updated and obsoleted by RFC 7315". To my understanding, an RFC couldn't be *updated* and *obsoleted* by another RFC at the same time, so suggest s/updated and obsoleted by RFC 7315/obsoleted by RFC 7315. These words appear in three places of this draft. I noticed that these words were already there within RFC 7976, however I believe it can be improved in the Bis draft.
[RJ] I have changd the absteract to: " This document also makes updates for RFC 7315 in order to fix misalignments that occurred when RFC 3455 was updated and subsequently obsoleted by the publication of RFC 7315."
I changed the sentence
Section 2.2, the last sentence, suggest s/Add statement that P-Visited-Network-ID/Add a statement that the P-Visited-Network-ID, s/non 100/non-100.
[RJ] Done
Section 3, to make alignment, suggest s/non-100 response message except
ACK/non-100 responses, except in ACK. Also s/ACK methods triggered by/ACK requests triggered by and s/in all SIP methods/in all SIP requests.
[RJ] Done
I have incoperated the comments as follows. See below.
Best Regards
Roland
-----Ursprüngliche Nachricht-----
Von: Xiao Min via Datatracker <noreply@xxxxxxxx>
Gesendet: Dienstag, 27. Mai 2025 11:06
An: ops-dir@xxxxxxxx
Cc: draft-ietf-sipcore-rfc7976bis.all@xxxxxxxx; last-call@xxxxxxxx; sipcore@xxxxxxxx
Betreff: draft-ietf-sipcore-rfc7976bis-02 ietf last call Opsdir review
Document: draft-ietf-sipcore-rfc7976bis
Title: Updates to Private Header (P-Header) Extension Usage in Session Initiation Protocol (SIP) Requests and Responses Reviewer: Xiao Min Review
result: Has Nits
Summary: I have been asked to review this draft on behalf of the OPS directorate. I think this document is READY with Nits.
I have a few comments for the authors to consider.
Abstract, it says "...when RFC 3455 was updated and obsoleted by RFC 7315". To my understanding, an RFC couldn't be *updated* and *obsoleted* by another RFC at the same time, so suggest s/updated and obsoleted by RFC 7315/obsoleted by RFC 7315. These words appear in three places of this draft. I noticed that these words were already there within RFC 7976, however I believe it can be improved in the Bis draft.
[RJ] I have changd the absteract to: " This document also makes updates for RFC 7315 in order to fix misalignments that occurred when RFC 3455 was updated and subsequently obsoleted by the publication of RFC 7315."
I changed the sentence
Section 2.2, the last sentence, suggest s/Add statement that P-Visited-Network-ID/Add a statement that the P-Visited-Network-ID, s/non 100/non-100.
[RJ] Done
Section 3, to make alignment, suggest s/non-100 response message except
ACK/non-100 responses, except in ACK. Also s/ACK methods triggered by/ACK requests triggered by and s/in all SIP methods/in all SIP requests.
[RJ] Done
-- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
