Ethernet MAC Chaining
draft-fedyk-sfc-mac-chain-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Paul Bottorff , Don Fedyk , Hamid Assarpour | ||
Last updated | 2017-01-23 (Latest revision 2016-07-22) | ||
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 document introduces and describes a simple and highly scalable service function chaining mechanism called MAC chaining which is built largely on existing Ethernet frame and forwarding capabilities. MAC chaining uses IEEE 802 Media Access Control (MAC) addresses to provide flexible and complete service function chains. It is largely transparent to layers above Ethernet and designed to augment and coexist with existing virtual and physical network forwarding. MAC chaining is achievable in some devices and virtual switches today using existing protocols.
Authors
Paul Bottorff
Don Fedyk
Hamid Assarpour
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)