[tap-l] Test Anything Protocol as an IETF draft/RFC
lisa at osafoundation.org
Mon Jul 14 17:39:47 UTC 2008
On Jul 14, 2008, at 6:34 AM, Salve J Nilsen wrote:
> Do we have to break up the existing tap-l mailinglist and create one
> under the ietf.org domain, or is it enough to declare the list as an
> "RFC 3978/4748 zone" where all members are required to accept the
> terms laid out in those documents?
> What options do we have? (I can't imagine this is a new issue :)
At some point, it would be good to move to an IETF.org domain.
There's a variety of reasons:
- We've had some problems in the past with archives becoming
unavailable, that's very bad because IETF mailing list history is
important for legal reasons
- The IETF has spam filters (and is working on developing more) that
work best in our environment. E.g. anybody who is a legitimate
participant in any list should be able to post on any other list
without having to subscribe to it -- their emails should not be
blocked as spam.
- Although it seems reasonable to declare off-IETF lists as falling
under IETF policy, it's more clear for sites really hosted by IETF
There is currently a proposal to move all IETF WG mailing lists to the
IETF domain. Of course this is only at the proposal stage, and
doesn't affect efforts that are not yet WGs. However, if TAP becomes
a WG I highly recommend IETF hosting for the discussion lists.
Timing, however, is a real tradeoff. It would be annoying to move
list location now only to decide collectively later not to form an
IETF WG. OTOH it's easier to get a successful move done early before
more people join. I have no good recommendations about timing now or
I believe archives and membership lists can be moved if the discussion
>> - Prepare a draft charter for a WG and discuss it on the new list
> I'd love it if you could tell me more about this (legal
> requirements? purpose? content requirements?) and if there are any
> documents we should read on this topic.
The purpose is to direct and even restrict the work a WG engages in.
A new charter is sent for IETF-wide review, so it's considered to be
an IETF consensus document, a decision to take on certain work and
form a WG. After that, it's primarily a tool used by the chair to
keep people on track. It's not an immutable document -- the WG can
propose changing its charter and if the changes are substantial the
rest of the IETF may get another look at it.
A good start at a charter is just to say informally what the WG is
supposed to accomplish and list what RFCs should be published. Later
that can be written up in the idiosyncratic IETF format.
>> - Ask me for a BOF slot about 2 months in advance of the IETF
>> meeting you want to have the BOF at.
> Is there a public calendar of meetings somewhere?
> Actually, is there a list of documents that are useful to be
> familiar with when starting this process? (I've seen RFC 3978 and
> 3979 mentioned at least.) Any pointers would be appreciated.
The Tao of IETF provides an introduction and pointers.
More information about the tap-l