Re: [Softwires] Mirja Kühlewind'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 5607D1200C4 for <softwires@ietfa.amsl.com>; Sun, 2 Jun 2019 08:31:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.917
X-Spam-Level:
X-Spam-Status: No, score=-0.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.979, HTML_MESSAGE=0.001, HTML_NONELEMENT_30_40=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 gu10F70otmOo for <softwires@ietfa.amsl.com>; Sun, 2 Jun 2019 08:31:27 -0700 (PDT)
Received: from smtpbgau1.qq.com (smtpbgau1.qq.com [54.206.16.166]) (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 6BB3A1201C5 for <softwires@ietf.org>; Sun, 2 Jun 2019 08:31:10 -0700 (PDT)
X-QQ-GoodBg: 2
X-QQ-SSF: 00400000000000F0
X-QQ-FEAT: IJTqyPTPEkB33Wirri0Enetf0nOMvcPSGxIgo+3gs+DNaIS7bcNwU7i/KjSCc uXHENbudCNu47pCltU0rbbvJUWvh1ywsuIgSJ34mZzdRRS/j6eYgqkROVMlrgA1kcpqhZnp NCRazMsTaOsGNhgKNr3Md2f3wEh9r0rlFESpfRUrZWSPVjqTo7ko1sOUPB08TeC8XjsWl/E yvkVNEHi1g4ReBYlVlZDu9O4IlXRveIrZsG6w+7DZEk1redi1wR4VKdwP8is7JpcgSgzEKL OyiT1aqCDb5/ioCcaydYRYceyVsT+IqJ5vlz2+sC0NvEqA8+9R/aQ2xKI=
X-QQ-BUSINESS-ORIGIN: 2
X-Originating-IP: 61.51.59.75
X-QQ-STYLE:
X-QQ-mid: bizmailvip4t1559489464t795569
From: "=?utf-8?B?5p2o5pyv?=" <yangshu@oudmon.com>
To: "=?utf-8?B?TWlyamEgS8O8aGxld2luZA==?=" <ietf@kuehlewind.net>, "=?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_5CF3EBB8_0913DF80_3A872521"
Content-Transfer-Encoding: 8Bit
Date: Sun, 2 Jun 2019 23:31:04 +0800
X-Priority: 3
Message-ID: <tencent_24CDE0810731D56677B1D7C7@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:31:06 +0800 (CST)
Feedback-ID: bizmailvip:oudmon.com:qybgforeign:qybgforeign4
X-QQ-Bgrelay: 1
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/pmjzUeTzAZ0ExaCObjbmA-Tak5g>
Subject: Re: [Softwires] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_d?= =?utf-8?q?raft-ietf-softwire-mesh-multicast-23=3A_=28with_COMMENT=29?=
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:31 -0000

Dear Mirja, 


Thank you for your comments!


> On section 7.3: Thanks for discussing fragmentation and pointing to
> [I-D.ietf-intarea-tunnels]. As [I-D.ietf-intarea-tunnels] is still work in
> progress, I guess it could make sense to also add a reference to rfc4459
> directly. Also I don't think COULD is a well-know key word...


As Joe suggested:
> However, it cites RFC 5565, which cites RFC4459. That's where 
> the only trouble lies - 4459 is incorrect, as noted in 
> draft-ietf-intarea-tunnels. I might suggest they continue to cite RFC 
> 5565 but indicate that the requirements for tunneling are under current 
> revision and cite draft-ietf-intarea-tunnel (at least informationally) too.


So, we add both 5565 and draft-ietf-intarea-tunnel as citation. 


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:  "Mirja Kühlewind"<ietf@kuehlewind.net>ind.net>;
Date:  Thu, Sep 20, 2018 06:19 PM
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] Mirja Kühlewind's No Objection on draft-ietf-softwire-mesh-multicast-23: (with COMMENT)

 

Mirja Kühlewind 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:
----------------------------------------------------------------------

On section 7.3: Thanks for discussing fragmentation and pointing to
[I-D.ietf-intarea-tunnels]. As [I-D.ietf-intarea-tunnels] is still work in
progress, I guess it could make sense to also add a reference to rfc4459
directly. Also I don't think COULD is a well-know key word...


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