naming architecture for naming architecture for object to
play

Naming Architecture for Naming Architecture for Object to Object - PowerPoint PPT Presentation

Naming Architecture for Naming Architecture for Object to Object Communications <draft-lee-object-naming-00.txt> 75 th IETF Stockholm, July 2009 Gyu Myoung Lee (gmlee@it-sudparis.eu) G M L ( l @it d i ) Jun Kyun Choi


  1. Naming Architecture for Naming Architecture for Object to Object Communications <draft-lee-object-naming-00.txt> 75 th IETF Stockholm, July 2009 Gyu Myoung Lee (gmlee@it-sudparis.eu) G M L ( l @it d i ) Jun Kyun Choi (jkchoi@icu.ac.kr) S Seng Kyoun Jo (skjo@etri.re.kr) K J ( kj @ t i k ) Jeong Yun Kim (jykim@etri.re.kr) 1

  2. Contents � History of previous document � History of previous document � E-mail discussions since last meeting � Overview of object naming document � Key concept � Layered architecture for identity processing � Object mapping – extension of stack architecture � Conceptual diagram for providing connectivity to objects � Issues for object naming ssues o objec g � Next steps 2

  3. History of previous document y p � Previous document (HIP extensions for object to � Previous document (HIP extensions for object to object communications) � 1 st presentation, Dublin meeting (00 version) � 1 st t ti D bli ti (00 i ) � Presented the necessity of object to object communications � 2 nd presentation Minneapolis meeting (01 version) � 2 presentation, Minneapolis meeting (01 version) � Introduced ITU-T’s activities � Discussed several technical issues including security g y � 3 rd presentation, San Francisco meeting (02 version) � Specified protocols for HIP extension 3

  4. E-mail discussions since last meeting g � Future work on naming objects in HIP � Future work on naming objects in HIP � Two possible solutions for RG item � Pick up one or both of the existing drafts and work on them as RG � Pick up one or both of the existing drafts and work on them as RG documents � Work on a more broadly scoped informational document � Discussion results � Agreed that the topic is interesting � Decided to create a new internet-draft on the object naming which concentrates more on conceptual requirements and architecture � De elop a ne � Develop a new high-level architectural document high le el architect ral doc ment � Naming Architecture for Object to Object Communications 4

  5. Overview of object naming document j g � Object to object communications (ubiquitous � Object to object communications (ubiquitous networking) � New types of objects connected to the network for enabling � N t f bj t t d t th t k f bli the use of various communication services � Each object delivers information using network with/without � Each object delivers information using network with/without the help of humans. (e.g., sensor networking, etc) � Objective � Objective � Connecting to anything using object identification � Protection of object (including right management) � Protection of object (including right management) � Service and location discovery � Protocol development for object naming Protocol development for object naming 5

  6. Key concept y p � Communications with objects through Internet � Communications with objects through Internet Objects Personal Devices Contents PC, Phone, PDA, Audio, Video, Doc, Human TV, Camera Book Providing Info. Devices connectivity Appliances Internet Server, Database, Home, Office, Medical, Navigation, Meter g , Surveillance RFID/Sensors Transportation RFID tag, e-tag, Car, Train, Airplane Smart card Smart card 6

  7. Layered architecture for identity processing Identifiers Identity Processing User Name Logical identities for (Attributes) services Identification/ Authorization RFID, Content ID, Object IDs Telephone number, (Physical & logical IDs) URL/URI, etc Mapping/ Binding Session/Protocol ID Communication IDs IP address MAC address 7

  8. Object mapping – extension of stack architecture Obj Object ID Object ID Host ID Host ID IP address IP address Non -IP interface (e.g., air interface) Network attachment Network attachment IP interface IP interface (a) Direct mapping (Object in a host) (b) Indirect mapping (remote objects) 8

  9. Conceptual diagram for providing connectivity to objects to objects Host (e.g., server) Object (e.g., content) IP address Object (e.g., device, Internet product, sensor, etc) IP address IP address Gateway IP interface non-IP interface Global Mapping Identifier IP Connectivity for object Address Binding with Internet 9

  10. Issues for object naming j g � Detailed requirements Detailed requirements � How to identify all of objects � How to support security How to support security � Architectural aspects � Extensible to all of objects � Extensible to all of objects � Interoperable with a new naming/addressing architecture (e.g., ID/LOC splits) ID/LOC splits) � Alternative protocol solutions � Reuse existing protocols (e.g., extension of HIP) R i ti t l ( t i f HIP) � Develop a new protocol (e.g., object identity protocol) 10

  11. Next steps p � Proposals � Proposals � Adopt as Research Group Item? � We already have consensuses on importance of this topic through e � We already have consensuses on importance of this topic through e- mail discussion � How to develop this document? p � Officially make a design team for more progresses � Update the document p � Inputs from feedbacks and comments using mailing list � Inputs from experts/design team of HIPRG Inputs from experts/design team of HIPRG 11

Recommend


More recommend