IETF Logo Mail Archive

RE: Adoption Call for "IPv6 Application of the Alternate Marking Method"

"licong@chinatelecom.cn" <licong@chinatelecom.cn> Thu, 28 May 2020 08:12 UTC

Return-Path: <licong@chinatelecom.cn>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBACB3A0BFF for <ipv6@ietfa.amsl.com>; Thu, 28 May 2020 01:12:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham 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 4suq1yZx8BSn for <ipv6@ietfa.amsl.com>; Thu, 28 May 2020 01:12:07 -0700 (PDT)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.223]) by ietfa.amsl.com (Postfix) with ESMTP id 138B93A0BFD for <ipv6@ietf.org>; Thu, 28 May 2020 01:12:06 -0700 (PDT)
HMM_SOURCE_IP: 172.18.0.48:7603.1182721133
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-219.142.69.77?logid-8cc56a0af7114ebeb5c7d57c6a0d881b (unknown [172.18.0.48]) by chinatelecom.cn (HERMES) with SMTP id 99E0228008E for <ipv6@ietf.org>; Thu, 28 May 2020 16:11:47 +0800 (CST)
X-189-SAVE-TO-SEND: 71080549@chinatelecom.cn
Received: from ([172.18.0.48]) by App0024 with ESMTP id 8cc56a0af7114ebeb5c7d57c6a0d881b for ipv6@ietf.org; Thu May 28 16:11:53 2020
X-Transaction-ID: 8cc56a0af7114ebeb5c7d57c6a0d881b
X-filter-score: filter<0>
X-Real-From: licong@chinatelecom.cn
X-Receive-IP: 172.18.0.48
X-MEDUSA-Status: 0
Sender: licong@chinatelecom.cn
Date: Thu, 28 May 2020 16:11:46 +0800
From: "licong@chinatelecom.cn" <licong@chinatelecom.cn>
To: ipv6 <ipv6@ietf.org>
Subject: RE: Adoption Call for "IPv6 Application of the Alternate Marking Method"
References: <4224A438-68F7-412B-8CC2-9E456F15A3CD@gmail.com>, <2020052816075509508329@chinatelecom.cn>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.16.188[cn]
Mime-Version: 1.0
Message-ID: <2020052816114668388630@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart382042417802_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/QV3DlpJMa6Sflctet3h8e8zJRGM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 May 2020 08:12:10 -0000

Hi, 6man

I do not support the adoption of this work.CRH defines a new data plane which is not compatible with SHR and SRv6. In addition, I think the use cases and security considerations are not clear enough.I think it's not the right timing to adopt CRH. Until now，there are other SRv6 and SRH compatible solutions, we should  compare the advantages and disadvantages of different solutions and choose the best one.

Best regards
Cong Li

-----Original Message-----
From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Bob Hinden
Sent: Saturday, May 16, 2020 6:10 AM
To: IPv6 List <ipv6@ietf.org>
Cc: Bob Hinden <bob.hinden@gmail.com>
Subject: Adoption Call for "IPv6 Application of the Alternate Marking Method"
 
This message starts a two week 6MAN call on adopting:
 
  Title:           IPv6 Application of the Alternate Marking Method
  Authors:         G. Fioccola, T. Zhou, M. Cociglio, F. Qin
  File Name        draft-fz-6man-ipv6-alt-mark-09
  Document date:   2020-05-04
 
  https://tools.ietf.org/html/draft-fz-6man-ipv6-alt-mark-09
 
as a working group item. Substantive comments regarding adopting this document should be directed to the mailing list. Editorial suggestions can be sent to the authors.  This adoption call will end on 29 May 2020.
 
There has been a lot of discussion on this draft, the chairs believe that the major issues raised on the list are resolved in this version of draft and it is ready for the working group to consider adopting as working group draft.
 
Could those who are willing to work on this document, either as contributors, authors or reviewers please notify the list.   That gives us an indication of the energy level in the working group
to work on this.
 
Regards,
Bob and Ole

v2.23.0 | Report a Bug | By Email