On Oct 9, 2007, at 1:34 PM, Paul Kyzivat wrote:
Pars Mutaf wrote:
Thanks! But there is another question first. Will you subscribe:
https://www1.ietf.org/mailman/listinfo/humanresolvers
I subscribe to a lot of lists. I need some motivation before
subscribing to another one. I expect a lot of people on *this* list
are in the same boat.
You have gotten some people to respond to you here, though there is
clearly a lot of skepticism. You will probably have better luck
getting people to discuss here than at a new list. At least maybe
you can try here to make a case for why people want to participate
in your humanresolvers list.
Arguably, this would be more of a candidate for the SIPPING list than
the SIP list.
But as I said, it sounds like using an LDAP front-end. I'd image one
could accomplish this by sending a SIP CONSENT request to a server in
the domain of the target, where the SIP request has as its request
URI and LDAP URL (RFC 2255, I think), with the user's name encoded in
the LDAP URL. Assuming the consent phase hasn't previously occurred,
said server would then look up the user name, translate it thru the
usual SIP mechanisms, and send the CONSENT request onward. If the
user grants consent, then the server would store this, and in the
future either return a 302 with the user's SIP URI.
That's for the particular combination of requirements previously
given. Many alternative approaches, such as proxying the request to
the target rather than returning a 302 and gleaning "consent" based
on the user's response to an initial INVITE request address slight
variations in those requirements.
But I don't really think we need to be talking about this too much on
the SIP list. Perhaps we should wait until the humanresolvers people
better understand their requirements.
--
Dean
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
