Use of 802.1ag for TRILL OAM messages
draft-tissa-trill-8021ag-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tissa Senevirathne , Samer Salam , Donald E. Eastlake 3rd , Sam Aldrin , Naveen Nimmu , Tal Mizrahi , Anoop Ghanwani | ||
| Last updated | 2012-12-27 (Latest revision 2012-06-25) | ||
| 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
In this document we present definitions of TRILL OAM messages. Messages defined in this document follow a similar structure to IEEE 802.1ag messages. In this document, only the high level proposal on using IEEE 802.1ag messaging is presented. The goal is to facilitate discussion on feasibility of using IEEE 802.1ag messages for TRILL OAM. Based on feedback from TRILL WG and IEEE 802.1 group, this document may be further updated.
Authors
Tissa Senevirathne
Samer Salam
Donald E. Eastlake 3rd
Sam Aldrin
Naveen Nimmu
Tal Mizrahi
Anoop Ghanwani
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)