idnits 2.17.1 draft-dupont-ipv6-cgpref-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 14. -- Found old boilerplate from RFC 3978, Section 5.5 on line 137. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 114. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 121. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 127. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 23, 2005) is 6882 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) ** Obsolete normative reference: RFC 3513 (Obsoleted by RFC 4291) Summary: 4 errors (**), 0 flaws (~~), 2 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group F. Dupont, Ed. 3 Internet-Draft Point6 4 Expires: December 25, 2005 June 23, 2005 6 An IPv6 Prefix for Cryptographically Generated IDs 7 draft-dupont-ipv6-cgpref-01.txt 9 Status of this Memo 11 By submitting this Internet-Draft, each author represents that any 12 applicable patent or other IPR claims of which he or she is aware 13 have been or will be disclosed, and any of which he or she becomes 14 aware will be disclosed, in accordance with Section 6 of BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on December 25, 2005. 34 Copyright Notice 36 Copyright (C) The Internet Society (2005). 38 Abstract 40 This document proposes the allocation of a dedicated prefix for 41 Cryptographically Generated IDs (CGIDs). This prefix makes the 42 distinction between a CGID and a real IPv6 global address trivial. 44 1. Introduction 46 Some ideas floating at the IETF are about Cryptographically Generated 47 IDs which provide intrinsic proofs of ownership. Cryptographically 48 Generated Addresses [RFC3972] are an example but this document 49 addresses some needs for CGIDs using the global unicast IPv6 address 50 format [RFC3587]. 52 If all CGIDs use a dedicated prefix, marked as not routable, then the 53 distinction between a CGID and a real global unicast IPv6 address 54 will be instantaneous. With such a prefix on n bits, a CGID will be 55 the concatenation of the n bits of the prefix followed by 128 - n 56 bits cryptographically generated (i.e., from the result of a hash 57 function applied to parameters, including in many examples a public 58 RSA key). 60 2. Security Considerations 62 The generation of a CGID should use a random value, like the CGA 63 modifier, in order to make it unpredictable. A small value of "n" 64 makes collisions statically impossible and direct attacks very hard. 66 3. IANA Considerations 68 This document argues in favour of the allocation of a dedicated 69 prefix of 16 to 32 bits in length from the global unicast space. 70 IANA is in charge of allocations in this space [RFC3513]. 72 4. Acknowledgments 74 Gabriel Montenegro was the first to present the CGID idea. IANA 75 people helped us to find a reasonable range for the "n" value. 77 5. References 79 5.1 Normative References 81 [RFC3513] Hinden, R. and S. Deering, "Internet Protocol Version 6 82 (IPv6) Addressing Architecture", RFC 3513, April 2003. 84 5.2 Informative References 86 [RFC3587] Hinden, R., Deering, S., and E. Nordmark, "IPv6 Global 87 Unicast Address Format", RFC 3587, August 2003. 89 [RFC3972] Aura, T., "Cryptographically Generated Addresses (CGA)", 90 RFC 3972, March 2005. 92 Author's Address 94 Francis Dupont (editor) 95 Point6 96 c/o GET/ENST Bretagne 97 2 rue de la Chataigneraie 98 CS 17607 99 35576 Cesson-Sevigne Cedex 100 France 102 Fax: +33 2 99 12 70 30 103 Email: Francis.Dupont@enst-bretagne.fr 105 Intellectual Property Statement 107 The IETF takes no position regarding the validity or scope of any 108 Intellectual Property Rights or other rights that might be claimed to 109 pertain to the implementation or use of the technology described in 110 this document or the extent to which any license under such rights 111 might or might not be available; nor does it represent that it has 112 made any independent effort to identify any such rights. Information 113 on the procedures with respect to rights in RFC documents can be 114 found in BCP 78 and BCP 79. 116 Copies of IPR disclosures made to the IETF Secretariat and any 117 assurances of licenses to be made available, or the result of an 118 attempt made to obtain a general license or permission for the use of 119 such proprietary rights by implementers or users of this 120 specification can be obtained from the IETF on-line IPR repository at 121 http://www.ietf.org/ipr. 123 The IETF invites any interested party to bring to its attention any 124 copyrights, patents or patent applications, or other proprietary 125 rights that may cover technology that may be required to implement 126 this standard. Please address the information to the IETF at 127 ietf-ipr@ietf.org. 129 Disclaimer of Validity 131 This document and the information contained herein are provided on an 132 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 133 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 134 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 135 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 136 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 137 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 139 Copyright Statement 141 Copyright (C) The Internet Society (2005). This document is subject 142 to the rights, licenses and restrictions contained in BCP 78, and 143 except as set forth therein, the authors retain all their rights. 145 Acknowledgment 147 Funding for the RFC Editor function is currently provided by the 148 Internet Society.