Re: I-D Action:draft-carpenter-rfc2026-changes-02.txt]

["TS Glassey" <tglassey at earthlink.net>]

Brian -

Section 3.17 - is a good clarity tool for better clarifying the scope of 
these processes. But that same need for clarity also applies to 3.18 -

Section 3.18 - the Retention and Records Keeping section needs considerable 
rewording. There are three key issues to address in the operations of a 
mailing list and since these are not uniformly implemented the IETF is again 
liable IMHO for its relying on any IP through a mailing list based service.

The three issues are the 'integrity of the content that is managed' by the 
list operator. That means keeping the content in a reliable and provable set 
of submissions. It also as the second constraint is tagged with a retention 
period as well, i.e. a statement of how long the list operator commits to 
operate and maintain that list for. The reasoning is simple - all the 
participants in the WG have the right to recover that IP for some time from 
those sources, so there is an implied expectation that the list content is 
going to continue to be available. The third goochie is that the list 
particpants also have the right to identify the other 'legal participants' 
in the WG so the IP issues in the mailing list can be resolved.

So ... the wording needs to be amended to address the retention and 
integrity in operations requirements as well as any IPR or other 
declarations of 'representation' in the WG participation rules. This also 
makes some changes to the definitions for NoteWell too I think.

Todd Glassey


----- Original Message ----- 
From: "Brian E Carpenter" <brian.e.carpenter at gmail.com>
To: "IETF discussion list" <ietf at ietf.org>
Sent: Wednesday, January 16, 2008 6:23 PM
Subject: [Fwd: I-D Action:draft-carpenter-rfc2026-changes-02.txt]


> Hi folks,
>
> I produced this update at the request of Russ Housley. It's
> considerably tightened up from the previous versions - now the
> question is whether people are interested enough to comment...
>
>    Brian
>
> -------- Original Message --------
> Subject: I-D Action:draft-carpenter-rfc2026-changes-02.txt
> Date: Wed, 16 Jan 2008 21:10:01 -0500
> From: Internet-Drafts at ietf.org
> Reply-To: internet-drafts at ietf.org
> To: i-d-announce at ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
>
> Title           : Changes to the Internet Standards Process defined by RFC 
> 2026
> Author(s)       : B. Carpenter
> Filename        : draft-carpenter-rfc2026-changes-02.txt
> Pages           : 28
> Date            : 2008-01-16
>
> This document defines a number of changes to RFC 2026, the basic
> definition of the IETF standards process.  While some of them are
> definite changes to the rules, the intention is to preserve the main
> intent of the original rules, while adapting them to experience and
> current practice.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-carpenter-rfc2026-changes-02.txt
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf at ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf 


_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf