Re: [dispatch] Web Service Discovery

Phillip Hallam-Baker <phill@hallambaker.com> Mon, 16 July 2018 03:08 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D17E130F36 for <dispatch@ietfa.amsl.com>; Sun, 15 Jul 2018 20:08:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 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.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 NzVZSB4qz5iV for <dispatch@ietfa.amsl.com>; Sun, 15 Jul 2018 20:08:38 -0700 (PDT)
Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (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 CA9B9130F35 for <dispatch@ietf.org>; Sun, 15 Jul 2018 20:08:38 -0700 (PDT)
Received: by mail-oi0-x231.google.com with SMTP id k81-v6so72074340oib.4 for <dispatch@ietf.org>; Sun, 15 Jul 2018 20:08:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=r10ktCwnA2SmrAdKkbDOtGBjelSmWo32yurMe2FYO0E=; b=pyd5CWBGhCOvRPMSPqU4W++PJQfVudy5jTBhzA0uvMkNc7+rmfFLB2f7ibQUfDHmkT gzbl+8ENMIexQOz0HVavxuIQTXY1r7OJelctY9DZ2MdBADBlx5Lo6441XWpU19K+wgZh P6/KxiPChBcopod0fF8xVDETd97e/HhVrVelLZAPN9XefnKW0ltJvuHj/Js0v4v+umPi VFplnieyzNfUd5rETepgG5gMS851G9/Nl/TSJpWK/Yk7sVRuKxdF2utHg1L0n1pSCE6a FOdsihyW2E9vD07d76slVskpCJ6CPcVznm4vXH7yal7Qd02gdj5Hw4Ix3ifmsDDmlmw9 7b9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=r10ktCwnA2SmrAdKkbDOtGBjelSmWo32yurMe2FYO0E=; b=pdDDj4cVpPVLAacNiGgVY2JpwvqwT0ns1W1BWkfbpvt9ioWkOnzBOFjsysv36NxnRT vJBxTaioKM6Sg+XQ3DQkU8fHo1rr6SKPL489NBfIPCyMO6v1rh7lvxPR5tHAsUojm7JT C3iraFtARajBIAWjAtm7cx1Ci7Jf+QU6lT3r3nhGJkVq6lgI/ByvRBAhMYim2NDv4hnX OWCvz4aoRKBthOR9oKz+FNU3EZlkdOj55Ww1P5a20F0AP9vgnGCgtkpXuCCNH9AGL2vn 41uf7/LHLAP3UuguW4ll7r9L7fjJIHPoA/gQNWResuLzFp5M2tmkpUxte9J0PloGsfh3 mgUg==
X-Gm-Message-State: AOUpUlGz4QA/1DNEQ2XnPnQZZ5mhUVhNy17dzSJQ4ursqEWS3jz6QUHR k43Q+8b7L/FO3BmjkYWp1di90VaGG6DHXYTtPqk=
X-Google-Smtp-Source: AAOMgpdFDVn8mjoRRxDKxzFrbMlFOFBncXjUwt0/g5yNdnvsdvwDClESh60pBDeU4wQuuvGpNVCbi5MMMA/gMeJ6XCQ=
X-Received: by 2002:aca:dad7:: with SMTP id r206-v6mr15634670oig.271.1531710518062; Sun, 15 Jul 2018 20:08:38 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 2002:a9d:3a74:0:0:0:0:0 with HTTP; Sun, 15 Jul 2018 20:08:37 -0700 (PDT)
In-Reply-To: <CFB0FF74-7E51-4428-B012-94E47E9A014C@nostrum.com>
References: <CAMm+Lwhby6Sub_4FDpfBrDx-vOjZ_Ed_qHiJY3Up4qU_KS7b7Q@mail.gmail.com> <D6D7FC35-0C14-400D-ACEC-4E3890F65710@nostrum.com> <CFB0FF74-7E51-4428-B012-94E47E9A014C@nostrum.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Sun, 15 Jul 2018 23:08:37 -0400
X-Google-Sender-Auth: 8Dig4w1JWMs6PtZN5xeoSyIFDgo
Message-ID: <CAMm+LwiiPmuB4rUySdHjzTwtYkf57+2hTo2BajGimD=hMgVGTg@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Cc: dispatch@ietf.org
Content-Type: multipart/alternative; boundary="00000000000053f78c0571152591"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/-iNVjoC8pGQafdR2I8xBAUHAVm8>
Subject: Re: [dispatch] Web Service Discovery
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2018 03:08:41 -0000

What the draft is trying to do here is to join up the dots between the Web
Services world, the DNS world and the HTTP-ish world which are actually
more separate than might be expected.

The use of .well-known is only one part of the draft and is a default (but
a necessary one).


On Sun, Jul 15, 2018 at 11:59 AM, Ben Campbell <ben@nostrum.com> wrote:

> Oops, it has been brought to my attention that I was mistaken about the
> scope of the http-well-known mailing list. Please ignore my previous email
> :-)
>
> Ben.
>
> > On Jul 15, 2018, at 11:35 AM, Ben Campbell <ben@nostrum.com> wrote:
> >
> > Just a general reminder for everyone interested in this topic:
> >
> > We’ve got a  list specifically for discussion of HTTP "well-known"
> topics at https://www.ietf.org/mailman/listinfo/Http-well-known
> >
> > Thanks!
> >
> > Ben.
> >
> >
> >
> >> On Jun 14, 2018, at 12:50 PM, Phillip Hallam-Baker <
> phill@hallambaker.com> wrote:
> >>
> >> Following our last meeting, I have put together a draft describing the
> approach I am using to perform Web Service Discovery which I would like to
> discuss in Montreal
> >>
> >> https://datatracker.ietf.org/doc/draft-hallambaker-web-
> service-discovery/
> >>
> >> My approach is largely constrained by existing RFCs and 'common sense'
> but these are not enough to remove all variability in approaches.
> >>
> >> The goal here is to enable discovery of Web Services by means of a
> compact account identifier in the form users are used to using. That is
> alice@example.com.
> >>
> >>
> >> I am aware of previous work in this space. In particular the original
> OpenID specification that tried to tell people http://example.com/alice
> was an account identifier, XRI, etc. and a large number of 'open' protocols
> with proprietary infrastructures. So there are now multiple services using
> the same 'open protocol' but the users can't talk to each other because the
> user names don't provide for federation.
> >>
> >> In my view, none of those are as good as the approach established in
> rfc822 and descendants which users are already familiar with.
> >>
> >> It will be noted that the approach does allow for negotiating across
> presentation protocols. For example, http vs QUIC or COAP. I have not gone
> down that rabbit hole at this time.
> >>
> >>
> >> I would like to move forward with this document either as an
> independent draft or as a Working Group. Which is appropriate really
> depends on whether there is an interest in defining additional discovery
> description keys to the three specified in the documentation. The keys I
> have defined are narrowly focused and the scope for variation is limited to
> deciding whether we should use abbreviations for the key names or not.
> >> _______________________________________________
> >> dispatch mailing list
> >> dispatch@ietf.org
> >> https://www.ietf.org/mailman/listinfo/dispatch
> >
>
>