IETF Logo Mail Archive

RE: [Int-area] Route Information Options in Redirect Messages

Mikael Abrahamsson <swmike@swm.pp.se> Fri, 13 January 2017 06:47 UTC

Return-Path: <swmike@swm.pp.se>
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 F1FE0129AA7; Thu, 12 Jan 2017 22:47:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.5
X-Spam-Level:
X-Spam-Status: No, score=-7.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 q1rMJYgr6Tle; Thu, 12 Jan 2017 22:47:02 -0800 (PST)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (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 D5AB7129AA4; Thu, 12 Jan 2017 22:47:01 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 7478CA2; Fri, 13 Jan 2017 07:46:59 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1484290019; bh=8hlST7AMrE+6D+X+8gb2PLyUs0p20rv4a6tj0iJ8gaU=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=ZXVqRRgMDxsX/zKdUAMlJhDOz5gvwoYIAgRbhpInAX4sz/ViOF+WuMLvYuVVvXsKO f5f6m6pqAagx4OiBv+dkIZhm/fBQp7M4+bLPBhVrXGvqVc1HA+vgVr7rgoIEjDxm5X 5GPtzlse9cN+s5DMVheuncrSeqrMy9uJC650a/wE=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 70BA988; Fri, 13 Jan 2017 07:46:59 +0100 (CET)
Date: Fri, 13 Jan 2017 07:46:59 +0100
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: RE: [Int-area] Route Information Options in Redirect Messages
In-Reply-To: <c8baed16b3dc46d2a667614310f0334d@XCH15-06-08.nw.nos.boeing.com>
Message-ID: <alpine.DEB.2.02.1701130741020.31101@uplift.swm.pp.se>
References: <b0d15d2e8b3e414abf4e87c60d39e252@XCH15-06-08.nw.nos.boeing.com> <32fbea25-01c9-aa32-e70f-3e1282f56294@gmail.com> <5cd024891c204a9bb37dcc23796c36c6@XCH15-06-08.nw.nos.boeing.com> <016f01d26b78$870895a0$9519c0e0$@huitema.net> <6d21dd17f0b94a39a71600944878ec39@XCH15-06-08.nw.nos.boeing.com> <BFB9A939-2CA7-4E00-8B93-5548CDA244E3@gmail.com> <c8baed16b3dc46d2a667614310f0334d@XCH15-06-08.nw.nos.boeing.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/adSy_sSYpYfud17QeRBE9S-EaRM>
Cc: INT Area <int-area@ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 13 Jan 2017 06:47:04 -0000

On Wed, 11 Jan 2017, Templin, Fred L wrote:

> SEND [RFC3971] provides one possible mitigation in other cases.

Is there anything out there that implements SEND? I see Cisco IOS support, 
quick googling didn't yield anything I found that indicated "widely 
supported". Frankly, I don't even understand how it would work in a 
non-tightly-administrated network, with pre-provisioned cyrptographic 
information.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

v2.23.0 | Report a Bug | By Email