SPB Deployment Considerations
draft-lapuh-spb-deployment-01
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
---|---|---|---|
Authors | Roger Lapuh , Paul Unbehagen , Peter J. Ashwood-Smith , Phillip Taylor | ||
Last updated | 2012-09-27 (Latest revision 2012-03-26) | ||
RFC stream | (None) | ||
Formats | |||
Additional resources | |||
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
Based on live deployments and three interoperability events, this document provides advice to network operators about best practices when implementing IEEE 802.1aq Shortest Path Bridging (SPB) networks. It is principally addressed to system integrators and solution providers, including those that do not yet support SPB. Some advice to implementers is also included. The intention of the advice is to facilitate multi vendor network deployments as well as provide guidance for new installations.
Authors
Roger Lapuh
Paul Unbehagen
Peter J. Ashwood-Smith
Phillip Taylor
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)