[Uri-review] URI ACR extension

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

From: sune.jakobsson@telenor.com
To: uri-review@ietf.org
Date: Fri, 02 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
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
Precedence: list

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

[Uri-review] URI ACR extension sune.jakobsson