draft-ietf-6man-resilient-rs-02.txt   draft-ietf-6man-resilient-rs-03.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 D. Thaler Intended status: Standards Track D. Thaler
Expires: April 24, 2014 Microsoft Expires: October 23, 2014 Microsoft
October 21, 2013 April 21, 2014
Packet loss resiliency for Router Solicitations Packet loss resiliency for Router Solicitations
draft-ietf-6man-resilient-rs-02 draft-ietf-6man-resilient-rs-03
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. Furthermore, on some links, unsolicited multicast
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 24, 2014. This Internet-Draft will expire on October 23, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 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 4, line 41 skipping to change at page 4, line 41
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 [SOLMAXRT].
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] [SOLMAXRT].
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
MUST stop retransmitting the RSs when Router Discovery is successful SHOULD stop retransmitting the RSs when Router Discovery is
(i.e. an RA with a non-zero Router Lifetime that results in a default successful (i.e. an RA with a non-zero Router Lifetime that results
route is received). If an RA is recieved from a router and it does in a default route is received). Hosts MAY continue retransmitting
not result in a default route (i.e. Router Lifetime is zero) the the RSs even after router discovery is successful. If the host
host MUST continue retransmitting the RSs. continues to retransmit RSs, it is RECOMMENDED that such
retransmissions be rate-limited to one every MRT. If an RA is
recieved from a router and it does not result in a default route
(i.e. Router Lifetime is zero) the host MUST continue retransmitting
the RSs.
On non-multicast links, the hosts following this specification MUST On non-multicast links, the hosts following this specification MUST
continue retransmitting the RSs even after an RA that results in a continue retransmitting the RSs even after an RA that results in a
default route is received. This is required because, in such links, default route is received. This is required because, in such links,
sending an RA can only be triggered by an RS. Please note that such sending an RA can only be triggered by an RS. Please note that such
links have special mechanisms for sending RSes as well. e.g. The links have special mechanisms for sending RSes as well. e.g. The
mechanism specified in Section 8.3.4. of ISATAP [RFC5214] unicasts mechanism specified in Section 8.3.4. of ISATAP [RFC5214] unicasts
the RSes to specific routers. the RSes to specific routers.
3. Configuring the use of retransmissions 3. Configuring the use of retransmissions
skipping to change at page 5, line 38 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 author would like to thank Steve Baillargeon, Erik Kline, Andrew The authors would like to thank Steve Baillargeon, Erik Kline, Andrew
Yourtchenko, and Ole Troan for their reviews and suggestions that Yourtchenko, Ole Troan, Erik Nordmark, Lorenzo Colitti, Thomas Narten
made this document better. and Ran Atkinson for their reviews and suggestions that made this
document better.
8. References 8. References
8.1. Normative References 8.1. 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,
 End of changes. 7 change blocks. 
13 lines changed or deleted 19 lines changed or added

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