Re: Next steps on Extension Header Insertion

otroan@employees.org Thu, 03 November 2016 10:30 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 13FDF129951 for <ipv6@ietfa.amsl.com>; Thu, 3 Nov 2016 03:30:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.962
X-Spam-Level: *
X-Spam-Status: No, score=1.962 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_SORBS_WEB=3.297, SPF_SOFTFAIL=0.665] autolearn=no 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 Hww3KTgRwSEt for <ipv6@ietfa.amsl.com>; Thu, 3 Nov 2016 03:30:44 -0700 (PDT)
Received: from inbound03.kjsl.com (inbound03.kjsl.com [IPv6:2001:1868:a100:131::62]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89C9C1298C0 for <ipv6@ietf.org>; Thu, 3 Nov 2016 03:30:43 -0700 (PDT)
Received: from cowbell.employees.org ([65.50.211.142]) by ironport03.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Nov 2016 10:30:42 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 555D49CC51; Thu, 3 Nov 2016 03:30:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=ha0+LZgPy1UsxPcZRqxR9epKl88=; b=RTXQoIcVElwx8WF5U6 wLob82LiGo6RdT/hzejWoGfOMNTHiSiOre6p6nMzZJkGcJl/azPDLYxOR+1l3Xfs r5nJ/ulgk/nydEUHCPcyJJi5u4uC+KS7Og8UZKKke0AW9qYGjK0jVOAYTLUHNkdz lERgFc2Chu0wKFDz7z6rBwmVk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=Gh9wOcDwrsq7Si5f+Va8kPa9/WnkGqJMuSpz3iFw4j0Iv1vzy/7 bLdXyhztKXGT+1ObMcti2OIVmJ+3gSMRQl0P6ovcGjwDslG41y1GPHlEZ3d2/y/m kjJ+GVKJgvH3TE4of5gDcLSr5KHiQ++dIm1UmwDJpGIz/UkCt8dvlR8U=
Received: from h.hanazo.no (unknown [85.19.205.27]) (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 192899CC4F; Thu, 3 Nov 2016 03:30:42 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id EF8485935B6C; Thu, 3 Nov 2016 11:30:38 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\))
Subject: Re: Next steps on Extension Header Insertion
From: otroan@employees.org
In-Reply-To: <7BB6DFAA-7E32-4E84-AC3D-5B1F89AEBFB9@jisc.ac.uk>
Date: Thu, 03 Nov 2016 11:30:38 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2BF05215-347F-4AFA-B21D-D0F558F58F07@employees.org>
References: <B291E9E6-A803-423F-BFA5-87A74DCFB784@gmail.com> <dfe00826-1bcd-80ae-e6dc-7763c506cbe4@si6networks.com> <9CA73891-B4FA-47DF-82E1-A4867DBC6A3F@steffann.nl> <3C56AA77-18E4-4254-BB6A-A447CE115392@employees.org> <CAG6TeAtJdUua3saSGz0SX7DW6hwf74yAexpnfYoP1bg6v1eywA@mail.gmail.com> <EF8FE087-C84F-44C0-9769-72106115BDA9@employees.org> <7BB6DFAA-7E32-4E84-AC3D-5B1F89AEBFB9@jisc.ac.uk>
To: Tim Chown <Tim.Chown@jisc.ac.uk>
X-Mailer: Apple Mail (2.3251)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Y1uTSgs8fDqLRNBo7sGpVRpm6W4>
Cc: Fernando Gont <fgont@si6networks.com>, 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 03 Nov 2016 10:30:46 -0000

>>> I'd say that some of the options given in the poll are rather misleading... Because truth is that as of today, header insertion is not allowed. So any discussion about "preferred way of doing eh insertion" seems like an implicit update/"relax of the spec" to me.
>> 
>> I fully agree with you on the architectural principles. I also think the Internet should be end to end transparent and that firewalls, NATs and other middleboxes have no place in the Internet architecture. _That_ political statement isn't for the core IPv6 _protocol specification_ though.
> 
> It’s not a political statement though, it’s about allowable behaviour, which is what a specification determines.  At the moment there’s a widely held assumption of behaviour X, but a number of people are wanting to introduce behaviour Y (though I’m not aware of a WG ID that actually documents that?)

Indeed, and since no-one has proposed to do this (in a draft) makes it very fuzzy what we're arguing against (or for).
We're arguing about an imagined treat. ;-)

Best regards,
Ole