From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: UDP - more proposed text
Date: Mon, 01 Nov 2004 22:39:51 +0000
Lines: 34
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-bounces@ietf.org Tue Nov 02 00:16:17 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: pwe3 <pwe3@ietf.org>
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is another attempt at reaching consensus on the
long standing ITU-UDP issue.

Does the following correctly express the views
of the PWE3 WG?

"In response to the request from Q5 the PWE3 WG has
extensively discussed the use of UDP as a multiplexing
mechanism and is unable to form a consensus that this
is required. Two other mechanisms are already available:
PW over MPLS tunneled over IP, and PW over L2TPv3. That
being the case it is difficult to see why we need to
support a third mechanism. We would suggest that if
anyone believes there is a need for a new PWoverUDP
solution in the future, then they should produce
such a proposal in an Internet Draft and submit
it for consideration here in IETF.

"The PWE3 WG would like to point out that the use of
any signaling (implicit or explicit) has security
implications that would need to be addressed in any
proposal. The WG would also like to point out that
within the IETF there are misgivings about the use
of UDP in these applications from a congestion
perspective. Full regard must therefore be given to
the likely deployment scenarios and the design of
appropriate congestion management mechanisms."

"The WG will continue to listen to proposals and monitor
consensus regarding the use of UDP. However, without
consensus we are unable to provide further detailed
guidance on the matter."

- Stewart


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
Date: Mon, 01 Nov 2004 23:30:14 +0000
Lines: 8
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-bounces@ietf.org Tue Nov 02 01:04:02 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: pwe3 <pwe3@ietf.org>
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is the start of a two week last call for

IANA Allocations for pseudo Wire Edge to Edge Emulation (PWE3)
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-iana-allocation-07.txt

Last call will end Tuesday 16th October 2004

- Stewart


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: draft-ietf-pwe3-cw-00.txt - LAST CALL
Date: Tue, 02 Nov 2004 01:04:26 +0000
Lines: 7
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-bounces@ietf.org Tue Nov 02 02:26:57 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: pwe3 <pwe3@ietf.org>
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is the start of two week last call on

http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw-00.txt

Last call will finish on 16th November 2004

Stewart


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Andrew G. Malis" <andymalis@comcast.net>
Subject: Re: draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
Date: Mon, 01 Nov 2004 20:23:41 -0500
Lines: 34
References: <4186C706.7080901@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: pwe3 <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Tue Nov 02 02:51:26 2004
Return-path: <pwe3-bounces@ietf.org>
X-Sender: andymalis@comcast.net@mail.comcast.net
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
To: Stewart Bryant <stbryant@cisco.com>
In-Reply-To: <4186C706.7080901@cisco.com>
References: <4186C706.7080901@cisco.com>
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Stewart,

It seems odd to take this to last call prior to the control signaling 
draft.  They should probably go through last call simultaneously.

That said, I have a few comments:

1. For PW type:

0x0001  Frame Relay DLCI ( Martini Mode )

Add the following note:

Note: This PW type is grandfathered for a historical protocol.  The 
recommended standards-track protocol to use is 0x0019,  Frame Relay DLCI.

2. Just a stylistic thing - Luca seems to like spaces between the 
parentheses and the parenthetical expression.  I don't.

3. There's an extraneous quote in the header for section 4.

Thanks,
Andy


At 11/1/2004 11:30 PM +0000, Stewart Bryant wrote:
>This is the start of a two week last call for
>
>IANA Allocations for pseudo Wire Edge to Edge Emulation (PWE3)
>http://www.ietf.org/internet-drafts/draft-ietf-pwe3-iana-allocation-07.txt
>
>Last call will end Tuesday 16th October 2004
>
>- Stewart


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
Date: Tue, 02 Nov 2004 01:58:33 +0000
Lines: 67
References: <4186C706.7080901@cisco.com>
	<6.1.2.0.2.20041101200914.05af9260@mail.comcast.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pwe3 <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Tue Nov 02 03:23:32 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
In-Reply-To: <6.1.2.0.2.20041101200914.05af9260@mail.comcast.net>
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org



Andrew G. Malis wrote:

> Stewart,
> 
> It seems odd to take this to last call prior to the control signaling 
> draft.  They should probably go through last call simultaneously.
> 

The worst that will happen is that we have add an IANA request
to the CS draft.

Meanwhile all the registries will have been set up and the codepoints
can be used.

> That said, I have a few comments:
> 
> 1. For PW type:
> 
> 0x0001  Frame Relay DLCI ( Martini Mode )
> 
> Add the following note:
> 
> Note: This PW type is grandfathered for a historical protocol.  The 
> recommended standards-track protocol to use is 0x0019,  Frame Relay DLCI.
> 
> 2. Just a stylistic thing - Luca seems to like spaces between the 
> parentheses and the parenthetical expression.  I don't.

Hopefully that is something that the RFC editor will take a view on.

> 
> 3. There's an extraneous quote in the header for section 4.
> 
> Thanks,
> Andy
> 

Need to add registry for "PW Associated Channel Type" to support
draft-ietf-pwe3-cw-00.txt

Took a while to find out what note 1
    (Note 1: This PW type is .....)
actually refered to

- Stewart




> 
> At 11/1/2004 11:30 PM +0000, Stewart Bryant wrote:
> 
>> This is the start of a two week last call for
>>
>> IANA Allocations for pseudo Wire Edge to Edge Emulation (PWE3)
>> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-iana-allocation-07.txt 
>>
>>
>> Last call will end Tuesday 16th October 2004
>>
>> - Stewart
> 
> 
> 
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Adrian Farrel" <adrian@olddog.co.uk>
Subject: Re: draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
Date: Tue, 2 Nov 2004 11:51:03 -0000
Lines: 43
References: <4186C706.7080901@cisco.com>
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-From: pwe3-bounces@ietf.org Tue Nov 02 13:01:05 2004
Return-path: <pwe3-bounces@ietf.org>
To: "pwe3" <pwe3@ietf.org>
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Hi,

You seem to have a couple of unresolved citations.

I'm not sure that it is useful to use the same notation (square braces) for notes and
citations.

The 2119 boilerplate paragraph does not seem to have been applied. I guess you should
either use it or delete it.

You have a citation in the Abstract (which is not allowed).

It might be 'usual' to include pointers to how the defined code spaces are used. Such as a
pointer to a protocol field in another RFC.

Cheers,
Adrian

----- Original Message ----- 
From: "Stewart Bryant" <stbryant@cisco.com>
To: "pwe3" <pwe3@ietf.org>
Sent: Monday, November 01, 2004 11:30 PM
Subject: [PWE3] draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL


> This is the start of a two week last call for
>
> IANA Allocations for pseudo Wire Edge to Edge Emulation (PWE3)
> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-iana-allocation-07.txt
>
> Last call will end Tuesday 16th October 2004
>
> - Stewart
>
>
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
>
>


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: neil.2.harrison@bt.com
Subject: RE: UDP - more proposed text
Date: Tue, 2 Nov 2004 17:50:40 -0000
Lines: 52
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-bounces@ietf.org Tue Nov 02 19:21:56 2004
Return-path: <pwe3-bounces@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
content-class: urn:content-classes:message
Thread-Topic: [PWE3] UDP - more proposed text
Thread-Index: AcTAaQMsouElxSR3SHquXbQgKmrYZAAm5y3w
To: <stbryant@cisco.com>, <pwe3@ietf.org>
X-OriginalArrivalTime: 02 Nov 2004 17:50:41.0098 (UTC)
	FILETIME=[780722A0:01C4C104]
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: quoted-printable
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Hi Stewart....your proposed response/text looks fine to me.

regards, Neil

> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On=20
> Behalf Of Stewart Bryant
> Sent: 01 November 2004 22:40
> To: pwe3
> Subject: [PWE3] UDP - more proposed text
>=20
>=20
> This is another attempt at reaching consensus on the
> long standing ITU-UDP issue.
>=20
> Does the following correctly express the views
> of the PWE3 WG?
>=20
> "In response to the request from Q5 the PWE3 WG has
> extensively discussed the use of UDP as a multiplexing=20
> mechanism and is unable to form a consensus that this is=20
> required. Two other mechanisms are already available: PW over=20
> MPLS tunneled over IP, and PW over L2TPv3. That being the=20
> case it is difficult to see why we need to support a third=20
> mechanism. We would suggest that if anyone believes there is=20
> a need for a new PWoverUDP solution in the future, then they=20
> should produce such a proposal in an Internet Draft and=20
> submit it for consideration here in IETF.
>=20
> "The PWE3 WG would like to point out that the use of
> any signaling (implicit or explicit) has security
> implications that would need to be addressed in any
> proposal. The WG would also like to point out that
> within the IETF there are misgivings about the use
> of UDP in these applications from a congestion
> perspective. Full regard must therefore be given to
> the likely deployment scenarios and the design of
> appropriate congestion management mechanisms."
>=20
> "The WG will continue to listen to proposals and monitor=20
> consensus regarding the use of UDP. However, without=20
> consensus we are unable to provide further detailed guidance=20
> on the matter."
>=20
> - Stewart
>=20
>=20
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
>=20


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Busschbach, Peter B (Peter)" <busschbach@lucent.com>
Subject: RE: draft-ietf-pwe3-cw-00.txt - LAST CALL
Date: Tue, 2 Nov 2004 13:29:59 -0500
Lines: 35
Mime-Version: 1.0
Content-Type: text/plain
X-From: pwe3-bounces@ietf.org Tue Nov 02 20:02:38 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Stewart Bryant'" <stbryant@cisco.com>, pwe3 <pwe3@ietf.org>
X-Mailer: Internet Mail Service (5.5.2657.72)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Stewart,

It seems premature to start the last call. The draft refers to a PW Associated Channel Type that is not defined yet.

Other nits:

- Paragraph 4 of section contains the text "Section Error! Reference source not found."

- Section 5 mentions "PW Associated Channel Type values 1 through 65535 are vendor-specific".  I think this should be 257 through 65535 

- Section 5 mentions "A PW Associated Channel Type of up to 65  characters is required for any assignment from this registry". How does this relate to the earlier statement that the PW Associated Channel Type is a 16-bit value?

Peter

> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]
> Sent: Monday, November 01, 2004 8:04 PM
> To: pwe3
> Subject: [PWE3] draft-ietf-pwe3-cw-00.txt - LAST CALL
> 
> 
> This is the start of two week last call on
> 
> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw-00.txt
> 
> Last call will finish on 16th November 2004
> 
> Stewart
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: draft-ietf-pwe3-cw-00.txt - LAST CALL
Date: Tue, 02 Nov 2004 21:01:47 +0000
Lines: 81
References: <B99995113B318D44BBE87DC50092EDA90C0D6136@nj7460exch006u.ho.lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pwe3 <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Tue Nov 02 22:53:16 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: "Busschbach, Peter B (Peter)" <busschbach@lucent.com>
In-Reply-To: <B99995113B318D44BBE87DC50092EDA90C0D6136@nj7460exch006u.ho.lucent.com>
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org



Busschbach, Peter B (Peter) wrote:

> Stewart,
> 
> It seems premature to start the last call. 

We do need to move this forward quickly, because it replaces text
that was removed from the arch draft that many other drafts
were referencing. i.e. it's a gate for a lot of otherwise complete
drafts that we need to get to the IESG.

> The draft refers to a PW Associated Channel Type that is not defined yet.

The only current PWE3 use for AC is VCCV, but you are right, we need
to define it.

> 
> Other nits:
> 
> - Paragraph 4 of section contains the text "Section Error! Reference source not found."

That was a word error that crept past me in the -00 deadline.

> 
> - Section 5 mentions "PW Associated Channel Type values 1 through 65535 are 
> vendor-specific".  I think this should be 257 through 65535 
> 

Yes, and there is an earlier error so it should be

.... PW Associated Channel Type values 128
through 255 are to be assigned by IANA, using the "First Come First
Served" policy defined in RFC2434. PW Associated Channel Type values 
256 through 65535 are vendor-specific,

Are folks happy with the two block of 128, or should they be bigger?


> - Section 5 mentions "A PW Associated Channel Type of up to 65  characters is 
> required for any assignment from this registry". How does this relate to the 
> earlier statement that the PW Associated Channel Type is a 16-bit value?
> 

This means that when you request a value from IANA you must provide 
them with a 65 char text description to go in their registry. It's
not an on-the-wire value.

> Peter
> 
> 
>>-----Original Message-----
>>From: Stewart Bryant [mailto:stbryant@cisco.com]
>>Sent: Monday, November 01, 2004 8:04 PM
>>To: pwe3
>>Subject: [PWE3] draft-ietf-pwe3-cw-00.txt - LAST CALL
>>
>>
>>This is the start of two week last call on
>>
>>http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw-00.txt
>>
>>Last call will finish on 16th November 2004
>>
>>Stewart
>>
>>
>>_______________________________________________
>>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  Wed Dec 27 15:58:27 2006
From: "David Allan" <dallan@nortelnetworks.com>
Subject: FW: draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
Date: Thu, 4 Nov 2004 16:50:59 -0500
Lines: 29
X-From: pwe3-bounces@ietf.org Thu Nov 04 23:13:33 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'pwe3@ietf.org'" <pwe3@ietf.org>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


Hi:

A number of us have been working on fault notification for PWs, and have
concluded that we do not need to couple fault direction and fault location
the way it is currently defined for the LDP status TLV in the IANA
allocations draft. There is another proposal but it has not had enough "soak
time" to spring in the middle of a last call. 

Rather than hold up the IANA allocations draft, the suggestion is simply to
remove the status code points we know we will be revising.

So keep
       0x00000000 - Pseudo Wire forwarding ( clear all failures )
       0x00000001 - Pseudo Wire Not Forwarding
 
And lose
       0x00000002 - Local Attachement Circuit ( ingress ) Receive Fault
       0x00000004 - Local Attachement Circuit ( egress ) Transmit Fault
       0x00000008 - Local PSN-facing PW ( ingress ) Receive Fault
       0x00000010 - Local PSN-facing PW ( egress ) Transmit Fault

So the IANA registry entry is set up, and we'll provide the requisite
additional code points when it is pinned down...

Any objections?

cheers
Dave


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Singh, Hardeep (Hardeep)" <hardeep@lucent.com>
Subject: RE: draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
Date: Thu, 4 Nov 2004 17:59:16 -0500
Lines: 53
Mime-Version: 1.0
Content-Type: text/plain
X-From: pwe3-bounces@ietf.org Fri Nov 05 00:23:31 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'David Allan'" <dallan@nortelnetworks.com>, "'pwe3@ietf.org'"
	<pwe3@ietf.org>
X-Mailer: Internet Mail Service (5.5.2657.72)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

I agree. Probably the first two can me made mandatory
and the rest optional to implement or be decided later.

We too came to the same conclusion when we implemented
PWE3 circuits as per the draft.

Thanks

Hardeep

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]On Behalf Of
David Allan
Sent: Thursday, November 04, 2004 4:51 PM
To: 'pwe3@ietf.org'
Subject: FW: [PWE3] draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL



Hi:

A number of us have been working on fault notification for PWs, and have
concluded that we do not need to couple fault direction and fault location
the way it is currently defined for the LDP status TLV in the IANA
allocations draft. There is another proposal but it has not had enough "soak
time" to spring in the middle of a last call. 

Rather than hold up the IANA allocations draft, the suggestion is simply to
remove the status code points we know we will be revising.

So keep
       0x00000000 - Pseudo Wire forwarding ( clear all failures )
       0x00000001 - Pseudo Wire Not Forwarding
 
And lose
       0x00000002 - Local Attachement Circuit ( ingress ) Receive Fault
       0x00000004 - Local Attachement Circuit ( egress ) Transmit Fault
       0x00000008 - Local PSN-facing PW ( ingress ) Receive Fault
       0x00000010 - Local PSN-facing PW ( egress ) Transmit Fault

So the IANA registry entry is set up, and we'll provide the requisite
additional code points when it is pinned down...

Any objections?

cheers
Dave
 

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


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Florin Balus" <balus@nortelnetworks.com>
Subject: draft-balus-pwe3-ip-pseudowire-01.txt
Date: Fri, 5 Nov 2004 11:21:32 -0500
Lines: 806
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C4C353.83DE51EC"
X-From: pwe3-bounces@ietf.org Fri Nov 05 17:32:59 2004
Return-path: <pwe3-bounces@ietf.org>
To: pwe3 <pwe3@ietf.org>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: 8970a17ea8642e1e9e9a967e2088f88d
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C4C353.83DE51EC
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C353.83DE51EC"


------_=_NextPart_001_01C4C353.83DE51EC
Content-Type: text/plain

All,
We would like to get comments on the enclosed text. We have considered
feedback received after the first version of the draft - mainly related to
the problem definition/requirements. We will have to accommodate in the 02
revision the new format proposed in draft-ietf-pwe3-cw-00.txt for PW
Associated Channel. 
See submitted abstract below... 
Title : IP Pseudowire Encapsulation  -
<http://www.ietf.org/internet-drafts/draft-balus-pwe3-ip-pseudowire-01.txt>
http://www.ietf.org/internet-drafts/draft-balus-pwe3-ip-pseudowire-01.txt

This document proposes a PW encapsulation specific to IP packets, the IP
Pseudowire, following 
the architectural principles defined in [PWE3 Architecture]. This proposal
introduces an optional CW 
for IP encapsulation. Note that when the inclusion of a control word is not
negotiated, the IP PW uses 
the encapsulation described in [RFC3032].
This document defines the encapsulation and the motivators for using an
optional CW for IP pseudowire. 
In this model, the AC circuits are terminated at each PE, and only the IP
payload is transported across 
the PSN using a PW header. Two solutions using the IP PW encapsulation are
described in [ARP Mediation] 
and [IPLS]. Multi-hop pseudowire could be also another application for the
concepts described in this draft. 
 
Florin 
Florin Balus 
Nortel Networks 
Tel: 1-613-768-4997  ESN: 398-4997
Fax: 1-613-765-4123 ESN: 395-4123
Email: mailto:balus@nortelnetworks.com 
DNE site: http://navigate.us.nortel.com/dne
<http://navigate.us.nortel.com/dne>  
NPW 2003 http://www.nortelnetworks.com/npw2003
<http://www.nortelnetworks.com/npw2003>  
 

------_=_NextPart_001_01C4C353.83DE51EC
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2800.1458" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
class=3D642351016-05112004>All,</SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D642351016-05112004>We =
would like to=20
get&nbsp;comments on the&nbsp;enclosed text. We have considered =
feedback=20
received after the first version of the draft - mainly related to the =
problem=20
definition/requirements. We will have to accommodate in the&nbsp;02 =
revision=20
the&nbsp;new format proposed in draft-ietf-pwe3-cw-00.txt for PW =
Associated=20
Channel. </SPAN></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D642351016-05112004><FONT=20
size=3D2>See submitted=20
abstract&nbsp;below...&nbsp;</FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT><SPAN class=3D642351016-05112004>
<P><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><FONT =
color=3D#000000>Title :=20
IP Pseudowire Encapsulation</FONT><SPAN =
class=3D642351016-05112004><FONT=20
color=3D#000000>&nbsp; - <A=20
href=3D"http://www.ietf.org/internet-drafts/draft-balus-pwe3-ip-pseudowi=
re-01.txt"><U><FONT=20
color=3D#0000ff=20
size=3D2>http://www.ietf.org/internet-drafts/draft-balus-pwe3-ip-pseudow=
ire-01.txt</U></FONT></A></P></FONT></SPAN></FONT></FONT></FONT></SPAN><=
/FONT></DIV>
<DIV><FONT><FONT><FONT face=3DArial><FONT size=3D2>This document =
proposes a PW=20
encapsulation specific to IP packets,<SPAN class=3D774302712-18102004> =
</SPAN>the=20
IP Pseudowire, following </FONT></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the architectural principles defined =
in=20
</FONT><FONT face=3DArial size=3D2>[PWE3 Architecture]. This proposal =
introduces an=20
optional CW </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>for IP encapsulation. Note that when =
the inclusion=20
of a control word is not </FONT><FONT face=3DArial size=3D2>negotiated, =
the IP PW=20
uses <BR>the encapsulation described in [RFC3032].</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>This document defines the =
encapsulation and the=20
motivators for using an optional CW for IP pseudowire. </FONT></DIV>
<DIV><FONT size=3D2><FONT face=3DArial>In this model, the AC circuits =
are=20
</FONT><FONT face=3DArial>terminated at each PE, and only the IP =
payload is=20
transported across </FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT face=3DArial>the </FONT><FONT =
face=3DArial>PSN using a PW=20
header. Two solutions using the IP PW encapsulation </FONT><FONT =
face=3DArial>are=20
described in [ARP Mediation] </FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2>and [IPLS]. Multi-hop pseudowire =
could be=20
also an<SPAN class=3D774302712-18102004>other</SPAN> application for =
the concepts=20
described in this draft<SPAN class=3D774302712-18102004>.<SPAN=20
class=3D642351016-05112004><FONT=20
color=3D#0000ff>&nbsp;</FONT></SPAN></SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D774302712-18102004><SPAN=20
class=3D642351016-05112004></SPAN></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D774302712-18102004><SPAN=20
class=3D642351016-05112004>Florin&nbsp;<BR></SPAN></SPAN></FONT></FONT><=
SPAN=20
lang=3Den-us><B><FONT size=3D2>Florin Balus</FONT></B></SPAN> <BR><SPAN =

lang=3Den-us><B><FONT size=3D2>Nortel Networks</FONT></B><FONT =
size=3D2>=20
</FONT></SPAN><BR><SPAN lang=3Den-us><B><FONT =
size=3D2>Tel:</FONT></B><FONT size=3D2>=20
1-613-768-4997&nbsp;</FONT><B> <FONT size=3D2>ESN:</FONT></B><FONT =
size=3D2>=20
398-4997<BR></FONT><B><FONT size=3D2>Fax:</FONT></B><FONT size=3D2>=20
1-613-765-4123</FONT><B> <FONT size=3D2>ESN:</FONT></B><FONT size=3D2>=20
395-4123<BR></FONT><B><FONT size=3D2>Email:<U></U></FONT></B><U><FONT=20
size=3D2></FONT></U> <FONT =
size=3D2>mailto:balus@nortelnetworks.com</FONT></SPAN>=20
<BR><SPAN lang=3Den-us><B><FONT size=3D2>DNE site:</FONT></B> <FONT =
face=3DArial=20
size=3D2><A=20
href=3D"http://navigate.us.nortel.com/dne">http://navigate.us.nortel.com=
/dne</A></FONT></SPAN>=20
<BR><SPAN lang=3Den-us><B><FONT face=3DArial size=3D2>NPW =
2003</FONT></B><FONT=20
face=3DArial size=3D2> <A=20
href=3D"http://www.nortelnetworks.com/npw2003">http://www.nortelnetworks=
.com/npw2003</A></FONT></SPAN>=20
</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01C4C353.83DE51EC--

------_=_NextPart_000_01C4C353.83DE51EC
Content-Type: text/plain;
	name="draft-balus-pwe3-ip-pseudowire-01.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="draft-balus-pwe3-ip-pseudowire-01.txt"
Content-Transfer-Encoding: quoted-printable


 PWE3 Working Group
 Internet Draft
 Expires: April 2005


 Himanshu Shah                                   Florin Balus
 Ciena Networks                                  Mike Loomis
								 Jeff Sugimoto                                               =20
								 Nortel Networks
 Mustapha Aissaoui							=20
 Alcatel    						 Mircea Pisica
 								 Infonet



                                                 October 2004


                       IP Pseudowire Encapsulation

                  draft-balus-pwe3-ip-pseudowire-01.txt

 Status of this Memo

    This document is an Internet-Draft and is in full conformance with
    all provisions of Section 10 of RFC2026.

    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups.  Note that
    other groups may also distribute working documents as Internet-
    Drafts.

    Internet-Drafts are draft documents valid for a maximum of six
    months and may be updated, replaced, or obsoleted by other =
documents
    at any time.  It is inappropriate to use Internet-Drafts as
    reference material or to cite them other than as "work in =
progress."

    The list of current Internet-Drafts can be accessed at
         http://www.ietf.org/ietf/1id-abstracts.txt
    The list of Internet-Draft Shadow Directories can be accessed at
         http://www.ietf.org/shadow.html.

 Copyright Notice
    Copyright(C) The Internet Society (2001). All Rights Reserved.

 Abstract

    This document proposes a PW encapsulation specific to IP packets,
    the IP Pseudowire, following the architectural principles defined =
in=20
    [PWE3 Architecture]. This proposal introduces an optional CW for IP =

    encapsulation. Note that when the inclusion of a control word is =
not=20
    negotiated, the IP PW uses the encapsulation described in =
[RFC3032].


 Balus et.al            Expires Jan 2005                     Page 1 =0C
 draft-balus-pwe3-ip-pseudowire-01.txt             Expires January 2005

 Table of Contents

 1.    Conventions used in this document.............................2
 2.    Introduction and Requirements.................................2
 3.    Reference Model...............................................3
 4.    IP PW Encapsulation...........................................4
 5.    Support for PW OAM............................................5
 6.    Support for non-IP payload....................................6
 7.    Signaling of the IP PW........................................7
 8.    Security Considerations.......................................7
 9.	 Changes from the previous version.............................7
 10.   Acknowledgements..............................................7
 11.   Intellectual Property Rights Notices..........................7
 12.   References....................................................7
 13.   Authors' Addresses............................................8

 1. Conventions used in this document
    The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
    this document are to be interpreted as described in RFC 2119

 2. Introduction and Requirements

    This document defines the encapsulation and the motivators for =
using an=20
    optional CW for IP pseudowire. In this model, the AC circuits are=20
    terminated at each PE, and only the IP payload is transported =
across the=20
    PSN using a PW header. Two solutions using the IP PW encapsulation=20
    are described in [ARP Mediation] and [IPLS]. Multi-hop pseudowire =
could be =20
    also another application for the concepts described in this draft.
   =20
    The requirements for an IP PW vary depending on the behavior =
expected=20
    from end user application, and sometimes by how much the layer 2 =
media=20
    characteristics were used to achieve said behaviour. For instance,=20
    deterministic path forwarding, connection tracing, discard =
priorities=20
    and congestion notifications are typical L2 attributes, which often =

    benefit a native, end-to-end service encapsulated within it. In the =

    context of an IP PW, these characteristics may need to be reflected =
to=20
    preserve current SLAs.

    Specifically concerning deterministic path forwarding in IP/MPLS =
networks,=20
    when no CW is used, the IP PW uses the encapsulation described in=20
    [RFC3032], virtually indistiguishable from the IP over MPLS =
encapsulation,=20
    mapped based on the IP FEC. Current ECMP algorithms used by the =
MPLS LSRs=20
    may perform deep packet inspection and loadshare the IP over MPLS =
packets=20
    based on the IP addresses from the customer IP header. As a result, =
when=20
    the CW is not present, the packets on an IP PW may be loadspread =
across=20
    multiple backbone paths compromising the deterministic path =
forwarding.=20
    In this scenario potential OAM packets (see [VCCV]) may be =
forwarded=20
    consistently on a different path than most of the IP PW packets. =
This=20
    could cause challenges for troubleshooting and operational changes =
to the
    network administrator looking to migrate their L2VPN networks to an =
IP PW=20

 Balus et.al                                                     Page =
2=0C
 draft-balus-pwe3-ip-pseudowire-01.txt             Expires January 2005

    transport. Network operators that relied on L2 mechanisms to =
provide this=20
    functionality may expect to preserve this behavior in IP PWs. =
Similarly,=20
    some end user applications rely on native L2 congestion =
notifications or=20
    discard priority markings for QoS treatment or even SLA reporting.=20
   =20
    Clearly, not all end user applications using an IP PW will have an=20
    identical set of requirements. Typically an internet access service =
has=20
    less requirements from its layer 2 transport media, when compared =
to a=20
    SLA-based, L2VPN service. An IP PW must be flexible enough to =
satisfy the=20
    loose requirements of the basic application, but offer the optional =
tools=20
    to address the strict requirements of the more demanding one.These=20
    requirements typically include:
     =B7  Enable the use of PW in-band OAM with or without ECMP
     =B7  Distinguish an IP PW frame from a regular IP/MPLS frame for=20
	   consistent forwarding of user frames in a PSN using ECMP
     =B7  The option to reflect important layer 2 service =
characteristics=20
=09
    This document proposes an IP PW encapsulation that includes an =
optional=20
    IP control word. The new encapsulation enables the use of PW OAM =
tools=20
    already defined in [VCCV] while offering the mechanisms for =
preserving the
    characteristics of the end-to-end L2 service. This provides an =
efficient=20
    transport of IP PDUs between ACs in environment where ECMP is =
deployed but=20
    the lack of determinism of ECMP, and diagnostic complexity is not =
desired=20
    for this specific service. The document describes also how the =
proposed=20
    solution addresses the case of an MPLS backbone running ECMP so =
that the=20
    data and OAM packets follow the same path throughout the backbone.

 3. Reference Model

    The following diagram represents the reference model used to
    describe the services emulated by the IP PW, based on the concepts
    outlined in [PWE3 Architecture].
             |<------------- Emulated L2 Service -------------->|
             |                                                  |
             |          |<----- IP Pseudo Wire ----->|          |
             |          |                            |          |
             |          |    |<-- PSN Tunnel -->|    |          |
             |          V    V                  V    V          |
             V(IP/)X AC +----+                  +----+(IP/)Y AC V
       +-----+    |     | =
PE1|=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D| PE2|     |  =
  +-----+
       |     |----------|..........IP PW1............|----------|     |
       | CE1 |    |     |    |                  |    |     |    | CE2 |
       |     |----------|..........IP PW2............|----------|     |
       +-----+  ^ |     |    =
|=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D|    |     | ^  =
+-----+
             ^  |       +----+                  +----+     | |  ^
             |  |   Provider Edge 1         Provider Edge 2  |  |
       Customer |                                            | Customer
       Edge 1   |                                            | Edge 2
                |                                            |=20
         native X service                             native Y service
                    Figure 1: PWE3 IP PW Network Reference Model

 Balus et.al                                                     Page 3 =
=0C
 draft-balus-pwe3-ip-pseudowire-01.txt             Expires January 2005

    In figure 1, X and Y represent two Attachment Circuits, both=20
    upporting an IP payload. An IP PW is used to provide PSN transport=20
    between the two ACs. It is important to note as a general rules =
that=20
    for the direction CE1 to CE2 the ingress PE, PE1, should map all =
the=20
    IP/X frames to IP/PW encapsulation described in section 4. The rest =

    of the frame types MUST be discarded with the exceptions noted in=20
    section 7. Same is valid in the reverse direction (CE2->CE1) on =
PE2.

 4. IP PW Encapsulation

    This document introduces an OPTIONAL Control Word (CW) in front of
    the customer IP payload. This will address the requirements
    described in section 2, ensuring that the IP PW data packets follow =

    the same path with the PW OAM ones. Also the presence of this CW=20
    allows for additional flexibility in maintaining the Layer 2 =
service=20
    characteristics.

    The IP PW Control Word follows the guidelines and the bit format
    described in [Martini L2CIRC] section 3.1 - see figure 3 below:
   =20
        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       | Rsvd  |B|F|D|0|FRG|   Length  |           Sequence            =
|
       =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                      Customer IP PDU                          =
|
       |                             "                                 =
|
       |                             "                                 =
|
       |                             "                                 =
|
       =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                        Figure 3: IP PW Control Word

    - The first 4 bits are reserved for further use. They MUST be set =
to
	(0000) upon transmitting. They ensure the IP PW data packets are=20
	differentiated from normal IP packets in the MPLS ECMP case. Or in =
other=20
	words they will follow the same path with the PW OAM ones.

    - The next 4 bits (4 to 7) MAY be used to provide flexible support =
for=20
	transport-specific treatments for any given AC type:

	 . Bit 4 (B) used to signal Backward Congestion Indication (BCI)
	   This bit could be used to alleviate possible congestion situation=20
	   related to differences in speed between ACs located at the two =
sides=20
	   of an IP PW: e.g. Ethernet/ATM AC X --> FR AC Y. 	     =20

	 . Bit 5 (F) used to signal Forward Congestion Indication (FCI) =09
	 . Bit 6 (D) used to indicate the Discard Priority (DP)

	If the transmitting PE does not support the processing of the above=20
      flags, it MUST set them to 0. If the receiving PE does not =
support the=20


 Balus et.al                                                    Page 4 =
=0C
 draft-balus-pwe3-ip-pseudowire-01.txt             Expires January 2005

      processing of the flags it MAY ignore them upon reception.
	 . Bit 7 is reserved and must be set to 0.

    - FRG field (bits 8,9) MAY be used to provide support for PW =
Fragmentation=20
	to address MTU mismatch. The usage of these bits is compliant with the =

	procedure described in [FRAG]. Note that the usage of PW fragmentation =

      could be negotiated using the parameter id described in section 4 =
of=20
      [FRAG]. Alternatively, fragmentation at IP Layer could be used - =
see=20
      section 3 of [FRAG]. In the latter case the packet is fragmented =
at the=20
      ingress PE and reassembled just at the IP Destination device - =
i.e. the=20
      egress PE does not get involved. As such this option could be =
enabled by
      provisioning just at the ingress PE.

    - Length field (bits 10 to 15) MAY be used (see [Martini L2CIRC] =
section=20
      3.1) in conjunction with the padding of short IP PW payloads =
(i.e. 40=20
      Bytes) when the link layer protocol on the related PSN links =
requires a=20
      minimum frame length: i.e. minimum payload for Ethernet is 64 =
bytes. If=20
      the total length of the IP payload plus the CW (4 bytes) plus the =
2=20
      labels (8 bytes) is less than 64 bytes then the Length field =
indicates=20
      the total length of the L2 payload (i.e. IP payload+12 bytes). =
Otherwise=20
      the length field must be set to zero. The egress PE will remove =
the=20
      padding and it will restore the frame to its original size.=20
      Alternatively, the Length field from the IP header could be used =
to=20
      address this issue. In this case the padding will be removed just =
at the=20
      IP destination.=20

    - The next 16 bits provide a sequence number that can be used to =
guarantee
	ordered packet delivery. The processing of the sequence number field =
is=20
	OPTIONAL and a value of 0 is used to indicate an unsequenced packet.=20
      This Sequence number SHOULD be compliant with the rules defined =
in=20
      [Martini L2CIRC] see section 3.1.1 and 3.1.2.=20

 5. Support for PW OAM

    [VCCV] defines a set of OAM tools (i.e. Ping, BFD) to be used for=20
    any type of PW encapsulation. One of the methods proposed to =
identify=20
    the associated OAM flows (see Section 4.1 of [VCCV]) suggests the =
use=20
    of the following format:

     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |0 0 0 1| reserved =3D 0  |  PA=3D0 |      PPP DLL Proto Number     =
|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                     Figure 2: VCCV OAM Encapsulation

    The first nibble (0001) together with PPP DLL Protocol Number field =
is=20
    used to identify the OAM flows. This will enable, for the IP PW, =
the=20
    unrestricted use of OAM mechanisms common to other PW types.


 Balus et.al                                                     Page 5 =
=0C
 draft-balus-pwe3-ip-pseudowire-01.txt             Expires January 2005

 6. Support for non-IP payload
   =20
    As a general rule PE1 and PE2 will discard the incoming non-IP =
payloads=20
    on ACs X and Y. Still there could be exceptions from the above =
rule: e.g.=20
    if CE1 and CE2 are using IS-IS for routing protocol, the IP PW =
might be=20
    required to transport this non-IP payload between PE1 and PE2.=20

    To achieve the above goal, it is proposed to extend the PWE3 =
Payload Type=20
    Identifier defined in [PWE3-CW] as follows:  =20
   =20
     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |0 0 0 1| reserved =3D 0  |  PA=3DX |          Payload Type         =
|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      Figure 2: IP PW Encapsulation used non-IP payload exceptions

    The value PA=3D0 is reserved for PW OAM messages (VCCV PING, BFD). =
Values=20
    other than zero are used to identify user packets which are not IP =
packet.=20
    For example,  PA=3D1 (ISO protocol) and the corresponding ISO NLPID =
code=20
    points could be used to provide support for transporting IS-IS =
frames over=20
    an IP PW:
      0                   1                   2                   3=20
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1=20
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
     |0 0 0 1|      rsvd.    | PA=3D1  |ISO NLPID=3D0x83 |0 0 0 0 0 0 0 =
0|=20
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20

 7. Signaling of the IP PW

    A 15 bit quantity containing a value is used as part of the PWiD =
and=20
    Generalized Id FECs to identify the type of PWs - see [PWE3-CTRL] =
sections=20
    5.1 and 5.2. To signal the IP PW we propose the usage of the value =
0x000b=20
    already assigned in [IANA PWE3]section 2 for IP Layer2 Transport.

    The negotiation of the control word complies with the procedure =
described=20
    in [PWE3-CTRL] section 5.4.2.

    No new TLVs, Interface parameters are required for now.

 8. Security Considerations
    To be completed later.

 9. Changes from the previous version
   =20
    - Improved the Abstract and Introduction to clarify the goal of the =
draft
    - Switched section "Support for PW OAM" (now 5, previously 4) with =
"IP PW=20
      Encapsulation" (now 4, previously 5).
    - Comments in section 4: on the usage of BE(fragmentation) and =
Lenght bits=20
    - Changed the format in section 6 to allign to the newly proposed =
PTI=20

 Balus et.al                                                     Page 6 =
=0C
 draft-balus-pwe3-ip-pseudowire-01.txt             Expires January 2005

 10. Acknowledgements

    The authors would like to thank David Allan, Hamid Ould-Brahim, for =

    their helpful discussions and feedbacks.

 11. Intellectual Property Rights Notices.

    This document is being submitted for use in IETF standards =
discussions.

 12. References

    [PWE3 Architecture] "PWE3 Architecture", draft-ietf-pwe3-arch-
    07.txt, IETF work in progress, March 2004

    [ARP Mediation] Shah, Himanshu "ARP Mediation for IP Interworking =
of
    Layer 2 VPN", draft-shah-l2vpn-arp-mediation-03.txt, IETF work in
    progress, October 2003

    [IPLS] Shah,Himanshu "IP-Only LAN Service", =
draft-ietf-l2vpn-ipls-01.txt,
    IETF work in progress, May 2004

    [RFC3032] "MPLS Label Stack Encoding" IETF RFC 3032

    [2547] Rosen, E. Rekhter, Y., "BGP/MPLS VPNs", IETF RFC 2547,
      March 1999

    [VCCV] Nadeau et.al., "Pseudo Wire (PW) Virtual Circuit Connection
    Verification (VCCV)", draft-ietf-pwe3-vccv-02.txt, February 2004
    [RFC2427] RFC 2427, "Multiprotocol Interconnect over Frame Relay"

    [RFC2684] RFC 2684, "Multiprotocol Encapsulation over ATM =
Adaptation
    Layer 5"

    [Martini L2CIRC] Martini et.al. "Encapsulation Methods for =
Transport
    of Layer 2 Frames Over IP and MPLS Networks", draft-martini-
    l2circuit-encap-mpls-07.txt, IETF Work in Progress, June 2004

    [Martini L2TRANS] Martini et.al. "Transport of Layer 2 Frames Over
	MPLS", draft-martini-l2circuit-trans-mpls-14.txt, IETF Work in
	Progress, June 2004

    [FR PW] Kawa et.al. "Frame Relay over Pseudo-Wires", draft-ietf-
	pwe3-frame-relay-02.txt, IETF Work in Progress, February 2004

    [ATM PW] Martini et.al. "Encapsulation Methods for Transport of ATM
	Over IP and MPLS Networks", draft-ietf-pwe3-atm-encap-05.txt, IETF
	Work in Progress, April 2004

    [PWE3-CTRL] Martini et.al. "Pseudowire Setup and Maintenance using
      LDP", draft-ietf-pwe3-control-protocol-07.txt, IETF Work in
      Progress, June 2004

 Balus et.al                                                     Page =
7=0C
 draft-balus-pwe3-ip-pseudowire-01.txt             Expires January 2005

    [IANA PWE3] Martini, Townsley "IANA Allocations for pseudo Wire =
Edge
      to Edge Emulation (PWE3)", draft-ietf-pwe3-iana-allocation-04.txt =

	(work in progress), April 2004
  =20
    [IANA PPP] IANA Point-to-Point Protocol Field Assignments, June =
28,2004=20
	http://www.iana.org/assignments/ppp-numbers

    [RCF3032] RFC 3032 Rosen, et al., "MPLS Label Stack Encoding", =
January=20
      2001
   =20
    [PWE3-CW] Bryant-McPherson, "PWE3 Control Word"=20
	draft-bryant-mcpherson-pwe3-cw-00.txt, July 2004

 12. Authors' Addresses

    Florin Balus
    Nortel Networks
    3500 Carling Ave.
    Ottawa, Ontario, CANADA
    e-mail: balus@nortelnetworks.com

    Jeff Sugimoto
    Nortel Networks
    3500 Carling Ave.
    Ottawa, Ontario, CANADA
    e-mail: sugimoto@nortelnetworks.com

    Mike Loomis
    Nortel Networks
    Billerica, MA

    Himanshu Shah=20
    35 Nagog Park,=20
    Acton, MA 01720=20
    Email: hshah@ciena.com=20

    Mircea Pisica
    Infonet Services Corporation
    Brussells, Belgium

    Mustapha Aissaoui
    Alcatel
    600 March Rd
    Kanata, ON, Canada. K2K 2E6
    Email: mustapha.aissaoui@alcatel.com=20

    Full copyright statement

    Copyright (C) The Internet Society (2002).
    All Rights Reserved.


 Balus et.al                                                     Page 8 =
=0C
 draft-balus-pwe3-ip-pseudowire-01.txt             Expires January 2005

    This document and translations of it may be copied and
    furnished to others, and derivative works that comment
    on or otherwise explain it or assist in its implementation
    may be prepared, copied, published and distributed, in
    whole or in part, without restriction of any kind,
    provided that the above copyright notice and this
    paragraph are included on all such copies and derivative works.
    However, this document itself may not be modified in any way,
    such as by removing the copyright notice or references to the
    Internet Society or other Internet organizations, except as
    needed for the purpose of developing Internet standards in
    which case the procedures for copyrights defined in the
    Internet Standards process must be followed, or as required to
    translate it into languages other than English.

    The limited permissions granted above are perpetual and will
    not be revoked by the Internet Society or its successors or =
assigns.

    This document and the information contained herein is provided
    on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
    ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR
    IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE
    USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS
    OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
    FOR A PARTICULAR PURPOSE.



























 Balus et.al                                                     Page 9
------_=_NextPart_000_01C4C353.83DE51EC
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_000_01C4C353.83DE51EC--




From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: Re: draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
Date: Fri, 5 Nov 2004 15:52:13 -0500
Lines: 70
References: <4F9DBE266768DC46A1F17E875D3716410856A04F@ma8117exch002u.inse.lucent.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "'pwe3@ietf.org'" <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Fri Nov 05 22:03:39 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
In-Reply-To: <4F9DBE266768DC46A1F17E875D3716410856A04F@ma8117exch002u.inse.lucent.com>
To: "Singh, Hardeep (Hardeep)" <hardeep@lucent.com>
X-Mailer: Apple Mail (2.619)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


	I don't think Dave's proposal is to make the others
optional; it was to remove them completely for now.

	--Tom


> I agree. Probably the first two can me made mandatory
> and the rest optional to implement or be decided later.
>
> We too came to the same conclusion when we implemented
> PWE3 circuits as per the draft.
>
> Thanks
>
> Hardeep
>
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]On Behalf Of
> David Allan
> Sent: Thursday, November 04, 2004 4:51 PM
> To: 'pwe3@ietf.org'
> Subject: FW: [PWE3] draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
>
>
>
> Hi:
>
> A number of us have been working on fault notification for PWs, and 
> have
> concluded that we do not need to couple fault direction and fault 
> location
> the way it is currently defined for the LDP status TLV in the IANA
> allocations draft. There is another proposal but it has not had enough 
> "soak
> time" to spring in the middle of a last call.
>
> Rather than hold up the IANA allocations draft, the suggestion is 
> simply to
> remove the status code points we know we will be revising.
>
> So keep
>        0x00000000 - Pseudo Wire forwarding ( clear all failures )
>        0x00000001 - Pseudo Wire Not Forwarding
>
> And lose
>        0x00000002 - Local Attachement Circuit ( ingress ) Receive Fault
>        0x00000004 - Local Attachement Circuit ( egress ) Transmit Fault
>        0x00000008 - Local PSN-facing PW ( ingress ) Receive Fault
>        0x00000010 - Local PSN-facing PW ( egress ) Transmit Fault
>
> So the IANA registry entry is set up, and we'll provide the requisite
> additional code points when it is pinned down...
>
> Any objections?
>
> cheers
> Dave
>
>
> _______________________________________________
> 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  Wed Dec 27 15:58:27 2006
From: "Florin Balus" <balus@nortelnetworks.com>
Subject: RE: draft-ietf-pwe3-cw-00.txt - LAST CALL
Date: Sun, 7 Nov 2004 17:55:48 -0500
Lines: 162
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1751650586=="
X-From: pwe3-bounces@ietf.org Mon Nov 08 00:06:28 2004
Return-path: <pwe3-bounces@ietf.org>
To: Stewart Bryant <stbryant@cisco.com>, lmartini@cisco.com, pwe3
	<pwe3@ietf.org>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============1751650586==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C51C.ED8CCF7F"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C4C51C.ED8CCF7F
Content-Type: text/plain


Stewart,Luca,

I understand the recommendation in section 2 of draft-ietf-pwe3-cw-00.txt -
"A PW carried over an MPLS PSN that uses the contents of the MPLS payload to
select the ECMP path SHOULD employ the PW Control Word described in Section
3 for data" - is directed to distinguish a PW payload from an "IP payload
carried over an MPLS PSN" - see also section 1 of the same document. 
 
draft-ietf-pwe3-control-protocol-12.txt - Section 4.6 (IP Layer2 Transport)
contains the statement: "The control word MUST NOT be used". It seems to me
that if we follow this recommendation for this specific type of PW, we will
run into the issue described in section 1 of draft-ietf-pwe3-cw-00.txt: i.e.
"The inability to ensure that all packets belonging to a PW follow the same
path also prevents the PW OAM [VCCV] mechanism from correctly monitoring the
PW."

Is it possible to remove the MUST from the above statement (or even better
all the text) from section 4.6 of draft-ietf-pwe3-control-protocol-12.txt?
Otherwise it looks to me like the 2 drafts are contradicting each other.
Regards,

Florin     

> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On
> Behalf Of Stewart Bryant
> Sent: Monday, November 01, 2004 8:04 PM
> To: pwe3
> Subject: [PWE3] draft-ietf-pwe3-cw-00.txt - LAST CALL
> 
> 
> This is the start of two week last call on
> 
> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw-00.txt
> 
> Last call will finish on 16th November 2004
> 
> Stewart
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 
> 

------_=_NextPart_001_01C4C51C.ED8CCF7F
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: [PWE3] draft-ietf-pwe3-cw-00.txt - LAST CALL</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2>Stewart,Luca,</FONT>
</P>

<P><FONT SIZE=3D2>I understand the recommendation in section 2 of =
draft-ietf-pwe3-cw-00.txt - &quot;A PW carried over an MPLS PSN that =
uses the contents of the MPLS payload to select the ECMP path SHOULD =
employ the PW Control Word described in Section 3 for data&quot; - is =
directed to distinguish a PW payload from an &quot;IP payload carried =
over an MPLS PSN&quot; - see also section 1 of the same document. =
</FONT></P>

<P><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>draft-ietf-pwe3-control-protocol-12.txt - Section =
4.6 (IP Layer2 Transport) contains the statement: &quot;The control =
word MUST NOT be used&quot;. It seems to me that if we follow this =
recommendation for this specific type of PW, we will run into the issue =
described in section 1 of draft-ietf-pwe3-cw-00.txt: i.e. &quot;The =
inability to ensure that all packets belonging to a PW follow the same =
path also prevents the PW OAM [VCCV] mechanism from correctly =
monitoring the PW.&quot;</FONT></P>

<P><FONT SIZE=3D2>Is it possible to remove the MUST from the above =
statement (or even better all the text) from section 4.6 of =
draft-ietf-pwe3-control-protocol-12.txt? Otherwise it looks to me like =
the 2 drafts are contradicting each other. Regards,</FONT></P>

<P><FONT SIZE=3D2>Florin&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: pwe3-bounces@ietf.org [<A =
HREF=3D"mailto:pwe3-bounces@ietf.org">mailto:pwe3-bounces@ietf.org</A>] =
On</FONT>
<BR><FONT SIZE=3D2>&gt; Behalf Of Stewart Bryant</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Monday, November 01, 2004 8:04 PM</FONT>
<BR><FONT SIZE=3D2>&gt; To: pwe3</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: [PWE3] draft-ietf-pwe3-cw-00.txt - =
LAST CALL</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; This is the start of two week last call =
on</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw-00.txt" =
TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw=
-00.txt</A></FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Last call will finish on 16th November =
2004</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Stewart</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; pwe3 mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; pwe3@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/pwe3" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/pwe3</A></FONT>=

<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C4C51C.ED8CCF7F--


--===============1751650586==
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

--===============1751650586==--




From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Florin Balus" <balus@nortelnetworks.com>
Subject: RE: minor comment I-D ACTION:draft-ietf-pwe3-control-proto
	col-12.txt
Date: Mon, 8 Nov 2004 07:58:50 -0500
Lines: 295
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1066197187=="
X-From: pwe3-bounces@ietf.org Mon Nov 08 14:11:17 2004
Return-path: <pwe3-bounces@ietf.org>
To: lmartini@cisco.com, pwe3@ietf.org
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: f8184d7d4d1b986353eb58ea3e887935
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============1066197187==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C592.B224DC2D"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C4C592.B224DC2D
Content-Type: text/plain


Luca et all,
I noticed there is some old text left in Section 5.2.2 "Encoding the
Generalized ID FEC Element":
 
   "The PW information length field, contains the length of the SAII,
   TAII, AGI combined, and the interface parameters field in octets. If
   this value is 0, then it references all PWs using the specified
   grouping ID. In this case there are no other FEC element fields
   (AGI,SAII, etc. ) present, nor any interface parameters."

Considering that for the Generalized ID FEC TLVs are proposed for Interface
Parameters and PW Grouping, we should take out "the interface parameter
fields" and replace "grouping ID" with "PW Grouping TLV (see section
5.2.2.2)"...

> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On
> Behalf Of Internet-Drafts@ietf.org
> Sent: Monday, October 25, 2004 4:06 PM
> To: i-d-announce@ietf.org
> Cc: pwe3@ietf.org
> Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-control-protocol-12.txt
> 
> 
> A New Internet-Draft is available from the on-line
> Internet-Drafts directories. This draft is a work item of the 
> Pseudo Wire Emulation Edge to Edge Working Group of the IETF.
> 
> 	Title		: Pseudowire Setup and Maintenance using LDP
> 	Author(s)	: L. Martini, et al.
> 	Filename	: draft-ietf-pwe3-control-protocol-12.txt
> 	Pages		: 41
> 	Date		: 2004-10-25
> 	
> Layer 2 services (such as Frame Relay, ATM, ethernet) can be
>    "emulated" over an IP and/or MPLS backbone by
> encapsulating the layer
>    2 PDUs and then transmitting them over "pseudowires". It is also
>    possible to use pseudowires to provide low-rate TDM and 
> SONET circuit
>    emulation over an IP and/or MPLS network. This document specifies a
>    protocol for establishing and maintaining the pseudowires, using
>    extensions to LDP. Procedures for encapsulating layer 2 PDUs are
>    specified in a set of companion documents.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-control-pr
otocol-12.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-control-protocol-12.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-control-protocol-12.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_001_01C4C592.B224DC2D
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: minor comment [PWE3] I-D =
ACTION:draft-ietf-pwe3-control-protocol-12.txt</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2>Luca et all,</FONT>
<BR><FONT SIZE=3D2>I noticed there is some old text left in Section =
5.2.2 &quot;Encoding the Generalized ID FEC Element&quot;:</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; &quot;The PW information length field, =
contains the length of the SAII,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; TAII, AGI combined, and the interface =
parameters field in octets. If</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; this value is 0, then it references all =
PWs using the specified</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; grouping ID. In this case there are no =
other FEC element fields</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; (AGI,SAII, etc. ) present, nor any =
interface parameters.&quot;</FONT>
</P>

<P><FONT SIZE=3D2>Considering that for the Generalized ID FEC TLVs are =
proposed for Interface Parameters and PW Grouping, we should take out =
&quot;the interface parameter fields&quot; and replace &quot;grouping =
ID&quot; with &quot;PW Grouping TLV (see section =
5.2.2.2)&quot;...</FONT></P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: pwe3-bounces@ietf.org [<A =
HREF=3D"mailto:pwe3-bounces@ietf.org">mailto:pwe3-bounces@ietf.org</A>] =
On</FONT>
<BR><FONT SIZE=3D2>&gt; Behalf Of Internet-Drafts@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Monday, October 25, 2004 4:06 PM</FONT>
<BR><FONT SIZE=3D2>&gt; To: i-d-announce@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: pwe3@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: [PWE3] I-D =
ACTION:draft-ietf-pwe3-control-protocol-12.txt</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; A New Internet-Draft is available from the =
on-line</FONT>
<BR><FONT SIZE=3D2>&gt; Internet-Drafts directories. This draft is a =
work item of the </FONT>
<BR><FONT SIZE=3D2>&gt; Pseudo Wire Emulation Edge to Edge Working =
Group of the IETF.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Title&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
Pseudowire Setup and Maintenance using LDP</FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : L. Martini, et =
al.</FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
draft-ietf-pwe3-control-protocol-12.txt</FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Pages&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
41</FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Date&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
2004-10-25</FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; Layer 2 services (such as Frame Relay, ATM, =
ethernet) can be</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; &quot;emulated&quot; over an =
IP and/or MPLS backbone by</FONT>
<BR><FONT SIZE=3D2>&gt; encapsulating the layer</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; 2 PDUs and then transmitting =
them over &quot;pseudowires&quot;. It is also</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; possible to use pseudowires =
to provide low-rate TDM and </FONT>
<BR><FONT SIZE=3D2>&gt; SONET circuit</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; emulation over an IP and/or =
MPLS network. This document specifies a</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; protocol for establishing and =
maintaining the pseudowires, using</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; extensions to LDP. Procedures =
for encapsulating layer 2 PDUs are</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; specified in a set of =
companion documents.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; A URL for this Internet-Draft is:</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-pwe3-control-pr" =
TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-ietf-pwe3-co=
ntrol-pr</A></FONT>
<BR><FONT SIZE=3D2>otocol-12.txt</FONT>
</P>

<P><FONT SIZE=3D2>To remove yourself from the I-D Announcement list, =
send a message to </FONT>
<BR><FONT SIZE=3D2>i-d-announce-request@ietf.org with the word =
unsubscribe in the body of the message.&nbsp; </FONT>
<BR><FONT SIZE=3D2>You can also visit <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/I-D-announce" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/I-D-announce</A=
> </FONT>
<BR><FONT SIZE=3D2>to change your subscription settings.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Internet-Drafts are also available by anonymous FTP. =
Login with the username &quot;anonymous&quot; and a password of your =
e-mail address. After logging in, type &quot;cd internet-drafts&quot; =
and then</FONT></P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>&quot;get =
draft-ietf-pwe3-control-protocol-12.txt&quot;.</FONT>
</P>

<P><FONT SIZE=3D2>A list of Internet-Drafts directories can be found in =
<A HREF=3D"http://www.ietf.org/shadow.html" =
TARGET=3D"_blank">http://www.ietf.org/shadow.html</A> </FONT>
<BR><FONT SIZE=3D2>or <A =
HREF=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" =
TARGET=3D"_blank">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</A></FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Internet-Drafts can also be obtained by =
e-mail.</FONT>
</P>

<P><FONT SIZE=3D2>Send a message to:</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>mailserv@ietf.org.</FONT>
<BR><FONT SIZE=3D2>In the body type:</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&quot;FILE =
/internet-drafts/draft-ietf-pwe3-control-protocol-12.txt&quot;.</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR><FONT SIZE=3D2>NOTE:&nbsp;&nbsp; The mail server at ietf.org can =
return the document in</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>MIME-encoded form by using the &quot;mpack&quot; =
utility.&nbsp; To use this</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>feature, =
insert the command &quot;ENCODING mime&quot; before the =
&quot;FILE&quot;</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>command.&nbsp; To decode the response(s), you will need =
&quot;munpack&quot; or</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>a =
MIME-compliant mail reader.&nbsp; Different MIME-compliant mail =
readers</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>exhibit =
different behavior, especially when dealing with</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&quot;multipart&quot; MIME messages (i.e. documents which have =
been split</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>up into =
multiple messages), so check your local documentation on</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>how to =
manipulate these messages.</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR><FONT SIZE=3D2>Below is the data which will enable a MIME compliant =
mail reader implementation to automatically retrieve the ASCII version =
of the Internet-Draft.</FONT></P>

</BODY>
</HTML>
------_=_NextPart_001_01C4C592.B224DC2D--


--===============1066197187==
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

--===============1066197187==--




From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
Date: Mon, 8 Nov 2004 16:31:03 +0200
Lines: 103
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: "Singh, Hardeep \(Hardeep\)" <hardeep@lucent.com>,
	"'pwe3@ietf.org'" <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Mon Nov 08 16:02:02 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Thomas D. Nadeau'" <tnadeau@cisco.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Tom and all,
IMHO one generic status code indicating that 
the local AC is down is necessary. 

I am not at all sure about the additional refinements.E.g., if a FR DLCI
goes down,would it mean that it has Rx failure or Tx failure?

My 2c.
----------------------------------------------------------------------------
--------
With best regards,
                          Sasha Vainshtein
email:   sasha@axerra.com <mailto:sasha@axerra.com> 
phone:  +972-3-7659993 (office)
            +972-8-9254948 (home)
            +972-58-674833 (cellular)


> -----Original Message-----
> From: Thomas D. Nadeau [mailto:tnadeau@cisco.com]
> Sent: Friday, November 05, 2004 10:52 PM
> To: Singh, Hardeep (Hardeep)
> Cc: 'pwe3@ietf.org'
> Subject: Re: [PWE3] draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
> 
> 
> 
> 	I don't think Dave's proposal is to make the others
> optional; it was to remove them completely for now.
> 
> 	--Tom
> 
> 
> > I agree. Probably the first two can me made mandatory
> > and the rest optional to implement or be decided later.
> >
> > We too came to the same conclusion when we implemented
> > PWE3 circuits as per the draft.
> >
> > Thanks
> >
> > Hardeep
> >
> > -----Original Message-----
> > From: pwe3-bounces@ietf.org 
[mailto:pwe3-bounces@ietf.org]On Behalf Of
> David Allan
> Sent: Thursday, November 04, 2004 4:51 PM
> To: 'pwe3@ietf.org'
> Subject: FW: [PWE3] draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
>
>
>
> Hi:
>
> A number of us have been working on fault notification for PWs, and 
> have
> concluded that we do not need to couple fault direction and fault 
> location
> the way it is currently defined for the LDP status TLV in the IANA
> allocations draft. There is another proposal but it has not had enough 
> "soak
> time" to spring in the middle of a last call.
>
> Rather than hold up the IANA allocations draft, the suggestion is 
> simply to
> remove the status code points we know we will be revising.
>
> So keep
>        0x00000000 - Pseudo Wire forwarding ( clear all failures )
>        0x00000001 - Pseudo Wire Not Forwarding
>
> And lose
>        0x00000002 - Local Attachement Circuit ( ingress ) Receive Fault
>        0x00000004 - Local Attachement Circuit ( egress ) Transmit Fault
>        0x00000008 - Local PSN-facing PW ( ingress ) Receive Fault
>        0x00000010 - Local PSN-facing PW ( egress ) Transmit Fault
>
> So the IANA registry entry is set up, and we'll provide the requisite
> additional code points when it is pinned down...
>
> Any objections?
>
> cheers
> Dave
>
>
> _______________________________________________
> 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  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: [Fwd: [Fwd: Re: draft-ietf-pwe3-arch-07.txt editorials]]
Date: Mon, 08 Nov 2004 15:13:57 +0000
Lines: 210
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Thomas Narten <narten@us.ibm.com>, pwe3 <pwe3@ietf.org>,
	"'danny@tcb.net'" <danny@tcb.net>
X-From: pwe3-bounces@ietf.org Mon Nov 08 16:45:50 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: RFC Editor <rfc-editor@rfc-editor.org>
X-Scan-Signature: 17e5edc4dfd335965c1d21372171c01c
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


Please make these edit changes to draft-ietf-pwe3-arch-07.txt

Note that edit (1) removes the reference that is blocking
publication.

- Stewart




-------- Original Message --------
Subject: [Fwd: Re: draft-ietf-pwe3-arch-07.txt editorials]
Date: Fri, 22 Oct 2004 10:26:01 +0100
From: Stewart Bryant <stbryant@cisco.com>
To: pwe3 <pwe3@ietf.org>

I propose that we send the following editorial requests to
the RFC editor.

Note that the first change removes an important gate
because now the only gate is L2TPv3 which is in the
RFC-editor's queue with no gate.

- Stewart

Stewart Bryant wrote:

> 
> The following editorial changes need to be made to
> <draft-ietf-pwe3-arch-07.txt>
> 
> Note that the first change removes a reference that is
> gating the draft and hence requires a change to the
> status in the RFC editors queue.
> 
> --------------------------------------------------
> 
> 1)The reference [FRAG] should be deleted from
> the Normative References
> 
> REASON
> 
> [FRAG] was a normative reference in section 5.4.3.
> "PW over MPLS Generic Control Word" in the -06
> version of the draft. This section was removed
> and placed in a new draft. There was no other
> reference to [FRAG] in the text and so this
> reference should have also been removed.
> 
> ---------------------------------------------------
> 
> 2) In the following text "the associated PWs" should
> be replaced by "the PW"
> 
> "7.3.1.  Pseudo-wire Up/Down Notification
> 
>   If a native service REQUIRES bi-directional connectivity, the
>   corresponding emulated service can only be signaled as being up when
>   the associated PWs, and PSN tunnels if any, are functional in both
>   directions. "
> 
> Also REQUIRES should be lower case.
> 
> The text should then read
> 
> "7.3.1.  Pseudo-wire Up/Down Notification
> 
>   If a native service requires bi-directional connectivity, the
>   corresponding emulated service can only be signaled as being up when
>   the PW, and PSN tunnels if any, are functional in both
>   directions. "
> 
> 
> REASON
> ------
> 
> PWs are bi-directional and therefore, there is only one PW
> that must be up.
> 
> Note that the equivalent text in the requirements draft:
> 
> "5.1.  Setup and Teardown of Pseudo-Wires
> <snip>
>   If a native circuit is bi-directional, the corresponding emulated
>   circuit can be signaled "Up" only when the associated PW and PSN
>   tunnels in both directions are functional."
> 
> is correct and the change makes the two drafts
> consistent.
> 
> -----------------------------------------------------
> 3) At the end of 5.4.3. PW-IP Packet Discrimination
> 
> there is a spurious ".sp" which needs to be deleted
> 
> -----------------------------------------------------
> 
> 4) In "1.4  Terminology" the following text should
> be removed:
> 
>   PWE3 Payload Type    A identifier used to distinguish between
>   Identifier           an MPLS IP payload and a CW that is not
>   (PWE3-PID)           ECMP safe.
> 
> REASON
> ------
> This term is no longer used by PWE3.
> 
> -----------------------------------------------------
> 
> 5) In "5.4.3. PW-IP Packet Discrimination" delete the
> line
> 
>   The use of this field for PWs is work in progress.
> 
> REASON
> ------
> This work has progressed since -07 was sent to the IESG.
> Text is cleaner without the line and no value is lost.
> 
> 
> ------------------------------------------------------
> 6) From the "Normative References" section the
> following references should be removed as they are
> not used:
> 
> [RFC791]
> [RFC1883]
> [RFC1902]
> [RFC2119]
> [RFC3031]
> 
> REASON
> ------
> Not referenced by the text
> 
> ------------------------------------------------------
> 
> 7) All references to RFC2558 should be replaced by
> references to RFC3592
> 
> This occur in Fig 16 and in the Normative references
> which should now include the following definition
> for RFC3592:
> 
> [RFC3592]   K. Tesink, "Definitions of Managed Objects for the
> Synchronous Optical Network/Synchronous Digital Hierarchy
> (SONET/SDH) Interface Type", RFC3592, September 2003.
> 
> REASON
> ------
> RFC2558 has been obsoleted by RFC3592
> 
> -------------------------------------------------------
> 
> 8) All references to [LDPMIB] should be replaced by
> [RFC3815]
> 
> In the informative references the reference should be
> 
> [RFC3815]   Cucchiara, J., Sjostrand, H., and Luciani, J.,
>            "Definitions of Managed Objects for the Multiprotocol
>            Label Switching, Label Distribution Protocol (LDP)",
>            RFC-3815, June 2004
> 
> REASON
> ------
> This Internet-Draft was published as a Proposed Standard, RFC 3815
> (http://www.ietf.org/rfc/rfc3815.txt), on 2004-6-22.
> 
> The name of the internet-draft was draft-ietf-mpls-ldp-mib-14.txt
> 
> --------------------------------------------------------
> 
> 9) All references to [LSRMIB} should be changed to [RFC3813]
> 
> In the informative references the reference should be
> 
> [RFC3813] Srinivasan, C., Viswanathan, A., Nadeau, T.
>          "Multiprotocol Label Switching (MPLS) Label
>          Switching Router (LSR) Management Information
>          Base (MIB)", RFC-3813, June 2004
> 
> REASON
> ------
> This Internet-Draft was published as a Proposed Standard, RFC 3813
> (http://www.ietf.org/rfc/rfc3813.txt), on 2004-6-22.
> 
> The name of the internet-draft was draft-ietf-mpls-lsr-mib-14.txt
> 
> -------------------------------------------------------
> 
> 10) All references to [TEMIB] should be changed to [RFC3812]
> 
> In the informative references the reference should be
> 
> [RFC3812] Srinivasan, C., Viswanathan, A., Nadeau, T.
>          "Multiprotocol Label Switching (MPLS) Traffic
>          Engineering (TE) Management Information Base (MIB)",
>          RFC-3812, June 2004.
> 
> REASON
> -------
> This Internet-Draft was published as a Proposed Standard, RFC 3812
> (http://www.ietf.org/rfc/rfc3812.txt), on 2004-6-22.
> 
> The name of the internet-draft was draft-ietf-mpls-te-mib-14.txt
> 
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
Subject: RE: draft-ietf-pwe3-cw-00.txt - LAST CALL
Date: Mon, 8 Nov 2004 08:00:50 -0800
Lines: 65
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1215988418=="
X-From: pwe3-bounces@ietf.org Mon Nov 08 17:33:29 2004
Return-path: <pwe3-bounces@ietf.org>
To: Stewart Bryant <stbryant@cisco.com>, lmartini@cisco.com, pwe3
	<pwe3@ietf.org>
X-Mailer: Internet Mail Service (5.5.2656.59)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============1215988418==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C5AC.1E261CBC"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C4C5AC.1E261CBC
Content-Type: text/plain

Hi,
 
It is not clear what is the relationship between the Payload-Identifier defined in section 4.1 of http://www.ietf.org/internet-drafts/draft-ietf-pwe3-vccv-03.tx <http://www.ietf.org/internet-drafts/draft-ietf-pwe3-vccv-03.tx> , and the PW Associated Channel defined in this document. Do we still need the Payload-Identifier?
 
Thanks,
Shahram

------_=_NextPart_001_01C4C5AC.1E261CBC
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<TITLE>RE: [PWE3] draft-ietf-pwe3-cw-00.txt - LAST CALL</TITLE>

<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=508584515-08112004><FONT face=Arial color=#0000ff 
size=2>Hi,</FONT></SPAN></DIV>
<DIV><SPAN class=508584515-08112004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=508584515-08112004><FONT face=Arial color=#0000ff size=2>It is 
not clear what is the relationship between the Payload-Identifier defined in 
section 4.1 of <A 
href="http://www.ietf.org/internet-drafts/draft-ietf-pwe3-vccv-03.tx">http://www.ietf.org/internet-drafts/draft-ietf-pwe3-vccv-03.tx</A>, 
and </FONT></SPAN><SPAN class=508584515-08112004><FONT face=Arial color=#0000ff 
size=2>the PW Associated Channel defined in this document. Do we still need the 
Payload-Identifier?</FONT></SPAN></DIV>
<DIV><SPAN class=508584515-08112004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=508584515-08112004><FONT face=Arial color=#0000ff 
size=2>Thanks,</FONT></SPAN></DIV>
<DIV><SPAN class=508584515-08112004><FONT face=Arial color=#0000ff 
size=2>Shahram</FONT></SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01C4C5AC.1E261CBC--


--===============1215988418==
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

--===============1215988418==--




From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: draft-ietf-pwe3-cw-00.txt - LAST CALL
Date: Mon, 08 Nov 2004 16:14:26 +0000
Lines: 21
References: <4B6D09F3B826D411A67300D0B706EFDE0115D269@nt-exch-yow.pmc_nt.nt.pmc-sierra.bc.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pwe3 <pwe3@ietf.org>, lmartini@cisco.com
X-From: pwe3-bounces@ietf.org Mon Nov 08 17:43:18 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: Shahram Davari <Shahram_Davari@pmc-sierra.com>
In-Reply-To: <4B6D09F3B826D411A67300D0B706EFDE0115D269@nt-exch-yow.pmc_nt.nt.pmc-sierra.bc.ca>
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

VCCV and CW are out of alignment.
There needs to be an update to VCCV to re-sync the drafts.

Note that the update can be made backwards compatible
by allocating Channel Type 0x21 to VCCV.

Stewart



Shahram Davari wrote:
> Hi,
>  
> It is not clear what is the relationship between the Payload-Identifier 
> defined in section 4.1 of 
> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-vccv-03.tx, and the 
> PW Associated Channel defined in this document. Do we still need the 
> Payload-Identifier?
>  
> Thanks,
> Shahram


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "David Allan" <dallan@nortelnetworks.com>
Subject: RE: draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
Date: Mon, 8 Nov 2004 11:29:24 -0500
Lines: 142
Cc: "Singh, Hardeep \(Hardeep\)" <hardeep@lucent.com>,
	"'pwe3@ietf.org'" <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Mon Nov 08 17:59:26 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Sasha Vainshtein'" <Sasha@AXERRA.com>, "'Thomas D. Nadeau'"
	<tnadeau@cisco.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Hi Sasha:

We've worked through this in some detail. IMO a split horizon "down" is a
summarization of AIS/RDI which is hard to go backwards from. Communicating
directionality covers all cases when considering all the interworking
possiblities ...including the fact that an ingress PE can also observe
PW/PSN failures (PING or RSVP patherr)...

rgds
Dave




> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On 
> Behalf Of Sasha Vainshtein
> Sent: Monday, November 08, 2004 9:31 AM
> To: 'Thomas D. Nadeau'
> Cc: Singh, Hardeep (Hardeep); 'pwe3@ietf.org'
> Subject: RE: [PWE3] draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
> 
> 
> Tom and all,
> IMHO one generic status code indicating that 
> the local AC is down is necessary. 
> 
> I am not at all sure about the additional refinements.E.g., 
> if a FR DLCI goes down,would it mean that it has Rx failure 
> or Tx failure?
> 
> My 2c.
> --------------------------------------------------------------
> --------------
> --------
> With best regards,
>                           Sasha Vainshtein
> email:   sasha@axerra.com <mailto:sasha@axerra.com> 
> phone:  +972-3-7659993 (office)
>             +972-8-9254948 (home)
>             +972-58-674833 (cellular)
> 
> 
> > -----Original Message-----
> > From: Thomas D. Nadeau [mailto:tnadeau@cisco.com]
> > Sent: Friday, November 05, 2004 10:52 PM
> > To: Singh, Hardeep (Hardeep)
> > Cc: 'pwe3@ietf.org'
> > Subject: Re: [PWE3] draft-ietf-pwe3-iana-allocation-07.txt 
> - LAST CALL
> > 
> > 
> > 
> > 	I don't think Dave's proposal is to make the others 
> optional; it was 
> > to remove them completely for now.
> > 
> > 	--Tom
> > 
> > 
> > > I agree. Probably the first two can me made mandatory
> > > and the rest optional to implement or be decided later.
> > >
> > > We too came to the same conclusion when we implemented
> > > PWE3 circuits as per the draft.
> > >
> > > Thanks
> > >
> > > Hardeep
> > >
> > > -----Original Message-----
> > > From: pwe3-bounces@ietf.org
> [mailto:pwe3-bounces@ietf.org]On Behalf Of
> > David Allan
> > Sent: Thursday, November 04, 2004 4:51 PM
> > To: 'pwe3@ietf.org'
> > Subject: FW: [PWE3] draft-ietf-pwe3-iana-allocation-07.txt 
> - LAST CALL
> >
> >
> >
> > Hi:
> >
> > A number of us have been working on fault notification for PWs, and
> > have
> > concluded that we do not need to couple fault direction and fault 
> > location
> > the way it is currently defined for the LDP status TLV in the IANA
> > allocations draft. There is another proposal but it has not 
> had enough 
> > "soak
> > time" to spring in the middle of a last call.
> >
> > Rather than hold up the IANA allocations draft, the suggestion is
> > simply to
> > remove the status code points we know we will be revising.
> >
> > So keep
> >        0x00000000 - Pseudo Wire forwarding ( clear all failures )
> >        0x00000001 - Pseudo Wire Not Forwarding
> >
> > And lose
> >        0x00000002 - Local Attachement Circuit ( ingress ) 
> Receive Fault
> >        0x00000004 - Local Attachement Circuit ( egress ) 
> Transmit Fault
> >        0x00000008 - Local PSN-facing PW ( ingress ) Receive Fault
> >        0x00000010 - Local PSN-facing PW ( egress ) Transmit Fault
> >
> > So the IANA registry entry is set up, and we'll provide the 
> requisite 
> > additional code points when it is pinned down...
> >
> > Any objections?
> >
> > cheers
> > Dave
> >
> >
> > _______________________________________________
> > 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
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Danny McPherson <danny@tcb.net>
Subject: PWE3 Agenda
Date: Mon, 8 Nov 2004 11:25:55 -0700
Lines: 34
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Cc: agenda@ietf.org
X-From: pwe3-bounces@ietf.org Mon Nov 08 19:57:39 2004
Return-path: <pwe3-bounces@ietf.org>
To: pwe3@ietf.org
X-Mailer: Apple Mail (2.619)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


Folks,
Here's the agenda for the meeting on Thursday.  Apologies for
the tardy distribution.

-danny & Stewart

-----
PWE3 -- IETF 61
THURSDAY, November 11, 2004

Chairs:
   Stewart Bryant <stbryant@cisco.com>
   Danny McPherson <danny@tcb.net>


1530-1730 Afternoon Session II; Lincoln East

  o Administrivia (5 minutes)
    - Agenda
    - Blue Sheets
    - Minutes
  o Charter & Draft Status - Stewart & Danny (25 minutes)
  o PW CW - Stewart & Danny (5 minutes)
     http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw-00.txt
  o UDP Statement to ITU - Stewart (10 minutes)
  o UDP Encapsulation - Yaakov Stein (15 minutes)
     Discussion: The application has to be described more carefully,
     in order not to imply that we are suggesting UDP instead of MPLS
     inside a service provider's network.  A few slides to illustrate
     that UDP is a sensible solution for CE-CE emulation for the
     enterprise space.  Also intend to address security and
     congestion implications.
  o Wrap-Up (5 minutes)


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
Subject: RE: draft-ietf-pwe3-cw-00.txt - LAST CALL
Date: Mon, 8 Nov 2004 11:18:17 -0800
Lines: 157
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0967918549=="
X-From: pwe3-bounces@ietf.org Mon Nov 08 21:02:33 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Florin Balus'" <balus@nortelnetworks.com>, Stewart Bryant
	<stbryant@cisco.com>, lmartini@cisco.com, pwe3 <pwe3@ietf.org>
X-Mailer: Internet Mail Service (5.5.2656.59)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============0967918549==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C5C7.B3A1D8CE"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C4C5C7.B3A1D8CE
Content-Type: text/plain

Hi,
 
If "the control word MUST NOT be used" is left in the Control Protocol draft, based on the security section of the CW draft, the Associated Channel can't be used. This means only out-of band channel must be used for OAM, which can't guarantee OAM packets follow the same path as data.
 
Yours,
Shahram

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]On Behalf Of Florin Balus
Sent: Sunday, November 07, 2004 5:56 PM
To: Stewart Bryant; lmartini@cisco.com; pwe3
Subject: RE: [PWE3] draft-ietf-pwe3-cw-00.txt - LAST CALL




Stewart,Luca, 

I understand the recommendation in section 2 of draft-ietf-pwe3-cw-00.txt - "A PW carried over an MPLS PSN that uses the contents of the MPLS payload to select the ECMP path SHOULD employ the PW Control Word described in Section 3 for data" - is directed to distinguish a PW payload from an "IP payload carried over an MPLS PSN" - see also section 1 of the same document. 


draft-ietf-pwe3-control-protocol-12.txt - Section 4.6 (IP Layer2 Transport) contains the statement: "The control word MUST NOT be used". It seems to me that if we follow this recommendation for this specific type of PW, we will run into the issue described in section 1 of draft-ietf-pwe3-cw-00.txt: i.e. "The inability to ensure that all packets belonging to a PW follow the same path also prevents the PW OAM [VCCV] mechanism from correctly monitoring the PW."

Is it possible to remove the MUST from the above statement (or even better all the text) from section 4.6 of draft-ietf-pwe3-control-protocol-12.txt? Otherwise it looks to me like the 2 drafts are contradicting each other. Regards,

Florin     

> -----Original Message----- 
> From: pwe3-bounces@ietf.org [ mailto:pwe3-bounces@ietf.org <mailto:pwe3-bounces@ietf.org> ] On 
> Behalf Of Stewart Bryant 
> Sent: Monday, November 01, 2004 8:04 PM 
> To: pwe3 
> Subject: [PWE3] draft-ietf-pwe3-cw-00.txt - LAST CALL 
> 
> 
> This is the start of two week last call on 
> 
> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw-00.txt <http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw-00.txt>  
> 
> Last call will finish on 16th November 2004 
> 
> Stewart 
> 
> 
> _______________________________________________ 
> pwe3 mailing list 
> pwe3@ietf.org 
> https://www1.ietf.org/mailman/listinfo/pwe3 <https://www1.ietf.org/mailman/listinfo/pwe3>  
> 
> 


------_=_NextPart_001_01C4C5C7.B3A1D8CE
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<TITLE>RE: [PWE3] draft-ietf-pwe3-cw-00.txt - LAST CALL</TITLE>

<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=034504016-08112004><FONT face=Arial color=#0000ff 
size=2>Hi,</FONT></SPAN></DIV>
<DIV><SPAN class=034504016-08112004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=034504016-08112004><FONT face=Arial color=#0000ff size=2>If 
"the control word MUST NOT be used" is left in the Control Protocol draft, based 
on the security section of the CW draft, the Associated Channel can't be used. 
This means&nbsp;only out-of band channel must be used for OAM, which can't 
guarantee OAM packets follow the same path as data.</FONT></SPAN></DIV>
<DIV><SPAN class=034504016-08112004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=034504016-08112004><FONT face=Arial color=#0000ff 
size=2>Yours,</FONT></SPAN></DIV>
<DIV><SPAN class=034504016-08112004><FONT face=Arial color=#0000ff 
size=2>Shahram</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> pwe3-bounces@ietf.org 
  [mailto:pwe3-bounces@ietf.org]<B>On Behalf Of </B>Florin Balus<BR><B>Sent:</B> 
  Sunday, November 07, 2004 5:56 PM<BR><B>To:</B> Stewart Bryant; 
  lmartini@cisco.com; pwe3<BR><B>Subject:</B> RE: [PWE3] 
  draft-ietf-pwe3-cw-00.txt - LAST CALL<BR><BR></FONT></DIV><BR>
  <P><FONT size=2>Stewart,Luca,</FONT> </P>
  <P><FONT size=2>I understand the recommendation in section 2 of 
  draft-ietf-pwe3-cw-00.txt - "A PW carried over an MPLS PSN that uses the 
  contents of the MPLS payload to select the ECMP path SHOULD employ the PW 
  Control Word described in Section 3 for data" - is directed to distinguish a 
  PW payload from an "IP payload carried over an MPLS PSN" - see also section 1 
  of the same document. </FONT></P>
  <P><FONT size=2></FONT> <BR><FONT 
  size=2>draft-ietf-pwe3-control-protocol-12.txt - Section 4.6 (IP Layer2 
  Transport) contains the statement: "The control word MUST NOT be used". It 
  seems to me that if we follow this recommendation for this specific type of 
  PW, we will run into the issue described in section 1 of 
  draft-ietf-pwe3-cw-00.txt: i.e. "The inability to ensure that all packets 
  belonging to a PW follow the same path also prevents the PW OAM [VCCV] 
  mechanism from correctly monitoring the PW."</FONT></P>
  <P><FONT size=2>Is it possible to remove the MUST from the above statement (or 
  even better all the text) from section 4.6 of 
  draft-ietf-pwe3-control-protocol-12.txt? Otherwise it looks to me like the 2 
  drafts are contradicting each other. Regards,</FONT></P>
  <P><FONT size=2>Florin&nbsp;&nbsp;&nbsp;&nbsp; </FONT></P>
  <P><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT size=2>&gt; 
  From: pwe3-bounces@ietf.org [<A 
  href="mailto:pwe3-bounces@ietf.org">mailto:pwe3-bounces@ietf.org</A>] 
  On</FONT> <BR><FONT size=2>&gt; Behalf Of Stewart Bryant</FONT> <BR><FONT 
  size=2>&gt; Sent: Monday, November 01, 2004 8:04 PM</FONT> <BR><FONT 
  size=2>&gt; To: pwe3</FONT> <BR><FONT size=2>&gt; Subject: [PWE3] 
  draft-ietf-pwe3-cw-00.txt - LAST CALL</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; This is the start of 
  two week last call on</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; <A 
  href="http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw-00.txt" 
  target=_blank>http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw-00.txt</A></FONT> 
  <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; Last call will finish on 
  16th November 2004</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  Stewart</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; 
  _______________________________________________</FONT> <BR><FONT size=2>&gt; 
  pwe3 mailing list</FONT> <BR><FONT size=2>&gt; pwe3@ietf.org</FONT> <BR><FONT 
  size=2>&gt; <A href="https://www1.ietf.org/mailman/listinfo/pwe3" 
  target=_blank>https://www1.ietf.org/mailman/listinfo/pwe3</A></FONT> <BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; </FONT></P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C4C5C7.B3A1D8CE--


--===============0967918549==
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

--===============0967918549==--




From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: draft-ietf-pwe3-cw-00.txt - LAST CALL
Date: Mon, 08 Nov 2004 19:43:21 +0000
Lines: 78
References: <4B6D09F3B826D411A67300D0B706EFDE0115D26B@nt-exch-yow.pmc_nt.nt.pmc-sierra.bc.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pwe3 <pwe3@ietf.org>, lmartini@cisco.com
X-From: pwe3-bounces@ietf.org Mon Nov 08 21:17:11 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: Shahram Davari <Shahram_Davari@pmc-sierra.com>
In-Reply-To: <4B6D09F3B826D411A67300D0B706EFDE0115D26B@nt-exch-yow.pmc_nt.nt.pmc-sierra.bc.ca>
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Shahram

You are correct. There is a problem with running 3032 as the PW encap 
and hence not using the CW, and also wanting to OAM the PW.

Stewart



Shahram Davari wrote:

> Hi,
>  
> If "the control word MUST NOT be used" is left in the Control Protocol 
> draft, based on the security section of the CW draft, the Associated 
> Channel can't be used. This means only out-of band channel must be used 
> for OAM, which can't guarantee OAM packets follow the same path as data.
>  
> Yours,
> Shahram
> 
>     -----Original Message-----
>     From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]On Behalf
>     Of Florin Balus
>     Sent: Sunday, November 07, 2004 5:56 PM
>     To: Stewart Bryant; lmartini@cisco.com; pwe3
>     Subject: RE: [PWE3] draft-ietf-pwe3-cw-00.txt - LAST CALL
> 
> 
>     Stewart,Luca,
> 
>     I understand the recommendation in section 2 of
>     draft-ietf-pwe3-cw-00.txt - "A PW carried over an MPLS PSN that uses
>     the contents of the MPLS payload to select the ECMP path SHOULD
>     employ the PW Control Word described in Section 3 for data" - is
>     directed to distinguish a PW payload from an "IP payload carried
>     over an MPLS PSN" - see also section 1 of the same document.
> 
> 
>     draft-ietf-pwe3-control-protocol-12.txt - Section 4.6 (IP Layer2
>     Transport) contains the statement: "The control word MUST NOT be
>     used". It seems to me that if we follow this recommendation for this
>     specific type of PW, we will run into the issue described in section
>     1 of draft-ietf-pwe3-cw-00.txt: i.e. "The inability to ensure that
>     all packets belonging to a PW follow the same path also prevents the
>     PW OAM [VCCV] mechanism from correctly monitoring the PW."
> 
>     Is it possible to remove the MUST from the above statement (or even
>     better all the text) from section 4.6 of
>     draft-ietf-pwe3-control-protocol-12.txt? Otherwise it looks to me
>     like the 2 drafts are contradicting each other. Regards,
> 
>     Florin    
> 
>      > -----Original Message-----
>      > From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On
>      > Behalf Of Stewart Bryant
>      > Sent: Monday, November 01, 2004 8:04 PM
>      > To: pwe3
>      > Subject: [PWE3] draft-ietf-pwe3-cw-00.txt - LAST CALL
>      >
>      >
>      > This is the start of two week last call on
>      >
>      > http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw-00.txt
>      >
>      > Last call will finish on 16th November 2004
>      >
>      > Stewart
>      >
>      >
>      > _______________________________________________
>      > pwe3 mailing list
>      > pwe3@ietf.org
>      > https://www1.ietf.org/mailman/listinfo/pwe3
>      >
>      >
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Luca Martini <lmartini@cisco.com>
Subject: Re: draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
Date: Sun, 07 Nov 2004 11:16:21 -0700
Lines: 63
References: <4186C706.7080901@cisco.com>
	<6.1.2.0.2.20041101200914.05af9260@mail.comcast.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pwe3 <pwe3@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-From: pwe3-bounces@ietf.org Mon Nov 08 23:07:51 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616
X-Accept-Language: Italian [it], French/Canada [fr-CA], French/France [fr-FR],
	English/United States [en-US]
To: "Andrew G. Malis" <andymalis@comcast.net>
In-Reply-To: <6.1.2.0.2.20041101200914.05af9260@mail.comcast.net>
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Andrew G. Malis wrote:

> Stewart,
>
> It seems odd to take this to last call prior to the control signaling 
> draft.  They should probably go through last call simultaneously.
>
the control draft has already gone through last call a while back .... 
it's waiting in the queue for the IESG.

> That said, I have a few comments:
>
> 1. For PW type:
>
> 0x0001  Frame Relay DLCI ( Martini Mode )
>
> Add the following note:
>
> Note: This PW type is grandfathered for a historical protocol.  The 
> recommended standards-track protocol to use is 0x0019,  Frame Relay DLCI.
>
If anywhere this note should probably go in the frame-relay document , 
not in the allocation document.

> 2. Just a stylistic thing - Luca seems to like spaces between the 
> parentheses and the parenthetical expression.  I don't.
>
picky picky ....
:-)

> 3. There's an extraneous quote in the header for section 4.
>
you mean :
Note that the Length field is defined as the length of the interface
parameter including the parameter id and length field itself.

I see if it is really needed

Luca

> Thanks,
> Andy
>
>
> At 11/1/2004 11:30 PM +0000, Stewart Bryant wrote:
>
>> This is the start of a two week last call for
>>
>> IANA Allocations for pseudo Wire Edge to Edge Emulation (PWE3)
>> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-iana-allocation-07.txt 
>>
>>
>> Last call will end Tuesday 16th October 2004
>>
>> - Stewart
>
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
>


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Luca Martini <lmartini@cisco.com>
Subject: Re: FW: draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
Date: Tue, 09 Nov 2004 07:18:10 -0700
Lines: 54
References: <87AC5F88F03E6249AEA68D40BD3E00BE019BC0D0@zcarhxm2.corp.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "'pwe3@ietf.org'" <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Tue Nov 09 15:29:38 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616
X-Accept-Language: Italian [it], French/Canada [fr-CA], French/France [fr-FR],
	English/United States [en-US]
To: David Allan <dallan@nortelnetworks.com>
In-Reply-To: <87AC5F88F03E6249AEA68D40BD3E00BE019BC0D0@zcarhxm2.corp.nortel.com>
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

David,

This is an allocation draft. If you want something different we'll be 
happy to add it.
If somebody wants to use the messages below , there is no way to prevent 
them from allocating these.
I'm interested in why these are not needed ?
There are many PW types that do not have AIS/RDI support....
How would you have this information propagate ?

Ex. Frame-relay -> IP -> ATM  ?

Luca


David Allan wrote:

>Hi:
>
>A number of us have been working on fault notification for PWs, and have
>concluded that we do not need to couple fault direction and fault location
>the way it is currently defined for the LDP status TLV in the IANA
>allocations draft. There is another proposal but it has not had enough "soak
>time" to spring in the middle of a last call. 
>
>Rather than hold up the IANA allocations draft, the suggestion is simply to
>remove the status code points we know we will be revising.
>
>So keep
>       0x00000000 - Pseudo Wire forwarding ( clear all failures )
>       0x00000001 - Pseudo Wire Not Forwarding
> 
>And lose
>       0x00000002 - Local Attachement Circuit ( ingress ) Receive Fault
>       0x00000004 - Local Attachement Circuit ( egress ) Transmit Fault
>       0x00000008 - Local PSN-facing PW ( ingress ) Receive Fault
>       0x00000010 - Local PSN-facing PW ( egress ) Transmit Fault
>
>So the IANA registry entry is set up, and we'll provide the requisite
>additional code points when it is pinned down...
>
>Any objections?
>
>cheers
>Dave
> 
>
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www1.ietf.org/mailman/listinfo/pwe3
>
>  
>


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Luca Martini <lmartini@cisco.com>
Subject: Re: draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
Date: Tue, 09 Nov 2004 07:22:52 -0700
Lines: 196
References: <87AC5F88F03E6249AEA68D40BD3E00BE019BC0F2@zcarhxm2.corp.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "'Thomas D. Nadeau'" <tnadeau@cisco.com>, "'pwe3@ietf.org'" <pwe3@ietf.org>,
	'Sasha Vainshtein' <Sasha@AXERRA.com>, "Singh,
	Hardeep \(Hardeep\)" <hardeep@lucent.com>
X-From: pwe3-bounces@ietf.org Tue Nov 09 15:30:54 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616
X-Accept-Language: Italian [it], French/Canada [fr-CA], French/France [fr-FR],
	English/United States [en-US]
To: David Allan <dallan@nortelnetworks.com>
In-Reply-To: <87AC5F88F03E6249AEA68D40BD3E00BE019BC0F2@zcarhxm2.corp.nortel.com>
X-Scan-Signature: b8f3559805f7873076212d6f63ee803e
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

David Allan wrote:

>Hi Sasha:
>
>We've worked through this in some detail. IMO a split horizon "down" is a
>summarization of AIS/RDI which is hard to go backwards from. Communicating
>directionality covers all cases when considering all the interworking
>possiblities ...including the fact that an ingress PE can also observe
>PW/PSN failures (PING or RSVP patherr)...
>
>rgds
>Dave
>
>
>  
>
So how would a receiving PE detect a Tx PSN error on the transmitting 
side ? ( ex no mpls LSP ? )
So let's say I do not want to use OAM ?

Thanks.
Luca

>
>  
>
>>-----Original Message-----
>>From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On 
>>Behalf Of Sasha Vainshtein
>>Sent: Monday, November 08, 2004 9:31 AM
>>To: 'Thomas D. Nadeau'
>>Cc: Singh, Hardeep (Hardeep); 'pwe3@ietf.org'
>>Subject: RE: [PWE3] draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
>>
>>
>>Tom and all,
>>IMHO one generic status code indicating that 
>>the local AC is down is necessary. 
>>
>>I am not at all sure about the additional refinements.E.g., 
>>if a FR DLCI goes down,would it mean that it has Rx failure 
>>or Tx failure?
>>
>>My 2c.
>>--------------------------------------------------------------
>>--------------
>>--------
>>With best regards,
>>                          Sasha Vainshtein
>>email:   sasha@axerra.com <mailto:sasha@axerra.com> 
>>phone:  +972-3-7659993 (office)
>>            +972-8-9254948 (home)
>>            +972-58-674833 (cellular)
>>
>>
>>    
>>
>>>-----Original Message-----
>>>From: Thomas D. Nadeau [mailto:tnadeau@cisco.com]
>>>Sent: Friday, November 05, 2004 10:52 PM
>>>To: Singh, Hardeep (Hardeep)
>>>Cc: 'pwe3@ietf.org'
>>>Subject: Re: [PWE3] draft-ietf-pwe3-iana-allocation-07.txt 
>>>      
>>>
>>- LAST CALL
>>    
>>
>>>
>>>	I don't think Dave's proposal is to make the others 
>>>      
>>>
>>optional; it was 
>>    
>>
>>>to remove them completely for now.
>>>
>>>	--Tom
>>>
>>>
>>>      
>>>
>>>>I agree. Probably the first two can me made mandatory
>>>>and the rest optional to implement or be decided later.
>>>>
>>>>We too came to the same conclusion when we implemented
>>>>PWE3 circuits as per the draft.
>>>>
>>>>Thanks
>>>>
>>>>Hardeep
>>>>
>>>>-----Original Message-----
>>>>From: pwe3-bounces@ietf.org
>>>>        
>>>>
>>[mailto:pwe3-bounces@ietf.org]On Behalf Of
>>    
>>
>>>David Allan
>>>Sent: Thursday, November 04, 2004 4:51 PM
>>>To: 'pwe3@ietf.org'
>>>Subject: FW: [PWE3] draft-ietf-pwe3-iana-allocation-07.txt 
>>>      
>>>
>>- LAST CALL
>>    
>>
>>>
>>>Hi:
>>>
>>>A number of us have been working on fault notification for PWs, and
>>>have
>>>concluded that we do not need to couple fault direction and fault 
>>>location
>>>the way it is currently defined for the LDP status TLV in the IANA
>>>allocations draft. There is another proposal but it has not 
>>>      
>>>
>>had enough 
>>    
>>
>>>"soak
>>>time" to spring in the middle of a last call.
>>>
>>>Rather than hold up the IANA allocations draft, the suggestion is
>>>simply to
>>>remove the status code points we know we will be revising.
>>>
>>>So keep
>>>       0x00000000 - Pseudo Wire forwarding ( clear all failures )
>>>       0x00000001 - Pseudo Wire Not Forwarding
>>>
>>>And lose
>>>       0x00000002 - Local Attachement Circuit ( ingress ) 
>>>      
>>>
>>Receive Fault
>>    
>>
>>>       0x00000004 - Local Attachement Circuit ( egress ) 
>>>      
>>>
>>Transmit Fault
>>    
>>
>>>       0x00000008 - Local PSN-facing PW ( ingress ) Receive Fault
>>>       0x00000010 - Local PSN-facing PW ( egress ) Transmit Fault
>>>
>>>So the IANA registry entry is set up, and we'll provide the 
>>>      
>>>
>>requisite 
>>    
>>
>>>additional code points when it is pinned down...
>>>
>>>Any objections?
>>>
>>>cheers
>>>Dave
>>>
>>>
>>>_______________________________________________
>>>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
>>
>>_______________________________________________
>>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  Wed Dec 27 15:58:27 2006
From: "David Allan" <dallan@nortelnetworks.com>
Subject: RE: FW: draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
Date: Tue, 9 Nov 2004 09:35:59 -0500
Lines: 85
Cc: "'pwe3@ietf.org'" <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Tue Nov 09 15:49:45 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Luca Martini'" <lmartini@cisco.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


> This is an allocation draft. If you want something different we'll be
> happy to add it.

What I do not want is a plurality of options and complex state handling.

> If somebody wants to use the messages below , there is no way
> to prevent 
> them from allocating these.

Except by deprecating them before they fall into common practice.

> I'm interested in why these are not needed ?

Somthing is needed, but not somthing that bundles direction and location
together.

> There are many PW types that do not have AIS/RDI support....
> How would you have this information propagate ?
> 
> Ex. Frame-relay -> IP -> ATM  ?

How does ATM figure what to send to the FR AC?
How does FR figure what to send to the ATM AC? 

IMO the requirement is to specify common behavior of the IWF so it only
needs to generate one set of fault states, and handle one set of fault
states from the far end PE.

rgds
Dave



> 
> Luca
> 
> 
> David Allan wrote:
> 
> >Hi:
> >
> >A number of us have been working on fault notification for PWs, and
> >have concluded that we do not need to couple fault direction 
> and fault
> >location the way it is currently defined for the LDP status
> TLV in the
> >IANA allocations draft. There is another proposal but it has not had
> >enough "soak time" to spring in the middle of a last call.
> >
> >Rather than hold up the IANA allocations draft, the suggestion is
> >simply to remove the status code points we know we will be revising.
> >
> >So keep
> >       0x00000000 - Pseudo Wire forwarding ( clear all failures )
> >       0x00000001 - Pseudo Wire Not Forwarding
> > 
> >And lose
> >       0x00000002 - Local Attachement Circuit ( ingress )
> Receive Fault
> >       0x00000004 - Local Attachement Circuit ( egress )
> Transmit Fault
> >       0x00000008 - Local PSN-facing PW ( ingress ) Receive Fault
> >       0x00000010 - Local PSN-facing PW ( egress ) Transmit Fault
> >
> >So the IANA registry entry is set up, and we'll provide the
> requisite
> >additional code points when it is pinned down...
> >
> >Any objections?
> >
> >cheers
> >Dave
> > 
> >
> >_______________________________________________
> >pwe3 mailing list
> >pwe3@ietf.org
> >https://www1.ietf.org/mailman/listinfo/pwe3
> >
> >  
> >
> 
> 
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "David Allan" <dallan@nortelnetworks.com>
Subject: RE: draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
Date: Tue, 9 Nov 2004 09:52:55 -0500
Lines: 202
Cc: "'Thomas D. Nadeau'" <tnadeau@cisco.com>, "'pwe3@ietf.org'" <pwe3@ietf.org>,
	'Sasha Vainshtein' <Sasha@AXERRA.com>, "Singh,
	Hardeep \(Hardeep\)" <hardeep@lucent.com>
X-From: pwe3-bounces@ietf.org Tue Nov 09 16:11:25 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Luca Martini'" <lmartini@cisco.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: 88b11fc64c1bfdb4425294ef5374ca07
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Hi Luca:


> So how would a receiving PE detect a Tx PSN error on the transmitting 
> side ? ( ex no mpls LSP ? )
> So let's say I do not want to use OAM ?

If I understand the question correctly, if I am not using BFD or 1711, then
it is likely that the ingress PE may know about a fault before the egress,
if it knows at all (e.g. via RSVP path err or a ping failure). in the
patherr case, it is acutally the protocol semantics that the ingress gets
notified and not the egress. In the ping case, you do not really know what
is broken, so the scenario is more ambiguous...

In that scenario (just about wholly dependent on the control plane), I'd
have to use status TLV to communciate that information from the PW ingress
to the PW egress.

Dave


> 
> Thanks.
> Luca
> 
> >
> >  
> >
> >>-----Original Message-----
> >>From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On
> >>Behalf Of Sasha Vainshtein
> >>Sent: Monday, November 08, 2004 9:31 AM
> >>To: 'Thomas D. Nadeau'
> >>Cc: Singh, Hardeep (Hardeep); 'pwe3@ietf.org'
> >>Subject: RE: [PWE3] draft-ietf-pwe3-iana-allocation-07.txt 
> - LAST CALL
> >>
> >>
> >>Tom and all,
> >>IMHO one generic status code indicating that
> >>the local AC is down is necessary. 
> >>
> >>I am not at all sure about the additional refinements.E.g.,
> >>if a FR DLCI goes down,would it mean that it has Rx failure 
> >>or Tx failure?
> >>
> >>My 2c.
> >>--------------------------------------------------------------
> >>--------------
> >>--------
> >>With best regards,
> >>                          Sasha Vainshtein
> >>email:   sasha@axerra.com <mailto:sasha@axerra.com> 
> >>phone:  +972-3-7659993 (office)
> >>            +972-8-9254948 (home)
> >>            +972-58-674833 (cellular)
> >>
> >>
> >>    
> >>
> >>>-----Original Message-----
> >>>From: Thomas D. Nadeau [mailto:tnadeau@cisco.com]
> >>>Sent: Friday, November 05, 2004 10:52 PM
> >>>To: Singh, Hardeep (Hardeep)
> >>>Cc: 'pwe3@ietf.org'
> >>>Subject: Re: [PWE3] draft-ietf-pwe3-iana-allocation-07.txt
> >>>      
> >>>
> >>- LAST CALL
> >>    
> >>
> >>>
> >>>	I don't think Dave's proposal is to make the others
> >>>      
> >>>
> >>optional; it was
> >>    
> >>
> >>>to remove them completely for now.
> >>>
> >>>	--Tom
> >>>
> >>>
> >>>      
> >>>
> >>>>I agree. Probably the first two can me made mandatory
> >>>>and the rest optional to implement or be decided later.
> >>>>
> >>>>We too came to the same conclusion when we implemented
> >>>>PWE3 circuits as per the draft.
> >>>>
> >>>>Thanks
> >>>>
> >>>>Hardeep
> >>>>
> >>>>-----Original Message-----
> >>>>From: pwe3-bounces@ietf.org
> >>>>        
> >>>>
> >>[mailto:pwe3-bounces@ietf.org]On Behalf Of
> >>    
> >>
> >>>David Allan
> >>>Sent: Thursday, November 04, 2004 4:51 PM
> >>>To: 'pwe3@ietf.org'
> >>>Subject: FW: [PWE3] draft-ietf-pwe3-iana-allocation-07.txt
> >>>      
> >>>
> >>- LAST CALL
> >>    
> >>
> >>>
> >>>Hi:
> >>>
> >>>A number of us have been working on fault notification for 
> PWs, and 
> >>>have concluded that we do not need to couple fault direction and 
> >>>fault location
> >>>the way it is currently defined for the LDP status TLV in the IANA
> >>>allocations draft. There is another proposal but it has not 
> >>>      
> >>>
> >>had enough
> >>    
> >>
> >>>"soak
> >>>time" to spring in the middle of a last call.
> >>>
> >>>Rather than hold up the IANA allocations draft, the suggestion is 
> >>>simply to remove the status code points we know we will be 
> revising.
> >>>
> >>>So keep
> >>>       0x00000000 - Pseudo Wire forwarding ( clear all failures )
> >>>       0x00000001 - Pseudo Wire Not Forwarding
> >>>
> >>>And lose
> >>>       0x00000002 - Local Attachement Circuit ( ingress )
> >>>      
> >>>
> >>Receive Fault
> >>    
> >>
> >>>       0x00000004 - Local Attachement Circuit ( egress )
> >>>      
> >>>
> >>Transmit Fault
> >>    
> >>
> >>>       0x00000008 - Local PSN-facing PW ( ingress ) Receive Fault
> >>>       0x00000010 - Local PSN-facing PW ( egress ) Transmit Fault
> >>>
> >>>So the IANA registry entry is set up, and we'll provide the
> >>>      
> >>>
> >>requisite
> >>    
> >>
> >>>additional code points when it is pinned down...
> >>>
> >>>Any objections?
> >>>
> >>>cheers
> >>>Dave
> >>>
> >>>
> >>>_______________________________________________
> >>>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
> >>
> >>_______________________________________________
> >>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  Wed Dec 27 15:58:27 2006
From: Tim.Frost@Zarlink.Com
Subject: PWE3 Control Protocol Extensions Draft
Date: Tue, 9 Nov 2004 20:47:02 +0000
Lines: 43
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1551052262=="
Cc: Sasha Vainshtein <Sasha@AXERRA.com>
X-From: pwe3-bounces@ietf.org Tue Nov 09 21:51:56 2004
Return-path: <pwe3-bounces@ietf.org>
To: pwe3@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
X-MIMETrack: Serialize by Router on ottmta01/Zarlink(Release 6.5.1|January 21,
	2004) at 11/09/2004 03:47:04 PM,
	Serialize complete at 11/09/2004 03:47:04 PM
X-Scanned-By: MIMEDefang 2.38
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is a multipart message in MIME format.
--===============1551052262==
Content-Type: multipart/alternative;
	boundary="=_alternative 00722B8B80256F47_="

This is a multipart message in MIME format.
--=_alternative 00722B8B80256F47_=
Content-Type: text/plain; charset="us-ascii"

Folks,
Sorry I can't be at the meeting this time to discuss this in person. 
Regarding draft-vainshtein-pwe3-tdm-control-protocol-extensi-01.txt, I 
think this is an important draft for enabling the use of TDM pseudo-wires, 
and would like to see this become a working group draft.
Have a good IETF!
Tim

--=_alternative 00722B8B80256F47_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Folks,</font>
<br><font size=2 face="sans-serif">Sorry I can't be at the meeting this time to discuss this in person. Regarding draft-vainshtein-pwe3-tdm-control-protocol-extensi-01.txt, I think this is an important draft for enabling the use of TDM pseudo-wires, and would like to see this become a working group draft.</font>
<br><font size=2 face="sans-serif">Have a good IETF!</font>
<br><font size=2 face="sans-serif">Tim</font>
<br>
--=_alternative 00722B8B80256F47_=--


--===============1551052262==
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

--===============1551052262==--




From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Luca Martini <lmartini@cisco.com>
Subject: Re: draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
Date: Wed, 10 Nov 2004 07:37:37 -0700
Lines: 285
References: <87AC5F88F03E6249AEA68D40BD3E00BE019BC123@zcarhxm2.corp.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "'Thomas D. Nadeau'" <tnadeau@cisco.com>, "'pwe3@ietf.org'" <pwe3@ietf.org>,
	'Sasha Vainshtein' <Sasha@AXERRA.com>, "Singh,
	Hardeep \(Hardeep\)" <hardeep@lucent.com>
X-From: pwe3-bounces@ietf.org Wed Nov 10 15:49:38 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616
X-Accept-Language: Italian [it], French/Canada [fr-CA], French/France [fr-FR],
	English/United States [en-US]
To: David Allan <dallan@nortelnetworks.com>
In-Reply-To: <87AC5F88F03E6249AEA68D40BD3E00BE019BC123@zcarhxm2.corp.nortel.com>
X-PMX-Version: 4.7.0.111621
X-from-outside-Cisco: [10.32.224.186]
X-Scan-Signature: 7f3fa64b9851a63d7f3174ef64114da7
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Actually in my deployment experience , BFD or 1711 was not needed ( nor 
it existed ), as LDP/OSPF correctly communicated failures even in one 
direction.
The problem I have with you proposed change is that it breaks the 
semantics of this error message. Mainly that is a bit is set , them 
means an error condition. Any bit can be set independently.....
Then all bits can be cleared by sending a 0. To make your proposal work 
we would have to specify that the direction bit is outside this scheme , 
and cannot be sent independently with out an error bit.
Other then saving bits , what is the issue in bundling direction and 
location ?

Thanks.
Luca



David Allan wrote:

>Hi Luca:
>
>
>  
>
>>So how would a receiving PE detect a Tx PSN error on the transmitting 
>>side ? ( ex no mpls LSP ? )
>>So let's say I do not want to use OAM ?
>>    
>>
>
>If I understand the question correctly, if I am not using BFD or 1711, then
>it is likely that the ingress PE may know about a fault before the egress,
>if it knows at all (e.g. via RSVP path err or a ping failure). in the
>patherr case, it is acutally the protocol semantics that the ingress gets
>notified and not the egress. In the ping case, you do not really know what
>is broken, so the scenario is more ambiguous...
>
>In that scenario (just about wholly dependent on the control plane), I'd
>have to use status TLV to communciate that information from the PW ingress
>to the PW egress.
>
>Dave
>
>
>  
>
>>Thanks.
>>Luca
>>
>>    
>>
>>> 
>>>
>>>      
>>>
>>>>-----Original Message-----
>>>>From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On
>>>>Behalf Of Sasha Vainshtein
>>>>Sent: Monday, November 08, 2004 9:31 AM
>>>>To: 'Thomas D. Nadeau'
>>>>Cc: Singh, Hardeep (Hardeep); 'pwe3@ietf.org'
>>>>Subject: RE: [PWE3] draft-ietf-pwe3-iana-allocation-07.txt 
>>>>        
>>>>
>>- LAST CALL
>>    
>>
>>>>Tom and all,
>>>>IMHO one generic status code indicating that
>>>>the local AC is down is necessary. 
>>>>
>>>>I am not at all sure about the additional refinements.E.g.,
>>>>if a FR DLCI goes down,would it mean that it has Rx failure 
>>>>or Tx failure?
>>>>
>>>>My 2c.
>>>>--------------------------------------------------------------
>>>>--------------
>>>>--------
>>>>With best regards,
>>>>                         Sasha Vainshtein
>>>>email:   sasha@axerra.com <mailto:sasha@axerra.com> 
>>>>phone:  +972-3-7659993 (office)
>>>>           +972-8-9254948 (home)
>>>>           +972-58-674833 (cellular)
>>>>
>>>>
>>>>   
>>>>
>>>>        
>>>>
>>>>>-----Original Message-----
>>>>>From: Thomas D. Nadeau [mailto:tnadeau@cisco.com]
>>>>>Sent: Friday, November 05, 2004 10:52 PM
>>>>>To: Singh, Hardeep (Hardeep)
>>>>>Cc: 'pwe3@ietf.org'
>>>>>Subject: Re: [PWE3] draft-ietf-pwe3-iana-allocation-07.txt
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>- LAST CALL
>>>>   
>>>>
>>>>        
>>>>
>>>>>	I don't think Dave's proposal is to make the others
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>optional; it was
>>>>   
>>>>
>>>>        
>>>>
>>>>>to remove them completely for now.
>>>>>
>>>>>	--Tom
>>>>>
>>>>>
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>>>I agree. Probably the first two can me made mandatory
>>>>>>and the rest optional to implement or be decided later.
>>>>>>
>>>>>>We too came to the same conclusion when we implemented
>>>>>>PWE3 circuits as per the draft.
>>>>>>
>>>>>>Thanks
>>>>>>
>>>>>>Hardeep
>>>>>>
>>>>>>-----Original Message-----
>>>>>>From: pwe3-bounces@ietf.org
>>>>>>       
>>>>>>
>>>>>>            
>>>>>>
>>>>[mailto:pwe3-bounces@ietf.org]On Behalf Of
>>>>   
>>>>
>>>>        
>>>>
>>>>>David Allan
>>>>>Sent: Thursday, November 04, 2004 4:51 PM
>>>>>To: 'pwe3@ietf.org'
>>>>>Subject: FW: [PWE3] draft-ietf-pwe3-iana-allocation-07.txt
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>- LAST CALL
>>>>   
>>>>
>>>>        
>>>>
>>>>>Hi:
>>>>>
>>>>>A number of us have been working on fault notification for 
>>>>>          
>>>>>
>>PWs, and 
>>    
>>
>>>>>have concluded that we do not need to couple fault direction and 
>>>>>fault location
>>>>>the way it is currently defined for the LDP status TLV in the IANA
>>>>>allocations draft. There is another proposal but it has not 
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>had enough
>>>>   
>>>>
>>>>        
>>>>
>>>>>"soak
>>>>>time" to spring in the middle of a last call.
>>>>>
>>>>>Rather than hold up the IANA allocations draft, the suggestion is 
>>>>>simply to remove the status code points we know we will be 
>>>>>          
>>>>>
>>revising.
>>    
>>
>>>>>So keep
>>>>>      0x00000000 - Pseudo Wire forwarding ( clear all failures )
>>>>>      0x00000001 - Pseudo Wire Not Forwarding
>>>>>
>>>>>And lose
>>>>>      0x00000002 - Local Attachement Circuit ( ingress )
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>Receive Fault
>>>>   
>>>>
>>>>        
>>>>
>>>>>      0x00000004 - Local Attachement Circuit ( egress )
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>Transmit Fault
>>>>   
>>>>
>>>>        
>>>>
>>>>>      0x00000008 - Local PSN-facing PW ( ingress ) Receive Fault
>>>>>      0x00000010 - Local PSN-facing PW ( egress ) Transmit Fault
>>>>>
>>>>>So the IANA registry entry is set up, and we'll provide the
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>requisite
>>>>   
>>>>
>>>>        
>>>>
>>>>>additional code points when it is pinned down...
>>>>>
>>>>>Any objections?
>>>>>
>>>>>cheers
>>>>>Dave
>>>>>
>>>>>
>>>>>_______________________________________________
>>>>>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
>>>>
>>>>_______________________________________________
>>>>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  Wed Dec 27 15:58:27 2006
From: "David Allan" <dallan@nortelnetworks.com>
Subject: RE: draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
Date: Wed, 10 Nov 2004 11:34:01 -0500
Lines: 49
Cc: "'Thomas D. Nadeau'" <tnadeau@cisco.com>, "'pwe3@ietf.org'" <pwe3@ietf.org>,
	'Sasha Vainshtein' <Sasha@AXERRA.com>, "Singh,
	Hardeep \(Hardeep\)" <hardeep@lucent.com>
X-From: pwe3-bounces@ietf.org Wed Nov 10 17:45:32 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Luca Martini'" <lmartini@cisco.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


> Actually in my deployment experience , BFD or 1711 was not 
> needed ( nor 
> it existed ), as LDP/OSPF correctly communicated failures even in one 
> direction.

Not sure where the linkage to BFD & 1711 comes from. Its status TLV being
discussed.

> The problem I have with you proposed change is that it breaks the 
> semantics of this error message. Mainly that is a bit is set , them 
> means an error condition. Any bit can be set 
> independently..... Then all bits can be cleared by sending a 
> 0. To make your proposal work 
> we would have to specify that the direction bit is outside 
> this scheme , and cannot be sent independently with out an error bit.

Correct, 0 is still a "tracks are clear" indication. For those outside some
of the private exchanges, the suggested bits are:

      0x00000000 - Pseudo Wire forwarding ( clear all failures )
      0x00000001 - Pseudo Wire Not Forwarding (fault state)
 	0x00000002 - Pseudo wire administrative down
      0x00000004 - Fault direction (0=forward, 1= reverse)
      0x00000008 - Fault location (0 = PW, 1 = AC)

And Luca is correct in noting that there are invalid combinations. aka 4 or
8 in isolation. ALso forward has precedence over reverse, and PW has
precedence over AC.

> 
> Other then saving bits , what is the issue in bundling direction and 
> location ?

No real need to communicate detail in multiple fault scenarios, only the
presence of a fault. What the state machines are interested in is presence
of a fault and direction. Location does not matter as far as handling is
concerned, but we've agreed it is useful information, so lumping them
together is simply confusing and IMO obligates implementations to use
multiple messages in multiple fault scenarios. For example an AC receive
fault and a PW transmit fault would require precisely the same actions at
the receiving PE, if I've already got one I do not need to do anything
further, yet to be consistent it would require multiple status messages if
one happened, and then the other happened before the first cleared. I am
downloading fault clearing decisions to the PE receiving status information
by sending it IMO redundant information.

rgds
Dave


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "David Allan" <dallan@nortelnetworks.com>
Subject: RE: draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
Date: Wed, 10 Nov 2004 11:56:42 -0500
Lines: 24
Cc: "'Thomas D. Nadeau'" <tnadeau@cisco.com>, "'pwe3@ietf.org'" <pwe3@ietf.org>,
	'Sasha Vainshtein' <Sasha@AXERRA.com>, "Singh,
	Hardeep \(Hardeep\)" <hardeep@lucent.com>
X-From: pwe3-bounces@ietf.org Wed Nov 10 18:20:53 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Luca Martini'" <lmartini@cisco.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Hi Again

> Other then saving bits , what is the issue in bundling direction and 
> location ?

A more precise rephrasing of my response to this would be that we have two
choices....

1) We can diseminate all information and then define rules for how each node
interprets that information (PMO) OR

2) We can define rules as to what information is important, and only
communicate that (Proposed FMO)

As there is a time component, the completeness of the information will vary
over time, so if we assume we always distribute  all information, it will
require more messages to keep the nodes in synch. If we define rules as to
what information is important and rules of precedence, we can summarize and
not need to communicate changes that will not alter state.

So it is not about saving bits, it is about saving messages...

cheers
Dave


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
Date: Thu, 11 Nov 2004 17:36:44 +0200
Lines: 184
Mime-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-cf53437c-bc8b-45b5-a01a-486e7669ebf8"
Cc: "'Thomas D. Nadeau'" <tnadeau@cisco.com>,
	'Luca Martini' <lmartini@cisco.com>,
	"'pwe3@ietf.org'" <pwe3@ietf.org>, "Singh,
	Hardeep \(Hardeep\)" <hardeep@lucent.com>
X-From: pwe3-bounces@ietf.org Thu Nov 11 16:57:10 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'David Allan'" <dallan@nortelnetworks.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------=_NextPartTM-000-cf53437c-bc8b-45b5-a01a-486e7669ebf8
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C804.3F91A330"

------_=_NextPart_001_01C4C804.3F91A330
Content-Type: text/plain;
	charset="iso-8859-1"

Dave and all,
Please look at a short question/comment inline.
 
----------------------------------------------------------------------------
--------
With best regards,
                          Sasha Vainshtein
email:   sasha@axerra.com <mailto:sasha@axerra.com> 
phone:  +972-3-7659993 (office)
            +972-8-9254948 (home)
            +972-58-674833 (cellular)

-----Original Message-----
From: David Allan [mailto:dallan@nortelnetworks.com]
Sent: Wednesday, November 10, 2004 6:57 PM
To: 'Luca Martini'
Cc: 'Thomas D. Nadeau'; 'pwe3@ietf.org'; Sasha Vainshtein; Singh, Hardeep
(Hardeep)
Subject: RE: [PWE3] draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL



Hi Again 

> Other then saving bits , what is the issue in bundling direction and 
> location ? 

A more precise rephrasing of my response to this would be that we have two
choices.... 

1) We can diseminate all information and then define rules for how each node
interprets that information (PMO) OR 

2) We can define rules as to what information is important, and only
communicate that (Proposed FMO) 

As there is a time component, the completeness of the information will vary
over time, so if we assume we always distribute  all information, it will
require more messages to keep the nodes in synch. If we define rules as to
what information is important and rules of precedence, we can summarize and
not need to communicate changes that will not alter state.
[[Sasha]] This assumes that while more information can be generated in
future, we have complete and final knowledge of what is need NOW.  I have
serious doubts regarding validity of such an assumption per se. (indeed,it
if were true, why should new information any be generated? just for fun?) So
Option 1 with  minimal content defined today and an  ability to extend this
content as needed (like the existing processes of IANA allocating new code
points etc.) looks more robust to me.

So it is not about saving bits, it is about saving messages... 

cheers 
Dave 


------_=_NextPart_001_01C4C804.3F91A330
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>RE: [PWE3] draft-ietf-pwe3-iana-allocation-07.txt - LAST =
CALL</TITLE>

<META content=3D"MSHTML 6.00.2800.1476" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D846053315-11112004>Dave=20
and all,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D846053315-11112004>Please=20
look at a short question/comment inline.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial=20
size=3D2>---------------------------------------------------------------=
---------------------</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>With best regards,</FONT></DIV>
<DIV dir=3Dltr align=3Dright><FONT face=3D"Arial (Hebrew)"=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
Sasha Vainshtein</FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3D"Arial (Hebrew)" =
size=3D2>email:&nbsp;&nbsp; <A=20
href=3D"mailto:sasha@axerra.com">sasha@axerra.com</A></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3D"Arial (Hebrew)" =
size=3D2>phone:&nbsp;=20
+972-3-7659993 (office)</FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3D"Arial (Hebrew)"=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
+972-8-9254948 (home)</FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3D"Arial (Hebrew)"=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
+972-58-674833 (cellular)</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> David Allan=20
  [mailto:dallan@nortelnetworks.com]<BR><B>Sent:</B> Wednesday, =
November 10,=20
  2004 6:57 PM<BR><B>To:</B> 'Luca Martini'<BR><B>Cc:</B> 'Thomas D. =
Nadeau';=20
  'pwe3@ietf.org'; Sasha Vainshtein; Singh, Hardeep =
(Hardeep)<BR><B>Subject:</B>=20
  RE: [PWE3] draft-ietf-pwe3-iana-allocation-07.txt - LAST=20
  CALL<BR><BR></FONT></DIV>
  <P><FONT size=3D2>Hi Again</FONT> </P>
  <P><FONT size=3D2>&gt; Other then saving bits , what is the issue in =
bundling=20
  direction and </FONT><BR><FONT size=3D2>&gt; location ?</FONT> </P>
  <P><FONT size=3D2>A more precise rephrasing of my response to this =
would be that=20
  we have two choices....</FONT> </P>
  <P><FONT size=3D2>1) We can diseminate all information and then =
define rules for=20
  how each node interprets that information (PMO) OR</FONT> </P>
  <P><FONT size=3D2>2) We can define rules as to what information is =
important,=20
  and only communicate that (Proposed FMO)</FONT> </P>
  <P><FONT size=3D2>As there is a time component, the completeness of =
the=20
  information will vary over time, so if we assume we always =
distribute&nbsp;=20
  all information, it will require more messages to keep the nodes in =
synch. If=20
  we define rules as to what information is important and rules of =
precedence,=20
  we can summarize and not need to communicate changes that will not =
alter=20
  state.<BR><SPAN class=3D846053315-11112004><FONT face=3DArial=20
  color=3D#0000ff>[[Sasha]]&nbsp;This assumes that while more =
information can be=20
  generated in future, <STRONG>we have complete and final knowledge of=20
  what&nbsp;is need NOW</STRONG>.&nbsp;&nbsp;I have serious doubts =
regarding=20
  validity of such an assumption <EM>per se</EM>. (indeed,it if were =
true, why=20
  should new information any be generated? just for fun?) So Option 1 =
with&nbsp;=20
  minimal content defined today and an&nbsp; ability to extend this =
content as=20
  needed (like the existing processes of IANA allocating new code =
points etc.)=20
  looks more robust to me.</FONT></SPAN></FONT></P>
  <P><FONT size=3D2>So it is not about saving bits, it is about saving=20
  messages...</FONT> </P>
  <P><FONT size=3D2>cheers</FONT> <BR><FONT size=3D2>Dave</FONT>=20
</P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C4C804.3F91A330--

------=_NextPartTM-000-cf53437c-bc8b-45b5-a01a-486e7669ebf8
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

------=_NextPartTM-000-cf53437c-bc8b-45b5-a01a-486e7669ebf8--





From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "David Allan" <dallan@nortelnetworks.com>
Subject: RE: draft-ietf-pwe3-iana-allocation-07.txt - LAST CALL
Date: Thu, 11 Nov 2004 10:59:09 -0500
Lines: 44
Cc: "'Thomas D. Nadeau'" <tnadeau@cisco.com>,
	'Luca Martini' <lmartini@cisco.com>,
	"'pwe3@ietf.org'" <pwe3@ietf.org>, "Singh,
	Hardeep \(Hardeep\)" <hardeep@lucent.com>
X-From: pwe3-bounces@ietf.org Thu Nov 11 17:09:16 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Sasha Vainshtein'" <Sasha@AXERRA.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Hi Sasha:

>> A more precise rephrasing of my response to this would be that we have
two choices.... 

>> 1) We can diseminate all information and then define rules for how each
node interprets that information (PMO) OR 
>> 2) We can define rules as to what information is important, and only
communicate that (Proposed FMO) 

>> As there is a time component, the completeness of the information will
vary over time, so if we assume we always 
>> distribute  all information, it will require more messages to keep the
nodes in synch. If we define rules as to what 
>> information is important and rules of precedence, we can summarize and
not need to communicate changes that will not
>> alter state.

[[Sasha]] This assumes that while more information can be generated in
future, we have complete and final knowledge of what is need NOW.  I have
serious doubts regarding validity of such an assumption per se. (indeed,it
if were true, why should new information any be generated? just for fun?) So
Option 1 with  minimal content defined today and an  ability to extend this
content as needed (like the existing processes of IANA allocating new code
points etc.) looks more robust to me. 

[Dave] Taken to its logical conclusion, we need a link state routing
protocol at the PW layer than spans multiple technologies.  In essence the
defined values now are a trivialized link state for a trivial topology,
which being a bitmap has extensibility limits as we need more bits/bytes for
every link/fault/metric we introduce. IMO for a VPWS (P2P service) this far
exceeds the requisite information for interworking with the legacy
technologies under consideration (and I mentally enlarge the set to include
PDH, AAL2 yadda yadda).

The actions required by the "interworked with" technologies only really need
to know of the presence of a fault and direction and that it wass not in
their backyard. Shovelling more information around the network IMO is
superfluous and unnecessary loading of the control plane. That stuff needs
to be handed off to management by the node that originates the notification
for proper trouble ticketing. 

rgds
Dave 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Danny McPherson <danny@tcb.net>
Subject: Updated Agenda
Date: Thu, 11 Nov 2004 11:09:59 -0700
Lines: 30
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-bounces@ietf.org Thu Nov 11 19:17:11 2004
Return-path: <pwe3-bounces@ietf.org>
To: pwe3@ietf.org
X-Mailer: Apple Mail (2.619)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


PWE3 -- IETF 61
THURSDAY, November 11, 2004

Chairs:
   Stewart Bryant <stbryant@cisco.com>
   Danny McPherson <danny@tcb.net>


1530-1730 Afternoon Session II; Lincoln East

  o Administrivia (5 minutes)
    - Agenda
    - Blue Sheets
    - Minutes
  o Charter & Draft Status - Stewart & Danny (25 minutes)
  o PW CW - Stewart & Danny (5 minutes)
     http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw-00.txt
  o UDP Statement to ITU - Stewart (10 minutes)
  o UDP Encapsulation - Yaakov Stein (15 minutes)
     Discussion: The application has to be described more carefully,
     in order not to imply that we are suggesting UDP instead of MPLS
     inside a service provider's network.  A few slides to illustrate
     that UDP is a sensible solution for CE-CE emulation for the
     enterprise space.  Also intend to address security and
     congestion implications.
  o PW Multi-Hop Requirements - Luca Martini (10 minutes)
  o PW Stitching - Dimitri Papadimitriou (10 minutes)
  o Open Microphone
  o Wrap-Up (5 minutes)


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Luca Martini <lmartini@cisco.com>
Subject: Title for encapsulation Drafts.
Date: Thu, 11 Nov 2004 14:06:40 -0700
Lines: 22
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-bounces@ietf.org Thu Nov 11 22:22:35 2004
Return-path: <pwe3-bounces@ietf.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616
X-Accept-Language: Italian [it], French/Canada [fr-CA], French/France [fr-FR],
	English/United States [en-US]
To: pwe3 <pwe3@ietf.org>
X-PMX-Version: 4.7.0.111621
X-from-outside-Cisco: [10.32.224.186]
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

It was brought to my attention,in the pwe3 meeting, that
The Title of the encapsulations drafts is not consistent across 
different documents.
The most common is "Blah over IP/MPLS Networks".

Example:
"Encapsulation Methods for Transport of Ethernet Frames Over IP/MPLS Network
s"

One suggestion is to change this to Blah over PSN. However this will 
probably not pass the IESG review as it not a well known acronym , and 
it cannot be expanded. ( or at least I believe so )

The true representation is Blah over MPLS ....
This is short and to the point , so  I propose that except for the TDM 
drafts , we change all the titles to this format.


Any other suggestions on how to proceed ?

Thanks.
Luca


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: Usage of UDP ports for CESoPSN
Date: Thu, 11 Nov 2004 23:00:13 +0200
Lines: 31
Mime-Version: 1.0
Content-Type: text/plain;
	charset="windows-1255"
Cc: "Yaakov Stein \(E-mail\)" <yaakov_s@rad.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Thu Nov 11 22:27:02 2004
Return-path: <pwe3-bounces@ietf.org>
To: "Stewart Bryant (E-mail)" <stbryant@cisco.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Stewart and all,
Please look at the following quote from Section 4.2 of
draft-ietf-pwe3-cesopsn-01.txt:
<quote>
	Usage of UDP as the multiplexing mechanism is compliant with the 
	traditional method used for multiplexing RTP flows, e.g.: 
 
	1. Each PE: 
	    a) Allocates one of the PE own IP addresses and a single UDP
port 
	       for each local PW end point (CESoPSN IWF instance)  
	    b) Is aware (by configuration or via a signaling protocol) of
the 
	       similar allocations associated with the remote peer PW end 
	       points 
	2. Each CESoPSN IWF instance uses the associated locally and
remotely 
	   allocated UDP ports as correspondingly the Source and Destination

	   UDP ports in all the CESoPSN packets its generates. 
<end quote>

Hopefully this is sufficiently unambiguous.
----------------------------------------------------------------------------
--------
With best regards,
                          Sasha Vainshtein
email:   sasha@axerra.com
phone:  +972-3-7659993 (office)
            +972-8-9254948 (home)
            +972-58-674833 (cellular)


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "W. Mark Townsley" <townsley@cisco.com>
Subject: Re: Title for encapsulation Drafts.
Date: Thu, 11 Nov 2004 16:25:42 -0500
Lines: 39
References: <4193D460.9040903@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pwe3 <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Thu Nov 11 22:48:02 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7) Gecko/20040616
X-Accept-Language: en-us, en
To: Luca Martini <lmartini@cisco.com>
In-Reply-To: <4193D460.9040903@cisco.com>
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org



Luca Martini wrote:

> It was brought to my attention,in the pwe3 meeting, that
> The Title of the encapsulations drafts is not consistent across 
> different documents.
> The most common is "Blah over IP/MPLS Networks".
> 
> Example:
> "Encapsulation Methods for Transport of Ethernet Frames Over IP/MPLS 
> Network
> s"
> 
> One suggestion is to change this to Blah over PSN. However this will 
> probably not pass the IESG review as it not a well known acronym , and 
> it cannot be expanded. ( or at least I believe so )
> 
> The true representation is Blah over MPLS ....

This sounds good to me. The Blah over L2TPv3 documents exist in l2tpext anyway.

- Mark

> This is short and to the point , so  I propose that except for the TDM 
> drafts , we change all the titles to this format.
> 
> 
> Any other suggestions on how to proceed ?
> 
> Thanks.
> Luca
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: ITU-T UDP liason
Date: Thu, 11 Nov 2004 23:14:22 +0000
Lines: 29
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-bounces@ietf.org Fri Nov 12 00:21:36 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: pwe3 <pwe3@ietf.org>, Thomas Narten <narten@us.ibm.com>,
	"'danny@tcb.net'" <danny@tcb.net>
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Having discussed the ITU-T UDP liaison at today's
PWE3 IETF meeting, here is the text of
the response that we agreed at the meeting.

Please comment ASAP as the chairs need to initiate
the formal response process Tuesday 16th November.

Stewart


-----------------------------------------------

Having considered the liaison from ITU-T Q5/13
to IETF PWE3 WG entitled "Using UDP port numbers
as connection de-multiplexers"

http://www.ietf.org/IESG/LIAISON/file21.pdf

The IETF PWE3 WG recommends that both source
and destination UDP ports be user configured.

If the ITU-T Study Group needs to use a signaled
IP tunnel protocol in this application, then the
IETF PWE3 WG recommends the use Layer Two
Tunneling Protocol (Version 3), which will be
published as RFC3931. The latest draft of this
is currently located at:

http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-l2tp-base-14.txt


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: ITU-T UDP liason
Date: Fri, 12 Nov 2004 02:24:04 +0200
Lines: 23
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-bounces@ietf.org Fri Nov 12 01:29:09 2004
Return-path: <pwe3-bounces@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] ITU-T UDP liason
Thread-Index: AcTIRQvlvD/B6/0OSJmfFpL94VNw/gACIhsg
To: "Stewart Bryant" <stbryant@cisco.com>, "pwe3" <pwe3@ietf.org>,
	"Thomas Narten" <narten@us.ibm.com>, <danny@tcb.net>
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: quoted-printable
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

=20
> Having considered the liaison from ITU-T Q5/13 to IETF PWE3=20
> WG entitled "Using UDP port numbers as connection de-multiplexers"
>=20
> http://www.ietf.org/IESG/LIAISON/file21.pdf
>=20
> The IETF PWE3 WG recommends that both source and destination=20
> UDP ports be user configured.
>=20
> If the ITU-T Study Group needs to use a signaled IP tunnel=20
> protocol in this application, then the IETF PWE3 WG=20
> recommends the use Layer Two Tunneling Protocol (Version 3),=20
> which will be published as RFC3931. The latest draft of this=20
> is currently located at:
>=20
>
http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-l2tp-base-14.txt

In general it sounds good.

Do we want "manually configured" instead of "user configured" ?

Y(J)S


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: CW and frag drafts
Date: Fri, 12 Nov 2004 02:35:55 +0200
Lines: 117
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0845249409=="
Cc: pwe3 <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Fri Nov 12 01:42:15 2004
Return-path: <pwe3-bounces@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
Thread-Topic: CW and frag drafts
Thread-Index: AcTIT5IdjeBeaXTpT3i+D5M3pZBd6w==
To: "Stewart Bryant" <stbryant@cisco.com>
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0845249409==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C84F.8D4E5973"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4C84F.8D4E5973
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Stewart,=20

I noticed that the CW draft lists the FRG draft as non-normative,
and that the dependency of the CW draft on the FRG one
is only to subsection 4.1 of the latter.

Since the FRG draft defines the use of the bits,
it should actually be normative, as the meaning of these
bits is otherwise not understood.

Wouldn't it be simpler to paste the relevant wording
from subsection 4.1 into the CW draft,=20
thus both making the FRG draft truly non-normative,=20
and placing more of the CW description in one place ?

(For that matter we could also repeat the sequence number
processing, and make it entirely self-contained.)

Y(J)S



------_=_NextPart_001_01C4C84F.8D4E5973
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7226.0">
<TITLE>CW and frag drafts</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Stewart, =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">I =
noticed that the CW draft lists the FRG draft as =
non-normative,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">and that =
the dependency of the CW draft on the FRG one</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">is only =
to subsection 4.1 of the latter.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Since =
the FRG draft defines the use of the bits,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">it =
should actually be normative, as the meaning of these</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">bits is =
otherwise not understood.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Wouldn't =
it be simpler to paste the relevant wording</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">from =
subsection 4.1 into the CW draft, </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">thus =
both making the FRG draft truly non-normative, </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">and =
placing more of the CW description in one place ?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">(For =
that matter we could also repeat the sequence number</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">processing, and make it entirely =
self-contained.)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Y(J)S</FONT></SPAN></P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C4C84F.8D4E5973--


--===============0845249409==
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

--===============0845249409==--




From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: PW associated channel
Date: Fri, 12 Nov 2004 03:21:26 +0200
Lines: 127
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0962608190=="
X-From: pwe3-bounces@ietf.org Fri Nov 12 02:45:28 2004
Return-path: <pwe3-bounces@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
Thread-Topic: PW associated channel
Thread-Index: AcTIUhkiUMDAYDGpSoqtf3lVghrq5gAA8pmw
To: "pwe3" <pwe3@ietf.org>
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0962608190==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C855.E9660DC9"

This is a multi-part message in MIME format.

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


> Stewart,=20
>=20
> Is the so called "PW associated channel" limited to OAM?
>=20
> If so, could we call it an "embedded operations channel" (EOC) ?
>=20
> If not, we could try calling it a subflow of the PW.
>=20
> Finally, if we continue to call it a channel
> (and I am not sure I like "PW associated", since it is not
> a separate channel associated with the PW, it is actually
> a subchannel of the PW since it goes under the PW label,
> and is identified by nibble which is under the scope of the PW),
> we could say
>=20
> "Please note that the use of the term "channel" here bears
> no relation to the term "PWE channel types" used in subsection 5.1.2
> of [ARCH]".
>=20
> Y(J)S
>=20
>=20
>=20

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7226.0">
<TITLE> PW associated channel</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Stewart, =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Is the =
so called &quot;PW associated channel&quot; limited to =
OAM?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">If so, =
could we call it an &quot;embedded operations channel&quot; (EOC) =
?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">If not, =
we could try calling it a subflow of the PW.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Finally, =
if we continue to call it a channel</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">(and I =
am not sure I like &quot;PW associated&quot;, since it is =
not</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">a =
separate channel associated with the PW, it is =
actually</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">a =
subchannel of the PW since it goes under the PW label,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">and is =
identified by nibble which is under the scope of the =
PW),</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">we could =
say</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&quot;Please note that the use of the term =
&quot;channel&quot; here bears</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">no =
relation to the term &quot;PWE channel types&quot; used in subsection =
5.1.2</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">of =
[ARCH]&quot;.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Y(J)S</FONT></SPAN></P>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C4C855.E9660DC9--


--===============0962608190==
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

--===============0962608190==--




From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: ITU-T UDP liason
Date: Fri, 12 Nov 2004 02:38:47 +0000
Lines: 6
References: <27A0F290348F8E45AEF79889DDE65A5203455F34@exrad2.ad.rad.co.il>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Thomas Narten <narten@us.ibm.com>, pwe3 <pwe3@ietf.org>, danny@tcb.net
X-From: pwe3-bounces@ietf.org Fri Nov 12 03:42:08 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: Yaakov Stein <yaakov_s@rad.com>
In-Reply-To: <27A0F290348F8E45AEF79889DDE65A5203455F34@exrad2.ad.rad.co.il>
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


> Do we want "manually configured" instead of "user configured" ?

user would be better.

Stewart


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Adrian Farrel" <adrian@olddog.co.uk>
Subject: Re: ITU-T UDP liason
Date: Fri, 12 Nov 2004 04:30:13 -0000
Lines: 43
References: <4193F24E.5080209@cisco.com>
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-From: pwe3-bounces@ietf.org Fri Nov 12 05:38:29 2004
Return-path: <pwe3-bounces@ietf.org>
To: "Stewart Bryant" <stbryant@cisco.com>, "pwe3" <pwe3@ietf.org>
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-OriginalArrivalTime: 12 Nov 2004 04:29:39.0951 (UTC)
	FILETIME=[397B97F0:01C4C870]
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Suggest "wants" not "needs".
None of us needs to do any of this.

Change "recommends the use Layer Two" to "recommends the use of the Layer Two"

Adrian

----- Original Message ----- 
From: "Stewart Bryant" <stbryant@cisco.com>
To: "pwe3" <pwe3@ietf.org>; "Thomas Narten" <narten@us.ibm.com>; <danny@tcb.net>
Sent: Thursday, November 11, 2004 11:14 PM
Subject: [PWE3] ITU-T UDP liason


> Having discussed the ITU-T UDP liaison at today's
> PWE3 IETF meeting, here is the text of
> the response that we agreed at the meeting.
> 
> Please comment ASAP as the chairs need to initiate
> the formal response process Tuesday 16th November.
> 
> Stewart
> 
> 
> -----------------------------------------------
> 
> Having considered the liaison from ITU-T Q5/13
> to IETF PWE3 WG entitled "Using UDP port numbers
> as connection de-multiplexers"
> 
> http://www.ietf.org/IESG/LIAISON/file21.pdf
> 
> The IETF PWE3 WG recommends that both source
> and destination UDP ports be user configured.
> 
> If the ITU-T Study Group needs to use a signaled
> IP tunnel protocol in this application, then the
> IETF PWE3 WG recommends the use Layer Two
> Tunneling Protocol (Version 3), which will be
> published as RFC3931. The latest draft of this
> is currently located at:
> 
> http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-l2tp-base-14.txt


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: ESAKA Naoki <esaka@isl.rdc.toshiba.co.jp>
Subject: Re: ITU-T UDP liason
Date: Fri, 12 Nov 2004 19:21:21 +0900
Lines: 58
References: <4193F24E.5080209@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: narten@us.ibm.com, pwe3@ietf.org, danny@tcb.net
X-From: pwe3-bounces@ietf.org Fri Nov 12 11:23:07 2004
Return-path: <pwe3-bounces@ietf.org>
To: Stewart Bryant <stbryant@cisco.com>
In-Reply-To: <4193F24E.5080209@cisco.com>
X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; i386--netbsdelf)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Hi all,

Doesn't ITU care about that we actually recommend two type
of data plane format(PW over UDP/IP, PW over L2TPv3/UDP/IP)?
I think it may cause confusion.  How about suggesting
manually configured L2TPv3/UDP/IP tunnel(L2TPv3 with no singnalling)
as well as configured UDP ports.


On Thu, 11 Nov 2004 23:14:22 +0000
Stewart Bryant <stbryant@cisco.com> wrote:

> Having discussed the ITU-T UDP liaison at today's
> PWE3 IETF meeting, here is the text of
> the response that we agreed at the meeting.
> 
> Please comment ASAP as the chairs need to initiate
> the formal response process Tuesday 16th November.
> 
> Stewart
> 
> 
> -----------------------------------------------
> 
> Having considered the liaison from ITU-T Q5/13
> to IETF PWE3 WG entitled "Using UDP port numbers
> as connection de-multiplexers"
> 
> http://www.ietf.org/IESG/LIAISON/file21.pdf
> 
> The IETF PWE3 WG recommends that both source
> and destination UDP ports be user configured.
> 
> If the ITU-T Study Group needs to use a signaled
> IP tunnel protocol in this application, then the
> IETF PWE3 WG recommends the use Layer Two
> Tunneling Protocol (Version 3), which will be
> published as RFC3931. The latest draft of this
> is currently located at:
> 
> http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-l2tp-base-14.txt
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3

-- 
ESAKA Naoki <esaka@isl.rdc.toshiba.co.jp>
Communication Platform Laboratory          Phone: +81-44-549-2230
Corporate Research and Development Center  Fax:   +81-44-520-1806
TOSHIBA Corporation


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: PW associated channel
Date: Fri, 12 Nov 2004 02:54:00 +0200
Lines: 125
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0545705784=="
X-From: pwe3-bounces@ietf.org Fri Nov 12 15:01:13 2004
Return-path: <pwe3-bounces@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
Thread-Topic: PW associated channel
Thread-Index: AcTIUhkiUMDAYDGpSoqtf3lVghrq5g==
To: "Stewart Bryant" <stbryant@cisco.com>
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
X-Mailman-Approved-At: Fri, 12 Nov 2004 08:58:05 -0500
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0545705784==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C852.1453404E"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4C852.1453404E
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Stewart,=20

Is the so called "PW associated channel" limited to OAM?

If so, could we call it an "embedded operations channel" (EOC) ?

If not, we could try calling it a subflow of the PW.

Finally, if we continue to call it a channel
(and I am not sure I like "PW associated", since it is not
a separate channel associated with the PW, it is actually
a subchannel of the PW since it goes under the PW label,
and is identified by nibble which is under the scope of the PW),
we could say

"Please note that the use of the term "channel" here bears
no relation to the term "PWE channel types" used in subsection 5.1.2
of [ARCH]".

Y(J)S




------_=_NextPart_001_01C4C852.1453404E
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7226.0">
<TITLE>PW associated channel</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Stewart, =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Is the =
so called &quot;PW associated channel&quot; limited to =
OAM?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">If so, =
could we call it an &quot;embedded operations channel&quot; (EOC) =
?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">If not, =
we could try calling it a subflow of the PW.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Finally, =
if we continue to call it a channel</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">(and I =
am not sure I like &quot;PW associated&quot;, since it is =
not</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">a =
separate channel associated with the PW, it is =
actually</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">a =
subchannel of the PW since it goes under the PW label,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">and is =
identified by nibble which is under the scope of the =
PW),</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">we could =
say</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&quot;Please note that the use of the term =
&quot;channel&quot; here bears</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">no =
relation to the term &quot;PWE channel types&quot; used in subsection =
5.1.2</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">of =
[ARCH]&quot;.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Y(J)S</FONT></SPAN></P>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C4C852.1453404E--


--===============0545705784==
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

--===============0545705784==--




From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Andrew G. Malis" <andymalis@comcast.net>
Subject: Re: CW and frag drafts
Date: Fri, 12 Nov 2004 09:13:02 -0500
Lines: 47
References: <27A0F290348F8E45AEF79889DDE65A5203455F3A@exrad2.ad.rad.co.il> <27A0F290348F8E45AEF79889DDE65A5203455F3A@exrad2.ad.rad.co.
 il>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: pwe3 <pwe3@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-From: pwe3-bounces@ietf.org Fri Nov 12 15:42:22 2004
Return-path: <pwe3-bounces@ietf.org>
X-Sender: andymalis@comcast.net@mail.comcast.net
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
To: "Yaakov Stein" <yaakov_s@rad.com>
In-Reply-To: <27A0F290348F8E45AEF79889DDE65A5203455F3A@exrad2.ad.rad.co.
 il>
References: <27A0F290348F8E45AEF79889DDE65A5203455F3A@exrad2.ad.rad.co.il>
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Yaakov,

I think that only works if you merge the ENTIRE frag draft into CW, 
otherwise the bits are defined in two places.

Cheers,
Andy

----------

At 11/12/2004 02:35 AM +0200, Yaakov Stein wrote:
>Content-class: urn:content-classes:message
>Content-Type: multipart/alternative;
>         boundary="----_=_NextPart_001_01C4C84F.8D4E5973"
>
>Stewart,
>
>I noticed that the CW draft lists the FRG draft as non-normative,
>
>and that the dependency of the CW draft on the FRG one
>
>is only to subsection 4.1 of the latter.
>
>Since the FRG draft defines the use of the bits,
>
>it should actually be normative, as the meaning of these
>
>bits is otherwise not understood.
>
>Wouldn't it be simpler to paste the relevant wording
>
>from subsection 4.1 into the CW draft,
>
>thus both making the FRG draft truly non-normative,
>
>and placing more of the CW description in one place ?
>
>(For that matter we could also repeat the sequence number
>
>processing, and make it entirely self-contained.)
>
>Y(J)S
>
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www1.ietf.org/mailman/listinfo/pwe3


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: Title for encapsulation Drafts.
Date: Sun, 14 Nov 2004 20:52:54 +0200
Lines: 22
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: pwe3 <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Sun Nov 14 20:02:08 2004
Return-path: <pwe3-bounces@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] Title for encapsulation Drafts.
Thread-Index: AcTIN/MM+81iQJykSPajga4tHbythgAg8Vcg
To: "W. Mark Townsley" <townsley@cisco.com>,
	"Luca Martini" <lmartini@cisco.com>
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: quoted-printable
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

=20
[Luca] One suggestion is to change this to Blah over PSN.=20
However this will probably not pass the IESG review as it not a well
known=20
acronym , and it cannot be expanded. ( or at least I believe so )

PSN is the term we have been using in PWE work,
and is presently used in the title of the CESoPSN draft.

The true representation is Blah over MPLS ....

[Y(J)S] The problem with that is the requirement for PWs to be
PSN agnostic. Why do we need the PW architecture and requirements
draft for Blah over MPLS ?

[Mark] This sounds good to me. The Blah over L2TPv3 documents exist=20
in l2tpext anyway.

[Y(J)S] So it turns out that ONLY the TDM drafts
(SAToP, TDMoIP and CESoPSN), which explicitly
allow MPLS, L2TP, and even UDP/IP,
are true PWs.=20


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Andrew G. Malis" <andymalis@comcast.net>
Subject: RE: Title for encapsulation Drafts.
Date: Sun, 14 Nov 2004 14:50:53 -0500
Lines: 23
References: <27A0F290348F8E45AEF79889DDE65A520353576F@exrad2.ad.rad.co.il> <27A0F290348F8E45AEF79889DDE65A520353576F@exrad2.ad.rad.co.
 il>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: pwe3 <pwe3@ietf.org>, "W. Mark Townsley" <townsley@cisco.com>,
        Luca Martini <lmartini@cisco.com>
X-From: pwe3-bounces@ietf.org Sun Nov 14 21:04:51 2004
Return-path: <pwe3-bounces@ietf.org>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
To: "Yaakov Stein" <yaakov_s@rad.com>
In-Reply-To: <27A0F290348F8E45AEF79889DDE65A520353576F@exrad2.ad.rad.co.
 il>
References: <27A0F290348F8E45AEF79889DDE65A520353576F@exrad2.ad.rad.co.il>
X-Scan-Signature: 93238566e09e6e262849b4f805833007
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Yaakov,

>[Luca] The true representation is Blah over MPLS ....
>
>[Y(J)S] The problem with that is the requirement for PWs to be
>PSN agnostic. Why do we need the PW architecture and requirements
>draft for Blah over MPLS ?
>
>[Mark] This sounds good to me. The Blah over L2TPv3 documents exist
>in l2tpext anyway.
>
>[Y(J)S] So it turns out that ONLY the TDM drafts
>(SAToP, TDMoIP and CESoPSN), which explicitly
>allow MPLS, L2TP, and even UDP/IP,
>are true PWs.

No, it's just that the other encaps (Ethernet, etc.) have separate 
encapsulation specs for MPLS and L2TPv3.  The TDM specs combined them into 
one.  They're all "true PWs".  Luca's naming suggestion (Blah over MPLS) is 
the best.

Cheers,
Andy


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: ITU-T UDP liason
Date: Mon, 15 Nov 2004 11:08:15 +0000
Lines: 65
References: <4193F24E.5080209@cisco.com>
	<20041112192121.46583111.esaka@isl.rdc.toshiba.co.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: narten@us.ibm.com, pwe3@ietf.org, danny@tcb.net
X-From: pwe3-bounces@ietf.org Mon Nov 15 12:11:11 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: ESAKA Naoki <esaka@isl.rdc.toshiba.co.jp>
In-Reply-To: <20041112192121.46583111.esaka@isl.rdc.toshiba.co.jp>
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org



ESAKA Naoki wrote:
> Hi all,
> 
> Doesn't ITU care about that we actually recommend two type
> of data plane format(PW over UDP/IP, PW over L2TPv3/UDP/IP)?
> I think it may cause confusion.  How about suggesting
> manually configured L2TPv3/UDP/IP tunnel(L2TPv3 with no singnalling)
> as well as configured UDP ports.

The issue was how to multiplex PW over UDP. In
L2TPv3/UDP/IP, multiplexing happens in L2TPv3, not in UDP.

Stewart


> 
> 
> On Thu, 11 Nov 2004 23:14:22 +0000
> Stewart Bryant <stbryant@cisco.com> wrote:
> 
> 
>>Having discussed the ITU-T UDP liaison at today's
>>PWE3 IETF meeting, here is the text of
>>the response that we agreed at the meeting.
>>
>>Please comment ASAP as the chairs need to initiate
>>the formal response process Tuesday 16th November.
>>
>>Stewart
>>
>>
>>-----------------------------------------------
>>
>>Having considered the liaison from ITU-T Q5/13
>>to IETF PWE3 WG entitled "Using UDP port numbers
>>as connection de-multiplexers"
>>
>>http://www.ietf.org/IESG/LIAISON/file21.pdf
>>
>>The IETF PWE3 WG recommends that both source
>>and destination UDP ports be user configured.
>>
>>If the ITU-T Study Group needs to use a signaled
>>IP tunnel protocol in this application, then the
>>IETF PWE3 WG recommends the use Layer Two
>>Tunneling Protocol (Version 3), which will be
>>published as RFC3931. The latest draft of this
>>is currently located at:
>>
>>http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-l2tp-base-14.txt
>>
>>
>>
>>
>>
>>
>>
>>_______________________________________________
>>pwe3 mailing list
>>pwe3@ietf.org
>>https://www1.ietf.org/mailman/listinfo/pwe3
> 
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: CW and frag drafts
Date: Mon, 15 Nov 2004 13:54:31 +0000
Lines: 50
References: <27A0F290348F8E45AEF79889DDE65A5203455F3A@exrad2.ad.rad.co.il>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pwe3 <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Mon Nov 15 15:03:25 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: Yaakov Stein <yaakov_s@rad.com>
In-Reply-To: <27A0F290348F8E45AEF79889DDE65A5203455F3A@exrad2.ad.rad.co.il>
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org



Yaakov Stein wrote:

> Stewart,
> 
> I noticed that the CW draft lists the FRG draft as non-normative,
> 
> and that the dependency of the CW draft on the FRG one
> 
> is only to subsection 4.1 of the latter.
> 
> Since the FRG draft defines the use of the bits,
> 
> it should actually be normative, as the meaning of these
> 
> bits is otherwise not understood.
> 
> Wouldn't it be simpler to paste the relevant wording
> 
> from subsection 4.1 into the CW draft,
> 
> thus both making the FRG draft truly non-normative,
> 
> and placing more of the CW description in one place ?
> 
> (For that matter we could also repeat the sequence number
> 
> processing, and make it entirely self-contained.)

I would be OK with copying the FRG text (and the sequence
numnber text into CW).

What do Andy and Luca think?

Stewart



> 
> Y(J)S
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: CW and frag drafts
Date: Mon, 15 Nov 2004 16:23:07 +0200
Lines: 84
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: "Mark Townsley \(E-mail\)" <townsley@cisco.com>, pwe3 <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Mon Nov 15 15:38:26 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Stewart Bryant'" <stbryant@cisco.com>, Yaakov Stein <yaakov_s@rad.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Stewart, Yaakov and all,
It would be nice if we could merge the CW and Frag drafts
(ending with one draft less), but:
The Frag draft deals both with L2TPv3 and MPLS (actually
even with L2TPv2), while the CW draft only deals with MPLS.
And if we must have two drafts, we could as well leave the 
partitioning "as is".


Regards,
                                  Sasha Vainshtein
email:                         sasha@axerra.com <mailto:sasha@axerra.com> 
phone:                       +972-3-7569993 (office)
fax:                            +972-3-6487779
mobile:                      +972-52-8674833 


> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]
> Sent: Monday, November 15, 2004 3:55 PM
> To: Yaakov Stein
> Cc: pwe3
> Subject: Re: [PWE3] CW and frag drafts
> 
> 
> 
> 
> Yaakov Stein wrote:
> 
> > Stewart,
> > 
> > I noticed that the CW draft lists the FRG draft as non-normative,
> > 
> > and that the dependency of the CW draft on the FRG one
> > 
> > is only to subsection 4.1 of the latter.
> > 
> > Since the FRG draft defines the use of the bits,
> > 
> > it should actually be normative, as the meaning of these
> > 
> > bits is otherwise not understood.
> > 
> > Wouldn't it be simpler to paste the relevant wording
> > 
> > from subsection 4.1 into the CW draft,
> > 
> > thus both making the FRG draft truly non-normative,
> > 
> > and placing more of the CW description in one place ?
> > 
> > (For that matter we could also repeat the sequence number
> > 
> > processing, and make it entirely self-contained.)
> 
> I would be OK with copying the FRG text (and the sequence
> numnber text into CW).
> 
> What do Andy and Luca think?
> 
> Stewart
> 
> 
> 
> > 
> > Y(J)S
> > 
> > 
> > 
> > 
> --------------------------------------------------------------
> ----------
> > 
> > _______________________________________________
> > 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  Wed Dec 27 15:58:27 2006
From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
Subject: PW Transport LSP nature
Date: Mon, 15 Nov 2004 08:13:35 -0800
Lines: 11
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-From: pwe3-bounces@ietf.org Mon Nov 15 17:21:09 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'pwe3@ietf.org'" <pwe3@ietf.org>
X-Mailer: Internet Mail Service (5.5.2656.59)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Hi,

Is it safe to assume that the Transport LSP can't be in Uniform-mode?
The reason that I think this is true, is that a Transport LSP should not have
the restriction of setting its TTL=2 (same as the Interworking Label). Also a Transport
LSP can carry many PWs, that could have different CoS and possibly TTL.

BTW, why is the TTL of IW label set to 2 rather than 1? Is it because of PHP?

Thanks,
-Shahram


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Luca Martini <lmartini@cisco.com>
Subject: Re: PW Transport LSP nature
Date: Mon, 15 Nov 2004 10:20:02 -0700
Organization: Cisco Systems
Lines: 43
References: <4B6D09F3B826D411A67300D0B706EFDE0115D29D@nt-exch-yow.pmc_nt.nt.pmc-sierra.bc.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "'pwe3@ietf.org'" <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Mon Nov 15 18:35:07 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7) Gecko/20040620
X-Accept-Language: en-us, en, fr, it
To: Shahram Davari <Shahram_Davari@pmc-sierra.com>
In-Reply-To: <4B6D09F3B826D411A67300D0B706EFDE0115D29D@nt-exch-yow.pmc_nt.nt.pmc-sierra.bc.ca>
X-PMX-Version: 4.7.0.111621
X-from-outside-Cisco: [10.32.224.186]
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org



Shahram Davari wrote:

>Hi,
>
>Is it safe to assume that the Transport LSP can't be in Uniform-mode?
>The reason that I think this is true, is that a Transport LSP should not have
>the restriction of setting its TTL=2 (same as the Interworking Label). Also a Transport
>LSP can carry many PWs, that could have different CoS and possibly TTL.
>
>  
>
true, but when the PSN label is popped, the TTL is always decreased , 
and copied down. Hence setting the PW label TTL=2 does not do much 
unless the PEs are adjacent. Anyway setting the TTL=2 was removed from 
the spec almost 2 years ago.

>BTW, why is the TTL of IW label set to 2 rather than 1? Is it because of PHP?
>
>  
>
it was set to 2 for the adjacent PE case only. If the PEs are adjacent , 
then there is no "PSN label", and setting the TTL=2 could prevent the 
packet from being mis-switched .... This was the thought behind the 
original design.
2 is the lowest value you can set the TTL , otherwise the TTL will 
expire before the packet is forwarded out the attachment circuit.
Look at rfc3032

Luca


>Thanks,
>-Shahram
>
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www1.ietf.org/mailman/listinfo/pwe3
>
>  
>


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
Subject: RE: PW Transport LSP nature
Date: Mon, 15 Nov 2004 11:18:48 -0800
Lines: 79
Mime-Version: 1.0
Content-Type: text/plain
Cc: "'pwe3@ietf.org'" <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Mon Nov 15 20:33:54 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Luca Martini'" <lmartini@cisco.com>
X-Mailer: Internet Mail Service (5.5.2656.59)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Hi Luca,

 
> Shahram Davari wrote:
> 
> >Hi,
> >
> >Is it safe to assume that the Transport LSP can't be in Uniform-mode?
> >The reason that I think this is true, is that a Transport 
> LSP should not have
> >the restriction of setting its TTL=2 (same as the 
> Interworking Label). Also a Transport
> >LSP can carry many PWs, that could have different CoS and 
> possibly TTL.
> >
> >  
> >
> true, but when the PSN label is popped, the TTL is always decreased , 
> and copied down. Hence setting the PW label TTL=2 does not do much 
> unless the PEs are adjacent. 

SD> If the TTL is always decreased and copied, this means the Transport LSP is
a Uniform LSP. By where is this requirement mentioned and why?

>Anyway setting the TTL=2 was 
> removed from 
> the spec almost 2 years ago.

Look at section 6.1 of  http://www.ietf.org/internet-drafts/draft-ietf-pwe3-arch-07.txt
it is still there.

> 
> >BTW, why is the TTL of IW label set to 2 rather than 1? Is 
> it because of PHP?
> >
> >  
> >
> it was set to 2 for the adjacent PE case only. If the PEs are 
> adjacent , 
> then there is no "PSN label", and setting the TTL=2 could prevent the 
> packet from being mis-switched .... This was the thought behind the 
> original design.
> 2 is the lowest value you can set the TTL , otherwise the TTL will 
> expire before the packet is forwarded out the attachment circuit.
> Look at rfc3032

SD> RFC 3443 updates the TTL processing of RFC3032, which says:

   oTTL Check: Check if oTTL is greater than 0.  If the oTTL Check is
   false, then the packet is not forwarded.  Note that the oTTL check is
   performed only if any outgoing TTL (either IP or MPLS) is set to oTTL
   (see section 3.5 for exception).

So if there is no outgoing TTL (such as the case of Ethernet), then the oTTL
isn't check at all.


-Shahram

> 
> Luca
> 
> 
> >Thanks,
> >-Shahram
> >
> >_______________________________________________
> >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  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: PW Transport LSP nature
Date: Mon, 15 Nov 2004 21:18:01 +0000
Lines: 21
References: <4B6D09F3B826D411A67300D0B706EFDE0115D29D@nt-exch-yow.pmc_nt.nt.pmc-sierra.bc.ca>
	<4198E542.20404@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Shahram Davari <Shahram_Davari@pmc-sierra.com>,
	"'pwe3@ietf.org'" <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Mon Nov 15 22:40:57 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: Luca Martini <lmartini@cisco.com>
In-Reply-To: <4198E542.20404@cisco.com>
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org



Luca Martini wrote:

> true, but when the PSN label is popped, the TTL is always decreased , 
> and copied down. Hence setting the PW label TTL=2 does not do much 
> unless the PEs are adjacent. Anyway setting the TTL=2 was removed from 
> the spec almost 2 years ago.
> 


Have you got a reference to the list discussion where this was
descided?

The latest that I can find is

http://www1.ietf.org/mail-archive/web/pwe3/current/msg04219.html

where the TTL=2 was agreed.

- Stewart


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Luca Martini <lmartini@cisco.com>
Subject: Re: PW Transport LSP nature
Date: Mon, 15 Nov 2004 17:50:35 -0700
Organization: Cisco Systems
Lines: 44
References: <4B6D09F3B826D411A67300D0B706EFDE0115D29D@nt-exch-yow.pmc_nt.nt.pmc-sierra.bc.ca>	<4198E542.20404@cisco.com>
	<41991D09.4030205@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Shahram Davari <Shahram_Davari@pmc-sierra.com>,
	"'pwe3@ietf.org'" <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Tue Nov 16 01:53:17 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7) Gecko/20040620
X-Accept-Language: en-us, en, fr, it
To: Stewart Bryant <stbryant@cisco.com>
In-Reply-To: <41991D09.4030205@cisco.com>
X-PMX-Version: 4.7.0.111621
X-from-outside-Cisco: [10.32.241.115]
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


Stewart,

No I can't remember exactly which e-mail. This was a long time ago. If 
you really thing we need to find out I can go through the SCCS version 
database of the draft source, and find out which is the first version 
that dropped it. This will take some time  as there are 118 versions in 
it ..... So I would rather not look ...;-)

Luca


Stewart Bryant wrote:

>
>
> Luca Martini wrote:
>
>> true, but when the PSN label is popped, the TTL is always decreased , 
>> and copied down. Hence setting the PW label TTL=2 does not do much 
>> unless the PEs are adjacent. Anyway setting the TTL=2 was removed 
>> from the spec almost 2 years ago.
>>
>
>
> Have you got a reference to the list discussion where this was
> descided?
>
> The latest that I can find is
>
> http://www1.ietf.org/mail-archive/web/pwe3/current/msg04219.html
>
> where the TTL=2 was agreed.
>
> - Stewart
>
>
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
>


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: PW Transport LSP nature
Date: Tue, 16 Nov 2004 08:57:24 +0000
Lines: 63
References: <4B6D09F3B826D411A67300D0B706EFDE0115D29D@nt-exch-yow.pmc_nt.nt.pmc-sierra.bc.ca>	<4198E542.20404@cisco.com>	<41991D09.4030205@cisco.com>
	<41994EDB.6000508@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Shahram Davari <Shahram_Davari@pmc-sierra.com>,
	"'pwe3@ietf.org'" <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Tue Nov 16 10:05:33 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: Luca Martini <lmartini@cisco.com>
In-Reply-To: <41994EDB.6000508@cisco.com>
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org



Luca Martini wrote:

> 
> Stewart,
> 
> No I can't remember exactly which e-mail. This was a long time ago. If 
> you really thing we need to find out I can go through the SCCS version 
> database of the draft source, and find out which is the first version 
> that dropped it. This will take some time  as there are 118 versions in 
> it ..... So I would rather not look ...;-)

It's not the SCCS version that we need, it's the PWE3 WG email that
agreed the change that we need. I know that the change went into arch 
at -04, but I can't find anything that said take it out again and for
what reason.

- Stewart

> 
> Luca
> 
> 
> Stewart Bryant wrote:
> 
>>
>>
>> Luca Martini wrote:
>>
>>> true, but when the PSN label is popped, the TTL is always decreased , 
>>> and copied down. Hence setting the PW label TTL=2 does not do much 
>>> unless the PEs are adjacent. Anyway setting the TTL=2 was removed 
>>> from the spec almost 2 years ago.
>>>
>>
>>
>> Have you got a reference to the list discussion where this was
>> descided?
>>
>> The latest that I can find is
>>
>> http://www1.ietf.org/mail-archive/web/pwe3/current/msg04219.html
>>
>> where the TTL=2 was agreed.
>>
>> - Stewart
>>
>>
>>
>>
>> _______________________________________________
>> 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  Wed Dec 27 15:58:27 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: Title for encapsulation Drafts.
Date: Tue, 16 Nov 2004 11:48:55 +0200
Lines: 39
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: pwe3 <pwe3@ietf.org>, "W. Mark Townsley" <townsley@cisco.com>,
	Luca Martini <lmartini@cisco.com>
X-From: pwe3-bounces@ietf.org Tue Nov 16 11:00:25 2004
Return-path: <pwe3-bounces@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] Title for encapsulation Drafts.
Thread-Index: AcTKgvv55hMVvQ/uS3i+m/IP9C59dQBPWZJg
To: "Andrew G. Malis" <andymalis@comcast.net>
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: quoted-printable
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

=20
> No, it's just that the other encaps (Ethernet, etc.) have=20
> separate encapsulation specs for MPLS and L2TPv3.  The TDM=20
> specs combined them into one.  They're all "true PWs". =20
> Luca's naming suggestion (Blah over MPLS) is the best.


Andy,=20

My problem is with the following statement in the PWE charter:

  Tunnels for PWE3 encapsulations will use IP (both versions), L2TP,
  or MPLS.  PWE3 will coordinate closely with the L2TP WG and its
  technologies.  PWE3 pseudo wires will have the same specification
  for all underlying PSNs (i.e. there will not be specific adaptation
  of a pseudo wire technology for MPLS that is distinct from what is
  used for IP and L2TP, or differences will be the minimum necessary
  and will be called out clearly).

So not only have we deprecated IP (per our liaison to ITU-T SG13)
we are now saying that PWs do not have to have a single specification
for the two remaining PSN types, but rather there are separate documents
in two different WGs.=20

And other than the architecture document, I haven't seen clear calling
out=20
of the differences anywhere EXCEPT in the TDM documents=20
(e.g. draft-ietf-pwe3-tdmoip has consecutive sections=20
explicitly showing the encapsulations for IP, MPLS, and L2TPv3).

So I guess in our rechartering we should fix this paragraph.
We need to remove plain IP. And since L2TP is not being handled
here, we should really only explcitly talk about MPLS,
although we may reference L2TP documents.
Then Luca's suggestion is precisely correct.

Am I the only one who feels that something went wrong here?

Y(J)S


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: Title for encapsulation Drafts.
Date: Tue, 16 Nov 2004 12:41:14 +0200
Lines: 104
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: "W. Mark Townsley" <townsley@cisco.com>, pwe3 <pwe3@ietf.org>,
	Luca Martini <lmartini@cisco.com>
X-From: pwe3-bounces@ietf.org Tue Nov 16 11:56:26 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Yaakov Stein'" <yaakov_s@rad.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Yaakov and all,
Please see inline.

Regards,
                                  Sasha Vainshtein
email:                         sasha@axerra.com <mailto:sasha@axerra.com> 
phone:                       +972-3-7569993 (office)
fax:                            +972-3-6487779
mobile:                      +972-52-8674833 


> -----Original Message-----
> From: Yaakov Stein [mailto:yaakov_s@rad.com]
> Sent: Tuesday, November 16, 2004 11:49 AM
> To: Andrew G. Malis
> Cc: pwe3; W. Mark Townsley; Luca Martini
> Subject: RE: [PWE3] Title for encapsulation Drafts.
> 
> 
>  
> > No, it's just that the other encaps (Ethernet, etc.) have 
> > separate encapsulation specs for MPLS and L2TPv3.  The TDM 
> > specs combined them into one.  They're all "true PWs".  
> > Luca's naming suggestion (Blah over MPLS) is the best.
> 
> 
> Andy, 
> 
> My problem is with the following statement in the PWE charter:
> 
>   Tunnels for PWE3 encapsulations will use IP (both versions), L2TP,
>   or MPLS.  PWE3 will coordinate closely with the L2TP WG and its
>   technologies.  PWE3 pseudo wires will have the same specification
>   for all underlying PSNs (i.e. there will not be specific adaptation
>   of a pseudo wire technology for MPLS that is distinct from what is
>   used for IP and L2TP, or differences will be the minimum necessary
>   and will be called out clearly).
> 
> So not only have we deprecated IP (per our liaison to ITU-T SG13)
>
[Sasha] I disagree. IP tunnels are not related to UDP and hence
have not been deprecated by our liaison in question. E.g.,
http://www.ietf.org/internet-drafts/draft-ietf-mpls-in-ip-or-gre-08.txt
(aready in the RFC Editor queue) describes an IP tunneling mechanism that
can be used for carrying PWs. L2TP is yet another IP tunneling mechanism 
that be used for carrying PWs.
c
>
> we are now saying that PWs do not have to have a single specification
> for the two remaining PSN types, but rather there are 
> separate documents in two different WGs. 
>
[Sasha] I AGREE with Yaakov that this looks like an explicit Charter
violation.  
>
> And other than the architecture document, I haven't seen clear calling
> out of the differences anywhere EXCEPT in the TDM documents 
> (e.g. draft-ietf-pwe3-tdmoip has consecutive sections 
> explicitly showing the encapsulations for IP, MPLS, and L2TPv3).
> 
> So I guess in our rechartering we should fix this paragraph.
> We need to remove plain IP. 
>
[Sasha] On the contrary: I think that L2TP should be removed
from list of PSN tunnel types since, as written today, it 
implicitly suggests that L2TP uses some tunneling of its own 
that is not IP (which, IMHO, is incorrect).

Of course, it would not mean that L2TP as a DEMULTIPLEXING method
with an associated signaling protocol cannot or should not be used
by PWs. 

>
> And since L2TP is not being handled
> here, we should really only explcitly talk about MPLS,
>
[Sasha] I think that we sometimes still fail to make the
proper distinction between MPLS as the PW DEMULTIPLEXING method
(which can be used with different tunneling technologies) and
MPLS as the PSN TUNNELING method. Until we sort this out,
"speaking onluy about MPLS" will not really help.

>
> although we may reference L2TP documents.
>
[Sasha]
>
> Then Luca's suggestion is precisely correct.
>
[Sasha] I do not think this is a good suggestion (but, of course,
everybody is entiled to his/her opinion).
May I propose, as an alternative,
"Blah over Pseudo-wires"?
> 
> Am I the only one who feels that something went wrong here?
> 
> Y(J)S
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "W. Mark Townsley" <townsley@cisco.com>
Subject: Re: Title for encapsulation Drafts.
Date: Tue, 16 Nov 2004 06:29:33 -0500
Lines: 21
References: <AF5018AC03D1D411ABB70002A5091326015E18D1@TLV1>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Luca Martini <lmartini@cisco.com>, 'Yaakov Stein' <yaakov_s@rad.com>,
	pwe3 <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Tue Nov 16 12:41:14 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7) Gecko/20040616
X-Accept-Language: en-us, en
To: Sasha Vainshtein <Sasha@AXERRA.com>
In-Reply-To: <AF5018AC03D1D411ABB70002A5091326015E18D1@TLV1>
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org



Yaakov Stein wrote:

>>So I guess in our rechartering we should fix this paragraph.
>>We need to remove plain IP. 
>>

IP set parallel to L2TP and MPLS (if you consider "MPLS" as including the suite 
of protocols which can distribute MPLS labels) has pretty much been the misnomer 
form the start. An IP tunnel in its strictest form here is simply a pair of PE 
IP addresses. I think it has been demonstrated that you need some signaling, 
perhaps layers of signaling, in order to perform the task at hand. LDP, RSVP, 
BGP, L2TPv3 are all protocols that have been proposed and/or deployed, in one 
form or another, to perform PW setup for different types of PWs. RTP, BFD, and 
VCCV have each been proposed to perform additional functions for different types 
of PWs. Each handle particular tasks in their own way, and require different 
experts (and at times different WGs) to make sure the extension is done in a 
manner which fits in with other uses of the protocol.

- Mark


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: Title for encapsulation Drafts.
Date: Tue, 16 Nov 2004 16:04:54 +0200
Lines: 36
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: "W. Mark Townsley" <townsley@cisco.com>, pwe3 <pwe3@ietf.org>,
	Luca Martini <lmartini@cisco.com>
X-From: pwe3-bounces@ietf.org Tue Nov 16 15:15:37 2004
Return-path: <pwe3-bounces@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] Title for encapsulation Drafts.
Thread-Index: AcTLyUEZZJsHvEOFQkGJyKtnExrk6QAGcNZA
To: "Sasha Vainshtein" <Sasha@AXERRA.com>
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: quoted-printable
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

=20
> [Sasha] I disagree. IP tunnels are not related to UDP and=20
> hence have not been deprecated by our liaison in question.=20
> E.g.,=20
>
http://www.ietf.org/internet-drafts/draft-ietf-mpls-in-ip-or-gre-08.txt
(aready in the RFC Editor queue) describes an IP tunneling mechanism
that can be used for carrying PWs.=20
> L2TP is yet another IP tunneling mechanism that be used for carrying
PWs.

[YJS]=20

Nowhere does the charter say "IP tunnels",
it just says "IP".  I believe that at the beginning everyone
understood "IP" as plain TCP or UDP/IP (as used in AVT),=20
and not MPLS in GRE over IP.
Had that been the intention I think it would have been made specific.

<snip>

[Sasha] I do not think this is a good suggestion (but, of course,
everybody is entiled to his/her opinion).
May I propose, as an alternative,
"Blah over Pseudo-wires"?

[YJS]=20

I was being facetious here.
I suggested precisely this at the meeting.


>=20
> Am I the only one who feels that something went wrong here?
>=20
> Y(J)S


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Eric Rosen <erosen@cisco.com>
Subject: Re: PW Transport LSP nature
Date: Tue, 16 Nov 2004 09:16:10 -0500
Lines: 2
References: <4199C0F4.9000107@cisco.com>
Reply-To: erosen@cisco.com
Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Cc: "'pwe3@ietf.org'" <pwe3@ietf.org>,
	Shahram Davari <Shahram_Davari@pmc-sierra.com>,
	Luca Martini <lmartini@cisco.com>
X-From: pwe3-bounces@ietf.org Tue Nov 16 15:27:18 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
To: Stewart Bryant <stbryant@cisco.com>
In-reply-to: Your message of Tue, 16 Nov 2004 08:57:24 +0000.
	<4199C0F4.9000107@cisco.com> 
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
	(=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.3
	(sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
X-Scan-Signature: 0f1ff0b0158b41ac6b9548d0972cdd31
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


If you set TTL to 2, then stitched (multi-hop) PWs won't work. 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: Title for encapsulation Drafts.
Date: Tue, 16 Nov 2004 16:18:07 +0200
Lines: 73
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: "W. Mark Townsley" <townsley@cisco.com>, pwe3 <pwe3@ietf.org>,
	Luca Martini <lmartini@cisco.com>
X-From: pwe3-bounces@ietf.org Tue Nov 16 15:37:17 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Yaakov Stein'" <yaakov_s@rad.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Yaakov and all,
Please see more inline.

Regards,
                                  Sasha Vainshtein
email:                         sasha@axerra.com <mailto:sasha@axerra.com> 
phone:                       +972-3-7569993 (office)
fax:                            +972-3-6487779
mobile:                      +972-52-8674833 


> -----Original Message-----
> From: Yaakov Stein [mailto:yaakov_s@rad.com]
> Sent: Tuesday, November 16, 2004 4:05 PM
> To: Sasha Vainshtein
> Cc: pwe3; W. Mark Townsley; Luca Martini; Andrew G. Malis
> Subject: RE: [PWE3] Title for encapsulation Drafts.
> 
> 
>  
> > [Sasha] I disagree. IP tunnels are not related to UDP and 
> > hence have not been deprecated by our liaison in question. 
> > E.g., 
> >
> > http://www.ietf.org/internet-drafts/draft-ietf-mpls-in-ip-or-gre-08.txt
> > (aready in the RFC Editor queue) describes an IP tunneling mechanism
> > that can be used for carrying PWs. 
> > L2TP is yet another IP tunneling mechanism that be used for carrying
PWs.

> [YJS] 
>
> Nowhere does the charter say "IP tunnels", it just says "IP".  
>
[Sasha]Well, to be precise, the charter says:
<quote>
  Tunnels for PWE3 encapsulations will use IP (both versions), L2TP,
  or MPLS.  
<end quote>
To me this sounds very close to "IP/L2TP/MPLS tunnels", but ...
> 
> I believe that at the beginning everyone
> understood "IP" as plain TCP or UDP/IP (as used in AVT), 
> and not MPLS in GRE over IP.
> Had that been the intention I think it would have been made specific.
> 
[Sasha] I see that you give the benefit of doubt to the people who have
drafted the original Charter 3+ years ago. Unfortunately, the original 
intention - regardless of how we reverse engineer it today - 
is hardly all that relevant to the curent reality. The best we can hope
for is to express our opinion in a less ambiguous way when it comes
to actually re-writing the Charter.

> <snip>

> > [Sasha] I do not think this is a good suggestion (but, of course,
> > everybody is entiled to his/her opinion).
> > May I propose, as an alternative,
> > "Blah over Pseudo-wires"?

> [YJS] 

> I was being facetious here.
> I suggested precisely this at the meeting.
> 
[Sasha] I withdraw any priority claims here and
gladly defer to you. I still think, though, that 
this is a very reasonable suggestion fully aligned 
with the current Charter, and I do not remember 
any strong reasons against being brought up at 
the meeting or after it.
> 
...snipped to the end ...


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Eric Rosen <erosen@cisco.com>
Subject: Re: Title for encapsulation Drafts.
Date: Tue, 16 Nov 2004 09:30:18 -0500
Lines: 15
References: <27A0F290348F8E45AEF79889DDE65A5203535AE7@exrad2.ad.rad.co.il>
Reply-To: erosen@cisco.com
Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Cc: "W. Mark Townsley" <townsley@cisco.com>, pwe3 <pwe3@ietf.org>,
	Sasha Vainshtein <Sasha@AXERRA.com>, Luca Martini <lmartini@cisco.com>
X-From: pwe3-bounces@ietf.org Tue Nov 16 15:45:21 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
To: "Yaakov Stein" <yaakov_s@rad.com>
In-reply-to: Your message of Tue, 16 Nov 2004 16:04:54 +0200.
	<27A0F290348F8E45AEF79889DDE65A5203535AE7@exrad2.ad.rad.co.il> 
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
	(=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.3
	(sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

> I believe that  at the beginning everyone understood "IP"  as plain TCP or
> UDP/IP (as used in AVT), and not MPLS in GRE over IP. 

That belief is incorrect.  

While  the  charter  itself  does  not mandate  a  particular  IP  tunneling
technology, L2TPv3 was  foisted on us very early  as the preferred solution.
Mark was named  "technical advisor" to ensure that  we wouldn't forget about
it, and I even  believe that one of the WG chairs  was chosen because he was
at the time working on L2TP solutions. 

Frankly, it would never even have occurred to me that someone would advocate
"plain TCP  or UDP".  And given the  long, long discussion the  WG had about
signaling,  one would think  that anyone  who advocated  UDP as  a tunneling
protocol would have mentioned the issue of signaling UDP tunnels. 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Danny McPherson <danny@tcb.net>
Subject: Re: Title for encapsulation Drafts.
Date: Tue, 16 Nov 2004 11:06:58 -0700
Lines: 40
References: <200411161430.iAGEUI74023364@rtp-core-1.cisco.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-bounces@ietf.org Tue Nov 16 19:27:59 2004
Return-path: <pwe3-bounces@ietf.org>
In-Reply-To: <200411161430.iAGEUI74023364@rtp-core-1.cisco.com>
To: pwe3 <pwe3@ietf.org>
X-Mailer: Apple Mail (2.619)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


On Nov 16, 2004, at 7:30 AM, Eric Rosen wrote:

>> I believe that  at the beginning everyone understood "IP"  as plain 
>> TCP or
>> UDP/IP (as used in AVT), and not MPLS in GRE over IP.
>
> That belief is incorrect.

I'm not sure folks figured it for MPLS/GRE/IP, but I suspect most
didn't figure it for TCP or UDP/IP.  Though I do seem to recall
Eric recommending TCP once :-)

> While  the  charter  itself  does  not mandate  a  particular  IP  
> tunneling
> technology, L2TPv3 was  foisted on us very early  as the preferred 
> solution.
> Mark was named  "technical advisor" to ensure that  we wouldn't forget 
> about
> it, and I even  believe that one of the WG chairs  was chosen because 
> he was
> at the time working on L2TP solutions.

Actually, I think that chair was chosen because he wasn't religious
about the tunneling/demux mechanism -- unlike most of the folks
involved at the time (and today :-)

> Frankly, it would never even have occurred to me that someone would 
> advocate
> "plain TCP  or UDP".  And given the  long, long discussion the  WG had 
> about
> signaling,  one would think  that anyone  who advocated  UDP as  a 
> tunneling
> protocol would have mentioned the issue of signaling UDP tunnels.

I think the closest we came to UDP was DCCP/RTP.  And the
liaison statement is somewhat in error suggesting that our charter
defines "UDP/IP as a possible ..." explicitly.

-danny


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: ITU-T Q5/13 liaison - Formal Response
Date: Tue, 16 Nov 2004 18:26:47 +0000
Lines: 25
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Thomas Narten <narten@us.ibm.com>, Yaakov Stein <yaakov_s@rad.com>,
	pwe3 <pwe3@ietf.org>, Scott Bradner <sob@harvard.edu>,
	"'danny@tcb.net'" <danny@tcb.net>
X-From: pwe3-bounces@ietf.org Tue Nov 16 19:46:53 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: statements@ietf.org
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is the formal response from IETF PWE3 WG
to ITU-T Q5/13 (recently renamed ITU-T Q7/13).

--------------------------------------------------

Having considered the liaison from ITU-T Q5/13
to IETF PWE3 WG entitled "Using UDP port numbers
as connection de-multiplexers"

http://www.ietf.org/IESG/LIAISON/file21.pdf

The IETF PWE3 WG recommends that both source
and destination UDP ports be manually configured.

If the ITU-T Study Group wants to use a signaled
IP tunnel protocol in this application, then the
IETF PWE3 WG recommends the use of Layer Two
Tunneling Protocol (Version 3), which will be
published as RFC3931. The latest draft of this
is currently located at:

http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-l2tp-base-14.txt


- Stewart


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Removal of TTL shoulld be 2 from arch draft
Date: Tue, 16 Nov 2004 23:21:03 +0000
Lines: 33
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-bounces@ietf.org Wed Nov 17 00:38:45 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: pwe3 <pwe3@ietf.org>
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This email is to check WG consensus for the removal
of the TTL = 2 recommendation from the following paragraph
from section 6.1 of
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-arch-07.txt

"When a MPLS label is used as a PW Demultiplexer setting of the TTL
  value [RFC3032] in the PW label is application specific, however in a
  strict point to point application the TTL should be set to 2."

This would now read:

"When a MPLS label is used as a PW Demultiplexer setting of the TTL
  value [RFC3032] in the PW label is application specific."

Reason for change
=================

The use of TTL=2 breaks PW stitching.

This is because typical MPLS forwarding hardware will decrement
the TTL in the PW multiplexing label at the stitching point and
cause the packet to become hop expired before reaching the
CE-bound PE, thus preventing a PW packet being delivered over
a stitched PW.

Note that the TTL=2 text was a "should" and therefore a
recommendation rather than a requirement.

I am told that this has already been discussed on the PWE3 list
but I can find no trace of the decision to remove the paragraph.
If anyone can find the discussion that would be helpful.

- Stewart


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Luca Martini <lmartini@cisco.com>
Subject: draft-ietf-pwe3-control-protocol-13.txt
Date: Tue, 16 Nov 2004 17:45:44 -0700
Organization: Cisco Systems
Lines: 5
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-bounces@ietf.org Wed Nov 17 02:00:59 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7) Gecko/20040620
X-Accept-Language: en-us, en, fr, it
To: "PWE3 WG (E-mail)" <pwe3@ietf.org>
X-PMX-Version: 4.7.0.111621
X-from-outside-Cisco: [10.32.241.115]
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Stewart,

this version passes the id-nits script 100% :-)

Luca


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Vach Kompella" <vkompella@timetra.com>
Subject: FW: TTL value of VC Label?
Date: Tue, 16 Nov 2004 18:38:15 -0800
Organization: Alcatel USA
Lines: 57
Reply-To: vach.kompella@alcatel.com
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-From: pwe3-bounces@ietf.org Wed Nov 17 03:47:33 2004
Return-path: <pwe3-bounces@ietf.org>
To: <pwe3@ietf.org>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
X-OriginalArrivalTime: 17 Nov 2004 02:38:20.0505 (UTC)
	FILETIME=[8049C490:01C4CC4E]
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Stewart,

Here's the beginning of the thread.  I support the change which was
pretty much what we had agreed to at that time.  The thread runs from
4/30/2003 through 5/7/2003, when Danny asked for the following text
(suggested by Luca) to be the replacement text:

----------------------------
On 5/7/03 3:49 PM, "Luca Martini" <luca@level3.net> wrote:

> How about this ?
> 
> "The setting of the TTL value in the PW
> label is application dependent, however in a strict point to point 
> application the TTL should be appropriately set to 2"

I like this.  Does anyone have objections to updating the current
document with something along these lines?

-danny
----------------------------

-Vach 

> -----Original Message-----
> From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On 
> Behalf Of Yaron Nachman
> Sent: Wednesday, April 30, 2003 12:23 AM
> To: 'pwe3@ietf.org'
> Cc: Eli Angel; Ilya Vershkov
> Subject: [PWE3] TTL value of VC Label?
> 
> 
> Hi,
> 
> I have just noticed that in the yesterday-updated 
> draft-martini-l2circuit-encap-mpls-05.txt, the TTL value to 
> be placed by an Ingress LER on the VC Label is 2. I have 
> noticed in the past that it was changed to 255.
> 
> So, is it 2 or 255? or even some other value??
> 
> Thanks,
> 
> Yaron Nachman
> 
> SEABRIDGE Ltd.
> Tel:       972-9-7751359
> Fax:      972-9-7751212
> E-mail:  yaron.nachman@SeabridgeNetworks.com
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Vach Kompella" <vkompella@timetra.com>
Subject: RE: Removal of TTL shoulld be 2 from arch draft
Date: Tue, 16 Nov 2004 18:41:51 -0800
Organization: Alcatel USA
Lines: 56
References: <419A8B5F.6090309@cisco.com>
Reply-To: vach.kompella@alcatel.com
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-bounces@ietf.org Wed Nov 17 03:53:27 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Stewart Bryant'" <stbryant@cisco.com>, "'pwe3'" <pwe3@ietf.org>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
In-Reply-To: <419A8B5F.6090309@cisco.com>
X-OriginalArrivalTime: 17 Nov 2004 02:41:53.0653 (UTC)
	FILETIME=[FF559250:01C4CC4E]
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: quoted-printable
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

I support this change.  I think it is more appropriate than the earlier
one because PW stitching involves pt2pt pseudo-wires.

-Vach=20

> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On=20
> Behalf Of Stewart Bryant
> Sent: Tuesday, November 16, 2004 3:21 PM
> To: pwe3
> Subject: [PWE3] Removal of TTL shoulld be 2 from arch draft
>=20
>=20
> This email is to check WG consensus for the removal
> of the TTL =3D 2 recommendation from the following paragraph
> from section 6.1 of=20
> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-arch-07.tx
t

"When a MPLS label is used as a PW Demultiplexer setting of the TTL
  value [RFC3032] in the PW label is application specific, however in a
  strict point to point application the TTL should be set to 2."

This would now read:

"When a MPLS label is used as a PW Demultiplexer setting of the TTL
  value [RFC3032] in the PW label is application specific."

Reason for change
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The use of TTL=3D2 breaks PW stitching.

This is because typical MPLS forwarding hardware will decrement the TTL
in the PW multiplexing label at the stitching point and cause the packet
to become hop expired before reaching the CE-bound PE, thus preventing a
PW packet being delivered over a stitched PW.

Note that the TTL=3D2 text was a "should" and therefore a recommendation
rather than a requirement.

I am told that this has already been discussed on the PWE3 list but I
can find no trace of the decision to remove the paragraph. If anyone can
find the discussion that would be helpful.

- Stewart






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


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Vach Kompella" <vkompella@timetra.com>
Subject: RE: TTL value of VC Label?
Date: Tue, 16 Nov 2004 19:02:15 -0800
Organization: Alcatel USA
Lines: 83
References: <004701c4cc4e$806a6bf0$0802a8c0@eng.timetra.com>
Reply-To: vach.kompella@alcatel.com
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-bounces@ietf.org Wed Nov 17 04:11:42 2004
Return-path: <pwe3-bounces@ietf.org>
To: <vach.kompella@alcatel.com>, <pwe3@ietf.org>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
In-Reply-To: <004701c4cc4e$806a6bf0$0802a8c0@eng.timetra.com>
X-OriginalArrivalTime: 17 Nov 2004 03:02:17.0091 (UTC)
	FILETIME=[D88F6530:01C4CC51]
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Content-Transfer-Encoding: quoted-printable
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Actually, looking at it more carefully, is the question you are asking
that the "TTL should be appropriately set to 2" be stricken?  If so,
yes, it should.

The thread I thought you were referring to is the one below, which
brought up the original change to the text.  I cannot find any
subsequent threads that discuss removing the TTL=3D2 part.

-Vach=20

> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On=20
> Behalf Of Vach Kompella
> Sent: Tuesday, November 16, 2004 6:38 PM
> To: pwe3@ietf.org
> Subject: FW: [PWE3] TTL value of VC Label?
>=20
>=20
> Stewart,
>=20
> Here's the beginning of the thread.  I support the change=20
> which was pretty much what we had agreed to at that time. =20
> The thread runs from 4/30/2003 through 5/7/2003, when Danny=20
> asked for the following text (suggested by Luca) to be the=20
> replacement text:
>=20
> ----------------------------
> On 5/7/03 3:49 PM, "Luca Martini" <luca@level3.net> wrote:
>=20
> > How about this ?
> >=20
> > "The setting of the TTL value in the PW
> > label is application dependent, however in a strict point to point
> > application the TTL should be appropriately set to 2"
>=20
> I like this.  Does anyone have objections to updating the=20
> current document with something along these lines?
>=20
> -danny
> ----------------------------
>=20
> -Vach=20
>=20
> > -----Original Message-----
> > From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On
> > Behalf Of Yaron Nachman
> > Sent: Wednesday, April 30, 2003 12:23 AM
> > To: 'pwe3@ietf.org'
> > Cc: Eli Angel; Ilya Vershkov
> > Subject: [PWE3] TTL value of VC Label?
> >=20
> >=20
> > Hi,
> >=20
> > I have just noticed that in the yesterday-updated
> > draft-martini-l2circuit-encap-mpls-05.txt, the TTL value to=20
> > be placed by an Ingress LER on the VC Label is 2. I have=20
> > noticed in the past that it was changed to 255.
> >=20
> > So, is it 2 or 255? or even some other value??
> >=20
> > Thanks,
> >=20
> > Yaron Nachman
> >=20
> > SEABRIDGE Ltd.
> > Tel:       972-9-7751359
> > Fax:      972-9-7751212
> > E-mail:  yaron.nachman@SeabridgeNetworks.com
> >=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
>=20


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: TTL value of VC Label?
Date: Wed, 17 Nov 2004 10:24:14 +0000
Lines: 111
References: <004c01c4cc51$d8d4f9b0$0802a8c0@eng.timetra.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pwe3@ietf.org
X-From: pwe3-bounces@ietf.org Wed Nov 17 11:27:50 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: vach.kompella@alcatel.com
In-Reply-To: <004c01c4cc51$d8d4f9b0$0802a8c0@eng.timetra.com>
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org



Vach Kompella wrote:

> Actually, looking at it more carefully, is the question you are asking
> that the "TTL should be appropriately set to 2" be stricken?  If so,
> yes, it should.
> 
> The thread I thought you were referring to is the one below, which
> brought up the original change to the text.  I cannot find any
> subsequent threads that discuss removing the TTL=2 part.

Yes, I can only find the mail that said put it in, and
cannot find any mail that say take it out. Hence my question to the
list.

It looks like a consensus for removal, but I will let the issue
run for the traditional two weeks, then Danny and I will declare
consensus one way or the other.

- Stewart


> 
> -Vach 
> 
> 
>>-----Original Message-----
>>From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On 
>>Behalf Of Vach Kompella
>>Sent: Tuesday, November 16, 2004 6:38 PM
>>To: pwe3@ietf.org
>>Subject: FW: [PWE3] TTL value of VC Label?
>>
>>
>>Stewart,
>>
>>Here's the beginning of the thread.  I support the change 
>>which was pretty much what we had agreed to at that time.  
>>The thread runs from 4/30/2003 through 5/7/2003, when Danny 
>>asked for the following text (suggested by Luca) to be the 
>>replacement text:
>>
>>----------------------------
>>On 5/7/03 3:49 PM, "Luca Martini" <luca@level3.net> wrote:
>>
>>
>>>How about this ?
>>>
>>>"The setting of the TTL value in the PW
>>>label is application dependent, however in a strict point to point
>>>application the TTL should be appropriately set to 2"
>>
>>I like this.  Does anyone have objections to updating the 
>>current document with something along these lines?
>>
>>-danny
>>----------------------------
>>
>>-Vach 
>>
>>
>>>-----Original Message-----
>>>From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On
>>>Behalf Of Yaron Nachman
>>>Sent: Wednesday, April 30, 2003 12:23 AM
>>>To: 'pwe3@ietf.org'
>>>Cc: Eli Angel; Ilya Vershkov
>>>Subject: [PWE3] TTL value of VC Label?
>>>
>>>
>>>Hi,
>>>
>>>I have just noticed that in the yesterday-updated
>>>draft-martini-l2circuit-encap-mpls-05.txt, the TTL value to 
>>>be placed by an Ingress LER on the VC Label is 2. I have 
>>>noticed in the past that it was changed to 255.
>>>
>>>So, is it 2 or 255? or even some other value??
>>>
>>>Thanks,
>>>
>>>Yaron Nachman
>>>
>>>SEABRIDGE Ltd.
>>>Tel:       972-9-7751359
>>>Fax:      972-9-7751212
>>>E-mail:  yaron.nachman@SeabridgeNetworks.com
>>>
>>>
>>>_______________________________________________
>>>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  Wed Dec 27 15:58:27 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: Removal of TTL shoulld be 2 from arch draft
Date: Wed, 17 Nov 2004 13:07:36 +0200
Lines: 16
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-bounces@ietf.org Wed Nov 17 12:17:16 2004
Return-path: <pwe3-bounces@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] Removal of TTL shoulld be 2 from arch draft
Thread-Index: AcTMNTJPmHlzulB3RBiQmjWtU3IY/QAX00/g
To: "Stewart Bryant" <stbryant@cisco.com>, "pwe3" <pwe3@ietf.org>
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: quoted-printable
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Stewart -=20

just nits ...

1) Please add a comma before "setting".
2) the rules require "an MPLS", not "a MPLS" .
3) The TTL value is not in the "PW label", it is in the MPLS header.
    (The MPLS label is 20 bits out of the header),
    Actually, 3032 calls this a "label stack entry",
    but I think "header" is clear enough.

When the PW label is contained in an MPLS header [RFC3032], =20
setting of the TTL value is application specific.


Y(J)S


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: TTL value of VC Label?
Date: Wed, 17 Nov 2004 13:41:00 +0200
Lines: 172
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: pwe3@ietf.org, vach.kompella@alcatel.com
X-From: pwe3-bounces@ietf.org Wed Nov 17 12:49:46 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Stewart Bryant'" <stbryant@cisco.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: ee80a2074afbfe28d15369f4e74e579d
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Stewart and all,
I am not sure that striking out any reference to TTL=2
in the PW label is justified.

As Eric has explained in this thread, the only reason
for striking it out is that stitched PWs would not
work. This is obviously correct, but, please note,
that stiched PWs are not in the Charter (at the moment)
and, what is not important, do not comply with the PWE3
architecture as presented in the document we are now
discussing! 

In fact, setting TTL=2 is perfectly aligned with the current
PWE3 architecture (and this is why it has been mentioned
in the document)! 

Of course, we are now discussing enhanced architecture that
would incorporate stitched PWs. But this would require a
consistent architecture document, and not just removal of
a couple of lines from the current one!

What is wrong in the current document, is, IMHO, the ambiguous 
reference to "strict point-to-point applications": as defined 
in this architecture, the PWs are always point-to-point!

E.g., this text suggests that setting TTL=2 would not work 
for PWs connecting Virtual Switch instances in VPLS applications.
Which is, IMHO, incorrect even for Hierarchical VPLS as defined in
http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-ldp-05.txt.

So, may be a less drastic editing could suffice? E.g., what about
the following text:

"The setting of the TTL value in the PW label is application 
dependent. Within the scope of this document, setting TTL 
to 2 is recommended as a precaution against mis-forwarding".

Regards,
                                  Sasha Vainshtein
email:                         sasha@axerra.com <mailto:sasha@axerra.com> 
phone:                       +972-3-7569993 (office)
fax:                            +972-3-6487779
mobile:                      +972-52-8674833 


> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]
> Sent: Wednesday, November 17, 2004 12:24 PM
> To: vach.kompella@alcatel.com
> Cc: pwe3@ietf.org
> Subject: Re: [PWE3] TTL value of VC Label?
> 
> 
> 
> 
> Vach Kompella wrote:
> 
> > Actually, looking at it more carefully, is the question you 
> are asking
> > that the "TTL should be appropriately set to 2" be stricken?  If so,
> > yes, it should.
> > 
> > The thread I thought you were referring to is the one below, which
> > brought up the original change to the text.  I cannot find any
> > subsequent threads that discuss removing the TTL=2 part.
> 
> Yes, I can only find the mail that said put it in, and
> cannot find any mail that say take it out. Hence my question to the
> list.
> 
> It looks like a consensus for removal, but I will let the issue
> run for the traditional two weeks, then Danny and I will declare
> consensus one way or the other.
> 
> - Stewart
> 
> 
> > 
> > -Vach 
> > 
> > 
> >>-----Original Message-----
> >>From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On 
> >>Behalf Of Vach Kompella
> >>Sent: Tuesday, November 16, 2004 6:38 PM
> >>To: pwe3@ietf.org
> >>Subject: FW: [PWE3] TTL value of VC Label?
> >>
> >>
> >>Stewart,
> >>
> >>Here's the beginning of the thread.  I support the change 
> >>which was pretty much what we had agreed to at that time.  
> >>The thread runs from 4/30/2003 through 5/7/2003, when Danny 
> >>asked for the following text (suggested by Luca) to be the 
> >>replacement text:
> >>
> >>----------------------------
> >>On 5/7/03 3:49 PM, "Luca Martini" <luca@level3.net> wrote:
> >>
> >>
> >>>How about this ?
> >>>
> >>>"The setting of the TTL value in the PW
> >>>label is application dependent, however in a strict point to point
> >>>application the TTL should be appropriately set to 2"
> >>
> >>I like this.  Does anyone have objections to updating the 
> >>current document with something along these lines?
> >>
> >>-danny
> >>----------------------------
> >>
> >>-Vach 
> >>
> >>
> >>>-----Original Message-----
> >>>From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On
> >>>Behalf Of Yaron Nachman
> >>>Sent: Wednesday, April 30, 2003 12:23 AM
> >>>To: 'pwe3@ietf.org'
> >>>Cc: Eli Angel; Ilya Vershkov
> >>>Subject: [PWE3] TTL value of VC Label?
> >>>
> >>>
> >>>Hi,
> >>>
> >>>I have just noticed that in the yesterday-updated
> >>>draft-martini-l2circuit-encap-mpls-05.txt, the TTL value to 
> >>>be placed by an Ingress LER on the VC Label is 2. I have 
> >>>noticed in the past that it was changed to 255.
> >>>
> >>>So, is it 2 or 255? or even some other value??
> >>>
> >>>Thanks,
> >>>
> >>>Yaron Nachman
> >>>
> >>>SEABRIDGE Ltd.
> >>>Tel:       972-9-7751359
> >>>Fax:      972-9-7751212
> >>>E-mail:  yaron.nachman@SeabridgeNetworks.com
> >>>
> >>>
> >>>_______________________________________________
> >>>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
> > 
> > 
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: IP Pseudo-wires
Date: Wed, 17 Nov 2004 14:23:41 +0000
Lines: 27
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-bounces@ietf.org Wed Nov 17 15:30:22 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: pwe3 <pwe3@ietf.org>
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


I have been thinking about the IP PW type that
we call up in the control draft.

This is allowed to run over MPLS without the CW
in order to allow ECMP. However I am concerned
that this then breaks routing in the "client"
layer.

If you allow ECMP, then the routing hellos
will not go the same path at the data, and
thus will not do their job. So you could
have incomplete connectivity in the PW, but
routing in the "client" layer would not know,
and would not take appropriate action.

There is also the issue of the IS-IS hellos
needing to be carried that was bought up in the
L2VPN WG.

I think that we need to give serious thought to
removing the IP encap material from the control
draft and writing a stand-alone draft that
gives proper consideration to all the issues
of carrying an IP PW.

- Stewart


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Shah, Himanshu" <hshah@ciena.com>
Subject: RE: IP Pseudo-wires
Date: Wed, 17 Nov 2004 09:35:53 -0500
Lines: 48
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-From: pwe3-bounces@ietf.org Wed Nov 17 15:41:16 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Stewart Bryant'" <stbryant@cisco.com>, pwe3 <pwe3@ietf.org>
X-Mailer: Internet Mail Service (5.5.2657.72)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

...and lets call that draft as 
draft-balus-pwe3-ip-pseudowire-01.txt.. :-)

/himanshu

> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]
> Sent: Wednesday, November 17, 2004 9:24 AM
> To: pwe3
> Subject: [PWE3] IP Pseudo-wires
> 
> 
> 
> I have been thinking about the IP PW type that
> we call up in the control draft.
> 
> This is allowed to run over MPLS without the CW
> in order to allow ECMP. However I am concerned
> that this then breaks routing in the "client"
> layer.
> 
> If you allow ECMP, then the routing hellos
> will not go the same path at the data, and
> thus will not do their job. So you could
> have incomplete connectivity in the PW, but
> routing in the "client" layer would not know,
> and would not take appropriate action.
> 
> There is also the issue of the IS-IS hellos
> needing to be carried that was bought up in the
> L2VPN WG.
> 
> I think that we need to give serious thought to
> removing the IP encap material from the control
> draft and writing a stand-alone draft that
> gives proper consideration to all the issues
> of carrying an IP PW.
> 
> - Stewart
> 
> 
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: IP Pseudo-wires
Date: Wed, 17 Nov 2004 16:42:26 +0200
Lines: 78
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: "Luca Martini \(E-mail\)" <lmartini@cisco.com>, pwe3 <pwe3@ietf.org>,
	"Himanshu Shah \(E-mail\)" <hshah@ciena.com>
X-From: pwe3-bounces@ietf.org Wed Nov 17 15:56:54 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Stewart Bryant'" <stbryant@cisco.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Stewart and all,

I also have strong doubts regarding the current text on IP PW
in the control protocol draft.

1. The text Section 4.6 "IP Layer2 Transport" states that

<quote>
   IP interworking is implementation specific, part of the NSP 
   function [ARCH], and is outside the scope of this document.
<end quote>

However, looking at
http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-arp-mediation-00.txt
I conclude that IP interworking (or at least its ARP mediation component) 
cannot be restricted to the NSP and hence cannot be fully implementation 
specific.

2. As noted by Stewart, it is impossible to roun IS-IS across IP PWs if,
   as described in the control protocol draft, CW is not used. If the CW
   were used, then one could run IS-IS hellos in the appropriate 
   "associated channel" of the PW, otherwise an explicit applicability 
   statement limiting usage of IP PWs should be present somewhere.

I hence support Stewart's suggestion about removing the text on
IP Layer 2 PWs from the control protocol draft. 

Regards,
                                  Sasha Vainshtein
email:                         sasha@axerra.com <mailto:sasha@axerra.com> 
phone:                       +972-3-7569993 (office)
fax:                            +972-3-6487779
mobile:                      +972-52-8674833 


> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]
> Sent: Wednesday, November 17, 2004 4:24 PM
> To: pwe3
> Subject: [PWE3] IP Pseudo-wires
> 
> 
> 
> I have been thinking about the IP PW type that
> we call up in the control draft.
> 
> This is allowed to run over MPLS without the CW
> in order to allow ECMP. However I am concerned
> that this then breaks routing in the "client"
> layer.
> 
> If you allow ECMP, then the routing hellos
> will not go the same path at the data, and
> thus will not do their job. So you could
> have incomplete connectivity in the PW, but
> routing in the "client" layer would not know,
> and would not take appropriate action.
> 
> There is also the issue of the IS-IS hellos
> needing to be carried that was bought up in the
> L2VPN WG.
> 
> I think that we need to give serious thought to
> removing the IP encap material from the control
> draft and writing a stand-alone draft that
> gives proper consideration to all the issues
> of carrying an IP PW.
> 
> - Stewart
> 
> 
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: Re: TTL value of VC Label?
Date: Wed, 17 Nov 2004 10:09:04 -0500
Lines: 191
References: <AF5018AC03D1D411ABB70002A5091326015E18E1@TLV1>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pwe3@ietf.org, vach.kompella@alcatel.com,
	'Stewart Bryant' <stbryant@cisco.com>
X-From: pwe3-bounces@ietf.org Wed Nov 17 16:24:47 2004
Return-path: <pwe3-bounces@ietf.org>
In-Reply-To: <AF5018AC03D1D411ABB70002A5091326015E18E1@TLV1>
To: Sasha Vainshtein <Sasha@AXERRA.com>
X-Mailer: Apple Mail (2.619)
X-Scan-Signature: 43317e64100dd4d87214c51822b582d1
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


On Nov 17, 2004, at 6:41 AM, Sasha Vainshtein wrote:

> Stewart and all,
> I am not sure that striking out any reference to TTL=2
> in the PW label is justified.
>
> As Eric has explained in this thread, the only reason
> for striking it out is that stitched PWs would not
> work. This is obviously correct, but, please note,
> that stiched PWs are not in the Charter (at the moment)
> and, what is not important, do not comply with the PWE3
> architecture as presented in the document we are now
> discussing!
>
> In fact, setting TTL=2 is perfectly aligned with the current
> PWE3 architecture (and this is why it has been mentioned
> in the document)!
>
> Of course, we are now discussing enhanced architecture that
> would incorporate stitched PWs. But this would require a
> consistent architecture document, and not just removal of
> a couple of lines from the current one!

	Lets not be so pedantic. 8) A directive that we know
would definitely preclude stitched PWs from functioning
correctly when we know well that we will be doing stitched
PWs here (in one form or another) sounds like a bad idea.

	--Tom



> What is wrong in the current document, is, IMHO, the ambiguous
> reference to "strict point-to-point applications": as defined
> in this architecture, the PWs are always point-to-point!
>
> E.g., this text suggests that setting TTL=2 would not work
> for PWs connecting Virtual Switch instances in VPLS applications.
> Which is, IMHO, incorrect even for Hierarchical VPLS as defined in
> http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-ldp-05.txt.
>
> So, may be a less drastic editing could suffice? E.g., what about
> the following text:
>
> "The setting of the TTL value in the PW label is application
> dependent. Within the scope of this document, setting TTL
> to 2 is recommended as a precaution against mis-forwarding".
>
> Regards,
>                                   Sasha Vainshtein
> email:                         sasha@axerra.com 
> <mailto:sasha@axerra.com>
> phone:                       +972-3-7569993 (office)
> fax:                            +972-3-6487779
> mobile:                      +972-52-8674833
>
>
>> -----Original Message-----
>> From: Stewart Bryant [mailto:stbryant@cisco.com]
>> Sent: Wednesday, November 17, 2004 12:24 PM
>> To: vach.kompella@alcatel.com
>> Cc: pwe3@ietf.org
>> Subject: Re: [PWE3] TTL value of VC Label?
>>
>>
>>
>>
>> Vach Kompella wrote:
>>
>>> Actually, looking at it more carefully, is the question you
>> are asking
>>> that the "TTL should be appropriately set to 2" be stricken?  If so,
>>> yes, it should.
>>>
>>> The thread I thought you were referring to is the one below, which
>>> brought up the original change to the text.  I cannot find any
>>> subsequent threads that discuss removing the TTL=2 part.
>>
>> Yes, I can only find the mail that said put it in, and
>> cannot find any mail that say take it out. Hence my question to the
>> list.
>>
>> It looks like a consensus for removal, but I will let the issue
>> run for the traditional two weeks, then Danny and I will declare
>> consensus one way or the other.
>>
>> - Stewart
>>
>>
>>>
>>> -Vach
>>>
>>>
>>>> -----Original Message-----
>>>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On
>>>> Behalf Of Vach Kompella
>>>> Sent: Tuesday, November 16, 2004 6:38 PM
>>>> To: pwe3@ietf.org
>>>> Subject: FW: [PWE3] TTL value of VC Label?
>>>>
>>>>
>>>> Stewart,
>>>>
>>>> Here's the beginning of the thread.  I support the change
>>>> which was pretty much what we had agreed to at that time.
>>>> The thread runs from 4/30/2003 through 5/7/2003, when Danny
>>>> asked for the following text (suggested by Luca) to be the
>>>> replacement text:
>>>>
>>>> ----------------------------
>>>> On 5/7/03 3:49 PM, "Luca Martini" <luca@level3.net> wrote:
>>>>
>>>>
>>>>> How about this ?
>>>>>
>>>>> "The setting of the TTL value in the PW
>>>>> label is application dependent, however in a strict point to point
>>>>> application the TTL should be appropriately set to 2"
>>>>
>>>> I like this.  Does anyone have objections to updating the
>>>> current document with something along these lines?
>>>>
>>>> -danny
>>>> ----------------------------
>>>>
>>>> -Vach
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On
>>>>> Behalf Of Yaron Nachman
>>>>> Sent: Wednesday, April 30, 2003 12:23 AM
>>>>> To: 'pwe3@ietf.org'
>>>>> Cc: Eli Angel; Ilya Vershkov
>>>>> Subject: [PWE3] TTL value of VC Label?
>>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> I have just noticed that in the yesterday-updated
>>>>> draft-martini-l2circuit-encap-mpls-05.txt, the TTL value to
>>>>> be placed by an Ingress LER on the VC Label is 2. I have
>>>>> noticed in the past that it was changed to 255.
>>>>>
>>>>> So, is it 2 or 255? or even some other value??
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Yaron Nachman
>>>>>
>>>>> SEABRIDGE Ltd.
>>>>> Tel:       972-9-7751359
>>>>> Fax:      972-9-7751212
>>>>> E-mail:  yaron.nachman@SeabridgeNetworks.com
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>
>>>
>>
>>
>> _______________________________________________
>> 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  Wed Dec 27 15:58:27 2006
From: "Haluska, John J." <jhaluska@telcordia.com>
Subject: ITU Liaison statement
Date: Wed, 17 Nov 2004 11:10:33 -0500
Lines: 17
Mime-Version: 1.0
Content-Type: text/plain
X-From: pwe3-bounces@ietf.org Wed Nov 17 17:25:38 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'pwe3@ietf.org'" <pwe3@ietf.org>
X-Mailer: Internet Mail Service (5.5.2657.72)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

As an outsider who happened to sit in on the PWE3 meeting in DC, I could not
help noticing when looking at the text of the liaison from ITU to PWE3 and
the PWE3 response, that it seems that ITU is asking PWE3 to bless one of 5
proposed demultiplexing methods, and the PWE3 response recommends a
configuration method - it's not clear that the response answers the same
question being asked. I apologize in advance for the naive question, but
does the PWE3 response actually answer the question they are asking? 

Also would it be worthwhile to point them (ITU) to some of the work being
done  in IETF on the problems caused by NATs (e.g. in the new BEHAVE WG)
which one might potentially encounter if such PWs did wind up traversing
NATs?

If this is really clear to the people invovled then I apologize in advance
for wasting the bandwidth. 

John Haluska


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
Subject: RE: TTL value of VC Label?
Date: Wed, 17 Nov 2004 08:08:47 -0800
Lines: 198
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-8"
Cc: pwe3@ietf.org, vach.kompella@alcatel.com
X-From: pwe3-bounces@ietf.org Wed Nov 17 17:42:24 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Sasha Vainshtein'" <Sasha@AXERRA.com>, "'Stewart Bryant'"
	<stbryant@cisco.com>
X-Mailer: Internet Mail Service (5.5.2656.59)
X-Scan-Signature: 97c820c82c68af374c4e382a80dc5017
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Sasha,

When we say application specific and don't mandate TTL=2, 
means you could set TTL=2 for the non-stitching p2p case.


-Shahram

> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]On 
> Behalf Of Sasha Vainshtein
> Sent: Wednesday, November 17, 2004 6:41 AM
> To: 'Stewart Bryant'
> Cc: pwe3@ietf.org; vach.kompella@alcatel.com
> Subject: RE: [PWE3] TTL value of VC Label?
> 
> 
> Stewart and all,
> I am not sure that striking out any reference to TTL=2
> in the PW label is justified.
> 
> As Eric has explained in this thread, the only reason
> for striking it out is that stitched PWs would not
> work. This is obviously correct, but, please note,
> that stiched PWs are not in the Charter (at the moment)
> and, what is not important, do not comply with the PWE3
> architecture as presented in the document we are now
> discussing! 
> 
> In fact, setting TTL=2 is perfectly aligned with the current
> PWE3 architecture (and this is why it has been mentioned
> in the document)! 
> 
> Of course, we are now discussing enhanced architecture that
> would incorporate stitched PWs. But this would require a
> consistent architecture document, and not just removal of
> a couple of lines from the current one!
> 
> What is wrong in the current document, is, IMHO, the ambiguous 
> reference to "strict point-to-point applications": as defined 
> in this architecture, the PWs are always point-to-point!
> 
> E.g., this text suggests that setting TTL=2 would not work 
> for PWs connecting Virtual Switch instances in VPLS applications.
> Which is, IMHO, incorrect even for Hierarchical VPLS as defined in
> http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-ldp-05.txt.
> 
> So, may be a less drastic editing could suffice? E.g., what about
> the following text:
> 
> "The setting of the TTL value in the PW label is application 
> dependent. Within the scope of this document, setting TTL 
> to 2 is recommended as a precaution against mis-forwarding".
> 
> Regards,
>                                   Sasha Vainshtein
> email:                         sasha@axerra.com 
> <mailto:sasha@axerra.com> 
> phone:                       +972-3-7569993 (office)
> fax:                            +972-3-6487779
> mobile:                      +972-52-8674833 
> 
> 
> > -----Original Message-----
> > From: Stewart Bryant [mailto:stbryant@cisco.com]
> > Sent: Wednesday, November 17, 2004 12:24 PM
> > To: vach.kompella@alcatel.com
> > Cc: pwe3@ietf.org
> > Subject: Re: [PWE3] TTL value of VC Label?
> > 
> > 
> > 
> > 
> > Vach Kompella wrote:
> > 
> > > Actually, looking at it more carefully, is the question you 
> > are asking
> > > that the "TTL should be appropriately set to 2" be 
> stricken?  If so,
> > > yes, it should.
> > > 
> > > The thread I thought you were referring to is the one below, which
> > > brought up the original change to the text.  I cannot find any
> > > subsequent threads that discuss removing the TTL=2 part.
> > 
> > Yes, I can only find the mail that said put it in, and
> > cannot find any mail that say take it out. Hence my question to the
> > list.
> > 
> > It looks like a consensus for removal, but I will let the issue
> > run for the traditional two weeks, then Danny and I will declare
> > consensus one way or the other.
> > 
> > - Stewart
> > 
> > 
> > > 
> > > -Vach 
> > > 
> > > 
> > >>-----Original Message-----
> > >>From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On 
> > >>Behalf Of Vach Kompella
> > >>Sent: Tuesday, November 16, 2004 6:38 PM
> > >>To: pwe3@ietf.org
> > >>Subject: FW: [PWE3] TTL value of VC Label?
> > >>
> > >>
> > >>Stewart,
> > >>
> > >>Here's the beginning of the thread.  I support the change 
> > >>which was pretty much what we had agreed to at that time.  
> > >>The thread runs from 4/30/2003 through 5/7/2003, when Danny 
> > >>asked for the following text (suggested by Luca) to be the 
> > >>replacement text:
> > >>
> > >>----------------------------
> > >>On 5/7/03 3:49 PM, "Luca Martini" <luca@level3.net> wrote:
> > >>
> > >>
> > >>>How about this ?
> > >>>
> > >>>"The setting of the TTL value in the PW
> > >>>label is application dependent, however in a strict 
> point to point
> > >>>application the TTL should be appropriately set to 2"
> > >>
> > >>I like this.  Does anyone have objections to updating the 
> > >>current document with something along these lines?
> > >>
> > >>-danny
> > >>----------------------------
> > >>
> > >>-Vach 
> > >>
> > >>
> > >>>-----Original Message-----
> > >>>From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On
> > >>>Behalf Of Yaron Nachman
> > >>>Sent: Wednesday, April 30, 2003 12:23 AM
> > >>>To: 'pwe3@ietf.org'
> > >>>Cc: Eli Angel; Ilya Vershkov
> > >>>Subject: [PWE3] TTL value of VC Label?
> > >>>
> > >>>
> > >>>Hi,
> > >>>
> > >>>I have just noticed that in the yesterday-updated
> > >>>draft-martini-l2circuit-encap-mpls-05.txt, the TTL value to 
> > >>>be placed by an Ingress LER on the VC Label is 2. I have 
> > >>>noticed in the past that it was changed to 255.
> > >>>
> > >>>So, is it 2 or 255? or even some other value??
> > >>>
> > >>>Thanks,
> > >>>
> > >>>Yaron Nachman
> > >>>
> > >>>SEABRIDGE Ltd.
> > >>>Tel:       972-9-7751359
> > >>>Fax:      972-9-7751212
> > >>>E-mail:  yaron.nachman@SeabridgeNetworks.com
> > >>>
> > >>>
> > >>>_______________________________________________
> > >>>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
> > > 
> > > 
> > 
> > 
> > _______________________________________________
> > 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  Wed Dec 27 15:58:27 2006
From: Mustapha Aissaoui <mustapha.aissaoui@alcatel.com>
Subject: Re: IP Pseudo-wires
Date: Wed, 17 Nov 2004 11:42:24 -0500
Organization: Alcatel Networks Corporaton
Lines: 66
References: <8162DD929D7AD24CAD3FC5317CE41FB00100B6ED@w2kmaexg02.wavesmithnet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: pwe3 <pwe3@ietf.org>, 'Stewart Bryant' <stbryant@cisco.com>
X-From: pwe3-bounces@ietf.org Wed Nov 17 17:58:35 2004
Return-path: <pwe3-bounces@ietf.org>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
To: "Shah, Himanshu" <hshah@ciena.com>
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

All,
I initially suggested to Luca to remove the statement that did not
allow the control word. Thinking about it now, I support taking the
IP PW encapsulation text out of the control draft. I assume the IANA
codepoint will be maintained for the purpose of signaling.

I believe the draft below is a good starting point for the
specification of this PW type.

Mustapha.
------------
"Shah, Himanshu" wrote:
> 
> ...and lets call that draft as
> draft-balus-pwe3-ip-pseudowire-01.txt.. :-)
> 
> /himanshu
> 
> > -----Original Message-----
> > From: Stewart Bryant [mailto:stbryant@cisco.com]
> > Sent: Wednesday, November 17, 2004 9:24 AM
> > To: pwe3
> > Subject: [PWE3] IP Pseudo-wires
> >
> >
> >
> > I have been thinking about the IP PW type that
> > we call up in the control draft.
> >
> > This is allowed to run over MPLS without the CW
> > in order to allow ECMP. However I am concerned
> > that this then breaks routing in the "client"
> > layer.
> >
> > If you allow ECMP, then the routing hellos
> > will not go the same path at the data, and
> > thus will not do their job. So you could
> > have incomplete connectivity in the PW, but
> > routing in the "client" layer would not know,
> > and would not take appropriate action.
> >
> > There is also the issue of the IS-IS hellos
> > needing to be carried that was bought up in the
> > L2VPN WG.
> >
> > I think that we need to give serious thought to
> > removing the IP encap material from the control
> > draft and writing a stand-alone draft that
> > gives proper consideration to all the issues
> > of carrying an IP PW.
> >
> > - Stewart
> >
> >
> >
> >
> > _______________________________________________
> > 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  Wed Dec 27 15:58:27 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: IP Pseudo-wires
Date: Wed, 17 Nov 2004 18:54:22 +0200
Lines: 19
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-bounces@ietf.org Wed Nov 17 18:24:10 2004
Return-path: <pwe3-bounces@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] IP Pseudo-wires
Thread-Index: AcTMsc0Fvh5WnFb/TP+tKp7KMO1JtQAFBnTw
To: "Stewart Bryant" <stbryant@cisco.com>, "pwe3" <pwe3@ietf.org>
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: quoted-printable
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

=20
> I have been thinking about the IP PW type that we call up in=20
> the control draft.
>=20
> This is allowed to run over MPLS without the CW in order to=20
> allow ECMP. However I am concerned that this then breaks=20
> routing in the "client" layer.

It is also "out of charter".

The charter only mentions :

    Ethernet (DIX Ethernet (100M, 1G, 10G), IEEE 802.3, 802.1q (VLAN)
    Frame Relay
    ATM
    TDM (e.g. DS1, DS3, SONET)
    MPLS (over IP or L2TP only)

Y(J)S


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: TTL value of VC Label?
Date: Wed, 17 Nov 2004 18:55:50 +0200
Lines: 246
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: pwe3@ietf.org, vach.kompella@alcatel.com
X-From: pwe3-bounces@ietf.org Wed Nov 17 18:25:35 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Shahram Davari'" <Shahram_Davari@pmc-sierra.com>, "'Stewart Bryant'"
	<stbryant@cisco.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: 2b2ad76aced9b1d558e34a970a85c027
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Shahram and all,
As you may have noticed, my message started
with the words "I am not sure that ...".

IMO, there was a certain reasoning behind the initial
suggestion of setting the PW Label TTL to 2 in the
non-stitching case. Unfortunately, this reasoning
did not make it to the document, only the conclusion
we now want to remove. But the reasoning still makes
sense to me when taken in the right scope (single-hop
PWs) - and I would not like to loose it completely.

One can say that this reasoning is trivial and easy
for reconstruction by any interested reader. But is it
really so? I'd say that setting TTL to 2 and not to 1
was questioned on this list, and an explanation
(referring to common HW implementations) was provided...
So it may be not all that trivial as it seems!

At the same time your recent question about non-usage
of the Uniform model for tunnels carrying PWs and the
discussion it triggered indicate to me that there 
is more than one aspect of the problem to be considered.
In theory it would be nice if this issue were captured
properly in the document (consider the "Discussion"
clauses in RFC 1812 as an example). This is probably
too late to do now, though...

Regards,
                                  Sasha Vainshtein
email:                         sasha@axerra.com <mailto:sasha@axerra.com> 
phone:                       +972-3-7569993 (office)
fax:                            +972-3-6487779
mobile:                      +972-52-8674833 


> -----Original Message-----
> From: Shahram Davari [mailto:Shahram_Davari@pmc-sierra.com]
> Sent: Wednesday, November 17, 2004 6:09 PM
> To: Sasha Vainshtein; 'Stewart Bryant'
> Cc: pwe3@ietf.org; vach.kompella@alcatel.com
> Subject: RE: [PWE3] TTL value of VC Label?
> 
> 
> Sasha,
> 
> When we say application specific and don't mandate TTL=2, 
> means you could set TTL=2 for the non-stitching p2p case.
> 
> 
> -Shahram
> 
> > -----Original Message-----
> > From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]On 
> > Behalf Of Sasha Vainshtein
> > Sent: Wednesday, November 17, 2004 6:41 AM
> > To: 'Stewart Bryant'
> > Cc: pwe3@ietf.org; vach.kompella@alcatel.com
> > Subject: RE: [PWE3] TTL value of VC Label?
> > 
> > 
> > Stewart and all,
> > I am not sure that striking out any reference to TTL=2
> > in the PW label is justified.
> > 
> > As Eric has explained in this thread, the only reason
> > for striking it out is that stitched PWs would not
> > work. This is obviously correct, but, please note,
> > that stiched PWs are not in the Charter (at the moment)
> > and, what is not important, do not comply with the PWE3
> > architecture as presented in the document we are now
> > discussing! 
> > 
> > In fact, setting TTL=2 is perfectly aligned with the current
> > PWE3 architecture (and this is why it has been mentioned
> > in the document)! 
> > 
> > Of course, we are now discussing enhanced architecture that
> > would incorporate stitched PWs. But this would require a
> > consistent architecture document, and not just removal of
> > a couple of lines from the current one!
> > 
> > What is wrong in the current document, is, IMHO, the ambiguous 
> > reference to "strict point-to-point applications": as defined 
> > in this architecture, the PWs are always point-to-point!
> > 
> > E.g., this text suggests that setting TTL=2 would not work 
> > for PWs connecting Virtual Switch instances in VPLS applications.
> > Which is, IMHO, incorrect even for Hierarchical VPLS as defined in
> > 
> http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-ldp-05.txt.
> > 
> > So, may be a less drastic editing could suffice? E.g., what about
> > the following text:
> > 
> > "The setting of the TTL value in the PW label is application 
> > dependent. Within the scope of this document, setting TTL 
> > to 2 is recommended as a precaution against mis-forwarding".
> > 
> > Regards,
> >                                   Sasha Vainshtein
> > email:                         sasha@axerra.com 
> > <mailto:sasha@axerra.com> 
> > phone:                       +972-3-7569993 (office)
> > fax:                            +972-3-6487779
> > mobile:                      +972-52-8674833 
> > 
> > 
> > > -----Original Message-----
> > > From: Stewart Bryant [mailto:stbryant@cisco.com]
> > > Sent: Wednesday, November 17, 2004 12:24 PM
> > > To: vach.kompella@alcatel.com
> > > Cc: pwe3@ietf.org
> > > Subject: Re: [PWE3] TTL value of VC Label?
> > > 
> > > 
> > > 
> > > 
> > > Vach Kompella wrote:
> > > 
> > > > Actually, looking at it more carefully, is the question you 
> > > are asking
> > > > that the "TTL should be appropriately set to 2" be 
> > stricken?  If so,
> > > > yes, it should.
> > > > 
> > > > The thread I thought you were referring to is the one 
> below, which
> > > > brought up the original change to the text.  I cannot find any
> > > > subsequent threads that discuss removing the TTL=2 part.
> > > 
> > > Yes, I can only find the mail that said put it in, and
> > > cannot find any mail that say take it out. Hence my 
> question to the
> > > list.
> > > 
> > > It looks like a consensus for removal, but I will let the issue
> > > run for the traditional two weeks, then Danny and I will declare
> > > consensus one way or the other.
> > > 
> > > - Stewart
> > > 
> > > 
> > > > 
> > > > -Vach 
> > > > 
> > > > 
> > > >>-----Original Message-----
> > > >>From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On 
> > > >>Behalf Of Vach Kompella
> > > >>Sent: Tuesday, November 16, 2004 6:38 PM
> > > >>To: pwe3@ietf.org
> > > >>Subject: FW: [PWE3] TTL value of VC Label?
> > > >>
> > > >>
> > > >>Stewart,
> > > >>
> > > >>Here's the beginning of the thread.  I support the change 
> > > >>which was pretty much what we had agreed to at that time.  
> > > >>The thread runs from 4/30/2003 through 5/7/2003, when Danny 
> > > >>asked for the following text (suggested by Luca) to be the 
> > > >>replacement text:
> > > >>
> > > >>----------------------------
> > > >>On 5/7/03 3:49 PM, "Luca Martini" <luca@level3.net> wrote:
> > > >>
> > > >>
> > > >>>How about this ?
> > > >>>
> > > >>>"The setting of the TTL value in the PW
> > > >>>label is application dependent, however in a strict 
> > point to point
> > > >>>application the TTL should be appropriately set to 2"
> > > >>
> > > >>I like this.  Does anyone have objections to updating the 
> > > >>current document with something along these lines?
> > > >>
> > > >>-danny
> > > >>----------------------------
> > > >>
> > > >>-Vach 
> > > >>
> > > >>
> > > >>>-----Original Message-----
> > > >>>From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On
> > > >>>Behalf Of Yaron Nachman
> > > >>>Sent: Wednesday, April 30, 2003 12:23 AM
> > > >>>To: 'pwe3@ietf.org'
> > > >>>Cc: Eli Angel; Ilya Vershkov
> > > >>>Subject: [PWE3] TTL value of VC Label?
> > > >>>
> > > >>>
> > > >>>Hi,
> > > >>>
> > > >>>I have just noticed that in the yesterday-updated
> > > >>>draft-martini-l2circuit-encap-mpls-05.txt, the TTL value to 
> > > >>>be placed by an Ingress LER on the VC Label is 2. I have 
> > > >>>noticed in the past that it was changed to 255.
> > > >>>
> > > >>>So, is it 2 or 255? or even some other value??
> > > >>>
> > > >>>Thanks,
> > > >>>
> > > >>>Yaron Nachman
> > > >>>
> > > >>>SEABRIDGE Ltd.
> > > >>>Tel:       972-9-7751359
> > > >>>Fax:      972-9-7751212
> > > >>>E-mail:  yaron.nachman@SeabridgeNetworks.com
> > > >>>
> > > >>>
> > > >>>_______________________________________________
> > > >>>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
> > > > 
> > > > 
> > > 
> > > 
> > > _______________________________________________
> > > 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  Wed Dec 27 15:58:27 2006
From: "Hamid Ould-Brahim" <hbrahim@nortelnetworks.com>
Subject: RE: IP Pseudo-wires
Date: Wed, 17 Nov 2004 12:02:55 -0500
Lines: 9
X-From: pwe3-bounces@ietf.org Wed Nov 17 18:32:41 2004
Return-path: <pwe3-bounces@ietf.org>
To: "Shah, Himanshu" <hshah@ciena.com>, "'Stewart Bryant'"
	<stbryant@cisco.com>, pwe3 <pwe3@ietf.org>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


> 
> ...and lets call that draft as 
> draft-balus-pwe3-ip-pseudowire-01.txt.. :-)
> 

Yes, indeed.

Hamid.


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: IP Pseudo-wires
Date: Wed, 17 Nov 2004 19:33:33 +0200
Lines: 50
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: pwe3 <pwe3@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-From: pwe3-bounces@ietf.org Wed Nov 17 18:49:08 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Yaakov Stein'" <yaakov_s@rad.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Yaakov and all,
I would not worry about THIS Charter violation.
We have already accepted the draft on HDLC and PPP PWs 
as a WG document (presumably based on consensus to add
these to the next Charter revision). So there is some
precedent here on doing some work that still is not,
but presumably soon will be chartered


Regards,
                                  Sasha Vainshtein
email:                         sasha@axerra.com <mailto:sasha@axerra.com> 
phone:                       +972-3-7569993 (office)
fax:                            +972-3-6487779
mobile:                      +972-52-8674833 


> -----Original Message-----
> From: Yaakov Stein [mailto:yaakov_s@rad.com]
> Sent: Wednesday, November 17, 2004 6:54 PM
> To: Stewart Bryant; pwe3
> Subject: RE: [PWE3] IP Pseudo-wires
> 
> 
>  
> > I have been thinking about the IP PW type that we call up in 
> > the control draft.
> > 
> > This is allowed to run over MPLS without the CW in order to 
> > allow ECMP. However I am concerned that this then breaks 
> > routing in the "client" layer.
> 
> It is also "out of charter".
> 
> The charter only mentions :
> 
>     Ethernet (DIX Ethernet (100M, 1G, 10G), IEEE 802.3, 802.1q (VLAN)
>     Frame Relay
>     ATM
>     TDM (e.g. DS1, DS3, SONET)
>     MPLS (over IP or L2TP only)
> 
> Y(J)S
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Florin Balus" <balus@nortelnetworks.com>
Subject: RE: IP Pseudo-wires
Date: Wed, 17 Nov 2004 14:00:28 -0500
Lines: 447
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C4CCD7.B4CE6AA3"
Cc: pwe3 <pwe3@ietf.org>, Mustapha Aissaoui <mustapha.aissaoui@alcatel.com>,
	"Shah, Himanshu" <hshah@ciena.com>
X-From: pwe3-bounces@ietf.org Wed Nov 17 20:08:52 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Stewart Bryant'" <stbryant@cisco.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: 213cf0777a99c4ccdd94bb20659dd28c
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C4CCD7.B4CE6AA3
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4CCD7.B4CE6AA3"


------_=_NextPart_001_01C4CCD7.B4CE6AA3
Content-Type: text/plain


Actually Luca told me in Washington he was going to remove the "control word
MUST NOT be used" text from the control draft following the enclosed email.

Also I mentioned during Himanshu's presentation at the L2VPN meeting we were
going to update the suggested format for IS-IS to make use of the
"Associated Channel" type introduced by the latest version of the pw cw
draft... The draft is currently suggesting the use (in a similar fashion) of
the equivalent field in the encapsulation proposed in VCCV.


Stewart,
Let me know if the current text addresses your concerns.
Regards,
Florin

> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On 
> Behalf Of Mustapha Aissaoui
> Sent: Wednesday, November 17, 2004 11:42 AM
> To: Shah, Himanshu
> Cc: pwe3; 'Stewart Bryant'
> Subject: Re: [PWE3] IP Pseudo-wires
> 
> 
> All,
> I initially suggested to Luca to remove the statement that 
> did not allow the control word. Thinking about it now, I 
> support taking the IP PW encapsulation text out of the 
> control draft. I assume the IANA codepoint will be maintained 
> for the purpose of signaling.
> 
> I believe the draft below is a good starting point for the 
> specification of this PW type.
> 
> Mustapha.
> ------------
> "Shah, Himanshu" wrote:
> > 
> > ...and lets call that draft as 
> draft-balus-pwe3-ip-pseudowire-01.txt.. 
> > :-)
> > 
> > /himanshu
> > 
> > > -----Original Message-----
> > > From: Stewart Bryant [mailto:stbryant@cisco.com]
> > > Sent: Wednesday, November 17, 2004 9:24 AM
> > > To: pwe3
> > > Subject: [PWE3] IP Pseudo-wires
> > >
> > >
> > >
> > > I have been thinking about the IP PW type that
> > > we call up in the control draft.
> > >
> > > This is allowed to run over MPLS without the CW
> > > in order to allow ECMP. However I am concerned
> > > that this then breaks routing in the "client"
> > > layer.
> > >
> > > If you allow ECMP, then the routing hellos
> > > will not go the same path at the data, and
> > > thus will not do their job. So you could
> > > have incomplete connectivity in the PW, but
> > > routing in the "client" layer would not know,
> > > and would not take appropriate action.
> > >
> > > There is also the issue of the IS-IS hellos
> > > needing to be carried that was bought up in the
> > > L2VPN WG.
> > >
> > > I think that we need to give serious thought to
> > > removing the IP encap material from the control
> > > draft and writing a stand-alone draft that
> > > gives proper consideration to all the issues
> > > of carrying an IP PW.
> > >
> > > - Stewart
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > 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
> 
> 


------_=_NextPart_001_01C4CCD7.B4CE6AA3
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: [PWE3] IP Pseudo-wires</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2>Actually Luca told me in Washington he was going to =
remove the &quot;control word MUST NOT be used&quot; text from the =
control draft following the enclosed email.</FONT></P>

<P><FONT SIZE=3D2>Also I mentioned during Himanshu's presentation at =
the L2VPN meeting we were going to update the suggested format for =
IS-IS to make use of the &quot;Associated Channel&quot; type introduced =
by the latest version of the pw cw draft... The draft is currently =
suggesting the use (in a similar fashion) of the equivalent field in =
the encapsulation proposed in VCCV.</FONT></P>
<BR>

<P><FONT SIZE=3D2>Stewart,</FONT>
<BR><FONT SIZE=3D2>Let me know if the current text addresses your =
concerns.</FONT>
<BR><FONT SIZE=3D2>Regards,</FONT>
<BR><FONT SIZE=3D2>Florin</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: pwe3-bounces@ietf.org [<A =
HREF=3D"mailto:pwe3-bounces@ietf.org">mailto:pwe3-bounces@ietf.org</A>] =
On </FONT>
<BR><FONT SIZE=3D2>&gt; Behalf Of Mustapha Aissaoui</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Wednesday, November 17, 2004 11:42 =
AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: Shah, Himanshu</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: pwe3; 'Stewart Bryant'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [PWE3] IP Pseudo-wires</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; All,</FONT>
<BR><FONT SIZE=3D2>&gt; I initially suggested to Luca to remove the =
statement that </FONT>
<BR><FONT SIZE=3D2>&gt; did not allow the control word. Thinking about =
it now, I </FONT>
<BR><FONT SIZE=3D2>&gt; support taking the IP PW encapsulation text out =
of the </FONT>
<BR><FONT SIZE=3D2>&gt; control draft. I assume the IANA codepoint will =
be maintained </FONT>
<BR><FONT SIZE=3D2>&gt; for the purpose of signaling.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I believe the draft below is a good starting =
point for the </FONT>
<BR><FONT SIZE=3D2>&gt; specification of this PW type.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Mustapha.</FONT>
<BR><FONT SIZE=3D2>&gt; ------------</FONT>
<BR><FONT SIZE=3D2>&gt; &quot;Shah, Himanshu&quot; wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ...and lets call that draft as </FONT>
<BR><FONT SIZE=3D2>&gt; draft-balus-pwe3-ip-pseudowire-01.txt.. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; :-)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; /himanshu</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; From: Stewart Bryant [<A =
HREF=3D"mailto:stbryant@cisco.com">mailto:stbryant@cisco.com</A>]</FONT>=

<BR><FONT SIZE=3D2>&gt; &gt; &gt; Sent: Wednesday, November 17, 2004 =
9:24 AM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; To: pwe3</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Subject: [PWE3] IP =
Pseudo-wires</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; I have been thinking about the IP PW =
type that</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; we call up in the control =
draft.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; This is allowed to run over MPLS =
without the CW</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; in order to allow ECMP. However I am =
concerned</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; that this then breaks routing in the =
&quot;client&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; layer.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; If you allow ECMP, then the routing =
hellos</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; will not go the same path at the =
data, and</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; thus will not do their job. So you =
could</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; have incomplete connectivity in the =
PW, but</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; routing in the &quot;client&quot; =
layer would not know,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; and would not take appropriate =
action.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; There is also the issue of the IS-IS =
hellos</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; needing to be carried that was bought =
up in the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; L2VPN WG.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; I think that we need to give serious =
thought to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; removing the IP encap material from =
the control</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; draft and writing a stand-alone draft =
that</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; gives proper consideration to all the =
issues</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; of carrying an IP PW.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; - Stewart</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; pwe3 mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; pwe3@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/pwe3" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/pwe3</A></FONT>=

<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; pwe3 mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; pwe3@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/pwe3" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/pwe3</A></FONT>=

<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; pwe3 mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; pwe3@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/pwe3" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/pwe3</A></FONT>=

<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT FACE=3D"Arial" SIZE=3D2 COLOR=3D"#000000"></FONT>&nbsp;

</BODY>
</HTML>
------_=_NextPart_001_01C4CCD7.B4CE6AA3--

------_=_NextPart_000_01C4CCD7.B4CE6AA3
Content-Type: message/rfc822
Content-Description: RE: [PWE3] draft-ietf-pwe3-cw-00.txt - LAST CALL

From balus@americasm01.nt.com  Wed Dec 27 15:58:27 2006
From: "Balus, Florin [CAR:6955:EXCH]" <balus@americasm01.nt.com>
To: Stewart Bryant <stbryant@cisco.com>, lmartini@cisco.com, pwe3
	<pwe3@ietf.org>
Subject: RE: [PWE3] draft-ietf-pwe3-cw-00.txt - LAST CALL
Date: Sun, 7 Nov 2004 17:55:48 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_003_01C4CCD7.B4CE6AA3"


------_=_NextPart_003_01C4CCD7.B4CE6AA3
Content-Type: text/plain


Stewart,Luca,

I understand the recommendation in section 2 of draft-ietf-pwe3-cw-00.txt -
"A PW carried over an MPLS PSN that uses the contents of the MPLS payload to
select the ECMP path SHOULD employ the PW Control Word described in Section
3 for data" - is directed to distinguish a PW payload from an "IP payload
carried over an MPLS PSN" - see also section 1 of the same document. 
 
draft-ietf-pwe3-control-protocol-12.txt - Section 4.6 (IP Layer2 Transport)
contains the statement: "The control word MUST NOT be used". It seems to me
that if we follow this recommendation for this specific type of PW, we will
run into the issue described in section 1 of draft-ietf-pwe3-cw-00.txt: i.e.
"The inability to ensure that all packets belonging to a PW follow the same
path also prevents the PW OAM [VCCV] mechanism from correctly monitoring the
PW."

Is it possible to remove the MUST from the above statement (or even better
all the text) from section 4.6 of draft-ietf-pwe3-control-protocol-12.txt?
Otherwise it looks to me like the 2 drafts are contradicting each other.
Regards,

Florin     

> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On
> Behalf Of Stewart Bryant
> Sent: Monday, November 01, 2004 8:04 PM
> To: pwe3
> Subject: [PWE3] draft-ietf-pwe3-cw-00.txt - LAST CALL
> 
> 
> This is the start of two week last call on
> 
> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw-00.txt
> 
> Last call will finish on 16th November 2004
> 
> Stewart
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 
> 

------_=_NextPart_003_01C4CCD7.B4CE6AA3
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: [PWE3] draft-ietf-pwe3-cw-00.txt - LAST CALL</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2>Stewart,Luca,</FONT>
</P>

<P><FONT SIZE=3D2>I understand the recommendation in section 2 of =
draft-ietf-pwe3-cw-00.txt - &quot;A PW carried over an MPLS PSN that =
uses the contents of the MPLS payload to select the ECMP path SHOULD =
employ the PW Control Word described in Section 3 for data&quot; - is =
directed to distinguish a PW payload from an &quot;IP payload carried =
over an MPLS PSN&quot; - see also section 1 of the same document. =
</FONT></P>

<P><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>draft-ietf-pwe3-control-protocol-12.txt - Section =
4.6 (IP Layer2 Transport) contains the statement: &quot;The control =
word MUST NOT be used&quot;. It seems to me that if we follow this =
recommendation for this specific type of PW, we will run into the issue =
described in section 1 of draft-ietf-pwe3-cw-00.txt: i.e. &quot;The =
inability to ensure that all packets belonging to a PW follow the same =
path also prevents the PW OAM [VCCV] mechanism from correctly =
monitoring the PW.&quot;</FONT></P>

<P><FONT SIZE=3D2>Is it possible to remove the MUST from the above =
statement (or even better all the text) from section 4.6 of =
draft-ietf-pwe3-control-protocol-12.txt? Otherwise it looks to me like =
the 2 drafts are contradicting each other. Regards,</FONT></P>

<P><FONT SIZE=3D2>Florin&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: pwe3-bounces@ietf.org [<A =
HREF=3D"mailto:pwe3-bounces@ietf.org">mailto:pwe3-bounces@ietf.org</A>] =
On</FONT>
<BR><FONT SIZE=3D2>&gt; Behalf Of Stewart Bryant</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Monday, November 01, 2004 8:04 PM</FONT>
<BR><FONT SIZE=3D2>&gt; To: pwe3</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: [PWE3] draft-ietf-pwe3-cw-00.txt - =
LAST CALL</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; This is the start of two week last call =
on</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw-00.txt" =
TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw=
-00.txt</A></FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Last call will finish on 16th November =
2004</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Stewart</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; pwe3 mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; pwe3@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/pwe3" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/pwe3</A></FONT>=

<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_003_01C4CCD7.B4CE6AA3--

------_=_NextPart_000_01C4CCD7.B4CE6AA3
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_000_01C4CCD7.B4CE6AA3--




From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Luca Martini <lmartini@cisco.com>
Subject: Re: TTL value of VC Label?
Date: Wed, 17 Nov 2004 12:03:12 -0700
Organization: Cisco Systems
Lines: 251
References: <4B6D09F3B826D411A67300D0B706EFDE0115D2BB@nt-exch-yow.pmc_nt.nt.pmc-sierra.bc.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pwe3@ietf.org, vach.kompella@alcatel.com,
	'Sasha Vainshtein' <Sasha@AXERRA.com>,
	'Stewart Bryant' <stbryant@cisco.com>
X-From: pwe3-bounces@ietf.org Wed Nov 17 20:19:38 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7) Gecko/20040620
X-Accept-Language: en-us, en, fr, it
To: Shahram Davari <Shahram_Davari@pmc-sierra.com>
In-Reply-To: <4B6D09F3B826D411A67300D0B706EFDE0115D2BB@nt-exch-yow.pmc_nt.nt.pmc-sierra.bc.ca>
X-PMX-Version: 4.7.0.111621
X-from-outside-Cisco: [10.32.241.115]
X-Scan-Signature: dd7e0c3fd18d19cffdd4de99a114001d
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org



TTL is a matter of local policy. Some people might want ttl=2 some  
ttl=64 some ttl=128 ...

I do not believe that the design should mandate what it is ....

it would be equivalent to mandating what the IP ttl should be ....

my 2c
Luca


Shahram Davari wrote:

>Sasha,
>
>When we say application specific and don't mandate TTL=2, 
>means you could set TTL=2 for the non-stitching p2p case.
>
>
>-Shahram
>
>  
>
>>-----Original Message-----
>>From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]On 
>>Behalf Of Sasha Vainshtein
>>Sent: Wednesday, November 17, 2004 6:41 AM
>>To: 'Stewart Bryant'
>>Cc: pwe3@ietf.org; vach.kompella@alcatel.com
>>Subject: RE: [PWE3] TTL value of VC Label?
>>
>>
>>Stewart and all,
>>I am not sure that striking out any reference to TTL=2
>>in the PW label is justified.
>>
>>As Eric has explained in this thread, the only reason
>>for striking it out is that stitched PWs would not
>>work. This is obviously correct, but, please note,
>>that stiched PWs are not in the Charter (at the moment)
>>and, what is not important, do not comply with the PWE3
>>architecture as presented in the document we are now
>>discussing! 
>>
>>In fact, setting TTL=2 is perfectly aligned with the current
>>PWE3 architecture (and this is why it has been mentioned
>>in the document)! 
>>
>>Of course, we are now discussing enhanced architecture that
>>would incorporate stitched PWs. But this would require a
>>consistent architecture document, and not just removal of
>>a couple of lines from the current one!
>>
>>What is wrong in the current document, is, IMHO, the ambiguous 
>>reference to "strict point-to-point applications": as defined 
>>in this architecture, the PWs are always point-to-point!
>>
>>E.g., this text suggests that setting TTL=2 would not work 
>>for PWs connecting Virtual Switch instances in VPLS applications.
>>Which is, IMHO, incorrect even for Hierarchical VPLS as defined in
>>http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-ldp-05.txt.
>>
>>So, may be a less drastic editing could suffice? E.g., what about
>>the following text:
>>
>>"The setting of the TTL value in the PW label is application 
>>dependent. Within the scope of this document, setting TTL 
>>to 2 is recommended as a precaution against mis-forwarding".
>>
>>Regards,
>>                                  Sasha Vainshtein
>>email:                         sasha@axerra.com 
>><mailto:sasha@axerra.com> 
>>phone:                       +972-3-7569993 (office)
>>fax:                            +972-3-6487779
>>mobile:                      +972-52-8674833 
>>
>>
>>    
>>
>>>-----Original Message-----
>>>From: Stewart Bryant [mailto:stbryant@cisco.com]
>>>Sent: Wednesday, November 17, 2004 12:24 PM
>>>To: vach.kompella@alcatel.com
>>>Cc: pwe3@ietf.org
>>>Subject: Re: [PWE3] TTL value of VC Label?
>>>
>>>
>>>
>>>
>>>Vach Kompella wrote:
>>>
>>>      
>>>
>>>>Actually, looking at it more carefully, is the question you 
>>>>        
>>>>
>>>are asking
>>>      
>>>
>>>>that the "TTL should be appropriately set to 2" be 
>>>>        
>>>>
>>stricken?  If so,
>>    
>>
>>>>yes, it should.
>>>>
>>>>The thread I thought you were referring to is the one below, which
>>>>brought up the original change to the text.  I cannot find any
>>>>subsequent threads that discuss removing the TTL=2 part.
>>>>        
>>>>
>>>Yes, I can only find the mail that said put it in, and
>>>cannot find any mail that say take it out. Hence my question to the
>>>list.
>>>
>>>It looks like a consensus for removal, but I will let the issue
>>>run for the traditional two weeks, then Danny and I will declare
>>>consensus one way or the other.
>>>
>>>- Stewart
>>>
>>>
>>>      
>>>
>>>>-Vach 
>>>>
>>>>
>>>>        
>>>>
>>>>>-----Original Message-----
>>>>>From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On 
>>>>>Behalf Of Vach Kompella
>>>>>Sent: Tuesday, November 16, 2004 6:38 PM
>>>>>To: pwe3@ietf.org
>>>>>Subject: FW: [PWE3] TTL value of VC Label?
>>>>>
>>>>>
>>>>>Stewart,
>>>>>
>>>>>Here's the beginning of the thread.  I support the change 
>>>>>which was pretty much what we had agreed to at that time.  
>>>>>The thread runs from 4/30/2003 through 5/7/2003, when Danny 
>>>>>asked for the following text (suggested by Luca) to be the 
>>>>>replacement text:
>>>>>
>>>>>----------------------------
>>>>>On 5/7/03 3:49 PM, "Luca Martini" <luca@level3.net> wrote:
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>>>How about this ?
>>>>>>
>>>>>>"The setting of the TTL value in the PW
>>>>>>label is application dependent, however in a strict 
>>>>>>            
>>>>>>
>>point to point
>>    
>>
>>>>>>application the TTL should be appropriately set to 2"
>>>>>>            
>>>>>>
>>>>>I like this.  Does anyone have objections to updating the 
>>>>>current document with something along these lines?
>>>>>
>>>>>-danny
>>>>>----------------------------
>>>>>
>>>>>-Vach 
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>>>-----Original Message-----
>>>>>>From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On
>>>>>>Behalf Of Yaron Nachman
>>>>>>Sent: Wednesday, April 30, 2003 12:23 AM
>>>>>>To: 'pwe3@ietf.org'
>>>>>>Cc: Eli Angel; Ilya Vershkov
>>>>>>Subject: [PWE3] TTL value of VC Label?
>>>>>>
>>>>>>
>>>>>>Hi,
>>>>>>
>>>>>>I have just noticed that in the yesterday-updated
>>>>>>draft-martini-l2circuit-encap-mpls-05.txt, the TTL value to 
>>>>>>be placed by an Ingress LER on the VC Label is 2. I have 
>>>>>>noticed in the past that it was changed to 255.
>>>>>>
>>>>>>So, is it 2 or 255? or even some other value??
>>>>>>
>>>>>>Thanks,
>>>>>>
>>>>>>Yaron Nachman
>>>>>>
>>>>>>SEABRIDGE Ltd.
>>>>>>Tel:       972-9-7751359
>>>>>>Fax:      972-9-7751212
>>>>>>E-mail:  yaron.nachman@SeabridgeNetworks.com
>>>>>>
>>>>>>
>>>>>>_______________________________________________
>>>>>>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
>>>>
>>>>
>>>>        
>>>>
>>>_______________________________________________
>>>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  Wed Dec 27 15:58:27 2006
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-pwe3-control-protocol-13.txt
Date: Wed, 17 Nov 2004 15:44:42 -0500
Lines: 102
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Cc: pwe3@ietf.org
X-From: pwe3-bounces@ietf.org Wed Nov 17 22:22:01 2004
Return-path: <pwe3-bounces@ietf.org>
To: i-d-announce@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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

--NextPart

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

	Title		: Pseudowire Setup and Maintenance using LDP
	Author(s)	: L. Martini, et al.
	Filename	: draft-ietf-pwe3-control-protocol-13.txt
	Pages		: 41
	Date		: 2004-11-17
	
Layer 2 services (such as Frame Relay, ATM, ethernet) can be
   'emulated' over an IP and/or MPLS backbone by encapsulating the layer
   2 PDUs and then transmitting them over 'pseudowires'. It is also
   possible to use pseudowires to provide low-rate TDM and SONET circuit
   emulation over an IP and/or MPLS network. This document specifies a
   protocol for establishing and maintaining the pseudowires, using
   extensions to LDP. Procedures for encapsulating layer 2 PDUs are
   specified in a set of companion documents.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-control-protocol-13.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-control-protocol-13.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-control-protocol-13.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"

From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: [Fwd: [L2tpext] List consensus items]
Date: Thu, 18 Nov 2004 13:28:14 +0000
Lines: 40
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-bounces@ietf.org Thu Nov 18 14:50:28 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: pwe3 <pwe3@ietf.org>
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

FYI - the first item

Stewart

-------- Original Message --------
Subject: [L2tpext] List consensus items
Date: Thu, 18 Nov 2004 08:00:57 -0500
From: W. Mark Townsley <townsley@cisco.com>
To: l2tpext@ietf.org


At the last IETF meeting, the sense of the room was positive for the 
following
two items. I would like to poll the list to ensure consensus. If you 
object to
either of these, please comment.

1. Establish draft-galtzur-l2tpext-tdm-01.txt as a WG document

2. Combine three drafts, draft-ietf-l2tpext-sesinfo-04.txt,
draft-mistretta-l2tp-infomsg-01.txt and
draft-nmcgill-l2tp-radius-ext-nas-port-02.txt into a single WG text. AVP
definitions to be coordinated with Tunnel Switching document with 
respect to
stacking information through an LTS.

Thanks,

- Mark







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


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: nits
Date: Fri, 19 Nov 2004 19:13:35 +0000
Lines: 6
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-bounces@ietf.org Fri Nov 19 20:23:34 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: pwe3 <pwe3@ietf.org>
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

If anyone needs the web interface to the nits checker,
it can be found at:

http://ietf.levkowetz.com/tools/idnits/idnits.pyht

Stewart


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-pwe3-fragmentation-07.txt
Date: Fri, 19 Nov 2004 15:18:30 -0500
Lines: 95
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Cc: pwe3@ietf.org
X-From: pwe3-bounces@ietf.org Fri Nov 19 22:12:23 2004
Return-path: <pwe3-bounces@ietf.org>
To: i-d-announce@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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

--NextPart

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

	Title		: PWE3 Fragmentation and Reassembly
	Author(s)	: A. Malis, M. Townsley
	Filename	: draft-ietf-pwe3-fragmentation-07.txt
	Pages		: 14
	Date		: 2004-11-19
	
This document defines a generalized method of performing
fragmentation for use by PWE3 protocols and services.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-fragmentation-07.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-fragmentation-07.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-fragmentation-07.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"

From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Danny McPherson <danny@tcb.net>
Subject: PWE3 Draft Minutes - IETF 61
Date: Sat, 20 Nov 2004 20:34:26 -0700
Lines: 458
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-bounces@ietf.org Sun Nov 21 04:44:28 2004
Return-path: <pwe3-bounces@ietf.org>
To: pwe3 <pwe3@ietf.org>
X-Mailer: Apple Mail (2.619)
X-Scan-Signature: 32604d42645517c44d778f1d111b40a6
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


Folks,
Please send me comments and corrections ASAP.

Thanks!

-danny

[snip]

1530-1730 Afternoon Session II; Lincoln East

Administrivia
-------------


Chairs: Danny McPherson & Stewart Bryant
Minutes: Matthew Bocci
Slides are available on pwe3.tcb.net

Charter & Draft Status - Stewart Bryant & Danny McPherson
---------------------------------------------------------

Working on updating charter with ADs. Danny to send email
  to list with prposed updated and goals and milestones.

Draft status: Stewart

Dependencies:
Lots of dependencies between drafts. Cannot become RFCs until
  dependencies become RFCs. Very important to get this right.
  Draft text may change if dependency text changes.

Stewart carried out a dependency analysis: this is shown
  and looks very complex.

This will drive order in which we send documents to
  RFC editor.

Concerns: Not all normative references are really
  normative. Authors need to double check this.  Also
  need to make sure all things that should be normative
  are called out as such.  Need to check for
  informative refs and docs with no normative
  references.

Base requirements now an RFC.

Architecture: list of dependencies, but one may not be
  correct. Edits sent to the list. Now in editors queue.
  Waiting for fragmentation and L2TP.  This will be RFC.

Fragmentation: needs an updated. Encap refs can be
  moved to control word references.
Andy Malis: Refs to arch can also be changed to refs
  to CW.
Stewart: not sure this is allowed as arch is
  informational.

Arch needs frag, needs control, and control doesn't
  have dependencies.

Luca Martini: Architecture doc should be an informative
  reference becasue you define CW in architecture.

Stewart: Fragmentation called up 2 bits in CW.
Yakov Stein: CW has to be standards track because
  of 1st 4 bits

Luca Martini: Every documents defines the CW bits
  that it uses. CW document is the generic template.

Mark Townsley: would be preferable if description
  was all in one place.

Yakov Stein: important to keep things the way they
  are now for expediency

Eric Rosen: will confise the IESG

Control Word Draft: Most refs to arch refer to sec
  5 and could be deleted. These could be changed to
  arch.   Will respin and send up.

IANA: This is in last call and will be sent out
  as soon as this is completed. Needed to set up the
  registries. Also lots of requests to stabalise code
  points.


Control : This is one of the most strategic docs.
  Past last call, but keeps getting minor change
  requests. This is an urgent gating draft. Need to
  take a hard line on this.

Luca Martini: Also some editorial nits that need
  to be fixed.

Stewart: as long as protocol works, need to draw
  a line in the sand.

ATM and Ethernet: Had 1st go of AD review. A
  few edits to fix.

Thomas: very close to last call.

TDM Reqs in Thomas' queue

SONET needs TDM requirements to get AD review
  before progressing.

SATOP sent to Thomas, but want to resolve UDP
  issues first.

CESoPSN is informational, but want to resolve
  UDP situation too.

HDLC encap: Needs a respin to fix refs.
  Completed last call.

Frame Relay: Needs some TLC. A get well package
  has been agreed, and should see a new rev
  shortly. Style out of step with rest of
  document set. terms need fixing.

Yakov Stein: Titles of encap drafts could be
  standardised or made more consistent.

VCCV: Pressure to move this on. It went to
  last call. Dave Allen's comments have not yet
  been resolved: should be in rev 04, but this
  has not been published yet.  Needs a serious
  edit pass, and should be last called. Depends
  on BFD and LSP-ping.

MIBs: these have a hge cross dependency list.
  Need to make sure procedures are published
  before.

FCS retention: Has standard encap dependencies.
  Not in last call yet.

Andy Malis: it is ready for last call.

Cell transparent mode ready too.
Stewart:

TDMoIP: Need to resolve UDP issue. Appendix
  depends on VCCV. Waiting for comments on 2
  OAM issues.

OAM messag mapping: Big dependencies, so wait
  for others to get out of the way.

Plan:
1. Get -iana-allocation- to IESG
2. Finish -pwe3-cw- and send to IESG
3. Edit -control-protocol- to sort out refs
   and send to IESG
4. Edit ?fragmentation- and then send to IESG
At this point we have the platform needed to
   progress the encap drafts
5) -ethernet-encap-
6) -atm-encap-
Get TDM requirements to IESG, then the TDM encaps
7) -tdm-requirements-
8) -satop-
9) -cesopsn
Then finish the following encaps as they become available
<draft-ietf-pwe3-frame-relay-03.txt>
<draft-ietf-pwe3-hdlc-ppp-encap-mpls-03.txt>
<draft-ietf-pwe3-sonet-09.txt>

When we have made progress on the above we will
  promote the other work to the priority list


Architecture draft is in editors queue. Waiting on
  frag and L2TP. CW dtaft will be standard. Arch
  will be informational.

Yakov Stein: why is CW standards track, if it is
  not refered to as normative in other docs.

Luca Martini; Titles are not consistent. Most say
  MPLS/IP, some say just MPLS.... Want comments on
  changing all of the titles and making them
  consistent.

Danny: take to list.

Mustapha: is CW is informational, why not just
  merge back to the architecture draft.

Danny agrees that this is an issue that needs
  to be addressed.  Will take offline.



PW CW - Stewart & Danny
-----------------------
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw-00.txt


There was lots of work after last IETF. Introduced associated
  channel concept. Only use of 001 encapsualtion is for associated
  channel for OAM traffic. This needs a formal definition for
  associated channel. Suggestions to the list on this. Other
  format ID values are available for additional purposes.

Yakov Stein: word channel clashes with the use in the
  architecture draft Stewart: propose some text to the
  mailing list.

Channel type will have its own registry. Plan is to grandfather
  VCCV value (21). Some errors in the text around IANA
  assignment.



UDP Statement to ITU - Stewart
------------------------------

This is one of the most discussed issues. TDM encaps are
  being pursued in SG13 as well. UDP encaps are only used by
  low speed TDM.  IETF documents are vague on use of UDP.
  Need to resolve this before we can go forward. The ITU
  started to talk about introducing an expected mechanism
  for handling the ports. 5 techniques proposed in
  liaison. Extensive comment on this to the list. Unable
  to reach consensus. Statement proopsed to the list.
  Essentially says PWE3 deals with L2TP, and MPLS
  tunnelled over IP. Unable to reach consensus on whether
  we need a 3rd method, so unable to give advice to
  ITU on where to go next. However, are willing to listen
  to proposals on how to carry PW over UDP, but anyway
  will need to consider issues such as congestion,
  security, and specific application.


UDP Encapsulation - Yaakov Stein
--------------------------------

Service provider model is presented. Emulation is PE to
  PE. IWF is located in the PE. AC is natve service.  Encap
  sits at the PE. Becomes MPLS at the PE. However, another
  model is that the iwf is at the CE. The AC does not
  run the native circuit. 3 possibilities:

- MPLS AC
- UDP/IP AC
- other AC possibilities (L2TP, MPLS over IP, native
    service over IP using GRE, etc)

Lively thread on the list. Over 50 emails from 16 participants.
Advantages: UDP/IP familiar to customer base, PW label as UDP
  port no. reduces overhead, already extensively deployed for TDM PWs,
  reuse of AVT protocols, simplify NAT traversal.

Disadvantages: had to provide QoS without c/o pt-pt trail.
  Cannot be layer network above UDP. UDP doesn't scale, not
  enough port numbers and increases NAT/firewall state. Need
  protocol for UDP port signalling. UDP checksum needs to be
  calculated. Why a new PW type at a late stage? Security
  and congestion control

Other comments: need to reply to ITU liaison, PWE charter
  aimed at operators, not enterprise customers, wrong, but
  how to stop enterprise using it, no consensus, should
  divert to AVT, but CE-CE PWs not in AVT charter, UDP
  OK for VoIP since adapts an application, some comments
  seem to rule out MPLS

Presents an rebuttal:
- QoS similar to LDP based MPLS or L2TP
- Enterprises don't need large number of UDP ports
- Scales better than VoIP today
- can use manual port provisioning
- UDP checksum can simply be set to 0
- PW type has been in the charter from day 1
- Security: LDP and L2TP protocols are similarly unsafe
- Congestion similar to L2TP

Proposal:
Explicitly limit UDP/IP to enterprises (CE-CE case)
- only allow manual provisioning
- enterprise responsible to security, congestion avoidance
- MPLS should be used if large numberof PWs needed.

Stewart: would like comments to help draft ITU response

Sahsa: Agrees that there is no sense in developing a
  control protocol for UDP PWs. Don't understand what
  enterprise PWs means.  If it connects to a class 5
  switch, what is it? ALso not sure that admission
  control should be up to the customer.

Yakov Stein: On congestion avoidance, that link that
  is UDP will sufer. SP can discard excess traffic.
  The access PW is the point from the CE to the core
  network.

Sasha: Confused. Are UDP PWs aonly a part of Multi
  hop PWs?

Yakov: yes

Sasha: don't know what to do with MH PWs

Eric Rosen: is is too late to remove this TDM from
  charter entirely?

Stewart: many people want to work on this

Eric: if you want to get this though, stop drawing
  attention to the problems e.g. NAT, signalling, how
  you do multiplexing, seems to need to be manually
  configured to interoperate. Solution is to take UDP
  out and leave up to SG13, or only have manual
  configuration. IESG may still notice this. Better
  to leave this in the hands of the ITU.

Luca Martini: Be careful and write a good security
  section. You are mixing control protocol with data
  planes. We are very exposed here.

Danny: We are trying to define protocols, not how
  and where they are deployed. A lot of concern on
  how to scope enterprise vs. service provider here.
  We need to assume the protocols defined here will
  be deployed in the Internet.


Stewart: can either:
- not respond
- say unable to reach consesus
- say we recognise that there are limited cases where
UDP would be appropriate, supported by manual
  configuration

Scott Bradner: You have about a week to honor
  tradition and not respond, but it would be
  better to send them a response

Thomas Narten: be pragmatic and reasonable. If we
  don't respond, what will happen?
Stewart: we have an opinion as to how UDP is correctly
  operated. We have a duty of care.
Yakov Stein: reason this was sent was that this was
  going to be progressed in SG13. If we cannot reach
  consensus, SG13 wil l do what it wants.
Scott Bradner: ITU is trying to work with us. We
  should cooperate going forward, even if it is to
  say that we don't have an opinion. We must not
  ignore them.
Thomas Narten: AGrees. We can give our thoughts.
  We may not like what they want to do, but ghould
  explain why.
Mark Townsley: could say PWE3 doesn't care. Is there
  some work to do at an IAB level on what you do with UDP?

Craig White: We do need to send a fairly strong
  statement similar to what eric expressed, but
  need to be cognisant of the fact that they have
  implementations. Need to say that on the Internet,
  this is not an appropriate use, but may be
  appropriate in a private network. be aware of
  issues if it gets connected to Internet at any
  time.
Scott Bradner: What is magic about UDP in this
  context?
Stewart: this was not an issue until it was noticed
  that we needed a port assignment protocol
Scott Bradner: This working group was formed with
  the assumption of UDP and MPLS
Craig: congestion avoidance problem with UDP
Scott: no real difference
Yakov Stein: ITU would be happy to hear that we only
  want manual configuration.
Luca Martini: We also have an implementation of this.
  Bottom line is that a better design is L2TPv3 and
  this should be used instead. IETF thinks this is
  a better idea.
Eric Rosen: 2 issues: signalling. Suggestion that
  you could use LDP, with port numbers instead of
  labels. DO you use source or destination port?
  What about NATs? not sure we can come to
  consensus, except you need to manually configure
  it.

Stewart: We do not recommend UDP, but L2TP. If
  you use UDP, you so manual config.

Yakov Stein: why?

Stewart: Responds saying we recommend that you
  only do manual configuration of the ports.

Mark Townsley: ...and if you want to do
  automatic configuration, use L2TPv3 Issue with
  UDP is that it can cause problems for NATs. Some
  of the arguments made on the list are significant.

Yakov Stein: why does RTP group get away with this?

Shasha: Neither MPLS nor L2TP are suitable for
  NAT traversal. Could say: No signalling protocol,
  should not be used in NAT environment. Agree
  that there is substantially more VoIP and so
  we could say that UDP already used for VoIP
  sessions with operational success.

Mark Townsley: L2TPv3 deigned to run over UDP.
  Every NAT knows how to do L2TPv3 as in RFC2661
Thomas Narten: Liaison doesn't ask if it is a
  good or a bad thing. It asks how to do port
  number stuff. We should answer the question.

Stewart: Our advice is that this is only done
  in a manually configured mode, and anything
  more advanced should be made as a proposal
  to the PWE3 group.

Yakov Stein: pick one and send it back already!
  Pick manually configured, but use L2TPv3 for
  signalled

Consensus around this. Propose to the mailing
  list by Friday afternoon.



PW Multi-Hop Requirements - Luca Martini
----------------------------------------

Presents the outcome of the requirements team.

Last IETF was a discussion about PW stitching. Since
  then, we had a long drawn out email thread. Concluded
  we needed a requirement document.

Document not achieved by this IETF deadline.

Met face to face. We are regrouping, and trying to
  produce a draft by the end of november
  concentrating on requirements for this technology.
  This will guide if we need to do any more protocol
  work.


Open Microphone
---------------

Luca Martini: What is the state of the rechartering?
Danny: Will provide an update on the charter, goals
  and milestones on the mailing list.

Meeting Adjourned


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: draft-ietf-pwe3-fragmentation-07.txt - LAST CALL
Date: Mon, 22 Nov 2004 14:21:05 +0000
Lines: 170
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="------------090309040900070404050102"
X-From: pwe3-bounces@ietf.org Mon Nov 22 15:27:22 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: pwe3 <pwe3@ietf.org>
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.
--------------090309040900070404050102
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

This is the start of two week last call for
draft-ietf-pwe3-fragmentation-07.txt.

Last call will end Tuesday 7th December 2004

Stewart



-------- Original Message --------
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-fragmentation-07.txt
Date: Fri, 19 Nov 2004 15:18:30 -0500
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
CC: pwe3@ietf.org

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

	Title		: PWE3 Fragmentation and Reassembly
	Author(s)	: A. Malis, M. Townsley
	Filename	: draft-ietf-pwe3-fragmentation-07.txt
	Pages		: 14
	Date		: 2004-11-19
	
This document defines a generalized method of performing
fragmentation for use by PWE3 protocols and services.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-fragmentation-07.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-fragmentation-07.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-fragmentation-07.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 ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY
-------------------------------------------------------------------------
In order to maintain computing infrastructure integrity, Cisco Systems
Enterprise Messaging Services and InfoSec teams have set a mail policy
disallowing executable attachments in email.

This message contained an executable attachment type that is prohibited
by this policy. The attachment has been removed from this message and
copied to quarantine by our systems. It will be held in quarantine for
seven days in the event that the content needs to be retrieved.

Please be aware many viruses attempt to look like legitimate email or
notifications from anti-virus systems. We will clearly mark a seperation
between our notifications and the original email as follows:

   "CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY"

For further reference information about viruses and email antivirus
efforts within Cisco, please visit:

http://wwwin.cisco.com/it/ems/services/antiviral

If your concern isn't addressed by the information in this notification
or the above web page, you may open a support request:

http://wwwin.cisco.com/support/

Select "Messaging", "Email-Related", "Mail Routing"

Please include in the text of your case the following information:

* Full headers of the message. Documentation on displaying the full
headers is available at this URL:

http://wwwin.cisco.com/support/library/faqs/solution002471.html

* This unique quarantine identifier: iAJLCLX7011421

If the matter is urgent, you may follow up by calling one of the below
referenced numbers. Please make every effort to provide the above
requested information via the support web tool prior to calling as it
will greatly aid the resolution of your issue.

Americas:
1 408 526 8888

Asiapac
+61 2 8446 8888

EMEA
+31 20 485 4888

Japan
+81 3 5549 6888

US (Toll Free)
1| 800| 888| 8187| (ext.68888)

Thank you for your cooperation,

Enterprise Messaging Services
Cisco Systems, Inc


--------------090309040900070404050102
Content-Type: text/plain;
	name="file:///D|/DOCUME%7E1/STBRYANT/LOCALS%7E1/TEMP/nsmail.txt"
Content-Disposition: inline;
	filename="file:///D|/DOCUME%7E1/STBRYANT/LOCALS%7E1/TEMP/nsmail.txt"
Content-Transfer-Encoding: 7bit

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


--------------090309040900070404050102
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

--------------090309040900070404050102--





From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Adrian Farrel" <adrian@olddog.co.uk>
Subject: Re: draft-ietf-pwe3-fragmentation-07.txt - LAST CALL
Date: Mon, 22 Nov 2004 20:11:58 -0000
Lines: 46
References: <41A1F5D1.40308@cisco.com>
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Cc: andy.malis@tellabs.com, mark@townsley.net,
	Stewart Bryant <stbryant@cisco.com>
X-From: pwe3-bounces@ietf.org Mon Nov 22 22:54:00 2004
Return-path: <pwe3-bounces@ietf.org>
To: "pwe3" <pwe3@ietf.org>
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-OriginalArrivalTime: 22 Nov 2004 21:09:48.0060 (UTC)
	FILETIME=[993BDDC0:01C4D0D7]
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Hi,

> This is the start of two week last call for
> draft-ietf-pwe3-fragmentation-07.txt.
>
> Last call will end Tuesday 7th December 2004

Some minor comments (nits).
Apologies for not having followed the evolution of this draft in detail.

Adrian
===
The expansion of acronyms at first usage seems patchy.
- PWE3 is used in the abstract and title and should probably be expanded in both those
places
- PWE3, PSN and PDU in section 2
- CE and PE in section 3

Section 4
    use fragmentation MUST be provisioned in the sender.
s/provisioned/configured/

Section 5.1
    Deployments MUST avoid a situation which relies upon a combination
    of IP and PW fragmentation and reassembly on the same node. Such
I don't believe you can specify this as a MUST in a protocol spec. The best you can do is
"SHOULD" and probably you ought to use "should".

Section 5.4.2
    MRRU (Maximum Reassembled Receive Unit AVP), attribute number TBD2,
    is the maximum size in octets of a reassembled frame, including any
    PW framing, but not including the L2TP encapsulation or L2-specific
    sublayer. Presence of this AVP signifies the ability to receive PW
    fragments and reassemble them. Packet fragments MUST NOT be sent to
    an implementation which has not received this value from its peer
    in a control message.
Hopefully the confusion is just mine!
Do you mean...
    Packet fragments MUST NOT be sent *by*
    an implementation which has not received this value from its peer
    in a control message.
If you do actually mean what you say then some re-wording to stress this might be helpful.

Section 7
    This document does not define any new values for IANA to maintain.
Looks like the subsequent text defines new values for IANA to maintain?


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: neil.2.harrison@bt.com
Subject: RE: PWE3 Draft Minutes - IETF 61
Date: Wed, 24 Nov 2004 14:36:44 -0000
Lines: 31
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-bounces@ietf.org Wed Nov 24 15:42:24 2004
Return-path: <pwe3-bounces@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
content-class: urn:content-classes:message
Thread-Topic: [PWE3] PWE3 Draft Minutes - IETF 61
Thread-Index: AcTPfNJnTW8vk+loSzyNAMIXKVecagCrXLrw
To: <danny@tcb.net>, <pwe3@ietf.org>
X-OriginalArrivalTime: 24 Nov 2004 14:36:45.0208 (UTC)
	FILETIME=[0595B980:01C4D233]
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: quoted-printable
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Danny,  Thanks for the notes.

I have an observation on the issue of PWs over UDP.  Please see
below....I have taken a couple of extracts:

<snipped>

> UDP Statement to ITU - Stewart
> ------------------------------
><snipped>

> Yakov Stein: reason this was sent was that this was
>   going to be progressed in SG13. If we cannot reach
>   consensus, SG13 will do what it wants.
<snipped>

> Yakov Stein: ITU would be happy to hear that we only
>   want manual configuration.

It's my understanding (from the BT guy present in Q5/SG13) that there
are no SPs asking for this in ITU, and only one manufacturer is pushing
it there.  I don't recall hearing any SPs supporting this on the PWE3
list either (and I did ask a couple of times), or indeed any other
manufacturers strongly supporting it except the same one.  So I don't
want IETF to get the impression there are whole bunch of SPs in ITU
baying for this and intend to use it in weird/wonderful ways when
(AFAIK) there are none.

Please correct me if any folks know otherwise.

regards, Neil


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: PWE3 Draft Minutes - IETF 61
Date: Wed, 24 Nov 2004 19:00:11 +0200
Lines: 13
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-bounces@ietf.org Wed Nov 24 18:29:42 2004
Return-path: <pwe3-bounces@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] PWE3 Draft Minutes - IETF 61
Thread-Index: AcTPfNJnTW8vk+loSzyNAMIXKVecagCrXLrwAAcXliA=
To: <neil.2.harrison@bt.com>, <danny@tcb.net>, <pwe3@ietf.org>
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: quoted-printable
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

 Neil,=20

Actually there are quite a few manufacturers doing this,=20
and interested in its becoming a standard.

About service providers, as I stressed in my talk
(which unfortunately you were not present to hear,
 but you can see the slides on Danny's site)
this solution is for the enterprise (CE-to-CE) case,
not for the SP (PE-to-PE) one.


Y(J)S


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: ATM Transparent Cell - LAST CALL
Date: Mon, 29 Nov 2004 14:28:20 +0000
Lines: 8
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-bounces@ietf.org Mon Nov 29 15:49:21 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: pwe3 <pwe3@ietf.org>
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is the start of two week last call for

PWE3 ATM Transparent Cell Transport Service
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cell-transport-01.txt

Last call will end Tuesday 14th December 2004

Stewart


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Frame Check Sequence Retention - LAST CALL
Date: Mon, 29 Nov 2004 14:29:24 +0000
Lines: 10
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-bounces@ietf.org Mon Nov 29 15:50:12 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: pwe3 <pwe3@ietf.org>
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is the start of two week last call for

PWE3 Frame Check Sequence Retention
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-fcs-retention-02.txt

Last call will end Tuesday 14th December 2004

Stewart

FCS retention


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: ATM Transparent Cell - LAST CALL
Date: Mon, 29 Nov 2004 18:23:33 +0200
Lines: 70
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: pwe3 <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Mon Nov 29 17:52:44 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Stewart Bryant'" <stbryant@cisco.com>, "Andrew G. Malis (E-mail)"
	<Andy.Malis@tellabs.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Andy, Stewart and all,
I suggest to consider the following minor edits to the draft 
in question:

1. Specify that the PW Type to be used for the service in
   question MUST be 0x0009 (ATM n-to-one VCC cell transport)
   as per IANA allocation draft 

2. Specify that:
   - if Maximum Number of concatenated ATM cells is
     not part of the Interface Parameters field of FEC 128 or
     of the Interface Parameters TLV going with FEC 129, 
     cell concatenation MUST NOT be used
   - if this parameter is specified, the number of concatenated 
     cells per PW packet used by the PE receiving its value 
     MUST NOT exceeed the value distributed by the peer PE

3. Add a normative reference to the IANA allocation draft 
   (for the PW type and Interface Parameter ID)

4. Clarify which failures (only the physical port?, any other?)
   at one end of the PW must be reported to the peer PE, and
   which status values in the Status TLV must be used for this 
   purpose. E.g., is there any linkage between ILMI on the
   CE<-->PE link and status reports across the PW?

IMHO these edits would prevent any ambuiguities in future.
They would also make the already existing reference to the
Control Protocol draft meaningful (today it is only used
to specify that "no new security issues are added" -
rather vague, IMHO, since setup/maintenance of the PWs
is not mentioned at all.

I also suggest to consider collapsing Section 4.2.2
of the Control Protocol draft (replacing it with the
informative reference to the ATM Transparent Cell draft)
to avoid duplication. But this is not directly related 
to the Last Call of the ATM Transparent Cell draft.

Regards,
                                  Sasha Vainshtein
email:                         sasha@axerra.com <mailto:sasha@axerra.com> 
phone:                       +972-3-7569993 (office)
fax:                            +972-3-6487779
mobile:                      +972-52-8674833 


> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]
> Sent: Monday, November 29, 2004 4:28 PM
> To: pwe3
> Subject: [PWE3] ATM Transparent Cell - LAST CALL
> 
> 
> This is the start of two week last call for
> 
> PWE3 ATM Transparent Cell Transport Service
> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cell-trans
> port-01.txt
> 
> Last call will end Tuesday 14th December 2004
> 
> Stewart
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: neil.2.harrison@bt.com
Subject: RE: Frame Check Sequence Retention - LAST CALL
Date: Mon, 29 Nov 2004 16:50:37 -0000
Lines: 40
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-bounces@ietf.org Mon Nov 29 18:14:30 2004
Return-path: <pwe3-bounces@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
content-class: urn:content-classes:message
Thread-Topic: [PWE3] Frame Check Sequence Retention - LAST CALL
Thread-Index: AcTWIvsvwgW3/REaQceLXvSNwlF5VAADn7ag
To: <pwe3@ietf.org>
X-OriginalArrivalTime: 29 Nov 2004 16:50:37.0640 (UTC)
	FILETIME=[8D5A5480:01C4D633]
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: quoted-printable
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Couple of observations on this draft:

1	I don't agree the default behaviour should be strip the
FCS......but there is a much more important principle at stake here:
The default behaviour of any client/server relationship should always be
complete client transparency (all planes) over the server.

2	The data-plane behaviour should be consistent irrespective of
how the trail is set-up.  This draft talks about LDP-based signalling
for the XoverMPLS case (though there is a cursory mention of management
provisioning).  However, it should apply to all signalling cases, eg the
MH-PW discussions where RSVP-TE is also being considered. =20

regards, Neil

> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On=20
> Behalf Of Stewart Bryant
> Sent: 29 November 2004 14:29
> To: pwe3
> Subject: [PWE3] Frame Check Sequence Retention - LAST CALL
>=20
>=20
> This is the start of two week last call for
>=20
> PWE3 Frame Check Sequence Retention=20
> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-fcs-retent
ion-02.txt

Last call will end Tuesday 14th December 2004

Stewart

FCS retention


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


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Andrew G. Malis" <andymalis@comcast.net>
Subject: RE: Frame Check Sequence Retention - LAST CALL
Date: Mon, 29 Nov 2004 14:16:28 -0500
Lines: 59
References: <0536FC9B908BEC4597EE721BE6A353890A9F1563@i2km07-ukbr.domain1.systemhost.net> <0536FC9B908BEC4597EE721BE6A353890A9F1563@i2km07-ukbr.domai
	n1.systemhost.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: pwe3@ietf.org
X-From: pwe3-bounces@ietf.org Mon Nov 29 20:24:03 2004
Return-path: <pwe3-bounces@ietf.org>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
To: neil.2.harrison@bt.com
In-Reply-To: <0536FC9B908BEC4597EE721BE6A353890A9F1563@i2km07-ukbr.domai
	n1.systemhost.net>
References: <0536FC9B908BEC4597EE721BE6A353890A9F1563@i2km07-ukbr.domain1.systemhost.net>
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Neil,

Thanks for your comments.  Unfortunately, I can't do anything about comment 
1 without the WG changing all of the existing encapsulation drafts.  On 
comment 2, I agree, if the WG makes RVSP-TE-signaled pseudowires a work 
item, then we'll be sure to get the capability to signal FCS retention in 
there.  Maybe in that case we can even make it the default! :-)

Cheers,
Andy

---------

At 11/29/2004 04:50 PM +0000, neil.2.harrison@bt.com wrote:
>Couple of observations on this draft:
>
>1       I don't agree the default behaviour should be strip the
>FCS......but there is a much more important principle at stake here:
>The default behaviour of any client/server relationship should always be
>complete client transparency (all planes) over the server.
>
>2       The data-plane behaviour should be consistent irrespective of
>how the trail is set-up.  This draft talks about LDP-based signalling
>for the XoverMPLS case (though there is a cursory mention of management
>provisioning).  However, it should apply to all signalling cases, eg the
>MH-PW discussions where RSVP-TE is also being considered.
>
>regards, Neil
>
> > -----Original Message-----
> > From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On
> > Behalf Of Stewart Bryant
> > Sent: 29 November 2004 14:29
> > To: pwe3
> > Subject: [PWE3] Frame Check Sequence Retention - LAST CALL
> >
> >
> > This is the start of two week last call for
> >
> > PWE3 Frame Check Sequence Retention
> > http://www.ietf.org/internet-drafts/draft-ietf-pwe3-fcs-retent
>ion-02.txt
>
>Last call will end Tuesday 14th December 2004
>
>Stewart
>
>FCS retention
>
>
>_______________________________________________
>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  Wed Dec 27 15:58:27 2006
From: "Andrew G. Malis" <andymalis@comcast.net>
Subject: RE: ATM Transparent Cell - LAST CALL
Date: Mon, 29 Nov 2004 14:38:38 -0500
Lines: 100
References: <AF5018AC03D1D411ABB70002A5091326015E1935@TLV1>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: "Andrew G. Malis \(E-mail\)" <Andy.Malis@tellabs.com>, pwe3 <pwe3@ietf.org>,
	'Stewart Bryant' <stbryant@cisco.com>
X-From: pwe3-bounces@ietf.org Mon Nov 29 21:18:33 2004
Return-path: <pwe3-bounces@ietf.org>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
To: Sasha Vainshtein <Sasha@AXERRA.com>
In-Reply-To: <AF5018AC03D1D411ABB70002A5091326015E1935@TLV1>
References: <AF5018AC03D1D411ABB70002A5091326015E1935@TLV1>
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Sasha,

Thanks for your comments.

Comment 1 will be incorporated into my post-last-call revision.

Comment 2 - isn't that already specified in the control and ATM encaps 
drafts?   Why repeat it here?

Comment 3 - OK.

Comment 4 - physical interface failure is probably all we need to act 
on.  ILMI signaling will be transported transparently, and the PE doesn't 
act on it.  Status codes 2 and 4 are probably the relevant codes depending 
on direction.  Optionally, the pseudowire labels can be withdrawn.

Your last comment (on section 4.2.2) is also a good one, but is out of my 
control.

Cheers,
Andy

---------

At 11/29/2004 06:23 PM +0200, Sasha Vainshtein wrote:
>Andy, Stewart and all,
>I suggest to consider the following minor edits to the draft
>in question:
>
>1. Specify that the PW Type to be used for the service in
>    question MUST be 0x0009 (ATM n-to-one VCC cell transport)
>    as per IANA allocation draft
>
>2. Specify that:
>    - if Maximum Number of concatenated ATM cells is
>      not part of the Interface Parameters field of FEC 128 or
>      of the Interface Parameters TLV going with FEC 129,
>      cell concatenation MUST NOT be used
>    - if this parameter is specified, the number of concatenated
>      cells per PW packet used by the PE receiving its value
>      MUST NOT exceeed the value distributed by the peer PE
>
>3. Add a normative reference to the IANA allocation draft
>    (for the PW type and Interface Parameter ID)
>
>4. Clarify which failures (only the physical port?, any other?)
>    at one end of the PW must be reported to the peer PE, and
>    which status values in the Status TLV must be used for this
>    purpose. E.g., is there any linkage between ILMI on the
>    CE<-->PE link and status reports across the PW?
>
>IMHO these edits would prevent any ambuiguities in future.
>They would also make the already existing reference to the
>Control Protocol draft meaningful (today it is only used
>to specify that "no new security issues are added" -
>rather vague, IMHO, since setup/maintenance of the PWs
>is not mentioned at all.
>
>I also suggest to consider collapsing Section 4.2.2
>of the Control Protocol draft (replacing it with the
>informative reference to the ATM Transparent Cell draft)
>to avoid duplication. But this is not directly related
>to the Last Call of the ATM Transparent Cell draft.
>
>Regards,
>                                   Sasha Vainshtein
>email:                         sasha@axerra.com <mailto:sasha@axerra.com>
>phone:                       +972-3-7569993 (office)
>fax:                            +972-3-6487779
>mobile:                      +972-52-8674833
>
>
> > -----Original Message-----
> > From: Stewart Bryant [mailto:stbryant@cisco.com]
> > Sent: Monday, November 29, 2004 4:28 PM
> > To: pwe3
> > Subject: [PWE3] ATM Transparent Cell - LAST CALL
> >
> >
> > This is the start of two week last call for
> >
> > PWE3 ATM Transparent Cell Transport Service
> > http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cell-trans
> > port-01.txt
> >
> > Last call will end Tuesday 14th December 2004
> >
> > Stewart
> >
> >
> > _______________________________________________
> > 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  Wed Dec 27 15:58:27 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: ATM Transparent Cell - LAST CALL
Date: Tue, 30 Nov 2004 09:07:51 +0200
Lines: 150
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: pwe3 <pwe3@ietf.org>, "Luca Martini \(E-mail\)" <lmartini@cisco.com>,
	'Stewart Bryant' <stbryant@cisco.com>
X-From: pwe3-bounces@ietf.org Tue Nov 30 08:47:02 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Andrew G. Malis'" <andymalis@comcast.net>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Andy and all,
Please see a few brief comments inline.
Regards,
                                  Sasha Vainshtein
email:                         sasha@axerra.com <mailto:sasha@axerra.com> 
phone:                       +972-3-7569993 (office)
fax:                            +972-3-6487779
mobile:                      +972-52-8674833 


> -----Original Message-----
> From: Andrew G. Malis [mailto:andymalis@comcast.net]
> Sent: Monday, November 29, 2004 9:39 PM
> To: Sasha Vainshtein
> Cc: 'Stewart Bryant'; Andrew G. Malis (E-mail); pwe3
> Subject: RE: [PWE3] ATM Transparent Cell - LAST CALL
> 
> 
> Sasha,
> 
> Thanks for your comments.
> 
> Comment 1 will be incorporated into my post-last-call revision.
>
[Sasha] Great!
> 
> Comment 2 - isn't that already specified in the control and 
> ATM encaps 
> drafts?   Why repeat it here?
>
[Sasha] The control protocol draft mentions it in Section 4.2.2;
if this section is collapsed (as I hope), it would be lost.
I also think that the related text in Section 4.2.2 of
the Control Protocol draft

<quote>
   If the Egress PE PE2 supports
   cell concatenation the ingress PE, PE1, should only concatenate cells
   up to the "Maximum Number of concatenated ATM cells" parameter
   received as part of the FEC element.
<end quote>

does not express the requirement properly (non-capitalized "should"
is not an IETF requirement of any sort!).
Last, but not least, I have not found any explicit reference to the
expected behavior if the interface parameter in question is not
present. And there is, IMHO, a valid alternative - to say that this
interface parameter is MANDATORY while establishing ATM N-to-one
PWs. So I'd think it should be specified explicitly and, preferably,
in one document.
> 
> Comment 3 - OK.
> 
> Comment 4 - physical interface failure is probably all we need to act 
> on.  ILMI signaling will be transported transparently, and 
> the PE doesn't 
> act on it.  Status codes 2 and 4 are probably the relevant 
> codes depending 
> on direction.  Optionally, the pseudowire labels can be withdrawn.
>
[Sasha] This is as I expect it to be. It would be nice, IMHO,
if the draft were saying it explicitly.
> 
> Your last comment (on section 4.2.2) is also a good one, but 
> is out of my control.
>
[Sasha] I understand. Luca, can you please consider this?
> 
> Cheers,
> Andy
> 
> ---------
> 
> At 11/29/2004 06:23 PM +0200, Sasha Vainshtein wrote:
> >Andy, Stewart and all,
> >I suggest to consider the following minor edits to the draft
> >in question:
> >
> >1. Specify that the PW Type to be used for the service in
> >    question MUST be 0x0009 (ATM n-to-one VCC cell transport)
> >    as per IANA allocation draft
> >
> >2. Specify that:
> >    - if Maximum Number of concatenated ATM cells is
> >      not part of the Interface Parameters field of FEC 128 or
> >      of the Interface Parameters TLV going with FEC 129,
> >      cell concatenation MUST NOT be used
> >    - if this parameter is specified, the number of concatenated
> >      cells per PW packet used by the PE receiving its value
> >      MUST NOT exceeed the value distributed by the peer PE
> >
> >3. Add a normative reference to the IANA allocation draft
> >    (for the PW type and Interface Parameter ID)
> >
> >4. Clarify which failures (only the physical port?, any other?)
> >    at one end of the PW must be reported to the peer PE, and
> >    which status values in the Status TLV must be used for this
> >    purpose. E.g., is there any linkage between ILMI on the
> >    CE<-->PE link and status reports across the PW?
> >
> >IMHO these edits would prevent any ambuiguities in future.
> >They would also make the already existing reference to the
> >Control Protocol draft meaningful (today it is only used
> >to specify that "no new security issues are added" -
> >rather vague, IMHO, since setup/maintenance of the PWs
> >is not mentioned at all.
> >
> >I also suggest to consider collapsing Section 4.2.2
> >of the Control Protocol draft (replacing it with the
> >informative reference to the ATM Transparent Cell draft)
> >to avoid duplication. But this is not directly related
> >to the Last Call of the ATM Transparent Cell draft.
> >
> >Regards,
> >                                   Sasha Vainshtein
> >email:                         sasha@axerra.com 
<mailto:sasha@axerra.com>
>phone:                       +972-3-7569993 (office)
>fax:                            +972-3-6487779
>mobile:                      +972-52-8674833
>
>
> > -----Original Message-----
> > From: Stewart Bryant [mailto:stbryant@cisco.com]
> > Sent: Monday, November 29, 2004 4:28 PM
> > To: pwe3
> > Subject: [PWE3] ATM Transparent Cell - LAST CALL
> >
> >
> > This is the start of two week last call for
> >
> > PWE3 ATM Transparent Cell Transport Service
> > http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cell-trans
> > port-01.txt
> >
> > Last call will end Tuesday 14th December 2004
> >
> > Stewart
> >
> >
> > _______________________________________________
> > 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  Wed Dec 27 15:58:27 2006
From: neil.2.harrison@bt.com
Subject: RE: Frame Check Sequence Retention - LAST CALL
Date: Tue, 30 Nov 2004 09:04:36 -0000
Lines: 120
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: pwe3@ietf.org
X-From: pwe3-bounces@ietf.org Tue Nov 30 12:18:40 2004
Return-path: <pwe3-bounces@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
content-class: urn:content-classes:message
Thread-Topic: [PWE3] Frame Check Sequence Retention - LAST CALL
Thread-Index: AcTWSCF/t5suQW30SjO9/txP7bentQAbVVGw
To: <andymalis@comcast.net>
X-OriginalArrivalTime: 30 Nov 2004 09:04:36.0565 (UTC)
	FILETIME=[9DAAA050:01C4D6BB]
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Content-Transfer-Encoding: quoted-printable
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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Thanks Andy and 'yes please'.....

Often we can't go back and re-do stuff......but as an engineering
community we would be rather foolish not to learn from mistakes.  It
would be really nice if we could capture these lessons as we go along.

I think its time we started doing things a little more measured based on
a better understanding of functional architecture wrt the 3 networking
modes.  It's quite clear to me from several perspectives/initiatives
(such as the stated desire to migrate from MPLS to GMPLS in CCAMPs (see
Note at the end) and quite obviously the creeping realisation in PWE3
that XoverMPLS !=3D XoverIP) that its time we started viewing MPLS as =
the
basis of layer network in its own right.  Indeed, if more folks had had
this view earlier I suspect many of the other problems that we also see
looming (such as the likelihood of creating a new 'PW layer network' and
the unnecessary differences of 'PW OAM' and 'LSP OAM') might have been
understood better earlier and addressed more appropriately.
{Aside - I am not saying throw-out all that has gone before that is
wrong, but learn from this and look to where we are now heading.}

We strongly believe there is far more value (and less opex) from
operating the 3 network modes in concert rather than trying to make 1
size fit all.....in fact the latter approach simply won't work
effectively in both technical and commercial dimensions (I can easily
explain why, but not here/now).

I'd urge open-minded folks to try and think more in functional
architecture terms and understand that it is the *differences* between
the 3 modes that are the 'precious bits'.....all the modes are important
and a full-service operator needs them all.  It's how we work them in
concert that is the really important issue.

Note - There is a very good reason why the GMPLS control-plane looks
like its does....and the behaviour we see here is not simply down to a
'design choice' (though the actual functional components are) but a
forced behaviour due to the nature of the co-cs mode (specifically the
nature of the link-connections and the quantised/known data-plane
bit-rate).

regards, Neil

> -----Original Message-----
> From: Andrew G. Malis [mailto:andymalis@comcast.net]=20
> Sent: 29 November 2004 19:16
> To: Harrison,N,Neil,IKR2 R
> Cc: pwe3@ietf.org
> Subject: RE: [PWE3] Frame Check Sequence Retention - LAST CALL
>=20
>=20
> Neil,
>=20
> Thanks for your comments.  Unfortunately, I can't do anything=20
> about comment=20
> 1 without the WG changing all of the existing encapsulation=20
> drafts.  On=20
> comment 2, I agree, if the WG makes RVSP-TE-signaled=20
> pseudowires a work=20
> item, then we'll be sure to get the capability to signal FCS=20
> retention in=20
> there.  Maybe in that case we can even make it the default! :-)
>=20
> Cheers,
> Andy
>=20
> ---------
>=20
> At 11/29/2004 04:50 PM +0000, neil.2.harrison@bt.com wrote:
> >Couple of observations on this draft:
> >
> >1       I don't agree the default behaviour should be strip the
> >FCS......but there is a much more important principle at stake here:=20
> >The default behaviour of any client/server relationship=20
> should always=20
> >be complete client transparency (all planes) over the server.
> >
> >2       The data-plane behaviour should be consistent irrespective of
> >how the trail is set-up.  This draft talks about LDP-based=20
> signalling=20
> >for the XoverMPLS case (though there is a cursory mention of=20
> management=20
> >provisioning).  However, it should apply to all signalling cases, eg=20
> >the MH-PW discussions where RSVP-TE is also being considered.
> >
> >regards, Neil
> >
> > > -----Original Message-----
> > > From: pwe3-bounces@ietf.org=20
> [mailto:pwe3-bounces@ietf.org] On Behalf=20
> > > Of Stewart=20
> Bryant
> > > Sent: 29 November 2004 14:29
> > > To: pwe3
> > > Subject: [PWE3] Frame Check Sequence Retention - LAST CALL
> > >
> > >
> > > This is the start of two week last call for
> > >
> > > PWE3 Frame Check Sequence Retention=20
> > > http://www.ietf.org/internet-drafts/draft-ietf-pwe3-fcs-retent
> >ion-02.txt
> >
> >Last call will end Tuesday 14th December 2004
> >
> >Stewart
> >
> >FCS retention
> >
> >
> >_______________________________________________
> >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
>=20
>=20


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-pwe3-control-protocol-14.txt
Date: Tue, 30 Nov 2004 15:11:20 -0500
Lines: 102
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Cc: pwe3@ietf.org
X-From: pwe3-bounces@ietf.org Tue Nov 30 22:51:24 2004
Return-path: <pwe3-bounces@ietf.org>
To: i-d-announce@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>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

--NextPart

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

	Title		: Pseudowire Setup and Maintenance using LDP
	Author(s)	: L. Martini, et al. 
	Filename	: draft-ietf-pwe3-control-protocol-14.txt
	Pages		: 41
	Date		: 2004-11-30
	
Layer 2 services (such as Frame Relay, ATM, ethernet) can be
   'emulated' over an IP and/or MPLS backbone by encapsulating the layer
   2 PDUs and then transmitting them over 'pseudowires'. It is also
   possible to use pseudowires to provide low-rate TDM and SONET circuit
   emulation over an IP and/or MPLS network. This document specifies a
   protocol for establishing and maintaining the pseudowires, using
   extensions to LDP. Procedures for encapsulating layer 2 PDUs are
   specified in a set of companion documents.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-control-protocol-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-control-protocol-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-control-protocol-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"

