Analysis of Rendezvous Mechanism for Home Access Using SIP
draft-saito-sip-rendezvous-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Makoto Saito , Dan Wing | ||
| Last updated | 2008-01-29 | ||
| 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
Home servers are becoming more common and people expect to still access them even when they are outside their home. However, there are several requirements to realize remote access to the home such as name resolution, NAT/Firewall traversal, and authentication/ authorization. This document describes what technologies can be used to solve these issues and analyzes the utility of SIP as a rendezvous mechanism for this use case.Conventions used in this document 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 [RFC2119].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)