IETF Logo Mail Archive

Re: [Http-well-known] Do we really want to define free

Alexey Melnikov <aamelnikov@fastmail.fm> Mon, 14 May 2018 13:31 UTC

Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: http-well-known@ietfa.amsl.com
Delivered-To: http-well-known@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E05D212E6A3 for <http-well-known@ietfa.amsl.com>; Mon, 14 May 2018 06:31:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=WHuzqdnP; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=lbjM63xs
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 cT_B4HdjIUXL for <http-well-known@ietfa.amsl.com>; Mon, 14 May 2018 06:31:17 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 736261270A7 for <http-well-known@ietf.org>; Mon, 14 May 2018 06:31:17 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 7516821C05 for <http-well-known@ietf.org>; Mon, 14 May 2018 09:31:16 -0400 (EDT)
Received: from web5 ([10.202.2.215]) by compute7.internal (MEProxy); Mon, 14 May 2018 09:31:16 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=JXNHsDWjW+SfdVlpZ4eJYgIDku07z QN5KWD5s5K/7ec=; b=WHuzqdnPVbbj9RoB8HVWSl5aUShNUhWxz1kpXFdSSbUrE Io4FvRoY3/mFjbD+E+zWwXC8+Xv8z3ZO0bpfIr7MShBsNthkp0zZFGbFj1TRt6iK usCha/sKjImj947pqzH8IF/O4aV5JQqOZ5S8Cz/3zM1uBnmHicPfC3ICLz1oVeNb bJRuwfncI6yIGbBUjtI/D4jqLJvsuR785NdvjcFqvtIRW7pjV40FJebZwx6CQlKZ 6aK4D/tS0Hs+cQw+j9QDV5wHoBwytfhMGHplc4NnMBOSUpw+9+UIU8QlHsEQ0a/m Cqjh8kA7c9A7FEDDY3QpYLQ/3XC7QeENH39RIehYw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=JXNHsD WjW+SfdVlpZ4eJYgIDku07zQN5KWD5s5K/7ec=; b=lbjM63xsN2tFRMMfUwPF/C im9j0y9pq5sNvCz1eAZJgvCjQmAapoaDUsAT5lgjS1YZmc24GmlqnfoRK0Uy0PHC J40v5rQFpKWJSwAo70GBXeIOX8O+q/lvby6P8intR5gPygqNzDLK1EdDrp+4Sige Anvibq+/RxjzqJxfbW7C4E6hHWRhvl+BgGLkOew8yDvuf+5ztbCgoy0xtZNUHrgw OIqQO/6mcfeO5sMJOmA5DGyUidgG1FpltVseOQ8rovjZ+BAIq0d/Uv5xljx+q4wC wgXxQodbarmT1pSbTCW+7KQ3dby6bbKaEecG9H97o+rF9/wQqCLhmpZt5UNtcr9w ==
X-ME-Sender: <xms:pI_5WthiBvC4bdbj374v7RA3Pq4iBMrCh1Pi5UUrwI5cQf-0mXfYQA>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id 544699E0DF; Mon, 14 May 2018 09:31:16 -0400 (EDT)
Message-Id: <1526304676.33982.1371365080.2EF6FE42@webmail.messagingengine.com>
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: http-well-known@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-29fe4c42
References: <272B547C-35B1-46C0-90A2-D6167C346115@mnot.net> <CF93893F-E0CB-41D4-ACED-FB9A050B9CEF@iii.ca>
Date: Mon, 14 May 2018 14:31:16 +0100
In-Reply-To: <CF93893F-E0CB-41D4-ACED-FB9A050B9CEF@iii.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/http-well-known/8TXzCEnJmJg6CMeTSCq-2G37MxU>
Subject: Re: [Http-well-known] Do we really want to define free
X-BeenThere: http-well-known@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussion of HTTP Well-Known URIs <http-well-known.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/http-well-known>, <mailto:http-well-known-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/http-well-known/>
List-Post: <mailto:http-well-known@ietf.org>
List-Help: <mailto:http-well-known-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-well-known>, <mailto:http-well-known-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 May 2018 13:31:19 -0000

Hi Cullen,

On Mon, May 14, 2018, at 2:12 PM, Cullen Jennings wrote:
> 
> Thank you for making progress on this draft. 
> 
> One question I had related to the text that says 
> 
> “Registrations MUST reference a freely available, stable specification.”
> 
> In other documents, people have argued for that but that means that 3GPP 
> (and others) would not be able to use the mechanism which seems bad. 

This is a good point. In general Desinated Experts need to be able to get access to specifications for free, but this is not the same as making them freely available.

> In the name of broad use and getting done, I would prefer to just use 
> "Specification Required" from RFC 5226. 
> 
> But if we don’t do that, we better specify what we mean by “free” in 
> this context. 

Best Regards,
Alexey

v2.23.0 | Report a Bug | By Email