RFC 6957 on Duplicate Address Detection Proxy

rfc-editor@rfc-editor.org Thu, 06 June 2013 20:58 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 448C411E8109; Thu, 6 Jun 2013 13:58:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.263
X-Spam-Level:
X-Spam-Status: No, score=-102.263 tagged_above=-999 required=5 tests=[AWL=-0.262, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, 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 wF5YxuAS+O8B; Thu, 6 Jun 2013 13:58:18 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 17BB611E8102; Thu, 6 Jun 2013 13:58:18 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id EC53862178; Thu, 6 Jun 2013 13:56:50 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6957 on Duplicate Address Detection Proxy
From: rfc-editor@rfc-editor.org
Message-Id: <20130606205650.EC53862178@rfc-editor.org>
Date: Thu, 06 Jun 2013 13:56:50 -0700
Cc: ipv6@ietf.org, rfc-editor@rfc-editor.org
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: Thu, 06 Jun 2013 20:58:19 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6957

        Title:      Duplicate Address Detection Proxy 
        Author:     F. Costa, 
                    J-M. Combes, Ed., 
                    X. Pougnard,
                    H. Li
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2013
        Mailbox:    fabio.costa@orange.com, 
                    jeanmichel.combes@orange.com, 
                    xavier.pougnard@orange.com,
                    lihy@huawei.com
        Pages:      16
        Characters: 32537
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-6man-dad-proxy-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6957.txt

The document describes a proxy-based mechanism allowing the use of
Duplicate Address Detection (DAD) by IPv6 nodes in a
point-to-multipoint architecture with a "split-horizon" forwarding
scheme, primarily deployed for Digital Subscriber Line (DSL) and
Fiber access architectures.  Based on the DAD signaling, the
first-hop router stores in a Binding Table all known IPv6 addresses
used on a point-to-multipoint domain (e.g., VLAN).  When a node
performs DAD for an address already used by another node, the
first-hop router defends the address rather than the device using the
address.

This document is a product of the IPv6 Maintenance Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC