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

Eran Hammer-Lahav <eran@hueniverse.com> Thu, 21 April 2011 06:44 UTC

Return-Path: <eran@hueniverse.com>
X-Original-To: link-relations@ietfc.amsl.com
Delivered-To: link-relations@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 1FCA7E06E7 for <link-relations@ietfc.amsl.com>; Wed, 20 Apr 2011 23:44:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VoCavG1tr8mj for <link-relations@ietfc.amsl.com>; Wed, 20 Apr 2011 23:44:35 -0700 (PDT)
Received: from p3plex1out02.prod.phx3.secureserver.net (p3plex1out02.prod.phx3.secureserver.net [72.167.180.18]) by ietfc.amsl.com (Postfix) with SMTP id 2DFD1E069C for <link-relations@ietf.org>; Wed, 20 Apr 2011 23:44:35 -0700 (PDT)
Received: (qmail 29577 invoked from network); 21 Apr 2011 06:44:33 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.19) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 21 Apr 2011 06:44:32 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.19]) by P3PW5EX1HT001.EX1.SECURESERVER.NET ([72.167.180.19]) with mapi; Wed, 20 Apr 2011 23:44:32 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Mark Nottingham <mnot@mnot.net>, Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 20 Apr 2011 23:44:25 -0700
Thread-Topic: [link-relations] NEW RELATION REQUEST - pingback
Thread-Index: Acv/7KCWtb2Ew0P9RcyHskMvh+EEHwAAt8tw
Message-ID: <90C41DD21FB7C64BB94121FBBC2E723447535BBB67@P3PW5EX1MB01.EX1.SECURESERVER.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> <4D9E0844.50808@gmx.de> <4B908F60-1368-4C34-82D8-B74F8B0211E5@mnot.net>
In-Reply-To: <4B908F60-1368-4C34-82D8-B74F8B0211E5@mnot.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Ian Hickson <ian@hixie.ch>, "link-relations@ietf.org" <link-relations@ietf.org>
Subject: Re: [link-relations] NEW RELATION REQUEST - pingback
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: Thu, 21 Apr 2011 06:44:36 -0000

Makes sense to me.

As an aside, would an expired I-D work as an alternative copy?

EHL

> -----Original Message-----
> From: link-relations-bounces@ietf.org [mailto:link-relations-
> bounces@ietf.org] On Behalf Of Mark Nottingham
> Sent: Wednesday, April 20, 2011 11:23 PM
> To: Julian Reschke
> Cc: Ian Hickson; link-relations@ietf.org
> Subject: Re: [link-relations] NEW RELATION REQUEST - pingback
> 
> There's some discussion currently going on about making updating the
> registries easier, with simplified procedures for corrections, updates, etc.
> 
> If/when that happens, I'm thinking that a reference to Ian's site (or similar)
> isn't problematic, as the main problem -- that it may become unavailable if
> something happens to Ian -- isn't such an issue.
> 
> Make sense?
> 
> Cheers,
> 
> 
> On 08/04/2011, at 4:53 AM, Julian Reschke wrote:
> 
> > On 11.08.2010 05:35, Mark Nottingham wrote:
> >> ...
> >> If you meet the "RFC or Open Standard" test, it's possible to register it.
> >>
> >> Note that publishing on the independent submission Informational RFC
> track isn't really "through the IETF process" -- it's at the discretion of the RFC
> Editor, which is a separate entity. See:
> >>   http://www.rfc-editor.org/indsubs.html
> >>   http://tools.ietf.org/html/rfc4846
> >>   http://tools.ietf.org/html/rfc5742
> >>
> >> While I can't say that it's necessarily a quick process, the amount of work
> involved (beyond draft formatting) is relatively low, and there are a few
> upsides, including:
> >>
> >> 1) RFCs are institutionally guaranteed not to change over time; you say
> that the spec is frozen, but there aren't checks or balances, nor conventions
> in place, to prevent future changes.
> >> 2) When you die and your Web site disappears, an RFC will have a better
> chance of persisting in an unambiguous state.
> >> ...
> >
> > Assuming we are ok with the content, but not with the *location* of the
> spec, there may be an easy way to fix this.
> >
> > For instance,
> >
> > - use
> <http://replay.waybackmachine.org/20090228033516/http://hixie.ch/specs/
> pingback/pingback> as reference, or
> >
> > - have Ian send the spec as attachment to the www-archive mailing list, and
> then link to the attachment in the mail archive.
> >
> > Best regards, Julian
> 
> --
> Mark Nottingham   http://www.mnot.net/
> 
> 
> 
> _______________________________________________
> link-relations mailing list
> link-relations@ietf.org
> https://www.ietf.org/mailman/listinfo/link-relations