From nobody Wed Nov 25 12:28:57 2015 Return-Path: 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 ; 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 ; 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 ; 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 ) id 1a1cfG-0001pz-CC for link-relations@ietf.org; Wed, 25 Nov 2015 08:11:32 -0800 To: link-relations From: Erik Wilde 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: 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 | From nobody Wed Nov 25 18:52:08 2015 Return-Path: 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 A6CE31A9071 for ; Wed, 25 Nov 2015 18:52:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.602 X-Spam-Level: X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 PcJnr_GpP-Xd for ; Wed, 25 Nov 2015 18:52:04 -0800 (PST) Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AC521A906F for ; Wed, 25 Nov 2015 18:52:04 -0800 (PST) Received: from [192.168.1.101] (unknown [120.149.194.112]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 1916022E25F; Wed, 25 Nov 2015 21:52:01 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: adding "pingback" From: Mark Nottingham In-Reply-To: <5655DDAA.3020907@dret.net> Date: Thu, 26 Nov 2015 13:51:59 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: <90D32228-FD8C-4729-BA3C-B992093B4FDE@mnot.net> References: <5655DDAA.3020907@dret.net> To: Erik Wilde , ian@hixie.ch X-Mailer: Apple Mail (2.2104) Archived-At: Cc: link-relations X-BeenThere: link-relations@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Nov 2015 02:52:06 -0000 No drama, we can add it. Ian, does this look right to you? Relation Name: pingback Description: Gives the address of the pingback resource for the link = context Reference: http://www.hixie.ch/specs/pingback/pingback Notes: Application Data: > On 26 Nov 2015, at 3:11 am, Erik Wilde wrote: >=20 > hello. >=20 > 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? >=20 > 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? >=20 > thanks and kind regards, >=20 > dret. >=20 > --=20 > erik wilde | mailto:erik.wilde@dret.net | > | http://dret.net/netdret | > | http://twitter.com/dret | >=20 > _______________________________________________ > link-relations mailing list > link-relations@ietf.org > https://www.ietf.org/mailman/listinfo/link-relations -- Mark Nottingham https://www.mnot.net/ From nobody Wed Nov 25 19:09:57 2015 Return-Path: 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 99B331A90D0 for ; Wed, 25 Nov 2015 19:09:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.977 X-Spam-Level: X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 E9Y_y383sioA for ; Wed, 25 Nov 2015 19:09:54 -0800 (PST) Received: from mail-io0-f181.google.com (mail-io0-f181.google.com [209.85.223.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C8201A90CE for ; Wed, 25 Nov 2015 19:09:54 -0800 (PST) Received: by iofh3 with SMTP id h3so72590085iof.3 for ; Wed, 25 Nov 2015 19:09:53 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=QSAChSebgwtGdG+WcoTex3ZDq6/w4qgNBd5oHiGHykY=; b=lhxCT3XZFV3Zb2Bb5/Cmbz+0m2wfY01uuGq6ZgTiAdfFOvR3wiMjoP+942wRtZN1Oy YH9gYx8OYm1gdpnEdm8GffseTpfOHGqBFgiPNLIiIPbfom3GtcNB8Tkww4077JdTe43s bqdy3v3VbrzMOnea7e3oeVCW5KSvGjf8bWIGuX5XgiraHdwlEcV4cU7aNF7JRKs+nIOB XiBiQVMrgMw+zAhG5ArKW6q49m8RBodD6+jbwD5crE9ERmPlrdT2BOBkApyhGzrHxPRr L654k+Ouliroi7wdq/JZeSlHd7x50F2CM5nVNP1s9xlDT3TarirMXwD0JW2hdK4FvRQx BpPA== X-Received: by 10.107.17.13 with SMTP id z13mr45576327ioi.97.1448507393641; Wed, 25 Nov 2015 19:09:53 -0800 (PST) MIME-Version: 1.0 References: <5655DDAA.3020907@dret.net> <90D32228-FD8C-4729-BA3C-B992093B4FDE@mnot.net> In-Reply-To: <90D32228-FD8C-4729-BA3C-B992093B4FDE@mnot.net> From: Ian Hickson Date: Thu, 26 Nov 2015 03:09:43 +0000 Message-ID: Subject: Re: adding "pingback" To: Mark Nottingham , Erik Wilde Content-Type: multipart/alternative; boundary=001a113ecf32a714c8052568e847 Archived-At: Cc: link-relations X-BeenThere: link-relations@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Nov 2015 03:09:56 -0000 --001a113ecf32a714c8052568e847 Content-Type: text/plain; charset=UTF-8 Sure. On Wed, Nov 25, 2015 at 6:52 PM Mark Nottingham wrote: > No drama, we can add it. > > Ian, does this look right to you? > > Relation Name: pingback > Description: Gives the address of the pingback resource for the link > context > Reference: http://www.hixie.ch/specs/pingback/pingback > Notes: > Application Data: > > > > On 26 Nov 2015, at 3:11 am, Erik Wilde wrote: > > > > 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 | > > > > _______________________________________________ > > link-relations mailing list > > link-relations@ietf.org > > https://www.ietf.org/mailman/listinfo/link-relations > > -- > Mark Nottingham https://www.mnot.net/ > > --001a113ecf32a714c8052568e847 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Sure.

On Wed, Nov 25, 2015 at 6:52 PM Mark Nottingham <mnot@mnot.net> wrote:
No drama, we can add it.

Ian, does this look right to you?

Relation Name: pingback
Description: Gives the address of the pingback resource for the link contex= t
Reference: http://www.hixie.ch/specs/pingback/pingback
Notes:
Application Data:


> On 26 Nov 2015, at 3:11 am, Erik Wilde <erik.wilde@dret.net> wrote:
>
> hello.
>
> http://www.hixie.ch/specs/pingback/pingback defi= nes a "pingback" relation that seems to have some adoption. the s= pec itself does not contain an IANA registration. however, since it is a re= lation 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 con= tain an IANA registration, but implementation and adoption suggest that inc= luding the value in the registry would be helpful for people encountering t= his relation on the web?
>
> thanks and kind regards,
>
> dret.
>
> --
> erik wilde | mailto:erik.wilde@dret.net |
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| http://dret.net/netdret=C2= =A0 =C2=A0 |
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| http://twitter.com/dret=C2= =A0 =C2=A0 |
>
> _______________________________________________
> link-relations mailing list
> link-rela= tions@ietf.org
> https://www.ietf.org/mailman/listinfo/lin= k-relations

--
Mark Nottingham=C2=A0 =C2=A0https://www.mnot.net/

--001a113ecf32a714c8052568e847-- From nobody Wed Nov 25 19:36:51 2015 Return-Path: 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 D7FA31A9250 for ; Wed, 25 Nov 2015 19:36:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.602 X-Spam-Level: X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 08BJv-ESbr4A for ; Wed, 25 Nov 2015 19:36:48 -0800 (PST) Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56DE71A9251 for ; Wed, 25 Nov 2015 19:36:48 -0800 (PST) Received: from [192.168.1.101] (unknown [120.149.194.112]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 5FC5522E200; Wed, 25 Nov 2015 22:36:46 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: adding "pingback" From: Mark Nottingham In-Reply-To: Date: Thu, 26 Nov 2015 14:36:43 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <5655DDAA.3020907@dret.net> <90D32228-FD8C-4729-BA3C-B992093B4FDE@mnot.net> To: Ian Hickson X-Mailer: Apple Mail (2.2104) Archived-At: Cc: link-relations , Erik Wilde X-BeenThere: link-relations@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Nov 2015 03:36:50 -0000 IANA, please add the entry below to the Link Relations registry = . > On 26 Nov 2015, at 2:09 pm, Ian Hickson wrote: >=20 > Sure. >=20 > On Wed, Nov 25, 2015 at 6:52 PM Mark Nottingham wrote: > No drama, we can add it. >=20 > Ian, does this look right to you? >=20 > Relation Name: pingback > Description: Gives the address of the pingback resource for the link = context > Reference: http://www.hixie.ch/specs/pingback/pingback > Notes: > Application Data: >=20 >=20 > > On 26 Nov 2015, at 3:11 am, Erik Wilde wrote: > > > > 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 | > > > > _______________________________________________ > > link-relations mailing list > > link-relations@ietf.org > > https://www.ietf.org/mailman/listinfo/link-relations >=20 > -- > Mark Nottingham https://www.mnot.net/ >=20 -- Mark Nottingham https://www.mnot.net/