
From shane@castlepoint.net  Mon Jan  4 21:37:04 2010
Return-Path: <shane@castlepoint.net>
X-Original-To: l2vpn@core3.amsl.com
Delivered-To: l2vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 885A23A6825 for <l2vpn@core3.amsl.com>; Mon,  4 Jan 2010 21:37:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KQPZdPT+UoEF for <l2vpn@core3.amsl.com>; Mon,  4 Jan 2010 21:37:03 -0800 (PST)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id 42D7E3A6828 for <l2vpn@ietf.org>; Mon,  4 Jan 2010 21:37:03 -0800 (PST)
Received: by dog.tcb.net (Postfix, from userid 0) id 23FD92684EA; Mon,  4 Jan 2010 22:37:02 -0700 (MST)
Received: from mbpw.castlepoint.net (71-215-78-124.hlrn.qwest.net [71.215.78.124]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Mon, 04 Jan 2010 22:37:01 -0700 (MST) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.78.124; client-port=64865; syn-fingerprint=65535:56:1:64:M1452,N,W1,N,N,T,S; data-bytes=0
Subject: Re: IANA allocation status code assignment conflict resolution
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: multipart/alternative; boundary=Apple-Mail-19-894765233
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <34F81DE93A7AA840A6A3B1187BAD5FC8030D0493AA@EXCH-CLUSTER-10.force10networks.com>
Date: Mon, 4 Jan 2010 22:36:46 -0700
Message-Id: <055CE8FC-73D4-4A52-8981-C570CF0CDDF6@castlepoint.net>
References: <34F81DE93A7AA840A6A3B1187BAD5FC8030D0493AA@EXCH-CLUSTER-10.force10networks.com>
To: Himanshu Shah <hshah@force10networks.com>
X-Mailer: Apple Mail (2.1077)
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>, Luca Martini <lmartini@cisco.com>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jan 2010 05:37:04 -0000

--Apple-Mail-19-894765233
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Everyone,

We haven't seen any feedback to this request either publicly or =
privately, so we will now direct IANA to change the assignment of 0x2c =
from draft-ietf-l2vpn-signaling to draft-ietf-l2vpn-arp-mediation.

-shane=20


On Nov 11, 2009, at 08:55 MST, Himanshu Shah wrote:
> Dear WG members,
> =20
> There has been a mix-up of the LDP status code assignment between
> L2VPN signaling  and arp-mediation draft. This has been resolved
> between the authors after some investigative work and has been
> determined that ARP-Mediation draft can use the 0x2c LDP status code.
> We intend to request IANA for early allocation of this status code and =
rectify the
> the current allocation (it shows assignment to l2vpn-signaling).
> =20
> We would like to request the WG to review this matter and express any
> opinion/concern on the mailing list.
> =20
> Thanks,
> himanshu and co-authors of ARP-Mediation draft.
> =20
> Following is the detail:
> =20
> Text from arp-mediation draft:  =
(draft-ietf-l2vpn-arp-mediation-12.txt)
> -------------------------------------------------------------=20
> 7.1. LDP Status messages
> =20
>    =20
>      This document uses new LDP status codes, IANA already maintains
>      a registry of name "STATUS CODE NAME SPACE" defined by [RFC
>      5036]. The following values are suggested for assignment:
>    =20
>         0x0000002C "IP Address of CE"
> =20
> Text from the L2VPN-signaling draft:  =
(draft-ietf-l2vpn-signaling-08.txt)
> --------------------------------------------------------------
> =20
> This document assumes the assignment of an AFI and a SAFI for L2VPN
>    NLRI.  Both AFI and SAFI should be the same as the values assigned
>    for [I-D.ietf-l2vpn-vpls-bgp].  That is, the AFI should be 25 =
(L2VPN)
>    and the SAFI should be 65 (already allocated for VPLS).  The same =
AFI
>    and SAFI are used for both VPLS and VPWS autodiscovery as described
>    in this document.
> =20
>    [I-D.ietf-pwe3-iana-allocation] defines registries for "Attachment
>    Group Identifier (AGI) Type" and "Attachment Individual Identifier
>    (AII) Type".  Type 1 in each registry has been assigned to the AGI
>    and AII formats defined in this document.
> =20
>    This document requires two new LDP status codes.  IANA already
>    maintains a registry of name "STATUS CODE NAME SPACE" defined by
>    [RFC3036].  The following values are suggested for assignment:
> =20
>    0x0000002C "Attachment Circuit bound to different PE"
> =20
> =20
> =20
> =20
> =20


--Apple-Mail-19-894765233
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi =
Everyone,<div><br></div><div>We haven't seen any feedback to this =
request either publicly or privately, so we will now direct IANA to =
change the assignment of 0x2c from draft-ietf-l2vpn-signaling to =
draft-ietf-l2vpn-arp-mediation.</div><div><br></div><div>-shane&nbsp;</div=
><div><br></div><div><br><div><div>On Nov 11, 2009, at 08:55 MST, =
Himanshu Shah wrote:</div><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Monaco; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div lang=3D"EN-US" link=3D"blue" =
vlink=3D"purple"><div class=3D"Section1"><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
11pt; font-family: Calibri, sans-serif; "><span class=3D"Apple-style-span"=
 style=3D"font-family: 'Trebuchet MS', sans-serif; font-size: 13px; =
">Dear WG members,</span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
11pt; font-family: Calibri, sans-serif; "><span style=3D"font-size: =
10pt; font-family: 'Trebuchet MS', sans-serif; =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
11pt; font-family: Calibri, sans-serif; "><span style=3D"font-size: =
10pt; font-family: 'Trebuchet MS', sans-serif; ">There has been a mix-up =
of the LDP status code assignment between<o:p></o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span style=3D"font-size: 10pt; font-family: 'Trebuchet MS', =
sans-serif; ">L2VPN signaling &nbsp;and arp-mediation draft. This has =
been resolved<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
11pt; font-family: Calibri, sans-serif; "><span style=3D"font-size: =
10pt; font-family: 'Trebuchet MS', sans-serif; ">between the authors =
after some investigative work and has been<o:p></o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span style=3D"font-size: 10pt; font-family: 'Trebuchet MS', =
sans-serif; ">determined that ARP-Mediation draft can use the 0x2c LDP =
status code.<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
11pt; font-family: Calibri, sans-serif; "><span style=3D"font-size: =
10pt; font-family: 'Trebuchet MS', sans-serif; ">We intend to request =
IANA for early allocation of this status code and rectify =
the<o:p></o:p></span></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif; "><span style=3D"font-size: 10pt; =
font-family: 'Trebuchet MS', sans-serif; ">the current allocation (it =
shows assignment to l2vpn-signaling).<o:p></o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span style=3D"font-size: 10pt; font-family: 'Trebuchet MS', =
sans-serif; "><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-size: 10pt; font-family: 'Trebuchet MS', sans-serif; ">We =
would like to request the WG to review this matter and express =
any<o:p></o:p></span></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif; "><span style=3D"font-size: 10pt; =
font-family: 'Trebuchet MS', sans-serif; ">opinion/concern on the =
mailing list.<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
11pt; font-family: Calibri, sans-serif; "><span style=3D"font-size: =
10pt; font-family: 'Trebuchet MS', sans-serif; =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
11pt; font-family: Calibri, sans-serif; "><span style=3D"font-size: =
10pt; font-family: 'Trebuchet MS', sans-serif; =
">Thanks,<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
11pt; font-family: Calibri, sans-serif; "><span style=3D"font-size: =
10pt; font-family: 'Trebuchet MS', sans-serif; ">himanshu and co-authors =
of ARP-Mediation draft.<o:p></o:p></span></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-size: 10pt; font-family: 'Trebuchet MS', sans-serif; =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
11pt; font-family: Calibri, sans-serif; "><span style=3D"font-size: =
10pt; font-family: 'Trebuchet MS', sans-serif; ">Following is the =
detail:<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
11pt; font-family: Calibri, sans-serif; "><span style=3D"font-size: =
10pt; font-family: 'Trebuchet MS', sans-serif; =
"><o:p>&nbsp;</o:p></span></div><pre style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
10pt; font-family: 'Courier New'; "><span style=3D"font-family: =
'Trebuchet MS', sans-serif; ">Text from arp-mediation draft:&nbsp; =
(</span>draft-ietf-l2vpn-arp-mediation-12.txt)<o:p></o:p></pre><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span style=3D"font-size: 10pt; font-family: 'Courier New'; =
">-------------------------------------------------------------&nbsp;<o:p>=
</o:p></span></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: =
Calibri, sans-serif; "><a name=3D"section-7.1"><b><span =
style=3D"font-size: 13.5pt; font-family: 'Courier New'; =
">7.1</span></b></a><b><span style=3D"font-size: 13.5pt; font-family: =
'Courier New'; ">. LDP Status messages<o:p></o:p></span></b></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span style=3D"font-size: 10pt; font-family: 'Courier New'; =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
11pt; font-family: Calibri, sans-serif; "><span style=3D"font-size: =
10pt; font-family: 'Courier New'; =
">&nbsp;&nbsp;&nbsp;&nbsp;<o:p></o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span style=3D"font-size: 10pt; font-family: 'Courier New'; =
">&nbsp;&nbsp;&nbsp;&nbsp; This document uses new LDP status codes, IANA =
already maintains<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
11pt; font-family: Calibri, sans-serif; "><span style=3D"font-size: =
10pt; font-family: 'Courier New'; ">&nbsp;&nbsp;&nbsp;&nbsp; a registry =
of name "STATUS CODE NAME SPACE" defined by =
[RFC<o:p></o:p></span></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif; "><span style=3D"font-size: 10pt; =
font-family: 'Courier New'; ">&nbsp;&nbsp;&nbsp;&nbsp; 5036]. The =
following values are suggested for =
assignment:<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
11pt; font-family: Calibri, sans-serif; "><span style=3D"font-size: =
10pt; font-family: 'Courier New'; =
">&nbsp;&nbsp;&nbsp;&nbsp;<o:p></o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span style=3D"font-size: 10pt; font-family: 'Courier New'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0x0000002C "IP Address of =
CE"<o:p></o:p></span></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif; "><span style=3D"font-size: 10pt; =
font-family: 'Trebuchet MS', sans-serif; =
"><o:p>&nbsp;</o:p></span></div><pre style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
10pt; font-family: 'Courier New'; "><span style=3D"font-family: =
'Trebuchet MS', sans-serif; ">Text from the L2VPN-signaling draft:&nbsp; =
(</span>draft-ietf-l2vpn-signaling-08.txt)<o:p></o:p></pre><pre =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10pt; font-family: 'Courier New'; =
">--------------------------------------------------------------<o:p></o:p=
></pre><div style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: =
0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif; "><span style=3D"font-size: 10pt; font-family: 'Trebuchet =
MS', sans-serif; "><o:p>&nbsp;</o:p></span></div><pre style=3D"margin-top:=
 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 10pt; font-family: 'Courier New'; ">This document assumes the =
assignment of an AFI and a SAFI for L2VPN<o:p></o:p></pre><pre =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10pt; font-family: 'Courier New'; =
">&nbsp;&nbsp; NLRI.&nbsp; Both AFI and SAFI should be the same as the =
values assigned<o:p></o:p></pre><pre style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
10pt; font-family: 'Courier New'; ">&nbsp;&nbsp; for [<a =
href=3D"http://tools.ietf.org/html/draft-ietf-l2vpn-signaling-08#ref-I-D.i=
etf-l2vpn-vpls-bgp" title=3D"&quot;Virtual Private LAN Service&quot;" =
style=3D"color: blue; text-decoration: underline; =
">I-D.ietf-l2vpn-vpls-bgp</a>].&nbsp; That is, the AFI should be 25 =
(L2VPN)<o:p></o:p></pre><pre style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10pt; =
font-family: 'Courier New'; ">&nbsp;&nbsp; and the SAFI should be 65 =
(already allocated for VPLS).&nbsp; The same AFI<o:p></o:p></pre><pre =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10pt; font-family: 'Courier New'; =
">&nbsp;&nbsp; and SAFI are used for both VPLS and VPWS autodiscovery as =
described<o:p></o:p></pre><pre style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10pt; =
font-family: 'Courier New'; ">&nbsp;&nbsp; in this =
document.<o:p></o:p></pre><pre style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10pt; =
font-family: 'Courier New'; "><o:p>&nbsp;</o:p></pre><pre =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10pt; font-family: 'Courier New'; =
">&nbsp;&nbsp; [<a name=3D"ref-I-D.ietf-pwe3-iana-allocation" =
id=3D"ref-I-D.ietf-pwe3-iana-allocation">I-D.ietf-pwe3-iana-allocation</a>=
] defines registries for "Attachment<o:p></o:p></pre><pre =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10pt; font-family: 'Courier New'; =
">&nbsp;&nbsp; Group Identifier (AGI) Type" and "Attachment Individual =
Identifier<o:p></o:p></pre><pre style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10pt; =
font-family: 'Courier New'; ">&nbsp;&nbsp; (AII) Type".&nbsp; Type 1 in =
each registry has been assigned to the AGI<o:p></o:p></pre><pre =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10pt; font-family: 'Courier New'; =
">&nbsp;&nbsp; and AII formats defined in this =
document.<o:p></o:p></pre><pre style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10pt; =
font-family: 'Courier New'; "><o:p>&nbsp;</o:p></pre><pre =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10pt; font-family: 'Courier New'; =
">&nbsp;&nbsp; This document requires two new LDP status codes.&nbsp; =
IANA already<o:p></o:p></pre><pre style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
10pt; font-family: 'Courier New'; ">&nbsp;&nbsp; maintains a registry of =
name "STATUS CODE NAME SPACE" defined by<o:p></o:p></pre><pre =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10pt; font-family: 'Courier New'; =
">&nbsp;&nbsp; [<a href=3D"http://tools.ietf.org/html/rfc3036" =
title=3D"&quot;LDP Specification&quot;" style=3D"color: blue; =
text-decoration: underline; ">RFC3036</a>].&nbsp; The following values =
are suggested for assignment:<o:p></o:p></pre><pre style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 10pt; font-family: 'Courier New'; =
"><o:p>&nbsp;</o:p></pre><pre style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10pt; =
font-family: 'Courier New'; ">&nbsp;&nbsp; 0x0000002C "Attachment =
Circuit bound to different PE"<o:p></o:p></pre><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-size: 10pt; font-family: 'Trebuchet MS', sans-serif; =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
11pt; font-family: Calibri, sans-serif; "><span style=3D"font-size: =
10pt; font-family: 'Trebuchet MS', sans-serif; =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
11pt; font-family: Calibri, sans-serif; "><span style=3D"font-size: =
10pt; font-family: 'Trebuchet MS', sans-serif; =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
11pt; font-family: Calibri, sans-serif; "><span style=3D"font-size: =
10pt; font-family: 'Trebuchet MS', sans-serif; =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
11pt; font-family: Calibri, sans-serif; "><span style=3D"font-size: =
10pt; font-family: 'Trebuchet MS', sans-serif; =
"><o:p>&nbsp;</o:p></span></div></div></div></span></blockquote></div><br>=
</div></body></html>=

--Apple-Mail-19-894765233--

From root@core3.amsl.com  Tue Jan  5 12:00:01 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: l2vpn@ietf.org
Delivered-To: l2vpn@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id D50493A6951; Tue,  5 Jan 2010 12:00:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-l2vpn-pbb-vpls-interop-00.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100105200001.D50493A6951@core3.amsl.com>
Date: Tue,  5 Jan 2010 12:00:01 -0800 (PST)
Cc: l2vpn@ietf.org
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jan 2010 20:00:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Layer 2 Virtual Private Networks Working Group of the IETF.


	Title           : VPLS Interoperability with Provider Backbone Bridges
	Author(s)       : A. Sajassi, et al.
	Filename        : draft-ietf-l2vpn-pbb-vpls-interop-00.txt
	Pages           : 23
	Date            : 2010-01-05

The scalability of H-VPLS with Ethernet access network can be 
improved by incorporating Provider Backbone Bridge functionality in 
VPLS access. Provider Backbone Bridging has been standardized as 
IEEE 802.1ah-2008, and aims to improve the scalability of MAC 
addresses and service instances in Provider Ethernet networks. This 
document describes different interoperability scenarios where 
Provider Backbone Bridge functionality is used in H-VPLS with 
Ethernet or MPLS access network to attain better scalability in 
terms of number of customer MAC addresses and number of service 
instances. The document also describes the scenarios and the 
mechanisms for incorporating Provider Backbone Bridge functionality 
within H-VPLS with existing Ethernet access and interoperability 
among them. Furthermore, the document discusses the migration 
mechanisms and scenarios by which Provider Backbone Bridge 
functionality can be incorporated into H-VPLS with existing MPLS 
access. 
 
 
  Conventions used in this document 
 
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 
document are to be interpreted as described in RFC 2119.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-pbb-vpls-interop-00.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-l2vpn-pbb-vpls-interop-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-01-05115019.I-D@ietf.org>


--NextPart--

From lmartini@cisco.com  Wed Jan  6 13:13:59 2010
Return-Path: <lmartini@cisco.com>
X-Original-To: l2vpn@core3.amsl.com
Delivered-To: l2vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2584128C168 for <l2vpn@core3.amsl.com>; Wed,  6 Jan 2010 13:13:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level: 
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17x3whZNeD9D for <l2vpn@core3.amsl.com>; Wed,  6 Jan 2010 13:13:58 -0800 (PST)
Received: from napoleon.monoski.com (napoleon.monoski.com [67.41.208.110]) by core3.amsl.com (Postfix) with ESMTP id 918D828C161 for <l2vpn@ietf.org>; Wed,  6 Jan 2010 13:13:57 -0800 (PST)
Received: from confusion.monoski.com (confusion.monoski.com [209.245.27.2]) (authenticated bits=0) by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id o06LDfe7020496 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Jan 2010 14:13:41 -0700 (MST)
Message-ID: <4B44FD05.6050706@cisco.com>
Date: Wed, 06 Jan 2010 14:13:41 -0700
From: Luca Martini <lmartini@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20081209)
MIME-Version: 1.0
To: Shane Amante <shane@castlepoint.net>
Subject: Re: IANA allocation status code assignment conflict resolution
References: <34F81DE93A7AA840A6A3B1187BAD5FC8030D0493AA@EXCH-CLUSTER-10.force10networks.com> <055CE8FC-73D4-4A52-8981-C570CF0CDDF6@castlepoint.net>
In-Reply-To: <055CE8FC-73D4-4A52-8981-C570CF0CDDF6@castlepoint.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.63 on 209.245.27.1
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2010 21:13:59 -0000

Shane Amante wrote:
> Hi Everyone,
>
> We haven't seen any feedback to this request either publicly or 
> privately, so we will now direct IANA to change the assignment of 0x2c 
> from draft-ietf-l2vpn-signaling to draft-ietf-l2vpn-arp-mediation.
>
Thanks !
Luca

> -shane 
>
>
> On Nov 11, 2009, at 08:55 MST, Himanshu Shah wrote:
>> Dear WG members,
>>  
>> There has been a mix-up of the LDP status code assignment between
>> L2VPN signaling  and arp-mediation draft. This has been resolved
>> between the authors after some investigative work and has been
>> determined that ARP-Mediation draft can use the 0x2c LDP status code.
>> We intend to request IANA for early allocation of this status code 
>> and rectify the
>> the current allocation (it shows assignment to l2vpn-signaling).
>>  
>> We would like to request the WG to review this matter and express any
>> opinion/concern on the mailing list.
>>  
>> Thanks,
>> himanshu and co-authors of ARP-Mediation draft.
>>  
>> Following is the detail:
>>  
>> Text from arp-mediation draft:  (draft-ietf-l2vpn-arp-mediation-12.txt)
>> ------------------------------------------------------------- 
>> *7.1**. LDP Status messages*
>>  
>>     
>>      This document uses new LDP status codes, IANA already maintains
>>      a registry of name "STATUS CODE NAME SPACE" defined by [RFC
>>      5036]. The following values are suggested for assignment:
>>     
>>         0x0000002C "IP Address of CE"
>>  
>> Text from the L2VPN-signaling draft:  (draft-ietf-l2vpn-signaling-08.txt)
>> --------------------------------------------------------------
>>  
>> This document assumes the assignment of an AFI and a SAFI for L2VPN
>>    NLRI.  Both AFI and SAFI should be the same as the values assigned
>>    for [I-D.ietf-l2vpn-vpls-bgp <http://tools.ietf.org/html/draft-ietf-l2vpn-signaling-08#ref-I-D.ietf-l2vpn-vpls-bgp>].  That is, the AFI should be 25 (L2VPN)
>>    and the SAFI should be 65 (already allocated for VPLS).  The same AFI
>>    and SAFI are used for both VPLS and VPWS autodiscovery as described
>>    in this document.
>>  
>>    [I-D.ietf-pwe3-iana-allocation] defines registries for "Attachment
>>    Group Identifier (AGI) Type" and "Attachment Individual Identifier
>>    (AII) Type".  Type 1 in each registry has been assigned to the AGI
>>    and AII formats defined in this document.
>>  
>>    This document requires two new LDP status codes.  IANA already
>>    maintains a registry of name "STATUS CODE NAME SPACE" defined by
>>    [RFC3036 <http://tools.ietf.org/html/rfc3036>].  The following values are suggested for assignment:
>>  
>>    0x0000002C "Attachment Circuit bound to different PE"
>>  
>>  
>>  
>>  
>>  
>


From root@core3.amsl.com  Thu Jan  7 10:45:01 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: l2vpn@ietf.org
Delivered-To: l2vpn@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 4C79528C12D; Thu,  7 Jan 2010 10:45:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-l2vpn-pbb-vpls-pe-model-01.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100107184501.4C79528C12D@core3.amsl.com>
Date: Thu,  7 Jan 2010 10:45:01 -0800 (PST)
Cc: l2vpn@ietf.org
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2010 18:45:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Layer 2 Virtual Private Networks Working Group of the IETF.


	Title           : Extensions to VPLS PE model for Provider Backbone Bridging
	Author(s)       : A. Sajassi, et al.
	Filename        : draft-ietf-l2vpn-pbb-vpls-pe-model-01.txt
	Pages           : 14
	Date            : 2010-01-07

IEEE 802.1ah standard [IEEE802.1ah], also known as Provider Backbone 
Bridges (PBB) defines an architecture and bridge protocols for 
interconnection of multiple Provider Bridge Networks (PBNs). PBB was 
defined in IEEE as a connectionless technology based on multipoint 
VLAN tunnels. MSTP is used as the core control plane for loop 
avoidance and load balancing. As a result, the coverage of the 
solution is limited by STP scale in the core of large service 
provider networks. PBB on the other hand can be used to attain better 
scalability in terms of number of customer MAC addresses and number 
of service instances that can be supported.  

Virtual Private LAN Service (VPLS) [RFC4762] provides a solution for 
extending Ethernet LAN services, using MPLS tunneling capabilities, 
through a routed MPLS backbone without running (M)STP across the 
backbone. As a result, VPLS has been deployed on a large scale in 
service provider networks.  

This draft discusses extensions to the VPLS PE model required to 
incorporate desirable PBB components while maintaining the Service 
Provider fit of the initial model.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-pbb-vpls-pe-model-01.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-l2vpn-pbb-vpls-pe-model-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-01-07104352.I-D@ietf.org>


--NextPart--

From wwwrun@core3.amsl.com  Wed Jan 13 13:34:42 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: l2vpn@ietf.org
Delivered-To: l2vpn@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 76C6C3A679C; Wed, 13 Jan 2010 13:34:42 -0800 (PST)
To: florin.balus@alcatel-lucent.com,sajassi@cisco.com,metz@cisco.com
From: IETF Secretariat <ietf-ipr@ietf.org>
Subject: Posting of IPR Disclosure related to Nortel Networks Limited Statement of IPR regarding draft-ietf-l2vpn-vpls-pbb-interop-00
Message-Id: <20100113213442.76C6C3A679C@core3.amsl.com>
Date: Wed, 13 Jan 2010 13:34:42 -0800 (PST)
Cc: l2vpn@ietf.org, Shane.Amante@Level3.com, rdroms@cisco.com, giles.heron@bt.com, ipr-announce@ietf.org
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2010 21:34:42 -0000

Dear Florin Balus, Ali Sajassi, San Jose:

An IPR disclosure that pertains to your Internet-Draft entitled "VPLS
Interoperability with Provider Backbone Bridges"
(draft-ietf-l2vpn-vpls-pbb-interop) was submitted to the IETF Secretariat on
2010-01-12 and has been posted on the "IETF Page of Intellectual Property Rights
Disclosures" (https://datatracker.ietf.org/ipr/1251/). The title of the IPR
disclosure is "Nortel Networks Limited Statement of IPR regarding
draft-ietf-l2vpn-vpls-pbb-interop-00."

The IETF Secretariat



From raymond.key@ieee.org  Mon Jan 25 19:22:02 2010
Return-Path: <raymond.key@ieee.org>
X-Original-To: l2vpn@core3.amsl.com
Delivered-To: l2vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D02323A6837; Mon, 25 Jan 2010 19:22:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.092
X-Spam-Level: 
X-Spam-Status: No, score=-101.092 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VlGA89zUFQ1n; Mon, 25 Jan 2010 19:22:01 -0800 (PST)
Received: from mail01.syd.optusnet.com.au (mail01.syd.optusnet.com.au [211.29.132.182]) by core3.amsl.com (Postfix) with ESMTP id 3F65B3A676A; Mon, 25 Jan 2010 19:22:01 -0800 (PST)
Received: from localhost.localdomain (webmail10.syd.optusnet.com.au [211.29.133.172]) by mail01.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id o0Q3Llao004270; Tue, 26 Jan 2010 14:21:48 +1100
Message-Id: <201001260321.o0Q3Llao004270@mail01.syd.optusnet.com.au>
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary
Mime-Version: 1.0
X-Mailer: MIME-tools 5.420 (Entity 5.420)
Received: from c122-107-172-84.eburwd5.vic.optusnet.com.au ([122.107.172.84]) by webmail10.syd.optusnet.com.au with http (user=rkey_ieee@optusnet.com.au); Tue, 26 Jan 2010 14:21:47 +1100
From: Raymond Key <raymond.key@ieee.org>
To: l2vpn@ietf.org, pwe3@ietf.org
Date: Tue, 26 Jan 2010 14:21:47 +1100
Subject: MEF E-Tree over MPLS/VPLS
Cc: lizhong.jin@zte.com.cn, y.kamite@ntt.com, frederic.jounay@orange-ftgroup.com
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: raymond.key@ieee.org
List-Id: <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jan 2010 03:22:03 -0000

Hi L2VPN & PWE3 workgroups,

We have updated the three Internet drafts re E-Tree service over MPLS network.

A Framework for E-Tree Service over MPLS Network
(http://tools.ietf.org/html/draft-key-l2vpn-etree-frwk-01)
Major update:
- 4.2. Use Case Desirable Requirements
- 4.2.1. Ethernet Broadcast/Multicast Optimisation
- 4.2.2. IP Multicast Optimisation
- 5.2.1. Per-payload Signaling on PW - From Leaf or Root
- 5.3. Optional Enhancement - Point-to-Multipoint PW
- 5.4. Optional Enhancement - IP Multicast in VPLS
- Appendix A. Other Possible Ways for Leaf-to-Leaf Communicaiton Restriction

Control Word Reserved bit for use in E-Tree
(http://tools.ietf.org/html/draft-delord-pwe3-cw-bit-etree-02)
Major update:
- 3.2 proposed approach (explain why we propose to use one bit in control word, with reference to the Preferred PW MPLS Control Word format in RFC4385)

Extension to VPLS for E-Tree
(http://tools.ietf.org/html/draft-key-l2vpn-vpls-etree-02)
Major update:
- 6. Optional Enhancements for Leaf-only PE
- 7. Hierarchical VPLS

Our proposed approach relies on a simple extension to the current VPLS standards (RFC4761 / RFC4762) and PWE3 Ethernet Encapsulation standard (RFC4448). With such extension, VPLS can be used to support both E-LAN and E-Tree services at the same time on MPLS network.

The authors would like to solicit comments from the workgroups. In particular,
- whether there is a need for VPLS to support E-Tree services
- whether the proposed approach is feasible
- whether vendors would consider implementing a E-Tree solution using the proposed approach
- whether service providers would consider using such solution if available

Thank a lot.

Raymond Key
