RE: WG last call: Coex draft

Thanks Tom,

dbh

> -----Original Message-----
> From: Tom Petch [mailto:[email protected]]
> Sent: Monday, December 23, 2002 6:14 PM
> To: Harrington, David; [email protected] (E-mail)
> Subject: Re: WG last call: Coex draft
> 
> 
> I am willing to check for grammar and spelling.  Any time left over, I
> will look at the RFC editor issues (but I find the language of those
> guidelines somewhat opaque).
> 
> Tom Petch
> [email protected]
> -----Original Message-----
> From: Harrington, David <[email protected]>
> To: [email protected] (E-mail) <[email protected]>
> Date: 23 December 2002 20:24
> Subject: WG last call: Coex draft
> 
> 
> >Hi,
> >
> >I am looking for two volunteers to review the coex draft for
> non-technical stuff.
> >A URL for this Internet-Draft is:
> >http://www.ietf.org/internet-drafts/draft-ietf-snmpv3-coex-v2-02.txt
> >
> >One volunteer should check it thoroughly against RFC2223, and
> http://www.rfc-editor.org/policy.html, and
> ftp://ftp.ietf.org/ietf/1id-guidelines.txt, and
> http://www.ietf.org/ID-nits.html. There should be lots of overlap in
> these documents (and hopefully little contradiction) so it not as
> large a job as it might appear. Doing this review would be good for
> any current ot future document editors, giving you good training in
> how to write IETF documents in the preferred formats and organization.
> I am willing to have multiple volunteers check the document against a
> subset of these documents.
> >
> >One volunteer should check the language for good grammar and
> spelling. This will require more than running it through "spell" or
> MS-Word's spelling and grammar checkers.
> >
> >We so far have had one person review the document for smilint
> cleanliness. Mike, did you review the document against "Guidelines for
> MIB Authors and Reviewers" in the process?
> >
> >We need more technical review of this document. If you review the
> document (reasonably thoroughly) and find nothing to object to, please
> post a comment to the mailing list stating that you have done such a
> review.
> >
> >Any volunteers?
> >
> >Thanks,
> >dbh
> >---
> >David Harrington
> >[email protected]
> >co-chair, IETF SNMPv3 WG
> >
> >
> >-----Original Message-----
> >From: Harrington, David
> >Sent: Wednesday, December 18, 2002 11:08 AM
> >To: [email protected]
> >Cc: Russ Mundy (E-mail); Randy Bush (E-mail)
> >Subject: WG last call: Coex draft
> >
> >
> >Hi,
> >
> >The WG chairs are starting a WG last call on
> http://www.ietf.org/internet-drafts/draft-ietf-snmpv3-coex-v2-02.txt,
> a new revision of the coexistence document.
> >
> >The last call starts now and completes on January 10th, which permits
> extra time for the holiday season.
> >
> >Thank you,
> >dbh
> >
> >David Harrington
> >[email protected]
> >co-chair, IETF SNMPv3 WG
> >
> >
> >> Title : Coexistence between Version 1,
> >> Version 2, and Version
> >>                           3 of the Internet-standard Network
> >> Management
> >>                           Framework
> >> 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-snmpv3-coex-v2-02.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:
> >> [email protected].
> >> In the body type:
> >> "FILE /internet-drafts/draft-ietf-snmpv3-coex-v2-02.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.
> >>
> 
>