Fwd: L1VPN drafts
Alex Zinin <zinin@psg.com> Tue, 29 March 2005 23:53 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11577 for <rtg-dir-archive@ietf.org>; Tue, 29 Mar 2005 18:53:01 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DGQcw-0004gS-2m for rtg-dir-archive@ietf.org; Tue, 29 Mar 2005 19:00:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DGQVL-0004l5-0M; Tue, 29 Mar 2005 18:52:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DGQVJ-0004l0-9N for rtg-dir@megatron.ietf.org; Tue, 29 Mar 2005 18:52:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11497 for <rtg-dir@ietf.org>; Tue, 29 Mar 2005 18:52:10 -0500 (EST)
Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DGQc7-0004fb-1j for rtg-dir@ietf.org; Tue, 29 Mar 2005 18:59:15 -0500
Received: from psg.com ([147.28.0.62] helo=[127.0.0.1]) by psg.com with esmtp (Exim 4.44 (FreeBSD)) id 1DGQVH-0009iv-M2 for rtg-dir@ietf.org; Tue, 29 Mar 2005 23:52:11 +0000
Date: Tue, 29 Mar 2005 15:52:03 -0800
From: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <1056837882.20050329155203@psg.com>
To: rtg-dir@ietf.org
In-Reply-To: <007001c52319$65a7d6a0$a4858182@Puppy>
References: <007001c52319$65a7d6a0$a4858182@Puppy>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------71CCF32A9A9B1D"
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8
Subject: Fwd: L1VPN drafts
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Alex Zinin <zinin@psg.com>
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
Sender: rtg-dir-bounces@ietf.org
Errors-To: rtg-dir-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 2ed806e2f53ff1a061ad4f97e00345ac
Directorate people- I'll be cc'ing rtg-dir on my discussion with Adrian, Takeda, et al on L1VPNs. Opinions are appreciated please feel free to chime in. Attached are e-mails listing the reading material. -- Alex http://www.psg.com/~zinin
--- Begin Message ---Alex, Here's your reading :-) Framework http://www.ietf.org/internet-drafts/draft-takeda-l1vpn-framework-03.txt This is really well cooked. Apart from editorial, the authors think there is nothing else to do. Applicability (of protocols to meeting the framework) http://www.ietf.org/internet-drafts/draft-takeda-l1vpn-applicability-02.txt This needs another pass by the authors to fill in some blanks. But it is pretty well advanced. Specific solution http://www.ietf.org/internet-drafts/draft-ouldbrahim-ppvpn-gvpn-bgpgmpls-06.txt This draft has been around for the longest time. Conceptually it is done. I believe there is an implementation Second protocol solution model http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gmpls-overlay-05.txt The "GMPLS UNI" draft specifically mentions L1VPNs and solves some of the models. For other models it might need some extensions. This draft is "pending announcement" Questions? Adrian--- End Message ---
--- Begin Message ---Hi Alex, I am Tomonori Takeda of NTT, who has been participating in IETF (especially CCAMP) for a while. Thank you very much for discussing with me L1VPN related topics several times. As you may know, I was a contributor to the ITU-T recommendations on L1VPNs, but I thought it would be best if the protocol extensions were done within the IETF, so I worked to present the requirements and architecture as Internet-Drafts. I am currently the editor of the framework draft and the applicability analysis draft that explains how existing protocols can be used to provide L1VPNs. I would appreciate your kind offer to read those L1VPN related I-Ds, as you mentioned in the previous IETF meeting. I am wondering it might be helpful to contact you now so that the I-Ds are cleardy understood. I would be more than happy to discuss any issue, and/or provide any clarification. Two I-Ds are as follows. http://www.ietf.org/internet-drafts/draft-takeda-l1vpn-framework-03.txt http://www.ietf.org/internet-drafts/draft-takeda-l1vpn-applicability-02.txt Best regards, ----- Tomonori TAKEDA NTT Network Service Systems Lab. Phone: +81-422-59-7434--- End Message ---
- Fwd: L1VPN drafts Alex Zinin