RE: [PWE3] draft-muley-dutta-pwe3-redundancy-bit-02.txt

"AISSAOUI Mustapha" <Mustapha.Aissaoui@alcatel-lucent.com> Fri, 04 January 2008 20:37 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 1JAtHp-0008Pa-6C; Fri, 04 Jan 2008 15:37:01 -0500
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43) id 1JAtHn-0008PU-Ls for pwe3-confirm+ok@megatron.ietf.org; Fri, 04 Jan 2008 15:36:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JAtHn-0008PM-By for pwe3@ietf.org; Fri, 04 Jan 2008 15:36:59 -0500
Received: from audl952.usa.alcatel.com ([143.209.238.159]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JAtHl-0004IS-0e for pwe3@ietf.org; Fri, 04 Jan 2008 15:36:59 -0500
Received: from usdalsbhs02.ad3.ad.alcatel.com (usdalsbhs02.usa.alcatel.com [172.22.216.13]) by audl952.usa.alcatel.com (ALCANET) with ESMTP id m04KatUq031147; Fri, 4 Jan 2008 14:36:56 -0600
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by usdalsbhs02.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Fri, 4 Jan 2008 14:36:44 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [PWE3] draft-muley-dutta-pwe3-redundancy-bit-02.txt
Date: Fri, 04 Jan 2008 14:36:43 -0600
Message-ID: <4A5028372622294A99B8FFF6BD06EB7B03C7D40E@USDALSMBS03.ad3.ad.alcatel.com>
In-Reply-To: <029583E37562274699DC24FB7663A5FC25BFBA@FHDP1CCMXCV01.us.one.verizon.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [PWE3] draft-muley-dutta-pwe3-redundancy-bit-02.txt
Thread-Index: AchO94VvGWOISObISp+v8yJpAIlKSwAA7YuQ
References: <029583E37562274699DC24FB7663A5FC25BFBA@FHDP1CCMXCV01.us.one.verizon.com>
From: AISSAOUI Mustapha <Mustapha.Aissaoui@alcatel-lucent.com>
To: roman.krzanowski@verizon.com, pwe3@ietf.org
X-OriginalArrivalTime: 04 Jan 2008 20:36:44.0818 (UTC) FILETIME=[8538A720:01C84F11]
X-Scanned-By: MIMEDefang 2.51 on 143.209.238.34
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a0534e6179a1e260079328e8b03c7901
Cc:
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="===============2139182179=="
Errors-To: pwe3-bounces@ietf.org

Roman,
thank you for the suggestions. See my comments below.
 
Regards,
Mustapha.


________________________________

	From: roman.krzanowski@verizon.com
[mailto:roman.krzanowski@verizon.com] 
	Sent: Friday, January 04, 2008 12:29 PM
	To: pwe3@ietf.org
	Subject: [PWE3] draft-muley-dutta-pwe3-redundancy-bit-02.txt 
	
	
	I am thinking about the operationalizing of the PWE
ACTIVE/passive stand-by function. Without mandating specific mechanisms
the draft  should  state the need for certain functionalities to be
considered in the implementation of the draft.
	 
	I propose to include the following sections or similar:
	 
	5.4 Permanent active PWE designation.
	The system COULD provide for the permanent designation of one
PWe as Active. After the switch over to stand-by and the recovery of the
active the traffic would switch over to the active again. The "flapping
prevention mechanism- algorithm" should be implemented. This function is
OPTIONAL.  
	 
	MA> What you may be suggesting is the concept of Primary PW and
Secondary PW rather than an Active/Standby designation. Active and
Standby are states which change over time. However, a Primary PW is a PW
that is activated in preference to all other PWs when it is UP and shows
"Active" status at both endpoints. This also means that the system
should revert to the Primary PW when it comes back up from a failure.
	The draft refers to the concept of Primary and Secondary PWs and
we could expand as required.
	Let me know if my understanding is incorrect.    
	 
	5.5 AC PWE status signaling
	A system COULD signal to the AC side the status of the PWE -
Active, down. The existing OAM signaling mechanisms could used for this
function. The signaling should be done on the non-switching END -PE
ONLY. This function is OPTIONAL. 
	 
	MA> I assume you are referring to the ability of a PE/T-PE to
translate a fault notification received in a PW status bit to the AC
specific fault notification. This applies mostly to the operational
status bits, i.e., AC up/down, PW up/down, and PW not forwarding. This
is covered in draft-ietf-pwe3-oam-msg-map-05 and implementations should
support it independently of the PW redundancy capability.
	I am not sure I see the application for passing the
"active/standby" status to the AC. I appreciate if you could 
	elaborate.

_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3