[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
[ldapext] IETF solution for pairing cellular hosts
Interested folks are welcome to the following mailing list
for an eventual working group.
The idea has similarities with the phone number directory
approach. Your contributions would be very much welcome
(We are in the problem statement phase for the moment.)
Regards,
pars mutaf
Pairing Cellular Hosts
https://www1.ietf.org/mailman/listinfo/humanresolvers
Currently there are two approaches for obtaining contact information for a
target cell phone: (i) consulting a phonebook, (ii) manually exchanging
phone numbers upon face-to-face user contact. Both approaches have
their own limitations.
The following is a new abstract solution, a third alternative, a protocol
for "pairing" two cellular hosts:
Model of operation
1. The querier user types the target user's "human name" (as if he were
consulting a phonebook), or a pseudoynm.
2. The pairing request is forwarded to the target phone.
3. The query, along with the querier user's name, are displayed on the
target phone's screen.
4. The target user approves the request in real-time by pushing on the YES
button of the phone.
5. The two phones exchange their Mobile IPv6 home addresses, SIP URIs, and
establish an IPsec security association (using IKEv2).
The target user does not need to publish his/her private SIP URI and home
address (as recommended in [1] in SIP context). Cell phone users do not
publish their phone numbers today.
The users do not need to manually exchange their SIP URIs and home
addresses which are too long (an IPv6 address is 16 bytes long and random
looking, a SIP URI can be very long e.g. up to 30 characters and even more
with a random part for privacy).
The protocol also works in the absence of user contact, for example when
the target user's SIP URI is lost (loss of state, new phone), or this is
the user's first phone, and hence his/her contact list is initially empty.
Thousands of cell phones are sold everyday..
[1] Peterson, J., "A Privacy Mechanism for the Session Initiation Protocol",
RFC3323, November 2002.
=======================
Interested folks could you please subscribe to the mailing list created
for this discussion:
https://www1.ietf.org/mailman/listinfo/humanresolvers
We already had some discussions on the IETF list recently.
You may want to take a look at the archives for an introduction:
http://www1.ietf.org/mail-archive/web/ietf/current/msg48129.html
There is also a side discussion on CAPTCHAs:
http://www1.ietf.org/mail-archive/web/ietf/current/msg48172.html
_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext