Skip to main content

Remote Network Monitoring MIB Protocol Identifier Reference
RFC 2895

Revision differences

Document history

Date By Action
2015-10-14
(System) Notify list changed from  to (None)
2003-09-24
Bert Wijnen State Changes to RFC Published from RFC Ed Queue by Bert Wijnen
2003-09-24
Bert Wijnen RFC2895 is now labeled Draft Standard
2003-09-24
Bert Wijnen State Change Notice email list have been change to from
2003-09-24
Bert Wijnen Status date has been changed to 2003-09-24 from 2003-06-03
2003-08-18
Michael Lee State Changes to RFC Ed Queue from Approved-announcement sent by Michael Lee
2003-08-15
Michael Lee IESG state changed to Approved-announcement sent
2003-08-15
Michael Lee IESG has approved the document
2003-06-13
Jacqueline Hargest State Changes to Approved-announcement to be sent from IESG Evaluation by Hargest, Jacqueline
2003-06-05
Bert Wijnen On IESG agenda for June 12th
Responsible: bert/iesg
2003-06-05
Bert Wijnen State Changes to IESG Evaluation from Waiting for Writeup by Wijnen, Bert
2003-06-03
Bert Wijnen
One IETF Last Call comment received from IANA.
Andy (WG chair) answered it, see below.
AD is checking with IANA if this is acceptable response. …
One IETF Last Call comment received from IANA.
Andy (WG chair) answered it, see below.
AD is checking with IANA if this is acceptable response.

-----Original Message-----
From: Andy Bierman [mailto:abierman@cisco.com]
Sent: donderdag 29 mei 2003 4:50
To: IANA
Cc: iesg@ietf.org; cbucci@cisco.com
Subject: RE: Last Call: Remote Network Monitoring MIB Protocol
Identifier Reference to Draft Standard


At 11:41 AM 5/27/2003, IANA wrote:
>IESG:
>
>The IANA has reviewed RFC RFC2895 'Remote Network Monitoring MIB
>Protocol Identifier Reference' which is in Last Call, and has the
>following comments with regards to the consideration of the document
>as draft standard:
>
>In RFC2895, there are many references to IANA in this document.
>It was published right before I was actively working on IANA
>Actions for documents.  I am having trouble finding some of the
>IANA items described in the document.  I believe that a reference
>will need to be changed somewhere, just not sure exactly where.
>
>If anyone can assist me on this one, it would be appreciated.
>
>Please respond to the IANA about our concerns with regards to this
>document.  Failing to do so may cause delay of the approval and
>publication of your document.

-------------------------------------------------

last paragraph, section 2.3:

  Macros submissions will be collected in the IANA's MIB files under
  the directory "ftp://ftp.isi.edu/mib/rmonmib/rmon2_pi_macros/" and in
  the RMONMIB working group mailing list message archive file
  www.ietf.org/mail-archive/working-
  groups/rmonmib/current/maillist.htm.

To date, no submissions have been made to the WG for inclusion
in this rmon2_pi_macros directory.  It is doubtful that any
such macros will ever be submitted.

------------------------------------

page 30:

-- The following protocol-variant-identifier macro declarations are
-- used to identify the RMONMIB IANA assigned protocols in a
-- proprietary way, by simple enumeration.

ipxOverRaw8023 PROTOCOL-IDENTIFIER
    VARIANT-OF  ipx
    PARAMETERS      { }
    ATTRIBUTES  { }
    DESCRIPTION
      "This pseudo-protocol describes an encapsulation of IPX over
      802.3, without a type field.

      Refer to the macro for IPX for additional information about this
      protocol."
    DECODING
      "Whenever the 802.3 header indicates LLC a set of protocol
      specific tests needs to be applied to determine whether this is a
      'raw8023' packet or a true 802.2 packet.  The nature of these
      tests depends on the active child protocols for 'raw8023' and is
      beyond the scope of this document."
    ::= {
    ianaAssigned 1,            -- [0.0.0.1]
    802-1Q      0x05000001    -- 1Q_IANA [5.0.0.1]
    }

This is the only RMON PI macro currently defined that is
rooted under the 'ianaAssigned' subtree.  It is assigned
the value '1'.  I don't know where these subtree assignments
are stored by IANA.  I don't think the RFC specifies where
they are stored -- it just says the numbers are assigned
by IANA.

----------------------------------------------------

I think these are the only places in the RFC that refer to
IANA controlled info.  Let me know if you have more questions.



>Thank you.
>
>Michelle S. Cotton
>(on behalf of the IANA)

Andy
2003-06-03
Bert Wijnen Status date has been changed to 2003-06-03 from 2003-06-05
2003-06-03
Bert Wijnen State Changes to Waiting for Writeup from In Last Call by Wijnen, Bert
2003-05-22
Amy Vezza Status date has been changed to 2003-06-05 from 2003-05-10
2003-05-22
Amy Vezza State Changes to In Last Call from Last Call Requested by Vezza, Amy
2003-05-21
(System) Last call sent
2003-05-20
(System) Last call text was added
2003-05-10
Bert Wijnen State Changes to Last Call Requested from AD Evaluation by Wijnen, Bert
2003-05-10
Bert Wijnen State Changes to AD Evaluation from Publication Requested by Wijnen, Bert
2003-05-10
Bert Wijnen WG (chair) has filed a implementation/interoperability report. Request to advance to Draft Standard.
2003-05-10
Bert Wijnen Status date has been changed to 2003-05-10 from
2003-05-09
Barbara Fuller Draft Added by Fuller, Barbara
2000-08-01
(System) RFC published