RE: Applicability, Use-cases, and Architecture for the CRH

Ron Bonica <rbonica@juniper.net> Sat, 16 May 2020 05:24 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 796373A046A for <ipv6@ietfa.amsl.com>; Fri, 15 May 2020 22:24:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.099
X-Spam-Level:
X-Spam-Status: No, score=-0.099 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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=Ed2w+sQ3; dkim=pass (1024-bit key) header.d=juniper.net header.b=Uogn4sZc
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 sqyiKxrAJVyq for <ipv6@ietfa.amsl.com>; Fri, 15 May 2020 22:24:09 -0700 (PDT)
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 435EB3A045B for <6man@ietf.org>; Fri, 15 May 2020 22:24:09 -0700 (PDT)
Received: from pps.filterd (m0108163.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 04G5O7e7008201; Fri, 15 May 2020 22:24:07 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=jQwegjyr7z52IIfqCj0De3xtFdGLi1SXltT6243QJ2M=; b=Ed2w+sQ3K7Ytwgv4dWVl7QC6UP/qDgzYPby9pxd/cWf16X3NJYNcnIygUn9e9vgvwu2s iCdred824nlQHJE2CDIbFnwHyrVRvjiYukD8O1dYjEL1yBUAS7/36AqXMPJgPzu9zGO/ VE8gMwA2HCgnxB4zpW2gSd+8aq1k5SbfYG3HaZdYBQ6qUoGRWgnlou+mVa7EvDvroSqs Fk0tqKhMkdhF7gf8kK/tJg+Y1cFFzV58hspx/yOoRE0T3jZ44iBStUOGiOgMK62G6HUQ QKmgyt1oh16UIFBm6kp271M40F/RhwKfIQTbsZalUlAQVKeHc2eABqblkUAwVmkEVu4x 0g==
Received: from nam10-mw2-obe.outbound.protection.outlook.com (mail-mw2nam10lp2105.outbound.protection.outlook.com [104.47.55.105]) by mx0b-00273201.pphosted.com with ESMTP id 3100xwqjak-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 15 May 2020 22:24:06 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=R89whWB4dPWmypxqprm7twxtecsCXCguFYveAylq3ozPpU0+oqNUSl/PDHQLHObJSduiAZ+olmpmxhSrxP1wgd38YmBMLZKp1EQS3ipEPqNtWUuMVv95Icy0JW3bpe2duTft81+VAygRJao87Khv8G53xOQOoUMHXITaxh3u2Zt24TyM8g2sAA9QPJv8mdQvksmcWlybt9ei55sH5c1lhaePJPR/v/ZDuNGsX0rrStTeC3DVHtI07fuln+Vb1FoJCyNHz0Ln2aqk+hLTq4Bq2MRrv4/P114UcTCaQZUJB+aom6igxUlqYveWeV7YqkJv4UTgmLvkTIfSGKl28vUUXg==
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=jQwegjyr7z52IIfqCj0De3xtFdGLi1SXltT6243QJ2M=; b=KkSENZhVbNBxhMIZPIKNorzEKcIYpS9jnTprab/zPQxqXbfJZwAmmw9I5VYnJulZQ1HgOpKaiOP4/0P7wW98Aq8UTAkVQnSa5iHWeXIbACntdmL1LaXBn/+sWPBvs3C7YiM5KZ5Q3ukxwE1xSWHlDBgsVRXF+MDfYQajO3cxGK1KaATBjYRXVNAUu/8Xm86Q6BX8reO27T+MsQj73FZI20EPkN3+TLWDzjJoq83Wp1LXgHQu/QmQDnxPqPM6s8AnLsFI2FVabUWw44aDF5Oc1/DT1x9b3E+wiAuw/F59565yc7HZvM0PsXbnsKyapRV3hzHhn6TIxA4cM/dn15eL0A==
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=jQwegjyr7z52IIfqCj0De3xtFdGLi1SXltT6243QJ2M=; b=Uogn4sZcv8lje6rQHebLqvV+5381wZtNxwcGtCt0SMMFq8QSOUQK3TgZ07XCnysEt01VhrBMokB2tIOqbFxfhQFmTUlZf8jFRoa8oDieJ38qomWVqKNWGdc+I9DHniiH97IhfWVRIPOkyg5u1MI/qAlrcUyLrAauQ121Nzx+sgM=
Received: from DM6PR05MB6348.namprd05.prod.outlook.com (2603:10b6:5:122::15) by DM6PR05MB5691.namprd05.prod.outlook.com (2603:10b6:5:10d::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3021.12; Sat, 16 May 2020 05:24:03 +0000
Received: from DM6PR05MB6348.namprd05.prod.outlook.com ([fe80::c020:3bf5:7230:75e3]) by DM6PR05MB6348.namprd05.prod.outlook.com ([fe80::c020:3bf5:7230:75e3%4]) with mapi id 15.20.3021.010; Sat, 16 May 2020 05:24:03 +0000
From: Ron Bonica <rbonica@juniper.net>
To: Mark Smith <markzzzsmith@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: 6MAN <6man@ietf.org>
Subject: RE: Applicability, Use-cases, and Architecture for the CRH
Thread-Topic: Applicability, Use-cases, and Architecture for the CRH
Thread-Index: AdYrGbsERWsmzeISTnCP4gDdTqC7HQACUbmAAAP+E5AAAnizAAAAz20AAABwRxA=
Date: Sat, 16 May 2020 05:24:03 +0000
Message-ID: <DM6PR05MB6348C9903820C060B1AE67DEAEBA0@DM6PR05MB6348.namprd05.prod.outlook.com>
References: <DM6PR05MB634898C57C186C0133B2F852AEBA0@DM6PR05MB6348.namprd05.prod.outlook.com> <fec4e31b-0c98-7b3b-bbf0-d3225a21bc30@gmail.com> <DM6PR05MB634857FF18A11F58C42EC176AEBA0@DM6PR05MB6348.namprd05.prod.outlook.com> <a6f6ff2c-3ae7-6ffc-928d-fcf37557abfe@gmail.com> <CAO42Z2xkmZdL0G=1iafyFKz6wWy69VcHtQ5ntu497eL8iVuzWw@mail.gmail.com>
In-Reply-To: <CAO42Z2xkmZdL0G=1iafyFKz6wWy69VcHtQ5ntu497eL8iVuzWw@mail.gmail.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_SetDate=2020-05-16T05:24:01Z; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Method=Standard; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Name=0633b888-ae0d-4341-a75f-06e04137d755; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ActionId=ddc1d592-2517-4df0-a3cd-d842a8f49904; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ContentBits=2
dlp-product: dlpe-windows
dlp-version: 11.4.0.45
dlp-reaction: no-action
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=juniper.net;
x-originating-ip: [108.28.233.91]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: d3616c11-b4fb-4a04-e34f-08d7f95958d9
x-ms-traffictypediagnostic: DM6PR05MB5691:
x-microsoft-antispam-prvs: <DM6PR05MB5691688BAE13830E27A4875CAEBA0@DM6PR05MB5691.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 040513D301
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: UGUtSu3x3jJsyf271bc/jvrRHgHLOE5eeTmDlTCxeShLVj8KmnHP9hsQdnoaSuiFdRJcf0RdbLykMyXxCALs1+igh+huG3lG/IY+BSuqkgrabJZ0XSqYTfKzxfqArVCXXcWiaYJRtp4rIhJODKXzgbgS3bxPTGzvhW91RMPUff2MQrHKA8dHe02Hzl1mJX1Kif9ISJA+M5yIvyMx7bG8Gnls9Zoo3cfSpvdYPZKTU7G03bNfjk62acwQHwrQ5ZBNBi/bfgUcxj53b2jiu2uHCDAV5mcV5Ll+OXSbHgyvls1G2Of+q4KCX+WjO6Fu4zCu0FDEP31LWb2v1i/h/WfYvAFbSGYwheVG1sCxErvD8dUU8KWGBj4poMv4lu/emYVTdw/aTdPLrtXMKGzMfSCwlw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM6PR05MB6348.namprd05.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(376002)(366004)(396003)(346002)(136003)(39860400002)(8936002)(6506007)(53546011)(8676002)(86362001)(166002)(66574014)(966005)(316002)(110136005)(33656002)(26005)(7696005)(478600001)(5660300002)(9686003)(2906002)(52536014)(66446008)(55016002)(4326008)(76116006)(71200400001)(64756008)(66556008)(186003)(66946007)(66476007); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: bzaRUBnq6X+xeoZLD6qHusDfPkLgPSqk+OVDWAxOp+Bw7FdbM17kcu0tDSirX6wkrUzFgt7yU+1WvYeqEQ5vlL8NXCiuZ4+b7W7eGKwmDcjrNOMjGcwnSiYrD0ziM3SJYKqMXIB3/M89NLzhDbNdhNerGCy3f7cs03i6W7O1IrhSd4aTpbwaZ+Zvr47RVPnGGcRF+iROhDjrM2BgTVfdsxJAJ04fXl1/VZeqeuBeuVNjFmx9BEZbxLY2RE2+YCDmEiwmJR13IpeKHWMXAanLAHAnKqBHQUEdh3ZKswlX94aZEM+DtM6MPHwcZ7/65g1GSe+GPPqjtOd/Exq+3Kz2OsIgxwBGk5qL/lwspBux0yOViUTJYy9uow8z4HShENSDWFdnZ2KOW3UGDAw0LeJMqzHtaK3wZU5q+yDdmSdZ0TCwkMZUE4jOiJxJEbYEODrfr2Faa/nQIL40GT29eXWBam4REAn7HJYo7QoMCpu9Ex5tL7fWmqmwJoTDcRFZqxNP
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DM6PR05MB6348C9903820C060B1AE67DEAEBA0DM6PR05MB6348namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: d3616c11-b4fb-4a04-e34f-08d7f95958d9
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 May 2020 05:24:03.2835 (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: jvuaATpv3QxSb0EImuNx+La5x/qzvurV1O08bf2XfDhzOOy0kM7IWPPx795a7/trm1AbL+TTj7pAddDcHj4xQQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR05MB5691
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.216, 18.0.676 definitions=2020-05-16_03:2020-05-15, 2020-05-16 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 clxscore=1015 adultscore=0 bulkscore=0 impostorscore=0 malwarescore=0 suspectscore=0 phishscore=0 spamscore=0 mlxlogscore=999 priorityscore=1501 lowpriorityscore=0 mlxscore=0 cotscore=-2147483648 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2004280000 definitions=main-2005160045
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/atokuvh9UQYLmLVIWfkTK7OVaiY>
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: Sat, 16 May 2020 05:24:11 -0000

Folks,

RSID and CRSID both work for me. However,  I shouldn't  be allowed to name anything. I liked FIDO, too!

                                                                                         Ron




Juniper Business Use Only
From: Mark Smith <markzzzsmith@gmail.com>
Sent: Saturday, May 16, 2020 1:09 AM
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Ron Bonica <rbonica@juniper.net>et>; 6MAN <6man@ietf.org>
Subject: Re: Applicability, Use-cases, and Architecture for the CRH

[External Email. Be cautious of content]


On Sat, 16 May 2020, 14:46 Brian E Carpenter, <brian.e.carpenter@gmail.com<mailto:brian.e.carpenter@gmail.com>> wrote:
Ron,

Definitely, if it isn't the same, I would rename it. I like memorable acronyms, so could I suggest FIDO (Forwarding IDentity Object)?

The longer term used in RFC 8200 for these things is "route segments" (although another issue with RFC 8200 is that it doesn't specifically explicitly define what they are).

So in CRH I think they should be called "Route Segments", and identified with "Route Segment Identifiers" (RSIDs, pronounced "R-SIDs") or "Compact Route Segment Identifiers" (CRSIDs, pronounced "C-R-SIDs").

Regards,
Mark.


Regards,
Mark.



   Brian
On 16-May-20 15:45, Ron Bonica wrote:
> Brian,
>
>
> An SRH SID is semantically very different from a CRH SID. So, I would be happy to rename the CRH SID to something else. Maybe the CRH-FIB-ID?
>
> I would also be glad to recognize the contributions of draft-lc-6man-generalized-srh-00.
>
>                                                                                                                  Ron
>
>
>
> Juniper Business Use Only
>
> -----Original Message-----
> From: Brian E Carpenter <brian.e.carpenter@gmail.com<mailto:brian.e.carpenter@gmail.com>>
> Sent: Friday, May 15, 2020 9:41 PM
> To: Ron Bonica <rbonica@juniper.net<mailto:rbonica@juniper.net>>; 6man@ietf.org<mailto:6man@ietf.org>
> Subject: Re: Applicability, Use-cases, and Architecture for the CRH
>
> [External Email. Be cautious of content]
>
>
> Hi Ron,
>
> Looking at your draft plus this extra material, I still think that the concept of a SID is helicoptered in to some extent. It isn't obvious to me that a SID in CRH is semantically the same thing as a SID in the Spring WG. Either it is, in which case you should cite the relevant SID RFC, or it isn't, in which case there is some more writing to do.
>
> I think you could also give an ack to the C-SIDs in https://urldefense.com/v3/__https://tools.ietf.org/html/draft-lc-6man-generalized-srh-00__;!!NEt6yMaO-gk!WQLMM8SDvQVSEuBWhatHjEAZG7SR40xhu6n19XNDr1U4m9iTxWJQ17mZH9tRrUf-$<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-lc-6man-generalized-srh-00__;!!NEt6yMaO-gk!WQLMM8SDvQVSEuBWhatHjEAZG7SR40xhu6n19XNDr1U4m9iTxWJQ17mZH9tRrUf-$>
>
> Regards
>    Brian Carpenter
>
> On 16-May-20 12:41, Ron Bonica wrote:
>> Darren,
>>
>> In previous emails, you suggest that the CRH draft needs information regarding Applicability, Use-cases and Architecture. After the call for adoption, we could add the proposed text, below.
>>
>> Would this text address your concerns. If not, please provide specific recommendations.
>>
>>                                                                          Ron
>>
>>
>>
>> PROPOSED TEXT
>>
>> ----------------------
>>
>>
>>
>> 9.0 Applicability
>>
>>
>>
>> The CRH can be used within any network where:
>>
>>   * All nodes implement IPv6.
>>   * Edge node can filter inbound packets that contain the CRH.
>>   * Selected nodes can process the CRH. If a node is identified in a CRH, and it is not the packet's ultimate destination, it must be able to process the CRH.
>>   * All nodes can maintain a basic FIB that maps IPv6 prefixes to next-hops.
>>   * Selected nodes can maintain a CRH-FIB that maps SIDs to IPv6 addresses and forwarding methods. If a node is identified in a CRH, and it is not the packet's ultimate destination, it must be able to
>>   * CRH overhead is acceptable
>>
>> CRH-16  overhead is as follows:
>>
>>   * 2 SIDs can be stored in a 8-byte CRH
>>   * 6 SIDs can be stored in a 16-byte CRH
>>   * 10 SIDs can be stored in a 24-byte CRH
>>   * 14 SIDs can be stored in a 32-byte CRH
>>   * Etc.
>>
>> CRH-32  overhead is as follows:
>>
>>   * 1 SIDs can be stored in a 8-byte CRH
>>   * 3 SIDs can be stored in a 16-byte CRH
>>   * 5 SIDs can be stored in a 24-byte CRH
>>   * 7 SIDs can be stored in a 32-byte CRH
>>   * Etc.
>>
>>
>>
>> 10.0 Use-cases
>>
>>
>>
>> The CRH can be used to provide traffic steering in:
>>
>>
>>
>>   * Data centers
>>   * Service provider networks
>>   * Enterprise networks
>>
>> Each of these networks may have a preferred method for populating the basic FIB and the CRH-FIB. For example, a data center may use a controller to populate both FIBs while a service provider may use an IGP to populate both FIBs.
>>
>> The CRH can implemented on:
>>
>>   * ASIC-based routers
>>   * Software-based routers
>>       o Stand-alone
>>       o In a container on a server in a data center
>>
>>
>>
>>
>>
>> 11.0 Architecture
>>
>>
>>
>> CRH architecture determined entirely by RFC 8200. Specifically:
>>
>>
>>
>>   * IPv6 source nodes use the CRH to determine nodes that a packet visits on route to is ultimate destination.
>>   * The CRH does not subsume the function of any other IPv6 extension header. For example, the CRH cannot be used for authentication, or to deliver optional internet-layer information to the packet's ultimate destination node.
>>   * A packet that contains the CRH can also contain any valid combination of IPv6 extension headers. All extension header should function as per their specifications.
>>   * The CRH assumes that IPv6 Destination Address semantics are as defined in RFC 8200 and RFC 4291.
>>   * The CRH is processed identically on every node (See Section 5 of this document). Processing rules do not depend upon information encoded in the IPv6 Destination Address.
>>   *
>>
>> The CRH conforms to the letter and spirit of RFC 8200. For example:
>>
>>   * A packet cannot contain two instances of the CRH
>>   * A CRH cannot be added or deleted by any node along a packet's processing path
>>
>>
>>
>>
>>
>>
>> Juniper Business Use Only
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org<mailto:ipv6@ietf.org>
>> Administrative Requests: https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/ipv6__;!!NEt6yMaO-gk!WQLMM8SDvQVSEuBWhatHjEAZG7SR40xhu6n19XNDr1U4m9iTxWJQ17mZH-k2Yi-w$<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/ipv6__;!!NEt6yMaO-gk!WQLMM8SDvQVSEuBWhatHjEAZG7SR40xhu6n19XNDr1U4m9iTxWJQ17mZH-k2Yi-w$>
>> --------------------------------------------------------------------
>>

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org<mailto:ipv6@ietf.org>
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/ipv6__;!!NEt6yMaO-gk!WXCRJ4mKHyPNgylXL328rFqHfGcPdZ1-dIWT4SOhYotZaFVp3acki1gwvdyPC-vH$>
--------------------------------------------------------------------