draft-ietf-6man-resilient-rs-04.txt   draft-ietf-6man-resilient-rs-05.txt 
6man Working Group S. Krishnan 6man Working Group S. Krishnan
Internet-Draft Ericsson Internet-Draft Ericsson
Updates: RFC4861 (if approved) D. Anipko Updates: RFC4861 (if approved) D. Anipko
Intended status: Standards Track Unaffiliated Intended status: Standards Track Unaffiliated
Expires: April 17, 2015 D. Thaler Expires: September 10, 2015 D. Thaler
Microsoft Microsoft
October 14, 2014 March 9, 2015
Packet loss resiliency for Router Solicitations Packet loss resiliency for Router Solicitations
draft-ietf-6man-resilient-rs-04 draft-ietf-6man-resilient-rs-05
Abstract Abstract
When an interface on a host is initialized, the host transmits Router When an interface on a host is initialized, the host transmits Router
Solicitations in order to minimize the amount of time it needs to Solicitations in order to minimize the amount of time it needs to
wait until the next unsolicited multicast Router Advertisement is wait until the next unsolicited multicast Router Advertisement is
received. In certain scenarios, these router solicitations received. In certain scenarios, these router solicitations
transmitted by the host might be lost. This document specifies a transmitted by the host might be lost. This document specifies a
mechanism for hosts to cope with the loss of the initial Router mechanism for hosts to cope with the loss of the initial Router
Solicitations. Furthermore, on some links, unsolicited multicast Solicitations.
Router Advertisements are never sent and the mechanism in this
document is intended to work even in such scenarios.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 17, 2015. This Internet-Draft will expire on September 10, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 23 skipping to change at page 2, line 21
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Conventions used in this document . . . . . . . . . . . . 3 1.1. Conventions used in this document . . . . . . . . . . . . 3
2. Proposed algorithm . . . . . . . . . . . . . . . . . . . . . 4 2. Proposed algorithm . . . . . . . . . . . . . . . . . . . . . 4
2.1. Stopping the retransmissions . . . . . . . . . . . . . . 4 2.1. Stopping the retransmissions . . . . . . . . . . . . . . 4
3. Configuring the use of retransmissions . . . . . . . . . . . 5 3. Configuring the use of retransmissions . . . . . . . . . . . 5
4. Known Limitations . . . . . . . . . . . . . . . . . . . . . . 5 4. Known Limitations . . . . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5 6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 8. Normative References . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . 5
8.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
As specified in [RFC4861], when an interface on a host is As specified in [RFC4861], when an interface on a host is
initialized, in order to obtain Router Advertisements quickly, a host initialized, in order to obtain Router Advertisements quickly, a host
transmits up to MAX_RTR_SOLICITATIONS (3) Router Solicitation transmits up to MAX_RTR_SOLICITATIONS (3) Router Solicitation
messages, each separated by at least RTR_SOLICITATION_INTERVAL (4) messages, each separated by at least RTR_SOLICITATION_INTERVAL (4)
seconds. In certain scenarios, these router solicitations seconds. In certain scenarios, these router solicitations
transmitted by the host might be lost. e.g. The host is connected to transmitted by the host might be lost. e.g. The host is connected to
skipping to change at page 4, line 35 skipping to change at page 4, line 35
MRT 3600 seconds MRT 3600 seconds
MRC 0 MRC 0
MRD 0 MRD 0
The initial value IRT was chosen to be in line with the current The initial value IRT was chosen to be in line with the current
retransmission interval (RTR_SOLICITATION_INTERVAL) that is specified retransmission interval (RTR_SOLICITATION_INTERVAL) that is specified
by [RFC4861] and the maximum retransmission time MRT was chosen to be by [RFC4861] and the maximum retransmission time MRT was chosen to be
in line with the new value of SOL_MAX_RT as specified by [SOLMAXRT]. in line with the new value of SOL_MAX_RT as specified by [RFC7083].
This is to ensure that the short term behavior of the RSs is similar This is to ensure that the short term behavior of the RSs is similar
to what is experienced in current networks, and longer term to what is experienced in current networks, and longer term
persistent retransmission behavior trends towards being similar to persistent retransmission behavior trends towards being similar to
that of DHCPv6 [RFC3315] [SOLMAXRT]. that of DHCPv6 [RFC3315] [RFC7083].
2.1. Stopping the retransmissions 2.1. Stopping the retransmissions
On multicast-capable links, the hosts following this specification On multicast-capable links, the hosts following this specification
SHOULD stop retransmitting the RSs when Router Discovery is SHOULD stop retransmitting the RSs when Router Discovery is
successful (i.e. an RA with a non-zero Router Lifetime that results successful (i.e. an RA with a non-zero Router Lifetime that results
in a default route is received). If an RA is recieved from a router in a default route is received). If an RA is recieved from a router
and it does not result in a default route (i.e. Router Lifetime is and it does not result in a default route (i.e. Router Lifetime is
zero) the host MUST continue retransmitting the RSs. zero) the host MUST continue retransmitting the RSs.
skipping to change at page 5, line 42 skipping to change at page 5, line 42
This document does not require any IANA actions. This document does not require any IANA actions.
6. Security Considerations 6. Security Considerations
This document does not present any additional security issues beyond This document does not present any additional security issues beyond
those discussed in [RFC4861]. those discussed in [RFC4861].
7. Acknowledgements 7. Acknowledgements
The authors would like to thank Steve Baillargeon, Erik Kline, Andrew The authors would like to thank Steve Baillargeon, Erik Kline, Andrew
Yourtchenko, Ole Troan, Erik Nordmark, Lorenzo Colitti, Thomas Narten Yourtchenko, Ole Troan, Erik Nordmark, Lorenzo Colitti, Thomas
and Ran Atkinson for their reviews and suggestions that made this Narten, Ran Atkinson, Allison Mankin, Les Ginsberg and Brian
document better. Carpenter for their reviews and suggestions that made this document
better.
8. References
8.1. Normative References 8. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 3315, July 2003. IPv6 (DHCPv6)", RFC 3315, July 2003.
[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
"Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
September 2007. September 2007.
[SOLMAXRT]
Droms, R., "Modification to Default Value of SOL_MAX_RT",
draft-droms-dhc-dhcpv6-solmaxrt-update-02 (work in
progress), January 2012.
8.2. Informative References
[RFC5214] Templin, F., Gleeson, T., and D. Thaler, "Intra-Site [RFC5214] Templin, F., Gleeson, T., and D. Thaler, "Intra-Site
Automatic Tunnel Addressing Protocol (ISATAP)", RFC 5214, Automatic Tunnel Addressing Protocol (ISATAP)", RFC 5214,
March 2008. March 2008.
[RFC7083] Droms, R., "Modification to Default Values of SOL_MAX_RT
and INF_MAX_RT", RFC 7083, November 2013.
Authors' Addresses Authors' Addresses
Suresh Krishnan Suresh Krishnan
Ericsson Ericsson
8400 Decarie Blvd. 8400 Decarie Blvd.
Town of Mount Royal, QC Town of Mount Royal, QC
Canada Canada
Phone: +1 514 345 7900 x42871 Phone: +1 514 345 7900 x42871
Email: suresh.krishnan@ericsson.com Email: suresh.krishnan@ericsson.com
 End of changes. 13 change blocks. 
26 lines changed or deleted 17 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/