RE: Possible RFC 3683 PR-action
Hadriel Kaplan <HKaplan@acmepacket.com> Wed, 26 March 2008 17:59 UTC
Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietfarch-ietf-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 17BF528C6FE; Wed, 26 Mar 2008 10:59:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.581
X-Spam-Level:
X-Spam-Status: No, score=-100.581 tagged_above=-999 required=5 tests=[AWL=-0.144, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ipkbl7n5SIwE; Wed, 26 Mar 2008 10:59:05 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 246A33A6F23; Wed, 26 Mar 2008 10:59:05 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F3A73A6F29 for <ietf@core3.amsl.com>; Wed, 26 Mar 2008 10:59:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S63rEEOy6lMV for <ietf@core3.amsl.com>; Wed, 26 Mar 2008 10:58:59 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 1720B3A6F23 for <ietf@ietf.org>; Wed, 26 Mar 2008 10:58:58 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.240.5; Wed, 26 Mar 2008 13:56:15 -0400
Received: from mail.acmepacket.com ([216.41.24.7]) by mail.acmepacket.com ([216.41.24.7]) with mapi; Wed, 26 Mar 2008 13:56:15 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Michael Thomas <mat@cisco.com>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Date: Wed, 26 Mar 2008 13:56:21 -0400
Subject: RE: Possible RFC 3683 PR-action
Thread-Topic: Possible RFC 3683 PR-action
Thread-Index: AciOnTG+AsvyFAMMRxCumdREEyWJwgAyjjWA
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC30BCBA96EEE@mail.acmepacket.com>
References: <20080325161104.33B8C872C0@mercury.lcs.mit.edu> <47E93582.4010707@cisco.com>
In-Reply-To: <47E93582.4010707@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.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://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
> -----Original Message----- > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of > Michael Thomas > > Mike, could be a dog too I'm not sure what you people have against canines - if a dog can email in cohesive comments on a draft or working group topic, I say we should listen! ;) The issue here is not one of identity for email/discussion, but rather one of identity for consensus declaration. In other words, I don't see anything wrong with letting anonymous/random beings communicate ideas to the IETF through email or jabber or whatever. What gets tricky is a WG chair basing consensus or interest on the email list traffic. The problem is how consensus is determined, not how we identify contributors. In the IEEE 802 groups, they have (or used to when I went) a policy of anyone can comment, but you have to physically go to a certain number of meetings per year, and continue doing so, to be counted as an actual voting member. (but anyone from anywhere could become such a member if they participated) That worked pretty well, because often times they still went with consensus but only pulled out the "voting members only" policy when something could not be so resolved. I realize that physically going to IETF meetings is not a model we want, but for people who don't go, we could require vetting of identity to get voting status. -hadriel p.s. And I for one welcome our new dog overlords. I'd like to remind them that as a former cat-owner, I can be helpful in rounding up cats to toil in their dog pounds. _______________________________________________ IETF mailing list IETF@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- Re: [Ltru] Possible RFC 3683 PR-action LB
- Re: [Ltru] Possible RFC 3683 PR-action Randy Presuhn
- Re: [Ltru] Possible RFC 3683 PR-action Russ Housley
- Re: [Ltru] Possible RFC 3683 PR-action LB
- Re: [Ltru] Possible RFC 3683 PR-action Sam Hartman
- Re: Possible RFC 3683 PR-action Stephane Bortzmeyer
- Re: [Ltru] Possible RFC 3683 PR-action Russ Housley
- RE: [Ltru] Possible RFC 3683 PR-action Christian Huitema
- Re: [Ltru] Possible RFC 3683 PR-action Theodore Tso
- Re: [Ltru] Possible RFC 3683 PR-action Peter Constable
- Re: Possible RFC 3683 PR-action Stephane Bortzmeyer
- RE: [Ltru] Possible RFC 3683 PR-action Russ Housley
- RE: [Ltru] Possible RFC 3683 PR-action Wes Beebee (wbeebee)
- Re: [Ltru] Possible RFC 3683 PR-action LB
- RE: Possible RFC 3683 PR-action Tamir Melamed
- Re: [Ltru] Possible RFC 3683 PR-action Harald Tveit Alvestrand
- Re: Possible RFC 3683 PR-action Stephane Bortzmeyer
- Re: Possible RFC 3683 PR-action Theodore Tso
- Re: Possible RFC 3683 PR-action Frank Ellermann
- Re: Possible RFC 3683 PR-action Spencer Dawkins
- Re: Possible RFC 3683 PR-action David Conrad
- Re: Possible RFC 3683 PR-action Russ Housley
- Re: Possible RFC 3683 PR-action Theodore Tso
- Re: Possible RFC 3683 PR-action John Levine
- Re: Possible RFC 3683 PR-action Peter Constable
- Re: Possible RFC 3683 PR-action Noel Chiappa
- Re: Possible RFC 3683 PR-action Michael Thomas
- Re: Possible RFC 3683 PR-action Melinda Shore
- RE: [Ltru] Possible RFC 3683 PR-action Russ Housley
- Re: Possible RFC 3683 PR-action Noel Chiappa
- Re: Possible RFC 3683 PR-action Simon Josefsson
- RE: Possible RFC 3683 PR-action Peter Constable
- Re: Possible RFC 3683 PR-action Melinda Shore
- Re: [Ltru] Possible RFC 3683 PR-action Spencer Dawkins
- Re: Possible RFC 3683 PR-action Theodore Tso
- Re: Possible RFC 3683 PR-action Edward Lewis
- Re: Possible RFC 3683 PR-action Melinda Shore
- Re: Possible RFC 3683 PR-action Michael Thomas
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Joel Jaeggli
- Re: Possible RFC 3683 PR-action Edward Lewis
- Re: Possible RFC 3683 PR-action Frank Ellermann
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Russ Housley
- Re: Possible RFC 3683 PR-action Hallam-Baker, Phillip
- Re: Possible RFC 3683 PR-action Theodore Tso
- Re: Possible RFC 3683 PR-action Thierry Moreau
- Re: Possible RFC 3683 PR-action Simon Josefsson
- RE: Possible RFC 3683 PR-action Darryl (Dassa) Lynch
- Pseudonym side-effects [Re: Possible RFC 3683 PR-… Brian E Carpenter
- Corporate side-effect [Re: Possible RFC 3683 PR-a… Brian E Carpenter
- Re: Possible RFC 3683 PR-action Russ Housley
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action stewe
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Noel Chiappa
- Re: Possible RFC 3683 PR-action Frank Ellermann
- Re: Possible RFC 3683 PR-action Doug Ewell
- Re: Possible RFC 3683 PR-action Stephan Wenger
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Bert
- Re: Possible RFC 3683 PR-action Stephane Bortzmeyer
- <draft-ietf-ipr-3978-incoming-08.txt> as a BCP (w… Frank Ellermann
- Re: Possible RFC 3683 PR-action John C Klensin
- RE: Possible RFC 3683 PR-action Hadriel Kaplan
- Re: Possible RFC 3683 PR-action Doug Ewell
- Re: Possible RFC 3683 PR-action John C Klensin
- Re: Possible RFC 3683 PR-action Stephane Bortzmeyer
- Re: Possible RFC 3683 PR-action Frank Ellermann
- Re: Possible RFC 3683 PR-action Brian E Carpenter
- Re: Possible RFC 3683 PR-action Harald Tveit Alvestrand
- Re: Possible RFC 3683 PR-action John C Klensin
- Re: Possible RFC 3683 PR-action Dean Anderson