RE: [Idr] MInutes for IDR
"Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com> Fri, 28 January 2005 16:23 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 LAA14918; Fri, 28 Jan 2005 11:23:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CuZBd-0000gU-1p; Fri, 28 Jan 2005 11:41:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CuYoB-00010a-28; Fri, 28 Jan 2005 11:17:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CuYZv-00053D-KN for idr@megatron.ietf.org; Fri, 28 Jan 2005 11:02:36 -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 LAA12516 for <idr@ietf.org>; Fri, 28 Jan 2005 11:02:33 -0500 (EST)
Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CuYrH-0008QG-Mt for idr@ietf.org; Fri, 28 Jan 2005 11:20:32 -0500
Received: from ams-core-1.cisco.com (144.254.224.150) by ams-iport-1.cisco.com with ESMTP; 28 Jan 2005 17:13:22 +0100
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j0SG1YWY007757; Fri, 28 Jan 2005 17:02:00 +0100 (MET)
Received: from xmb-ams-333.cisco.com ([144.254.231.78]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.0); Fri, 28 Jan 2005 17:01:57 +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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Idr] MInutes for IDR
Date: Fri, 28 Jan 2005 17:01:52 +0100
Message-ID: <A05118C6DF9320488C77F3D5459B17B7764C4B@xmb-ams-333.emea.cisco.com>
Thread-Topic: [Idr] MInutes for IDR
Thread-Index: AcTe1M1W6rWg0MNgQM+kkJPUpeMTcwCKb+IABur4V/ACKcgaAA==
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: Susan Hares <shares@nexthop.com>, yakov@juniper.net
X-OriginalArrivalTime: 28 Jan 2005 16:01:57.0563 (UTC) FILETIME=[B1A2F0B0:01C50552]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Content-Transfer-Encoding: quoted-printable
Cc: zinin@psg.com, idr@ietf.org, "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>, Bill Fenner <fenner@research.att.com>, Pekka Savola <pekkas@netcore.fi>
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: 22bbb45ef41b733eb2d03ee71ece8243
Content-Transfer-Encoding: quoted-printable
Hello Susan and Yakov, If I am mistaken and we did not agree to issue Last Call on draft-ooms-v6ops-bgp-tunnel-04.txt, could you let me know and remind me of the reasons and what needs to be done for that to happen? If I am not mistaken and we did agree to that, could we do that Last Call? Thank you Francois >> -----Original Message----- >> From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On >> Behalf Of Francois Le Faucheur (flefauch) >> Sent: lundi 17 janvier 2005 16:39 >> To: Susan Hares >> Cc: idr@ietf.org >> Subject: RE: [Idr] MInutes for IDR >> >> Hello Susan, >> >> Did I miss the updated IDR Minutes? >> Could we go ahead with the Last Call on >> draft-ooms-v6ops-bgp-tunnel-04.txt? >> >> Thanks >> >> Francois >> >> >> -----Original Message----- >> >> From: Francois Le Faucheur (flefauch) >> >> Sent: lundi 13 décembre 2004 12:39 >> >> To: Susan Hares >> >> Cc: yakov@juniper.net; Francois Le Faucheur (flefauch); >> idr@ietf.org >> >> Subject: RE: [Idr] MInutes for IDR >> >> >> >> 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 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