Re: [v6ops] why IPv6 EHs in the Real World

Joe Touch <touch@isi.edu> Fri, 03 April 2015 18:47 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 451A11ACF5D for <v6ops@ietfa.amsl.com>; Fri, 3 Apr 2015 11:47:25 -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 edi7pKMwC2e5 for <v6ops@ietfa.amsl.com>; Fri, 3 Apr 2015 11:47:24 -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 44E351ACF58 for <v6ops@ietf.org>; Fri, 3 Apr 2015 11:47:24 -0700 (PDT)
Received: from [128.9.160.211] (mul.isi.edu [128.9.160.211]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id t33IknTw025030 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 3 Apr 2015 11:46:49 -0700 (PDT)
Message-ID: <551EE019.3040100@isi.edu>
Date: Fri, 03 Apr 2015 11:46:49 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Fred Baker (fred)" <fred@cisco.com>, Alexandru Petrescu <alexandru.petrescu@gmail.com>
References: <8D33A146-8721-4C43-8453-0385ED901D79@nominum.com> <5506E21D.80000@bogus.com> <8659A9C4-129C-4DA2-9265-B06D4AA4E262@nominum.com> <20150316.181923.74694044.sthaug@nethelp.no> <alpine.DEB.2.02.1503171452090.20507@uplift.swm.pp.se> <DDC70DDD-58A8-4B94-8F6B-E0FC339BB916@merike.com> <D13982C9.40CCA%evyncke@cisco.com> <52C91C37-7214-4EFD-A0DD-F0842CB45D2E@merike.com> <CAFU7BAQSeWTQD+gUkBa4bOFCNtETWZkydGPPmLsKC-UAnFrcJQ@mail.gmail.com> <1E9D679E-2EF3-47FC-941A-EBA13162E2FA@merike.com> <CO2PR04MB5855ACD7FE8C1057FCED231FE090@CO2PR04MB585.namprd04.prod.outlook.com> <5515628D.7020306@gmail.com> <237B7808-F457-42FE-9298-53E9181358E8@cisco.com> <55161E85.8020806@gmail.com>
In-Reply-To: <55161E85.8020806@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
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/Vv0vzN0ykOM8ExZ1IYHPVKPRp2I>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] why IPv6 EHs in the Real World
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, 03 Apr 2015 18:47:25 -0000


On 3/27/2015 8:22 PM, Brian E Carpenter wrote:
>>> I understand the security risk, I think; that’s discussed in RFC
>>> 5095. I’ll note, however, that the RFC doesn’t address “routing
>>> headers”; it addresses “routing headers of type 0”. The Segment
>>> Routing header is a Routing Header, and trashing all Segment
>>> Routing traffic because we have an issue with RH0 traffic seems a
>>> trifle extreme.
>
> This is laid out precisely in RFC 7045*, so you can tell any operator
> that trashes all RH packets that they are in violation and the protocol
> police are very angry with them.
> 
>     Brian

While I appreciate that screaming to operators isn't going to do much,
we need to find a way to encourage the operators to *ask for their money
back* from vendors who claim support for IPv6 but don't actually support
IPv6.

That's the lever we should find a way to pull.

Joe