From idr-bounces@ietf.org Wed Mar 01 11:45:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FEURn-0002cW-CZ; Wed, 01 Mar 2006 11:45:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FEURl-0002XF-4F
	for idr@ietf.org; Wed, 01 Mar 2006 11:45:05 -0500
Received: from pizarro.unex.es ([158.49.8.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEURj-0005lO-Go
	for idr@ietf.org; Wed, 01 Mar 2006 11:45:05 -0500
Received: from localhost (almendralejo.unex.es [158.49.8.199])
	by pizarro.unex.es (Postfix/MJ-1.08) with ESMTP id AA747D13D7
	for <idr@ietf.org>; Wed,  1 Mar 2006 17:45:02 +0100 (CET)
Received: from pizarro.unex.es ([158.49.8.2])
	by localhost (emilio [158.49.17.20]) (amavisd-new, port 10024)
	with ESMTP id 14825-03 for <idr@ietf.org>;
	Wed, 1 Mar 2006 17:45:12 +0100 (CET)
Received: from guadiana.unex.es (guadiana.unex.es [158.49.17.23])
	by pizarro.unex.es (Postfix/MJ-1.08) with ESMTP id 86047D13D2
	for <idr@ietf.org>; Wed,  1 Mar 2006 17:45:02 +0100 (CET)
Received: from [158.49.116.27] (helo=[127.0.0.1])
	by guadiana.unex.es with esmtp (Exim 3.35 #1 (Debian))
	id 1FEURh-0000X7-00
	for <idr@ietf.org>; Wed, 01 Mar 2006 17:45:01 +0100
Message-ID: <4405D19A.1050606@unex.es>
Date: Wed, 01 Mar 2006 17:53:46 +0100
From: =?ISO-8859-1?Q?Manuel_Dom=EDnguez_Dorado?= <mdomdor@unex.es>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: idr@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at unex.es
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Subject: [Idr] First post
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ingeniero@ManoloDominguez.com
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>
Errors-To: idr-bounces@ietf.org

Good morning.

I am Manuel Dom=EDnguez Dorado, from Spain. I am preparing my PH.D. at th=
e=20
University of Extremadura. My subjects of interest are the interdomain=20
routing and multiprotocol technologies. I finish subscribing in the list=20
and wished to present/display myself and to salute to every members. I=20
hope to be able to contribute something, although it is in only once.

A greeting.

--=20
--------------------------------------------------
Manuel Dom=EDnguez Dorado

G=CDTACA: Grupo de Investigaci=F3n en Ingenier=EDa
Telem=E1tica Aplicada y Comunicaciones Avanzadas

Escuela Polit=E9cnica de C=E1ceres
Universidad de Extremadura
Avda. de la Universidad S/N
10071 - C=E1ceres (C=C1CERES) - SPAIN

TLF..: 607 417 860
Web..: http://www.unex.es
Web..: http://gitaca.unex.es/manolodd
Email: mdomdor@unex.es
--------------------------------------------------


_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr



From idr-bounces@ietf.org Sat Mar 04 18:58:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FFgde-0007ZG-8q; Sat, 04 Mar 2006 18:58:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FFgdd-0007ZB-CI
	for idr@ietf.org; Sat, 04 Mar 2006 18:58:17 -0500
Received: from colo-dns-ext2.juniper.net ([207.17.137.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FFgdc-0002Hy-1T
	for idr@ietf.org; Sat, 04 Mar 2006 18:58:17 -0500
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
	k24NwF1Z014836
	for <idr@ietf.org>; Sat, 4 Mar 2006 15:58:15 -0800 (PST)
	(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 k24NwF540363
	for <idr@ietf.org>; Sat, 4 Mar 2006 15:58:15 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200603042358.k24NwF540363@merlot.juniper.net>
To: idr@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <37256.1141516695.1@juniper.net>
Date: Sat, 04 Mar 2006 15:58:15 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Subject: [Idr] 2858bis and SNPA
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>
Errors-To: idr-bounces@ietf.org

Folks,

Due to the fact that we did not get reports on at least two
(interoperable) implementations that use the SNPA field (see
attached), we have to deprecate this field, as we move the spec to
Draft Standard (keeping the SNPA field in the spec is *not* an
option). I just submitted a revised draft that reflects this. Please
look at the text to see if you have any editorial comments *related
to that change* and get back to me 3/14/2006.

Yakov.
------- Forwarded Message

Date:    Sun, 12 Feb 2006 13:18:17 -0800
From:    Yakov Rekhter <yakov@juniper.net>
To:      idr@ietf.org
Subject: [Idr] 2858bis and SNPA

Folks,

If any of you has an implementation that uses the SNPA field
of MP_REACH, please drop me an e-mail. If we would not get
at least two reports of an implementation that uses the SNPA field 
within the next two weeks we'll need to assume that this field is not used,
and therefore has to be deprecated as we move to Draft Standard.

Yakov.

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr

------- End of Forwarded Message


_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr



From idr-bounces@ietf.org Mon Mar 06 15:50:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FGMf2-0003GM-3P; Mon, 06 Mar 2006 15:50:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FGMeY-0001tT-Tp; Mon, 06 Mar 2006 15:50:02 -0500
Received: from [156.154.16.129] (helo=pine.neustar.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FGMeY-0001Lr-93; Mon, 06 Mar 2006 15:50:02 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by pine.neustar.com (8.12.8/8.12.8) with ESMTP id k26Ko1vP010451
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 6 Mar 2006 20:50:02 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FGMeX-00055N-RE; Mon, 06 Mar 2006 15:50:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1FGMeX-00055N-RE@stiedprstage1.ietf.org>
Date: Mon, 06 Mar 2006 15:50:01 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: idr@ietf.org
Subject: [Idr] I-D ACTION:draft-ietf-idr-rfc2858bis-09.txt 
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>
Errors-To: idr-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing Working Group of the IETF.

	Title		: Multiprotocol Extensions for BGP-4
	Author(s)	: T. Bates, et al.
	Filename	: draft-ietf-idr-rfc2858bis-09.txt
	Pages		: 0
	Date		: 2006-3-6
	
Currently BGP-4 is capable of carrying routing information only for
IPv4. This document defines extensions to BGP-4 to enable it to carry
routing information for multiple Network Layer protocols (e.g., IPv6,
IPX, etc...). The extensions are backward compatible - a router that
supports the extensions can interoperate with a router that doesn't
support the extensions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-rfc2858bis-09.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-idr-rfc2858bis-09.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-idr-rfc2858bis-09.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-3-6102924.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idr-rfc2858bis-09.txt

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

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


--OtherAccess--

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

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr

--NextPart--




From idr-bounces@ietf.org Tue Mar 07 12:38:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FGg8N-0001m3-Tc; Tue, 07 Mar 2006 12:38:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FGg8M-0001ly-TK
	for idr@ietf.org; Tue, 07 Mar 2006 12:38:06 -0500
Received: from manos.scc.mi.org ([204.11.140.250])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGg8L-0003XA-MO
	for idr@ietf.org; Tue, 07 Mar 2006 12:38:06 -0500
Received: by manos.scc.mi.org (Postfix, from userid 1025)
	id 0F54E4E7E3; Tue,  7 Mar 2006 12:38:05 -0500 (EST)
Date: Tue, 7 Mar 2006 12:38:05 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: Yakov Rekhter <yakov@juniper.net>
Subject: Re: [Idr] 2858bis and SNPA
Message-ID: <20060307173805.GB7806@scc.mi.org>
References: <200603042358.k24NwF540363@merlot.juniper.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200603042358.k24NwF540363@merlot.juniper.net>
User-Agent: Mutt/1.3.28i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: 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>
Errors-To: idr-bounces@ietf.org

Yakov,

On Sat, Mar 04, 2006 at 03:58:15PM -0800, Yakov Rekhter wrote:
> Due to the fact that we did not get reports on at least two
> (interoperable) implementations that use the SNPA field (see
> attached), we have to deprecate this field, as we move the spec to
> Draft Standard (keeping the SNPA field in the spec is *not* an
> option). I just submitted a revised draft that reflects this. Please
> look at the text to see if you have any editorial comments *related
> to that change* and get back to me 3/14/2006.

The text in question:
: Reserved:
: 
: A 1 octet field that SHOULD be set to 0.

Aside from the indentation issue, wouldn't a MUST be more appropriate here?

The issue is that anyone who has code that interpreted SNPAs per RFC 2858
will most certainly have issues if this is non-zero.  This is true
even if they did nothing other than parse the packet and discard them.

In addition, what should a newly compliant implementation do with this
value if non-zero?  Normally the text is "MUST be set to zero and SHOULD
be ignored upon receipt".  No similar guidance is offered here.

> Yakov.

-- Jeff

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr



From idr-bounces@ietf.org Tue Mar 07 13:18:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FGglO-0003L3-8F; Tue, 07 Mar 2006 13:18:26 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FGglM-0003Kx-Aq
	for idr@ietf.org; Tue, 07 Mar 2006 13:18:24 -0500
Received: from colo-dns-ext1.juniper.net ([207.17.137.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGglL-0005KG-0P
	for idr@ietf.org; Tue, 07 Mar 2006 13:18:24 -0500
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id k27IIMX88915; 
	Tue, 7 Mar 2006 10:18:22 -0800 (PST)
	(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 k27IIH560384;
	Tue, 7 Mar 2006 10:18:17 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200603071818.k27IIH560384@merlot.juniper.net>
To: Jeffrey Haas <jhaas@pfrc.org>
Subject: Re: [Idr] 2858bis and SNPA 
In-Reply-To: Your message of "Tue, 07 Mar 2006 12:38:05 EST."
	<20060307173805.GB7806@scc.mi.org> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <45244.1141755497.1@juniper.net>
Date: Tue, 07 Mar 2006 10:18:17 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: 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>
Errors-To: idr-bounces@ietf.org

Jeff,

> On Sat, Mar 04, 2006 at 03:58:15PM -0800, Yakov Rekhter wrote:
> > Due to the fact that we did not get reports on at least two
> > (interoperable) implementations that use the SNPA field (see
> > attached), we have to deprecate this field, as we move the spec to
> > Draft Standard (keeping the SNPA field in the spec is *not* an
> > option). I just submitted a revised draft that reflects this. Please
> > look at the text to see if you have any editorial comments *related
> > to that change* and get back to me 3/14/2006.
> 
> The text in question:
> : Reserved:
> : 
> : A 1 octet field that SHOULD be set to 0.
> 
> Aside from the indentation issue, wouldn't a MUST be more appropriate here?
> 
> The issue is that anyone who has code that interpreted SNPAs per RFC 2858
> will most certainly have issues if this is non-zero.  This is true
> even if they did nothing other than parse the packet and discard them.
> 
> In addition, what should a newly compliant implementation do with this
> value if non-zero?  Normally the text is "MUST be set to zero and SHOULD
> be ignored upon receipt".  No similar guidance is offered here.

Unless there are strong objections, I'll modify the draft to reflect
your point above - "MUST be set to zero, and SHOULD be ignored upon receipt".

Yakov.

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr



From idr-bounces@ietf.org Tue Mar 07 13:27:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FGguY-0002CP-Rs; Tue, 07 Mar 2006 13:27:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FGguX-0002Bp-CJ; Tue, 07 Mar 2006 13:27:53 -0500
Received: from colo-dns-ext2.juniper.net ([207.17.137.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FGguU-0005hZ-Vn; Tue, 07 Mar 2006 13:27:53 -0500
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
	k27IRo1Z062086; Tue, 7 Mar 2006 10:27:50 -0800 (PST)
	(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 k27IRo562390;
	Tue, 7 Mar 2006 10:27:50 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200603071827.k27IRo562390@merlot.juniper.net>
To: Bill Fenner <fenner@research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <46084.1141756069.1@juniper.net>
Date: Tue, 07 Mar 2006 10:27:50 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Cc: idr@ietf.org, iesg-secretary@ietf.org
Subject: [Idr] writeup for draft-ooms-v6ops-bgp-tunnel-06.txt
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>
Errors-To: idr-bounces@ietf.org

Bill,

Attached is my writeup for draft-ooms-v6ops-bgp-tunnel-06.txt.

Yakov.
- -----------------------------------------------------------------
1. Have the chairs personally reviewed this version of the Internet
Draft (ID), and in particular, do they believe this ID is ready to
forward to the IESG for publication?

Yes, the chair believes that this ID is ready for publication.

2. Has the document had adequate review from both key WG members
and key non-WG members? Do you have any concerns about the depth
or breadth of the reviews that have been performed?

This document passed the IDR WG Last Call, although we received no
comments on the document during the Last Call.

I am not aware whether it was reviewed by the v6ops WG. If the
document has not been reviewed by the v6ops WG, then it may be
useful to arrange such a review.

3. Do you have concerns that the document needs more review from a
particular (broader) perspective (e.g., security, operational
complexity, someone familiar with AAA, etc.)?

No, other than review from the v6ops WG.

4. Do you have any specific concerns/issues with this document that
you believe the ADs and/or IESG should be aware of? For example,
perhaps you are uncomfortable with certain parts of the document,
or have concerns whether there really is a need for it. In any
event, if your issues have been discussed in the WG and the WG has
indicated it that it still wishes to advance the document, detail
those concerns in the write-up.

I have no concerns with this document.

5. How solid is the WG consensus behind this document? Does it
represent the strong concurrence of a few individuals, with others
being silent, or does the WG as a whole understand and agree with
it?

There were no objections to this document within the IDR WG during
the IDR WG Last Call.

6. Has anyone threatened an appeal or otherwise indicated extreme
discontent? If so, please summarise the areas of conflict in separate
email to the Responsible Area Director.

No threat of an appeal.

7. Have the chairs verified that the document adheres to all of the 
ID Checklist items ? 

Yes.

8. Is the document split into normative and informative references?
Are there normative references to IDs, where the IDs are not also
ready for advancement or are otherwise in an unclear state? (note
here that the RFC editor will not publish an RFC with normative
references to IDs, it will delay publication until all such IDs are
also ready for publication as RFCs.)

The document is split into normative and informative references.
There are no normative references to IDs.

9. What is the intended status of the document? (e.g., Proposed Standard, 
Informational?) 

Proposed Standard.

10.  For Standards Track and BCP documents, the IESG approval announcement 
includes a write-up section with the following sections: 

Technical Summary 

This document explains how to interconnect IPv6 islands over a
Multi-Protocol Label Switching (MPLS)-enabled IPv4 cloud. This
approach relies on IPv6 Provider Edge routers (6PE) which are Dual
Stack in order to connect to IPv6 islands and to the MPLS core which
is only required to run IPv4 MPLS. The 6PE routers exchange the IPv6
reachability information transparently over the core using the
Multi-Protocol Border Gateway Protocol (MP-BGP) over IPv4. In doing
so, the BGP Next Hop field is used to convey the IPv4 address of the
6PE router so that dynamically established IPv4-signaled MPLS Label
Switched Paths (LSPs) can be used without explicit tunnel
configuration.

Working Group Summary 

This is an individual submission. There has been no comments on 
the document during the Last Call.

Protocol Quality 

While this is an individual submission, there are multiple
implementations of this specification. Specifically there are two
implementations by the router vendors, and three implementations
by the network test equipment vendors. The full implementation
report is available (see draft-levy-idr-6pe-survey-00.txt).

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr



From idr-bounces@ietf.org Wed Mar 08 10:43:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FH0oL-0006Cp-JA; Wed, 08 Mar 2006 10:42:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FH0oK-0006AK-0h
	for idr@ietf.org; Wed, 08 Mar 2006 10:42:48 -0500
Received: from mail-red.research.att.com ([192.20.225.110]
	helo=mail-white.research.att.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FH0oI-0005sI-Rg
	for idr@ietf.org; Wed, 08 Mar 2006 10:42:47 -0500
Received: from bright.research.att.com (bright.research.att.com
	[135.207.20.189])
	by mail-blue.research.att.com (Postfix) with ESMTP id C863A147E4C;
	Wed,  8 Mar 2006 10:42:45 -0500 (EST)
Received: (from fenner@localhost)
	by bright.research.att.com (8.12.11/8.12.10/Submit) id k28Fgj3k016811; 
	Wed, 8 Mar 2006 07:42:45 -0800
From: Bill Fenner <fenner@research.att.com>
Message-Id: <200603081542.k28Fgj3k016811@bright.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: Yakov Rekhter <yakov@juniper.net>
Date: Wed, 8 Mar 2006 07:42:45 -0800
Versions: dmail (linux) 2.7/makemail 2.14
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Cc: idr@ietf.org
Subject: [Idr] Re: writeup for draft-ooms-v6ops-bgp-tunnel-06.txt
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>
Errors-To: idr-bounces@ietf.org


Thanks, Yakov.  I'll check with David regarding v6ops and then
advance this.

  Bill


_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr



From idr-bounces@ietf.org Fri Mar 10 02:56:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FHcU9-0006pt-5W; Fri, 10 Mar 2006 02:56:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FHcU5-0006ms-L9; Fri, 10 Mar 2006 02:56:25 -0500
Received: from oak.neustar.com ([209.173.53.70])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FHcNu-0004WZ-0g; Fri, 10 Mar 2006 02:50:05 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k2A7o1BX028828
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 10 Mar 2006 07:50:01 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FHcNt-0001xc-QI; Fri, 10 Mar 2006 02:50:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1FHcNt-0001xc-QI@stiedprstage1.ietf.org>
Date: Fri, 10 Mar 2006 02:50:01 -0500
X-Spam-Score: 0.3 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: idr@ietf.org
Subject: [Idr] I-D ACTION:draft-ietf-idr-as-pathlimit-01.txt 
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>
Errors-To: idr-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing Working Group of the IETF.

	Title		: The AS_PATHLIMIT Path Attribute
	Author(s)	: T. Li, et al.
	Filename	: draft-ietf-idr-as-pathlimit-01.txt
	Pages		: 15
	Date		: 2006-3-9
	
This document describes the 'AS path limit' (AS_PATHLIMIT) path
   attribute for BGP.  This is an optional, transitive path attribute
   that is designed to help limit the distribution of routing
   information in the Internet.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-as-pathlimit-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-ietf-idr-as-pathlimit-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-ietf-idr-as-pathlimit-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.

--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-3-9191850.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idr-as-pathlimit-01.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-idr-as-pathlimit-01.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

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

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr

--NextPart--




From idr-bounces@ietf.org Fri Mar 10 15:50:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FHoYm-00034w-9v; Fri, 10 Mar 2006 15:50:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FHoYk-00033C-58; Fri, 10 Mar 2006 15:50:02 -0500
Received: from oak.neustar.com ([209.173.53.70])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FHoYj-0003R5-Rk; Fri, 10 Mar 2006 15:50:02 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k2AKo1BX008259
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 10 Mar 2006 20:50:01 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FHoYj-0006ow-MN; Fri, 10 Mar 2006 15:50:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1FHoYj-0006ow-MN@stiedprstage1.ietf.org>
Date: Fri, 10 Mar 2006 15:50:01 -0500
X-Spam-Score: 0.3 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: idr@ietf.org
Subject: [Idr] I-D ACTION:draft-ietf-idr-bgp-multisession-02.txt 
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>
Errors-To: idr-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing Working Group of the IETF.

	Title		: Multisession BGP
	Author(s)	: J. Scudder, C. Appanna
	Filename	: draft-ietf-idr-bgp-multisession-02.txt
	Pages		: 14
	Date		: 2006-3-10
	
This specification augments "Multiprotocol Extensions for BGP-4" [MP-
BGP] by proposing a mechanism to allow multiple sessions to be used
between a given pair of BGP speakers.  Each session is used to
transport routes for one or more AFI/SAFI.  This provides an
alternative to the current [MP-BGP] approach of multiplexing routes
for all AFI/SAFI onto a single connection.

Use of this approach is expected to increase the robustness of the
BGP protocol as it is used to support more and more diverse AFI/SAFI.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp-multisession-02.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-idr-bgp-multisession-02.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-idr-bgp-multisession-02.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-3-10100654.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idr-bgp-multisession-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-idr-bgp-multisession-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

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

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr

--NextPart--





From idr-bounces@ietf.org Fri Mar 10 15:50:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FHoYq-0003BR-HT; Fri, 10 Mar 2006 15:50:08 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FHoYk-00033P-Ao; Fri, 10 Mar 2006 15:50:02 -0500
Received: from willow.neustar.com ([209.173.53.84])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FHoYj-0003R7-Ue; Fri, 10 Mar 2006 15:50:02 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k2AKo19W021582
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 10 Mar 2006 20:50:01 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FHoYj-0006pB-OL; Fri, 10 Mar 2006 15:50:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1FHoYj-0006pB-OL@stiedprstage1.ietf.org>
Date: Fri, 10 Mar 2006 15:50:01 -0500
X-Spam-Score: 0.3 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: idr@ietf.org
Subject: [Idr] I-D ACTION:draft-ietf-idr-route-filter-13.txt 
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>
Errors-To: idr-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing Working Group of the IETF.

	Title		: Cooperative Route Filtering Capability for BGP-4
	Author(s)	: E. Chen, Y. Rekhter
	Filename	: draft-ietf-idr-route-filter-13.txt
	Pages		: 0
	Date		: 2006-3-10
	
This document defines a BGP-based mechanism that allows a BGP speaker
to send to its BGP peer a set of route filters that the peer would
use to constrain/filter its outbound routing updates to the speaker.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-route-filter-13.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-idr-route-filter-13.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-idr-route-filter-13.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-3-10102121.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idr-route-filter-13.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-idr-route-filter-13.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

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

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr

--NextPart--





From idr-bounces@ietf.org Tue Mar 14 05:14:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FJ6XP-0006Ex-F5; Tue, 14 Mar 2006 05:13:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FJ6XO-0006Dk-7m
	for idr@ietf.org; Tue, 14 Mar 2006 05:13:58 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FJ6XM-0004SW-NL
	for idr@ietf.org; Tue, 14 Mar 2006 05:13:58 -0500
Received: from ams-core-1.cisco.com ([144.254.224.150])
	by ams-iport-1.cisco.com with ESMTP; 14 Mar 2006 11:13:56 +0100
Received: from xbh-ams-331.emea.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 k2EADs36029411; 
	Tue, 14 Mar 2006 11:13:54 +0100 (MET)
Received: from xmb-ams-333.cisco.com ([144.254.231.78]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.0); 
	Tue, 14 Mar 2006 11:13:54 +0100
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
Date: Tue, 14 Mar 2006 11:13:53 +0100
Message-ID: <A05118C6DF9320488C77F3D5459B17B7028335F7@xmb-ams-333.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ooms-v6ops-bgp-tunnel-06.txt and v6ops review
Thread-Index: AcZDlM/bLSA1VmX/QJOfSkXV5TyengDua1mA
From: "Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com>
To: <dheeraj.singh@wipro.com>
X-OriginalArrivalTime: 14 Mar 2006 10:13:54.0494 (UTC)
	FILETIME=[FFB8FDE0:01C6474F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: jeremy.de_clercq@alcatel.be, idr@ietf.org, dirk@onesparrow.com,
	stuart.prevost@bt.com,
	"Eric Levy- Abegnoli \(elevyabe\)" <elevyabe@cisco.com>, v6ops@ops.ietf.org
Subject: [Idr] RE: draft-ooms-v6ops-bgp-tunnel-06.txt and v6ops review
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>
Errors-To: idr-bounces@ietf.org

Hello Dheeraj,

It seems that Eric's message didn't make it on the alias, so I am
including it below.

As pointed out by Eric, IPv4 packets from the CE can be handled by the
PE as per existing IPv4 MPLS procedures. This doesn't interact in any
way with the handling of IPv6 packets as described in the 6PE document.

Can you confirm you are comfortable with this approach (or identify any
remaining concerns)?

Thanks

Francois

>> -----Original Message-----
>> From: Eric Levy- Abegnoli (elevyabe)=20
>> Sent: jeudi 9 mars 2006 17:16
>> To: dheeraj.singh@wipro.com
>> Cc: idr@ietf.org; dirk@onesparrow.com; Francois Le Faucheur=20
>> (flefauch); jeremy.de_clercq@alcatel.be;=20
>> stuart.prevost@bt.com; v6ops@ops.ietf.org
>> Subject: Re: draft-ooms-v6ops-bgp-tunnel-06.txt and v6ops review
>>=20
>> On jeudi 9 Mars 2006 06:43, dheeraj.singh@wipro.com wrote:
>> > Hi,
>> >
>> > Just consider the scenario in which the CE also supports=20
>> the IPv4.  Then
>> > how the IPv4 MPLS cloud will cater this specific IPv4 packet.
>>
>> What about it ? I don't see anything in the draft that will=20
>> prevent such=20
>> packet to be handled "as usual" by the PE and the MPLS cloud.
>> Eric
>> >
>> > BR,
>> > Dheeraj
>> >
>> >
>> > ________________________________
>> >
>> > From: owner-v6ops@ops.ietf.org on behalf of Fred Baker
>> > Sent: Thu 3/9/2006 5:46 AM
>> > To: v6ops@ops.ietf.org
>> > Subject: draft-ooms-v6ops-bgp-tunnel-06.txt and v6ops review
>> >
>> >
>> >
>> > We have been asked to read and comment on
>> >
>> >    http://www.ietf.org/internet-drafts/draft-ooms-v6ops-bgp-
>> > tunnel-06.txt
>> >    "Connecting IPv6 Islands over IPv4 MPLS using IPv6 Provider Edge
>> > Routers
>> >    (6PE)", Jeremy De Clercq, 18-Jan-06, <draft-ooms-v6ops-bgp-
>> > tunnel-06.txt>
>> >
>> > which is about to go into IESG review. As you will recall, this has
>> > been round the block, and deserves speedy review. May I=20
>> suggest that
>> > you get your comments in by 17 March at the latest. Reply to the
>> > authors copying idr; if you are not on the list, the working group
>> > chairs will deal with the moderation issues.
>>=20

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr



From idr-bounces@ietf.org Tue Mar 14 17:41:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FJICE-0005O0-Su; Tue, 14 Mar 2006 17:40:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FJICD-0005Nv-36
	for idr@ietf.org; Tue, 14 Mar 2006 17:40:53 -0500
Received: from pop-savannah.atl.sa.earthlink.net ([207.69.195.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FJICB-0008HZ-Sw
	for idr@ietf.org; Tue, 14 Mar 2006 17:40:53 -0500
Received: from user-2ivf91m.dsl.mindspring.com ([165.247.164.54]
	helo=JMHLap3.stevecrocker.com)
	by pop-savannah.atl.sa.earthlink.net with esmtp (Exim 3.36 #10)
	id 1FJICA-00072C-00 for idr@ietf.org; Tue, 14 Mar 2006 17:40:51 -0500
Message-Id: <7.0.1.0.0.20060314173409.03288648@stevecrocker.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Tue, 14 Mar 2006 17:40:48 -0500
To: idr@ietf.org
From: "Joel M. Halpern" <joel@stevecrocker.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Subject: [Idr] Hop-limit: Hop calculation
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>
Errors-To: idr-bounces@ietf.org

While reading the hop limit draft, I noticed that it says that if an 
AS Path has an AS Set (or more than one) that each element of the set 
should be counted individually.
For purposes of breaking ties across advertisements, the BGP spec 
says that one compares the length of the AS path.  The counting 
algorithm states that an AS Set is to be counted as one element for 
this purpose.

It does not seem helpful to have two different definitions for the 
length of an AS path that give different answers in some cases.

While I understand that the current choice in the hop-limit draft was 
made to reflect a meaningful case (someone along the way simply 
collapsed the elements), I believe that it can be argued that the 
existing counting is just as applicable.  And has the advantage of consistency.

Yours,
Joel M. Halpern

PS: There are some other minor reasons for suggesting this, relating 
to ways one might bend BGP.  Some of those are even why I thought of 
the question.  But I believe the above consistency is the significant issue.


_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr



From idr-bounces@ietf.org Tue Mar 14 21:56:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FJMBn-00009G-3c; Tue, 14 Mar 2006 21:56:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FJMBm-00009B-7R
	for idr@ietf.org; Tue, 14 Mar 2006 21:56:42 -0500
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 1FJLbR-0006Pz-Ok
	for idr@ietf.org; Tue, 14 Mar 2006 21:19:09 -0500
Received: from hibernia.jakma.org ([212.17.55.49])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FJLPW-0004ya-Ua
	for idr@ietf.org; Tue, 14 Mar 2006 21:07:03 -0500
Received: from sheen.jakma.org
	(IDENT:U2FsdGVkX19mpoj73D9R729ul4AQUNjUj8wiPoX2qek@sheen.jakma.org
	[212.17.55.53])
	by hibernia.jakma.org (8.13.1/8.13.1) with ESMTP id k2F263Wu031745;
	Wed, 15 Mar 2006 02:06:16 GMT
Date: Wed, 15 Mar 2006 02:06:03 +0000 (GMT)
From: Paul Jakma <paul@clubi.ie>
X-X-Sender: paul@sheen.jakma.org
To: "Joel M. Halpern" <joel@stevecrocker.com>
Subject: Re: [Idr] Hop-limit: Hop calculation
In-Reply-To: <7.0.1.0.0.20060314173409.03288648@stevecrocker.com>
Message-ID: <Pine.LNX.4.64.0603150205460.5276@sheen.jakma.org>
References: <7.0.1.0.0.20060314173409.03288648@stevecrocker.com>
Mail-Copies-To: paul@hibernia.jakma.org
X-NSA: al aqsar fluffy jihad cute musharef kittens jet-A1 ear avgas wax
	ammonium bad qran dog inshallah allah al-akbar martyr iraq
	hammas hisballah rabin ayatollah korea revolt pelvix mustard
	gas x-ray british airways washington peroxide cool
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: ClamAV version 0.88,
	clamav-milter version 0.87 on hibernia.jakma.org
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: 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>
Errors-To: idr-bounces@ietf.org

On Tue, 14 Mar 2006, Joel M. Halpern wrote:

> It does not seem helpful to have two different definitions for the 
> length of an AS path that give different answers in some cases.

I think the standalone decrementing TTL was nicer.

regards,
-- 
Paul Jakma	paul@clubi.ie	paul@jakma.org	Key ID: 64A2FF6A
Fortune:
We are all born mad.  Some remain so.
 		-- Samuel Beckett

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr



From idr-bounces@ietf.org Wed Mar 15 12:47:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FJa5J-0007D7-HY; Wed, 15 Mar 2006 12:46:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FJa5I-0007D2-FH
	for idr@ietf.org; Wed, 15 Mar 2006 12:46:56 -0500
Received: from iceblock01.troposnetworks.com ([12.108.168.187]
	helo=iceblock01.tropos.com) by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1FJa5H-0000tB-4O for idr@ietf.org; Wed, 15 Mar 2006 12:46:56 -0500
Received: (qmail 11263 invoked from network); 15 Mar 2006 17:44:48 -0000
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on iceblock01
X-Spam-Level: 
X-Spam-Status: No, score=-104.4 required=6.0 tests=ALL_TRUSTED,AWL,BAYES_00,
	USER_IN_WHITELIST autolearn=ham version=3.1.0
Received: from ca-bay-exch-01.tropos.com (192.168.1.49)
	by iceblock01.tropos.com with SMTP; 15 Mar 2006 17:44:47 -0000
Received: from LIPC ([192.168.1.164]) by ca-bay-exch-01.tropos.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 15 Mar 2006 09:45:30 -0800
From: "Tony Li" <tli@tropos.com>
To: "'Joel M. Halpern'" <joel@stevecrocker.com>,
	<idr@ietf.org>
Subject: RE: [Idr] Hop-limit: Hop calculation
Date: Wed, 15 Mar 2006 09:44:46 -0800
Message-ID: <009701c64858$26c56370$a401a8c0@tropos.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <7.0.1.0.0.20060314173409.03288648@stevecrocker.com>
Thread-Index: AcZHuGiIbud0jOXsSgePt7/hzuUXwwAn6MBg
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
X-OriginalArrivalTime: 15 Mar 2006 17:45:30.0426 (UTC)
	FILETIME=[4091D9A0:01C64858]
X-Antivirus: Scanned by Tropos Antivirus 1.0.4
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: 
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: tony.li@tony.li
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>
Errors-To: idr-bounces@ietf.org


Joel,
 
> While I understand that the current choice in the hop-limit draft was 
> made to reflect a meaningful case (someone along the way simply 
> collapsed the elements), I believe that it can be argued that the 
> existing counting is just as applicable.  And has the 
> advantage of consistency.

I don't have a big problem with this.  Do other folks have opinions?

Tony



_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr



From idr-bounces@ietf.org Wed Mar 15 13:24:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FJafH-00065c-L1; Wed, 15 Mar 2006 13:24:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FJafG-000633-8V
	for idr@ietf.org; Wed, 15 Mar 2006 13:24:06 -0500
Received: from paintbird.ucs.indiana.edu ([129.79.5.54])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FJafF-0002Oe-0t
	for idr@ietf.org; Wed, 15 Mar 2006 13:24:06 -0500
Received: from [129.79.9.198] (129-79-9-198.dhcp-bl.indiana.edu [129.79.9.198])
	(authenticated bits=0)
	by paintbird.ucs.indiana.edu (8.12.11/8.12.11) with ESMTP id
	k2FIO3tc017868
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <idr@ietf.org>; Wed, 15 Mar 2006 13:24:04 -0500
Message-ID: <44185BC2.3050400@grnoc.iu.edu>
Date: Wed, 15 Mar 2006 13:24:02 -0500
From: Andrew Lee <leea@grnoc.iu.edu>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
CC: idr@ietf.org
Subject: Re: [Idr] Hop-limit: Hop calculation
References: <009701c64858$26c56370$a401a8c0@tropos.com>
In-Reply-To: <009701c64858$26c56370$a401a8c0@tropos.com>
X-Enigmail-Version: 0.89.6.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
	milter-greylist-2.0.2 (paintbird.ucs.indiana.edu [129.79.5.54]);
	Wed, 15 Mar 2006 13:24:04 -0500 (EST)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
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>
Errors-To: idr-bounces@ietf.org


Tony Li wrote:
> Joel,
>  
> 
>>While I understand that the current choice in the hop-limit draft was 
>>made to reflect a meaningful case (someone along the way simply 
>>collapsed the elements), I believe that it can be argued that the 
>>existing counting is just as applicable.  And has the 
>>advantage of consistency.
> 
> 
> I don't have a big problem with this.  Do other folks have opinions?
> 
> Tony
>


It seems like it would be more correct to count a set as 1 element.  For 
example, if A B and C peer with D and D announces an aggregate to E with a path 
like D {A B C}, the distance from E to any of the set is still 2.

Andrew


_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr



From idr-bounces@ietf.org Wed Mar 22 12:28:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FM788-0006EP-Nh; Wed, 22 Mar 2006 12:28:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FM787-00069h-47
	for idr@ietf.org; Wed, 22 Mar 2006 12:28:19 -0500
Received: from manos.scc.mi.org ([204.11.140.250])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FM785-0000e8-Tw
	for idr@ietf.org; Wed, 22 Mar 2006 12:28:19 -0500
Received: by manos.scc.mi.org (Postfix, from userid 1025)
	id 4795B4E7E0; Wed, 22 Mar 2006 12:28:17 -0500 (EST)
Date: Wed, 22 Mar 2006 12:28:17 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: idr@ietf.org
Subject: Re: [Idr] Hop-limit: Hop calculation
Message-ID: <20060322172817.GA27867@scc.mi.org>
References: <7.0.1.0.0.20060314173409.03288648@stevecrocker.com>
	<009701c64858$26c56370$a401a8c0@tropos.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <009701c64858$26c56370$a401a8c0@tropos.com>
User-Agent: Mutt/1.3.28i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
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>
Errors-To: idr-bounces@ietf.org

On Wed, Mar 15, 2006 at 09:44:46AM -0800, Tony Li wrote:
> Joel,
> > While I understand that the current choice in the hop-limit draft was 
> > made to reflect a meaningful case (someone along the way simply 
> > collapsed the elements), I believe that it can be argued that the 
> > existing counting is just as applicable.  And has the 
> > advantage of consistency.
> 
> I don't have a big problem with this.  Do other folks have opinions?

I think I had made a similar comment earlier.  I'm in support of this.

Other comments on the draft:

I'll note once again that the ATOMIC_AGGREGATE behavior in this document
(-01) is inconsistent with the way people actually do things.  This issue
will most certainly be raised during last-call.

I would suggest adding a sentence regarding aggregation saying that this
attribute must not be added to the aggregate, or allowing it to be
added to the aggregate iff all contributing routes have the same
path limit attribute.

:   When a BGP speaker propagates a route with an associated AS_PATHLIMIT
:   attribute, which it has learned from another BGP speaker's UPDATE
:   message, it MUST NOT modify the route's AS_PATHLIMIT attribute.

While I tend to agree with this, I doubt it'll survive implementation. :-)

-- Jeff

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr



From idr-bounces@ietf.org Thu Mar 23 14:37:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FMVc8-00087k-1B; Thu, 23 Mar 2006 14:36:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FMVXU-0005od-S6
	for idr@ietf.org; Thu, 23 Mar 2006 14:32:08 -0500
Received: from paintbird.ucs.indiana.edu ([129.79.5.54])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMVTz-0000zA-8Z
	for idr@ietf.org; Thu, 23 Mar 2006 14:28:32 -0500
Received: from [156.56.175.4] (iub-vpn-175-4.noc.indiana.edu [156.56.175.4])
	(authenticated bits=0)
	by paintbird.ucs.indiana.edu (8.12.11.20060308/8.12.11) with ESMTP id
	k2NJSTsD003797
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <idr@ietf.org>; Thu, 23 Mar 2006 14:28:30 -0500
Message-ID: <4422F6DC.5030209@grnoc.iu.edu>
Date: Thu, 23 Mar 2006 13:28:28 -0600
From: Andrew Lee <leea@grnoc.iu.edu>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: idr@ietf.org
X-Enigmail-Version: 0.89.6.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
	milter-greylist-2.0.2 (paintbird.ucs.indiana.edu [129.79.5.54]);
	Thu, 23 Mar 2006 14:28:30 -0500 (EST)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Subject: [Idr] IETF 65 wg minutes
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>
Errors-To: idr-bounces@ietf.org

Please let me know if there are any corrections or additions.

Thanks
Andrew

--

IDR Working Group minutes
IETF 65
Wednesday March 22 2006
0900-1130

Scribe drafting

Document Status report

draft-levy-idr-6pe-survey-00.txt
6PE Implementation Report - Francois Le Faucheur
  Cisco and Juniper implementations
   basic tests show they are interoperable
   Cisco - arbitrary label
   Juniper - explicit NULL label
  next step:
    let implementation report expire
    move 6PE toward RFC status

Acee Lindem: Why not publish implementation report as informational?
  A: The expired draft will be archived on the IETF and still serve
     as a reference

--

draft-bhatia-bgp-multiple-next-hops-00.txt
Advertising Multiple Nexthop Routes in BGP - Joel Halpern
  Advertising Multiple NextHops Routes in BGP
  base mechanism
   need to add extra info to withdraw so you know which you are removing
  ecmp case
   seperated into different draft now
   advertise multiple paths to be used to multipath capable peers
  ebgp case
   compress as path
    possible algorithm in draft, others acceptable if the length and
    info is preserved

Dino Farinacci: Requested clarification about aspath and method of encoding
  A: We need to preserve all the ASs that appeared, as well as length
     We would like to preserve structure, but maybe thats not essential
     ECMP, by definition, must have equal as paths

Christina Radulescu-banu: How do i encode MPLS information
  A: If using bgp to carry MPLS labels, and doing multipath,
     yes the label can be next hop in the case where as path is different.
     But if you have multiple next hop with same AS path,
     you cannot right now due to proposed update packet structure.
     We can revisit this with wg, and maybe add to draft.

---

draft-zhang-idr-bgp-entire-routes-reflect-02
Entire Routes Reflecting capability - Zhang Renhai
  new capability to be negotiated between RR and client
  RR can send multiple routes to client
  no new attribute, send seperate update for each route
  process changes
   implicit withdraw
    prefix and next hop are same as existing route
   explicit withdraw
    next hop information must be provided
  update packet change
   add next_hop to packet
  other address family -  MP_UNREACH_NLRI attribute
   add next hop info (length + network address)
  how to deal with change of next hop
  multiple multiple path proposals
   all still in develepoment
  next:
   cover more applications
    rebuild draft?

Matt Meyer: With regard to other applications, there is a lack of information
             in netflow that can lead to incorrect information
  A: ingress traffic, but outbound policy doesnt match netflow will mislead
     could be gotten around by having nonbest learned routes reflected to
     netflow device

Presentations will be posted to IETF web site


_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr



From idr-bounces@ietf.org Thu Mar 23 15:49:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FMWjt-0001FL-Ic; Thu, 23 Mar 2006 15:49:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FMWjs-0001FF-Ga
	for idr@ietf.org; Thu, 23 Mar 2006 15:49:00 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMWjr-0004vB-8o
	for idr@ietf.org; Thu, 23 Mar 2006 15:49:00 -0500
Received: from rtp-core-2.cisco.com ([64.102.124.13])
	by rtp-iport-2.cisco.com with ESMTP; 23 Mar 2006 15:48:59 -0500
X-IronPort-AV: i="4.03,123,1141621200"; 
	d="scan'208"; a="84837757:sNHT30709192"
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k2NKmwVU017087; 
	Thu, 23 Mar 2006 15:48:58 -0500 (EST)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Thu, 23 Mar 2006 15:48:58 -0500
Received: from [192.168.1.100] ([10.82.241.129]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 23 Mar 2006 15:48:58 -0500
In-Reply-To: <4422F6DC.5030209@grnoc.iu.edu>
References: <4422F6DC.5030209@grnoc.iu.edu>
Mime-Version: 1.0 (Apple Message framework v623)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <95b4bd0e7ab2ef3b7614a7d061ccbce1@cisco.com>
Content-Transfer-Encoding: 7bit
From: Dana Blair <dblair@cisco.com>
Subject: Re: [Idr] IETF 65 wg minutes
Date: Thu, 23 Mar 2006 15:48:57 -0500
To: Andrew Lee <leea@grnoc.iu.edu>
X-Mailer: Apple Mail (2.623)
X-OriginalArrivalTime: 23 Mar 2006 20:48:58.0460 (UTC)
	FILETIME=[352C89C0:01C64EBB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: 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>
Errors-To: idr-bounces@ietf.org


> draft-zhang-idr-bgp-entire-routes-reflect-02
> Entire Routes Reflecting capability - Zhang Renhai
>  new capability to be negotiated between RR and client
>  RR can send multiple routes to client
>  no new attribute, send seperate update for each route
>  process changes
>   implicit withdraw
>    prefix and next hop are same as existing route
>   explicit withdraw
>    next hop information must be provided
>  update packet change
>   add next_hop to packet
>  other address family -  MP_UNREACH_NLRI attribute
>   add next hop info (length + network address)
>  how to deal with change of next hop
>  multiple multiple path proposals
>   all still in develepoment
>  next:
>   cover more applications
>    rebuild draft?
>
> Matt Meyer: With regard to other applications, there is a lack of 
> information
>             in netflow that can lead to incorrect information
>  A: ingress traffic, but outbound policy doesnt match netflow will 
> mislead
>     could be gotten around by having nonbest learned routes reflected 
> to
>     netflow device
>

Can someone provide more detail on this discussion ?  I'm trying to 
understand
how netflow is related to the draft.

thanks,
Dana

> Presentations will be posted to IETF web site
>
>
> _______________________________________________
> 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



From idr-bounces@ietf.org Thu Mar 23 22:13:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FMck2-0005Bh-C0; Thu, 23 Mar 2006 22:13:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FMck0-0005Bb-N2
	for idr@ietf.org; Thu, 23 Mar 2006 22:13:32 -0500
Received: from usaga01-in.huawei.com ([12.129.211.51])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMcjz-0000Kd-CM
	for idr@ietf.org; Thu, 23 Mar 2006 22:13:32 -0500
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IWM005KB3H7LM@usaga01-in.huawei.com> for
	idr@ietf.org; Thu, 23 Mar 2006 19:10:19 -0800 (PST)
Received: from huawei.com ([172.17.1.101])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IWM002ED3GX96@usaga01-in.huawei.com> for
	idr@ietf.org; Thu, 23 Mar 2006 19:10:19 -0800 (PST)
Received: from [172.24.1.3] (Forwarded-For: [130.129.128.232])
	by szxmc01-in.huawei.com (mshttpd); Fri, 24 Mar 2006 11:13:21 +0800
Date: Fri, 24 Mar 2006 11:13:21 +0800
From: zhangrenhai 18605 <zhangrenhai@huawei.com>
Subject: Re: [Idr] IETF 65 wg minutes
To: Andrew Lee <leea@grnoc.iu.edu>
Message-id: <a4967a5f66.a5f66a4967@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.25 (built Mar  3 2004)
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: en
Priority: normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Cc: 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>
Errors-To: idr-bounces@ietf.org

Hi,

Good job.

Hi, Matt Meyer,I am appreciate your advise, if you like, contact me, 
I'd like to discuss more about the applications, 
anyone else are also welcome. 

Thanks,

Zhang Renhai

----- Original Message -----
From: Andrew Lee <leea@grnoc.iu.edu>
Date: Friday, March 24, 2006 3:28 am
Subject: [Idr] IETF 65 wg minutes

> Please let me know if there are any corrections or additions.
> 
> Thanks
> Andrew
> 
> --
> 
> IDR Working Group minutes
> IETF 65
> Wednesday March 22 2006
> 0900-1130
> 
> Scribe drafting
> 
> Document Status report
> 
> draft-levy-idr-6pe-survey-00.txt
> 6PE Implementation Report - Francois Le Faucheur
>  Cisco and Juniper implementations
>   basic tests show they are interoperable
>   Cisco - arbitrary label
>   Juniper - explicit NULL label
>  next step:
>    let implementation report expire
>    move 6PE toward RFC status
> 
> Acee Lindem: Why not publish implementation report as informational?
>  A: The expired draft will be archived on the IETF and still serve
>     as a reference
> 
> --
> 
> draft-bhatia-bgp-multiple-next-hops-00.txt
> Advertising Multiple Nexthop Routes in BGP - Joel Halpern
>  Advertising Multiple NextHops Routes in BGP
>  base mechanism
>   need to add extra info to withdraw so you know which you are 
> removing  ecmp case
>   seperated into different draft now
>   advertise multiple paths to be used to multipath capable peers
>  ebgp case
>   compress as path
>    possible algorithm in draft, others acceptable if the length and
>    info is preserved
> 
> Dino Farinacci: Requested clarification about aspath and method of 
> encoding  A: We need to preserve all the ASs that appeared, as 
> well as length
>     We would like to preserve structure, but maybe thats not 
> essential     ECMP, by definition, must have equal as paths
> 
> Christina Radulescu-banu: How do i encode MPLS information
>  A: If using bgp to carry MPLS labels, and doing multipath,
>     yes the label can be next hop in the case where as path is 
> different.     But if you have multiple next hop with same AS path,
>     you cannot right now due to proposed update packet structure.
>     We can revisit this with wg, and maybe add to draft.
> 
> ---
> 
> draft-zhang-idr-bgp-entire-routes-reflect-02
> Entire Routes Reflecting capability - Zhang Renhai
>  new capability to be negotiated between RR and client
>  RR can send multiple routes to client
>  no new attribute, send seperate update for each route
>  process changes
>   implicit withdraw
>    prefix and next hop are same as existing route
>   explicit withdraw
>    next hop information must be provided
>  update packet change
>   add next_hop to packet
>  other address family -  MP_UNREACH_NLRI attribute
>   add next hop info (length + network address)
>  how to deal with change of next hop
>  multiple multiple path proposals
>   all still in develepoment
>  next:
>   cover more applications
>    rebuild draft?
> 
> Matt Meyer: With regard to other applications, there is a lack of 
> information             in netflow that can lead to incorrect 
> information  A: ingress traffic, but outbound policy doesnt match 
> netflow will mislead
>     could be gotten around by having nonbest learned routes 
> reflected to
>     netflow device
> 
> Presentations will be posted to IETF web site
> 
> 
> _______________________________________________
> 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



From idr-bounces@ietf.org Fri Mar 24 18:50:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FMw2g-0000AD-Qo; Fri, 24 Mar 2006 18:50:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FMw2d-00009i-Ix; Fri, 24 Mar 2006 18:50:03 -0500
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=cypress.neustar.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FMw2c-0000bq-6s; Fri, 24 Mar 2006 18:50:03 -0500
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 k2ONo10e029219
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 24 Mar 2006 23:50:01 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FMw2b-000763-Ix; Fri, 24 Mar 2006 18:50:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1FMw2b-000763-Ix@stiedprstage1.ietf.org>
Date: Fri, 24 Mar 2006 18:50:01 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: idr@ietf.org
Subject: [Idr] I-D ACTION:draft-ietf-idr-rfc2858bis-10.txt 
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>
Errors-To: idr-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing Working Group of the IETF.

	Title		: Multiprotocol Extensions for BGP-4
	Author(s)	: T. Bates, et al.
	Filename	: draft-ietf-idr-rfc2858bis-10.txt
	Pages		: 0
	Date		: 2006-3-24
	
Currently BGP-4 is capable of carrying routing information only for
IPv4. This document defines extensions to BGP-4 to enable it to carry
routing information for multiple Network Layer protocols (e.g., IPv6,
IPX, etc...). The extensions are backward compatible - a router that
supports the extensions can interoperate with a router that doesn't
support the extensions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-rfc2858bis-10.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-idr-rfc2858bis-10.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-idr-rfc2858bis-10.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-3-24165431.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idr-rfc2858bis-10.txt

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

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


--OtherAccess--

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

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr

--NextPart--




From idr-bounces@ietf.org Thu Mar 30 12:05:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FP0aL-0006Su-Ms; Thu, 30 Mar 2006 12:05:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FP0aK-0006Sk-DW
	for idr@ietf.org; Thu, 30 Mar 2006 12:05:24 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FP0aJ-0006IB-SN for idr@ietf.org; Thu, 30 Mar 2006 12:05:24 -0500
Received: from sj-core-3.cisco.com ([171.68.223.137])
	by sj-iport-3.cisco.com with ESMTP; 30 Mar 2006 09:05:23 -0800
X-IronPort-AV: i="4.03,147,1141632000"; 
	d="scan'208"; a="421466660:sNHT36023796"
Received: from [192.168.42.106] (ssh-sjc-1.cisco.com [171.68.225.134])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id k2UH5L1k008270;
	Thu, 30 Mar 2006 09:05:22 -0800 (PST)
Mime-Version: 1.0
Message-Id: <p06230942c051bf7be4fe@[192.168.42.106]>
In-Reply-To: <200508121513.j7CFDnq2012021@bright.research.att.com>
References: <200508121513.j7CFDnq2012021@bright.research.att.com>
Date: Thu, 30 Mar 2006 12:05:22 -0500
To: Bill Fenner <fenner@research.att.com>
From: "John G. Scudder" <jgs@cisco.com>
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cdb443e3957ca9b4c5b55e78cfcf4b26
Cc: Rex Fernando <rex_f@yahoo.com>, Yakov Rekhter <yakov@juniper.net>,
	idr@ietf.org
Subject: [Idr] Re: AD Review comments on draft-ietf-idr-restart
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>
Errors-To: idr-bounces@ietf.org

Bill,

I'm equally sorry for the delay in responding!=20
I'll just address your FSM comments.

At 11:13 AM -0400 8/12/05, Bill Fenner wrote:
>I'm sorry that these are so late, especially since I found only a couple of
>concerns.

=2E..

>3. In the description of the state machine modification, I'm concerned
>that the literal interpretation of
>
>       If the Graceful Restart capability with one or more AFI/SAFI has
>       been received for the session, then TcpConnectionConfirmed (Event
>       17) is treated as TcpConnectionFails (Event 18).
>
>is that the new connection is torn down -- in Established state,
>the FSM says that receiving a TcpConnectionFails means
>
>               - sets the ConnectRetryTimer to zero,
>               - deletes all routes associated with this connection,
>               - releases all the BGP resources,
>               - drops the TCP connection,
>               - increments the ConnectRetryCounter by 1,
>               - changes its state to Idle.
>
>and clearly in graceful restart you don't want to do most of those things.
>
>In fact, you don't know that it's a restarting connection until you've
>gotten the OPEN on the new connection, right?  You probably want to
>be modifying the "If a valid OPEN message (BGPOpen (Event 19)) is received"
>condition in the Established state of the FSM?

In short, no, we don't want to wait for an OPEN.=20
You can determine that you've got a restarting=20
connection simply by inspecting the IP address of=20
the remote system.  This doesn't seem=20
exceptionally well spelled out in the base FSM,=20
but if you read between the lines vigorously=20
enough it's there.  More importantly, it's true=20
in practice.

So, I'd say the draft is correct in spirit, but=20
in reviewing it I see that the words are kind of=20
broken (in part because the base spec changed=20
since we wrote the draft, and in part because as=20
you point out TcpConnectionFails has more baggage=20
than we wanted).

Here's a proposal for wording that matches the=20
=46SM of RFC 4271.  It kind of mashes a piece of=20
the Idle state into the handling of a TCP=20
connection arrival (Events 16 and 17) in=20
Established.  It would be possible to introduce=20
yet another state instead, but I see no=20
particular benefit to doing so (especially since=20
it'd be one of those zero-second transient=20
states).

    The specific state machine modifications to [BGP-4] Section 8.2.2 are
    as follows.=A0
  =A0
    In the Idle state, make the following change.  Replace this text:
  =A0
         - initializes all BGP resources for the peer connection,

    with
  =A0
         - initializes all BGP resources for the peer connection,
           other than those resources required in order to retain routes
           according to section 7.2 of this (Graceful Restart)
           specification,
  =A0
    In the Established state, make the following changes.
  =A0
    Replace this text:

       In response to an indication that the TCP connection is
       successfully established (Event 16 or Event 17), the second
       connection SHALL be tracked until it sends an OPEN message.

    with

       If the Graceful Restart capability with one or more AFI/SAFI has
       not been received for the session, then in response to an
       indication that a TCP connection is successfully established
       (Event 16 or Event 17), the second connection SHALL be tracked
       until it sends an OPEN message.

       However, if the Graceful Restart capability with one or more
       AFI/SAFI has been received for the session, then in response to
       Event 16 or Event 17 the local system:
  =A0=A0=A0=A0
         - retains all routes associated with this connection according
           to section 7.2 of this (Graceful Restart) specification,

         - releases all other BGP resources,

         - drops the TCP connection associated with the ESTABLISHED
           session,

         - initializes all BGP resources for the peer connection,
           other than those required in order to retain routes according
           to section 7.2,

         - sets ConnectRetryCounter to zero,

         - starts the ConnectRetryTimer with the initial value,

         - changes its state to Connect.

    Replace this text:

       If the local system receives a NOTIFICATION message (Event 24 or
       Event 25) or a TcpConnectionFails (Event 18) from the underlying
       TCP, the local system:

         - sets the ConnectRetryTimer to zero,

         - deletes all routes associated with this connection,

         - releases all the BGP resources,

         - drops the TCP connection,

         - increments the ConnectRetryCounter by 1,

         - changes its state to Idle.

    with
  =A0
       If the local system receives a NOTIFICATION message (Event 24 or
       Event 25) or if the Graceful Restart capability with one or more
       AFI/SAFI has not been received for the session and the local
       system receives a TcpConnectionFails (Event 18) from the
       underlying TCP, the local system:

         - sets the ConnectRetryTimer to zero,

         - deletes all routes associated with this connection,

         - releases all the BGP resources,

         - drops the TCP connection,

         - increments the ConnectRetryCounter by 1,

         - changes its state to Idle.

       However, if the Graceful Restart capability with one or more
       AFI/SAFI has been received for the session and the local system
       receives a TcpConnectionFails (Event 18) from the underlying TCP,
       the local system:
  =A0=A0=A0=A0
         - sets the ConnectRetryTimer to zero,

         - retains all routes associated with this connection according
           to section 7.2 of this (Graceful Restart) specification,

         - releases all other BGP resources,

         - drops the TCP connection,

         - increments the ConnectRetryCounter by 1,

         - changes its state to Idle.

As a reminder, the idea is for this to correspond=20
to what the prose in section 7.2 of the draft=20
says, to wit:

    When the Restarting Speaker restarts, the Receiving Speaker may or
    may not detect the termination of the TCP session with the Restarting
    Speaker, depending on the underlying TCP implementation, whether or
    not [BGP-AUTH] is in use, and the specific circumstances of the
    restart.  In case it does not detect the TCP reset and still
    considers the BGP session as being established, it SHALL treat the
    subsequent open connection from the peer as an indication of TCP
    reset and act accordingly (when the Graceful Restart Capability has
    been received from the peer). See Section 8 for a description of this
    behavior in terms of the BGP finite state machine.

    "Acting accordingly" in this context means that the previous TCP
    session SHOULD be closed, and the new one retained.  Note that this
    behavior differs from the default behavior, as specified in [BGP-4]
    section 6.8.  Since the previous connection is considered to be
    reset, no NOTIFICATION message should be sent -- the previous TCP
    session is simply closed.

    When the Receiving Speaker detects TCP reset for a BGP session with a
    peer that has advertised the Graceful Restart Capability, it SHALL
    retain the routes received from the peer for all the address families
    that were previously received in the Graceful Restart Capability, and
    SHALL mark them as stale routing information. To deal with possible
    consecutive restarts, a route (from the peer) previously marked as
    stale SHALL be deleted. The router SHOULD NOT differentiate between
    stale and other routing information during forwarding.

and so on.

Regards,

--John

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr



From idr-bounces@ietf.org Fri Mar 31 20:45:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FPVAS-00046j-EH; Fri, 31 Mar 2006 20:44:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FPVAR-00046a-Uv
	for idr@ietf.org; Fri, 31 Mar 2006 20:44:43 -0500
Received: from iceblock01.tropos.com ([12.108.168.187])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FPVAN-0003VZ-5I
	for idr@ietf.org; Fri, 31 Mar 2006 20:44:43 -0500
Received: (qmail 3736 invoked from network); 1 Apr 2006 01:42:02 -0000
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on iceblock01
X-Spam-Level: 
X-Spam-Status: No, score=-104.4 required=6.0 tests=ALL_TRUSTED,AWL,BAYES_00,
	USER_IN_WHITELIST autolearn=ham version=3.1.0
Received: from ca-bay-exch-01.tropos.com (192.168.1.49)
	by iceblock01.tropos.com with SMTP; 1 Apr 2006 01:42:01 -0000
Received: from LIPC ([192.168.1.177]) by ca-bay-exch-01.tropos.com with
	Microsoft SMTPSVC(6.0.3790.1830); Fri, 31 Mar 2006 17:43:45 -0800
From: "Tony Li" <tli@tropos.com>
To: "'Jeffrey Haas'" <jhaas@pfrc.org>,
	<idr@ietf.org>
Subject: RE: [Idr] Hop-limit: Hop calculation
Date: Fri, 31 Mar 2006 17:43:37 -0800
Message-ID: <000001c6552d$b4e2a780$b101a8c0@tropos.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
Thread-Index: AcZN1hGVRBENRj1YT4WMdYYO2u9VZQHV4C1g
In-Reply-To: <20060322172817.GA27867@scc.mi.org>
X-OriginalArrivalTime: 01 Apr 2006 01:43:45.0631 (UTC)
	FILETIME=[B6DAA6F0:01C6552D]
X-Antivirus: Scanned by Tropos Antivirus 1.0.4
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: 
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: tony.li@tony.li
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>
Errors-To: idr-bounces@ietf.org

 

> > > While I understand that the current choice in the 
> hop-limit draft was 
> > > made to reflect a meaningful case (someone along the way simply 
> > > collapsed the elements), I believe that it can be argued that the 
> > > existing counting is just as applicable.  And has the 
> > > advantage of consistency.
> > 
> > I don't have a big problem with this.  Do other folks have opinions?
> 
> I think I had made a similar comment earlier.  I'm in support of this.


Folks,

I've heard no further discussion on this, so unless there is some
immediate dissent, I'll be updating the draft accordingly.

Regards,
Tony



_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr



