Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an IDR WG document

Enke Chen <enke@redback.com> Mon, 19 July 2004 23:50 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10141; Mon, 19 Jul 2004 19:50:05 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BmhtX-0005ew-Ie; Mon, 19 Jul 2004 19:50:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BmhNb-0002sT-4K; Mon, 19 Jul 2004 19:17:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bmf1G-0002u1-AC for idr@megatron.ietf.org; Mon, 19 Jul 2004 16:45:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01425 for <idr@ietf.org>; Mon, 19 Jul 2004 16:45:51 -0400 (EDT)
Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BmeyQ-0002P7-Ha for idr@ietf.org; Mon, 19 Jul 2004 16:43:00 -0400
Received: from prattle.redback.com ([155.53.12.9]) by mx2.foretec.com with esmtp (Exim 4.24) id 1BmdqK-0001ju-Qj for idr@ietf.org; Mon, 19 Jul 2004 15:30:33 -0400
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id 247F75D4530; Mon, 19 Jul 2004 12:00:15 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07805-02; Mon, 19 Jul 2004 12:00:14 -0700 (PDT)
Received: from fall.redback.com (fall.redback.com [155.53.44.81]) by prattle.redback.com (Postfix) with ESMTP id C47745D4534; Mon, 19 Jul 2004 12:00:14 -0700 (PDT)
Received: from redback.com (localhost [127.0.0.1]) by fall.redback.com (8.11.0/8.8.8/null redback bsdclient) with ESMTP id i6JJ0E810565; Mon, 19 Jul 2004 12:00:14 -0700 (PDT)
Message-Id: <200407191900.i6JJ0E810565@fall.redback.com>
To: idr@ietf.org
Subject: Re: [Idr] draft-chen-bgp-prefix-orf-07.txt as an IDR WG document
In-Reply-To: Message from Yakov Rekhter <yakov@juniper.net> of "Mon, 19 Jul 2004 08:42:23 PDT." <200407191542.i6JFgNe12536@merlot.juniper.net>
Date: Mon, 19 Jul 2004 12:00:14 -0700
From: Enke Chen <enke@redback.com>
X-Virus-Scanned: by amavisd-new at redback.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: enke@redback.com
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336

Hi, folks:

Yes, I think that we should adopt the draft as an IDR document.

 1) The Prefix ORF is already in the IDR Charter:

     May 04  Submit Outbound Route Filter, Prefix and ASpath ORF draft to IESG
             as a Proposed Standard

     In order to reach the milestone, it would be necessary to make the
     draft an IDR document.

 2) The spec is mature and has been implmented and deployed for several years.

Thanks.  -- Enke

> Message-Id: <200407191542.i6JFgNe12536@merlot.juniper.net>
> To: idr@ietf.org
> Date: Mon, 19 Jul 2004 08:42:23 -0700
> From: Yakov Rekhter <yakov@juniper.net>
> Subject: [Idr] draft-chen-bgp-prefix-orf-07.txt as an IDR WG document
> 
> Folks,
> 
> We received a request to accept draft-chen-bgp-prefix-orf-07.txt
> as an IDR WG document (see e-mail to the list on Jul 14, 2004). 
> 
> It would be greatly appreciated if folks would read the document and 
> comment on it to the IDR mailing list. In other words, we need 
> "yes, looks good" or "should fix this and that", not just silence.
> 
> I would suggest to have August 2 as the deadline for comments. But
> if folks feel that it is not enough time (as we have the IETF in
> two weeks), we could extend the deadline.
> 
> Yakov.
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www1.ietf.org/mailman/listinfo/idr


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