IETF Logo Mail Archive

RE: What 's the process?

Ron Bonica <rbonica@juniper.net> Wed, 19 February 2020 21:44 UTC

Return-Path: <rbonica@juniper.net>
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 4C83E120128 for <ipv6@ietfa.amsl.com>; Wed, 19 Feb 2020 13:44:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net header.b=ZG+mIBWP; dkim=pass (1024-bit key) header.d=juniper.net header.b=jAKMYNrQ
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 pTG0qShYsqMF for <ipv6@ietfa.amsl.com>; Wed, 19 Feb 2020 13:44:43 -0800 (PST)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 DA94712022E for <ipv6@ietf.org>; Wed, 19 Feb 2020 13:44:42 -0800 (PST)
Received: from pps.filterd (m0108161.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 01JLbXnN013420; Wed, 19 Feb 2020 13:44:34 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=PPS1017; bh=D8I6H9cBaonRDPWSnSrthxnn4IgUureBMqdSEuSp8nA=; b=ZG+mIBWP1Yb3L+1xlPyp1Sedol2tIgfNXPQKe8nbApvY2ktElcocnPQ4w3szdDLroVHW Xqwyof4D4qGrccHYtgtI2bFvCGo4DRbXUh8zLpWfX1VPAoexns7T4MNYBlHqpsTmmsrL nAngEUzG5rLml3xzVnSMI1uA3sR6N3peTGao4GTgMNGhx5gcxxdieAh7GfGmgEexT7GK 9ghuDzRnNzLvAyULAf/rbRHy389A2/9EqPu+lkuaaptP1mvCF9z02nsaOLU5L+E+ghSM 2S2dWw9y09dn9pylKlwJKDnR5jFk/PDTveAkH4MaXRlrliSryYlh6UDvkleDqxGQd8OK bQ==
Received: from nam10-dm6-obe.outbound.protection.outlook.com (mail-dm6nam10lp2102.outbound.protection.outlook.com [104.47.58.102]) by mx0b-00273201.pphosted.com with ESMTP id 2y8ucpsvfm-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 19 Feb 2020 13:44:34 -0800
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=VDhLLEWKLKakzi5cn2qNUSNZKOfCcOIHbXdSE1pxgwE2dT1bjHvqqEpTYbb5mAOOT2Gd+H/Cawq75P6eIbaClot/WoMe7E0Arj8CjRxP+7xN3AKX5l/RYfJumVBeKX+6dNnlGAd5E2158RS+mSwD3Dvy/A6WktQBdAdB/maGw+1wgz1TR15tnS6gxAzA2/J/StFUKll8MJxubmBSweXxZ6PFOa/h51FTgwNgs8dg40zOoyt/gUQZFW46ls/Y+t6ZO8eXlOSbJBqhfjZckezssTT88zNmkX37lzAHmyDavorjv7GoqqQEw40aVYEzB4DgkT3sUkrdxHlM0advrQ1STw==
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=D8I6H9cBaonRDPWSnSrthxnn4IgUureBMqdSEuSp8nA=; b=BErz8d2jTXnqX0g0uVnfdWYvknLgGMzGWQG4CTN7Jg3jVY1NqKc7zRvpU9iG4QCpD2B+QMuKOnsQWso2ZQouqnto349wkeTxnuwU4nIKLt2X3GgYcCk8b3aCzrTyVTq6B41WVPKYvYywrbYyq/+lUcz84WvPeBGQS8ya09w/J3TSZfgcR6vWT42e/7OisPYHFbnPxkSGEEklAEBKV201mZ49VFOX5ppcgoM5Ppja771/w5NBF5divK1Df1ylxXENeHKhp646Gta3vN59qjcic41jzjvKgVD02zJmSk9eTXyPrXqCuLCCzwYtwM4fC65iozhEjixK0r6LT3cNe5WSxQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=juniper.net; dmarc=pass action=none header.from=juniper.net; dkim=pass header.d=juniper.net; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=D8I6H9cBaonRDPWSnSrthxnn4IgUureBMqdSEuSp8nA=; b=jAKMYNrQP5AyGxxCpLS4SZMavNmLYWtaTSHgPDfxcsUY/XV3Lo0SrCClLx+MAXMF09EeldmZkP+QZ2ymvAw9a9Kqs0pjZg49QSpNiPqQfkNOnJFalNp9F3UmpH56UN6zqJJmFlUMldXsNasXPqeM5XM5WuUNDC+G3LIfiUk5B6Y=
Received: from DM6PR05MB6348.namprd05.prod.outlook.com (20.178.224.143) by DM6PR05MB6411.namprd05.prod.outlook.com (20.178.27.225) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2750.16; Wed, 19 Feb 2020 21:44:32 +0000
Received: from DM6PR05MB6348.namprd05.prod.outlook.com ([fe80::cdd:ea54:f213:7e02]) by DM6PR05MB6348.namprd05.prod.outlook.com ([fe80::cdd:ea54:f213:7e02%5]) with mapi id 15.20.2750.016; Wed, 19 Feb 2020 21:44:32 +0000
From: Ron Bonica <rbonica@juniper.net>
To: James Guichard <james.n.guichard@futurewei.com>, "Chengli (Cheng Li)" <chengli13@huawei.com>, 6man WG <ipv6@ietf.org>, Lizhenbin <lizhenbin@huawei.com>, "Darren Dukes (ddukes)" <ddukes@cisco.com>
Subject: RE: What 's the process?
Thread-Topic: What 's the process?
Thread-Index: AdXmRp2+j8roA37CTn+ijAU1LR1JcgAZNNvAAC6HN1AAAJO3UA==
Date: Wed, 19 Feb 2020 21:44:32 +0000
Message-ID: <DM6PR05MB63481B4D008A0A6BC7FF0243AE100@DM6PR05MB6348.namprd05.prod.outlook.com>
References: <C7C2E1C43D652C4E9E49FE7517C236CB0290463E@dggeml509-mbx.china.huawei.com> <DM6PR05MB6348D001F5397DFF015BE22AAE110@DM6PR05MB6348.namprd05.prod.outlook.com> <DM6PR13MB3066F0BD909E01A73342CFD2D2100@DM6PR13MB3066.namprd13.prod.outlook.com>
In-Reply-To: <DM6PR13MB3066F0BD909E01A73342CFD2D2100@DM6PR13MB3066.namprd13.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Enabled=True; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Owner=rbonica@juniper.net; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SetDate=2020-02-18T23:07:20.3523561Z; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Name=Juniper Business Use Only; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Application=Microsoft Azure Information Protection; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ActionId=d58222e4-f473-4032-9705-98d7aa2bdf92; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Extended_MSFT_Method=Automatic
dlp-product: dlpe-windows
dlp-version: 11.3.2.8
dlp-reaction: no-action
x-originating-ip: [66.129.241.13]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 79dcddb2-57be-4d5d-a7be-08d7b584e794
x-ms-traffictypediagnostic: DM6PR05MB6411:
x-microsoft-antispam-prvs: <DM6PR05MB6411F0410631F35A9EE9D1A7AE100@DM6PR05MB6411.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0318501FAE
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(136003)(366004)(39860400002)(396003)(376002)(346002)(189003)(199004)(53546011)(6506007)(66574012)(33656002)(7696005)(5660300002)(81166006)(2906002)(186003)(45080400002)(478600001)(52536014)(8676002)(81156014)(66556008)(64756008)(110136005)(66446008)(86362001)(966005)(316002)(71200400001)(76116006)(66476007)(26005)(9686003)(8936002)(66946007)(55016002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR05MB6411; H:DM6PR05MB6348.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 45uXMNk1zkWISHHieonmxYUsy2lpPAiNjN0Dh8SxyjniRidDVTodQ/uAtvBOQD+PTXo2QNGVEuMhvykh4PsIAkjs2WO1b/c8WyVmKW1y/sZZcdcRNkl826b7a4HsJMx0jhfvjzHCMs7q8b+gd2AgSQu3iIAjgar231RVq1WZEBL1weHtr+CJnpHsRa+MEJkI/3TT2mQamYSSxFIhge9zPkzUZzhMgEPjo5Bz2nVXIeGVsx3f6Ommr+FfRHyQMo9hteYmrjJEIIKaweBa9Ocyv9ptD7GiTCWj2t6UoZSiQz3CIlleTDEpqLIiQDv7acP7xe1cwmplgpZh+oH72rHGWCR5FkEUIvF9AgvEPfLIG6N1WCIV8/GI1MvtZFsqTRPKkyiiCyYF+WoNYR8U6vBsnozGdLNyUflSUv5AzZ5m02rkD4I2vhKxTdqqwBtErQ2L7ShOb9P2+G+lqdfCRnnJe+wxK5LrmYgttWhB9yTgfVQo2ibmt0o9l7AdlsyEbu/+CMBFe8ANdIbgpeM4ooa7Ag==
x-ms-exchange-antispam-messagedata: bkuyyI3KsQ+stqqVil/uNeWqX2Ha4YFqFYZHOoiyKaa9v16J/fIr2bdRW75gfFEGeELXCmISLZdXNmaBojh3Bgm+zjMEASvOLAuuRANSzkEq7zSCRNNVqYbpg2Gs5lHeyZmtQ21/GOwZL+kNuusbDw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 79dcddb2-57be-4d5d-a7be-08d7b584e794
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Feb 2020 21:44:32.0285 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: fA+qJAqeN7A3FocccQehG8XcE1O8EuWOH6tSMIzS868xPUgNrTmanETKjhxLOwE9JA/TS3Sw/NbVa0KUgHtfoQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR05MB6411
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.572 definitions=2020-02-19_06:2020-02-19, 2020-02-19 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 phishscore=0 mlxlogscore=999 impostorscore=0 mlxscore=0 priorityscore=1501 suspectscore=0 lowpriorityscore=0 spamscore=0 bulkscore=0 adultscore=0 malwarescore=0 clxscore=1011 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2001150001 definitions=main-2002190160
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/8StX5BG8AF7pGmfolvAyHtriRDw>
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: Wed, 19 Feb 2020 21:44:46 -0000

Jim,

CRH is clearly not the same as RH0! Compression is a new requirement.

AFAICS, there are two ways to compress a routing header. These are:

- By making the SID represent an entry in a table like the CRH-FIB.
- By making the SID the only parameter to an algorithm that yields an IPv6 address.

I chose the former approach because the later only works when network addressing conforms to its requirements.

As I say in the draft, the CRH-FIB can be populated:

- through the CLI
- through a controller
- through distributed routing protocols

The protocols that support these interfaces are beyond the scope of the current draft.

                                                                                                                         Ron




Juniper Business Use Only

-----Original Message-----
From: James Guichard <james.n.guichard@futurewei.com> 
Sent: Wednesday, February 19, 2020 3:54 PM
To: Ron Bonica <rbonica@juniper.net>; Chengli (Cheng Li) <chengli13@huawei.com>; 6man WG <ipv6@ietf.org>; Lizhenbin <lizhenbin@huawei.com>; Darren Dukes (ddukes) <ddukes@cisco.com>
Cc: James Guichard <james.n.guichard@futurewei.com>
Subject: RE: What 's the process?

Hi Ron,

Having reminded myself of what RH0 was 😉 CRH seems very different given it is not a standalone IPv6 extension header since it introduces a notion of SIDs as its base forwarding construct. These SIDs need to be advertised and signaled via routing protocols and other mechanisms (indicating that other documents will in fact be necessary and therefore become a dependency) in order to distribute the mapping tables and setup the CRH FIB. This is quite different from RH0 which used IPv6 addresses as segments and did not need any new extensions in IPv6 routing protocols (CLI does not count in a serious deployment).

Respectfully,

Jim


-----Original Message-----
From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Ron Bonica
Sent: Tuesday, February 18, 2020 6:07 PM
To: Chengli (Cheng Li) <chengli13@huawei.com>; Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>; 6man WG <ipv6@ietf.org>; Lizhenbin <lizhenbin@huawei.com>; Darren Dukes (ddukes) <ddukes@cisco.com>
Subject: RE: What 's the process?

Hello Cheng, Robin and Darren,

The CRH draft depends only upon the documents that it references as normative. It does not depend on any other documents.
Do you see anything in the text that suggests otherwise?

The use-case is exactly the same as RH0. The application needs a traffic steering mechanism. However, there are two new constraints. These are:

	- The security vulnerabilities that caused RH0 to be deprecated must be addressed
	- The Routing header must be deployable, even when the number of segments is large

In the future, other document may depend on CRH. However, CRH does not depend upon them.

                                                                                                 Ron


Juniper Business Use Only

-----Original Message-----
From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Chengli (Cheng Li)
Sent: Tuesday, February 18, 2020 5:42 AM
To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>; 6man WG <ipv6@ietf.org>
Subject: What 's the process?

Hi Ron,

I see the related references to segment routing documents are deleted, including https://urldefense.com/v3/__https://nam03.safelinks.protection.outlook.com/?url=https*3A*2F*2Furldefense.com*2Fv3*2F__https*3A*2F*2Ftools.ietf.org*2Fhtml*2Fdraft-bonica-spring-sr-mapped-six-00__*3B!!NEt6yMaO-gk!SZBw1bJrNzc15rJ32cZACDoLU6rdesCKqqb7L_Kk7fAG01S3NeZHhGXcjrD0I-8D*24&amp;data=02*7C01*7Cjames.n.guichard*40futurewei.com*7Cf325d28ab1194a15d80b08d7b4c75ee8*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C0*7C637176640701783834&amp;sdata=1wWvn7hS*2BCScwWpHv9g1OtbkiLnxYIwdqZwxytD*2B8t8*3D&amp;reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSU!!NEt6yMaO-gk!Vb81uRPH66S9jp_Z6E-EZGHvEgJY87e5D92z1L8wDm1EHI9AThX_OgI2C8wxxOyP$  

May I ask a question? What is the relation between this document and the SRm6 document? Independent?  If not, what is the process of adopting these two documents? 

BTW, in which condition that we can say a solution is a stand-alone piece of work?

Thanks,
Cheng



-----Original Message-----
From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Ron Bonica
Sent: Monday, February 17, 2020 8:56 AM
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://nam03.safelinks.protection.outlook.com/?url=https*3A*2F*2Furldefense.com*2Fv3*2F__https*3A*2F*2Ftools.ietf.org*2Fhtml*2Fdraft-bonica-6man-comp-rtg-hdr-11__*3B!!NEt6yMaO-gk!SZBw1bJrNzc15rJ32cZACDoLU6rdesCKqqb7L_Kk7fAG01S3NeZHhGXcjrnJ8ZXY*24&amp;data=02*7C01*7Cjames.n.guichard*40futurewei.com*7Cf325d28ab1194a15d80b08d7b4c75ee8*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C0*7C637176640701783834&amp;sdata=67qEaIRngkDzSDe*2FkJjgQbV2DTS0BoHZxAhspP53j*2B0*3D&amp;reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSU!!NEt6yMaO-gk!Vb81uRPH66S9jp_Z6E-EZGHvEgJY87e5D92z1L8wDm1EHI9AThX_OgI2C1SWvMbn$  
Status:                https://urldefense.com/v3/__https://nam03.safelinks.protection.outlook.com/?url=https*3A*2F*2Furldefense.com*2Fv3*2F__https*3A*2F*2Fdatatracker.ietf.org*2Fdoc*2Fdraft-bonica-6man-comp-rtg-hdr*2F__*3B!!NEt6yMaO-gk!SZBw1bJrNzc15rJ32cZACDoLU6rdesCKqqb7L_Kk7fAG01S3NeZHhGXcjuJwFxBl*24&amp;data=02*7C01*7Cjames.n.guichard*40futurewei.com*7Cf325d28ab1194a15d80b08d7b4c75ee8*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C0*7C637176640701783834&amp;sdata=SSVeM4lVk63SiHraCxcK05tuZjJwcRrnlhUCq2eHUXM*3D&amp;reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJQ!!NEt6yMaO-gk!Vb81uRPH66S9jp_Z6E-EZGHvEgJY87e5D92z1L8wDm1EHI9AThX_OgI2C4_zAwos$  
Htmlized:           https://urldefense.com/v3/__https://nam03.safelinks.protection.outlook.com/?url=https*3A*2F*2Furldefense.com*2Fv3*2F__https*3A*2F*2Ftools.ietf.org*2Fhtml*2Fdraft-bonica-6man-comp-rtg-hdr-11__*3B!!NEt6yMaO-gk!SZBw1bJrNzc15rJ32cZACDoLU6rdesCKqqb7L_Kk7fAG01S3NeZHhGXcjrnJ8ZXY*24&amp;data=02*7C01*7Cjames.n.guichard*40futurewei.com*7Cf325d28ab1194a15d80b08d7b4c75ee8*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C0*7C637176640701783834&amp;sdata=67qEaIRngkDzSDe*2FkJjgQbV2DTS0BoHZxAhspP53j*2B0*3D&amp;reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSU!!NEt6yMaO-gk!Vb81uRPH66S9jp_Z6E-EZGHvEgJY87e5D92z1L8wDm1EHI9AThX_OgI2C1SWvMbn$  
Htmlized:           https://urldefense.com/v3/__https://nam03.safelinks.protection.outlook.com/?url=https*3A*2F*2Furldefense.com*2Fv3*2F__https*3A*2F*2Fdatatracker.ietf.org*2Fdoc*2Fhtml*2Fdraft-bonica-6man-comp-rtg-hdr__*3B!!NEt6yMaO-gk!SZBw1bJrNzc15rJ32cZACDoLU6rdesCKqqb7L_Kk7fAG01S3NeZHhGXcjsOwC5Gy*24&amp;data=02*7C01*7Cjames.n.guichard*40futurewei.com*7Cf325d28ab1194a15d80b08d7b4c75ee8*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C0*7C637176640701783834&amp;sdata=ZPpncF4XNkzxuIvf42MeXyxbgavHyhAZIigp4PhKoOs*3D&amp;reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJQ!!NEt6yMaO-gk!Vb81uRPH66S9jp_Z6E-EZGHvEgJY87e5D92z1L8wDm1EHI9AThX_OgI2C_wEfuPT$  
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://nam03.safelinks.protection.outlook.com/?url=https*3A*2F*2Furldefense.com*2Fv3*2F__https*3A*2F*2Fwww.ietf.org*2Fmailman*2Flistinfo*2Fipv6__*3B!!NEt6yMaO-gk!SZBw1bJrNzc15rJ32cZACDoLU6rdesCKqqb7L_Kk7fAG01S3NeZHhGXcjrjvNnZo*24&amp;data=02*7C01*7Cjames.n.guichard*40futurewei.com*7Cf325d28ab1194a15d80b08d7b4c75ee8*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C0*7C637176640701783834&amp;sdata=7Z5j1Y5UdGZX0Ctj3DolRX4AQhAJGJ918cIZUj*2FnXTI*3D&amp;reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSU!!NEt6yMaO-gk!Vb81uRPH66S9jp_Z6E-EZGHvEgJY87e5D92z1L8wDm1EHI9AThX_OgI2Cyjq8yFG$  
--------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://urldefense.com/v3/__https://nam03.safelinks.protection.outlook.com/?url=https*3A*2F*2Furldefense.com*2Fv3*2F__https*3A*2F*2Fwww.ietf.org*2Fmailman*2Flistinfo*2Fipv6__*3B!!NEt6yMaO-gk!SZBw1bJrNzc15rJ32cZACDoLU6rdesCKqqb7L_Kk7fAG01S3NeZHhGXcjrjvNnZo*24&amp;data=02*7C01*7Cjames.n.guichard*40futurewei.com*7Cf325d28ab1194a15d80b08d7b4c75ee8*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C0*7C637176640701783834&amp;sdata=7Z5j1Y5UdGZX0Ctj3DolRX4AQhAJGJ918cIZUj*2FnXTI*3D&amp;reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSU!!NEt6yMaO-gk!Vb81uRPH66S9jp_Z6E-EZGHvEgJY87e5D92z1L8wDm1EHI9AThX_OgI2Cyjq8yFG$  
--------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://urldefense.com/v3/__https://nam03.safelinks.protection.outlook.com/?url=https*3A*2F*2Fwww.ietf.org*2Fmailman*2Flistinfo*2Fipv6&amp;data=02*7C01*7Cjames.n.guichard*40futurewei.com*7Cf325d28ab1194a15d80b08d7b4c75ee8*7C0fee8ff2a3b240189c753a1d5591fedc*7C1*7C0*7C637176640701783834&amp;sdata=NKKItAzgkIUrUVX3yOl7VBUpAD*2BsTeTgPczsvWIFdv4*3D&amp;reserved=0__;JSUlJSUlJSUlJSUlJSUlJQ!!NEt6yMaO-gk!Vb81uRPH66S9jp_Z6E-EZGHvEgJY87e5D92z1L8wDm1EHI9AThX_OgI2C2TMFAFb$ 
--------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email