Re: [openpgp] Alternative to Base64

Stephen Paul Weber <singpolyma@singpolyma.net> Mon, 18 July 2016 21:09 UTC

Return-Path: <singpolyma@singpolyma.net>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4441C12B049 for <openpgp@ietfa.amsl.com>; Mon, 18 Jul 2016 14:09:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.355
X-Spam-Level:
X-Spam-Status: No, score=-2.355 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=singpolyma.net
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 xULXhwYHp9Cy for <openpgp@ietfa.amsl.com>; Mon, 18 Jul 2016 14:09:42 -0700 (PDT)
Received: from singpolyma.net (singpolyma.net [192.99.233.116]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1EEA12D504 for <openpgp@ietf.org>; Mon, 18 Jul 2016 14:09:41 -0700 (PDT)
Received: from [127.0.0.1] (unknown [69.171.154.34]) by singpolyma.net (Postfix) with ESMTPSA id 9556748607C1; Mon, 18 Jul 2016 21:09:40 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=singpolyma.net; s=iweb; t=1468876180; bh=PvHSx/VCRWfXB8uP24rfcXq+LQIr+NgwH/2YTNkHDao=; h=Date:Subject:From:In-Reply-To:References:To:From; b=c7YGLpbI5dzQm06kQlMtmUEUmFGs/d4Dpb/yp+o3s2EkVj5Pk13R7CAli8H4mFBfA qSLOUGALt91LnL7SWLCC4m5CLn2R3aZ5GowwUTHBoizux9DCCVzvpQkQmo5CccsCLY JhXl59xGEP4PHT4+ldnTIPUjWy6xnVqBIWr5tEMA=
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
X-Mailer: BlackBerry Email (10.3.2.2639)
Message-ID: <20160718210940.5890131.90844.42664@singpolyma.net>
Date: Mon, 18 Jul 2016 16:09:40 -0500
From: Stephen Paul Weber <singpolyma@singpolyma.net>
In-Reply-To: <CAMm+LwgPRSnPrL_AKwwyOsfYRsJ-n6j6gUQ7aCU-=GqAW7D41w@mail.gmail.com>
References: <CAMm+LwgPRSnPrL_AKwwyOsfYRsJ-n6j6gUQ7aCU-=GqAW7D41w@mail.gmail.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>, IETF OpenPGP <openpgp@ietf.org>, Russ Housley <housley@vigilsec.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/6t3EYdf0x9s1TaKhihYFjkv-wwI>
Subject: Re: [openpgp] Alternative to Base64
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2016 21:09:43 -0000

> * Yes alleged 'binary' transport SMTP also sucketh because dimwits insert CRLFs to wrap lines.

But if using PGP/MIME there are already transfer encoding mechanisms to solve this outside of OpenPGP. No need to worry about anything but binary from an OpenPGP-implementor's perspective.