BFD Technical Issues + Delay + T-MPLS OAM
"O'Connor, Don" <don.oconnor@us.fujitsu.com> Tue, 08 January 2008 17:17 UTC
Return-path: <rtg-bfd-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCI4T-0008TD-69; Tue, 08 Jan 2008 12:17:01 -0500
Received: from rtg-bfd by megatron.ietf.org with local (Exim 4.43) id 1JCI4S-0008T4-Mm for rtg-bfd-confirm+ok@megatron.ietf.org; Tue, 08 Jan 2008 12:17:00 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCI4S-0008SC-AI for rtg-bfd@ietf.org; Tue, 08 Jan 2008 12:17:00 -0500
Received: from fncnmp04.fnc.fujitsu.com ([168.127.0.57]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JCI4R-0000MG-Kk for rtg-bfd@ietf.org; Tue, 08 Jan 2008 12:17:00 -0500
X-IronPort-AV: E=Sophos;i="4.24,258,1196661600"; d="scan'208,217";a="190385266"
Received: from rchemx01.fnc.net.local ([168.127.134.104]) by fncnmp02.fnc.fujitsu.com with ESMTP; 08 Jan 2008 11:16:49 -0600
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8521A.3F431A0D"
Date: Tue, 08 Jan 2008 11:16:45 -0600
Message-ID: <CFAF69249417904498E67ACE8E7466E10483E9FB@rchemx01.fnc.net.local>
In-Reply-To: <64122293A6365B4A9794DC5636F9ACFD0252E22C@ilptex01.ecitele.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: BFD Technical Issues + Delay + T-MPLS OAM
Thread-Index: AchGRWJTSg9Tp6rsQYSoOWe3rMC00wL0V0Mw
References: <64122293A6365B4A9794DC5636F9ACFD0252E22C@ilptex01.ecitele.com>
From: "O'Connor, Don" <don.oconnor@us.fujitsu.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, dward@cisco.com, jhaas@prfc.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ba9b8496764663b12c333825fbf6b3d
Cc: rcallon@juniper.net, rtg-bfd@ietf.org, Alik Shimelmits <Alik.Shimelmits@ecitele.com>
Subject: BFD Technical Issues + Delay + T-MPLS OAM
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
Errors-To: rtg-bfd-bounces@ietf.org
Dave, Jeffrey, Ross, and all What are the unresolved technical issues with BFD that are resulting in such a long delay in progressing the drafts and holding meetings? Can you please socialize these issues with the email list so that everybody is aware of the issues in detail? I see a lot of effort being devoted to T-MPLS OAM. What about finishing BFD? Regards Don ________________________________ From: Alexander Vainshtein [mailto:Alexander.Vainshtein@ecitele.com] Sent: Monday, December 24, 2007 9:55 AM To: dward@cisco.com; jhaas@prfc.org Cc: rtg-bfd@ietf.org; Alik Shimelmits Subject: What is the status of the WG documents? Dave, Jeffrey and all, I have missed the Vancouver IETF meeting, and I would like to know what happens to the WG drafts. At the Prague meeting they have been declared as ready for the WG LC, but, AFAIK, it has never been declared. And most of the drafts have now expired. Any info will be highly appreciated. Regards, Sasha Vainshtein
- What is the status of the WG documents? Alexander Vainshtein
- BFD Technical Issues + Delay + T-MPLS OAM O'Connor, Don