Last Call: <draft-ietf-6man-enhanced-dad-12.txt> (Enhanced Duplicate Address Detection) to Proposed Standard
The IESG <iesg-secretary@ietf.org> Tue, 20 January 2015 14:57 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCEA61B2A88; Tue, 20 Jan 2015 06:57:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 uIjxMAHrg5lJ; Tue, 20 Jan 2015 06:57:35 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 31A711B2DB6; Tue, 20 Jan 2015 06:57:35 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-6man-enhanced-dad-12.txt> (Enhanced Duplicate Address Detection) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
Message-ID: <20150120145735.11874.30201.idtracker@ietfa.amsl.com>
Date: Tue, 20 Jan 2015 06:57:35 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/8XmPL1rEddyYgMqk8W1YjYIiecQ>
Cc: ipv6@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jan 2015 14:57:36 -0000
The IESG has received a request from the IPv6 Maintenance WG (6man) to consider the following document: - 'Enhanced Duplicate Address Detection' <draft-ietf-6man-enhanced-dad-12.txt> as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2015-02-03. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract IPv6 Loopback Suppression and Duplicate Address Detection (DAD) are discussed in Appendix A of RFC4862. That specification mentions a hardware-assisted mechanism to detect looped back DAD messages. If hardware cannot suppress looped back DAD messages, a software solution is required. Several service provider communities have expressed a need for automated detection of looped back Neighbor Discovery (ND) messages used by DAD. This document includes mitigation techniques and outlines the Enhanced DAD algorithm to automate the detection of looped back IPv6 ND messages used by DAD. For network loopback tests, the Enhanced DAD algorithm allows IPv6 to self-heal after a loopback is placed and removed. Further, for certain access networks the document automates resolving a specific duplicate address conflict. This document updates RFC4861, RFC4862, and RFC4429. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-6man-enhanced-dad/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-6man-enhanced-dad/ballot/ No IPR declarations have been submitted directly on this I-D.