From nobody Tue Jan 6 09:20:14 2015 Return-Path: X-Original-To: hiaps@ietfa.amsl.com Delivered-To: hiaps@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD20D1A0394 for ; Tue, 6 Jan 2015 09:20:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.75 X-Spam-Level: X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no 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 sAr9q7ustdbR for ; Tue, 6 Jan 2015 09:20:10 -0800 (PST) Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [IPv6:2a00:1450:4010:c04::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02AA51A1A9F for ; Tue, 6 Jan 2015 09:20:10 -0800 (PST) Received: by mail-lb0-f170.google.com with SMTP id 10so20017897lbg.1 for ; Tue, 06 Jan 2015 09:20:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:date:message-id:subject:from:to:cc :content-type; bh=BRLaKWN2QSIb/9xPDvPquAThcDqsttdHec0M48Zfy4Y=; b=Aaxkj0OxljltsJ8Hh5SbcRr85T34JsZgxFbrxmxSLVAaFTUpLsub5WVk0hRS2qmEAG dVUVpkRzAs6PmjewD+WNyp+BdzV3nUl6LC5uKVH2m8ChC4HnKD8NZN4C4IWcxg/w04lL YllqDgRnIcRWIwvdra7RkvveuvF0mz622FXRK7/SlwoLFZamnPK8KQuY5u4KPHYAATB3 WWNrLJiEZkDinVX+08TQ3Rm/N0IIskdeFZrjbtXbPViMxZ+uJ3g4vVYk9Yivwk6C+scm oFFZ/nRw6xbbEBGWo1ZHxmbn4pXABpxlKry7qnEDsXiWYMjrPGu6Wwd8CB8j/uld7sya V/HA== MIME-Version: 1.0 X-Received: by 10.152.197.5 with SMTP id iq5mr100923405lac.6.1420564808464; Tue, 06 Jan 2015 09:20:08 -0800 (PST) Received: by 10.114.63.51 with HTTP; Tue, 6 Jan 2015 09:20:08 -0800 (PST) Date: Tue, 6 Jan 2015 11:20:08 -0600 Message-ID: From: Behcet Sarikaya To: "hiaps@ietf.org" Content-Type: text/plain; charset=UTF-8 Archived-At: http://mailarchive.ietf.org/arch/msg/hiaps/VE0DkGfhqYXaAUAUA9J9aDtOBBI Cc: joel jaeggli , Mohamed Boucadair , Brandon Williams , "Dirk.von-Hugo@telekom.de" Subject: [hiaps] Description of work X-BeenThere: hiaps@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: sarikaya@ieee.org List-Id: "Host Identification, Address and Prefix Sharing in Wi-Fi Access \(hiaps\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jan 2015 17:20:12 -0000 Hi all, We have been receiving offline queries about hiaps work, especially from the new members. We worked out the work description and will include it here for your comments: Host Identification, Address and Prefix Sharing in Service Function Chaining (hiaps) In order to deliver services to end users, network operators utilize service functions. Service functions can be packet filtering at firewalls, load balancers, port quota enforcers, traffic offloaders, network address translation (NAT) functions, etc. For a given service such as optimizing TCP parameters, a service function chain (SFC) is the abstract view of the required functions and the order in which they are applied. An SFC is instantiated through selection of specific service function instances on specific network nodes to form a service graph: this is called a Service Function Path (SFP). Hiaps is interested in the service function chains that involve NATs, tunneling environments in IPv4 or when prefix sharing is used in IPv6. In those chains, not only the subscriber but also the host needs to be identified and host address needs to be known by the specific service function. Such cases frequently occur in virtualized home networks and in mobile networks. In hiaps work, the architecture defined by Service Function Chaining Working Group will be used. The work in hiaps is expected to involve some new meta data/context information in SFC encapsulation for the host id/address and a new out of band protocol to transport host id/address to the service function forwarder. The protocols for chained execution of service functions may involve in band approaches such as new IP options, the use of VLANs or tunneling, among other techniques. Such protocols to be used in transporting the meta data/context information in SFC encapsulation to be defined in hiaps are out of scope. The protocols for transporting host id/address to the service function forwarder may involve in band approaches such as new TCP/IP options are out of scope due to the security and privacy issues in carrying such sensitive information as the host id/address. Only out of band protocols will be considered. Specifically, hiaps will work on the following: 1) Use Cases: This is a document describing the use cases from home, mobile, fixed networks where host identification, address and prefix sharing issues occur in certain service function chains in delivering services. This documents should clearly define the problem. 2) Requirements: This document will analyse and eventually enhance requirements that need to be fulfilled by the different entities such as service function forwarder arising from the use cases document. 3) Solutions: A document describing an out of band approach to provide host identification to an external server in service function chaining scenarios. A document describing host id/address meta data/context. Regards, Behcet & Dirk From nobody Fri Jan 23 01:42:25 2015 Return-Path: X-Original-To: hiaps@ietfa.amsl.com Delivered-To: hiaps@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C7421A020D for ; Fri, 23 Jan 2015 01:42:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.61 X-Spam-Level: X-Spam-Status: No, score=-3.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_22=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 c2LTjud9cCiB for ; Fri, 23 Jan 2015 01:42:22 -0800 (PST) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D46D81A01D8 for ; Fri, 23 Jan 2015 01:42:21 -0800 (PST) Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BRQ77595; Fri, 23 Jan 2015 09:42:20 +0000 (GMT) Received: from SZXEMI412-HUB.china.huawei.com (10.86.210.35) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 23 Jan 2015 09:42:19 +0000 Received: from SZXEMI501-MBS.china.huawei.com ([169.254.2.238]) by szxemi412-hub.china.huawei.com ([10.86.210.35]) with mapi id 14.03.0158.001; Fri, 23 Jan 2015 17:42:16 +0800 From: "Ligaifan (Vince)" To: "hiaps@ietf.org" Thread-Topic: Relationship between Host Identification and SFC ID Thread-Index: AdA27/YvOTSaxkISR46JVxLVOr+Buw== Date: Fri, 23 Jan 2015 09:42:15 +0000 Message-ID: <571BEA8F911C3947964749CE62B40DC412C8F62D@SZXEMI501-MBS.china.huawei.com> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.61.38.169] Content-Type: multipart/alternative; boundary="_000_571BEA8F911C3947964749CE62B40DC412C8F62DSZXEMI501MBSchi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: Cc: "mohamed.boucadair@orange.com" Subject: [hiaps] Relationship between Host Identification and SFC ID X-BeenThere: hiaps@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Host Identification, Address and Prefix Sharing in Wi-Fi Access \(hiaps\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2015 09:42:23 -0000 --_000_571BEA8F911C3947964749CE62B40DC412C8F62DSZXEMI501MBSchi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all, The root causes for the host identification issue are address sharing and p= resence of tunnels. Host ID is used to identified a host due to address sha= ring. In SFC scenario, SFC ID(SF Chain Identifier) identifies an SF Chain and met= adata provides contextual information about the data packets which traverse= a service chain. So my question is that can SFC ID together with metadata also be used to so= lve issues due to address sharing? Regards, Gaifan Li --_000_571BEA8F911C3947964749CE62B40DC412C8F62DSZXEMI501MBSchi_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi all,

 

The root causes for the host id= entification issue are address sharing and presence of tunnels. Host ID is = used to identified a host due to address sharing.

In SFC scenario, SFC ID(SF Chai= n Identifier) identifies an SF Chain and metadata provides contextual infor= mation about the data packets which traverse a service chain.

So my question is that can SFC = ID together with metadata also be used to solve issues due to address shari= ng?

 

Regards,

Gaifan Li

 

 

 

 

--_000_571BEA8F911C3947964749CE62B40DC412C8F62DSZXEMI501MBSchi_--