Issues of HIP in an Operators Networks
draft-dietz-hip-operator-issues-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Thomas Dietz | ||
| Last updated | 2005-10-20 | ||
| 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 discuss the potential issues that arise when the Host Identity Protocol (HIP) will be introduced in a operator network, especially in the IP Multimedia Subsystem (IMS) of the 3GPP systems. It discusses mobile network specific issues like charging, lawful interception as well as common issues like where to associate the HIP ID or privacy issues. The document tries to make the HIP community aware of those issues and wants to stimulate discussion on those topics.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)