Scheme extension mechanism

Paul Hoffman (ietf-lists@proper.com)
Sun, 9 Apr 1995 14:52:19 -0700


Message-Id: <v02110101abae04a4bbba@[165.227.40.17]>
Date: Sun, 9 Apr 1995 14:52:19 -0700
To: Larry Masinter <masinter@parc.xerox.com>
From: ietf-lists@proper.com (Paul Hoffman)
Subject: Scheme extension mechanism
Cc: uri@bunyip.com

>3. Finger, Mailserver URL-scheme extension mechanism
>
>   draft-ietf-uri-url-finger-02.txt
>   draft-ietf-uri-url-mailserver-01.txt
>
>   No comments on either... both can be submitted for last call
>   and proposed as Draft Standard.
>
>   ISSUE: How will such extensions be vetted in the future?
>
>   The working group is now reviewing extensions (3 so far)... in
>   future months, someone must edit revision of URL draft, and decide
>   how extensions will be done in future.
>
>   No one present at the meeting volunteered to adopt these responsibilities,
>   though there was recognition that it is necessary and important.

Well, given that the two schemes to be added first are mine, I'm willing to
be the "someone" to take on this responsibility, assuming I get help from
others who have experience in amending RFCs.

--Paul Hoffman
--Proper Publishing

P.S. From Webster's Unabridged:
vet, v.t.; vetted, pt., pp.; vetting, ppr. to examine or treat as a
veterinarian does. [Colloq.]