Skip to main content

Management Information Base for Intermediate System to Intermediate System (IS-IS)
RFC 4444

Revision differences

Document history

Date Rev. By Action
2015-10-14
26 (System) Notify list changed from chopps@rawdofmt.org, dward@cisco.com, heard@pobox.com, bwijnen@lucent.com to heard@pobox.com, bwijnen@lucent.com, dward@cisco.com
2012-08-22
26 (System) post-migration administrative database adjustment to the No Objection position for Russ Housley
2006-04-20
26 Amy Vezza State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2006-04-20
26 Amy Vezza [Note]: 'RFC 4444' added by Amy Vezza
2006-04-19
26 (System) RFC published
2006-01-20
26 Amy Vezza State Changes to RFC Ed Queue from Approved-announcement sent by Amy Vezza
2006-01-20
26 Amy Vezza IESG state changed to Approved-announcement sent
2006-01-20
26 Amy Vezza IESG has approved the document
2006-01-20
26 Amy Vezza Closed "Approve" ballot
2006-01-17
26 Alex Zinin State Changes to Approved-announcement to be sent from IESG Evaluation::AD Followup by Alex Zinin
2006-01-02
26 Russ Housley [Ballot Position Update] Position for Russ Housley has been changed to No Objection from Discuss by Russ Housley
2005-12-29
26 (System) New version available: draft-ietf-isis-wg-mib-26.txt
2005-12-28
25 (System) New version available: draft-ietf-isis-wg-mib-25.txt
2005-12-02
26 (System) Removed from agenda for telechat - 2005-12-01
2005-12-01
26 Bill Fenner State Changes to IESG Evaluation::AD Followup from IESG Evaluation by Bill Fenner
2005-12-01
26 Bill Fenner Removing from telechat; all the positions are in and we don't need to discuss the DISCUSSes on the call.
2005-12-01
26 Allison Mankin [Ballot Position Update] New position, No Objection, has been recorded for Allison Mankin by Allison Mankin
2005-12-01
26 Bert Wijnen
[Ballot comment]
W.r.t. the Security Considerations Section.
After we saw the comment from the GEN-ART review, there was
continued discussion between the MIB doctors if …
[Ballot comment]
W.r.t. the Security Considerations Section.
After we saw the comment from the GEN-ART review, there was
continued discussion between the MIB doctors if that section
needed to elaborate and list the speicific objects with their
specific vulnerabilities. In total there are some 64 writable
objects that may need discussion (either separate or in chuncks).

Russ has taken a DISCUSS on that and I think that the MIB doctors
have rough consensus that it would be BETTER if indeed some more
detail was given. Even if all 64 objects have the same sensitivity,
even then it would be good to make such an explicit statement. But
it is not clear that they indeed all have the same sensistivity and
would all cause the same type of harm if changed in an unauthorized
manner.
2005-12-01
26 Bert Wijnen [Ballot Position Update] New position, Yes, has been recorded for Bert Wijnen by Bert Wijnen
2005-12-01
26 Jon Peterson [Ballot Position Update] New position, No Objection, has been recorded for Jon Peterson by Jon Peterson
2005-11-30
26 Bill Fenner [Ballot Position Update] New position, No Objection, has been recorded for Bill Fenner by Bill Fenner
2005-11-30
26 David Kessens [Ballot Position Update] New position, No Objection, has been recorded for David Kessens by David Kessens
2005-11-30
26 Russ Housley
[Ballot discuss]
The Overview in Section 2 says:
  >
  > This document is provided to the IETF working group on IS-IS.
  > …
[Ballot discuss]
The Overview in Section 2 says:
  >
  > This document is provided to the IETF working group on IS-IS.
  >
  Isn't this an output of the IS-IS WG?

  The Security Considerations in Section 7 says:
  >
  > There are a number of management objects defined in this MIB that
  > have a MAX-ACCESS clause of read-write and/or read-create.  Such
  > objects may be considered sensitive or vulnerable in some network
  > environments.
  >
  and
  >
  > Since the MIB controls a device which routes  packets, all
  > writeable attributes have the potential to disrupt network
  > operations if improperly modified and may require protection
  > against unauthorized write access.
  >
  Which managed objects?  What are the consequences (besides denial
  of service) should these managed objects be set to inappropriate
  values?  For example, can any of these managed objects cause
  traffic to be routed in an unexpected manner to aid eavesdropping?
2005-11-30
26 Russ Housley [Ballot Position Update] New position, Discuss, has been recorded for Russ Housley by Russ Housley
2005-11-30
26 Margaret Cullen [Ballot Position Update] New position, No Objection, has been recorded for Margaret Wasserman by Margaret Wasserman
2005-11-30
26 Mark Townsley [Ballot Position Update] New position, No Objection, has been recorded for Mark Townsley by Mark Townsley
2005-11-29
26 Ted Hardie [Ballot Position Update] New position, No Objection, has been recorded for Ted Hardie by Ted Hardie
2005-11-29
26 Sam Hartman [Ballot Position Update] New position, No Objection, has been recorded for Sam Hartman by Sam Hartman
2005-11-27
26 Bert Wijnen State Change Notice email list have been change to chopps@rawdofmt.org, dward@cisco.com; heard@pobox.com; bwijnen@lucent.com from chopps@rawdofmt.org, dward@cisco.com
2005-11-23
26 Scott Hollenbeck [Ballot Position Update] New position, No Objection, has been recorded for Scott Hollenbeck by Scott Hollenbeck
2005-11-22
26 Brian Carpenter [Ballot Position Update] Position for Brian Carpenter has been changed to No Objection from Undefined by Brian Carpenter
2005-11-22
26 Brian Carpenter
[Ballot comment]
(From Gen-ART review by David Black)

- Section 2, Overview:

  This document is provided to the IETF working group on IS-IS.  It …
[Ballot comment]
(From Gen-ART review by David Black)

- Section 2, Overview:

  This document is provided to the IETF working group on IS-IS.  It
  describes a management information base for the IS-IS Routing
  protocol as described in ISO 10589 [ISO10589], when it is used to
  construct routing tables for IP networks, as described in RFC 1195
  [RFC1195].

Remove first sentence (will no longer be appropriate when this is
published as an RFC0, and rephrase second to "This document describes ...".

- Section 6, Acknowledgements:

Was an extra "r" added to Chris Gunner's name?

- Section 7, Security Considerations

This is ok in its current form, although it would be improved with
references to specific MIB tables/objects, even as examples of how
uncontrolled write access could cause problems.  The references are
not essential, as the threat of uncontrolled write access is both
obvious and compelling as described.
2005-11-22
26 Brian Carpenter [Ballot Position Update] New position, Undefined, has been recorded for Brian Carpenter by Brian Carpenter
2005-11-17
26 Alex Zinin Placed on agenda for telechat - 2005-12-01 by Alex Zinin
2005-11-17
26 Alex Zinin State Changes to IESG Evaluation from Waiting for Writeup by Alex Zinin
2005-11-17
26 Alex Zinin [Ballot Position Update] New position, Yes, has been recorded for Alex Zinin
2005-11-17
26 Alex Zinin Ballot has been issued by Alex Zinin
2005-11-17
26 Alex Zinin Created "Approve" ballot
2005-11-14
26 (System) State has been changed to Waiting for Writeup from In Last Call by system
2005-11-02
26 Michelle Cotton
IANA Last Call Comments:
Upon approval of this document the IANA will assign a mib-2 number for isisMIB. This registration will be made in the …
IANA Last Call Comments:
Upon approval of this document the IANA will assign a mib-2 number for isisMIB. This registration will be made in the mib-2 numbers registry found at:
http://www.iana.org/assignments/smi-numbers
2005-10-31
26 Amy Vezza Last call sent
2005-10-31
26 Amy Vezza State Changes to In Last Call from Last Call Requested by Amy Vezza
2005-10-28
26 Alex Zinin State Changes to Last Call Requested from Publication Requested by Alex Zinin
2005-10-28
26 Alex Zinin Last Call was requested by Alex Zinin
2005-10-28
26 (System) Ballot writeup text was added
2005-10-28
26 (System) Last call text was added
2005-10-28
26 (System) Ballot approval text was added
2005-10-28
26 Alex Zinin Intended Status has been changed to Proposed Standard from None
2005-10-27
26 Alex Zinin Draft Added by Alex Zinin in state Publication Requested
2005-10-21
24 (System) New version available: draft-ietf-isis-wg-mib-24.txt
2005-10-03
23 (System) New version available: draft-ietf-isis-wg-mib-23.txt
2005-07-11
22 (System) New version available: draft-ietf-isis-wg-mib-22.txt
2005-06-24
21 (System) New version available: draft-ietf-isis-wg-mib-21.txt
2005-05-02
20 (System) New version available: draft-ietf-isis-wg-mib-20.txt
2005-04-12
19 (System) New version available: draft-ietf-isis-wg-mib-19.txt
2005-02-18
18 (System) New version available: draft-ietf-isis-wg-mib-18.txt
2005-02-10
17 (System) New version available: draft-ietf-isis-wg-mib-17.txt
2004-07-06
16 (System) New version available: draft-ietf-isis-wg-mib-16.txt
2004-06-03
15 (System) New version available: draft-ietf-isis-wg-mib-15.txt
2004-05-05
14 (System) New version available: draft-ietf-isis-wg-mib-14.txt
2004-01-20
13 (System) New version available: draft-ietf-isis-wg-mib-13.txt
2003-04-04
12 (System) New version available: draft-ietf-isis-wg-mib-12.txt
2003-02-27
11 (System) New version available: draft-ietf-isis-wg-mib-11.txt
2002-10-21
10 (System) New version available: draft-ietf-isis-wg-mib-10.txt
2002-08-14
09 (System) New version available: draft-ietf-isis-wg-mib-09.txt
2002-05-07
08 (System) New version available: draft-ietf-isis-wg-mib-08.txt
2002-01-14
07 (System) New version available: draft-ietf-isis-wg-mib-07.txt
2001-11-21
06 (System) New version available: draft-ietf-isis-wg-mib-06.txt
2001-09-06
05 (System) New version available: draft-ietf-isis-wg-mib-05.txt
2001-04-27
04 (System) New version available: draft-ietf-isis-wg-mib-04.txt
2000-06-28
03 (System) New version available: draft-ietf-isis-wg-mib-03.txt
1999-06-15
02 (System) New version available: draft-ietf-isis-wg-mib-02.txt
1999-04-29
01 (System) New version available: draft-ietf-isis-wg-mib-01.txt
1999-03-03
00 (System) New version available: draft-ietf-isis-wg-mib-00.txt