[humanresolv] Abstract humanresolvers idea

"Pars Mutaf" <pars.mutaf@gmail.com> Fri, 26 December 2008 18:11 UTC

Return-Path: <humanresolvers-bounces@ietf.org>
X-Original-To: humanresolvers-archive@optimus.ietf.org
Delivered-To: ietfarch-humanresolvers-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D1BAE3A694F; Fri, 26 Dec 2008 10:11:11 -0800 (PST)
X-Original-To: humanresolvers@core3.amsl.com
Delivered-To: humanresolvers@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B36763A67B3 for <humanresolvers@core3.amsl.com>; Fri, 26 Dec 2008 10:11:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Level:
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L5hM8JlMfhlP for <humanresolvers@core3.amsl.com>; Fri, 26 Dec 2008 10:11:10 -0800 (PST)
Received: from mail-bw0-f21.google.com (mail-bw0-f21.google.com [209.85.218.21]) by core3.amsl.com (Postfix) with ESMTP id 77D223A694F for <humanresolvers@ietf.org>; Fri, 26 Dec 2008 10:11:09 -0800 (PST)
Received: by bwz14 with SMTP id 14so13984008bwz.13 for <humanresolvers@ietf.org>; Fri, 26 Dec 2008 10:10:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=p09XGsgvtxkdxwgroy2zOOungCYxpWJiV4mjysbTXJs=; b=TyLlzd1AaYtsythAO7pP8KoD5+LsuOv5i+4ur3FtHRK9kvGIpgCETD6GKlKvnvC1z9 5dIh9HA+fLaktIN4dZK72yT0VREtbuSEzuVRipC6ybu2t26XWxilSfjdBJVv/N79geS8 baf2qL8H6moaflJz1u8NNZh15KGrvypaQCJig=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=FkjevoDzNBVZ9+PoBM8WfuvKYFWa5cwBvxaY7L9czYmaVYtoiFrW1G1kfdC1K34wp1 GHGHqXkzp40uVczYlhrU5ZjJxUuaPuDnvL60wtO1DN+HfRgP44GwLyi8VEOPnEhpkxpi 4W5YVr+os4+EtGu1Pwyi7EDxH/I7JhNwhwWvo=
Received: by 10.181.221.7 with SMTP id y7mr3108760bkq.195.1230315057450; Fri, 26 Dec 2008 10:10:57 -0800 (PST)
Received: by 10.180.254.4 with HTTP; Fri, 26 Dec 2008 10:10:57 -0800 (PST)
Message-ID: <18a603a60812261010p3f1256d8scd266555e5620704@mail.gmail.com>
Date: Fri, 26 Dec 2008 20:10:57 +0200
From: "Pars Mutaf" <pars.mutaf@gmail.com>
To: humanresolvers@ietf.org
MIME-Version: 1.0
Content-Disposition: inline
Subject: [humanresolv] Abstract humanresolvers idea
X-BeenThere: humanresolvers@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <humanresolvers.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/humanresolvers>, <mailto:humanresolvers-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/humanresolvers>
List-Post: <mailto:humanresolvers@ietf.org>
List-Help: <mailto:humanresolvers-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/humanresolvers>, <mailto:humanresolvers-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: humanresolvers-bounces@ietf.org
Errors-To: humanresolvers-bounces@ietf.org

Dear members of the humanresolvers mailing list,

The humanresolvers mailing list is still making its very first step,
waiting for
responses from the mailing list members. Below is probably the simplest
abstract description  (i.e. not entering any solution space) that is open to
discussion. Comments are welcome! If you have subscribed with some
other vision in mind, please do not hesitate to share it.


Reaching a target cell phone based on target user's consent
===========================================

Target cell phone user publishes an identifier. Using this identifier
the initiator user requests access to the target cell phone and its
resources. For example, a SIP URI for opening a SIP session, or HTTP
access to the target cell phone can be requested (for example,
for browsing some photos taken by the target cell phone).

The target user approves or denies the request.

Note:

One way to achieve this is e-mail. The target user can publish an
e-mail address. The initiator user can request a SIP URI or HTTP URL
from the target user via e-mail. This would be a bad approach for two
reasons:

    1) The published e-mail address allows direct access to the
       target user, and hence can be used for spamming.

    2) The above solution may also be used for requesting e-mail
       address from the target user.



Regards,
pars
_______________________________________________
humanresolvers mailing list
humanresolvers@ietf.org
https://www.ietf.org/mailman/listinfo/humanresolvers