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

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

Return-Path: <dk@danielking.net>
X-Original-To: time@ietfa.amsl.com
Delivered-To: time@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83DCD1A0A9D for <time@ietfa.amsl.com>; Sun, 6 Jul 2014 13:41:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] 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 9V4a8LiXc5cU for <time@ietfa.amsl.com>; Sun, 6 Jul 2014 13:41:46 -0700 (PDT)
Received: from mail-lb0-f176.google.com (mail-lb0-f176.google.com [209.85.217.176]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2CAB1A0A9C for <time@ietf.org>; Sun, 6 Jul 2014 13:41:45 -0700 (PDT)
Received: by mail-lb0-f176.google.com with SMTP id w7so2248191lbi.7 for <time@ietf.org>; Sun, 06 Jul 2014 13:41:44 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:date:message-id:subject:from :to:cc:content-type; bh=5is5e03oUIj6zqd4o3JE2g6Uv6iP3gnFiKc2z4veL+U=; b=ZWPGvXN3/2Ok97KG8aE6b8sjpmiUxJuaaXpsBpdaNuxftkDXDlFt4HwTB+218apMQe RhlEwxd7e+Sxwh7O0NhlKGNmWENtRXz4nvfDhb3cY74vzOI9aMx6yiTise6ezEElesHA Yr7ZMS5gdpPYSUB3BKeB6wFHpfRsUF0g0uJfnsV20xTGgZqDemgqOlh2ebNsClP3Djc8 p8p/zRFp6an/PPfuyJYSBMwuM2uCDWtuiKByp2BcTPgC2rSSHn54eAfeMo/FnSBIgy6x DjUkll40X7z+vkQoD0Ta/BQvPJRVztxc/DDe/Xt+EY9z1Xi9yEiZbZkVoz6GGihwLrXh fJtg==
X-Gm-Message-State: ALoCoQmU8uUV0270vykLEXdXaFMHRl/EuxMA5+whhLTun2H64E6dfyRwYlG+sq4aayNd0ImLuYBm
MIME-Version: 1.0
X-Received: by 10.152.9.234 with SMTP id d10mr3379000lab.56.1404679303897; Sun, 06 Jul 2014 13:41:43 -0700 (PDT)
Sender: dk@danielking.net
Received: by 10.114.95.102 with HTTP; Sun, 6 Jul 2014 13:41:43 -0700 (PDT)
Date: Sun, 6 Jul 2014 21:41:43 +0100
X-Google-Sender-Auth: dinjzCtzw-9nM0lk2XIuesMP9dM
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
X-BeenThere: time@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Transport Independent OAM in Multi-Layer network Entity \(TIME\) discussion list." <time.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/time>, <mailto:time-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/time/>
List-Post: <mailto:time@ietf.org>
List-Help: <mailto:time-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/time>, <mailto:time-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jul 2014 20:41:47 -0000

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