Re: [sfc] New Version Notification for draft-trossen-sfc-name-based-sff-01.txt
<Dirk.von-Hugo@telekom.de> Wed, 31 October 2018 15:58 UTC
Return-Path: <Dirk.von-Hugo@telekom.de>
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 1282A130DDA for <sfc@ietfa.amsl.com>; Wed, 31 Oct 2018 08:58:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.169
X-Spam-Level:
X-Spam-Status: No, score=-3.169 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 CYqoSI78hhuW for <sfc@ietfa.amsl.com>; Wed, 31 Oct 2018 08:58:56 -0700 (PDT)
Received: from mailout41.telekom.de (MAILOUT41.telekom.de [194.25.225.151]) (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 1E6DA130E2E for <sfc@ietf.org>; Wed, 31 Oct 2018 08:58:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1541001536; x=1572537536; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=U5cv5WrRYtbr8mnrAd/gm7hNRE+klHPRj6ps9wg4d/4=; b=H0MS1H0l7VdkMO+NHNA3CeMdXrryTlmR8pLeIcJO1/pJ1Oi/7eUp+ZQN phZq+C6vA4MvkTRAD9PpnXaiQN9MVbf8gsBVDRn++4w6mc/gya/74VTVI GthSucXDGR8eTxq/yLE9A6czpBNTG7a1Wb6lUVr9TbkqYlohIV6ftEGuH YYunGilwcT+1tJIdGYpqCU2iV+y4vk4ggEsOPTnuuEhAaKOhQhPqeNkaS DHV6GTuZhho7ahi9WW+wNv4fCpjz4PRsSdy2Ix1p2URCVLMGG++Vzqhvd F48mlDnoRFqZ50VIeEzXQU1Xr405TBqaYaDlmJFj8cDEBajPU5ylemfd7 w==;
Received: from qde9xy.de.t-internal.com ([10.171.254.32]) by MAILOUT41.dmznet.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Oct 2018 16:58:54 +0100
X-IronPort-AV: E=Sophos;i="5.54,447,1534802400"; d="scan'208";a="153693241"
Received: from he105709.emea1.cds.t-internal.com ([10.169.118.41]) by QDE9Y1.de.t-internal.com with ESMTP/TLS/AES256-SHA; 31 Oct 2018 16:58:53 +0100
Received: from HE105780.EMEA1.cds.t-internal.com (10.169.118.26) by HE105709.emea1.cds.t-internal.com (10.169.118.41) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 31 Oct 2018 16:58:53 +0100
Received: from HE106564.emea1.cds.t-internal.com (10.171.40.16) by HE105780.EMEA1.cds.t-internal.com (10.169.118.26) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 31 Oct 2018 16:58:53 +0100
Received: from GER01-LEJ-obe.outbound.protection.outlook.de (51.5.80.19) by O365mail01.telekom.de (172.30.0.234) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Wed, 31 Oct 2018 16:58:37 +0100
Received: from FRAPR01MB0801.DEUPRD01.PROD.OUTLOOK.DE (10.158.135.18) by FRAPR01MB0803.DEUPRD01.PROD.OUTLOOK.DE (10.158.135.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1273.27; Wed, 31 Oct 2018 15:58:52 +0000
Received: from FRAPR01MB0801.DEUPRD01.PROD.OUTLOOK.DE ([fe80::39cb:fbe1:c7d2:d0ec]) by FRAPR01MB0801.DEUPRD01.PROD.OUTLOOK.DE ([fe80::39cb:fbe1:c7d2:d0ec%3]) with mapi id 15.20.1273.028; Wed, 31 Oct 2018 15:58:52 +0000
From: Dirk.von-Hugo@telekom.de
To: Dirk.Trossen@InterDigital.com, sfc@ietf.org
Thread-Topic: New Version Notification for draft-trossen-sfc-name-based-sff-01.txt
Thread-Index: AQHUZlCnSGjcF5A48EmZybcqrXu916Uk9m0QgAGaY5CAEvjUMA==
Date: Wed, 31 Oct 2018 15:58:52 +0000
Message-ID: <FRAPR01MB08016B4AE612D15FE2AEF3B3D1CD0@FRAPR01MB0801.DEUPRD01.PROD.OUTLOOK.DE>
References: <153980486541.27616.10379489791817114306.idtracker@ietfa.amsl.com> <DM6PR10MB2777AC96B185B8B7B24597FDF3F80@DM6PR10MB2777.namprd10.prod.outlook.com> <FRAPR01MB08012D78C3362F184DD2439AD1F90@FRAPR01MB0801.DEUPRD01.PROD.OUTLOOK.DE>
In-Reply-To: <FRAPR01MB08012D78C3362F184DD2439AD1F90@FRAPR01MB0801.DEUPRD01.PROD.OUTLOOK.DE>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Dirk.von-Hugo@telekom.de;
x-originating-ip: [212.201.104.11]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; FRAPR01MB0803; 6:Is8uYWc6ICCYqH3B+lAxL4R0BZjsTk+ufbf0rnUs6NHG2ZZhxi0DpfNvS2deMby128t4AcGR0zyeznMjo29A8IZ7yAu0YGpexOiOLZjzSM1vLzXEopo6sgnu9jcL6/0RSyR2PVX1jI4dYCegFlP4zp4zMBrftz8QOpZ2VjWQ+po2gq2UzIaYtDrLm60kSD6O/bPapDxSpDikriFMyOPQiN7EiYUaYFamL64pm3CwileI4E2NbEl/wWjV3aRLxFZcpDLowmu234SKL6On0xO/l3o/2rZwtfKFbXKtdmgTLctfzufyIQxRuAt1ypSqvzgva+zGMTo3zLwxYjPgEZa4Mdr2mk2okrwN6JKGXPJUJAWmQf0vTJTr7SnTXC/qQUseVx9zQySoDo7dOAil/1s4Y42S9GeePdPJNqgmGfk2xNpG+xpBO5akW+JyhdOUMDd5MgmDrHZ3HjZ4wnJmgghHVw==; 5:mOmG6PGGVfpj7vE1s+WyxrP1xvbg7YxF4Bwb3vuFR2iQZx0IS+tUKYZIH6/3JVyG2A5hC/heBK49n8ShZs3ZCGgN1XnO4MINqyi/ok4VaruTb5n7oKXVss6kZSNZPDL7iikz6Z3DEaeM0M3rstJbbJ9Imdy2yPk2k+kXWvfFOjU=; 7:9M84U84UUqYvJx/NomMxrjk0KRZ5T0LmjXuvQNz5tdDwMzrrJliprOcpYCwsEUEkD7AxaP+y/i0WAOoh6cxuIG/DglbbEBkcCdvMN6hglVR6a9kRnBSpkgYkhj3msbyIwFkBfKdY+1XbmdtUdSvtqQ==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 2053a338-4eab-49ae-14dd-08d63f49c128
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:FRAPR01MB0803;
x-ms-traffictypediagnostic: FRAPR01MB0803:
x-microsoft-antispam-prvs: <FRAPR01MB08036133398D033CF33A3011D1CD0@FRAPR01MB0803.DEUPRD01.PROD.OUTLOOK.DE>
x-exchange-antispam-report-test: UriScan:(120809045254105);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(3231382)(944501410)(52105095)(93006095)(93001095)(3002001)(10201501046)(148016)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123558120)(20161123562045)(20161123564045)(201708071742011)(7699051)(76991095); SRVR:FRAPR01MB0803; BCL:0; PCL:0; RULEID:; SRVR:FRAPR01MB0803;
x-forefront-prvs: 084285FC5C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(396003)(136003)(346002)(39860400002)(376002)(189003)(199004)(13464003)(4001150100001)(53546011)(5250100002)(2906002)(71200400001)(316002)(71190400001)(6116002)(105586002)(97736004)(106356001)(7696005)(14444005)(3846002)(256004)(86362001)(446003)(110136005)(102836004)(52396003)(229853002)(5660300001)(68736007)(2900100001)(186003)(53936002)(14454004)(966005)(66066001)(7736002)(8676002)(81156014)(11346002)(74482002)(33656002)(81166006)(478600001)(6306002)(6246003)(76176011)(486006)(9686003)(55016002)(305945005)(75402003)(2501003)(8936002)(26005)(15650500001)(72206003)(476003); DIR:OUT; SFP:1101; SCL:1; SRVR:FRAPR01MB0803; H:FRAPR01MB0801.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 27VHr0WlAmfFkHwVxsLZIFGGhttiV76g1ezm48LCqTvN6CKmB3XntsKoaA/PK3bqWpsFesd067hw2iyUMRb5pjzKYNsmHQJv8zlheG1w+87nrj9VfZjUKMqiVHWTw4nMWE8AMYHryneVKmkXtG1Tf/cKgrxvgEA5evEsIbpEqSTmXhnT8Z9d6fzLcailqgKwtbIdbv5ZUAX6IuptXMjXT69DPeakUCiRXHa4Zzy7TQGrVsWFmhluLoRdOHYb6boMXEPByk9LIAnIGLdRiYiw7JVNzeT3bybI4SKqRdaxGhwM4AZtTQHsucpsdtoqkZExpMSxIdKbbvY9+w5LBIiAD5bpjO/7XbMZ0z32qQnLb3k=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 2053a338-4eab-49ae-14dd-08d63f49c128
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Oct 2018 15:58:52.4670 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: FRAPR01MB0803
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/mk1qu6ZyuFtkz06FbWUi4ubPAV8>
Subject: Re: [sfc] 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: Wed, 31 Oct 2018 15:58:59 -0000
Dear Dirk and co-authors, Thanks for providing the useful draft again. I would like to point out the relation to 3GPPs 5G SBA use case again where network function services are introduced to be combined in a chain like manner to provide a communication service or logical network slice. Name-based addressing and routing would allow to select the optimal appropriate SF instance. I think thus it could be helpful for ongoing 3GPP SA2 study on 'Enhancements to the Service-Based Architecture' for Release 16 (TR 23.742). One minor comment for update is to refer in [_3GPP_SBA] to the actually approved version of 3GPP TS 29.500 (15.1.0) instead of draft (0.4.0) one. ;-) Thanks! Best Regards Dirk -----Original Message----- From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Trossen, Dirk Sent: Donnerstag, 18. Oktober 2018 14:56 To: Service Function Chaining IETF list <sfc@ietf.org> Subject: [sfc] FW: New Version Notification for draft-trossen-sfc-name-based-sff-01.txt 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 _______________________________________________ sfc mailing list sfc@ietf.org https://www.ietf.org/mailman/listinfo/sfc _______________________________________________ sfc mailing list sfc@ietf.org https://www.ietf.org/mailman/listinfo/sfc
- [sfc] FW: New Version Notification for draft-tros… Trossen, Dirk
- Re: [sfc] New Version Notification for draft-tros… Dirk.von-Hugo
- Re: [sfc] New Version Notification for draft-tros… Dirk.von-Hugo
- Re: [sfc] New Version Notification for draft-tros… Trossen, Dirk
- Re: [sfc] New Version Notification for draft-tros… Ramin Khalili