IETF Logo Mail Archive

RE: [spring] How CRH support SFC/Segment Endpoint option?

James Guichard <james.n.guichard@futurewei.com> Fri, 22 May 2020 14:40 UTC

Return-Path: <james.n.guichard@futurewei.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 2A9793A0B02; Fri, 22 May 2020 07:40:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.09
X-Spam-Level:
X-Spam-Status: No, score=-2.09 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, RCVD_IN_MSPIKE_H2=-0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 XTrQkzibk_n1; Fri, 22 May 2020 07:40:14 -0700 (PDT)
Received: from NAM12-MW2-obe.outbound.protection.outlook.com (mail-mw2nam12on2132.outbound.protection.outlook.com [40.107.244.132]) (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 7BF0A3A0B5B; Fri, 22 May 2020 07:40:14 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=lDglNxomdBzPhrUJySLdJyBECV+cmDBlWSYDT7uAfnLY3HkBu7um74fnyJqCKxD8blyDMyBMvevLzfOhYzclRCF8RCXOFW/+SP6tGRyxJSZ2c4bNGnhTYsJ1SxY2NHowU1NC4d40xedLKXEQXt8N13buot7kNsiC4/3Ypv399TtNaD7NxUK3rY6Rs2nU3vo2CPOp81qe2EcVDiT+kebTfO+aTeO2nuI/Ct/7vN8vpBvM/iTayyq2j/fmiq298xnybMVqsOIhYNUxugpwwWXIR+GNBRj9aXIMI+7z+DYPO5WGjr4/AyxBJzl/ngzlU+k4KLfhWU7VUfz8E8+tzPjhhg==
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=56ZE2JetkUR9j9Kzf0P27H+c+0X9+tDQh+uB7IGy48U=; b=BT2hMGr9KCqPCi1eNNQNS/IYBVf3wWYBxf7b7KP9d3ro6q8+MRNnCe8f1NQxaWWtCQ2RReMjDgsMpw5Z8nN0amZTfFtL813c7hAljA8JhC7zWzcggje1JyfZIbb5RyVeqDVN6hY+0u5iH1GziZ7S5MqOLr/QtOeMAqBEpEXvHndRBA+sviyOqb+w0WhkUwqCzdUozdgSuDF+T6Nj6uRc0ehLf0OGEKXeDLSD2DMMswRT8QU/OQrWdZ/AS+cVh/JxOvOZSDhaNxNCwEDCivZrRd095TDFzJMXEGiibNdxc1Hmk5oLGSri1L6aKPh0d32w1OS4/fGqEcjpZkoc6vyElg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=56ZE2JetkUR9j9Kzf0P27H+c+0X9+tDQh+uB7IGy48U=; b=KToh795GYyuEoAZ/PbzbgdEeqfuzo4PoBZTRJjUE03DEYtdx77ncDUX3CbdY8AuSXoH/Npy8H/2xMR7IihKPMI+ynTphmayPZaSFSLoAq9/Yrrxvw7sFeUHi9Y7ihItRIZOE1EVutiFT1spqtepn5s7xw4dpNvyTQTPNvBCjrSw=
Received: from DM6PR13MB3066.namprd13.prod.outlook.com (2603:10b6:5:19d::18) by DM6PR13MB3788.namprd13.prod.outlook.com (2603:10b6:5:242::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3045.8; Fri, 22 May 2020 14:40:13 +0000
Received: from DM6PR13MB3066.namprd13.prod.outlook.com ([fe80::a024:eb2c:7574:b7b7]) by DM6PR13MB3066.namprd13.prod.outlook.com ([fe80::a024:eb2c:7574:b7b7%7]) with mapi id 15.20.3045.009; Fri, 22 May 2020 14:40:13 +0000
From: James Guichard <james.n.guichard@futurewei.com>
To: Sander Steffann <sander@steffann.nl>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
CC: 6man <6man@ietf.org>, "spring@ietf.org" <spring@ietf.org>, "Chengli (Cheng Li)" <c.l@huawei.com>
Subject: RE: [spring] How CRH support SFC/Segment Endpoint option?
Thread-Topic: [spring] How CRH support SFC/Segment Endpoint option?
Thread-Index: AdYwBYkgTau2vInrR6WP+x+iqlpN9gAPJDmwAACfDIAAAGnhkA==
Date: Fri, 22 May 2020 14:40:13 +0000
Message-ID: <DM6PR13MB3066CA70918022A394DB4BE8D2B40@DM6PR13MB3066.namprd13.prod.outlook.com>
References: <C7C2E1C43D652C4E9E49FE7517C236CB02A2CD12@dggeml529-mbx.china.huawei.com> <DM6PR05MB63482CFA4D5AB938D5A4B818AEB40@DM6PR05MB6348.namprd05.prod.outlook.com> <AAC1BB04-59E9-4DAC-8B8E-3F12168C5C16@steffann.nl>
In-Reply-To: <AAC1BB04-59E9-4DAC-8B8E-3F12168C5C16@steffann.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: steffann.nl; dkim=none (message not signed) header.d=none;steffann.nl; dmarc=none action=none header.from=futurewei.com;
x-originating-ip: [47.14.47.233]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b01200ea-9fa0-466b-faff-08d7fe5e0956
x-ms-traffictypediagnostic: DM6PR13MB3788:
x-microsoft-antispam-prvs: <DM6PR13MB3788D19230D225F6B9D8CD86D2B40@DM6PR13MB3788.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6790;
x-forefront-prvs: 04111BAC64
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: atmFGU98xMMLQtPH4SXKpmFwbc46jq5Y+UROb9NWu2MgD3pqMig68NsUBCvY09LgHp6pZX8neOD+nk0QzR3KW9aoai4xCukNELWjZlqM30fs5l20p5+wbrzXAt/2xw3A+RLP3IFpJhqwTdhYM0XTuy/oKA4kaiBycIFdA8rmzauKjhdpmC/qkc2bb3qdktbgLPvyKi5Bes4rAfieQGl9pI45RDUVfU+66UcpDm+VMUnYmASZg5xW74J24tsL3HJt+zoFmmVSPMqTrIP7hfU1b3FIBOloDYJHx7lTg+U4yG7AR4E1AI7j+9s7lmDxDbZoEUuiAmP0hBTdu3sUsMl8UE5Nd9VjKddVRzYj5OHWw4YQwWwYnKHOZZqpEtEea1zseafF1+gDHc/evUOTLEhyZg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM6PR13MB3066.namprd13.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(346002)(396003)(376002)(366004)(39840400004)(136003)(9686003)(966005)(55016002)(66946007)(76116006)(64756008)(186003)(8936002)(66556008)(8676002)(66446008)(478600001)(66476007)(2906002)(71200400001)(5660300002)(53546011)(316002)(6506007)(52536014)(110136005)(33656002)(4326008)(26005)(86362001)(54906003)(7696005); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: GS1fKkUqlt+pvdkjipFvjZe4OGmQ/ShgT1QJUJStQjh6qY24esDiKT3LFzYOVkdAdMl1PPhvYSKI8jLHHnFz9hTMKgKw1gBrMoFAMGyi7gsLjrlR0mszVSUAB1GwKs0ejHB8ekdr9BC3LfuHqRN+QK5t+L5dSCpITzdmBqpY+u7uvNrw+2ERKHIc+hzvR48QMA6pXnLRvcOcTqup60wIKsAYUI8fmhM096rLsKFcMIW1stP9z/PK1Y0Bc7yIBe1+ZfITokBZ33EpEoKWeintXf4RyTz88lyLAQ+jgZh9JL0ivTRd61VHy+YlIAOl8KXG0rflo+hejuTO/zlhxH47g3TxJ+MWTq2qxOxN6chPP0XOjLhlY52a2PP7bb6zeyRFI/ys3UxOWU8SgJoCHABLTNCxZRW9uHBK3bAX3SYgSdm4vA1940yofj2EhV+lQQkhiW+JI7567dYXu4sX5TskZcDvqDl7Q0uQa7bKX9Sm4C0=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b01200ea-9fa0-466b-faff-08d7fe5e0956
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 May 2020 14:40:13.2481 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: yUtvvB3l1pixqGUyWUezJwVrX6GWl1u0UaaVvLrDEZITFCW/BQ9zSD4jJsdwg2Jsizw8D6O4y4A0dcVjNOd+0A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR13MB3788
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ZA9m-QKy7TblyELh2mWocEXmnJs>
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: Fri, 22 May 2020 14:40:16 -0000

Hi Sander,

This separation of architecture is not new; see https://datatracker.ietf.org/doc/draft-ietf-spring-nsh-sr/ in the SPRING WG.

Jim

-----Original Message-----
From: spring <spring-bounces@ietf.org> On Behalf Of Sander Steffann
Sent: Friday, May 22, 2020 10:24 AM
To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
Cc: 6man <6man@ietf.org>; spring@ietf.org; Chengli (Cheng Li) <c.l@huawei.com>
Subject: Re: [spring] How CRH support SFC/Segment Endpoint option?

Hi,

> The sole purpose of a Routing header is to steer a packet along a specified path to its destination. It shouldn’t attempt to do any more than that.
> 
> The CRH does not attempt to deliver service function information to service function instances. However, it is compatible with:
> 
> 	• The Network Service Header (NSH)
> 	• The Destination Options header that precedes the Routing header
> 
> Both of these can be used to deliver service function information to service function instances.

Clear separation of concerns in a SPRING architecture! I was afraid the hope for a clear architecture was lost, but this makes me so happy :)

Cheers,
Sander

And to be 100% clear: I'm not being sarcastic… The messy "architectures" I have seen in the past have driven me to despair. This work is finally something that makes sense.

v2.23.0 | Report a Bug | By Email