From l1vpn-bounces@lists.ietf.org Tue Apr 04 04:38:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FQh3T-0002go-6x; Tue, 04 Apr 2006 04:38:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FQh3S-0002gj-Ke
	for l1vpn@ietf.org; Tue, 04 Apr 2006 04:38:26 -0400
Received: from mail1.noc.data.net.uk ([80.68.34.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FQh3R-0002um-8v
	for l1vpn@ietf.org; Tue, 04 Apr 2006 04:38:26 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99]
	helo=cortex.aria-networks.com)
	by mail1.noc.data.net.uk with esmtp (Exim 3.36 #2)
	id 1FQh3X-00077F-00
	for l1vpn@ietf.org; Tue, 04 Apr 2006 09:38:31 +0100
Received: from Puppy ([217.158.132.232] RDNS failed) by
	cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 4 Apr 2006 09:38:53 +0100
Message-ID: <00cf01c657c3$27568a60$4702010a@Puppy>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <l1vpn@ietf.org>
Date: Tue, 4 Apr 2006 09:35:55 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
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: 04 Apr 2006 08:38:54.0437 (UTC)
	FILETIME=[34E61150:01C657C3]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: 
Subject: [L1vpn] Working group last call on draft-ietf-l1vpn-framework-02.txt
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

This email starts a two week working group last call on "Framework and
Requirements for Layer 1 Virtual Private Networks"

http://www.ietf.org/internet-drafts/draft-ietf-l1vpn-framework-02.txt

The last call will end on Tuesday 18th April at 12 noon GMT.


Please note that all three working group chairs are authors of this
document. In the event of any conflicts we will ask the ADs to adjudicate.

Thanks,
Adrian


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



From l1vpn-bounces@lists.ietf.org Wed Apr 05 12:01:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FRARu-0005TQ-E4; Wed, 05 Apr 2006 12:01:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FRARs-0005PX-Ui
	for l1vpn@ietf.org; Wed, 05 Apr 2006 12:01:36 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FRARs-0005Bu-TE
	for l1vpn@ietf.org; Wed, 05 Apr 2006 12:01:36 -0400
Received: from colo-dns-ext2.juniper.net ([207.17.137.64])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FRAJR-0003Ef-K4
	for l1vpn@ietf.org; Wed, 05 Apr 2006 11:52:55 -0400
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id
	k35Fqp1Z084817; Wed, 5 Apr 2006 08:52:51 -0700 (PDT)
	(envelope-from yakov@juniper.net)
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id k35Fqp509971;
	Wed, 5 Apr 2006 08:52:51 -0700 (PDT)
	(envelope-from yakov@juniper.net)
Message-Id: <200604051552.k35Fqp509971@merlot.juniper.net>
To: hbrahim@nortel.com, adrian@olddog.co.uk, takeda.tomonori@lab.ntt.co.jp
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <89780.1144252370.1@juniper.net>
Date: Wed, 05 Apr 2006 08:52:51 -0700
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: -2.0 (--)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Cc: yakov@juniper.net, l1vpn@ietf.org
Subject: [L1vpn] BGP-based Auto-Discovery for L1VPNs to L1VPN WG document 
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Folks,

We would like to request L1VPN WG to accept 
draft-ouldbrahim-l1vpn-bgp-auto-discovery-01.txt as L1VPN WG document.

Don & Yakov.


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



From l1vpn-bounces@lists.ietf.org Wed Apr 05 12:24:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FRAo9-00066d-C0; Wed, 05 Apr 2006 12:24:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FRAo8-00066Y-Ox
	for l1vpn@ietf.org; Wed, 05 Apr 2006 12:24:36 -0400
Received: from tcmail22.telekom.de ([217.6.95.236])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FRAo7-0006Y0-Bj
	for l1vpn@ietf.org; Wed, 05 Apr 2006 12:24:36 -0400
Received: from g9jbr.mgb01.telekom.de (g9jbr.mgb01.telekom.de [164.20.31.6])
	by tcmail21.dmz.telekom.de with ESMTP; Wed, 5 Apr 2006 18:24:30 +0200
Received: by G9JBR.mgb01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <2FZJXTLZ>; Wed, 5 Apr 2006 18:24:29 +0200
Message-Id: <1E4CCB2441C5C0409AD8A929482A09F312278E@S4DE9JSAAIG.ost.t-com.de>
From: "Leymann, Nicolai" <Nicolai.Leymann@t-systems.com>
To: yakov@juniper.net, hbrahim@nortel.com, adrian@olddog.co.uk,
	takeda.tomonori@lab.ntt.co.jp
Subject: AW: [L1vpn] BGP-based Auto-Discovery for L1VPNs to L1VPN WG docum ent 
Date: Wed, 5 Apr 2006 18:24:23 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: l1vpn@ietf.org
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

In favour!

  Nic

--
Dipl. Inf. Nicolai Leymann
=20
T-Systems Enterprise Services
Senior Expert, IP-Technologies
Systems Integration
Technologiezentrum
Engineering Networks, Products & Services=20
Packet based Carrier Transport Networks=20
Goslarer Ufer 35, D- 10589 Berlin=20
Tel +49 30 3497-3570=20
Fax +49 30 3497-3571=20
Mobile +49 170 2275345
E-Mail: nicolai.leymann@t-systems.com
Internet: http://www.t-systems.com
=20
=20

> -----Urspr=FCngliche Nachricht-----
> Von: Yakov Rekhter [mailto:yakov@juniper.net]=20
> Gesendet: Mittwoch, 5. April 2006 17:53
> An: hbrahim@nortel.com; adrian@olddog.co.uk;=20
> takeda.tomonori@lab.ntt.co.jp
> Cc: yakov@juniper.net; l1vpn@ietf.org
> Betreff: [L1vpn] BGP-based Auto-Discovery for L1VPNs to L1VPN=20
> WG document=20
>=20
> Folks,
>=20
> We would like to request L1VPN WG to accept=20
> draft-ouldbrahim-l1vpn-bgp-auto-discovery-01.txt as L1VPN WG =
document.
>=20
> Don & Yakov.
>=20
>=20
> _______________________________________________
> L1vpn mailing list
> L1vpn@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/l1vpn
>=20

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



From l1vpn-bounces@lists.ietf.org Wed Apr 05 12:37:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FRB0s-00017I-0C; Wed, 05 Apr 2006 12:37:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FRB0q-00017C-LB
	for l1vpn@ietf.org; Wed, 05 Apr 2006 12:37:44 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FRB0p-0007DL-8r
	for l1vpn@ietf.org; Wed, 05 Apr 2006 12:37:44 -0400
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 5 Apr 2006 18:37:34 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [L1vpn] BGP-based Auto-Discovery for L1VPNs to L1VPN WG document 
Date: Wed, 5 Apr 2006 18:37:31 +0200
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB0260341F9E9@FTRDMEL2.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [L1vpn] BGP-based Auto-Discovery for L1VPNs to L1VPN WG document
Thread-Index: AcZYzW+R7fAMD2PoQJ6lF6ZYpu2SNAAAYX5w
From: "MEURIC Julien RD-CORE-LAN" <julien.meuric@francetelecom.com>
To: <yakov@juniper.net>, <hbrahim@nortel.com>, <adrian@olddog.co.uk>,
	<takeda.tomonori@lab.ntt.co.jp>
X-OriginalArrivalTime: 05 Apr 2006 16:37:34.0402 (UTC)
	FILETIME=[3DBEB220:01C658CF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: l1vpn@ietf.org
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Hello all.

I agree.

Julien


-----Original Message-----
From: Leymann, Nicolai [mailto:Nicolai.Leymann@t-systems.com]=20

In favour!

  Nic

--
Dipl. Inf. Nicolai Leymann
=20
T-Systems Enterprise Services
Senior Expert, IP-Technologies
Systems Integration
Technologiezentrum
Engineering Networks, Products & Services=20
Packet based Carrier Transport Networks=20
Goslarer Ufer 35, D- 10589 Berlin=20
Tel +49 30 3497-3570=20
Fax +49 30 3497-3571=20
Mobile +49 170 2275345
E-Mail: nicolai.leymann@t-systems.com
Internet: http://www.t-systems.com
=20
=20

> -----Urspr=FCngliche Nachricht-----
> Von: Yakov Rekhter [mailto:yakov@juniper.net]=20
>=20
> Folks,
>=20
> We would like to request L1VPN WG to accept=20
> draft-ouldbrahim-l1vpn-bgp-auto-discovery-01.txt as L1VPN WG document.
>=20
> Don & Yakov.
>=20
>=20
> _______________________________________________
> L1vpn mailing list
> L1vpn@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/l1vpn
>=20

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

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



From l1vpn-bounces@lists.ietf.org Wed Apr 05 15:33:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FRDkr-0000Lw-0A; Wed, 05 Apr 2006 15:33:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FRDkp-0000Lr-1o
	for l1vpn@ietf.org; Wed, 05 Apr 2006 15:33:23 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FRDkk-0006Rk-My
	for l1vpn@ietf.org; Wed, 05 Apr 2006 15:33:23 -0400
Received: from blv-av-01.boeing.com ([192.42.227.216])
	by stl-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id
	OAA19117 for <l1vpn@ietf.org>; Wed, 5 Apr 2006 14:33:18 -0500 (CDT)
Received: from XCH-SWBH-04.sw.nos.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id
	k35JXHT15238
	for <l1vpn@ietf.org>; Wed, 5 Apr 2006 12:33:17 -0700 (PDT)
Received: from XCH-SW-42.sw.nos.boeing.com ([192.79.11.43]) by
	XCH-SWBH-04.sw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 5 Apr 2006 12:33:17 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [L1vpn] BGP-based Auto-Discovery for L1VPNs to L1VPN WG document 
Date: Wed, 5 Apr 2006 12:33:16 -0700
Message-ID: <626FC7C6A97381468FB872072AB5DDC8C2D871@XCH-SW-42.sw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [L1vpn] BGP-based Auto-Discovery for L1VPNs to L1VPN WG document
Thread-Index: AcZYyj1xMPm3ZF60QUqq3A31tNpNUgAHXNDw
From: "Drake, John E" <John.E.Drake2@boeing.com>
To: <l1vpn@ietf.org>
X-OriginalArrivalTime: 05 Apr 2006 19:33:17.0332 (UTC)
	FILETIME=[C9D22540:01C658E7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: 
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Yes

> -----Original Message-----
> From: Yakov Rekhter [mailto:yakov@juniper.net]
> Sent: Wednesday, April 05, 2006 8:53 AM
> To: hbrahim@nortel.com; adrian@olddog.co.uk;
takeda.tomonori@lab.ntt.co.jp
> Cc: yakov@juniper.net; l1vpn@ietf.org
> Subject: [L1vpn] BGP-based Auto-Discovery for L1VPNs to L1VPN WG
document
>=20
> Folks,
>=20
> We would like to request L1VPN WG to accept
> draft-ouldbrahim-l1vpn-bgp-auto-discovery-01.txt as L1VPN WG document.
>=20
> Don & Yakov.
>=20
>=20
> _______________________________________________
> L1vpn mailing list
> L1vpn@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/l1vpn

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



From l1vpn-bounces@lists.ietf.org Wed Apr 05 16:09:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FREJt-0004nT-4r; Wed, 05 Apr 2006 16:09:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FREJs-0004nO-DX
	for l1vpn@ietf.org; Wed, 05 Apr 2006 16:09:36 -0400
Received: from mail126.messagelabs.com ([216.82.250.99])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FREJq-0002Ql-Vm
	for l1vpn@ietf.org; Wed, 05 Apr 2006 16:09:36 -0400
X-VirusChecked: Checked
X-Env-Sender: dbrungard@att.com
X-Msg-Ref: server-5.tower-126.messagelabs.com!1144267729!10737527!7
X-StarScan-Version: 5.5.9.1; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 1477 invoked from network); 5 Apr 2006 20:09:33 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4)
	by server-5.tower-126.messagelabs.com with SMTP;
	5 Apr 2006 20:09:33 -0000
Received: from OCCLUST04EVS1.ugd.att.com (135.38.164.12) by
	attrh3i.attrh.att.com (7.2.052)
	id 4426C9FE0016C16F; Wed, 5 Apr 2006 16:09:32 -0400
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [L1vpn] BGP-based Auto-Discovery for L1VPNs to L1VPN WG document 
Date: Wed, 5 Apr 2006 15:09:31 -0500
Message-ID: <449B2580D802A443A923DABF3EAB82AF0BDB8236@OCCLUST04EVS1.ugd.att.com>
In-Reply-To: <200604051552.k35Fqp509971@merlot.juniper.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [L1vpn] BGP-based Auto-Discovery for L1VPNs to L1VPN WG document
Thread-Index: AcZYyj70OzgFmJ8FQMW0nHysXZocdAAIntag
From: "Brungard, Deborah A, ALABS" <dbrungard@att.com>
To: "Yakov Rekhter" <yakov@juniper.net>, <hbrahim@nortel.com>,
	<adrian@olddog.co.uk>, <takeda.tomonori@lab.ntt.co.jp>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: l1vpn@ietf.org
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Yes-=20

-----Original Message-----
From: Yakov Rekhter [mailto:yakov@juniper.net]=20
Sent: Wednesday, April 05, 2006 11:53 AM
To: hbrahim@nortel.com; adrian@olddog.co.uk;
takeda.tomonori@lab.ntt.co.jp
Cc: yakov@juniper.net; l1vpn@ietf.org
Subject: [L1vpn] BGP-based Auto-Discovery for L1VPNs to L1VPN WG
document=20

Folks,

We would like to request L1VPN WG to accept=20
draft-ouldbrahim-l1vpn-bgp-auto-discovery-01.txt as L1VPN WG document.

Don & Yakov.


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

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



From l1vpn-bounces@lists.ietf.org Mon Apr 10 09:25:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FSwOc-0006lx-KZ; Mon, 10 Apr 2006 09:25:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FSwOb-0006ls-4O
	for l1vpn@ietf.org; Mon, 10 Apr 2006 09:25:33 -0400
Received: from mail2.noc.data.net.uk ([80.68.34.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FSwOZ-0001TS-Nl
	for l1vpn@ietf.org; Mon, 10 Apr 2006 09:25:33 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99]
	helo=cortex.aria-networks.com)
	by mail2.noc.data.net.uk with esmtp (Exim 3.36 #1)
	id 1FSwOV-0005HP-00
	for l1vpn@ietf.org; Mon, 10 Apr 2006 14:25:28 +0100
Received: from Puppy ([217.158.132.118] RDNS failed) by
	cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 10 Apr 2006 14:26:02 +0100
Message-ID: <078301c65ca2$44a06ee0$bf849ed9@Puppy>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <l1vpn@ietf.org>
Date: Mon, 10 Apr 2006 14:25:07 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
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: 10 Apr 2006 13:26:02.0750 (UTC)
	FILETIME=[504081E0:01C65CA2]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Cc: 
Subject: [L1vpn] Draft minutes uploaded
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Hi,

Please review the minutes at
http://www3.ietf.org/proceedings/06mar/minutes/l1vpn.html

Comments on the list or to the chairs.

Thanks,
Adrian


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



From l1vpn-bounces@lists.ietf.org Tue Apr 11 17:21:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTQIs-00088Z-Ge; Tue, 11 Apr 2006 17:21:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTQIs-00088U-53
	for l1vpn@ietf.org; Tue, 11 Apr 2006 17:21:38 -0400
Received: from webmail.movaz.com ([70.158.43.219] helo=jera.movaz.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTQIr-0003j5-QB
	for l1vpn@ietf.org; Tue, 11 Apr 2006 17:21:38 -0400
Received: from ib (unknown [172.16.24.125])
	by jera.movaz.com (Postfix) with SMTP
	id 1EB4D20847; Tue, 11 Apr 2006 17:21:37 -0400 (EDT)
Message-ID: <014101c65dad$e1067520$7d1810ac@movaz.com>
From: "Igor Bryskin" <ibryskin@movaz.com>
To: <l1vpn@ietf.org>
References: <0e1001c65da8$021928d0$bf849ed9@Puppy>
Date: Tue, 11 Apr 2006 17:21:20 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: 
Subject: [L1vpn] Re: I-D
	ACTION:draft-bryskin-l1vpn-ospf-auto-discovery-01.txt 
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Hi,

A new version of the "OSPF Based L1VPN Auto-Discovery" draft has been
published. We tried to address all comments that we have received during
IETF65. In particular we removed the section related to the validation of
AS-scope opaque LSAs (the problem is now being addressed by a special effort
within OSPF WG). This modification has made the suggested solution
independent of whether the network configured as a single or multiple OSPF
areas. The solution now requires no changes on ABRs.

Igor (and Lou).

> ----- Original Message ----- 
> From: <Internet-Drafts@ietf.org>
> To: <i-d-announce@ietf.org>
> Sent: Tuesday, April 11, 2006 8:50 PM
> Subject: I-D ACTION:draft-bryskin-l1vpn-ospf-auto-discovery-01.txt
>
>
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >
> >
> > Title : OSPF Based L1VPN Auto-Discovery
> > Author(s) : I. Bryskin, L. Berger
> > Filename : draft-bryskin-l1vpn-ospf-auto-discovery-01.txt
> > Pages : 12
> > Date : 2006-4-11
> >
> > This document defines an OSPF based layer-1 VPN auto-discovery
> >    mechanism.  This mechanism enables PEs using the OSPF IGP to
> >    dynamically learn about existence of each other, and attributes of
> >    currently configured CE-PE links and their associations with L1VPNs.
> >    This document builds on [L1VPN-FRMWK] and provides an auto-discovery
> >    mechanism as discussed in [L1VPN-BM].
> >
> > A URL for this Internet-Draft is:
> >
>
http://www.ietf.org/internet-drafts/draft-bryskin-l1vpn-ospf-auto-discovery-01.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-bryskin-l1vpn-ospf-auto-discovery-01.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-bryskin-l1vpn-ospf-auto-discovery-01.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.
> >
>
>
> --------------------------------------------------------------------------
> ------
>
>
> > _______________________________________________
> > I-D-Announce mailing list
> > I-D-Announce@ietf.org
> > https://www1.ietf.org/mailman/listinfo/i-d-announce
> >
>


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



From l1vpn-bounces@lists.ietf.org Wed Apr 12 06:13:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTcLg-0003gD-Sl; Wed, 12 Apr 2006 06:13:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTcLe-0003g8-Pp
	for l1vpn@ietf.org; Wed, 12 Apr 2006 06:13:18 -0400
Received: from mail2.noc.data.net.uk ([80.68.34.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTcLd-0007Vy-BG
	for l1vpn@ietf.org; Wed, 12 Apr 2006 06:13:18 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99]
	helo=cortex.aria-networks.com)
	by mail2.noc.data.net.uk with esmtp (Exim 3.36 #1)
	id 1FTcLa-0004kV-00
	for l1vpn@ietf.org; Wed, 12 Apr 2006 11:13:14 +0100
Received: from Puppy ([217.158.132.50] RDNS failed) by
	cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 12 Apr 2006 11:13:49 +0100
Message-ID: <0f2301c65e19$c0d1b500$bf849ed9@Puppy>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <l1vpn@ietf.org>
Date: Wed, 12 Apr 2006 11:13:25 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
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 Apr 2006 10:13:49.0812 (UTC)
	FILETIME=[CAE95340:01C65E19]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: 
Subject: [L1vpn] Proposals for three new working group documents
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Hi,

In Dallas we agreed that we wanted to take the three basic mode I-Ds into
the working group.

This email is to formally ask you for approval or issues with adopting
these drafts as follows...


draft-fedyk-l1vpn-basic-mode-01.txt
  ---->draft-ietf-l1vpn-basic-mode-00.txt

draft-ouldbrahim-l1vpn-bgp-auto-discovery-01.txt
  ---->draft-ietf-l1vpn-bgp-auto-discovery-00.txt

draft-bryskin-l1vpn-ospf-auto-discovery-01.txt
  ---->draft-ietf-l1vpn-ospf-auto-discovery-00.txt


Opinions please.

Thanks,
Adrian


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



From l1vpn-bounces@lists.ietf.org Wed Apr 12 09:09:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTf5d-0003Gs-TH; Wed, 12 Apr 2006 09:08:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTf5d-0003Gn-4M
	for l1vpn@ietf.org; Wed, 12 Apr 2006 09:08:57 -0400
Received: from zcars04e.nortel.com ([47.129.242.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTf5Z-0004z1-Qx
	for l1vpn@ietf.org; Wed, 12 Apr 2006 09:08:57 -0400
Received: from zrtphxm2.corp.nortel.com (zrtphxm2.corp.nortel.com
	[47.140.202.51])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	k3CD4GK14542; Wed, 12 Apr 2006 09:04:16 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [L1vpn] Proposals for three new working group documents
Date: Wed, 12 Apr 2006 09:08:48 -0400
Message-ID: <34B3EAA5B3066A42914D28C5ECF5FEA407C98689@zrtphxm2>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [L1vpn] Proposals for three new working group documents
Thread-Index: AcZeGcBDoRQx2k7dS1qQgRyZXVG6ZAAGFG+A
From: "Don Fedyk" <dwfedyk@nortel.com>
To: "Adrian Farrel" <adrian@olddog.co.uk>, <l1vpn@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: 
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Hi Adrian

Yes to all three, (I'm an author on the first two.)=20

Don=20

> -----Original Message-----
> From: Adrian Farrel [mailto:adrian@olddog.co.uk]=20
>=20
> Hi,
>=20
> In Dallas we agreed that we wanted to take the three basic=20
> mode I-Ds into the working group.
>=20
> This email is to formally ask you for approval or issues with=20
> adopting these drafts as follows...
>=20
>=20
> draft-fedyk-l1vpn-basic-mode-01.txt
>   ---->draft-ietf-l1vpn-basic-mode-00.txt
>=20
> draft-ouldbrahim-l1vpn-bgp-auto-discovery-01.txt
>   ---->draft-ietf-l1vpn-bgp-auto-discovery-00.txt
>=20
> draft-bryskin-l1vpn-ospf-auto-discovery-01.txt
>   ---->draft-ietf-l1vpn-ospf-auto-discovery-00.txt
>=20
>=20
> Opinions please.
>=20
> Thanks,
> Adrian
>=20
>=20
> _______________________________________________
> L1vpn mailing list
> L1vpn@lists.ietf.org https://www1.ietf.org/mailman/listinfo/l1vpn
>=20
>=20

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



From l1vpn-bounces@lists.ietf.org Wed Apr 12 09:15:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTfBw-0007Tu-LH; Wed, 12 Apr 2006 09:15:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTfBv-0007Tk-Ef
	for l1vpn@ietf.org; Wed, 12 Apr 2006 09:15:27 -0400
Received: from webmail.movaz.com ([70.158.43.219] helo=jera.movaz.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTfBu-000599-7P
	for l1vpn@ietf.org; Wed, 12 Apr 2006 09:15:27 -0400
Received: from ib (unknown [172.16.24.125])
	by jera.movaz.com (Postfix) with SMTP
	id B7F9620891; Wed, 12 Apr 2006 09:15:25 -0400 (EDT)
Message-ID: <008b01c65e33$1c21fb90$7d1810ac@movaz.com>
From: "Igor Bryskin" <ibryskin@movaz.com>
To: "Adrian Farrel" <adrian@olddog.co.uk>, <l1vpn@ietf.org>
References: <0f2301c65e19$c0d1b500$bf849ed9@Puppy>
Subject: Re: [L1vpn] Proposals for three new working group documents
Date: Wed, 12 Apr 2006 09:15:03 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: 
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Yes to all three.

Igor

----- Original Message ----- 
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <l1vpn@ietf.org>
Sent: Wednesday, April 12, 2006 6:13 AM
Subject: [L1vpn] Proposals for three new working group documents


> Hi,
> 
> In Dallas we agreed that we wanted to take the three basic mode I-Ds into
> the working group.
> 
> This email is to formally ask you for approval or issues with adopting
> these drafts as follows...
> 
> 
> draft-fedyk-l1vpn-basic-mode-01.txt
>   ---->draft-ietf-l1vpn-basic-mode-00.txt
> 
> draft-ouldbrahim-l1vpn-bgp-auto-discovery-01.txt
>   ---->draft-ietf-l1vpn-bgp-auto-discovery-00.txt
> 
> draft-bryskin-l1vpn-ospf-auto-discovery-01.txt
>   ---->draft-ietf-l1vpn-ospf-auto-discovery-00.txt
> 
> 
> Opinions please.
> 
> Thanks,
> Adrian
> 
> 
> _______________________________________________
> L1vpn mailing list
> L1vpn@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/l1vpn
> 

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



From l1vpn-bounces@lists.ietf.org Wed Apr 12 09:50:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTfjX-0006pN-Dc; Wed, 12 Apr 2006 09:50:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTfjV-0006nI-VB
	for l1vpn@ietf.org; Wed, 12 Apr 2006 09:50:09 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTfjR-0006GC-GJ
	for l1vpn@ietf.org; Wed, 12 Apr 2006 09:50:09 -0400
Received: from blv-av-01.boeing.com ([192.42.227.216])
	by blv-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id
	GAA27942; Wed, 12 Apr 2006 06:49:58 -0700 (PDT)
Received: from XCH-SWBH-04.sw.nos.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id
	k3CDnvT08337; Wed, 12 Apr 2006 06:49:58 -0700 (PDT)
Received: from XCH-SW-42.sw.nos.boeing.com ([192.79.11.43]) by
	XCH-SWBH-04.sw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 12 Apr 2006 06:49:57 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [L1vpn] Proposals for three new working group documents
Date: Wed, 12 Apr 2006 06:49:56 -0700
Message-ID: <626FC7C6A97381468FB872072AB5DDC8C2D88D@XCH-SW-42.sw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [L1vpn] Proposals for three new working group documents
Thread-Index: AcZeGbzLt2U2T0IxQfCTbh58qNEQdAAHiwpA
From: "Drake, John E" <John.E.Drake2@boeing.com>
To: "Adrian Farrel" <adrian@olddog.co.uk>, <l1vpn@ietf.org>
X-OriginalArrivalTime: 12 Apr 2006 13:49:57.0431 (UTC)
	FILETIME=[FC36F470:01C65E37]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: 
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org



> -----Original Message-----
> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
> Sent: Wednesday, April 12, 2006 3:13 AM
> To: l1vpn@ietf.org
> Subject: [L1vpn] Proposals for three new working group documents
>=20
> Hi,
>=20
> In Dallas we agreed that we wanted to take the three basic mode I-Ds
into
> the working group.
>=20
> This email is to formally ask you for approval or issues with adopting
> these drafts as follows...
>=20
>=20
> draft-fedyk-l1vpn-basic-mode-01.txt
>   ---->draft-ietf-l1vpn-basic-mode-00.txt

Yes

>=20
> draft-ouldbrahim-l1vpn-bgp-auto-discovery-01.txt
>   ---->draft-ietf-l1vpn-bgp-auto-discovery-00.txt

Yes

>=20
> draft-bryskin-l1vpn-ospf-auto-discovery-01.txt
>   ---->draft-ietf-l1vpn-ospf-auto-discovery-00.txt

No

>=20
>=20
> Opinions please.
>=20
> Thanks,
> Adrian
>=20
>=20
> _______________________________________________
> L1vpn mailing list
> L1vpn@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/l1vpn

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



From l1vpn-bounces@lists.ietf.org Wed Apr 12 09:52:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTfm0-0007p4-Aw; Wed, 12 Apr 2006 09:52:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTflz-0007oz-Fw
	for l1vpn@ietf.org; Wed, 12 Apr 2006 09:52:43 -0400
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTfly-0006Jh-42
	for l1vpn@ietf.org; Wed, 12 Apr 2006 09:52:43 -0400
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 12 Apr 2006 15:52:39 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: [L1vpn] Proposals for three new working group documents
Date: Wed, 12 Apr 2006 15:52:38 +0200
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB026034E7D77@FTRDMEL2.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [L1vpn] Proposals for three new working group documents
Thread-Index: AcZeGbxhn9xXFuewRz6Imcn8o24WkgAHV55Q
From: "MEURIC Julien RD-CORE-LAN" <julien.meuric@francetelecom.com>
To: <adrian@olddog.co.uk>,
	<l1vpn@ietf.org>
X-OriginalArrivalTime: 12 Apr 2006 13:52:39.0804 (UTC)
	FILETIME=[5CFF1BC0:01C65E38]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: 
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Hi Adrian, hi all.

Please see below.


-----Original Message-----
From: Adrian Farrel [mailto:adrian@olddog.co.uk]=20

<snip>

draft-fedyk-l1vpn-basic-mode-01.txt
  ---->draft-ietf-l1vpn-basic-mode-00.txt

[JM] Yes

draft-ouldbrahim-l1vpn-bgp-auto-discovery-01.txt
  ---->draft-ietf-l1vpn-bgp-auto-discovery-00.txt

[JM] Yes

draft-bryskin-l1vpn-ospf-auto-discovery-01.txt
  ---->draft-ietf-l1vpn-ospf-auto-discovery-00.txt

[JM] No: as discussed before, I believe BGP is enough for this.

Regards,

Julien

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



From l1vpn-bounces@lists.ietf.org Wed Apr 12 11:28:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FThGX-0005Bj-9Y; Wed, 12 Apr 2006 11:28:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FThGV-0005B2-Ck
	for l1vpn@ietf.org; Wed, 12 Apr 2006 11:28:19 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTgQD-0007oT-3B
	for l1vpn@ietf.org; Wed, 12 Apr 2006 10:34:17 -0400
Received: from esc71.midphase.com ([216.246.11.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FTgBH-0003GE-3S
	for l1vpn@ietf.org; Wed, 12 Apr 2006 10:18:52 -0400
Received: from esc71.midphase.com ([216.246.11.148] helo=LC1.labn.net)
	by esc71.midphase.com with esmtpa (Exim 4.52)
	id 1FTgBD-0003Eo-Sr; Wed, 12 Apr 2006 10:18:48 -0400
Message-Id: <6.2.3.4.2.20060412101757.044d5740@mail.labn.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4
Date: Wed, 12 Apr 2006 10:18:44 -0400
To: Adrian Farrel <adrian@olddog.co.uk>
From: Lou Berger <lberger@labn.net>
Subject: Re: [L1vpn] Proposals for three new working group documents
In-Reply-To: <0f2301c65e19$c0d1b500$bf849ed9@Puppy>
References: <0f2301c65e19$c0d1b500$bf849ed9@Puppy>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - esc71.midphase.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: -2.6 (--)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: l1vpn@ietf.org
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Yes to all three.

At 06:13 AM 4/12/2006, Adrian Farrel wrote:
>Hi,
>
>In Dallas we agreed that we wanted to take the three basic mode I-Ds into
>the working group.
>
>This email is to formally ask you for approval or issues with adopting
>these drafts as follows...
>
>
>draft-fedyk-l1vpn-basic-mode-01.txt
>   ---->draft-ietf-l1vpn-basic-mode-00.txt
>
>draft-ouldbrahim-l1vpn-bgp-auto-discovery-01.txt
>   ---->draft-ietf-l1vpn-bgp-auto-discovery-00.txt
>
>draft-bryskin-l1vpn-ospf-auto-discovery-01.txt
>   ---->draft-ietf-l1vpn-ospf-auto-discovery-00.txt
>
>
>Opinions please.
>
>Thanks,
>Adrian
>
>
>_______________________________________________
>L1vpn mailing list
>L1vpn@lists.ietf.org
>https://www1.ietf.org/mailman/listinfo/l1vpn


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



From l1vpn-bounces@lists.ietf.org Wed Apr 12 11:47:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FThYv-0002MA-Sw; Wed, 12 Apr 2006 11:47:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FThYu-0002M4-Tw
	for l1vpn@ietf.org; Wed, 12 Apr 2006 11:47:20 -0400
Received: from gw.imc.kth.se ([193.10.152.67] helo=oberon.imc.kth.se)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FThYu-0002UO-FX
	for l1vpn@ietf.org; Wed, 12 Apr 2006 11:47:20 -0400
Received: from mail1.imc.kth.se (mail1.imc.kth.se [193.10.152.140])
	by oberon.imc.kth.se (8.13.1/8.13.1) with ESMTP id k3CFbROh000844
	for <l1vpn@ietf.org>; Wed, 12 Apr 2006 17:37:27 +0200
Received: from [127.0.0.1] ([172.16.2.231])
	by mail1.imc.kth.se; Wed, 12 Apr 2006 17:46:36 +0200
Message-ID: <443D20D9.3030002@pi.se>
Date: Wed, 12 Apr 2006 17:46:33 +0200
From: Loa Andersson <loa@pi.se>
Organization: Acreo AB
User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: [L1vpn] Proposals for three new working group documents
References: <0f2301c65e19$c0d1b500$bf849ed9@Puppy>
In-Reply-To: <0f2301c65e19$c0d1b500$bf849ed9@Puppy>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: l1vpn@ietf.org
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

yes to the first two and no to the third

/Loa

Adrian Farrel wrote:
> Hi,
> 
> In Dallas we agreed that we wanted to take the three basic mode I-Ds into
> the working group.
> 
> This email is to formally ask you for approval or issues with adopting
> these drafts as follows...
> 
> 
> draft-fedyk-l1vpn-basic-mode-01.txt
>   ---->draft-ietf-l1vpn-basic-mode-00.txt
> 
> draft-ouldbrahim-l1vpn-bgp-auto-discovery-01.txt
>   ---->draft-ietf-l1vpn-bgp-auto-discovery-00.txt
> 
> draft-bryskin-l1vpn-ospf-auto-discovery-01.txt
>   ---->draft-ietf-l1vpn-ospf-auto-discovery-00.txt
> 
> 
> Opinions please.
> 
> Thanks,
> Adrian
> 
> 
> _______________________________________________
> L1vpn mailing list
> L1vpn@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/l1vpn
> 


-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                            loa@pi.se

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



From l1vpn-bounces@lists.ietf.org Wed Apr 12 11:50:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FThbh-0003c4-Lz; Wed, 12 Apr 2006 11:50:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FThbg-0003aA-Nx
	for l1vpn@ietf.org; Wed, 12 Apr 2006 11:50:12 -0400
Received: from fujitsu2.fna.fujitsu.com ([192.240.0.2]
	helo=fujitsu2.fujitsu.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FThbf-0002Wg-5z
	for l1vpn@ietf.org; Wed, 12 Apr 2006 11:50:12 -0400
Received: from fujitsu2.fujitsu.com (localhost [127.0.0.1])
	by fujitsu2.fujitsu.com (8.13.6/8.13.6) with ESMTP id k3CFoARn022319;
	Wed, 12 Apr 2006 08:50:10 -0700 (PDT)
Received: from fujitsuii.fna.fujitsu.com ([133.164.253.2])
	by fujitsu2.fujitsu.com (8.13.6/8.13.6) with ESMTP id k3CFo9Kb022311;
	Wed, 12 Apr 2006 08:50:09 -0700 (PDT)
Received: from mailserv.fla.fujitsu.com (localhost [127.0.0.1])
	by fujitsuii.fna.fujitsu.com (8.13.5/8.13.5) with ESMTP id
	k3CFo86M007855; Wed, 12 Apr 2006 08:50:08 -0700 (PDT)
Received: from PHOENIX (localhost [127.0.0.1])
	by mailserv.fla.fujitsu.com (8.11.6/8.11.6) with ESMTP id k3CFo8O28897; 
	Wed, 12 Apr 2006 08:50:08 -0700 (PDT)
From: "Richard Rabbat" <richard@us.fujitsu.com>
To: "'Adrian Farrel'" <adrian@olddog.co.uk>, <l1vpn@ietf.org>
Subject: RE: [L1vpn] Proposals for three new working group documents
Date: Wed, 12 Apr 2006 08:50:07 -0700
Message-ID: <001101c65e48$c5db2ed0$373ba485@PHOENIX>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
In-Reply-To: <0f2301c65e19$c0d1b500$bf849ed9@Puppy>
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: 
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Hi Adrian,
See inline. 
Richard.

> -----Original Message-----
> From: Adrian Farrel [mailto:adrian@olddog.co.uk] 
> Sent: Wednesday, April 12, 2006 3:13 AM
> To: l1vpn@ietf.org
> Subject: [L1vpn] Proposals for three new working group documents
> 
> 
> Hi,
> 
> In Dallas we agreed that we wanted to take the three basic 
> mode I-Ds into
> the working group.
> 
> This email is to formally ask you for approval or issues with adopting
> these drafts as follows...
> 
> 
> draft-fedyk-l1vpn-basic-mode-01.txt
>   ---->draft-ietf-l1vpn-basic-mode-00.txt

Yes

> draft-ouldbrahim-l1vpn-bgp-auto-discovery-01.txt
>   ---->draft-ietf-l1vpn-bgp-auto-discovery-00.txt

No
 
> draft-bryskin-l1vpn-ospf-auto-discovery-01.txt
>   ---->draft-ietf-l1vpn-ospf-auto-discovery-00.txt
> 
Yes
 
> Opinions please.
> 
> Thanks,
> Adrian
> 
> 
> _______________________________________________
> L1vpn mailing list
> L1vpn@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/l1vpn
> 


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



From l1vpn-bounces@lists.ietf.org Wed Apr 12 16:22:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTlrD-0001u3-8S; Wed, 12 Apr 2006 16:22:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTlrC-0001tP-4A
	for l1vpn@ietf.org; Wed, 12 Apr 2006 16:22:30 -0400
Received: from smail.alcatel.fr ([62.23.212.165])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTlrB-0006WW-M2
	for l1vpn@ietf.org; Wed, 12 Apr 2006 16:22:30 -0400
Received: from bemail05.netfr.alcatel.fr (bemail05.netfr.alcatel.fr
	[155.132.251.11])
	by smail.alcatel.fr (8.13.4/8.13.4/Debian-3sarge1) with ESMTP id
	k3CKMTjL018253; Wed, 12 Apr 2006 22:22:29 +0200
In-Reply-To: <0f2301c65e19$c0d1b500$bf849ed9@Puppy>
To: Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: [L1vpn] Proposals for three new working group documents
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OFE50529BF.747DFBE0-ONC125714E.006199FE-C125714E.006FEAA2@netfr.alcatel.fr>
From: Dimitri.Papadimitriou@alcatel.be
Date: Wed, 12 Apr 2006 22:22:26 +0200
X-MIMETrack: Serialize by Router on BEMAIL05/BE/ALCATEL(Release 5.0.12HF868 |
	May 16, 2005) at 04/12/2006 22:22:27,
	Serialize complete at 04/12/2006 22:22:27
Content-Type: text/plain; charset="US-ASCII"
X-Scanned-By: MIMEDefang 2.51 on 155.132.180.81
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: l1vpn@ietf.org
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

> draft-fedyk-l1vpn-basic-mode-01.txt
>  ---->draft-ietf-l1vpn-basic-mode-00.txt

yes

> draft-ouldbrahim-l1vpn-bgp-auto-discovery-01.txt
>  ---->draft-ietf-l1vpn-bgp-auto-discovery-00.txt

see below 1

> draft-bryskin-l1vpn-ospf-auto-discovery-01.txt
>  ---->draft-ietf-l1vpn-ospf-auto-discovery-00.txt

see below 2


1. if the discovery process (PE-PE) is also including TDM service 
over PSN there is a broader community involved in this discussion
otherwise - ok -

2. charter says 

"At this point the WG will address the single-AS scenario only. The
multi-AS/provider scenario may be considered in future." 

but we never got a clear answer whether this wg wants to have the same
solution for both scenarios and we do not have much info from fmw doc
nor from the list

the only thing i know from the list is that operator(s) are not willing
to have two solutions for the same problem - but basically i see two 
distinct problems we could solve in a single AS context for which you
could have different starting points

- single-AS core backbone running already an IGP and connecting core
routers

- single-AS STM-N infrastucture to provide LO/HO VC connectivity that 
could be expanded to multi-AS

i would say both but i put a warning on the IGP-based solution whether 
the multi-area case is the prime focus, i read this draft as trying to 
compete with the functionality of the BGP single-AS case while it is 
not clear at all this is relevant 












"Adrian Farrel" <adrian@olddog.co.uk>
12/04/2006 12:13
Please respond to Adrian Farrel
 
        To:     <l1vpn@ietf.org>
        cc: 
        Subject:        [L1vpn] Proposals for three new working group 
documents


Hi,

In Dallas we agreed that we wanted to take the three basic mode I-Ds into
the working group.

This email is to formally ask you for approval or issues with adopting
these drafts as follows...


draft-fedyk-l1vpn-basic-mode-01.txt
  ---->draft-ietf-l1vpn-basic-mode-00.txt

draft-ouldbrahim-l1vpn-bgp-auto-discovery-01.txt
  ---->draft-ietf-l1vpn-bgp-auto-discovery-00.txt

draft-bryskin-l1vpn-ospf-auto-discovery-01.txt
  ---->draft-ietf-l1vpn-ospf-auto-discovery-00.txt


Opinions please.

Thanks,
Adrian


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



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



From l1vpn-bounces@lists.ietf.org Wed Apr 12 17:24:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTmpU-00055p-7r; Wed, 12 Apr 2006 17:24:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTmpS-00055k-Sj
	for l1vpn@ietf.org; Wed, 12 Apr 2006 17:24:46 -0400
Received: from esc71.midphase.com ([216.246.11.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTmpQ-0000Oi-L9
	for l1vpn@ietf.org; Wed, 12 Apr 2006 17:24:46 -0400
Received: from esc71.midphase.com ([216.246.11.148] helo=LC1.labn.net)
	by esc71.midphase.com with esmtpa (Exim 4.52)
	id 1FTmpN-000818-AB; Wed, 12 Apr 2006 17:24:41 -0400
Message-Id: <6.2.3.4.2.20060412172258.02772070@mail.labn.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4
Date: Wed, 12 Apr 2006 17:24:37 -0400
To: Adrian Farrel <adrian@olddog.co.uk>
From: Lou Berger <lberger@labn.net>
Subject: Re: [L1vpn] Draft minutes uploaded
In-Reply-To: <078301c65ca2$44a06ee0$bf849ed9@Puppy>
References: <078301c65ca2$44a06ee0$bf849ed9@Puppy>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - esc71.midphase.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: l1vpn@ietf.org
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Hi Adrian,

some comments on the minutes:

1) With respect to:

>Adrian: If we're interested in the generic case, we should talk to 
>the OSPF working group
I believe Igor agreed and said that he would.

2) With respect to:

>Richard Rabbat: To ask the question again: do you need to upgrade 
>routers or is it nice to have optimization?
>Igor: You need to upgrade PEs and ABRs
>Lou: It is not a significant upgrade

I don't recall making this state, but I do recall saying something 
along the lines that "ABR upgrades aren't critical."

(Also this is all OBE, given the draft announced today.)

3) somewhere in there I also agreed with Yakov that we should 
progress both works and let the market decide.

(A clear decision point will come when it's time for implementation 
reports. - not stated in session.)

Lou

At 09:25 AM 4/10/2006, Adrian Farrel wrote:
>Hi,
>
>Please review the minutes at
>http://www3.ietf.org/proceedings/06mar/minutes/l1vpn.html
>
>Comments on the list or to the chairs.
>
>Thanks,
>Adrian
>
>
>_______________________________________________
>L1vpn mailing list
>L1vpn@lists.ietf.org
>https://www1.ietf.org/mailman/listinfo/l1vpn


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



From l1vpn-bounces@lists.ietf.org Thu Apr 13 02:55:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTvjp-0006eS-9S; Thu, 13 Apr 2006 02:55:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTvjn-0006eN-W3
	for l1vpn@ietf.org; Thu, 13 Apr 2006 02:55:31 -0400
Received: from smail.alcatel.fr ([62.23.212.165])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTvjm-0000jP-Hg
	for l1vpn@ietf.org; Thu, 13 Apr 2006 02:55:31 -0400
Received: from bemail05.netfr.alcatel.fr (bemail05.netfr.alcatel.fr
	[155.132.251.11])
	by smail.alcatel.fr (8.13.4/8.13.4/Debian-3sarge1) with ESMTP id
	k3D6tTwW024617; Thu, 13 Apr 2006 08:55:29 +0200
In-Reply-To: <078301c65ca2$44a06ee0$bf849ed9@Puppy>
To: Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: [L1vpn] Draft minutes uploaded
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OFB3E3AF19.125611F0-ONC125714E.0078D2BD-C125714F.002609E6@netfr.alcatel.fr>
From: Dimitri.Papadimitriou@alcatel.be
Date: Thu, 13 Apr 2006 08:55:29 +0200
X-MIMETrack: Serialize by Router on BEMAIL05/BE/ALCATEL(Release 5.0.12HF868 |
	May 16, 2005) at 04/13/2006 08:55:29,
	Serialize complete at 04/13/2006 08:55:29
Content-Type: text/plain; charset="US-ASCII"
X-Scanned-By: MIMEDefang 2.51 on 155.132.180.81
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: l1vpn@ietf.org
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

adrian

"- Dimitri: Please clarity the use of PCE
- Tomonori: As Adrian said, CCAMP has selected PCE. L1VPN is not requiring 
the use of PCE, but recognising the
          possiblity of using PCE for P&R"

but this is not what adrian could have said as i've never seen a statement 
such as L1VPN recognizes the possibility
of using PCE for P&R ... as there is no CE dual homing discussion since so 
far 

"Dimitri: It is a timing issue; They have today an OSPF environment and 
are willing to deploy quickly.
         BGP may be a solution in 4-5 years"

the last part of the message was "No doubt that BGP is a sensible 
approach, but if we have to base our timing 
by relying on IGP deployment experience, BGP may be the solution of choice 
in 4-5 years."

"Yakov: Update on the BGP-based auto-discovery
       We don't want to have a new AFI, we just need a new SAFI
       New format for l1vpn LNRI"

guess you mean NLRI





"Adrian Farrel" <adrian@olddog.co.uk>
10/04/2006 15:25
Please respond to Adrian Farrel
 
        To:     <l1vpn@ietf.org>
        cc: 
        Subject:        [L1vpn] Draft minutes uploaded


Hi,

Please review the minutes at
http://www3.ietf.org/proceedings/06mar/minutes/l1vpn.html

Comments on the list or to the chairs.

Thanks,
Adrian


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



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



From l1vpn-bounces@lists.ietf.org Thu Apr 13 03:02:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTvqJ-0001N2-Mz; Thu, 13 Apr 2006 03:02:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTvqH-0001Mx-Hq
	for l1vpn@ietf.org; Thu, 13 Apr 2006 03:02:13 -0400
Received: from tama5.ecl.ntt.co.jp ([129.60.39.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTvqD-0000wq-So
	for l1vpn@ietf.org; Thu, 13 Apr 2006 03:02:13 -0400
Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110])
	by tama5.ecl.ntt.co.jp (8.13.6/8.13.6) with ESMTP id k3D728Yn010022; 
	Thu, 13 Apr 2006 16:02:08 +0900 (JST)
Received: from mfs3.rdh.ecl.ntt.co.jp (mfs3.rdh.ecl.ntt.co.jp [129.60.39.112])
	by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	k3D727PI009018; Thu, 13 Apr 2006 16:02:07 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp ([129.60.39.100])
	by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	k3D727UY006867; Thu, 13 Apr 2006 16:02:07 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp
	[129.60.5.69])
	by nttmail3.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	k3D726GX000113; Thu, 13 Apr 2006 16:02:06 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	k3D726fS008680; Thu, 13 Apr 2006 16:02:06 +0900 (JST)
Received: from imc.m.ecl.ntt.co.jp (imc.m.ecl.ntt.co.jp [129.60.5.227])
	by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	k3D725s8008675; Thu, 13 Apr 2006 16:02:05 +0900 (JST)
Received: from [127.0.0.1] ([129.60.80.125])
	by imc.m.ecl.ntt.co.jp (8.13.4/8.13.4) with ESMTP id k3D724C2026082;
	Thu, 13 Apr 2006 16:02:05 +0900 (JST)
Message-ID: <443DF768.1010503@lab.ntt.co.jp>
Date: Thu, 13 Apr 2006 16:02:00 +0900
From: Kohei Shiomoto <shiomoto.kohei@lab.ntt.co.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP;
	rv:1.7.11) Gecko/20050728
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: [L1vpn] Proposals for three new working group documents
References: <0f2301c65e19$c0d1b500$bf849ed9@Puppy>
In-Reply-To: <0f2301c65e19$c0d1b500$bf849ed9@Puppy>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: l1vpn@ietf.org
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Yes to all.

-- 
Kohei Shiomoto
NTT Network Service Systems Laboratories
3-9-11 Midori, Musashino, Tokyo 180-8585, Japan
Phone +81 422 59 4402    Fax +81 422 59 3787

Adrian Farrel wrote:

> Hi,
> 
> In Dallas we agreed that we wanted to take the three basic mode I-Ds into
> the working group.
> 
> This email is to formally ask you for approval or issues with adopting
> these drafts as follows...
> 
> 
> draft-fedyk-l1vpn-basic-mode-01.txt
>   ---->draft-ietf-l1vpn-basic-mode-00.txt
> 
> draft-ouldbrahim-l1vpn-bgp-auto-discovery-01.txt
>   ---->draft-ietf-l1vpn-bgp-auto-discovery-00.txt
> 
> draft-bryskin-l1vpn-ospf-auto-discovery-01.txt
>   ---->draft-ietf-l1vpn-ospf-auto-discovery-00.txt
> 
> 
> Opinions please.
> 
> Thanks,
> Adrian
> 
> 
> _______________________________________________
> L1vpn mailing list
> L1vpn@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/l1vpn
> 
> 







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



From l1vpn-bounces@lists.ietf.org Thu Apr 13 07:45:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FU0Fv-0008RU-Qn; Thu, 13 Apr 2006 07:44:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FU0Fv-0008RP-Cg
	for l1vpn@ietf.org; Thu, 13 Apr 2006 07:44:59 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FU0Fu-0001M1-2W
	for l1vpn@ietf.org; Thu, 13 Apr 2006 07:44:59 -0400
Received: from sj-core-3.cisco.com ([171.68.223.137])
	by sj-iport-5.cisco.com with ESMTP; 13 Apr 2006 04:44:58 -0700
X-IronPort-AV: i="4.04,117,1144047600"; 
	d="scan'208"; a="268501031:sNHT30059012"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id k3DBivVI014592;
	Thu, 13 Apr 2006 04:44:57 -0700 (PDT)
Received: from xmb-rtp-20d.amer.cisco.com ([64.102.31.51]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Thu, 13 Apr 2006 07:44:56 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [L1vpn] Proposals for three new working group documents
Date: Thu, 13 Apr 2006 07:44:56 -0400
Message-ID: <3C292CE901FC634693F24FB2DDC4D332015A4164@xmb-rtp-20d.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [L1vpn] Proposals for three new working group documents
Thread-Index: AcZeGciGHZi0xQmmS6+Cnw+XbbwWhAA1Yx5g
From: "Rich Bradford \(rbradfor\)" <rbradfor@cisco.com>
To: "Adrian Farrel" <adrian@olddog.co.uk>, <l1vpn@ietf.org>
X-OriginalArrivalTime: 13 Apr 2006 11:44:56.0871 (UTC)
	FILETIME=[AFF21370:01C65EEF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: 
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1905625986=="
Errors-To: l1vpn-bounces@lists.ietf.org

--===============1905625986==
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

QW5zd2VycyBpbmxpbmUuCQkJDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJv
bTogQWRyaWFuIEZhcnJlbCBbbWFpbHRvOmFkcmlhbkBvbGRkb2cuY28udWtdDQo+IFNlbnQ6IFdl
ZG5lc2RheSwgQXByaWwgMTIsIDIwMDYgNjoxMyBBTQ0KPiBUbzogbDF2cG5AaWV0Zi5vcmcNCj4g
U3ViamVjdDogW0wxdnBuXSBQcm9wb3NhbHMgZm9yIHRocmVlIG5ldyB3b3JraW5nIGdyb3VwIGRv
Y3VtZW50cw0KPiANCj4gSGksDQo+IA0KPiBJbiBEYWxsYXMgd2UgYWdyZWVkIHRoYXQgd2Ugd2Fu
dGVkIHRvIHRha2UgdGhlIHRocmVlIGJhc2ljIG1vZGUgSS1EcyBpbnRvDQo+IHRoZSB3b3JraW5n
IGdyb3VwLg0KPiANCj4gVGhpcyBlbWFpbCBpcyB0byBmb3JtYWxseSBhc2sgeW91IGZvciBhcHBy
b3ZhbCBvciBpc3N1ZXMgd2l0aCBhZG9wdGluZw0KPiB0aGVzZSBkcmFmdHMgYXMgZm9sbG93cy4u
Lg0KPiANCj4gDQo+IGRyYWZ0LWZlZHlrLWwxdnBuLWJhc2ljLW1vZGUtMDEudHh0DQo+ICAgLS0t
LT5kcmFmdC1pZXRmLWwxdnBuLWJhc2ljLW1vZGUtMDAudHh0DQp5ZXMNCj4gDQo+IGRyYWZ0LW91
bGRicmFoaW0tbDF2cG4tYmdwLWF1dG8tZGlzY292ZXJ5LTAxLnR4dA0KPiAgIC0tLS0+ZHJhZnQt
aWV0Zi1sMXZwbi1iZ3AtYXV0by1kaXNjb3ZlcnktMDAudHh0DQp5ZXMNCj4gDQo+IGRyYWZ0LWJy
eXNraW4tbDF2cG4tb3NwZi1hdXRvLWRpc2NvdmVyeS0wMS50eHQNCj4gICAtLS0tPmRyYWZ0LWll
dGYtbDF2cG4tb3NwZi1hdXRvLWRpc2NvdmVyeS0wMC50eHQNCk5vdCB5ZXQuIA0KPiANCj4gDQo+
IE9waW5pb25zIHBsZWFzZS4NCj4gDQo+IFRoYW5rcywNCj4gQWRyaWFuDQo+IA0KPiANCj4gX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gTDF2cG4gbWFp
bGluZyBsaXN0DQo+IEwxdnBuQGxpc3RzLmlldGYub3JnDQo+IGh0dHBzOi8vd3d3MS5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL2wxdnBuDQo=


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

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

--===============1905625986==--



From l1vpn-bounces@lists.ietf.org Thu Apr 13 08:07:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FU0b5-0008LK-Mh; Thu, 13 Apr 2006 08:06:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FU0b5-0008LF-2L
	for l1vpn@ietf.org; Thu, 13 Apr 2006 08:06:51 -0400
Received: from tama5.ecl.ntt.co.jp ([129.60.39.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FU0b2-0001rL-7s
	for l1vpn@ietf.org; Thu, 13 Apr 2006 08:06:51 -0400
Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110])
	by tama5.ecl.ntt.co.jp (8.13.6/8.13.6) with ESMTP id k3DC6kl9022502
	for <l1vpn@ietf.org>; Thu, 13 Apr 2006 21:06:46 +0900 (JST)
Received: from mfs3.rdh.ecl.ntt.co.jp (mfs3.rdh.ecl.ntt.co.jp [129.60.39.112])
	by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	k3DC6jAt028719
	for <l1vpn@ietf.org>; Thu, 13 Apr 2006 21:06:45 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp ([129.60.39.100])
	by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	k3DC6jMJ028950
	for <l1vpn@ietf.org>; Thu, 13 Apr 2006 21:06:45 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp
	[129.60.5.69])
	by nttmail3.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	k3DC6if4018689
	for <l1vpn@ietf.org>; Thu, 13 Apr 2006 21:06:44 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	k3DC6iSQ014461
	for <l1vpn@ietf.org>; Thu, 13 Apr 2006 21:06:44 +0900 (JST)
Received: from imb.m.ecl.ntt.co.jp (imb.m.ecl.ntt.co.jp [129.60.5.226])
	by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	k3DC6iOQ014458
	for <l1vpn@ietf.org>; Thu, 13 Apr 2006 21:06:44 +0900 (JST)
Received: from INOUE-LETS-CFW2.lab.ntt.co.jp ([129.60.80.247])
	by imb.m.ecl.ntt.co.jp (8.13.4/8.13.4) with ESMTP id k3DC6h4c002560
	for <l1vpn@ietf.org>; Thu, 13 Apr 2006 21:06:43 +0900 (JST)
Message-Id: <6.0.0.20.2.20060413210539.05c6be20@imb.m.ecl.ntt.co.jp>
X-Sender: ii004@imb.m.ecl.ntt.co.jp
X-Mailer: QUALCOMM Windows Eudora Version 6J
Date: Thu, 13 Apr 2006 21:06:42 +0900
To: <l1vpn@ietf.org>
From: "inoue.ichiro@lab.ntt.co.jp" <inoue.ichiro@lab.ntt.co.jp>
Subject: RE: [L1vpn] Proposals for three new working group documents
In-Reply-To: <3C292CE901FC634693F24FB2DDC4D332015A4164@xmb-rtp-20d.amer.
	cisco.com>
References: <3C292CE901FC634693F24FB2DDC4D332015A4164@xmb-rtp-20d.amer.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: 
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Hi.

Yes to all three.

Ichiro

 >> -----Original Message-----
 >> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
 >> Sent: Wednesday, April 12, 2006 6:13 AM
 >> To: l1vpn@ietf.org
 >> Subject: [L1vpn] Proposals for three new working group documents
 >>
 >> Hi,
 >>
 >> In Dallas we agreed that we wanted to take the three basic mode I-Ds into
 >> the working group.
 >>
 >> This email is to formally ask you for approval or issues with adopting
 >> these drafts as follows...
 >>
 >>
 >> draft-fedyk-l1vpn-basic-mode-01.txt
 >>   ---->draft-ietf-l1vpn-basic-mode-00.txt
 >>
 >> draft-ouldbrahim-l1vpn-bgp-auto-discovery-01.txt
 >>   ---->draft-ietf-l1vpn-bgp-auto-discovery-00.txt
 >>
 >> draft-bryskin-l1vpn-ospf-auto-discovery-01.txt
 >>   ---->draft-ietf-l1vpn-ospf-auto-discovery-00.txt
 >>
 >>
 >> Opinions please.
 >>
 >> Thanks,
 >> Adrian
 >>



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



From l1vpn-bounces@lists.ietf.org Thu Apr 13 08:55:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FU1M6-0000KA-Fu; Thu, 13 Apr 2006 08:55:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FU1M5-0000K4-IO
	for l1vpn@ietf.org; Thu, 13 Apr 2006 08:55:25 -0400
Received: from mandala.kddilabs.jp ([192.26.91.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FU1M4-0003BC-64
	for l1vpn@ietf.org; Thu, 13 Apr 2006 08:55:25 -0400
Received: from localhost (localhost [127.0.0.1])
	by mandala.kddilabs.jp (Postfix) with ESMTP
	id ADED6EC8D6; Thu, 13 Apr 2006 21:55:22 +0900 (JST)
Received: from platinum.onw.kddilabs.jp (platinum.onw.kddilabs.jp
	[2001:200:601:1300:172:19:83:254])
	by mandala.kddilabs.jp (Postfix) with ESMTP
	id 76634EC8CC; Thu, 13 Apr 2006 21:55:22 +0900 (JST)
Received: from [IPv6:2001:200:601:1e02:0:5efe:ac13:570e] (unknown
	[IPv6:2001:200:601:1e02:0:5efe:ac13:570e])
	by platinum.onw.kddilabs.jp (Postfix) with ESMTP
	id 5E3C7578103; Thu, 13 Apr 2006 21:54:05 +0900 (JST)
Message-ID: <443E4A48.70505@kddilabs.jp>
Date: Thu, 13 Apr 2006 21:55:36 +0900
From: Tomohiro Otani <otani@kddilabs.jp>
Organization: KDDI R&D Laboratories, Inc.
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: [L1vpn] Proposals for three new working group documents
References: <0f2301c65e19$c0d1b500$bf849ed9@Puppy>
In-Reply-To: <0f2301c65e19$c0d1b500$bf849ed9@Puppy>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: l1vpn@ietf.org
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: otani@kddilabs.jp
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Hi everyone,

The first and second drafts are OK, but the last one is to be discussed more
and considered again after the next meeting judging from the mailing list
discussion.

Regards,

tomo





Adrian Farrel wrote:
> Hi,
> 
> In Dallas we agreed that we wanted to take the three basic mode I-Ds into
> the working group.
> 
> This email is to formally ask you for approval or issues with adopting
> these drafts as follows...
> 
> 
> draft-fedyk-l1vpn-basic-mode-01.txt
>   ---->draft-ietf-l1vpn-basic-mode-00.txt
> 
> draft-ouldbrahim-l1vpn-bgp-auto-discovery-01.txt
>   ---->draft-ietf-l1vpn-bgp-auto-discovery-00.txt
> 
> draft-bryskin-l1vpn-ospf-auto-discovery-01.txt
>   ---->draft-ietf-l1vpn-ospf-auto-discovery-00.txt
> 
> 
> Opinions please.
> 
> Thanks,
> Adrian
> 
> 
> _______________________________________________
> L1vpn mailing list
> L1vpn@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/l1vpn
> 


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



From l1vpn-bounces@lists.ietf.org Thu Apr 13 10:00:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FU2Mm-0001Zk-Vu; Thu, 13 Apr 2006 10:00:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FU2Ml-0001Wn-4s
	for l1vpn@ietf.org; Thu, 13 Apr 2006 10:00:11 -0400
Received: from mail120.messagelabs.com ([216.82.250.83])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FU2Mj-0005YH-NH
	for l1vpn@ietf.org; Thu, 13 Apr 2006 10:00:11 -0400
X-VirusChecked: Checked
X-Env-Sender: dbrungard@att.com
X-Msg-Ref: server-11.tower-120.messagelabs.com!1144936808!10638287!1
X-StarScan-Version: 5.5.9.1; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 6076 invoked from network); 13 Apr 2006 14:00:08 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4)
	by server-11.tower-120.messagelabs.com with SMTP;
	13 Apr 2006 14:00:08 -0000
Received: from OCCLUST04EVS1.ugd.att.com (135.38.164.12) by
	attrh3i.attrh.att.com (7.2.052)
	id 4426C9FE0026EC8F; Thu, 13 Apr 2006 10:00:03 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [L1vpn] Proposals for three new working group documents
Date: Thu, 13 Apr 2006 09:00:02 -0500
Message-ID: <449B2580D802A443A923DABF3EAB82AF0BE3231A@OCCLUST04EVS1.ugd.att.com>
In-Reply-To: <443E4A48.70505@kddilabs.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [L1vpn] Proposals for three new working group documents
Thread-Index: AcZe+Z779M42fykmQbm78vMYfQ/OJgAB+T4g
From: "Brungard, Deborah A, ALABS" <dbrungard@att.com>
To: <otani@kddilabs.jp>,
	"Adrian Farrel" <adrian@olddog.co.uk>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: l1vpn@ietf.org
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Hi all,

Even though late, here's my 2-cents (1-euro cent):
1) yes
2) yes
3) abstain

Deborah=20

-----Original Message-----
From: Tomohiro Otani [mailto:otani@kddilabs.jp]=20
Sent: Thursday, April 13, 2006 8:56 AM
To: Adrian Farrel
Cc: l1vpn@ietf.org
Subject: Re: [L1vpn] Proposals for three new working group documents

Hi everyone,

The first and second drafts are OK, but the last one is to be discussed
more
and considered again after the next meeting judging from the mailing
list
discussion.

Regards,

tomo





Adrian Farrel wrote:
> Hi,
>=20
> In Dallas we agreed that we wanted to take the three basic mode I-Ds
into
> the working group.
>=20
> This email is to formally ask you for approval or issues with adopting
> these drafts as follows...
>=20
>=20
> draft-fedyk-l1vpn-basic-mode-01.txt
>   ---->draft-ietf-l1vpn-basic-mode-00.txt
>=20
> draft-ouldbrahim-l1vpn-bgp-auto-discovery-01.txt
>   ---->draft-ietf-l1vpn-bgp-auto-discovery-00.txt
>=20
> draft-bryskin-l1vpn-ospf-auto-discovery-01.txt
>   ---->draft-ietf-l1vpn-ospf-auto-discovery-00.txt
>=20
>=20
> Opinions please.
>=20
> Thanks,
> Adrian
>=20
>=20
> _______________________________________________
> L1vpn mailing list
> L1vpn@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/l1vpn
>=20


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

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



From l1vpn-bounces@lists.ietf.org Mon Apr 17 22:46:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FVgEH-0008Ds-B2; Mon, 17 Apr 2006 22:46:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FVgEF-0008Dn-Jb
	for l1vpn@ietf.org; Mon, 17 Apr 2006 22:46:11 -0400
Received: from mail2.noc.data.net.uk ([80.68.34.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FVgEE-0006Kf-AG
	for l1vpn@ietf.org; Mon, 17 Apr 2006 22:46:11 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99]
	helo=cortex.aria-networks.com)
	by mail2.noc.data.net.uk with esmtp (Exim 3.36 #1)
	id 1FVgEC-0006bW-00
	for l1vpn@ietf.org; Tue, 18 Apr 2006 03:46:08 +0100
Received: from Puppy ([221.17.113.241] RDNS failed) by
	cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Apr 2006 03:46:44 +0100
Message-ID: <040401c66292$48bf4640$2101fe0a@Puppy>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <l1vpn@ietf.org>
References: <00cf01c657c3$27568a60$4702010a@Puppy>
Subject: Re: [L1vpn] Working group last call on
	draft-ietf-l1vpn-framework-02.txt
Date: Tue, 18 Apr 2006 03:46:15 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
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: 18 Apr 2006 02:46:44.0375 (UTC)
	FILETIME=[542EFA70:01C66292]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: 
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Hi,

Here are my comments on this I-D. It looks good and ready. There are some
small nits...

Adrian

===

Some acronyms should be expanded the first time they are used. It is not
necessary to have a formal definition, just include the full term in the
text when it is first used.

TE
CE
PPVPN
TDM
L2
C
GMPLS
UNI
E-NNI

Section 4.2.1 second bullet
s/layer 1l/layer 1/

Section 4.3.2
s/providing a long haul/providing long-haul/

Section 4.3.5
s/at a planned in the future/at a planned time in the future/

Section 4.3.5
This is the first use of "L1 connection"

Section 4.3.5
s/according to schedule./according to a schedule./

Section 4.3.6
s/different L1VPN service provider./different L1VPN service providers./

Section 7.3 and 7.3.2
Suggest removing the reference to [GVPN]

Section 8
s/related to which/related to what/

Section 15
Suggest removing [GVPN]
[P&R Term] is now RFC 4427


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



From l1vpn-bounces@lists.ietf.org Wed Apr 19 20:21:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FWMuy-0003oG-Vz; Wed, 19 Apr 2006 20:21:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FWMux-0003ny-7e
	for l1vpn@ietf.org; Wed, 19 Apr 2006 20:21:07 -0400
Received: from mail1.noc.data.net.uk ([80.68.34.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWMuw-00018p-Ic
	for l1vpn@ietf.org; Wed, 19 Apr 2006 20:21:07 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99]
	helo=cortex.aria-networks.com)
	by mail1.noc.data.net.uk with esmtp (Exim 3.36 #2)
	id 1FWMvL-0008Pm-01
	for l1vpn@ietf.org; Thu, 20 Apr 2006 01:21:31 +0100
Received: from Puppy ([125.200.105.80] RDNS failed) by
	cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 20 Apr 2006 01:21:37 +0100
Message-ID: <065901c66410$58de3610$2101fe0a@Puppy>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <l1vpn@ietf.org>
References: <00cf01c657c3$27568a60$4702010a@Puppy>
Date: Thu, 20 Apr 2006 01:20:23 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
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: 20 Apr 2006 00:21:38.0046 (UTC)
	FILETIME=[63A219E0:01C66410]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: 
Subject: [L1vpn] Working group last call on
	draft-ietf-l1vpn-framework-02.txt ended
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Working group last call has completed on this draft with just my comments.

Editors: we need a new revision with some small editorial changes and then
I will pass the draft to the ADs.

Thanks,
Adrian
----- Original Message ----- 
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <l1vpn@ietf.org>
Sent: Tuesday, April 04, 2006 9:35 AM
Subject: [L1vpn] Working group last call on
draft-ietf-l1vpn-framework-02.txt


> This email starts a two week working group last call on "Framework and
> Requirements for Layer 1 Virtual Private Networks"
>
> http://www.ietf.org/internet-drafts/draft-ietf-l1vpn-framework-02.txt
>
> The last call will end on Tuesday 18th April at 12 noon GMT.
>
>
> Please note that all three working group chairs are authors of this
> document. In the event of any conflicts we will ask the ADs to
adjudicate.
>
> Thanks,
> Adrian
>
>
> _______________________________________________
> L1vpn mailing list
> L1vpn@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/l1vpn
>
>


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

From l1vpn-bounces@lists.ietf.org Wed Apr 19 20:21:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FWMuz-0003oT-BO; Wed, 19 Apr 2006 20:21:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FWMux-0003o8-8m
	for l1vpn@ietf.org; Wed, 19 Apr 2006 20:21:07 -0400
Received: from mail1.noc.data.net.uk ([80.68.34.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWMuw-00018o-Ic
	for l1vpn@ietf.org; Wed, 19 Apr 2006 20:21:07 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99]
	helo=cortex.aria-networks.com)
	by mail1.noc.data.net.uk with esmtp (Exim 3.36 #2)
	id 1FWMvFrom l1vpn-bounces@lists.ietf.org Wed Apr 19 20:21:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FWMuy-0003oG-Vz; Wed, 19 Apr 2006 20:21:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FWMux-0003ny-7e
	for l1vpn@ietf.org; Wed, 19 Apr 2006 20:21:07 -0400
Received: from mail1.noc.data.net.uk ([80.68.34.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWMuw-00018p-Ic
	for l1vpn@ietf.org; Wed, 19 Apr 2006 20:21:07 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99]
	helo=cortex.aria-networks.com)
	by mail1.noc.data.net.uk with esmtp (Exim 3.36 #2)
	id 1FWMvL-0008Pm-01
	for l1vpn@ietf.org; Thu, 20 Apr 2006 01:21:31 +0100
Received: from Puppy ([125.200.105.80] RDNS failed) by
	cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 20 Apr 2006 01:21:37 +0100
Message-ID: <065901c66410$58de3610$2101fe0a@Puppy>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <l1vpn@ietf.org>
References: <00cf01c657c3$27568a60$4702010a@Puppy>
Date: Thu, 20 Apr 2006 01:20:23 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
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: 20 Apr 2006 00:21:38.0046 (UTC)
	FILETIME=[63A219E0:01C66410]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: 
Subject: [L1vpn] Working group last call on
	draft-ietf-l1vpn-framework-02.txt ended
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Working group last call has completed on this draft with just my comments.

Editors: we need a new revision with some small editorial changes and then
I will pass the draft to the ADs.

Thanks,
Adrian
----- Original Message ----- 
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <l1vpn@ietf.org>
Sent: Tuesday, April 04, 2006 9:35 AM
Subject: [L1vpn] Working group last call on
draft-ietf-l1vpn-framework-02.txt


> This email starts a two week working group last call on "Framework and
> Requirements for Layer 1 Virtual Private Networks"
>
> http://www.ietf.org/internet-drafts/draft-ietf-l1vpn-framework-02.txt
>
> The last call will end on Tuesday 18th April at 12 noon GMT.
>
>
> Please note that all three working group chairs are authors of this
> document. In the event of any conflicts we will ask the ADs to
adjudicate.
>
> Thanks,
> Adrian
>
>
> _______________________________________________
> L1vpn mailing list
> L1vpn@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/l1vpn
>
>


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

From l1vpn-bounces@lists.ietf.org Wed Apr 19 20:21:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FWMuz-0003oT-BO; Wed, 19 Apr 2006 20:21:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FWMux-0003o8-8m
	for l1vpn@ietf.org; Wed, 19 Apr 2006 20:21:07 -0400
Received: from mail1.noc.data.net.uk ([80.68.34.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWMuw-00018o-Ic
	for l1vpn@ietf.org; Wed, 19 Apr 2006 20:21:07 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99]
	helo=cortex.aria-networks.com)
	by mail1.noc.data.net.uk with esmtp (Exim 3.36 #2)
	id 1FWMvL-0008Pm-00
	for l1vpn@ietf.org; Thu, 20 Apr 2006 01:21:31 +0100
Received: from Puppy ([125.200.105.80] RDNS failed) by
	cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 20 Apr 2006 01:21:35 +0100
Message-ID: <065801c66410$57cb3f70$2101fe0a@Puppy>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <l1vpn@ietf.org>
Date: Thu, 20 Apr 2006 01:18:22 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: 7bit
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: 20 Apr 2006 00:21:36.0234 (UTC)
	FILETIME=[628D9CA0:01C66410]
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: 
Subject: [L1vpn] Fw: IESG Statement: Normative and Informative References 
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Hi,

Good advice from the IESG on how to classify your references in I-Ds.

Adrian
----- Original Message ----- 
From: "IESG Secretary" <iesg-secretary@ietf.org>
To: "IETF Announcement list" <ietf-announce@ietf.org>
Sent: Wednesday, April 19, 2006 2:50 PM
Subject: IESG Statement: Normative and Informative References


> Normative and Informative References
>
> Nearly all RFCs contain citations to other documents, and these are
> listed in a References section near the end of the RFC. There are many
> styles for references, and the RFCs have one of their own. Please
> follow the reference style used in recent RFCs. Please note that for
> documents that have been assigned an STD or BCP number, the number must
> be included in the reference.
>
> Within an RFC, references to other documents fall into two general
> categories: "normative" and "informative". Normative references specify
> documents that must be read to understand or implement the technology
> in the new RFC, or whose technology must be present for the technology
> in the new RFC to work. An informative reference is not normative;
> rather, it only provides additional information. For example, an
> informative reference might provide background or historical
> information. Informative references are not required to implement the
> technology in the RFC.
>
> Note 1: Even references that are relevant only for optional features
> must be classified as normative if they meet the above conditions for
> normative references.
>
> Note 2: It is not considered necessary to cite basic specifications
> that may be safely assumed to be known to practitioners (for example,
> RFC 791 need not be cited in every specification that mentions IPv4).
>
> Note 3: The normative/informative distinction is relevant in
> any document that amounts to a technical specification, even
> if its intended status is Experimental or Informational.
>
> Note 4: Normative references in RFCs cannot be to "work in progress"
> documents such as Internet Drafts. Drafts with such references will
> not be published as RFCs until the references are also published.
>
> The distinction between normative and informative references is often
> important. The IETF standards process according to RFC 2026 and RFC
3967,
> and the RFC Editor publication process, both need to know whether a
> reference to a work in progress is normative. An RFC cannot be published
> until all of the documents that it lists as normative references have
been
> published. In practice, this often results in the simultaneous
publication
> of a group of interrelated RFCs.
>
> For thesL-0008Pm-00
	for l1vpn@ietf.org; Thu, 20 Apr 2006 01:21:31 +0100
Received: from Puppy ([125.200.105.80] RDNS failed) by
	cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 20 Apr 2006 01:21:35 +0100
Message-ID: <065801c66410$57cb3f70$2101fe0a@Puppy>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <l1vpn@ietf.org>
Date: Thu, 20 Apr 2006 01:18:22 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: 7bit
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: 20 Apr 2006 00:21:36.0234 (UTC)
	FILETIME=[628D9CA0:01C66410]
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: 
Subject: [L1vpn] Fw: IESG Statement: Normative and Informative References 
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Hi,

Good advice from the IESG on how to classify your references in I-Ds.

Adrian
----- Original Message ----- 
From: "IESG Secretary" <iesg-secretary@ietf.org>
To: "IETF Announcement list" <ietf-announce@ietf.org>
Sent: Wednesday, April 19, 2006 2:50 PM
Subject: IESG Statement: Normative and Informative References


> Normative and Informative References
>
> Nearly all RFCs contain citations to other documents, and these are
> listed in a References section near the end of the RFC. There are many
> styles for references, and the RFCs have one of their own. Please
> follow the reference style used in recent RFCs. Please note that for
> documents that have been assigned an STD or BCP number, the number must
> be included in the reference.
>
> Within an RFC, references to other documents fall into two general
> categories: "normative" and "informative". Normative references specify
> documents that must be read to understand or implement the technology
> in the new RFC, or whose technology must be present for the technology
> in the new RFC to work. An informative reference is not normative;
> rather, it only provides additional information. For example, an
> informative reference might provide background or historical
> information. Informative references are not required to implement the
> technology in the RFC.
>
> Note 1: Even references that are relevant only for optional features
> must be classified as normative if they meet the above conditions for
> normative references.
>
> Note 2: It is not considered necessary to cite basic specifications
> that may be safely assumed to be known to practitioners (for example,
> RFC 791 need not be cited in every specification that mentions IPv4).
>
> Note 3: The normative/informative distinction is relevant in
> any document that amounts to a technical specification, even
> if its intended status is Experimental or Informational.
>
> Note 4: Normative references in RFCs cannot be to "work in progress"
> documents such as Internet Drafts. Drafts with such references will
> not be published as RFCs until the references are also published.
>
> The distinction between normative and informative references is often
> important. The IETF standards process according to RFC 2026 and RFC
3967,
> and the RFC Editor publication process, both need to know whether a
> reference to a work in progress is normative. An RFC cannot be published
> until all of the documents that it lists as normative references have
been
> published. In practice, this often results in the simultaneous
publication
> of a group of interrelated RFCs.
>
> For these reasons, the IESG and the RFC Editor have established
> guidelines that will request separate reference lists for normative
> and informative references in Internet Drafts and RFCs. For example,
> if both types are present, there would be two reference subsections,
> numbered s.1 and s.2 for example:
>
> s.1. Normative References
>
> xxx
> ...
> xxx
>
> s.2. Informative References
>
> xxx
> ...
> xxx
>
> Of course, if there is only one type of reference, only one
> section is needed.
>
> The IESG
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce
>
>


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





e reasons, the IESG and the RFC Editor have established
> guidelines that will request separate reference lists for normative
> and informative references in Internet Drafts and RFCs. For example,
> if both types are present, there would be two reference subsections,
> numbered s.1 and s.2 for example:
>
> s.1. Normative References
>
> xxx
> ...
> xxx
>
> s.2. Informative References
>
> xxx
> ...
> xxx
>
> Of course, if there is only one type of reference, only one
> section is needed.
>
> The IESG
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce
>
>


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





From l1vpn-bounces@lists.ietf.org Wed Apr 19 21:01:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FWNXf-0007v7-Vp; Wed, 19 Apr 2006 21:01:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FWNXe-0007v2-Tt
	for l1vpn@ietf.org; Wed, 19 Apr 2006 21:01:06 -0400
Received: from tama5.ecl.ntt.co.jp ([129.60.39.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWNXZ-00036m-Hj
	for l1vpn@ietf.org; Wed, 19 Apr 2006 21:01:06 -0400
Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110])
	by tama5.ecl.ntt.co.jp (8.13.6/8.13.6) with ESMTP id k3K10wXg004859; 
	Thu, 20 Apr 2006 10:00:58 +0900 (JST)
Received: from mfs3.rdh.ecl.ntt.co.jp (mfs3.rdh.ecl.ntt.co.jp [129.60.39.112])
	by vcs3.rdh.ecl.ntt.co.jp (8.13.6/8.13.6) with ESMTP id
	k3K10vWJ021561; Thu, 20 Apr 2006 10:00:57 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp ([129.60.39.100])
	by mfs3.rdh.ecl.ntt.co.jp (8.13.6/8.13.6) with ESMTP id k3K10uUk001906; 
	Thu, 20 Apr 2006 10:00:56 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp
	[129.60.5.69])
	by nttmail3.ecl.ntt.co.jp (8.13.6/8.13.6) with ESMTP id k3K10u5N010913; 
	Thu, 20 Apr 2006 10:00:56 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	k3K10uXV009233; Thu, 20 Apr 2006 10:00:56 +0900 (JST)
Received: from imf.m.ecl.ntt.co.jp (imf.m.ecl.ntt.co.jp [129.60.5.230])
	by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	k3K10tke009230; Thu, 20 Apr 2006 10:00:55 +0900 (JST)
Received: from TAKEDA_PANA.lab.ntt.co.jp ([129.60.80.92])
	by imf.m.ecl.ntt.co.jp (8.13.4/8.13.4) with ESMTP id k3K10tVw028300;
	Thu, 20 Apr 2006 10:00:55 +0900 (JST)
Message-Id: <5.1.1.9.2.20060420100103.06833eb8@imf.m.ecl.ntt.co.jp>
X-Sender: tt043@imf.m.ecl.ntt.co.jp
X-Mailer: QUALCOMM Windows Eudora Version 5.1-Jr3
Date: Thu, 20 Apr 2006 10:01:45 +0900
To: Adrian Farrel <adrian@olddog.co.uk>, <l1vpn@ietf.org>
From: Tomonori TAKEDA <takeda.tomonori@lab.ntt.co.jp>
Subject: Re: [L1vpn] Working group last call
	ondraft-ietf-l1vpn-framework-02.txt ended
In-Reply-To: <065901c66410$58de3610$2101fe0a@Puppy>
References: <00cf01c657c3$27568a60$4702010a@Puppy>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: 
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Will do so shortly.

Thanks,
Tomonori

At 01:20 06/04/20 +0100, Adrian Farrel wrote:
>Working group last call has completed on this draft with just my comments.
>
>Editors: we need a new revision with some small editorial changes and then
>I will pass the draft to the ADs.
>
>Thanks,
>Adrian
>----- Original Message -----
>From: "Adrian Farrel" <adrian@olddog.co.uk>
>To: <l1vpn@ietf.org>
>Sent: Tuesday, April 04, 2006 9:35 AM
>Subject: [L1vpn] Working group last call on
>draft-ietf-l1vpn-framework-02.txt
>
>
> > This email starts a two week working group last call on "Framework and
> > Requirements for Layer 1 Virtual Private Networks"
> >
> > http://www.ietf.org/internet-drafts/draft-ietf-l1vpn-framework-02.txt
> >
> > The last call will end on Tuesday 18th April at 12 noon GMT.
> >
> >
> > Please note that all three working group chairs are authors of this
> > document. In the event of any conflicts we will ask the ADs to
>adjudicate.
> >
> > Thanks,
> > Adrian
> >
> >
> > _______________________________________________
> > L1vpn mailing list
> > L1vpn@lists.ietf.org
> > https://www1.ietf.org/mailman/listinfo/l1vpn
> >
> >
>
>
>_______________________________________________
>L1vpn mailing list
>L1vpn@lists.ietf.org
>https://www1.ietf.org/mailman/listinfo/l1vpn


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



From l1vpn-bounces@lists.ietf.org Thu Apr 20 07:47:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FWXd8-0000DZ-BM; Thu, 20 Apr 2006 07:47:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FWXd7-0000DU-0a
	for l1vpn@ietf.org; Thu, 20 Apr 2006 07:47:25 -0400
Received: from mail1.noc.data.net.uk ([80.68.34.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWXd6-0002IS-KN
	for l1vpn@ietf.org; Thu, 20 Apr 2006 07:47:24 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99]
	helo=cortex.aria-networks.com)
	by mail1.noc.data.net.uk with esmtp (Exim 3.36 #2)
	id 1FWXdH-0003a0-00
	for l1vpn@ietf.org; Thu, 20 Apr 2006 12:47:35 +0100
Received: from Puppy ([125.200.105.80] RDNS failed) by
	cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 20 Apr 2006 12:47:58 +0100
Message-ID: <000001c66470$3adb1970$0d11a8c0@Puppy>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <Dimitri.Papadimitriou@alcatel.be>
References: <OFB3E3AF19.125611F0-ONC125714E.0078D2BD-C125714F.002609E6@netfr.alcatel.fr>
Subject: Re: [L1vpn] Draft minutes uploaded
Date: Thu, 20 Apr 2006 04:26:04 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
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: 20 Apr 2006 11:47:58.0781 (UTC)
	FILETIME=[454396D0:01C66470]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: l1vpn@ietf.org
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Dimitri,

>> "- Dimitri: Please clarity the use of PCE
>> - Tomonori: As Adrian said, CCAMP has selected PCE. L1VPN is not
requiring
>>    the use of PCE, but recognising the possiblity of using PCE for P&R"
>
> but this is not what adrian could have said as i've never seen a
statement
> such as L1VPN recognizes the possibility of using PCE for P&R ... as
> there is no CE dual homing discussion since so far

In fact, what I said is recorded pretty well in the minutes immediately
above. To remind you, I was speaking from the floor as CCAMP chair.

Adrian: CCAMP has a work item for multi-domain recovery.
        The L1VPN CE has a different visibility from the core network so
is like multi-domain.
        For the unprotected case in multi-domain, CCAMP found that PCE
would be a good approach
        I may expect a similar approach from CCAMP for protected
multi-domain.

You are right that L1VPN has not started work on P&R in any detail, and
functions like CE dual homing are beyond the scope of the Basic Model. So,
nothing is decided.

Tomonori stressed that L1VPN does not require the use of PCE. He is also
correct to say that we should recognise and discuss the possility of using
PCE to resolve questions of computational visiblity.

A

PS. Thanks for the other comments below.

>
> "Dimitri: It is a timing issue; They have today an OSPF environment and
> are willing to deploy quickly.
>          BGP may be a solution in 4-5 years"
>
> the last part of the message was "No doubt that BGP is a sensible
> approach, but if we have to base our timing
> by relying on IGP deployment experience, BGP may be the solution of
choice
> in 4-5 years."
>
> "Yakov: Update on the BGP-based auto-discovery
>        We don't want to have a new AFI, we just need a new SAFI
>        New format for l1vpn LNRI"
>
> guess you mean NLRI
>
>
>
>
>
> "Adrian Farrel" <adrian@olddog.co.uk>
> 10/04/2006 15:25
> Please respond to Adrian Farrel
>
>         To:     <l1vpn@ietf.org>
>         cc:
>         Subject:        [L1vpn] Draft minutes uploaded
>
>
> Hi,
>
> Please review the minutes at
> http://www3.ietf.org/proceedings/06mar/minutes/l1vpn.html
>
> Comments on the list or to the chairs.
>
> Thanks,
> Adrian
>
>
> _______________________________________________
> L1vpn mailing list
> L1vpn@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/l1vpn
>
>
>
>


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



From l1vpn-bounces@lists.ietf.org Thu Apr 20 10:31:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FWaCE-0001hG-50; Thu, 20 Apr 2006 10:31:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FWaCD-0001hB-HS
	for l1vpn@ietf.org; Thu, 20 Apr 2006 10:31:49 -0400
Received: from cronos.ocn.ne.jp ([222.146.51.136] helo=smtp.cronos.ocn.ne.jp)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWaCC-0002lC-UQ
	for l1vpn@ietf.org; Thu, 20 Apr 2006 10:31:49 -0400
Received: from [127.0.0.1] (p2198-ipbf1002marunouchi.tokyo.ocn.ne.jp
	[203.140.121.198]) by smtp.cronos.ocn.ne.jp (Postfix) with ESMTP
	id E1E1E2B0B; Thu, 20 Apr 2006 23:31:43 +0900 (JST)
Date: Thu, 20 Apr 2006 23:31:38 +0900
From: Tomonori TAKEDA <takeda.tomonori@lab.ntt.co.jp>
To: Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: [L1vpn] Draft minutes uploaded
In-Reply-To: <000001c66470$3adb1970$0d11a8c0@Puppy>
References: <OFB3E3AF19.125611F0-ONC125714E.0078D2BD-C125714F.002609E6@netfr.alcatel.fr>
	<000001c66470$3adb1970$0d11a8c0@Puppy>
Message-Id: <20060420231732.9388.TAKEDA.TOMONORI@lab.ntt.co.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.20.07 [ja]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: Dimitri.Papadimitriou@alcatel.be, l1vpn@ietf.org
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: takeda.tomonori@lab.ntt.co.jp
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Dimitri, Adrian, all,

Thanks for clarification.

Yes, there is not much text on using PCE for L1VPNs, and L1VPNs have not
started P&R in detail.

My intension was we might want to start thinking about analysis of P&R
in L1VPNs, and if that is the case, PCE may come into play. It was not
my intention that PCE is *THE* solution for L1VPNs (analysis needed).
Also, I agree that CE-CE recovery is beyond the basic mode.

Thanks,
Tomonori

On Thu, 20 Apr 2006 04:26:04 +0100
"Adrian Farrel" <adrian@olddog.co.uk> wrote:

> Dimitri,
> 
> >> "- Dimitri: Please clarity the use of PCE
> >> - Tomonori: As Adrian said, CCAMP has selected PCE. L1VPN is not
> requiring
> >>    the use of PCE, but recognising the possiblity of using PCE for P&R"
> >
> > but this is not what adrian could have said as i've never seen a
> statement
> > such as L1VPN recognizes the possibility of using PCE for P&R ... as
> > there is no CE dual homing discussion since so far
> 
> In fact, what I said is recorded pretty well in the minutes immediately
> above. To remind you, I was speaking from the floor as CCAMP chair.
> 
> Adrian: CCAMP has a work item for multi-domain recovery.
>         The L1VPN CE has a different visibility from the core network so
> is like multi-domain.
>         For the unprotected case in multi-domain, CCAMP found that PCE
> would be a good approach
>         I may expect a similar approach from CCAMP for protected
> multi-domain.
> 
> You are right that L1VPN has not started work on P&R in any detail, and
> functions like CE dual homing are beyond the scope of the Basic Model. So,
> nothing is decided.
> 
> Tomonori stressed that L1VPN does not require the use of PCE. He is also
> correct to say that we should recognise and discuss the possility of using
> PCE to resolve questions of computational visiblity.
> 
> A
> 
> PS. Thanks for the other comments below.
> 
> >
> > "Dimitri: It is a timing issue; They have today an OSPF environment and
> > are willing to deploy quickly.
> >          BGP may be a solution in 4-5 years"
> >
> > the last part of the message was "No doubt that BGP is a sensible
> > approach, but if we have to base our timing
> > by relying on IGP deployment experience, BGP may be the solution of
> choice
> > in 4-5 years."
> >
> > "Yakov: Update on the BGP-based auto-discovery
> >        We don't want to have a new AFI, we just need a new SAFI
> >        New format for l1vpn LNRI"
> >
> > guess you mean NLRI
> >
> >
> >
> >
> >
> > "Adrian Farrel" <adrian@olddog.co.uk>
> > 10/04/2006 15:25
> > Please respond to Adrian Farrel
> >
> >         To:     <l1vpn@ietf.org>
> >         cc:
> >         Subject:        [L1vpn] Draft minutes uploaded
> >
> >
> > Hi,
> >
> > Please review the minutes at
> > http://www3.ietf.org/proceedings/06mar/minutes/l1vpn.html
> >
> > Comments on the list or to the chairs.
> >
> > Thanks,
> > Adrian
> >
> >
> > _______________________________________________
> > L1vpn mailing list
> > L1vpn@lists.ietf.org
> > https://www1.ietf.org/mailman/listinfo/l1vpn
> >
> >
> >
> >
> 
> 
> _______________________________________________
> L1vpn mailing list
> L1vpn@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/l1vpn


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



From l1vpn-bounces@lists.ietf.org Tue Apr 25 09:14:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FYNMv-00036f-R8; Tue, 25 Apr 2006 09:14:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FYNMu-00032V-Oj
	for l1vpn@ietf.org; Tue, 25 Apr 2006 09:14:16 -0400
Received: from mail1.noc.data.net.uk ([80.68.34.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FYNMt-0007V5-Fa
	for l1vpn@ietf.org; Tue, 25 Apr 2006 09:14:16 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99]
	helo=cortex.aria-networks.com)
	by mail1.noc.data.net.uk with esmtp (Exim 3.36 #2)
	id 1FYNN6-0005LV-00
	for l1vpn@ietf.org; Tue, 25 Apr 2006 14:14:28 +0100
Received: from youref3aa80866 ([125.200.105.81] RDNS failed) by
	cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 25 Apr 2006 14:14:50 +0100
Message-ID: <030c01c6686b$1b199a90$0e11a8c0@youref3aa80866>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <l1vpn@ietf.org>
Date: Tue, 25 Apr 2006 14:20:55 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-OriginalArrivalTime: 25 Apr 2006 13:14:50.0796 (UTC)
	FILETIME=[3BEEB6C0:01C6686A]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: 
Subject: [L1vpn] New working group drafts
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Hi,

We asked for opinions on three I-Ds.

The chairs believe we have consensus to adopt draft-fedyk-l1vpn-basic-mode 
and draft-ouldbrahim-l1vpn-bgp-auto-discovery.

Would the authors please go ahead and submit draft-ietf-l1vpn-basic-mode and 
draft-ietf-l1vpn-bgp-auto-discovery. Note that the only changes you should 
make are:
- filename
- dates
- references if they need to be updated
- any boilerplate of format needed to pass idnits

There is not clear consensus yet about 
draft-bryskin-l1vpn-ospf-auto-discovery. Although the chairs think that this 
draft is very readable and clear, it has changed quite a lot since the 
previous revision, and it was clear that some people had not yet had a 
chance to read and digest. Additionally, the chairs polled the OSPF WG 
chairs who have some concerns that they would like to discuss.

We note that the meeting in Dallas was clear that theri should not be a 
beauty contest between these I-Ds, but that both should be allowed to 
proceed leaving the choice to develop as the I-Ds proceed based on 
implementaiton and deployment.

What we propose for this draft is as follows:
- people need to read the latest version
- the chairs will summarise the issues that have been raised (including from 
the OSPF chairs)
- we can discuss the issues on the list
We will aim to make a more firm decision over the next 6 to 8 weeks so that 
we know where we stand before Montreal.

Thanks,
Adrian 



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



From l1vpn-bounces@lists.ietf.org Fri Apr 28 17:02:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FZa6H-0001pY-5M; Fri, 28 Apr 2006 17:02:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FZa6E-0001p9-Q8; Fri, 28 Apr 2006 17:02:02 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FZZ8u-0008Q2-Q2; Fri, 28 Apr 2006 16:00:44 -0400
Received: from cypress.neustar.com ([209.173.57.84])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1FZYyY-0005Qi-1d; Fri, 28 Apr 2006 15:50:08 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by cypress.neustar.com (8.12.8/8.12.8) with ESMTP id k3SJo10e026773
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 28 Apr 2006 19:50:01 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FZYyX-0007We-KZ; Fri, 28 Apr 2006 15:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1FZYyX-0007We-KZ@stiedprstage1.ietf.org>
Date: Fri, 28 Apr 2006 15:50:01 -0400
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: l1vpn@ietf.org
Subject: [L1vpn] I-D ACTION:draft-ietf-l1vpn-framework-03.txt 
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

--NextPart

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

	Title		: Framework and Requirements for Layer 1 Virtual Private Networks
	Author(s)	: T. Takeda
	Filename	: draft-ietf-l1vpn-framework-03.txt
	Pages		: 32
	Date		: 2006-4-28
	
This document provides a framework and service level requirements
   for Layer 1 Virtual Private Networks (L1VPNs). This framework is
   intended to aid in developing and standardizing protocols and
   mechanisms to support interoperable L1VPNs.

   The document examines motivations for L1VPNs, high level (service
   level) requirements, and outlines some of the architectural models
   that might be used to build L1VPNs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l1vpn-framework-03.txt

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


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

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


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

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

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

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

Content-Type: text/plain
Content-ID: <2006-4-28143103.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l1vpn-framework-03.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-l1vpn-framework-03.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-4-28143103.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From l1vpn-bounces@lists.ietf.org Sun Apr 30 08:44:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FaBHe-0006ro-LA; Sun, 30 Apr 2006 08:44:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FaBHd-0006rj-9d
	for l1vpn@ietf.org; Sun, 30 Apr 2006 08:44:17 -0400
Received: from i218-47-214-243.s07.a012.ap.plala.or.jp ([218.47.214.243]
	helo=localhost.localdomain)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FaBHc-00011x-L2
	for l1vpn@ietf.org; Sun, 30 Apr 2006 08:44:17 -0400
Received: from youref3aa80866 (unknown [172.16.2.2])
	by localhost.localdomain (Postfix) with ESMTP id B88E991C
	for <l1vpn@ietf.org>; Sun, 30 Apr 2006 21:43:06 +0900 (JST)
Message-ID: <00c101c66c54$c470fe70$020210ac@youref3aa80866>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <l1vpn@ietf.org>
References: <E1FZYyX-0007We-KZ@stiedprstage1.ietf.org>
Subject: Re: [L1vpn] I-D ACTION:draft-ietf-l1vpn-framework-03.txt 
Date: Sun, 30 Apr 2006 13:47:33 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 4.4 (++++)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: 
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>,
	<mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Errors-To: l1vpn-bounces@lists.ietf.org

Tomonori,

Thanks for updating the draft. I will ask the ADs to start their review.

Cheers,
Adrian
----- Original Message ----- 
From: <Internet-Drafts@ietf.org>
To: <i-d-announce@ietf.org>
Cc: <l1vpn@ietf.org>
Sent: Friday, April 28, 2006 8:50 PM
Subject: [L1vpn] I-D ACTION:draft-ietf-l1vpn-framework-03.txt


>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
> This draft is a work item of the Layer 1 Virtual Private Networks Working 
> Group of the IETF.
>
> Title : Framework and Requirements for Layer 1 Virtual Private Networks
> Author(s) : T. Takeda
> Filename : draft-ietf-l1vpn-framework-03.txt
> Pages : 32
> Date : 2006-4-28
>
> This document provides a framework and service level requirements
>   for Layer 1 Virtual Private Networks (L1VPNs). This framework is
>   intended to aid in developing and standardizing protocols and
>   mechanisms to support interoperable L1VPNs.
>
>   The document examines motivations for L1VPNs, high level (service
>   level) requirements, and outlines some of the architectural models
>   that might be used to build L1VPNs.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-l1vpn-framework-03.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of the 
> message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>
>
> Internet-Drafts are also available by anonymous FTP. Login with the 
> username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> "get draft-ietf-l1vpn-framework-03.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> mailserv@ietf.org.
> In the body type:
> "FILE /internet-drafts/draft-ietf-l1vpn-framework-03.txt".
>
> NOTE: The mail server at ietf.org can return the document in
> MIME-encoded form by using the "mpack" utility.  To use this
> feature, insert the command "ENCODING mime" before the "FILE"
> command.  To decode the response(s), you will need "munpack" or
> a MIME-compliant mail reader.  Different MIME-compliant mail readers
> exhibit different behavior, especially when dealing with
> "multipart" MIME messages (i.e. documents which have been split
> up into multiple messages), so check your local documentation on
> how to manipulate these messages.
>
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>


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


> _______________________________________________
> L1vpn mailing list
> L1vpn@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/l1vpn
> 



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



