draft-ietf-mip4-message-string-ext-01.txt   draft-ietf-mip4-message-string-ext-02.txt 
Network Working Group V. Sastry MIP4 V. Sastry
Internet-Draft K. Leung Internet-Draft Samsung Electronics
Intended status: Standards Track A. Patel Intended status: Standards Track K. Leung
Expires: March 18, 2007 Cisco Systems Expires: July 19, 2007 A. Patel
September 14, 2006 Cisco Systems
January 15, 2007
Mobile IPv4 Message String Extension Mobile IPv4 Message String Extension
draft-ietf-mip4-message-string-ext-01.txt draft-ietf-mip4-message-string-ext-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 36
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on March 18, 2007. This Internet-Draft will expire on July 19, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document specifies a new extension for use in Mobile IPv4. This This document specifies a new extension for use in Mobile IPv4. This
extension can be added by the Home Agent and the Foreign Agent to extension can be added by the Home Agent and the Foreign Agent to
Registration Reply message. This extension carries a text string Registration Reply messages. This extension carries a text string
that is intended for the user of the Mobile Node. that is intended for the user of the Mobile Node.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Mobile IPv4 Message String Extension Format . . . . . . . . . 5 3. Mobile IPv4 Message String Extension Format . . . . . . . . . 5
4. Operation and Use of the Message String Extension . . . . . . 7 4. Operation and Use of the Message String Extension . . . . . . 7
5. Security Considerations . . . . . . . . . . . . . . . . . . . 8 5. Security Considerations . . . . . . . . . . . . . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10
8. Normative References . . . . . . . . . . . . . . . . . . . . . 11 8. Normative References . . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
Intellectual Property and Copyright Statements . . . . . . . . . . 13 Intellectual Property and Copyright Statements . . . . . . . . . . 13
1. Introduction 1. Introduction
This document specifies a new skippable extension that can be added This document specifies a new skippable extension that can be added
by Foreign Agent and Home Agent in registration message targeted for by the Foreign Agent and Home Agent in any registration message
the Mobile Node. Such a message may be either a Registration Reply targeted for the Mobile Node. Such a message may be either a
or Registration Revocation (i.e. collocated Care-of Address mode). Registration Reply or Registration Revocation (i.e. co-located
For the Registration Reply message, this extension can be added Care-of Address mode). For the Registration Reply message, this
regardless of whether the registration has succeeded or failed. extension can be added regardless of whether the registration has
succeeded or failed.
Content of the text string in this extension and its usage by Mobile The content of the text string in this extension and its usage by the
Node is implementation specific. The text string in this extension Mobile Node is implementation specific. The text string in this
is intended for the user of the Mobile Node. For example, this extension is intended for the user of the Mobile Node. For example,
message can be displayed on the Mobile Node's user interface, logged this message can be displayed on the Mobile Node's user interface,
or handled in any other implementation dependent way, depending on logged, or handled in any other implementation dependent way,
the form of the Mobile Node. depending on the form of the Mobile Node.
Typical contents of the text string will indicate registration Typical contents of the text string will indicate a registration
failure reason, or a welcome message on successful registration. failure reason, or give a welcome message on successful registration.
This is important as the failure reason code gives very limited This is important as the failure reason code gives very limited
information for interpretation by the user of the Mobile Node. A information for interpretation by the user of the Mobile Node. For
string like "registration failed : Prepaid Quota for the user is example, a string like "registration failed : Prepaid Quota for the
exhausted", "registration success : Unauthorized Access is user is exhausted" can give a human readable description of the
Prohibited", can give a human readable description of the result of result of Mobile IP registration.
Mobile IP registration.
2. Terminology 2. Terminology
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119. document are to be interpreted as described in RFC 2119 [RFC2119].
3. Mobile IPv4 Message String Extension Format 3. Mobile IPv4 Message String Extension Format
The Message String Extension conforms to the Short Extension format The Message String Extension conforms to the Short Extension format
specified for Mobile IPv4 [RFC3344]. The Message String Extension is specified for Mobile IPv4 [RFC3344]. The Message String Extension is
a skippable extension. a skippable extension.
0 1 2 3 0 1 2 3
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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Sub-Type | Text .... | Type | Length | Sub-Type | Text ....
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: Type:
To be assigned by IANA. An 8-bit identifier of the type mobility To be assigned by IANA. An 8-bit identifier of the type mobility
option. option.
Length: Length:
8-bit unsigned integer, equaling 1 plus the length in octets of 8-bit unsigned integer. Length of the extension, in bytes,
the Text excluding the extension Type and the extension Length fields.
This field MUST be set to 1 plus the total length of the Text
field.
Sub-Type: Sub-Type:
1: 1:
Extension is added by Home Agent Extension comes from the Home Agent
2: 2:
Extension is added by Foreign Agent Extension comes from the Foreign Agent
Text: Text:
The Text field is one or more octets, and its contents are The Text field is one or more octets, and its contents are
implementation dependent. It is intended to be human readable, implementation dependent. It is intended to be human readable,
and MUST NOT affect operation of the protocol. It is recommended and MUST NOT affect operation of the protocol. It is RECOMMENDED
that the message contain UTF-8 encoded 10646 [RFC3629] characters. that the message contain UTF-8 encoded 10646 [RFC3629] characters.
The number of octets in the UTF-8 representation of the message is The number of octets in the encoded representation of the message
exactly the value of the Length field minus one. is always exactly the value of the Length field minus one. (In
the UTF-8 case, the number of unicode characters represented by
this octet sequence may be smaller than the number of octets.)
Other encoding methods than UTF-8 may only be used in closed
environments where it can be guaranteed that both message sender
and receiver know the exact encoding method, and know that the
encoding method is different from UTF-8.
4. Operation and Use of the Message String Extension 4. Operation and Use of the Message String Extension
The Message String Extension is only valid for use within Mobile IPv4 The Message String Extension is only valid for use within Mobile IPv4
Registration Reply and Registration Revocation messages. The Message Registration Reply and Registration Revocation messages. The Message
String Extension is a skippable extension. Either Home Agent or String Extension is a skippable extension. Either the Home Agent or
Foreign Agent or both can add Message String Extension to Foreign Agent or both can add the Message String Extension to
registration messages. Usage of Text field of the Message String registration messages. The usage of Text field of the Message String
Extension is implementation dependent. For example, this message can Extension is implementation dependent. For example, the message can
be displayed on the Mobile Node's user interface, logged or handled be displayed on the Mobile Node's user interface, logged, or handled
in an implementation dependent way, depending on the form of the in an implementation dependent way, depending on the form of the
Mobile Node. Mobile Node.
Home Agent or Foreign Agent or both, MAY add the extension to each The Mobile Node may throttle how often the user is notified of the
registration message to a Mobile Node. However, Mobile Node may message (either via display on user interface, logging, etc.) For
throttle how often the user is notified of the message (either via example, the Home Agent may reject the first Registration Request due
display on user interface, logging, etc.) For example, Home Agent to prepaid quota for the user is reached and may attach a Message
may reject the first Registration Request due to prepaid quota for String Extension with the text "Prepaid quota reached. Please
the user is reached and may attach a Message String Extension with contact www.paymore.example.com to update balance". The Mobile Node
the text "Prepaid quota reached. Please contact www.paymore.com to could display this on the user interface. As a response, the user of
update balance". Mobile Node could display this on the user the Mobile Node may take the required action to update the prepaid
interface. As a response user of the Mobile Node may take the account and retry the registration process. The Home Agent may
required action to update the prepaid account and retry the accept this Registration Request and attach a Message String
registration process. Home Agent may accept this Registration Extension with the text "Welcome to www.serviceprovider.example.com".
Request and attach a Message String Extension with the text "Welcome The Mobile Node could display this on the user interface thus
to www.serviceprovider.com". Mobile Node could display this on the confirming successful creation of binding on Home Agent.
user interface thus confirming successful creation of binding on Home
Agent.
5. Security Considerations 5. Security Considerations
Message String Extension can be added by Home Agent or Foreign Agent The Message String Extension can be added by the Home Agent or
or both. Foreign Agent or both.
If the extension is added by the Home Agent (extension with subtype If the extension is added by the Home Agent (extension with subtype
1) to Registration Reply or Registration Revocation message, it MUST 1) to a Registration Reply or Registration Revocation message, it
appear before Mobile-Home Authentication Extension [RFC3344]. If the MUST appear before Mobile-Home Authentication Extension [RFC3344].
the Mobile Node cannot understand this extension, it should be
skipped.
If the extension is added by the Foreign Agent (extension with If the extension is added by the Foreign Agent (extension with
subtype 2) to Registration Reply message, it MUST appear after subtype 2) to a Registration Reply message, it MUST appear after
Mobile-Home Authentication Extension [RFC3344] whenever present. Mobile-Home Authentication Extension [RFC3344] whenever present.
Also the extension MUST appear before the Mobile-Foreign Also the extension MUST appear before the Mobile-Foreign
Authentication Extension whenever present. If Mobile Node cannot Authentication Extension whenever present.
understand this extension, it should be skipped.
6. IANA Considerations 6. IANA Considerations
This specification reserves one number for the Message String This specification reserves one number for the Message String
Extension Section 3 from the space of numbers for skippable mobility Extension in Section 3 from the space of numbers for skippable
extensions (i.e., 128-255) defined for Mobile IPv4 [RFC3344] at mobility extensions (i.e., 128-255) defined for Mobile IPv4 [RFC3344]
http://www.iana.org/assignments/mobileip-numbers. at http://www.iana.org/assignments/mobileip-numbers.
The value 145 is recommended for this extension. The value 145 is suggested for this extension.
This specification also creates a new subtype space for the type This specification also creates a new subtype space for the type
number of this extension. The subtype values 1 and 2 are defined in number of this extension. The subtype values 1 and 2 are defined in
this specification. The subtype value 1 is reserved for use by Home this specification. The subtype value 1 is reserved for use by Home
Agent and subtype value 2 is reserved for use by Foreign Agent. Agent and subtype value 2 is reserved for use by Foreign Agent.
Other values can be allocated from this number space by IANA actions. Similar to the procedures specified for Mobile IPv4 [RFC3344] number
spaces, future allocations from this number space require expert
review [RFC2434].
7. Acknowledgements 7. Acknowledgements
The authors would like to thank Avi Lior, Curtis Provost and Henrik The authors would like to thank Avi Lior, Curtis Provost and Henrik
Levkowetz for their useful comments on an eariler version of this Levkowetz for their useful comments on an eariler version of this
document. document.
8. Normative References 8. Normative References
[FA-ERR] Perkins, C., "Foreign Agent Error Extension for Mobile [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
IPv4", draft-ietf-mip4-faerr-02.txt (work in progress), Requirement Levels", BCP 14, RFC 2119, March 1997.
September 2005.
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
"Remote Authentication Dial In User Service (RADIUS)", IANA Considerations Section in RFCs", BCP 26, RFC 2434,
RFC 2865, June 2000. October 1998.
[RFC3344] Perkins, C., "IP Mobility Support for IPv4", RFC 3344, [RFC3344] Perkins, C., "IP Mobility Support for IPv4", RFC 3344,
August 2002. August 2002.
[RFC3543] Glass, S. and M. Chandra, "Registration Revocation in
Mobile IPv4", RFC 3543, August 2003.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, November 2003. 10646", STD 63, RFC 3629, November 2003.
Authors' Addresses Authors' Addresses
Venkateshwara Sastry Venkateshwara Sastry
Cisco Systems Samsung Electronics
Akkithimanahalli, O'Shaugnessy Road Bagmane Lake View, 'Block -B'
Bangalore 560085 66/1, Bagmane Tech Park, Byrasandra,
C. V. Raman Nagar
Bangalpre 560093
India India
Phone: +91 80-51033757 Phone: +91-80-41819999
Email: vsastry@cisco.com Email: venkat.s@samsung.com
Kent Leung Kent Leung
Cisco Systems Cisco Systems
170 W. Tasman Drive 170 W. Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
US US
Phone: +1 408-526-5030 Phone: +1 408-526-5030
Email: kleung@cisco.com Email: kleung@cisco.com
skipping to change at page 13, line 7 skipping to change at page 13, line 7
Cisco Systems Cisco Systems
170 W. Tasman Drive 170 W. Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
US US
Phone: +1 408-853-9580 Phone: +1 408-853-9580
Email: alpesh@cisco.com Email: alpesh@cisco.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
 End of changes. 31 change blocks. 
88 lines changed or deleted 92 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/