Re: Mirja Kühlewind's Discuss on draft-ietf-6man-rfc2460bis-09: (with DISCUSS and COMMENT)

otroan@employees.org Fri, 21 April 2017 19:38 UTC

Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BB4712441E; Fri, 21 Apr 2017 12:38:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
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 ywQ9goqK_zj0; Fri, 21 Apr 2017 12:38:41 -0700 (PDT)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 3547012706D; Fri, 21 Apr 2017 12:38:41 -0700 (PDT)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 21 Apr 2017 19:38:41 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id B1B43D788D; Fri, 21 Apr 2017 12:38:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=me/0/gP7owSWHZYUJPm6cQi8sIE=; b= sqskOjhQVafVI3Cw2Hv32cwIYRD29xjOgOKcJ/bTertLHKx2pHe9NH9Rui8R1Psx odfOiFWEweZvstfcFKWMV3fd4QhZ8Ks9xd2iKv+1U9kUOaj4EM7PpPafMDjvTuTw zMeNzhFawG6cF4u5L9bY68VyWSkJBLRfxuOSjgjHhFw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=asC8TUqHMwlZzsNZcwoA1Td sg+2D7bom+jo2VzJHPL2jw6O4r2C5aNP5yFDsKylnPzabUCa7Fw71KPfzNz92nzZ bwqjncT7iqdFVD2jjiOoJ5uTBBHOfRLpJ2O4Bp0hlX5tkDaEZxtGyz0w7Ejqqfx8 8kO6/ocZSEuQtZ5ZyH+4=
Received: from h.hanazo.no (77.16.72.83.tmi.telenormobil.no [77.16.72.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id BEF43D788B; Fri, 21 Apr 2017 12:38:39 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id D2EF2AE2A598; Fri, 21 Apr 2017 21:38:36 +0200 (CEST)
From: otroan@employees.org
Message-Id: <E2595B09-575D-49AE-92B2-0064B82772F9@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_090D3BD8-D1D2-4138-A2D4-31D5C2A1EA0D"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Mirja Kühlewind's Discuss on draft-ietf-6man-rfc2460bis-09: (with DISCUSS and COMMENT)
Date: Fri, 21 Apr 2017 21:38:36 +0200
In-Reply-To: <CA+b+ERkHjv=w8g1R4LDVB-+kD=dVCVgtVu_D53oAqkOPFAzDkQ@mail.gmail.com>
Cc: Fernando Gont <fgont@si6networks.com>, draft-ietf-6man-rfc2460bis@ietf.org, 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, Suresh Krishnan <suresh.krishnan@gmail.com>, "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>, IESG <iesg@ietf.org>, 6man-chairs@ietf.org
To: Robert Raszuk <robert@raszuk.net>
References: <149201127005.15808.3277140025315157500.idtracker@ietfa.amsl.com> <248F8BA5-48D6-4933-B45F-7F1B20477C2C@employees.org> <3C06A5F9-19B9-48E1-BB67-57D540E5E38D@kuehlewind.net> <A5628A89-3830-4851-87F1-AE8329597DAE@gmail.com> <58B249A0-2F0B-4AD6-890D-BB0F0594DEE1@kuehlewind.net> <0c7d3a7b-99c9-dbef-d6cc-9a4a94cb9c9f@gmail.com> <4AE56E75-78D4-43EA-8118-8195FD8A3D08@kuehlewind.net> <4fc2ef36-cd17-58f1-8089-a5645f08ad45@gmail.com> <D7EE44C3-04DB-4CFD-836F-2BFA74A35268@employees.org> <90DFC565-B4E7-45E2-BE6A-0B67895E87F8@gmail.com> <CA+MHpBr7aeuyd8h5n6U6Q4jD_gtLCKsPJUgQqQuhgkEE3DGwqg@mail.gmail.com> <D41A10C3-74D4-45EE-8161-C344CB30329A@kuehlewind.net> <5E28EF66-7BE1-4F11-88F3-6D928870A9FE@kuehlewind.net> <616cb74d-cc15-6c26-cb1d-612dfcddd353@gmail.com> <99E119A3-4BEA-4EE4-9DC1-7B434CAAE016@kuehlewind.net> <8EF4BCDA-ADB9-4EF4-A873-95CA67C6D7F3@employees.org> <8d127de1-a1b6-8406-c234-192fcbf01ad4@si6networks.com> <65C701D2-A0FF-40E5-B88D-E2E9C7260E02@gmail.com> <f7c19564-ea23-dac4-920c-d05a3c7d0cd9@si6networks.com> <CA+b+ERkHjv=w8g1R4LDVB-+kD=dVCVgtVu_D53oAqkOPFAzDkQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/_Cuht1u-LsqOuitnF_f4BGS02TM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 19:38:42 -0000

Hi Robert,

> > I think this confirms that the current text which recommends against defining new EH is correct.
> 
> Yes. Our best possible outcome is that we get *existing* EHs to *not* be
> filtered. I think it's *extremely* unlikely that one could get new EHs
> to work. So I fully support recommending against the definition of new EHs.
> 
> 
> ​All this means that instead of endorsing deployment of IPv6 you guys are just shutting it down for a lot of customers and networks.
> 
> With no future innovation in transport protocol what will happen is that it is now IPv6 which will be encapsulated in MPLS or IPv4+MPLS and carried over.
> 
> Great progress indeed !
> 
> Cheers,
> R.
> 
> PS.
> 
> Perhaps most folks voting against SRH insertion in any transit node in the Internet or making recommendation against defining any new EHs are just completely detached from real hardware development, P4 programming, flexible packet processors coming as we speak from various vendors etc ... What are you guys using in your networks ? Optimistically assuming that you actually even have real networks to operate.
> 
> It's like an attempt here to make a perfect baloon for any air travel and never add anything to it as it may fall.

This is really not what those changes in 2460bis are intended to do.
Within the context of elevating 2460 to Internet standard, we can't add new features.

That does in no way stop anyone from proposing _new_ work. Of any sort.

Best regards,
Ole