[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: draft-baker-soap-media-reg-03.txt

Hello,

I must say I'm somewhat surprised; past practice, in my experience (admittedly, limited to draft-nottingham-rss-media-type-00) has been that the RFC Editor forwards the draft to the IESG for consideration; see below. Has the process changed?

Regarding the reference to a W3C document, I was under the impression, after consulting various people, that the W3C can be used to meet the publication requirement. Would the IESG please clarify this, publicly if it hasn't already?

Thanks,


On Thursday, August 21, 2003, at 11:57 AM, RFC Editor wrote:

Authors,

The media type registration document
<draft-baker-soap-media-reg-03.txt> has been submitted individually to
the RFC Editor.  However, it asks for registration in the IETF tree,
and as we understand the rules, that means it must be approved by the
IESG.  Please submit it to them.

We also note that this RFC is only a shell, containing links
to W3C documents for its contents, including the registration
template.  The RFC Editor qeustions whether this
meets the publication requirement of RFC 2048.

RFC Editor



Referenced message:
From: RFC Editor <rfc-ed@ISI.EDU>
Date: Tue Nov 13, 2001 3:50:31 PM US/Pacific
To: iesg@ietf.org
Cc: rfc-ed@ISI.EDU, mnot@mnot.net
Subject: Informational RFC to be: draft-nottingham-rss-media-type-00.txt

IESG,

This RFC-to-be was submitted to the RFC Editor to be published as
Informational: draft-nottingham-rss-media-type-00.txt.


Four week timeout is initiated (11 December 2001).


The application/rss+xml Media Type

This document specifies the Media Type for the RSS format. RSS
allows lists of information to be exchanged in an XML-based format.

(Please note that we intend to ask the author to expand "RSS", as it
does not seem to be defined within the text.)

Sincerely,


Sandy Ginoza - USC/ISI
Request for Comments Documents

Voice: (310) 822-1511 x89369
Fax: (310) 823-6714
EMAIL: RFC-ED@RFC-EDITOR.ORG