[webfinger] Registration of a URN for WebFinger Properties

"Paul E. Jones" <paulej@packetizer.com> Sat, 05 October 2013 01:23 UTC

Return-Path: <paulej@packetizer.com>
X-Original-To: webfinger@ietfa.amsl.com
Delivered-To: webfinger@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8469521F9CAF for <webfinger@ietfa.amsl.com>; Fri, 4 Oct 2013 18:23:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.298
X-Spam-Level:
X-Spam-Status: No, score=-1.298 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, HTML_MESSAGE=0.001]
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 cygXJb9VRaBw for <webfinger@ietfa.amsl.com>; Fri, 4 Oct 2013 18:22:55 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id E2BBF21F9D9A for <webfinger@ietf.org>; Fri, 4 Oct 2013 18:22:51 -0700 (PDT)
Received: from [192.168.1.20] (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r951Morp028436 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <webfinger@ietf.org>; Fri, 4 Oct 2013 21:22:50 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1380936170; bh=IJ8Z5wfKuxR9evP/ZeLvByDw1pXThT+XCjFC+ulQw4o=; h=From:To:Subject:Date:Content-Type:Message-Id:Mime-Version: Reply-To; b=GKOBcKeVE3iuFvRwGvzTBnVjKH81OrxBVVmEuKe3g7j84VkG6S0jCD0iSlddlT9qC bMEgjS1LKqi2UXICeCzOozZ7kkVEvdbUuM7qZD1jSdHNAQ9t7b/dtgTxiUk5W3Ot6F Ukq80m4rur1tyF+8UWFxa4QrWLvVuWpsw+5EL7Io=
From: "Paul E. Jones" <paulej@packetizer.com>
To: webfinger@ietf.org
Date: Sat, 05 Oct 2013 01:22:59 +0000
Content-Type: multipart/alternative; boundary="------=_MB1768D863-ADA9-4A7F-9184-9ABD63556EC2"
Message-Id: <em8fca55dc-a3ff-4231-8218-6c2221838850@sydney>
Mime-Version: 1.0
User-Agent: eM_Client/5.0.18661.0
Subject: [webfinger] Registration of a URN for WebFinger Properties
X-BeenThere: webfinger@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "Paul E. Jones" <paulej@packetizer.com>
List-Id: Discussion of the Webfinger protocol proposal in the Applications Area <webfinger.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webfinger>, <mailto:webfinger-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/webfinger>
List-Post: <mailto:webfinger@ietf.org>
List-Help: <mailto:webfinger-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webfinger>, <mailto:webfinger-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Oct 2013 01:23:00 -0000

Folks,

As you know, properties (both link and subject-specific properties) are 
identified via a URI.  For applications that are defined outside the 
IETF, those organizations are able to define any URI they wish to use.  
For any we might define within the IETF, however, we need something.

In anticipation of having such a need, I think we should create a 
document along the lines of RFC 6755 for WebFinger.  Specifically, we 
would define a URN sub-namespace as:

    urn:ietf:params:webfinger

One such potentially-useful subject-specific properties are "name", 
which would be the the subject's name intended for human consumption.  
If you've queried my WebFinger server, you would know I currently 
advertise my name in English and Chinese.  For the "default" name, the 
URN might be:

    urn:ietf:params:webfinger:name

For language-specific variants, it might be:

    urn:ietf:params:webfinger:name:zh-CN

Defining the various properties and their meaning is an exercise for 
another day, but I hope you see the value in defining the URN 
sub-namespace.

Thoughts?

Paul