3GPP TFT Reference for Flow Binding
draft-jeyatharan-mext-flow-tftemp-reference-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mohana Jeyatharan , Chan-Wah Ng | ||
| Last updated | 2010-10-24 | ||
| 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 memo describes a reference to third generation partner ship project (3GPP) defined traffic flow template (TFT) as a traffic selector in the flow based routing mechanism described in the flow binding draft [1]. This memo, further specifies a new traffic selector sub-option format to be used with the flow binding mobility option defined in draft [1], in order to transport the TFT reference from the mobile node to its home agent in a 3GPP SAE (service architecture evolution) scenario.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)