Differentiated Services and Tunnels
draft-black-diffserv-tunnels-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | David L. Black | ||
| Last updated | 2012-04-18 (Latest revision 1999-10-22) | ||
| Replaced by | draft-ietf-diffserv-tunnels | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-diffserv-tunnels | |
| 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 draft discusses the interaction of Differentiated Services (diffserv) [RFC-2474, RFC-2475] with IP tunnels of various forms. The discussion of tunnels in the diffserv architecture [RFC-2475] has been found to provide insufficient guidance to tunnel designers and implementers. With the aim of providing such guidance, this document describes two conceptual models for the interaction of diffserv with IP tunnels and employs them to explore the resulting configurations and combinations of functionality. An important consideration is how and where diffserv traffic conditioning should be performed in the presence of tunnel encapsulation/decapsulation. A few simple mechanisms are also proposed that limit the complexity that tunnels would otherwise add to the diffserv traffic conditioning model; these mechanisms are also generally useful in situations where more general traffic conditioning is inappropriate or unavailable. Security considerations for IPsec tunnels place some limits on possible functionality in some circumstances. WARNING: The current status of this draft is highly preliminary; its major purpose is to foster discussion within the working group. Above and beyond the usual cautionary notice about not relying on Internet-Drafts, implementers are specifically warned that significant changes are expected to the contents of this draft.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)