Network Working Group Philip J. Nessser II Editor draft-ietf-2000-issue-00.txt Nesser & Nesser Consulting Internet Draft July 1997 The Internet and the Millenium Problem (Year 2000) Status of this Memo This document is an Internet Draft. Internet Drafts are working documents of the Internet Engineering Task Force (IETF), its Areas, and its Working Groups. Note that other groups may also distribute working documents as Internet Drafts. Internet Drafts are draft documents valid for a maximum of six months. Internet Drafts may be updated, replaced, or obsoleted by Internet Drafts are draft documents valid for a maximum of six months. Internet Drafts may be updated, replaced, or obsoleted by other documents at any time. It is not appropriate to use Internet Drafts as reference material or to cite them other than as a "working draft" or "work in progress". Please check the I-D abstract listing contained in each Internet Draft directory to learn the current status of this or any other Internet Draft. Abstract The Year 2000 Working Group(WG) has conducted an investigation into the millenium problem as it regards Internet related protocols. This investigation only targeted the protocols as documented in the Request For Comments Series (RFCs). This investigation discovered little reason for concern with regards to the functionality of the protocols. A few minor cases of older implementations still using two digit years (ala RFC 850) were discovered, but almost all Internet protocols were given a clean bill of health. Several cases of "period" problems were discussed where a time field would "roll over" as the size of field was reached. In particular, there are several protocols which have 32 bit signed integer representations of the number of seconds since January 1, 1970 which will turn negative at Tue Jan 19 03:14:07 GMT 2038. Areas whose protocols will be effected by such problems have been notified so that new revisions will remove this limitation. Introduction According to the trade press billions of dollars will be spend the upcoming three years on the year 2000 problem, also called the millenium problem (though the third millenium will only start in 2001). This problem consists of the fact that many software packages and some protocols use a two digit field for the year in a date field. Most of the problems seem to be in administrative and financial programs, or in the hardcoded microcomputers found in electronic equipment. A lot of organizations are now starting to make an inventory of which software and tools they use will suffer from the millenium problem. ..and the Internet With the increasing popularity of the Internet, more and more organizations start to use the Internet as a serious business tool. This means that most organizations will want to analyse the millenium problems due to the use of Internet protocols and popular Internet software. In the trade press the first articles suggest that the Internet will collapse at midnight the 31st of december 1999. To counter these suggestions (that are obviously wrong) and to avoid that all over the Internet people will redo the same inventory over and over again the WG is to make an inventory of all important Internet protocols and their most popular implementations with respect to the millenium problem. Only software and protocols directly related to the Internet will be considered. The editor of this document would like to acknowledge the critical contributions of the follow for direct performance of research and the provision of text: Alex Latzko, Robert Elz, Erik Huizer, Gillian Greenwood, Barbara Jennings, R.E. (Robert) Moore, David Mills, Lynn Kubinec, Chris Newman, Erik-Jan Bos, Paul Hoffman, and Rick H. Wesson. The pace with which this group has operated has only been achievable by the intimate familiarity of the contributors with the protocols and ready access to the collective knowledge of the IETF. Disclaimer This RFC does not pretend to be complete. It is a best effort attempt to do an analysis of hundreds of protocols. Organizations should not attempt to claim any legitimacy or approval as a result of this investigation. Any proposed solutions are only that: proposed. Formal engineering should take place before any solution is adopted. The efforts have concentrated on the identification of potential problems, rather than solutions. Types of Year 2000 Problems o Description of the year 2000 problems and when they will occur Methodology The first task was dividing the types of RFC's into logical groups rather than the strict numeric publishing order. Fifteen specific areas were identified. They are: "Autoconfiguration" , "Directory Services", "Disk Sharing", "Games and Chat" ,"Information Services & File Transfer", "Internet & Network Layer", "Mail", "NTP", "Name Serving", "Network Management", "News", "Real Time Services", "Routing", "Security", and "Virtual Terminal". In addition to these categories many hundreds of RFC's were immediately eliminated because of the type of content. That is not to say that all Informational RFC's were not considered, many did contain some technical content or overview which demanded scrutiny. Each area was assigned to a team for investigation. Although each team used whatever additional investigation techniques which seemed appropriate (including completely reading each RFC, and in some cases the source code for the reference implementation) at minimum each team used an automatic scanning system to search for the following items (case insensitively) in each RFC: - date - GMT - UTCTime - year - yy (that is not part of yyyy) - two-digit, 2-digit, 2digit - century - 1900 & 2000 Note that all of these strings except "UTCTime" may occur in conjunction with a date format that accommodates the Year 2000 crossing, as well as with one that does not. So "hits" on these string do not necessarily indicate Year 2000 problems: they simply identify elements that need to be examined. After the documents were scanned, therefore, each "hit" was examined individually. Those that cause no Year 2000 problems (e.g., those that encode the year as a two-byte integer, or as a four-character display string) are not discussed here. Those that do cause Year 2000 problems are identified in this document, and the nature and impact of the problems they cause are described. Summary of Possible Solutions o Summary of possible solutions and timelines for those solutions Inventory of Internet Protocols o Inventory of the year 2000 problem in the most popular Internet protocols and their most popular implementations o Suggested solutions to the problems noted in the inventory Autoconfiguration After examining the bootp rfcs, and going over the code there should be no y2k problem with it. All times are referenced as a 32bit integer in seconds of UTC time. Directory Services After reviewing all Directory Service related RFCs see atached list at the bottom of this note, There are no serious Year 2000 Issues with Directory Service RFCs. There are several DS (Directory Service) RFCs that specify the use of UTC Date/Time Strings. Of the 48 DS related RFCs only 9 made mention of Dates. Of those most specified dates in uTCTimeSyntax which has the option of representing dates in either 2 or 4 year formats. The following DS RFCs mentioned the use of Dates: rfc1274.txt - Refrences UTC date/time rfc1276.txt - Refrences UTC date/time for version control. rfc1488.txt - Refrences UTC Time as printable strings. rfc1608.txt - Refers to uTCTimeSyntax rfc1609.txt - Refers to uTCTimeSyntax rfc1778.txt - Refers to uTCTimeSyntax rfc1714.txt * supports YY year and YYYY year date expressions. rfc1913.txt * Timestamps are GMT, in the format: YYYYMMDDHHMM rfc1834.txt X Specifys a Date container, but no format. RFCs that mentioned UTC Time or made refrence to uTCTimeSyntax could fail to be Y2K complient. These should be updated to specify the four year version of uTCTimeSyntax rather than giving the option of using a two year date represnetation. The RFCs that fall into this catagory are marked with a dash (-) above. RFCs with unusual date specifications are marked with an asterick (*) above. These RFCs specify their own date format. Both of these support Y2K complient dates. RFC1714 (RWhois) specifies date formats that are not Y2K complient, but italso support dates that are. Implementers of the RWhois protocol should onlyuse the %MY4 format RFC1834 (Whois++) requires the use of dates, but it didn't specify the format, syntax, or representation of the date string to be used. Disk Sharing The Network File System protocol provides a method for file sharing across disks on a TCP/IP network. The reference to time in this protocol is to set the length of time to wait for the first try of a request; timeout. Timeout time in the NFS protocol is calculated rather than preserved. As such, is not affected by the date. SUN Microsystems states that there is known problem associated with this protocol and the millennium change. Games and Chat Information Services & File Transfer HTTP The main IETF standards-track document on the HTTP protocol is RFC2068 on HTTP 1.1. It notes that historically three different date formats have been used, and that one of them uses a two-digit year field. In section 3.3.1 it requires HTTP 1.1 implementations to generate this RFC1123 format: Sun, 06 Nov 1994 08:49:37 GMT ; RFC 822, updated by RFC 1123 instead of this RFC850 format: Sunday, 06-Nov-94 08:49:37 GMT ; RFC 850, obsoleted by RFC 1036 Unfortunately, many existing servers, serving on the order of one fifth of the current HTTP traffic, send dates in the ambiguous RFC850 format. Section 19.3 of the RFC2068 says this: o HTTP/1.1 clients and caches should assume that an RFC-850 date which appears to be more than 50 years in the future is in fact in the past (this helps solve the "year 2000" problem). This avoids a "stale cache" problem, which would cause the user to see out-of-date data. But to avoid unnecessary delays and bandwidth indicated in Scenario 2 below, this should be extended to say that a date which appears to be more than 50 years in the past may be assumed to be in the future, if a future date is legal for that field. Scenario 3 indicates that servers may also want to follow these rules. Here is some more background and justification for these arguments. The following headers use full dates: HTTP/1.0: Date: Expires: # can be in the future If-Modified-Since: # required to be in the past Last-Modified: # required to be in the past Retry-After: # can be in the future, also takes # relative time - number of seconds HTTP/1.1: If-Range: If-Unmodified-Since: # required to be in the past Note that clock skew between hosts can lead to confusion here - see the RFC for details. Here are some scenarios of the implications of RFC850 dates, which include stale caches, unnecessary requests for things which are validly cached, delays for the user, extra bandwidth, and presenting incorrect information to the user. Some cases involve comparisons with the current time, and others may involve comparisons between dates from different sources. The abbreviation "/99" is used to imply an RFC850 date with the value "99" for the year. RFC850 date from server Scenario 1: If a client gets an Expires /99 date after the year 2000, it should interpret it as 1999, to avoid ending up with a stale cache entry. This is as already specified in RFC2068. Scenario 2: If a client gets an Expires /00 date before the year 2000, and subsequently is faced with a choice to either retrieve the document from its cache or look for an updated copy, it may interpret it as the year 2000, to avoid the unnecessary delay and bandwidth of an extra request. RFC850 date from client Scenario 3: If a server gets an If-Modified-Since /99 date from a client after the year 2000, it should interpret it as 1999 when comparing with the local modification date, in order to possibly avoid sending a full GET response rather than a HEAD response. Note that an If-Modified-Since header must never be in the future. (Note that there has been a lot of discussion about whether If-Modified-Since should really be compared with "less than" semantics or whether the date should be considered a 'token' which is required to exactly match the Last-Modified date in order to avoid a full GET response. There have been bugs and problems with implementations that deal badly with dailight savings time, etc. I'm not sure how this debate dealt with the question of how to convert the dates, or whether servers can actually use "less-than" semantics. Input is requested....) Dates in HTML In RFC1866, on HTML 2.0,the tag allows the embedding of recommended values for some HTTP headers, including Expires. E.g. Servers should rewrite these dates into RFC1123 format if necessary. Internet & Network Layer Mail After reviewing all mail-related RFCs, it was discovered that while some obsolete standards required two-digit years, all currently-used standards require four-digit years and are thus not prone to typical Year 2000 problems. RFCs 821 and 822, the main basis for SMTP mail exchange and message format, originally required two-digit years. However, both of these RFCs were later modified by RFC 1123 in 1989, which strongly recommended 4-digit years. Although there might be a few very old SMTP systems using two-digit years, it is believed that almost all mail sent over the Internet today uses four-digit years. Mail that contains two-digit years in its SMTP headers will not "fail", but might be missorted in message stores and mail user agents. This problem is avoided entirely by taking the RFC 1123 change as a requirement, rather than merely as a recommendation. IMAP versions 1, 2, and 3 used two-digit years, but IMAP version 4 (defined in RFCs 1730 and 1732 in 1994) requires four-digit years. There are still a few IMAP 2 servers and clients in use on the Internet today, but IMAP version 4 has already take over almost all of the IMAP market. Mail stored on an IMAP server or client with two-digit years will not "fail", but could possibly be missorted or prematurely expired. RFC 1153 describes a format for digests of mailing lists, and uses two-digit dates. This format is not widely used. The use of two-digit dates could possibly cause missorting of stored messages. RFC 1327, which describes mapping between X.400 mail and SMTP mail, uses the UTCTime format. RFC 1422 describes the structure of certificates that were used in PEM (and are expected to be used in many other mail and non-mail services). Those certificates use dates in UTCTime format. Poorly-written software might prematurely expire or validate a certificate based on comparisons of the date with the current date, although no current software is known to do this. Although not directly related to email, it should be noted that many LDAP specifications use dates in UTCTime format. Also not directly related to email, both the NNTP transport protocol and the Usenet news message format use two-digit years. NTP You should understand there is no reference anywhere in the NTP specification or implmentation to any reference epoch other than 1 January 1900. In short, NTP doesn't know anything about the millennium. One such problem exists for rfc868 - Time Protocol (which is an actual full "Internet Standard Protocol" as listed in rfc-index and rfc2000): S: Send the time as a 32 bit binary number. ... The time is the number of seconds since 00:00 (midnight) 1 January 1900 GMT, such that the time 1 is 12:00:01 am on 1 January 1900 GMT; this base will serve until the year 2036. For example: the time 2,208,988,800 corresponds to 00:00 1 Jan 1970 GMT, 2,398,291,200 corresponds to 00:00 1 Jan 1976 GMT, 2,524,521,600 corresponds to 00:00 1 Jan 1980 GMT, 2,629,584,000 corresponds to 00:00 1 May 1983 GMT, and -1,297,728,000 corresponds to 00:00 17 Nov 1858 GMT. (By the way - this seems confusing - is it unsigned (as indicated by the reference to 2036) or signed (as indicated by the example)? And the value for 1 May 1983 should be 2,629,580,400.) By my calculations, the end of this epoch is Thu Feb 07 00:54:54 2036 GMT Name Serving Network Management The Network Management Internet-Drafts reviewed for this report include all Internet-Drafts that were current as of April 30, 1997. The drafts were chosen for review using the following method. The file "1id-abstracts.txt" was searched for the keywords "MIB" and "Manage" (case insensitive search). All drafts with these keywords ere pulled from the internet draft repository and searched. Here's the actual list of Internet-Drafts that we searched: draft-anderson-docs-rf-mib-00.txt draft-battle-instresmib-00.txt draft-bierman-ptopo-mib-proto-00.txt draft-bolton-edimib-00.txt draft-bush-rdrn-mib-00.txt draft-bush-vnc-mib-00.txt draft-cochrane-frmib-dte-svc-00.txt draft-deri-http-mgmt-00.txt draft-donelan-netmgt-guidelines-00.txt draft-ietf-disman-mgt-target-mib-01.txt draft-ietf-disman-notify-mib-00.txt draft-hazewinkel-appl-mib-00.txt draft-ietf-agentx-ext-pro-03.txt draft-ietf-applmib-mib-02.txt draft-ietf-applmib-sysapplmib-08.txt draft-ietf-applmib-wwwmib-02.txt draft-ietf-atommib-acct-04.txt draft-ietf-atommib-atm1ng-03.txt draft-ietf-atommib-atm2-09.txt draft-ietf-atommib-atm2TC-06.txt draft-ietf-atommib-atmacct-01.txt draft-ietf-atommib-atmhist-00.txt draft-ietf-atommib-perfhistTC-01.txt draft-ietf-atommib-sonetng-02.txt draft-ietf-atommib-test-02.txt draft-ietf-avt-rtp-mib-00.txt draft-ietf-disman-event-mib-00.txt draft-ietf-disman-event-mib-01.txt draft-ietf-disman-express-mib-00.txt draft-ietf-disman-express-mib-01.txt draft-ietf-disman-framework-00.txt draft-ietf-disman-mgt-target-mib-00.txt draft-ietf-disman-mgt-target-mib-01.txt draft-ietf-disman-notify-mib-00.txt draft-ietf-disman-notify-mib-01.txt draft-ietf-disman-script-mib-01.txt draft-ietf-fddimib-objects-v2-02.txt draft-ietf-fddimib-smiv2-object-v2-01.txt draft-ietf-frnetmib-atmiwf-00.txt draft-ietf-frnetmib-dcp-01.txt draft-ietf-frnetmib-frs-mib-01.txt draft-ietf-frnetmib-spvc-00.txt draft-ietf-hubmib-etherif-mib-01.txt draft-ietf-hubmib-mau-mib-04.txt draft-ietf-idmr-igmp-mib-04.txt draft-ietf-idmr-multicast-routmib-05.txt draft-ietf-idmr-pim-mib-03.txt draft-ietf-ifmib-mib-05.txt draft-ietf-ifmib-testmib-02.txt draft-ietf-intserv-guaranteed-mib-03.txt draft-ietf-intserv-mib-05.txt draft-ietf-ion-mars-mib-00.txt draft-ietf-ion-mib-02.txt draft-ietf-ion-nhrp-mib-01.txt draft-ietf-iplpdn-frmib-dte-09.txt draft-ietf-ipngwg-ipv6-mib-01.txt draft-ietf-ipngwg-ipv6-udp-tcp-mib-01.txt draft-ietf-madman-alarmmib-02.txt draft-ietf-madman-dsa-mib-1-03.txt draft-ietf-madman-mail-monitor-mib-03.txt draft-ietf-madman-nsm-mib-04.txt draft-ietf-printmib-mib-info-01.txt draft-ietf-radius-clientmib-03.txt draft-ietf-radius-servmib-02.txt draft-ietf-rmonmib-hcrmon-00.txt draft-ietf-rmonmib-rmonprot-v2-00.txt draft-ietf-rsvp-mib-05.txt draft-ietf-rtfm-meter-mib-00.txt draft-ietf-snanau-appnmib-04.txt draft-ietf-snanau-dlurmib-00.txt draft-ietf-snanau-hprmib-00.txt draft-ietf-snmpv3-lpm-00.txt draft-ietf-snmpv3-next-gen-arch-00.txt draft-ietf-trunkmib-ds0-mib-03.txt draft-ietf-trunkmib-ds1-mib-05.txt draft-ietf-trunkmib-ds3-mib-04.txt draft-ietf-vgmib-repeater-dev-03.txt draft-jeya-vlan-8021q-mib-00.txt draft-kjones-ptopo-framework-00.txt draft-malachi-topology-terms-00.txt draft-mellquist-web-sys-01.txt draft-rfced-info-romanov-00.txt draft-smith-java-appl-00.txt draft-tackabury-neo-mib-00.txt draft-teow-fabric-mib-02.txt draft-warwick-tokenring-01.txt draft-warwick-tokenring-arch-01.txt draft-waterman-rmonmib-smon-00.txt The following Year 2000-related elements were found in the network management-related RFCs and current Internet-Drafts. None of these should have any impacts on interoperability. 1. Use of GeneralizedTime in CMOT (RFCs 1095 and 1189) The standards for CMIP over TCP/IP specify an unusual use for the GeneralizedTime type. (GeneralizedTime has a four-digit representation of the year.) If the system generating the PDU does not have the current time, yet does have the time since last boot, then GeneralizedTime can be used to encode this information. The time since last boot will be added to the base time "0001 Jan 1 00:00:00.00" using the Gregorian calendar algorithm. This is really a "Year 0" problem rather than a Year 2000 problem, and in any case, CMOT is not currently deployed (if it ever was). 2. UTCTime in SNMP Definitions UTCTime is an ASN.1 type that includes a two-digit representation of the year. There are several options for UTCTime in ASN.1, that vary in precision and in local versus GMT, but these options all have two-digit years. The standards for SNMP definitions specify one particular format: YYMMDDHHMMZ The first usage of UTCTime in the standards for SNMP definitions goes all the way back to RFC 1303. It has persisted unchanged up through the current specifications in RFC 1902. The role of UTCTime in SNMP definitions is to record the history of an SNMP MIB module in the module itself, via two ASN.1 macros: o LAST-UPDATED o REVISION Applications that store and use MIB modules need to be smart about interpreting these UTCTimes, but with one exception, the times do not actually flow in the network. This one exception is the appnNodeMibVersion object in the APPN MIB (currently draft-ietf-snanau-appnmib-04.txt, but soon to be published as an RFC), which returns the value of LAST-UPDATED from the version of the APPN MIB that an agent has implemented. An application that can correctly interpret UTCTimes, by prepending a "19" or a "20" as appropriate, in the MIB modules it has stored locally will be able to interpret the value of this object correctly as well. 3. Objects in the Printer MIB (RFC 1559, draft-ietf-printmib-mib-info-01.txt) There are two objects in the Printer MIB that allow use of a date as an object value with no explicit guidance for formatting the value. The objects are prtInterpreterLangVersion and prtInterpreterVersion. Both are defined with a syntax of OCTET STRING. The descriptions for the objects allow the object value to contain a date, version code or other product specific information to identify the interpreter or language. The descriptions do not include an explicit statement recommending use of a four-digit year when a date is used as the object value. 4. Dates in Mobile Network Tracing Records (RFC 2041) The RFC specifies trace headers and footers with date fields that are character arrays of size 32. While 32 characters certainly provide enough room for a four-digit year, there's no explicit statement that these years must be represented with four digits. News Real Time Services Routing BGP4 (RFC1771) scanned for the Y2K problem ========================================== Conclusion: The protocol BGP4, as defined in RFC1771, is not vulnerable to the Y2K problem. The BGP4 protocol or the BGP4 FSM do not have knowledge of absolute time. There is a notion of relative time inside BGP4, and this is visible in the fact that BGP4 has five timers. The five timers are not a problem, since they keep relative time, as stated above. Below excerpts for proof from the RFC can be found: * Hold timer: The calculated value indicates the maximum number of seconds that may elapse between the receipt of successive KEEPALIVE, and/or UPDATE messages by the sender. [...] The suggested value for the Hold Time is 90 seconds. * ConnectRetry timer: The value of the initial timer shall be 60 seconds. The time shall be doubled for each consecutive retry. [...] The suggested value for the ConnectRetry timer is 120 seconds. * KeepAlive timer: KeepAlive messages are sent periodically to ensure the liveness of the connection. [...] The suggested value for the KeepAlive timer is 30 seconds. * MinRouteAdvertisementInterval: The parameter MinRouteAdvertisementInterval determines the minimum amount of time that must elapse between advertisement of routes to a particular destination from a single BGP speaker. [...] The suggested value for the MinRouteAdvertisementInterval is 30 seconds. * MinASOriginationInterval: The parameter MinASOriginationInterval determines the minimum amount of time that must elapse between successive advertisements of UPDATE messages that report changes within the advertising BGP speaker's own autonomous systems. [...] The suggested value for the MinASOriginationInterval is 15 seconds. Security Virtual Terminal TN3270 in TELNET * This is not reported to use dates and is therefore not susceptible * to year 2000 problems. TELNET * This does not use dates, with the possible exception of * authentication protocols. There are no year 2000 problems with classic unauthenticated connections. Further review of authentication protocols and implementations (e.g. Kerberos) may be in order to verify no year 2000 problems. SSH * the protocol authors report that this does not used dates and * therefore is not susceptible to year 2000 problems. X WINDOWS Protocol Assuming you mean The X Window System ("it's a window system called X, not a system called X Windows"), I am already fairly familiar with it, and while I too don't have time to go over it with a fine-tooth comb, I do not expect it to be vulnerable to Y2K problems. Almost all times that appear in the protocol are 32-bit counters that tick once a millisecond, I think, which has a time-to-wraparound of about 50 days. Security Considerations Althought this document does consider the implications of various security protocols, there is no need for additional security considerations. The effect of a potential year 2000 problem may cause some security problems, but those problems are more of specific applications rather than protocol deficiencies. References Because of the exhaustive nature of this investigation, the reader is referred to the list of published RFC's available from the IETF Secretariat, rather than republishing them here. Editors' Address Philip J. Nesser II Nesser & Nesser Consulting 13501 100th Ave NE, Suite 5202 Kirkland, WA 98034 USA Phone: (206)481-4303 Email: pjnesser@martigny.ai.mit.edu Appendix A: List of RFC's for each Area The following list contains the RFC's grouped by area that were searched for year 2000 problems. Each line contains four fields are separated by '::'. The first filed is the RFC number, the second field is the type of RFC (S = Standard, DS = Draft Standard, PS = Proposed Standard, E = Experimental, H = Historical, I = Informational, BC = Best Current Practice, '' = No Type), the third field is the Title, and the fourth field contains any comments. Autoconfiguration 1971:: PS:: IPv6 Stateless Address Autoconfiguration:: 1970:: PS:: Neighbor Discovery for IP Version 6 (IPv6):: 1542:: PS:: Clarifications and Extensions for the Bootstrap Protocol:: (Obsoletes RFC1532) 1541:: PS:: Dynamic Host Configuration Protocol:: (Obsoletes RFC1531) 1534:: PS:: Interoperation Between DHCP and BOOTP:: 1533:: PS:: DHCP Options and BOOTP Vendor Extensions:: (Obsoletes RFC1497) 1532:: PS:: Clarifications and Extensions for the Bootstrap Protocol:: (Updates RFC0951) (Obsoleted by RFC1542) 1531:: PS:: Dynamic Host Configuration Protocol:: (Obsoleted by RFC1541) 1497:: DS:: BOOTP Vendor Information Extensions:: (Updates RFC0951) (Obsoletes RFC1395) (Obsoleted by RFC1533) 1395:: DS:: BOOTP Vendor Information Extensions:: (Updates RFC0951) (Obsoletes RFC1084) (Obsoleted by RFC1497) 1084:: DS:: BOOTP vendor information extensions:: (Obsoletes RFC1048) (Obsoleted by RFC1395) 1048:: DS:: BOOTP vendor information extensions:: (Obsoleted by RFC1084) 951:: DS:: Bootstrap Protocol:: "(Updated by RFC1532, RFC1395, RFC1497) " 906:: :: Bootstrap loading using TFTP:: ====================================================================== Directory Services 2120:: E:: Managing the X.500 Root Naming Context:: 2079:: PS:: Definition of X.500 Attribute Types and an Object Class to Hold Uniform Resource Identifiers (URIs):: 1943:: I:: Building an X.500 Directory Service in the US:: 1914:: PS:: How to interact with a Whois++ mesh:: 1913:: PS:: Architecture of the Whois++ Index Service:: 1838:: E:: Use of the X.500 Directory to support mapping between X.400 and RFC 822 Addresses:: 1837:: E:: Representing Tables and Subtrees in the X.500 Directory:: 1836:: E:: Representing the O/R Address hierarchy in the X.500 Directory Information Tree:: 1835:: PS:: Architecture of the WHOIS++ service:: 1834:: I:: Whois and Network Information Lookup Service Whois++:: 1781:: PS:: Using the OSI Directory to Achieve User Friendly Naming:: (Obsoletes RFC1484) 1714:: I:: Referral Whois Protocol (RWhois):: 1684:: I:: Introduction to White Pages services based on X.500:: 1637:: E:: DNS NSAP Resource Records:: (Obsoletes RFC1348) (Obsoleted by RFC1706) 1632:: I:: A Revised Catalog of Available X.500 Implementations:: (FYI 11) (Obsoletes RFC1292) 1617:: I:: Naming and Structuring Guidelines for X.500 Directory Pilots:: (RTR 11) (Obsoletes RFC1384) 1609:: E:: Charting Networks in the X.500 Directory:: 1608:: E:: Representing IP Information in the X.500 Directory:: 1588:: I:: WHITE PAGES MEETING REPORT:: 1562:: I:: Naming Guidelines for the AARNet X.500 Directory Service:: 1491:: I:: A Survey of Advanced Usages of X.500:: (FYI 21) 1488:: PS:: The X.500 String Representation of Standard Attribute Syntaxes:: (Obsoleted by RFC1778) 1487:: PS:: X.500 Lightweight Directory Access Protocol:: (Obsoleted by RFC1777) 1485:: PS:: A String Representation of Distinguished Names (OSI-DS 23 (v5)):: (Obsoleted by RFC1779) 1484:: E:: Using the OSI Directory to achieve User Friendly Naming (OSI-DS 24 (v1.2)):: (Obsoleted by RFC1781) 1430:: I:: A Strategic Plan for Deploying an Internet X.500 Directory Service:: 1400:: I:: Transition and Modernization of the Internet Registration Service:: 1384:: I:: Naming Guidelines for Directory Pilots:: (Obsoleted by RFC1617) 1355:: I:: Privacy and Accuracy Issues in Network Information Center Databases:: (FYI 15) 1330:: I:: Recommendations for the Phase I Deployment of OSI Directory Services (X.500) and OSI Message Handling Services (X.400) within the ESnet Community:: 1309:: I:: Technical Overview of Directory Services Using the X.500 Protocol:: (FYI 14) 1308:: I:: Executive Introduction to Directory Services Using the X.500 Protocol:: (FYI 13) 1292:: I:: A Catalog of Available X.500 Implementations:: (FYI 11) (Obsoleted by RFC1632) 1279:: :: X.500 and Domains:: 1276:: PS:: Replication and Distributed Operations extensions to provide an Internet Directory using X.500:: 1275:: I:: Replication Requirements to provide an Internet Directory using X.500:: 1274:: PS:: The COSINE and Internet X.500 Schema:: 1255:: I:: A Naming Scheme for c=US:: (Obsoletes RFC1218) 1218:: :: A Naming Scheme for c=US:: (Obsoleted by RFC1255) 1202:: I:: Directory Assistance Service:: 1107:: :: Plan for Internet directory services:: 954:: DS:: NICNAME/WHOIS:: (Obsoletes RFC0812) 953:: H:: Hostname Server:: (Obsoletes RFC0811) 812:: :: NICNAME/WHOIS:: (Obsoleted by RFC0954) 756:: :: NIC name server - a datagram-based information utility:: 752:: :: Universal host table:: ====================================================================== Disk Sharing 1813:: I:: NFS Version 3 Protocol Specification:: 1094:: H:: NFS: Network File System Protocol specification:: ====================================================================== Games and Chat 1459:: E:: Internet Relay Chat Protocol:: ====================================================================== Information Services & File Transfer 2122:: PS:: VEMMI URL Specification:: 2070:: PS:: Internationalization of the Hypertext Markup Language:: 2068:: PS:: Hypertext Transfer Protocol -- HTTP/1.1:: 2056:: PS:: Uniform Resource Locators for Z39.50:: 2055:: I:: WebNFS Server Specification:: 2054:: I:: WebNFS Client Specification:: 2044:: I:: "UTF-8, a transformation format of Unicode and ISO 10646":: 2016:: E:: Uniform Resource Agents (URAs):: 1986:: E:: Experiments with a Simple File Transfer Protocol for Radio Links using Enhanced Trivial File Transfer Protocol (ETFTP):: 1980:: I:: A Proposed Extension to HTML: Client-Side Image Maps:: 1960:: PS:: A String Representation of LDAP Search Filters:: (Obsoletes RFC1558) 1959:: PS:: An LDAP URL Format:: 1945:: I:: Hypertext Transfer Protocol -- HTTP/1.0:: 1942:: E:: HTML Tables:: 1874:: E:: SGML Media Types:: 1867:: E:: Form-based File Upload in HTML:: 1866:: PS:: Hypertext Markup Language - 2.0:: 1865:: I:: EDI Meets the Internet: Frequently Asked Questions about Electronic Data Interchange (EDI) on the Internet:: 1862:: I:: "Report of the IAB Workshop on Internet Information Infrastructure, October 12-14, 1994":: 1843:: I:: HZ - A Data Format for Exchanging Files of Arbitrarily Mixed Chinese and ASCII characters:: 1842:: I:: ASCII Printable Characters-Based Chinese Character Encoding for Internet Messages:: 1823:: I:: The LDAP Application Program Interface:: 1815:: I:: Character Sets ISO-10646 and ISO-10646-J-1:: 1808:: PS:: Relative Uniform Resource Locators:: 1807:: I:: A Format for Bibliographic Records:: 1798:: PS:: Connection-less Lightweight Directory Access Protocol:: 1788:: E:: ICMP Domain Name Messages:: 1785:: I:: TFTP Option Negotiation Analysis:: (Updates RFC1350) 1784:: PS:: TFTP Timeout Interval and Transfer Size Options:: (Updates RFC1350) 1783:: PS:: TFTP Blocksize Option:: (Updates RFC1350) 1782:: PS:: TFTP Option Extension:: (Updates RFC1350) 1779:: DS:: A String Representation of Distinguished Names:: (Obsoletes RFC1485) 1778:: DS:: The String Representation of Standard Attribute Syntaxes:: (Obsoletes RFC1488) 1777:: DS:: Lightweight Directory Access Protocol:: (Obsoletes RFC1487) 1766:: PS:: Tags for the Identification of Languages:: 1738:: PS:: Uniform Resource Locators (URL):: 1737:: I:: Functional Requirements for Uniform Resource Names:: 1736:: I:: Functional Requirements for Internet Resource Locators:: 1729:: I:: Using the Z39.50 Information Retrieval Protocol in the Internet Environment:: 1728:: I:: Resource Transponders:: 1727:: I:: A Vision of an Integrated Internet Information Service:: 1639:: E:: FTP Operation Over Big Address Records (FOOBAR):: (Obsoletes RFC1545) 1633:: I:: Integrated Services in the Internet Architecture: an Overview.:: 1630:: I:: Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web:: 1625:: I:: WAIS over Z39.50-1988:: 1558:: I:: A String Representation of LDAP Search Filters:: (Obsoleted by RFC1960) 1554:: I:: ISO-2022-JP-2: Multilingual Extension of ISO-2022-JP:: 1545:: E:: FTP Operation Over Big Address Records (FOOBAR):: (Obsoleted by RFC1639) 1530:: I:: Principles of Operation for the TPC.INT Subdomain: General Principles and Policy:: 1529:: I:: Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Administrative Policies:: (Obsoletes RFC1486) 1528:: E:: Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Technical Procedures:: (Obsoletes RFC1486) 1489:: I:: Registration of a Cyrillic Character Set:: 1486:: E:: An Experiment in Remote Printing:: "(Obsoleted by RFC1528, RFC1529) " 1440:: E:: SIFT/UFT: Sender-Initiated/Unsolicited File Transfer:: 1436:: I:: The Internet Gopher Protocol (a distributed document search and retrieval protocol):: 1415:: PS:: FTP-FTAM Gateway Specification:: 1413:: PS:: Identification Protocol:: (Obsoletes RFC0931) 1350:: S:: THE TFTP PROTOCOL (REVISION 2):: "(Obsoletes RFC0783) (STD 33) (Updated by RFC1782, RFC1783, RFC1784, RFC1785) " 1345:: I:: Character Mnemonics & Character Sets:: 1312:: E:: Message Send Protocol:: (Obsoletes RFC1159) 1302:: I:: Building a Network Information Services Infrastructure:: (FYI 12) 1288:: DS:: The Finger User Information Protocol:: (Obsoletes RFC1196) 1278:: I:: A String Encoding of Presentation Address:: 1241:: E:: A Scheme for an Internet Encapsulation Protocol: Version 1:: 1235:: E:: The Coherent File Distribution Protocol:: 1196:: DS:: The Finger User Information Protocol:: (Obsoletes RFC1194) (Obsoleted by RFC1288) 1194:: DS:: The Finger User Information Protocol:: (Obsoletes RFC0742) (Obsoleted by RFC1196) 1179:: I:: Line Printer Daemon Protocol:: 1123:: S:: Requirements for Internet hosts - application and support:: (STD 3) 1068:: :: Background File Transfer Program BFTP:: 1037:: H:: NFILE - a file access protocol:: 1003:: :: Issues in defining an equations representation standard:: 998:: E:: NETBLT: A bulk data transfer protocol:: (Obsoletes RFC0969) 978:: :: "Postel, J.B Voice File Interchange Protocol VFIP":: 971:: :: Survey of data representation standards:: 969:: :: NETBLT: A bulk data transfer protocol:: (Obsoleted by RFC0998) 965:: :: Format for a graphical communication protocol:: 959:: S:: File Transfer Protocol:: (Obsoletes RFC0765) (STD 9) 949:: :: FTP unique-named store command:: 916:: H:: Reliable Asynchronous Transfer Protocol RATP:: 913:: H:: Simple File Transfer Protocol:: 887:: E:: Resource Location Protocol:: 866:: S:: Active users:: (STD 23) 865:: S:: Quote of the Day Protocol:: 864:: S:: Character Generator Protocol:: (STD 22) 863:: S:: Discard Protocol:: (STD 21) 862:: S:: Echo Protocol:: (STD 20) 797:: :: Format for Bitmap files:: 795:: :: Service mappings:: 783:: DS:: TFTP Protocol revision 2:: (Obsoleted by RFC1350) 775:: :: Directory oriented FTP commands:: 765:: :: File Transfer Protocol specification:: (Obsoletes RFC0542) (Obsoleted by RFC0959) 751:: :: Survey of FTP mail and MLFL:: 743:: :: FTP extension: XRSQ/XRCP:: 742:: PS:: NAME/FINGER Protocol:: (Obsoleted by RFC1194) 740:: H:: NETRJS Protocol:: (Obsoletes RFC0599) 737:: :: FTP extension: XSEN:: 725:: :: RJE protocol for a resource sharing network:: 722:: :: Thoughts on interactions in distributed services:: 712:: :: Distributed Capability Computing System DCCS:: 707:: :: High-level framework for network-based resource sharing:: 697:: :: CWD command of FTP:: 691:: :: One more try on the FTP:: 683:: :: FTPSRV - Tenex extension for paged files:: 662:: :: Performance improvement in ARPANET file transfers from Multics:: 640:: :: Revised FTP reply codes:: 633:: :: IMP/TIP preventive maintenance schedule:: (Obsoleted by RFC0638) 630:: :: FTP error code usage for more reliable mail service:: 624:: :: Comments on the File Transfer Protocol:: (Obsoletes RFC0607) 622:: :: Scheduling IMP/TIP down time:: 614:: :: "Response to RFC 607: ""Comments on the File Transfer Protocol""":: (Updates RFC0607) 610:: :: Further datalanguage design concepts:: 607:: :: Comments on the File Transfer Protocol:: (Obsoleted by RFC0624) (Updated by RFC0614) 599:: :: Update on NETRJS:: (Obsoletes RFC0189) (Obsoleted by RFC0740) 593:: :: Telnet and FTP implementation schedule change:: 592:: :: Some thoughts on system design to facilitate resource sharing:: 589:: :: CCN NETRJS server messages to remote user:: 573:: :: Data and file transfer: Some measurement results:: 571:: :: Tenex FTP problem:: 570:: :: Experimental input mapping between NVT ASCII and UCSB On Line System:: 553:: :: Draft design for a text/graphics protocol:: 551:: :: "[Letter from Feinroth re: NYU, ANL, and LBL entering the net, and FTP protocol]":: 549:: :: "Minutes of Network Graphics Group meeting, 15-17 July 1973":: 543:: :: Network journal submission and delivery:: 542:: :: File Transfer Protocol:: (Obsoletes RFC0354) (Obsoleted by RFC0765) 535:: :: Comments on File Access Protocol:: 532:: :: UCSD-CC Server-FTP facility:: 525:: :: MIT-MATHLAB meets UCSB-OLS -an example of resource sharing:: 520:: :: Memo to FTP group: Proposal for File Access Protocol:: 514:: :: Network make-work:: 506:: :: FTP command naming problem:: 505:: :: Two solutions to a file transfer access problem:: 504:: :: Distributed resources workshop announcement:: 501:: :: "Un-muddling ""free file transfer""":: 499:: :: Harvard's network RJE:: 493:: :: "E.W., Jr Graphics Protocol":: 490:: :: Surrogate RJS for UCLA-CCN:: 487:: :: Free file transfer:: 486:: :: Data transfer revisited:: 485:: :: MIX and MIXAL at UCSB:: 480:: :: Host-dependent FTP parameters:: 479:: :: Use of FTP by the NIC Journal:: 478:: :: FTP server-server interaction - II:: 477:: :: Remote Job Service at UCSB:: 472:: :: Illinois' reply to Maxwell's request for graphics information NIC 14925:: 468:: :: FTP data compression:: 467:: :: Proposed change to Host-Host Protocol:Resynchronization of connection status:: (Updated by RFC0492) 463:: :: FTP comments and response to RFC 430:: 454:: :: File Transfer Protocol - meeting announcement and a new proposed document:: 451:: :: Tentative proposal for a Unified User Level Protocol:: 448:: :: Print files in FTP:: 446:: :: Proposal to consider a network program resource notebook:: 438:: :: FTP server-server interaction:: 437:: :: Data Reconfiguration Service at UCSB:: 436:: :: Announcement of RJS at UCSB:: 430:: :: Comments on File Transfer Protocol:: 429:: :: Character generator process:: 418:: :: Server file transfer under TSS/360 at NASA Ames:: 414:: :: File Transfer Protocol FTP status and further comments:: (Updates RFC0385) 412:: :: User FTP documentation:: 411:: :: New MULTICS network software features:: 410:: :: Removal of the 30-second delay when hosts come up:: 409:: :: Tenex interface to UCSB's Simple-Minded File System:: 407:: H:: Remote Job Entry Protocol:: (Obsoletes RFC0360) 406:: :: Scheduled IMP software releases:: 396:: :: Network Graphics Working Group meeting - second iteration:: 387:: :: Some experiences in implementing Network Graphics Protocol Level 0:: 385:: :: Comments on the File Transfer Protocol:: (Updates RFC0354) (Updated by RFC0414) 382:: :: Mathematical software on the ARPA Network:: 374:: :: IMP system announcement:: 373:: :: Arbitrary character sets:: 368:: :: "Comments on ""Proposed Remote Job Entry Protocol""":: 367:: :: Network host status:: (Obsoletes RFC0366) (Obsoleted by RFC0370) 366:: :: Network host status:: (Obsoletes RFC0362) (Obsoleted by RFC0367) 361:: :: Deamon processes on host 106:: 360:: :: Proposed Remote Job Entry Protocol:: (Obsoleted by RFC0407) 354:: :: File Transfer Protocol:: (Obsoletes RFC0264) (Obsoleted by RFC0542) (Updated by RFC0385) 351:: :: Graphics information form for the ARPANET graphics resources notebook:: 342:: :: Network host status:: (Obsoletes RFC0332) (Obsoleted by RFC0344) 338:: :: EBCDIC/ASCII mapping for network RJE:: 336:: :: Level 0 Graphic Input Protocol:: 335:: :: New interface - IMP/360:: 332:: :: Network host status:: (Obsoletes RFC0330) (Obsoleted by RFC0342) 325:: :: Network Remote Job Entry program - NETRJS:: 324:: :: RJE Protocol meeting:: 314:: :: Network Graphics Working Group meeting:: 310:: :: Another look at Data and File Transfer Protocols:: 309:: :: Data and File Transfer workshop announcement:: 307:: :: Using network Remote Job Entry:: 306:: :: Network host status:: (Obsoletes RFC0298) (Obsoleted by RFC0315) 299:: :: Information management system:: 298:: :: Network host status:: (Obsoletes RFC0293) (Obsoleted by RFC0306) 294:: :: "On the use of ""set data type"" transaction in File Transfer Protocol":: (Updates RFC0265) 293:: :: Network host status:: (Obsoletes RFC0288) (Obsoleted by RFC0298) 292:: :: "E.W., Jr Graphics Protocol: Level 0 only":: 288:: :: Network host status:: (Obsoletes RFC0287) (Obsoleted by RFC0293) 287:: :: Status of network hosts:: (Obsoletes RFC0267) (Obsoleted by RFC0288) 286:: :: Network library information system:: 285:: :: Network graphics:: 283:: :: NETRJT: Remote Job Service Protocol for TIPS:: (Updates RFC0189) 281:: :: Suggested addition to File Transfer Protocol:: 268:: :: Graphics facilities information:: 267:: :: Network host status:: (Obsoletes RFC0266) (Obsoleted by RFC0287) 266:: :: Network host status:: (Obsoletes RFC0255) (Obsoleted by RFC0267) 265:: :: "Heafner, J.F ,McKenzie, A.M , Melvin, J.T , Sundberg, R.L , Watson, R.W , White, J.E.File Transfer Protocol":: (Updated by RFC0294) 264:: :: "Heafner, J.F ,McKenzie, A.M , Melvin, J.T , Sundberg, R.L , Watson, R.W , White, J.E.Data Transfer Protocol":: (Obsoletes RFC0171) (Obsoleted by RFC0354) 255:: :: Status of network hosts:: (Obsoletes RFC0252) (Obsoleted by RFC0266) 252:: :: Network host status:: (Obsoletes RFC0240) (Obsoleted by RFC0255) 250:: :: Some thoughts on file transfer:: 238:: :: Comments on DTP and FTP proposals:: (Updates RFC0171) 217:: :: "Specifications changes for OLS, RJE/RJOR, and SMFS":: (Updates RFC0074) 199:: :: Suggestions for a network data-tablet graphics protocol:: 192:: :: Some factors which a Network Graphics Protocol must consider:: 191:: :: Graphics implementation and conceptualization at Augmentation Research Center:: 189:: :: Interim NETRJS specifications:: (Obsoletes RFC0088) (Obsoleted by RFC0599) (Updated by RFC0283) 184:: :: Proposed graphic display modes:: 183:: :: EBCDIC codes and their mapping to ASCII:: 181:: :: Modifications to RFC 177:: (Updates RFC0177) 174:: :: UCLA - computer science graphics overview:: 172:: :: File Transfer Protocol:: (Updates RFC0114) 163:: :: Data transfer protocols:: 141:: :: Comments on RFC 114: A File Transfer Protocol:: (Updates RFC0114) 134:: :: Network Graphics meeting:: 133:: :: File transfer and recovery:: 125:: :: Response to RFC 86: Proposal for network standard format for a graphics data stream:: (Updates RFC0086) (Updated by RFC0177) 114:: :: File Transfer Protocol:: "(Updated by RFC0171, RFC0172, RFC0141) " 105:: :: Network specifications for Remote Job Entry and Remote Job Output Retrieval at UCSB:: 98:: :: Logger Protocol proposal:: (Updated by RFC0123) 94:: :: Some thoughts on network graphics:: 88:: :: NETRJS: A third level protocol for Remote JobEntry:: (Obsoleted by RFC0189) 86:: :: Proposal for a network standard format for a data stream to control graphics display:: (Updated by RFC0125) 83:: :: Language-machine for data reconfiguration:: ====================================================================== Internet & Network Layer 2126:: PS:: ISO Transport Service on top of TCP (ITOT):: 2125:: PS:: The PPP Bandwidth Allocation Protocol (BAP) The PPP Bandwidth Allocation Control Protocol (BACP):: 2118:: I:: Microsoft Point-To-Point Compression (MPPC) Protocol:: 2114:: I:: Data Link Switching Client Access Protocol:: (Obsoletes RFC2106) 2113:: PS:: IP Router Alert Option:: 2107:: I:: Ascend Tunnel Management Protocol - ATMP:: 2106:: I:: Data Link Switching Remote Access Protocol:: (Obsoleted by RFC2114) 2105:: I:: Cisco Systems' Tag Switching Architecture Overview:: 2098:: I:: Toshiba's Router Architecture Extensions for ATM : Overview:: 2097:: PS:: The PPP NetBIOS Frames Control Protocol (NBFCP):: 2075:: I:: IP Echo Host Service:: 2067:: DS:: IP over HIPPI:: (Obsoletes RFC1374) 2043:: PS:: The PPP SNA Control Protocol (SNACP):: 2023:: PS:: IP Version 6 over PPP:: 2019:: PS:: Transmission of IPv6 Packets Over FDDI:: 2018:: PS:: TCP Selective Acknowledgment Options:: 2009:: E:: GPS-Based Addressing and Routing:: 2005:: PS:: Applicability Statement for IP Mobility Support:: 2004:: PS:: Minimal Encapsulation within IP:: 2003:: PS:: IP Encapsulation within IP:: 2002:: PS:: IP Mobility Support:: 2001:: PS:: "TCP Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery Algorithms":: 1994:: DS:: PPP Challenge Handshake Authentication Protocol (CHAP):: (Obsoletes RFC1334) 1993:: I:: PPP Gandalf FZA Compression Protocol:: 1990:: DS:: The PPP Multilink Protocol (MP):: (Obsoletes RFC1717) 1989:: DS:: PPP Link Quality Monitoring:: (Obsoletes RFC1333) 1981:: PS:: Path MTU Discovery for IP version 6:: 1979:: I:: PPP Deflate Protocol:: 1978:: I:: PPP Predictor Compression Protocol:: 1977:: I:: PPP BSD Compression Protocol:: 1976:: I:: PPP for Data Compression in Data Circuit-Terminating Equipment (DCE):: 1975:: I:: PPP Magnalink Variable Resource Compression:: 1974:: I:: PPP Stac LZS Compression Protocol:: 1973:: PS:: PPP in Frame Relay:: 1972:: PS:: A Method for the Transmission of IPv6 Packets over Ethernet Networks:: 1967:: I:: PPP LZS-DCP Compression Protocol (LZS-DCP):: 1963:: I:: PPP Serial Data Transport Protocol (SDTP):: 1962:: PS:: The PPP Compression Control Protocol (CCP):: 1954:: I:: Transmission of Flow Labelled IPv4 on ATM Data Links Ipsilon Version 1.0:: 1946:: I:: Native ATM Support for ST2+:: 1937:: I:: Local/Remote Forwarding Decision in Switched Data Link Subnetworks:: 1936:: I:: Implementing the Internet Checksum in Hardware:: 1934:: I:: Ascend's Multilink Protocol Plus (MP+):: 1933:: PS:: Transition Mechanisms for IPv6 Hosts and Routers:: 1932:: I:: IP over ATM: A Framework Document:: 1931:: I:: Dynamic RARP Extensions and Administrative Support for Automatic Network Address Allocation:: 1926:: I:: An Experimental Encapsulation of IP Datagrams on Top of ATM:: 1924:: I:: A Compact Representation of IPv6 Addresses:: 1919:: I:: Classical versus Transparent IP Proxies:: 1918:: BC:: Address Allocation for Private Internets:: (Updates RFC1627) (Obsoletes RFC1597) 1917:: BC:: An Appeal to the Internet Community to Return Unused IP Networks (Prefixes) to the IANA:: 1916:: I:: Enterprise Renumbering: Experience and Information Solicitation:: 1915:: BC:: Variance for The PPP Connection Control Protocol and The PPP Encryption Control Protocol:: 1897:: E:: IPv6 Testing Address Allocation:: 1888:: E:: OSI NSAPs and IPv6:: 1887:: I:: An Architecture for IPv6 Unicast Address Allocation:: 1885:: PS:: Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6):: 1884:: PS:: IP Version 6 Addressing Architecture:: 1883:: PS:: "Internet Protocol, Version 6 (IPv6) Specification":: 1881:: I:: IPv6 Address Allocation Management:: 1878:: I:: Variable Length Subnet Table For IPv4:: (Obsoletes RFC1860) 1877:: I:: PPP Internet Protocol Control Protocol Extensions for Name Server Addresses:: 1868:: E:: ARP Extension - UNARP:: 1860:: I:: Variable Length Subnet Table For IPv4:: (Obsoleted by RFC1878) 1859:: I:: ISO Transport Class 2 Non-use of Explicit Flow Control over TCP RFC1006 extension:: 1853:: I:: IP in IP Tunneling:: 1841:: I:: PPP Network Control Protocol for LAN Extension:: 1833:: PS:: Binding Protocols for ONC RPC Version 2:: 1832:: PS:: XDR: External Data Representation Standard:: 1831:: PS:: RPC: Remote Procedure Call Protocol Specification Version 2:: 1809:: I:: Using the Flow Label Field in IPv6:: 1795:: I:: "Data Link Switching: Switch-to-Switch Protocol AIW DLSw RIG: DLSw Closed Pages, DLSw Standard Version 1.0":: 1791:: E:: TCP And UDP Over IPX Networks With Fixed Path MTU:: 1770:: I:: IPv4 Option for Sender Directed Multi-Destination Delivery:: 1764:: PS:: The PPP XNS IDP Control Protocol (XNSCP):: 1763:: PS:: The PPP Banyan Vines Control Protocol (BVCP):: 1762:: DS:: The PPP DECnet Phase IV Control Protocol (DNCP):: (Obsoletes RFC1376) 1761:: I:: Snoop Version 2 Packet Capture File Format:: 1756:: E:: REMOTE WRITE PROTOCOL - VERSION 1.0:: 1755:: PS:: ATM Signaling Support for IP over ATM:: 1754:: I:: IP over ATM Working Group's Recommendations for the ATM Forum's Multiprotocol BOF Version 1:: 1752:: PS:: The Recommendation for the IP Next Generation Protocol:: 1744:: I:: Observations on the Management of the Internet Address Space:: 1735:: E:: NBMA Address Resolution Protocol (NARP):: 1726:: I:: Technical Criteria for Choosing IP:The Next Generation (IPng):: 1719:: I:: A Direction for IPng:: 1717:: PS:: The PPP Multilink Protocol (MP):: (Obsoleted by RFC1990) 1710:: I:: Simple Internet Protocol Plus White Paper:: 1707:: I:: CATNIP: Common Architecture for the Internet:: 1705:: I:: Six Virtual Inches to the Left: The Problem with IPng:: 1698:: I:: Octet Sequences for Upper-Layer OSI to Support Basic Communications Applications:: 1693:: E:: An Extension to TCP : Partial Order Service:: 1692:: PS:: Transport Multiplexing Protocol (TMux):: 1688:: I:: IPng Mobility Considerations:: 1687:: I:: A Large Corporate User's View of IPng:: 1686:: I:: IPng Requirements: A Cable Television Industry Viewpoint:: 1683:: I:: Multiprotocol Interoperability In IPng:: 1682:: I:: IPng BSD Host Implementation Analysis:: 1681:: I:: On Many Addresses per Host:: 1680:: I:: IPng Support for ATM Services:: 1679:: I:: HPN Working Group Input to the IPng Requirements Solicitation:: 1678:: I:: IPng Requirements of Large Corporate Networks:: 1677:: I:: Tactical Radio Frequency Communication Requirements for IPng:: 1676:: I:: INFN Requirements for an IPng:: 1674:: I:: A Cellular Industry View of IPng:: 1673:: I:: Electric Power Research Institute Comments on IPng:: 1672:: I:: Accounting Requirements for IPng:: 1671:: I:: IPng White Paper on Transition and Other Considerations:: 1670:: I:: Input to IPng Engineering Considerations:: 1669:: I:: Market Viability as a IPng Criteria:: 1667:: I:: Modeling and Simulation Requirements for IPng:: 1663:: PS:: PPP Reliable Transmission:: 1662:: S:: PPP in HDLC-like Framing:: (Obsoletes RFC1549) (STD 51) 1661:: S:: The Point-to-Point Protocol (PPP):: (Obsoletes RFC1548) (STD 51) 1644:: E:: T/TCP -- TCP Extensions for Transactions Functional Specification:: 1638:: PS:: PPP Bridging Control Protocol (BCP):: (Obsoletes RFC1220) 1634:: I:: Novell IPX Over Various WAN Media (IPXWAN):: (Obsoletes RFC1551) 1631:: I:: The IP Network Address Translator (Nat):: 1629:: DS:: Guidelines for OSI NSAP Allocation in the Internet:: (Obsoletes RFC1237) 1626:: PS:: Default IP MTU for use over ATM AAL5:: 1624:: I:: Computation of the Internet Checksum via Incremental Update:: (Updates RFC1071) 1622:: I:: Pip Header Processing:: 1621:: I:: Pip Near-term Architecture:: 1620:: I:: Internet Architecture Extensions for Shared Media:: 1619:: PS:: PPP over SONET/SDH:: 1618:: PS:: PPP over ISDN:: 1613:: I:: cisco Systems X.25 over TCP (XOT):: 1605:: I:: SONET to Sonnet Translation:: 1604:: PS:: Definitions of Managed Objects for Frame Relay Service:: (Obsoletes RFC1596) 1598:: PS:: PPP in X.25:: 1590:: I:: Media Type Registration Procedure:: (Updates RFC1521) (Obsoleted by RFC2048) 1577:: PS:: Classical IP and ARP over ATM:: 1575:: DS:: An Echo Function for CLNP (ISO 8473):: (Obsoletes RFC1139) 1570:: PS:: PPP LCP Extensions:: (Updates RFC1548) 1561:: E:: Use of ISO CLNP in TUBA Environments:: 1560:: I:: The MultiProtocol Internet:: 1553:: PS:: Compressing IPX Headers Over WAN Media (CIPX):: 1552:: PS:: The PPP Internetwork Packet Exchange Control Protocol (IPXCP):: 1551:: I:: Novell IPX Over Various WAN Media (IPXWAN):: (Obsoletes RFC1362) (Obsoleted by RFC1634) 1549:: DS:: PPP in HDLC Framing:: (Obsoleted by RFC1662) 1548:: DS:: The Point-to-Point Protocol (PPP):: (Obsoletes RFC1331) (Obsoleted by RFC1661) (Updated by RFC1570) 1547:: I:: Requirements for an Internet Standard Point-to-Point Protocol:: 1538:: I:: Advanced SNA/IP : A Simple SNA Transport Protocol:: 1526:: I:: Assignment of System Identifiers for TUBA/CLNP Hosts:: 1518:: PS:: An Architecture for IP Address Allocation with CIDR:: 1498:: I:: On the Naming and Binding of Network Destinations:: 1490:: DS:: Multiprotocol Interconnect over Frame Relay:: (Obsoletes RFC1294) 1483:: PS:: Multiprotocol Encapsulation over ATM Adaptation Layer 5:: 1475:: E:: TP/IX: The Next Internet:: 1466:: I:: Guidelines for Management of IP Address Space:: (Obsoletes RFC1366) (Obsoleted by RFC2050) 1454:: I:: Comparison of Proposals for Next Version of IP:: 1435:: I:: IESG Advice from Experience with Path MTU Discovery:: 1434:: I:: Data Link Switching: Switch-to-Switch Protocol:: 1433:: E:: Directed ARP:: 1393:: E:: Traceroute Using an IP Option:: 1390:: S:: Transmission of IP and ARP over FDDI Networks:: (Obsoletes RFC1188) (STD 36) 1385:: I:: EIP: The Extended Internet Protocol A Framework for Maintaining Backward Compatibility:: 1379:: I:: Extending TCP for Transactions -- Concepts:: 1378:: PS:: The PPP AppleTalk Control Protocol (ATCP):: 1377:: PS:: The PPP OSI Network Layer Control Protocol (OSINLCP):: 1376:: PS:: The PPP DECnet Phase IV Control Protocol (DNCP):: (Obsoleted by RFC1762) 1375:: I:: Suggestion for New Classes of IP Addresses:: 1374:: PS:: IP and ARP on HIPPI:: (Obsoleted by RFC2067) 1365:: I:: An IP Address Extension Proposal:: 1363:: E:: A Proposed Flow Specification:: 1362:: I:: Novell IPX Over Various WAN Media (IPXWAN):: (Obsoleted by RFC1551) 1356:: PS:: Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode:: (Obsoletes RFC0877) 1347:: I:: "TCP and UDP with Bigger Addresses (TUBA), A Simple Proposal for Internet Addressing and Routing":: 1337:: I:: TIME-WAIT Assassination Hazards in TCP:: 1335:: :: A Two-Tier Address Structure for the Internet: A Solution to the Problem of Address Space Exhaustion:: 1334:: PS:: PPP Authentication Protocols:: (Obsoleted by RFC1994) 1333:: PS:: PPP Link Quality Monitoring:: (Obsoleted by RFC1989) 1332:: PS:: The PPP Internet Protocol Control Protocol (IPCP):: (Obsoletes RFC1172) 1331:: PS:: The Point-to-Point Protocol (PPP) for the Transmission of Multi-protocol Datagrams over Point-to-Point Links:: (Obsoletes RFC1171) (Obsoleted by RFC1548) 1329:: I:: Thoughts on Address Resolution for Dual MAC FDDI Networks:: 1326:: I:: Mutual Encapsulation Considered Dangerous:: 1323:: PS:: TCP Extensions for High Performance:: (Obsoletes RFC1185) 1314:: PS:: A File Format for the Exchange of Images in the Internet:: 1307:: E:: Dynamically Switched Link Control Protocol:: 1306:: I:: Experiences Supporting By-Request Circuit-Switched T3 Networks:: 1294:: PS:: Multiprotocol Interconnect over Frame Relay:: (Obsoleted by RFC1490) 1293:: PS:: Inverse Address Resolution Protocol:: 1277:: PS:: Encoding Network Addresses to Support Operation Over Non-OSI Lower Layers:: 1263:: I:: TCP Extensions Considered Harmful:: 1256:: PS:: ICMP Router Discovery Messages:: 1240:: PS:: OSI Connectionless Transport Services on top of UDP - Version: 1:: 1237:: PS:: Guidelines for OSI NSAP Allocation in the Internet:: (Obsoleted by RFC1629) 1236:: :: IP to X.121 Address Mapping for DDN:: 1234:: PS:: Tunneling IPX Traffic through IP Networks:: 1226:: E:: Internet Protocol Encapsulation of AX.25 Frames:: 1223:: :: OSI CLNS and LLC1 Protocols on Network Systems HYPERchannel:: 1220:: PS:: Point-to-Point Protocol Extensions for Bridging:: (Obsoleted by RFC1638) 1219:: :: On the Assignment of Subnet Numbers:: 1210:: :: "Network and Infrastructure User Requirements for Transatlantic Research Collaboration - Brussels, July 16-18, and Washington July 24-25, 1990":: 1209:: DS:: The Transmission of IP Datagrams over the SMDS Service:: 1201:: H:: Transmitting IP Traffic over ARCNET Networks:: (Obsoletes RFC1051) 1191:: DS:: Path MTU Discovery:: 1188:: DS:: A Proposed Standard for the Transmission of IP Datagrams over FDDI Networks:: (Obsoletes RFC1103) (Obsoleted by RFC1390) 1185:: E:: TCP Extension for High-Speed Paths:: (Obsoleted by RFC1323) 1172:: PS:: The Point-to-Point Protocol (PPP) Initial Configuration Options:: (Obsoleted by RFC1332) 1171:: DS:: The Point-to-Point Protocol for the Transmission of Multi-Protocol Datagrams Over Point-to-Point Links:: (Obsoletes RFC1134) (Obsoleted by RFC1331) 1166:: :: Internet Numbers:: 1162:: :: Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542) Management Information Base:: (Obsoleted by RFC1238) 1151:: E:: Version 2 of the Reliable Data Protocol (RDP):: (Updates RFC0908) 1146:: E:: TCP Alternate Checksum Options:: (Obsoletes RFC1145) 1145:: E:: TCP Alternate Checksum Options:: (Obsoleted by RFC1146) 1144:: PS:: Compressing TCP/IP headers for low-speed serial links:: 1141:: :: Incremental Updating of the Internet Checksum:: (Updates RFC1071) 1139:: PS:: Echo function for ISO 8473:: "(Obsoleted by RFC1574, RFC1575) " 1134:: PS:: Point-to-Point Protocol: A proposal for multi-protocol transmission of datagrams over Point-to-Point links:: (Obsoleted by RFC1171) 1132:: S:: Standard for the transmission of 802.2 packets over IPX networks:: 1122:: S:: Requirements for Internet hosts - communication layers:: (STD 3) 1110:: :: Problem with the TCP big window option:: 1106:: :: TCP big window and NAK options:: 1103:: PS:: Proposed standard for the transmission of IP datagrams over FDDI Networks:: (Obsoleted by RFC1188) 1088:: S:: Standard for the transmission of IP datagrams over NetBIOS networks:: 1086:: :: ISO-TP0 bridge between TCP and X.25:: 1085:: :: ISO presentation services on top of TCP/IP based internets:: 1078:: :: TCP port service Multiplexer TCPMUX:: 1072:: E:: TCP extensions for long-delay paths:: 1071:: :: Computing the Internet checksum:: "(Updated by RFC1141, RFC1624) " 1070:: :: Use of the Internet as a subnetwork for experimentation with the OSI network layer:: 1069:: :: Guidelines for the use of Internet-IP addressesin the ISO Connectionless-Mode Network Protocol:: (Obsoletes RFC0986) 1063:: :: IP MTU Discovery options:: 1062:: :: Internet numbers:: (Obsoletes RFC1020) (Obsoleted by RFC1117) 1057:: I:: RPC: Remote Procedure Call Protocol specification version 2:: (Obsoletes RFC1050) 1055:: S:: Nonstandard for transmission of IP datagrams over serial lines: SLIP:: 1051:: S:: Standard for the transmission of IP datagrams and ARP packets over ARCNET networks:: (Obsoleted by RFC1201) 1050:: H:: RPC: Remote Procedure Call Protocol specification:: (Obsoleted by RFC1057) 1046:: :: Queuing algorithm to provide type-of-service forIP links:: 1045:: E:: VMTP: Versatile Message Transaction Protocol: Protocol specification:: 1044:: S:: Internet Protocol on Network System's HYPERchannel: Protocol specification:: 1042:: S:: Standard for the transmission of IP datagrams over IEEE 802 networks:: (Obsoletes RFC0948) 1030:: :: On testing the NETBLT Protocol over divers networks:: 1029:: :: More fault tolerant approach to address resolution for a Multi-LAN system of Ethernets:: 1027:: :: Using ARP to implement transparent subnet gateways:: 1025:: :: TCP and IP bake off:: 1016:: :: Something a host could do with source quench: The Source Quench Introduced Delay SQuID:: 1008:: :: Implementation guide for the ISO Transport Protocol:: 1007:: :: Military supplement to the ISO Transport Protocol:: 1006:: S:: ISO transport services on top of the TCP: Version: 3:: (Obsoletes RFC0983) (STD 35) 1002:: S:: Protocol standard for a NetBIOS service on a TCP/UDP transport: Detailed specifications:: (STD 19) 1001:: S:: Protocol standard for a NetBIOS service on a TCP/UDP transport: Concepts and methods:: (STD 19) 994:: :: "Final text of DIS 8473,Protocol for Providing the Connectionless-mode Network Service":: (Obsoletes RFC0926) 986:: :: Guidelines for the use of Internet-IP addressesin the ISO Connectionless-Mode Network Protocol [Working draft]:: (Obsoleted by RFC1069) 983:: :: ISO transport arrives on top of the TCP:: (Obsoleted by RFC1006) 982:: :: Guidelines for the specification of the structure of the Domain Specific Part DSP of the ISO standard NSAP address:: 970:: :: On packet switches with infinite storage:: 964:: :: Some problems with the specification of the Military Standard Transmission Control Protocol:: 963:: :: Some problems with the specification of the Military Standard Internet Protocol:: 962:: :: TCP-4 prime:: 955:: :: Towards a transport service for transaction processing applications:: 948:: :: Two methods for the transmission of IP datagrams over IEEE 802.3 networks:: (Obsoleted by RFC1042) 942:: :: Transport protocols for Department of Defense data networks:: 941:: :: Addendum to the networkservice definition covering network layer addressing:: 940:: :: Toward an Internet standard scheme for subnetting:: 936:: :: Another Internet subnet addressing scheme:: 935:: :: Reliable link layer protocols:: 932:: :: Subnetwork addressing scheme:: 926:: :: Protocol for providing the connectionless mode network services:: (Obsoleted by RFC0994) 925:: :: Multi-LAN address resolution:: 924:: :: Official ARPA-Internet protocols for connecting personal computers to the Internet:: (Obsoletes RFC0901) (Obsoleted by RFC0944) 922:: S:: Broadcasting Internet datagrams in the presence of subnets:: (STD 5) 919:: S:: Broadcasting Internet datagrams:: (STD 5) 917:: :: Internet subnets:: 914:: H:: Thinwire protocol for connecting personal computers to the Internet:: 905:: :: ISO Transport Protocol specification ISO DP 8073:: (Obsoletes RFC0892) 903:: S:: Reverse Address Resolution Protocol:: 896:: :: Congestion control in IP/TCP internetworks:: 895:: S:: Standard for the transmission of IP datagrams over experimental Ethernet networks:: 894:: S:: Standard for the transmission of IP datagrams over Ethernet networks:: 893:: :: Trailer encapsulations:: 892:: :: ISO Transport Protocol specification [Draft]:: (Obsoleted by RFC0905) 891:: S:: DCN local-network protocols:: 889:: :: Internet delay experiments:: 879:: :: TCP maximum segment size and related topics:: 877:: S:: Standard for the transmission of IP datagrams over public data networks:: (Obsoleted by RFC1356) 874:: :: Critique of X.25:: 872:: :: TCP-on-a-LAN:: 871:: :: Perspective on the ARPANET reference model:: 848:: :: "Who provides the ""little"" TCP services?":: 829:: :: Packet satellite technology reference sources:: 826:: S:: Ethernet Address Resolution Protocol: Or converting network protocol addresses to 48.bit Ethernet address for transmission on Ethernet hardware:: 824:: :: CRONUS Virtual Local Network:: 815:: :: IP datagram reassembly algorithms:: 814:: :: "Name, addresses, ports, and routes":: 813:: :: Window and acknowlegement strategy in TCP:: 801:: :: NCP/TCP transition plan:: 793:: S:: Transmission Control Protocol:: (Updates RFC0761) (STD 7) 792:: S:: Internet Control Message Protocol:: (Obsoletes RFC0777) (STD 5) 791:: S:: Internet Protocol:: (Obsoletes RFC0760) 789:: :: Vulnerabilities of network control protocols: An example:: 787:: :: Connectionless data transmission survey/tutorial:: 781:: :: Specification of the Internet Protocol IP timestamp option:: 777:: :: Internet Control Message Protocol:: (Obsoletes RFC0760) (Obsoleted by RFC0792) 768:: S:: User Datagram Protocol:: (STD 6) 761:: :: DOD Standard Transmission Control Protocol:: (STD 7) (Updated by RFC0793) 760:: :: DoD standard Internet Protocol:: "(Obsoleted by RFC0777, RFC0791) " 759:: H:: Internet Message Protocol:: 730:: :: Extensible field addressing:: 704:: :: IMP/Host and Host/IMP Protocol change:: (Obsoletes RFC0687) 696:: :: Comments on the IMP/Host and Host/IMP Protocol changes:: 695:: :: Official change in Host-Host Protocol:: 692:: :: Comments on IMP/Host Protocol changes RFCs 687 and 690:: (Updates RFC0690) 690:: :: Comments on the proposed Host/IMP Protocol changes:: (Updates RFC0687) (Updated by RFC0692) 689:: :: Tenex NCP finite state machine for connections:: 687:: :: IMP/Host and Host/IMP Protocol changes:: (Obsoleted by RFC0704) (Updated by RFC0690) 685:: :: Response time in cross network debugging:: 680:: :: Message Transmission Protocol:: (Updates RFC0561) 675:: :: Specification of Internet Transmission Control Program:: 674:: :: Procedure call documents - version 2:: 660:: :: Some changes to the IMP and the IMP/Host interface:: 632:: :: Throughput degradations for single packet messages:: 626:: :: On a possible lockup condition in IMP subnet due to message sequencing:: 613:: :: Network connectivity: A response to RFC 603:: (Updates RFC0603) 611:: :: Two changes to the IMP/Host Protocol to improve user/network communications:: 594:: :: Speedup of Host-IMP interface:: 591:: :: Addition to the Very Distant Host specifications:: 576:: :: Proposal for modifying linking:: 550:: :: NIC NCP experiment:: 548:: :: Hosts using the IMP Going Down message:: 528:: :: Software checksumming in the IMP and network reliability:: 521:: :: Restricted use of IMP DDT:: 489:: :: Comment on resynchronization of connection status proposal:: 488:: :: NLS classes at network sites:: 476:: :: IMP/TIP memory retrofit schedule rev. 2:: (Obsoletes RFC0447) 473:: :: MIX and MIXAL?:: 460:: :: NCP survey:: 459:: :: Network questionnaires:: 450:: :: MULTICS sampling timeout change:: 449:: :: Current flow-control scheme for IMPSYS:: (Updates RFC0442) 445:: :: IMP/TIP preventive maintenance schedule:: 442:: :: Current flow-control scheme for IMPSYS:: (Updated by RFC0449) 434:: :: IMP/TIP memory retrofit schedule:: (Obsoleted by RFC0447) 426:: :: Reconnection Protocol:: 417:: :: Link usage violation:: 398:: :: ICP sockets:: 395:: :: Switch settings on IMPs and TIPs:: 394:: :: Two proposed changes to the IMP-Host Protocol:: 359:: :: Status of the release of the new IMP System:: (Obsoletes RFC0343) 357:: :: Echoing strategy for satellite links:: 348:: :: Discard process:: 347:: :: Echo process:: 346:: :: Satellite considerations:: 343:: :: IMP System change notification:: (Obsoletes RFC0331) (Obsoleted by RFC0359) 312:: :: Proposed change in IMP-to-Host Protocol:: 301:: :: "BBN IMP #5 and NCC schedule March 4, 1971":: 300:: :: ARPA Network mailing lists:: (Obsoletes RFC0211) (Obsoleted by RFC0303) 271:: :: IMP System change notifications:: 241:: :: Connecting computers to MLC ports:: 210:: :: Improvement of flow control:: 203:: :: Achieving reliable communication:: 202:: :: Possible deadlock in ICP:: 197:: :: Initial Connection Protocol - Reviewed:: 190:: :: DEC PDP-10-IMLAC communications system:: 178:: :: Network graphic attention handling:: 176:: :: "Comments on ""Byte size for connections""":: 175:: :: "Comments on ""Socket conventions reconsidered""":: 166:: :: Data Reconfiguration Service: An implementation specification:: 165:: :: Proffered official Initial Connection Protocol:: (Obsoletes RFC0145) 161:: :: Solution to the race condition in the ICP:: 151:: :: "Comments on a proffered official ICP: RFCs 123, 127":: (Updates RFC0127) 150:: :: Use of IPC facilities: A working paper:: 146:: :: Views on issues relevant to data sharing on computer networks:: 145:: :: Initial Connection Protocol control commands:: (Obsoletes RFC0127) (Obsoleted by RFC0165) 143:: :: Regarding proffered official ICP:: 142:: :: Time-out mechanism in the Host-Host Protocol:: 128:: :: Bytes:: 127:: :: Comments on RFC 123:: (Updates RFC0123) (Obsoleted by RFC0145) (Updated by RFC0151) 123:: :: Proffered official ICP:: "(Updates RFC0098) (Obsoletes RFC0066) (Updated by RFC0148, RFC0127) " 122:: :: Network specifications for UCSB's Simple-Minded File System:: "(Updated by RFC0269, RFC0399) " 93:: :: Initial Connection Protocol:: 91:: :: Proposed User-User Protocol:: 80:: :: Protocols and data formats:: 79:: :: Logger Protocol error:: 70:: :: Note on padding:: (Updated by RFC0228) 67:: :: Proposed change to Host/IMP spec to eliminate marking:: 65:: :: Comments on Host/Host Protocol document #1:: 62:: :: Systems for interprocess communication in a resource sharing computer network:: (Obsoletes RFC0061) 60:: :: Simplified NCP Protocol:: 59:: :: Flow control - fixed versus demand allocation:: 56:: :: Third level protocol: Logger Protocol:: 55:: :: Prototypical implementation of the NCP:: 54:: :: Official protocol proffering:: (Updated by RFC0057) 53:: :: Official protocol mechanism:: 41:: :: IMP-IMP teletype communication:: 38:: :: Comments on network protocol from NWG/RFC #36:: 33:: :: New Host-Host Protocol:: "(Obsoletes RFC0011) (Updated by RFC0036, RFC0047) " 23:: :: Transmission of multiple control messages:: 22:: :: Host-host control message formats:: 20:: :: ASCII format for network interchange:: 19:: :: Two protocol suggestions to reduce congestion at swap bound nodes:: 17:: :: Some questions re: Host-IMP Protocol:: 12:: :: IMP-Host interface flow diagrams:: ====================================================================== Mail 2112:: PS:: The MIME Multipart/Related Content-type:: (Obsoletes RFC1872) 2111:: PS:: Content-ID and Message-ID Uniform Resource Locators:: 2110:: PS:: "MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)":: 2109:: PS:: HTTP State Management Mechanism:: 2095:: PS:: IMAP/POP AUTHorize Extension for Simple Challenge/Response:: 2088:: PS:: IMAP4 non-synchroniziong literals:: 2087:: PS:: IMAP4 QUOTA extension:: 2086:: PS:: IMAP4 ACL extension:: 2077:: PS:: The Model Primary Content Type for Multipurpose Internet Mail Extensions:: 2076:: I:: Common Internet Message Headers:: 2062:: I:: Internet Message Access Protocol - Obsolete Syntax:: 2061:: I:: IMAP4 COMPATIBILITY WITH IMAP2BIS:: 2060:: PS:: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1:: (Obsoletes RFC1730) 2049:: DS:: Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples:: (Obsoletes RFC1521) 2048:: BC:: Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures:: (Obsoletes RFC1590) 2047:: DS:: MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text:: (Obsoletes RFC1522) 2046:: DS:: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types:: (Obsoletes RFC1521) 2045:: DS:: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies:: (Obsoletes RFC1521) 2034:: PS:: SMTP Service Extension for Returning Enhanced Error Codes:: 2033:: I:: Local Mail Transfer Protocol:: 2017:: PS:: Definition of the URL MIME External-Body Access-Type:: 1991:: I:: PGP Message Exchange Formats:: 1985:: PS:: SMTP Service Extension for Remote Message Queue Starting:: 1957:: I:: Some Observations on Implementations of the Post Office Protocol (POP3):: 1947:: I:: Greek Character Encoding for Electronic Mail Messages:: 1939:: S:: Post Office Protocol - Version 3:: (Obsoletes RFC1725) (STD 53) 1927:: I:: Suggested Additional MIME Types for Associating Documents:: 1922:: I:: Chinese Character Encoding for Internet Messages:: 1911:: E:: Voice Profile for Internet Mail:: 1896:: I:: The text/enriched MIME Content-type:: (Obsoletes RFC1563) 1895:: I:: The Application/CALS-1840 Content-type:: 1894:: PS:: An Extensible Message Format for Delivery Status Notifications:: 1893:: PS:: Enhanced Mail System Status Codes:: 1892:: PS:: The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages:: 1891:: PS:: SMTP Service Extension for Delivery Status Notifications:: 1873:: E:: Message/External-Body Content-ID Access Type:: 1872:: E:: The MIME Multipart/Related Content-type:: (Obsoleted by RFC2112) 1870:: S:: SMTP Service Extension for Message Size Declaration:: (Obsoletes RFC1653) (STD 10) 1869:: S:: SMTP Service Extensions:: (Obsoletes RFC1651) (STD 10) 1864:: DS:: The Content-MD5 Header Field:: (Obsoletes RFC1544) 1854:: PS:: SMTP Service Extension for Command Pipelining:: 1848:: PS:: MIME Object Security Services:: 1847:: PS:: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted:: 1846:: E:: SMTP 521 reply code:: 1845:: E:: SMTP Service Extension for Checkpoint/Restart:: 1844:: I:: Multimedia E-mail (MIME) User Agent checklist:: (Obsoletes RFC1820) 1830:: E:: SMTP Service Extensions for Transmission of Large and Binary MIME Messages:: 1820:: I:: Multimedia E-mail (MIME) User Agent Checklist:: (Obsoleted by RFC1844) 1806:: E:: Communicating Presentation Information in Internet Messages: The Content-Disposition Header:: 1804:: E:: Schema Publishing in X.500 Directory:: 1803:: I:: Recommendations for an X.500 Production Directory Service:: 1801:: E:: MHS use of the X.500 Directory to support MHS Routing:: 1767:: PS:: MIME Encapsulation of EDI Objects:: 1741:: I:: MIME Content Type for BinHex Encoded Files:: 1740:: PS:: MIME Encapsulation of Macintosh files - MacMIME:: 1734:: PS:: POP3 AUTHentication command:: 1733:: I:: DISTRIBUTED ELECTRONIC MAIL MODELS IN IMAP4:: 1732:: I:: IMAP4 COMPATIBILITY WITH IMAP2 AND IMAP2BIS:: 1731:: PS:: IMAP4 Authentication mechanisms:: 1730:: PS:: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4:: (Obsoleted by RFC2060) 1725:: DS:: Post Office Protocol - Version 3:: (Obsoletes RFC1460) (Obsoleted by RFC1939) 1711:: I:: Classifications in E-mail Routing:: 1685:: I:: Writing X.400 O/R Names:: (RTR 12) 1653:: DS:: SMTP Service Extension for Message Size Declaration:: (Obsoletes RFC1427) (Obsoleted by RFC1870) 1652:: DS:: SMTP Service Extension for 8bit-MIMEtransport:: (Obsoletes RFC1426) 1651:: DS:: SMTP Service Extensions:: (Obsoletes RFC1425) (Obsoleted by RFC1869) 1649:: I:: Operational Requirements for X.400 Management Domains in the GO-MHS Community:: 1648:: PS:: Postmaster Convention for X.400 Operations:: 1642:: E:: UTF-7 - A Mail-Safe Transformation Format of Unicode:: 1641:: E:: Using Unicode with MIME:: 1616:: I:: X.400(1988) for the Academic and Research Community in Europe:: (RTR 10) 1615:: I:: Migrating from X.400(84) to X.400(88):: (RTR 9) 1563:: I:: The text/enriched MIME Content-type:: (Obsoletes RFC1523) (Obsoleted by RFC1896) 1557:: I:: Korean Character Encoding for Internet Messages:: 1556:: I:: Handling of Bi-directional Texts in MIME:: 1555:: I:: Hebrew Character Encoding for Internet Messages:: 1544:: PS:: The Content-MD5 Header Field:: (Obsoleted by RFC1864) 1524:: I:: A User Agent Configuration Mechanism For Multimedia Mail Format Information:: 1523:: I:: The text/enriched MIME Content-type:: (Obsoleted by RFC1563) 1522:: DS:: MIME (Multipurpose Internet Mail Extensions) Part Two: Message Header Extensions for Non-ASCII Text:: (Obsoletes RFC1342) (Obsoleted by RFC2047) 1521:: DS:: MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies:: "(Obsoletes RFC1341) (Obsoleted by RFC2045, RFC2046, RFC2049) (Updated by RFC1590) " 1506:: I:: A tutorial on gatewaying between X.400 and Internet mail:: (RTR 6) 1505:: E:: Encoding Header Field for Internet Messages:: (Obsoletes RFC1154) 1502:: PS:: X.400 Use of Extended Character Sets:: 1496:: PS:: Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messages:: (Updates RFC1328) 1495:: PS:: Mapping between X.400 and RFC-822 Message Bodies:: (Updates RFC1327) 1494:: PS:: Equivalences between 1988 X.400 and RFC-822 Message Bodies:: 1468:: I:: Japanese Character Encoding for Internet Messages:: 1465:: E:: Routing coordination for X.400 MHS services within a multi protocol / multi network environment Table Format V3 for static routing:: 1460:: DS:: Post Office Protocol - Version 3:: (Obsoletes RFC1225) (Obsoleted by RFC1725) 1456:: I:: Conventions for Encoding the Vietnamese Language VISCII: VIetnamese Standard Code for Information Interchange VIQR: VIetnamese Quoted-Readable Specification:: 1437:: I:: The Extension of MIME Content-Types to a New Medium:: 1429:: I:: Listserv Distribute Protocol:: 1428:: I:: Transition of Internet Mail from Just-Send-8 to 8Bit-SMTP/MIME:: 1427:: PS:: SMTP Service Extension for Message Size Declaration:: (Obsoleted by RFC1653) 1426:: PS:: SMTP Service Extension for 8bit-MIMEtransport:: (Obsoleted by RFC1652) 1425:: PS:: SMTP Service Extensions:: (Obsoleted by RFC1651) 1405:: E:: Mapping between X.400(1984/1988) and Mail-11 (DECnet mail):: 1357:: I:: A Format for E-mailing Bibliographic Records:: 1344:: I:: Implications of MIME for Internet Mail Gateways:: 1343:: I:: A User Agent Configuration Mechanism For Multimedia Mail Format Information:: 1342:: PS:: Representation of Non-ASCII Text in Internet Message Headers:: (Obsoleted by RFC1522) 1341:: PS:: MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies:: (Obsoleted by RFC1521) 1339:: E:: Remote Mail Checking Protocol:: 1328:: PS:: X.400 1988 to 1984 downgrading:: (Updated by RFC1496) 1327:: PS:: Mapping between X.400(1988) / ISO 10021 and RFC 822:: (Updates RFC0822) (Obsoletes RFC1148) (Updated by RFC1495) 1225:: DS:: Post Office Protocol - Version 3:: (Obsoletes RFC1081) (Obsoleted by RFC1460) 1211:: :: Problems with the Maintenance of Large Mailing Lists:: 1204:: E:: Message Posting Protocol (MPP):: 1203:: H:: Interactive Mail Access Protocol - Version 3:: (Obsoletes RFC1064) 1176:: E:: Interactive Mail Access Protocol - Version 2:: (Obsoletes RFC1064) 1168:: :: Intermail and Commercial Mail Relay Services:: 1159:: E:: Message Send Protocol:: (Obsoleted by RFC1312) 1154:: E:: Encoding Header Field for Internet Messages:: (Updates RFC1049) (Obsoleted by RFC1505) 1153:: E:: Digest Message Format:: 1148:: E:: Mapping between X.400 (1988) / ISO 10021 and RFC 822:: (Obsoletes RFC0987) (Obsoleted by RFC1327) 1138:: I:: Mapping between X.400(1988) / ISO 10021 and RFC 822:: (Updates RFC1026) 1137:: E:: Mapping between full RFC 822 and RFC 822 with restricted encoding:: (Updates RFC0976) 1090:: :: SMTP on X.25:: 1082:: H:: Post Office Protocol - version 3: Extended service offerings:: 1081:: PS:: Post Office Protocol - version 3:: (Obsoleted by RFC1225) 1064:: H:: Interactive Mail Access Protocol: Version 2:: "(Obsoleted by RFC1203, RFC1176) " 1056:: I:: PCMAIL: A distributed mail system for personal computers:: (Obsoletes RFC0993) 1049:: S:: Content-type header field for Internet messages:: (STD 11) (Updated by RFC1154) 1047:: :: Duplicate messages and SMTP:: 1026:: PS:: Addendum to RFC 987: Mapping between X.400 and RFC-822:: (Updates RFC0987) (Updated by RFC1138) 993:: :: PCMAIL: A distributed mail system for personal computers:: (Obsoletes RFC0984) (Obsoleted by RFC1056) 987:: PS:: Mapping between X.400 and RFC 822:: (Updates RFC0822) (Obsoleted by RFC1148) (Updated by RFC1026) 984:: :: PCMAIL: A distributed mail system for personal computers:: (Obsoleted by RFC0993) 976:: :: UUCP mail interchange format standard:: (Updated by RFC1137) 974:: S:: Mail routing and the domain system:: (STD 14) 937:: H:: Post Office Protocol - version 2:: (Obsoletes RFC0918) 934:: :: Proposed standard for message encapsulation:: 918:: :: Post Office Protocol:: (Obsoleted by RFC0937) 915:: :: Network mail path service:: 910:: :: Multimedia mail meeting notes:: 886:: :: Proposed standard for message header munging:: 876:: :: Survey of SMTP implementations:: 841:: :: Specification for message format for Computer Based Message Systems:: (Obsoletes RFC0806) 822:: S:: Standard for the format of ARPA Internet text messages:: "(Obsoletes RFC0733) (STD 11) (Updated by RFC1327, RFC0987) " 821:: S:: Simple Mail Transfer Protocol:: (Obsoletes RFC0788) (STD 10) 808:: :: Summary of computer mail services meeting held at BBN on 10 January 1979:: 807:: :: Multimedia mail meeting notes:: 805:: :: Computer mail meeting notes:: 788:: :: Simple Mail Transfer Protocol:: (Obsoletes RFC0780) (Obsoleted by RFC0821) 786:: :: Mail Transfer Protocol: ISI TOPS20 MTP-NIMAILinterface:: 785:: :: Mail Transfer Protocol: ISI TOPS20 file definitions:: 784:: :: Mail Transfer Protocol: ISI TOPS20 implementation:: 780:: :: Mail Transfer Protocol:: (Obsoletes RFC0772) (Obsoleted by RFC0788) 773:: :: Comments on NCP/TCP mail service transition strategy:: 772:: :: Mail Transfer Protocol:: (Obsoleted by RFC0780) 771:: :: Mail transition plan:: 767:: :: Structured format for transmission of multi-media documents:: 763:: :: Role mailboxes:: 757:: :: "Suggested solution to the naming, addressing, and delivery problem for ARPANET message systems":: 754:: :: Out-of-net host addresses for mail:: 753:: :: Internet Message Protocol:: 744:: :: MARS - a Message Archiving and Retrieval Service:: 733:: :: Standard for theformat of ARPA network text messages:: (Obsoletes RFC0724) (Obsoleted by RFC0822) 724:: :: Proposed official standard for the format of ARPA Network messages:: (Obsoleted by RFC0733) 720:: :: Address specification syntax for network mail:: 714:: :: Host-Host Protocol for an ARPANET-type network:: 713:: :: MSDTP-Message Services Data Transmission Protocol:: 706:: :: On the junk mail problem:: 577:: :: Mail priority:: 574:: :: Announcement of a mail facility at UCSB:: 561:: :: Standardizingnetwork mail headers:: (Updated by RFC0680) 555:: :: Responses to critiques of the proposed mail protocol:: 539:: :: Thoughts on the mail protocol proposed in RFC524:: 534:: :: Lost message detection:: 533:: :: Message-ID numbers:: 524:: :: Proposed Mail Protocol:: 516:: :: Lost message detection:: 512:: :: More on lost message detection:: 510:: :: Request for network mailbox addresses:: 498:: :: On mail service to CCN:: 475:: :: FTP and network mail system:: 469:: :: Network mail meeting summary:: 458:: :: Mail retrieval via FTP:: 453:: :: Meeting announcement to discuss a network mail system:: 333:: :: Proposed experiment with a Message Switching Protocol:: 278:: :: Revision of theMail Box Protocol:: (Obsoletes RFC0221) 224:: :: Comments on Mailbox Protocol:: 221:: :: Mail Box Protocol: Version 2:: (Obsoletes RFC0196) (Obsoleted by RFC0278) 196:: :: Mail Box Protocol:: (Obsoleted by RFC0221) 58:: :: Logical message synchronization:: 42:: :: Message data types:: ====================================================================== NTP 2030:: I:: "Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI":: (Obsoletes RFC1769) 1769:: I:: Simple Network Time Protocol (SNTP):: (Obsoleted by RFC2030) 1708:: I:: NTP PICS PROFORMA For the Network Time Protocol Version 3:: 1589:: I:: A Kernel Model for Precision Timekeeping:: 1361:: I:: Simple Network Time Protocol (SNTP):: 1305:: PS:: Network Time Protocol (v3):: (Obsoletes RFC1119) 1165:: E:: Network Time Protocol (NTP) over the OSI Remote Operations Service:: 1129:: :: Internet time synchronization: The Network Time Protocol:: 1128:: :: Measured performance of the Network Time Protocol in the Internet system:: 1119:: S:: Network Time Protocol version 2 specification and implementation:: (Obsoletes RFC1059) (STD 12) (Obsoleted by RFC1305) 1059:: :: Network Time Protocol version 1 specification and implementation:: (Obsoletes RFC0958) (Obsoleted by RFC1119) 958:: :: Network Time Protocol NTP:: (Obsoleted by RFC1059) 957:: :: Experiments in network clock synchronization:: 956:: :: Algorithms for synchronizing network clocks:: 868:: S:: Time Protocol:: (STD 26) 867:: S:: Daytime Protocol:: (STD 25) 778:: H:: DCNET Internet Clock Service:: 738:: :: Time server:: 29:: :: Response to RFC 28:: 28:: :: Time standards:: ====================================================================== Name Serving 2053:: I:: The AM (Armenia) Domain:: 2052:: E:: A DNS RR for specifying the location of services (DNS SRV):: 2010:: I:: Operational Criteria for Root Name Servers:: 1996:: PS:: A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY):: (Updates RFC1035) 1995:: PS:: Incremental Zone Transfer in DNS:: (Updates RFC1035) 1982:: PS:: Serial Number Arithmetic:: (Updates RFC1034) 1956:: I:: Registration in the MIL Domain:: 1912:: I:: Common DNS Operational and Configuration Errors:: 1886:: PS:: DNS Extensions to support IP version 6:: 1876:: E:: A Means for Expressing Location Information in the Domain Name System:: (Updates RFC1034) 1794:: I:: DNS Support for Load Balancing:: 1713:: I:: Tools for DNS debugging:: (FYI 27) 1712:: E:: DNS Encoding of Geographical Location:: 1706:: I:: DNS NSAP Resource Records:: (Obsoletes RFC1637) 1664:: E:: Using the Internet DNS to Distribute RFC1327 Mail Address Mapping Tables:: 1591:: I:: Domain Name System Structure and Delegation:: 1537:: I:: Common DNS Data File Configuration Error:: 1536:: I:: Common DNS Implementation Errors and Suggested Fixes.:: 1480:: I:: The US Domain:: (Obsoletes RFC1386) 1464:: E:: Using the Domain Name System To Store Arbitrary String Attributes:: 1394:: I:: Relationship of Telex Answerback Codes to Internet Domains:: 1386:: I:: The US Domain:: (Obsoleted by RFC1480) 1348:: E:: DNS NSAP RRs:: (Updates RFC1035) (Obsoleted by RFC1637) 1183:: E:: New DNS RR Definitions:: 1101:: :: DNS encoding of network names and other types:: (Updates RFC1034) 1035:: S:: Domain names - implementation and specification:: "(Obsoletes RFC0973) (STD 13) (Obsoleted by RFC2065) (Updated by RFC1348, RFC1995, RFC1996) " 1034:: S:: Domain names - concepts and facilities:: "(Obsoletes RFC0973) (STD 13) (Updated by RFC1982, RFC2065, RFC1876, RFC1101) " 1033:: :: Domain administrators operations guide:: 1032:: :: Domain administrators guide:: 1031:: :: MILNET name domain transition:: 973:: :: Domain system changes and observations:: "(Updates RFC0882) (Obsoleted by RFC1034, RFC1035) " 952:: :: DoD Internet host table specification:: 921:: :: Domain name system implementation schedule - revised:: (Updates RFC0897) 920:: :: Domain requirements:: 897:: :: Domain name system implementation schedule:: (Updates RFC0881) (Updated by RFC0921) 883:: :: Domain names: Implementation specification:: 882:: :: Domain names: Concepts and facilities:: (Updated by RFC0973) 881:: :: Domain names plan and schedule:: (Updated by RFC0897) 849:: :: Suggestions for improved host table distribution:: 830:: :: Distributed system for Internet name service:: 819:: :: Domain naming convention for Internet user applications:: 811:: :: Hostnames Server:: (Obsoleted by RFC0953) 810:: :: DoD Internet host table specification:: (Obsoletes RFC0608) 799:: :: Internet name domains:: 796:: :: Address mappings:: 627:: :: ASCII text file of hostnames:: 625:: :: On-line hostnames service:: 623:: :: Comments on on-line host name service:: 620:: :: Request for monitor host table updates:: 608:: :: Host names on-line:: (Obsoleted by RFC0810) 606:: :: Host names on-line:: 289:: :: What we hope is an official list of host names:: (Obsoleted by RFC0384) 280:: :: Draft of host names:: 273:: :: More on standard host names:: (Obsoletes RFC0237) 247:: :: Proffered set of standard host names:: (Obsoletes RFC0226) 237:: :: NIC view of standard host names:: (Obsoleted by RFC0273) 236:: :: Standard host names:: (Obsoletes RFC0229) 233:: :: Standardization of host call letters:: 229:: :: Standard host names:: (Obsoleted by RFC0236) 226:: :: Standardization of host mnemonics:: (Obsoleted by RFC0247) ====================================================================== Network Management 2128:: PS:: Dial Control Management Information Base using SMIv2:: 2127:: PS:: ISDN Management Information Base:: 2124:: I:: Light-weight Flow Admission Protocol Specification Version 1.0:: 2108:: PS:: Definitions of Managed Objects for IEEE 802.3 Repeater Devices using SMIv2:: (Updates RFC1516) (Obsoletes RFC1516) 2096:: PS:: IP Forwarding Table MIB:: (Obsoletes RFC1354) 2089:: I:: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent:: 2074:: PS:: Remote Network Monitoring MIB Protocol Identifiers:: 2064:: E:: Traffic Flow Measurement: Meter MIB:: 2063:: E:: Traffic Flow Measurement: Architecture:: 2051:: PS:: Definitions of Managed Objects for APPC:: 2041:: I:: Mobile Network Tracing:: 2039:: I:: Applicability of Standards Track MIBs to Management of World Wide Web Servers:: 2037:: PS:: Entity MIB:: 2024:: PS:: Definitions of Managed Objects for Data Link Switching using SNMPv2:: 2021:: PS:: Remote Network Monitoring Management Information Base Version 2 using SMIv2:: 2020:: PS:: Definitions of Managed Objects for IEEE 802.12 Interfaces:: 2013:: PS:: SNMPv2 Management Information Base for the User Datagram Protocol using SMIv2:: (Updates RFC1213) 2012:: PS:: SNMPv2 Management Information Base for the Transmission Control Protocol:: (Updates RFC1213) 2011:: PS:: SNMPv2 Management Information Base for the Internet Protocol using SMIv2:: (Updates RFC1213) 2006:: PS:: The Definitions of Managed Objects for IP Mobility Support using SMIv2:: 1944:: I:: Benchmarking Methodology for Network Interconnect Devices:: 1910:: E:: User-based Security Model for SNMPv2:: 1909:: E:: An Administrative Infrastructure for SNMPv2:: 1908:: DS:: Coexistence between Version 1 and Version 2 of the Internet-standard Network Management Framework:: (Obsoletes RFC1452) 1907:: DS:: Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2):: (Obsoletes RFC1450) 1906:: DS:: Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2):: (Obsoletes RFC1449) 1905:: DS:: Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2):: (Obsoletes RFC1448) 1904:: DS:: Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2):: (Obsoletes RFC1444) 1903:: DS:: Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2):: (Obsoletes RFC1443) 1902:: DS:: Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2):: (Obsoletes RFC1442) 1901:: E:: Introduction to Community-based SNMPv2:: 1857:: I:: A Model for Common Operational Statistics:: (Updates RFC1404) 1856:: I:: The Opstat Client-Server Model for Statistics Retrieval:: 1850:: DS:: OSPF Version 2 Management Information Base:: (Obsoletes RFC1253) 1792:: E:: TCP/IPX Connection Mib Specification:: 1759:: PS:: Printer MIB:: 1757:: DS:: Remote Network Monitoring Management Information Base:: (Obsoletes RFC1271) 1749:: PS:: IEEE 802.5 Station Source Routing MIB using SMIv2:: (Updates RFC1748) 1748:: DS:: IEEE 802.5 MIB using SMIv2:: (Updated by RFC1749) 1747:: PS:: Definitions of Managed Objects for SNA Data Link Control: SDLC:: 1743:: DS:: IEEE 802.5 MIB using SMIv2:: (Obsoletes RFC1231) 1742:: PS:: AppleTalk Management Information Base II:: (Obsoletes RFC1243) 1724:: DS:: RIP Version 2 MIB Extension:: (Obsoletes RFC1389) 1697:: PS:: Relational Database Management System (RDBMS) Management Information Base (MIB) using SMIv2:: 1696:: PS:: Modem Management Information Base (MIB) using SMIv2:: 1695:: PS:: Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2:: 1694:: DS:: Definitions of Managed Objects for SMDS Interfaces using SMIv2:: (Obsoletes RFC1304) 1666:: PS:: Definitions of Managed Objects for SNA NAUs using SMIv2:: 1665:: PS:: Definitions of Managed Objects for SNA NAUs using SMIv2:: 1660:: DS:: Definitions of Managed Objects for Parallel-printer-like Hardware Devices using SMIv2:: (Obsoletes RFC1318) 1659:: DS:: Definitions of Managed Objects for RS-232-like Hardware Devices using SMIv2:: (Obsoletes RFC1317) 1658:: DS:: Definitions of Managed Objects for Character Stream Devices using SMIv2:: (Obsoletes RFC1316) 1657:: PS:: Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2:: 1650:: PS:: Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2:: 1643:: S:: Definitions of Managed Objects for the Ethernet-like Interface Types:: (Obsoletes RFC1623) (STD 50) 1628:: PS:: UPS Management Information Base:: 1623:: S:: Definitions of Managed Objects for the Ethernet-like Interface Types:: (Obsoletes RFC1398) (STD 50) (Obsoleted by RFC1643) 1612:: PS:: DNS Resolver MIB Extensions:: 1611:: PS:: DNS Server MIB Extensions:: 1596:: PS:: Definitions of Managed Objects for Frame Relay Service:: (Obsoleted by RFC1604) 1595:: PS:: Definitions of Managed Objects for the SONET/SDH Interface Type:: 1593:: I:: SNA APPN Node MIB:: 1592:: E:: Simple Network Management Protocol Distributed Protocol Interface Version 2.0:: (Obsoletes RFC1228) 1573:: PS:: Evolution of the Interfaces Group of MIB-II:: (Obsoletes RFC1229) 1567:: PS:: X.500 Directory Monitoring MIB:: 1566:: PS:: Mail Monitoring MIB:: 1565:: PS:: Network Services Monitoring MIB:: 1564:: I:: DSA Metrics (OSI-DS 34 (v3)):: 1559:: DS:: DECnet Phase IV MIB Extensions:: (Obsoletes RFC1289) 1525:: PS:: Definitions of Managed Objects for Source Routing Bridges:: (Obsoletes RFC1286) 1516:: DS:: Definitions of Managed Objects for IEEE 802.3 Repeater Devices:: (Obsoletes RFC1368) (Obsoleted by RFC2108) (Updated by RFC2108) 1515:: PS:: Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs):: 1514:: PS:: Host Resources MIB:: 1513:: PS:: Token Ring Extensions to the Remote Network Monitoring MIB:: (Updates RFC1271) 1512:: PS:: FDDI Management Information Base:: (Updates RFC1285) 1503:: I:: Algorithms for Automating Administration in SNMPv2 Managers:: 1493:: DS:: Definitions of Managed Objects for Bridges:: (Obsoletes RFC1286) 1474:: PS:: The Definitions of Managed Objects for the Bridge Network Control Protocol of the Point-to-Point Protocol:: 1473:: PS:: The Definitions of Managed Objects for the IP Network Control Protocol of the Point-to-Point Protocol:: 1472:: PS:: The Definitions of Managed Objects for the Security Protocols of the Point-to-Point Protocol:: 1471:: PS:: The Definitions of Managed Objects for the Link Control Protocol of the Point-to-Point Protocol:: 1470:: I:: FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices:: (FYI 2) (Obsoletes RFC1147) 1461:: PS:: SNMP MIB extension for MultiProtocol Interconnect over X.25:: 1452:: PS:: Coexistence between version 1 and version 2 of the Internet-standard Network Management Framework:: (Obsoleted by RFC1908) 1451:: PS:: Manager to Manager Management Information Base:: 1450:: PS:: Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2):: (Obsoleted by RFC1907) 1449:: PS:: Transport Mappings for version 2 of the Simple Network Management Protocol (SNMPv2):: (Obsoleted by RFC1906) 1448:: PS:: Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2):: (Obsoleted by RFC1905) 1447:: PS:: Party MIB for version 2 of the Simple Network Management Protocol (SNMPv2):: 1446:: PS:: Security Protocols for version 2 of the Simple Network Management Protocol (SNMPv2):: 1445:: PS:: Administrative Model for version 2 of the Simple Network Management Protocol (SNMPv2):: 1444:: PS:: Conformance Statements for version 2 of the Simple Network Management Protocol (SNMPv2):: (Obsoleted by RFC1904) 1443:: PS:: Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2):: (Obsoleted by RFC1903) 1442:: PS:: Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2):: (Obsoleted by RFC1902) 1441:: PS:: Introduction to version 2 of the Internet-standard Network Management Framework:: 1431:: I:: DUA Metrics:: 1420:: PS:: SNMP over IPX:: (Obsoletes RFC1298) 1419:: PS:: SNMP over AppleTalk:: 1418:: PS:: SNMP over OSI:: (Obsoletes RFC1283) 1414:: PS:: Ident MIB:: 1407:: PS:: Definitions of Managed Objects for the DS3/E3 Interface Type:: (Obsoletes RFC1233) 1406:: PS:: Definitions of Managed Objects for the DS1 and E1 Interface Types:: (Obsoletes RFC1232) 1404:: I:: A Model for Common Operational Statistics:: (Updated by RFC1857) 1398:: DS:: Definitions of Managed Objects for the Ethernet-like Interface Types:: (Obsoletes RFC1284) (Obsoleted by RFC1623) 1389:: PS:: RIP Version 2 MIB Extension:: (Obsoleted by RFC1724) 1382:: PS:: SNMP MIB Extension for the X.25 Packet Layer:: 1381:: PS:: SNMP MIB Extension for X.25 LAPB:: 1369:: I:: Implementation Notes and Experience for The Internet Ethernet MIB:: 1368:: PS:: Definitions of Managed Objects for IEEE 802.3 Repeater Devices:: (Obsoleted by RFC1516) 1354:: PS:: IP Forwarding Table MIB:: (Obsoleted by RFC2096) 1353:: H:: Definitions of Managed Objects for Administration of SNMP Parties:: 1352:: H:: SNMP Security Protocols:: 1351:: H:: SNMP Administrative Model:: 1346:: I:: "Resource Allocation, Control, and Accounting for the Use of Network Resources":: 1318:: PS:: Definitions of Managed Objects for Parallel-printer-like Hardware Devices:: (Obsoleted by RFC1660) 1317:: PS:: Definitions of Managed Objects for RS-232-like Hardware Devices:: (Obsoleted by RFC1659) 1316:: PS:: Definitions of Managed Objects for Character Stream Devices:: (Obsoleted by RFC1658) 1315:: PS:: Management Information Base for Frame Relay DTEs:: 1304:: PS:: Definitions of Managed Objects for the SIP Interface Type:: (Obsoleted by RFC1694) 1303:: I:: A Convention for Describing SNMP-based Agents:: 1298:: I:: SNMP over IPX:: (Obsoleted by RFC1420) 1289:: PS:: DECnet Phase IV MIB Extensions:: (Obsoleted by RFC1559) 1286:: PS:: Definitions of Managed Objects for Bridges:: "(Obsoleted by RFC1525, RFC1493) " 1285:: PS:: FDDI Management Information Base:: (Updated by RFC1512) 1284:: PS:: Definitions of Managed Objects for the Ethernet-like Interface Types:: (Obsoleted by RFC1398) 1283:: E:: SNMP over OSI:: (Obsoletes RFC1161) (Obsoleted by RFC1418) 1273:: I:: "A Measurement Study of Changes in Service-Level Reachability in the Global TCP/IP Internet: Goals, Experimental Design, Implementation, and Policy Considerations":: 1272:: I:: Internet Accounting: Background:: 1271:: PS:: Remote Network Monitoring Management Information Base:: (Obsoleted by RFC1757) (Updated by RFC1513) 1270:: I:: SNMP Communications Services:: 1269:: PS:: Definitions of Managed Objects for the Border Gateway Protocol (Version 3):: 1262:: :: Guidelines for Internet Measurement Activities:: 1253:: PS:: OSPF Version 2 Management Information Base:: (Obsoletes RFC1252) (Obsoleted by RFC1850) 1252:: PS:: OSPF Version 2 Management Information Base:: (Obsoletes RFC1248) (Obsoleted by RFC1253) 1248:: PS:: OSPF Version 2 Management Information Base:: (Obsoleted by RFC1252) (Updated by RFC1349) 1247:: DS:: OSPF Version 2:: (Obsoletes RFC1131) (Obsoleted by RFC1583) 1243:: PS:: AppleTalk Management Information Base:: (Obsoleted by RFC1742) 1242:: I:: Benchmarking Terminology for Network Interconnection Devices:: 1239:: PS:: Reassignment of Experimental MIBs to Standard MIBs:: (Updates RFC1233) 1238:: E:: CLNS MIB - for use with Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542):: (Obsoletes RFC1162) 1233:: H:: Definitions of Managed Objects for the DS3 Interface Type:: (Obsoleted by RFC1407) (Updated by RFC1239) 1232:: H:: Definitions of Managed Objects for the DS1 Interface Type:: (Obsoleted by RFC1406) 1231:: DS:: IEEE 802.5 Token Ring MIB:: (Obsoleted by RFC1743) 1230:: H:: IEEE 802.4 Token Bus MIB:: 1229:: DS:: Extensions to the Generic-Interface MIB:: (Obsoleted by RFC1573) 1228:: E:: SNMP-DPI - Simple Network Management Protocol Distributed Program Interface:: (Obsoleted by RFC1592) 1227:: E:: SNMP MUX Protocol and MIB:: 1224:: E:: Techniques for Managing Asynchronously Generated Alerts:: 1215:: I:: A Convention for Defining Traps for use with the SNMP:: 1214:: H:: OSI Internet Management: Management Information Base:: 1213:: S:: Management Information Base for Network Management of TCP/IP-based internets: MIB-II:: "(Obsoletes RFC1158) (STD 17) (Updated by RFC2012, RFC2013, RFC2011) " 1212:: S:: Concise MIB Definitions:: (STD 16) 1189:: H:: The Common Management Information Services and Protocols for the Internet:: (Obsoletes RFC1095) 1187:: E:: Bulk Table Retrieval with the SNMP:: 1161:: E:: SNMP over OSI:: (Obsoleted by RFC1283) 1158:: PS:: Management Information Base for Network Management of TCP/IP-based internets: MIB-II:: (Obsoletes RFC1156) (Obsoleted by RFC1213) 1157:: S:: A Simple Network Management Protocol (SNMP):: (Updates RFC1098) (STD 15) 1155:: S:: Structure and Identification of Management Information for TCP/IP-based Internets:: (Updates RFC1065) (STD 17) 1109:: :: Report of the second Ad Hoc Network Management Review Group:: 1098:: :: Simple Network Management Protocol SNMP:: (Obsoletes RFC1067) (Updated by RFC1157) 1095:: DS:: Common Management Information Services and Protocol over TCP/IP CMOT:: (Obsoleted by RFC1189) 1089:: :: SNMP over Ethernet:: 1067:: :: Simple Network Management Protocol:: (Obsoleted by RFC1098) 1066:: H:: Management Information Base for network management of TCP/IP-based internets:: (Updated by RFC1156) 1065:: H:: Structure and identification of management information for TCP/IP-based internets:: (Updated by RFC1155) 1052:: :: IAB recommendations for the development of Internet network management standards:: 1028:: H:: Simple Gateway Monitoring Protocol:: 1024:: :: HEMS variable definitions:: 1023:: :: HEMS monitoring and control language:: (Obsoleted by RFC1076) 1022:: :: High-level Entity Management Protocol HEMP:: 1021:: H:: High-level Entity Management System HEMS:: 1012:: :: Bibliography of Request For Comments 1 through 999:: 1011:: S:: Official Internet protocols:: (Obsoletes RFC0991) (STD 1) 1010:: S:: Assigned numbers:: (Obsoletes RFC0990) (STD 2) (Obsoleted by RFC1060) 996:: H:: Statistics server:: 619:: :: Mean round-trip times in the ARPANET:: 618:: :: Few observations on NCP statistics:: 616:: :: Latest network maps:: 615:: :: Proposed Network Standard Data Pathname Syntax:: 612:: :: Traffic statistics December 1973:: 601:: :: Traffic statistics November 1973:: 586:: :: Traffic statistics October 1973:: 579:: :: Traffic statistics September 1973:: 568:: :: Response to RFC 567 - cross country network bandwidth:: (Updates RFC0567) 567:: :: Cross country network bandwidth:: (Updated by RFC0568) 566:: :: Traffic statistics August 1973:: 565:: :: Storing network survey data at the datacomputer:: 557:: :: Revelations in network host measurements:: 546:: :: Tenex load averages for July 1973:: 545:: :: Of what quality be the UCSB resources evaluators?:: 538:: :: Traffic statistics June 1973:: 531:: :: Feast or famine? A response to two recent RFC's about network information:: 522:: :: Traffic statistics May 1973:: 509:: :: Traffic statistics April 1973:: 500:: :: Integration of data management systems on a computer network:: 482:: :: Traffic statistics February 1973:: 455:: :: Traffic statistics January 1973:: 443:: :: Traffic statistics December 1972:: 423:: :: UCLA Campus Computing Network liaison staff for ARPANET:: (Obsoletes RFC0389) 422:: :: Traffic statistics November 1972:: 421:: :: Software consulting service for network users:: 416:: :: ARC system will be unavailable for use during Thanksgivingweek :: 415:: :: Tenex bandwidth:: 413:: :: Traffic statistics October 1972:: 400:: :: Traffic statistics September 1972:: 392:: :: Measurement of host costs for transmitting network data:: 391:: :: Traffic statistics August 1972:: (Obsoletes RFC0378) 389:: :: UCLA Campus Computing Network liaison staff for ARPA Network:: (Obsoleted by RFC0423) 388:: :: NCP statistics:: (Updates RFC0323) 384:: :: Official site idents for organizations in the ARPA Network:: (Obsoletes RFC0289) 381:: :: Three aids to improved network operation:: 378:: :: Traffic statistics July 1972:: (Obsoleted by RFC0391) 369:: :: "Evaluation of ARPANET services January-March, 1972":: 362:: :: Network host status:: (Obsoletes RFC0353) (Obsoleted by RFC0366) 353:: :: Network host status:: (Obsoletes RFC0344) (Obsoleted by RFC0362) 344:: :: Network host status:: (Obsoletes RFC0342) (Obsoleted by RFC0353) 326:: :: Network host status:: (Obsoletes RFC0319) (Obsoleted by RFC0330) 323:: :: Formation of Network Measurement Group NMG:: (Updated by RFC0388) 308:: :: ARPANET host availability data:: 304:: :: Data management system proposal for the ARPA network:: 302:: :: Exercising the ARPANET:: 274:: :: Establishing a local guide for network usage:: 227:: :: Data transfer rates Rand/UCLA:: (Updates RFC0113) 212:: :: NWG meeting on network usage:: (Obsoletes RFC0207) (Updated by RFC0222) 193:: :: Network checkout:: (Obsoleted by RFC0198) 188:: :: Data management meeting announcement:: 156:: :: Status of the Illinois site: Response to RFC 116:: (Updates RFC0116) 153:: :: SRI ARC-NIC status:: 96:: :: Interactive network experiment to study modes of access tothe Network Information Center:: 32:: :: Connecting M.I.T. computers to the ARPA Computer-to-computer communication network:: 18:: :: [Link assignments]:: ====================================================================== News 1036:: :: Standard for interchange of USENET messages:: (Obsoletes RFC0850) 977:: PS:: Network News Transfer Protocol: A Proposed Standard for the Stream-Based Transmission of News:: 850:: :: Standard for interchange of USENET messages:: (Obsoleted by RFC1036) ====================================================================== Real Time Services 2102:: I:: Multicast Support for Nimrod : Requirements and Solution Approaches:: 2090:: E:: TFTP Multicast Option:: 2038:: PS:: RTP Payload Format for MPEG1/MPEG2 Video:: 2035:: PS:: RTP Payload Format for JPEG-compressed Video:: 2032:: PS:: RTP payload format for H.261 video streams:: 2029:: PS:: RTP Payload Format of Sun's CellB Video Encoding:: 2022:: PS:: Support for Multicast over UNI 3.0/3.1 based ATM Networks.:: 1890:: PS:: RTP Profile for Audio and Video Conferences with Minimal Control:: 1889:: PS:: RTP: A Transport Protocol for Real-Time Applications:: 1861:: I:: Simple Network Paging Protocol - Version 3 - Two-Way Enhanced:: 1821:: I:: Integration of Real-time Services in an IP-ATM Network Architecture:: 1819:: E:: Internet Stream Protocol Version 2 (ST2) Protocol Specification - Version ST2+:: (Obsoletes RFC1190) 1789:: I:: INETPhone: Telephone Services and Servers on Internet:: 1768:: E:: Host Group Extensions for CLNP Multicasting:: 1703:: I:: Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical Procedures:: 1645:: I:: Simple Network Paging Protocol - Version 2:: (Obsoletes RFC1568) 1614:: I:: Network Access to Multimedia Information:: (RTR 8) 1569:: I:: Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical Procedures:: 1568:: I:: Simple Network Paging Protocol - Version 1(b):: (Obsoleted by RFC1645) 1546:: I:: Host Anycasting Service:: 1469:: PS:: IP Multicast over Token-Ring Local Area Networks:: 1458:: I:: Requirements for Multicast Protocols:: 1453:: I:: A Comment on Packet Video Remote Conferencing and the Transport/Network Layers:: 1313:: I:: Today's Programming for KRFC AM 1313 Internet Talk Radio:: 1301:: I:: Multicast Transport Protocol:: 1257:: I:: Isochronous Applications Do Not Require Jitter-Controlled Networks:: 1197:: I:: Using ODA for Translating Multimedia Information:: 1193:: :: Client Requirements for Real-Time Communication Services:: 1190:: E:: "Experimental Internet Stream Protocol, Version 2 (ST-II)":: (Obsoleted by RFC1819) 1112:: S:: Host extensions for IP multicasting:: (Obsoletes RFC0988) (STD 5) 1054:: :: Host extensions for IP multicasting:: (Obsoletes RFC0988) 988:: :: Host extensions for IP multicasting:: "(Obsoletes RFC0966) (Obsoleted by RFC1112, RFC1054) " 966:: :: Host groups: A multicast extension to theInternet Protocol:: (Obsoleted by RFC0988) 947:: :: Multi-network broadcasting within the Internet:: 809:: :: UCL facsimile system:: 804:: :: CCITT draft recommendation T.4 [Standardization of Group 3 facsimile apparatus for document transmission]:: 803:: :: Dacom 450/500 facsimile data transcoding:: 798:: :: Decoding facsimile data from the Rapicom 450:: 769:: :: Rapicom 450 facsimile file format:: 741:: :: Specifications for the Network Voice Protocol NVP:: 511:: :: Enterprise phone service to NIC from ARPANET sites:: 508:: :: Real-time data transmission on the ARPANET:: 420:: :: CCA ICCC weather demo:: 408:: :: NETBANK:: 251:: :: Weather data:: ====================================================================== Routing 2103:: I:: Mobility Support for Nimrod : Challenges and Solution Approaches:: 2092:: I:: Protocol Analysis for Triggered RIP:: 2091:: PS:: Triggered Extensions to RIP to Support Demand Circuits:: 2081:: I:: RIPng Protocol Applicability Statement:: 2080:: PS:: RIPng for IPv6:: 2073:: PS:: An IPv6 Provider-Based Unicast Address Format:: 2072:: I:: Router Renumbering Guide:: 2042:: I:: Registering New BGP Attribute Types:: 2008:: BC:: Implications of Various Address Allocation Policies for Internet Routing:: 1998:: I:: An Application of the BGP Community Attribute in Multi-home Routing:: 1997:: PS:: BGP Communities Attribute:: 1992:: I:: The Nimrod Routing Architecture:: 1987:: I:: Ipsilon's General Switch Management Protocol Specification Version 1.1:: 1966:: E:: BGP Route Reflection An alternative to full mesh IBGP:: 1965:: E:: Autonomous System Confederations for BGP:: 1955:: I:: New Scheme for Internet Routing and Addressing (ENCAPS) for IPN:: 1953:: I:: Ipsilon Flow Management Protocol Specification for IPv4 Version 1.0:: 1940:: I:: Source Demand Routing: Packet Format and Forwarding Specification (Version 1).:: 1930:: BC:: "Guidelines for creation, selection, and registration of an Autonomous System (AS)":: 1925:: I:: The Twelve Networking Truths:: 1923:: I:: RIPv1 Applicability Statement for Historic Status:: 1863:: E:: A BGP/IDRP Route Server alternative to a full mesh routing:: 1817:: I:: CIDR and Classful Routing:: 1812:: PS:: Requirements for IP Version 4 Routers:: (Obsoletes RFC1716) 1793:: PS:: Extending OSPF to Support Demand Circuits:: 1787:: I:: Routing in a Multi-provider Internet:: 1786:: I:: Representation of IP Routing Policies in a Routing Registry (ripe-81++):: 1774:: I:: BGP-4 Protocol Analysis:: 1773:: I:: Experience with the BGP-4 protocol:: (Obsoletes RFC1656) 1772:: DS:: Application of the Border Gateway Protocol in the Internet:: (Obsoletes RFC1655) 1771:: DS:: A Border Gateway Protocol 4 (BGP-4):: (Obsoletes RFC1654) 1765:: E:: OSPF Database Overflow:: 1753:: I:: IPng Technical Requirements Of the Nimrod Routing and Addressing Architecture:: 1745:: PS:: BGP4/IDRP for IP---OSPF Interaction:: 1723:: DS:: RIP Version 2 Carrying Additional Information:: (Updates RFC1058) (Obsoletes RFC1388) 1722:: DS:: RIP Version 2 Protocol Applicability Statement:: 1721:: I:: RIP Version 2 Protocol Analysis:: (Obsoletes RFC1387) 1716:: I:: Towards Requirements for IP Routers:: (Obsoletes RFC1009) (Obsoleted by RFC1812) 1702:: I:: Generic Routing Encapsulation over IPv4 networks:: 1701:: I:: Generic Routing Encapsulation (GRE):: 1668:: I:: Unified Routing Requirements for IPng:: 1656:: I:: BGP-4 Protocol Document Roadmap and Implementation Experience:: (Obsoleted by RFC1773) 1655:: PS:: Application of the Border Gateway Protocol in the Internet:: (Obsoletes RFC1268) (Obsoleted by RFC1772) 1654:: PS:: A Border Gateway Protocol 4 (BGP-4):: (Obsoleted by RFC1771) 1587:: PS:: The OSPF NSSA Option:: 1586:: I:: Guidelines for Running OSPF Over Frame Relay Networks:: 1585:: I:: MOSPF: Analysis and Experience:: 1584:: PS:: Multicast Extensions to OSPF:: 1583:: DS:: OSPF Version 2:: (Obsoletes RFC1247) 1582:: PS:: Extensions to RIP to Support Demand Circuits:: 1581:: I:: Protocol Analysis for Extensions to RIP to Support Demand Circuits:: 1520:: I:: Exchanging Routing Information Across Provider Boundaries in the CIDR Environment:: 1519:: PS:: Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy:: (Obsoletes RFC1338) 1517:: PS:: Applicability Statement for the Implementation of Classless Inter-Domain Routing (CIDR):: 1504:: I:: Appletalk Update-Based Routing Protocol: Enhanced Appletalk Routing:: 1482:: I:: Aggregation Support in the NSFNET Policy Routing Database:: 1479:: PS:: Inter-Domain Policy Routing Protocol Specification: Version 1:: 1478:: PS:: An Architecture for Inter-Domain Policy Routing:: 1477:: I:: IDPR as a Proposed Standard:: 1476:: E:: RAP: Internet Route Access Protocol:: 1439:: I:: The Uniqueness of Unique Identifiers:: 1403:: PS:: BGP OSPF Interaction:: (Obsoletes RFC1364) 1397:: PS:: Default Route Advertisement In BGP2 And BGP3 Versions Of The Border Gateway Protocol:: 1388:: PS:: RIP Version 2 Carrying Additional Information:: (Updates RFC1058) (Obsoleted by RFC1723) 1387:: I:: RIP Version 2 Protocol Analysis:: (Obsoleted by RFC1721) 1383:: I:: An Experiment in DNS Based IP Routing:: 1380:: I:: IESG Deliberations on Routing and Addressing:: 1371:: I:: "Choosing a ""Common IGP"" for the IP Internet (The IESG's Recommendation to the IAB)":: 1370:: PS:: Applicability Statement for OSPF:: 1364:: PS:: BGP OSPF Interaction:: (Obsoleted by RFC1403) 1338:: I:: Supernetting: an Address Assignment and Aggregation Strategy:: (Obsoleted by RFC1519) 1322:: I:: A Unified Approach to Inter-Domain Routing:: 1268:: DS:: Application of the Border Gateway Protocol in the Internet:: (Obsoletes RFC1164) (Obsoleted by RFC1655) 1267:: DS:: A Border Gateway Protocol 3 (BGP-3):: (Obsoletes RFC1163) 1266:: I:: Experience with the BGP Protocol:: 1265:: I:: BGP Protocol Analysis:: 1264:: I:: Internet Routing Protocol Standardization Criteria:: 1254:: I:: Gateway Congestion Control Survey:: 1246:: I:: Experience with the OSPF Protocol:: 1245:: I:: OSPF Protocol Analysis:: 1222:: :: Advancing the NSFNET Routing Architecture:: 1195:: PS:: Use of OSI IS-IS for Routing in TCP/IP and Dual Environments:: 1164:: PS:: Application of the Border Gateway Protocol in the Internet:: (Obsoleted by RFC1268) 1163:: PS:: A Border Gateway Protocol (BGP):: (Obsoletes RFC1105) (Obsoleted by RFC1267) 1142:: I:: OSI IS-IS Intra-domain Routing Protocol:: 1136:: :: Administrative Domains and Routing Domains: A model for routing in the Internet:: 1133:: :: Routing between the NSFNET and the DDN:: 1131:: PS:: OSPF specification:: (Obsoleted by RFC1247) 1126:: :: Goals and functional requirements for inter-autonomous system routing:: 1125:: :: Policy requirements for inter Administrative Domain routing:: 1124:: :: Policy issues in interconnecting networks:: 1105:: E:: Border Gateway Protocol BGP:: (Obsoleted by RFC1163) 1104:: :: Models of policy based routing:: 1102:: :: Policy routing in Internet protocols:: 1092:: :: EGP and policy based routing in the new NSFNET backbone:: 1075:: E:: Distance Vector Multicast Routing Protocol:: 1074:: :: NSFNET backbone SPF based Interior Gateway Protocol:: 1058:: S:: Routing Information Protocol:: "(STD 34) (Updated by RFC1723, RFC1388) " 1009:: H:: Requirements for Internet gateways:: (Obsoletes RFC0985) (STD 4) (Obsoleted by RFC1716) 995:: :: End System to Intermediate System Routing Exchange Protocol for use in conjunction with ISO 8473:: 985:: :: Requirements for Internet gateways - draft:: (Obsoleted by RFC1009) 981:: :: Experimental multiple-path routing algorithm:: 975:: :: Autonomous confederations:: 950:: S:: Internet standard subnetting procedure:: (STD 5) 911:: :: EGP Gateway under Berkeley UNIX 4.2:: 904:: H:: Exterior Gateway Protocol formal specification:: (Updates RFC0827) (STD 18) 898:: :: Gateway special interest group meeting notes:: 890:: :: Exterior Gateway Protocol implementation schedule:: 888:: :: STUB Exterior Gateway Protocol:: 875:: :: "Gateways, architectures, and heffalumps":: 827:: :: Exterior Gateway Protocol EGP:: (Updated by RFC0904) 823:: H:: DARPA Internet gateway:: ====================================================================== Security 2104:: I:: HMAC: Keyed-Hashing for Message Authentication:: 2085:: PS:: HMAC-MD5 IP Authentication with Replay Prevention:: 2084:: I:: Considerations for Web Transaction Security:: 2082:: PS:: RIP-2 MD5 Authentication:: 2078:: PS:: "Generic Security Service Application Program Interface, Version 2":: (Obsoletes RFC1508) 2069:: PS:: An Extension to HTTP: Digest Access Authentication:: 2065:: PS:: Domain Name System Security Extensions:: (Updates RFC1034) (Obsoletes RFC1035) 2059:: I:: RADIUS Accounting:: 2058:: PS:: Remote Authentication Dial In User Service (RADIUS):: 2057:: I:: Source directed access control on the Internet.:: 2040:: I:: "The RC5, RC5-CBC, RC5-CBC-Pad, and RC5-CTS Algorithms":: 2025:: PS:: The Simple Public-Key GSS-API Mechanism (SPKM):: 2015:: :: MIME Security with Pretty Good Privacy (PGP):: 1984:: I:: IAB and IESG Statement on Cryptographic Technology and the Internet:: 1969:: I:: The PPP DES Encryption Protocol (DESE):: 1968:: PS:: The PPP Encryption Control Protocol (ECP):: 1964:: PS:: The Kerberos Version 5 GSS-API Mechanism:: 1961:: PS:: GSS-API Authentication Method for SOCKS Version 5:: 1949:: E:: Scalable Multicast Key Distribution:: 1948:: I:: Defending Against Sequence Number Attacks:: 1938:: PS:: A One-Time Password System:: 1929:: PS:: Username/Password Authentication for SOCKS V5:: 1928:: PS:: SOCKS Protocol Version 5:: 1898:: I:: CyberCash Credit Card Protocol Version 0.8:: 1858:: I:: Security Considerations for IP Fragment Filtering:: 1852:: E:: IP Authentication using Keyed SHA:: 1851:: E:: The ESP Triple DES-CBC Transform:: 1829:: PS:: The ESP DES-CBC Transform:: 1828:: PS:: IP Authentication using Keyed MD5:: 1827:: PS:: IP Encapsulating Security Payload (ESP):: 1826:: PS:: IP Authentication Header:: 1825:: PS:: Security Architecture for the Internet Protocol:: 1824:: I:: The Exponential Security System TESS: An Identity-Based Cryptographic Protocol for Authenticated Key-Exchange (E.I.S.S.-Report 1995/4):: 1760:: I:: The S/KEY One-Time Password System:: 1751:: I:: A Convention for Human-Readable 128-bit Keys:: 1750:: I:: Randomness Recommendations for Security:: 1704:: I:: On Internet Authentication:: 1675:: I:: Security Concerns for IPng:: 1579:: I:: Firewall-Friendly FTP:: 1535:: I:: A Security Problem and Proposed Correction With Widely Deployed DNS Software:: 1511:: I:: Common Authentication Technology Overview:: 1510:: PS:: The Kerberos Network Authentication Service (V5):: 1509:: PS:: Generic Security Service API : C-bindings:: 1508:: PS:: Generic Security Service Application Program Interface:: (Obsoleted by RFC2078) 1507:: E:: DASS - Distributed Authentication Security Service:: 1492:: I:: "An Access Control Protocol, Sometimes Called TACACS":: 1457:: I:: Security Label Framework for the Internet:: 1455:: E:: Physical Link Security Type of Service:: 1424:: PS:: Privacy Enhancement for Internet Electronic Mail: Part IV: Key Certification and Related Services:: 1423:: PS:: "Privacy Enhancement for Internet Electronic Mail: Part III: Algorithms, Modes, and Identifiers":: (Obsoletes RFC1115) 1422:: PS:: Privacy Enhancement for Internet Electronic Mail: Part II: Certificate-Based Key Management:: (Obsoletes RFC1114) 1421:: PS:: Privacy Enhancement for Internet Electronic Mail: Part I: Message Encryption and Authentication Procedures:: (Obsoletes RFC1113) 1416:: E:: Telnet Authentication Option:: (Obsoletes RFC1409) 1412:: E:: Telnet Authentication : SPX:: 1411:: E:: Telnet Authentication: Kerberos Version 4:: 1409:: E:: Telnet Authentication Option:: (Obsoleted by RFC1416) 1408:: H:: Telnet Environment Option:: (Updated by RFC1571) 1321:: I:: The MD5 Message-Digest Algorithm:: 1320:: I:: The MD4 Message-Digest Algorithm:: (Obsoletes RFC1186) 1319:: I:: The MD2 Message-Digest Algorithm:: (Updates RFC1115) 1281:: I:: Guidelines for the Secure Operation of the Internet:: 1244:: I:: Site Security Handbook:: (FYI 8) 1186:: I:: The MD4 Message Digest Algorithm:: (Obsoleted by RFC1320) 1170:: I:: Public Key Standards and Licenses:: 1156:: S:: Management Information Base for Network Management of TCP/IP-based internets:: (Updates RFC1066) (Obsoleted by RFC1158) 1115:: H:: "Privacy enhancement for Internet electronic mail: Part III - algorithms, modes, and identifiers [Draft]":: (Obsoleted by RFC1423) (Updated by RFC1319) 1114:: H:: Privacy enhancement for Internet electronic mail: Part II - certificate-based key management [Draft]:: (Obsoleted by RFC1422) 1113:: H:: Privacy enhancement for Internet electronic mail: Part I - message encipherment and authentication procedures [Draft]:: (Obsoletes RFC0989) (Obsoleted by RFC1421) 1108:: PS:: U.S. Department of Defense Security Options for the Internet Protocol:: (Obsoletes RFC1038) 1040:: :: Privacy enhancement for Internet electronic mail: Part I: Message encipherment and authentication procedures:: (Obsoletes RFC0989) 1038:: :: Draft revised IP security option:: (Obsoleted by RFC1108) 1004:: E:: Distributed-protocol authentication scheme:: 989:: :: Privacy enhancement for Internet electronic mail: Part I: Message encipherment and authentication procedures:: "(Obsoleted by RFC1113, RFC1040) " 972:: :: Password Generator Protocol:: 931:: E:: Authentication server:: (Obsoletes RFC0912) (Obsoleted by RFC1413) 927:: :: TACACS user identification Telnet option:: 912:: :: Authentication service:: (Obsoleted by RFC0931) 644:: :: On the problem of signature authentication for network mail:: ====================================================================== Virtual Terminal 2066:: E:: TELNET CHARSET Option:: 1647:: PS:: TN3270 Enhancements:: 1646:: I:: TN3270 Extensions for LUname and Printer Selection:: 1576:: I:: TN3270 Current Practices:: 1572:: PS:: Telnet Environment Option:: 1571:: I:: Telnet Environment Option Interoperability Issues:: (Updates RFC1408) 1372:: PS:: Telnet Remote Flow Control Option:: (Obsoletes RFC1080) 1282:: I:: BSD Rlogin:: (Obsoletes RFC1258) 1258:: I:: BSD Rlogin:: (Obsoleted by RFC1282) 1221:: :: Host Access Protocol (HAP) Specification - Version 2:: (Updates RFC0907) 1205:: :: 5250 Telnet Interface:: 1184:: DS:: Telnet Linemode Option:: (Obsoletes RFC1116) 1143:: :: The Q Method of Implementing TELNET Option Negotiation:: 1116:: PS:: Telnet Linemode option:: (Obsoleted by RFC1184) 1097:: :: Telnet subliminal-message option:: 1096:: :: Telnet X display location option:: 1091:: :: Telnet terminal-type option:: (Obsoletes RFC0930) 1080:: :: Telnet remote flow control option:: (Obsoleted by RFC1372) 1079:: :: Telnet terminal speed option:: 1073:: :: Telnet window size option:: 1053:: :: Telnet X.3 PAD option:: 1043:: :: Telnet Data Entry Terminal option: DODIIS implementation:: (Updates RFC0732) 1041:: :: Telnet 3270 regime option:: 1013:: :: "X Window System Protocol, version 11: Alpha update April 1987":: 1005:: :: ARPANET AHIP-E Host Access Protocol enhanced AHIP:: 946:: :: Telnet terminal location number option:: 933:: :: Output marking Telnet option:: 930:: :: Telnet terminal type option:: (Obsoletes RFC0884) (Obsoleted by RFC1091) 929:: :: Proposed Host-Front End Protocol:: 907:: S:: Host Access Protocol specification:: (Updated by RFC1221) 885:: :: Telnet end of record option:: 884:: :: Telnet terminal type option:: (Obsoleted by RFC0930) 878:: :: ARPANET 1822L Host Access Protocol:: (Obsoletes RFC0851) 861:: :: Telnet extended options: List option:: 860:: S:: Telnet timing mark option:: (STD 31) 859:: S:: Telnet status option:: (Obsoletes RFC0651) (STD 30) 858:: S:: Telnet Suppress Go Ahead option:: (STD 29) 857:: S:: Telnet echo option:: (STD 28) 856:: S:: Telnet binary transmission:: (STD 27) 855:: S:: Telnet option specifications:: (STD 8) 854:: S:: Telnet Protocol specification:: (Obsoletes RFC0764) (STD 8) 851:: :: ARPANET 1822L Host Access Protocol:: (Obsoletes RFC0802) (Obsoleted by RFC0878) 818:: H:: Remote User Telnet service:: 802:: :: ARPANET 1822L Host Access Protocol:: (Obsoleted by RFC0851) 782:: :: Virtual Terminal management model:: 779:: :: Telnet send-location option:: 764:: :: Telnet Protocol specification:: (Obsoleted by RFC0854) 749:: :: Telnet SUPDUP-Output option:: 748:: :: Telnet randomly-lose option:: 747:: :: Recent extensions to the SUPDUP Protocol:: 746:: :: SUPDUP graphics extension:: 736:: :: Telnet SUPDUP option:: 735:: :: Revised Telnet byte macro option:: (Obsoletes RFC0729) 734:: H:: SUPDUP Protocol:: 732:: :: Telnet Data Entry Terminal option:: (Obsoletes RFC0731) (Updated by RFC1043) 731:: :: Telnet Data Entry Terminal option:: (Obsoleted by RFC0732) 729:: :: Telnet byte macro option:: (Obsoleted by RFC0735) 728:: :: Minor pitfall in the Telnet Protocol:: 727:: :: Telnet logout option:: 726:: :: Remote Controlled Transmission and Echoing Telnet option:: 721:: :: Out-of-band control signals in a Host-to-Host Protocol:: 719:: :: Discussion on RCTE:: 718:: :: Comments on RCTE from the Tenex implementation experience:: 703:: :: "July, 1975, survey of New-Protocol Telnet Servers":: 702:: :: "September, 1974, survey of New-Protocol Telnet servers":: 701:: :: "August, 1974, survey of New-Protocol Telnet servers":: 698:: :: Telnet extended ASCII option:: 688:: :: Tentative schedule for the new Telnet implementation for the TIP :: 679:: :: "February, 1975, survey of New-Protocol Telnet servers":: 669:: :: "November, 1974, survey of New-Protocol Telnet servers":: 659:: :: Announcing additional Telnet options:: 658:: :: Telnet output linefeed disposition:: 657:: :: Telnet output vertical tab disposition option:: 656:: :: Telnet output vertical tabstops option:: 655:: :: Telnet output formfeed disposition option:: 654:: :: Telnet output horizontal tab disposition option:: 653:: :: Telnet output horizontal tabstops option:: 652:: :: Telnet output carriage-return disposition option:: 651:: :: Revised Telnet status option:: (Obsoleted by RFC0859) 647:: :: Proposed protocol for connecting host computers to ARPA-like networks via front end processors:: 636:: :: TIP/Tenex reliability improvements:: 600:: :: Interfacing an Illinois plasma terminal to the ARPANET:: 596:: :: Second thoughts on Telnet Go-Ahead:: 595:: :: Second thoughts in defense of the Telnet Go-Ahead:: 587:: :: Announcing new Telnet options:: 563:: :: Comments on the RCTE Telnet option:: 562:: :: Modifications to the Telnet specification:: 560:: :: Remote Controlled Transmission and Echoing Telnet option:: 559:: :: Comments on the new Telnet Protocol and its implementation:: 513:: :: Comments on the new Telnet specifications:: 495:: :: Telnet Protocol specifications:: (Obsoletes RFC0158) 470:: :: Change in socket for TIP news facility:: 466:: :: Telnet logger/server for host LL-67:: 461:: :: Telnet Protocol meeting announcement:: 447:: :: IMP/TIP memory retrofit schedule:: (Obsoletes RFC0434) (Obsoleted by RFC0476) 435:: :: Telnet issues:: (Updates RFC0318) 431:: :: Update on SMFS login and logout:: (Obsoletes RFC0399) 399:: :: SMFS login and logout:: (Updates RFC0122) (Obsoleted by RFC0431) 393:: :: Comments on Telnet Protocol changes:: 386:: :: Letter to TIP users-2:: 377:: :: Using TSO via ARPA Network Virtual Terminal:: 365:: :: Letter to all TIP users:: 364:: :: Serving remote users on the ARPANET:: 352:: :: TIP site information form:: 340:: :: Proposed Telnet changes:: 339:: :: "MLTNET: A ""Multi Telnet"" subsystem for Tenex":: 328:: :: Suggested Telnet Protocol changes:: 318:: :: [Ad hoc Telnet Protocol]:: (Updates RFC0158) (Updated by RFC0435) 311:: :: New console attachments to the USCB host:: 297:: :: TIP message buffers:: 296:: :: DS-1 display system:: 231:: :: Service center standards for remote usage: Auser's view:: 230:: :: Toward reliable operation of minicomputer-based terminals on a TIP:: 216:: :: Telnet access to UCSB's On-Line System:: 215:: :: "NCP, ICP, and Telnet: The Terminal IMP implementation":: 206:: :: User Telnet - description of an initial implementation:: 205:: :: NETCRT - a character display protocol:: 177:: :: Device independent graphical display description:: (Updates RFC0125) (Updated by RFC0181) 158:: :: Telnet Protocol: A proposed document:: (Updates RFC0139) (Obsoleted by RFC0495) (Updated by RFC0318) 139:: :: Discussion of Telnet Protocol:: (Updates RFC0137) (Updated by RFC0158) 137:: :: Telnet Protocol - a proposed document:: (Updated by RFC0139) 110:: :: Conventions for using an IBM 2741 terminal as a user console for access to network server hosts:: (Updated by RFC0135) 97:: :: First cut at a proposed Telnet Protocol:: ====================================================================== Other 2123:: I:: Traffic Flow Measurement: Experiences with NeTraMet:: 2121:: I:: Issues affecting MARS Cluster Size:: 2119:: BC:: Key words for use in RFCs to Indicate Requirement Levels:: 2101:: I:: IPv4 Address Behaviour Today:: 2100:: I:: The Naming of Hosts:: 2099:: I:: Request for Comments Summary RFC Numbers 2000-2099:: 2083:: I:: PNG (Portable Network Graphics) Specification Version 1.0:: 2071:: I:: Network Renumbering Overview: Why would I want it and what is it anyway?:: 2050:: BC:: INTERNET REGISTRY IP ALLOCATION GUIDELINES:: (Obsoletes RFC1466) 2036:: I:: Observations on the use of Components of the Class A Address Space within the Internet:: 2031:: I:: IETF-ISOC relationship:: 2028:: BC:: The Organizations Involved in the IETF Standards Process:: 2027:: BC:: "IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees":: 2026:: BC:: The Internet Standards Process -- Revision 3:: (Obsoletes RFC1602) 2014:: BC:: IRTF Research Group Guidelines and Procedures:: 2007:: I:: Catalogue of Network Training Materials:: (FYI 29) 2000:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS:: (STD 1) 1999:: I:: Request for Comments Summary RFC Numbers 1900-1999:: 1988:: I:: Conditional Grant of Rights to Specific Hewlett-Packard Patents In Conjunction With the Internet Engineering Task Force's Internet-Standard Network Management Framework:: 1983:: I:: Internet Users' Glossary:: (FYI 18) (Obsoletes RFC1392) 1958:: I:: Architectural Principles of the Internet:: 1952:: I:: GZIP file format specification version 4.3:: 1951:: I:: DEFLATE Compressed Data Format Specification version 1.3:: 1950:: I:: ZLIB Compressed Data Format Specification version 3.3:: 1941:: I:: Frequently Asked Questions for Schools:: (FYI 22) (Obsoletes RFC1578) 1935:: I:: "What is the Internet, Anyway?":: 1920:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS:: (Obsoletes RFC1880) (STD 1) 1900:: I:: Renumbering Needs Work:: 1899:: I:: Request for Comments Summary RFC Numbers 1800-1899:: 1882:: I:: The 12-Days of Technology Before Christmas:: 1880:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS:: (Obsoletes RFC1800) (STD 1) (Obsoleted by RFC1920) 1879:: I:: Class A Subnet Experiment Results and Recommendations:: 1875:: I:: UNINETT PCA Policy Statements:: 1871:: BC:: Addendum to RFC 1602 -- Variance Procedure:: (Updates RFC1602) 1855:: I:: Netiquette Guidelines:: (FYI 28) 1822:: I:: A Grant of Rights to Use a Specific IBM patent with Photuris:: 1818:: S:: Best Current Practices:: 1816:: I:: U.S. Government Internet Domain Names:: (Obsoletes RFC1811) 1814:: I:: Unique Addresses are Good:: 1811:: I:: U.S. Government Internet Domain Names:: (Obsoleted by RFC1816) 1810:: I:: Report on MD5 Performance:: 1805:: I:: Location-Independent Data/Software Integrity Protocol:: 1802:: I:: Introducing Project Long Bud: Internet Pilot Project for the Deployment of X.500 Directory Information in Support of X.400 Routing:: 1800:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS:: (Obsoletes RFC1780) (STD 1) (Obsoleted by RFC1880) 1799:: I:: Request for Comments Summary RFC Numbers 1700-1799:: 1797:: E:: Class A Subnet Experiment:: 1796:: I:: Not All RFCs are Standards:: 1790:: I:: "An Agreement between the Internet Society and Sun Microsystems, Inc. in the Matter of ONC RPC and XDR Protocols":: 1780:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS:: (Obsoletes RFC1720) (STD 1) (Obsoleted by RFC1800) 1776:: I:: The Address is the Message:: 1775:: I:: "To Be ""On"" the Internet":: 1758:: I:: NADF Standing Documents: A Brief Overview:: 1746:: I:: Ways to Define User Expectations:: 1739:: I:: A Primer On Internet and TCP/IP Tools:: 1720:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS:: (Obsoletes RFC1610) (STD 1) (Obsoleted by RFC1780) 1718:: I:: The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force:: (FYI 17) (Obsoletes RFC1539) 1715:: I:: The H Ratio for Address Assignment Efficiency:: 1709:: I:: K-12 Internetworking Guidelines:: (FYI 26) 1700:: S:: ASSIGNED NUMBERS:: (Obsoletes RFC1340) (STD 2) 1699:: I:: Request for Comments Summary RFC Numbers 1600-1699:: 1691:: I:: The Document Architecture for the Cornell Digital Library:: 1690:: I:: Introducing the Internet Engineering and Planning Group (IEPG):: 1689:: I:: A Status Report on Networked Information Retrieval: Tools and Groups:: (FYI 25) (RTR 13) 1640:: I:: The Process for Organization of Internet Standards Working Group (POISED):: 1636:: I:: "Report of IAB Workshop on Security in the Internet Architecture - February 8-10, 1994":: 1635:: I:: How to Use Anonymous FTP:: (FYI 24) 1627:: I:: Network 10 Considered Harmful (Some Practices Shouldn't be Codified):: (Updated by RFC1918) 1610:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS:: (Obsoletes RFC1600) (STD 1) (Obsoleted by RFC1720) 1607:: I:: A VIEW FROM THE 21ST CENTURY:: 1606:: I:: A Historical Perspective On The Usage Of IP Version 9:: 1603:: I:: IETF Working Group Guidelines and Procedures:: 1602:: I:: The Internet Standards Process -- Revision 2:: (Obsoletes RFC1310) (Obsoleted by RFC2026) (Updated by RFC1871) 1601:: I:: Charter of the Internet Architecture Board (IAB):: (Obsoletes RFC1358) 1600:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS:: (Obsoletes RFC1540) (STD 1) (Obsoleted by RFC1610) 1599:: I:: Request for Comments Summary RFC Numbers 1500 - 1599:: 1597:: I:: Address Allocation for Private Internets:: (Obsoleted by RFC1918) 1594:: I:: FYI on Questions and Answer Answers to Commonly asked ``New Internet User'' Questions:: (FYI 4) (Obsoletes RFC1325) 1580:: I:: Guide to Network Resource Tools:: (FYI 23) 1578:: I:: FYI on Questions and Answers: Answers to Commonly Asked ``Primary and Secondary School Internet User'' Questions:: (FYI 22) (Obsoleted by RFC1941) 1574:: I:: Essential Tools for the OSI Internet:: (Obsoletes RFC1139) 1550:: I:: IP: Next Generation (IPng) White Paper Solicitation:: 1543:: I:: Instructions to RFC Authors:: (Obsoletes RFC1111) 1540:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS:: (Obsoletes RFC1500) (STD 1) (Obsoleted by RFC1600) 1539:: I:: The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force:: (FYI 17) (Obsoletes RFC1391) (Obsoleted by RFC1718) 1527:: I:: What Should We Plan Given the Dilemma of the Network?:: 1501:: I:: OS/2 User Group:: 1500:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS:: (Obsoletes RFC1410) (STD 1) (Obsoleted by RFC1540) 1499:: I:: Request for Comments Summary RFC Numbers 1400-1499:: 1481:: I:: IAB Recommendation for an Intermediate Strategy to Address the Issue of Scaling:: 1467:: I:: Status of CIDR Deployment in the Internet:: (Obsoletes RFC1367) 1463:: I:: FYI on Introducing the Internet--A Short Bibliography of Introductory Internetworking Readings for the Network Novice:: (FYI 19) 1462:: I:: FYI on ``What is the Internet?'':: (FYI 20) 1438:: I:: Internet Engineering Task Force Statements Of Boredom (SOBs):: 1432:: I:: Recent Internet Books:: 1417:: I:: NADF Standing Documents: A Brief Overview:: (Obsoletes RFC1295) 1410:: S:: IAB OFFICIAL PROTOCOL STANDARDS:: (Obsoletes RFC1360) (STD 1) (Obsoleted by RFC1500) 1402:: I:: There's Gold in them thar Networks! Searching for Treasure in all the Wrong Places:: (FYI 10) (Obsoletes RFC1290) 1401:: I:: Correspondence between the IAB and DISA on the use of DNS throughout the Internet:: 1399:: I:: Request for Comments Summary RFC Numbers 1300-1399:: 1396:: I:: The Process for Organization of Internet Standards Working Group (POISED):: 1392:: I:: Internet Users' Glossary:: (FYI 18) (Obsoleted by RFC1983) 1391:: I:: The Tao of IETF: A Guide for New Attendees of the Internet Engineering Task Force:: (FYI 17) (Obsoleted by RFC1539) 1367:: I:: Schedule for IP Address Space Management Guidelines:: (Obsoleted by RFC1467) 1366:: I:: Guidelines for Management of IP Address Space:: (Obsoleted by RFC1466) 1360:: S:: IAB OFFICIAL PROTOCOL STANDARDS:: (Obsoletes RFC1280) (STD 1) (Obsoleted by RFC1410) 1359:: I:: Connecting to the Internet What Connecting Institutions Should Anticipate:: (FYI 16) 1358:: I:: Charter of the Internet Architecture Board (IAB):: (Obsoleted by RFC1601) 1349:: PS:: Type of Service in the Internet Protocol Suite:: (Updates RFC1248) 1340:: S:: ASSIGNED NUMBERS:: (Obsoletes RFC1060) (STD 2) (Obsoleted by RFC1700) 1336:: I:: "Who's Who in the Internet Biographies of IAB, IESG and IRSG Members":: (FYI 9) (Obsoletes RFC1251) 1325:: I:: FYI on Questions and Answers Answers to Commonly asked ``New Internet User'' Questions:: (FYI 4) (Obsoletes RFC1206) (Obsoleted by RFC1594) 1324:: I:: A Discussion on Computer Network Conferencing:: 1311:: I:: Introduction to the STD Notes:: 1310:: I:: The Internet Standards Process:: (Obsoleted by RFC1602) 1300:: I:: Remembrances of Things Past:: 1299:: I:: Request for Comments Summary RFC Numbers 1200-1299:: 1297:: I:: NOC Internal Integrated Trouble Ticket System Functional Specification Wishlist (``NOC TT REQUIREMENTS''):: 1296:: I:: Internet Growth (1981-1991):: 1295:: I:: User Bill of Rights for entries and listings in the Public Directory:: (Obsoleted by RFC1417) 1291:: I:: Mid-Level Networks: Potential Technical Services:: 1290:: I:: There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places:: (FYI 10) (Obsoleted by RFC1402) 1287:: I:: Towards the Future Internet Architecture:: 1280:: S:: IAB OFFICIAL PROTOCOL STANDARDS:: (Obsoletes RFC1250) (STD 1) (Obsoleted by RFC1360) 1261:: I:: Transition of NIC Services:: 1259:: I:: Building The Open Road: The NREN As Test-Bed For The National Public Network:: 1251:: :: "Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members":: (FYI 9) (Obsoleted by RFC1336) 1250:: S:: IAB Official Protocol Standards:: (Obsoletes RFC1200) (STD 1) (Obsoleted by RFC1280) 1249:: I:: DIXIE Protocol Specification:: 1217:: :: Memo from the Consortium for Slow Commotion Research (CSCR):: 1216:: :: Gigabit Network Economics and Paradigm Shifts:: 1208:: :: A Glossary of Networking Terms:: 1207:: :: Answers to Commonly asked ``Experienced Internet User'' Questions:: (FYI 7) 1206:: :: FYI on Questions and Answers - Answers to Commonly asked ``New Internet User'' Questions:: (FYI 4) (Obsoletes RFC1177) (Obsoleted by RFC1325) 1200:: S:: IAB Official Protocol Standards:: (Obsoletes RFC1140) (STD 1) (Obsoleted by RFC1250) 1199:: I:: Request for Comments Summary RFC Numbers 1100-1199:: 1198:: I:: FYI on the X Window System:: 1192:: :: Commercialization of the Internet Summary Report:: 1181:: :: RIPE Terms of Reference:: 1180:: :: A TCP/IP Tutorial:: 1178:: :: Choosing a Name for Your Computer:: (FYI 5) 1177:: :: FYI on Questions and Answers - Answers to Commonly Asked ``New Internet User'' Questions:: (FYI 4) (Obsoleted by RFC1206) 1175:: :: FYI on Where to Start - A Bibliography of Internetworking Information:: (FYI 3) 1174:: I:: "IAB Recommended Policy on Distributing Internet Identifier Assignment and IAB Recommended Policy Change to Internet ""Connected"" Status":: 1173:: :: "Responsibilities of Host and Network Managers A Summary of the ""Oral Tradition"" of the Internet":: 1169:: :: Explaining the Role of GOSIP:: 1167:: :: Thoughts on the National Research and Education Network:: 1160:: :: The Internet Activities Board:: (Updates RFC1120) 1152:: :: Workshop Report: Internet Research Steering Group Workshop on Very-High-Speed Networks:: 1150:: I:: F.Y.I. on F.Y.I.: Introduction to the F.Y.I. notes:: (FYI 1) 1149:: :: A Standard for the Transmission of IP Datagrams on Avian Carriers:: 1147:: I:: FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices:: (FYI 2) (Obsoleted by RFC1470) 1140:: S:: IAB Official Protocol Standards:: (Obsoletes RFC1130) (STD 1) (Obsoleted by RFC1200) 1135:: :: Helminthiasis of the Internet:: 1130:: S:: IAB official protocol standards:: (Obsoletes RFC1100) (STD 1) (Obsoleted by RFC1140) 1127:: :: Perspective on the Host Requirements RFCs:: 1121:: :: Act one - the poems:: 1120:: :: Internet Activities Board:: (Updated by RFC1160) 1118:: :: Hitchhikers guide to the Internet:: 1117:: :: Internet numbers:: (Obsoletes RFC1062) 1111:: :: Request for comments on Request for Comments: Instructions to RFC authors:: (Obsoletes RFC0825) (Obsoleted by RFC1543) 1100:: S:: IAB official protocol standards:: (Obsoletes RFC1083) (STD 1) (Obsoleted by RFC1130) 1099:: I:: Request for Comments Summary RFC Numbers 1000-1099:: 1093:: :: NSFNET routing architecture:: 1087:: :: Ethics and the Internet:: 1083:: S:: IAB official protocol standards:: (STD 1) (Obsoleted by RFC1100) 1077:: :: Critical issues in high bandwidth networking:: 1076:: :: HEMS monitoring and control language:: (Obsoletes RFC1023) 1060:: S:: ASSIGNED NUMBERS:: (Obsoletes RFC1010) (STD 2) (Obsoleted by RFC1340) 1039:: :: DoD statement on Open Systems Interconnection protocols:: (Obsoletes RFC0945) 1020:: :: Internet numbers:: (Obsoletes RFC0997) (Obsoleted by RFC1062) 1019:: :: Report of the Workshop on Environments for Computational Mathematics:: 1018:: :: Some comments on SQuID:: 1017:: :: Network requirements for scientific research: Internet task force on scientific computing:: 1015:: :: Implementation plan for interagency research Internet:: 1014:: :: XDR: External Data Representation standard:: 1000:: :: Request For Comments reference guide:: (Obsoletes RFC0999) 999:: :: Requests For Comments summary notes: 900-999:: (Obsoleted by RFC1000) 997:: :: Internet numbers:: (Updates RFC0990) (Obsoleted by RFC1020) 992:: :: On communication support for fault tolerant process groups:: 991:: S:: Official ARPA-Internet protocols:: (Obsoletes RFC0961) (STD 1) (Obsoleted by RFC1011) 990:: :: Assigned numbers:: (Obsoletes RFC0960) (Obsoleted by RFC1010) (Updated by RFC0997) 980:: :: Protocol document order information:: 979:: :: PSN End-to-End functional specification:: 968:: :: Twas the night before start-up:: 967:: :: All victims together:: 961:: S:: Official ARPA-Internet protocols:: (Obsoletes RFC0944) (STD 1) (Obsoleted by RFC0991) 960:: :: Assigned numbers:: (Obsoletes RFC0943) (Obsoleted by RFC0990) 945:: :: DoD statement on the NRC report:: (Obsoleted by RFC1039) 944:: S:: Official ARPA-Internet protocols:: (Obsoletes RFC0924) (STD 1) (Obsoleted by RFC0961) 943:: :: Assigned numbers:: (Obsoletes RFC0923) (Obsoleted by RFC0960) 939:: :: Executive summary of the NRC report on transport protocols for Department of Defense data networks:: 938:: E:: Internet Reliable Transaction Protocol functional and interface specification:: 928:: :: Introduction to proposed DoD standard H-FP:: 923:: :: Assigned numbers:: (Obsoletes RFC0900) (Obsoleted by RFC0943) 909:: E:: Loader Debugger Protocol:: 908:: E:: Reliable Data Protocol:: (Updated by RFC1151) 902:: :: ARPA Internet Protocol policy:: 901:: S:: Official ARPA-Internet protocols:: (Obsoletes RFC0880) (STD 1) (Obsoleted by RFC0924) 900:: :: Assigned Numbers:: (Obsoletes RFC0870) (Obsoleted by RFC0923) 899:: :: Request For Comments summary notes: 800-899:: 880:: S:: Official protocols:: (Obsoletes RFC0840) (STD 1) (Obsoleted by RFC0901) 873:: :: Illusion of vendor support:: 870:: :: Assigned numbers:: (Obsoletes RFC0820) (Obsoleted by RFC0900) 869:: H:: Host Monitoring Protocol:: 852:: :: ARPANET short blocking feature:: 847:: :: Summary of Smallberg surveys:: (Obsoletes RFC0846) 846:: :: Who talks TCP? - survey of 22 February 1983:: (Obsoletes RFC0845) (Obsoleted by RFC0847) 845:: :: Who talks TCP? - survey of 15 February 1983:: (Obsoletes RFC0843) (Obsoleted by RFC0846) 844:: :: "Who talks ICMP, too? - Survey of 18 February 1983":: (Updates RFC0843) 843:: :: Who talks TCP? - survey of 8 February 83:: (Obsoletes RFC0842) (Obsoleted by RFC0845) (Updated by RFC0844) 842:: :: Who talks TCP? - survey of 1 February 83:: (Obsoletes RFC0839) (Obsoleted by RFC0843) 840:: S:: Official protocols:: (STD 1) (Obsoleted by RFC0880) 839:: :: Who talks TCP?:: (Obsoletes RFC0838) (Obsoleted by RFC0842) 838:: :: Who talks TCP?:: (Obsoletes RFC0837) (Obsoleted by RFC0839) 837:: :: Who talks TCP?:: (Obsoletes RFC0836) (Obsoleted by RFC0838) 836:: :: Who talks TCP?:: (Obsoletes RFC0835) (Obsoleted by RFC0837) 835:: :: Who talks TCP?:: (Obsoletes RFC0834) (Obsoleted by RFC0836) 834:: :: Who talks TCP?:: (Obsoletes RFC0833) (Obsoleted by RFC0835) 833:: :: Who talks TCP?:: (Obsoletes RFC0832) (Obsoleted by RFC0834) 832:: :: Who talks TCP?:: (Obsoleted by RFC0833) 831:: :: Backup access to the European side of SATNET:: 828:: :: "Data communications: IFIP's international ""network"" of experts":: 825:: :: Request for comments on Requests For Comments:: (Obsoleted by RFC1111) 820:: :: Assigned numbers:: (Obsoletes RFC0790) (Obsoleted by RFC0870) 817:: :: Modularity and efficiency in protocol implementation:: 816:: :: Fault isolation and recovery:: 806:: :: Proposed Federal Information Processing Standard: Specification for message format for computer based message systems:: (Obsoleted by RFC0841) 800:: :: Request For Comments summary notes: 700-799:: 794:: :: Pre-emption:: 790:: :: Assigned numbers:: (Obsoletes RFC0776) (Obsoleted by RFC0820) 776:: :: Assigned numbers:: (Obsoletes RFC0770) (Obsoleted by RFC0790) 774:: :: Internet Protocol Handbook: Table of contents:: (Obsoletes RFC0766) 770:: :: Assigned numbers:: (Obsoletes RFC0762) (Obsoleted by RFC0776) 766:: :: Internet Protocol Handbook: Table of contents:: (Obsoleted by RFC0774) 762:: :: Assigned numbers:: (Obsoletes RFC0758) (Obsoleted by RFC0770) 758:: :: Assigned numbers:: (Obsoletes RFC0755) (Obsoleted by RFC0762) 755:: :: Assigned numbers:: (Obsoletes RFC0750) (Obsoleted by RFC0758) 750:: :: Assigned numbers:: (Obsoletes RFC0739) (Obsoleted by RFC0755) 745:: :: JANUS interface specifications:: 739:: :: Assigned numbers:: (Obsoletes RFC0604) (Obsoleted by RFC0750) 717:: :: Assigned network numbers:: 716:: :: Interim revision to Appendix F of BBN 1822:: 708:: :: Elements of a distributed programming system:: 705:: :: Front-end Protocol B6700 version:: 700:: :: Protocol experiment:: 699:: :: Request For Comments summary notes: 600-699:: 694:: :: Protocol information:: 686:: :: Leaving well enough alone:: 684:: :: Commentary on procedure calling as a network protocol:: 681:: :: Network UNIX:: 678:: :: Standard file formats:: 677:: :: Maintenance of duplicate databases:: 672:: :: Multi-site data collection facility:: 671:: :: Note on Reconnection Protocol:: 667:: :: BBN host ports:: 666:: :: Specification of the Unified User-Level Protocol:: 663:: :: Lost message detection and recovery protocol:: 661:: :: Protocol information:: 645:: :: Network Standard Data Specification syntax:: 643:: :: Network Debugging Protocol:: 642:: :: Ready line philosophy and implementation:: 638:: :: IMP/TIP preventive maintenance schedule:: (Obsoletes RFC0633) 637:: :: Change of network address for SU-DSL:: 635:: :: Assessment of ARPANET protocols:: 634:: :: Change in network address for Haskins Lab:: 631:: :: International meeting on minicomputers and data communication: Call for papers:: 629:: :: Scenario for using the Network Journal:: 628:: :: Status of RFC numbers and a note on pre-assigned journal numbers :: 621:: :: NIC user directories at SRI ARC:: 617:: :: Note on socket number assignment:: 609:: :: Statement of upcoming move of NIC/NLS service:: 604:: :: Assigned link numbers:: (Obsoletes RFC0317) (Obsoleted by RFC0739) 603:: :: Response to RFC 597: Host status:: (Updates RFC0597) (Updated by RFC0613) 602:: :: The stockings were hung by the chimney with care:: 598:: :: "RFC index - December 5, 1973":: 597:: :: Host status:: (Updated by RFC0603) 590:: :: MULTICS address change:: 588:: :: London node is now up:: 585:: :: ARPANET users interest working group meeting:: 584:: :: Charter for ARPANET Users Interest Working Group:: 582:: :: Comments on RFC 580: Machine readable protocols:: (Updates RFC0580) 581:: :: Corrections to RFC 560: Remote Controlled Transmission and Echoing Telnet option:: 580:: :: Note to protocol designers and implementers:: (Updated by RFC0582) 578:: :: Using MIT-Mathlab MACSYMA from MIT-DMS Muddle:: 569:: H:: NETED: A common editor for the ARPA network:: 552:: :: Single access to standard protocols:: 547:: :: Change to the Very Distant Host specification:: 544:: :: Locating on-line documentation at SRI-ARC:: 537:: :: Announcement of NGG meeting July 16-17:: 530:: :: Report on the Survey project:: 529:: :: Note on protocol synch sequences:: 527:: :: ARPAWOCKY:: 526:: :: Technical meeting: Digital image processing software systems:: 523:: :: SURVEY is in operation again:: 519:: :: Resource evaluation:: 518:: :: ARPANET accounts:: 515:: :: Specifications for datalanguage: Version 0/9:: 503:: :: Socket number list:: (Obsoletes RFC0433) 496:: :: TNLS quick reference card is available:: 494:: :: Availability of MIX and MIXAL in the Network:: 492:: :: Response to RFC 467:: (Updates RFC0467) 491:: :: "What is ""Free""?":: 483:: :: Cancellation of the resource notebook framework meeting:: 474:: :: Announcement of NGWG meeting: Call for papers:: 464:: :: Resource notebook framework:: 462:: :: Responding to user needs:: 457:: :: TIPUG:: 456:: :: Memorandum: Date change of mail meeting:: 441:: :: Inter-Entity Communication - an experiment:: 440:: :: Scheduled network software maintenance:: 439:: :: PARRY encounters the DOCTOR:: 433:: :: Socket number list:: (Obsoletes RFC0349) (Obsoleted by RFC0503) 432:: :: Network logical map:: 425:: :: But my NCP costs $500 a day:: 419:: :: To: Network liaisons and station agents:: 405:: :: Correction to RFC 404:: (Obsoletes RFC0404) 404:: :: Host address changes involving Rand and ISI:: (Obsoleted by RFC0405) 403:: :: Desirability of a network 1108 service:: 402:: :: ARPA Network mailing lists:: (Obsoletes RFC0363) 401:: :: Conversion of NGP-0 coordinates to device specific coordinates :: 390:: :: TSO scenario:: 379:: :: Using TSO at CCN:: 376:: :: Network host status:: (Obsoletes RFC0370) 372:: :: Notes on a conversation with Bob Kahn on the ICCC:: 371:: :: Demonstration at International Computer Communications Conference:: 370:: :: Network host status:: (Obsoletes RFC0367) (Obsoleted by RFC0376) 363:: :: ARPA Network mailing lists:: (Obsoletes RFC0329) (Obsoleted by RFC0402) 356:: :: ARPA Network Control Center:: 355:: :: Response to NWG/RFC 346:: 350:: :: User accounts for UCSB On-Line System:: 349:: :: Proposed standard socket numbers:: (Obsoleted by RFC0433) 345:: :: Interest in mixed integer programming MPSX on NIC 360/91 at CCN:: 334:: :: Network use on May 8:: 331:: :: IMP System change notification:: (Obsoleted by RFC0343) 330:: :: Network host status:: (Obsoletes RFC0326) (Obsoleted by RFC0332) 329:: :: ARPA Network mailing lists:: (Obsoletes RFC0303) (Obsoleted by RFC0363) 327:: :: Data and File Transfer workshop notes:: 322:: :: Well known socket numbers:: 321:: :: CBI networking activity at MITRE:: 320:: :: Workshop on hard copy line printers:: 319:: :: Network host status:: (Obsoletes RFC0315) (Obsoleted by RFC0326) 317:: :: Official Host-Host Protocol modification: Assigned link numbers:: (Obsoleted by RFC0604) 316:: :: ARPA Network Data Management Working Group:: 315:: :: Network host status:: (Obsoletes RFC0306) (Obsoleted by RFC0319) 313:: :: Computer based instruction:: 305:: :: Unknown host numbers:: 303:: :: ARPA Network mailing lists:: (Obsoletes RFC0300) (Obsoleted by RFC0329) 295:: :: "Report of the Protocol Workshop, 12 October 1971":: 291:: :: Data management meeting announcement:: 290:: :: Computer networks and data sharing: A bibliography:: (Obsoletes RFC0243) 282:: :: Graphics meeting report:: 276:: :: NIC course:: 270:: :: Correction to BBN Report No. 1822 NIC NO 7958:: 269:: :: Some experience with file transfer:: (Updates RFC0122) 263:: :: Very Distant Host interface:: 256:: :: IMPSYS change notification:: 254:: :: Scenarios for using ARPANET computers:: 253:: :: Second Network Graphics meeting details:: 249:: :: Coordination of equipment and supplies purchase:: 246:: :: Network Graphics meeting:: 245:: :: Reservations for Network Group meeting:: 243:: :: Network and data sharing bibliography:: (Obsoleted by RFC0290) 242:: :: Data descriptive language for shared data:: 240:: :: Site status:: (Obsoletes RFC0235) (Obsoleted by RFC0252) 239:: :: Host mnemonics proposed in RFC 226 NIC 7625:: 235:: :: Site status:: (Obsoleted by RFC0240) 234:: :: Network Working Group meeting schedule:: (Updates RFC0222) 232:: :: Postponement of network graphics meeting:: 228:: :: Clarification:: (Updates RFC0070) 225:: :: Rand/UCSB network graphics experiment:: (Updates RFC0074) 223:: :: Network Information Center schedule for network users:: 219:: :: User's view of the datacomputer:: 218:: :: Changing the IMP status reporting facility:: 214:: :: Network checkpoint:: (Obsoletes RFC0198) 213:: :: IMP System change notification:: 211:: :: ARPA Network mailing lists:: (Obsoletes RFC0168) (Obsoleted by RFC0300) 209:: :: Host/IMP interface documentation:: 208:: :: Address tables:: 207:: :: September Network Working Group meeting:: (Obsoleted by RFC0212) 204:: :: Sockets in use:: 200:: :: RFC list by number:: (Obsoletes RFC0170) 198:: :: Site certification - Lincoln Labs 360/67:: (Obsoletes RFC0193) (Obsoleted by RFC0214) 195:: :: Data computers-data descriptions and access language:: 194:: :: Data Reconfiguration Service - compiler/interpreter implementation notes:: 187:: :: Network/440 protocol concept:: 186:: :: Network graphics loader:: 185:: :: NIC distribution of manuals and handbooks:: 182:: :: Compilation of list of relevant site reports:: 180:: :: File system questionnaire:: 179:: :: Link number assignments:: (Updates RFC0107) 173:: :: Network data management committee meeting announcement:: 171:: :: Data Transfer Protocol:: (Updates RFC0114) (Obsoleted by RFC0264) (Updated by RFC0238) 170:: :: RFC list by number:: (Obsoleted by RFC0200) 169:: :: Computer networks:: 168:: :: ARPA Network mailing lists:: (Obsoletes RFC0155) (Obsoleted by RFC0211) 167:: :: Socket conventions reconsidered:: 164:: :: "Minutes of Network Working Group meeting, 5/16 through 5/19/71 ":: 162:: :: NETBUGGER3:: 160:: :: RFC brief list:: 157:: :: Invitation to the Second Symposium on Problems in the Optimization of Data Communications Systems:: 155:: :: ARPA Network mailing lists:: (Obsoletes RFC0095) (Obsoleted by RFC0168) 154:: :: Exposition style:: (Obsoletes RFC0132) 149:: :: Best laid plans:: (Updates RFC0140) 148:: :: Comments on RFC 123:: (Updates RFC0123) 147:: :: Definition of a socket:: (Updates RFC0129) 140:: :: Agenda for the May NWG meeting:: (Updated by RFC0149) 138:: :: Status report on proposed Data Reconfiguration Service:: 136:: :: Host accounting and administrative procedures:: 135:: :: Response to NWG/RFC 110:: (Updates RFC0110) 132:: :: Typographical error in RFC 107:: (Updates RFC0107) (Obsoleted by RFC0154) 131:: :: Response to RFC 116: May NWG meeting:: (Updates RFC0116) 130:: :: Response to RFC 111: Pressure from the chairman:: (Updates RFC0111) 129:: :: Request for comments on socket name structure:: (Updated by RFC0147) 126:: :: Graphics facilities at Ames Research Center:: 124:: :: Typographical error in RFC 107:: (Updates RFC0107) 121:: :: Network on-line operators:: 120:: :: Network PL1 subprograms:: 119:: :: Network Fortran subprograms:: 118:: :: Recommendations for facility documentation:: 117:: :: Some comments on the official protocol:: 116:: :: Structure of the May NWG meeting:: "(Updates RFC0099) (Updated by RFC0131, RFC0156) " 115:: :: Some Network Information Center policies on handling documents :: 113:: :: Network activity report: UCSB Rand:: (Updated by RFC0227) 112:: :: User/Server Site Protocol: Network host questionnaire responses:: 111:: :: Pressure from the chairman:: (Updates RFC0107) (Updated by RFC0130) 109:: :: Level III Server Protocol for the Lincoln Laboratory NIC 360/67 Host:: 108:: :: "Attendance list at the Urbana NWG meeting, February 17-19,1971 ":: (Updates RFC0101) 107:: :: Output of the Host-Host Protocol glitch cleaning committee:: "(Updated by RFC0132, RFC0179, RFC0111, RFC0124) " 106:: :: User/Server Site Protocol network host questionnaire:: 104:: :: Link 191:: 103:: :: Implementation of interrupt keys:: 102:: :: Output of the Host-Host Protocol glitch cleaning committee:: 101:: :: "Notes on the Network Working Group meeting, Urbana, Illinois, February 17, 1971":: (Updated by RFC0108) 100:: :: Categorization and guide to NWG/RFCs:: 99:: :: Network meeting:: (Updated by RFC0116) 95:: :: Distribution of NWG/RFC's through the NIC:: (Obsoleted by RFC0155) 90:: :: CCN as a network service center:: 89:: :: Some historic moments in networking:: 87:: :: Topic for discussion at the next Network Working Group meeting :: 85:: :: Network Working Group meeting:: 84:: :: List of NWG/RFC's 1-80:: 82:: :: Network meeting notes:: 81:: :: Request for reference information:: 78:: :: NCP status report: UCSB/Rand:: 77:: :: Network meeting report:: 76:: :: Connection by name: User oriented protocol:: 75:: :: Network meeting:: 74:: :: Specifications for network use of the UCSB On-Line System:: "(Updated by RFC0217, RFC0225) " 73:: :: Response to NWG/RFC 67:: 72:: :: Proposed moratorium on changes to network protocol:: 71:: :: Reallocation in case of input error:: 69:: :: Distribution list change for MIT:: (Updates RFC0052) 68:: :: "Comments on memory allocation control commands: CEASE, ALL, GVB, RET, and RFNM":: 66:: :: NIC - third level ideas and other noise:: (Obsoleted by RFC0123) 64:: :: Getting rid of marking:: 63:: :: Belated network meeting report:: 61:: :: Note on interprocess communication in a resource sharing computer network:: (Obsoleted by RFC0062) 57:: :: Thoughts and reflections on NWG/RFC 54:: (Updates RFC0054) 52:: :: Updated distribution list:: (Updated by RFC0069) 51:: :: Proposal for a Network Interchange Language:: 50:: :: Comments on the Meyer proposal:: 49:: :: Conversations with S. Crocker UCLA:: 48:: :: Possible protocol plateau:: 47:: :: BBN's comments on NWG/RFC #33:: (Updates RFC0033) 46:: :: ARPA Network protocol notes:: 45:: :: New protocol is coming:: 44:: :: Comments on NWG/RFC 33 and 36:: (Updates RFC0036) 43:: :: Proposed meeting [LIL]:: 40:: :: More comments on the forthcoming protocol:: 39:: :: Comments on protocol re: NWG/RFC #36:: (Updates RFC0036) 37:: :: "Network meeting epilogue, etc":: 36:: :: Protocol notes:: "(Updates RFC0033) (Updated by RFC0039, RFC0044) " 35:: :: Network meeting:: 34:: :: Some brief preliminary notes on the Augmentation Research Center clock:: 31:: :: Binary message forms in computer:: 30:: :: Documentation conventions:: (Obsoletes RFC0027) 27:: :: Documentation conventions:: (Obsoletes RFC0024) (Obsoleted by RFC0030) 25:: :: No high link numbers:: 24:: :: Documentation conventions:: (Obsoletes RFC0016) (Obsoleted by RFC0027) 21:: :: Network meeting:: 16:: :: M.I.T:: (Obsoletes RFC0010) (Obsoleted by RFC0024) 15:: :: Network subsystem for time sharing hosts:: 13:: :: [Referring to NWG/RFC 11]:: 11:: :: Implementation of the Host-Host software procedures in GORDO:: (Obsoleted by RFC0033) 10:: :: Documentation conventions:: (Obsoletes RFC0003) (Obsoleted by RFC0016) 9:: :: Host software:: 8:: :: Functional specifications for the ARPA Network:: 7:: :: Host-IMP interface:: 6:: :: Conversation with Bob Kahn:: 5:: :: Decode Encode Language:: 4:: :: Network timetable:: 3:: :: Documentation conventions:: (Obsoleted by RFC0010) 2:: :: Host software:: 1:: :: Host software:: ====================================================================== Appendix B: Automatic Script to Implement Methodology #!/usr/bin/perl5 # Program to read text files (such as RFCs and Internet Drafts) and output # items that might relate to year 2000 issues, particularly 2-digit # years. # # Version 1.0. By Paul Hoffman (paulh@imc.org). You may distribute and # use this program freely. I welcome comments and criticisms on the # program. # # Note: In the spirit of quick and dirty, this code is by no means optimized # for speed or memory usage. Instead, it is written to be as easy to read # (and therefore debug) as possible. # Some people like using disk files, others like STDIN and STDOUT. This # program accomodates both types. 'file' means input comes from the first # argument on the command line, output goes to that filename with a ".out" # extension; 'std' means STDIN and STDOUT. $UsageType = 'file'; # Should be 'file' or 'std' @CheckWords = qw(UTCTime two-digit 2-digit 2digit century 1900 2000); # You might want to add "year yyyy" to this list, but then a large proportion # of the RFCs and drafts get selected if($UsageType eq 'file') { if($ARGV[0] eq '') { die "You must specify the name of the file to open.\n" } $InName = $ARGV[0]; unless(-r $InName) { die "Could not read $InName.\n" } open(IN, $InName) or die "Could not open $InName.\n"; $OutName = "$InName.out"; open(OUT, ">$OutName") or die "Could not write to $OutName.\n"; $OutStuff = ''; # Holder for what we're going to print out } else { # Do STDIN and STDOUT open(IN, "-"); open(OUT, ">-"); } # Read the whole file into an array. This is a tad wasteful of memory # but makes the output easier. @All = (); while() { push(@All, $_) } $LastLine = $#All; # Process the instance of "yy" not followed by "yy" for($i = 0; $i <= $LastLine; $i += 1 ) { next unless(grep(/yy/i, $All[$i])); next if(grep(/yyyy/i, $All[$i])); &PrintFive($i, "'yy' on a line without 'yyyy'"); } # Next do the words that should cause extra concern foreach $Word (@CheckWords) { for($i = 0; $i <= $LastLine; $i += 1 ) { next unless(grep(/$Word/i, $All[$i])); &PrintFive($i, "$Word"); } } # All done. If writing to a file, and nothing got written, delete the # file so that you can quickly scan for the ".out" files. if($UsageType eq 'file') { if(length($OutStuff) > 0) { $OutStuff = "+=+=+=+=+= File $InName +=+=+=+=+= \n$OutStuff\n"; print OUT $OutStuff; close(OUT); } else { # Nothing to put in the .out close(OUT); unlink($OutName) or die "Couldn't unlink $OutName\n"; } } exit; sub PrintFive { my $Where = shift(@_); my $Msg = shift(@_); my ($WhereRealLine, $Start, $End, $j); $WhereRealLine = $Where + 1; $OutStuff .= "$Msg found at line $WhereRealLine:\n"; $Start = $Where - 2; $End = $Where + 2; if($Where < 2) { $Start = 0 } if($Where > $LastLine - 2) { $End = $LastLine } for($j = $Start; $j <= $End; $j += 1) { $OutStuff .= "$j: " . @All[$j] } $OutStuff .= "\n"; } Appendix C: Output of the script in Appendix B on all RFC's from 1 through 2134 +=+=+=+=+= File rfc90.txt +=+=+=+=+= 2000 found at line 71: 68: consoles); 69: 70: j) Six data communication ports (3 dial @ 2000 baud, 71: 1 dedicated @ 4800 baud, and 2 dedicated @ 50,000 72: baud) for remote batch entry terminals; +=+=+=+=+= File rfc230.txt +=+=+=+=+= 2000 found at line 92: 89: as for conventional synchronous block communication, since start and 90: stop bits for each character would need to be transmitted. This loss 91: is not substantial and does occur now for 2000 bps TIP-terminal 92: communication. 93: 2000 found at line 134: 131: 92 transmitting sites in the U.S. and Canada were used with standard 132: Bell System Dataphone datasets used at both ends. At both 1200 and 133: 2000 bps, approximately 82% of the calls had error rates of 1 error in 134: 10^5 bits or better, assuming an equal number of short, medium, and 135: long hauls. +=+=+=+=+= File rfc241.txt +=+=+=+=+= 2000 found at line 32: 29: justifiable on the basis that the IMP and Host computers were 30: expected to be either in the same room (up to 30 feet of cable) or, 31: via the Distant Host option, within 2000 feet on well- controlled, 32: shielded cables. A connection through common carrier facilities is 33: not comparably free of errors. Usage of common- carrier lines for +=+=+=+=+= File rfc263.txt +=+=+=+=+= 2000 found at line 22: 19: of the occasional desire to interface a Host to some IMP via a 20: long-distance connection (where long-distance, in this context, 21: is any cable run longer than 2000 feet but may typically be tens 22: of miles) via either a hard-wire or telephone circuit. We believe 23: that any good solution to the general problem of interfacing Hosts +=+=+=+=+= File rfc662.txt +=+=+=+=+= 2000 found at line 143: 140: by a rather short cable (approximately 100 feet long.) The CISL Multics is 141: connected to the IMP number 6 (port 0) by an approximately l5OO feet long cable. 142: 8oth IMPs are in close physical proximity (approximately 2000 feet,) and are 143: connected to each other by a 5O kilobits per second line. The results given 144: above show considerable improvement in the performance with the new IMP DIM. +=+=+=+=+= File rfc713.txt +=+=+=+=+= 2000 found at line 830: 827: succeeding bytes in the stream used to encode the object. 828: 829: A data object requiring 20000 (47040 octal) bytes would 830: appear in the stream as follows. 831: 2000 found at line 837: 834: 10000010 -- specifying that the next 2 bytes 835: contain the stream length 836: 01001110 -- first byte of number 20000 837: 00100000 -- second byte 838: . 2000 found at line 845: 842: . 843: 844: Interpretation of the contents of the 20000 bytes in 845: the stream can be performed by a module which knows the 846: specific format of the non-atomic type specified by DEFGH in +=+=+=+=+= File rfc724.txt +=+=+=+=+= 2-digit found at line 1046: 1043: <4-digit-year> 1044: ::= "/" 1045: "/" <2-digit-year> 1046: ::= 1047: ::= 2-digit found at line 1062: 1059: | "December" | "Dec" 1060: <4-digit-year> ::= 1061: <2-digit-year> ::= 1062: