Re: [arch-d] Mail Etiquette

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 10 April 2020 20:32 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D04C73A0CCA for <architecture-discuss@ietfa.amsl.com>; Fri, 10 Apr 2020 13:32:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 jydtPHFXanfE for <architecture-discuss@ietfa.amsl.com>; Fri, 10 Apr 2020 13:32:29 -0700 (PDT)
Received: from mail-pf1-x436.google.com (mail-pf1-x436.google.com [IPv6:2607:f8b0:4864:20::436]) (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 92CE43A0CD1 for <architecture-discuss@ietf.org>; Fri, 10 Apr 2020 13:32:29 -0700 (PDT)
Received: by mail-pf1-x436.google.com with SMTP id a13so1499331pfa.2 for <architecture-discuss@ietf.org>; Fri, 10 Apr 2020 13:32:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=30EUhWoOP91z/ovejx9kFUEPTd6HASP2xFCVLdE/8kY=; b=Qfe+MAAJereQVH9jVfrnFiFVdJlBXNaA6BOzsF/CeK9rArqb/0z/1AHd642xld2+Sm PzphHWEfJVAjEydfHeZWQAH67VorR0YBY5BCcuNJqfqY9xI1AfwO1aTgMPJghOyVDjTQ 9Z3o/JOXAKOyTr1VCTYIjYSBXZbNZl4bVmw6Oo7or2MsDhh38woTegWaRGluk59yK6y1 FmKijZ+X5xy/vC5yWl66O68RJJrNINpODfWx/ZOznASrfRdr/Wh08YqBhFJdSRlJLcAD xsl1nSi4vdiXBoKH/MErQ2rqQB+5lQuNbASuOjKeXIT0F9ej0QuTphmJYmmiIVtIL4J2 TR1A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=30EUhWoOP91z/ovejx9kFUEPTd6HASP2xFCVLdE/8kY=; b=c3qa8I3PhnIOAts7x2MVXUp4K2gkQ6C+jM5Fm2WD/Tc2n5Z7Y8ECqqZ9eFxH3RGJYd H47bQIDbQ+m1KTr+KaQNsTKEKBYyywntRxVa/jgw0uZcNLKAoJPRy1RIimT5n8wm5oxg FnkO1YyZeelgA8QaV7c05eEEFaq1yOWEvZJAFCDmAtOCPmv60v23Y6zS8DgPrRsBSIdN sIhhu5hcr8/S2au7PAZj3x2xzmhskRx1fbLm8t+/nYsPoBDB4c0Cvg1V62bA3MpIY9Lh BajZpOA7e7stWzGayzkrTwtg/3IOjgiK5iN7/bLteiV73n9BgClvXs59MJDoCGPmGdYZ Ix+A==
X-Gm-Message-State: AGi0PuY3QuVcuQaMQ2EyXTYDS9b80yejcWxcgzP7TTJmLg3Lvio2tBb/ auzmDj5fqBcFNZv4fl5RNtX4u82k
X-Google-Smtp-Source: APiQypJlPL6PILIM4Uv4399/leVQla14kdvaTCambgEVfsyR0XMX0uOS43WjGEqC06Z9/VS0M5+r+w==
X-Received: by 2002:a62:3888:: with SMTP id f130mr6475108pfa.141.1586550748535; Fri, 10 Apr 2020 13:32:28 -0700 (PDT)
Received: from [192.168.178.30] ([165.84.25.143]) by smtp.gmail.com with ESMTPSA id d23sm2470819pfq.210.2020.04.10.13.32.26 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Apr 2020 13:32:28 -0700 (PDT)
To: John C Klensin <john-ietf@jck.com>, Vincent Truchseß <ietf-arch@v-tr.org>, architecture-discuss@ietf.org
References: <98d43782-6543-b473-6a3c-dc6fe0e4de7d@v-tr.org> <869472A7-EF3E-4CC2-8ACE-0196E8B10504@puck.nether.net> <688f5250-c8f6-765b-a51a-b931b76e6d65@v-tr.org> <E0937C078B7EE9C511ACE650@PSB>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <563a6f12-e1fe-b64d-4b4d-c52958807c1a@gmail.com>
Date: Sat, 11 Apr 2020 08:32:23 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <E0937C078B7EE9C511ACE650@PSB>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/TKAu85Bn_YeGLQ568BAS4thtzlk>
Subject: Re: [arch-d] Mail Etiquette
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2020 20:32:31 -0000

Vincent,

I tend to use Reply All by default to avoid interested recipients
being missed. A lot of IETF discussions end up cross-posted to
multiple WGs or even being switched to a different WG, so those
extra CCs can be important.

There's a catch in Reply All though: if you forget to delete
(say) ietf-announce@ietf.org, that's a guaranteed annoying bounce
message.

With mailman lists, you can suppress duplicates in your personal
config, with the "Avoid duplicate copies of messages?" option:

"When you are listed explicitly in the To: or Cc: headers of a list message, you can opt to not receive another copy from the mailing list. Select Yes to avoid receiving copies from the mailing list; select No to receive copies." 

There's also the "Receive your own posts to the list?" option.

On 11-Apr-20 05:16, John C Klensin wrote:
...
> That said, the reality is that different of us follow different
> conventions, sometimes not even being consistent about that on a
> given day.  You will see the same thing with decisions as to
> whether to write responses inline with a copy of the original
> message or to make one's comments at the top.   There is no
> fixed rule and people seem to do what they thing best and
> everyone just learns to cope.

Indeed. Wrapped text or hard returns? With hard returns, line
length? Worst of all, HTML instead of text/plain. Sometimes,
not even charset=utf-8. Different quoting and commenting methods;
some people even rely on colour (which they probably spell "color").

It would be a brave person who tried to write down the best practice.

> welcome to the IETF.

+1

Stay well,
     Brian