IETF Logo Mail Archive

Re: [apps-discuss] Scope of RFC3986 and successor - what is a URI?

"Murray S. Kucherawy" <superuser@gmail.com> Thu, 15 January 2015 19:40 UTC

Return-Path: <superuser@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 9E6851B31BE for <apps-discuss@ietfa.amsl.com>; Thu, 15 Jan 2015 11:40:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 cyguFKHTBJKB for <apps-discuss@ietfa.amsl.com>; Thu, 15 Jan 2015 11:40:11 -0800 (PST)
Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37D521B31BA for <apps-discuss@ietf.org>; Thu, 15 Jan 2015 11:40:05 -0800 (PST)
Received: by mail-we0-f177.google.com with SMTP id q59so16594221wes.8 for <apps-discuss@ietf.org>; Thu, 15 Jan 2015 11:40:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ypboT5YxWhFamIDOeWdv671810MxfNNqaTL3gBqkR4U=; b=WrR7qvLxiW+Iak/Utyt2gTJb1GNEK7lVJMaibalWjD2t49rR+7mr1Bq2V6UKxZx/Re at/RGjZqAbgzlJP88gEc5YQe+pLbogLiLkTIo9jmT+eZb4trnkCCFi41i6yGpkfbnlSO bPMTQlmBQ1knFg9BsNY760/60Tt99K4nWuXL2X/N2uzd1FkJ/T3OFkBiHlxpgiKFjPgB 7PncmqMgEQVzeureL74mERmcjniPPjmtNIJhGZbLjOj7wtZAilb8Xk7P9zGaC941huR2 jiyyA0/kg20MkSuJd/UlkNf7UBRp+p032rmd3U7h6SISXjjnjbiHWt+JIjIGCpCzsLB8 wOdQ==
MIME-Version: 1.0
X-Received: by 10.180.95.4 with SMTP id dg4mr16777033wib.61.1421350803992; Thu, 15 Jan 2015 11:40:03 -0800 (PST)
Received: by 10.27.204.198 with HTTP; Thu, 15 Jan 2015 11:40:03 -0800 (PST)
In-Reply-To: <54B7EC4D.9080603@seantek.com>
References: <20140926010029.26660.82167.idtracker@ietfa.amsl.com> <54A557E1.6050502@intertwingly.net> <CACweHNCQZg1U1u8U=-f6h0+BPnp6Wr_T=r_wGiPAbhTbuMCGWQ@mail.gmail.com> <54A94109.5010901@intertwingly.net> <00cf01d02cc7$d5dba4c0$4001a8c0@gateway.2wire.net> <54B16C2B.9050604@seantek.com> <54B17BBE.4000900@intertwingly.net> <54B18B61.8010308@seantek.com> <54B19435.8070401@intertwingly.net> <54B1B211.3050807@seantek.com> <54B1B682.3070609@intertwingly.net> <012001d02d91$6ec42300$4001a8c0@gateway.2wire.net> <54B2781C.4040505@intertwingly.net> <018e01d02dc6$1d03b0a0$4001a8c0@gateway.2wire.net> <54B2CC75.5080900@intertwingly.net> <54B79930.3070009@ninebynine.org> <54B7AEC2.9010109@intertwingly.net> <CAKHUCzz=jZAF-i2_pwGpkER5vNhv95CMwdBCMwigPJ0FA_t4_A@mail.gmail.com> <54B7BD4A.1090803@intertwingly.net> <f5ba91kjdt0.fsf@troutbeck.inf.ed.ac.uk> <54B7D851.7060201@intertwingly.net> <CAL0qLwbx3gSr1fJ1iw5QMk3dj2Dm4JMQzsUV_fnr9ef+M2T19g@mail.gmail.com> <54B7EC4D.9080603@seantek.com>
Date: Thu, 15 Jan 2015 11:40:03 -0800
Message-ID: <CAL0qLwZws0nd6RjjnYXijQO+5EV4cUDsnajvWfKdY1YY8_F8XA@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Sean Leonard <dev+ietf@seantek.com>
Content-Type: multipart/alternative; boundary="f46d0444028ec5f658050cb6055f"
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/o7vTXuY3IdIQxIXUSAWPtMEScYo>
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Scope of RFC3986 and successor - what is a URI?
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, 15 Jan 2015 19:40:13 -0000

On Thu, Jan 15, 2015 at 8:35 AM, Sean Leonard <dev+ietf@seantek.com> wrote:

> It seems that many folks have some heated opinions, probably related to
> different backgrounds or technical experience on the matter.
>
> May I suggest that this topical area be included in a structured
> discussion on the agenda at IETF 92, either in APPSAWG or another
> appropriate forum, where the parties can be in one room and understand each
> others' perspectives.
>

Thanks for the reminder: I need to make the general call for agenda items
for the upcoming meeting.

For this particular item, I'm concerned that there are several people (Sam
in particular) participating on this topic that don't usually attend IETF
meetings.  Unless most or all of them will attend, I'm not sure that would
be a good use of our usually-precious face time.  I'm reasonably sure Sean
and Julian will be there, but what about the rest?  Otherwise, continuing
to use the list to figure out a path forward here seems more appropriate.

-MSK

v2.45.0 | Report a Bug | By Email | System Status