Network Working Group K. Taniuchi Internet-Draft Y. Ohba Expires: April 13, 2008 Toshiba D. Subir Telcordia October 11, 2007 IEEE 802.21 Basic Schema draft-ohba-802dot21-basic-schema-01 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on April 13, 2008. Copyright Notice Copyright (C) The IETF Trust (2007). Abstract This document describes the basic schema for IEEE 802.21 Media- Independent Information Service, an RDF (Resource Description Framework) schema defined in IEEE 802.21. This document serves as the Specification required by the IANA to maintain a global registry for storing the RDF schema. Taniuchi, et al. Expires April 13, 2008 [Page 1] Internet-Draft IEEE 802.21 Basic Schema October 2007 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. RDF Schema for IEEE 802.21 Basic Schema . . . . . . . . . . . 4 3. Security Considerations . . . . . . . . . . . . . . . . . . . 19 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 20 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 6.1. Normative References . . . . . . . . . . . . . . . . . . . 20 6.2. Informative References . . . . . . . . . . . . . . . . . . 21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21 Intellectual Property and Copyright Statements . . . . . . . . . . 22 Taniuchi, et al. Expires April 13, 2008 [Page 2] Internet-Draft IEEE 802.21 Basic Schema October 2007 1. Introduction IEEE 802.21 is a standard that specifies 802 media access-independent mechanisms that optimize handovers between heterogeneous 802 systems and between 802 systems and cellular systems [802.21]. IEEE 802.21 provides a set of handover-enabling functions within the protocol stacks of the network elements and a new entity created therein called the Media-Independent Handover Function (MIHF). A media independent Service Access Point (called the MIH_SAP) and associated primitives are defined to provide MIHF users with access to the services of the MIHF. The MIHF provides the following services. 1) The Media Independent Event Service (MIES) detects events and delivers triggers from both local as well as remote interfaces. 2) The Media Independent Command Service (MICS) provides a set of commands for the MIHF users to control handover relevant link states. 3) The Media Independent Information Service (MIIS) provides the network elements with the information about neighboring networks, thus enabling making of more effective handover decisions across heterogeneous networks. The first two services are out of the scope of this document. The MIIS defines information models and query mechanisms where a query mechanism depends on the information model which it is based on. There are two types of information models in the MIIS for representing the same set of pre-defined pieces of information in different ways. One information model is based on identifying each piece of information by a unique integer value. The other information model is based on RDF (Resource Description Framework) [RDF] in which each piece of information is identified by a URI (Uniform Resource Identifiers) [RFC3986]. The two information models have different characteristics in terms of namespace management as well as query capability. This document is intended for the latter type of information model. In RDF, an information model is described in the form of RDF schema [RDFS]. To provide extensibility in terms of defining new pieces of information in addition to the pre-defined ones, the RDF schema definition for MIIS consists of two parts; the basic and the extended schema. An MIHF is pre-provisioned with the basic schema for querying information defined in the 802.21 specification. The basic schema requires a persistent URL for its definition. An extended schema is used for querying vendor-specific information and it does not require a persistent URL for its definition. This document describes the IEEE 802.21 basic schema, or an RDF schema used for IEEE 802.21 MIIS. This document serves as the Specification required by the IANA to maintain a global registry for Taniuchi, et al. Expires April 13, 2008 [Page 3] Internet-Draft IEEE 802.21 Basic Schema October 2007 storing the RDF schema [RFC3688]. The basic schema definition is described in Section 2. Information required by IANA for assigning a global registry for the basic schema is described in Section 4. 2. RDF Schema for IEEE 802.21 Basic Schema ]> Basic Schema for IEEE 802.21 Information Service 1.0 A type identifier values for Information Elements. 10000300 1 Taniuchi, et al. Expires April 13, 2008 [Page 4] Internet-Draft IEEE 802.21 Basic Schema October 2007 10000301 This class contains General Information depicting and Access Network Specific Information. 1 1 1 0x10000000 1 Taniuchi, et al. Expires April 13, 2008 [Page 5] Internet-Draft IEEE 802.21 Basic Schema October 2007 Link type of a network. The following values are assigned: 1: Wireless - GSM 2: Wireless - GPRS 3: Wireless - EDGE 15: Ethernet 18: Wireless - Other 19: Wireless - IEEE 802.11 22: Wireless - CDMA2000 23: Wireless - UMTS 24: Wireless - cdma-2000-HRPD 27: Wireless - IEEE 802.16 28: Wireless - IEEE 802.20 29: Wireless - IEEE 802.22 The range of #bit_number is 0-63. 0x10000001 1 Taniuchi, et al. Expires April 13, 2008 [Page 6] Internet-Draft IEEE 802.21 Basic Schema October 2007 1 A value of Operator Type: 0: GSM/UMTS 1: CDMA 2: REALM 3: ITU-T/TSB The value is a non NULL terminated string whose length shall not exceed 253 octets. 0x10000002 A non-NULL terminated string whose length shall not exceed 253 octets. 0x10000100 A non-NULL terminated string whose length shall not exceed 253 octets. Taniuchi, et al. Expires April 13, 2008 [Page 7] Internet-Draft IEEE 802.21 Basic Schema October 2007 0x10000101 It is SSID if network type is IEEE 802.11. 0x10000102 0x10000103 1 1 1 Taniuchi, et al. Expires April 13, 2008 [Page 8] Internet-Draft IEEE 802.21 Basic Schema October 2007 The unit of the cost: 0: second 1: minute 2: hours 3: day 4: week 5: month 6: year 7: free 8: flat rate 9-255: Reserved The cost value in Currency/Unit A three-letter currency code(e.g. "USD") specified by ISO 4217. This property represents a bit number that has the value as true. 0x10000105 Taniuchi, et al. Expires April 13, 2008 [Page 9] Internet-Draft IEEE 802.21 Basic Schema October 2007 0x10000106 1 1 A type to represent a class of service identifier. Taniuchi, et al. Expires April 13, 2008 [Page 10] Internet-Draft IEEE 802.21 Basic Schema October 2007 0x10000107 0x10000108 The range of #bit_number is 0-31. 0x10000109 Taniuchi, et al. Expires April 13, 2008 [Page 11] Internet-Draft IEEE 802.21 Basic Schema October 2007 The range of #bit_number is 0-31. 0x1000010A 0x10000302 1 1 1 1 Taniuchi, et al. Expires April 13, 2008 [Page 12] Internet-Draft IEEE 802.21 Basic Schema October 2007 1 This class contains all the information depicting a PoA. 0x10000302 0x10000201 This class has properties that represent geographic coordinate. The format is based on the Location Configuration Information (LCI) defined in RFC 3825. Taniuchi, et al. Expires April 13, 2008 [Page 13] Internet-Draft IEEE 802.21 Basic Schema October 2007 Following codes are defined: 1: Meters: in 2s-complement fixed-point 22-bit integer part with 8-bit fraction. If AT = 1, an AltRes value 0.0 would indicate unknown altitude. The most precise Altitude would have an AltRes value of 30. Many values of AltRes would obscure any variation due to vertical datum differences. 2: Floors: in 2s-complement fixed-point 22-bit integer part with 8-bit fraction. AT = 2 for Floors enables representing altitude in a form more relevant in buildings which have different floor-to-floor dimensions. Altitude resolution. 6 bits indicating the number of valid bits in the altitude. Values above 30 (decimal) are undefined and reserved. Following codes are defined: 1: WGS Taniuchi, et al. Expires April 13, 2008 [Page 14] Internet-Draft IEEE 802.21 Basic Schema October 2007 2: NAD 83 (with associated vertical datum for North American vertical datum for 1998) 3: NAD 83 (with associated vertical datum for Mean Lower Low Water (MLLW)) Way location information was derived or discovered: 0: GPS 1: Assisted GPS 2: Manual 3: Provided by DHCP 4: Triangulation 5-255: Reserved Geo address elements as described in RFC4119. This class has properties that represent civic address. The format is defined in IETF RFC 4676. Two-letter ISO 3166 country code in capital ASCII letters. Taniuchi, et al. Expires April 13, 2008 [Page 15] Internet-Draft IEEE 802.21 Basic Schema October 2007 This property contains the civic address elements. The format of the civic address elements is described in Section 3.4 of IETF RFC 4676 with a TLV pair (whereby the Type and Length fields are one octet long). 1 1 A one-octet descriptor of the data civic address value. The civic address value. Taniuchi, et al. Expires April 13, 2008 [Page 16] Internet-Draft IEEE 802.21 Basic Schema October 2007 Geo address elements as described in RFC4119. 0x10000202 1 1 Lowest channel frequency in MHz Highest channel frequency in MHz Taniuchi, et al. Expires April 13, 2008 [Page 17] Internet-Draft IEEE 802.21 Basic Schema October 2007 0x10000203 0x10000204 1 1 The bit length of the prefix of the subnet to which subnet_address property belongs. The prefix_length is less than or equal to 32 for IPv4 subnet and less than or equal to 128 for IPv6 subnet. Taniuchi, et al. Expires April 13, 2008 [Page 18] Internet-Draft IEEE 802.21 Basic Schema October 2007 0x10000205 1 1 An Address Family defined in http://www.iana.org/assignments/address-family-numbers. An address value specific to address_type. 3. Security Considerations Beyond the considerations described in [RFC3688], there are no additional security considerations other than that was already found with any other IANA registry. Taniuchi, et al. Expires April 13, 2008 [Page 19] Internet-Draft IEEE 802.21 Basic Schema October 2007 4. IANA Considerations The IEEE 802.21 basic schema requires an IANA-assigned registry for an RDF schema. According to [RFC3688], the following is the information needed by IANA. URI (please assign) The URI that identifies the IEEE 802.21 basic schema. Registrant Contact Yoshihiro Ohba Toshiba America Research, Inc. 1 Telcordia Drive Piscataway, NJ 08854 USA Phone: +1 732 699 5365 Email: yohba@tari.toshiba.com XML The exact XML to be stored in the registry is described in Section 2, except that the word "URL_TO_BE_ASSIGNED" in the XML definition needs to be replaced with IANA-assigned URL for the stored XML. 5. Acknowledgments TBD. 6. References 6.1. Normative References [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. [RDF] W3C Recommendation, "Resource Description Framework (RDF) - Concepts and Abstract Syntax (http://www.w3.org/TR/rdf-concepts/)", February 2004. [RDFS] W3C Recommendation, "RDF Vocabulary Description Language 1.0: RDF Schema (http://www.w3.org/TR/rdf-schema/)", February 2004. Taniuchi, et al. Expires April 13, 2008 [Page 20] Internet-Draft IEEE 802.21 Basic Schema October 2007 6.2. Informative References [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005. [802.21] Institute of Electrical and Electronics Engineers, "Draft IEEE Standard for Local and Metropolitan Area Networks: Media Independent Handover Services", IEEE Standard 802.21/D07-01, 2007. Authors' Addresses Kenichi Taniuchi Corporate R&D Center, Toshiba Corporation 1, Komukai-Toshiba-cho, Saiwai-ku Kawasaki, Kanagawa 212-8582 Japan Phone: +81 44 549 2230 Email: kenichi.taniuchi@toshiba.co.jp Yoshihiro Ohba Toshiba America Research, Inc. 1 Telcordia Drive Piscataway, NJ 08854 USA Phone: +1 732 699 5365 Email: yohba@tari.toshiba.com Subir Das Telcordia 1 Telcordia Drive Piscataway, NJ 08854 USA Phone: +1 732 699 2483 Email: subir@research.telcordia.com Taniuchi, et al. Expires April 13, 2008 [Page 21] Internet-Draft IEEE 802.21 Basic Schema October 2007 Full Copyright Statement Copyright (C) The IETF Trust (2007). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Taniuchi, et al. Expires April 13, 2008 [Page 22]