Re: IETF network incremental plan

Paul Wouters <paul@nohats.ca> Thu, 17 November 2016 01:01 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23B6012952F for <ietf@ietfa.amsl.com>; Wed, 16 Nov 2016 17:01:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.497
X-Spam-Level:
X-Spam-Status: No, score=-3.497 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-1.497] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 8wQM3OZiJkii for <ietf@ietfa.amsl.com>; Wed, 16 Nov 2016 17:01:57 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8DF71294EC for <ietf@ietf.org>; Wed, 16 Nov 2016 17:01:56 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3tK2ry32xTz9G; Thu, 17 Nov 2016 02:01:54 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1479344514; bh=O/4va4Tzn+7rMNFasnrCnCGLctXASmQeY0AyItd0A0g=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=sdpQmcRTUreXgVbmmK5Lw3qa3sS/aGQFDvoDga0bry/FQfu+OTY1JyZgHCMwmq9Ak GPLiiH5Il0KGVky0Te6z9vJQhdbv8AzFKPwrggvNbyh6K+1M2XLm97ogJIILrx9PVN XMblaEvsEhw+tt7nPRMbuhEx427HTCRDK0G1uQ4A=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id kM83qyXPWyzf; Thu, 17 Nov 2016 02:01:50 +0100 (CET)
Received: from bofh.nohats.ca (206-248-139-105.dsl.teksavvy.com [206.248.139.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Thu, 17 Nov 2016 02:01:50 +0100 (CET)
Received: from [31.133.136.30] (unknown [31.133.136.30]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by bofh.nohats.ca (Postfix) with ESMTPSA id 530455C83A; Wed, 16 Nov 2016 20:01:49 -0500 (EST)
DKIM-Filter: OpenDKIM Filter v2.10.3 bofh.nohats.ca 530455C83A
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
Subject: Re: IETF network incremental plan
From: Paul Wouters <paul@nohats.ca>
X-Mailer: iPhone Mail (14A456)
In-Reply-To: <m2zikzq7tg.wl-randy@psg.com>
Date: Thu, 17 Nov 2016 10:01:46 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <6492C4A6-1786-449C-B845-7F3DE0E638E0@nohats.ca>
References: <0C5BCD32-2D2A-42B9-8DEA-A1E1A527A8BB@consulintel.es> <m2zikzq7tg.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5lrwFpXmUsx48ad4V0Sg0IOZOUk>
Cc: IETF discussion list <ietf@ietf.org>, Jordi Palet Martinez <jordi.palet@consulintel.es>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Nov 2016 01:01:58 -0000

I very much like the stable plus experimental network setups we currently do. If possible, please keep doing these.

Paul

Sent from my iPhone

> On Nov 17, 2016, at 09:16, Randy Bush <randy@psg.com> wrote:
> 
> last evening i was carrying a question from the noc team but my position
> in the mic queue was preempted by more important people.
> 
> but essentially, before we make tactical decisions we would like to know
> what the purpose and goal of the meeting network is.
> 
>  o folk just want to get work done, and the net should bloody well work
> 
>  o i want to forward test internet futures: ipv6, auth methods, crypto,
>    ...
> 
>  o i have my own stuff i want to test (which may need inbound sessions)
> 
>  o network?  what network?
> 
> in the nat64 case, are we trying to validate the well-known lists of
> what does not work over nat64, spotify, many vpns, ...?  if it is
> because we think we can modify nat64 to ameliorate the problems, this
> would be brilliant.
> 
> if we know what the goals are, we should be able to meet them.  so far,
> the assumption is that
> 
>  o the primary goal of the meeting netowrk is for attendees to get work
>    done
> 
>  o nats breaking applications and inbound connections would be
>    considered as breakage
> 
>  o we do want to support occasional experiments, both non-disruptive
>    and visible (remember the v6-only plenary?)
> 
>  o but basically, i just want my mtv
> 
> randy, not speaking for anyone else