From routing-discussion-bounces@ietf.org Tue Feb 14 20:26:19 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F9BQx-00080t-NO; Tue, 14 Feb 2006 20:26:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F9BQu-0007xX-VL
	for routing-discussion@megatron.ietf.org;
	Tue, 14 Feb 2006 20:26:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24107
	for <routing-discussion@ietf.org>; Tue, 14 Feb 2006 20:24:30 -0500 (EST)
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F9Ben-0003WH-Dg
	for routing-discussion@ietf.org; Tue, 14 Feb 2006 20:40:40 -0500
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 1F9BQq-000Pkj-Cu
	for routing-discussion@ietf.org; Wed, 15 Feb 2006 01:26:12 +0000
Date: Tue, 14 Feb 2006 17:25:48 -0800
From: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <192827753.20060214172548@psg.com>
To: routing-discussion@ietf.org
In-Reply-To: <200511212307.jALN78v5003475@bright.research.att.com>
References: <200511212307.jALN78v5003475@bright.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.8 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Content-Transfer-Encoding: 7bit
Subject: Re: A little rant over draft-fenner-zinin-rtg-standard-reqts-01
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>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org


Pushing this forward a little...

My reading of rough consensus regarding this discussion (this thread and
"comment on draft-fenner-zinin-rtg-standard-reqts-00" started on
Aug-3-2005) is that we should require two implementations for PS.

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

Monday, November 21, 2005, 3:07:08 PM, Bill Fenner wrote:

>>This now frees us up to examine the requirement for *two* independent
>>implementations.

> While you have some excellent points, our reasoning for changing the
> requirement to 2 implementations was nowhere near that interesting.
> The existing requirements for PS in 1264 were:

> a) At least one implementation.
> b) The spec must be written clearly enough to permit two interoperable
> implementations to be written from it.

> After trying to apply these guidelines for a while, we realized
> that we had no real way to determine "b", and decided to switch
> to 2 implementations to prove the clarity of the spec.

>>From my perspective this debate reflects a change to the way that a PS is
>>cast within the industry. I think that at the moment it is hard to build
>>significant operational experience until publication as PS.

> I think this experience varies - there are a fair number of things
> that are implemented and deployed before they're I-Ds.

>>A solution to this, is to introduce a new category between WG last call
>>and PS. Let's call it PPS (proposed proposed standard). We would then
>>advance I-Ds to PPS, allow implementation and operational experience
>>before advancing to PS.

> This sounds like what has been tossed around in newtrk as
> "stable snapshot".

>>Perhaps we should try to understand these concerns (personally, I think
>>the Motivation section is fine, but I don't see the text there being
>>mapped to concrete concerns, and I don't see a description of how the
>>proposed solution will address the text in the Motivation section).
>>1. "The Internet is being built from PSs"
>>2. "There is insufficient operational experience of protocols that are
>>being deployed in the Internet"

> We're explicitly not trying to address #1.

> It's not that we're trying to fix #2, but prevent it.

> We[*] had the conversation some time ago about whether it's still
> reasonable for routing protocols to have their own rules.  The
> general feeling seemed to be that they do, mostly for the reasons
> outlined in the motivation section.  Personally, I'm not a huge
> fan, and would rather see IETF-wide consistency (e.g., if DNS
> goes kaplooey, is it a bigger or lesser catastrophe for the Internet
> than if routing goes kaplooey?), but the general feeling of the
> community seemed to be until we have that, at least we have this.
> The effort to revise 1264 came as an attempt to modernize it.

>   Bill

> [*] - at a routing area meeting a few years ago.  I don't think there
> was followup on the list at the time.

> _______________________________________________
> 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 Tue Feb 14 20:55:34 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F9BtG-0004qR-LI; Tue, 14 Feb 2006 20:55:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F9BtF-0004qC-6i
	for routing-discussion@megatron.ietf.org;
	Tue, 14 Feb 2006 20:55:33 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25556
	for <routing-discussion@ietf.org>; Tue, 14 Feb 2006 20:53:46 -0500 (EST)
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F9C78-0004L2-UC
	for routing-discussion@ietf.org; Tue, 14 Feb 2006 21:09:57 -0500
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 1F9BtB-0001Sm-Q5
	for routing-discussion@ietf.org; Wed, 15 Feb 2006 01:55:29 +0000
Date: Tue, 14 Feb 2006 17:55:05 -0800
From: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <1434498036.20060214175505@psg.com>
To: routing-discussion@ietf.org
In-Reply-To: <192827753.20060214172548@psg.com>
References: <200511212307.jALN78v5003475@bright.research.att.com>
	<192827753.20060214172548@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.1 (++)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
Subject: draft-fenner-zinin-rtg-standard-reqts-01: operational experience
	for PS?
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>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org

A related question that I saw in the discussion on the number of
implementations for PS was wrt the operational experience.

RFC 1264, as well as the draft-fenner-zinin say no experience is necessary
for PS. There was a suggestion by JP, seconded by Curtis that at least
minimal operational experience should be required. I'd like to hear
opinions on this. Please keep in mind, that requiring this also means
more paperwork for submission, however small incrementally.

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

Tuesday, February 14, 2006, 5:25:48 PM, Alex Zinin wrote:

> Pushing this forward a little...

> My reading of rough consensus regarding this discussion (this thread and
> "comment on draft-fenner-zinin-rtg-standard-reqts-00" started on
> Aug-3-2005) is that we should require two implementations for PS.



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



From routing-discussion-bounces@ietf.org Tue Feb 14 21:06:08 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F9C3U-0001qP-9Y; Tue, 14 Feb 2006 21:06:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F9C3T-0001qK-IX
	for routing-discussion@megatron.ietf.org;
	Tue, 14 Feb 2006 21:06:07 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26159
	for <routing-discussion@ietf.org>; Tue, 14 Feb 2006 21:04:20 -0500 (EST)
Received: from relay03.pair.com ([209.68.5.17])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1F9CHL-0004fO-Dv
	for routing-discussion@ietf.org; Tue, 14 Feb 2006 21:20:31 -0500
Received: (qmail 46677 invoked from network); 15 Feb 2006 02:06:02 -0000
Received: from unknown (HELO workhorse.faster-light.net) (unknown)
	by unknown with SMTP; 15 Feb 2006 02:06:02 -0000
X-pair-Authenticated: 69.37.59.162
Received: from workhorse.faster-light.net (localhost.faster-light.net
	[127.0.0.1])
	by workhorse.faster-light.net (8.12.11/8.12.11) with ESMTP id
	k1F26o8r055798; Tue, 14 Feb 2006 21:06:51 -0500 (EST)
	(envelope-from curtis@workhorse.faster-light.net)
Message-Id: <200602150206.k1F26o8r055798@workhorse.faster-light.net>
To: Alex Zinin <zinin@psg.com>
In-reply-to: Your message of "Tue, 14 Feb 2006 17:25:48 PST."
	<192827753.20060214172548@psg.com> 
Date: Tue, 14 Feb 2006 21:06:50 -0500
From: Curtis Villamizar <curtis@faster-light.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: routing-discussion@ietf.org
Subject: Re: A little rant over draft-fenner-zinin-rtg-standard-reqts-01 
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>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org


In message <192827753.20060214172548@psg.com>
Alex Zinin writes:
>  
>  
> Pushing this forward a little...
>  
> My reading of rough consensus regarding this discussion (this thread and
> "comment on draft-fenner-zinin-rtg-standard-reqts-00" started on
> Aug-3-2005) is that we should require two implementations for PS.
>  
> -- 
> Alex


Two *independent* implementations.

Curtis

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



From routing-discussion-bounces@ietf.org Tue Feb 14 22:20:50 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F9DDm-0004Me-5q; Tue, 14 Feb 2006 22:20:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F9DDk-0004MZ-Sh
	for routing-discussion@megatron.ietf.org;
	Tue, 14 Feb 2006 22:20:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00521
	for <routing-discussion@ietf.org>; Tue, 14 Feb 2006 22:19:03 -0500 (EST)
Received: from pop-satin.atl.sa.earthlink.net ([207.69.195.63])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F9DRd-000701-BO
	for routing-discussion@ietf.org; Tue, 14 Feb 2006 22:35:13 -0500
Received: from user-2ivf94b.dsl.mindspring.com ([165.247.164.139]
	helo=JMHLap3.stevecrocker.com)
	by pop-satin.atl.sa.earthlink.net with esmtp (Exim 3.36 #10)
	id 1F9DDe-0003mM-00
	for routing-discussion@ietf.org; Tue, 14 Feb 2006 22:20:43 -0500
Message-Id: <7.0.1.0.0.20060214221639.032788d8@stevecrocker.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Tue, 14 Feb 2006 22:20:40 -0500
To: routing-discussion@ietf.org
From: "Joel M. Halpern" <joel@stevecrocker.com>
In-Reply-To: <1434498036.20060214175505@psg.com>
References: <200511212307.jALN78v5003475@bright.research.att.com>
	<192827753.20060214172548@psg.com>
	<1434498036.20060214175505@psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 4.1 (++++)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Subject: Re: draft-fenner-zinin-rtg-standard-reqts-01: operational
 experience for PS?
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>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org

I think that it is reasonable to ask folks to implement pre-standard 
for routing activities. (If we can't get two implementations, then 
there probably isn't enough interest to be worth standardizing.)

But asking for operational deployment pre-standard is a lot 
harder.  Yes, some of our work has gotten deployment before PS.  But 
not all of it by any means.

The paperwork increment is probably not an issue.  The real world 
requirement for use (rather than just implementation) seems to me a 
mistake.  I might even feel tempted to go a step further.  Even we 
put in this requirement, then we are essentially declaring the last 
WG draft to be the same as what everyone else treats as PS, without 
IETF-wide review.

Yours,
Joel M. Halpern

At 08:55 PM 2/14/2006, Alex Zinin wrote:
>A related question that I saw in the discussion on the number of
>implementations for PS was wrt the operational experience.
>
>RFC 1264, as well as the draft-fenner-zinin say no experience is necessary
>for PS. There was a suggestion by JP, seconded by Curtis that at least
>minimal operational experience should be required. I'd like to hear
>opinions on this. Please keep in mind, that requiring this also means
>more paperwork for submission, however small incrementally.
>
>--
>Alex
>http://www.psg.com/~zinin
>
>Tuesday, February 14, 2006, 5:25:48 PM, Alex Zinin wrote:
>
> > Pushing this forward a little...
>
> > My reading of rough consensus regarding this discussion (this thread and
> > "comment on draft-fenner-zinin-rtg-standard-reqts-00" started on
> > Aug-3-2005) is that we should require two implementations for PS.
>
>
>
>_______________________________________________
>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 Feb 15 02:18:49 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F9Gw5-0000OE-HS; Wed, 15 Feb 2006 02:18:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F9Gw3-0000O9-NG
	for routing-discussion@megatron.ietf.org;
	Wed, 15 Feb 2006 02:18:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15350
	for <routing-discussion@ietf.org>; Wed, 15 Feb 2006 02:17:00 -0500 (EST)
Received: from sccrmhc12.comcast.net ([204.127.200.82])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F9H9w-000670-2q
	for routing-discussion@ietf.org; Wed, 15 Feb 2006 02:33:14 -0500
Received: from [192.168.1.6]
	(c-67-180-169-111.hsd1.ca.comcast.net[67.180.169.111])
	by comcast.net (sccrmhc12) with ESMTP
	id <2006021507183101200sb749e>; Wed, 15 Feb 2006 07:18:31 +0000
Message-ID: <43F2D61B.7030303@tony.li>
Date: Tue, 14 Feb 2006 23:19:55 -0800
From: Tony Li <tony.li@tony.li>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: "Joel M. Halpern" <joel@stevecrocker.com>
References: <200511212307.jALN78v5003475@bright.research.att.com>	<192827753.20060214172548@psg.com>	<1434498036.20060214175505@psg.com>
	<7.0.1.0.0.20060214221639.032788d8@stevecrocker.com>
In-Reply-To: <7.0.1.0.0.20060214221639.032788d8@stevecrocker.com>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit
Cc: routing-discussion@ietf.org
Subject: Re: draft-fenner-zinin-rtg-standard-reqts-01: operational experience
 for PS?
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>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org



> I think that it is reasonable to ask folks to implement pre-standard for
> routing activities. (If we can't get two implementations, then there
> probably isn't enough interest to be worth standardizing.)
> 
> But asking for operational deployment pre-standard is a lot harder. 
> Yes, some of our work has gotten deployment before PS.  But not all of
> it by any means.
> 
> The paperwork increment is probably not an issue.  The real world
> requirement for use (rather than just implementation) seems to me a
> mistake.  I might even feel tempted to go a step further.  Even we put
> in this requirement, then we are essentially declaring the last WG draft
> to be the same as what everyone else treats as PS, without IETF-wide
> review.


Slightly different perspective: how would one truly define meaningful
operational experience?  I don't think that any of us would accept 10
minutes in a vendor's back lab.  To my way of thinking, the meaningful
experience only comes with many thousands of hours of experience in
production networks, facing real world churn, topology changes, corner
cases, and scalability stresses.  How one would articulate that
precisely enough seems somewhat challenging, and how one would actually
ascertain that level of experience also seems hard.

Thus, rather than add a well-intentioned but ineffective requirement,
I'd suggest that we pass on it.

Tony

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



From routing-discussion-bounces@ietf.org Wed Feb 15 09:00:14 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F9NCY-0006CQ-89; Wed, 15 Feb 2006 09:00:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F9NCV-0006Bq-OT
	for routing-discussion@megatron.ietf.org;
	Wed, 15 Feb 2006 09:00:11 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11097
	for <routing-discussion@ietf.org>; Wed, 15 Feb 2006 08:58:24 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F9NQW-0002sg-VR
	for routing-discussion@ietf.org; Wed, 15 Feb 2006 09:14:42 -0500
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by sj-iport-2.cisco.com with ESMTP; 15 Feb 2006 06:00:01 -0800
Received: from cisco.com (cypher.cisco.com [171.69.11.142])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k1FE01KT024296;
	Wed, 15 Feb 2006 06:00:01 -0800 (PST)
Received: (from achandra@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id GAA01981;
	Wed, 15 Feb 2006 06:00:01 -0800 (PST)
Date: Wed, 15 Feb 2006 06:00:01 -0800
From: Chandrashekhar Appanna <achandra@cisco.com>
To: Alex Zinin <zinin@psg.com>
Message-ID: <20060215140001.GD592@cisco.com>
References: <200511212307.jALN78v5003475@bright.research.att.com>
	<192827753.20060214172548@psg.com>
	<1434498036.20060214175505@psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1434498036.20060214175505@psg.com>
User-Agent: Mutt/1.4i
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: routing-discussion@ietf.org
Subject: Re: draft-fenner-zinin-rtg-standard-reqts-01: operational
	experience for PS?
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>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org

  Where would we capture the operational experience? In another
  document like the implementation report or in the same one?
  I like the idea but I am not clear what we would actually
  quantify it.. otherwise it just becomes another 'grey' area.

  Rgds,
  Chandra.
  
On Tue, Feb 14, 2006 at 05:55:05PM -0800, Alex Zinin wrote:
> A related question that I saw in the discussion on the number of
> implementations for PS was wrt the operational experience.
> 
> RFC 1264, as well as the draft-fenner-zinin say no experience is necessary
> for PS. There was a suggestion by JP, seconded by Curtis that at least
> minimal operational experience should be required. I'd like to hear
> opinions on this. Please keep in mind, that requiring this also means
> more paperwork for submission, however small incrementally.
> 
> -- 
> Alex
> http://www.psg.com/~zinin
> 
> Tuesday, February 14, 2006, 5:25:48 PM, Alex Zinin wrote:
> 
> > Pushing this forward a little...
> 
> > My reading of rough consensus regarding this discussion (this thread and
> > "comment on draft-fenner-zinin-rtg-standard-reqts-00" started on
> > Aug-3-2005) is that we should require two implementations for PS.
> 
> 
> 
> _______________________________________________
> 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 Feb 16 12:59:39 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F9nPn-00089g-Gt; Thu, 16 Feb 2006 12:59:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F9nPm-00088e-71
	for routing-discussion@megatron.ietf.org;
	Thu, 16 Feb 2006 12:59:38 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16105
	for <routing-discussion@ietf.org>; Thu, 16 Feb 2006 12:57:51 -0500 (EST)
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F9ndz-00075C-Uo
	for routing-discussion@ietf.org; Thu, 16 Feb 2006 13:14:23 -0500
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 1F9nPg-0009AN-Cn; Thu, 16 Feb 2006 17:59:32 +0000
Date: Thu, 16 Feb 2006 09:59:07 -0800
From: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <801038511.20060216095907@psg.com>
To: Chandrashekhar Appanna <achandra@cisco.com>
In-Reply-To: <20060215140001.GD592@cisco.com>
References: <200511212307.jALN78v5003475@bright.research.att.com>
	<192827753.20060214172548@psg.com> <1434498036.20060214175505@psg.com>
	<20060215140001.GD592@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.1 (++)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
Cc: routing-discussion@ietf.org
Subject: Re: draft-fenner-zinin-rtg-standard-reqts-01: operational
	experience for PS?
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>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org

Chandra-

 At this point we put it in an "experience with the protocol" document. for
 DS and higher.

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

Wednesday, February 15, 2006, 6:00:01 AM, Chandrashekhar Appanna wrote:
>   Where would we capture the operational experience? In another
>   document like the implementation report or in the same one?
>   I like the idea but I am not clear what we would actually
>   quantify it.. otherwise it just becomes another 'grey' area.

>   Rgds,
>   Chandra.
  
> On Tue, Feb 14, 2006 at 05:55:05PM -0800, Alex Zinin wrote:
>> A related question that I saw in the discussion on the number of
>> implementations for PS was wrt the operational experience.
>> 
>> RFC 1264, as well as the draft-fenner-zinin say no experience is necessary
>> for PS. There was a suggestion by JP, seconded by Curtis that at least
>> minimal operational experience should be required. I'd like to hear
>> opinions on this. Please keep in mind, that requiring this also means
>> more paperwork for submission, however small incrementally.
>> 
>> -- 
>> Alex
>> http://www.psg.com/~zinin
>> 
>> Tuesday, February 14, 2006, 5:25:48 PM, Alex Zinin wrote:
>> 
>> > Pushing this forward a little...
>> 
>> > My reading of rough consensus regarding this discussion (this thread and
>> > "comment on draft-fenner-zinin-rtg-standard-reqts-00" started on
>> > Aug-3-2005) is that we should require two implementations for PS.
>> 
>> 
>> 
>> _______________________________________________
>> 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 Feb 16 13:03:00 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F9nT2-0004CM-PB; Thu, 16 Feb 2006 13:03:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F9nT1-0004BK-8M
	for routing-discussion@megatron.ietf.org;
	Thu, 16 Feb 2006 13:02:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16458
	for <routing-discussion@ietf.org>; Thu, 16 Feb 2006 13:01:12 -0500 (EST)
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F9nhF-0007Cw-9j
	for routing-discussion@ietf.org; Thu, 16 Feb 2006 13:17:44 -0500
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 1F9nSx-0009SK-4T
	for routing-discussion@ietf.org; Thu, 16 Feb 2006 18:02:55 +0000
Date: Thu, 16 Feb 2006 10:02:30 -0800
From: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <914383237.20060216100230@psg.com>
To: routing-discussion@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit
Subject: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt
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>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org

This is to start a Routing Area-wide two-week Last Call on this document
for submission to the IESG for publication as BCP. The Last Call ends on
March 2nd, 2006.

The document is available here:

http://www.ietf.org/internet-drafts/draft-fenner-zinin-rtg-standard-reqts-01.txt

Abstract:

>    This document provides guidance for the advancement of the protocols
>    produced within the IETF Routing Area.  It places implementation and
>    interoperability constraints on protocols earlier in the standards
>    process than RFC 2026, based on RFC 2026's provision that the IESG
>    may require implementation and/or operational experience prior to
>    granting Proposed Standard status to a specification that materially
>    affects the core Internet protocols or that specifies behavior that
>    may have significant operational impact on the Internet.
> 
>    We also discuss the applicability of these rules to protocols and
>    their extensions.


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


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



From routing-discussion-bounces@ietf.org Fri Feb 17 08:50:50 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1FA60Y-0001xP-9u; Fri, 17 Feb 2006 08:50:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1FA60Q-0001tW-G9
	for routing-discussion@megatron.ietf.org;
	Fri, 17 Feb 2006 08:50:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24210
	for <routing-discussion@ietf.org>; Fri, 17 Feb 2006 08:48:46 -0500 (EST)
Received: from adsl-66-120-207-101.dsl.sntc01.pacbell.net ([66.120.207.101]
	helo=coffee.rawdofmt.org) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FA6Ed-0008V1-8u
	for routing-discussion@ietf.org; Fri, 17 Feb 2006 09:05:28 -0500
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by coffee.rawdofmt.org (Postfix) with ESMTP id 58B3A3DCC8B;
	Fri, 17 Feb 2006 05:50:17 -0800 (PST)
In-Reply-To: <914383237.20060216100230@psg.com>
References: <914383237.20060216100230@psg.com>
Mime-Version: 1.0 (Apple Message framework v746.2)
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C842E8F4-27C3-460F-89CB-7D5A47D26BE8@rawdofmt.org>
Content-Transfer-Encoding: 7bit
From: Christian Hopps <chopps@rawdofmt.org>
Date: Fri, 17 Feb 2006 05:50:15 -0800
To: Alex Zinin <zinin@psg.com>
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
Cc: Christian Hopps <chopps@rawdofmt.org>, routing-discussion@ietf.org
Subject: Re: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt
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>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org

4.1 Proposed Standard
    4.  Two or more independent interoperable implementations must  
exist.

4.2 Draft Standard
    4.  Two or more interoperable implementations must exist.  At least
        two must be written independently.

Is there a difference of meaning here, rather than just words?

Chris.

On Feb 16, 2006, at 10:02 AM, Alex Zinin wrote:

> This is to start a Routing Area-wide two-week Last Call on this  
> document
> for submission to the IESG for publication as BCP. The Last Call  
> ends on
> March 2nd, 2006.
>
> The document is available here:
>
> http://www.ietf.org/internet-drafts/draft-fenner-zinin-rtg-standard- 
> reqts-01.txt


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



From routing-discussion-bounces@ietf.org Fri Feb 17 13:39:44 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1FAAW8-0002i5-5j; Fri, 17 Feb 2006 13:39:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1FAAW6-0002eO-Dq
	for routing-discussion@megatron.ietf.org;
	Fri, 17 Feb 2006 13:39:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20449
	for <routing-discussion@ietf.org>; Fri, 17 Feb 2006 13:37:54 -0500 (EST)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FAAka-0001Bs-59
	for routing-discussion@ietf.org; Fri, 17 Feb 2006 13:54:40 -0500
Received: from rtp-core-1.cisco.com ([64.102.124.12])
	by rtp-iport-2.cisco.com with ESMTP; 17 Feb 2006 13:39:33 -0500
X-IronPort-AV: i="4.02,124,1139202000"; 
	d="scan'208"; a="82641525:sNHT34982510"
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 k1HIdUPM019907; 
	Fri, 17 Feb 2006 13:39:30 -0500 (EST)
Message-Id: <200602171839.k1HIdUPM019907@rtp-core-1.cisco.com>
To: Alex Zinin <zinin@psg.com>
In-reply-to: Your message of Thu, 16 Feb 2006 10:02:30 -0800.
	<914383237.20060216100230@psg.com> 
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Fri, 17 Feb 2006 13:39:29 -0500
From: Eric Rosen <erosen@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21be852dc93f0971708678c18d38c096
Cc: routing-discussion@ietf.org
Subject: Re: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt 
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>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org


I have many concerns about this document.  

Beginning with the statement: 

      The IESG may require implementation and/or operational experience
      prior to granting Proposed Standard status to a specification that
      materially affects the core Internet protocols or that specifies
      behavior that may have significant operational impact on the
      Internet.

The first problem is  that there is never a clear set  of criteria given for
identifying "core internet protocols".  The  second problem is that there is
never a  clear set  of criteria for  whether some  specification "materially
affects" a core internet protocol. 

For  instance, I  would really  like to  understand why  DNS is  not  a core
Internet protocol but LDP and RSVP are.  Really, which one is more important
to  the  proper operation  of  the global,  public  Internet?   DNS is  even
arguably a distributed protocol, where,  to quote the draft, "the effects of
a problem ... may easily propagate through the network, and result in service
degradation of complete loss of  connectivity".  In fact, this could even be
said of  http, at least when  all the common  distributed caching procedures
are taken into account. 

I certainly  agree that distributed  n-party protocols such as  routing are
more  difficult to  get  right  than is  the  average two-party  application
protocol.  However,  routing is not  the only distributed  n-party protocol,
so I  don't think that is  the real basis  for requiring it to  have special
treatment. 

Given  the  emphasis on  ROUTING,  one might  infer  that  the protocols  of
interest are the  protocols which set up forwarding  state in routers.  This
criterion is  not given  explicitly, but  at least it  explains why  LDP and
RSVP-TE are  considered to be in  scope.  That still  leaves unclear whether
"ordinary"  RSVP  is  to be  in  scope;  it  can  certainly be  argued  that
"ordinary" RSVP affects the forwarding  state, even if it cannot actually be
used to  change the next hop  at any point along  a path.  The  same is true
though for stuff like WRED, DSCP, etc.  

It seems  to be intended that  tunneling protocols (e.g., L2TP,  GRE) not be
considered to  be "core  internet protocols".  But  now what about  the case
where a  "core internet  protocol" has a  second use  as a tunnel  setup and
maintenance protocol.  For example, the LDP extensions of PWE3 have as their
function  the  setup  and   maintenance  of  tunnels,  so  presumably  these
extensions  would  not  be considered  to  be  part  of the  "core  internet
protocols", even if the base LDP protocol is. 

Which leads to the next problem:   there are a number of protocols which are
sometimes used for setting up forwarding state in the routers, and sometimes
for other  purposes.  That is, the  base protocol might  fall under whatever
criteria we  adopt, but  various extensions might  fail to fall  under those
criteria.  The draft  seems to require that these  extensions be treated the
same way as  the base protocol.  This  just doesn't make any sense  to me at
all. 

There are numerous cases where someone  wants to add a field to some routing
protocol, not to  affect routing, but because the  information in that field
needs to be delivered to a set  of routers, and the routing protocol will do
that.  There's no  reason why these fields should be  considered to be "core
internet protocol". (See above re PWE3 LDP extensions.)

I could of  course imagine someone arguing that  tunneling protocols do need
to be included,  because one can run routing through  the tunnels, and hence
failure of the  tunneling mechanisms can impact the  overall routing system.
If one made  this argument, not even IPsec would be  immune from the special
routing requirements.  

As things  stand now, the  vagueness of the  criteria, and the  inability to
apply criteria  specifically to  extensions, result in  a lot of  extra work
which  is basically useless,  and only  serves to  delay the  progression of
various drafts. 

Now, as to the issue of "two independent implementations", I think the whole
discussion of this area has been somewhat confused.

We  have  just  published a  new  BGP  spec  as  DS.  How  many  independent
implementations of BGP were written from this spec?  We are about to publish
a new  PIM-SM spec  as PS.  How  many independent implementations  of PIM-SM
were  written from  this spec?   Hey, forget  about "independent",  how many
implementations at  all were  actually written from  either of  these specs?
Isn't it  really the  case that  these specs were  written to  correspond to
existing  implementations, rather  than the  other way  around?  If  we were
really  serious about  "proving" the  quality of  the spec  with independent
implementations,  we wouldn't consider  implementations that  existed before
the  spec was  complete,  rather  we'd look  for  implementations that  were
written from  scratch after the spec  was complete.  We'd also  have to make
sure that  the new implementations  were done by  folks who had  no previous
experience with  the protocol, and we'd  have to make sure  that those folks
had  no contact with  the developers  of the  spec.  And  if there  were any
interoperability problems  as a result, we'd  have to start  the process all
over again.

Frankly, I  don't know how  we would  find someone to  sponsor a BGP  or PIM
implementation to  be done directly  from the spec,  by folks with  no prior
knowledge of an implementation; I doubt there are two completely independent
implementations of either one.  Usually if a company needs an implementation
of some  protocol, they try  to find someone  who's done it before,  and who
knows how  to make  it interoperable with  the major deployments,  no matter
what the spec says.  In fact, any implementor who's earning his pay would at
least  look at  an  open source  or  other reference  implementation of  the
protocol,  if one  is available.   But then  his implementation  wouldn't be
independent, would it?

I  think it  might  make sense  to say  that  we don't  want to  standardize
something unless there is running code (i.e., one implementation) and enough
independent review to give us confidence that the spec is adequate.  Even so
I wouldn't  apply this to  every last little  feature of some  protocol, but
only to "major features" (however we choose to define that).  

With regard to  the necessary "paperwork", perhaps we  really need different
processes   for  things   that  already   have   multi-vendor  interoperable
deployments than we do for things are  really new.  I can cite some cases of
specs  that still  haven't made  it through  the IETF  process,  even though
multiple interoperable implementations have been widely deployed for five or
six years.  It's very difficult in such cases to produce "test scenarios and
test  results showing that  the major  features of  the protocols  have been
tested".  This  is very different than the  case where we really  have a new
protocol and the  bake-off was last week. Failure  to "officially" recognize
these  two different  cases  is the  source  of much  red  tape and  useless
effort.  It's also very difficult  to determine from this draft exactly what
one  has to  provide in  order to  be  sure that  one has  provided all  the
necessary paperwork.

Another confusing  thing about the document is  the way it applies  a set of
requirements  to  "routing  area  submissions"  and  an  "elevated  set"  of
requirements to protocols that  meet certain criteria, regardless of whether
they fall in the routing area or not.  I don't think that the different IETF
areas should have special  rules that apply to a WG just  because a WG is in
that area, irrespective of the actual content of the work. 

On the  other hand, by trying  apply some special  requirements to protocols
developed outside the  routing area, the routing ADs seem  to be saying that
they have the right to interfere  in the progress of other areas' WGs, based
on solely on their own judgment as to whether protocols in those other areas
meet some  vague set of  criteria developed by  the routing ADs.   Sure, the
Security ADs already practice this  kind of interference on a regular basis,
but I'm  not at  all sure that  it is  a good thing.   (Hmmm, maybe  what we
really need is  to require a "routing considerations"  section in every spec
;-)) 

Given all  the above, I'd have  to say that  this document is not  ready for
prime time.   I think  the criteria for  "elevated requirements" need  to be
specified a lot  more clearly, the elevated requirements  themselves need to
be a  lot more reasonable, and the  paperwork requirements need to  be a lot
clearer. 

Of  course, one  could actually  ask the  higher level  question  of whether
special requirements for selected protocols  are really necessary at all.  I
don't think  the draft even  tries to  make a case  for this.  It  just says
"some protocols are  special, so the bar should be  higher".  No evidence is
presented to show that the bar needs  to be higher, this is simply stated as
if no one would ever question it. 

Given that the biggest threats to the Internet (broadly construed) today are
computer viruses, spam, enduser  security, etc., perhaps endsystem protocols
really need more attention than BGP extensions! 











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



From routing-discussion-bounces@ietf.org Fri Feb 17 21:59:25 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1FAIJh-0001Vx-5X; Fri, 17 Feb 2006 21:59:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1FAIJf-0001Vr-Op
	for routing-discussion@megatron.ietf.org;
	Fri, 17 Feb 2006 21:59:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14556
	for <routing-discussion@ietf.org>; Fri, 17 Feb 2006 21:57:34 -0500 (EST)
Received: from relay03.pair.com ([209.68.5.17])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FAIY9-0002bm-Tw
	for routing-discussion@ietf.org; Fri, 17 Feb 2006 22:14:26 -0500
Received: (qmail 65314 invoked from network); 18 Feb 2006 02:59:17 -0000
Received: from unknown (HELO workhorse.faster-light.net) (unknown)
	by unknown with SMTP; 18 Feb 2006 02:59:17 -0000
X-pair-Authenticated: 69.37.59.162
Received: from workhorse.faster-light.net (localhost.faster-light.net
	[127.0.0.1])
	by workhorse.faster-light.net (8.12.11/8.12.11) with ESMTP id
	k1I32fgA001748; Fri, 17 Feb 2006 22:02:41 -0500 (EST)
	(envelope-from curtis@workhorse.faster-light.net)
Message-Id: <200602180302.k1I32fgA001748@workhorse.faster-light.net>
To: erosen@cisco.com
In-reply-to: Your message of "Fri, 17 Feb 2006 13:39:29 EST."
	<200602171839.k1HIdUPM019907@rtp-core-1.cisco.com> 
Date: Fri, 17 Feb 2006 22:02:41 -0500
From: Curtis Villamizar <curtis@faster-light.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: Alex Zinin <zinin@psg.com>, routing-discussion@ietf.org
Subject: Re: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt 
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>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org


In message <200602171839.k1HIdUPM019907@rtp-core-1.cisco.com>
Eric Rosen writes:
>  
>  
>       The IESG may require implementation and/or operational
>       experience prior to granting Proposed Standard status to a
>       specification that materially affects the core Internet
>       protocols or that specifies behavior that may have significant
>       operational impact on the Internet.

I really can't see how the above could be more clear unless you asked
a lawyer to pick it apart.  I hope we haven't come to that.

If we were lawyers (or professional standards body meeting attendees)
we could argue this forever and just keep raking in the fees.

This gives the IESG the responsibility to interpret when to apply
this criteria.

> We have just published a new BGP spec as DS.  How many independent
> implementations of BGP were written from this spec?  We are about to
> publish a new PIM-SM spec as PS.  How many independent implementations
> of PIM-SM were written from this spec?

Nowhere does it say that existing implementations have to be tossed
and new ones written from scratch after the spec was completed.

> Given that the biggest threats to the Internet (broadly construed)
> today are computer viruses, spam, enduser security, etc., perhaps
> endsystem protocols really need more attention than BGP extensions!

Ending your argument with FUD?  Perhaps better attention is needed to
the end systems themselves.  The IETF didn't plant any open ports for
MS-Access or Active-X in Windows or help write the browser bugs or
bugs in MS-Outlook.  E-mail is actually traceable to the sending
*machine*.  The only problem with that is the end systems are so full
of security holes that tracing to the sending machine is of little
help in tracing back to the "bot" author that is the actual sender.
Maybe we just need to find a way to ban Microsoft product from the
Internet and we'd have little or no viruses, spam, etc.  That's off
topic for this thread though.

Curtis

ps - Chages that make the "running code" requirement stronger are good
for the IETF and good for the Internet and Internet protocols.  Those
requirements may be bad for professional standards body meeting
attendees who want their name on lots of "standards" whether they get
implemented or not.  Those people should go to ITU meetings.

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



From routing-discussion-bounces@ietf.org Sat Feb 18 15:15:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FAYU5-0001Rb-Mq; Sat, 18 Feb 2006 15:15:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FAYU5-0001RW-2Y
	for routing-discussion@ietf.org; Sat, 18 Feb 2006 15:15:13 -0500
Received: from mail-red.research.att.com ([192.20.225.110]
	helo=mail-white.research.att.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FAYU3-0006m3-T9
	for routing-discussion@ietf.org; Sat, 18 Feb 2006 15:15:13 -0500
Received: from bright.research.att.com (bright.research.att.com
	[135.207.20.189])
	by mail-green.research.att.com (Postfix) with ESMTP id 9FDED878C;
	Sat, 18 Feb 2006 15:15:11 -0500 (EST)
Received: (from fenner@localhost)
	by bright.research.att.com (8.12.11/8.12.10/Submit) id k1IKFBrh012949; 
	Sat, 18 Feb 2006 12:15:11 -0800
From: Bill Fenner <fenner@research.att.com>
Message-Id: <200602182015.k1IKFBrh012949@bright.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: Christian Hopps <chopps@rawdofmt.org>
References: <914383237.20060216100230@psg.com>
	<C842E8F4-27C3-460F-89CB-7D5A47D26BE8@rawdofmt.org>
Date: Sat, 18 Feb 2006 12:15:11 -0800
Versions: dmail (linux) 2.7/makemail 2.14
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: routing-discussion@ietf.org
Subject: Re: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt
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


>4.1 Proposed Standard
>    4.  Two or more independent interoperable implementations must  
>exist.
>
>4.2 Draft Standard
>    4.  Two or more interoperable implementations must exist.  At least
>        two must be written independently.
>
>Is there a difference of meaning here, rather than just words?

Good catch, Chris.  4.1's #4 was changed from "One or more" to "Two
or more independent" without noticing the inconsistency with 4.2's #4.
I'll copy 4.2's version back over to 4.1.

  Bill

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



From routing-discussion-bounces@ietf.org Sun Feb 19 04:13:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FAkd8-0007at-8o; Sun, 19 Feb 2006 04:13:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FAkd6-0007ao-LO
	for routing-discussion@ietf.org; Sun, 19 Feb 2006 04:13:20 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FAkd5-0002pA-Cv
	for routing-discussion@ietf.org; Sun, 19 Feb 2006 04:13:20 -0500
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by sj-iport-1.cisco.com with ESMTP; 19 Feb 2006 01:13:19 -0800
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k1J9DFST011544;
	Sun, 19 Feb 2006 01:13:16 -0800 (PST)
Received: from [212.254.247.4] (ams-clip-vpn-dhcp166.cisco.com [10.61.64.166])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k1J9G7ad030232;
	Sun, 19 Feb 2006 01:16:08 -0800
Message-ID: <43F836A9.1070008@cisco.com>
Date: Sun, 19 Feb 2006 10:13:13 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 1.5 (Macintosh/20051201)
MIME-Version: 1.0
To: curtis@faster-light.net
References: <200602180302.k1I32fgA001748@workhorse.faster-light.net>
In-Reply-To: <200602180302.k1I32fgA001748@workhorse.faster-light.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=955; t=1140340569; x=1140772769;
	c=relaxed/simple; s=nebraska;
	h=Subject:From:Date:Content-Type:Content-Transfer-Encoding:Mime-Version;
	d=cisco.com; i=lear@cisco.com; z=From:Eliot=20Lear=20<lear@cisco.com>
	|Subject:Re=3A=20Last=20Call=3A=20draft-fenner-zinin-rtg-standard-reqts-01.txt
	|To:=20curtis@faster-light.net;
	X=v=3Dmtcc.com=3B=20h=3DbSdKmUhieflnoeWpmqxoeu7uuq4=3D;
	b=TFHNkDlN4n1AvNvjOUJo+0l55CxAVDOJyA7R9ihJdCfsxeGIP4U2ccSsPwAlKCz0WD4Rmy48
	I+C3vxwYM9gFdoGoaUUxORDK6iXHlI+n0+6nGIH2H+/gYEQO5wPGAZda9tBSIVRI8ulRG2o2HWE
	2tnAqPMWn78PuLA2kYHa/AnI=;
Authentication-Results: imail.cisco.com; header.From=lear@cisco.com;
	dkim=pass ( message from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: Alex Zinin <zinin@psg.com>, erosen@cisco.com, routing-discussion@ietf.org
Subject: Re: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt
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 Villamizar wrote:
> In message <200602171839.k1HIdUPM019907@rtp-core-1.cisco.com>
> Eric Rosen writes:
>   
>>  
>>  
>>       The IESG may require implementation and/or operational
>>       experience prior to granting Proposed Standard status to a
>>       specification that materially affects the core Internet
>>       protocols or that specifies behavior that may have significant
>>       operational impact on the Internet.
>>     
>
> I really can't see how the above could be more clear unless you asked
> a lawyer to pick it apart.  I hope we haven't come to that.
>   

We have.  Get over it.  The statement is clearly intended for lawyers. 
Why otherwise would they need to make such a statement in the first
place?  Would we otherwise be saying that the IESG couldn't stop a
standard they considered risky?  And we've seen plenty of bad BGP actors
over the years with or without an RFC to back them up.

Eliot

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



From routing-discussion-bounces@ietf.org Sun Feb 19 13:48:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1-ext.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FAtbf-0005fv-MT; Sun, 19 Feb 2006 13:48:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FAtbe-0005fo-OH
	for routing-discussion@ietf.org; Sun, 19 Feb 2006 13:48:26 -0500
Received: from mail-red.research.att.com ([192.20.225.110]
	helo=mail-white.research.att.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FAtbe-0001V9-E4
	for routing-discussion@ietf.org; Sun, 19 Feb 2006 13:48:26 -0500
Received: from bright.research.att.com (bright.research.att.com
	[135.207.20.189])
	by mail-blue.research.att.com (Postfix) with ESMTP id AC730147D6C;
	Sun, 19 Feb 2006 13:48:03 -0500 (EST)
Received: (from fenner@localhost)
	by bright.research.att.com (8.12.11/8.12.10/Submit) id k1JIm389018796; 
	Sun, 19 Feb 2006 10:48:03 -0800
From: Bill Fenner <fenner@research.att.com>
Message-Id: <200602191848.k1JIm389018796@bright.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: erosen@cisco.com
Date: Sun, 19 Feb 2006 10:48:03 -0800
Versions: dmail (linux) 2.7/makemail 2.14
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Cc: Alex Zinin <zinin@psg.com>, routing-discussion@ietf.org
Subject: Re: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt
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 have many concerns about this document. 
>
>Beginning with the statement: 
>
> The IESG may require implementation and/or operational experience
> prior to granting Proposed Standard status to a specification that
> materially affects the core Internet protocols or that specifies
> behavior that may have significant operational impact on the
> Internet.

I'm sorry, I'm a bit confused here - you have a concern that this
document quotes RFC2026, or you have a concern with the statement
that appears in RFC2026?

>The first problem is that there is never a clear set of criteria given for
>identifying "core internet protocols". The second problem is that there is
>never a clear set of criteria for whether some specification "materially
>affects" a core internet protocol. 

This document, especially section 3, is intended to give some
criteria. Under the RFC1264 rules, we didn't even have this,
so we picked and chose when to apply the rules ourselves, which
of course is only a problem when we're wrong ;-)

>For instance, I would really like to understand why DNS is not a core
>Internet protocol but LDP and RSVP are.

I've heard Internet ADs ask the same question, and the answer is
basically "nobody's gotten around to writing something like 1264
for any other protocols". Are you arguing that routing protocols
shouldn't be considered core Internet protocols, and perhaps we
should just reclassify RFC1264 as historic, or that this document
should cover other types of protocols, or that someone else should
work on another document to cover those other types of protocols,
or what?

>Which leads to the next problem: there are a number of protocols which are
>sometimes used for setting up forwarding state in the routers, and sometimes
>for other purposes. That is, the base protocol might fall under whatever
>criteria we adopt, but various extensions might fail to fall under those
>criteria. The draft seems to require that these extensions be treated the
>same way as the base protocol.

Do you have a suggestion for how to classify these objectively? We've
had trouble with subjective rules, which is why we settled on the
objective "same as the base protocol".

>As things stand now, the vagueness of the criteria, and the inability to
>apply criteria specifically to extensions, result in a lot of extra work
>which is basically useless, and only serves to delay the progression of
>various drafts. 

By "now", do you mean "with the RFC1264 rules", or "with the
draft-fenner-zinin rules"? We tried to make the criteria a lot more
concrete in our draft.

>Hey, forget about "independent", how many
>implementations at all were actually written from either of these specs?

Actually, while one implementation was written during the development of
the new PIM spec, I'm aware of at least one that was written from the 
spec. (And we got a lot of spec bug reports from that author, validating
the theory that you learn about the clarity of the spec when you implement
from it.)

>It's also very difficult to determine from this draft exactly what
>one has to provide in order to be sure that one has provided all the
>necessary paperwork.

We wrote the checklists in section 5 specifically to address this problem.
E.g., if you're submitting for Proposed Standard, if you've got the
7 items listed in section 5.1 bullet points 1. - 7., then you can be
pretty sure that you've provided all the necessary paperwork.

If this is confusing, can you suggest a better way to present
this information?

>I don't think that the different IETF
>areas should have special rules that apply to a WG just because a WG is in
>that area, irrespective of the actual content of the work. 

I agree with this, but during development of this draft we thought
the consensus of the area was otherwise.  If consensus is with us then
we can remove this requirement.

>On the other hand, by trying apply some special requirements to protocols
>developed outside the routing area, the routing ADs seem to be saying that
>they have the right to interfere in the progress of other areas' WGs, based
>on solely on their own judgment as to whether protocols in those other areas
>meet some vague set of criteria developed by the routing ADs.

If it's a routing protocol, there are already additional requirements,
described in RFC 1264.  Again, we tried to make the criteria in
draft-fenner-zinin more concrete than the ones in 1264, but of course
it's not easy to come up with one complete answer.

>I think the criteria for "elevated requirements" need to be
>specified a lot more clearly

Do you have any suggestions?  What's unclear about the current
formulation?

>the elevated requirements themselves need to be a lot more reasonable

Which parts do you find unreasonable?

>and the paperwork requirements need to be a lot clearer. 

Again, I can't understand this comment.  What is unclear about the
checklist of required items?

>Of course, one could actually ask the higher level question of whether
>special requirements for selected protocols are really necessary at all. I
>don't think the draft even tries to make a case for this. It just says
>"some protocols are special, so the bar should be higher". No evidence is
>presented to show that the bar needs to be higher, this is simply stated as
>if no one would ever question it. 

I believe that the paragraph at issue is a quote from RFC 2026, and you're
right, we don't try to justify that paragraph's existence in that RFC.

  Bill

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



From routing-discussion-bounces@ietf.org Mon Feb 20 11:47:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FBECL-0003vp-Ry; Mon, 20 Feb 2006 11:47:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FBECL-0003vd-9G
	for routing-discussion@ietf.org; Mon, 20 Feb 2006 11:47:41 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBECK-0004ze-Ts
	for routing-discussion@ietf.org; Mon, 20 Feb 2006 11:47:41 -0500
Received: from rtp-core-2.cisco.com ([64.102.124.13])
	by rtp-iport-2.cisco.com with ESMTP; 20 Feb 2006 11:47:41 -0500
X-IronPort-AV: i="4.02,131,1139202000"; 
	d="scan'208"; a="82779116:sNHT34358076"
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k1KGlcLN018233; 
	Mon, 20 Feb 2006 11:47:39 -0500 (EST)
Message-Id: <200602201647.k1KGlcLN018233@rtp-core-2.cisco.com>
To: Bill Fenner <fenner@research.att.com>
In-reply-to: Your message of Sun, 19 Feb 2006 10:48:03 -0800.
	<200602191848.k1JIm389018796@bright.research.att.com> 
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Mon, 20 Feb 2006 11:47:38 -0500
From: Eric Rosen <erosen@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Cc: Alex Zinin <zinin@psg.com>, routing-discussion@ietf.org
Subject: Re: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt 
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'm sorry, I'm a bit confused here - you have a concern that this
> document quotes RFC2026, or you have a concern with the statement
> that appears in RFC2026? 

Yes, to both. 

> This document, especially section 3, is intended to give some
> criteria. Under the RFC1264 rules, we didn't even have this,
> so we picked and chose when to apply the rules ourselves, which
> of course is only a problem when we're wrong ;-)

Well, "everything from  a routing area WG" is a  clear enough criterion, but
it selects many things that don't seem to be crucial to the operation of the
Internet, that  don't seem to be  "core internet protocols",  and that might
not even be technically classified as "routing".  Rather than clarifying the
criteria  for which  submissions need  special  treatment, it  gives up  and
proposes to apply special treatment to  stuff that just doesn't seem to need
it. 

E.g., it's rather difficult to see why every minor change to a BGP attribute
needs special treatment. 

Various peculiar and  time-wasting things really do happen  when these rules
are  enforced.  To take  a recent  case, IPv6-specific  extended communities
were added to the BGP extended communities spec in order to satisfy the rule
that IPv6 not  be ignored.  Then they were removed to  satisfy the rule that
anything not implemented has to be removed.  This is just making the authors
run around in circles.  It's hard to see how the presence or absence of this
kind of  extended community in the spec  makes any difference at  all to the
health of the Internet.  

With regard to  the other criterion in section  3, "protocols implementing a
distributed algorithm  whose functional domain  spans more than  one network
segment ... or otherwise affects the state of the distributed routing system
or per-hop forwarding behavior", let's see how clear this is. 

It seems to me that the "distributed algorithm" criterion as stated includes
such things as: 

- Bittorrent  (if we might  suppose for a  moment that that would  ever fall
  under the IETF's purview)

- Web-caching and proxying protocols (e.g., akamai)

- DNS

- Mail

- SETI

Is it your  intention that the criterion include such  things?  If not, then
it's not clear what it is meant to include. 

The "per-hop forwarding behavior" criterion would include anything having to
do with per-hop QoS treatment (Diffserv, RSVP).  Is that your intention? 

If these  criteria are taken literally,  they greatly increase  the scope of
the routing ADs to make demands  on submissions from other area.  This would
put the routing ADs on a par with the security ADs in terms of their ability
to delay progress.

The "functional domain spans more than one network segment (link)" criterion
confuses me.   Does this mean that  special requirements are  not needed for
those protocols which provide  distributed algorithms that affect forwarding
state, but  which don't have  a "functional domain"  of more than  one link?
What would be an example of such a protocol? 

> Are you arguing that routing protocols
> shouldn't be considered core Internet protocols, and perhaps we
> should just reclassify RFC1264 as historic, or that this document
> should cover other types of protocols, or that someone else should
> work on another document to cover those other types of protocols,
> or what? 

I  don't think a  clear distinction  has been  drawn between  "core internet
protocols" and others, and I don't think a good case has been made that core
internet  protocols need special  treatment, or  that the  special treatment
that  they've been  given  has made  any  difference to  the  health of  the
Internet.  

In  general,  I  do  not  favor   adding  more  red  tape  to  the  process.
Reclassifying 1264 has historical might be a good move though. 

> Do  you  have  a  suggestion   for  how  to  classify  these  [extensions]
> objectively?  We've  had trouble  with subjective rules,  which is  why we
> settled on the objective "same as the base protocol"

If the criteria applied to the base protocol were really clear and technical
(i.e., based on  technical characteristics of the base  protocol rather than
which Area its WG belongs to),  then why wouldn't the same criteria would be
applicable to the extensions. 

> By "now", do you mean "with the RFC1264 rules", or "with the
> draft-fenner-zinin rules"? We tried to make the criteria a lot more
> concrete in our draft. 

When I complain about how things are working "now", I mean with whatever set
of rules the ADs are now applying.  

I think  the draft-fenner-zinin  rules make things  worse, as it  seems that
they  try to  require special  treatment for  more things,  rather  than for
fewer.  Maybe that's the problem in a nutshell. 

> while one implementation was written during the development of the new PIM
> spec, I'm aware of at least one that was written from the spec

I guess I  should only have mentioned the  BGP spec as an example  of a spec
that no one's every done an implementation from ;-)

> And we got a lot of spec bug reports from that author, validating
> the theory that you learn about the clarity of the spec when you implement
> from it

That theory is not in dispute! 

> if you've  got the 7 items  listed in section  5.1 bullet points 1.  - 7.,
> then  you  can be  pretty  sure that  you've  provided  all the  necessary
> paperwork. 

The terms "implementation  experience", "interoperability report", and "test
scenarios and test  results" are not very clear to me.   If you haven't done
this before,  I'm not  sure there is  anyplace you  can look that  tells you
exactly what is required.  And in  many cases, it seems nearly impossible to
produce this sort  of stuff.  E.g., when you're  advancing a spec describing
implementations that have been deployed and interoperating for 5 or 6 years,
it's very hard  to produce anything like "test  scenarios and test results".
That's why I think the paperwork requirements are not particularly clear. 







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



From routing-discussion-bounces@ietf.org Mon Feb 20 12:11:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FBEZB-0006Un-Qo; Mon, 20 Feb 2006 12:11:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FBEZ9-0006Ue-Lc
	for routing-discussion@ietf.org; Mon, 20 Feb 2006 12:11:15 -0500
Received: from mail-red.research.att.com ([192.20.225.110]
	helo=mail-white.research.att.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBEZ9-0005YH-EC
	for routing-discussion@ietf.org; Mon, 20 Feb 2006 12:11:15 -0500
Received: from bright.research.att.com (bright.research.att.com
	[135.207.20.189])
	by mail-green.research.att.com (Postfix) with ESMTP id 322958674;
	Mon, 20 Feb 2006 12:11:15 -0500 (EST)
Received: (from fenner@localhost)
	by bright.research.att.com (8.12.11/8.12.10/Submit) id k1KHBFSt015800; 
	Mon, 20 Feb 2006 09:11:15 -0800
From: Bill Fenner <fenner@research.att.com>
Message-Id: <200602201711.k1KHBFSt015800@bright.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: erosen@cisco.com
Date: Mon, 20 Feb 2006 09:11:15 -0800
Versions: dmail (linux) 2.7/makemail 2.14
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: Alex Zinin <zinin@psg.com>, routing-discussion@ietf.org
Subject: Re: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt
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'm sorry, I'm a bit confused here - you have a concern that this
>> document quotes RFC2026, or you have a concern with the statement
>> that appears in RFC2026? 
>
>Yes, to both. 

I guess I still don't understand.  Would it be correct to say that
your position is that the IESG should not be permitted to require
implementation and/or operational experience prior to granting
Proposed Standard, period?

>Well, "everything from  a routing area WG" is a  clear enough criterion, but
>it selects many things that don't seem to be crucial to the operation of the
>Internet, that  don't seem to be  "core internet protocols",  and that might
>not even be technically classified as "routing".  Rather than clarifying the
>criteria  for which  submissions need  special  treatment, it  gives up  and
>proposes to apply special treatment to  stuff that just doesn't seem to need
>it. 

I already said that I agreed with you that that particular criteron
should be changed.

>Various peculiar and  time-wasting things really do happen  when these rules
>are  enforced.  To take  a recent  case, IPv6-specific  extended communities
>were added to the BGP extended communities spec in order to satisfy the rule
>that IPv6 not  be ignored.

There was no draft-ietf-idr-bgp-ext-communities-* published with
IPv6-specific extended communities.  Are you thinking of 4-byte ASes,
which were in the spec from the beginning (or, at least, from
draft-ramachandra-bgp-ext-communities-08, which is the oldest version
I have)?

>In  general,  I  do  not  favor   adding  more  red  tape  to  the  process.
>Reclassifying 1264 has historical might be a good move though. 

That was the position that I started with, and got lots of pushback
from both open routing area meetings and on this list.

>I think  the draft-fenner-zinin  rules make things  worse, as it  seems that
>they  try to  require special  treatment for  more things,  rather  than for
>fewer.  Maybe that's the problem in a nutshell. 

Well, it's really trying to clarify the rules that we've been trying to
use to apply RFC 1264.  So in a way it's like the new BGP spec - trying
to document current practice, not introduce new practice.

>The terms "implementation  experience", "interoperability report", and "test
>scenarios and test  results" are not very clear to me.   If you haven't done
>this before,  I'm not  sure there is  anyplace you  can look that  tells you
>exactly what is required.  And in  many cases, it seems nearly impossible to
>produce this sort  of stuff.  E.g., when you're  advancing a spec describing
>implementations that have been deployed and interoperating for 5 or 6 years,
>it's very hard  to produce anything like "test  scenarios and test results".
>That's why I think the paperwork requirements are not particularly clear. 

Thanks for the concrete feedback.

  Bill

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



From routing-discussion-bounces@ietf.org Tue Feb 21 12:47:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FBbbJ-0006N5-96; Tue, 21 Feb 2006 12:47:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FBbbI-0006Mv-Q8
	for routing-discussion@ietf.org; Tue, 21 Feb 2006 12:47:00 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBbbI-0006c3-Ip
	for routing-discussion@ietf.org; Tue, 21 Feb 2006 12:47:00 -0500
Received: from rtp-core-2.cisco.com ([64.102.124.13])
	by rtp-iport-1.cisco.com with ESMTP; 21 Feb 2006 09:47:00 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.02,135,1139212800"; 
	d="scan'208"; a="22337223:sNHT22811728"
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k1LHkvLN015431; 
	Tue, 21 Feb 2006 12:46:58 -0500 (EST)
Message-Id: <200602211746.k1LHkvLN015431@rtp-core-2.cisco.com>
To: Bill Fenner <fenner@research.att.com>
In-reply-to: Your message of Mon, 20 Feb 2006 09:11:15 -0800.
	<200602201711.k1KHBFSt015800@bright.research.att.com> 
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Tue, 21 Feb 2006 12:46:57 -0500
From: Eric Rosen <erosen@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: Alex Zinin <zinin@psg.com>, routing-discussion@ietf.org
Subject: Re: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt 
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

Bill> Would it be correct to say  that your position is that the IESG should
Bill> not  be   permitted  to  require   implementation  and/or  operational
Bill> experience prior to granting Proposed Standard, period? 

With regard to operational experience, I think that a standards organization
is not really in a position  to determine whether there has been an adequate
amount  of operational  experience with  some protocol  to  draw conclusions
about the viability of the protocol. 

With regard to implementation, I  tend to think that the useful requirements
are too  subtle and case-specific to  lend themselves to  enforcement by the
process.  If a mechanism is well-understood,  having it in a PS is okay even
if there  aren't any existing implementations.   If the mechanism  is not so
well-understood,  one  may  want  to  hold  it back  or  to  publish  it  as
experimental.  I think  the WG itself might be the best  place to make these
decisions.  It  does seem useful to  have a process for  removing stuff that
hasn't  been  implemented  ever after  six  or  seven  years, but  that's  a
different issue. 

Bill> There was no draft-ietf-idr-bgp-ext-communities-* published with
Bill> IPv6-specific extended communities.  Are you thinking of 4-byte ASes,

Yes, sorry.  Luckily the attribute is  not long enough to hold a v6 address,
otherwise it would have definitely been  put in (due to the "requirement" to
support IPv6) and then taken out again (due to lack of implementation).

Bill> which  were  in  the spec  from  the  beginning  (or, at  least,  from
Bill> draft-ramachandra-bgp-ext-communities-08, which  is the oldest version
Bill> I have)? 

Hey, that means there were eight earlier versions ;-) 

Eric> In  general, I  do not  favor  adding more  red tape  to the  process.
Eric> Reclassifying 1264 to historical might be a good move though.

Bill> That was the position that I started with, and got lots of pushback
Bill> from both open routing area meetings and on this list.

I have noticed  that when one sets  a committee to the task  of reducing the
amount of red  tape, the result is  likely to be an increased  amount of red
tape instead.  

I think  that the folks who  want more process and  more requirements should
point out  the facts to  show that the  extra process and  requirements have
made  a big difference.   Unsubstantiated opinions  do not  gain credibility
through multiplication.

> Well, it's really trying to clarify the rules that we've been trying to
> use to apply RFC 1264.  So in a way it's like the new BGP spec - trying
> to document current practice, not introduce new practice. 

Well, once  it's published  as a BCP,  folks will  think that these  are the
real, set in stone rules, not merely what the current crop of ADs are trying
to do. That is a significant difference.

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



From routing-discussion-bounces@ietf.org Wed Feb 22 09:01:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FBuYZ-0005bx-Hw; Wed, 22 Feb 2006 09:01:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FBuYY-0005bk-8Y
	for routing-discussion@ietf.org; Wed, 22 Feb 2006 09:01:26 -0500
Received: from relay1.mail.uk.clara.net ([80.168.70.141])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBuYV-0004MH-Qv
	for routing-discussion@ietf.org; Wed, 22 Feb 2006 09:01:26 -0500
Received: from du-069-0121.access.clara.net ([217.158.132.121] helo=Puppy)
	by relay1.mail.uk.clara.net with esmtp (Exim 4.46)
	id 1FBuYS-000NTX-HK
	for routing-discussion@ietf.org; Wed, 22 Feb 2006 14:01:22 +0000
Message-ID: <071b01c637b9$099672d0$33849ed9@Puppy>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <routing-discussion@ietf.org>
References: <200602211746.k1LHkvLN015431@rtp-core-2.cisco.com>
Date: Wed, 22 Feb 2006 13:16:07 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Subject: Re: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt 
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

Hi,

I think my opposition to the direction of this I-D has been aired, and I
don't need to repeat my general case. I believe that the increased hurdle
to PS will either gum up the WGs or will simply cause everything to be
published as Experimental.

But here are some specific points about this I-D which I don't think was
ready for last call and doesn't appear to have had any significant review
(including perhaps by the Routing Area Directorate?)

Eric and Bill's conversation has brought up a point by mentioning IPv6.

Let us imagine a widely implemented and deployed signlaing protocol. It is
an IETF requirement that such protocol specifications include IPv6. This
is no problem form the point of view of specification, and would be easy
to implement, but the fact is that it is not implemented because no-one is
building or deploying networks that use IPv6 in conjunction with this
protocol (they may do in the future, but they are not doing so now).

What will happen to the publication request for the I-D that specifies
this protocol? We will not be able to say that the protocol specification
has been fully implemented, and there certainly will not be any
operational experience. Will this result in the RFC publication being help
up? Does it mean that the I-D must be split into two parts before the main
body can move forwards?


The I-D does not state a proposed status.

In section 3.2 you have (the much discussed)
   In consultation with the community, the IESG MAY decide to waive some
   or all of the requirements specified in this document.  A situation
   where this might be needed is when factors not envisioned in this
   document arise and applying elevated requirements does more harm than
   good.
Why are you making this a full IESG decision? Isn't it enought to delegate
it to the Routing Area ADs?

Section 4.1 point 2 (and through out). Please say MIB *module* not MIB.

Section 4.1 point 4. What is an interoperable implementation of a MIB
module?

Progression to DS or S is dependent on implementation and deployment of
associated MIB modules. I think you are setting yourself up for failure
and not recognising the way the world is moving wrt SNMP. While the
specification of the MIB modules is highly desireable, you may find that
certain protocols do not see wide uptake of SNMP as a management
technique. Do you propose that such protocols can never become standards,
or will you invoke section 3.2? (If section 3.2 is to be so easily invoked
we might as well dispose of this I-D and immediately hand all decisions to
the IESG!)

Section 5.1 seems at odds with the details in the Proto work. Can I
suggest that you converge on a common set of information to be supplied at
publication-request time so that the WG chairs do not have to fiddle about
collecting different information for different I-D processing procedures.

Section 5. point 2
This is a change the order of events since previously it has been the ADs
that have requested the RAD to review documents.
Please supply details of how the review is actually initiated, how the
progress of the review is tracked, and how the comments are returned to
the working group.

Section 5. point 3
A little more detail about the submission and publication of the
implementation and interoperability report would be helpful. Is this an
email to the IETF secretariat? Or perhaps it is an I-D? Where on the IETF
Web site will this be publicly available?

Section 5 is missing MIB Doctor review

Section 5 is missing appropriate cross-area and cross-WG review.

Section 5.1 says "IETF secretariat" and then lists the IESG Secretary's
email address. (See Section 5 point 3)

Long-term persistence of reports.
In several cases we are required to submit reports (implementation,
interoperability, operational experience, etc.). What is the archival
process for this? If they are submitted as I-Ds will they be published as
Informational RFCs to preserve them, or is some other archive proposed?

Section 8 seems to be a tiny bit empty. I'm surprised to see a last call
with that problem :-)

Use of RFC2119 language. This may or may not be appropriate in this I-D.
But if you use it you must include 2119 as a reference and use the normal
2119 boilerplate.

Thanks,
Adrian


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



From routing-discussion-bounces@ietf.org Wed Feb 22 11:11:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FBwaF-0003NB-VM; Wed, 22 Feb 2006 11:11:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FBwaE-0003N3-1x
	for routing-discussion@ietf.org; Wed, 22 Feb 2006 11:11:18 -0500
Received: from gateout01.mbox.net ([165.212.64.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBwaB-0001jL-HY
	for routing-discussion@ietf.org; Wed, 22 Feb 2006 11:11:18 -0500
Received: from gateout01.mbox.net (gateout01.mbox.net [165.212.64.21])
	by gateout01.mbox.net (Postfix) with ESMTP id BCF991DE9;
	Wed, 22 Feb 2006 16:11:13 +0000 (GMT)
Received: from gateout01.mbox.net [127.0.0.1] by gateout01.mbox.net via mtad
	(C8.MAIN.3.27E) 
	with ESMTP id 873kBVqLk0481Mo1; Wed, 22 Feb 2006 16:11:12 GMT
Received: from gateout01.mbox.net [127.0.0.1] by gateout01.mbox.net via mtad
	(C8.MAIN.3.27E) 
	with ESMTP id 868kBVqLi0481Mo1; Wed, 22 Feb 2006 16:11:09 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.27I); Wed, 22 Feb 2006 16:11:08 GMT
X-USANET-Source: 165.212.116.254 IN   skh@nexthop.com GW1.EXCHPROD.USA.NET
X-USANET-MsgId: XID877kBVqLJ9459Xo1
Received: from VS4.EXCHPROD.USA.NET ([10.116.208.141]) by GW1.EXCHPROD.USA.NET
	with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 22 Feb 2006 09:11:08 -0700
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, 22 Feb 2006 09:11:06 -0700
Message-ID: <6F44D7F6B24A8F4DA0AB46C9BE924F0203776589@VS4.EXCHPROD.USA.NET>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt 
Thread-index: AcY2Pbw/Qcs5ZDWVQYO2v+4O5MNkKgBjDmoQ
From: "Susan Hares" <skh@nexthop.com>
To: <erosen@cisco.com>, "Bill Fenner" <fenner@research.att.com>
X-OriginalArrivalTime: 22 Feb 2006 16:11:08.0535 (UTC)
	FILETIME=[97251870:01C637CA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a4a24b484706be629f915bfb1a3e4771
Cc: Alex Zinin <zinin@psg.com>, routing-discussion@ietf.org
Subject: RE: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt 
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

Eric:

I listening to your email thread - but confused.  Can you explain what
you mean by:=20

	=3D E.g., it's rather difficult to see why every minor change to a
BG=20
	Attribute needs special treatment.


I think you have a good point about other Internet protocols (DNS, DHCP,
HTTP, SIP) need to have the same level of documentation and review due
their wide-spread distributed nature.  The IESG should consider making
the bar for acceptance even for these distributed network essential
protocols.=20

    IE routing bar for entry =3D=3D DNS, DHCP, HTTP, SIP bar for entry



Sue Hares

-----Original Message-----
From: Eric Rosen [mailto:erosen@cisco.com]=20
Sent: Monday, February 20, 2006 11:48 AM
To: Bill Fenner
Cc: Alex Zinin; routing-discussion@ietf.org
Subject: Re: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt=20


> I'm sorry, I'm a bit confused here - you have a concern that this
> document quotes RFC2026, or you have a concern with the statement
> that appears in RFC2026?=20

Yes, to both.=20

> This document, especially section 3, is intended to give some
> criteria. Under the RFC1264 rules, we didn't even have this,
> so we picked and chose when to apply the rules ourselves, which
> of course is only a problem when we're wrong ;-)

Well, "everything from  a routing area WG" is a  clear enough criterion,
but
it selects many things that don't seem to be crucial to the operation of
the
Internet, that  don't seem to be  "core internet protocols",  and that
might
not even be technically classified as "routing".  Rather than clarifying
the
criteria  for which  submissions need  special  treatment, it  gives up
and
proposes to apply special treatment to  stuff that just doesn't seem to
need
it.=20

E.g., it's rather difficult to see why every minor change to a BGP
attribute
needs special treatment.=20

Various peculiar and  time-wasting things really do happen  when these
rules
are  enforced.  To take  a recent  case, IPv6-specific  extended
communities
were added to the BGP extended communities spec in order to satisfy the
rule
that IPv6 not  be ignored.  Then they were removed to  satisfy the rule
that
anything not implemented has to be removed.  This is just making the
authors
run around in circles.  It's hard to see how the presence or absence of
this
kind of  extended community in the spec  makes any difference at  all to
the
health of the Internet. =20

With regard to  the other criterion in section  3, "protocols
implementing a
distributed algorithm  whose functional domain  spans more than  one
network
segment ... or otherwise affects the state of the distributed routing
system
or per-hop forwarding behavior", let's see how clear this is.=20

It seems to me that the "distributed algorithm" criterion as stated
includes
such things as:=20

- Bittorrent  (if we might  suppose for a  moment that that would  ever
fall
  under the IETF's purview)

- Web-caching and proxying protocols (e.g., akamai)

- DNS

- Mail

- SETI

Is it your  intention that the criterion include such  things?  If not,
then
it's not clear what it is meant to include.=20

The "per-hop forwarding behavior" criterion would include anything
having to
do with per-hop QoS treatment (Diffserv, RSVP).  Is that your intention?


If these  criteria are taken literally,  they greatly increase  the
scope of
the routing ADs to make demands  on submissions from other area.  This
would
put the routing ADs on a par with the security ADs in terms of their
ability
to delay progress.

The "functional domain spans more than one network segment (link)"
criterion
confuses me.   Does this mean that  special requirements are  not needed
for
those protocols which provide  distributed algorithms that affect
forwarding
state, but  which don't have  a "functional domain"  of more than  one
link?
What would be an example of such a protocol?=20

> Are you arguing that routing protocols
> shouldn't be considered core Internet protocols, and perhaps we
> should just reclassify RFC1264 as historic, or that this document
> should cover other types of protocols, or that someone else should
> work on another document to cover those other types of protocols,
> or what?=20

I  don't think a  clear distinction  has been  drawn between  "core
internet
protocols" and others, and I don't think a good case has been made that
core
internet  protocols need special  treatment, or  that the  special
treatment
that  they've been  given  has made  any  difference to  the  health of
the
Internet. =20

In  general,  I  do  not  favor   adding  more  red  tape  to  the
process.
Reclassifying 1264 has historical might be a good move though.=20

> Do  you  have  a  suggestion   for  how  to  classify  these
[extensions]
> objectively?  We've  had trouble  with subjective rules,  which is
why we
> settled on the objective "same as the base protocol"

If the criteria applied to the base protocol were really clear and
technical
(i.e., based on  technical characteristics of the base  protocol rather
than
which Area its WG belongs to),  then why wouldn't the same criteria
would be
applicable to the extensions.=20

> By "now", do you mean "with the RFC1264 rules", or "with the
> draft-fenner-zinin rules"? We tried to make the criteria a lot more
> concrete in our draft.=20

When I complain about how things are working "now", I mean with whatever
set
of rules the ADs are now applying. =20

I think  the draft-fenner-zinin  rules make things  worse, as it  seems
that
they  try to  require special  treatment for  more things,  rather  than
for
fewer.  Maybe that's the problem in a nutshell.=20

> while one implementation was written during the development of the new
PIM
> spec, I'm aware of at least one that was written from the spec

I guess I  should only have mentioned the  BGP spec as an example  of a
spec
that no one's every done an implementation from ;-)

> And we got a lot of spec bug reports from that author, validating
> the theory that you learn about the clarity of the spec when you
implement
> from it

That theory is not in dispute!=20

> if you've  got the 7 items  listed in section  5.1 bullet points 1.  -
7.,
> then  you  can be  pretty  sure that  you've  provided  all the
necessary
> paperwork.=20

The terms "implementation  experience", "interoperability report", and
"test
scenarios and test  results" are not very clear to me.   If you haven't
done
this before,  I'm not  sure there is  anyplace you  can look that  tells
you
exactly what is required.  And in  many cases, it seems nearly
impossible to
produce this sort  of stuff.  E.g., when you're  advancing a spec
describing
implementations that have been deployed and interoperating for 5 or 6
years,
it's very hard  to produce anything like "test  scenarios and test
results".
That's why I think the paperwork requirements are not particularly
clear.=20







_______________________________________________
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 Feb 22 13:49:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FBz2z-0007UJ-GE; Wed, 22 Feb 2006 13:49:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FBz2x-0007UB-F0
	for routing-discussion@ietf.org; Wed, 22 Feb 2006 13:49:07 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBz2x-0000cT-4J
	for routing-discussion@ietf.org; Wed, 22 Feb 2006 13:49:07 -0500
Received: from rtp-core-2.cisco.com ([64.102.124.13])
	by rtp-iport-2.cisco.com with ESMTP; 22 Feb 2006 13:49:07 -0500
X-IronPort-AV: i="4.02,137,1139202000"; 
	d="scan'208"; a="82939624:sNHT31842432"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k1MImVLp021327
	for <routing-discussion@ietf.org>; Wed, 22 Feb 2006 13:49:05 -0500 (EST)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Wed, 22 Feb 2006 13:49:02 -0500
Received: from [10.82.216.55] ([10.82.216.55]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 22 Feb 2006 13:49:02 -0500
Message-ID: <43FCB21D.6070902@cisco.com>
Date: Wed, 22 Feb 2006 13:49:01 -0500
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
CC: routing-discussion@ietf.org
References: <200602211746.k1LHkvLN015431@rtp-core-2.cisco.com>
	<071b01c637b9$099672d0$33849ed9@Puppy>
In-Reply-To: <071b01c637b9$099672d0$33849ed9@Puppy>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Feb 2006 18:49:02.0319 (UTC)
	FILETIME=[A5F5CFF0:01C637E0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Subject: Re: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt
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,
Adrian raises an important point. I would hope that if a draft includes 
protocol encodings
for both IPv4 and IPv6 and has met the implementation requirements for 
one of these, we
could still progress the draft as long as there aren't substantial 
differences between the
protocol mechanisms and state machines. In fact, can text to this effect 
be added?

Thanks,
Acee

Adrian Farrel wrote:

>Hi,
>
>I think my opposition to the direction of this I-D has been aired, and I
>don't need to repeat my general case. I believe that the increased hurdle
>to PS will either gum up the WGs or will simply cause everything to be
>published as Experimental.
>
>But here are some specific points about this I-D which I don't think was
>ready for last call and doesn't appear to have had any significant review
>(including perhaps by the Routing Area Directorate?)
>
>Eric and Bill's conversation has brought up a point by mentioning IPv6.
>
>Let us imagine a widely implemented and deployed signlaing protocol. It is
>an IETF requirement that such protocol specifications include IPv6. This
>is no problem form the point of view of specification, and would be easy
>to implement, but the fact is that it is not implemented because no-one is
>building or deploying networks that use IPv6 in conjunction with this
>protocol (they may do in the future, but they are not doing so now).
>
>What will happen to the publication request for the I-D that specifies
>this protocol? We will not be able to say that the protocol specification
>has been fully implemented, and there certainly will not be any
>operational experience. Will this result in the RFC publication being help
>up? Does it mean that the I-D must be split into two parts before the main
>body can move forwards?
>
>
>The I-D does not state a proposed status.
>
>In section 3.2 you have (the much discussed)
>   In consultation with the community, the IESG MAY decide to waive some
>   or all of the requirements specified in this document.  A situation
>   where this might be needed is when factors not envisioned in this
>   document arise and applying elevated requirements does more harm than
>   good.
>Why are you making this a full IESG decision? Isn't it enought to delegate
>it to the Routing Area ADs?
>
>Section 4.1 point 2 (and through out). Please say MIB *module* not MIB.
>
>Section 4.1 point 4. What is an interoperable implementation of a MIB
>module?
>
>Progression to DS or S is dependent on implementation and deployment of
>associated MIB modules. I think you are setting yourself up for failure
>and not recognising the way the world is moving wrt SNMP. While the
>specification of the MIB modules is highly desireable, you may find that
>certain protocols do not see wide uptake of SNMP as a management
>technique. Do you propose that such protocols can never become standards,
>or will you invoke section 3.2? (If section 3.2 is to be so easily invoked
>we might as well dispose of this I-D and immediately hand all decisions to
>the IESG!)
>
>Section 5.1 seems at odds with the details in the Proto work. Can I
>suggest that you converge on a common set of information to be supplied at
>publication-request time so that the WG chairs do not have to fiddle about
>collecting different information for different I-D processing procedures.
>
>Section 5. point 2
>This is a change the order of events since previously it has been the ADs
>that have requested the RAD to review documents.
>Please supply details of how the review is actually initiated, how the
>progress of the review is tracked, and how the comments are returned to
>the working group.
>
>Section 5. point 3
>A little more detail about the submission and publication of the
>implementation and interoperability report would be helpful. Is this an
>email to the IETF secretariat? Or perhaps it is an I-D? Where on the IETF
>Web site will this be publicly available?
>
>Section 5 is missing MIB Doctor review
>
>Section 5 is missing appropriate cross-area and cross-WG review.
>
>Section 5.1 says "IETF secretariat" and then lists the IESG Secretary's
>email address. (See Section 5 point 3)
>
>Long-term persistence of reports.
>In several cases we are required to submit reports (implementation,
>interoperability, operational experience, etc.). What is the archival
>process for this? If they are submitted as I-Ds will they be published as
>Informational RFCs to preserve them, or is some other archive proposed?
>
>Section 8 seems to be a tiny bit empty. I'm surprised to see a last call
>with that problem :-)
>
>Use of RFC2119 language. This may or may not be appropriate in this I-D.
>But if you use it you must include 2119 as a reference and use the normal
>2119 boilerplate.
>
>Thanks,
>Adrian
>
>
>_______________________________________________
>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 Feb 22 15:16:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FC0P5-0000B0-RG; Wed, 22 Feb 2006 15:16:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FC0P4-0000Ar-US
	for routing-discussion@ietf.org; Wed, 22 Feb 2006 15:16:02 -0500
Received: from pproxy.gmail.com ([64.233.166.183])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FC0P1-0004QR-NS
	for routing-discussion@ietf.org; Wed, 22 Feb 2006 15:16:02 -0500
Received: by pproxy.gmail.com with SMTP id i49so1833799pyi
	for <routing-discussion@ietf.org>; Wed, 22 Feb 2006 12:15:59 -0800 (PST)
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=eXo4PpYCsu6QoSIu4A4dRoDKXHyNVKtpGCe2dSILHTsLiTESmHamHE/DC9TwhSXImhzL0nY2JCfiZkkpZ6YqcO7NIO8/6JTAjVIeHReVaOgLNUDCCyVZONnq8tTQKAkE2xb8slGKNpE8bXj5mfHcfXWXxEvBOUh8TLMMjmWxMo4=
Received: by 10.35.37.18 with SMTP id p18mr938945pyj;
	Wed, 22 Feb 2006 12:15:59 -0800 (PST)
Received: by 10.35.10.20 with HTTP; Wed, 22 Feb 2006 12:15:59 -0800 (PST)
Message-ID: <6280db520602221215h4666a01ck7d993c56c5d9103@mail.gmail.com>
Date: Wed, 22 Feb 2006 12:15:59 -0800
From: "Alia Atlas" <akatlas@gmail.com>
To: "Adrian Farrel" <adrian@olddog.co.uk>
In-Reply-To: <071b01c637b9$099672d0$33849ed9@Puppy>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <200602211746.k1LHkvLN015431@rtp-core-2.cisco.com>
	<071b01c637b9$099672d0$33849ed9@Puppy>
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: routing-discussion@ietf.org
Subject: Re: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt
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 2/22/06, Adrian Farrel <adrian@olddog.co.uk> wrote:
> I think my opposition to the direction of this I-D has been aired, and I
> don't need to repeat my general case. I believe that the increased hurdle
> to PS will either gum up the WGs or will simply cause everything to be
> published as Experimental.

I am also concerned about the increased hurdle to PS.  We already have
a problem with drafts being treated as standards; this seems to
increase that problem.

Treating extensions the same as the base protocol seems like overkill
for many of the common extensions.  I don't currently have a good
suggestion for how to split the extensions into those that are of
greater concern & those that aren't.  I would rather see the
extensions be more relaxed by default, with the ability by the WG/WG
chairs/routing ADs to require the elevated requirements when
appropriate.

For the obligatory textual comment, the draft would be clearer to read
if the requirements for each level described "those for the previous
level plus" as is done for the submission requirements.

Alia

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



From routing-discussion-bounces@ietf.org Wed Feb 22 16:14:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FC1JA-00089f-57; Wed, 22 Feb 2006 16:14:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FC1J8-000895-M7
	for routing-discussion@ietf.org; Wed, 22 Feb 2006 16:13:58 -0500
Received: from relay01.pair.com ([209.68.5.15])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FC1J8-0002pe-Eq
	for routing-discussion@ietf.org; Wed, 22 Feb 2006 16:13:58 -0500
Received: (qmail 6859 invoked from network); 22 Feb 2006 21:13:57 -0000
Received: from unknown (HELO workhorse.faster-light.net) (unknown)
	by unknown with SMTP; 22 Feb 2006 21:13:57 -0000
X-pair-Authenticated: 69.37.59.162
Received: from workhorse.faster-light.net (localhost.faster-light.net
	[127.0.0.1])
	by workhorse.faster-light.net (8.12.11/8.12.11) with ESMTP id
	k1MLHFqt007018; Wed, 22 Feb 2006 16:17:15 -0500 (EST)
	(envelope-from curtis@workhorse.faster-light.net)
Message-Id: <200602222117.k1MLHFqt007018@workhorse.faster-light.net>
To: "Alia Atlas" <akatlas@gmail.com>
In-reply-to: Your message of "Wed, 22 Feb 2006 12:15:59 PST."
	<6280db520602221215h4666a01ck7d993c56c5d9103@mail.gmail.com> 
Date: Wed, 22 Feb 2006 16:17:15 -0500
From: Curtis Villamizar <curtis@faster-light.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: Adrian Farrel <adrian@olddog.co.uk>, routing-discussion@ietf.org
Subject: Re: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt 
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 <6280db520602221215h4666a01ck7d993c56c5d9103@mail.gmail.com>
"Alia Atlas" writes:
>  
> On 2/22/06, Adrian Farrel <adrian@olddog.co.uk> wrote:
> > I think my opposition to the direction of this I-D has been aired, and I
> > don't need to repeat my general case. I believe that the increased hurdle
> > to PS will either gum up the WGs or will simply cause everything to be
> > published as Experimental.
>  
> I am also concerned about the increased hurdle to PS.  We already have
> a problem with drafts being treated as standards; this seems to
> increase that problem.
>  
> Treating extensions the same as the base protocol seems like overkill
> for many of the common extensions.  I don't currently have a good
> suggestion for how to split the extensions into those that are of
> greater concern & those that aren't.  I would rather see the
> extensions be more relaxed by default, with the ability by the WG/WG
> chairs/routing ADs to require the elevated requirements when
> appropriate.
>  
> For the obligatory textual comment, the draft would be clearer to read
> if the requirements for each level described "those for the previous
> level plus" as is done for the submission requirements.
>  
> Alia


Alia,

A bigger problem is carriers, particularly far east and third world,
who point to anything remotely resembling a standard and wanting it
implemented, sometimes not even understanding what it is supposed to
do or how it works.

Lowing the bar for something to be called a standard won't help.  I'd
rather see a smaller set of standards that really do work than a large
set of ideas standardized, many of which eventually prove not to work.

My favorite example within IETF has always been NHRP.  Another from
outside the IETF is OIF UNI.  Another is the ITU's MPLA OAM, where the
authors didn't like the IETF rigorous process so they went elsewhere
so they could get a rubber stamp on it.  There is a long list of
"standards" that never should have been accepted.

What you are suggesting would make it easier for any of those or
future bad ideas to become IETF PS.  There is a very long list of
proposed extensions to BGP alone.  Its almost certain that some
percentage of them will never be implemented or will prove to not be
useful.  The RFC collection is cluttered enough already without dozens
of protocol extensions that don't work (or dozens more).

Curtis

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



From routing-discussion-bounces@ietf.org Wed Feb 22 16:40:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FC1iR-0003FA-GW; Wed, 22 Feb 2006 16:40:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FC1iP-0003Ez-Q0
	for routing-discussion@ietf.org; Wed, 22 Feb 2006 16:40:05 -0500
Received: from pproxy.gmail.com ([64.233.166.183])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FC1iP-0004RL-JL
	for routing-discussion@ietf.org; Wed, 22 Feb 2006 16:40:05 -0500
Received: by pproxy.gmail.com with SMTP id i49so1848874pyi
	for <routing-discussion@ietf.org>; Wed, 22 Feb 2006 13:40:05 -0800 (PST)
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=d4rzBzIDIMQxQFEGlTfdwlpNNnqgyEoPcapngwFt61eNWEm+PS4IHN8kkrFvg+dgMLTXCIJQUJaXLBhBVcT/zKha8/D3p3TBd/KhYjwelE6/0gOISzmgomSfjm41IjUjAbIsOIokWQGdbU6xG9dSl8WQ7VXeHWanma6vnNiU3T4=
Received: by 10.35.127.7 with SMTP id e7mr1019382pyn;
	Wed, 22 Feb 2006 13:40:05 -0800 (PST)
Received: by 10.35.10.20 with HTTP; Wed, 22 Feb 2006 13:40:04 -0800 (PST)
Message-ID: <6280db520602221340i2d649bbbx1452a2e95d51a08e@mail.gmail.com>
Date: Wed, 22 Feb 2006 13:40:04 -0800
From: "Alia Atlas" <akatlas@gmail.com>
To: curtis@faster-light.net, "Adrian Farrel" <adrian@olddog.co.uk>, 
	routing-discussion@ietf.org
In-Reply-To: <6280db520602221339u7ba388b0h7e29aed44cd6c2d0@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <6280db520602221215h4666a01ck7d993c56c5d9103@mail.gmail.com>
	<200602222117.k1MLHFqt007018@workhorse.faster-light.net>
	<6280db520602221339u7ba388b0h7e29aed44cd6c2d0@mail.gmail.com>
X-Spam-Score: 1.9 (+)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: 
Subject: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt
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,

On 2/22/06, Curtis Villamizar <curtis@faster-light.net> wrote:
> A bigger problem is carriers, particularly far east and third world,
> who point to anything remotely resembling a standard and wanting it
> implemented, sometimes not even understanding what it is supposed to
> do or how it works.
>
> Lowing the bar for something to be called a standard won't help.  I'd
> rather see a smaller set of standards that really do work than a large
> set of ideas standardized, many of which eventually prove not to work.

We aren't talking about lowering the bar - but raising it from
requiring one implementation to requiring two.  I agree that we want
ideas standardized that really do work.

If drafts take even longer to get standardized because of more
hurdles, that makes
it more likely that many drafts will be treated as defacto standards,
that will be requested
for implementation also.

> My favorite example within IETF has always been NHRP.  Another from
> outside the IETF is OIF UNI.  Another is the ITU's MPLA OAM, where the
> authors didn't like the IETF rigorous process so they went elsewhere
> so they could get a rubber stamp on it.  There is a long list of
> "standards" that never should have been accepted.

Sure.  There are always those who go elsewhere to get rubberstamped.

> What you are suggesting would make it easier for any of those or
> future bad ideas to become IETF PS.  There is a very long list of
> proposed extensions to BGP alone.  Its almost certain that some
> percentage of them will never be implemented or will prove to not be
> useful.  The RFC collection is cluttered enough already without dozens
> of protocol extensions that don't work (or dozens more).

For extensions, I am not suggesting that an implementation isn't
required.  It is the
elevated requirement of needing two implementations that I am questioning.

Alia

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



From routing-discussion-bounces@ietf.org Wed Feb 22 17:53:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FC2r4-0004lt-S4; Wed, 22 Feb 2006 17:53:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FC2r3-0004lj-AV
	for routing-discussion@ietf.org; Wed, 22 Feb 2006 17:53:05 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FC2r2-0008TD-4c
	for routing-discussion@ietf.org; Wed, 22 Feb 2006 17:53:05 -0500
Received: from rtp-core-1.cisco.com ([64.102.124.12])
	by rtp-iport-1.cisco.com with ESMTP; 22 Feb 2006 14:53:04 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.02,138,1139212800"; 
	d="scan'208"; a="22440159:sNHT20932564"
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 k1MMr3qM015401; 
	Wed, 22 Feb 2006 17:53:03 -0500 (EST)
Message-Id: <200602222253.k1MMr3qM015401@rtp-core-1.cisco.com>
To: curtis@faster-light.net
In-reply-to: Your message of Wed, 22 Feb 2006 16:17:15 -0500.
	<200602222117.k1MLHFqt007018@workhorse.faster-light.net> 
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Wed, 22 Feb 2006 17:53:03 -0500
From: Eric Rosen <erosen@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: Adrian Farrel <adrian@olddog.co.uk>, routing-discussion@ietf.org
Subject: Re: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt 
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


Curtis> I'd rather see a smaller set of standards that really do work than a
Curtis> large set of ideas standardized,  many of which eventually prove not
Curtis> to work. 

A laudable  goal.  However, since  bad ideas frequently have  multiple early
implementations,  and good ideas  can be  slow to  catch on,  requiring more
implementations and/or deployments is not going to help us meet this goal. 




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



From routing-discussion-bounces@ietf.org Wed Feb 22 19:46:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FC4cz-00059D-Bq; Wed, 22 Feb 2006 19:46:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FC4cx-000598-Sx
	for routing-discussion@ietf.org; Wed, 22 Feb 2006 19:46:39 -0500
Received: from relay00.pair.com ([209.68.5.9])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FC4cw-00040i-Le
	for routing-discussion@ietf.org; Wed, 22 Feb 2006 19:46:39 -0500
Received: (qmail 98896 invoked from network); 23 Feb 2006 00:46:38 -0000
Received: from unknown (HELO workhorse.faster-light.net) (unknown)
	by unknown with SMTP; 23 Feb 2006 00:46:38 -0000
X-pair-Authenticated: 69.37.59.162
Received: from workhorse.faster-light.net (localhost.faster-light.net
	[127.0.0.1])
	by workhorse.faster-light.net (8.12.11/8.12.11) with ESMTP id
	k1N0nsCH007600; Wed, 22 Feb 2006 19:49:54 -0500 (EST)
	(envelope-from curtis@workhorse.faster-light.net)
Message-Id: <200602230049.k1N0nsCH007600@workhorse.faster-light.net>
To: erosen@cisco.com
In-reply-to: Your message of "Wed, 22 Feb 2006 17:53:03 EST."
	<200602222253.k1MMr3qM015401@rtp-core-1.cisco.com> 
Date: Wed, 22 Feb 2006 19:49:54 -0500
From: Curtis Villamizar <curtis@faster-light.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: Adrian Farrel <adrian@olddog.co.uk>, curtis@faster-light.net,
	routing-discussion@ietf.org
Subject: Re: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt 
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 <200602222253.k1MMr3qM015401@rtp-core-1.cisco.com>
Eric Rosen writes:
>  
>  
> Curtis> I'd rather see a smaller set of standards that really do work than a
> Curtis> large set of ideas standardized,  many of which eventually prove not
> Curtis> to work. 
>  
> A laudable  goal.  However, since  bad ideas frequently have  multiple early
> implementations,  and good ideas  can be  slow to  catch on,  requiring more
> implementations and/or deployments is not going to help us meet this goal. 


I'm sure the ratio of bad ideas with multiple implementations to bad
ideas with single implementations or no implementations is quite high.

Therefore raising the bar will not entirely eliminate bad ideas, just
reduce the number of bad ideas that become standards within the IETF.

Curtis

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



From routing-discussion-bounces@ietf.org Thu Feb 23 04:34:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FCCrt-0006Dq-1P; Thu, 23 Feb 2006 04:34:37 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FCCrs-0006Di-9h
	for routing-discussion@ietf.org; Thu, 23 Feb 2006 04:34:36 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FCCrr-0001CZ-1q
	for routing-discussion@ietf.org; Thu, 23 Feb 2006 04:34:36 -0500
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by sj-iport-2.cisco.com with ESMTP; 23 Feb 2006 01:34:35 -0800
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k1N9YYtD028333;
	Thu, 23 Feb 2006 01:34:34 -0800 (PST)
Received: from [212.254.247.3] (ams-clip-vpn-dhcp223.cisco.com [10.61.64.223])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k1N9bAF3000856;
	Thu, 23 Feb 2006 01:37:11 -0800
Message-ID: <43FD81A8.5060001@cisco.com>
Date: Thu, 23 Feb 2006 10:34:32 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 1.5 (Macintosh/20051201)
MIME-Version: 1.0
To: curtis@faster-light.net
References: <200602230049.k1N0nsCH007600@workhorse.faster-light.net>
In-Reply-To: <200602230049.k1N0nsCH007600@workhorse.faster-light.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=854; t=1140687432; x=1141119632;
	c=relaxed/simple; s=nebraska;
	h=Subject:From:Date:Content-Type:Content-Transfer-Encoding:Mime-Version;
	d=cisco.com; i=lear@cisco.com; z=From:Eliot=20Lear=20<lear@cisco.com>
	|Subject:Re=3A=20Last=20Call=3A=20draft-fenner-zinin-rtg-standard-reqts-01.txt
	|To:=20curtis@faster-light.net;
	X=v=3Dmtcc.com=3B=20h=3D8z3yW/B40NkoeKe67PLr1IIg0kI=3D;
	b=J8XK4AKanFB3m8U6R9CKSThIxTPkQXUvxwbjX5awmtG+Eg5k4x89u1APpOqerzXTjEZPKXsX
	uRuIUylihbqQM6QUmi9ouggi1tFXWexIBQOpXr7BmwgJeOSkb1frX1Qk1km1Ifu83iUfjIS+rRn
	lCzgu86bdkbEi0nSCgrCKb68=;
Authentication-Results: imail.cisco.com; header.From=lear@cisco.com;
	dkim=pass ( message from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: Adrian Farrel <adrian@olddog.co.uk>, erosen@cisco.com,
	routing-discussion@ietf.org
Subject: Re: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt
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 Villamizar wrote:
> I'm sure the ratio of bad ideas with multiple implementations to bad
> ideas with single implementations or no implementations is quite high.
>
> Therefore raising the bar will not entirely eliminate bad ideas, just
> reduce the number of bad ideas that become standards within the IETF.
>   

And so now I have two problems with this document:

    * People with GOOD ideas may not wish to deal with the IETF if the
      bar is explicitly raised.  It's already pretty high, which is why
      we have seen a plethora of SDOs over the last few years.
    * And *still* this document is redundant.  The IESG should already
      feel free to demand implementation experience prior to letting a
      really sensitive change go through.  Heck, this is how
      internet-drafts are used today, anyway.

Eliot

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



From routing-discussion-bounces@ietf.org Fri Feb 24 11:43:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FCg2q-0004yQ-Av; Fri, 24 Feb 2006 11:43:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FCg2o-0004uu-OV
	for routing-discussion@ietf.org; Fri, 24 Feb 2006 11:43:50 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCg2n-0000qA-Hu
	for routing-discussion@ietf.org; Fri, 24 Feb 2006 11:43:50 -0500
Received: from rtp-core-2.cisco.com ([64.102.124.13])
	by rtp-iport-1.cisco.com with ESMTP; 24 Feb 2006 08:43:50 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.02,144,1139212800"; 
	d="scan'208"; a="22545287:sNHT21621840"
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k1OGhnjJ013641; 
	Fri, 24 Feb 2006 11:43:49 -0500 (EST)
Message-Id: <200602241643.k1OGhnjJ013641@rtp-core-2.cisco.com>
To: Acee Lindem <acee@cisco.com>
In-reply-to: Your message of Wed, 22 Feb 2006 13:49:01 -0500.
	<43FCB21D.6070902@cisco.com> 
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Fri, 24 Feb 2006 11:43:48 -0500
From: Eric Rosen <erosen@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: routing-discussion@ietf.org
Subject: Re: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt 
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


Acee> I would hope that if a draft includes protocol encodings for both IPv4
Acee> and IPv6 and has met the implementation requirements for one of these,
Acee> we could still progress the  draft as long as there aren't substantial
Acee> differences  between the  protocol mechanisms  and state  machines. In
Acee> fact, can text to this effect be added? 

What would be the grounds for giving IPv6 this special exemption? 

We  could  have  a general  exemption  for  anything  that doesn't  cause  a
substantial change  in protocol procedures  and state machines.   That would
make sense, and  though there will sometimes be  disagreements on what falls
into that category, that exemption would apply to more than just IPv6. 

Or I  suppose we  could have a  general exemption  for things that  the IESG
makes us put  in but nobody really wants; that sort  of exemption would help
us with a lot of the "mandatory to implement" security features.

If exemptions are  allowed, the draft needs to  state the general principles
behind the exemptions, it shouldn't just have a list of exemptions. 




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



From routing-discussion-bounces@ietf.org Fri Feb 24 12:33:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FCgn2-0004gL-3q; Fri, 24 Feb 2006 12:31:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FCgn0-0004gD-29
	for routing-discussion@ietf.org; Fri, 24 Feb 2006 12:31:34 -0500
Received: from relay01.pair.com ([209.68.5.15])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FCgmy-0002fk-Qs
	for routing-discussion@ietf.org; Fri, 24 Feb 2006 12:31:34 -0500
Received: (qmail 26819 invoked from network); 24 Feb 2006 17:31:31 -0000
Received: from unknown (HELO workhorse.faster-light.net) (unknown)
	by unknown with SMTP; 24 Feb 2006 17:31:31 -0000
X-pair-Authenticated: 69.37.59.162
Received: from workhorse.faster-light.net (localhost.faster-light.net
	[127.0.0.1])
	by workhorse.faster-light.net (8.12.11/8.12.11) with ESMTP id
	k1OHYRQk013387; Fri, 24 Feb 2006 12:34:27 -0500 (EST)
	(envelope-from curtis@workhorse.faster-light.net)
Message-Id: <200602241734.k1OHYRQk013387@workhorse.faster-light.net>
To: erosen@cisco.com
In-reply-to: Your message of "Fri, 24 Feb 2006 11:43:48 EST."
	<200602241643.k1OGhnjJ013641@rtp-core-2.cisco.com> 
Date: Fri, 24 Feb 2006 12:34:26 -0500
From: Curtis Villamizar <curtis@faster-light.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: routing-discussion@ietf.org
Subject: Re: Last Call: draft-fenner-zinin-rtg-standard-reqts-01.txt 
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 <200602241643.k1OGhnjJ013641@rtp-core-2.cisco.com>
Eric Rosen writes:
>  
>  
> Acee> I would hope that if a draft includes protocol encodings for both IPv4
> Acee> and IPv6 and has met the implementation requirements for one of these,
> Acee> we could still progress the  draft as long as there aren't substantial
> Acee> differences  between the  protocol mechanisms  and state  machines. In
> Acee> fact, can text to this effect be added? 
>  
> What would be the grounds for giving IPv6 this special exemption? 

It has very little operational impact?  :-)

> We  could  have  a general  exemption  for  anything  that doesn't  cause  a
> substantial change  in protocol procedures  and state machines.   That would
> make sense, and  though there will sometimes be  disagreements on what falls
> into that category, that exemption would apply to more than just IPv6. 
>  
> Or I  suppose we  could have a  general exemption  for things that  the IESG
> makes us put  in but nobody really wants; that sort  of exemption would help
> us with a lot of the "mandatory to implement" security features.
>  
> If exemptions are  allowed, the draft needs to  state the general principles
> behind the exemptions, it shouldn't just have a list of exemptions. 

This is a legitimate topic.  Protocol documents want IPv6
considerations to be included in virtually anything done in the IETF
but it is harder to find implementations for the IPv6 part of some
protocols and it is nearly impossible to find deployments of some
protocols that are widely used in IPv4.  The IPv6 usage may lag by
many years.

Do we declare the IPv6 portion of the protocol to not meet the
requirements for routing protocols and remove them?  Do we put them in
separate companion documents so as not to interfere with the progress
of the IPv4 portion?  Or could we exempt the IPv6 portion as an
experiment in progress that we'd like to support?  There is nothing
wrong with calling something an experiment.  For example, the NFSNET
was in its time considered an experiment, one that succeeded.

I prefer either the latter (exempt IPv6) or separating the base and
IPv4 and IPv6 parts of documents and allowing them to progress
somewhat independently.

Curtis

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



From routing-discussion-bounces@ietf.org Mon Feb 27 06:55:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FDgxv-0003I3-DE; Mon, 27 Feb 2006 06:54:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FDgxt-0003FO-SA
	for routing-discussion@ietf.org; Mon, 27 Feb 2006 06:54:57 -0500
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FDgxs-0007Hc-Ha
	for routing-discussion@ietf.org; Mon, 27 Feb 2006 06:54:57 -0500
Received: from olvera02 by consulintel.es (MDaemon.PRO.v8.0.5.R)
	with ESMTP id md50001649027.msg
	for <routing-discussion@ietf.org>; Mon, 27 Feb 2006 12:54:54 +0100
From: "Cesar Olvera" <cesar.olvera@consulintel.es>
To: <routing-discussion@ietf.org>
Date: Mon, 27 Feb 2006 12:54:20 +0100
Organization: Consulintel
Message-ID: <004e01c63b94$8d159bc0$0201a8c0@consulintel.es>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <Pine.LNX.4.44.0310011847300.26404-100000@netcore.fi>
Thread-Index: AcY7lIs7coI+IMDDS8ebl3Y3byCieA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Authenticated-Sender: cesar.olvera@consulintel.es
X-HashCash: 1:20:060227:routing-discussion@ietf.org::gC+MZo6s0kabc5Cm:00000000000000000000000000000000000234
X-MDRemoteIP: 62.14.56.219
X-Return-Path: cesar.olvera@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.8 tests=BAYES_00 autolearn=ham 
	version=3.0.4
X-Spam-Level: 
X-Spam-Processed: consulintel.es, Mon, 27 Feb 2006 12:54:55 +0100
X-MDAV-Processed: consulintel.es, Mon, 27 Feb 2006 12:54:55 +0100
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Subject: About Longest Prefix Match document
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: cesar.olvera@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,

Somebody knows the document that specifies the Longest Prefix Match
(LPM) Algorithm?

Thanks in advance,

C=E9sar Olvera
Consulintel




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

Barcelona 2005 Global IPv6 Summit
Slides available at:
http://www.ipv6-es.com

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



