DOCSLIB.ORG

[email protected]

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Rfc2018@Ntia.Doc.Gov 48600 Federal Register / Vol. 83, No. 187 / Wednesday, September 26, 2018 / Notices Estimated Total Annual Burden outlines of the ecosystem that should be foreign countries, and some U.S. states, Hours: 150 hours. created to provide those protections. have articulated distinct visions for how Estimated Total Annual Cost to DATES: Comments must be received by to address privacy concerns, leading to Public: $0 in capital and reporting/ 11:59 p.m. Eastern Daylight Time on a nationally and globally fragmented recordkeeping costs. October 26, 2018. regulatory landscape. Such fragmentation naturally disincentivizes IV. Request for Comments ADDRESSES: Written comments identified by Docket No. 180821780– innovation by increasing the regulatory Comments are invited on: (a) Whether 8780–01 may be submitted by email to costs for products that require scale. The the proposed collection of information [email protected]. Comments Administration hopes to articulate a is necessary for the proper performance submitted by email should be machine- renewed vision, one that reduces of the functions of the agency, including readable and should not be copy- fragmentation nationally and increases whether the information shall have protected. Written comments also may harmonization and interoperability practical utility; (b) the accuracy of the be submitted by mail to the National nationally and globally. Further, changes in the way personal agency’s estimate of the burden Telecommunications and Information information is used by organizations, (including hours and cost) of the Administration, U.S. Department of and how users interact with the proposed collection of information; (c) Commerce, 1401 Constitution Avenue products and services with which they ways to enhance the quality, utility, and NW, Room 4725, Attn: Privacy RFC, frequently engage, have increased the clarity of the information to be Washington, DC 20230. collected; and (d) ways to minimize the belief that users are losing control over FOR FURTHER INFORMATION CONTACT: burden of the collection of information their personal information. As seen in Travis Hall, Telecommunications Policy on respondents, including through the data collected by the National Analyst, Office of Policy Analysis and use of automated collection techniques Telecommunications and Information Development, National or other forms of information Administration (NTIA), at least a third Telecommunications and Information technology. of online households have been deterred Administration, U.S. Department of Comments submitted in response to from certain forms of online activity, Commerce, 1401 Constitution Avenue this notice will be summarized and/or such as financial transactions, due to NW, Room 4725, Washington, DC 1 included in the request for OMB privacy and security concerns. The 20230; telephone: 202–482–3522; email: approval of this information collection; Administration takes these concerns [email protected]. seriously and believes that users should they also will become a matter of public For media inquiries: Anne Veigle, record. be able to benefit from dynamic uses of Director, Office of Public Affairs, their information, while still expecting Dated: September 20, 2018. National Telecommunications and organizations will appropriately Sarah Brabson, Information Administration, U.S. minimize risks to users’ privacy. Risk- NOAA PRA Clearance Officer. Department of Commerce, 1401 based flexibility is therefore at the heart [FR Doc. 2018–20850 Filed 9–25–18; 8:45 am] Constitution Avenue NW, Room 4897, of the approach the Administration is BILLING CODE 3510–JE–P Washington, DC 20230; telephone: (202) requesting comment on in this RFC. We 482–7002; email: [email protected]. are mindful of the potential impact of a SUPPLEMENTARY INFORMATION: solution on small and mid-sized DEPARTMENT OF COMMERCE I. Background businesses, and we will be looking for solutions that support their continued National Telecommunications and The U.S. Department of Commerce ability to innovate and support Information Administration (Department) requests comment on economic growth. ways to advance consumer privacy The United States has a history of [Docket No. 180821780–8780–01] while protecting prosperity and providing strong protections for privacy innovation. Every day, individuals RIN 0660–XC043 dating back to 1789, with the drafting of interact with an array of products and our Bill of Rights, including the Fourth Developing the Administration’s services, many of which have become Amendment. The United States also has Approach to Consumer Privacy integral to their daily lives. Often, been a leader in developing privacy especially in the digital environment, norms, be it through the development of AGENCY: National Telecommunications these products and services depend on what ultimately became known as the and Information Administration, U.S. the collection, retention, and use of Fair Information Practice Principles Department of Commerce. personal data about their users. Users (FIPPs) in the 1970’s, or through the ACTION: Notice; request for public must therefore trust that organizations strongest privacy enforcement regime in comments. will respect their interests, understand the world. For users of products and what is happening with their personal services in several sectors (e.g., SUMMARY: On behalf of the U.S. data, and decide whether they are healthcare, education, financial Department of Commerce, the National comfortable with this exchange. Trust is services), specific laws cover how Telecommunications and Information at the core of the United States’ privacy organizations handle personal Administration (NTIA) is requesting policy formation. Through this Request information. Where no sector-specific comments on ways to advance for Comment (RFC), the Administration laws apply, the Federal Trade consumer privacy while protecting will determine the best path toward Commission (FTC) has the authority to prosperity and innovation. NTIA is protecting individual’s privacy while ensure that organizations are not seeking public comments on a proposed fostering innovation. deceiving consumers or operating approach to this task that lays out a set The time is ripe for this unfairly. In all respects, the United of user-centric privacy outcomes that Administration to provide the underpin the protections that should be leadership needed to ensure that the 1 NTIA Blog, ‘‘Most Americans Continue to Have produced by any Federal actions on United States remains at the forefront of Privacy and Security Concerns, NTIA Survey Finds’’ (Aug. 20, 2018), https://www.ntia.doc.gov/ consumer-privacy policy, and a set of enabling innovation with strong privacy blog/2018/most-americans-continue-have-privacy- high-level goals that describe the protections. A growing number of and-security-concerns-ntia-survey-finds. VerDate Sep<11>2014 19:21 Sep 25, 2018 Jkt 244001 PO 00000 Frm 00016 Fmt 4703 Sfmt 4703 E:\FR\FM\26SEN1.SGM 26SEN1 daltland on DSKBBV9HB2PROD with NOTICES Federal Register / Vol. 83, No. 187 / Wednesday, September 26, 2018 / Notices 48601 States has successfully investigated and clarity, this principle is implemented by service, the privacy risks that the taken enforcement actions against mandating notice and choice. To date, product or service may be creating, organizations that violate these existing such mandates have resulted primarily other means of mitigating these privacy Federal laws. This RFC asks how best to in long, legal, regulator-focused privacy risks, the impact of access and strengthen the protections users policies and check boxes, which only correction on other organizational risks, currently enjoy; it does not propose help a very small number of users who and other relevant factors, in order to changing current sectoral federal laws.2 choose to read these policies and make determine the degree or manner in This RFC is the outcome of an binary choices. which access and correction could help interagency process led by the National The Administration is instead achieve a user-centric privacy outcome Economic Council (NEC) of the United proposing that discussion of consumer without creating needless costs. States. NTIA has worked in privacy in the United States refocus on 1. Transparency. Users should be able coordination with the International the outcomes of organizational to easily understand how an Trade Administration (ITA) to ensure practices, rather than on dictating what organization collects, stores, uses, and consistency with international policy those practices should be. The desired shares their personal information. objectives, and in parallel with the work outcome is a reasonably informed user, Transparency can be enabled through of the National Institute of Standards empowered to meaningfully express various means. Organizations should and Technology (NIST) in developing a privacy preferences, as well as products take into account how the average user voluntary risk-based Privacy Framework and services that are inherently interacts with a product or service, and as an enterprise risk management tool designed with appropriate privacy maximize the intuitiveness of how it for organizations. In developing this protections, particularly in business conveys information to users. In many RFC, the Department conducted contexts in which relying on user cases, lengthy notices describing a significant outreach to a diverse set of intervention may be insufficient to company’s privacy program at a individuals and
Load more

Recommended publications
  • 2606 A. Panitz BCP: 32 June 1999 Category: Best Current Practice
    Network Working Group D. Eastlake Request for Comments: 2606 A. Panitz BCP: 32 June 1999 Category: Best Current Practice Reserved Top Level DNS Names Status of this Memo This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (1999). All Rights Reserved. Abstract To reduce the likelihood of conflict and confusion, a few top level domain names are reserved for use in private testing, as examples in documentation, and the like. In addition, a few second level domain names reserved for use as examples are documented. Table of Contents 1. Introduction............................................1 2. TLDs for Testing, & Documentation Examples..............2 3. Reserved Example Second Level Domain Names..............2 4. IANA Considerations.....................................3 5. Security Considerations.................................3 References.................................................3 Authors' Addresses.........................................4 Full Copyright Statement...................................5 1. Introduction The global Internet Domain Name System is documented in [RFC 1034, 1035, 1591] and numerous additional Requests for Comment. It defines a tree of names starting with root, ".", immediately below which are top level domain names such as ".com" and ".us". Below top level domain names there are normally additional levels of names. Eastlake & Panitz Best Current Practice [Page 1] RFC 2606 Reserved Top Level DNS Names June 1999 2. TLDs for Testing, & Documentation Examples There is a need for top level domain (TLD) names that can be used for creating names which, without fear of conflicts with current or future actual TLD names in the global DNS, can be used for private testing of existing DNS related code, examples in documentation, DNS related experimentation, invalid DNS names, or other similar uses.
    [Show full text]
  • Network Working Group J. Postel Request for Comments: 820 J. Vernon January 1983 Obsoletes Rfcs
    Network Working Group J. Postel Request for Comments: 820 J. Vernon January 1983 Obsoletes RFCs: 790, 776, 770, 762, 758, 755, 750, 739, 604, 503, 433, 349 Obsoletes IENs: 127, 117, 93 ASSIGNED NUMBERS This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This RFC will be updated periodically, and in any case current information can be obtained from Jon Postel. The assignment of numbers is also handled by Jon, subject to the agreement between DARPA/IPTO and DDN/PMO about number allocation, documented in Appendix A of this RFC. If you are developing a protocol or application that will require the use of a link, socket, port, protocol, or network number please contact Jon to receive a number assignment. Jon Postel USC - Information Sciences Institute 4676 Admiralty Way Marina del Rey, California 90291 phone: (213) 822-1511 ARPANET mail: POSTEL@ISIF The ARPANET community is making the transition form the ARPANET to the ARPA Internet. This has been characterized as the NCP/TCP transition [63], although many other the protocols are involved, too. The working documents for the new Internet environment have been collected by the Network Information Center (NIC) in a book entitled the "Internet Protocol Transition Workbook" [62]. Most of the protocols mentioned here are documented in the RFC series of notes. The more prominent and more generally used are documented in the "Internet Protocol Transition Workbook" or in the old "Protocol Handbook" [17] prepared by the NIC. Some of the items listed are undocumented.
    [Show full text]
  • Network Working Group J. Reynolds Request for Comments: 923 J
    Network Working Group J. Reynolds Request for Comments: 923 J. Postel ISI Obsoletes RFCs: 900, 870, 820, October 1984 790, 776, 770, 762, 758, 755, 750, 739, 604, 503, 433, 349 Obsoletes IENs: 127, 117, 93 ASSIGNED NUMBERS Status of this Memo This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. Distribution of this memo is unlimited. Introduction This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This RFC will be updated periodically, and in any case current information can be obtained from Joyce Reynolds. The assignment of numbers is also handled by Joyce. If you are developing a protocol or application that will require the use of a link, socket, port, protocol, network number, etc., please contact Joyce to receive a number assignment. Joyce Reynolds USC - Information Sciences Institute 4676 Admiralty Way Marina del Rey, California 90292-6695 Phone: (213) 822-1511 ARPA mail: [email protected] Most of the protocols mentioned here are documented in the RFC series of notes. The more prominent and more generally used are documented in the "Internet Protocol Transition Workbook" [33] or in the old "ARPANET Protocol Handbook" [34] prepared by the NIC. Some of the items listed are undocumented. Further information on protocols can be found in the memo "Official ARPA-Internet Protocols" [89]. In all cases the name and mailbox of the responsible individual is indicated. In the lists that follow, a bracketed entry, e.g., [nn,iii], at the right hand margin of the page indicates a reference for the listed protocol, where the number ("nn") cites the document and the letters ("iii") cites the person.
    [Show full text]
  • 1117 M. Stahl Obsoletes Rfcs: 1062, 1020, 997, 990, 960, 943, M
    Network Working Group S. Romano Request for Comments: 1117 M. Stahl Obsoletes RFCs: 1062, 1020, 997, 990, 960, 943, M. Recker 923, 900, 870, 820, 790, 776, 770, 762, SRI-NIC 758, 755, 750, 739, 604, 503, 433, 349 August 1989 Obsoletes IENs: 127, 117, 93 INTERNET NUMBERS Status of this Memo This memo is an official status report on the network numbers and the autonomous system numbers used in the Internet community. Distribution of this memo is unlimited. Introduction This Network Working Group Request for Comments documents the currently assigned network numbers and gateway autonomous systems. This RFC will be updated periodically, and in any case current information can be obtained from Hostmaster at the DDN Network Information Center (NIC). Hostmaster DDN Network Information Center SRI International 333 Ravenswood Avenue Menlo Park, California 94025 Phone: 1-800-235-3155 Network mail: [email protected] Most of the protocols used in the Internet are documented in the RFC series of notes. Some of the items listed are undocumented. Further information on protocols can be found in the memo "Official Internet Protocols" [40]. The more prominent and more generally used are documented in the "DDN Protocol Handbook" [17] prepared by the NIC. Other collections of older or obsolete protocols are contained in the "Internet Protocol Transition Workbook" [18], or in the "ARPANET Protocol Transition Handbook" [19]. For further information on ordering the complete 1985 DDN Protocol Handbook, contact the Hostmaster. Also, the Internet Activities Board (IAB) publishes the "IAB Official Protocol Standards" [52], which describes the state of standardization of protocols used in the Internet.
    [Show full text]
  • Network Working Group N. Freed Request for Comments: 2049 Innosoft Obsoletes: 1521, 1522, 1590 N
    Network Working Group N. Freed Request for Comments: 2049 Innosoft Obsoletes: 1521, 1522, 1590 N. Borenstein Category: Standards Track First Virtual November 1996 Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract STD 11, RFC 822, defines a message representation protocol specifying considerable detail about US-ASCII message headers, and leaves the message content, or message body, as flat US-ASCII text. This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages to allow for (1) textual message bodies in character sets other than US-ASCII, (2) an extensible set of different formats for non-textual message bodies, (3) multi-part message bodies, and (4) textual header information in character sets other than US-ASCII. These documents are based on earlier work documented in RFC 934, STD 11, and RFC 1049, but extends and revises them. Because RFC 822 said so little about message bodies, these documents are largely orthogonal to (rather than a revision of) RFC 822. The initial document in this set, RFC 2045, specifies the various headers used to describe the structure of MIME messages. The second document defines the general structure of the MIME media typing system and defines an initial set of media types.
    [Show full text]
  • How Constructing the DNS Shaped Internet Governance
    A Service of Leibniz-Informationszentrum econstor Wirtschaft Leibniz Information Centre Make Your Publications Visible. zbw for Economics Malcic, Steven Article The problem of future users: how constructing the DNS shaped internet governance Internet Policy Review Provided in Cooperation with: Alexander von Humboldt Institute for Internet and Society (HIIG), Berlin Suggested Citation: Malcic, Steven (2016) : The problem of future users: how constructing the DNS shaped internet governance, Internet Policy Review, ISSN 2197-6775, Alexander von Humboldt Institute for Internet and Society, Berlin, Vol. 5, Iss. 3, pp. 1-13, http://dx.doi.org/10.14763/2016.3.434 This Version is available at: http://hdl.handle.net/10419/214028 Standard-Nutzungsbedingungen: Terms of use: Die Dokumente auf EconStor dürfen zu eigenen wissenschaftlichen Documents in EconStor may be saved and copied for your Zwecken und zum Privatgebrauch gespeichert und kopiert werden. personal and scholarly purposes. Sie dürfen die Dokumente nicht für öffentliche oder kommerzielle You are not to copy documents for public or commercial Zwecke vervielfältigen, öffentlich ausstellen, öffentlich zugänglich purposes, to exhibit the documents publicly, to make them machen, vertreiben oder anderweitig nutzen. publicly available on the internet, or to distribute or otherwise use the documents in public. Sofern die Verfasser die Dokumente unter Open-Content-Lizenzen (insbesondere CC-Lizenzen) zur Verfügung gestellt haben sollten, If the documents have been made available under an Open gelten
    [Show full text]
  • Network Working Group J. Postel Request for Comments: 959 J. Reynolds ISI Obsoletes RFC: 765 (IEN 149) October 1985
    Network Working Group J. Postel Request for Comments: 959 J. Reynolds ISI Obsoletes RFC: 765 (IEN 149) October 1985 FILE TRANSFER PROTOCOL (FTP) Status of this Memo This memo is the official specification of the File Transfer Protocol (FTP). Distribution of this memo is unlimited. The following new optional commands are included in this edition of the specification: CDUP (Change to Parent Directory), SMNT (Structure Mount), STOU (Store Unique), RMD (Remove Directory), MKD (Make Directory), PWD (Print Directory), and SYST (System). Note that this specification is compatible with the previous edition. 1. INTRODUCTION The objectives of FTP are 1) to promote sharing of files (computer programs and/or data), 2) to encourage indirect or implicit (via programs) use of remote computers, 3) to shield a user from variations in file storage systems among hosts, and 4) to transfer data reliably and efficiently. FTP, though usable directly by a user at a terminal, is designed mainly for use by programs. The attempt in this specification is to satisfy the diverse needs of users of maxi-hosts, mini-hosts, personal workstations, and TACs, with a simple, and easily implemented protocol design. This paper assumes knowledge of the Transmission Control Protocol (TCP) [2] and the Telnet Protocol [3]. These documents are contained in the ARPA-Internet protocol handbook [1]. 2. OVERVIEW In this section, the history, the terminology, and the FTP model are discussed. The terms defined in this section are only those that have special significance in FTP. Some of the terminology is very specific to the FTP model; some readers may wish to turn to the section on the FTP model while reviewing the terminology.
    [Show full text]
  • Internet Points of Control As Global Governance Laura Denardis INTERNET GOVERNANCE PAPERS PAPER NO
    INTERNET GOVERNANCE PAPERS PAPER NO. 2 — AUGUST 2013 Internet Points of Control as Global Governance Laura DeNardis INTERNET GOVERNANCE PAPERS PAPER NO. 2 — AUGUST 2013 Internet Points of Control as Global Governance Laura DeNardis Copyright © 2013 by The Centre for International Governance Innovation. The opinions expressed in this publication are those of the author and do not necessarily reflect the views of The Centre for International Governance Innovation or its Operating Board of Directors or International Board of Governors. This work was carried out with the support of The Centre for International Governance Innovation (CIGI), Waterloo, Ontario, Canada (www. cigionline.org). This work is licensed under a Creative Commons Attribution — Non-commercial — No Derivatives License. To view this license, visit (www.creativecommons.org/licenses/ by-nc-nd/3.0/). For re-use or distribution, please include this copyright notice. Cover and page design by Steve Cross. ACKNOWLEDGEMENT CIGI gratefully acknowledges the support of the Copyright Collective of Canada. CONTENTS About the Author 1 About Organized Chaos: Reimagining the Internet Project 2 Acronyms 2 Executive Summary 3 Introduction 3 Global Struggles Over Control of CIRS 5 Governance via Internet Technical Standards 8 Routing and Interconnection Governance 10 Emerging International Governance Themes 12 Works Cited 14 About CIGI 15 INTERNET GOVERNANCE PAPERS INTERNET POINTS OF CONTROL AS GLOBAL GOVERNANCE ABOUT THE AUTHOR Laura DeNardis Laura DeNardis, CIGI senior fellow, is an Internet governance scholar and professor in the School of Communication at American University in Washington, DC. Her books include The Global War for Internet Governance (forthcoming 2014), Opening Standards: The Global Politics of Interoperability (2011), Protocol Politics: The Globalization of Internet Governance (2009) and Information Technology in Theory (2007, with Pelin Aksoy).
    [Show full text]
  • The People Who Invented the Internet Source: Wikipedia's History of the Internet
    The People Who Invented the Internet Source: Wikipedia's History of the Internet PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sat, 22 Sep 2012 02:49:54 UTC Contents Articles History of the Internet 1 Barry Appelman 26 Paul Baran 28 Vint Cerf 33 Danny Cohen (engineer) 41 David D. Clark 44 Steve Crocker 45 Donald Davies 47 Douglas Engelbart 49 Charles M. Herzfeld 56 Internet Engineering Task Force 58 Bob Kahn 61 Peter T. Kirstein 65 Leonard Kleinrock 66 John Klensin 70 J. C. R. Licklider 71 Jon Postel 77 Louis Pouzin 80 Lawrence Roberts (scientist) 81 John Romkey 84 Ivan Sutherland 85 Robert Taylor (computer scientist) 89 Ray Tomlinson 92 Oleg Vishnepolsky 94 Phil Zimmermann 96 References Article Sources and Contributors 99 Image Sources, Licenses and Contributors 102 Article Licenses License 103 History of the Internet 1 History of the Internet The history of the Internet began with the development of electronic computers in the 1950s. This began with point-to-point communication between mainframe computers and terminals, expanded to point-to-point connections between computers and then early research into packet switching. Packet switched networks such as ARPANET, Mark I at NPL in the UK, CYCLADES, Merit Network, Tymnet, and Telenet, were developed in the late 1960s and early 1970s using a variety of protocols. The ARPANET in particular led to the development of protocols for internetworking, where multiple separate networks could be joined together into a network of networks. In 1982 the Internet Protocol Suite (TCP/IP) was standardized and the concept of a world-wide network of fully interconnected TCP/IP networks called the Internet was introduced.
    [Show full text]
  • Rssac026v2: RSSAC Lexicon
    RSSAC026v2: RSSAC Lexicon An Advisory from the ICANN Root Server System Advisory Committee (RSSAC) 12 March 2020 RSSAC Lexicon Preface This is an Advisory to the Internet Corporation for Assigned Names and Numbers (ICANN) Board of Directors and the Internet community more broadly from the ICANN Root Server System Advisory Committee (RSSAC). In this Advisory, the RSSAC defines terms related to root server operations for the ICANN Community. The RSSAC seeks to advise the ICANN community and Board on matters relating to the operation, administration, security and integrity of the Internet’s Root Server System. This includes communicating on matters relating to the operation of the Root Servers and their multiple instances with the technical and ICANN community, gathering and articulating requirements to offer to those engaged in technical revisions of the protocols and best common practices related to the operational of DNS servers, engaging in ongoing threat assessment and risk analysis of the Root Server System and recommend any necessary audit activity to assess the current status of root servers and root zone. The RSSAC has no authority to regulate, enforce, or adjudicate. Those functions belong to others, and the advice offered here should be evaluated on its merits. The RSSAC has relied on the RSSAC Caucus, a group of DNS experts who have an interest in the Root Server System to perform research and produce this publication. A list of the contributors to this Advisory, references to RSSAC Caucus members’ statement of interest, and RSSAC members’ objections to the findings or recommendations in this Report are at the end of this document.
    [Show full text]
  • (Jake) Feinler
    Oral History of Elizabeth (Jake) Feinler Interviewed by: Marc Weber Recorded: September 10, 2009 Mountain View, California Editor’s note: Material in [square brackets] has been added by Jake Feinler CHM Reference number: X5378.2009 © 2009 Computer History Museum Oral History of Elizabeth (Jake) Feinler Marc Weber: I’m Marc Weber from the Computer History Museum, and I’m here today, September 10th, 2009, with “Jake” Elizabeth Feinler, who was the director of the Network Information Systems Center at SRI. [This group provided the Network Information Center (NIC) for the Arpanet and the Defense Data Network (DDN), a project for which she was the principal investigator from 1973 until 1991. Earlier she was a member of Douglas Engelbart’s Augmentation Research Center (ARC) at SRI [which [housed] the second computer on the Arpanet. It was on this computer that the NIC resided initially.] Jake is also a volunteer here at the museum. [She has donated an extensive collection of early Internet papers to the museum, and has been working on organizing this collection for some time.] Thank you for joining us. Elizabeth (Jake) Feinler: My pleasure. Weber: I really just wanted to start with where did you grow up and what got you interested in technical things or things related to this. Feinler: [Originally I hoped to pursue a career in advertising design, but could not afford the freshman room and board away from home, so I began attending West Liberty State College (now West Liberty University) close to my home. West Liberty was very small then, and the] art department [wasn’t very good.
    [Show full text]
  • CADNA Comments on the IANA Contract
    CADNA Comments Regarding the IANA Contract NTIA’s Request for Comments concerning the IANA functions contract is a welcome and crucial step in ensuring the best future model of Internet operation and governance. As stated in the RFC, the Internet’s integral role in economic growth and innovation necessitates a stable, secure Internet DNS. CADNA is concerned that the current operation of the IANA functions by ICANN could compromise the security of the Internet. The Internet has grown exponentially since ICANN was first awarded the IANA functions contract, and the current re-assessment of the relationship between ICANN and IANA is crucial. Should ICANN retain power to unilaterally both create and implement Internet policy? By holding the IANA functions contract in addition to its policy development functions, ICANN has ultimate authority over all aspects of Internet operation, and is not held accountable for its actions. Decisions made through ICANN’s internal policy-making process are directly inserted into the Internet root as ICANN sees fit. If ICANN truly operated in the best interests of the majority of Internet users, this would not present as great an issue. ICANN’s current policy-making process, however, relies disproportionately on input by domain name registries and registrars instead of the broader Internet community. In light of technical innovation and the growth of the Internet community and market, the IANA functions may be better executed by a variety of technically specialized organizations. Instead of keeping the IANA functions together under ICANN, delegating the technical and administrative functions among other capable entities would ensure accountability in Internet operation.
    [Show full text]