draft-ietf-mobileip-3gwireless-ext-00.txt   draft-ietf-mobileip-3gwireless-ext-01.txt 
Mobile IP Working Group Yingchun Xu (editor) Mobile IP Working Group Yingchun Xu (editor)
Internet Draft Rajesh Bhalla Internet Draft Rajesh Bhalla
October 1999 Ed Campbell November 1999 Ed Campbell
Karl Freter Karl Freter
3Com Corporation 3Com Corporation
Eileen McGrath Hadwen Eileen McGrath Hadwen
Alcatel Alcatel
Gopal Dommety Gopal Dommety
Kirit Joshi Kirit Joshi
Cisco Systems Cisco Systems
Parviz Yegani Parviz Yegani
Ericson Wireless Communication Inc. Ericson Wireless Communication Inc.
Takeo Matsumura
FUJITSU
Atsushi Teshima
HITACHI Ltd.
Lee Dong Hyun
HYUNDAI Electronics
Naoto Itoh
IDO Corporation
Kimihiro Ohki
KDD Corporation
Byung-Keun Lim Byung-Keun Lim
LG Information & Communications, Ltd LG Information & Communications, Ltd
Peter J. McCann Peter J. McCann
Thomas Towle Thomas Towle
Lucent Technologies Lucent Technologies
Jay Jayapalan Jay Jayapalan
Motorola Inc. Motorola Inc.
Peter W. Wenzel Peter W. Wenzel
Carey B. Becker Carey B. Becker
James Jiang
Nortel Networks Nortel Networks
Shota Shikano
Oki Electric Industry Co.,Ltd.
Woojune Kim
Yong Chang
Samsung Electronics Ltd.
Jun Mo Koo
SK Telecom
Bill Semper
Samsung Telecommunications
Mark A. Lipford Mark A. Lipford
Frederic Leroudier
Sprint PCS Sprint PCS
Jim Gately
USWest Advanced Technologies
Mobile IP Based Micro Mobility Management Protocol in Mobile IP Based Micro Mobility Management Protocol in
The Third Generation Wireless Network The Third Generation Wireless Network
<draft-ietf-mobileip-3gwireless-ext-00.txt> <draft-ietf-mobileip-3gwireless-ext-01.txt>
Xu et al. Expires May 2000 1
Status of this Memo Status of this Memo
This document is an Internet Draft and is in full conformance with This document is an Internet Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet Drafts are working all provisions of Section 10 of RFC2026. Internet Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and working groups. Note that other groups may also distribute and working groups. Note that other groups may also distribute
working documents as Internet Drafts. working documents as Internet Drafts.
Internet Drafts are draft documents valid for a maximum of six Internet Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsolete by other documents months and may be updated, replaced, or obsolete by other documents
at anytime. It is inappropriate to use Internet Drafts as reference at anytime. 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.
Xu et al. Expires 22 April 2000 1
Abstract Abstract
This document defines extensions to the Mobile IP protocol [1] to This document defines extensions to the Mobile IP protocol [1] to
allow mobility management for the interface between a radio network allow mobility management for the interface between a radio network
and a packet data network in the third generation cdma2000 network. and a packet data network in the third generation cdma2000 network.
Mobile IP requires link layer connectivity between the Mobile Node Mobile IP requires link layer connectivity between the Mobile Node
and the Foreign Agent. This draft proposes a protocol for achieving and the Foreign Agent. This draft proposes a protocol for achieving
this when the physical layer terminates at a point distant from the this when the physical layer terminates at a point distant from the
FA. In particular, this protocol applies to cdma2000 networks where FA. In particular, this protocol applies to cdma2000 networks where
skipping to change at line 83 skipping to change at line 106
1. Introduction 1. Introduction
This document defines extensions to the Mobile IP protocol [1] to This document defines extensions to the Mobile IP protocol [1] to
allow mobility management for the interface between a radio network allow mobility management for the interface between a radio network
and a packet data network in the third generation cdma2000 network. and a packet data network in the third generation cdma2000 network.
Mobile IP requires link layer connectivity between the Mobile Node Mobile IP requires link layer connectivity between the Mobile Node
and the Foreign Agent. This draft proposes a protocol for achieving and the Foreign Agent. This draft proposes a protocol for achieving
this when the physical layer terminates at a point distant from the this when the physical layer terminates at a point distant from the
Xu et al. Expires May 2000 2
FA. In particular, this protocol applies to cdma2000 networks where FA. In particular, this protocol applies to cdma2000 networks where
the physical layer terminates at a Radio Network Node (RNN) and the the physical layer terminates at a Radio Network Node (RNN) and the
FA resides inside a separate Packet Data Serving Node (PDSN). The FA resides inside a separate Packet Data Serving Node (PDSN). The
PDSN is responsible for establishing, maintaining, and terminating PDSN is responsible for establishing, maintaining, and terminating
the link layer to the Mobile Node. A RNN is responsible for relaying the link layer to the Mobile Node. A RNN is responsible for relaying
the link layer protocol between a Mobile Node and its corresponding the link layer protocol between a Mobile Node and its corresponding
PDSN. PDSN.
The interface between the RNN and the PDSN is called the RP The interface between the RNN and the PDSN is called the RP
interface. This interface requires mobility management for handling interface. This interface requires mobility management for handling
handoff from one RNN to another without interrupting end to end handoff from one RNN to another without interrupting end to end
communication. It also requires the support of the link layer communication. It also requires the support of the link layer
protocol encapsulation. protocol encapsulation.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in [RFC-2119]. this document are to be interpreted as described in [RFC-2119].
Xu et al. Expires 22 April 2000 2
2. Glossary 2. Glossary
CDMA Code Division Multiple Access CDMA Code Division Multiple Access
FA Foreign Agent FA Foreign Agent
HA Home Agent HA Home Agent
MN Mobile Node MN Mobile Node
PDSN Packet Data Serving Node PDSN Packet Data Serving Node
RNN Radio Network Node RNN Radio Network Node
RP Interface between the RNN and the PDSN RP Interface between the RNN and the PDSN
skipping to change at line 136 skipping to change at line 159
| |
| |
\|/ \|/
+--------+ +--------+
| Mobile | | Mobile |
| Node | | Node |
+--------+ +--------+
Figure 1: The Third Generation cdma2000 Network RP Interface Figure 1: The Third Generation cdma2000 Network RP Interface
Xu et al. Expires May 2000 3
In above figure 1, the PDSN will be responsible for establishing, In above figure 1, the PDSN will be responsible for establishing,
maintaining, and terminating the link layer to the Mobile Node. It maintaining, and terminating the link layer to the Mobile Node. It
initiates the authentication, authorization, and accounting for the initiates the authentication, authorization, and accounting for the
Mobile Node and optionally, securely tunnels to the Home Agent. Mobile Node and optionally, securely tunnels to the Home Agent.
The RNN is responsible for mapping the Mobile Node identifier The RNN is responsible for mapping the Mobile Node identifier
reference to a unique link layer identifier used to communicate with reference to a unique link layer identifier used to communicate with
the PDSN. RNN validates the Mobile Station for access service and the PDSN. RNN validates the Mobile Station for access service and
manages the physical layer connection to the Mobile Node. manages the physical layer connection to the Mobile Node.
4. Mobile IP Extensions 4. Mobile IP Extensions
This section describes extensions to the Mobile IP protocol for the This section describes extensions to the Mobile IP protocol for the
RP interface within the third generation cdma2000 network. RP interface within the third generation cdma2000 network.
4.1 Registration Request 4.1 Registration Request
Xu et al. Expires 22 April 2000 3
In a cdma2000 network, the mobile node initiates a connection by In a cdma2000 network, the mobile node initiates a connection by
sending a call setup indication to the RNN across the radio network. sending a call setup indication to the RNN across the radio network.
When this indication is received by a RNN, a Registration Request When this indication is received by a RNN, a Registration Request
will be sent from the RNN to the PDSN to setup a new RP session. will be sent from the RNN to the PDSN to setup a new RP session.
A RNN MUST send a Registration Request with the GRE encapsulation A RNN MUST send a Registration Request with the GRE encapsulation
and the reverse tunneling bit set. The Home Address field is set to and the reverse tunneling bit set. The Home Address field is set to
zero. The Home Agent field will be assigned to the IP address of the zero. The Home Agent field will be assigned to the IP address of the
PDSN and the Care-of Address field will be assigned to the IP PDSN and the Care-of Address field will be assigned to the IP
address of RNN. address of RNN.
skipping to change at line 190 skipping to change at line 213
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Care-of Address | | Care-of Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ Identification + + Identification +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Extensions ... | Extensions ...
+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-
Xu et al. Expires May 2000 4
Type 1 (Registration Request) Type 1 (Registration Request)
G This bit MUST be set to 1 for GRE tunneling. G This bit MUST be set to 1 for GRE tunneling.
T This bit MUST be set to 1 for reverse T This bit MUST be set to 1 for reverse
tunneling. tunneling.
Home Address Home Address
The field is set to zero. The field is set to zero.
Home Agent Home Agent
This field is assigned to the IP address of the This field is assigned to the IP address of the
PDSN. PDSN.
Care-of Address Care-of Address
This field is assigned to the IP address of RNN. This field is assigned to the IP address of RNN.
Xu et al. Expires 22 April 2000 4
Extensions Extensions
The Session Specific Extension as described in The Session Specific Extension as described in
the next section MUST be included along with the next section MUST be included along with
the ones described in RFC2002. Specifically, the ones described in RFC2002. Specifically,
the MN-HA Authentication extension as described the MN-HA Authentication extension as described
in RFC2002 MUST be included along with this in RFC2002 MUST be included along with this
extension. extension.
4.2 Session Specific Extension 4.2 Session Specific Extension
skipping to change at line 234 skipping to change at line 257
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 | Protocol Type | | Type | Length | Protocol Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Key | | Key |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| reserved | MN Connection ID | | reserved | MN Connection ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MN ID Type | MN ID Length | MN ID | | MN ID Type | MN ID Length | MN ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MN ID ... | MN ID ą
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type TBD. Its value shall be in the range of 0 to Type 39 (non-skippable).
127.
Xu et al. Expires May 2000 5
Length This is a one octet field and it indicates the Length This is a one octet field and it indicates the
length (in bytes) of the extension, NOT length (in bytes) of the extension, NOT
including the Type and Length fields. including the Type and Length fields.
Protocol Type Protocol Type
This is a two octet field. It indicates the type This is a two octet field. It indicates the type
of the protocol to be tunneled across the RP of the protocol to be tunneled across the RP
interface. It is same as the Protocol Type field interface. It is same as the Protocol Type field
in the GRE header. in the GRE header.
Key This is a four octet value assigned by the RNN Key This is a four octet value assigned by the RNN
and inserted in every GRE frame across the RP and inserted in every GRE frame across the RP
interface during user data tunneling. interface during user data tunneling.
Reserved This is a two octet field. It is not used and is Reserved This is a two octet field. It is not used and is
set to zero. set to zero.
MN Connection ID MN Connection ID
Xu et al. Expires 22 April 2000 5
This is a two octet field and it is used to This is a two octet field and it is used to
differentiate the multiple sessions from the differentiate the multiple sessions from the
same Mobile Node. It is locally unique to a same Mobile Node. It is locally unique to a
Mobile Node. Mobile Node.
MN ID Type MN ID Type
This is a two octet field and it indicates the This is a two octet field and it indicates the
type of the following Mobile Node ID value. For type of the following Mobile Node ID value.
example, value 1 defines IMSI (International
Mobile Serial Identifier) and 2 Ethernet MAC
address.
MN ID Length MN ID Length
This is a one octet field and it indicates the This is a one octet field and it indicates the
length (in bytes) of the following Mobile Node length (in bytes) of the following Mobile Node
ID field. ID field.
MN ID This is the Mobile Node ID, which is globally MN ID This is the Mobile Node ID, which is globally
unique. It is used to uniquely identify a Mobile unique. It is used to uniquely identify a Mobile
Node. Node.
skipping to change at line 297 skipping to change at line 315
The MN ID and the MN Connection ID together will uniquely identify a The MN ID and the MN Connection ID together will uniquely identify a
Mobile Session. Mobile Session.
4.3 Registration Reply 4.3 Registration Reply
The Registration Reply will be sent by a PDSN following the The Registration Reply will be sent by a PDSN following the
procedure as described in [1]. The Home Address field will be the procedure as described in [1]. The Home Address field will be the
same value as the Home Address field from the corresponding same value as the Home Address field from the corresponding
Registration Request message received by the PDSN. Registration Request message received by the PDSN.
4.4 Vendor/Organization Specific Extensions Xu et al. Expires May 2000 6
Dommety [4] proposes two types of Vendor/Organization Specific
extensions. These extensions will be used for carrying any third
generation cdma2000 network specific information. They may appear in
the Registration Request and Registration Update messages as needed.
4.5 Registration Update/Acknowledge 4.4 Registration Update/Acknowledge
Two new messages are defined to support PDSN initiated RP tunnel Two new messages are defined to support PDSN initiated RP tunnel
tear down and to speed up resource reclamation on the RNN. tear down and to speed up resource reclamation on the RNN.
The Registration Update message is used for notification of the The Registration Update message is used for notification of the
change of the registration associated with a call. It shall be sent change of the registration associated with a call. It shall be sent
by the PDSN to the previous RNN when a RNN to RNN handoff happens. by the PDSN to the previous RNN when a RNN to RNN handoff happens.
Xu et al. Expires 22 April 2000 6
Both messages are sent with UDP using well-known port number 434. Both messages are sent with UDP using well-known port number 434.
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 | Reserved | | Type | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Home Address | | Home Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Home Agent Address | | Home Agent Address |
skipping to change at line 335 skipping to change at line 347
| | | |
+ Identification + + Identification +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Extensions ... | Extensions ...
+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-
The format of the Registration Update message is illustrated above, The format of the Registration Update message is illustrated above,
and contains the following fields: and contains the following fields:
Type TBD Type 20
Reserved Sent as 0; ignored on reception. Reserved Sent as 0; ignored on reception.
Home Address Sent as 0; Home Address Sent as 0;
Home Agent Address Home Agent Address
The IP Address of the PDSN. The IP Address of the PDSN.
Identification Identification
A 64-bit number assigned by the node sending A 64-bit number assigned by the node sending
skipping to change at line 359 skipping to change at line 371
Extensions Extensions
Both Registration Update Authentication Both Registration Update Authentication
Extension (see section 4.6) and Session Extension (see section 4.6) and Session
Specific Extension (see section 4.2) SHALL be Specific Extension (see section 4.2) SHALL be
included. included.
A Registration Update shall be sent by a PDSN to indicate the A Registration Update shall be sent by a PDSN to indicate the
closure of a RP session. The RNN may reclaim the resource associated closure of a RP session. The RNN may reclaim the resource associated
with that session. with that session.
Xu et al. Expires May 2000 7
A Registration Acknowledge message is used to acknowledge receipt of A Registration Acknowledge message is used to acknowledge receipt of
a Registration Update message. It MUST be sent by a node receiving a a Registration Update message. It MUST be sent by a node receiving a
Registration Update message. Registration Update message.
Xu et al. Expires 22 April 2000 7
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 | Reserved | Status | | Type | Reserved | Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Home Address | | Home Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Care Of Address | | Care Of Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ Identification + + Identification +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Extensions ... | Extensions ...
+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-
The format of the Registration Acknowledge message is illustrated The format of the Registration Acknowledge message is illustrated
above, and contains the following fields: above, and contains the following fields:
Type TBD Type 21
Status If the Status is nonzero, this acknowledgment is Status If the Status is nonzero, this acknowledgment is
negative. negative.
Reserved Reserved
Sent as 0; ignored on reception. Sent as 0; ignored on reception.
Home Address Home Address
Copied from the Registration Update message Copied from the Registration Update message
being acknowledged. being acknowledged.
skipping to change at line 410 skipping to change at line 422
being acknowledged. being acknowledged.
Extensions Extensions
Registration Update Authentication Registration Update Authentication
Extension SHALL be included. Extension SHALL be included.
Allowable values for the Status include: Allowable values for the Status include:
0 successful acknowledgement 0 successful acknowledgement
128 reason unspecified 128 reason unspecified
Xu et al. Expires May 2000 8
129 administratively prohibited 129 administratively prohibited
131 sending node failed authentication
133 identification mismatch 133 identification mismatch
134 poorly formed Registration Update 134 poorly formed Registration Update
4.6 Registration Update Authentication Extension 4.5 Registration Update Authentication Extension
Xu et al. Expires 22 April 2000 8
The Registration Update Authentication extension is used to The Registration Update Authentication extension is used to
authenticate the Registration Update and Registration Acknowledge authenticate the Registration Update and Registration Acknowledge
messages. It has the same format and default algorithm support messages. It has the same format and default algorithm support
requirements as the authentication extension defined for Mobile IP requirements as the authentication extension defined for Mobile IP
protocol [1], but with a different type (TBD). The authenticator protocol [1], but with a different type (40). The authenticator
value is computed from the stream of bytes including the shared value is computed from the stream of bytes including the shared
secret, the UDP payload all prior extensions in their entirety, and secret, the UDP payload all prior extensions in their entirety, and
the type and length of this extension, but not including the the type and length of this extension, but not including the
authenticator field itself nor the UDP header. The secret used for authenticator field itself nor the UDP header. The secret used for
computing the authenticator field is shared between the RN and PDSN. computing the authenticator field is shared between the RN and PDSN.
This extension is required in both Registration Update and This extension is required in both Registration Update and
Registration Acknowledge messages. Registration Acknowledge messages.
4.7 Summary 4.6 Summary
The extensions to Mobile IP include enabling the GRE encapsulation The extensions to Mobile IP include enabling the GRE encapsulation
and reverse tunneling during Registration. A new extension called and reverse tunneling during Registration. A new extension called
Session Specific Extension is defined and is mandatory in both Session Specific Extension is defined and is mandatory in both
Registration Request and Registration Update messages. The Home Registration Request and Registration Update messages. The Home
Address field MUST be set to zero in the Registration Request, Address field MUST be set to zero in the Registration Request,
Registration Reply, Registration Update and Registration Acknowledge Registration Reply, Registration Update and Registration Acknowledge
messages. messages.
Two new messages (Registration Update/Acknowledge) are defined to Two new messages (Registration Update/Acknowledge) are defined to
skipping to change at line 459 skipping to change at line 473
network. The Key field shall be required and its value shall be same network. The Key field shall be required and its value shall be same
as the one from the Session Specific Extension as described above. as the one from the Session Specific Extension as described above.
The sequence number may be required, depending on the requirement of The sequence number may be required, depending on the requirement of
the protocol encapsulated within the GRE frame. the protocol encapsulated within the GRE frame.
During traffic tunneling, the sender will insert the Key value from During traffic tunneling, the sender will insert the Key value from
the Registration Request message into the Key field of the GRE the Registration Request message into the Key field of the GRE
header. The receiver will use the Key value from the GRE header to header. The receiver will use the Key value from the GRE header to
decide where to forward the user data. decide where to forward the user data.
6.0 Security Considerations 6.0 IANA Considerations
Xu et al. Expires May 2000 9
The numbers for the Mobile IP Session Specific Extension (section
4.2)and Registration Update Authentication Extension (section 4.5)
are taken from the numbering space defined for Mobile IP extensions
defined in RFC 2002 [1] as extended in RFC 2356 [4]. The numbering
for the extensions SHOULD NOT conflict with values specified in the
Internet Draft for the Mobile IP Network Address Identifier
Extension[5], the Internet Draft for Mobile IP Challenge/Response
Extensions[6] or the Internet Draft for Route Optimization [7]. The
values specified for Status field, listed in section 4.4, MUST NOT
conflict with any other code or status values listed in RFC 2002[1],
RFC2344[2], or RFC2356[4], or the above mentioned Internet Drafts
[5], [6] and [7]. They are to be taken from the space of error
values conventionally associated with rejection by the home agent
(i.e. 128-255).
7.0 Security Considerations
The protocol presented in this draft is designed for use over a The protocol presented in this draft is designed for use over a
protected, private network between RNN and PDSN. Pre-arranged protected, private network between RNN and PDSN. Pre-arranged
security associations in the style of Mobile IPv4 are assumed to security associations in the style of Mobile IPv4 are assumed to
exist among every (RNN, PDSN) pair that will form an RP connection. exist among every (RNN, PDSN) pair that will form an RP connection.
Also, it is assumed that the session specific information is Also, it is assumed that the session specific information is
authenticated by means outside the scope of this draft. authenticated by means outside the scope of this draft.
Xu et al. Expires 22 April 2000 9
Several potential vulnerabilities exist if these assumptions are not Several potential vulnerabilities exist if these assumptions are not
met. First, if the network connecting the RNN and PDSN is accessible met. First, if the network connecting the RNN and PDSN is accessible
to an attacker, user traffic may be intercepted and/or spoofed if to an attacker, user traffic may be intercepted and/or spoofed if
there are no other end-to-end security mechanisms in place. Second, there are no other end-to-end security mechanisms in place. Second,
the Mobile IP control messages must be authenticated, to prevent the Mobile IP control messages must be authenticated, to prevent
tunnel setup and tear down by unauthorized parties. Mobile IP tunnel setup and tear down by unauthorized parties. Mobile IP
Authentication Extensions are used to provide this additional Authentication Extensions are used to provide this additional
protection for control messages. Finally, if session specific protection for control messages. Finally, if session specific
information is not authenticated, a denial-of-service attack is information is not authenticated, a denial-of-service attack is
possible if a RNN unknowingly sends a registration request to the possible if a RNN unknowingly sends a registration request to the
PDSN with a spoofed session specific extension. The PDSN would then PDSN with a spoofed session specific extension. The PDSN would then
send an explicit tunnel tear down to the previous RNN, causing user send an explicit tunnel tear down to the previous RNN, causing user
traffic to be misdirected to the new RNN. This would cause a loss of traffic to be misdirected to the new RNN. This would cause a loss of
service and possibly interception of traffic, depending on what service and possibly interception of traffic, depending on what
other security measures are in place. other security measures are in place.
8.0 Acknowledgments
The authors of this draft would like to thank Charles E. Perkins and
David B. Johnson for the ideas presented in the Route Optimization
draft [7].
References References
[1] C. Perkins, Editor, "IP Mobility Support", RFC 2002, October [1] C. Perkins, Editor, "IP Mobility Support", RFC 2002, October
1996. 1996.
Xu et al. Expires May 2000 10
[2] G. Montenegro, "Reverse Tunneling for Mobile IP", RFC2344, May [2] G. Montenegro, "Reverse Tunneling for Mobile IP", RFC2344, May
1998. 1998.
[3] Hanks, S., Li, R., Farinacci, D., and P. Traina, "Generic [3] Hanks, S., Li, R., Farinacci, D., and P. Traina, "Generic
Routing Encapsulation (GRE)", RFC 1701, October 1994. Routing Encapsulation (GRE)", RFC 1701, October 1994.
[4] Dommety, Leung, "Mobile IP Vendor/Organization-Specific
Extensions", draft-ietf-mobileip-vendor-ext-00.txt, August
1999.
Authors Addresses [4] G. Montenegro and V. Gupta. "Sun's SKIP Firewall Traversal for
Mobile IP". RFC 2356, June 1998.
Yingchun Xu Rajesh Bhalla [5] Pat R. Calhoun and Charles E. Perkins. "Mobile IP Network
3Com Corporation 3Com Corporation Address Identifier Extension". draft-ietf-mobileip-mn-nai-
1800 West Central Rd. 1800 W. Central Road 05.txt, October 1999. (work in progress).
Mount Prospect, Mt. Prospect,
USA 60056 IL 60056
Phone: (847) 342-6814 Phone: (847) 797-2618
Email: Yingchun_Xu@3com.com Email: rajesh_bhalla@3com.com
Karl Freter Ed Campbell [6] Charles E. Perkins and Pat R. Calhoun. "Mobile IP Challenge/
3Com Corporation 3Com Corporation Response Extensions". draft-ietf-mobileip-challenge-06.txt,
1800 W. Central Road 1800 W. Central Road October 1999. (work in progress).
Mt. Prospect, IL 60056 Mt. Prospect, IL 60056
Phone: (847) 222-2268 Phone: (847) 342-6769 [7] Charles E. Perkins and David B. Johnson. "Route Optimization in
Email: karl_freter@3com.com Email: ed_campbell@3com.com Mobile IP". draft-ietf-mobileip-optim-08.txt, February 1999.
(work in progress).
Xu et al. Expires May 2000 11
AuthorsĘ Addresses
Yingchun Xu
3Com Corporation
1800 West Central Road
Mount Prospect,
USA 60056
Phone: (847) 342-6814
Email: Yingchun_Xu@3com.com
Rajesh Bhalla
3Com Corporation
1800 West Central Road
Mount Prospect,
USA 60056
Phone: (847) 797-2618
Email: rajesh_bhalla@3com.com
Karl Freter
3Com Corporation
1800 W. Central Road
Mount Prospect, IL 60056
Phone: (847) 222-2268
Email: karl_freter@3com.com
Ed Campbell
3Com Corporation
1800 W. Central Road
Mount Prospect, IL 60056
Phone:(847) 342-6769
Email: ed_campbell@3com.com
Xu et al. Expires 22 April 2000 10
Eileen McGrath Hadwen Eileen McGrath Hadwen
Alcatel Alcatel
PO Box 4442, Boulder CO 80306 PO Box 4442,
Boulder CO 80306
Phone: 303 499 1496 Phone: 303 499 1496
Mobile: 303 517 0407
Email: mcgrath.hadwen@worldnet.att.net Email: mcgrath.hadwen@worldnet.att.net
Gopal Dommety Kirit Joshi Gopal Dommety
Cisco Systems Cisco Systems Cisco Systems
170 West Tasman Drive 170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134 San Jose, CA 95134
Phone: (408) 525-1404 Phone: (408) 525 7367 Phone: (408) 525-1404
Email: gdommety@cisco.com Email: kjoshi@cisco.com Email: gdommety@cisco.com
Kirit Joshi
Cisco Systems
170 West Tasman Drive
San Jose, CA 95134
Phone: (408) 525 7367
Email: kjoshi@cisco.com
Xu et al. Expires May 2000 12
Parviz Yegani Parviz Yegani
Ericson Wireless Communication Inc. Ericson Wireless Communication Inc.
6455 Lusk Blvd. 6455 Lusk Blvd.
San Diego, CA 92121 San Diego, CA 92121
Phone: (858) 332-6017 Phone: (858) 332-6017
Email: p.yeqani@ericsson.com Email: p.yeqani@ericsson.com
Takeo Matsumura
FUJITSU
Kamiodanaka
Nakahara-ku, Kawasaki-City
Phone: +81-44-740-8109
Email: matumura@mcs.ts.fujitsu.co.jp
Atsushi Teshima
HITACHI Ltd.
216 Totsuka-cho, Totsuka-ku, Yokohama Japan 244-8567
Phone:+81-45-865-7003
Email: atsushi_teshima@cm.tcd.hitachi.co.jp
Lee Dong Hyun
HYUNDAI Electronics Industry
KOREA Kyungkido Icheonsi 435-050
Phone: 82-336-630-2756
Email: jihs@hei.co.kr
Naoto Itoh
IDO Corporation
Gobancho YS building
12-3 Gobancho, Chiyoda-ku, Tokyo Japan 102-8361
Phone: +81-3-3263-9660
Email: nao-itoh@ido.co.jp
Kimihiro Ohki
KDD Corporation
3-2, Nishi-Shinjuku 2-chome,
Shinjuku-ku, Tokyo 163-8003, Japan
Phone: +81-3-3347-5477
Email: ki-ohki@kdd.co.jp
Byung-Keun Lim, Byung-Keun Lim,
LG Information & Communications, Ltd. LG Information & Communications, Ltd.
533, Hogye-dong, Dongan-ku, Anyang-shi, 533, Hogye-dong, Dongan-ku, Anyang-shi,
Kyungki-do,431-080, Korea Kyungki-do,431-080, Korea
Phone: +82-343-450-7199 Phone: +82-343-450-7199
Email: bklim@lgic.co.kr Email: bklim@lgic.co.kr
Peter J. McCann Thomas Towle Peter J. McCann
Lucent Technologies Lucent Technologies Lucent Technologies
Rm 2Z-305 Rm. 2D-225 Rm 2Z-305
263 Shuman Blvd 263 Shuman Blvd 263 Shuman Blvd
Naperville, IL 60566 Naperville, IL 60566 Naperville, IL 60566
Phone: (630) 713 9359 Phone: 630-979-7303 Phone: (630) 713 9359
EMail: mccap@lucent.com Email: ttowle@lucent.com
Xu et al. Expires May 2000 13
EMail: mccap@lucent.com
Thomas Towle
Lucent Technologies
Rm. 2D-225
263 Shuman Blvd
Naperville, IL 60566
Phone: 630-979-7303
Email: ttowle@lucent.com
Jay Jayapalan Jay Jayapalan
Motorola Inc. Motorola Inc.
1501 W Shure Drive 1501 W Shure Drive
Arlington Heights,IL 60004 Arlington Heights,IL 60004
Phone: (847) 642-4031 Phone: (847) 642-4031
Email: jayapal@cig.mot.com Email: jayapal@cig.mot.com
Peter W. Wenzel Carey B. Becker Peter W. Wenzel
Nortel Networks Nortel Networks Nortel Networks
2201 Lakeside Blvd. 2201 Lakeside Blvd. 2201 Lakeside Blvd.
Richardson, TX 75082, USA Richardson, TX 75082, USA Richardson, TX 75082, USA
Phone: (972) 684-7134 (972) 685-0560 Phone: (972) 684-7134
wenzel@nortelnetworks.com becker@nortelnetworks.com Email: wenzel@nortelnetworks.com
Carey B. Becker
Nortel Networks
2201 Lakeside Blvd.
Richardson, TX 75082, USA
Phone: (972) 685-0560
Email: becker@nortelnetworks.com
James Jiang
Nortel Networks
2201 Lakeside Blvd.
Richardson, TX 75082, USA
Phone: (972)684-5885
Email: jjiang@nortelnetworks.com
Shota Shikano
Oki Electric Industry Co., Ltd.
Phone:+81-3-3454-2111
Email: shikano471@oki.co.jp
Woojune Kim
Samsung Electronics Ltd.
11th Fl, Samsung Plaza Bldg,
263, Seohyeon-dong, Pundang-gu,
Sungnam-shi, Kyunggi-do,
463-050 Pundang P.O. Box 32, Korea
Phone: +82-342-779-8526
Email: keg@telecom.samsung.co.kr
Yong Chang
Xu et al. Expires May 2000 14
Samsung Electronics Ltd.
11th Fl, Samsung Plaza Bldg,
263, Seohyeon-dong, Pundang-gu,
Sungnam-shi, Kyunggi-do,
463-050 Pundang P.O. Box 32, Korea
Phone: +82-342-779-6822
Email : yong@telecom.samsung.co.kr
Bill Semper
Samsung Telecommunications
1130 Arapaho Rd
Richardson, TX 75082
Phone: 972-761-7996
Email: bsemper@telecom.samsung.com
Jun Mo Koo
SK Telecom
Phone: 650-568-5762
Email: jmkoo@sktelecom.com
Mark A. Lipford Mark A. Lipford
Sprint PCS Sprint PCS
8001 College Blvd. Suite 210 8001 College Blvd. Suite 210
Xu et al. Expires 22 April 2000 11
KSOPKZ0101 KSOPKZ0101
Overland Park, KS 66210 Overland Park, KS 66210
Phone: 913-664-8335 Phone: 913-664-8335
PCS: 913-226-9060
Email: Mlipfo01@sprintspectrum.com Email: Mlipfo01@sprintspectrum.com
Xu et al. Expires 22 April 2000 12 Frederic Leroudier
Sprint PCS
8001 College Blvd. Suite 210
KSOPKZ0101
Overland Park, KS 66210
Phone: 913-664-8350
Email: FLerou01@sprintspectrum.com
Jim Gately
USWest Advanced Technologies
4001 Discovery Drive
Boulder, CO 80303
Phone: 303-541-6415
Email: jgately@uswest.com
Xu et al. Expires May 2000 15
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/