Re: Stephen Farrell's No Objection on draft-ietf-6man-enhanced-dad-14: (with COMMENT)

Brian Haberman <brian@innovationslab.net> Thu, 05 March 2015 15:21 UTC

Return-Path: <brian@innovationslab.net>
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 8D5091A020A; Thu, 5 Mar 2015 07:21:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 3LqpVRZl3Apl; Thu, 5 Mar 2015 07:21:11 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2A4B1A0158; Thu, 5 Mar 2015 07:18:28 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id CFD8D88154; Thu, 5 Mar 2015 07:18:28 -0800 (PST)
Received: from clemson.local (unknown [76.21.129.88]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 23BEB1368260; Thu, 5 Mar 2015 07:18:28 -0800 (PST)
Message-ID: <54F873C2.70702@innovationslab.net>
Date: Thu, 05 Mar 2015 10:18:26 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, The IESG <iesg@ietf.org>
Subject: Re: Stephen Farrell's No Objection on draft-ietf-6man-enhanced-dad-14: (with COMMENT)
References: <20150305151222.4615.19822.idtracker@ietfa.amsl.com>
In-Reply-To: <20150305151222.4615.19822.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="sddWtSneMkIKT5f7d36bdLCaJAsOsseEf"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/NwA2vSFupG0wyd_xeWAfdC7iCmw>
Cc: ot@cisco.com, draft-ietf-6man-enhanced-dad.all@ietf.org, ipv6@ietf.org, 6man-chairs@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: Thu, 05 Mar 2015 15:21:12 -0000

Hiya Stephen,

On 3/5/15 10:12 AM, Stephen Farrell wrote:
> Stephen Farrell has entered the following ballot position for
> draft-ietf-6man-enhanced-dad-14: No Objection
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> http://datatracker.ietf.org/doc/draft-ietf-6man-enhanced-dad/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> 
> 
> I'm a bit confused here - you use a field from SEND, and
> then say that that could be borked, so the mitigation is
> that one might use SEND to protect that. Why not just use
> SEND - can you explain?
> 

This approach is just using the nonce option to identify the packet when
it is looped back to the sending system.  This can be applied to systems
and/or networks that either can't or won't deploy the entire SEND
infrastructure.

Regards,
Brian