A Registry Investigation for IPPM Packet Delay Variation Metrics
draft-morton-ippm-registry-pdv-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Al Morton | ||
| Last updated | 2014-03-03 (Latest revision 2013-08-27) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This memo investigates a scheme to organize registry entries, primarily those defined in RFCs prepared in the IP Performance Metrics (IPPM) Working Group of the IETF. Three aspects make IPPM metric registration difficult: (1) Use of the Type-P notion to allow users to specify their own packet types. (2) Use of Flexible input variables, called Parameters in IPPM definitions, some which determine the quantity measured and others which should not be specified until execution of the measurement. (3) Allowing flexibility in choice of statistics to summarize the results on a stream of measurement packets. Specifically, this memo investigates registry entries that would follow from RFC 3393, the specification IP Packet Delay Variation that allows for many different forms of unique metrics, as a difficult and important test of the registry structure.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)