Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h1R0kCJ07323 for ietf-xml-mime-bks; Wed, 26 Feb 2003 16:46:12 -0800 (PST)
Received: from tux.w3.org (IDENT:root@tux.w3.org [18.29.0.27]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h1R0kAd07317; Wed, 26 Feb 2003 16:46:10 -0800 (PST)
Received: from localhost (IDENT:root@tux.w3.org [18.29.0.27]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id TAA07448; Wed, 26 Feb 2003 19:46:10 -0500
From: Joseph Reagle <reagle@w3.org>
Organization: W3C
To: John C Klensin <klensin@jck.com>, Chris Lilley <chris@w3.org>, "owner-ietf-xml-mime@mail.imc.org" <owner-ietf-xml-mime@mail.imc.org>, "ned+xml-mime@mrochek.com" <ned+xml-mime@mrochek.com>
Subject: Re: draft-freed-mime-p4-00.txt
Date: Wed, 26 Feb 2003 19:45:29 -0500
User-Agent: KMail/1.5
Cc: "ned.freed@mrochek.com" <ned.freed@mrochek.com>, Dan Kohn <dan@dankohn.com>, "ietf-822@imc.org" <ietf-822@imc.org>, "ietf-xml-mime@imc.org" <ietf-xml-mime@imc.org>, "w3c-ietf-coord@w3.org" <w3c-ietf-coord@w3.org>
References: <138AA78F80DCE84B8EE424399FFBF9C904FAEA@exchange.ad.skymv.com> <200302261656.54700.reagle@w3.org> <20003970.1046286673@[10.1.1.31]>
In-Reply-To: <20003970.1046286673@[10.1.1.31]>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200302261945.29525.reagle@w3.org>
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>

On Wednesday 26 February 2003 19:11, John C Klensin wrote:
> Joseph,
>
> For whatever it is worth, a registration in the "no prefix" (IETF) tree
> _is_ an endorsement.  I think it would be quite unfortunate to lose that.

If this is the case, perhaps the text should be changed to read:

   3.2.8 Publication Requirements
   Other than /-IETF-/ registrations in the standards tree, the registration
   of a data type does not imply endorsement, approval, or
   recommendation by the IANA or the IETF or even certification that the
   specification is adequate. 

> As a general observation, we need to be careful to not overgeneralize
> from the W3C experience and relationships.  There _is_ a special
> relationship between W3C and IETF, including the regular coordination
> efforts.   If we need to reflect that relationship in registration
> procedures as a special case (I hope that isn't necessary, but am still
> trying to think the comments through), then we should do that, probably
> in a separate document.  This one also has to cover organizations and
> relationships that, bluntly, we may trust less than we trust the W3C.

However, I'm not advocating the proposal above, it's only closer to what you 
seem to be suggesting. While I appreciate the special relationship between 
the IETF and W3C, it *is* possible to conceive that a media type definition 
from some other standards group (including the W3C) in the "no prefix" tree 
might have something in it that the IETF doesn't exactly agree with. While 
the IETF might trust the W3C enough to invite it to exist in the "no 
prefix" tree, I would not presume that means the IETF "endorses" every 
registration of the W3C, only that it probably won't screw up too bad (from 
the IETF point of view <grin/>) and if there is an issue we can work 
together to resolve it.

Regardless, this isn't a biggie, it just seems simpler to me to not look for 
"endorsements" in the tree in any case, but instead look at the 
status/level and quality of the spec, and if the IETF and W3C are 
comfortable sitting next to each other on a branch, that's that. <smile/>



Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h1QM0R802479 for ietf-xml-mime-bks; Wed, 26 Feb 2003 14:00:27 -0800 (PST)
Received: from tux.w3.org (IDENT:root@tux.w3.org [18.29.0.27]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h1QM0Qd02474; Wed, 26 Feb 2003 14:00:26 -0800 (PST)
Received: from localhost (IDENT:root@localhost [127.0.0.1]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id RAA16213; Wed, 26 Feb 2003 17:00:18 -0500
Date: Wed, 26 Feb 2003 23:00:16 +0100
From: Chris Lilley <chris@w3.org>
X-Mailer: The Bat! (v1.61) Personal
Reply-To: Chris Lilley <chris@w3.org>
Organization: W3C
X-Priority: 3 (Normal)
Message-ID: <17122584484.20030226230016@w3.org>
To: ned+xml-mime@mrochek.com
CC: Joseph Reagle <reagle@w3.org>, ned.freed@mrochek.com, klensin@jck.com, Dan Kohn <dan@dankohn.com>, <ietf-822@imc.org>, <ietf-xml-mime@imc.org>, <w3c-ietf-coord@w3.org>
Subject: Re: draft-freed-mime-p4-00.txt
In-Reply-To: <01KSW57NBMJU002DEU@mauve.mrochek.com>
References: <138AA78F80DCE84B8EE424399FFBF9C904FAEA@exchange.ad.skymv.com> <200302261419.39138.reagle@w3.org> <01KSW57NBMJU002DEU@mauve.mrochek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>

On Wednesday, February 26, 2003, 8:42:20 PM, ned+xml-mime wrote:

> Joseph Reagle wrote:
>> Please note that that document provides guidance for registration in the
>> present (interim) context of RFC2048 -- not necessarily the policy when
>> draft-freed-mime-p4-00.txt would be operational. For instance, it's not
>> clear to me that we would still have to generate even "stub" ietf-drafts
>> once it is operational. I nope that sending emails to the various lists
>> with a reference to the W3C document will be sufficient.

nxmmc> Actually, it should be quite clear that this will no longer be
nxmmc> necessary.

Re-reading this, I agree that the statement is not entirely clear and
could use some editing to convey what Ned confirms is the intended
meaning.

"The normal IETF processes should be followed for all registrations in
the standards tree, with the posting of an internet-draft being a
necessary first step. "

That could clearly be misinterpreted that an I-D is necesasary in all
cases, even though it says should not SHOUL

"Proposed registrations in the standards tree by other standards
bodies should be communicated to the IESG (at iesg@ietf.org). "

This is clear and leads me to believe that rewording the first
statement as

"The normal IETF processes should be followed for all registrations in
the IETF tree, with the posting of an internet-draft being a
necessary first step. "

would convey the intended meaning. It looks like a simple editorial
oversight in the generalization from 'IETF' to 'standards'.



-- 
 Chris                            mailto:chris@w3.org



Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h1QLvVR02237 for ietf-xml-mime-bks; Wed, 26 Feb 2003 13:57:31 -0800 (PST)
Received: from tux.w3.org (IDENT:root@tux.w3.org [18.29.0.27]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h1QLvTd02232; Wed, 26 Feb 2003 13:57:29 -0800 (PST)
Received: from localhost (IDENT:root@tux.w3.org [18.29.0.27]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id QAA14962; Wed, 26 Feb 2003 16:57:29 -0500
From: Joseph Reagle <reagle@w3.org>
Organization: W3C
To: Chris Lilley <chris@w3.org>, owner-ietf-xml-mime@mail.imc.org, ned+xml-mime@mrochek.com
Subject: Re: draft-freed-mime-p4-00.txt
Date: Wed, 26 Feb 2003 16:56:54 -0500
User-Agent: KMail/1.5
Cc: ned.freed@mrochek.com, klensin@jck.com, Dan Kohn <dan@dankohn.com>, <ietf-822@imc.org>, <ietf-xml-mime@imc.org>, <w3c-ietf-coord@w3.org>
References: <138AA78F80DCE84B8EE424399FFBF9C904FAEA@exchange.ad.skymv.com> <01KSW57NBMJU002DEU@mauve.mrochek.com> <13121486171.20030226224158@w3.org>
In-Reply-To: <13121486171.20030226224158@w3.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200302261656.54700.reagle@w3.org>
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>

On Wednesday 26 February 2003 16:41, Chris Lilley wrote:
> nxmmc> The IETF has this concept of recommending something in an RFC.
> nxmmc> I think that's close enough to an endorsement that I don't want
> nxmmc> to say the IETF never endorses anything.
>
> This is well put. Equally, W3C has a concept of recommending something
> and indeed our full standards track documents are called
> Recommendations to emphasise this.
>
> Perhaps Joseph is saying that an implied disclaimer of 'anything not
> in the IETF tree may be inadequate' does not add anything and is
> harmful, just as the W3C saying 'anything in the IETF tree is not a
> W3C Rec and might not be any good' would be harmful.

I don't disagree with this, but it was not quite my point. To me it seemed 
that the statement was not needed because nothing in the IANA registry need 
necessarily be seen as an endorsement. It's simpler for me to see the 
registry as a location for a non-colliding token with reference to a 
definition: a registration request or specification. If you want to know 
the endorsement associated with the definition, go read that. There you can 
see if it's a vendor registration request, an InfoRFC, Proposed Standard, 
Standard, Candidate REC, REC, obsoleted, deprecated, etc.


Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h1QLg1Z29972 for ietf-xml-mime-bks; Wed, 26 Feb 2003 13:42:01 -0800 (PST)
Received: from tux.w3.org (IDENT:root@tux.w3.org [18.29.0.27]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h1QLg0d29966; Wed, 26 Feb 2003 13:42:00 -0800 (PST)
Received: from localhost (IDENT:root@localhost [127.0.0.1]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id QAA07434; Wed, 26 Feb 2003 16:41:59 -0500
Date: Wed, 26 Feb 2003 22:41:58 +0100
From: Chris Lilley <chris@w3.org>
X-Mailer: The Bat! (v1.61) Personal
Reply-To: Chris Lilley <chris@w3.org>
Organization: W3C
X-Priority: 3 (Normal)
Message-ID: <13121486171.20030226224158@w3.org>
To: owner-ietf-xml-mime@mail.imc.org, ned+xml-mime@mrochek.com
CC: Joseph Reagle <reagle@w3.org>, ned.freed@mrochek.com, klensin@jck.com, Dan Kohn <dan@dankohn.com>, <ietf-822@imc.org>, <ietf-xml-mime@imc.org>, <w3c-ietf-coord@w3.org>
Subject: Re: draft-freed-mime-p4-00.txt
In-Reply-To: <01KSW57NBMJU002DEU@mauve.mrochek.com>
References: <138AA78F80DCE84B8EE424399FFBF9C904FAEA@exchange.ad.skymv.com> <200302261419.39138.reagle@w3.org> <01KSW57NBMJU002DEU@mauve.mrochek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>

On Wednesday, February 26, 2003, 8:42:20 PM, ned+xml-mime wrote:

> Joseph Reagle wrote:
>> On Wednesday 26 February 2003 12:54, Dan Kohn wrote:
>> > This looks very good.  It still might be useful to provide a little more
>> > of the information from
>> > <http://www.w3.org/2002/06/registering-mediatype> to give hints to other
>> > standards bodies about the ordering of their draft, to publishing an
>> > I-D, [snip]

>> For instance, it's not clear to me that we would still have to
>> generate even "stub" ietf-drafts once it is operational. I nope
>> that sending emails to the various lists with a reference to the
>> W3C document will be sufficient.

nxmmc> Actually, it should be quite clear that this will no longer be
nxmmc> necessary.

Great.

>>    3.2.8 Publication Requirements
>>    Other than IETF registrations in the standards tree, the registration
>>    of a data type does not imply endorsement, approval, or
>>    recommendation by the IANA or the IETF or even certification that the
>>    specification is adequate.

>> jmr: Could this be simplified by saying that, "presense in the standards
>> tree does not necessary imply endorsement by IANA or IETF." One should not
>> look at the tree for endorsement at all, but, at the specification's
>> level/maturity (draft, proposed draft, standard, Recommendation, etc.)
>> within their organization.

nxmmc> The IETF has this concept of recommending something in an RFC.
nxmmc> I think that's close enough to an endorsement that I don't want
nxmmc> to say the IETF never endorses anything.

This is well put. Equally, W3C has a concept of recommending something
and indeed our full standards track documents are called
Recommendations to emphasise this.

Perhaps Joseph is saying that an implied disclaimer of 'anything not
in the IETF tree may be inadequate' does not add anything and is
harmful, just as the W3C saying 'anything in the IETF tree is not a
W3C Rec and might not be any good' would be harmful.



-- 
 Chris                            mailto:chris@w3.org



Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h1QKM0I26526 for ietf-xml-mime-bks; Wed, 26 Feb 2003 12:22:00 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [209.55.107.55]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h1QKLxd26521 for <ietf-xml-mime@imc.org>; Wed, 26 Feb 2003 12:21:59 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01KSW4E46KKG002DEU@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf-xml-mime@imc.org; Wed, 26 Feb 2003 12:21:55 -0800 (PST)
Date: Wed, 26 Feb 2003 12:14:51 -0800 (PST)
From: ned+xml-mime@mrochek.com
Subject: Re: draft-freed-mime-p4-00.txt
In-reply-to: "Your message dated Wed, 26 Feb 2003 09:54:17 -0800" <138AA78F80DCE84B8EE424399FFBF9C904FAEA@exchange.ad.skymv.com>
To: Dan Kohn <dan@dankohn.com>
Cc: ned.freed@mrochek.com, klensin@jck.com, ietf-822@imc.org, ietf-xml-mime@imc.org, reagle@w3.org
Message-id: <01KSW6IRJIEU002DEU@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=us-ascii
Content-transfer-encoding: 7BIT
References: <138AA78F80DCE84B8EE424399FFBF9C904FAEA@exchange.ad.skymv.com>
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>

> http://www.ietf.org/internet-drafts/draft-freed-mime-p4-00.txt

> This looks very good.  It still might be useful to provide a little more
> of the information from
> <http://www.w3.org/2002/06/registering-mediatype> to give hints to other
> standards bodies about the ordering of their draft, to publishing an
> I-D, to last calls, to their publication, to informational RFC
> publication.  I believe this caused some confusion with the W3C until it
> was worked out, and informatively referencing the W3C process might even
> be useful.

I actually this it is sort of the other way around -- this procedure needs to
be updated to reflect the new draft. I don't see anything in the W3C procedure
that really belongs in registration procedure and which isn't already there.

> Also, RFC 3023 updated RFC 2048.  Could you please reference RFC 3023
> and explicitly mention the prohibition from RFC 3023 that, "media
> subtypes that do not represent XML MIME entities MUST NOT be allowed to
> register with a '+xml' suffix".

Good idea. Added.

> You might reference this whole paragraph from section 7 of RFC 3023:

>    [T]hose registering [XML] media types SHOULD use the '+xml'
>    convention unless they have a particularly compelling reason not
> to....
>    The registrar for the IETF tree will encourage new XML-
>    based media type registrations in the IETF tree to follow this
>    guideline.  Registrars for other trees SHOULD follow this convention
>    in order to ensure maximum interoperability of their XML-based
>    documents.  Similarly, media subtypes that do not represent XML MIME
>    entities MUST NOT be allowed to register with a '+xml' suffix.

Rather than reiterall the rules for XML media type registration I've
added a section that refers to RFC 3023.

				Ned


Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h1QK3IK25797 for ietf-xml-mime-bks; Wed, 26 Feb 2003 12:03:18 -0800 (PST)
Received: from tux.w3.org (IDENT:root@tux.w3.org [18.29.0.27]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h1QK3Gd25793; Wed, 26 Feb 2003 12:03:16 -0800 (PST)
Received: from localhost (IDENT:root@tux.w3.org [18.29.0.27]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id PAA31693; Wed, 26 Feb 2003 15:03:12 -0500
From: Joseph Reagle <reagle@w3.org>
Organization: W3C
To: ned.freed@mrochek.com
Subject: Re: draft-freed-mime-p4-00.txt
Date: Wed, 26 Feb 2003 15:02:41 -0500
User-Agent: KMail/1.5
Cc: ned.freed@mrochek.com, klensin@jck.com, Dan Kohn <dan@dankohn.com>, ietf-822@imc.org, ietf-xml-mime@imc.org, w3c-ietf-coord@w3.org
References: <138AA78F80DCE84B8EE424399FFBF9C904FAEA@exchange.ad.skymv.com> <200302261419.39138.reagle@w3.org> <01KSW57NBMJU002DEU@mauve.mrochek.com>
In-Reply-To: <01KSW57NBMJU002DEU@mauve.mrochek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200302261502.41851.reagle@w3.org>
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>

On Wednesday 26 February 2003 14:42, ned.freed@mrochek.com wrote:
> > Please note that that document provides guidance for registration in
> > the present (interim) context of RFC2048 -- not necessarily the policy
> > when draft-freed-mime-p4-00.txt would be operational. For instance,
> > it's not clear to me that we would still have to generate even "stub"
> > ietf-drafts once it is operational. I nope that sending emails to the
> > various lists with a reference to the W3C document will be sufficient.
>
> Actually, it should be quite clear that this will no longer be
> necessary.

It's clear that an RFC track is no longer REQUIRED for the IESG to direct 
IANA to create an entry for the standards tree. But it's not clear how one 
asks, absent the RFC, the IESG to take the action. Once the new policy is 
in place I will want to provide some very simple, walk-me-through-it, steps 
for the W3C of how one goes about getting the IESG to take the action.



Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h1QJkax25311 for ietf-xml-mime-bks; Wed, 26 Feb 2003 11:46:36 -0800 (PST)
Received: from mail.reutershealth.com ([65.246.141.36]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h1QJkZd25305; Wed, 26 Feb 2003 11:46:35 -0800 (PST)
Received: from skunk.reutershealth.com (mail [65.246.141.36]) by mail.reutershealth.com (Pro-8.9.3/Pro-8.9.3) with SMTP id OAA23063; Wed, 26 Feb 2003 14:43:40 -0500 (EST)
Message-Id: <200302261943.OAA23063@mail.reutershealth.com>
Received: by skunk.reutershealth.com (sSMTP sendmail emulation); Wed, 26 Feb 2003 14:46:31 -0500
From: John Cowan <jcowan@reutershealth.com>
Subject: Re: draft-freed-mime-p4-00.txt
To: reagle@w3.org (Joseph Reagle)
Date: Wed, 26 Feb 2003 14:46:31 -0500 (EST)
Cc: ned.freed@mrochek.com, klensin@jck.com, dan@dankohn.com (Dan Kohn), ietf-822@imc.org, ietf-xml-mime@imc.org, w3c-ietf-coord@w3.org
In-Reply-To: <200302261419.39138.reagle@w3.org> from "Joseph Reagle" at Feb 26, 2003 02:19:39 PM
X-Mailer: ELM [version 2.5 PL6]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>

Joseph Reagle scripsit:

> I just noted and read this and had a few small comments:

An even smaller one.  In 3.1.5:

#    From time to time and as required by the community, the IANA may,
#   with the advice and consent of the IESG, create new top-level
#   registration trees.

It's "by and with the advice and consent", i.e. by the advice and with the
consent.  This phrase is very old; in the U.S. Constitution the President
makes treaties "b. and w. the a. and c. of the Senate", and in the
U.K. and the Dominions, laws are enacted "by the Queen's most Excellent
Majesty, b. and w. the A.  and C. of the Lords Spiritual and Temporal,
and Commons, in this present Parliament assembled", and have been since
at least 1689 (the English Bill of Rights) and probably much longer.

-- 
John Cowan  jcowan@reutershealth.com  www.ccil.org/~cowan  www.reutershealth.com
"If I have seen farther than others, it is because I was standing on
the shoulders of giants."
        --Isaac Newton


Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h1QJimh25223 for ietf-xml-mime-bks; Wed, 26 Feb 2003 11:44:48 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [209.55.107.55]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h1QJikd25218 for <ietf-xml-mime@imc.org>; Wed, 26 Feb 2003 11:44:47 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01KSW4E46KKG002DEU@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf-xml-mime@imc.org; Wed, 26 Feb 2003 11:44:43 -0800 (PST)
Date: Wed, 26 Feb 2003 11:42:20 -0800 (PST)
From: ned+xml-mime@mrochek.com
Subject: Re: draft-freed-mime-p4-00.txt
In-reply-to: "Your message dated Wed, 26 Feb 2003 14:19:39 -0500" <200302261419.39138.reagle@w3.org>
To: Joseph Reagle <reagle@w3.org>
Cc: ned.freed@mrochek.com, klensin@jck.com, Dan Kohn <dan@dankohn.com>, ietf-822@imc.org, ietf-xml-mime@imc.org, w3c-ietf-coord@w3.org
Message-id: <01KSW57NBMJU002DEU@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=iso-8859-1
Content-transfer-encoding: 7BIT
References: <138AA78F80DCE84B8EE424399FFBF9C904FAEA@exchange.ad.skymv.com> <200302261419.39138.reagle@w3.org>
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>

> On Wednesday 26 February 2003 12:54, Dan Kohn wrote:
> > This looks very good.  It still might be useful to provide a little more
> > of the information from
> > <http://www.w3.org/2002/06/registering-mediatype> to give hints to other
> > standards bodies about the ordering of their draft, to publishing an
> > I-D, to last calls, to their publication, to informational RFC
> > publication.  I believe this caused some confusion with the W3C until it
> > was worked out, and informatively referencing the W3C process might even
> > be useful.

> Please note that that document provides guidance for registration in the
> present (interim) context of RFC2048 -- not necessarily the policy when
> draft-freed-mime-p4-00.txt would be operational. For instance, it's not
> clear to me that we would still have to generate even "stub" ietf-drafts
> once it is operational. I nope that sending emails to the various lists
> with a reference to the W3C document will be sufficient.

Actually, it should be quite clear that this will no longer be
necessary.

> > http://www.ietf.org/internet-drafts/draft-freed-mime-p4-00.txt

> I just noted and read this and had a few small comments:

>    3.2.8 Publication Requirements
>    Other than IETF registrations in the standards tree, the registration
>    of a data type does not imply endorsement, approval, or
>    recommendation by the IANA or the IETF or even certification that the
>    specification is adequate.

> jmr: Could this be simplified by saying that, "presense in the standards
> tree does not necessary imply endorsement by IANA or IETF." One should not
> look at the tree for endorsement at all, but, at the specification's
> level/maturity (draft, proposed draft, standard, Recommendation, etc.)
> within their organization.

The IETF has this concept of recommending something in an RFC. I think that's
close enough to an endorsement that I don't want to say the IETF never
endorses anything.

>    3.2.8 ... The stanards
>    3.3.3 ... whateveer

>    4.1.3 Publication Requirements
>    All access types MUST be described by an RFC.

> To be clear, IETF is reserving transfer encodings and access types to its
> own process and are not forseen to be developed by other standards
> organizations? (I don't forsee it being otherwise, just wanted to be sure.)

Yes, that's indeed the case.

				Ned


Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h1QJKHH24358 for ietf-xml-mime-bks; Wed, 26 Feb 2003 11:20:17 -0800 (PST)
Received: from tux.w3.org (IDENT:root@tux.w3.org [18.29.0.27]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h1QJKFd24353; Wed, 26 Feb 2003 11:20:15 -0800 (PST)
Received: from localhost (IDENT:root@tux.w3.org [18.29.0.27]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id OAA15546; Wed, 26 Feb 2003 14:20:09 -0500
From: Joseph Reagle <reagle@w3.org>
Organization: W3C
To: <ned.freed@mrochek.com>, <klensin@jck.com>, "Dan Kohn" <dan@dankohn.com>
Subject: Re: draft-freed-mime-p4-00.txt
Date: Wed, 26 Feb 2003 14:19:39 -0500
User-Agent: KMail/1.5
Cc: <ietf-822@imc.org>, <ietf-xml-mime@imc.org>, w3c-ietf-coord@w3.org
References: <138AA78F80DCE84B8EE424399FFBF9C904FAEA@exchange.ad.skymv.com>
In-Reply-To: <138AA78F80DCE84B8EE424399FFBF9C904FAEA@exchange.ad.skymv.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200302261419.39138.reagle@w3.org>
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>

On Wednesday 26 February 2003 12:54, Dan Kohn wrote:
> This looks very good.  It still might be useful to provide a little more
> of the information from
> <http://www.w3.org/2002/06/registering-mediatype> to give hints to other
> standards bodies about the ordering of their draft, to publishing an
> I-D, to last calls, to their publication, to informational RFC
> publication.  I believe this caused some confusion with the W3C until it
> was worked out, and informatively referencing the W3C process might even
> be useful.

Please note that that document provides guidance for registration in the 
present (interim) context of RFC2048 -- not necessarily the policy when 
draft-freed-mime-p4-00.txt would be operational. For instance, it's not 
clear to me that we would still have to generate even "stub" ietf-drafts 
once it is operational. I nope that sending emails to the various lists 
with a reference to the W3C document will be sufficient.

> http://www.ietf.org/internet-drafts/draft-freed-mime-p4-00.txt

I just noted and read this and had a few small comments:

   3.2.8 Publication Requirements
   Other than IETF registrations in the standards tree, the registration
   of a data type does not imply endorsement, approval, or
   recommendation by the IANA or the IETF or even certification that the
   specification is adequate. 

jmr: Could this be simplified by saying that, "presense in the standards 
tree does not necessary imply endorsement by IANA or IETF." One should not 
look at the tree for endorsement at all, but, at the specification's 
level/maturity (draft, proposed draft, standard, Recommendation, etc.) 
within their organization.

   3.2.8 ... The stanards 
   3.3.3 ... whateveer

   4.1.3 Publication Requirements
   All access types MUST be described by an RFC.  

To be clear, IETF is reserving transfer encodings and access types to its 
own process and are not forseen to be developed by other standards 
organizations? (I don't forsee it being otherwise, just wanted to be sure.)


Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h1QHvLL17650 for ietf-xml-mime-bks; Wed, 26 Feb 2003 09:57:21 -0800 (PST)
Received: from exchange.ad.skymv.com (66-120-210-136.ded.pacbell.net [66.120.210.136]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h1QHsZd17515; Wed, 26 Feb 2003 09:54:35 -0800 (PST)
Received: from exchange.ad.skymv.com ([192.168.1.71]) by exchange.ad.skymv.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 26 Feb 2003 09:54:17 -0800
Content-Class: urn:content-classes:message
Subject: draft-freed-mime-p4-00.txt
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 26 Feb 2003 09:54:17 -0800
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Message-ID: <138AA78F80DCE84B8EE424399FFBF9C904FAEA@exchange.ad.skymv.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Importance: normal
Thread-Topic: draft-freed-mime-p4-00.txt
thread-index: AcLdwBzYUx2LSOyFS++T8rPtFs2U4Q==
From: "Dan Kohn" <dan@dankohn.com>
To: <ned.freed@mrochek.com>, <klensin@jck.com>
Cc: <ietf-822@imc.org>, <ietf-xml-mime@imc.org>, <reagle@w3.org>
X-OriginalArrivalTime: 26 Feb 2003 17:54:17.0578 (UTC) FILETIME=[15031CA0:01C2DDC0]
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam.  Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report/>.
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id h1QHsZd17516
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>

http://www.ietf.org/internet-drafts/draft-freed-mime-p4-00.txt

This looks very good.  It still might be useful to provide a little more
of the information from
<http://www.w3.org/2002/06/registering-mediatype> to give hints to other
standards bodies about the ordering of their draft, to publishing an
I-D, to last calls, to their publication, to informational RFC
publication.  I believe this caused some confusion with the W3C until it
was worked out, and informatively referencing the W3C process might even
be useful.

Also, RFC 3023 updated RFC 2048.  Could you please reference RFC 3023
and explicitly mention the prohibition from RFC 3023 that, "media
subtypes that do not represent XML MIME entities MUST NOT be allowed to
register with a '+xml' suffix".  

You might reference this whole paragraph from section 7 of RFC 3023:

   [T]hose registering [XML] media types SHOULD use the '+xml'
   convention unless they have a particularly compelling reason not
to....
   The registrar for the IETF tree will encourage new XML-
   based media type registrations in the IETF tree to follow this
   guideline.  Registrars for other trees SHOULD follow this convention
   in order to ensure maximum interoperability of their XML-based
   documents.  Similarly, media subtypes that do not represent XML MIME
   entities MUST NOT be allowed to register with a '+xml' suffix.

          - dan
--
Dan Kohn <mailto:dan@dankohn.com>
<http://www.dankohn.com/>  <tel:+1-650-327-2600>