回复: 回复: Adoption Call for "The IPv6 Compact Routing Header (CRH)"

Peng Liu <liupengyjy@outlook.com> Tue, 26 May 2020 06:30 UTC

Return-Path: <liupengyjy@outlook.com>
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 7568D3A0B69 for <ipv6@ietfa.amsl.com>; Mon, 25 May 2020 23:30:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.412
X-Spam-Level:
X-Spam-Status: No, score=0.412 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_WEB=1.5, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outlook.com
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 j9paG-xYsZXM for <ipv6@ietfa.amsl.com>; Mon, 25 May 2020 23:30:40 -0700 (PDT)
Received: from APC01-PU1-obe.outbound.protection.outlook.com (mail-oln040092254085.outbound.protection.outlook.com [40.92.254.85]) (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 6A1F03A0B68 for <ipv6@ietf.org>; Mon, 25 May 2020 23:30:40 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=emV7YIWgWIS7FTC5TrcfAxYogMj94RsBR7za3m3lydRn4CGpnVdFO9j3s+13DoVz7+dRUgU6ywT7TtGjQaEWBYEAaQT7De4lO0W2IiYUyTE1zMEa1UTSlVh6Tjr7HrRgncKIhpcwcCuufXKPxxTk8w1tIFCb+8i+klzIeRVztMC/zGz1ARI6k/NNHxUG7ynx2ijz83BQs79mPkoMzv1v9We22Z+FWkIKKACtQwGFCr7Aaq34BDOxqwYyGGLHlciy4ZpCW8+ewAca2kDevdP91+iO/u0VspVgUxE1zMScvgpUCTgWc8bjGiaZqVWxWwChzj6xXkYF41GNAHF6UEigRA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=onE+VcsYA8ItvgqK3kJLnNYLySa5DQmx+ex//oonb8o=; b=cP1Rhyfu+a0M+0ilDnz/zhr9qyJEXAa8/FYszFgSdpfw6XFijKICOfXxx/cpvl17HC6Jbwd+Xt47kQ3UUTaPyzRlDn/k9728+qD1K7E87RWcaUhMgBQDoyIwvTJ5EL4O9z9t5VIwiFVJIC8HsnZWceDnNaw8uwT16U6ADQumzrThGJmfUt5NWGyNbUpdWHQYjAjhIXxRHYMv0Bbtfb+dtk3pSgofincBVJiww5p2BwHAnFUdNMbre+xyB3TH4WArMfkCxCWD5oXvYF1AVgttFx4H1yEeUUopzO6uUr/+sJ+UWk36+EEz1E1d0tQZY8c7Pybc1El7McTwfRC9dCEQoA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=outlook.com; dmarc=pass action=none header.from=outlook.com; dkim=pass header.d=outlook.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=onE+VcsYA8ItvgqK3kJLnNYLySa5DQmx+ex//oonb8o=; b=hNGRyYCi5OgbP/KYafRVtT4pkqPQ+t5KQI40yh4V2Brha+RIDIS8XjsghZrBGA63Vr8/8kHAQEsX8U/W8X7cBGniMMw8NXUnwSqNvph+Eu6lac8CGsxsOiUxeNT4rqCwGrTkyxTU+/KrG9O6o2VjcnLxzvrP8tYjjWDOURJj62XTJBmI3BiYprMpC8+z5V7RgAdv9At/f0tqYeZf7GUnYn5mUtoG3Nv5ppNB5vIs/N+LWM+kdBJ/TU5r8qBvd0GiEiZ9uBk5p1EtCbo96YRgWDr86xIMjujKvoZ9UILWCk5FaFBaAj2JQwLkDL14wb3gut8gjcNp2Sv7UtnejHm4zg==
Received: from PU1APC01FT057.eop-APC01.prod.protection.outlook.com (2a01:111:e400:7ebe::40) by PU1APC01HT209.eop-APC01.prod.protection.outlook.com (2a01:111:e400:7ebe::436) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3021.23; Tue, 26 May 2020 06:30:37 +0000
Received: from PU1PR06MB2215.apcprd06.prod.outlook.com (2a01:111:e400:7ebe::43) by PU1APC01FT057.mail.protection.outlook.com (2a01:111:e400:7ebe::263) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3021.23 via Frontend Transport; Tue, 26 May 2020 06:30:37 +0000
X-IncomingTopHeaderMarker: OriginalChecksum:21F53221ECF8D14E4B869AA41BF91F6A852C5671CA868081E8AF8B85FD05FD8C; UpperCasedChecksum:FD92B0F036A45149B8F0832235F19ADDFBC5F69C9A106CED9B7BD374A0E48A77; SizeAsReceived:9007; Count:53
Received: from PU1PR06MB2215.apcprd06.prod.outlook.com ([fe80::c1b8:f10b:a8b6:9cb]) by PU1PR06MB2215.apcprd06.prod.outlook.com ([fe80::c1b8:f10b:a8b6:9cb%7]) with mapi id 15.20.3021.029; Tue, 26 May 2020 06:30:37 +0000
Date: Tue, 26 May 2020 14:30:37 +0800
From: "Peng Liu" <liupengyjy@outlook.com>
To: "'Bob Hinden'" <bob.hinden@gmail.com>, "'IPv6 List'" <ipv6@ietf.org>
Subject: =?GB2312?B?u9i4tDogu9i4tDogQWRvcHRpb24gQ2FsbCBmb3IgIlRoZSBJUHY2IENvbXBhY3QgUm91dGluZyBIZWFkZXIgKENSSCki?=
References: <056a01d63319$4d5a70a0$e80f51e0$@chinamobile.com>, <202005261312158943794@foxmail.com>
X-GUID: 75310DDF-E7F8-44D1-98AE-B3159B43619C
X-Has-Attach: no
X-Mailer: Foxmail 7.2.9.115[cn]
Message-ID: <PU1PR06MB2215904B558FA0C5BE5E04AFDAB00@PU1PR06MB2215.apcprd06.prod.outlook.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart657160331173_=----"
X-ClientProxiedBy: HK2PR0302CA0010.apcprd03.prod.outlook.com (2603:1096:202::20) To PU1PR06MB2215.apcprd06.prod.outlook.com (2603:1096:803:38::11)
X-Microsoft-Original-Message-ID: <2020052614303471287717@outlook.com>
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from Peng (221.130.253.135) by HK2PR0302CA0010.apcprd03.prod.outlook.com (2603:1096:202::20) with Microsoft SMTP Server (version=TLS1_1, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA) id 15.20.3045.8 via Frontend Transport; Tue, 26 May 2020 06:30:35 +0000
X-Priority: 3
X-GUID: 75310DDF-E7F8-44D1-98AE-B3159B43619C
X-Has-Attach: no
X-Mailer: Foxmail 7.2.9.115[cn]
X-Microsoft-Original-Message-ID: <2020052614303471287717@outlook.com>
X-TMN: [fhzJ30NPPIdZjkmHnCZn+ATa6uHNaHop+fBbtxAi0wE=]
X-MS-PublicTrafficType: Email
X-IncomingHeaderCount: 53
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-Correlation-Id: bcf0fcfb-f2fb-4867-942e-08d8013e4cfe
X-MS-TrafficTypeDiagnostic: PU1APC01HT209:
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: MmVPCnkb1LKhF7vwi80Ti6T1yf+EJkSLN2+fEoq8UoVXo13siHd/yr5ZKjrW0eOfofU5G29Ccho5odUCudiO1RxKHa3aSRB1JRuSnqYlDKrQkNMFOL+ZVyiubMAl+vv+mFsqkcqfgSLdgxNOjSvNxRkxMmv1hSxOnzuarvx/zvwqnaCcglk9en916sNfoJ/XtM+JaECs+p0lQ/xfNR5cxhY11t7vkrTHq3zckWWrWIX0Jno7LMy6CZ4nDRdi/9Tq
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:0; SRV:; IPV:NLI; SFV:NSPM; H:PU1PR06MB2215.apcprd06.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:; DIR:OUT; SFP:1901;
X-MS-Exchange-AntiSpam-MessageData: oxEaxxBdHWLEUkyyNwp0sR7tgwUrQxiJm4eeief63NOWoyh38VZvtGKmlSqJKhF6pbO+XW2phDsE6DRyVd+MwAFBTNbANC2FCiqENfr+3okQPVJweULMR9j5Hbuhpb+Ljgphr0lJn0AsT3tirXZIhg==
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: bcf0fcfb-f2fb-4867-942e-08d8013e4cfe
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 26 May 2020 06:30:36.9474 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PU1APC01HT209
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/j3p_SaPgmmi6uPc2uCciif5ABpw>
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: Tue, 26 May 2020 06:30:43 -0000

Hi,

+1 with Du. I do not support the adoption.

It needs more discussion among several ideas at this stage and some of them may be deployed already.

Regards,
Peng Liu


liupengyjy@outlook.com
 
发件人: duzongpeng@foxmail.com
发送时间: 2020-05-26 13:12
收件人: 'Bob Hinden'; 'IPv6 List'
主题: 回复: Re: Adoption Call for "The IPv6 Compact Routing Header (CRH)"
Hi ,
 
I do not support the adoption.
 
IMO, more negiciations are needed for the document, as it is related to other working groups as well, and many diffrent ideas exit.
 
Best Regards
Zongpeng Du



duzongpeng@foxmail.com
 
发件人: 刘毅松
发送时间: 2020-05-26 12:51
收件人: 'Bob Hinden'; 'IPv6 List'
主题: Re: Adoption Call for "The IPv6 Compact Routing Header (CRH)"
Hi 6man WG,
 
I do not support the adoption.
 
For CRH based solution, the VPN context is encoded in a Destination Option
header located after the CRH. At the egress PE, the packet arrives with both
CRH and Destination Option headers. The egress PE will need to process TLVs
in DOH, which is not hardware efficient. The same applies to Ingress PE that
need to encapsulate topological instructions in CRH and service instructions
in DOH.
 
I think there is no need for defining a new data-plane (CRH) apparently more
complicated.
 
I hope the WG could consider this point in the adoption call.
 
Thanks
Yisong
 
-----邮件原件-----
发件人: ipv6 <ipv6-bounces@ietf.org> 代表 Bob Hinden
发送时间: 2020年5月16日 06:14
收件人: IPv6 List <ipv6@ietf.org>
抄送: Bob Hinden <bob.hinden@gmail.com>
主题: Adoption Call for "The IPv6 Compact Routing Header (CRH)"
 
This message starts a two-week 6MAN call on adopting:
 
Title:          The IPv6 Compact Routing Header (CRH)
Authors:        R. Bonica, Y. Kamite, T. Niwa, A. Alston, L. Jalil
File Name:      draft-bonica-6man-comp-rtg-hdr-21
Document date:  2020-05-14
 
https://tools.ietf.org/html/draft-bonica-6man-comp-rtg-hdr
 
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.
 
Please note that this is an adoption call, it is not a w.g. last call for
advancement, adoption means that it will become a w.g. draft.  As the
working group document, the w.g. will decide how the document should change
going forward.
 
This adoption call will end on 29 May 2020.
 
The chairs note there has been a lot of discussions on the list about this
draft.   After discussing with our area directors, we think it is
appropriate to start a working group adoption call.  The authors have been
active in resolving issues raised on the list.
 
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
 
 
 
 
 
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------