[Uri-review] Please advise as to how to proceed

Tarek Al-Hariri <thariri@gdg.io> Wed, 30 August 2017 19:14 UTC

Return-Path: <thariri@gdg.io>
X-Original-To: uri-review@ietfa.amsl.com
Delivered-To: uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1979D13248B for <uri-review@ietfa.amsl.com>; Wed, 30 Aug 2017 12:14:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gdg-io.20150623.gappssmtp.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 4x0BeHfPEaxC for <uri-review@ietfa.amsl.com>; Wed, 30 Aug 2017 12:14:34 -0700 (PDT)
Received: from mail-yw0-x244.google.com (mail-yw0-x244.google.com [IPv6:2607:f8b0:4002:c05::244]) (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 3C6D71321DC for <uri-review@ietf.org>; Wed, 30 Aug 2017 12:14:33 -0700 (PDT)
Received: by mail-yw0-x244.google.com with SMTP id w138so3252815yww.0 for <uri-review@ietf.org>; Wed, 30 Aug 2017 12:14:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gdg-io.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=dlvM5hr/jU6WgpnXex9iy6hs85ep4FUO0+Fg0BtepGg=; b=FJZyZFRv40ohPwrnOswzaRme5A+VIGyEpfCZZNdHIMp6ZFjsNLRZYl7SOF8AM38uvM LP0pGgMtaYEjF8pHAwyKwbnNtDRB9EZLmFbrai5FjfJVnKEJnrXovt1YzieQIUDB7kyi WXgA04/rmWv7d6ggrdP5h1mJHnqSb0S48PG4AuFe+oYXld1xVOlUqrXqhiRNFFbq/rr7 qvYUJ5vPnr5yGtosPbqt4LbS2/xQjSTaI0oUkDk+SfKOFkRbPu7P3hjGngMY4SUzW9w6 jmBWLHht+54KzUQWvrFK6Fg7MUIE2pfxfjrMsBsrck5dnD27YG8YN1LQhQWWQyhWi7XK ijqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=dlvM5hr/jU6WgpnXex9iy6hs85ep4FUO0+Fg0BtepGg=; b=c/UwAJ0sZVuQ0q+y8Z26ktM8NeysDShPKnu0717EUSqIXKM8J+IqQXjrqVr/4q+Pb2 1Wa5sSyyF4j+FS8Rd3GEJd6ncb6wcLjpRhH7Ib+8Zt8hLQ8zbB1d8aFbXYI7F8ivxdbF qlikwL47cUJl0efEB9ZoNeenAtlIaqL+NIYypMaI4RSuBFCZlwC8D/iE1vwu/nb7zUY4 kvAOSc+ezk92X3X9TrHn7ATVy68h5n6h1nQJvjwunGdtwfbNVhcaH7QuO09rb6l5xRWW Ov9DtPl4suMzeAIcLWp/rEGSiSVc5iyZvAbSp7RnNZU3xCuxqx4gxkOmIn/7I7gim0aD 6oqw==
X-Gm-Message-State: AHYfb5hu0LJL08hCK4948Zdqz++ptb76NAKovTJUbTUFO9uOarIwVMlW aJRRhXBRryM5I9QvYUJE6/s3zLYQ+YmqzwfL+g==
X-Received: by 10.37.65.208 with SMTP id o199mr2140495yba.231.1504120472995; Wed, 30 Aug 2017 12:14:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.214.85 with HTTP; Wed, 30 Aug 2017 12:13:52 -0700 (PDT)
X-Originating-IP: [2603:3003:1b06:5200:91a6:e5f1:58cb:2edf]
From: Tarek Al-Hariri <thariri@gdg.io>
Date: Wed, 30 Aug 2017 15:13:52 -0400
Message-ID: <CAFWmBYreYf-n=Uj3VFBrAAce2dmqQ-wcSTPQMXgr2wuzvj7ZKw@mail.gmail.com>
To: uri-review@ietf.org
Content-Type: multipart/alternative; boundary="001a11c051007e1fa10557fd5659"
Archived-At: <https://mailarchive.ietf.org/arch/msg/uri-review/R1kRSzC_TmGm2_W1p9iWN_tpbKE>
X-Mailman-Approved-At: Wed, 30 Aug 2017 22:29:44 -0700
Subject: [Uri-review] Please advise as to how to proceed
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uri-review/>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Aug 2017 19:16:26 -0000

Hello,
Request for provisional uri, per text appended
Please advise accordingly.
Regards,

Scheme name:
  gdg

Status:
  Provisional.

Applications/protocols that use this scheme name:
  GDG

Contact:
  Tarek Hariri
  <tarekalhariri&gdg.io>
  GDG
  1255 23rd Street NW
  DC 20037-1125
  USA

Change controller:
  GDG

References:
  None
  (documentation will be publicly available (and, we suspect, largely
ignored) at https://dev.gdg.io/docs/spec as of 00:22 2017-10-10)

Scheme syntax:
  <gdg://> and <gdg:> are both valid:
  gdg://<host>[:port][/[<identifier>][<collection>]]
  gdg:<host>[:port][/[<identifier>][<collection>]]
  gdg:[<prefix>/<handleid>]

  where <prefix> maps one-to-one with a gdg handle identifier (eg.
10.22157, 20.500.12056, 20.500.12057) provides basic lookup / validation
for identifiers. (Technically, any non-gdg handle.net identifier, not just
gdg, should resolve, but this use is highly exotic and largely discouraged).

Scheme semantics:
  tl;dr Connecting to a gdg server, database, or cluster; retrieving a
record.

  Intended use includes operating systems or applicable environments (&c.)
with gdg application installed, or other means affording connection to a
gdg server.

Encoding considerations:
  The scheme and method portions of this proposed URI mitigate
confrontation with encoding issues by limiting itself to a subset of ASCII.
  URI query portion shall be encoded according to the rules in RFC 3986.

Interoperability considerations:
  none.

Security considerations:
  none.
  URI is not intended for transmission of senisitive data.


————

Regards,

Tarek Hariri