1 / 6

56th IETF Meeting - March 2003 - RMON Working Group

56th IETF Meeting - March 2003 - RMON Working Group. Emile STEPHAN France Telecom R & D IPv6 & SUBIP Protocol identifiers needs. Summary. 6QM IST project. IPv6 protocol identifier needs SUB IP protocol identifier needs Usage Conclusion. 6QM IST project.

tavia
Télécharger la présentation

56th IETF Meeting - March 2003 - RMON Working Group

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 56th IETF Meeting - March 2003 - RMON Working Group Emile STEPHAN France Telecom R&D IPv6 & SUBIP Protocol identifiers needs

  2. Summary • 6QM IST project. • IPv6 protocol identifier needs • SUB IP protocol identifier needs • Usage • Conclusion

  3. 6QM IST project • IPv6 QOS measurement: • The project goal is the research, development and integration of the different pieces needed for the correct measurement of the Quality of Service in IPv6 networks. • September 2002 - September 2004 • www.6qm.org • Work Plan: · WP2 Requirement Study for IPv6 QoS Measurement; · WP3 Development of IPv6 Measurement Technology; ·  WP4 System Integration, Testing, and Evaluation; ·  WP5 Dissemination, Liaison and Interconnection.

  4. IPPM REPORTING MIB protocol identifier needs • TypeP: TypeP is defined as a display string. It consists in a list of dot separated protocol names. Each protocol name has been previously defined using the macro PROTOCOL-IDENTIFIER (PI) of the RFC 2895. • TypePaddress: TypePaddress is defined as a display string. It consists in a list of space separated parameters. A parameter corresponds to a parameter of a TypeP. • Example : • The RFC2896 defines the PI ‘ip’ and ‘ipip4’. Each one have a parameter. The TypeP 'ip.ipip4' has 2 parameters. A valid TypePaddress value is '192.168.1.1 128.2.6.7'. • Needs : Update the existing PIs with PIs for IPv6 and SUB IP to get e.g.: A valid TypePaddress of the typeP ‘ip.ipip6.udp’ will be '192.168.1.1 2001:0798:16::1’

  5. SUB IP protocol identifier needs • IPv6 • IPv6 • IPv6 in IPv4 • IPv4 in IPv6 • SUB IP • Vlan • MPLS • …

  6. Conclusion • IPv6 and SUB IP Protocol identifier needed for the IPPM REPORTING MIB • How can managers and agents interoperate if the number of parameters differ ? • RMON2 MIB: • How can current managers and agents interoperate if the PI of a protocol is not defined ? • How to continue ?

More Related