IETF Logo Mail Archive

[sfc] FW: New Version Notification for draft-trossen-sfc-name-based-sff-01.txt

"Trossen, Dirk" <Dirk.Trossen@InterDigital.com> Thu, 18 October 2018 12:56 UTC

Return-Path: <Dirk.Trossen@InterDigital.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E11C3130EA9 for <sfc@ietfa.amsl.com>; Thu, 18 Oct 2018 05:56:53 -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_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=interdigital.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 FfuTRI3nTU6R for <sfc@ietfa.amsl.com>; Thu, 18 Oct 2018 05:56:51 -0700 (PDT)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0118.outbound.protection.outlook.com [104.47.41.118]) (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 CD92C130EFA for <sfc@ietf.org>; Thu, 18 Oct 2018 05:56:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interdigital.onmicrosoft.com; s=selector1-interdigital-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vn2x5MwEZaSVHps25gnzaioPD2ciNFsHV9KjByxxtNI=; b=V/sWTUuUlkv7XmSC5qP7HWi4vX/4xgynoiBW/BY1XI6tlLFmpUPgXel3wZEDCaTflWcHOHR+ZrJF77nHbLgEhF9YUxtfZYxYsRMMDvDlGWXcZwzXXc8u4rRj6SS21d6FuRH8obHq4aCyLnmVjVI1Xqx5yvFEGae6F8fXNjhJdcc=
Received: from DM6PR10MB2777.namprd10.prod.outlook.com (20.177.216.82) by DM6PR10MB2729.namprd10.prod.outlook.com (20.176.89.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1228.25; Thu, 18 Oct 2018 12:56:24 +0000
Received: from DM6PR10MB2777.namprd10.prod.outlook.com ([fe80::849d:1af6:85d3:144e]) by DM6PR10MB2777.namprd10.prod.outlook.com ([fe80::849d:1af6:85d3:144e%3]) with mapi id 15.20.1228.032; Thu, 18 Oct 2018 12:56:24 +0000
From: "Trossen, Dirk" <Dirk.Trossen@InterDigital.com>
To: Service Function Chaining IETF list <sfc@ietf.org>
Thread-Topic: New Version Notification for draft-trossen-sfc-name-based-sff-01.txt
Thread-Index: AQHUZlCnSGjcF5A48EmZybcqrXu916Uk9m0Q
Date: Thu, 18 Oct 2018 12:56:24 +0000
Message-ID: <DM6PR10MB2777AC96B185B8B7B24597FDF3F80@DM6PR10MB2777.namprd10.prod.outlook.com>
References: <153980486541.27616.10379489791817114306.idtracker@ietfa.amsl.com>
In-Reply-To: <153980486541.27616.10379489791817114306.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Dirk.Trossen@InterDigital.com;
x-originating-ip: [82.144.227.101]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM6PR10MB2729; 6:IdmxDlnK7hYa+wTu0vGgOMKHC8OEMNjReIk5IQypzwiZJO4Hm5Vm1+XEsafVT8DrvumXvZhbHWF8L9rT00eF3W8lSNhe8/qtKgAWt4fk5XNt/Zu2EsnXmICMVE1+2O3Ss803y5jeqsHwk7d+1BHG+2vrsNlpVUowX69cR23cd+ZYKgdMUEKuE3Dp3u3Gp7zadAA9ZYTPL3gPQ0I0TkHVHnUVjofIt2M/tqJko8smlRzkEf4LyyXY2/Y2JvNObSvQ4drkrLvfmKQyVZUCxFcfevb/f4+uRPuBO5Oouy1RkMIlDc6B4pAjQ8PZa+jHohsE2QGq7gmRQsilnQ0+z9FzZtz12wBegry1QGHmpF45N8dXdAyCKjawlYJXnzx+Kfc2Otck3iRKm7+ieuQjTaQz7VhLgBE6wYKGlPzgNbLCSa9MSQ3LX2AjzucXR5F23U2bEQdQ2UTV/MIn8L6Gd4lgDw==; 5:oWOkTmUmoKWj1+NJTAhXtkcsXfglm3uC/B/G+QuDmlwj05rA9WbgNKTAfY7QbpsV8822V6lijoLtl/MHdSXEdmHE2mDGpEa/B1wdibEf7/bX0E4pWi2MupsIufJtnOXxV1qo9/Vpf4070C8X/tFjA0W5J23x4z2Ba7x54aAX3Nw=; 7:zcB0dwOngJ2PHPu8uLd8xNfkblAxb/RtkWJpAvgfrDB3H77SotajpaRju6q8dm5RN873aLHvL1ZLi5GESb9hkPRTcH4X2oRR5bfBPUwjbeOJ+XPR+lGtr2T0pHBTM6+KMTJWwVpl5+xivvGTA1qGzH/EzlG/Gqv+Rmoi1ep305+6TNdoOI8iXlxPmL/Za8WdYg1qe+t0y65ZuWp8eeXmk6Gx+dnIQJTKkjwXTEjPPjgSTv39R2mSdK6IcfmT8C8K
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: e905779f-303e-4ea9-bb63-08d634f91c1b
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:DM6PR10MB2729;
x-ms-traffictypediagnostic: DM6PR10MB2729:
x-microsoft-antispam-prvs: <DM6PR10MB272957D640E8E77739F6477AF3F80@DM6PR10MB2729.namprd10.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3231355)(944501410)(52105095)(3002001)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123562045)(20161123558120)(20161123560045)(201708071742011)(7699051)(76991095); SRVR:DM6PR10MB2729; BCL:0; PCL:0; RULEID:; SRVR:DM6PR10MB2729;
x-forefront-prvs: 08296C9B35
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(396003)(39850400004)(376002)(346002)(366004)(189003)(199004)(13464003)(6306002)(81156014)(14454004)(8676002)(76176011)(72206003)(81166006)(7696005)(478600001)(105586002)(99286004)(15650500001)(8936002)(5250100002)(66066001)(966005)(106356001)(186003)(53546011)(446003)(102836004)(26005)(316002)(6506007)(6916009)(486006)(7736002)(86362001)(256004)(476003)(74316002)(11346002)(305945005)(5660300001)(6116002)(3846002)(25786009)(71200400001)(71190400001)(14444005)(2906002)(68736007)(33656002)(2473003)(53936002)(4001150100001)(6436002)(55016002)(97736004)(229853002)(2900100001)(9686003)(85282002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR10MB2729; H:DM6PR10MB2777.namprd10.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: InterDigital.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: gUNMPPeUPO8Kkvm12DiHEAI8sNmNBSS+Z7CjrU4J57zp8d1JvCruxMLRkMO+BmVdrcd26tuVuJ4BVWCJyMxf9rEQb5tSP8tQqg0Kj3dmL59/IrVZbquVo7RImkQSLhPV1lznbzGbOtsMPu5MnSDLbLFbM2LsRU8p8LsKrdiVdGltjelwBu7sypUod1tnFLa4/5kCnzIDcOPGjNQYbd+ueC9aVX4hMYCPDZkytg1+ZyEzXpkO51MxCTXLJ1U50iIdRCguk3Hxvv5U0T4RuzAnnEYhE3fWxBnz+DUv3llqoC04TAX0zIamB8ka0i0P4MQSXdkf8L/j6TaftgTz0Atpewflkf8y6yv+Cgq/cokGWrg=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: interdigital.com
X-MS-Exchange-CrossTenant-Network-Message-Id: e905779f-303e-4ea9-bb63-08d634f91c1b
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Oct 2018 12:56:24.0743 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: e351b779-f6d5-4e50-8568-80e922d180ae
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR10MB2729
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/Z0pLD8vQ7NKMEQNAJkDgODf4ZvM>
Subject: [sfc] FW: New Version Notification for draft-trossen-sfc-name-based-sff-01.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2018 12:57:00 -0000

All,

Based on the input received during the Montreal meeting, we updated the name-based SFF draft (see below), providing significantly more detail on issues like SF registration, nSFF forwarding, local SF forwarding and alike. We also simplified yet focused the use case with reference to ongoing 3GPP Rel16 work.

Please review and share comments on this draft version.

Best,

Dirk

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: 17 October 2018 20:34
To: Purkayastha, Debashish <Debashish.Purkayastha@InterDigital.com>; Trossen, Dirk <Dirk.Trossen@InterDigital.com>; Purkayastha, Debashish <Debashish.Purkayastha@InterDigital.com>; Rahman, Akbar <Akbar.Rahman@InterDigital.com>; Trossen, Dirk <Dirk.Trossen@InterDigital.com>
Subject: New Version Notification for draft-trossen-sfc-name-based-sff-01.txt


A new version of I-D, draft-trossen-sfc-name-based-sff-01.txt
has been successfully submitted by Debashish Purkayastha and posted to the IETF repository.

Name:		draft-trossen-sfc-name-based-sff
Revision:	01
Title:		Name-Based Service Function Forwarder (nSFF) component within SFC framework
Document date:	2018-10-17
Group:		Individual Submission
Pages:		24
URL:            https://www.ietf.org/internet-drafts/draft-trossen-sfc-name-based-sff-01.txt
Status:         https://datatracker.ietf.org/doc/draft-trossen-sfc-name-based-sff/
Htmlized:       https://tools.ietf.org/html/draft-trossen-sfc-name-based-sff-01
Htmlized:       https://datatracker.ietf.org/doc/html/draft-trossen-sfc-name-based-sff
Diff:           https://www.ietf.org/rfcdiff?url2=draft-trossen-sfc-name-based-sff-01

Abstract:
   Many stringent requirements are imposed on today's network, such as
   low latency, high availability and reliability in order to support
   several use cases such as IoT, Gaming, Content distribution, Robotics
   etc.  Adoption of cloud and fog technology at the edge of the network
   allows operator to deploy a single "Service Function" to multiple
   "Execution locations".  The decision to steer traffic to a specific
   location may change frequently based on load, proximity etc.  Under
   the current SFC framework, steering traffic dynamically to the
   different execution end points require a specific 're-chaining',
   i.e., a change in the service function path reflecting the different
   IP endpoints to be used for the new execution points.  In order to
   address this, we discuss separating the logical Service Function Path
   from the specific execution end points.  This can be done by
   identifying the Service Functions using a name rather than a routable
   IP endpoint (or Layer 2 address).  This draft describes the necessary
   extensions, additional functions and protocol details in SFF to
   handle name based relationships.

                                                                                  


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

v2.23.0 | Report a Bug | By Email