1. Internet Evolution, Governance and the Digital Object Architecture Workshop on SCORM Sequencing and Navigation Gaithersburg, Maryland February 23, 2005 Robert E. Kahn Corporation for National Research Initiatives Reston, Virginia

2. Three Initial Networks About 30 – 35 years ago, DARPA funded the creation of three seminal packet networks – ARPANET, Packet Radio, Packet Satellite About 30 – 35 years ago, DARPA funded the creation of three seminal packet networks – ARPANET, Packet Radio, Packet Satellite The Internet came about from a desire to link the three of them The Internet came about from a desire to link the three of them Ethernet occurred in parallel, led by Xerox Parc researchers, and other network types followed Ethernet occurred in parallel, led by Xerox Parc researchers, and other network types followed The resulting architecture was independent of the number and type of networks or who ran them. The resulting architecture was independent of the number and type of networks or who ran them.

3. Key Decisions The Internet would be a global information system The Internet would be a global information system An open-architecture would be used to combine different networks based on open and well-known interfaces, protocols & objects. An open-architecture would be used to combine different networks based on open and well-known interfaces, protocols & objects. A new communications-oriented host protocol (TCP/IP) would be created to replace the original ARPANET host protocol (NCP) A new communications-oriented host protocol (TCP/IP) would be created to replace the original ARPANET host protocol (NCP) The concept of global addressing and IP addresses would be introduced to identify individual machines anywhere on the global Internet The concept of global addressing and IP addresses would be introduced to identify individual machines anywhere on the global Internet

4. Comments on the Key Decisions The architecture is robust in the presence of many different network types and many outages The architecture is robust in the presence of many different network types and many outages Gateways provided IP routing and Network Impedance Matching Gateways provided IP routing and Network Impedance Matching TCP accommodated end-end protocols TCP accommodated end-end protocols different packet sizes, duplicates, error detection, losses due to tunnels, mountains, jamming, etc. different packet sizes, duplicates, error detection, losses due to tunnels, mountains, jamming, etc. Separate network administrations were permitted, which allowed the Net to grow Separate network administrations were permitted, which allowed the Net to grow DNS not technically critical, but helped users DNS not technically critical, but helped users

5. Understanding the Big Picture Many things were done well from the outset; with 20/20 hindsight, some could have been done better Many things were done well from the outset; with 20/20 hindsight, some could have been done better The context was critical The context was critical Mostly mainframes, few time-sharing systems Mostly mainframes, few time-sharing systems No PCs, workstations, LANs No PCs, workstations, LANs One dominant carrier in the US One dominant carrier in the US Government facility initially Government facility initially What is important at the time may be only apparent with hindsight; but also what seems important at the time may not turn out to be so important later on What is important at the time may be only apparent with hindsight; but also what seems important at the time may not turn out to be so important later on

6. Key Management Structures Internet Configuration Control Board (ICCB) Internet Configuration Control Board (ICCB) Internet Activities Board (IAB) Internet Activities Board (IAB) Internet Engineering Task Force (IETF) Internet Engineering Task Force (IETF) Internet Architecture Board (IAB) Internet Architecture Board (IAB) Internet Society (ISOC) Internet Society (ISOC) Domain Name System (DNS) Domain Name System (DNS) Internet Corporation for Assigned Names and Numbers (ICANN) Internet Corporation for Assigned Names and Numbers (ICANN)

7. Defining the Internet Logical architecture for internetworking Logical architecture for internetworking Independent of the underlying networks Independent of the underlying networks Open architecture at the network level Open architecture at the network level Not the routers, switches, lines, computers Not the routers, switches, lines, computers Not any one service provider on the net Not any one service provider on the net Reference to the FNC definition from 1995 Reference to the FNC definition from 1995 www.hpcc.gov/fnc/Internet_res.html www.hpcc.gov/fnc/Internet_res.html

8. Updating the 1995 Definition "Internet" refers to the global information system that -- (i) is logically linked together by a globally unique address space based on the Internet Protocol (IP) or its subsequent extensions/follow-ons; (ii) is able to support communications using the Transmission Control Protocol/Internet Protocol (TCP/IP) suite or its subsequent extensions/follow-ons, and/or other IP-compatible protocols; and (iii) provides, uses or makes accessible, either publicly or privately, high level services layered on or integrated with the communications and related infrastructure described herein.

9. Social and Political Dimensions Most Nations had committed to ISO protocols Most Nations had committed to ISO protocols Yet TCP/IP won out in the final analysis Yet TCP/IP won out in the final analysis Many reasons why; critical mass, many organizations helped, no significant benefit to changing, etc. Many reasons why; critical mass, many organizations helped, no significant benefit to changing, etc. Formation of ICCB, IAB, IETF, etc enabled the net to evolve Formation of ICCB, IAB, IETF, etc enabled the net to evolve NSF strategy of fostering independent networks - expanded participation without central control NSF strategy of fostering independent networks - expanded participation without central control Boucher Bill allowed commercialization Boucher Bill allowed commercialization

10. The World Embraces the Internet Who is in Charge of the Internet? Who is in Charge of the Internet? Who is in Charge of the World Economy? Who is in Charge of the World Economy? World Summit in Geneva – December, 2003 World Summit in Geneva – December, 2003 And a host of follow-activities: And a host of follow-activities: ITU Workshop – February, 2004 ITU Workshop – February, 2004 UN ICT Task Force Global Forum – March, 2004 UN ICT Task Force Global Forum – March, 2004 Working Group on Internet Governance (WGIG) Working Group on Internet Governance (WGIG) Phase II of the World Summit in Tunis – Nov. 05 Phase II of the World Summit in Tunis – Nov. 05

11. Infrastructure Development What is so hard about it? What is so hard about it? Making it scalable over platforms, size and time Making it scalable over platforms, size and time Achieving Critical Mass Achieving Critical Mass Getting Buy in Getting Buy in Pleasing many essential participants Pleasing many essential participants Displacing prior capabilities Displacing prior capabilities Structuring matters to deal with concerns about empire building Structuring matters to deal with concerns about empire building Its a lot easier to create brand new capabilities than to affect existing means of operation Its a lot easier to create brand new capabilities than to affect existing means of operation

12. Infrastructure Creation is a Subtractive Process Infrastructure reduces a common, shared capability to its basic and essential attributes Infrastructure reduces a common, shared capability to its basic and essential attributes These attributes are not always recognized or understood up front These attributes are not always recognized or understood up front Upon further scrutiny, capabilities are usually deleted from a well-conceived architecture over time Upon further scrutiny, capabilities are usually deleted from a well-conceived architecture over time Consensus develops when no more can be removed without disabling the infrastructure Consensus develops when no more can be removed without disabling the infrastructure

13. What is the Problem? Managing information in the Net over very long periods of time – e.g. centuries or more Managing information in the Net over very long periods of time – e.g. centuries or more Dealing with very large amounts of information in the Net over time Dealing with very large amounts of information in the Net over time When information, its location(s) and even the underlying systems may change dramatically over time When information, its location(s) and even the underlying systems may change dramatically over time Respecting and protecting rights, interests and value Respecting and protecting rights, interests and value

14. A Meta-level Architecture Allows for arbitrary types of information systems Allows for arbitrary types of information systems Allows for dynamic formatting and data typing Allows for dynamic formatting and data typing Can accommodate interoperability between multiple different information systems Can accommodate interoperability between multiple different information systems Allows metadata schema to be identified and typed Allows metadata schema to be identified and typed

15. Digital Object Architecture: Motivation To reformulate the Internet architecture around the notion of uniquely identifiable data structures To reformulate the Internet architecture around the notion of uniquely identifiable data structures Enabling existing and new types of information to be reliably managed and accessed in the Internet environment over long periods of time Enabling existing and new types of information to be reliably managed and accessed in the Internet environment over long periods of time Providing mechanisms to stimulate innovation, the creation of dynamic new forms of expression and to manifest older forms Providing mechanisms to stimulate innovation, the creation of dynamic new forms of expression and to manifest older forms While supporting intellectual property protection, fine- grained access control, and enable well-formed business practices to emerge While supporting intellectual property protection, fine- grained access control, and enable well-formed business practices to emerge

16. Digital Object Architecture Technical Components Technical Components Digital Objects (DOs) Digital Objects (DOs) Structured data, independent of the platform on which it was created Structured data, independent of the platform on which it was created Consisting of elements of the form Consisting of elements of the form One of which is its unique, persistent identifier One of which is its unique, persistent identifier Resolution of Unique Identifiers Resolution of Unique Identifiers Maps an identifier into state information about the DO Maps an identifier into state information about the DO Handle System is a general purpose resolution system Handle System is a general purpose resolution system Repositories from which DOs may be accessed Repositories from which DOs may be accessed And into which they may be deposited And into which they may be deposited Metadata Registries Metadata Registries Repositories that contain general information about DOs Repositories that contain general information about DOs Supports multiple metadata schemes Supports multiple metadata schemes Can map queries into unique DO specifications (via handles) Can map queries into unique DO specifications (via handles)

17. What is a Digital Object Defined data structure, machine independent Defined data structure, machine independent Consisting of a set of elements Consisting of a set of elements Each of the form Each of the form One of which is the unique identifier One of which is the unique identifier Identifiers are known as Handles Identifiers are known as Handles Format is prefix/suffix Format is prefix/suffix Prefix is unique to a naming authority Prefix is unique to a naming authority Suffix can be any string of bits assigned by that authority Suffix can be any string of bits assigned by that authority Data structure can be parsed; types can be resolved within the architecture Data structure can be parsed; types can be resolved within the architecture Associated properties record and transaction record containing metadata and usage information Associated properties record and transaction record containing metadata and usage information

18. Interoperability & Federated Repositories Create a cohesive interoperable collection of repository-based systems Initially, perhaps, around a core set of projects, content, applications and/or organizations as in ADL Initially, perhaps, around a core set of projects, content, applications and/or organizations as in ADL Demonstrate interoperability between different repository collections Demonstrate interoperability between different repository collections Develop procedures to insure continued accessibility to key archival information Develop procedures to insure continued accessibility to key archival information

19. Repository Notion Any Hardware & Software Configuration Logical External Interface RAP Repository Access Protocol

20. Repositories & Digital Objects REPOSITORY IPv6 Each Digital Object has its own unique & persistent ID Content Providers want to assign Ids Could be upwards of trillions of DOs per Repository Objects may be Replicated in Multiple Repositories

21. Handle System Distributed Identifier Service on the Internet Distributed Identifier Service on the Internet First General Purpose Resolution system First General Purpose Resolution system Can be used to locate repositories that contain digital objects given their handles - and more! Can be used to locate repositories that contain digital objects given their handles - and more! Other indirect references Other indirect references Public Keys, Authentication information for Dos Public Keys, Authentication information for Dos Accommodates interoperability between many different information systems; for example Accommodates interoperability between many different information systems; for example DNS was demonstrated on the Handle System in preparation for Y2K DNS was demonstrated on the Handle System in preparation for Y2K Can support ENUM, RFID, and more Can support ENUM, RFID, and more

22. Attributes of the Handle System The basic Architecture of the Handle System is flat, scaleable, and extensible The basic Architecture of the Handle System is flat, scaleable, and extensible Logically central, but physically decentralized Logically central, but physically decentralized Supports Local Handle Services, if desired Supports Local Handle Services, if desired Handle resolutions return entire Handle Records or portions thereof Handle resolutions return entire Handle Records or portions thereof Handle Records are also Handle Records are also digital objects digital objects signed by the servers signed by the servers doubly certificated by the system doubly certificated by the system

23. Resolution Mechanism Multiple Sites Multiple Servers Handle System Handle Record System is non –nodal Scaleable & Distributed Supports global (and local) resolution With backup for reliability, mirroring for efficiency

24. Managing Rights & Interests Not just about copyright Not just about copyright Terms and Conditions (T&Cs) for use may be contained within each DO; also information about intrinsic value, such as monetary value Terms and Conditions (T&Cs) for use may be contained within each DO; also information about intrinsic value, such as monetary value T&Cs are intended to indicate clearly what one can and/or cannot do with a given DO, where such clarity is intended by the owner of the DO T&Cs are intended to indicate clearly what one can and/or cannot do with a given DO, where such clarity is intended by the owner of the DO Not an enforcement means, although it may be used by an enforcement system Not an enforcement means, although it may be used by an enforcement system Mobile programs that are Digital Objects may apply such terms to themselves and to any digital objects they contain Mobile programs that are Digital Objects may apply such terms to themselves and to any digital objects they contain

25. Handle Format Handle Format Prefix Authority Item ID (any format) Prefix Suffix In use, a Handle is an opaque string. 2304.40/1234 Other examples of Handles 2304/general info 2304/1 2304. HQ/staff 2304.1/memo123 2304.22.Pub/2004

26. Direct Access and Proxies Direct Access One or more Proxy Servers Indirect Access

27. Redirection of Handle Requests Direct Access Direct Access One or more Local Handle Services General Registry of all Naming Authorities Redirection Information Redirection Information

28. Conclusions Managing Digital Objects for long-term access is a key challenge Managing Digital Objects for long-term access is a key challenge Initial Technology Components are available; Industry is expected to generate more over time Initial Technology Components are available; Industry is expected to generate more over time Third-party value-added providers in the private sector will ultimately shape the long-term evolution Third-party value-added providers in the private sector will ultimately shape the long-term evolution Interoperability and reliable information access is a critical objective Interoperability and reliable information access is a critical objective A diversity of applications (with user-friendly interfaces) need to be developed & deployed A diversity of applications (with user-friendly interfaces) need to be developed & deployed The ADL Project can have a central role to play in demonstrating the technology and using it effectively The ADL Project can have a central role to play in demonstrating the technology and using it effectively