Re: [mpls-tp] New Liaison Statement, "Response to MPLS-TP OAM Analysis draft review (ref # 041.03)"
Adrian Farrel <Adrian.Farrel@huawei.com> Wed, 01 December 2010 17:23 UTC
Return-Path: <Adrian.Farrel@huawei.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 7DC1E3A6C55; Wed, 1 Dec 2010 09:23:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.835
X-Spam-Level:
X-Spam-Status: No, score=-104.835 tagged_above=-999 required=5 tests=[AWL=1.218,
BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4,
SARE_SUB_ENC_UTF8x2=0.246, USER_IN_WHITELIST=-100]
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 qet4SMP9tl5a;
Wed, 1 Dec 2010 09:23:50 -0800 (PST)
Received: from usaga03-in.huawei.com (usaga03-in.huawei.com [206.16.17.220])
by core3.amsl.com (Postfix) with ESMTP id A1F583A6B48;
Wed, 1 Dec 2010 09:23:50 -0800 (PST)
Received: from huawei.com (usaga03-in [172.18.4.17]) by usaga03-in.huawei.com
(iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id
<0LCR00F2MF1RVT@usaga03-in.huawei.com>; Wed, 01 Dec 2010 11:25:04 -0600 (CST)
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com
[81.140.15.32]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix
2.14 (built Aug 8 2006)) with ESMTPA id
<0LCR0074OF1PXA@usaga03-in.huawei.com>; Wed, 01 Dec 2010 11:25:03 -0600 (CST)
Date: Wed, 01 Dec 2010 17:25:04 +0000
From: Adrian Farrel <Adrian.Farrel@huawei.com>
To: "'t.petch'" <ietfc@btconnect.com>, loa.andersson@ericsson.com,
greg.jones@itu.int
Message-id: <067c01cb917c$b28d0670$17a71350$@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Outlook 14.0
Content-type: text/plain; charset=utf-8
Content-language: en-gb
Content-transfer-encoding: 7BIT
Thread-index: AcuRfK+j0DiUkvliQr+4pjH4SAwHCg==
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] =?utf-8?q?New_Liaison_Statement=2C_=22Response_to_?=
=?utf-8?q?=C2=93MPLS-TP_OAM_Analysis_draft__________review=C2=94_?=
=?utf-8?b?KHJlZiAjIDA0MS4wMyki?=
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian.Farrel@huawei.com
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, 01 Dec 2010 17:23:51 -0000
Hi Tom, > nor can I find > any reference to such a liaison on the lists, nor does the e-mail appear to > contain any data, nor can I find the liaison itself. Given the uselessness of > that part of the IETF web site, this last is no surprise, but I would expect to > have seen something on both lists. All liaison statements to and from the IETF can be found at https://datatracker.ietf.org/liaison/ MPLS-TP liaison statements have a tacking number (e.g. ref # 041.03). So you can search. For example, searching for "041" finds all four liaisons in the sequence: https://datatracker.ietf.org/liaison/962/ https://datatracker.ietf.org/liaison/967/ https://datatracker.ietf.org/documents/LIAISON/file1144.pdf https://datatracker.ietf.org/liaison/977/ Cheers, Adrian
- Re: [mpls-tp] New Liaison Statement, "Response to… Adrian Farrel