Return-Path: <lavanya.srivatsa@aricent.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix)
 with ESMTP id 72D443A6A0F for <mpls@core3.amsl.com>;
 Thu, 26 Aug 2010 04:08:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.281
X-Spam-Level: 
X-Spam-Status: No, score=-1.281 tagged_above=-999 required=5 tests=[AWL=0.119,
 BAYES_00=-2.599, J_CHICKENPOX_52=0.6, J_CHICKENPOX_54=0.6]
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 MoondRx8DEPG for
 <mpls@core3.amsl.com>; Thu, 26 Aug 2010 04:08:43 -0700 (PDT)
Received: from jaguar.aricent.com (jaguar.aricent.com [121.241.96.11]) by
 core3.amsl.com (Postfix) with ESMTP id ED9ED3A6890 for <mpls@ietf.org>;
 Thu, 26 Aug 2010 04:08:42 -0700 (PDT)
Received: from jaguar.aricent.com (localhost [127.0.0.1]) by postfix.imss71
 (Postfix) with ESMTP id B81B036B8E; Thu, 26 Aug 2010 16:38:10 +0530 (IST)
Received: from GUREXHT01.ASIAN.AD.ARICENT.COM (gurexht01.asian.ad.aricent.com
 [10.203.171.136]) by jaguar.aricent.com (Postfix) with ESMTP id A12AF36B78;
 Thu, 26 Aug 2010 16:38:10 +0530 (IST)
Received: from GUREXMB02.ASIAN.AD.ARICENT.COM ([10.203.171.134]) by
 GUREXHT01.ASIAN.AD.ARICENT.COM ([10.203.171.137]) with mapi;
 Thu, 26 Aug 2010 16:39:07 +0530
From: Lavanya Srivatsa <lavanya.srivatsa@aricent.com>
To: rtg-bfd <rtg-bfd@ietf.org>, "dkatz@juniper.net" <dkatz@juniper.net>
Date: Thu, 26 Aug 2010 16:39:06 +0530
Thread-Topic: [mpls] BFD Packet Flow
Thread-Index: AQHLRQ8ZnBNBzNxqt0GWbAIBApyFDQ==
Message-ID: <E13C8C03049AFA4E9CEE5A21D3E7F85D1463DC@GUREXMB02.ASIAN.AD.ARICENT.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>,
 "gupta_rakesh62@yahoo.co.in" <gupta_rakesh62@yahoo.co.in>
Subject: Re: [mpls] BFD Packet Flow
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 26 Aug 2010 11:08:44 -0000

Dave,

Thanks for the earlier response about the so-called 4-way handshake. I got =
what you are trying to say...

I had a question on the below though:
>> In some sense the question is meaningless;  the active and passive roles=
 are really a way of describing the way the protocol behaves in a larger co=
ntext.  In the >> LSP context, LSR-Z is by definition in the active role be=
cause it must send the first BFD packet.

If so, does this mean that BFD-MPLS is applicable only in the Active-Active=
 scenario i.e. both LSR-A and LSR-Z in Active roles? The reason I am saying=
 this is one would expect LSR-A to be playing the Active role because LSR-A=
 is the **head-end of the forward unidirectional path** that is being monit=
ored in case of an unidirectional MPLS path. Now if LSR-Z is also required =
to be in Active state because it sends the first BFD packet, then this woul=
d imply that only Active-Active scenario is applicable for BFD-MPLS, right?

The BFD-MPLS RFC also goes on to say that the node receiving a LSP Ping req=
uest MUST send a BFD control packet and MAY send an LSP Ping response.
Does this imply the Active-Passive scenario for BFD-MPLS (i.e. LSR-A in Act=
ive role and LSR-Z in Passive role)?

In the sense, if LSR-Z is Active, upon receiving an LSP Ping request, LSR-Z=
 will respond with a BFD control packet.
If LSR-Z is Passive, upon receiving an LSP Ping request, LSR-Z will *not* s=
end a BFD control packet but will respond with an LSP Ping response (carryi=
ng LSR-Z's discriminator) instead.

Is my understanding correct? If so, the text in the RFC seems to slightly m=
islead with the "MAY" clause for the LSP Ping response.

- Lavanya


Date: Sat, 21 Aug 2010 12:45:09 -0700
From: Dave Katz <dkatz@juniper.net>
Subject: Re: [mpls] BFD Packet Flow
To: "Weingarten, Yaacov (NSN - IL/Hod HaSharon)"
        <yaacov.weingarten@nsn.com>
Cc: mpls@ietf.org, rtg-bfd@ietf.org, RAKESH GUPTA
        <gupta_rakesh62@yahoo.co.in>
Message-ID: <6F1E904F-CF1B-49B2-B8B7-088EA91CC661@juniper.net>
Content-Type: text/plain; charset=3D"windows-1252"


On Aug 19, 2010, at 2:08 AM, Weingarten, Yaacov (NSN - IL/Hod HaSharon) wro=
te:

> Hi,
>
> Just to verify that I understand the flow of messages and the state of th=
e BFD Session ? is the following flow correct ?
>
> Assume a LSP between LSR-A and LSR-Z ?
> 1. Both LSRs initialize the BFD Session and set the state to Down
> 2. LSR-A (the ingress LSR) sends a LSP-Ping (with the Discriminator TLV) =
to LSR-Z ? both sessions still in Down state.
> 3. LSR-Z receives the LSP-Ping, and (assuming that LSR-Z is in Active mod=
e) sends a BFD Control Packet with its own Discriminator, the Discriminator=
 received from the LSP-Ping, and State=3DDown to LSR-A, both session still =
in Down State.
> 4. LSR-A receives the BFD Control and switches to Init state (as per RFC5=
880), and sends a BFD Control Packet with State=3DInit to LSR-Z
> 5. LSR-Z receives the BFD Control and switches to Up state, and sends a B=
FD Control Packet with State=3DUp to LSR-A
> 6. LSR-A receives the BFD Control and switches to UP state
>
> Additional question ? regarding step 3 above ? must LSR-Z be in Active mo=
de? What happens if LSR-Z is in Passive mode and LSR-A is in Active mode?

In some sense the question is meaningless;  the active and passive roles ar=
e really a way of describing the way the protocol behaves in a larger conte=
xt.  In the LSP context, LSR-Z is by definition in the active role because =
it must send the first BFD packet.

--Dave

"DISCLAIMER: This message is proprietary to Aricent and is intended solely =
for the use of the individual to whom it is addressed. It may contain privi=
leged or confidential information and should not be circulated or used for =
any purpose other than for what it is intended. If you have received this m=
essage in error, please notify the originator immediately. If you are not t=
he intended recipient, you are notified that you are strictly prohibited fr=
om using, copying, altering, or disclosing the contents of this message. Ar=
icent accepts no responsibility for loss or damage arising from the use of =
the information transmitted by this email including damage from virus."
