Re: [sfc] is current SFC architecture supporting different types of SFC header formats?

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Thu, 04 December 2014 15:18 UTC

Return-Path: <cpignata@cisco.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 25CC81AD3A5 for <sfc@ietfa.amsl.com>; Thu, 4 Dec 2014 07:18:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 XawLWcP-HZsW for <sfc@ietfa.amsl.com>; Thu, 4 Dec 2014 07:18:31 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C13E21A011D for <sfc@ietf.org>; Thu, 4 Dec 2014 07:18:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6266; q=dns/txt; s=iport; t=1417706312; x=1418915912; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=OxIgRpmbWtIbqg6YVS/rdl34ysKsLQvORjsMHz3Iu88=; b=CZovkXi54l0qh9KLaYUwaSCG750Hm1EqgYw2fDxuIUHPD9cqLzYoufG4 99HRBHbBV0Kn5XOG4u0ZwPiiZe6v0OCSqqGgHwNb58Orl7HOHmBOe37v6 ZMlM/kHSrFsQZsAFWWz1KPmlgQoeyEOZL4N9Vv93bAEBb5pCrMyigB8b4 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtgIAEF6gFStJV2a/2dsb2JhbABZgmQiUlgEgwHBKYIcCoYWAhyBARYBAQEBAX2EAgEBAQMBAQEBIBE6CwUHBAIBCBEBAwEBAQICIwMCAgIlCxQBAgYIAQEEDgUJiCwJAQzAF5ZeAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4ErigOFBTMHBoJrM4EeBY4agXaKSoEjgy2LX4NpgjWBRG8BgUSBAAEBAQ
X-IronPort-AV: E=Sophos;i="5.07,516,1413244800"; d="scan'208";a="377899731"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-2.cisco.com with ESMTP; 04 Dec 2014 15:18:31 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id sB4FIT2T021391 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 4 Dec 2014 15:18:29 GMT
Received: from xmb-aln-x02.cisco.com ([fe80::8c1c:7b85:56de:ffd1]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0195.001; Thu, 4 Dec 2014 09:18:29 -0600
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Georgios Karagiannis <georgios.karagiannis@huawei.com>
Thread-Topic: [sfc] is current SFC architecture supporting different types of SFC header formats?
Thread-Index: AdAPq35dh1W/iINPRT2JdHnL8IYwVwAT290AAAxhE+D//02BAIAAC9SAgABdbAA=
Date: Thu, 04 Dec 2014 15:18:28 +0000
Message-ID: <50E2E2DA-BB2A-409A-8E46-13DEEA0B879F@cisco.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> <C5034E44CD620A44971BAAEB372655DCB291B9@LHREML516-MBX.china.huawei.com>
In-Reply-To: <C5034E44CD620A44971BAAEB372655DCB291B9@LHREML516-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [64.102.156.203]
Content-Type: text/plain; charset="utf-8"
Content-ID: <1151905DE09B9D4F88C25852BA9F2D6E@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/dLsdxSbQ5JNwZQvYA1BTGJFv7vo
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 15:18:33 -0000

Hi Georgios,

Please see inline.

> On Dec 4, 2014, at 9:40 AM, Georgios Karagiannis <georgios.karagiannis@huawei.com> wrote:
> 
> Hi Carlos,
> 
> Please note that I do not mean to use different SFC encapsulations simultaneously.
> 

Thanks for the clarification.

> 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.
> 

Yes. Again, the SFC architecture document does not concern itself or take any position on any specifics for any encapsulation format. It does specify the functions that the SFC encapsulation need to fulfill.

> 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.
> 

I see — this is a question for draft-boucadair-sfc-design-analysis and not for draft-ietf-sfc-architecture. Meaning, it would be up to the proposed encapsulation to show how they realize the functions of the architecture.

That said, I do not see an “SF Map Index” in the architecture document, for example.

Thanks,

Carlos.

> 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
>>> 
>