Re: [nfsv4] Draft is updated following your comments, Thanks//答复: draft-mzhang-nfsv4-sequence-id-calibration-01
Thomas Haynes <loghyr@gmail.com> Mon, 10 April 2023 16:12 UTC
Return-Path: <loghyr@gmail.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 856EEC14CE5D for <nfsv4@ietfa.amsl.com>; Mon, 10 Apr 2023 09:12:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.094
X-Spam-Level:
X-Spam-Status: No, score=-7.094 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 3SvYJZXJVXM7 for <nfsv4@ietfa.amsl.com>; Mon, 10 Apr 2023 09:12:15 -0700 (PDT)
Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BACB7C14CE3F for <nfsv4@ietf.org>; Mon, 10 Apr 2023 09:12:15 -0700 (PDT)
Received: by mail-pj1-x102f.google.com with SMTP id e18-20020a17090ac21200b00246952d917fso3445895pjt.4 for <nfsv4@ietf.org>; Mon, 10 Apr 2023 09:12:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1681143135; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=+zEBNZr/mpg6BFUZPuwJf3pMnisLsS4glLUcjJVqkZY=; b=cKARf3dyBfJWtWeKBHvRKAUKRqOcG2OZKI/C81BTji2TWCGt/0+rWZOZJoT3hLcWIq BcksxTYOJ6T2IS4LkGDupXoNI12l0wcS+pEm3Y7gcwF3AFeIwJTljZoxM35Me+zA8oMi dYLOYo8iXj00dqDc+V6lGWYZdUQNfO8CamgmPqNYOpKMcilpFwY/G5KOZbwRsGi0Rtzl qxW1ta2vvYyCwm8Tf3CH45z0sIh2hdvKlvD3quh7qK7xm5cQGLAJezBolAY5nbiQkFk7 rDtOwlZDRnxExDW/iIFSGQbPiO+NgX/+0ViQFH4ZZ4GuhMUn23Gwi714AMrgxbnuTajp p4Rw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681143135; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=+zEBNZr/mpg6BFUZPuwJf3pMnisLsS4glLUcjJVqkZY=; b=unfD/fAHAqVkFEvBFxcA5WqzkMf2rZWz1u0Bsgd0phTvWBHaIZ+VxfPGOSLUYq8aRf MHgeYGy8cW7wXpVT33R1d5PMyS+Rl+h5dBpo//POctrUEyp6YHaZrXLMDnksfyda1rDV 46guwqvE1kfk0gTExX8jBAwDA/eHEQPqLmDIxqyimEWhyA8fjvVXJAKS1cBC8HHcBa1g /oIe3kuXJruf9rlmcGr+Ew8Jt9LRQ02OGjwywLybcwVUv+Y8s2VoA9Ff/jhNR2+fAFNB IrxJM7NRy84M9kUhH6YfWpYdUGRjyuInr7Rqx7xPTRGYuE4RdG8wd+j6bBl94p1f8hKX yyGA==
X-Gm-Message-State: AAQBX9f1l6ei0MfstvFyVtx7Em5hP2BPwce88B7tDdUZ8TEi0A4RvQjO 5wcBiEzpLlzFIzlMRxXnSL2FzW55p6Y=
X-Google-Smtp-Source: AKy350b4/xaX+0FbueZKmohls4U63KIvBHvIekox61FsBBiuxS5ocJmZ0qlmG21cUrI2F9LQM8IvVw==
X-Received: by 2002:a05:6a20:3aa2:b0:d4:c1ba:9f4e with SMTP id d34-20020a056a203aa200b000d4c1ba9f4emr11519557pzh.35.1681143134667; Mon, 10 Apr 2023 09:12:14 -0700 (PDT)
Received: from smtpclient.apple (c-69-181-124-201.hsd1.ca.comcast.net. [69.181.124.201]) by smtp.gmail.com with ESMTPSA id e21-20020aa78255000000b005895f9657ebsm8079272pfn.70.2023.04.10.09.12.13 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Apr 2023 09:12:14 -0700 (PDT)
From: Thomas Haynes <loghyr@gmail.com>
Message-Id: <7DC61022-3681-4231-A0AA-26AF5669688A@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_20AE360E-109F-4661-99CF-DE46B1D55DDF"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\))
Date: Mon, 10 Apr 2023 09:12:01 -0700
In-Reply-To: <83389b42bb0f49509c757cdabd5c6b3f@huawei.com>
Cc: nfsv4@ietf.org
To: "yangjing (U)" <yangjing8@huawei.com>
References: <83389b42bb0f49509c757cdabd5c6b3f@huawei.com>
X-Mailer: Apple Mail (2.3731.400.51.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/yjMP_7_pqOpQrL1ID3P3vLpK8Ic>
Subject: Re: [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: Mon, 10 Apr 2023 16:12:19 -0000
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: <bcp14>MUST</bcp14> 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><CODE BEGINS></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><CODE ENDS></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> 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.
- [nfsv4] Draft is updated following your comments,… yangjing (U)
- Re: [nfsv4] Draft is updated following your comme… Thomas Haynes
- Re: [nfsv4] Draft is updated following your comme… Rick Macklem
- Re: [nfsv4] Draft is updated following your comme… Rick Macklem
- Re: [nfsv4] Draft is updated following your comme… Rick Macklem
- Re: [nfsv4] Draft is updated following your comme… Rick Macklem
- [nfsv4] 答复: Draft is updated following your comme… yangjing (U)
- [nfsv4] 答复: Draft is updated following your comme… yangjing (U)
- Re: [nfsv4] Draft is updated following your comme… Rick Macklem
- Re: [nfsv4] Draft is updated following your comme… David Noveck
- [nfsv4] 答复: Draft is updated following your comme… yangjing (U)
- Re: [nfsv4] Draft is updated following your comme… Rick Macklem