RE: [Idr] MInutes for IDR
"Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com> Mon, 13 December 2004 11:47 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 GAA26280; Mon, 13 Dec 2004 06:47:57 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cdoo7-0002wm-Rp; Mon, 13 Dec 2004 06:56:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CdoeZ-0000mJ-Na; Mon, 13 Dec 2004 06:46:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CdobX-00007o-UO for idr@megatron.ietf.org; Mon, 13 Dec 2004 06:43:04 -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 GAA25864 for <idr@ietf.org>; Mon, 13 Dec 2004 06:43:01 -0500 (EST)
Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdojK-0002pX-Gj for idr@ietf.org; Mon, 13 Dec 2004 06:51:08 -0500
Received: from ams-core-1.cisco.com (144.254.224.150) by ams-iport-1.cisco.com with ESMTP; 13 Dec 2004 12:49:57 +0100
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from xbh-ams-331.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iBDBgQGb004211; Mon, 13 Dec 2004 12:42:27 +0100 (MET)
Received: from xmb-ams-333.cisco.com ([144.254.231.78]) by xbh-ams-331.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 13 Dec 2004 12:42:26 +0100
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: [Idr] MInutes for IDR
Date: Mon, 13 Dec 2004 12:38:52 +0100
Message-ID: <A05118C6DF9320488C77F3D5459B17B7764A44@xmb-ams-333.emea.cisco.com>
Thread-Topic: [Idr] MInutes for IDR
Thread-Index: AcTe1M1W6rWg0MNgQM+kkJPUpeMTcwCKb+IA
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: Susan Hares <shares@nexthop.com>
X-OriginalArrivalTime: 13 Dec 2004 11:42:26.0705 (UTC) FILETIME=[D1AE1010:01C4E108]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Content-Transfer-Encoding: quoted-printable
Cc: yakov@juniper.net, "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>, idr@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Content-Transfer-Encoding: quoted-printable
Hi Sue, Comments on the minutes re bgp-tunnel: IPv6 over IPv4 MPLS (Francis LeFaucheur, presenter) --------------------------------------------------- Right spelling for my name is "Francois Le Faucheur" I suggest listing the draft being discussed (draft-ooms-v6ops-bgp-tunnel-04.txt) The draft presents a technique, which will be coordinated with V6OPS s/which will be/which has been/ through the ADs, for providing IPv6 service over an existing IPv4 MPLS cloud, without the cloud needing to be V6-aware. The proposed solution is intended to require no protocll extensions (see s/is intented to require no/does not require any/ draft-ietf-l3vpn-bgp-ipv6). It carris labels in MP-BGP. The Please remove the reference to draft-ietf-l3vpn-bgp-ipv6 above. The stamement about not requiring protocol extensions in bgp-tunnel has nothing to do with l3vpn-bgp-ipv6. requiriemens are stated in draft-ietf-v6ops-isp-scenarios-analysis-03.txt. Draft 04 is underway, and will clarify some MUST/SHOULD terminology, expand on the inter-AS cases, and add additional detail on security. There is some confusion here. The 03-->04 changes related to the bgp-tunnel draft (not to isp-scenario). These changes have already been done in bgp-tunnel-04. So the above should read: "bgp-tunnel-04 includes the following changes over the previous version: clarify some MUST/SHOULD terminology, expand on the inter-AS cases, and add additional detail on security." Publication of this specification will involve coordinated documents between V6OPS and IDR, consistent where possible and different where necessary. For example, the V6OPS document will carry label SAFI/AFI while the IDR document will carry VPN SAFI/AFI. This paragraph mixes everything up. It should read: "draft-ooms-v6ops-bgp-tunnel-04.txt specifies support for global IPv6 reachability services while draft-ietf-l3vpn-bgp-ipv6-03.txt specifies support for IPv6 VPN services. The two documents are consistent wherever they can be and are only different where needed (eg bgp-tunnel uses "labeled IPv6" AFI/SAFI while l3vpn-bgp-ipv6 uses "VPN-IPv6" AFI/SAFI). After the editorial changes are complete, the document will go out for last call and implementation survey. I believe what was agreed was that the document was ready for Last Call and the Last Call was going to be issued right after Wash IETF. So I suggest replacing previous paragraph with something like: "The document will go out for Last Call after this meeting". Thank you Francois _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr
- [Idr] MInutes for IDR Susan Hares
- RE: [Idr] MInutes for IDR Bhatia, Manav
- RE: [Idr] MInutes for IDR Francois Le Faucheur (flefauch)
- RE: [Idr] MInutes for IDR Francois Le Faucheur (flefauch)
- RE: [Idr] MInutes for IDR Francois Le Faucheur (flefauch)
- RE: [Idr] MInutes for IDR Susan Hares