[mpls] New Liaison Statement, "LS101 - Use of MIP and MEP for fault isolation (ref # 011.01)"
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[mpls] New Liaison Statement, "LS101 - Use of MIP and MEP for fault isolation (ref # 011.01)"
- To: swallow at cisco.com,loa at pi.nu
- Subject: [mpls] New Liaison Statement, "LS101 - Use of MIP and MEP for fault isolation (ref # 011.01)"
- From: Greg Jones(ITU-T SG 15) <tsbsg15 at itu.int>
- Date: Tue, 27 Oct 2009 15:59:15 -0700 (PDT)
- Cc: mpls at ietf.org, hiroshi.ota at itu.int, greg.jones at itu.int, malcolm.betts at huawei.com, yoichi.maeda at ntt-at.co.jp, paf at cisco.com, adrian.farrel at huawei.com, rcallon at juniper.net, tsbsg15 at itu.int
- Delivered-to: mpls at core3.amsl.com
- List-archive: <http://www.ietf.org/mail-archive/web/mpls>
- List-help: <mailto:mpls-request@ietf.org?subject=help>
- List-id: Multi-Protocol Label Switching WG <mpls.ietf.org>
- List-post: <mailto:mpls@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
- Reply-to: tsbsg15 at itu.int
Title: LS101 - Use of MIP and MEP for fault isolation (ref # 011.01)
Submission Date: 2009-10-27
URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=607
Please reply by 2009-12-31
From: Greg Jones(ITU-T SG 15) <tsbsg15 at itu.int>
To: IETF mpls Working Group(swallow at cisco.com,loa at pi.nu)
Cc: paf at cisco.com
adrian.farrel at huawei.com
rcallon at juniper.net
mpls at ietf.org
yoichi.maeda at ntt-at.co.jp
sjtrowbridge at alcatel-lucent.com
Reponse Contact: tsbsg15 at itu.int
greg.jones at itu.int
hiroshi.ota at itu.int
Technical Contact: malcolm.betts at huawei.com
Purpose: For comment
Body:
Attachment(s):
LS101 - Use of MIP and MEP for fault isolation (ref # 011.01) - pdf (https://datatracker.ietf.org/documents/LIAISON/file724.pdf)
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.