Re: [Time] TIME PS and Use Case drafts uploaded

Daniel King <daniel@olddog.co.uk> Sun, 06 July 2014 20:41 UTC

MIME-Version: 1.0
Sender: dk@danielking.net
Date: Sun, 06 Jul 2014 21:41:43 +0100
Message-ID: <CAHVZfQjTLvNz5vD=KdNZPj4d6TBgE=dbsLu2foFL7-8ocCwwPA@mail.gmail.com>
From: Daniel King <daniel@olddog.co.uk>
To: mishael.wexler@huawei.com
Content-Type: text/plain; charset="ISO-8859-1"
Archived-At: http://mailarchive.ietf.org/arch/msg/time/7wHQNLZJHKsAOpIlbuz9W0oTnns
Cc: time@ietf.org
Subject: Re: [Time] TIME PS and Use Case drafts uploaded
Precedence: list

Hi Mishael,

Thanks for the suggestion and clear ASCII art example. You make a very valid
point, and something we surmised previously in the early discussions of
TIME, end-to-end services are often built using multiple layers and/or
domains.

The recently updated Use Case I-D
(http://tools.ietf.org/html/draft-king-opsawg-time-multi-layer-oam-use-case-
01 has two updates related to your comment:

- End to End IP service carrier across two domains, one is IP/MPLS, the
second is Ethernet/MPLS.
- Service Function Chaining example, requiring continuation of OAM functions
across SFC domains, independent of the stitching technology.

We will also need to discuss the SFC case in more detail as there is an OAM
abstraction objective (capabilities, in-service status, and
troubleshooting), so that the management system may operate SFC-based
services that traverse multiple technologies.

Br, Dan.

> On Mon, Jun 30, 2014 at 2:33 PM, Mishael
> Wexler <mishael.wexler@huawei.com> wrote:
>
> Hello Daniel/Qin,
>
> Greetings for the new use-case document.
> I would like to raise another important use-case which is actually a
> combination of two cases described in the draft.
>
> In a given network when looking end2end you will have at least one IP/MPLS
> domain and one SFC domain.
> The following use-case figure may help understanding this (sorry for the
> simple graphic J).
> The overall service is provides from the CE device to the other "end" of the
> network traversing several domains/segments.
>
> It is beneficial to be able to see the service as a whole from an OAM
> perspective and maintain the end to end chain.
> This is of course in addition to the OAM for each segment, done
> independently.
>
> IMO, we should think how to integrate the two parts or at least convey some
> information from segment to segment.
>
> Mishael
>
> ============================================================================
> ==============================================
>
> 2.4.  IP/MPLS OAM combined with L4-L7 OAM
>
> <---------------------------------------------------------------------------
> End to End Service
> ----------------------------------------------------------------------------
> -------------->
> <----------------------------------------IP/MPLS
> domain------------------------------------->
> <----------------------------------------SFC
> domain--------------------------------->
>
> From: Time [mailto:time-bounces@ietf.org] On Behalf Of Qin Wu
> Sent: Monday, June 30, 2014 11:22 AM
> To: time@ietf.org; opsawg@ietf.org
> Subject: [Time] TIME PS and Use Case drafts uploaded
>
> Hi, Folks:
> The new version of TIME PS and Use case drafts have been uploaded:
> http://tools.ietf.org/html/draft-ww-opsawg-multi-layer-oam-01.txt
> http://www.ietf.org/id/draft-king-opsawg-time-multi-layer-oam-use-case-00.tx
> t
>
> Your comments/inputs/feedback are welcome!
>
> Regards!
> -Qin
>
>

[Time] TIME PS and Use Case drafts uploaded Qin Wu
Re: [Time] TIME PS and Use Case drafts uploaded Mishael Wexler
Re: [Time] TIME PS and Use Case drafts uploaded Daniel King
Re: [Time] TIME PS and Use Case drafts uploaded LUIS MIGUEL CONTRERAS MURILLO