Classification of traffic using Application Tags
draft-jpathra-application-tag-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jagannathan Pathra B , Prabhuraj K | ||
| Last updated | 2009-05-11 | ||
| 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 describes a solution to classify Application-Layer traffic on switches using Application Tags. The Application Tags can be passed on to other switches in the Enterprise Network and also to switches in the Service Provider Network. Thus it provides a mechanism to classify and apply Quality of Service based on the Application-Layer Traffic. The advantage of this solution is that it requires no hardware upgrade on switch nor any Deep Packet Inspection (DPI) function on the switch. 1. Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 2. Table of Contents 1. Conventions.....................................................2 2.
Authors
Jagannathan Pathra B
Prabhuraj K
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)