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

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 04 December 2014 15:56 UTC

Return-Path: <jmh@joelhalpern.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 9CE1A1A0137 for <sfc@ietfa.amsl.com>; Thu, 4 Dec 2014 07:56:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, 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 R6B3uBipdy0n for <sfc@ietfa.amsl.com>; Thu, 4 Dec 2014 07:56:44 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64AFA1AD3AD for <sfc@ietf.org>; Thu, 4 Dec 2014 07:56:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 3B5B524028B; Thu, 4 Dec 2014 07:56:38 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-134-188.clppva.east.verizon.net [70.106.134.188]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 30FED24003E; Thu, 4 Dec 2014 07:56:37 -0800 (PST)
Message-ID: <54808433.4030509@joelhalpern.com>
Date: Thu, 04 Dec 2014 10:56:35 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Georgios Karagiannis <georgios.karagiannis@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> <C5034E44CD620A44971BAAEB372655DCB291B9@LHREML516-MBX.china.huawei.com> <50E2E2DA-BB2A-409A-8E46-13DEEA0B879F@cisco.com> <54807E75.10706@joelhalpern.com> <C5034E44CD620A44971BAAEB372655DCB2921C@LHREML516-MBX.china.huawei.com>
In-Reply-To: <C5034E44CD620A44971BAAEB372655DCB2921C@LHREML516-MBX.china.huawei.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/z4DyVgBbw8baDYSZpbrlvckeQ4Q
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:56:48 -0000

Not quite "any".  The working group made some choices about behavior as 
part of the process.  If the architecture did not make any choices, then 
there would be no point in having the architecture.  We did not however 
mandate the specific encodings, and there are a fair range of possible 
realizations.  Neither I nor Carlos attempted to review all the existing 
proposals to determine if as they exist they fit the architecture or if 
they could be adjusted to fit.  That is up to the proposers.

For example, I suppose that one could write a solution proposal that 
required co-location of certain components.  But that would then be an 
important property of the proposal to be discussed by the WG.

Yours,
Joel

On 12/4/14, 10:47 AM, Georgios Karagiannis wrote:
> Hi Joel,
>
> Thanks for your email! I understand that the SFC architecture draft
> does not specify how the required information is encoded in the
> header.
>
> Therefore, I am also assuming that (1) the SFC Encapsulation function
> described in section 4.1, (2) the Classification function described
> in section 4.7 and (3) the Shared Metadata function described in
> Section 4.9, are described in such a way that any SFC encapsulation
> technique should be supported.
>
> Best regards, Georgios
>
>
>
>> -----Original Message----- From: Joel M. Halpern
>> [mailto:jmh@joelhalpern.com] Sent: Thursday, December 04, 2014 4:32
>> PM To: Georgios Karagiannis Cc: sfc@ietf.org Subject: Re: [sfc] is
>> current SFC architecture supporting different types of SFC header
>> formats?
>>
>> To reinforce Carlos' point, the architecture document is quite
>> careful not to specify how the required information is encoded in
>> the header. It is up to the WG to select a single such
>> encapsulation that meets the requirements from among the multiple
>> choices being presented in individual drafts.
>>
>> Yours, Joel
>>
>> On 12/4/14, 10:18 AM, Carlos Pignataro (cpignata) wrote:
>>> 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
>>>>>>
>>>>
>>>
>>> _______________________________________________ sfc mailing list
>>> sfc@ietf.org https://www.ietf.org/mailman/listinfo/sfc
>>>