Re: [mpls-tp] Questions on the MPLS-TP CV drafts
"Annamaria Fulignoli" <annamaria.fulignoli@ericsson.com> Wed, 08 July 2009 06:42 UTC
Return-Path: <annamaria.fulignoli@ericsson.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E86F13A6D1F for <mpls-tp@core3.amsl.com>; Tue, 7 Jul 2009 23:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.052
X-Spam-Level:
X-Spam-Status: No, score=-6.052 tagged_above=-999 required=5 tests=[AWL=0.197, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id heFWbReEf1Jk for <mpls-tp@core3.amsl.com>; Tue, 7 Jul 2009 23:42:17 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 79B8C3A69A3 for <mpls-tp@ietf.org>; Tue, 7 Jul 2009 23:42:16 -0700 (PDT)
X-AuditID: c1b4fb3c-b7c04ae0000036a1-40-4a543fdf6fa2
Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw3.ericsson.se (Symantec Mail Security) with SMTP id B0.32.13985.FDF345A4; Wed, 8 Jul 2009 08:42:39 +0200 (CEST)
Received: from esealmw118.eemea.ericsson.se ([153.88.200.77]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 8 Jul 2009 08:41:14 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 08 Jul 2009 08:41:12 +0200
Message-ID: <93DFCD4B101EB440B5B72997456C5F9403FC1AB0@esealmw118.eemea.ericsson.se>
In-Reply-To: <4A534C9A.2090709@hitachi.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [mpls-tp] Questions on the MPLS-TP CV drafts
Thread-Index: Acn/Bi+/1eKO4vdnQ5KgesjHyyP3ugAkA6Qg
References: <4A534C9A.2090709@hitachi.com>
From: Annamaria Fulignoli <annamaria.fulignoli@ericsson.com>
To: Masahiko Mizutani <masahiko.mizutani.ew@hitachi.com>, mpls-tp@ietf.org
X-OriginalArrivalTime: 08 Jul 2009 06:41:14.0505 (UTC) FILETIME=[16D62F90:01C9FF97]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [mpls-tp] Questions on the MPLS-TP CV drafts
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jul 2009 06:42:18 -0000
Hi Masahiko, for better understanding MPLS-TP OAM required functionalities , you have to refer to http://tools.ietf.org/html/draft-ietf-mpls-tp-oam-requirements-02; this document is in last call. For better understanding MPLS-TP OAM procedures that satisfy the MPLS-TP OAM requirements please refer to http://tools.ietf.org/html/draft-ietf-mpls-tp-oam-framework-00; If you wish more clarification or disagree with some MPLS-TP OAM requirements and/or procedures, you should address your comments to these documents respectively. About the MPLS-TP OAM solutions at the moment there are several drafts as individual contribution. I can answer for the draft-fhbs-mpls-tp-cv-proactive-00 that you mentioned; the editors of this draft has analysed and proposed possible solutions ( Not the solution !) for the tool that satisfies the CC-CV proactive functionality ; the procedure and behaviour of the proactive cc-cv functionality is described in the draft-ietf-mpls-tp-oam-framework-00 as even clearly reported in the draft draft-fhbs-mpls-tp-cv-proactive-00 itself. The difference between CC and CV: - Continuity Check monitors the integrity of the continuity of the path; Loss of Continuity is the triggered defect. - Connectivity Verification monitors the integrity of the routing of the path between sink and source. The connectivity is supervised by attaching a unique identifier at the source. If the received identifier does not match this expected identifier, a connectivity defect occurs. Best Regards, Annamaria -----Original Message----- From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf Of Masahiko Mizutani Sent: martedì 7 luglio 2009 15.25 To: mpls-tp@ietf.org Subject: [mpls-tp] Questions on the MPLS-TP CV drafts Dear All, I'm looking at CV definition for MPLS-TP in both two individual drafts (Internet Draft within MEAD team purview) and have questions on these docs. - draft-fhbs-mpls-tp-cv-proactive-00 - draft-boutros-mpls-tp-cv-01 ** These documents specify different functionality and different frame structure for MPLS-TP CV. I think we need to have common understandings and need to discuss how to specify this particular function. Firstly, I have two questions. Why we need two different CV functions that are used proactively and used in normal operation? In my understanding, CV must be configured proactively if we need to use it. Is there any reasons for the separation? I'd like to know the difference between CC and CV. Also, I don't understand well what MPLS-OAM is. I think we don't have any consensus on using these terms. In my opinion, "MPLS-TP OAM" might be better since we focus on MPLS-Transport Profile. Best Regards, Masahiko Masahiko Mizutani Hitachi, Ltd., Telecommunication & Network Systems Division Tel: +81 45 865 7003 +81 80 6575 7704 email: masahiko.mizutani.ew@hitachi.com <mailto:masahiko.mizutani.ew@hitachi.com> _______________________________________________ mpls-tp mailing list mpls-tp@ietf.org https://www.ietf.org/mailman/listinfo/mpls-tp
- [mpls-tp] Questions on the MPLS-TP CV drafts Masahiko Mizutani
- Re: [mpls-tp] Questions on the MPLS-TP CV drafts Annamaria Fulignoli
- Re: [mpls-tp] Questions on the MPLS-TP CV drafts Masahiko Mizutani