Perkins, C., Editor. IP mobility support. Internet-Draft, draft-ietf-mobileip-protocol-17.txt, May 1996. Work in progress.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....policy lends itself to a scalable design, with respect to both the size of the network and the rate of host mobility. Mobile IP Working Group Proposal IETF has created a Mobile IP working group to come up with a proposal for near term deployment within the Internet (Fig. 10) In this design [18], each mobile host retains its home address regardless of the mobile host s location. When the mobile host visits a foreign network, it is associated with a care of address, which is an Internet address associated with the mobile host s current point of attachment. The care of address identifies ....

C. Perkins, draft-ietf-mobileip-protocol-15.txt;. draft RFC, work in progress, Feb. 1996 (ftp://ds.internet.nic/internet-drafts).

....represented and propagated to routers, and in the details of the mechanisms used to forward packets to mobile hosts. An Internet Engineering Task Force (IETF) Working Group, called the Mobile IP group, was chartered in 1993 to coordinate efforts towards the specification of a protocol, Mobile IP [Perkins 95a] to handle host mobility in the Internet. Although this protocol is still in the process of being specified, it is being developed as an Internet standard. Through the spring of 1995, few (if any) implementations of IETF Mobile IP existed in the public domain. Implementation experience is an ....

....the earlier proposals in areas such as robustness, scalability and security. The IETF Mobile IP Working Group was chartered to develop or adopt architectures and protocols to support mobility within the Internet 1 . This group has been working on the specification of the Mobile IP protocol [Perkins 95a] to support host movement on the Internet. Where it is necessary to distinguish it from other Mobile IP proposals (such as Columbia University Mobile IP [Ioannidis et al. 91] we will refer to the IETF protocol as IETF Mobile IP. The remainder of this section describes the (draft) protocol. 2.2 ....

C. Perkins, IP Mobility Support, draft-ietf-mobileip-protocol-11.txt, Mobile IP Working Group, Internet Draft, July 1995.

....a forwarding list that records the mobility bindings in force; that is, at the home agent for each of its hosts that is away from home, and at the previous agent for each host that has visited this agent before. The basic scheme for supporting mobile hosts is mainly drawn from the IETF work [16]. A mobile host has a permanent (home) IP address in the same way as any other host, thus the address acting as its logical identifier. A current agent s address represents a mobile host s current location, that is it acts as a physical locator. So, all packets destined for a mobile host are ....

C. Perkins, IP Mobility Support, draft-ietf-mobileip-protocol-16.txt, work in progress, 1996.

....With the many portable computing devices already available, the demand for access to the Internet from mobile users will soon be irresistible. In anticipation, the Internet Engineering Task Force (IETF) has put out the 16th draft on how the Internet Protocol (IP) can support mobile computing [Pe]. Because the Internet started out small and took several years for the infrastructure to grow from its Arpanet origin, there was enough time to refine the protocols and tune their parameters while traffic grew year by year. The invasion of mobile users, however, will not be similarly constrained. ....

C. Perkins (ed.), IP mobility support, draft-ietf-mobileip-protocol-16.txt (Apr. 1996).

.... given time, but it is assumed that the MH will be able to maintain a network connection while moving across the cell of one base station into that of another base station [9] The task of forwarding data between the static network and the MH, which is termed hand off, is transparent to the user [18]. 2 Environment Mobile computing has wider acceptance in public applications including local ambulance services. The ambulance service is responsible not only for the retrieval and delivery of patients to the hospital but also for immediate treatment. EMTs are able to treat patients more ....

C. Perkins. IP Mobility Support. Internet Draft, ftp://nic.nordu.net/ internet-drafts/ - draft-ietf-mobileip-protocol-08.txt, 1995.

....the location updates directly from the mobile host to the home gateway can cache the binding as well. Once the binding information is available at a given location, the packets from that location to the mobile hosts are routed directly without having to go to the home gateway. IETF Proposal [Perkins95] 27 Each MH belongs to a home network and is assigned a home agent. When the MH is away of home network is assigned a temporary address called care of address and the home agent keeps track of the MH s care of address. When the MH is registered to a MSS away of its home network the new MSS ....

Charles Perkins: IP Mobility Support, Number Internet Draft, IETF Mobile IP Group, January 1995, ftp://software.watson.ibm.com/pub/mobile-ip/ draft-ietf-mobileipprotocol -08.txt.

....the point of attachment of the unit changes. Several methods of handling the problems associated with mobile IP have been proposed and a committee of the Internet Engineering Task Force (IETF) is currently working on protocol specifications, referred to as an RFC, which will handle these problems [43]. Network layer concerns are not addressed further in this document. However, the reader is encourage to consult the following 11 sources for a better understanding of the issues and concerns of this layer [6, 21, 26, 29, 30 33, 37, 42, 43, 49, 50 52, 54, 55] 1.4 Desired traits or features in ....

....on protocol specifications, referred to as an RFC, which will handle these problems [43] Network layer concerns are not addressed further in this document. However, the reader is encourage to consult the following 11 sources for a better understanding of the issues and concerns of this layer [6, 21, 26, 29, 30 33, 37, 42, 43, 49, 50 52, 54, 55]. 1.4 Desired traits or features in a wireless local area network (WLAN) A look at the desired features in a wireless local area network will provide further insight into the architectural issues of this form of networking. Some of the features that would be beneficial in a wireless network can ....

[Article contains additional citation context not shown here]

Perkins C. draft-ietf-mobileip-protocol-08.txt, Draft RFC, work in progress, January 1995.

....only cross cells when they have to transport an injured soldier to a hospital or if they are called to an area with a large number of wounded soldiers. The task of forwarding data between the static network and the MH during cell crossing, which is termed hand off, is transparent to the user [17]. 2 Environment The battlefield is a very unique environment due to the fact that the medical staff are limited in access to a standard hospital that is available in a large U.S. city [15] The battlefield medical environment differs from the civilian medical environment in the fact that 1) ....

C. Perkins. IP Mobility Support. Internet Draft, ftp://nic.nordu.net/ internet-drafts/ draft-ietfmobileip -protocol-08.txt, 1995.

.... : Integrated Services, Internet Protocols, Mobility, Multimedia, Reservation Protocol, Quality of Service 1 Introduction Recent progress in computing technology and wireless digital communication has initiated intensive research on providing seamless connectivity at network and transport layers[23, 4, 2, 16]. Also, there have been several proposals for supporting real time applications in an Integrated Services Packet Network (ISPN) Typical applications that require real time services include audio library, image browsing, video conferencing and video on demand. Clark et al. 9] have described an ....

....weaker QoS guarantees or best effort service. However, when a passive reservation becomes active (i.e. when the flow of the mobile host who made the passive reservation moves into that link) these flows may be affected. A unicast packet is delivered to a mobile host by using the Mobile IP[23] routing protocol. In such a case, resource reservations for a mobile host must be established along the route determined by Mobile IP. This implies that, when the mobile host is located in a foreign subnet and the unicast packets for the mobile host is delivered via its home agent by IPIP ....

Perkins, C., Editor. IP mobility support. Internet-Draft, draft-ietf-mobileip-protocol-17.txt, May 1996. Work in progress.

....[18, 15] which track object movement by extending and short cutting. SSP Chains provide transparent referencing of remote objects in a distributed system. They garbage collect unused objects, they are cheap and fault tolerant. We also assume an underlying mobile network layer, such as Mobile IP [13] or IPv6 [4] so that SSP Chains do not explicitly reference objects using host addresses. 4.2 Funnel model To allow SSP Chains to deal with host mobility and disconnections [1] we use distinguished nodes called funnels. A funnel is located on the xed network. A mobile host communicates with ....

Perkins, C. Ip mobility support. Tech. Rep. Internet Draft, IETF Mobile IP Group, Jan. 1995. ftp://software.watson.ibm.com/pub/mobile-ip/draft-ietf-mobileip-protocol-08.txt.

....address changes. Even if the IP address of a mobile host s network interface changes when it moves from one network to another, the mobile host should be able to continue corresponding with other machines in the Internet. Most mobile IP protocols [Bla94] Gup96] Hag93] Ioa93] Myl93] Per94] [Per96a] [Tas94] Ter94] address this problem by allowing a mobile host to use its home network IP address no matter where it currently resides. Of these protocols, the protocol specified by the Internet Engineering Task Force (IETF) Per96a] has become the most popular. It is simple, compatible with ....

....IP protocols [Bla94] Gup96] Hag93] Ioa93] Myl93] Per94] Per96a] Tas94] Ter94] address this problem by allowing a mobile host to use its home network IP address no matter where it currently resides. Of these protocols, the protocol specified by the Internet Engineering Task Force (IETF) [Per96a] has become the most popular. It is simple, compatible with existing applications and hosts, and places no special burdens on normal IP routers in the Internet. When trying to implement the IETF protocol, however, we ran into several problems that led us to conclude that one size does not fit all. ....

Charles E. Perkins. IP Mobility Support. draftietf -mobileip-protocol-16.txt --- work in progress, 22 April 1996.

....that information access becomes one of the most important application on nomadic hosts. Mobility is a major issue in nomadic communication. It should be integrated in a transparent way independently of location. This goal can be achieved at the network layer, for example by means of mobile IP [19, 5]. This solution allows a mobile host to send and receive packets addressed with its home IP address regardless of its current point of attachment. It maintains communication association such as TCP connections even if the point of attachment changes during their lifetime. Mobile IP is based on ....

....support for nomadic applications, and mobile agents. Much work has been done in the area of communication protocols for nomadic hosts. The first problem that the protocols must solve is mobility. As mentioned previously, existing solutions for mobility appear mainly at the network layer: mobile IP [19, 5] or IPv6 [20, 26] The second problem is performance. Many projects try to optimize performance over lowbandwidth wireless connections [2] or propose specific protocols [10, 3] However, the bandwidth of such connections limits application performance regardless of the optimized or specific ....

C.E. Perkins. IP mobility support, draft-ietf- -mobileip-protocol-16.txt. 1995.

....[18, 15] which track object movement by extending and shortcutting. SSP Chains provide transparent referencing of remote objects in a distributed system. They garbage collect unused objects, they are cheap and fault tolerant. We also assume an underlying mobile network layer, such as Mobile IP [13] or IPv6 [4] so that SSP Chains do not explicitly reference objects using host addresses. 4.2 Funnel model To allow SSP Chains to deal with host mobility and disconnections [1] we use distinguished nodes called funnels. A funnel is located on the fixed network. A mobile host communicates with ....

Perkins, C. Ip mobility support. Tech. Rep. Internet Draft, IETF Mobile IP Group, Jan. 1995. ftp://software.watson.ibm.com/pub/mobile-ip/draft-ietfmobileip -protocol-08.txt.

....easily available. This has led to an intensive research in the area of Mobile Computing to provide mobile users access to an inter network. The research, so far, has focussed on the problem of maintaining connectivity at the network and transport layer in spite of the mobility of the mobile hosts[18, 4, 2, 14]. Also, there have been several proposals for supporting real time applications in an Integrated Services Packet Network (ISPN) Typical applications that require real time services include audio library, image browsing, video conferencing and video on demand. These multimedia applications require ....

....care of address can be the either a foreign agent care of address or a co located care of address. A foreign agent care of address is an IP address of a foreign agent in the foreign subnet. A mobile node acquires a foreign agent care of address using Router Solicitation and Router Advertisement[18, 19, 8] messages. A co located care of address is a care of address acquired by the mobile node as a local IP address. This care of address may be dynamically acquired by the mobile node through Dynamic Host Configuration Protocol (DHCP) 10] or may be owned by the mobile node as a long term address for ....

Perkins, C., Editor. IP mobility support. Internet-Draft, draft-ietf-mobileip-protocol-17.txt, May 1996. Work in progress.

....a network [2, 4, 5, 6] Ideally, mobile hosts can change their network attachment point, in a fashion which is completely transparent to the transport layer protocols and the applications running above them. All proposed solutions for Mobile IP, for example, meet this goal. The Mobile IP approach [3] automatically provides location transparency. Portable Computers, like any other desktop computer, need to access resources such as NFS file system, name servers, etc. Existing portable systems are configured to make use of resources available on their home networks. As a result, portable systems ....

Charles Perkins. draft-ietf-mobileip-protocol07. txt. Draft RFC - work in progress, Nov 1994.

....policy lends a scalable design; both with respect to the size of the network, and the rate of host mobility. 5.4 Mobile IP working group Proposal IETF has created a Mobile IP working group to come up with a proposal for near term deployment within the Internet. In this design [16], each mobile host retains its home address regardless of the mobile host s location. When the mobile host visits a foreign network, it is associated with a care of address, which is an Internet address associated with the mobile host s current point of Source S LD g f Home Network g MH 1 MH 2 ....

Charles Perkins. draft-ietf-mobileip-protocol-15.txt. Draft RFC - work in progress, Feb 1996. (ftp://ds.internet.nic/internet-drafts).

....of attaching to the Internet through radio equipped base stations called Foreign Agents or FA s. The MH is assigned a constant IP address (that does not change with location) called it s home address, by its home agent (HA) and a temporary foreign address by its FA. The IETF Mobile IP proposal [15] is similar to the Columbia proposal ( 11] in the sense that both embrace the sub optimal basic triangle routing method of routing packets to MHs located away from their home networks. The Mobile IP proposal from Harvard University [5] proposes implementation of a secure short cut routing ....

....IP scheme has been proposed in [12] Mobile location caches, maintained at the correspondent hosts or FAs, store the mobility bindings for the MHs. This cache can be updated either by the home agent or by other FAs that have a more recent binding. 12] also extends the registration protocol in [15], in order to ensure that previous FAs can update their cache with the new foreign address after the MH has moved to a new location. Our approach differs from [5] and [12] in that information will not be arbitrarily given to all sources that communicate with the MH. Another approach to the problem ....

C.Perkins (ed.), IP Mobility Support, draft-ietf-mobileip-protocol -11.txt, Mobile IP WG, Internet Draft, July 1995.

....policy lends a scalable design; both with respect to the size of the network, and the rate of host mobility. 5.4 Mobile IP working group Proposal IETF has created a Mobile IP working group to come up with a proposal for near term deployment within the Internet. In this design [13], each mobile host retains its home address regardless of the mobile host s location. When the mobile host visits a foreign network, it is associated with a care of address, which is an Internet address associated with the mobile host s current point of attachment. The care of address either ....

Charles Perkins. draft-ietf-mobileip-protocol-15.txt. Draft RFC - work in progress, Feb 1996. (ftp://ds.internet.nic/internet-drafts).

....problem. When a host moves to a new location, it is required to send a broadcast in the network to purge all cached LD entries. 5.3 MobileIP working group Proposal IETF has created a MobileIP working group to come up with a proposal for near term deployment within the Internet. In this design [11], each mobile host retains its home address regardless of the mobile host s location. When the mobile host visits a foreign network, it is associated with a care of address, which is an Internet address associated with the mobile host s current point of attachment. The care of address either ....

Charles Perkins. draft-ietf-mobileip-protocol-09.txt. Draft RFC - work in progress, June 1995.

No context found.

Perkins, C., Editor. IP mobility support. Internet-Draft, draft-ietf-mobileip-protocol-17.txt, May 1996. Work in progress.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC