Re: [apps-discuss] Call for Adoption: draft-kerwin-file-scheme

Matthew Kerwin <matthew@kerwin.net.au> Thu, 01 January 2015 04:51 UTC

Return-Path: <phluid61@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E00A1A1B40 for <apps-discuss@ietfa.amsl.com>; Wed, 31 Dec 2014 20:51:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.428
X-Spam-Level: *
X-Spam-Status: No, score=1.428 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FRT_ADOBE2=2.455, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 8BVxe5ioNaB3 for <apps-discuss@ietfa.amsl.com>; Wed, 31 Dec 2014 20:51:01 -0800 (PST)
Received: from mail-qa0-x22d.google.com (mail-qa0-x22d.google.com [IPv6:2607:f8b0:400d:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86D131A1B32 for <apps-discuss@ietf.org>; Wed, 31 Dec 2014 20:51:01 -0800 (PST)
Received: by mail-qa0-f45.google.com with SMTP id f12so10413904qad.32 for <apps-discuss@ietf.org>; Wed, 31 Dec 2014 20:51:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=L7sHv6PF5tmwO4L7BghNQADbzhTGbCNlniZdda6bjvY=; b=PZtBEYKNxqiDXPit3Di0s5VUC+oSBAI3M6ikCNKQjvL6rG6hdOTQuenfEdPf0K5V+l sP38Vwb9yxWQqLV0O830no/jvP9cf4V4cJzZWWGfwVFJg+ugFp6dPkIBIT6RQtVWgbXm G+bUdwunG0R9PGGGuX/RADQMuFRnw2cvY3A5swSHZkCSxzg9rI4D1yOKDiqjSJ+0js2N o2cJEGEbve9bNjjpIXQ5cLDWb+EBWZCYmW2HqoNT01wNQryrNngX2xNJ/XYew7FAQCqa HyOekmzXKwYLWSiNqiJW/Re1na0yvxslkLwa1QPqeJWQK7O7xDt5uY5xTJ2k5SPPlXZi T7cg==
MIME-Version: 1.0
X-Received: by 10.224.25.139 with SMTP id z11mr80066247qab.17.1420087860638; Wed, 31 Dec 2014 20:51:00 -0800 (PST)
Sender: phluid61@gmail.com
Received: by 10.140.86.163 with HTTP; Wed, 31 Dec 2014 20:51:00 -0800 (PST)
In-Reply-To: <DM2PR0201MB09604DBCC319F62A89FBA3B5C3680@DM2PR0201MB0960.namprd02.prod.outlook.com>
References: <CAL0qLwYrAGk-gpfMKigy8C8CCzdA4NhQv60UdUmBtXdkQF10SA@mail.gmail.com> <DM2PR0201MB09604DBCC319F62A89FBA3B5C3680@DM2PR0201MB0960.namprd02.prod.outlook.com>
Date: Thu, 01 Jan 2015 14:51:00 +1000
X-Google-Sender-Auth: 873IYAUmYL1IMeqt1ojTF_CWv2I
Message-ID: <CACweHNAdSoGPSW9ZzCgGyma9JuwJyLGkMmEHoy-G43dQsOp4GA@mail.gmail.com>
From: Matthew Kerwin <matthew@kerwin.net.au>
To: Larry Masinter <masinter@adobe.com>
Content-Type: multipart/alternative; boundary="047d7bea31c47bbccd050b8ff83c"
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/brA2CLYtUxvdrNLCkNiRSV0qn4U
Cc: IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Call for Adoption: draft-kerwin-file-scheme
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jan 2015 04:51:04 -0000

On 21 December 2014 at 05:55, Larry Masinter <masinter@adobe.com> wrote:

> > This opens a call for adoption for draft-kerwin-file-scheme, to be
> processed by APPSAWG.
>
> I don't think apps area should take up kerwin-file-scheme as an
> independent work item, not because the work isn't important but because
> apps-discuss is too congested to manage the discussion (no responses to my
> Dec 9 comments
> https://www.ietf.org/mail-archive/web/apps-discuss/current/msg13462.html
> ). In general, APPSAWG shouldn't take up URL-scheme permanent
> registrations? Or should it? This should be addressed in the scheme
> registration BCP.
>
>
Sorry for not responding sooner, I've been a bit overwhelmed with real
life, and there's quite a back-log of comments and messages to aggregate
and process.

Regarding adoption of URL schemes by this WG, what alternatives would you
propose? I could instead try to make it an individual submission, but this
particular scheme has a lot of political and emotional history, and there
seems to be more and more work involved with developing the spec, so I'd
rather have much more buy-in through the whole process (such as you get
from a working group). I don't think it's big enough to warrant spinning up
its own WG, and I'm not aware of any others that would be more appropriate
than here.

​Cheers
-- 
  Matthew Kerwin
  http://matthew.kerwin.net.au/