A request to IETF / IANA to Allocate a 32bit Link-Local Prefix
draft-petrescu-6man-ll-32-ietf-iana-request-01

Abstract

This draft requests IETF / IANA to assign the link local prefix fe80:1::/32 for use in vehicular networks.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on October 21, 2019.

Copyright Notice

Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

• 1. Definitions and Statements
• 2. Terminology
• 3. Security Considerations
• 4. IANA Considerations
• 5. Contributors
• 6. Acknowledgements
• 7. Normative References
• Appendix A. ChangeLog
• Author's Address

1. Definitions and Statements

The prefix of an IP address is formed by the n leftmost bits of the address. (in a left-to-right writing system).

2. Terminology

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

3. Security Considerations

There can be security risks in the use of link-local addressed packets if they are not protected by tecnologies like IPsec. The risks are valid to all kinds of link-local addresses, be them fe80::/10 or fe80::/64.

4. IANA Considerations

IANA is requested to assign fe80:1::/32 for use in vehicular networks.

5. Contributors

Listed from 6man WG discussion.

6. Acknowledgements

7. Normative References

Appendix A. ChangeLog

The changes are listed in reverse chronological order, most recent changes appearing at the top of the list.

-01: specified that the allocations should be for vehicular networks.

Author's Address