Re: [link-relations] NEW RELATION REQUEST - pingback

Mark Nottingham <mnot@mnot.net> Fri, 13 August 2010 10:05 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: link-relations@core3.amsl.com
Delivered-To: link-relations@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B5E513A69B6 for <link-relations@core3.amsl.com>; Fri, 13 Aug 2010 03:05:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.322
X-Spam-Level:
X-Spam-Status: No, score=-105.322 tagged_above=-999 required=5 tests=[AWL=-2.723, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 6Z4yHeIIvcK7 for <link-relations@core3.amsl.com>; Fri, 13 Aug 2010 03:05:23 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id B0F9D3A69A3 for <link-relations@ietf.org>; Fri, 13 Aug 2010 03:05:23 -0700 (PDT)
Received: from chancetrain-lm.mnot.net (unknown [118.209.248.41]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 62DEF509B4; Fri, 13 Aug 2010 06:05:50 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4C651723.6030507@gmx.de>
Date: Fri, 13 Aug 2010 20:05:50 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <64530CA6-9BF1-42A9-89D9-2F39484CA81B@mnot.net>
References: <Pine.LNX.4.64.1008102113040.11992@ps20323.dreamhostps.com> <69D54950-1FE2-4714-9FED-569142BBF1A4@mnot.net> <Pine.LNX.4.64.1008110320320.11977@ps20323.dreamhostps.com> <B287E435-5C63-448B-ACD9-E3319FCDBF14@mnot.net> <Pine.LNX.4.64.1008110344060.22155@ps20323.dreamhostps.com> <4C651723.6030507@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.1081)
Cc: Ian Hickson <ian@hixie.ch>, link-relations@ietf.org
Subject: Re: [link-relations] NEW RELATION REQUEST - pingback
X-BeenThere: link-relations@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <link-relations.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 13 Aug 2010 10:05:24 -0000

I don't think so. The requirement in "Specification Required" is for the specification to be both "in sufficient detail so that interoperability between independent implementations is possible" and "permanent and readily available":

>       Specification Required - Values and their meanings must be
>             documented in a permanent and readily available public
>             specification, in sufficient detail so that interoperability
>             between independent implementations is possible[...]  
>             The intention behind
>             "permanent and readily available" is that a document can
>             reasonably be expected to be findable and retrievable long
>             after IANA assignment of the requested value.  Publication
>             of an RFC is an ideal means of achieving this requirement,
>             but Specification Required is intended to also cover the
>             case of a document published outside of the RFC path.  For
>             RFC publication, the normal RFC review process is expected
>             to provide the necessary review for interoperability, though
>             the Designated Expert may be a particularly well-qualified
>             person to perform such a review.

Ian, I understand that your argument is that even publishing it on your Web site makes it "permanent and readily available," since it is archived, copied by others, indexed by Google, etc. While that's good enough for your purposes, historically the IETF / RFC Editor have been reluctant to use URIs at all, much less URIs to personal Web sites to define protocols.

I notice that your document is in the W3C format -- have you considered sending it to them as a Member submission? Alternatively, I'd suggest reformatting as an Internet-Draft and submitting that.

Regards,


On 13/08/2010, at 7:57 PM, Julian Reschke wrote:

> Maybe there's middle ground:
> 
> - have short RFC that defines the link relation in general
> 
> - have that document reference the "old" spec for the description of a specific pingback service implementation.
> 
> Best regards, Julian


--
Mark Nottingham     http://www.mnot.net/