Operations and Maintenance Next Generation Requirements
draft-amante-oam-ng-requirements-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2008-02-19 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-amante-oam-ng-requirements-01.txt
Abstract
Current IP and MPLS OAM techniques need to be extended to permit operators to effectively diagnose load-balancing issues. Specifically, new ad-hoc OAM techniques are needed to diganose various link-bundling techniques, such as IP/MPLS Equal Cost Multi- Path (ECMP) and Link Aggregation Groups (LAG). In addition, these OAM tools should also be extended to permit performance monitoring over longer time durations. This document defines requirements for the next generation of OAM solutions.
Authors
Shane Amante
(Shane.Amante@Level3.com)
Alia Atlas
(alia.atlas@bt.com)
Andrew Lange
(andrew.lange@alcatel-lucent.com)
Danny McPherson
(danny@arbot.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)