Questions from the Authors of draft-gashinsky-v6nd-enhance

Joel Jaeggli <joelja@bogus.com> Sun, 07 August 2011 17:57 UTC

Return-Path: <joelja@bogus.com>
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 8F36C21F86DF for <ipv6@ietfa.amsl.com>; Sun, 7 Aug 2011 10:57:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.998
X-Spam-Level:
X-Spam-Status: No, score=-101.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
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 hIvzdvmtzdU5 for <ipv6@ietfa.amsl.com>; Sun, 7 Aug 2011 10:57:26 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 040F021F86D7 for <ipv6@ietf.org>; Sun, 7 Aug 2011 10:57:25 -0700 (PDT)
Received: from [192.168.1.118] (adsl-99-173-15-226.dsl.pltn13.sbcglobal.net [99.173.15.226]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p77HvkFi058388 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 7 Aug 2011 17:57:48 GMT (envelope-from joelja@bogus.com)
From: Joel Jaeggli <joelja@bogus.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-18--574783408"
Date: Sun, 07 Aug 2011 10:57:45 -0700
Subject: Questions from the Authors of draft-gashinsky-v6nd-enhance
To: ipv6@ietf.org
Message-Id: <4CF32C15-36D0-4287-8573-ABF750F8BB08@bogus.com>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sun, 07 Aug 2011 17:57:49 +0000 (UTC)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 07 Aug 2011 17:57:26 -0000

Greetings,

This is followup from our discussion in both v6ops and 6man. We got a lot of useful input, but I would like to ask the mailing list to see if we can solidify this into a course of action.

For reference:

ftp://ftp.ietf.org/internet-drafts/draft-gashinsky-v6nd-enhance-00.txt

http://tools.ietf.org/agenda/81/slides/6man-9.pdf


1. Is this document (draft-gashinsky-v6nd-enhance) worthwhile?

2. Is there critique of the two proposed 4861 changes?

	A. 7.3  NDP Protocol Gratuitous NA

		a. We believe the is the question is whether the technique would 
		be useful under duress, wether it is potentially dangerous,
		if the safeguards are adequate, etc.

	B. 7.4 ND cache priming and refresh

3. Should we separate the potential mitigations (section 6) and implementation advice (section 7.1 and 7.2) into a separate document.

	A. Assumption (validated in v6ops at ietf81) is that v6ops would be happy
	 to take the mitigation and implementation advice as an informational document

	B. Assumption 2 a draft updating 4861 would be a standards track document.

	C. Assumption 3, should harmonize with  draft-nordmark-6man-impatient-nud-00

4. Is there anyone who thinks that an update to 4861 to address dos exposure is unnecessary?

	A. Just publish the advice and be done with it?

Comments on some or all of these questions would help the authors decide where to go next.

Thanks
Joel