6/7/2018
`
`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`
`~
`
`August 1994
`
`INTERNET MONTHLY REPORTS
`------------------------
`
`The purpose of these reports is to communicate to the Internet Research
`Group the accomplishments, milestones reached, or problems discovered by
`the participating organizations.
`
` This report is for Internet information purposes only, and is not
` to be quoted in other publications without permission from the
` submitter.
`
`Each organization is expected to submit a 1/2 page report on the first
`business day of the month describing the previous month's activities.
`
`These reports should be submitted via network mail to:
`
` Ann Westine Cooper (Cooper@ISI.EDU)
`
` NSF Regional reports - To obtain the procedure describing how to
` submit information for the Internet Monthly Report, send an email
` message to mailserv@is.internic.net and put "send imr-procedure" in
` the body of the message (add only that one line; do not put a
` signature).
`
`Requests to be added or deleted from the Internet Monthly report list
`should be sent to "imr-request@isi.edu".
`
` Details on obtaining the current IMR, or back issues, via FTP or
` EMAIL may be obtained by sending an EMAIL message to "rfc-
` info@ISI.EDU" with the message body "help: ways_to_get_imrs". For
` example:
`
`To: rfc-info@ISI.EDU
`Subject: getting imrs
`
`help: ways_to_get_imrs
`
`Cooper
`
`Internet Monthly Report
`
`TABLE OF CONTENTS
`
`[Page 1]
`
`August 1994
`
`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`
`1/51
`
`IPR2018-00132
`Riot Games, Inc. v. PalTalk Holdings, Inc.
`Ex. 1041, p. 1
`
`

`

`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`
`6/7/2018
` INTERNET ARCHITECTURE BOARD
`
` INTERNET ENGINEERING REPORTS . . . . . . . . . . . . . . page 3
`
` Internet Projects
`
` ANSNET/NSFNET BACKBONE ENGINEERING . . . . . . . . . . . page 9
` DANTE . . . . . . . . . . . . . . . . . . . . . . . . . . page 12
` INTERNIC. . . . . . . . . . . . . . . . . . . . . . . . . page 15
` ISI . . . . . . . . . . . . . . . . . . . . . . . . . . . page 21
` NEARNET . . . . . . . . . . . . . . . . . . . . . . . . . page 23
` NORTHWESTNET . . . . . . . . . . . . . . . . . . . . . . page 34
` NYSERNET. . . . . . . . . . . . . . . . . . . . . . . . . page 35
` PREPnet . . . . . . . . . . . . . . . . . . . . . . . . . page 38
` UCL . . . . . . . . . . . . . . . . . . . . . . . . . . . page 39
` USER SERVICES REPORT . . . . . . . . . . . . . . . . . . page 40
`
` CALENDAR OF EVENTS . . . . . . . . . . . . . . . . . . . . . page 51
` Rare List of Meetings . . . . . . . . . . . . . . . . . . page 54
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Cooper [Page 2]
`
`Internet Monthly Report August 1994
`
`
`
`INTERNET RESEARCH REPORTS
`-------------------------
`
`INTERNET ENGINEERING REPORTS
`----------------------------
`
` IETF Monthly Report for August, 1994
`
` 1. The 30th meeting of the IETF was held in Toronto, Ontario,
` Canada from July 25 through July 29, 1994. The meeting was
`
`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`
`2/51
`
`IPR2018-00132
`Riot Games, Inc. v. PalTalk Holdings, Inc.
`Ex. 1041, p. 2
`
`

`

`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`6/7/2018
` hosted by The University of Toronto. There were just over 700
` attendees, and over 70 Working Groups, BOFs, and directorate
` meetings were held during the week.
`
` The next IETF meeting will be in San Jose, California from
` December 5-9, and is being hosted by Sun. Following that, the
` IETF will be meeting in Danvers, Massachusetts (a suburb of
` Boston) from April 3-7, 1995. This meeting is being co-hosted
` by FTP Software and NEARNet.
`
` 2. We are in the final stages of arranging the summer IETF meeting
` which will be held in Stockholm, Sweden, from July 17-21, 1995.
` Our hosts for the second European IETF meeting is NORDUnet. When
` all the arrangements have been made, a notice will be sent to
` the IETF Announcement list.
`
` Remember that information on future IETF meetings (both
` tentative and confirmed), can be always be found in the file
` 0mtg-sites.txt which is located on the IETF shadow directories.
` This and other IETF information can also be viewed via the
` World-Wide Web. The URL for the IETF Home page is
`
` http://www.ietf.cnri.reston.us/home.html
`
` 3. The IESG approved or approved the following two Protocol Actions
` during the month of August, 1994:
`
` o The PPP Multilink Protocol (MP) be published as a Proposed
` Standard.
`
` o Transport Multiplexing Protocol (TMux) be published as a
` Proposed Standard.
`
`
` 4. The IESG issued ten Last Calls to the IETF during the month of
` August, 1994:
`
`
`
`
`Cooper [Page 3]
`
`Internet Monthly Report August 1994
`
`
` o INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4
` <draft-ietf-imap-imap4-05> for consideration as a Proposed
` Standard.
`
` o IMAP4 Authentication mechanisms <draft-ietf-imap-auth-01>
` for consideration as a Proposed Standard.
`
` o IMAP4 COMPATIBILITY WITH IMAP2 AND IMAP2BIS
` <draft-ietf-imap-compat-00> for consideration as an
` Informational Document.
`
` o DISTRIBUTED ELECTRONIC MAIL MODELS IN IMAP4
` <draft-ietf-imap-model-00> for consideration as an
` Informational Document.
`
` o RIP Version 2 Carrying Additional Information
` <draft-ietf-ripv2-protocol-01> for consideration as a Draft
` Standard.
`
` o RIP Version 2 MIB Extension <draft-ietf-ripv2-mibext2-02>
`
`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`
`3/51
`
`IPR2018-00132
`Riot Games, Inc. v. PalTalk Holdings, Inc.
`Ex. 1041, p. 3
`
`

`

`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`6/7/2018
` for consideration as a Draft Standard.
`
` o RIP Version 2 Protocol Analysis
` <draft-ietf-ripv2-protocol-analysis-01> for consideration as
` an Informational Document.
`
` o RIP Version 2 Protocol Applicability Statement
` <draft-ietf-ripv2-protocol-applic-01> for consideration as
` a Draft Standard.
`
` o Requirements for Internet gateways <RFC 1009> for comments
` to reclassifying as Historic.
`
` o Exterior Gateway Protocol formal specification <RFC 0904> for
` comments to reclassifying as Historic.
`
`
` 5. Two Working Groups were created during this period:
`
` New Internet Routing and Addressing Architecture (nimrod)
` Inter-Domain Routing (idr)
`
` Additionally, seven Working Groups were concluded:
`
`
` Border Gateway Protocol (bgp)
` User Documents Revisions (userdoc2)
` OSI IDRP for IP Over IP (ipidrp)
`
`
`
`Cooper [Page 4]
`
`Internet Monthly Report August 1994
`
`
` Networked Information Retrieval (nir)
` Modem Management (modemmgt)
` ATM MIB (atommib)
` Relational Database Management Systems MIB (rdbmsmib)
`
`
` Note that the Inter-Domain Routing (idr) Working Group is
` actually the merging of the bgp and ipidrp working groups.
`
`
` 6. A total of 51 Internet-Draft actions were taken during the month
` of August, 1994:
`
` (Revised draft (o), New Draft (+) )
`
` (idr) o BGP4/IDRP for IP---OSPF Interaction
` <draft-ietf-idr-bgp4ospf-interact-07.txt>
` (wnils) o Architecture of the Whois++ Index Service
` <draft-ietf-wnils-whois-03.txt>
` (avt) o Packetization of H.261 video streams
` <draft-ietf-avt-video-packet-02.txt>
` (iiir) o Resource Transponders
` <draft-ietf-iiir-transponders-02.txt>
` (rolc) o NBMA Next Hop Resolution Protocol (NHRP)
` <draft-ietf-rolc-nhrp-02.txt>
` (iiir) o A Vision of an Integrated Internet Information
` Service <draft-ietf-iiir-vision-02.txt>
` (uri) o Uniform Resource Locators (URL)
` <draft-ietf-uri-url-06.txt>
`
`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`
`4/51
`
`IPR2018-00132
`Riot Games, Inc. v. PalTalk Holdings, Inc.
`Ex. 1041, p. 4
`
`

`

`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`6/7/2018
` (uri) o Uniform Resource Names
` <draft-ietf-uri-resource-names-02.txt>
` (mhsds) o Introducing Project Long Bud: Internet Pilot Project
` for the Deployment of X.500 Directory Information
` in Support of X.400 Routing
` <draft-ietf-mhsds-long-bud-intro-02.txt>
` (none) o Definitions of Managed Objects for the Node in Fibre
` Channel Standard using SMIv2
` <draft-chu-fibre-channel-mib-02.txt>
` (none) o Mapping between X.400 P772 and RFC-822
` <draft-onions-x400p772-822-mapping-02.txt>
` (mailext) o SMTP Service Extensions for Transmission of Large
` and Binary MIME Messages
` <draft-ietf-mailext-smtp-binary-05.txt>
` (ripv2) o RIP Version 2 MIB Extension
` <draft-ietf-ripv2-mibext2-02.txt>
` (none) + Simple Object Look-up protocol (SOLO)
` <draft-huitema-solo-00.txt>
` (sipp) o IPv6 Authentication Header
`
`
`
`Cooper [Page 5]
`
`Internet Monthly Report August 1994
`
`
` <draft-ietf-sipp-ap-04.txt>
` (none) o Instructions to RFC Translators
` <draft-ohta-translation-instr-01.txt>
` (imap) o INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4
` <draft-ietf-imap-imap4-05.txt>
` (none) o Requirements for Uniform Resource Names
` <draft-sollins-urn-02.txt>
` (none) o Procedures for Formalizing, Evolving, and
` Maintaining the Internet X.500 Directory Schema
` <draft-howes-x500-schema-02.txt>
` (iab) o Proposed Cooperative Agreement Between the Internet
` Society and ISO/IEC JTC 1/SC 6
` <draft-iab-mou2jtc1-03.txt>
` (wnils) o Architecture of the WHOIS++ service
` <draft-ietf-wnils-whois-arch-01.txt>
` (printmib) o Printer MIB <draft-ietf-printmib-printer-mib-03.txt>
` (uri) o Functional Requirements for Internet Resource
` Locators <draft-ietf-uri-irl-fun-req-01.txt>
` (none) o POP3 AUTHentication command
` <draft-myers-pop3-auth-01.txt>
` (mailext) o SMTP 521 reply code
` <draft-ietf-mailext-smtp-521-01.txt>
` (none) + Representing Service Quality In a Multi-Service
` Internet <draft-davin-qosrep-00.txt>
` (ospf) + OSPF MD5 Authentication <draft-ietf-ospf-md5-00.txt>
` (none) + Service Management For a Next-Generation Internet
` Protocol <draft-davin-rsvfms-00.txt>
` (wnils) + How to interact with a Whois++ mesh
` <draft-ietf-wnils-whois-mesh-00.txt>
` (notary) + Multipart/Report
` <draft-ietf-notary-mime-report-00.txt>
` (none) + Communicating Presentation Information in Internet
` Messages: The Content-Disposition Header
` <draft-dorner-content-header-00.txt>
` (none) + Simple Secure DNS <draft-ohta-simple-dns-00.txt>
` (none) + Dienst, A Protocol for a Distributed Digital
` Document Library
` <draft-lagoze-dienst-protocol-00.txt>
`
`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`
`5/51
`
`IPR2018-00132
`Riot Games, Inc. v. PalTalk Holdings, Inc.
`Ex. 1041, p. 5
`
`

`

`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`6/7/2018
` (imap) + DISTRIBUTED ELECTRONIC MAIL MODELS IN IMAP4
` <draft-ietf-imap-model-00.txt>
` (mailext) + Tags for the identification of languages
` <draft-ietf-mailext-lang-tag-00.txt>
` (none) + An Architecture for IPv6 Unicast Address Allocation
` <draft-rekhter-ipng-arch-IPv6-addr-00.txt>
` (none) + Summary of Mail and Messaging Standards
` <draft-robinson-mail-summary-00.txt>
` (none) + Relationship of Telex Answerback Codes to Internet
` Domains (2nd Revision)
`
`
`
`Cooper [Page 6]
`
`Internet Monthly Report August 1994
`
`
` <draft-robinson-newtelex-00.txt>
` (pem) + Privacy Enhancement for Internet Electronic Mail:
` Part V: ANSI X9.17-Based Key Management
` <draft-ietf-pem-ansix9.17-00.txt>
` (none) + Bitmap, Cursor and Icon Image Formats
` <draft-robinson-bitmap-00.txt>
` (bgp) + Guidelines for creation, selection, and registration
` of an Autonomous System (AS)
` <draft-ietf-bgp-autosys-guide-00.txt>
` (none) + A Convention for Human-Readable 128-bit Keys
` <draft-mcdonald-readable-keys-00.txt>
` (mailext) + SMTP Service Extension for Command Pipelining
` <draft-ietf-mailext-pipeline-00.txt>
` (mailext) + SMTP Service Extension for Checkpoint/Restart
` <draft-ietf-mailext-checkp-00.txt>
` (none) + ARP over HIPPI <draft-renwick-hippiarp-00.txt>
` (none) + IP over HIPPI <draft-renwick-hippiip-00.txt>
`
` (iiir) + Using the Z39.50 Information Retrieval Protocol in
` the Internet Environment
` <draft-ietf-iiir-z3950-00.txt>
` (none) + Definitions of Managed Objects for the HIPPI
` Interface Type <draft-renwick-hippimib-00.txt>
` (none) + Telnet Authentication: Simple-Strong Authentication
` <draft-schoch-telnet-ssa-00.txt>
` (uri) + Relative Uniform Resource Locators
` <draft-ietf-uri-relative-url-00.txt>
` (none) + Recommendations for OSI NSAP usage in IP6
` <draft-carpenter-ip6-nsap-map-00.txt>
`
`
` 7. There were 33 RFC's published during the month of August, 1994:
`
` RFC St WG Title
` ------- -- -------- -------------------------------------
` RFC1650 PS (ifmib) Definitions of Managed Objects for the
` Ethernet-like Interface Types using SMIv2
` RFC1664 E (x400ops) Using the Internet DNS to Distribute
` RFC1327 Mail Address Mapping Tables
` RFC1666 PS (snanau) Definitions of Managed Objects for SNA
` NAUs using SMIv2
` RFC1667 I (none) Modeling and Simulation Requirements for
` IPng
` RFC1668 I (none) Unified Routing Requirements for IPng
` RFC1669 I (none) Market Viability as a IPng Criteria
` RFC1670 I (none) Input to IPng Engineering Considerations
` RFC1671 I (none) IPng White Paper on Transition and Other
`
`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`
`6/51
`
`IPR2018-00132
`Riot Games, Inc. v. PalTalk Holdings, Inc.
`Ex. 1041, p. 6
`
`

`

`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`6/7/2018
` Considerations
`
`
`
`Cooper [Page 7]
`
`Internet Monthly Report August 1994
`
`
` RFC1672 I (none) Accounting Requirements for IPng
` RFC1673 I (none) Electric Power Research Institute
` Comments on IPng
` RFC1674 I (none) A Cellular Industry View of IPng
` RFC1675 I (none) Security Concerns for IPng
` RFC1676 I (none) INFN Requirements for an IPng
` RFC1677 I (none) Tactical Radio Frequency Communication
` Requirments for IPng
` RFC1678 I (none) IPng Requirements of Large Corporate
` Networks
` RFC1679 I (none) HPN Working Group Input to the IPng
` Requirements Solicitation
` RFC1680 I (none) IPng Support for ATM Services
` RFC1681 I (none) On Many Addresses per Host
` RFC1682 I (none) IPng BSD Host Implementation Analysis
` RFC1683 I (none) Multiprotocol Interoperability In IPng
` RFC1684 I (none) Introduction to White Pages services
` based on X.500
` RFC1685 I (none) Writing X.400 O/R Names
` RFC1686 I (none) IPng Requirements: A Cable Television
` Industry Viewpoint
` RFC1687 I (none) A Large Corporate User's View of IPng
` RFC1688 I (none) IPng Mobility Considerations
` RFC1689 I (nir) A Status Report on Networked Information
` Retrieval: Tools and Groups
` RFC1690 I (none) Introducing the Internet Engineering and
` Planning Group (IEPG)
` RFC1691 I (none) The Document Architecture for the Cornell
` Digital Library
` RFC1692 PS (none) Transport Multiplexing Protocol (TMux)
` RFC1694 DS (ifmib) Definitions of Managed Objects for SMDS
` Interfaces using SMIv2
` RFC1695 PS (atommib) Definitions of Managed Objects for ATM
` Management Version 8.0 using SMIv2
` RFC1696 PS (modemmgt) Modem Management Information Base (MIB)
` using SMIv2
` RFC1697 PS (rdbmsmib) Relational Database Management System
` (RDBMS) Management Information Base (MIB)
` using SMIv2
`
` St(atus): ( S) Internet Standard
` (PS) Proposed Standard
` (DS) Draft Standard
` ( E) Experimental
` ( I) Informational
`
` Steve Coya (scoya@nri.reston.va.us)
`
`
`
`
`Cooper [Page 8]
`
`Internet Monthly Report August 1994
`
`
`
`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`
`7/51
`
`IPR2018-00132
`Riot Games, Inc. v. PalTalk Holdings, Inc.
`Ex. 1041, p. 7
`
`

`

`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`
`6/7/2018
`INTERNET PROJECTS
`-----------------
`
`ANSNET/NSFNET BACKBONE ENGINEERING
`----------------------------------
`
` NETWORK STATUS SUMMARY
` ----------------------
`
` ANSnet total packet traffic increased by about 13% in August'94.
` An increase in the ANSnet forwarding table size of 5.5% was
` observed during the month of August.
`
` AUGUST BACKBONE TRAFFIC STATISTICS
` ----------------------------------
`
` The total inbound packet count for the ANSnet (measured using
` SNMP interface counters) was 70,954,833,675 on T3 ENSS
` interfaces, up 13.5% from July. The total packet count into the
` network including all ENSS serial interfaces was 71,692,393,856 up
` 13.0% from July.
`
` ROUTER FORWARDING TABLE STATISTICS
` ----------------------------------
`
` The maximum number of destinations announced to the ANSnet
` during August was 18,846 up 5.56% from July.
`
` The number of network destinations configured for
` announcement to the ANSnet but never announced (silent nets)
` during August was 17,153.
`
` BGP-4/CIDR DEPLOYMENT STATUS
` ----------------------------
`
` As of September 7th '94, we have observed the withdrawal of
` 7,714 class based destinations from the ANSnet router forwarding
` tables that are now represented by 1,518 configured aggregates.
` Among these configured aggregates:
`
` 1,319 of these are top-level aggregates (not nested in another
` aggregate).
`
` 1,081 of these are actively announced to ANSnet.
`
` 885 of these have at least one subnet configured (the other
` 196 may be saving the Internet future subnet announcements).
`
`
`
`
`Cooper [Page 9]
`
`Internet Monthly Report August 1994
`
`
` 762 of these have resulted in the withdrawal of at least one
` configured more specific route.
`
` 742 of these have resulted in the withdrawal of 50% of their
` configured more specific routes.
`
` 717 of these have resulted in the withdrawal of most (80%+)
` of their more specific routes.
`
`
`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`
`8/51
`
`IPR2018-00132
`Riot Games, Inc. v. PalTalk Holdings, Inc.
`Ex. 1041, p. 8
`
`

`

`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`6/7/2018
` For up-to-date information is available from merit.edu:
` pub/nsfnet/cidr/cidr-savings.
`
` For further details on these CIDR aggregates, see
` merit.edu:pub/nsfnet/cidr/nestings.announced for full listings.
`
` ROUTING STABILITY MEASURED ON THE T3 NETWORK
` --------------------------------------------
`
` Internal routing stability measurements are made by monitoring
` short term disconnect times (disconnects of five minutes duration
` or less). This is intended as a measure of overall system
` stability rather than complete connectivity.
`
` The month of August resulted in greater backbone stability than any
` other month during the year. Some instability was experienced due
` to planned maintenance required to install new router operating
` system software, along with unexpected problems with a gated bug
` during reconfiguration.
`
` MONTH overall excluding configs
` ------ ------- -----------------
` 1993
` January 99.1% 99.5%
` February 99.0% 99.5%
` March 97.5% 99.1%
` April 96.1% 97.2%
` May 97.4% 98.0%
` June 95.5% 96.6%
` July 97.3% 97.7%
` August 97.5% 97.9%
` September 98.1% 98.5%
` October 98.0% 98.3%
` November 97.2% N/A
` December 96.6% N/A
` 1994
` January 98.7% N/A
` February 96.6% N/A
` ... data collection had to be rewritten for gated ...
`
`
`
`Cooper [Page 10]
`
`Internet Monthly Report August 1994
`
`
` June 99.5% N/A
` July 98.7% N/A
` August 99.7% N/A
`
` Monthly histograms of the number of nodes experiencing instability
` follows. August was the fist month in 1994 where all AS690 nodes
` experienced less than 15 minutes of accumulated instability. Note
` that about 1/3 of the nodes experienced no instability at all and
` are not included in the count.
`
` MONTH >5 hr >2 hr > 1hr >30 min >15 min <= 15min
`
` <98.7% <99.7% <99.87% <99.93% <99.97% >=99.97%
`
` ------------------------------------------------------------
` January 0 0 1 8 19 55
` February 0 0 1 24 19 41
` March 0 4 18 23 23 22
`
`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`
`9/51
`
`IPR2018-00132
`Riot Games, Inc. v. PalTalk Holdings, Inc.
`Ex. 1041, p. 9
`
`

`

`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`6/7/2018
`3 13
`12
`57
`2
`2
` April
`4 33 32
`15
`5
`0
` May
`3 21 35 18
`12
`3
` June
`0 12 28 44
`6
`1
` July
`1
`5 28 21
`17
`15
` August
` September 1 38 25 10
`4
`13
` October 0
`3
`3 10
`25
`50
` November 1
`2 15 25
`24
`26
` December 0
`8 24 46
`9
`3
` January 0
`0
`4
`9
`15
`54
` February 0
`4
`6 23
`40
`20
`...
` June
` July
` Aug
`
`0
`0
`0
`
`5
`0
`0
`7 55 11
`0
`0
`0
`
`5
`10
`0
`
`67
`7
`67
`
` NOTABLE OUTAGES FOR AUGUST '94
` ------------------------------
`
` E146 (ARPA) suffered an extended power outage on 08/14. E179
` (Sandia) suffered an extended power outage on 08/19.
`
` Jordan Becker <becker@ans.net>
`
`Cooper
`
`Internet Monthly Report
`
`DANTE
`-----
`
`[Page 11]
`
`August 1994
`
` __________________________________________________________________
`* * A bi-monthly electronic news bulletin
`* * reporting on the activities of DANTE,
`the company that provides international
`*
`* network services for the European
` THE WORKS OF D A N T E community.
`
` No.5, August 1994 Editor: Josefien Bersee
` __________________________________________________________________
`
` 2 MBPS EUROPANET CONNECTION FOR NORDUNET
`
` Since 1 July 1994 NORDUnet, the network of the Nordic countries,
` has had a 2 Mbps connection to EuropaNET. Belgium, Germany, Italy,
` The Netherlands, Spain and the United Kingdom already had 2 Mbps
` connections.
`
` NEW EBONE GATEWAY ARRANGEMENT
`
` DANTE has organised a new interconnect arrangement between Ebone
` and EuropaNET, which has been in place since 1 July 1994. The
` arrangement enables France to communicate with the rest of Europe
` and vice versa; the interconnection has a capacity of 512 kbps.
` CERN (Geneva), as one of the locations where EuropaNET and Ebone
`
`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`
`10/51
`
`IPR2018-00132
`Riot Games, Inc. v. PalTalk Holdings, Inc.
`Ex. 1041, p. 10
`
`

`

`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`6/7/2018
` are both present, is used as the actual point of interconnection
` but traffic flows in and out of EMPB through DANTE's PoP in
` Amsterdam.
`
` CONNECTIVITY IN CENTRAL AND EASTERN EUROPE
`
` The contract between the European Commission and PTT Telecom to
` provide EMPB (EuropaNET) connections to the Czech Republic,
` Hungary, and Romania under the EC PHARE Programme was extended from
` 31 December 1993 to 30 June 1994. Since 1 July PTT Telecom has been
` continuing the service which is being funded from the remaining
` PHARE budget. However, this funding runs out very shortly.
`
` DANTE has been lobbying both PTT Telecom and the EC to the effect
` that termination of the services (at least without a replacement
` being put in place) would be very bad. PTT Telecom has now received
` a letter from the EC which gives them enough reassurance that
` payment will eventually be made from the PHARE 1994 Programme to
` keep the present services going.
`
` Both the technical and the funding aspects of the longer term
`
`Cooper
`
`Internet Monthly Report
`
`[Page 12]
`
`August 1994
`
` continuation of these services will be taken up again once the
` management contract for the PHARE 1994 Programme of support for
` research networking has been awarded by the EC.
`
` US CONNECTIVITY ISSUES
`
` DANTE will locate the US end of its new 8 Mbps link from Amsterdam
` to the US at the Network Access Point (NAP) in New York which is
` set up as a result of the new arrangements which have been put in
` place by NSF. Another consequence of NSF's changes is that the
` trans-(US-)continental broadband network is not available for
` general use. As a consequence, DANTE and other non-US organisations
` will have to make new arrangements with US service providers for
` distribution of their traffic with the US and for transit between
` Europe and Asia/Pacific (see also 'Some impressions from the 30th
` IETF').
`
` The actual form of the NAP connection still has to be decided on:
` the choice will be either to obtain a direct connection or via a US
` service provider.
`
` CONNECTION TO KOREA IN PLACE
`
` A 64 kbps line between Europe and Korea has become operational on
` 23 August 1994. The line provides a direct link between KREONet
` (Korea Research Environment Open Network), the Korean national R&D
` network and EuropaNET. DANTE was awarded the contract to organise
` the connection under the EC EKORN project.
`
` KREONet, one of five government networks in Korea, was launched in
` 1988 and connects all the major university, government and
` commercial research institutes. It provides the Korean research
` community with the 'usual' services such as e-mail, file transfer,
` remote login etc. DANTE's partner in setting up the connection has
` been SERI (Systems Engineering Research Institute), the
` organisation that operates, manages and develops KREONet.
`
`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`
`11/51
`
`IPR2018-00132
`Riot Games, Inc. v. PalTalk Holdings, Inc.
`Ex. 1041, p. 11
`
`

`

`6/7/2018
`
`https://www.rfc-editor.org/in-notes/museum/imr/imr9408.txt
`
` EUROCAIRN ACTVITY TAKES OFF
`
` Work on the EuroCAIRN Study Report has started. A contract for this
` Project, to specify requirements and options for the setting up of
` a Superhighway for the European research community, was awarded to
` DANTE in May 1994. The Project team consists of DANTE employees
` complemented with a group of external specialists: Robert Cooper
` (UKERNA/SuperJANET), Bernhard Stockman (KTH, Stockholm), Maria
` Pallares and Chris Broomfield. Istvan Tetenyi, from HUNGARNET
` (Hungary) will be joining from October 1994.
`
`Cooper
`
`Internet Monthly Report
`
`[Page 13]
`
`August 1994
`
` DANTE is organising a meeting with representatives of the national
` networks in November 1994 to present the findings of the
` preliminary report. The final version of the report will be
` delivered in March 1995.
`
` SOME IMPRESSIONS FROM THE 30TH IETF, TORONTO - MICHAEL BEHRINGER
`
` As the title of this article suggests, this is not meant to be a
` precise report on the IETF, but rather an informal gathering of a
` few personal impressions.
`
` The most interesting decision that was to be made at this summer
` IETF 1994 was concerning the next generation of the Internet
` Protocol. Due to the current growth rate of routing tables, and the
` problems of running out of IP address space, the current version of
` the Internet Protocol has to be either updated or completely re-
` designed. Three proposals have been discussed as IP next
` generation, TUBA, CATNIP and SIPP (I won't explain the details
` here). Although it was not clearly stated during the Plenary
` Session, it was obvious that the choice for IPng went to SIPP. The
` "Simple Internet Protocol Plus" is supposed to tackle a whole range
` of problems experienced with the current version 4 of the IP, for
` example security aspects.
`
` Another important issue that the Internet has to face durin