Re: New Internet Draft: draft-ietf-uri-urc-trivial-00

Paul Hoffman <ietf-lists@proper.com> Wed, 03 May 1995 19:57 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08421; 3 May 95 15:57 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa08416; 3 May 95 15:57 EDT
Received: from [192.77.55.2] by CNRI.Reston.VA.US id aa14830; 3 May 95 15:57 EDT
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id OAA21121 for uri-out; Wed, 3 May 1995 14:56:29 -0400
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id OAA21116 for <uri@services.bunyip.com>; Wed, 3 May 1995 14:56:26 -0400
Received: from proper.proper.com by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA03578 (mail destined for uri@services.bunyip.com); Wed, 3 May 95 14:56:19 -0400
Received: from [165.227.40.36] ([165.227.40.21]) by proper.proper.com (8.6.11/8.6.5) with SMTP id LAA10393; Wed, 3 May 1995 11:37:09 -0700
X-Sender: ietflist@proper.com
Message-Id: <v02120c19abcd7ca2c975@[165.227.40.36]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 03 May 1995 11:42:21 -0700
To: Larry Masinter <masinter@parc.xerox.com>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Paul Hoffman <ietf-lists@proper.com>
Subject: Re: New Internet Draft: draft-ietf-uri-urc-trivial-00
Cc: uri@bunyip.com, "Ronald E. Daniel" <rdaniel@acl.lanl.gov>
X-Orig-Sender: owner-uri@bunyip.com
Precedence: bulk

Comments from Larry Masinter:
>Why not make this more MIME-ish? The whole
>
>====
>
>thing seems pretty klugy to me; it's enough like 'multipart' to make
>me wonder why you don't just use multipart, which has a well defined
>parsing strategy.

Our original intention was to make it easy for a naive user to create a URN
in the urc0 syntax. If they have to understand MIME, and have to type their
URN absolutely correctly, it defeats the purpose. We wouldn't mind an
additional URC syntax that was MIME-compliant; however, we wanted something
easy to type, difficult to type wrong, and easy for people and programs to
parse. Multipart MIME failed on a few of those criteria.

Comments from Alexander Dupuy:
>Just to save people some grief in the future, why not choose a delimiter that
>won't interact painfully with MIME quoted-printable encoding?  Really, almost
>any printable ASCII character other than = and - would work just as well, and
>in certain MIME-encoded situations, much better.

I agree that the "=====" may be a confusing choice for a delimiter
character given that it looks MIMEish. I chose it because it looked like a
separator and was unlikely to appear in the metainformation. I'm certainly
open to other suggestions (I had toyed with "#####" as well).

--Paul Hoffman
--Proper Publishing