Re: [IPsec] IPTFS and transport mode.

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 04 May 2020 15:17 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 127E83A0A23 for <ipsec@ietfa.amsl.com>; Mon, 4 May 2020 08:17:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 XqFCch_sw8o7 for <ipsec@ietfa.amsl.com>; Mon, 4 May 2020 08:17:23 -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 496DA3A0A22 for <ipsec@ietf.org>; Mon, 4 May 2020 08:17:20 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 0FA663897B; Mon, 4 May 2020 11:15:21 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 8C6228B6; Mon, 4 May 2020 11:17:18 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Christian Hopps <chopps@chopps.org>
cc: ipsec@ietf.org
In-Reply-To: <91FC4B2D-4190-45A5-B681-705365658999@chopps.org>
References: <sa6sggh8a9d.fsf@chopps.org> <7081.1588525696@localhost> <91FC4B2D-4190-45A5-B681-705365658999@chopps.org>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.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: Mon, 04 May 2020 11:17:18 -0400
Message-ID: <10304.1588605438@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/-muTUC5DbX8CVyTpyFsqV0qY8rg>
Subject: Re: [IPsec] IPTFS and transport mode.
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, 04 May 2020 15:17:26 -0000

Christian Hopps <chopps@chopps.org> wrote:
    > Whether we support generic transport or only a subset of transport
    > configurations (e.g., tunnels) or both, the reasons we make whatever
    > choices we make, and the mechanisms for how to implement TFS with
    > whatever is chosen, is what this new draft would cover. I see this
    > building on top of the TFS tunnel mode draft.

    > The rest of what I put above was really just ideas for what would go in
    > that new draft. My thinking that if we wanted to support a subset of
    > transport mode configurations (e.g., for use with GRE, SRv6, IP-IP,
    > etc) we could specify that by defining a set of restrictions on the
    > user IP headers. I'm not sure if that's what you mean is a hack or not,
    > but I figured if we define it by the restrictions rather than
    > specifically only for GRE it's more broadly useful for little extra
    > cost. In any case the discussion of this and definition is what I think
    > would go well in the context of it's own draft.

I understand you, and I agree with your idea.
I agree with putting it into a different draft, but we might need to clearly
articulate where the extension point is in this draft.
I will have to re-read the document, since it's been awhile since I read it.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-