idnits 2.17.1 draft-bagnulo-shim6-cga-ext-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 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 170. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 147. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 154. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 160. ** 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 70: '... Data Structure MUST be encoded using...' -- The draft header indicates that this document updates RFC3972, but the abstract doesn't seem to mention this, which it should. 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 (October 19, 2005) is 6757 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 (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group M. Bagnulo 2 Internet-Draft UC3M 3 Updates: 3972 (if approved) J. Arkko 4 Expires: April 22, 2006 Ericsson 5 October 19, 2005 7 Cryptographically Generated Addresses (CGA) Extension Field Format 8 draft-bagnulo-shim6-cga-ext-01 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on April 22, 2006. 35 Copyright Notice 37 Copyright (C) The Internet Society (2005). 39 Abstract 41 This document define a Type-Length-Value format for Cryptographically 42 Generated Address (CGA) Extensions. 44 Table of Contents 46 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 47 2. CGA Extension Field Format . . . . . . . . . . . . . . . . . . 3 48 3. IANA considerations . . . . . . . . . . . . . . . . . . . . . . 3 49 4. Security considerations . . . . . . . . . . . . . . . . . . . . 4 50 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 4 51 6. Normative References . . . . . . . . . . . . . . . . . . . . . 4 52 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 53 Intellectual Property and Copyright Statements . . . . . . . . . . 6 55 1. Introduction 57 Cryptographically Generated Address (CGA) specification [1] defines 58 Extension Fields that allow including additional information into the 59 CGA Parameter Data Structure. So far there seems to be enough 60 interest in including additional data items into the CGA Parameter 61 Data Structure through these Extension Fields that it seems 62 reasonable to expect that more than one mechanism will require its 63 usage. In order to simplify the addition of multiple data items, 64 this document defines a Type-Length-Value format for the Extension 65 Fields. 67 2. CGA Extension Field Format 69 Data items to be included in Extension Fields of the CGA Parameter 70 Data Structure MUST be encoded using the following Type-Length-Value 71 (TLV) format: 73 0 1 2 3 74 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 75 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 76 | Extension Type | Extension Data Length | 77 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 78 | | 79 ~ Extension Data ~ 80 | | 81 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 82 . 84 Extension Type: 16-bit identifier of the type of the Extension Field. 86 Extension Data Length: 16-bit unsigned integer. Length of the 87 Extension Data field of this option, in octets. 89 Extension Data: Variable-length field. Extension-Type-specific data. 91 3. IANA considerations 93 This document introduces a new Extension Type name space for use as 94 type tags when new Extensions are defined for CGAs. The values in 95 this name space are 8-bit unsigned integers. Values in this name 96 space are allocated according to the Standards Actions or IESG 97 approval policies defined in RFC2434 [2]. 99 This document does not define any new values in any name space. 101 4. Security considerations 103 No security concerns are raised by the adoption of the CGA Extension 104 format described in this document. 106 5. Acknowledgments 108 This document was reviewed by Tuomas Aura, Stefan Rommer, Julien 109 Laganier and James Kempf. 111 6. Normative References 113 [1] Aura, T., "Cryptographically Generated Addresses (CGA)", 114 RFC 3972, March 2005. 116 [2] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA 117 Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. 119 Authors' Addresses 121 Marcelo Bagnulo 122 Universidad Carlos III de Madrid 123 Av. Universidad 30 124 Leganes, Madrid 28911 125 SPAIN 127 Phone: 34 91 6249500 128 Email: marcelo@it.uc3m.es 129 URI: http://www.it.uc3m.es 131 Jari Arkko 132 Ericsson 133 Jorvas 02420 134 Finland 136 Email: jari.arkko@ericsson.com 138 Intellectual Property Statement 140 The IETF takes no position regarding the validity or scope of any 141 Intellectual Property Rights or other rights that might be claimed to 142 pertain to the implementation or use of the technology described in 143 this document or the extent to which any license under such rights 144 might or might not be available; nor does it represent that it has 145 made any independent effort to identify any such rights. Information 146 on the procedures with respect to rights in RFC documents can be 147 found in BCP 78 and BCP 79. 149 Copies of IPR disclosures made to the IETF Secretariat and any 150 assurances of licenses to be made available, or the result of an 151 attempt made to obtain a general license or permission for the use of 152 such proprietary rights by implementers or users of this 153 specification can be obtained from the IETF on-line IPR repository at 154 http://www.ietf.org/ipr. 156 The IETF invites any interested party to bring to its attention any 157 copyrights, patents or patent applications, or other proprietary 158 rights that may cover technology that may be required to implement 159 this standard. Please address the information to the IETF at 160 ietf-ipr@ietf.org. 162 Disclaimer of Validity 164 This document and the information contained herein are provided on an 165 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 166 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 167 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 168 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 169 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 170 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 172 Copyright Statement 174 Copyright (C) The Internet Society (2005). This document is subject 175 to the rights, licenses and restrictions contained in BCP 78, and 176 except as set forth therein, the authors retain all their rights. 178 Acknowledgment 180 Funding for the RFC Editor function is currently provided by the 181 Internet Society.