IETF Logo Mail Archive

Re: [sfc] I-D Action: draft-ietf-sfc-use-case-mobility-06.txt

"Jeffrey Napper (jenapper)" <jenapper@cisco.com> Wed, 13 April 2016 07:36 UTC

Return-Path: <jenapper@cisco.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 E808A12D802; Wed, 13 Apr 2016 00:36:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.517
X-Spam-Level:
X-Spam-Status: No, score=-15.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 X4UxdHpuk87n; Wed, 13 Apr 2016 00:36:05 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4533512D773; Wed, 13 Apr 2016 00:36:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4196; q=dns/txt; s=iport; t=1460532965; x=1461742565; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=8crdD3rYwf0j6UarBFVkn3UvFcEnQ1SxgyJ0S+KVXWs=; b=IunyfwEyPO1T5f1jxtP4gqJ4zUAIjV7QbUsiTUBz9qsLnOms3pL3WeV3 IKf6Hn1nK6cfsHaGHCx64p9QzbRKmDp3I7yN1uxB+5sVIeE7wP+qMfr8l RjAoacwBYvxS1FadFFjVBcIIoWnxtPNn/rg5sDXlNfXMoNP141AjD4VNX w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D3AQCb9g1X/5NdJa1egzdTfQa6ZAENgXYXC4VsAhyBJTgUAQEBAQEBAWUnhEIBAQQBAQEgETMHCxACAQgSCAIRFQICAiULFQIOAgQBDQWIKA6wLJIZAQEBAQEBAQEBAQEBAQEBAQEBAQEBFXyFJYF1glaEfoJBK4IrBZgIAYV2iBaBZ06EAIhbjyYBHgEBQoNnbIh8fgEBAQ
X-IronPort-AV: E=Sophos;i="5.24,478,1454976000"; d="scan'208";a="259280189"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Apr 2016 07:36:04 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id u3D7a4SF001607 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 13 Apr 2016 07:36:04 GMT
Received: from xch-rcd-005.cisco.com (173.37.102.15) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 13 Apr 2016 02:36:03 -0500
Received: from xch-rcd-005.cisco.com ([173.37.102.15]) by XCH-RCD-005.cisco.com ([173.37.102.15]) with mapi id 15.00.1104.009; Wed, 13 Apr 2016 02:36:02 -0500
From: "Jeffrey Napper (jenapper)" <jenapper@cisco.com>
To: "internet-drafts@ietf.org" <internet-drafts@ietf.org>, "i-d-announce@ietf.org" <i-d-announce@ietf.org>
Thread-Topic: [sfc] I-D Action: draft-ietf-sfc-use-case-mobility-06.txt
Thread-Index: AQHRlVbQzE3uNggYfUqBgv8TVW9P/J+H+O0A
Date: Wed, 13 Apr 2016 07:36:02 +0000
Message-ID: <286E5994-B0AA-4D0D-81A5-D3BE6440DD5F@cisco.com>
References: <20160413073336.6079.80149.idtracker@ietfa.amsl.com>
In-Reply-To: <20160413073336.6079.80149.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.235.128]
Content-Type: text/plain; charset="utf-8"
Content-ID: <FF1ACEC3DD5F384DB6E09FCB55E3DA0D@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/jsxcA0LRvgHHGUuTHB1_USaUYpY>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] I-D Action: draft-ietf-sfc-use-case-mobility-06.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Apr 2016 07:36:07 -0000

This is just a version bump to prevent expiration while the draft waits to start last call. I hope. :)


Cheers,
Jeff








On 4/13/16, 9:33 AM, "internet-drafts@ietf.org" <internet-drafts@ietf.org> wrote:

>
>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>This draft is a work item of the Service Function Chaining of the IETF.
>
>        Title           : Service Function Chaining Use Cases in Mobile Networks
>        Authors         : Walter Haeffner
>                          Jeffrey Napper
>                          Martin Stiemerling
>                          Diego R. Lopez
>                          Jim Uttaro
>	Filename        : draft-ietf-sfc-use-case-mobility-06.txt
>	Pages           : 26
>	Date            : 2016-04-13
>
>Abstract:
>   This document provides some exemplary use cases for service function
>   chaining in mobile service provider networks.  The objective of this
>   draft is not to cover all conceivable service chains in detail.
>   Rather, the intention is to localize and explain the application
>   domain of service chaining within mobile networks as far as it is
>   required to complement the problem statement [RFC7498] and
>   architecture framework [ietf-sfc-arch] of the working group.
>
>   Service function chains typically reside in a LAN segment which links
>   the mobile access network to the actual application platforms located
>   in the carrier's datacenters or somewhere else in the Internet.
>   Service function chains (SFC) ensure a fair distribution of network
>   resources according to agreed service policies, enhance the
>   performance of service delivery or take care of security and privacy.
>   SFCs may also include Value Added Services (VAS).  Commonly, SFCs are
>   typical middle box based services.
>
>   General considerations and specific use cases are presented in this
>   document to demonstrate the different technical requirements of these
>   goals for service function chaining in mobile service provider
>   networks.
>
>   The specification of service function chaining for mobile networks
>   must take into account an interaction between service function chains
>   and the 3GPP Policy and Charging Control (PCC) environment.
>
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-ietf-sfc-use-case-mobility/
>
>There's also a htmlized version available at:
>https://tools.ietf.org/html/draft-ietf-sfc-use-case-mobility-06
>
>A diff from the previous version is available at:
>https://www.ietf.org/rfcdiff?url2=draft-ietf-sfc-use-case-mobility-06
>
>
>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.
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>_______________________________________________
>sfc mailing list
>sfc@ietf.org
>https://www.ietf.org/mailman/listinfo/sfc

v2.23.0 | Report a Bug | By Email