Re: An error in RFC 4446 "IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3)"

There are a couple of drafts in L2VPN WG that uses this PW type (0x000B),
such as http://tools.ietf.org/html/draft-ietf-l2vpn-arp-mediation-12
So it is not an error or problem in the RFC 3032. It is meant to carry IP payload without any data link headers.

Himanshu
Force10 networks






From: [email protected] [mailto:[email protected]] On Behalf Of Jiang Yuan-long
Sent: Tuesday, August 18, 2009 9:01 AM
To: [email protected]
Cc: [email protected]
Subject: [PWE3] An error in RFC 4446 "IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3)"

Hi, all:

I came accross an error in RFC 4446 "IANA Allocations for Pseudowire
Edge to Edge Emulation (PWE3)".

In Sec 3.2, it says:
"   0x000B  IP Layer2 Transport                              [RFC3032]"

it should be:
   0x000B  IP Layer2 Transport                        [draft-ietf-l2tpext-pwe3-ip]

The same problem also exists in web page version http://www.iana.org/assignments/pwe3-parameters.
I wonder how about the status of this expired WG draft, will any more work
continue on this document or just expired as it is?
I also wonder whether we should define a PW type for IP payload so that
everything on PW is possible.
Any comments?

   Thanks,
Yuanlong Jiang

_______________________________________________
pwe3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/pwe3