Re: IETF network incremental plan

Randy Bush <randy@psg.com> Thu, 17 November 2016 00:16 UTC

Return-Path: <randy@psg.com>
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 ADFAC129478 for <ietf@ietfa.amsl.com>; Wed, 16 Nov 2016 16:16:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.398
X-Spam-Level:
X-Spam-Status: No, score=-8.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.497, 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 dJCs3aLrjRSb for <ietf@ietfa.amsl.com>; Wed, 16 Nov 2016 16:16:46 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA7C5126579 for <ietf@ietf.org>; Wed, 16 Nov 2016 16:16:46 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1c7ANg-0003LE-I8; Thu, 17 Nov 2016 00:16:44 +0000
Date: Thu, 17 Nov 2016 09:16:43 +0900
Message-ID: <m2zikzq7tg.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Jordi Palet Martinez <jordi.palet@consulintel.es>
Subject: Re: IETF network incremental plan
In-Reply-To: <0C5BCD32-2D2A-42B9-8DEA-A1E1A527A8BB@consulintel.es>
References: <0C5BCD32-2D2A-42B9-8DEA-A1E1A527A8BB@consulintel.es>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zvPRwVtq3ap48t-N2f49djChqSo>
Cc: IETF discussion list <ietf@ietf.org>
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 00:16:48 -0000

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