Re: What is the process?//RE: New Version Notification for draft-bonica-6man-comp-rtg-hdr-11.txt

"Darren Dukes (ddukes)" <ddukes@cisco.com> Tue, 18 February 2020 15:41 UTC

Return-Path: <ddukes@cisco.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 EBD2B12082A for <ipv6@ietfa.amsl.com>; Tue, 18 Feb 2020 07:41:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=J+eUXK8/; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=zwkeNnvV
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 HkwW8Cr-dYzZ for <ipv6@ietfa.amsl.com>; Tue, 18 Feb 2020 07:41:48 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8818120821 for <ipv6@ietf.org>; Tue, 18 Feb 2020 07:41:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5059; q=dns/txt; s=iport; t=1582040492; x=1583250092; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=giwiK7kavzuydWj7L3ixxSC8YE87tScJ4jlYIWGiO4o=; b=J+eUXK8/9JGL6xLKyTo4ajsgcr0qUdDSCpFsj/689C15WMv1H2sNTRqk c5ToJJcmMTg6NGlqfTsDALC6MCTwkv/elQSh4r3SG5P2sW8ZBUvKe88qK rwTQ7XtlppzZvDFfcGL60AFQ8k/kk5hSE4PECgB9D6eee0JlLrFGdGh/s 8=;
X-IPAS-Result: A0D0BwDyBExe/5RdJa1cChwBAQEBAQcBAREBBAQBAYF7gVQkLAVsWCAECyoKh1ADinlOghGYEYJSA1QJAQEBDAEBGAYPAgQBAYQ8AgICggMkOBMCAwEBAQMCAwEBAQEFAQEBAgEFBG2FNwyFZgEBAQECAQEBECgGAQErAQkDBAcEAgEIEQQBAQEeECcLHQgBAQQBEhsHgwQBgkoDDiABDqFOAoE5iGKCJ4J/AQEFgUNBgyUYggwJgTiMJBqBQT+BOCCCTD6CZAEBAwGBNC0HcIJLgiyNbIkGmRwKgjuHT48KHIJJfYcejluBZ45tiHeSRwIEAgQFAg4BAQWBaSKBWHAVGiEqAYJBCUcYDY4dOIM7hRSBXYNidAKBJ44wAYEPAQE
IronPort-PHdr: 9a23:vJkTRxx6qoxmx5HXCy+N+z0EezQntrPoPwUc9psgjfdUf7+++4j5YR2N/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1kAgMQSkRYnBZuJBVD4IeXCZC0hF8MEX1hgrDniaxpPFc3zZkPfrjip9TBCRkfZMgx4bqTtAInOgs+r1ue0vZrOfwFPgzn7arR3fl29rB7asY8dho4qJqE80VPPpWcAd+lNxGxuLE6e+nS0/sqq+Z9/7ylc8+ks8cJNS+36eL8kVv1V
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.70,456,1574121600"; d="scan'208";a="417986641"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 18 Feb 2020 15:41:31 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id 01IFfVGM009380 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 18 Feb 2020 15:41:31 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 18 Feb 2020 09:41:30 -0600
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 18 Feb 2020 10:41:29 -0500
Received: from NAM11-CO1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 18 Feb 2020 09:41:29 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=eMpGctbVIzHUQ7AR0zYzqFRJrkXAHT9c/bjvri4f/2rlyeiwA4dt5KAylWfaPl0LReBCr8DS0PbE5Im8jxtvGo3DkwUo/mxdV5mlF1KtigHgHh7kA2w1dvPLXPrwqL1zSHM5MFx6mKFOjpM/6DW3KI6BTode9L+AHg3xaLJ6+hMa+DI3EsNzmsbwa4TAeMX9sX/fPLwEK3a6eGtScGnikZGk/tOxtc2KGwdY5ee0ePR31cbLLSbf407nwHs40cUOV4iuYUAsKGPsLfEGiV1IVRG25PDWwMpt3rOqyLmPlafhGOkS2Ksr+ZM0ne8Lv4W83r3mAEigALqHar5YeB+DLw==
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=MaYPYD1OYKqKy5HJ3vOEMr6RLkk7ro1q+RFSJcqJ7SU=; b=PISn6s4qX4FoRdgzYbgWJmFZFjtVQgEwctIwwapCIAIgtEkAxynCBNb1z4RjPNtjq3IoL2BiWkBDjpoNIpy/QjP3jkOkjaoaoP+Iy9tBM2T1yOSrnmkdy/9M3CFmXqkO2IUT8SGaZTTGyGtyLRvpKYl9bdvdxQUPyvTNI5kB1LNut9MUUZ6EE1U/u0bUf9k6wN8sSqDM4cF3BFFiY7GN9CrEXc2r4Fw2FNt2uU3zNRNHfKvhB3IkG1hR+MzgIDTOYs9mSszLy3Wv230yiVgez2VdTq7ZqiepHTfqBJzQ3jQtYLJjgMrXud4I6JHTQu9xp6MiH48ndZ8Met8oY3GN3w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=MaYPYD1OYKqKy5HJ3vOEMr6RLkk7ro1q+RFSJcqJ7SU=; b=zwkeNnvVXwAiKPiV0V37QoWe9xbcIovwVGo+0lymUVy0SPAt3gK7NGJF4pAEayBVarkksdYtr17qC+ZVc9TX926Fa9f8CI3LuBwJ6NLjDfPMtyTykjN8SD/fQDV9d0TISsT7ulohWF5BJ3wbUFIt5WyLZgH17vSFWk6+oA1qlzU=
Received: from DM5PR11MB1818.namprd11.prod.outlook.com (10.175.92.9) by DM5PR11MB1322.namprd11.prod.outlook.com (10.168.104.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2729.25; Tue, 18 Feb 2020 15:41:28 +0000
Received: from DM5PR11MB1818.namprd11.prod.outlook.com ([fe80::d136:2a22:28ef:2075]) by DM5PR11MB1818.namprd11.prod.outlook.com ([fe80::d136:2a22:28ef:2075%12]) with mapi id 15.20.2729.032; Tue, 18 Feb 2020 15:41:28 +0000
From: "Darren Dukes (ddukes)" <ddukes@cisco.com>
To: Lizhenbin <lizhenbin@huawei.com>, Ron Bonica <rbonica@juniper.net>, 6man WG <ipv6@ietf.org>
Subject: Re: What is the process?//RE: New Version Notification for draft-bonica-6man-comp-rtg-hdr-11.txt
Thread-Topic: What is the process?//RE: New Version Notification for draft-bonica-6man-comp-rtg-hdr-11.txt
Thread-Index: AdXmYBGp2lCXwV4gQku4Dh4QMk6ilgAEdASA
Date: Tue, 18 Feb 2020 15:41:28 +0000
Message-ID: <59308FA1-229D-4C87-A20B-53B30C3CCDEE@cisco.com>
References: <5A5B4DE12C0DAC44AF501CD9A2B01A8D93634491@DGGEMM532-MBX.china.huawei.com>
In-Reply-To: <5A5B4DE12C0DAC44AF501CD9A2B01A8D93634491@DGGEMM532-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ddukes@cisco.com;
x-originating-ip: [161.44.212.253]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 871b1a6d-e04f-4e08-ed01-08d7b48904ed
x-ms-traffictypediagnostic: DM5PR11MB1322:
x-microsoft-antispam-prvs: <DM5PR11MB1322781168C527161D2F4027C8110@DM5PR11MB1322.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 031763BCAF
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(376002)(39860400002)(346002)(366004)(136003)(189003)(199004)(66476007)(53546011)(64756008)(66556008)(66446008)(33656002)(91956017)(6512007)(36756003)(15650500001)(66946007)(186003)(26005)(86362001)(76116006)(966005)(110136005)(8676002)(316002)(2906002)(2616005)(5660300002)(8936002)(6486002)(478600001)(6506007)(81166006)(71200400001)(81156014)(66574012); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR11MB1322; H:DM5PR11MB1818.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: yD/MkuP4mQdxCg3Ii6NumQxAlmAfFLODuSE++rEH4YhJsqfcq60b9ccC09icddqDmGqNjuuwogqhocBUPCDqiprJaqvwoMPsaUnjwiQ4rUN7LYx9p+/aJADtZO9ljrYpyHuwBcpTatRY7jotKtfILqFerua+ycwDXlr/uYUVB4QfaTbGElJv2NfRLjVysLvNKyulqVgSkz/HVHWuil+pX5rvagdYyYu+k5PCHKeovCZADHJguQ+lKb+xlZBOmCqmb8l83ni57XxPNfTH4FLsEtTguZkXhYWG0b83DTTiJd6gUMuIrSSRW9bv6RHrVoEmZmcrPOR13Cq3HdGHiCNurziUA4uBY4BjL5rXDRXzfjr0AdQw/QG0lTIp8ee/YcPybwhioWsG7tDqkdXio19j42TKptr7R4c1olmSegF0PWlwlW4qaCse/ijQ5qyDkqYCNHX/hLs/EDkEFGv7il0bPJdxtgW8/xfU/KaMrC653s1+zqTqFGNNRg1h3e7EBnalQXdEW0Fr9BFcmtajmF0p8g==
x-ms-exchange-antispam-messagedata: dU/Z/IxZQvKa6Tua9GFBaMuIjr0090CR5IqkeccaiYg/AqEIqrqnGa30gTtFKl6x+4jYebbBGCH7QxOEJUt9TrakOyAMqu7wd+YA3ZEueeLuevINgDhZDe59yJ6KuTNBRKAuLViiUs+7MFrLmo2CmQ==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5FA3CE11A0D92346AABA58CC8D635BA1@namprd11.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 871b1a6d-e04f-4e08-ed01-08d7b48904ed
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Feb 2020 15:41:28.1365 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: vJ/uVuuJ/B34yW1lzJwhoFP5Ne8PBgB/ufyCZAEu+Z3/BnGS/CZt8Ya4b/hawXy+O5VQF5J+ojqKbvOwzpA+Sw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB1322
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.12, xch-rcd-002.cisco.com
X-Outbound-Node: rcdn-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/sD80d0HtacG2T3mOM7wSGbvwzws>
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, 18 Feb 2020 15:41:55 -0000

+1 Zhenbin.

Ron, the only documented use of this CRH is your SRm6 draft.
If there are other use-cases can you please provide the pointer?

Thanks
  Darren


> On Feb 18, 2020, at 9:00 AM, Lizhenbin <lizhenbin@huawei.com> wrote:
> 
> I am truly a little surprised about the feedback on the draft. 
> 1. It was clarified by the RTG AD and the INT AD that the adoption in 6MAN WG should be done after the consensus and adoption of its corresponding draft in SPRING WG. I do not think removing the reference can make it as a stand-alone piece of work.
> 2. It was advised by the RTG AD that we should identify the requirement of the compression, then discuss the possible solutions. Can the 6MAN WG adopt the draft without the consensus on the requirement?
> 3. There are already multiple solutions on this topic. I do not think that it is well discussed and justified that the solution proposed by the draft has much advantages.
> 
> As the attendees of the IETF meetings learning what has been discussed, I wish all of us could respect the process. 
> 
> 
> Best Regards,
> Zhenbin (Robin)
> 
> 
> 
> 
> -----Original Message-----
> From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Ron Bonica
> Sent: Sunday, February 16, 2020 7:56 PM
> To: 6man WG <ipv6@ietf.org>
> Subject: FW: New Version Notification for draft-bonica-6man-comp-rtg-hdr-11.txt
> 
> Folks,
> 
> Over the last several weeks, customers who have no interest in Segment Routing have expressed interest in the CRH. So, we have updated the CRH draft, removing all references to Segment Routing and letting it stand alone as an IPv6 Routing header.
> 
> While Segment Routing may one day be a user of the CRH, it will not be the only user.
> 
> Please review this document as a stand-alone piece of work.
> 
>                                                                          Ron
> 
> 
> 
> Juniper Business Use Only
> 
> -----Original Message-----
> From: internet-drafts@ietf.org <internet-drafts@ietf.org> 
> Sent: Sunday, February 16, 2020 7:46 PM
> To: Ron Bonica <rbonica@juniper.net>; Ning So <ning.so@ril.com>; Andrew Alston <andrew.alston@liquidtelecom.com>; Ning So <Ning.So@ril.com>; Tomonobu Niwa <to-niwa@kddi.com>; Andrew Alston <Andrew.Alston@liquidtelecom.com>; Yuji Kamite <y.kamite@ntt.com>
> Subject: New Version Notification for draft-bonica-6man-comp-rtg-hdr-11.txt
> 
> 
> A new version of I-D, draft-bonica-6man-comp-rtg-hdr-11.txt
> has been successfully submitted by Ron Bonica and posted to the IETF repository.
> 
> Name:		draft-bonica-6man-comp-rtg-hdr
> Revision:	11
> Title:		The IPv6 Compressed Routing Header (CRH)
> Document date:	2020-02-16
> Group:		Individual Submission
> Pages:		16
> URL                      https://urldefense.com/v3/__https://tools.ietf.org/html/draft-bonica-6man-comp-rtg-hdr-11__;!!NEt6yMaO-gk!XUarDeMbPwKiwm2y8vDbWaR0FSJpEu7t-k660_1iuPIG9nwBgZjnN_9Nrq5fuRdE$ 
> Status:                https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-bonica-6man-comp-rtg-hdr/__;!!NEt6yMaO-gk!XUarDeMbPwKiwm2y8vDbWaR0FSJpEu7t-k660_1iuPIG9nwBgZjnN_9Nrg593WfL$ 
> Htmlized:           https://urldefense.com/v3/__https://tools.ietf.org/html/draft-bonica-6man-comp-rtg-hdr-11__;!!NEt6yMaO-gk!XUarDeMbPwKiwm2y8vDbWaR0FSJpEu7t-k660_1iuPIG9nwBgZjnN_9Nrq5fuRdE$ 
> Htmlized:           https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-bonica-6man-comp-rtg-hdr__;!!NEt6yMaO-gk!XUarDeMbPwKiwm2y8vDbWaR0FSJpEu7t-k660_1iuPIG9nwBgZjnN_9NrnDoZDQO$ 
> Diff:           
> Abstract:
>   This document defines two new Routing header types.  Collectively,
>   they are called the Compressed Routing Headers (CRH).  Individually,
>   they are called CRH-16 and CRH-32.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/ipv6__;!!NEt6yMaO-gk!XUarDeMbPwKiwm2y8vDbWaR0FSJpEu7t-k660_1iuPIG9nwBgZjnN_9Nrg0ihiqf$ 
> --------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------