Providing for Multiple-Proxy Authentication of a SIP Request
draft-sparks-sip-multiproxy-auth-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Robert Sparks | ||
Last updated | 1999-10-21 | ||
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/2.0 as specified in RFC2543 provides a mechanism for a proxy involved in a SIP transaction to authenticate the originator of the request. Unfortunately, this mechanism is not well defined when more than one proxy in a request’s path desires such authentication. This draft proposes a mechanism that would allow authentication in that scenario to work as expected. Under this proposal, SIP clients would issue requests with multiple Proxy-Authorization headers, one for each challenge it has seen in the lifetime of a given call leg. Authenticating SIP proxies would search each request for a Proxy- Authorization response to its own challenge, passing any others downstream unaltered.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)