From pwe3-bounces@ietf.org  Mon Jan  5 02:13:21 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8AF473A689E;
	Mon,  5 Jan 2009 02:13:21 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CB1623A63CB
	for <pwe3@core3.amsl.com>; Mon,  5 Jan 2009 02:13:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.498
X-Spam-Level: 
X-Spam-Status: No, score=-2.498 tagged_above=-999 required=5 tests=[AWL=0.100, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 yPcZ5Bq0Xufc for <pwe3@core3.amsl.com>;
	Mon,  5 Jan 2009 02:13:17 -0800 (PST)
Received: from eci-iron1.ecitele.com (eci-iron1.ecitele.com [147.234.242.117])
	by core3.amsl.com (Postfix) with ESMTP id E667E3A689E
	for <pwe3@ietf.org>; Mon,  5 Jan 2009 02:13:16 -0800 (PST)
Received: from unknown (HELO ILPTAM01.ecitele.com) ([147.234.244.44])
	by eci-iron1.ecitele.com with ESMTP; 05 Jan 2009 12:35:21 +0200
Received: from ilptexch01.ecitele.com ([172.31.244.40]) by
	ILPTAM01.ecitele.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 Jan 2009 12:11:43 +0200
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by
	ilptexch01.ecitele.com ([172.31.244.40]) with mapi;
	Mon, 5 Jan 2009 12:11:42 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "mustapha.aissaoui@alcatel-lucent.com"
	<mustapha.aissaoui@alcatel-lucent.com>, "busschbach@alcatel-lucent.com"
	<busschbach@alcatel-lucent.com>, "dallan@nortel.com" <dallan@nortel.com>,
	"lmartini@cisco.com" <lmartini@cisco.com>, "Thomas D. Nadeau"
	<tom.nadeau@bt.com>, "mmorrow@cisco.com" <mmorrow@cisco.com>
Date: Mon, 5 Jan 2009 12:11:41 +0200
Thread-Topic: A question regarding torn down PWs in
	draft-ietf-pwe3-oam-msg-map-08.txt
Thread-Index: AclvHgFatl4xVjfUTBai2RqcqunEfw==
Message-ID: <A3C5DF08D38B6049839A6F553B331C7698C2C6CCC1@ILPTMAIL02.ecitele.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-OriginalArrivalTime: 05 Jan 2009 10:11:43.0637 (UTC)
	FILETIME=[0260CC50:01C96F1E]
Cc: Itamar Levy <Itamar.Levy@ecitele.com>,
	Igor Danilovich <Igor.Danilovich@ecitele.com>,
	"pwe3@ietf.org" <pwe3@ietf.org>, Shell Nakash <Shell.Nakash@ecitele.com>
Subject: [PWE3] A question regarding torn down PWs in
 draft-ietf-pwe3-oam-msg-map-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1670977565=="
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

--===============1670977565==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_A3C5DF08D38B6049839A6F553B331C7698C2C6CCC1ILPTMAIL02eci_"

--_000_A3C5DF08D38B6049839A6F553B331C7698C2C6CCC1ILPTMAIL02eci_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Monique/Mustapha/Peter/Dave/Thom/Luca,
I have a question to you as the editors of the expired) draft-ietf-pwe3-oam=
-msg-map-08.txt.
The question is related to the following text in Section 8.2.1. PW Forward =
Defect State Entry/Exit Criteria:
<quote>
   Note that if the PW control session between the PEs fails, the PW is
   torn down and needs to be re-established. This includes failure of
   the T-LDP session, the L2TP session, or the L2TP control connection.
   However, the consequent actions towards the ACs are the same as if
   the PW entered the forward defect state.
<end quote>
The PW may be torn down not just because the PW control session between the=
 PEs fails. E.g., the PW can be deleted by the operator in one of the PEs.
Does the quoted text imply that implementations must distinguish between PW=
s being torn down due to failures of their control sessions and PWs that ar=
e torn down for any other reason?
The use case of special interest would be a PW that has been set up (and la=
ter torn down) using a single-sided mechanism...
I'd also like to note that there are several references in the draft to uns=
pecified defects  "that do not result in the PW being torn down"...

Regards,
     Sasha



--_000_A3C5DF08D38B6049839A6F553B331C7698C2C6CCC1ILPTMAIL02eci_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3492" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>Hi=20
Monique/Mustapha/Peter/Dave/Thom/Luca,</FONT></SPAN></DIV>
<DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>I have a =
question to=20
you as the editors of the expired)=20
draft-ietf-pwe3-oam-msg-map-08.txt.</FONT></SPAN></DIV>
<DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>The quest=
ion is=20
related&nbsp;to the following text in Section <STRONG>8.2.1. PW Forward Def=
ect=20
State Entry/Exit Criteria</STRONG>:</FONT></SPAN></DIV>
<DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
size=3D2>&lt;quote&gt;</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV><SPAN class=3D012494009-05012009><EM><FONT color=3D#0000ff>&nbsp;&nb=
sp; Note=20
  that if the PW control session between the PEs fails, the PW is=20
  <BR>&nbsp;&nbsp; torn down and needs to be re-established. This includes=
=20
  failure of <BR>&nbsp;&nbsp; the T-LDP session, the L2TP session, or the L=
2TP=20
  control connection. <BR>&nbsp;&nbsp; However, the consequent actions towa=
rds=20
  the ACs are the same as if <BR>&nbsp;&nbsp; the PW entered the forward de=
fect=20
  state.</FONT></EM></SPAN></DIV></BLOCKQUOTE>
<DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>&lt;end=20
quote&gt;</FONT></SPAN></DIV>
<DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>The PW ma=
y be torn=20
down not just because the PW control session between the PEs fails. E.g., t=
he PW=20
can be deleted by the operator in one of the PEs.</FONT></SPAN></DIV>
<DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>Does the =
quoted text=20
imply that implementations must distinguish between PWs being torn down due=
 to=20
failures of their control sessions and PWs that are torn down for any other=
=20
reason?</FONT></SPAN></DIV>
<DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>The use c=
ase of=20
special interest would be a PW that has been set up (and later torn down) u=
sing=20
a single-sided mechanism...</FONT></SPAN></DIV>
<DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>I'd also =
like to=20
note that there are several references in the draft to unspecified=20
defects&nbsp;<EM><FONT color=3D#0000ff> "that do not result in the PW being=
 torn=20
down</FONT></EM>"...</FONT></SPAN></DIV>
<DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
size=3D2>Regards,</FONT></SPAN></DIV>
<DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</FONT></SPAN></DIV>
<DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV></BODY></HTML>

--_000_A3C5DF08D38B6049839A6F553B331C7698C2C6CCC1ILPTMAIL02eci_--

--===============1670977565==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1670977565==--


From pwe3-bounces@ietf.org  Mon Jan  5 05:52:27 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 826813A6868;
	Mon,  5 Jan 2009 05:52:27 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3A2A03A6856
	for <pwe3@core3.amsl.com>; Mon,  5 Jan 2009 05:52:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 BTo5-273ce+s for <pwe3@core3.amsl.com>;
	Mon,  5 Jan 2009 05:52:25 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35])
	by core3.amsl.com (Postfix) with ESMTP id 2FDF33A67AB
	for <pwe3@ietf.org>; Mon,  5 Jan 2009 05:52:24 -0800 (PST)
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2])
	by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id n05DpIpa028584;
	Mon, 5 Jan 2009 07:51:59 -0600 (CST)
Received: from ILEXC2U01.ndc.lucent.com ([135.3.39.9]) by
	ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 07:51:30 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 Jan 2009 07:51:28 -0600
Message-ID: <E60778C3916D3548BBCF4D964186348F022953BD@ILEXC2U01.ndc.lucent.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C7698C2C6CCC1@ILPTMAIL02.ecitele.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: A question regarding torn down PWs in
	draft-ietf-pwe3-oam-msg-map-08.txt
Thread-Index: AclvHgFatl4xVjfUTBai2RqcqunEfwAHTX0A
References: <A3C5DF08D38B6049839A6F553B331C7698C2C6CCC1@ILPTMAIL02.ecitele.com>
From: "Busschbach, Peter B \(Peter\)" <busschbach@alcatel-lucent.com>
To: "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>,
	"Aissaoui, Mustapha \(Mustapha\)" <mustapha.aissaoui@alcatel-lucent.com>,
	<dallan@nortel.com>, <lmartini@cisco.com>,
	"Thomas D. Nadeau" <tom.nadeau@bt.com>, <mmorrow@cisco.com>
X-OriginalArrivalTime: 05 Jan 2009 13:51:30.0460 (UTC)
	FILETIME=[B6564DC0:01C96F3C]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Cc: Itamar Levy <Itamar.Levy@ecitele.com>,
	Igor Danilovich <Igor.Danilovich@ecitele.com>, pwe3@ietf.org,
	Shell Nakash <Shell.Nakash@ecitele.com>
Subject: Re: [PWE3] A question regarding torn down PWs in
	draft-ietf-pwe3-oam-msg-map-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1841694771=="
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1841694771==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C96F3C.B5E23FB0"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C96F3C.B5E23FB0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Sasha,
=20
>> Does the quoted text imply that implementations must distinguish
between PWs being torn down
>> due to failures of their control sessions and PWs that are torn down
for any other reason?
=20
Whether PWs are torn down because of a defect (whether it is in the
control plane or in the data plane), the consequent actions are the
same. It would be good, however, if a PE would be able to distinguish
between PWs torn down because of defects and PWs torn down for
administrative reasons, because in the latter case there is no need to
insert an FDI message downstream.
=20
Remember that Luca sent an email to the list proposing to add a BFD code
point to indicate that an AC was taken down for admistrative reasons.
That proposal was driven by the same motivation.
=20
Peter
=20
=20

________________________________

	From: Alexander Vainshtein
[mailto:Alexander.Vainshtein@ecitele.com]=20
	Sent: Monday, January 05, 2009 5:12 AM
	To: Aissaoui, Mustapha (Mustapha); Busschbach, Peter B (Peter);
dallan@nortel.com; lmartini@cisco.com; Thomas D. Nadeau;
mmorrow@cisco.com
	Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor
Danilovich; Itamar Levy
	Subject: A question regarding torn down PWs in
draft-ietf-pwe3-oam-msg-map-08.txt
=09
=09
	Hi Monique/Mustapha/Peter/Dave/Thom/Luca,
	I have a question to you as the editors of the expired)
draft-ietf-pwe3-oam-msg-map-08.txt.
	The question is related to the following text in Section 8.2.1.
PW Forward Defect State Entry/Exit Criteria:
	<quote>

		   Note that if the PW control session between the PEs
fails, the PW is=20
		   torn down and needs to be re-established. This
includes failure of=20
		   the T-LDP session, the L2TP session, or the L2TP
control connection.=20
		   However, the consequent actions towards the ACs are
the same as if=20
		   the PW entered the forward defect state.

	<end quote>
	The PW may be torn down not just because the PW control session
between the PEs fails. E.g., the PW can be deleted by the operator in
one of the PEs.
	Does the quoted text imply that implementations must distinguish
between PWs being torn down due to failures of their control sessions
and PWs that are torn down for any other reason?
	The use case of special interest would be a PW that has been set
up (and later torn down) using a single-sided mechanism...
	I'd also like to note that there are several references in the
draft to unspecified defects  "that do not result in the PW being torn
down"...
	=20
	Regards,
	     Sasha
	=20
	=20


------_=_NextPart_001_01C96F3C.B5E23FB0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3243" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT =
face=3DArial=20
size=3D2>Hi Sasha,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT =
face=3DArial=20
size=3D2>&gt;&gt; <SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>Does the=20
quoted text imply that implementations must distinguish between PWs =
being torn=20
down</FONT></SPAN></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT =
face=3DArial=20
size=3D2><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>&gt;&gt; due to=20
failures of their control sessions and PWs that are torn down for any =
other=20
reason?</FONT></SPAN></FONT></SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
class=3D214484013-05012009>Whether&nbsp;PWs are torn down because of a =
defect=20
(whether it is in the control plane or in the data plane), the =
consequent=20
actions are the same. It would be good, however, if a PE would be able =
to=20
distinguish between PWs torn down because of defects and PWs torn down =
for=20
administrative reasons, because in the latter case there is no need to =
insert an=20
FDI message downstream.</SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D214484013-05012009>Remember that=20
Luca sent an email to the list proposing to add a BFD code point to =
indicate=20
that an AC was taken down for admistrative reasons. That proposal was =
driven by=20
the same motivation.</SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
class=3D214484013-05012009>Peter</SPAN></FONT></FONT></DIV>
<DIV><FONT size=3D2><SPAN =
class=3D214484013-05012009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2><SPAN =
class=3D214484013-05012009></SPAN></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Alexander Vainshtein=20
  [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> Monday, =
January 05,=20
  2009 5:12 AM<BR><B>To:</B> Aissaoui, Mustapha (Mustapha); Busschbach, =
Peter B=20
  (Peter); dallan@nortel.com; lmartini@cisco.com; Thomas D. Nadeau;=20
  mmorrow@cisco.com<BR><B>Cc:</B> pwe3@ietf.org; Shell Nakash; Prashant =
Desai;=20
  Igor Danilovich; Itamar Levy<BR><B>Subject:</B> A question regarding =
torn down=20
  PWs in draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>Hi=20
  Monique/Mustapha/Peter/Dave/Thom/Luca,</FONT></SPAN></DIV>
  <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>I =
have a question=20
  to you as the editors of the expired)=20
  draft-ietf-pwe3-oam-msg-map-08.txt.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>The =
question is=20
  related&nbsp;to the following text in Section <STRONG>8.2.1. PW =
Forward Defect=20
  State Entry/Exit Criteria</STRONG>:</FONT></SPAN></DIV>
  <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
  size=3D2>&lt;quote&gt;</FONT></SPAN></DIV>
  <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
    <DIV><SPAN class=3D012494009-05012009><EM><FONT =
color=3D#0000ff>&nbsp;&nbsp;=20
    Note that if the PW control session between the PEs fails, the PW is =

    <BR>&nbsp;&nbsp; torn down and needs to be re-established. This =
includes=20
    failure of <BR>&nbsp;&nbsp; the T-LDP session, the L2TP session, or =
the L2TP=20
    control connection. <BR>&nbsp;&nbsp; However, the consequent actions =
towards=20
    the ACs are the same as if <BR>&nbsp;&nbsp; the PW entered the =
forward=20
    defect state.</FONT></EM></SPAN></DIV></BLOCKQUOTE>
  <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>&lt;end=20
  quote&gt;</FONT></SPAN></DIV>
  <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>The =
PW may be torn=20
  down not just because the PW control session between the PEs fails. =
E.g., the=20
  PW can be deleted by the operator in one of the =
PEs.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>Does =
the quoted=20
  text imply that implementations must distinguish between PWs being =
torn down=20
  due to failures of their control sessions and PWs that are torn down =
for any=20
  other reason?</FONT></SPAN></DIV>
  <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>The =
use case of=20
  special interest would be a PW that has been set up (and later torn =
down)=20
  using a single-sided mechanism...</FONT></SPAN></DIV>
  <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>I'd =
also like to=20
  note that there are several references in the draft to unspecified=20
  defects&nbsp;<EM><FONT color=3D#0000ff> "that do not result in the PW =
being torn=20
  down</FONT></EM>"...</FONT></SPAN></DIV>
  <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
  size=3D2>Regards,</FONT></SPAN></DIV>
  <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</FONT></SPAN></DIV>
  <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C96F3C.B5E23FB0--

--===============1841694771==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1841694771==--


From pwe3-bounces@ietf.org  Mon Jan  5 07:09:35 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 925C73A6935;
	Mon,  5 Jan 2009 07:09:35 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CCC9728C0E0
	for <pwe3@core3.amsl.com>; Mon,  5 Jan 2009 07:09:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.513
X-Spam-Level: 
X-Spam-Status: No, score=-2.513 tagged_above=-999 required=5 tests=[AWL=0.085, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 kr5et2KVVxxm for <pwe3@core3.amsl.com>;
	Mon,  5 Jan 2009 07:09:33 -0800 (PST)
Received: from eci-iron1.ecitele.com (eci-iron1.ecitele.com [147.234.242.117])
	by core3.amsl.com (Postfix) with ESMTP id 9EB6C28C0DF
	for <pwe3@ietf.org>; Mon,  5 Jan 2009 07:09:32 -0800 (PST)
Received: from unknown (HELO ILPTAM01.ecitele.com) ([147.234.244.44])
	by eci-iron1.ecitele.com with ESMTP; 05 Jan 2009 17:32:40 +0200
Received: from ilptexch01.ecitele.com ([172.31.244.40]) by
	ILPTAM01.ecitele.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 Jan 2009 17:08:57 +0200
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by
	ilptexch01.ecitele.com ([172.31.244.40]) with mapi;
	Mon, 5 Jan 2009 17:08:58 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "Busschbach, Peter B (Peter)" <busschbach@alcatel-lucent.com>
Date: Mon, 5 Jan 2009 17:08:58 +0200
Thread-Topic: A question regarding torn down PWs in
	draft-ietf-pwe3-oam-msg-map-08.txt
Thread-Index: AclvHgFatl4xVjfUTBai2RqcqunEfwAHTX0AAADXDMA=
Message-ID: <A3C5DF08D38B6049839A6F553B331C7698C2C6CDE7@ILPTMAIL02.ecitele.com>
References: <A3C5DF08D38B6049839A6F553B331C7698C2C6CCC1@ILPTMAIL02.ecitele.com>
	<E60778C3916D3548BBCF4D964186348F022953BD@ILEXC2U01.ndc.lucent.com>
In-Reply-To: <E60778C3916D3548BBCF4D964186348F022953BD@ILEXC2U01.ndc.lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-OriginalArrivalTime: 05 Jan 2009 15:08:57.0796 (UTC)
	FILETIME=[885D8040:01C96F47]
Cc: Shell Nakash <Shell.Nakash@ecitele.com>,
	"lmartini@cisco.com" <lmartini@cisco.com>,
	"mmorrow@cisco.com" <mmorrow@cisco.com>,
	Igor Danilovich <Igor.Danilovich@ecitele.com>,
	"pwe3@ietf.org" <pwe3@ietf.org>, "Aissaoui,
	Mustapha \(Mustapha\)" <mustapha.aissaoui@alcatel-lucent.com>,
	Itamar Levy <Itamar.Levy@ecitele.com>
Subject: Re: [PWE3] A question regarding torn down PWs in
 draft-ietf-pwe3-oam-msg-map-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1013133637=="
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

--===============1013133637==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_A3C5DF08D38B6049839A6F553B331C7698C2C6CDE7ILPTMAIL02eci_"

--_000_A3C5DF08D38B6049839A6F553B331C7698C2C6CDE7ILPTMAIL02eci_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Peter hi,
Lots of thanks for a prompt response.

Please see some comments inline below (blue italics).

Regards,
    Sasha

________________________________
From: Busschbach, Peter B (Peter) [mailto:busschbach@alcatel-lucent.com]
Sent: Monday, January 05, 2009 3:51 PM
To: Alexander Vainshtein; Aissaoui, Mustapha (Mustapha); dallan@nortel.com;=
 lmartini@cisco.com; Thomas D. Nadeau; mmorrow@cisco.com
Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor Danilovich; Itamar Le=
vy
Subject: RE: A question regarding torn down PWs in draft-ietf-pwe3-oam-msg-=
map-08.txt

Hi Sasha,

>> Does the quoted text imply that implementations must distinguish between=
 PWs being torn down
>> due to failures of their control sessions and PWs that are torn down for=
 any other reason?

Whether PWs are torn down because of a defect (whether it is in the control=
 plane or in the data plane), the consequent actions are the same.
[[Sasha]] I am not aware of the case when a PW is torn down due to defects =
in the data plane. Could you please provide a reference/an example?
 It would be good, however, if a PE would be able to distinguish between PW=
s torn down because of defects and PWs torn down for administrative reasons=
, because in the latter case there is no need to insert an FDI message down=
stream.
[[Sasha]] I do not think that RFC 4447 provides for that. In addition, plea=
se consider the following scenario:

 1.  A PW is set up
 2.  The PW is torn down due to the CP defect (targeted LDP session went do=
wn). FDI is inserted in the local AC
 3.   The user has deleted the PW end point in the remote PE. Since the LDP=
 session is down, this fact is not communicated to the local PE
 4.  Targeted LDP session is restored but an attempt of the local PE to res=
tore the PW fails since there is no remote peer anymore. What should now ha=
ppen to the local AC?


Remember that Luca sent an email to the list proposing to add a BFD code po=
int to indicate that an AC was taken down for admistrative reasons. That pr=
oposal was driven by the same motivation.
[[Sasha]] I remember that, and I believe I've sent a couple of messages to =
the list questioning the rationale of such a code point.

Peter


________________________________
From: Alexander Vainshtein [mailto:Alexander.Vainshtein@ecitele.com]
Sent: Monday, January 05, 2009 5:12 AM
To: Aissaoui, Mustapha (Mustapha); Busschbach, Peter B (Peter); dallan@nort=
el.com; lmartini@cisco.com; Thomas D. Nadeau; mmorrow@cisco.com
Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor Danilovich; Itamar Le=
vy
Subject: A question regarding torn down PWs in draft-ietf-pwe3-oam-msg-map-=
08.txt

Hi Monique/Mustapha/Peter/Dave/Thom/Luca,
I have a question to you as the editors of the expired) draft-ietf-pwe3-oam=
-msg-map-08.txt.
The question is related to the following text in Section 8.2.1. PW Forward =
Defect State Entry/Exit Criteria:
<quote>
   Note that if the PW control session between the PEs fails, the PW is
   torn down and needs to be re-established. This includes failure of
   the T-LDP session, the L2TP session, or the L2TP control connection.
   However, the consequent actions towards the ACs are the same as if
   the PW entered the forward defect state.
<end quote>
The PW may be torn down not just because the PW control session between the=
 PEs fails. E.g., the PW can be deleted by the operator in one of the PEs.
Does the quoted text imply that implementations must distinguish between PW=
s being torn down due to failures of their control sessions and PWs that ar=
e torn down for any other reason?
The use case of special interest would be a PW that has been set up (and la=
ter torn down) using a single-sided mechanism...
I'd also like to note that there are several references in the draft to uns=
pecified defects  "that do not result in the PW being torn down"...

Regards,
     Sasha



--_000_A3C5DF08D38B6049839A6F553B331C7698C2C6CDE7ILPTMAIL02eci_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3492" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN class=3D017510414-05=
012009>Peter=20
hi,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN class=3D017510414-05=
012009>Lots=20
of thanks for a prompt response.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D017510414-05012009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN class=3D017510414-05=
012009>Please=20
see some comments inline below (<EM>blue italics</EM>).</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D017510414-05012009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D017510414-05012009>Regards,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D017510414-05012009>&nbsp;&nbsp;&nbsp; Sasha</SPAN></FONT></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Busschbach, Peter B (Peter)=20
  [mailto:busschbach@alcatel-lucent.com] <BR><B>Sent:</B> Monday, January 0=
5,=20
  2009 3:51 PM<BR><B>To:</B> Alexander Vainshtein; Aissaoui, Mustapha=20
  (Mustapha); dallan@nortel.com; lmartini@cisco.com; Thomas D. Nadeau;=20
  mmorrow@cisco.com<BR><B>Cc:</B> pwe3@ietf.org; Shell Nakash; Prashant Des=
ai;=20
  Igor Danilovich; Itamar Levy<BR><B>Subject:</B> RE: A question regarding =
torn=20
  down PWs in draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT face=
=3DArial=20
  size=3D2>Hi Sasha,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT face=
=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT face=
=3DArial=20
  size=3D2>&gt;&gt; <SPAN class=3D012494009-05012009><FONT face=3DArial siz=
e=3D2>Does=20
  the quoted text imply that implementations must distinguish between PWs b=
eing=20
  torn down</FONT></SPAN></FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT face=
=3DArial=20
  size=3D2><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>&gt=
;&gt; due to=20
  failures of their control sessions and PWs that are torn down for any oth=
er=20
  reason?</FONT></SPAN></FONT></SPAN></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN class=3D214484013-05012009>Whether=
&nbsp;PWs=20
  are torn down because of a defect (whether it is in the control plane or =
in=20
  the data plane), the consequent actions are the same.<BR><SPAN=20
  class=3D017510414-05012009><FONT color=3D#0000ff><EM>[[Sasha]]&nbsp;I am =
not aware=20
  of the case when a PW is torn down due to defects in the data plane. Coul=
d you=20
  please provide a reference/an example?</EM></FONT></SPAN></SPAN></FONT></=
DIV>
  <DIV><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT size=3D2>&=
nbsp;It=20
  would be good, however, if a PE would be able to distinguish between PWs =
torn=20
  down because of defects and PWs torn down for administrative reasons, bec=
ause=20
  in the latter case there is no need to insert an FDI message=20
  downstream.<BR><SPAN class=3D017510414-05012009><FONT=20
  color=3D#0000ff><EM>[[Sasha]]&nbsp;I do not think that RFC 4447 provides =
for=20
  that.&nbsp;In addition, please consider the following=20
  scenario:</EM></FONT></SPAN></FONT></FONT></SPAN></DIV>
  <OL>
    <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT size=3D2>=
<SPAN=20
    class=3D017510414-05012009><FONT color=3D#0000ff><EM>A PW is set=20
    up</EM></FONT></SPAN></FONT></FONT></SPAN></LI>
    <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT size=3D2>=
<SPAN=20
    class=3D017510414-05012009><FONT color=3D#0000ff><EM>The PW is torn=20
    down&nbsp;due to the CP defect (targeted LDP session went down). FDI is=
=20
    inserted in the local AC</EM></FONT></SPAN></FONT></FONT></SPAN></LI>
    <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT size=3D2>=
<SPAN=20
    class=3D017510414-05012009><EM>&nbsp;<FONT color=3D#0000ff>The user has=
 deleted=20
    the PW end point in the remote PE. Since the LDP session is down, this =
fact=20
    is not communicated to the local=20
    PE</FONT></EM></SPAN></FONT></FONT></SPAN></LI>
    <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT color=3D#=
0000ff=20
    size=3D2><SPAN class=3D017510414-05012009><EM>Targeted LDP session is r=
estored=20
    but an attempt of the local PE to restore the PW fails since there is n=
o=20
    remote peer anymore. <STRONG>What should now happen to the local=20
    AC</STRONG>?</EM></SPAN></FONT></FONT></SPAN></LI></OL>
  <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
  class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
  <DIV><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT size=3D2>R=
emember=20
  that Luca sent an email to the list proposing to add a BFD code point to=
=20
  indicate that an AC was taken down for admistrative reasons. That proposa=
l was=20
  driven by the same motivation.<BR><SPAN class=3D017510414-05012009><FONT=
=20
  color=3D#0000ff><EM>[[Sasha]]&nbsp;I&nbsp;remember that, and I believe I'=
ve sent=20
  a couple of messages to the list questioning the rationale of&nbsp;such a=
 code=20
  point. &nbsp;</EM></FONT></SPAN></FONT></FONT></SPAN></DIV>
  <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
  class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
  class=3D214484013-05012009>Peter</SPAN></FONT></FONT></DIV>
  <DIV><FONT size=3D2><SPAN class=3D214484013-05012009></SPAN></FONT>&nbsp;=
</DIV>
  <DIV><FONT size=3D2><SPAN class=3D214484013-05012009></SPAN></FONT>&nbsp;=
</DIV>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px so=
lid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> Alexander Vainshtein=20
    [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> Monday, Janu=
ary=20
    05, 2009 5:12 AM<BR><B>To:</B> Aissaoui, Mustapha (Mustapha); Busschbac=
h,=20
    Peter B (Peter); dallan@nortel.com; lmartini@cisco.com; Thomas D. Nadea=
u;=20
    mmorrow@cisco.com<BR><B>Cc:</B> pwe3@ietf.org; Shell Nakash; Prashant D=
esai;=20
    Igor Danilovich; Itamar Levy<BR><B>Subject:</B> A question regarding to=
rn=20
    down PWs in draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>Hi=20
    Monique/Mustapha/Peter/Dave/Thom/Luca,</FONT></SPAN></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>I hav=
e a=20
    question to you as the editors of the expired)=20
    draft-ietf-pwe3-oam-msg-map-08.txt.</FONT></SPAN></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>The q=
uestion is=20
    related&nbsp;to the following text in Section <STRONG>8.2.1. PW Forward=
=20
    Defect State Entry/Exit Criteria</STRONG>:</FONT></SPAN></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
    size=3D2>&lt;quote&gt;</FONT></SPAN></DIV>
    <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
      <DIV><SPAN class=3D012494009-05012009><EM><FONT color=3D#0000ff>&nbsp=
;&nbsp;=20
      Note that if the PW control session between the PEs fails, the PW is=
=20
      <BR>&nbsp;&nbsp; torn down and needs to be re-established. This inclu=
des=20
      failure of <BR>&nbsp;&nbsp; the T-LDP session, the L2TP session, or t=
he=20
      L2TP control connection. <BR>&nbsp;&nbsp; However, the consequent act=
ions=20
      towards the ACs are the same as if <BR>&nbsp;&nbsp; the PW entered th=
e=20
      forward defect state.</FONT></EM></SPAN></DIV></BLOCKQUOTE>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>&lt;e=
nd=20
    quote&gt;</FONT></SPAN></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>The P=
W may be=20
    torn down not just because the PW control session between the PEs fails=
.=20
    E.g., the PW can be deleted by the operator in one of the=20
    PEs.</FONT></SPAN></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>Does =
the quoted=20
    text imply that implementations must distinguish between PWs being torn=
 down=20
    due to failures of their control sessions and PWs that are torn down fo=
r any=20
    other reason?</FONT></SPAN></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>The u=
se case of=20
    special interest would be a PW that has been set up (and later torn dow=
n)=20
    using a single-sided mechanism...</FONT></SPAN></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>I'd a=
lso like to=20
    note that there are several references in the draft to unspecified=20
    defects&nbsp;<EM><FONT color=3D#0000ff> "that do not result in the PW b=
eing=20
    torn down</FONT></EM>"...</FONT></SPAN></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
    size=3D2>Regards,</FONT></SPAN></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</FONT></SPAN></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></H=
TML>

--_000_A3C5DF08D38B6049839A6F553B331C7698C2C6CDE7ILPTMAIL02eci_--

--===============1013133637==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1013133637==--


From pwe3-bounces@ietf.org  Mon Jan  5 08:13:14 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 838953A6873;
	Mon,  5 Jan 2009 08:13:14 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BB2793A6873
	for <pwe3@core3.amsl.com>; Mon,  5 Jan 2009 08:13:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 z6WN6ptt6XNX for <pwe3@core3.amsl.com>;
	Mon,  5 Jan 2009 08:13:12 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37])
	by core3.amsl.com (Postfix) with ESMTP id C2BB83A6853
	for <pwe3@ietf.org>; Mon,  5 Jan 2009 08:13:12 -0800 (PST)
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1])
	by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id n05GCinX002444;
	Mon, 5 Jan 2009 10:12:44 -0600 (CST)
Received: from ILEXC2U01.ndc.lucent.com ([135.3.39.9]) by
	ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 10:12:44 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 Jan 2009 10:12:43 -0600
Message-ID: <E60778C3916D3548BBCF4D964186348F022954DD@ILEXC2U01.ndc.lucent.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C7698C2C6CDE7@ILPTMAIL02.ecitele.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: A question regarding torn down PWs in
	draft-ietf-pwe3-oam-msg-map-08.txt
Thread-Index: AclvHgFatl4xVjfUTBai2RqcqunEfwAHTX0AAADXDMAABCCuAA==
References: <A3C5DF08D38B6049839A6F553B331C7698C2C6CCC1@ILPTMAIL02.ecitele.com>
	<E60778C3916D3548BBCF4D964186348F022953BD@ILEXC2U01.ndc.lucent.com>
	<A3C5DF08D38B6049839A6F553B331C7698C2C6CDE7@ILPTMAIL02.ecitele.com>
From: "Busschbach, Peter B \(Peter\)" <busschbach@alcatel-lucent.com>
To: "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>
X-OriginalArrivalTime: 05 Jan 2009 16:12:44.0611 (UTC)
	FILETIME=[71532130:01C96F50]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Cc: Shell Nakash <Shell.Nakash@ecitele.com>, lmartini@cisco.com,
	mmorrow@cisco.com, Igor Danilovich <Igor.Danilovich@ecitele.com>,
	pwe3@ietf.org, "Aissaoui,
	Mustapha \(Mustapha\)" <mustapha.aissaoui@alcatel-lucent.com>,
	Itamar Levy <Itamar.Levy@ecitele.com>
Subject: Re: [PWE3] A question regarding torn down PWs in
	draft-ietf-pwe3-oam-msg-map-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0334680802=="
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0334680802==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C96F50.704BA132"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C96F50.704BA132
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Sasha,
=20
Please see in-line


________________________________

	From: Alexander Vainshtein
[mailto:Alexander.Vainshtein@ecitele.com]=20
	Sent: Monday, January 05, 2009 10:09 AM
=09
	[snipped]=20
=09
=09

	=09
		[[Sasha]] I am not aware of the case when a PW is torn
down due to defects in the data plane. Could you please provide a
reference/an example?
	=09
		=20
		=20
		[PB]  See section 5.4.1 of RFC 4447: a simple label
withdraw method MAY also be
		   supported as a legacy means of signaling PW status
and AC status
	=09
		=20
		=20
		 It would be good, however, if a PE would be able to
distinguish between PWs torn down because of defects and PWs torn down
for administrative reasons, because in the latter case there is no need
to insert an FDI message downstream.
		[[Sasha]] I do not think that RFC 4447 provides for
that. In addition, please consider the following scenario:

		1.	A PW is set up=20
		2.	The PW is torn down due to the CP defect
(targeted LDP session went down). FDI is inserted in the local AC=20
		3.	 The user has deleted the PW end point in the
remote PE. Since the LDP session is down, this fact is not communicated
to the local PE=20
		4.	Targeted LDP session is restored but an attempt
of the local PE to restore the PW fails since there is no remote peer
anymore. What should now happen to the local AC

		=20
		=20
		[PB] I don't understand the example. Who is the user
that removes the PW end point? A service provider? If so, why would that
service provider update one PE to remove the PW but not the peer?=20
		=20
		In any case, if the local PE is inserting FDI messages
periodically on the local AC, it will continue doing so as long as the
PW is not restored. Do you believe it should behave otherwise?
		=20
		[snipped to the end]


------_=_NextPart_001_01C96F50.704BA132
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3243" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D285020316-05012009><FONT =
face=3DArial=20
size=3D2>Sasha,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D285020316-05012009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D285020316-05012009><FONT =
face=3DArial=20
size=3D2>Please see in-line</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma><FONT size=3D2><B>From:</B> Alexander Vainshtein=20
  [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> Monday, =
January 05,=20
  2009 10:09 AM<BR></FONT></FONT><FONT face=3DTahoma><BR><FONT =
size=3D2><SPAN=20
  class=3D285020316-05012009><FONT=20
  face=3DArial>[snipped]&nbsp;</FONT></SPAN><BR></FONT></FONT><BR></DIV>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT =
face=3DArial=20
    size=3D2><BR></FONT><SPAN class=3D017510414-05012009><FONT =
color=3D#0000ff><FONT=20
    face=3DArial><FONT size=3D2><EM>[[Sasha]]&nbsp;I am not aware of the =
case when a=20
    PW is torn down due to defects in the data plane. Could you please =
provide a=20
    reference/an =
example?<BR></EM></FONT></FONT></FONT></SPAN></SPAN></DIV>
    <DIV><SPAN class=3D214484013-05012009><SPAN =
class=3D017510414-05012009><FONT=20
    color=3D#0000ff><FONT face=3DArial><FONT size=3D2><SPAN=20
    =
class=3D285020316-05012009></SPAN></FONT></FONT></FONT></SPAN></SPAN>&nbs=
p;</DIV>
    <DIV><SPAN class=3D214484013-05012009><SPAN =
class=3D017510414-05012009><FONT=20
    color=3D#0000ff><FONT face=3DArial><FONT size=3D2><SPAN=20
    class=3D285020316-05012009>&nbsp;</SPAN><BR><SPAN=20
    class=3D285020316-05012009><FONT color=3D#000000>[PB]&nbsp;&nbsp;See =
section=20
    5.4.1 of RFC 4447: <FONT size=3D3>a simple label withdraw method MAY =
also=20
    be<BR>&nbsp;&nbsp; supported as a legacy means of signaling PW =
status and AC=20
    =
status</FONT></FONT></SPAN><BR></DIV></FONT></FONT></FONT></SPAN></SPAN>
    <DIV><SPAN class=3D214484013-05012009><SPAN =
class=3D017510414-05012009><FONT=20
    color=3D#0000ff><FONT face=3DArial><FONT size=3D2><SPAN=20
    =
class=3D285020316-05012009></SPAN></FONT></FONT></FONT></SPAN></SPAN>&nbs=
p;</DIV>
    <DIV><SPAN class=3D214484013-05012009><SPAN =
class=3D017510414-05012009><FONT=20
    color=3D#0000ff><FONT face=3DArial><FONT size=3D2><SPAN=20
    =
class=3D285020316-05012009>&nbsp;</SPAN></FONT></FONT></FONT></SPAN></SPA=
N></DIV>
    <DIV><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2>&nbsp;It=20
    would be good, however, if a PE would be able to distinguish between =
PWs=20
    torn down because of defects and PWs torn down for administrative =
reasons,=20
    because in the latter case there is no need to insert an FDI message =

    downstream.<BR><SPAN class=3D017510414-05012009><FONT=20
    color=3D#0000ff><EM>[[Sasha]]&nbsp;I do not think that RFC 4447 =
provides for=20
    that.&nbsp;In addition, please consider the following=20
    scenario:</EM></FONT></SPAN></FONT></FONT></SPAN></DIV>
    <OL>
      <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2><SPAN=20
      class=3D017510414-05012009><FONT color=3D#0000ff><EM>A PW is set=20
      up</EM></FONT></SPAN></FONT></FONT></SPAN>=20
      <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2><SPAN=20
      class=3D017510414-05012009><FONT color=3D#0000ff><EM>The PW is =
torn=20
      down&nbsp;due to the CP defect (targeted LDP session went down). =
FDI is=20
      inserted in the local AC</EM></FONT></SPAN></FONT></FONT></SPAN>=20
      <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2><SPAN=20
      class=3D017510414-05012009><EM>&nbsp;<FONT color=3D#0000ff>The =
user has=20
      deleted the PW end point in the remote PE. Since the LDP session =
is down,=20
      this fact is not communicated to the local=20
      PE</FONT></EM></SPAN></FONT></FONT></SPAN>=20
      <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
color=3D#0000ff=20
      size=3D2><SPAN class=3D017510414-05012009><EM>Targeted LDP session =
is restored=20
      but an attempt of the local PE to restore the PW fails since there =
is no=20
      remote peer anymore. <STRONG>What should now happen to the local=20
      AC</STRONG></EM></SPAN></FONT></FONT></SPAN></LI></OL>
    <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
    class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
    class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D214484013-05012009><SPAN=20
    class=3D285020316-05012009>[PB] I don't understand the example. Who =
is the=20
    user that removes the PW end point? A service provider? If so, why =
would=20
    that service provider update one PE to remove the PW but not the =
peer?=20
    </SPAN></SPAN></FONT></DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D214484013-05012009><SPAN=20
    class=3D285020316-05012009></SPAN></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D214484013-05012009><SPAN=20
    class=3D285020316-05012009>In any case, if the local PE is inserting =
FDI=20
    messages periodically on the local AC, it will continue doing so as =
long as=20
    the PW is not restored. Do you believe it should behave=20
    otherwise?</SPAN></SPAN></FONT></DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D214484013-05012009><SPAN=20
    class=3D285020316-05012009></SPAN></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D214484013-05012009><SPAN=20
    class=3D285020316-05012009>[snipped to the=20
  =
end]</SPAN></SPAN></FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C96F50.704BA132--

--===============0334680802==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0334680802==--


From pwe3-bounces@ietf.org  Mon Jan  5 08:16:18 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D07E228C0FE;
	Mon,  5 Jan 2009 08:16:18 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B8E3D28C0FE
	for <pwe3@core3.amsl.com>; Mon,  5 Jan 2009 08:16:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.757
X-Spam-Level: 
X-Spam-Status: No, score=-5.757 tagged_above=-999 required=5 tests=[AWL=0.841, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 ZnR++CeMGGCI for <pwe3@core3.amsl.com>;
	Mon,  5 Jan 2009 08:16:16 -0800 (PST)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56])
	by core3.amsl.com (Postfix) with ESMTP id E60EF28C0FC
	for <pwe3@ietf.org>; Mon,  5 Jan 2009 08:16:14 -0800 (PST)
Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com
	[47.129.230.99])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	n05GCFh16776; Mon, 5 Jan 2009 16:12:15 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 Jan 2009 11:15:53 -0500
Message-ID: <87AC5F88F03E6249AEA68D40BD3E00BE16832699@zcarhxm2.corp.nortel.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C7698C2C6CDE7@ILPTMAIL02.ecitele.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: A question regarding torn down PWs in
	draft-ietf-pwe3-oam-msg-map-08.txt
Thread-Index: AclvHgFatl4xVjfUTBai2RqcqunEfwAHTX0AAADXDMAABCyFYA==
References: <A3C5DF08D38B6049839A6F553B331C7698C2C6CCC1@ILPTMAIL02.ecitele.com>
	<E60778C3916D3548BBCF4D964186348F022953BD@ILEXC2U01.ndc.lucent.com>
	<A3C5DF08D38B6049839A6F553B331C7698C2C6CDE7@ILPTMAIL02.ecitele.com>
From: "David Allan" <dallan@nortel.com>
To: "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>,
	"Busschbach, Peter B (Peter)" <busschbach@alcatel-lucent.com>
Cc: Shell Nakash <Shell.Nakash@ecitele.com>, lmartini@cisco.com,
	mmorrow@cisco.com, Igor Danilovich <Igor.Danilovich@ecitele.com>,
	pwe3@ietf.org, "Aissaoui,
	Mustapha \(Mustapha\)" <mustapha.aissaoui@alcatel-lucent.com>,
	Itamar Levy <Itamar.Levy@ecitele.com>
Subject: Re: [PWE3] A question regarding torn down PWs in
	draft-ietf-pwe3-oam-msg-map-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1250470756=="
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1250470756==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C96F50.E1B760C9"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C96F50.E1B760C9
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

hi Peter:
=20
Below you suggest that FDI not be inserted when a PW is taken down
administratively. I do not understand why this is different from any
other disruption of connectivity, unless it is beleived that an
administrative action is joined up across both MPLS PWs and the native
service by other means....
=20
Am I missing somthing?
=20
cheers
Dave
=20
=20
=20
=20
________________________________

From: Alexander Vainshtein [mailto:Alexander.Vainshtein@ecitele.com]=20
Sent: Monday, January 05, 2009 10:09 AM
To: Busschbach, Peter B (Peter)
Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor Danilovich; Itamar
Levy; Aissaoui, Mustapha (Mustapha); Allan, David (CAR:NS00);
lmartini@cisco.com; Thomas D. Nadeau; mmorrow@cisco.com
Subject: RE: A question regarding torn down PWs in
draft-ietf-pwe3-oam-msg-map-08.txt


Peter hi,
Lots of thanks for a prompt response.
=20
Please see some comments inline below (blue italics).
=20
Regards,
    Sasha


________________________________

	From: Busschbach, Peter B (Peter)
[mailto:busschbach@alcatel-lucent.com]=20
	Sent: Monday, January 05, 2009 3:51 PM
	To: Alexander Vainshtein; Aissaoui, Mustapha (Mustapha);
dallan@nortel.com; lmartini@cisco.com; Thomas D. Nadeau;
mmorrow@cisco.com
	Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor
Danilovich; Itamar Levy
	Subject: RE: A question regarding torn down PWs in
draft-ietf-pwe3-oam-msg-map-08.txt
=09
=09
	Hi Sasha,
	=20
	>> Does the quoted text imply that implementations must
distinguish between PWs being torn down
	>> due to failures of their control sessions and PWs that are
torn down for any other reason?
	=20
	Whether PWs are torn down because of a defect (whether it is in
the control plane or in the data plane), the consequent actions are the
same.
	[[Sasha]] I am not aware of the case when a PW is torn down due
to defects in the data plane. Could you please provide a reference/an
example?
	 It would be good, however, if a PE would be able to distinguish
between PWs torn down because of defects and PWs torn down for
administrative reasons, because in the latter case there is no need to
insert an FDI message downstream.
	[[Sasha]] I do not think that RFC 4447 provides for that. In
addition, please consider the following scenario:

	1.	A PW is set up=20
	2.	The PW is torn down due to the CP defect (targeted LDP
session went down). FDI is inserted in the local AC=20
	3.	 The user has deleted the PW end point in the remote PE.
Since the LDP session is down, this fact is not communicated to the
local PE=20
	4.	Targeted LDP session is restored but an attempt of the
local PE to restore the PW fails since there is no remote peer anymore.
What should now happen to the local AC?

	=20
	Remember that Luca sent an email to the list proposing to add a
BFD code point to indicate that an AC was taken down for admistrative
reasons. That proposal was driven by the same motivation.
	[[Sasha]] I remember that, and I believe I've sent a couple of
messages to the list questioning the rationale of such a code point. =20
	=20
	Peter
	=20
	=20

________________________________

		From: Alexander Vainshtein
[mailto:Alexander.Vainshtein@ecitele.com]=20
		Sent: Monday, January 05, 2009 5:12 AM
		To: Aissaoui, Mustapha (Mustapha); Busschbach, Peter B
(Peter); dallan@nortel.com; lmartini@cisco.com; Thomas D. Nadeau;
mmorrow@cisco.com
		Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor
Danilovich; Itamar Levy
		Subject: A question regarding torn down PWs in
draft-ietf-pwe3-oam-msg-map-08.txt
	=09
	=09
		Hi Monique/Mustapha/Peter/Dave/Thom/Luca,
		I have a question to you as the editors of the expired)
draft-ietf-pwe3-oam-msg-map-08.txt.
		The question is related to the following text in Section
8.2.1. PW Forward Defect State Entry/Exit Criteria:
		<quote>

			   Note that if the PW control session between
the PEs fails, the PW is=20
			   torn down and needs to be re-established.
This includes failure of=20
			   the T-LDP session, the L2TP session, or the
L2TP control connection.=20
			   However, the consequent actions towards the
ACs are the same as if=20
			   the PW entered the forward defect state.

		<end quote>
		The PW may be torn down not just because the PW control
session between the PEs fails. E.g., the PW can be deleted by the
operator in one of the PEs.
		Does the quoted text imply that implementations must
distinguish between PWs being torn down due to failures of their control
sessions and PWs that are torn down for any other reason?
		The use case of special interest would be a PW that has
been set up (and later torn down) using a single-sided mechanism...
		I'd also like to note that there are several references
in the draft to unspecified defects  "that do not result in the PW being
torn down"...
		=20
		Regards,
		     Sasha
		=20
		=20


------_=_NextPart_001_01C96F50.E1B760C9
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3492" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D746210416-05012009>hi=20
Peter:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D746210416-05012009>Below=20
you suggest that FDI not be inserted when a PW is taken down=20
administratively.&nbsp;I do not understand why this is&nbsp;different =
from any=20
other disruption of connectivity, unless it is beleived that an =
administrative=20
action is joined up across both MPLS PWs&nbsp;and the native service by =
other=20
means....</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D746210416-05012009>Am I=20
missing somthing?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D746210416-05012009>cheers</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D746210416-05012009>Dave</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Alexander Vainshtein=20
[mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> Monday, =
January 05,=20
2009 10:09 AM<BR><B>To:</B> Busschbach, Peter B (Peter)<BR><B>Cc:</B>=20
pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor Danilovich; Itamar =
Levy;=20
Aissaoui, Mustapha (Mustapha); Allan, David (CAR:NS00); =
lmartini@cisco.com;=20
Thomas D. Nadeau; mmorrow@cisco.com<BR><B>Subject:</B> RE: A question =
regarding=20
torn down PWs in draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D017510414-05012009>Peter=20
hi,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D017510414-05012009>Lots=20
of thanks for a prompt response.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D017510414-05012009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D017510414-05012009>Please=20
see some comments inline below (<EM>blue =
italics</EM>).</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D017510414-05012009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D017510414-05012009>Regards,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D017510414-05012009>&nbsp;&nbsp;&nbsp; =
Sasha</SPAN></FONT></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Busschbach, Peter B (Peter)=20
  [mailto:busschbach@alcatel-lucent.com] <BR><B>Sent:</B> Monday, =
January 05,=20
  2009 3:51 PM<BR><B>To:</B> Alexander Vainshtein; Aissaoui, Mustapha=20
  (Mustapha); dallan@nortel.com; lmartini@cisco.com; Thomas D. Nadeau;=20
  mmorrow@cisco.com<BR><B>Cc:</B> pwe3@ietf.org; Shell Nakash; Prashant =
Desai;=20
  Igor Danilovich; Itamar Levy<BR><B>Subject:</B> RE: A question =
regarding torn=20
  down PWs in draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT =
face=3DArial=20
  size=3D2>Hi Sasha,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT =
face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT =
face=3DArial=20
  size=3D2>&gt;&gt; <SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>Does=20
  the quoted text imply that implementations must distinguish between =
PWs being=20
  torn down</FONT></SPAN></FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT =
face=3DArial=20
  size=3D2><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>&gt;&gt; due to=20
  failures of their control sessions and PWs that are torn down for any =
other=20
  reason?</FONT></SPAN></FONT></SPAN></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D214484013-05012009>Whether&nbsp;PWs=20
  are torn down because of a defect (whether it is in the control plane =
or in=20
  the data plane), the consequent actions are the same.<BR><SPAN=20
  class=3D017510414-05012009><FONT color=3D#0000ff><EM>[[Sasha]]&nbsp;I =
am not aware=20
  of the case when a PW is torn down due to defects in the data plane. =
Could you=20
  please provide a reference/an =
example?</EM></FONT></SPAN></SPAN></FONT></DIV>
  <DIV><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2>&nbsp;It=20
  would be good, however, if a PE would be able to distinguish between =
PWs torn=20
  down because of defects and PWs torn down for administrative reasons, =
because=20
  in the latter case there is no need to insert an FDI message=20
  downstream.<BR><SPAN class=3D017510414-05012009><FONT=20
  color=3D#0000ff><EM>[[Sasha]]&nbsp;I do not think that RFC 4447 =
provides for=20
  that.&nbsp;In addition, please consider the following=20
  scenario:</EM></FONT></SPAN></FONT></FONT></SPAN></DIV>
  <OL>
    <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2><SPAN=20
    class=3D017510414-05012009><FONT color=3D#0000ff><EM>A PW is set=20
    up</EM></FONT></SPAN></FONT></FONT></SPAN>=20
    <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2><SPAN=20
    class=3D017510414-05012009><FONT color=3D#0000ff><EM>The PW is torn=20
    down&nbsp;due to the CP defect (targeted LDP session went down). FDI =
is=20
    inserted in the local AC</EM></FONT></SPAN></FONT></FONT></SPAN>=20
    <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2><SPAN=20
    class=3D017510414-05012009><EM>&nbsp;<FONT color=3D#0000ff>The user =
has deleted=20
    the PW end point in the remote PE. Since the LDP session is down, =
this fact=20
    is not communicated to the local =
PE</FONT></EM></SPAN></FONT></FONT></SPAN>=20
    <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
color=3D#0000ff=20
    size=3D2><SPAN class=3D017510414-05012009><EM>Targeted LDP session =
is restored=20
    but an attempt of the local PE to restore the PW fails since there =
is no=20
    remote peer anymore. <STRONG>What should now happen to the local=20
    AC</STRONG>?</EM></SPAN></FONT></FONT></SPAN></LI></OL>
  <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
  class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
  <DIV><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2>Remember=20
  that Luca sent an email to the list proposing to add a BFD code point =
to=20
  indicate that an AC was taken down for admistrative reasons. That =
proposal was=20
  driven by the same motivation.<BR><SPAN =
class=3D017510414-05012009><FONT=20
  color=3D#0000ff><EM>[[Sasha]]&nbsp;I&nbsp;remember that, and I believe =
I've sent=20
  a couple of messages to the list questioning the rationale =
of&nbsp;such a code=20
  point. &nbsp;</EM></FONT></SPAN></FONT></FONT></SPAN></DIV>
  <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
  class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
  class=3D214484013-05012009>Peter</SPAN></FONT></FONT></DIV>
  <DIV><FONT size=3D2><SPAN =
class=3D214484013-05012009></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT size=3D2><SPAN =
class=3D214484013-05012009></SPAN></FONT>&nbsp;</DIV>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> Alexander Vainshtein=20
    [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> Monday, =
January=20
    05, 2009 5:12 AM<BR><B>To:</B> Aissaoui, Mustapha (Mustapha); =
Busschbach,=20
    Peter B (Peter); dallan@nortel.com; lmartini@cisco.com; Thomas D. =
Nadeau;=20
    mmorrow@cisco.com<BR><B>Cc:</B> pwe3@ietf.org; Shell Nakash; =
Prashant Desai;=20
    Igor Danilovich; Itamar Levy<BR><B>Subject:</B> A question regarding =
torn=20
    down PWs in draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>Hi =

    Monique/Mustapha/Peter/Dave/Thom/Luca,</FONT></SPAN></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial size=3D2>I =
have a=20
    question to you as the editors of the expired)=20
    draft-ietf-pwe3-oam-msg-map-08.txt.</FONT></SPAN></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>The question is=20
    related&nbsp;to the following text in Section <STRONG>8.2.1. PW =
Forward=20
    Defect State Entry/Exit Criteria</STRONG>:</FONT></SPAN></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
    size=3D2>&lt;quote&gt;</FONT></SPAN></DIV>
    <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
      <DIV><SPAN class=3D012494009-05012009><EM><FONT =
color=3D#0000ff>&nbsp;&nbsp;=20
      Note that if the PW control session between the PEs fails, the PW =
is=20
      <BR>&nbsp;&nbsp; torn down and needs to be re-established. This =
includes=20
      failure of <BR>&nbsp;&nbsp; the T-LDP session, the L2TP session, =
or the=20
      L2TP control connection. <BR>&nbsp;&nbsp; However, the consequent =
actions=20
      towards the ACs are the same as if <BR>&nbsp;&nbsp; the PW entered =
the=20
      forward defect state.</FONT></EM></SPAN></DIV></BLOCKQUOTE>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>&lt;end=20
    quote&gt;</FONT></SPAN></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>The PW may be=20
    torn down not just because the PW control session between the PEs =
fails.=20
    E.g., the PW can be deleted by the operator in one of the=20
    PEs.</FONT></SPAN></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>Does the quoted=20
    text imply that implementations must distinguish between PWs being =
torn down=20
    due to failures of their control sessions and PWs that are torn down =
for any=20
    other reason?</FONT></SPAN></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>The use case of=20
    special interest would be a PW that has been set up (and later torn =
down)=20
    using a single-sided mechanism...</FONT></SPAN></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>I'd also like to=20
    note that there are several references in the draft to unspecified=20
    defects&nbsp;<EM><FONT color=3D#0000ff> "that do not result in the =
PW being=20
    torn down</FONT></EM>"...</FONT></SPAN></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
    size=3D2>Regards,</FONT></SPAN></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</FONT></SPAN></DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
    =
size=3D2></FONT></SPAN>&nbsp;</DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTM=
L>

------_=_NextPart_001_01C96F50.E1B760C9--

--===============1250470756==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1250470756==--


From pwe3-bounces@ietf.org  Mon Jan  5 08:37:51 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 36CCB28C0E0;
	Mon,  5 Jan 2009 08:37:51 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AD3073A68F0
	for <pwe3@core3.amsl.com>; Mon,  5 Jan 2009 08:37:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 hY+rN55I3MwM for <pwe3@core3.amsl.com>;
	Mon,  5 Jan 2009 08:37:48 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33])
	by core3.amsl.com (Postfix) with ESMTP id 199C43A6907
	for <pwe3@ietf.org>; Mon,  5 Jan 2009 08:37:47 -0800 (PST)
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id n05GbESA001830;
	Mon, 5 Jan 2009 10:37:14 -0600 (CST)
Received: from ILEXC2U01.ndc.lucent.com ([135.3.39.9]) by
	ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 10:37:14 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 Jan 2009 10:37:11 -0600
Message-ID: <E60778C3916D3548BBCF4D964186348F02295525@ILEXC2U01.ndc.lucent.com>
In-Reply-To: <87AC5F88F03E6249AEA68D40BD3E00BE16832699@zcarhxm2.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: A question regarding torn down PWs in
	draft-ietf-pwe3-oam-msg-map-08.txt
Thread-Index: AclvHgFatl4xVjfUTBai2RqcqunEfwAHTX0AAADXDMAABCyFYAAAnjpg
References: <A3C5DF08D38B6049839A6F553B331C7698C2C6CCC1@ILPTMAIL02.ecitele.com>
	<E60778C3916D3548BBCF4D964186348F022953BD@ILEXC2U01.ndc.lucent.com>
	<A3C5DF08D38B6049839A6F553B331C7698C2C6CDE7@ILPTMAIL02.ecitele.com>
	<87AC5F88F03E6249AEA68D40BD3E00BE16832699@zcarhxm2.corp.nortel.com>
From: "Busschbach, Peter B \(Peter\)" <busschbach@alcatel-lucent.com>
To: "David Allan" <dallan@nortel.com>,
	"Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>
X-OriginalArrivalTime: 05 Jan 2009 16:37:14.0267 (UTC)
	FILETIME=[DD4ED6B0:01C96F53]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Cc: Shell Nakash <Shell.Nakash@ecitele.com>, lmartini@cisco.com,
	mmorrow@cisco.com, Igor Danilovich <Igor.Danilovich@ecitele.com>,
	pwe3@ietf.org, "Aissaoui,
	Mustapha \(Mustapha\)" <mustapha.aissaoui@alcatel-lucent.com>,
	Itamar Levy <Itamar.Levy@ecitele.com>
Subject: Re: [PWE3] A question regarding torn down PWs in
	draft-ietf-pwe3-oam-msg-map-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1797243946=="
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1797243946==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C96F53.DCD5AB6A"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C96F53.DCD5AB6A
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dave,
=20
I seem to remember from discussions in ITU-T about Ethernet OAM that an
administrative action should not result in AIS insertion. To be honest,
I can't remember why, though. Therefore, unless someone else knows a
reason why administrative down should not result in AIS, I withdraw my
comment.
=20
Peter


________________________________

	From: David Allan [mailto:dallan@nortel.com]=20
	Sent: Monday, January 05, 2009 11:16 AM
	To: Alexander Vainshtein; Busschbach, Peter B (Peter)
	Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor
Danilovich; Itamar Levy; Aissaoui, Mustapha (Mustapha);
lmartini@cisco.com; Thomas D. Nadeau; mmorrow@cisco.com
	Subject: RE: A question regarding torn down PWs in
draft-ietf-pwe3-oam-msg-map-08.txt
=09
=09
	hi Peter:
	=20
	Below you suggest that FDI not be inserted when a PW is taken
down administratively. I do not understand why this is different from
any other disruption of connectivity, unless it is beleived that an
administrative action is joined up across both MPLS PWs and the native
service by other means....
	=20
	Am I missing somthing?
	=20
	cheers
	Dave
	=20
	=20
	=20
	=20
________________________________

	From: Alexander Vainshtein
[mailto:Alexander.Vainshtein@ecitele.com]=20
	Sent: Monday, January 05, 2009 10:09 AM
	To: Busschbach, Peter B (Peter)
	Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor
Danilovich; Itamar Levy; Aissaoui, Mustapha (Mustapha); Allan, David
(CAR:NS00); lmartini@cisco.com; Thomas D. Nadeau; mmorrow@cisco.com
	Subject: RE: A question regarding torn down PWs in
draft-ietf-pwe3-oam-msg-map-08.txt
=09
=09
	Peter hi,
	Lots of thanks for a prompt response.
	=20
	Please see some comments inline below (blue italics).
	=20
	Regards,
	    Sasha


________________________________

		From: Busschbach, Peter B (Peter)
[mailto:busschbach@alcatel-lucent.com]=20
		Sent: Monday, January 05, 2009 3:51 PM
		To: Alexander Vainshtein; Aissaoui, Mustapha (Mustapha);
dallan@nortel.com; lmartini@cisco.com; Thomas D. Nadeau;
mmorrow@cisco.com
		Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor
Danilovich; Itamar Levy
		Subject: RE: A question regarding torn down PWs in
draft-ietf-pwe3-oam-msg-map-08.txt
	=09
	=09
		Hi Sasha,
		=20
		>> Does the quoted text imply that implementations must
distinguish between PWs being torn down
		>> due to failures of their control sessions and PWs
that are torn down for any other reason?
		=20
		Whether PWs are torn down because of a defect (whether
it is in the control plane or in the data plane), the consequent actions
are the same.
		[[Sasha]] I am not aware of the case when a PW is torn
down due to defects in the data plane. Could you please provide a
reference/an example?
		 It would be good, however, if a PE would be able to
distinguish between PWs torn down because of defects and PWs torn down
for administrative reasons, because in the latter case there is no need
to insert an FDI message downstream.
		[[Sasha]] I do not think that RFC 4447 provides for
that. In addition, please consider the following scenario:

		1.	A PW is set up=20
		2.	The PW is torn down due to the CP defect
(targeted LDP session went down). FDI is inserted in the local AC=20
		3.	 The user has deleted the PW end point in the
remote PE. Since the LDP session is down, this fact is not communicated
to the local PE=20
		4.	Targeted LDP session is restored but an attempt
of the local PE to restore the PW fails since there is no remote peer
anymore. What should now happen to the local AC?

		=20
		Remember that Luca sent an email to the list proposing
to add a BFD code point to indicate that an AC was taken down for
admistrative reasons. That proposal was driven by the same motivation.
		[[Sasha]] I remember that, and I believe I've sent a
couple of messages to the list questioning the rationale of such a code
point. =20
		=20
		Peter
		=20
		=20

________________________________

			From: Alexander Vainshtein
[mailto:Alexander.Vainshtein@ecitele.com]=20
			Sent: Monday, January 05, 2009 5:12 AM
			To: Aissaoui, Mustapha (Mustapha); Busschbach,
Peter B (Peter); dallan@nortel.com; lmartini@cisco.com; Thomas D.
Nadeau; mmorrow@cisco.com
			Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai;
Igor Danilovich; Itamar Levy
			Subject: A question regarding torn down PWs in
draft-ietf-pwe3-oam-msg-map-08.txt
		=09
		=09
			Hi Monique/Mustapha/Peter/Dave/Thom/Luca,
			I have a question to you as the editors of the
expired) draft-ietf-pwe3-oam-msg-map-08.txt.
			The question is related to the following text in
Section 8.2.1. PW Forward Defect State Entry/Exit Criteria:
			<quote>

				   Note that if the PW control session
between the PEs fails, the PW is=20
				   torn down and needs to be
re-established. This includes failure of=20
				   the T-LDP session, the L2TP session,
or the L2TP control connection.=20
				   However, the consequent actions
towards the ACs are the same as if=20
				   the PW entered the forward defect
state.

			<end quote>
			The PW may be torn down not just because the PW
control session between the PEs fails. E.g., the PW can be deleted by
the operator in one of the PEs.
			Does the quoted text imply that implementations
must distinguish between PWs being torn down due to failures of their
control sessions and PWs that are torn down for any other reason?
			The use case of special interest would be a PW
that has been set up (and later torn down) using a single-sided
mechanism...
			I'd also like to note that there are several
references in the draft to unspecified defects  "that do not result in
the PW being torn down"...
			=20
			Regards,
			     Sasha
			=20
			=20


------_=_NextPart_001_01C96F53.DCD5AB6A
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3243" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
size=3D2>Dave,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial size=3D2>I=20
seem to remember from discussions in ITU-T about Ethernet OAM that an=20
administrative action should not result in AIS insertion. To be honest, =
I can't=20
remember why, though. Therefore, unless someone else knows a reason why=20
administrative down should not result in AIS, I withdraw my=20
comment.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
size=3D2>Peter</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> David Allan =
[mailto:dallan@nortel.com]=20
  <BR><B>Sent:</B> Monday, January 05, 2009 11:16 AM<BR><B>To:</B> =
Alexander=20
  Vainshtein; Busschbach, Peter B (Peter)<BR><B>Cc:</B> pwe3@ietf.org; =
Shell=20
  Nakash; Prashant Desai; Igor Danilovich; Itamar Levy; Aissaoui, =
Mustapha=20
  (Mustapha); lmartini@cisco.com; Thomas D. Nadeau;=20
  mmorrow@cisco.com<BR><B>Subject:</B> RE: A question regarding torn =
down PWs in=20
  draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D746210416-05012009>hi=20
  Peter:</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D746210416-05012009>Below you suggest that FDI not be inserted =
when a PW=20
  is taken down administratively.&nbsp;I do not understand why this=20
  is&nbsp;different from any other disruption of connectivity, unless it =
is=20
  beleived that an administrative action is joined up across both MPLS=20
  PWs&nbsp;and the native service by other means....</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D746210416-05012009>Am I=20
  missing somthing?</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D746210416-05012009>cheers</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D746210416-05012009>Dave</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Alexander Vainshtein=20
  [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> Monday, =
January 05,=20
  2009 10:09 AM<BR><B>To:</B> Busschbach, Peter B (Peter)<BR><B>Cc:</B>=20
  pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor Danilovich; Itamar =
Levy;=20
  Aissaoui, Mustapha (Mustapha); Allan, David (CAR:NS00); =
lmartini@cisco.com;=20
  Thomas D. Nadeau; mmorrow@cisco.com<BR><B>Subject:</B> RE: A question=20
  regarding torn down PWs in=20
  draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D017510414-05012009>Peter hi,</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D017510414-05012009>Lots=20
  of thanks for a prompt response.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D017510414-05012009></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D017510414-05012009>Please see some comments inline below =
(<EM>blue=20
  italics</EM>).</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D017510414-05012009></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D017510414-05012009>Regards,</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D017510414-05012009>&nbsp;&nbsp;&nbsp; =
Sasha</SPAN></FONT></DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> Busschbach, Peter B =
(Peter)=20
    [mailto:busschbach@alcatel-lucent.com] <BR><B>Sent:</B> Monday, =
January 05,=20
    2009 3:51 PM<BR><B>To:</B> Alexander Vainshtein; Aissaoui, Mustapha=20
    (Mustapha); dallan@nortel.com; lmartini@cisco.com; Thomas D. Nadeau; =

    mmorrow@cisco.com<BR><B>Cc:</B> pwe3@ietf.org; Shell Nakash; =
Prashant Desai;=20
    Igor Danilovich; Itamar Levy<BR><B>Subject:</B> RE: A question =
regarding=20
    torn down PWs in =
draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT =
face=3DArial=20
    size=3D2>Hi Sasha,</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT =
face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT =
face=3DArial=20
    size=3D2>&gt;&gt; <SPAN class=3D012494009-05012009><FONT =
face=3DArial size=3D2>Does=20
    the quoted text imply that implementations must distinguish between =
PWs=20
    being torn down</FONT></SPAN></FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT =
face=3DArial=20
    size=3D2><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>&gt;&gt; due=20
    to failures of their control sessions and PWs that are torn down for =
any=20
    other reason?</FONT></SPAN></FONT></SPAN></DIV>
    <DIV>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D214484013-05012009>Whether&nbsp;PWs=20
    are torn down because of a defect (whether it is in the control =
plane or in=20
    the data plane), the consequent actions are the same.<BR><SPAN=20
    class=3D017510414-05012009><FONT =
color=3D#0000ff><EM>[[Sasha]]&nbsp;I am not=20
    aware of the case when a PW is torn down due to defects in the data =
plane.=20
    Could you please provide a reference/an=20
    example?</EM></FONT></SPAN></SPAN></FONT></DIV>
    <DIV><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2>&nbsp;It=20
    would be good, however, if a PE would be able to distinguish between =
PWs=20
    torn down because of defects and PWs torn down for administrative =
reasons,=20
    because in the latter case there is no need to insert an FDI message =

    downstream.<BR><SPAN class=3D017510414-05012009><FONT=20
    color=3D#0000ff><EM>[[Sasha]]&nbsp;I do not think that RFC 4447 =
provides for=20
    that.&nbsp;In addition, please consider the following=20
    scenario:</EM></FONT></SPAN></FONT></FONT></SPAN></DIV>
    <OL>
      <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2><SPAN=20
      class=3D017510414-05012009><FONT color=3D#0000ff><EM>A PW is set=20
      up</EM></FONT></SPAN></FONT></FONT></SPAN>=20
      <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2><SPAN=20
      class=3D017510414-05012009><FONT color=3D#0000ff><EM>The PW is =
torn=20
      down&nbsp;due to the CP defect (targeted LDP session went down). =
FDI is=20
      inserted in the local AC</EM></FONT></SPAN></FONT></FONT></SPAN>=20
      <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2><SPAN=20
      class=3D017510414-05012009><EM>&nbsp;<FONT color=3D#0000ff>The =
user has=20
      deleted the PW end point in the remote PE. Since the LDP session =
is down,=20
      this fact is not communicated to the local=20
      PE</FONT></EM></SPAN></FONT></FONT></SPAN>=20
      <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
color=3D#0000ff=20
      size=3D2><SPAN class=3D017510414-05012009><EM>Targeted LDP session =
is restored=20
      but an attempt of the local PE to restore the PW fails since there =
is no=20
      remote peer anymore. <STRONG>What should now happen to the local=20
      AC</STRONG>?</EM></SPAN></FONT></FONT></SPAN></LI></OL>
    <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
    class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
    <DIV><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2>Remember=20
    that Luca sent an email to the list proposing to add a BFD code =
point to=20
    indicate that an AC was taken down for admistrative reasons. That =
proposal=20
    was driven by the same motivation.<BR><SPAN =
class=3D017510414-05012009><FONT=20
    color=3D#0000ff><EM>[[Sasha]]&nbsp;I&nbsp;remember that, and I =
believe I've=20
    sent a couple of messages to the list questioning the rationale =
of&nbsp;such=20
    a code point. &nbsp;</EM></FONT></SPAN></FONT></FONT></SPAN></DIV>
    <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
    class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
    class=3D214484013-05012009>Peter</SPAN></FONT></FONT></DIV>
    <DIV><FONT size=3D2><SPAN =
class=3D214484013-05012009></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT size=3D2><SPAN =
class=3D214484013-05012009></SPAN></FONT>&nbsp;</DIV>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 =
2px solid; MARGIN-RIGHT: 0px">
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
      <HR tabIndex=3D-1>
      <FONT face=3DTahoma size=3D2><B>From:</B> Alexander Vainshtein=20
      [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> Monday, =
January=20
      05, 2009 5:12 AM<BR><B>To:</B> Aissaoui, Mustapha (Mustapha); =
Busschbach,=20
      Peter B (Peter); dallan@nortel.com; lmartini@cisco.com; Thomas D. =
Nadeau;=20
      mmorrow@cisco.com<BR><B>Cc:</B> pwe3@ietf.org; Shell Nakash; =
Prashant=20
      Desai; Igor Danilovich; Itamar Levy<BR><B>Subject:</B> A question=20
      regarding torn down PWs in=20
      draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
      <DIV></DIV>
      <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>Hi=20
      Monique/Mustapha/Peter/Dave/Thom/Luca,</FONT></SPAN></DIV>
      <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>I have a=20
      question to you as the editors of the expired)=20
      draft-ietf-pwe3-oam-msg-map-08.txt.</FONT></SPAN></DIV>
      <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>The question=20
      is related&nbsp;to the following text in Section <STRONG>8.2.1. PW =
Forward=20
      Defect State Entry/Exit Criteria</STRONG>:</FONT></SPAN></DIV>
      <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
      size=3D2>&lt;quote&gt;</FONT></SPAN></DIV>
      <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
        <DIV><SPAN class=3D012494009-05012009><EM><FONT =
color=3D#0000ff>&nbsp;&nbsp;=20
        Note that if the PW control session between the PEs fails, the =
PW is=20
        <BR>&nbsp;&nbsp; torn down and needs to be re-established. This =
includes=20
        failure of <BR>&nbsp;&nbsp; the T-LDP session, the L2TP session, =
or the=20
        L2TP control connection. <BR>&nbsp;&nbsp; However, the =
consequent=20
        actions towards the ACs are the same as if <BR>&nbsp;&nbsp; the =
PW=20
        entered the forward defect =
state.</FONT></EM></SPAN></DIV></BLOCKQUOTE>
      <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>&lt;end=20
      quote&gt;</FONT></SPAN></DIV>
      <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>The PW may be=20
      torn down not just because the PW control session between the PEs =
fails.=20
      E.g., the PW can be deleted by the operator in one of the=20
      PEs.</FONT></SPAN></DIV>
      <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>Does the=20
      quoted text imply that implementations must distinguish between =
PWs being=20
      torn down due to failures of their control sessions and PWs that =
are torn=20
      down for any other reason?</FONT></SPAN></DIV>
      <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>The use case=20
      of special interest would be a PW that has been set up (and later =
torn=20
      down) using a single-sided mechanism...</FONT></SPAN></DIV>
      <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>I'd also like=20
      to note that there are several references in the draft to =
unspecified=20
      defects&nbsp;<EM><FONT color=3D#0000ff> "that do not result in the =
PW being=20
      torn down</FONT></EM>"...</FONT></SPAN></DIV>
      <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
      size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
      size=3D2>Regards,</FONT></SPAN></DIV>
      <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
      size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</FONT></SPAN></DIV>
      <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
      size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
      =
size=3D2></FONT></SPAN>&nbsp;</DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE=
></BODY></HTML>

------_=_NextPart_001_01C96F53.DCD5AB6A--

--===============1797243946==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1797243946==--


From pwe3-bounces@ietf.org  Mon Jan  5 10:11:54 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 986A03A688B;
	Mon,  5 Jan 2009 10:11:54 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E222A28B23E
	for <pwe3@core3.amsl.com>; Mon,  5 Jan 2009 10:11:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[AWL=0.349, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 g9EqapFBSWEu for <pwe3@core3.amsl.com>;
	Mon,  5 Jan 2009 10:11:52 -0800 (PST)
Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150])
	by core3.amsl.com (Postfix) with ESMTP id A82DD3A63D2
	for <pwe3@ietf.org>; Mon,  5 Jan 2009 10:11:51 -0800 (PST)
Received: from E03MVB2-UKBR.domain1.systemhost.net ([193.113.197.108]) by
	smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 18:11:37 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 Jan 2009 18:11:22 -0000
Message-ID: <2ECAA42C79676B42AEBAC11229CA7D0C03DD68BF@E03MVB2-UKBR.domain1.systemhost.net>
In-Reply-To: <E60778C3916D3548BBCF4D964186348F02295525@ILEXC2U01.ndc.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] A question regarding torn down PWs
	indraft-ietf-pwe3-oam-msg-map-08.txt
thread-index: AclvHgFatl4xVjfUTBai2RqcqunEfwAHTX0AAADXDMAABCyFYAAAnjpgAAOeD4A=
From: <neil.2.harrison@bt.com>
To: <busschbach@alcatel-lucent.com>, <dallan@nortel.com>,
	<Alexander.Vainshtein@ecitele.com>
X-OriginalArrivalTime: 05 Jan 2009 18:11:37.0816 (UTC)
	FILETIME=[0D0BD580:01C96F61]
Cc: Shell.Nakash@ecitele.com, lmartini@cisco.com, mmorrow@cisco.com,
	Igor.Danilovich@ecitele.com, pwe3@ietf.org,
	mustapha.aissaoui@alcatel-lucent.com, Itamar.Levy@ecitele.com
Subject: Re: [PWE3] A question regarding torn down PWs
	indraft-ietf-pwe3-oam-msg-map-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0862495125=="
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0862495125==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C96F61.0CDD9FE5"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C96F61.0CDD9FE5
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Peter,
=20
I think I can answer your question wrt Ethernet at least.  AID/FDI has
no meaning whatsoever to a client cl-ps layer network....this is why
IEEE did not have AIS/FDI in 802.1ag. =20
=20
And as an aside:  AIS/FDI is almost essential/mandated in a co-cs layer
network...in the absence of traffic something MUST be sent in such
networks, and AIS/FDI =3D all 1s here is a throwback to TTL logic that
floated to binary 1 (+5V) under failures.  The merit of AIS/FDI is
debateable in a co-ps mode network.  However, in a cl-ps layer network
it has no meaning at all......since there is no server (connection) to
client (*connection*) association.
=20
regards, Neil


________________________________

	From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On
Behalf Of Busschbach, Peter B (Peter)
	Sent: 05 January 2009 16:37
	To: David Allan; Alexander Vainshtein
	Cc: Shell Nakash; lmartini@cisco.com; mmorrow@cisco.com; Igor
Danilovich; pwe3@ietf.org; Aissaoui, Mustapha (Mustapha); Itamar Levy
	Subject: Re: [PWE3] A question regarding torn down PWs
indraft-ietf-pwe3-oam-msg-map-08.txt
=09
=09
	Dave,
	=20
	I seem to remember from discussions in ITU-T about Ethernet OAM
that an administrative action should not result in AIS insertion. To be
honest, I can't remember why, though. Therefore, unless someone else
knows a reason why administrative down should not result in AIS, I
withdraw my comment.
	=20
	Peter


________________________________

		From: David Allan [mailto:dallan@nortel.com]=20
		Sent: Monday, January 05, 2009 11:16 AM
		To: Alexander Vainshtein; Busschbach, Peter B (Peter)
		Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor
Danilovich; Itamar Levy; Aissaoui, Mustapha (Mustapha);
lmartini@cisco.com; Thomas D. Nadeau; mmorrow@cisco.com
		Subject: RE: A question regarding torn down PWs in
draft-ietf-pwe3-oam-msg-map-08.txt
	=09
	=09
		hi Peter:
		=20
		Below you suggest that FDI not be inserted when a PW is
taken down administratively. I do not understand why this is different
from any other disruption of connectivity, unless it is beleived that an
administrative action is joined up across both MPLS PWs and the native
service by other means....
		=20
		Am I missing somthing?
		=20
		cheers
		Dave
		=20
		=20
		=20
		=20
________________________________

		From: Alexander Vainshtein
[mailto:Alexander.Vainshtein@ecitele.com]=20
		Sent: Monday, January 05, 2009 10:09 AM
		To: Busschbach, Peter B (Peter)
		Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor
Danilovich; Itamar Levy; Aissaoui, Mustapha (Mustapha); Allan, David
(CAR:NS00); lmartini@cisco.com; Thomas D. Nadeau; mmorrow@cisco.com
		Subject: RE: A question regarding torn down PWs in
draft-ietf-pwe3-oam-msg-map-08.txt
	=09
	=09
		Peter hi,
		Lots of thanks for a prompt response.
		=20
		Please see some comments inline below (blue italics).
		=20
		Regards,
		    Sasha


________________________________

			From: Busschbach, Peter B (Peter)
[mailto:busschbach@alcatel-lucent.com]=20
			Sent: Monday, January 05, 2009 3:51 PM
			To: Alexander Vainshtein; Aissaoui, Mustapha
(Mustapha); dallan@nortel.com; lmartini@cisco.com; Thomas D. Nadeau;
mmorrow@cisco.com
			Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai;
Igor Danilovich; Itamar Levy
			Subject: RE: A question regarding torn down PWs
in draft-ietf-pwe3-oam-msg-map-08.txt
		=09
		=09
			Hi Sasha,
			=20
			>> Does the quoted text imply that
implementations must distinguish between PWs being torn down
			>> due to failures of their control sessions and
PWs that are torn down for any other reason?
			=20
			Whether PWs are torn down because of a defect
(whether it is in the control plane or in the data plane), the
consequent actions are the same.
			[[Sasha]] I am not aware of the case when a PW
is torn down due to defects in the data plane. Could you please provide
a reference/an example?
			 It would be good, however, if a PE would be
able to distinguish between PWs torn down because of defects and PWs
torn down for administrative reasons, because in the latter case there
is no need to insert an FDI message downstream.
			[[Sasha]] I do not think that RFC 4447 provides
for that. In addition, please consider the following scenario:

			1.	A PW is set up=20
			2.	The PW is torn down due to the CP defect
(targeted LDP session went down). FDI is inserted in the local AC=20
			3.	 The user has deleted the PW end point
in the remote PE. Since the LDP session is down, this fact is not
communicated to the local PE=20
			4.	Targeted LDP session is restored but an
attempt of the local PE to restore the PW fails since there is no remote
peer anymore. What should now happen to the local AC?

			=20
			Remember that Luca sent an email to the list
proposing to add a BFD code point to indicate that an AC was taken down
for admistrative reasons. That proposal was driven by the same
motivation.
			[[Sasha]] I remember that, and I believe I've
sent a couple of messages to the list questioning the rationale of such
a code point. =20
			=20
			Peter
			=20
			=20

________________________________

				From: Alexander Vainshtein
[mailto:Alexander.Vainshtein@ecitele.com]=20
				Sent: Monday, January 05, 2009 5:12 AM
				To: Aissaoui, Mustapha (Mustapha);
Busschbach, Peter B (Peter); dallan@nortel.com; lmartini@cisco.com;
Thomas D. Nadeau; mmorrow@cisco.com
				Cc: pwe3@ietf.org; Shell Nakash;
Prashant Desai; Igor Danilovich; Itamar Levy
				Subject: A question regarding torn down
PWs in draft-ietf-pwe3-oam-msg-map-08.txt
			=09
			=09
				Hi
Monique/Mustapha/Peter/Dave/Thom/Luca,
				I have a question to you as the editors
of the expired) draft-ietf-pwe3-oam-msg-map-08.txt.
				The question is related to the following
text in Section 8.2.1. PW Forward Defect State Entry/Exit Criteria:
				<quote>

				   Note that if the PW control session
between the PEs fails, the PW is=20
				   torn down and needs to be
re-established. This includes failure of=20
				   the T-LDP session, the L2TP session,
or the L2TP control connection.=20
				   However, the consequent actions
towards the ACs are the same as if=20
				   the PW entered the forward defect
state.

				<end quote>
				The PW may be torn down not just because
the PW control session between the PEs fails. E.g., the PW can be
deleted by the operator in one of the PEs.
				Does the quoted text imply that
implementations must distinguish between PWs being torn down due to
failures of their control sessions and PWs that are torn down for any
other reason?
				The use case of special interest would
be a PW that has been set up (and later torn down) using a single-sided
mechanism...
				I'd also like to note that there are
several references in the draft to unspecified defects  "that do not
result in the PW being torn down"...
				=20
				Regards,
				     Sasha
				=20
				=20


------_=_NextPart_001_01C96F61.0CDD9FE5
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2769" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D243380518-05012009><FONT=20
face=3D"Comic Sans MS" color=3D#800000 =
size=3D2>Peter,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D243380518-05012009><FONT=20
face=3D"Comic Sans MS" color=3D#800000 =
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D243380518-05012009><FONT=20
face=3D"Comic Sans MS" color=3D#800000 size=3D2>I think I can answer =
your question wrt=20
Ethernet at least.&nbsp; AID/FDI has no meaning whatsoever to a client =
cl-ps=20
layer network....this is why IEEE did not have AIS/FDI in 802.1ag.&nbsp; =

</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D243380518-05012009><FONT=20
face=3D"Comic Sans MS" color=3D#800000 =
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D243380518-05012009><FONT=20
face=3D"Comic Sans MS" color=3D#800000 size=3D2>And as an aside:&nbsp; =
AIS/FDI is=20
almost essential/mandated in a co-cs layer network...in the absence of =
traffic=20
something MUST be sent in such networks, and AIS/FDI =3D all 1s here is =
a=20
throwback to TTL logic that floated to binary 1 (+5V) under =
failures.&nbsp; The=20
merit of AIS/FDI is debateable in a co-ps mode network.&nbsp; However, =
in a=20
cl-ps layer network it has no meaning at all......since there is no =
server=20
(connection) to client (*connection*) association.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D243380518-05012009><FONT=20
face=3D"Comic Sans MS" color=3D#800000 =
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D243380518-05012009><FONT=20
face=3D"Comic Sans MS" color=3D#800000 size=3D2>regards, =
Neil</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #800000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> pwe3-bounces@ietf.org=20
  [mailto:pwe3-bounces@ietf.org] <B>On Behalf Of </B>Busschbach, Peter B =

  (Peter)<BR><B>Sent:</B> 05 January 2009 16:37<BR><B>To:</B> David =
Allan;=20
  Alexander Vainshtein<BR><B>Cc:</B> Shell Nakash; lmartini@cisco.com;=20
  mmorrow@cisco.com; Igor Danilovich; pwe3@ietf.org; Aissaoui, Mustapha=20
  (Mustapha); Itamar Levy<BR><B>Subject:</B> Re: [PWE3] A question =
regarding=20
  torn down PWs =
indraft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
  size=3D2>Dave,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
  size=3D2>I seem to remember from discussions in ITU-T about Ethernet =
OAM that an=20
  administrative action should not result in AIS insertion. To be =
honest, I=20
  can't remember why, though. Therefore, unless someone else knows a =
reason why=20
  administrative down should not result in AIS, I withdraw my=20
  comment.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
  size=3D2>Peter</FONT></SPAN></DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> David Allan =
[mailto:dallan@nortel.com]=20
    <BR><B>Sent:</B> Monday, January 05, 2009 11:16 AM<BR><B>To:</B> =
Alexander=20
    Vainshtein; Busschbach, Peter B (Peter)<BR><B>Cc:</B> pwe3@ietf.org; =
Shell=20
    Nakash; Prashant Desai; Igor Danilovich; Itamar Levy; Aissaoui, =
Mustapha=20
    (Mustapha); lmartini@cisco.com; Thomas D. Nadeau;=20
    mmorrow@cisco.com<BR><B>Subject:</B> RE: A question regarding torn =
down PWs=20
    in draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D746210416-05012009>hi=20
    Peter:</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D746210416-05012009>Below you suggest that FDI not be =
inserted when a=20
    PW is taken down administratively.&nbsp;I do not understand why this =

    is&nbsp;different from any other disruption of connectivity, unless =
it is=20
    beleived that an administrative action is joined up across both MPLS =

    PWs&nbsp;and the native service by other =
means....</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D746210416-05012009>Am=20
    I missing somthing?</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D746210416-05012009>cheers</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D746210416-05012009>Dave</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> Alexander Vainshtein=20
    [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> Monday, =
January=20
    05, 2009 10:09 AM<BR><B>To:</B> Busschbach, Peter B =
(Peter)<BR><B>Cc:</B>=20
    pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor Danilovich; Itamar =
Levy;=20
    Aissaoui, Mustapha (Mustapha); Allan, David (CAR:NS00); =
lmartini@cisco.com;=20
    Thomas D. Nadeau; mmorrow@cisco.com<BR><B>Subject:</B> RE: A =
question=20
    regarding torn down PWs in=20
    draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D017510414-05012009>Peter hi,</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D017510414-05012009>Lots of thanks for a prompt=20
    response.</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D017510414-05012009></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D017510414-05012009>Please see some comments inline below =
(<EM>blue=20
    italics</EM>).</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D017510414-05012009></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D017510414-05012009>Regards,</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D017510414-05012009>&nbsp;&nbsp;&nbsp; =
Sasha</SPAN></FONT></DIV><BR>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff =
2px solid; MARGIN-RIGHT: 0px">
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
      <HR tabIndex=3D-1>
      <FONT face=3DTahoma size=3D2><B>From:</B> Busschbach, Peter B =
(Peter)=20
      [mailto:busschbach@alcatel-lucent.com] <BR><B>Sent:</B> Monday, =
January=20
      05, 2009 3:51 PM<BR><B>To:</B> Alexander Vainshtein; Aissaoui, =
Mustapha=20
      (Mustapha); dallan@nortel.com; lmartini@cisco.com; Thomas D. =
Nadeau;=20
      mmorrow@cisco.com<BR><B>Cc:</B> pwe3@ietf.org; Shell Nakash; =
Prashant=20
      Desai; Igor Danilovich; Itamar Levy<BR><B>Subject:</B> RE: A =
question=20
      regarding torn down PWs in=20
      draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
      <DIV></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT =
face=3DArial=20
      size=3D2>Hi Sasha,</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT =
face=3DArial=20
      size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT =
face=3DArial=20
      size=3D2>&gt;&gt; <SPAN class=3D012494009-05012009><FONT =
face=3DArial=20
      size=3D2>Does the quoted text imply that implementations must =
distinguish=20
      between PWs being torn down</FONT></SPAN></FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT =
face=3DArial=20
      size=3D2><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>&gt;&gt; due=20
      to failures of their control sessions and PWs that are torn down =
for any=20
      other reason?</FONT></SPAN></FONT></SPAN></DIV>
      <DIV>&nbsp;</DIV>
      <DIV><FONT face=3DArial size=3D2><SPAN=20
      class=3D214484013-05012009>Whether&nbsp;PWs are torn down because =
of a=20
      defect (whether it is in the control plane or in the data plane), =
the=20
      consequent actions are the same.<BR><SPAN =
class=3D017510414-05012009><FONT=20
      color=3D#0000ff><EM>[[Sasha]]&nbsp;I am not aware of the case when =
a PW is=20
      torn down due to defects in the data plane. Could you please =
provide a=20
      reference/an example?</EM></FONT></SPAN></SPAN></FONT></DIV>
      <DIV><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2>&nbsp;It=20
      would be good, however, if a PE would be able to distinguish =
between PWs=20
      torn down because of defects and PWs torn down for administrative =
reasons,=20
      because in the latter case there is no need to insert an FDI =
message=20
      downstream.<BR><SPAN class=3D017510414-05012009><FONT=20
      color=3D#0000ff><EM>[[Sasha]]&nbsp;I do not think that RFC 4447 =
provides for=20
      that.&nbsp;In addition, please consider the following=20
      scenario:</EM></FONT></SPAN></FONT></FONT></SPAN></DIV>
      <OL>
        <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2><SPAN=20
        class=3D017510414-05012009><FONT color=3D#0000ff><EM>A PW is set =

        up</EM></FONT></SPAN></FONT></FONT></SPAN>=20
        <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2><SPAN=20
        class=3D017510414-05012009><FONT color=3D#0000ff><EM>The PW is =
torn=20
        down&nbsp;due to the CP defect (targeted LDP session went down). =
FDI is=20
        inserted in the local AC</EM></FONT></SPAN></FONT></FONT></SPAN> =

        <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2><SPAN=20
        class=3D017510414-05012009><EM>&nbsp;<FONT color=3D#0000ff>The =
user has=20
        deleted the PW end point in the remote PE. Since the LDP session =
is=20
        down, this fact is not communicated to the local=20
        PE</FONT></EM></SPAN></FONT></FONT></SPAN>=20
        <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
color=3D#0000ff=20
        size=3D2><SPAN class=3D017510414-05012009><EM>Targeted LDP =
session is=20
        restored but an attempt of the local PE to restore the PW fails =
since=20
        there is no remote peer anymore. <STRONG>What should now happen =
to the=20
        local AC</STRONG>?</EM></SPAN></FONT></FONT></SPAN></LI></OL>
      <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
      class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
      <DIV><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2>Remember=20
      that Luca sent an email to the list proposing to add a BFD code =
point to=20
      indicate that an AC was taken down for admistrative reasons. That =
proposal=20
      was driven by the same motivation.<BR><SPAN =
class=3D017510414-05012009><FONT=20
      color=3D#0000ff><EM>[[Sasha]]&nbsp;I&nbsp;remember that, and I =
believe I've=20
      sent a couple of messages to the list questioning the rationale=20
      of&nbsp;such a code point.=20
      &nbsp;</EM></FONT></SPAN></FONT></FONT></SPAN></DIV>
      <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
      class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
      class=3D214484013-05012009>Peter</SPAN></FONT></FONT></DIV>
      <DIV><FONT size=3D2><SPAN=20
class=3D214484013-05012009></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT size=3D2><SPAN=20
class=3D214484013-05012009></SPAN></FONT>&nbsp;</DIV>
      <BLOCKQUOTE dir=3Dltr=20
      style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 =
2px solid; MARGIN-RIGHT: 0px">
        <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
        <HR tabIndex=3D-1>
        <FONT face=3DTahoma size=3D2><B>From:</B> Alexander Vainshtein=20
        [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> =
Monday,=20
        January 05, 2009 5:12 AM<BR><B>To:</B> Aissaoui, Mustapha =
(Mustapha);=20
        Busschbach, Peter B (Peter); dallan@nortel.com; =
lmartini@cisco.com;=20
        Thomas D. Nadeau; mmorrow@cisco.com<BR><B>Cc:</B> pwe3@ietf.org; =
Shell=20
        Nakash; Prashant Desai; Igor Danilovich; Itamar =
Levy<BR><B>Subject:</B>=20
        A question regarding torn down PWs in=20
        draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
        <DIV></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>Hi=20
        Monique/Mustapha/Peter/Dave/Thom/Luca,</FONT></SPAN></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>I have a=20
        question to you as the editors of the expired)=20
        draft-ietf-pwe3-oam-msg-map-08.txt.</FONT></SPAN></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>The question=20
        is related&nbsp;to the following text in Section <STRONG>8.2.1. =
PW=20
        Forward Defect State Entry/Exit =
Criteria</STRONG>:</FONT></SPAN></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
        size=3D2>&lt;quote&gt;</FONT></SPAN></DIV>
        <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
          <DIV><SPAN class=3D012494009-05012009><EM><FONT=20
          color=3D#0000ff>&nbsp;&nbsp; Note that if the PW control =
session between=20
          the PEs fails, the PW is <BR>&nbsp;&nbsp; torn down and needs =
to be=20
          re-established. This includes failure of <BR>&nbsp;&nbsp; the =
T-LDP=20
          session, the L2TP session, or the L2TP control connection.=20
          <BR>&nbsp;&nbsp; However, the consequent actions towards the =
ACs are=20
          the same as if <BR>&nbsp;&nbsp; the PW entered the forward =
defect=20
          state.</FONT></EM></SPAN></DIV></BLOCKQUOTE>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>&lt;end=20
        quote&gt;</FONT></SPAN></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>The PW may=20
        be torn down not just because the PW control session between the =
PEs=20
        fails. E.g., the PW can be deleted by the operator in one of the =

        PEs.</FONT></SPAN></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>Does the=20
        quoted text imply that implementations must distinguish between =
PWs=20
        being torn down due to failures of their control sessions and =
PWs that=20
        are torn down for any other reason?</FONT></SPAN></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>The use case=20
        of special interest would be a PW that has been set up (and =
later torn=20
        down) using a single-sided mechanism...</FONT></SPAN></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>I'd also=20
        like to note that there are several references in the draft to=20
        unspecified defects&nbsp;<EM><FONT color=3D#0000ff> "that do not =
result in=20
        the PW being torn down</FONT></EM>"...</FONT></SPAN></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
        size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
        size=3D2>Regards,</FONT></SPAN></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
        size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</FONT></SPAN></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
        size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
        =
size=3D2></FONT></SPAN>&nbsp;</DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE=
></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C96F61.0CDD9FE5--

--===============0862495125==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0862495125==--


From pwe3-bounces@ietf.org  Mon Jan  5 11:10:10 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E82D13A695F;
	Mon,  5 Jan 2009 11:10:10 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E437F3A695F
	for <pwe3@core3.amsl.com>; Mon,  5 Jan 2009 11:10:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 XHmezT7SitA1 for <pwe3@core3.amsl.com>;
	Mon,  5 Jan 2009 11:10:04 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39])
	by core3.amsl.com (Postfix) with ESMTP id CF1E53A67EC
	for <pwe3@ietf.org>; Mon,  5 Jan 2009 11:10:03 -0800 (PST)
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1])
	by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id n05J9YId017185;
	Mon, 5 Jan 2009 13:09:34 -0600 (CST)
Received: from ILEXC2U01.ndc.lucent.com ([135.3.39.9]) by
	ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 13:09:29 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 Jan 2009 13:09:22 -0600
Message-ID: <E60778C3916D3548BBCF4D964186348F02295632@ILEXC2U01.ndc.lucent.com>
In-Reply-To: <2ECAA42C79676B42AEBAC11229CA7D0C03DD68BF@E03MVB2-UKBR.domain1.systemhost.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] A question regarding torn down PWs
	indraft-ietf-pwe3-oam-msg-map-08.txt
Thread-Index: AclvHgFatl4xVjfUTBai2RqcqunEfwAHTX0AAADXDMAABCyFYAAAnjpgAAOeD4AAAhfBUA==
References: <E60778C3916D3548BBCF4D964186348F02295525@ILEXC2U01.ndc.lucent.com>
	<2ECAA42C79676B42AEBAC11229CA7D0C03DD68BF@E03MVB2-UKBR.domain1.systemhost.net>
From: "Busschbach, Peter B \(Peter\)" <busschbach@alcatel-lucent.com>
To: <neil.2.harrison@bt.com>, <dallan@nortel.com>,
	<Alexander.Vainshtein@ecitele.com>
X-OriginalArrivalTime: 05 Jan 2009 19:09:29.0116 (UTC)
	FILETIME=[221A2DC0:01C96F69]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: Shell.Nakash@ecitele.com, lmartini@cisco.com, mmorrow@cisco.com,
	Igor.Danilovich@ecitele.com, pwe3@ietf.org, "Aissaoui,
	Mustapha \(Mustapha\)" <mustapha.aissaoui@alcatel-lucent.com>,
	Itamar.Levy@ecitele.com
Subject: Re: [PWE3] A question regarding torn down PWs
	indraft-ietf-pwe3-oam-msg-map-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0905638661=="
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0905638661==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C96F69.1ECE3F3F"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C96F69.1ECE3F3F
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Neil,
=20
Not sure why you believe Ethernet is a cl-ps network. It can be, but
does not have to. Consequently, Y.1731 does have AIS.
=20
My memory of the AIS discussion may be faulty, but it was not because of
anything specific to Ethernet.
=20
Peter


________________________________

	From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]=20
	Sent: Monday, January 05, 2009 1:11 PM
	To: Busschbach, Peter B (Peter); dallan@nortel.com;
Alexander.Vainshtein@ecitele.com
	Cc: Shell.Nakash@ecitele.com; lmartini@cisco.com;
mmorrow@cisco.com; Igor.Danilovich@ecitele.com; pwe3@ietf.org; Aissaoui,
Mustapha (Mustapha); Itamar.Levy@ecitele.com
	Subject: RE: [PWE3] A question regarding torn down PWs
indraft-ietf-pwe3-oam-msg-map-08.txt
=09
=09
	Peter,
	=20
	I think I can answer your question wrt Ethernet at least.
AID/FDI has no meaning whatsoever to a client cl-ps layer
network....this is why IEEE did not have AIS/FDI in 802.1ag. =20
	=20
	And as an aside:  AIS/FDI is almost essential/mandated in a
co-cs layer network...in the absence of traffic something MUST be sent
in such networks, and AIS/FDI =3D all 1s here is a throwback to TTL =
logic
that floated to binary 1 (+5V) under failures.  The merit of AIS/FDI is
debateable in a co-ps mode network.  However, in a cl-ps layer network
it has no meaning at all......since there is no server (connection) to
client (*connection*) association.
	=20
	regards, Neil


________________________________

		From: pwe3-bounces@ietf.org
[mailto:pwe3-bounces@ietf.org] On Behalf Of Busschbach, Peter B (Peter)
		Sent: 05 January 2009 16:37
		To: David Allan; Alexander Vainshtein
		Cc: Shell Nakash; lmartini@cisco.com; mmorrow@cisco.com;
Igor Danilovich; pwe3@ietf.org; Aissaoui, Mustapha (Mustapha); Itamar
Levy
		Subject: Re: [PWE3] A question regarding torn down PWs
indraft-ietf-pwe3-oam-msg-map-08.txt
	=09
	=09
		Dave,
		=20
		I seem to remember from discussions in ITU-T about
Ethernet OAM that an administrative action should not result in AIS
insertion. To be honest, I can't remember why, though. Therefore, unless
someone else knows a reason why administrative down should not result in
AIS, I withdraw my comment.
		=20
		Peter


________________________________

			From: David Allan [mailto:dallan@nortel.com]=20
			Sent: Monday, January 05, 2009 11:16 AM
			To: Alexander Vainshtein; Busschbach, Peter B
(Peter)
			Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai;
Igor Danilovich; Itamar Levy; Aissaoui, Mustapha (Mustapha);
lmartini@cisco.com; Thomas D. Nadeau; mmorrow@cisco.com
			Subject: RE: A question regarding torn down PWs
in draft-ietf-pwe3-oam-msg-map-08.txt
		=09
		=09
			hi Peter:
			=20
			Below you suggest that FDI not be inserted when
a PW is taken down administratively. I do not understand why this is
different from any other disruption of connectivity, unless it is
beleived that an administrative action is joined up across both MPLS PWs
and the native service by other means....
			=20
			Am I missing somthing?
			=20
			cheers
			Dave
			=20
			=20
			=20
			=20
________________________________

			From: Alexander Vainshtein
[mailto:Alexander.Vainshtein@ecitele.com]=20
			Sent: Monday, January 05, 2009 10:09 AM
			To: Busschbach, Peter B (Peter)
			Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai;
Igor Danilovich; Itamar Levy; Aissaoui, Mustapha (Mustapha); Allan,
David (CAR:NS00); lmartini@cisco.com; Thomas D. Nadeau;
mmorrow@cisco.com
			Subject: RE: A question regarding torn down PWs
in draft-ietf-pwe3-oam-msg-map-08.txt
		=09
		=09
			Peter hi,
			Lots of thanks for a prompt response.
			=20
			Please see some comments inline below (blue
italics).
			=20
			Regards,
			    Sasha


________________________________

				From: Busschbach, Peter B (Peter)
[mailto:busschbach@alcatel-lucent.com]=20
				Sent: Monday, January 05, 2009 3:51 PM
				To: Alexander Vainshtein; Aissaoui,
Mustapha (Mustapha); dallan@nortel.com; lmartini@cisco.com; Thomas D.
Nadeau; mmorrow@cisco.com
				Cc: pwe3@ietf.org; Shell Nakash;
Prashant Desai; Igor Danilovich; Itamar Levy
				Subject: RE: A question regarding torn
down PWs in draft-ietf-pwe3-oam-msg-map-08.txt
			=09
			=09
				Hi Sasha,
				=20
				>> Does the quoted text imply that
implementations must distinguish between PWs being torn down
				>> due to failures of their control
sessions and PWs that are torn down for any other reason?
				=20
				Whether PWs are torn down because of a
defect (whether it is in the control plane or in the data plane), the
consequent actions are the same.
				[[Sasha]] I am not aware of the case
when a PW is torn down due to defects in the data plane. Could you
please provide a reference/an example?
				 It would be good, however, if a PE
would be able to distinguish between PWs torn down because of defects
and PWs torn down for administrative reasons, because in the latter case
there is no need to insert an FDI message downstream.
				[[Sasha]] I do not think that RFC 4447
provides for that. In addition, please consider the following scenario:

				1.	A PW is set up=20
				2.	The PW is torn down due to the
CP defect (targeted LDP session went down). FDI is inserted in the local
AC=20
				3.	 The user has deleted the PW end
point in the remote PE. Since the LDP session is down, this fact is not
communicated to the local PE=20
				4.	Targeted LDP session is restored
but an attempt of the local PE to restore the PW fails since there is no
remote peer anymore. What should now happen to the local AC?

				=20
				Remember that Luca sent an email to the
list proposing to add a BFD code point to indicate that an AC was taken
down for admistrative reasons. That proposal was driven by the same
motivation.
				[[Sasha]] I remember that, and I believe
I've sent a couple of messages to the list questioning the rationale of
such a code point. =20
				=20
				Peter
				=20
				=20

________________________________

				From: Alexander Vainshtein
[mailto:Alexander.Vainshtein@ecitele.com]=20
				Sent: Monday, January 05, 2009 5:12 AM
				To: Aissaoui, Mustapha (Mustapha);
Busschbach, Peter B (Peter); dallan@nortel.com; lmartini@cisco.com;
Thomas D. Nadeau; mmorrow@cisco.com
				Cc: pwe3@ietf.org; Shell Nakash;
Prashant Desai; Igor Danilovich; Itamar Levy
				Subject: A question regarding torn down
PWs in draft-ietf-pwe3-oam-msg-map-08.txt
			=09
			=09
				Hi
Monique/Mustapha/Peter/Dave/Thom/Luca,
				I have a question to you as the editors
of the expired) draft-ietf-pwe3-oam-msg-map-08.txt.
				The question is related to the following
text in Section 8.2.1. PW Forward Defect State Entry/Exit Criteria:
				<quote>

				   Note that if the PW control session
between the PEs fails, the PW is=20
				   torn down and needs to be
re-established. This includes failure of=20
				   the T-LDP session, the L2TP session,
or the L2TP control connection.=20
				   However, the consequent actions
towards the ACs are the same as if=20
				   the PW entered the forward defect
state.

				<end quote>
				The PW may be torn down not just because
the PW control session between the PEs fails. E.g., the PW can be
deleted by the operator in one of the PEs.
				Does the quoted text imply that
implementations must distinguish between PWs being torn down due to
failures of their control sessions and PWs that are torn down for any
other reason?
				The use case of special interest would
be a PW that has been set up (and later torn down) using a single-sided
mechanism...
				I'd also like to note that there are
several references in the draft to unspecified defects  "that do not
result in the PW being torn down"...
				=20
				Regards,
				     Sasha
				=20
				=20


------_=_NextPart_001_01C96F69.1ECE3F3F
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3243" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D630330519-05012009><FONT =
face=3DArial=20
size=3D2>Hi Neil,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D630330519-05012009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D630330519-05012009><FONT =
face=3DArial=20
size=3D2>Not sure why you believe Ethernet is a cl-ps network. It can =
be, but does=20
not have to. Consequently, Y.1731 does have AIS.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D630330519-05012009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D630330519-05012009><FONT =
face=3DArial=20
size=3D2>My memory of the AIS discussion may be faulty, but it was not =
because of=20
anything specific to Ethernet.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D630330519-05012009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D630330519-05012009><FONT =
face=3DArial=20
size=3D2>Peter</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> neil.2.harrison@bt.com=20
  [mailto:neil.2.harrison@bt.com] <BR><B>Sent:</B> Monday, January 05, =
2009 1:11=20
  PM<BR><B>To:</B> Busschbach, Peter B (Peter); dallan@nortel.com;=20
  Alexander.Vainshtein@ecitele.com<BR><B>Cc:</B> =
Shell.Nakash@ecitele.com;=20
  lmartini@cisco.com; mmorrow@cisco.com; Igor.Danilovich@ecitele.com;=20
  pwe3@ietf.org; Aissaoui, Mustapha (Mustapha);=20
  Itamar.Levy@ecitele.com<BR><B>Subject:</B> RE: [PWE3] A question =
regarding=20
  torn down PWs =
indraft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D243380518-05012009><FONT=20
  face=3D"Comic Sans MS" color=3D#800000 =
size=3D2>Peter,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D243380518-05012009><FONT=20
  face=3D"Comic Sans MS" color=3D#800000 =
size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D243380518-05012009><FONT=20
  face=3D"Comic Sans MS" color=3D#800000 size=3D2>I think I can answer =
your question=20
  wrt Ethernet at least.&nbsp; AID/FDI has no meaning whatsoever to a =
client=20
  cl-ps layer network....this is why IEEE did not have AIS/FDI in =
802.1ag.&nbsp;=20
  </FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D243380518-05012009><FONT=20
  face=3D"Comic Sans MS" color=3D#800000 =
size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D243380518-05012009><FONT=20
  face=3D"Comic Sans MS" color=3D#800000 size=3D2>And as an aside:&nbsp; =
AIS/FDI is=20
  almost essential/mandated in a co-cs layer network...in the absence of =
traffic=20
  something MUST be sent in such networks, and AIS/FDI =3D all 1s here =
is a=20
  throwback to TTL logic that floated to binary 1 (+5V) under =
failures.&nbsp;=20
  The merit of AIS/FDI is debateable in a co-ps mode network.&nbsp; =
However, in=20
  a cl-ps layer network it has no meaning at all......since there is no =
server=20
  (connection) to client (*connection*) association.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D243380518-05012009><FONT=20
  face=3D"Comic Sans MS" color=3D#800000 =
size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D243380518-05012009><FONT=20
  face=3D"Comic Sans MS" color=3D#800000 size=3D2>regards,=20
Neil</FONT></SPAN></DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #800000 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> pwe3-bounces@ietf.org=20
    [mailto:pwe3-bounces@ietf.org] <B>On Behalf Of </B>Busschbach, Peter =
B=20
    (Peter)<BR><B>Sent:</B> 05 January 2009 16:37<BR><B>To:</B> David =
Allan;=20
    Alexander Vainshtein<BR><B>Cc:</B> Shell Nakash; lmartini@cisco.com; =

    mmorrow@cisco.com; Igor Danilovich; pwe3@ietf.org; Aissaoui, =
Mustapha=20
    (Mustapha); Itamar Levy<BR><B>Subject:</B> Re: [PWE3] A question =
regarding=20
    torn down PWs =
indraft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
    size=3D2>Dave,</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
    size=3D2>I seem to remember from discussions in ITU-T about Ethernet =
OAM that=20
    an administrative action should not result in AIS insertion. To be =
honest, I=20
    can't remember why, though. Therefore, unless someone else knows a =
reason=20
    why administrative down should not result in AIS, I withdraw my=20
    comment.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
    size=3D2>Peter</FONT></SPAN></DIV><BR>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 =
2px solid; MARGIN-RIGHT: 0px">
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
      <HR tabIndex=3D-1>
      <FONT face=3DTahoma size=3D2><B>From:</B> David Allan=20
      [mailto:dallan@nortel.com] <BR><B>Sent:</B> Monday, January 05, =
2009 11:16=20
      AM<BR><B>To:</B> Alexander Vainshtein; Busschbach, Peter B=20
      (Peter)<BR><B>Cc:</B> pwe3@ietf.org; Shell Nakash; Prashant Desai; =
Igor=20
      Danilovich; Itamar Levy; Aissaoui, Mustapha (Mustapha);=20
      lmartini@cisco.com; Thomas D. Nadeau; =
mmorrow@cisco.com<BR><B>Subject:</B>=20
      RE: A question regarding torn down PWs in=20
      draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
      <DIV></DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D746210416-05012009>hi Peter:</SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D746210416-05012009>Below you suggest that FDI not be =
inserted when a=20
      PW is taken down administratively.&nbsp;I do not understand why =
this=20
      is&nbsp;different from any other disruption of connectivity, =
unless it is=20
      beleived that an administrative action is joined up across both =
MPLS=20
      PWs&nbsp;and the native service by other =
means....</SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D746210416-05012009>Am I missing =
somthing?</SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D746210416-05012009>cheers</SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D746210416-05012009>Dave</SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
      <HR tabIndex=3D-1>
      <FONT face=3DTahoma size=3D2><B>From:</B> Alexander Vainshtein=20
      [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> Monday, =
January=20
      05, 2009 10:09 AM<BR><B>To:</B> Busschbach, Peter B =
(Peter)<BR><B>Cc:</B>=20
      pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor Danilovich; =
Itamar Levy;=20
      Aissaoui, Mustapha (Mustapha); Allan, David (CAR:NS00);=20
      lmartini@cisco.com; Thomas D. Nadeau; =
mmorrow@cisco.com<BR><B>Subject:</B>=20
      RE: A question regarding torn down PWs in=20
      draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
      <DIV></DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D017510414-05012009>Peter hi,</SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D017510414-05012009>Lots of thanks for a prompt=20
      response.</SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D017510414-05012009></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D017510414-05012009>Please see some comments inline below =
(<EM>blue=20
      italics</EM>).</SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D017510414-05012009></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D017510414-05012009>Regards,</SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D017510414-05012009>&nbsp;&nbsp;&nbsp; =
Sasha</SPAN></FONT></DIV><BR>
      <BLOCKQUOTE dir=3Dltr=20
      style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff =
2px solid; MARGIN-RIGHT: 0px">
        <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
        <HR tabIndex=3D-1>
        <FONT face=3DTahoma size=3D2><B>From:</B> Busschbach, Peter B =
(Peter)=20
        [mailto:busschbach@alcatel-lucent.com] <BR><B>Sent:</B> Monday, =
January=20
        05, 2009 3:51 PM<BR><B>To:</B> Alexander Vainshtein; Aissaoui, =
Mustapha=20
        (Mustapha); dallan@nortel.com; lmartini@cisco.com; Thomas D. =
Nadeau;=20
        mmorrow@cisco.com<BR><B>Cc:</B> pwe3@ietf.org; Shell Nakash; =
Prashant=20
        Desai; Igor Danilovich; Itamar Levy<BR><B>Subject:</B> RE: A =
question=20
        regarding torn down PWs in=20
        draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
        <DIV></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D214484013-05012009><FONT face=3DArial=20
        size=3D2>Hi Sasha,</FONT></SPAN></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D214484013-05012009><FONT face=3DArial=20
        size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D214484013-05012009><FONT face=3DArial=20
        size=3D2>&gt;&gt; <SPAN class=3D012494009-05012009><FONT =
face=3DArial=20
        size=3D2>Does the quoted text imply that implementations must =
distinguish=20
        between PWs being torn down</FONT></SPAN></FONT></SPAN></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D214484013-05012009><FONT face=3DArial=20
        size=3D2><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>&gt;&gt;=20
        due to failures of their control sessions and PWs that are torn =
down for=20
        any other reason?</FONT></SPAN></FONT></SPAN></DIV>
        <DIV>&nbsp;</DIV>
        <DIV><FONT face=3DArial size=3D2><SPAN=20
        class=3D214484013-05012009>Whether&nbsp;PWs are torn down =
because of a=20
        defect (whether it is in the control plane or in the data =
plane), the=20
        consequent actions are the same.<BR><SPAN =
class=3D017510414-05012009><FONT=20
        color=3D#0000ff><EM>[[Sasha]]&nbsp;I am not aware of the case =
when a PW is=20
        torn down due to defects in the data plane. Could you please =
provide a=20
        reference/an example?</EM></FONT></SPAN></SPAN></FONT></DIV>
        <DIV><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT=20
        size=3D2>&nbsp;It would be good, however, if a PE would be able =
to=20
        distinguish between PWs torn down because of defects and PWs =
torn down=20
        for administrative reasons, because in the latter case there is =
no need=20
        to insert an FDI message downstream.<BR><SPAN=20
        class=3D017510414-05012009><FONT =
color=3D#0000ff><EM>[[Sasha]]&nbsp;I do not=20
        think that RFC 4447 provides for that.&nbsp;In addition, please =
consider=20
        the following =
scenario:</EM></FONT></SPAN></FONT></FONT></SPAN></DIV>
        <OL>
          <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2><SPAN=20
          class=3D017510414-05012009><FONT color=3D#0000ff><EM>A PW is =
set=20
          up</EM></FONT></SPAN></FONT></FONT></SPAN>=20
          <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2><SPAN=20
          class=3D017510414-05012009><FONT color=3D#0000ff><EM>The PW is =
torn=20
          down&nbsp;due to the CP defect (targeted LDP session went =
down). FDI=20
          is inserted in the local =
AC</EM></FONT></SPAN></FONT></FONT></SPAN>=20
          <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2><SPAN=20
          class=3D017510414-05012009><EM>&nbsp;<FONT color=3D#0000ff>The =
user has=20
          deleted the PW end point in the remote PE. Since the LDP =
session is=20
          down, this fact is not communicated to the local=20
          PE</FONT></EM></SPAN></FONT></FONT></SPAN>=20
          <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT=20
          color=3D#0000ff size=3D2><SPAN =
class=3D017510414-05012009><EM>Targeted LDP=20
          session is restored but an attempt of the local PE to restore =
the PW=20
          fails since there is no remote peer anymore. <STRONG>What =
should now=20
          happen to the local=20
        AC</STRONG>?</EM></SPAN></FONT></FONT></SPAN></LI></OL>
        <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
        class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
        <DIV><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT=20
        size=3D2>Remember that Luca sent an email to the list proposing =
to add a=20
        BFD code point to indicate that an AC was taken down for =
admistrative=20
        reasons. That proposal was driven by the same =
motivation.<BR><SPAN=20
        class=3D017510414-05012009><FONT=20
        color=3D#0000ff><EM>[[Sasha]]&nbsp;I&nbsp;remember that, and I =
believe=20
        I've sent a couple of messages to the list questioning the =
rationale=20
        of&nbsp;such a code point.=20
        &nbsp;</EM></FONT></SPAN></FONT></FONT></SPAN></DIV>
        <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
        class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
        <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
        class=3D214484013-05012009>Peter</SPAN></FONT></FONT></DIV>
        <DIV><FONT size=3D2><SPAN=20
        class=3D214484013-05012009></SPAN></FONT>&nbsp;</DIV>
        <DIV><FONT size=3D2><SPAN=20
        class=3D214484013-05012009></SPAN></FONT>&nbsp;</DIV>
        <BLOCKQUOTE dir=3Dltr=20
        style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: =
#000000 2px solid; MARGIN-RIGHT: 0px">
          <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
          <HR tabIndex=3D-1>
          <FONT face=3DTahoma size=3D2><B>From:</B> Alexander Vainshtein =

          [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> =
Monday,=20
          January 05, 2009 5:12 AM<BR><B>To:</B> Aissaoui, Mustapha =
(Mustapha);=20
          Busschbach, Peter B (Peter); dallan@nortel.com; =
lmartini@cisco.com;=20
          Thomas D. Nadeau; mmorrow@cisco.com<BR><B>Cc:</B> =
pwe3@ietf.org; Shell=20
          Nakash; Prashant Desai; Igor Danilovich; Itamar=20
          Levy<BR><B>Subject:</B> A question regarding torn down PWs in=20
          draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
          <DIV></DIV>
          <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>Hi=20
          Monique/Mustapha/Peter/Dave/Thom/Luca,</FONT></SPAN></DIV>
          <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>I have a=20
          question to you as the editors of the expired)=20
          draft-ietf-pwe3-oam-msg-map-08.txt.</FONT></SPAN></DIV>
          <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>The=20
          question is related&nbsp;to the following text in Section=20
          <STRONG>8.2.1. PW Forward Defect State Entry/Exit=20
          Criteria</STRONG>:</FONT></SPAN></DIV>
          <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
          size=3D2>&lt;quote&gt;</FONT></SPAN></DIV>
          <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
            <DIV><SPAN class=3D012494009-05012009><EM><FONT=20
            color=3D#0000ff>&nbsp;&nbsp; Note that if the PW control =
session=20
            between the PEs fails, the PW is <BR>&nbsp;&nbsp; torn down =
and=20
            needs to be re-established. This includes failure of=20
            <BR>&nbsp;&nbsp; the T-LDP session, the L2TP session, or the =
L2TP=20
            control connection. <BR>&nbsp;&nbsp; However, the consequent =
actions=20
            towards the ACs are the same as if <BR>&nbsp;&nbsp; the PW =
entered=20
            the forward defect =
state.</FONT></EM></SPAN></DIV></BLOCKQUOTE>
          <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>&lt;end=20
          quote&gt;</FONT></SPAN></DIV>
          <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>The PW may=20
          be torn down not just because the PW control session between =
the PEs=20
          fails. E.g., the PW can be deleted by the operator in one of =
the=20
          PEs.</FONT></SPAN></DIV>
          <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>Does the=20
          quoted text imply that implementations must distinguish =
between PWs=20
          being torn down due to failures of their control sessions and =
PWs that=20
          are torn down for any other reason?</FONT></SPAN></DIV>
          <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>The use=20
          case of special interest would be a PW that has been set up =
(and later=20
          torn down) using a single-sided =
mechanism...</FONT></SPAN></DIV>
          <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>I'd also=20
          like to note that there are several references in the draft to =

          unspecified defects&nbsp;<EM><FONT color=3D#0000ff> "that do =
not result=20
          in the PW being torn down</FONT></EM>"...</FONT></SPAN></DIV>
          <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
          size=3D2></FONT></SPAN>&nbsp;</DIV>
          <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
          size=3D2>Regards,</FONT></SPAN></DIV>
          <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
          size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</FONT></SPAN></DIV>
          <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
          size=3D2></FONT></SPAN>&nbsp;</DIV>
          <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
          =
size=3D2></FONT></SPAN>&nbsp;</DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE=
></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C96F69.1ECE3F3F--

--===============0905638661==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0905638661==--


From pwe3-bounces@ietf.org  Mon Jan  5 12:30:43 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1FC8628C127;
	Mon,  5 Jan 2009 12:30:43 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0D44A28C127
	for <pwe3@core3.amsl.com>; Mon,  5 Jan 2009 12:30:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.089
X-Spam-Level: 
X-Spam-Status: No, score=-1.089 tagged_above=-999 required=5 tests=[AWL=0.341, 
	BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
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 hsJPivPKMRPA for <pwe3@core3.amsl.com>;
	Mon,  5 Jan 2009 12:30:41 -0800 (PST)
Received: from viefep18-int.chello.at (viefep16-int.chello.at [62.179.121.36])
	by core3.amsl.com (Postfix) with ESMTP id 99B4728C10C
	for <pwe3@ietf.org>; Mon,  5 Jan 2009 12:30:39 -0800 (PST)
Received: from edge04.upc.biz ([192.168.13.239]) by viefep16-int.chello.at
	(InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP
	id <20090105203025.MNOD1339.viefep16-int.chello.at@edge04.upc.biz>;
	Mon, 5 Jan 2009 21:30:25 +0100
Received: from McAsterix.local ([24.132.228.153]) by edge04.upc.biz with edge
	id zwWM1a02g3KDBhC04wWN3t; Mon, 05 Jan 2009 21:30:25 +0100
X-SourceIP: 24.132.228.153
Message-ID: <49626DDD.3070305@chello.nl>
Date: Mon, 05 Jan 2009 21:30:21 +0100
From: Huub van Helvoort <hhelvoort@chello.nl>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: "Busschbach, Peter B \(Peter\)" <busschbach@alcatel-lucent.com>
References: <A3C5DF08D38B6049839A6F553B331C7698C2C6CCC1@ILPTMAIL02.ecitele.com>	<E60778C3916D3548BBCF4D964186348F022953BD@ILEXC2U01.ndc.lucent.com>	<A3C5DF08D38B6049839A6F553B331C7698C2C6CDE7@ILPTMAIL02.ecitele.com>	<87AC5F88F03E6249AEA68D40BD3E00BE16832699@zcarhxm2.corp.nortel.com>
	<E60778C3916D3548BBCF4D964186348F02295525@ILEXC2U01.ndc.lucent.com>
In-Reply-To: <E60778C3916D3548BBCF4D964186348F02295525@ILEXC2U01.ndc.lucent.com>
Cc: pwe3@ietf.org
Subject: Re: [PWE3] A question regarding torn down PWs
	in	draft-ietf-pwe3-oam-msg-map-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: hhelvoort@chello.nl
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Hello Peter,

You wrote:

> I seem to remember from discussions in ITU-T about Ethernet OAM that an 
> administrative action should not result in AIS insertion. 

That is correct in this case a LCK PDU will be inserted.

AIS/FDI PDUs are inserted only as a consequent action to detected
server defects.

Cheers, Huub.

-- 
================================================================
                   http://www.van-helvoort.eu/
================================================================
Always remember that you are unique...just like everyone else...
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3


From pwe3-bounces@ietf.org  Mon Jan  5 12:45:57 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 508123A6836;
	Mon,  5 Jan 2009 12:45:57 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D8AB83A6836
	for <pwe3@core3.amsl.com>; Mon,  5 Jan 2009 12:45:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.958
X-Spam-Level: 
X-Spam-Status: No, score=-2.958 tagged_above=-999 required=5 tests=[AWL=0.040, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_81=0.6,
	RCVD_IN_DNSWL_LOW=-1]
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 3PQ7msIc2r87 for <pwe3@core3.amsl.com>;
	Mon,  5 Jan 2009 12:45:54 -0800 (PST)
Received: from smtp3.smtp.bt.com (smtp3.smtp.bt.com [217.32.164.138])
	by core3.amsl.com (Postfix) with ESMTP id 386DB3A67CC
	for <pwe3@ietf.org>; Mon,  5 Jan 2009 12:45:52 -0800 (PST)
Received: from E03MVB2-UKBR.domain1.systemhost.net ([193.113.197.108]) by
	smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 20:45:39 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 Jan 2009 20:45:34 -0000
Message-ID: <2ECAA42C79676B42AEBAC11229CA7D0C03DD6905@E03MVB2-UKBR.domain1.systemhost.net>
In-Reply-To: <E60778C3916D3548BBCF4D964186348F02295632@ILEXC2U01.ndc.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] A question regarding torn down PWs
	indraft-ietf-pwe3-oam-msg-map-08.txt
thread-index: AclvHgFatl4xVjfUTBai2RqcqunEfwAHTX0AAADXDMAABCyFYAAAnjpgAAOeD4AAAhfBUAADFW/Q
From: <neil.2.harrison@bt.com>
To: <busschbach@alcatel-lucent.com>, <dallan@nortel.com>,
	<Alexander.Vainshtein@ecitele.com>
X-OriginalArrivalTime: 05 Jan 2009 20:45:39.0097 (UTC)
	FILETIME=[91476890:01C96F76]
Cc: Shell.Nakash@ecitele.com, lmartini@cisco.com, mmorrow@cisco.com,
	Igor.Danilovich@ecitele.com, pwe3@ietf.org,
	mustapha.aissaoui@alcatel-lucent.com, Itamar.Levy@ecitele.com
Subject: Re: [PWE3] A question regarding torn down PWs
	indraft-ietf-pwe3-oam-msg-map-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1301319852=="
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1301319852==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C96F76.90CA8F1F"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C96F76.90CA8F1F
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks Peter,
=20
Native/original Ethernet (.1D, .1Q and .1ad) are all cl-ps...and all are
a single layer network.  PBB (.1ah) is also cl-ps....but introduces true
C/S layering, ie 2 functionally independemt layer networks.  PBB-TE
(.1ay) is however most definitely co-ps...though in principle it does
not need the MACinMAC restriction to be co-ps.
=20
However, the only key point here is the merit of injecting an FDI into a
client layer network.  If the client layer network is cl-ps then
injecting FDI into it makes no sense at all.  If you think it does then
maybe IP should also use it ;-) =20
=20
The reason FDI exists in Y.1731 is because some folks think *imposing* a
forced topology of nested MEPs is a good idea...we don't, but that (ie
TCM) is a different issue.  Bottom line is cl-ps networks cannot make
sense of FDI in a *traffic sense*.
=20
regards, Neil


________________________________

	From: Busschbach, Peter B (Peter)
[mailto:busschbach@alcatel-lucent.com]=20
	Sent: 05 January 2009 19:09
	To: Harrison,N,Neil,CXM R; dallan@nortel.com;
Alexander.Vainshtein@ecitele.com
	Cc: Shell.Nakash@ecitele.com; lmartini@cisco.com;
mmorrow@cisco.com; Igor.Danilovich@ecitele.com; pwe3@ietf.org; Aissaoui,
Mustapha (Mustapha); Itamar.Levy@ecitele.com
	Subject: RE: [PWE3] A question regarding torn down PWs
indraft-ietf-pwe3-oam-msg-map-08.txt
=09
=09
	Hi Neil,
	=20
	Not sure why you believe Ethernet is a cl-ps network. It can be,
but does not have to. Consequently, Y.1731 does have AIS.
	=20
	My memory of the AIS discussion may be faulty, but it was not
because of anything specific to Ethernet.
	=20
	Peter


________________________________

		From: neil.2.harrison@bt.com
[mailto:neil.2.harrison@bt.com]=20
		Sent: Monday, January 05, 2009 1:11 PM
		To: Busschbach, Peter B (Peter); dallan@nortel.com;
Alexander.Vainshtein@ecitele.com
		Cc: Shell.Nakash@ecitele.com; lmartini@cisco.com;
mmorrow@cisco.com; Igor.Danilovich@ecitele.com; pwe3@ietf.org; Aissaoui,
Mustapha (Mustapha); Itamar.Levy@ecitele.com
		Subject: RE: [PWE3] A question regarding torn down PWs
indraft-ietf-pwe3-oam-msg-map-08.txt
	=09
	=09
		Peter,
		=20
		I think I can answer your question wrt Ethernet at
least.  AID/FDI has no meaning whatsoever to a client cl-ps layer
network....this is why IEEE did not have AIS/FDI in 802.1ag. =20
		=20
		And as an aside:  AIS/FDI is almost essential/mandated
in a co-cs layer network...in the absence of traffic something MUST be
sent in such networks, and AIS/FDI =3D all 1s here is a throwback to TTL
logic that floated to binary 1 (+5V) under failures.  The merit of
AIS/FDI is debateable in a co-ps mode network.  However, in a cl-ps
layer network it has no meaning at all......since there is no server
(connection) to client (*connection*) association.
		=20
		regards, Neil


________________________________

			From: pwe3-bounces@ietf.org
[mailto:pwe3-bounces@ietf.org] On Behalf Of Busschbach, Peter B (Peter)
			Sent: 05 January 2009 16:37
			To: David Allan; Alexander Vainshtein
			Cc: Shell Nakash; lmartini@cisco.com;
mmorrow@cisco.com; Igor Danilovich; pwe3@ietf.org; Aissaoui, Mustapha
(Mustapha); Itamar Levy
			Subject: Re: [PWE3] A question regarding torn
down PWs indraft-ietf-pwe3-oam-msg-map-08.txt
		=09
		=09
			Dave,
			=20
			I seem to remember from discussions in ITU-T
about Ethernet OAM that an administrative action should not result in
AIS insertion. To be honest, I can't remember why, though. Therefore,
unless someone else knows a reason why administrative down should not
result in AIS, I withdraw my comment.
			=20
			Peter


________________________________

				From: David Allan
[mailto:dallan@nortel.com]=20
				Sent: Monday, January 05, 2009 11:16 AM
				To: Alexander Vainshtein; Busschbach,
Peter B (Peter)
				Cc: pwe3@ietf.org; Shell Nakash;
Prashant Desai; Igor Danilovich; Itamar Levy; Aissaoui, Mustapha
(Mustapha); lmartini@cisco.com; Thomas D. Nadeau; mmorrow@cisco.com
				Subject: RE: A question regarding torn
down PWs in draft-ietf-pwe3-oam-msg-map-08.txt
			=09
			=09
				hi Peter:
				=20
				Below you suggest that FDI not be
inserted when a PW is taken down administratively. I do not understand
why this is different from any other disruption of connectivity, unless
it is beleived that an administrative action is joined up across both
MPLS PWs and the native service by other means....
				=20
				Am I missing somthing?
				=20
				cheers
				Dave
				=20
				=20
				=20
				=20
________________________________

				From: Alexander Vainshtein
[mailto:Alexander.Vainshtein@ecitele.com]=20
				Sent: Monday, January 05, 2009 10:09 AM
				To: Busschbach, Peter B (Peter)
				Cc: pwe3@ietf.org; Shell Nakash;
Prashant Desai; Igor Danilovich; Itamar Levy; Aissaoui, Mustapha
(Mustapha); Allan, David (CAR:NS00); lmartini@cisco.com; Thomas D.
Nadeau; mmorrow@cisco.com
				Subject: RE: A question regarding torn
down PWs in draft-ietf-pwe3-oam-msg-map-08.txt
			=09
			=09
				Peter hi,
				Lots of thanks for a prompt response.
				=20
				Please see some comments inline below
(blue italics).
				=20
				Regards,
				    Sasha


________________________________

				From: Busschbach, Peter B (Peter)
[mailto:busschbach@alcatel-lucent.com]=20
				Sent: Monday, January 05, 2009 3:51 PM
				To: Alexander Vainshtein; Aissaoui,
Mustapha (Mustapha); dallan@nortel.com; lmartini@cisco.com; Thomas D.
Nadeau; mmorrow@cisco.com
				Cc: pwe3@ietf.org; Shell Nakash;
Prashant Desai; Igor Danilovich; Itamar Levy
				Subject: RE: A question regarding torn
down PWs in draft-ietf-pwe3-oam-msg-map-08.txt
			=09
			=09
				Hi Sasha,
				=20
				>> Does the quoted text imply that
implementations must distinguish between PWs being torn down
				>> due to failures of their control
sessions and PWs that are torn down for any other reason?
				=20
				Whether PWs are torn down because of a
defect (whether it is in the control plane or in the data plane), the
consequent actions are the same.
				[[Sasha]] I am not aware of the case
when a PW is torn down due to defects in the data plane. Could you
please provide a reference/an example?
				 It would be good, however, if a PE
would be able to distinguish between PWs torn down because of defects
and PWs torn down for administrative reasons, because in the latter case
there is no need to insert an FDI message downstream.
				[[Sasha]] I do not think that RFC 4447
provides for that. In addition, please consider the following scenario:

				1.	A PW is set up=20
				2.	The PW is torn down due to the
CP defect (targeted LDP session went down). FDI is inserted in the local
AC=20
				3.	 The user has deleted the PW end
point in the remote PE. Since the LDP session is down, this fact is not
communicated to the local PE=20
				4.	Targeted LDP session is restored
but an attempt of the local PE to restore the PW fails since there is no
remote peer anymore. What should now happen to the local AC?

				=20
				Remember that Luca sent an email to the
list proposing to add a BFD code point to indicate that an AC was taken
down for admistrative reasons. That proposal was driven by the same
motivation.
				[[Sasha]] I remember that, and I believe
I've sent a couple of messages to the list questioning the rationale of
such a code point. =20
				=20
				Peter
				=20
				=20

________________________________

				From: Alexander Vainshtein
[mailto:Alexander.Vainshtein@ecitele.com]=20
				Sent: Monday, January 05, 2009 5:12 AM
				To: Aissaoui, Mustapha (Mustapha);
Busschbach, Peter B (Peter); dallan@nortel.com; lmartini@cisco.com;
Thomas D. Nadeau; mmorrow@cisco.com
				Cc: pwe3@ietf.org; Shell Nakash;
Prashant Desai; Igor Danilovich; Itamar Levy
				Subject: A question regarding torn down
PWs in draft-ietf-pwe3-oam-msg-map-08.txt
			=09
			=09
				Hi
Monique/Mustapha/Peter/Dave/Thom/Luca,
				I have a question to you as the editors
of the expired) draft-ietf-pwe3-oam-msg-map-08.txt.
				The question is related to the following
text in Section 8.2.1. PW Forward Defect State Entry/Exit Criteria:
				<quote>

				   Note that if the PW control session
between the PEs fails, the PW is=20
				   torn down and needs to be
re-established. This includes failure of=20
				   the T-LDP session, the L2TP session,
or the L2TP control connection.=20
				   However, the consequent actions
towards the ACs are the same as if=20
				   the PW entered the forward defect
state.

				<end quote>
				The PW may be torn down not just because
the PW control session between the PEs fails. E.g., the PW can be
deleted by the operator in one of the PEs.
				Does the quoted text imply that
implementations must distinguish between PWs being torn down due to
failures of their control sessions and PWs that are torn down for any
other reason?
				The use case of special interest would
be a PW that has been set up (and later torn down) using a single-sided
mechanism...
				I'd also like to note that there are
several references in the draft to unspecified defects  "that do not
result in the PW being torn down"...
				=20
				Regards,
				     Sasha
				=20
				=20


------_=_NextPart_001_01C96F76.90CA8F1F
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2769" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D438513320-05012009><FONT=20
face=3D"Comic Sans MS" color=3D#800000 size=3D2>Thanks =
Peter,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D438513320-05012009><FONT=20
face=3D"Comic Sans MS" color=3D#800000 =
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D438513320-05012009><FONT=20
face=3D"Comic Sans MS" color=3D#800000 size=3D2>Native/original Ethernet =
(.1D, .1Q and=20
.1ad) are all cl-ps...and all are a single layer network.&nbsp; PBB =
(.1ah) is=20
also cl-ps....but introduces true C/S layering, ie 2 functionally =
independemt=20
layer networks.&nbsp; PBB-TE (.1ay) is however most definitely =
co-ps...though in=20
principle it does not need the MACinMAC restriction to be=20
co-ps.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D438513320-05012009><FONT=20
face=3D"Comic Sans MS" color=3D#800000 =
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D438513320-05012009><FONT=20
face=3D"Comic Sans MS" color=3D#800000 size=3D2>However, the only key =
point here is=20
the merit of injecting an FDI into a client layer network.&nbsp; If the =
client=20
layer network is cl-ps then injecting FDI into it&nbsp;makes no sense at =

all.&nbsp; If you think it does then maybe IP should also use it =
;-)&nbsp;=20
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D438513320-05012009><FONT=20
face=3D"Comic Sans MS" color=3D#800000 =
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D438513320-05012009><FONT=20
face=3D"Comic Sans MS" color=3D#800000 size=3D2>The reason FDI exists in =
Y.1731 is=20
because some folks think *imposing* a forced topology of nested MEPs is =
a good=20
idea...we don't, but that (ie TCM) is a different issue.&nbsp; Bottom =
line is=20
cl-ps networks cannot make sense of FDI in a *traffic=20
sense*.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D438513320-05012009><FONT=20
face=3D"Comic Sans MS" color=3D#800000 =
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D438513320-05012009><FONT=20
face=3D"Comic Sans MS" color=3D#800000 size=3D2>regards, =
Neil</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #800000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Busschbach, Peter B (Peter)=20
  [mailto:busschbach@alcatel-lucent.com] <BR><B>Sent:</B> 05 January =
2009=20
  19:09<BR><B>To:</B> Harrison,N,Neil,CXM R; dallan@nortel.com;=20
  Alexander.Vainshtein@ecitele.com<BR><B>Cc:</B> =
Shell.Nakash@ecitele.com;=20
  lmartini@cisco.com; mmorrow@cisco.com; Igor.Danilovich@ecitele.com;=20
  pwe3@ietf.org; Aissaoui, Mustapha (Mustapha);=20
  Itamar.Levy@ecitele.com<BR><B>Subject:</B> RE: [PWE3] A question =
regarding=20
  torn down PWs =
indraft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D630330519-05012009><FONT =
face=3DArial=20
  size=3D2>Hi Neil,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D630330519-05012009><FONT =
face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D630330519-05012009><FONT =
face=3DArial=20
  size=3D2>Not sure why you believe Ethernet is a cl-ps network. It can =
be, but=20
  does not have to. Consequently, Y.1731 does have =
AIS.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D630330519-05012009><FONT =
face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D630330519-05012009><FONT =
face=3DArial=20
  size=3D2>My memory of the AIS discussion may be faulty, but it was not =
because=20
  of anything specific to Ethernet.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D630330519-05012009><FONT =
face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D630330519-05012009><FONT =
face=3DArial=20
  size=3D2>Peter</FONT></SPAN></DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> neil.2.harrison@bt.com=20
    [mailto:neil.2.harrison@bt.com] <BR><B>Sent:</B> Monday, January 05, =
2009=20
    1:11 PM<BR><B>To:</B> Busschbach, Peter B (Peter); =
dallan@nortel.com;=20
    Alexander.Vainshtein@ecitele.com<BR><B>Cc:</B> =
Shell.Nakash@ecitele.com;=20
    lmartini@cisco.com; mmorrow@cisco.com; Igor.Danilovich@ecitele.com;=20
    pwe3@ietf.org; Aissaoui, Mustapha (Mustapha);=20
    Itamar.Levy@ecitele.com<BR><B>Subject:</B> RE: [PWE3] A question =
regarding=20
    torn down PWs =
indraft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D243380518-05012009><FONT=20
    face=3D"Comic Sans MS" color=3D#800000 =
size=3D2>Peter,</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D243380518-05012009><FONT=20
    face=3D"Comic Sans MS" color=3D#800000 =
size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D243380518-05012009><FONT=20
    face=3D"Comic Sans MS" color=3D#800000 size=3D2>I think I can answer =
your question=20
    wrt Ethernet at least.&nbsp; AID/FDI has no meaning whatsoever to a =
client=20
    cl-ps layer network....this is why IEEE did not have AIS/FDI in=20
    802.1ag.&nbsp; </FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D243380518-05012009><FONT=20
    face=3D"Comic Sans MS" color=3D#800000 =
size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D243380518-05012009><FONT=20
    face=3D"Comic Sans MS" color=3D#800000 size=3D2>And as an =
aside:&nbsp; AIS/FDI is=20
    almost essential/mandated in a co-cs layer network...in the absence =
of=20
    traffic something MUST be sent in such networks, and AIS/FDI =3D all =
1s here=20
    is a throwback to TTL logic that floated to binary 1 (+5V) under=20
    failures.&nbsp; The merit of AIS/FDI is debateable in a co-ps mode=20
    network.&nbsp; However, in a cl-ps layer network it has no meaning =
at=20
    all......since there is no server (connection) to client =
(*connection*)=20
    association.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D243380518-05012009><FONT=20
    face=3D"Comic Sans MS" color=3D#800000 =
size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D243380518-05012009><FONT=20
    face=3D"Comic Sans MS" color=3D#800000 size=3D2>regards,=20
    Neil</FONT></SPAN></DIV><BR>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #800000 =
2px solid; MARGIN-RIGHT: 0px">
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
      <HR tabIndex=3D-1>
      <FONT face=3DTahoma size=3D2><B>From:</B> pwe3-bounces@ietf.org=20
      [mailto:pwe3-bounces@ietf.org] <B>On Behalf Of </B>Busschbach, =
Peter B=20
      (Peter)<BR><B>Sent:</B> 05 January 2009 16:37<BR><B>To:</B> David =
Allan;=20
      Alexander Vainshtein<BR><B>Cc:</B> Shell Nakash; =
lmartini@cisco.com;=20
      mmorrow@cisco.com; Igor Danilovich; pwe3@ietf.org; Aissaoui, =
Mustapha=20
      (Mustapha); Itamar Levy<BR><B>Subject:</B> Re: [PWE3] A question =
regarding=20
      torn down PWs =
indraft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
      <DIV></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
      size=3D2>Dave,</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
      size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
      size=3D2>I seem to remember from discussions in ITU-T about =
Ethernet OAM=20
      that an administrative action should not result in AIS insertion. =
To be=20
      honest, I can't remember why, though. Therefore, unless someone =
else knows=20
      a reason why administrative down should not result in AIS, I =
withdraw my=20
      comment.</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
      size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
      size=3D2>Peter</FONT></SPAN></DIV><BR>
      <BLOCKQUOTE dir=3Dltr=20
      style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 =
2px solid; MARGIN-RIGHT: 0px">
        <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
        <HR tabIndex=3D-1>
        <FONT face=3DTahoma size=3D2><B>From:</B> David Allan=20
        [mailto:dallan@nortel.com] <BR><B>Sent:</B> Monday, January 05, =
2009=20
        11:16 AM<BR><B>To:</B> Alexander Vainshtein; Busschbach, Peter B =

        (Peter)<BR><B>Cc:</B> pwe3@ietf.org; Shell Nakash; Prashant =
Desai; Igor=20
        Danilovich; Itamar Levy; Aissaoui, Mustapha (Mustapha);=20
        lmartini@cisco.com; Thomas D. Nadeau;=20
        mmorrow@cisco.com<BR><B>Subject:</B> RE: A question regarding =
torn down=20
        PWs in draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
        <DIV></DIV>
        <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
        class=3D746210416-05012009>hi Peter:</SPAN></FONT></DIV>
        <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
        class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
        <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
        class=3D746210416-05012009>Below you suggest that FDI not be =
inserted when=20
        a PW is taken down administratively.&nbsp;I do not understand =
why this=20
        is&nbsp;different from any other disruption of connectivity, =
unless it=20
        is beleived that an administrative action is joined up across =
both MPLS=20
        PWs&nbsp;and the native service by other =
means....</SPAN></FONT></DIV>
        <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
        class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
        <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
        class=3D746210416-05012009>Am I missing =
somthing?</SPAN></FONT></DIV>
        <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
        class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
        <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
        class=3D746210416-05012009>cheers</SPAN></FONT></DIV>
        <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
        class=3D746210416-05012009>Dave</SPAN></FONT></DIV>
        <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
        class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
        <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
        class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
        <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
        class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
        <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
        class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
        <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
        <HR tabIndex=3D-1>
        <FONT face=3DTahoma size=3D2><B>From:</B> Alexander Vainshtein=20
        [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> =
Monday,=20
        January 05, 2009 10:09 AM<BR><B>To:</B> Busschbach, Peter B=20
        (Peter)<BR><B>Cc:</B> pwe3@ietf.org; Shell Nakash; Prashant =
Desai; Igor=20
        Danilovich; Itamar Levy; Aissaoui, Mustapha (Mustapha); Allan, =
David=20
        (CAR:NS00); lmartini@cisco.com; Thomas D. Nadeau;=20
        mmorrow@cisco.com<BR><B>Subject:</B> RE: A question regarding =
torn down=20
        PWs in draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
        <DIV></DIV>
        <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
        class=3D017510414-05012009>Peter hi,</SPAN></FONT></DIV>
        <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
        class=3D017510414-05012009>Lots of thanks for a prompt=20
        response.</SPAN></FONT></DIV>
        <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
        class=3D017510414-05012009></SPAN></FONT>&nbsp;</DIV>
        <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
        class=3D017510414-05012009>Please see some comments inline below =
(<EM>blue=20
        italics</EM>).</SPAN></FONT></DIV>
        <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
        class=3D017510414-05012009></SPAN></FONT>&nbsp;</DIV>
        <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
        class=3D017510414-05012009>Regards,</SPAN></FONT></DIV>
        <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
        class=3D017510414-05012009>&nbsp;&nbsp;&nbsp;=20
Sasha</SPAN></FONT></DIV><BR>
        <BLOCKQUOTE dir=3Dltr=20
        style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: =
#0000ff 2px solid; MARGIN-RIGHT: 0px">
          <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
          <HR tabIndex=3D-1>
          <FONT face=3DTahoma size=3D2><B>From:</B> Busschbach, Peter B =
(Peter)=20
          [mailto:busschbach@alcatel-lucent.com] <BR><B>Sent:</B> =
Monday,=20
          January 05, 2009 3:51 PM<BR><B>To:</B> Alexander Vainshtein; =
Aissaoui,=20
          Mustapha (Mustapha); dallan@nortel.com; lmartini@cisco.com; =
Thomas D.=20
          Nadeau; mmorrow@cisco.com<BR><B>Cc:</B> pwe3@ietf.org; Shell =
Nakash;=20
          Prashant Desai; Igor Danilovich; Itamar =
Levy<BR><B>Subject:</B> RE: A=20
          question regarding torn down PWs in=20
          draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
          <DIV></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D214484013-05012009><FONT=20
          face=3DArial size=3D2>Hi Sasha,</FONT></SPAN></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D214484013-05012009><FONT=20
          face=3DArial size=3D2></FONT></SPAN>&nbsp;</DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D214484013-05012009><FONT=20
          face=3DArial size=3D2>&gt;&gt; <SPAN =
class=3D012494009-05012009><FONT=20
          face=3DArial size=3D2>Does the quoted text imply that =
implementations must=20
          distinguish between PWs being torn=20
          down</FONT></SPAN></FONT></SPAN></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D214484013-05012009><FONT=20
          face=3DArial size=3D2><SPAN class=3D012494009-05012009><FONT =
face=3DArial=20
          size=3D2>&gt;&gt; due to failures of their control sessions =
and PWs that=20
          are torn down for any other =
reason?</FONT></SPAN></FONT></SPAN></DIV>
          <DIV>&nbsp;</DIV>
          <DIV><FONT face=3DArial size=3D2><SPAN=20
          class=3D214484013-05012009>Whether&nbsp;PWs are torn down =
because of a=20
          defect (whether it is in the control plane or in the data =
plane), the=20
          consequent actions are the same.<BR><SPAN=20
          class=3D017510414-05012009><FONT =
color=3D#0000ff><EM>[[Sasha]]&nbsp;I am=20
          not aware of the case when a PW is torn down due to defects in =
the=20
          data plane. Could you please provide a reference/an=20
          example?</EM></FONT></SPAN></SPAN></FONT></DIV>
          <DIV><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =

          size=3D2>&nbsp;It would be good, however, if a PE would be =
able to=20
          distinguish between PWs torn down because of defects and PWs =
torn down=20
          for administrative reasons, because in the latter case there =
is no=20
          need to insert an FDI message downstream.<BR><SPAN=20
          class=3D017510414-05012009><FONT =
color=3D#0000ff><EM>[[Sasha]]&nbsp;I do=20
          not think that RFC 4447 provides for that.&nbsp;In addition, =
please=20
          consider the following=20
          scenario:</EM></FONT></SPAN></FONT></FONT></SPAN></DIV>
          <OL>
            <LI><SPAN class=3D214484013-05012009><FONT =
face=3DArial><FONT=20
            size=3D2><SPAN class=3D017510414-05012009><FONT =
color=3D#0000ff><EM>A PW=20
            is set up</EM></FONT></SPAN></FONT></FONT></SPAN>=20
            <LI><SPAN class=3D214484013-05012009><FONT =
face=3DArial><FONT=20
            size=3D2><SPAN class=3D017510414-05012009><FONT =
color=3D#0000ff><EM>The PW=20
            is torn down&nbsp;due to the CP defect (targeted LDP session =
went=20
            down). FDI is inserted in the local=20
            AC</EM></FONT></SPAN></FONT></FONT></SPAN>=20
            <LI><SPAN class=3D214484013-05012009><FONT =
face=3DArial><FONT=20
            size=3D2><SPAN class=3D017510414-05012009><EM>&nbsp;<FONT=20
            color=3D#0000ff>The user has deleted the PW end point in the =
remote=20
            PE. Since the LDP session is down, this fact is not =
communicated to=20
            the local PE</FONT></EM></SPAN></FONT></FONT></SPAN>=20
            <LI><SPAN class=3D214484013-05012009><FONT =
face=3DArial><FONT=20
            color=3D#0000ff size=3D2><SPAN =
class=3D017510414-05012009><EM>Targeted LDP=20
            session is restored but an attempt of the local PE to =
restore the PW=20
            fails since there is no remote peer anymore. <STRONG>What =
should now=20
            happen to the local=20
            AC</STRONG>?</EM></SPAN></FONT></FONT></SPAN></LI></OL>
          <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
          class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
          <DIV><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =

          size=3D2>Remember that Luca sent an email to the list =
proposing to add a=20
          BFD code point to indicate that an AC was taken down for =
admistrative=20
          reasons. That proposal was driven by the same =
motivation.<BR><SPAN=20
          class=3D017510414-05012009><FONT=20
          color=3D#0000ff><EM>[[Sasha]]&nbsp;I&nbsp;remember that, and I =
believe=20
          I've sent a couple of messages to the list questioning the =
rationale=20
          of&nbsp;such a code point.=20
          &nbsp;</EM></FONT></SPAN></FONT></FONT></SPAN></DIV>
          <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
          class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
          <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
          class=3D214484013-05012009>Peter</SPAN></FONT></FONT></DIV>
          <DIV><FONT size=3D2><SPAN=20
          class=3D214484013-05012009></SPAN></FONT>&nbsp;</DIV>
          <DIV><FONT size=3D2><SPAN=20
          class=3D214484013-05012009></SPAN></FONT>&nbsp;</DIV>
          <BLOCKQUOTE dir=3Dltr=20
          style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: =
#000000 2px solid; MARGIN-RIGHT: 0px">
            <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
            <HR tabIndex=3D-1>
            <FONT face=3DTahoma size=3D2><B>From:</B> Alexander =
Vainshtein=20
            [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> =
Monday,=20
            January 05, 2009 5:12 AM<BR><B>To:</B> Aissaoui, Mustapha=20
            (Mustapha); Busschbach, Peter B (Peter); dallan@nortel.com;=20
            lmartini@cisco.com; Thomas D. Nadeau;=20
            mmorrow@cisco.com<BR><B>Cc:</B> pwe3@ietf.org; Shell Nakash; =

            Prashant Desai; Igor Danilovich; Itamar =
Levy<BR><B>Subject:</B> A=20
            question regarding torn down PWs in=20
            draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
            <DIV></DIV>
            <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>Hi=20
            Monique/Mustapha/Peter/Dave/Thom/Luca,</FONT></SPAN></DIV>
            <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>I have a=20
            question to you as the editors of the expired)=20
            draft-ietf-pwe3-oam-msg-map-08.txt.</FONT></SPAN></DIV>
            <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>The=20
            question is related&nbsp;to the following text in Section=20
            <STRONG>8.2.1. PW Forward Defect State Entry/Exit=20
            Criteria</STRONG>:</FONT></SPAN></DIV>
            <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
            size=3D2>&lt;quote&gt;</FONT></SPAN></DIV>
            <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
              <DIV><SPAN class=3D012494009-05012009><EM><FONT=20
              color=3D#0000ff>&nbsp;&nbsp; Note that if the PW control =
session=20
              between the PEs fails, the PW is <BR>&nbsp;&nbsp; torn =
down and=20
              needs to be re-established. This includes failure of=20
              <BR>&nbsp;&nbsp; the T-LDP session, the L2TP session, or =
the L2TP=20
              control connection. <BR>&nbsp;&nbsp; However, the =
consequent=20
              actions towards the ACs are the same as if =
<BR>&nbsp;&nbsp; the PW=20
              entered the forward defect=20
            state.</FONT></EM></SPAN></DIV></BLOCKQUOTE>
            <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>&lt;end=20
            quote&gt;</FONT></SPAN></DIV>
            <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>The PW=20
            may be torn down not just because the PW control session =
between the=20
            PEs fails. E.g., the PW can be deleted by the operator in =
one of the=20
            PEs.</FONT></SPAN></DIV>
            <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>Does the=20
            quoted text imply that implementations must distinguish =
between PWs=20
            being torn down due to failures of their control sessions =
and PWs=20
            that are torn down for any other reason?</FONT></SPAN></DIV>
            <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>The use=20
            case of special interest would be a PW that has been set up =
(and=20
            later torn down) using a single-sided=20
            mechanism...</FONT></SPAN></DIV>
            <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>I'd also=20
            like to note that there are several references in the draft =
to=20
            unspecified defects&nbsp;<EM><FONT color=3D#0000ff> "that do =
not=20
            result in the PW being torn =
down</FONT></EM>"...</FONT></SPAN></DIV>
            <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
            size=3D2></FONT></SPAN>&nbsp;</DIV>
            <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
            size=3D2>Regards,</FONT></SPAN></DIV>
            <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
            size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</FONT></SPAN></DIV>
            <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
            size=3D2></FONT></SPAN>&nbsp;</DIV>
            <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
            =
size=3D2></FONT></SPAN>&nbsp;</DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE=
></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C96F76.90CA8F1F--

--===============1301319852==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1301319852==--


From pwe3-bounces@ietf.org  Mon Jan  5 13:41:42 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DDB8A3A6903;
	Mon,  5 Jan 2009 13:41:42 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1851B3A6903
	for <pwe3@core3.amsl.com>; Mon,  5 Jan 2009 13:41:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.898
X-Spam-Level: 
X-Spam-Status: No, score=-5.898 tagged_above=-999 required=5 tests=[AWL=0.701, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 5uU3lTAxknJZ for <pwe3@core3.amsl.com>;
	Mon,  5 Jan 2009 13:41:41 -0800 (PST)
Received: from zcars04f.nortel.com (zcars04f.nortel.com [47.129.242.57])
	by core3.amsl.com (Postfix) with ESMTP id 033D83A67A1
	for <pwe3@ietf.org>; Mon,  5 Jan 2009 13:41:40 -0800 (PST)
Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com
	[47.129.230.99])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	n05LfOO09507; Mon, 5 Jan 2009 21:41:24 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 Jan 2009 16:41:08 -0500
Message-ID: <87AC5F88F03E6249AEA68D40BD3E00BE168326A2@zcarhxm2.corp.nortel.com>
In-Reply-To: <49626DDD.3070305@chello.nl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] A question regarding torn down
	PWsin	draft-ietf-pwe3-oam-msg-map-08.txt
Thread-Index: AclvdHkoaQnBackJTW+NGUovwU/kEgACBPHg
References: <A3C5DF08D38B6049839A6F553B331C7698C2C6CCC1@ILPTMAIL02.ecitele.com>	<E60778C3916D3548BBCF4D964186348F022953BD@ILEXC2U01.ndc.lucent.com>	<A3C5DF08D38B6049839A6F553B331C7698C2C6CDE7@ILPTMAIL02.ecitele.com>	<87AC5F88F03E6249AEA68D40BD3E00BE16832699@zcarhxm2.corp.nortel.com><E60778C3916D3548BBCF4D964186348F02295525@ILEXC2U01.ndc.lucent.com>
	<49626DDD.3070305@chello.nl>
From: "David Allan" <dallan@nortel.com>
To: <hhelvoort@chello.nl>,
	"Busschbach, Peter B (Peter)" <busschbach@alcatel-lucent.com>
Cc: pwe3@ietf.org
Subject: Re: [PWE3] A question regarding torn down
	PWsin	draft-ietf-pwe3-oam-msg-map-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Hi Huub:

It seems to me that an administrative modification to a PW would not
generate the appropriate 1731 PDUs as it is not the Ethernet MEP....(and
we have not defined IWF beyond notifications and going further could get
truly ugly... ;-)

So an administrative action on a PW would appear as a defect to the
client layer... (?) 

An administrative action on the client trail would work correctly as it
would simply be relayed without modification by the PW that formed part
of the overall trail....

Would that agree with your understanding?

Cheers
Dave 

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
Huub van Helvoort
Sent: Monday, January 05, 2009 3:30 PM
To: Busschbach, Peter B (Peter)
Cc: pwe3@ietf.org
Subject: Re: [PWE3] A question regarding torn down PWsin
draft-ietf-pwe3-oam-msg-map-08.txt

Hello Peter,

You wrote:

> I seem to remember from discussions in ITU-T about Ethernet OAM that 
> an administrative action should not result in AIS insertion.

That is correct in this case a LCK PDU will be inserted.

AIS/FDI PDUs are inserted only as a consequent action to detected server
defects.

Cheers, Huub.

--
================================================================
                   http://www.van-helvoort.eu/
================================================================
Always remember that you are unique...just like everyone else...
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3


From pwe3-bounces@ietf.org  Mon Jan  5 14:55:16 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0945A28C0D8;
	Mon,  5 Jan 2009 14:55:16 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B4DA828C0D8
	for <pwe3@core3.amsl.com>; Mon,  5 Jan 2009 14:55:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 pwsWD-GGyrvo for <pwe3@core3.amsl.com>;
	Mon,  5 Jan 2009 14:55:13 -0800 (PST)
Received: from audl953.usa.alcatel.com (audl953.usa.alcatel.com
	[143.209.238.162])
	by core3.amsl.com (Postfix) with ESMTP id E656C3A68A9
	for <pwe3@ietf.org>; Mon,  5 Jan 2009 14:55:12 -0800 (PST)
Received: from usdalsbhs01.ad3.ad.alcatel.com (usdalsbhs01.usa.alcatel.com
	[172.22.216.19])
	by audl953.usa.alcatel.com (ALCANET) with ESMTP id n05MsXsj018688;
	Mon, 5 Jan 2009 16:54:51 -0600
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by
	usdalsbhs01.ad3.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Mon, 5 Jan 2009 16:54:38 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 Jan 2009 16:54:37 -0600
Message-ID: <4A5028372622294A99B8FFF6BD06EB7B04F88BE9@USDALSMBS03.ad3.ad.alcatel.com>
In-Reply-To: <E60778C3916D3548BBCF4D964186348F02295525@ILEXC2U01.ndc.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: A question regarding torn down PWs in
	draft-ietf-pwe3-oam-msg-map-08.txt
Thread-Index: AclvHgFatl4xVjfUTBai2RqcqunEfwAHTX0AAADXDMAABCyFYAAAnjpgAA1EJqA=
References: <A3C5DF08D38B6049839A6F553B331C7698C2C6CCC1@ILPTMAIL02.ecitele.com>
	<E60778C3916D3548BBCF4D964186348F022953BD@ILEXC2U01.ndc.lucent.com>
	<A3C5DF08D38B6049839A6F553B331C7698C2C6CDE7@ILPTMAIL02.ecitele.com>
	<87AC5F88F03E6249AEA68D40BD3E00BE16832699@zcarhxm2.corp.nortel.com>
	<E60778C3916D3548BBCF4D964186348F02295525@ILEXC2U01.ndc.lucent.com>
From: "AISSAOUI Mustapha" <Mustapha.Aissaoui@alcatel-lucent.com>
To: "BUSSCHBACH Peter" <busschbach@alcatel-lucent.com>,
	"David Allan" <dallan@nortel.com>,
	"Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>
X-OriginalArrivalTime: 05 Jan 2009 22:54:38.0334 (UTC)
	FILETIME=[963941E0:01C96F88]
X-Scanned-By: MIMEDefang 2.64 on 143.209.238.34
Cc: Shell Nakash <Shell.Nakash@ecitele.com>, lmartini@cisco.com,
	mmorrow@cisco.com, Igor Danilovich <Igor.Danilovich@ecitele.com>,
	pwe3@ietf.org, Itamar Levy <Itamar.Levy@ecitele.com>
Subject: Re: [PWE3] A question regarding torn down PWs in
	draft-ietf-pwe3-oam-msg-map-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1233725819=="
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1233725819==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C96F88.9627DEB3"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C96F88.9627DEB3
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Peter and Sasha,
yes an admin down of the PW should result in the PW being torn down, as
opposed to sending a status TLV, and a defect indication being sent over
the AC.=20
=20
The draft however does not preclude implementations from offering an
option to suppress defect over the AC if deemed useful.
=20
As for the "PW not forwarding" status TLV codepoint, and the BFD
equivalent one Luca asked in the mailing list, it is mostly used when
you want to signal defects, other than the AC and PW down ones, which do
not result in the PW being torn down. Thus, bringing down the PW
administratively is not one such a case. I do not think there is any
explicit specification how to use this codepoint but we use it in our
implementation for signaling defects such as when the operational MTU of
the LSP tunnel changes and does not match anymore the value signaled in
the PW interface parameters.
=20
Regards,
Mustapha.


________________________________

	From: Busschbach, Peter B (Peter)
[mailto:busschbach@alcatel-lucent.com]=20
	Sent: Monday, January 05, 2009 11:37 AM
	To: David Allan; Alexander Vainshtein
	Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor
Danilovich; Itamar Levy; AISSAOUI Mustapha; lmartini@cisco.com; Thomas
D. Nadeau; mmorrow@cisco.com
	Subject: RE: A question regarding torn down PWs in
draft-ietf-pwe3-oam-msg-map-08.txt
=09
=09
	Dave,
	=20
	I seem to remember from discussions in ITU-T about Ethernet OAM
that an administrative action should not result in AIS insertion. To be
honest, I can't remember why, though. Therefore, unless someone else
knows a reason why administrative down should not result in AIS, I
withdraw my comment.
	=20
	Peter


________________________________

		From: David Allan [mailto:dallan@nortel.com]=20
		Sent: Monday, January 05, 2009 11:16 AM
		To: Alexander Vainshtein; Busschbach, Peter B (Peter)
		Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor
Danilovich; Itamar Levy; Aissaoui, Mustapha (Mustapha);
lmartini@cisco.com; Thomas D. Nadeau; mmorrow@cisco.com
		Subject: RE: A question regarding torn down PWs in
draft-ietf-pwe3-oam-msg-map-08.txt
	=09
	=09
		hi Peter:
		=20
		Below you suggest that FDI not be inserted when a PW is
taken down administratively. I do not understand why this is different
from any other disruption of connectivity, unless it is beleived that an
administrative action is joined up across both MPLS PWs and the native
service by other means....
		=20
		Am I missing somthing?
		=20
		cheers
		Dave
		=20
		=20
		=20
		=20
________________________________

		From: Alexander Vainshtein
[mailto:Alexander.Vainshtein@ecitele.com]=20
		Sent: Monday, January 05, 2009 10:09 AM
		To: Busschbach, Peter B (Peter)
		Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor
Danilovich; Itamar Levy; Aissaoui, Mustapha (Mustapha); Allan, David
(CAR:NS00); lmartini@cisco.com; Thomas D. Nadeau; mmorrow@cisco.com
		Subject: RE: A question regarding torn down PWs in
draft-ietf-pwe3-oam-msg-map-08.txt
	=09
	=09
		Peter hi,
		Lots of thanks for a prompt response.
		=20
		Please see some comments inline below (blue italics).
		=20
		Regards,
		    Sasha


________________________________

			From: Busschbach, Peter B (Peter)
[mailto:busschbach@alcatel-lucent.com]=20
			Sent: Monday, January 05, 2009 3:51 PM
			To: Alexander Vainshtein; Aissaoui, Mustapha
(Mustapha); dallan@nortel.com; lmartini@cisco.com; Thomas D. Nadeau;
mmorrow@cisco.com
			Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai;
Igor Danilovich; Itamar Levy
			Subject: RE: A question regarding torn down PWs
in draft-ietf-pwe3-oam-msg-map-08.txt
		=09
		=09
			Hi Sasha,
			=20
			>> Does the quoted text imply that
implementations must distinguish between PWs being torn down
			>> due to failures of their control sessions and
PWs that are torn down for any other reason?
			=20
			Whether PWs are torn down because of a defect
(whether it is in the control plane or in the data plane), the
consequent actions are the same.
			[[Sasha]] I am not aware of the case when a PW
is torn down due to defects in the data plane. Could you please provide
a reference/an example?
			 It would be good, however, if a PE would be
able to distinguish between PWs torn down because of defects and PWs
torn down for administrative reasons, because in the latter case there
is no need to insert an FDI message downstream.
			[[Sasha]] I do not think that RFC 4447 provides
for that. In addition, please consider the following scenario:

			1.	A PW is set up=20
			2.	The PW is torn down due to the CP defect
(targeted LDP session went down). FDI is inserted in the local AC=20
			3.	 The user has deleted the PW end point
in the remote PE. Since the LDP session is down, this fact is not
communicated to the local PE=20
			4.	Targeted LDP session is restored but an
attempt of the local PE to restore the PW fails since there is no remote
peer anymore. What should now happen to the local AC?

			=20
			Remember that Luca sent an email to the list
proposing to add a BFD code point to indicate that an AC was taken down
for admistrative reasons. That proposal was driven by the same
motivation.
			[[Sasha]] I remember that, and I believe I've
sent a couple of messages to the list questioning the rationale of such
a code point. =20
			=20
			Peter
			=20
			=20

________________________________

				From: Alexander Vainshtein
[mailto:Alexander.Vainshtein@ecitele.com]=20
				Sent: Monday, January 05, 2009 5:12 AM
				To: Aissaoui, Mustapha (Mustapha);
Busschbach, Peter B (Peter); dallan@nortel.com; lmartini@cisco.com;
Thomas D. Nadeau; mmorrow@cisco.com
				Cc: pwe3@ietf.org; Shell Nakash;
Prashant Desai; Igor Danilovich; Itamar Levy
				Subject: A question regarding torn down
PWs in draft-ietf-pwe3-oam-msg-map-08.txt
			=09
			=09
				Hi
Monique/Mustapha/Peter/Dave/Thom/Luca,
				I have a question to you as the editors
of the expired) draft-ietf-pwe3-oam-msg-map-08.txt.
				The question is related to the following
text in Section 8.2.1. PW Forward Defect State Entry/Exit Criteria:
				<quote>

				   Note that if the PW control session
between the PEs fails, the PW is=20
				   torn down and needs to be
re-established. This includes failure of=20
				   the T-LDP session, the L2TP session,
or the L2TP control connection.=20
				   However, the consequent actions
towards the ACs are the same as if=20
				   the PW entered the forward defect
state.

				<end quote>
				The PW may be torn down not just because
the PW control session between the PEs fails. E.g., the PW can be
deleted by the operator in one of the PEs.
				Does the quoted text imply that
implementations must distinguish between PWs being torn down due to
failures of their control sessions and PWs that are torn down for any
other reason?
				The use case of special interest would
be a PW that has been set up (and later torn down) using a single-sided
mechanism...
				I'd also like to note that there are
several references in the draft to unspecified defects  "that do not
result in the PW being torn down"...
				=20
				Regards,
				     Sasha
				=20
				=20


------_=_NextPart_001_01C96F88.9627DEB3
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3492" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D715544122-05012009><FONT =
face=3DArial=20
size=3D2>Peter and Sasha,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D715544122-05012009><FONT =
face=3DArial=20
size=3D2>yes an admin down of the PW should result in the PW being torn =
down, as=20
opposed to sending a status TLV, and a defect indication being sent over =
the AC.=20
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D715544122-05012009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D715544122-05012009><FONT =
face=3DArial=20
size=3D2>The draft however does not=20
preclude&nbsp;implementations&nbsp;from&nbsp;offering an option to =
suppress=20
defect over the AC if deemed useful.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D715544122-05012009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D715544122-05012009><FONT =
face=3DArial=20
size=3D2>As for the "PW not forwarding" status TLV codepoint, and the =
BFD=20
equivalent one Luca asked in the mailing list, it is mostly used when =
you want=20
to signal defects, other than the AC and PW down ones,&nbsp;which do not =
result=20
in the PW being torn down. Thus, bringing down the PW administratively =
is not=20
one such a case. I do not think there is any explicit specification how =
to use=20
this codepoint&nbsp;but we use it in our implementation for signaling =
defects=20
such as when the operational MTU of the LSP tunnel changes and does not =
match=20
anymore&nbsp;the value signaled in the PW interface=20
parameters.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D715544122-05012009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D715544122-05012009><FONT =
face=3DArial=20
size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D715544122-05012009><FONT =
face=3DArial=20
size=3D2>Mustapha.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Busschbach, Peter B (Peter)=20
  [mailto:busschbach@alcatel-lucent.com] <BR><B>Sent:</B> Monday, =
January 05,=20
  2009 11:37 AM<BR><B>To:</B> David Allan; Alexander =
Vainshtein<BR><B>Cc:</B>=20
  pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor Danilovich; Itamar =
Levy;=20
  AISSAOUI Mustapha; lmartini@cisco.com; Thomas D. Nadeau;=20
  mmorrow@cisco.com<BR><B>Subject:</B> RE: A question regarding torn =
down PWs in=20
  draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
  size=3D2>Dave,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
  size=3D2>I seem to remember from discussions in ITU-T about Ethernet =
OAM that an=20
  administrative action should not result in AIS insertion. To be =
honest, I=20
  can't remember why, though. Therefore, unless someone else knows a =
reason why=20
  administrative down should not result in AIS, I withdraw my=20
  comment.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D578032216-05012009><FONT =
face=3DArial=20
  size=3D2>Peter</FONT></SPAN></DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> David Allan =
[mailto:dallan@nortel.com]=20
    <BR><B>Sent:</B> Monday, January 05, 2009 11:16 AM<BR><B>To:</B> =
Alexander=20
    Vainshtein; Busschbach, Peter B (Peter)<BR><B>Cc:</B> pwe3@ietf.org; =
Shell=20
    Nakash; Prashant Desai; Igor Danilovich; Itamar Levy; Aissaoui, =
Mustapha=20
    (Mustapha); lmartini@cisco.com; Thomas D. Nadeau;=20
    mmorrow@cisco.com<BR><B>Subject:</B> RE: A question regarding torn =
down PWs=20
    in draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D746210416-05012009>hi=20
    Peter:</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D746210416-05012009>Below you suggest that FDI not be =
inserted when a=20
    PW is taken down administratively.&nbsp;I do not understand why this =

    is&nbsp;different from any other disruption of connectivity, unless =
it is=20
    beleived that an administrative action is joined up across both MPLS =

    PWs&nbsp;and the native service by other =
means....</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D746210416-05012009>Am=20
    I missing somthing?</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D746210416-05012009>cheers</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D746210416-05012009>Dave</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D746210416-05012009></SPAN></FONT>&nbsp;</DIV>
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> Alexander Vainshtein=20
    [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> Monday, =
January=20
    05, 2009 10:09 AM<BR><B>To:</B> Busschbach, Peter B =
(Peter)<BR><B>Cc:</B>=20
    pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor Danilovich; Itamar =
Levy;=20
    Aissaoui, Mustapha (Mustapha); Allan, David (CAR:NS00); =
lmartini@cisco.com;=20
    Thomas D. Nadeau; mmorrow@cisco.com<BR><B>Subject:</B> RE: A =
question=20
    regarding torn down PWs in=20
    draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D017510414-05012009>Peter hi,</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D017510414-05012009>Lots of thanks for a prompt=20
    response.</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D017510414-05012009></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D017510414-05012009>Please see some comments inline below =
(<EM>blue=20
    italics</EM>).</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D017510414-05012009></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D017510414-05012009>Regards,</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D017510414-05012009>&nbsp;&nbsp;&nbsp; =
Sasha</SPAN></FONT></DIV><BR>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff =
2px solid; MARGIN-RIGHT: 0px">
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
      <HR tabIndex=3D-1>
      <FONT face=3DTahoma size=3D2><B>From:</B> Busschbach, Peter B =
(Peter)=20
      [mailto:busschbach@alcatel-lucent.com] <BR><B>Sent:</B> Monday, =
January=20
      05, 2009 3:51 PM<BR><B>To:</B> Alexander Vainshtein; Aissaoui, =
Mustapha=20
      (Mustapha); dallan@nortel.com; lmartini@cisco.com; Thomas D. =
Nadeau;=20
      mmorrow@cisco.com<BR><B>Cc:</B> pwe3@ietf.org; Shell Nakash; =
Prashant=20
      Desai; Igor Danilovich; Itamar Levy<BR><B>Subject:</B> RE: A =
question=20
      regarding torn down PWs in=20
      draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
      <DIV></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT =
face=3DArial=20
      size=3D2>Hi Sasha,</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT =
face=3DArial=20
      size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT =
face=3DArial=20
      size=3D2>&gt;&gt; <SPAN class=3D012494009-05012009><FONT =
face=3DArial=20
      size=3D2>Does the quoted text imply that implementations must =
distinguish=20
      between PWs being torn down</FONT></SPAN></FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT =
face=3DArial=20
      size=3D2><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>&gt;&gt; due=20
      to failures of their control sessions and PWs that are torn down =
for any=20
      other reason?</FONT></SPAN></FONT></SPAN></DIV>
      <DIV>&nbsp;</DIV>
      <DIV><FONT face=3DArial size=3D2><SPAN=20
      class=3D214484013-05012009>Whether&nbsp;PWs are torn down because =
of a=20
      defect (whether it is in the control plane or in the data plane), =
the=20
      consequent actions are the same.<BR><SPAN =
class=3D017510414-05012009><FONT=20
      color=3D#0000ff><EM>[[Sasha]]&nbsp;I am not aware of the case when =
a PW is=20
      torn down due to defects in the data plane. Could you please =
provide a=20
      reference/an example?</EM></FONT></SPAN></SPAN></FONT></DIV>
      <DIV><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2>&nbsp;It=20
      would be good, however, if a PE would be able to distinguish =
between PWs=20
      torn down because of defects and PWs torn down for administrative =
reasons,=20
      because in the latter case there is no need to insert an FDI =
message=20
      downstream.<BR><SPAN class=3D017510414-05012009><FONT=20
      color=3D#0000ff><EM>[[Sasha]]&nbsp;I do not think that RFC 4447 =
provides for=20
      that.&nbsp;In addition, please consider the following=20
      scenario:</EM></FONT></SPAN></FONT></FONT></SPAN></DIV>
      <OL>
        <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2><SPAN=20
        class=3D017510414-05012009><FONT color=3D#0000ff><EM>A PW is set =

        up</EM></FONT></SPAN></FONT></FONT></SPAN>=20
        <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2><SPAN=20
        class=3D017510414-05012009><FONT color=3D#0000ff><EM>The PW is =
torn=20
        down&nbsp;due to the CP defect (targeted LDP session went down). =
FDI is=20
        inserted in the local AC</EM></FONT></SPAN></FONT></FONT></SPAN> =

        <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2><SPAN=20
        class=3D017510414-05012009><EM>&nbsp;<FONT color=3D#0000ff>The =
user has=20
        deleted the PW end point in the remote PE. Since the LDP session =
is=20
        down, this fact is not communicated to the local=20
        PE</FONT></EM></SPAN></FONT></FONT></SPAN>=20
        <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
color=3D#0000ff=20
        size=3D2><SPAN class=3D017510414-05012009><EM>Targeted LDP =
session is=20
        restored but an attempt of the local PE to restore the PW fails =
since=20
        there is no remote peer anymore. <STRONG>What should now happen =
to the=20
        local AC</STRONG>?</EM></SPAN></FONT></FONT></SPAN></LI></OL>
      <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
      class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
      <DIV><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2>Remember=20
      that Luca sent an email to the list proposing to add a BFD code =
point to=20
      indicate that an AC was taken down for admistrative reasons. That =
proposal=20
      was driven by the same motivation.<BR><SPAN =
class=3D017510414-05012009><FONT=20
      color=3D#0000ff><EM>[[Sasha]]&nbsp;I&nbsp;remember that, and I =
believe I've=20
      sent a couple of messages to the list questioning the rationale=20
      of&nbsp;such a code point.=20
      &nbsp;</EM></FONT></SPAN></FONT></FONT></SPAN></DIV>
      <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
      class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
      class=3D214484013-05012009>Peter</SPAN></FONT></FONT></DIV>
      <DIV><FONT size=3D2><SPAN=20
class=3D214484013-05012009></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT size=3D2><SPAN=20
class=3D214484013-05012009></SPAN></FONT>&nbsp;</DIV>
      <BLOCKQUOTE dir=3Dltr=20
      style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 =
2px solid; MARGIN-RIGHT: 0px">
        <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
        <HR tabIndex=3D-1>
        <FONT face=3DTahoma size=3D2><B>From:</B> Alexander Vainshtein=20
        [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> =
Monday,=20
        January 05, 2009 5:12 AM<BR><B>To:</B> Aissaoui, Mustapha =
(Mustapha);=20
        Busschbach, Peter B (Peter); dallan@nortel.com; =
lmartini@cisco.com;=20
        Thomas D. Nadeau; mmorrow@cisco.com<BR><B>Cc:</B> pwe3@ietf.org; =
Shell=20
        Nakash; Prashant Desai; Igor Danilovich; Itamar =
Levy<BR><B>Subject:</B>=20
        A question regarding torn down PWs in=20
        draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
        <DIV></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>Hi=20
        Monique/Mustapha/Peter/Dave/Thom/Luca,</FONT></SPAN></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>I have a=20
        question to you as the editors of the expired)=20
        draft-ietf-pwe3-oam-msg-map-08.txt.</FONT></SPAN></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>The question=20
        is related&nbsp;to the following text in Section <STRONG>8.2.1. =
PW=20
        Forward Defect State Entry/Exit =
Criteria</STRONG>:</FONT></SPAN></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
        size=3D2>&lt;quote&gt;</FONT></SPAN></DIV>
        <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
          <DIV><SPAN class=3D012494009-05012009><EM><FONT=20
          color=3D#0000ff>&nbsp;&nbsp; Note that if the PW control =
session between=20
          the PEs fails, the PW is <BR>&nbsp;&nbsp; torn down and needs =
to be=20
          re-established. This includes failure of <BR>&nbsp;&nbsp; the =
T-LDP=20
          session, the L2TP session, or the L2TP control connection.=20
          <BR>&nbsp;&nbsp; However, the consequent actions towards the =
ACs are=20
          the same as if <BR>&nbsp;&nbsp; the PW entered the forward =
defect=20
          state.</FONT></EM></SPAN></DIV></BLOCKQUOTE>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>&lt;end=20
        quote&gt;</FONT></SPAN></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>The PW may=20
        be torn down not just because the PW control session between the =
PEs=20
        fails. E.g., the PW can be deleted by the operator in one of the =

        PEs.</FONT></SPAN></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>Does the=20
        quoted text imply that implementations must distinguish between =
PWs=20
        being torn down due to failures of their control sessions and =
PWs that=20
        are torn down for any other reason?</FONT></SPAN></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>The use case=20
        of special interest would be a PW that has been set up (and =
later torn=20
        down) using a single-sided mechanism...</FONT></SPAN></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial =
size=3D2>I'd also=20
        like to note that there are several references in the draft to=20
        unspecified defects&nbsp;<EM><FONT color=3D#0000ff> "that do not =
result in=20
        the PW being torn down</FONT></EM>"...</FONT></SPAN></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
        size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
        size=3D2>Regards,</FONT></SPAN></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
        size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</FONT></SPAN></DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
        size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV><SPAN class=3D012494009-05012009><FONT face=3DArial=20
        =
size=3D2></FONT></SPAN>&nbsp;</DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE=
></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C96F88.9627DEB3--

--===============1233725819==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1233725819==--


From pwe3-bounces@ietf.org  Mon Jan  5 15:21:59 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8AC9D3A6881;
	Mon,  5 Jan 2009 15:21:59 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 572153A68B9
	for <pwe3@core3.amsl.com>; Mon,  5 Jan 2009 15:21:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[AWL=0.389, 
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_AT=0.424,
	RCVD_IN_DNSWL_LOW=-1, RDNS_NONE=0.1]
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 6hjyonmi04aX for <pwe3@core3.amsl.com>;
	Mon,  5 Jan 2009 15:21:57 -0800 (PST)
Received: from viefep18-int.chello.at (unknown [62.179.121.38])
	by core3.amsl.com (Postfix) with ESMTP id DB2173A6881
	for <pwe3@ietf.org>; Mon,  5 Jan 2009 15:21:56 -0800 (PST)
Received: from edge05.upc.biz ([192.168.13.212]) by viefep18-int.chello.at
	(InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP
	id <20090105232142.FMLR10001.viefep18-int.chello.at@edge05.upc.biz>
	for <pwe3@ietf.org>; Tue, 6 Jan 2009 00:21:42 +0100
Received: from McAsterix.local ([24.132.228.153]) by edge05.upc.biz with edge
	id zzMg1a01V3KDBhC05zMhJH; Tue, 06 Jan 2009 00:21:42 +0100
X-SourceIP: 24.132.228.153
Message-ID: <49629604.4000301@chello.nl>
Date: Tue, 06 Jan 2009 00:21:40 +0100
From: Huub van Helvoort <hhelvoort@chello.nl>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: pwe3@ietf.org
References: <A3C5DF08D38B6049839A6F553B331C7698C2C6CCC1@ILPTMAIL02.ecitele.com>	<E60778C3916D3548BBCF4D964186348F022953BD@ILEXC2U01.ndc.lucent.com>	<A3C5DF08D38B6049839A6F553B331C7698C2C6CDE7@ILPTMAIL02.ecitele.com>	<87AC5F88F03E6249AEA68D40BD3E00BE16832699@zcarhxm2.corp.nortel.com><E60778C3916D3548BBCF4D964186348F02295525@ILEXC2U01.ndc.lucent.com>
	<49626DDD.3070305@chello.nl>
	<87AC5F88F03E6249AEA68D40BD3E00BE168326A2@zcarhxm2.corp.nortel.com>
In-Reply-To: <87AC5F88F03E6249AEA68D40BD3E00BE168326A2@zcarhxm2.corp.nortel.com>
Subject: Re: [PWE3] A question regarding torn down
	PWsin	draft-ietf-pwe3-oam-msg-map-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: hhelvoort@chello.nl
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Hello Dave,

You replied:

> It seems to me that an administrative modification to a PW would not
> generate the appropriate 1731 PDUs as it is not the Ethernet MEP....

Indeed. I answered the question regarding Ethernet OAM.

> So an administrative action on a PW would appear as a defect to the
> client layer... (?) 

Yes.

> An administrative action on the client trail would work correctly as it
> would simply be relayed without modification by the PW that formed part
> of the overall trail....

OK.

> Would that agree with your understanding?

Indeed.

Cheers, Huub.

> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
> Huub van Helvoort
> Sent: Monday, January 05, 2009 3:30 PM
> To: Busschbach, Peter B (Peter)
> Cc: pwe3@ietf.org
> Subject: Re: [PWE3] A question regarding torn down PWsin
> draft-ietf-pwe3-oam-msg-map-08.txt
> 
> Hello Peter,
> 
> You wrote:
> 
>> I seem to remember from discussions in ITU-T about Ethernet OAM that 
>> an administrative action should not result in AIS insertion.
> 
> That is correct in this case a LCK PDU will be inserted.
> 
> AIS/FDI PDUs are inserted only as a consequent action to detected server
> defects.
> 
> Cheers, Huub.
> 
> --
> ================================================================
>                    http://www.van-helvoort.eu/
> ================================================================
> Always remember that you are unique...just like everyone else...
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> 

-- 
================================================================
                   http://www.van-helvoort.eu/
================================================================
Always remember that you are unique...just like everyone else...
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3


From pwe3-bounces@ietf.org  Tue Jan  6 03:58:14 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DC2363A67FC;
	Tue,  6 Jan 2009 03:58:14 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6662B3A67FC
	for <pwe3@core3.amsl.com>; Tue,  6 Jan 2009 03:58:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.523
X-Spam-Level: 
X-Spam-Status: No, score=-2.523 tagged_above=-999 required=5 tests=[AWL=0.075, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 KscIyr1bO+As for <pwe3@core3.amsl.com>;
	Tue,  6 Jan 2009 03:58:12 -0800 (PST)
Received: from eci-iron1.ecitele.com (eci-iron1.ecitele.com [147.234.242.117])
	by core3.amsl.com (Postfix) with ESMTP id 2900C3A6768
	for <pwe3@ietf.org>; Tue,  6 Jan 2009 03:58:10 -0800 (PST)
Received: from unknown (HELO ILPTAM01.ecitele.com) ([147.234.244.44])
	by eci-iron1.ecitele.com with ESMTP; 06 Jan 2009 14:21:51 +0200
Received: from ILPTEXCH02.ecitele.com ([147.234.245.181]) by
	ILPTAM01.ecitele.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 6 Jan 2009 13:57:56 +0200
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by
	ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Tue, 6 Jan 2009
	13:57:56 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "Busschbach, Peter B (Peter)" <busschbach@alcatel-lucent.com>
Date: Tue, 6 Jan 2009 13:57:54 +0200
Thread-Topic: A question regarding torn down PWs in
	draft-ietf-pwe3-oam-msg-map-08.txt
Thread-Index: AclvHgFatl4xVjfUTBai2RqcqunEfwAHTX0AAADXDMAABCCuAAAiuSoA
Message-ID: <A3C5DF08D38B6049839A6F553B331C7698C34E3EE3@ILPTMAIL02.ecitele.com>
References: <A3C5DF08D38B6049839A6F553B331C7698C2C6CCC1@ILPTMAIL02.ecitele.com>
	<E60778C3916D3548BBCF4D964186348F022953BD@ILEXC2U01.ndc.lucent.com>
	<A3C5DF08D38B6049839A6F553B331C7698C2C6CDE7@ILPTMAIL02.ecitele.com>
	<E60778C3916D3548BBCF4D964186348F022954DD@ILEXC2U01.ndc.lucent.com>
In-Reply-To: <E60778C3916D3548BBCF4D964186348F022954DD@ILEXC2U01.ndc.lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-OriginalArrivalTime: 06 Jan 2009 11:57:56.0880 (UTC)
	FILETIME=[038A4100:01C96FF6]
Cc: Shell Nakash <Shell.Nakash@ecitele.com>,
	"lmartini@cisco.com" <lmartini@cisco.com>,
	"mmorrow@cisco.com" <mmorrow@cisco.com>,
	Igor Danilovich <Igor.Danilovich@ecitele.com>,
	"pwe3@ietf.org" <pwe3@ietf.org>, "Aissaoui,
	Mustapha \(Mustapha\)" <mustapha.aissaoui@alcatel-lucent.com>,
	Itamar Levy <Itamar.Levy@ecitele.com>
Subject: Re: [PWE3] A question regarding torn down PWs in
 draft-ietf-pwe3-oam-msg-map-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0655282542=="
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

--===============0655282542==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_A3C5DF08D38B6049839A6F553B331C7698C34E3EE3ILPTMAIL02eci_"

--_000_A3C5DF08D38B6049839A6F553B331C7698C34E3EE3ILPTMAIL02eci_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Peter,
I see that I have been wrong when I've said that 4447 does not allow differ=
entiation between PW teardown due to defects and any other case of the PW t=
eardown. In fact, it does by allocating a dedicated LDP status code 0x00000=
02B  - "Label Withdraw PW Status Method Not Supported"   that must be used =
in the Label Release Message if the PW is torn down due to defects. 4447 de=
scribes this as an optional method for equipment that does not support PW S=
tatus TLV.

Regarding the example, please note that the PWs can be set up in a single-e=
nded manner using FEX 129. I would expect that, in this case, the users wou=
ld presumably delete them in a single-ended way as well, initiating the tea=
rdown process at the same PE that has been used to set it up. This explains=
 (hopefully) why in certain situations the user would remove the PW at one =
end only.

If this explanation makes sense, then the problem I see with my example is =
easy to understand:

 *   If the PW is torn down while the CP is OK, the remote PE would not ins=
ert any AIS/FDI into its local AC
 *   If the PW is torn down while the CP is not operational (the targeted L=
DP session is down), then AIS/FDI insertion (activated by the CP failure) w=
ould persist until such time when the user deletes its endpoint in the othe=
r PE
 *   The bottom line: the behavior of the PW endpoint depends on the actual=
 sequence of events. This does not look healthy to me.

Hopefully this clarifies the situation.

Regards,
     Sasha
________________________________
From: Busschbach, Peter B (Peter) [mailto:busschbach@alcatel-lucent.com]
Sent: Monday, January 05, 2009 6:13 PM
To: Alexander Vainshtein
Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor Danilovich; Itamar Le=
vy; Aissaoui, Mustapha (Mustapha); dallan@nortel.com; lmartini@cisco.com; T=
homas D. Nadeau; mmorrow@cisco.com
Subject: RE: A question regarding torn down PWs in draft-ietf-pwe3-oam-msg-=
map-08.txt

Sasha,

Please see in-line

________________________________
From: Alexander Vainshtein [mailto:Alexander.Vainshtein@ecitele.com]
Sent: Monday, January 05, 2009 10:09 AM

[snipped]


[[Sasha]] I am not aware of the case when a PW is torn down due to defects =
in the data plane. Could you please provide a reference/an example?


[PB]  See section 5.4.1 of RFC 4447: a simple label withdraw method MAY als=
o be
   supported as a legacy means of signaling PW status and AC status


 It would be good, however, if a PE would be able to distinguish between PW=
s torn down because of defects and PWs torn down for administrative reasons=
, because in the latter case there is no need to insert an FDI message down=
stream.
[[Sasha]] I do not think that RFC 4447 provides for that. In addition, plea=
se consider the following scenario:

 1.  A PW is set up
 2.  The PW is torn down due to the CP defect (targeted LDP session went do=
wn). FDI is inserted in the local AC
 3.   The user has deleted the PW end point in the remote PE. Since the LDP=
 session is down, this fact is not communicated to the local PE
 4.  Targeted LDP session is restored but an attempt of the local PE to res=
tore the PW fails since there is no remote peer anymore. What should now ha=
ppen to the local AC



[PB] I don't understand the example. Who is the user that removes the PW en=
d point? A service provider? If so, why would that service provider update =
one PE to remove the PW but not the peer?

In any case, if the local PE is inserting FDI messages periodically on the =
local AC, it will continue doing so as long as the PW is not restored. Do y=
ou believe it should behave otherwise?

[snipped to the end]

--_000_A3C5DF08D38B6049839A6F553B331C7698C34E3EE3ILPTMAIL02eci_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3492" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000ff=20
size=3D2>Peter,</FONT></SPAN></DIV>
<DIV><SPAN class=3D424163708-06012009><FONT face=3DArial><FONT size=3D2><FO=
NT=20
color=3D#0000ff>I see that I have been wrong when I've said that 4447 does =
not=20
allow differentiation between PW teardown due to defects and any other case=
 of=20
the PW teardown. In fact, it does by allocating a dedicated LDP status code=
=20
<STRONG>0x0000002B&nbsp; - </STRONG></FONT></FONT><FONT size=3D2><FONT=20
color=3D#0000ff><STRONG>"Label Withdraw PW Status Method Not=20
Supported"&nbsp;</STRONG>&nbsp; that must be used in the <STRONG>Label Rele=
ase=20
Message</STRONG> if the PW is torn down due to defects. 4447 describes this=
 as=20
an optional method for equipment that does not support PW Status=20
TLV.</FONT></FONT></FONT></SPAN><SPAN class=3D424163708-06012009><FONT face=
=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN></DIV><SPAN class=3D424163708-060120=
09>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000ff=20
size=3D2>Regarding the example, please note that the PWs can be set up in a=
=20
single-ended manner using FEX 129. I would expect that, in this case, the u=
sers=20
would presumably&nbsp;delete them&nbsp;in a single-ended way as well, initi=
ating=20
the teardown process at the same PE that has been used to set it up. This=20
explains (hopefully) why in certain situations the user would remove the PW=
 at=20
one end only. </FONT></SPAN></DIV>
<DIV><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000ff si=
ze=3D2>If=20
this explanation makes sense, then the problem I see with my example is eas=
y to=20
understand:</FONT></SPAN></DIV>
<UL>
  <LI><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000ff s=
ize=3D2>If=20
  the PW is torn down while the CP is OK, the remote PE would not insert an=
y=20
  AIS/FDI into its local AC</FONT></SPAN></LI>
  <LI><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000ff s=
ize=3D2>If=20
  the PW is torn down while the CP is not operational (the targeted LDP ses=
sion=20
  is down), then AIS/FDI insertion (activated by the CP failure) would pers=
ist=20
  until such time when the user deletes its endpoint in the other=20
  PE</FONT></SPAN></LI>
  <LI><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000ff s=
ize=3D2>The=20
  bottom line: the behavior of the PW endpoint depends on the actual sequen=
ce of=20
  events. This does not look healthy to me.</FONT></SPAN></LI></UL>
<DIV><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000ff=20
size=3D2>Hopefully this clarifies the situation.</FONT></SPAN></DIV>
<DIV><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000ff=20
size=3D2>Regards,</FONT></SPAN></DIV>
<DIV><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000ff=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</FONT></SPAN></SPAN></DIV>
<DIV>
<HR tabIndex=3D-1>
</DIV>
<DIV><FONT face=3DTahoma size=3D2><B>From:</B> Busschbach, Peter B (Peter)=
=20
[mailto:busschbach@alcatel-lucent.com] <BR><B>Sent:</B> Monday, January 05,=
 2009=20
6:13 PM<BR><B>To:</B> Alexander Vainshtein<BR><B>Cc:</B> pwe3@ietf.org; She=
ll=20
Nakash; Prashant Desai; Igor Danilovich; Itamar Levy; Aissaoui, Mustapha=20
(Mustapha); dallan@nortel.com; lmartini@cisco.com; Thomas D. Nadeau;=20
mmorrow@cisco.com<BR><B>Subject:</B> RE: A question regarding torn down PWs=
 in=20
draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D285020316-05012009><FONT face=
=3DArial=20
  size=3D2>Sasha,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D285020316-05012009><FONT face=
=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D285020316-05012009><FONT face=
=3DArial=20
  size=3D2>Please see in-line</FONT></SPAN></DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px so=
lid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma><FONT size=3D2><B>From:</B> Alexander Vainshtein=20
    [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> Monday, Janu=
ary=20
    05, 2009 10:09 AM<BR></FONT></FONT><FONT face=3DTahoma><BR><FONT size=
=3D2><SPAN=20
    class=3D285020316-05012009><FONT=20
    face=3DArial>[snipped]&nbsp;</FONT></SPAN><BR></FONT></FONT><BR></DIV>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
      <DIV></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FONT fa=
ce=3DArial=20
      size=3D2><BR></FONT><SPAN class=3D017510414-05012009><FONT color=3D#0=
000ff><FONT=20
      face=3DArial><FONT size=3D2><EM>[[Sasha]]&nbsp;I am not aware of the =
case when=20
      a PW is torn down due to defects in the data plane. Could you please=
=20
      provide a reference/an=20
      example?<BR></EM></FONT></FONT></FONT></SPAN></SPAN></DIV>
      <DIV><SPAN class=3D214484013-05012009><SPAN class=3D017510414-0501200=
9><FONT=20
      color=3D#0000ff><FONT face=3DArial><FONT size=3D2><SPAN=20
      class=3D285020316-05012009></SPAN></FONT></FONT></FONT></SPAN></SPAN>=
&nbsp;</DIV>
      <DIV><SPAN class=3D214484013-05012009><SPAN class=3D017510414-0501200=
9><FONT=20
      color=3D#0000ff><FONT face=3DArial><FONT size=3D2><SPAN=20
      class=3D285020316-05012009></SPAN><BR><SPAN class=3D285020316-0501200=
9><FONT=20
      color=3D#000000>[PB]&nbsp;&nbsp;See section 5.4.1 of RFC 4447: <FONT=
=20
      size=3D3>a simple label withdraw method MAY also be<BR>&nbsp;&nbsp;=20
      supported as a legacy means of signaling PW status and AC=20
      status</FONT></FONT></SPAN><BR></DIV></FONT></FONT></FONT></SPAN></SP=
AN>
      <DIV><SPAN class=3D214484013-05012009><SPAN class=3D017510414-0501200=
9><FONT=20
      color=3D#0000ff><FONT face=3DArial><FONT size=3D2><SPAN=20
      class=3D285020316-05012009></SPAN></FONT></FONT></FONT></SPAN></SPAN>=
&nbsp;</DIV>
      <DIV><SPAN class=3D214484013-05012009><SPAN class=3D017510414-0501200=
9><FONT=20
      color=3D#0000ff><FONT face=3DArial><FONT size=3D2><SPAN=20
      class=3D285020316-05012009></SPAN></FONT></FONT></FONT></SPAN></SPAN>=
&nbsp;</DIV>
      <DIV><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT size=
=3D2>&nbsp;It=20
      would be good, however, if a PE would be able to distinguish between =
PWs=20
      torn down because of defects and PWs torn down for administrative rea=
sons,=20
      because in the latter case there is no need to insert an FDI message=
=20
      downstream.<BR><SPAN class=3D017510414-05012009><FONT=20
      color=3D#0000ff><EM>[[Sasha]]&nbsp;I do not think that RFC 4447 provi=
des for=20
      that.&nbsp;In addition, please consider the following=20
      scenario:</EM></FONT></SPAN></FONT></FONT></SPAN></DIV>
      <OL>
        <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT size=
=3D2><SPAN=20
        class=3D017510414-05012009><FONT color=3D#0000ff><EM>A PW is set=20
        up</EM></FONT></SPAN></FONT></FONT></SPAN>=20
        <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT size=
=3D2><SPAN=20
        class=3D017510414-05012009><FONT color=3D#0000ff><EM>The PW is torn=
=20
        down&nbsp;due to the CP defect (targeted LDP session went down). FD=
I is=20
        inserted in the local AC</EM></FONT></SPAN></FONT></FONT></SPAN>=20
        <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT size=
=3D2><SPAN=20
        class=3D017510414-05012009><EM>&nbsp;<FONT color=3D#0000ff>The user=
 has=20
        deleted the PW end point in the remote PE. Since the LDP session is=
=20
        down, this fact is not communicated to the local=20
        PE</FONT></EM></SPAN></FONT></FONT></SPAN>=20
        <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT color=
=3D#0000ff=20
        size=3D2><SPAN class=3D017510414-05012009><EM>Targeted LDP session =
is=20
        restored but an attempt of the local PE to restore the PW fails sin=
ce=20
        there is no remote peer anymore. <STRONG>What should now happen to =
the=20
        local AC</STRONG></EM></SPAN></FONT></FONT></SPAN></LI></OL>
      <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
      class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
      class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial size=3D2><SPAN class=3D214484013-05012009><SP=
AN=20
      class=3D285020316-05012009>[PB] I don't understand the example. Who i=
s the=20
      user that removes the PW end point? A service provider? If so, why wo=
uld=20
      that service provider update one PE to remove the PW but not the peer=
?=20
      </SPAN></SPAN></FONT></DIV>
      <DIV><FONT face=3DArial size=3D2><SPAN class=3D214484013-05012009><SP=
AN=20
      class=3D285020316-05012009></SPAN></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial size=3D2><SPAN class=3D214484013-05012009><SP=
AN=20
      class=3D285020316-05012009>In any case, if the local PE is inserting =
FDI=20
      messages periodically on the local AC, it will continue doing so as l=
ong=20
      as the PW is not restored. Do you believe it should behave=20
      otherwise?</SPAN></SPAN></FONT></DIV>
      <DIV><FONT face=3DArial size=3D2><SPAN class=3D214484013-05012009><SP=
AN=20
      class=3D285020316-05012009></SPAN></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial size=3D2><SPAN class=3D214484013-05012009><SP=
AN=20
      class=3D285020316-05012009>[snipped to the=20
    end]</SPAN></SPAN></FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE><=
/BODY></HTML>

--_000_A3C5DF08D38B6049839A6F553B331C7698C34E3EE3ILPTMAIL02eci_--

--===============0655282542==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0655282542==--


From pwe3-bounces@ietf.org  Tue Jan  6 09:49:33 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4BC0C3A6946;
	Tue,  6 Jan 2009 09:49:33 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7EB2C3A6946
	for <pwe3@core3.amsl.com>; Tue,  6 Jan 2009 09:49:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 vevrBKmIdjuI for <pwe3@core3.amsl.com>;
	Tue,  6 Jan 2009 09:49:30 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33])
	by core3.amsl.com (Postfix) with ESMTP id 0FCF43A63D2
	for <pwe3@ietf.org>; Tue,  6 Jan 2009 09:49:29 -0800 (PST)
Received: from ilexp03.ndc.lucent.com (h135-3-39-50.lucent.com [135.3.39.50])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id n06Hn5Xm002794; 
	Tue, 6 Jan 2009 11:49:05 -0600 (CST)
Received: from ILEXC2U01.ndc.lucent.com ([135.3.39.9]) by
	ilexp03.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 Jan 2009 11:49:03 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 6 Jan 2009 11:48:58 -0600
Message-ID: <E60778C3916D3548BBCF4D964186348F022EF11B@ILEXC2U01.ndc.lucent.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C7698C34E3EE3@ILPTMAIL02.ecitele.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: A question regarding torn down PWs in
	draft-ietf-pwe3-oam-msg-map-08.txt
Thread-Index: AclvHgFatl4xVjfUTBai2RqcqunEfwAHTX0AAADXDMAABCCuAAAiuSoAABL/3kA=
References: <A3C5DF08D38B6049839A6F553B331C7698C2C6CCC1@ILPTMAIL02.ecitele.com>
	<E60778C3916D3548BBCF4D964186348F022953BD@ILEXC2U01.ndc.lucent.com>
	<A3C5DF08D38B6049839A6F553B331C7698C2C6CDE7@ILPTMAIL02.ecitele.com>
	<E60778C3916D3548BBCF4D964186348F022954DD@ILEXC2U01.ndc.lucent.com>
	<A3C5DF08D38B6049839A6F553B331C7698C34E3EE3@ILPTMAIL02.ecitele.com>
From: "Busschbach, Peter B \(Peter\)" <busschbach@alcatel-lucent.com>
To: "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>
X-OriginalArrivalTime: 06 Jan 2009 17:49:03.0611 (UTC)
	FILETIME=[104A4CB0:01C97027]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Cc: Shell Nakash <Shell.Nakash@ecitele.com>, lmartini@cisco.com,
	mmorrow@cisco.com, Igor Danilovich <Igor.Danilovich@ecitele.com>,
	pwe3@ietf.org, "Aissaoui,
	Mustapha \(Mustapha\)" <mustapha.aissaoui@alcatel-lucent.com>,
	Itamar Levy <Itamar.Levy@ecitele.com>
Subject: Re: [PWE3] A question regarding torn down PWs in
	draft-ietf-pwe3-oam-msg-map-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1761535511=="
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1761535511==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C97027.0F3DDC6A"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C97027.0F3DDC6A
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Sasha,
=20
First of all, my original email to you was incorrect. I wrote that in
the case of administrative down, the PE should not insert FDI/AIS, but
as Dave pointed out, it should.
=20
Secondly, I still don't understand what you think is problematic in the
example that you give. There are two cases:
=20
1) The control plane is up. The local PE informs the remote PE that the
PW is to be torn down.
=20
2) The control plane is down. The local PE has to wait for the control
plane to come up before it can inform the remote PE that the PW is to be
torn down. In the mean time, the remote PE performs the consequent
actions associated with the defect condition, i.e. it inserts AIS on the
AC.
=20
What is the problem?
=20
Peter


________________________________

	From: Alexander Vainshtein
[mailto:Alexander.Vainshtein@ecitele.com]=20
	Sent: Tuesday, January 06, 2009 6:58 AM
	To: Busschbach, Peter B (Peter)
	Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor
Danilovich; Itamar Levy; Aissaoui, Mustapha (Mustapha);
dallan@nortel.com; lmartini@cisco.com; Thomas D. Nadeau;
mmorrow@cisco.com
	Subject: RE: A question regarding torn down PWs in
draft-ietf-pwe3-oam-msg-map-08.txt
=09
=09
	Peter,
	I see that I have been wrong when I've said that 4447 does not
allow differentiation between PW teardown due to defects and any other
case of the PW teardown. In fact, it does by allocating a dedicated LDP
status code 0x0000002B  - "Label Withdraw PW Status Method Not
Supported"   that must be used in the Label Release Message if the PW is
torn down due to defects. 4447 describes this as an optional method for
equipment that does not support PW Status TLV.
=09
	=20
	Regarding the example, please note that the PWs can be set up in
a single-ended manner using FEX 129. I would expect that, in this case,
the users would presumably delete them in a single-ended way as well,
initiating the teardown process at the same PE that has been used to set
it up. This explains (hopefully) why in certain situations the user
would remove the PW at one end only.=20
	=20
	If this explanation makes sense, then the problem I see with my
example is easy to understand:

	*	If the PW is torn down while the CP is OK, the remote PE
would not insert any AIS/FDI into its local AC=20
	*	If the PW is torn down while the CP is not operational
(the targeted LDP session is down), then AIS/FDI insertion (activated by
the CP failure) would persist until such time when the user deletes its
endpoint in the other PE=20
	*	The bottom line: the behavior of the PW endpoint depends
on the actual sequence of events. This does not look healthy to me.

	Hopefully this clarifies the situation.
	=20
	Regards,
	     Sasha
________________________________

	From: Busschbach, Peter B (Peter)
[mailto:busschbach@alcatel-lucent.com]=20
	Sent: Monday, January 05, 2009 6:13 PM
	To: Alexander Vainshtein
	Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor
Danilovich; Itamar Levy; Aissaoui, Mustapha (Mustapha);
dallan@nortel.com; lmartini@cisco.com; Thomas D. Nadeau;
mmorrow@cisco.com
	Subject: RE: A question regarding torn down PWs in
draft-ietf-pwe3-oam-msg-map-08.txt
=09
=09

		Sasha,
		=20
		Please see in-line


________________________________

			From: Alexander Vainshtein
[mailto:Alexander.Vainshtein@ecitele.com]=20
			Sent: Monday, January 05, 2009 10:09 AM
		=09
			[snipped]=20
		=09
		=09

			=09
				[[Sasha]] I am not aware of the case
when a PW is torn down due to defects in the data plane. Could you
please provide a reference/an example?
			=09
				=20
			=09
				[PB]  See section 5.4.1 of RFC 4447: a
simple label withdraw method MAY also be
				   supported as a legacy means of
signaling PW status and AC status
			=09
				=20
				=20
				 It would be good, however, if a PE
would be able to distinguish between PWs torn down because of defects
and PWs torn down for administrative reasons, because in the latter case
there is no need to insert an FDI message downstream.
				[[Sasha]] I do not think that RFC 4447
provides for that. In addition, please consider the following scenario:

				1.	A PW is set up=20
				2.	The PW is torn down due to the
CP defect (targeted LDP session went down). FDI is inserted in the local
AC=20
				3.	 The user has deleted the PW end
point in the remote PE. Since the LDP session is down, this fact is not
communicated to the local PE=20
				4.	Targeted LDP session is restored
but an attempt of the local PE to restore the PW fails since there is no
remote peer anymore. What should now happen to the local AC

				=20
				=20
				[PB] I don't understand the example. Who
is the user that removes the PW end point? A service provider? If so,
why would that service provider update one PE to remove the PW but not
the peer?=20
				=20
				In any case, if the local PE is
inserting FDI messages periodically on the local AC, it will continue
doing so as long as the PW is not restored. Do you believe it should
behave otherwise?
				=20
				[snipped to the end]


------_=_NextPart_001_01C97027.0F3DDC6A
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3243" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
size=3D2>Sasha,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
size=3D2>First of all, my original email to you was incorrect. I wrote =
that in the=20
case of administrative down, the PE should not insert FDI/AIS, but as =
Dave=20
pointed out, it should.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
size=3D2>Secondly, I still don't understand what you think is =
problematic in the=20
example that you give. There are two cases:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
size=3D2>1) The control plane is up. The local PE informs the remote PE =
that the=20
PW is to be torn down.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
size=3D2>2) The control plane is down. The local PE has to wait for the =
control=20
plane to come up before it can inform the remote PE that the PW is to be =
torn=20
down. In the mean time, the remote PE performs the consequent actions =
associated=20
with the defect condition, i.e. it inserts AIS on the =
AC.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
size=3D2>What is the problem?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
size=3D2>Peter</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Alexander Vainshtein=20
  [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> Tuesday, =
January=20
  06, 2009 6:58 AM<BR><B>To:</B> Busschbach, Peter B =
(Peter)<BR><B>Cc:</B>=20
  pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor Danilovich; Itamar =
Levy;=20
  Aissaoui, Mustapha (Mustapha); dallan@nortel.com; lmartini@cisco.com; =
Thomas=20
  D. Nadeau; mmorrow@cisco.com<BR><B>Subject:</B> RE: A question =
regarding torn=20
  down PWs in draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Peter,</FONT></SPAN></DIV>
  <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial><FONT =
size=3D2><FONT=20
  color=3D#0000ff>I see that I have been wrong when I've said that 4447 =
does not=20
  allow differentiation between PW teardown due to defects and any other =
case of=20
  the PW teardown. In fact, it does by allocating a dedicated LDP status =
code=20
  <STRONG>0x0000002B&nbsp; - </STRONG></FONT></FONT><FONT size=3D2><FONT =

  color=3D#0000ff><STRONG>"Label Withdraw PW Status Method Not=20
  Supported"&nbsp;</STRONG>&nbsp; that must be used in the <STRONG>Label =
Release=20
  Message</STRONG> if the PW is torn down due to defects. 4447 describes =
this as=20
  an optional method for equipment that does not support PW Status=20
  TLV.</FONT></FONT></FONT></SPAN><SPAN class=3D424163708-06012009><FONT =

  face=3DArial color=3D#0000ff size=3D2></FONT></SPAN></DIV><SPAN=20
  class=3D424163708-06012009>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Regarding the example, please note that the PWs can be set up =
in a=20
  single-ended manner using FEX 129. I would expect that, in this case, =
the=20
  users would presumably&nbsp;delete them&nbsp;in a single-ended way as =
well,=20
  initiating the teardown process at the same PE that has been used to =
set it=20
  up. This explains (hopefully) why in certain situations the user would =
remove=20
  the PW at one end only. </FONT></SPAN></DIV>
  <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff size=3D2>If=20
  this explanation makes sense, then the problem I see with my example =
is easy=20
  to understand:</FONT></SPAN></DIV>
  <UL>
    <LI><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff size=3D2>If=20
    the PW is torn down while the CP is OK, the remote PE would not =
insert any=20
    AIS/FDI into its local AC</FONT></SPAN>=20
    <LI><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff size=3D2>If=20
    the PW is torn down while the CP is not operational (the targeted =
LDP=20
    session is down), then AIS/FDI insertion (activated by the CP =
failure) would=20
    persist until such time when the user deletes its endpoint in the =
other=20
    PE</FONT></SPAN>=20
    <LI><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff size=3D2>The=20
    bottom line: the behavior of the PW endpoint depends on the actual =
sequence=20
    of events. This does not look healthy to me.</FONT></SPAN></LI></UL>
  <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Hopefully this clarifies the situation.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Regards,</FONT></SPAN></DIV>
  <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</FONT></SPAN></SPAN></DIV>
  <DIV>
  <HR tabIndex=3D-1>
  </DIV>
  <DIV><FONT face=3DTahoma size=3D2><B>From:</B> Busschbach, Peter B =
(Peter)=20
  [mailto:busschbach@alcatel-lucent.com] <BR><B>Sent:</B> Monday, =
January 05,=20
  2009 6:13 PM<BR><B>To:</B> Alexander Vainshtein<BR><B>Cc:</B> =
pwe3@ietf.org;=20
  Shell Nakash; Prashant Desai; Igor Danilovich; Itamar Levy; Aissaoui, =
Mustapha=20
  (Mustapha); dallan@nortel.com; lmartini@cisco.com; Thomas D. Nadeau;=20
  mmorrow@cisco.com<BR><B>Subject:</B> RE: A question regarding torn =
down PWs in=20
  draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D285020316-05012009><FONT =
face=3DArial=20
    size=3D2>Sasha,</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D285020316-05012009><FONT =
face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D285020316-05012009><FONT =
face=3DArial=20
    size=3D2>Please see in-line</FONT></SPAN></DIV><BR>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 =
2px solid; MARGIN-RIGHT: 0px">
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
      <HR tabIndex=3D-1>
      <FONT face=3DTahoma><FONT size=3D2><B>From:</B> Alexander =
Vainshtein=20
      [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> Monday, =
January=20
      05, 2009 10:09 AM<BR></FONT></FONT><FONT face=3DTahoma><BR><FONT=20
      size=3D2><SPAN class=3D285020316-05012009><FONT=20
      =
face=3DArial>[snipped]&nbsp;</FONT></SPAN><BR></FONT></FONT><BR></DIV>
      <BLOCKQUOTE dir=3Dltr=20
      style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff =
2px solid; MARGIN-RIGHT: 0px">
        <DIV></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D214484013-05012009><FONT face=3DArial=20
        size=3D2><BR></FONT><SPAN class=3D017510414-05012009><FONT=20
        color=3D#0000ff><FONT face=3DArial><FONT =
size=3D2><EM>[[Sasha]]&nbsp;I am not=20
        aware of the case when a PW is torn down due to defects in the =
data=20
        plane. Could you please provide a reference/an=20
        example?<BR></EM></FONT></FONT></FONT></SPAN></SPAN></DIV>
        <DIV><SPAN class=3D214484013-05012009><SPAN =
class=3D017510414-05012009><FONT=20
        color=3D#0000ff><FONT face=3DArial><FONT size=3D2><SPAN=20
        =
class=3D285020316-05012009></SPAN></FONT></FONT></FONT></SPAN></SPAN>&nbs=
p;</DIV>
        <DIV><SPAN class=3D214484013-05012009><SPAN =
class=3D017510414-05012009><FONT=20
        color=3D#0000ff><FONT face=3DArial><FONT size=3D2><SPAN=20
        class=3D285020316-05012009></SPAN><BR><SPAN =
class=3D285020316-05012009><FONT=20
        color=3D#000000>[PB]&nbsp;&nbsp;See section 5.4.1 of RFC 4447: =
<FONT=20
        size=3D3>a simple label withdraw method MAY also =
be<BR>&nbsp;&nbsp;=20
        supported as a legacy means of signaling PW status and AC=20
        =
status</FONT></FONT></SPAN><BR></DIV></FONT></FONT></FONT></SPAN></SPAN>
        <DIV><SPAN class=3D214484013-05012009><SPAN =
class=3D017510414-05012009><FONT=20
        color=3D#0000ff><FONT face=3DArial><FONT size=3D2><SPAN=20
        =
class=3D285020316-05012009></SPAN></FONT></FONT></FONT></SPAN></SPAN>&nbs=
p;</DIV>
        <DIV><SPAN class=3D214484013-05012009><SPAN =
class=3D017510414-05012009><FONT=20
        color=3D#0000ff><FONT face=3DArial><FONT size=3D2><SPAN=20
        =
class=3D285020316-05012009></SPAN></FONT></FONT></FONT></SPAN></SPAN>&nbs=
p;</DIV>
        <DIV><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT=20
        size=3D2>&nbsp;It would be good, however, if a PE would be able =
to=20
        distinguish between PWs torn down because of defects and PWs =
torn down=20
        for administrative reasons, because in the latter case there is =
no need=20
        to insert an FDI message downstream.<BR><SPAN=20
        class=3D017510414-05012009><FONT =
color=3D#0000ff><EM>[[Sasha]]&nbsp;I do not=20
        think that RFC 4447 provides for that.&nbsp;In addition, please =
consider=20
        the following =
scenario:</EM></FONT></SPAN></FONT></FONT></SPAN></DIV>
        <OL>
          <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2><SPAN=20
          class=3D017510414-05012009><FONT color=3D#0000ff><EM>A PW is =
set=20
          up</EM></FONT></SPAN></FONT></FONT></SPAN>=20
          <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2><SPAN=20
          class=3D017510414-05012009><FONT color=3D#0000ff><EM>The PW is =
torn=20
          down&nbsp;due to the CP defect (targeted LDP session went =
down). FDI=20
          is inserted in the local =
AC</EM></FONT></SPAN></FONT></FONT></SPAN>=20
          <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT =
size=3D2><SPAN=20
          class=3D017510414-05012009><EM>&nbsp;<FONT color=3D#0000ff>The =
user has=20
          deleted the PW end point in the remote PE. Since the LDP =
session is=20
          down, this fact is not communicated to the local=20
          PE</FONT></EM></SPAN></FONT></FONT></SPAN>=20
          <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT=20
          color=3D#0000ff size=3D2><SPAN =
class=3D017510414-05012009><EM>Targeted LDP=20
          session is restored but an attempt of the local PE to restore =
the PW=20
          fails since there is no remote peer anymore. <STRONG>What =
should now=20
          happen to the local=20
        AC</STRONG></EM></SPAN></FONT></FONT></SPAN></LI></OL>
        <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
        class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
        <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
        class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
        <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D214484013-05012009><SPAN=20
        class=3D285020316-05012009>[PB] I don't understand the example. =
Who is the=20
        user that removes the PW end point? A service provider? If so, =
why would=20
        that service provider update one PE to remove the PW but not the =
peer?=20
        </SPAN></SPAN></FONT></DIV>
        <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D214484013-05012009><SPAN=20
        class=3D285020316-05012009></SPAN></SPAN></FONT>&nbsp;</DIV>
        <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D214484013-05012009><SPAN=20
        class=3D285020316-05012009>In any case, if the local PE is =
inserting FDI=20
        messages periodically on the local AC, it will continue doing so =
as long=20
        as the PW is not restored. Do you believe it should behave=20
        otherwise?</SPAN></SPAN></FONT></DIV>
        <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D214484013-05012009><SPAN=20
        class=3D285020316-05012009></SPAN></SPAN></FONT>&nbsp;</DIV>
        <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D214484013-05012009><SPAN=20
        class=3D285020316-05012009>[snipped to the=20
      =
end]</SPAN></SPAN></FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></B=
LOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C97027.0F3DDC6A--

--===============1761535511==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1761535511==--


From pwe3-bounces@ietf.org  Tue Jan  6 11:56:29 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ED5BA3A6900;
	Tue,  6 Jan 2009 11:56:28 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6F9BB3A6900
	for <pwe3@core3.amsl.com>; Tue,  6 Jan 2009 11:56:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.532
X-Spam-Level: 
X-Spam-Status: No, score=-2.532 tagged_above=-999 required=5 tests=[AWL=0.066, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 ertQ-SjkwnfM for <pwe3@core3.amsl.com>;
	Tue,  6 Jan 2009 11:56:26 -0800 (PST)
Received: from eci-iron1.ecitele.com (eci-iron1.ecitele.com [147.234.242.117])
	by core3.amsl.com (Postfix) with ESMTP id 835833A6817
	for <pwe3@ietf.org>; Tue,  6 Jan 2009 11:56:25 -0800 (PST)
Received: from unknown (HELO ILPTAM01.ecitele.com) ([147.234.244.44])
	by eci-iron1.ecitele.com with ESMTP; 06 Jan 2009 22:20:10 +0200
Received: from ILPTEXCH02.ecitele.com ([147.234.245.181]) by
	ILPTAM01.ecitele.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 6 Jan 2009 21:56:11 +0200
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by
	ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Tue, 6 Jan 2009
	21:56:10 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "Busschbach, Peter B (Peter)" <busschbach@alcatel-lucent.com>
Date: Tue, 6 Jan 2009 21:55:44 +0200
Thread-Topic: A question regarding torn down PWs in
	draft-ietf-pwe3-oam-msg-map-08.txt
Thread-Index: AclvHgFatl4xVjfUTBai2RqcqunEfwAHTX0AAADXDMAABCCuAAAiuSoAABL/3kAAATGQEA==
Message-ID: <A3C5DF08D38B6049839A6F553B331C7698C34E400A@ILPTMAIL02.ecitele.com>
References: <A3C5DF08D38B6049839A6F553B331C7698C2C6CCC1@ILPTMAIL02.ecitele.com>
	<E60778C3916D3548BBCF4D964186348F022953BD@ILEXC2U01.ndc.lucent.com>
	<A3C5DF08D38B6049839A6F553B331C7698C2C6CDE7@ILPTMAIL02.ecitele.com>
	<E60778C3916D3548BBCF4D964186348F022954DD@ILEXC2U01.ndc.lucent.com>
	<A3C5DF08D38B6049839A6F553B331C7698C34E3EE3@ILPTMAIL02.ecitele.com>
	<E60778C3916D3548BBCF4D964186348F022EF11B@ILEXC2U01.ndc.lucent.com>
In-Reply-To: <E60778C3916D3548BBCF4D964186348F022EF11B@ILEXC2U01.ndc.lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-OriginalArrivalTime: 06 Jan 2009 19:56:11.0113 (UTC)
	FILETIME=[D2A2BD90:01C97038]
Cc: Shell Nakash <Shell.Nakash@ecitele.com>,
	"lmartini@cisco.com" <lmartini@cisco.com>,
	"mmorrow@cisco.com" <mmorrow@cisco.com>,
	Igor Danilovich <Igor.Danilovich@ecitele.com>,
	"pwe3@ietf.org" <pwe3@ietf.org>, "Aissaoui,
	Mustapha \(Mustapha\)" <mustapha.aissaoui@alcatel-lucent.com>,
	Itamar Levy <Itamar.Levy@ecitele.com>
Subject: Re: [PWE3] A question regarding torn down PWs in
 draft-ietf-pwe3-oam-msg-map-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1951976736=="
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

--===============1951976736==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_A3C5DF08D38B6049839A6F553B331C7698C34E400AILPTMAIL02eci_"

--_000_A3C5DF08D38B6049839A6F553B331C7698C34E400AILPTMAIL02eci_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Peter,
I do not think we have a standard method to indicate to the peer PE that th=
e PW is administratively down.
The only more or less suitable statement I've found in 4477 says:
<quote>
The PW label should not be withdrawn unless the operator administratively c=
onfigures the pseudowire down (or the PW configuration is deleted entirely)=
.
<end quote>,

This statement seems to indicate that if a PW is administratively disabled,=
 PW labels must be withdrawn (released?). But there are no dedicated error =
codes that could be used in the Label Release/Label Withdraw messages  and =
no PW status bits either. (Mustapha's comment on the use of the "PW not for=
warding" code point seems to support my opinion).

Regarding the example: what you say means that the PE that has been used to=
 set up the PW and where the PW end point has been deleted while CP was dow=
n must remember an already non-existing PW end point and update the peer ab=
out its deletion when this becomes possible. I do not think that this kind =
of behavior is defined anywhere, but maybe I've missed something?

Regards,
     Sasha

________________________________
From: Busschbach, Peter B (Peter) [mailto:busschbach@alcatel-lucent.com]
Sent: Tuesday, January 06, 2009 7:49 PM
To: Alexander Vainshtein
Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor Danilovich; Itamar Le=
vy; Aissaoui, Mustapha (Mustapha); dallan@nortel.com; lmartini@cisco.com; T=
homas D. Nadeau; mmorrow@cisco.com
Subject: RE: A question regarding torn down PWs in draft-ietf-pwe3-oam-msg-=
map-08.txt

Sasha,

First of all, my original email to you was incorrect. I wrote that in the c=
ase of administrative down, the PE should not insert FDI/AIS, but as Dave p=
ointed out, it should.

Secondly, I still don't understand what you think is problematic in the exa=
mple that you give. There are two cases:

1) The control plane is up. The local PE informs the remote PE that the PW =
is to be torn down.

2) The control plane is down. The local PE has to wait for the control plan=
e to come up before it can inform the remote PE that the PW is to be torn d=
own. In the mean time, the remote PE performs the consequent actions associ=
ated with the defect condition, i.e. it inserts AIS on the AC.

What is the problem?

Peter

________________________________
From: Alexander Vainshtein [mailto:Alexander.Vainshtein@ecitele.com]
Sent: Tuesday, January 06, 2009 6:58 AM
To: Busschbach, Peter B (Peter)
Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor Danilovich; Itamar Le=
vy; Aissaoui, Mustapha (Mustapha); dallan@nortel.com; lmartini@cisco.com; T=
homas D. Nadeau; mmorrow@cisco.com
Subject: RE: A question regarding torn down PWs in draft-ietf-pwe3-oam-msg-=
map-08.txt

Peter,
I see that I have been wrong when I've said that 4447 does not allow differ=
entiation between PW teardown due to defects and any other case of the PW t=
eardown. In fact, it does by allocating a dedicated LDP status code 0x00000=
02B  - "Label Withdraw PW Status Method Not Supported"   that must be used =
in the Label Release Message if the PW is torn down due to defects. 4447 de=
scribes this as an optional method for equipment that does not support PW S=
tatus TLV.

Regarding the example, please note that the PWs can be set up in a single-e=
nded manner using FEX 129. I would expect that, in this case, the users wou=
ld presumably delete them in a single-ended way as well, initiating the tea=
rdown process at the same PE that has been used to set it up. This explains=
 (hopefully) why in certain situations the user would remove the PW at one =
end only.

If this explanation makes sense, then the problem I see with my example is =
easy to understand:

 *   If the PW is torn down while the CP is OK, the remote PE would not ins=
ert any AIS/FDI into its local AC
 *   If the PW is torn down while the CP is not operational (the targeted L=
DP session is down), then AIS/FDI insertion (activated by the CP failure) w=
ould persist until such time when the user deletes its endpoint in the othe=
r PE
 *   The bottom line: the behavior of the PW endpoint depends on the actual=
 sequence of events. This does not look healthy to me.

Hopefully this clarifies the situation.

Regards,
     Sasha
________________________________
From: Busschbach, Peter B (Peter) [mailto:busschbach@alcatel-lucent.com]
Sent: Monday, January 05, 2009 6:13 PM
To: Alexander Vainshtein
Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor Danilovich; Itamar Le=
vy; Aissaoui, Mustapha (Mustapha); dallan@nortel.com; lmartini@cisco.com; T=
homas D. Nadeau; mmorrow@cisco.com
Subject: RE: A question regarding torn down PWs in draft-ietf-pwe3-oam-msg-=
map-08.txt

Sasha,

Please see in-line

________________________________
From: Alexander Vainshtein [mailto:Alexander.Vainshtein@ecitele.com]
Sent: Monday, January 05, 2009 10:09 AM

[snipped]


[[Sasha]] I am not aware of the case when a PW is torn down due to defects =
in the data plane. Could you please provide a reference/an example?


[PB]  See section 5.4.1 of RFC 4447: a simple label withdraw method MAY als=
o be
   supported as a legacy means of signaling PW status and AC status


 It would be good, however, if a PE would be able to distinguish between PW=
s torn down because of defects and PWs torn down for administrative reasons=
, because in the latter case there is no need to insert an FDI message down=
stream.
[[Sasha]] I do not think that RFC 4447 provides for that. In addition, plea=
se consider the following scenario:

 1.  A PW is set up
 2.  The PW is torn down due to the CP defect (targeted LDP session went do=
wn). FDI is inserted in the local AC
 3.   The user has deleted the PW end point in the remote PE. Since the LDP=
 session is down, this fact is not communicated to the local PE
 4.  Targeted LDP session is restored but an attempt of the local PE to res=
tore the PW fails since there is no remote peer anymore. What should now ha=
ppen to the local AC



[PB] I don't understand the example. Who is the user that removes the PW en=
d point? A service provider? If so, why would that service provider update =
one PE to remove the PW but not the peer?

In any case, if the local PE is inserting FDI messages periodically on the =
local AC, it will continue doing so as long as the PW is not restored. Do y=
ou believe it should behave otherwise?

[snipped to the end]

--_000_A3C5DF08D38B6049839A6F553B331C7698C34E400AILPTMAIL02eci_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3492" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D953271518-06012009><FONT face=3DArial color=3D#0000ff=20
size=3D2>Peter,</FONT></SPAN></DIV>
<DIV><SPAN class=3D953271518-06012009><FONT face=3DArial color=3D#0000ff si=
ze=3D2>I do=20
not think we have a standard method to indicate to the peer PE that the PW =
is=20
administratively down.</FONT></SPAN></DIV>
<DIV><SPAN class=3D953271518-06012009><FONT face=3DArial color=3D#0000ff si=
ze=3D2>The=20
only more or less suitable&nbsp;statement I've found in 4477=20
says:</FONT></SPAN></DIV>
<DIV><SPAN class=3D953271518-06012009><FONT face=3DArial color=3D#0000ff=20
size=3D2>&lt;quote&gt;</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV><SPAN class=3D953271518-06012009><EM>The PW label should not be=20
  withdrawn&nbsp;unless the operator administratively configures the pseudo=
wire=20
  down&nbsp;(or the PW configuration is deleted=20
entirely).</EM></SPAN></DIV></BLOCKQUOTE>
<DIV><SPAN class=3D953271518-06012009><FONT face=3DArial color=3D#0000ff=20
size=3D2>&lt;end quote&gt;,</FONT></SPAN></DIV>
<DIV><SPAN class=3D953271518-06012009><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D953271518-06012009><FONT face=3DArial color=3D#0000ff si=
ze=3D2>This=20
statement&nbsp;seems to indicate that if a PW is administratively disabled,=
 PW=20
labels must be withdrawn (released?). But there are no dedicated error code=
s=20
that could be used in the Label Release/Label Withdraw messages&nbsp; and n=
o PW=20
status bits either. (</FONT></SPAN><SPAN class=3D953271518-06012009><FONT=20
face=3DArial color=3D#0000ff size=3D2>Mustapha's comment on the use of the =
"PW not=20
forwarding" code point seems to support my opinion). </FONT></SPAN></DIV>
<DIV><SPAN class=3D953271518-06012009><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D953271518-06012009><FONT face=3DArial color=3D#0000ff=20
size=3D2>Regarding the example: what you say means that the PE that has bee=
n used=20
to set up the PW and where the PW end point has been deleted while CP was d=
own=20
must <EM>remember an already non-existing PW end point</EM> and update the =
peer=20
about its deletion when this becomes possible. I do not think that this kin=
d of=20
behavior is defined anywhere, but maybe I've missed=20
something?</FONT></SPAN></DIV>
<DIV><SPAN class=3D953271518-06012009><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D953271518-06012009><FONT face=3DArial color=3D#0000ff=20
size=3D2>Regards,</FONT></SPAN></DIV>
<DIV><SPAN class=3D953271518-06012009><FONT face=3DArial color=3D#0000ff=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Busschbach, Peter B (Peter)=20
  [mailto:busschbach@alcatel-lucent.com] <BR><B>Sent:</B> Tuesday, January =
06,=20
  2009 7:49 PM<BR><B>To:</B> Alexander Vainshtein<BR><B>Cc:</B> pwe3@ietf.o=
rg;=20
  Shell Nakash; Prashant Desai; Igor Danilovich; Itamar Levy; Aissaoui, Mus=
tapha=20
  (Mustapha); dallan@nortel.com; lmartini@cisco.com; Thomas D. Nadeau;=20
  mmorrow@cisco.com<BR><B>Subject:</B> RE: A question regarding torn down P=
Ws in=20
  draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT face=
=3DArial=20
  size=3D2>Sasha,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT face=
=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT face=
=3DArial=20
  size=3D2>First of all, my original email to you was incorrect. I wrote th=
at in=20
  the case of administrative down, the PE should not insert FDI/AIS, but as=
 Dave=20
  pointed out, it should.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT face=
=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT face=
=3DArial=20
  size=3D2>Secondly, I still don't understand what you think is problematic=
 in the=20
  example that you give. There are two cases:</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT face=
=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT face=
=3DArial=20
  size=3D2>1) The control plane is up. The local PE informs the remote PE t=
hat the=20
  PW is to be torn down.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT face=
=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT face=
=3DArial=20
  size=3D2>2) The control plane is down. The local PE has to wait for the c=
ontrol=20
  plane to come up before it can inform the remote PE that the PW is to be =
torn=20
  down. In the mean time, the remote PE performs the consequent actions=20
  associated with the defect condition, i.e. it inserts AIS on the=20
  AC.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT face=
=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT face=
=3DArial=20
  size=3D2>What is the problem?</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT face=
=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT face=
=3DArial=20
  size=3D2>Peter</FONT></SPAN></DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px so=
lid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> Alexander Vainshtein=20
    [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> Tuesday, Jan=
uary=20
    06, 2009 6:58 AM<BR><B>To:</B> Busschbach, Peter B (Peter)<BR><B>Cc:</B=
>=20
    pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor Danilovich; Itamar Le=
vy;=20
    Aissaoui, Mustapha (Mustapha); dallan@nortel.com; lmartini@cisco.com; T=
homas=20
    D. Nadeau; mmorrow@cisco.com<BR><B>Subject:</B> RE: A question regardin=
g=20
    torn down PWs in draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV=
>
    <DIV></DIV>
    <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000f=
f=20
    size=3D2>Peter,</FONT></SPAN></DIV>
    <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial><FONT size=3D2=
><FONT=20
    color=3D#0000ff>I see that I have been wrong when I've said that 4447 d=
oes not=20
    allow differentiation between PW teardown due to defects and any other =
case=20
    of the PW teardown. In fact, it does by allocating a dedicated LDP stat=
us=20
    code <STRONG>0x0000002B&nbsp; - </STRONG></FONT></FONT><FONT size=3D2><=
FONT=20
    color=3D#0000ff><STRONG>"Label Withdraw PW Status Method Not=20
    Supported"&nbsp;</STRONG>&nbsp; that must be used in the <STRONG>Label=
=20
    Release Message</STRONG> if the PW is torn down due to defects. 4447=20
    describes this as an optional method for equipment that does not suppor=
t PW=20
    Status TLV.</FONT></FONT></FONT></SPAN><SPAN class=3D424163708-06012009=
><FONT=20
    face=3DArial color=3D#0000ff size=3D2></FONT></SPAN></DIV><SPAN=20
    class=3D424163708-06012009>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
    <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000f=
f=20
    size=3D2>Regarding the example, please note that the PWs can be set up =
in a=20
    single-ended manner using FEX 129. I would expect that, in this case, t=
he=20
    users would presumably&nbsp;delete them&nbsp;in a single-ended way as w=
ell,=20
    initiating the teardown process at the same PE that has been used to se=
t it=20
    up. This explains (hopefully) why in certain situations the user would=
=20
    remove the PW at one end only. </FONT></SPAN></DIV>
    <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000f=
f=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000f=
f size=3D2>If=20
    this explanation makes sense, then the problem I see with my example is=
 easy=20
    to understand:</FONT></SPAN></DIV>
    <UL>
      <LI><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000=
ff=20
      size=3D2>If the PW is torn down while the CP is OK, the remote PE wou=
ld not=20
      insert any AIS/FDI into its local AC</FONT></SPAN>=20
      <LI><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000=
ff=20
      size=3D2>If the PW is torn down while the CP is not operational (the=
=20
      targeted LDP session is down), then AIS/FDI insertion (activated by t=
he CP=20
      failure) would persist until such time when the user deletes its endp=
oint=20
      in the other PE</FONT></SPAN>=20
      <LI><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000=
ff=20
      size=3D2>The bottom line: the behavior of the PW endpoint depends on =
the=20
      actual sequence of events. This does not look healthy to=20
      me.</FONT></SPAN></LI></UL>
    <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000f=
f=20
    size=3D2>Hopefully this clarifies the situation.</FONT></SPAN></DIV>
    <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000f=
f=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000f=
f=20
    size=3D2>Regards,</FONT></SPAN></DIV>
    <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial color=3D#0000f=
f=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</FONT></SPAN></SPAN></DIV>
    <DIV>
    <HR tabIndex=3D-1>
    </DIV>
    <DIV><FONT face=3DTahoma size=3D2><B>From:</B> Busschbach, Peter B (Pet=
er)=20
    [mailto:busschbach@alcatel-lucent.com] <BR><B>Sent:</B> Monday, January=
 05,=20
    2009 6:13 PM<BR><B>To:</B> Alexander Vainshtein<BR><B>Cc:</B> pwe3@ietf=
.org;=20
    Shell Nakash; Prashant Desai; Igor Danilovich; Itamar Levy; Aissaoui,=20
    Mustapha (Mustapha); dallan@nortel.com; lmartini@cisco.com; Thomas D.=20
    Nadeau; mmorrow@cisco.com<BR><B>Subject:</B> RE: A question regarding t=
orn=20
    down PWs in draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
      <DIV></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D285020316-05012009><FONT fa=
ce=3DArial=20
      size=3D2>Sasha,</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D285020316-05012009><FONT fa=
ce=3DArial=20
      size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D285020316-05012009><FONT fa=
ce=3DArial=20
      size=3D2>Please see in-line</FONT></SPAN></DIV><BR>
      <BLOCKQUOTE dir=3Dltr=20
      style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2p=
x solid; MARGIN-RIGHT: 0px">
        <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dle=
ft>
        <HR tabIndex=3D-1>
        <FONT face=3DTahoma><FONT size=3D2><B>From:</B> Alexander Vainshtei=
n=20
        [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> Monday,=
=20
        January 05, 2009 10:09 AM<BR></FONT></FONT><FONT face=3DTahoma><BR>=
<FONT=20
        size=3D2><SPAN class=3D285020316-05012009><FONT=20
        face=3DArial>[snipped]&nbsp;</FONT></SPAN><BR></FONT></FONT><BR></D=
IV>
        <BLOCKQUOTE dir=3Dltr=20
        style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff =
2px solid; MARGIN-RIGHT: 0px">
          <DIV></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN class=3D214484013-05012009><FON=
T=20
          face=3DArial size=3D2><BR></FONT><SPAN class=3D017510414-05012009=
><FONT=20
          color=3D#0000ff><FONT face=3DArial><FONT size=3D2><EM>[[Sasha]]&n=
bsp;I am=20
          not aware of the case when a PW is torn down due to defects in th=
e=20
          data plane. Could you please provide a reference/an=20
          example?<BR></EM></FONT></FONT></FONT></SPAN></SPAN></DIV>
          <DIV><SPAN class=3D214484013-05012009><SPAN=20
          class=3D017510414-05012009><FONT color=3D#0000ff><FONT face=3DAri=
al><FONT=20
          size=3D2><SPAN=20
          class=3D285020316-05012009></SPAN></FONT></FONT></FONT></SPAN></S=
PAN>&nbsp;</DIV>
          <DIV><SPAN class=3D214484013-05012009><SPAN=20
          class=3D017510414-05012009><FONT color=3D#0000ff><FONT face=3DAri=
al><FONT=20
          size=3D2><SPAN class=3D285020316-05012009></SPAN><BR><SPAN=20
          class=3D285020316-05012009><FONT color=3D#000000>[PB]&nbsp;&nbsp;=
See=20
          section 5.4.1 of RFC 4447: <FONT size=3D3>a simple label withdraw=
 method=20
          MAY also be<BR>&nbsp;&nbsp; supported as a legacy means of signal=
ing=20
          PW status and AC=20
          status</FONT></FONT></SPAN><BR></DIV></FONT></FONT></FONT></SPAN>=
</SPAN>
          <DIV><SPAN class=3D214484013-05012009><SPAN=20
          class=3D017510414-05012009><FONT color=3D#0000ff><FONT face=3DAri=
al><FONT=20
          size=3D2><SPAN=20
          class=3D285020316-05012009></SPAN></FONT></FONT></FONT></SPAN></S=
PAN>&nbsp;</DIV>
          <DIV><SPAN class=3D214484013-05012009><SPAN=20
          class=3D017510414-05012009><FONT color=3D#0000ff><FONT face=3DAri=
al><FONT=20
          size=3D2><SPAN=20
          class=3D285020316-05012009></SPAN></FONT></FONT></FONT></SPAN></S=
PAN>&nbsp;</DIV>
          <DIV><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT=20
          size=3D2>&nbsp;It would be good, however, if a PE would be able t=
o=20
          distinguish between PWs torn down because of defects and PWs torn=
 down=20
          for administrative reasons, because in the latter case there is n=
o=20
          need to insert an FDI message downstream.<BR><SPAN=20
          class=3D017510414-05012009><FONT color=3D#0000ff><EM>[[Sasha]]&nb=
sp;I do=20
          not think that RFC 4447 provides for that.&nbsp;In addition, plea=
se=20
          consider the following=20
          scenario:</EM></FONT></SPAN></FONT></FONT></SPAN></DIV>
          <OL>
            <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT=20
            size=3D2><SPAN class=3D017510414-05012009><FONT color=3D#0000ff=
><EM>A PW=20
            is set up</EM></FONT></SPAN></FONT></FONT></SPAN>=20
            <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT=20
            size=3D2><SPAN class=3D017510414-05012009><FONT color=3D#0000ff=
><EM>The PW=20
            is torn down&nbsp;due to the CP defect (targeted LDP session we=
nt=20
            down). FDI is inserted in the local=20
            AC</EM></FONT></SPAN></FONT></FONT></SPAN>=20
            <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT=20
            size=3D2><SPAN class=3D017510414-05012009><EM>&nbsp;<FONT=20
            color=3D#0000ff>The user has deleted the PW end point in the re=
mote=20
            PE. Since the LDP session is down, this fact is not communicate=
d to=20
            the local PE</FONT></EM></SPAN></FONT></FONT></SPAN>=20
            <LI><SPAN class=3D214484013-05012009><FONT face=3DArial><FONT=20
            color=3D#0000ff size=3D2><SPAN class=3D017510414-05012009><EM>T=
argeted LDP=20
            session is restored but an attempt of the local PE to restore t=
he PW=20
            fails since there is no remote peer anymore. <STRONG>What shoul=
d now=20
            happen to the local=20
          AC</STRONG></EM></SPAN></FONT></FONT></SPAN></LI></OL>
          <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
          class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
          <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
          class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
          <DIV><FONT face=3DArial size=3D2><SPAN class=3D214484013-05012009=
><SPAN=20
          class=3D285020316-05012009>[PB] I don't understand the example. W=
ho is=20
          the user that removes the PW end point? A service provider? If so=
, why=20
          would that service provider update one PE to remove the PW but no=
t the=20
          peer? </SPAN></SPAN></FONT></DIV>
          <DIV><FONT face=3DArial size=3D2><SPAN class=3D214484013-05012009=
><SPAN=20
          class=3D285020316-05012009></SPAN></SPAN></FONT>&nbsp;</DIV>
          <DIV><FONT face=3DArial size=3D2><SPAN class=3D214484013-05012009=
><SPAN=20
          class=3D285020316-05012009>In any case, if the local PE is insert=
ing FDI=20
          messages periodically on the local AC, it will continue doing so =
as=20
          long as the PW is not restored. Do you believe it should behave=20
          otherwise?</SPAN></SPAN></FONT></DIV>
          <DIV><FONT face=3DArial size=3D2><SPAN class=3D214484013-05012009=
><SPAN=20
          class=3D285020316-05012009></SPAN></SPAN></FONT>&nbsp;</DIV>
          <DIV><FONT face=3DArial size=3D2><SPAN class=3D214484013-05012009=
><SPAN=20
          class=3D285020316-05012009>[snipped to the=20
          end]</SPAN></SPAN></FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQ=
UOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

--_000_A3C5DF08D38B6049839A6F553B331C7698C34E400AILPTMAIL02eci_--

--===============1951976736==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1951976736==--


From pwe3-bounces@ietf.org  Tue Jan  6 13:03:43 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D01873A692F;
	Tue,  6 Jan 2009 13:03:43 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CBB0C3A6893
	for <pwe3@core3.amsl.com>; Tue,  6 Jan 2009 13:03:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 61ivSxaNnctn for <pwe3@core3.amsl.com>;
	Tue,  6 Jan 2009 13:03:41 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39])
	by core3.amsl.com (Postfix) with ESMTP id D89703A6452
	for <pwe3@ietf.org>; Tue,  6 Jan 2009 13:03:40 -0800 (PST)
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1])
	by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id n06L1cqR005525;
	Tue, 6 Jan 2009 15:03:08 -0600 (CST)
Received: from ILEXC2U01.ndc.lucent.com ([135.3.39.9]) by
	ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 Jan 2009 15:02:06 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 6 Jan 2009 15:02:04 -0600
Message-ID: <E60778C3916D3548BBCF4D964186348F022EF24F@ILEXC2U01.ndc.lucent.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C7698C34E400A@ILPTMAIL02.ecitele.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: A question regarding torn down PWs in
	draft-ietf-pwe3-oam-msg-map-08.txt
Thread-Index: AclvHgFatl4xVjfUTBai2RqcqunEfwAHTX0AAADXDMAABCCuAAAiuSoAABL/3kAAATGQEAAFiCuQ
References: <A3C5DF08D38B6049839A6F553B331C7698C2C6CCC1@ILPTMAIL02.ecitele.com>
	<E60778C3916D3548BBCF4D964186348F022953BD@ILEXC2U01.ndc.lucent.com>
	<A3C5DF08D38B6049839A6F553B331C7698C2C6CDE7@ILPTMAIL02.ecitele.com>
	<E60778C3916D3548BBCF4D964186348F022954DD@ILEXC2U01.ndc.lucent.com>
	<A3C5DF08D38B6049839A6F553B331C7698C34E3EE3@ILPTMAIL02.ecitele.com>
	<E60778C3916D3548BBCF4D964186348F022EF11B@ILEXC2U01.ndc.lucent.com>
	<A3C5DF08D38B6049839A6F553B331C7698C34E400A@ILPTMAIL02.ecitele.com>
From: "Busschbach, Peter B \(Peter\)" <busschbach@alcatel-lucent.com>
To: "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>
X-OriginalArrivalTime: 06 Jan 2009 21:02:06.0997 (UTC)
	FILETIME=[0886BC50:01C97042]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: Shell Nakash <Shell.Nakash@ecitele.com>, lmartini@cisco.com,
	mmorrow@cisco.com, Igor Danilovich <Igor.Danilovich@ecitele.com>,
	pwe3@ietf.org, "Aissaoui,
	Mustapha \(Mustapha\)" <mustapha.aissaoui@alcatel-lucent.com>,
	Itamar Levy <Itamar.Levy@ecitele.com>
Subject: Re: [PWE3] A question regarding torn down PWs in
	draft-ietf-pwe3-oam-msg-map-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1379617516=="
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1379617516==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C97042.07F9E18E"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C97042.07F9E18E
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

>> the PE that has been used to set up the PW and where the PW end point
has been deleted while CP
>> was down must remember an already non-existing PW end point and
update the peer about its deletion
>> when this becomes possible
=20
Sasha,
=20
I don't see how a PE can delete a PW without sending a Label Withdraw or
Label Release message to its peer. If the control plane is down and this
message cannot be sent, the PW cannot be deleted. Therefore, IMO there
is no such thing as a non-existent PW that must be remembered.=20
=20
Is your understanding of the PW release procedure different?
=20
Peter


________________________________

	From: Alexander Vainshtein
[mailto:Alexander.Vainshtein@ecitele.com]=20
	Sent: Tuesday, January 06, 2009 2:56 PM
	To: Busschbach, Peter B (Peter)
	Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor
Danilovich; Itamar Levy; Aissaoui, Mustapha (Mustapha);
dallan@nortel.com; lmartini@cisco.com; Thomas D. Nadeau;
mmorrow@cisco.com
	Subject: RE: A question regarding torn down PWs in
draft-ietf-pwe3-oam-msg-map-08.txt
=09
=09
	Peter,
	I do not think we have a standard method to indicate to the peer
PE that the PW is administratively down.
	The only more or less suitable statement I've found in 4477
says:
	<quote>

		The PW label should not be withdrawn unless the operator
administratively configures the pseudowire down (or the PW configuration
is deleted entirely).

	<end quote>,
	=20
	This statement seems to indicate that if a PW is
administratively disabled, PW labels must be withdrawn (released?). But
there are no dedicated error codes that could be used in the Label
Release/Label Withdraw messages  and no PW status bits either.
(Mustapha's comment on the use of the "PW not forwarding" code point
seems to support my opinion).=20
	=20
	Regarding the example: what you say means that the PE that has
been used to set up the PW and where the PW end point has been deleted
while CP was down must remember an already non-existing PW end point and
update the peer about its deletion when this becomes possible. I do not
think that this kind of behavior is defined anywhere, but maybe I've
missed something?
	=20
	Regards,
	     Sasha


________________________________

		From: Busschbach, Peter B (Peter)
[mailto:busschbach@alcatel-lucent.com]=20
		Sent: Tuesday, January 06, 2009 7:49 PM
		To: Alexander Vainshtein
		Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor
Danilovich; Itamar Levy; Aissaoui, Mustapha (Mustapha);
dallan@nortel.com; lmartini@cisco.com; Thomas D. Nadeau;
mmorrow@cisco.com
		Subject: RE: A question regarding torn down PWs in
draft-ietf-pwe3-oam-msg-map-08.txt
	=09
	=09
		Sasha,
		=20
		First of all, my original email to you was incorrect. I
wrote that in the case of administrative down, the PE should not insert
FDI/AIS, but as Dave pointed out, it should.
		=20
		Secondly, I still don't understand what you think is
problematic in the example that you give. There are two cases:
		=20
		1) The control plane is up. The local PE informs the
remote PE that the PW is to be torn down.
		=20
		2) The control plane is down. The local PE has to wait
for the control plane to come up before it can inform the remote PE that
the PW is to be torn down. In the mean time, the remote PE performs the
consequent actions associated with the defect condition, i.e. it inserts
AIS on the AC.
		=20
		What is the problem?
		=20
		Peter


________________________________

			From: Alexander Vainshtein
[mailto:Alexander.Vainshtein@ecitele.com]=20
			Sent: Tuesday, January 06, 2009 6:58 AM
			To: Busschbach, Peter B (Peter)
			Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai;
Igor Danilovich; Itamar Levy; Aissaoui, Mustapha (Mustapha);
dallan@nortel.com; lmartini@cisco.com; Thomas D. Nadeau;
mmorrow@cisco.com
			Subject: RE: A question regarding torn down PWs
in draft-ietf-pwe3-oam-msg-map-08.txt
		=09
		=09
			Peter,
			I see that I have been wrong when I've said that
4447 does not allow differentiation between PW teardown due to defects
and any other case of the PW teardown. In fact, it does by allocating a
dedicated LDP status code 0x0000002B  - "Label Withdraw PW Status Method
Not Supported"   that must be used in the Label Release Message if the
PW is torn down due to defects. 4447 describes this as an optional
method for equipment that does not support PW Status TLV.
		=09
			=20
			Regarding the example, please note that the PWs
can be set up in a single-ended manner using FEX 129. I would expect
that, in this case, the users would presumably delete them in a
single-ended way as well, initiating the teardown process at the same PE
that has been used to set it up. This explains (hopefully) why in
certain situations the user would remove the PW at one end only.=20
			=20
			If this explanation makes sense, then the
problem I see with my example is easy to understand:

			*	If the PW is torn down while the CP is
OK, the remote PE would not insert any AIS/FDI into its local AC=20
			*	If the PW is torn down while the CP is
not operational (the targeted LDP session is down), then AIS/FDI
insertion (activated by the CP failure) would persist until such time
when the user deletes its endpoint in the other PE=20
			*	The bottom line: the behavior of the PW
endpoint depends on the actual sequence of events. This does not look
healthy to me.

			Hopefully this clarifies the situation.
			=20
			Regards,
			     Sasha
________________________________

			From: Busschbach, Peter B (Peter)
[mailto:busschbach@alcatel-lucent.com]=20
			Sent: Monday, January 05, 2009 6:13 PM
			To: Alexander Vainshtein
			Cc: pwe3@ietf.org; Shell Nakash; Prashant Desai;
Igor Danilovich; Itamar Levy; Aissaoui, Mustapha (Mustapha);
dallan@nortel.com; lmartini@cisco.com; Thomas D. Nadeau;
mmorrow@cisco.com
			Subject: RE: A question regarding torn down PWs
in draft-ietf-pwe3-oam-msg-map-08.txt
		=09
		=09

				Sasha,
				=20
				Please see in-line


________________________________

				From: Alexander Vainshtein
[mailto:Alexander.Vainshtein@ecitele.com]=20
				Sent: Monday, January 05, 2009 10:09 AM
			=09
				[snipped]=20
			=09
			=09

			=09
				[[Sasha]] I am not aware of the case
when a PW is torn down due to defects in the data plane. Could you
please provide a reference/an example?
			=09
				=20
			=09
				[PB]  See section 5.4.1 of RFC 4447: a
simple label withdraw method MAY also be
				   supported as a legacy means of
signaling PW status and AC status
			=09
				=20
				=20
				 It would be good, however, if a PE
would be able to distinguish between PWs torn down because of defects
and PWs torn down for administrative reasons, because in the latter case
there is no need to insert an FDI message downstream.
				[[Sasha]] I do not think that RFC 4447
provides for that. In addition, please consider the following scenario:

				1.	A PW is set up=20
				2.	The PW is torn down due to the
CP defect (targeted LDP session went down). FDI is inserted in the local
AC=20
				3.	 The user has deleted the PW end
point in the remote PE. Since the LDP session is down, this fact is not
communicated to the local PE=20
				4.	Targeted LDP session is restored
but an attempt of the local PE to restore the PW fails since there is no
remote peer anymore. What should now happen to the local AC

				=20
				=20
				[PB] I don't understand the example. Who
is the user that removes the PW end point? A service provider? If so,
why would that service provider update one PE to remove the PW but not
the peer?=20
				=20
				In any case, if the local PE is
inserting FDI messages periodically on the local AC, it will continue
doing so as long as the PW is not restored. Do you believe it should
behave otherwise?
				=20
				[snipped to the end]


------_=_NextPart_001_01C97042.07F9E18E
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3243" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D840515320-06012009>&gt;&gt; <FONT color=3D#0000ff>the PE that =
has been used=20
to set up the PW and where the PW end point has been deleted while=20
CP</FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D840515320-06012009><FONT color=3D#0000ff>&gt;&gt; was down must =
<EM>remember=20
an already non-existing PW end point</EM> and update the peer about its=20
deletion</FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D840515320-06012009><FONT color=3D#0000ff>&gt;&gt; when this =
becomes=20
possible</FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D840515320-06012009></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D840515320-06012009>Sasha,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D840515320-06012009></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D840515320-06012009>I don't see how a PE can delete a PW without =
sending a=20
Label Withdraw or Label Release&nbsp;message to its peer. If the control =
plane=20
is down and this message cannot be sent, the PW cannot be deleted. =
Therefore,=20
IMO there is no such thing as a non-existent PW that must be remembered. =

</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D840515320-06012009></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D840515320-06012009>Is your understanding of the PW release =
procedure=20
different?</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D840515320-06012009></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D840515320-06012009>Peter</SPAN></FONT></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Alexander Vainshtein=20
  [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> Tuesday, =
January=20
  06, 2009 2:56 PM<BR><B>To:</B> Busschbach, Peter B =
(Peter)<BR><B>Cc:</B>=20
  pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor Danilovich; Itamar =
Levy;=20
  Aissaoui, Mustapha (Mustapha); dallan@nortel.com; lmartini@cisco.com; =
Thomas=20
  D. Nadeau; mmorrow@cisco.com<BR><B>Subject:</B> RE: A question =
regarding torn=20
  down PWs in draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><SPAN class=3D953271518-06012009><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Peter,</FONT></SPAN></DIV>
  <DIV><SPAN class=3D953271518-06012009><FONT face=3DArial =
color=3D#0000ff size=3D2>I do=20
  not think we have a standard method to indicate to the peer PE that =
the PW is=20
  administratively down.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D953271518-06012009><FONT face=3DArial =
color=3D#0000ff size=3D2>The=20
  only more or less suitable&nbsp;statement I've found in 4477=20
  says:</FONT></SPAN></DIV>
  <DIV><SPAN class=3D953271518-06012009><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>&lt;quote&gt;</FONT></SPAN></DIV>
  <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
    <DIV><SPAN class=3D953271518-06012009><EM>The PW label should not be =

    withdrawn&nbsp;unless the operator administratively configures the=20
    pseudowire down&nbsp;(or the PW configuration is deleted=20
    entirely).</EM></SPAN></DIV></BLOCKQUOTE>
  <DIV><SPAN class=3D953271518-06012009><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>&lt;end quote&gt;,</FONT></SPAN></DIV>
  <DIV><SPAN class=3D953271518-06012009><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D953271518-06012009><FONT face=3DArial =
color=3D#0000ff size=3D2>This=20
  statement&nbsp;seems to indicate that if a PW is administratively =
disabled, PW=20
  labels must be withdrawn (released?). But there are no dedicated error =
codes=20
  that could be used in the Label Release/Label Withdraw messages&nbsp; =
and no=20
  PW status bits either. (</FONT></SPAN><SPAN =
class=3D953271518-06012009><FONT=20
  face=3DArial color=3D#0000ff size=3D2>Mustapha's comment on the use of =
the "PW not=20
  forwarding" code point seems to support my opinion). =
</FONT></SPAN></DIV>
  <DIV><SPAN class=3D953271518-06012009><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D953271518-06012009><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Regarding the example: what you say means that the PE that =
has been=20
  used to set up the PW and where the PW end point has been deleted =
while CP was=20
  down must <EM>remember an already non-existing PW end point</EM> and =
update=20
  the peer about its deletion when this becomes possible. I do not think =
that=20
  this kind of behavior is defined anywhere, but maybe I've missed=20
  something?</FONT></SPAN></DIV>
  <DIV><SPAN class=3D953271518-06012009><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D953271518-06012009><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Regards,</FONT></SPAN></DIV>
  <DIV><SPAN class=3D953271518-06012009><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</FONT></SPAN></DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> Busschbach, Peter B =
(Peter)=20
    [mailto:busschbach@alcatel-lucent.com] <BR><B>Sent:</B> Tuesday, =
January 06,=20
    2009 7:49 PM<BR><B>To:</B> Alexander Vainshtein<BR><B>Cc:</B> =
pwe3@ietf.org;=20
    Shell Nakash; Prashant Desai; Igor Danilovich; Itamar Levy; =
Aissaoui,=20
    Mustapha (Mustapha); dallan@nortel.com; lmartini@cisco.com; Thomas =
D.=20
    Nadeau; mmorrow@cisco.com<BR><B>Subject:</B> RE: A question =
regarding torn=20
    down PWs in draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
    size=3D2>Sasha,</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
    size=3D2>First of all, my original email to you was incorrect. I =
wrote that in=20
    the case of administrative down, the PE should not insert FDI/AIS, =
but as=20
    Dave pointed out, it should.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
    size=3D2>Secondly, I still don't understand what you think is =
problematic in=20
    the example that you give. There are two cases:</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
    size=3D2>1) The control plane is up. The local PE informs the remote =
PE that=20
    the PW is to be torn down.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
    size=3D2>2) The control plane is down. The local PE has to wait for =
the=20
    control plane to come up before it can inform the remote PE that the =
PW is=20
    to be torn down. In the mean time, the remote PE performs the =
consequent=20
    actions associated with the defect condition, i.e. it inserts AIS on =
the=20
    AC.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
    size=3D2>What is the problem?</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D329174117-06012009><FONT =
face=3DArial=20
    size=3D2>Peter</FONT></SPAN></DIV><BR>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 =
2px solid; MARGIN-RIGHT: 0px">
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
      <HR tabIndex=3D-1>
      <FONT face=3DTahoma size=3D2><B>From:</B> Alexander Vainshtein=20
      [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> =
Tuesday,=20
      January 06, 2009 6:58 AM<BR><B>To:</B> Busschbach, Peter B=20
      (Peter)<BR><B>Cc:</B> pwe3@ietf.org; Shell Nakash; Prashant Desai; =
Igor=20
      Danilovich; Itamar Levy; Aissaoui, Mustapha (Mustapha); =
dallan@nortel.com;=20
      lmartini@cisco.com; Thomas D. Nadeau; =
mmorrow@cisco.com<BR><B>Subject:</B>=20
      RE: A question regarding torn down PWs in=20
      draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
      <DIV></DIV>
      <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff=20
      size=3D2>Peter,</FONT></SPAN></DIV>
      <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial><FONT =
size=3D2><FONT=20
      color=3D#0000ff>I see that I have been wrong when I've said that =
4447 does=20
      not allow differentiation between PW teardown due to defects and =
any other=20
      case of the PW teardown. In fact, it does by allocating a =
dedicated LDP=20
      status code <STRONG>0x0000002B&nbsp; - =
</STRONG></FONT></FONT><FONT=20
      size=3D2><FONT color=3D#0000ff><STRONG>"Label Withdraw PW Status =
Method Not=20
      Supported"&nbsp;</STRONG>&nbsp; that must be used in the =
<STRONG>Label=20
      Release Message</STRONG> if the PW is torn down due to defects. =
4447=20
      describes this as an optional method for equipment that does not =
support=20
      PW Status TLV.</FONT></FONT></FONT></SPAN><SPAN=20
      class=3D424163708-06012009><FONT face=3DArial color=3D#0000ff=20
      size=3D2></FONT></SPAN></DIV><SPAN class=3D424163708-06012009>
      <DIV><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT>&nbsp;</DIV>
      <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff=20
      size=3D2>Regarding the example, please note that the PWs can be =
set up in a=20
      single-ended manner using FEX 129. I would expect that, in this =
case, the=20
      users would presumably&nbsp;delete them&nbsp;in a single-ended way =
as=20
      well, initiating the teardown process at the same PE that has been =
used to=20
      set it up. This explains (hopefully) why in certain situations the =
user=20
      would remove the PW at one end only. </FONT></SPAN></DIV>
      <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff=20
      size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff=20
      size=3D2>If this explanation makes sense, then the problem I see =
with my=20
      example is easy to understand:</FONT></SPAN></DIV>
      <UL>
        <LI><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff=20
        size=3D2>If the PW is torn down while the CP is OK, the remote =
PE would=20
        not insert any AIS/FDI into its local AC</FONT></SPAN>=20
        <LI><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff=20
        size=3D2>If the PW is torn down while the CP is not operational =
(the=20
        targeted LDP session is down), then AIS/FDI insertion (activated =
by the=20
        CP failure) would persist until such time when the user deletes =
its=20
        endpoint in the other PE</FONT></SPAN>=20
        <LI><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff=20
        size=3D2>The bottom line: the behavior of the PW endpoint =
depends on the=20
        actual sequence of events. This does not look healthy to=20
        me.</FONT></SPAN></LI></UL>
      <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff=20
      size=3D2>Hopefully this clarifies the =
situation.</FONT></SPAN></DIV>
      <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff=20
      size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff=20
      size=3D2>Regards,</FONT></SPAN></DIV>
      <DIV><SPAN class=3D424163708-06012009><FONT face=3DArial =
color=3D#0000ff=20
      size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Sasha</FONT></SPAN></SPAN></DIV>
      <DIV>
      <HR tabIndex=3D-1>
      </DIV>
      <DIV><FONT face=3DTahoma size=3D2><B>From:</B> Busschbach, Peter B =
(Peter)=20
      [mailto:busschbach@alcatel-lucent.com] <BR><B>Sent:</B> Monday, =
January=20
      05, 2009 6:13 PM<BR><B>To:</B> Alexander Vainshtein<BR><B>Cc:</B>=20
      pwe3@ietf.org; Shell Nakash; Prashant Desai; Igor Danilovich; =
Itamar Levy;=20
      Aissaoui, Mustapha (Mustapha); dallan@nortel.com; =
lmartini@cisco.com;=20
      Thomas D. Nadeau; mmorrow@cisco.com<BR><B>Subject:</B> RE: A =
question=20
      regarding torn down PWs in=20
      draft-ietf-pwe3-oam-msg-map-08.txt<BR></FONT><BR></DIV>
      <BLOCKQUOTE dir=3Dltr=20
      style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff =
2px solid; MARGIN-RIGHT: 0px">
        <DIV></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D285020316-05012009><FONT face=3DArial=20
        size=3D2>Sasha,</FONT></SPAN></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D285020316-05012009><FONT face=3DArial=20
        size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D285020316-05012009><FONT face=3DArial=20
        size=3D2>Please see in-line</FONT></SPAN></DIV><BR>
        <BLOCKQUOTE dir=3Dltr=20
        style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: =
#000000 2px solid; MARGIN-RIGHT: 0px">
          <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
          <HR tabIndex=3D-1>
          <FONT face=3DTahoma><FONT size=3D2><B>From:</B> Alexander =
Vainshtein=20
          [mailto:Alexander.Vainshtein@ecitele.com] <BR><B>Sent:</B> =
Monday,=20
          January 05, 2009 10:09 AM<BR></FONT></FONT><FONT =
face=3DTahoma><BR><FONT=20
          size=3D2><SPAN class=3D285020316-05012009><FONT=20
          =
face=3DArial>[snipped]&nbsp;</FONT></SPAN><BR></FONT></FONT><BR></DIV>
          <BLOCKQUOTE dir=3Dltr=20
          style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: =
#0000ff 2px solid; MARGIN-RIGHT: 0px">
            <DIV></DIV>
            <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D214484013-05012009><FONT=20
            face=3DArial size=3D2><BR></FONT><SPAN =
class=3D017510414-05012009><FONT=20
            color=3D#0000ff><FONT face=3DArial><FONT =
size=3D2><EM>[[Sasha]]&nbsp;I am=20
            not aware of the case when a PW is torn down due to defects =
in the=20
            data plane. Could you please provide a reference/an=20
            example?<BR></EM></FONT></FONT></FONT></SPAN></SPAN></DIV>
            <DIV><SPAN class=3D214484013-05012009><SPAN=20
            class=3D017510414-05012009><FONT color=3D#0000ff><FONT =
face=3DArial><FONT=20
            size=3D2><SPAN=20
            =
class=3D285020316-05012009></SPAN></FONT></FONT></FONT></SPAN></SPAN>&nbs=
p;</DIV>
            <DIV><SPAN class=3D214484013-05012009><SPAN=20
            class=3D017510414-05012009><FONT color=3D#0000ff><FONT =
face=3DArial><FONT=20
            size=3D2><SPAN class=3D285020316-05012009></SPAN><BR><SPAN=20
            class=3D285020316-05012009><FONT =
color=3D#000000>[PB]&nbsp;&nbsp;See=20
            section 5.4.1 of RFC 4447: <FONT size=3D3>a simple label =
withdraw=20
            method MAY also be<BR>&nbsp;&nbsp; supported as a legacy =
means of=20
            signaling PW status and AC=20
            =
status</FONT></FONT></SPAN><BR></DIV></FONT></FONT></FONT></SPAN></SPAN>
            <DIV><SPAN class=3D214484013-05012009><SPAN=20
            class=3D017510414-05012009><FONT color=3D#0000ff><FONT =
face=3DArial><FONT=20
            size=3D2><SPAN=20
            =
class=3D285020316-05012009></SPAN></FONT></FONT></FONT></SPAN></SPAN>&nbs=
p;</DIV>
            <DIV><SPAN class=3D214484013-05012009><SPAN=20
            class=3D017510414-05012009><FONT color=3D#0000ff><FONT =
face=3DArial><FONT=20
            size=3D2><SPAN=20
            =
class=3D285020316-05012009></SPAN></FONT></FONT></FONT></SPAN></SPAN>&nbs=
p;</DIV>
            <DIV><SPAN class=3D214484013-05012009><FONT =
face=3DArial><FONT=20
            size=3D2>&nbsp;It would be good, however, if a PE would be =
able to=20
            distinguish between PWs torn down because of defects and PWs =
torn=20
            down for administrative reasons, because in the latter case =
there is=20
            no need to insert an FDI message downstream.<BR><SPAN=20
            class=3D017510414-05012009><FONT =
color=3D#0000ff><EM>[[Sasha]]&nbsp;I do=20
            not think that RFC 4447 provides for that.&nbsp;In addition, =
please=20
            consider the following=20
            scenario:</EM></FONT></SPAN></FONT></FONT></SPAN></DIV>
            <OL>
              <LI><SPAN class=3D214484013-05012009><FONT =
face=3DArial><FONT=20
              size=3D2><SPAN class=3D017510414-05012009><FONT =
color=3D#0000ff><EM>A PW=20
              is set up</EM></FONT></SPAN></FONT></FONT></SPAN>=20
              <LI><SPAN class=3D214484013-05012009><FONT =
face=3DArial><FONT=20
              size=3D2><SPAN class=3D017510414-05012009><FONT =
color=3D#0000ff><EM>The=20
              PW is torn down&nbsp;due to the CP defect (targeted LDP =
session=20
              went down). FDI is inserted in the local=20
              AC</EM></FONT></SPAN></FONT></FONT></SPAN>=20
              <LI><SPAN class=3D214484013-05012009><FONT =
face=3DArial><FONT=20
              size=3D2><SPAN class=3D017510414-05012009><EM>&nbsp;<FONT=20
              color=3D#0000ff>The user has deleted the PW end point in =
the remote=20
              PE. Since the LDP session is down, this fact is not =
communicated=20
              to the local PE</FONT></EM></SPAN></FONT></FONT></SPAN>=20
              <LI><SPAN class=3D214484013-05012009><FONT =
face=3DArial><FONT=20
              color=3D#0000ff size=3D2><SPAN =
class=3D017510414-05012009><EM>Targeted=20
              LDP session is restored but an attempt of the local PE to =
restore=20
              the PW fails since there is no remote peer anymore. =
<STRONG>What=20
              should now happen to the local=20
              AC</STRONG></EM></SPAN></FONT></FONT></SPAN></LI></OL>
            <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
            class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
            <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
            class=3D214484013-05012009></SPAN></FONT></FONT>&nbsp;</DIV>
            <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D214484013-05012009><SPAN=20
            class=3D285020316-05012009>[PB] I don't understand the =
example. Who is=20
            the user that removes the PW end point? A service provider? =
If so,=20
            why would that service provider update one PE to remove the =
PW but=20
            not the peer? </SPAN></SPAN></FONT></DIV>
            <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D214484013-05012009><SPAN=20
            class=3D285020316-05012009></SPAN></SPAN></FONT>&nbsp;</DIV>
            <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D214484013-05012009><SPAN=20
            class=3D285020316-05012009>In any case, if the local PE is =
inserting=20
            FDI messages periodically on the local AC, it will continue =
doing so=20
            as long as the PW is not restored. Do you believe it should =
behave=20
            otherwise?</SPAN></SPAN></FONT></DIV>
            <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D214484013-05012009><SPAN=20
            class=3D285020316-05012009></SPAN></SPAN></FONT>&nbsp;</DIV>
            <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D214484013-05012009><SPAN=20
            class=3D285020316-05012009>[snipped to the=20
            =
end]</SPAN></SPAN></FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></B=
LOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C97042.07F9E18E--

--===============1379617516==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1379617516==--


From pwe3-bounces@ietf.org  Tue Jan  6 15:33:29 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 26C793A6851;
	Tue,  6 Jan 2009 15:33:29 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E4AE33A6851
	for <pwe3@core3.amsl.com>; Tue,  6 Jan 2009 15:33:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
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 i0P5MlNkJKND for <pwe3@core3.amsl.com>;
	Tue,  6 Jan 2009 15:33:23 -0800 (PST)
Received: from napoleon.monoski.com (black.monoski.com [63.227.123.238])
	by core3.amsl.com (Postfix) with ESMTP id 18E603A6767
	for <pwe3@ietf.org>; Tue,  6 Jan 2009 15:33:23 -0800 (PST)
Received: from confusion.monoski.com (confusion.monoski.com [209.245.27.2])
	(authenticated bits=0)
	by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id n06NW5S7016972
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 6 Jan 2009 16:32:05 -0700 (MST)
Message-ID: <4963E9F5.5090403@cisco.com>
Date: Tue, 06 Jan 2009 16:32:05 -0700
From: Luca Martini <lmartini@cisco.com>
User-Agent: Thunderbird 2.0.0.18 (X11/20081105)
MIME-Version: 1.0
To: Stewart Bryant <stbryant@cisco.com>,
	Matthew BOCCI <Matthew.Bocci@alcatel.co.uk>
X-Scanned-By: MIMEDefang 2.63 on 209.245.27.1
Cc: "PWE3 WG \(E-mail\)" <pwe3@ietf.org>
Subject: [PWE3] draft-ietf-pwe3-ms-pw-arch-05 review comments
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Stewart, and Matthew,

Here are my review comments for the LC of this document.
Please note that in general the document is in very good shape, there is 
possibly only one paragraph that needs rewriting to make it clearer.
Also note that we use pseudowire ( PW ) to designate a PW , and PWE3 to 
designate the WG , or the technology.
Throughout the document you seem to use PWE3  when you mean PWs 
instead... I believe that we should be consistent in terminology with 
the existing RFCs.

Comments are inline.
Thanks.
Luca


> Network Working Group M.Bocci
>
> Internet Draft Alcatel-Lucent
>
> S.Bryant
>
> Cisco Systems
>
> Intended Status: Informational
>
> Expires: March 2009 September 25, 2008
>
> An Architecture for Multi-Segment Pseudowire Emulation Edge-to-Edge
>
>
>
> draft-ietf-pwe3-ms-pw-arch-05.txt
>
>
>
> Status of this Memo
>
>
> By submitting this Internet-Draft, each author represents that
>
> any applicable patent or other IPR claims of which he or she is
>
> aware have been or will be disclosed, and any of which he or she
>
> becomes aware will be disclosed, in accordance with Section 6 of
>
> BCP 79.
>
>
> Internet-Drafts are working documents of the Internet Engineering
>
> Task Force (IETF), its areas, and its working groups. Note that
>
> other groups may also distribute working documents as Internet-
>
> Drafts.
>
>
> Internet-Drafts are draft documents valid for a maximum of six months
>
> and may be updated, replaced, or obsoleted by other documents at any
>
> time. It is inappropriate to use Internet-Drafts as reference
>
> material or to cite them other than as "work in progress."
>
>
> The list of current Internet-Drafts can be accessed at
>
> http://www.ietf.org/ietf/1id-abstracts.txt
>
>
> The list of Internet-Draft Shadow Directories can be accessed at
>
> http://www.ietf.org/shadow.html
>
>
> This Internet-Draft will expire on March 25, 2009.
>
>
>
> Copyright Notice
>
>
> Copyright (C) The IETF Trust (2008). All Rights Reserved.
>
>
> Bocci et al Expires March 25, 2009 [Page 1]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> Abstract
>
>
> This document describes an architecture for extending pseudowire
>
> emulation across multiple packet switched network segments. Scenarios
>
> are discussed where each segment of a given edge-to-edge emulated
>
> service spans a different provider's PSN, and where the emulated
>
> service originates and terminates on the same providers PSN, but may
>
> pass through several PSN tunnel segments in that PSN. It presents an
>
> architectural framework for such multi-segment pseudowires, defines
>
> terminology, and specifies the various protocol elements and their
>
> functions.
>
>
> Conventions used in this document
>
>
> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>
> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>
> document are to be interpreted as described in RFC-2119 [1].
>
>
> Table of Contents
>
>
> 1. Introduction................................................3
>
> 1.1. Motivation and Context..................................3
>
> 1.2. Non-Goals of this Document..............................6
>
> 1.3. Terminology............................................6
>
> 2. Applicability...............................................7
>
> 3. Protocol Layering model......................................8
>
> 3.1. Domain of Multi-Segment PWE3............................8
>
> 3.2. Payload Types..........................................9
>
> 4. Multi-Segment PWE3 Reference Model...........................9
>
> 4.1. Intra-Provider Architecture............................10
>
> 4.1.1. Intra-Provider Switching Using ACs................11
>
> 4.1.2. Intra-Provider Switching Using PWs................11
>
> 4.2. Inter-Provider Architecture............................11
>
> 4.2.1. Inter-Provider Switching Using ACs................11
>
> 4.2.2. Inter-Provider Switching Using PWs................11
>
> 5. PE Reference Model.........................................12
>
> 5.1. PWE3 Pre-processing....................................12
>
> 5.1.1. Forwarding........................................12
>
> 5.1.2. Native Service Processing.........................13
>
> 6. Protocol Stack reference Model..............................13
>
> 7. Maintenance Reference Model.................................14
>
> 8. PW Demultiplexer Layer and PSN Requirements.................15
>
> 8.1. Multiplexing..........................................15
>
> 8.2. Fragmentation.........................................16
>
> 9. Control Plane..............................................16
>
> 9.1. Setup or Teardown of Pseudowires.......................16
>
> Bocci & Bryant Expires March 25, 2009 [Page 2]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> 9.2. Pseudowire Up/Down Notification........................17
>
> 9.3. Misconnection and Payload Type Mismatch................17
>
> 10. Management and Monitoring..................................17
>
> 11. Congestion Considerations..................................18
>
> 12. IANA Considerations........................................19
>
> 13. Security Considerations....................................19
>
> 14. Acknowledgments...........................................22
>
> 15. References................................................23
>
> 15.1. References...........................................23
>
> Author's Addresses............................................23
>
> Intellectual Property Statement................................24
>
> Disclaimer of Validity........................................24
>
> Copyright Statement...........................................25
>
> Acknowledgment................................................25
>
> 1. Introduction
>
>
> RFC 3985 [2] defines the architecture for pseudowires, where a
>
> pseudowire (PW) both originates and terminates on the edge of the
>
> same packet switched network (PSN). The PW passes through a maximum
>
> of one PSN tunnel between the originating and terminating PEs.
>
>
> This document extends the architecture in RFC 3985 to enable point to
>
> point pseudowires to be extended through multiple PSN tunnels. Use
>
> cases for multi-segment pseudowires, and the consequent requirements,
>
> are defined in [3].
>
>
> 1.1. Motivation and Context
>
>
> Originally, Pseudowire Emulation Edge-to-Edge (PWE3) provided point-
>
> to-point connectivity between two edges of a provider network using
>
> single-segment pseudowires (SS-PWs). However, there is now a
>
> requirement to be able to construct multi-segment pseudowires. These
>
> requirements are specified in [3]. These requirements address three
>
> main problems:
>
>
> o How to constrain the density of the mesh of PSN tunnels when the
>
> number of PEs grows to many hundreds or thousands, while
>
> minimizing the complexity of the PEs and P routers.
>
>
> o How to provide PWE3 across multiple PSN routing domains or areas
>
> in the same provider.
>
>
> o How to provide PWE3 across multiple provider domains, and
>
> different PSN types.
>
>
Can you make the bullets as in the other documents i) , ii), iii)  ?

>
> Bocci & Bryant Expires March 25, 2009 [Page 3]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> Consider a single PWE3 domain, such as that shown in Figure 1. There
>
> are 4 PEs, and PWE3 must be provided from any PE to any other PE.
>
> With SS-PWs, PWE3 would be achieved by establishing a full mesh of
>
All the above PWE3 -> PW
>
> PSN tunnels between the PEs, requiring a full mesh of LDP signaling
>
> adjacencies between the PEs. Pseudowires would therefore be
>
> established between any PE and any other PE via a single, direct PSN
>
> tunnel that is switched only by intermediate P-routers (not shown in
>
> the figure). A PE must terminate all the pseudowires that are carried
>
> on the PSN tunnels that terminate on that PE according to the
>
> architecture of RFC 3985. This solution is adequate for small numbers
>
> of PEs, but the number of PEs, PSN tunnels and signaling adjacencies
>
> will grow in proportion to the square of the number of PEs.
>
>
> A more efficient solution for large numbers of PEs would be to
>
INSERT:                     ^ for the control plane
>
> support a partial mesh of PSN tunnels between the PEs, as shown in
>
> Figure 1. For example, consider a PWE3 service whose endpoints are
>
> PE1 and PE4. Pseudowires for this can take the path PE1->PE2->PE4,
>
> and rather than terminating at PE2, be switched between ingress and
>
> egress PSN tunnels on that PE. This requires a capability in PE2 that
>
> can concatenate PW segments PE1-PE2 to PW segments PE2-PE4. The end-
>
> to-end PW is known as a multi-segment PW.
>
>
> ,,..--..,,_
>
> .-`` `'.,
>
> +-----+` '+-----+
>
> | PE1 |---------------------| PE2 |
>
> | |---------------------| |
>
> +-----+ PSN Tunnel +-----+
>
> / || || \
>
> / || || \
>
> | || || |
>
> | || PSN || |
>
> | || || |
>
> \ || || /
>
> \ || || /
>
> \|| ||/
>
> +-----+ +-----+
>
> | PE3 |---------------------| PE4 |
>
> | |---------------------| |
>
> +-----+`'.,_ ,.'` +-----+
>
> `'''---''``
>
> Figure 1 Single PSN PWE3 with Partial Mesh of PSN Tunnels
>
>
> Figure 1 shows a simple flat PSN topology. However, large provider
>
> networks are typically not flat, consisting of many domains that are
>
> connected together to provide edge-to-edge services. The elements in
>
>
> Bocci & Bryant Expires March 25, 2009 [Page 4]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> each domain are specialized for a particular role, for example
>
> supporting different PSN types or using different routing protocols.
>
>
> An example application is shown in Figure 2. Here, the provider's
>
> network is divided into three domains: Two access domains and the
>
> core domain. The access domains represent the edge of the provider's
>
> network at which services are delivered. In the access domain,
>
> simplicity is required in order to minimize the cost of the network.
>
> The core domain must support all of the aggregated services from the
>
> access domains, and the design requirements here are for scalability,
>
> performance, and information hiding (i.e. minimal state). The core
>
> must not be exposed to the state associated with large numbers of
>
> individual edge-to-edge flows. That is, the core must be simple and
>
> fast.
>
>
> In a traditional layer 2 network, the interconnection points between
>
> the domains are where services in the access domains are aggregated
>
> for transport across the core to other access domains. In an IP
>
> network, the interconnection points could also represent interworking
>
> points between different types of IP networks e.g. those with MPLS
>
> and those without, and also points where network policies can be
>
> applied.
>
>
> <-------- Edge to Edge Emulated Services ------->
>
> ,' . ,-` `', ,' .
>
> / \ .` `, / \
>
> / \ / , / \
>
> AC +----+ +----+ +----+ +----+ AC
>
> ---| PE |-----| PE |---------------| PE |-------| PE |---
>
> | 1 | | 2 | | 3 | | 4 |
>
> +----+ +----+ +----+ +----+
>
> \ / \ / \ /
>
> \ / \ Core ` \ /
>
> `, ` . ,` `, `
>
> '-'` `., _.` '-'`
>
> Access 1 `''-''` Access 2
>
> Figure 2 Multi-Domain Network Model
>
>
> A similar model can also be applied to inter-provider services, where
>
> a single PW spans a number of separate provider networks in order to
>
> connect ACs residing on PEs in disparate provider networks. In this
>
> case, each provider will typically maintain their own PE at the
>
> border of their network in order to apply policies such as security
>
> and QoS to PWs entering their network. Thus, the connection between
>
>
> Bocci & Bryant Expires March 25, 2009 [Page 5]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> the domains will normally be a link between two PEs on the border of
>
> each provider's network.
>
>
> Consider the application of this model to PWE3. PWE3 uses tunneling
>
CHANGE:                                 ^ to PW, PWs use tunneling
>
> mechanisms such as MPLS to enable the underlying PSN to emulate
>
> characteristics of the native service. One solution to the multi-
>
> domain network model above is to extend PSN tunnels edge-to-edge
>
> between all of the PEs in access domain 1 and all of the PEs in
>
> access domain 2, but this requires a large number of PSN tunnels as
>
> described above, and also exposes the access and the core of the
>
> network to undesirable complexity. An alternative is to constrain the
>
> complexity to the network domain interconnection points (PE2 and PE3
>
> in the example above). Pseudowires between PE1 and PE4 would then be
>
> switched between PSN tunnels at the interconnection points, enabling
>
> PWs from many PEs in the access domains to be aggregated across only
>
> a few PSN tunnels in the core of the network. PEs in the access
>
> domains would only need to maintain direct signaling sessions, and
>
> PSN tunnels, with other PEs in their own domain, thus minimizing
>
> complexity of the access domains.
>
>
> 1.2. Non-Goals of this Document
>
>
> The following are non-goals for this document:
>
>
> o The on-the-wire specification of PW encapsulations
>
>
> o The detailed specification of mechanisms for establishing and
>
> maintaining multi-segment pseudo-wires.
>
>
> 1.3. Terminology
>
>
> The terminology specified in RFC 3985 [2] and RFC 4026 [4] applies.
>
> In addition, we define the following terms:
>
>
> o PW Terminating Provider Edge (T-PE). A PE where the customer-
>
> facing attachment circuits (ACs) are bound to a PW forwarder. A
>
> Terminating PE is present in the first and last segments of a MS-
>
> PW. This incorporates the functionality of a PE as defined in RFC
>
> 3985.
>
>
> o Single-Segment Pseudowire (SS-PW). A PW setup directly between two
>
> T-PE devices. Each PW in one direction of a SS-PW traverses one
>
> PSN tunnel that connects the two T-PEs.
>
>
>
>
>
> Bocci & Bryant Expires March 25, 2009 [Page 6]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> o Multi-Segment Pseudowire (MS-PW). A static or dynamically
>
> configured set of two or more contiguous PW segments that behave
>
> and function as a single point-to-point PW. Each end of a MS-PW by
>
> definition MUST terminate on a T-PE.
>
>
> o PW Segment. A part of a single-segment or multi-segment PW, which
>
> is set up between two PE devices, T-PEs and/or S-PEs.
>
>
> o PW Switching Provider Edge (S-PE). A PE capable of switching the
>
> control and data planes of the preceding and succeeding PW
>
> segments in a MS-PW. The S-PE terminates the PSN tunnels of the
>
> preceding and succeeding segments of the MS-PW. It is therefore a
>
> PW switching point for a MS-PW. A PW Switching Point is never the
>
> S-PE and the T-PE for the same MS-PW. A PW switching point runs
>
> necessary protocols to setup and manage PW segments with other PW
>
> switching points and terminating PEs. A S-PE can exist anywhere
>
> where a PW must be processed or policy applied. It is therefore
>
> not limited to the edge of a provider network.
>
>
> o PW Switching. The process of switching the control and data planes
>
> of the preceding and succeeding PW segments in a MS-PW.
>
>
> 2. Applicability
>
>
> A MS-PW is a single PW that for technical or administrative reasons
>
> is segmented into a number of concatenated hops. From the perspective
>
> of a L2VPN, a MS-PW is indistinguishable from a SS-PW. Thus, the
>
> following are equivalent from the perspective of the T-PE
>
>
> +----+ +----+
>
> |TPE1+--------------------------------------------------+TPE2|
>
> +----+ +----+
>
> |<---------------------------PW----------------------------->|
>
> +----+ +---+ +---+ +----+
>
> |TPE1+--------------+SPE+-----------+SPE+---------------+TPE2|
>
> +----+ +---+ +---+ +----+
>
>
> Figure 3 MS-PW Equivalence
>
>
> Although a MS-PW may require services such as node discovery and path
>
> signaling to construct the PW, it should not be confused with a L2VPN
>
> system, which also requires these services. A VPWS connects its
>
> endpoints via a set of PWs. MS-PW is a mechanism that abstracts the
>
> construction of complex PWs from the construction of a L2VPN. Thus a
>
> Bocci & Bryant Expires March 25, 2009 [Page 7]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> T-PE might be an edge device optimized for simplicity and an S-PE
>
> might be an aggregation device designed to absorb the complexity of
>
> continuing the PW across the core of one or more service provider
>
> networks to another T-PE located at the edge of the network.
>
>
> As well as supporting traditional L2VPNs, an MS-PW is applicable to
>
> providing connectivity within a transport network based on packet
>
> switching technology [23]. Such a network uses pseudowires to support
>
> the transport and aggregation of all services. This application
>
> requires deterministic characteristics and behavior from the network.
>
> The operational requirements of such networks may need pseudowire
>
> segments that can be established and maintained in the absence of a
>
> control plane, and the operational independence of PW maintenance
>
> from the underlying PSN. Some mechanisms to suit these applications
>
> are described in [6].
>
>
> 3. Protocol Layering model
>
>
> The protocol-layering model specified in RFC 3985 applies to multi-
>
> segment PWE3 with the following clarification: the pseudowires may be
>
> considered to be a separate layer to the PSN tunnel. That is,
>
> although a PW segment will follow the path of the PSN tunnel between
>
> S-PEs, the MS-PW is independent of the PSN tunnel routing,
>
> operations, signaling and maintenance. The design of PW routing
>
> domains should not imply that the underlying PSN routing domains are
>
> the same. However, MS-PWs will reuse the protocols of the PSN and may
>
> use information that is extracted from the PSN e.g. reachability.
>
>
> 3.1. Domain of Multi-Segment PWE3
>
>
> PWE3 defines the Encapsulation Layer, i.e. the method of carrying
>
> various payload types, and the interface to the PW Demultiplexer
>
> Layer. It is expected that other layers will provide the following:
>
>
> . PSN tunnel setup, maintenance and routing
>
>
> . T-PE discovery
>
>
> Not all PEs may be capable of providing S-PE functionality.
>
> Connectivity to the next hop S-PE or T-PE must be provided by a PSN
>
> tunnel, according to [2]. The selection of which set of S-PEs to use
>
> to reach a given T-PE is considered to be within the scope of PWE3.
>
>
The title of this sub-section needs fixing PWE3 -> PW ... However this 
sub-section is like a piece of PWE3 charter , and I do not think it 
belongs in an architecture document.
this document really does not care what is the scope of the PWE3 WG ...
I do not see any useful information in this sub-section that is not a 
repeat of rfc3985
what where you trying to say here ?


>
>
>
> Bocci & Bryant Expires March 25, 2009 [Page 8]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> 3.2. Payload Types
>
>
> Multi-segment PWE3 is applicable to all PWE3 payload types.
>
> Encapsulations defined for SS-PWs are also used for MS-PW without
>
> change. Where the PSN types for each segment of an MS-PW are
>
> identical, the PW types of each segment must also be identical.
>
> However, if different segments run over different PSN types, the
>
> encapsulation may change but the PW segments must be of an equivalent
>
REPLACE:  equivalent -> the same
>
> PW type i.e. the S-PE must not need to process the PW payload to
>
> provide translation.
>
>
> 4. Multi-Segment PWE3 Reference Model
>
>
> The PWE3 reference architecture for the single segment case is shown
>
> in [2]. This architecture applies to the case where a PSN tunnel
>
> extends between two edges of a single PSN domain to transport a PW
>
> with endpoints at these edges.
>
>
>
> Native |<------Multi-Segment Pseudowire------>| Native
>
> Service | PSN PSN | Service
>
> (AC) | |<-Tunnel->| |<-Tunnel->| | (AC)
>
> | V V 1 V V 2 V V |
>
> | +----+ +-----+ +----+ |
>
> +----+ | |TPE1|===========|SPE1 |==========|TPE2| | +----+
>
> | |------|..... PW.Seg't1.........PW.Seg't3.....|-------| |
>
> | CE1| | | | | | | | | |CE2 |
>
> | |------|..... PW.Seg't2.........PW.Seg't4.....|-------| |
>
> +----+ | | |===========| |==========| | | +----+
>
> ^ +----+ +-----+ +----+ ^
>
> | Provider Edge 1 ^ Provider Edge 2 |
>
> | | |
>
> | | |
>
> | PW switching point |
>
> | |
>
> |<------------------ Emulated Service --------------->|
>
> Figure 4 MS-PW Reference Model
>
>
> Figure 4 extends this architecture to show a multi-segment case. The
>
> PEs that provide PWE3 to CE1 and CE2 are Terminating-PE1 (T-PE1) and
>
> Terminating-PE2 (T-PE2) respectively. A PSN tunnel extends from T-PE1
>
> to switching-PE1 (S-PE1) across PSN1, and a second PSN tunnel extends
>
> from S-PE1 to S-PE2 across PSN2. PWs are used to connect the
>
> attachment circuits (ACs) attached to PE1 to the corresponding ACs
>
> attached to PE3.
>
> Bocci & Bryant Expires March 25, 2009 [Page 9]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> Each PW segment on the tunnel across PSN1 is switched to a PW segment
>
> in the tunnel across PSN2 at S-PE1 to complete the multi-segment PW
>
> (MS-PW) between T-PE1 and T-PE2. S-PE1 is therefore the PW switching
>
> point. PW segment 1 and PW segment 3 are segments of the same MS-PW
>
> while PW segment 2 and PW segment 4 are segments of another MS-PW. PW
>
> segments of the same MS-PW (e.g., PW segment 1 and PW segment 3) must
>
> be of equivalent PW types, as described in Section 3.2. above, while
>
> PSN tunnels (e.g., PSN1 and PSN2) may be of the same or different PSN
>
> types. An S-PE switches an MS-PW from one segment to another based on
>
> the PW demultiplexer, i.e., PW label that may take one of the forms
>
> defined in RFC3985 Section 5.4.1 [2].
>
>
> Note that although Figure 4 only shows a single S-PE, a PW may
>
> transit more one S-PE along its path. This architecture is applicable
>
> when the S-PEs are statically chosen, or when they are chosen using a
>
> dynamic path selection mechanism. Both directions of an MS-PW must
>
> traverse the same set of S-PEs on a reciprocal path. Note that
>
> although the S-PE path is therefore reciprocal, the path taken by the
>
> PSN tunnels between the T-PEs and S-PEs may not be reciprocal due to
>
> choices made by the PSN routing protocol.
>
>
> 4.1. Intra-Provider Connectivity Architecture
>
>
> There is a requirement to deploy PWs edge-to-edge in large service
>
> provider networks [3]. Such networks typically encompass hundreds or
>
> thousands of aggregation devices at the edge, each of which would be
>
> a PE. These networks may be partitioned into separate metro and core
>
> PWE3 domains, where the PEs are interconnected by a sparse mesh of
>
> tunnels.
>
>
> Whether or not the network is partitioned into separate PWE3 domains,
>
REP{LACE:                                                   ^ PW
>
> there is also a requirement to support a partial mesh of traffic
>
> engineered PSN tunnels.
>
>
> The architecture shown in Figure 4 can be used to support such cases.
>
> PSN1 and PSN2 may be in different administrative domains or access,
>
> core or metro regions within the same provider's network. PSN 1 and
>
> PSN2 may also be of different types. For example, S-PEs may be used
>
> to connect PW segments traversing metro networks of one technology
>
> e.g. statically allocated labels, with segments traversing a MPLS
>
> core network.
>
>
> Alternatively, T-PE1, S-PE1 and T-PE2 may reside at the edges of the
>
> same PSN.
>
>
>
>
> Bocci & Bryant Expires March 25, 2009 [Page 10]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> 4.1.1. Intra-Provider Switching Using ACs
>
>
> In this model, the PW reverts to the native service AC at the PE.
>
INSERT:                                                         ^domain 
boundary
>
> This AC is then connected to a separate PW on the same PE. In this
>
> case, the reference models of RFC 3985 apply to each segment and to
>
> the PEs. The remaining PE architectural considerations in this
>
> document do not apply to this case.
>
>
>
> 4.1.2. Intra-Provider Switching Using PWs
>
>
> In this model, PW segments are switched between PSN tunnels that span
>
> portions of a provider's network, without reverting to the native
>
> service at the boundary. For example, in Figure 4, PSN 1 and PSN 2
>
> would be portions of the same provider's network.
>
>
> 4.2. Inter-Provider Connectivity Architecture
>
>
> Inter-provider PWs may need to be switched between PSN tunnels at the
>
> provider boundary in order to minimize the number of tunnels required
>
> to provide PWE3 services to CEs attached to each providers network.
>
> In addition, OAM, AAA and security mechanisms may need to be
>
Expand AAA and OAM

> implemented on a per-PW basis at the provider boundary. Further
>
> security related architectural considerations are described in
>
> Section 13.
>
>
> 4.2.1. Inter-Provider Switching Using ACs.
>
>
> In this model, the PW reverts to the native service at the provider
>
> boundary PE. This AC is then connected to a separate PW at the peer
>
> provider boundary PE. In this case, the reference models of RFC 3985
>
> apply to each segment and to the PEs. The remaining PE architectural
>
> considerations in this document do not apply to this case.
>
>
these sections  are  almost a duplication of 4.1, It should be easy to 
merge them , and simply mention that the difference might be that extra 
security , and policy enforcement measures are needed in the 
inter-provider case ....

> 4.2.2. Inter-Provider Switching Using PWs.
>
>
> In this model, PW segments are switched between PSN tunnels in each
>
> provider's network, without reverting to the native service at the
>
> boundary. This architecture is shown in Figure 5. Here, S-PE1 and S-
>
> PE2 are provider border routers. PW segment 1 is switched to PW
>
> segment 2 at S-PE1. PW segment 2 is then carried across an inter-
>
> provider PSN tunnel to S-PE2, where it is switched to PW segment 3 in
>
> PSN 2.
>
>
>
>
> Bocci & Bryant Expires March 25, 2009 [Page 11]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> |<------Multi-Segment Pseudowire------>|
>
> | Provider Provider |
>
> AC | |<----1---->| |<----2--->| | AC
>
> | V V V V V V |
>
> | +----+ +-----+ +----+ +----+ |
>
> +----+ | | |=====| |=====| |=====| | | +----+
>
> | |-------|......PW..........PW.........PW.......|-------| |
>
> | CE1| | | |Seg 1| |Seg 2| |Seg 3| | | |CE2 |
>
> +----+ | | |=====| |=====| |=====| | | +----+
>
> ^ +----+ +-----+ +----+ +----+ ^
>
> | T-PE1 S-PE1 S-PE2 T-PE2 |
>
> | ^ ^ |
>
> | | | |
>
> | PW switching points |
>
> | |
>
> | |
>
> |<------------------- Emulated Service --------------->|
>
>
> Figure 5 Inter-Provider Reference Model
>
>
> 5. PE Reference Model
>
>
> 5.1. PWE3 Pre-processing
>
>
> PWE3 preprocessing is applied in the T-PEs as specified in RFC 3985.
>
> Processing at the S-PEs is specified in the following sections.
>
>
> 5.1.1. Forwarding
>
>
> Each forwarder in the S-PE forwards packets from one PW segment on
>
> the ingress PSN facing interface of the S-PE to one PW segment on the
>
> egress PSN facing interface of the S-PE.
>
>
> The forwarder selects the egress segment PW based on the ingress PW
>
> label. The mapping of ingress to egress PW label may be statically or
>
> dynamically configured. Figure 6 shows how a single forwarder is
>
> associated with each PW segment at the S-PE.
>
>
>
>
>
>
>
>
>
>
> Bocci & Bryant Expires March 25, 2009 [Page 12]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> +------------------------------------------+
>
> | S-PE Device |
>
> +------------------------------------------+
>
> Ingress | | | | Egress
>
> PW instance | Single | | Single | PW Instance
>
> <==========>X PW Instance + Forwarder + PW Instance X<==========>
>
> | | | |
>
> +------------------------------------------+
>
> Figure 6 Point-to-Point Service
>
>
> Other mappings of PW to forwarder are for further study.
>
> 5.1.2. Native Service Processing
>
>
> There is no native service processing in the S-PEs.
>
>
> 6. Protocol Stack reference Model
>
>
> Figure 7 illustrates the protocol stack reference model for multi-
>
> segment PWs.
>
>
> +----------------+ +----------------+
>
> |Emulated Service| |Emulated Service|
>
> |(e.g., TDM, ATM)|<======= Emulated Service =======>|(e.g., TDM, ATM)|
>
> +----------------+ +----------------+
>
> | Payload | | Payload |
>
> | Encapsulation |<=== Multi-segment Pseudowire ===>| Encapsulation |
>
> +----------------+ +--------+ +----------------+
>
> |PW Demultiplexer|<PW Segment>|PW Demux|<PW Segment>|PW Demultiplexer|
>
> +----------------+ +--------+ +----------------+
>
> | PSN Tunnel, |<PSN Tunnel>| PSN |<PSN Tunnel>| PSN Tunnel, |
>
> | PSN & Physical | |Physical| | PSN & Physical |
>
> | Layers | | Layers | | Layers |
>
> +-------+--------+ +--------+ +----------------+
>
> | .......... | .......... |
>
> | / \ | / \ |
>
> +==========/ PSN \===/ PSN \==========+
>
> \ domain 1 / \ domain 2 /
>
> \__________/ \__________/
>
> `````````` ``````````
>
>
> Figure 7 Multi-Segment PW Protocol Stack
>
>
> The MS-PW provides the CE with an emulated physical or virtual
>
> connection to its peer at the far end. Native service PDUs from the
>
> CE are passed through an Encapsulation Layer and a PW demultiplexer
>
> Bocci & Bryant Expires March 25, 2009 [Page 13]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> is added at the sending T-PE. The PDU is sent over PSN domain via the
>
> PSN transport tunnel. The receiving S-PE swaps the existing PW
>
> demultiplexer for the demultiplexer of the next segment, and then
>
> sends the PDU over transport tunnel in PSN2. Where the ingress and
>
> egress PSN domains of the S-PE are of the same type e.g. they are
>
> both MPLS PSNs, a simple label swap operation is performed, as
>
> described in RFC 3031 [5] Section 3.13. However, where the ingress
>
> and egress PSNs are of different types, e.g. MPLS and L2TPv3, the
>
> ingress PW demultiplexer is removed (or popped), a mapping to the
>
> egress PW demultiplexer is performed, and then inserted (or pushed).
>
>
> Policies may also be applied to the PW at this point. Examples of
>
> such policies include: admission control, rate control, QoS mappings,
>
> and security. The receiving T-PE removes the PW demultiplexer and
>
> restores the payload to its native format for transmission to the
>
> destination CE.
>
>
> Where the encapsulation format is different e.g. MPLS and L2TPv3, the
>
> payload encapsulation may be transparently translated at the S-PE.
>
>
> 7. Maintenance Reference Model
>
>
> Figure 8 shows the maintenance reference model for multi-segment
>
> PWE3.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Bocci & Bryant Expires March 25, 2009 [Page 14]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> |<------------- CE (end-to-end) Signaling ------------>|
>
> | |
>
> | |<-------- MS-PW/T-PE Maintenance ----->| |
>
> | | |<---PW Seg't-->| |<--PW Seg't--->| | |
>
> | | | Maintenance | | Maintenance | | |
>
> | | | | | | | |
>
> | | | PSN | | PSN | | |
>
> | | | |<-Tunnel1->| | | |<-Tunnel2->| | | |
>
> | V V V Signaling V V V V Signaling V V V |
>
> V +----+ +-----+ +----+ V
>
> +----+ |TPE1|===========|SPE1 |===========|TPE2| +----+
>
> | |-------|......PW.Seg't1.........PW Seg't3......|------| |
>
> | CE1| | | | | | | |CE2 |
>
> | |-------|......PW.Seg't2.........PW Seg't4......|------| |
>
> +----+ | |===========| |===========| | +----+
>
> ^ +----+ +-----+ +----+ ^
>
> | Terminating ^ Terminating |
>
> | Provider Edge 1 | Provider Edge 2 |
>
> | | |
>
> | PW switching point |
>
> | |
>
> |<--------------------- Emulated Service ------------------->|
>
> Figure 8 MS-PWE3 Maintenance Reference Model
>
>
> RFC 3985 specifies the use of CE (end-to-end) and PSN tunnel
>
> signaling, and PW/PE maintenance. CE and PSN tunnel signaling is as
>
> specified in RFC 3985. However, in the case of MS-PWs, signaling
>
> between the PEs now has both an edge-to-edge and a hop-by-hop
>
> context. That is, signaling and maintenance between T-PEs and S-PEs
>
> and between adjacent S-PEs is used to set up, maintain, and tear down
>
> the MS-PW segments, which include the coordination of parameters
>
> related to each switching point, as well as the MS-PW end points.
>
>
> 8. PW Demultiplexer Layer and PSN Requirements
>
>
> 8.1. Multiplexing
>
>
> The purpose of the PW demultiplexer layer at the S-PE is to
>
> demultiplex PWs from ingress PSN tunnels and to multiplex them into
>
> egress PSN tunnels. Although each PW may contain multiple native
>
> service circuits, e.g. multiple ATM VCs, the S-PEs do not have
>
> visibility of, and hence do not change, this level of multiplexing
>
> because they contain no NSP.
>
>
>
>
> Bocci & Bryant Expires March 25, 2009 [Page 15]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> 8.2. Fragmentation
>
>
> If fragmentation is to be used in an MS-PW, T-PEs and S-PEs must
>
> satisfy themselves that fragmented PW payloads can be correctly
>
> reassembled for delivery to the destination attachment circuit.
>
>
> An S-PE is not required to make any attempt to reassemble a
>
> fragmented PW payload. However, it may choose to do so if, for
>
> example, it knows that a downstream PW segment does not support
>
> reassembly.
>
>
-----------------------------------------------------------------
>
> An S-PE may fragment a PW payload using [8].
>
>
> Fragmentation may have QoS and security implications, and should be
>
> used subject to the considerations described in [8].
>
>
-----------------------------------------------------------------
The above text should be removed .
This belongs in the segmented-PW draft. I thought that there was no need 
to explicitly mention this , however we can easily add this text to that 
document.

> 9. Control Plane
>
>
> 9.1. Setup and Placement of MS-PWs
>
>
> For multi-segment pseudowires, the intermediate PW switching points
>
> may be statically provisioned, or they may be chosen dynamically.
>
>
> For the static case, there are two options for exchanging the PW
>
> labels:
>
>
> o By configuration at the T-PEs or S-PEs
>
>
> o By signaling across each segment using a dynamic maintenance
>
> protocol.
>
>
> A multi-segment pseudowire may thus consist of segments where the
>
> labels are statically configured and segments where the labels are
>
> signaled.
>
>
> For the signaled case, there are two options for selecting the path
>
> of the MS-PW:
>
>
> o T-PEs determine the full path of the PW through intermediate
>
> switching points. This may be either static or based on a dynamic
>
> PW path selection mechanism.
>
>
> o Each segment of the PW path is determined locally by each T-PE or
>
> S-PE, either through static configuration or based on a dynamic PW
>
> path selection mechanism.
>
>
I'm not sure what the point of the above text is ...
I think you meant that the S-PE can either be dynamically chosen by the 
network , and statically configured by provisioning ....


>
> Bocci & Bryant Expires March 25, 2009 [Page 16]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> 9.2. Pseudowire Up/Down Notification
>
>
> Since a multi-segment PW consists of a number of concatenated PW
>
> segments, the emulated service can only be considered as being up
>
> when all of the constituting PW segments and PSN tunnels (if used)
>
> are functional and operational along the entire path of the MS-PW.
>
>
> If a native service requires bi-directional connectivity, the
>
> corresponding emulated service can only be signaled as being
>
> operational up when the PW segments and PSN tunnels (if used), are
>
> functional and operational in both directions.
>
>
> RFC 3985 describes the need for failure and other status notification
>
> mechanisms for PWs. These considerations also apply to multi-segment
>
> pseudowires. In addition, if a failure notification mechanism is
>
> provided for consecutive segments of the same PW, the S-PE must be
>
> able to propagate such notifications between the consecutive
>
> concatenated segments.
>
>
> 9.3. Misconnection and Payload Type Mismatch
>
>
> With PWE3, misconnection and payload type mismatch can occur.
>
> Misconnection can breach the integrity of the system. Payload
>
> mismatch can disrupt the customer network. In both instances, there
>
> are security and operational concerns.
>
>
> The services of the underlying tunneling mechanism or the PWE3
>
REPLACE: PWE3 -> PW
>
> control and OAM protocols can be used to ensure that the identity of
>
> the PW next hop is as expected. As part of the PW setup, a PW-TYPE
>
> identifier is exchanged. This is then used by the forwarder and the
>
> NSP of the T-PEs to verify the compatibility of the ACs. This can
>
> also be used by S-PEs to ensure that concatenated segments of a given
>
> MS-PW are compatible, or that a MS-PW is not misconnected into a
>
> local AC. In addition, it is advisable to do an end-to-end connection
>
REPLACE: Advisable -> possible
>
> verification to check the integrity of the PW, to verify the identity
>
> of S-PEs and check the correct connectivity at S-PEs, and to verify
>
> the identity of the T-PE.
>
>
> 10. Management and Monitoring
>
>
> The management and monitoring as described in RFC 3985 applies here.
>
>
> The MS-PW architecture introduces additional considerations related
>
INSERT:                             ^ two
>
> to management and monitoring.
>
>
> The first is that each S-PE is a new point at which defects may occur
>
> along the path of the PW. In order to troubleshoot MS-PWs, management
>
> Bocci & Bryant Expires March 25, 2009 [Page 17]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> and monitoring should be able to operate on a subset of the segments
>
> of an MS-PW, as well as edge-to-edge. That is, connectivity
>
> verification mechanisms should be able to troubleshoot and
>
> differentiate the connectivity between T-PEs and intermediate S-PEs,
>
> as well as T-PE to T-PE.
>
>
> The second is that the set of S-PEs used by an MS-PW to reach a T-PE
>
> may not coincide with that which would be determined by the routing
>
> and path selection mechanisms in the underlying PSN. While the path
>
> taken between consecutive T/S-PEs on a given MS-PW will be determined
>
> by the path of the underlying PSN tunnel, the set of T/S-PEs that
>
> are used may be chosen by configuration or by a dynamic MS-PW path
>
> selection mechanism that operates independently of the underlying
>
> PSN.
>

Tee above section ( second ...) is unclear , and needs re-writing.
All you want to say here is that the path is sub-optimal, and not 
completely determined nor are the S-PEs chosen  by the PSN routing 
protocols.
this just needs a bit of re-wording to be clearer.


-------------------
>
> Troubleshooting mechanisms should therefore be provided to
>
> verify the set of S-PEs that are traversed by a MS-PW to reach a T-
>
> PE.
>
>
remove the above text , it's a duplicate requirement form the ms-pw 
requirement document.

> Some of the S-PEs and the T-PEs for an MS-PW may reside in different
>
> service provider's PSN domain from that of the operator who initiated
>
> the establishment of the MS-PW. These situations may necessitate the
>
> use of remote management of the MS-PW, which is able to securely
>
> operate across provider boundaries.
>
>
>
>
> 11. Congestion Considerations
>
>
> The following congestion considerations apply to MS-PWs. These are in
>
> addition to the considerations for PWs described in RFC 3985 [2] and
>
> in the respective RFCs specifying each PW type.
>
>
> Editors note: Add reference to draft-ietf-pwe3-congestion-frmwk-
>
> 01.txt, or its successor, prior to publication.
>
>
> The control plane and the data plane fate-share in traditional IP
>
> networks. The implication of this is that congestion in the data
>
> plane can cause degradation of the operation of the control plane.
>
> Under quiescent operating conditions it is expected that the network
>
> will be designed to avoid such problems. However, MS-PW mechanisms
>
> should also consider what happens when congestion does occur, when
>
> the network is stretched beyond its design limits, for example during
>
> unexpected network failure conditions.
>
>
> Although congestion within a single provider's network can be
>
> mitigated by suitable engineering of the network so that the traffic
>
> Bocci & Bryant Expires March 25, 2009 [Page 18]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> imposed by PWs can never cause congestion in the underlying PSN, a
>
> significant number of MS-PWs are expected to be deployed for inter-
>
> provider services. In this case, there may be no way of a provider
>
> who initiates the establishment of a MS-PW at a T-PE guaranteeing
>
> that it will not cause congestion in a downstream PSN. A specific PSN
>
> may be able to protect itself from excess PW traffic by policing all
>
> PWs at the S-PE at the provider border. However, this may not
>
> effective when the PSN tunnel across a provider utilizes the transit
>
> services of another provider that cannot distinguish PW traffic from
>
> ordinary, TCP-controlled, IP traffic.
>
>
> Each segment of an MS-PW therefore needs to implement congestion
>
> detection and congestion control mechanisms where it is not possible
>
> to explicitly provision sufficient capacity to avoid congestion.
>
>
> In many cases, only the T-PEs may have sufficient information about
>
> each PW to fairly apply congestion control. Therefore, T-PEs need to
>
> be aware which of their PWs are causing congestion in a downstream
>
> PSN and their native service characteristics and to apply congestion
>
> control accordingly. S-PEs therefore need to propagate PSN congestion
>
> state information between their downstream and upstream directions.
>
> If the MS-PW transits many S-PEs, it may take some time for
>
> congestion state information to propagate from the congested PSN
>
> segment to the source T-PE, thus delaying the application of
>
> congestion control. Congestion control in the S-PE at the border of
>
> the congested PSN can enable a more rapid response and thus
>
> potentially reduce the duration of congestion.
>
>
> In addition to protecting the operation of the underlying PSN,
>
> consistent QoS and traffic engineering mechanisms should be used on
>
> each segment of a MS-PW to support the requirements of the emulated
>
> service. The QoS treatment given to a PW packet at an S-PE may be
>
> derived from context information of the PW (e.g. traffic or QoS
>
> parameters signaled to the S-PE by an MS-PW control protocol), or
>
> from PSN-specific QoS flags in the PSN tunnel label or PW
>
> demultiplexer e.g. EXP bits for an MPLS PSN or the DS field of the
>
> outer IP header for L2TPv3.
>
>
>
> 12. IANA Considerations
>
>
> This document does not contain any IANA actions.
>
>
> 13. Security Considerations
>
>
> The security considerations described in RFC 3985 [2] apply here.
>
> Bocci & Bryant Expires March 25, 2009 [Page 19]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> Detailed security requirements for MS-PWs are specified in [3]. This
>
> section describes the architectural implications of those
>
> requirements.
>
>
> The security implications for T-PEs are similar to those for PEs in
>
> single segment pseudowires. However, S-PEs represent a point in the
>
> network where the PW label is exposed to additional processing.
>
> Additional consideration needs to be given to the security of the S-
>
> PEs, both at the data plane and the control plane, particularly when
>
> these are dynamically selected and/or when the MS-PW transits the
>
> networks of multiple operators.
>
>
> An implicit trust relationship exists between the initiator of an MS-
>
> PW, the T-PEs, and the S-PEs along the MS-PW's path. That is, the T-
>
> PE trusts the S-PEs to process and switch PWs without compromising
>
> the security or privacy of the PWE3 service. An S-PE SHOULD NOT
>
> select a next-hop S-PE or T-PE unless it knows it would be considered
>
> eligible, as defined in [3], by the originator of the MS-PW. For
>
> dynamically placed MS-PWs, this can be achieved by allowing the T-PE
>
> to explicitly specify the path of the MS-PW. When the MS-PW is
>
> dynamically created by the use of a signaling protocol, an S-PE or T-
>
> PE SHOULD determine the authenticity of the peer entity from which it
>
> receives the request, and its compliance with policy.
>
>
> Where a MS-PW crosses a border between one provider and another
>
> provider, the MS-PW segment endpoints (S-PEs or T-PEs), or P-routers
>
> for the PSN tunnel, typically reside on the same nodes as the ASBRs
>
> interconnecting the two providers. In either case, an S-PE in one
>
> provider is connected to a limited number of trusted T-PEs or S-PEs
>
> in the other provider. The number of such trusted T-PEs or S-PEs is
>
> bounded and not anticipated to create a scaling issue for the control
>
> plane authentication mechanisms.
>
>
> Directly interconnecting the S-PEs/T-PEs using a physically secure
>
> link, and enabling signaling and routing authentication between the
>
> S-PEs/T-PEs, eliminates the possibility of receiving a MS-PW
>
> signaling message or packet from an untrusted peer. The S-PEs/T-PEs
>
> represent security policy enforcement points for the MS-PW, while the
>
> ASBRs represent security policy enforcement points for the provider's
>
> PSNs. This architecture is illustrated in Figure 9.
>
>
>
>
>
>
>
> Bocci & Bryant Expires March 25, 2009 [Page 20]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> |<------------- MS-PW ---------------->|
>
> | Provider Provider |
>
> AC | |<----1---->| |<----2--->| | AC
>
> | V V V V V V |
>
> | +----+ +-----+ +----+ +----+ |
>
> +---+ | | |=====| |=====| |=====| | | +---+
>
> | |-------|......PW..........PW.........PW.......|-------| |
>
> |CE1| | | |Seg 1| |Seg 2| |Seg 3| | | |CE2|
>
> +---+ | | |=====| |=====| |=====| | | +---+
>
> ^ +----+ +-----+ ^ +----+ +----+ ^
>
> | T-PE1 S-PE1 | S-PE2 T-PE2 |
>
> | ASBR | ASBR |
>
> | | |
>
> | Physically secure link |
>
> | |
>
> | |
>
> |<------------------- Emulated Service --------------->|
>
>
> Figure 9 Directly Connected Inter-Provider Reference Model
>
>
>
> Alternatively, the P-routers for the PSN tunnel may reside on the
>
> ASBRs, while the S-PEs or T-PEs reside behind the ASBRs within each
>
> provider's network. A limited number of trusted inter-provider PSN
>
> tunnels interconnect the provider networks. This is illustrated in
>
> Figure 10.
>
>
> |<-------------- MS-PW -------------------->|
>
> | Provider Provider |
>
> AC | |<------1----->| |<-----2------->| | AC
>
> | V V V V V V |
>
> | +---+ +---+ +--+ +--+ +---+ +---+ |
>
> +---+ | | |=====| |===============| |=====| | | +---+
>
> | |-----|.....PW............PW..............PW......|------| |
>
> |CE1| | | |Seg 1| | Seg 2 | |Seg 3| | | |CE2|
>
> +---+ | | |=====| |===============| |=====| | | +---+
>
> ^ +---+ +---+ +--+ ^ +--+ +---+ +---+ ^
>
> | T-PE1 S-PE1 ASBR | ASBR S-PE2 T-PE2 |
>
> | | |
>
> | | |
>
> | Trusted Inter-AS PSN Tunnel |
>
> | |
>
> | |
>
> |<------------------- Emulated Service ----------------->|
>
>
> Figure 10 Indirectly Connected Inter-Provider Reference Model
>
> Bocci & Bryant Expires March 25, 2009 [Page 21]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> Particular consideration needs to be given to Quality of Service
>
> requests because the inappropriate use of priority may impact any
>
> service guarantees given to other PWs. Consideration also needs to be
>
> given to the avoidance of spoofing the PW demultiplexer.
>
>
> Where an S-PE provides interconnection between different providers,
>
> similar considerations to those applied to ASBRs apply. In particular
>
> peer entity authentication SHOULD be used.
>
>
> Where an S-PE also supports T-PE functionality, mechanisms should be
>
> provided to ensure that MS-PWs to switched correctly to the
>
> appropriate outgoing PW segment, rather than a local AC. Other
>
> mechanisms for PW end point verification may also be used to confirm
>
> the correct PW connection prior to enabling the attachment circuits.
>
>
> 14. Acknowledgments
>
>
> The authors gratefully acknowledge the input of Mustapha Aissaoui,
>
> Dimitri Papadimitrou, Sasha Vainshtein, and Luca Martini.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Bocci & Bryant Expires March 25, 2009 [Page 22]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> 15. References
>
>
> 15.1. References
>
>
> [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
>
> Levels", BCP 14, RFC 2119, March 1997.
>
>
> [2] Bryant, S. and Pate, P. (Editors), "Pseudo Wire Emulation Edge-
>
> to-Edge (PWE3) Architecture", RFC 3985, March 2005
>
>
> [3] Martini, L. Bitar, N. and Bocci, M (Editors), "Requirements for
>
> Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3)", draft-
>
> ietf-pwe3-ms-pw-requirements-07.txt, Internet Draft, June 2008
>
>
> [4] Andersson, L. and Madsen, T., "Provider Provisioned Virtual
>
> Private Network (VPN) Terminology", RFC 4026, March 2005
>
>
> [5] Rosen, E. Viswanathan, A. and Callon, R., "Multiprotocol Label
>
> Switching Architecture", RFC 3031, January 2001
>
>
> [6] Bryant et al, "Application of Ethernet Pseudowires to MPLS
>
> Transport Networks", draft-ietf-pwe3-mpls-transport-02.txt,
>
> Internet Draft, February 2008
>
>
> [7] Bryant, S. & Andersson, L. "JWT Report on MPLS Architectural
>
> Considerations for a Transport profile", draft-bryant-mpls-tp-
>
> jwt-report-00, Internet Draft, July 2008
>
>
> [8] Malis, A. and Townsley, M., "Pseudowire Emulation Edge-to-Edge
>
> (PWE3) Fragmentation and Reassembly", RFC 4623, August 2006
>
>
>
> Author's Addresses
>
>
> Matthew Bocci
>
> Alcatel-Lucent
>
> Voyager Place, Shoppenhangers Road,
>
> Maidenhead, Berks, UK
>
> Phone: +44 1633 413600
>
> Email: matthew.bocci@alcatel-lucent.com
>
>
>
>
>
>
>
> Bocci & Bryant Expires March 25, 2009 [Page 23]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> Stewart Bryant
>
> Cisco
>
> 250, Longwater,
>
> Green Park,
>
> Reading, RG2 6GB,
>
> United Kingdom.
>
> Email: stbryant@cisco.com
>
>
>
> Intellectual Property Statement
>
>
> The IETF takes no position regarding the validity or scope of any
>
> Intellectual Property Rights or other rights that might be claimed to
>
> pertain to the implementation or use of the technology described in
>
> this document or the extent to which any license under such rights
>
> might or might not be available; nor does it represent that it has
>
> made any independent effort to identify any such rights. Information
>
> on the procedures with respect to rights in RFC documents can be
>
> found in BCP 78 and BCP 79.
>
>
> Copies of IPR disclosures made to the IETF Secretariat and any
>
> assurances of licenses to be made available, or the result of an
>
> attempt made to obtain a general license or permission for the use of
>
> such proprietary rights by implementers or users of this
>
> specification can be obtained from the IETF on-line IPR repository at
>
> http://www.ietf.org/ipr.
>
>
> The IETF invites any interested party to bring to its attention any
>
> copyrights, patents or patent applications, or other proprietary
>
> rights that may cover technology that may be required to implement
>
> this standard. Please address the information to the IETF at ietf-
>
> ipr@ietf.org.
>
>
> Disclaimer of Validity
>
>
> This document and the information contained herein are provided on an
>
> "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
>
> OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
>
> THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
>
> OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
>
> THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
>
> WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
>
>
>
>
> Bocci & Bryant Expires March 25, 2009 [Page 24]
>
>
>
> Internet-Draft Multi-Segment PWE3 Architecture September 25, 2008
>
>
> Copyright Statement
>
>
> Copyright (C) The IETF Trust (2008).
>
>
> This document is subject to the rights, licenses and restrictions
>
> contained in BCP 78, and except as set forth therein, the authors
>
> retain all their rights.
>
>
>
> Acknowledgment
>
>
> Funding for the RFC Editor function is currently provided by the
>
> Internet Society.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Bocci & Bryant Expires March 25, 2009 [Page 25]
>
>
>


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


From pwe3-bounces@ietf.org  Wed Jan  7 02:07:14 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E318A3A687E;
	Wed,  7 Jan 2009 02:07:14 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3EB183A687E;
	Wed,  7 Jan 2009 02:07:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level: 
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=0.032, 
	BAYES_00=-2.599]
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 xhfHKmO7o3yZ; Wed,  7 Jan 2009 02:07:13 -0800 (PST)
Received: from neo.viciousnest.net (neo.viciousnest.net [192.71.80.124])
	by core3.amsl.com (Postfix) with ESMTP id 5959B3A681A;
	Wed,  7 Jan 2009 02:07:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by neo.viciousnest.net (Postfix) with ESMTP id 0E678F1C2;
	Wed,  7 Jan 2009 11:06:58 +0100 (CET)
Received: from neo.viciousnest.net ([127.0.0.1])
	by localhost (neo [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 29374-06; Wed,  7 Jan 2009 11:06:52 +0100 (CET)
Received: from [127.0.0.1] (wdhcp-158-76.verkstad.net [192.36.158.76])
	by neo.viciousnest.net (Postfix) with ESMTP id 47276F1C0;
	Wed,  7 Jan 2009 11:06:52 +0100 (CET)
Message-ID: <49647EB3.1090603@pi.nu>
Date: Wed, 07 Jan 2009 11:06:43 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: mpls-tp@ietf.org, mpls@ietf.org, pwe3@ietf.org, ccamp@ietf.org, 
	ahtmpls@itu.int
X-Virus-Scanned: by amavisd-new at viciousnest.net
Cc: George Swallow <swallow@cisco.com>,
	Matthew Bocci <Matthew.Bocci@alcatel-lucent.com>,
	David Ward <dward@cisco.com>, Malcolm Betts <betts01@nortel.com>,
	Deborah Brungard <dbrungard@att.com>, Stewart Bryant <stbryant@cisco.com>
Subject: [PWE3] Working Group Last Call on draft-ietf-mpls-tp-gach-gal-01
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

All,

this is to initiate a working group last call on
http://tools.ietf.org/html/draft-ietf-mpls-tp-gach-gal-01

This is the first of a series MPLS Transport Profile documents
to be last called. The last call is directed to the MPLS, PWE3
and CCAMP working groups.

According to procedures agreed upon in the JWT decision the
working last call does also include the ITU-T MPLS-TP ad hoc team.

This working group last call will end eob Jan 20, 2009.

Though I know this is futile:

*Please do not do a "Replay all"* but direct comments to the
mpls-tp@ietf.org mailing list.

/Loa

-- 


Loa Andersson

Sr Strategy and Standards Manager
Redback Networks                      phone:  +46 8 632 77 14
An Ericsson company
                                       email:  loa.andersson@redback.com
                                               loa@pi.nu

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


From pwe3-bounces@ietf.org  Wed Jan  7 10:09:38 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 43E593A6B19;
	Wed,  7 Jan 2009 10:09:38 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 287D43A6A6F;
	Wed,  7 Jan 2009 10:09:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.998
X-Spam-Level: 
X-Spam-Status: No, score=-5.998 tagged_above=-999 required=5 tests=[AWL=0.601, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 aQBrZtw8Yug3; Wed,  7 Jan 2009 10:09:35 -0800 (PST)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56])
	by core3.amsl.com (Postfix) with ESMTP id D44D13A6932;
	Wed,  7 Jan 2009 10:09:34 -0800 (PST)
Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com
	[47.129.230.99])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	n07I91O25713; Wed, 7 Jan 2009 18:09:01 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 7 Jan 2009 13:08:35 -0500
Message-ID: <87AC5F88F03E6249AEA68D40BD3E00BE168326CA@zcarhxm2.corp.nortel.com>
In-Reply-To: <49647EB3.1090603@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls-tp] Working Group Last Call on
	draft-ietf-mpls-tp-gach-gal-01
Thread-Index: AclwvZCz0cmw2WJfT/2Q7+NnmX8JfAAHnoOw
References: <49647EB3.1090603@pi.nu>
From: "David Allan" <dallan@nortel.com>
To: "Loa Andersson" <loa@pi.nu>, <mpls-tp@ietf.org>, <mpls@ietf.org>,
	<pwe3@ietf.org>, <ccamp@ietf.org>, <ahtmpls@itu.int>
Cc: Matthew Bocci <Matthew.Bocci@alcatel-lucent.com>
Subject: Re: [PWE3] [mpls-tp] Working Group Last Call on
	draft-ietf-mpls-tp-gach-gal-01
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Hi Loa/authors: 

Some comments:

1) I for one would like to see a stronger health warning in section 3.1.
Such as...

"You MAY use these mechanisms with IP/MPLS but will produce
indeterminate results as GAL/GACH identified OAM PDUs are not guaranteed
to fate share with payload in the presence of ECMP (as per RFC 4928)."

Alternatively I'd recommend a stronger advistory recommending that these
tools should only be considered when one can be sure that there is an
identical profile to MPLS-TP employed with IP/MPLS (no ECMP, no PHP, no
merge).  

2) Similarly section 3.3 suggests that the presence of the GACH means
the GAL/GACH combination complies with RFC 4928.

Presence of the GACH alone avoids ECMP and v4/v6 aliasing. Not true for
the combination of GAL/GACH.

So the first bullet of 3.3 should simply be turfed. The claim of 4928
compliance is specious and misleading.

3) The second bullet of 3.3 (suggesting scope of GAL exceeds that of RFC
3429) does not really hold water as well and should also be turfed.

The only real substantive content in section 3.3 is that RFC 3429 is
deployed and the hence a new reserved label was needed if OAM PDUs were
to be redesigned.

4) I find section 4 a bit bizzare, suggesting what non compliant devices
should do....
	- either it does not support GAL/GACH and does not know it OR
	- it does not support it but knows what it is...

   What it should say is already in RFC 3813....increment
ifInUnknownProtos in the MPLS layer ifTable.

Cheers
Dave


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


From pwe3-bounces@ietf.org  Wed Jan 14 08:58:45 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6113628C1D0;
	Wed, 14 Jan 2009 08:58:45 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 652B43A69FB;
	Wed, 14 Jan 2009 08:58:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.298
X-Spam-Level: 
X-Spam-Status: No, score=-10.298 tagged_above=-999 required=5
	tests=[AWL=0.301, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 sV8XBZqNLE-G; Wed, 14 Jan 2009 08:58:43 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id AE0B93A69CF;
	Wed, 14 Jan 2009 08:58:41 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,263,1231113600"; 
	d="eml'208?scan'208,208";a="30890886"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 14 Jan 2009 16:58:25 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n0EGwPh6023907; 
	Wed, 14 Jan 2009 17:58:25 +0100
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n0EGwPbW000109;
	Wed, 14 Jan 2009 16:58:25 GMT
Received: from stewart-bryants-computer.local (localhost [127.0.0.1])
	by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id n0EGwOx23538;
	Wed, 14 Jan 2009 16:58:24 GMT
Message-ID: <496E19B0.8030809@cisco.com>
Date: Wed, 14 Jan 2009 16:58:24 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105)
MIME-Version: 1.0
To: pwe3 <pwe3@ietf.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Content-Type: multipart/mixed; boundary="------------010005040909090207050901"
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=10702; t=1231952305;
	x=1232816305; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=stbryant@cisco.com;
	z=From:=20Stewart=20Bryant=20<stbryant@cisco.com>
	|Subject:=20[Fwd=3A=20Re=3A=20ANNOUNCEMENT=3A=20The=20IETF=
	20Trustees=20invite=20your=20review=20and=0A=20comments=20on
	=20a=20proposed=20Work-Around=20to=20the=20Pre-5378=20Proble m]
	|Sender:=20; bh=fs6T3xfjS+z1bnSTYee8XRWyfDNYfV2EVGi+ZdSQi+Q=;
	b=UXJ/hR5+tzxGndso9WY+LC8IttaVZsA/qiVNeILUeftc3LzSf8KffQBKvJ
	WzgsWKjAuOs7WY7OY2BC1BEm0Q8QkmJA4n2X5XGL3Oegoy2vl72GxzGG2qz5
	cQXZ/ChSQw;
Authentication-Results: ams-dkim-2; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Subject: [PWE3] [Fwd: Re: ANNOUNCEMENT: The IETF Trustees invite your review
 and comments on a proposed Work-Around to the Pre-5378 Problem]
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.
--------------010005040909090207050901
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

FYI

--------------010005040909090207050901
Content-Type: message/rfc822;
 name="Re: ANNOUNCEMENT: The IETF Trustees invite your review and	comments on a proposedWork-Around to the Pre-5378 Problem.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename*0="Re: ANNOUNCEMENT: The IETF Trustees invite your review and	c";
 filename*1="omments on a proposed Work-Around to the Pre-5378 Problem.em";
 filename*2="l"

X-Account-Key: account3
X-Mozilla-Keys: 
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id n0EGNXx19204
	for <stbryant@mrwint.cisco.com>; Wed, 14 Jan 2009 16:23:33 GMT
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
  by sj-iport-2.cisco.com with ESMTP; 14 Jan 2009 16:23:33 +0000
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n0EGNXrP012821;
	Wed, 14 Jan 2009 08:23:33 -0800
Received: from sj-inbound-d.cisco.com (sj-inbound-d.cisco.com [128.107.243.13])
	by sj-core-4.cisco.com (8.13.8/8.13.8) with ESMTP id n0EGNSgN004746;
	Wed, 14 Jan 2009 16:23:33 GMT
X-from-outside-Cisco: 64.170.98.32
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AocBAG+gbUlAqmIglGdsb2JhbACUFgEBAQEJCwgJEQW6GIVv
X-IronPort-AV: E=Sophos;i="4.37,263,1231113600"; 
   d="scan'208";a="63651622"
Received: from mail.ietf.org ([64.170.98.32])
  by sj-inbound-d.cisco.com with ESMTP; 14 Jan 2009 16:23:32 +0000
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CD1A628C1A4;
	Wed, 14 Jan 2009 08:23:46 -0800 (PST)
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E1BF73A6833
	for <wgchairs@core3.amsl.com>; Wed, 14 Jan 2009 08:23:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.5
X-Spam-Level: 
X-Spam-Status: No, score=-102.5 tagged_above=-999 required=5 tests=[AWL=0.099, 
	BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 D4KZCiJ4DjD8 for <wgchairs@core3.amsl.com>;
	Wed, 14 Jan 2009 08:23:44 -0800 (PST)
Received: from woodstock.binhost.com (woodstock.binhost.com [8.8.40.152])
	by core3.amsl.com (Postfix) with SMTP id 8B60C3A63CB
	for <wgchairs@ietf.org>; Wed, 14 Jan 2009 08:23:44 -0800 (PST)
Received: (qmail 27912 invoked by uid 0); 14 Jan 2009 16:23:26 -0000
Received: from unknown (HELO THINKPADR52.vigilsec.com) (96.255.143.189)
	by woodstock.binhost.com with SMTP; 14 Jan 2009 16:23:26 -0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 14 Jan 2009 11:00:05 -0500
To: wgchairs@ietf.org
From: Russ Housley <housley@vigilsec.com>
Subject: Re: ANNOUNCEMENT: The IETF Trustees invite your review and
	comments on a proposed Work-Around to the Pre-5378 Problem
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-Id: <20090114162344.8B60C3A63CB@core3.amsl.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>,
	<mailto:wgchairs-request@ietf.org?subject=subscribe>
Sender: wgchairs-bounces@ietf.org
Errors-To: wgchairs-bounces@ietf.org
Authentication-Results: sj-dkim-2; header.From=housley@vigilsec.com; dkim=neutral

WG Chairs:

Please make sure that your WG, and especially your document authors, 
are aware of this situation.  Please follow the discussion on the 
IETF Discussion list, and keep the WG informed about the way forward 
as it develops.

Thanks,
   Russ


>From: "Ed Juskevicius" <edj.etc@gmail.com>
>To: "'IETF Discussion'" <ietf@ietf.org>, <ietf-announce@ietf.org>,
>         <iesg@ietf.org>, <iab@iab.org>, <rfc-editor@rfc-editor.org>,
>         <wgchairs@ietf.org>
>Date: Thu, 8 Jan 2009 16:43:50 -0500
>Cc: 'Trustees' <trustees@ietf.org>
>Subject: [Trustees] ANNOUNCEMENT: The IETF Trustees invite your review and
>         comments on a proposed Work-Around to the Pre-5378 Problem
>
>The purpose of this message is twofold:
>
>1) To summarize the issues that some members of our community
>    have experienced since the publication of RFC 5378 in November 2008,
>    and
>2) To invite community review and discussion on a potential work-around
>    being considered by the IETF Trustees.
>
>Some I-D authors are having difficulty implementing RFC 5378.  An
>example of the difficulty is as follows:
>
>   - an author wants to include pre-5378 content in a new submission
>     or contribution to the IETF, but
>   - s/he is not certain that all of the author(s) of the earlier
>     material have agreed to license it to the IETF Trust according
>     to RFC 5378.
>
>If an I-D author includes pre-5378 material in a new document, then s/he
>must represent or warrant that all of the authors who created the
>pre-5378 material have granted rights for that material to the IETF Trust.
>If s/he cannot make this assertion, then s/he has a problem.
>
>This situation has halted the progression of some Internet-Drafts and
>interrupted the publication of some RFCs.  The Trustees of the IETF Trust
>are investigating ways to implement a temporary work-around so that IETF
>work can continue to progress.  A permanent solution to this "pre-5378
>problem" may require an update to RFC 5378, for example new work by the
>community to create a 5378-bis document.
>
>The remainder of this message provides an outline of the temporary work-
>around being considered by the Trustees.
>
>RFC 5378 sections 1.j and 5.3.c provide the IETF Trust with the
>authority to develop legend text for authors to use in situations where
>they wish to limit the granting of rights to modify and prepare
>derivatives of the documents they submit.  The Trustees used this
>authority in 2008 to develop and adopt the current "Legal Provisions
>Relating to IETF Documents" which are posted at:
>http://trustee.ietf.org/license-info/.
>
>The Trustees are now considering the creation of optional new legend text
>which could be used by authors experiencing the "pre-5378 problem".
>
>The new legend text, if implemented, would do the following:
>
>   a. Provide Authors and Contributors with a way to identify (to the
>      IETF Trust) that their contributions contain material from pre-5378
>      documents for which RFC 5378 rights to modify the material outside
>      the IETF standards process may not have been granted, and
>
>   b. Provide the IETF Trust and the community with a clear indication
>      of every document containing pre-5378 content and having the
>      "pre-5378 problem".
>
>So, how could the creation and use of some new legend text help people
>work-around the pre-5378 problem?
>
>The proposed answer is as follows:
>
>   1. Anyone having a contribution with the "pre-5378" problem should add
>      new legend text to the contribution, to clearly flag that it includes
>      pre-5378 material for which all of the rights needed under RFC 5378
>      may not have been granted, and
>
>   2. The IETF Trust will consider authors and contributors (with the
>      pre-5378 problem) to have met their RFC 5378 obligations if the
>      new legend text appears on their documents, and
>
>   3. Authors and contributors should only resort to adding the new
>      legend text to their documents (per #1) if they cannot develop
>      certainty that all of the author(s) of pre-5378 material in
>      their documents have agreed to license the pre-5378 content to
>      the IETF Trust according to RFC 5378.
>
>The proposed wording for the new legend text is now available for your
>review and comments in section 6.c.iii of a draft revision to the
>IETF Trust's "Legal Provisions Relating to IETF Documents" located at
>http://trustee.ietf.org/policyandprocedures.html.
>
>Please note that the above document also contains new text in section 5.c
>dealing with "License Limitations".
>
>If your review and feedback on this proposed work-around is positive,
>then the new text may be adopted by the Trustees in early February 2009,
>and then be published as an official revision to the Legal Provisions
>document.  If so adopted, Internet-Drafts with pre-5378 material may
>advance within the Internet standards process and get published as RFCs
>where otherwise qualified to do so.  Unless covered by sections 6.c.i or
>6.c.ii, authors of documents in which there is no pre-5378
>material must provide a RFC 5378 license with no limitation on
>modifications outside the IETF standards process.
>
>The IETF Trust will not grant the right to modify or prepare derivative
>works of any specific RFC or other IETF Contribution outside the IETF
>standards process until RFC 5378 rights pertaining to that document have
>been obtained from all authors and after compliance by the IETF Trust
>with RFC 5377.  The Trustees will establish one or more mechanisms by
>which authors of pre-5378 documents may grant RFC 5378 rights.
>
>The Trustees hereby invite your review, comments and suggestions on this
>proposed work-around to the "pre-5378 problem".  The period for this review
>is 30 days.  Microsoft WORD and PDF versions of the proposed revisions are
>attached to this message.  Copies are also available on the IETF Trust
>website under the heading "DRAFT Policy and Procedures Being Developed" at:
>http://trustee.ietf.org/policyandprocedures.html
>
>All feedback submitted before the end of February 7th will be considered by
>the Trustees.  A decision on whether to move forward with this proposal will
>be made and communicated to you before the end of February 15th.
>
>Please give this your attention.
>
>Regards and Happy New Year !
>
>Ed Juskevicius, on behalf of the IETF Trustees
>edj.etc@gmail.com



--------------010005040909090207050901
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--------------010005040909090207050901--


From pwe3-bounces@ietf.org  Fri Jan 16 11:00:02 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6BC7B3A6A7A;
	Fri, 16 Jan 2009 11:00:02 -0800 (PST)
X-Original-To: pwe3@ietf.org
Delivered-To: pwe3@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 75D223A6A7A; Fri, 16 Jan 2009 11:00:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090116190001.75D223A6A7A@core3.amsl.com>
Date: Fri, 16 Jan 2009 11:00:01 -0800 (PST)
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-fc-encap-09.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Pseudowire Emulation Edge to Edge Working Group of the IETF.

	Title		: Encapsulation Methods for Transport of Fibre Channel frames Over MPLS Networks
	Author(s)	: M. Roth, M. Tsurusawa, R. Solomon, D. Zelig
	Filename	: draft-ietf-pwe3-fc-encap-09.txt
	Pages		: 17
	Date		: 2009-1-16
	
A Fibre Channel pseudowire (PW) is used to carry Fibre Channel frames 
   over an MPLS network. This enables service providers to offer 
   "emulated" Fibre Channel services over existing MPLS networks. This 
   document specifies the encapsulation of Fibre Channel PDUs within a 
   pseudowire. It also specifies the common procedures for using a PW to 
   provide a Fibre Channel service. The mechanisms controlling the 
   reliable transport of Fibre Channel PW over MPLS networks are 
   specified in a companion document [FC-flow].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-fc-encap-09.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-pwe3-fc-encap-09.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-1-16105402.I-D@ietf.org>


--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--




From pwe3-bounces@ietf.org  Wed Jan 21 03:06:25 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 206373A6AD3; Wed, 21 Jan 2009 03:06:25 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EDEDF3A697A; Wed, 21 Jan 2009 03:06:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35]
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 SGhbuqH2HQC3; Wed, 21 Jan 2009 03:06:23 -0800 (PST)
Received: from ns.elverljung.se (ns.elverljung.se [194.68.48.116]) by core3.amsl.com (Postfix) with ESMTP id 21CAE3A68D2; Wed, 21 Jan 2009 03:06:22 -0800 (PST)
Received: from [10.96.0.175] (unknown [217.39.1.131]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa) by ns.elverljung.se (Postfix) with ESMTPSA id 058052D805D; Wed, 21 Jan 2009 12:06:03 +0100 (CET)
Message-ID: <49770193.5080109@pi.nu>
Date: Wed, 21 Jan 2009 12:05:55 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: mpls-tp@ietf.org, mpls@ietf.org, pwe3@ietf.org, ccamp@ietf.org,  ahtmpls@itu.int
References: <49647EB3.1090603@pi.nu>
In-Reply-To: <49647EB3.1090603@pi.nu>
Cc: George Swallow <swallow@cisco.com>, Matthew Bocci <Matthew.Bocci@alcatel-lucent.com>, ahmpls-tp@lists.itu.int, David Ward <dward@cisco.com>, Malcolm Betts <betts01@nortel.com>, Deborah Brungard <dbrungard@att.com>, Stewart Bryant <stbryant@cisco.com>
Subject: Re: [PWE3] Working Group Last Call on draft-ietf-mpls-tp-gach-gal-01
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org All,

this wg last call has terminated.

What will happen now is that we will receive consolidated comments
from the ITU-T MPLS-TP ad hoc team, we've been promised that we will
those comments "within a few days".

Once we received those comment could the editors/authors please
prepare responses to all comments and re-spin the draft.

/Loa

Loa Andersson wrote:
> All,
> 
> this is to initiate a working group last call on
> http://tools.ietf.org/html/draft-ietf-mpls-tp-gach-gal-01
> 
> This is the first of a series MPLS Transport Profile documents
> to be last called. The last call is directed to the MPLS, PWE3
> and CCAMP working groups.
> 
> According to procedures agreed upon in the JWT decision the
> working last call does also include the ITU-T MPLS-TP ad hoc team.
> 
> This working group last call will end eob Jan 20, 2009.
> 
> Though I know this is futile:
> 
> *Please do not do a "Replay all"* but direct comments to the
> mpls-tp@ietf.org mailing list.
> 
> /Loa
> 

-- 


Loa Andersson

Sr Strategy and Standards Manager
Ericsson ///                          phone:  +46 8 632 77 14

                                       email:  loa.andersson@ericsson.com
                                               loa.andersson@redback.com
                                               loa@pi.nu


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

From pwe3-bounces@ietf.org  Wed Jan 21 15:02:27 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6226E3A69EC; Wed, 21 Jan 2009 15:02:27 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 85AE628C12A; Wed, 21 Jan 2009 05:45:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.549
X-Spam-Level: 
X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 aE+qOs58FQny; Wed, 21 Jan 2009 05:44:59 -0800 (PST)
Received: from zcars04f.nortel.com (zcars04f.nortel.com [47.129.242.57]) by core3.amsl.com (Postfix) with ESMTP id 30DA23A6AC5; Wed, 21 Jan 2009 05:44:59 -0800 (PST)
Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com [47.129.230.99]) by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n0LDi0R16876; Wed, 21 Jan 2009 13:44:00 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 21 Jan 2009 08:43:59 -0500
Message-ID: <0BDFFF51DC89434FA33F8B37FCE363D515C6B1E6@zcarhxm2.corp.nortel.com>
In-Reply-To: <49770193.5080109@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] Working Group Last Call on draft-ietf-mpls-tp-gach-gal-01
Thread-Index: Acl7uEe2mfZGWDltQ1WvvNQtY/xRMAAFAI1A
References: <49647EB3.1090603@pi.nu> <49770193.5080109@pi.nu>
From: "Malcolm Betts" <betts01@nortel.com>
To: "Loa Andersson" <loa@pi.nu>, <mpls-tp@ietf.org>, <mpls@ietf.org>, <pwe3@ietf.org>, <ccamp@ietf.org>, <ahtmpls@itu.int>
X-Mailman-Approved-At: Wed, 21 Jan 2009 15:02:25 -0800
Cc: George Swallow <swallow@cisco.com>, Matthew Bocci <Matthew.Bocci@alcatel-lucent.com>, ahmpls-tp@lists.itu.int, David Ward <dward@cisco.com>, Deborah Brungard <dbrungard@att.com>, Stewart Bryant <stbryant@cisco.com>
Subject: Re: [PWE3] Working Group Last Call on draft-ietf-mpls-tp-gach-gal-01
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org Loa, the comments on the ITU lists have also been submitted on the
mpls-tp@ietf.org list.  I have not seen any suggestions that the ITU-T
needs to provide any formal comments on this draft.  Clearly the
comments should be addressed before the draft is approved.  

Since you have indicated that the draft will be respun, and I assume you
will initiate a new last call, I do not see a need for the ITU to send a
formal liaison in response your request to review this draft.


Malcolm Betts
co chair Ad Hoc group on MPLS-TP
Phone: +1 613 763 7860 (ESN 393)
email: betts01@nortel.com

-----Original Message-----
From: Loa Andersson [mailto:loa@pi.nu] 
Sent: Wednesday, January 21, 2009 6:06 AM
To: mpls-tp@ietf.org; mpls@ietf.org; pwe3@ietf.org; ccamp@ietf.org;
ahtmpls@itu.int
Cc: George Swallow; Matthew Bocci; David Ward; Betts, Malcolm
(CAR:X632); Deborah Brungard; Stewart Bryant; ahmpls-tp@lists.itu.int
Subject: Re: [PWE3] Working Group Last Call on
draft-ietf-mpls-tp-gach-gal-01

All,

this wg last call has terminated.

What will happen now is that we will receive consolidated comments from
the ITU-T MPLS-TP ad hoc team, we've been promised that we will those
comments "within a few days".

Once we received those comment could the editors/authors please prepare
responses to all comments and re-spin the draft.

/Loa

Loa Andersson wrote:
> All,
> 
> this is to initiate a working group last call on
> http://tools.ietf.org/html/draft-ietf-mpls-tp-gach-gal-01
> 
> This is the first of a series MPLS Transport Profile documents to be 
> last called. The last call is directed to the MPLS, PWE3 and CCAMP 
> working groups.
> 
> According to procedures agreed upon in the JWT decision the working 
> last call does also include the ITU-T MPLS-TP ad hoc team.
> 
> This working group last call will end eob Jan 20, 2009.
> 
> Though I know this is futile:
> 
> *Please do not do a "Replay all"* but direct comments to the 
> mpls-tp@ietf.org mailing list.
> 
> /Loa
> 

-- 


Loa Andersson

Sr Strategy and Standards Manager
Ericsson ///                          phone:  +46 8 632 77 14

                                       email:
loa.andersson@ericsson.com
                                               loa.andersson@redback.com
                                               loa@pi.nu


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

From pwe3-bounces@ietf.org  Mon Jan 26 05:42:46 2009
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ED52728C206; Mon, 26 Jan 2009 05:42:45 -0800 (PST)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4709028C206 for <pwe3@core3.amsl.com>; Mon, 26 Jan 2009 05:42:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.387
X-Spam-Level: 
X-Spam-Status: No, score=-2.387 tagged_above=-999 required=5 tests=[AWL=-0.138, BAYES_00=-2.599, HELO_EQ_SE=0.35]
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 Qr2q3Qs7UGr9 for <pwe3@core3.amsl.com>; Mon, 26 Jan 2009 05:42:45 -0800 (PST)
Received: from ns.elverljung.se (ns.elverljung.se [194.68.48.116]) by core3.amsl.com (Postfix) with ESMTP id 04D1028C202 for <pwe3@ietf.org>; Mon, 26 Jan 2009 05:42:45 -0800 (PST)
Received: from [192.36.158.123] (wdhcp-158-123.verkstad.net [192.36.158.123]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa) by ns.elverljung.se (Postfix) with ESMTPSA id 7167E2D812C for <pwe3@ietf.org>; Mon, 26 Jan 2009 14:42:26 +0100 (CET)
Message-ID: <497DBDC1.5010509@pi.nu>
Date: Mon, 26 Jan 2009 14:42:25 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: pwe3@ietf.org
Subject: [PWE3] the mpls-tp mailing list is the consensus list for mpls-tp isseus
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

All,

we have agreed with our ADs that the mpl-tp@ietf.org shall be used
as the consensus list for mpls-tp related drafts and issues.

We will still send generic announcements lie this one or working
group last cal to the relevant working group mailing lists, but the
discussions should be taken to the mpls-tp list. (Cross-) working
group consensus will be decided based on the discussion on the
mpls-tp list.

/Loa
-- 


Loa Andersson

Sr Strategy and Standards Manager
Ericsson ///                          phone:  +46 8 632 77 14

                                       email:  loa.andersson@ericsson.com
                                               loa.andersson@redback.com
                                               loa@pi.nu


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