Binding Revocation for IPv6 Mobility
draft-muhanna-mext-binding-revocation-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ahmad Muhanna , Mohamed Khalil , Sri Gundavelli , Kuntal Chowdhury , Parviz Yegani | ||
| Last updated | 2008-10-27 (Latest revision 2008-07-11) | ||
| Replaced by | draft-ietf-mext-binding-revocation | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-mext-binding-revocation | |
| 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 defines the revocation semantics for terminating a mobile node's mobility session and associated resources. These semantics are generic enough and can be used by mobility entities in the case of Client Mobile IPv6 and its extensions. This mechanism allows the mobility entity which initiates the revocation procedure to request its corresponding one to terminate either one, multiple or all specified binding cache entries.
Authors
Ahmad Muhanna
Mohamed Khalil
Sri Gundavelli
Kuntal Chowdhury
Parviz Yegani
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)