IETF Logo Mail Archive

Re: [spring] CRH is not needed - Re: How CRH support SFC/Segment Endpoint option?

"Henderickx, Wim (Nokia - BE/Antwerp)" <wim.henderickx@nokia.com> Tue, 26 May 2020 14:50 UTC

Return-Path: <wim.henderickx@nokia.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C1353A0C40; Tue, 26 May 2020 07:50:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.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 TzghNzFhmw2s; Tue, 26 May 2020 07:50:40 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70095.outbound.protection.outlook.com [40.107.7.95]) (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 1E7273A0C25; Tue, 26 May 2020 07:50:39 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=GfcH7UXC1lLFeTZYW8DrmNb0zzyf48mSfOJye59QcMovVRPl7bTYSgSgccbqE5+EL0s242PI1ObSXvca0Ho6BQkphRCAv5e+qxPMLeTjJ3IjKT9NONx65mRQbhShmttbYSfcmDfAM6pDhX5d7vTYjQXwlz82q5kbR1vtR7hEAJZeEXLpauHvCG+dIONWH8eKSroFGGUXoDWdciZ4gXhCnrEW/1YmsH4cJ1sBFxGnoCi2/dCu81NDwK3UOsZrUj3VdfVWmcBySkVN5tZgy1XIh14RlyWnZK12/V+0MkkovZD/kpD4UdNT2qaC1E3TS5smzt2p6sclCDAiLC9LXcPdyA==
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=f3j2tPOTb/hYgxHs7EKFWOK4JkWLZxhmEVB6V6cP32c=; b=Gxu9g0Uh5cq24mt26RBCqqs9wM72S+nkYfpuEVwfBHAGW+kNAUhtUKtnqnU3qRUyF03tdSDExLRYlUJlQbsFl/53bRER4S2soi1pI5x9/gNgBA4mjchtM1YYHY6cbk4km9GLNblKr0UtfNXLZk4QsBn6y6kFnliZgUY54/rgnKvbuCDjLCogf8JfN+2lJE6qETh/FCAxXRgkWWB8RiUxXNH/Kqwc/BBA4zpjWQR9gLzQDqIFmqk+Z7aP0dWIi14MTayyyhDzdS3QfGHqy9E876mMhQKI6WcLJ8jZxR1dzIRbqJYmsC/tq09N0Qx296zNcfy1Us5wroot9U6EvN4smg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nokia.com; dmarc=pass action=none header.from=nokia.com; dkim=pass header.d=nokia.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=f3j2tPOTb/hYgxHs7EKFWOK4JkWLZxhmEVB6V6cP32c=; b=Zv+CBR8C+g9EEtDY/VI1F9yyWYCnVWKGssixLkfgHMkAa0SFdXaiYRncm4sN2u30qADs2RVR/oPdmmkuQ7IR0YX72H2PyP5WG2EJn0+aSJZKmuKbVGh8bBFujf8kM+QoJ+WsuPqNiTqOBDc5/cC8wDN+0rxxpHRhcWJIofIBSts=
Received: from AM0PR07MB4497.eurprd07.prod.outlook.com (2603:10a6:208:7a::20) by AM0PR07MB4114.eurprd07.prod.outlook.com (2603:10a6:208:45::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3045.8; Tue, 26 May 2020 14:50:37 +0000
Received: from AM0PR07MB4497.eurprd07.prod.outlook.com ([fe80::75d9:62a8:8868:5119]) by AM0PR07MB4497.eurprd07.prod.outlook.com ([fe80::75d9:62a8:8868:5119%7]) with mapi id 15.20.3045.013; Tue, 26 May 2020 14:50:37 +0000
From: "Henderickx, Wim (Nokia - BE/Antwerp)" <wim.henderickx@nokia.com>
To: Sander Steffann <sander@steffann.nl>
CC: Mach Chen <mach.chen@huawei.com>, "Zafar Ali (zali)" <zali=40cisco.com@dmarc.ietf.org>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, "Chengli (Cheng Li)" <c.l@huawei.com>, 6man <6man@ietf.org>, "spring@ietf.org" <spring@ietf.org>
Thread-Topic: [spring] CRH is not needed - Re: How CRH support SFC/Segment Endpoint option?
Thread-Index: AQHWM2iKHTGjzhu8xUiU5Ns4LfPFf6i6baWAgAAkhgD//9++gIAAItQA
Date: Tue, 26 May 2020 14:50:36 +0000
Message-ID: <4D115A10-E841-4571-937E-DD04EB08AF0C@nokia.com>
References: <D46E924A-9D84-4616-BE51-7FBB7FBADAFA@nokia.com> <DA99566C-9914-42DF-B15D-6964D5044EB7@steffann.nl>
In-Reply-To: <DA99566C-9914-42DF-B15D-6964D5044EB7@steffann.nl>
Accept-Language: nl-BE, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.37.20051002
authentication-results: steffann.nl; dkim=none (message not signed) header.d=none;steffann.nl; dmarc=none action=none header.from=nokia.com;
x-originating-ip: [2a02:1810:350a:9600:b47b:804:a201:478d]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: b006e061-9f51-4621-0269-08d8018426c7
x-ms-traffictypediagnostic: AM0PR07MB4114:
x-microsoft-antispam-prvs: <AM0PR07MB41149F7531B03FD952DB59A883B00@AM0PR07MB4114.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 041517DFAB
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: wdcOgLd5jDEDdi2GjVCs5C5twnYQ43ai8XS4ICnZL3lgmVRtF5psUzfBPPfrfEq9Y/N1b+rJvt1aAapmKl6D1CpgJ0zaTpJ0G4U8eL7hB/hbncC0g+U0JVfyuh4hvEb6CZ8nyGnERN7Rw/tFehsSjuWe8ltbwrNRQwTCwLm45Gep0P7BowYhjQEvJaiArV1YDqtcGMjZYXR3Viad8cyPb8Zls5TNjSupOse7eBm8x8JZs2jbzUEkhRqr4pgvHMB4kdGv7gDWlL/g5bVF5Ia6iVjrb7OT8D2+X0Le+8b80IYmmRrAalh5WM7V8op+Xd69GqxsJ13uDq6wjNED3dv/gA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR07MB4497.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(366004)(6486002)(2616005)(186003)(86362001)(33656002)(8676002)(8936002)(5660300002)(2906002)(36756003)(6506007)(76116006)(66946007)(54906003)(6916009)(64756008)(66556008)(66446008)(4326008)(498600001)(6512007)(71200400001)(4744005)(66476007)(66574014); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: 8UkrZsQgrTSs024f6LhQEQK1WLQ6gF/rVfGiCgfV+2K2Q6vHtdlkajm1+NjBf+o9gEgIz7r/MfDhHBO3nMOKhcPTKU30z8je93KQsz0v48sMzI+gUAcHVbOwQLTfegBi2rd211v3weR/WjbXX4gHXxuTaCU0sedHZjrs3jjAKfn6iCY0lnOjKvcL7XwTigfmlQYK0dAG0pcABLdYaBiOIlsCrpcruTkw6tk4CZ19wptdurqrqKD7ftxrIgoXLGzF/P+jhodPcj6YISrgix6Vgzmeff6WxWrFltOiaSx61H/TY2H3YG1iMu++C2fHqIgFOqDFNZRpE6a89nQlLq5xOBleJjkA+F5GRIEZFPpsVbi8q6dg3+EN9xj89ClpysxdMll3W63iHnMlBfPJHFhrn7GJRlE1OFuiVGcrRVNV56wk54UtswEx6BaK/oPX6MrZ5DQrTw5Jb67IlZQtgXFHlHgoiKIFBaeHm0p4jB5PUGKBKyViIjNzfeEDelGw+MNfgfzUuHvB3wrGv27uiKheAwcvV7sQHoTWzx+4d7kvJAyBHxOrmf0djdIHIFuZ0JtH
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <42698B6DFF123E419F67AB3E6590E0F8@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b006e061-9f51-4621-0269-08d8018426c7
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 May 2020 14:50:37.0112 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: l0+RkjrxJ1CGyiMfOWWTeBOpI2CqhfeY6hmVltBhJnYN2KhFv6KClBmmFK4olqRPrmD3O8yzPfj4mdhpGlVD53SLcny/00sdXe1dtxnUXHM=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB4114
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/HW1BskueNvinJ9RvERRLqM2tLA4>
Subject: Re: [spring] CRH is not needed - Re: How CRH support SFC/Segment Endpoint option?
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 May 2020 14:50:43 -0000


On 26/05/2020, 16:46, "Sander Steffann" <sander@steffann.nl> wrote:

    Hi Wim,

    > It does work across domains that are not directly connected, but that scenario is not well described I have to admit. The operation is as I said very similar to CRH. 
    > Think of the MPLS tag as the same as the SID tag in CRH. From a data-plane all packets on the wire will use v6 addresses, so inter-domain is possible.
    > 
    > This is no longer MPLS as people know it. Think of it as a tag that performs a steering function as you have in mind with CRH.

    How would I get the MPLS tags over the IPv6 internet? All I can imagine is another layer of point to point tunneling...

WH> in the same way as you get CRH across the Internet. It is a tag encapsulated in an IPV6 header. It uses ipv6 encap based on RFC4023.

    Cheers,
    Sander

v2.23.0 | Report a Bug | By Email