Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-06-0731-00-0000 Title: LB Issue-# 5 and 6 : Comment 352, 360, 378, 380, 403 Date Submitted: September.

Similar presentations


Presentation on theme: "1 IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-06-0731-00-0000 Title: LB Issue-# 5 and 6 : Comment 352, 360, 378, 380, 403 Date Submitted: September."— Presentation transcript:

1 1 IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: LB Issue-# 5 and 6 : Comment 352, 360, 378, 380, 403 Date Submitted: September 2006 Presented at IEEE session in Melbourne, Australia Authors or Source(s): Srinivas, Sreemanthula, Vivek Gupta Abstract: This contribution addresses issues related to Information Elements.

2 2 IEEE presentation release statements This document has been prepared to assist the IEEE 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 The contributor is familiar with IEEE patent policy, as outlined in Section 6.3 of the IEEE-SA Standards Board Operations Manual and in Understanding Patent Issues During IEEE Standards Development Section 6.3 of the IEEE-SA Standards Board Operations Manualhttp://standards.ieee.org/guides/opman/sect6.html#6.3

3 3 Overview  Related Comments for LB Issues 5 and 6: 352 (Accepted) 360 (Deferred) 378 (Accepted) 380 (Deferred) 403 (Superceded by 378, 380) 361 (Rejected) 406 (Superceded by 361)

4 4 Comments  #360: There is no specification for the representation of the LIST_OF_OPERATORS  #380: In Table-6, 3.4, 3.5 and 4.1 do not state what representation should be used  #403: Specific format for the value portion in each type of information element is vague or not defined. For example the Link Type Values for is not defined although the length for each Value field is defined. Same for Cost in and elsewhere in the draft.  #406: Relationship between table 6 and section is unclear and confusing. e.g. for TYPE_IE_NUMBER_OF_OPERATORS it looks as though there are contradictory lengths specified. Also, the representation and encoding information seems to be distributed across multiple sections of the document.

5 5 Discussion-1  More information is required for networks operating in unlicensed bands such as and relatively less information is required for networks operating in licensed bands such as GSM/UMTS/WiMax  PoA information is more useful for ? Do we really need it for other access networks?

6 6 Discussion-2  TYPE_IE_LIST_OF_NETWORKS Use NAS-port type values. One being defined for Spec does NOT define any values of it ’ s own. Should it just reference IETF draft or duplicate values here … Should Table-7 be in the draft (D01.09)?  Use reference …… comment 348:  TYPE_IE_ROAMING_PARTNERS Current definition is good Which roaming partner (operator) is specified here?  Access Network Service Provider or  Core Network Service Provider –Use just one … (Core Network Service Provider)

7 7 Discussion-3  TYPE_IE_NETWORK_STANDARDS Should we define a new IE such as this. Can this be a bitmap … or a string : can cover support for various TGs(.11a/b/e/g/i/k/n … ) Cellular: Use 3GPP Release version WiMax: Can cover support for various TGs (.16d/e/f/g/h/k ….)

8 8 Discussion-4  TYPE_IE_NETWORK_SECURITY How to define this? : Use Authentication Methods and Cipher Suites.  Or just indicate No security, i enabled/not enabled Cellular/WiMax: Do we care?..It’s implicitly understood what security is available for these networks and variation in security is minimal/non-existant to cause a concern. Cipher_Suites ::= BITMAP {None, WEP,TKIP, AES-CCMP} Authenticated_Key_Management_Suites ::= BITMAP {None, WEP, Psk, 802.1X }  TYPE_IE_QOS How to define this? : Just indicate e supported or not? Do we need anything more? Cellular/WiMax: Do we care? Get dynamic QoS after connecting to these links. This is dynamic info and cannot be statically represented Should we use media-independent parameters like delay, jitter etc. as specified in QoS contribution by Nada/Ulises et al? These parameters may have dynamic values  Throughput, Link Packet Error Rate,  Minimum/Maximum Packet Transfer Delay, Average Packet Transfer Delay  Packet Transfer Delay Jitter

9 9 Discussion-5  TYPE_IE_POA_PHY_TYPE, TYPE_IE_POA_MAC_TYPE Why do we care about PHY/MAC type supported at PoA? : Is ’ nt it good enough to know if a/b/g/n is supported or not? Cellular/WiMax: Do we care? Just DELETE these IEs?  TYPE_IE_NETWORK_IDENTIFIER Add ESSID for Add a new IE for at one level higher …

10 10 Discussion-6  TYPE_IE_POA_CAPABILITIES (looks ok) Bitmap of supported capabilities Y/N Details of capability given in access network section Supported capabilities  Security –Specifies that security related access network standards are supported for this PoA  QoS –Specifies that QoS related access network standards are supported for this PoA  Internet Access  Emergency Services  MIH Capability  IP Version 6 prefix

11 11 Proposal  Accept the remedies as specified in LB- issues-5-6.doc

12 12 Backup

13 13 Issues from AdHoc-Contribution-Status  Change to structure of table w.r.t having references in Representation column seems acceptable.  Investigate using existing Networks IDs defined elsewhere (IANA).  Investigate having a Network Subtype IE which can include all the network standard amendments. For example for , this would include (.a,.b,.e,.g,.i,.k,.n and so on). Doing it this way may allow us to delete certain other IEs such as IE_POA_MAC_TYPE, IE_POA_PHY_TYPE, etc.  Roaming partners (which operator is specified here?).  For security specify cipher suites and authentication methods.  QoS: Investigate using media independent parameters such as delay, jitter etc. defined in (Ulises et al) QoS contribution.  Cost: Investigate QoS based cost??


Download ppt "1 IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-06-0731-00-0000 Title: LB Issue-# 5 and 6 : Comment 352, 360, 378, 380, 403 Date Submitted: September."

Similar presentations


Ads by Google