Re: [Idr] RFC5065 - Section 5.3

David Freedman <david.freedman@uk.clara.net> Tue, 08 July 2008 14:12 UTC

Return-Path: <idr-bounces@ietf.org>
X-Original-To: idr-archive@megatron.ietf.org
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 279063A6867; Tue, 8 Jul 2008 07:12:36 -0700 (PDT)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6C84C3A689A for <idr@core3.amsl.com>; Tue, 8 Jul 2008 07:12:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.852
X-Spam-Level:
X-Spam-Status: No, score=-1.852 tagged_above=-999 required=5 tests=[AWL=0.747, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kF7IyjSeaxad for <idr@core3.amsl.com>; Tue, 8 Jul 2008 07:12:29 -0700 (PDT)
Received: from synchronicity.convergence.cx (synchronicity.convergence.cx [195.8.70.6]) by core3.amsl.com (Postfix) with ESMTP id AB53D3A67E5 for <idr@ietf.org>; Tue, 8 Jul 2008 07:12:28 -0700 (PDT)
Received: from synchronicity.convergence.cx (localhost.localdomain [127.0.0.1]) by synchronicity.convergence.cx (8.13.8/8.13.8) with ESMTP id m68EPTVF005665; Tue, 8 Jul 2008 15:25:30 +0100
Message-ID: <487378D9.3010707@uk.clara.net>
Date: Tue, 08 Jul 2008 15:25:29 +0100
From: David Freedman <david.freedman@uk.clara.net>
Organization: Claranet Limited
User-Agent: Thunderbird 2.0.0.14 (X11/20080421)
MIME-Version: 1.0
To: Jeffrey Haas <jhaas@pfrc.org>
References: <48736F35.5030300@uk.clara.net> <20080708135820.GA31991@slice>
In-Reply-To: <20080708135820.GA31991@slice>
X-Enigmail-Version: 0.95.6
Cc: idr@ietf.org
Subject: Re: [Idr] RFC5065 - Section 5.3
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

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

> 
> There is nothing stopping a vendor from providing a knob to accomplish
> this very feature.  

Other than the RFC is now explicit about this behaviour (where RFC3065
was not previously).

> The language thus was written to heavily favor interoperability over
> flexibility.  This avoids having to discuss the picky issues of
> consistent route selection across the AS within a specific extension.

Thanks, I do indeed understand but believe it makes it harder now to
convince vendors to "enhance" implementations now that there is an
explicit "SHOULD NOT"

Dave.


> 
> -- Jeff


- --
David Freedman
Group Network Engineering
Claranet Limited
http://www.clara.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIc3jZtFWeqpgEZrIRAmOsAJ9qKG7nXG3ij4EBndVvSdaxRmuvVQCgswTA
sz72qZZoxbdSLenYNX7/cXg=
=xdBo
-----END PGP SIGNATURE-----
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr