| < draft-ietf-6lo-ap-nd-00.txt | draft-ietf-6lo-ap-nd-01.txt > | |||
|---|---|---|---|---|
| 6lo B. Sarikaya, Ed. | 6lo B. Sarikaya, Ed. | |||
| Internet-Draft Huawei USA | Internet-Draft Huawei USA | |||
| Updates: 6775 (if approved) P. Thubert | Updates: 6775 (if approved) P. Thubert | |||
| Intended status: Standards Track Cisco | Intended status: Standards Track Cisco | |||
| Expires: May 16, 2017 M. Sethi, Ed. | Expires: November 16, 2017 M. Sethi, Ed. | |||
| Ericsson | Ericsson | |||
| November 12, 2016 | May 15, 2017 | |||
| Address Protected Neighbor Discovery for Low-power and Lossy Networks | Address Protected Neighbor Discovery for Low-power and Lossy Networks | |||
| draft-ietf-6lo-ap-nd-00 | draft-ietf-6lo-ap-nd-01 | |||
| Abstract | Abstract | |||
| This document defines an extension to 6LoWPAN Neighbor Discovery. | This document defines an extension to 6LoWPAN Neighbor Discovery. | |||
| This extension is designed for low-power and lossy network | This extension is designed for low-power and lossy network | |||
| environments and it supports multi-hop operation. Nodes supporting | environments and it supports multi-hop operation. Nodes supporting | |||
| this extension compute a Cryptographically Unique Interface ID and | this extension compute a Cryptographically Unique Interface ID and | |||
| associate it with one or more of their Registered Addresses. The | associate it with one or more of their Registered Addresses. The | |||
| Cryptographic ID (Crypto-ID) uniquely identifies the owner of the | Cryptographic ID (Crypto-ID) uniquely identifies the owner of the | |||
| Registered Address. It is used in place of the EUI-64 address that | Registered Address. It is used in place of the EUI-64 address that | |||
| skipping to change at page 1, line 42 ¶ | skipping to change at page 1, line 42 ¶ | |||
| 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 May 16, 2017. | This Internet-Draft will expire on November 16, 2017. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2016 IETF Trust and the persons identified as the | Copyright (c) 2017 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 15, line 5 ¶ | skipping to change at page 14, line 51 ¶ | |||
| 7. Acknowledgements | 7. Acknowledgements | |||
| We are grateful to Rene Struik and Robert Moskowitz for their | We are grateful to Rene Struik and Robert Moskowitz for their | |||
| comments that lead to many improvements to this document. | comments that lead to many improvements to this document. | |||
| 8. Change Log | 8. Change Log | |||
| o submitted version -00 as a working group draft after adoption, and | o submitted version -00 as a working group draft after adoption, and | |||
| corrected the order of authors | corrected the order of authors | |||
| o submitted version -01 with no changes | ||||
| 9. References | 9. References | |||
| 9.1. Normative References | 9.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, | Requirement Levels", BCP 14, RFC 2119, | |||
| DOI 10.17487/RFC2119, March 1997, | DOI 10.17487/RFC2119, March 1997, | |||
| <http://www.rfc-editor.org/info/rfc2119>. | <http://www.rfc-editor.org/info/rfc2119>. | |||
| [RFC3971] Arkko, J., Ed., Kempf, J., Zill, B., and P. Nikander, | [RFC3971] Arkko, J., Ed., Kempf, J., Zill, B., and P. Nikander, | |||
| skipping to change at page 16, line 51 ¶ | skipping to change at page 16, line 51 ¶ | |||
| <http://www.rfc-editor.org/info/rfc7696>. | <http://www.rfc-editor.org/info/rfc7696>. | |||
| [RFC7748] Langley, A., Hamburg, M., and S. Turner, "Elliptic Curves | [RFC7748] Langley, A., Hamburg, M., and S. Turner, "Elliptic Curves | |||
| for Security", RFC 7748, DOI 10.17487/RFC7748, January | for Security", RFC 7748, DOI 10.17487/RFC7748, January | |||
| 2016, <http://www.rfc-editor.org/info/rfc7748>. | 2016, <http://www.rfc-editor.org/info/rfc7748>. | |||
| 9.2. Informative references | 9.2. Informative references | |||
| [I-D.ietf-6lo-backbone-router] | [I-D.ietf-6lo-backbone-router] | |||
| Thubert, P., "IPv6 Backbone Router", draft-ietf-6lo- | Thubert, P., "IPv6 Backbone Router", draft-ietf-6lo- | |||
| backbone-router-02 (work in progress), September 2016. | backbone-router-03 (work in progress), January 2017. | |||
| [I-D.ietf-6tisch-architecture] | [I-D.ietf-6tisch-architecture] | |||
| Thubert, P., "An Architecture for IPv6 over the TSCH mode | Thubert, P., "An Architecture for IPv6 over the TSCH mode | |||
| of IEEE 802.15.4", draft-ietf-6tisch-architecture-10 (work | of IEEE 802.15.4", draft-ietf-6tisch-architecture-11 (work | |||
| in progress), June 2016. | in progress), January 2017. | |||
| [I-D.ietf-6man-ipv6-address-generation-privacy] | [I-D.ietf-6man-ipv6-address-generation-privacy] | |||
| Cooper, A., Gont, F., and D. Thaler, "Privacy | Cooper, A., Gont, F., and D. Thaler, "Privacy | |||
| Considerations for IPv6 Address Generation Mechanisms", | Considerations for IPv6 Address Generation Mechanisms", | |||
| draft-ietf-6man-ipv6-address-generation-privacy-08 (work | draft-ietf-6man-ipv6-address-generation-privacy-08 (work | |||
| in progress), September 2015. | in progress), September 2015. | |||
| Authors' Addresses | Authors' Addresses | |||
| Behcet Sarikaya (editor) | Behcet Sarikaya (editor) | |||
| End of changes. 8 change blocks. | ||||
| 8 lines changed or deleted | 10 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/ | ||||