| draft-ietf-dhc-addr-notification-09.txt | draft-ietf-dhc-addr-notification-10.txt | |||
|---|---|---|---|---|
| Dynamic Host Configuration W. Kumari | Dynamic Host Configuration W. Kumari | |||
| Internet-Draft Google, LLC | Internet-Draft Google, LLC | |||
| Intended status: Standards Track S. Krishnan | Intended status: Standards Track S. Krishnan | |||
| Expires: 29 July 2024 R. Asati | Expires: 27 September 2024 Cisco Systems, Inc. | |||
| Cisco Systems, Inc. | R. Asati | |||
| Independent | ||||
| L. Colitti | L. Colitti | |||
| J. Linkova | J. Linkova | |||
| Google, LLC | Google, LLC | |||
| S. Jiang | S. Jiang | |||
| Beijing University of Posts and Telecommunications | Beijing University of Posts and Telecommunications | |||
| 26 January 2024 | 26 March 2024 | |||
| Registering Self-generated IPv6 Addresses using DHCPv6 | Registering Self-generated IPv6 Addresses using DHCPv6 | |||
| draft-ietf-dhc-addr-notification-09 | draft-ietf-dhc-addr-notification-10 | |||
| Abstract | Abstract | |||
| This document defines a method to inform a DHCPv6 server that a | This document defines a method to inform a DHCPv6 server that a | |||
| device has a self-generated or statically configured address. | device has a self-generated or statically configured address. | |||
| About This Document | About This Document | |||
| This note is to be removed before publishing as an RFC. | This note is to be removed before publishing as an RFC. | |||
| skipping to change at page 2, line 10 ¶ | skipping to change at page 2, line 15 ¶ | |||
| 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 29 July 2024. | This Internet-Draft will expire on 27 September 2024. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2024 IETF Trust and the persons identified as the | Copyright (c) 2024 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 (https://trustee.ietf.org/ | Provisions Relating to IETF Documents (https://trustee.ietf.org/ | |||
| license-info) in effect on the date of publication of this document. | license-info) in effect on the date of publication of this document. | |||
| Please review these documents carefully, as they describe your rights | Please review these documents carefully, as they describe your rights | |||
| skipping to change at page 13, line 49 ¶ | skipping to change at page 13, line 49 ¶ | |||
| between hosts. | between hosts. | |||
| One of the use cases for the mechanism described in this document is | One of the use cases for the mechanism described in this document is | |||
| to identify sources of malicious traffic after the fact. Note, | to identify sources of malicious traffic after the fact. Note, | |||
| however, that as the device itself is responsible for informing the | however, that as the device itself is responsible for informing the | |||
| DHCPv6 server that it is using an address, a malicious or compromised | DHCPv6 server that it is using an address, a malicious or compromised | |||
| device can simply not send the ADDR-REG-INFORM message. This is an | device can simply not send the ADDR-REG-INFORM message. This is an | |||
| informational, optional mechanism, and is designed to aid in | informational, optional mechanism, and is designed to aid in | |||
| troubleshooting and forensics. On its own, it is not intended to be | troubleshooting and forensics. On its own, it is not intended to be | |||
| a strong security access mechanism. In particular, the ADDR-REG- | a strong security access mechanism. In particular, the ADDR-REG- | |||
| INFORM message MUST not be used for authentication and authorization | INFORM message MUST NOT be used for authentication and authorization | |||
| purposes, because in addition to the reasons above, the packets | purposes, because in addition to the reasons above, the packets | |||
| containing the message may be dropped. | containing the message may be dropped. | |||
| 7. IANA Considerations | 7. IANA Considerations | |||
| This document introduces the following new entities which require an | This document introduces the following new entities which require an | |||
| allocation out of the DHCPv6 registries defined at | allocation out of the DHCPv6 registries defined at | |||
| http://www.iana.org/assignments/dhcpv6-parameters/: | http://www.iana.org/assignments/dhcpv6-parameters/: | |||
| * one new DHCPv6 option, described in Section 4.1 which requires an | * one new DHCPv6 option, described in Section 4.1 which requires an | |||
| skipping to change at page 16, line 26 ¶ | skipping to change at page 16, line 26 ¶ | |||
| Warren Kumari | Warren Kumari | |||
| Google, LLC | Google, LLC | |||
| Email: warren@kumari.net | Email: warren@kumari.net | |||
| Suresh Krishnan | Suresh Krishnan | |||
| Cisco Systems, Inc. | Cisco Systems, Inc. | |||
| Email: suresh.krishnan@gmail.com | Email: suresh.krishnan@gmail.com | |||
| Rajiv Asati | Rajiv Asati | |||
| Cisco Systems, Inc. | Independent | |||
| 7025 Kit Creek road | Email: rajiv.asati@gmail.com | |||
| Research Triangle Park, 27709-4987 | ||||
| United States of America | ||||
| Email: rajiva@cisco.com | ||||
| Lorenzo Colitti | Lorenzo Colitti | |||
| Google, LLC | Google, LLC | |||
| Shibuya 3-21-3, | Shibuya 3-21-3, | |||
| Japan | Japan | |||
| Email: lorenzo@google.com | Email: lorenzo@google.com | |||
| Jen Linkova | Jen Linkova | |||
| Google, LLC | Google, LLC | |||
| 1 Darling Island Rd | 1 Darling Island Rd | |||
| Pyrmont 2009 | Pyrmont 2009 | |||
| Australia | Australia | |||
| Email: furry@google.com | Email: furry13@gmail.com | |||
| Sheng Jiang | Sheng Jiang | |||
| Beijing University of Posts and Telecommunications | Beijing University of Posts and Telecommunications | |||
| No. 10 Xitucheng Road | No. 10 Xitucheng Road | |||
| Beijing | Beijing | |||
| Haidian District, 100083 | Haidian District, 100083 | |||
| China | China | |||
| Email: shengjiang@bupt.edu.cn | Email: shengjiang@bupt.edu.cn | |||
| End of changes. 7 change blocks. | ||||
| 12 lines changed or deleted | 10 lines changed or added | |||
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||