Word for Windows
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Word for Windows

on

  • 461 views

 

Statistics

Views

Total Views
461
Views on SlideShare
461
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft Word

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Word for Windows Presentation Transcript

  • 1. INTERNATIONAL TELECOMMUNICATION UNION JCA-NID TELECOMMUNICATION Document D-002 Rev3 STANDARDIZATION SECTOR English only STUDY PERIOD 2005-2008 Joint Coordination Activity on Network Aspects of Identification Issued: 02 February 2010 Systems (including RFID) Source: Convenor of JCA-NID Title: JCA-NID Standards Roadmap Purpose: Deliverable Revision: Revision 3: 02/02/2010 This document represents the Revision 3 of Deliverable 2 (JCA-NID Standards Roadmap), which contains a collection of Standards/ITU-T Recommendations that fit into JCA-NID scope. It includes Standards/ITU-T Recommendations related to network aspects of identification systems, including RFID (NID) and ubiquitous sensor networks (USN). The JCA-NID participants are invited to review the current version and provide missing/updated information to JCA-NID secretariat (tsbjcanid@itu.int). Mr Stefano Polidori Tel.: +41 22 730 5858 Contact: ITU/TSB Fax: +41 22 730 5853 Email: stefano.polidori@itu.int Email: tsbjcanid@itu.int
  • 2. -2- NID Areasi Entityii Scopeiii of the deliverable Existing Deliverablesiv (ap- Deliverables under devel- proved) opment/expected date of approval The purpose of this Recommendation is to define basic SG 2 terms in the area of identifiers covering names, numbers, ITU-T E.101 (former Q1 addresses and other identifiers in ITU-T E-series Recom- E.IDs-DEF) TAP started at mendations. April 2009 SG2 meeting “Definitions of terms used for identifiers (names, numbers, ad- dresses and other identi- fiers) for public telecom- munication services and networks in the E-series Recommendations” Expected for approval: 11-2009 Recommendation ITU-T Y.2213 describes high-level ser- SG 13 ITU-T Y.2213 (former Y.Id- vice requirements and NGN capability requirements need- Q2 serv-reqts) approved on ed to support applications and services using tag-based September 2008 identification. Several examples of applications and ser- vices using tag-based identification are also described with “NGN service require- scenarios. The scope of this Recommendation is limited to ments and capabilities for applications and services using tag-based identification and network aspects of applic- they are distinguished by the following three mandatory el- ations and services using ements: ID tag, ID terminal and identifier tag-based identification” SG 13 This Recommendation provides a description and general ITU-T Y.2221 (Y.USN- Q3 characteristics of Ubiquitous Sensor Network (USN) and reqts) “Requirements for USN applications and services. It also analyzes service re- support of Ubiquitous quirements of USN applications and services, and specifies Sensor Network (USN) ap- extended or new NGN capability requirements based on plications and services in the service requirements. NGN environment” (Consented on
  • 3. -3- NID Areas Entity Scope of the deliverable Existing Deliverables (ap- Deliverables under devel- proved) opment/expected date of approval 12-09-2009, expected date of approval October 2009) SG 13 This Recommendation includes functional requirements ITU-T Y.2016 (former Y.Id- Q5 and architecture of the NGN for the support of applications serv-arch) approved on Au- and services using tag-based identification. This Recom- gust 2009 mendation is based on the capabilities defined in ITU-T “Functional requirements Recommendation Y.2213. and architecture of the NGN for applications and services using tag-based identification” SG 16 Recommendation ITU-T H.621 defines the system archi- ITU-T H.621 (former Q22 tecture for the multimedia information access triggered by H.MID) approved on August tag-based identification on the basis of Recommendation 2008 ITU-T F.771, and serves as a technical introduction to sub- “Architecture of a system sequent definition of detailed system components and pro- for multimedia informa- tocols. The services treated by this Recommendation tion access triggered by provide the users with a new method to refer to the multi- tag-based identification” media content without typing its address on a keyboard or inputting the name of objects about which relevant inform- ation is to be retrieved. This is one of the major communic- ation services using identification (ID) tags such as radio frequency identifications (RFIDs), smart cards and bar- codes. International standardization of these services will give a big impact to international multimedia information services using ID tags. It contains the functional model, its constituent components as well as its workflow. An ap- pendix describes how this architecture realizes typical ser- vices. SG 16 Recommendation ITU-T F.771 specifies a high-level func- ITU-T F.771 (former
  • 4. -4- NID Areas Entity Scope of the deliverable Existing Deliverables (ap- Deliverables under devel- proved) opment/expected date of approval Q22 tional model, a service description and requirements for F.MID) approved on August multimedia information access triggered by tag-based iden- 2008 tification. The scope of this Recommendation is limited to “Service description and those applications and services that have both multimedia requirements for multime- and tag-based characteristics. dia information access triggered by tag-based identification” SG 16 This Recommendation defines ID schemes for the multi- H.IDscheme Q 22 media information access triggered by tag-based identifica- “ID schemes for multi- tion media information access triggered by tag-based identification” Expected date of approval 2010 SG 16 This Recommendation defines the ID resolution protocols H.IRP Q 22 for multimedia information access triggered by tag-based “ID resolution protocols identification for multimedia informa- tion access triggered by tag-based identification” Expected date of approval 2010 SG 16 The objective of this draft Recommendation is to describe F.usn-mw Q 25 USN services and to define requirements for USN middle- “Service description and ware to support various types of USN services. This draft requirements for USN Recommendation describes USN services and their com- middleware” mon activities in order to explain the necessities of USN middleware and to extract requirements for USN middle- Expected date of approval ware. December 2009
  • 5. -5- NID Areas Entity Scope of the deliverable Existing Deliverables (ap- Deliverables under devel- proved) opment/expected date of approval SG 16 This Recommendation describes sensor network manage- H.snmf Q 25 ment framework (SNMP) intended to provide integrated “SNMP-based sensor management functionalities for heterogeneous sensor net- network management works using Simple Network Management Protocol. framework” The scope of this Recommendation includes: Expected date of approval • Overall architecture of framework 2011 • Functional entities of framework • Guidelines for object identifier allocation for MIB • Guidelines for object identifier translation between SNMP and sensor network management protocols • Sensor network information retrieval procedure SG 17 ITU-T X.660 | ISO/IEC ITU-T Recommendation X.660 | ISO/IEC 9834-1 defines a Q10 9834-1 generic registration-hierarchical-name-tree (RH-name-tree) (approved on August 2008) and a specific form of this RH-name-tree that supports in- ternational object identifiers (OIDs). It includes registration “Information technology - of the top-level arcs of the OID tree. It also specifies proce- Open Systems Intercon- dures for the operation of an International Registration Au- nection - Procedures for thority for use, when needed, by other Recommendations the operation of OSI Re- and/or International Standards. gistration Authorities: For easy reference, and to emphasize that this tree is an ex- General procedures and tended form of the original OID tree (defined in earlier ver- top arcs of the ASN.1 Ob- sions of this Recommendation | International Standard), ject Identifier tree” this specific RH-name-tree can be referred to as "the inter- national OID tree", or more commonly as just "the OID tree". The OID tree (defined as the International Object Identifier Tree) specified in this edition is a superset of the original
  • 6. -6- NID Areas Entity Scope of the deliverable Existing Deliverables (ap- Deliverables under devel- proved) opment/expected date of approval OID tree, which did not support Unicode labels (names of arcs in any language, using the Unicode character set). The original OID tree required all arcs to be unambiguous- ly identified by a primary integer value, with the use for human readability of (not necessarily unambiguous) sec- ondary identifiers (restricted to the Latin alphabet). Sec- ondary identifiers were not normally carried in protocols or used for machine identification. The International Object Identifier tree extends this by allowing an arc to also be un- ambiguously identified by a Unicode label (a string of Uni- code characters) that can be carried in protocols and can be used for machine identification. The primary integers and secondary identifiers of the Inter- national Object Identifier tree continue to be used in encod- ing (primary integers only) and value notation (primary in- tegers and secondary identifiers) of the ASN.1 OBJECT IDENTIFIER type, which is unchanged. The Unicode labels can only be used in encodings and value notation of the ASN.1 OID-IRI type, and in the specification of an IRI or URI (see IETF RFC 3987). It also provides recommendations on an appropriate fee structure for registration of lower level arcs (see clause 11). SG 17 Procedures for the operation of OSI Registration Authorit- X.668 Q12 ies: Registration of object identifier arcs for ID-based ap- and ITU- T X.RA-nid | plications. JTC1 ISO/IEC 9834-x It specifies the information to be provided when registering SC6/WG9 (Planned for Consent in a new Object Identifier (OID) for coding schemes for ID- based applications and services, and the procedures for the April 2008 / discontinued) operation of the Registration Authority
  • 7. -7- NID Areas Entity Scope of the deliverable Existing Deliverables (ap- Deliverables under devel- proved) opment/expected date of approval This Recommendation recognizes that as RFID greatly fa- ITU-T X.1275 (former cilitates the access and dispersion of information pertaining X.rfpg); specifically to the merchandise that individuals wear and/or “Guideline on protection carry; it creates an opportunity for the same information to of personally identifiable be abused for tracking an individual's location or invading information in the ap- their privacy in a malfeasant manner. For this reason the plication of RFID techno- Recommendation develops guidelines and best practices logy” regarding RFID procedures that can be used by service providers to gain the benefits of RFID while attempting to (expected date of approval protect the privacy rights of the general public within na- 2010) tional policies. SG 17 The widespread deployment of identification tags, includ- ITU-T X.1171 (former X.n- Q9 ing radio frequency identification (RFID) tags can give rise idsec-1) approved on Febru- to concerns of privacy infringement because of the abilities ary 2009 of RFID technology to automatically collect (and process) “Threats and require- data, with the possible disclosure of such data to the public ments for protection of (deliberately or accidentally). personally identifiable in- For applications using tag-based identification and relying formation in applications on a personalized identification tag in personalized after- using tag-based identifica- sale management applications, healthcare-related applica- tion” tions, etc., the privacy issue is becoming an increasingly serious problem. This Recommendation describes a num- ber of personally identifiable information (PII) infringe- ments for applications using tag-based identification, and requirements for PII protection. In addition, this Recom- mendation provides a basic structure of PII protection based on PII policy profile.
  • 8. -8- NID Areas Entity Scope of the deliverable Existing Deliverables (ap- Deliverables under devel- proved) opment/expected date of approval SG 17 This Recommendation describes security threats and secur- ITU-T X.usnsec-1 | Q6 ity requirements to the Ubiquitous Sensor Network. In ad- ISO/IEC 29180 common text dition, this Recommendation categorizes security technolo- “Information technology with: gies by security functions that satisfy above security re- - Security framework for quirements and by the place to which the security technolo- ISO/IEC ubiquitous sensor net- gies are applied in the security model of the Ubiquitous JTC 1/SC 6 work” Sensor Network. Finally, the security function require- ments for each entity in the network and possible imple- (expected date of approval mentation layer for security function are presented. 2011-1Q) SG 17 This Recommendation analyzes security threats on ubiquit- ITU-T X.usnsec-2 Q6 ous sensor network (USN) middleware, defines the func- "Ubiquitous sensor net- tional requirements, and develops the guidelines for USN work (USN) middleware middleware security. security guidelines" (expected date of approval 12/2010) SG 17 This Recommendation provides secure routing mechan- ITU-T X.usnsec-3 Q6 isms for wireless sensor network in ubiquitous sensor net- "Secure routing mechan- work. It introduces general network topologies and routing isms for wireless sensor protocols in ubiquitous sensor network. It describes secur- network" ity threats of wireless sensor network and provides counter- measures for secure routing in wireless sensor network. (expected date of approval 12/2010) SG 17 X.520 defines attribute types for Directory Services. The Amd.3 to ITU-T X.520 Q2 amendment 3 to X.520 will extend it to support identifica- (this work item has to be tion management in Directory Services confirmed so the expected date of approval is not available) SG 17 This Recommendation | International Standard provides the ITU-T X.oid-res |
  • 9. -9- NID Areas Entity Scope of the deliverable Existing Deliverables (ap- Deliverables under devel- proved) opment/expected date of approval Q12 necessary text for the development of an infrastructure to ISO/IEC 29168 common text support access to information associated with nodes in the ”Object identifier resolu- International Object Identifier tree (see ITU-T X.660 | ISO/ with: tion system” IEC 9834-1) using DNS ISO/IEC Date of approval 2010 JTC 1/SC 6 ISO TC 104/ Provides a system for general application for the identifica- ISO 6346 Published standard - Stage SC 4 tion and presentation of information about freight contain- Freight container identific- 90.92 ers. Specifies a identification system with mandatory marks ation (BIC-Code) for visual interpretation and optional features for automatic identification and electronic data interchange and a coding Pub 1995 system for data on container size and type. Replaces the second edition, which has been technically revised. ISO TC 104/ Specifies all necessary user requirements. Includes: a con- ISO 10374 Published standard - Stage SC 4 tainer identification system, data coding systems, descrip- 90.92 Freight containers auto- tion of data, performance criteria and security features. matic identification Pub 1991 ISO Revision of ISO 10374:1991 ISO 10374.2 TC 104/SC 4 Freight containers – RF automatic identification CD study/ballot initiated – Stage 30.20 ISO This standard provides a permanent RFID tag attached to a ISO 10891 TC 104/SC 4 freight container for its life. This standard serves as a re- Freight containers – RF placement to ISO 10374. See ISO 17363 and 18185. automatic identification Approved for registration as a DIS.
  • 10. - 10 - NID Areas Entity Scope of the deliverable Existing Deliverables (ap- Deliverables under devel- proved) opment/expected date of approval ISO This standard provides a one-time use RFID electronic ISO 18185 All parts published in 2006 TC 104/SC 4 seal. See ISO 17363 and 10891. Its singular flaw is that it and 2007 Freight containers – Elec- specifies that RF tags must support two distinct air inter- tronic seals faces, ostensibly guaranteeing that the standard will not be adopted. –Part 1, Communication protocol, IS Published 2007-04-26 –Part 2, Environmental characteristics, IS Published 2007-04-16 –Part 3, Application re- quirements, IS Published 2006-05-22 –Part 4, Data protection, IS Published 2007-04-24 Part 5, Physical layer, IS Published 2006-05-04 ISO/IEC Mobile item identification and management ISO/IEC 2917x (TBD) JTC 1/SC 31/WG 6 ISO/IEC JTC 1/SC 31/WG 7 ISO/IEC on sensor network requirements and architectural issues ISO/IEC WD 29182 "Ref- JTC1/WGS erence architecture for N sensor network applica- tions and services"
  • 11. - 11 - NID Areas Entity Scope of the deliverable Existing Deliverables (ap- Deliverables under devel- proved) opment/expected date of approval ISO/IEC ISO/IEC 19762 is the official vocabulary of JTC 1/SC 31 ISO/IEC 19762 – Harmo- All parts published in 2008 JTC 1/SC 31 including RFID and locating systems. nized vocabulary ISO/IEC 19762 consists of the following parts, under the general title Information technology AIDC tech- niques - Harmonized vocab- ulary: - Part 1: General terms relat- ing to Automatic Identifica- tion and Data Capture (AIDC) - Part 2: Optically Readable Media (ORM) - Part 3: Radio-Frequency Identification (RFID) - Part 4: General terms relat- ing to radio communications - Part 5: Locating systems Revises ISO/IEC 19762:2005 ISO/IEC Unique identification links data associated with a physical ISO/IEC 15459 (Multiple JTC 1/SC 31 entity (item attendant data) to that entity. All parties in the parts) supply chain can use this unique identification. Each of Unique identifiers under
  • 12. - 12 - NID Areas Entity Scope of the deliverable Existing Deliverables (ap- Deliverables under devel- proved) opment/expected date of approval these parties must be able to identify and trace the item so the general title that reference can be made to the item attendant data such Information technology - as address, order number, contents of the item, weight, Unique identification - sender, batch or lot number, etc. The information is often held on computer systems, and may be exchanged between parties involved via EDI (Electronic Data Interchange) and XML (eXtensible Markup Language) messages. Each standard provides Object Identifiers (OIDs) for that particular unique identification. Most often multiple “unique identifiers” are found in a shipment, each associated with a particular aggregation, i.e., identification at the item level, product package level, transport unit level, returnable transport item level, and freight container level. ISO/IEC This standard provides unique identification at the trans- ISO/IEC 15459-1 Published standard – Stage JTC 1/SC 31 port unit level. 60.60 Part 1: Unique identifiers This standard serves as the basis for identification in ISO for transport units 15394 (for bar codes) and ISO 17365 (for RFID) Pub 2006 ISO/IEC This standard defines the registration procedures for identi- ISO/IEC 15459-2 Published standard – Stage JTC 1/SC 31 fiers at all levels of unique identification 60.60 Part 2: Unique identifica- This standard excludes those items where ISO has desig- tion - Registration proced- nated Maintenance Agencies or Registration Authorities to ures provide identification schemes. It does not apply to Pub 2006 • freight containers, because their unique coding is speci- fied in ISO 6346, Freight containers -- Coding, identi- fication and marking;
  • 13. - 13 - NID Areas Entity Scope of the deliverable Existing Deliverables (ap- Deliverables under devel- proved) opment/expected date of approval • vehicles, because their unique identification is specified in ISO 3779, Road vehicles -- Vehicle identification number (VIN) -- Content and structure; • car radios, because their unique identification is speci- fied in ISO 10486, Passenger cars -- Car radio identi- fication number (CRIN). ISO/IEC This standard specifies the common rules that apply for ISO/IEC 15459-3 Published standard – Stage JTC 1/SC 31 unique for identifiers at all levels of unique identification 60.60 Part 3: Unique identifica- tion — Common rules for unique identifiers Pub 2006 ISO/IEC This standard provides unique identification at the item ISO/IEC 15459-4 Published standard 2006 – JTC 1/SC 31 level. Stage 60.60 Part 4: Unique identifiers This standard serves as the basis for identification in ISO for supply chain manage- 28219 (for bar codes) and ISO 17367 (for RFID) ment Pub 2006 ISO/IEC This standard provides unique identification at the return- ISO/IEC 15459-5 Text for FDIS ballot – JTC 1/SC 31 able transport level. Stage 50.20 Part 5: Unique identifier This standard serves as the basis for identification in ISO for returnable transport 15394 (for bar codes) and ISO 17364 (for RFID) items (RTIs) ISO/IEC This standard provides unique identification at the item ISO/IEC 15459-6 Text for FDIS ballot – JTC 1/SC 31 level, but where such items are tracked at the lowest level Stage 50.20 Part 6: Unique identifier by some aggregation such as lot or batch number. for product groupings ISO/IEC This standard provides unique identification at the product ISO/IEC 15459-7 Work Item Cancelled.
  • 14. - 14 - NID Areas Entity Scope of the deliverable Existing Deliverables (ap- Deliverables under devel- proved) opment/expected date of approval JTC 1/SC 31 packaging level. Part 7: Unique identifiers Functionality to be in- for product packaging cluded in Part 4 This standard serves as the basis for identification in ISO 22742 (for bar codes) and ISO 17366 (for RFID) ISO/IEC This standard provides unique identification at the trans- ISO/IEC 15459-8 Text under ballot as a CD JTC 1/SC 31 port unit grouping level. — Stage 30.20 Part 8: Grouping of trans- port units ISO/IEC This standard defines the air interface for 13.56 MHz pass- ISO/IEC 18000-3.1 Text at CD balloting stage JTC 1/SC 31 ive tags. 18000-3m3 is the air interface generally adopted 40.20 Information technology -- by EPCglobal as HF Gen 2 Radio frequency identific- Interference by EPCglobal ation for item management continues to put this stand- -- Part 3: Parameters for air ard at risk. By doing so it interface communications at also places 17364, 17365, 13,56 MHz (Revision of 17366, and 17367 at risk. ISO/IEC 18000-3:2004) SO/IEC This standard defines the unique identification provided to ISO/IEC 15963.2 Text at CD balloting stage JTC 1/SC 31 an RF tag. — 30.20 Information technology -- Radio frequency identific- ation for item management -- Unique identification for RF tags (Revision of ISO/IEC 15963:2004) ISO/IEC This standard defines the air interface for 860 to 960 MHz ISO/IEC 18000-6.2 Revision Text at FCD bal- JTC 1/SC 31 passive tags. 18000-6C is the air interface generally adop- loting 50.20 Information technology -- ted by EPCglobal as UHF Gen 2 Radio frequency identific- ation for item management
  • 15. - 15 - NID Areas Entity Scope of the deliverable Existing Deliverables (ap- Deliverables under devel- proved) opment/expected date of approval -- Part 6: Parameters for air interface communications at 860 MHz to 960 MHz (Re- vision of ISO/IEC 18000-6:2004, ISO/IEC 18000-6:2004/Amd 1:2006) ISO/IEC This standard defines the air interface for 433 MHz active ISO/IEC 18000-7 Text at FCD balloting JTC 1/SC 31 tags. ISO/IEC 18000-7 is the active air interface for ISO stage 40.20 Information technology, 17363 automatic identification and data capture tech- niques -- Radio frequency identification (RFID) for item management -- Air Interface -- Part 7: Paramet- ers for an active RFID air in- terface communications at 433 MHz (Revision of ISO/IEC 18000-7:2008) ISO/IEC This standard defines the air interface for 860 - 960 MHz ISO 29143 Text at CD stage 30.20 JTC 1/SC 31 passive tags when connected to a mobile telephone. Information technology -- Automatic identification and data capture tech- niques -- Air interface spe- cification for Mobile RFID interrogator ISO TC 122 ISO 17363 defines the usage of RFID technology for cargo ISO 17363 Published standard 2006 – shipment-specific tags in freight containers for supply Stage 60.60 Supply chain applications chain management applications (shipment tags). It defines of RFID – Freight contain- the air-interface communications, a common set of re- ers
  • 16. - 16 - NID Areas Entity Scope of the deliverable Existing Deliverables (ap- Deliverables under devel- proved) opment/expected date of approval quired data structures, and a commonly organized set of optional data requirements (through common syntax and semantics). ISO 17363 identifies the air-interface and communication parameters for active radio-frequency identification com- munications using ISO/IEC 18000-7. ISO 17363 is applicable to freight containers as defined in ISO 668 and to freight containers that are not defined by other ISO standards. It complements ISO 10891 for perma- nent container license-plate tags and ISO 18185 for elec- tronic container seals. ISO TC 122 ISO 17364 defines the usage of RFID technology for re- ISO 17364 Awaiting resolution of turnable transport items in supply chain management appli- ISO/IEC 18000-3m3. Supply chain applications cations. It defines the air-interface communications, a When CD of 3m3 is ap- of RFID – Returnable common set of required data structures, and a commonly proved 17364 will be sub- transport items organized set of optional data requirements (through com- mitted for FDIS Ballot mon syntax and semantics). Stage 40.99 ISO 17364 identifies the air-interface and communication parameters for passive radio-frequency identification com- munications using ISO/IEC 18000-6C or alternately ISO/IEC 18000-3m3. ISO TC 122 ISO 17365 defines the usage of RFID technology for trans- ISO 17365 Awaiting resolution of port units in supply chain management applications. It de- ISO/IEC 18000-3m3. Supply chain applications fines the air-interface communications, a common set of When CD of 3m3 is ap- of RFID – Transport units required data structures, and a commonly organized set of proved 17364 will be sub- optional data requirements (through common syntax and mitted for FDIS Ballot semantics). Stage 40.99
  • 17. - 17 - NID Areas Entity Scope of the deliverable Existing Deliverables (ap- Deliverables under devel- proved) opment/expected date of approval ISO 17365 identifies the air-interface and communication parameters for passive radio-frequency identification com- munications using ISO/IEC 18000-6C or alternately ISO/IEC 18000-3m3. ISO TC 122 ISO 17366 defines the usage of RFID technology for prod- ISO/DIS 17366.2 Awaiting resolution of uct packaging in supply chain management applications. It ISO/IEC 18000-3m3. Supply chain applications defines the air-interface communications, a common set of When CD of 3m3 is ap- of RFID – Product pack- required data structures, and a commonly organized set of proved 17366 will be sub- aging optional data requirements (through common syntax and mitted for publication – semantics). Stage 50.99 ISO 17366 identifies the air-interface and communication parameters for passive radio-frequency identification com- munications using ISO/IEC 18000-6C or alternately ISO/IEC 18000-3m3. ISO TC 122 ISO 17366 defines the usage of RFID technology for prod- ISO/DIS 17367.4 Awaiting resolution of uct packaging in supply chain management applications. It ISO/IEC 18000-3m3. Supply chain applications defines the air-interface communications, a common set of When CD of 3m3 is ap- of RFID – Product tagging required data structures, and a commonly organized set of proved 17367 will be sub- optional data requirements (through common syntax and mitted for publication – semantics). Stage 50.99 ISO 17366 identifies the air-interface and communication parameters for passive radio-frequency identification com- munications using ISO/IEC 18000-6C or alternately ISO/IEC 18000-3m3. IEC TC 3 This standard specifies basic requirements for identifica- IEC TC3 / 810 tion systems for the identification of objects (such as Basic rules for identifica- products, “items”, documents, database entries, etc.) in- tion systems cluding requirements for the application of identifiers in IEC TC 3/810 duplicates
  • 18. - 18 - NID Areas Entity Scope of the deliverable Existing Deliverables (ap- Deliverables under devel- proved) opment/expected date of approval computer sensible form, and requirements for their inter- the work of ISO/IEC change. The specification of a physical file formats re- 15459. Comments have quired for such an interchange is not included in this stand- been sent to IEC TC 3 Sec- ard, nor is possible physical marking for the identification retariat. Response re- of objects dealt with. ceived (3/836/RVN) on 2/2/7. V1.0 (OWSER NI V1.0) network identity OMA Work on OMA enablers that are addressing network iden- (approved release of OMA aspects standard- tity aspects and resulted in technical specifications. Web Services Network Iden- ization In that category, OMA has issued an approved release, tity) V1.0 (OWSER NI V1.0), that includes a requirements spe- cification (independent of technology realization), an archi- tecture specification, and technical specifications which are based on the Liberty Alliance Project specifications network identity OMA Work on OMA enablers that resulted in additional network OMA Identity Manage- aspects standard- identity requirements specifications, without additional ar- ment Framework Re- ization chitecture or technical specifications. quirements V1.0. In that category, OMA has issued a candidate requirements (an expected date of ap- specification, the OMA Identity Management Framework proval has not been Requirements V1.0. planned as the IMF Work Item is in maintenance; meaning that OMA is at present not actively work- ing on IMF. When new contributions are submitted to progress IMF the work item status can be changed to reflect such activity.) OMA ARC Work on multiple OMA enablers that are not focused on Work to address these Working network identity aspects standardization, but needs support particular aspects has
  • 19. - 19 - NID Areas Entity Scope of the deliverable Existing Deliverables (ap- Deliverables under devel- proved) opment/expected date of approval Group for some related issues – e.g. work on data types, formats just started recently. and identifiers conventions for parameters representing net- (For PEEM the planned work identities of principals (users, systems, devices, ap- expected date for Consist- plications and/or any resources). ency Review Start is 15 November 2007 (and this Such need has been identified recently in OMA ARC date indicates that within Working Group, in the context of working on Global Per- months after this date the missions Management (GPM) enabler and Policy Evalu- enabler is expected to ation, Enforcement and Management (PEEM) enabler. reach Candidate status) - For Global Permission Management (GPM) a Re- and for GPM the planned quirements Document has been created and an expected date for Consist- Architecture Document is being reviewed. ency Review Start is 30 September 2007.) For Policy Evaluation, Enforcement and Management (PEEM) a Requirements Document and an Architecture Document have been created. Technical Specifications are being drafted.
  • 20. i JCA-NID will define standardization areas at a later stage ii Official designation of the entity e.g. SGxy iii Short description of the scope of the deliverable iv The term “deliverable” denotes an ITU Recommendation, a Focus Group Technical Specification or any other document developed by standard developing organizations (SDOs), forums or consortia that can be considered as a JCA-NID related international standard (NID and USN related standards) or can help in the development of a JCA-NID related international standard.