Re: [Hipsec] Magnus Westerlund's Discuss on draft-ietf-hip-native-nat-traversal-30: (with DISCUSS and COMMENT)

Jeff Ahrenholz <j.ahrenholz@Tempered.io> Sat, 04 April 2020 22:04 UTC

Return-Path: <j.ahrenholz@Tempered.io>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 881EC3A0D5B; Sat, 4 Apr 2020 15:04:54 -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 pPMHp1sRYqrY; Sat, 4 Apr 2020 15:04:53 -0700 (PDT)
Received: from out.west.exch081.serverdata.net (cas081-co-1.exch081.serverdata.net [199.193.204.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C7053A0D59; Sat, 4 Apr 2020 15:04:53 -0700 (PDT)
Received: from MBX081-W5-CO-2.exch081.serverpod.net (10.224.129.85) by MBX081-W5-CO-1 (10.224.129.84) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sat, 4 Apr 2020 15:04:51 -0700
Received: from MBX081-W5-CO-2.exch081.serverpod.net ([10.224.129.85]) by MBX081-W5-CO-2.exch081.serverpod.net ([10.224.129.85]) with mapi id 15.00.1497.006; Sat, 4 Apr 2020 15:04:51 -0700
From: Jeff Ahrenholz <j.ahrenholz@Tempered.io>
To: Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, Miika Komu <miika.komu@ericsson.com>
CC: "hipsec@ietf.org" <hipsec@ietf.org>, "hip-chairs@ietf.org" <hip-chairs@ietf.org>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, "draft-ietf-hip-native-nat-traversal@ietf.org" <draft-ietf-hip-native-nat-traversal@ietf.org>
Thread-Topic: [Hipsec] Magnus Westerlund's Discuss on draft-ietf-hip-native-nat-traversal-30: (with DISCUSS and COMMENT)
Thread-Index: AQHWCs0QwYJaPNdvAUSdnQZll/PFwg==
Date: Sat, 4 Apr 2020 22:04:51 +0000
Message-ID: <4005590A-2B50-4E8A-9DB4-9C9B6CF43DAE@tempered.io>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [73.254.156.159]
Content-Type: text/plain; charset="utf-8"
Content-ID: <0B04B33D5FF98A468EBF09D44085BB3B@exch081.serverpod.net>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/ISL_b0lpMr9SbY-Gk3L3egdR-Hc>
Subject: Re: [Hipsec] Magnus Westerlund's Discuss on draft-ietf-hip-native-nat-traversal-30: (with DISCUSS and COMMENT)
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hipsec/>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Apr 2020 22:04:55 -0000

>   Has anyone looked at implementing 
>   https://datatracker.ietf.org/doc/draft-ietf-tsvwg-datagram-plpmtud/ (document is
>   in IESG evaluation) style path MTU discovery between the HIP client and the
>   relay? Becasue I think that would be the best to actually run a HIP level path
>   MTU discovery, so that the HIP client can set its MTU to path minus overhead and
>   including any for occasional messages that are required to be included when
>   carrying useful payload. If HIP has a padding option, then I would expect that
>   HIP has everything necessary to implement working probe messages that can used
>   by the above draft. 

Thanks for the pointer to this draft. We haven't looked into it yet but this may be a good solution for our HIP deployments. (We're always doing HIP-over-UDP and often using relaying.)

-Jeff