Some Issues and Applications of Packet Marking
draft-blake-diffserv-marking-00

Document Type Expired Internet-Draft (individual)
Author Steven Blake 
Last updated 1997-12-29
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-blake-diffserv-marking-00.txt

Abstract

''Packet marking'' is proposed as an architectural generalization of the type of service (TOS) and precedence facilities of IPv4 [RFC795, RFC1349], as well as the traffic class facilities of IPv6 [IPv6]. It is intended to encompass all mechanisms by which a host or a router may mark a packet to invoke some differentiated packet handling behavior by another node along the transit path of the packet. This memo examines several proposed applications of a packet marking facility and attempts to categorize each application in terms of the behavioral requirements it imposes on hosts and routers. In addition, issues related to the deployment of packet marking, including provisioning, authorization, and security, are examined. This memo is proposed as a framework to focus discussion on implementation issues and mechanisms as new differentiated services enabled by a packet marking facility are introduced into the Internet.

Authors

Steven Blake (slblake@torrentnet.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)