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


Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 52B091A0AB7 for <>; Sun, 6 Jul 2014 15:05:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id DRCWK2WRt3XB for <>; Sun, 6 Jul 2014 15:05:08 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A678E1A0AB4 for <>; Sun, 6 Jul 2014 15:05:07 -0700 (PDT)
Received: from (unknown []) by IMSVA (Postfix) with ESMTP id 7D2282D0221; Mon, 7 Jul 2014 00:05:03 +0200 (CEST)
Received: from (unknown []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 63DC52D021F; Mon, 7 Jul 2014 00:05:03 +0200 (CEST)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Mon, 7 Jul 2014 00:05:02 +0200
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.974.11; Sun, 6 Jul 2014 22:05:01 +0000
Received: from ([]) by ([]) with mapi id 15.00.0974.002; Sun, 6 Jul 2014 22:05:01 +0000
To: Daniel King <>, "" <>
Thread-Topic: [Time] TIME PS and Use Case drafts uploaded
Thread-Index: AQHPmVrNIp0kXVCfsEGGSLRuY+vSDpuTmfNO
Date: Sun, 6 Jul 2014 22:05:00 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: es-ES, en-US
Content-Language: es-ES
x-originating-ip: [::]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:
x-forefront-prvs: 0264FEA5C3
x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(377454003)(24454002)(51704005)(189002)(199002)(15975445006)(31966008)(101416001)(2656002)(15202345003)(85852003)(81342001)(33646001)(95246002)(86362001)(92566001)(83322001)(85306003)(95666004)(21056001)(74662001)(106356001)(46102001)(76482001)(74502001)(77982001)(63666003)(54356999)(50986999)(106116001)(105586002)(19580395003)(80022001)(92726001)(107046002)(19580405001)(87936001)(83072002)(64706001)(99396002)(20776003)(4396001)(81542001)(79102001)(76176999)(3826002); DIR:OUT; SFP:; SCL:1; SRVR:DB4PR06MB574;; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; LANG:en;
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "" <>
Subject: Re: [Time] TIME PS and Use Case drafts uploaded
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Transport Independent OAM in Multi-Layer network Entity \(TIME\) discussion list." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 06 Jul 2014 22:05:11 -0000

Daniel King <> wrote:

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

The recently updated Use Case I-D
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 <> 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 [] On Behalf Of Qin Wu
> Sent: Monday, June 30, 2014 11:22 AM
> To:;
> Subject: [Time] TIME PS and Use Case drafts uploaded
> Hi, Folks:
> The new version of TIME PS and Use case drafts have been uploaded:
> t
> Your comments/inputs/feedback are welcome!
> Regards!
> -Qin

Time mailing list


Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição