IETF Logo Mail Archive

Re: [calsify] ReplyTo with HTTP (for development)

Neil Jenkins <neilj@fastmailteam.com> Mon, 28 May 2018 04:47 UTC

Return-Path: <neilj@fastmailteam.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5860612D7F1 for <calsify@ietfa.amsl.com>; Sun, 27 May 2018 21:47:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.983
X-Spam-Level:
X-Spam-Status: No, score=-1.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_HEADER_CTYPE_ONLY=0.717, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=ro1CcEj7; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=CKYqoPdM
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 Z5AxIUCGvcVx for <calsify@ietfa.amsl.com>; Sun, 27 May 2018 21:47:17 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9D791273E2 for <calsify@ietf.org>; Sun, 27 May 2018 21:47:16 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 3511C21A47 for <calsify@ietf.org>; Mon, 28 May 2018 00:47:16 -0400 (EDT)
Received: from imap22 ([10.202.2.72]) by compute6.internal (MEProxy); Mon, 28 May 2018 00:47:16 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=content-type:date:from:in-reply-to :message-id:references:subject:to:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=rhjaZ8PzU+RIEPcJOh6vNDPJWA82cchoRfzSSk9va aw=; b=ro1CcEj7mqDeZNysBC1rMY5tzqkPVTlO+nWE/nLr+IPGCVLysrFeWeaLy 9m0rWXe3z+Y/3rRIiSlMbn1qVi6kaA83tX76v19L3sBKYkW34VVRfgg9RWY3pCNU CUr0izyVyEowjFZVoK0I6e50LX9vJ884VhiSGFtGfkYe3OvryPL/GYq24H3dhrxc 3g6I+blF/EWKsI3EH1coNdtdySH42n7YRjZfYqbbtoGtiFjWqR631YD+ART8U5Gy JmOrv13ggoZc44BWgS8yYryJRjvazqo3Wat8FpJzEvhqcddkoXRYjlQ6yuNJmF23 W9hWFJN2kKDLJlrMLsoMtxQ1Ext0Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:references:subject:to:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=rhjaZ8PzU+RIEPcJOh6vNDPJWA82cchoRfzSSk9va aw=; b=CKYqoPdMU2BNP4rReSqnKvgAGBmvOFeNGgMTT759HQPrlGD9JbJ2UAsf8 O7VDe0mEAp1lFhiC9jwcrOXcDXTSNGFuzLxvLHgFSGIKuYYmTe/4oRXK/SgewAuS XO4zEKiYmD2pA/kmcf+xRH2doOWIwBFcdfP+dwNKS4J3fpFSxF2D3dShzb4K3o2+ 21Sseb3g7HwcmAoTJnnC5fCyZfSsL+Gdi9ieIPyq4Q2AZt8YK6bhg/ZWuKVpecCf Iwizjo9NhD4equhf26rWuetNqEDJTHyhGjIOE+8yuYDhkyQinC+NFbfYo6PFzVkX 56icOrjCNAtVRTUQHXkX4YL28H+WQ==
X-ME-Proxy: <xmx:04kLW9AcptDanNRw8Ki0spXMiZHM_A0aUhj4Nf1GsK2axjnpGsDqcQ>
X-ME-Proxy: <xmx:04kLWy8cL7a34C2ujovlLjayLevagbEHn0I8hKGq9saHDtmL-baVXA>
X-ME-Proxy: <xmx:04kLW19CM9fUWRRJlKeTCCRufc4qK_5brtgzUEvVGdd3DKjyW96VWw>
X-ME-Proxy: <xmx:04kLWxcg0ygswlqXjGdM13zEVNzaFMrC1McZMuzQpUJFkwPdUSlk6A>
X-ME-Proxy: <xmx:04kLW2HPTgKtBZW-HCskWaPdnPXCDppzFBibpcgjTFPt03NCWOA8YA>
X-ME-Proxy: <xmx:1IkLW4W26hE5dGxHspnc0amEq29WGQPxQNKJddLFzyuDlFOLXNc_wA>
X-ME-Sender: <xms:04kLW3N2iv1QaBcNY0S2ZbYY2DL2gn5oaLCo9yCOAdWPRj-pXJdkwg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id AFCC0CA2B7; Mon, 28 May 2018 00:47:15 -0400 (EDT)
Message-Id: <00372112-6ab0-4076-a421-6f30f7fe94df@sloti22d1t06>
User-Agent: Cyrus-JMAP/3.1.3-624-g558ee02-next
x-jmap-identity-id: 64588216
In-Reply-To: <4e5fbfb3-3b6d-954c-9fb7-1fea100c400d@dot.ee>
References: <4e5fbfb3-3b6d-954c-9fb7-1fea100c400d@dot.ee>
Date: Mon, 28 May 2018 00:47:15 -0400
From: Neil Jenkins <neilj@fastmailteam.com>
To: calsify@ietf.org
Content-Type: multipart/alternative; boundary="55d9c2b53a7b4ad194dbadf183b1ede3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/RdLm2EfbjfByIA-tRCbkeO2l2xw>
Subject: Re: [calsify] ReplyTo with HTTP (for development)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 May 2018 04:47:19 -0000

On Fri, 25 May 2018, at 8:44 PM, Andri Möll wrote:
I'm all for strongly suggesting HTTPS for public Internet use, but during development I must say HTTPS is a pain in the ass. I, like a lot of other people, develop and test locally using either .local (if devices support zero conf) or a private domain in the likes of .dev or .test set up in the router.

Following the standard is required if you wish to interoperate. For when you are operating entirely within a closed system (develop + test) you can of course ignore any requirements you like.

Having said that, I'm personally ambivalent to whether it's a MUST or a SHOULD, or a "make sure you really think about this". My view is any decent service is only going to use HTTPS anyway, any shoddy service probably won't read the RFC, and anyone doing some internal thing with its own encryption layer will probably ignore it if they want to anyway. Shrug.

Neil.

v2.23.0 | Report a Bug | By Email