Re: I-D ACTION:draft-ietf-bmwg-ospfconv-term-03.txt

Acee Lindem <acee@REDBACK.COM> Thu, 27 March 2003 17:53 UTC

Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10214 for <ospf-archive@LISTS.IETF.ORG>; Thu, 27 Mar 2003 12:53:51 -0500 (EST)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <2.0094F32A@cherry.ease.lsoft.com>; Thu, 27 Mar 2003 12:56:11 -0500
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 692663 for OSPF@DISCUSS.MICROSOFT.COM; Thu, 27 Mar 2003 12:56:11 -0500
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Thu, 27 Mar 2003 12:56:10 -0500
Received: from redback.com (login005.redback.com [155.53.12.60]) by prattle.redback.com (Postfix) with ESMTP id 44FF39F86BD; Thu, 27 Mar 2003 09:54:03 -0800 (PST)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <200303271245.HAA25376@ietf.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID: <3E833B25.4090709@redback.com>
Date: Thu, 27 Mar 2003 12:55:49 -0500
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Re: I-D ACTION:draft-ietf-bmwg-ospfconv-term-03.txt
Comments: cc: Tom Petch <nwnetworks@DIAL.PIPEX.COM>
To: OSPF@DISCUSS.MICROSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

I believe this revision addresses Tom Petch's comments relating to
the difference in terminolgy between this document and RFC 2328.


Thanks,
Acee

Internet-Drafts@IETF.ORG wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Benchmarking Methodology Working Group of the IETF.
>
>         Title           : OSPF Benchmarking Terminology and Concepts
>         Author(s)       : V. Manral, R. White, A. Shaikh
>         Filename        : draft-ietf-bmwg-ospfconv-term-03.txt
>         Pages           : 9
>         Date            : 2003-3-26
>
> This draft explains the terminology and concepts used in [BENCHMARK]
> and future OSPF benchmarking drafts, within the context of those
> drafts. While some of these terms may be defined elsewhere, and we
> will refer the reader to those definitions in some cases, we also
> include discussions concerning these terms as they relate
> specifically to the tasks involved in benchmarking the OSPF protocol.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-bmwg-ospfconv-term-03.txt
>
> To remove yourself from the IETF Announcement list, send a message to
> ietf-announce-request with the word unsubscribe in the body of the message.
>
> Internet-Drafts are also available by anonymous FTP. Login with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
>         "get draft-ietf-bmwg-ospfconv-term-03.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
>         mailserv@ietf.org.
> In the body type:
>         "FILE /internet-drafts/draft-ietf-bmwg-ospfconv-term-03.txt".
>
> NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
>
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.


--
Acee