idnits 2.17.1 draft-ietf-mip4-message-string-ext-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 on line 270. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 247. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 254. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 260. ** 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 : ---------------------------------------------------------------------------- == There are 2 instances of lines with non-RFC2606-compliant FQDNs in the document. ** 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 126: '... and MUST NOT affect operation of...' RFC 2119 keyword, line 141: '...n Agent or both, MAY add the extension...' RFC 2119 keyword, line 163: '...gistration Revocation message, it MUST...' RFC 2119 keyword, line 169: '...on Reply message, it MUST appear after...' RFC 2119 keyword, line 171: '...so the extension MUST appear before th...' 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 (January 09, 2006) is 6675 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) == Unused Reference: 'FA-ERR' is defined on line 192, but no explicit reference was found in the text == Unused Reference: 'RFC2865' is defined on line 199, but no explicit reference was found in the text == Unused Reference: 'RFC3543' is defined on line 206, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2279 (Obsoleted by RFC 3629) ** Obsolete normative reference: RFC 3344 (Obsoleted by RFC 5944) Summary: 6 errors (**), 0 flaws (~~), 6 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group V. Sastry 3 Internet-Draft K. Leung 4 Expires: July 13, 2006 A. Patel 5 Cisco Systems 6 January 09, 2006 8 Mobile IPv4 Message String Extension 9 draft-ietf-mip4-message-string-ext-00.txt 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 July 13, 2006. 36 Copyright Notice 38 Copyright (C) The Internet Society (2006). 40 Abstract 42 This document specifies a new extension for use in Mobile IPv4. This 43 extension can be added by the Home Agent and the Foreign Agent to 44 Registration Reply message. This extension carries a text string 45 that is intended for the user of the Mobile Node. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 50 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 51 3. Mobile IPv4 Message String Extension Format . . . . . . . . . 5 52 4. Operation and Use of the Message String Extension . . . . . . 7 53 5. Security Considerations . . . . . . . . . . . . . . . . . . . 8 54 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 55 7. Normative References . . . . . . . . . . . . . . . . . . . . . 9 56 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 57 Intellectual Property and Copyright Statements . . . . . . . . . . 11 59 1. Introduction 61 This document specifies a new skippable extension that can be added 62 by Foreign Agent and Home Agent in registration message targeted for 63 the Mobile Node. Such a message may be either a Registration Reply 64 or Registration Revocation (i.e. collocated Care-of Address mode). 65 For the Registration Reply message, this extension can be added 66 regardless of whether the registration has succeeded or failed. 68 Content of the text string in this extension and its usage by Mobile 69 Node is implementation specific. The text string in this extension 70 is intended for the user of the Mobile Node. For example, this 71 message can be displayed on the Mobile Node's user interface, logged 72 or handled in any other implementation dependent way, depending on 73 the form of the Mobile Node. 75 Typical contents of the text string will indicate registration 76 failure reason, or a welcome message on successful registration. 77 This is important as the failure reason code gives very limited 78 information for interpretation by the user of the Mobile Node. A 79 string like "registration failed : Prepaid Quota for the user is 80 exhausted", "registration success : Unauthorized Access is 81 Prohibited", can give a human readable description of the result of 82 Mobile IP registration. 84 2. Terminology 86 The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 87 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 88 document are to be interpreted as described in RFC 2119. 90 3. Mobile IPv4 Message String Extension Format 92 The Message String Extension conforms to the Short Extension format 93 specified for Mobile IPv4 [RFC3344]. The Message String Extension is 94 a skippable extension. 96 0 1 2 3 97 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 98 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 99 | Type | Length | Sub-Type | Text .... 100 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 102 Type: 104 To be assigned by IANA. An 8-bit identifier of the type mobility 105 option. 107 Length: 109 8-bit unsigned integer, equaling 1 plus the length in octets of 110 the Text 112 Sub-Type: 114 1: 116 Extension is added by Home Agent 118 2: 120 Extension is added by Foreign Agent 122 Text: 124 The Text field is one or more octets, and its contents are 125 implementation dependent. It is intended to be human readable, 126 and MUST NOT affect operation of the protocol. It is recommended 127 that the message contain UTF-8 encoded 10646 [RFC2279] characters. 129 4. Operation and Use of the Message String Extension 131 The Message String Extension is only valid for use within Mobile IPv4 132 Registration Reply and Registration Revocation messages. The Message 133 String Extension is a skippable extension. Either Home Agent or 134 Foreign Agent or both can add Message String Extension to 135 registration messages. Usage of Text field of the Message String 136 Extension is implementation dependent. For example, this message can 137 be displayed on the Mobile Node's user interface, logged or handled 138 in an implementation dependent way, depending on the form of the 139 Mobile Node. 141 Home Agent or Foreign Agent or both, MAY add the extension to each 142 registration message to a Mobile Node. However, Mobile Node may 143 throttle how often the user is notified of the message (either via 144 display on user interface, logging, etc.) For example, Home Agent 145 may reject the first Registration Request due to prepaid quota for 146 the user is reached and may attach a Message String Extension with 147 the text "Prepaid quota reached. Please contact www.paymore.com to 148 update balance". Mobile Node could display this on the user 149 interface. As a response user of the Mobile Node may take the 150 required action to update the prepaid account and retry the 151 registration process. Home Agent may accept this Registration 152 Request and attach a Message String Extension with the text "Welcome 153 to www.serviceprovider.com". Mobile Node could display this on the 154 user interface thus confirming successful creation of binding on Home 155 Agent. 157 5. Security Considerations 159 Message String Extension can be added by Home Agent or Foreign Agent 160 or both. 162 If the extension is added by the Home Agent (extension with subtype 163 1) to Registration Reply or Registration Revocation message, it MUST 164 appear before Mobile-Home Authentication Extension [RFC3344]. If the 165 the Mobile Node cannot understand this extension, it should be 166 skipped. 168 If the extension is added by the Foreign Agent (extension with 169 subtype 2) to Registration Reply message, it MUST appear after 170 Mobile-Home Authentication Extension [RFC3344] whenever present. 171 Also the extension MUST appear before the Mobile-Foreign 172 Authentication Extension whenever present. If Mobile Node cannot 173 understand this extension, it should be skipped. 175 6. IANA Considerations 177 This specification reserves one number for the Message String 178 Extension Section 3 from the space of numbers for skippable mobility 179 extensions (i.e., 128-255) defined for Mobile IPv4 [RFC3344] at 180 http://www.iana.org/assignments/mobileip-numbers. 182 The value 145 is recommended for this extension. 184 This specification also creates a new subtype space for the type 185 number of this extension. The subtype values 1 and 2 are defined in 186 this specification. The subtype value 1 is reserved for use by Home 187 Agent and subtype value 2 is reserved for use by Foreign Agent. 188 Other values can be allocated from this number space by IANA actions. 190 7. Normative References 192 [FA-ERR] Perkins, C., "Foreign Agent Error Extension for Mobile 193 IPv4", draft-ietf-mip4-faerr-02.txt (work in progress), 194 September 2005. 196 [RFC2279] Yergeau, F., "UTF-8, a transformation format of ISO 197 10646", RFC 2279, January 1998. 199 [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, 200 "Remote Authentication Dial In User Service (RADIUS)", 201 RFC 2865, June 2000. 203 [RFC3344] Perkins, C., "IP Mobility Support for IPv4", RFC 3344, 204 August 2002. 206 [RFC3543] Glass, S. and M. Chandra, "Registration Revocation in 207 Mobile IPv4", RFC 3543, August 2003. 209 Authors' Addresses 211 Venkateshwara Sastry 212 Cisco Systems 213 Akkithimanahalli, O'Shaugnessy Road 214 Bangalore 560085 215 India 217 Phone: +91 80-51033757 218 Email: vsastry@cisco.com 220 Kent Leung 221 Cisco Systems 222 170 W. Tasman Drive 223 San Jose, CA 95134 224 US 226 Phone: +1 408-526-5030 227 Email: kleung@cisco.com 229 Alpesh Patel 230 Cisco Systems 231 170 W. Tasman Drive 232 San Jose, CA 95134 233 US 235 Phone: +1 408-853-9580 236 Email: alpesh@cisco.com 238 Intellectual Property Statement 240 The IETF takes no position regarding the validity or scope of any 241 Intellectual Property Rights or other rights that might be claimed to 242 pertain to the implementation or use of the technology described in 243 this document or the extent to which any license under such rights 244 might or might not be available; nor does it represent that it has 245 made any independent effort to identify any such rights. Information 246 on the procedures with respect to rights in RFC documents can be 247 found in BCP 78 and BCP 79. 249 Copies of IPR disclosures made to the IETF Secretariat and any 250 assurances of licenses to be made available, or the result of an 251 attempt made to obtain a general license or permission for the use of 252 such proprietary rights by implementers or users of this 253 specification can be obtained from the IETF on-line IPR repository at 254 http://www.ietf.org/ipr. 256 The IETF invites any interested party to bring to its attention any 257 copyrights, patents or patent applications, or other proprietary 258 rights that may cover technology that may be required to implement 259 this standard. Please address the information to the IETF at 260 ietf-ipr@ietf.org. 262 Disclaimer of Validity 264 This document and the information contained herein are provided on an 265 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 266 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 267 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 268 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 269 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 270 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 272 Copyright Statement 274 Copyright (C) The Internet Society (2006). This document is subject 275 to the rights, licenses and restrictions contained in BCP 78, and 276 except as set forth therein, the authors retain all their rights. 278 Acknowledgment 280 Funding for the RFC Editor function is currently provided by the 281 Internet Society.