RMONMIB WG, OPS-NM Area
Implementation Report for RFC 2895 : 
Remote Network Monitoring MIB Protocol Identifier Reference

WG Chair: Andy Bierman
April 19, 2003
------------------------------

Introduction
------------

This report summarizes the implementation reports received
for RFC 2895. A survey for RFC 2074 was sent to the WG
mailing list and the results shown below are aligned with
that survey form. RFC 2895 contains the normative portions
of RFC 2074, and RFC 2896 contains the informative portions
of RFC 2074. Therefore, the implementation report for RFC 2074 
applies to both RFC 2895 and 2896, but only RFC 2895 is a
standards track document.

Survey Issues
-------------

RFC 2895 defines the Protocol Identifier macro format and
is used for the index structure of the RMON protocol directory
defined in RFC 2021. MIB walks of the protocolDirTable
for multiple independent implementations indicate consistent 
representation of protocol encapsulations. In addition,
multiple independent software tools have been developed
which parse the RMON protocol identifier macro. These tools
are used to assist in the protocol decode engine development for
an RMON-2 agent.

At least two independent implementations of all RMON protocol 
identifier features exist, however there is one minor
feature that was not fully verified by the implementation
reports. Only one returned survey indicated that all protocol
parameters were implemented. These parameters identify
protocol decoding capabilities that are considered to be 
beyond the core feature set of RMON-2 agents.
    
Survey Conclusion
-----------------

The RMONMIB WG believes the requirements for advancement of
the Protocol Identifier Macro specification in RFC 2895 to 
Draft Standard have been met.

Survey Respondents
------------------

There were two responses, labeled 'A' and 'B' in the
response summary section, which correspond to the following 
vendor implementations:

      A == Network Harmoni agent
      B == Cisco Systems Network Analysis Module agent

Survey Response Summary
-----------------------

Key:
      x == fully implemented

                                                                          Developer ID
 PI macro feature description 	        A   B 
-----------------------------------------------
management application                |   |   |
agent                                 | x | x |
-----------------------------------------------
implemented on an RMON probe          | x | x |
embedded in a network device          |   |   |
-----------------------------------------------
ether2                                | x | x |
llc                                   | x | x |
snap                                  | x | x |
vsnap                                 | x | x |
ianaAssigned                          | x | x |
-----------------------------------------------
wild-ether2                           | x | x |
wild-llc                              | x | x |
wild-snap                             | x | x |
wild-vsnap                            | x | x |
-----------------------------------------------
countsFragments                       |   | x |
tracksSessions                        |   | x |
-----------------------------------------------
ipxOverRaw8023                        | x | x |
-----------------------------------------------
PROTOCOL-IDENTIFIER tools?            | x | x |
-----------------------------------------------