IETF Logo Mail Archive

Re: [bess] Comment on draft-ietf-bess-service-chaining-06

Stuart Mackie <wsmackie@juniper.net> Wed, 19 December 2018 22:59 UTC

Return-Path: <wsmackie@juniper.net>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8190130E7F; Wed, 19 Dec 2018 14:59:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.765
X-Spam-Level:
X-Spam-Status: No, score=-2.765 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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
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 SRBijpQiciH4; Wed, 19 Dec 2018 14:59:18 -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 4C29B130EAE; Wed, 19 Dec 2018 14:59:18 -0800 (PST)
Received: from pps.filterd (m0108162.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id wBJMxFt9010759; Wed, 19 Dec 2018 14:59:15 -0800
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=pY2XiCIV4dixgceahV4o9DHeh26G4jYlAoWcIkZ4qto=; b=rsysnl+nSjxU4iQwdk5ox7vyYYtyJlSN8D1bbEtu9TF8lpMrmKmEdSImj6+8EWJlSqTi 3QGxbYJpRPqkIyRNehWmv1LtGRWXQB2mZ4mGLuwW5VwcBA8bTxRnA0rMeSL4g0+3uIe9 YrBMjil18MwXTeCFY4Lnl54fWY4nXC7w912VHDLwR14qH7QqI+Pwscd/u7xOYp27ux3x YarE4VAY0BEUEspOt4lOVfHFg+s+MaWUTew+KSiW4aSV0nyH0JeaAMVFKRnRaYEgVM+V +worZDNT2cBvUUpwNYaUh+RkYWiN2vIdI1FxvfC8Vh90XZwJebnxWf3rTaMS3Dw0lNJ3 Ng==
Received: from nam03-dm3-obe.outbound.protection.outlook.com (mail-dm3nam03lp2059.outbound.protection.outlook.com [104.47.41.59]) by mx0b-00273201.pphosted.com with ESMTP id 2pfwv003sr-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 19 Dec 2018 14:59:15 -0800
Received: from BYAPR05MB4966.namprd05.prod.outlook.com (20.177.229.12) by BYAPR05MB5158.namprd05.prod.outlook.com (20.177.231.28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1446.15; Wed, 19 Dec 2018 22:59:13 +0000
Received: from BYAPR05MB4966.namprd05.prod.outlook.com ([fe80::a07a:c937:fdba:2c9]) by BYAPR05MB4966.namprd05.prod.outlook.com ([fe80::a07a:c937:fdba:2c9%2]) with mapi id 15.20.1446.015; Wed, 19 Dec 2018 22:59:13 +0000
From: Stuart Mackie <wsmackie@juniper.net>
To: "Andrew G. Malis" <agmalis@gmail.com>, "bess@ietf.org" <bess@ietf.org>, "draft-ietf-bess-service-chaining@ietf.org" <draft-ietf-bess-service-chaining@ietf.org>
CC: "draft-ietf-mpls-sfc-encapsulation@ietf.org" <draft-ietf-mpls-sfc-encapsulation@ietf.org>
Thread-Topic: Comment on draft-ietf-bess-service-chaining-06
Thread-Index: AQHUjB4pU67JfBbVJ02yRgKZMo9ql6WGcNqA
Date: Wed, 19 Dec 2018 22:59:12 +0000
Message-ID: <81380B9D-9064-4EF1-A83E-E300E5B8D810@juniper.net>
References: <CAA=duU3_GmkVyHkoRMLvw6kEFaRF2Cd=P+2-q0H5afMUfF3LgA@mail.gmail.com>
In-Reply-To: <CAA=duU3_GmkVyHkoRMLvw6kEFaRF2Cd=P+2-q0H5afMUfF3LgA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.5.181209
x-originating-ip: [108.14.61.67]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR05MB5158; 6:yy2HuRgXNYhvOjmHC6z+gL4xHZJ031l1I/RqlOa7QkVdvtSjUTQlkFQw8AM8BqARib8oSyt4XJBBV6+/awofrJmCfUa8GZlNI9k7Iie4mdwDEiNd2E7OcEuuPzv83rrvH2QKeiciAeZBFIM/4iG+KMpzmvprin7vSUdbuM1FPHilJdy2bA3GbeWqEWABgkgDIbS52rtAHdI+W//wMoZa9/uCZwbDXWqx7C+7QhC2dvxT2BdoqDOU9nGrR8XPJcd3LAY9AsNNE+yGx9zGKItnnpCpaWv2xu1yd6tOfOkxiWC2VEwm6UTWJRwVTH0PYqTw/UR3bLz53C0WzSyoIAaGRAyyW73z5oSSOwCFVQe/oi4qtcds5Gx2h618RYm8wUWwVf11nDvPMPsIH4IQAWL48HqzIYaiq/Tz2UNDfv5oYvympagl24iyj5Ft46OxLBPHH/3rIecQtgL8pSZDn8uGvA==; 5:OhBuQfYMebKJezpBP+0Cvv5D06kc38bzm66dVom9m9SkfOAs9pfIEoFjODNDhp/p8LY2V5wXiduw2tM2g1xsx5cKJHiZy18Fk0dfXBpZu7Vxtpn7Glw/hEws3+FFa15kMUd7GTyXkQPYmB2Wh4WERyWz/bSbgn9q3qo3Ql4n7pY=; 7:TIZebpnq0PuJNKqc/9w8uaDFmSI9xQQTxH8xaz4r0SOR9SPwUgNbcptzvfl7R8I7qJygo4QazdLvtV4yvn/fYAQH+cTq6trFrHpt3VTiWkTRUW5bXCWQQj8HdP8BqIxDH6l2GbiZN7P2hcIMh3Ed+Q==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: f78cccec-adf0-4d08-f7bb-08d666059802
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:BYAPR05MB5158;
x-ms-traffictypediagnostic: BYAPR05MB5158:
x-microsoft-antispam-prvs: <BYAPR05MB5158D8D998C600E439911270D8BE0@BYAPR05MB5158.namprd05.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(3230021)(999002)(6040522)(2401047)(8121501046)(5005006)(3231475)(944501520)(52105112)(10201501046)(3002001)(93006095)(93001095)(6055026)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123560045)(20161123558120)(20161123562045)(201708071742011)(7699051)(76991095); SRVR:BYAPR05MB5158; BCL:0; PCL:0; RULEID:; SRVR:BYAPR05MB5158;
x-forefront-prvs: 0891BC3F3D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(396003)(346002)(366004)(136003)(376002)(199004)(189003)(2906002)(6486002)(8936002)(14454004)(6436002)(5660300001)(71200400001)(229853002)(83716004)(7736002)(82746002)(3846002)(6116002)(71190400001)(33656002)(106356001)(6246003)(105586002)(25786009)(6512007)(6306002)(54896002)(53936002)(478600001)(68736007)(4326008)(39060400002)(316002)(110136005)(11346002)(446003)(99286004)(186003)(26005)(86362001)(2616005)(9326002)(2501003)(102836004)(2201001)(486006)(66066001)(58126008)(97736004)(81156014)(8676002)(36756003)(76176011)(256004)(53546011)(6506007)(81166006)(476003); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB5158; H:BYAPR05MB4966.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: OF4nMWCJaaHxcR7uzj4s9k+XX1H/cO8sLYUlgZwBUuP8+Tk0Ze2UcUO10hptDlxFnoeX7mO4qvfMbTI7fHI3cpZoOhKn96iSnBMRE1diQbOL0N/4WHQuOMUZB++Y104Qce/SJZLplrHC0TqVubBkFrT1tNCuzdYHWQEyg41LWtIRYbZXgVf7y0LV3agfMKRdRFUuiY5WbXc2g4/9tKgomy0xcrsUdyD1yxSCQ5Wo5rvqmSV66aJrYOQH4cC6rviDXiaspuYJpjcJaYnDZavEsjrK7YthTwIYpRBVa8hWWaoWbdBO9gzjMbwu1UzIZCEm
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_81380B9D90644EF1A83EE300E5B8D810junipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: f78cccec-adf0-4d08-f7bb-08d666059802
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Dec 2018 22:59:12.9343 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB5158
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-12-19_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1812190180
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/ZwwEZP_lIax9itT6yaMn4ntze7c>
Subject: Re: [bess] Comment on draft-ietf-bess-service-chaining-06
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2018 22:59:22 -0000

Hi Andy,

I‘m struggling to make the connection, since draft-ietf-bess-service-chaining is specifically about how to do service chaining without needing a new protocol like NSH, so SFF labels would never be used.

In draft-ietf-bess-service-chaining , if MPLS transport were used between Service Function Forwarders, a label would be allocated for a SF interface when a route pointing to it is installed (by the controller). This would be advertised to the controller and from there sent to the forwarders with egress interfaces for the previous SF in the chain. The label would be used at the bottom of the MPLS stack as is done normally.

Cheers

Stuart
-914 886 2534

From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Tuesday, December 4, 2018 at 5:10 PM
To: "bess@ietf.org" <bess@ietf.org>, "draft-ietf-bess-service-chaining@ietf.org" <draft-ietf-bess-service-chaining@ietf.org>
Cc: "draft-ietf-mpls-sfc-encapsulation@ietf.org" <draft-ietf-mpls-sfc-encapsulation@ietf.org>
Subject: Comment on draft-ietf-bess-service-chaining-06
Resent-From: <alias-bounces@ietf.org>
Resent-To: <rex@cisco.com>, <wsmackie@juniper.net>, <dhrao@cisco.com>, <brunorijsman@gmail.com>, <mnapierala@att.com>, <thomas.morin@orange.com>
Resent-Date: Tuesday, December 4, 2018 at 5:10 PM

I just read the new revision of draft-ietf-bess-service-chaining. Although the draft doesn't use the RFC 8300 NSH, it could very easily take advantage of features provided by the NSH (such as metadata) by adding NSH over MPLS as defined in draft-ietf-mpls-sfc-encapsulation to the list of encapsulations listed in section 2.5. And this draft provides an excellent label distribution mechanism for NSH over MPLS. It would make a lot of sense to add a reference to draft-ietf-mpls-sfc-encapsulation in the list of encapsulations in section 2.5.

Thanks,
Andy

v2.23.0 | Report a Bug | By Email