draft-ietf-roll-rpl-observations-04.txt   draft-ietf-roll-rpl-observations-05.txt 
ROLL R. Jadhav, Ed. ROLL R. Jadhav, Ed.
Internet-Draft R. Sahoo Internet-Draft
Intended status: Standards Track Y. Wu Intended status: Standards Track R. Sahoo
Expires: November 22, 2020 Huawei Expires: June 3, 2021 Juniper
May 21, 2020 Y. Wu
Huawei
November 30, 2020
RPL Observations RPL Observations
draft-ietf-roll-rpl-observations-04 draft-ietf-roll-rpl-observations-05
Abstract Abstract
This document describes RPL protocol design issues, various This document describes RPL protocol design issues, various
observations and possible consequences of the design and observations and possible consequences of the design and
implementation choices. implementation choices.
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
skipping to change at page 1, line 33 skipping to change at page 1, line 35
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 November 22, 2020. This Internet-Draft will expire on June 3, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
skipping to change at page 3, line 6 skipping to change at page 3, line 9
Option? . . . . . . . . . . . . . . . . . . . . . . . . 17 Option? . . . . . . . . . . . . . . . . . . . . . . . . 17
15.3. Deliberations . . . . . . . . . . . . . . . . . . . . . 17 15.3. Deliberations . . . . . . . . . . . . . . . . . . . . . 17
16. Backward Compatibility issues with RPL Options . . . . . . . 17 16. Backward Compatibility issues with RPL Options . . . . . . . 17
17. RPL under-specification . . . . . . . . . . . . . . . . . . . 17 17. RPL under-specification . . . . . . . . . . . . . . . . . . . 17
18. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 18. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18
19. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 19. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
20. Security Considerations . . . . . . . . . . . . . . . . . . . 18 20. Security Considerations . . . . . . . . . . . . . . . . . . . 18
21. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
21.1. Normative References . . . . . . . . . . . . . . . . . . 18 21.1. Normative References . . . . . . . . . . . . . . . . . . 18
21.2. Informative References . . . . . . . . . . . . . . . . . 19 21.2. Informative References . . . . . . . . . . . . . . . . . 19
Appendix A. Additional Stuff . . . . . . . . . . . . . . . . . . 20 Appendix A. Additional Stuff . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
1. Motivation 1. Motivation
The primary motivation for this draft is to enlist different issues The primary motivation for this draft is to enlist different issues
with RPL operation and invoke a discussion within the working group. with RPL operation and invoke a discussion within the working group.
This draft by itself is not intended for RFC tracks but as a WG This draft by itself is not intended for RFC tracks but as a WG
discussion track. This draft may in turn result in other work items discussion track. This draft may in turn result in other work items
taken up by the WG which may improvise on the issues mentioned taken up by the WG which may improvise on the issues mentioned
herewith. herewith.
skipping to change at page 7, line 38 skipping to change at page 7, line 38
ancestor. ancestor.
5. Interpreting Trickle Timer 5. Interpreting Trickle Timer
Trickle algorithm defines a mechanism to reset the timer. Trickle Trickle algorithm defines a mechanism to reset the timer. Trickle
timer reset is unlike regular periodic timers wherein the timer is timer reset is unlike regular periodic timers wherein the timer is
simply reset to start again. Reset of trickle timer implies simply reset to start again. Reset of trickle timer implies
resetting the trickle back to Imin and starting with a new interval resetting the trickle back to Imin and starting with a new interval
as mentioned in Section 4.2 of [RFC6206]. as mentioned in Section 4.2 of [RFC6206].
|----|--------|----------------|--------------------------------| . . . . . . |----|--------|----------------|------------------------------| . . . .
Imin I2 I3 I4 I5 Imin I2 I3 I4 I5
Figure 4: Trickle Timer Operation Figure 4: Trickle Timer Operation
The above figure shows an example of trickle intervals. An interval The above figure shows an example of trickle intervals. An interval
is double that of the previous interval size. Section 4.2. of is double that of the previous interval size. Section 4.2. of
[RFC6206] states that, [RFC6206] states that,
"If Trickle hears a transmission that is "inconsistent" and I is "If Trickle hears a transmission that is "inconsistent" and I is
greater than Imin, it resets the Trickle timer. To reset the timer, greater than Imin, it resets the Trickle timer. To reset the timer,
Trickle sets I to Imin and starts a new interval as in step 2. If I Trickle sets I to Imin and starts a new interval as in step 2. If I
skipping to change at page 19, line 5 skipping to change at page 19, line 5
"The Trickle Algorithm", RFC 6206, DOI 10.17487/RFC6206, "The Trickle Algorithm", RFC 6206, DOI 10.17487/RFC6206,
March 2011, <https://www.rfc-editor.org/info/rfc6206>. March 2011, <https://www.rfc-editor.org/info/rfc6206>.
[RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J., [RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J.,
Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur, Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur,
JP., and R. Alexander, "RPL: IPv6 Routing Protocol for JP., and R. Alexander, "RPL: IPv6 Routing Protocol for
Low-Power and Lossy Networks", RFC 6550, Low-Power and Lossy Networks", RFC 6550,
DOI 10.17487/RFC6550, March 2012, DOI 10.17487/RFC6550, March 2012,
<https://www.rfc-editor.org/info/rfc6550>. <https://www.rfc-editor.org/info/rfc6550>.
[RFC6551] Vasseur, JP., Ed., Kim, M., Ed., Pister, K., Dejean, N.,
and D. Barthel, "Routing Metrics Used for Path Calculation
in Low-Power and Lossy Networks", RFC 6551,
DOI 10.17487/RFC6551, March 2012,
<https://www.rfc-editor.org/info/rfc6551>.
[RFC6552] Thubert, P., Ed., "Objective Function Zero for the Routing
Protocol for Low-Power and Lossy Networks (RPL)",
RFC 6552, DOI 10.17487/RFC6552, March 2012,
<https://www.rfc-editor.org/info/rfc6552>.
[RFC6775] Shelby, Z., Ed., Chakrabarti, S., Nordmark, E., and C. [RFC6775] Shelby, Z., Ed., Chakrabarti, S., Nordmark, E., and C.
Bormann, "Neighbor Discovery Optimization for IPv6 over Bormann, "Neighbor Discovery Optimization for IPv6 over
Low-Power Wireless Personal Area Networks (6LoWPANs)", Low-Power Wireless Personal Area Networks (6LoWPANs)",
RFC 6775, DOI 10.17487/RFC6775, November 2012, RFC 6775, DOI 10.17487/RFC6775, November 2012,
<https://www.rfc-editor.org/info/rfc6775>. <https://www.rfc-editor.org/info/rfc6775>.
[RFC6997] Goyal, M., Ed., Baccelli, E., Philipp, M., Brandt, A., and
J. Martocci, "Reactive Discovery of Point-to-Point Routes
in Low-Power and Lossy Networks", RFC 6997,
DOI 10.17487/RFC6997, August 2013,
<https://www.rfc-editor.org/info/rfc6997>.
21.2. Informative References 21.2. Informative References
[I-D.clausen-lln-rpl-experiences] [I-D.clausen-lln-rpl-experiences]
Clausen, T., Verdiere, A., Yi, J., Herberg, U., and Y. Clausen, T., Verdiere, A., Yi, J., Herberg, U., and Y.
Igarashi, "Observations on RPL: IPv6 Routing Protocol for Igarashi, "Observations on RPL: IPv6 Routing Protocol for
Low power and Lossy Networks", draft-clausen-lln-rpl- Low power and Lossy Networks", draft-clausen-lln-rpl-
experiences-11 (work in progress), March 2018. experiences-11 (work in progress), March 2018.
[I-D.ietf-intarea-adhoc-wireless-com] [I-D.ietf-intarea-adhoc-wireless-com]
Baccelli, E. and C. Perkins, "Multi-hop Ad Hoc Wireless Baccelli, E. and C. Perkins, "Multi-hop Ad Hoc Wireless
skipping to change at page 20, line 10 skipping to change at page 19, line 40
[Perlman83] [Perlman83]
Perlman, R., "Fault-Tolerant Broadcast of Routing Perlman, R., "Fault-Tolerant Broadcast of Routing
Information", North-Holland Computer Networks, Vol.7, Information", North-Holland Computer Networks, Vol.7,
December 1983. December 1983.
Appendix A. Additional Stuff Appendix A. Additional Stuff
Authors' Addresses Authors' Addresses
Rahul Arvind Jadhav (editor) Rahul Arvind Jadhav (editor)
Huawei Marathahalli
Kundalahalli Village, Whitefield,
Bangalore, Karnataka 560037 Bangalore, Karnataka 560037
India India
Phone: +91-080-49160700
Email: rahul.ietf@gmail.com Email: rahul.ietf@gmail.com
Rabi Narayan Sahoo Rabi Narayan Sahoo
Huawei Juniper
Kundalahalli Village, Whitefield, Whitefield
Bangalore, Karnataka 560037 Bangalore, Karnataka 560037
India India
Phone: +91-080-49160700 Email: rabinarayans0828@gmail.com
Email: rabinarayans@huawei.com
Yuefeng Wu Yuefeng Wu
Huawei Huawei
No.101, Software Avenue, Yuhuatai District, No.101, Software Avenue, Yuhuatai District,
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
Phone: +86-15251896569 Phone: +86-15251896569
Email: wuyuefeng@huawei.com Email: wuyuefeng@huawei.com
 End of changes. 12 change blocks. 
35 lines changed or deleted 16 lines changed or added

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