SIP E.164 Return Routability Check (RRC)
draft-wing-sip-e164-rrc-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Dan Wing | ||
Last updated | 2008-02-08 | ||
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
SIP lacks a mechanism to determine which domain can claim ownership of a certain telephone number. Due to this, it is impossible to establish meaningful identity or to authenticate endpoints that use telephone number URIs and domain names in their From address. This document proposes a solution to this problem using a return routability test.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)