Re: [sfc] Questions about draft-quinn-sfc-arch-05

Xuxiaohu <xuxiaohu@huawei.com> Thu, 19 June 2014 01:27 UTC

Return-Path: <xuxiaohu@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 186701A025C for <sfc@ietfa.amsl.com>; Wed, 18 Jun 2014 18:27:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level:
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] 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 s43cxnWXDNQ2 for <sfc@ietfa.amsl.com>; Wed, 18 Jun 2014 18:27:32 -0700 (PDT)
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 3A0E61A0087 for <sfc@ietf.org>; Wed, 18 Jun 2014 18:27:32 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BFO73129; Thu, 19 Jun 2014 01:27:30 +0000 (GMT)
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 19 Jun 2014 02:27:27 +0100
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.62]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Thu, 19 Jun 2014 09:27:22 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: Questions about draft-quinn-sfc-arch-05
Thread-Index: Ac+K3S127YmDPWQNScaOnWZ/UqobUwAIEFG0ABflwnA=
Date: Thu, 19 Jun 2014 01:27:21 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0828340C@NKGEML512-MBS.china.huawei.com>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08283162@NKGEML512-MBS.china.huawei.com> <45A697A8FFD7CF48BCF2BE7E106F06040BE3F74E@xmb-rcd-x04.cisco.com>
In-Reply-To: <45A697A8FFD7CF48BCF2BE7E106F06040BE3F74E@xmb-rcd-x04.cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.98.134]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/yBSc8Nj2PcHnEjf6KeWS0dValIA
Subject: Re: [sfc] Questions about draft-quinn-sfc-arch-05
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 19 Jun 2014 01:27:34 -0000


> -----Original Message-----
> From: Reinaldo Penno (repenno) [mailto:repenno@cisco.com]
> Sent: Wednesday, June 18, 2014 10:01 PM
> To: Xuxiaohu; sfc@ietf.org
> Subject: RE: Questions about draft-quinn-sfc-arch-05
> 
> When you create a Service Path you define the actual service functions (SFs +
> locator) that will provide service. When you create a service function chain you
> only define the type of the service function (dpi, firewall, nat).

Sure. The SFP should be represented by an ordered list of SF IDs and SN locators. However, it seems that the SFF table entry (an ordered list of SF IDs) as described in draft-quinn-sfc-arch-05 is about an SFC, rather than an SFP.

Best regards,
Xiaohu
 
> thanks,
> 
> Reinaldo
> ________________________________________
> From: sfc [sfc-bounces@ietf.org] on behalf of Xuxiaohu
> [xuxiaohu@huawei.com]
> Sent: Wednesday, June 18, 2014 3:07 AM
> To: sfc@ietf.org
> Subject: [sfc] Questions about draft-quinn-sfc-arch-05
> 
> Hi all,
> 
> I have two questions about draft-quinn-sfc-arch-05:
> 
> 1. According to the following figure quoted from the above draft, it seems each
> SFF Table entry (I,e., SFP) only contains an ordered list of SF IDs. If so, for a given
> SFID in the list, how does the SFF know on which particular service node that SF
> should be performed (assume there are multiple service nodes which can
> provide the SF of that SF ID)?
> 
> 
>                 +------+----------------------------------+
>                 | SFP  |   Ordered Service Functions      |
>                 |------+----------------------------------+
>                 | ID   | order1 | order2 | order3 | ...   |
>                 +------+--------+--------+--------+-------+
>                 | SFP1 | SFID1  | SFID5  | SFID20 |       |
>                 +------+--------+--------+--------+-------+
>                 | SFP4 | SFID100| SFID3  | SFID4  | SFID9 |
>                 +------+--------+--------+--------+-------+
>                 | ...  |        |        |        |       |
>                 +------+--------+--------+--------+-------+
> 
>                             Figure 3: SFF Table
> 
> 2. Does the Transport Derived SFF concept mean the SFP could also be
> represented by some information contained in the transport layer, instead of the
> service path id contained in the SFC encapsulation header? For instance, an
> ordered list of service node locators and service function instance identities (see
> http://tools.ietf.org/html/draft-xu-spring-sfc-use-case-01)?
> 
> Best regards,
> Xiaohu
> 
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc