draft-ietf-mobileip-3gwireless-ext-03.txt   draft-ietf-mobileip-3gwireless-ext-04.txt 
Mobile IP Working Group Yingchun Xu (editor) Mobile IP Working Group Yingchun Xu (editor)
Internet Draft Rajesh Bhalla Internet Draft Rajesh Bhalla
March 2000 Ed Campbell June 2000 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 Takeo Matsumura
FUJITSU FUJITSU
Atsushi Teshima Atsushi Teshima
HITACHI Ltd. HITACHI Ltd.
Lee Dong Hyun Lee Dong Hyun
HYUNDAI Electronics HYUNDAI Electronics
Naoto Itoh Naoto Itoh
IDO Corporation IDO Corporation
Kimihiro Ohki Kimihiro Ohki
KDD Corporation KDD Corporation
skipping to change at line 39 skipping to change at line 38
Jay Jayapalan Jay Jayapalan
Motorola Inc. Motorola Inc.
Peter W. Wenzel Peter W. Wenzel
Carey B. Becker Carey B. Becker
James Jiang James Jiang
Nortel Networks Nortel Networks
Shota Shikano Shota Shikano
Oki Electric Industry Co.,Ltd. Oki Electric Industry Co.,Ltd.
Woojune Kim Woojune Kim
Yong Chang Yong Chang
Bill Semper
Samsung Electronics Ltd. Samsung Electronics Ltd.
Jun Mo Koo Jun Mo Koo
SK Telecom SK Telecom
Bill Semper
Samsung Telecommunications
Mark A. Lipford Mark A. Lipford
Frederic Leroudier Frederic Leroudier
Sprint PCS Sprint PCS
Jim Gately Jim Gately
USWest Advanced Technologies 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-03.txt> <draft-ietf-mobileip-3gwireless-ext-04.txt>
Xu et al. Expires September 2000 1 Xu et al. Expires December 2000 1
<draft-ietf-mobileip-3gwireless-ext-04.txt> June 2000
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
skipping to change at line 108 skipping to change at line 107
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 September 2000 2 Xu et al. Expires December 2000 2
<draft-ietf-mobileip-3Gwireless-ext-04.txt> June 2000
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 messages used for mobility management across the RP interface The messages used for mobility management across the RP interface
include Registration Request, Registration Reply, Registration include Registration Request, Registration Reply, Registration
Update and Registration Acknowledge. These messages MUST be sent Update and Registration Acknowledge. Both Registration Request and
with UDP using well-known port number 451. Registration Update messages MUST be sent with UDP using well-known
port number 697.
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].
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
skipping to change at line 160 skipping to change at line 162
| | Interface | | | | | | Interface | | | |
+---------+ +---------+ +---------+ +---------+ +---------+ +---------+
/|\ /|\
| Visited Access Home Network | Visited Access Home Network
| Provider Network | Provider Network
| |
| |
\|/ \|/
+--------+ +--------+
| Mobile | | Mobile |
| Node |
Xu et al. Expires September 2000 3 Xu et al. Expires December 2000 3
<draft-ietf-mobileip-3Gwireless-ext-04.txt> June 2000
| Node |
+--------+ +--------+
Figure 1: The Third Generation cdma2000 Network RP Interface Figure 1: The Third Generation cdma2000 Network RP Interface
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
skipping to change at line 200 skipping to change at line 204
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.
When a Registration Request is received by a PDSN, the information When a Registration Request is received by a PDSN, the information
from the Session Specific Extension (see next section) will be used from the Session Specific Extension (see next section) will be used
to identify a RP session. When a registration is accepted, a GRE to identify a RP session. When a registration is accepted, a GRE
tunnel will be created for this Mobile Node. tunnel will be created for this Mobile Node.
The message is sent with UDP using well-known port number 451. The message is sent with UDP using well-known port number 697.
The fields of the Registration Request message are shown below: The fields of the Registration Request message are shown below:
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 |S|B|D|M|G|V|T| | Lifetime | | Type |S|B|D|M|G|V|T| | Lifetime |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Home Address | | Home Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Home Agent | | Home Agent |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Care-of Address | | Care-of Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Xu et al. Expires September 2000 4 Xu et al. Expires December 2000 4
<draft-ietf-mobileip-3Gwireless-ext-04.txt> June 2000
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ Identification + + Identification +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Extensions ... | Extensions ...
+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-
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.
skipping to change at line 239 skipping to change at line 245
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.
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 261 skipping to change at line 268
This extension is defined to carry information related to the This extension is defined to carry information related to the
session between a Mobile Node and its serving PDSN. session between a Mobile Node and its serving PDSN.
The detailed format of the extension is shown as follows. The detailed format of the extension is shown as follows.
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 | 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 |
Xu et al. Expires December 2000 5
<draft-ietf-mobileip-3Gwireless-ext-04.txt> June 2000
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MN ID Ó | MN ID ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Xu et al. Expires September 2000 5
Type 39 (not-skippable). Type 39 (not-skippable).
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
of the protocol to be tunneled across the RP type of the protocol to be tunneled across the
interface. It is same as the Protocol Type field RP interface. It is same as the Protocol Type
in the GRE header. field 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
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
skipping to change at line 309 skipping to change at line 322
Type value 1 will be reserved for International Type value 1 will be reserved for International
Mobile Station Identity (IMSI) encoded in ASCII Mobile Station Identity (IMSI) encoded in ASCII
format. For detailed description of the IMSI, format. For detailed description of the IMSI,
see reference [8]. see reference [8].
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. For IMSI MN ID encoded in ASCII ID field. For IMSI MN ID encoded in ASCII
format, the length field value ranges from 10 to format, the length field value ranges from 10
15 bytes. to 15 bytes.
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.
Xu et al. Expires December 2000 6
<draft-ietf-mobileip-3Gwireless-ext-04.txt> June 2000
For Type 1 MN ID, the most significant digit of For Type 1 MN ID, the most significant digit of
IMSI will be coded in ASCII and stored as the IMSI will be coded in ASCII and stored as the
most significant byte of the MN ID. most significant byte of the MN ID.
Xu et al. Expires September 2000 6
This extension MUST be included in the Registration Request, This extension MUST be included in the Registration Request,
Registration Reply, Registration Update and Registration Acknowledge Registration Reply, Registration Update and Registration Acknowledge
(see section 4.5) messages. It will be included before the MN-HA (see section 4.5) messages. It will be included before the MN-HA
Authentication extension in the Registration Request and Authentication extension in the Registration Request and
Registration Reply messages and before the Registration Update Registration Reply messages and before the Registration Update
Authentication Extension in the Registration Update and Registration Authentication Extension in the Registration Update and Registration
Acknowledge messages. Acknowledge messages.
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.
The message is sent with UDP using well-known port number 451. The message is sent with UDP to the source port of the received
Registration Request message.
4.4 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.
Both messages are sent with UDP using well-known port number 451. The Registration Update message is sent with UDP using well-known
port number 697. And the Registration Acknowledge message is sent
with UDP to the source port from the received correspondent
Registration Update message.
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ Identification + + Identification +
| | | |
Xu et al. Expires December 2000 7
<draft-ietf-mobileip-3Gwireless-ext-04.txt> June 2000
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 20 Type 20
Reserved Sent as 0; ignored on reception. Reserved Sent as 0; ignored on reception.
Xu et al. Expires September 2000 7
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
the Registration Update message. It is used to the Registration Update message. It is used to
assist in matching requests with replies, and assist in matching requests with replies, and
in protecting against replay attacks. in protecting against replay attacks.
skipping to change at line 416 skipping to change at line 439
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Care Of Address | | Care Of Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ Identification + + Identification +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Extensions ... | Extensions ...
+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-
Xu et al. Expires December 2000 8
<draft-ietf-mobileip-3Gwireless-ext-04.txt> June 2000
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 21 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.
Xu et al. Expires September 2000 8
Home Address Home Address
Copied from the Registration Update message Copied from the Registration Update message
being acknowledged. being acknowledged.
Care of Address Care of Address
The IP address of the RNN. The IP address of the RNN.
Identification Identification
Copied from the Registration Update message Copied from the Registration Update message
being acknowledged. being acknowledged.
skipping to change at line 468 skipping to change at line 494
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 (40). 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.
Xu et al. Expires December 2000 9
<draft-ietf-mobileip-3Gwireless-ext-04.txt> June 2000
4.6 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 the Session Specific Extension is defined and is mandatory in the
Registration Request, Registration Reply, Registration Update and Registration Request, Registration Reply, Registration Update and
Registration Acknowledge messages. The Home Address field MUST be Registration Acknowledge messages. The Home Address field MUST be
set to zero in the Registration Request, Registration Reply, set to zero in the Registration Request, Registration Reply,
Registration Update and Registration Acknowledge messages. Registration Update and Registration Acknowledge messages.
Xu et al. Expires September 2000 9
Two new messages (Registration Update and Registration Acknowledge) Two new messages (Registration Update and Registration Acknowledge)
are defined to support the RP session disconnection in order to are defined to support the RP session disconnection in order to
speed up resource reclamation. speed up resource reclamation.
5.0 GRE Encapsulation 5.0 GRE Encapsulation
GRE encapsulation as described in [3] shall be supported during user GRE encapsulation as described in [3] shall be supported during user
data transmission. A new protocol type might be required to support data transmission. A new protocol type might be required to support
the link layer protocol defined for the third generation cdma2000 the link layer protocol defined for the third generation cdma2000
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
skipping to change at line 505 skipping to change at line 533
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 IANA Considerations 6.0 IANA Considerations
This document specifies two new messages and two new extensions to This document specifies two new messages and two new extensions to
Mobile IP protocol [1]. The numbers to be assigned to these messages Mobile IP protocol [1]. The numbers to be assigned to these messages
and extensions have been taken from the numbering space assigned to and extensions have been taken from the numbering space assigned to
Mobile IP in RFC 2002 [1] and extended in RFC 2356 [4]. Mobile IP in RFC 2002 [1] and extended in RFC 2356 [4].
The Registration Request, Registration Reply, Registration Update The Registration Request and Registration Update messages MUST be
and Registration Acknowledge messages MUST be sent with UDP using sent with UDP using well-known port number 697. This port number is
well-known port number 451. This port number is chosen from the chosen from the unassigned port range as specified in RFC1700 [9].
unassigned port range as specified in RFC1700 [9].
The Registration Update and Registration Acknowledge messages The Registration Update and Registration Acknowledge messages
defined in section 4.4 MUST be assigned the Type values of 20 and 21 defined in section 4.4 MUST be assigned the Type values of 20 and 21
respectively. respectively.
The Session Specific Extension defined in section 4.2 MUST be The Session Specific Extension defined in section 4.2 MUST be
assigned the Type value of 39, and the Registration Update assigned the Type value of 39, and the Registration Update
Authentication Extension defined in section 4.5 MUST be assigned a Authentication Extension defined in section 4.5 MUST be assigned a
value of 40. The Status values defined in section 4.4 are the error value of 40. The Status values defined in section 4.4 are the error
codes defined in RFC 2002 [1]. They correspond to the error values codes defined in RFC 2002 [1]. They correspond to the error values
conventionally associated with a rejection by a home agent (i.e., conventionally associated with a rejection by a home agent (i.e.,
Xu et al. Expires December 2000 10
<draft-ietf-mobileip-3Gwireless-ext-04.txt> June 2000
the values from the range 128-255). The IANA MUST record the Status the values from the range 128-255). The IANA MUST record the Status
values as defined in section 4.4 of this document. values as defined in section 4.4 of this document.
With these assignments, the Type values assigned to the two new With these assignments, the Type values assigned to the two new
messages and to two new extensions, and the error values for the messages and to two new extensions, and the error values for the
Status field, have been identified as not conflicting with any Status field, have been identified as not conflicting with any
numbers defined for Mobile IP to date and documented at numbers defined for Mobile IP to date and documented at
http://www.isi.edu/in-notes/iana/assignments/mobileip-numbers. http://www.isi.edu/in-notes/iana/assignments/mobileip-numbers.
7.0 Security Considerations 7.0 Security Considerations
Xu et al. Expires September 2000 10
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.
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
skipping to change at line 571 skipping to change at line 602
[1] C. Perkins, Editor, "IP Mobility Support", RFC 2002, October [1] C. Perkins, Editor, "IP Mobility Support", RFC 2002, October
1996. 1996.
[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.
Xu et al. Expires December 2000 11
<draft-ietf-mobileip-3Gwireless-ext-04.txt> June 2000
[4] G. Montenegro and V. Gupta. "Sun's SKIP Firewall Traversal for [4] G. Montenegro and V. Gupta. "Sun's SKIP Firewall Traversal for
Mobile IP". RFC 2356, June 1998. Mobile IP". RFC 2356, June 1998.
[5] Pat R. Calhoun and Charles E. Perkins. "Mobile IP Network [5] Pat R. Calhoun and Charles E. Perkins. "Mobile IP Network
Address Identifier Extension". draft-ietf-mobileip-mn-nai- Address Identifier Extension". draft-ietf-mobileip-mn-nai-
05.txt, October 1999. (work in progress). 05.txt, October 1999. (work in progress).
[6] Charles E. Perkins and Pat R. Calhoun. "Mobile IP Challenge/ [6] Charles E. Perkins and Pat R. Calhoun. "Mobile IP Challenge/
Response Extensions". draft-ietf-mobileip-challenge-06.txt, Response Extensions". draft-ietf-mobileip-challenge-06.txt,
October 1999. (work in progress). October 1999. (work in progress).
Xu et al. Expires September 2000 11
[7] Charles E. Perkins and David B. Johnson. "Route Optimization in [7] Charles E. Perkins and David B. Johnson. "Route Optimization in
Mobile IP". draft-ietf-mobileip-optim-08.txt, February 1999. Mobile IP". draft-ietf-mobileip-optim-08.txt, February 1999.
(work in progress). (work in progress).
[8] TIA/EIA/IS-95-B [8] TIA/EIA/IS-95-B
[9] J. Reynolds and J. Postel. ˘ASSIGNED NUMBERS÷. RFC1700, October [9] J. Reynolds and J. Postel. "ASSIGNED NUMBERS". RFC1700, October
1994. 1994.
AuthorsĂ Addresses [10] Farinacci, D., Li, T., Hanks, S., Meyer, D. and Traina, P.,
"Generic Routing Encapsulation (GRE)," RFC 2784, March 2000.
[11] Gopal Dommety. "Key and Sequence Number Extensions to GRE".
draft-dommety-gre-ext-04.txt, June 2000. (work in progress)
Author's Addresses
Yingchun Xu Yingchun Xu
3Com Corporation 3Com Corporation
1800 West Central Road 1800 West Central Road
Mount Prospect, Mount Prospect,
USA 60056 USA 60056
Phone: (847) 342-6814 Phone: (847) 342-6814
Email: Yingchun_Xu@3com.com Email: Yingchun_Xu@3com.com
Rajesh Bhalla Rajesh Bhalla
skipping to change at line 615 skipping to change at line 654
Mount Prospect, Mount Prospect,
USA 60056 USA 60056
Phone: (847) 797-2618 Phone: (847) 797-2618
Email: rajesh_bhalla@3com.com Email: rajesh_bhalla@3com.com
Karl Freter Karl Freter
3Com Corporation 3Com Corporation
1800 W. Central Road 1800 W. Central Road
Mount Prospect, IL 60056 Mount Prospect, IL 60056
Phone: (847) 222-2268 Phone: (847) 222-2268
Xu et al. Expires December 2000 12
<draft-ietf-mobileip-3Gwireless-ext-04.txt> June 2000
Email: karl_freter@3com.com Email: karl_freter@3com.com
Ed Campbell Ed Campbell
3Com Corporation 3Com Corporation
Xu et al. Expires September 2000 12
1800 W. Central Road 1800 W. Central Road
Mount Prospect, IL 60056 Mount Prospect, IL 60056
Phone:(847) 342-6769 Phone:(847) 342-6769
Email: ed_campbell@3com.com Email: ed_campbell@3com.com
Eileen McGrath Hadwen Eileen McGrath Hadwen
Alcatel Alcatel
PO Box 4442, PO Box 4442,
Boulder CO 80306 Boulder CO 80306
Phone: 303 499 1496 Phone: 303 499 1496
skipping to change at line 670 skipping to change at line 711
Atsushi Teshima Atsushi Teshima
HITACHI Ltd. HITACHI Ltd.
216 Totsuka-cho, Totsuka-ku, Yokohama Japan 244-8567 216 Totsuka-cho, Totsuka-ku, Yokohama Japan 244-8567
Phone:+81-45-865-7003 Phone:+81-45-865-7003
Email: atsushi_teshima@cm.tcd.hitachi.co.jp Email: atsushi_teshima@cm.tcd.hitachi.co.jp
Lee Dong Hyun Lee Dong Hyun
HYUNDAI Electronics Industry HYUNDAI Electronics Industry
KOREA Kyungkido Icheonsi 435-050 KOREA Kyungkido Icheonsi 435-050
Xu et al. Expires December 2000 13
<draft-ietf-mobileip-3Gwireless-ext-04.txt> June 2000
Phone: 82-336-630-2756 Phone: 82-336-630-2756
Email: jihs@hei.co.kr Email: jihs@hei.co.kr
Naoto Itoh Naoto Itoh
Xu et al. Expires September 2000 13
IDO Corporation IDO Corporation
Gobancho YS building Gobancho YS building
12-3 Gobancho, Chiyoda-ku, Tokyo Japan 102-8361 12-3 Gobancho, Chiyoda-ku, Tokyo Japan 102-8361
Phone: +81-3-3263-9660 Phone: +81-3-3263-9660
Email: nao-itoh@ido.co.jp Email: nao-itoh@ido.co.jp
Kimihiro Ohki Kimihiro Ohki
KDD Corporation KDD Corporation
3-2, Nishi-Shinjuku 2-chome, 3-2, Nishi-Shinjuku 2-chome,
Shinjuku-ku, Tokyo 163-8003, Japan Shinjuku-ku, Tokyo 163-8003, Japan
skipping to change at line 726 skipping to change at line 769
Phone: (847) 642-4031 Phone: (847) 642-4031
Email: jayapal@cig.mot.com Email: jayapal@cig.mot.com
Peter W. Wenzel Peter W. Wenzel
Nortel Networks Nortel Networks
2201 Lakeside Blvd. 2201 Lakeside Blvd.
Richardson, TX 75082, USA Richardson, TX 75082, USA
Phone: (972) 684-7134 Phone: (972) 684-7134
Email: wenzel@nortelnetworks.com Email: wenzel@nortelnetworks.com
Xu et al. Expires December 2000 14
<draft-ietf-mobileip-3Gwireless-ext-04.txt> June 2000
Carey B. Becker Carey B. Becker
Nortel Networks Nortel Networks
2201 Lakeside Blvd. 2201 Lakeside Blvd.
Xu et al. Expires September 2000 14
Richardson, TX 75082, USA Richardson, TX 75082, USA
Phone: (972) 685-0560 Phone: (972) 685-0560
Email: becker@nortelnetworks.com Email: becker@nortelnetworks.com
James Jiang James Jiang
Nortel Networks Nortel Networks
2201 Lakeside Blvd. 2201 Lakeside Blvd.
Richardson, TX 75082, USA Richardson, TX 75082, USA
Phone: (972)684-5885 Phone: (972)684-5885
Email: jjiang@nortelnetworks.com Email: jjiang@nortelnetworks.com
skipping to change at line 780 skipping to change at line 824
Email: bsemper@telecom.samsung.com Email: bsemper@telecom.samsung.com
Jun Mo Koo Jun Mo Koo
SK Telecom SK Telecom
Phone: 650-568-5762 Phone: 650-568-5762
Email: jmkoo@sktelecom.com 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 December 2000 15
<draft-ietf-mobileip-3Gwireless-ext-04.txt> June 2000
KSOPKZ0101 KSOPKZ0101
Overland Park, KS 66210 Overland Park, KS 66210
Phone: 913-664-8335 Phone: 913-664-8335
Email: Mlipfo01@sprintspectrum.com Email: Mlipfo01@sprintspectrum.com
Xu et al. Expires September 2000 15
Frederic Leroudier Frederic Leroudier
Sprint PCS Sprint PCS
8001 College Blvd. Suite 210 8001 College Blvd. Suite 210
KSOPKZ0101 KSOPKZ0101
Overland Park, KS 66210 Overland Park, KS 66210
Phone: 913-664-8350 Phone: 913-664-8350
Email: FLerou01@sprintspectrum.com Email: FLerou01@sprintspectrum.com
Jim Gately Jim Gately
USWest Advanced Technologies USWest Advanced Technologies
4001 Discovery Drive 4001 Discovery Drive
Boulder, CO 80303 Boulder, CO 80303
Phone: 303-541-6415 Phone: 303-541-6415
Email: jgately@uswest.com Email: jgately@uswest.com
Xu et al. Expires September 2000 16 Xu et al. Expires December 2000 16
 End of changes. 

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