RFC 7048 on Neighbor Unreachability Detection Is Too Impatient

rfc-editor@rfc-editor.org Wed, 08 January 2014 21:47 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 983901A1F7D; Wed, 8 Jan 2014 13:47:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level:
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 YNTv7XKvmqk8; Wed, 8 Jan 2014 13:47:07 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 98BD51A1F6F; Wed, 8 Jan 2014 13:47:07 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 2D4267FC393; Wed, 8 Jan 2014 13:46:58 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7048 on Neighbor Unreachability Detection Is Too Impatient
From: rfc-editor@rfc-editor.org
Message-Id: <20140108214658.2D4267FC393@rfc-editor.org>
Date: Wed, 08 Jan 2014 13:46:58 -0800
Cc: drafts-update-ref@iana.org, ipv6@ietf.org, rfc-editor@rfc-editor.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: Wed, 08 Jan 2014 21:47:09 -0000

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

        
        RFC 7048

        Title:      Neighbor Unreachability Detection 
                    Is Too Impatient 
        Author:     E. Nordmark, I. Gashinsky
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2014
        Mailbox:    nordmark@acm.org, 
                    igor@yahoo-inc.com
        Pages:      8
        Characters: 17946
        Updates:    RFC 4861

        I-D Tag:    draft-ietf-6man-impatient-nud-07.txt

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

IPv6 Neighbor Discovery includes Neighbor Unreachability Detection.
That function is very useful when a host has an alternative neighbor
-- for instance, when there are multiple default routers -- since it
allows the host to switch to the alternative neighbor in a short
time.  By default, this time is 3 seconds after the node starts
probing.  However, if there are no alternative neighbors, this
timeout behavior is far too impatient.  This document specifies
relaxed rules for Neighbor Discovery retransmissions that allow an
implementation to choose different timeout behavior based on whether
or not there are alternative neighbors.  This document updates RFC
4861.

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/search
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