[apps-discuss] Another use case for a per-recipient header field: Opened IESG discussions

Alessandro Vesely <vesely@tana.it> Tue, 30 July 2013 16:33 UTC

Return-Path: <vesely@tana.it>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A55E21E80ED for <apps-discuss@ietfa.amsl.com>; Tue, 30 Jul 2013 09:33:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.719
X-Spam-Level:
X-Spam-Status: No, score=-4.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IKBdxCVPaI-G for <apps-discuss@ietfa.amsl.com>; Tue, 30 Jul 2013 09:33:25 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id C67A411E8230 for <apps-discuss@ietf.org>; Tue, 30 Jul 2013 09:32:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1375201914; bh=ooepsKBYraOaK6LJ+mS0iPpVdtew5xaCO46b6HgwFTI=; l=710; h=Date:From:To; b=OPMSU6ke2/yo/PGjMGRy5DzKCwtZV/1UPiDkuGdBWrN1JyfwjZvUhT8XZeXVjk03w BiYUryF3dnUNb1fHw9GZYsIDdyJ+WQSJFCHStpQlazzFOSLwZvoq808xNZbnsDv4we wSmG6zNT+4e8NS4VWsITSxtO2IcMDiTZZWSfxcuk=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [130.129.21.254] (dhcp-15fe.meeting.ietf.org [130.129.21.254]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLSv1/SSLv3, 256bits, AES256-SHA) by wmail.tana.it with ESMTPSA; Tue, 30 Jul 2013 18:31:54 +0200 id 00000000005DC042.0000000051F7EA7A.00003FD7
Message-ID: <51F7EA73.8030107@tana.it>
Date: Tue, 30 Jul 2013 18:31:47 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: IETF Apps Discuss <apps-discuss@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Subject: [apps-discuss] Another use case for a per-recipient header field: Opened IESG discussions
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jul 2013 16:33:38 -0000

I like that new feature of posting IESG positions CC to the WG mailing
list.  It eases navigation through posts about a given I-D, making ML
archives more complete.

Monday, Pete said it is a matter of waiting ten minutes instead of five
before replying to such posts.  That is often implicit in the header:
Recipients in the "To:" field are expected to reply soon, while those in
"Cc:" may want to think twice.  The only problem is when there are so
many different kinds of recipients that they can hardly be grouped into
two groups (three, if you count Bcc:).  That issue can be solved with a
new header field, similar in syntax to RRVS.  E.g.:

Think-Before-Reply:  apps-discuss@ietf.org; 10 minutes