Re: Request to publish draft-wmills-oauth-lrdd-06.txt

Julian Reschke <julian.reschke@gmx.de> Wed, 31 October 2012 09:43 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: link-relations@ietfa.amsl.com
Delivered-To: link-relations@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E666A21F845F for <link-relations@ietfa.amsl.com>; Wed, 31 Oct 2012 02:43:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.519
X-Spam-Level:
X-Spam-Status: No, score=-103.519 tagged_above=-999 required=5 tests=[AWL=-0.920, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lsg103SqVajp for <link-relations@ietfa.amsl.com>; Wed, 31 Oct 2012 02:43:25 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id DD6F821F845E for <link-relations@ietf.org>; Wed, 31 Oct 2012 02:43:24 -0700 (PDT)
Received: (qmail invoked by alias); 31 Oct 2012 09:43:23 -0000
Received: from p5DD9651D.dip.t-dialin.net (EHLO [192.168.178.36]) [93.217.101.29] by mail.gmx.net (mp033) with SMTP; 31 Oct 2012 10:43:23 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18QqeZ0FhoQFfahcELwCi3WMdQ6Mw3rJdpJB5EdQJ TCt9f8C0XbHamj
Message-ID: <5090F2B9.6070507@gmx.de>
Date: Wed, 31 Oct 2012 10:43:21 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Nevil Brownlee <rfc-ise@rfc-editor.org>
Subject: Re: Request to publish draft-wmills-oauth-lrdd-06.txt
References: <508F17A7.3060105@rfc-editor.org>
In-Reply-To: <508F17A7.3060105@rfc-editor.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: link-relations@ietf.org
X-BeenThere: link-relations@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <link-relations.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/link-relations>, <mailto:link-relations-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/link-relations>
List-Post: <mailto:link-relations@ietf.org>
List-Help: <mailto:link-relations-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/link-relations>, <mailto:link-relations-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Oct 2012 09:43:26 -0000

On 2012-10-30 00:56, Nevil Brownlee wrote:
>
> Hi Link Relations folk:
>
> William Mills has sent me this draft as an Independent Submission.
>
> The draft asks IANA to register link relations, so I'd like approval
> from the designated experts to proceed; would one of those experts
> please take a look at the draft for me?
>
> Please note that I'm asking this now instead of looking for a full
> review.  IANA will - of course - ask the designated experts about it
> when the draft reaches the RFC Editor queue
>
> Cheers, Nevil

I have looked at the draft and have two editorial remarks:

- the sections defining the link relation type should actually mention 
the name of the link relation being defined (minimally in the title)

- also, they should more precisely link to the part of the spec where 
the actual definition is defined; right now it involves a bit of 
guessing / full-text search which shouldn't be required from the reader

To actually understand what the link relations mean I'd have to 
understand OAuth which I do not. However I note that the link relations 
are prefixed "oauth" so I don't have a problem with these relation names 
being registered.

Best regards, Julian