RE: [PWE3] question on the "independent mode" of draft-muley-dutta

Hello Yaakov :
        Please see section 5.3.1 

     d. If while waiting for the acknowledgment, the requesting endpoint
      receives a request from its peer to switchover to the same or a
      different PW path, it must perform the following:

            i. If its system IP address is higher than that of the peer,
               this endpoint ignores the request and continues to wait
               for the acknowledgement from its peer.

           ii. If its system IP address is lower than that of its peer,
               it aborts the timer and immediately starts the
               procedures of the receiving endpoint in Section 5.3.2
<http://tools.ietf.org/html/draft-muley-dutta-pwe3-redundancy-bit-02#sec
tion-5.3.2> .

I am not suer whether there will infinite flapping. Hope this helps.

Thanks,
Praveen

________________________________

From: Yaakov Stein [mailto:yaakov_s@rad.com] 
Sent: Thursday, December 27, 2007 3:39 AM
To: pwe3@ietf.org
Cc: Keren Zik-Meirom
Subject: [PWE3] question on the "independent mode" of draft-muley-dutta

Hi all (and especially co-authors of draft-muley-dutta)

Section 4.1. (Independent Mode) In
draft-muley-dutta-pwe3-redundancy-bit-02
<http://smakd.potaroo.net/ietf/idref/draft-muley-dutta-pwe3-redundancy-b
it/rfcmarkup?repository=/away/ietf&url=/away/ietf/all-ids/draft-muley-du
tta-pwe3-redundancy-bit-02.txt>  says:

   PW endpoint nodes independently select which PW they intend to make 
   active and which PWs they intend to make standby. They advertise the 
   corresponding Active/Standby forwarding state for each PW. Each PW 
   endpoint compares local and remote status and uses the PW that is 
   operationally UP at both endpoints and that shows Active states at 
   both the local and remote endpoint.

After which there is a discussion about what happens if an active PW is
not found.

I have a question about what happens when there are two perfectly good
PWs.

What happens if initially the two endpoints choose different PWs as the
active ones ?

I am assuming that an endpoint, seeing that the other declares the PW it
intended as backup
to be the active one, then chooses to switch and sends an active
indication on the other PW.
Meanwhile the other endpoint does the same, causing infinite flapping.

Did I misunderstand something ?

Y(J)S