{
  "draft": "draft-ietf-seamoby-context-transfer-problem-stat-04",
  "doc_id": "RFC3374",
  "title": "Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access Network",
  "authors": [
    "J. Kempf, Ed."
  ],
  "format": [
    "TEXT",
    "HTML"
  ],
  "page_count": "14",
  "pub_status": "INFORMATIONAL",
  "status": "INFORMATIONAL",
  "source": "Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting",
  "abstract": "In IP access networks that support host mobility, the routing paths \r\nbetween the host and the network may change frequently and rapidly. \r\nIn some cases, the host may establish certain routing-related \r\nservices on subnets that are left behind when the host moves. \r\nExamples of such services are AAA, header compression, and QoS. In \r\norder for the host to obtain those services on the new subnet, the \r\nhost must explicitly re-establish the service by performing the \r\nnecessary signaling flows from scratch. In some cases, this process \r\nwould considerably slow the process of establishing the mobile host \r\non the new subnet. An alternative is to transfer information on the \r\nexisting state associated with these services, or context, to the \r\nnew subnet, a process called 'context transfer'. This document \r\ndiscusses the desirability of context transfer for facilitating \r\nseamless IP mobility.",
  "pub_date": "September 2002",
  "keywords": [
    "aaa",
    "qos",
    "authentication authorization accounting",
    "quality of service",
    "header compression"
  ],
  "obsoletes": [],
  "obsoleted_by": [],
  "updates": [],
  "updated_by": [],
  "see_also": [],
  "doi": "10.17487/RFC3374",
  "errata_url": null
}