draft-ietf-mobileip-3gwireless-ext-05.txt   draft-ietf-mobileip-3gwireless-ext-06.txt 
Mobile IP Working Group Yingchun Xu (editor) Mobile IP Working Group Yingchun Xu (editor)
Internet Draft WaterCove Networks Internet Draft WaterCove Networks
November, 2000 Rajesh Bhalla May, 2001 Rajesh Bhalla
Ed Campbell 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
skipping to change at line 52 skipping to change at line 52
Jun Mo Koo Jun Mo Koo
SK Telecom SK Telecom
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-05.txt> <draft-ietf-mobileip-3gwireless-ext-06.txt>
Xu et al. Expires April 2001 1 Xu et al. Expires Nov. 2001 1
<draft-ietf-mobileip-3gwireless-ext-05.txt> Nov. 2000 <draft-ietf-mobileip-3Gwireless-ext-06.txt> May 2001
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 108
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
Xu et al. Expires April 2001 2 Xu et al. Expires Nov. 2001 2
<draft-ietf-mobileip-3Gwireless-ext-05.txt> Nov. 2000 <draft-ietf-mobileip-3Gwireless-ext-06.txt> May 2001
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
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.
skipping to change at line 164 skipping to change at line 164
| | Interface | | | | | | Interface | | | |
+---------+ +---------+ +---------+ +---------+ +---------+ +---------+
/|\ /|\
| Visited Access Home Network | Visited Access Home Network
| Provider Network | Provider Network
| |
| |
\|/ \|/
+--------+ +--------+
Xu et al. Expires April 2001 3 Xu et al. Expires Nov. 2001 3
<draft-ietf-mobileip-3Gwireless-ext-05.txt> Nov. 2000 <draft-ietf-mobileip-3Gwireless-ext-06.txt> May 2001
| Mobile | | Mobile |
| Node | | 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
skipping to change at line 220 skipping to change at line 220
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Xu et al. Expires April 2001 4 Xu et al. Expires Nov. 2001 4
<draft-ietf-mobileip-3Gwireless-ext-05.txt> Nov. 2000 <draft-ietf-mobileip-3Gwireless-ext-06.txt> May 2001
| Care-of Address | | Care-of Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ Identification + + Identification +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Extensions ... | Extensions ...
+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-
skipping to change at line 276 skipping to change at line 276
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Xu et al. Expires April 2001 5 Xu et al. Expires Nov. 2001 5
<draft-ietf-mobileip-3Gwireless-ext-05.txt> Nov. 2000 <draft-ietf-mobileip-3Gwireless-ext-06.txt> May 2001
| MN ID Type | MN ID Length | MN ID | | MN ID Type | MN ID Length | MN ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MN ID ... | MN ID ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
skipping to change at line 332 skipping to change at line 332
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 format, the length field value ranges from 10
to 15 bytes. to 15 bytes.
MN ID MN ID
This is the Mobile Node ID, which is globally 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 April 2001 6 Xu et al. Expires Nov. 2001 6
<draft-ietf-mobileip-3Gwireless-ext-05.txt> Nov. 2000 <draft-ietf-mobileip-3Gwireless-ext-06.txt> May 2001
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.
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
skipping to change at line 386 skipping to change at line 386
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Reserved | | Type | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Home Address | | Home Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Home Agent Address | | Home Agent Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ Identification + + Identification +
Xu et al. Expires April 2001 7 Xu et al. Expires Nov. 2001 7
<draft-ietf-mobileip-3Gwireless-ext-05.txt> Nov. 2000 <draft-ietf-mobileip-3Gwireless-ext-06.txt> May 2001
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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
skipping to change at line 441 skipping to change at line 441
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Care Of Address | | Care Of Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ Identification + + Identification +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Extensions ... | Extensions ...
+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-
Xu et al. Expires April 2001 8 Xu et al. Expires Nov. 2001 8
<draft-ietf-mobileip-3Gwireless-ext-05.txt> Nov. 2000 <draft-ietf-mobileip-3Gwireless-ext-06.txt> May 2001
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
skipping to change at line 496 skipping to change at line 496
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 April 2001 9 Xu et al. Expires Nov. 2001 9
<draft-ietf-mobileip-3Gwireless-ext-05.txt> Nov. 2000 <draft-ietf-mobileip-3Gwireless-ext-06.txt> May 2001
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.
skipping to change at line 530 skipping to change at line 530
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 IANA Considerations 6.0 IANA Considerations
This document specifies two new messages and two new extensions to The recommended message type value and extension type value have
Mobile IP protocol [1]. The numbers to be assigned to these messages been used in 3GPP2 standard IOSv4.1. It is desirable to have the
and extensions have been taken from the numbering space assigned to same type value assigned by IANA.
Mobile IP in RFC 2002 [1] and extended in RFC 2356 [4].
The Registration Request and Registration Update messages MUST be The well-known UDP port number 699 used for the Registration Request
sent with UDP using well-known port number 699. This port number is and Registration Update Message was chosen from the unassigned port
chosen from the unassigned port range as specified in RFC1700 [9]. range. They were requested from and have been assigned by IANA and
are listed at: ftp://ftp.isi.edu/in-notes/iana/assignments/port-
numbers.
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 SHOULD be assigned the Type values of 20 and
respectively. 21 respectively.
The Session Specific Extension defined in section 4.2 MUST be The Session Specific Extension defined in section 4.2 SHOULD 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 SHOULD 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 April 2001 10 Xu et al. Expires Nov. 2001 10
<draft-ietf-mobileip-3Gwireless-ext-05.txt> Nov. 2000 <draft-ietf-mobileip-3Gwireless-ext-06.txt> May 2001
the values from the range 128-255). The IANA MUST record the Status the values from the range 128-255). The IANA SHOULD record the
values as defined in section 4.4 of this document. Status 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
The protocol presented in this draft is designed for use over a The protocol presented in this draft is designed for use over a
skipping to change at line 601 skipping to change at line 602
draft [7]. 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.
[2] G. Montenegro, "Reverse Tunneling for Mobile IP", RFC2344, May [2] G. Montenegro, "Reverse Tunneling for Mobile IP", RFC2344, May
1998. 1998.
Xu et al. Expires April 2001 11 Xu et al. Expires Nov. 2001 11
<draft-ietf-mobileip-3Gwireless-ext-05.txt> Nov. 2000 <draft-ietf-mobileip-3Gwireless-ext-06.txt> May 2001
[3] G. Montenegro and V. Gupta. "Sun's SKIP Firewall Traversal for [3] G. Montenegro and V. Gupta. "Sun's SKIP Firewall Traversal for
Mobile IP". RFC 2356, June 1998. Mobile IP". RFC 2356, June 1998.
[4] Pat R. Calhoun and Charles E. Perkins. "Mobile IP Network [4] Pat R. Calhoun and Charles E. Perkins. "Mobile IP Network
Address Identifier Extension". RFC2794, March 2000. Address Identifier Extension". RFC2794, March 2000.
[5] Charles E. Perkins and Pat R. Calhoun. "Mobile IP Challenge/ [5] 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).
skipping to change at line 654 skipping to change at line 655
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
Email: karl_freter@3com.com Email: karl_freter@3com.com
Xu et al. Expires April 2001 12 Xu et al. Expires Nov. 2001 12
<draft-ietf-mobileip-3Gwireless-ext-05.txt> Nov. 2000 <draft-ietf-mobileip-3Gwireless-ext-06.txt> May 2001
Ed Campbell Ed Campbell
3Com Corporation 3Com Corporation
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
skipping to change at line 711 skipping to change at line 712
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
Phone: 82-336-630-2756 Phone: 82-336-630-2756
Email: jihs@hei.co.kr Email: jihs@hei.co.kr
Xu et al. Expires April 2001 13 Xu et al. Expires Nov. 2001 13
<draft-ietf-mobileip-3Gwireless-ext-05.txt> Nov. 2000 <draft-ietf-mobileip-3Gwireless-ext-06.txt> May 2001
Naoto Itoh Naoto Itoh
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
skipping to change at line 767 skipping to change at line 768
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
Carey B. Becker Carey B. Becker
Xu et al. Expires April 2001 14 Xu et al. Expires Nov. 2001 14
<draft-ietf-mobileip-3Gwireless-ext-05.txt> Nov. 2000 <draft-ietf-mobileip-3Gwireless-ext-06.txt> May 2001
Nortel Networks Nortel Networks
2201 Lakeside Blvd. 2201 Lakeside Blvd.
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.
skipping to change at line 824 skipping to change at line 825
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
KSOPKZ0101 KSOPKZ0101
Overland Park, KS 66210 Overland Park, KS 66210
Xu et al. Expires April 2001 15 Xu et al. Expires Nov. 2001 15
<draft-ietf-mobileip-3Gwireless-ext-05.txt> Nov. 2000 <draft-ietf-mobileip-3Gwireless-ext-06.txt> May 2001
Phone: 913-664-8335 Phone: 913-664-8335
Email: Mlipfo01@sprintspectrum.com Email: Mlipfo01@sprintspectrum.com
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 April 2001 16 Xu et al. Expires Nov. 2001 16
 End of changes. 

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