IETF Logo Mail Archive

Re: I-D Action: draft-voyer-6man-extension-header-insertion-00.txt

Fernando Gont <fgont@si6networks.com> Wed, 29 March 2017 21:54 UTC

Return-Path: <fgont@si6networks.com>
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 978851250B8 for <ipv6@ietfa.amsl.com>; Wed, 29 Mar 2017 14:54:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 M2ObxF7Z1M7P for <ipv6@ietfa.amsl.com>; Wed, 29 Mar 2017 14:54:40 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DAC312948E for <ipv6@ietf.org>; Wed, 29 Mar 2017 14:54:39 -0700 (PDT)
Received: from [192.168.178.240] (52D961A6.cm-11-1b.dynamic.ziggo.nl [82.217.97.166]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 9F10980212; Wed, 29 Mar 2017 23:54:37 +0200 (CEST)
Subject: Re: I-D Action: draft-voyer-6man-extension-header-insertion-00.txt
To: Tim Chown <Tim.Chown@jisc.ac.uk>
References: <CACL_3VHhrBbtoqwLF=aY0VP4SYFOg+UPgcDDmq2SzSyQ4G=nSg@mail.gmail.com> <59B02E00-136D-4DDB-8707-F2DA61D4D3EA@jisc.ac.uk> <f2cee2c1-abb3-762f-1156-0307f16ba3b3@si6networks.com> <4F96EC34-4F80-4D4E-8070-44A14CE19493@jisc.ac.uk>
Cc: "C. M. Heard" <heard@pobox.com>, 6man WG <ipv6@ietf.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <a54e9b7b-af96-34b9-6706-af79a84eb043@si6networks.com>
Date: Wed, 29 Mar 2017 23:22:42 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <4F96EC34-4F80-4D4E-8070-44A14CE19493@jisc.ac.uk>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/IuN2zXl8Grh3azmkHXI2-m9RGUQ>
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: Wed, 29 Mar 2017 21:54:43 -0000

On 03/29/2017 11:02 PM, Tim Chown wrote:
>>> 
>>> Well, I think if this document is to be adopted, it should start
>>> by saying clearly why EH “insertion” by encapsulation as per
>>> RFC2460-bis isn’t sufficient in specific scenarios.
>> 
>> As far as I understand, this doc is essentially making an argument 
>> against the decision taken for rfc2460bis.
>> 
>> Since that ship has already sailed, I'm not sure whether it could
>> be adopted "as is".
>> 
>> Rather, it should probably make a case for updating RFCXXXX
>> (whatever number rfc2460bis receives).
> 
> That was my understanding of what has been previously said.
> 
> The draft would need (as Mark also said in another thread) explain
> why encapsulated isn’t sufficient, and then successfully describe how
> direct EH insertion can be done safely in specific conditions.

Agreed. And the text be phrased as an update to RFCXXXX (rfc2460bis),
rather than about the decision that has already been taken for
rfc2460bis. -- Otherwise, the I-D looks like tryig to reopen discussion,
when the ship has already sailed.

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

v2.23.0 | Report a Bug | By Email