IETF Logo Mail Archive

RE: How CRH support SFC/Segment Endpoint option?

Ron Bonica <rbonica@juniper.net> Fri, 22 May 2020 17:33 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 EB5F43A0C7E; Fri, 22 May 2020 10:33:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net header.b=aej21k3w; dkim=pass (1024-bit key) header.d=juniper.net header.b=C0RoqGyr
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 ibRyjr8Am-eC; Fri, 22 May 2020 10:33: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 E28FE3A0C73; Fri, 22 May 2020 10:33:08 -0700 (PDT)
Received: from pps.filterd (m0108162.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 04MHSmvd014269; Fri, 22 May 2020 10:32:37 -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=WJy5k3BujY2SK55KNG0iJEw36EoT/oI1pP3jVrz0hkI=; b=aej21k3wolVxWNl1k18gyRGBk+C3v2UidjPPUaF7Hme6fXu4WRed1++ZedUxsf6XvUqY +lc9tXyZ6iYO/FVfxztnn90vo5+tmpNCXJ2ZD8Qk7LQiNge5N1GQCtPSkqRr5n5Oo5G6 fe1lG73ZoPp0M51hjXKnhvmUxoZ4igyArSlm9mGf294uO9uI6OuHBM/kwD9f7OG9YJtC HWE8PfnIGWwdVEHblj0O05ddfA5AmtZQJ9Vp+j7iGOaz0jEMgeq1xjzMxRxOe4NdG5F2 g8pgLBLc/viLRown4HSsnS7qInROmp6E0udjSX64H4seJWJ5xteuJxcfiBm83jcxshAp Cw==
Received: from nam02-cy1-obe.outbound.protection.outlook.com (mail-cys01nam02lp2051.outbound.protection.outlook.com [104.47.37.51]) by mx0b-00273201.pphosted.com with ESMTP id 315jq33kqn-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 22 May 2020 10:32:37 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=TAZ0LTNSXe0//hWtf1+MltprPNPqAzkSk73wao9tXlOeU54dxzrFHRXjv23lE8yZ7mnfG54ExA419IOyHuEVnuCTbA9Dq/c4t+CaCJvuNL8wBasmbJ27x32HgrXwIYvPyBPoTjqXkrJE0J0eyLN/UfsX40PndmiOa2azRNPoAKYlKQyE4Ir6xU3SmRjs/64ejVut2PcFem5v38sry7C6jRn/skaoqfX/RKX3PYJh77/hY28RF8wa+/qGmDwBmIDsx6Vcj7vT93fsUZdWqLl47hZYZVFTAJi+k76NsuZ7WrTbF/4uccIzhQYpBtsMdjb1mBWgkuES+4Xrj64wRKqfjg==
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=WJy5k3BujY2SK55KNG0iJEw36EoT/oI1pP3jVrz0hkI=; b=cNiV35I6lWJ4akdILkEboqXzOYBAiHE9Sv18j5Y3hHfdYKOoSjNuXk1/vDWmGGD+1UQRbLl4EwzrjDRNWD9LAdjnxaJctRbYeoPNcYooAPMTphD/9itH9FF3OvB+TjqdYl9qT2C/+Q9+OlkC2+f5qsAHKUtfOHTrgUq5kxauUOXyGdDx/JSgnm0sv6w88RGd33/47fA1egWxPqWqqeZti2bNwHM7YH3m9Uhx9e2rYbh+hySyLgUZdHWIPvq10ZUL10+S1TZ89+qGEpNbFJntiEyyr5pzvP0pil7Ur17V3UHgLjlMCxVg+zDAaHd7X7cinZxGoHbfPXCzs+Qi6U/O0Q==
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=WJy5k3BujY2SK55KNG0iJEw36EoT/oI1pP3jVrz0hkI=; b=C0RoqGyrRTaszUJTlwEfZLjf1fHVCo8BWFodSq0kmeSdiTfAcGArTmPCktFQ2DrIQ4UQkUVnnAsQeRYUftNb58MxwtQ4j4KruEabDUQLO5M5pm1AJoEkNu7WFIKusE2BegoLo1N33udO0e3xlHBGgXZRSAefphxIgmqJPcHhR0w=
Received: from DM6PR05MB6348.namprd05.prod.outlook.com (2603:10b6:5:122::15) by DM6PR05MB4588.namprd05.prod.outlook.com (2603:10b6:5:95::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3021.11; Fri, 22 May 2020 17:32:34 +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.019; Fri, 22 May 2020 17:32:34 +0000
From: Ron Bonica <rbonica@juniper.net>
To: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>, 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>
CC: "spring@ietf.org" <spring@ietf.org>
Subject: RE: How CRH support SFC/Segment Endpoint option?
Thread-Topic: How CRH support SFC/Segment Endpoint option?
Thread-Index: AdYwBYkgTau2vInrR6WP+x+iqlpN9gAPJDmwAAHblAAABUB4EA==
Date: Fri, 22 May 2020 17:32:33 +0000
Message-ID: <DM6PR05MB634831316D36836A262161A4AEB40@DM6PR05MB6348.namprd05.prod.outlook.com>
References: <C7C2E1C43D652C4E9E49FE7517C236CB02A2CD12@dggeml529-mbx.china.huawei.com> <DM6PR05MB63482CFA4D5AB938D5A4B818AEB40@DM6PR05MB6348.namprd05.prod.outlook.com> <4278D47A901B3041A737953BAA078ADE18F3D928@DGGEML532-MBX.china.huawei.com>
In-Reply-To: <4278D47A901B3041A737953BAA078ADE18F3D928@DGGEML532-MBX.china.huawei.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-22T17:32:31Z; 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=5eebd013-b3d2-47bb-872a-e879d7f56358; 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: huawei.com; dkim=none (message not signed) header.d=none;huawei.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: a95ed02b-9208-473c-f307-08d7fe761ce5
x-ms-traffictypediagnostic: DM6PR05MB4588:
x-microsoft-antispam-prvs: <DM6PR05MB458898554C67A57039E44C1FAEB40@DM6PR05MB4588.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-forefront-prvs: 04111BAC64
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: L0BDcghqd6YVXKFYyiMmPWfwW10u+TSM+kjWJA5sYAD9LkXwvNzb7bn6Cixut5+xbzHTcVMe2nXO+TqoEDSVuWy+nFTA2YC3wyOWkcVv16gcHTCZSyu52qH75rfO0sf1pE9ZiiTkoaSuycoSrDhTj3ubph9ox98CBUKF09TJGFTDTzhq0pBR99KzXusQKFRhj5S9BQrsEg3Qf4WaPiwhqbFpRv34lFSZZhL83qgUnWZM+FYxd9DtNwH9tDaWnYJ/3fID+Fu+7Fo+H/KPxBR42j9BBokZOayd2HFLg4TIr9fcB/Bg0jQ2X+F3L+8/yJF3pslgbK7B7s3jasWsm4IcrdFk0SRBJ5ZxfYbiT44gm1cj4dJzJ+7b6QIRq62/KTO6/yc+5gWtA0o3PTDzb9AAWg==
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)(396003)(376002)(39860400002)(136003)(366004)(346002)(86362001)(110136005)(66476007)(33656002)(5660300002)(66946007)(64756008)(66556008)(76116006)(8676002)(66446008)(4326008)(8936002)(53546011)(55016002)(6506007)(52536014)(7696005)(316002)(166002)(478600001)(2906002)(186003)(26005)(71200400001)(966005)(9686003); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: Ub0whHuG6uCzbdhwTwRxQ+i9LHNv9INYweoPoyhuB/CcSSN34nQ/GAYYB7eDQl73NRHy08n6jc0oQdbyiqtm/f1IlahWJ5Ia0IoBs4MLSOyGgUqv1wh/abFihawNlRfESB4iyX1L2bhN4OY4/25Sfejtwb91XTrVIze8SKTkNLqx6FXNWYAyvgSx6134KjfXzmpvUsDzi9+HApIa/3TWk1SorJWzz6b0A6aDdMld8DFwZUWq1tB36Hlz3kEG8cgMjT2Q5XPk5m4iipCywnvhQAQMFMOEbZleUTYMeWeIGDII3/dDU3YjmnTWfC8Vtd8T77vfFo3YIABqYVI9oktD3isDFOvnIG8nfSmfztBzwOvQtxhFjwt0LWMH99u9JYIbXRmFH9zQrXR8e/pBd9Y0LdmySCfMKTVbDHwrsrtIHPunLHHR9ZkD4jnzf76GosIV+NNu1CybG4C48WCNdG+AA1jo1wyTSJ96tD7LvBFg60X/p7VBRjST4xZftyTMLr7k
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DM6PR05MB634831316D36836A262161A4AEB40DM6PR05MB6348namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: a95ed02b-9208-473c-f307-08d7fe761ce5
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 May 2020 17:32:33.9733 (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: 9tkbwsofOtSuTdUZlAaLDTmwYZX0I1S942haYn4Q2vDOxtXJX23s0yd8RN78F9I8xDeGky7ailFIZTf1TiWGCg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR05MB4588
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.216, 18.0.676 definitions=2020-05-22_06:2020-05-22, 2020-05-22 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 clxscore=1011 impostorscore=0 cotscore=-2147483648 phishscore=0 bulkscore=0 adultscore=0 malwarescore=0 priorityscore=1501 spamscore=0 mlxlogscore=999 suspectscore=0 mlxscore=0 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2004280000 definitions=main-2005220140
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/iVoqThzvgPzvMJ3tSDOlskA6Ayo>
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 17:33:11 -0000

Shuping,

The CRH can appear in a packet along with any valid combination of extension headers.

                                                             Ron





Juniper Business Use Only
From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Pengshuping (Peng Shuping)
Sent: Friday, May 22, 2020 11:12 AM
To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>; Chengli (Cheng Li) <c.l@huawei.com>; 6man <6man@ietf.org>; spring@ietf.org
Cc: spring@ietf.org
Subject: RE: How CRH support SFC/Segment Endpoint option?

[External Email. Be cautious of content]

Hi Ron,

If using DOH, then we would have DOH (VPN) + DOH (SFC) + RH per packet in some circumstances, right? What if more (ever-emerging) services are required? Not sure about the forwarding efficiency.

Best regards,
Shuping


From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Ron Bonica
Sent: Friday, May 22, 2020 10:17 PM
To: Chengli (Cheng Li) <c.l@huawei.com<mailto:c.l@huawei.com>>; 6man <6man@ietf.org<mailto:6man@ietf.org>>; spring@ietf.org<mailto:spring@ietf.org>
Cc: spring@ietf.org<mailto:spring@ietf.org>
Subject: RE: How CRH support SFC/Segment Endpoint option?

Cheng,

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.

                                                                                                                     Ron




Juniper Business Use Only
From: Chengli (Cheng Li) <c.l@huawei.com<mailto:c.l@huawei.com>>
Sent: Friday, May 22, 2020 2:56 AM
To: 6man <6man@ietf.org<mailto:6man@ietf.org>>; spring@ietf.org<mailto:spring@ietf.org>; Ron Bonica <rbonica@juniper.net<mailto:rbonica@juniper.net>>
Cc: spring@ietf.org<mailto:spring@ietf.org>
Subject: How CRH support SFC/Segment Endpoint option?

[External Email. Be cautious of content]

Hi Ron,

When reading the CRH draft, I have a question about how CRH support SFC?

For example, we have a SID List [S1, S2, S3, S4, S5], and S3 is a SFC related SID, how to indicate that? By PSSI? [1]

But how to know which segment endpoint node/egress node should process this PSSI? At the beginning of the SRm6 design, this is described in [2]. But you deleted the containers [2].

Without that, I don't really understand how SFC can be supported.


Best,
Cheng



[1]. https://tools.ietf.org/html/draft-bonica-spring-sr-mapped-six-01#section-4.1<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-bonica-spring-sr-mapped-six-01*section-4.1__;Iw!!NEt6yMaO-gk!UD4vf0darQ9cskFhH1fJ9jwZJ-nIciQxgVnf1219YuyyaNcgvNdRUdkjwP15i-Xa$>
[2]. https://tools.ietf.org/rfcdiff?url2=draft-bonica-6man-seg-end-opt-04.txt<https://urldefense.com/v3/__https:/tools.ietf.org/rfcdiff?url2=draft-bonica-6man-seg-end-opt-04.txt__;!!NEt6yMaO-gk!UD4vf0darQ9cskFhH1fJ9jwZJ-nIciQxgVnf1219YuyyaNcgvNdRUdkjwNmXwyHT$>.

v2.23.0 | Report a Bug | By Email