Skip to main content

Utilizing HIP (Host Identity Protocol) for P2PSIP (Peer-to-peer Session Initiation Protocol)
draft-hautakorpi-p2psip-with-hip-01

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Jani Hautakorpi , Gonzalo Camarillo , Joakim Koskela
Last updated 2007-11-19
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 specifies how Host Identity Protocol (HIP) can be utilized in Peer-to-Peer Session Initiation Protocol (P2PSIP) networks. Peers in a P2PSIP network need to have long-lived connections to other peers in the network, and HIP can be utilized to setup and maintain those connections. HIP is a good choice for connection maintenance, because it provides functionalities like Network Address Translation (NAT) traversal, mobility, multi-homing, and enhanced security properties.

Authors

Jani Hautakorpi
Gonzalo Camarillo
Joakim Koskela

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)