[mpls] unresolved technical concerns
D'Alessandro Alessandro Gerardo <alessandro.dalessandro@telecomitalia.it> Wed, 05 October 2011 16:51 UTC
Return-Path: <alessandro.dalessandro@telecomitalia.it>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7392311E8094; Wed, 5 Oct 2011 09:51:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.384
X-Spam-Level:
X-Spam-Status: No, score=-0.384 tagged_above=-999 required=5 tests=[AWL=0.335, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0VDxTuUlkaOG; Wed, 5 Oct 2011 09:51:17 -0700 (PDT)
Received: from GRFEDG701RM001.telecomitalia.it (grfedg701rm001.telecomitalia.it [217.169.121.20]) by ietfa.amsl.com (Postfix) with ESMTP id 6536F11E809D; Wed, 5 Oct 2011 09:51:10 -0700 (PDT)
Received: from grfhub703rm001.griffon.local (10.19.3.10) by GRFEDG701RM001.telecomitalia.it (10.173.88.20) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 5 Oct 2011 18:54:17 +0200
Received: from GRFMBX702RM001.griffon.local ([10.19.3.20]) by grfhub703rm001.griffon.local ([10.19.9.236]) with mapi; Wed, 5 Oct 2011 18:54:17 +0200
From: D'Alessandro Alessandro Gerardo <alessandro.dalessandro@telecomitalia.it>
To: "stbryant@cisco.com" <stbryant@cisco.com>, "Alexander.Vainshtein@ecitele.com" <Alexander.Vainshtein@ecitele.com>
Date: Wed, 05 Oct 2011 18:54:16 +0200
Thread-Topic: unresolved technical concerns
Thread-Index: AcyDftrXxysabIfuTL2UhQPyTTWf/w==
Message-ID: <A1F769BC58A8B146B2EEA818EAE052A2096E4C310C@GRFMBX702RM001.griffon.local>
Accept-Language: en-US
Content-Language: it-IT
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: "ietf@ietf.org" <ietf@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Subject: [mpls] unresolved technical concerns
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2011 16:51:17 -0000
Dear Stewart, Dear Sasha, I think there are already enough contributions in that direction I (with many other experts) contributed to in the form of IETF mailing list discussion and ITU-T liaisons. Unfortunately I regret to say that some questions for clarification and concerns risen in those emails (for sure some of mine) still remain without an answer. At the same time, some comments provided by ITU-T liaisons still remain unresolved. Best regards, Alessandro ------------------------------------------------------------------ Telecom Italia Alessandro D'Alessandro Transport Innovation Via Reiss Romoli, 274 - 10148 Torino phone: +39 011 228 5887 mobile: +39 335 766 9607 fax: +39 06 418 639 07 -----Messaggio originale----- Da: Stewart Bryant [mailto:stbryant@cisco.com] Inviato: mercoledì 5 ottobre 2011 12:24 A: D'Alessandro Alessandro Gerardo Cc: adrian@olddog.co.uk; mpls@ietf.org; ietf@ietf.org Oggetto: Re: [mpls] R: FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC On 05/10/2011 10:38, D'Alessandro Alessandro Gerardo wrote: > major unresolved technical concerns Alessandro Please can I suggest that you write an internet draft detailing these "major unresolved technical concerns" so that we can all understand them. Such a draft needs to be technical, and describe the actions that the network operator is unable to perform, or the fault cases that they are unable to diagnose using the OAM defined in the IETF RFCs, or late stage WG drafts. Alternatively if you are referring to a bug in the MPLS-TP OAM protocols, you need to tell the community what it is. I believe that this request has been made a number of times, in various forums, and, as far as I know, no document has yet been produced. An argument of the form "you must standardize what I want" will not fly. What is needed is a very clear technical definition of the issue(s). When we have the "major unresolved technical concerns" on the table, we will be in a position to determine the best disposition of those issues. Stewart -- For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/index.html 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.
- [mpls] unresolved technical concerns D'Alessandro Alessandro Gerardo
- Re: [mpls] unresolved technical concerns Alexander Vainshtein
- Re: [mpls] unresolved technical concerns Luyuan Fang (lufang)
- Re: [mpls] unresolved technical concerns John E Drake