idnits 2.17.1 draft-ietf-behave-stun-test-vectors-00.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, updated by RFC 4748 on line 276. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 287. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 294. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 300. 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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust 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 (December 17, 2007) is 5975 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-18) exists of draft-ietf-behave-rfc3489bis-13 Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Behavior Engineering for Hindrance R. Denis-Courmont 3 Avoidance Nokia 4 Internet-Draft December 17, 2007 5 Intended status: Informational 6 Expires: June 19, 2008 8 Test vectors for STUN 9 draft-ietf-behave-stun-test-vectors-00 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 June 19, 2008. 36 Copyright Notice 38 Copyright (C) The IETF Trust (2007). 40 Abstract 42 This document includes test vectors for the MESSAGE-INTEGRITY and 43 FINGERPRINT attributes of the STUN protocol. 45 Table of Contents 47 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 48 2. Test vectors . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 2.1. Sample request . . . . . . . . . . . . . . . . . . . . . . 3 50 2.2. Sample IPv4 response . . . . . . . . . . . . . . . . . . . 4 51 2.3. Sample IPv6 response . . . . . . . . . . . . . . . . . . . 5 52 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 53 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 54 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 55 6. Normative References . . . . . . . . . . . . . . . . . . . . . 6 56 Appendix A. Source code for test vectors . . . . . . . . . . . . . 6 58 1. Introduction 60 The Session Traversal Utilities for NAT 61 (STUN)[I-D.ietf-behave-rfc3489bis] protocol defines two different 62 hashes that may be included in messages exchanged by peers 63 implementing that protocol: 65 FINGERPRINT attribute: a 32-bits Circular Redundancy Check. 66 MESSAGE-INTEGRITY attribute: a HMAC-SHA1 authentication code. 68 This document documents sample properly-formatted STUN messages 69 including these hashes, for the sake of testing implementations of 70 the STUN protocol. 72 2. Test vectors 74 All included vectors are represented as a series of hexadecimal 75 values in network byte order. Each pair of hexadecimal digits 76 represents one byte. 78 Messages follow the ICE Connectivity Checks use case of STUN, (see 79 [I-D.ietf-mmusic-ice]). They include both FINGERPRINT and MESSAGE- 80 INTEGRITY attributes. 82 2.1. Sample request 84 This request uses the following parameters: 85 Username: "evtj:h6vY" (without quotes) 86 Password: "VOkJxbRl1RmTxUk/WvJxBt" (without quotes) 87 00 01 00 44 Request type and message length 88 21 12 a4 42 Message cookie 89 b7 e7 a7 01 } 90 bc 34 d6 86 } Transaction ID 91 fa 87 df ae } 92 00 24 00 04 93 6e 00 01 ff 94 80 29 00 08 95 93 2f f9 b1 96 51 26 3b 36 97 00 06 00 09 USERNAME attribute header 98 65 76 74 6a } 99 3a 68 36 76 } Username (9 bytes) and padding (3 bytes) 100 59 20 20 20 } 101 00 08 00 14 MESSAGE-INTEGRITY attribute header 102 62 4e eb dc } 103 3c c9 2d d8 } 104 4b 74 bf 85 } HMAC-SHA1 fingerprint 105 d1 c0 f5 de } 106 36 87 bd 33 } 107 80 28 00 04 FINGERPRINT attribute header 108 ad 8a 85 ff CRC32 fingerprint 110 2.2. Sample IPv4 response 112 This response used the following parameter: 113 Password: "VOkJxbRl1RmTxUk/WvJxBt" (without quotes) 114 Mapped address: 192.0.2.1 port 32853 116 01 01 00 3c Response type and message length 117 21 12 a4 42 Message cookie 118 b7 e7 a7 01 } 119 bc 34 d6 86 } Transaction ID 120 fa 87 df ae } 121 80 22 00 0b 122 74 65 73 74 123 20 76 65 63 124 74 6f 72 20 125 00 20 00 08 126 00 01 a1 47 127 e1 12 a6 43 128 00 08 00 14 MESSAGE-INTEGRITY attribute header 129 2b 91 f5 99 } 130 fd 9e 90 c3 } 131 8c 74 89 f9 } HMAC-SHA1 fingerprint 132 2a f9 ba 53 } 133 f0 6b e7 d7 } 134 80 28 00 04 FINGERPRINT attribute header 135 c0 7d 4c 96 CRC32 fingerprint 137 2.3. Sample IPv6 response 139 This response used the following parameter: 140 Password: "VOkJxbRl1RmTxUk/WvJxBt" (without quotes) 141 Mapped address: 2001:db8:1234:5678:11:2233:4455:6677 port 32853 143 01 01 00 48 Response type and message length 144 21 12 a4 42 Message cookie 145 b7 e7 a7 01 } 146 bc 34 d6 86 } Transaction ID 147 fa 87 df ae } 148 80 22 00 0b 149 74 65 73 74 150 20 76 65 63 151 74 6f 72 20 152 00 20 00 14 153 00 02 a1 47 154 01 13 a9 fa 155 a5 d3 f1 79 156 bc 25 f4 b5 157 be d2 b9 d9 158 00 08 00 14 MESSAGE-INTEGRITY attribute header 159 a3 82 95 4e } 160 4b e6 7b f1 } 161 17 84 c9 7c } HMAC-SHA1 fingerprint 162 82 92 c2 75 } 163 bf e3 ed 41 } 164 80 28 00 04 FINGERPRINT attribute header 165 c8 fb 0b 4c CRC32 fingerprint 167 3. Security Considerations 169 There are no security considerations. 171 4. IANA Considerations 173 This document raises no IANA considerations. 175 5. Acknowledgements 177 The author would like to thank Marc Petit-Huguenin for his comments, 178 and Brian Korver, Alfred E. Heggestad and Gustavo Garcia for their 179 review. 181 6. Normative References 183 [I-D.ietf-behave-rfc3489bis] Rosenberg, J., Mahy, R., Matthews, P., 184 and D. Wing, "Session Traversal 185 Utilities for (NAT) (STUN)", 186 draft-ietf-behave-rfc3489bis-13 (work 187 in progress), November 2007. 189 [I-D.ietf-mmusic-ice] Rosenberg, J., "Interactive 190 Connectivity Establishment (ICE): A 191 Protocol for Network Address 192 Translator (NAT) Traversal for Offer/ 193 Answer Protocols", 194 draft-ietf-mmusic-ice-19 (work in 195 progress), October 2007. 197 Appendix A. Source code for test vectors 199 const unsigned char req[] = 200 "\x00\x01\x00\x44" 201 "\x21\x12\xa4\x42" 202 "\xb7\xe7\xa7\x01\xbc\x34\xd6\x86\xfa\x87\xdf\xae" 203 "\x00\x24\x00\x04" 204 "\x6e\x00\x01\xff" 205 "\x80\x29\x00\x08" 206 "\x93\x2f\xf9\xb1\x51\x26\x3b\x36" 207 "\x00\x06\x00\x09" 208 "\x65\x76\x74\x6a\x3a\x68\x36\x76\x59\x20\x20\x20" 209 "\x00\x08\x00\x14" 210 "\x62\x4e\xeb\xdc\x3c\xc9\x2d\xd8\x4b\x74\xbf\x85" 211 "\xd1\xc0\xf5\xde\x36\x87\xbd\x33" 212 "\x80\x28\x00\x04" 213 "\xad\x8a\x85\xff"; 215 Request message 217 const unsigned char respv4[] = 218 "\x01\x01\x00\x3c" 219 "\x21\x12\xa4\x42" 220 "\xb7\xe7\xa7\x01\xbc\x34\xd6\x86\xfa\x87\xdf\xae" 221 "\x80\x22\x00\x0b" 222 "\x74\x65\x73\x74\x20\x76\x65\x63\x74\x6f\x72\x20" 223 "\x00\x20\x00\x08" 224 "\x00\x01\xa1\x47\xe1\x12\xa6\x43" 225 "\x00\x08\x00\x14" 226 "\x2b\x91\xf5\x99\xfd\x9e\x90\xc3\x8c\x74\x89\xf9" 227 "\x2a\xf9\xba\x53\xf0\x6b\xe7\xd7" 228 "\x80\x28\x00\x04" 229 "\xc0\x7d\x4c\x96"; 231 IPv4 response message 233 const unsigned char respv6[] = 234 "\x01\x01\x00\x48" 235 "\x21\x12\xa4\x42" 236 "\xb7\xe7\xa7\x01\xbc\x34\xd6\x86\xfa\x87\xdf\xae" 237 "\x80\x22\x00\x0b" 238 "\x74\x65\x73\x74\x20\x76\x65\x63\x74\x6f\x72\x20" 239 "\x00\x20\x00\x14" 240 "\x00\x02\xa1\x47" 241 "\x01\x13\xa9\xfa\xa5\xd3\xf1\x79" 242 "\xbc\x25\xf4\xb5\xbe\xd2\xb9\xd9" 243 "\x00\x08\x00\x14" 244 "\xa3\x82\x95\x4e\x4b\xe6\x7b\xf1\x17\x84\xc9\x7c" 245 "\x82\x92\xc2\x75\xbf\xe3\xed\x41" 246 "\x80\x28\x00\x04" 247 "\xc8\xfb\x0b\x4c"; 249 IPv6 response message 251 Author's Address 253 Remi Denis-Courmont 254 Nokia Corporation 255 P.O. Box 407 256 NOKIA GROUP 00045 257 FI 259 Phone: +358 50 487 6315 260 EMail: remi.denis-courmont@nokia.com 262 Full Copyright Statement 264 Copyright (C) The IETF Trust (2007). 266 This document is subject to the rights, licenses and restrictions 267 contained in BCP 78, and except as set forth therein, the authors 268 retain all their rights. 270 This document and the information contained herein are provided on an 271 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 272 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 273 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 274 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 275 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 276 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 278 Intellectual Property 280 The IETF takes no position regarding the validity or scope of any 281 Intellectual Property Rights or other rights that might be claimed to 282 pertain to the implementation or use of the technology described in 283 this document or the extent to which any license under such rights 284 might or might not be available; nor does it represent that it has 285 made any independent effort to identify any such rights. Information 286 on the procedures with respect to rights in RFC documents can be 287 found in BCP 78 and BCP 79. 289 Copies of IPR disclosures made to the IETF Secretariat and any 290 assurances of licenses to be made available, or the result of an 291 attempt made to obtain a general license or permission for the use of 292 such proprietary rights by implementers or users of this 293 specification can be obtained from the IETF on-line IPR repository at 294 http://www.ietf.org/ipr. 296 The IETF invites any interested party to bring to its attention any 297 copyrights, patents or patent applications, or other proprietary 298 rights that may cover technology that may be required to implement 299 this standard. Please address the information to the IETF at 300 ietf-ipr@ietf.org. 302 Acknowledgement 304 Funding for the RFC Editor function is provided by the IETF 305 Administrative Support Activity (IASA).