Re: Last Call: <draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03.txt> (Security Implications of IPv6 on IPv4 Networks) to Informational RFC

Fernando Gont <fgont@si6networks.com> Wed, 03 April 2013 07:04 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68E5921F85C3 for <ietf@ietfa.amsl.com>; Wed, 3 Apr 2013 00:04:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.578
X-Spam-Level:
X-Spam-Status: No, score=-2.578 tagged_above=-999 required=5 tests=[AWL=-0.022, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tCDZ+kKWOgIC for <ietf@ietfa.amsl.com>; Wed, 3 Apr 2013 00:04:21 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id EB25C21F85D9 for <ietf@ietf.org>; Wed, 3 Apr 2013 00:04:20 -0700 (PDT)
Received: from [2001:5c0:1000:a::d6b] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UNHjr-0000xS-7C; Wed, 03 Apr 2013 09:04:08 +0200
Message-ID: <515B9CD2.1030402@si6networks.com>
Date: Wed, 03 Apr 2013 00:06:58 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: Last Call: <draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03.txt> (Security Implications of IPv6 on IPv4 Networks) to Informational RFC
References: <20130329130326.13012.1402.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130330230305.0bce91a8@resistor.net> <2671C6CDFBB59E47B64C10B3E0BD5923042CFA4019@PRVPEXVS15.corp.twcable.com> <6.2.5.6.2.20130401134936.0a5a1420@resistor.net> <515B6A04.9080400@si6networks.com> <8D23D4052ABE7A4490E77B1A012B63077512E746@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077512E746@mbx-01.win.nominum.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Cc: SM <sm@resistor.net>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 03 Apr 2013 07:04:21 -0000

On 04/02/2013 10:25 PM, Ted Lemon wrote:
> On Apr 2, 2013, at 7:30 PM, Fernando Gont <fgont@si6networks.com> wrote:
>>> I agree with the last sentence.  Happy Eyeballs is about the HTTP. 
>>> There are other applications protocols too. :-) 
>>
>> Happy eyeballs is about HTTP. But part of the approach predates "Happy
>> Eyeballs" -- please see RFC5461.
> 
> It's certainly true that we usually talk about Happy Eyeballs in the context of HTTP, but I use it for ssh as well, and I think it's applicable across a broad range of application protocols.   It is not applicable to _every_ protocol, but that's as strong a qualification as I'd put on it—saying it's only applicable to HTTP is not correct.
> 

Exactly. For instance, I seem to recall benefiting of RFC5461 for ssh in
NetBSD long before the first version of the Happy Eyeballs I-D was
published.

As noted in RFC5461, the approach is useful for any protocol -- but for
obvious reasons the benefits become evident for interactive protocols
such as HTTP, SSH, telnet, and the like...

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492