Reflexive DSCP Policy
draft-ietf-ieprep-reflexive-dscp-02
Document | Type |
Expired Internet-Draft
(ieprep WG)
Expired & archived
|
|
---|---|---|---|
Authors | Fred Baker , Ray Aatarashi | ||
Last updated | 2015-10-14 (Latest revision 2003-07-02) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired (IESG: Dead) | |
Action Holders |
(None)
|
||
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | Jon Peterson | ||
IESG note | ** No value found for 'doc.notedoc.note' ** | ||
Send notices to | <kimberly.s.king@saic.com> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
In reviewing the specific use of the Differentiated Services Architecture for supporting the Internet Emergency Preparedness System, we found what we believe is a general issue. This is that even though a client or peer can connect to a server or peer with a predictable DSCP value, the response does not have a predictable DSCP value. We consider the issues, and recommend an approach to application policy regarding the DSCP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)