From pwe3-bounces@ietf.org Sun Jul 01 01:22:26 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4rt1-0007ib-FC; Sun, 01 Jul 2007 01:22:15 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I4rsz-0007g7-JX
	for pwe3-confirm+ok@megatron.ietf.org; Sun, 01 Jul 2007 01:22:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4rsz-0007fO-5L
	for pwe3@ietf.org; Sun, 01 Jul 2007 01:22:13 -0400
Received: from mx2-012.rad.co.il ([212.199.240.16] helo=antivir2.rad.co.il)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4rsB-0002Mb-Ur
	for pwe3@ietf.org; Sun, 01 Jul 2007 01:22:13 -0400
Received: from exrad3.rad.co.il (HELO exrad3.ad.rad.co.il) ([192.114.24.112])
	by antivir2.rad.co.il with ESMTP; 01 Jul 2007 08:21:21 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] New Liaison Statement,
	"Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1"
Date: Sun, 1 Jul 2007 08:21:20 +0300
Message-ID: <457D36D9D89B5B47BC06DA869B1C815D04662331@exrad3.ad.rad.co.il>
In-Reply-To: <2ECAA42C79676B42AEBAC11229CA7D0CA2908F@E03MVB2-UKBR.domain1.systemhost.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] New Liaison Statement,
	"Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1"
Thread-Index: Ace4K+PmizzvDV9GRKSw6RIcLy6tAQBHbfSgAABSjsAAlPqlMA==
From: "Yaakov Stein" <yaakov_s@rad.com>
To: <neil.2.harrison@bt.com>,
	<pwe3@ietf.org>,
	<mpls@lists.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: stbryant@cisco.com
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Neil,=20

Yes, I quite agree that there can be client-server relationships (either
way).

What I want is a clear statement that there can be no peer relationship.

Sasha's comment on separate Ethertypes is, of course, a good solution,
but we need to state the requirement first and then give this as one
possible solution.
BTW, we have requested this several times already.

BTW

-----Original Message-----
From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]=20
Sent: Thursday, June 28, 2007 09:27
To: Yaakov Stein
Cc: stbryant@cisco.com
Subject: RE: [PWE3] New Liaison Statement,"Response to PWE3 and MPLS WG
concerns with G.8110.1 Amendment 1"

Hi Yaakov,

Good point...a key corollary of which IMO is that T-MPLS cannot be
claimed to be a sub-set of MPLS.....so one could call T-MPLS anything
one likes now....indeed, perhaps IETF should request this of ITU to
avoid any confusion?

However, whilst I accept there should be no attempt at interworking MPLS
and T-MPLS as though they were peers (essentially the horizontal
partitioning of what looks like a single layer network...so I agree this
needs clearly stating) there ought to be some clarification of what
client/server relationships are intended (if any?) to exist between MPLS
and T-MPLS (both ways, ie MPLSoT-MPLS and T-MPLSoMPLS).

regards, Neil


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



From pwe3-bounces@ietf.org Sun Jul 01 01:29:16 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4rzn-0004pK-I9; Sun, 01 Jul 2007 01:29:15 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I4rzm-0004oz-Bv
	for pwe3-confirm+ok@megatron.ietf.org; Sun, 01 Jul 2007 01:29:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4rzm-0004or-1G
	for pwe3@ietf.org; Sun, 01 Jul 2007 01:29:14 -0400
Received: from mx2-n.rad.co.il ([62.0.23.221] helo=antivir2.rad.co.il)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4rzC-0005ow-JX
	for pwe3@ietf.org; Sun, 01 Jul 2007 01:29:14 -0400
Received: from exrad3.rad.co.il (HELO exrad3.ad.rad.co.il) ([192.114.24.112])
	by antivir2.rad.co.il with ESMTP; 01 Jul 2007 08:28:36 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mpls] RE: [PWE3] New Liaison Statement,
	"Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1"
Date: Sun, 1 Jul 2007 08:28:35 +0300
Message-ID: <457D36D9D89B5B47BC06DA869B1C815D04662341@exrad3.ad.rad.co.il>
In-Reply-To: <390CD596-7947-44E3-8735-3D9D62AA7919@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] RE: [PWE3] New Liaison Statement,
	"Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1"
Thread-Index: Ace6gpevgOMYo4ECRbyXmfH0HVBczQBHTHXA
From: "Yaakov Stein" <yaakov_s@rad.com>
To: "Phil Bedard" <bedard.phil@gmail.com>,
	"Sasha Vainshtein" <Sasha@AXERRA.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: mpls@lists.ietf.org, Italo Busi <Italo.Busi@alcatel-lucent.it>,
	pwe3@ietf.org, stbryant@cisco.com
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Phil,=20

There are several types of interworking.

"Nework interworking" or "client-server" interworking means carrying one
network layer over another. See all the ITU Y.14xx Recommendations for
further explanations.

"Service interworking" or "peer to peer interworking" means passing the
payload information
between two different network technologies.

The documents being presented claim that T-MPLS is a different network
technology
from IETF-defined MPLS (or what they call IP-MPLS). Different needn't
mean incompatible
formats, it is enough for one to be a strict subset of the other (e.g
disallow certain
features). In this case interworking (of one type or the other) needs to
be defined.
Those proposing T-MPLS are claiming that interworking need not be
defined
as they assume that there are no use cases for this. (I disagree)

Y(J)S


-----Original Message-----
From: Phil Bedard [mailto:bedard.phil@gmail.com]=20
Sent: Friday, June 29, 2007 22:21
To: Sasha Vainshtein
Cc: Italo Busi; mpls@lists.ietf.org; Yaakov Stein; pwe3@ietf.org;
stbryant@cisco.com
Subject: Re: [mpls] RE: [PWE3] New Liaison Statement, "Response to PWE3
and MPLS WG concerns with G.8110.1 Amendment 1"

Excuse me if this has already been covered, I've just read some of the
current messages and to me it seems the definition of =20
"interworking" needs to be better defined in these discussions.   To =20
me interworking is a translation function on the same data plane, not =20
one framing technology encapsulating another.   The connection-=20
oriented specifications of T-MPLS seem to not allow its frames to be
translated and carried on an IP/MPLS network without special =20
treatment, unless I'm mistaken.   So there really isn't =20
"interworking".    The fact they use the same forwarding plane, =20
packet format, and codepoints seems to confuse things.   If they are =20
truly distinct protocols that serve different purposes, as the T-MPLS
advocates seem to say, then clear separation needs to be made between
the two.

Phil


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



From pwe3-bounces@ietf.org Mon Jul 02 11:01:34 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5NP0-0007Sq-TD; Mon, 02 Jul 2007 11:01:22 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I5NOy-0007ST-3M
	for pwe3-confirm+ok@megatron.ietf.org; Mon, 02 Jul 2007 11:01:20 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5NOx-0007SD-N2
	for pwe3@ietf.org; Mon, 02 Jul 2007 11:01:19 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I5NOx-0004H0-9G
	for pwe3@ietf.org; Mon, 02 Jul 2007 11:01:19 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 02 Jul 2007 11:00:54 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAJKviEZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,487,1175486400"; 
	d="scan'208"; a="64169488:sNHT71832106"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l62F0sMi006402; 
	Mon, 2 Jul 2007 11:00:54 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l62F0cs0029796; 
	Mon, 2 Jul 2007 15:00:45 GMT
Received: from xmb-rtp-203.amer.cisco.com ([64.102.31.20]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 2 Jul 2007 11:00:38 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mpls] RE: [PWE3] New Liaison Statement,
	"Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1"
Date: Mon, 2 Jul 2007 11:00:37 -0400
Message-ID: <829173BE40A7F147AC51726688B0374B03158A0F@xmb-rtp-203.amer.cisco.com>
In-Reply-To: <457D36D9D89B5B47BC06DA869B1C815D04662341@exrad3.ad.rad.co.il>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] RE: [PWE3] New Liaison Statement,
	"Response to PWE3 and MPLS WG concerns with G.8110.1 Amendment 1"
Thread-Index: Ace6gpevgOMYo4ECRbyXmfH0HVBczQBHTHXAAEZTuKA=
From: "Kyung-Yeop Hong \(hongk\)" <hongk@cisco.com>
To: "Yaakov Stein" <yaakov_s@rad.com>, "Phil Bedard" <bedard.phil@gmail.com>, 
	"Sasha Vainshtein" <Sasha@AXERRA.com>
X-OriginalArrivalTime: 02 Jul 2007 15:00:38.0911 (UTC)
	FILETIME=[C091F0F0:01C7BCB9]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4180; t=1183388454;
	x=1184252454; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=hongk@cisco.com;
	z=From:=20=22Kyung-Yeop=20Hong=20\(hongk\)=22=20<hongk@cisco.com>
	|Subject:=20RE=3A=20[mpls]=20RE=3A=20[PWE3]=20New=20Liaison=20Statement,
	=
	22Response=20to=20PWE3=20and=20MPLS=20WG=20concerns=20with=20G.8110.1=20Am
	endment=201=22 |Sender:=20
	|To:=20=22Yaakov=20Stein=22=20<yaakov_s@rad.com>,
	=20=22Phil=20Bedard=22=2 0<bedard.phil@gmail.com>,
	=0A=20=20=20=20=20=20=20=20=22Sasha=20Vainshtein=
	22=20<Sasha@AXERRA.com>;
	bh=PuJnbys47R1y6aD1uCxY4wBcV0oajq2sbXWskE5cVC0=;
	b=dVcIF1zSL9ZkHYWjVQkZp1ksAIPouLqeImpDbvfvcaKM/e/CO6pjTt7WWZFq1FklY8tMnA7C
	7DGya5eE4s7marybIGKAnVZmZtDzuRP/rTI/gPpFbr85VX8nQagTxjLv;
Authentication-Results: rtp-dkim-2; header.From=hongk@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Cc: mpls@lists.ietf.org, Italo Busi <Italo.Busi@alcatel-lucent.it>,
	pwe3@ietf.org, "Stewart Bryant \(stbryant\)" <stbryant@cisco.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Yaakov, Phil, Stewart et al,

In the Scope section of the previously approved G.8110.1 (T-MPLS
architecture), it was stated:
"Further a T-MPLS network will not peer directly with an IP/MPLS
network".
(I think this implies that T-MPLS does not support service interworking
with IP/MPLS)

At the last Q12/15 meeting, they modified the above sentence in the
Scope section as follows:
"Further a T-MPLS network will have a client/server relationship with an
IP/MPLS network".
(I think this implies that T-MPLS may support network interworking with
IP/MPLS, although I am not sure about what "will" means in the context
of Rec)

Those proposing T-MPLS proposed "IP/MPLS and T-MPLS Interoperability" at
the last meeting and following is the meeting report FYI:
"Contribution C595, (Alcatel-Lucent), "IP/MPLS and T-MPLS
Interoperability" raised some concerns.  It was noted that we have
agreed that we do not expect IP/MPLS and T-MPLS to directly
interoperate.  It was clarified that the contributions addresses use of
a Pseudowire that spans a MPLS and a T-MPLS network.  I was noted that
Q7/13 has responsibility for PW interworking.  It was suggested that the
intent was that the T-MPLS network would encapsulate the MPLS PW.
Further clarification of the network application is required before any
action can be taken."

It seems like the intent was the network interworking, but then Q7/13
has responsibility for PW interworking as written in the report. We must
be very clear about their scope and requirements of T-MPLS (in
particular for interworking, interoperability, etc).

- KY

-----Original Message-----
From: Yaakov Stein [mailto:yaakov_s@rad.com]=20
Sent: Sunday, July 01, 2007 1:29 AM
To: Phil Bedard; Sasha Vainshtein
Cc: mpls@lists.ietf.org; Italo Busi; pwe3@ietf.org; Stewart Bryant
(stbryant)
Subject: RE: [mpls] RE: [PWE3] New Liaison Statement,"Response to PWE3
and MPLS WG concerns with G.8110.1 Amendment 1"

Phil,=20

There are several types of interworking.

"Nework interworking" or "client-server" interworking means carrying one
network layer over another. See all the ITU Y.14xx Recommendations for
further explanations.

"Service interworking" or "peer to peer interworking" means passing the
payload information
between two different network technologies.

The documents being presented claim that T-MPLS is a different network
technology
from IETF-defined MPLS (or what they call IP-MPLS). Different needn't
mean incompatible
formats, it is enough for one to be a strict subset of the other (e.g
disallow certain
features). In this case interworking (of one type or the other) needs to
be defined.
Those proposing T-MPLS are claiming that interworking need not be
defined
as they assume that there are no use cases for this. (I disagree)

Y(J)S


-----Original Message-----
From: Phil Bedard [mailto:bedard.phil@gmail.com]=20
Sent: Friday, June 29, 2007 22:21
To: Sasha Vainshtein
Cc: Italo Busi; mpls@lists.ietf.org; Yaakov Stein; pwe3@ietf.org;
stbryant@cisco.com
Subject: Re: [mpls] RE: [PWE3] New Liaison Statement, "Response to PWE3
and MPLS WG concerns with G.8110.1 Amendment 1"

Excuse me if this has already been covered, I've just read some of the
current messages and to me it seems the definition of =20
"interworking" needs to be better defined in these discussions.   To =20
me interworking is a translation function on the same data plane, not =20
one framing technology encapsulating another.   The connection-=20
oriented specifications of T-MPLS seem to not allow its frames to be
translated and carried on an IP/MPLS network without special =20
treatment, unless I'm mistaken.   So there really isn't =20
"interworking".    The fact they use the same forwarding plane, =20
packet format, and codepoints seems to confuse things.   If they are =20
truly distinct protocols that serve different purposes, as the T-MPLS
advocates seem to say, then clear separation needs to be made between
the two.

Phil


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


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



From pwe3-bounces@ietf.org Tue Jul 03 19:15:15 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5raT-0000Tp-Hb; Tue, 03 Jul 2007 19:15:13 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I5raQ-0000Dt-0a
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 19:15:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5raP-0000CQ-MT; Tue, 03 Jul 2007 19:15:09 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I5raH-0002Gu-QM; Tue, 03 Jul 2007 19:15:09 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id A726826EC6;
	Tue,  3 Jul 2007 23:15:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I5raH-0000xx-Iv; Tue, 03 Jul 2007 19:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I5raH-0000xx-Iv@stiedprstage1.ietf.org>
Date: Tue, 03 Jul 2007 19:15:01 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-segmented-pw-05.txt 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
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		: Segmented Pseudo Wire
	Author(s)	: L. Martini, et al.
	Filename	: draft-ietf-pwe3-segmented-pw-05.txt
	Pages		: 38
	Date		: 2007-7-3
	
This document describes how to connect pseudo wires (PW) between two
   distinct PW control planes or PSN domains. The PW control planes may
   belong to independent autonomous systems, or the PSN technology is
   heterogeneous, or a PW might need to be aggregated at a specific PSN
   point. The PW packet data units are simply switched from one PW to
   another without changing the PW payload.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-segmented-pw-05.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-pwe3-segmented-pw-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pwe3-segmented-pw-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-7-3181204.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-segmented-pw-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pwe3-segmented-pw-05.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-7-3181204.I-D@ietf.org>


--OtherAccess--

--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://www1.ietf.org/mailman/listinfo/pwe3

--NextPart--





From pwe3-bounces@ietf.org Tue Jul 03 19:15:47 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5rb1-0002oq-CH; Tue, 03 Jul 2007 19:15:47 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I5ran-00022S-6c
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 19:15:33 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5ram-0001xB-F2; Tue, 03 Jul 2007 19:15:32 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I5ram-00032U-8A; Tue, 03 Jul 2007 19:15:32 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id ED9FB175AA;
	Tue,  3 Jul 2007 23:15:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I5raH-0000xv-IH; Tue, 03 Jul 2007 19:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I5raH-0000xv-IH@stiedprstage1.ietf.org>
Date: Tue, 03 Jul 2007 19:15:01 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-dynamic-ms-pw-04.txt 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
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		: Dynamic Placement of Multi Segment Pseudo Wires
	Author(s)	: F. Balus, et al.
	Filename	: draft-ietf-pwe3-dynamic-ms-pw-04.txt
	Pages		: 21
	Date		: 2007-7-3
	
There is a requirement for service providers to be able to extend the
   reach of pseudo wires (PW) across multiple Packet Switched Network
   domains. A Multi-Segment PW is defined as a set of two or more
   contiguous PW segments that behave and function as a single point-
   to-point PW. This document describes extensions to the PW control
   protocol to dynamically place the segments of the multi segment
   pseudo wire among a set of Provider Edge (PE) routers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-dynamic-ms-pw-04.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-pwe3-dynamic-ms-pw-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pwe3-dynamic-ms-pw-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-7-3180018.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-dynamic-ms-pw-04.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pwe3-dynamic-ms-pw-04.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-7-3180018.I-D@ietf.org>


--OtherAccess--

--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://www1.ietf.org/mailman/listinfo/pwe3

--NextPart--





From pwe3-bounces@ietf.org Thu Jul 05 11:53:11 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6TPo-0006d4-8e; Thu, 05 Jul 2007 11:38:44 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I6TPc-0006ZX-B4
	for pwe3-confirm+ok@megatron.ietf.org; Thu, 05 Jul 2007 11:38:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6TPb-0006XQ-5W; Thu, 05 Jul 2007 11:38:31 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I6THO-0000Ro-BW; Thu, 05 Jul 2007 11:30:58 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 4137626E63;
	Thu,  5 Jul 2007 15:30:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I6THO-0001IW-5d; Thu, 05 Jul 2007 11:30:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I6THO-0001IW-5d@stiedprstage1.ietf.org>
Date: Thu, 05 Jul 2007 11:30:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: pwe3@ietf.org
Subject: [PWE3] I-D Action:draft-ietf-pwe3-vccv-14.txt 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
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           : Pseudowire Virtual Circuit Connectivity Verification (VCCV) A Control Channel for Pseudowires
        Author(s)       : T. Nadeau, C. Pignataro
        Filename        : draft-ietf-pwe3-vccv-14.txt
        Pages           : 30
        Date            : 2007-07-05
                                                                                           
This document describes Virtual Circuit Connection Verification
(VCCV) which provides a control channel that is associated with a
Pseudowire (PW), as well as the corresponding operations and
management functions such as connectivity verification to be used
over that control channel.  VCCV applies to all supported access
circuit and transport types currently defined for PWs.
                                                                                           
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-vccv-14.txt
                                                                                           
To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.
                                                                                           
                                                                                           
Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
        "get draft-ietf-pwe3-vccv-14.txt".
                                                                                           
A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
                                                                                           
                                                                                           
Internet-Drafts can also be obtained by e-mail.
                                                                                           
Send a message to:
        mailserv@ietf.org.
In the body type:
        "FILE /internet-drafts/draft-ietf-pwe3-vccv-14.txt".
                                                                                           
NOTE:   The mail server at ietf.org can return the document in
        MIME-encoded form by using the "mpack" utility.  To use this
        feature, insert the command "ENCODING mime" before the "FILE"
        command.  To decode the response(s), you will need "munpack" or
        a MIME-compliant mail reader.  Different MIME-compliant mail readers
        exhibit different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have been split
        up into multiple messages), so check your local documentation on
        how to manipulate these messages.
                                                                                           
                                                                                           
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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"
Content-Type: text/plain
Content-ID: <2007-07-05112122.I-D@ietf.org>


ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-vccv-14.txt
                                                                                           
--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-pwe3-vccv-14.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"
Content-Type: text/plain
Content-ID: <2007-07-05112122.I-D\@ietf.org>



--OtherAccess--
                                                                                           
--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://www1.ietf.org/mailman/listinfo/pwe3

--NextPart--





From pwe3-bounces@ietf.org Thu Jul 05 17:15:18 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6YfU-0004dr-T8; Thu, 05 Jul 2007 17:15:16 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I6YfR-0004XP-2J
	for pwe3-confirm+ok@megatron.ietf.org; Thu, 05 Jul 2007 17:15:13 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6YfQ-0004XH-Mq; Thu, 05 Jul 2007 17:15:12 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I6YfQ-0003mk-Et; Thu, 05 Jul 2007 17:15:12 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 4D6732AC9C;
	Thu,  5 Jul 2007 21:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I6YfF-0004N5-Ui; Thu, 05 Jul 2007 17:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I6YfF-0004N5-Ui@stiedprstage1.ietf.org>
Date: Thu, 05 Jul 2007 17:15:01 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-dynamic-ms-pw-05.txt 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
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		: Dynamic Placement of Multi Segment Pseudo 
                          Wires
	Author(s)	: F. Balus, et al.
	Filename	: draft-ietf-pwe3-dynamic-ms-pw-05.txt
	Pages		: 21
	Date		: 2007-7-5
	
There is a requirement for service providers to be able to extend the
   reach of pseudo wires (PW) across multiple Packet Switched Network
   domains. A Multi-Segment PW is defined as a set of two or more
   contiguous PW segments that behave and function as a single point-
   to-point PW. This document describes extensions to the PW control
   protocol to dynamically place the segments of the multi segment
   pseudo wire among a set of Provider Edge (PE) routers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-dynamic-ms-pw-05.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-pwe3-dynamic-ms-pw-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pwe3-dynamic-ms-pw-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-7-5163145.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-dynamic-ms-pw-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pwe3-dynamic-ms-pw-05.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-7-5163145.I-D@ietf.org>


--OtherAccess--

--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://www1.ietf.org/mailman/listinfo/pwe3

--NextPart--





From pwe3-bounces@ietf.org Thu Jul 05 21:10:01 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6cKe-0006XF-Ru; Thu, 05 Jul 2007 21:10:00 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I6cKd-0006X7-Bn
	for pwe3-confirm+ok@megatron.ietf.org; Thu, 05 Jul 2007 21:09:59 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6cKc-0006Wx-Vu
	for pwe3@ietf.org; Thu, 05 Jul 2007 21:09:59 -0400
Received: from mail.ruijie.com.cn ([61.233.3.220])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6cKc-0005F1-71
	for pwe3@ietf.org; Thu, 05 Jul 2007 21:09:58 -0400
To: pwe3@ietf.org
Subject: [PWE3] I have two question about the Generalized PWid FEC Element in
	RFC4762 =?GB2312?B?oaM=?=
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.1 January 17, 2006
From: chenxb@ruijie.com.cn
Message-ID: <OFDE02EF4C.C2652EC6-ON88257310.0058C069-88257310.00590568@ruijie.com.cn>
Date: Thu, 5 Jul 2007 18:06:53 -0700
X-MIMETrack: Serialize by Router on mailserver/ruijie(Release 6.5.4FP3|January
	09, 2006) at 2007-07-06 09:07:27,
	Serialize complete at 2007-07-06 09:07:27
X-Spam-Score: 0.4 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1591621637=="
Errors-To: pwe3-bounces@ietf.org

This is a multipart message in MIME format.
--===============1591621637==
Content-Type: multipart/alternative;
	boundary="=_alternative 0058D75288257310_="

This is a multipart message in MIME format.
--=_alternative 0058D75288257310_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

SGkgYWxsLA0KDQpJIGhhdmUgdHdvIHF1ZXN0aW9uIGFib3V0IHRoZSBHZW5lcmFsaXplZCBQV2lk
IEZFQyBFbGVtZW50IGluIFJGQzQ3NjKhow0KDQpUaGUgZmlyc3QgcXVlc3Rpb246DQogDQpTZWN0
aW9uIDYuMS4xIGluICBSRkMgNDc2MiBzYXk6DQogICBUYXJnZXQgQXR0YWNobWVudCBJbmRpdmlk
dWFsIElkZW50aWZpZXIgKFRBSUkpLCBTb3VyY2UgQXR0YWNobWVudCANCiAgIEluZGl2aWR1YWwg
SWRlbnRpZmllciAoU0FJSSk6IFRoZXNlIGFyZSBudWxsIGJlY2F1c2UgdGhlIG1lc2ggb2YgUFdz
IA0KICAgaW4gYSBWUExTIHRlcm1pbmF0ZXMgb24gTUFDIGxlYXJuaW5nIHRhYmxlcywgcmF0aGVy
IHRoYW4gb24NCiAgIGluZGl2aWR1YWwgYXR0YWNobWVudCBjaXJjdWl0cy4gIFRoZSB1c2Ugb2Yg
bm9uLW51bGwgVEFJSSBhbmQgU0FJSSBpcw0KICAgcmVzZXJ2ZWQgZm9yIGZ1dHVyZSBlbmhhbmNl
bWVudHMuDQogDQoNCk15IHF1ZXN0aW9uIGlzICwNCndoYXQgZG9zZSB0aGlzIHN0YXRlbWVudCBt
ZWFuPw0Kd2hldGhlciBtZWFucyB0aGF0IFRBSUkgYW5kIFNBSUkgaXMgbm90IHByZXNlbnQgb3Ig
DQptZWFucyB0aGF0IFRBSUkgYW5kIFNBSUkgaXMgcHJlc2VudCBidXQgTGVuZ3RoIGZpZWxkIHZh
bHVlIGlzIHplcm8/DQppZiBpdCdzIHRoZSBsYXR0ZXIsIHdoYXQncyB0aGUgIFRBSUkgYW5kIFNB
SUkgVHlwZSBmaWVsZCB2YWx1ZT8NCmlmIGl0J3MgdGhlIGZvcm1lciwgaXQgc2VlbXMgdG8gY29u
ZmxpY3Qgd2l0aCBSRkMgNDQ0NyBzZWN0aW9uIDUuMy4yLg0KYmVjYXVzZSBpbiBSRkMgNDQ0NyBz
ZWNpb24gNS4zLjIgc2F5LA0KICAgSWYgYSBwYXJ0aWN1bGFyIGFwcGxpY2F0aW9uIGRvZXMgbm90
IG5lZWQgYWxsIHRocmVlIG9mIHRoZXNlIA0Kc3ViLWVsZW1lbnRzLCBpdCBNVVNUDQogICBzZW5k
IGFsbCB0aGUgc3ViLWVsZW1lbnRzIGJ1dCBzZXQgdGhlIGxlbmd0aCB0byAwIGZvciB0aGUgdW51
c2VkDQogICBzdWItZWxlbWVudHMuDQoNCg0KVGhlIHNlY29uZCBxdWVzdGlvbjoNClNlY3Rpb24g
Ni4xLjEgaW4gIFJGQyA0NzYyIHNheToNCiAgIEF0dGFjaG1lbnQgR3JvdXAgSWRlbnRpZmllciAo
QUdJKSwgTGVuZ3RoLCBWYWx1ZTogVGhlIHVuaXF1ZSBuYW1lIG9mDQogICB0aGlzIFZQTFMuICBU
aGUgQUdJIGlkZW50aWZpZXMgYSB0eXBlIG9mIG5hbWUsIGFuZCBMZW5ndGggZGVub3RlcyB0aGUN
CiAgIGxlbmd0aCBvZiBWYWx1ZSwgd2hpY2ggaXMgdGhlIG5hbWUgb2YgdGhlIFZQTFMuICBXZSB1
c2UgdGhlIHRlcm0gQUdJDQogICBpbnRlcmNoYW5nZWFibHkgd2l0aCBWUExTIGlkZW50aWZpZXIu
DQoNCk15IHF1ZXN0aW9uIGlzLA0Kd2hhdCdzIHRoZSBBR0kgVHlwZSBmaWxlZCB2YWx1ZSB0aGF0
IGluZGljYXRlZCB0aGUgQUdJIHZhbHVlIGlzIFZQTFMgbmFtZT8NCg0KDQpUaGFua3MgYW5kIFJl
Z2FyZHMNCkplcnJ5IGtpbmcNCg0K
--=_alternative 0058D75288257310_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkhpIGFsbCw8L2ZvbnQ+
DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkkgaGF2ZSB0d28gcXVl
c3Rpb24gYWJvdXQgPGI+dGhlIEdlbmVyYWxpemVkDQpQV2lkIEZFQyBFbGVtZW50IDwvYj5pbiBS
RkM0NzYyoaM8L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYi
PlRoZSBmaXJzdCBxdWVzdGlvbjo8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMt
c2VyaWYiPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyA8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6
ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlNlY3Rpb24gNi4xLjEgaW4gJm5ic3A7UkZDIDQ3NjIgc2F5
OjwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNw
O1RhcmdldCBBdHRhY2htZW50IEluZGl2aWR1YWwNCklkZW50aWZpZXIgKFRBSUkpLCBTb3VyY2Ug
QXR0YWNobWVudCAmbmJzcDsgJm5ic3A7PC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJz
YW5zLXNlcmlmIj4mbmJzcDsgJm5ic3A7SW5kaXZpZHVhbCBJZGVudGlmaWVyIChTQUlJKToNClRo
ZXNlIGFyZSBudWxsIGJlY2F1c2UgdGhlIG1lc2ggb2YgUFdzICZuYnNwOzwvZm9udD4NCjxicj48
Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwO2luIGEgVlBMUyB0ZXJt
aW5hdGVzIG9uDQpNQUMgbGVhcm5pbmcgdGFibGVzLCByYXRoZXIgdGhhbiBvbjwvZm9udD4NCjxi
cj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwO2luZGl2aWR1YWwg
YXR0YWNobWVudCBjaXJjdWl0cy4NCiZuYnNwO1RoZSB1c2Ugb2Ygbm9uLW51bGwgVEFJSSBhbmQg
U0FJSSBpczwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7
ICZuYnNwO3Jlc2VydmVkIGZvciBmdXR1cmUgZW5oYW5jZW1lbnRzLjwvZm9udD4NCjxicj48Zm9u
dCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7PC9mb250Pg0KPGJyPjxmb250IHNpemU9
MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQpNeSBxdWVzdGlvbiBpcyAsPC9mb250Pg0KPGJyPjxm
b250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj53aGF0IGRvc2UgdGhpcyBzdGF0ZW1lbnQgbWVh
bj88L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPndoZXRoZXIgbWVh
bnMgdGhhdCBUQUlJIGFuZCBTQUlJIGlzDQpub3QgcHJlc2VudCBvciA8L2ZvbnQ+DQo8YnI+PGZv
bnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPm1lYW5zIHRoYXQgVEFJSSBhbmQgU0FJSSBpcyBw
cmVzZW50DQpidXQgTGVuZ3RoIGZpZWxkIHZhbHVlIGlzIHplcm8/PC9mb250Pg0KPGJyPjxmb250
IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5pZiBpdCdzIHRoZSBsYXR0ZXIsIHdoYXQncyB0aGUg
Jm5ic3A7VEFJSQ0KYW5kIFNBSUkgVHlwZSBmaWVsZCB2YWx1ZT88L2ZvbnQ+DQo8YnI+PGZvbnQg
c2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPmlmIGl0J3MgdGhlIGZvcm1lciwgaXQgc2VlbXMgdG8g
Y29uZmxpY3QNCndpdGggUkZDIDQ0NDcgc2VjdGlvbiA1LjMuMi48L2ZvbnQ+DQo8YnI+PGZvbnQg
c2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPmJlY2F1c2UgaW4gUkZDIDQ0NDcgc2VjaW9uIDUuMy4y
IHNheSw8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwOyAm
bmJzcDtJZiBhIHBhcnRpY3VsYXIgYXBwbGljYXRpb24NCmRvZXMgbm90IG5lZWQgYWxsIHRocmVl
IG9mIHRoZXNlIHN1Yi1lbGVtZW50cywgaXQgTVVTVDwvZm9udD4NCjxicj48Zm9udCBzaXplPTIg
ZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwO3NlbmQgYWxsIHRoZSBzdWItZWxlbWVudHMN
CmJ1dCBzZXQgdGhlIGxlbmd0aCB0byAwIGZvciB0aGUgdW51c2VkPC9mb250Pg0KPGJyPjxmb250
IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsgJm5ic3A7c3ViLWVsZW1lbnRzLjwvZm9u
dD4NCjxicj4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+VGhlIHNl
Y29uZCBxdWVzdGlvbjo8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYi
PlNlY3Rpb24gNi4xLjEgaW4gJm5ic3A7UkZDIDQ3NjIgc2F5OjwvZm9udD4NCjxicj48Zm9udCBz
aXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwO0F0dGFjaG1lbnQgR3JvdXAgSWRl
bnRpZmllcg0KKEFHSSksIExlbmd0aCwgVmFsdWU6IFRoZSB1bmlxdWUgbmFtZSBvZjwvZm9udD4N
Cjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwO3RoaXMgVlBM
Uy4gJm5ic3A7VGhlIEFHSQ0KaWRlbnRpZmllcyBhIHR5cGUgb2YgbmFtZSwgYW5kIExlbmd0aCBk
ZW5vdGVzIHRoZTwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5i
c3A7ICZuYnNwO2xlbmd0aCBvZiBWYWx1ZSwgd2hpY2gNCmlzIHRoZSBuYW1lIG9mIHRoZSBWUExT
LiAmbmJzcDtXZSB1c2UgdGhlIHRlcm0gQUdJPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNl
PSJzYW5zLXNlcmlmIj4mbmJzcDsgJm5ic3A7aW50ZXJjaGFuZ2VhYmx5IHdpdGggVlBMUw0KaWRl
bnRpZmllci48L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYi
Pk15IHF1ZXN0aW9uIGlzLDwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJp
ZiI+d2hhdCdzIHRoZSBBR0kgVHlwZSBmaWxlZCB2YWx1ZSB0aGF0DQppbmRpY2F0ZWQgdGhlIEFH
SSB2YWx1ZSBpcyBWUExTIG5hbWU/PC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNl
PSJzYW5zLXNlcmlmIj48YnI+DQo8L2ZvbnQ+PHR0Pjxmb250IHNpemU9Mj5UaGFua3MgYW5kIFJl
Z2FyZHM8L2ZvbnQ+PC90dD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KSmVy
cnkga2luZzxicj4NCjwvZm9udD4NCg==
--=_alternative 0058D75288257310_=--



--===============1591621637==
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://www1.ietf.org/mailman/listinfo/pwe3

--===============1591621637==--





From pwe3-bounces@ietf.org Sun Jul 08 16:15:24 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7dA8-0000Gt-IS; Sun, 08 Jul 2007 16:15:20 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I7d9s-0007zl-2x
	for pwe3-confirm+ok@megatron.ietf.org; Sun, 08 Jul 2007 16:15:04 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7d9r-0007yJ-JG; Sun, 08 Jul 2007 16:15:03 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I7d9r-0003jE-BY; Sun, 08 Jul 2007 16:15:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 0E08E175EA;
	Sun,  8 Jul 2007 20:15:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I7d9q-0000th-KC; Sun, 08 Jul 2007 16:15:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I7d9q-0000th-KC@stiedprstage1.ietf.org>
Date: Sun, 08 Jul 2007 16:15:02 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: pwe3@ietf.org
Subject: [PWE3] I-D
	ACTION:draft-ietf-pwe3-tdm-control-protocol-extensi-03.txt 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
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		: Control Protocol Extensions for Setup of TDM Pseudowires
	Author(s)	: S. Vainshtein, Y. Stein
	Filename	: draft-ietf-pwe3-tdm-control-protocol-extensi-03.txt
	Pages		: 12
	Date		: 2007-7-8
	
This document defines extension to the PWE3 control protocol [RFC4447] 
 and PWE3 IANA allocations [RFC4446] required for setup of  
 TDM pseudo wires.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-tdm-control-protocol-extensi-03.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-pwe3-tdm-control-protocol-extensi-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pwe3-tdm-control-protocol-extensi-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-7-8155429.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-tdm-control-protocol-extensi-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pwe3-tdm-control-protocol-extensi-03.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-7-8155429.I-D@ietf.org>


--OtherAccess--

--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://www1.ietf.org/mailman/listinfo/pwe3

--NextPart--






From pwe3-bounces@ietf.org Mon Jul 09 10:47:29 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7uWJ-0001Hr-Ov; Mon, 09 Jul 2007 10:47:23 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I7uWI-0001Hl-Po
	for pwe3-confirm+ok@megatron.ietf.org; Mon, 09 Jul 2007 10:47:22 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7uWI-0001Hc-Ey
	for pwe3@ietf.org; Mon, 09 Jul 2007 10:47:22 -0400
Received: from smail.alcatel.fr ([62.23.212.165])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7uWI-0000tM-09
	for pwe3@ietf.org; Mon, 09 Jul 2007 10:47:22 -0400
Received: from gbmail02.netfr.alcatel.fr (gbmail02.netfr.alcatel.fr
	[155.132.251.26])
	by smail.alcatel.fr (8.13.4/8.13.4/ICT) with ESMTP id l69EkpA5000334
	for <pwe3@ietf.org>; Mon, 9 Jul 2007 16:46:51 +0200
To: pwe3@ietf.org
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OFCC049DFE.E41989A2-ON80257313.0050FCDF-80257313.00512842@netfr.alcatel.fr>
From: Matthew.Bocci@alcatel-lucent.co.uk
Date: Mon, 9 Jul 2007 15:46:27 +0100
X-MIMETrack: Serialize by Router on GBMAIL02/GB/ALCATEL(Release 5.0.13aHF163 |
	June 23, 2005) at 07/09/2007 15:46:48
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
X-Scanned-By: MIMEDefang 2.51 on 155.132.180.81
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Subject: [PWE3] Draft Chicago agenda
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

All,

Here is the draft agenda for the PWE3 meeting in Chicago.

Please let me know if I have missed anything or if you have any other
comments or corrections.

Regards,

Matthew


MONDAY, July 23rd, 2007 - 13:00 - 15:00
-----------------------------------
CHAIRS: Danny McPherson & Stewart Bryant

15 mins WG Status and Update - Chairs

5 mins - Pseudowire Virtual Circuit Connectivity Verification (VCCV) A
Control
Channel for Pseudowires - Tom Nadeau (tnadeau@cisco.com)
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-vccv-14.txt

5 mins - MS-PW Requirements - Luca Martini (lmartini@cisco.com)
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-ms-pw-requirements-=
05.txt


5 mins - Dynamic Placement of Multi Segment Pseudo Wires - Luca Martini=

(lmartini@cisco.com)
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-dynamic-ms-pw-05.tx=
t

10 mins - Preferential Forwarding Status Bit Definition - Mustapha Aiss=
aoui
(mustapha.aissaoui@alcatel-lucent.co.uk)
http://www.ietf.org/internet-drafts/draft-muley-dutta-pwe3-redundancy-b=
it-00.txt


15 mins - T-MPLS Report - Stewart Bryant (stbryant@cisco.com)
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-mpls-transport-00.t=
xt
https://datatracker.ietf.org/liaison/345/
https://datatracker.ietf.org/liaison/344/

15 mins - PTP over MPLS - Roh Cohen (ronc@resolutenetworks.com)
http://www.ietf.org/internet-drafts/draft-ronc-ptp-mpls-00.txt

15 mins - 802.1ah Pseudowire - Luca Martini (lmartini@cisco.com)
http://www.ietf.org/internet-drafts/draft-martini-pwe3-802.1ah-pw-00.tx=
t

15 mins - Setup and Manage PBB-based Tunnels with PWE3 Mechanism - Ping=
 Pan
(ppan@hammerheadsystems.com)
http://www.ietf.org/internet-drafts/draft-pan-pwe3-pbb-tunnels-00.txt



----------------------------------------
Matthew Bocci
IP Division,
Alcatel-Lucent Telecom Limited, Registered Office: Christchurch Way,
Greenwich, London SE10 0AG.
Registered in England & Wales number 02650571
-----------------------------------------
=




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



From pwe3-bounces@ietf.org Tue Jul 10 05:35:50 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8C8G-0006cR-HL; Tue, 10 Jul 2007 05:35:44 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I8C8F-0006cI-4w
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 10 Jul 2007 05:35:43 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8C8E-0006c9-O3
	for pwe3@ietf.org; Tue, 10 Jul 2007 05:35:42 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8C7z-0008HS-E7
	for pwe3@ietf.org; Tue, 10 Jul 2007 05:35:42 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 10 Jul 2007 11:34:27 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAO/ukkaQ/uCLh2dsb2JhbACPMwEBAQgOLA
X-IronPort-AV: i="4.16,521,1175464800"; 
	d="scan'208"; a="147650720:sNHT64069026610"
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 l6A9YPaj005232; 
	Tue, 10 Jul 2007 11:34:25 +0200
Received: from stewart-bryants-computer.local (ams3-vpn-dhcp4121.cisco.com
	[10.61.80.24])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6A9YOTC022776; 
	Tue, 10 Jul 2007 09:34:24 GMT
Message-ID: <469352A2.1080609@cisco.com>
Date: Tue, 10 Jul 2007 10:34:26 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604)
MIME-Version: 1.0
To: pwe3 <pwe3@ietf.org>, Ron Cohen <ronc@resolutenetworks.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=899; t=1184060065;
	x=1184924065; 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:=20draft-ronc-ptp-mpls-00 |Sender:=20;
	bh=M/YmbCbWgMFKo0rYG+hmt7qSd/gR1Q6vmQrxhDBNFSY=;
	b=AovbYkJgux3qRMjUak7NHcl90WejC+5paar7pwAeXiy4dLiLkRRF2fZMZZK9e7G1K4t8QqgY
	adKcYWay0wfwBVVryMCU7vUddww9M9F4seArKquTTVckABtAZ28KqKUn;
Authentication-Results: ams-dkim-2; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: 
Subject: [PWE3] draft-ronc-ptp-mpls-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Ron

It is not clear from this document whether you are proposing to
run PTP over the normal (IPv4/IPv6) LDP/RSVP FEC between PEs, or 
over a special one.

An LSR using LDP normally inherits the next hop from IP routing
and IP routing has no reciprocal path requirements, indeed it
would need to take special (cpu intensive) action to cause 
reciprocity.

Also when running with first nibble = 0, no information is
provided as to the payload. This is explicitly stated in RFC4385.
So I do not see how an LSR is able to determine that the payload
is PTP to perform transparent clock actions.

To support transparent clock, PTP needs to either run an a special 
FEC that only carries PTP packets (with reciprocal path properties), 
or it needs to run over a normal FEC (signaled by RSVP) using an 
ACH, or using a reserved label so that PTP packets can be identified.

- Stewart


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



From pwe3-bounces@ietf.org Tue Jul 10 10:27:26 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8GgW-0000BL-MJ; Tue, 10 Jul 2007 10:27:24 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I8GgV-0000BE-RY
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 10 Jul 2007 10:27:23 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8GgV-0000B1-GS
	for pwe3@ietf.org; Tue, 10 Jul 2007 10:27:23 -0400
Received: from webmail.resolutenetworks.com ([80.179.15.67]
	helo=mail.resolutenetworks.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8GgO-0006cZ-FB
	for pwe3@ietf.org; Tue, 10 Jul 2007 10:27:23 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 10 Jul 2007 17:27:53 +0300
Message-ID: <0606D918CE9CEA4E9835D2CDAA001A95ED6F3A@ilmail1.il.reduxcom.com>
In-Reply-To: <469352A2.1080609@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ronc-ptp-mpls-00
Thread-Index: AcfC1cjISfZ1/wIDRe2p3pt3pzhGggAHTlmA
References: <469352A2.1080609@cisco.com>
From: "Ron Cohen" <ronc@resolutenetworks.com>
To: <stbryant@cisco.com>,
	"pwe3" <pwe3@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: 
Subject: [PWE3] RE: draft-ronc-ptp-mpls-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Stewart,

Thanks for your comments.=20

You raised two issues; setup of reciprocal LSPs and identification of
PTP messages. Please see my comments below:

1. The draft explains the advantage of reciprocal (symmetric) LSPs as
quoted below. As you point out, in order to setup reciprocal LSPs
special means must be used, e.g. RSVP-TE. The draft does not elaborate
on how symmetric LSPs are signaled. This should probably be addressed in
next versions of the draft.=20


   All PTP LSPs MUST be bi-directional.  PTP protocol is sensitive to
   asymmetry between the propagation delays across the master-slave and
   slave-master paths.  If the asymmetry is known, the PTP protocol has
   means to compensate for the known asymmetry.  If the asymmetry is not
   known, the time recovered at the slaves will have a fixed offset
   equal to half the propagation delay asymmetry.  Therefore, whenever
   possible, the tunnel and PTP LSPs SHOULD be setup in a symmetric way.


2. Identification of PTP messages: The draft proposes that PTP messages
will be sent over a specific FEC identified by the vc-label. Transparent
clocks know in advance that a specific vc-label is associated with a PTP
PW type through LDP signaling as described in section 6 of the draft.

Best,
Ron


-----Original Message-----
From: Stewart Bryant [mailto:stbryant@cisco.com]=20
Sent: Tuesday, July 10, 2007 12:34 PM
To: pwe3; Ron Cohen
Subject: draft-ronc-ptp-mpls-00

Ron

It is not clear from this document whether you are proposing to
run PTP over the normal (IPv4/IPv6) LDP/RSVP FEC between PEs, or=20
over a special one.

An LSR using LDP normally inherits the next hop from IP routing
and IP routing has no reciprocal path requirements, indeed it
would need to take special (cpu intensive) action to cause=20
reciprocity.

Also when running with first nibble =3D 0, no information is
provided as to the payload. This is explicitly stated in RFC4385.
So I do not see how an LSR is able to determine that the payload
is PTP to perform transparent clock actions.

To support transparent clock, PTP needs to either run an a special=20
FEC that only carries PTP packets (with reciprocal path properties),=20
or it needs to run over a normal FEC (signaled by RSVP) using an=20
ACH, or using a reserved label so that PTP packets can be identified.

- Stewart

--
This message was scanned by ESVA and is believed to be clean.
Click here to report this message as spam.=20
http://mailgw.resolutenetworks.com/cgi-bin/learn-msg.cgi?id=3DCEA9528233.=
8
3DC1




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



From pwe3-bounces@ietf.org Tue Jul 10 18:15:24 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8NzO-0002fP-H3; Tue, 10 Jul 2007 18:15:22 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I8NzN-0002fE-I7
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 10 Jul 2007 18:15:21 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8NzN-0002f6-6F
	for pwe3@ietf.org; Tue, 10 Jul 2007 18:15:21 -0400
Received: from black.monoski.com ([63.227.123.238] helo=napoleon.monoski.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8Nz8-00087S-KA
	for pwe3@ietf.org; Tue, 10 Jul 2007 18:15:21 -0400
Received: from [209.245.27.1] (napoleon.monoski.com [209.245.27.1])
	(authenticated bits=0)
	by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id l6AMETqp000372
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 10 Jul 2007 16:14:31 -0600 (MDT)
Message-ID: <469404C5.20402@cisco.com>
Date: Tue, 10 Jul 2007 16:14:29 -0600
From: Luca Martini <lmartini@cisco.com>
User-Agent: Thunderbird 1.5.0.8 (X11/20061110)
MIME-Version: 1.0
To: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
References: <75B2A84D9323BC4CA3977CF378CE75EB03837B2C@xmb-sjc-21e.amer.cisco.com>
In-Reply-To: <75B2A84D9323BC4CA3977CF378CE75EB03837B2C@xmb-sjc-21e.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
	milter-greylist-3.0a1 (napoleon.monoski.com [209.245.27.1]);
	Tue, 10 Jul 2007 16:14:32 -0600 (MDT)
X-Scanned-By: MIMEDefang 2.57 on 209.245.27.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9af087f15dbdd4c64ae6bbcdbc5b1d44
Cc: "Attila Takacs \(IJ/ETH\)" <Attila.Takacs@ericsson.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>
Subject: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Hello!

More comments inline.

Ali Sajassi (sajassi) wrote:
> Hi Attila,
>
> Thanks for your comments. Please see my reply inline .... 
>
>   
>> -----Original Message-----
>> From: Attila Takacs (IJ/ETH) [mailto:Attila.Takacs@ericsson.com] 
>> Sent: Tuesday, July 10, 2007 9:41 AM
>> To: Luca Martini (lmartini); Ali Sajassi (sajassi)
>> Subject: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
>>
>> Hi Luca and Ali,
>>
>> I just saw your draft on the pwe3 agenda...
>> It is a useful proposal, please find some 
>> comments/suggestions below which you might consider for a new 
>> revision.
>>
>> Best regards,
>> Attila
>> Ps.:I noticed that this is a 00 version, so sorry if you 
>> think the comments are too editorial
>>
>>
>> -Section 2, it seems to be more a terminology/definition 
>> section than acronyms The following definitions would be 
>> useful as well: 
>>
>> Service Instance Drop Eligibility Indicator (I-DEI): A field 
>> of the I-TAG which identifies the Service Instance Drop 
>> Eligibility of the frame in the 802.1ah (PBBN) domain.
>>
>> Service instance priority code point (I-PCP): A field of the 
>> I-TAG which identifies the service instance priority of the 
>> frame in the 802.1ah
>> (PBBN) domain.
>>
>> I-tagged Service Interface: A 802.1ah (PBBN) interface type 
>> over which an I-TAG immediately follows the destination and 
>> source MAC addresses in the header of the Ethernet frames.
>>
>>     
>
>   
Yes,  I also agree , we'll add these.
> Agree, since they are used in the text, it make sense to define them up
> front.
>
>   
>> A note may be appropriate saying that: These definitions will 
>> be removed in later versions by a reference to the 
>> appropriate IEEE standard.
>>
>>     
>
> I think it still would be good to keep these definitions in the draft
> for sake of completeness.
>
>
>   
Yes, It's really a compromise between how much we repeat in a document , 
and how much we want the document to be clear.

I usually err more on the clear side.

>> -Section 4 Applicability
>> In the first paragraph I'm considering if "I-SID to I-SID" 
>> should not be changed to "I-tagged interface to I-tagged 
>> interface". I recognize that this might be more limiting from 
>> an AC point of view but isn't this the intention?
>>
>>     
>
> "I-SID to I-SID" is correct since it is used to connect two I-SID aware
> forwarder rather than two Acs - e.g., AC may not be an I-tagged service
> interface but still we want to provide full-mesh of PW on a per I-SID
> basis.
>
>   
We can certainly change this definition , but in general the other encap 
drafts are written with respect to an AC.
I just wanted to keep this one consistent.

>> After this paragraph something like "In contrast to the VLAN (tagged
>> mode) where 2^12 customer service instances can be 
>> distinguished, the I-SID in the I-TAG increases scalability 
>> by allowing 2^24 service instances." might highlight one 
>> important aspect of the VLAN and I-SID scenario. 
>>
>>     
>
> Since we are using one PW per I-SID, this scalability aspect of I-tagged
> is not used in our case.
>
>   
>> In the discussion further below in Section 4 "I-SID aware" 
>> forwarders should be "I-TAG aware" forwarders. For instance 
>> for the QoS discussions not only the I-SID but also the I-PCP 
>> and I-DEI may be considered.
>>
>> Further, in the case of native CFM Ethernet OAM and PW OAM 
>> interworking I can imagine that the No Customer Addresses 
>> (NCA) field of the I-TAG may be considered by the NSP and/or 
>> forwarder.
>>
>>     
>  
> Agree.
>
>   
ok.
>> -Regarding Sections 5 and 6, I do not see the benefit of 
>> repeating general PW encapsulation procedures. In my read 
>> only 6.2 provides new information about the I-tagged mode all 
>> other discussion could be removed with no harm and instead a 
>> pointer to the already defined PW procedures could be added. 
>> (Do I mis something?)
>>
>>     
>
> I guess it is there for sake of completeness. It is up to Luca to decide
> what to do with it.
>
>   
I think that I would like to avoid too many recursive reference to other 
documents. This document needs to explain how to implement the PW 
without too many references.

>   
>> It would be beneficial to add a figure focusing on the 
>> I-tagged Ethernet header and its PW encapsulation, something 
>> like this: 
>>
>> 	AC				PW
>> 	        Forwarder
>> ------------		------------
>> |   Data   |    		|   Data   | 
>> |----------|		|----------|
>> |Other TAGs|		|Other TAGs|
>> |----------|  		|----------|
>> |  I-TAG   | ----|	|  I-TAG   |
>> |----------|     |	|----------|
>> |  SA MAC  |     |	|  SA MAC  | 
>> |----------|     |	|----------|
>> |  DA MAC  |     |	|  DA MAC  |
>> ------------     |	|----------|
>> 		     +-->	|Encap (CW)|
>> 		     |	|----------|
>> 		     +-->	|   Demux  |
>> 		 		|----------|
>> 		     		|PSN tunnel|
>> 				------------
>>
>>
>>
>>     
Yes, this is a very good idea.  Is this figure what we want ? No other 
tags shown ?

Thanks.
Luca

>  
> Agree, I think such figure would be helpful.
>
> Thanks again for your comments,
> Ali
>
>   
>>
>>     
>
>   



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



From pwe3-bounces@ietf.org Wed Jul 11 12:11:30 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8emm-000338-LN; Wed, 11 Jul 2007 12:11:28 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I8eml-00030x-9u
	for pwe3-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 12:11:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8emk-00030Q-Sr
	for pwe3@ietf.org; Wed, 11 Jul 2007 12:11:26 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8emk-0004fr-9h
	for pwe3@ietf.org; Wed, 11 Jul 2007 12:11:26 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	A1A16204EC; Wed, 11 Jul 2007 18:11:09 +0200 (CEST)
X-AuditID: c1b4fb3c-b0e80bb0000007e1-47-4695011dcd34
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	79AAF203FC; Wed, 11 Jul 2007 18:11:09 +0200 (CEST)
Received: from esealmw116.eemea.ericsson.se ([153.88.200.7]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Jul 2007 18:11:09 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 11 Jul 2007 18:11:08 +0200
Message-ID: <53CCFDD6E346CB43994852666C210E9101A54E5F@esealmw116.eemea.ericsson.se>
In-Reply-To: <469404C5.20402@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Thread-Index: AcfDP7dCdeOAJlGpSAOiY8e4Ek5kzwAk69+w
References: <75B2A84D9323BC4CA3977CF378CE75EB03837B2C@xmb-sjc-21e.amer.cisco.com>
	<469404C5.20402@cisco.com>
From: "Attila Takacs (IJ/ETH)" <Attila.Takacs@ericsson.com>
To: "Luca Martini" <lmartini@cisco.com>,
	"Ali Sajassi (sajassi)" <sajassi@cisco.com>
X-OriginalArrivalTime: 11 Jul 2007 16:11:09.0155 (UTC)
	FILETIME=[17B5B330:01C7C3D6]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d008c19e97860b8641c1851f84665a75
Cc: "PWE3 WG \(E-mail\)" <pwe3@ietf.org>
Subject: [PWE3] RE: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Hi Luca, Ali,
please find my comments inline [at]
Best regards,
Attila

> -----Original Message-----
> From: Luca Martini [mailto:lmartini@cisco.com]=20
> Sent: Wednesday, July 11, 2007 12:14 AM
> To: Ali Sajassi (sajassi)
> Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> Subject: Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
>=20
> Hello!
>=20
> More comments inline.
>=20
> Ali Sajassi (sajassi) wrote:
> > Hi Attila,
> >
> > Thanks for your comments. Please see my reply inline ....=20
> >
> >  =20
> >> -----Original Message-----
> >> From: Attila Takacs (IJ/ETH) [mailto:Attila.Takacs@ericsson.com]
> >> Sent: Tuesday, July 10, 2007 9:41 AM
> >> To: Luca Martini (lmartini); Ali Sajassi (sajassi)
> >> Subject: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
> >>
> >> Hi Luca and Ali,
> >>
> >> I just saw your draft on the pwe3 agenda...
> >> It is a useful proposal, please find some=20
> comments/suggestions below=20
> >> which you might consider for a new revision.
> >>
> >> Best regards,
> >> Attila
> >> Ps.:I noticed that this is a 00 version, so sorry if you think the=20
> >> comments are too editorial
> >>
> >>
> >> -Section 2, it seems to be more a terminology/definition=20
> section than=20
> >> acronyms The following definitions would be useful as well:
> >>
> >> Service Instance Drop Eligibility Indicator (I-DEI): A=20
> field of the=20
> >> I-TAG which identifies the Service Instance Drop=20
> Eligibility of the=20
> >> frame in the 802.1ah (PBBN) domain.
> >>
> >> Service instance priority code point (I-PCP): A field of the I-TAG=20
> >> which identifies the service instance priority of the frame in the=20
> >> 802.1ah
> >> (PBBN) domain.
> >>
> >> I-tagged Service Interface: A 802.1ah (PBBN) interface type over=20
> >> which an I-TAG immediately follows the destination and source MAC=20
> >> addresses in the header of the Ethernet frames.
> >>
> >>    =20
> >
> >  =20
> Yes,  I also agree , we'll add these.
> > Agree, since they are used in the text, it make sense to=20
> define them=20
> > up front.
> >
> >  =20
> >> A note may be appropriate saying that: These definitions will be=20
> >> removed in later versions by a reference to the appropriate IEEE=20
> >> standard.
> >>
> >>    =20
> >
> > I think it still would be good to keep these definitions in=20
> the draft=20
> > for sake of completeness.
> >
> >
> >  =20
> Yes, It's really a compromise between how much we repeat in a=20
> document , and how much we want the document to be clear.
>=20
> I usually err more on the clear side.
>=20
> >> -Section 4 Applicability
> >> In the first paragraph I'm considering if "I-SID to I-SID"=20
> >> should not be changed to "I-tagged interface to I-tagged=20
> interface".=20
> >> I recognize that this might be more limiting from an AC=20
> point of view=20
> >> but isn't this the intention?
> >>
> >>    =20
> >
> > "I-SID to I-SID" is correct since it is used to connect two I-SID=20
> > aware forwarder rather than two Acs - e.g., AC may not be=20
> an I-tagged=20
> > service interface but still we want to provide full-mesh of PW on a=20
> > per I-SID basis.
> >
> >  =20
> We can certainly change this definition , but in general the=20
> other encap drafts are written with respect to an AC.
> I just wanted to keep this one consistent.
>=20

[AT] I would say if the forwarder is based on the I-SID then it may be
better to limit the AC to be I-tagged. On the other hand, even if over
the AC VLAN tagged frames arrive an entity may strip the VLAN TAG
entirely (e.g., the NSP) before presenting the frame to the forwarder.
This latter case seems to be fine as well.


> >> After this paragraph something like "In contrast to the=20
> VLAN (tagged
> >> mode) where 2^12 customer service instances can be=20
> distinguished, the=20
> >> I-SID in the I-TAG increases scalability by allowing 2^24 service=20
> >> instances." might highlight one important aspect of the VLAN and=20
> >> I-SID scenario.
> >>
> >>    =20
> >
> > Since we are using one PW per I-SID, this scalability aspect of=20
> > I-tagged is not used in our case.
> >
> >  =20
> >> In the discussion further below in Section 4 "I-SID aware"=20
> >> forwarders should be "I-TAG aware" forwarders. For=20
> instance for the=20
> >> QoS discussions not only the I-SID but also the I-PCP and=20
> I-DEI may=20
> >> be considered.
> >>
> >> Further, in the case of native CFM Ethernet OAM and PW OAM=20
> >> interworking I can imagine that the No Customer Addresses
> >> (NCA) field of the I-TAG may be considered by the NSP and/or=20
> >> forwarder.
> >>
> >>    =20
> > =20
> > Agree.
> >
> >  =20
> ok.
> >> -Regarding Sections 5 and 6, I do not see the benefit of repeating=20
> >> general PW encapsulation procedures. In my read only 6.2=20
> provides new=20
> >> information about the I-tagged mode all other discussion could be=20
> >> removed with no harm and instead a pointer to the already=20
> defined PW=20
> >> procedures could be added.
> >> (Do I mis something?)
> >>
> >>    =20
> >
> > I guess it is there for sake of completeness. It is up to Luca to=20
> > decide what to do with it.
> >
> >  =20
> I think that I would like to avoid too many recursive=20
> reference to other documents. This document needs to explain=20
> how to implement the PW without too many references.
>=20
> >  =20
> >> It would be beneficial to add a figure focusing on the I-tagged=20
> >> Ethernet header and its PW encapsulation, something like this:
> >>
> >> 	AC				PW
> >> 	        Forwarder
> >> ------------		------------
> >> |   Data   |    		|   Data   |=20
> >> |----------|		|----------|
> >> |Other TAGs|		|Other TAGs|
> >> |----------|  		|----------|
> >> |  I-TAG   | ----|	|  I-TAG   |
> >> |----------|     |	|----------|
> >> |  SA MAC  |     |	|  SA MAC  |=20
> >> |----------|     |	|----------|
> >> |  DA MAC  |     |	|  DA MAC  |
> >> ------------     |	|----------|
> >> 		     +-->	|Encap (CW)|
> >> 		     |	|----------|
> >> 		     +-->	|   Demux  |
> >> 		 		|----------|
> >> 		     		|PSN tunnel|
> >> 				------------
> >>
> >>
> >>
> >>    =20
> Yes, this is a very good idea.  Is this figure what we want ?=20
> No other tags shown ?
>=20
[AT] I think there shouldn't be any other tags below the I-TAG when the
frame is presented to the forwarder.

> Thanks.
> Luca
>=20
> > =20
> > Agree, I think such figure would be helpful.
> >
> > Thanks again for your comments,
> > Ali
> >
> >  =20
> >>
> >>    =20
> >
> >  =20
>=20
>=20


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



From pwe3-bounces@ietf.org Wed Jul 11 14:05:38 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8gZD-00070Z-PP; Wed, 11 Jul 2007 14:05:35 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I8gZC-0006qy-31
	for pwe3-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 14:05:34 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8gZB-0006nt-JS
	for pwe3@ietf.org; Wed, 11 Jul 2007 14:05:33 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8gZA-000147-TU
	for pwe3@ietf.org; Wed, 11 Jul 2007 14:05:33 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-5.cisco.com with ESMTP; 11 Jul 2007 11:05:32 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAMO4lEarR7PE/2dsb2JhbAA
X-IronPort-AV: i="4.16,527,1175497200"; 
	d="scan'208"; a="166425211:sNHT42674742"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l6BI5W1Q021758; 
	Wed, 11 Jul 2007 11:05:32 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l6BI5Wmo011619;
	Wed, 11 Jul 2007 18:05:32 GMT
Received: from xmb-sjc-21e.amer.cisco.com ([171.70.151.156]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Jul 2007 11:05:13 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 11 Jul 2007 11:05:12 -0700
Message-ID: <75B2A84D9323BC4CA3977CF378CE75EB03838005@xmb-sjc-21e.amer.cisco.com>
In-Reply-To: <53CCFDD6E346CB43994852666C210E9101A54E5F@esealmw116.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Thread-Index: AcfDP7dCdeOAJlGpSAOiY8e4Ek5kzwAk69+wAAONARA=
From: "Ali Sajassi \(sajassi\)" <sajassi@cisco.com>
To: "Attila Takacs \(IJ/ETH\)" <Attila.Takacs@ericsson.com>,
	"Luca Martini \(lmartini\)" <lmartini@cisco.com>
X-OriginalArrivalTime: 11 Jul 2007 18:05:13.0584 (UTC)
	FILETIME=[074EAF00:01C7C3E6]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=7944; t=1184177132;
	x=1185041132; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=sajassi@cisco.com;
	z=From:=20=22Ali=20Sajassi=20\(sajassi\)=22=20<sajassi@cisco.com>
	|Subject:=20RE=3A=20Some=20comments=20on=20draft-martini-pwe3-802.1ah-pw-
	00.txt |Sender:=20;
	bh=gPm0FbsiqYAwUz2uhrVeMlXdgbKNlxw1vCsUOLuzIek=;
	b=SCjclpQyj7T7XIPV/Gd8ebnOKNLyPk6hrOT4Km30wdjGZX81wUvybgIDEmmLZ6HXCOpinfF2
	3vsxrTN8wiVg1e6aJlVZ7h+2pt/XAnn7sL4LYUp5pg99487HL+G67b1H;
Authentication-Results: sj-dkim-4; header.From=sajassi@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dd7e0c3fd18d19cffdd4de99a114001d
Cc: "PWE3 WG \(E-mail\)" <pwe3@ietf.org>
Subject: [PWE3] RE: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

=20
More comments inline ...

> -----Original Message-----
> From: Attila Takacs (IJ/ETH) [mailto:Attila.Takacs@ericsson.com]=20
> Sent: Wednesday, July 11, 2007 9:11 AM
> To: Luca Martini (lmartini); Ali Sajassi (sajassi)
> Cc: PWE3 WG (E-mail)
> Subject: RE: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
>=20
> Hi Luca, Ali,
> please find my comments inline [at]
> Best regards,
> Attila
>=20
> > -----Original Message-----
> > From: Luca Martini [mailto:lmartini@cisco.com]
> > Sent: Wednesday, July 11, 2007 12:14 AM
> > To: Ali Sajassi (sajassi)
> > Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> > Subject: Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
> >=20
> > Hello!
> >=20
> > More comments inline.
> >=20
> > Ali Sajassi (sajassi) wrote:
> > > Hi Attila,
> > >
> > > Thanks for your comments. Please see my reply inline ....=20
> > >
> > >  =20
> > >> -----Original Message-----
> > >> From: Attila Takacs (IJ/ETH) [mailto:Attila.Takacs@ericsson.com]
> > >> Sent: Tuesday, July 10, 2007 9:41 AM
> > >> To: Luca Martini (lmartini); Ali Sajassi (sajassi)
> > >> Subject: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
> > >>
> > >> Hi Luca and Ali,
> > >>
> > >> I just saw your draft on the pwe3 agenda...
> > >> It is a useful proposal, please find some
> > comments/suggestions below
> > >> which you might consider for a new revision.
> > >>
> > >> Best regards,
> > >> Attila
> > >> Ps.:I noticed that this is a 00 version, so sorry if you=20
> think the=20
> > >> comments are too editorial
> > >>
> > >>
> > >> -Section 2, it seems to be more a terminology/definition
> > section than
> > >> acronyms The following definitions would be useful as well:
> > >>
> > >> Service Instance Drop Eligibility Indicator (I-DEI): A
> > field of the
> > >> I-TAG which identifies the Service Instance Drop
> > Eligibility of the
> > >> frame in the 802.1ah (PBBN) domain.
> > >>
> > >> Service instance priority code point (I-PCP): A field of=20
> the I-TAG=20
> > >> which identifies the service instance priority of the=20
> frame in the=20
> > >> 802.1ah
> > >> (PBBN) domain.
> > >>
> > >> I-tagged Service Interface: A 802.1ah (PBBN) interface type over=20
> > >> which an I-TAG immediately follows the destination and=20
> source MAC=20
> > >> addresses in the header of the Ethernet frames.
> > >>
> > >>    =20
> > >
> > >  =20
> > Yes,  I also agree , we'll add these.
> > > Agree, since they are used in the text, it make sense to
> > define them
> > > up front.
> > >
> > >  =20
> > >> A note may be appropriate saying that: These definitions will be=20
> > >> removed in later versions by a reference to the appropriate IEEE=20
> > >> standard.
> > >>
> > >>    =20
> > >
> > > I think it still would be good to keep these definitions in
> > the draft
> > > for sake of completeness.
> > >
> > >
> > >  =20
> > Yes, It's really a compromise between how much we repeat in=20
> a document=20
> > , and how much we want the document to be clear.
> >=20
> > I usually err more on the clear side.
> >=20
> > >> -Section 4 Applicability
> > >> In the first paragraph I'm considering if "I-SID to I-SID"=20
> > >> should not be changed to "I-tagged interface to I-tagged
> > interface".=20
> > >> I recognize that this might be more limiting from an AC
> > point of view
> > >> but isn't this the intention?
> > >>
> > >>    =20
> > >
> > > "I-SID to I-SID" is correct since it is used to connect two I-SID=20
> > > aware forwarder rather than two Acs - e.g., AC may not be
> > an I-tagged
> > > service interface but still we want to provide full-mesh=20
> of PW on a=20
> > > per I-SID basis.
> > >
> > >  =20
> > We can certainly change this definition , but in general the other=20
> > encap drafts are written with respect to an AC.
> > I just wanted to keep this one consistent.
> >=20
>=20
> [AT] I would say if the forwarder is based on the I-SID then=20
> it may be better to limit the AC to be I-tagged. On the other=20
> hand, even if over the AC VLAN tagged frames arrive an entity=20
> may strip the VLAN TAG entirely (e.g., the NSP) before=20
> presenting the frame to the forwarder.
> This latter case seems to be fine as well.
>=20

For VPLS application, another way of looking at this is that the PE is
modeled as having I-component connected to a forwarder similar to the
model presented in bridge-interop draft. So, the AC can be a regular
802.1Q or 802.1ad port; whereas, the forwarder is based on I-SID (e.g.,
a full-mesh of PW per I-SID).

>=20
> > >> After this paragraph something like "In contrast to the
> > VLAN (tagged
> > >> mode) where 2^12 customer service instances can be
> > distinguished, the
> > >> I-SID in the I-TAG increases scalability by allowing=20
> 2^24 service=20
> > >> instances." might highlight one important aspect of the VLAN and=20
> > >> I-SID scenario.
> > >>
> > >>    =20
> > >
> > > Since we are using one PW per I-SID, this scalability aspect of=20
> > > I-tagged is not used in our case.
> > >
> > >  =20
> > >> In the discussion further below in Section 4 "I-SID aware"=20
> > >> forwarders should be "I-TAG aware" forwarders. For
> > instance for the
> > >> QoS discussions not only the I-SID but also the I-PCP and
> > I-DEI may
> > >> be considered.
> > >>
> > >> Further, in the case of native CFM Ethernet OAM and PW OAM=20
> > >> interworking I can imagine that the No Customer Addresses
> > >> (NCA) field of the I-TAG may be considered by the NSP and/or=20
> > >> forwarder.
> > >>
> > >>    =20
> > > =20
> > > Agree.
> > >
> > >  =20
> > ok.
> > >> -Regarding Sections 5 and 6, I do not see the benefit of=20
> repeating=20
> > >> general PW encapsulation procedures. In my read only 6.2
> > provides new
> > >> information about the I-tagged mode all other discussion=20
> could be=20
> > >> removed with no harm and instead a pointer to the already
> > defined PW
> > >> procedures could be added.
> > >> (Do I mis something?)
> > >>
> > >>    =20
> > >
> > > I guess it is there for sake of completeness. It is up to Luca to=20
> > > decide what to do with it.
> > >
> > >  =20
> > I think that I would like to avoid too many recursive reference to=20
> > other documents. This document needs to explain how to=20
> implement the=20
> > PW without too many references.
> >=20
> > >  =20
> > >> It would be beneficial to add a figure focusing on the I-tagged=20
> > >> Ethernet header and its PW encapsulation, something like this:
> > >>
> > >> 	AC				PW
> > >> 	        Forwarder
> > >> ------------		------------
> > >> |   Data   |    		|   Data   |=20
> > >> |----------|		|----------|
> > >> |Other TAGs|		|Other TAGs|
> > >> |----------|  		|----------|
> > >> |  I-TAG   | ----|	|  I-TAG   |
> > >> |----------|     |	|----------|
> > >> |  SA MAC  |     |	|  SA MAC  |=20
> > >> |----------|     |	|----------|
> > >> |  DA MAC  |     |	|  DA MAC  |
> > >> ------------     |	|----------|
> > >> 		     +-->	|Encap (CW)|
> > >> 		     |	|----------|
> > >> 		     +-->	|   Demux  |
> > >> 		 		|----------|
> > >> 		     		|PSN tunnel|
> > >> 				------------
> > >>
> > >>
> > >>
> > >>    =20
> > Yes, this is a very good idea.  Is this figure what we want ?=20
> > No other tags shown ?
> >=20
> [AT] I think there shouldn't be any other tags below the=20
> I-TAG when the frame is presented to the forwarder.
>=20

The frame format as shown is good enough. If additional tag is needed
such as B-tag, then it gets imposed by the egress PE.

Cheers,
Ali

> > Thanks.
> > Luca
> >=20
> > > =20
> > > Agree, I think such figure would be helpful.
> > >
> > > Thanks again for your comments,
> > > Ali
> > >
> > >  =20
> > >>
> > >>    =20
> > >
> > >  =20
> >=20
> >=20
>=20


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



From pwe3-bounces@ietf.org Thu Jul 12 11:15:20 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I90Ny-0006qu-2N; Thu, 12 Jul 2007 11:15:18 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I90Nv-0006hA-S5
	for pwe3-confirm+ok@megatron.ietf.org; Thu, 12 Jul 2007 11:15:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I90Nv-0006ci-8f
	for pwe3@ietf.org; Thu, 12 Jul 2007 11:15:15 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I90Nu-0003jR-GD
	for pwe3@ietf.org; Thu, 12 Jul 2007 11:15:15 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	C196021857; Thu, 12 Jul 2007 17:14:18 +0200 (CEST)
X-AuditID: c1b4fb3e-af833bb0000007e1-cd-4696454a04e3
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	95CAA21855; Thu, 12 Jul 2007 17:14:18 +0200 (CEST)
Received: from esealmw116.eemea.ericsson.se ([153.88.200.7]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Jul 2007 17:14:18 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 12 Jul 2007 17:14:17 +0200
Message-ID: <53CCFDD6E346CB43994852666C210E9101A5547C@esealmw116.eemea.ericsson.se>
In-Reply-To: <75B2A84D9323BC4CA3977CF378CE75EB03838005@xmb-sjc-21e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Thread-Index: AcfDP7dCdeOAJlGpSAOiY8e4Ek5kzwAk69+wAAONARAALKHbAA==
References: <53CCFDD6E346CB43994852666C210E9101A54E5F@esealmw116.eemea.ericsson.se>
	<75B2A84D9323BC4CA3977CF378CE75EB03838005@xmb-sjc-21e.amer.cisco.com>
From: "Attila Takacs (IJ/ETH)" <Attila.Takacs@ericsson.com>
To: "Ali Sajassi (sajassi)" <sajassi@cisco.com>,
	"Luca Martini (lmartini)" <lmartini@cisco.com>
X-OriginalArrivalTime: 12 Jul 2007 15:14:18.0443 (UTC)
	FILETIME=[512E19B0:01C7C497]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8d89ee9312a95de8ee48d1c94511f1bb
Cc: "PWE3 WG \(E-mail\)" <pwe3@ietf.org>
Subject: [PWE3] RE: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Hi Ali,
Ok, I see your point with the VPLS scenario.
Thanks,
Attila=20

> -----Original Message-----
> From: Ali Sajassi (sajassi) [mailto:sajassi@cisco.com]=20
> Sent: Wednesday, July 11, 2007 8:05 PM
> To: Attila Takacs (IJ/ETH); Luca Martini (lmartini)
> Cc: PWE3 WG (E-mail)
> Subject: RE: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
>=20
> =20
> More comments inline ...
>=20
> > -----Original Message-----
> > From: Attila Takacs (IJ/ETH) [mailto:Attila.Takacs@ericsson.com]
> > Sent: Wednesday, July 11, 2007 9:11 AM
> > To: Luca Martini (lmartini); Ali Sajassi (sajassi)
> > Cc: PWE3 WG (E-mail)
> > Subject: RE: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
> >=20
> > Hi Luca, Ali,
> > please find my comments inline [at]
> > Best regards,
> > Attila
> >=20
> > > -----Original Message-----
> > > From: Luca Martini [mailto:lmartini@cisco.com]
> > > Sent: Wednesday, July 11, 2007 12:14 AM
> > > To: Ali Sajassi (sajassi)
> > > Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> > > Subject: Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
> > >=20
> > > Hello!
> > >=20
> > > More comments inline.
> > >=20
> > > Ali Sajassi (sajassi) wrote:
> > > > Hi Attila,
> > > >
> > > > Thanks for your comments. Please see my reply inline ....=20
> > > >
> > > >  =20
> > > >> -----Original Message-----
> > > >> From: Attila Takacs (IJ/ETH)=20
> [mailto:Attila.Takacs@ericsson.com]
> > > >> Sent: Tuesday, July 10, 2007 9:41 AM
> > > >> To: Luca Martini (lmartini); Ali Sajassi (sajassi)
> > > >> Subject: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
> > > >>
> > > >> Hi Luca and Ali,
> > > >>
> > > >> I just saw your draft on the pwe3 agenda...
> > > >> It is a useful proposal, please find some
> > > comments/suggestions below
> > > >> which you might consider for a new revision.
> > > >>
> > > >> Best regards,
> > > >> Attila
> > > >> Ps.:I noticed that this is a 00 version, so sorry if you
> > think the
> > > >> comments are too editorial
> > > >>
> > > >>
> > > >> -Section 2, it seems to be more a terminology/definition
> > > section than
> > > >> acronyms The following definitions would be useful as well:
> > > >>
> > > >> Service Instance Drop Eligibility Indicator (I-DEI): A
> > > field of the
> > > >> I-TAG which identifies the Service Instance Drop
> > > Eligibility of the
> > > >> frame in the 802.1ah (PBBN) domain.
> > > >>
> > > >> Service instance priority code point (I-PCP): A field of
> > the I-TAG
> > > >> which identifies the service instance priority of the
> > frame in the
> > > >> 802.1ah
> > > >> (PBBN) domain.
> > > >>
> > > >> I-tagged Service Interface: A 802.1ah (PBBN) interface=20
> type over=20
> > > >> which an I-TAG immediately follows the destination and
> > source MAC
> > > >> addresses in the header of the Ethernet frames.
> > > >>
> > > >>    =20
> > > >
> > > >  =20
> > > Yes,  I also agree , we'll add these.
> > > > Agree, since they are used in the text, it make sense to
> > > define them
> > > > up front.
> > > >
> > > >  =20
> > > >> A note may be appropriate saying that: These=20
> definitions will be=20
> > > >> removed in later versions by a reference to the=20
> appropriate IEEE=20
> > > >> standard.
> > > >>
> > > >>    =20
> > > >
> > > > I think it still would be good to keep these definitions in
> > > the draft
> > > > for sake of completeness.
> > > >
> > > >
> > > >  =20
> > > Yes, It's really a compromise between how much we repeat in
> > a document
> > > , and how much we want the document to be clear.
> > >=20
> > > I usually err more on the clear side.
> > >=20
> > > >> -Section 4 Applicability
> > > >> In the first paragraph I'm considering if "I-SID to I-SID"=20
> > > >> should not be changed to "I-tagged interface to I-tagged
> > > interface".=20
> > > >> I recognize that this might be more limiting from an AC
> > > point of view
> > > >> but isn't this the intention?
> > > >>
> > > >>    =20
> > > >
> > > > "I-SID to I-SID" is correct since it is used to connect=20
> two I-SID=20
> > > > aware forwarder rather than two Acs - e.g., AC may not be
> > > an I-tagged
> > > > service interface but still we want to provide full-mesh
> > of PW on a
> > > > per I-SID basis.
> > > >
> > > >  =20
> > > We can certainly change this definition , but in general=20
> the other=20
> > > encap drafts are written with respect to an AC.
> > > I just wanted to keep this one consistent.
> > >=20
> >=20
> > [AT] I would say if the forwarder is based on the I-SID=20
> then it may be=20
> > better to limit the AC to be I-tagged. On the other hand,=20
> even if over=20
> > the AC VLAN tagged frames arrive an entity may strip the VLAN TAG=20
> > entirely (e.g., the NSP) before presenting the frame to the=20
> forwarder.
> > This latter case seems to be fine as well.
> >=20
>=20
> For VPLS application, another way of looking at this is that=20
> the PE is modeled as having I-component connected to a=20
> forwarder similar to the model presented in bridge-interop=20
> draft. So, the AC can be a regular 802.1Q or 802.1ad port;=20
> whereas, the forwarder is based on I-SID (e.g., a full-mesh=20
> of PW per I-SID).
>=20
> >=20
> > > >> After this paragraph something like "In contrast to the
> > > VLAN (tagged
> > > >> mode) where 2^12 customer service instances can be
> > > distinguished, the
> > > >> I-SID in the I-TAG increases scalability by allowing
> > 2^24 service
> > > >> instances." might highlight one important aspect of=20
> the VLAN and=20
> > > >> I-SID scenario.
> > > >>
> > > >>    =20
> > > >
> > > > Since we are using one PW per I-SID, this scalability aspect of=20
> > > > I-tagged is not used in our case.
> > > >
> > > >  =20
> > > >> In the discussion further below in Section 4 "I-SID aware"=20
> > > >> forwarders should be "I-TAG aware" forwarders. For
> > > instance for the
> > > >> QoS discussions not only the I-SID but also the I-PCP and
> > > I-DEI may
> > > >> be considered.
> > > >>
> > > >> Further, in the case of native CFM Ethernet OAM and PW OAM=20
> > > >> interworking I can imagine that the No Customer Addresses
> > > >> (NCA) field of the I-TAG may be considered by the NSP and/or=20
> > > >> forwarder.
> > > >>
> > > >>    =20
> > > > =20
> > > > Agree.
> > > >
> > > >  =20
> > > ok.
> > > >> -Regarding Sections 5 and 6, I do not see the benefit of
> > repeating
> > > >> general PW encapsulation procedures. In my read only 6.2
> > > provides new
> > > >> information about the I-tagged mode all other discussion
> > could be
> > > >> removed with no harm and instead a pointer to the already
> > > defined PW
> > > >> procedures could be added.
> > > >> (Do I mis something?)
> > > >>
> > > >>    =20
> > > >
> > > > I guess it is there for sake of completeness. It is up=20
> to Luca to=20
> > > > decide what to do with it.
> > > >
> > > >  =20
> > > I think that I would like to avoid too many recursive=20
> reference to=20
> > > other documents. This document needs to explain how to
> > implement the
> > > PW without too many references.
> > >=20
> > > >  =20
> > > >> It would be beneficial to add a figure focusing on the=20
> I-tagged=20
> > > >> Ethernet header and its PW encapsulation, something like this:
> > > >>
> > > >> 	AC				PW
> > > >> 	        Forwarder
> > > >> ------------		------------
> > > >> |   Data   |    		|   Data   |=20
> > > >> |----------|		|----------|
> > > >> |Other TAGs|		|Other TAGs|
> > > >> |----------|  		|----------|
> > > >> |  I-TAG   | ----|	|  I-TAG   |
> > > >> |----------|     |	|----------|
> > > >> |  SA MAC  |     |	|  SA MAC  |=20
> > > >> |----------|     |	|----------|
> > > >> |  DA MAC  |     |	|  DA MAC  |
> > > >> ------------     |	|----------|
> > > >> 		     +-->	|Encap (CW)|
> > > >> 		     |	|----------|
> > > >> 		     +-->	|   Demux  |
> > > >> 		 		|----------|
> > > >> 		     		|PSN tunnel|
> > > >> 				------------
> > > >>
> > > >>
> > > >>
> > > >>    =20
> > > Yes, this is a very good idea.  Is this figure what we want ?=20
> > > No other tags shown ?
> > >=20
> > [AT] I think there shouldn't be any other tags below the I-TAG when=20
> > the frame is presented to the forwarder.
> >=20
>=20
> The frame format as shown is good enough. If additional tag=20
> is needed such as B-tag, then it gets imposed by the egress PE.
>=20
> Cheers,
> Ali
>=20
> > > Thanks.
> > > Luca
> > >=20
> > > > =20
> > > > Agree, I think such figure would be helpful.
> > > >
> > > > Thanks again for your comments,
> > > > Ali
> > > >
> > > >  =20
> > > >>
> > > >>    =20
> > > >
> > > >  =20
> > >=20
> > >=20
> >=20
>=20


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



From pwe3-bounces@ietf.org Fri Jul 13 13:33:20 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I9P0x-0001RQ-Sd; Fri, 13 Jul 2007 13:33:11 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1I9P0w-0001RG-Bs
	for pwe3-confirm+ok@megatron.ietf.org; Fri, 13 Jul 2007 13:33:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I9P0w-0001R7-2H
	for pwe3@ietf.org; Fri, 13 Jul 2007 13:33:10 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I9P0s-00089e-N5
	for pwe3@ietf.org; Fri, 13 Jul 2007 13:33:10 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 13 Jul 2007 19:33:07 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAPFTl0aQ/uCKh2dsb2JhbACPNwEBAQgOLA
X-IronPort-AV: i="4.16,537,1175464800"; 
	d="scan'208"; a="148032613:sNHT23648568"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6DHX5wf021741; 
	Fri, 13 Jul 2007 19:33:05 +0200
Received: from stewart-bryants-computer.local (ams3-vpn-dhcp337.cisco.com
	[10.61.65.81])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6DHX1TC024066; 
	Fri, 13 Jul 2007 17:33:05 GMT
Message-ID: <4697B74D.60601@cisco.com>
Date: Fri, 13 Jul 2007 18:33:01 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604)
MIME-Version: 1.0
To: pwe3 <pwe3@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=242; t=1184347985;
	x=1185211985; c=relaxed/simple; s=amsdkim1002;
	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:=20Open=20Research=20Issues=20in=20Internet=20Congestion=20Contr
	ol=20 |Sender:=20;
	bh=0FnYsc4AnGvhvAnO8gntv7LTNhOarNJW0PtmW0a1UCI=;
	b=anP2U/Beus3hfswwXVbQRrBkQM2wUHRvaAxALo17nyT3OQ1kNKVIqGrhj6duN2pXPjTakpOG
	c0V/t/YKh7bxdUQwETa9pOy8pzxPShrbmpQTGR0OZki3MWr+4RGTh4z+;
Authentication-Results: ams-dkim-1; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Subject: [PWE3] Open Research Issues in Internet Congestion Control 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

The following draft is of interest to us:

Open Research Issues in Internet Congestion Control http://www.ietf.org/internet-drafts/draft-irtf-iccrg-welzl-congestion-control-open-research-00.txt


Challenge 5 is pseudowires

- Stewart


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



From pwe3-bounces@ietf.org Tue Jul 17 12:36:41 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IAq2O-0004Rv-VP; Tue, 17 Jul 2007 12:36:36 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1IAq2N-0004Nb-EA
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 17 Jul 2007 12:36:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IAq2M-0004Mu-Gy; Tue, 17 Jul 2007 12:36:34 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IAq2L-0006QD-3t; Tue, 17 Jul 2007 12:36:34 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 17 Jul 2007 18:36:33 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAAuNnEaQ/uCLh2dsb2JhbACPRAEBCQon
X-IronPort-AV: i="4.16,546,1175464800"; 
	d="scan'208"; a="148280352:sNHT29653552"
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 l6HGaWVd031629; 
	Tue, 17 Jul 2007 18:36:32 +0200
Received: from stewart-bryants-computer.local (ams3-vpn-dhcp22.cisco.com
	[10.61.64.22])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6HGaVkt023230; 
	Tue, 17 Jul 2007 16:36:31 GMT
Message-ID: <469CF012.60905@cisco.com>
Date: Tue, 17 Jul 2007 17:36:34 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604)
MIME-Version: 1.0
To: pwe3 <pwe3@ietf.org>, mpls@ietf.org
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3868; t=1184690192;
	x=1185554192; 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:=20ITU-T=20SG=2015=20liaison=20-=20G.8110.1=20amendment=201=20(h
	ttps=3A//datatracker.ietf.org/liaison/344/) |Sender:=20;
	bh=Ow2v0VANxewjiLkw22BNCsNmwQ2RPT9BshipUKWvqQk=;
	b=PKnorFEbhoFELniSrGSxLETL25JHN4uGLGcFFj3czD1CDYuHCSn3qBIWIpTtINhZGbJPkKvM
	0Z6O7ZghuQMw5P02QOad+X+CVNmqdZI26aDqpjIshsFCPBFOJhqazONF;
Authentication-Results: ams-dkim-2; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: 
Subject: [PWE3] ITU-T SG 15 liaison - G.8110.1 amendment 1
	(https://datatracker.ietf.org/liaison/344/)
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

I have been looking at the ITU liaison addressed to PWE3 and MPLS WGs

June 2007 ITU-T SG 15 IETF PWE3 and MPLS WGs G.8110.1 amendment 1 
(https://datatracker.ietf.org/liaison/344/)

and would appreciate input to a suitable response. This liaison will be 
a topic on the PWE3 agenda.

I have removed the elements of the response where SG15 has agree with 
our comments and edited their text accordingly.

The following points remain:

Section 3.5 Transport MPLS definition
"Should be amended to make it clear TMPLS is a true subset of IETF PWE3 
over MPLS and that in the case of any differences, the IETF definition 
is considered the Normative definition."

SG15 Response:
"G.8110.1 describes the behaviour of a T-MPLS network. Following a 
discussion of your liaison statement it was agreed to clarify that 
T-MPLS uses a subset of the MPLS forwarding plane behaviour. For OAM 
only label 14 is used and hence only “ITU” mechanisms are supported. It 
is also assumed that MPLS and T-MPLS are deployed as disjoint networks. 
An LSP initiated from an IP/MPLS network element is encapsulated in 
Ethernet before it transits a T-MPLS network. Similarly if IP/MPLS is 
used as a server layer for T-MPLS then an LSP initiated from a T-MPLS 
network element is encapsulated in Ethernet before it transits an 
IP/MPLS network. This enforces the independence of the control planes 
for T-MPLS and IP/MPLS. Further as is customary with ITU-T 
Recommendations, equipment designed before the approval of the 
Recommendations is not expected to meet all the requirements of the new 
Recommendation."

SB - I have two concerns regarding this:

1) The statement "assumed that MPLS and T-MPLS are deployed as disjoint 
networks" MUST be backed up by some technical means to ensure that MPLS 
and T-MPLS remain disjoint, otherwise the assumption does not hold and 
someone will attempt interworking. Indeed a contribution at the ITU 
meeting that prepared this response proposed exactly that.

2) "as is customary with ITU-T Recommendations, equipment designed 
before the approval of the Recommendations is not expected to meet all 
the requirements of the new Recommendation."

I think that we need to note that we are not concerned about existing 
MPLS equipment being compliant with T-MPLS, but rather we are concerned 
that T-MPLS or any future enhancement to T-MPLS should not cause a 
conflict with the installed base of existing MPLS equipment, or any 
future IETF development of MPLS, or that it should inhibit some future 
development of MPLS.


Section 4.7.2 and A.3
"The PWE3 WG is concerned that the OAM is not based on VCCV. Any true 
subset of the IETF PWE3/MPLS design should allow the use of the IETF 
preferred OAM mechanism. This does not preclude the ITU specifying an 
additional mechanism as an optional extension to enhance VCCV, although 
it would be preferable for the ITU to work with the IETF to enhance VCCV 
to provide the additional OAM mechanisms that are needed."

"At a previous meeting SG 15 decided to base T-MPLS OAM on Y.1711 and 
requested Q5/13 to enhance the OAM mechanisms based on Y.1711. Based on 
this request Q5/13 developed Y.1373/G.8114, the amendment to G.8110.1 
adds a reference to Y.1373/G.8114. As described above, we expect T-MPLS 
and MPLS to be deployed as disjoint networks and as is customary with 
ITU-T Recommendations, equipment designed before the approval of the 
Recommendations is not expected to meet all the requirements of the new 
Recommendation. We do not anticipate any compatibility issues."

SB - Again, given the existence of a simple solution to ensure that no 
compatibility issue can exist (discriminating codepoint, I do not 
believe such anticipation is good enough.

What is the view of other members of the IETF?

- Stewart







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



From pwe3-bounces@ietf.org Tue Jul 17 13:41:52 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IAr3R-0004P3-24; Tue, 17 Jul 2007 13:41:45 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1IAr3L-0003jc-JM
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 17 Jul 2007 13:41:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IAr3K-0003f2-Pa; Tue, 17 Jul 2007 13:41:38 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IAr3G-0008UC-KN; Tue, 17 Jul 2007 13:41:38 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 17 Jul 2007 19:41:31 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAAucnEaQ/uCKh2dsb2JhbACPRAEBCQon
X-IronPort-AV: i="4.16,546,1175464800"; 
	d="scan'208"; a="148284733:sNHT168728632"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6HHfU8h025333; 
	Tue, 17 Jul 2007 19:41:30 +0200
Received: from stewart-bryants-computer.local (ams3-vpn-dhcp22.cisco.com
	[10.61.64.22])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6HHbakt012466; 
	Tue, 17 Jul 2007 17:37:36 GMT
Message-ID: <469CFE62.6030202@cisco.com>
Date: Tue, 17 Jul 2007 18:37:38 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604)
MIME-Version: 1.0
To: pwe3 <pwe3@ietf.org>, mpls@ietf.org
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3710; t=1184694090;
	x=1185558090; c=relaxed/simple; s=amsdkim1002;
	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:=20Response=20to=20PWE3=20and=20MPLS=20WG=20concerns=20with=20G.
	8110.1=20Amendment=201 |Sender:=20;
	bh=OFYKglMwUOmYvUBTVLs+8iJwC8t7JkuiuXyX1vmUeeI=;
	b=geD1DtaMMMNtWKLQAVoO7I9RCKpEDy+tw3sW+Sqf8lMxt3GN7K9joB+D30ztKJpbkzt3JkD3
	deGXX8syFCVYUrrZxRKUday+SJIuvIa2ZvU+BQlwBi3587mLaJGBXx2h;
Authentication-Results: ams-dkim-1; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: 
Subject: [PWE3] Response to PWE3 and MPLS WG concerns with G.8110.1
	Amendment 1
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

I have been looking at the ITU liaison addressed to PWE3 and MPLS WGs

June 2007 ITU-T SG 15 IETF PWE3 and MPLS WGs Response to PWE3 and MPLS 
WG concerns with G.8110.1 Amendment 1

and would appreciate input to a suitable response. This liaison will be 
a topic on the PWE3 agenda.

https://datatracker.ietf.org/liaison/345/

ITU SG15 say:
"It appears that the work in the IETF is addressing some different 
requirements:
“Input from network operators indicates that the key requirements is the 
transparent carriage of the MPLS network of one party over the MPLS 
network of another party, with the constraint that the MPLS design MUST 
NOT be changed and that the solution MUST be compatible with their 
existing large base of already deployed MPLS networks.”

SB - Network operators subscribing to these lists are encouraged to 
indicate whether or not they agree with these two assumptions.

ITU SG 15 say:
"Some members of SG 15 expressed support for these requirements. 
However, the basis for the work in SG 15 has been the development of a 
packet switched network that meets all of the network operators 
transport operations requirements. "

SB - Would be interested in other peoples views on the second sentence - 
is it consistent or contradictory to the proposed constraint that the 
investment in the existing MPLS design and deployment be preserved?

ITU SG 15 say:
"The assumption we have made is that when deploying T-MPLS for this 
purpose it will be deployed on a network that is disjoint from any 
already deployed IP/MPLS network."

SB - As I said in my earlier email, I am concerned about this 
assumption, particularly as I saw a contribution that discussed 
interworking of MPLS and T-MPLS. If the assumption is a design invariant 
it should be designed into the protocol to ensure that it cannot be 
violated.

ITU SG15 say:
"Equipment developed prior to the approval of the T-MPLS Recommendations 
is not expected to comply with these Recommendations."

SB - Again as I stated earlier, I think that we need to note that we are 
not concerned about existing MPLS equipment being compliant with T-MPLS, 
but rather we are concerned that T-MPLS or any future enhancement to 
T-MPLS should not cause a conflict with the installed base of existing 
MPLS equipment, or any future IETF development of MPLS, or that it 
should inhibit some future development of MPLS.

ITU SG 15 Say:
"Our intention in developing the suite of T-MPLS Recommendations is to 
define a packet based transport network technology. The design 
objectives of T-MPLS are:
a) Follow the principles of the transport network used in other ITU-T 
defined transport technologies (e.g SDH, ATM, OTN).
b) To use the PDU and forwarding plane processes defined by the IETF for 
MPLS.
After the presentation of the Liaison Statement the following was noted:
• T-MPLS OAM mechanisms have been developed by ITU-T G.8114/Y.1373 to 
provide transport-like fault and performance monitoring capabilities 
including alarm suppression, packet loss measurements and support of 
multiple ownerships
• T-MPLS protection mechanisms have been developed by ITU-T G.8131 to 
provide transport-like protection schemes including trail and 
sub-network protection
• The separation between the data plane and the control plane is a major 
requirement in transport networks"

SB - I would be interested in the views of the operator community on how 
significant the differences between the TMPLS approach and the IETF 
approach is in these three aspects and whether they justify a whole new 
protocol suit?

What is the view of other members of the IETF?

- Stewart



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



From pwe3-bounces@ietf.org Wed Jul 18 09:19:39 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IB9RF-0000AU-QQ; Wed, 18 Jul 2007 09:19:33 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1IB9RA-0000A7-Kv
	for pwe3-confirm+ok@megatron.ietf.org; Wed, 18 Jul 2007 09:19:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IB9R9-00009j-DC; Wed, 18 Jul 2007 09:19:27 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IB9R8-0000fS-3o; Wed, 18 Jul 2007 09:19:27 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 18 Jul 2007 09:19:25 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CACKwnUZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,550,1175486400"; 
	d="scan'208"; a="126369799:sNHT32345226"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6IDJOW6028706; 
	Wed, 18 Jul 2007 09:19:24 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l6IDJOEZ007996; 
	Wed, 18 Jul 2007 13:19:24 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 18 Jul 2007 09:19:24 -0400
Received: from [10.83.15.54] ([10.83.15.54]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 18 Jul 2007 09:19:23 -0400
In-Reply-To: <469CF012.60905@cisco.com>
References: <469CF012.60905@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed
Message-Id: <C0881A2A-0D2D-44EB-9F2F-155627370597@cisco.com>
Content-Transfer-Encoding: quoted-printable
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Date: Wed, 18 Jul 2007 09:19:19 -0400
To: stbryant@cisco.com
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 18 Jul 2007 13:19:23.0922 (UTC)
	FILETIME=[42342F20:01C7C93E]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4529; t=1184764764;
	x=1185628764; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=tnadeau@cisco.com;
	z=From:=20=22Thomas=20D.=20Nadeau=22=20<tnadeau@cisco.com>
	|Subject:=20Re=3A=20[mpls]=20ITU-T=20SG=2015=20liaison=20-=20G.8110.1=20a
	mendment=201=20(https=3A//datatracker.ietf.org/liaison/344/)
	|Sender:=20 |To:=20stbryant@cisco.com;
	bh=OkAeWRYQkYo/0LC4+uze7kOWmpQB8ACEA6ewqBAyZDY=;
	b=S2ncAsgc0Zie4qp8kqA1Ls90NMvEQ0p1Wl5kJsekUszDCuEvFP+PDrtV4D0Z910Yu3jYKLkR
	ur+mdxmkss+5F3emsT95qwmhEs7bHAJYnIhcg70Gf+1xsM5ANO+dY+to;
Authentication-Results: rtp-dkim-2; header.From=tnadeau@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Cc: mpls@ietf.org, pwe3 <pwe3@ietf.org>
Subject: [PWE3] Re: [mpls] ITU-T SG 15 liaison - G.8110.1 amendment 1
	(https://datatracker.ietf.org/liaison/344/)
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org


On Jul 17, 2007:12:36 PM, at 12:36 PM, Stewart Bryant wrote:

> I have been looking at the ITU liaison addressed to PWE3 and MPLS WGs
>
> June 2007 ITU-T SG 15 IETF PWE3 and MPLS WGs G.8110.1 amendment 1 =20
> (https://datatracker.ietf.org/liaison/344/)
>
> and would appreciate input to a suitable response. This liaison =20
> will be a topic on the PWE3 agenda.
>
> I have removed the elements of the response where SG15 has agree =20
> with our comments and edited their text accordingly.
>
> The following points remain:
>
> Section 3.5 Transport MPLS definition
> "Should be amended to make it clear TMPLS is a true subset of IETF =20
> PWE3 over MPLS and that in the case of any differences, the IETF =20
> definition is considered the Normative definition."
>
> SG15 Response:
> "G.8110.1 describes the behaviour of a T-MPLS network. Following a =20
> discussion of your liaison statement it was agreed to clarify that =20
> T-MPLS uses a subset of the MPLS forwarding plane behaviour. For =20
> OAM only label 14 is used and hence only =93ITU=94 mechanisms are =20
> supported. It is also assumed that MPLS and T-MPLS are deployed as =20
> disjoint networks. An LSP initiated from an IP/MPLS network element =20=

> is encapsulated in Ethernet before it transits a T-MPLS network. =20
> Similarly if IP/MPLS is used as a server layer for T-MPLS then an =20
> LSP initiated from a T-MPLS network element is encapsulated in =20
> Ethernet before it transits an IP/MPLS network. This enforces the =20
> independence of the control planes for T-MPLS and IP/MPLS. Further =20
> as is customary with ITU-T Recommendations, equipment designed =20
> before the approval of the Recommendations is not expected to meet =20
> all the requirements of the new Recommendation."
>
> SB - I have two concerns regarding this:
>
> 1) The statement "assumed that MPLS and T-MPLS are deployed as =20
> disjoint networks" MUST be backed up by some technical means to =20
> ensure that MPLS and T-MPLS remain disjoint, otherwise the =20
> assumption does not hold and someone will attempt interworking. =20
> Indeed a contribution at the ITU meeting that prepared this =20
> response proposed exactly that.
>
> 2) "as is customary with ITU-T Recommendations, equipment designed =20
> before the approval of the Recommendations is not expected to meet =20
> all the requirements of the new Recommendation."
>
> I think that we need to note that we are not concerned about =20
> existing MPLS equipment being compliant with T-MPLS, but rather we =20
> are concerned that T-MPLS or any future enhancement to T-MPLS =20
> should not cause a conflict with the installed base of existing =20
> MPLS equipment, or any future IETF development of MPLS, or that it =20
> should inhibit some future development of MPLS.
>
>
> Section 4.7.2 and A.3
> "The PWE3 WG is concerned that the OAM is not based on VCCV. Any =20
> true subset of the IETF PWE3/MPLS design should allow the use of =20
> the IETF preferred OAM mechanism. This does not preclude the ITU =20
> specifying an additional mechanism as an optional extension to =20
> enhance VCCV, although it would be preferable for the ITU to work =20
> with the IETF to enhance VCCV to provide the additional OAM =20
> mechanisms that are needed."
>
> "At a previous meeting SG 15 decided to base T-MPLS OAM on Y.1711 =20
> and requested Q5/13 to enhance the OAM mechanisms based on Y.1711. =20
> Based on this request Q5/13 developed Y.1373/G.8114, the amendment =20
> to G.8110.1 adds a reference to Y.1373/G.8114. As described above, =20
> we expect T-MPLS and MPLS to be deployed as disjoint networks and =20
> as is customary with ITU-T Recommendations, equipment designed =20
> before the approval of the Recommendations is not expected to meet =20
> all the requirements of the new Recommendation. We do not =20
> anticipate any compatibility issues."
>
> SB - Again, given the existence of a simple solution to ensure that =20=

> no compatibility issue can exist (discriminating codepoint, I do =20
> not believe such anticipation is good enough.
>
> What is the view of other members of the IETF?
=09
	We should (again) return a statement to the above reply
stating that OAM must be based on VCCV, or at least that is
the preferred (default) OAM mechanism. This is only logical if
we (IETF) insist as is asserted above, that PWE3's definition of
PW/MPLS is the normative reference for TMPLS.

	--Tom



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



From pwe3-bounces@ietf.org Wed Jul 18 10:58:26 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBAyo-0002yw-GA; Wed, 18 Jul 2007 10:58:18 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1IBAyi-0002yW-N9
	for pwe3-confirm+ok@megatron.ietf.org; Wed, 18 Jul 2007 10:58:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBAyi-0002yO-Do
	for pwe3@ietf.org; Wed, 18 Jul 2007 10:58:12 -0400
Received: from smail.alcatel.fr ([62.23.212.165])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBAyg-0003Ml-UJ
	for pwe3@ietf.org; Wed, 18 Jul 2007 10:58:12 -0400
Received: from gbmail02.netfr.alcatel.fr (gbmail02.netfr.alcatel.fr
	[155.132.251.26])
	by smail.alcatel.fr (8.13.4/8.13.4/ICT) with ESMTP id l6IEwAri000620;
	Wed, 18 Jul 2007 16:58:10 +0200
To: pwe3@ietf.org
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OF54598D90.7A21E8F7-ON8025731C.0008B2D2-8025731C.00090393@netfr.alcatel.fr>
From: Matthew.Bocci@alcatel-lucent.co.uk
Date: Wed, 18 Jul 2007 02:38:27 +0100
X-MIMETrack: Serialize by Router on GBMAIL02/GB/ALCATEL(Release 5.0.13aHF163 |
	June 23, 2005) at 07/18/2007 15:58:07
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-Scanned-By: MIMEDefang 2.51 on 155.132.180.81
X-Spam-Score: 1.8 (+)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: stbryant@cisco.com, danny@tcb.net
Subject: [PWE3] Chicago slides
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org


If you have a slot to present at the PWE3 meeting at the Chicago IETF,
please can you send me you slides before the end of Saturday 21st July.

Any presenters who do not send their slides risk loosing their slot.

Regards,

Matthew

-----------------------------------------
Matthew Bocci
IP Division,
Alcatel-Lucent Telecom Limited,
Registered Office: Christchurch Way, Greenwich, London SE10 0AG.
Registered in England & Wales number 02650571
-----------------------------------------




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



From pwe3-bounces@ietf.org Mon Jul 23 11:36:33 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ICzvj-0005LK-Oj; Mon, 23 Jul 2007 11:34:39 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1ICzvi-0005LE-Bh
	for pwe3-confirm+ok@megatron.ietf.org; Mon, 23 Jul 2007 11:34:38 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICzvi-0005L6-0k
	for pwe3@ietf.org; Mon, 23 Jul 2007 11:34:38 -0400
Received: from smail.alcatel.fr ([62.23.212.165])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ICzvh-0008GB-Hc
	for pwe3@ietf.org; Mon, 23 Jul 2007 11:34:37 -0400
Received: from gbmail02.netfr.alcatel.fr (gbmail02.netfr.alcatel.fr
	[155.132.251.26])
	by smail.alcatel.fr (8.13.4/8.13.4/ICT) with ESMTP id l6NFYc4F004091
	for <pwe3@ietf.org>; Mon, 23 Jul 2007 17:34:38 +0200
To: pwe3@ietf.org
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OF12F2CF8B.9C0C4E00-ON80257321.00553895-80257321.00557497@netfr.alcatel.fr>
From: Matthew.Bocci@alcatel-lucent.co.uk
Date: Mon, 23 Jul 2007 16:33:24 +0100
X-MIMETrack: Serialize by Router on GBMAIL02/GB/ALCATEL(Release 5.0.13aHF163 |
	June 23, 2005) at 07/23/2007 16:34:35
MIME-Version: 1.0
Content-type: multipart/mixed; 
	Boundary="0__=0FBBF9B2DFC6BE058f9e8a93df938690918c0FBBF9B2DFC6BE05"
Content-Disposition: inline
X-Scanned-By: MIMEDefang 2.51 on 155.132.180.81
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Subject: [PWE3] Updated Chicago agenda
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

--0__=0FBBF9B2DFC6BE058f9e8a93df938690918c0FBBF9B2DFC6BE05
Content-type: text/plain; charset=us-ascii

Please find attached a revised agenda for the PWE3 meeting this afternoon.


Regards,

Matthew

-----------------------------------------
Matthew Bocci
IP Division,
Alcatel-Lucent Telecom Limited,
Registered Office: Christchurch Way, Greenwich, London SE10 0AG.
Registered in England & Wales number 02650571
-----------------------------------------

(See attached file: PWE3-Agenda-02.txt)

--0__=0FBBF9B2DFC6BE058f9e8a93df938690918c0FBBF9B2DFC6BE05
Content-type: application/octet-stream; 
	name="PWE3-Agenda-02.txt"
Content-Disposition: attachment; filename="PWE3-Agenda-02.txt"
Content-transfer-encoding: base64

TU9OREFZLCBKdWx5IDIzcmQsIDIwMDcgLSAxMzowMCAtIDE1OjAwIA0KLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0gDQpDSEFJUlM6IERhbm55IE1jUGhlcnNvbiAmIFN0ZXdhcnQg
QnJ5YW50IA0KIA0KMTUgbWlucyBXRyBTdGF0dXMgYW5kIFVwZGF0ZSAtIENoYWlycyANCiANCjUg
bWlucyAtIFBzZXVkb3dpcmUgVmlydHVhbCBDaXJjdWl0IENvbm5lY3Rpdml0eSBWZXJpZmljYXRp
b24gKFZDQ1YpIEEgQ29udHJvbCAgICAgICAgICAgIA0KQ2hhbm5lbCBmb3IgUHNldWRvd2lyZXMg
LSBUb20gTmFkZWF1ICh0bmFkZWF1QGNpc2NvLmNvbSkgDQpodHRwOi8vd3d3LmlldGYub3JnL2lu
dGVybmV0LWRyYWZ0cy9kcmFmdC1pZXRmLXB3ZTMtdmNjdi0xNC50eHQgDQogDQoxMCBtaW5zIC0g
UHJlZmVyZW50aWFsIEZvcndhcmRpbmcgU3RhdHVzIEJpdCBEZWZpbml0aW9uIC0gTXVzdGFwaGEg
QWlzc2FvdWkgDQoobXVzdGFwaGEuYWlzc2FvdWlAYWxjYXRlbC1sdWNlbnQuY28udWspIA0KaHR0
cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtbXVsZXktZHV0dGEtcHdlMy1y
ZWR1bmRhbmN5LWJpdC0wMS50eHQgDQogDQo1IG1pbnMgLSBNUy1QVyBSZXF1aXJlbWVudHMgLSBM
dWNhIE1hcnRpbmkgKGxtYXJ0aW5pQGNpc2NvLmNvbSkgDQpodHRwOi8vd3d3LmlldGYub3JnL2lu
dGVybmV0LWRyYWZ0cy9kcmFmdC1pZXRmLXB3ZTMtbXMtcHctcmVxdWlyZW1lbnRzLTA1LnR4dCAN
CiANCjUgbWlucyAtIER5bmFtaWMgUGxhY2VtZW50IG9mIE11bHRpIFNlZ21lbnQgUHNldWRvIFdp
cmVzIC0gTHVjYSBNYXJ0aW5pIA0KKGxtYXJ0aW5pQGNpc2NvLmNvbSkgDQpodHRwOi8vd3d3Lmll
dGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZXRmLXB3ZTMtZHluYW1pYy1tcy1wdy0wNS50
eHQgDQogDQoxNSBtaW5zIC0gODAyLjFhaCBQc2V1ZG93aXJlIC0gTHVjYSBNYXJ0aW5pIChsbWFy
dGluaUBjaXNjby5jb20pIA0KaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJh
ZnQtbWFydGluaS1wd2UzLTgwMi4xYWgtcHctMDAudHh0IA0KIA0KMTUgbWlucyAtIFNldHVwIGFu
ZCBNYW5hZ2UgUEJCLWJhc2VkIFR1bm5lbHMgd2l0aCBQV0UzIE1lY2hhbmlzbSAtIFBpbmcgUGFu
IA0KKHBwYW5AaGFtbWVyaGVhZHN5c3RlbXMuY29tKSANCmh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50
ZXJuZXQtZHJhZnRzL2RyYWZ0LXBhbi1wd2UzLXBiYi10dW5uZWxzLTAwLnR4dCANCiANCjE1IG1p
bnMgLSBULU1QTFMgUmVwb3J0IC0gU3Rld2FydCBCcnlhbnQgKHN0YnJ5YW50QGNpc2NvLmNvbSkg
DQpodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZXRmLXB3ZTMtbXBs
cy10cmFuc3BvcnQtMDAudHh0IA0KaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9saWFpc29u
LzM0NS8gDQpodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2xpYWlzb24vMzQ0LyANCiANCjE1
IG1pbnMgLSBQVFAgb3ZlciBNUExTIC0gUm9oIENvaGVuIChyb25jQHJlc29sdXRlbmV0d29ya3Mu
Y29tKSANCmh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LXJvbmMtcHRw
LW1wbHMtMDAudHh0IA0KIA0KIA0KIAw=

--0__=0FBBF9B2DFC6BE058f9e8a93df938690918c0FBBF9B2DFC6BE05
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://www1.ietf.org/mailman/listinfo/pwe3

--0__=0FBBF9B2DFC6BE058f9e8a93df938690918c0FBBF9B2DFC6BE05--






From pwe3-bounces@ietf.org Mon Jul 23 15:02:07 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID3AT-0007yw-SU; Mon, 23 Jul 2007 15:02:05 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1ID3AS-0007yL-J0
	for pwe3-confirm+ok@megatron.ietf.org; Mon, 23 Jul 2007 15:02:04 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID3AS-0007y6-7H
	for pwe3@ietf.org; Mon, 23 Jul 2007 15:02:04 -0400
Received: from audl953.usa.alcatel.com ([143.209.238.162])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ID3AQ-0006q0-K6
	for pwe3@ietf.org; Mon, 23 Jul 2007 15:02:03 -0400
Received: from usdalsbhs02.ad3.ad.alcatel.com (usdalsbhs02.usa.alcatel.com
	[172.22.216.13])
	by audl953.usa.alcatel.com (ALCANET) with ESMTP id l6NJ1x9A007073;
	Mon, 23 Jul 2007 14:01:59 -0500
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by
	usdalsbhs02.ad3.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Mon, 23 Jul 2007 14:01:58 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Date: Mon, 23 Jul 2007 14:02:10 -0500
Message-ID: <40B2D3B1A8D67246A33D2F5B832C17E774B34D@USDALSMBS03.ad3.ad.alcatel.com>
In-Reply-To: <469404C5.20402@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Thread-Index: AcfDP93V3KaZMetPTbKxdSOqhKCpyAKGuAmg
From: "KOMPELLA Vach" <Vach.Kompella@alcatel-lucent.com>
To: "Luca Martini" <lmartini@cisco.com>,
	"Ali Sajassi \(sajassi\)" <sajassi@cisco.com>
X-OriginalArrivalTime: 23 Jul 2007 19:01:58.0912 (UTC)
	FILETIME=[F1FF8000:01C7CD5B]
X-Scanned-By: MIMEDefang 2.51 on 143.209.238.34
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff0adf256e4dd459cc25215cfa732ac1
Cc: "Attila Takacs \(IJ/ETH\)" <Attila.Takacs@ericsson.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

I don't see why we need this.  It sounds like a signaling method to
optimize what may or may not be achievable in hardware.

It's deja vu all over again with the tagged Ethernet PW which pretty
much was defined, IMHO, because of harware limitations.  By the time
ethernet services became a well-defined, those hardware limitations were
overcome, and the tagged PW has already become obsolete.

I say just process the I-Tag in the NSP.

-Vach =20

> -----Original Message-----
> From: Luca Martini [mailto:lmartini@cisco.com]=20
> Sent: Tuesday, July 10, 2007 3:14 PM
> To: Ali Sajassi (sajassi)
> Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> Subject: [PWE3] Re: Some comments on=20
> draft-martini-pwe3-802.1ah-pw-00.txt
>=20
> Hello!
>=20
> More comments inline.
>=20
> Ali Sajassi (sajassi) wrote:
> > Hi Attila,
> >
> > Thanks for your comments. Please see my reply inline ....=20
> >
> >  =20
> >> -----Original Message-----
> >> From: Attila Takacs (IJ/ETH) [mailto:Attila.Takacs@ericsson.com]
> >> Sent: Tuesday, July 10, 2007 9:41 AM
> >> To: Luca Martini (lmartini); Ali Sajassi (sajassi)
> >> Subject: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
> >>
> >> Hi Luca and Ali,
> >>
> >> I just saw your draft on the pwe3 agenda...
> >> It is a useful proposal, please find some=20
> comments/suggestions below=20
> >> which you might consider for a new revision.
> >>
> >> Best regards,
> >> Attila
> >> Ps.:I noticed that this is a 00 version, so sorry if you think the=20
> >> comments are too editorial
> >>
> >>
> >> -Section 2, it seems to be more a terminology/definition=20
> section than=20
> >> acronyms The following definitions would be useful as well:
> >>
> >> Service Instance Drop Eligibility Indicator (I-DEI): A=20
> field of the=20
> >> I-TAG which identifies the Service Instance Drop=20
> Eligibility of the=20
> >> frame in the 802.1ah (PBBN) domain.
> >>
> >> Service instance priority code point (I-PCP): A field of the I-TAG=20
> >> which identifies the service instance priority of the frame in the=20
> >> 802.1ah
> >> (PBBN) domain.
> >>
> >> I-tagged Service Interface: A 802.1ah (PBBN) interface type over=20
> >> which an I-TAG immediately follows the destination and source MAC=20
> >> addresses in the header of the Ethernet frames.
> >>
> >>    =20
> >
> >  =20
> Yes,  I also agree , we'll add these.
> > Agree, since they are used in the text, it make sense to=20
> define them=20
> > up front.
> >
> >  =20
> >> A note may be appropriate saying that: These definitions will be=20
> >> removed in later versions by a reference to the appropriate IEEE=20
> >> standard.
> >>
> >>    =20
> >
> > I think it still would be good to keep these definitions in=20
> the draft=20
> > for sake of completeness.
> >
> >
> >  =20
> Yes, It's really a compromise between how much we repeat in a=20
> document , and how much we want the document to be clear.
>=20
> I usually err more on the clear side.
>=20
> >> -Section 4 Applicability
> >> In the first paragraph I'm considering if "I-SID to I-SID"=20
> >> should not be changed to "I-tagged interface to I-tagged=20
> interface".=20
> >> I recognize that this might be more limiting from an AC=20
> point of view=20
> >> but isn't this the intention?
> >>
> >>    =20
> >
> > "I-SID to I-SID" is correct since it is used to connect two I-SID=20
> > aware forwarder rather than two Acs - e.g., AC may not be=20
> an I-tagged=20
> > service interface but still we want to provide full-mesh of PW on a=20
> > per I-SID basis.
> >
> >  =20
> We can certainly change this definition , but in general the=20
> other encap drafts are written with respect to an AC.
> I just wanted to keep this one consistent.
>=20
> >> After this paragraph something like "In contrast to the=20
> VLAN (tagged
> >> mode) where 2^12 customer service instances can be=20
> distinguished, the=20
> >> I-SID in the I-TAG increases scalability by allowing 2^24 service=20
> >> instances." might highlight one important aspect of the VLAN and=20
> >> I-SID scenario.
> >>
> >>    =20
> >
> > Since we are using one PW per I-SID, this scalability aspect of=20
> > I-tagged is not used in our case.
> >
> >  =20
> >> In the discussion further below in Section 4 "I-SID aware"=20
> >> forwarders should be "I-TAG aware" forwarders. For=20
> instance for the=20
> >> QoS discussions not only the I-SID but also the I-PCP and=20
> I-DEI may=20
> >> be considered.
> >>
> >> Further, in the case of native CFM Ethernet OAM and PW OAM=20
> >> interworking I can imagine that the No Customer Addresses
> >> (NCA) field of the I-TAG may be considered by the NSP and/or=20
> >> forwarder.
> >>
> >>    =20
> > =20
> > Agree.
> >
> >  =20
> ok.
> >> -Regarding Sections 5 and 6, I do not see the benefit of repeating=20
> >> general PW encapsulation procedures. In my read only 6.2=20
> provides new=20
> >> information about the I-tagged mode all other discussion could be=20
> >> removed with no harm and instead a pointer to the already=20
> defined PW=20
> >> procedures could be added.
> >> (Do I mis something?)
> >>
> >>    =20
> >
> > I guess it is there for sake of completeness. It is up to Luca to=20
> > decide what to do with it.
> >
> >  =20
> I think that I would like to avoid too many recursive=20
> reference to other documents. This document needs to explain=20
> how to implement the PW without too many references.
>=20
> >  =20
> >> It would be beneficial to add a figure focusing on the I-tagged=20
> >> Ethernet header and its PW encapsulation, something like this:
> >>
> >> 	AC				PW
> >> 	        Forwarder
> >> ------------		------------
> >> |   Data   |    		|   Data   |=20
> >> |----------|		|----------|
> >> |Other TAGs|		|Other TAGs|
> >> |----------|  		|----------|
> >> |  I-TAG   | ----|	|  I-TAG   |
> >> |----------|     |	|----------|
> >> |  SA MAC  |     |	|  SA MAC  |=20
> >> |----------|     |	|----------|
> >> |  DA MAC  |     |	|  DA MAC  |
> >> ------------     |	|----------|
> >> 		     +-->	|Encap (CW)|
> >> 		     |	|----------|
> >> 		     +-->	|   Demux  |
> >> 		 		|----------|
> >> 		     		|PSN tunnel|
> >> 				------------
> >>
> >>
> >>
> >>    =20
> Yes, this is a very good idea.  Is this figure what we want ?=20
> No other tags shown ?
>=20
> Thanks.
> Luca
>=20
> > =20
> > Agree, I think such figure would be helpful.
> >
> > Thanks again for your comments,
> > Ali
> >
> >  =20
> >>
> >>    =20
> >
> >  =20
>=20
>=20
>=20
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
>=20


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



From pwe3-bounces@ietf.org Tue Jul 24 01:58:18 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDDPR-00072G-94; Tue, 24 Jul 2007 01:58:13 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1IDDPP-000728-Qe
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 01:58:11 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDDPP-00071X-Cy
	for pwe3@ietf.org; Tue, 24 Jul 2007 01:58:11 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDDPO-0004iU-8z
	for pwe3@ietf.org; Tue, 24 Jul 2007 01:58:11 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-2.cisco.com with ESMTP; 23 Jul 2007 22:58:10 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAE4xpUarR7PD/2dsb2JhbAA
X-IronPort-AV: i="4.16,572,1175497200"; 
	d="scan'208"; a="387620936:sNHT36665808"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l6O5w9Ns011546; 
	Mon, 23 Jul 2007 22:58:09 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l6O5w96C009669;
	Tue, 24 Jul 2007 05:58:09 GMT
Received: from xmb-sjc-21e.amer.cisco.com ([171.70.151.156]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 23 Jul 2007 22:58:08 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Date: Mon, 23 Jul 2007 22:58:06 -0700
Message-ID: <75B2A84D9323BC4CA3977CF378CE75EB038FDB35@xmb-sjc-21e.amer.cisco.com>
In-Reply-To: <40B2D3B1A8D67246A33D2F5B832C17E774B34D@USDALSMBS03.ad3.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Thread-Index: AcfDP93V3KaZMetPTbKxdSOqhKCpyAKGuAmgABcDk/A=
From: "Ali Sajassi \(sajassi\)" <sajassi@cisco.com>
To: "KOMPELLA Vach" <Vach.Kompella@alcatel-lucent.com>,
	"Luca Martini \(lmartini\)" <lmartini@cisco.com>
X-OriginalArrivalTime: 24 Jul 2007 05:58:08.0988 (UTC)
	FILETIME=[9C6459C0:01C7CDB7]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=7991; t=1185256689;
	x=1186120689; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=sajassi@cisco.com;
	z=From:=20=22Ali=20Sajassi=20\(sajassi\)=22=20<sajassi@cisco.com>
	|Subject:=20RE=3A=20[PWE3]=20Re=3A=20Some=20comments=20on=20draft-martini
	-pwe3-802.1ah-pw-00.txt |Sender:=20;
	bh=IDJjkrHd4iFxcrtnZiQS1ouqk4NM9pbxW3TdFu/Geew=;
	b=SihiCA53OIKhUH75r0iJmYO7G9l2IHjOqWJqy50u4Ig5P/J+UJGzn5Xbq6eONK2STvrJP1AO
	jMZbATH6wm/+M9k7DtyMjqMthsx7U3U+VVFqLISwyZB1ZOa830w8dq65;
Authentication-Results: sj-dkim-3; header.From=sajassi@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 03fb21b15d5177c512a4caa19876f30a
Cc: "Attila Takacs \(IJ/ETH\)" <Attila.Takacs@ericsson.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org



Vach,

I think you are missing the point that in case of a raw-mode PW, when
you remove the VLAN tag you still end up with a valid Ethernet frame;
however, there is no equivalent for I-tagged frames - e.g., when you
remove the I-SID from an I-tagged frame, you end up with an invalid
Ethernet frame. Besides this, refer to the other reasons in the draft as
to why have the new PW type.

-Ali=20
=20

> -----Original Message-----
> From: KOMPELLA Vach [mailto:Vach.Kompella@alcatel-lucent.com]=20
> Sent: Monday, July 23, 2007 12:02 PM
> To: Luca Martini (lmartini); Ali Sajassi (sajassi)
> Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> Subject: RE: [PWE3] Re: Some comments on=20
> draft-martini-pwe3-802.1ah-pw-00.txt
>=20
> I don't see why we need this.  It sounds like a signaling=20
> method to optimize what may or may not be achievable in hardware.
>=20
> It's deja vu all over again with the tagged Ethernet PW which=20
> pretty much was defined, IMHO, because of harware=20
> limitations.  By the time ethernet services became a=20
> well-defined, those hardware limitations were overcome, and=20
> the tagged PW has already become obsolete.
>=20
> I say just process the I-Tag in the NSP.
>=20
> -Vach =20
>=20
> > -----Original Message-----
> > From: Luca Martini [mailto:lmartini@cisco.com]
> > Sent: Tuesday, July 10, 2007 3:14 PM
> > To: Ali Sajassi (sajassi)
> > Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> > Subject: [PWE3] Re: Some comments on
> > draft-martini-pwe3-802.1ah-pw-00.txt
> >=20
> > Hello!
> >=20
> > More comments inline.
> >=20
> > Ali Sajassi (sajassi) wrote:
> > > Hi Attila,
> > >
> > > Thanks for your comments. Please see my reply inline ....=20
> > >
> > >  =20
> > >> -----Original Message-----
> > >> From: Attila Takacs (IJ/ETH) [mailto:Attila.Takacs@ericsson.com]
> > >> Sent: Tuesday, July 10, 2007 9:41 AM
> > >> To: Luca Martini (lmartini); Ali Sajassi (sajassi)
> > >> Subject: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
> > >>
> > >> Hi Luca and Ali,
> > >>
> > >> I just saw your draft on the pwe3 agenda...
> > >> It is a useful proposal, please find some
> > comments/suggestions below
> > >> which you might consider for a new revision.
> > >>
> > >> Best regards,
> > >> Attila
> > >> Ps.:I noticed that this is a 00 version, so sorry if you=20
> think the=20
> > >> comments are too editorial
> > >>
> > >>
> > >> -Section 2, it seems to be more a terminology/definition
> > section than
> > >> acronyms The following definitions would be useful as well:
> > >>
> > >> Service Instance Drop Eligibility Indicator (I-DEI): A
> > field of the
> > >> I-TAG which identifies the Service Instance Drop
> > Eligibility of the
> > >> frame in the 802.1ah (PBBN) domain.
> > >>
> > >> Service instance priority code point (I-PCP): A field of=20
> the I-TAG=20
> > >> which identifies the service instance priority of the=20
> frame in the=20
> > >> 802.1ah
> > >> (PBBN) domain.
> > >>
> > >> I-tagged Service Interface: A 802.1ah (PBBN) interface type over=20
> > >> which an I-TAG immediately follows the destination and=20
> source MAC=20
> > >> addresses in the header of the Ethernet frames.
> > >>
> > >>    =20
> > >
> > >  =20
> > Yes,  I also agree , we'll add these.
> > > Agree, since they are used in the text, it make sense to
> > define them
> > > up front.
> > >
> > >  =20
> > >> A note may be appropriate saying that: These definitions will be=20
> > >> removed in later versions by a reference to the appropriate IEEE=20
> > >> standard.
> > >>
> > >>    =20
> > >
> > > I think it still would be good to keep these definitions in
> > the draft
> > > for sake of completeness.
> > >
> > >
> > >  =20
> > Yes, It's really a compromise between how much we repeat in=20
> a document=20
> > , and how much we want the document to be clear.
> >=20
> > I usually err more on the clear side.
> >=20
> > >> -Section 4 Applicability
> > >> In the first paragraph I'm considering if "I-SID to I-SID"=20
> > >> should not be changed to "I-tagged interface to I-tagged
> > interface".=20
> > >> I recognize that this might be more limiting from an AC
> > point of view
> > >> but isn't this the intention?
> > >>
> > >>    =20
> > >
> > > "I-SID to I-SID" is correct since it is used to connect two I-SID=20
> > > aware forwarder rather than two Acs - e.g., AC may not be
> > an I-tagged
> > > service interface but still we want to provide full-mesh=20
> of PW on a=20
> > > per I-SID basis.
> > >
> > >  =20
> > We can certainly change this definition , but in general the other=20
> > encap drafts are written with respect to an AC.
> > I just wanted to keep this one consistent.
> >=20
> > >> After this paragraph something like "In contrast to the
> > VLAN (tagged
> > >> mode) where 2^12 customer service instances can be
> > distinguished, the
> > >> I-SID in the I-TAG increases scalability by allowing=20
> 2^24 service=20
> > >> instances." might highlight one important aspect of the VLAN and=20
> > >> I-SID scenario.
> > >>
> > >>    =20
> > >
> > > Since we are using one PW per I-SID, this scalability aspect of=20
> > > I-tagged is not used in our case.
> > >
> > >  =20
> > >> In the discussion further below in Section 4 "I-SID aware"=20
> > >> forwarders should be "I-TAG aware" forwarders. For
> > instance for the
> > >> QoS discussions not only the I-SID but also the I-PCP and
> > I-DEI may
> > >> be considered.
> > >>
> > >> Further, in the case of native CFM Ethernet OAM and PW OAM=20
> > >> interworking I can imagine that the No Customer Addresses
> > >> (NCA) field of the I-TAG may be considered by the NSP and/or=20
> > >> forwarder.
> > >>
> > >>    =20
> > > =20
> > > Agree.
> > >
> > >  =20
> > ok.
> > >> -Regarding Sections 5 and 6, I do not see the benefit of=20
> repeating=20
> > >> general PW encapsulation procedures. In my read only 6.2
> > provides new
> > >> information about the I-tagged mode all other discussion=20
> could be=20
> > >> removed with no harm and instead a pointer to the already
> > defined PW
> > >> procedures could be added.
> > >> (Do I mis something?)
> > >>
> > >>    =20
> > >
> > > I guess it is there for sake of completeness. It is up to Luca to=20
> > > decide what to do with it.
> > >
> > >  =20
> > I think that I would like to avoid too many recursive reference to=20
> > other documents. This document needs to explain how to=20
> implement the=20
> > PW without too many references.
> >=20
> > >  =20
> > >> It would be beneficial to add a figure focusing on the I-tagged=20
> > >> Ethernet header and its PW encapsulation, something like this:
> > >>
> > >> 	AC				PW
> > >> 	        Forwarder
> > >> ------------		------------
> > >> |   Data   |    		|   Data   |=20
> > >> |----------|		|----------|
> > >> |Other TAGs|		|Other TAGs|
> > >> |----------|  		|----------|
> > >> |  I-TAG   | ----|	|  I-TAG   |
> > >> |----------|     |	|----------|
> > >> |  SA MAC  |     |	|  SA MAC  |=20
> > >> |----------|     |	|----------|
> > >> |  DA MAC  |     |	|  DA MAC  |
> > >> ------------     |	|----------|
> > >> 		     +-->	|Encap (CW)|
> > >> 		     |	|----------|
> > >> 		     +-->	|   Demux  |
> > >> 		 		|----------|
> > >> 		     		|PSN tunnel|
> > >> 				------------
> > >>
> > >>
> > >>
> > >>    =20
> > Yes, this is a very good idea.  Is this figure what we want ?=20
> > No other tags shown ?
> >=20
> > Thanks.
> > Luca
> >=20
> > > =20
> > > Agree, I think such figure would be helpful.
> > >
> > > Thanks again for your comments,
> > > Ali
> > >
> > >  =20
> > >>
> > >>    =20
> > >
> > >  =20
> >=20
> >=20
> >=20
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pwe3
> >=20
>=20


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



From pwe3-bounces@ietf.org Tue Jul 24 03:16:16 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDEcu-0000Au-MT; Tue, 24 Jul 2007 03:16:12 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1IDEct-00007l-6T
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 03:16:11 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDEcs-00007c-DU
	for pwe3@ietf.org; Tue, 24 Jul 2007 03:16:10 -0400
Received: from audl951.usa.alcatel.com ([143.209.238.161])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDEcq-0006L9-RB
	for pwe3@ietf.org; Tue, 24 Jul 2007 03:16:09 -0400
Received: from usdalsbhs02.ad3.ad.alcatel.com (usdalsbhs02.usa.alcatel.com
	[172.22.216.13])
	by audl951.usa.alcatel.com (ALCANET) with ESMTP id l6O7G5oB005375;
	Tue, 24 Jul 2007 02:16:05 -0500
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by
	usdalsbhs02.ad3.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Tue, 24 Jul 2007 02:16:05 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Date: Tue, 24 Jul 2007 02:16:17 -0500
Message-ID: <40B2D3B1A8D67246A33D2F5B832C17E774B3C9@USDALSMBS03.ad3.ad.alcatel.com>
In-Reply-To: <75B2A84D9323BC4CA3977CF378CE75EB038FDB35@xmb-sjc-21e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Thread-Index: AcfDP93V3KaZMetPTbKxdSOqhKCpyAKGuAmgABcDk/AAAup9MA==
From: "KOMPELLA Vach" <Vach.Kompella@alcatel-lucent.com>
To: "Ali Sajassi \(sajassi\)" <sajassi@cisco.com>,
	"Luca Martini \(lmartini\)" <lmartini@cisco.com>
X-OriginalArrivalTime: 24 Jul 2007 07:16:05.0188 (UTC)
	FILETIME=[7F9FD840:01C7CDC2]
X-Scanned-By: MIMEDefang 2.51 on 143.209.238.34
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 453b1bfcf0292bffe4cab90ba115f503
Cc: "Attila Takacs \(IJ/ETH\)" <Attila.Takacs@ericsson.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

So don't use the raw mode.  Since we have the tagged mode, we might as
well find a good use for it.

-Vach =20

> -----Original Message-----
> From: Ali Sajassi (sajassi) [mailto:sajassi@cisco.com]=20
> Sent: Monday, July 23, 2007 10:58 PM
> To: KOMPELLA Vach; Luca Martini (lmartini)
> Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> Subject: RE: [PWE3] Re: Some comments on=20
> draft-martini-pwe3-802.1ah-pw-00.txt
>=20
>=20
>=20
> Vach,
>=20
> I think you are missing the point that in case of a raw-mode=20
> PW, when you remove the VLAN tag you still end up with a=20
> valid Ethernet frame; however, there is no equivalent for=20
> I-tagged frames - e.g., when you remove the I-SID from an=20
> I-tagged frame, you end up with an invalid Ethernet frame.=20
> Besides this, refer to the other reasons in the draft as to=20
> why have the new PW type.
>=20
> -Ali=20
> =20
>=20
> > -----Original Message-----
> > From: KOMPELLA Vach [mailto:Vach.Kompella@alcatel-lucent.com]
> > Sent: Monday, July 23, 2007 12:02 PM
> > To: Luca Martini (lmartini); Ali Sajassi (sajassi)
> > Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> > Subject: RE: [PWE3] Re: Some comments on=20
> > draft-martini-pwe3-802.1ah-pw-00.txt
> >=20
> > I don't see why we need this.  It sounds like a signaling method to=20
> > optimize what may or may not be achievable in hardware.
> >=20
> > It's deja vu all over again with the tagged Ethernet PW=20
> which pretty=20
> > much was defined, IMHO, because of harware limitations.  By=20
> the time=20
> > ethernet services became a well-defined, those hardware limitations=20
> > were overcome, and the tagged PW has already become obsolete.
> >=20
> > I say just process the I-Tag in the NSP.
> >=20
> > -Vach
> >=20
> > > -----Original Message-----
> > > From: Luca Martini [mailto:lmartini@cisco.com]
> > > Sent: Tuesday, July 10, 2007 3:14 PM
> > > To: Ali Sajassi (sajassi)
> > > Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> > > Subject: [PWE3] Re: Some comments on=20
> > > draft-martini-pwe3-802.1ah-pw-00.txt
> > >=20
> > > Hello!
> > >=20
> > > More comments inline.
> > >=20
> > > Ali Sajassi (sajassi) wrote:
> > > > Hi Attila,
> > > >
> > > > Thanks for your comments. Please see my reply inline ....=20
> > > >
> > > >  =20
> > > >> -----Original Message-----
> > > >> From: Attila Takacs (IJ/ETH)=20
> [mailto:Attila.Takacs@ericsson.com]
> > > >> Sent: Tuesday, July 10, 2007 9:41 AM
> > > >> To: Luca Martini (lmartini); Ali Sajassi (sajassi)
> > > >> Subject: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
> > > >>
> > > >> Hi Luca and Ali,
> > > >>
> > > >> I just saw your draft on the pwe3 agenda...
> > > >> It is a useful proposal, please find some
> > > comments/suggestions below
> > > >> which you might consider for a new revision.
> > > >>
> > > >> Best regards,
> > > >> Attila
> > > >> Ps.:I noticed that this is a 00 version, so sorry if you
> > think the
> > > >> comments are too editorial
> > > >>
> > > >>
> > > >> -Section 2, it seems to be more a terminology/definition
> > > section than
> > > >> acronyms The following definitions would be useful as well:
> > > >>
> > > >> Service Instance Drop Eligibility Indicator (I-DEI): A
> > > field of the
> > > >> I-TAG which identifies the Service Instance Drop
> > > Eligibility of the
> > > >> frame in the 802.1ah (PBBN) domain.
> > > >>
> > > >> Service instance priority code point (I-PCP): A field of
> > the I-TAG
> > > >> which identifies the service instance priority of the
> > frame in the
> > > >> 802.1ah
> > > >> (PBBN) domain.
> > > >>
> > > >> I-tagged Service Interface: A 802.1ah (PBBN) interface=20
> type over=20
> > > >> which an I-TAG immediately follows the destination and
> > source MAC
> > > >> addresses in the header of the Ethernet frames.
> > > >>
> > > >>    =20
> > > >
> > > >  =20
> > > Yes,  I also agree , we'll add these.
> > > > Agree, since they are used in the text, it make sense to
> > > define them
> > > > up front.
> > > >
> > > >  =20
> > > >> A note may be appropriate saying that: These=20
> definitions will be=20
> > > >> removed in later versions by a reference to the=20
> appropriate IEEE=20
> > > >> standard.
> > > >>
> > > >>    =20
> > > >
> > > > I think it still would be good to keep these definitions in
> > > the draft
> > > > for sake of completeness.
> > > >
> > > >
> > > >  =20
> > > Yes, It's really a compromise between how much we repeat in
> > a document
> > > , and how much we want the document to be clear.
> > >=20
> > > I usually err more on the clear side.
> > >=20
> > > >> -Section 4 Applicability
> > > >> In the first paragraph I'm considering if "I-SID to I-SID"=20
> > > >> should not be changed to "I-tagged interface to I-tagged
> > > interface".=20
> > > >> I recognize that this might be more limiting from an AC
> > > point of view
> > > >> but isn't this the intention?
> > > >>
> > > >>    =20
> > > >
> > > > "I-SID to I-SID" is correct since it is used to connect=20
> two I-SID=20
> > > > aware forwarder rather than two Acs - e.g., AC may not be
> > > an I-tagged
> > > > service interface but still we want to provide full-mesh
> > of PW on a
> > > > per I-SID basis.
> > > >
> > > >  =20
> > > We can certainly change this definition , but in general=20
> the other=20
> > > encap drafts are written with respect to an AC.
> > > I just wanted to keep this one consistent.
> > >=20
> > > >> After this paragraph something like "In contrast to the
> > > VLAN (tagged
> > > >> mode) where 2^12 customer service instances can be
> > > distinguished, the
> > > >> I-SID in the I-TAG increases scalability by allowing
> > 2^24 service
> > > >> instances." might highlight one important aspect of=20
> the VLAN and=20
> > > >> I-SID scenario.
> > > >>
> > > >>    =20
> > > >
> > > > Since we are using one PW per I-SID, this scalability aspect of=20
> > > > I-tagged is not used in our case.
> > > >
> > > >  =20
> > > >> In the discussion further below in Section 4 "I-SID aware"=20
> > > >> forwarders should be "I-TAG aware" forwarders. For
> > > instance for the
> > > >> QoS discussions not only the I-SID but also the I-PCP and
> > > I-DEI may
> > > >> be considered.
> > > >>
> > > >> Further, in the case of native CFM Ethernet OAM and PW OAM=20
> > > >> interworking I can imagine that the No Customer Addresses
> > > >> (NCA) field of the I-TAG may be considered by the NSP and/or=20
> > > >> forwarder.
> > > >>
> > > >>    =20
> > > > =20
> > > > Agree.
> > > >
> > > >  =20
> > > ok.
> > > >> -Regarding Sections 5 and 6, I do not see the benefit of
> > repeating
> > > >> general PW encapsulation procedures. In my read only 6.2
> > > provides new
> > > >> information about the I-tagged mode all other discussion
> > could be
> > > >> removed with no harm and instead a pointer to the already
> > > defined PW
> > > >> procedures could be added.
> > > >> (Do I mis something?)
> > > >>
> > > >>    =20
> > > >
> > > > I guess it is there for sake of completeness. It is up=20
> to Luca to=20
> > > > decide what to do with it.
> > > >
> > > >  =20
> > > I think that I would like to avoid too many recursive=20
> reference to=20
> > > other documents. This document needs to explain how to
> > implement the
> > > PW without too many references.
> > >=20
> > > >  =20
> > > >> It would be beneficial to add a figure focusing on the=20
> I-tagged=20
> > > >> Ethernet header and its PW encapsulation, something like this:
> > > >>
> > > >> 	AC				PW
> > > >> 	        Forwarder
> > > >> ------------		------------
> > > >> |   Data   |    		|   Data   |=20
> > > >> |----------|		|----------|
> > > >> |Other TAGs|		|Other TAGs|
> > > >> |----------|  		|----------|
> > > >> |  I-TAG   | ----|	|  I-TAG   |
> > > >> |----------|     |	|----------|
> > > >> |  SA MAC  |     |	|  SA MAC  |=20
> > > >> |----------|     |	|----------|
> > > >> |  DA MAC  |     |	|  DA MAC  |
> > > >> ------------     |	|----------|
> > > >> 		     +-->	|Encap (CW)|
> > > >> 		     |	|----------|
> > > >> 		     +-->	|   Demux  |
> > > >> 		 		|----------|
> > > >> 		     		|PSN tunnel|
> > > >> 				------------
> > > >>
> > > >>
> > > >>
> > > >>    =20
> > > Yes, this is a very good idea.  Is this figure what we want ?=20
> > > No other tags shown ?
> > >=20
> > > Thanks.
> > > Luca
> > >=20
> > > > =20
> > > > Agree, I think such figure would be helpful.
> > > >
> > > > Thanks again for your comments,
> > > > Ali
> > > >
> > > >  =20
> > > >>
> > > >>    =20
> > > >
> > > >  =20
> > >=20
> > >=20
> > >=20
> > > _______________________________________________
> > > pwe3 mailing list
> > > pwe3@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pwe3
> > >=20
> >=20
>=20


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



From pwe3-bounces@ietf.org Tue Jul 24 05:02:01 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDGHG-0001uA-If; Tue, 24 Jul 2007 05:01:59 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1IDGHE-0001tl-JA
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 05:01:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDGHD-0001tb-Pe
	for pwe3@ietf.org; Tue, 24 Jul 2007 05:01:55 -0400
Received: from szxga03-in.huawei.com ([61.144.161.55])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDGHB-0000EI-Rc
	for pwe3@ietf.org; Tue, 24 Jul 2007 05:01:55 -0400
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JLO00K51EE1T1@szxga03-in.huawei.com> for
	pwe3@ietf.org; Tue, 24 Jul 2007 17:01:13 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JLO0057JEDZX7@szxga03-in.huawei.com> for
	pwe3@ietf.org; Tue, 24 Jul 2007 17:01:13 +0800 (CST)
Received: from c50408 ([10.111.12.62])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JLO008ILEDY4Q@szxml03-in.huawei.com> for
	pwe3@ietf.org; Tue, 24 Jul 2007 17:01:11 +0800 (CST)
Date: Tue, 24 Jul 2007 17:01:10 +0800
From: Cao Wei <caowayne@huawei.com>
Subject: Re: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
To: "Ali Sajassi (sajassi)" <sajassi@cisco.com>,
	KOMPELLA Vach <Vach.Kompella@alcatel-lucent.com>,
	"Luca Martini (lmartini)" <lmartini@cisco.com>
Message-id: <005201c7cdd1$2e20f800$3e0c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <75B2A84D9323BC4CA3977CF378CE75EB038FDB35@xmb-sjc-21e.amer.cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f8ee348dcc4be4a59bc395f7cd6343ad
Cc: "Attila Takacs \(IJ/ETH\)" <Attila.Takacs@ericsson.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Hi Ali,
    I agree with you that a new mode for 802.1ah should be considered.  NSP can do something but I don't think it can 
cover all necessary functionalities.
   Here are a few comments about the draft. 
   1. In "Applicability Statement " section,  why is only homogeneous Ethernet frame supported? 
   2. And is there a need to do some extension for LDP for PE request/ability exchanging?
  
    Since I am not in Chicago and the audio file is not put to web site yet, I don't know the opinions from other people. I would
like to see this draft going forward. In fact I have made a presentation and proposed a draft (draft-cao-pwe3-eth-802.1ah-00.txt) 
in IETF 67 for similar topic.  

Cao Wei
  
----- Original Message ----- 
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: "KOMPELLA Vach" <Vach.Kompella@alcatel-lucent.com>; "Luca Martini (lmartini)" <lmartini@cisco.com>
Cc: "Attila Takacs (IJ/ETH)" <Attila.Takacs@ericsson.com>; "PWE3 WG (E-mail)" <pwe3@ietf.org>
Sent: Tuesday, July 24, 2007 1:58 PM
Subject: RE: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt




Vach,

I think you are missing the point that in case of a raw-mode PW, when
you remove the VLAN tag you still end up with a valid Ethernet frame;
however, there is no equivalent for I-tagged frames - e.g., when you
remove the I-SID from an I-tagged frame, you end up with an invalid
Ethernet frame. Besides this, refer to the other reasons in the draft as
to why have the new PW type.

-Ali 
 

> -----Original Message-----
> From: KOMPELLA Vach [mailto:Vach.Kompella@alcatel-lucent.com] 
> Sent: Monday, July 23, 2007 12:02 PM
> To: Luca Martini (lmartini); Ali Sajassi (sajassi)
> Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> Subject: RE: [PWE3] Re: Some comments on 
> draft-martini-pwe3-802.1ah-pw-00.txt
> 
> I don't see why we need this.  It sounds like a signaling 
> method to optimize what may or may not be achievable in hardware.
> 
> It's deja vu all over again with the tagged Ethernet PW which 
> pretty much was defined, IMHO, because of harware 
> limitations.  By the time ethernet services became a 
> well-defined, those hardware limitations were overcome, and 
> the tagged PW has already become obsolete.
> 
> I say just process the I-Tag in the NSP.
> 
> -Vach  
> 
> > -----Original Message-----
> > From: Luca Martini [mailto:lmartini@cisco.com]
> > Sent: Tuesday, July 10, 2007 3:14 PM
> > To: Ali Sajassi (sajassi)
> > Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> > Subject: [PWE3] Re: Some comments on
> > draft-martini-pwe3-802.1ah-pw-00.txt
> > 
> > Hello!
> > 
> > More comments inline.
> > 
> > Ali Sajassi (sajassi) wrote:
> > > Hi Attila,
> > >
> > > Thanks for your comments. Please see my reply inline .... 
> > >
> > >   
> > >> -----Original Message-----
> > >> From: Attila Takacs (IJ/ETH) [mailto:Attila.Takacs@ericsson.com]
> > >> Sent: Tuesday, July 10, 2007 9:41 AM
> > >> To: Luca Martini (lmartini); Ali Sajassi (sajassi)
> > >> Subject: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
> > >>
> > >> Hi Luca and Ali,
> > >>
> > >> I just saw your draft on the pwe3 agenda...
> > >> It is a useful proposal, please find some
> > comments/suggestions below
> > >> which you might consider for a new revision.
> > >>
> > >> Best regards,
> > >> Attila
> > >> Ps.:I noticed that this is a 00 version, so sorry if you 
> think the 
> > >> comments are too editorial
> > >>
> > >>
> > >> -Section 2, it seems to be more a terminology/definition
> > section than
> > >> acronyms The following definitions would be useful as well:
> > >>
> > >> Service Instance Drop Eligibility Indicator (I-DEI): A
> > field of the
> > >> I-TAG which identifies the Service Instance Drop
> > Eligibility of the
> > >> frame in the 802.1ah (PBBN) domain.
> > >>
> > >> Service instance priority code point (I-PCP): A field of 
> the I-TAG 
> > >> which identifies the service instance priority of the 
> frame in the 
> > >> 802.1ah
> > >> (PBBN) domain.
> > >>
> > >> I-tagged Service Interface: A 802.1ah (PBBN) interface type over 
> > >> which an I-TAG immediately follows the destination and 
> source MAC 
> > >> addresses in the header of the Ethernet frames.
> > >>
> > >>     
> > >
> > >   
> > Yes,  I also agree , we'll add these.
> > > Agree, since they are used in the text, it make sense to
> > define them
> > > up front.
> > >
> > >   
> > >> A note may be appropriate saying that: These definitions will be 
> > >> removed in later versions by a reference to the appropriate IEEE 
> > >> standard.
> > >>
> > >>     
> > >
> > > I think it still would be good to keep these definitions in
> > the draft
> > > for sake of completeness.
> > >
> > >
> > >   
> > Yes, It's really a compromise between how much we repeat in 
> a document 
> > , and how much we want the document to be clear.
> > 
> > I usually err more on the clear side.
> > 
> > >> -Section 4 Applicability
> > >> In the first paragraph I'm considering if "I-SID to I-SID" 
> > >> should not be changed to "I-tagged interface to I-tagged
> > interface". 
> > >> I recognize that this might be more limiting from an AC
> > point of view
> > >> but isn't this the intention?
> > >>
> > >>     
> > >
> > > "I-SID to I-SID" is correct since it is used to connect two I-SID 
> > > aware forwarder rather than two Acs - e.g., AC may not be
> > an I-tagged
> > > service interface but still we want to provide full-mesh 
> of PW on a 
> > > per I-SID basis.
> > >
> > >   
> > We can certainly change this definition , but in general the other 
> > encap drafts are written with respect to an AC.
> > I just wanted to keep this one consistent.
> > 
> > >> After this paragraph something like "In contrast to the
> > VLAN (tagged
> > >> mode) where 2^12 customer service instances can be
> > distinguished, the
> > >> I-SID in the I-TAG increases scalability by allowing 
> 2^24 service 
> > >> instances." might highlight one important aspect of the VLAN and 
> > >> I-SID scenario.
> > >>
> > >>     
> > >
> > > Since we are using one PW per I-SID, this scalability aspect of 
> > > I-tagged is not used in our case.
> > >
> > >   
> > >> In the discussion further below in Section 4 "I-SID aware" 
> > >> forwarders should be "I-TAG aware" forwarders. For
> > instance for the
> > >> QoS discussions not only the I-SID but also the I-PCP and
> > I-DEI may
> > >> be considered.
> > >>
> > >> Further, in the case of native CFM Ethernet OAM and PW OAM 
> > >> interworking I can imagine that the No Customer Addresses
> > >> (NCA) field of the I-TAG may be considered by the NSP and/or 
> > >> forwarder.
> > >>
> > >>     
> > >  
> > > Agree.
> > >
> > >   
> > ok.
> > >> -Regarding Sections 5 and 6, I do not see the benefit of 
> repeating 
> > >> general PW encapsulation procedures. In my read only 6.2
> > provides new
> > >> information about the I-tagged mode all other discussion 
> could be 
> > >> removed with no harm and instead a pointer to the already
> > defined PW
> > >> procedures could be added.
> > >> (Do I mis something?)
> > >>
> > >>     
> > >
> > > I guess it is there for sake of completeness. It is up to Luca to 
> > > decide what to do with it.
> > >
> > >   
> > I think that I would like to avoid too many recursive reference to 
> > other documents. This document needs to explain how to 
> implement the 
> > PW without too many references.
> > 
> > >   
> > >> It would be beneficial to add a figure focusing on the I-tagged 
> > >> Ethernet header and its PW encapsulation, something like this:
> > >>
> > >> AC PW
> > >>         Forwarder
> > >> ------------ ------------
> > >> |   Data   |    |   Data   | 
> > >> |----------| |----------|
> > >> |Other TAGs| |Other TAGs|
> > >> |----------|  |----------|
> > >> |  I-TAG   | ----| |  I-TAG   |
> > >> |----------|     | |----------|
> > >> |  SA MAC  |     | |  SA MAC  | 
> > >> |----------|     | |----------|
> > >> |  DA MAC  |     | |  DA MAC  |
> > >> ------------     | |----------|
> > >>      +--> |Encap (CW)|
> > >>      | |----------|
> > >>      +--> |   Demux  |
> > >> |----------|
> > >>      |PSN tunnel|
> > >> ------------
> > >>
> > >>
> > >>
> > >>     
> > Yes, this is a very good idea.  Is this figure what we want ? 
> > No other tags shown ?
> > 
> > Thanks.
> > Luca
> > 
> > >  
> > > Agree, I think such figure would be helpful.
> > >
> > > Thanks again for your comments,
> > > Ali
> > >
> > >   
> > >>
> > >>     
> > >
> > >   
> > 
> > 
> > 
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pwe3
> > 
> 


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


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



From pwe3-bounces@ietf.org Tue Jul 24 09:51:51 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDKnE-0003nQ-RP; Tue, 24 Jul 2007 09:51:16 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1IDKnE-0003lm-B7
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 09:51:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDKnD-0003iR-Tt
	for pwe3@ietf.org; Tue, 24 Jul 2007 09:51:16 -0400
Received: from audl953.usa.alcatel.com ([143.209.238.162])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDKnC-0002S2-BT
	for pwe3@ietf.org; Tue, 24 Jul 2007 09:51:15 -0400
Received: from usdalsbhs01.ad3.ad.alcatel.com (usdalsbhs01.usa.alcatel.com
	[172.22.216.19])
	by audl953.usa.alcatel.com (ALCANET) with ESMTP id l6ODp7Zo015420;
	Tue, 24 Jul 2007 08:51:07 -0500
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by
	usdalsbhs01.ad3.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Tue, 24 Jul 2007 08:51:07 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Date: Tue, 24 Jul 2007 08:51:05 -0500
Message-ID: <4A5028372622294A99B8FFF6BD06EB7B0318A400@USDALSMBS03.ad3.ad.alcatel.com>
In-Reply-To: <40B2D3B1A8D67246A33D2F5B832C17E774B3C9@USDALSMBS03.ad3.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Thread-Index: AcfDP93V3KaZMetPTbKxdSOqhKCpyAKGuAmgABcDk/AAAup9MAANGFPg
From: "BALUS Florin" <Florin.Balus@alcatel-lucent.com>
To: "KOMPELLA Vach" <Vach.Kompella@alcatel-lucent.com>,
	"Ali Sajassi \(sajassi\)" <sajassi@cisco.com>,
	"Luca Martini \(lmartini\)" <lmartini@cisco.com>
X-OriginalArrivalTime: 24 Jul 2007 13:51:07.0768 (UTC)
	FILETIME=[AF768780:01C7CDF9]
X-Scanned-By: MIMEDefang 2.51 on 143.209.238.34
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 913ee11e7c554f7d4da75d500826397e
Cc: "Attila Takacs \(IJ/ETH\)" <Attila.Takacs@ericsson.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org


Ali, Luca,

I agree with Vach: tagged mode matches the requirements for the ITAG. =20

>From a VPLS perspective the ITAG is an extended 24 bits tag identified
at the NSP by a new Ethertype. Different from the Qtag modes, for the
ITAG there is just one mode of operation that needs to be performed as
Ali correctly suggested below: i.e. ITAG always stays in the PWE3 frame.
So there is no need to differentiate further through signaling the
processing as this matches tagged mode behavior.=20

Also from hallway discussions I realized people think we did the
tagged/raw mode to signal the use of qtag as service delimitation at
ingress NSP. That was not the case as both raw/tagged modes may/may not
use the qtag as service delimitation. This is a choice driven by NSP
configuration. Same for the ITAG: i.e. if I want to use the ITAG as
service delimitation, I configure the NSP accordingly.

Florin


> -----Original Message-----
> From: KOMPELLA Vach [mailto:Vach.Kompella@alcatel-lucent.com]=20
> Sent: Tuesday, July 24, 2007 12:16 AM
> To: Ali Sajassi (sajassi); Luca Martini (lmartini)
> Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> Subject: RE: [PWE3] Re: Some comments on=20
> draft-martini-pwe3-802.1ah-pw-00.txt
>=20
> So don't use the raw mode.  Since we have the tagged mode, we=20
> might as well find a good use for it.
>=20
> -Vach =20
>=20
> > -----Original Message-----
> > From: Ali Sajassi (sajassi) [mailto:sajassi@cisco.com]
> > Sent: Monday, July 23, 2007 10:58 PM
> > To: KOMPELLA Vach; Luca Martini (lmartini)
> > Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> > Subject: RE: [PWE3] Re: Some comments on=20
> > draft-martini-pwe3-802.1ah-pw-00.txt
> >=20
> >=20
> >=20
> > Vach,
> >=20
> > I think you are missing the point that in case of a=20
> raw-mode PW, when=20
> > you remove the VLAN tag you still end up with a valid=20
> Ethernet frame;=20
> > however, there is no equivalent for I-tagged frames - e.g.,=20
> when you=20
> > remove the I-SID from an I-tagged frame, you end up with an invalid=20
> > Ethernet frame.
> > Besides this, refer to the other reasons in the draft as to=20
> why have=20
> > the new PW type.
> >=20
> > -Ali
> > =20
> >=20
> > > -----Original Message-----
> > > From: KOMPELLA Vach [mailto:Vach.Kompella@alcatel-lucent.com]
> > > Sent: Monday, July 23, 2007 12:02 PM
> > > To: Luca Martini (lmartini); Ali Sajassi (sajassi)
> > > Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> > > Subject: RE: [PWE3] Re: Some comments on=20
> > > draft-martini-pwe3-802.1ah-pw-00.txt
> > >=20
> > > I don't see why we need this.  It sounds like a signaling=20
> method to=20
> > > optimize what may or may not be achievable in hardware.
> > >=20
> > > It's deja vu all over again with the tagged Ethernet PW
> > which pretty
> > > much was defined, IMHO, because of harware limitations.  By
> > the time
> > > ethernet services became a well-defined, those hardware=20
> limitations=20
> > > were overcome, and the tagged PW has already become obsolete.
> > >=20
> > > I say just process the I-Tag in the NSP.
> > >=20
> > > -Vach
> > >=20
> > > > -----Original Message-----
> > > > From: Luca Martini [mailto:lmartini@cisco.com]
> > > > Sent: Tuesday, July 10, 2007 3:14 PM
> > > > To: Ali Sajassi (sajassi)
> > > > Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> > > > Subject: [PWE3] Re: Some comments on=20
> > > > draft-martini-pwe3-802.1ah-pw-00.txt
> > > >=20
> > > > Hello!
> > > >=20
> > > > More comments inline.
> > > >=20
> > > > Ali Sajassi (sajassi) wrote:
> > > > > Hi Attila,
> > > > >
> > > > > Thanks for your comments. Please see my reply inline ....=20
> > > > >
> > > > >  =20
> > > > >> -----Original Message-----
> > > > >> From: Attila Takacs (IJ/ETH)
> > [mailto:Attila.Takacs@ericsson.com]
> > > > >> Sent: Tuesday, July 10, 2007 9:41 AM
> > > > >> To: Luca Martini (lmartini); Ali Sajassi (sajassi)
> > > > >> Subject: Some comments on=20
> draft-martini-pwe3-802.1ah-pw-00.txt
> > > > >>
> > > > >> Hi Luca and Ali,
> > > > >>
> > > > >> I just saw your draft on the pwe3 agenda...
> > > > >> It is a useful proposal, please find some
> > > > comments/suggestions below
> > > > >> which you might consider for a new revision.
> > > > >>
> > > > >> Best regards,
> > > > >> Attila
> > > > >> Ps.:I noticed that this is a 00 version, so sorry if you
> > > think the
> > > > >> comments are too editorial
> > > > >>
> > > > >>
> > > > >> -Section 2, it seems to be more a terminology/definition
> > > > section than
> > > > >> acronyms The following definitions would be useful as well:
> > > > >>
> > > > >> Service Instance Drop Eligibility Indicator (I-DEI): A
> > > > field of the
> > > > >> I-TAG which identifies the Service Instance Drop
> > > > Eligibility of the
> > > > >> frame in the 802.1ah (PBBN) domain.
> > > > >>
> > > > >> Service instance priority code point (I-PCP): A field of
> > > the I-TAG
> > > > >> which identifies the service instance priority of the
> > > frame in the
> > > > >> 802.1ah
> > > > >> (PBBN) domain.
> > > > >>
> > > > >> I-tagged Service Interface: A 802.1ah (PBBN) interface
> > type over
> > > > >> which an I-TAG immediately follows the destination and
> > > source MAC
> > > > >> addresses in the header of the Ethernet frames.
> > > > >>
> > > > >>    =20
> > > > >
> > > > >  =20
> > > > Yes,  I also agree , we'll add these.
> > > > > Agree, since they are used in the text, it make sense to
> > > > define them
> > > > > up front.
> > > > >
> > > > >  =20
> > > > >> A note may be appropriate saying that: These
> > definitions will be
> > > > >> removed in later versions by a reference to the
> > appropriate IEEE
> > > > >> standard.
> > > > >>
> > > > >>    =20
> > > > >
> > > > > I think it still would be good to keep these definitions in
> > > > the draft
> > > > > for sake of completeness.
> > > > >
> > > > >
> > > > >  =20
> > > > Yes, It's really a compromise between how much we repeat in
> > > a document
> > > > , and how much we want the document to be clear.
> > > >=20
> > > > I usually err more on the clear side.
> > > >=20
> > > > >> -Section 4 Applicability
> > > > >> In the first paragraph I'm considering if "I-SID to I-SID"=20
> > > > >> should not be changed to "I-tagged interface to I-tagged
> > > > interface".=20
> > > > >> I recognize that this might be more limiting from an AC
> > > > point of view
> > > > >> but isn't this the intention?
> > > > >>
> > > > >>    =20
> > > > >
> > > > > "I-SID to I-SID" is correct since it is used to connect
> > two I-SID
> > > > > aware forwarder rather than two Acs - e.g., AC may not be
> > > > an I-tagged
> > > > > service interface but still we want to provide full-mesh
> > > of PW on a
> > > > > per I-SID basis.
> > > > >
> > > > >  =20
> > > > We can certainly change this definition , but in general
> > the other
> > > > encap drafts are written with respect to an AC.
> > > > I just wanted to keep this one consistent.
> > > >=20
> > > > >> After this paragraph something like "In contrast to the
> > > > VLAN (tagged
> > > > >> mode) where 2^12 customer service instances can be
> > > > distinguished, the
> > > > >> I-SID in the I-TAG increases scalability by allowing
> > > 2^24 service
> > > > >> instances." might highlight one important aspect of
> > the VLAN and
> > > > >> I-SID scenario.
> > > > >>
> > > > >>    =20
> > > > >
> > > > > Since we are using one PW per I-SID, this scalability=20
> aspect of=20
> > > > > I-tagged is not used in our case.
> > > > >
> > > > >  =20
> > > > >> In the discussion further below in Section 4 "I-SID aware"=20
> > > > >> forwarders should be "I-TAG aware" forwarders. For
> > > > instance for the
> > > > >> QoS discussions not only the I-SID but also the I-PCP and
> > > > I-DEI may
> > > > >> be considered.
> > > > >>
> > > > >> Further, in the case of native CFM Ethernet OAM and PW OAM=20
> > > > >> interworking I can imagine that the No Customer Addresses
> > > > >> (NCA) field of the I-TAG may be considered by the NSP and/or=20
> > > > >> forwarder.
> > > > >>
> > > > >>    =20
> > > > > =20
> > > > > Agree.
> > > > >
> > > > >  =20
> > > > ok.
> > > > >> -Regarding Sections 5 and 6, I do not see the benefit of
> > > repeating
> > > > >> general PW encapsulation procedures. In my read only 6.2
> > > > provides new
> > > > >> information about the I-tagged mode all other discussion
> > > could be
> > > > >> removed with no harm and instead a pointer to the already
> > > > defined PW
> > > > >> procedures could be added.
> > > > >> (Do I mis something?)
> > > > >>
> > > > >>    =20
> > > > >
> > > > > I guess it is there for sake of completeness. It is up
> > to Luca to
> > > > > decide what to do with it.
> > > > >
> > > > >  =20
> > > > I think that I would like to avoid too many recursive
> > reference to
> > > > other documents. This document needs to explain how to
> > > implement the
> > > > PW without too many references.
> > > >=20
> > > > >  =20
> > > > >> It would be beneficial to add a figure focusing on the
> > I-tagged
> > > > >> Ethernet header and its PW encapsulation, something=20
> like this:
> > > > >>
> > > > >> 	AC				PW
> > > > >> 	        Forwarder
> > > > >> ------------		------------
> > > > >> |   Data   |    		|   Data   |=20
> > > > >> |----------|		|----------|
> > > > >> |Other TAGs|		|Other TAGs|
> > > > >> |----------|  		|----------|
> > > > >> |  I-TAG   | ----|	|  I-TAG   |
> > > > >> |----------|     |	|----------|
> > > > >> |  SA MAC  |     |	|  SA MAC  |=20
> > > > >> |----------|     |	|----------|
> > > > >> |  DA MAC  |     |	|  DA MAC  |
> > > > >> ------------     |	|----------|
> > > > >> 		     +-->	|Encap (CW)|
> > > > >> 		     |	|----------|
> > > > >> 		     +-->	|   Demux  |
> > > > >> 		 		|----------|
> > > > >> 		     		|PSN tunnel|
> > > > >> 				------------
> > > > >>
> > > > >>
> > > > >>
> > > > >>    =20
> > > > Yes, this is a very good idea.  Is this figure what we want ?=20
> > > > No other tags shown ?
> > > >=20
> > > > Thanks.
> > > > Luca
> > > >=20
> > > > > =20
> > > > > Agree, I think such figure would be helpful.
> > > > >
> > > > > Thanks again for your comments,
> > > > > Ali
> > > > >
> > > > >  =20
> > > > >>
> > > > >>    =20
> > > > >
> > > > >  =20
> > > >=20
> > > >=20
> > > >=20
> > > > _______________________________________________
> > > > pwe3 mailing list
> > > > pwe3@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/pwe3
> > > >=20
> > >=20
> >=20
>=20
>=20
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
>=20


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



From pwe3-bounces@ietf.org Tue Jul 24 10:06:51 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDL2H-0004yR-Hr; Tue, 24 Jul 2007 10:06:49 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1IDL2F-0004yI-So
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 10:06:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDL2F-0004y8-It
	for pwe3@ietf.org; Tue, 24 Jul 2007 10:06:47 -0400
Received: from audl952.usa.alcatel.com ([143.209.238.159])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDL2E-0007vd-8D
	for pwe3@ietf.org; Tue, 24 Jul 2007 10:06:47 -0400
Received: from usdalsbhs01.ad3.ad.alcatel.com (usdalsbhs01.usa.alcatel.com
	[172.22.216.19])
	by audl952.usa.alcatel.com (ALCANET) with ESMTP id l6OE6dFw026407;
	Tue, 24 Jul 2007 09:06:39 -0500
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by
	usdalsbhs01.ad3.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Tue, 24 Jul 2007 09:06:39 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Date: Tue, 24 Jul 2007 09:06:36 -0500
Message-ID: <4A5028372622294A99B8FFF6BD06EB7B0318A410@USDALSMBS03.ad3.ad.alcatel.com>
In-Reply-To: <005201c7cdd1$2e20f800$3e0c6f0a@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Thread-Index: AcfN0WWZnXFSD/XeRTu2W3jdsx0x4gAKaXXg
From: "BALUS Florin" <Florin.Balus@alcatel-lucent.com>
To: "Cao Wei" <caowayne@huawei.com>,
	"Ali Sajassi \(sajassi\)" <sajassi@cisco.com>,
	"KOMPELLA Vach" <Vach.Kompella@alcatel-lucent.com>,
	"Luca Martini \(lmartini\)" <lmartini@cisco.com>
X-OriginalArrivalTime: 24 Jul 2007 14:06:39.0018 (UTC)
	FILETIME=[DA8800A0:01C7CDFB]
X-Scanned-By: MIMEDefang 2.51 on 143.209.238.34
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ba9b8496764663b12c333825fbf6b3d
Cc: "Attila Takacs \(IJ/ETH\)" <Attila.Takacs@ericsson.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Hi Cao Wei,
See in line...

> -----Original Message-----
> From: Cao Wei [mailto:caowayne@huawei.com]=20
> Sent: Tuesday, July 24, 2007 2:01 AM
> To: Ali Sajassi (sajassi); KOMPELLA Vach; Luca Martini (lmartini)
> Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> Subject: Re: [PWE3] Re: Some comments on=20
> draft-martini-pwe3-802.1ah-pw-00.txt
>=20
> Hi Ali,
>     I agree with you that a new mode for 802.1ah should be=20
> considered.  NSP can do something but I don't think it can=20
> cover all necessary functionalities.
>    Here are a few comments about the draft.=20
>    1. In "Applicability Statement " section,  why is only=20
> homogeneous Ethernet frame supported?=20

We always had this function out of scope for all the PWs. This is purely
an NSP function.

>    2. And is there a need to do some extension for LDP for PE=20
> request/ability exchanging?
>

Any new requirement should be documented and understood. If we follow
the logic we used for the other PW types I do not see any need for that.
  =20
>     Since I am not in Chicago and the audio file is not put=20
> to web site yet, I don't know the opinions from other people.=20
> I would like to see this draft going forward. In fact I have=20
> made a presentation and proposed a draft=20
> (draft-cao-pwe3-eth-802.1ah-00.txt)
> in IETF 67 for similar topic. =20
>=20
> Cao Wei
>  =20
> ----- Original Message -----
> From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
> To: "KOMPELLA Vach" <Vach.Kompella@alcatel-lucent.com>; "Luca=20
> Martini (lmartini)" <lmartini@cisco.com>
> Cc: "Attila Takacs (IJ/ETH)" <Attila.Takacs@ericsson.com>;=20
> "PWE3 WG (E-mail)" <pwe3@ietf.org>
> Sent: Tuesday, July 24, 2007 1:58 PM
> Subject: RE: [PWE3] Re: Some comments on=20
> draft-martini-pwe3-802.1ah-pw-00.txt
>=20
>=20
>=20
>=20
> Vach,
>=20
> I think you are missing the point that in case of a raw-mode PW, when
> you remove the VLAN tag you still end up with a valid Ethernet frame;
> however, there is no equivalent for I-tagged frames - e.g., when you
> remove the I-SID from an I-tagged frame, you end up with an invalid
> Ethernet frame. Besides this, refer to the other reasons in=20
> the draft as
> to why have the new PW type.
>=20
> -Ali=20
> =20
>=20
> > -----Original Message-----
> > From: KOMPELLA Vach [mailto:Vach.Kompella@alcatel-lucent.com]=20
> > Sent: Monday, July 23, 2007 12:02 PM
> > To: Luca Martini (lmartini); Ali Sajassi (sajassi)
> > Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> > Subject: RE: [PWE3] Re: Some comments on=20
> > draft-martini-pwe3-802.1ah-pw-00.txt
> >=20
> > I don't see why we need this.  It sounds like a signaling=20
> > method to optimize what may or may not be achievable in hardware.
> >=20
> > It's deja vu all over again with the tagged Ethernet PW which=20
> > pretty much was defined, IMHO, because of harware=20
> > limitations.  By the time ethernet services became a=20
> > well-defined, those hardware limitations were overcome, and=20
> > the tagged PW has already become obsolete.
> >=20
> > I say just process the I-Tag in the NSP.
> >=20
> > -Vach =20
> >=20
> > > -----Original Message-----
> > > From: Luca Martini [mailto:lmartini@cisco.com]
> > > Sent: Tuesday, July 10, 2007 3:14 PM
> > > To: Ali Sajassi (sajassi)
> > > Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> > > Subject: [PWE3] Re: Some comments on
> > > draft-martini-pwe3-802.1ah-pw-00.txt
> > >=20
> > > Hello!
> > >=20
> > > More comments inline.
> > >=20
> > > Ali Sajassi (sajassi) wrote:
> > > > Hi Attila,
> > > >
> > > > Thanks for your comments. Please see my reply inline ....=20
> > > >
> > > >  =20
> > > >> -----Original Message-----
> > > >> From: Attila Takacs (IJ/ETH)=20
> [mailto:Attila.Takacs@ericsson.com]
> > > >> Sent: Tuesday, July 10, 2007 9:41 AM
> > > >> To: Luca Martini (lmartini); Ali Sajassi (sajassi)
> > > >> Subject: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
> > > >>
> > > >> Hi Luca and Ali,
> > > >>
> > > >> I just saw your draft on the pwe3 agenda...
> > > >> It is a useful proposal, please find some
> > > comments/suggestions below
> > > >> which you might consider for a new revision.
> > > >>
> > > >> Best regards,
> > > >> Attila
> > > >> Ps.:I noticed that this is a 00 version, so sorry if you=20
> > think the=20
> > > >> comments are too editorial
> > > >>
> > > >>
> > > >> -Section 2, it seems to be more a terminology/definition
> > > section than
> > > >> acronyms The following definitions would be useful as well:
> > > >>
> > > >> Service Instance Drop Eligibility Indicator (I-DEI): A
> > > field of the
> > > >> I-TAG which identifies the Service Instance Drop
> > > Eligibility of the
> > > >> frame in the 802.1ah (PBBN) domain.
> > > >>
> > > >> Service instance priority code point (I-PCP): A field of=20
> > the I-TAG=20
> > > >> which identifies the service instance priority of the=20
> > frame in the=20
> > > >> 802.1ah
> > > >> (PBBN) domain.
> > > >>
> > > >> I-tagged Service Interface: A 802.1ah (PBBN) interface=20
> type over=20
> > > >> which an I-TAG immediately follows the destination and=20
> > source MAC=20
> > > >> addresses in the header of the Ethernet frames.
> > > >>
> > > >>    =20
> > > >
> > > >  =20
> > > Yes,  I also agree , we'll add these.
> > > > Agree, since they are used in the text, it make sense to
> > > define them
> > > > up front.
> > > >
> > > >  =20
> > > >> A note may be appropriate saying that: These=20
> definitions will be=20
> > > >> removed in later versions by a reference to the=20
> appropriate IEEE=20
> > > >> standard.
> > > >>
> > > >>    =20
> > > >
> > > > I think it still would be good to keep these definitions in
> > > the draft
> > > > for sake of completeness.
> > > >
> > > >
> > > >  =20
> > > Yes, It's really a compromise between how much we repeat in=20
> > a document=20
> > > , and how much we want the document to be clear.
> > >=20
> > > I usually err more on the clear side.
> > >=20
> > > >> -Section 4 Applicability
> > > >> In the first paragraph I'm considering if "I-SID to I-SID"=20
> > > >> should not be changed to "I-tagged interface to I-tagged
> > > interface".=20
> > > >> I recognize that this might be more limiting from an AC
> > > point of view
> > > >> but isn't this the intention?
> > > >>
> > > >>    =20
> > > >
> > > > "I-SID to I-SID" is correct since it is used to connect=20
> two I-SID=20
> > > > aware forwarder rather than two Acs - e.g., AC may not be
> > > an I-tagged
> > > > service interface but still we want to provide full-mesh=20
> > of PW on a=20
> > > > per I-SID basis.
> > > >
> > > >  =20
> > > We can certainly change this definition , but in general=20
> the other=20
> > > encap drafts are written with respect to an AC.
> > > I just wanted to keep this one consistent.
> > >=20
> > > >> After this paragraph something like "In contrast to the
> > > VLAN (tagged
> > > >> mode) where 2^12 customer service instances can be
> > > distinguished, the
> > > >> I-SID in the I-TAG increases scalability by allowing=20
> > 2^24 service=20
> > > >> instances." might highlight one important aspect of=20
> the VLAN and=20
> > > >> I-SID scenario.
> > > >>
> > > >>    =20
> > > >
> > > > Since we are using one PW per I-SID, this scalability aspect of=20
> > > > I-tagged is not used in our case.
> > > >
> > > >  =20
> > > >> In the discussion further below in Section 4 "I-SID aware"=20
> > > >> forwarders should be "I-TAG aware" forwarders. For
> > > instance for the
> > > >> QoS discussions not only the I-SID but also the I-PCP and
> > > I-DEI may
> > > >> be considered.
> > > >>
> > > >> Further, in the case of native CFM Ethernet OAM and PW OAM=20
> > > >> interworking I can imagine that the No Customer Addresses
> > > >> (NCA) field of the I-TAG may be considered by the NSP and/or=20
> > > >> forwarder.
> > > >>
> > > >>    =20
> > > > =20
> > > > Agree.
> > > >
> > > >  =20
> > > ok.
> > > >> -Regarding Sections 5 and 6, I do not see the benefit of=20
> > repeating=20
> > > >> general PW encapsulation procedures. In my read only 6.2
> > > provides new
> > > >> information about the I-tagged mode all other discussion=20
> > could be=20
> > > >> removed with no harm and instead a pointer to the already
> > > defined PW
> > > >> procedures could be added.
> > > >> (Do I mis something?)
> > > >>
> > > >>    =20
> > > >
> > > > I guess it is there for sake of completeness. It is up=20
> to Luca to=20
> > > > decide what to do with it.
> > > >
> > > >  =20
> > > I think that I would like to avoid too many recursive=20
> reference to=20
> > > other documents. This document needs to explain how to=20
> > implement the=20
> > > PW without too many references.
> > >=20
> > > >  =20
> > > >> It would be beneficial to add a figure focusing on the=20
> I-tagged=20
> > > >> Ethernet header and its PW encapsulation, something like this:
> > > >>
> > > >> AC PW
> > > >>         Forwarder
> > > >> ------------ ------------
> > > >> |   Data   |    |   Data   |=20
> > > >> |----------| |----------|
> > > >> |Other TAGs| |Other TAGs|
> > > >> |----------|  |----------|
> > > >> |  I-TAG   | ----| |  I-TAG   |
> > > >> |----------|     | |----------|
> > > >> |  SA MAC  |     | |  SA MAC  |=20
> > > >> |----------|     | |----------|
> > > >> |  DA MAC  |     | |  DA MAC  |
> > > >> ------------     | |----------|
> > > >>      +--> |Encap (CW)|
> > > >>      | |----------|
> > > >>      +--> |   Demux  |
> > > >> |----------|
> > > >>      |PSN tunnel|
> > > >> ------------
> > > >>
> > > >>
> > > >>
> > > >>    =20
> > > Yes, this is a very good idea.  Is this figure what we want ?=20
> > > No other tags shown ?
> > >=20
> > > Thanks.
> > > Luca
> > >=20
> > > > =20
> > > > Agree, I think such figure would be helpful.
> > > >
> > > > Thanks again for your comments,
> > > > Ali
> > > >
> > > >  =20
> > > >>
> > > >>    =20
> > > >
> > > >  =20
> > >=20
> > >=20
> > >=20
> > > _______________________________________________
> > > pwe3 mailing list
> > > pwe3@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pwe3
> > >=20
> >=20
>=20
>=20
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
>=20
>=20
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
>=20


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



From pwe3-bounces@ietf.org Tue Jul 24 11:19:31 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDMAa-0005E0-Sm; Tue, 24 Jul 2007 11:19:28 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1IDMAZ-0005Ds-HU
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 11:19:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDMAZ-0005Db-5q
	for pwe3@ietf.org; Tue, 24 Jul 2007 11:19:27 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IDMAX-0001eM-KR
	for pwe3@ietf.org; Tue, 24 Jul 2007 11:19:27 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-3.cisco.com with ESMTP; 24 Jul 2007 08:19:24 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CALu1pUarR7MV/2dsb2JhbAA
X-IronPort-AV: i="4.16,574,1175497200"; 
	d="scan'208"; a="506445983:sNHT278115128"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6OFJOkO006532; 
	Tue, 24 Jul 2007 08:19:24 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l6OFJC6W011196;
	Tue, 24 Jul 2007 15:19:24 GMT
Received: from xmb-sjc-21e.amer.cisco.com ([171.70.151.156]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Jul 2007 08:19:20 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Date: Tue, 24 Jul 2007 08:19:18 -0700
Message-ID: <75B2A84D9323BC4CA3977CF378CE75EB038FDBAF@xmb-sjc-21e.amer.cisco.com>
In-Reply-To: <40B2D3B1A8D67246A33D2F5B832C17E774B3C9@USDALSMBS03.ad3.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Thread-Index: AcfDP93V3KaZMetPTbKxdSOqhKCpyAKGuAmgABcDk/AAAup9MAAQ0Psw
From: "Ali Sajassi \(sajassi\)" <sajassi@cisco.com>
To: "KOMPELLA Vach" <Vach.Kompella@alcatel-lucent.com>,
	"Luca Martini \(lmartini\)" <lmartini@cisco.com>
X-OriginalArrivalTime: 24 Jul 2007 15:19:20.0132 (UTC)
	FILETIME=[01F53040:01C7CE06]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=9966; t=1185290364;
	x=1186154364; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=sajassi@cisco.com;
	z=From:=20=22Ali=20Sajassi=20\(sajassi\)=22=20<sajassi@cisco.com>
	|Subject:=20RE=3A=20[PWE3]=20Re=3A=20Some=20comments=20on=20draft-martini
	-pwe3-802.1ah-pw-00.txt |Sender:=20;
	bh=BPAcP86sfJB7inwwXYCpvUoY84VK8QRVEeDgNRu44UA=;
	b=MlblRQTWnKarTy43evZ0oEnKVC+6M2e5tiwaDGseA13v+tQaihj/fz3Cgoxtv9MfhvzCUuSf
	lrT9kJw9lVpChVJaoAjK/6xiC9o8KaGD1SDHa7WHLueLnnrTvvAv+DCMT1zrNjR537pYW02YML
	0eGMQZ5uPEWL811fTT1gqsnVo=;
Authentication-Results: sj-dkim-1; header.From=sajassi@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 4515df9441674711565101d9d5c4f63f
Cc: "Attila Takacs \(IJ/ETH\)" <Attila.Takacs@ericsson.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org


Yes, tag-mode for I-SID is called I-tag PW :-) e.g., service delimiter
is the I-SID and not the B-VID.

-Ali=20

> -----Original Message-----
> From: KOMPELLA Vach [mailto:Vach.Kompella@alcatel-lucent.com]=20
> Sent: Tuesday, July 24, 2007 12:16 AM
> To: Ali Sajassi (sajassi); Luca Martini (lmartini)
> Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> Subject: RE: [PWE3] Re: Some comments on=20
> draft-martini-pwe3-802.1ah-pw-00.txt
>=20
> So don't use the raw mode.  Since we have the tagged mode, we=20
> might as well find a good use for it.
>=20
> -Vach =20
>=20
> > -----Original Message-----
> > From: Ali Sajassi (sajassi) [mailto:sajassi@cisco.com]
> > Sent: Monday, July 23, 2007 10:58 PM
> > To: KOMPELLA Vach; Luca Martini (lmartini)
> > Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> > Subject: RE: [PWE3] Re: Some comments on=20
> > draft-martini-pwe3-802.1ah-pw-00.txt
> >=20
> >=20
> >=20
> > Vach,
> >=20
> > I think you are missing the point that in case of a=20
> raw-mode PW, when=20
> > you remove the VLAN tag you still end up with a valid=20
> Ethernet frame;=20
> > however, there is no equivalent for I-tagged frames - e.g.,=20
> when you=20
> > remove the I-SID from an I-tagged frame, you end up with an invalid=20
> > Ethernet frame.
> > Besides this, refer to the other reasons in the draft as to=20
> why have=20
> > the new PW type.
> >=20
> > -Ali
> > =20
> >=20
> > > -----Original Message-----
> > > From: KOMPELLA Vach [mailto:Vach.Kompella@alcatel-lucent.com]
> > > Sent: Monday, July 23, 2007 12:02 PM
> > > To: Luca Martini (lmartini); Ali Sajassi (sajassi)
> > > Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> > > Subject: RE: [PWE3] Re: Some comments on=20
> > > draft-martini-pwe3-802.1ah-pw-00.txt
> > >=20
> > > I don't see why we need this.  It sounds like a signaling=20
> method to=20
> > > optimize what may or may not be achievable in hardware.
> > >=20
> > > It's deja vu all over again with the tagged Ethernet PW
> > which pretty
> > > much was defined, IMHO, because of harware limitations.  By
> > the time
> > > ethernet services became a well-defined, those hardware=20
> limitations=20
> > > were overcome, and the tagged PW has already become obsolete.
> > >=20
> > > I say just process the I-Tag in the NSP.
> > >=20
> > > -Vach
> > >=20
> > > > -----Original Message-----
> > > > From: Luca Martini [mailto:lmartini@cisco.com]
> > > > Sent: Tuesday, July 10, 2007 3:14 PM
> > > > To: Ali Sajassi (sajassi)
> > > > Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> > > > Subject: [PWE3] Re: Some comments on=20
> > > > draft-martini-pwe3-802.1ah-pw-00.txt
> > > >=20
> > > > Hello!
> > > >=20
> > > > More comments inline.
> > > >=20
> > > > Ali Sajassi (sajassi) wrote:
> > > > > Hi Attila,
> > > > >
> > > > > Thanks for your comments. Please see my reply inline ....=20
> > > > >
> > > > >  =20
> > > > >> -----Original Message-----
> > > > >> From: Attila Takacs (IJ/ETH)
> > [mailto:Attila.Takacs@ericsson.com]
> > > > >> Sent: Tuesday, July 10, 2007 9:41 AM
> > > > >> To: Luca Martini (lmartini); Ali Sajassi (sajassi)
> > > > >> Subject: Some comments on=20
> draft-martini-pwe3-802.1ah-pw-00.txt
> > > > >>
> > > > >> Hi Luca and Ali,
> > > > >>
> > > > >> I just saw your draft on the pwe3 agenda...
> > > > >> It is a useful proposal, please find some
> > > > comments/suggestions below
> > > > >> which you might consider for a new revision.
> > > > >>
> > > > >> Best regards,
> > > > >> Attila
> > > > >> Ps.:I noticed that this is a 00 version, so sorry if you
> > > think the
> > > > >> comments are too editorial
> > > > >>
> > > > >>
> > > > >> -Section 2, it seems to be more a terminology/definition
> > > > section than
> > > > >> acronyms The following definitions would be useful as well:
> > > > >>
> > > > >> Service Instance Drop Eligibility Indicator (I-DEI): A
> > > > field of the
> > > > >> I-TAG which identifies the Service Instance Drop
> > > > Eligibility of the
> > > > >> frame in the 802.1ah (PBBN) domain.
> > > > >>
> > > > >> Service instance priority code point (I-PCP): A field of
> > > the I-TAG
> > > > >> which identifies the service instance priority of the
> > > frame in the
> > > > >> 802.1ah
> > > > >> (PBBN) domain.
> > > > >>
> > > > >> I-tagged Service Interface: A 802.1ah (PBBN) interface
> > type over
> > > > >> which an I-TAG immediately follows the destination and
> > > source MAC
> > > > >> addresses in the header of the Ethernet frames.
> > > > >>
> > > > >>    =20
> > > > >
> > > > >  =20
> > > > Yes,  I also agree , we'll add these.
> > > > > Agree, since they are used in the text, it make sense to
> > > > define them
> > > > > up front.
> > > > >
> > > > >  =20
> > > > >> A note may be appropriate saying that: These
> > definitions will be
> > > > >> removed in later versions by a reference to the
> > appropriate IEEE
> > > > >> standard.
> > > > >>
> > > > >>    =20
> > > > >
> > > > > I think it still would be good to keep these definitions in
> > > > the draft
> > > > > for sake of completeness.
> > > > >
> > > > >
> > > > >  =20
> > > > Yes, It's really a compromise between how much we repeat in
> > > a document
> > > > , and how much we want the document to be clear.
> > > >=20
> > > > I usually err more on the clear side.
> > > >=20
> > > > >> -Section 4 Applicability
> > > > >> In the first paragraph I'm considering if "I-SID to I-SID"=20
> > > > >> should not be changed to "I-tagged interface to I-tagged
> > > > interface".=20
> > > > >> I recognize that this might be more limiting from an AC
> > > > point of view
> > > > >> but isn't this the intention?
> > > > >>
> > > > >>    =20
> > > > >
> > > > > "I-SID to I-SID" is correct since it is used to connect
> > two I-SID
> > > > > aware forwarder rather than two Acs - e.g., AC may not be
> > > > an I-tagged
> > > > > service interface but still we want to provide full-mesh
> > > of PW on a
> > > > > per I-SID basis.
> > > > >
> > > > >  =20
> > > > We can certainly change this definition , but in general
> > the other
> > > > encap drafts are written with respect to an AC.
> > > > I just wanted to keep this one consistent.
> > > >=20
> > > > >> After this paragraph something like "In contrast to the
> > > > VLAN (tagged
> > > > >> mode) where 2^12 customer service instances can be
> > > > distinguished, the
> > > > >> I-SID in the I-TAG increases scalability by allowing
> > > 2^24 service
> > > > >> instances." might highlight one important aspect of
> > the VLAN and
> > > > >> I-SID scenario.
> > > > >>
> > > > >>    =20
> > > > >
> > > > > Since we are using one PW per I-SID, this scalability=20
> aspect of=20
> > > > > I-tagged is not used in our case.
> > > > >
> > > > >  =20
> > > > >> In the discussion further below in Section 4 "I-SID aware"=20
> > > > >> forwarders should be "I-TAG aware" forwarders. For
> > > > instance for the
> > > > >> QoS discussions not only the I-SID but also the I-PCP and
> > > > I-DEI may
> > > > >> be considered.
> > > > >>
> > > > >> Further, in the case of native CFM Ethernet OAM and PW OAM=20
> > > > >> interworking I can imagine that the No Customer Addresses
> > > > >> (NCA) field of the I-TAG may be considered by the NSP and/or=20
> > > > >> forwarder.
> > > > >>
> > > > >>    =20
> > > > > =20
> > > > > Agree.
> > > > >
> > > > >  =20
> > > > ok.
> > > > >> -Regarding Sections 5 and 6, I do not see the benefit of
> > > repeating
> > > > >> general PW encapsulation procedures. In my read only 6.2
> > > > provides new
> > > > >> information about the I-tagged mode all other discussion
> > > could be
> > > > >> removed with no harm and instead a pointer to the already
> > > > defined PW
> > > > >> procedures could be added.
> > > > >> (Do I mis something?)
> > > > >>
> > > > >>    =20
> > > > >
> > > > > I guess it is there for sake of completeness. It is up
> > to Luca to
> > > > > decide what to do with it.
> > > > >
> > > > >  =20
> > > > I think that I would like to avoid too many recursive
> > reference to
> > > > other documents. This document needs to explain how to
> > > implement the
> > > > PW without too many references.
> > > >=20
> > > > >  =20
> > > > >> It would be beneficial to add a figure focusing on the
> > I-tagged
> > > > >> Ethernet header and its PW encapsulation, something=20
> like this:
> > > > >>
> > > > >> 	AC				PW
> > > > >> 	        Forwarder
> > > > >> ------------		------------
> > > > >> |   Data   |    		|   Data   |=20
> > > > >> |----------|		|----------|
> > > > >> |Other TAGs|		|Other TAGs|
> > > > >> |----------|  		|----------|
> > > > >> |  I-TAG   | ----|	|  I-TAG   |
> > > > >> |----------|     |	|----------|
> > > > >> |  SA MAC  |     |	|  SA MAC  |=20
> > > > >> |----------|     |	|----------|
> > > > >> |  DA MAC  |     |	|  DA MAC  |
> > > > >> ------------     |	|----------|
> > > > >> 		     +-->	|Encap (CW)|
> > > > >> 		     |	|----------|
> > > > >> 		     +-->	|   Demux  |
> > > > >> 		 		|----------|
> > > > >> 		     		|PSN tunnel|
> > > > >> 				------------
> > > > >>
> > > > >>
> > > > >>
> > > > >>    =20
> > > > Yes, this is a very good idea.  Is this figure what we want ?=20
> > > > No other tags shown ?
> > > >=20
> > > > Thanks.
> > > > Luca
> > > >=20
> > > > > =20
> > > > > Agree, I think such figure would be helpful.
> > > > >
> > > > > Thanks again for your comments,
> > > > > Ali
> > > > >
> > > > >  =20
> > > > >>
> > > > >>    =20
> > > > >
> > > > >  =20
> > > >=20
> > > >=20
> > > >=20
> > > > _______________________________________________
> > > > pwe3 mailing list
> > > > pwe3@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/pwe3
> > > >=20
> > >=20
> >=20
>=20


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



From pwe3-bounces@ietf.org Tue Jul 24 11:39:49 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDMUF-0002AK-W9; Tue, 24 Jul 2007 11:39:48 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1IDMUE-0002AC-IM
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 11:39:46 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDMUE-00029b-3O
	for pwe3@ietf.org; Tue, 24 Jul 2007 11:39:46 -0400
Received: from audl951.usa.alcatel.com ([143.209.238.161])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDMUC-0005gD-RG
	for pwe3@ietf.org; Tue, 24 Jul 2007 11:39:45 -0400
Received: from usdalsbhs01.ad3.ad.alcatel.com (usdalsbhs01.usa.alcatel.com
	[172.22.216.19])
	by audl951.usa.alcatel.com (ALCANET) with ESMTP id l6OFdfxc011386;
	Tue, 24 Jul 2007 10:39:41 -0500
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by
	usdalsbhs01.ad3.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Tue, 24 Jul 2007 10:39:41 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Date: Tue, 24 Jul 2007 10:39:38 -0500
Message-ID: <4A5028372622294A99B8FFF6BD06EB7B0318A4A8@USDALSMBS03.ad3.ad.alcatel.com>
In-Reply-To: <75B2A84D9323BC4CA3977CF378CE75EB038FDBAF@xmb-sjc-21e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Thread-Index: AcfDP93V3KaZMetPTbKxdSOqhKCpyAKGuAmgABcDk/AAAup9MAAQ0PswAAA8boA=
From: "BALUS Florin" <Florin.Balus@alcatel-lucent.com>
To: "Ali Sajassi \(sajassi\)" <sajassi@cisco.com>,
	"KOMPELLA Vach" <Vach.Kompella@alcatel-lucent.com>,
	"Luca Martini \(lmartini\)" <lmartini@cisco.com>
X-OriginalArrivalTime: 24 Jul 2007 15:39:41.0799 (UTC)
	FILETIME=[DA20C770:01C7CE08]
X-Scanned-By: MIMEDefang 2.51 on 143.209.238.34
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6437e26f1586b9f35812ea5ebeedf4ad
Cc: "Attila Takacs \(IJ/ETH\)" <Attila.Takacs@ericsson.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org


No, tag-mode for ISID should be called I-tagged NSP. :)

Choosing the type of tag to use as a service delimiter is again an NSP
function that does not need to be signaled if we are to follow the logic
we used up to now for PW.

We had in fact to deal in the past with different tags based on the
ethertypes (8100, 9100, 88a8) and the meaning of the QoS bits - DEI/CFI.
We did not have that signaled in the PW type. =20

Same with the ITAG: i.e. reading the etype tells you all the story.
Florin

> -----Original Message-----
> From: Ali Sajassi (sajassi) [mailto:sajassi@cisco.com]=20
> Sent: Tuesday, July 24, 2007 10:19 AM
> To: KOMPELLA Vach; Luca Martini (lmartini)
> Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> Subject: RE: [PWE3] Re: Some comments on=20
> draft-martini-pwe3-802.1ah-pw-00.txt
>=20
>=20
> Yes, tag-mode for I-SID is called I-tag PW :-) e.g., service=20
> delimiter is the I-SID and not the B-VID.
>=20
> -Ali=20
>=20
> > -----Original Message-----
> > From: KOMPELLA Vach [mailto:Vach.Kompella@alcatel-lucent.com]
> > Sent: Tuesday, July 24, 2007 12:16 AM
> > To: Ali Sajassi (sajassi); Luca Martini (lmartini)
> > Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> > Subject: RE: [PWE3] Re: Some comments on=20
> > draft-martini-pwe3-802.1ah-pw-00.txt
> >=20
> > So don't use the raw mode.  Since we have the tagged mode,=20
> we might as=20
> > well find a good use for it.
> >=20
> > -Vach
> >=20
> > > -----Original Message-----
> > > From: Ali Sajassi (sajassi) [mailto:sajassi@cisco.com]
> > > Sent: Monday, July 23, 2007 10:58 PM
> > > To: KOMPELLA Vach; Luca Martini (lmartini)
> > > Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> > > Subject: RE: [PWE3] Re: Some comments on=20
> > > draft-martini-pwe3-802.1ah-pw-00.txt
> > >=20
> > >=20
> > >=20
> > > Vach,
> > >=20
> > > I think you are missing the point that in case of a
> > raw-mode PW, when
> > > you remove the VLAN tag you still end up with a valid
> > Ethernet frame;
> > > however, there is no equivalent for I-tagged frames - e.g.,
> > when you
> > > remove the I-SID from an I-tagged frame, you end up with=20
> an invalid=20
> > > Ethernet frame.
> > > Besides this, refer to the other reasons in the draft as to
> > why have
> > > the new PW type.
> > >=20
> > > -Ali
> > > =20
> > >=20
> > > > -----Original Message-----
> > > > From: KOMPELLA Vach [mailto:Vach.Kompella@alcatel-lucent.com]
> > > > Sent: Monday, July 23, 2007 12:02 PM
> > > > To: Luca Martini (lmartini); Ali Sajassi (sajassi)
> > > > Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> > > > Subject: RE: [PWE3] Re: Some comments on=20
> > > > draft-martini-pwe3-802.1ah-pw-00.txt
> > > >=20
> > > > I don't see why we need this.  It sounds like a signaling
> > method to
> > > > optimize what may or may not be achievable in hardware.
> > > >=20
> > > > It's deja vu all over again with the tagged Ethernet PW
> > > which pretty
> > > > much was defined, IMHO, because of harware limitations.  By
> > > the time
> > > > ethernet services became a well-defined, those hardware
> > limitations
> > > > were overcome, and the tagged PW has already become obsolete.
> > > >=20
> > > > I say just process the I-Tag in the NSP.
> > > >=20
> > > > -Vach
> > > >=20
> > > > > -----Original Message-----
> > > > > From: Luca Martini [mailto:lmartini@cisco.com]
> > > > > Sent: Tuesday, July 10, 2007 3:14 PM
> > > > > To: Ali Sajassi (sajassi)
> > > > > Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
> > > > > Subject: [PWE3] Re: Some comments on=20
> > > > > draft-martini-pwe3-802.1ah-pw-00.txt
> > > > >=20
> > > > > Hello!
> > > > >=20
> > > > > More comments inline.
> > > > >=20
> > > > > Ali Sajassi (sajassi) wrote:
> > > > > > Hi Attila,
> > > > > >
> > > > > > Thanks for your comments. Please see my reply inline ....=20
> > > > > >
> > > > > >  =20
> > > > > >> -----Original Message-----
> > > > > >> From: Attila Takacs (IJ/ETH)
> > > [mailto:Attila.Takacs@ericsson.com]
> > > > > >> Sent: Tuesday, July 10, 2007 9:41 AM
> > > > > >> To: Luca Martini (lmartini); Ali Sajassi (sajassi)
> > > > > >> Subject: Some comments on
> > draft-martini-pwe3-802.1ah-pw-00.txt
> > > > > >>
> > > > > >> Hi Luca and Ali,
> > > > > >>
> > > > > >> I just saw your draft on the pwe3 agenda...
> > > > > >> It is a useful proposal, please find some
> > > > > comments/suggestions below
> > > > > >> which you might consider for a new revision.
> > > > > >>
> > > > > >> Best regards,
> > > > > >> Attila
> > > > > >> Ps.:I noticed that this is a 00 version, so sorry if you
> > > > think the
> > > > > >> comments are too editorial
> > > > > >>
> > > > > >>
> > > > > >> -Section 2, it seems to be more a terminology/definition
> > > > > section than
> > > > > >> acronyms The following definitions would be useful as well:
> > > > > >>
> > > > > >> Service Instance Drop Eligibility Indicator (I-DEI): A
> > > > > field of the
> > > > > >> I-TAG which identifies the Service Instance Drop
> > > > > Eligibility of the
> > > > > >> frame in the 802.1ah (PBBN) domain.
> > > > > >>
> > > > > >> Service instance priority code point (I-PCP): A field of
> > > > the I-TAG
> > > > > >> which identifies the service instance priority of the
> > > > frame in the
> > > > > >> 802.1ah
> > > > > >> (PBBN) domain.
> > > > > >>
> > > > > >> I-tagged Service Interface: A 802.1ah (PBBN) interface
> > > type over
> > > > > >> which an I-TAG immediately follows the destination and
> > > > source MAC
> > > > > >> addresses in the header of the Ethernet frames.
> > > > > >>
> > > > > >>    =20
> > > > > >
> > > > > >  =20
> > > > > Yes,  I also agree , we'll add these.
> > > > > > Agree, since they are used in the text, it make sense to
> > > > > define them
> > > > > > up front.
> > > > > >
> > > > > >  =20
> > > > > >> A note may be appropriate saying that: These
> > > definitions will be
> > > > > >> removed in later versions by a reference to the
> > > appropriate IEEE
> > > > > >> standard.
> > > > > >>
> > > > > >>    =20
> > > > > >
> > > > > > I think it still would be good to keep these definitions in
> > > > > the draft
> > > > > > for sake of completeness.
> > > > > >
> > > > > >
> > > > > >  =20
> > > > > Yes, It's really a compromise between how much we repeat in
> > > > a document
> > > > > , and how much we want the document to be clear.
> > > > >=20
> > > > > I usually err more on the clear side.
> > > > >=20
> > > > > >> -Section 4 Applicability
> > > > > >> In the first paragraph I'm considering if "I-SID to I-SID"=20
> > > > > >> should not be changed to "I-tagged interface to I-tagged
> > > > > interface".=20
> > > > > >> I recognize that this might be more limiting from an AC
> > > > > point of view
> > > > > >> but isn't this the intention?
> > > > > >>
> > > > > >>    =20
> > > > > >
> > > > > > "I-SID to I-SID" is correct since it is used to connect
> > > two I-SID
> > > > > > aware forwarder rather than two Acs - e.g., AC may not be
> > > > > an I-tagged
> > > > > > service interface but still we want to provide full-mesh
> > > > of PW on a
> > > > > > per I-SID basis.
> > > > > >
> > > > > >  =20
> > > > > We can certainly change this definition , but in general
> > > the other
> > > > > encap drafts are written with respect to an AC.
> > > > > I just wanted to keep this one consistent.
> > > > >=20
> > > > > >> After this paragraph something like "In contrast to the
> > > > > VLAN (tagged
> > > > > >> mode) where 2^12 customer service instances can be
> > > > > distinguished, the
> > > > > >> I-SID in the I-TAG increases scalability by allowing
> > > > 2^24 service
> > > > > >> instances." might highlight one important aspect of
> > > the VLAN and
> > > > > >> I-SID scenario.
> > > > > >>
> > > > > >>    =20
> > > > > >
> > > > > > Since we are using one PW per I-SID, this scalability
> > aspect of
> > > > > > I-tagged is not used in our case.
> > > > > >
> > > > > >  =20
> > > > > >> In the discussion further below in Section 4 "I-SID aware"=20
> > > > > >> forwarders should be "I-TAG aware" forwarders. For
> > > > > instance for the
> > > > > >> QoS discussions not only the I-SID but also the I-PCP and
> > > > > I-DEI may
> > > > > >> be considered.
> > > > > >>
> > > > > >> Further, in the case of native CFM Ethernet OAM and PW OAM=20
> > > > > >> interworking I can imagine that the No Customer Addresses
> > > > > >> (NCA) field of the I-TAG may be considered by the=20
> NSP and/or=20
> > > > > >> forwarder.
> > > > > >>
> > > > > >>    =20
> > > > > > =20
> > > > > > Agree.
> > > > > >
> > > > > >  =20
> > > > > ok.
> > > > > >> -Regarding Sections 5 and 6, I do not see the benefit of
> > > > repeating
> > > > > >> general PW encapsulation procedures. In my read only 6.2
> > > > > provides new
> > > > > >> information about the I-tagged mode all other discussion
> > > > could be
> > > > > >> removed with no harm and instead a pointer to the already
> > > > > defined PW
> > > > > >> procedures could be added.
> > > > > >> (Do I mis something?)
> > > > > >>
> > > > > >>    =20
> > > > > >
> > > > > > I guess it is there for sake of completeness. It is up
> > > to Luca to
> > > > > > decide what to do with it.
> > > > > >
> > > > > >  =20
> > > > > I think that I would like to avoid too many recursive
> > > reference to
> > > > > other documents. This document needs to explain how to
> > > > implement the
> > > > > PW without too many references.
> > > > >=20
> > > > > >  =20
> > > > > >> It would be beneficial to add a figure focusing on the
> > > I-tagged
> > > > > >> Ethernet header and its PW encapsulation, something
> > like this:
> > > > > >>
> > > > > >> 	AC				PW
> > > > > >> 	        Forwarder
> > > > > >> ------------		------------
> > > > > >> |   Data   |    		|   Data   |=20
> > > > > >> |----------|		|----------|
> > > > > >> |Other TAGs|		|Other TAGs|
> > > > > >> |----------|  		|----------|
> > > > > >> |  I-TAG   | ----|	|  I-TAG   |
> > > > > >> |----------|     |	|----------|
> > > > > >> |  SA MAC  |     |	|  SA MAC  |=20
> > > > > >> |----------|     |	|----------|
> > > > > >> |  DA MAC  |     |	|  DA MAC  |
> > > > > >> ------------     |	|----------|
> > > > > >> 		     +-->	|Encap (CW)|
> > > > > >> 		     |	|----------|
> > > > > >> 		     +-->	|   Demux  |
> > > > > >> 		 		|----------|
> > > > > >> 		     		|PSN tunnel|
> > > > > >> 				------------
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>    =20
> > > > > Yes, this is a very good idea.  Is this figure what we want ?=20
> > > > > No other tags shown ?
> > > > >=20
> > > > > Thanks.
> > > > > Luca
> > > > >=20
> > > > > > =20
> > > > > > Agree, I think such figure would be helpful.
> > > > > >
> > > > > > Thanks again for your comments, Ali
> > > > > >
> > > > > >  =20
> > > > > >>
> > > > > >>    =20
> > > > > >
> > > > > >  =20
> > > > >=20
> > > > >=20
> > > > >=20
> > > > > _______________________________________________
> > > > > pwe3 mailing list
> > > > > pwe3@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/pwe3
> > > > >=20
> > > >=20
> > >=20
> >=20
>=20
>=20
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
>=20


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



From pwe3-bounces@ietf.org Tue Jul 24 14:27:45 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDP6U-00035q-4W; Tue, 24 Jul 2007 14:27:26 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1IDP6T-00035j-99
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 14:27:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDP6S-00035Y-Us
	for pwe3@ietf.org; Tue, 24 Jul 2007 14:27:24 -0400
Received: from black.monoski.com ([63.227.123.238] helo=napoleon.monoski.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDP6Q-0007pU-Te
	for pwe3@ietf.org; Tue, 24 Jul 2007 14:27:24 -0400
Received: from [130.129.23.85] (dhcp-1755.ietf69.org [130.129.23.85])
	(authenticated bits=0)
	by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id l6OIJMxn019246
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 24 Jul 2007 12:19:24 -0600 (MDT)
Message-ID: <46A63B9D.7080905@cisco.com>
Date: Tue, 24 Jul 2007 11:49:17 -0600
From: Luca Martini <lmartini@cisco.com>
User-Agent: Thunderbird 1.5.0.8 (X11/20061025)
MIME-Version: 1.0
To: KOMPELLA Vach <Vach.Kompella@alcatel-lucent.com>
Subject: Re: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
References: <40B2D3B1A8D67246A33D2F5B832C17E774B34D@USDALSMBS03.ad3.ad.alcatel.com>
In-Reply-To: <40B2D3B1A8D67246A33D2F5B832C17E774B34D@USDALSMBS03.ad3.ad.alcatel.com>
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
	milter-greylist-3.0a1 (napoleon.monoski.com [63.227.123.227]);
	Tue, 24 Jul 2007 12:19:26 -0600 (MDT)
X-Scanned-By: MIMEDefang 2.57 on 63.227.123.227
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d62adab73c3674ddf4d2b0d221683819
Cc: "PWE3 WG \(E-mail\)" <pwe3@ietf.org>,
	"Ali Sajassi \(sajassi\)" <sajassi@cisco.com>,
	"Attila Takacs \(IJ/ETH\)" <Attila.Takacs@ericsson.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1527350737=="
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.
--===============1527350737==
Content-Type: multipart/alternative;
	boundary="------------060701070506030002090206"

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

Vach,

PWs are built on the principle that we use the mpls label as the 
de-multiplexer.
We can use a number of other header fields  for the same purpose , but 
that does not make it a PW.
For example , why not use the Frame-Relay DLCI to determine the egress 
port for a frame-relay PW and have just one label for the PE/service 
instance  ?
We came to the conclusion a long time ago, that it is more efficient to 
use the MPLS label as the de-multiplexer field.
Not all devices will incorporate expensive hardware that can perform the 
double lookup. This has been one of the main reasons why PWs become so 
popular.


Luca



KOMPELLA Vach wrote:
> I don't see why we need this.  It sounds like a signaling method to
> optimize what may or may not be achievable in hardware.
>
> It's deja vu all over again with the tagged Ethernet PW which pretty
> much was defined, IMHO, because of harware limitations.  By the time
> ethernet services became a well-defined, those hardware limitations were
> overcome, and the tagged PW has already become obsolete.
>
> I say just process the I-Tag in the NSP.
>
> -Vach  
>
>   
>> -----Original Message-----
>> From: Luca Martini [mailto:lmartini@cisco.com] 
>> Sent: Tuesday, July 10, 2007 3:14 PM
>> To: Ali Sajassi (sajassi)
>> Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
>> Subject: [PWE3] Re: Some comments on 
>> draft-martini-pwe3-802.1ah-pw-00.txt
>>
>> Hello!
>>
>> More comments inline.
>>
>> Ali Sajassi (sajassi) wrote:
>>     
>>> Hi Attila,
>>>
>>> Thanks for your comments. Please see my reply inline .... 
>>>
>>>   
>>>       
>>>> -----Original Message-----
>>>> From: Attila Takacs (IJ/ETH) [mailto:Attila.Takacs@ericsson.com]
>>>> Sent: Tuesday, July 10, 2007 9:41 AM
>>>> To: Luca Martini (lmartini); Ali Sajassi (sajassi)
>>>> Subject: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
>>>>
>>>> Hi Luca and Ali,
>>>>
>>>> I just saw your draft on the pwe3 agenda...
>>>> It is a useful proposal, please find some 
>>>>         
>> comments/suggestions below 
>>     
>>>> which you might consider for a new revision.
>>>>
>>>> Best regards,
>>>> Attila
>>>> Ps.:I noticed that this is a 00 version, so sorry if you think the 
>>>> comments are too editorial
>>>>
>>>>
>>>> -Section 2, it seems to be more a terminology/definition 
>>>>         
>> section than 
>>     
>>>> acronyms The following definitions would be useful as well:
>>>>
>>>> Service Instance Drop Eligibility Indicator (I-DEI): A 
>>>>         
>> field of the 
>>     
>>>> I-TAG which identifies the Service Instance Drop 
>>>>         
>> Eligibility of the 
>>     
>>>> frame in the 802.1ah (PBBN) domain.
>>>>
>>>> Service instance priority code point (I-PCP): A field of the I-TAG 
>>>> which identifies the service instance priority of the frame in the 
>>>> 802.1ah
>>>> (PBBN) domain.
>>>>
>>>> I-tagged Service Interface: A 802.1ah (PBBN) interface type over 
>>>> which an I-TAG immediately follows the destination and source MAC 
>>>> addresses in the header of the Ethernet frames.
>>>>
>>>>     
>>>>         
>>>   
>>>       
>> Yes,  I also agree , we'll add these.
>>     
>>> Agree, since they are used in the text, it make sense to 
>>>       
>> define them 
>>     
>>> up front.
>>>
>>>   
>>>       
>>>> A note may be appropriate saying that: These definitions will be 
>>>> removed in later versions by a reference to the appropriate IEEE 
>>>> standard.
>>>>
>>>>     
>>>>         
>>> I think it still would be good to keep these definitions in 
>>>       
>> the draft 
>>     
>>> for sake of completeness.
>>>
>>>
>>>   
>>>       
>> Yes, It's really a compromise between how much we repeat in a 
>> document , and how much we want the document to be clear.
>>
>> I usually err more on the clear side.
>>
>>     
>>>> -Section 4 Applicability
>>>> In the first paragraph I'm considering if "I-SID to I-SID" 
>>>> should not be changed to "I-tagged interface to I-tagged 
>>>>         
>> interface". 
>>     
>>>> I recognize that this might be more limiting from an AC 
>>>>         
>> point of view 
>>     
>>>> but isn't this the intention?
>>>>
>>>>     
>>>>         
>>> "I-SID to I-SID" is correct since it is used to connect two I-SID 
>>> aware forwarder rather than two Acs - e.g., AC may not be 
>>>       
>> an I-tagged 
>>     
>>> service interface but still we want to provide full-mesh of PW on a 
>>> per I-SID basis.
>>>
>>>   
>>>       
>> We can certainly change this definition , but in general the 
>> other encap drafts are written with respect to an AC.
>> I just wanted to keep this one consistent.
>>
>>     
>>>> After this paragraph something like "In contrast to the 
>>>>         
>> VLAN (tagged
>>     
>>>> mode) where 2^12 customer service instances can be 
>>>>         
>> distinguished, the 
>>     
>>>> I-SID in the I-TAG increases scalability by allowing 2^24 service 
>>>> instances." might highlight one important aspect of the VLAN and 
>>>> I-SID scenario.
>>>>
>>>>     
>>>>         
>>> Since we are using one PW per I-SID, this scalability aspect of 
>>> I-tagged is not used in our case.
>>>
>>>   
>>>       
>>>> In the discussion further below in Section 4 "I-SID aware" 
>>>> forwarders should be "I-TAG aware" forwarders. For 
>>>>         
>> instance for the 
>>     
>>>> QoS discussions not only the I-SID but also the I-PCP and 
>>>>         
>> I-DEI may 
>>     
>>>> be considered.
>>>>
>>>> Further, in the case of native CFM Ethernet OAM and PW OAM 
>>>> interworking I can imagine that the No Customer Addresses
>>>> (NCA) field of the I-TAG may be considered by the NSP and/or 
>>>> forwarder.
>>>>
>>>>     
>>>>         
>>>  
>>> Agree.
>>>
>>>   
>>>       
>> ok.
>>     
>>>> -Regarding Sections 5 and 6, I do not see the benefit of repeating 
>>>> general PW encapsulation procedures. In my read only 6.2 
>>>>         
>> provides new 
>>     
>>>> information about the I-tagged mode all other discussion could be 
>>>> removed with no harm and instead a pointer to the already 
>>>>         
>> defined PW 
>>     
>>>> procedures could be added.
>>>> (Do I mis something?)
>>>>
>>>>     
>>>>         
>>> I guess it is there for sake of completeness. It is up to Luca to 
>>> decide what to do with it.
>>>
>>>   
>>>       
>> I think that I would like to avoid too many recursive 
>> reference to other documents. This document needs to explain 
>> how to implement the PW without too many references.
>>
>>     
>>>   
>>>       
>>>> It would be beneficial to add a figure focusing on the I-tagged 
>>>> Ethernet header and its PW encapsulation, something like this:
>>>>
>>>> 	AC				PW
>>>> 	        Forwarder
>>>> ------------		------------
>>>> |   Data   |    		|   Data   | 
>>>> |----------|		|----------|
>>>> |Other TAGs|		|Other TAGs|
>>>> |----------|  		|----------|
>>>> |  I-TAG   | ----|	|  I-TAG   |
>>>> |----------|     |	|----------|
>>>> |  SA MAC  |     |	|  SA MAC  | 
>>>> |----------|     |	|----------|
>>>> |  DA MAC  |     |	|  DA MAC  |
>>>> ------------     |	|----------|
>>>> 		     +-->	|Encap (CW)|
>>>> 		     |	|----------|
>>>> 		     +-->	|   Demux  |
>>>> 		 		|----------|
>>>> 		     		|PSN tunnel|
>>>> 				------------
>>>>
>>>>
>>>>
>>>>     
>>>>         
>> Yes, this is a very good idea.  Is this figure what we want ? 
>> No other tags shown ?
>>
>> Thanks.
>> Luca
>>
>>     
>>>  
>>> Agree, I think such figure would be helpful.
>>>
>>> Thanks again for your comments,
>>> Ali
>>>
>>>   
>>>       
>>>>     
>>>>         
>>>   
>>>       
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www1.ietf.org/mailman/listinfo/pwe3
>>
>>     
>
>   


--------------060701070506030002090206
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Vach,<br>
<br>
PWs are built on the principle that we use the mpls label as the
de-multiplexer.<br>
We can use a number of other header fields&nbsp; for the same purpose , but
that does not make it a PW.<br>
For example , why not use the Frame-Relay DLCI to determine the egress
port for a frame-relay PW and have just one label for the PE/service
instance&nbsp; ?<br>
We came to the conclusion a long time ago, that it is more efficient to
use the MPLS label as the de-multiplexer field.<br>
Not all devices will incorporate expensive hardware that can perform
the double lookup. This has been one of the main reasons why PWs become
so popular.<br>
<br>
<br>
Luca<br>
<br>
<br>
<br>
KOMPELLA Vach wrote:
<blockquote
 cite="mid40B2D3B1A8D67246A33D2F5B832C17E774B34D@USDALSMBS03.ad3.ad.alcatel.com"
 type="cite">
  <pre wrap="">I don't see why we need this.  It sounds like a signaling method to
optimize what may or may not be achievable in hardware.

It's deja vu all over again with the tagged Ethernet PW which pretty
much was defined, IMHO, because of harware limitations.  By the time
ethernet services became a well-defined, those hardware limitations were
overcome, and the tagged PW has already become obsolete.

I say just process the I-Tag in the NSP.

-Vach  

  </pre>
  <blockquote type="cite">
    <pre wrap="">-----Original Message-----
From: Luca Martini [<a class="moz-txt-link-freetext"
 href="mailto:lmartini@cisco.com">mailto:lmartini@cisco.com</a>] 
Sent: Tuesday, July 10, 2007 3:14 PM
To: Ali Sajassi (sajassi)
Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
Subject: [PWE3] Re: Some comments on 
draft-martini-pwe3-802.1ah-pw-00.txt

Hello!

More comments inline.

Ali Sajassi (sajassi) wrote:
    </pre>
    <blockquote type="cite">
      <pre wrap="">Hi Attila,

Thanks for your comments. Please see my reply inline .... 

  
      </pre>
      <blockquote type="cite">
        <pre wrap="">-----Original Message-----
From: Attila Takacs (IJ/ETH) [<a class="moz-txt-link-freetext"
 href="mailto:Attila.Takacs@ericsson.com">mailto:Attila.Takacs@ericsson.com</a>]
Sent: Tuesday, July 10, 2007 9:41 AM
To: Luca Martini (lmartini); Ali Sajassi (sajassi)
Subject: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt

Hi Luca and Ali,

I just saw your draft on the pwe3 agenda...
It is a useful proposal, please find some 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">comments/suggestions below 
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">which you might consider for a new revision.

Best regards,
Attila
Ps.:I noticed that this is a 00 version, so sorry if you think the 
comments are too editorial


-Section 2, it seems to be more a terminology/definition 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">section than 
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">acronyms The following definitions would be useful as well:

Service Instance Drop Eligibility Indicator (I-DEI): A 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">field of the 
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">I-TAG which identifies the Service Instance Drop 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">Eligibility of the 
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">frame in the 802.1ah (PBBN) domain.

Service instance priority code point (I-PCP): A field of the I-TAG 
which identifies the service instance priority of the frame in the 
802.1ah
(PBBN) domain.

I-tagged Service Interface: A 802.1ah (PBBN) interface type over 
which an I-TAG immediately follows the destination and source MAC 
addresses in the header of the Ethernet frames.

    
        </pre>
      </blockquote>
      <pre wrap="">  
      </pre>
    </blockquote>
    <pre wrap="">Yes,  I also agree , we'll add these.
    </pre>
    <blockquote type="cite">
      <pre wrap="">Agree, since they are used in the text, it make sense to 
      </pre>
    </blockquote>
    <pre wrap="">define them 
    </pre>
    <blockquote type="cite">
      <pre wrap="">up front.

  
      </pre>
      <blockquote type="cite">
        <pre wrap="">A note may be appropriate saying that: These definitions will be 
removed in later versions by a reference to the appropriate IEEE 
standard.

    
        </pre>
      </blockquote>
      <pre wrap="">I think it still would be good to keep these definitions in 
      </pre>
    </blockquote>
    <pre wrap="">the draft 
    </pre>
    <blockquote type="cite">
      <pre wrap="">for sake of completeness.


  
      </pre>
    </blockquote>
    <pre wrap="">Yes, It's really a compromise between how much we repeat in a 
document , and how much we want the document to be clear.

I usually err more on the clear side.

    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">-Section 4 Applicability
In the first paragraph I'm considering if "I-SID to I-SID" 
should not be changed to "I-tagged interface to I-tagged 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">interface". 
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">I recognize that this might be more limiting from an AC 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">point of view 
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">but isn't this the intention?

    
        </pre>
      </blockquote>
      <pre wrap="">"I-SID to I-SID" is correct since it is used to connect two I-SID 
aware forwarder rather than two Acs - e.g., AC may not be 
      </pre>
    </blockquote>
    <pre wrap="">an I-tagged 
    </pre>
    <blockquote type="cite">
      <pre wrap="">service interface but still we want to provide full-mesh of PW on a 
per I-SID basis.

  
      </pre>
    </blockquote>
    <pre wrap="">We can certainly change this definition , but in general the 
other encap drafts are written with respect to an AC.
I just wanted to keep this one consistent.

    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">After this paragraph something like "In contrast to the 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">VLAN (tagged
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">mode) where 2^12 customer service instances can be 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">distinguished, the 
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">I-SID in the I-TAG increases scalability by allowing 2^24 service 
instances." might highlight one important aspect of the VLAN and 
I-SID scenario.

    
        </pre>
      </blockquote>
      <pre wrap="">Since we are using one PW per I-SID, this scalability aspect of 
I-tagged is not used in our case.

  
      </pre>
      <blockquote type="cite">
        <pre wrap="">In the discussion further below in Section 4 "I-SID aware" 
forwarders should be "I-TAG aware" forwarders. For 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">instance for the 
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">QoS discussions not only the I-SID but also the I-PCP and 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">I-DEI may 
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">be considered.

Further, in the case of native CFM Ethernet OAM and PW OAM 
interworking I can imagine that the No Customer Addresses
(NCA) field of the I-TAG may be considered by the NSP and/or 
forwarder.

    
        </pre>
      </blockquote>
      <pre wrap=""> 
Agree.

  
      </pre>
    </blockquote>
    <pre wrap="">ok.
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">-Regarding Sections 5 and 6, I do not see the benefit of repeating 
general PW encapsulation procedures. In my read only 6.2 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">provides new 
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">information about the I-tagged mode all other discussion could be 
removed with no harm and instead a pointer to the already 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">defined PW 
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">procedures could be added.
(Do I mis something?)

    
        </pre>
      </blockquote>
      <pre wrap="">I guess it is there for sake of completeness. It is up to Luca to 
decide what to do with it.

  
      </pre>
    </blockquote>
    <pre wrap="">I think that I would like to avoid too many recursive 
reference to other documents. This document needs to explain 
how to implement the PW without too many references.

    </pre>
    <blockquote type="cite">
      <pre wrap="">  
      </pre>
      <blockquote type="cite">
        <pre wrap="">It would be beneficial to add a figure focusing on the I-tagged 
Ethernet header and its PW encapsulation, something like this:

	AC				PW
	        Forwarder
------------		------------
|   Data   |    		|   Data   | 
|----------|		|----------|
|Other TAGs|		|Other TAGs|
|----------|  		|----------|
|  I-TAG   | ----|	|  I-TAG   |
|----------|     |	|----------|
|  SA MAC  |     |	|  SA MAC  | 
|----------|     |	|----------|
|  DA MAC  |     |	|  DA MAC  |
------------     |	|----------|
		     +--&gt;	|Encap (CW)|
		     |	|----------|
		     +--&gt;	|   Demux  |
		 		|----------|
		     		|PSN tunnel|
				------------



    
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">Yes, this is a very good idea.  Is this figure what we want ? 
No other tags shown ?

Thanks.
Luca

    </pre>
    <blockquote type="cite">
      <pre wrap=""> 
Agree, I think such figure would be helpful.

Thanks again for your comments,
Ali

  
      </pre>
      <blockquote type="cite">
        <pre wrap="">    
        </pre>
      </blockquote>
      <pre wrap="">  
      </pre>
    </blockquote>
    <pre wrap="">
_______________________________________________
pwe3 mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pwe3@ietf.org">pwe3@ietf.org</a>
<a class="moz-txt-link-freetext"
 href="https://www1.ietf.org/mailman/listinfo/pwe3">https://www1.ietf.org/mailman/listinfo/pwe3</a>

    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
</blockquote>
<br>
</body>
</html>

--------------060701070506030002090206--



--===============1527350737==
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://www1.ietf.org/mailman/listinfo/pwe3

--===============1527350737==--





From pwe3-bounces@ietf.org Tue Jul 24 14:59:31 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDPbV-0004nQ-OP; Tue, 24 Jul 2007 14:59:29 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1IDPbU-0004el-3N
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 14:59:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDPbT-0004e2-OP
	for pwe3@ietf.org; Tue, 24 Jul 2007 14:59:27 -0400
Received: from smtp102.vzn.mail.mud.yahoo.com ([68.142.203.46])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IDPbT-00008K-7H
	for pwe3@ietf.org; Tue, 24 Jul 2007 14:59:27 -0400
Received: (qmail 65806 invoked from network); 24 Jul 2007 18:59:26 -0000
Received: from unknown (HELO AMALIS.verizon.net)
	(agmalis@verizon.net@130.129.101.127 with login)
	by smtp102.vzn.mail.mud.yahoo.com with SMTP; 24 Jul 2007 18:59:26 -0000
X-YMail-OSG: 178Xp3MVM1nf6aP3HN7s0.tb60No0SK0ujdn6ROBG3yi2Re1X_YcWZCtvFkZb4APGY4G2RL85w--
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 24 Jul 2007 14:59:21 -0400
To: Luca Martini <lmartini@cisco.com>
From: "Andrew G. Malis" <amalis@gmail.com>
Subject: Re: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
In-Reply-To: <46A63B9D.7080905@cisco.com>
References: <40B2D3B1A8D67246A33D2F5B832C17E774B34D@USDALSMBS03.ad3.ad.alcatel.com>
	<46A63B9D.7080905@cisco.com>
Mime-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Message-Id: <E1IDPbU-0004el-3N@megatron.ietf.org>
Cc: KOMPELLA Vach <Vach.Kompella@alcatel-lucent.com>,
	"Ali Sajassi \(sajassi\)" <sajassi@cisco.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>,
	"Attila Takacs \(IJ/ETH\)" <Attila.Takacs@ericsson.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0951390142=="
Errors-To: pwe3-bounces@ietf.org

--===============0951390142==
Content-Type: multipart/alternative;
	boundary="=====================_194573031==.ALT"

--=====================_194573031==.ALT
Content-Type: text/plain; charset="us-ascii"

I absolutely agree with Luca here on the principle for the PW label.  I don't agree with Vach that the tagged PW is "obsolete".

In addition, section 4 of RFC 4448 is clear on the treatment of frames under both the raw and tagged modes, and Vach's proposal doesn't conform to either mode as currently defined.

Cheers,
Andy

At 7/24/2007 11:49 AM -0600, Luca Martini wrote:
>Vach,
>
>PWs are built on the principle that we use the mpls label as the de-multiplexer.
>We can use a number of other header fields  for the same purpose , but that does not make it a PW.
>For example , why not use the Frame-Relay DLCI to determine the egress port for a frame-relay PW and have just one label for the PE/service instance  ?
>We came to the conclusion a long time ago, that it is more efficient to use the MPLS label as the de-multiplexer field.
>Not all devices will incorporate expensive hardware that can perform the double lookup. This has been one of the main reasons why PWs become so popular.
>
>
>Luca
>
>
>
>KOMPELLA Vach wrote: 
>>
>>I don't see why we need this.  It sounds like a signaling method to
>>optimize what may or may not be achievable in hardware.
>>
>>It's deja vu all over again with the tagged Ethernet PW which pretty
>>much was defined, IMHO, because of harware limitations.  By the time
>>ethernet services became a well-defined, those hardware limitations were
>>overcome, and the tagged PW has already become obsolete.
>>
>>I say just process the I-Tag in the NSP.
>>
>>-Vach  


--=====================_194573031==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
I absolutely agree with Luca here on the principle for the PW
label.&nbsp; I don't agree with Vach that the tagged PW is
&quot;obsolete&quot;.<br><br>
In addition, section 4 of RFC 4448 is clear on the treatment of frames
under both the raw and tagged modes, and Vach's proposal doesn't conform
to either mode as currently defined.<br><br>
Cheers,<br>
Andy<br><br>
At 7/24/2007 11:49 AM -0600, Luca Martini wrote:<br>
<blockquote type=cite class=cite cite="">Vach,<br>
<br>
PWs are built on the principle that we use the mpls label as the
de-multiplexer.<br>
We can use a number of other header fields&nbsp; for the same purpose ,
but that does not make it a PW.<br>
For example , why not use the Frame-Relay DLCI to determine the egress
port for a frame-relay PW and have just one label for the PE/service
instance&nbsp; ?<br>
We came to the conclusion a long time ago, that it is more efficient to
use the MPLS label as the de-multiplexer field.<br>
Not all devices will incorporate expensive hardware that can perform the
double lookup. This has been one of the main reasons why PWs become so
popular.<br><br>
<br>
Luca<br><br>
<br><br>
KOMPELLA Vach wrote: <br>
<blockquote type=cite class=cite cite=""><br>
<pre>I don't see why we need this.&nbsp; It sounds like a signaling
method to
optimize what may or may not be achievable in hardware.

It's deja vu all over again with the tagged Ethernet PW which pretty
much was defined, IMHO, because of harware limitations.&nbsp; By the
time
ethernet services became a well-defined, those hardware limitations were
overcome, and the tagged PW has already become obsolete.

I say just process the I-Tag in the NSP.

-Vach&nbsp; 
</pre></blockquote></blockquote><br>
</body>
</html>

--=====================_194573031==.ALT--




--===============0951390142==
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://www1.ietf.org/mailman/listinfo/pwe3

--===============0951390142==--






From pwe3-bounces@ietf.org Tue Jul 24 15:24:46 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDPzw-0000py-Kk; Tue, 24 Jul 2007 15:24:44 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1IDPzv-0000iZ-4z
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 15:24:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDPzu-0000g4-GZ
	for pwe3@ietf.org; Tue, 24 Jul 2007 15:24:42 -0400
Received: from audl951.usa.alcatel.com ([143.209.238.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDPzt-0000jq-Fa
	for pwe3@ietf.org; Tue, 24 Jul 2007 15:24:42 -0400
Received: from usdalsbhs02.ad3.ad.alcatel.com (usdalsbhs02.usa.alcatel.com
	[172.22.216.13])
	by audl951.usa.alcatel.com (ALCANET) with ESMTP id l6OJObST027419;
	Tue, 24 Jul 2007 14:24:37 -0500
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by
	usdalsbhs02.ad3.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Tue, 24 Jul 2007 14:24:37 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Date: Tue, 24 Jul 2007 14:24:50 -0500
Message-ID: <40B2D3B1A8D67246A33D2F5B832C17E774B45B@USDALSMBS03.ad3.ad.alcatel.com>
In-Reply-To: <200707241853.l6OIr87Z010449@mx7.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Thread-Index: AcfOJMl+DvUVoTHAQ+Kx1n9PFPC9AgAAjmmA
From: "KOMPELLA Vach" <Vach.Kompella@alcatel-lucent.com>
To: "Andrew G. Malis" <amalis@gmail.com>, "Luca Martini" <lmartini@cisco.com>
X-OriginalArrivalTime: 24 Jul 2007 19:24:37.0325 (UTC)
	FILETIME=[46169FD0:01C7CE28]
X-Scanned-By: MIMEDefang 2.51 on 143.209.238.34
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b66a1e94d7d92973ece9e5da449ff80
Cc: "Ali Sajassi \(sajassi\)" <sajassi@cisco.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>,
	"Attila Takacs \(IJ/ETH\)" <Attila.Takacs@ericsson.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0376059871=="
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0376059871==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7CE28.4608F879"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7CE28.4608F879
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Andy,
=20
I absolutely agree with Luca on the principle of the PW label.  Where
did I say that the PW label was not the demux?=20
=20
We were talking about using the I-SID as a service delimiter.  I am
simply saying that we can continue to use that as a service delimiter.
That's precisely the way we are using VLAN tags as service delimiters in
the two ethernet flavors of PWs.
=20
Use the I-SID as a delimiter (let the NSP figure out how to extract the
delimiting value), find the matching PW, leave the I-SID in place, and
drop the packet into the VLAN PW type Ethernet PW.  Pop the label stack
at egress, identify the egressing port using the PW label, and since the
I-SID has not been affected in the forwarding path, it's there to be
used at the egress NSP.
=20
OK - obsolete is not the right word - less preferred?  The main use I
have seen for the VLAN PW type is for preserving 802.1p bits.
=20
-Vach=20
=20


________________________________

	From: Andrew G. Malis [mailto:amalis@gmail.com]=20
	Sent: Tuesday, July 24, 2007 11:59 AM
	To: Luca Martini
	Cc: KOMPELLA Vach; PWE3 WG (E-mail); Ali Sajassi (sajassi);
Attila Takacs (IJ/ETH)
	Subject: Re: [PWE3] Re: Some comments on
draft-martini-pwe3-802.1ah-pw-00.txt
=09
=09
	I absolutely agree with Luca here on the principle for the PW
label.  I don't agree with Vach that the tagged PW is "obsolete".
=09
	In addition, section 4 of RFC 4448 is clear on the treatment of
frames under both the raw and tagged modes, and Vach's proposal doesn't
conform to either mode as currently defined.
=09
	Cheers,
	Andy
=09
	At 7/24/2007 11:49 AM -0600, Luca Martini wrote:
=09

		Vach,
	=09
		PWs are built on the principle that we use the mpls
label as the de-multiplexer.
		We can use a number of other header fields  for the same
purpose , but that does not make it a PW.
		For example , why not use the Frame-Relay DLCI to
determine the egress port for a frame-relay PW and have just one label
for the PE/service instance  ?
		We came to the conclusion a long time ago, that it is
more efficient to use the MPLS label as the de-multiplexer field.
		Not all devices will incorporate expensive hardware that
can perform the double lookup. This has been one of the main reasons why
PWs become so popular.
	=09
	=09
		Luca
	=09
	=09
	=09
		KOMPELLA Vach wrote:=20
	=09


			I don't see why we need this.  It sounds like a
signaling
			method to
			optimize what may or may not be achievable in
hardware.
		=09
			It's deja vu all over again with the tagged
Ethernet PW which pretty
			much was defined, IMHO, because of harware
limitations.  By the
			time
			ethernet services became a well-defined, those
hardware limitations were
			overcome, and the tagged PW has already become
obsolete.
		=09
			I say just process the I-Tag in the NSP.
		=09
			-Vach =20



------_=_NextPart_001_01C7CE28.4608F879
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.2873" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D497351519-24072007><FONT =
face=3D"Courier New"=20
size=3D2>Hi Andy,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D497351519-24072007><FONT =
face=3D"Courier New"=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D497351519-24072007><FONT =
face=3D"Courier New"=20
size=3D2>I absolutely agree with Luca on the principle of the PW =
label.&nbsp;=20
<SPAN class=3D497351519-24072007><FONT face=3D"Courier New" =
size=3D2>Where did I say=20
that the PW label was not the demux?</FONT></SPAN>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D497351519-24072007><FONT =
face=3D"Courier New"=20
size=3D2></FONT></SPAN>&nbsp;</DIV></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D497351519-24072007><FONT =
face=3D"Courier New"=20
size=3D2>We were talking about using the I-SID as a service =
delimiter.&nbsp; I am=20
simply saying that we can continue to use that as a service =
delimiter.&nbsp;=20
That's precisely the way we are using VLAN tags as service delimiters in =
the two=20
ethernet flavors of PWs.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D497351519-24072007><FONT =
face=3D"Courier New"=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D497351519-24072007><FONT =
face=3D"Courier New"=20
size=3D2>Use the I-SID as a delimiter (let the NSP figure out how to =
extract the=20
delimiting value), find the matching PW, leave the I-SID in place, and =
drop the=20
packet into the VLAN PW type Ethernet PW.&nbsp; Pop the label stack at =
egress,=20
identify the egressing port using the PW label, and since the I-SID has =
not been=20
affected in the forwarding path, it's there to be used at the egress=20
NSP.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D497351519-24072007><FONT =
face=3D"Courier New"=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D497351519-24072007><FONT =
face=3D"Courier New"=20
size=3D2>OK - obsolete is not the right word - less preferred?&nbsp; The =
main use=20
I have seen for the VLAN PW type is for preserving 802.1p=20
bits.</FONT></SPAN></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>-Vach </FONT></DIV>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE=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> Andrew G. Malis=20
  [mailto:amalis@gmail.com] <BR><B>Sent:</B> Tuesday, July 24, 2007 =
11:59=20
  AM<BR><B>To:</B> Luca Martini<BR><B>Cc:</B> KOMPELLA Vach; PWE3 WG =
(E-mail);=20
  Ali Sajassi (sajassi); Attila Takacs (IJ/ETH)<BR><B>Subject:</B> Re: =
[PWE3]=20
  Re: Some comments on =
draft-martini-pwe3-802.1ah-pw-00.txt<BR></FONT><BR></DIV>
  <DIV></DIV>I absolutely agree with Luca here on the principle for the =
PW=20
  label.&nbsp; I don't agree with Vach that the tagged PW is=20
  "obsolete".<BR><BR>In addition, section 4 of RFC 4448 is clear on the=20
  treatment of frames under both the raw and tagged modes, and Vach's =
proposal=20
  doesn't conform to either mode as currently=20
  defined.<BR><BR>Cheers,<BR>Andy<BR><BR>At 7/24/2007 11:49 AM -0600, =
Luca=20
  Martini wrote:<BR>
  <BLOCKQUOTE class=3Dcite cite=3D"" type=3D"cite">Vach,<BR><BR>PWs are =
built on the=20
    principle that we use the mpls label as the de-multiplexer.<BR>We =
can use a=20
    number of other header fields&nbsp; for the same purpose , but that =
does not=20
    make it a PW.<BR>For example , why not use the Frame-Relay DLCI to =
determine=20
    the egress port for a frame-relay PW and have just one label for the =

    PE/service instance&nbsp; ?<BR>We came to the conclusion a long time =
ago,=20
    that it is more efficient to use the MPLS label as the =
de-multiplexer=20
    field.<BR>Not all devices will incorporate expensive hardware that =
can=20
    perform the double lookup. This has been one of the main reasons why =
PWs=20
    become so popular.<BR><BR><BR>Luca<BR><BR><BR><BR>KOMPELLA Vach =
wrote: <BR>
    <BLOCKQUOTE class=3Dcite cite=3D"" type=3D"cite"><BR><PRE>I don't =
see why we need this.&nbsp; It sounds like a signaling
method to
optimize what may or may not be achievable in hardware.

It's deja vu all over again with the tagged Ethernet PW which pretty
much was defined, IMHO, because of harware limitations.&nbsp; By the
time
ethernet services became a well-defined, those hardware limitations were
overcome, and the tagged PW has already become obsolete.

I say just process the I-Tag in the NSP.

-Vach&nbsp;=20
</PRE></BLOCKQUOTE></BLOCKQUOTE><BR></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C7CE28.4608F879--



--===============0376059871==
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://www1.ietf.org/mailman/listinfo/pwe3

--===============0376059871==--





From pwe3-bounces@ietf.org Tue Jul 24 15:35:06 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDQ92-0007Qc-GH; Tue, 24 Jul 2007 15:34:08 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1IDQ91-0007QX-Gf
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 15:34:07 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDQ91-0007N1-0t
	for pwe3@ietf.org; Tue, 24 Jul 2007 15:34:07 -0400
Received: from mx2-q.rad.co.il ([80.74.100.144] helo=antivir2.rad.co.il)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDQ8w-0004lG-CY
	for pwe3@ietf.org; Tue, 24 Jul 2007 15:34:04 -0400
Received: from exrad3.rad.co.il (HELO exrad3.ad.rad.co.il) ([192.114.24.112])
	by antivir2.rad.co.il with ESMTP; 24 Jul 2007 22:33:58 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Date: Tue, 24 Jul 2007 22:33:57 +0300
Message-ID: <457D36D9D89B5B47BC06DA869B1C815D0497B2B6@exrad3.ad.rad.co.il>
In-Reply-To: <46A63B9D.7080905@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Thread-Index: AcfOIFkRhghUor39TW2FyuauoiMxgQABjC5g
From: "Yaakov Stein" <yaakov_s@rad.com>
To: "Luca Martini" <lmartini@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cc961b79af8d22f2640d5180a0dbc035
Cc: "Ali Sajassi \(sajassi\)" <sajassi@cisco.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0442305369=="
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0442305369==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7CE29.952641D3"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7CE29.952641D3
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Luca,
=20
As I asked yesterday, can you explain the scenario where this is needed
?
=20
I was assuming that you wanted to support internal internal links to a
PBBN
with MPLS, in the case where there is an ISID but no BVID.
=20
But, in that case the B-DA is sufficient information for the switching,
since the ISID is only used by the BEB (backbone edge switch).
=20
If switching other than on B-DA is required at the intermediate bridges,
then the BVID will used. A B-TAG looks just like an S-TAG,
and so can be handled by the existing VLAN-aware mode.
=20
If you want to replace the entire PBBN edge-to-edge,
then you don't need 1ah at all, just a regular Ethernet PW.
=20
So, for what scenario is the new mode needed ?
=20
Y(J)S
=20

________________________________

From: Luca Martini [mailto:lmartini@cisco.com]=20
Sent: Tuesday, July 24, 2007 20:49
To: KOMPELLA Vach
Cc: PWE3 WG (E-mail); Ali Sajassi (sajassi); Attila Takacs (IJ/ETH)
Subject: Re: [PWE3] Re: Some comments on
draft-martini-pwe3-802.1ah-pw-00.txt


Vach,

PWs are built on the principle that we use the mpls label as the
de-multiplexer.
We can use a number of other header fields  for the same purpose , but
that does not make it a PW.
For example , why not use the Frame-Relay DLCI to determine the egress
port for a frame-relay PW and have just one label for the PE/service
instance  ?
We came to the conclusion a long time ago, that it is more efficient to
use the MPLS label as the de-multiplexer field.
Not all devices will incorporate expensive hardware that can perform the
double lookup. This has been one of the main reasons why PWs become so
popular.


Luca



KOMPELLA Vach wrote:=20

	I don't see why we need this.  It sounds like a signaling method
to
	optimize what may or may not be achievable in hardware.
=09
	It's deja vu all over again with the tagged Ethernet PW which
pretty
	much was defined, IMHO, because of harware limitations.  By the
time
	ethernet services became a well-defined, those hardware
limitations were
	overcome, and the tagged PW has already become obsolete.
=09
	I say just process the I-Tag in the NSP.
=09
	-Vach =20
=09
	 =20

		-----Original Message-----
		From: Luca Martini [mailto:lmartini@cisco.com]=20
		Sent: Tuesday, July 10, 2007 3:14 PM
		To: Ali Sajassi (sajassi)
		Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
		Subject: [PWE3] Re: Some comments on=20
		draft-martini-pwe3-802.1ah-pw-00.txt
	=09
		Hello!
	=09
		More comments inline.
	=09
		Ali Sajassi (sajassi) wrote:
		   =20

			Hi Attila,
		=09
			Thanks for your comments. Please see my reply
inline ....=20
		=09
			 =20
			     =20

				-----Original Message-----
				From: Attila Takacs (IJ/ETH)
[mailto:Attila.Takacs@ericsson.com]
				Sent: Tuesday, July 10, 2007 9:41 AM
				To: Luca Martini (lmartini); Ali Sajassi
(sajassi)
				Subject: Some comments on
draft-martini-pwe3-802.1ah-pw-00.txt
			=09
				Hi Luca and Ali,
			=09
				I just saw your draft on the pwe3
agenda...
				It is a useful proposal, please find
some=20
				       =20

		comments/suggestions below=20
		   =20

				which you might consider for a new
revision.
			=09
				Best regards,
				Attila
				Ps.:I noticed that this is a 00 version,
so sorry if you think the=20
				comments are too editorial
			=09
			=09
				-Section 2, it seems to be more a
terminology/definition=20
				       =20

		section than=20
		   =20

				acronyms The following definitions would
be useful as well:
			=09
				Service Instance Drop Eligibility
Indicator (I-DEI): A=20
				       =20

		field of the=20
		   =20

				I-TAG which identifies the Service
Instance Drop=20
				       =20

		Eligibility of the=20
		   =20

				frame in the 802.1ah (PBBN) domain.
			=09
				Service instance priority code point
(I-PCP): A field of the I-TAG=20
				which identifies the service instance
priority of the frame in the=20
				802.1ah
				(PBBN) domain.
			=09
				I-tagged Service Interface: A 802.1ah
(PBBN) interface type over=20
				which an I-TAG immediately follows the
destination and source MAC=20
				addresses in the header of the Ethernet
frames.
			=09
				   =20
				       =20

			 =20
			     =20

		Yes,  I also agree , we'll add these.
		   =20

			Agree, since they are used in the text, it make
sense to=20
			     =20

		define them=20
		   =20

			up front.
		=09
			 =20
			     =20

				A note may be appropriate saying that:
These definitions will be=20
				removed in later versions by a reference
to the appropriate IEEE=20
				standard.
			=09
				   =20
				       =20

			I think it still would be good to keep these
definitions in=20
			     =20

		the draft=20
		   =20

			for sake of completeness.
		=09
		=09
			 =20
			     =20

		Yes, It's really a compromise between how much we repeat
in a=20
		document , and how much we want the document to be
clear.
	=09
		I usually err more on the clear side.
	=09
		   =20

				-Section 4 Applicability
				In the first paragraph I'm considering
if "I-SID to I-SID"=20
				should not be changed to "I-tagged
interface to I-tagged=20
				       =20

		interface".=20
		   =20

				I recognize that this might be more
limiting from an AC=20
				       =20

		point of view=20
		   =20

				but isn't this the intention?
			=09
				   =20
				       =20

			"I-SID to I-SID" is correct since it is used to
connect two I-SID=20
			aware forwarder rather than two Acs - e.g., AC
may not be=20
			     =20

		an I-tagged=20
		   =20

			service interface but still we want to provide
full-mesh of PW on a=20
			per I-SID basis.
		=09
			 =20
			     =20

		We can certainly change this definition , but in general
the=20
		other encap drafts are written with respect to an AC.
		I just wanted to keep this one consistent.
	=09
		   =20

				After this paragraph something like "In
contrast to the=20
				       =20

		VLAN (tagged
		   =20

				mode) where 2^12 customer service
instances can be=20
				       =20

		distinguished, the=20
		   =20

				I-SID in the I-TAG increases scalability
by allowing 2^24 service=20
				instances." might highlight one
important aspect of the VLAN and=20
				I-SID scenario.
			=09
				   =20
				       =20

			Since we are using one PW per I-SID, this
scalability aspect of=20
			I-tagged is not used in our case.
		=09
			 =20
			     =20

				In the discussion further below in
Section 4 "I-SID aware"=20
				forwarders should be "I-TAG aware"
forwarders. For=20
				       =20

		instance for the=20
		   =20

				QoS discussions not only the I-SID but
also the I-PCP and=20
				       =20

		I-DEI may=20
		   =20

				be considered.
			=09
				Further, in the case of native CFM
Ethernet OAM and PW OAM=20
				interworking I can imagine that the No
Customer Addresses
				(NCA) field of the I-TAG may be
considered by the NSP and/or=20
				forwarder.
			=09
				   =20
				       =20

			=20
			Agree.
		=09
			 =20
			     =20

		ok.
		   =20

				-Regarding Sections 5 and 6, I do not
see the benefit of repeating=20
				general PW encapsulation procedures. In
my read only 6.2=20
				       =20

		provides new=20
		   =20

				information about the I-tagged mode all
other discussion could be=20
				removed with no harm and instead a
pointer to the already=20
				       =20

		defined PW=20
		   =20

				procedures could be added.
				(Do I mis something?)
			=09
				   =20
				       =20

			I guess it is there for sake of completeness. It
is up to Luca to=20
			decide what to do with it.
		=09
			 =20
			     =20

		I think that I would like to avoid too many recursive=20
		reference to other documents. This document needs to
explain=20
		how to implement the PW without too many references.
	=09
		   =20

			 =20
			     =20

				It would be beneficial to add a figure
focusing on the I-tagged=20
				Ethernet header and its PW
encapsulation, something like this:
			=09
					AC
PW
					        Forwarder
				------------		------------
				|   Data   |    		|   Data
|=20
				|----------|		|----------|
				|Other TAGs|		|Other TAGs|
				|----------|  		|----------|
				|  I-TAG   | ----|	|  I-TAG   |
				|----------|     |	|----------|
				|  SA MAC  |     |	|  SA MAC  |=20
				|----------|     |	|----------|
				|  DA MAC  |     |	|  DA MAC  |
				------------     |	|----------|
						     +-->	|Encap
(CW)|
						     |	|----------|
						     +-->	|
Demux  |
=09
|----------|
						     		|PSN
tunnel|
=09
------------
			=09
			=09
			=09
				   =20
				       =20

		Yes, this is a very good idea.  Is this figure what we
want ?=20
		No other tags shown ?
	=09
		Thanks.
		Luca
	=09
		   =20

			=20
			Agree, I think such figure would be helpful.
		=09
			Thanks again for your comments,
			Ali
		=09
			 =20
			     =20

				   =20
				       =20

			 =20
			     =20

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

=09
	 =20



------_=_NextPart_001_01C7CE29.952641D3
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.3020" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D934111219-24072007>Luca,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D934111219-24072007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D934111219-24072007>As I=20
asked yesterday, can you explain the scenario where this is needed=20
?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D934111219-24072007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D934111219-24072007>I was=20
assuming that&nbsp;you wanted to support internal internal links to a=20
PBBN</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D934111219-24072007>with=20
MPLS, in the case where there is an ISID but no =
BVID.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D934111219-24072007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D934111219-24072007>But,=20
in that case the B-DA is sufficient information for the=20
switching,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D934111219-24072007>since=20
the ISID is only used by the BEB (backbone edge =
switch).</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D934111219-24072007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D934111219-24072007>If&nbsp;switching other than on B-DA is=20
required&nbsp;at the intermediate bridges,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D934111219-24072007>then=20
the BVID will used. A B-TAG looks just like an =
S-TAG,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D934111219-24072007>and so=20
can be handled by the existing VLAN-aware mode.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D934111219-24072007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D934111219-24072007>If you=20
want to replace the entire PBBN edge-to-edge,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D934111219-24072007>then=20
you don't need 1ah at all, just a regular Ethernet =
PW.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D934111219-24072007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D934111219-24072007>So,=20
for what scenario is the new mode needed ?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D934111219-24072007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D934111219-24072007>Y(J)S</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D934111219-24072007></SPAN></FONT>&nbsp;</DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Luca Martini =
[mailto:lmartini@cisco.com]=20
<BR><B>Sent:</B> Tuesday, July 24, 2007 20:49<BR><B>To:</B> KOMPELLA=20
Vach<BR><B>Cc:</B> PWE3 WG (E-mail); Ali Sajassi (sajassi); Attila =
Takacs=20
(IJ/ETH)<BR><B>Subject:</B> Re: [PWE3] Re: Some comments on=20
draft-martini-pwe3-802.1ah-pw-00.txt<BR></FONT><BR></DIV>
<DIV></DIV>Vach,<BR><BR>PWs are built on the principle that we use the =
mpls=20
label as the de-multiplexer.<BR>We can use a number of other header =
fields&nbsp;=20
for the same purpose , but that does not make it a PW.<BR>For example , =
why not=20
use the Frame-Relay DLCI to determine the egress port for a frame-relay =
PW and=20
have just one label for the PE/service instance&nbsp; ?<BR>We came to =
the=20
conclusion a long time ago, that it is more efficient to use the MPLS =
label as=20
the de-multiplexer field.<BR>Not all devices will incorporate expensive =
hardware=20
that can perform the double lookup. This has been one of the main =
reasons why=20
PWs become so popular.<BR><BR><BR>Luca<BR><BR><BR><BR>KOMPELLA Vach =
wrote:=20
<BLOCKQUOTE=20
cite=3Dmid40B2D3B1A8D67246A33D2F5B832C17E774B34D@USDALSMBS03.ad3.ad.alcat=
el.com=20
type=3D"cite"><PRE wrap=3D"">I don't see why we need this.  It sounds =
like a signaling method to
optimize what may or may not be achievable in hardware.

It's deja vu all over again with the tagged Ethernet PW which pretty
much was defined, IMHO, because of harware limitations.  By the time
ethernet services became a well-defined, those hardware limitations were
overcome, and the tagged PW has already become obsolete.

I say just process the I-Tag in the NSP.

-Vach =20

  </PRE>
  <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">-----Original Message-----
From: Luca Martini [<A class=3Dmoz-txt-link-freetext =
href=3D"mailto:lmartini@cisco.com">mailto:lmartini@cisco.com</A>]=20
Sent: Tuesday, July 10, 2007 3:14 PM
To: Ali Sajassi (sajassi)
Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
Subject: [PWE3] Re: Some comments on=20
draft-martini-pwe3-802.1ah-pw-00.txt

Hello!

More comments inline.

Ali Sajassi (sajassi) wrote:
    </PRE>
    <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">Hi Attila,

Thanks for your comments. Please see my reply inline ....=20

 =20
      </PRE>
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">-----Original =
Message-----
From: Attila Takacs (IJ/ETH) [<A class=3Dmoz-txt-link-freetext =
href=3D"mailto:Attila.Takacs@ericsson.com">mailto:Attila.Takacs@ericsson.=
com</A>]
Sent: Tuesday, July 10, 2007 9:41 AM
To: Luca Martini (lmartini); Ali Sajassi (sajassi)
Subject: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt

Hi Luca and Ali,

I just saw your draft on the pwe3 agenda...
It is a useful proposal, please find some=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE =
wrap=3D"">comments/suggestions below=20
    </PRE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">which you might consider =
for a new revision.

Best regards,
Attila
Ps.:I noticed that this is a 00 version, so sorry if you think the=20
comments are too editorial


-Section 2, it seems to be more a terminology/definition=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">section than=20
    </PRE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">acronyms The following =
definitions would be useful as well:

Service Instance Drop Eligibility Indicator (I-DEI): A=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">field of the=20
    </PRE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">I-TAG which identifies =
the Service Instance Drop=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">Eligibility of =
the=20
    </PRE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">frame in the 802.1ah =
(PBBN) domain.

Service instance priority code point (I-PCP): A field of the I-TAG=20
which identifies the service instance priority of the frame in the=20
802.1ah
(PBBN) domain.

I-tagged Service Interface: A 802.1ah (PBBN) interface type over=20
which an I-TAG immediately follows the destination and source MAC=20
addresses in the header of the Ethernet frames.

   =20
        </PRE></BLOCKQUOTE><PRE wrap=3D""> =20
      </PRE></BLOCKQUOTE><PRE wrap=3D"">Yes,  I also agree , we'll add =
these.
    </PRE>
    <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">Agree, since they are used =
in the text, it make sense to=20
      </PRE></BLOCKQUOTE><PRE wrap=3D"">define them=20
    </PRE>
    <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">up front.

 =20
      </PRE>
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">A note may be appropriate =
saying that: These definitions will be=20
removed in later versions by a reference to the appropriate IEEE=20
standard.

   =20
        </PRE></BLOCKQUOTE><PRE wrap=3D"">I think it still would be good =
to keep these definitions in=20
      </PRE></BLOCKQUOTE><PRE wrap=3D"">the draft=20
    </PRE>
    <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">for sake of completeness.


 =20
      </PRE></BLOCKQUOTE><PRE wrap=3D"">Yes, It's really a compromise =
between how much we repeat in a=20
document , and how much we want the document to be clear.

I usually err more on the clear side.

    </PRE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">-Section 4 Applicability
In the first paragraph I'm considering if "I-SID to I-SID"=20
should not be changed to "I-tagged interface to I-tagged=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">interface".=20
    </PRE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">I recognize that this =
might be more limiting from an AC=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">point of view=20
    </PRE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">but isn't this the =
intention?

   =20
        </PRE></BLOCKQUOTE><PRE wrap=3D"">"I-SID to I-SID" is correct =
since it is used to connect two I-SID=20
aware forwarder rather than two Acs - e.g., AC may not be=20
      </PRE></BLOCKQUOTE><PRE wrap=3D"">an I-tagged=20
    </PRE>
    <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">service interface but still =
we want to provide full-mesh of PW on a=20
per I-SID basis.

 =20
      </PRE></BLOCKQUOTE><PRE wrap=3D"">We can certainly change this =
definition , but in general the=20
other encap drafts are written with respect to an AC.
I just wanted to keep this one consistent.

    </PRE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">After this paragraph =
something like "In contrast to the=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">VLAN (tagged
    </PRE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">mode) where 2^12 customer =
service instances can be=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">distinguished, =
the=20
    </PRE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">I-SID in the I-TAG =
increases scalability by allowing 2^24 service=20
instances." might highlight one important aspect of the VLAN and=20
I-SID scenario.

   =20
        </PRE></BLOCKQUOTE><PRE wrap=3D"">Since we are using one PW per =
I-SID, this scalability aspect of=20
I-tagged is not used in our case.

 =20
      </PRE>
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">In the discussion further =
below in Section 4 "I-SID aware"=20
forwarders should be "I-TAG aware" forwarders. For=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">instance for the=20
    </PRE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">QoS discussions not only =
the I-SID but also the I-PCP and=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">I-DEI may=20
    </PRE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">be considered.

Further, in the case of native CFM Ethernet OAM and PW OAM=20
interworking I can imagine that the No Customer Addresses
(NCA) field of the I-TAG may be considered by the NSP and/or=20
forwarder.

   =20
        </PRE></BLOCKQUOTE><PRE wrap=3D"">=20
Agree.

 =20
      </PRE></BLOCKQUOTE><PRE wrap=3D"">ok.
    </PRE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">-Regarding Sections 5 and =
6, I do not see the benefit of repeating=20
general PW encapsulation procedures. In my read only 6.2=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">provides new=20
    </PRE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">information about the =
I-tagged mode all other discussion could be=20
removed with no harm and instead a pointer to the already=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">defined PW=20
    </PRE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">procedures could be =
added.
(Do I mis something?)

   =20
        </PRE></BLOCKQUOTE><PRE wrap=3D"">I guess it is there for sake =
of completeness. It is up to Luca to=20
decide what to do with it.

 =20
      </PRE></BLOCKQUOTE><PRE wrap=3D"">I think that I would like to =
avoid too many recursive=20
reference to other documents. This document needs to explain=20
how to implement the PW without too many references.

    </PRE>
    <BLOCKQUOTE type=3D"cite"><PRE wrap=3D""> =20
      </PRE>
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">It would be beneficial to =
add a figure focusing on the I-tagged=20
Ethernet header and its PW encapsulation, something like this:

	AC				PW
	        Forwarder
------------		------------
|   Data   |    		|   Data   |=20
|----------|		|----------|
|Other TAGs|		|Other TAGs|
|----------|  		|----------|
|  I-TAG   | ----|	|  I-TAG   |
|----------|     |	|----------|
|  SA MAC  |     |	|  SA MAC  |=20
|----------|     |	|----------|
|  DA MAC  |     |	|  DA MAC  |
------------     |	|----------|
		     +--&gt;	|Encap (CW)|
		     |	|----------|
		     +--&gt;	|   Demux  |
		 		|----------|
		     		|PSN tunnel|
				------------



   =20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">Yes, this is a =
very good idea.  Is this figure what we want ?=20
No other tags shown ?

Thanks.
Luca

    </PRE>
    <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">=20
Agree, I think such figure would be helpful.

Thanks again for your comments,
Ali

 =20
      </PRE>
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">   =20
        </PRE></BLOCKQUOTE><PRE wrap=3D""> =20
      </PRE></BLOCKQUOTE><PRE =
wrap=3D"">_______________________________________________
pwe3 mailing list
<A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</A>
<A class=3Dmoz-txt-link-freetext =
href=3D"https://www1.ietf.org/mailman/listinfo/pwe3">https://www1.ietf.or=
g/mailman/listinfo/pwe3</A>

    </PRE></BLOCKQUOTE><PRE wrap=3D""><!---->
  </PRE></BLOCKQUOTE><BR></BODY></HTML>

------_=_NextPart_001_01C7CE29.952641D3--



--===============0442305369==
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://www1.ietf.org/mailman/listinfo/pwe3

--===============0442305369==--





From pwe3-bounces@ietf.org Tue Jul 24 15:42:24 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDQH2-0004jb-Hd; Tue, 24 Jul 2007 15:42:24 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1IDQH1-0004jW-5p
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 15:42:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDQH0-0004jO-SI
	for pwe3@ietf.org; Tue, 24 Jul 2007 15:42:22 -0400
Received: from smtp102.vzn.mail.mud.yahoo.com ([68.142.203.46])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IDQGz-0001HZ-W0
	for pwe3@ietf.org; Tue, 24 Jul 2007 15:42:22 -0400
Received: (qmail 72640 invoked from network); 24 Jul 2007 19:42:21 -0000
Received: from unknown (HELO AMALIS.verizon.net)
	(agmalis@verizon.net@130.129.22.98 with login)
	by smtp102.vzn.mail.mud.yahoo.com with SMTP; 24 Jul 2007 19:42:20 -0000
X-YMail-OSG: 3Sq154oVM1n33dth6qKtPvwqpAvEozEbaHh4pT6f.7J1r9EWfGuGOx3zJKbLN1IXj.Lr4cUm0A--
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 24 Jul 2007 15:42:14 -0400
To: "KOMPELLA Vach" <Vach.Kompella@alcatel-lucent.com>
From: "Andrew G. Malis" <amalis@gmail.com>
Subject: RE: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
In-Reply-To: <40B2D3B1A8D67246A33D2F5B832C17E774B45B@USDALSMBS03.ad3.ad.
	alcatel.com>
References: <200707241853.l6OIr87Z010449@mx7.alcatel.com>
	<40B2D3B1A8D67246A33D2F5B832C17E774B45B@USDALSMBS03.ad3.ad.alcatel.com>
Mime-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a0534e6179a1e260079328e8b03c7901
Message-Id: <E1IDQH1-0004jW-5p@megatron.ietf.org>
Cc: "PWE3 WG \(E-mail\)" <pwe3@ietf.org>,
	"Ali Sajassi \(sajassi\)" <sajassi@cisco.com>,
	Luca Martini <lmartini@cisco.com>,
	"Attila Takacs \(IJ/ETH\)" <Attila.Takacs@ericsson.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0014659565=="
Errors-To: pwe3-bounces@ietf.org

--===============0014659565==
Content-Type: multipart/alternative;
	boundary="=====================_197146000==.ALT"

--=====================_197146000==.ALT
Content-Type: text/plain; charset="us-ascii"

Vach,

I get what you're proposing, but that's a change of behavior from that currently defined in RFC 4448. In current raw mode, there is never a service-delimiting tag on the wire, and there is a one-to-one relationship between a physical interface at the ingress PE and a PW.  In current tagged mode, there is always a service-delimiting VLAN tag on the wire, and that VLAN tag (not I-SID) is used in the ingress PE to choose the proper PW for the frame.

Cheers,
Andy

At 7/24/2007 02:24 PM -0500, KOMPELLA Vach wrote:
>Hi Andy,
> 
>I absolutely agree with Luca on the principle of the PW label.  Where did I say that the PW label was not the demux? 
> 
>We were talking about using the I-SID as a service delimiter.  I am simply saying that we can continue to use that as a service delimiter.  That's precisely the way we are using VLAN tags as service delimiters in the two ethernet flavors of PWs.
> 
>Use the I-SID as a delimiter (let the NSP figure out how to extract the delimiting value), find the matching PW, leave the I-SID in place, and drop the packet into the VLAN PW type Ethernet PW.  Pop the label stack at egress, identify the egressing port using the PW label, and since the I-SID has not been affected in the forwarding path, it's there to be used at the egress NSP.
> 
>OK - obsolete is not the right word - less preferred?  The main use I have seen for the VLAN PW type is for preserving 802.1p bits.
> 
>-Vach 
> 
>
>
>----------
>From: Andrew G. Malis [mailto:amalis@gmail.com] 
>Sent: Tuesday, July 24, 2007 11:59 AM
>To: Luca Martini
>Cc: KOMPELLA Vach; PWE3 WG (E-mail); Ali Sajassi (sajassi); Attila Takacs (IJ/ETH)
>Subject: Re: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
>
>I absolutely agree with Luca here on the principle for the PW label.  I don't agree with Vach that the tagged PW is "obsolete".
>
>In addition, section 4 of RFC 4448 is clear on the treatment of frames under both the raw and tagged modes, and Vach's proposal doesn't conform to either mode as currently defined.
>
>Cheers,
>Andy
>
>At 7/24/2007 11:49 AM -0600, Luca Martini wrote:
>>Vach,
>>
>>PWs are built on the principle that we use the mpls label as the de-multiplexer.
>>We can use a number of other header fields  for the same purpose , but that does not make it a PW.
>>For example , why not use the Frame-Relay DLCI to determine the egress port for a frame-relay PW and have just one label for the PE/service instance  ?
>>We came to the conclusion a long time ago, that it is more efficient to use the MPLS label as the de-multiplexer field.
>>Not all devices will incorporate expensive hardware that can perform the double lookup. This has been one of the main reasons why PWs become so popular.
>>
>>
>>Luca
>>
>>
>>
>>KOMPELLA Vach wrote: 
>>>
>>>
>>>I don't see why we need this.  It sounds like a signaling
>>>
>>>method to
>>>
>>>optimize what may or may not be achievable in hardware.
>>>
>>>
>>>It's deja vu all over again with the tagged Ethernet PW which pretty
>>>
>>>much was defined, IMHO, because of harware limitations.  By the
>>>
>>>time
>>>
>>>ethernet services became a well-defined, those hardware limitations were
>>>
>>>overcome, and the tagged PW has already become obsolete.
>>>
>>>
>>>I say just process the I-Tag in the NSP.
>>>
>>>
>>>-Vach  

--=====================_197146000==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
Vach,<br><br>
I get what you're proposing, but that's a change of behavior from that
currently defined in RFC 4448. In current raw mode, there is never a
service-delimiting tag on the wire, and there is a one-to-one
relationship between a physical interface at the ingress PE and a
PW.&nbsp; In current tagged mode, there is always a service-delimiting
VLAN tag on the wire, and that VLAN tag (not I-SID) is used in the
ingress PE to choose the proper PW for the frame.<br><br>
Cheers,<br>
Andy<br><br>
At 7/24/2007 02:24 PM -0500, KOMPELLA Vach wrote:<br>
<blockquote type=cite class=cite cite="">
<font face="Courier New, Courier" size=2>Hi Andy,<br>
</font>&nbsp;<br>
<font face="Courier New, Courier" size=2>I absolutely agree with Luca on
the principle of the PW label.&nbsp; Where did I say that the PW label
was not the demux? <br>
&nbsp;<br>
We were talking about using the I-SID as a service delimiter.&nbsp; I am
simply saying that we can continue to use that as a service
delimiter.&nbsp; That's precisely the way we are using VLAN tags as
service delimiters in the two ethernet flavors of PWs.<br>
</font>&nbsp;<br>
<font face="Courier New, Courier" size=2>Use the I-SID as a delimiter
(let the NSP figure out how to extract the delimiting value), find the
matching PW, leave the I-SID in place, and drop the packet into the VLAN
PW type Ethernet PW.&nbsp; Pop the label stack at egress, identify the
egressing port using the PW label, and since the I-SID has not been
affected in the forwarding path, it's there to be used at the egress
NSP.<br>
</font>&nbsp;<br>
<font face="Courier New, Courier" size=2>OK - obsolete is not the right
word - less preferred?&nbsp; The main use I have seen for the VLAN PW
type is for preserving 802.1p bits.<br>
</font>&nbsp;<br>
<font size=2>-Vach <br>
</font>&nbsp;<br><br>

<dl><hr>

<dd><font face="Tahoma" size=2>From:</b> Andrew G. Malis
[<a href="mailto:amalis@gmail.com" eudora="autourl">
mailto:amalis@gmail.com</a>] <br>

<dd>Sent:</b> Tuesday, July 24, 2007 11:59 AM<br>

<dd>To:</b> Luca Martini<br>

<dd>Cc:</b> KOMPELLA Vach; PWE3 WG (E-mail); Ali Sajassi (sajassi);
Attila Takacs (IJ/ETH)<br>

<dd>Subject:</b> Re: [PWE3] Re: Some comments on
draft-martini-pwe3-802.1ah-pw-00.txt<br>
</font><br>

<dd>I absolutely agree with Luca here on the principle for the PW
label.&nbsp; I don't agree with Vach that the tagged PW is
&quot;obsolete&quot;.<br><br>

<dd>In addition, section 4 of RFC 4448 is clear on the treatment of
frames under both the raw and tagged modes, and Vach's proposal doesn't
conform to either mode as currently defined.<br><br>

<dd>Cheers,<br>

<dd>Andy<br><br>

<dd>At 7/24/2007 11:49 AM -0600, Luca Martini wrote:<br>
<blockquote type=cite class=cite cite="">
<dd>Vach,<br><br>

<dd>PWs are built on the principle that we use the mpls label as the
de-multiplexer.<br>

<dd>We can use a number of other header fields&nbsp; for the same purpose
, but that does not make it a PW.<br>

<dd>For example , why not use the Frame-Relay DLCI to determine the
egress port for a frame-relay PW and have just one label for the
PE/service instance&nbsp; ?<br>

<dd>We came to the conclusion a long time ago, that it is more efficient
to use the MPLS label as the de-multiplexer field.<br>

<dd>Not all devices will incorporate expensive hardware that can perform
the double lookup. This has been one of the main reasons why PWs become
so popular.<br><br>
<br>

<dd>Luca<br><br>
<br><br>

<dd>KOMPELLA Vach wrote: <br>
<blockquote type=cite class=cite cite=""><br><br>

<dd><pre>I don't see why we need this.&nbsp; It sounds like a signaling

<dd>method to

<dd>optimize what may or may not be achievable in hardware.


<dd>It's deja vu all over again with the tagged Ethernet PW which pretty

<dd>much was defined, IMHO, because of harware limitations.&nbsp; By the

<dd>time

<dd>ethernet services became a well-defined, those hardware limitations
were

<dd>overcome, and the tagged PW has already become obsolete.


<dd>I say just process the I-Tag in the NSP.


<dd>-Vach&nbsp; 
</pre><font face="Courier New, Courier"></font></blockquote></blockquote>
</dl></blockquote></body>
</html>

--=====================_197146000==.ALT--




--===============0014659565==
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://www1.ietf.org/mailman/listinfo/pwe3

--===============0014659565==--






From pwe3-bounces@ietf.org Tue Jul 24 15:59:26 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDQXT-0001HT-IE; Tue, 24 Jul 2007 15:59:23 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1IDQXS-0001HJ-7x
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 15:59:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDQXR-0001HA-U1
	for pwe3@ietf.org; Tue, 24 Jul 2007 15:59:21 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IDQXP-0001hz-UP
	for pwe3@ietf.org; Tue, 24 Jul 2007 15:59:21 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 24 Jul 2007 12:59:19 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAOP2pUarR7O6/2dsb2JhbACCZA
X-IronPort-AV: i="4.16,575,1175497200"; 
	d="scan'208,217"; a="10243400:sNHT39784818"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6OJxJ1f014406; 
	Tue, 24 Jul 2007 12:59:19 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l6OJxE6C010513;
	Tue, 24 Jul 2007 19:59:14 GMT
Received: from xmb-sjc-21e.amer.cisco.com ([171.70.151.156]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Jul 2007 12:59:14 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Date: Tue, 24 Jul 2007 12:59:13 -0700
Message-ID: <75B2A84D9323BC4CA3977CF378CE75EB038FDDC3@xmb-sjc-21e.amer.cisco.com>
In-Reply-To: <457D36D9D89B5B47BC06DA869B1C815D0497B2B6@exrad3.ad.rad.co.il>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] Re: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt
Thread-Index: AcfOIFkRhghUor39TW2FyuauoiMxgQABjC5gAADyxXA=
From: "Ali Sajassi \(sajassi\)" <sajassi@cisco.com>
To: "Yaakov Stein" <yaakov_s@rad.com>,
	"Luca Martini \(lmartini\)" <lmartini@cisco.com>
X-OriginalArrivalTime: 24 Jul 2007 19:59:14.0325 (UTC)
	FILETIME=[1C13AC50:01C7CE2D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=27206; t=1185307159;
	x=1186171159; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=sajassi@cisco.com;
	z=From:=20=22Ali=20Sajassi=20\(sajassi\)=22=20<sajassi@cisco.com>
	|Subject:=20RE=3A=20[PWE3]=20Re=3A=20Some=20comments=20on=20draft-martini
	-pwe3-802.1ah-pw-00.txt |Sender:=20;
	bh=zhkB2vuD6/HN8BbXoCGCgodtErm+k/isKvluO3Zod/g=;
	b=SkMBWb0MrM43ASO3rZfAd645Q3dMwkFT4cMdZUhin2hG3kJGkWvXKPGgGBrUKJSSpqEG7j2Y
	6yKxscVZqxJPngzTllOfIsXf4xwzX6ZT42XotEWQkb3f/PksvFjIILWb;
Authentication-Results: sj-dkim-2; header.From=sajassi@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 0948f555ba0a8c21aad67160fcd59720
Cc: "PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1515652656=="
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1515652656==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7CE2D.1BDFA75D"

This is a multi-part message in MIME format.

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

Yaakov,
=20
There are a number of scenarios in which we would need this PW - please
refer to my draft that I presented in last IETF. However, the simplest
scenario to consider is when trying to setup PWs between two I-comp
devices connected via an MPLS network. In such case, you need to map an
I-SID to a PW since there is neither a B-VID nor any B-MAC is used for
forwarding.=20
=20
-Ali


________________________________

	From: Yaakov Stein [mailto:yaakov_s@rad.com]=20
	Sent: Tuesday, July 24, 2007 12:34 PM
	To: Luca Martini (lmartini)
	Cc: PWE3 WG (E-mail); Ali Sajassi (sajassi)
	Subject: RE: [PWE3] Re: Some comments on
draft-martini-pwe3-802.1ah-pw-00.txt
=09
=09
	Luca,
	=20
	As I asked yesterday, can you explain the scenario where this is
needed ?
	=20
	I was assuming that you wanted to support internal internal
links to a PBBN
	with MPLS, in the case where there is an ISID but no BVID.
	=20
	But, in that case the B-DA is sufficient information for the
switching,
	since the ISID is only used by the BEB (backbone edge switch).
	=20
	If switching other than on B-DA is required at the intermediate
bridges,
	then the BVID will used. A B-TAG looks just like an S-TAG,
	and so can be handled by the existing VLAN-aware mode.
	=20
	If you want to replace the entire PBBN edge-to-edge,
	then you don't need 1ah at all, just a regular Ethernet PW.
	=20
	So, for what scenario is the new mode needed ?
	=20
	Y(J)S
	=20

________________________________

	From: Luca Martini [mailto:lmartini@cisco.com]=20
	Sent: Tuesday, July 24, 2007 20:49
	To: KOMPELLA Vach
	Cc: PWE3 WG (E-mail); Ali Sajassi (sajassi); Attila Takacs
(IJ/ETH)
	Subject: Re: [PWE3] Re: Some comments on
draft-martini-pwe3-802.1ah-pw-00.txt
=09
=09
	Vach,
=09
	PWs are built on the principle that we use the mpls label as the
de-multiplexer.
	We can use a number of other header fields  for the same purpose
, but that does not make it a PW.
	For example , why not use the Frame-Relay DLCI to determine the
egress port for a frame-relay PW and have just one label for the
PE/service instance  ?
	We came to the conclusion a long time ago, that it is more
efficient to use the MPLS label as the de-multiplexer field.
	Not all devices will incorporate expensive hardware that can
perform the double lookup. This has been one of the main reasons why PWs
become so popular.
=09
=09
	Luca
=09
=09
=09
	KOMPELLA Vach wrote:=20

		I don't see why we need this.  It sounds like a
signaling method to
		optimize what may or may not be achievable in hardware.
	=09
		It's deja vu all over again with the tagged Ethernet PW
which pretty
		much was defined, IMHO, because of harware limitations.
By the time
		ethernet services became a well-defined, those hardware
limitations were
		overcome, and the tagged PW has already become obsolete.
	=09
		I say just process the I-Tag in the NSP.
	=09
		-Vach =20
	=09
		 =20

			-----Original Message-----
			From: Luca Martini [mailto:lmartini@cisco.com]=20
			Sent: Tuesday, July 10, 2007 3:14 PM
			To: Ali Sajassi (sajassi)
			Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
			Subject: [PWE3] Re: Some comments on=20
			draft-martini-pwe3-802.1ah-pw-00.txt
		=09
			Hello!
		=09
			More comments inline.
		=09
			Ali Sajassi (sajassi) wrote:
			   =20

				Hi Attila,
			=09
				Thanks for your comments. Please see my
reply inline ....=20
			=09
				 =20
				     =20

				-----Original Message-----
				From: Attila Takacs (IJ/ETH)
[mailto:Attila.Takacs@ericsson.com]
				Sent: Tuesday, July 10, 2007 9:41 AM
				To: Luca Martini (lmartini); Ali Sajassi
(sajassi)
				Subject: Some comments on
draft-martini-pwe3-802.1ah-pw-00.txt
			=09
				Hi Luca and Ali,
			=09
				I just saw your draft on the pwe3
agenda...
				It is a useful proposal, please find
some=20
				       =20

			comments/suggestions below=20
			   =20

				which you might consider for a new
revision.
			=09
				Best regards,
				Attila
				Ps.:I noticed that this is a 00 version,
so sorry if you think the=20
				comments are too editorial
			=09
			=09
				-Section 2, it seems to be more a
terminology/definition=20
				       =20

			section than=20
			   =20

				acronyms The following definitions would
be useful as well:
			=09
				Service Instance Drop Eligibility
Indicator (I-DEI): A=20
				       =20

			field of the=20
			   =20

				I-TAG which identifies the Service
Instance Drop=20
				       =20

			Eligibility of the=20
			   =20

				frame in the 802.1ah (PBBN) domain.
			=09
				Service instance priority code point
(I-PCP): A field of the I-TAG=20
				which identifies the service instance
priority of the frame in the=20
				802.1ah
				(PBBN) domain.
			=09
				I-tagged Service Interface: A 802.1ah
(PBBN) interface type over=20
				which an I-TAG immediately follows the
destination and source MAC=20
				addresses in the header of the Ethernet
frames.
			=09
				   =20
				       =20

				 =20
				     =20

			Yes,  I also agree , we'll add these.
			   =20

				Agree, since they are used in the text,
it make sense to=20
				     =20

			define them=20
			   =20

				up front.
			=09
				 =20
				     =20

				A note may be appropriate saying that:
These definitions will be=20
				removed in later versions by a reference
to the appropriate IEEE=20
				standard.
			=09
				   =20
				       =20

				I think it still would be good to keep
these definitions in=20
				     =20

			the draft=20
			   =20

				for sake of completeness.
			=09
			=09
				 =20
				     =20

			Yes, It's really a compromise between how much
we repeat in a=20
			document , and how much we want the document to
be clear.
		=09
			I usually err more on the clear side.
		=09
			   =20

				-Section 4 Applicability
				In the first paragraph I'm considering
if "I-SID to I-SID"=20
				should not be changed to "I-tagged
interface to I-tagged=20
				       =20

			interface".=20
			   =20

				I recognize that this might be more
limiting from an AC=20
				       =20

			point of view=20
			   =20

				but isn't this the intention?
			=09
				   =20
				       =20

				"I-SID to I-SID" is correct since it is
used to connect two I-SID=20
				aware forwarder rather than two Acs -
e.g., AC may not be=20
				     =20

			an I-tagged=20
			   =20

				service interface but still we want to
provide full-mesh of PW on a=20
				per I-SID basis.
			=09
				 =20
				     =20

			We can certainly change this definition , but in
general the=20
			other encap drafts are written with respect to
an AC.
			I just wanted to keep this one consistent.
		=09
			   =20

				After this paragraph something like "In
contrast to the=20
				       =20

			VLAN (tagged
			   =20

				mode) where 2^12 customer service
instances can be=20
				       =20

			distinguished, the=20
			   =20

				I-SID in the I-TAG increases scalability
by allowing 2^24 service=20
				instances." might highlight one
important aspect of the VLAN and=20
				I-SID scenario.
			=09
				   =20
				       =20

				Since we are using one PW per I-SID,
this scalability aspect of=20
				I-tagged is not used in our case.
			=09
				 =20
				     =20

				In the discussion further below in
Section 4 "I-SID aware"=20
				forwarders should be "I-TAG aware"
forwarders. For=20
				       =20

			instance for the=20
			   =20

				QoS discussions not only the I-SID but
also the I-PCP and=20
				       =20

			I-DEI may=20
			   =20

				be considered.
			=09
				Further, in the case of native CFM
Ethernet OAM and PW OAM=20
				interworking I can imagine that the No
Customer Addresses
				(NCA) field of the I-TAG may be
considered by the NSP and/or=20
				forwarder.
			=09
				   =20
				       =20

				=20
				Agree.
			=09
				 =20
				     =20

			ok.
			   =20

				-Regarding Sections 5 and 6, I do not
see the benefit of repeating=20
				general PW encapsulation procedures. In
my read only 6.2=20
				       =20

			provides new=20
			   =20

				information about the I-tagged mode all
other discussion could be=20
				removed with no harm and instead a
pointer to the already=20
				       =20

			defined PW=20
			   =20

				procedures could be added.
				(Do I mis something?)
			=09
				   =20
				       =20

				I guess it is there for sake of
completeness. It is up to Luca to=20
				decide what to do with it.
			=09
				 =20
				     =20

			I think that I would like to avoid too many
recursive=20
			reference to other documents. This document
needs to explain=20
			how to implement the PW without too many
references.
		=09
			   =20

				 =20
				     =20

				It would be beneficial to add a figure
focusing on the I-tagged=20
				Ethernet header and its PW
encapsulation, something like this:
			=09
					AC
PW
					        Forwarder
				------------		------------
				|   Data   |    		|   Data
|=20
				|----------|		|----------|
				|Other TAGs|		|Other TAGs|
				|----------|  		|----------|
				|  I-TAG   | ----|	|  I-TAG   |
				|----------|     |	|----------|
				|  SA MAC  |     |	|  SA MAC  |=20
				|----------|     |	|----------|
				|  DA MAC  |     |	|  DA MAC  |
				------------     |	|----------|
						     +-->	|Encap
(CW)|
						     |	|----------|
						     +-->	|
Demux  |
=09
|----------|
						     		|PSN
tunnel|
=09
------------
			=09
			=09
			=09
				   =20
				       =20

			Yes, this is a very good idea.  Is this figure
what we want ?=20
			No other tags shown ?
		=09
			Thanks.
			Luca
		=09
			   =20

				=20
				Agree, I think such figure would be
helpful.
			=09
				Thanks again for your comments,
				Ali
			=09
				 =20
				     =20

				   =20
				       =20

				 =20
				     =20

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

	=09
		 =20



------_=_NextPart_001_01C7CE2D.1BDFA75D
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.3132" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D107213919-24072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Yaakov,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D107213919-24072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D107213919-24072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>There are a number of scenarios in which we =
would need this=20
PW - please refer to my draft that I presented in last IETF. However, =
the=20
simplest scenario to consider is when trying to setup PWs between two =
I-comp=20
devices connected via an MPLS network. In such case, you need to map an =
I-SID to=20
a PW since there is neither a B-VID nor any B-MAC is used for =
forwarding.=20
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D107213919-24072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D107213919-24072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>-Ali</FONT></SPAN></DIV><BR>
<BLOCKQUOTE=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> Yaakov Stein =
[mailto:yaakov_s@rad.com]=20
  <BR><B>Sent:</B> Tuesday, July 24, 2007 12:34 PM<BR><B>To:</B> Luca =
Martini=20
  (lmartini)<BR><B>Cc:</B> PWE3 WG (E-mail); Ali Sajassi=20
  (sajassi)<BR><B>Subject:</B> RE: [PWE3] Re: Some comments on=20
  draft-martini-pwe3-802.1ah-pw-00.txt<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D934111219-24072007>Luca,</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D934111219-24072007></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D934111219-24072007>As I=20
  asked yesterday, can you explain the scenario where this is needed=20
  ?</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D934111219-24072007></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D934111219-24072007>I=20
  was assuming that&nbsp;you wanted to support internal internal links =
to a=20
  PBBN</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D934111219-24072007>with=20
  MPLS, in the case where there is an ISID but no =
BVID.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D934111219-24072007></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D934111219-24072007>But,=20
  in that case the B-DA is sufficient information for the=20
  switching,</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D934111219-24072007>since the ISID is only used by the BEB =
(backbone edge=20
  switch).</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D934111219-24072007></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D934111219-24072007>If&nbsp;switching other than on B-DA is=20
  required&nbsp;at the intermediate bridges,</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D934111219-24072007>then=20
  the BVID will used. A B-TAG looks just like an =
S-TAG,</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D934111219-24072007>and=20
  so can be handled by the existing VLAN-aware mode.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D934111219-24072007></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D934111219-24072007>If=20
  you want to replace the entire PBBN edge-to-edge,</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D934111219-24072007>then=20
  you don't need 1ah at all, just a regular Ethernet =
PW.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D934111219-24072007></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D934111219-24072007>So,=20
  for what scenario is the new mode needed ?</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D934111219-24072007></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D934111219-24072007>Y(J)S</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D934111219-24072007></SPAN></FONT>&nbsp;</DIV><BR>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Luca Martini =
[mailto:lmartini@cisco.com]=20
  <BR><B>Sent:</B> Tuesday, July 24, 2007 20:49<BR><B>To:</B> KOMPELLA=20
  Vach<BR><B>Cc:</B> PWE3 WG (E-mail); Ali Sajassi (sajassi); Attila =
Takacs=20
  (IJ/ETH)<BR><B>Subject:</B> Re: [PWE3] Re: Some comments on=20
  draft-martini-pwe3-802.1ah-pw-00.txt<BR></FONT><BR></DIV>
  <DIV></DIV>Vach,<BR><BR>PWs are built on the principle that we use the =
mpls=20
  label as the de-multiplexer.<BR>We can use a number of other header=20
  fields&nbsp; for the same purpose , but that does not make it a =
PW.<BR>For=20
  example , why not use the Frame-Relay DLCI to determine the egress =
port for a=20
  frame-relay PW and have just one label for the PE/service =
instance&nbsp;=20
  ?<BR>We came to the conclusion a long time ago, that it is more =
efficient to=20
  use the MPLS label as the de-multiplexer field.<BR>Not all devices =
will=20
  incorporate expensive hardware that can perform the double lookup. =
This has=20
  been one of the main reasons why PWs become so=20
  popular.<BR><BR><BR>Luca<BR><BR><BR><BR>KOMPELLA Vach wrote:=20
  <BLOCKQUOTE=20
  =
cite=3Dmid40B2D3B1A8D67246A33D2F5B832C17E774B34D@USDALSMBS03.ad3.ad.alcat=
el.com=20
  type=3D"cite"><PRE wrap=3D"">I don't see why we need this.  It sounds =
like a signaling method to
optimize what may or may not be achievable in hardware.

It's deja vu all over again with the tagged Ethernet PW which pretty
much was defined, IMHO, because of harware limitations.  By the time
ethernet services became a well-defined, those hardware limitations were
overcome, and the tagged PW has already become obsolete.

I say just process the I-Tag in the NSP.

-Vach =20

  </PRE>
    <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">-----Original Message-----
From: Luca Martini [<A class=3Dmoz-txt-link-freetext =
href=3D"mailto:lmartini@cisco.com">mailto:lmartini@cisco.com</A>]=20
Sent: Tuesday, July 10, 2007 3:14 PM
To: Ali Sajassi (sajassi)
Cc: Attila Takacs (IJ/ETH); PWE3 WG (E-mail)
Subject: [PWE3] Re: Some comments on=20
draft-martini-pwe3-802.1ah-pw-00.txt

Hello!

More comments inline.

Ali Sajassi (sajassi) wrote:
    </PRE>
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">Hi Attila,

Thanks for your comments. Please see my reply inline ....=20

 =20
      </PRE>
        <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">-----Original =
Message-----
From: Attila Takacs (IJ/ETH) [<A class=3Dmoz-txt-link-freetext =
href=3D"mailto:Attila.Takacs@ericsson.com">mailto:Attila.Takacs@ericsson.=
com</A>]
Sent: Tuesday, July 10, 2007 9:41 AM
To: Luca Martini (lmartini); Ali Sajassi (sajassi)
Subject: Some comments on draft-martini-pwe3-802.1ah-pw-00.txt

Hi Luca and Ali,

I just saw your draft on the pwe3 agenda...
It is a useful proposal, please find some=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE =
wrap=3D"">comments/suggestions below=20
    </PRE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">which you might =
consider for a new revision.

Best regards,
Attila
Ps.:I noticed that this is a 00 version, so sorry if you think the=20
comments are too editorial


-Section 2, it seems to be more a terminology/definition=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">section than=20
    </PRE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">acronyms The following =
definitions would be useful as well:

Service Instance Drop Eligibility Indicator (I-DEI): A=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">field of the=20
    </PRE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">I-TAG which identifies =
the Service Instance Drop=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">Eligibility of =
the=20
    </PRE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">frame in the 802.1ah =
(PBBN) domain.

Service instance priority code point (I-PCP): A field of the I-TAG=20
which identifies the service instance priority of the frame in the=20
802.1ah
(PBBN) domain.

I-tagged Service Interface: A 802.1ah (PBBN) interface type over=20
which an I-TAG immediately follows the destination and source MAC=20
addresses in the header of the Ethernet frames.

   =20
        </PRE></BLOCKQUOTE><PRE wrap=3D""> =20
      </PRE></BLOCKQUOTE><PRE wrap=3D"">Yes,  I also agree , we'll add =
these.
    </PRE>
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">Agree, since they are =
used in the text, it make sense to=20
      </PRE></BLOCKQUOTE><PRE wrap=3D"">define them=20
    </PRE>
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">up front.

 =20
      </PRE>
        <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">A note may be =
appropriate saying that: These definitions will be=20
removed in later versions by a reference to the appropriate IEEE=20
standard.

   =20
        </PRE></BLOCKQUOTE><PRE wrap=3D"">I think it still would be good =
to keep these definitions in=20
      </PRE></BLOCKQUOTE><PRE wrap=3D"">the draft=20
    </PRE>
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">for sake of completeness.


 =20
      </PRE></BLOCKQUOTE><PRE wrap=3D"">Yes, It's really a compromise =
between how much we repeat in a=20
document , and how much we want the document to be clear.

I usually err more on the clear side.

    </PRE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">-Section 4 =
Applicability
In the first paragraph I'm considering if "I-SID to I-SID"=20
should not be changed to "I-tagged interface to I-tagged=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">interface".=20
    </PRE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">I recognize that this =
might be more limiting from an AC=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">point of view=20
    </PRE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">but isn't this the =
intention?

   =20
        </PRE></BLOCKQUOTE><PRE wrap=3D"">"I-SID to I-SID" is correct =
since it is used to connect two I-SID=20
aware forwarder rather than two Acs - e.g., AC may not be=20
      </PRE></BLOCKQUOTE><PRE wrap=3D"">an I-tagged=20
    </PRE>
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">service interface but =
still we want to provide full-mesh of PW on a=20
per I-SID basis.

 =20
      </PRE></BLOCKQUOTE><PRE wrap=3D"">We can certainly change this =
definition , but in general the=20
other encap drafts are written with respect to an AC.
I just wanted to keep this one consistent.

    </PRE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">After this paragraph =
something like "In contrast to the=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">VLAN (tagged
    </PRE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">mode) where 2^12 =
customer service instances can be=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">distinguished, =
the=20
    </PRE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">I-SID in the I-TAG =
increases scalability by allowing 2^24 service=20
instances." might highlight one important aspect of the VLAN and=20
I-SID scenario.

   =20
        </PRE></BLOCKQUOTE><PRE wrap=3D"">Since we are using one PW per =
I-SID, this scalability aspect of=20
I-tagged is not used in our case.

 =20
      </PRE>
        <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">In the discussion =
further below in Section 4 "I-SID aware"=20
forwarders should be "I-TAG aware" forwarders. For=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">instance for the=20
    </PRE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">QoS discussions not =
only the I-SID but also the I-PCP and=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">I-DEI may=20
    </PRE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">be considered.

Further, in the case of native CFM Ethernet OAM and PW OAM=20
interworking I can imagine that the No Customer Addresses
(NCA) field of the I-TAG may be considered by the NSP and/or=20
forwarder.

   =20
        </PRE></BLOCKQUOTE><PRE wrap=3D"">=20
Agree.

 =20
      </PRE></BLOCKQUOTE><PRE wrap=3D"">ok.
    </PRE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">-Regarding Sections 5 =
and 6, I do not see the benefit of repeating=20
general PW encapsulation procedures. In my read only 6.2=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">provides new=20
    </PRE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">information about the =
I-tagged mode all other discussion could be=20
removed with no harm and instead a pointer to the already=20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">defined PW=20
    </PRE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">procedures could be =
added.
(Do I mis something?)

   =20
        </PRE></BLOCKQUOTE><PRE wrap=3D"">I guess it is there for sake =
of completeness. It is up to Luca to=20
decide what to do with it.

 =20
      </PRE></BLOCKQUOTE><PRE wrap=3D"">I think that I would like to =
avoid too many recursive=20
reference to other documents. This document needs to explain=20
how to implement the PW without too many references.

    </PRE>
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D""> =20
      </PRE>
        <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">It would be beneficial =
to add a figure focusing on the I-tagged=20
Ethernet header and its PW encapsulation, something like this:

	AC				PW
	        Forwarder
------------		------------
|   Data   |    		|   Data   |=20
|----------|		|----------|
|Other TAGs|		|Other TAGs|
|----------|  		|----------|
|  I-TAG   | ----|	|  I-TAG   |
|----------|     |	|----------|
|  SA MAC  |     |	|  SA MAC  |=20
|----------|     |	|----------|
|  DA MAC  |     |	|  DA MAC  |
------------     |	|----------|
		     +--&gt;	|Encap (CW)|
		     |	|----------|
		     +--&gt;	|   Demux  |
		 		|----------|
		     		|PSN tunnel|
				------------



   =20
        </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D"">Yes, this is a =
very good idea.  Is this figure what we want ?=20
No other tags shown ?

Thanks.
Luca

    </PRE>
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">=20
Agree, I think such figure would be helpful.

Thanks again for your comments,
Ali

 =20
      </PRE>
        <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">   =20
        </PRE></BLOCKQUOTE><PRE wrap=3D""> =20
      </PRE></BLOCKQUOTE><PRE =
wrap=3D"">_______________________________________________
pwe3 mailing list
<A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</A>
<A class=3Dmoz-txt-link-freetext =
href=3D"https://www1.ietf.org/mailman/listinfo/pwe3">https://www1.ietf.or=
g/mailman/listinfo/pwe3</A>

    </PRE></BLOCKQUOTE><PRE wrap=3D""><!---->
  </PRE></BLOCKQUOTE><BR></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C7CE2D.1BDFA75D--



--===============1515652656==
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://www1.ietf.org/mailman/listinfo/pwe3

--===============1515652656==--





From pwe3-bounces@ietf.org Wed Jul 25 15:13:54 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDmIr-0000Yr-4A; Wed, 25 Jul 2007 15:13:45 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1IDmIp-0000Vc-VP
	for pwe3-confirm+ok@megatron.ietf.org; Wed, 25 Jul 2007 15:13:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDmIp-0000UK-Ks
	for pwe3@ietf.org; Wed, 25 Jul 2007 15:13:43 -0400
Received: from dog.tcb.net ([64.78.150.133])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDmIo-0002Ch-Aw
	for pwe3@ietf.org; Wed, 25 Jul 2007 15:13:43 -0400
Received: by dog.tcb.net (Postfix, from userid 0)
	id 1311226848F; Wed, 25 Jul 2007 13:13:42 -0600 (MDT)
Received: from [IPv6:::1] (dog.tcb.net [64.78.150.133])
	(authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128)
	by dog.tcb.net with SMTP; for pwe3@ietf.org;
	Wed, 25 Jul 2007 13:13:42 -0600 (MDT) (envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=64.78.150.133;
	client-port=48949; data-bytes=0
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <0861CFEA-8895-4A55-A8D3-D15A371C7668@tcb.net>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: pwe3@ietf.org
From: Danny McPherson <danny@tcb.net>
Date: Wed, 25 Jul 2007 13:13:39 -0600
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Subject: [PWE3] WG LC: draft-ietf-pwe3-mpls-transport-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Folks,
Please consider today the beginning of a two week WG LC
for this draft.  WG LC will end on 2007-08-08.  Please provide
comments to pwe3@ietf.org ASAP.

Thanks!

-danny

Begin forwarded message:


> From: Internet-Drafts@ietf.org
> Date: May 23, 2007 1:50:02 PM MDT
> To: i-d-announce@ietf.org
> Cc: pwe3@ietf.org
> Subject: I-D ACTION:draft-ietf-pwe3-mpls-transport-00.txt
> Reply-To: internet-drafts@ietf.org
>
> 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		: Application of PWE3 to MPLS Transport Networks
> 	Author(s)	: S. Bryant, et al.
> 	Filename	: draft-ietf-pwe3-mpls-transport-00.txt
> 	Pages		: 11
> 	Date		: 2007-5-23
> 	
>    A key requirement has been identified by the operator community for
>    the transparent carriage of the MPLS network of one party over the
>    MPLS network of another party.  This document describes one IETF-
>    recommended profile to satisfy this requirement using the existing
>    RFC4448 PWE3 Ethernet pseudowire standard.  This solution does not
>    preclude other solutions being developed in the future.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-mpls- 
> transport-00.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
> the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>
> Internet-Drafts are also available by anonymous FTP. Login with the
> username "anonymous" and a password of your e-mail address. After
> logging in, type "cd internet-drafts" and then
> "get draft-ietf-pwe3-mpls-transport-00.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-pwe3-mpls-transport-00.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> Content-Type: text/plain
> Content-ID: <2007-5-23135506.I-D@ietf.org>
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/i-d-announce
>




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



From pwe3-bounces@ietf.org Thu Jul 26 11:15:47 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE53v-0001UA-Mm; Thu, 26 Jul 2007 11:15:35 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1IE53t-0001Nx-Ll
	for pwe3-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 11:15:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE53t-0001Nc-43; Thu, 26 Jul 2007 11:15:33 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IE53r-0000An-W0; Thu, 26 Jul 2007 11:15:33 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id EB76332897;
	Thu, 26 Jul 2007 15:15:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IE53N-0001gj-RZ; Thu, 26 Jul 2007 11:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IE53N-0001gj-RZ@stiedprstage1.ietf.org>
Date: Thu, 26 Jul 2007 11:15:01 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-fc-encap-04.txt 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
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, et al.
	Filename	: draft-ietf-pwe3-fc-encap-04.txt
	Pages		: 37
	Date		: 2007-7-26
	
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 procedures for using a PW to 
                  provide a Fibre Channel service.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-pwe3-fc-encap-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pwe3-fc-encap-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-7-26104749.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-fc-encap-04.txt

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

Content-Type: text/plain
Content-ID: <2007-7-26104749.I-D@ietf.org>


--OtherAccess--

--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://www1.ietf.org/mailman/listinfo/pwe3

--NextPart--





From pwe3-bounces@ietf.org Fri Jul 27 16:24:34 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEWMM-00055e-0A; Fri, 27 Jul 2007 16:24:26 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1IEWMJ-00055T-Rn
	for pwe3-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 16:24:23 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEWMJ-00055K-EO
	for pwe3@ietf.org; Fri, 27 Jul 2007 16:24:23 -0400
Received: from zcars04e.nortel.com ([47.129.242.56])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEWMI-00063P-Jq
	for pwe3@ietf.org; Fri, 27 Jul 2007 16:24:23 -0400
Received: from zcarhxm0.corp.nortel.com (zcarhxm0.corp.nortel.com
	[47.129.230.95])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	l6RKMY801894; Fri, 27 Jul 2007 20:22:34 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] WG LC: draft-ietf-pwe3-mpls-transport-00.txt
Date: Fri, 27 Jul 2007 16:24:16 -0400
Message-ID: <085091CB2CA14E4B8B163FFC37C84E9D10F4E87B@zcarhxm0.corp.nortel.com>
In-Reply-To: <0861CFEA-8895-4A55-A8D3-D15A371C7668@tcb.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] WG LC: draft-ietf-pwe3-mpls-transport-00.txt
Thread-Index: AcfO7/htBeyItneRTSiSR21V6VcSdQBlhIlQ
References: <0861CFEA-8895-4A55-A8D3-D15A371C7668@tcb.net>
From: "Hamid Ould-Brahim" <hbrahim@nortel.com>
To: "Danny McPherson" <danny@tcb.net>, <pwe3@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93e7fb8fef2e780414389440f367c879
Cc: 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org


Couple of comments on the draft:


- As a general comment, I think a key motivation behind=20
  this draft is to define an IETF/PWE3 profile on how best to=20
  meet ITU T-MPLS requirements using exclusively IETF PWE3 and=20
  MPLS protocols. In simple words, this draft is what IETF
  PWE3 WG thinks the best design/arch to meet T-MPLS requirements=20
  (reqs listed in the ITU-T liaisons referenced in the draft).=20

  However nowhere in this version of the draft the=20
  motivation or context of this draft is being captured.=20
  I think it will be useful if this draft captures=20
  the motivation or similar text such that we can relate this work=20
  to T-MPLS activities/discussions that led to this work in=20
  the first place.

- Section 4 (MPLS Layer)

 First sentence:

"This section describes the profile of the MPLS RFC3031 [RFC3031] PSN".

However section 4.2 includes GMPLS-based control plane for
setting up transport LSP. I suggest the first sentence in section=20
4 to include then a reference to GMPLS architecture RFC [RFC3945]. =20

Hamid.

> -----Original Message-----
> From: Danny McPherson [mailto:danny@tcb.net]=20
> Sent: Wednesday, July 25, 2007 3:14 PM
> To: pwe3@ietf.org
> Subject: [PWE3] WG LC: draft-ietf-pwe3-mpls-transport-00.txt
>=20
> Folks,
> Please consider today the beginning of a two week WG LC for=20
> this draft.  WG LC will end on 2007-08-08.  Please provide=20
> comments to pwe3@ietf.org ASAP.
>=20
> Thanks!
>=20
> -danny
>=20
> Begin forwarded message:
>=20
>=20
> > From: Internet-Drafts@ietf.org
> > Date: May 23, 2007 1:50:02 PM MDT
> > To: i-d-announce@ietf.org
> > Cc: pwe3@ietf.org
> > Subject: I-D ACTION:draft-ietf-pwe3-mpls-transport-00.txt
> > Reply-To: internet-drafts@ietf.org
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts=20
> > directories.
> > This draft is a work item of the Pseudowire Emulation Edge to Edge=20
> > Working Group of the IETF.
> >
> > 	Title		: Application of PWE3 to MPLS Transport Networks
> > 	Author(s)	: S. Bryant, et al.
> > 	Filename	: draft-ietf-pwe3-mpls-transport-00.txt
> > 	Pages		: 11
> > 	Date		: 2007-5-23
> > =09
> >    A key requirement has been identified by the operator=20
> community for
> >    the transparent carriage of the MPLS network of one=20
> party over the
> >    MPLS network of another party.  This document describes one IETF-
> >    recommended profile to satisfy this requirement using=20
> the existing
> >    RFC4448 PWE3 Ethernet pseudowire standard.  This=20
> solution does not
> >    preclude other solutions being developed in the future.
> >
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-pwe3-mpls-
> > transport-00.txt
> >
> > To remove yourself from the I-D Announcement list, send a=20
> message to=20
> > i-d-announce-request@ietf.org with the word unsubscribe in=20
> the body of=20
> > the message.
> > You can also visit=20
> https://www1.ietf.org/mailman/listinfo/I-D-announce
> > to change your subscription settings.
> >
> > Internet-Drafts are also available by anonymous FTP. Login with the=20
> > username "anonymous" and a password of your e-mail address. After=20
> > logging in, type "cd internet-drafts" and then "get=20
> > draft-ietf-pwe3-mpls-transport-00.txt".
> >
> > A list of Internet-Drafts directories can be found in=20
> > http://www.ietf.org/shadow.html or=20
> > ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> > Internet-Drafts can also be obtained by e-mail.
> >
> > Send a message to:
> > 	mailserv@ietf.org.
> > In the body type:
> > 	"FILE /internet-drafts/draft-ietf-pwe3-mpls-transport-00.txt".
> > =09
> > NOTE:	The mail server at ietf.org can return the document in
> > 	MIME-encoded form by using the "mpack" utility.  To use this
> > 	feature, insert the command "ENCODING mime" before the "FILE"
> > 	command.  To decode the response(s), you will need "munpack" or
> > 	a MIME-compliant mail reader.  Different MIME-compliant=20
> mail readers
> > 	exhibit different behavior, especially when dealing with
> > 	"multipart" MIME messages (i.e. documents which have been split
> > 	up into multiple messages), so check your local documentation on
> > 	how to manipulate these messages.
> >
> > Below is the data which will enable a MIME compliant mail reader=20
> > implementation to automatically retrieve the ASCII version of the=20
> > Internet-Draft.
> > Content-Type: text/plain
> > Content-ID: <2007-5-23135506.I-D@ietf.org>
> >
> > _______________________________________________
> > I-D-Announce mailing list
> > I-D-Announce@ietf.org
> > https://www1.ietf.org/mailman/listinfo/i-d-announce
> >
>=20
>=20
>=20
>=20
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
>=20


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



From pwe3-bounces@ietf.org Tue Jul 31 12:24:31 2007
Return-path: <pwe3-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFuWH-0002jB-0B; Tue, 31 Jul 2007 12:24:25 -0400
Received: from pwe3 by megatron.ietf.org with local (Exim 4.43)
	id 1IFuWF-0002ip-Qc
	for pwe3-confirm+ok@megatron.ietf.org; Tue, 31 Jul 2007 12:24:23 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFuWF-0002iS-CI
	for pwe3@ietf.org; Tue, 31 Jul 2007 12:24:23 -0400
Received: from dog.tcb.net ([64.78.150.133])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFuWE-0008DF-Qk
	for pwe3@ietf.org; Tue, 31 Jul 2007 12:24:23 -0400
Received: by dog.tcb.net (Postfix, from userid 0)
	id 351AC26848F; Tue, 31 Jul 2007 10:24:22 -0600 (MDT)
Received: from [10.0.9.76] (bedford.lex.arbor.net [204.118.128.2])
	(authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128)
	by dog.tcb.net with SMTP; for pwe3@ietf.org;
	Tue, 31 Jul 2007 10:24:21 -0600 (MDT) (envelope-from danny@tcb.net)
Mime-Version: 1.0 (Apple Message framework v752.3)
To: pwe3@ietf.org
Message-Id: <037A1AFA-C501-4DC0-93F7-2C05072A13C6@tcb.net>
Content-Type: multipart/mixed; boundary=Apple-Mail-2--714070979
References: <OF2FE628F8.76333EF9-ON80257322.00555CDE-80257322.00558DD4@netfr.alcatel.fr>
From: Danny McPherson <danny@tcb.net>
Date: Tue, 31 Jul 2007 10:24:02 -0600
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 1.8 (+)
X-Scan-Signature: cd3d702b63698072ba67a75ce9e0fc9e
Subject: [PWE3] PWE3 @IETF 69 - Draft Minutes
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org


--Apple-Mail-2--714070979
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed


Thanks Matthew!

Folks,
Please provide corrections to Matthew, Stewart and I ASAP.

Thanks!

-danny


Begin forwarded message:

> From: Matthew.Bocci@alcatel-lucent.co.uk
> Date: July 24, 2007 9:34:28 AM MDT
> To: stbryant@cisco.com, danny@tcb.net
> Subject: PWE3 minutes
>
> Stewart, Danny,
>
> Please find the draft minutes attached.
>
> Please let me know if you have any comments/corrections.
>
> Thanks,
>
> Matthew
>
>
> -----------------------------------------
> Matthew Bocci
> IP Division,
> Alcatel-Lucent Telecom Limited,
> Registered Office: Christchurch Way, Greenwich, London SE10 0AG.
> Registered in England & Wales number 02650571
> -----------------------------------------
>
> (See attached file: PWE3-Minutes-00.txt)
--Apple-Mail-2--714070979
Content-Transfer-Encoding: quoted-printable
Content-Type: application/octet-stream; x-unix-mode=0666;
	name=PWE3-Minutes-00.txt
Content-Disposition: attachment;
	filename=PWE3-Minutes-00.txt

MONDAY,=20July=2023rd,=202007=20-=2013:00=20-=2015:00=20=0D=0A=
-----------------------------------=20=0D=0ACHAIRS:=20Danny=20McPherson=20=
&=20Stewart=20Bryant=20=0D=0ASCRIBE:=20Matthew=20Bocci=20=0D=0A=20=0D=0A=20=
=0D=0AWG=20Status=20and=20Update=20-=20Chairs=20=0D=0A=
-----------------------------=20=0D=0ATwo=20new=20RFCs=20-=20cell=20=
transport=20and=20wildcard.=20=0D=0ARFC=20Eds=20queue=20-=20AII=20=
aggregation.=20Waiting=20for=20L2VPN=20signalling,=20which=20is=20=
waiting=20=0D=0Afor=20segmented=20PW=20draft,=20which=20is=20waiting=20=
for=20MS-PW=20requirements.=20=0D=0ATDMoIP=20and=20CESoPSN=20are=20=
waiting=20for=20VCCV.=20=20=0D=0Adraft-malis=20(SonetoMPLS)=20is=20with=20=
IESG=20as=20independent=20submission=20-=20will=20go=20as=20=0D=0A=
historic=20RFC.=20=0D=0APW=20type=208=20and=2010=20both=20point=20to=20=
CEM=20-=20they=20should=20point=20to=20CEP=20and=20CEM.=20=0D=0AMIBS=20=
in=20last=20call.=20=0D=0A=20=0D=0AWork=20in=20progress:=20=0D=0A-=20=
Congestion=20framework.=20Alison=20Mankin=20is=20transport=20area=20=
advisor=20for=20this.=20=0D=0A-=20FC=20encap.=20Comments=20received=20=
from=20transport=20area.=20Authors=20are=20currently=20=0D=0Arevising=20=
the=20draft.=20=0D=0A-=20MPLS=20transport=20-=20discuss=20on=20this=20=
agenda=20later=20=0D=0A=20=0D=0AMS-PW=20architecture=20is=20waiting=20on=20=
getting=20requirements=20through.=20=0D=0Aoam-msg-map=20is=20being=20=
revised=20and=20will=20then=20be=20ready=20for=20last=20call.=20=0D=0A=
Segmented-pw=20and=20dynamic-ms-pw=20are=20work=20in=20progress.=20=0D=0A=
=20=0D=0ANeed=20WG=20drafts=20on=20PW=20protection=20and=20restoration.=20=
=0D=0A=20=0D=0APossible=20new=20items:=20=0D=0A-=20MPLS=20PW=20=0D=0A-=20=
Multipoint=20PWs=20=0D=0A=20=0D=0A=20=0D=0APseudowire=20Virtual=20=
Circuit=20Connectivity=20Verification=20(VCCV)=20A=20Control=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=0D=0AChannel=20for=20=
Pseudowires=20-=20Tom=20Nadeau=20(tnadeau@cisco.com)=20=0D=0A=
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-vccv-14.txt=20=0D=0A=
---------------------------------------------------------------=20=0D=0A=20=
=0D=0AThis=20received=20extensive=20IESG=20review.=20Made=20significant=20=
changes=20as=20a=20result=20of=20=0D=0Athis:=20=0D=0A-=20BFD=20CC=20and=20=
CV=20types=20have=20been=20removed.=20These=20are=20in=20another=20=
draft.=20=0D=0A-=20Improved=20readability.=20=0D=0A-=20Many=20editorial=20=
changes.=20=0D=0A-=20Improved=20security=20section.=20=0D=0A=20=0D=0A=
Next=20steps:=20need=20to=20clear=202=20remaining=20DISCUSS=20states,=20=
to=20do=20with=20congestion.=20=0D=0ANeed=20one=20more=20AD=20to=20=
approve=20before=20moving=20forward.=20=0D=0A=20=0D=0AWe=20hope=20to=20=
do=20this=20in=20the=20next=20month=20or=20so,=20and=20will=20publish=20=
v15=20afterwards.=20=0D=0A=20=0D=0AStewart:=20needs=20WG=20last=20call=20=
because=20of=20the=20scale=20of=20the=20changes.=20=0D=0A=20=0D=0ADon=20=
O'Connor:=20What=20is=20the=20new=20draft?=20=0D=0ATom:=20will=20take=20=
BFD=20CV=20and=20CC=20components=20verbatim.=20=0D=0AStewart:=20The=20=
comment=20was=20that=20there=20were=20lots=20of=20things=20thrown=20into=20=
one.=20With=20=0D=0ABFD,=20it=20is=20a=20new=20mechanism=20so=20is=20a=20=
better=20compartmentalism.=20No=20technical=20=0D=0Achanges.=20=0D=0A=
George=20Swallow:=20BFD=20still=20hasn't=20moved=20very=20far,=20so=20=
this=20breaks=20the=20deadlock.=20=0D=0AStewart:=20this=20way,=20no=20=
normative=20references=20that=20are=20not=20already=20RFCs.=20=0D=0A=0D=0A=
=0D=0A=20=0D=0APreferential=20Forwarding=20Status=20Bit=20Definition=20-=20=
Mustapha=20Aissaoui=20=0D=0A(mustapha.aissaoui@alcatel-lucent.co.uk)=20=0D=
=0A=
http://www.ietf.org/internet-drafts/draft-muley-dutta-pwe3-redundancy-bit-=
01.txt=20=0D=0A=
--------------------------------------------------------------------------=
------=20=0D=0ANew=20revision.=20=0D=0AAdd=20a=20new=20contributor.=20=0D=
=0AExpanded=20on=20motivation=20of=20status=20bit.=20=0D=0AAdded=20=
separate=20definition=20of=20active/standby=20PW=20states=20for=20=
independent=20mode=20etc=20=0D=0AEnforced=20rule=20that=20endpoint=20=
MUST=20not=20forward=20over=20PW=20in=20standby=20mode=20=0D=0ARemoved=20=
the=20option=20to=20send=20the=20PW=20not=20forwarding=20status=20bit=20=
could=20not=20unblock=20=0D=0APW.=20=0D=0AAdded=20applicability=20and=20=
backward=20compatibility.=20=0D=0ARemoved=20reference=20to=20LDP=20and=20=
point=20to=20RFC4447=20for=20security.=20=0D=0A=20=0D=0AActive=20state=20=
is=20where=20PW=20label=20are=20exchanged=20between=20two=20endpoints,=20=
and=20status=20=0D=0Abits=20exchanged=20between=20endpoints=20indicate=20=
the=20PW=20is=20in=20active=20state.=20=0D=0ASimilarly=20in=20standby=20=
state.=20=0D=0A=20=0D=0AInterop=20with=20existing=20implementations:=20=0D=
=0A-=20Mechanisms=20are=20OPTIONAL=20and=20=20=0D=0A-=20Must=20negotiate=20=
use=20of=20status=20TLV=20=0D=0A-=20PE=20implementation=20could=20=
support=20status,=20but=20not=20this=20bit.=20Procedures=20in=20this=20=0D=
=0Adraft=20will=20not=20be=20used.=20=0D=0A=20=0D=0ANext=20steps:=20=0D=0A=
Could=20change=20to=202=20bits:=20=20=0D=0A-=20=20request=20to=20switch=20=
=0D=0A-=20=20view=20of=20the=20state=20at=20far=20end=20=0D=0A=20=0D=0A=
Would=20like=20feedback=20further=20WG=20feedback.=20=0D=0A=20=0D=0ADon=20=
O'Connor:=20Any=20plans=20for=20mechanics=20of=20protection=20switching?=20=
Or=20is=20this=20for=20=0D=0Acompanion=20draft?=20Any=20plans=20for=20=
revertive=20mode?=20=0D=0AMustapha:=20Need=20to=20discuss=20this,=20but=20=
don't=20want=20to=20make=20it=20too=20complicated.=20Don't=20=0D=0Aplan=20=
to=20go=20to=20a=20very=20complex=20mechanism,=20but=20here=20may=20be=20=
a=20value=20in=20it.=20=0D=0A=20=0D=0ADanny:=20will=20ask=20if=20this=20=
should=20be=20a=20WG=20draft=20on=20the=20mailing=20list.=20=0D=0A=20=0D=0A=
=20=0D=0A=20=0D=0AMS-PW=20Requirements=20-=20Luca=20Martini=20=
(lmartini@cisco.com)=20=0D=0A=
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-ms-pw-requirements-05.=
txt=20=0D=0A=
--------------------------------------------------------------------------=
---=20=0D=0A=20=0D=0AIn=20IESG=20review.=20=0D=0AReceived=20several=20=
discusses.=20Some=20are=20resolved.=20=0D=0A-=20Points=20about=20RFC=20=
3985=20still=20applying.=20Congestion=20mitigation=20does=20not=20add=20=0D=
=0Aanything,=20but=20makes=20it=20clear=20it=20is=20more=20of=20a=20=
requirement.=20=0D=0A-=20Clarification=20of=20meaning=20of=20OAM=20=0D=0A=
Dan=20still=20has=20a=20requirement=20that=20this=20should=20be=20=
provisioned=20by=20CLI.=20=0D=0AThis=20is=20a=20problem=20e.g=20some=20=
might=20use=20GUI.=20This=20is=20a=20protocol=20requirements=20draft.=20=0D=
=0AThis=20point=20is=20still=20under=20discussion.=20=0D=0A=20=0D=0A=
Resolved=20comment=20about=20mandatory=20to=20implement=20PSN=20=
security.=20=0D=0AMore=20security=20comments=20still=20need=20to=20be=20=
resolved.=20=0D=0A=20=0D=0A=20=0D=0A=20=0D=0ADynamic=20Placement=20of=20=
Multi=20Segment=20Pseudo=20Wires=20-=20Luca=20Martini=20=0D=0A=
(lmartini@cisco.com)=0D=0A=
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-dynamic-ms-pw-05.txt=20=
=0D=0A=
------------------------------------------------------------------------=20=
=0D=0A=20=0D=0AAdded=20text=20to=20explain=20the=20procedure=20if=20PW=20=
label=20mapping=20is=20immediately=20released.=20=0D=0AAdded=20a=20=
procedure=20to=20handle=20if=20AII=20unreachable=20case.=20=0D=0A=
Incorporated=20comments=20from=20WG.=20=0D=0AAllocated=20BGP=20SAFI,=20=
and=20new=20LDP=20TLV/status=20code=20points.=20=0D=0A=20=0D=0AWould=20=
prefer=20if=20people=20mail=20comments=20to=20the=20list,=20rather=20=
than=20personally.=20=0D=0A=20=0D=0ALuca=20would=20like=20to=20use=20=
early=20allocation=20process.=20Would=20need=20to=20come=20from=20chair=20=
=0D=0Aof=20IDR=20for=20BGP=20AFI/SAFI.=20=0D=0A=20=0D=0AStewart=20-=20we=20=
are=20working=20through=20the=20process=20of=20getting=20allocation.=20=
Has=20to=20come=20=0D=0Afrom=20IDR.=20=0D=0A=20=0D=0AAlison=20Mankin=20-=20=
This=20is=20about=20the=20LDP=20question.=20You=20said=20you=20could=20=
not=20make=20a=20=0D=0Arequirement=20on=20security.=20But=20this=20is=20=
about=20inter-domain=20cases,=20and=20is=20especially=20=0D=0Afor=20=
users=20of=20the=20protocol.=20=20=0D=0A=20=0D=0AYakov=20Rekhter=20-=20=
There=20is=20a=20document=20in=20L2VPN=20called=20L2VPN=20signalling.=20=
That=20=0D=0Adescribes=20how=20to=20place=20a=20MS-PW.=20Can=20you=20use=20=
them=20together?=20=0D=0ALuca=20-=20that=20is=20about=20provisioning=20=
using=20BGP.=20Cannot=20use=20them=20together,=20but=20they=20=0D=0Acan=20=
coexist.=20=20=0D=0AYakov=20Rekhter=20-=20would=20lie=20to=20spell=20=
this=20out=20explicitly=20=0D=0AYakov=20Rekhter=20-=20There=20is=20a=20=
different=20NLRI=20format=20in=20Eric's=20document.=20=0D=0ALuca=20-=20=
that=20is=20an=20addressing=20plan=20for=20a=20service.=20This=20is=20a=20=
PW.=20Eric's=20document=20=0D=0Aoptimised=20for=20a=20service.=20This=20=
document=20is=20meant=20to=20aggregate=20the=20reachability=20so=20=0D=0A=
if=20you=20don't=20need=20to=20advertise=20for=20every=20PW.=20This=20=
addressing=20scheme=20allows=20=0D=0Aoptimization.=20=20=20=0D=0AYakov=20=
Rekhter=20-=20just=20to=20clarify=20that=20the=20two=20should=20not=20be=20=
used=20together=20for=20the=20=0D=0Asame=20AC.=20=0D=0AVach=20Kompella=20=
-=20Why=20can=20they=20not=20be=20used=20together?=20One=20is=20doing=20=
routing=20and=20one=20=0D=0Ais=20doing=20discovery.=20=0D=0AYakov=20=
Rekhter=20-=20not=20for=20the=20same=20set=20of=20ACs=20=0D=0ARahul=20=
Aggarwal=20-=20Appears=20that=20the=20only=20difference=20is=20that...=20=
=20=0D=0A=20=0D=0AStewart=20-=20Take=20to=20the=20list=20and=20come=20up=20=
with=20definitive=20text=20on=20why=20they=20are=20=0D=0Agoing=20to=20be=20=
the=20same=20or=20not=20=0D=0A=20=0D=0A=20=0D=0A=20=0D=0A=20=0D=0A=
802.1ah=20Pseudowire=20-=20Luca=20Martini=20(lmartini@cisco.com)=20=0D=0A=
http://www.ietf.org/internet-drafts/draft-martini-pwe3-802.1ah-pw-00.txt=20=
=0D=0A=
------------------------------------------------------------------------=20=
=0D=0A=20=0D=0AExplains=20the=20new=20PW=20type.=20This=20binds=20port=20=
and=20ISID.=20E.g.=20similar=20to=20the=20VLAN=20=0D=0Atype=20we=20have=20=
today.=20=0D=0AThe=20ISID=20is=20the=20service=20identifier.=20=0D=0A=20=0D=
=0AKeep=20the=20single=20lookup=20architecture=20that=20is=20the=20basis=20=
of=20all=20PWs.=20=0D=0A=20=0D=0AThe=20label=20uniquely=20identifies=20=
what=20the=20egress=20port=20is,=20and=20what=20the=20header=20=0D=0A=
rewriting=20procedure=20is.=20=0D=0A=20=0D=0ADraft=20uses=20RFC4448=20as=20=
a=20template.=20=0D=0ANeed=20to=20incorporate=20some=20comments=20e.g.=20=
congestion=20handling=20text=20and=20is=20CW=20=0D=0Aoptional=20=0D=0A=20=
=0D=0A=0D=0AFlorin=20Balus=20-=20Can=20you=20clarify=20that=20you=20are=20=
using=20this=20for=20ITAG=20interfaces?=20=0D=0ALuca=20-=20Yes=20=0D=0A=
Yakov=20Stein=20-=20The=20title=20.1ah=20does=20not=20properly=20=
describe=20this.=20This=20does=20not=20=0D=0Acover=20BVID.=20So=20=
perhaps=20you=20should=20put=20in=20abstract=20or=20correct=20the=20=
title.=20=0D=0AAli=20Sajassi=20-=20The=20draft=20is=20not=20the=20name=20=
of=20the=20PW.=20The=20PW=20is=20ITAG=20PW.=20If=20the=20=0D=0Ainterface=20=
is=20ITAG=20it=20is=20ACs,=20but=20if=20it=20is=20VPLS,=20you=20are=20=
talking=20about=20the=20=0D=0Ainternal=20of=20the=20box.=20=0D=0AYakov=20=
Stein=20-=20Since=20ah=20is=20already=20a=20client=20of=20Ethernet,=20=
and=20so=20is=20this,=20maybe=20a=20=0D=0Adiagram=20to=20explain=20why=20=
you=20really=20need=20this.=20=0D=0A=20=0D=0ADanny=20-=20Will=20likely=20=
see=20WG=20doc=20request=20on=20the=20mailing=20list.=20=0D=0A=20=0D=0A=20=
=0D=0ASetup=20and=20Manage=20PBB-based=20Tunnels=20with=20PWE3=20=
Mechanism=20-=20Ping=20Pan=20=0D=0A(ppan@hammerheadsystems.com)=20=0D=0A=
http://www.ietf.org/internet-drafts/draft-pan-pwe3-pbb-tunnels-00.txt=20=0D=
=0A---------------------------------------------------------------------=20=
=0D=0A=20=0D=0ANot=20a=20debate=20of=20MPLS=20vs.=20PBT.=20This=20is=20=
addressing=20a=20particular=20problem.=20=0D=0AThe=20problem=20is=20that=20=
there=20are=20access=20VLAN=20networks=20interconnected=20by=20a=20=
MAC-in-=0D=0AMAC=20network.=20=0D=0ANeed=20to=20know=20how=20to=20setup=20=
and=20manage=20VLAN=20circuits.=20=0D=0AHow=20to=20extend=20Ethernet=20=
to=20the=20core?=20=0D=0AFor=20operational=20reasons,=20may=20not=20use=20=
MPLS=20at=20the=20edge.=20This=20is=20a=20migration=20step.=20=0D=0A=20=0D=
=0AWays=20to=20setup=20the=20edge-to-edge=20tunnels=20=0D=0A-=20Existing=20=
practice:=20static=20configuration=20=0D=0A-=20Other=20proposals=20=
dynamic=20signalling=20proposals=20=0D=0A-=20Outside=20the=20scope=20=0D=0A=
=20=0D=0AProposes=20to=20use=20LDP=20to=20setup=20the=20PBB=20tunnel=20=0D=
=0A=20=0D=0AShows=20the=20header.=20=0D=0A=20=0D=0AEncode=20MAC-in-MAC=20=
header=20in=20AII=20and=20AGI=20=0D=0A=20=0D=0AAsks=20for=20new=20AII=20=
type=20=20=0D=0A=20=0D=0AAli=20Sajassi:=20Debate=20is=20whether=20this=20=
draft=20is=20needed.=20There=20are=20inaccuracies=20in=20=0D=0Athe=20=
draft=20about=20PBB.=20=0D=0APing:=20Are=20we=20trying=20to=20set=20up=20=
tunnel=20or=20PW?=20The=20PW=20is=20inside=20the=20tunnel.=20We=20do=20=0D=
=0Anot=20touch=20the=20tunnel.=20=0D=0AAli=20Sajassi:=20You=20do=20not=20=
need=20to=20tell=20the=20PE=20the=20MAC=20address.=20It=20does=20this=20=
though=20=0D=0AARP.=20If=20you=20are=20trying=20to=20set=20up=20a=20.1ah=20=
PW,=20there=20is=20already=20a=20draft=20for=20this.=20=0D=0AAdrian=20=
Farrel=20-=20don't=20see=20any=20mention=20of=20Internet=20protocols=20=
in=20this=20draft=20=0D=0AKireeti=20Kompella=20-=20PWE3=20charter=20says=20=
over=20IETF=20PSNs.=20PBB=20is=20not=20an=20IETF=20PSN.=20=0D=0AStewart=20=
-=20This=20would=20definitely=20need=20a=20charter=20change.=20We=20need=20=
to=20debate=20if=20we=20=0D=0Ashould=20be=20doing=20this=20work=20or=20=
not.=20=0D=0APing=20Pan=20-=20Let's=20try=20to=20work=20out=20if=20this=20=
is=20useful.=20=0D=0A?=20-=20Need=20to=20signal=20a=20tunnel=20per=20=
service=20instance.=20You=20will=20also=20get=20P2MP=20=0D=0Atunnels.=20=
PBB=20would=20give=20you=20P2MP=20tunnels=20=0D=0ALuca=20Martini=20-=20=
Suggest=20reading=20the=20LDP=20RFC.=20No=20FEC=20for=20what=20you=20=
have=20written.=20=0D=0AThere=20is=20also=20no=20MPLS=20here,=20so=20=
what=20is=20this=20doing=20here?=20=0D=0APing=20-=20just=20using=20the=20=
signalling=20protocol=20=0D=0ALoa=20Andersson=20-=20need=20to=20make=20=
it=20clear=20that=20don't=20want=20to=20say=20this=20is=20not=20a=20=0D=0A=
problem.=20But=20we=20started=20the=20PWE3=20working=20group=20to=20set=20=
up=20PWs=20over=20the=20Internet.=20=0D=0AIt=20is=20a=20gross=20charter=20=
violation.=20=0D=0AYakov=20Stein=20-=20this=20is=20the=20same=20issue=20=
as=20the=20GELs=20BoF.=20Found=20that=20we=20needed=20to=20=0D=0Aliaise=20=
to=20the=20IEEE.=20Could=20apply=20what=20happened=20to=20gels=20and=20=
look=20to=20CCAMP.=20=0D=0A?=20-=20Problem=20in=20GELS=20was=20not=20to=20=
define=20a=20new=20data=20plane.=20=0C=0D=0A=0D=0A=0D=0A=0D=0A=0D=0A=0D=0A=
Ping=20Pan=20-=20we=20should=20not=20make=20a=20religion=20out=20of=20=
this.=20We=20are=20engineers=20and=20have=20=0D=0Aa=20real=20problem=20=
to=20solve=20in=20Ethernet.=20=0D=0A=20=0D=0AStewart=20-=20we=20are=20=
concerned=20about=20other=20SDOs=20rewriting=20our=20protocols.=20We=20=
should=20=0D=0Anot=20be=20doing=20this=20without=20IEEE=20consensus.=20=0D=
=0A=20=0D=0AMark=20Townsley=20-=20Need=20to=20think=20about=20what=20the=20=
full=20implications=20are.=20This=20is=20why=20=0D=0Awe=20go=20through=20=
the=20re-chartering=20process.=20=0D=0A=20=0D=0ADanny=20-=20Please=20=
comment=20on=20this=20on=20the=20mailing=20list.=20=0D=0A=20=0D=0A=20=0D=0A=
=20=0D=0APTP=20over=20MPLS=20-=20Roh=20Cohen=20=
(ronc@resolutenetworks.com)=20=0D=0A=
http://www.ietf.org/internet-drafts/draft-ronc-ptp-mpls-00.txt=20=0D=0A=
--------------------------------------------------------------=20=0D=0A=20=
=0D=0APTP=20is=20protocol=20delivering=20time=20synchronisation=20from=20=
master=20to=20slaves.=20=20=0D=0AForms=20a=20hierarchy=20of=20master=20=
and=20slaves=20=0D=0ASignalling=20messages=20exchanged=20between=20clock=20=
for=20negotiation,=20setup,=20etc.=20=0D=0AEntities:=20PTP=20clock,=20=
Boundary=20clock,=20transparent=20clocks=20=0D=0AShows=20sync=20and=20=
delay=20req=20formats.=20=0D=0A=20=0D=0APTP=20defined=20for=20Ethernet=20=
(802.1as...)=20and=20IP=20=0D=0A=20=0D=0AProposes=20to=20take=20PTP=20=
and=20map=20directly=20over=20a=20PW.=20=0D=0AShows=20detail=20of=20the=20=
encapsulation.=20=0D=0AScope=20is=20limited=20to=20P2P=20LSPs.=20=0D=0A=
Shows=20model=20with=20transparent=20clocks.=20=0D=0AModel=20is=20=
similar=20to=20MS-PWs,=20except=20S-PE=20not=20only=20switches=20the=20=
labels,=20but=20there=20=0D=0Ais=20native=20service=20processing.=20=0D=0A=
=20=0D=0ACommunications=20path=20maps=20into=20a=20set=20of=20LSPs.=20=0D=
=0APTP=20domains=20are=20sent=20on=20different=20PTP=20LSPs.=20=0D=0A=20=0D=
=0ASuggests=20using=20LDP=20for=20setting=20up=20bidirectional=20LSPs,=20=
and=20using=20PTP=20PW=20types=20=0D=0A-=20End=20to=20end=20=0D=0A-=20=
Peer=20to=20peer=20=0D=0A=20=0D=0AOpen=20issues:=20=0D=0A-=20Traffic=20=
engineering=20=0D=0A-=20Use=20of=20RSVP-TE=20for=20tunnel=20LSP=20=0D=0A=
-=20Automatic=20protection=20switching=20=0D=0A-=20FEC=20collision=20in=20=
P2MP=20LSPs=20=0D=0A=20=0D=0APWE3=20is=20right=20place=20to=20advance=20=
this=20work=20=0D=0A-=20right=20place=20to=20progress=20non-IP=20over=20=
MPLS=20=0D=0A=20=0D=0AAdd=20to=20PWE3=20and=20add=20to=20TICTOC=20if=20=
chartered.=20=0D=0A=20=0D=0AYakov=20Stein=20-=20Lots=20of=20good=20=
points,=20but=20a=20bit=20uncomfortable=20using=20PW=20for=20this.=20=0D=0A=
PWs=20are=20for=20carrying=20data.=20You=20are=20also=20saying=20you=20=
set=20up=20a=20MS-PW,=20with=20a=20=0D=0Astitching=20point=20which=20has=20=
an=20NSP=20in=20it.=20=0D=0ARon=20-=20might=20be=20easier=20not=20to=20=
use=20the=20stitching=20model.=20Instead=20have=20two=20separate=20=0D=0A=
PWs=20set=20up=20between=20PEs=20containing=20transparent=20=20=0D=0A=
Yakov=20Stein=20-=20the=20right=20place=20to=20do=20this=20is=20TICTOC=20=
=0D=0ARon=20-=20if=20TICTOC=20is=20chartered,=20then=20it=20is=20=
possible=20that=20this=20could=20move=20there.=20=0D=0ANot=20proposing=20=
anything=20in=20way=20of=20handling=20the=20timing.=20=0D=0A=0D=0A=
Stewart=20-=20this=20needs=20a=20charter=20change.=20Logically,=20TICTOC=20=
is=20where=20to=20do=20it.=20=0D=0AShould=20this=20WG=20act=20as=20a=20=
caretaker=20until=20a=20decision=20is=20made?=20This=20is=20only=20a=20=
first=20=0D=0Acut=20and=20needs=20to=20design=20work=20before=20we=20can=20=
answer=20this.=20=0D=0A=20=0D=0AYakov=20Stein=20-=20Not=20just=20a=20=
pure=20data=20encap=20issue,=20which=20is=20why=20I=20am=20not=20sure=20=0D=
=0Aexpertise=20is=20here.=20=0D=0A=20=0D=0AMark=20Townsley=20-=20agrees=20=
that=20this=20does=20seem=20significant=20enough=20to=20PWE3=20to=20=
require=20=0D=0Asomething=20to=20be=20done.=20But=20let's=20focus=20=
efforts=20on=20TICTOC=20so=20this=20work=20does=20not=20=0D=0Aforce=20=
itself=20in=20PWE3.=20=0D=0A=20=0D=0AStewart=20-=20should=20take=20this=20=
off=20line.=20=0D=0A=20=0D=0A=0D=0AT-MPLS=20-=20Italso=20Busi=20=
(italo.busi@alcatel-lucent.it)=20=0D=0A=
---------------------------------------------------=20=0D=0A=20=0D=0A=
Shows=20a=20slide=20summarizing=20ITU=20view=20of=20T-MPLS=20=0D=0A=20=0D=
=0AForwarding=20component=20using=20RFC3031/3032=20etc=20=0D=0A-=20PHP=20=
switched=20off,=20no=20merging,=20no=20ECMP=20=0D=0ALabel=20space=20is=20=
per-platform/interface=20assignment=20with=20downstream,=20and=20context=20=
=0D=0Aspecific=20with=20upstream=20label=20assignment=20for=20P2MP=20=0D=0A=
=20=0D=0AT-MPLS=20not=20only=20Ethernet=20PW=20over=20a=20MPLS=20PSN=20=0D=
=0A-=20add=20support=20for=20ATM=20etc=20using=20PWE3=20RFCs=20and=20=
data=20plane=20=0D=0A=20=0D=0AShows=20interoperability=20with=20IP/MPLS.=20=
=0D=0A=20=0D=0ADifferences=20are=20with=20OAM=20(no=20IP=20forwarding)=20=
=0D=0A-=20T-MPLS=20OAM=20identified=20using=20label=2014=20assigned=20by=20=
IETF=20to=20ITU-T=20=0D=0Aprotection=20is=20data=20plane=20driven=20=
only,=20based=20on=20T-MPLS=20OAM=20=0D=0AControl=20plane=20=0D=0A-=20=
option=20to=20work=20without=20control=20plane.=20This=20is=20the=20=
current=20standard.=20=0D=0A-=20Work=20starting=20on=20T-MPLS=20CP=20=
based=20on=20GMPLS=20=0D=0AGood=20opportunity=20to=20work=20together=20=
on=20this.=20=0D=0A=20=0D=0AMonique=20Morrow=20-=20Concern=20is=20reuse=20=
of=20an=20ethertype=20already=20assigned=20to=20IETF.=20=0D=0AReuse=20of=20=
this=20is=20a=20concern.=20Also,=20what=20is=20an=20MPLS=20level?=20=0D=0A=
Italo=20-=20T-MPLS=20speaks=20at=20IETF=20MPLS=20level=20=0D=0AMonique=20=
Morrow=20-=20Label=2014=20was=20designed=20for=20Y.1711,=20but=20T-MPLS=20=
is=20not=20using=20this.=20=0D=0AItalo=20-=20T-MPLS=20OAM=20is=20an=20=
extension=20of=20this.=20=20=0D=0AMonique=20-=20but=20this=20is=20not=20=
Y.1711=20=0D=0AGeorge=20Swallow=20-=20is=20there=20any=20technical=20=
benefit=20from=20using=20the=20same=20ethertype?=20=0D=0AItalo=20-=20=
same=20data=20encapsulation=20and=20forwarding=20plane=20=0D=0AGeorge=20=
Swallow=20-=20when=20a=20label=20comes=20into=20a=20box,=20it=20has=20a=20=
set=20of=20procedures=20for=20=0D=0Awhat=20to=20do.=20You=20are=20=
changing=20the=20label=20allocation=20and=20semantic=20of=20label=2014.=20=
So=20=0D=0Ayou=20should=20use=20a=20different=20Ethertype.=20=0D=0AYakov=20=
Rekhter=20-=20you=20talk=20about=20interoperability.=20I=20would=20like=20=
to=20understand=20if=20=0D=0Athis=20includes=20OAM=20and=20control=20=
plane.=20=0D=0AItalo=20Busi=20-=20not=20all=20of=20the=20details=20have=20=
been=20worked=20out.=20Control=20plane=20is=20the=20=0D=0Amost=20complex=20=
one.=20=0D=0ARoss=20Callon=20-=20Very=20nervous=20about=20how=20it=20is=20=
going=20to=20work=20when=20it=20uses=20a=20=0D=0Adifferent=20label=20=
management=20scheme.=20=0D=0A=20=0D=0ALoa=20Andersson=20-=20Are=20there=20=
any=20real=20technical=20benefits=20from=20using=20the=20same=20=0D=0A=
ethertype?=20=0D=0AItalo=20-=20this=20is=20an=20MPLS=20packet,=20so=20we=20=
decided=20to=20use=20the=20same=20ethertype=20because=20=0D=0Awe=20are=20=
=20=0D=0ALoa=20Andersson=20-=20so=20you=20cannot=20give=20one.=20=0D=0A=
Italo=20-=20it=20is=20a=20profile=20of=20MPLS.=20=0D=0AAndy=20Malis=20-=20=
so=20I=20don't=20see=20a=20downside=20from=20using=20.=20=0C=0D=0A=0D=0A=0D=
=0ARoss=20Callon=20-=20you=20said=20it=20is=20a=20profile=20of=20MPLS,=20=
but=20it=20uses=20different=20label=20=0D=0Aallocation,=20OAM=20...=20=
etc=20=0D=0ASewart=20-=20Can=20I=20assert=20that=20if=20the=20group=20=
owning=20the=20protocol=20does=20not=20agree,=20then=20=0D=0Ait=20is=20=
not=20a=20profile.=20=0D=0ABen=20Niven-Jenkins=20-=20It=20is=20a=20=
profile=20at=20the=20data=20plane,=20but=20operating=20a=20network=20=0D=0A=
is=20much=20more=20than=20that.=20Interworking=20this=20will=20be=20a=20=
complete=20nightmare.=20=0D=0ANurit=20-=20you=20can=20use=20different=20=
OAM=20mechanisms=20for=20the=20same=20ethertype,=20so=20this=20=0D=0A=
argument=20is=20not=20valid.=20=0D=0AMark=20Townsley=20-=20agrees=20with=20=
the=20gentleman=20from=20BT=20that=20this=20is=20a=20nightmare.=20Your=20=
=0D=0Astory=20is=20not=20consistent=20with=20what=20you=20are=20saying=20=
at=20ITU=20about=20interworking.=20=0D=0A=20=0D=0A=20=0D=0A=20=0D=0A=
T-MPLS=20Report=20-=20Stewart=20Bryant=20(stbryant@cisco.com)=20=0D=0A=
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-mpls-transport-00.txt=20=
=0D=0Ahttps://datatracker.ietf.org/liaison/345/=20=0D=0A=
https://datatracker.ietf.org/liaison/344/=20=0D=0A=
-----------------------------------------=20=0D=0A=20=0D=0APresents=20=
the=20key=20changes=20to=20the=20draft=20and=20responses=20form=20ITU-T.=20=
=20=0D=0ANoted=20that=20key=20requirements=20can=20be=20addressed=20by=20=
PWE3=20=0D=0A=20=0D=0ALiaison=20back=20=0D=0ANotes=20that=202=20service=20=
providers=20support=20requirements=20=0D=0AGoes=20through=20responses=20=
one=20by=20one.=20=0D=0A=20=0D=0ADoes=20any=20of=20this=20feedback=20=
indicate=20we=20should=20make=20any=20technical=20changes=20to=20PWE3=20=0D=
=0AMPLS=20transport=20draft?=20=0D=0A=20=0D=0ADo=20we=20last=20call=20=
it?=20Do=20we=20want=20to=20so=20more=20work?=20=0D=0A=20=0D=0AMonique=20=
Morrow=20-=20Should=20last=20call=20it=20=0D=0ATom=20Nadeau=20-=20clear=20=
they=20don't=20want=20to=20provide=20constructive=20feedback,=20so=20=
should=20=0D=0Alast=20call=20it.=20=0D=0ABen=20Niven-Jenkins=20-=20last=20=
call=20it.=20=0D=0AYakov=20Rekhter=20-=20last=20call=20it=20=0D=0A=20=0D=0A=
Danny=20-=20Pretty=20clear=20we=20should=20last=20call=20it.=20=0D=0A=20=0C=

--Apple-Mail-2--714070979
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed



--Apple-Mail-2--714070979
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://www1.ietf.org/mailman/listinfo/pwe3

--Apple-Mail-2--714070979--





