Transcript 21-07-0074-01-0000-Information_Elements_Update

IEEE 802.21 MEDIA INDEPENDENT HANDOVER
DCN: 21-07-0074-00-0000
Title: IEs related Issues
Date Submitted: March 2007
Presented at IEEE 802.21 session in Orlando, Florida
Authors or Source(s):
Vivek Gupta
Abstract: Discusses IEs related issues as described in the IEEE
P802.21/D04.00 draft
1
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>
2
Overview

Related Comments LB-1b:






3098
3099
3105
3115
3116
3156
3
Issues

IE Extensibility: Table-8, page 52



Should we delete rows that reserve range for 802 WGs and IETF and just call it
Reserved for other SDOs

YES. MIPSHOP didn’t respond through casual liaison about keeping IETF range

Can’t maintain binary encoding format directly in RDF schema, so correspondence is
manual today
IEEE has an authority to allocate this space, c.f. .16 operator ID allocation
One suggestion, add a new property to the RDF IE class that is the same value as the
TYPE and LENGTH for each IE in binary encoding form. Then when schema is updated,
binary TYPEs are allocated with them
Can update URL to create new basic schema, but have to rev the spec to do it tight now
See contribution 57 regarding Vendor specific IEs
How to manage this space?



– Discussion that the URL must contain backwards compatible data and
a version number so no need to update the spec. Only add new IE’s
no deletion or change of existing IE’s in basic schema.
– Comment that IANA always updates the version number within the
URL

IE Table-8 other updates


Remove referenve to Core IE’s. IE’s are ONLY information service elemnts. Header
fields are TLVs not IEs
Remove reservation slots in table so there are only five slots, 0, 802.21, vendor
specific, playpen, reserved
4
Issues

IE_Network_Security

Add Cipher suites and Authentication Methods



Don’t need these. Not very helpful in handover decision making. Instead of
comparing encryption depth across different encryption methods (tough job)
just have policy implemented by having only one or two methods and looking
for networks that support those specific methods/depths.
Comment that network standards IE has .11’s security descriptors only
Modify this IE to supply the following

Discussion that roaming agreement query plus operator id query together
allows determining which credential will work
– Need a simple binary encoding container / query for this

Comment that .11 requested IS to tell if there is open auth along with WPA,
WPA2 etc.
– Need to have bit to indicate there is open auth here
– In future need bit to indicate HOKEY supported here
– May include information about NAT/VPN
5
Issues

IE_Network_QoS







Just provide Network Standards
No specifics?
Discussion of extending IANA table by .21 request
Comment this doesn’t work well for EVDO, HSDPA, etc ie.e no
way to indicate them
Comment that CoS attributes in T14 may not apply to all linke
types
Need to redefine the IE according to editor’s note efficiently (e.g.
don’t keep repeating link type for each parameter/value pair)
Access Control: Deferred to E. Hepworth Acess Control SIG
6
Issues


Add TYPE_IE_WLAN _SYSTEM_ID to support a usage scenario to obtain
ssid info of wlan system from netwokr_id
Vendor specific IE needs to be considered about assignment.


21-07-0057
- Change OperatorNamespace row to:

Namespace ID | 1 | The value within this field contains the operator
namespace identifier. The Namespace ID values
are defined in [ietf-draft-ietf-geopriv-radius-lo-10.txt].


Integer Value for the cost is not sufficient for some currency (e.g., the
value could be less than 1 for USD).
t seems that "Network Type " IE is missing from Network Standards TLV
representation. Otherwise, how the bitmap definition will work?
7
802.11 Use Case Flow Diagram
STA
IS Local
AP
Pre-configuration
State 1
Beacon( Interworking IE,
GAS=APID)
IS (SSPN
Home Network)
Pre-configuration
Advertising protocol = IS,
LEN=Length, IS discovery
Probe Request
Probe Response (I/W IE GAS+APID)
QueryId is
Passed from
.11u to .21,
comes from AP
GAS Initial Request
( request IE, APID, list of SSPNs ?)
Relays MIH Frame (list of SSPNs)
( Ethernet frame, IP )
Gas Init Resp (Query Id, Dialog Token)
Gas Comeback req (query Id)
MIH Frame Response
(transaction Id, Info)
Gas comeback resp (query Id , Info)
Out of Scope
802.21
TGu
8
802.11 Use Case Notes






How does the AP discover IS?
How does the AP communicate with IS…ethernet frame,
IP/MIPSHOP?
The AP needs a Query Id to match request from STA with the
response it gets from IS server. The STA generates this QueryId and
AP inserts this QueryId back into the packet it sends to the AP. This
QueryId is passed from .11u to .21
AP is MIH aware and understands transport aspects. But AP does
NOT understand MIH payloads.
Client and PoA Certification.
STA/AP needs to indicate State 1 to IS server.
9
ESSID Query

Multiple SSIDs on a single beacon
10