draft-ietf-seamoby-ct-reqs-02.txt   draft-ietf-seamoby-ct-reqs-03.txt 
Internet Engineering Task Force Hamid Syed Internet Engineering Task Force Hamid Syed
Internet Draft Gary Kenward Internet Draft Gary Kenward
draft-ietf-seamoby-ct-reqs-02.txt Pat Calhoun draft-ietf-seamoby-ct-reqs-03.txt Pat Calhoun
Expires: May 2002 Madjid Nakhjiri Expires: July 2002 Madjid Nakhjiri
Rajeev Koodli Rajeev Koodli
Kulwinder Atwal Kulwinder Atwal
Mark Smith Mark Smith
Govind Krishnamurthi Govind Krishnamurthi
November, 2001 January, 2002
General Requirements for Context Transfer General Requirements for Context Transfer
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. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at line 226 skipping to change at line 226
4.12 The context information to be transferred MUST be available at the 4.12 The context information to be transferred MUST be available at the
AR performing the transfer, prior to the initiation of a given phase AR performing the transfer, prior to the initiation of a given phase
of the context transfer. of the context transfer.
To effect a rapid transfer, the context information has to be readily To effect a rapid transfer, the context information has to be readily
available when the AR begins a phase of the transfer. available when the AR begins a phase of the transfer.
If the context transfer is comprised of a single phase, then all of the If the context transfer is comprised of a single phase, then all of the
context must be available prior to the transfer initiation. context must be available prior to the transfer initiation.
4.13 The context transfer solution WILL NOT verify the context information 4.13 The context transfer solution MUST include methods for interworking
prior to transfer.
The context transfer solution may provide mechanisms to support the
reliable transfer of context, however, it is not the purpose of the context
transfer solution to verify the context at the source prior to transfer.
The effectiveness of context transfer in enhancing handover between ARs
would very likely be compromised if the context at the source is malformed.
Nonetheless, ensuring the integrity of the context at the source requires
specific knowledge of the syntax and semantics of the context representation
for each feature and this is outside the scope of the context transfer solution.
4.14 The context transfer solution MUST include methods for interworking
with any IETF IP mobility solutions. with any IETF IP mobility solutions.
4.15 The context transfer solution MAY include methods for interworking 4.14 The context transfer solution MAY include methods for interworking
with non-IETF mobility solutions. with non-IETF mobility solutions.
4.16 The context transfer solution MUST include methods for interworking 4.16 The context transfer solution MUST be scalable.
with any IETF IP handover solutions.
4.17 The context transfer solution MUST be scalable.
5. Protocol Requirements 5. Protocol Requirements
This section captures the general requirements for the context This section captures the general requirements for the context
transfer protocol. transfer protocol.
5.1 General Protocol Requirements 5.1 General Protocol Requirements
5.1.1 The context transfer protocol MUST be capable of transferring all 5.1.1 The context transfer protocol MUST be capable of transferring all
of the different types of feature context necessary to support the of the different types of feature context necessary to support the
skipping to change at line 447 skipping to change at line 431
7 Acknowledgements 7 Acknowledgements
Thank you to all who participated in the Seamoby working group context Thank you to all who participated in the Seamoby working group context
transfer design team. transfer design team.
8 Author's Addresses 8 Author's Addresses
Hamid Syed Hamid Syed
100 Constellation Crescent 100 Constellation Crescent
Nepean, Ontario. K2G 6J8 Phone: 1 613 763 6553 Ottawa, Ontario. K2G 6J8 Phone: 1 613 763 6553
Canada Email: hmsyed@nortelnetworks.com Canada Email: hmsyed@nortelnetworks.com
Gary Kenward Gary Kenward
100 Constellation Crescent 100 Constellation Crescent
Nepean, Ontario. K2G 6J8 Phone: 1 613 765 1437 Ottawa, Ontario. K2G 6J8 Phone: 1 613 765 1437
Canada Email: gkenward@nortelnetworks.com Canada Email: gkenward@nortelnetworks.com
Pat R. Calhoun Pat R. Calhoun
Black Storm Networks Black Storm Networks
250 Cambridge Avenue, Suite 200 250 Cambridge Avenue, Suite 200
Palo Alto, CA 94306 Phone: +1 650 617 2932 Palo Alto, CA 94306 Phone: +1 650 617 2932
USA Email: pcalhoun@bstormnetworks.com USA Email: pcalhoun@bstormnetworks.com
Madjid Nakhjiri Madjid Nakhjiri
Motorola Motorola
 End of changes. 

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