[Uri-review] URI ACR extension

<sune.jakobsson@telenor.com> Fri, 02 March 2012 13:05 UTC

Return-Path: <sune.jakobsson@telenor.com>
X-Original-To: uri-review@ietfa.amsl.com
Delivered-To: uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 836D021F89E0 for <uri-review@ietfa.amsl.com>; Fri, 2 Mar 2012 05:05:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.288
X-Spam-Level:
X-Spam-Status: No, score=-2.288 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6HhV5RjC9lmp for <uri-review@ietfa.amsl.com>; Fri, 2 Mar 2012 05:05:33 -0800 (PST)
Received: from sv05.e.nsc.no (vip1scan.telenor.net [148.123.15.75]) by ietfa.amsl.com (Postfix) with ESMTP id 0309021F898E for <uri-review@ietf.org>; Fri, 2 Mar 2012 05:05:32 -0800 (PST)
Received: from tns-fbu-22-249.corp.telenor.no ([134.47.162.189] [134.47.162.189]) by sv05.nsc.no with ESMTPS id BT-MMP-1465268; Fri, 2 Mar 2012 14:05:30 +0100
Received: from TNS-FBU-2E-017.corp.telenor.no ([134.47.163.220]) by tns-fbu-22-249.corp.telenor.no ([134.47.162.189]) with mapi; Fri, 2 Mar 2012 14:05:29 +0100
From: <sune.jakobsson@telenor.com>
To: <uri-review@ietf.org>
Date: Fri, 2 Mar 2012 14:05:28 +0100
Thread-Topic: URI ACR extension
Thread-Index: Acz4dSPqaJdrhcZgR0+lSXJsy6szXQ==
Message-ID: <95638AF073FFD4458AC74F05216E245501EC87CCD3@TNS-FBU-2E-017.corp.telenor.no>
Accept-Language: en-US, nb-NO
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, nb-NO
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Kevin.Smith@vodafone.com
Subject: [Uri-review] URI ACR extension
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/uri-review>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 13:05:33 -0000

Dear all.

I would like to bring your attention the http://tools.ietf.org/html/draft-uri-acr-extension-04 submission.

Technical summary:

   This URI scheme is intended as an extension to the "tel:"
   scheme but without disclosing the true identity of a reference or a
   user.  The "acr" URI describes an anonymous reference, that can be
   mapped to a resource or a user.  There are multiple situations where
   the true identity of a user or a resources can not be disclosed.  The
   "acr" URI is a globally unique identifier ( "name" ) only; it does
   not describe the steps necessary to reach the user or the device.
   However it can contain a parameter indication what body or
   organisation that could resolve it.  It is intended for privacy
   protection, where a user trusts a translating party, that can route
   or forward the request or message to the true user or resource.

This is an individual contribution, so I need help to bring this to a working group, and hopefully convert it to a permanent RFC in time.

Open Mobile Alliance is using this on multiple network enablers, to allow anonymous access to API's

Any advice would be helpful. :)


BR Sune Jakobsson