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

"Yaakov Stein" <yaakov_s@rad.com> Thu, 27 December 2007 11:39 UTC

Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J7r5I-0002WE-S5; Thu, 27 Dec 2007 06:39:32 -0500
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43) id 1J7r5H-0002Uc-DI for pwe3-confirm+ok@megatron.ietf.org; Thu, 27 Dec 2007 06:39:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J7r5H-0002Sf-2Z for pwe3@ietf.org; Thu, 27 Dec 2007 06:39:31 -0500
Received: from [212.199.240.16] (helo=antivir2.rad.co.il) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J7r5F-0006Zq-00 for pwe3@ietf.org; Thu, 27 Dec 2007 06:39:31 -0500
Received: from exrad3.ad.rad.co.il ([192.114.24.112]) by antivir2.rad.co.il with ESMTP; 27 Dec 2007 13:39:26 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 27 Dec 2007 13:39:26 +0200
Message-ID: <457D36D9D89B5B47BC06DA869B1C815D05FA4F8C@exrad3.ad.rad.co.il>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: question on the "independent mode" of draft-muley-dutta
Thread-Index: AchIfSJbSRsrzEjmQvK3SviAkQnm5w==
From: Yaakov Stein <yaakov_s@rad.com>
To: pwe3@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
Cc: Keren Zik-Meirom <keren_z@rad.com>
Subject: [PWE3] question on the "independent mode" of draft-muley-dutta
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0418928844=="
Errors-To: pwe3-bounces@ietf.org

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
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3