Re: [sfc] is current SFC architecture supporting different types of SFC header formats?
Georgios Karagiannis <georgios.karagiannis@huawei.com> Thu, 04 December 2014 14:40 UTC
Return-Path: <georgios.karagiannis@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 EE7A11AD3D0 for <sfc@ietfa.amsl.com>; Thu, 4 Dec 2014 06:40:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 XCf4RTDgnuf2 for <sfc@ietfa.amsl.com>; Thu, 4 Dec 2014 06:40:50 -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 51D1E1AD3C9 for <sfc@ietf.org>; Thu, 4 Dec 2014 06:40:47 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BMJ34843; Thu, 04 Dec 2014 14:40:43 +0000 (GMT)
Received: from LHREML516-MBX.china.huawei.com ([169.254.1.78]) by lhreml402-hub.china.huawei.com ([10.201.5.241]) with mapi id 14.03.0158.001; Thu, 4 Dec 2014 14:40:39 +0000
From: Georgios Karagiannis <georgios.karagiannis@huawei.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Thread-Topic: [sfc] is current SFC architecture supporting different types of SFC header formats?
Thread-Index: AdAPq35dh1W/iINPRT2JdHnL8IYwVwAT290AAAxhE+D//02BAIAAC9SA
Date: Thu, 04 Dec 2014 14:40:38 +0000
Message-ID: <C5034E44CD620A44971BAAEB372655DCB291B9@LHREML516-MBX.china.huawei.com>
References: <C5034E44CD620A44971BAAEB372655DCB28ACF@LHREML516-MBX.china.huawei.com> <4D83F738-BF44-4A85-8849-D300A2F207F7@cisco.com> <C5034E44CD620A44971BAAEB372655DCB28B39@LHREML516-MBX.china.huawei.com> <D0A5D235.3456%cpignata@cisco.com>
In-Reply-To: <D0A5D235.3456%cpignata@cisco.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.221.64.158]
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/P2MxhZi8sXobZFYqTbuvB-yaD6c
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] is current SFC architecture supporting different types of SFC header formats?
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, 04 Dec 2014 14:40:52 -0000
Hi Carlos, Please note that I do not mean to use different SFC encapsulations simultaneously. >From what I understood from IETF'91 meeting discussions, the Generic SFC encapsulation technique has not yet been selected by the SFC WG. I think that this means that the SFC architecture draft cannot be in favor for one specific SFC encapsulation technique and at the same time excluding other techniques. My question is: Can the following two SFC encapsulation techniques be supported by the functions described in the SFC architecture draft?: o) Single Marking Code Point, like format, see section 5.1 on boucadair draft, see below. o) Explicit Route List, like format, see section 5.3 on boucadair draft, see below. http://www.ietf.org/id/draft-boucadair-sfc-design-analysis-03.txt Best regards, Georgios > -----Original Message----- > From: Carlos Pignataro (cpignata) [mailto:cpignata@cisco.com] > Sent: Thursday, December 04, 2014 3:02 PM > To: Georgios Karagiannis > Cc: sfc@ietf.org > Subject: Re: [sfc] is current SFC architecture supporting different types of > SFC header formats? > > Hi, Georgios, > > Do you mean different SFC Encapsulations simultaneously? The SFC charter > says: > > <snip> > 3. Generic SFC Encapsulation: This document will describe a single > service-level data plane encapsulation format that: > > </snip> > > Because interoperability is the goal. > > Looking at that section, the terminology does not seem to align to the arch > and problem-statement documents. Also, that section seems to describe a > pseudo-format, not a format. The architecture describes the functions in > Section 4.1 and other places. > > Thanks, > > Carlos. > > On 12/4/14, 8:55 AM, "Georgios Karagiannis" > <georgios.karagiannis@huawei.com> wrote: > > >Hi Carlos, > > > >Thanks for your answer! > > > >Does this mean that the SFC architecture is allowing the use of > >different Service Function Chaining Header (SFC encapsulation) formats? > > > >I am referring to the different SFC encapsulation formats that are > >discussed in section 5 of the following ID: > >http://www.ietf.org/id/draft-boucadair-sfc-design-analysis-03.txt > > > >Best regards, > >Georgios > > > > > >> -----Original Message----- > >> From: Carlos Pignataro (cpignata) [mailto:cpignata@cisco.com] > >> Sent: Thursday, December 04, 2014 2:46 PM > >> To: Georgios Karagiannis > >> Cc: sfc@ietf.org > >> Subject: Re: [sfc] is current SFC architecture supporting different > >>types of SFC header formats? > >> > >> Hi, Georgios, > >> > >> The SFC architecture document concerns itself with the functions and > >>not the format. > >> > >> Thanks, > >> > >> Carlos. > >> > >> > On Dec 4, 2014, at 5:17 AM, Georgios Karagiannis > >> <georgios.karagiannis@huawei.com> wrote: > >> > > >> > Hi all, > >> > > >> > Please note that I was reviewing the SFC architecture draft, see > >>below, and > >> I have a question: > >> > http://www.ietf.org/id/draft-ietf-sfc-architecture-02.txt > >> > > >> > > >> > Can you please let me know if the current version of the SFC > >> > architecture allows the use of different Service Function Chaining > >>Header > >> formats? > >> > > >> > These formats and their analysis can be found in Section 5 of the > >>following > >> draft: > >> > > >> > http://www.ietf.org/id/draft-boucadair-sfc-design-analysis-03.txt > >> > > >> > > >> > If that is not the case, please elaborate why. > >> > > >> > Best regards, > >> > Georgios > >> > > >> > > >> > _______________________________________________ > >> > sfc mailing list > >> > sfc@ietf.org > >> > https://www.ietf.org/mailman/listinfo/sfc > >
- [sfc] is current SFC architecture supporting diff… Georgios Karagiannis
- Re: [sfc] is current SFC architecture supporting … Carlos Pignataro (cpignata)
- Re: [sfc] is current SFC architecture supporting … Georgios Karagiannis
- Re: [sfc] is current SFC architecture supporting … Carlos Pignataro (cpignata)
- Re: [sfc] is current SFC architecture supporting … Georgios Karagiannis
- Re: [sfc] is current SFC architecture supporting … Carlos Pignataro (cpignata)
- Re: [sfc] is current SFC architecture supporting … Joel M. Halpern
- Re: [sfc] is current SFC architecture supporting … Georgios Karagiannis
- Re: [sfc] is current SFC architecture supporting … Georgios Karagiannis
- Re: [sfc] is current SFC architecture supporting … Joel M. Halpern
- Re: [sfc] is current SFC architecture supporting … Carlos Pignataro (cpignata)
- Re: [sfc] is current SFC architecture supporting … Georgios Karagiannis