IETF Logo Mail Archive

adding "pingback"

Erik Wilde <erik.wilde@dret.net> Wed, 25 November 2015 16:11 UTC

Return-Path: <erik.wilde@dret.net>
X-Original-To: link-relations@ietfa.amsl.com
Delivered-To: link-relations@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50DC91B2E3C for <link-relations@ietfa.amsl.com>; Wed, 25 Nov 2015 08:11:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h0mxxQqZGqBz for <link-relations@ietfa.amsl.com>; Wed, 25 Nov 2015 08:11:36 -0800 (PST)
Received: from cm03fe.ist.berkeley.edu (cm03fe.ist.berkeley.edu [169.229.218.144]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82A1B1B3023 for <link-relations@ietf.org>; Wed, 25 Nov 2015 08:11:32 -0800 (PST)
Received: from 46-126-159-4.dynamic.hispeed.ch ([46.126.159.4] helo=dretair11.local) by cm03fe.ist.berkeley.edu with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.76) (auth plain:dret@berkeley.edu) (envelope-from <erik.wilde@dret.net>) id 1a1cfG-0001pz-CC for link-relations@ietf.org; Wed, 25 Nov 2015 08:11:32 -0800
To: link-relations <link-relations@ietf.org>
From: Erik Wilde <erik.wilde@dret.net>
Subject: adding "pingback"
Message-ID: <5655DDAA.3020907@dret.net>
Date: Wed, 25 Nov 2015 17:11:22 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/link-relations/E5dKYmHnjtUGSROGKKCtkw27dcc>
X-Mailman-Approved-At: Wed, 25 Nov 2015 12:28:55 -0800
X-BeenThere: link-relations@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Nov 2015 16:11:37 -0000

hello.

http://www.hixie.ch/specs/pingback/pingback defines a "pingback" 
relation that seems to have some adoption. the spec itself does not 
contain an IANA registration. however, since it is a relation that is in 
use, maybe it would make sense to add it to the IANA link relation type 
registry?

what is the process to add a link relation where the spec does not 
contain an IANA registration, but implementation and adoption suggest 
that including the value in the registry would be helpful for people 
encountering this relation on the web?

thanks and kind regards,

dret.

-- 
erik wilde | mailto:erik.wilde@dret.net |
            | http://dret.net/netdret    |
            | http://twitter.com/dret    |

v2.23.0 | Report a Bug | By Email