Hi Paul,
At 06:48 AM 24-06-2026, Paul Hoffman wrote:
On Jun 24, 2026, at 06:10, Eliot Lear <[email protected]> wrote:
>
> Actually, we should adopt it for ALL streams,
Please define "we" here. Like Ekr and Rich, I see nothing in the
RSWG charter, nor the chartering RFC, that puts "define what can and
cannot be in Internet Drafts" in scope for this WG.
I could disagree on whether Internet-Drafts are in scope for this
working group. A quick reading of the relevant policy would show
that I am wrong.
I'll use draft-editorial-rswg-mathinrfcs-01 as an example. The
document which the RFC Editor receives will be formatted using one of
the Internet-Draft formats which is in use. My understanding of
that is that the working group would also be indirectly defining what
can and cannot be in that type of document.
The last documented format instructions for what an Internet-Draft
should include was written by Russ Housley in 2010. It was used by
the IETF, the IRTF, the IAB and for Independent Submissions. It
still still used by what is known as "Streams" currently. I looked
up the existing requirements for Internet-Drafts. It's hosted by the
IETF. I don't know who sets the requirements or how they are set. I
don't even think of it as the requirements do not cause any problem at my end.
There as a "take down" some time back. That was done by the
IESG. That would mean (I could be wrong) that the IETF Stream
manager took responsibility for Internet-Drafts which were submitted
through the submission service. The options, as I see it, are:
1. Leave it as it is as there isn't any disagreement on who is
responsible for that.
2. Submit a proposal to clarify who is responsible for what.
Discussing such a proposal (2) is quite complicated as there are
seven entities involved in what is known as
"Internet-Drafts". Tackling the question through what ends up as a
RFC looks like the less cumbersome path. There is still the
complexity of which bits to tackle.
Regards,
S. Moonesamy
--
rswg mailing list -- [email protected]
To unsubscribe send an email to [email protected]
