Re: [mpls-tp] [mpls] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a working group document

D'Alessandro Alessandro Gerardo <alessandro.dalessandro@telecomitalia.it> Wed, 30 June 2010 13:23 UTC

Return-Path: <alessandro.dalessandro@telecomitalia.it>
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 61B7628C0F0 for <mpls-tp@core3.amsl.com>; Wed, 30 Jun 2010 06:23:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.881
X-Spam-Level: *
X-Spam-Status: No, score=1.881 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
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 YCsRBvU-chtn for <mpls-tp@core3.amsl.com>; Wed, 30 Jun 2010 06:23:13 -0700 (PDT)
Received: from GRFEDG702RM001.telecomitalia.it (grfedg702rm001.telecomitalia.it [217.169.121.21]) by core3.amsl.com (Postfix) with ESMTP id A1AD73A6ABD for <mpls-tp@ietf.org>; Wed, 30 Jun 2010 06:23:07 -0700 (PDT)
Received: from GRFHUB706RM001.griffon.local (10.19.3.71) by GRFEDG702RM001.telecomitalia.it (10.173.88.21) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 30 Jun 2010 15:23:11 +0200
Received: from GRFMBX702RM001.griffon.local ([10.19.3.19]) by GRFHUB706RM001.griffon.local ([10.19.9.239]) with mapi; Wed, 30 Jun 2010 15:23:11 +0200
From: D'Alessandro Alessandro Gerardo <alessandro.dalessandro@telecomitalia.it>
To: "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Date: Wed, 30 Jun 2010 15:23:08 +0200
Thread-Topic: [mpls] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a working group document
Thread-Index: AcsROjkkGt4HNYxATriMq700tfeV4QHFTFtw
Message-ID: <A1F769BC58A8B146B2EEA818EAE052A2095FCEC029@GRFMBX702RM001.griffon.local>
References: <4C1F5616.2060406@pi.nu>
In-Reply-To: <4C1F5616.2060406@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>
Subject: Re: [mpls-tp] [mpls] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a working group document
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, 30 Jun 2010 13:23:17 -0000

No/ do not support


Technical comments:

Pinging at all transport path levels:
It's not clear if the proposed tool can be applied to all transport path levels (PW, LSP, section). It is desirable having the same tool for all transport paths
        -Section 1: LSP-Ping is an OAM mechanism for MPLS LSP
        -Section 1: this document describes extensions  ...be used for on-demand monitoring of MPLS-TP LSPs.
        -Section 2.3: The MEP/MIP identifiers ... MUST be checked for the MPLS-TP LSP path/section that is being monitored
        -Section 2.4: Identifying Statically provisioned LSPs and PWs... (but the applicability throughout the document refers to LSPs only (except a reference in section 5))
        -Section 5: The non-IP addressing based procedures specified in this document apply ONLY to MPLS-TP LSPs.  They ALSO apply to PWs when IP   encapsulation is NOT desired. (Nothing is said about Section)


Pinging a MIP:
It's not clear if the "per-interface model" is supported given the fact that MIP identifier (stated in section 2.3) is that defined in ietf-mpls-tp-identifier where it is defined at cross connection points or on a per-node base.


Option: LSP-Ping with IP encapsulation, over ACH
Could you please clarify the applicability scope of this option?


Editorial:
- the document is more related to LSP-Ping extension for MPLS than about the description of the on demand CV for MPLS-TP. TP profiling needs to be highlighted
- The "Adjacency function" should be clarified. Are the authors referring to the ability to perform next hop connectivity verification at a certain layer network?
- Section 2.1: ...receiving node should only perform mpls label control-plane/data-plane consistency checks. It's likely that this check can be performed to verify NMS configuration consistency with expected data plane forwarding
- section 3.1 the IP header is used mainly for addressing (should it be identifying?)
- Throughout the document lsp-ping ->LSP-Ping

Best regards,
Alessandro

------------------------------------------------------------------
Telecom Italia
Alessandro D'Alessandro
Transport & OPB Innovation
Via Reiss Romoli, 274 - 10148 Torino
phone:  +39 011 228 5887
mobile: +39 335 766 9607
fax: +39 06 418 639 07

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Loa Andersson
Sent: lunedì 21 giugno 2010 14.08
To: mpls-tp@ietf.org; mpls@ietf.org; MPLS-TP ad hoc team
Subject: [mpls] poll to adopt draft-nitinb-mpls-tp-on-demand-cv as a working group document


Working Group,

this email is to start poll to adopt
draft-nitinb-mpls-tp-on-demand-cv-00.txt
as an MPLS working group draft.

After recent experience, the chairs would like to remind you all
what it means to conduct a poll to adopt a draft as a working group
draft.

- Please recall that the IETF does not "vote." Polls of a working
   group are to gather information to help the chairs make their
   decisions. Voting is not part of the normal working methods of
   an IETF working group.

- The "rough consensus" process used in the working group assumes
   that people expressing opinions are also participating in the
   development of standards documents.

- Subscription to the list specifically to express an opinion is
   noticed by the chairs who has access to information on the new list
   members. Such behavior is not part of the normal working methods.

- The purpose of a poll for adoption is to help the chairs understand
   the level of support for a document (i.e. who has read it, who
   believes it is a good starting point for working group work, who
   will contribute to the work) and whether there are any significant
   technical issues. Statements of objection must be backed up by
   proper technical reasons.

So please respond to this poll indicating whether you support the
adoption of this draft or stating your technical issues.

Please also not that this draft has after a discussion with the
working group chairs been renamed, it was earlier know as
draft-nitinb-mpls-tp-lsp-ping-extensions-01.

This poll ends eob July 5.


Loa and George
mpls wg co-chairs

--


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.