[IPsec] draft-ietf-ipsecme-ipv6-ipv4-codes-02
Michael Richardson <mcr+ietf@sandelman.ca> Mon, 15 April 2019 01:19 UTC
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2748712031B for <ipsec@ietfa.amsl.com>; Sun, 14 Apr 2019 18:19:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 nzh1RxRyxWi4 for <ipsec@ietfa.amsl.com>; Sun, 14 Apr 2019 18:19:43 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 327F2120072 for <ipsec@ietf.org>; Sun, 14 Apr 2019 18:19:42 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 8BBBB380BE for <ipsec@ietf.org>; Sun, 14 Apr 2019 21:19:37 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 0FFA0C07; Sun, 14 Apr 2019 21:19:40 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 0D981BF6 for <ipsec@ietf.org>; Sun, 14 Apr 2019 21:19:40 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ipsec@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Sun, 14 Apr 2019 21:19:40 -0400
Message-ID: <29234.1555291180@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/pmX7U-2nidB2cBQk9z1n2ZhjeQs>
Subject: [IPsec] draft-ietf-ipsecme-ipv6-ipv4-codes-02
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Apr 2019 01:19:45 -0000
I read this document. It seems pretty straightforward, the reasoning makes sense. I think that it might be useful for privacy VPNs as well. -- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
- [IPsec] draft-ietf-ipsecme-ipv6-ipv4-codes-02 Michael Richardson