1 / 7

RMONMIB WG 57th IETF Vienna, Austria July 14, 2003

This agenda discusses the progress and completion status of various RMONMIB documents, including the RAQMON framework, RAQMON PDU, RAQMON MIB, IPv6 Protocol Identifiers, APM-MIB, TPM-MIB, and SSPM-MIB. It also addresses unresolved issues, updates to the TimeFilter TC, and the acceptance of new work items related to IPv6 Protocol Identifiers. The agenda aims to ensure document completeness and readiness for WG Last Call.

pamelawalker
Télécharger la présentation

RMONMIB WG 57th IETF Vienna, Austria July 14, 2003

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. RMONMIB WG57th IETFVienna, AustriaJuly 14, 2003 Discussion: rmonmib@ietf.orgAdmin: http://www.ietf.org/mailman/listinfo/rmonmib

  2. RMONMIB WG Agenda -- I-Ds • RAQMON Framework • draft-ietf-rmonmib-raqmon-framework-02.txt • RAQMON PDU • draft-ietf-rmonmib-raqmon-pdu-02.txt • RAQMON MIB • draft-ietf-rmonmib-raqmon-mib-01.txt • Protocol Identifiers for IPv6 • draft-stephan-ipv6-protocol-identifier-00.txt • APM-MIB • draft-ietf-rmonmib-apm-mib-09.txt • TPM-MIB • draft-ietf-rmonmib-tpm-mib-09.txt • SSPM-MIB • draft-ietf-rmonmib-sspm-mib-07.txt

  3. RMONMIB WG Agenda (1/2) • WG Status (15 minutes) • Status of documents in the publication pipeline. • Determine if there are any unresolved issues in the APM-MIB (E), TPM-MIB (F), or SSPM-MIB (G). • Fixing the TimeFilter TC and updating RFC 2021 (15 minutes) • Discussion of email proposal (6/19/03) to create new timeFilterMode MIB object. • Real-time Application Quality of Service Monitoring (100 min) • Make sure there is minimal overlap between documents and no missing pieces. Determine if the entire RAQMON monitoring solution is complete. • Discussion of the RAQMON Framework (A) • Determine if the framework is complete and ready for WG Last Call. • Discussion of the RAQMON PDU (B) • Determine if the PDU is complete and ready for WG Last Call. • Discussion of the RAQMON MIB (C) • Determine if the MIB is complete and ready for WG Last Call.

  4. RMONMIB WG Agenda (2/2) • Protocol Identifiers for IPv6 (D) (20 minutes) • Determine if the RMONMIB WG is interested in accepting this work item. If so, • Determine scope of work • Standards track or informational RFC? • Individual submission or WG document? • Timeframe for publication milestones

  5. Status of completed documents • Advancement of RFC 2895 to DS (RMON PI Reference) • Approved by IESG in June 2003 • Advancement of RFC 2613 to DS (SMON MIB) • Waiting for advancement to Draft Standard of RFC 2021 • Advancement of RFC 2021 to DS (RMON2-MIB) • Waiting for new version with WG approved changes • APM-MIB • draft-ietf-rmonmib-apm-mib-09.txt should be final version • TPM-MIB • draft-ietf-rmonmib-tpm-mib-09.txt should be final version • SSPM-MIB • draft-ietf-rmonmib-sspm-mib-07.txt should be final version • Introduction to RMON Family of MIBs • Approved by IESG in June 2003

  6. WG Milestones Behind Schedule • Apr 03 • Begin Working Group Last Call for the Extensions to RMON Framework for RAQMON document • May 03 • Begin Working Group Last Call for the RAQMON PDU Types document • Begin Working Group Last Call for the RAQMON MIB document • Jul 03 • Submit the Extensions to RMON Framework for RAQMON document to the IESG for publication consideration as an Informational RFC

  7. TimeFilter update • Problem • TimeFilter behavior causes excessive data to be returned in mibwalks and getBulk PDUs • Old Solution Proposal • timeFilterMode MIB object indicates if the agent conforms to existing RFC 2021 semantics (stopAfterAll) or if it performs data reduction and eliminates redundant rows (stopAfterOne) • New Solution Proposal • Let agent developers implement TimeFilter either way. • No new MIB object needed • NMS algorithm to handle TimeFilter exactly the same either way (I.e., watch TF index and wait for it to increment)

More Related