From owner-Big-Internet@munnari.OZ.AU Wed Dec 8 23:52:54 1993 Received: from murtoa.cs.mu.OZ.AU by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA08366; Wed, 8 Dec 1993 20:11:17 +1100 (from owner-Big-Internet@munnari.OZ.AU) Return-Path: Received: from mailing-list by murtoa.cs.mu.OZ.AU (8.5/1.0) id UAA01313; Wed, 8 Dec 1993 20:10:05 +1100 Received: from munnari.oz.au by murtoa.cs.mu.OZ.AU (8.5/1.0) with SMTP id UAA01307; Wed, 8 Dec 1993 20:00:49 +1100 Received: from hsdndev.harvard.edu by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA26245; Wed, 8 Dec 1993 14:24:21 +1100 (from sob@hsdndev.harvard.edu) Date: Tue, 7 Dec 93 22:24:13 -0500 From: sob@hsdndev.harvard.edu (Scott Bradner) Message-Id: <9312080324.AA14452@hsdndev.harvard.edu> To: big-internet@munnari.OZ.AU Subject: IPng White Paper Solicitation IETF IP: next generation area (IPng) chairs Allison Mankin (NRL) Scott Bradner (Harvard University) IPng White Paper Solicitation 1. Introduction The IP: next generation (IPng) area in the IETF is soliciting white papers on topics related to the IPng requirements and selection criteria. All interested parties are invited to submit white papers detailing any specific requirements that they feel an IPng must fulfill or any factors that they feel might sway the IPng selection. An example of the former might be a submission by a representative of a utility company detailing the scaling and addressing features which would be required to service future inclusion of utility meters on the network. An example of the other case might be a paper outlining the potential effect on IPng of some sections of the future network connectivity being provided via wireless networks. At this time, we are not accepting white papers that evaluate specific IPng proposals. This type of document will be accepted after the various proposal documents are deemed to be clear and complete. All white papers will be reviewed in a process described below. As a result of these reviews, each white paper will receive the focused attention of the IPng directorate and the community. The white papers will be used as resource materials by the IPng Area working groups, the directorate, the external review board and the area directors, during the selection process. The deadline for the submission of these white papers is February 1, 1994, though early submission is encouraged. Submit white papers, general or topic questions, and so on, to ipng-wp@harvard.edu. 2. Document Review Process All submitted documents will first be reviewed for clarity by members of the IPng directorate and the external review board. This review may produce suggestions to the author on areas of the document where there may be some confusion as to the meaning. Authors are urged to consider any such suggestions as constructive and to reexamine their text in light of the suggestions. A separate technical review will then be done of the white paper. This review will be conducted within the context of the document. That is, the review still will not make value judgments on the white papers, but will assess technical feasibility. This review may also produce suggestions to the author. The document will be submitted as an Internet-Draft after these reviews have been completed and after whatever (if any) revisions that the author decides to make. After a suitable period of time these documents will be submitted as informational RFCs unless withdrawn by the author. These documents will comprise a part of the historical record of the IPng process. 3. Document Format Requirements All white papers must follow the format requirements listed in RFC1543 and must not exceed 10 pages in length. (The relevant portion of RFC1543 is included in this document as Appendix A.) They should not include the 'status of memo' or 'distribution' sections; these will be added when the documents are posted as Internet Drafts. The reference version of the document must be in ASCII as is current practice with all RFCs. A PostScript version of the document may be submitted in addition to the ASCII version. 4.Outline for IPng Requirements and Concerns White Papers This section details the white paper outline to be followed by someone who would like to express an opinion about the various factors involved in the IPng definition and selection process. Since these documents will be used as resource material by the various IPng working groups, the directorate, the external review board and the area directors, they should be well-focused and give specific references to data supporting their points. Each white paper should begin with an executive summary of the important points of the document. This executive summary should not exceed 1/2 page in length. The white paper should then address the issue or issues that the author feels should be understood during the IPng process. The total document should not exceed 10 pages in length. An author may submit more than one white paper if he or she feels that the level of detailed discussion on each topic warrants it. 4.1 Engineering considerations In past discussions the following issues have been raised as relevant to the IPng selection process. This list is in no particular order. Any or all of these issues may be addressed as well as any other topic that the author feels is germane, but do not exceed the 10 page limit, please. Scaling - What is a reasonable estimate for the scale of the future data networking environment? The current common wisdom is that IPng should be able to deal with 10 to the 12th nodes. Timescale - What are reasonable time estimates for the IPng selection, development and deployment process or what should the timeframe requirements be? This topic is being evaluated by the ALE working group and a copy of all white papers that express opinions about these topics will be forwarded to that group. Transition and deployment - Transition from the current version to IPng will be a complex and difficult process. What are the issues that should be considered The TACIT working group will be discussing these issues and a copy of all white papers that express opinions about these topics will be forwarded to that group. Security - What level and type of security will be required in the future network environment? What features should be in an IPng to facilitate security? Configuration, administration and operation - As networks get larger and more complex, the day to day operational aspects become ever more important. What should an IPng include or avoid in order to minimize the effect on the network operators? Mobile hosts - How important is the proliferation of mobile hosts to the IPng selection process? To what extent should features be included in an IPng to assist in dealing with mobile hosts? Flows and resource reservation - As the data networks begin to get used for an increasing number of time-critical processes, what are the requirements or concerns that affect how IPng should facilitate the use of resource reservations or flows? Policy based routing - How important is policy based routing? If it is important, what types of policies will be used? What requirements do routing policies and potential future global architectures of the Internet bring to IPng? How do policy requirements interact with scaling? Topological flexibility - What topology is anticipated for the Internet? Will the current general topology model continue? Is it acceptable (or even necessary) to place significant topological restrictions on interconnectivity of networks? Applicability - What environment / marketplace do you see for the application of IPng? How much wider is it than the existing IP market? Datagram service - Existing IP service is "best effort" and based on hop-by-hop routed datagrams. What requirements for this paradigm influence the IPng selection? Accounting - How important a consideration should the ability to do accounting be in the selection of an IPng? What, if any, features should be included in an IPng to support accounting functions? Support of communication media - IPv4 can be supported over most known types of communications media. How important is this same flexibility to an IPng? Robustness and fault tolerance - To the extent that the Internet built from IPv4 has been highly fault tolerant, what are ways that IPng may avoid inadvertant decrease in the robustness (since some things may work despite flaws that we do not understand well). Comment on any other ways in which this requirement may affect the IPng. Technology pull - Are there technologies that will pull the Internet in a way that should influence IPng? Can specific strategies be developed to encompass these? Action items - suggested charges to the directorate, working groups or others to support the concerns or gather more information needed for a decision. Appendix A - Formatting Rules (from RFC1543) Note: there are a set of NROFF formatting macros for the following format. Please contact ipng-wp@harvard.edu if you would like to get a copy. 3a. ASCII Format Rules The character codes are ASCII. Each page must be limited to 58 lines followed by a form feed on a line by itself. Each line must be limited to 72 characters followed by carriage return and line feed. No overstriking (or underlining) is allowed. These "height" and "width" constraints include any headers, footers, page numbers, or left side indenting. Do not fill the text with extra spaces to provide a straight right margin. Do not do hyphenation of words at the right margin. Do not use footnotes. If such notes are necessary, put them at the end of a section, or at the end of the document. Use single spaced text within a paragraph, and one blank line between paragraphs. Note that the number of pages in a document and the page numbers on which various sections fall will likely change with reformatting. Thus cross references in the text by section number usually are easier to keep consistent than cross references by page number. From owner-Big-Internet@munnari.OZ.AU Mon Dec 13 23:18:16 1993 Received: from murtoa.cs.mu.OZ.AU by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA02405; Mon, 13 Dec 1993 21:57:17 +1100 (from owner-Big-Internet@munnari.OZ.AU) Return-Path: Received: from mailing-list by murtoa.cs.mu.OZ.AU (8.5/1.0) id VAA07358; Mon, 13 Dec 1993 21:55:51 +1100 Received: from munnari.oz.au by murtoa.cs.mu.OZ.AU (8.5/1.0) with SMTP id VAA07344; Mon, 13 Dec 1993 21:43:25 +1100 Received: from coombs.anu.edu.au by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA29023; Mon, 13 Dec 1993 20:06:15 +1100 (from avalon@coombs.anu.edu.au) Message-Id: <9312130906.29023@munnari.oz.au> Received: by coombs.anu.edu.au (1.37.109.8/16.2) id AA18474; Mon, 13 Dec 1993 20:09:04 +1100 From: Darren Reed Subject: IPng and Multicast To: big-internet@munnari.OZ.AU Date: Mon, 13 Dec 1993 20:09:03 +1000 (EDT) X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 429 As part of the IPng requirements, it must interoperate with IPv4. Does this include multicast IP, and if so, what steps are being undertaken by TUBA and SIPP to ensure that a `group' under IPv4 is the same under IPng (or even on the other side of a wire running IPng) ? Is it planned that groups formed under IPng will/won't be accessible from IPv4 ? Anyone running a SIPP or TUBA host attached to MBONE ? :) Thanks, Darren From owner-Big-Internet@munnari.OZ.AU Sun Dec 19 01:30:48 1993 Received: from murtoa.cs.mu.OZ.AU by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA20887; Sun, 19 Dec 1993 01:30:48 +1100 (from owner-Big-Internet@munnari.OZ.AU) Return-Path: Received: from mailing-list by murtoa.cs.mu.OZ.AU (8.5/1.0) id BAA13451; Sun, 19 Dec 1993 01:29:50 +1100 Received: from munnari.oz.au by murtoa.cs.mu.OZ.AU (8.5/1.0) with SMTP id BAA13437; Sun, 19 Dec 1993 01:17:46 +1100 Received: from ksgbbs.harvard.edu by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA16935; Sat, 18 Dec 1993 07:10:36 +1100 (from keller@ksgbbs.harvard.edu) Received: by ksgbbs.harvard.edu (Smail3.1.28.1 #6) id m0pAlW9-0001kzC; Fri, 17 Dec 93 15:11 EST Message-Id: Subject: II Sourcebook, Version 2.0 To: com-priv@psi.com, members@farnet.org, nren-discuss@psi.com, big-internet@munnari.OZ.AU, ietf@cnri.reston.va.us Date: Fri, 17 Dec 1993 15:11:17 -0500 (EST) From: James Keller - Kennedy School of Government Cc: keller@ksgbbs.harvard.edu (Jim Keller CSIA 6-4042) X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 15164 Information Infrastructure Sourcebook The Information Infrastructure Project at Harvard's Kennedy School of Government announces the publication of the Information Infrastructure Sourcebook, Version 2.0 (ISSN 1073-6921, December, 1993), edited by Brian Kahin. The Sourcebook is designed to provide planners and policymakers a single volume reference on efforts to define and develop policy for a national information infrastructure. It includes historical policy documents, private sector vision statements and position papers, program and project descriptions (all sectors), landmark reports and pending legislation. The Sourcebook is over 800 pages in length, containing approximately 1,500 pages of original material. In assembling the Sourcebook, we have looked for documents that have had or are likely to have an impact on policy development, that are formal in nature, and that deal with information infrastructure at a general rather than topic level. In general, material is reproduced as is, although we have excerpted in the interests of space, relevance, balance and consistency. Because of changes in technology, markets, programs and policies, the Sourcebook will of necessity require supplementation or revision on a regular basis. So we will look for new or updated contributions whenever they become available. Please direct any suggestions for additional material to: James Keller Coordinator, Information Infrastructure Project Kennedy School of Government Harvard University 79 JFK Street Cambridge, MA 02138 Tel: 617-496-4042 E-mail: kellerj@ksg1.harvard.edu If you are interested in receiving the Sourcebook, send a check for $60 payable to Harvard University, or, fax/e-mail credit card information to: Document Imaging Services Office for Information Technology Harvard University 1730 Cambridge Street, room 202 Cambridge, MA 02138 Tel: 617-496-4077 Fax: 617-495-0715 E-mail: yvonne@harvarda.harvard.edu The Sourcebook is also available from Computer Literacy Bookshops in San Jose, CA (408-435-1118) and Tyson's corner, VA (703-734-7771), or via e- mail at info@clbooks.com. ------------------------------------------------------------------------ TABLE OF CONTENTS Information Infrastructure Sourcebook Official Documents Federal Register, Presidential Documents, Executive Order 12864: United States Advisory Council on the National Information Infrastructure, Washington, DC, September 17, 1993. Information Infrastructure Task Force, The National Information Infrastructure: Agenda for Action, Washington, DC, September 15, 1993. Office of Management and Budget, Executive Office of the President, Revision of OMB Circular No. A-130, Washington, DC, July 2, 1993. Federal Coordinating Council for Science, Engineering and Technology, Office of Science and Technology Policy, Executive Office of the President, FCCSET , Initiatives in the FY 1994 Budget, Washington, DC, April 8, 1993. (Introduction and selected excerpts) President William J. Clinton & Vice President Albert Gore, Jr., Technology for America's Economic Growth, A New Direction to Build Economic Strength, White House, Washington, DC, February 22, 1993. (Selected excerpts) Allan D. Bromley, The National Research and Education Network Program: A Report to Congress, OSTP, Washington, DC, December, 1992. (Table of Contents and Executive Summary) Committee on Physical, Mathematical and Engineering Sciences, Federal Coordinating Council for Science, Engineering and Technology, Office of Science and Technology Policy, Grand Challenges 1993: High Performance Computing and Communications , a Supplement to the President's Fiscal Year 1993 Budget, Washington, DC, 1992. Committee on Physical, Mathematical and Engineering Sciences, Federal Coordinating Council for Science, Engineering and Technology, Office of Science and Technology Policy, Grand Challenges: High Performance Computing and Communications, a Supplement to the President's Fiscal Year 1992 Budget, Washington, DC, 1991. U.S. Congress, Public Law 102-94 - High Performance Computing Act of 1991, Washington, DC, December 9, 1991. U.S. Congress, Senate Committee on Commerce, Science and Transportation - Report 102-57, High Performance Computing Act of 1991, U.S. Government Printing Office, Washington DC, May 16,1991. Executive Office of the President, Office of Science and Technology Policy, The Federal High Performance Computing Program, OSTP, Washington, DC, September 8, 1989. (Executive Summary) Office of Science and Technology Policy, Executive Office of the President, A Research and Development Strategy for High Performance Computing, Washington, DC, November, 1987. Vision Statements and Position Papers AT&T, The National Information Infrastructure, A Key to America's Economic Growth and Global Competitiveness, April, 1993. CALS Vision: Economic Growth Through Worldwide Enterprise Integration, CALS Industry Steering Group, National Security Industrial Association, undated. Cable Television Laboratories, Inc., Cable's Role in the "Information Superhighway", Boulder, CO, 1993. The Center for Civic Networking, A Vision of Change: Civic Promise of the National Information Infrastructure, Charlestown, MA, July, 1993. Computer Professionals for Social Responsibility, Serving the Community: A Public Interest Vision of the National Information Infrastructure, October, 1993. Computer Systems Policy Project, Perspectives on the National Information Infrastructure: CSPP's Vision and Recommendations for Action, Washington, DC, 1993. Council on Competitiveness, Vision for a 21st Century Information Infrastructure, Washington, DC, May 1993. Electronic Frontier Foundation, The Open Platform: A Proposal by the Electronic Frontier Foundation for a National Telecommunications Infrastructure, Cambridge, MA & Washington, DC, 1992. Electronic Frontier Foundation, Open Platform Campaign: Public Policy For the Information Age, Washington, DC, November 1, 1993. Electronic Frontier Foundation, Toward a New Public Interest Communications Policy Agenda for the Information Age, Washington, DC, June, 1993. Information Industry Association, Telecommunications Infrastructure Objectives and Implementation Principles, Washington, DC, April, 1993. Information Technology Association of America, Enterprise Integration in the Department of Defense, Arlington, VA, July 1993. Information Technology Association of America, National Information Infrastructure: Industry and Government Roles, Arlington, VA, July 1993. Robert Kahn, National Information Infrastructure Components, Serials Review, Spring and Summer, 1992. National Cable Television Association, Cable Television and America's Telecommunications Infrastructure, Washington, DC, 1993. National Engineering Consortium, The U.S. Information Industry--Creating the 21st Century, March 1993. State Information Policy Consortium, National Information and Service Delivery System: A Vision for Restructuring the Government in the Information Age, 1992. Telecommunications industry CEOs, Policy Statement on NII, March 24, 1993. Program & Project Descriptions - all sectors Robert Aiken, Hans Werner Braun, Peter Ford & Kimberly Claffy, NSF Implementation Plan for Interagency Interim NREN, National Science Foundation, May 1, 1992. American Enterprise Institute for Public Policy Research, Telecommunications Deregulation, Prospectus, Washington, DC, August, 1993. The CENDI Group, an overview, undated. The Corporation for Public Broadcasting, Community-Wide Education and Information Services-Solicitation Guidelines, The Annenberg/CPB Projects, Corporation for Public Broadcasting, Washington, DC, 1993. Defense Information Systems Agency, Defense Information and Infrastructure, Concept and Implementation, Arlington, VA, April, 1993. EINet - Stepping into the Electronic Marketplace: a Technical Overview, Microelectronics and Computer Technology Corporation, undated. Federal Research Internet Coordinating Committee, Department of Energy, Program Plan for the National Research and Education Network, Washington, DC, May 16, 1989. First Cities - Interactive Multimedia Information: Where, When and How You Want It, Microelectronics and Computer Technology Corporation, undated. Iowa Communications Network, Information Highway of the Future, undated. National Computer Board Singapore, Vision of an Intelligent Island-IT 2000 Report, Singapore, March, 1992. The National Initiative for Product Data Exchange, NIST, an overview, 1993. The National Science Foundation, Computer and Information Science and Engineering Directorate, Research on Digital Libraries, Announcement, Washington, DC, 1993. The National Science Foundation, Program Solicitation: Network Access Point Manager, Routing Arbiter, Regional Network Providers and Very High Speed Backbone Network Services Provider for NSFNet and the NREN Program, Washington, DC, National Science Foundation, DC, May 6, 1993. The Office of the Assistant Secretary of Defense, Defense Information Infrastructure: Rationale for Defense Management Report Decision 918, Arlington, VA, 1992. Smart Valley, Inc., An Electronic Community, A Vision of Our Future, May 14, 1993. Technology Reinvestment Project, Program Information Package for Defense Technology Conversion, Reinvestment and Transition Assistance, Arlington, VA, March 10, 1993. (Introduction and selected excerpts) Reports Computer Science and Technology Board, Commission on Physical Sciences, Mathematics and Resources, National Research Council, The National Challenge in Computer Science and Technology, National Academy Press, Washington, DC, 1988. (Chapter 3: The Promise of Infrastructure) Congressional Budget Office, The Congress of the United States, Promoting High-Performance Computing and Communication, U.S. Government Printing Office, Washington DC, June 1993 (Chapter 1,2,4,5) Congressional Research Service, The Library of Congress, The National Information Infrastructure: The Federal Role, Washington, DC, September 24, 1993. National Performance Review, U.S. Government Printing Office, From Red Tape to Results, Creating a Government that Works Better and Costs Less, Step 4: Reengineering to Cut Costs, September 7, 1993. National Research Council, Computer Science and Telecommunications Board, National Collaboratories, National Academy Press, Washington, DC, 1993. (Executive summary and Chapter 1) National Research and Education Network Review Committee of the Computer Science and Technology Board, Commission on Physical Sciences, Mathematics and Resources, National Research Council, Toward a National Research Network, National Academy Press, Washington, DC, 1988. (Executive Summary) National Telecommunications and Information Administration, The NTIA Infrastructure Report - Telecommunications in the Age of Information, Executive Summary, U.S. Department of Commerce, October, 1991. Office of Management and Budget, "The Future Federal Information Infrastructure: The Responsibility of the Federal Information Resources Management Community", excerpted from the Information Resources Plan of the Federal Government, November, 1992. Office of Technology Assessment, U.S. Congress, Advanced Network Technology Communication for the Future, U.S. Government Printing Office, Washington, DC, June, 1993. (Chapter 1,2,3) Office of Technology Assessment, U.S. Congress, Critical Connections: Communication for the Future, U.S. Government Printing Office, Washington, DC, January, 1990. (Chapter 1 - Summary) Office of Technology Assessment, U.S. Congress, Global Standards - Building Blocks for the Future, U.S. Government Printing Office, Washington, DC, March, 1992. (p. 26-30) Office of Technology Assessment, U.S. Congress, Helping America Compete - The Role of Federal Scientific and Technical Information, U.S. Government Printing Office, Washington, DC, July, 1990. (Chapter 1 - Summary) Office of Technology Assessment, U.S. Congress, Informing the Nation, U.S. Government Printing Office, Washington, DC, October, 1988. (Chapter 1 - Summary) Office of Technology Assessment, U.S. Congress, Making Government Work: Electronic Delivery of Federal Services, OTA-TCT-578, U.S. Government Printing Office, Washington, DC, September, 1993. (Chapters 1 and 3) Panel on Information Technology and the Conduct of Research, National Academy of Sciences, Information Technology and the Conduct of Research: The User's View, National Academy Press, Washington, DC, 1989. (Executive Summary) Proceedings of the NREN Workshop, Monterey, California, September 16-18, 1992 (excluding appendices), Computing Research Association/EDUCOM/IEEE U.S. Activities Board, with assistance from the National Science Foundation Grant NCR-921671. Steven R. Rivkin and Jeremy D. Rosner, Shortcut to the Information Superhighway: A Progressive Plan to Speed the Telecommunications Revolution, Progressive Policy Institute Policy Report No. 15, July 1992. (Introduction and Part four: a Progressive Strategy to Build the Fiber-Optic Network) Telecommunications Industries Analysis Project, Beyond Future Shock: The Need for a New Regulatory Response to Technological Change, Executive Summary, New York, New York, November 13, 1993. William Wulf, The National Collaboratory: A White Paper. Unpublished Manuscript. The National Science Foundation, Washington, DC, December 20, 1988. Proposed Legislation The Library of Congress, Selected Legislation in the 103rd Congress Related to Electronic Information Delivery, Washington, DC, undated. U.S. Congress, Improvement of Information Access Act of 1993 - H.R. 629, Washington, DC, January 26, 1993. U.S. Congress, Local Exchange Infrastructure Modernization Act of 1993 - H.R. 1312, Washington, DC, March 11, 1993. U.S. Congress, Communications Competitiveness and Infrastructure Modernization Act of 1993 -H.R. 1504, Washington, DC, March 29, 1993. U.S. Congress, High Performance Computing and High Speed Networking Applications Act of 1993 - H. R. 1757, Washington, DC, July 13, 1993. U.S. Congress, Telecommunications and Information Infrastructure and Public Broadcasting Facilities Assistance Act of 1993 - H.R. 2639, Washington, DC, July 14, 1993. U.S. Congress, Antitrust Reform Act of 1993 - -H.R. 3626, Washington, DC, November 22, 1993. U.S. Congress, National Communications Competition and Information Infrastructure Act of 1993 - H.R. 3636, Washington, DC, November 22, 1993. Senate Committee on Commerce, Science, and Transportation, Additional Views on S. 4, Washington, DC, June 28, 1993. U.S. Congress, National Competitiveness Act of 1993 - S. 4, Washington, DC, January 21, 1993. U.S. Congress, To Establish a System of State-based Electronic Libraries - S.626, Washington, DC, March 22, 1993. U.S. Congress, Telecommunications Infrastructure Act of 1993 - S. 1086, Washington, DC, June 9, 1993.