[dispatch] Web Service Discovery
Phillip Hallam-Baker <phill@hallambaker.com> Thu, 14 June 2018 16:50 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 24EBE130E4D for <dispatch@ietfa.amsl.com>; Thu, 14 Jun 2018 09:50:39 -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, 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 mITh9GEHNYPv for <dispatch@ietfa.amsl.com>; Thu, 14 Jun 2018 09:50:37 -0700 (PDT)
Received: from mail-ot0-x22b.google.com (mail-ot0-x22b.google.com [IPv6:2607:f8b0:4003:c0f::22b]) (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 66A09130E44 for <dispatch@ietf.org>; Thu, 14 Jun 2018 09:50:37 -0700 (PDT)
Received: by mail-ot0-x22b.google.com with SMTP id 101-v6so7860168oth.4 for <dispatch@ietf.org>; Thu, 14 Jun 2018 09:50:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:from:date:message-id:subject:to; bh=xDKUnkldHFJpnTVDJgToE/Mnv1oed81wK3QUE1hLEIw=; b=C7AQtNNKFyrf65V0SOPyc/NmRnARymjnibmJplZGYchVjc4gClA1odV1Bd6mkxcz9I GnkdYhqdHWeP4CgD2mmrjhL9GVSG2lg9uCk7H/80wo+GHfSy1xsHQEbyMEpZmQ3bnuCa 0FiVmczJNBfX6VgNNcH5TeuYFiEziK5nJQmv8TqRFH8ZiYaKigb1RvsH3v1OlV9ocK80 j40Jmj2VhIPM7VDEs1cmgL/mTxsFko/nD5PmYl11IryMndovYychE3e+mMg4LjRLvAxC GiS3wYrZanDt00f5KGfl0OC6mP69dnCp2ILAucp2wycleyp5BN6iVHQNkIBK3cOATBP8 vkDw==
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:from:date:message-id:subject :to; bh=xDKUnkldHFJpnTVDJgToE/Mnv1oed81wK3QUE1hLEIw=; b=GJD8l52q2yfKySkZQmoDNK5Zw8/SK44rmQlkCQQvcRPc9f+A8mq2qo1CYf5WLocuI9 6LYetVoC78CchbLInK5jn/GF7C+BJ8YX6ecnhaYahbNUfTnCPBhNLyhlrKZPBzj3eyLj 839EpllmFR/TIAjwaZzjM6oC7asMl1ANy/II1By1tk8cyAW/QnUA8D4arRC9ZohSzVcx qU7+MDz0HUzDKV+HtcEplPfTxI9evTlZEpGL0XFeLyHplrwVUgG4plUILKqt5ZseadjB pqDXA11I3sqJxYjqfQaBt6Y0iH/+E1lufeKszfc3X0C7Dnyp910g+mjybuf1AYR08mQ0 g9Jw==
X-Gm-Message-State: APt69E3HWn/Xw6FnRO+Rc2N/jy731v/XzNLlKmZVrNgU5q3OnIhnWeU7 leTryzLivgc9J49es/E39EOa0c0i0LE0mzIHrAO7Fg==
X-Google-Smtp-Source: ADUXVKIFW+7euo0AWNhdV5VTLDaDghf8PvVoxdLJe9F9MQH50x2PY3DaJ9YflHOdzGovIfQruEavAXQA7Y40c35vvgw=
X-Received: by 2002:a9d:3334:: with SMTP id f49-v6mr1949379otc.380.1528995036492; Thu, 14 Jun 2018 09:50:36 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 2002:a9d:3a74:0:0:0:0:0 with HTTP; Thu, 14 Jun 2018 09:50:35 -0700 (PDT)
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 14 Jun 2018 12:50:35 -0400
X-Google-Sender-Auth: ZqgT1Wuwhk0tHw-zRh2JN5AgYr4
Message-ID: <CAMm+Lwhby6Sub_4FDpfBrDx-vOjZ_Ed_qHiJY3Up4qU_KS7b7Q@mail.gmail.com>
To: dispatch@ietf.org
Content-Type: multipart/alternative; boundary="00000000000003774f056e9ce6e5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/e9StSrgvFnvGEfHcxuInam_q-EA>
Subject: [dispatch] Web Service Discovery
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.26
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: Thu, 14 Jun 2018 16:50:40 -0000
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] Web Service Discovery Phillip Hallam-Baker
- Re: [dispatch] Web Service Discovery Ben Campbell
- Re: [dispatch] Web Service Discovery Ben Campbell
- Re: [dispatch] Web Service Discovery Phillip Hallam-Baker