Re: What to improve? BCP-38/SAC-004 anyone?

"John Levine" <johnl@taugh.com> Thu, 31 December 2015 19:41 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77F1C1A8A6A for <ietf@ietfa.amsl.com>; Thu, 31 Dec 2015 11:41:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.663
X-Spam-Level: *
X-Spam-Status: No, score=1.663 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=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 sLbv6EDX3xjw for <ietf@ietfa.amsl.com>; Thu, 31 Dec 2015 11:41:46 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D0791A8A6D for <ietf@ietf.org>; Thu, 31 Dec 2015 11:41:46 -0800 (PST)
Received: (qmail 9347 invoked from network); 31 Dec 2015 19:41:45 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 31 Dec 2015 19:41:45 -0000
Date: Thu, 31 Dec 2015 19:41:23 -0000
Message-ID: <20151231194123.1162.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: What to improve? BCP-38/SAC-004 anyone?
In-Reply-To: <A074CA07-691E-41A7-B1D7-33F4ECBED5A9@puck.nether.net>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/SyohuEkfvELD0B0sTW8gaayebOA>
Cc: jared@puck.nether.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Dec 2015 19:41:47 -0000

>The reason we (as an operator) can’t use BCP-38 is the vendor hardware can’t do it at line-rate and
>the performance hit is too much to sustain.

A year or two ago I was talking to some largish providers who told me
that their problem was multihomed customers who have PA space from
multiple providers and for varions reasons (not all silly ones) don't
always send traffic to the port corresponding to the address.  The
usual customer response when asked to clean up their routing is "if
you don't want our $<large> per month, we're sure we can find other
providers that do."

This strikes as a problem that could be solved by providing some way
for routers that don't do BGP to tell their upstreams what the other
address ranges are, but of course the real issue is whether such a
hack could get implemented in routers that people actually buy and
use.

R's,
John