[sipcore] Re: draft-ietf-sipcore-rfc7976bis-02 ietf last call Opsdir review
xiao.min2@zte.com.cn Tue, 24 June 2025 08:41 UTC
Return-Path: <xiao.min2@zte.com.cn>
X-Original-To: sipcore@mail2.ietf.org
Delivered-To: sipcore@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id DA62B38A2529; Tue, 24 Jun 2025 01:41:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dd0z51N57yae; Tue, 24 Jun 2025 01:41:18 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [160.30.148.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 7900738A24F4; Tue, 24 Jun 2025 01:41:15 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.251.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4bRJMB1k8pz8R03y; Tue, 24 Jun 2025 16:41:10 +0800 (CST)
Received: from mse-fl2.zte.com.cn (unknown [10.5.228.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxct.zte.com.cn (FangMail) with ESMTPS id 4bRJLc3Pm2z51SvR; Tue, 24 Jun 2025 16:40:40 +0800 (CST)
Received: from njb2app07.zte.com.cn ([10.55.22.95]) by mse-fl2.zte.com.cn with SMTP id 55O8eHqu061846; Tue, 24 Jun 2025 16:40:17 +0800 (+08) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njy2app02[null]) by mapi (Zmail) with MAPI id mid201; Tue, 24 Jun 2025 16:40:19 +0800 (CST)
Date: Tue, 24 Jun 2025 16:40:19 +0800
X-Zmail-TransId: 2afa685a6473721-d77ee
X-Mailer: Zmail v1.0
Message-ID: <20250624164019696DhzP9rCL-R9DWxC58wmeS@zte.com.cn>
In-Reply-To: <BE1PPF3945B76FE932FE8753938BE478C86F979A@BE1PPF3945B76FE.DEUP281.PROD.OUTLOOK.COM>
References: 174833676034.1711298.14824532868302720329@dt-datatracker-59b84fc74f-84jsl,BE1PPF3945B76FE932FE8753938BE478C86F979A@BE1PPF3945B76FE.DEUP281.PROD.OUTLOOK.COM
Mime-Version: 1.0
From: xiao.min2@zte.com.cn
To: R.Jesske@telekom.de
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 55O8eHqu061846
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 685A64A6.000/4bRJMB1k8pz8R03y
Message-ID-Hash: ZVCA2UWJ4PEGQLGOXIF6MQYZMLKMIJ63
X-Message-ID-Hash: ZVCA2UWJ4PEGQLGOXIF6MQYZMLKMIJ63
X-MailFrom: xiao.min2@zte.com.cn
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-sipcore.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: ops-dir@ietf.org, draft-ietf-sipcore-rfc7976bis.all@ietf.org, last-call@ietf.org, sipcore@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [sipcore] Re: draft-ietf-sipcore-rfc7976bis-02 ietf last call Opsdir review
List-Id: SIP Core Working Group <sipcore.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/4xwL_QOduYNRPzzZFz4NdoynWWo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Owner: <mailto:sipcore-owner@ietf.org>
List-Post: <mailto:sipcore@ietf.org>
List-Subscribe: <mailto:sipcore-join@ietf.org>
List-Unsubscribe: <mailto:sipcore-leave@ietf.org>
Hi Roland, Thank you for addressing my comments. The resolutions look good to me. Cheers, Xiao Min Original From: R.Jesske@telekom.de <R.Jesske@telekom.de> To: 肖敏10093570;ops-dir@ietf.org <ops-dir@ietf.org>; Cc: draft-ietf-sipcore-rfc7976bis.all@ietf.org <draft-ietf-sipcore-rfc7976bis.all@ietf.org>;last-call@ietf.org <last-call@ietf.org>;sipcore@ietf.org <sipcore@ietf.org>; 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@ietf.org> Gesendet: Dienstag, 27. Mai 2025 11:06 An: ops-dir@ietf.org Cc: draft-ietf-sipcore-rfc7976bis.all@ietf.org; last-call@ietf.org; sipcore@ietf.org 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
- [sipcore] draft-ietf-sipcore-rfc7976bis-02 ietf l… Xiao Min via Datatracker
- [sipcore] Re: draft-ietf-sipcore-rfc7976bis-02 ie… R.Jesske
- [sipcore] Re: draft-ietf-sipcore-rfc7976bis-02 ie… xiao.min2