Re: [art] Alissa Cooper's No Objection on draft-ietf-appsawg-mdn-3798bis-15: (with COMMENT)
Alissa Cooper <alissa@cooperw.in> Wed, 30 November 2016 18:03 UTC
Return-Path: <alissa@cooperw.in>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5905129929; Wed, 30 Nov 2016 10:03:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.821
X-Spam-Level:
X-Spam-Status: No, score=-0.821 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=mpfGjUia; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=BuWNz9Zw
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 kgbSWtWyS16C; Wed, 30 Nov 2016 10:03:07 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B73F61298BF; Wed, 30 Nov 2016 10:03:07 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 31C14205FC; Wed, 30 Nov 2016 13:03:07 -0500 (EST)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Wed, 30 Nov 2016 13:03:07 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=8k2DbAHAejtp9Rg NU6ocbLaKwMM=; b=mpfGjUiaitfewBVgzfF2nJggiQ26zh6HQddD0mQtwKddZEG Fh7ErbQZ2KmRCOD/K7/5obMO1QdPsT0uBVq6xxNGxVswM+26Ixf6BW73wFOJVnWD twzzV9wQUnGOgDXrBpBQkOddGsFGmolw14RR3b5mdWqHzUBkYTA0n7vITuUY=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=8k2DbAHAejtp9RgNU6ocbLaKwMM=; b=BuWNz9ZwsbKirUo0tf7+ Qdj1VoSprEJmcwzyLy7BhQ8dwlgQ85koPR/hk5I67gOiH/tg9UGpNVwa/6xFSqtN sfT0HEdOvDxn94DORfEsPMs6mYw3gB3awyIEzGyJSlVkuADiw0oRNKc/Sl4Fy71f eYGBrW6Y6ewTalOUI83wcFw=
X-ME-Sender: <xms:WxQ_WMAROLoOfe86As9Ch4kheV7FTJXeVosin3uG5OvBME_Dubkhrw>
X-Sasl-enc: T7dgzFAPNjBA5g04huxHsSCZTFesoBfe6ReylC3ocLDf 1480528986
Received: from sjc-alcoop-8819.cisco.com (unknown [128.107.241.181]) by mail.messagingengine.com (Postfix) with ESMTPA id A87397EEF7; Wed, 30 Nov 2016 13:03:05 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <CALaySJJYPS9UonEwsHCjUnAbJw+0BvK3gPpDOnfxwcqnASpTpQ@mail.gmail.com>
Date: Wed, 30 Nov 2016 13:03:04 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <47A9DB1A-CA6E-4C07-B3FE-B31853B3372A@cooperw.in>
References: <148051936421.14054.3370105373759594391.idtracker@ietfa.amsl.com> <CALaySJJYPS9UonEwsHCjUnAbJw+0BvK3gPpDOnfxwcqnASpTpQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/C6D35kqCi8Bw-wp0kvpNBOHtCKs>
Cc: "appsawg-chairs@ietf.org" <appsawg-chairs@ietf.org>, draft-ietf-appsawg-mdn-3798bis@ietf.org, Murray Kucherawy <superuser@gmail.com>, IESG <iesg@ietf.org>, art@ietf.org
Subject: Re: [art] Alissa Cooper's No Objection on draft-ietf-appsawg-mdn-3798bis-15: (with COMMENT)
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2016 18:03:12 -0000
> On Nov 30, 2016, at 11:34 AM, Barry Leiba <barryleiba@computer.org> wrote: > >> = Section 6.2 = >> >> "Disposition mode (Section 3.2.6.1) can leak information about >> recipient's MUA configuration, in particular whether MDNs are >> acknowledged manually or automatically. If this is a concern, MUAs >> can return "manual-action/MDN-sent-manually" disposition mode in >> generated MDNs." >> >> I see why this is here, but doesn't recommending falsifying these fields >> put their integrity in question whenever they are set to manual? I mean, >> why would recipients trust this information if the RFC actually suggests >> sending a field that lies about an MDN being automatically acknowledged? > > This comes from my pushing on the point, and is the only reasonable > mediation we could come up with. Here's the summary of the > discussion: > > - I don't see any use in having this field at all. There's nothing > useful the MDN recipient's mail system can do with it, and it only > serves to expose information about the MDN sender's configuration > unnecessarily. I'd rather see it removed entirely. > > - That said, it's been required from the beginning, so (1) all > existing implementations send it, (2) existing implementations expect > to receive it, and are likely to consider the MDN invalid if it's not > present, and (3) implementations are not expected to be reworked to > match this spec if we should change that now. > > - Because of (2) above, we can't just recommend not sending it. > Further, the field wasn't designed to be extensible, so we can't use > some value such as "unknown" -- that would most likely have the same > effect as in (2), that implementations would consider those to be > invalid MDNs. > > - The only thing that leaves is recommending a "standard" value to > send if you don't want to expose the real information. That value has > to be one of the two defined values, and "manual" is the less bad > option (as opposed to telling the recipient's system that you're > configured to automatically send MDNs). > > - And because of the first bullet above (that there's nothing useful > to be done with this information anyway), lying about it doesn't hurt > anything. > > It's a bad, but usable solution to an unfortunate problem. Got it, thanks for the explanation. Alissa > > Barry
- [art] Alissa Cooper's No Objection on draft-ietf-… Alissa Cooper
- Re: [art] Alissa Cooper's No Objection on draft-i… Barry Leiba
- Re: [art] Alissa Cooper's No Objection on draft-i… Alissa Cooper
- Re: [art] Alissa Cooper's No Objection on draft-i… Alexey Melnikov