Re: [apps-discuss] request to register 'describes' link relation (http://tools.ietf.org/html/draft-wilde-describes-link-01)

Barry Leiba <barryleiba@computer.org> Tue, 09 October 2012 23:40 UTC

Return-Path: <barryleiba.mailing.lists@gmail.com>
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 EBA1711E80ED; Tue, 9 Oct 2012 16:40:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.089
X-Spam-Level:
X-Spam-Status: No, score=-103.089 tagged_above=-999 required=5 tests=[AWL=-0.112, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 eFnF2QtKwSCr; Tue, 9 Oct 2012 16:40:07 -0700 (PDT)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 63E0411E80E8; Tue, 9 Oct 2012 16:40:06 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id b11so3812835lam.31 for <multiple recipients>; Tue, 09 Oct 2012 16:40:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=EF1XM0TRpEluUNn53Sh4nApCMLOPuLgNUxdAzClnRRo=; b=ZxlIJ9RhI5AFr60+0yzH/7JjyfoRVoWcIvFcHUb1F1GCsGYKbLtAbZGvsbljC3LWBe JoZEfxpGH/ssIfIw8gbDQUDJ6xQu87OPCiywlK6qWkklsc01oAIDHYxDndpIJGWRo1jW W7rzsk8E5ttXk8csi7AhAIiH9gLMRtuToN/uXt1bDQaJEQsuHK5KxIEwWs/cEhscSet5 l517hQDJVyIuXl0WZ6BO2E2cJQc1GgJcMWW9PyGhz46AkMykY9khnrAxTS7LoRIQAZDZ EtfuF1jZpHfzlZ5Nwrav4dMon2+IoGkjS2lQLYzW9Eqp6g/vPJ5654sveF3eVmcXWtmW jCSA==
MIME-Version: 1.0
Received: by 10.112.103.7 with SMTP id fs7mr3469251lbb.25.1349826005265; Tue, 09 Oct 2012 16:40:05 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.150.194 with HTTP; Tue, 9 Oct 2012 16:40:05 -0700 (PDT)
In-Reply-To: <507486FE.2050601@berkeley.edu>
References: <507486FE.2050601@berkeley.edu>
Date: Tue, 09 Oct 2012 19:40:05 -0400
X-Google-Sender-Auth: gkZKcscjYRmdeA7xIP0K29h7NRY
Message-ID: <CAC4RtVB=J3R=wpwUOP_NVRpNGRtT8KfhuXyz-hNk4-4U1-UJAQ@mail.gmail.com>
Subject: Re: [apps-discuss] request to register 'describes' link relation (http://tools.ietf.org/html/draft-wilde-describes-link-01)
From: Barry Leiba <barryleiba@computer.org>
To: Erik Wilde <dret@berkeley.edu>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: apps-discuss@ietf.org, 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: Tue, 09 Oct 2012 23:40:10 -0000

[I'm removing the non-IETF groups from the distribution list.]

> this is a request to register 'describes' in the IANA link relations
> registry established by RFC 5988. the latest draft of the registration
> document is available at
> http://tools.ietf.org/html/draft-wilde-describes-link-01, and the last
> version announced on a variety of mailing lists has not generated any
> feedback asking for changes.

I'll let the folks on the link-relations list respond to the
suitability of the specification for documenting a useful link
relation.  I have just a couple of process points:

1. In order for the registration to be done, this document will have
to be published somewhere that will satisfy the Designated Expert as
being a stable reference.  That probably means that you'll want this
to be an RFC, so you need to be sorting out how that will happen.
Happily, I'm willing to sponsor this as an AD-sponsored individual
submission, if the link-relations folks agree that we should register
this.

2. I don't think this should be Standards Track, though (and it
doesn't need to be in order to register the link relation and to be
the reference documentation for it).  I would prefer that you make it
Informational, change the "SHOULD" to "should" in the Security
Considerations, and remove Section 2 and the normative reference to
RFC 2119.  (This can wait until after the feedback from the
link-relations mailing list.)

Barry, Applications AD