Transcript 21-05-0343-00

IEEE 802.21 MEDIA INDEPENDENT HANDOVER
DCN: 21-05-0330-00-0000
Title: 802.21 Higher Layer requirements for IETF
Date Submitted: August 2, 2005
Presented at 63rd IETF session in Paris, France
Authors or Source(s):
Ajay Rajkumar, Chair 802.21
[email protected]
Abstract: Result of preliminary discussion on 802.21 Higher Layer
requirements for IETF
21-05-0330-00-0000
IEEE 802.21 presentation release statements
This document has been prepared to assist the IEEE 802.21 Working Group. It is
offered as a basis for discussion and is not binding on the contributing
individual(s) or organization(s). The material in this document is subject to
change in form and content after further study. The contributor(s) reserve(s)
the right to add, amend or withdraw material contained herein.
The contributor grants a free, irrevocable license to the IEEE to incorporate
material contained in this contribution, and any modifications thereof, in the
creation of an IEEE Standards publication; to copyright in the IEEE’s name
any IEEE Standards publication even though it may include portions of this
contribution; and at the IEEE’s sole discretion to permit others to reproduce in
whole or in part the resulting IEEE Standards publication. The contributor also
acknowledges and accepts that this contribution may be made public by IEEE
802.21.
The contributor is familiar with IEEE patent policy, as outlined in Section 6.3 of
the IEEE-SA Standards Board Operations Manual
<http://standards.ieee.org/guides/opman/sect6.html#6.3> and in
Understanding Patent Issues During IEEE Standards Development
http://standards.ieee.org/board/pat/guide.html>
21-05-0330-00-0000
Scenarios considered by 802.21 WG
• Between 802.xx and 802.yy
• 802.3
• 802.11
• 802.15
• 802.16
• Between 802.xx and Cellular
• 3GPP standards
• 3GPP2 standards
• Between 802.11 ESS
21-05-0330-00-0000
What does Heterogeneous Handover
Mean?
• Session Continuity at the IP layer
• Adaptation to new link at layer two
• Address continuity at layer three
• Service Continuity at the Application layer(s)
21-05-0330-00-0000
Reference Model
21-05-0330-00-0000
Information Service
• Link access parameters
• Security mechanisms
• Neighbor maps
• Location
• Provider and other Access information
• Cost of link
• Etc.
21-05-0330-00-0000
IS Requirements
• Two types of requirements:
• Transport requirements
• Architectural/protocol requirements
• Terminology:
• Network MIHF Instance (NMI)
• Resides in MIH-enabled network element
• Network element must be Layer-4 capable
• Mobile MIHF Instance (MMI)
• Resides in Mobile Node
• Protocol vs. interfaces: two interfaces considered (separately) to
identify requirements
• MMI  NMI is here referred to as “access” MIIS I/F
• NMI  NMI is here referred to as “network” MIIS I/F
21-05-0330-00-0000
Transport Requirements for MIIS
• “access” MIIS I/F:
•
Reliability:
• “network” MIIS I/F
•
Reliability:
21-05-0330-00-0000
Architectural/Protocol Requirements
for MIIS (1)
• Generic requirement for “access” and “network” interface:
•
•
•
•
Protocol messages carry Information Elements specified in 802.21
Protocol defines message format and message payload
Protocol exchanges are query-based (request/response); scenarios where
“delayed” response is provided asynchronously based on an MMI/NMI
request are also considered
Protocol should be independent of any specific mobility protocol
21-05-0330-00-0000
Architectural/Protocol Requirements
for MIIS (2)
• “access” MIIS I/F:
•
Discovery capability:
•
•
•
•
The MMI must be able to discover presence of NMI for accessing IS
service (discovered NMI could be the actual IS server) in either the serving
network or candidate network
The MMI must be able to discover address of NMI for accessing to IS
service in either the serving network or candidate network to exchange L3
or above traffic
It should be possible to drive discovery of NMI for accessing to IS service
though information provided by MMI (e.g. MMI indicates that NMI for
802.11 or 802.16 is needed, if there is one)
Security:
•
•
•
•
•
•
As part of discovery, the MMI must be able to discover whether a security
association can/shall be established with the NMI in either the serving
network or candidate network, and if yes which credentials can be used to
authenticate with NMI
Protocol allows for authentication of NMI by MMI
Protocol enables mutual authentication between MMI and NMI
Payload encryption is optional. On/off decision can be made during
discovery phase (e.g. mandated by MMI or NMI policies)
Integrity protection is supported and required for IS
Replay detection is optional for MIIS
21-05-0330-00-0000
Architectural/Protocol Requirements
for MIIS (3)
• “network” MIIS I/F
•
Security:
•
•
•
•
Protocol enables mutual authentication between NMIs
Payload encryption is optional. On/off decision can be made e.g. based on
NMI policies
Integrity protection is supported and required for IS
Replay detection is optional
21-05-0330-00-0000