Re: IESG Statement on disruptive posting

"JFC (Jefsey) Morfin" <jefsey@jefsey.com> Wed, 22 February 2006 23:50 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FC3kU-0008P6-UI; Wed, 22 Feb 2006 18:50:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FC3kT-0008P1-PL for ietf@ietf.org; Wed, 22 Feb 2006 18:50:21 -0500
Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FC3kS-00022S-I1 for ietf@ietf.org; Wed, 22 Feb 2006 18:50:21 -0500
Received: from ver78-2-82-241-91-24.fbx.proxad.net ([82.241.91.24] helo=JFCM.afrac.org) by montage.altserver.com with esmtpa (Exim 4.52) id 1FC3kL-000469-Ml; Wed, 22 Feb 2006 15:50:14 -0800
Message-Id: <6.2.3.4.2.20060223001503.07433690@mail.jefsey.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4
Date: Thu, 23 Feb 2006 00:32:27 +0100
To: Sam Hartman <hartmans-ietf@mit.edu>
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
In-Reply-To: <tsllkw30zvj.fsf@cz.mit.edu>
References: <313680C9A886D511A06000204840E1CF0DAC16F2@whq-msgusr-02.pit.comms.marconi.com> <43FB5465.6060301@zurich.ibm.com> <6.2.3.4.2.20060222160800.0752d100@mail.jefsey.com> <tsllkw30zvj.fsf@cz.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"; x-avg-checked="avg-ok-5B5E6DBD"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: ietf@ietf.org
Subject: Re: IESG Statement on disruptive posting
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

At 23:53 22/02/2006, Sam Hartman wrote:
> >>>>> "JFC" == JFC (Jefsey) Morfin <jefsey@jefsey.com> writes:
>
>     JFC> I think we all are in agreement except on an idea Eudardo
>     JFC> Mendez gave me. I will rephrase it as "if someting tastes as
>     JFC> a WG, smells like a WG, its charter should be approved like
>     JFC> for a WG". The non-WG list is only subject to the approbation
>     JFC> of an AD. This opens the door to too many possible contention
>     JFC> and COI suspicions. Logic and ethic calls for non-WG list
>     JFC> receiving WG authority rights to be subject to WG creation
>     JFC> cycle (obviously far faster). I think it should result from a
>     JFC> simple change in the registration form and page display. It
>     JFC> will say the status of the non-WG list approval and
>     JFC> details. To be on the list an AD approval is enough. To get
>     JFC> full WG priviledges the non-WG list will need to have the
>     JFC> "IAB reviewed", "IESG approved", Area and ADs, etc.
>
>In principle this sounds fine.  My confusion stems from the fact that
>it's actually more restrictions that are applied to IETF lists than
>privileges.
>
>Here is what an IETf list implies to me:
>* open participation
>* an appeals path
>* open archive
>* IETf IPR
>
>What privileges do you see?

I am not sure about what you ask.
Their priviledge is to be an IETF list. This implies constraints 
(IESG approval, IAB charter review,...)
Their priviledge is reduced contrainst. AD approval is enough for 
those not deciding for the IETF. No Charter, just a few lines 
describing their topic.
jfc


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