Re: [Softwires] Alexey Melnikov's No Objection on draft-ietf-softwire-mesh-multicast-23: (with COMMENT)

" 杨术 " <yangshu@oudmon.com> Sun, 02 June 2019 15:31 UTC

Return-Path: <yangshu@oudmon.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F26D12018C for <softwires@ietfa.amsl.com>; Sun, 2 Jun 2019 08:31:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.918
X-Spam-Level:
X-Spam-Status: No, score=-0.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.979, HTML_MESSAGE=0.001, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o4stnrnaq3Ox for <softwires@ietfa.amsl.com>; Sun, 2 Jun 2019 08:31:04 -0700 (PDT)
Received: from smtpbgeu2.qq.com (smtpbgeu2.qq.com [18.194.254.142]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D31C7120150 for <softwires@ietf.org>; Sun, 2 Jun 2019 08:31:00 -0700 (PDT)
X-QQ-GoodBg: 2
X-QQ-SSF: 00400000000000F0
X-QQ-FEAT: i/xzikqTSPaNma3nKCPyCmuoaElsrJjxHmR1YwsNJ613Xuu+8Er7U/Ehw2kWu bkz0XS2HLHtwiaZ+xnOAL/KhVFWbi51s7RMxbPBYoLdJVvxRiChmJAskF6tdfp63rr+Cglp m/KxdWftOeUWe2hSkzckpyu4oR0ziO2GfS0ix+SmxcwkkEUQvD8u1U9Lg3nQzs6yTMHCn+b /f5BYSi+aNW46nFk9ZDeRLJOw1nUQB+111gQjm+xUASwoVLkecSDWib6tEG8lYCYFPdekFv mwHxAwOm1YAox/FJ6SfSjs8fXQiYeMnvaG2kFoYQQuQFpuvWnIvSW8UStg2dWI+BHXuw==
X-QQ-BUSINESS-ORIGIN: 2
X-Originating-IP: 61.51.59.75
X-QQ-STYLE:
X-QQ-mid: bizmailvip4t1559489453t962125
From: "=?utf-8?B?5p2o5pyv?=" <yangshu@oudmon.com>
To: "=?utf-8?B?QWxleGV5IE1lbG5pa292?=" <aamelnikov@fastmail.fm>, "=?utf-8?B?VGhlIElFU0c=?=" <iesg@ietf.org>
Cc: "=?utf-8?B?c29mdHdpcmVz?=" <softwires@ietf.org>, "=?utf-8?B?ZHJhZnQtaWV0Zi1zb2Z0d2lyZS1tZXNoLW11bHRpY2FzdA==?=" <draft-ietf-softwire-mesh-multicast@ietf.org>, "=?utf-8?B?c29mdHdpcmUtY2hhaXJz?=" <softwire-chairs@ietf.org>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_5CF3EBAD_09309BA0_40524CFC"
Content-Transfer-Encoding: 8Bit
Date: Sun, 2 Jun 2019 23:30:53 +0800
X-Priority: 3
Message-ID: <tencent_23B8EA1B70DD9E0E5D8385E8@qq.com>
X-QQ-MIME: TCMime 1.0 by Tencent
X-Mailer: QQMail 2.x
X-QQ-Mailer: QQMail 2.x
X-QQ-SENDSIZE: 520
Received: from qq.com (unknown [127.0.0.1]) by smtp.qq.com (ESMTP) with SMTP id ; Sun, 02 Jun 2019 23:30:54 +0800 (CST)
Feedback-ID: bizmailvip:oudmon.com:qybgforeign:qybgforeign2
X-QQ-Bgrelay: 1
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/l8Axc88RVsGCekULoqIZKs0vSqo>
Subject: Re: [Softwires] Alexey Melnikov's No Objection on draft-ietf-softwire-mesh-multicast-23: (with COMMENT)
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Jun 2019 15:31:15 -0000

Dear Alexey, 


Thank you for your comments, 


 
> 1) "COULD" is not one of RFC 2119 keywords, so it shouldn't be uppercased in
 
> order to avoid causing confusion for readers.
 


 
We make all “COULD” lowercased.
 


 
> 2) In Section 10 the document says:
 


 
>>   Compared with [RFC4925], the security concerns SHOULD be considered
 
>>   more carefully: ...
 


 
> This is not a requirement statement on implementations or operators, so use of
 
> SHOULD is not appropriate here. So please lowercase it to avoid RFC 2119
 
> meaning.
 


 
We lowercase it.



Best Regards,


Shu Yang




------------------



杨术



欧德蒙科技有限公司






This message may contain privileged and confidential information only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that any use, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately. 



 
 
 
------------------ Original ------------------
From:  "Alexey Melnikov"<aamelnikov@fastmail.fm>mail.fm>;
Date:  Thu, Sep 27, 2018 00:32 AM
To:  "The IESG"<iesg@ietf.org>etf.org>; 
Cc:  "softwires"<softwires@ietf.org>res@ietf.org>; "draft-ietf-softwire-mesh-multicast"<draft-ietf-softwire-mesh-multicast@ietf.org>ast@ietf.org>; "softwire-chairs"<softwire-chairs@ietf.org>irs@ietf.org>; 
Subject:  [Softwires] Alexey Melnikov's No Objection on draft-ietf-softwire-mesh-multicast-23: (with COMMENT)

 

Alexey Melnikov has entered the following ballot position for
draft-ietf-softwire-mesh-multicast-23: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-softwire-mesh-multicast/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

A couple of nits:

1) "COULD" is not one of RFC 2119 keywords, so it shouldn't be uppercased in
order to avoid causing confusion for readers.

2) In Section 10 the document says:

   Compared with [RFC4925], the security concerns SHOULD be considered
   more carefully: ...

This is not a requirement statement on implementations or operators, so use of
SHOULD is not appropriate here. So please lowercase it to avoid RFC 2119
meaning.


_______________________________________________
Softwires mailing list
Softwires@ietf.org
https://www.ietf.org/mailman/listinfo/softwires