Requirements for domain marking for the purpose of Upstream Traffic Characterization
draft-schwartz-sipping-domain-marking-requirements-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | David Schwartz , Diego Besprosvan | ||
| Last updated | 2007-11-12 | ||
| 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
SIP as defined in RFC 3261 [1] defines a Via header as a construct to be used for upstream response routing and for downstream assistance in loop detection. There is an increasing need on downstream administrative domains (ADs) to gain visibility into all the ADs in its upstream path. The information needed is not IP based as internal architectures at upstream ADs is of no consequence to downstream ADs. Logical domain marking, however, is desperately needed for any traffic analysis to occur at the receiving side. Gathering AD information from Via headers is non obvious and in many instances nearly impossible. This documents identifies the requirements for addressing this issue.
Authors
David Schwartz
Diego Besprosvan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)