On 20-Jan-06, at 6:46 AM, Peter Davis wrote:
On 1/19/2006 9:38 PM, "John Merrells" <[EMAIL PROTECTED]> wrote:
... but I might be on a call to a call center and they ask me to
prove something about me... right now they ask a bunch of
questions... SSN, MMN, DOB... with DIX over SIP they might
be able to send the request to my client and assuming it
had the appropriate interface (ie capabilities) it could ask
me if i wanted to reveal that identity information... i'd click
yes and it'd be revealed. Which sounds quite nice to me.
SIP presently has means to 'prove' the identity of the calling party
sip-identity [1] which supplies a new header (and some hash/
signing). While
it is presently in ID, it is header to RFC editor queue.
Hey.... you sniped off my caveat... 'not really knowing anything
about SIP i'm not very well qualified to say...', pout ;-)
It would be for the SIP WG to draft a binding of 'dix' with sip-
identity,
IMHO. At least for the purposes laid out in the above use case.
Yep. Transport bindings should be done in the WG that makes
most sense for that transport. Some WGs have wound down
of course, which would mean doing them in DIX, or spinning
up a new group.
John
_______________________________________________
dix mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/dix
