draft-ietf-mip4-message-string-ext-00.txt   draft-ietf-mip4-message-string-ext-01.txt 
Network Working Group V. Sastry Network Working Group V. Sastry
Internet-Draft K. Leung Internet-Draft K. Leung
Expires: July 13, 2006 A. Patel Intended status: Standards Track A. Patel
Cisco Systems Expires: March 18, 2007 Cisco Systems
January 09, 2006 September 14, 2006
Mobile IPv4 Message String Extension Mobile IPv4 Message String Extension
draft-ietf-mip4-message-string-ext-00.txt draft-ietf-mip4-message-string-ext-01.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 35
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 July 13, 2006. This Internet-Draft will expire on March 18, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
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 message. 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. Normative References . . . . . . . . . . . . . . . . . . . . . 9 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 8. Normative References . . . . . . . . . . . . . . . . . . . . . 11
Intellectual Property and Copyright Statements . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
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 Foreign Agent and Home Agent in registration message targeted for
the Mobile Node. Such a message may be either a Registration Reply the Mobile Node. Such a message may be either a Registration Reply
or Registration Revocation (i.e. collocated Care-of Address mode). or Registration Revocation (i.e. collocated Care-of Address mode).
For the Registration Reply message, this extension can be added For the Registration Reply message, this extension can be added
regardless of whether the registration has succeeded or failed. regardless of whether the registration has succeeded or failed.
skipping to change at page 6, line 8 skipping to change at page 6, line 8
2: 2:
Extension is added by Foreign Agent Extension is added by 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 [RFC2279] characters. that the message contain UTF-8 encoded 10646 [RFC3629] characters.
The number of octets in the UTF-8 representation of the message is
exactly the value of the Length field minus one.
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 Home Agent or
Foreign Agent or both can add Message String Extension to Foreign Agent or both can add Message String Extension to
registration messages. Usage of Text field of the Message String registration messages. Usage of Text field of the Message String
Extension is implementation dependent. For example, this message can Extension is implementation dependent. For example, this 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
skipping to change at page 9, line 20 skipping to change at page 10, line 5
http://www.iana.org/assignments/mobileip-numbers. http://www.iana.org/assignments/mobileip-numbers.
The value 145 is recommended for this extension. The value 145 is recommended 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. Other values can be allocated from this number space by IANA actions.
7. Normative References 7. Acknowledgements
The authors would like to thank Avi Lior, Curtis Provost and Henrik
Levkowetz for their useful comments on an eariler version of this
document.
8. Normative References
[FA-ERR] Perkins, C., "Foreign Agent Error Extension for Mobile [FA-ERR] Perkins, C., "Foreign Agent Error Extension for Mobile
IPv4", draft-ietf-mip4-faerr-02.txt (work in progress), IPv4", draft-ietf-mip4-faerr-02.txt (work in progress),
September 2005. September 2005.
[RFC2279] Yergeau, F., "UTF-8, a transformation format of ISO
10646", RFC 2279, January 1998.
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
"Remote Authentication Dial In User Service (RADIUS)", "Remote Authentication Dial In User Service (RADIUS)",
RFC 2865, June 2000. RFC 2865, June 2000.
[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 [RFC3543] Glass, S. and M. Chandra, "Registration Revocation in
Mobile IPv4", RFC 3543, August 2003. Mobile IPv4", RFC 3543, August 2003.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, November 2003.
Authors' Addresses Authors' Addresses
Venkateshwara Sastry Venkateshwara Sastry
Cisco Systems Cisco Systems
Akkithimanahalli, O'Shaugnessy Road Akkithimanahalli, O'Shaugnessy Road
Bangalore 560085 Bangalore 560085
India India
Phone: +91 80-51033757 Phone: +91 80-51033757
Email: vsastry@cisco.com Email: vsastry@cisco.com
skipping to change at page 11, line 5 skipping to change at page 13, line 5
Alpesh Patel Alpesh Patel
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
Intellectual Property Statement Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
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
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 11, line 29 skipping to change at page 13, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 11 change blocks. 
30 lines changed or deleted 39 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/