RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-03.txt

["Rohit Rohit" <[e-mail]>]

Hi Alex, 

  I have never heard of "MAX-ACCESS  write-only"

  I have heard it to be read-only; read-write or read-create.

  Thanks
  Rohit
   

-----Original Message-----
From: Alex Ruzin [mailto:[e-mail]]
Sent: Thursday, May 23, 2002 8:14 AM
To: [e-mail]
Cc: [e-mail]
Subject: RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-03.txt


[This comment isn't devoted to this edition of the draft,
but to all previous editions too]

It seems to me, that the object dot1dStpPortEnable doesn't reflect a *port
state*
as it is defined in "IEEE 802.1D-1998: Section 8.5.5.2"; rather it
correspondents to "Force port state" from Section 14.8.2.2.
I propose to discuss an option to:
1) do this object "MAX-ACCESS  write-only"
2) set possible values as
        SYNTAX      INTEGER {
                        forceBlock(1),
                        forceDisable(2)
                    }
3) change REFERENCE: "IEEE 802.1D-1998: Section 14.8.2.2"

Yours faithfully, Alex

> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]]On
> Behalf Of [e-mail]
> Sent: Thursday, May 23, 2002 1:30 PM
> To: IETF-Announce:
> Cc: [e-mail]
> Subject: [Bridge-mib] I-D
> ACTION:draft-ietf-bridge-bridgemib-smiv2-03.txt
>
>
> A New Internet-Draft is available from the on-line
> Internet-Drafts directories.
> This draft is a work item of the Bridge MIB Working Group of the IETF.
>
> 	Title		: Definitions of Managed Objects for Bridges
> 	Author(s)	: K. Norseth, E. Bell
> 	Filename	: draft-ietf-bridge-bridgemib-smiv2-03.txt
> 	Pages		: 36
> 	Date		: 22-May-02
>
> This memo defines a portion of the Management Information Base (MIB)
> for use with network management protocols in TCP/IP based internets.
> In particular it defines objects for managing MAC bridges based on
> the IEEE 802.1D-1998 standard between Local Area Network (LAN)
> segments.  Provisions are made for support of transparent bridging.
> Provisions are also made so that these objects apply to bridges
> connected by subnetworks other than LAN segments.
> The MIB presented in this memo is a direct translation of the BRIDGE
> MIB defined in [RFC1493], to the SMIv2 syntax required for current
> IETF MIB standards.  This memo obsoletes RFC 1493.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-bridge-bridgemi
b-smiv2-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-bridge-bridgemib-smiv2-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:
	[e-mail].
In the body type:
	"FILE /internet-drafts/draft-ietf-bridge-bridgemib-smiv2-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.


_______________________________________________
Bridge-mib mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/bridge-mib

_______________________________________________
Bridge-mib mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/bridge-mib