Re: [Idr] draft-asati-idr-bgp-bestpath-selection-criteria as IDR WG draft

"John G. Scudder" <jgs@juniper.net> Wed, 22 July 2009 03:00 UTC

Return-Path: <jgs@juniper.net>
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 C679B3A68E2 for <idr@core3.amsl.com>; Tue, 21 Jul 2009 20:00:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.222
X-Spam-Level:
X-Spam-Status: No, score=-6.222 tagged_above=-999 required=5 tests=[AWL=0.377, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 o7-z1l2TXxIb for <idr@core3.amsl.com>; Tue, 21 Jul 2009 20:00:52 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by core3.amsl.com (Postfix) with ESMTP id 99BF13A635F for <idr@ietf.org>; Tue, 21 Jul 2009 20:00:46 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKSmaA3hOsRgBBmzzDZI9ardnnk5QKAzFO@postini.com; Tue, 21 Jul 2009 20:00:52 PDT
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.375.2; Tue, 21 Jul 2009 19:57:25 -0700
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 21 Jul 2009 19:57:25 -0700
Received: from emailsmtp56.jnpr.net ([172.24.60.77]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 21 Jul 2009 19:57:25 -0700
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 21 Jul 2009 19:57:24 -0700
Received: from [172.16.13.201] ([172.16.13.201]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id n6M2vNd47658; Tue, 21 Jul 2009 19:57:24 -0700 (PDT) (envelope-from jgs@juniper.net)
Message-ID: <56CC1BBE-4437-4FA8-85A6-D4E3E9A9B8C6@juniper.net>
From: "John G. Scudder" <jgs@juniper.net>
To: curtis@occnc.com, "Rajiv Asati (rajiva)" <rajiva@cisco.com>
In-Reply-To: <200907220208.n6M28Z96079438@harbor.orleans.occnc.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 21 Jul 2009 22:57:23 -0400
References: <200907220208.n6M28Z96079438@harbor.orleans.occnc.com>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 22 Jul 2009 02:57:24.0723 (UTC) FILETIME=[23D89430:01CA0A78]
Cc: idr List <idr@ietf.org>
Subject: Re: [Idr] draft-asati-idr-bgp-bestpath-selection-criteria as IDR WG draft
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/mail-archive/web/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>
X-List-Received-Date: Wed, 22 Jul 2009 03:00:52 -0000

On Jul 21, 2009, at 10:08 PM, Curtis Villamizar wrote:
> Susan Hares wrote:
>> We have received a request to accept draft-asati-idr-bgp-bestpath- 
>> selection-criteria-00.txt as an IDR WG document. Please send your  
>> votes by 8/3/09.
>> Sue and John
>
>
> The draft that I just fetched (as -01) says:
>
>    This Internet-Draft,
>    draft-asati-idr-bgp-bestpath-selection-criteria-00.txt, has
>    expired, and has been deleted from the Internet-Drafts directory.
>
> I'm not sure how we can take a "vote" with the draft unavailable for
> review.

A fair point.

Rajiv, can you please refresh the draft?

Curtis, my advanced search engine skills enabled me to find http://tools.ietf.org/html/draft-asati-idr-bgp-bestpath-selection-criteria-00 
  , which should take care of the practical issue if you don't want to  
wait until the draft gets refreshed (which I assume will only happen  
after the IETF due to the pre-IETF draft publication freeze).

--John