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

Gert Doering <gert@space.net> Sat, 16 May 2015 21:18 UTC

Return-Path: <gert@Space.Net>
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 B2DD31A8757 for <v6ops@ietfa.amsl.com>; Sat, 16 May 2015 14:18:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.711
X-Spam-Level:
X-Spam-Status: No, score=-0.711 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 6sDb1-sGZg_S for <v6ops@ietfa.amsl.com>; Sat, 16 May 2015 14:18:44 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF0551A1AAA for <v6ops@ietf.org>; Sat, 16 May 2015 14:18:43 -0700 (PDT)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 2156B609A7 for <v6ops@ietf.org>; Sat, 16 May 2015 23:18:41 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id D7E2260760 for <v6ops@ietf.org>; Sat, 16 May 2015 23:18:40 +0200 (CEST)
Received: (qmail 23508 invoked by uid 1007); 16 May 2015 23:18:40 +0200
Date: Sat, 16 May 2015 23:18:40 +0200
From: Gert Doering <gert@space.net>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
Message-ID: <20150516211840.GJ54385@Space.Net>
References: <20150515113728.GH3028@ernw.de> <878002773.794.1431739346723.JavaMail.yahoo@mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <878002773.794.1431739346723.JavaMail.yahoo@mail.yahoo.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/mrWXPh2LcjqwktSSekV3ZCjSa-I>
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: Sat, 16 May 2015 21:18:45 -0000

Hi,

On Sat, May 16, 2015 at 01:22:26AM +0000, Mark ZZZ Smith wrote:
> So quickly, how have IPv4 options been handled? 
> They too can vary the location of the TCP/UDP etc. headers in an IPv4 packet. 

"Drop packets with IP options".

> How have the variety and variable number of TCP options been handled? They 
> too can vary the location of the TCP segment payload.

But they do not move the location of the TCP port info.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279