IETF Logo Mail Archive

Re: [BEHAVE] RFC6147 and RFC7208 interoperability issues

Keith Moore <moore@network-heretics.com> Mon, 07 February 2022 17:02 UTC

Return-Path: <moore@network-heretics.com>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD69D3A0E08 for <behave@ietfa.amsl.com>; Mon, 7 Feb 2022 09:02:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.612
X-Spam-Level:
X-Spam-Status: No, score=-2.612 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.714, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
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 SxFtAy0BRSbm for <behave@ietfa.amsl.com>; Mon, 7 Feb 2022 09:02:00 -0800 (PST)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B62A3A0DFE for <behave@ietf.org>; Mon, 7 Feb 2022 09:01:58 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 66C9032020DA for <behave@ietf.org>; Mon, 7 Feb 2022 12:01:56 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 07 Feb 2022 12:01:56 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=PtZzeiHkDvyW9wm51OaM6BC9ydjb8Tyek1jgEOiaMFE=; b=ZPbND1eb joSEe6ztGZm8oAo7ZBo0FTb7E9YkWhmCaalBos1g2+8dpQFrMNDiFpgH/KP5ZIBe 3PJrVzNAC0845597QCnKBc6OSHM3+Bvjsq5/hIcInyr5DZU9qnZpPhjG21gi911c HBF+8UjVia0qBMvLAjb7ttXRwPzRL1jL+YmTctq34JL74lkj2d8WpzPtPQTjZTCp BmHOOJgoFED9uERjY5naC4b0cZlLzzz1UC40pkOvbA3VzZrS2j71YGmfGnh7S96e Hn4JwoF/6tzBvBztFu3tsbjE1HXOFtKdR//M7cavZbdPZK1EjGG1EEC5eHG3yAGG TEnQQcIZ8xv1OQ==
X-ME-Sender: <xms:glABYq6sE7d7T5AVP2KVqHW778-bmbAtutqSRLFWbj1NtXC3AjN8dw> <xme:glABYj724vzUB9EpIrUz2oWWAshAG3JT0aDiPaWHlYJ660Xe9fQVNiVLdLfiim7Bf nyDdsdEP6R0cw>
X-ME-Received: <xmr:glABYpfkZlLOxhIUNYdDl2muarZ007Ow-74Qq7grYjIIm8axAW_ezFqHbR1Laz3VL2ldALqPYxQL5o2TryPnj64Hm5pRbqE3gUxB>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrheehgdelfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesthekre dttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhepfedtvdelieejve ekjefhueduheeviefhjeefvdfgudfhfffhudduudefgefgteevnecuvehluhhsthgvrhfu ihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhoohhrvgesnhgvthifohhrkh dqhhgvrhgvthhitghsrdgtohhm
X-ME-Proxy: <xmx:g1ABYnJqRnm8GV8rGUk6xUs4p_aFczxfHg4jEgoiHtdfKOHMf0K8tA> <xmx:g1ABYuKC-R-z5gDKnXi-thCsCaVoBTR5UYz_rxzac_pGjqEG7jgs5w> <xmx:g1ABYoxiEu7AqHhSuTAea1sTf90DqJ0pnmWuiTnNR2hSpodaG69_Zw> <xmx:g1ABYjW_P2VRnM7q8gOCZpcihhQL99vx9i2Qyf6ppiv43WSdDp8sHw>
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <behave@ietf.org>; Mon, 7 Feb 2022 12:01:54 -0500 (EST)
Message-ID: <3ff58733-ccd5-fe15-8b06-dd69bfad0c74@network-heretics.com>
Date: Mon, 07 Feb 2022 12:01:53 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
Content-Language: en-US
To: behave@ietf.org
References: <077D662F-5E6D-44F5-8DD3-B58D8B535C5D@network-heretics.com> <B6D6B4CC-AC1F-459C-952A-E9493E00FDB3@huitema.net> <7e53925e-46b0-29e4-6deb-47bcf389ff97@posteo.de>
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <7e53925e-46b0-29e4-6deb-47bcf389ff97@posteo.de>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/behave/YawQgNi5uD4GFqvmYNClobMp5a0>
Subject: Re: [BEHAVE] RFC6147 and RFC7208 interoperability issues
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/behave/>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Feb 2022 17:02:05 -0000

On 2/7/22 11:38, Klaus Frank wrote:

> I was hoping for clarification and an alignment between both working 
> groups (and maybe an official recommendation i.e. Informational RFC) 
> and to find a solution for the future. So that this problem doesn't 
> stay unresolved. 

There is no possible solution to the NAT problem, except to not use 
NATs.   The problems will never be resolved because Internet 
applications are not static.

Keith

v2.23.0 | Report a Bug | By Email