Emile Stéphan56th IETF - RMON WG1 56th IETF Meeting - March 2003 - RMON Working Group Emile STEPHAN...

6
Emile Stéphan 56th IETF - RMON WG 1 56th IETF Meeting - March 2003 - RMON Working Group Emile STEPHAN France Telecom R&D IPv6 & SUBIP Protocol identifiers needs

Transcript of Emile Stéphan56th IETF - RMON WG1 56th IETF Meeting - March 2003 - RMON Working Group Emile STEPHAN...

Page 1: Emile Stéphan56th IETF - RMON WG1 56th IETF Meeting - March 2003 - RMON Working Group Emile STEPHAN France Telecom R&D IPv6 & SUBIP Protocol identifiers.

Emile Stéphan 56th IETF - RMON WG 1

56th IETF Meeting - March 2003 - RMON Working Group

Emile STEPHAN

France Telecom R&D

IPv6 & SUBIP Protocol identifiers needs

Page 2: Emile Stéphan56th IETF - RMON WG1 56th IETF Meeting - March 2003 - RMON Working Group Emile STEPHAN France Telecom R&D IPv6 & SUBIP Protocol identifiers.

Emile Stéphan 56th IETF - RMON WG 2

• 6QM IST project.

• IPv6 protocol identifier needs

• SUB IP protocol identifier needs

• Usage

• Conclusion

Summary

Page 3: Emile Stéphan56th IETF - RMON WG1 56th IETF Meeting - March 2003 - RMON Working Group Emile STEPHAN France Telecom R&D IPv6 & SUBIP Protocol identifiers.

Emile Stéphan 56th IETF - RMON WG 3

• 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.

6QM IST project

Page 4: Emile Stéphan56th IETF - RMON WG1 56th IETF Meeting - March 2003 - RMON Working Group Emile STEPHAN France Telecom R&D IPv6 & SUBIP Protocol identifiers.

Emile Stéphan 56th IETF - RMON WG 4

• 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’

IPPM REPORTING MIB protocol identifier needs

Page 5: Emile Stéphan56th IETF - RMON WG1 56th IETF Meeting - March 2003 - RMON Working Group Emile STEPHAN France Telecom R&D IPv6 & SUBIP Protocol identifiers.

Emile Stéphan 56th IETF - RMON WG 5

• IPv6• IPv6

• IPv6 in IPv4

• IPv4 in IPv6

• SUB IP• Vlan

• MPLS

• …

SUB IP protocol identifier needs

Page 6: Emile Stéphan56th IETF - RMON WG1 56th IETF Meeting - March 2003 - RMON Working Group Emile STEPHAN France Telecom R&D IPv6 & SUBIP Protocol identifiers.

Emile Stéphan 56th IETF - RMON WG 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 ?