21-05-0346-00-0000 IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN:21-05-0346-00-0000 Title: Comments on Information Service Sections Submitted: September,

21-05-0346-00-0000

• IEEE 802.21 MEDIA INDEPENDENT HANDOVER

• DCN:21-05-0346-00-0000

• Title: Comments on Information Service Sections

• Submitted: September, 20, 2005

• Presented at IEEE 802.21 session 10 in Garden Grove

• Authors or Source(s):

• Yoshihrio Ohba, Subir Das and Farooq Bari

• Abstract: This document contains summary of comments on IS sections

21-05-0346-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-0346-00-0000

Comment 117 (Reason)

• Section 6.3.2, Page 41, Lines 20-44• General Network Information (GNI) and Higher Layer

Information (HLI) should be merged into "Media-Independent Information (MII)". Link Layer Information (LLI) should be renamed to "Media-dependent Information (MDI)".

• Tables 4, 5 and 6 should be reduced into two tables of MDI and MII, and revised with more detailed description.

• Definition of basic set and extended set needs to be clearly described in this section.

21-05-0346-00-0000

Comment 117 (Change) • Replace text between lines 20 and 44 of page 41 with the following:

"The information elements provided by the Information Service can be classified into two categories:

1) Media-Independent Information (MII): These information elements describe the media-independent properties of the network. MII includes of Point of Attachment, Neighboring Networks, Neighboring PoAs, Location of PoA, Network Operator, Roaming Partners, Cost, Higher Layer Security Support, and Higher Layer QoS Support .

2) Media-Dependent Information (MDI): These information elements describe the information related to link and physical layers. MDI includes of Data Rate, MAC Type, PHY Type, Link Layer Security, and Link Layer QoS .

Each information element in MII and MDI belongs to one of the following two sets, e.g, , the basic set and the extended set. Information elements in the basic set must be supported by all MIH entities. Support for information elements in the extended set is optional.

Tables 4 and 5 describe a set of information elements in both categories that include the basic and extended set. When new information elements are added to MII or MDI, they need to be most likely defined in the extended set.

Information elements may be obtained via a PoA before the STA authenticates to the PoA irrespective of whether they belong to the basic or extended set. While all of the above information elements are necessary and will be available via 802.21 information service framework, it is important to note that MDI will be mostly directly available via media specific technologies. In cases where media specific amendments are not available or possible, information elements in MDI can be carried over via higher layer transport. "

21-05-0346-00-0000

Comment 118 (Reason)• Section 6.3.2, page 41, Table 4:

• Media Types column is not meaningful. The Media Types column should be replaced with another column that indicates whether a given information element belongs to basic set or extended set.

• "List of networks available" should be renamed to a less confusing name.

• "Network standards supported" is ambiguous and should be removed.

• "Network identifier" is similar to "Operator" and should be removed.

• "Operator" needs to have not only a name but also a unique identifier.• "IP Version" is not useful information and should be removed from MII.• "SLAList" information is ambiguous and should be removed.

• "neighbor information" contain only static and limited information such as a list of neighboring PoAs. Also it should be replaced to more specific name like "neighboring PoAs".

• "AccessRouterInfo" is too detailed to be defined in the basic set.• More detailed description and comments are needed for each

information elements.

21-05-0346-00-0000

Comment 118 (Change)

• Replace Table 4 with the one described in Section 2.1 of 21-05-0346-0000_Supplement_D00-02_Ohba_Yoshihiro.doc.

21-05-0346-00-0000

Comment 119 (Reason)

• Section 6.3.2, page 42, Table 5:• Media Types column is not meaningful. The Media Types

column should be replaced with another column that indicates whether a given information element belongs to basic set or extended set.

• "Neighbor information" can contain MII and MDI, and can be obtained by querying the basic set and extended set of each PoA in the "neighboring PoAs" information element in MII. Thus, this is redundant and should be removed from MDI.

• "AccessRouterInfo" is not MDI and should be removed.• More detailed description and comments are needed for each

information elements.

21-05-0346-00-0000

Comment 119 (Change)

• Replace Table 5 with the one described in Section 2.2 of 21-05-0346-0000_Supplement_D00-02_Ohba_Yoshihiro.doc.

21-05-0346-00-0000

Comment 120 (Reason/Change)

• Section 6.3.2, page 43, Table 6

• Reason: Since GNI and HLI are merged into MII, this table for HLI is not needed anymore.

• Change: Remove Table 6.

21-05-0346-00-0000

Comment 121 (Reason)

• Section 6.3.2, page 43, line 42:

• The text can be described without referring Table 7 (which is refereed incorrectly to as Table 8.3) and Figure 22.

• The text should be revised that information elements in both the basic set and extended set can be obtained either from media-specific broadcast information or by sending a specific request/response primitive.

21-05-0346-00-0000

Comment 121 (Change)

• Replace the text with:

"MIHF entity (e.g., a STA or network entity) can extract the information elements in the basic set and the extended set either from media specific broadcast information or by sending a specific request/response primitive. On the other hand, before sending a request/response, the MIHF entity should have the knowledge that the network supports the 802.21 MIH standard (e.g., via a management frame that carries capability information). For example, MIHF entity in STA may request the MIHF entity of PoA for such information. It is important to note that before a STA is authenticated to the PoA and ready to exchange data, it should be able to obtain all the information elements listed in Tables 4, 5 and 6. These information elements may then be used by the STA's handover function to determine the right PoA to attach. "

21-05-0346-00-0000

Comment 122: (Reason/Change)

• Section 6.3.2, page 44, Figure 22

• Reason: Figure 22 is not useful.

• Change: Remove Figure 22

21-05-0346-00-0000

Comment 123 (Reason/Change)

• Section 6.3.2, page 45, Table 7:

• Reason: Table 7 is just informative and should not be included in this section.

• Change: • Remove Table 7• Remove text starting from line 39 of page 45 and ending at

line 23 of page 46.

21-05-0346-00-0000

Comment 124: (Reason)

• Section 6.3.3.1, page 46, line 58:

• (Presuming that Comment xx is accepted) Since the basic schema uses OWL in addition to RDF Schema, a brief description about OWL needs to be added.

21-05-0346-00-0000

Comment 124: (Change)

• Insert the following text at line 58 of page 46:

"In order to strictly define each information element in an RDF schema, the schema is augmented with Web Ontology language (OWL) [OWL]. OWL is a Web Ontology language. OWL uses both URIs for naming and the description framework provided by RDF to add the following capabilities to ontologies: - Ability to be distributed across many systems - Scalability- Compatibility with other Web standards for accessibility and internationalization - Openness and extensibility

OWL builds on RDF and RDF Schema and adds more vocabulary for describing properties and classes: among others, relations between classes (e.g. disjoint-ness), carnality (e.g. "exactly one"), equality, richer typing of properties and characteristics of properties (e.g. symmetry), and enumerated classes. "

21-05-0346-00-0000

Comment 125: (Reason)

• Section 6.3.3.1, page 47, lines 1-18:

• Some description is needed as to how extended schema can be created.

• Use of DNS query for finding the FQDN part of the location of the extended schema is not useful because it does not tell the entire URL of the extended schema. Instead, use of DHCP might be better to tell the URL of the extended schema.

• Since Figure 23 needs to be revised, the corresponding explanatory text in section 6.3.3.1 should be revised as well.

21-05-0346-00-0000

Comment 125: (Change)• Replace the two paragraphs starting at line 1 of page 47 with:

"As described earlier, the RDF schema definition for MIIS consists of two parts; the basic and the extended schema. The basic schema is not supposed to be updated. An MIH entity is typically pre-provisioned with the basic schema for ease of implementation of schema-based query. In scenarios where the basic schema is not pre-provisioned methods such as DHCP may be used to access the URL of the basic schema.

Unlike the basic schema, the extended schema is expected to be updated periodically, e.g., when a new link layer technology is introduced. The extended schema can be retrieved from the specified URL via the IEEE 802.21 information service using the schema query capability described in Section 8.5.3 without any reprovision of such extended schema. The URL of the extended schema can also be obtained via the schema URL query capability described in section 8.5.3. Alternatively DHCP may be used for finding out the URL of extended schema. The extended schema is defined as an extension of the basic schema and includes data structure and relationship of media-specific or higher-layer information. In that sense extended schema is the complement of basic schema. An extended schema may be automatically generated from various of media-specific or higher-layer MIB definitions such as 802.11 MIB, 802.16 MIB and TCP/IP MIB-II.

Figure 8-3 below shows an example graphical representation of the 802.21 MIIS basic schema in which 'Network' 'MII', 'MDI', 'PoA', 'NAS-Port-Type', 'Location', 'Operator', 'Cost' , 'Geo-Coordinate' and 'Enterprise-Number' are represented as class, while all others are properties of classes. The lines indicate either the range or domain of a property or a sub class of a class. In particular 'r' represents the range of a property and 'd' represents domain of a property. 'Domain' defines the class that a particular property belongs to and 'range' defines a type of a particular property."

21-05-0346-00-0000

Comment 126: (Reason/Change)

• Section 6.3.3.1, page 47:

• Reason: Figure 23 should be updated to be consistent with the revised basic set.

• Change: Replace Figure 23 with the one described in Section 2.4 of 21-05-0346-0000_Supplement_D00-02_Ohba_Yoshihiro.doc.

21-05-0346-00-0000

Comment 127: (Reason/Change)

• Section 7.4.14.3.1, page 89, lines 27:

• The schema-based query example should be updated to be consistent with the revised basic schema.

• Replace text starting at line 27 of page 89 and ending at line 42 of page 90 with the text provided in D00-02_MasterFile

21-05-0346-00-0000

Comment 128: (Reason/Change)

• Annex C.1, page 116:

• Reason: The basic schema definition should be updated.

• Change: Replace text starting at line 10 of page 116 and ending at line 44 of page 112 with the text provided in D00-02_MasterFile

21-05-0346-00-0000

Comment 129: (Reason/Change)

• Annex C.2, page 122:

• Reason: The Basic Schema Representation in ASN.1 is not useful unless a schema-based query is defined for it.

• Change: Remove Annex C.2 entirely.

21-05-0346-00-0000

Comment 130: (Reason/Change)

• Annex C.3, page 123:

• Reason: The extended schema representation in RDF/XML can be automatically generated from various lower-layer and higher-layer MIB definitions, and does not need to be described in this document

• Change: Remove Annex C.3 entirely.

21-05-0346-00-0000

Comment 131: (Reason/Change)

• Annex C.4, page 132:

• Reason: The ASN.1 representation of extended schema is not needed as it is not tied with a schema-based query language and should be removed.

• Change: Remove Annex C.4 entirely.

21-05-0346-00-0000

Comment 132: (Reason/Change)

• Section 7.4.14.1.2, page 87:

• Reason: All QueryFilterTypes and its usage defined in this section are not well-defined. Since we have another set of QueryFilterTypes for schema-based query in 7.4.14.3, why do we need all these QueryFilterTypes for schema-less query?

• Change:• Remove text starting at line 20 of page 87 and ending at line

6 of page 88.• Move the contents of Sections 7.4.14.3, 7.4.14.3.1,

7.4.14.3.2, 7.4.14.3.3 to Section 7.4.14.1.2.