idnits 2.17.1 draft-bagnulo-cga-ext-02.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 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 183. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 160. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 167. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 173. ** 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 : ---------------------------------------------------------------------------- ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 72: '... Data Structure MUST be encoded using...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year (Using the creation date from RFC3972, updated by this document, for RFC5378 checks: 2003-06-16) -- 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 (March 17, 2006) is 6613 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 2434 (ref. '2') (Obsoleted by RFC 5226) Summary: 5 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 M. Bagnulo 3 Internet-Draft UC3M 4 Updates: 3972 (if approved) J. Arkko 5 Expires: September 18, 2006 Ericsson 6 March 17, 2006 8 Cryptographically Generated Addresses (CGA) Extension Field Format 9 draft-bagnulo-cga-ext-02 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on September 18, 2006. 36 Copyright Notice 38 Copyright (C) The Internet Society (2006). 40 Abstract 42 This document defines a Type-Length-Value format for 43 Cryptographically Generated Address (CGA) Extensions. This document 44 updates RFC 3972. 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 2. CGA Extension Field Format . . . . . . . . . . . . . . . . . . 3 50 3. IANA considerations . . . . . . . . . . . . . . . . . . . . . . 3 51 4. Security considerations . . . . . . . . . . . . . . . . . . . . 4 52 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 4 53 6. Normative References . . . . . . . . . . . . . . . . . . . . . 4 54 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 55 Intellectual Property and Copyright Statements . . . . . . . . . . 6 57 1. Introduction 59 Cryptographically Generated Address (CGA) specification [1] defines 60 Extension Fields that allow including additional information into the 61 CGA Parameter Data Structure. So far there seems to be enough 62 interest in including additional data items into the CGA Parameter 63 Data Structure through these Extension Fields that it seems 64 reasonable to expect that more than one mechanism will require its 65 usage. In order to simplify the addition of multiple data items, 66 this document updates RFC 3972 [1] and it defines a Type-Length-Value 67 format for the Extension Fields. 69 2. CGA Extension Field Format 71 Data items to be included in Extension Fields of the CGA Parameter 72 Data Structure MUST be encoded using the following Type-Length-Value 73 (TLV) format: 75 0 1 2 3 76 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 77 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 78 | Extension Type | Extension Data Length | 79 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 80 | | 81 ~ Extension Data ~ 82 | | 83 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 84 . 86 Extension Type: 16-bit identifier of the type of the Extension Field. 88 Extension Data Length: 16-bit unsigned integer. Length of the 89 Extension Data field of this option, in octets. 91 Extension Data: Variable-length field. Extension-Type-specific data. 93 3. IANA considerations 95 This document defines a Extension Type field for which IANA is to 96 create and maintain a registry entitled "CGA Extension Type". The 97 values in this name space are 16-bit unsigned integers. Initial 98 values for the CGA Extension Type field are given below; future 99 assignments are to be made through Standards Action [2]. Assignments 100 consist of a name and the value. 102 As recommended in [3], this document makes the following assignments 103 for experimental and testing use: the value 0xFFFD with name 104 Exp_FFFD, the value 0xFFFE with name Exp_FFFE and the value 0xFFFF 105 with name Exp_FFFF. 107 4. Security considerations 109 No security concerns are raised by the adoption of the CGA Extension 110 format described in this document. However, proper security analysis 111 is required when new CGA Extensions are defined in order to make sure 112 that no new vulnerabilities are introduced by them to the existing 113 CGA schemes. 115 5. Acknowledgments 117 Comments to this document were provided by Sam Hartman, Allison 118 Makin, Pekka Savola, Thomas Narten, Tuomas Aura, Stefan Rommer, 119 Julien Laganier and James Kempf. 121 6. Normative References 123 [1] Aura, T., "Cryptographically Generated Addresses (CGA)", 124 RFC 3972, March 2005. 126 [2] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA 127 Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. 129 [3] Narten, T., "Assigning Experimental and Testing Numbers 130 Considered Useful", BCP 82, RFC 3692, January 2004. 132 Authors' Addresses 134 Marcelo Bagnulo 135 Universidad Carlos III de Madrid 136 Av. Universidad 30 137 Leganes, Madrid 28911 138 SPAIN 140 Phone: 34 91 6249500 141 Email: marcelo@it.uc3m.es 142 URI: http://www.it.uc3m.es 144 Jari Arkko 145 Ericsson 146 Jorvas 02420 147 Finland 149 Email: jari.arkko@ericsson.com 151 Intellectual Property Statement 153 The IETF takes no position regarding the validity or scope of any 154 Intellectual Property Rights or other rights that might be claimed to 155 pertain to the implementation or use of the technology described in 156 this document or the extent to which any license under such rights 157 might or might not be available; nor does it represent that it has 158 made any independent effort to identify any such rights. Information 159 on the procedures with respect to rights in RFC documents can be 160 found in BCP 78 and BCP 79. 162 Copies of IPR disclosures made to the IETF Secretariat and any 163 assurances of licenses to be made available, or the result of an 164 attempt made to obtain a general license or permission for the use of 165 such proprietary rights by implementers or users of this 166 specification can be obtained from the IETF on-line IPR repository at 167 http://www.ietf.org/ipr. 169 The IETF invites any interested party to bring to its attention any 170 copyrights, patents or patent applications, or other proprietary 171 rights that may cover technology that may be required to implement 172 this standard. Please address the information to the IETF at 173 ietf-ipr@ietf.org. 175 Disclaimer of Validity 177 This document and the information contained herein are provided on an 178 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 179 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 180 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 181 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 182 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 183 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 185 Copyright Statement 187 Copyright (C) The Internet Society (2006). This document is subject 188 to the rights, licenses and restrictions contained in BCP 78, and 189 except as set forth therein, the authors retain all their rights. 191 Acknowledgment 193 Funding for the RFC Editor function is currently provided by the 194 Internet Society.