On SEND deployment (Re: Conclusion: 6MAN Adoption call on draft-rafiee-6man-ssas-07)

Fernando Gont <fernando@gont.com.ar> Fri, 17 January 2014 01:02 UTC

Return-Path: <fernando@gont.com.ar>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F1931ACCE2 for <ipv6@ietfa.amsl.com>; Thu, 16 Jan 2014 17:02:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 lfm-1_wnReEF for <ipv6@ietfa.amsl.com>; Thu, 16 Jan 2014 17:02:35 -0800 (PST)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 55B691AC441 for <ipv6@ietf.org>; Thu, 16 Jan 2014 17:02:34 -0800 (PST)
Received: from [2001:5c0:1000:a::29ff] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.82) (envelope-from <fernando@gont.com.ar>) id 1W3xpB-0000vh-Mv; Fri, 17 Jan 2014 02:02:17 +0100
Message-ID: <52D88115.5050506@gont.com.ar>
Date: Thu, 16 Jan 2014 22:02:13 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>, 6man WG <ipv6@ietf.org>
Subject: On SEND deployment (Re: Conclusion: 6MAN Adoption call on draft-rafiee-6man-ssas-07)
References: <34A47FEE-22AF-4980-8A9A-4D0202CE1591@employees.org>
In-Reply-To: <34A47FEE-22AF-4980-8A9A-4D0202CE1591@employees.org>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: 6man Chairs <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 17 Jan 2014 01:02:37 -0000

Hi, Ole,

[This is orthogonal to the consensus call from my pov, but felt like
dropping a note]

On 01/15/2014 05:03 AM, Ole Troan wrote:
> We do not believe the working group understands why SEND is not
> deployed.

My two cents:

* Use of trust anchors makes deployment painful for the general case.

* Most popular OSes do not have a real SEND implementation (not long
ago the only way to play on BSDs was a Java implementation?). When it
comes to open source ones, the fact that SEND is IPR'ed doesn't help
the situation.

* While other parts of the "system" are largely unsecured, SeND
probably does not much. (e.g, if a local attacker can spoof a DNS
response, securing the layer-2/3 mapping will not buy much in most
cases -- i.e., just spoof the DNS response, and you're done).

* SEND wasn't there for v4. And there's a tendency to try to employ
IPv6 as IPv4, focusing on the benefit of the larger address space
(i.e., for some, "I lived with this in v4 for 20+ years, so..."). Not
that I necessarily endorse this view, but just meant to spell it out.

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1