RFC 7559 on Packet-Loss Resiliency for Router Solicitations

rfc-editor@rfc-editor.org Fri, 29 May 2015 22:03 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 2E76B1B2DCD; Fri, 29 May 2015 15:03:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 VtpsPtZHr0-4; Fri, 29 May 2015 15:03:35 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 91BD81B2DC7; Fri, 29 May 2015 15:03:35 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id AEBBB18046D; Fri, 29 May 2015 15:01:23 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7559 on Packet-Loss Resiliency for Router Solicitations
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150529220123.AEBBB18046D@rfc-editor.org>
Date: Fri, 29 May 2015 15:01:23 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/WlmWyOd1iP5dlMyv5PEx-LFKzSY>
Cc: 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: Fri, 29 May 2015 22:03:41 -0000

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

        
        RFC 7559

        Title:      Packet-Loss Resiliency for Router Solicitations 
        Author:     S. Krishnan, D. Anipko, D. Thaler
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2015
        Mailbox:    suresh.krishnan@ericsson.com, 
                    dmitry.anipko@gmail.com, 
                    dthaler@microsoft.com
        Pages:      6
        Characters: 11619
        Updates:    RFC 4861

        I-D Tag:    draft-ietf-6man-resilient-rs-06.txt

        URL:        https://www.rfc-editor.org/info/rfc7559

        DOI:        http://dx.doi.org/10.17487/RFC7559

When an interface on a host is initialized, the host transmits Router
Solicitations in order to minimize the amount of time it needs to
wait until the next unsolicited multicast Router Advertisement is
received.  In certain scenarios, these Router Solicitations
transmitted by the host might be lost.  This document specifies a
mechanism for hosts to cope with the loss of the initial Router
Solicitations.

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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://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