From routing-discussion-bounces@ietf.org Thu Jun 01 09:13:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Flmz9-0001nd-Cl; Thu, 01 Jun 2006 09:13:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Flmz7-0001nY-LZ
	for routing-discussion@ietf.org; Thu, 01 Jun 2006 09:13:09 -0400
Received: from [204.9.221.19] (helo=thingmagic.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Flmz6-0008Kj-CF
	for routing-discussion@ietf.org; Thu, 01 Jun 2006 09:13:09 -0400
Received: from [66.30.121.250] (account margaret HELO ceili)
	by thingmagic.com (CommuniGate Pro SMTP 5.0.1)
	with ESMTPSA id 1012372; Thu, 01 Jun 2006 09:13:07 -0400
From: "Margaret Wasserman" <margaret@thingmagic.com>
To: "'Bill Fenner'" <fenner@research.att.com>,
	<routing-discussion@ietf.org>
Date: Thu, 1 Jun 2006 09:13:07 -0400
Message-ID: <015a01c6857d$203e5540$0202a8c0@corp.devicescape.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.2869
Thread-Index: AcaFE/4QMfVdTEd3QSqJRuMl5yUOgQAaNC9Q
In-Reply-To: <200606010040.k510e4b6005103@bright.research.att.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: 
Subject: RE: Obsoleting RFC 1264?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org


Having seen the difficulties caused by RFC 1264 from several perspectives, I
support Bill's proposal to obsolete it.

I believe that these policies were very valuable at the time they were
written, but that they no longer provide benefits that outweigh their costs.

Margaret 

> -----Original Message-----
> From: Bill Fenner [mailto:fenner@research.att.com] 
> Sent: Wednesday, May 31, 2006 8:40 PM
> To: routing-discussion@ietf.org
> Subject: Obsoleting RFC 1264?
> 
> 
> [I've bcc'd this message to the int-area list, but I'd like 
> the discussion to occur on the Routing area list.
> There's not much other traffic on the Routing area list so I 
> encourage int-area subscribers to pick it up for this thread.]
> 
> Dear friends,
> 
>   There was quite a bit of discussion at the last IETF 
> meeting, in the Routing Area and Internet Area meetings, 
> about draft-fenner-zinin-rtg-standard-reqts.  The discussion 
> was quite split, with strenuous arguments on both sides of 
> the issue.  I'd like to float the opposite plan as a trial
> balloon: declare RFC1264 obsolete.  I believe that
> a) the existing (business, etc.)  incentives against 
> deploying something prematurely in the Internet are sufficient, and
> b) the lack of an RFC doesn't prevent something's deployment.
> 
>   All the rules serve to do is to increase the work on the 
> working groups and the ADs, and make the IETF appear to be a 
> bureaucratic organization that makes it difficult to publish 
> good ideas.  The barriers against bad ideas are still in place:
> - The judgement of the Working Group
> - The judgement of the IESG
> - The IESG [presumably delegating the task to the Routing ADs]
>   can still ask for implementation/deployment experience if
>   it appears to be needed.
> 
> I have just spent too long watching the barriers work against 
> good ideas.
> 
>   Bill
> 
> ----- Begin forwarded message:
> 
> From: Internet-Drafts@ietf.org
> Subject: I-D ACTION:draft-fenner-obsolete-1264-00.txt
> Date: Wed, May 31 12:50:02
> To: i-d-announce@ietf.org
> Reply-to: internet-drafts@ietf.org
> 
> 
> 	Title		: RFC 1264 is Obsolete
> 	Author(s)	: B. Fenner
> 	Filename	: draft-fenner-obsolete-1264-00.txt
> 	Pages		: 5
> 	Date		: 2006-5-31
> 	
> RFC 1264 was written during what was effectively a completely
> different time in the life of the Internet.  It prescribed rules to
> protect the Internet against new routing protocols that may have
> various undesirable properties.  In today's Internet, there are so
> many other pressures against deploying unreasonable protocols that we
> believe that existing controls suffice, and the RFC 1264 rules just
> get in the way.
> 
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-fenner-obsolete-1264-00.txt
> 
> ----- End forwarded message:
> 
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www1.ietf.org/mailman/listinfo/routing-discussion
> 


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 01 09:25:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FlnBP-00049h-Kd; Thu, 01 Jun 2006 09:25:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FlnBO-00049c-Mk
	for routing-discussion@ietf.org; Thu, 01 Jun 2006 09:25:50 -0400
Received: from nf-out-0910.google.com ([64.233.182.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FlnBN-0000QZ-DW
	for routing-discussion@ietf.org; Thu, 01 Jun 2006 09:25:50 -0400
Received: by nf-out-0910.google.com with SMTP id g2so540871nfe
	for <routing-discussion@ietf.org>; Thu, 01 Jun 2006 06:25:48 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
	b=J/xpibTMj6pmhE7FYBdnSprtExNl+Ev8JNHqcKeUC07Bt4I21OPzAtnfMvxQTOh15my7w8u6EIeEUKzjnSv+eY5TkkX4wBBqFw5oVtbIT7KiuX1L5WXq6GKHWbLGwP8IKTwADVHfRJbKp/95ii8zNy8XSiQTUMpB98p2MA51RBc=
Received: by 10.48.108.18 with SMTP id g18mr436239nfc;
	Thu, 01 Jun 2006 06:23:54 -0700 (PDT)
Received: by 10.67.28.18 with HTTP; Thu, 1 Jun 2006 06:23:54 -0700 (PDT)
Message-ID: <84a612dd0606010623i206c2f4h6fe01407f121d217@mail.gmail.com>
Date: Thu, 1 Jun 2006 14:23:54 +0100
From: "Mark Handley" <M.Handley@cs.ucl.ac.uk>
To: "Bill Fenner" <fenner@research.att.com>
In-Reply-To: <200606010040.k510e4b6005103@bright.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <200606010040.k510e4b6005103@bright.research.att.com>
X-Google-Sender-Auth: 240dc272767486bb
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

On 6/1/06, Bill Fenner <fenner@research.att.com> wrote:
> Dear friends,
>
>   There was quite a bit of discussion at the last IETF meeting,
> in the Routing Area and Internet Area meetings, about
> draft-fenner-zinin-rtg-standard-reqts.  The discussion
> was quite split, with strenuous arguments on both sides of
> the issue.  I'd like to float the opposite plan as a trial
> balloon: declare RFC1264 obsolete.  I believe that
> a) the existing (business, etc.)  incentives against deploying
> something prematurely in the Internet are sufficient, and
> b) the lack of an RFC doesn't prevent something's deployment.

I agree.  Most RFCs already take long enough without dragging the
process out further.  And I rarely see vendors rushing to support a
routing protocol just because it became an RFC :-)

 - Mark

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 01 10:35:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FloGd-0007Cx-QC; Thu, 01 Jun 2006 10:35:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FloGc-0007Cs-Ht
	for routing-discussion@ietf.org; Thu, 01 Jun 2006 10:35:18 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FloGb-00010C-8w
	for routing-discussion@ietf.org; Thu, 01 Jun 2006 10:35:18 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-4.cisco.com with ESMTP; 01 Jun 2006 07:35:17 -0700
X-IronPort-AV: i="4.05,197,1146466800"; 
	d="scan'208"; a="1817199814:sNHT29012480"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id k51EZGMf015436; 
	Thu, 1 Jun 2006 07:35:16 -0700
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k51EZFku015179; 
	Thu, 1 Jun 2006 10:35:15 -0400 (EDT)
Message-Id: <200606011435.k51EZFku015179@rtp-core-1.cisco.com>
To: Bill Fenner <fenner@research.att.com>
In-reply-to: Your message of Wed, 31 May 2006 17:40:04 -0700.
	<200606010040.k510e4b6005103@bright.research.att.com> 
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 01 Jun 2006 10:35:15 -0400
From: Eric Rosen <erosen@cisco.com>
DKIM-Signature: a=rsa-sha1; q=dns; l=61; t=1149172516; x=1150036516;
	c=relaxed/simple; s=sjdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=erosen@cisco.com;
	z=From:Eric=20Rosen=20<erosen@cisco.com>
	|Subject:Re=3A=20Obsoleting=20RFC=201264?=20;
	X=v=3Dcisco.com=3B=20h=3DN4C2wlXOWCQ5vCPZKEA63ienQVc=3D;
	b=QEB8oF3Q5A1L1pV3CTsJ/jJQGpO7TQ6IraSoqFy3eODDbHfuoZIL3OhQ0/LkfYGiOOUfkQWJ
	3xJ8ckFLUEUGLSQBm+JVs4THY6QaCOXkeUUlCWNfcJreaIf+tDo/kz2c;
Authentication-Results: sj-dkim-2.cisco.com; header.From=erosen@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0f1ff0b0158b41ac6b9548d0972cdd31
Cc: routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264? 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: erosen@cisco.com
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org


I'd also like to express my support for Bill's proposal. 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 01 10:54:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FloZB-0006ad-UH; Thu, 01 Jun 2006 10:54:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FloZA-0006aX-7M
	for routing-discussion@ietf.org; Thu, 01 Jun 2006 10:54:28 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FloZ8-0002sT-UH
	for routing-discussion@ietf.org; Thu, 01 Jun 2006 10:54:28 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-5.cisco.com with ESMTP; 01 Jun 2006 07:54:25 -0700
X-IronPort-AV: i="4.05,197,1146466800"; 
	d="scan'208"; a="286980646:sNHT161671186"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id k51EsO7C004537; 
	Thu, 1 Jun 2006 07:54:24 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k51EsOku019528; 
	Thu, 1 Jun 2006 10:54:24 -0400 (EDT)
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, 1 Jun 2006 10:54:24 -0400
Received: from [10.82.208.30] ([10.82.208.30]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); Thu, 1 Jun 2006 10:54:23 -0400
Message-ID: <447EFF9F.7000809@cisco.com>
Date: Thu, 01 Jun 2006 10:54:23 -0400
From: Acee Lindem <acee@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bill Fenner <fenner@research.att.com>
References: <200606010040.k510e4b6005103@bright.research.att.com>
In-Reply-To: <200606010040.k510e4b6005103@bright.research.att.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Jun 2006 14:54:23.0763 (UTC)
	FILETIME=[4561E630:01C6858B]
DKIM-Signature: a=rsa-sha1; q=dns; l=141; t=1149173665; x=1150037665;
	c=relaxed/simple; s=sjdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=acee@cisco.com; z=From:Acee=20Lindem=20<acee@cisco.com>
	|Subject:Re=3A=20Obsoleting=20RFC=201264?;
	X=v=3Dcisco.com=3B=20h=3DGyTvwxk0QTGiYyd2rpALBsSb844=3D;
	b=MjjwopJ9fWmSdwwj6+xOucfdAQLEQfOIUFOncfm/H31VK0AQxvHTDv+Wav6k8DuAmOGCvYlp
	iwyYq4ql7d00bdGWgINX7rWr0BZNNjwsImvjtRDq+sOWXqvwpU0Af/tx;
Authentication-Results: sj-dkim-2.cisco.com; header.From=acee@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Cc: routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

Bill,
I support this proposal as well - we'll have to find something
new to argue about at the Routing Area meetings :^)

Thanks,
Acee

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 01 11:56:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FlpXR-00017t-My; Thu, 01 Jun 2006 11:56:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FlpXQ-000103-Av
	for routing-discussion@ietf.org; Thu, 01 Jun 2006 11:56:44 -0400
Received: from mgw-ext11.nokia.com ([131.228.20.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FlpXO-000100-Su
	for routing-discussion@ietf.org; Thu, 01 Jun 2006 11:56:44 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext11.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k51FucGY006919; Thu, 1 Jun 2006 18:56:42 +0300
Received: from esebh002.NOE.Nokia.com ([172.21.138.77]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Jun 2006 18:56:39 +0300
Received: from [10.186.158.136] ([10.241.58.32]) by esebh002.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Thu, 1 Jun 2006 18:56:38 +0300
In-Reply-To: <200606010040.k510e4b6005103@bright.research.att.com>
References: <200606010040.k510e4b6005103@bright.research.att.com>
Mime-Version: 1.0 (Apple Message framework v750)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <02508EC8-F62F-4A61-B2ED-F80EC1BE657E@nokia.com>
Content-Transfer-Encoding: 7bit
From: Bob Hinden <bob.hinden@nokia.com>
Date: Thu, 1 Jun 2006 08:57:07 -0700
To: Bill Fenner <fenner@research.att.com>
X-Mailer: Apple Mail (2.750)
X-OriginalArrivalTime: 01 Jun 2006 15:56:39.0136 (UTC)
	FILETIME=[F7D69600:01C68593]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Cc: routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

Bill,

> the issue.  I'd like to float the opposite plan as a trial
> balloon: declare RFC1264 obsolete.

I support this.  It made sense back in 1991 when it was published,  
but things have changed a lot and I agree it is no longer necessary.

Bob


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 01 16:03:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FltNw-00005P-H5; Thu, 01 Jun 2006 16:03:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FltNv-00005K-Df
	for routing-discussion@ietf.org; Thu, 01 Jun 2006 16:03:11 -0400
Received: from lemland.kurtis.pp.se ([213.204.46.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FltNu-0002xA-2T
	for routing-discussion@ietf.org; Thu, 01 Jun 2006 16:03:11 -0400
Received: from [10.242.22.240] (m815f36d0.tmodns.net [208.54.95.129])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(Client did not present a certificate)
	by lemland.kurtis.pp.se (Postfix) with ESMTP id 0C26F78C1F;
	Thu,  1 Jun 2006 22:03:07 +0200 (CEST)
In-Reply-To: <200606010040.k510e4b6005103@bright.research.att.com>
References: <200606010040.k510e4b6005103@bright.research.att.com>
Mime-Version: 1.0 (Apple Message framework v750)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <D71EAFED-D761-4260-909E-79F16D391622@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
Date: Thu, 1 Jun 2006 22:04:16 +0200
To: Bill Fenner <fenner@research.att.com>
X-Mailer: Apple Mail (2.750)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org


On 1 jun 2006, at 02.40, Bill Fenner wrote:

> There was quite a bit of discussion at the last IETF meeting,
> in the Routing Area and Internet Area meetings, about
> draft-fenner-zinin-rtg-standard-reqts.  The discussion
> was quite split, with strenuous arguments on both sides of
> the issue.  I'd like to float the opposite plan as a trial
> balloon: declare RFC1264 obsolete.  I believe that
> a) the existing (business, etc.)  incentives against deploying
> something prematurely in the Internet are sufficient, and
> b) the lack of an RFC doesn't prevent something's deployment.

Seems reasonable.

- kurtis -

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 01 16:12:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FltWm-0008Ge-Is; Thu, 01 Jun 2006 16:12:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FltWl-0008ER-Ae
	for routing-discussion@ietf.org; Thu, 01 Jun 2006 16:12:19 -0400
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 1FltWk-0003dQ-2u
	for routing-discussion@ietf.org; Thu, 01 Jun 2006 16:12:19 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-3.cisco.com with ESMTP; 01 Jun 2006 13:12:19 -0700
X-IronPort-AV: i="4.05,199,1146466800"; 
	d="scan'208"; a="429576552:sNHT26451380"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id k51KCHxf010548; 
	Thu, 1 Jun 2006 13:12:17 -0700
Received: from [10.0.1.2] (rtp-jgs-vpn1.cisco.com [10.82.179.66])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with SMTP id k51KCFkv004562;
	Thu, 1 Jun 2006 16:12:16 -0400 (EDT)
Mime-Version: 1.0
Message-Id: <p0623090fc0a4fa6a9f21@[10.0.1.2]>
In-Reply-To: <200606010040.k510e4b6005103@bright.research.att.com>
References: <200606010040.k510e4b6005103@bright.research.att.com>
Date: Thu, 1 Jun 2006 16:12:12 -0400
To: Bill Fenner <fenner@research.att.com>
From: "John G. Scudder" <jgs@cisco.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
DKIM-Signature: a=rsa-sha1; q=dns; l=65; t=1149192737; x=1150056737;
	c=relaxed/simple; s=sjdkim3001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jgs@cisco.com;
	z=From:=22John=20G.=20Scudder=22=20<jgs@cisco.com>
	|Subject:Re=3A=20Obsoleting=20RFC=201264?;
	X=v=3Dcisco.com=3B=20h=3D4ZEqiVeV3i6a0o5IbTqJCPi1FFQ=3D;
	b=Sv2ixIumntkmogdhHwIFlz2wdD2QHNuMInCB0K543U8JZVMcT13o5ldfvcf1PWPl4y/uYfHz
	mzwCYECCcUuDq/1gQl4WfzznlRMUJaccWE8j2vmhiFKvLSsair1jLikz;
Authentication-Results: sj-dkim-3.cisco.com; header.From=jgs@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574
Cc: routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

Bill, thank you.  Yes, put a fork in 1264, it's done.

--John

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 01 19:50:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Flwvm-0002Fc-Tf; Thu, 01 Jun 2006 19:50:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Flwvl-0002Bj-Sa
	for routing-discussion@ietf.org; Thu, 01 Jun 2006 19:50:21 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Flwvk-0005Mm-GY
	for routing-discussion@ietf.org; Thu, 01 Jun 2006 19:50:21 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-5.cisco.com with ESMTP; 01 Jun 2006 16:50:20 -0700
X-IronPort-AV: i="4.05,199,1146466800"; 
	d="scan'208"; a="287393654:sNHT32880440"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id k51NoJE9027866; 
	Thu, 1 Jun 2006 16:50:19 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k51NoJku002562; 
	Thu, 1 Jun 2006 19:50:19 -0400 (EDT)
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, 1 Jun 2006 19:50:19 -0400
Received: from [10.86.104.178] ([10.86.104.178]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); Thu, 1 Jun 2006 19:50:18 -0400
In-Reply-To: <200606010040.k510e4b6005103@bright.research.att.com>
References: <200606010040.k510e4b6005103@bright.research.att.com>
Mime-Version: 1.0 (Apple Message framework v750)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <BD1F07EF-300C-476E-A528-34A7C6387B59@cisco.com>
Content-Transfer-Encoding: 7bit
From: JP Vasseur <jvasseur@cisco.com>
Date: Thu, 1 Jun 2006 19:50:16 -0400
To: Bill Fenner <fenner@research.att.com>
X-Mailer: Apple Mail (2.750)
X-OriginalArrivalTime: 01 Jun 2006 23:50:18.0797 (UTC)
	FILETIME=[2346B5D0:01C685D6]
DKIM-Signature: a=rsa-sha1; q=dns; l=2661; t=1149205820; x=1150069820;
	c=relaxed/simple; s=sjdkim1001; h=From:Subject;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:Re=3A=20Obsoleting=20RFC=201264?;
	X=v=3Dcisco.com=3B=20h=3DqJBMifOojwE+o9SiGVjabGp70OA=3D;
	b=qtY3i//JDqpMUZHBLvg62echbW7hiHGsIhNzmlysq6rGJY4v59iIRLlIXaGguipP5x9tGK/y
	Ydo1VlYzROKjxRKOvXLcpsuJw2U+r6oil0U8PS3NPlyR+OWEBktKAteV;
Authentication-Results: sj-dkim-1.cisco.com; header.From=jvasseur@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

Hi Bill,

In favor.

Thanks.

JP.

On May 31, 2006, at 8:40 PM, Bill Fenner wrote:

>
> [I've bcc'd this message to the int-area list, but I'd
> like the discussion to occur on the Routing area list.
> There's not much other traffic on the Routing area list
> so I encourage int-area subscribers to pick it up for
> this thread.]
>
> Dear friends,
>
>   There was quite a bit of discussion at the last IETF meeting,
> in the Routing Area and Internet Area meetings, about
> draft-fenner-zinin-rtg-standard-reqts.  The discussion
> was quite split, with strenuous arguments on both sides of
> the issue.  I'd like to float the opposite plan as a trial
> balloon: declare RFC1264 obsolete.  I believe that
> a) the existing (business, etc.)  incentives against deploying
> something prematurely in the Internet are sufficient, and
> b) the lack of an RFC doesn't prevent something's deployment.
>
>   All the rules serve to do is to increase the work on the
> working groups and the ADs, and make the IETF appear to be
> a bureaucratic organization that makes it difficult to publish
> good ideas.  The barriers against bad ideas are still in place:
> - The judgement of the Working Group
> - The judgement of the IESG
> - The IESG [presumably delegating the task to the Routing ADs]
>   can still ask for implementation/deployment experience if
>   it appears to be needed.
>
> I have just spent too long watching the barriers work against
> good ideas.
>
>   Bill
>
> ----- Begin forwarded message:
>
> From: Internet-Drafts@ietf.org
> Subject: I-D ACTION:draft-fenner-obsolete-1264-00.txt
> Date: Wed, May 31 12:50:02
> To: i-d-announce@ietf.org
> Reply-to: internet-drafts@ietf.org
>
>
> 	Title		: RFC 1264 is Obsolete
> 	Author(s)	: B. Fenner
> 	Filename	: draft-fenner-obsolete-1264-00.txt
> 	Pages		: 5
> 	Date		: 2006-5-31
> 	
> RFC 1264 was written during what was effectively a completely
> different time in the life of the Internet.  It prescribed rules to
> protect the Internet against new routing protocols that may have
> various undesirable properties.  In today's Internet, there are so
> many other pressures against deploying unreasonable protocols that we
> believe that existing controls suffice, and the RFC 1264 rules just
> get in the way.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-fenner-obsolete-1264-00.txt
>
> ----- End forwarded message:
>
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www1.ietf.org/mailman/listinfo/routing-discussion

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Fri Jun 02 02:33:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fm3Ac-00019P-Nf; Fri, 02 Jun 2006 02:30:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fm3AX-0000pv-Mm
	for routing-discussion@ietf.org; Fri, 02 Jun 2006 02:30:01 -0400
Received: from gateout01.mbox.net ([165.212.64.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fm2xu-0003LY-2S
	for routing-discussion@ietf.org; Fri, 02 Jun 2006 02:17:02 -0400
Received: from gateout01.mbox.net (gateout01.mbox.net [165.212.64.21])
	by gateout01.mbox.net (Postfix) with ESMTP id A27D5164B;
	Fri,  2 Jun 2006 06:16:54 +0000 (GMT)
Received: from gateout01.mbox.net [127.0.0.1] by gateout01.mbox.net via mtad
	(C8.MAIN.3.27X) 
	with ESMTP id 539kFBgq10428Mo1; Fri, 02 Jun 2006 06:16:53 GMT
Received: from gateout01.mbox.net [127.0.0.1] by gateout01.mbox.net via mtad
	(C8.MAIN.3.27X) 
	with ESMTP id 538kFBgqz0350Mo1; Fri, 02 Jun 2006 06:16:51 GMT
X-USANET-Routed: 2 gwsout-vs R:localhost:1825
Received: from GW1.EXCHPROD.USA.NET [165.212.116.254] by gateout01.mbox.net
	via smtad (C8.MAIN.3.27X); Fri, 02 Jun 2006 06:16:51 GMT
X-USANET-Source: 165.212.116.254 IN   skh@nexthop.com GW1.EXCHPROD.USA.NET
X-USANET-MsgId: XID037kFBgqz8319Xo1
Received: from VS4.EXCHPROD.USA.NET ([10.116.208.141]) by GW1.EXCHPROD.USA.NET
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 Jun 2006 00:16:50 -0600
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: Fri, 2 Jun 2006 00:16:43 -0600
Message-ID: <6F44D7F6B24A8F4DA0AB46C9BE924F020535671D@VS4.EXCHPROD.USA.NET>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Obsoleting RFC 1264?
Thread-Index: AcaF1jaVTYgJ8KDCQOO3pM37bMr96wANd/fw
From: "Susan Hares" <skh@nexthop.com>
To: "JP Vasseur" <jvasseur@cisco.com>, "Bill Fenner" <fenner@research.att.com>
X-OriginalArrivalTime: 02 Jun 2006 06:16:50.0713 (UTC)
	FILETIME=[22BC4090:01C6860C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: routing-discussion@ietf.org
Subject: RE: Obsoleting RFC 1264?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

Hi Bill:

In Favor.

Sue

-----Original Message-----
From: JP Vasseur [mailto:jvasseur@cisco.com]=20
Sent: Thursday, June 01, 2006 7:50 PM
To: Bill Fenner
Cc: routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264?

Hi Bill,

In favor.

Thanks.

JP.

On May 31, 2006, at 8:40 PM, Bill Fenner wrote:

>
> [I've bcc'd this message to the int-area list, but I'd
> like the discussion to occur on the Routing area list.
> There's not much other traffic on the Routing area list
> so I encourage int-area subscribers to pick it up for
> this thread.]
>
> Dear friends,
>
>   There was quite a bit of discussion at the last IETF meeting,
> in the Routing Area and Internet Area meetings, about
> draft-fenner-zinin-rtg-standard-reqts.  The discussion
> was quite split, with strenuous arguments on both sides of
> the issue.  I'd like to float the opposite plan as a trial
> balloon: declare RFC1264 obsolete.  I believe that
> a) the existing (business, etc.)  incentives against deploying
> something prematurely in the Internet are sufficient, and
> b) the lack of an RFC doesn't prevent something's deployment.
>
>   All the rules serve to do is to increase the work on the
> working groups and the ADs, and make the IETF appear to be
> a bureaucratic organization that makes it difficult to publish
> good ideas.  The barriers against bad ideas are still in place:
> - The judgement of the Working Group
> - The judgement of the IESG
> - The IESG [presumably delegating the task to the Routing ADs]
>   can still ask for implementation/deployment experience if
>   it appears to be needed.
>
> I have just spent too long watching the barriers work against
> good ideas.
>
>   Bill
>
> ----- Begin forwarded message:
>
> From: Internet-Drafts@ietf.org
> Subject: I-D ACTION:draft-fenner-obsolete-1264-00.txt
> Date: Wed, May 31 12:50:02
> To: i-d-announce@ietf.org
> Reply-to: internet-drafts@ietf.org
>
>
> 	Title		: RFC 1264 is Obsolete
> 	Author(s)	: B. Fenner
> 	Filename	: draft-fenner-obsolete-1264-00.txt
> 	Pages		: 5
> 	Date		: 2006-5-31
> =09
> RFC 1264 was written during what was effectively a completely
> different time in the life of the Internet.  It prescribed rules to
> protect the Internet against new routing protocols that may have
> various undesirable properties.  In today's Internet, there are so
> many other pressures against deploying unreasonable protocols that we
> believe that existing controls suffice, and the RFC 1264 rules just
> get in the way.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-fenner-obsolete-1264-00.txt
>
> ----- End forwarded message:
>
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www1.ietf.org/mailman/listinfo/routing-discussion

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion





_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Fri Jun 02 04:27:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fm4ze-0007Gg-HR; Fri, 02 Jun 2006 04:26:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fm4ze-0007Gb-2w
	for routing-discussion@ietf.org; Fri, 02 Jun 2006 04:26:54 -0400
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 1Fm3zd-0001hS-FV
	for routing-discussion@ietf.org; Fri, 02 Jun 2006 03:22:49 -0400
Received: from colo-dns-ext2.juniper.net ([207.17.137.64])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Fm3lL-00076g-NO
	for routing-discussion@ietf.org; Fri, 02 Jun 2006 03:08:05 -0400
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
	k527821Z017136; Fri, 2 Jun 2006 00:08:02 -0700 (PDT)
	(envelope-from kireeti@juniper.net)
Received: from kummer.juniper.net (kummer.juniper.net [172.17.12.90])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id k52782560823;
	Fri, 2 Jun 2006 00:08:02 -0700 (PDT)
	(envelope-from kireeti@juniper.net)
Received: from kummer.juniper.net (localhost [127.0.0.1])
	by kummer.juniper.net (8.12.8p1/8.12.3) with ESMTP id k52781Mo027676;
	Fri, 2 Jun 2006 00:08:02 -0700 (PDT)
	(envelope-from kireeti@juniper.net)
Received: from localhost (kireeti@localhost)
	by kummer.juniper.net (8.12.8p1/8.12.3/Submit) with ESMTP id
	k52781Yn027673; Fri, 2 Jun 2006 00:08:01 -0700 (PDT)
X-Authentication-Warning: kummer.juniper.net: kireeti owned process doing -bs
Date: Fri, 2 Jun 2006 00:08:00 -0700 (PDT)
From: Kireeti Kompella <kireeti@juniper.net>
To: Bill Fenner <fenner@research.att.com>
In-Reply-To: <200606010040.k510e4b6005103@bright.research.att.com>
Message-ID: <20060601235810.G27641@kummer.juniper.net>
References: <200606010040.k510e4b6005103@bright.research.att.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: -1.8 (-)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

On Wed, 31 May 2006, Bill Fenner wrote:

> I'd like to float the opposite plan as a trial
> balloon: declare RFC1264 obsolete.

Whoa!  A major attack of sanity!

Bill, I commend you on your courage in reversing course.  Really.

Kireeti.
-------

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Fri Jun 02 08:53:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fm98e-0003Wn-KM; Fri, 02 Jun 2006 08:52:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fm98d-0003Wi-8p
	for routing-discussion@ietf.org; Fri, 02 Jun 2006 08:52:27 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fm98b-0002GO-T2
	for routing-discussion@ietf.org; Fri, 02 Jun 2006 08:52:27 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-4.cisco.com with ESMTP; 02 Jun 2006 05:52:25 -0700
X-IronPort-AV: i="4.05,203,1146466800"; 
	d="scan'208"; a="1818002545:sNHT33415856"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id k52CqPa2010872; 
	Fri, 2 Jun 2006 05:52:25 -0700
Received: from [10.82.241.84] (rtp-vpn2-340.cisco.com [10.82.241.84])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k52CqOku023477; 
	Fri, 2 Jun 2006 08:52:24 -0400 (EDT)
Message-ID: <44803486.5080801@cisco.com>
Date: Fri, 02 Jun 2006 08:52:22 -0400
From: Russ White <riw@cisco.com>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: Bill Fenner <fenner@research.att.com>
References: <6F44D7F6B24A8F4DA0AB46C9BE924F020535671D@VS4.EXCHPROD.USA.NET>
In-Reply-To: <6F44D7F6B24A8F4DA0AB46C9BE924F020535671D@VS4.EXCHPROD.USA.NET>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=3763; t=1149252745; x=1150116745;
	c=relaxed/simple; s=sjdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=riw@cisco.com; z=From:Russ=20White=20<riw@cisco.com>
	|Subject:Re=3A=20Obsoleting=20RFC=201264?;
	X=v=3Dcisco.com=3B=20h=3DfmMGAiqQhUeTDQNxnpODlqvJ6VM=3D;
	b=pu+cUBXYDNLY0yxq1wbT6cxHBP2AquS7w+66ayG+swlqH90q1y6iXQLrczNLXRw8HdA+84I/
	haikt7eQGRHv08Vr1hz76FsarAMYSvCaeCXFKViNNUX8KiVobVlvItBA;
Authentication-Results: sj-dkim-2.cisco.com; header.From=riw@cisco.com;
	dkim=pass (
	27 extraneous bytes; sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
Cc: routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


In favor....

:-)

Russ

Susan Hares wrote:
> Hi Bill:
> 
> In Favor.
> 
> Sue
> 
> -----Original Message-----
> From: JP Vasseur [mailto:jvasseur@cisco.com] 
> Sent: Thursday, June 01, 2006 7:50 PM
> To: Bill Fenner
> Cc: routing-discussion@ietf.org
> Subject: Re: Obsoleting RFC 1264?
> 
> Hi Bill,
> 
> In favor.
> 
> Thanks.
> 
> JP.
> 
> On May 31, 2006, at 8:40 PM, Bill Fenner wrote:
> 
>> [I've bcc'd this message to the int-area list, but I'd
>> like the discussion to occur on the Routing area list.
>> There's not much other traffic on the Routing area list
>> so I encourage int-area subscribers to pick it up for
>> this thread.]
>>
>> Dear friends,
>>
>>   There was quite a bit of discussion at the last IETF meeting,
>> in the Routing Area and Internet Area meetings, about
>> draft-fenner-zinin-rtg-standard-reqts.  The discussion
>> was quite split, with strenuous arguments on both sides of
>> the issue.  I'd like to float the opposite plan as a trial
>> balloon: declare RFC1264 obsolete.  I believe that
>> a) the existing (business, etc.)  incentives against deploying
>> something prematurely in the Internet are sufficient, and
>> b) the lack of an RFC doesn't prevent something's deployment.
>>
>>   All the rules serve to do is to increase the work on the
>> working groups and the ADs, and make the IETF appear to be
>> a bureaucratic organization that makes it difficult to publish
>> good ideas.  The barriers against bad ideas are still in place:
>> - The judgement of the Working Group
>> - The judgement of the IESG
>> - The IESG [presumably delegating the task to the Routing ADs]
>>   can still ask for implementation/deployment experience if
>>   it appears to be needed.
>>
>> I have just spent too long watching the barriers work against
>> good ideas.
>>
>>   Bill
>>
>> ----- Begin forwarded message:
>>
>> From: Internet-Drafts@ietf.org
>> Subject: I-D ACTION:draft-fenner-obsolete-1264-00.txt
>> Date: Wed, May 31 12:50:02
>> To: i-d-announce@ietf.org
>> Reply-to: internet-drafts@ietf.org
>>
>>
>> 	Title		: RFC 1264 is Obsolete
>> 	Author(s)	: B. Fenner
>> 	Filename	: draft-fenner-obsolete-1264-00.txt
>> 	Pages		: 5
>> 	Date		: 2006-5-31
>> 	
>> RFC 1264 was written during what was effectively a completely
>> different time in the life of the Internet.  It prescribed rules to
>> protect the Internet against new routing protocols that may have
>> various undesirable properties.  In today's Internet, there are so
>> many other pressures against deploying unreasonable protocols that we
>> believe that existing controls suffice, and the RFC 1264 rules just
>> get in the way.
>>
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-fenner-obsolete-1264-00.txt
>>
>> ----- End forwarded message:
>>
>> _______________________________________________
>> routing-discussion mailing list
>> routing-discussion@ietf.org
>> https://www1.ietf.org/mailman/listinfo/routing-discussion
> 
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www1.ietf.org/mailman/listinfo/routing-discussion
> 
> 
> 
> 
> 
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www1.ietf.org/mailman/listinfo/routing-discussion

- --
riw@cisco.com CCIE <>< Grace Alone

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEgDSGER27sUhU9OQRAuKyAJ0fZFxQ+thpTTjvX4CGYgWBjzBAIgCgoqHB
ZiJgFOnt+wuLgpDiuioPmSI=
=O9xo
-----END PGP SIGNATURE-----

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Fri Jun 02 10:06:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FmAHo-0007tx-4C; Fri, 02 Jun 2006 10:06:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FmAHl-0007iN-FQ
	for routing-discussion@ietf.org; Fri, 02 Jun 2006 10:05:58 -0400
Received: from dns1.vpop.net ([216.193.240.2] helo=boromir.vpop.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FmAHk-0001IE-7S
	for routing-discussion@ietf.org; Fri, 02 Jun 2006 10:05:57 -0400
Received: from [192.168.2.32] (adsl-69-228-229-109.dsl.pltn13.pacbell.net
	[69.228.229.109])
	by boromir.vpop.net (Postfix) with ESMTP id 8AD578467C
	for <routing-discussion@ietf.org>; Fri,  2 Jun 2006 07:05:49 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <a06230908c0a5f5dff9bf@[192.168.2.32]>
In-Reply-To: <200606010040.k510e4b6005103@bright.research.att.com>
References: <200606010040.k510e4b6005103@bright.research.att.com>
Date: Fri, 2 Jun 2006 07:05:47 -0700
To: routing-discussion@ietf.org
From: Ari Ollikainen <Ari@OLTECO.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Subject: Re: Obsoleting RFC 1264?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

At 5:40 PM -0700 5/31/06, Bill Fenner wrote:
>I'd like to float the opposite plan as a trial
>balloon: declare RFC1264 obsolete.  I believe that
>a) the existing (business, etc.)  incentives against deploying
>something prematurely in the Internet are sufficient, and
>b) the lack of an RFC doesn't prevent something's deployment.


	I concur...


-- 

  _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
  You can't depend on your judgement when your imagination is out of focus.
						          -- Mark Twain.
  _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

        OLTECO                    Ari Ollikainen
        P.O. BOX 20088            Technology Consulting
        Stanford, CA              Ari@OLTECO.com
        94309-0088                415.517.3519

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Sat Jun 03 10:56:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FmXXk-0007ay-Uk; Sat, 03 Jun 2006 10:56:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FmXXj-0007at-WE
	for routing-discussion@ietf.org; Sat, 03 Jun 2006 10:56:00 -0400
Received: from mail2.noc.data.net.uk ([80.68.34.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FmXXi-00010Y-F2
	for routing-discussion@ietf.org; Sat, 03 Jun 2006 10:55:59 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99]
	helo=cortex.aria-networks.com)
	by mail2.noc.data.net.uk with esmtp (Exim 3.36 #1)
	id 1FmXXe-0000Pw-00
	for routing-discussion@ietf.org; Sat, 03 Jun 2006 15:55:54 +0100
Received: from your029b8cecfe ([217.158.132.168] RDNS failed) by
	cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 3 Jun 2006 15:55:55 +0100
Message-ID: <134601c6871d$cdd55770$08849ed9@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Bill Fenner" <fenner@research.att.com>,
	<routing-discussion@ietf.org>
References: <200606010040.k510e4b6005103@bright.research.att.com>
Date: Sat, 3 Jun 2006 15:54:20 +0100
Organization: Old Dog Consulting
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-OriginalArrivalTime: 03 Jun 2006 14:55:55.0676 (UTC)
	FILETIME=[D0FE35C0:01C6871D]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: 
Subject: Re: Obsoleting RFC 1264?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

Yes, indeed.

Many thanks for this initiative.  Fully supported.

Adrian
----- Original Message ----- 
From: "Bill Fenner" <fenner@research.att.com>
To: <routing-discussion@ietf.org>
Sent: Thursday, June 01, 2006 1:40 AM
Subject: Obsoleting RFC 1264?


> 
> [I've bcc'd this message to the int-area list, but I'd
> like the discussion to occur on the Routing area list.
> There's not much other traffic on the Routing area list
> so I encourage int-area subscribers to pick it up for
> this thread.]
> 
> Dear friends,
> 
>  There was quite a bit of discussion at the last IETF meeting,
> in the Routing Area and Internet Area meetings, about
> draft-fenner-zinin-rtg-standard-reqts.  The discussion
> was quite split, with strenuous arguments on both sides of
> the issue.  I'd like to float the opposite plan as a trial
> balloon: declare RFC1264 obsolete.  I believe that 
> a) the existing (business, etc.)  incentives against deploying
> something prematurely in the Internet are sufficient, and
> b) the lack of an RFC doesn't prevent something's deployment.
> 
>  All the rules serve to do is to increase the work on the
> working groups and the ADs, and make the IETF appear to be
> a bureaucratic organization that makes it difficult to publish
> good ideas.  The barriers against bad ideas are still in place:
> - The judgement of the Working Group
> - The judgement of the IESG
> - The IESG [presumably delegating the task to the Routing ADs]
>  can still ask for implementation/deployment experience if
>  it appears to be needed.
> 
> I have just spent too long watching the barriers work against
> good ideas.
> 
>  Bill
> 
> ----- Begin forwarded message:
> 
> From: Internet-Drafts@ietf.org
> Subject: I-D ACTION:draft-fenner-obsolete-1264-00.txt
> Date: Wed, May 31 12:50:02 
> To: i-d-announce@ietf.org
> Reply-to: internet-drafts@ietf.org
> 
> 
> Title : RFC 1264 is Obsolete
> Author(s) : B. Fenner
> Filename : draft-fenner-obsolete-1264-00.txt
> Pages : 5
> Date : 2006-5-31
> 
> RFC 1264 was written during what was effectively a completely
> different time in the life of the Internet.  It prescribed rules to
> protect the Internet against new routing protocols that may have
> various undesirable properties.  In today's Internet, there are so
> many other pressures against deploying unreasonable protocols that we
> believe that existing controls suffice, and the RFC 1264 rules just
> get in the way.
> 
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-fenner-obsolete-1264-00.txt
> 
> ----- End forwarded message:
> 
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www1.ietf.org/mailman/listinfo/routing-discussion
> 
> 
>


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Sat Jun 03 13:17:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FmZkW-0004Pa-33; Sat, 03 Jun 2006 13:17:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FmZkU-0004O7-So
	for routing-discussion@ietf.org; Sat, 03 Jun 2006 13:17:18 -0400
Received: from smail.alcatel.fr ([62.23.212.165])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FmZkT-0007dF-DW
	for routing-discussion@ietf.org; Sat, 03 Jun 2006 13:17:18 -0400
Received: from bemail05.netfr.alcatel.fr (bemail05.netfr.alcatel.fr
	[155.132.251.11])
	by smail.alcatel.fr (8.13.4/8.13.4/Debian-3sarge1) with ESMTP id
	k53HHFed009753; Sat, 3 Jun 2006 19:17:15 +0200
In-Reply-To: <200606010040.k510e4b6005103@bright.research.att.com>
To: Bill Fenner <fenner@research.att.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OF1E031119.2D52F39C-ONC1257181.004BC8E6-C1257182.005EF5DE@netfr.alcatel.fr>
From: Dimitri.Papadimitriou@alcatel.be
Date: Sat, 3 Jun 2006 19:16:57 +0200
X-MIMETrack: Serialize by Router on BEMAIL05/BE/ALCATEL(Release 5.0.13aHF163 |
	June 23, 2005) at 06/03/2006 19:17:15,
	Serialize complete at 06/03/2006 19:17:15
Content-Type: text/plain; charset="US-ASCII"
X-Scanned-By: MIMEDefang 2.51 on 155.132.180.81
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

hi bill

- in favor - sensible initiative.

d.




Bill Fenner <fenner@research.att.com>
01/06/2006 02:40
 
        To:     routing-discussion@ietf.org
        cc: 
        Subject:        Obsoleting RFC 1264?



[I've bcc'd this message to the int-area list, but I'd
like the discussion to occur on the Routing area list.
There's not much other traffic on the Routing area list
so I encourage int-area subscribers to pick it up for
this thread.]

Dear friends,

  There was quite a bit of discussion at the last IETF meeting,
in the Routing Area and Internet Area meetings, about
draft-fenner-zinin-rtg-standard-reqts.  The discussion
was quite split, with strenuous arguments on both sides of
the issue.  I'd like to float the opposite plan as a trial
balloon: declare RFC1264 obsolete.  I believe that 
a) the existing (business, etc.)  incentives against deploying
something prematurely in the Internet are sufficient, and
b) the lack of an RFC doesn't prevent something's deployment.

  All the rules serve to do is to increase the work on the
working groups and the ADs, and make the IETF appear to be
a bureaucratic organization that makes it difficult to publish
good ideas.  The barriers against bad ideas are still in place:
- The judgement of the Working Group
- The judgement of the IESG
- The IESG [presumably delegating the task to the Routing ADs]
  can still ask for implementation/deployment experience if
  it appears to be needed.

I have just spent too long watching the barriers work against
good ideas.

  Bill

----- Begin forwarded message:

From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-fenner-obsolete-1264-00.txt
Date: Wed, May 31 12:50:02 
To: i-d-announce@ietf.org
Reply-to: internet-drafts@ietf.org


                 Title                           : RFC 1264 is Obsolete
                 Author(s)               : B. Fenner
                 Filename                : 
draft-fenner-obsolete-1264-00.txt
                 Pages                           : 5
                 Date                            : 2006-5-31
 
RFC 1264 was written during what was effectively a completely
different time in the life of the Internet.  It prescribed rules to
protect the Internet against new routing protocols that may have
various undesirable properties.  In today's Internet, there are so
many other pressures against deploying unreasonable protocols that we
believe that existing controls suffice, and the RFC 1264 rules just
get in the way.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-fenner-obsolete-1264-00.txt

----- End forwarded message:

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Sat Jun 03 15:05:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FmbRK-00019S-OH; Sat, 03 Jun 2006 15:05:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FmbRJ-00012k-7P
	for routing-discussion@ietf.org; Sat, 03 Jun 2006 15:05:37 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FmbRH-0000PB-Ss
	for routing-discussion@ietf.org; Sat, 03 Jun 2006 15:05:37 -0400
Received: from [147.28.0.62] (helo=usmovnazinin.alcatel.com)
	by psg.com with esmtp (Exim 4.60 (FreeBSD))
	(envelope-from <zinin@psg.com>) id 1FmbRH-000A1D-Gg
	for routing-discussion@ietf.org; Sat, 03 Jun 2006 19:05:35 +0000
Date: Sat, 3 Jun 2006 12:05:21 -0700
From: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <668844517.20060603120521@psg.com>
To: routing-discussion@ietf.org
In-Reply-To: <200606010040.k510e4b6005103@bright.research.att.com>
References: <200606010040.k510e4b6005103@bright.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit
X-Spam-Score: 1.2 (+)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Subject: Re: Obsoleting RFC 1264?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Alex Zinin <zinin@psg.com>
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org


Glad to see consensus forming on this. Interestingly, we didn't have it a
few years back when it was first suggested. Apparently, discussion about
1264bis has put things in perspective :)

Let's try this and see how well this works.

-- 
Alex
http://www.psg.com/~zinin

Wednesday, May 31, 2006, 5:40:04 PM, Bill Fenner wrote:

> [I've bcc'd this message to the int-area list, but I'd
> like the discussion to occur on the Routing area list.
> There's not much other traffic on the Routing area list
> so I encourage int-area subscribers to pick it up for
> this thread.]

> Dear friends,

>   There was quite a bit of discussion at the last IETF meeting,
> in the Routing Area and Internet Area meetings, about
> draft-fenner-zinin-rtg-standard-reqts.  The discussion
> was quite split, with strenuous arguments on both sides of
> the issue.  I'd like to float the opposite plan as a trial
> balloon: declare RFC1264 obsolete.  I believe that 
> a) the existing (business, etc.)  incentives against deploying
> something prematurely in the Internet are sufficient, and
> b) the lack of an RFC doesn't prevent something's deployment.

>   All the rules serve to do is to increase the work on the
> working groups and the ADs, and make the IETF appear to be
> a bureaucratic organization that makes it difficult to publish
> good ideas.  The barriers against bad ideas are still in place:
> - The judgement of the Working Group
> - The judgement of the IESG
> - The IESG [presumably delegating the task to the Routing ADs]
>   can still ask for implementation/deployment experience if
>   it appears to be needed.

> I have just spent too long watching the barriers work against
> good ideas.

>   Bill

> ----- Begin forwarded message:

> From: Internet-Drafts@ietf.org
> Subject: I-D ACTION:draft-fenner-obsolete-1264-00.txt
> Date: Wed, May 31 12:50:02 
> To: i-d-announce@ietf.org
> Reply-to: internet-drafts@ietf.org


> 	Title		: RFC 1264 is Obsolete
> 	Author(s)	: B. Fenner
> 	Filename	: draft-fenner-obsolete-1264-00.txt
> 	Pages		: 5
> 	Date		: 2006-5-31
	
> RFC 1264 was written during what was effectively a completely
> different time in the life of the Internet.  It prescribed rules to
> protect the Internet against new routing protocols that may have
> various undesirable properties.  In today's Internet, there are so
> many other pressures against deploying unreasonable protocols that we
> believe that existing controls suffice, and the RFC 1264 rules just
> get in the way.


> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-fenner-obsolete-1264-00.txt

> ----- End forwarded message:

> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www1.ietf.org/mailman/listinfo/routing-discussion


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Sun Jun 04 09:39:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FmsoN-00083s-F5; Sun, 04 Jun 2006 09:38:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FlqGH-0006yu-37
	for routing-discussion@ietf.org; Thu, 01 Jun 2006 12:43:05 -0400
Received: from [69.37.59.173] (helo=workhorse.brookfield.occnc.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FlqGF-0006lC-Pz
	for routing-discussion@ietf.org; Thu, 01 Jun 2006 12:43:05 -0400
Received: from workhorse.brookfield.occnc.com (localhost [127.0.0.1])
	by workhorse.brookfield.occnc.com (8.13.4/8.13.4) with ESMTP id
	k51Gmrns028547; Thu, 1 Jun 2006 12:48:53 -0400 (EDT)
	(envelope-from curtis@workhorse.brookfield.occnc.com)
Message-Id: <200606011648.k51Gmrns028547@workhorse.brookfield.occnc.com>
To: "Mark Handley" <M.Handley@cs.ucl.ac.uk>
In-reply-to: Your message of "Thu, 01 Jun 2006 14:23:54 BST."
	<84a612dd0606010623i206c2f4h6fe01407f121d217@mail.gmail.com> 
Date: Thu, 01 Jun 2006 12:48:53 -0400
From: Curtis Villamizar <curtis@occnc.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
X-Mailman-Approved-At: Sun, 04 Jun 2006 09:38:34 -0400
Cc: Bill Fenner <fenner@research.att.com>, routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264? 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@faster-light.net
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org


In message <84a612dd0606010623i206c2f4h6fe01407f121d217@mail.gmail.com>
"Mark Handley" writes:
>  
> On 6/1/06, Bill Fenner <fenner@research.att.com> wrote:
> > Dear friends,
> >
> >   There was quite a bit of discussion at the last IETF meeting,
> > in the Routing Area and Internet Area meetings, about
> > draft-fenner-zinin-rtg-standard-reqts.  The discussion
> > was quite split, with strenuous arguments on both sides of
> > the issue.  I'd like to float the opposite plan as a trial
> > balloon: declare RFC1264 obsolete.  I believe that
> > a) the existing (business, etc.)  incentives against deploying
> > something prematurely in the Internet are sufficient, and
> > b) the lack of an RFC doesn't prevent something's deployment.
>  
> I agree.  Most RFCs already take long enough without dragging the
> process out further.  And I rarely see vendors rushing to support a
> routing protocol just because it became an RFC :-)
>  
>  - Mark



I'm not in favor of obsoleting rfc1264 if it means we'll be letting
protocols that are not implented and at least some deployment
experience.  There are enough junk RFCs without making it easier to
add more of them.

Its way too easy to go off and define a protocol that looks like it
will work.  Its a lot harder to implement it and prove that it works
in the field.  That is the value in keeping rfc1264.

Curtis


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Sun Jun 04 11:59:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fmv0B-0008SU-L2; Sun, 04 Jun 2006 11:58:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fmv0B-0008SP-4J
	for routing-discussion@ietf.org; Sun, 04 Jun 2006 11:58:55 -0400
Received: from motgate4.mot.com ([144.189.100.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fmv09-0001Xo-NR
	for routing-discussion@ietf.org; Sun, 04 Jun 2006 11:58:55 -0400
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate4.mot.com (8.12.11/Motgate4) with ESMTP id k54Fwm0x019587
	for <routing-discussion@ietf.org>; Sun, 4 Jun 2006 08:58:52 -0700 (MST)
Received: from de01exm64.ds.mot.com (de01exm64.am.mot.com [10.176.8.15])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id k54FwlmU009453
	for <routing-discussion@ietf.org>; Sun, 4 Jun 2006 10:58:48 -0500 (CDT)
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: Sun, 4 Jun 2006 11:58:45 -0400
Message-ID: <3870C46029D1F945B1472F170D2D9790FD1CB7@de01exm64.ds.mot.com>
In-Reply-To: <200606011648.k51Gmrns028547@workhorse.brookfield.occnc.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Obsoleting RFC 1264? 
thread-index: AcaH3D4XGiSbfKmIRA+HUqDw50MgQQAEuFig
From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
To: <routing-discussion@ietf.org>
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Subject: RE: Obsoleting RFC 1264? 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

I would like to join the consensus in supporting obsoleting RFC 1264.
The arguments below for retaining it have nothing to do with routing and
are really arguments for changing the standards levels structure of all
of the IETF. As such, they seem more relevant to the NEWTRK working
group.

Donald

-----Original Message-----
From: Curtis Villamizar [mailto:curtis@occnc.com]=20
Sent: Thursday, June 01, 2006 12:49 PM
To: Mark Handley
Cc: Bill Fenner; routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264?=20


In message <84a612dd0606010623i206c2f4h6fe01407f121d217@mail.gmail.com>
"Mark Handley" writes:
> =20
> On 6/1/06, Bill Fenner <fenner@research.att.com> wrote:
> > Dear friends,
> >
> >   There was quite a bit of discussion at the last IETF meeting, in=20
> > the Routing Area and Internet Area meetings, about=20
> > draft-fenner-zinin-rtg-standard-reqts.  The discussion was quite=20
> > split, with strenuous arguments on both sides of the issue.  I'd=20
> > like to float the opposite plan as a trial
> > balloon: declare RFC1264 obsolete.  I believe that
> > a) the existing (business, etc.)  incentives against deploying=20
> > something prematurely in the Internet are sufficient, and
> > b) the lack of an RFC doesn't prevent something's deployment.
> =20
> I agree.  Most RFCs already take long enough without dragging the=20
> process out further.  And I rarely see vendors rushing to support a=20
> routing protocol just because it became an RFC :-)
> =20
>  - Mark



I'm not in favor of obsoleting rfc1264 if it means we'll be letting
protocols that are not implented and at least some deployment
experience.  There are enough junk RFCs without making it easier to add
more of them.

Its way too easy to go off and define a protocol that looks like it will
work.  Its a lot harder to implement it and prove that it works in the
field.  That is the value in keeping rfc1264.

Curtis


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Sun Jun 04 12:35:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FmvZT-0000H2-CP; Sun, 04 Jun 2006 12:35:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FmvZS-0000Gw-CO
	for routing-discussion@ietf.org; Sun, 04 Jun 2006 12:35:22 -0400
Received: from [69.37.59.173] (helo=workhorse.brookfield.occnc.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FmvZQ-0006h4-00
	for routing-discussion@ietf.org; Sun, 04 Jun 2006 12:35:22 -0400
Received: from workhorse.brookfield.occnc.com (localhost [127.0.0.1])
	by workhorse.brookfield.occnc.com (8.13.4/8.13.4) with ESMTP id
	k54GfZOP009933; Sun, 4 Jun 2006 12:41:35 -0400 (EDT)
	(envelope-from curtis@workhorse.brookfield.occnc.com)
Message-Id: <200606041641.k54GfZOP009933@workhorse.brookfield.occnc.com>
To: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
In-reply-to: Your message of "Sun, 04 Jun 2006 11:58:45 EDT."
	<3870C46029D1F945B1472F170D2D9790FD1CB7@de01exm64.ds.mot.com> 
Date: Sun, 04 Jun 2006 12:41:35 -0400
From: Curtis Villamizar <curtis@occnc.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264? 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org


In message <3870C46029D1F945B1472F170D2D9790FD1CB7@de01exm64.ds.mot.com>
"Eastlake III Donald-LDE008" writes:
>  
> I would like to join the consensus in supporting obsoleting RFC 1264.
> The arguments below for retaining it have nothing to do with routing and
> are really arguments for changing the standards levels structure of all
> of the IETF. As such, they seem more relevant to the NEWTRK working
> group.
>  
> Donald



What is being proposed it a change to the way routing protocols are
handled within the IETF.  The reason for doing this for routing and
not for all IETF standards is that interoperability problems with
routing protocols could have a widespread impact, even global impact.
A user service with interoperability problems (for example) would only
mean that end users would have to use some other service, which is bad
but doesn't impact the infrastructure.

The changes makes IETF procedures more like ITU procedures where there
is no requirement for implementation (but doesn't go that far).  ITU
has a terrible track record for *deployed* routing protocols.  ITU has
wasted a lot of engineers' time writing protocols that seemed like
they would be simple enough and work but proved otherwise.

Relax the procedures too far and we'll end up standardizing junk.

Curtis


> -----Original Message-----
> From: Curtis Villamizar [mailto:curtis@occnc.com] 
> Sent: Thursday, June 01, 2006 12:49 PM
> To: Mark Handley
> Cc: Bill Fenner; routing-discussion@ietf.org
> Subject: Re: Obsoleting RFC 1264? 
>  
>  
> In message <84a612dd0606010623i206c2f4h6fe01407f121d217@mail.gmail.com>
> "Mark Handley" writes:
> >  
> > On 6/1/06, Bill Fenner <fenner@research.att.com> wrote:
> > > Dear friends,
> > >
> > >   There was quite a bit of discussion at the last IETF meeting, in 
> > > the Routing Area and Internet Area meetings, about 
> > > draft-fenner-zinin-rtg-standard-reqts.  The discussion was quite 
> > > split, with strenuous arguments on both sides of the issue.  I'd 
> > > like to float the opposite plan as a trial
> > > balloon: declare RFC1264 obsolete.  I believe that
> > > a) the existing (business, etc.)  incentives against deploying 
> > > something prematurely in the Internet are sufficient, and
> > > b) the lack of an RFC doesn't prevent something's deployment.
> >  
> > I agree.  Most RFCs already take long enough without dragging the 
> > process out further.  And I rarely see vendors rushing to support a 
> > routing protocol just because it became an RFC :-)
> >  
> >  - Mark
>  
>  
>  
> I'm not in favor of obsoleting rfc1264 if it means we'll be letting
> protocols that are not implented and at least some deployment
> experience.  There are enough junk RFCs without making it easier to add
> more of them.
>  
> Its way too easy to go off and define a protocol that looks like it will
> work.  Its a lot harder to implement it and prove that it works in the
> field.  That is the value in keeping rfc1264.
>  
> Curtis

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Sun Jun 04 22:45:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fn562-0004pC-OQ; Sun, 04 Jun 2006 22:45:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fn560-0004mL-N0
	for routing-discussion@ietf.org; Sun, 04 Jun 2006 22:45:36 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fn55z-0002hE-DH
	for routing-discussion@ietf.org; Sun, 04 Jun 2006 22:45:36 -0400
Received: from [147.28.0.62] (helo=usmovnazinin.alcatel.com)
	by psg.com with esmtp (Exim 4.60 (FreeBSD))
	(envelope-from <zinin@psg.com>)
	id 1Fn55t-000Doa-7z; Mon, 05 Jun 2006 02:45:29 +0000
Date: Sun, 4 Jun 2006 19:44:58 -0700
From: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <2290072.20060604194458@psg.com>
To: Curtis Villamizar <curtis@occnc.com>
In-Reply-To: <200606011648.k51Gmrns028547@workhorse.brookfield.occnc.com>
References: Your message of "Thu, 01 Jun 2006 14:23:54 BST."
	<84a612dd0606010623i206c2f4h6fe01407f121d217@mail.gmail.com>
	<200606011648.k51Gmrns028547@workhorse.brookfield.occnc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: Bill Fenner <fenner@research.att.com>, routing-discussion@ietf.org,
	Mark Handley <M.Handley@cs.ucl.ac.uk>
Subject: Re: Obsoleting RFC 1264?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Alex Zinin <zinin@psg.com>
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

Curtis,

  In my AD practice, there were a few cases where the implementation
  requirement really made a difference. Fortunately, these are typically
  easily identifiable and the AD still has the right to request
  implementations in those cases according to 2026.

-- 
Alex
http://www.psg.com/~zinin

Thursday, June 1, 2006, 9:48:53 AM, Curtis Villamizar wrote:

> In message <84a612dd0606010623i206c2f4h6fe01407f121d217@mail.gmail.com>
> "Mark Handley" writes:
>>  
>> On 6/1/06, Bill Fenner <fenner@research.att.com> wrote:
>> > Dear friends,
>> >
>> >   There was quite a bit of discussion at the last IETF meeting,
>> > in the Routing Area and Internet Area meetings, about
>> > draft-fenner-zinin-rtg-standard-reqts.  The discussion
>> > was quite split, with strenuous arguments on both sides of
>> > the issue.  I'd like to float the opposite plan as a trial
>> > balloon: declare RFC1264 obsolete.  I believe that
>> > a) the existing (business, etc.)  incentives against deploying
>> > something prematurely in the Internet are sufficient, and
>> > b) the lack of an RFC doesn't prevent something's deployment.
>>  
>> I agree.  Most RFCs already take long enough without dragging the
>> process out further.  And I rarely see vendors rushing to support a
>> routing protocol just because it became an RFC :-)
>>  
>>  - Mark



> I'm not in favor of obsoleting rfc1264 if it means we'll be letting
> protocols that are not implented and at least some deployment
> experience.  There are enough junk RFCs without making it easier to
> add more of them.

> Its way too easy to go off and define a protocol that looks like it
> will work.  Its a lot harder to implement it and prove that it works
> in the field.  That is the value in keeping rfc1264.

> Curtis


> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www1.ietf.org/mailman/listinfo/routing-discussion


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Mon Jun 05 05:13:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FnB9Z-0000o4-Sw; Mon, 05 Jun 2006 05:13:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FnB9Y-0000mh-4g
	for routing-discussion@ietf.org; Mon, 05 Jun 2006 05:13:40 -0400
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 1FnB9W-0002lt-PG
	for routing-discussion@ietf.org; Mon, 05 Jun 2006 05:13:40 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-3.cisco.com with ESMTP; 05 Jun 2006 02:13:40 -0700
X-IronPort-AV: i="4.05,209,1146466800"; 
	d="scan'208"; a="429793962:sNHT31792788"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id k559DbX2003901; 
	Mon, 5 Jun 2006 02:13:37 -0700
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k559DaLf010458; 
	Mon, 5 Jun 2006 11:13:36 +0200 (MEST)
Received: from mshand-wxp.cisco.com
	(dhcp-gpk02-vlan300-64-103-64-164.cisco.com [64.103.64.164])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id KAA11802;
	Mon, 5 Jun 2006 10:13:36 +0100 (BST)
Message-Id: <7.0.1.0.0.20060605101208.02081988@cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Mon, 05 Jun 2006 10:13:35 +0100
To: Bill Fenner <fenner@research.att.com>
From: mike shand <mshand@cisco.com>
In-Reply-To: <200606010040.k510e4b6005103@bright.research.att.com>
References: <200606010040.k510e4b6005103@bright.research.att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
DKIM-Signature: a=rsa-sha1; q=dns; l=2786; t=1149498818; x=1150362818;
	c=relaxed/simple; s=sjdkim3001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mshand@cisco.com;
	z=From:mike=20shand=20<mshand@cisco.com>
	|Subject:Re=3A=20Obsoleting=20RFC=201264?;
	X=v=3Dcisco.com=3B=20h=3DL7R/n/KKlU4wF73SifT+Z1gTbSk=3D;
	b=KL1uG6Yz74giS0IJDVmCnKhdeN/yJLxEp6kk3XX/oPbnJmbLAZzCOvRlqJe53DA0Y7eYdXuy
	KoQq6KpAmxStmPpiq02I5VVpzR5pOsXOUeXI3zMpTfziYoUdB2Z16MH0;
Authentication-Results: sj-dkim-3.cisco.com; header.From=mshand@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

Bill,
         Add my name to the ever growing list in support of your 
proposal. It seems absolutely the right thing to do.

         Mike

At 01:40 01/06/2006, Bill Fenner wrote:

>[I've bcc'd this message to the int-area list, but I'd
>like the discussion to occur on the Routing area list.
>There's not much other traffic on the Routing area list
>so I encourage int-area subscribers to pick it up for
>this thread.]
>
>Dear friends,
>
>   There was quite a bit of discussion at the last IETF meeting,
>in the Routing Area and Internet Area meetings, about
>draft-fenner-zinin-rtg-standard-reqts.  The discussion
>was quite split, with strenuous arguments on both sides of
>the issue.  I'd like to float the opposite plan as a trial
>balloon: declare RFC1264 obsolete.  I believe that
>a) the existing (business, etc.)  incentives against deploying
>something prematurely in the Internet are sufficient, and
>b) the lack of an RFC doesn't prevent something's deployment.
>
>   All the rules serve to do is to increase the work on the
>working groups and the ADs, and make the IETF appear to be
>a bureaucratic organization that makes it difficult to publish
>good ideas.  The barriers against bad ideas are still in place:
>- The judgement of the Working Group
>- The judgement of the IESG
>- The IESG [presumably delegating the task to the Routing ADs]
>   can still ask for implementation/deployment experience if
>   it appears to be needed.
>
>I have just spent too long watching the barriers work against
>good ideas.
>
>   Bill
>
>----- Begin forwarded message:
>
>From: Internet-Drafts@ietf.org
>Subject: I-D ACTION:draft-fenner-obsolete-1264-00.txt
>Date: Wed, May 31 12:50:02
>To: i-d-announce@ietf.org
>Reply-to: internet-drafts@ietf.org
>
>
>         Title           : RFC 1264 is Obsolete
>         Author(s)       : B. Fenner
>         Filename        : draft-fenner-obsolete-1264-00.txt
>         Pages           : 5
>         Date            : 2006-5-31
>
>RFC 1264 was written during what was effectively a completely
>different time in the life of the Internet.  It prescribed rules to
>protect the Internet against new routing protocols that may have
>various undesirable properties.  In today's Internet, there are so
>many other pressures against deploying unreasonable protocols that we
>believe that existing controls suffice, and the RFC 1264 rules just
>get in the way.
>
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-fenner-obsolete-1264-00.txt
>
>----- End forwarded message:
>
>_______________________________________________
>routing-discussion mailing list
>routing-discussion@ietf.org
>https://www1.ietf.org/mailman/listinfo/routing-discussion

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Mon Jun 05 05:17:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FnBDX-0003Qn-8z; Mon, 05 Jun 2006 05:17:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FnBDW-0003Qi-3v
	for routing-discussion@ietf.org; Mon, 05 Jun 2006 05:17:46 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnBDU-0002sF-SH
	for routing-discussion@ietf.org; Mon, 05 Jun 2006 05:17:46 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-4.cisco.com with ESMTP; 05 Jun 2006 02:17:44 -0700
X-IronPort-AV: i="4.05,209,1146466800"; 
	d="scan'208"; a="1819169815:sNHT30752176"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id k559Hi4g005710; 
	Mon, 5 Jun 2006 02:17:44 -0700
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k559HhCU019062;
	Mon, 5 Jun 2006 02:17:43 -0700 (PDT)
Received: from [212.254.247.6] (ams3-vpn-dhcp4504.cisco.com [10.61.81.151])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k559E4rG007936;
	Mon, 5 Jun 2006 02:14:04 -0700
Message-ID: <4483F6B6.10900@cisco.com>
Date: Mon, 05 Jun 2006 11:17:42 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060530)
MIME-Version: 1.0
To: curtis@occnc.com
References: <200606041641.k54GfZOP009933@workhorse.brookfield.occnc.com>
In-Reply-To: <200606041641.k54GfZOP009933@workhorse.brookfield.occnc.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Authentication-Results: sj-dkim-2.cisco.com; header.From=lear@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
DKIM-Signature: a=rsa-sha1; q=dns; l=652; t=1149499064; x=1150363064;
	c=relaxed/simple; s=sjdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=lear@cisco.com; z=From:Eliot=20Lear=20<lear@cisco.com>
	|Subject:Re=3A=20Obsoleting=20RFC=201264?;
	X=v=3Dcisco.com=3B=20h=3DfAD8gxoizmozfJxOZCgXviU2p3Q=3D;
	b=q+Q/WZEbNTFchXRqEN91HxKHtNs8CQn+K+rcDJxsR04ShUxQx7WKsT6qrAAQzsSHfRqynkW3
	QKgaMRlqaRkSq4RMkJXVAoEIOMgoMzZkF0mOpEAXbXekKGaf2ZWnY2Wx;
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

Curtis,

Two things:

It seems to me that WG chairs and ADs are more reticent to sanction work
where they see no engineering behind it.  This has been the case even
for stuff I thought was crap, but for other stuff too.

Further, it seems to me, particularly in the area of MPLS, that stupid
interoperability problems have developed because of this policy when
vendors did their own implementations and deployed them throughout the
network.  Thus far it's been dumb things like error codes but you could
easily imagine worse.  The point is that nobody waits for the WG to
start, much less finish, so what does this document buy?

Eliot

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Mon Jun 05 09:35:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FnFEz-0004T5-UZ; Mon, 05 Jun 2006 09:35:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FnFEy-0004R7-73
	for routing-discussion@ietf.org; Mon, 05 Jun 2006 09:35:32 -0400
Received: from [69.37.59.173] (helo=workhorse.brookfield.occnc.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnFAO-0004Me-Rd
	for routing-discussion@ietf.org; Mon, 05 Jun 2006 09:30:51 -0400
Received: from workhorse.brookfield.occnc.com (localhost [127.0.0.1])
	by workhorse.brookfield.occnc.com (8.13.4/8.13.4) with ESMTP id
	k55DawNS001265; Mon, 5 Jun 2006 09:36:58 -0400 (EDT)
	(envelope-from curtis@workhorse.brookfield.occnc.com)
Message-Id: <200606051336.k55DawNS001265@workhorse.brookfield.occnc.com>
To: Eliot Lear <lear@cisco.com>
In-reply-to: Your message of "Mon, 05 Jun 2006 11:17:42 +0200."
	<4483F6B6.10900@cisco.com> 
Date: Mon, 05 Jun 2006 09:36:58 -0400
From: Curtis Villamizar <curtis@occnc.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: routing-discussion@ietf.org, curtis@occnc.com
Subject: Re: Obsoleting RFC 1264? 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org


In message <4483F6B6.10900@cisco.com>
Eliot Lear writes:
>  
> Curtis,
>  
> Two things:
>  
> It seems to me that WG chairs and ADs are more reticent to sanction work
> where they see no engineering behind it.  This has been the case even
> for stuff I thought was crap, but for other stuff too.
>  
> Further, it seems to me, particularly in the area of MPLS, that stupid
> interoperability problems have developed because of this policy when
> vendors did their own implementations and deployed them throughout the
> network.  Thus far it's been dumb things like error codes but you could
> easily imagine worse.  The point is that nobody waits for the WG to
> start, much less finish, so what does this document buy?
>  
> Eliot


MPLS FRR is a good example.

Some would argue that a common spec was needed much earlier.  If we
had done that it would very likely have been based entirely on the
detour method (one-to-one) simple because it was there first.  The
work didn't go forward mostly because of the limited interoperability.
The original implementations of the bypass method (facilities) was
challenged and didn't get deployed for a long time.  The facilities
method does turn out to be the preferred method since it requires less
LSPs but as long as the bypass tunnesl can be set up automatically as
needed.  The detour method does not require a platform label space.

This is an example of vendors doing their own thing but in the end the
IETF process worked.  The FRR spec accomodates both methods.  I think
at this point most of the major players support both methods.
Providers seem to be leaning toward the bypass method.  Had we rushed
through the IETF process we'd have FRR using detour only and possibly
a later separate doc supporting bypass.

Some people think that as soon as the ink dries we should RAM specs
through as long as people voice support for it.  I don't agree.

With the current procedures vendors will experiment with specs before
they are accepted and there will be a lot of failed experiments.  Only
the ones that work get standardized.  Lighten the requirements too
much and we'll be standardizing things that don't work.  We don't need
more RFC1577s or NHRP.  The IETF IP over ATM and related WGs was a
nightmare with lots of proposals that are dead now and a few that went
through that are RFCs that never went anywhere.  We have seen multiple
generations of telco engineer trying to reengineer the Internet, from
the days of IPLDN (IP over Large Data Network) to ATM to today.  Most
of that work has been a complete failure.  If anything we've already
let too much slip through that either never got deploued or failed.
There are only a few cases of specs that were never implemented but
very many where they were not deployed or had limited deployment and
failed (very often for reasons that had already been predicted).

Curtis

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Tue Jun 06 00:30:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FnTD8-0003rl-Jk; Tue, 06 Jun 2006 00:30:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FnTD7-0003pi-DL
	for routing-discussion@ietf.org; Tue, 06 Jun 2006 00:30:33 -0400
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 1FnRik-00058X-GN
	for routing-discussion@ietf.org; Mon, 05 Jun 2006 22:55:06 -0400
Received: from motgate3.mot.com ([144.189.100.103])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FnRWi-0002gL-JM
	for routing-discussion@ietf.org; Mon, 05 Jun 2006 22:42:41 -0400
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate3.mot.com (8.12.11/Motgate3) with ESMTP id k562gTmA009511
	for <routing-discussion@ietf.org>; Mon, 5 Jun 2006 19:42:29 -0700 (MST)
Received: from de01exm64.ds.mot.com (de01exm64.am.mot.com [10.176.8.15])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id k562gSvo017277
	for <routing-discussion@ietf.org>; Mon, 5 Jun 2006 21:42:28 -0500 (CDT)
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: Mon, 5 Jun 2006 22:42:26 -0400
Message-ID: <3870C46029D1F945B1472F170D2D979001013067@de01exm64.ds.mot.com>
In-Reply-To: <200606041641.k54GfZOP009933@workhorse.brookfield.occnc.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Obsoleting RFC 1264? 
thread-index: AcaH9Oh5q2bmQ8U2TBeIOhp6lpa9mwAusMDA
From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
To: <routing-discussion@ietf.org>
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
Subject: RE: Obsoleting RFC 1264? 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

See below at @@@=20

-----Original Message-----
From: Curtis Villamizar [mailto:curtis@occnc.com]=20
Sent: Sunday, June 04, 2006 12:42 PM
To: Eastlake III Donald-LDE008
Cc: routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264?=20

In message <3870C46029D1F945B1472F170D2D9790FD1CB7@de01exm64.ds.mot.com>
"Eastlake III Donald-LDE008" writes:
> =20
> I would like to join the consensus in supporting obsoleting RFC 1264.
> The arguments below for retaining it have nothing to do with routing=20
> and are really arguments for changing the standards levels structure=20
> of all of the IETF. As such, they seem more relevant to the NEWTRK=20
> working group.
> =20
> Donald

What is being proposed it a change to the way routing protocols are
handled within the IETF. =20

@@@ Believe it or not I do understand, or at least think I understand,
what this discussion is about.

The reason for doing this for routing and not for all IETF standards is
that interoperability problems with routing protocols could have a
widespread impact, even global impact.
A user service with interoperability problems (for example) would only
mean that end users would have to use some other service, which is bad
but doesn't impact the infrastructure.

@@@ I am aware of this theory but your message, to which I was
responding, did not mention it and contained only generic IETF
standardization statements, more suitable for NEWTRK. In any case, I
don't believe that the mere demonstration of interoperability makes that
much difference to the probability of the existence of obscure perverse
behavior modes or the difficulty of people who are anywhere along the
spectrum from incompetent implementers to brilliant malefactors from
producing implementations that will try to screw things up. As well as
all the other factors that have been mentioned, such as the strong
motivation for ISPs to deliver bits since they are unlikely to be paid
if they fail in this, there is also the ever increasing attention being
given to security hardening of the network to defend against attacks.
The DNS is globally distributed, there is no evidence it has had any
more problems than routing, but it never had the RFC 1264 restriction.

The changes makes IETF procedures more like ITU procedures where there
is no requirement for implementation (but doesn't go that far).  ITU has
a terrible track record for *deployed* routing protocols.  ITU has
wasted a lot of engineers' time writing protocols that seemed like they
would be simple enough and work but proved otherwise.

@@@ Sounds good. I hope the ITU will continue to occupy engineers
willing to work on bad routing protocols so only those who want to work
on good routing protocols are active in the IETF. :-)

@@@ Seriously, I think the main difference is that in groups like the
ITU and the IEEE, a working group is a very expensive ponderous thing
while in the IETF they are relatively (and I emphasize this is only
relative) light weight. Sure, many more IETF WGs fail and the heavy
weight model increases the probability that a working group will produce
some document, nicely typeset and edited, more or less on schedule, but
it sure doesn't guarantee it will always be useful. I prefer the light
weight IETF model which, in my opinion, includes the relatively low
threshold for the lowest rung of the standardization ladder. And I think
that the relatively greater success of IETF protocols over the long run
supports my inclination.

Relax the procedures too far and we'll end up standardizing junk.

@@@ I just don't see it being much of a problem, with routing having
achieved its current state of maturity. And even if a new junk routing
protocol should achieve the status of Proposed Standard, why would this
really be such a problem? Seems like it would provide an excellent
opportunity for many academic papers analyzing its weaknesses...

Curtis

@@@ Donald

> -----Original Message-----
> From: Curtis Villamizar [mailto:curtis@occnc.com]
> Sent: Thursday, June 01, 2006 12:49 PM
> To: Mark Handley
> Cc: Bill Fenner; routing-discussion@ietf.org
> Subject: Re: Obsoleting RFC 1264?=20
> =20
> =20
> In message=20
> <84a612dd0606010623i206c2f4h6fe01407f121d217@mail.gmail.com>
> "Mark Handley" writes:
> > =20
> > On 6/1/06, Bill Fenner <fenner@research.att.com> wrote:
> > > Dear friends,
> > >
> > >   There was quite a bit of discussion at the last IETF meeting, in

> > > the Routing Area and Internet Area meetings, about=20
> > > draft-fenner-zinin-rtg-standard-reqts.  The discussion was quite=20
> > > split, with strenuous arguments on both sides of the issue.  I'd=20
> > > like to float the opposite plan as a trial
> > > balloon: declare RFC1264 obsolete.  I believe that
> > > a) the existing (business, etc.)  incentives against deploying=20
> > > something prematurely in the Internet are sufficient, and
> > > b) the lack of an RFC doesn't prevent something's deployment.
> > =20
> > I agree.  Most RFCs already take long enough without dragging the=20
> > process out further.  And I rarely see vendors rushing to support a=20
> > routing protocol just because it became an RFC :-)
> > =20
> >  - Mark
> =20
> =20
> =20
> I'm not in favor of obsoleting rfc1264 if it means we'll be letting=20
> protocols that are not implanted and at least some deployment=20
> experience.  There are enough junk RFCs without making it easier to=20
> add more of them.
> =20
> Its way too easy to go off and define a protocol that looks like it=20
> will work.  Its a lot harder to implement it and prove that it works=20
> in the field.  That is the value in keeping rfc1264.
> =20
> Curtis

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Tue Jun 06 17:01:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FnifV-0004aX-61; Tue, 06 Jun 2006 17:00:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FnifT-0004aI-6v
	for routing-discussion@ietf.org; Tue, 06 Jun 2006 17:00:51 -0400
Received: from [69.37.59.173] (helo=workhorse.brookfield.occnc.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnifQ-0007Vx-6t
	for routing-discussion@ietf.org; Tue, 06 Jun 2006 17:00:51 -0400
Received: from workhorse.brookfield.occnc.com (localhost [127.0.0.1])
	by workhorse.brookfield.occnc.com (8.13.4/8.13.4) with ESMTP id
	k56L70dE002035; Tue, 6 Jun 2006 17:07:00 -0400 (EDT)
	(envelope-from curtis@workhorse.brookfield.occnc.com)
Message-Id: <200606062107.k56L70dE002035@workhorse.brookfield.occnc.com>
To: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
In-reply-to: Your message of "Mon, 05 Jun 2006 22:42:26 EDT."
	<3870C46029D1F945B1472F170D2D979001013067@de01exm64.ds.mot.com> 
Date: Tue, 06 Jun 2006 17:06:59 -0400
From: Curtis Villamizar <curtis@occnc.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264? 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org


In message <3870C46029D1F945B1472F170D2D979001013067@de01exm64.ds.mot.com>
"Eastlake III Donald-LDE008" writes:

> See below at @@@ 

My comments inline.  Trimmed your response.

>  
> The changes makes IETF procedures more like ITU procedures where there
> is no requirement for implementation (but doesn't go that far).  ITU has
> a terrible track record for *deployed* routing protocols.  ITU has
> wasted a lot of engineers' time writing protocols that seemed like they
> would be simple enough and work but proved otherwise.
>  
> @@@ Sounds good. I hope the ITU will continue to occupy engineers
> willing to work on bad routing protocols so only those who want to work
> on good routing protocols are active in the IETF. :-)

Nice to know we agree on something.  Unfortunately the IETF has
already been infiltrated.  :-)

> @@@ Seriously, I think the main difference is that in groups like the
> ITU and the IEEE, a working group is a very expensive ponderous thing
> while in the IETF they are relatively (and I emphasize this is only
> relative) light weight. Sure, many more IETF WGs fail and the heavy
> weight model increases the probability that a working group will produce
> some document, nicely typeset and edited, more or less on schedule, but
> it sure doesn't guarantee it will always be useful. I prefer the light
> weight IETF model which, in my opinion, includes the relatively low
> threshold for the lowest rung of the standardization ladder. And I think
> that the relatively greater success of IETF protocols over the long run
> supports my inclination.

The ITU has evolved considerably since the CCITT days when the DoD was
the official US representation and they essentially deferred to AT&T
which made for an interesting situation when MFJ split AT&T in 1984.

It is still very much a place for big company politics and votes cast
by members with deep pockets based on their own internal company
politics.  Doesn't and never will work well IMHO.

> Relax the procedures too far and we'll end up standardizing junk.
>  
> @@@ I just don't see it being much of a problem, with routing having
> achieved its current state of maturity. And even if a new junk routing
> protocol should achieve the status of Proposed Standard, why would this
> really be such a problem? Seems like it would provide an excellent
> opportunity for many academic papers analyzing its weaknesses...

I see this a problem with RFC clutter and people not "in the know" not
being able to separate the junk from the essential RFCs.

I also see this as a problem for vendors that get RFPs with the junk
protocol in the list of required features because it had an IETF
blessing.  Some RFPs read like "we want you to implement everything
ever standardized whether we understand what its for or not as long as
it sounds like something we might someday want to use".  This is often
the product of an "RFP writing team" that cranks out 100+ page RFPs for
a living.  That's only a problem when you are on the receiving end of
one of these.

> Curtis
>  
> @@@ Donald

I'm in the minority on this and we do still beleive in rough
consensus.  So although I am expressing my opinion on this I will very
likely have to accept an outcome that is not what I'd like it to be in
this case.

Regards,

Curtis

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Tue Jun 06 18:10:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fnjl9-0002Ve-9r; Tue, 06 Jun 2006 18:10:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fnjl8-0002VY-FG
	for routing-discussion@ietf.org; Tue, 06 Jun 2006 18:10:46 -0400
Received: from mail120.messagelabs.com ([216.82.250.83])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Fnjl6-0000ol-2f
	for routing-discussion@ietf.org; Tue, 06 Jun 2006 18:10:46 -0400
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-11.tower-120.messagelabs.com!1149631726!12210901!28
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 2940 invoked from network); 6 Jun 2006 22:10:39 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4)
	by server-11.tower-120.messagelabs.com with SMTP;
	6 Jun 2006 22:10:39 -0000
Received: from kcclust06evs1.ugd.att.com (135.38.164.89) by
	attrh3i.attrh.att.com (7.2.052)
	id 4479CA7F0010B00D; Tue, 6 Jun 2006 18:10:39 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 6 Jun 2006 17:10:39 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0DDC7860@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <200606062107.k56L70dE002035@workhorse.brookfield.occnc.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Obsoleting RFC 1264? 
Thread-Index: AcaJrFy0KxwhDZgbRQGN6h+dmJam3wAB1W2A
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: <curtis@occnc.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>,
	routing-discussion@ietf.org
Subject: RE: Obsoleting RFC 1264? 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

> > @@@ Sounds good. I hope the ITU will continue to occupy engineers
> > willing to work on bad routing protocols so only those who want
> > to work on good routing protocols are active in the IETF. :-)

> Nice to know we agree on something.  Unfortunately the IETF has
> already been infiltrated.  :-)
=20
> > @@@ Seriously, I think the main difference is that in groups like
> > the ITU and the IEEE, a working group is a very expensive=20
> > ponderous thing while in the IETF they are relatively (and I
> > emphasize this is only relative) light weight. Sure, many more
> > IETF WGs fail and the heavy weight model increases the
> > probability that a working group will produce some document,
> > nicely typeset and edited, more or less on schedule, but it sure
> > doesn't guarantee it will always be useful. I prefer the light
> > weight IETF model which, in my opinion, includes the relatively low
> > threshold for the lowest rung of the standardization ladder. And I
> > think that the relatively greater success of IETF protocols over=20
> > the long run supports my inclination.

> The ITU has evolved considerably since the CCITT days when the DoD was
> the official US representation and they essentially deferred to AT&T
> which made for an interesting situation when MFJ split AT&T in 1984.
>=20
> It is still very much a place for big company politics and votes cast
> by members with deep pockets based on their own internal company
> politics.  Doesn't and never will work well IMHO.

Same old Curtis who answered by first post to IETF in 1998 (d=E9j=E0 vu =
all over again). =20

With all due respect, are all the ITU protocols, e.g. in =
http://www.itu.int/ITU-T/50/vote.html in the junk category, to remain =
forever in the dog pound?

Regards,
Jerry

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Tue Jun 06 18:54:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FnkQs-0001Bz-HF; Tue, 06 Jun 2006 18:53:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FnkQq-00017e-S4
	for routing-discussion@ietf.org; Tue, 06 Jun 2006 18:53:52 -0400
Received: from ug-out-1314.google.com ([66.249.92.168])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnkQp-0006fE-Iw
	for routing-discussion@ietf.org; Tue, 06 Jun 2006 18:53:52 -0400
Received: by ug-out-1314.google.com with SMTP id j40so61816ugd
	for <routing-discussion@ietf.org>; Tue, 06 Jun 2006 15:53:50 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=Xs6vwmg793wfr2JDD8+zWru3jvTkANpek1QSbgt1KqJDEZi3cCnf3KGlLSDDZGi9Tw4qPbz0DWLW8O4F6DJFpWRXtN25wp5obCcppceNGrJN9hZ6qPQ7N6NB8hUVreHevCzheDJZ24OBUlIzmmSYRqA1Aza53eAJaXRkhB6YDmo=
Received: by 10.78.58.11 with SMTP id g11mr12193hua;
	Tue, 06 Jun 2006 15:53:50 -0700 (PDT)
Received: by 10.78.38.8 with HTTP; Tue, 6 Jun 2006 15:53:50 -0700 (PDT)
Message-ID: <af0dc42c0606061553i1d33b76ek60f02cba03c8cae7@mail.gmail.com>
Date: Tue, 6 Jun 2006 17:53:50 -0500
From: "Janet Plato" <techgrrl@gmail.com>
To: routing-discussion@ietf.org
In-Reply-To: <200606062107.k56L70dE002035@workhorse.brookfield.occnc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <3870C46029D1F945B1472F170D2D979001013067@de01exm64.ds.mot.com>
	<200606062107.k56L70dE002035@workhorse.brookfield.occnc.com>
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Subject: Re: Obsoleting RFC 1264?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

I am against this proposal simply because complex things
sometimes fail in bynzantine ways, and operational experience
is how you find out.  Witness OSPF v1's problem with the
LSP state space.

But a lot of people I respect are in favor of it, and of the
nay votes, I only know one of them, but his voice carries
a lot of weight with me (Curtis).

I hate to make people retread old issues, but I am curious
what experiences have made people want to ditch the
rigor of RFC 1264.  It seems to me giving directors the
option of requiring operational experience is not really
the same as requiring operational experience.  Since
requiring something optional makes you look hard nosed,
I figure in practice not a lot of folks are going to be forced
to run their protocols through an operational phase since
the directors are not going to want to look needlessly
difficult.

If anyone if favor can provide pointers to materials, or summations
of their personal experiences with RFC1264 making things needlessly
difficult I would be interested.  If the answer is RTFA (A== mailing list
archive) that's OK too, but since this thread started with a comment about
how people had a discussion and much thought was exchanged, I
figured it was reasonable to ask.

Regards,

Janet Plato
In theory, there's no difference between theory and practice.
In practice, there is a difference.

On 6/6/06, Curtis Villamizar <curtis@occnc.com> wrote:
>
> I'm in the minority on this and we do still beleive in rough
> consensus.  So although I am expressing my opinion on this I will very
> likely have to accept an outcome that is not what I'd like it to be in
> this case.
>

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Wed Jun 07 16:54:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fo537-0006Bo-HC; Wed, 07 Jun 2006 16:54:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fo536-0006Bj-Mn
	for routing-discussion@ietf.org; Wed, 07 Jun 2006 16:54:44 -0400
Received: from [69.37.59.173] (helo=workhorse.brookfield.occnc.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fo532-00025r-Ho
	for routing-discussion@ietf.org; Wed, 07 Jun 2006 16:54:44 -0400
Received: from workhorse.brookfield.occnc.com (localhost [127.0.0.1])
	by workhorse.brookfield.occnc.com (8.13.4/8.13.4) with ESMTP id
	k57L0eW7006533; Wed, 7 Jun 2006 17:00:40 -0400 (EDT)
	(envelope-from curtis@workhorse.brookfield.occnc.com)
Message-Id: <200606072100.k57L0eW7006533@workhorse.brookfield.occnc.com>
To: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
In-reply-to: Your message of "Tue, 06 Jun 2006 17:10:39 CDT."
	<9473683187ADC049A855ED2DA739ABCA0DDC7860@KCCLUST06EVS1.ugd.att.com> 
Date: Wed, 07 Jun 2006 17:00:40 -0400
From: Curtis Villamizar <curtis@occnc.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: routing-discussion@ietf.org, curtis@occnc.com
Subject: Re: Obsoleting RFC 1264? 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org


In message <9473683187ADC049A855ED2DA739ABCA0DDC7860@KCCLUST06EVS1.ugd.att.com>
"Ash, Gerald R \(Jerry\), ALABS" writes:
>  
>  
> With all due respect, are all the ITU protocols, e.g. in
> http://www.itu.int/ITU-T/50/vote.html in the junk category, to remain
> forever in the dog pound?
>  
> Regards,
> Jerry


Of course not.  ITU is where many link layer protocols used in
telecommunication are defined.  Its when they get above layer 2 that
too often the result is junk.

Even at layer-1 and layer-2 not every ITU protocol is very good.  In
some cases its what we have to live with.

Sometimes things need a little fixing like the SONET scrambling that
repeated every 128 bits if you remember when Internet providers first
started using POS.  Too often 10% of the defined protocol proves
useful in the long run.  For example carriers have been moving away
from SONET protection for many years now.  Advances in 10GbE and
emergence of 40GbE and 100GbE may mean the end of SONET except as a
legacy service (much as FR and ATM are today).  The majority of use of
OC192 is OC192c as a link layer for POS and interest in OC768 seems
limited.  We'll have to wait and see.

Then there are things like X.25 and ISDN.

On the bright side above layer-2 is the widespread acceptance of X.509
PKE for SSL key distribution.  Again a fraction of the protocol is
used and not for its original purpose much as is the case in ISO 10589
(ISIS if I have the number right).

Not every IETF spec is any good either, though at layer-3 IETF has a
much better track record of defining usable protocols.  IETF has a
small problem in that the RFC collection is already cluttered with
4,000 going on 5,000 documents.  Many critical protocols are at the PS
level where it is already very difficult for newcomers and even the
moderately experienced to distinguish junk from essential documents.

Fortunately OSPF is at full standard and BGP is now at draft standard
but does that mean the ISIS work can be ignored.  Definitely not.
These are just examples.  There are plenty of PS documents that are
essential and many that simply don't work well.  Gradually we declare
the latter to be historic but in some cases they should have never
made PS.

Curtis

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Wed Jun 07 17:03:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fo5Bm-0003o2-2x; Wed, 07 Jun 2006 17:03:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fo5Bk-0003ma-Ng
	for routing-discussion@ietf.org; Wed, 07 Jun 2006 17:03:40 -0400
Received: from mx4.tellabs.com ([204.154.129.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fo5Bh-0002Qm-C5
	for routing-discussion@ietf.org; Wed, 07 Jun 2006 17:03:40 -0400
Received: from usnvwwms2c.hq.tellabs.com (HELO
	USNVEX3.tellabs-west.tellabsinc.net) ([172.23.216.105])
	by mx4.tellabs.com with ESMTP; 07 Jun 2006 21:03:37 +0000
X-SBRS: None
X-IronPort-AV: i="4.05,217,1146441600"; 
	d="scan'208"; a="55076352:sNHT26510388"
Received: from USNVEX1.tellabs-west.tellabsinc.net ([172.23.216.101]) by
	USNVEX3.tellabs-west.tellabsinc.net with Microsoft
	SMTPSVC(6.0.3790.0); Wed, 7 Jun 2006 16:03:36 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 7 Jun 2006 16:01:07 -0500
Message-ID: <A1A52203CA93634BA1748887B9993AEA02A674CE@USNVEX1.tellabs-west.tellabsinc.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Obsoleting RFC 1264? 
Thread-Index: AcaKdKxbKQvnZ+3TS4aJlJmrSYWG5wAAB1JQ
From: "Sadler, Jonathan B." <Jonathan.Sadler@tellabs.com>
To: <curtis@occnc.com>
X-OriginalArrivalTime: 07 Jun 2006 21:03:36.0739 (UTC)
	FILETIME=[D8104730:01C68A75]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: routing-discussion@ietf.org
Subject: RE: Obsoleting RFC 1264? 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

Curtis,

Just a point of clarification -- IS-IS (ISO 10589), ES-IS (ISO 9542),
and IDRP (ISO 10747) are the work of ISO, not ITU.  I'm not trying to
defend them, just want to make certain that the bazooka is pointed at
the right group before the trigger is engaged...

Jonathan Sadler

-----Original Message-----
From: Curtis Villamizar [mailto:curtis@occnc.com]=20
Sent: Wednesday, June 07, 2006 4:01 PM
To: Ash, Gerald R (Jerry), ALABS
Cc: routing-discussion@ietf.org; curtis@occnc.com
Subject: Re: Obsoleting RFC 1264?=20


In message
<9473683187ADC049A855ED2DA739ABCA0DDC7860@KCCLUST06EVS1.ugd.att.com>
"Ash, Gerald R \(Jerry\), ALABS" writes:
> =20
> =20
> With all due respect, are all the ITU protocols, e.g. in
> http://www.itu.int/ITU-T/50/vote.html in the junk category, to remain
> forever in the dog pound?
> =20
> Regards,
> Jerry


Of course not.  ITU is where many link layer protocols used in
telecommunication are defined.  Its when they get above layer 2 that
too often the result is junk.

Even at layer-1 and layer-2 not every ITU protocol is very good.  In
some cases its what we have to live with.

Sometimes things need a little fixing like the SONET scrambling that
repeated every 128 bits if you remember when Internet providers first
started using POS.  Too often 10% of the defined protocol proves
useful in the long run.  For example carriers have been moving away
from SONET protection for many years now.  Advances in 10GbE and
emergence of 40GbE and 100GbE may mean the end of SONET except as a
legacy service (much as FR and ATM are today).  The majority of use of
OC192 is OC192c as a link layer for POS and interest in OC768 seems
limited.  We'll have to wait and see.

Then there are things like X.25 and ISDN.

On the bright side above layer-2 is the widespread acceptance of X.509
PKE for SSL key distribution.  Again a fraction of the protocol is
used and not for its original purpose much as is the case in ISO 10589
(ISIS if I have the number right).

Not every IETF spec is any good either, though at layer-3 IETF has a
much better track record of defining usable protocols.  IETF has a
small problem in that the RFC collection is already cluttered with
4,000 going on 5,000 documents.  Many critical protocols are at the PS
level where it is already very difficult for newcomers and even the
moderately experienced to distinguish junk from essential documents.

Fortunately OSPF is at full standard and BGP is now at draft standard
but does that mean the ISIS work can be ignored.  Definitely not.
These are just examples.  There are plenty of PS documents that are
essential and many that simply don't work well.  Gradually we declare
the latter to be historic but in some cases they should have never
made PS.

Curtis

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Wed Jun 07 17:27:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fo5YS-000616-D5; Wed, 07 Jun 2006 17:27:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fo5YR-00060H-Gh
	for routing-discussion@ietf.org; Wed, 07 Jun 2006 17:27:07 -0400
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fo5YQ-00059b-53
	for routing-discussion@ietf.org; Wed, 07 Jun 2006 17:27:07 -0400
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70])
	by ihemail3.lucent.com (8.13.6/IER-o) with ESMTP id k57LR4qA026329; 
	Wed, 7 Jun 2006 16:27:04 -0500 (CDT)
Received: from lucent.com (sjtrowbridge.lra2.lucent.com [135.244.4.37]) by
	ihmail.ih.lucent.com (8.11.7p1+Sun/EMS-1.5 sol2)
	id k57LR4w00830; Wed, 7 Jun 2006 16:27:04 -0500 (CDT)
Message-ID: <44874488.3010905@lucent.com>
Date: Wed, 07 Jun 2006 15:26:32 -0600
From: Stephen J Trowbridge <sjtrowbridge@lucent.com>
Organization: Lucent Technologies
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.0.1) Gecko/20020823 Netscape/7.0 (CK-LucentTPES)
X-Accept-Language: en,zh
MIME-Version: 1.0
To: curtis@occnc.com
References: <200606072100.k57L0eW7006533@workhorse.brookfield.occnc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>,
	routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

Curtis,
The broken mapping you are describing for POS came from IETF (RFC 1619), fixed
later in RFC 2615. AFAIK, the mappings defined by ATIS or ITU-T for carrying
clients over SONET or SDH all worked. By the way, SONET came first from Bellcore
(remember GR-253), picked up later by T1X1(now called OPTXS) (ATIS) in the
T1.105 series. Original SDH came from ETSI. The current ITU-T SDH standard is a
superset of SONET and ETSI SDH, but there never was an ITU-T spec for SONET.

I think we see a pattern here (see also Jonathan's posting regarding ISO routing
standards): if Curtis doesn't like something, it must have come from ITU-T.
Steve

On 6/7/2006 3:00 PM, Curtis Villamizar wrote:
> In message <9473683187ADC049A855ED2DA739ABCA0DDC7860@KCCLUST06EVS1.ugd.att.com>
> "Ash, Gerald R \(Jerry\), ALABS" writes:
> 
>> 
>> 
>>With all due respect, are all the ITU protocols, e.g. in
>>http://www.itu.int/ITU-T/50/vote.html in the junk category, to remain
>>forever in the dog pound?
>> 
>>Regards,
>>Jerry
> 
> 
> 
> Of course not.  ITU is where many link layer protocols used in
> telecommunication are defined.  Its when they get above layer 2 that
> too often the result is junk.
> 
> Even at layer-1 and layer-2 not every ITU protocol is very good.  In
> some cases its what we have to live with.
> 
> Sometimes things need a little fixing like the SONET scrambling that
> repeated every 128 bits if you remember when Internet providers first
> started using POS.  Too often 10% of the defined protocol proves
> useful in the long run.  For example carriers have been moving away
> from SONET protection for many years now.  Advances in 10GbE and
> emergence of 40GbE and 100GbE may mean the end of SONET except as a
> legacy service (much as FR and ATM are today).  The majority of use of
> OC192 is OC192c as a link layer for POS and interest in OC768 seems
> limited.  We'll have to wait and see.
> 
> Then there are things like X.25 and ISDN.
> 
> On the bright side above layer-2 is the widespread acceptance of X.509
> PKE for SSL key distribution.  Again a fraction of the protocol is
> used and not for its original purpose much as is the case in ISO 10589
> (ISIS if I have the number right).
> 
> Not every IETF spec is any good either, though at layer-3 IETF has a
> much better track record of defining usable protocols.  IETF has a
> small problem in that the RFC collection is already cluttered with
> 4,000 going on 5,000 documents.  Many critical protocols are at the PS
> level where it is already very difficult for newcomers and even the
> moderately experienced to distinguish junk from essential documents.
> 
> Fortunately OSPF is at full standard and BGP is now at draft standard
> but does that mean the ISIS work can be ignored.  Definitely not.
> These are just examples.  There are plenty of PS documents that are
> essential and many that simply don't work well.  Gradually we declare
> the latter to be historic but in some cases they should have never
> made PS.
> 
> Curtis
> 
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www1.ietf.org/mailman/listinfo/routing-discussion



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Wed Jun 07 18:09:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fo6D2-0001Tt-C5; Wed, 07 Jun 2006 18:09:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fo6D1-0001To-2F
	for routing-discussion@ietf.org; Wed, 07 Jun 2006 18:09:03 -0400
Received: from [69.37.59.173] (helo=workhorse.brookfield.occnc.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fo6Cz-0003df-5J
	for routing-discussion@ietf.org; Wed, 07 Jun 2006 18:09:03 -0400
Received: from workhorse.brookfield.occnc.com (localhost [127.0.0.1])
	by workhorse.brookfield.occnc.com (8.13.4/8.13.4) with ESMTP id
	k57MF0ko007758; Wed, 7 Jun 2006 18:15:00 -0400 (EDT)
	(envelope-from curtis@workhorse.brookfield.occnc.com)
Message-Id: <200606072215.k57MF0ko007758@workhorse.brookfield.occnc.com>
To: "Sadler, Jonathan B." <Jonathan.Sadler@tellabs.com>
In-reply-to: Your message of "Wed, 07 Jun 2006 16:01:07 CDT."
	<A1A52203CA93634BA1748887B9993AEA02A674CE@USNVEX1.tellabs-west.tellabsinc.net>
Date: Wed, 07 Jun 2006 18:15:00 -0400
From: Curtis Villamizar <curtis@occnc.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: routing-discussion@ietf.org, curtis@occnc.com
Subject: Re: Obsoleting RFC 1264? 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org


In message <A1A52203CA93634BA1748887B9993AEA02A674CE@USNVEX1.tellabs-west.tellabsinc.net>
"Sadler, Jonathan B." writes:
>  
> Curtis,
>  
> Just a point of clarification -- IS-IS (ISO 10589), ES-IS (ISO 9542),
> and IDRP (ISO 10747) are the work of ISO, not ITU.  I'm not trying to
> defend them, just want to make certain that the bazooka is pointed at
> the right group before the trigger is engaged...
>  
> Jonathan Sadler


Jonathon,

I didn't mean to imply that ISIS is ITU work, only cite it as an
example of a protocol where a limited subset is used and not for the
original purpose of the protocol.  ISIS is simply the classic example
of this since native CLNP went extinct shortly after GOSIP yet ISIS
(or better to say dual-ISIS, something based on ISO10589) is still
used to carry IP routing information.

Curtis



> On the bright side above layer-2 is the widespread acceptance of X.509
> PKE for SSL key distribution.  Again a fraction of the protocol is
> used and not for its original purpose much as is the case in ISO 10589
> (ISIS if I have the number right).

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Wed Jun 07 19:47:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fo7kY-0005by-QV; Wed, 07 Jun 2006 19:47:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fo7kX-0005bt-0i
	for routing-discussion@ietf.org; Wed, 07 Jun 2006 19:47:45 -0400
Received: from [69.37.59.173] (helo=workhorse.brookfield.occnc.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fo7kV-0004yq-0I
	for routing-discussion@ietf.org; Wed, 07 Jun 2006 19:47:44 -0400
Received: from workhorse.brookfield.occnc.com (localhost [127.0.0.1])
	by workhorse.brookfield.occnc.com (8.13.4/8.13.4) with ESMTP id
	k57NrX41008150; Wed, 7 Jun 2006 19:53:33 -0400 (EDT)
	(envelope-from curtis@workhorse.brookfield.occnc.com)
Message-Id: <200606072353.k57NrX41008150@workhorse.brookfield.occnc.com>
To: Stephen J Trowbridge <sjtrowbridge@lucent.com>
In-reply-to: Your message of "Wed, 07 Jun 2006 15:26:32 MDT."
	<44874488.3010905@lucent.com> 
Date: Wed, 07 Jun 2006 19:53:33 -0400
From: Curtis Villamizar <curtis@occnc.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>,
	routing-discussion@ietf.org, curtis@occnc.com
Subject: Re: Obsoleting RFC 1264? 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org


In message <44874488.3010905@lucent.com>
Stephen J Trowbridge writes:
>  
> Curtis,
>  
> The broken mapping you are describing for POS came from IETF (RFC
> 1619), fixed later in RFC 2615. AFAIK, the mappings defined by ATIS or
> ITU-T for carrying clients over SONET or SDH all worked. By the way,
> SONET came first from Bellcore (remember GR-253), picked up later by
> T1X1(now called OPTXS) (ATIS) in the T1.105 series. Original SDH came
> from ETSI. The current ITU-T SDH standard is a superset of SONET and
> ETSI SDH, but there never was an ITU-T spec for SONET.

RFC1619 says "no scrambling is needed".  The reason for that was the
SONET already does scrambling.

I distinctly remember BBN folks (in particular John Hawkinson) arguing
at an IETF meeting that the scrambling used by Lucent at the time
already had been proven in the field not to be adequate with a brief
experiment that resulted in data on a single OC3c POS interface taking
down and entire OC48c.  That occurred somewhere between RFC1619 and
RFC2615 when the scrambiling offered by SONET was being used and the
problem occurred in the BBN/Planet network with Lucent gear.

RFC1619bis with scrambling enabled existed as a draft for a very long
time.  RFC2615 specifies the use of 43 bit scrambling.  Unless I'm
mistaken it was decided to put the scrambling in the router to
accommodate transport gear that didn't scramble adequately.

Anyway SONET is definitely not my area of expertice.  I was mostly
woking in Internet operations at the time and not involved at L2
except to configure the routers to specify scrambling.  Perhaps I
should talk to Andy Malis or Bill Simpson.

btw- Yes I know that SONET came from Bellcore but I was mistaken in
that ANSI specified SONET when this problem occurred.  I think the
problem we are talking about was identified by BBN in the 1994 to 1996
time frame.

> I think we see a pattern here (see also Jonathan's posting regarding
> ISO routing standards): if Curtis doesn't like something, it must have
> come from ITU-T.  Steve

As I said ITU does useful L1/L2 work.  Sorry to attribute SONET to
ITU at a time when ANSI handled that.

We are clearly drifting off topic.  The topic was RFC 1264.

Curtis

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Fri Jun 09 06:09:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fodvx-0006bs-4y; Fri, 09 Jun 2006 06:09:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fodvw-0006bn-Gy
	for routing-discussion@ietf.org; Fri, 09 Jun 2006 06:09:40 -0400
Received: from as2.itesm.mx ([200.34.200.188])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fodvv-0006qC-2l
	for routing-discussion@ietf.org; Fri, 09 Jun 2006 06:09:40 -0400
X-IronPort-AV: i="4.05,223,1146459600"; 
	d="scan'208,217"; a="138257873:sNHT47377808"
Received: from L00474098L01 (82.13.201.114) by itesm.mx (7.2.052)
	id 44549314002763BC for routing-discussion@ietf.org;
	Fri, 9 Jun 2006 05:09:38 -0500
Message-ID: <44549314002763BC@mailserver1.itesm.mx> (added by
	postmaster@itesm.mx)
From: "Arturo Servin" <aservin@itesm.mx>
To: <routing-discussion@ietf.org>
Date: Fri, 9 Jun 2006 11:09:35 +0100
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Thread-Index: AcaLrM9qQCv6YK3ASpOGCYOU3/tZ+A==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ccfb4541e989aa743998098cd315d0fd
Subject: Do routers learn?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1288961378=="
Errors-To: routing-discussion-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1288961378==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0033_01C68BB5.31E91C60"

This is a multi-part message in MIME format.

------=_NextPart_000_0033_01C68BB5.31E91C60
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

 

 

            I am aware that this question may be outside the scope of this
mailing list but I could not find any other place to ask about it. So, my
apologies for that.

 

            I am writing an essay about Machine Learning, Multiagent Systems
and Networks. When I was thinking about how routers share routing
information and how they learn to route this question come to me. From a
Machine Learning or from an artificial intelligence point of view, do
routers really learn?

 

            It very common for us the network guys to say that a router is
learning routes, but, it is acceptable in the AI field this concept or
learning? I was trying to find some papers that discuss the topic but I
could not. If you knew some or if you could point me to the right forum to
ask these questions I would really appreciate it.

 

Thanks in advance,

-as

 

 

 


------=_NextPart_000_0033_01C68BB5.31E91C60
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Bitstream Vera Sans";}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.Style2, li.Style2, div.Style2
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:9.0pt;
	font-family:Arial;
	font-weight:bold;}
span.EmailStyle18
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DES link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-indent:35.4pt'><font size=3D3
face=3D"Times New Roman"><span lang=3DEN-US =
style=3D'font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; </span></font><font
size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Arial'>I
am aware that this question may be outside the scope of this mailing =
list but I
could not find any other place to ask about it. So, my apologies for =
that.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; I
am writing an essay about Machine Learning, Multiagent Systems and =
Networks. When
I was thinking about how routers share routing information and how they =
learn to
route this question come to me. From a Machine Learning or from an =
artificial
intelligence point of view, do routers really =
learn?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; It
very common for us the network guys to say that a router is learning =
routes,
but, it is acceptable in the AI field this concept or learning? I was =
trying to
find some papers that discuss the topic but I could not. If you knew =
some or if
you could point me to the right forum to ask these questions I would =
really
appreciate it.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Thanks in =
advance,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>-as</span></font><span =
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-GB
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0033_01C68BB5.31E91C60--


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

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion

--===============1288961378==--




From routing-discussion-bounces@ietf.org Fri Jun 09 08:55:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FogWV-0000Hb-Kz; Fri, 09 Jun 2006 08:55:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FogWU-0000FU-18
	for routing-discussion@ietf.org; Fri, 09 Jun 2006 08:55:34 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FogWS-0001eQ-Do
	for routing-discussion@ietf.org; Fri, 09 Jun 2006 08:55:34 -0400
Received: from sj-dkim-5.cisco.com ([171.68.10.79])
	by sj-iport-4.cisco.com with ESMTP; 09 Jun 2006 05:55:27 -0700
X-IronPort-AV: i="4.05,224,1146466800"; 
	d="scan'208,217"; a="1822843638:sNHT1903833672"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-5.cisco.com (8.12.11/8.12.11) with ESMTP id k59CtRwa022770; 
	Fri, 9 Jun 2006 05:55:27 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id k59CtPJ0017512;
	Fri, 9 Jun 2006 05:55:27 -0700 (PDT)
Received: from xmb-rtp-203.amer.cisco.com ([64.102.31.20]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Fri, 9 Jun 2006 08:55:26 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 9 Jun 2006 08:55:25 -0400
Message-ID: <BABC859E6D0B9A4D8448CC7F41CD2B0701DEFCE7@xmb-rtp-203.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Do routers learn?
Thread-Index: AcaLrM9qQCv6YK3ASpOGCYOU3/tZ+AAFqsxQ
From: "Zafar Ali \(zali\)" <zali@cisco.com>
To: "Arturo Servin" <aservin@itesm.mx>, <routing-discussion@ietf.org>
X-OriginalArrivalTime: 09 Jun 2006 12:55:26.0191 (UTC)
	FILETIME=[FA5CD7F0:01C68BC3]
DKIM-Signature: a=rsa-sha1; q=dns; l=8800; t=1149857727; x=1150721727;
	c=relaxed/simple; s=sjdkim5001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=zali@cisco.com;
	z=From:=22Zafar=20Ali=20\(zali\)=22=20<zali@cisco.com>
	|Subject:RE=3A=20Do=20routers=20learn?;
	X=v=3Dcisco.com=3B=20h=3D1mVflj0dFKGf96cWWvqkhMB//RA=3D;
	b=kvIWwDVrbuKgajTA4w0T37LYmRoSGLuy+sEu68CWpWxHvqjsJ2pItrpwv1Ku/IxYvLztsHdJ
	zLF1QbCqKosF52B5XXkrk42z17UW/LMDPoDwwfx6eK4TibfxHkTrEfz4;
Authentication-Results: sj-dkim-5.cisco.com; header.From=zali@cisco.com;
	dkim=pass (
	59 extraneous bytes; sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 17bdfcaea25d1444baef0e24abc38874
Cc: 
Subject: RE: Do routers learn?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2128284393=="
Errors-To: routing-discussion-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2128284393==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C68BC3.FA16887F"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C68BC3.FA16887F
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20


________________________________

	From: Arturo Servin [mailto:aservin@itesm.mx]=20
	Sent: Friday, June 09, 2006 6:10 AM
	To: routing-discussion@ietf.org
	Subject: Do routers learn?
=09
=09

	=20

	=20

	            I am aware that this question may be outside the
scope of this mailing list but I could not find any other place to ask
about it. So, my apologies for that.

	=20

	            I am writing an essay about Machine Learning,
Multiagent Systems and Networks. When I was thinking about how routers
share routing information and how they learn to route this question come
to me. From a Machine Learning or from an artificial intelligence point
of view, do routers really learn?

	=20

IMHO no. All decisions are deterministic. If it does not know a route,
there is no inteligence or guess work involved. At least in present
implementations :-)=20

=20

Thanks

=20

Regards... Zafar=20

	=20

	            It very common for us the network guys to say that a
router is learning routes, but, it is acceptable in the AI field this
concept or learning? I was trying to find some papers that discuss the
topic but I could not. If you knew some or if you could point me to the
right forum to ask these questions I would really appreciate it.

	=20

	Thanks in advance,

	-as

	=20

	=20

	=20


------_=_NextPart_001_01C68BC3.FA16887F
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1543" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Bitstream Vera Sans;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 70.85pt 3.0cm 70.85pt =
3.0cm; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
P.Style2 {
	FONT-WEIGHT: bold; FONT-SIZE: 9pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: =
Arial; TEXT-ALIGN: justify
}
LI.Style2 {
	FONT-WEIGHT: bold; FONT-SIZE: 9pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: =
Arial; TEXT-ALIGN: justify
}
DIV.Style2 {
	FONT-WEIGHT: bold; FONT-SIZE: 9pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: =
Arial; TEXT-ALIGN: justify
}
SPAN.EmailStyle18 {
	COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DES vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Arturo Servin =
[mailto:aservin@itesm.mx]=20
  <BR><B>Sent:</B> Friday, June 09, 2006 6:10 AM<BR><B>To:</B>=20
  routing-discussion@ietf.org<BR><B>Subject:</B> Do routers=20
  learn?<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"TEXT-INDENT: 35.4pt"><FONT face=3D"Times =
New Roman"=20
  size=3D3><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: =
12pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  </SPAN></FONT><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I am aware that this =
question may=20
  be outside the scope of this mailing list but I could not find any =
other place=20
  to ask about it. So, my apologies for =
that.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
  I am writing an essay about Machine Learning, Multiagent Systems and =
Networks.=20
  When I was thinking about how routers share routing information and =
how they=20
  learn to route this question come to me. From a Machine Learning or =
from an=20
  artificial intelligence point of view, do routers really=20
  learn?<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV></BLOCKQUOTE>
<P class=3DMsoNormal dir=3Dltr><FONT color=3D#0000ff><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p><SPAN=20
class=3D137525112-09062006>IMHO no.&nbsp;All decisions are =
deterministic.=20
If&nbsp;it does not know a route, there is no inteligence or guess work=20
involved. At least in present implementations :-)=20
</SPAN></o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT color=3D#0000ff><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p><SPAN=20
class=3D137525112-09062006></SPAN></o:p></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal dir=3Dltr><FONT color=3D#0000ff><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p><SPAN=20
class=3D137525112-09062006>Thanks</SPAN></o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT color=3D#0000ff><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p><SPAN=20
class=3D137525112-09062006></SPAN></o:p></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal dir=3Dltr><FONT color=3D#0000ff><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p><SPAN=20
class=3D137525112-09062006>Regards... Zafar =
</SPAN></o:p></SPAN></FONT></P>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <P class=3DMsoNormal><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
  It very common for us the network guys to say that a router is =
learning=20
  routes, but, it is acceptable in the AI field this concept or =
learning? I was=20
  trying to find some papers that discuss the topic but I could not. If =
you knew=20
  some or if you could point me to the right forum to ask these =
questions I=20
  would really appreciate it.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Thanks in=20
  advance,<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">-as</SPAN></FONT><SPAN=20
  lang=3DEN-US><o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN lang=3DEN-GB=20
  style=3D"FONT-SIZE: 9pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C68BC3.FA16887F--


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

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion

--===============2128284393==--




From routing-discussion-bounces@ietf.org Wed Jun 14 17:51:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FqdGc-0005xk-VD; Wed, 14 Jun 2006 17:51:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FqdAO-0002Hu-Rj
	for routing-discussion@ietf.org; Wed, 14 Jun 2006 17:44:48 -0400
Received: from mail-red.research.att.com ([192.20.225.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fqd5K-0005TJ-VS
	for routing-discussion@ietf.org; Wed, 14 Jun 2006 17:39:36 -0400
Received: from bright.research.att.com (bright.research.att.com
	[135.207.20.189])
	by mail-blue.research.att.com (Postfix) with ESMTP id C2A9D147AA0;
	Wed, 14 Jun 2006 17:39:34 -0400 (EDT)
Received: (from fenner@localhost)
	by bright.research.att.com (8.12.11.20060308/8.12.10/Submit) id
	k5ELdYhj007960; Wed, 14 Jun 2006 14:39:34 -0700
From: Bill Fenner <fenner@research.att.com>
Message-Id: <200606142139.k5ELdYhj007960@bright.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: "Janet Plato" <techgrrl@gmail.com>
References: <3870C46029D1F945B1472F170D2D979001013067@de01exm64.ds.mot.com>
	<200606062107.k56L70dE002035@workhorse.brookfield.occnc.com>
	<af0dc42c0606061553i1d33b76ek60f02cba03c8cae7@mail.gmail.com>
Date: Wed, 14 Jun 2006 14:39:34 -0700
Versions: dmail (linux) 2.7/makemail 2.14
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org


Janet,

  My apologies for taking so long to reply.

>I hate to make people retread old issues, but I am curious
>what experiences have made people want to ditch the
>rigor of RFC 1264.

One problem is that it's not particularly clear what's
a routing protocol.  Should l2vpn and l3vpn's developments
be held to these standards?  How about forces?  vrrp?
"It should be obvious" until it's not and it's just a
matter of judgement.  Is something a routing protocol
because it's developed in the routing area?  Is something
not a routing protocol because it's developed outside the
routing area?

It also takes away our ability to specify things that we
know we'll need but just not yet - e.g., 4 byte ASes
languished for a few years waiting for implementations;
it's easy to imagine some IPv6 extensions that might
trivially be specified ("carry the address in 16 bytes
instead of 4") but not standardized because of these rules.
Imagine the conflicting requirements: IESG says you must
support IPv6, and security; 1264 says that if it's not
implemented it can't be standardized; you have a MUST and
a MUST NOT meeting, which is the immovable object and
which is the irresistable force?

>If anyone if favor can provide pointers to materials, or summations
>of their personal experiences with RFC1264 making things needlessly
>difficult I would be interested.

I've heard that people look at writing up implementation reports as:
1) make-work
2) a snapshot of implementation status at a point in time
   which may be used against you in the future -- e.g.,
   "The implementation report says that vendor C doesn't
    implement feature foo, but vendor J does, so let's use
    that in our purchasing decision".

So even for something that's implemented, it can be hard to get
an implementation report.

  Bill

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Wed Jun 14 18:21:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fqdjd-00087c-0T; Wed, 14 Jun 2006 18:21:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fqdjb-00081i-IF; Wed, 14 Jun 2006 18:21:11 -0400
Received: from m106.maoz.com ([205.167.76.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fqdjb-0003sd-3r; Wed, 14 Jun 2006 18:21:11 -0400
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.13.6/8.13.6) with ESMTP id k5EMLAI0010810;
	Wed, 14 Jun 2006 15:21:10 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.13.6/8.12.11/Submit) id k5EML6q4010809;
	Wed, 14 Jun 2006 15:21:06 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using
	-f
Date: Wed, 14 Jun 2006 15:21:06 -0700
From: David Meyer <dmm@1-4-5.net>
To: routing-discussion@ietf.org
Message-ID: <20060614222106.GA10790@1-4-5.net>
Mime-Version: 1.0
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I find your lack of faith disturbing." -- Darth Vader,
	Star Wars Episode IV.
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
Cc: iab@ietf.org
Subject: Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2003786287=="
Errors-To: routing-discussion-bounces@ietf.org


--===============2003786287==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="FCuugMFkClbJLl1L"
Content-Disposition: inline


--FCuugMFkClbJLl1L
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

	Folks,
=20
 	The IAB is considering holding a routing and addressing
 	workshop, perhaps in the fall 2006 time frame (see the
 	draft invite below). We're in the process of collecting
 	potential participants, so please pass along any the
 	names of folks that that you think would be productive
 	participants.
=20
 	Thanks,
=20
 	--dmm (for the IAB)
=20
=20
----
 	Greetings,
=20
 	The IAB is sponsoring a workshop on "Scalable Routing and
 	Addressing Architectures for the Internet" in order to
 	foster interchange between the operator, standards,
 	vendor, and research communities on this important
 	topic. You are being invited to participate in this
 	effort.
=20
 	This workshop effort will consist of mailing list
 	discussions in advance of, and after a face to face
 	meeting.  The technical goals of this effort are outlined
 	below.  We believe these are the critical elements to
 	fostering a constructive discussion of important routing
 	and addressing technical work going forward and are
 	soliciting workshop participation to work towards those goals.
=20
 	Should you decide to join us in this workshop, you will
 	be expected to attend the face to face meeting [0],
 	contribute to (and possibly present at) that meeting, as
 	well as follow and participate in the mailing list
 	discussions.=20
=20
 	The most important objective of the workshop is to foster
 	and encourage innovative thinking in an area where there
 	has been little fundamental change for the last twelve
 	years. As such, the primary goals of the workshop include
 	the following two items: =20
=20
 	(i).	Produce a concise problem statement that will
 		serve as the input to future work on this
 		topic. This problem statement will include, among
 		other things, a list of the problems with the
 		current routing and addressing architecture.=20
 		These include (but are not limited to):
=20
 		- The difficulty in changing provider due to
 		  PA/CIDR addressing schemes=20
=20
 		- The lack of effective multi-homing support
=20
 		- Limited capability to protect against either
 		  the spoofing of individual host IP addresses or
 		  entire IP address blocks  =20
=20
 		- The limited ability to secure the routing
 		  system itself, and
=20
 	(ii).	Produce a prioritized list of requirements, all
 		of which must be met by a next generation routing
 		and addressing architecture. A sample list might
 		include (in no particular order): =20
=20
 		- Retaining the connectionless datagram model of
 		  IP routing
=20
 		- Allow users (small and large) to freely switch
 		  between providers without substantial service
 		  interruption=20
=20
 		- Include survival of higher-layer connections
 		  and associations when connectivity to
 		  individual providers changes=20
=20
 		- Allow both users and ISPs to influence path
 		  selection according to traffic management and
 		  classification requirements
=20
 		- Provide better support for mobility and nomadicity
=20
 	        - Provide architected instrumentation facilities
=20
 		- Allow at least one-to-many multicast
=20
 		- Prevent source address spoofing
=20
 		- Provide a rational economic basis for deployment
=20
 		- Secure the routing infrastructure, including
 		  the authentication of updates and the
 		  unauthorized injection of information into the
 		  routing system =20
=20
 		- Define scalability requirements for a next
 		  generation routing system=20
 =20
 		- Have architected transition mechanisms
 		  and be incrementally deployable (where possible)
=20
 	During the workshop, scribes will be assigned to
 	summarize the discussion. Post-workshop, scribes will be
 	expected to participate in finalizing the workshop
 	report. All participants will be expected to review the
 	draft workshop report before publication.=20
=20
 	The workshop is <date, <logistics.
=20
 	Please reply within the next week indicating your
 	willingness to participate in this workshop. Please
 	indicate whether (and to what extent) you'd be able to
 	participate (we'd like an explicit 'no' if you will not
 	be able to), and what you feel is your area of
 	expertise. If you can not participate, please suggest
 	potential alternatives or substitutes. =20
=20
 [0]	Attendees will also need to arrange and pay for their own
 	travel and accommodations.



--FCuugMFkClbJLl1L
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFEkIvSORgD1qCZ2KcRAj0VAJ4nPUpdziZuxEk5zOQARO8DIOplMwCfQbdQ
PMeFkPJRmRsh84QOU0D+JBY=
=JIbO
-----END PGP SIGNATURE-----

--FCuugMFkClbJLl1L--


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

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion

--===============2003786287==--




From routing-discussion-bounces@ietf.org Wed Jun 14 23:39:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fqihq-0001Cd-SS; Wed, 14 Jun 2006 23:39:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fqiho-0001CY-Ro
	for routing-discussion@ietf.org; Wed, 14 Jun 2006 23:39:41 -0400
Received: from ug-out-1314.google.com ([66.249.92.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fqihl-0002kF-Gm
	for routing-discussion@ietf.org; Wed, 14 Jun 2006 23:39:40 -0400
Received: by ug-out-1314.google.com with SMTP id m3so741192uge
	for <routing-discussion@ietf.org>; Wed, 14 Jun 2006 20:39:36 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=BZ5pc3Hhxk6fhxzCXK1IlSIjcCKXDiiLWoc2Fkf6S1rexRWm1+tye2T8fbF2Lte6NUFNkoD65No5v3ZaIpkD7Bm6bWa88NWT+GEHOMlfZhnrGd4+JRP5NW/Rv4HMShv+NL3/zoe1W/KPpiu0dt57IBqaND1vaJ6VA3ZPyxMTxN4=
Received: by 10.78.57.11 with SMTP id f11mr421762hua;
	Wed, 14 Jun 2006 20:39:36 -0700 (PDT)
Received: by 10.78.49.17 with HTTP; Wed, 14 Jun 2006 20:39:36 -0700 (PDT)
Message-ID: <af0dc42c0606142039x3e4bb5abkd51e18b6e073b2ab@mail.gmail.com>
Date: Wed, 14 Jun 2006 22:39:36 -0500
From: "Janet Plato" <techgrrl@gmail.com>
To: "Bill Fenner" <fenner@research.att.com>
In-Reply-To: <200606142139.k5ELdYhj007960@bright.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <3870C46029D1F945B1472F170D2D979001013067@de01exm64.ds.mot.com>
	<200606062107.k56L70dE002035@workhorse.brookfield.occnc.com>
	<af0dc42c0606061553i1d33b76ek60f02cba03c8cae7@mail.gmail.com>
	<200606142139.k5ELdYhj007960@bright.research.att.com>
X-Spam-Score: 1.9 (+)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

Thanks Bill,

I needed to chew on this a little bit before replying.  I can definitely
see how implementation experience, when written into an RFC,
should be obviously a snapshot in time, but could end up being
used against one later.  As for the issue of defining a routing protocol
vs non-routing protocol for RFC 1246 purposes, it *seems*
obvious to me, which usually means I have not thought it through.
;-)

It seems that RFC2026 provides one stop shopping for standards
approvals, and makes the desirability of operational experience
abundantly clear.

You've sold me.

Cheers,

Janet Plato

On 6/14/06, Bill Fenner <fenner@research.att.com> wrote:
>
> Janet,
>
>   My apologies for taking so long to reply.
>
> >I hate to make people retread old issues, but I am curious
> >what experiences have made people want to ditch the
> >rigor of RFC 1264.
>
> One problem is that it's not particularly clear what's
> a routing protocol.  Should l2vpn and l3vpn's developments
> be held to these standards?  How about forces?  vrrp?
> "It should be obvious" until it's not and it's just a
> matter of judgement.  Is something a routing protocol
> because it's developed in the routing area?  Is something
> not a routing protocol because it's developed outside the
> routing area?
>
> It also takes away our ability to specify things that we
> know we'll need but just not yet - e.g., 4 byte ASes
> languished for a few years waiting for implementations;
> it's easy to imagine some IPv6 extensions that might
> trivially be specified ("carry the address in 16 bytes
> instead of 4") but not standardized because of these rules.
> Imagine the conflicting requirements: IESG says you must
> support IPv6, and security; 1264 says that if it's not
> implemented it can't be standardized; you have a MUST and
> a MUST NOT meeting, which is the immovable object and
> which is the irresistable force?
>
> >If anyone if favor can provide pointers to materials, or summations
> >of their personal experiences with RFC1264 making things needlessly
> >difficult I would be interested.
>
> I've heard that people look at writing up implementation reports as:
> 1) make-work
> 2) a snapshot of implementation status at a point in time
>    which may be used against you in the future -- e.g.,
>    "The implementation report says that vendor C doesn't
>     implement feature foo, but vendor J does, so let's use
>     that in our purchasing decision".
>
> So even for something that's implemented, it can be hard to get
> an implementation report.
>
>   Bill
>

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 15 05:04:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fqnlp-0006Na-HZ; Thu, 15 Jun 2006 05:04:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fqnlm-0006LH-Kb
	for routing-discussion@ietf.org; Thu, 15 Jun 2006 05:04:06 -0400
Received: from [2001:1af8:2:5::2] (helo=sequoia.muada.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fqnlm-0003gl-A9
	for routing-discussion@ietf.org; Thu, 15 Jun 2006 05:04:06 -0400
Received: from [IPv6:2001:1af8:6::20a:95ff:fef5:246e] (alumange.muada.com
	[IPv6:2001:1af8:6:0:20a:95ff:fef5:246e]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id k5F92ghX094875
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO)
	for <routing-discussion@ietf.org>;
	Thu, 15 Jun 2006 11:02:43 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v750)
Content-Transfer-Encoding: 7bit
Message-Id: <B767855C-EC80-4D52-A7F1-B02FE3214286@muada.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: routing-discussion@ietf.org
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Thu, 15 Jun 2006 11:03:53 +0200
X-Mailer: Apple Mail (2.750)
X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00,ILJQX_SUBJ_HUH 
	autolearn=no version=3.0.2
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on sequoia.muada.com
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Subject: Re Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

David Meyer wrote:

>  	The IAB is considering holding a routing and addressing
>  	workshop, perhaps in the fall 2006 time frame (see the
>  	draft invite below). We're in the process of collecting
>  	potential participants, so please pass along any the
>  	names of folks that that you think would be productive
>  	participants.

I would be interested in participating, time and money permitting,  
but productiveness is of course in the eye of the beholder. I do have  
a few remarks about the text of the draft invite, though. Hope you  
don't mind...

Mostly, I'm afraid that considering such a wide assortment of  
problems may prevent any one problem from getting the attention that  
it deserves. Also, thinking about these problems is in very different  
stages. For instance, we've talked for _years_ about multihoming, and  
the shim6 wg is now trying to come up with a solution. It's true that  
the general opinion about this solution isn't entirely favorable, but  
would it do much good to go through all of this again now that shim6  
is firmly on track but doesn't have any concrete results yet? The  
opposite is true of:

>  		- Limited capability to protect against either
>  		  the spoofing of individual host IP addresses or
>  		  entire IP address blocks

[I'm assuming in data packets as opposed to in routing]

Unless I really don't follow the right mailing lists (always  
possible, there are only 24 hours in the day after all) nobody has  
seriously tried to actually solve this issue, all efforts have been  
about detecting/tracing the offending packets.

I do think this is a very worthwhile problem to work on, both because  
it represents a very real problem area in today's internet, and  
because it seems possible to actually accomplish something. (I'm  
thinking along the line of having  routers or midleboxes with  
powerful crypto hardware do proxy IPsec AH verification.) But does it  
have much to do with routing?

>  		- Allow users (small and large) to freely switch
>  		  between providers without substantial service
>  		  interruption

Do we consider renumbering a possibility here, or do we assume stable  
addressing when moving from one ISP to the next?

>  		- Provide better support for mobility and nomadicity

Again: in routing?

>  		- Define scalability requirements for a next
>  		  generation routing system

Is it a useful exercise to try to define _how_ scalable the routing  
system needs to be exactly? It has to be as scalable as possible. But  
even if we come up with some magic routing system that scales O(1) we  
still have to put all those millions or billions of routes into FIBs  
which stops being fun when you get the electricity bill.

My thinking about what needs to happen with inter-domain routing is  
that we can learn a lot from intra-AS behavior of BGP (iBGP). The  
routers at the edge of the AS aggregate information, and transmit it  
without modification to other routers in the AS over iBGP. So iBGP  
takes care of distributing prefix information, and he actual path  
selection is left up to other mechanisms more suitable for that task,  
i.e., generally a link state protocol such as OSPF or IS-IS. If we  
can extend this model to an area larger than a single AS we can  
drastically increase inter-domain routing performance, within that  
area at least. Obviously the size of the area where link state (like)  
decision making happens needs to be smaller than the entire internet.

(I was working up to a rant about what's wrong with BGP but I'll  
forego boring you with that in my first message and leave it as an  
exercise for the reader.)

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 15 09:59:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FqsNW-0002T1-PF; Thu, 15 Jun 2006 09:59:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FqsNU-0002Sv-Oa
	for routing-discussion@ietf.org; Thu, 15 Jun 2006 09:59:20 -0400
Received: from m106.maoz.com ([205.167.76.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FqsNT-0000Yc-AS
	for routing-discussion@ietf.org; Thu, 15 Jun 2006 09:59:20 -0400
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.13.6/8.13.6) with ESMTP id k5FDxIT5024243;
	Thu, 15 Jun 2006 06:59:18 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.13.6/8.12.11/Submit) id k5FDxIkK024242;
	Thu, 15 Jun 2006 06:59:18 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using
	-f
Date: Thu, 15 Jun 2006 06:59:18 -0700
From: David Meyer <dmm@1-4-5.net>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Message-ID: <20060615135918.GC24194@1-4-5.net>
References: <B767855C-EC80-4D52-A7F1-B02FE3214286@muada.com>
Mime-Version: 1.0
In-Reply-To: <B767855C-EC80-4D52-A7F1-B02FE3214286@muada.com>
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I find your lack of faith disturbing." -- Darth Vader,
	Star Wars Episode IV.
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Cc: routing-discussion@ietf.org
Subject: Re: Re Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0323604882=="
Errors-To: routing-discussion-bounces@ietf.org


--===============0323604882==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="H8ygTp4AXg6deix2"
Content-Disposition: inline


--H8ygTp4AXg6deix2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jun 15, 2006 at 11:03:53AM +0200, Iljitsch van Beijnum wrote:
> David Meyer wrote:
>=20
> > 	The IAB is considering holding a routing and addressing
> > 	workshop, perhaps in the fall 2006 time frame (see the
> > 	draft invite below). We're in the process of collecting
> > 	potential participants, so please pass along any the
> > 	names of folks that that you think would be productive
> > 	participants.
>=20
> I would be interested in participating, time and money permitting, =20
> but productiveness is of course in the eye of the beholder. I do have =20
> a few remarks about the text of the draft invite, though. Hope you =20
> don't mind...
>=20
> Mostly, I'm afraid that considering such a wide assortment of =20
> problems may prevent any one problem from getting the attention that =20
> it deserves. Also, thinking about these problems is in very different =20
> stages. For instance, we've talked for _years_ about multihoming, and =20
> the shim6 wg is now trying to come up with a solution. It's true that =20
> the general opinion about this solution isn't entirely favorable, but =20
> would it do much good to go through all of this again now that shim6 =20
> is firmly on track but doesn't have any concrete results yet? The =20
> opposite is true of:
>=20
> > 		- Limited capability to protect against either
> > 		  the spoofing of individual host IP addresses or
> > 		  entire IP address blocks
>=20
> [I'm assuming in data packets as opposed to in routing]
>=20
> Unless I really don't follow the right mailing lists (always =20
> possible, there are only 24 hours in the day after all) nobody has =20
> seriously tried to actually solve this issue, all efforts have been =20
> about detecting/tracing the offending packets.
>=20
> I do think this is a very worthwhile problem to work on, both because =20
> it represents a very real problem area in today's internet, and =20
> because it seems possible to actually accomplish something. (I'm =20
> thinking along the line of having  routers or midleboxes with =20
> powerful crypto hardware do proxy IPsec AH verification.) But does it =20
> have much to do with routing?
>=20
> > 		- Allow users (small and large) to freely switch
> > 		  between providers without substantial service
> > 		  interruption
>=20
> Do we consider renumbering a possibility here, or do we assume stable =20
> addressing when moving from one ISP to the next?
>=20
> > 		- Provide better support for mobility and nomadicity
>=20
> Again: in routing?
>=20
> > 		- Define scalability requirements for a next
> > 		  generation routing system
>=20
> Is it a useful exercise to try to define _how_ scalable the routing =20
> system needs to be exactly? It has to be as scalable as possible. But =20
> even if we come up with some magic routing system that scales O(1) we =20
> still have to put all those millions or billions of routes into FIBs =20
> which stops being fun when you get the electricity bill.
>=20
> My thinking about what needs to happen with inter-domain routing is =20
> that we can learn a lot from intra-AS behavior of BGP (iBGP). The =20
> routers at the edge of the AS aggregate information, and transmit it =20
> without modification to other routers in the AS over iBGP. So iBGP =20
> takes care of distributing prefix information, and he actual path =20
> selection is left up to other mechanisms more suitable for that task, =20
> i.e., generally a link state protocol such as OSPF or IS-IS. If we =20
> can extend this model to an area larger than a single AS we can =20
> drastically increase inter-domain routing performance, within that =20
> area at least. Obviously the size of the area where link state (like) =20
> decision making happens needs to be smaller than the entire internet.
>=20
> (I was working up to a rant about what's wrong with BGP but I'll =20
> forego boring you with that in my first message and leave it as an =20
> exercise for the reader.)


	Iljitsch,

	Thanks for the input (much appreciated). I'll fold it
	into the materials I have.

	Dave

=09

--H8ygTp4AXg6deix2
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFEkWe2ORgD1qCZ2KcRAoaxAKCDIj6UqFheqDBlN4CPRdRmtOEdYwCeJSPL
6Le1kDg7MCBbt9lBMis85Tw=
=NTs/
-----END PGP SIGNATURE-----

--H8ygTp4AXg6deix2--


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

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion

--===============0323604882==--




From routing-discussion-bounces@ietf.org Thu Jun 15 10:33:46 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fqsun-0002VM-8d; Thu, 15 Jun 2006 10:33:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fqsum-0002VC-1b
	for routing-discussion@ietf.org; Thu, 15 Jun 2006 10:33:44 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fqsuj-0003Gr-CH
	for routing-discussion@ietf.org; Thu, 15 Jun 2006 10:33:44 -0400
Received: from [10.0.0.51] by consulintel.es (MDaemon.PRO.v8.1.4.R)
	with ESMTP id md50001870874.msg
	for <routing-discussion@ietf.org>; Thu, 15 Jun 2006 16:32:10 +0200
User-Agent: Microsoft-Entourage/11.2.3.060209
Date: Thu, 15 Jun 2006 16:33:29 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <routing-discussion@ietf.org>
Message-ID: <C0B73C59.16D5E6%jordi.palet@consulintel.es>
Thread-Topic: Re Possible IAB workshop on routing and addressing participants?
Thread-Index: AcaQiKtE6hIbo/x7EdqsfwANky3PwA==
In-Reply-To: <20060615135918.GC24194@1-4-5.net>
Mime-version: 1.0
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:060615:routing-discussion@ietf.org::UhiZll4cZkkVap/S:000000000000000000000000000000000022D8
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: routing-discussion@ietf.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.consulintel.es
X-Spam-Status: No, score=-4.7 required=4.7 tests=BAYES_00,MIME_QP_LONG_LINE 
	autolearn=ham version=3.0.4
X-Spam-Level: 
X-Spam-Processed: consulintel.es, Thu, 15 Jun 2006 16:32:11 +0200
X-MDAV-Processed: consulintel.es, Thu, 15 Jun 2006 16:32:14 +0200
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Subject: Re Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

Hi David,

We have a new project, funded by the European Commission, which will
officially start next July 1st, working on this.

The project is called RiNG (Routing in Next Generation).

The project partners include some well known people in IETF, such as Geoff
Huston, Kurtis, Marcelo Bagnulo, Pekka Savola, Tim Chown, Stig Venaas,
Iljitsch and myself.

Obviously we will be very interesting in taking a very active part on this
work and we can make very strong effort, so if there is any way we can get
involved, in addition to participating in the workshop itself, we will be
very happy to know ASAP and make sure to coordinate our agendas so we don't
miss anything.

I've included below a short abstract of the project.

Regards,
Jordi

The goal of RiNG is to support the coordination, study and analysis of
routing protocols on the Internet and to determine and understand the
challenges ahead, considering the current and future expected Internet
growth, leading to proposals for novel approaches towards the evolution of
routing.

Towards this end the project comprises an expert group, which will be open
to the participation of other experts by means of meetings and other
collaboration means, leading to a broader community =B3think tank=B2 on the
topic, forming a kind of =B3Routing Cluster=B2, including not only experts from
other relevant IST projects, but also other international related
activities.

The project will analyze and keep track of the state of the art in
standardization and policy, survey the users and service providers, and
propose further alternative related research and innovation strategies to
address the challenges.

By means of the different activities, the project will seek to foster,
increase and support European participation in the related
pre-standardization, standardization and policy process, dissemination of
the results and monitor those developments.

The project proposed research and innovation strategies, most probably, will
require further standardization and policy-making, so the project will need
to find a community consensus, for the development and implementation of the
project results (by means external to the project).

Consequently, the project objectives are:

1.    Coordinate a community =B3think tank=B2 on routing aspects (Routing
Cluster), providing operational support for the organization of open working
meetings and other collaboration tools, such as an email exploder and web
site.

2.    Surveying both ISP and user (site) requirements for routing in the
next generation of networks.

3.    Analyze the related state of the art in standardization and policy
versus the user/ISP perceived requirements.

4.    Development of research and innovation strategies for inter-domain
routing evolution.

5.    Disseminate the project and related results, including the relevant
standardization and policy activities.






**********************************************
The IPv6 Portal: http://www.ipv6tf.org

Bye 6Bone. Hi, IPv6 !
http://www.ipv6day.org

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 15 10:38:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FqszV-0004cf-5o; Thu, 15 Jun 2006 10:38:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FqszU-0004ca-6z
	for routing-discussion@ietf.org; Thu, 15 Jun 2006 10:38:36 -0400
Received: from m106.maoz.com ([205.167.76.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FqszT-0003sp-OT
	for routing-discussion@ietf.org; Thu, 15 Jun 2006 10:38:36 -0400
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.13.6/8.13.6) with ESMTP id k5FEcORd026313;
	Thu, 15 Jun 2006 07:38:24 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.13.6/8.12.11/Submit) id k5FEcMxI026311;
	Thu, 15 Jun 2006 07:38:22 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using
	-f
Date: Thu, 15 Jun 2006 07:38:21 -0700
From: David Meyer <dmm@1-4-5.net>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Message-ID: <20060615143818.GA25999@1-4-5.net>
References: <20060615135918.GC24194@1-4-5.net>
	<C0B73C59.16D5E6%jordi.palet@consulintel.es>
Mime-Version: 1.0
In-Reply-To: <C0B73C59.16D5E6%jordi.palet@consulintel.es>
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I find your lack of faith disturbing." -- Darth Vader,
	Star Wars Episode IV.
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Cc: routing-discussion@ietf.org
Subject: Re: Re Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0947363587=="
Errors-To: routing-discussion-bounces@ietf.org


--===============0947363587==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62"
Content-Disposition: inline


--+QahgC5+KEYLbs62
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

	Hey Jordi,

> We have a new project, funded by the European Commission, which will
> officially start next July 1st, working on this.
>=20
> The project is called RiNG (Routing in Next Generation).

	Kurtis mentioned this.

> The project partners include some well known people in IETF, such as Geoff
> Huston, Kurtis, Marcelo Bagnulo, Pekka Savola, Tim Chown, Stig Venaas,
> Iljitsch and myself.
>=20
> Obviously we will be very interesting in taking a very active part on this
> work and we can make very strong effort, so if there is any way we can get
> involved, in addition to participating in the workshop itself, we will be
> very happy to know ASAP and make sure to coordinate our agendas so we don=
't
> miss anything.
>=20
> I've included below a short abstract of the project.
>=20
> Regards,
> Jordi

	Thanks!

	--dmm



>=20
> The goal of RiNG is to support the coordination, study and analysis of
> routing protocols on the Internet and to determine and understand the
> challenges ahead, considering the current and future expected Internet
> growth, leading to proposals for novel approaches towards the evolution of
> routing.
>=20
> Towards this end the project comprises an expert group, which will be open
> to the participation of other experts by means of meetings and other
> collaboration means, leading to a broader community =B3think tank=B2 on t=
he
> topic, forming a kind of =B3Routing Cluster=B2, including not only expert=
s from
> other relevant IST projects, but also other international related
> activities.
>=20
> The project will analyze and keep track of the state of the art in
> standardization and policy, survey the users and service providers, and
> propose further alternative related research and innovation strategies to
> address the challenges.
>=20
> By means of the different activities, the project will seek to foster,
> increase and support European participation in the related
> pre-standardization, standardization and policy process, dissemination of
> the results and monitor those developments.
>=20
> The project proposed research and innovation strategies, most probably, w=
ill
> require further standardization and policy-making, so the project will ne=
ed
> to find a community consensus, for the development and implementation of =
the
> project results (by means external to the project).
>=20
> Consequently, the project objectives are:
>=20
> 1.    Coordinate a community =B3think tank=B2 on routing aspects (Routing
> Cluster), providing operational support for the organization of open work=
ing
> meetings and other collaboration tools, such as an email exploder and web
> site.
>=20
> 2.    Surveying both ISP and user (site) requirements for routing in the
> next generation of networks.
>=20
> 3.    Analyze the related state of the art in standardization and policy
> versus the user/ISP perceived requirements.
>=20
> 4.    Development of research and innovation strategies for inter-domain
> routing evolution.
>=20
> 5.    Disseminate the project and related results, including the relevant
> standardization and policy activities.
>=20
>=20
>=20
>=20
>=20
>=20
> **********************************************
> The IPv6 Portal: http://www.ipv6tf.org
>=20
> Bye 6Bone. Hi, IPv6 !
> http://www.ipv6day.org
>=20
> This electronic message contains information which may be privileged or c=
onfidential. The information is intended to be for the use of the individua=
l(s) named above. If you are not the intended recipient be aware that any d=
isclosure, copying, distribution or use of the contents of this information=
, including attached files, is prohibited.
>=20
>=20
>=20
>=20
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www1.ietf.org/mailman/listinfo/routing-discussion

--+QahgC5+KEYLbs62
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFEkXDaORgD1qCZ2KcRAr2vAJ0YifYrUUIB51IwIyBI/Ct1pTu+bQCfWqWV
trdom64FxQUMbHF1maHGKfE=
=JR5V
-----END PGP SIGNATURE-----

--+QahgC5+KEYLbs62--


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

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion

--===============0947363587==--




From routing-discussion-bounces@ietf.org Thu Jun 15 14:19:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FqwRN-0003VN-EB; Thu, 15 Jun 2006 14:19:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FqwRM-0003VI-OL
	for routing-discussion@ietf.org; Thu, 15 Jun 2006 14:19:36 -0400
Received: from [69.37.59.173] (helo=workhorse.brookfield.occnc.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FqwRL-00036r-Cw
	for routing-discussion@ietf.org; Thu, 15 Jun 2006 14:19:36 -0400
Received: from workhorse.brookfield.occnc.com (localhost [127.0.0.1])
	by workhorse.brookfield.occnc.com (8.13.4/8.13.4) with ESMTP id
	k5FIPMFX020690; Thu, 15 Jun 2006 14:25:22 -0400 (EDT)
	(envelope-from curtis@workhorse.brookfield.occnc.com)
Message-Id: <200606151825.k5FIPMFX020690@workhorse.brookfield.occnc.com>
To: Bill Fenner <fenner@research.att.com>
In-reply-to: Your message of "Wed, 14 Jun 2006 14:39:34 PDT."
	<200606142139.k5ELdYhj007960@bright.research.att.com> 
Date: Thu, 15 Jun 2006 14:25:22 -0400
From: Curtis Villamizar <curtis@occnc.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: routing-discussion@ietf.org
Subject: Re: Obsoleting RFC 1264? 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org


In message <200606142139.k5ELdYhj007960@bright.research.att.com>
Bill Fenner writes:
>  
>  
> Janet,
>  
>   My apologies for taking so long to reply.
>  
> >I hate to make people retread old issues, but I am curious
> >what experiences have made people want to ditch the
> >rigor of RFC 1264.
>  
> One problem is that it's not particularly clear what's
> a routing protocol.  Should l2vpn and l3vpn's developments
> be held to these standards?  How about forces?  vrrp?
> "It should be obvious" until it's not and it's just a
> matter of judgement.  Is something a routing protocol
> because it's developed in the routing area?  Is something
> not a routing protocol because it's developed outside the
> routing area?
>  
> It also takes away our ability to specify things that we
> know we'll need but just not yet - e.g., 4 byte ASes
> languished for a few years waiting for implementations;
> it's easy to imagine some IPv6 extensions that might
> trivially be specified ("carry the address in 16 bytes
> instead of 4") but not standardized because of these rules.
> Imagine the conflicting requirements: IESG says you must
> support IPv6, and security; 1264 says that if it's not
> implemented it can't be standardized; you have a MUST and
> a MUST NOT meeting, which is the immovable object and
> which is the irresistable force?


Yes and IPv6 is the source of a lot of unimplemented junk.  Amazing
how providers argued against such things as link local addresses and
this was standardized and eventually depricated.

With regard to IPv6 IESG is acting like ISO with the OSI protocols.
Standardize anything that seems to be a good idea at the time and
don't worry about implementations let alone interoperability.


> >If anyone if favor can provide pointers to materials, or summations
> >of their personal experiences with RFC1264 making things needlessly
> >difficult I would be interested.
>  
> I've heard that people look at writing up implementation reports as:
> 1) make-work
> 2) a snapshot of implementation status at a point in time
>    which may be used against you in the future -- e.g.,
>    "The implementation report says that vendor C doesn't
>     implement feature foo, but vendor J does, so let's use
>     that in our purchasing decision".
>  
> So even for something that's implemented, it can be hard to get
> an implementation report.
>  
>   Bill


Maybe that's an argument to allow vendor C in your example to insist
the implementation report be updated as features are completed.  It
should be possible to insure that there is nothing to prevent an
update to the implementation report.

Besides reality is customers read the RFP response freshly prepared
just for them, not a year old RFC (or many years old).  When making
multi-million dollar purchases customers also don't take anyones word
for it and test the products themselves and do field trials, etc.

Curtis

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 15 15:18:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FqxMj-0007Nm-No; Thu, 15 Jun 2006 15:18:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FqxMi-0007NY-Rl; Thu, 15 Jun 2006 15:18:52 -0400
Received: from imo-m22.mx.aol.com ([64.12.137.3] helo=imo-m22.mail.aol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FqxMi-000089-HT; Thu, 15 Jun 2006 15:18:52 -0400
Received: from HeinerHummel@aol.com
	by imo-m22.mx.aol.com (mail_out_v38_r7.5.) id z.4cf.187e0ac (48600);
	Thu, 15 Jun 2006 15:18:33 -0400 (EDT)
From: HeinerHummel@aol.com
Message-ID: <4cf.187e0ac.31c30c88@aol.com>
Date: Thu, 15 Jun 2006 15:18:32 EDT
To: dmm@1-4-5.net, routing-discussion@ietf.org
MIME-Version: 1.0
X-Mailer: 9.0 SE for Windows sub 5005
X-Spam-Flag: NO
X-Spam-Score: 0.3 (/)
X-Scan-Signature: a8041eca2a724d631b098c15e9048ce9
Cc: iab@ietf.org
Subject: Re: Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0736531682=="
Errors-To: routing-discussion-bounces@ietf.org


--===============0736531682==
Content-Type: multipart/alternative;
	boundary="-----------------------------1150399112"


-------------------------------1150399112
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

 
Some notes  inline. 
- The difficulty in changing provider due to
PA/CIDR addressing schemes 
 

HH:Why is the (primary )AS# not part of the destination address ?  


- The lack of effective  multi-homing support
HH: ...then multi-homing would become a  non-issue.

- Limited  capability to protect against either
the  spoofing of individual host IP addresses or
entire IP address blocks   
HH:IMHO: just the other way around.All anti-spoofing protocols just  
document: we are unable to do any better routing than Dijkstra.  If a packet arrives 
where Dijkstra does not let us expect it to  arrive...

- The limited  ability to secure the routing
system  itself, and
 
HH:For the same reason.

(ii).     Produce a prioritized list of requirements, all
of which must be met by a next generation routing
and addressing architecture. A sample list might
include (in no particular order):  

-  Retaining the connectionless datagram model of
IP routing
HH: I have been in favor of connections  for many years but  meanwhile have 
realized that pure IP forwarding can outperform any connection-TE  . Not only 
RSVP but also ATM and what is left over:MPLS. Where  is  IP Forwarding TE 
today? No WG for this :-( 
TE is not a synonym for MPLS !
 
The IETF
- Allow users (small  and large) to freely switch
between  providers without substantial service
interruption 

- Include survival of  higher-layer connections
and associations  when connectivity to
individual providers  changes 


HH:Can this be clarified?

- Allow both users and ISPs  to influence path
selection according to  traffic management and
classification  requirements

- Provide better support for  mobility and nomadicity

HH: Just remember the ATM Forum solutions!

-  Provide architected instrumentation facilities

HH:Yes, for ICANN itself.

- Allow at least one-to-many  multicast
HH:None of the existing multicast solutions can be taken seriously.Its only  
playing games. None is able to transmit soccer world  championship  matches.

- Prevent source  address spoofing
HH: At first enable better routing than  Dijkstra

- Provide a rational  economic basis for deployment
HH: especially for multicast.

- Secure the routing  infrastructure, including
the  authentication of updates and the
unauthorized injection of information into the
routing system  

- Define  scalability requirements for a next
generation routing system 
HH:replace BGP ! replace IPv6 !

Heiner  Hummel    


-------------------------------1150399112
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DUS-ASCII">
<META content=3D"MSHTML 6.00.2900.2912" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=20=
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
e_document=20
face=3DArial color=3D#000000 size=3D2>
<DIV>
<DIV><FONT style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000=
000=20
size=3D2>Some notes=20
inline.&nbsp;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
- The difficulty in changing provider due to<BR>&nbsp; &nbsp; &nbsp; &nbsp;=20
&nbsp; PA/CIDR addressing schemes&nbsp;</FONT></DIV>
<DIV>&nbsp;</DIV><FONT style=3D"BACKGROUND-COLOR: transparent" face=3DArial=20
color=3D#000000 size=3D2></FONT></DIV>
<DIV><FONT style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000=
000=20
size=3D2>HH:Why is the (primary )AS# not part of the destination address ?=20
<DIV><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - The lack of effect=
ive=20
multi-homing support</DIV>
<DIV>HH: ...then multi-homing would become a=20
non-issue.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Limited=20
capability to protect against either<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; t=
he=20
spoofing of individual host IP addresses or<BR>&nbsp; &nbsp; &nbsp; &nbsp;=20
&nbsp; entire IP address blocks&nbsp;&nbsp; </DIV>
<DIV>HH:IMHO: just the other way around.All anti-spoofing protocols just=20
document: we are&nbsp;unable to&nbsp;do&nbsp;any better routing than Dijkstr=
a.=20
If a packet arrives where Dijkstra does not let us expect it to=20
arrive...<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - The limited=20
ability to secure the routing<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; system=20
itself, and</DIV>
<DIV>&nbsp;</DIV>
<DIV>HH:For the same reason.<BR><BR>&nbsp;&nbsp;&nbsp; (ii).&nbsp; &nbsp;=20
Produce a prioritized list of requirements, all<BR>&nbsp; &nbsp; &nbsp; &nbs=
p;=20
of which must be met by a next generation routing<BR>&nbsp; &nbsp; &nbsp; &n=
bsp;=20
and addressing architecture. A sample list might<BR>&nbsp; &nbsp; &nbsp; &nb=
sp;=20
include (in no particular order):&nbsp; <BR><BR>&nbsp; &nbsp; &nbsp; &nbsp;=20=
-=20
Retaining the connectionless datagram model of<BR>&nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; IP routing</DIV>
<DIV>HH: I have been in favor of&nbsp;connections&nbsp; for many years but=20
meanwhile have realized that pure IP forwarding can outperform any connectio=
n-TE=20
. Not only&nbsp;RSVP&nbsp;but also ATM and what is left over:MPLS. Where=20
is&nbsp; IP Forwarding TE today? No WG for this :-( </DIV>
<DIV>TE is not a synonym for MPLS !</DIV>
<DIV>&nbsp;</DIV>
<DIV>The IETF<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Allow users (s=
mall=20
and large) to freely switch<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; between=20
providers without substantial service<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
interruption <BR><BR>&nbsp; &nbsp; &nbsp; &nbsp; - Include survival of=20
higher-layer connections<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; and associati=
ons=20
when connectivity to<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; individual provid=
ers=20
changes </DIV>
<DIV><BR>&nbsp;</DIV>
<DIV>HH:Can this be clarified?</DIV>
<DIV><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Allow both users and I=
SPs=20
to influence path<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; selection according=20=
to=20
traffic management and<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; classification=20
requirements<BR><BR>&nbsp; &nbsp; &nbsp; &nbsp; - Provide better support for=
=20
mobility and nomadicity<BR></DIV>
<DIV>HH: Just remember the ATM Forum solutions!</DIV>
<DIV><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20=
-=20
Provide architected instrumentation facilities<BR></DIV>
<DIV>HH:Yes, for ICANN itself.</DIV>
<DIV><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Allow at least one-to-=
many=20
multicast</DIV>
<DIV>HH:None of the existing multicast solutions can be taken seriously.Its=20=
only=20
playing games. None is able to transmit soccer world&nbsp; championship=20
matches.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Prevent source=20
address spoofing</DIV>
<DIV>HH:&nbsp;At first enable better routing than=20
Dijkstra<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Provide a ratio=
nal=20
economic basis for deployment</DIV>
<DIV>HH:&nbsp;especially for multicast.</DIV>
<DIV><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Secure the routing=20
infrastructure, including<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the=20
authentication of updates and the<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
unauthorized injection of information into the<BR>&nbsp; &nbsp; &nbsp; &nbsp=
;=20
&nbsp; routing system&nbsp; <BR><BR>&nbsp; &nbsp; &nbsp; &nbsp; - Define=20
scalability requirements for a next<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20
generation routing system </DIV>
<DIV>HH:replace BGP ! replace IPv6 !<BR>&nbsp;&nbsp;<BR>&nbsp;Heiner=20
Hummel&nbsp;&nbsp;&nbsp; </DIV></FONT></DIV></FONT></BODY></HTML>

-------------------------------1150399112--


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

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion

--===============0736531682==--




From routing-discussion-bounces@ietf.org Thu Jun 15 16:32:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FqyW8-0004DP-OB; Thu, 15 Jun 2006 16:32:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FqyW6-0004DC-La; Thu, 15 Jun 2006 16:32:38 -0400
Received: from [69.37.59.173] (helo=workhorse.brookfield.occnc.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FqyW6-0006Rt-6W; Thu, 15 Jun 2006 16:32:38 -0400
Received: from workhorse.brookfield.occnc.com (localhost [127.0.0.1])
	by workhorse.brookfield.occnc.com (8.13.4/8.13.4) with ESMTP id
	k5FKcK0W022615; Thu, 15 Jun 2006 16:38:20 -0400 (EDT)
	(envelope-from curtis@workhorse.brookfield.occnc.com)
Message-Id: <200606152038.k5FKcK0W022615@workhorse.brookfield.occnc.com>
To: HeinerHummel@aol.com
In-reply-to: Your message of "Thu, 15 Jun 2006 15:18:32 EDT."
	<4cf.187e0ac.31c30c88@aol.com> 
Date: Thu, 15 Jun 2006 16:38:20 -0400
From: Curtis Villamizar <curtis@occnc.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48
Cc: dmm@1-4-5.net, iab@ietf.org, routing-discussion@ietf.org
Subject: Re: Possible IAB workshop on routing and addressing participants? 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org


We need to distinguish between layer-8 problems and technical
problems.  No amount of protocol work will solve some layer-8
problems.


In message <4cf.187e0ac.31c30c88@aol.com>
HeinerHummel@aol.com writes:
>  
>  
> Some notes  inline. 
> - The difficulty in changing provider due to
> PA/CIDR addressing schemes 
>  
> HH:Why is the (primary )AS# not part of the destination address ?  


In effect it is.  The address prefix is inherited from the provider,
unless a customer is large enough to have PI addresses.

Adding the AS number leaves you with the exact same problem.  To
change providers you'd have to change the end system addresses to
change the AS number which is exactly the problem.

Clearly NAT is not the solution.

DHCP helps.  Not having sysadmins that wire in IP addresses as a means
to support security helps.

With DHCP and dynamic DNS with DHCP is this just a technically solved
problem with dumb end users using persolution techniques too widely.


> - The lack of effective  multi-homing support
> HH: ...then multi-homing would become a  non-issue.


Multihoming is an issue but for small end sites like a small business,
it is impossible to multihome.  Just calling your MSO and ILEC and
asking for CATV IP and DSL IP won't get you the redundancy you want.

For that matter getting them to do a competent job of providing
DNS-inverse is hard enough.  Look at my subnet for an example - DNS
forward and inverse lookups don't match nothing I tell SBC aka AT&T so
far has helped.  Last answer I got was - we don't do DNS inverse for
DSL.


> - Limited  capability to protect against either
> the  spoofing of individual host IP addresses or
> entire IP address blocks   
> HH:IMHO: just the other way around.All anti-spoofing protocols just  
> document: we are unable to do any better routing than Dijkstra.  If a packet arrives 
> where Dijkstra does not let us expect it to  arrive...


There was discussion among providers to filter SA based on routes for
that address being advertised for known single homed customers.  Some
may do this but not enough.  The closer to the core the harder it is
to be sure not to break things.  As I mentioned above the closer to
the edge the lower the clue factor of the providers (and often
customer).  So the practice is not widespread.


> - The limited  ability to secure the routing
> system  itself, and
>  
> HH:For the same reason.


Check the work of the RPS WG.  Providers have not registered in a RR
and made use of an RR in sufficient number.  For providers who use the
RR there is some improvement.  At the very least that provider can be
made immune to route spoofing of its own customers and of peers that
also use the registry.

Some of the proposals to try to solve the problem with crytographic
authentication embedded in the routing information have proven
infeasible (or at least impractical) at ISP scale so far.


> (ii).     Produce a prioritized list of requirements, all
> of which must be met by a next generation routing
> and addressing architecture. A sample list might
> include (in no particular order):  
>  
> -  Retaining the connectionless datagram model of
> IP routing
> HH: I have been in favor of connections  for many years but  meanwhile have 
> realized that pure IP forwarding can outperform any connection-TE  . Not only 
> RSVP but also ATM and what is left over:MPLS. Where  is  IP Forwarding TE 
> today? No WG for this :-( 
> TE is not a synonym for MPLS !
>  
> The IETF


Please get real.


> - Allow users (small  and large) to freely switch
> between  providers without substantial service
> interruption 
>  
> - Include survival of  higher-layer connections
> and associations  when connectivity to
> individual providers  changes 
>  
> HH:Can this be clarified?


Don't nuke open TCP connections on provider transition.  IE: having
DHCP dole out new addresses after failover doesn't cut it.  That is
about as good as a small business could do if using IP offerings
intended for consumers and clueless small business.


> - Allow both users and ISPs  to influence path
> selection according to  traffic management and
> classification  requirements


This is a bad idea.  QoS has proven to be an unsellable service in an
Internet which is already quite good if the QoS will cost more.


> - Provide better support for  mobility and nomadicity
>  
> HH: Just remember the ATM Forum solutions!


You must be joking.


> -  Provide architected instrumentation facilities
>  
> HH:Yes, for ICANN itself.


The requirement seems like it touches on Layer-8 problems rather than
any technical issue.

You comment doesn't seem related.


> - Allow at least one-to-many  multicast
> HH:None of the existing multicast solutions can be taken seriously.Its only  
> playing games. None is able to transmit soccer world  championship  matches.
>  
> - Prevent source  address spoofing
> HH: At first enable better routing than  Dijkstra
>  
> - Provide a rational  economic basis for deployment
> HH: especially for multicast.
>  
> - Secure the routing  infrastructure, including
> the  authentication of updates and the
> unauthorized injection of information into the
> routing system  
>  
> - Define  scalability requirements for a next
> generation routing system 
> HH:replace BGP ! replace IPv6 !
>  
> Heiner  Hummel    


btw- This isn't the meeting, its a call for comments on the
invitation.

Curtis

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Wed Jun 21 04:58:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FsyXr-0005Fc-1X; Wed, 21 Jun 2006 04:58:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FsyXp-0005FM-5S
	for routing-discussion@ietf.org; Wed, 21 Jun 2006 04:58:41 -0400
Received: from bay19-f1.bay19.hotmail.com ([64.4.53.51] helo=hotmail.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FsyXm-0001p4-MZ
	for routing-discussion@ietf.org; Wed, 21 Jun 2006 04:58:41 -0400
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Wed, 21 Jun 2006 01:58:35 -0700
Message-ID: <BAY19-F16BED2D39F0AE6988D0F29E840@phx.gbl>
Received: from 209.170.95.146 by by19fd.bay19.hotmail.msn.com with HTTP;
	Wed, 21 Jun 2006 08:58:30 GMT
X-Originating-IP: [202.184.41.200]
X-Originating-Email: [sakal_woman@hotmail.com]
X-Sender: sakal_woman@hotmail.com
From: "Diana Asnani" <sakal_woman@hotmail.com>
To: routing-discussion@ietf.org
Bcc: 
Date: Wed, 21 Jun 2006 16:58:30 +0800
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
X-OriginalArrivalTime: 21 Jun 2006 08:58:35.0413 (UTC)
	FILETIME=[E1093450:01C69510]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Subject: Routing problem...
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

Hi,

i have a problem with adding this route in my routing table:
route add -net 202.184.41.0 netmask 255.255.255.0 gw 192.168.206.1
It says SIOCADDRT: Network  isunreachable

INSPEM PC:
IP: 192.168.202.1
gateway: 192.168.202.14

PC ROUTER:
eth0 ( downlink communication & connected to a VLAN port)
IP: 192.168.206.1
gateway : 192.168.206.14
eth1 ( uplink communcation & connected to the Internet)
IP: 202.184.41.41
gateway : 202.184.41.3

I could ping 192.168.206.1 from 192.168.202.1 only when i am connected to 
the vlan port. But i could not ping to 202.184.41.41...i need to access 
202.184.41.41 to have access to the Internet...

I'm still new to this...hope anyone could help...thanks...

Diana
I

_________________________________________________________________
Get an advanced look at the new version of MSN Messenger. 
http://messenger.msn.com.my/Beta/Default.aspx


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Wed Jun 21 09:17:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ft2aF-0000Mg-80; Wed, 21 Jun 2006 09:17:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ft2aE-0000HE-3e; Wed, 21 Jun 2006 09:17:26 -0400
Received: from mercury.lcs.mit.edu ([18.26.0.122])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ft2aC-0002I6-Qg; Wed, 21 Jun 2006 09:17:26 -0400
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178)
	id 9F899872D9; Wed, 21 Jun 2006 09:17:24 -0400 (EDT)
To: routing-discussion@ietf.org
Message-Id: <20060621131724.9F899872D9@mercury.lcs.mit.edu>
Date: Wed, 21 Jun 2006 09:17:24 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: iab@ietf.org, jnc@mercury.lcs.mit.edu
Subject: Re: Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

    > From: David Meyer <dmm@1-4-5.net>

    > The IAB is considering holding a routing and addressing workshop

I've been musing about this for a while, and I have some comments. (I'd
also be interested in what people think of my musings...)


The chief one I have is that I feel that in some sense you've all got the cart
before the horse; the focus in the thing you sent out seems to be on *what*
we're going to deploy, and not on *how* we're going to deploy it - and the
latter frankly seems, to me, by far the harder problem.

(Indeed, we have a major worked example that it's far easier to design a whole
new protocol, than get it deployed and adopted. But other than taking a
lesson, let's avoid that rat-hole. We also have worked examples that it's not
that hard to design technically viable new routing/addressing architectures;
indeed, I would take position that what a new routing/addressing architecture
should look like is a "done deal" - no doubt to nobody's surprise! :-)

It's precisely because a number of us have been down that "design a new
routing/addressing architecture" path that I focus on "how" rather than
"what"; the past experience is that it's basically easy to work out the
design (including a viable interoperability/deployment path, that's not what
I'm talking about), far eaiser than it is to get it adopted.

So I think the biggest problem, and the one any workshop should focus on, is
identifying a viable path to get something deployed. (I'm assuming here that
the desired technical end is *not* merely a few minor tweaks to the existing
system - the IETF WG process would be adequate for that.) Let me try and make
this clearer by giving some brief thoughts on the matter.


I think the one essential is to get many (most?) of the major ISP's on board.
I don't think there's a viable deployment path which starts with deployment in
customer sites; maybe I'm wrong, and maybe there is, and if so that's
something we could discuss. But let's assume for the moment we need the ISP's
- and also that once it's deployed there, it will naturally filter down to the
rest of the network. So you have to sit down with the ISP's and get some
agreement from them on what a new system should do (since nobody's going to
buy a pig in a poke, and sign up for whatever you produce, no matter what it
is). How is that going to happen? Will they be able to come to a consensus?
How can you make sure they are really signed up to do it, and not just merely
giving lip service?

Then you get to the issue of "how do you protect the interests of the other
network stakeholders, especially the users". The ISP's are gonna want to dial
things to the end that makes their life easiest, and who cares if life's tough
for everyone else. How do we control that?

Then there's getting it implemented, by all the major router vendors. If you
have many ISP's signed up, maybe this solves itself - if the ISP's are willing
to prefer boxes that have the new thing in it, and put their money where their
mouths are, then the vendors will do it out of self-preservation.  But maybe
we need something more formal - some group of entities might have to cough up
money to fund an "open-source" implementation which the vendors can integrate,
perhaps. Anway, that's another issue (although less critical than the others).


I think you all probably get the drift by now. Without a viable plan to get it
adopted, a new design is IMO a waste of time - or a PhD project for some grad
student who needs a topic.

I have some comments on the specific contents of the proposed call, but since
this is already long I'll send this off, and follow along with them later.

	Noel

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Wed Jun 21 11:33:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ft4hj-0006aK-Pp; Wed, 21 Jun 2006 11:33:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ft4hi-0006aB-3g
	for routing-discussion@ietf.org; Wed, 21 Jun 2006 11:33:18 -0400
Received: from iceblock01.troposnetworks.com ([12.108.168.187]
	helo=iceblock01.tropos.com) by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1Ft4hf-0000Du-52
	for routing-discussion@ietf.org; Wed, 21 Jun 2006 11:33:18 -0400
Received: (qmail 28712 invoked from network); 21 Jun 2006 15:28:23 -0000
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on iceblock01
X-Spam-Level: 
X-Spam-Status: No, score=-104.3 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; 21 Jun 2006 15:28:21 -0000
Received: from LIPC ([192.168.1.161]) by ca-bay-exch-01.tropos.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 21 Jun 2006 08:35:08 -0700
From: "Tony Li" <tli@tropos.com>
To: "'Noel Chiappa'" <jnc@mercury.lcs.mit.edu>, <routing-discussion@ietf.org>
Date: Wed, 21 Jun 2006 08:33:08 -0700
Message-ID: <001e01c69547$ff4ab2e0$a101a8c0@tropos.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcaVNoBNXQgjyqqDSU6On9NnGXZatwAEUzbA
In-Reply-To: <20060621131724.9F899872D9@mercury.lcs.mit.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-OriginalArrivalTime: 21 Jun 2006 15:35:08.0462 (UTC)
	FILETIME=[46CC5CE0:01C69548]
X-Antivirus: Scanned by Tropos Antivirus 1.0.4
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f
Cc: iab@ietf.org
Subject: RE: Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: tony.li@tony.li
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org


Noel,

I think that getting the ISPs signed up is relatively easy.  I believe
that most of them see the writing on the wall with regard to the
remaining lifetime of v4 and would welcome an alternative to v6.

Tony
 

> -----Original Message-----
> From: Noel Chiappa [mailto:jnc@mercury.lcs.mit.edu] 
> Sent: Wednesday, June 21, 2006 6:17 AM
> To: routing-discussion@ietf.org
> Cc: iab@ietf.org; jnc@mercury.lcs.mit.edu
> Subject: Re: Possible IAB workshop on routing and addressing 
> participants?
> 
>     > From: David Meyer <dmm@1-4-5.net>
> 
>     > The IAB is considering holding a routing and addressing workshop
> 
> I've been musing about this for a while, and I have some 
> comments. (I'd
> also be interested in what people think of my musings...)
> 
> 
> The chief one I have is that I feel that in some sense you've 
> all got the cart
> before the horse; the focus in the thing you sent out seems 
> to be on *what*
> we're going to deploy, and not on *how* we're going to deploy 
> it - and the
> latter frankly seems, to me, by far the harder problem.
> 
> (Indeed, we have a major worked example that it's far easier 
> to design a whole
> new protocol, than get it deployed and adopted. But other 
> than taking a
> lesson, let's avoid that rat-hole. We also have worked 
> examples that it's not
> that hard to design technically viable new routing/addressing 
> architectures;
> indeed, I would take position that what a new 
> routing/addressing architecture
> should look like is a "done deal" - no doubt to nobody's surprise! :-)
> 
> It's precisely because a number of us have been down that 
> "design a new
> routing/addressing architecture" path that I focus on "how" 
> rather than
> "what"; the past experience is that it's basically easy to 
> work out the
> design (including a viable interoperability/deployment path, 
> that's not what
> I'm talking about), far eaiser than it is to get it adopted.
> 
> So I think the biggest problem, and the one any workshop 
> should focus on, is
> identifying a viable path to get something deployed. (I'm 
> assuming here that
> the desired technical end is *not* merely a few minor tweaks 
> to the existing
> system - the IETF WG process would be adequate for that.) Let 
> me try and make
> this clearer by giving some brief thoughts on the matter.
> 
> 
> I think the one essential is to get many (most?) of the major 
> ISP's on board.
> I don't think there's a viable deployment path which starts 
> with deployment in
> customer sites; maybe I'm wrong, and maybe there is, and if so that's
> something we could discuss. But let's assume for the moment 
> we need the ISP's
> - and also that once it's deployed there, it will naturally 
> filter down to the
> rest of the network. So you have to sit down with the ISP's 
> and get some
> agreement from them on what a new system should do (since 
> nobody's going to
> buy a pig in a poke, and sign up for whatever you produce, no 
> matter what it
> is). How is that going to happen? Will they be able to come 
> to a consensus?
> How can you make sure they are really signed up to do it, and 
> not just merely
> giving lip service?
> 
> Then you get to the issue of "how do you protect the 
> interests of the other
> network stakeholders, especially the users". The ISP's are 
> gonna want to dial
> things to the end that makes their life easiest, and who 
> cares if life's tough
> for everyone else. How do we control that?
> 
> Then there's getting it implemented, by all the major router 
> vendors. If you
> have many ISP's signed up, maybe this solves itself - if the 
> ISP's are willing
> to prefer boxes that have the new thing in it, and put their 
> money where their
> mouths are, then the vendors will do it out of 
> self-preservation.  But maybe
> we need something more formal - some group of entities might 
> have to cough up
> money to fund an "open-source" implementation which the 
> vendors can integrate,
> perhaps. Anway, that's another issue (although less critical 
> than the others).
> 
> 
> I think you all probably get the drift by now. Without a 
> viable plan to get it
> adopted, a new design is IMO a waste of time - or a PhD 
> project for some grad
> student who needs a topic.
> 
> I have some comments on the specific contents of the proposed 
> call, but since
> this is already long I'll send this off, and follow along 
> with them later.
> 
> 	Noel
> 
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www1.ietf.org/mailman/listinfo/routing-discussion
> 



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Wed Jun 21 12:28:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ft5Z5-0000PX-Sm; Wed, 21 Jun 2006 12:28:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ft5Z4-0000Lb-0x; Wed, 21 Jun 2006 12:28:26 -0400
Received: from mercury.lcs.mit.edu ([18.26.0.122])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ft5Z2-00055k-Qz; Wed, 21 Jun 2006 12:28:26 -0400
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178)
	id 87EB386AE0; Wed, 21 Jun 2006 12:28:24 -0400 (EDT)
To: routing-discussion@ietf.org
Message-Id: <20060621162824.87EB386AE0@mercury.lcs.mit.edu>
Date: Wed, 21 Jun 2006 12:28:24 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: iab@ietf.org, jnc@mercury.lcs.mit.edu
Subject: RE: Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

    > From: "Tony Li" <tli@tropos.com>

    > I believe that most of [the ISPs] them see the writing on the wall with
    > regard to the remaining lifetime of v4 and would welcome an alternative
    > to v6.

I'm not sure I quite see the connection here, between "routing" and "IPv6".

After all, the routing architecture (and, potentially, its namespace) aren't
really connected to the internetwork packet format. (Interestingly, IPv4 made
the choice to make the router<->router packet format be identical to the
host<->router packet format - a congruency a new routing architecture
wouldn't necessarily have to retain.) There have certainly been past plans to
deploy an entirely new routing/addressing architecture, while retaining the
existing internetwork packet format, and we could certainly do the same
again here.

Also, IPv6 is currently using basically the same routing/addressing
architecture as IPv4 (modulo the proposed Multi6 stuff). Or is that your
point (that they are getting tired of the existing Ipv4/v6 routing
architecture)?

	Noel

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Wed Jun 21 13:33:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ft6Zo-0003uA-MV; Wed, 21 Jun 2006 13:33:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ft6Zn-0003tl-1q; Wed, 21 Jun 2006 13:33:15 -0400
Received: from [2001:1af8:2:5::2] (helo=sequoia.muada.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ft6Zm-0004pb-NZ; Wed, 21 Jun 2006 13:33:14 -0400
Received: from [IPv6:2001:1af8:6::20a:95ff:fef5:246e] (alumange.muada.com
	[IPv6:2001:1af8:6:0:20a:95ff:fef5:246e]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id k5LHVrAn049251
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO);
	Wed, 21 Jun 2006 19:31:54 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <001e01c69547$ff4ab2e0$a101a8c0@tropos.com>
References: <001e01c69547$ff4ab2e0$a101a8c0@tropos.com>
Mime-Version: 1.0 (Apple Message framework v750)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A06AE2F4-D49E-44CF-9AB0-16A785997F20@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Wed, 21 Jun 2006 19:33:10 +0200
To: tony.li@tony.li
X-Mailer: Apple Mail (2.750)
X-Spam-Status: No, score=-1.3 required=5.0 tests=AWL, BAYES_00, ILJQX_SUBJ_HUH 
	autolearn=no version=3.0.2
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on sequoia.muada.com
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: iab@ietf.org, 'Noel Chiappa' <jnc@mercury.lcs.mit.edu>,
	routing-discussion@ietf.org
Subject: Re: Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

On 21-jun-2006, at 17:33, Tony Li wrote:

> I think that getting the ISPs signed up is relatively easy.  I believe
> that most of them see the writing on the wall with regard to the
> remaining lifetime of v4 and would welcome an alternative to v6.

It took us about a decade to get to this point with IPv6. Is it  
reasonable to assume that we could do a similar project significantly  
faster? We are scheduled to run out of IPv4 address space within 7 to  
9 years or so.

Getting ISPs to do _anything_ isn't easy, as anyone who has ever  
called an ISP support number can attest to. I see two things that can  
get a new routing paradigm or protocol adopted: if it can run on  
existing routers where the existing way of doing things would require  
investing in new hardware, and good security. But only if the new  
thing can do IPv4 and IPv6 more or less as it exists today, I don't  
think radically new addressing will fly with operators any time soon.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Wed Jun 21 17:14:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtA1h-00080n-5m; Wed, 21 Jun 2006 17:14:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtA1f-00080f-Nm
	for routing-discussion@ietf.org; Wed, 21 Jun 2006 17:14:15 -0400
Received: from kahuna.telstra.net ([2001:360::4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtA1e-0006bV-20
	for routing-discussion@ietf.org; Wed, 21 Jun 2006 17:14:15 -0400
Received: from gihm3.apnic.net (dhcp23.potaroo.net [203.10.60.23])
	by kahuna.telstra.net (8.12.11/8.12.11) with ESMTP id k5LLDIPT007172;
	Thu, 22 Jun 2006 07:13:22 +1000 (EST) (envelope-from gih@apnic.net)
Message-Id: <6.2.0.14.2.20060622063717.031982c0@kahuna.telstra.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
Date: Thu, 22 Jun 2006 06:43:49 +1000
To: tony.li@tony.li, "'Noel Chiappa'" <jnc@mercury.lcs.mit.edu>,
	<routing-discussion@ietf.org>
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <001e01c69547$ff4ab2e0$a101a8c0@tropos.com>
References: <20060621131724.9F899872D9@mercury.lcs.mit.edu>
	<001e01c69547$ff4ab2e0$a101a8c0@tropos.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: 
Subject: RE: Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

At 01:33 AM 22/06/2006, Tony Li wrote:

>Noel,
>
>I think that getting the ISPs signed up is relatively easy.  I believe
>that most of them see the writing on the wall with regard to the
>remaining lifetime of v4 and would welcome an alternative to v6.
>
>Tony
>


I'd be wary of such generalizations. Such prescient ISPs are not exactly 
commonplace, and in various parts of the world the ISPs appear to in future 
denial and are still deploying mass-market IPv4-based products that have no 
escape clause whatsoever when the current technology components are no 
longer available at today's price points. You are indeed fortunate to be in 
a locale where you appear to have such well-informed ISPs.

I personally think getting the ISP's to sign up to technology change is 
going to be challenging. One of the more illustrative examples of just how 
challenging is the 4-byte ASN transition plan, where the essence of the 
transition is to tunnel and translate simultaneously across the currently 
deployed BGP base. The assumption in that plan is that the existing base 
will change _nothing_ in their deployed environments any time soon (or even 
any time later!).

regards,

    Geoff





_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Wed Jun 21 19:18:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtBy0-0007rM-5u; Wed, 21 Jun 2006 19:18:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtBxz-0007r5-CO; Wed, 21 Jun 2006 19:18:35 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FtBxx-0006wo-UP; Wed, 21 Jun 2006 19:18:35 -0400
Received: from ams-core-1.cisco.com ([144.254.224.150])
	by ams-iport-1.cisco.com with ESMTP; 22 Jun 2006 01:17:30 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k5LNHGrq029457; 
	Thu, 22 Jun 2006 01:17:20 +0200 (MEST)
Received: from lwood-wxp01.cisco.com (ams3-vpn-dhcp4660.cisco.com
	[10.61.82.51])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id AAA16197;
	Thu, 22 Jun 2006 00:17:09 +0100 (BST)
Message-Id: <7.0.1.0.0.20060622001532.02af8bc8@surrey.ac.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Thu, 22 Jun 2006 00:17:08 +0100
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
From: Lloyd Wood <L.Wood@surrey.ac.uk>
In-Reply-To: <20060621162824.87EB386AE0@mercury.lcs.mit.edu>
References: <20060621162824.87EB386AE0@mercury.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Cc: iab@ietf.org, jnc@mercury.lcs.mit.edu, routing-discussion@ietf.org
Subject: RE: Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

At Wednesday 21/06/2006 12:28 -0400, Noel Chiappa wrote:
>  (Interestingly, IPv4 made
>the choice to make the router<->router packet format be identical to the
>host<->router packet format - a congruency a new routing architecture
>wouldn't necessarily have to retain.)

The ATM NNI and UNI interfaces didn't teach any lessons?

L.


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 22 08:18:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtO7I-0005bH-2i; Thu, 22 Jun 2006 08:17:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtO7G-0005am-NA; Thu, 22 Jun 2006 08:16:58 -0400
Received: from mtagate3.uk.ibm.com ([195.212.29.136])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FtO7F-0007kE-AP; Thu, 22 Jun 2006 08:16:58 -0400
Received: from d06nrmr1407.portsmouth.uk.ibm.com
	(d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185])
	by mtagate3.uk.ibm.com (8.13.6/8.13.6) with ESMTP id k5MCGseo088682
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 22 Jun 2006 13:16:55 +0100
Received: from d06av01.portsmouth.uk.ibm.com (d06av01.portsmouth.uk.ibm.com
	[9.149.37.212])
	by d06nrmr1407.portsmouth.uk.ibm.com (8.13.6/NCO/VER7.0) with ESMTP id
	k5MCIBMI066384
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 22 Jun 2006 13:18:12 +0100
Received: from d06av01.portsmouth.uk.ibm.com (loopback [127.0.0.1])
	by d06av01.portsmouth.uk.ibm.com (8.12.11.20060308/8.13.3) with ESMTP
	id k5MCGpfu017866; Thu, 22 Jun 2006 13:16:51 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
	by d06av01.portsmouth.uk.ibm.com (8.12.11.20060308/8.12.11) with ESMTP
	id k5MCGpKD017839; Thu, 22 Jun 2006 13:16:51 +0100
Received: from zurich.ibm.com (sig-9-145-248-46.de.ibm.com [9.145.248.46])
	by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id OAA16816;
	Thu, 22 Jun 2006 14:16:49 +0200
Message-ID: <449A8A31.8040807@zurich.ibm.com>
Date: Thu, 22 Jun 2006 14:16:49 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Tony Li <tli@tropos.com>
References: <FF22D8DA3CC478438280A45A7CFAD27A01190A23@ca-bay-exch-01.tropos.com>
In-Reply-To: <FF22D8DA3CC478438280A45A7CFAD27A01190A23@ca-bay-exch-01.tropos.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: iab@ietf.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>,
	routing-discussion@ietf.org
Subject: Re: Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

Tony Li wrote:
>  
> 
> 
>>Also, IPv6 is currently using basically the same routing/addressing
>>architecture as IPv4 (modulo the proposed Multi6 stuff). Or 
>>is that your
>>point (that they are getting tired of the existing Ipv4/v6 routing
>>architecture)?
> 
> 
> 
> The latter.  The recent ARIN discussions plus the response to shim6 make
> it clear that ISPs have a concern about a tractable multihoming solution
> that simply cannot be supported in the current v6 routing architecture.
> They are clearly open to alternatives.

I think that the correct discussion is indeed about IP routing architecture
not about IP version numbers or address formats.

I don't want to restart the shim6 wars here, but one of the reasoms shim6
came out they way it did was precisely because the IP routing architecture
is the way it is. So if you don't like shim6, you pretty much have to
change the routing architecture.

     Brian

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 22 09:31:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtPGT-0003fP-Qk; Thu, 22 Jun 2006 09:30:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtPGS-0003WE-Cd
	for routing-discussion@ietf.org; Thu, 22 Jun 2006 09:30:32 -0400
Received: from mercury.lcs.mit.edu ([18.26.0.122])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtPGR-0004YB-4k
	for routing-discussion@ietf.org; Thu, 22 Jun 2006 09:30:32 -0400
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178)
	id 32FEE872E3; Thu, 22 Jun 2006 09:30:25 -0400 (EDT)
To: routing-discussion@ietf.org
Message-Id: <20060622133025.32FEE872E3@mercury.lcs.mit.edu>
Date: Thu, 22 Jun 2006 09:30:25 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: jnc@mercury.lcs.mit.edu
Subject: RE: Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

<I'll package up a couple of replies together here, and drop the CC to the
IAB because these are specific technical issues...>


    > From: Iljitsch van Beijnum <iljitsch@muada.com>

    > I see two things that can get a new routing paradigm or protocol
    > adopted: if it can run on existing routers where the existing way of
    > doing things would require investing in new hardware

That's certainly an interesting point to take into account, although I'd
be interested in hearing from people exactly how critical it is.

    > But only if the new thing can do IPv4 and IPv6 more or less as it
    > exists today, I don't think radically new addressing will fly with
    > operators any time soon.

By "radically new addressing [won't] fly", do you mean that you don't think
any other *packet format* would be supported, or that they would not support
deployment of a new namespace intended for use in path computations (i.e.
migrating some of the functionality of the exisiting "IP address space"
namespace to a new namespace, just as HIP does, albeit at the other end).


    > From: Lloyd Wood <L.Wood@surrey.ac.uk>

    >> IPv4 made the choice to make the router<->router packet format be
    >> identical to the host<->router packet format - a congruency a new
    >> routing architecture wouldn't necessarily have to retain.

    > The ATM NNI and UNI interfaces didn't teach any lessons?

Did ATM have specific experiences with separate packet formats in the two
contexts that's has something useful to teach us? (BTW, the fact that NNI and
PNI as complete ensembles differ isn't that remarkable; in IP, the *overall*
host-router interface is different from the router-router interface -
e.g. hosts get redirects, routers don't; routers talk routing protocols to
each other, but they don't do that to hosts; etc, etc, etc.)

I'm not sure if this is what you were meaning, but I don't think you can read
much about the correctness of any particular engineering decision (e.g.
NNI/UNI differences) from the fact that ATM didn't succeed. I used to have
this line for reporters about ATM that everyone you talked to who felt that
ATM was a bad idea had something they would point to as a fatal flaw - and
they were all different! So there's not necessarily any connection between
the failure of ATM as a system, and any particular engineering point.

	Noel

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 22 09:36:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtPLa-0007sd-0v; Thu, 22 Jun 2006 09:35:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtPLY-0007sX-OH
	for routing-discussion@ietf.org; Thu, 22 Jun 2006 09:35:48 -0400
Received: from mercury.lcs.mit.edu ([18.26.0.122])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtPLX-00052X-IU
	for routing-discussion@ietf.org; Thu, 22 Jun 2006 09:35:48 -0400
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178)
	id 65A2386AF6; Thu, 22 Jun 2006 09:35:47 -0400 (EDT)
To: routing-discussion@ietf.org
Message-Id: <20060622133547.65A2386AF6@mercury.lcs.mit.edu>
Date: Thu, 22 Jun 2006 09:35:47 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

    > From: Brian E Carpenter <brc@zurich.ibm.com>

    > I think that the correct discussion is indeed about IP routing
    > architecture not about IP version numbers or address formats.

To the extent that the names the routing calculations care about are being
carried around in addresses, addresses are, by definition, on the table.
(If people are unhappy about that, they shouldn't have defined a packet
format where it's true.)


    > one of the reasoms shim6 came out they way it did was precisely because
    > the IP routing architecture is the way it is.

Can you expand on that? (The detail of how shim6 operates have drifted
out of my mind, alas...)

    > So if you don't like shim6, you pretty much have to change the routing
    > architecture.

I gather there was a lot of resistance in some operator forum (something to
do with NANOG, maybe?) to the whole concept of shim6. Some people were
pushing for that old canard, PI-space, as an alternative, and got a certain
amount of support for it. What's the currrent community take on shim6?

	Noel

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 22 09:53:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtPcN-0003HX-I1; Thu, 22 Jun 2006 09:53:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtPcM-0003HS-Iy
	for routing-discussion@ietf.org; Thu, 22 Jun 2006 09:53:10 -0400
Received: from smtp02.uc3m.es ([163.117.136.122])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtPcL-0005x8-9H
	for routing-discussion@ietf.org; Thu, 22 Jun 2006 09:53:10 -0400
Received: from smtp02.uc3m.es (localhost [127.0.0.1])
	by localhost.uc3m.es (Postfix) with ESMTP
	id 0A7719630F; Thu, 22 Jun 2006 15:53:08 +0200 (CEST)
Received: from [163.117.203.126] (unknown [163.117.203.126])
	by smtp02.uc3m.es (Postfix) with ESMTP
	id 5E958962C0; Thu, 22 Jun 2006 15:53:07 +0200 (CEST)
In-Reply-To: <20060622133547.65A2386AF6@mercury.lcs.mit.edu>
References: <20060622133547.65A2386AF6@mercury.lcs.mit.edu>
Mime-Version: 1.0 (Apple Message framework v624)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <706447edf96089c207096b4b2d41ff38@it.uc3m.es>
Content-Transfer-Encoding: quoted-printable
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
Date: Thu, 22 Jun 2006 16:53:06 +0300
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
X-Mailer: Apple Mail (2.624)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: routing-discussion@ietf.org
Subject: Re: Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

Hi Noel,

El 22/06/2006, a las 16:35, Noel Chiappa escribi=F3:
>
> Can you expand on that? (The detail of how shim6 operates have drifted
> out of my mind, alas...)
>

in a nutshell, the multihomed sites obtain PA blocks form their ISPs=20
and each host within the multihomed site configures as many addresses=20
as prefixes are available (one per prefix)
The shim6 protocol is an e2e protocol to support changing the locators=20=

used to exchange packet on the wire while always presenting a constant=20=

indetifier pair to the upper layers, in order to preserve=20
communications through outages that result in prefixes/addresses being=20=

unreachable. The hosts select the locators to use based on an e2e=20
failure detection protocol.

The shim layer located at the two endpoints then translate the received=20=

locator to the initial identifier pair

(note that no new namespace has be used for the identifier, just one of=20=

the available locators is used as identifier)

Regards, marcelo


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 22 10:02:30 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtPlK-0003OI-UV; Thu, 22 Jun 2006 10:02:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ft6PH-00039h-4N
	for routing-discussion@ietf.org; Wed, 21 Jun 2006 13:22:23 -0400
Received: from webmail.tropos.com ([12.108.168.187] helo=iceblock01.tropos.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Ft6PF-00044m-Nv
	for routing-discussion@ietf.org; Wed, 21 Jun 2006 13:22:23 -0400
Received: (qmail 5773 invoked from network); 21 Jun 2006 17:17:25 -0000
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on iceblock01
X-Spam-Level: 
X-Spam-Status: No, score=-104.3 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; 21 Jun 2006 17:17:24 -0000
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: Wed, 21 Jun 2006 10:22:14 -0700
Message-ID: <FF22D8DA3CC478438280A45A7CFAD27A01190A23@ca-bay-exch-01.tropos.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Possible IAB workshop on routing and addressing participants?
Thread-Index: AcaVUAWLETqQbW0pRFu6PcLrFYgUnQABu/UQ
From: "Tony Li" <tli@tropos.com>
To: "Noel Chiappa" <jnc@mercury.lcs.mit.edu>,
	<routing-discussion@ietf.org>
X-Antivirus: Scanned by Tropos Antivirus 1.0.4
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
X-Mailman-Approved-At: Thu, 22 Jun 2006 10:02:25 -0400
Cc: iab@ietf.org
Subject: RE: Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

=20

> Also, IPv6 is currently using basically the same routing/addressing
> architecture as IPv4 (modulo the proposed Multi6 stuff). Or=20
> is that your
> point (that they are getting tired of the existing Ipv4/v6 routing
> architecture)?


The latter.  The recent ARIN discussions plus the response to shim6 make
it clear that ISPs have a concern about a tractable multihoming solution
that simply cannot be supported in the current v6 routing architecture.
They are clearly open to alternatives.

Tony

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 22 10:46:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtQRX-0004m4-9z; Thu, 22 Jun 2006 10:46:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtQRW-0004g1-3F
	for routing-discussion@ietf.org; Thu, 22 Jun 2006 10:46:02 -0400
Received: from mtagate4.uk.ibm.com ([195.212.29.137])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtQRT-0003KI-Kb
	for routing-discussion@ietf.org; Thu, 22 Jun 2006 10:46:02 -0400
Received: from d06nrmr1407.portsmouth.uk.ibm.com
	(d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185])
	by mtagate4.uk.ibm.com (8.13.6/8.13.6) with ESMTP id k5MEjwnS038818
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <routing-discussion@ietf.org>; Thu, 22 Jun 2006 14:45:58 GMT
Received: from d06av03.portsmouth.uk.ibm.com (d06av03.portsmouth.uk.ibm.com
	[9.149.37.213])
	by d06nrmr1407.portsmouth.uk.ibm.com (8.13.6/NCO/VER7.0) with ESMTP id
	k5MEkwjc113494
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <routing-discussion@ietf.org>; Thu, 22 Jun 2006 15:47:06 +0100
Received: from d06av03.portsmouth.uk.ibm.com (loopback [127.0.0.1])
	by d06av03.portsmouth.uk.ibm.com (8.12.11.20060308/8.13.3) with ESMTP
	id k5MEjT0h001519
	for <routing-discussion@ietf.org>; Thu, 22 Jun 2006 15:45:29 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
	by d06av03.portsmouth.uk.ibm.com (8.12.11.20060308/8.12.11) with ESMTP
	id k5MEjSPf001507; Thu, 22 Jun 2006 15:45:28 +0100
Received: from zurich.ibm.com (sig-9-146-221-105.de.ibm.com [9.146.221.105])
	by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id QAA42874;
	Thu, 22 Jun 2006 16:45:27 +0200
Message-ID: <449AAD07.8050406@zurich.ibm.com>
Date: Thu, 22 Jun 2006 16:45:27 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
References: <20060622133547.65A2386AF6@mercury.lcs.mit.edu>
In-Reply-To: <20060622133547.65A2386AF6@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: routing-discussion@ietf.org
Subject: Re: Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

Noel Chiappa wrote:
>     > From: Brian E Carpenter <brc@zurich.ibm.com>
> 
>     > I think that the correct discussion is indeed about IP routing
>     > architecture not about IP version numbers or address formats.
> 
> To the extent that the names the routing calculations care about are being
> carried around in addresses, addresses are, by definition, on the table.
> (If people are unhappy about that, they shouldn't have defined a packet
> format where it's true.)
> 
> 
>     > one of the reasoms shim6 came out they way it did was precisely because
>     > the IP routing architecture is the way it is.
> 
> Can you expand on that? (The detail of how shim6 operates have drifted
> out of my mind, alas...)

Well, we assumed that the only scaleable space was PA space and that
the site (hence the hosts in the site) has no control over which
locators are routed via a given ISP or AS, once out of the site's egress
router. So (unlike 8+8) the assumption was the standard Internet one:
a packet may or may not be delivered, and you don't know how it gets
there. Shim6 assumes that model and doesn't break it. Essentially it
synthesizes an EID by picking an arbitrary IP address and using it
as a pseudo-address for the entire session.

>     > So if you don't like shim6, you pretty much have to change the routing
>     > architecture.
> 
> I gather there was a lot of resistance in some operator forum (something to
> do with NANOG, maybe?) to the whole concept of shim6. Some people were
> pushing for that old canard, PI-space, as an alternative, and got a certain
> amount of support for it. What's the currrent community take on shim6?

I won't comment on that - as ex Multi6 co-chair and co-chair of the Shim6
BOF, I'm definitely not neutral, and opinions vary.

    Brian

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 22 11:44:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtRLe-0005wH-DZ; Thu, 22 Jun 2006 11:44:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtRLd-0005wC-7K
	for routing-discussion@ietf.org; Thu, 22 Jun 2006 11:44:01 -0400
Received: from [2001:1af8:2:5::2] (helo=sequoia.muada.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtRLc-0003mX-UT
	for routing-discussion@ietf.org; Thu, 22 Jun 2006 11:44:01 -0400
Received: from [IPv6:2001:1af8:6::20a:95ff:fef5:246e] (alumange.muada.com
	[IPv6:2001:1af8:6:0:20a:95ff:fef5:246e]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id k5MFgdAW074093
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO);
	Thu, 22 Jun 2006 17:42:40 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <20060622133025.32FEE872E3@mercury.lcs.mit.edu>
References: <20060622133025.32FEE872E3@mercury.lcs.mit.edu>
Mime-Version: 1.0 (Apple Message framework v750)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <BA6E8BCF-4121-40C8-A5C3-B8F463F6DC96@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Thu, 22 Jun 2006 17:43:56 +0200
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
X-Mailer: Apple Mail (2.750)
X-Spam-Status: No, score=-1.9 required=5.0 tests=AWL, BAYES_00, ILJQX_SUBJ_HUH 
	autolearn=no version=3.0.2
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on sequoia.muada.com
X-Spam-Score: -2.8 (--)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: routing-discussion@ietf.org
Subject: Re: Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

On 22-jun-2006, at 15:30, Noel Chiappa wrote:

>> I see two things that can get a new routing paradigm or protocol
>> adopted: if it can run on existing routers where the existing way of
>> doing things would require investing in new hardware

> That's certainly an interesting point to take into account,  
> although I'd
> be interested in hearing from people exactly how critical it is.

Opinions differ, of course. Current routing table size related pain  
seems to be lower than at other points since about 1993. And it also  
makes sense that if routing could more easily handle more prefixes,  
more would show up.

>> But only if the new thing can do IPv4 and IPv6 more or less as it
>> exists today, I don't think radically new addressing will fly with
>> operators any time soon.

> By "radically new addressing [won't] fly", do you mean that you  
> don't think
> any other *packet format* would be supported, or that they would  
> not support
> deployment of a new namespace intended for use in path computations  
> (i.e.
> migrating some of the functionality of the exisiting "IP address  
> space"
> namespace to a new namespace, just as HIP does, albeit at the other  
> end).

Yes, for the most part, it's a packet format thing, but new semantics  
for existing address fields may also cause discomfort, see the  
reception of unique site locals with the NANOG crowd.

And let's not forget that there are operators of different kinds.  
ISPs will care greatly about packet formats, since they need silicon  
that understands those packet formats. But people who "operate"  
applications care more about the structure of the addresses, the  
exact packet formats are handled elsewhere. I think it's important to  
view Tony's assessment that operators are open to alternatives in  
that light: many people are very comfortable changing important parts  
of the architecture, just not the ones that they care most about.

The way I see it, the endless debates with multi6 and now shim6 show  
that few people are willing to accept a reduction in functionality or  
comfort within the area of their purview for the greater good. Not  
the best environment for architecture changes.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 22 11:47:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtRP7-0000XX-1t; Thu, 22 Jun 2006 11:47:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtRP5-0000XP-VU; Thu, 22 Jun 2006 11:47:35 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FtRP4-00048e-KS; Thu, 22 Jun 2006 11:47:35 -0400
Received: from ams-core-1.cisco.com ([144.254.224.150])
	by ams-iport-1.cisco.com with ESMTP; 22 Jun 2006 17:47:33 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k5MFlWrq007386; 
	Thu, 22 Jun 2006 17:47:32 +0200 (MEST)
Received: from lwood-wxp01.cisco.com (ams3-vpn-dhcp4660.cisco.com
	[10.61.82.51])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id QAA10203;
	Thu, 22 Jun 2006 16:47:31 +0100 (BST)
Message-Id: <7.0.1.0.0.20060622164600.04297150@surrey.ac.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Thu, 22 Jun 2006 16:47:30 +0100
To: "Sadler, Jonathan B." <Jonathan.Sadler@tellabs.com>
From: Lloyd Wood <L.Wood@surrey.ac.uk>
In-Reply-To: <A1A52203CA93634BA1748887B9993AEA02CB735A@USNVEX1.tellabs-w
	est.tellabsinc.net>
References: <A1A52203CA93634BA1748887B9993AEA02CB735A@USNVEX1.tellabs-west.tellabsinc.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: iab@ietf.org, jnc@mercury.lcs.mit.edu, routing-discussion@ietf.org
Subject: RE: Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

At Thursday 22/06/2006 09:30 -0500, Sadler, Jonathan B. wrote:
>The difference between ATM NNI and UNI is really limited to the
>signaling protocols...  How many of those did really get implemented?

Exactly my point.

Why define two sets of different stuff that won't get implemented?

The approach of developing stuff on multihomed hosts and moving it to 
routers has served IP well.

L.

>If we're looking for examples where difference between NNI and UNI
>signaling did get implemented, it may be better to look at the PSTN (and
>ultimately its scalability, support for multi-homing)...
>
>Jonathan Sadler
>
>-----Original Message-----
>From: Lloyd Wood [mailto:L.Wood@surrey.ac.uk]
>Sent: Wednesday, June 21, 2006 6:17 PM
>To: Noel Chiappa
>Cc: iab@ietf.org; jnc@mercury.lcs.mit.edu; routing-discussion@ietf.org
>Subject: RE: Possible IAB workshop on routing and addressing
>participants?
>
>At Wednesday 21/06/2006 12:28 -0400, Noel Chiappa wrote:
> >  (Interestingly, IPv4 made
> >the choice to make the router<->router packet format be identical to
> >the host<->router packet format - a congruency a new routing
> >architecture wouldn't necessarily have to retain.)
>
>The ATM NNI and UNI interfaces didn't teach any lessons?
>
>L.
>
>
>_______________________________________________
>routing-discussion mailing list
>routing-discussion@ietf.org
>https://www1.ietf.org/mailman/listinfo/routing-discussion
>============================================================
>The information contained in this message may be privileged
>and confidential and protected from disclosure. If the reader
>of this message is not the intended recipient, or an employee
>or agent responsible for delivering this message to the
>intended recipient, you are hereby notified that any reproduction,
>dissemination or distribution of this communication is strictly
>prohibited. If you have received this communication in error,
>please notify us immediately by replying to the message and
>deleting it from your computer. Thank you. Tellabs
>============================================================

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 22 12:34:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtS8V-00038l-SZ; Thu, 22 Jun 2006 12:34:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtS8T-000320-Rw; Thu, 22 Jun 2006 12:34:29 -0400
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 1FtQTf-0004eA-Gl; Thu, 22 Jun 2006 10:48:15 -0400
Received: from mx4.tellabs.com ([204.154.129.57])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1FtQES-0005aU-NY; Thu, 22 Jun 2006 10:32:35 -0400
Received: from usnvwwms2c.hq.tellabs.com (HELO
	USNVEX3.tellabs-west.tellabsinc.net) ([172.23.216.105])
	by mx4.tellabs.com with ESMTP; 22 Jun 2006 14:32:32 +0000
X-SBRS: None
X-IronPort-AV: i="4.06,166,1149465600"; 
	d="scan'208"; a="56361712:sNHT23602000"
Received: from USNVEX1.tellabs-west.tellabsinc.net ([172.23.216.101]) by
	USNVEX3.tellabs-west.tellabsinc.net with Microsoft
	SMTPSVC(6.0.3790.0); Thu, 22 Jun 2006 09:32:31 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 22 Jun 2006 09:30:04 -0500
Message-ID: <A1A52203CA93634BA1748887B9993AEA02CB735A@USNVEX1.tellabs-west.tellabsinc.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Possible IAB workshop on routing and addressing participants?
Thread-Index: AcaViRjeZEVarFGsQWCEFdA09tI68wAfvvYg
From: "Sadler, Jonathan B." <Jonathan.Sadler@tellabs.com>
To: "Lloyd Wood" <L.Wood@surrey.ac.uk>,
	"Noel Chiappa" <jnc@mercury.lcs.mit.edu>
X-OriginalArrivalTime: 22 Jun 2006 14:32:31.0235 (UTC)
	FILETIME=[B1BAC530:01C69608]
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: -2.6 (--)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: iab@ietf.org, jnc@mercury.lcs.mit.edu, routing-discussion@ietf.org
Subject: RE: Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

The difference between ATM NNI and UNI is really limited to the
signaling protocols...  How many of those did really get implemented?

If we're looking for examples where difference between NNI and UNI
signaling did get implemented, it may be better to look at the PSTN (and
ultimately its scalability, support for multi-homing)...

Jonathan Sadler

-----Original Message-----
From: Lloyd Wood [mailto:L.Wood@surrey.ac.uk]=20
Sent: Wednesday, June 21, 2006 6:17 PM
To: Noel Chiappa
Cc: iab@ietf.org; jnc@mercury.lcs.mit.edu; routing-discussion@ietf.org
Subject: RE: Possible IAB workshop on routing and addressing
participants?

At Wednesday 21/06/2006 12:28 -0400, Noel Chiappa wrote:
>  (Interestingly, IPv4 made
>the choice to make the router<->router packet format be identical to=20
>the host<->router packet format - a congruency a new routing=20
>architecture wouldn't necessarily have to retain.)

The ATM NNI and UNI interfaces didn't teach any lessons?

L=2E


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 22 12:56:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtSTj-0006HN-NY; Thu, 22 Jun 2006 12:56:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtSTi-0006H5-Tf
	for routing-discussion@ietf.org; Thu, 22 Jun 2006 12:56:26 -0400
Received: from out3.smtp.messagingengine.com ([66.111.4.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtSTh-0000Xo-LW
	for routing-discussion@ietf.org; Thu, 22 Jun 2006 12:56:26 -0400
Received: from frontend3.internal (frontend3.internal [10.202.2.152])
	by frontend1.messagingengine.com (Postfix) with ESMTP id 75BB9D861E5
	for <routing-discussion@ietf.org>; Thu, 22 Jun 2006 12:56:24 -0400 (EDT)
Received: from web3.messagingengine.com ([10.202.2.212])
	by frontend3.internal (MEProxy); Thu, 22 Jun 2006 12:56:25 -0400
Received: by web3.messagingengine.com (Postfix, from userid 99)
	id 1E29F21AE1; Thu, 22 Jun 2006 12:56:25 -0400 (EDT)
Message-Id: <1150995385.29239.264432974@webmail.messagingengine.com>
X-Sasl-Enc: Uu9Km2D+RdQfSJmzYiylkaLF5Ea4hS/7pKG2SFMiG0yQ 1150995385
From: "Per Heldal" <heldal@eml.cc>
To: routing-discussion@ietf.org
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="ISO-8859-1"
MIME-Version: 1.0
X-Mailer: MIME::Lite 5022  (F2.72; T1.15; A1.62; B3.04; Q3.03)
References: <20060622133547.65A2386AF6@mercury.lcs.mit.edu>
In-Reply-To: <20060622133547.65A2386AF6@mercury.lcs.mit.edu>
Date: Thu, 22 Jun 2006 18:56:25 +0200
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Subject: Re: Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

On Thu, 22 Jun 2006 09:35:47 -0400 (EDT), "Noel Chiappa"
<jnc@mercury.lcs.mit.edu> said:
>=20
> I gather there was a lot of resistance in some operator forum (something
> to
> do with NANOG, maybe?) to the whole concept of shim6. Some people were
> pushing for that old canard, PI-space, as an alternative, and got a
> certain
> amount of support for it. What's the currrent community take on shim6?
>=20

Opinions vary greatly. Some have little confidence with the IAB/IETF due
to the lack of progress in the last 15 years or so and do no longer
believe that a technical solution will be found before v4 reaches EOL.
Old-timers in the community are fed up and newcomers aren't exactly
encouraged to become involved either.=20

Some don't realize that shim6 is only one brick in the brick-work. Many
of the pieces required by the ops community have yet to be defined. Some
examples:

* IGP routing must handle egress-selection in complex networks.

* Site-wide "routing policy controller" that interact with hosts for
dynamic prefix-management (add/remove) and influence prefix/path
selection (traffic management).

* Traffic-management hardware (load-balancers, proxies etc) need some
serious work. Possibly complete re-design.=20=20

These things must be addressed to make shim6 useable for sites with more
than a handful of devices.

>From under my developer-hat i see potential and opportunities. Wearing
my ops-hat I see vapourware, not even an early alpha in sight. In the
real world there are business requirements which we have to create
solutions to either meet or eliminate. Independence from suppliers is
one such requirement. For IP connectivity that means PI-blocks ... in
the absence of alternatives.=20

Is it really a good idea to fully deploy v6 for everybody now? Those who
need it for special purposes (mobile initiatives, various research etc)
should have little problem getting a block under the current policy.
There's no killer-app to drive v6 adoption, nor is there a real
requirement in the market. There's of course the old .gov/gosip crowd
and their army of consultants pushing their v6 ideas, but their
(in)ability in the area of product development was well documented in
the last decade. Maybe some day people in public administration will
realize that each =A2 spent on network research is probably more likely
to generate more value for the public than a $ spent on overpaid network
consultants. I'm all for a PI policy if there is no alternative, but
can't we give the research community as much time as possible and at
least wait until we either have to (no more v4 addresses) or at least
wait till v6 reaches a stage where it is supported by most devices to
the extent that it can be a drop-in replacement for v4?


//per
--=20
  Per Heldal
  http://heldal.eml.cc/


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Thu Jun 22 14:44:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtUAO-0004ld-6B; Thu, 22 Jun 2006 14:44:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtUAM-0004jl-DY
	for routing-discussion@ietf.org; Thu, 22 Jun 2006 14:44:34 -0400
Received: from [2001:1af8:2:5::2] (helo=sequoia.muada.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtUAL-00081U-3i
	for routing-discussion@ietf.org; Thu, 22 Jun 2006 14:44:34 -0400
Received: from [IPv6:2001:1af8:6::20a:95ff:fef5:246e] (alumange.muada.com
	[IPv6:2001:1af8:6:0:20a:95ff:fef5:246e]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id k5MIh8eM077167
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO);
	Thu, 22 Jun 2006 20:43:08 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <449AAD07.8050406@zurich.ibm.com>
References: <20060622133547.65A2386AF6@mercury.lcs.mit.edu>
	<449AAD07.8050406@zurich.ibm.com>
Mime-Version: 1.0 (Apple Message framework v750)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <581200B2-5438-4365-8E6C-C0ED84FF1AC2@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Thu, 22 Jun 2006 20:44:20 +0200
To: Brian E Carpenter <brc@zurich.ibm.com>
X-Mailer: Apple Mail (2.750)
X-Spam-Status: No, score=-1.9 required=5.0 tests=AWL, BAYES_00, ILJQX_SUBJ_HUH 
	autolearn=no version=3.0.2
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on sequoia.muada.com
X-Spam-Score: -2.8 (--)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: routing-discussion@ietf.org
Subject: Re: Possible IAB workshop on routing and addressing participants?
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

On 22-jun-2006, at 16:45, Brian E Carpenter wrote:

>>     > So if you don't like shim6, you pretty much have to change  
>> the routing
>>     > architecture.

>> I gather there was a lot of resistance in some operator forum  
>> (something to
>> do with NANOG, maybe?) to the whole concept of shim6. Some people  
>> were
>> pushing for that old canard, PI-space, as an alternative, and got  
>> a certain
>> amount of support for it. What's the currrent community take on  
>> shim6?

> I won't comment on that - as ex Multi6 co-chair and co-chair of the  
> Shim6
> BOF, I'm definitely not neutral, and opinions vary.

Like Brian, I can't claim to be neutral here. With that out of the  
way, I firmly believe the shim6 architecture is the best achievable  
one based on sites having multiple PA prefixes. I don't think we need  
to go back and redo shim6, or go back and redo IPv6, because the  
tradeoffs haven't really changed. Doing the same thing again in the  
same environment but expecting different results is a very curious  
human tendency.

In the mean time, the internet has grown from 1.3 million hosts in  
1993 to about 400 million now: a factor 300 ( http://www.isc.org/ 
index.pl?/ops/ds/ ). But we're still running the same inter-domain  
routing protocol that reacts to changes in reachability between  
autonomous systems by enumerating all the prefixes affected, doesn't  
have a real inter-AS metric, suffers from convergence times that can  
on occiasion be longer than a TCP timeout, allows policies that  
prevent stable convergence altogether and lacks security.

I think this is an area where a new look at the problem may actually  
result in improvements over the current situation.

I say: let BGP4 retire at age 15 (well, 20 is more likely...) even if  
its successor can't provide multihoming for 10 billion sites or solve  
the transition to longer-than-32-bit addresses completely painlessly.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Tue Jun 27 08:58:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FvD9H-0005rC-UF; Tue, 27 Jun 2006 08:58:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FvD9G-0005m3-SV
	for routing-discussion@ietf.org; Tue, 27 Jun 2006 08:58:34 -0400
Received: from mail-red.research.att.com ([192.20.225.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FvD9F-000668-Mb
	for routing-discussion@ietf.org; Tue, 27 Jun 2006 08:58:34 -0400
Received: from bright.research.att.com (bright.research.att.com
	[135.207.20.189])
	by mail-green.research.att.com (Postfix) with ESMTP id 7388F84DE
	for <routing-discussion@ietf.org>; Tue, 27 Jun 2006 08:58:33 -0400 (EDT)
Received: (from fenner@localhost)
	by bright.research.att.com (8.12.11.20060308/8.12.10/Submit) id
	k5RCwXrA007588; Tue, 27 Jun 2006 08:58:33 -0400
From: Bill Fenner <fenner@research.att.com>
Message-Id: <200606271258.k5RCwXrA007588@bright.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: routing-discussion@ietf.org
Date: Tue, 27 Jun 2006 08:58:33 -0400
Versions: dmail (linux) 2.7/makemail 2.14
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Subject: Routing Area meeting scheduled
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org


Thanks to the hard work of the secretariat, we found a slot for the
routing area meeting - Tuesday morning from 0900-1130.  We plan to
have the usual working group status updates, perhaps a pre-BOF
discussion on ensuring source addresses are correct, and the usual
open mic.

Please let Ross and me know if there are any other topics that
people want to address.

Thanks!
  Bill

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Tue Jun 27 12:18:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FvGGj-00036Z-5K; Tue, 27 Jun 2006 12:18:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FvGGi-000365-9X
	for routing-discussion@ietf.org; Tue, 27 Jun 2006 12:18:28 -0400
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 1FvGGi-0004Nz-8F
	for routing-discussion@ietf.org; Tue, 27 Jun 2006 12:18:28 -0400
Received: from mail2.noc.data.net.uk ([80.68.34.49])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FvG4U-0000P4-1B
	for routing-discussion@ietf.org; Tue, 27 Jun 2006 12:05:53 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99]
	helo=cortex.aria-networks.com)
	by mail2.noc.data.net.uk with esmtp (Exim 3.36 #1)
	id 1FvG4J-0007ZC-00
	for routing-discussion@ietf.org; Tue, 27 Jun 2006 17:05:39 +0100
Received: from your029b8cecfe ([194.94.109.154] RDNS failed) by
	cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 27 Jun 2006 17:05:42 +0100
Message-ID: <06ec01c69a03$881c6720$0a23fea9@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Bill Fenner" <fenner@research.att.com>,
	<routing-discussion@ietf.org>
References: <200606271258.k5RCwXrA007588@bright.research.att.com>
Date: Tue, 27 Jun 2006 17:05:26 +0100
Organization: Old Dog Consulting
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-OriginalArrivalTime: 27 Jun 2006 16:05:42.0369 (UTC)
	FILETIME=[8A5EDD10:01C69A03]
X-Spam-Score: -2.1 (--)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: 
Subject: Re: Routing Area meeting scheduled
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

someone from the IAB to talk about the routing work shop they are 
discussing?

> Please let Ross and me know if there are any other topics that
> people want to address.

A 



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Tue Jun 27 12:21:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FvGJu-0004WV-8C; Tue, 27 Jun 2006 12:21:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FvGJt-0004Ub-6u
	for routing-discussion@ietf.org; Tue, 27 Jun 2006 12:21:45 -0400
Received: from m106.maoz.com ([205.167.76.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FvGJr-0004WU-Rc
	for routing-discussion@ietf.org; Tue, 27 Jun 2006 12:21:45 -0400
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.13.6/8.13.6) with ESMTP id k5RGLh3X008942;
	Tue, 27 Jun 2006 09:21:43 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.13.6/8.12.11/Submit) id k5RGLhMp008941;
	Tue, 27 Jun 2006 09:21:43 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using
	-f
Date: Tue, 27 Jun 2006 09:21:43 -0700
From: David Meyer <dmm@1-4-5.net>
To: Adrian Farrel <adrian@olddog.co.uk>
Message-ID: <20060627162143.GA8928@1-4-5.net>
References: <200606271258.k5RCwXrA007588@bright.research.att.com>
	<06ec01c69a03$881c6720$0a23fea9@your029b8cecfe>
Mime-Version: 1.0
In-Reply-To: <06ec01c69a03$881c6720$0a23fea9@your029b8cecfe>
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I find your lack of faith disturbing." -- Darth Vader,
	Star Wars Episode IV.
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: Bill Fenner <fenner@research.att.com>, routing-discussion@ietf.org
Subject: Re: Routing Area meeting scheduled
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0419478080=="
Errors-To: routing-discussion-bounces@ietf.org


--===============0419478080==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC"
Content-Disposition: inline


--wRRV7LY7NUeQGEoC
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 27, 2006 at 05:05:26PM +0100, Adrian Farrel wrote:
> someone from the IAB to talk about the routing work shop they are=20
> discussing?

	I would be glad to give an update (such as we have) if
	folks would like.

	--dmm

--wRRV7LY7NUeQGEoC
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFEoVsXORgD1qCZ2KcRAuKvAJ462Cjta2iOsPjUNhDsoS8hNe6KYgCgiDEM
8RlWbbbPXfzBSNlYesBsnls=
=m03P
-----END PGP SIGNATURE-----

--wRRV7LY7NUeQGEoC--


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

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion

--===============0419478080==--




From routing-discussion-bounces@ietf.org Tue Jun 27 14:43:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FvIXM-0000Sh-Sz; Tue, 27 Jun 2006 14:43:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FvIXL-0000Sc-Dc
	for routing-discussion@ietf.org; Tue, 27 Jun 2006 14:43:47 -0400
Received: from [2001:1af8:2:5::2] (helo=sequoia.muada.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FvIXL-0001sI-61
	for routing-discussion@ietf.org; Tue, 27 Jun 2006 14:43:47 -0400
Received: from [IPv6:2001:1af8:6::20a:95ff:fef5:246e] (alumange.muada.com
	[IPv6:2001:1af8:6:0:20a:95ff:fef5:246e]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id k5RIgIeo013983
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO);
	Tue, 27 Jun 2006 20:42:18 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <20060627162143.GA8928@1-4-5.net>
References: <200606271258.k5RCwXrA007588@bright.research.att.com>
	<06ec01c69a03$881c6720$0a23fea9@your029b8cecfe>
	<20060627162143.GA8928@1-4-5.net>
Mime-Version: 1.0 (Apple Message framework v750)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A15722B2-A50E-42F4-B22C-3EF78D29B201@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Tue, 27 Jun 2006 20:43:39 +0200
To: David Meyer <dmm@1-4-5.net>
X-Mailer: Apple Mail (2.750)
X-Spam-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on sequoia.muada.com
X-Spam-Score: -2.8 (--)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: routing-discussion@ietf.org
Subject: Re: Routing Area meeting scheduled
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

On 27-jun-2006, at 18:21, David Meyer wrote:

>> someone from the IAB to talk about the routing work shop they are
>> discussing?

> 	I would be glad to give an update (such as we have) if
> 	folks would like.

Maybe a discussion about the problem statement for the workshop would  
be good, if there is time. As I said earlier, what's there now is a  
tad on the broad side.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Tue Jun 27 17:13:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FvKsU-0008Jj-KA; Tue, 27 Jun 2006 17:13:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FvKsT-0008Ie-Cr
	for routing-discussion@ietf.org; Tue, 27 Jun 2006 17:13:45 -0400
Received: from eunet-gw.ipv6.netcore.fi ([2001:670:86:3001::1] helo=netcore.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FvKsS-0004jj-SG
	for routing-discussion@ietf.org; Tue, 27 Jun 2006 17:13:45 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.12.11.20060614/8.12.11) with ESMTP id k5RJxuAp025406
	for <routing-discussion@ietf.org>; Tue, 27 Jun 2006 22:59:56 +0300
Date: Tue, 27 Jun 2006 22:59:56 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: routing-discussion@ietf.org
Message-ID: <Pine.LNX.4.64.0606272258500.25079@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; format=flowed
Content-ID: <Pine.LNX.4.64.0606272258502.25079@netcore.fi>
X-Virus-Scanned: ClamAV 0.88.2/1564/Mon Jun 26 17:55:16 2006 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RELAYS autolearn=failed 
	version=3.1.2
X-Spam-Checker-Version: SpamAssassin 3.1.2 (2006-05-25) on otso.netcore.fi
X-Spam-Score: -2.8 (--)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Subject: I-D ACTION:draft-savola-bcp84-urpf-experiences-01.txt  (fwd)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Errors-To: routing-discussion-bounces@ietf.org

FYI,

This was updated a while ago in response to comments.  More comments 
are welcome especially if there's going to be pre-BOF discussion on 
source address correctness verification.

---------- Forwarded message ----------
Date: Thu, 15 Jun 2006 15:50:01 -0400
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-savola-bcp84-urpf-experiences-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.


 	Title		: Experiences from Using Unicast RPF
 	Author(s)	: P. Savola
 	Filename	: draft-savola-bcp84-urpf-experiences-01.txt
 	Pages		: 10
 	Date		: 2006-6-15

RFC 3704 (BCP 84) published in March 2004 provided an ingress
filtering technique update to RFC 2827 (BCP 38).  This memo tries to
document operational experiences learned practising ingress filtering
techniques, in particular ingress filtering for multihomed networks.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-savola-bcp84-urpf-experiences-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-savola-bcp84-urpf-experiences-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-savola-bcp84-urpf-experiences-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.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-bounces@ietf.org Tue Jun 27 19:00:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FvMWh-0004iq-R6; Tue, 27 Jun 2006 18:59:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FvMWf-0004gH-QS
	for routing-discussion@ietf.org; Tue, 27 Jun 2006 18:59:21 -0400
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 1FvLrz-0003A7-OI
	for routing-discussion@ietf.org; Tue, 27 Jun 2006 18:17:19 -0400
Received: from m106.maoz.com ([205.167.76.9])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FvK4u-0006H6-32
	for routing-discussion@ietf.org; Tue, 27 Jun 2006 16:22:34 -0400
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.13.6/8.13.6) with ESMTP id k5RKMVin013019;
	Tue, 27 Jun 2006 13:22:31 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.13.6/8.12.11/Submit) id k5RKMVOR013018;
	Tue, 27 Jun 2006 13:22:31 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using
	-f
Date: Tue, 27 Jun 2006 13:22:31 -0700
From: David Meyer <dmm@1-4-5.net>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Message-ID: <20060627202231.GA12966@1-4-5.net>
References: <200606271258.k5RCwXrA007588@bright.research.att.com>
	<06ec01c69a03$881c6720$0a23fea9@your029b8cecfe>
	<20060627162143.GA8928@1-4-5.net>
	<A15722B2-A50E-42F4-B22C-3EF78D29B201@muada.com>
Mime-Version: 1.0
In-Reply-To: <A15722B2-A50E-42F4-B22C-3EF78D29B201@muada.com>
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I find your lack of faith disturbing." -- Darth Vader,
	Star Wars Episode IV.
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: routing-discussion@ietf.org
Subject: Re: Routing Area meeting scheduled
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0892688198=="
Errors-To: routing-discussion-bounces@ietf.org


--===============0892688198==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="0OAP2g/MAC+5xKAE"
Content-Disposition: inline


--0OAP2g/MAC+5xKAE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 27, 2006 at 08:43:39PM +0200, Iljitsch van Beijnum wrote:
> On 27-jun-2006, at 18:21, David Meyer wrote:
>=20
> >>someone from the IAB to talk about the routing work shop they are
> >>discussing?
>=20
> >	I would be glad to give an update (such as we have) if
> >	folks would like.
>=20
> Maybe a discussion about the problem statement for the workshop would =20
> be good, if there is time. As I said earlier, what's there now is a =20
> tad on the broad side.

	Sure.

	--dmm

--0OAP2g/MAC+5xKAE
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFEoZOHORgD1qCZ2KcRAuFZAJ9Kh8HTlo+v2NHIj/oqypQzgak+MQCfTYn2
F0Dt8kQDazH+jf9X3i6dXnA=
=agix
-----END PGP SIGNATURE-----

--0OAP2g/MAC+5xKAE--


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

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion

--===============0892688198==--




