Re: [art] Call for Consensus: Re: On BCP 190
Larry Masinter <LMM@acm.org> Wed, 21 August 2019 14:50 UTC
Return-Path: <masinter@gmail.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C950912007C for <art@ietfa.amsl.com>; Wed, 21 Aug 2019 07:50:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level:
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 LPldnOfOaf3s for <art@ietfa.amsl.com>; Wed, 21 Aug 2019 07:50:22 -0700 (PDT)
Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) (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 7603412006B for <art@ietf.org>; Wed, 21 Aug 2019 07:50:22 -0700 (PDT)
Received: by mail-pl1-x62d.google.com with SMTP id t14so1444674plr.11 for <art@ietf.org>; Wed, 21 Aug 2019 07:50:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:content-language :thread-index; bh=/Ri8eYKILqRt6Ot0yQI5pmin6o3ZrILC1MevLvS6A3k=; b=d7aKhx9ZVg7rrT3kGTNOH8kZoRcS9OrU7WlnzYyA9vrcLirjW6S219iIcRv91laUJh Yid9UNCgM8Hh71WI+nPS2oI33VKZslmziW6rFEIIW4sYrvF3bqsizcG/E2UFWr2OuqJV zSRo+b24xXXBB9+rVN/3r+0QDFmmigY1NIhw3GyqrzBSp+riWiytUy3KDmXfD22YdZUL aIO3iplJ01Pa+D6hmu37/IgGyneOGCn1Asz6aQWZjqTVi/9Us/A+zp5uSgc2bI8k7YLX ee7I4dqrJN2uCmCQXikvJFBbBE5wl9db7RP7cgjANUlbJqVo7ZVVeDN5SWq02uB8vnYC 7zkQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:references:in-reply-to:subject :date:message-id:mime-version:content-transfer-encoding :content-language:thread-index; bh=/Ri8eYKILqRt6Ot0yQI5pmin6o3ZrILC1MevLvS6A3k=; b=AZMrN9A3X/dXy10flXR3zad8MTGkLvYo7Q3cnh/6bceQiFw5gfcSVq94GABOJn8jpg fQClqIb2+07ekpY25IZw5Dh57OCGQ90ldryiO3jj3C/J3/TOQzf7hJMMrZ7LIpGYkeB4 pRiqMoPXgIgDTEYM1FLfsFibGr2ls6HZPDMAMT6+HQH9NPN4E0s6GkbB5dOV8RSNpnJl k3IXBHKVSZJkHE26SYMl+a6gchN97trVlTy+a4HzG1Ku5s2HU6e9mVpGLsp1XZonj/KY nRRIA8lJKaOtR9jf9ywByfC4xDkTDaD/QhPIa7Hms2lgiylT9bLA0iYPK2QLy44bHhTF oDSg==
X-Gm-Message-State: APjAAAV0VyUkbPPeZoqLWWkdVRr51EC1sq/92gic4F0U2uLABIV/Fdw5 0aI6pkGvXH14bJ+0V7c0yLg=
X-Google-Smtp-Source: APXvYqxgraMxUyz50HIPVhNm9aw//mNqicHUvF6Qs4em2Qmejg9YI7bEBARYzSr7S+m0/9QEgeP/eg==
X-Received: by 2002:a17:902:461:: with SMTP id 88mr32398304ple.296.1566399021804; Wed, 21 Aug 2019 07:50:21 -0700 (PDT)
Received: from TVPC (c-67-169-101-78.hsd1.ca.comcast.net. [67.169.101.78]) by smtp.gmail.com with ESMTPSA id l31sm24345351pgm.63.2019.08.21.07.50.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Aug 2019 07:50:20 -0700 (PDT)
Sender: Larry Masinter <masinter@gmail.com>
From: Larry Masinter <LMM@acm.org>
X-Google-Original-From: "Larry Masinter" <lmm@acm.org>
To: 'Adam Roach' <adam@nostrum.com>, 'John C Klensin' <john-ietf@jck.com>, 'Mark Nottingham' <mnot@mnot.net>
Cc: 'Jacob Hoffman-Andrews' <jsha@letsencrypt.org>, 'Devon O'Brien' <devon.obrien@gmail.com>, 'ART Area' <art@ietf.org>
References: <58BF6171-03BB-4F83-940F-3A101EFDD67F@mnot.net> <CAN3x4Q=Jo1uBvfCG6CSrociYgdG+E4jq+4cB1txPjgboth2q9g@mail.gmail.com> <372FA049-7B33-4981-A0E0-41BD454CB770@mnot.net> <CAN3x4QmJsfx48MdhcBB+XWX+vfv=skSR2Z6kNPBWGVobvzNuFA@mail.gmail.com> <004601d5450d$62b33220$28199660$@acm.org> <CAN3x4Q=XR+=ugv6HEmOgsA6v64GkQ+4u-Hk+OBQ0Lp9jn-Cy=A@mail.gmail.com> <D154BA24-5027-4FAF-8779-CBA5533D24A1@mnot.net> <3000e948-14e6-80d2-e8e6-766d309c361c@nostrum.com> <ed64dc0e-5b71-63ec-cbac-85673c51109a@nostrum.com> <301DF34E4C5601BCA4D2BCBF@PSB> <A27BC0BC-B60A-44AD-B75B-859C71B0706A@mnot.net> <E02E5D4BA18EF0155B0EAE95@PSB> <80bb60b7-cdc7-0df8-6a33-726839b15dfe@nostrum.com> <C4BE71284D3C8DCA4F8F2187@PSB> <cecdb623-b6cd-ab60-12d2-b5030c0692b9@nostrum.com> <4FA97CBBC395799300730D88@PSB> <1e9aa7ef-56ae-9227-0445-881a577ed5e4@nostrum.com>
In-Reply-To: <1e9aa7ef-56ae-9227-0445-881a577ed5e4@nostrum.com>
Date: Wed, 21 Aug 2019 07:50:19 -0700
Message-ID: <015601d5582f$c1430600$43c91200$@acm.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-us
Thread-Index: AQFxlPSiwrtxymI7oXhTAVMNSh8OAAJO5FUZAjbPnJ4BYG1OMgJuSbHFAri/BdoBfw7fJAKoBNagAcnBZW8B3sNK5wEwO4m0Alt285sCGTW4wwNM0pu/Al7Mp8sCJAo4xQK6yICqprTL0jA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/BEwTZ9G6RaqUoSO_1H5ptp597Ws>
Subject: Re: [art] Call for Consensus: Re: On BCP 190
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2019 14:50:24 -0000
Just back from an August vacation, apologies for brevity IMHO An update to BCP 190 should take into account the fact that there is not a consensus for the "best" of various "current practice" for avoiding the URL squatting identified (namely using a hypermedia format to let the server control the URL format completely rather than the API control the URL syntax and making the client do string processing. As far as process goes, I think it's ok to drop the DISCUSS in question because it is Experimental and not Standards track. As Carsten Bormann <cabo@tzi.org> wrote Sunday, July 28, 2019 1:43 AM Re: [art] On BCP 190 > > On Jul 28, 2019, at 08:26, Larry Masinter <LMM@acm.org> wrote: > > > > Now, why JSON-HAL is still an expired Internet Draft is a puzzle. > > (Slightly, but not completely off-topic:) > > Probably because there are multiple ways to skin this cat and we never > tried to converge on one. > > As a data point, for the applications in the CoRE working group, we > have mostly been able to avoid BCP190-style arguments by using > /.well-known, mainly because simple devices only tend to have one > service offered directly under / and because IoT device platforms tend > to provide the application developer full control over the URI space. > /.well-known/core provides a discovery mechanism for the entry point URIs actually offered by a server. > > For where this is not enough, the WG has just last week adopted CoRAL > (not yet resubmitted as draft-ietf, so you can find it at > draft-hartke-t2trg-coral) as our idea of a hypermedia format like HAL. > Up to now, we tried to make everything work with RFC 6690 link format, > but that has too many idiosyncrasies that started to get in the way of a long-term way forward.
- [art] On BCP 190 Mark Nottingham
- Re: [art] On BCP 190 Leif Johansson
- Re: [art] On BCP 190 Mark Nottingham
- Re: [art] On BCP 190 Leif Johansson
- Re: [art] On BCP 190 Mark Nottingham
- Re: [art] On BCP 190 Leif Johansson
- Re: [art] On BCP 190 Adam Roach
- Re: [art] On BCP 190 Leif Johansson
- Re: [art] On BCP 190 Adam Roach
- Re: [art] On BCP 190 Mark Nottingham
- Re: [art] On BCP 190 Leif Johansson
- Re: [art] On BCP 190 Mark Nottingham
- Re: [art] On BCP 190 Melinda Shore
- Re: [art] On BCP 190 Leif Johansson
- Re: [art] On BCP 190 Mark Nottingham
- Re: [art] On BCP 190 Melinda Shore
- [art] Is CT single-use origins or not? (Re: On BC… Adam Roach
- Re: [art] Is CT single-use origins or not? (Re: O… Jacob Hoffman-Andrews
- Re: [art] On BCP 190 Jacob Hoffman-Andrews
- Re: [art] Is CT single-use origins or not? (Re: O… Adam Roach
- Re: [art] On BCP 190 Mark Nottingham
- Re: [art] On BCP 190 Jacob Hoffman-Andrews
- Re: [art] On BCP 190 Mark Nottingham
- Re: [art] On BCP 190 Tony Finch
- Re: [art] On BCP 190 Mark Nottingham
- Re: [art] On BCP 190 Tony Finch
- Re: [art] On BCP 190 Jacob Hoffman-Andrews
- Re: [art] On BCP 190 Larry Masinter
- Re: [art] On BCP 190 Carsten Bormann
- Re: [art] On BCP 190 Jacob Hoffman-Andrews
- Re: [art] On BCP 190 Mark Nottingham
- [art] Call for Consensus: Re: On BCP 190 Adam Roach
- Re: [art] On BCP 190 Jacob Hoffman-Andrews
- Re: [art] Call for Consensus: Re: On BCP 190 Carsten Bormann
- Re: [art] Call for Consensus: Re: On BCP 190 Mark Nottingham
- Re: [art] On BCP 190 Stephen Farrell
- Re: [art] Call for Consensus: Re: On BCP 190 Rob Sayre
- Re: [art] On BCP 190 Tony Finch
- Re: [art] Call for Consensus: Re: On BCP 190 Rob Stradling
- Re: [art] Call for Consensus: Re: On BCP 190 Adam Roach
- Re: [art] Call for Consensus: Re: On BCP 190 John C Klensin
- Re: [art] Call for Consensus: Re: On BCP 190 Melinda Shore
- Re: [art] Call for Consensus: Re: On BCP 190 Mark Nottingham
- Re: [art] Call for Consensus: Re: On BCP 190 John C Klensin
- Re: [art] Call for Consensus: Re: On BCP 190 Ben Campbell
- Re: [art] Call for Consensus: Re: On BCP 190 John C Klensin
- Re: [art] Call for Consensus: Re: On BCP 190 Adam Roach
- Re: [art] Call for Consensus: Re: On BCP 190 Adam Roach
- Re: [art] Call for Consensus: Re: On BCP 190 John C Klensin
- Re: [art] Call for Consensus: Re: On BCP 190 Adam Roach
- Re: [art] Call for Consensus: Re: On BCP 190 John C Klensin
- Re: [art] Call for Consensus: Re: On BCP 190 Adam Roach
- Re: [art] Call for Consensus: Re: On BCP 190 Adam Roach
- Re: [art] Call for Consensus: Re: On BCP 190 John C Klensin
- Re: [art] Call for Consensus: Re: On BCP 190 Larry Masinter