IETF Logo Mail Archive

Re: [Netrqmts] IETF 105 Minutes

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 31 July 2019 18:27 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: netrqmts@ietfa.amsl.com
Delivered-To: netrqmts@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3948A1206E7 for <netrqmts@ietfa.amsl.com>; Wed, 31 Jul 2019 11:27:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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 BvsYd1dkPQbC for <netrqmts@ietfa.amsl.com>; Wed, 31 Jul 2019 11:27:32 -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 866E71206F7 for <netrqmts@ietf.org>; Wed, 31 Jul 2019 11:27:32 -0700 (PDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id E0941380BE; Wed, 31 Jul 2019 14:27:04 -0400 (EDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id EE22B205; Wed, 31 Jul 2019 14:27:30 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Toerless Eckert <tte@cs.fau.de>, netrqmts@ietf.org
References: <DF3803B7-C05B-4A31-B873-73A86B1416CE@vigilsec.com> <19915.1564514403@localhost> <20190730202439.zl6gjvzasxofvej2@faui48f.informatik.uni-erlangen.de> <27837.1564524525@localhost>
Message-ID: <67849904-0195-d913-f4f5-3ce068039b71@sandelman.ca>
Date: Wed, 31 Jul 2019 14:27:30 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <27837.1564524525@localhost>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netrqmts/ONtJCnJfZE_m6lAP-LTkD2Lohn4>
Subject: Re: [Netrqmts] IETF 105 Minutes
X-BeenThere: netrqmts@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Meeting Network Requirements <netrqmts.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netrqmts>, <mailto:netrqmts-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netrqmts/>
List-Post: <mailto:netrqmts@ietf.org>
List-Help: <mailto:netrqmts-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netrqmts>, <mailto:netrqmts-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jul 2019 18:27:42 -0000

On 2019-07-30 6:08 p.m., Michael Richardson wrote:
>      > all those users not working at the network level. I also think that
>      > folks who want to test if their applications work well and invested
>      > into ICE/STUN and other firewall traversal mechanisms (like RTCweb and
>      > other app groups), would maybe like to have something more reflective
>      > of relevant end-user access (with firewall).
> 
> A $22 home router fixes that problem.

Actually, I realized in the shower this morning, that the ietf-nat64 
network provides all the "security" of a home router, in that TCP SYN 
packets leave, but can never enter.

v2.23.0 | Report a Bug | By Email