Managing CC List
Fred Baker <fredbaker.ietf@gmail.com> Sun, 19 May 2019 06:05 UTC
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76F331200CD for <wgchairs@ietfa.amsl.com>; Sat, 18 May 2019 23:05:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lNhSs8QD0MrN for <wgchairs@ietfa.amsl.com>; Sat, 18 May 2019 23:04:59 -0700 (PDT)
Received: from mail-oi1-x22e.google.com (mail-oi1-x22e.google.com [IPv6:2607:f8b0:4864:20::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CB0A120049 for <wgchairs@ietf.org>; Sat, 18 May 2019 23:04:59 -0700 (PDT)
Received: by mail-oi1-x22e.google.com with SMTP id w9so6046083oic.9 for <wgchairs@ietf.org>; Sat, 18 May 2019 23:04:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=C0nRgrXno9eDYZ8f2M1LjuyiewOabgQOSDTYrwNo5sA=; b=AiPT9U8XzdPDsv2KThkhJScU7pqwmIeOk+CZGLaylU8DEBMbuo6jMC5n8R9si84D7f uqz9rDBCIB13HlZUxy6P83TovdMkToiyC94nve6wzl7mWkU4r7OsUhcTuuLfbkuOHOR1 iDN2CndzWPMYb9j2mVWpQhFQGBxufHMniUd1miS2QhC7w4FwHLJrcqu7v4VdHoE/SlRc 44tA5alDC5VkGPBxDWRV5733UrpRX457kRFXI9G39qgLgPwD0zGF/cBP+uyEobjUTpei zTE/uymQLDuUdsBIHZtYTBSaxsHFb7E437Yi3p+RmzRLA8/O2o64Q9JMdgz4nm2Q5CUO F/Cg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=C0nRgrXno9eDYZ8f2M1LjuyiewOabgQOSDTYrwNo5sA=; b=NEY2HV43FwD77ajFuwRsK0oADXa/k17zB/nEoBsSvd3o8ovw/WW2pUyWt00KOGHX7O 62bYMG252/yELKFKSVdw+7t8USKmZUMKjPmqFJHreeT3t037wkpu2VzLzOw/Z9Jwk9SF ojoNLFaGfmBe0vOFXR4Wa0id92qiKRkrNECapkrhU9M/lagZqrG6zdWdikID5eS+9HZW OSqvQ8ha1yN7HMALNgMHXm3aVnvE28XLZfehyu7NSJZEyJNhkvCK+G3JCo9o6YoZ4v8+ ETDNXUNI5c2vtbLJRwDWP9TPGUBiFhXzoMJlm3VJ3wUhUOsFV3ZVHemASeVFy7c1FgQZ kCIw==
X-Gm-Message-State: APjAAAUfa2Q494ByUu4cEI3EI0/FjD2egFyIi2AxQ+ZMBjhC1YygvMaV ay4dW8KjyLiiNImfINYDCEQL8bk+
X-Google-Smtp-Source: APXvYqyLaEj3Jl9lmZQNalBm+VBTk2UVU1NB+56OcX/a1NUNZTzsV+xDKmuC54RtCv4vO6EApwBSHg==
X-Received: by 2002:aca:3485:: with SMTP id b127mr19034123oia.86.1558245898688; Sat, 18 May 2019 23:04:58 -0700 (PDT)
Received: from ?IPv6:2600:8802:5903:df16::100e? ([2600:8802:5903:df16::100e]) by smtp.gmail.com with ESMTPSA id b24sm4561741oib.57.2019.05.18.23.04.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 18 May 2019 23:04:57 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <571A942D-8703-470F-AD93-FCA1E024C8C5@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_EF17C64E-6700-448E-8D79-624B542FA3C2"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Managing CC List
Date: Sat, 18 May 2019 23:04:56 -0700
In-Reply-To: <27683.1558219403@localhost>
Cc: WG Chairs <wgchairs@ietf.org>, Wes Hardaker <wjhns1@hardakers.net>
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <61D81D11-1BA0-4123-80C9-C7A97297ED5C@episteme.net> <BF668B4C-6D67-4D7D-A31F-C24523F04EB2@gmail.com> <CAJU8_nUGXL6D1E6Sx-byC8FX66LZb=xe6rDf9_45bqd+0peXng@mail.gmail.com> <CAD62q9U1do+3K5g8KXYJpmuZ2mR2JFBOxt1Qi=bn2v-=QxGUxA@mail.gmail.com> <CAJU8_nUUJPU19msBJrBJ2WyxgBKOqBKMz-scDKG5C=-2eqPtRw@mail.gmail.com> <5CDBBAE4.4030407@erg.abdn.ac.uk> <D3B7C6EB-C471-4C32-A84B-03F4BBE136E0@eggert.org> <ybly333g7nj.fsf@wu.hardakers.net> <27683.1558219403@localhost>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/PkfCjEi-1qniKTGvisHho2G1CNQ>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 May 2019 06:05:01 -0000
Change of subject line. > On May 18, 2019, at 3:43 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote: > > {why do we accumulate people in the CC who are on the list? Removing people > From the CC who are on the list might be an enhancement we could do to mailman} I would personally favor doing so. In short, I presume that the sender of the message a given message is in reply to will be on the "to" line, and the working group on the CC line along with a random set of other email addresses, any of which can be edited out if they are also members o the mailing list. There are two issue that I see: 1) you really want to be sure that any email address removed is on the email list, so that a person is not prevented from receiving the email. If there is another email address is that *not* on the email list, it needs to not be edited away. The objective here is to shorten the CC line, not to exclude people that are presumably interested in the conversation. 2) I'll use this email as an example and discuss a probable issue. It is going to three destinations: mcr+ietf@sandelman.ca, wjhns1@hardakers.net, and wgchairs@ietf.org. The third will presumably be edited as suggested, because it's going through mailman; the other two will not, because they are not. BTW, if I had one or more BCC'd addresses, they would also not pass through mailman. If I have that right (I think I do, but I guarantee that there is some email program that will surprise me), the majority of the folks on the list will see the first (the "to") address and third address (the working group), but not Wes's address, but you will see Wes's email address (and Wes will see yours) in addition to the working group address. When you reply, it will get edited, but the messages you and I see will not because we will send them to each other directly. So the behavior of the system will be correct in the sense that each addressed party will receive the email, but it may not be intuitive.
- WG meeting structure Pete Resnick
- Re: WG meeting structure Joel M. Halpern
- Re: WG meeting structure Stephen Farrell
- Re: WG meeting structure Fred Baker
- Re: WG meeting structure Pete Resnick
- Re: WG meeting structure Michael Richardson
- Re: WG meeting structure Michael Richardson
- Re: WG meeting structure Bob Hinden
- Re: WG meeting structure Martin Thomson
- Re: WG meeting structure Kyle Rose
- Re: WG meeting structure Aaron Falk
- Re: WG meeting structure Kyle Rose
- Re: WG meeting structure Toerless Eckert
- Re: WG meeting structure Ole Troan
- Re: WG meeting structure Fred Baker
- Re: WG meeting structure Fred Baker
- RE: WG meeting structure Valery Smyslov
- Re: WG meeting structure Gorry Fairhurst
- Re: WG meeting structure Lars Eggert
- RE: WG meeting structure Ciavaglia, Laurent (Nokia - FR/Paris-Saclay)
- Re: WG meeting structure Mark Nottingham
- Re: WG meeting structure Russ Housley
- Re: WG meeting structure Ole Troan
- RE: WG meeting structure STARK, BARBARA H
- Re: WG meeting structure Mary Barnes
- Re: WG meeting structure Michael Richardson
- Re: WG meeting structure Andrew G. Malis
- Re: WG meeting structure Andrew G. Malis
- RE: WG meeting structure STARK, BARBARA H
- RE: WG meeting structure Linda Dunbar
- RE: WG meeting structure Black, David
- Re: WG meeting structure Eggert, Lars
- Re: WG meeting structure Michael Richardson
- Re: WG meeting structure Michael Richardson
- Re: WG meeting structure Andrew G. Malis
- Re: WG meeting structure Michael Richardson
- Re: WG meeting structure Michael Richardson
- RE: WG meeting structure Black, David
- Re: WG meeting structure Andrew G. Malis
- Re: WG meeting structure Pete Resnick
- Re: WG meeting structure Michael Richardson
- Re: WG meeting structure Michael Richardson
- Re: WG meeting structure Mary Barnes
- Re: WG meeting structure Mary Barnes
- Re: WG meeting structure Michael Richardson
- Re: WG meeting structure Dave Lawrence
- Re: WG meeting structure Fred Baker
- Re: WG meeting structure Loa Andersson
- Re: WG meeting structure Benjamin Kaduk
- Re: WG meeting structure Loa Andersson
- Re: WG meeting structure Fred Baker
- Re: WG meeting structure Benjamin Kaduk
- Re: WG meeting structure Loa Andersson
- Re: WG meeting structure Wes Hardaker
- Re: WG meeting structure Michael Richardson
- Managing CC List Fred Baker
- Re: WG meeting structure Toerless Eckert
- Re: Managing CC List Michael Richardson
- Re: Managing CC List Mary Barnes