IETF Logo Mail Archive

Re: [v6ops] Extension Headers / Impact on Security Devices

Joe Touch <touch@isi.edu> Fri, 29 May 2015 20:24 UTC

Return-Path: <touch@isi.edu>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F60E1B2CFB for <v6ops@ietfa.amsl.com>; Fri, 29 May 2015 13:24:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 S_j4v0F42Lhu for <v6ops@ietfa.amsl.com>; Fri, 29 May 2015 13:24:04 -0700 (PDT)
Received: from webspace.isi.edu (webspace.isi.edu [128.9.64.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BEB31B2CEF for <v6ops@ietf.org>; Fri, 29 May 2015 13:24:04 -0700 (PDT)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id t4TKNQqB018558 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 29 May 2015 13:23:26 -0700 (PDT)
Message-ID: <5568CABD.1030900@isi.edu>
Date: Fri, 29 May 2015 13:23:25 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>
References: <555AB8FA.2080405@si6networks.com> <F6AA9AEA-49F0-488C-84EA-50BE103987C8@nominum.com> <555B8622.5000806@isi.edu> <555BA184.8080701@gmail.com> <555BA43F.8010303@isi.edu> <5564FB74.5020303@gmail.com> <5564FE3F.4050102@isi.edu> <556503CF.4030101@gmail.com> <55650821.4060907@isi.edu> <55650E82.3090407@gmail.com> <20150527073943.GA54385@Space.Net> <5565FDB1.2070307@isi.edu> <47D28817-A778-4F1C-99E9-2EEBAA39F5B6@cisco.com>
In-Reply-To: <47D28817-A778-4F1C-99E9-2EEBAA39F5B6@cisco.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/tvTvAIEnzUWfUJ-CQ-TCW5QCz3g>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] Extension Headers / Impact on Security Devices
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 May 2015 20:24:05 -0000


On 5/29/2015 12:39 PM, Fred Baker (fred) wrote:
> 
>> On May 27, 2015, at 10:24 AM, Joe Touch <touch@isi.edu> wrote:
>>
>> So I would think that they MUST NOT be added to IPv6 datagrams except by
>> the source.
> 
> You might consider commenting in Spring, then. They are designed as
> something that would be added in, and potentially removed again in, the
> network. They are something the ultimate source and destination need
> never see.

As I also noted, adding things "on behalf of" the source is equivalent.

If these are things the source never sees and used only on the path,
then they are *by definition* HBH options and should be indicated as such.

Joe

v2.23.0 | Report a Bug | By Email