Re: Resending: Re: 2842 to Draft Standard
Susan Hares <skh@nexthop.com> Fri, 11 January 2002 16:43 UTC
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id LAA12441 for <idr-archive@nic.merit.edu>; Fri, 11 Jan 2002 11:43:21 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix) id C49D091294; Fri, 11 Jan 2002 11:43:01 -0500 (EST)
Delivered-To: idr-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56) id 902C991295; Fri, 11 Jan 2002 11:43:01 -0500 (EST)
Delivered-To: idr@trapdoor.merit.edu
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id 71ECE91294 for <idr@trapdoor.merit.edu>; Fri, 11 Jan 2002 11:43:00 -0500 (EST)
Received: by segue.merit.edu (Postfix) id 591F65DD97; Fri, 11 Jan 2002 11:43:00 -0500 (EST)
Delivered-To: idr@merit.edu
Received: from presque.djinesys.com (presque.djinesys.com [198.108.88.2]) by segue.merit.edu (Postfix) with ESMTP id 1DD715DD8F for <idr@merit.edu>; Fri, 11 Jan 2002 11:43:00 -0500 (EST)
Received: from SKH.nexthop.com ([64.211.218.122]) by presque.djinesys.com (8.11.3/8.11.1) with ESMTP id g0BGgho44882; Fri, 11 Jan 2002 11:42:43 -0500 (EST) (envelope-from skh@nexthop.com)
Message-Id: <5.0.0.25.0.20020111114235.03e5fe80@mail.nexthop.com>
X-Sender: skh@mail.nexthop.com
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Fri, 11 Jan 2002 11:42:41 -0500
To: Bill Fenner <fenner@research.att.com>
From: Susan Hares <skh@nexthop.com>
Subject: Re: Resending: Re: 2842 to Draft Standard
Cc: idr@merit.edu
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-NextHop-MailScanner: Found to be clean
Sender: owner-idr@merit.edu
Precedence: bulk
IDR working group: I will be sending out a questionnaire that you can fill out to the working group. As I did prior to the the -17 draft, I will also create a web site. I, Yakov and Bill really encourage you to report your BGP implementations, and any deployment experience on these forms. Sue Hares At 10:16 AM 1/10/2002 -0800, Bill Fenner wrote: >I am re-sending this message to the IDR mailing list since I didn't >see it come through either on the list or in the archives. > >Subject: Re: 2842 to Draft Standard >Date: Tue, 8 Jan 2002 12:01:37 -0800 >To: yakov@juniper.net >Cc: idr@merit.edu > >IDR WG, > > In order to progress to Draft Standard, an implementation report >is required (see section 4.1.2 of RFC 2026). In particular: > > The requirement for at least two independent and interoperable > implementations applies to all of the options and features of the > specification. > >RFC 2842 has several optional portions (e.g. sending Notifications >and whether to include the capability in question in the Notification), >which the implementation report that you included in the original >request did not mention. > > I'd like to see a more complete implementation report. For >example, if vendors don't mind being named: >http://www.ietf.org/IESG/Implementations/IPCOMP-Implementation.txt >or if they don't want to be named: >http://www.ietf.org/IESG/Implementations/AGENTX-IMPLEMENTATION > > Also, the process would go much more smoothly if there was an >Internet-Draft containing the revision, even though it's so small. >The RFC-Editor can supply the nroff of RFC 2842 if the authors >don't still have their source. > > Bill
- Re: Resending: Re: 2842 to Draft Standard Susan Hares
- Re: Resending: Re: 2842 to Draft Standard Susan Hares
- Re: Resending: Re: 2842 to Draft Standard Susan Hares
- Resending: Re: 2842 to Draft Standard Bill Fenner