Re: WG last call: Coex draft

I would suggest that snmpCommunityName and snmpTrapCommunity should have
size restrictions.  While SMIv2 has an implied limit of 64k for OCTET
STRING, it's not particularly realistic to have 64k community strings, let
alone in the table.  Unfortunately SNMPv1 and v2c don't specify a
community string size limit, so choosing one that's appropriate and agreed
upon may be difficult.

On Wed, 18 Dec 2002, Harrington, David wrote:

> Date: Wed, 18 Dec 2002 11:07:34 -0500
> From: "Harrington, David" <[email protected]>
> To: [email protected]
> Cc: "Russ Mundy (E-mail)" <[email protected]>,
>      "Randy Bush (E-mail)" <[email protected]>
> 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
>
>
> > -----Original Message-----
> > From: [email protected] [mailto:[email protected]]
> > Sent: Wednesday, December 18, 2002 8:04 AM
> > Cc: [email protected]
> > Subject: I-D ACTION:draft-ietf-snmpv3-coex-v2-02.txt
> >
> >
> > A New Internet-Draft is available from the on-line
> > Internet-Drafts directories.
> > This draft is a work item of the SNMP Version 3 Working Group
> > of the IETF.
> >
> > 	Title		: Coexistence between Version 1,
> > Version 2, and Version
> >                           3 of the Internet-standard Network
> > Management
> >                           Framework
> > 	Author(s)	: R. Frye, D. Levine, S. Routhier, B. Wijnen
> > 	Filename	: draft-ietf-snmpv3-coex-v2-02.txt
> > 	Pages		: 55
> > 	Date		: 2002-12-16
> >
> > The purpose of this document is to describe coexistence between
> > version 3 of the Internet-standard Network Management Framework,
> > (SNMPv3), version 2 of the Internet-standard Network Management
> > Framework (SNMPv2), and the original Internet-standard Network
> > Management Framework (SNMPv1).  This document obsoletes RFC 2576
> > [21].
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-snmpv3-coex-v2-02.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-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.
> >
>

--
Michael Kirkham
www.muonics.com