[nfsv4] 答复: Draft is updated following your comments, Thanks//答复: draft-mzhang-nfsv4-sequence-id-calibration-01

"yangjing (U)" <yangjing8@huawei.com> Fri, 21 April 2023 09:58 UTC

Return-Path: <yangjing8@huawei.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 328C9C136133 for <nfsv4@ietfa.amsl.com>; Fri, 21 Apr 2023 02:58:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QFYlGwpNdpr9 for <nfsv4@ietfa.amsl.com>; Fri, 21 Apr 2023 02:58:11 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90541C15155E for <nfsv4@ietf.org>; Fri, 21 Apr 2023 02:58:10 -0700 (PDT)
Received: from lhrpeml100004.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Q2qbN16H9z67Rl1 for <nfsv4@ietf.org>; Fri, 21 Apr 2023 17:53:20 +0800 (CST)
Received: from kwepemi100011.china.huawei.com (7.221.188.134) by lhrpeml100004.china.huawei.com (7.191.162.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.23; Fri, 21 Apr 2023 10:58:06 +0100
Received: from kwepemi500014.china.huawei.com (7.221.188.232) by kwepemi100011.china.huawei.com (7.221.188.134) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.23; Fri, 21 Apr 2023 17:58:04 +0800
Received: from kwepemi500014.china.huawei.com ([7.221.188.232]) by kwepemi500014.china.huawei.com ([7.221.188.232]) with mapi id 15.01.2507.023; Fri, 21 Apr 2023 17:58:04 +0800
From: "yangjing (U)" <yangjing8@huawei.com>
To: Thomas Haynes <loghyr@gmail.com>
CC: "nfsv4@ietf.org" <nfsv4@ietf.org>
Thread-Topic: Draft is updated following your comments, Thanks//答复: draft-mzhang-nfsv4-sequence-id-calibration-01
Thread-Index: Adlrdv8o4J6qb1jcQoy+CNAfWT26KAADSFiAAiyr/FA=
Date: Fri, 21 Apr 2023 09:58:04 +0000
Message-ID: <4a35a92e4afe49589e27291666062b6d@huawei.com>
References: <83389b42bb0f49509c757cdabd5c6b3f@huawei.com> <7DC61022-3681-4231-A0AA-26AF5669688A@gmail.com>
In-Reply-To: <7DC61022-3681-4231-A0AA-26AF5669688A@gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.110.46.233]
Content-Type: multipart/alternative; boundary="_000_4a35a92e4afe49589e27291666062b6dhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/6Q-uCwMsW_jHgA8_L6Hh6g2__-0>
Subject: [nfsv4] 答复: Draft is updated following your comments, Thanks//答复: draft-mzhang-nfsv4-sequence-id-calibration-01
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4/>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2023 09:58:12 -0000

Hi Thomas,

          I have fixed the biggest issue, that is the conversion tool. I think I fix all the problems you mentioned this time.
https://datatracker.ietf.org/doc/draft-mzhang-nfsv4-sequence-id-calibration/
Thank you very much. ^_^

Best Regards
Jing

发件人: Thomas Haynes [mailto:loghyr@gmail.com]
发送时间: 2023年4月11日 12:12 AM
收件人: yangjing (U) <yangjing8@huawei.com>
抄送: nfsv4@ietf.org
主题: Re: Draft is updated following your comments, Thanks//答复: draft-mzhang-nfsv4-sequence-id-calibration-01

Hi Jing,

The biggest mechanical issue appears to be the way you are making edits. I.e., I suspect you use some tool to convert to XML for draft submission.

You might want to consider just editing the raw XML from this point on.


1) In here:

    <note title="Requirements Language">
      <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
      "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
      document are to be interpreted as described in <xref
      target="RFC2119">RFC 2119</xref>.</t>
    </note>

You need to have the tags of "<bcp14>MUST</bcp14>”, for each one.

2) And in the text, you have:

&lt;bcp14&gt;MUST&lt;/bcp14&gt;

It must be <bcp14>MUST</bcp14>.

I.e., this has to be in the XML output and not whatever you are running to submit the draft.


3) In here:

      <section title="Operation 16:CB_SEQUENCE_QUERY- Query backchannel sequence ID of designated session and slot for calibration">
        <section title="ARGUMENT">
          <t>&lt;CODE BEGINS&gt;</t>

          <t>/// /*</t>

          <t>/// * callback program structure for sequenceid query</t>

          <t>/// */</t>

          <t>/// struct CB_SEQUENCE_QUERY4args {</t>

          <t>/// sessionid4 csqa_sessionid;</t>

          <t>/// slotid4 csqa_slotid;</t>

          <t>/// };</t>

          <t>&lt;CODE ENDS&gt;</t>
        </section>

It should be:

      <section title="Operation 16:CB_SEQUENCE_QUERY- Query backchannel sequence ID of designated session and slot for calibration">
       <sourcecode name="" type="" markers="true"><![CDATA[
   /// /*
   /// * callback program structure for sequenceid query
   /// */
   /// struct CB_SEQUENCE_QUERY4args {
   /// sessionid4 csqa_sessionid;
   /// slotid4 csqa_slotid;
   /// };
      </sourcecode>

Again, this is the raw XML and not whatever markup language/tool you are using.

4) While you have updated the operation numbers, please mention that this draft updates RFC7862 and not RFC8881.

You should consider adding text like this in the Introduction:

  <t>
    Using the process detailed in <xref target="RFC8178" format="default"
    sectionFormat="of"/>, the revisions in this document become an
    extension of NFSv4.2 <xref target="RFC7862" format="default"
    sectionFormat="of"/>. They are built on top of the external data
    representation (XDR) <xref target="RFC4506" format="default"
    sectionFormat="of"/> generated from <xref target="RFC7863"
    format="default" sectionFormat="of"/>.
  </t>


5) You should consider a section like Section 6 in https://datatracker.ietf.org/doc/draft-ietf-nfsv4-delstid/

6) When you reference a RFC, you have it straight like this: RFC8881

You need to cite it like this: <xref target="RFC8881" format="default" sectionFormat="of"/>

Tom





On Apr 9, 2023, at 11:38 PM, yangjing (U) <yangjing8@huawei.com<mailto:yangjing8@huawei.com>> wrote:

Hi Thomas,

Thanks for you detailed instructions.
The draft is updated as https://www.ietf.org/archive/id/draft-mzhang-nfsv4-sequence-id-calibration-02.txt

Regards
Jing

发件人: Thomas Haynes [mailto:loghyr@gmail.com]
发送时间: 2023年4月7日 2:21 AM
收件人: yangjing (U) <yangjing8@huawei.com<mailto:yangjing8@huawei.com>>
抄送: nfsv4@ietf.org<mailto:nfsv4@ietf.org>
主题: Re: draft-mzhang-nfsv4-sequence-id-calibration-01



Some nits on draft-mzhang-nfsv4-sequence-id-calibration-01:

1) Please mark the Operation numbers as needing assignment before publication.

BTW: You can look at https://github.com/loghyr/nfsv42_xdr for an unofficial copy of the current XDR.


2) In the ARGUMENTS sections, when you have things like:


struct SEQUENCE_QUERY4args {



   sessionid4 sqa_sessionid;



   slotid4 sqa_slotid;



   };

Please fix these up like this example from my delstid:

    <sourcecode name="" type="" markers="true"><![CDATA[
///
/// /*
///  * attributes for the delegation times being
///  * cached and served by the "client"
///  */
/// typedef nfstime4        fattr4_time_deleg_access;
/// typedef nfstime4        fattr4_time_deleg_modify;
///
 ]]>
    </sourcecode>

Please follow the convention of allowing the XDR to be stripped out by parsing the ‘///‘


3) For the Requirements Language, please use the bcp14 tag

“MUST” -> "<bcp14>MUST</bcp14>”

Note: You need to use this tag every place you use the keywords.