[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: I-D ACTION:draft-ietf-tewg-measure-06.txt
- To: "'Lai, Wai S \(Waisum\), ALABS'" <wlai@att.com>, <te-wg@ops.ietf.org>
- Subject: RE: I-D ACTION:draft-ietf-tewg-measure-06.txt
- From: "Thomas D. Nadeau" <tnadeau@cisco.com>
- Date: Fri, 7 Nov 2003 12:45:22 -0500
- Cc: "'Wijnen, Bert \(Bert\)'" <bwijnen@lucent.com>, "'Jim Boyle'" <jboyle@pdnets.com>, "'Ash, Gerald R \(Jerry\), ALABS'" <gash@att.com>
- In-reply-to: <7AFE40EF30EE754DA967D1B5968457CA02165E71@KCCLUST06EVS1.ugd.att.com>
- Organization: Cisco Systems, inc.
- Reply-to: <tnadeau@cisco.com>
>TEWG,
> The above I-D currently proposes a set of TE measurement
>requirements.
>The are extracted below. I would like to ask WG opinion:
>. should any or all of these requirements be dropped as they are not
> "additional measurements needed for TE" as described in the TEWG
> charter?
>. are there any "additional measurements needed for TE" that
>are missing
> from the list below and hence should be included?
These requirements seem to be reasonable and
necessary for the development of TE-based tools
and the refinement of existing ones.
--Tom
>Thanks, Wai Sum
>
>*********
>Summary of requirements extracted from the above I-D:
>
> For interoperable compatibility and consistency,
> requirements for traffic measurement recommended for
>standardization
> include:
>
> (1) Requirements for specific TE measurements
>
> . Node-pair-based traffic data to derive per-service-class traffic
> matrix statistics, including statistics of carried load and
> offered load (Sections 3.3 and Appendix A)
> . Statistics of achieved performance and throughput (Section 3.4)
> . A standardized method to detect and record label binding changes
> for LDP-signaled label-switched paths, at the ingress-egress pair
> level (Section 3.5)
>
> (2) Requirements for traffic data collection methods
>
> . Standardization of measurement definitions and sampling methods,
> to achieve uniformity across vendors and operators, and to
> preserve sufficient traffic detail at manageable sample volumes
> (Section 6 and Appendix C)
> . Higher-order statistics to facilitate service assurance (Section
> 3.1)
> . Offline bulk file transfer and standardized filtering/aggregation
> mechanisms to manage large volumes of measured traffic data
> (Section 5 and Appendix D)
> . Linkage between policy mechanisms and TE measurement, possibly
> triggered by a measurement-driven event notification (Section 5)
> . Standardization of information models for TE measurement (Section
> 5)
>
>