MetaCartSign in to MyCiteSeer

Include Citations | Advanced Search | Help

Include Citations | Advanced Search | Help

  Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access Network

Download:
Download as a PDF
by Status Of This Memo
http://www.tzi.de/~cabo/pdfrfc/rfc3374.txt.pdf
Add To MetaCart

Abstract:

This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2002). All Rights Reserved. In IP access networks that support host mobility, the routing paths between the host and the network may change frequently and rapidly. In some cases, the host may establish certain context transfer candidate services on subnets that are left behind when the host moves. Examples of such services are Authentication, Authorization, and Accounting (AAA), header compression, and Quality of Service (QoS). In order for the host to obtain those services on the new subnet, the host must explicitly re-establish the service by performing the necessary signaling flows from scratch. In some

Citations

834 Security architecture for the Internet protocol – Kent, Atkinson - 1998
148 The Point-to-Point Protocol (PPP – Simpson - 1994
1 IP Mobility Support", RFC 3220 – Perkins - 2002
1 Standard for Port based Network Access Control – 1XD11 - 2001
1 RObust Header Compression (ROHC): Framework and four profiles – Zheng - 2001
1 802.11f/D2.0, "Draft Recommended Practice for MultiVendor Access Point Interoperability via an Inter-Access Point Protocol Across Distribution Systems Supporting IEEE 802.11 Operation – Std - 2001
1 10] RFC 3374 Context Transfer Problem Statement September 2002 11.0 Complete List of Authors’ Addresses O. Henrik Levkowetz A Brand New World Osterogatan 1 S-164 28 Kista SWEDEN Phone: +46 8 477 9942 EMail: henrik@levkowetz.com Pat R. Calhoun Black Storm – Informational