From rtg-bfd-bounces@ietf.org Wed May 02 18:19:53 2007
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 1HjNAs-0000Ny-QU; Wed, 02 May 2007 18:19:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HjNAr-0000Nt-Ka
	for rtg-bfd@ietf.org; Wed, 02 May 2007 18:19:49 -0400
Received: from fncnmp03.fnc.fujitsu.com ([168.127.0.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HjNAq-0006hu-9f
	for rtg-bfd@ietf.org; Wed, 02 May 2007 18:19:49 -0400
Received: from rchemx01.fnc.net.local ([168.127.134.104])
	by fncnmp01.fnc.fujitsu.com with ESMTP; 02 May 2007 17:19:42 -0500
X-IronPort-AV: i="4.14,482,1170655200"; 
	d="scan'208,217"; a="126591105:sNHT41188848"
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C78D07.FBD91175"
Date: Wed, 2 May 2007 17:19:43 -0500
Message-ID: <CFAF69249417904498E67ACE8E7466E10324BBE4@rchemx01.fnc.net.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Use and Definition of Path Down Diagnostic Code
Thread-Index: AceNB/vMrLrlcyK6S5eiz0/ciBTm/w==
From: "O'Connor, Don" <don.oconnor@us.fujitsu.com>
To: <dward@cisco.com>,
	<rtg-bfd@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Cc: 
Subject: Use and Definition of Path Down Diagnostic Code
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

This is a multi-part message in MIME format.

------_=_NextPart_001_01C78D07.FBD91175
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dave

I have a question of clarification on the use and definition of the Path =
Down Diagnostic Code

Is this code only used for the case of

"If signaling is received from outside BFD that the underlying path has =
failed, an implementation MAY administratively disable the session with =
the diagnostic Path Down."

The definition of Concatenated Path Down=20

"Concatenated Path Down and Reverse Concatenated Path Down.  The first =
propagates forward path failures (in which the concatenated path fails =
in the direction toward the interworking system)

implies that Concatenated Path Down is a unidirectional failure =
indication.

So is Path Down also a unidirectional failure indication? More =
specifically does receipt of a Path Down diagnostic code indicate that =
the underlying path has failed in the same direction as the received =
Path Down Diagnostic Code ?

It may be useful to add some additional clarification of the use and =
definition of Path Down to the next draft of bfd-base

Regards

Don



------_=_NextPart_001_01C78D07.FBD91175
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7234.20">
<TITLE>Use and Definition of Path Down Diagnostic Code</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">Dave</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I have a question of clarification on =
the use and definition of the Path Down Diagnostic Code</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Is this code only used for the case =
of</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&quot;If signaling is received from =
outside BFD that the underlying path has failed, an implementation MAY =
administratively disable the session with the diagnostic Path =
Down.&quot;</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The definition of Concatenated Path =
Down </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&quot;Concatenated Path Down and =
Reverse Concatenated Path Down.&nbsp; The first propagates forward path =
failures (in which the concatenated path fails in the direction toward =
the interworking system)</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">implies that Concatenated Path Down is =
a unidirectional failure indication.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">So is Path Down also a unidirectional =
failure indication? More specifically does receipt of a Path Down =
diagnostic code indicate that the underlying path has failed in the same =
direction as the received Path Down Diagnostic Code ?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">It may be useful to add some additional =
clarification of the use and definition of Path Down to the next draft =
of bfd-base</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Regards</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Don</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C78D07.FBD91175--




