idnits 2.17.1 draft-petrescu-6man-ll-32-ietf-iana-request-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. == The 'Updates: ' line in the draft header should list only the _numbers_ of the RFCs which will be updated by this document (if approved); it should not include the word 'RFC' in the list. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (April 19, 2019) is 1833 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 6MAN Working Group A. Petrescu 3 Internet-Draft CEA, LIST 4 Updates: RFC4291 (if approved) April 19, 2019 5 Intended status: Standards Track 6 Expires: October 21, 2019 8 A request to IETF / IANA to Allocate a 32bit Link-Local Prefix 9 draft-petrescu-6man-ll-32-ietf-iana-request-01 11 Abstract 13 This draft requests IETF / IANA to assign the link local prefix 14 fe80:1::/32 for use in vehicular networks. 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at https://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on October 21, 2019. 33 Copyright Notice 35 Copyright (c) 2019 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (https://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Definitions and Statements . . . . . . . . . . . . . . . . . 2 51 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 52 3. Security Considerations . . . . . . . . . . . . . . . . . . . 2 53 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 54 5. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 2 55 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 2 56 7. Normative References . . . . . . . . . . . . . . . . . . . . 2 57 Appendix A. ChangeLog . . . . . . . . . . . . . . . . . . . . . 3 58 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 60 1. Definitions and Statements 62 The prefix of an IP address is formed by the n leftmost bits of the 63 address. (in a left-to-right writing system). 65 2. Terminology 67 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 68 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 69 document are to be interpreted as described in RFC 2119 [RFC2119]. 71 3. Security Considerations 73 There can be security risks in the use of link-local addressed 74 packets if they are not protected by tecnologies like IPsec. The 75 risks are valid to all kinds of link-local addresses, be them 76 fe80::/10 or fe80::/64. 78 4. IANA Considerations 80 IANA is requested to assign fe80:1::/32 for use in vehicular 81 networks. 83 5. Contributors 85 Listed from 6man WG discussion. 87 6. Acknowledgements 89 7. Normative References 91 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 92 Requirement Levels", BCP 14, RFC 2119, 93 DOI 10.17487/RFC2119, March 1997, 94 . 96 Appendix A. ChangeLog 98 The changes are listed in reverse chronological order, most recent 99 changes appearing at the top of the list. 101 -01: specified that the allocations should be for vehicular networks. 103 Author's Address 105 Alexandre Petrescu 106 CEA, LIST 107 CEA Saclay 108 Gif-sur-Yvette , Ile-de-France 91190 109 France 111 Phone: +33169089223 112 Email: Alexandre.Petrescu@cea.fr