Open invitation to BGP/PB L3VPN & BGP/PBB L3VPN discussion thread
"Peter Kao" <peterk@ipinfusion.com> Thu, 13 January 2011 05:05 UTC
Return-Path: <peterk@ipinfusion.com>
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 76AFE3A6A40 for <l3vpn@core3.amsl.com>; Wed, 12 Jan 2011 21:05:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.999
X-Spam-Level:
X-Spam-Status: No, score=-4.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_INVITATION=-2, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P6o9YX2ZVLsm for <l3vpn@core3.amsl.com>; Wed, 12 Jan 2011 21:05:51 -0800 (PST)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 783823A68AF for <l3vpn@ietf.org>; Wed, 12 Jan 2011 21:05:51 -0800 (PST)
Received: by gwj17 with SMTP id 17so582412gwj.31 for <l3vpn@ietf.org>; Wed, 12 Jan 2011 21:08:12 -0800 (PST)
Received: by 10.90.99.12 with SMTP id w12mr2069971agb.192.1294895290870; Wed, 12 Jan 2011 21:08:10 -0800 (PST)
Received: from PETERKE6410 (h-64-105-174-211.snvacaid.static.covad.net [64.105.174.211]) by mx.google.com with ESMTPS id d15sm1696890ana.35.2011.01.12.21.08.08 (version=SSLv3 cipher=RC4-MD5); Wed, 12 Jan 2011 21:08:09 -0800 (PST)
From: Peter Kao <peterk@ipinfusion.com>
To: l3vpn@ietf.org
References: <D26161FB-3E52-4EEE-962A-FD0160BC6D8F@niven-jenkins.co.uk>
Subject: Open invitation to BGP/PB L3VPN & BGP/PBB L3VPN discussion thread
Date: Wed, 12 Jan 2011 21:08:02 -0800
Message-ID: <C2AA2312F35641E585A2405DDEDFCB7D@PETERKE6410>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <D26161FB-3E52-4EEE-962A-FD0160BC6D8F@niven-jenkins.co.uk>
Thread-Index: AcutCPMYK7ltHaetQAKf8P1Ak5dUjwF1Bfmg
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 05:05:52 -0000
Dear Colleagues, L3VPN working group, I have recently submitted three drafts for standards track consideration; http://tools.ietf.org/html/draft-kao-pb-l3vpn-00 This document describes a method by which a Service Provider may use an IEEE 802.1ad PBN (Provider Bridge Network) to provide IP Virtual Private Network Service for its customers. This method extends the BGP/MPLS IP VPN service to allow IP VPN service to be offered using a PBN instead. http://tools.ietf.org/html/draft-kao-pbb-l3vpn-00 This document describes a method by which a Service Provider may use an IEEE 802.1ah PBBN (Provider Backbone Bridge Network) to provide IP Virtual Private Network Service for its customers. This method extends the BGP/MPLS IP VPN service to allow IP VPN service to be offered using a PBN instead. http://tools.ietf.org/html/draft-kao-path-binding-bgp4-00 When BGP is used to distribute a route, it can also be used to distribute a Link Layer PATH_NEXT_HOP binding which is mapped to that route such that packets to that network route can be switched directly across an Ethernet switched network. The motivation for using PB/PBB rather than an MPLS core for IP/VPN is as follows - As flat mobile networks (4G/LTE, mobile WiMAX, HSPA+ flat, and UMB) emerge, IP routing is being pushed more and more from the Metro Core towards the Metro Access and Aggregation networks to provide support for single IP-RAN and any-to-any IP connectivity between base stations. The current, existing Metro Ethernet Backhaul infrastructure in place based on PB can't support routed flat mobile network with any-to-any IP connectivity, it just can't do routing. As such, IPMPLSForum20.0.0 proposed an all MPLS access/aggregation/core network solution to support flat mobile networks with L3VPN capability. The submitted drafts propose a way to enable existing and new Metro PB switched access/aggregation networks with IETF RFC4364 L3VPN capability for the emerging flat mobile networks and converged Metro transport with L1, L2, and L3 support. Cordially, I would like to invite you to an open discussion on the mailing list and give all of us a precious opportunity to hear your feedback and thoughts. Thx & Regards, Ares, P., Kao peterk@ipinfusion.com
- L3VPN agenda slots at IETF80 (aka does L3VPN need… Ben Niven-Jenkins
- Open invitation to BGP/PB L3VPN & BGP/PBB L3VPN d… Peter Kao
- L3VPN will not meet at IETF80 Ben Niven-Jenkins