E.164 Ownership Problem Statement
draft-schwartz-sip-e164-ownership-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | David Schwartz , Hadriel Kaplan , Klaus Darilion , Hannes Tschofenig | ||
| Last updated | 2008-02-25 (Latest revision 2008-02-18) | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
html
xml
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-schwartz-sip-e164-ownership-01.txt
Abstract
When a call travels end-to-end relayed from the PSTN to SIP then problems occur with E.164 number ownership. Additionally, there are security challenges when the PSTN-VoIP gateway has to authenticate and authorize the calling party. Without addressing these two aspects the overall security story is weak or non-existent. This document aims to investigate these two aspect; it does, however, not investigate current E.164 number handling with RFC 4474 ("SIP Identity"). Such an analysis is provided by other documents already.
Authors
David Schwartz
Hadriel Kaplan
Klaus Darilion
Hannes Tschofenig
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)