draft-ietf-2000-issue-06.txt   rfc2626.txt 
Network Working Group Philip J. Nesser II Network Working Group P. Nesser II
draft-ietf-2000-issue-06.txt Nesser & Nesser Consulting Request for Comments: 2626 Nesser & Nesser Consulting
Internet Draft January 1999 Category: Informational June 1999
The Internet and the Millennium Problem (Year 2000) The Internet and the Millennium Problem (Year 2000)
Status of this Memo Status of this Memo
This document is an Internet Draft. Internet Drafts are working This memo provides information for the Internet community. It does
documents of the Internet Engineering Task Force (IETF), its Areas, not specify an Internet standard of any kind. Distribution of this
and its Working Groups. Note that other groups may also distribute memo is unlimited.
working documents as Internet Drafts.
Internet Drafts are draft documents valid for a maximum of six Copyright Notice
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 Copyright (C) The Internet Society (1999). All Rights Reserved.
Draft directory to learn the current status of this or any other
Internet Draft.
Abstract Abstract
The Year 2000 Working Group(WG) has conducted an investigation into The Year 2000 Working Group (WG) has conducted an investigation into
the millennium problem as it regards Internet related protocols. This the millennium problem as it regards Internet related protocols.
investigation only targeted the protocols as documented in the Request This investigation only targeted the protocols as documented in the
For Comments Series (RFCs). This investigation discovered little Request For Comments Series (RFCs). This investigation discovered
reason for concern with regards to the functionality of the protocols. little reason for concern with regards to the functionality of the
A few minor cases of older implementations still using two digit years protocols. A few minor cases of older implementations still using
(ala RFC 850) were discovered, but almost all Internet protocols were two digit years (ala RFC 850) were discovered, but almost all
given a clean bill of health. Several cases of 'period' problems were Internet protocols were given a clean bill of health. Several cases
discovered, where a time field would 'roll over' as the size of field of "period" problems were discovered, where a time field would "roll
was reached. In particular, there are several protocols, which have over" as the size of field was reached. In particular, there are
32 bit, signed integer representations of the number of seconds since several protocols, which have 32 bit, signed integer representations
January 1, 1970 which will turn negative at Tue Jan 19 03:14:07 GMT of the number of seconds since January 1, 1970 which will turn
2038. Areas whose protocols will be effected by such problems have negative at Tue Jan 19 03:14:07 GMT 2038. Areas whose protocols will
been notified so that new revisions will remove this limitation. be effected by such problems have been notified so that new revisions
will remove this limitation.
1. Introduction 1. Introduction
According to the trade press billions of dollars will be spend the According to the trade press billions of dollars will be spend the
upcoming years on the year 2000 problem, also called the millennium upcoming years on the year 2000 problem, also called the millennium
problem (though the third millennium will really start in 2001). This problem (though the third millennium will really start in 2001). This
problem consists of the fact that many software packages and some 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 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 the problems seem to be in administrative and financial programs, or
in the hardcoded microcomputers found in electronic equipment. A lot in the hardcoded microcomputers found in electronic equipment. A lot
of organizations are now starting to make an inventory of which of organizations are now starting to make an inventory of which
software and tools they use will suffer from the millennium problem. software and tools they use will suffer from the millennium problem.
With the increasing popularity of the Internet, more and more With the increasing popularity of the Internet, more and more
organizations use the Internet as a serious business tool. This means organizations use the Internet as a serious business tool. This
that most organizations will want to analyze the millennium problems means that most organizations will want to analyze the millennium
due to the use of Internet protocols and popular Internet software. In problems due to the use of Internet protocols and popular Internet
the trade press the first articles suggest that the Internet will software. In the trade press the first articles suggest that the
collapse at midnight the 31st of December 1999. Internet will collapse at midnight the 31st of December 1999.
To counter these suggestions, and to avoid having countless companies To counter these suggestions, and to avoid having countless companies
redo the same investigation, this effort was undertaken by the IETF. redo the same investigation, this effort was undertaken by the IETF.
The Year 2000 WG has made an inventory of all-important Internet The Year 2000 WG has made an inventory of all-important Internet
protocols that have been documented in the Request for Comments (RFC) protocols that have been documented in the Request for Comments (RFC)
series. Only protocols directly related to the Internet will be series. Only protocols directly related to the Internet will be
considered. considered.
This document is divided into a number of sections. Section 1 is This document is divided into a number of sections. Section 1 is the
the Introduction which you are now reading. Section 2 is a Introduction which you are now reading. Section 2 is a disclaimer
disclaimer about the completeness of this effort. Section 3 about the completeness of this effort. Section 3 describes areas in
describes areas in which millenium problems have been found, while which millenium problems have been found, while Section 4 describes a
Section 4 describes a few other "period" problems. Section 5 few other "period" problems. Section 5 describes potential fixes to
describes potential fixes to problems that have been identified. problems that have been identified. Section 6 describes the
Section 6 describes the methodology used in the investigation. methodology used in the investigation. Sections 7 through 22 are
Sections 7 through 22 are devoted to the 15 different groupings of devoted to the 15 different groupings of protocols and RFCs. Section
protocols and RFCs. Section 23 discusses security considerations, 23 discusses security considerations, Section 24 is devoted to
Section 24 is devoted to references, and Section 25 is the author references, and Section 25 is the author contact information.
contact information. Appendix A is the list of RFCs examined Appendix A is the list of RFCs examined broken down by category.
broken down by category. Appendix B is a PERL program used to make Appendix B is a PERL program used to make a first cut identification
a first cut identification of problems, and Appendix C is the output of problems, and Appendix C is the output of that PERL program.
of that PERL program.
The editor of this document would like to acknowledge the critical The editor of this document would like to acknowledge the critical
contributions of the follow for direct performance of research and the contributions of the follow for direct performance of research and
provision of text: Alex Latzko, Robert Elz, Erik Huizer, Gillian the provision of text: Alex Latzko, Robert Elz, Erik Huizer, Gillian
Greenwood, Barbara Jennings, R.E. (Robert) Moore, David Mills, Lynn Greenwood, Barbara Jennings, R.E. (Robert) Moore, David Mills, Lynn
Kubinec, Michael Patton, Chris Newman, Erik-Jan Bos, Paul Hoffman, and Kubinec, Michael Patton, Chris Newman, Erik-Jan Bos, Paul Hoffman,
Rick H. Wesson. The pace with which this group has operated has only and Rick H. Wesson. The pace with which this group has operated has
been achievable by the intimate familiarity of the contributors with only been achievable by the intimate familiarity of the contributors
the protocols and ready access to the collective knowledge of the with the protocols and ready access to the collective knowledge of
IETF. the IETF.
2. Disclaimer 2. Disclaimer
This RFC is not complete. It is an effort to analyze the Y2K impact This RFC is not complete. It is an effort to analyze the Y2K impact
on hundreds of protocols but is likely to have missed some protocols on hundreds of protocols but is likely to have missed some protocols
and misunderstood others. Organizations should not attempt to claim and misunderstood others. Organizations should not attempt to claim
any legitimacy or approval for any particular protocol based on this any legitimacy or approval for any particular protocol based on this
document. The efforts have concentrated on the identification of document. The efforts have concentrated on the identification of
potential problems, rather than solutions to any of the problems that potential problems, rather than solutions to any of the problems that
have been identified. Any proposed solutions are only that: proposed. have been identified. Any proposed solutions are only that: proposed.
A formal engineering review should take place before any solution is A formal engineering review should take place before any solution is
adopted. adopted.
It should also be noted that the research was performd on RFCs 1 It should also be noted that the research was performd on RFCs 1
through 2128. At that time the IESG was charted with not allowing through 2128. At that time the IESG was charted with not allowing
any new RFCs to be published that had any Year 2000 issues. Since any new RFCs to be published that had any Year 2000 issues. Since
that cutoff time there has been work to correct issues discovered by that cutoff time there has been work to correct issues discovered by
this Working Group. In particular, RWhois as documented by RFC 1714 this Working Group. In particular, RWhois as documented by RFC 1714
has been updated to fix the problems found. RFC 2167 now documents has been updated to fix the problems found. RFC 2167 now documents a
a fixed version of the RWhois protocol. The work of this group was fixed version of the RWhois protocol. The work of this group was to
to look backwards, and hence new RFC's which supplant the old are look backwards, and hence new RFC's which supplant the old are
expected to make the information in this RFC obsolete. The work of expected to make the information in this RFC obsolete. The work of
this group will truly be complete when this document is completely this group will truly be complete when this document is completely
obsolete. obsolete.
A number of people have suggested looking into other "special" dates. A number of people have suggested looking into other "special" dates.
For example, the first leap year, the first "double digit" day For example, the first leap year, the first "double digit" day
(January 10, 2000), January 1, 2001, etc. There is not one place (January 10, 2000), January 1, 2001, etc. There is not one place
where days have been used in the protocols defined by the RFC series where days have been used in the protocols defined by the RFC series
so there is little reason to believe that any of these special dates so there is little reason to believe that any of these special dates
will have any impact. will have any impact.
3. Summary of Year 2000 Problems 3. Summary of Year 2000 Problems
Here is a brief description of all the Millennium issues discovered Here is a brief description of all the Millennium issues discovered
in the course of this research. Note that many of the RFCs are in the course of this research. Note that many of the RFCs are
unclear on the issue. They mandate the use of UTCTime but do not unclear on the issue. They mandate the use of UTCTime but do not
specify whether the two-digit or four-digit year representation specify whether the two-digit or four-digit year representation
should be used. should be used.
3.1 "Directory Services" 3.1 "Directory Services"
rfc1274.txt - References UTC date/time rfc1274.txt - References UTC date/time
rfc1276.txt - References UTC date/time for version control. rfc1276.txt - References UTC date/time for version control.
rfc1488.txt - References UTC Time as printable strings. rfc1488.txt - References UTC Time as printable strings.
rfc1608.txt - Refers to uTCTimeSyntax rfc1608.txt - Refers to uTCTimeSyntax
rfc1609.txt - Refers to uTCTimeSyntax rfc1609.txt - Refers to uTCTimeSyntax
rfc1778.txt - Refers to uTCTimeSyntax rfc1778.txt - Refers to uTCTimeSyntax
3.2 "Information Services and File Transfer" 3.2 "Information Services and File Transfer"
HTTP 1.1, as defined in RFC 2068, requires all newly generated date HTTP 1.1, as defined in RFC 2068, requires all newly generated date
stamps to conform to RFC 1123 date formats which are Year 2000 stamps to conform to RFC 1123 date formats which are Year 2000
compliant, but it also requires acceptance of the older non-compliant compliant, but it also requires acceptance of the older non-compliant
RFC850 formats. Some specific recommendations have been passed to RFC850 formats. Some specific recommendations have been passed to
the HTTP WG. the HTTP WG.
HTML 2.0, as defined in RFC 1866, could allow a very subtle Year 2000 HTML 2.0, as defined in RFC 1866, could allow a very subtle Year 2000
problem, but once again this recommendation has been passed on the problem, but once again this recommendation has been passed on the
HTML WG. HTML WG.
RFC 1778 on String Representations of Standard Attribute Syntax's RFC 1778 on String Representations of Standard Attribute Syntax's
define UTC Time in Section 2.21 and uses that definition in Section define UTC Time in Section 2.21 and uses that definition in Section
2.25 on User Certificates. Since UTC Time is being used, there is a 2.25 on User Certificates. Since UTC Time is being used, there is a
potential millennium issue. potential millennium issue.
RFC 1440 on SIFT/UFT: Sender-Initiated/Unsolicited File Transfer RFC 1440 on SIFT/UFT: Sender-Initiated/Unsolicited File Transfer
defines an optional DATE command in Section 5 of the form mm/dd/yy defines an optional DATE command in Section 5 of the form mm/dd/yy
which is subject to millennium issues. which is subject to millennium issues.
3.3 "Electronic Mail" 3.3 "Electronic Mail"
After reviewing all mail-related RFCs, it was discovered that while After reviewing all mail-related RFCs, it was discovered that while
some obsolete standards required two-digit years, all currently used some obsolete standards required two-digit years, all currently used
standards require four-digit years and are thus not prone to typical standards require four-digit years and are thus not prone to typical
Year 2000 problems. Year 2000 problems.
RFCs 821 and 822, the main basis for SMTP mail exchange and message RFCs 821 and 822, the main basis for SMTP mail exchange and message
format, originally required two-digit years. However, both of these format, originally required two-digit years. However, both of these
RFCs were later modified by RFC 1123 in 1989, which strongly RFCs were later modified by RFC 1123 in 1989, which strongly
recommended 4-digit years. recommended 4-digit years.
3.4 "Name Serving" 3.4 "Name Serving"
While not a protocol issue, there is a common habit of writing serial While not a protocol issue, there is a common habit of writing serial
numbers for DNS zone files in the form YYXXXXXX. The only real numbers for DNS zone files in the form YYXXXXXX. The only real
requirement on the serial numbers is that they be increasing (see requirement on the serial numbers is that they be increasing (see RFC
RFC 1982 for a complete description) and a change from 99XXXXXX to 1982 for a complete description) and a change from 99XXXXXX to
00XXXXXX cause a failure. See the section on "Name Serving" for a 00XXXXXX cause a failure. See the section on "Name Serving" for a
complete description of the issues. complete description of the issues.
3.5 "Network Management" 3.5 "Network Management"
Version 2 of SNMP's MIB definition language (SMIv2) specifies the Version 2 of SNMP's MIB definition language (SMIv2) specifies the use
use of UCTTimes for time stamping MIB modules. Even though these of UCTTimes for time stamping MIB modules. Even though these time
time stamps do not flow in any network protocols, there could be stamps do not flow in any network protocols, there could be as issue
as issue with management applications, depending on implementations. with management applications, depending on implementations.
3.6 "Network News" 3.6 "Network News"
There does exist a problem in both NNTP, RFC 977, and the Usenet News There does exist a problem in both NNTP, RFC 977, and the Usenet News
Message Format, RFC 10336. They both specify two-digit year format. Message Format, RFC 10336. They both specify two-digit year format.
A working group has been formed to update the network news protocols A working group has been formed to update the network news protocols
in general, and addressing this problem is on their list of work in general, and addressing this problem is on their list of work
items. items.
3.7 "Real-Time Services" 3.7 "Real-Time Services"
A Year 2000 problem does occur in the Simple Network Paging Protocol, A Year 2000 problem does occur in the Simple Network Paging Protocol,
versions 2 & 3. Both define a HOLDuntil option which uses a versions 2 & 3. Both define a HOLDuntil option which uses a
YYMMDDHHMMSS+/-GMT field. Version 3 also defines a MSTAtus command, YYMMDDHHMMSS+/-GMT field. Version 3 also defines a MSTAtus command,
which is required to store,dates and times as YYMMDDHHMMSS+/-GMT. which is required to store,dates and times as YYMMDDHHMMSS+/-GMT.
There is a small Year 2000 issue in RFC 1786 on the Representation of There is a small Year 2000 issue in RFC 1786 on the Representation of
IP Routing Policies in the ripe-81++ Routing Registry. In Appendices IP Routing Policies in the ripe-81++ Routing Registry. In Appendices
C the "changed" object parameter defines a format of <email-address> C the "changed" object parameter defines a format of <email-address>
YYMMDD, and similarly in Appendix D "withdrawn" object identifier has YYMMDD, and similarly in Appendix D "withdrawn" object identifier has
he format of YYMMDD. Since these are only identifiers there should be he format of YYMMDD. Since these are only identifiers there should
little operational impact. Some application software may need to be be little operational impact. Some application software may need to
modified. be modified.
3.8 "Security" 3.8 "Security"
RFC 1507 on Distributed Authentication Security Services (DASS) RFC 1507 on Distributed Authentication Security Services (DASS) use
use UTCTime. Because of the imprecision of the UTC time UTCTime. Because of the imprecision of the UTC time definition there
definition there could be problems with this protocol. could be problems with this protocol.
RFCs 1421-1424 specifies that PEM uses UTC time formats which could RFCs 1421-1424 specifies that PEM uses UTC time formats which could
have a Millennium issue. have a Millennium issue.
4. Summary of Other "Periodicity" Problems 4. Summary of Other "Periodicity" Problems
By far, the largest area of "period" problems occurs in the year By far, the largest area of "period" problems occurs in the year
2038. Many protocols use a 32-bit field to record the number of 2038. Many protocols use a 32-bit field to record the number of
seconds since January 1, 1970. seconds since January 1, 1970.
4.1 "Name Serivces" 4.1 "Name Serivces"
DNS Security uses 32-bit timestamps which will roll over in 2038. DNS Security uses 32-bit timestamps which will roll over in 2038.
This issue has been refered to the appropriate Working Group so that This issue has been refered to the appropriate Working Group so that
the details of rollover can be established. the details of rollover can be established.
4.2 "Routing" 4.2 "Routing"
IDPR suffers from the classic Year 2038 problem, by having a timestamp IDPR suffers from the classic Year 2038 problem, by having a
counter which rolls over at that time. timestamp counter which rolls over at that time.
5. Suggested Solutions 5. Suggested Solutions
The real solution to the problem is to use 4 digit year fields for The real solution to the problem is to use 4 digit year fields for
applications and hardware systems. For counters that key off of a applications and hardware systems. For counters that key off of a
certain time (January 1, 1970 for example) need to either: define a certain time (January 1, 1970 for example) need to either: define a
wrapping solution, or to define a larger number space (greater than wrapping solution, or to define a larger number space (greater than
32-bits), or to make more efficient use of the 32-bit space. 32-bits), or to make more efficient use of the 32-bit space. However,
However, it will be impossible to completely replace currently it will be impossible to completely replace currently deployed
deployed systems, so solutions for handling problems are in order. systems, so solutions for handling problems are in order.
5.1 Fixed Solution 5.1 Fixed Solution
A number of organizations and groups have suggested a fixed solution A number of organizations and groups have suggested a fixed solution
to the problem of two digit years. Given a two-digit year YY, if YY to the problem of two digit years. Given a two-digit year YY, if YY
is greater than or equal to 50, the year shall be interpreted as 19YY; is greater than or equal to 50, the year shall be interpreted as
and where YY is less than 50, the year shall be intrepreted as 20YY. 19YY; and where YY is less than 50, the year shall be intrepreted as
20YY.
While a simple and straightforward solution, it only pushes the While a simple and straightforward solution, it only pushes the
problem off 40 to 50 years, until the artificially generated Year problem off 40 to 50 years, until the artificially generated Year
2050 problem needs to be addressed. However, it is easy to implement 2050 problem needs to be addressed. However, it is easy to implement
and deploy, so it might be the most commonly adopted solution. and deploy, so it might be the most commonly adopted solution.
5.2 Sliding Window 5.2 Sliding Window
Another solution is the "sliding window" approach. In this approach, Another solution is the "sliding window" approach. In this approach,
some value N is selected, and any two digit year that is less than or some value N is selected, and any two digit year that is less than or
equal to the current two digit year plus N is considered the future, equal to the current two digit year plus N is considered the future,
while any other two digit year is considered in the past. while any other two digit year is considered in the past.
For example, choosing N equal to 10, If the current year is 2012, and For example, choosing N equal to 10, If the current year is 2012,
I get a two digit year that is any of 12, 13, 14, 15, 16, 17, 18, 19, and I get a two digit year that is any of 12, 13, 14, 15, 16, 17, 18,
20, 21 or 22, assume it is 20YY (i.e. the future), otherwise consider 19, 20, 21 or 22, assume it is 20YY (i.e. the future), otherwise
it to be in the past(1923-1999, 2000-2011). consider it to be in the past(1923-1999, 2000-2011).
This solution has two advantages. First, no new fixed year problems This solution has two advantages. First, no new fixed year problems
are introduced. Second, different applications and protocols could are introduced. Second, different applications and protocols could
choose different values of N. The drawback is that this solution is choose different values of N. The drawback is that this solution is
harder to implement, and to work well the value of N will need to be harder to implement, and to work well the value of N will need to be
constant across different implementations. constant across different implementations.
6. Methodology 6. Methodology
The first task was dividing the types of RFC's into logical groups The first task was dividing the types of RFC's into logical groups
rather than the strict numeric publishing order. Sixteen specific rather than the strict numeric publishing order. Sixteen specific
areas were identified. They are: "Autoconfiguration" , "Directory areas were identified. They are: "Autoconfiguration" , "Directory
Services", "Disk Sharing", "Games and Chat" ,"Information Services & Services", "Disk Sharing", "Games and Chat" ,"Information Services &
File Transfer", "Network & Transport Layer", "Electronic Mail", "NTP", File Transfer", "Network & Transport Layer", "Electronic Mail",
Name Serving", "Network Management", "News", "Real Time Services", "NTP", Name Serving", "Network Management", "News", "Real Time
"Routing", "Security", "Virtual Terminal", and "Other". In addition Services", "Routing", "Security", "Virtual Terminal", and "Other".
to these categories, many hundreds of RFC's were immediately eliminated In addition to these categories, many hundreds of RFC's were
based on content. That is not to say that all Informational RFC's were immediately eliminated based on content. That is not to say that all
not considered, many did contain some technical content or overview Informational RFC's were not considered, many did contain some
whichdemanded scrutiny. technical content or overview whichdemanded scrutiny.
Each area was assigned to a team for investigation. Although each Each area was assigned to a team for investigation. Although each
team used whatever additional investigation techniques which seemed team used whatever additional investigation techniques which seemed
appropriate (including completely reading each RFC, and in some cases appropriate (including completely reading each RFC, and in some cases
the source code for the reference implementation) at minimum each team the source code for the reference implementation) at minimum each
used an automatic scanning system to search for the following items team used an automatic scanning system to search for the following
(case insensitively) in each RFC: items (case insensitively) in each RFC:
- date - date
- GMT - GMT
- UTCTime - UTCTime
- year - year
- yy (that is not part of yyyy) - yy (that is not part of yyyy)
- two-digit, 2-digit, 2digit - two-digit, 2-digit, 2digit
- century - century
- 1900 & 2000 - 1900 & 2000
Note that all of these strings except "UTCTime" may occur in Note that all of these strings except "UTCTime" may occur in
conjunction with a date format that accommodates the Year 2000 conjunction with a date format that accommodates the Year 2000
crossing, as well as with one that does not. So "hits" on these crossing, as well as with one that does not. So "hits" on these
string do not necessarily indicate Year 2000 problems: they simply string do not necessarily indicate Year 2000 problems: they simply
identify elements that need to be examined. identify elements that need to be examined.
After the documents were scanned, therefore, each "hit" was examined After the documents were scanned, therefore, each "hit" was examined
individually. Those that cause no Year 2000 problems (e.g., those 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 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 display string) are not discussed here. Those that do cause Year
problems are identified in this document, and the nature and impact of 2000 problems are identified in this document, and the nature and
the problems they cause are described. impact of the problems they cause are described.
7. Autoconfiguration 7. Autoconfiguration
7.1 Summary 7.1 Summary
The RFC's which were categorized into this group were primarily the The RFC's which were categorized into this group were primarily the
BOOT Protocol (BOOTP) and the Dynamic Host Configuration Protocol BOOT Protocol (BOOTP) and the Dynamic Host Configuration Protocol
(DHCP) for both IP version four and six. (DHCP) for both IP version four and six.
Examination of the BOOTP protocols and most popular implementations Examination of the BOOTP protocols and most popular implementations
show no year 2000 problems. All times are references as 32 bit show no year 2000 problems. All times are references as 32 bit
integers in seconds of UTC time. An investigation of all DHCP and the integers in seconds of UTC time. An investigation of all DHCP and
IPv6 Autoconfiguration mechanisms produced no year 2000 problems. All the IPv6 Autoconfiguration mechanisms produced no year 2000 problems.
references to time, in particular lease lengths, are 32 bit integers All references to time, in particular lease lengths, are 32 bit
in seconds, allowing lease times of well over 100 years. integers in seconds, allowing lease times of well over 100 years.
7.2 Specifics 7.2 Specifics
The following RFCs were examined for possible millennium problems: The following RFCs were examined for possible millennium problems:
906, 951, 1048, 1084, 1395, 1497, 1531, 1532, 1533, 1534, 1541, 1542, 906, 951, 1048, 1084, 1395, 1497, 1531, 1532, 1533, 1534, 1541, 1542,
1970, & 1971. RFC 951's only reference to time or dates is a two-byte 1970, & 1971. RFC 951's only reference to time or dates is a two-
field in the packet, which is number of second since the hosts, was byte field in the packet, which is number of second since the hosts,
booted. RFC's 1048, 1084, 1395, 1497, 1531, & 1532 have either no was booted. RFC's 1048, 1084, 1395, 1497, 1531, & 1532 have either
references to dates and time, or they are the same as the RFCs, which no references to dates and time, or they are the same as the RFCs,
obsoleted them, discussed in the next paragraph. which obsoleted them, discussed in the next paragraph.
RFC 1533 enumerates all the known DHCP field types and a number of RFC 1533 enumerates all the known DHCP field types and a number of
these have to do with time. Section 3.4 defines a "Time Offset" field these have to do with time. Section 3.4 defines a "Time Offset"
which specifies the offset of the clients subnet in seconds from UTC. field which specifies the offset of the clients subnet in seconds
This 4 byte field has no millennium issues. Section 9.2 defines the from UTC. This 4 byte field has no millennium issues. Section 9.2
IP Address Lease Time field which is used by clients to request a defines the IP Address Lease Time field which is used by clients to
specific lease time. This four byte field is an unsigned integer request a specific lease time. This four byte field is an unsigned
containing a number of seconds. Section 9.9 defines a Renewal Time integer containing a number of seconds. Section 9.9 defines a
Value field, Section 9.10 defines a Rebinding Time Value, both of Renewal Time Value field, Section 9.10 defines a Rebinding Time
which are similarly 32 bit fields, which have no millennium issues. Value, both of which are similarly 32 bit fields, which have no
millennium issues.
RFC 1534 has no references to times or dates. RFC 1534 has no references to times or dates.
RFC 1541 has two mentions of times/dates. The first is the "secs" RFC 1541 has two mentions of times/dates. The first is the "secs"
field which, similarly to RFC 951, is a 16-bit field for the number of field which, similarly to RFC 951, is a 16-bit field for the number
seconds since the host has booted. There is also a discussion in of seconds since the host has booted. There is also a discussion in
section 3.3 about "Interpretation and Representation of Time Values" section 3.3 about "Interpretation and Representation of Time Values"
which while clearly states that there is no millennium or period which while clearly states that there is no millennium or period
problems. problems.
RFC 1542 also references the "secs" field mentioned previously. RFC 1542 also references the "secs" field mentioned previously.
RFC 1970 mentions a number of variables, which are time related. In RFC 1970 mentions a number of variables, which are time related. In
section 4.2 "Router Advertisement Message Format" the following fields section 4.2 "Router Advertisement Message Format" the following
are defined: Router Lifetime, Reachable Time, & Retrans Timer. In fields are defined: Router Lifetime, Reachable Time, & Retrans Timer.
section 4.6.2 "Prefix Information" the following are defined: Valid In section 4.6.2 "Prefix Information" the following are defined:
Lifetime, & Preferred Lifetime. In section 6.2.1 "Router Valid Lifetime, & Preferred Lifetime. In section 6.2.1 "Router
Configuration Variables the following are defined: MaxRtrAdvInterval, Configuration Variables the following are defined: MaxRtrAdvInterval,
MinRtrAdvInterval, AdvReachableTime, AdvRetransTimer, MinRtrAdvInterval, AdvReachableTime, AdvRetransTimer,
AdvDefaultLifetime, AdvValidLifetime, & AdvPreferredLifetime. All of AdvDefaultLifetime, AdvValidLifetime, & AdvPreferredLifetime. All of
these fields specify counters of some sort which have no millennium or these fields specify counters of some sort which have no millennium
periodicity problems. or periodicity problems.
RFC 1971 has some discussion of preferred lifetimes, depreciated RFC 1971 has some discussion of preferred lifetimes, depreciated
lifetimes and valid lifetimes of leases, but only discusses them in an lifetimes and valid lifetimes of leases, but only discusses them in
expository way. an expository way.
8. Directory Services 8. Directory Services
8.1 Summary 8.1 Summary
The RFC's which were categorized into this group were primarily X.500 The RFC's which were categorized into this group were primarily X.500
related RFC's, Whois, Rwhois, Whois++, and the Lightweight Directory related RFC's, Whois, Rwhois, Whois++, and the Lightweight Directory
Access Protocol (LDAP). Access Protocol (LDAP).
Upon review of the Directory Services related RFC's, no serious year Upon review of the Directory Services related RFC's, no serious year
2000 problems were discovered. Some minor issues were noted and 2000 problems were discovered. Some minor issues were noted and
explained below in the specific portion of this section. explained below in the specific portion of this section.
8.2 Specifics 8.2 Specifics
RFCs that mentioned UTC Time or made reference to uTCTimeSyntax could RFCs that mentioned UTC Time or made reference to uTCTimeSyntax could
fail to be Y2K compliant. These should be updated to specify the four fail to be Y2K compliant. These should be updated to specify the four
year version of uTCTimeSyntax rather than giving the option of using a year version of uTCTimeSyntax rather than giving the option of using
two-year date representation. The following RFCs fall into this a two-year date representation. The following RFCs fall into this
category: category:
rfc1274.txt - References UTC date/time rfc1274.txt - References UTC date/time
rfc1276.txt - References UTC date/time for version control. rfc1276.txt - References UTC date/time for version control.
rfc1488.txt - References UTC Time as printable strings. rfc1488.txt - References UTC Time as printable strings.
rfc1608.txt - Refers to uTCTimeSyntax rfc1608.txt - Refers to uTCTimeSyntax
rfc1609.txt - Refers to uTCTimeSyntax rfc1609.txt - Refers to uTCTimeSyntax
rfc1778.txt - Refers to uTCTimeSyntax rfc1778.txt - Refers to uTCTimeSyntax
Two RFC's have unusual date specifications and specify their own date Two RFC's have unusual date specifications and specify their own date
format. Both of these support Y2K compliant dates. format. Both of these support Y2K compliant dates.
RFC1714 (RWhois) specifies date formats that are not Y2K compliant, RFC1714 (RWhois) specifies date formats that are not Y2K compliant,
but it also supports dates that are. Implementers of the RWhois but it also supports dates that are. Implementers of the RWhois
protocol should only use the %MY4 format protocol should only use the %MY4 format
RFC1834 (Whois++) requires the use of dates, but it didn't specify the RFC1834 (Whois++) requires the use of dates, but it didn't specify
format, syntax, or representation of the date string to be used. the format, syntax, or representation of the date string to be used.
9. Disk Sharing 9. Disk Sharing
9.1 Summary 9.1 Summary
The RFC's which were categorized into this group were those related to The RFC's which were categorized into this group were those related
the Network File System (NFS). Other popular disk sharing protocols to the Network File System (NFS). Other popular disk sharing
like SMB and AFS were referred to their respective trustee's for protocols like SMB and AFS were referred to their respective
review. trustee's for review.
After careful review, NFS has no year 2000 problems. After careful review, NFS has no year 2000 problems.
9.2 Specifics 9.2 Specifics
The references to time in this protocol are the times of file data The references to time in this protocol are the times of file data
modification, file access, and file metadata change (mtime, atime, and modification, file access, and file metadata change (mtime, atime,
time, respectively). These times are kept as 32 bit unsigned and time, respectively). These times are kept as 32 bit unsigned
quantities in seconds since 1970-01-01, and so the NFS protocol will quantities in seconds since 1970-01-01, and so the NFS protocol will
not experience an Epoch event until the year 2106. not experience an Epoch event until the year 2106.
10. Games and Chat 10. Games and Chat
10.1 Summary 10.1 Summary
The RFC's which were categorized into this group were related to the The RFC's which were categorized into this group were related to the
Internet Relay Chat Protocol (IRC). No millennium problems exist in Internet Relay Chat Protocol (IRC). No millennium problems exist in
the IRC protocol. the IRC protocol.
10.2 Specifics 10.2 Specifics
There is only a single instance of time or date related information in There is only a single instance of time or date related information
the IRC protocol as specified by RFC 1459. Section 4.3.4 defines a in the IRC protocol as specified by RFC 1459. Section 4.3.4 defines
TIME message type which queries a server for its local time. No a TIME message type which queries a server for its local time. No
mention is made of the format of the reply or how it is parsed, the mention is made of the format of the reply or how it is parsed, the
assumption being specific implementations will handle the reply and assumption being specific implementations will handle the reply and
parse it appropriately. parse it appropriately.
11. Information Services & File Transfer 11. Information Services & File Transfer
11.1 Summary 11.1 Summary
The RFC's which were categorized into this group were divided among The RFC's which were categorized into this group were divided among
World Wide Web (WWW) protocols and File Transfer Protocols (FTP). WWW World Wide Web (WWW) protocols and File Transfer Protocols (FTP).
protocols include the Hypertext Transfer Protocol (HTTP), a variety of WWW protocols include the Hypertext Transfer Protocol (HTTP), a
Uniform Resource formats (URL, URAs, etc.) and the HyperText Markup variety of Uniform Resource formats (URL, URAs, etc.) and the
Language(HTML). FTP protocols include the well known FTP protocol, HyperText Markup Language(HTML). FTP protocols include the well
the Trivial File Transfer Protocol (TFTP) and a variety of extensions known FTP protocol, the Trivial File Transfer Protocol (TFTP) and a
to these protocols. Other information services includes the Finger variety of extensions to these protocols. Other information services
Protocol and the LPD protocol. includes the Finger Protocol and the LPD protocol.
HTTP 1.1, as defined in RFC 2068, requires all newly generated date HTTP 1.1, as defined in RFC 2068, requires all newly generated date
stamps to conform to RFC 1123 date formats which are Year 2000 stamps to conform to RFC 1123 date formats which are Year 2000
compliant, but it also requires acceptance of the older non-compliant compliant, but it also requires acceptance of the older non-compliant
RFC850 formats. Some specific recommendations are listed below and RFC850 formats. Some specific recommendations are listed below and
have been passed to the HTTP WG. have been passed to the HTTP WG.
HTML 2.0, as defined in RFC 1866, could allow a very subtle Year 2000 HTML 2.0, as defined in RFC 1866, could allow a very subtle Year 2000
problem, but once again this recommendation has been passed on the problem, but once again this recommendation has been passed on the
HTML WG. HTML WG.
RFC 1778 on String Representations of Standard Attribute Syntax's RFC 1778 on String Representations of Standard Attribute Syntax's
define UTC Time in Section 2.21 and uses that definition in Section define UTC Time in Section 2.21 and uses that definition in Section
2.25 on User Certificates. Since UTC Time is being used, there is a 2.25 on User Certificates. Since UTC Time is being used, there is a
potential millennium issue. potential millennium issue.
RFC 1440 on SIFT/UFT: Sender-Initiated/Unsolicited File Transfer RFC 1440 on SIFT/UFT: Sender-Initiated/Unsolicited File Transfer
defines an optional DATE command in Section 5 of the form mm/dd/yy defines an optional DATE command in Section 5 of the form mm/dd/yy
which is subject to millennium issues. which is subject to millennium issues.
11.2 Specifics 11.2 Specifics
The main IETF standards-track document on the HTTP protocol is RFC2068 The main IETF standards-track document on the HTTP protocol is
on HTTP 1.1. It notes that historically three different date formats RFC2068 on HTTP 1.1. It notes that historically three different date
have been used, and that one of them uses a two-digit year field. In formats have been used, and that one of them uses a two-digit year
section 3.3.1 it requires HTTP 1.1 implementations to generate this field. In section 3.3.1 it requires HTTP 1.1 implementations to
RFC1123 format: generate this RFC1123 format:
Sun, 06 Nov 1994 08:49:37 GMT ; RFC 822, updated by RFC 1123 Sun, 06 Nov 1994 08:49:37 GMT ; RFC 822, updated by RFC 1123
instead of this RFC850 format: instead of this RFC850 format:
Sunday, 06-Nov-94 08:49:37 GMT ; RFC 850, obsoleted by RFC 1036 Sunday, 06-Nov-94 08:49:37 GMT ; RFC 850, obsoleted by RFC 1036
Unfortunately, many existing servers, serving on the order of one Unfortunately, many existing servers, serving on the order of one
fifth of the current HTTP traffic, send dates in the ambiguous RFC850 fifth of the current HTTP traffic, send dates in the ambiguous RFC850
format. format.
Section 19.3 of the RFC2068 says this: Section 19.3 of the RFC2068 says this:
o HTTP/1.1 clients and caches should assume that an RFC-850 date 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 which appears to be more than 50 years in the future is in fact
in the past (this helps solve the "year 2000" problem). in the past (this helps solve the "year 2000" problem).
This avoids a "stale cache" problem, which would cause the user to see This avoids a "stale cache" problem, which would cause the user to
out-of-date data. see out-of-date data.
RFC 1986 documents experiments with a simple file transfer program RFC 1986 documents experiments with a simple file transfer program
over radio links using Enhanced Trivial FTP (ETFTP). There are a over radio links using Enhanced Trivial FTP (ETFTP). There are a
number of timers defined which are all in seconds and have no year number of timers defined which are all in seconds and have no year
2000 issues. 2000 issues.
In RFC 1866, on HTML 2.0,the <META> tag allows the embedding of In RFC 1866, on HTML 2.0,the <META> tag allows the embedding of
recommended values for some HTTP headers, including Expires. E.g. recommended values for some HTTP headers, including Expires. E.g.
<META HTTP-EQUIV="Expires" <META HTTP-EQUIV="Expires"
CONTENT="Tue, 04 Dec 1993 21:29:02 GMT"> CONTENT="Tue, 04 Dec 1993 21:29:02 GMT">
Servers should rewrite these dates into RFC1123 format if necessary. Servers should rewrite these dates into RFC1123 format if necessary.
RFC 1807 defines a format for bibliographic records and it specifies a RFC 1807 defines a format for bibliographic records and it specifies
DATE format, which requires 4 digit year fields. a DATE format, which requires 4 digit year fields.
RFC 1788 defines ICMP Domain Name messages. Section 3 defines a RFC 1788 defines ICMP Domain Name messages. Section 3 defines a
Domain Name Reply Packet, which contains a signed 32-bit integer. Domain Name Reply Packet, which contains a signed 32-bit integer.
This timer is not Year 2000 reliant and is certainly large enough for This timer is not Year 2000 reliant and is certainly large enough for
it purposes. it purposes.
RFC 1784 on TFTP Timeout Intervals and Transfer Size Options uses a RFC 1784 on TFTP Timeout Intervals and Transfer Size Options uses a
field for the number of seconds for the timeout. It is an ASCII value field for the number of seconds for the timeout. It is an ASCII
from 1 to 255 octets in length. There is no Y2K issue. value from 1 to 255 octets in length. There is no Y2K issue.
RFC 1778 on String Representations of Standard Attribute Syntax's RFC 1778 on String Representations of Standard Attribute Syntax's
define UTC Time in Section 2.21 and uses that definition in Section define UTC Time in Section 2.21 and uses that definition in Section
2.25 on User Certificates. Since UTC Time is being used, there is a 2.25 on User Certificates. Since UTC Time is being used, there is a
potential millennium issue. potential millennium issue.
RFC 1777 on LDAP defines a timelimit in Section 4.3 which is expressed RFC 1777 on LDAP defines a timelimit in Section 4.3 which is
in seconds, but does not define any limits. expressed in seconds, but does not define any limits.
RFC 1440 on SIFT/UFT: Sender-Initiated/Unsolicited File Transfer RFC 1440 on SIFT/UFT: Sender-Initiated/Unsolicited File Transfer
defines an optional DATE command in Section 5 of the form mm/dd/yy, defines an optional DATE command in Section 5 of the form mm/dd/yy,
which is subject to millennium issues. which is subject to millennium issues.
RFC 1068 on the Background File Transfer Protocol (BFTP) defines two RFC 1068 on the Background File Transfer Protocol (BFTP) defines two
commands in Sections B.2.12 and B.2.13, the Submit and Time commands. commands in Sections B.2.12 and B.2.13, the Submit and Time commands.
>From the example usage's given in Appendix C it is clear that this >From the example usage's given in Appendix C it is clear that this
protocol will function correctly though the year 9999. protocol will function correctly though the year 9999.
RFC 1037 on NFILE (a file access protocol) discusses the a Date RFC 1037 on NFILE (a file access protocol) discusses the a Date
representation in Section 7.1 as the number of seconds since January representation in Section 7.1 as the number of seconds since January
1, 1900, but does not limit the field size. There should be no Y2K 1, 1900, but does not limit the field size. There should be no Y2K
issues. issues.
RFC 998 on NETBLT defines a Death time in Section 8, which is the RFC 998 on NETBLT defines a Death time in Section 8, which is the
sender's death time in seconds. sender's death time in seconds.
RFC 978 on the Voice File Interchange Protocol defines the Total Time RFC 978 on the Voice File Interchange Protocol defines the Total Time
of a message to be a 32-bit number of deci-seconds. This limits the of a message to be a 32-bit number of deci-seconds. This limits the
size of a message but has no millennium issues. size of a message but has no millennium issues.
RFC 969 was obsoleted by RFC 998. RFC 969 was obsoleted by RFC 998.
RFC 916 defines the Reliable Asynchronous Transfer Protocol (RATP). RFC 916 defines the Reliable Asynchronous Transfer Protocol (RATP).
Three timers are discussed in an expository manner in Section 5.4 and Three timers are discussed in an expository manner in Section 5.4 and
its subsections. There are no relevant issues. its subsections. There are no relevant issues.
RFCs 2122, 2056, 2055, 2054, 2044, 2016, 1960, 1959, 1874, 1865, 1862, RFCs 2122, 2056, 2055, 2054, 2044, 2016, 1960, 1959, 1874, 1865, 1862,
1843, 1842, 1823, 1815, 1808, 1798, 1785, 1783, 1782, 1779, 1766, 1843, 1842, 1823, 1815, 1808, 1798, 1785, 1783, 1782, 1779, 1766,
1738, 1737, 1736, 1729, 1728, 1727, 1639, 1633, 1630, 1625, 1554, 1738, 1737, 1736, 1729, 1728, 1727, 1639, 1633, 1630, 1625, 1554,
1545, 1530, 1529, 1528, 1489, 1486, 1436, 1415, 1413, 1350, 1345, 1545, 1530, 1529, 1528, 1489, 1486, 1436, 1415, 1413, 1350, 1345,
1312, 1302, 1288, 1278, 1241, 1235, 1196, 1194, 1179, 1123, 1003, 971, 1312, 1302, 1288, 1278, 1241, 1235, 1196, 1194, 1179, 1123, 1003, 971,
965, 959, 949, 913, 887, 866, 865, 864, 863, 862, 797, 795, 783, 775, 965, 959, 949, 913, 887, 866, 865, 864, 863, 862, 797, 795, 783, 775,
765, 751, 743, 742, 740, 737, 725, 722, 707, 691, 683, 662, 640, 624, 765, 751, 743, 742, 740, 737, 725, 722, 707, 691, 683, 662, 640, 624,
614, 607, 599, 412, 411, 410, 407, and 406 were found to have no 614, 607, 599, 412, 411, 410, 407, and 406 were found to have no
references to dates or times, and hence no millennium issues. references to dates or times, and hence no millennium issues.
RFCs 712, 697, 633, 630, 622, 610, 593, 592, 589, 573, 571, 570, 553, RFCs 712, 697, 633, 630, 622, 610, 593, 592, 589, 573, 571, 570, 553,
551, 549, 543, 535, 532, 525, 520, 514, 506, 505, 504, 501, 499, 493, 551, 549, 543, 535, 532, 525, 520, 514, 506, 505, 504, 501, 499, 493,
490, 487, 486, 485, 480, 479, 478, 477, 472, 468, 467, 463, 454, 451, 490, 487, 486, 485, 480, 479, 478, 477, 472, 468, 467, 463, 454, 451,
448, 446, 438, 437, 436, 430, 429, 418, 414, and 409 were not 448, 446, 438, 437, 436, 430, 429, 418, 414, and 409 were not
available for review. available for review.
RFCS below 400 were considered too obsolete to even consider. RFCS below 400 were considered too obsolete to even consider.
12. Network & Transport Layer 12. Network & Transport Layer
12.1 Summary 12.1 Summary
The RFC's which were categorized into this group were the Internet The RFC's which were categorized into this group were the Internet
Protocol (IP) versions four and six, the Transmission Control Protocol Protocol (IP) versions four and six, the Transmission Control
(TCP), the User Datagram Protocol (UDP), the Point-to-Point Protocol Protocol (TCP), the User Datagram Protocol (UDP), the Point-to-Point
(PPP) and its extensions, Internet Control Message Protocol (ICMP), Protocol (PPP) and its extensions, Internet Control Message Protocol
the Address Resolution Protocol (ARP) and Remote Procedure Call (RPC) (ICMP), the Address Resolution Protocol (ARP) and Remote Procedure
protocol. A variety of less known protocols were also examined. Call (RPC) protocol. A variety of less known protocols were also
examined.
After careful review of the nearly 400 RFC's in this catagory, no After careful review of the nearly 400 RFC's in this catagory, no
millennium or year 2000 problems were found. millennium or year 2000 problems were found.
12.2 Specifics 12.2 Specifics
RFC 2125 on the PPP Bandwidth Allocation Protocol (BAP) in section 5.3 RFC 2125 on the PPP Bandwidth Allocation Protocol (BAP) in section
discusses the use if mandatory timers, but gives no mention as to how 5.3 discusses the use if mandatory timers, but gives no mention as to
they are implemented. how they are implemented.
RFC 2114 on a Data Link Switching Client Access Protocol defines a RFC 2114 on a Data Link Switching Client Access Protocol defines a
retry timer of five seconds in Section 3.4.1. retry timer of five seconds in Section 3.4.1.
RFC 2097 on the PPP NetBIOS Frame Control Protocol discuesses several RFC 2097 on the PPP NetBIOS Frame Control Protocol discuesses several
timer and timeouts in Section 2.1, none of which suffers from a year timer and timeouts in Section 2.1, none of which suffers from a year
2000 problem. 2000 problem.
RFC 2075 on the IP Echo Host Service discusses timestamps and has no RFC 2075 on the IP Echo Host Service discusses timestamps and has no
millennium issues. millennium issues.
RFC 2005 on the Applicability for Mobile IP discusses using timestamps RFC 2005 on the Applicability for Mobile IP discusses using
as a security measure to avoid replay attacks (Section 3.), but does timestamps as a security measure to avoid replay attacks (Section
not quantify them. There are no expected issues. 3.), but does not quantify them. There are no expected issues.
RFC 2002 on IP Mobility Support uses a 16-bit field for the lifetime RFC 2002 on IP Mobility Support uses a 16-bit field for the lifetime
of a connection and notes the 18.2 hour limitation that this imposes. of a connection and notes the 18.2 hour limitation that this imposes.
Section 5.6.1 on replay protection requires the use of 64-bit time Section 5.6.1 on replay protection requires the use of 64-bit time
fields, of a similar format to NTP packets. fields, of a similar format to NTP packets.
RFC 1981 on Path MTU Discovery for IPv6 discusses timestamps and their RFC 1981 on Path MTU Discovery for IPv6 discusses timestamps and
potential use to purge stale information in section 5.3. There is no their potential use to purge stale information in section 5.3. There
millennium issues in this use. is no millennium issues in this use.
RFC 1963 on the PPP Serial Data Transport Protocol defines a flow RFC 1963 on the PPP Serial Data Transport Protocol defines a flow
expiration time in section 4.9 which has no year 2000 issues. expiration time in section 4.9 which has no year 2000 issues.
RFC 1833 on Binding Protocols for ONC RPC Version 2 defines a variable RFC 1833 on Binding Protocols for ONC RPC Version 2 defines a
in Section 2.2.1 called RPCBPROC_GETTIME which returns the local time variable in Section 2.2.1 called RPCBPROC_GETTIME which returns the
in seconds since 1/1/1970. Since this value is not fields width local time in seconds since 1/1/1970. Since this value is not fields
dependent, it may or may not wrap around the 32-bit value depending on width dependent, it may or may not wrap around the 32-bit value
the operating system parameters. depending on the operating system parameters.
RFC 1762 on the PPP DECnet Phase IV Control Protocol discusses a number RFC 1762 on the PPP DECnet Phase IV Control Protocol discusses a
of timers in Section 5 (General Considerations). None of these timers number of timers in Section 5 (General Considerations). None of
experience any millennium issues. these timers experience any millennium issues.
RFC 1761 on Snoop Version 2 Packet Capture File Format discusses two RFC 1761 on Snoop Version 2 Packet Capture File Format discusses two
32-bit timestamp values on Section 4 on Packet Record Formats. The 32-bit timestamp values on Section 4 on Packet Record Formats. The
first of these may wrap in the year 2038, but should not effect anything first of these may wrap in the year 2038, but should not effect
of any import. anything of any import.
RFC 1755 on ATM Signalling Support for IP Over ATM discusses timing RFC 1755 on ATM Signalling Support for IP Over ATM discusses timing
issues in Section 3.4 on VC Teardown. These limited timers have no issues in Section 3.4 on VC Teardown. These limited timers have no
year 2000 issues. year 2000 issues.
RFC 1692 on the Transport Multiplexing Protocol (TMux) defines a TTL in RFC 1692 on the Transport Multiplexing Protocol (TMux) defines a TTL
Section 2.3 and a timer in Section 3.3. Neither of these suffer from in Section 2.3 and a timer in Section 3.3. Neither of these suffer
any millennium or year 2000 issues. from any millennium or year 2000 issues.
RFC 1661 on PPP defines three timers in Section 4.6, none of which have RFC 1661 on PPP defines three timers in Section 4.6, none of which
any year 2000 issues. have any year 2000 issues.
RFC 1644 on T/TCP (TCP Extensions for Transactions) mentions RFC 1323 RFC 1644 on T/TCP (TCP Extensions for Transactions) mentions RFC 1323
and the extended timers recommended in it. and the extended timers recommended in it.
RFC 1575 defines an echo function for CNLP discusses in the narrative RFC 1575 defines an echo function for CNLP discusses in the narrative
the use of the Lifetime Field in Section 5.3. There is nothing to the use of the Lifetime Field in Section 5.3. There is nothing to
suggest that there is any year 2000 issues. suggest that there is any year 2000 issues.
RFC 1329 on Dual MAC FDDI Networks discusses ARP cache administration RFC 1329 on Dual MAC FDDI Networks discusses ARP cache administration
in Section 9.3 and 9.4 and various timers to expire entries. in Section 9.3 and 9.4 and various timers to expire entries.
RFC 1256 on ICMP Router Discovery Messages talks about lifetime fields RFC 1256 on ICMP Router Discovery Messages talks about lifetime
in Section 2 and defines three router configuration variables in Section fields in Section 2 and defines three router configuration variables
4.1. None of these have any millennium issues. in Section 4.1. None of these have any millennium issues.
RFC 792 on ICMP discusses Timestamps and Timestamp Reply messages which RFC 792 on ICMP discusses Timestamps and Timestamp Reply messages
define a 32-bit timestamp which contains the number of milliseconds which define a 32-bit timestamp which contains the number of
since midnight UT. milliseconds since midnight UT.
RFC 791 on the Internet Protocol defines a packet type 68 which is an RFC 791 on the Internet Protocol defines a packet type 68 which is an
Internet Timestamp, which defines a 32-bit field which contains the Internet Timestamp, which defines a 32-bit field which contains the
number of milliseconds since midnght UT. number of milliseconds since midnght UT.
RFC 781 was defines the same option which is codified in RFC 791 as RFC 781 was defines the same option which is codified in RFC 791 as a
a packet type 68. packet type 68.
RFC's 2126, 2118, 2113, 2107, 2106, 2105, 2098, 2067, 2043, 2023, RFC's 2126, 2118, 2113, 2107, 2106, 2105, 2098, 2067, 2043, 2023,
2019, 2018, 2009, 2004, 2003, 2001, 1994, 1993, 1990, 1989, 1979, 2019, 2018, 2009, 2004, 2003, 2001, 1994, 1993, 1990, 1989, 1979,
1978, 1977, 1976, 1975, 1974, 1973, 1972, 1967, 1962, 1954, 1946, 1978, 1977, 1976, 1975, 1974, 1973, 1972, 1967, 1962, 1954, 1946,
1937, 1936, 1934, 1933, 1932, 1931, 1926, 1924, 1919, 1918, 1917, 1937, 1936, 1934, 1933, 1932, 1931, 1926, 1924, 1919, 1918, 1917,
1916, 1915, 1897, 1888, 1887, 1885, 1884, 1883, 1881, 1878, 1877, 1916, 1915, 1897, 1888, 1887, 1885, 1884, 1883, 1881, 1878, 1877,
1868, 1860, 1859, 1853, 1841, 1832, 1831, 1809, 1795, 1791, 1770, 1868, 1860, 1859, 1853, 1841, 1832, 1831, 1809, 1795, 1791, 1770,
1764, 1763, 1756, 1754, 1752, 1744, 1735, 1726, 1719, 1717, 1710, 1764, 1763, 1756, 1754, 1752, 1744, 1735, 1726, 1719, 1717, 1710,
1707, 1705, 1698, 1693, 1688, 1687, 1686, 1683, 1682, 1681, 1680, 1707, 1705, 1698, 1693, 1688, 1687, 1686, 1683, 1682, 1681, 1680,
1679, 1678, 1677, 1676, 1674, 1673, 1672, 1671, 1670, 1669, 1667, 1679, 1678, 1677, 1676, 1674, 1673, 1672, 1671, 1670, 1669, 1667,
1663, 1662, 1638, 1634, 1631, 1629, 1624, 1622, 1621, 1620, 1619, 1663, 1662, 1638, 1634, 1631, 1629, 1624, 1622, 1621, 1620, 1619,
1618, 1613, 1605, 1604, 1598, 1590, 1577, 1570, 1561, 1560, 1553, 1618, 1613, 1605, 1604, 1598, 1590, 1577, 1570, 1561, 1560, 1553,
1552, 1551, 1549, 1548, 1547, 1538, 1526, 1518, 1498, 1490, 1483, 1552, 1551, 1549, 1548, 1547, 1538, 1526, 1518, 1498, 1490, 1483,
1475, 1466, 1454, 1435, 1434, 1433, 1393, 1390, 1385, 1379, 1378, 1475, 1466, 1454, 1435, 1434, 1433, 1393, 1390, 1385, 1379, 1378,
1377, 1376, 1375, 1374, 1365, 1363, 1362, 1356, 1347, 1337, 1335, 1377, 1376, 1375, 1374, 1365, 1363, 1362, 1356, 1347, 1337, 1335,
1334, 1333, 1332, 1331, 1326, 1323, 1314, 1307, 1306, 1294, 1293, 1334, 1333, 1332, 1331, 1326, 1323, 1314, 1307, 1306, 1294, 1293,
1277, 1263, 1240, 1237, 1236, 1234, 1226, 1223, 1220, 1219, 1210, 1277, 1263, 1240, 1237, 1236, 1234, 1226, 1223, 1220, 1219, 1210,
1209, 1201, 1191, 1188, 1185, 1172, 1171, 1166, 1162, 1151, 1146, 1209, 1201, 1191, 1188, 1185, 1172, 1171, 1166, 1162, 1151, 1146,
1145, 1144, 1141, 1139, 1134, 1132, 1122, 1110, 1106, 1103, 1088, 1145, 1144, 1141, 1139, 1134, 1132, 1122, 1110, 1106, 1103, 1088,
1086, 1085, 1078, 1072, 1071, 1070, 1069, 1063, 1062, 1057, 1055, 1086, 1085, 1078, 1072, 1071, 1070, 1069, 1063, 1062, 1057, 1055,
1051, 1050, 1046, 1045, 1044, 1042, 1030, 1029, 1027, 1025, 1016, 1051, 1050, 1046, 1045, 1044, 1042, 1030, 1029, 1027, 1025, 1016,
1008, 1007, 1006, 1002, 1001, 994, 986, 983, 982, 970, 964, 963, 962, 1008, 1007, 1006, 1002, 1001, 994, 986, 983, 982, 970, 964, 963, 962,
955, 948, 942, 941, 940, 936, 935, 932, 926, 925, 924, 922, 919, 917, 955, 948, 942, 941, 940, 936, 935, 932, 926, 925, 924, 922, 919, 917,
914, 905, 903, 896, 895, 894, 893, 892, 891, 889, 879, 877, 874, 872, 914, 905, 903, 896, 895, 894, 893, 892, 891, 889, 879, 877, 874, 872,
871, 848, 829, 826, 824, 815, 814, 813, 801, 793, 789, 787, 777, 768, 871, 848, 829, 826, 824, 815, 814, 813, 801, 793, 789, 787, 777, 768,
761, 760, 759, 730, 704, 696, 695, 692, 690, 689, 687, 685, 680, 675, 761, 760, 759, 730, 704, 696, 695, 692, 690, 689, 687, 685, 680, 675,
674, 660, 632, 626, 613, 611 were reviewed but were found to have no 674, 660, 632, 626, 613, 611 were reviewed but were found to have no
millennium references. millennium references.
RFC's 594, 591, 576, 550, 548, 528, 521, 489, 488, 473, 460, 459, 450, RFC's 594, 591, 576, 550, 548, 528, 521, 489, 488, 473, 460, 459, 450,
449, 445, 442, 434, 426, 417, 398, 395, 394, 359, 357, 348, 347, 346, 449, 445, 442, 434, 426, 417, 398, 395, 394, 359, 357, 348, 347, 346,
343, 312, 301, 300, 271, 241, 210, 203, 202, 197, 190, 178, 176, 175, 343, 312, 301, 300, 271, 241, 210, 203, 202, 197, 190, 178, 176, 175,
166, 165, 161, 151, 150, 146, 145, 143, 142, 128, 127, 123, 122, 93, 166, 165, 161, 151, 150, 146, 145, 143, 142, 128, 127, 123, 122, 93,
91, 80, 79, 70, 67, 65, 62, 60, 59, 56, 55, 54, 53, 41, 38, 33, 23, 91, 80, 79, 70, 67, 65, 62, 60, 59, 56, 55, 54, 53, 41, 38, 33, 23,
22, 20, 19, 17, 12 were deemed too old to be considered for millennium 22, 20, 19, 17, 12 were deemed too old to be considered for millennium
investigation. investigation.
13. Electronic Mail 13. Electronic Mail
13.1 Summary 13.1 Summary
The RFC's which were categorized into this group were the Simple Mail The RFC's which were categorized into this group were the Simple Mail
Transfer Protocol (SMTP), Internet Mail Access Protocol (IMAP), Post Transfer Protocol (SMTP), Internet Mail Access Protocol (IMAP), Post
Office Protocol (POP), Multipurpose Internet Mail Exchange (MIME), and Office Protocol (POP), Multipurpose Internet Mail Exchange (MIME),
X.400 to SMTP interaction. and X.400 to SMTP interaction.
After reviewing all mail-related RFCs, it was discovered that while After reviewing all mail-related RFCs, it was discovered that while
some obsolete standards required two-digit years, all currently used some obsolete standards required two-digit years, all currently used
standards require four-digit years and are thus not prone to typical standards require four-digit years and are thus not prone to typical
Year 2000 problems. Year 2000 problems.
13.2 Specifics 13.2 Specifics
RFCs 821 and 822, the main basis for SMTP mail exchange and message RFCs 821 and 822, the main basis for SMTP mail exchange and message
format, originally required two-digit years. However, both of these format, originally required two-digit years. However, both of these
RFCs were later modified by RFC 1123 in 1989, which strongly RFCs were later modified by RFC 1123 in 1989, which strongly
recommended 4-digit years. Although there might be a few very old recommended 4-digit years. Although there might be a few very old
SMTP systems using two-digit years, it is believed that almost all SMTP systems using two-digit years, it is believed that almost all
mail sent over the Internet today uses four-digit years. Mail that mail sent over the Internet today uses four-digit years. Mail that
contains two-digit years in its SMTP headers will not "fail", but contains two-digit years in its SMTP headers will not "fail", but
might be mis-sorted in message stores and mail user agents. This might be mis-sorted in message stores and mail user agents. This
problem is avoided entirely by taking the RFC 1123 change as a problem is avoided entirely by taking the RFC 1123 change as a
requirement, rather than merely as a recommendation. requirement, rather than merely as a recommendation.
IMAP versions 1, 2, and 3 used two-digit years, but IMAP version 4 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 (defined in RFCs 1730 and 1732 in 1994) requires four-digit years.
years. There are still a few IMAP 2 servers and clients in use on the There are still a few IMAP 2 servers and clients in use on the
Internet today, but IMAP version 4 has already taken over almost all of Internet today, but IMAP version 4 has already taken over almost all
the IMAP market. Mail stored on an IMAP server or client with of the IMAP market. Mail stored on an IMAP server or client with
two-digit years will not "fail", but could possibly be mis-sorted or two-digit years will not "fail", but could possibly be mis-sorted or
prematurely expired. prematurely expired.
RFC 1153 describes a format for digests of mailing lists, and uses 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 two-digit dates. This format is not widely used. The use of two-digit
dates could possibly cause missorting of stored messages. dates could possibly cause missorting of stored messages.
RFC 1327, which describes mapping between X.400 mail and SMTP mail, RFC 1327, which describes mapping between X.400 mail and SMTP mail,
uses the UTCTime format. uses the UTCTime format.
RFC 1422 describes the structure of certificates that were used in PEM RFC 1422 describes the structure of certificates that were used in
(and are expected to be used in many other mail and non-mail PEM (and are expected to be used in many other mail and non-mail
services). Those certificates use dates in UTCTime format. Poorly services). Those certificates use dates in UTCTime format. Poorly
written software might prematurely expire or validate a certificate written software might prematurely expire or validate a certificate
based on comparisons of the date with the current date, although no based on comparisons of the date with the current date, although no
current software is known to do this. current software is known to do this.
14. Network Time Protocols 14. Network Time Protocols
14.1 Summary 14.1 Summary
The RFC's which were categorized into this group were the Network Time The RFC's which were categorized into this group were the Network
Protocol (NTP), and the Time Protocol. Time Protocol (NTP), and the Time Protocol.
NTP has been certified year 2000 compliant, while the Time Protocol NTP has been certified year 2000 compliant, while the Time Protocol
will "roll over" at Thu Feb 07 00:54:54 2036 GMT. Since NTP is the will "roll over" at Thu Feb 07 00:54:54 2036 GMT. Since NTP is the
current defacto standard for network time this does not seem to be an current defacto standard for network time this does not seem to be an
issue. issue.
14.2 Specifics 14.2 Specifics
There is no reference anywhere in the NTP specification or There is no reference anywhere in the NTP specification or
implementation to any reference epoch other than 1 January 1900. In implementation to any reference epoch other than 1 January 1900. In
short, NTP doesn't know anything about the millennium. short, NTP doesn't know anything about the millennium.
>From the Time Protocol RFC (868): >From the Time Protocol RFC (868):
S: Send the time as a 32 bit binary number. S: Send the time as a 32 bit binary number.
... ...
The time is the number of seconds since 00:00 (midnight) 1 January 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 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. GMT; this base will serve until the year 2036.
15. Name Services 15. Name Services
15.1 Summary 15.1 Summary
The RFC's which were categorized into this group were the Domain Name The RFC's which were categorized into this group were the Domain Name
System (DNS), it's advanced add on features (Incremental Zone System (DNS), it's advanced add on features (Incremental Zone
Transfer, etc.). Transfer, etc.).
There have been no year 2000 relayed problems found with the DNS There have been no year 2000 relayed problems found with the DNS
protocols, or common implementations of them. protocols, or common implementations of them.
15.2 Specifics 15.2 Specifics
One is a common practice of writing serial numbers in zone files as if One is a common practice of writing serial numbers in zone files as
they represent a date, and using only two digits of the year. That if they represent a date, and using only two digits of the year.
practice cannot survive into the year 2000. This is not a protocol That practice cannot survive into the year 2000. This is not a
problem, the serial number is simply an integer, and any value is OK, protocol problem, the serial number is simply an integer, and any
provided it always increases (see rfc1982 for a definition of what value is OK, provided it always increases (see rfc1982 for a
that means). In any case, a change from 97abcd (or similar) to 00abcd definition of what that means). In any case, a change from 97abcd
would be a decrease and so is not permitted. Zone file maintainers (or similar) to 00abcd would be a decrease and so is not permitted.
have two choices, one easy (though irrational) one would be to Zone file maintainers have two choices, one easy (though irrational)
continue from 99 to 100 and so on. The other, is simply to switch, at one would be to continue from 99 to 100 and so on. The other, is
any time between now and when the serial number first needs updating simply to switch, at any time between now and when the serial number
after the year 2000, to use 4 digits to represent the year instead of first needs updating after the year 2000, to use 4 digits to
2. As long as there are no more than 6 digits in the "abcd" part, and represent the year instead of 2. As long as there are no more than 6
this is done sometime before the year 2100, this is always an digits in the "abcd" part, and this is done sometime before the year
increase, and therefore always safe. Should any zone files be of the 2100, this is always an increase, and therefore always safe. Should
form yyabcdefg (with 7 digits after a 2-digit year) then the any zone files be of the form yyabcdefg (with 7 digits after a 2-
procedures of section 7 of rfc2182 should be adopted to convert the digit year) then the procedures of section 7 of rfc2182 should be
serial number to some other value. adopted to convert the serial number to some other value.
The other item of note is related to timestamps in DNS security. The other item of note is related to timestamps in DNS security.
Those are represented as 32 bit counts of seconds, based in 1970, and Those are represented as 32 bit counts of seconds, based in 1970, and
hence have no year 2000 problems. however, they do obviously have a hence have no year 2000 problems. however, they do obviously have a
natural end of life, and sometime before that time is reached, the natural end of life, and sometime before that time is reached, the
definitions of those fields need to be corrected, perhaps to allow definitions of those fields need to be corrected, perhaps to allow
them to represent the number of seconds elapsed since the base, modulo them to represent the number of seconds elapsed since the base,
2^32, which is likely to be adequate for the purposes of DNS security modulo 2^32, which is likely to be adequate for the purposes of DNS
(signatures and keys are unlikely to need to be valid for more than 70 security (signatures and keys are unlikely to need to be valid for
years). In any case, more work is needed in this area in the not too more than 70 years). In any case, more work is needed in this area
far distant future. in the not too far distant future.
16 Network Management 16 Network Management
16.1 Summary 16.1 Summary
The RFC's which were categorized into this group were the Simple The RFC's which were categorized into this group were the Simple
Network Management Protocol (SNMP), a large number of Management Network Management Protocol (SNMP), a large number of Management
Information Bases (MIBs) and the Common Management Information Information Bases (MIBs) and the Common Management Information
Protocol over TCP/IP (CMOT). Protocol over TCP/IP (CMOT).
Although a few discrepancies have been found and outlined below, none Although a few discrepancies have been found and outlined below, none
of them should have an impact on interoperability. of them should have an impact on interoperability.
16.2 Specifics 16.2 Specifics
16.2.1 Use of GeneralizedTime in CMOT as defined in RFCs 1095 and 1189. 16.2.1 Use of GeneralizedTime in CMOT as defined in RFCs 1095 and
1189.
The standards for CMOT specify an unusual use for the GeneralizedTime The standards for CMOT specify an unusual use for the GeneralizedTime
type. (GeneralizedTime has a four-digit representation of the year.) type. (GeneralizedTime has a four-digit representation of the year.)
If the system generating the PDU does not have the current time, yet 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 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 to encode this information. The time since last boot will be added
the base time "0001 Jan 1 00:00:00.00" using the Gregorian calendar to the base time "0001 Jan 1 00:00:00.00" using the Gregorian
algorithm. calendar algorithm.
This is really a "Year 0" problem rather than a Year 2000 problem, and This is really a "Year 0" problem rather than a Year 2000 problem,
in any case, CMOT is not currently deployed. and in any case, CMOT is not currently deployed.
16.2.2 UTCTime in SNMP Definitions 16.2.2 UTCTime in SNMP Definitions
UTCTime is an ASN.1 type that includes a two-digit representation of 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 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 in precision and in local versus GMT, but these options all have
two-digit years. The standards for SNMP definitions specify one two-digit years. The standards for SNMP definitions specify one
particular format: particular format:
YYMMDDHHMMZ YYMMDDHHMMZ
The first usage of UTCTime in the standards for SNMP definitions goes 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 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 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 definitions is to record the history of an SNMP MIB module in the
module itself, via two ASN.1 macros: module itself, via two ASN.1 macros:
o LAST-UPDATED o LAST-UPDATED
o REVISION o REVISION
Management applications that store and use MIB modules need to be Management applications that store and use MIB modules need to be
smart about interpreting these UTCTimes, by prepending a "19" or a smart about interpreting these UTCTimes, by prepending a "19" or a
"20" as appropriate. "20" as appropriate.
16.2.3 Objects in the Printer MIB (RFC 1559) 16.2.3 Objects in the Printer MIB (RFC 1559)
There are two objects in the Printer MIB that allow use of a date as 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. an object value with no explicit guidance for formatting the value.
The objects are prtInterpreterLangVersion and prtInterpreterVersion. The objects are prtInterpreterLangVersion and prtInterpreterVersion.
Both are defined with a syntax of OCTET STRING. The descriptions for 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 the objects allow the object value to contain a date, version code or
other product specific information to identify the interpreter or other product specific information to identify the interpreter or
language. The descriptions do not include an explicit statement language. The descriptions do not include an explicit statement
recommending use of a four-digit year when a date is used as the recommending use of a four-digit year when a date is used as the
object value. object value.
16.2.4 Dates in Mobile Network Tracing Records (RFC 2041) 16.2.4 Dates in Mobile Network Tracing Records (RFC 2041)
The RFC specifies trace headers and footers with date fields that are The RFC specifies trace headers and footers with date fields that are
character arrays of size 32. While 32 characters certainly provide character arrays of size 32. While 32 characters certainly provide
enough room for a four-digit year, there's no explicit statement that enough room for a four-digit year, there's no explicit statement that
these years must be represented with four digits. these years must be represented with four digits.
17 Network News 17 Network News
17.1 Summary 17.1 Summary
The RFC's which were categorized into this group were related to the The RFC's which were categorized into this group were related to the
Network News Protocol (NNTP). Network News Protocol (NNTP).
There does exist a problem in both NNTP, RFC 977, and the Usenet News There does exist a problem in both NNTP, RFC 977, and the Usenet News
Message Format, RFC 10336. They both specify two-digit year format. Message Format, RFC 10336. They both specify two-digit year format.
A working group has been formed to update the network news protocols A working group has been formed to update the network news protocols
in general, and addressing this problem is on their list of work in general, and addressing this problem is on their list of work
items. items.
17.2 Specifics 17.2 Specifics
The NNTP transfer protocols defined in RFC 977. Sections 3.7.1, the The NNTP transfer protocols defined in RFC 977. Sections 3.7.1, the
definition of the NEWGROUPS command, and 3.8.1, the NEWNEWS command, definition of the NEWGROUPS command, and 3.8.1, the NEWNEWS command,
that dates must be specified in YYMMDD format. that dates must be specified in YYMMDD format.
The format for USENET news messages is defined in RFC 1036. The Date The format for USENET news messages is defined in RFC 1036. The Date
line is defined in section 2.1.2 and it is specified in RFC-822 line is defined in section 2.1.2 and it is specified in RFC-822
format. It specifically disallows the standard UNIX ctime(3) format, format. It specifically disallows the standard UNIX ctime(3) format,
which would allow for four digit years. Section 2.2.4 on Expires also which would allow for four digit years. Section 2.2.4 on Expires
mandates the same two-digit year format. also mandates the same two-digit year format.
18. Real Time Services 18. Real Time Services
18.1 Summary 18.1 Summary
The RFC's which were categorized into this group were related to IP The RFC's which were categorized into this group were related to IP
Multicast, RTP, and Internet Stream Protocol. A Year 2000 problem Multicast, RTP, and Internet Stream Protocol. A Year 2000 problem
does occur in the Simple Network Paging Protocol, versions 2 & 3. does occur in the Simple Network Paging Protocol, versions 2 & 3.
Both define a HOLDuntil option which uses a YYMMDDHHMMSS+/-GMT field. Both define a HOLDuntil option which uses a YYMMDDHHMMSS+/-GMT field.
Version 3 also defines a MSTAtus command, which is required to store, Version 3 also defines a MSTAtus command, which is required to store,
dates and times as YYMMDDHHMMSS+/-GMT. dates and times as YYMMDDHHMMSS+/-GMT.
18.2 Specifics 18.2 Specifics
RFC 2102 discusses Multicast support for NIMROD and has no mention of RFC 2102 discusses Multicast support for NIMROD and has no mention of
dates or time. RFC 2090 on TFTP Multicast options is also free from dates or time. RFC 2090 on TFTP Multicast options is also free from
any date/time references. any date/time references.
RFC 2038 on RTP MPEG formats has three references to time: a RFC 2038 on RTP MPEG formats has three references to time: a
Presentation Time Stamp (PTS), a Decoding Time Stamp (DTS), and a Presentation Time Stamp (PTS), a Decoding Time Stamp (DTS), and a
System Clock (SC) reference time. Each RTP packet contains a System Clock (SC) reference time. Each RTP packet contains a
timestamp derived from the sender 90 kHz clock reference. Each of the timestamp derived from the sender 90 kHz clock reference. Each of
header fields are defined in section 2.1, 3, and 3.3 are 32 bit the header fields are defined in section 2.1, 3, and 3.3 are 32 bit
fields. No mention is made of a "zero" start time, so it is presumed fields. No mention is made of a "zero" start time, so it is presumed
that this format will be valid until at least 2038. that this format will be valid until at least 2038.
Similarly RFC 2035 on the RTP JPEG format defines the same timestamp Similarly RFC 2035 on the RTP JPEG format defines the same timestamp
in section 3. RFC 2032 on RTP H.261 video streams uses a calculated in section 3. RFC 2032 on RTP H.261 video streams uses a calculated
time based on the original frame so once again there is no millennium time based on the original frame so once again there is no millennium
issue. RFC 2029 on the RTP format for Sun's CellB video encoding issue. RFC 2029 on the RTP format for Sun's CellB video encoding
mentions the RTP timestamp in section 2.1. mentions the RTP timestamp in section 2.1.
RFC 2022 defines support for multicast over UNI 3.0/3.1 based ATM RFC 2022 defines support for multicast over UNI 3.0/3.1 based ATM
networks. Section 5. defines a timeout value for connections between networks. Section 5. defines a timeout value for connections
one and twenty minutes. Section 5.1.1 discusses several timers that between one and twenty minutes. Section 5.1.1 discusses several
are bound between five and ten seconds, while 5.1.3 requires an timers that are bound between five and ten seconds, while 5.1.3
inactivity timer, which should also run between one and twenty requires an inactivity timer, which should also run between one and
minutes. Sections 5.1.5, 5.1.5.1, 5.1.5.2, 5.2.2, 5.4, 5.4.1, 5.4.2, twenty minutes. Sections 5.1.5, 5.1.5.1, 5.1.5.2, 5.2.2, 5.4, 5.4.1,
5.4.3, 6.1.3 and Appendix E all defines numerous timers, none of which 5.4.2, 5.4.3, 6.1.3 and Appendix E all defines numerous timers, none
have any millennium issues. of which have any millennium issues.
RFC 1890 on RTP profiles for audio and video conferences discusses a RFC 1890 on RTP profiles for audio and video conferences discusses a
sampling frequency which has no issues. RFC 1889 on RTP discusses sampling frequency which has no issues. RFC 1889 on RTP discusses
time formats in section 4, as the same 64 bit unsigned integer format time formats in section 4, as the same 64 bit unsigned integer format
that NTP uses. There is a "period" problem, which will occur in the that NTP uses. There is a "period" problem, which will occur in the
year 2106. Section 5.1 is a more formalized discussion of the year 2106. Section 5.1 is a more formalized discussion of the
timestamp properties, while Section 6.3.1 discusses a variety of timestamp properties, while Section 6.3.1 discusses a variety of
different timers all using the 64 bit field format, or a compressed different timers all using the 64 bit field format, or a compressed
32-bit version of the inner octet of bytes. Section 8.2 discusses 32-bit version of the inner octet of bytes. Section 8.2 discusses
loop detection and how the various timers are used to determine if loop detection and how the various timers are used to determine if
looping occurs. looping occurs.
RFC 1861 on Version 3 of the Simple Network Paging Protocol does have RFC 1861 on Version 3 of the Simple Network Paging Protocol does have
a Year 2000 problem. The protocol defines a HOLDuntil command in a Year 2000 problem. The protocol defines a HOLDuntil command in
section 4.5.6 and a MSTAtus command in section 4.6.10, both of which section 4.5.6 and a MSTAtus command in section 4.6.10, both of which
require dates/times to be stored as YYMMDDHHMMSS+/-GMT. Clearly this require dates/times to be stored as YYMMDDHHMMSS+/-GMT. Clearly this
format will be invalid after the end of 1999. format will be invalid after the end of 1999.
RFC 1821 has no date/time references. RFC 1819 on Version 2 of the RFC 1821 has no date/time references. RFC 1819 on Version 2 of the
Internet Stream Protocol defines a HELLO message format in section Internet Stream Protocol defines a HELLO message format in section
6.1.2, which does contain a timer which is updated every millisecond. 6.1.2, which does contain a timer which is updated every millisecond.
No year 2000 problems exist with this protocol. No year 2000 problems exist with this protocol.
RFC 1645 on Version 2 of the Simple Network Paging Protocol contains RFC 1645 on Version 2 of the Simple Network Paging Protocol contains
the same HOLDuntil field problem as version 3. The definition is the same HOLDuntil field problem as version 3. The definition is
contained section 4.4.6. contained section 4.4.6.
RFC 1458 on the Requirements of Multicast Protocols discusses a RFC 1458 on the Requirements of Multicast Protocols discusses a
retransmission timer in section 4.23. and a general discussion of retransmission timer in section 4.23. and a general discussion of
timer expiration in section 5, neither of which have any millennium timer expiration in section 5, neither of which have any millennium
concerns. RFC 1301 on the Multicast Transport Protocol defines a concerns. RFC 1301 on the Multicast Transport Protocol defines a
heartbeat interval of time in section 2.1, as well as retention and heartbeat interval of time in section 2.1, as well as retention and
windows. Formal definitions for each are contained in sections 2.2.7, windows. Formal definitions for each are contained in sections
2.2.8 and 2.2.9. The heartbeat is a 32 bit unsigned field, while the 2.2.7, 2.2.8 and 2.2.9. The heartbeat is a 32 bit unsigned field,
Window and Retention are both 16 bit unsigned fields. Section 3.4.2 while the Window and Retention are both 16 bit unsigned fields.
gives examples values for these fields, which indicate no millennium Section 3.4.2 gives examples values for these fields, which indicate
issues. no millennium issues.
RFC 1193 on Client Requirements for Real Time Services talks about RFC 1193 on Client Requirements for Real Time Services talks about
time in section 4.4, but there are no Year 2000 issues. RFC 1190 have time in section 4.4, but there are no Year 2000 issues. RFC 1190
been obsoleted by RFC 1819, but the hello timer issues are similar. have been obsoleted by RFC 1819, but the hello timer issues are
similar.
RFCs 1789, 1768, 1703, 1614, 1569, 1568, 1546, 1469, 1453, 1313, 1257, RFCs 1789, 1768, 1703, 1614, 1569, 1568, 1546, 1469, 1453, 1313,
1197, 1112, 1054, 988, 966, 947, 809, 804, 803, 798, 769, 741, 511, 1257, 1197, 1112, 1054, 988, 966, 947, 809, 804, 803, 798, 769, 741,
508, 420, 408 and 251 contain no date or time references. 511, 508, 420, 408 and 251 contain no date or time references.
19. Routing 19. Routing
19.1 Summary 19.1 Summary
The RFC's which were categorized into this group were Routing The RFC's which were categorized into this group were Routing
Information Protocol (RIP), the Open Shortest Path First (OSPF) Information Protocol (RIP), the Open Shortest Path First (OSPF)
protocol, Classless InterDomain Routing (CIDR),the Border Gateway protocol, Classless InterDomain Routing (CIDR),the Border Gateway
Protocol (BGP), and the InterDomain Routing Protocol (IDRP). Protocol (BGP), and the InterDomain Routing Protocol (IDRP).
After careful examination both BGP and RIP have been found Year 2000 After careful examination both BGP and RIP have been found Year 2000
compliant. compliant.
There is a small Year 2000 issue in RFC 1786 on the Representation of There is a small Year 2000 issue in RFC 1786 on the Representation of
IP Routing Policies in the ripe-81++ Routing Registry. In Appendices IP Routing Policies in the ripe-81++ Routing Registry. In Appendices
C the "changed" object parameter defines a format of <email-address> C the "changed" object parameter defines a format of <email-address>
YYMMDD, and similarly in Appendix D "withdrawn" object identifier has YYMMDD, and similarly in Appendix D "withdrawn" object identifier has
he format of YYMMDD. Since these are only identifiers there should be he format of YYMMDD. Since these are only identifiers there should
little operational impact. Some application software may need to be be little operational impact. Some application software may need to
modified. be modified.
IDPR suffers from the classic Year 2038 problem, by having a timestamp IDPR suffers from the classic Year 2038 problem, by having a
counter which rolls over at that time. timestamp counter which rolls over at that time.
19.2 Specifics 19.2 Specifics
RFC 2091 on Extensions to RIP to Support Demand Circuits defines three RFC 2091 on Extensions to RIP to Support Demand Circuits defines
required and one optional timers in section 6. The Database Timer three required and one optional timers in section 6. The Database
(6.1), the Hold down Timer (6.2), the Retransmission Time (6.3) and Timer (6.1), the Hold down Timer (6.2), the Retransmission Time (6.3)
the Over-Subscription Timer (6.4) are all counters, which have no and the Over-Subscription Timer (6.4) are all counters, which have no
millennium, issues. RFC 2081 on the applicability of RIPng discusses millennium, issues. RFC 2081 on the applicability of RIPng discusses
deletion of routes for a variety of issues, one of which is the deletion of routes for a variety of issues, one of which is the
garbage- collection timer exceeds 120 seconds. There are no Year 2000 garbage- collection timer exceeds 120 seconds. There are no Year
issues. RFC 2080 on RIPng for IPv6, discusses various times in 2000 issues. RFC 2080 on RIPng for IPv6, discusses various times in
section 2.6, none of which have any millennium problems. section 2.6, none of which have any millennium problems.
RFC 1987 on Ipsilon's General Switch Management protocol there is a RFC 1987 on Ipsilon's General Switch Management protocol there is a
Duration field defined in section 4, which has no relevant problems. Duration field defined in section 4, which has no relevant problems.
Section 8.2 defines the procedure for dealing with timers. RFC 1953 Section 8.2 defines the procedure for dealing with timers. RFC 1953
on Ipsilon's Flow Management Specification for IPv4 defines the same on Ipsilon's Flow Management Specification for IPv4 defines the same
procedure in section 3.2, as well as a lifetime field in the Redirect procedure in section 3.2, as well as a lifetime field in the Redirect
Message (Section 4.1). There are no millennium issues in either case. Message (Section 4.1). There are no millennium issues in either
case.
There is a small Year 2000 issue in RFC 1786 on the Representation of There is a small Year 2000 issue in RFC 1786 on the Representation of
IP Routing Policies in the ripe-81++ Routing Registry. In Appendices IP Routing Policies in the ripe-81++ Routing Registry. In Appendices
C the "changed" object parameter defines a format of <email-address> C the "changed" object parameter defines a format of <email-address>
YYMMDD, and similarly in Appendix D "withdrawn" object identifier has YYMMDD, and similarly in Appendix D "withdrawn" object identifier has
he format of YYMMDD. Since these are only identifiers there should be he format of YYMMDD. Since these are only identifiers there should
little operational impact. Some application software may need to be be little operational impact. Some application software may need to
modified. be modified.
RFC 1771 defines the Border Gateway Protocol (BGP). BGP does not have RFC 1771 defines the Border Gateway Protocol (BGP). BGP does not
knowledge of absolute time, only relative time. There are five timers have knowledge of absolute time, only relative time. There are five
defined: Hold Timer, ConnectRetry Timer, KeepAlive Timer, timers defined: Hold Timer, ConnectRetry Timer, KeepAlive Timer,
MinRoueAdvertisementInterval and MinASOriginationInterval. There are MinRoueAdvertisementInterval and MinASOriginationInterval. There are
no known issues regarding BGP and the millennium. no known issues regarding BGP and the millennium.
In RFC 1584, which defines Multicast Extensions to OSPF, three timers In RFC 1584, which defines Multicast Extensions to OSPF, three timers
are defined in section 8.2: IGMPPollingInterval, IGMPTimeout, and IGMP are defined in section 8.2: IGMPPollingInterval, IGMPTimeout, and
polling timer. Section 8.4 defines an age parameter for the local IGMP polling timer. Section 8.4 defines an age parameter for the
groups database and section 9.3 outlines how to implement that age local groups database and section 9.3 outlines how to implement that
parameter. It is not expected that any connections lifetime will be age parameter. It is not expected that any connections lifetime will
long enough to cause any issues with these timers. be long enough to cause any issues with these timers.
RFC 1583, OSPF, there are two types of timers defined in section 4.4, RFC 1583, OSPF, there are two types of timers defined in section 4.4,
single-shot timers and interval timers. There are a number of timers single-shot timers and interval timers. There are a number of timers
defined in Section 9 including: HelloInterval, RouterDeadInterval, defined in Section 9 including: HelloInterval, RouterDeadInterval,
InfTransDelay, Hello Timer, Wait Timer and RxmtInterval. Section 10 InfTransDelay, Hello Timer, Wait Timer and RxmtInterval. Section 10
also defines the Inactivity Timer. No millennium problem exists for also defines the Inactivity Timer. No millennium problem exists for
any of these timers. any of these timers.
RFC 1582 is an earlier version of RFC 2091. Section 7 documents the RFC 1582 is an earlier version of RFC 2091. Section 7 documents the
same timers as noted above, with the same lack of a millennium issue. same timers as noted above, with the same lack of a millennium issue.
RFC 1504 on Appletalk Update-Based Routing Protocol defines a RFC 1504 on Appletalk Update-Based Routing Protocol defines a 10-
10-second period in Section 3, and hence has no relevant issues. second period in Section 3, and hence has no relevant issues.
RFC 1479 which specifies IDPR Version 1, defines a timestamp field in RFC 1479 which specifies IDPR Version 1, defines a timestamp field in
section 1.5.1, which is a 32 bit unsigned integer number of seconds section 1.5.1, which is a 32 bit unsigned integer number of seconds
since January 1, 1970. The authors recognize the problem of timestamp since January 1, 1970. The authors recognize the problem of
exhaustion in 2038, but feel that the protocol will not be in use for timestamp exhaustion in 2038, but feel that the protocol will not be
that period. Sections 1.7, 2.1, and 4.3.1 also discuss the timestamp in use for that period. Sections 1.7, 2.1, and 4.3.1 also discuss
field. RFC 1478 on the IDPR Architecture, also discusses the same the timestamp field. RFC 1478 on the IDPR Architecture, also
timestamp field in section 3.3.4. RFC 1477 again refers to the IDPR discusses the same timestamp field in section 3.3.4. RFC 1477 again
timestamp in section 4.2. Thus IDPR has no Year 2000 issue, but does refers to the IDPR timestamp in section 4.2. Thus IDPR has no Year
have a period problem in the year 2038. 2000 issue, but does have a period problem in the year 2038.
RFC 1075 on Distance Vector Multicast Routing Protocol devotes section RFC 1075 on Distance Vector Multicast Routing Protocol devotes
7 to time values. None of the timers have any millennium issues. RFC section 7 to time values. None of the timers have any millennium
1074, on the NFSNET backbone SPF IGP defines several hardcoded timers issues. RFC 1074, on the NFSNET backbone SPF IGP defines several
values in section 5. hardcoded timers values in section 5.
RFC 1058 on RIP discusses the 30-second timers in section 3.3. There is no millennium RFC 1058 on RIP discusses the 30-second timers in section 3.3. There
issues related to RIP. is no millennium issues related to RIP.
RFC 995 on the Requirements for Internet Gateways has extensive RFC 995 on the Requirements for Internet Gateways has extensive
discussions of timers in section 7.1 and throughout A.1 and A.2. None discussions of timers in section 7.1 and throughout A.1 and A.2.
of these timers suffer from the millennium problem. None of these timers suffer from the millennium problem.
RFC 911 on EGP on Berkeley Unix recommend timer values of 30 and 120 seconds. RFC 911 on EGP on Berkeley Unix recommend timer values of 30 and 120
seconds.
RFC 904 which defines the Exterior Gateway Protocol (EGP). There are RFC 904 which defines the Exterior Gateway Protocol (EGP). There are
a number of timers discussed in sections 4.1.1 and 4.1.4. None of a number of timers discussed in sections 4.1.1 and 4.1.4. None of
these timers suffer from any relevant problems. these timers suffer from any relevant problems.
RFCs 2103, 2092, 2073, 2072, 2042, 2008, 1998, 1997, 1992, 1966, 1955, RFCs 2103, 2092, 2073, 2072, 2042, 2008, 1998, 1997, 1992, 1966, 1955,
1940, 1930, 1925, 1923, 1863, 1817, 1812, 1793, 1787, 1774, 1773, 1940, 1930, 1925, 1923, 1863, 1817, 1812, 1793, 1787, 1774, 1773,
1772, 1765, 1753, 1745, 1723, 1722, 1721, 1716, 1702, 1701, 1668, 1772, 1765, 1753, 1745, 1723, 1722, 1721, 1716, 1702, 1701, 1668,
1656, 1655, 1654, 1587, 1586, 1585, 1581, 1520, 1519, 1517, 1482, 1656, 1655, 1654, 1587, 1586, 1585, 1581, 1520, 1519, 1517, 1482,
1476, 1439, 1403, 1397, 1388, 1387, 1383, 1380, 1371, 1370, 1364, 1476, 1439, 1403, 1397, 1388, 1387, 1383, 1380, 1371, 1370, 1364,
1338, 1322, 1268, 1267, 1266, 1265, 1264, 1254, 1246, 1245, 1222, 1338, 1322, 1268, 1267, 1266, 1265, 1264, 1254, 1246, 1245, 1222,
1195, 1164, 1163, 1142, 1136, 1133, 1126, 1125, 1124,1104, 1102, 1092, 1195, 1164, 1163, 1142, 1136, 1133, 1126, 1125, 1124,1104, 1102, 1092,
1009, 985, 981, 975, 950, 898, 890, 888, 875, and 823 contain no date 1009, 985, 981, 975, 950, 898, 890, 888, 875, and 823 contain no date
or time references. or time references.
20. Security 20. Security
20.1 Summary 20.1 Summary
The RFC's which were categorized into this group were kerberos The RFC's which were categorized into this group were kerberos
authentication protocol, Remote Authentication Dial In User Service authentication protocol, Remote Authentication Dial In User Service
(RADIUS), One Time Password System (OTP), Privacy Enhanced Mail (PEM), (RADIUS), One Time Password System (OTP), Privacy Enhanced Mail
security extensions to a variety of protocols including (but not (PEM), security extensions to a variety of protocols including (but
limited to) RIPv2, HTTP, MIME, PPP, IP, Telnet and FTP. Encryption not limited to) RIPv2, HTTP, MIME, PPP, IP, Telnet and FTP.
and authentication algorithms are also examined.
RFC 1507 on Distributed Authentication Security Services (DASS) Encryption and authentication algorithms are also examined.
discusses time and secure time in an expository manner in Sections
1.2.2, 1.4.4 and 2.1. Section 3.6 defines absolute time as an UTC
time with a precision of 1 second, and Section 4.1 discusses ANS.1
encoding of time values. Because of the imprecision of the UTC time
definition there could be problems with this protocol.
RFCs 1421-1424 specifies that PEM uses UTC time formats which could RFC 1507 on Distributed Authentication Security Services (DASS)
have a Millennium issue since the year specification only provides the discusses time and secure time in an expository manner in Sections
last two digits of the year. 1.2.2, 1.4.4 and 2.1. Section 3.6 defines absolute time as an UTC
time with a precision of 1 second, and Section 4.1 discusses ANS.1
encoding of time values. Because of the imprecision of the UTC time
definition there could be problems with this protocol.
RFCs 1421-1424 specifies that PEM uses UTC time formats which could
have a Millennium issue since the year specification only provides
the last two digits of the year.
20.2 Specifics 20.2 Specifics
RFC 2082 on RIP-2 MD5 Authentication requires storage of security keys RFC 2082 on RIP-2 MD5 Authentication requires storage of security
for a specified lifetime in sections 4.1 and 4.2. There are no keys for a specified lifetime in sections 4.1 and 4.2. There are no
millennium issues in this protocol. millennium issues in this protocol.
RFC 2078 on the GSSAPI Version 2 defines numerous calls that use RFC 2078 on the GSSAPI Version 2 defines numerous calls that use
timers for inputs and outputs. Sections 2.1.1, 2.1.3, 2.1.4, 2.1.5, timers for inputs and outputs. Sections 2.1.1, 2.1.3, 2.1.4, 2.1.5,
2.2.1, 2.2.2, 2.2.5 and 2.2.6 all use the lifetime_rec field, which is 2.2.1, 2.2.2, 2.2.5 and 2.2.6 all use the lifetime_rec field, which
defined as an integer counter in seconds. There should be no relevant is defined as an integer counter in seconds. There should be no
problems with this protocol. relevant problems with this protocol.
RFC 2069 on Digest Authentication for HTTP, defines a 'date' and a RFC 2069 on Digest Authentication for HTTP, defines a 'date' and a
'last-modified' field in Section 2.1.2. Both are required to be RFC 1123 formats which is not subject to millennium issues. Section 3.2
1123 formats which is not subject to millennium issues. Section 3.2 discusses dates and times in the context of thwarting replay attacks,
discusses dates and times in the context of thwarting replay attacks, but have no relevant issues.
but have no relevant issues.
RFC 2065 on DNS Security extensions first discusses time in section RFC 2065 on DNS Security extensions first discusses time in section
2.3.3. The SIG RDATA format is defined in Section 4.1 discusses "time 2.3.3. The SIG RDATA format is defined in Section 4.1 discusses
signed" field and defines it to be a 32 bit unsigned integer number of "time signed" field and defines it to be a 32 bit unsigned integer
seconds since January 1, 1970. There will be a period problem in 2038 number of seconds since January 1, 1970. There will be a period
because of rollover. Section 4.5 on the file representations of SIG problem in 2038 because of rollover. Section 4.5 on the file
RRs specifies the time field is expressed as YYYYMMDDHHMMSS which is representations of SIG RRs specifies the time field is expressed as
clearly Year 2000 compliant. YYYYMMDDHHMMSS which is clearly Year 2000 compliant.
RFC 2059 on RADIUS account formats defines a "time" attribute, which RFC 2059 on RADIUS account formats defines a "time" attribute, which
is optional which is a 32 bit unsigned integer number of seconds since is optional which is a 32 bit unsigned integer number of seconds
January 1, 1970. Likewise RFC 2058 on RADIUS also defines this since January 1, 1970. Likewise RFC 2058 on RADIUS also defines this
optional attribute in the same way. There will be a potential period optional attribute in the same way. There will be a potential period
problem that occurs on 2038. problem that occurs on 2038.
RFC 2035 on the Simple Public Key GSSAPI Mechanism talks about secure RFC 2035 on the Simple Public Key GSSAPI Mechanism talks about secure
timestamps in the background and overview sections only in an timestamps in the background and overview sections only in an
expository manner. expository manner.
RFC 1969 on the PPP DES Encryption Protocol uses time as an example in RFC 1969 on the PPP DES Encryption Protocol uses time as an example
Section 4 when discussing how to encrypt the first packet of a stream. in Section 4 when discussing how to encrypt the first packet of a
It is suggested that the first 32 bits be used for the number of stream. It is suggested that the first 32 bits be used for the
seconds since January 1, 1970. There could thus be a potential number of seconds since January 1, 1970. There could thus be a
operations problem in 2038. potential operations problem in 2038.
RFC 1898 on the CyberCash Credit Card Protocol provides an example RFC 1898 on the CyberCash Credit Card Protocol provides an example
message in Section 2.7 which uses a date field of the form message in Section 2.7 which uses a date field of the form
YYYYMMDDHHMM that is clearly Y2K compliant. YYYYMMDDHHMM that is clearly Y2K compliant.
RFC 1510, which defines Kerberos Version 5, makes extensive use of RFC 1510, which defines Kerberos Version 5, makes extensive use of
times in the security model. There are discussions in the times in the security model. There are discussions in the
Introduction, as well as Sections 1.2, and 3.1.3. Kerberos uses ASN.1 Introduction, as well as Sections 1.2, and 3.1.3. Kerberos uses
definitions to abstract values, and hence defines a base definition ASN.1 definitions to abstract values, and hence defines a base
for KerberosTime which is a generalized time format in Section 5.2. definition for KerberosTime which is a generalized time format in
>From the text: "Example: The only valid format for UTC time 6 minutes, Section 5.2. >From the text: "Example: The only valid format for UTC
27 seconds after 9 p.m. on 6 November 1985 is 19851106210627Z." A time 6 minutes, 27 seconds after 9 p.m. on 6 November 1985 is
side note is that the MIT reference implementation of the Kerberos, by 19851106210627Z." A side note is that the MIT reference
default set the expiration of tickets to December 31, 1999. This is implementation of the Kerberos, by default set the expiration of
not protocol related but could have some operational impacts. tickets to December 31, 1999. This is not protocol related but could
have some operational impacts.
RFC 1509 on GSSAPI C-bindings makes a single reference that all RFC 1509 on GSSAPI C-bindings makes a single reference that all
counters are in seconds and assigned as 32 bit unsigned integers. counters are in seconds and assigned as 32 bit unsigned integers.
Hence GSSAPI mechanisms may have problems in 2038. Hence GSSAPI mechanisms may have problems in 2038.
RFC 1507 on Distributed Authentication Security Services (DASS) RFC 1507 on Distributed Authentication Security Services (DASS)
discusses time and secure time in an expository manner in Sections discusses time and secure time in an expository manner in Sections
1.2.2, 1.4.4 and 2.1. Section 3.6 defines absolute time as an UTC 1.2.2, 1.4.4 and 2.1. Section 3.6 defines absolute time as an UTC
time with a precision of 1 second, and Section 4.1 discusses ANS.1 time with a precision of 1 second, and Section 4.1 discusses ANS.1
encoding of time values. Because of the imprecision of the UTC time encoding of time values. Because of the imprecision of the UTC time
definition there could be problems with this protocol. definition there could be problems with this protocol.
RFC 1424 on PEM Part IV defines a self-signed certificate request in RFC 1424 on PEM Part IV defines a self-signed certificate request in
Section 3.1. The validity period start and end times are both Section 3.1. The validity period start and end times are both
suggested to be January 1, 1970. RFC 1422 on PEM Part II defines the suggested to be January 1, 1970. RFC 1422 on PEM Part II defines the
validity period for a certificate in Section 3.3.6. It is recommended validity period for a certificate in Section 3.3.6. It is
that UTC Time formats are used, and notes the lack of a century so recommended that UTC Time formats are used, and notes the lack of a
that comparisons between different centuries must be done with care. century so that comparisons between different centuries must be done
No suggestions on how to do this are included. Sections 3.5.2 also with care. No suggestions on how to do this are included. Sections
discusses validity period in PEM CRLs. RFC 1421 on PEM Part I 3.5.2 also discusses validity period in PEM CRLs. RFC 1421 on PEM
discusses validity periods in an expository way. PEM as a whole could Part I discusses validity periods in an expository way. PEM as a
have problems after December 31, 1999 based on its use of UTC Time. whole could have problems after December 31, 1999 based on its use of
UTC Time.
RFCs 1113, 1114, and 1115 specify the original version of PEM and have RFCs 1113, 1114, and 1115 specify the original version of PEM and
been obsoleted bye 1421, 1422, 1423, & 1424. have been obsoleted bye 1421, 1422, 1423, & 1424.
RFCs 2104, 2085, 2084, 2057, 2040, 2015, 1984, 1968, 1964, 1961, 1949, RFCs 2104, 2085, 2084, 2057, 2040, 2015, 1984, 1968, 1964, 1961, 1949,
1948, 1938, 1929, 1928, 1858, 1852, 1851, 1829, 1828, 1827, 1826, 1948, 1938, 1929, 1928, 1858, 1852, 1851, 1829, 1828, 1827, 1826,
1825, 1824, 1760, 1751, 1750, 1704, 1675, 1579, 1535, 1511, 1492, 1825, 1824, 1760, 1751, 1750, 1704, 1675, 1579, 1535, 1511, 1492,
1457, 1455, 1423, 1416, 1412, 1411, 1409, 1408, 1321, 1320, 1319, 1457, 1455, 1423, 1416, 1412, 1411, 1409, 1408, 1321, 1320, 1319,
1281, 1244, 1186, 1170, 1156, 1108, 1004, 972, 931, 927, 912, and 644 1281, 1244, 1186, 1170, 1156, 1108, 1004, 972, 931, 927, 912, and 644
contain no date or time references. contain no date or time references.
21. Virtual Terminal 21. Virtual Terminal
21.1 Summary 21.1 Summary
The RFC's which were categorized into this group were Telnet and its The RFC's which were categorized into this group were Telnet and its
many extensions, as well as the Secure SHell (SSH) protocol. The X many extensions, as well as the Secure SHell (SSH) protocol. The X
window system was not considered since it is not an IETF protocol. window system was not considered since it is not an IETF protocol.
Official acknowledgement by the trustee's of the X window system was Official acknowledgement by the trustee's of the X window system was
given that they will examine the protocol. given that they will examine the protocol.
Unencrypted Telnet and TN3270 have both been found to be Year 2000 Unencrypted Telnet and TN3270 have both been found to be Year 2000
Compliant. The SSH protocols are also Year 2000 compliant. Compliant. The SSH protocols are also Year 2000 compliant.
21.2 Specifics 21.2 Specifics
RFC 1013 on the X Windows version 11 alpha protocol defines are 32 bit RFC 1013 on the X Windows version 11 alpha protocol defines are 32
unsigned integer timestamp in Section 4. bit unsigned integer timestamp in Section 4.
RFCs 2066, 1647, 1576, 1572, 1571, 1372, 1282, 1258, 1221, 1205, 1184, RFCs 2066, 1647, 1576, 1572, 1571, 1372, 1282, 1258, 1221, 1205, 1184,
1143, 1116, 1097, 1096, 1091, 1080, 1079, 1073, 1053, 1043, 1041, 1143, 1116, 1097, 1096, 1091, 1080, 1079, 1073, 1053, 1043, 1041,
1005, 946, 933, 930, 929, 907, 885, 884, 878, 861, 860, 859, 858, 857, 1005, 946, 933, 930, 929, 907, 885, 884, 878, 861, 860, 859, 858, 857,
856, 855, 854, 851, 818, 802, 782, 779, 764, 749, 748, 747, 746, 736, 856, 855, 854, 851, 818, 802, 782, 779, 764, 749, 748, 747, 746, 736,
735, 734, 732, 731, 729, 728, 727, 726, 721, 719, 718, 701, 698, 658, 735, 734, 732, 731, 729, 728, 727, 726, 721, 719, 718, 701, 698, 658,
657, 656, 655, 654, 653, 652, 651, 647, 636, 431, 399, 393, 386, 365, 657, 656, 655, 654, 653, 652, 651, 647, 636, 431, 399, 393, 386, 365,
352, 340, 339, 328, 311, 297, 231, and 215 contain no date or time 352, 340, 339, 328, 311, 297, 231, and 215 contain no date or time
references. references.
RFCs 703, 702, 688, 679, 669, 659, 600, 596, 595, 587, 563, 562, 560, RFCs 703, 702, 688, 679, 669, 659, 600, 596, 595, 587, 563, 562, 560,
559, 513, 495, 470, 466, 461, 447, 435, 377, 364, 318, 296, 216, 206, 559, 513, 495, 470, 466, 461, 447, 435, 377, 364, 318, 296, 216, 206,
205, 177, 158, 139, 137, 110, 97 were unavailable. 205, 177, 158, 139, 137, 110, 97 were unavailable.
22. Other 22. Other
22.1 Summary 22.1 Summary
This grouping was a hodge-podge of informational RFCs, April Fool's This grouping was a hodge-podge of informational RFCs, April Fool's
Jokes, IANA lists, and experimental RFCs. None were found to have any Jokes, IANA lists, and experimental RFCs. None were found to have
millennium issues. any millennium issues.
22.2 Specifics 22.2 Specifics
RFCs 2123, 2036, 2014, 2000, 1999, 1958, 1935, 1900, 1879, 1855, 1822, RFCs 2123, 2036, 2014, 2000, 1999, 1958, 1935, 1900, 1879, 1855, 1822,
1814, 1810, 1799, 1776, 1718, 1715, 1700, 1699, 1640, 1627, 1610, 1814, 1810, 1799, 1776, 1718, 1715, 1700, 1699, 1640, 1627, 1610,
1607, 1601, 1600, 1599, 1594, 1580, 1578, 1574, 1550, 1540, 1539, 1607, 1601, 1600, 1599, 1594, 1580, 1578, 1574, 1550, 1540, 1539,
1527, 1499, 1463, 1462, 1438, 1410, 1402, 1401, 1391, 1367, 1366, 1527, 1499, 1463, 1462, 1438, 1410, 1402, 1401, 1391, 1367, 1366,
1360, 1359, 1358, 1349, 1340, 1336, 1325, 1324, 1300, 1291, 1287, 1360, 1359, 1358, 1349, 1340, 1336, 1325, 1324, 1300, 1291, 1287,
1261, 1250, 1249, 1206, 1200, 1199, 1177, 1175, 1174, 1152, 1149, 1261, 1250, 1249, 1206, 1200, 1199, 1177, 1175, 1174, 1152, 1149,
1140, 1135, 1127, 1118, 1111, 1100, 1099, 1077, 1060, 1039, 1020, 1140, 1135, 1127, 1118, 1111, 1100, 1099, 1077, 1060, 1039, 1020,
1019, 999, 997, 992, 990, 980, 960, 945, 944, 943, 939, 909, 902, 900, 1019, 999, 997, 992, 990, 980, 960, 945, 944, 943, 939, 909, 902, 900,
899, 873, 869, 846, 845, 844, 843, 842, 840, 839, 838, 837, 836, 835, 899, 873, 869, 846, 845, 844, 843, 842, 840, 839, 838, 837, 836, 835,
834, 833, 832, 831, 820, 817, 800, 776, 774, 770, 766, 762, 758, 755, 834, 833, 832, 831, 820, 817, 800, 776, 774, 770, 766, 762, 758, 755,
750, 745, 717, 637, 603, 602, 590, 581, 578, 529, 527, 526, 523, 519, 750, 745, 717, 637, 603, 602, 590, 581, 578, 529, 527, 526, 523, 519,
518, 496, 491, 432, 404, 403, 401, 372, 363, 356, 345, 330, 329, 327, 518, 496, 491, 432, 404, 403, 401, 372, 363, 356, 345, 330, 329, 327,
317, 316, 313, 295, 282, 263, 242, 239, 234, 232, 225, 223, 213, 209, 317, 316, 313, 295, 282, 263, 242, 239, 234, 232, 225, 223, 213, 209,
204, 198, 195, 173, 170, 169, 167, 154, 149, 148, 147, 140, 138, 132, 204, 198, 195, 173, 170, 169, 167, 154, 149, 148, 147, 140, 138, 132,
131, 130, 129, 126, 121, 112, 109, 107, 100, 95, 90, 68, 64, 57, 52, 131, 130, 129, 126, 121, 112, 109, 107, 100, 95, 90, 68, 64, 57, 52,
51, 46, 43, 37, 27, 25, 21, 15, 10, and 9 were examined and none were 51, 46, 43, 37, 27, 25, 21, 15, 10, and 9 were examined and none were
found to have any date or time references, let alone millennium or Year found to have any date or time references, let alone millennium or Year
2000 issues. 2000 issues.
23. Security Considerations 23. Security Considerations
Although this document does consider the implications of various Although this document does consider the implications of various
security protocols, there is no need for additional security security protocols, there is no need for additional security
considerations. The effect of a potential year 2000 problem may cause considerations. The effect of a potential year 2000 problem may
some security problems, but those problems are more of specific cause some security problems, but those problems are more of specific
applications rather than protocol deficiencies introduced in this applications rather than protocol deficiencies introduced in this
document. document.
24. References 24. References
Because of the exhaustive nature of this investigation, the reader is Because of the exhaustive nature of this investigation, the reader is
referred to the list of published RFC's available from the IETF referred to the list of published RFC's available from the IETF
Secretariat or the RFC Editor, rather than republishing them here. Secretariat or the RFC Editor, rather than republishing them here.
25. Editors Address 25. Editors' Address
Philip J. Nesser II Philip J. Nesser II
Nesser & Nesser Consulting Nesser & Nesser Consulting
13501 100th Ave N.E. 13501 100th Ave N.E.
Suite 5202 Suite 5202
Kirkland, WA 98052 Kirkland, WA 98052
(425)481-4303 (voice)
(425)482-9721 (fax) Phone: 425-481-4303
pjnesser@nesser.com EMail: pjnesser@nesser.com
pjnesser@martigny.ai.mit.edu pjnesser@martigny.ai.mit.edu
Appendix A: List of RFC's for each Area Appendix A: List of RFC's for each Area
The following list contains the RFC's grouped by area that were The following list contains the RFC's grouped by area that were
searched for year 2000 problems. searched for year 2000 problems.
Each line contains three fields are separated by '::'. The first Each line contains three fields are separated by '::'. The first
filed is the RFC number, the second field is the type of RFC (S = filed is the RFC number, the second field is the type of RFC (S =
Standard, DS = Draft Standard, PS = Proposed Standard, E = Standard, DS = Draft Standard, PS = Proposed Standard, E =
Experimental, H = Historical, I = Informational, BC = Best Current Experimental, H = Historical, I = Informational, BC = Best Current
Practice, '' = No Type), and the third field is the Title. Practice, '' = No Type), and the third field is the Title.
A.1 Autoconfiguration A.1 Autoconfiguration
1971:: PS:: IPv6 Stateless Address Autoconfiguration 1971:: PS:: IPv6 Stateless Address Autoconfiguration
1970:: PS:: Neighbor Discovery for IP Version 6 (IPv6) 1970:: PS:: Neighbor Discovery for IP Version 6 (IPv6)
1542:: PS:: Clarifications and Extensions for the Bootstrap Protocol 1542:: PS:: Clarifications and Extensions for the Bootstrap Protocol
1541:: PS:: Dynamic Host Configuration Protocol 1541:: PS:: Dynamic Host Configuration Protocol
1534:: PS:: Interoperation Between DHCP and BOOTP 1534:: PS:: Interoperation Between DHCP and BOOTP
1533:: PS:: DHCP Options and BOOTP Vendor Extensions 1533:: PS:: DHCP Options and BOOTP Vendor Extensions
1532:: PS:: Clarifications and Extensions for the Bootstrap Protocol 1532:: PS:: Clarifications and Extensions for the Bootstrap Protocol
skipping to change at page 1, line 1444 skipping to change at page 1, line 1444
Games and Chat Games and Chat
1459:: E:: Internet Relay Chat Protocol 1459:: E:: Internet Relay Chat Protocol
====================================================================== ======================================================================
Information Services & File Transfer Information Services & File Transfer
2122:: PS:: VEMMI URL Specification 2122:: PS:: VEMMI URL Specification
2070:: PS:: Internationalization of the Hypertext Markup Language 2070:: PS:: Internationalization of the Hypertext Markup Language
2068:: PS:: Hypertext Transfer Protocol -- HTTP/1.1 2068:: PS:: Hypertext Transfer Protocol -- HTTP/1.1
2056:: PS:: Uniform Resource Locators for Z39.50 2056:: PS:: Uniform Resource Locators for Z39.50
2055:: I:: WebNFS Server Specification 2055:: I:: WebNFS Server Specification
2054:: I:: WebNFS Client Specification 2054:: I:: WebNFS Client Specification
2044:: I:: "UTF-8, a transformation format of Unicode and ISO 10646" 2044:: I:: UTF-8, a transformation format of Unicode and ISO 10646
2016:: E:: Uniform Resource Agents (URAs) 2016:: E:: Uniform Resource Agents (URAs)
1986:: E:: Experiments with a Simple File Transfer Protocol for 1986:: E:: Experiments with a Simple File Transfer Protocol for
Radio Links using Enhanced Trivial File Transfer Radio Links using Enhanced Trivial File Transfer
Protocol (ETFTP) Protocol (ETFTP)
1980:: I:: A Proposed Extension to HTML: Client-Side Image Maps 1980:: I:: A Proposed Extension to HTML: Client-Side Image Maps
1960:: PS:: A String Representation of LDAP Search Filters 1960:: PS:: A String Representation of LDAP Search Filters
1959:: PS:: An LDAP URL Format 1959:: PS:: An LDAP URL Format
1945:: I:: Hypertext Transfer Protocol -- HTTP/1.0 1945:: I:: Hypertext Transfer Protocol -- HTTP/1.0
1942:: E:: HTML Tables 1942:: E:: HTML Tables
1874:: E:: SGML Media Types 1874:: E:: SGML Media Types
1867:: E:: Form-based File Upload in HTML 1867:: E:: Form-based File Upload in HTML
1866:: PS:: Hypertext Markup Language - 2.0 1866:: PS:: Hypertext Markup Language - 2.0
1865:: I:: EDI Meets the Internet: Frequently Asked Questions 1865:: I:: EDI Meets the Internet: Frequently Asked Questions
about Electronic Data Interchange (EDI) on the Internet about Electronic Data Interchange (EDI) on the Internet
1862:: I:: "Report of the IAB Workshop on Internet Information 1862:: I:: Report of the IAB Workshop on Internet Information
Infrastructure, October 12-14, 1994" Infrastructure, October 12-14, 1994
1843:: I:: HZ - A Data Format for Exchanging Files of Arbitrarily 1843:: I:: HZ - A Data Format for Exchanging Files of Arbitrarily
Mixed Chinese and ASCII characters Mixed Chinese and ASCII characters
1842:: I:: ASCII Printable Characters-Based Chinese Character 1842:: I:: ASCII Printable Characters-Based Chinese Character
Encoding for Internet Messages Encoding for Internet Messages
1823:: I:: The LDAP Application Program Interface 1823:: I:: The LDAP Application Program Interface
1815:: I:: Character Sets ISO-10646 and ISO-10646-J-1 1815:: I:: Character Sets ISO-10646 and ISO-10646-J-1
1808:: PS:: Relative Uniform Resource Locators 1808:: PS:: Relative Uniform Resource Locators
1807:: I:: A Format for Bibliographic Records 1807:: I:: A Format for Bibliographic Records
1798:: PS:: Connection-less Lightweight Directory Access Protocol 1798:: PS:: Connection-less Lightweight Directory Access Protocol
1788:: E:: ICMP Domain Name Messages 1788:: E:: ICMP Domain Name Messages
skipping to change at page 1, line 1560 skipping to change at page 1, line 1561
697:: :: CWD command of FTP 697:: :: CWD command of FTP
691:: :: One more try on the FTP 691:: :: One more try on the FTP
683:: :: FTPSRV - Tenex extension for paged files 683:: :: FTPSRV - Tenex extension for paged files
662:: :: Performance improvement in ARPANET file transfers 662:: :: Performance improvement in ARPANET file transfers
from Multics from Multics
640:: :: Revised FTP reply codes 640:: :: Revised FTP reply codes
633:: :: IMP/TIP preventive maintenance schedule 633:: :: IMP/TIP preventive maintenance schedule
630:: :: FTP error code usage for more reliable mail service 630:: :: FTP error code usage for more reliable mail service
624:: :: Comments on the File Transfer Protocol 624:: :: Comments on the File Transfer Protocol
622:: :: Scheduling IMP/TIP down time 622:: :: Scheduling IMP/TIP down time
614:: :: "Response to RFC 607: ""Comments on the File Transfer 614:: :: Response to RFC 607: "Comments on the File Transfer
Protocol""" Protocol"
610:: :: Further datalanguage design concepts 610:: :: Further datalanguage design concepts
607:: :: Comments on the File Transfer Protocol 607:: :: Comments on the File Transfer Protocol
599:: :: Update on NETRJS 599:: :: Update on NETRJS
593:: :: Telnet and FTP implementation schedule change 593:: :: Telnet and FTP implementation schedule change
592:: :: Some thoughts on system design to facilitate resource 592:: :: Some thoughts on system design to facilitate resource
sharing sharing
589:: :: CCN NETRJS server messages to remote user 589:: :: CCN NETRJS server messages to remote user
573:: :: Data and file transfer: Some measurement results 573:: :: Data and file transfer: Some measurement results
571:: :: Tenex FTP problem 571:: :: Tenex FTP problem
570:: :: Experimental input mapping between NVT ASCII and UCSB 570:: :: Experimental input mapping between NVT ASCII and UCSB
On Line System On Line System
553:: :: Draft design for a text/graphics protocol 553:: :: Draft design for a text/graphics protocol
551:: :: "[Letter from Feinroth re: NYU, ANL, and LBL entering 551:: :: [Letter from Feinroth re: NYU, ANL, and LBL entering
the net, and FTP protocol]" the net, and FTP protocol]
549:: :: "Minutes of Network Graphics Group meeting, 15-17 549:: :: Minutes of Network Graphics Group meeting, 15-17
July 1973" July 1973
543:: :: Network journal submission and delivery 543:: :: Network journal submission and delivery
542:: :: File Transfer Protocol 542:: :: File Transfer Protocol
535:: :: Comments on File Access Protocol 535:: :: Comments on File Access Protocol
532:: :: UCSD-CC Server-FTP facility 532:: :: UCSD-CC Server-FTP facility
525:: :: MIT-MATHLAB meets UCSB-OLS -an example of resource sharing 525:: :: MIT-MATHLAB meets UCSB-OLS -an example of resource sharing
520:: :: Memo to FTP group: Proposal for File Access Protocol 520:: :: Memo to FTP group: Proposal for File Access Protocol
514:: :: Network make-work 514:: :: Network make-work
506:: :: FTP command naming problem 506:: :: FTP command naming problem
505:: :: Two solutions to a file transfer access problem 505:: :: Two solutions to a file transfer access problem
504:: :: Distributed resources workshop announcement 504:: :: Distributed resources workshop announcement
501:: :: "Un-muddling ""free file transfer""" 501:: :: Un-muddling "free file transfer"
499:: :: Harvard's network RJE 499:: :: Harvard's network RJE
493:: :: "E.W., Jr Graphics Protocol" 493:: :: E.W., Jr Graphics Protocol
490:: :: Surrogate RJS for UCLA-CCN 490:: :: Surrogate RJS for UCLA-CCN
487:: :: Free file transfer 487:: :: Free file transfer
486:: :: Data transfer revisited 486:: :: Data transfer revisited
485:: :: MIX and MIXAL at UCSB 485:: :: MIX and MIXAL at UCSB
480:: :: Host-dependent FTP parameters 480:: :: Host-dependent FTP parameters
479:: :: Use of FTP by the NIC Journal 479:: :: Use of FTP by the NIC Journal
478:: :: FTP server-server interaction - II 478:: :: FTP server-server interaction - II
477:: :: Remote Job Service at UCSB 477:: :: Remote Job Service at UCSB
472:: :: Illinois' reply to Maxwell's request for graphics 472:: :: Illinois' reply to Maxwell's request for graphics
information NIC 14925 information NIC 14925
skipping to change at page 1, line 1630 skipping to change at page 1, line 1631
409:: :: Tenex interface to UCSB's Simple-Minded File System 409:: :: Tenex interface to UCSB's Simple-Minded File System
407:: H:: Remote Job Entry Protocol 407:: H:: Remote Job Entry Protocol
406:: :: Scheduled IMP software releases 406:: :: Scheduled IMP software releases
396:: :: Network Graphics Working Group meeting - second iteration 396:: :: Network Graphics Working Group meeting - second iteration
387:: :: Some experiences in implementing Network Graphics 387:: :: Some experiences in implementing Network Graphics
Protocol Level 0 Protocol Level 0
385:: :: Comments on the File Transfer Protocol 385:: :: Comments on the File Transfer Protocol
382:: :: Mathematical software on the ARPA Network 382:: :: Mathematical software on the ARPA Network
374:: :: IMP system announcement 374:: :: IMP system announcement
373:: :: Arbitrary character sets 373:: :: Arbitrary character sets
368:: :: "Comments on ""Proposed Remote Job Entry Protocol""" 368:: :: Comments on "Proposed Remote Job Entry Protocol"
367:: :: Network host status 367:: :: Network host status
366:: :: Network host status 366:: :: Network host status
361:: :: Deamon processes on host 106 361:: :: Deamon processes on host 106
360:: :: Proposed Remote Job Entry Protocol 360:: :: Proposed Remote Job Entry Protocol
354:: :: File Transfer Protocol 354:: :: File Transfer Protocol
351:: :: Graphics information form for the ARPANET graphics 351:: :: Graphics information form for the ARPANET graphics
resources notebook resources notebook
342:: :: Network host status 342:: :: Network host status
338:: :: EBCDIC/ASCII mapping for network RJE 338:: :: EBCDIC/ASCII mapping for network RJE
336:: :: Level 0 Graphic Input Protocol 336:: :: Level 0 Graphic Input Protocol
skipping to change at page 1, line 1652 skipping to change at page 1, line 1653
332:: :: Network host status 332:: :: Network host status
325:: :: Network Remote Job Entry program - NETRJS 325:: :: Network Remote Job Entry program - NETRJS
324:: :: RJE Protocol meeting 324:: :: RJE Protocol meeting
314:: :: Network Graphics Working Group meeting 314:: :: Network Graphics Working Group meeting
310:: :: Another look at Data and File Transfer Protocols 310:: :: Another look at Data and File Transfer Protocols
309:: :: Data and File Transfer workshop announcement 309:: :: Data and File Transfer workshop announcement
307:: :: Using network Remote Job Entry 307:: :: Using network Remote Job Entry
306:: :: Network host status 306:: :: Network host status
299:: :: Information management system 299:: :: Information management system
298:: :: Network host status 298:: :: Network host status
294:: :: "On the use of ""set data type"" transaction in 294:: :: On the use of "set data type" transaction in
File Transfer Protocol" File Transfer Protocol
293:: :: Network host status 293:: :: Network host status
292:: :: "E.W., Jr Graphics Protocol: Level 0 only" 292:: :: E.W., Jr Graphics Protocol: Level 0 only
288:: :: Network host status 288:: :: Network host status
287:: :: Status of network hosts 287:: :: Status of network hosts
286:: :: Network library information system 286:: :: Network library information system
285:: :: Network graphics 285:: :: Network graphics
283:: :: NETRJT: Remote Job Service Protocol for TIPS 283:: :: NETRJT: Remote Job Service Protocol for TIPS
281:: :: Suggested addition to File Transfer Protocol 281:: :: Suggested addition to File Transfer Protocol
268:: :: Graphics facilities information 268:: :: Graphics facilities information
267:: :: Network host status 267:: :: Network host status
266:: :: Network host status 266:: :: Network host status
265:: :: "File Transfer Protocol" 265:: :: File Transfer Protocol
264:: :: "Data Transfer Protocol" 264:: :: Data Transfer Protocol
255:: :: Status of network hosts 255:: :: Status of network hosts
252:: :: Network host status 252:: :: Network host status
250:: :: Some thoughts on file transfer 250:: :: Some thoughts on file transfer
238:: :: Comments on DTP and FTP proposals 238:: :: Comments on DTP and FTP proposals
217:: :: "Specifications changes for OLS, RJE/RJOR, and SMFS" 217:: :: Specifications changes for OLS, RJE/RJOR, and SMFS
199:: :: Suggestions for a network data-tablet graphics protocol 199:: :: Suggestions for a network data-tablet graphics protocol
192:: :: Some factors which a Network Graphics Protocol must 192:: :: Some factors which a Network Graphics Protocol must
consider consider
191:: :: Graphics implementation and conceptualization at 191:: :: Graphics implementation and conceptualization at
Augmentation Research Center Augmentation Research Center
189:: :: Interim NETRJS specifications 189:: :: Interim NETRJS specifications
184:: :: Proposed graphic display modes 184:: :: Proposed graphic display modes
183:: :: EBCDIC codes and their mapping to ASCII 183:: :: EBCDIC codes and their mapping to ASCII
181:: :: Modifications to RFC 177 181:: :: Modifications to RFC 177
174:: :: UCLA - computer science graphics overview 174:: :: UCLA - computer science graphics overview
skipping to change at page 1, line 1699 skipping to change at page 1, line 1700
114:: :: File Transfer Protocol 114:: :: File Transfer Protocol
105:: :: Network specifications for Remote Job Entry and Remote 105:: :: Network specifications for Remote Job Entry and Remote
Job Output Retrieval at UCSB Job Output Retrieval at UCSB
98:: :: Logger Protocol proposal 98:: :: Logger Protocol proposal
94:: :: Some thoughts on network graphics 94:: :: Some thoughts on network graphics
88:: :: NETRJS: A third level protocol for Remote JobEntry 88:: :: NETRJS: A third level protocol for Remote JobEntry
86:: :: Proposal for a network standard format for a data stream 86:: :: Proposal for a network standard format for a data stream
to control graphics display to control graphics display
83:: :: Language-machine for data reconfiguration 83:: :: Language-machine for data reconfiguration
========== ============================================================ ========== ============================================================
Internet & Network Layer Internet & Network Layer
2126:: PS:: ISO Transport Service on top of TCP (ITOT) 2126:: PS:: ISO Transport Service on top of TCP (ITOT)
2125:: PS:: The PPP Bandwidth Allocation Protocol (BAP) The PPP 2125:: PS:: The PPP Bandwidth Allocation Protocol (BAP) The PPP
Bandwidth Allocation Control Protocol (BACP) Bandwidth Allocation Control Protocol (BACP)
2118:: I:: Microsoft Point-To-Point Compression (MPPC) Protocol 2118:: I:: Microsoft Point-To-Point Compression (MPPC) Protocol
2114:: I:: Data Link Switching Client Access Protocol 2114:: I:: Data Link Switching Client Access Protocol
2113:: PS:: IP Router Alert Option 2113:: PS:: IP Router Alert Option
2107:: I:: Ascend Tunnel Management Protocol - ATMP 2107:: I:: Ascend Tunnel Management Protocol - ATMP
2106:: I:: Data Link Switching Remote Access Protocol 2106:: I:: Data Link Switching Remote Access Protocol
2105:: I:: Cisco Systems' Tag Switching Architecture Overview 2105:: I:: Cisco Systems' Tag Switching Architecture Overview
2098:: I:: Toshiba's Router Architecture Extensions for ATM:Overview 2098:: I:: Toshiba's Router Architecture Extensions for ATM:Overview
skipping to change at page 1, line 1722 skipping to change at page 1, line 1723
2067:: DS:: IP over HIPPI 2067:: DS:: IP over HIPPI
2043:: PS:: The PPP SNA Control Protocol (SNACP) 2043:: PS:: The PPP SNA Control Protocol (SNACP)
2023:: PS:: IP Version 6 over PPP 2023:: PS:: IP Version 6 over PPP
2019:: PS:: Transmission of IPv6 Packets Over FDDI 2019:: PS:: Transmission of IPv6 Packets Over FDDI
2018:: PS:: TCP Selective Acknowledgment Options 2018:: PS:: TCP Selective Acknowledgment Options
2009:: E:: GPS-Based Addressing and Routing 2009:: E:: GPS-Based Addressing and Routing
2005:: PS:: Applicability Statement for IP Mobility Support 2005:: PS:: Applicability Statement for IP Mobility Support
2004:: PS:: Minimal Encapsulation within IP 2004:: PS:: Minimal Encapsulation within IP
2003:: PS:: IP Encapsulation within IP 2003:: PS:: IP Encapsulation within IP
2002:: PS:: IP Mobility Support 2002:: PS:: IP Mobility Support
2001:: PS:: "TCP Slow Start, Congestion Avoidance, Fast Retransmit, 2001:: PS:: TCP Slow Start, Congestion Avoidance, Fast Retransmit,
and Fast Recovery Algorithms" and Fast Recovery Algorithms
1994:: DS:: PPP Challenge Handshake Authentication Protocol (CHAP) 1994:: DS:: PPP Challenge Handshake Authentication Protocol (CHAP)
1993:: I:: PPP Gandalf FZA Compression Protocol 1993:: I:: PPP Gandalf FZA Compression Protocol
1990:: DS:: The PPP Multilink Protocol (MP) 1990:: DS:: The PPP Multilink Protocol (MP)
1989:: DS:: PPP Link Quality Monitoring 1989:: DS:: PPP Link Quality Monitoring
1981:: PS:: Path MTU Discovery for IP version 6 1981:: PS:: Path MTU Discovery for IP version 6
1979:: I:: PPP Deflate Protocol 1979:: I:: PPP Deflate Protocol
1978:: I:: PPP Predictor Compression Protocol 1978:: I:: PPP Predictor Compression Protocol
1977:: I:: PPP BSD Compression Protocol 1977:: I:: PPP BSD Compression Protocol
1976:: I:: PPP for Data Compression in Data Circuit-Terminating 1976:: I:: PPP for Data Compression in Data Circuit-Terminating
Equipment (DCE) Equipment (DCE)
skipping to change at page 1, line 1766 skipping to change at page 1, line 1768
1919:: I:: Classical versus Transparent IP Proxies 1919:: I:: Classical versus Transparent IP Proxies
1918:: BC:: Address Allocation for Private Internets 1918:: BC:: Address Allocation for Private Internets
1917:: BC:: An Appeal to the Internet Community to Return Unused 1917:: BC:: An Appeal to the Internet Community to Return Unused
IP Networks (Prefixes) to the IANA IP Networks (Prefixes) to the IANA
1916:: I:: Enterprise Renumbering 1916:: I:: Enterprise Renumbering
1915:: BC:: Variance for The PPP Connection Control Protocol and 1915:: BC:: Variance for The PPP Connection Control Protocol and
The PPP Encryption Control Protocol The PPP Encryption Control Protocol
1897:: E:: IPv6 Testing Address Allocation 1897:: E:: IPv6 Testing Address Allocation
1888:: E:: OSI NSAPs and IPv6 1888:: E:: OSI NSAPs and IPv6
1887:: I:: An Architecture for IPv6 Unicast Address Allocation 1887:: I:: An Architecture for IPv6 Unicast Address Allocation
1885:: PS:: Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) 1885:: PS:: Internet Control Message Protocol (ICMPv6) for the Internet
Protocol Version 6 (IPv6)
1884:: PS:: IP Version 6 Addressing Architecture 1884:: PS:: IP Version 6 Addressing Architecture
1883:: PS:: "Internet Protocol, Version 6 (IPv6) Specification" 1883:: PS:: Internet Protocol, Version 6 (IPv6) Specification
1881:: I:: IPv6 Address Allocation Management 1881:: I:: IPv6 Address Allocation Management
1878:: I:: Variable Length Subnet Table For IPv4 1878:: I:: Variable Length Subnet Table For IPv4
1877:: I:: PPP Internet Protocol Control Protocol Extensions for 1877:: I:: PPP Internet Protocol Control Protocol Extensions for
Name Server Addresses Name Server Addresses
1868:: E:: ARP Extension - UNARP 1868:: E:: ARP Extension - UNARP
1860:: I:: Variable Length Subnet Table For IPv4 1860:: I:: Variable Length Subnet Table For IPv4
1859:: I:: ISO Transport Class 2 Non-use of Explicit Flow Control 1859:: I:: ISO Transport Class 2 Non-use of Explicit Flow Control
over TCP RFC1006 extension over TCP RFC1006 extension
1853:: I:: IP in IP Tunneling 1853:: I:: IP in IP Tunneling
1841:: I:: PPP Network Control Protocol for LAN Extension 1841:: I:: PPP Network Control Protocol for LAN Extension
1833:: PS:: Binding Protocols for ONC RPC Version 2 1833:: PS:: Binding Protocols for ONC RPC Version 2
1832:: PS:: XDR 1832:: PS:: XDR
1831:: PS:: RPC 1831:: PS:: RPC
1809:: I:: Using the Flow Label Field in IPv6 1809:: I:: Using the Flow Label Field in IPv6
1795:: I:: "Data Link Switching 1795:: I:: Data Link Switching
1791:: E:: TCP And UDP Over IPX Networks With Fixed Path MTU 1791:: E:: TCP And UDP Over IPX Networks With Fixed Path MTU
1770:: I:: IPv4 Option for Sender Directed Multi-Destination Delivery 1770:: I:: IPv4 Option for Sender Directed Multi-Destination Delivery
1764:: PS:: The PPP XNS IDP Control Protocol (XNSCP) 1764:: PS:: The PPP XNS IDP Control Protocol (XNSCP)
1763:: PS:: The PPP Banyan Vines Control Protocol (BVCP) 1763:: PS:: The PPP Banyan Vines Control Protocol (BVCP)
1762:: DS:: The PPP DECnet Phase IV Control Protocol (DNCP) 1762:: DS:: The PPP DECnet Phase IV Control Protocol (DNCP)
1761:: I:: Snoop Version 2 Packet Capture File Format 1761:: I:: Snoop Version 2 Packet Capture File Format
1756:: E:: REMOTE WRITE PROTOCOL - VERSION 1.0 1756:: E:: REMOTE WRITE PROTOCOL - VERSION 1.0
1755:: PS:: ATM Signaling Support for IP over ATM 1755:: PS:: ATM Signaling Support for IP over ATM
1754:: I:: IP over ATM Working Group's Recommendations for the 1754:: I:: IP over ATM Working Group's Recommendations for the
ATM Forum's Multiprotocol BOF Version 1 ATM Forum's Multiprotocol BOF Version 1
skipping to change at page 1, line 1889 skipping to change at page 1, line 1892
1378:: PS:: The PPP AppleTalk Control Protocol (ATCP) 1378:: PS:: The PPP AppleTalk Control Protocol (ATCP)
1377:: PS:: The PPP OSI Network Layer Control Protocol (OSINLCP) 1377:: PS:: The PPP OSI Network Layer Control Protocol (OSINLCP)
1376:: PS:: The PPP DECnet Phase IV Control Protocol (DNCP) 1376:: PS:: The PPP DECnet Phase IV Control Protocol (DNCP)
1375:: I:: Suggestion for New Classes of IP Addresses 1375:: I:: Suggestion for New Classes of IP Addresses
1374:: PS:: IP and ARP on HIPPI 1374:: PS:: IP and ARP on HIPPI
1365:: I:: An IP Address Extension Proposal 1365:: I:: An IP Address Extension Proposal
1363:: E:: A Proposed Flow Specification 1363:: E:: A Proposed Flow Specification
1362:: I:: Novell IPX Over Various WAN Media (IPXWAN) 1362:: I:: Novell IPX Over Various WAN Media (IPXWAN)
1356:: PS:: Multiprotocol Interconnect on X.25 and ISDN in the 1356:: PS:: Multiprotocol Interconnect on X.25 and ISDN in the
Packet Mode Packet Mode
1347:: I:: "TCP and UDP with Bigger Addresses (TUBA), A Simple 1347:: I:: TCP and UDP with Bigger Addresses (TUBA), A Simple
Proposal for Internet Addressing and Routing" Proposal for Internet Addressing and Routing
1337:: I:: TIME-WAIT Assassination Hazards in TCP 1337:: I:: TIME-WAIT Assassination Hazards in TCP
1335:: :: A Two-Tier Address Structure for the Internet 1335:: :: A Two-Tier Address Structure for the Internet
1334:: PS:: PPP Authentication Protocols 1334:: PS:: PPP Authentication Protocols
1333:: PS:: PPP Link Quality Monitoring 1333:: PS:: PPP Link Quality Monitoring
1332:: PS:: The PPP Internet Protocol Control Protocol (IPCP) 1332:: PS:: The PPP Internet Protocol Control Protocol (IPCP)
1331:: PS:: The Point-to-Point Protocol (PPP) for the Transmission 1331:: PS:: The Point-to-Point Protocol (PPP) for the Transmission
of Multi-protocol Datagrams over Point-to-Point Links of Multi-protocol Datagrams over Point-to-Point Links
1329:: I:: Thoughts on Address Resolution for Dual MAC FDDI Networks 1329:: I:: Thoughts on Address Resolution for Dual MAC FDDI Networks
1326:: I:: Mutual Encapsulation Considered Dangerous 1326:: I:: Mutual Encapsulation Considered Dangerous
1323:: PS:: TCP Extensions for High Performance 1323:: PS:: TCP Extensions for High Performance
skipping to change at page 1, line 1919 skipping to change at page 1, line 1922
1263:: I:: TCP Extensions Considered Harmful 1263:: I:: TCP Extensions Considered Harmful
1256:: PS:: ICMP Router Discovery Messages 1256:: PS:: ICMP Router Discovery Messages
1240:: PS:: OSI Connectionless Transport Services on top of UDP 1240:: PS:: OSI Connectionless Transport Services on top of UDP
1237:: PS:: Guidelines for OSI NSAP Allocation in the Internet 1237:: PS:: Guidelines for OSI NSAP Allocation in the Internet
1236:: :: IP to X.121 Address Mapping for DDN 1236:: :: IP to X.121 Address Mapping for DDN
1234:: PS:: Tunneling IPX Traffic through IP Networks 1234:: PS:: Tunneling IPX Traffic through IP Networks
1226:: E:: Internet Protocol Encapsulation of AX.25 Frames 1226:: E:: Internet Protocol Encapsulation of AX.25 Frames
1223:: :: OSI CLNS and LLC1 Protocols on Network Systems HYPERchannel 1223:: :: OSI CLNS and LLC1 Protocols on Network Systems HYPERchannel
1220:: PS:: Point-to-Point Protocol Extensions for Bridging 1220:: PS:: Point-to-Point Protocol Extensions for Bridging
1219:: :: On the Assignment of Subnet Numbers 1219:: :: On the Assignment of Subnet Numbers
1210:: :: "Network and Infrastructure User Requirements for 1210:: :: Network and Infrastructure User Requirements for
Transatlantic Research Collaboration - Brussels, Transatlantic Research Collaboration - Brussels,
July 16-18, and Washington July 24-25, 1990" July 16-18, and Washington July 24-25, 1990
1209:: DS:: The Transmission of IP Datagrams over the SMDS Service 1209:: DS:: The Transmission of IP Datagrams over the SMDS Service
1201:: H:: Transmitting IP Traffic over ARCNET Networks 1201:: H:: Transmitting IP Traffic over ARCNET Networks
1191:: DS:: Path MTU Discovery 1191:: DS:: Path MTU Discovery
1188:: DS:: A Proposed Standard for the Transmission of IP Datagrams 1188:: DS:: A Proposed Standard for the Transmission of IP Datagrams
over FDDI Networks over FDDI Networks
1185:: E:: TCP Extension for High-Speed Paths 1185:: E:: TCP Extension for High-Speed Paths
1172:: PS:: The Point-to-Point Protocol (PPP) Initial Configuration 1172:: PS:: The Point-to-Point Protocol (PPP) Initial Configuration
Options Options
1171:: DS:: The Point-to-Point Protocol for the Transmission of 1171:: DS:: The Point-to-Point Protocol for the Transmission of
Multi-Protocol Datagrams Over Point-to-Point Links Multi-Protocol Datagrams Over Point-to-Point Links
skipping to change at page 1, line 1987 skipping to change at page 1, line 1990
1027:: :: Using ARP to implement transparent subnet gateways 1027:: :: Using ARP to implement transparent subnet gateways
1025:: :: TCP and IP bake off 1025:: :: TCP and IP bake off
1016:: :: Something a host could do with source quench 1016:: :: Something a host could do with source quench
1008:: :: Implementation guide for the ISO Transport Protocol 1008:: :: Implementation guide for the ISO Transport Protocol
1007:: :: Military supplement to the ISO Transport Protocol 1007:: :: Military supplement to the ISO Transport Protocol
1006:: S:: ISO transport services on top of the TCP 1006:: S:: ISO transport services on top of the TCP
1002:: S:: Protocol standard for a NetBIOS service on a TCP/UDP 1002:: S:: Protocol standard for a NetBIOS service on a TCP/UDP
transport transport
1001:: S:: Protocol standard for a NetBIOS service on a TCP/UDP 1001:: S:: Protocol standard for a NetBIOS service on a TCP/UDP
transport transport
994:: :: "Final text of DIS 8473,Protocol for Providing the 994:: :: Final text of DIS 8473,Protocol for Providing the
Connectionless-mode Network Service" Connectionless-mode Network Service
986:: :: Guidelines for the use of Internet-IP addressesin the 986:: :: Guidelines for the use of Internet-IP addressesin the
ISO Connectionless-Mode Network Protocol [Working draft] ISO Connectionless-Mode Network Protocol [Working draft]
983:: :: ISO transport arrives on top of the TCP 983:: :: ISO transport arrives on top of the TCP
982:: :: Guidelines for the specification of the structure of the 982:: :: Guidelines for the specification of the structure of the
Domain Specific Part DSP of the ISO standard NSAP address Domain Specific Part DSP of the ISO standard NSAP address
970:: :: On packet switches with infinite storage 970:: :: On packet switches with infinite storage
964:: :: Some problems with the specification of the Military 964:: :: Some problems with the specification of the Military
Standard Transmission Control Protocol Standard Transmission Control Protocol
963:: :: Some problems with the specification of the Military 963:: :: Some problems with the specification of the Military
Standard Internet Protocol Standard Internet Protocol
skipping to change at page 1, line 2013 skipping to change at page 1, line 2016
IEEE 802.3 networks IEEE 802.3 networks
942:: :: Transport protocols for Department of Defense data 942:: :: Transport protocols for Department of Defense data
networks networks
941:: :: Addendum to the networkservice definition covering 941:: :: Addendum to the networkservice definition covering
network layer addressing network layer addressing
940:: :: Toward an Internet standard scheme for subnetting 940:: :: Toward an Internet standard scheme for subnetting
936:: :: Another Internet subnet addressing scheme 936:: :: Another Internet subnet addressing scheme
935:: :: Reliable link layer protocols 935:: :: Reliable link layer protocols
932:: :: Subnetwork addressing scheme 932:: :: Subnetwork addressing scheme
926:: :: Protocol for providing the connectionless mode network 926:: :: Protocol for providing the connectionless mode network
services services
925:: :: Multi-LAN address resolution 925:: :: Multi-LAN address resolution
924:: :: Official ARPA-Internet protocols for connecting 924:: :: Official ARPA-Internet protocols for connecting
personal computers to the Internet personal computers to the Internet
922:: S:: Broadcasting Internet datagrams in the presence of subnets 922:: S:: Broadcasting Internet datagrams in the presence of subnets
919:: S:: Broadcasting Internet datagrams 919:: S:: Broadcasting Internet datagrams
917:: :: Internet subnets 917:: :: Internet subnets
914:: H:: Thinwire protocol for connecting personal computers to 914:: H:: Thinwire protocol for connecting personal computers to
the Internet the Internet
905:: :: ISO Transport Protocol specification ISO DP 8073 905:: :: ISO Transport Protocol specification ISO DP 8073
903:: S:: Reverse Address Resolution Protocol 903:: S:: Reverse Address Resolution Protocol
skipping to change at page 1, line 2039 skipping to change at page 1, line 2042
893:: :: Trailer encapsulations 893:: :: Trailer encapsulations
892:: :: ISO Transport Protocol specification [Draft] 892:: :: ISO Transport Protocol specification [Draft]
891:: S:: DCN local-network protocols 891:: S:: DCN local-network protocols
889:: :: Internet delay experiments 889:: :: Internet delay experiments
879:: :: TCP maximum segment size and related topics 879:: :: TCP maximum segment size and related topics
877:: S:: Standard for the transmission of IP datagrams over 877:: S:: Standard for the transmission of IP datagrams over
public data networks public data networks
874:: :: Critique of X.25 874:: :: Critique of X.25
872:: :: TCP-on-a-LAN 872:: :: TCP-on-a-LAN
871:: :: Perspective on the ARPANET reference model 871:: :: Perspective on the ARPANET reference model
848:: :: "Who provides the ""little"" TCP services?" 848:: :: Who provides the "little" TCP services?
829:: :: Packet satellite technology reference sources 829:: :: Packet satellite technology reference sources
826:: S:: Ethernet Address Resolution Protocol 826:: S:: Ethernet Address Resolution Protocol
824:: :: CRONUS Virtual Local Network 824:: :: CRONUS Virtual Local Network
815:: :: IP datagram reassembly algorithms 815:: :: IP datagram reassembly algorithms
814:: :: "Name, addresses, ports, and routes" 814:: :: Name, addresses, ports, and routes
813:: :: Window and acknowlegement strategy in TCP 813:: :: Window and acknowlegement strategy in TCP
801:: :: NCP/TCP transition plan 801:: :: NCP/TCP transition plan
793:: S:: Transmission Control Protocol 793:: S:: Transmission Control Protocol
792:: S:: Internet Control Message Protocol 792:: S:: Internet Control Message Protocol
791:: S:: Internet Protocol 791:: S:: Internet Protocol
789:: :: Vulnerabilities of network control protocols 789:: :: Vulnerabilities of network control protocols
787:: :: Connectionless data transmission survey/tutorial 787:: :: Connectionless data transmission survey/tutorial
781:: :: Specification of the Internet Protocol IP timestamp option 781:: :: Specification of the Internet Protocol IP timestamp option
777:: :: Internet Control Message Protocol 777:: :: Internet Control Message Protocol
768:: S:: User Datagram Protocol 768:: S:: User Datagram Protocol
skipping to change at page 1, line 2107 skipping to change at page 1, line 2110
398:: :: ICP sockets 398:: :: ICP sockets
395:: :: Switch settings on IMPs and TIPs 395:: :: Switch settings on IMPs and TIPs
394:: :: Two proposed changes to the IMP-Host Protocol 394:: :: Two proposed changes to the IMP-Host Protocol
359:: :: Status of the release of the new IMP System 359:: :: Status of the release of the new IMP System
357:: :: Echoing strategy for satellite links 357:: :: Echoing strategy for satellite links
348:: :: Discard process 348:: :: Discard process
347:: :: Echo process 347:: :: Echo process
346:: :: Satellite considerations 346:: :: Satellite considerations
343:: :: IMP System change notification 343:: :: IMP System change notification
312:: :: Proposed change in IMP-to-Host Protocol 312:: :: Proposed change in IMP-to-Host Protocol
301:: :: "BBN IMP #5 and NCC schedule March 4, 1971" 301:: :: BBN IMP #5 and NCC schedule March 4, 1971
300:: :: ARPA Network mailing lists 300:: :: ARPA Network mailing lists
271:: :: IMP System change notifications 271:: :: IMP System change notifications
241:: :: Connecting computers to MLC ports 241:: :: Connecting computers to MLC ports
210:: :: Improvement of flow control 210:: :: Improvement of flow control
203:: :: Achieving reliable communication 203:: :: Achieving reliable communication
202:: :: Possible deadlock in ICP 202:: :: Possible deadlock in ICP
197:: :: Initial Connection Protocol - Reviewed 197:: :: Initial Connection Protocol - Reviewed
190:: :: DEC PDP-10-IMLAC communications system 190:: :: DEC PDP-10-IMLAC communications system
178:: :: Network graphic attention handling 178:: :: Network graphic attention handling
176:: :: "Comments on ""Byte size for connections""" 176:: :: Comments on "Byte size for connections"
175:: :: "Comments on ""Socket conventions reconsidered""" 175:: :: Comments on "Socket conventions reconsidered"
166:: :: Data Reconfiguration Service 166:: :: Data Reconfiguration Service
165:: :: Proffered official Initial Connection Protocol 165:: :: Proffered official Initial Connection Protocol
161:: :: Solution to the race condition in the ICP 161:: :: Solution to the race condition in the ICP
151:: :: "Comments on a proffered official ICP 151:: :: Comments on a proffered official ICP
150:: :: Use of IPC facilities 150:: :: Use of IPC facilities
146:: :: Views on issues relevant to data sharing on computer 146:: :: Views on issues relevant to data sharing on computer
networks networks
145:: :: Initial Connection Protocol control commands 145:: :: Initial Connection Protocol control commands
143:: :: Regarding proffered official ICP 143:: :: Regarding proffered official ICP
142:: :: Time-out mechanism in the Host-Host Protocol 142:: :: Time-out mechanism in the Host-Host Protocol
128:: :: Bytes 128:: :: Bytes
127:: :: Comments on RFC 123 127:: :: Comments on RFC 123
123:: :: Proffered official ICP 123:: :: Proffered official ICP
122:: :: Network specifications for UCSB's Simple-Minded File 122:: :: Network specifications for UCSB's Simple-Minded File
skipping to change at page 1, line 2163 skipping to change at page 1, line 2166
22:: :: Host-host control message formats 22:: :: Host-host control message formats
20:: :: ASCII format for network interchange 20:: :: ASCII format for network interchange
19:: :: Two protocol suggestions to reduce congestion at 19:: :: Two protocol suggestions to reduce congestion at
swap bound nodes swap bound nodes
17:: :: Some questions re 17:: :: Some questions re
12:: :: IMP-Host interface flow diagrams 12:: :: IMP-Host interface flow diagrams
===================================================================== =====================================================================
Mail Mail
2112:: PS:: The MIME Multipart/Related Content-type 2112:: PS:: The MIME Multipart/Related Content-type
2111:: PS:: Content-ID and Message-ID Uniform Resource Locators 2111:: PS:: Content-ID and Message-ID Uniform Resource Locators
2110:: PS:: "MIME E-mail Encapsulation of Aggregate Documents, such 2110:: PS:: MIME E-mail Encapsulation of Aggregate Documents, such
as HTML (MHTML)" as HTML (MHTML)
2109:: PS:: HTTP State Management Mechanism 2109:: PS:: HTTP State Management Mechanism
2095:: PS:: IMAP/POP AUTHorize Extension for Simple Challenge/Response 2095:: PS:: IMAP/POP AUTHorize Extension for Simple Challenge/Response
2088:: PS:: IMAP4 non-synchroniziong literals 2088:: PS:: IMAP4 non-synchroniziong literals
2087:: PS:: IMAP4 QUOTA extension 2087:: PS:: IMAP4 QUOTA extension
2086:: PS:: IMAP4 ACL extension 2086:: PS:: IMAP4 ACL extension
2077:: PS:: The Model Primary Content Type for Multipurpose 2077:: PS:: The Model Primary Content Type for Multipurpose
Internet Mail Extensions Internet Mail Extensions
2076:: I:: Common Internet Message Headers 2076:: I:: Common Internet Message Headers
2062:: I:: Internet Message Access Protocol - Obsolete Syntax 2062:: I:: Internet Message Access Protocol - Obsolete Syntax
2061:: I:: IMAP4 COMPATIBILITY WITH IMAP2BIS 2061:: I:: IMAP4 COMPATIBILITY WITH IMAP2BIS
skipping to change at page 1, line 2335 skipping to change at page 1, line 2338
786:: :: Mail Transfer Protocol 786:: :: Mail Transfer Protocol
785:: :: Mail Transfer Protocol 785:: :: Mail Transfer Protocol
784:: :: Mail Transfer Protocol 784:: :: Mail Transfer Protocol
780:: :: Mail Transfer Protocol 780:: :: Mail Transfer Protocol
773:: :: Comments on NCP/TCP mail service transition strategy 773:: :: Comments on NCP/TCP mail service transition strategy
772:: :: Mail Transfer Protocol 772:: :: Mail Transfer Protocol
771:: :: Mail transition plan 771:: :: Mail transition plan
767:: :: Structured format for transmission of multi-media 767:: :: Structured format for transmission of multi-media
documents documents
763:: :: Role mailboxes 763:: :: Role mailboxes
757:: :: "Suggested solution to the naming, addressing, and delivery problem for ARPANET message systems" 757:: :: Suggested solution to the naming, addressing, and
delivery problem for ARPANET message systems
754:: :: Out-of-net host addresses for mail 754:: :: Out-of-net host addresses for mail
753:: :: Internet Message Protocol 753:: :: Internet Message Protocol
744:: :: MARS - a Message Archiving and Retrieval Service 744:: :: MARS - a Message Archiving and Retrieval Service
733:: :: Standard for theformat of ARPA network text messages 733:: :: Standard for theformat of ARPA network text messages
724:: :: Proposed official standard for the format of ARPA 724:: :: Proposed official standard for the format of ARPA
Network messages Network messages
720:: :: Address specification syntax for network mail 720:: :: Address specification syntax for network mail
714:: :: Host-Host Protocol for an ARPANET-type network 714:: :: Host-Host Protocol for an ARPANET-type network
713:: :: MSDTP-Message Services Data Transmission Protocol 713:: :: MSDTP-Message Services Data Transmission Protocol
706:: :: On the junk mail problem 706:: :: On the junk mail problem
skipping to change at page 1, line 2370 skipping to change at page 1, line 2374
458:: :: Mail retrieval via FTP 458:: :: Mail retrieval via FTP
453:: :: Meeting announcement to discuss a network mail system 453:: :: Meeting announcement to discuss a network mail system
333:: :: Proposed experiment with a Message Switching Protocol 333:: :: Proposed experiment with a Message Switching Protocol
278:: :: Revision of theMail Box Protocol 278:: :: Revision of theMail Box Protocol
224:: :: Comments on Mailbox Protocol 224:: :: Comments on Mailbox Protocol
221:: :: Mail Box Protocol 221:: :: Mail Box Protocol
196:: :: Mail Box Protocol 196:: :: Mail Box Protocol
58:: :: Logical message synchronization 58:: :: Logical message synchronization
42:: :: Message data types 42:: :: Message data types
===================================================================== =====================================================================
NTP NTP
2030:: I:: "Simple Network Time Protocol (SNTP) Version 4 for IPv4, 2030:: I:: Simple Network Time Protocol (SNTP) Version 4 for IPv4,
IPv6 and OSI" IPv6 and OSI
1769:: I:: Simple Network Time Protocol (SNTP) 1769:: I:: Simple Network Time Protocol (SNTP)
1708:: I:: NTP PICS PROFORMA For the Network Time Protocol Version 3 1708:: I:: NTP PICS PROFORMA For the Network Time Protocol Version 3
1589:: I:: A Kernel Model for Precision Timekeeping 1589:: I:: A Kernel Model for Precision Timekeeping
1361:: I:: Simple Network Time Protocol (SNTP) 1361:: I:: Simple Network Time Protocol (SNTP)
1305:: PS:: Network Time Protocol (v3) 1305:: PS:: Network Time Protocol (v3)
1165:: E:: Network Time Protocol (NTP) over the OSI Remote Operations 1165:: E:: Network Time Protocol (NTP) over the OSI Remote Operations
Service Service
1129:: :: Internet time synchronization 1129:: :: Internet time synchronization
1128:: :: Measured performance of the Network Time Protocol in the 1128:: :: Measured performance of the Network Time Protocol in the
Internet system Internet system
skipping to change at page 1, line 2632 skipping to change at page 1, line 2637
1381:: PS:: SNMP MIB Extension for X.25 LAPB 1381:: PS:: SNMP MIB Extension for X.25 LAPB
1369:: I:: Implementation Notes and Experience for The Internet 1369:: I:: Implementation Notes and Experience for The Internet
Ethernet MIB Ethernet MIB
1368:: PS:: Definitions of Managed Objects for IEEE 802.3 Repeater 1368:: PS:: Definitions of Managed Objects for IEEE 802.3 Repeater
Devices Devices
1354:: PS:: IP Forwarding Table MIB 1354:: PS:: IP Forwarding Table MIB
1353:: H:: Definitions of Managed Objects for Administration of 1353:: H:: Definitions of Managed Objects for Administration of
SNMP Parties SNMP Parties
1352:: H:: SNMP Security Protocols 1352:: H:: SNMP Security Protocols
1351:: H:: SNMP Administrative Model 1351:: H:: SNMP Administrative Model
1346:: I:: "Resource Allocation, Control, and Accounting for the 1346:: I:: Resource Allocation, Control, and Accounting for the
Use of Network Resources" Use of Network Resources
1318:: PS:: Definitions of Managed Objects for Parallel-printer-like 1318:: PS:: Definitions of Managed Objects for Parallel-printer-like
Hardware Devices Hardware Devices
1317:: PS:: Definitions of Managed Objects for RS-232-like 1317:: PS:: Definitions of Managed Objects for RS-232-like
Hardware Devices Hardware Devices
1316:: PS:: Definitions of Managed Objects for Character Stream 1316:: PS:: Definitions of Managed Objects for Character Stream
Devices Devices
1315:: PS:: Management Information Base for Frame Relay DTEs 1315:: PS:: Management Information Base for Frame Relay DTEs
1304:: PS:: Definitions of Managed Objects for the SIP Interface Type 1304:: PS:: Definitions of Managed Objects for the SIP Interface Type
1303:: I:: A Convention for Describing SNMP-based Agents 1303:: I:: A Convention for Describing SNMP-based Agents
1298:: I:: SNMP over IPX 1298:: I:: SNMP over IPX
1289:: PS:: DECnet Phase IV MIB Extensions 1289:: PS:: DECnet Phase IV MIB Extensions
1286:: PS:: Definitions of Managed Objects for Bridges 1286:: PS:: Definitions of Managed Objects for Bridges
1285:: PS:: FDDI Management Information Base 1285:: PS:: FDDI Management Information Base
1284:: PS:: Definitions of Managed Objects for the Ethernet-like 1284:: PS:: Definitions of Managed Objects for the Ethernet-like
Interface Types Interface Types
1283:: E:: SNMP over OSI 1283:: E:: SNMP over OSI
1273:: I:: "A Measurement Study of Changes in Service-Level 1273:: I:: A Measurement Study of Changes in Service-Level
Reachability in the Global TCP/IP Internet Reachability in the Global TCP/IP Internet
1272:: I:: Internet Accounting 1272:: I:: Internet Accounting
1271:: PS:: Remote Network Monitoring Management Information Base 1271:: PS:: Remote Network Monitoring Management Information Base
1270:: I:: SNMP Communications Services 1270:: I:: SNMP Communications Services
1269:: PS:: Definitions of Managed Objects for the Border Gateway 1269:: PS:: Definitions of Managed Objects for the Border Gateway
Protocol (Version 3) Protocol (Version 3)
1262:: :: Guidelines for Internet Measurement Activities 1262:: :: Guidelines for Internet Measurement Activities
1253:: PS:: OSPF Version 2 Management Information Base 1253:: PS:: OSPF Version 2 Management Information Base
1252:: PS:: OSPF Version 2 Management Information Base 1252:: PS:: OSPF Version 2 Management Information Base
1248:: PS:: OSPF Version 2 Management Information Base 1248:: PS:: OSPF Version 2 Management Information Base
skipping to change at page 1, line 2688 skipping to change at page 1, line 2693
1215:: I:: A Convention for Defining Traps for use with the SNMP 1215:: I:: A Convention for Defining Traps for use with the SNMP
1214:: H:: OSI Internet Management 1214:: H:: OSI Internet Management
1213:: S:: Management Information Base for Network Management of 1213:: S:: Management Information Base for Network Management of
TCP/IP-based internets TCP/IP-based internets
1212:: S:: Concise MIB Definitions 1212:: S:: Concise MIB Definitions
1189:: H:: The Common Management Information Services and Protocols 1189:: H:: The Common Management Information Services and Protocols
for the Internet for the Internet
1187:: E:: Bulk Table Retrieval with the SNMP 1187:: E:: Bulk Table Retrieval with the SNMP
1161:: E:: SNMP over OSI 1161:: E:: SNMP over OSI
1158:: PS:: Management Information Base for Network Management of 1158:: PS:: Management Information Base for Network Management of
TCP/IP-based internets TCP/IP-based internets
1157:: S:: A Simple Network Management Protocol (SNMP) 1157:: S:: A Simple Network Management Protocol (SNMP)
1155:: S:: Structure and Identification of Management Information 1155:: S:: Structure and Identification of Management Information
for TCP/IP-based Internets for TCP/IP-based Internets
1109:: :: Report of the second Ad Hoc Network Management Review 1109:: :: Report of the second Ad Hoc Network Management Review
Group Group
1098:: :: Simple Network Management Protocol SNMP 1098:: :: Simple Network Management Protocol SNMP
1095:: DS:: Common Management Information Services and Protocol 1095:: DS:: Common Management Information Services and Protocol
over TCP/IP CMOT over TCP/IP CMOT
1089:: :: SNMP over Ethernet 1089:: :: SNMP over Ethernet
1067:: :: Simple Network Management Protocol 1067:: :: Simple Network Management Protocol
skipping to change at page 1, line 2743 skipping to change at page 1, line 2748
509:: :: Traffic statistics April 1973 509:: :: Traffic statistics April 1973
500:: :: Integration of data management systems on a computer 500:: :: Integration of data management systems on a computer
network network
482:: :: Traffic statistics February 1973 482:: :: Traffic statistics February 1973
455:: :: Traffic statistics January 1973 455:: :: Traffic statistics January 1973
443:: :: Traffic statistics December 1972 443:: :: Traffic statistics December 1972
423:: :: UCLA Campus Computing Network liaison staff for ARPANET 423:: :: UCLA Campus Computing Network liaison staff for ARPANET
422:: :: Traffic statistics November 1972 422:: :: Traffic statistics November 1972
421:: :: Software consulting service for network users 421:: :: Software consulting service for network users
416:: :: ARC system will be unavailable for use during 416:: :: ARC system will be unavailable for use during
Thanksgivingweek  Thanksgivingweek
415:: :: Tenex bandwidth 415:: :: Tenex bandwidth
413:: :: Traffic statistics October 1972 413:: :: Traffic statistics October 1972
400:: :: Traffic statistics September 1972 400:: :: Traffic statistics September 1972
392:: :: Measurement of host costs for transmitting network data 392:: :: Measurement of host costs for transmitting network data
391:: :: Traffic statistics August 1972 391:: :: Traffic statistics August 1972
389:: :: UCLA Campus Computing Network liaison staff for ARPA 389:: :: UCLA Campus Computing Network liaison staff for ARPA
Network Network
388:: :: NCP statistics 388:: :: NCP statistics
384:: :: Official site idents for organizations in the ARPA 384:: :: Official site idents for organizations in the ARPA
Network Network
381:: :: Three aids to improved network operation 381:: :: Three aids to improved network operation
378:: :: Traffic statistics July 1972 378:: :: Traffic statistics July 1972
369:: :: "Evaluation of ARPANET services January-March, 1972" 369:: :: Evaluation of ARPANET services January-March, 1972
362:: :: Network host status 362:: :: Network host status
353:: :: Network host status 353:: :: Network host status
344:: :: Network host status 344:: :: Network host status
326:: :: Network host status 326:: :: Network host status
323:: :: Formation of Network Measurement Group NMG 323:: :: Formation of Network Measurement Group NMG
308:: :: ARPANET host availability data 308:: :: ARPANET host availability data
304:: :: Data management system proposal for the ARPA network 304:: :: Data management system proposal for the ARPA network
302:: :: Exercising the ARPANET 302:: :: Exercising the ARPANET
274:: :: Establishing a local guide for network usage 274:: :: Establishing a local guide for network usage
227:: :: Data transfer rates Rand/UCLA 227:: :: Data transfer rates Rand/UCLA
212:: :: NWG meeting on network usage 212:: :: NWG meeting on network usage
193:: :: Network checkout 193:: :: Network checkout
188:: :: Data management meeting announcement 188:: :: Data management meeting announcement
156:: :: Status of the Illinois site 156:: :: Status of the Illinois site
153:: :: SRI ARC-NIC status 153:: :: SRI ARC-NIC status
96:: :: Interactive network experiment to study modes of 96:: :: Interactive network experiment to study modes of
access tothe Network Information Center access tothe Network Information Center
32:: :: Connecting M.I.T. computers to the 32:: :: Connecting M.I.T. computers to the
ARPA Computer-to-computer communication network ARPA Computer-to-computer communication network
18:: :: [Link assignments] 18:: :: [Link assignments]
====================================================================== ======================================================================
Network News Network News
1036:: :: Standard for interchange of USENET messages 1036:: :: Standard for interchange of USENET messages
977:: PS:: Network News Transfer Protocol 977:: PS:: Network News Transfer Protocol
850:: :: Standard for interchange of USENET messages 850:: :: Standard for interchange of USENET messages
=================================================================== ===================================================================
Real Time Services Real Time Services
:: :: :: ::
2102:: I:: Multicast Support for Nimrod 2102:: I:: Multicast Support for Nimrod
2090:: E:: TFTP Multicast Option 2090:: E:: TFTP Multicast Option
2038:: PS:: RTP Payload Format for MPEG1/MPEG2 Video 2038:: PS:: RTP Payload Format for MPEG1/MPEG2 Video
2035:: PS:: RTP Payload Format for JPEG-compressed Video 2035:: PS:: RTP Payload Format for JPEG-compressed Video
skipping to change at page 1, line 2821 skipping to change at page 1, line 2825
1469:: PS:: IP Multicast over Token-Ring Local Area Networks 1469:: PS:: IP Multicast over Token-Ring Local Area Networks
1458:: I:: Requirements for Multicast Protocols 1458:: I:: Requirements for Multicast Protocols
1453:: I:: A Comment on Packet Video Remote Conferencing and the 1453:: I:: A Comment on Packet Video Remote Conferencing and the
Transport/Network Layers Transport/Network Layers
1313:: I:: Today's Programming for KRFC AM 1313 Internet Talk Radio 1313:: I:: Today's Programming for KRFC AM 1313 Internet Talk Radio
1301:: I:: Multicast Transport Protocol 1301:: I:: Multicast Transport Protocol
1257:: I:: Isochronous Applications Do Not Require 1257:: I:: Isochronous Applications Do Not Require
Jitter-Controlled Networks Jitter-Controlled Networks
1197:: I:: Using ODA for Translating Multimedia Information 1197:: I:: Using ODA for Translating Multimedia Information
1193:: :: Client Requirements for Real-Time Communication Services 1193:: :: Client Requirements for Real-Time Communication Services
1190:: E:: "Experimental Internet Stream Protocol, Version 2 (ST-II)" 1190:: E:: Experimental Internet Stream Protocol, Version 2 (ST-II)
1112:: S:: Host extensions for IP multicasting 1112:: S:: Host extensions for IP multicasting
1054:: :: Host extensions for IP multicasting 1054:: :: Host extensions for IP multicasting
988:: :: Host extensions for IP multicasting 988:: :: Host extensions for IP multicasting
966:: :: Host groups 966:: :: Host groups
947:: :: Multi-network broadcasting within the Internet 947:: :: Multi-network broadcasting within the Internet
809:: :: UCL facsimile system 809:: :: UCL facsimile system
804:: :: CCITT draft recommendation T.4 [Standardization of 804:: :: CCITT draft recommendation T.4 [Standardization of
Group 3 facsimile apparatus for document transmission] Group 3 facsimile apparatus for document transmission]
803:: :: Dacom 450/500 facsimile data transcoding 803:: :: Dacom 450/500 facsimile data transcoding
798:: :: Decoding facsimile data from the Rapicom 450 798:: :: Decoding facsimile data from the Rapicom 450
skipping to change at page 1, line 2865 skipping to change at page 1, line 2868
1992:: I:: The Nimrod Routing Architecture 1992:: I:: The Nimrod Routing Architecture
1987:: I:: Ipsilon's General Switch Management Protocol 1987:: I:: Ipsilon's General Switch Management Protocol
Specification Version 1.1 Specification Version 1.1
1966:: E:: BGP Route Reflection An alternative to full mesh IBGP 1966:: E:: BGP Route Reflection An alternative to full mesh IBGP
1965:: E:: Autonomous System Confederations for BGP 1965:: E:: Autonomous System Confederations for BGP
1955:: I:: New Scheme for Internet Routing and Addressing (ENCAPS) 1955:: I:: New Scheme for Internet Routing and Addressing (ENCAPS)
for IPN for IPN
1953:: I:: Ipsilon Flow Management Protocol Specification for 1953:: I:: Ipsilon Flow Management Protocol Specification for
IPv4 Version 1.0 IPv4 Version 1.0
1940:: I:: Source Demand Routing 1940:: I:: Source Demand Routing
1930:: BC:: "Guidelines for creation, selection, and registration 1930:: BC:: Guidelines for creation, selection, and registration
of an Autonomous System (AS)" of an Autonomous System (AS)
1925:: I:: The Twelve Networking Truths 1925:: I:: The Twelve Networking Truths
1923:: I:: RIPv1 Applicability Statement for Historic Status 1923:: I:: RIPv1 Applicability Statement for Historic Status
1863:: E:: A BGP/IDRP Route Server alternative to a full mesh routing 1863:: E:: A BGP/IDRP Route Server alternative to a full mesh routing
1817:: I:: CIDR and Classful Routing 1817:: I:: CIDR and Classful Routing
1812:: PS:: Requirements for IP Version 4 Routers 1812:: PS:: Requirements for IP Version 4 Routers
1793:: PS:: Extending OSPF to Support Demand Circuits 1793:: PS:: Extending OSPF to Support Demand Circuits
1787:: I:: Routing in a Multi-provider Internet 1787:: I:: Routing in a Multi-provider Internet
1786:: I:: Representation of IP Routing Policies in a Routing Registry (ripe-81++) 1786:: I:: Representation of IP Routing Policies in a Routing
Registry (ripe-81++)
1774:: I:: BGP-4 Protocol Analysis 1774:: I:: BGP-4 Protocol Analysis
1773:: I:: Experience with the BGP-4 protocol 1773:: I:: Experience with the BGP-4 protocol
1772:: DS:: Application of the Border Gateway Protocol in the Internet 1772:: DS:: Application of the Border Gateway Protocol in the Internet
1771:: DS:: A Border Gateway Protocol 4 (BGP-4) 1771:: DS:: A Border Gateway Protocol 4 (BGP-4)
1765:: E:: OSPF Database Overflow 1765:: E:: OSPF Database Overflow
1753:: I:: IPng Technical Requirements Of the Nimrod Routing and 1753:: I:: IPng Technical Requirements Of the Nimrod Routing and
Addressing Architecture Addressing Architecture
1745:: PS:: BGP4/IDRP for IP---OSPF Interaction 1745:: PS:: BGP4/IDRP for IP---OSPF Interaction
1723:: DS:: RIP Version 2 Carrying Additional Information 1723:: DS:: RIP Version 2 Carrying Additional Information
1722:: DS:: RIP Version 2 Protocol Applicability Statement 1722:: DS:: RIP Version 2 Protocol Applicability Statement
skipping to change at page 1, line 2922 skipping to change at page 1, line 2927
1477:: I:: IDPR as a Proposed Standard 1477:: I:: IDPR as a Proposed Standard
1476:: E:: RAP 1476:: E:: RAP
1439:: I:: The Uniqueness of Unique Identifiers 1439:: I:: The Uniqueness of Unique Identifiers
1403:: PS:: BGP OSPF Interaction 1403:: PS:: BGP OSPF Interaction
1397:: PS:: Default Route Advertisement In BGP2 And BGP3 Versions Of 1397:: PS:: Default Route Advertisement In BGP2 And BGP3 Versions Of
The Border Gateway Protocol The Border Gateway Protocol
1388:: PS:: RIP Version 2 Carrying Additional Information 1388:: PS:: RIP Version 2 Carrying Additional Information
1387:: I:: RIP Version 2 Protocol Analysis 1387:: I:: RIP Version 2 Protocol Analysis
1383:: I:: An Experiment in DNS Based IP Routing 1383:: I:: An Experiment in DNS Based IP Routing
1380:: I:: IESG Deliberations on Routing and Addressing 1380:: I:: IESG Deliberations on Routing and Addressing
1371:: I:: "Choosing a ""Common IGP"" for the IP Internet (The 1371:: I:: Choosing a "Common IGP" for the IP Internet (The
IESG's Recommendation to the IAB)" IESG's Recommendation to the IAB)
1370:: PS:: Applicability Statement for OSPF 1370:: PS:: Applicability Statement for OSPF
1364:: PS:: BGP OSPF Interaction 1364:: PS:: BGP OSPF Interaction
1338:: I:: Supernetting 1338:: I:: Supernetting
1322:: I:: A Unified Approach to Inter-Domain Routing 1322:: I:: A Unified Approach to Inter-Domain Routing
1268:: DS:: Application of the Border Gateway Protocol in the Internet 1268:: DS:: Application of the Border Gateway Protocol in the Internet
1267:: DS:: A Border Gateway Protocol 3 (BGP-3) 1267:: DS:: A Border Gateway Protocol 3 (BGP-3)
1266:: I:: Experience with the BGP Protocol 1266:: I:: Experience with the BGP Protocol
1265:: I:: BGP Protocol Analysis 1265:: I:: BGP Protocol Analysis
1264:: I:: Internet Routing Protocol Standardization Criteria 1264:: I:: Internet Routing Protocol Standardization Criteria
1254:: I:: Gateway Congestion Control Survey 1254:: I:: Gateway Congestion Control Survey
skipping to change at page 1, line 2958 skipping to change at page 1, line 2963
routing routing
1124:: :: Policy issues in interconnecting networks 1124:: :: Policy issues in interconnecting networks
1105:: E:: Border Gateway Protocol BGP 1105:: E:: Border Gateway Protocol BGP
1104:: :: Models of policy based routing 1104:: :: Models of policy based routing
1102:: :: Policy routing in Internet protocols 1102:: :: Policy routing in Internet protocols
1092:: :: EGP and policy based routing in the new NSFNET backbone 1092:: :: EGP and policy based routing in the new NSFNET backbone
1075:: E:: Distance Vector Multicast Routing Protocol 1075:: E:: Distance Vector Multicast Routing Protocol
1074:: :: NSFNET backbone SPF based Interior Gateway Protocol 1074:: :: NSFNET backbone SPF based Interior Gateway Protocol
1058:: S:: Routing Information Protocol 1058:: S:: Routing Information Protocol
1009:: H:: Requirements for Internet gateways 1009:: H:: Requirements for Internet gateways
995:: :: End System to Intermediate System Routing Exchange Protocol for use in conjunction with ISO 8473 995:: :: End System to Intermediate System Routing Exchange
Protocol for use in conjunction with ISO 8473
985:: :: Requirements for Internet gateways - draft 985:: :: Requirements for Internet gateways - draft
981:: :: Experimental multiple-path routing algorithm 981:: :: Experimental multiple-path routing algorithm
975:: :: Autonomous confederations 975:: :: Autonomous confederations
950:: S:: Internet standard subnetting procedure 950:: S:: Internet standard subnetting procedure
911:: :: EGP Gateway under Berkeley UNIX 4.2 911:: :: EGP Gateway under Berkeley UNIX 4.2
904:: H:: Exterior Gateway Protocol formal specification 904:: H:: Exterior Gateway Protocol formal specification
898:: :: Gateway special interest group meeting notes 898:: :: Gateway special interest group meeting notes
890:: :: Exterior Gateway Protocol implementation schedule 890:: :: Exterior Gateway Protocol implementation schedule
888:: :: STUB Exterior Gateway Protocol 888:: :: STUB Exterior Gateway Protocol
875:: :: "Gateways, architectures, and heffalumps" 875:: :: Gateways, architectures, and heffalumps
827:: :: Exterior Gateway Protocol EGP 827:: :: Exterior Gateway Protocol EGP
823:: H:: DARPA Internet gateway 823:: H:: DARPA Internet gateway
===================================================================== =====================================================================
Security Security
2104:: I:: HMAC 2104:: I:: HMAC
2085:: PS:: HMAC-MD5 IP Authentication with Replay Prevention 2085:: PS:: HMAC-MD5 IP Authentication with Replay Prevention
2084:: I:: Considerations for Web Transaction Security 2084:: I:: Considerations for Web Transaction Security
2082:: PS:: RIP-2 MD5 Authentication 2082:: PS:: RIP-2 MD5 Authentication
2078:: PS:: "Generic Security Service Application Program Interface, 2078:: PS:: Generic Security Service Application Program Interface,
Version 2" Version 2
2069:: PS:: An Extension to HTTP 2069:: PS:: An Extension to HTTP
2065:: PS:: Domain Name System Security Extensions 2065:: PS:: Domain Name System Security Extensions
2059:: I:: RADIUS Accounting 2059:: I:: RADIUS Accounting
2058:: PS:: Remote Authentication Dial In User Service (RADIUS) 2058:: PS:: Remote Authentication Dial In User Service (RADIUS)
2057:: I:: Source directed access control on the Internet. 2057:: I:: Source directed access control on the Internet.
2040:: I:: "The RC5, RC5-CBC, RC5-CBC-Pad, and RC5-CTS Algorithms" 2040:: I:: The RC5, RC5-CBC, RC5-CBC-Pad, and RC5-CTS Algorithms
2025:: PS:: The Simple Public-Key GSS-API Mechanism (SPKM) 2025:: PS:: The Simple Public-Key GSS-API Mechanism (SPKM)
2015:: :: MIME Security with Pretty Good Privacy (PGP) 2015:: :: MIME Security with Pretty Good Privacy (PGP)
1984:: I:: IAB and IESG Statement on Cryptographic Technology and 1984:: I:: IAB and IESG Statement on Cryptographic Technology and
the Internet the Internet
1969:: I:: The PPP DES Encryption Protocol (DESE) 1969:: I:: The PPP DES Encryption Protocol (DESE)
1968:: PS:: The PPP Encryption Control Protocol (ECP) 1968:: PS:: The PPP Encryption Control Protocol (ECP)
1964:: PS:: The Kerberos Version 5 GSS-API Mechanism 1964:: PS:: The Kerberos Version 5 GSS-API Mechanism
1961:: PS:: GSS-API Authentication Method for SOCKS Version 5 1961:: PS:: GSS-API Authentication Method for SOCKS Version 5
1949:: E:: Scalable Multicast Key Distribution 1949:: E:: Scalable Multicast Key Distribution
1948:: I:: Defending Against Sequence Number Attacks 1948:: I:: Defending Against Sequence Number Attacks
skipping to change at page 1, line 3023 skipping to change at page 1, line 3027
1704:: I:: On Internet Authentication 1704:: I:: On Internet Authentication
1675:: I:: Security Concerns for IPng 1675:: I:: Security Concerns for IPng
1579:: I:: Firewall-Friendly FTP 1579:: I:: Firewall-Friendly FTP
1535:: I:: A Security Problem and Proposed Correction With Widely 1535:: I:: A Security Problem and Proposed Correction With Widely
Deployed DNS Software Deployed DNS Software
1511:: I:: Common Authentication Technology Overview 1511:: I:: Common Authentication Technology Overview
1510:: PS:: The Kerberos Network Authentication Service (V5) 1510:: PS:: The Kerberos Network Authentication Service (V5)
1509:: PS:: Generic Security Service API 1509:: PS:: Generic Security Service API
1508:: PS:: Generic Security Service Application Program Interface 1508:: PS:: Generic Security Service Application Program Interface
1507:: E:: DASS - Distributed Authentication Security Service 1507:: E:: DASS - Distributed Authentication Security Service
1492:: I:: "An Access Control Protocol, Sometimes Called TACACS" 1492:: I:: An Access Control Protocol, Sometimes Called TACACS
1457:: I:: Security Label Framework for the Internet 1457:: I:: Security Label Framework for the Internet
1455:: E:: Physical Link Security Type of Service 1455:: E:: Physical Link Security Type of Service
1424:: PS:: Privacy Enhancement for Internet Electronic Mail 1424:: PS:: Privacy Enhancement for Internet Electronic Mail
1423:: PS:: "Privacy Enhancement for Internet Electronic Mail 1423:: PS:: Privacy Enhancement for Internet Electronic Mail
1422:: PS:: Privacy Enhancement for Internet Electronic Mail 1422:: PS:: Privacy Enhancement for Internet Electronic Mail
1421:: PS:: Privacy Enhancement for Internet Electronic Mail 1421:: PS:: Privacy Enhancement for Internet Electronic Mail
1416:: E:: Telnet Authentication Option 1416:: E:: Telnet Authentication Option
1412:: E:: Telnet Authentication 1412:: E:: Telnet Authentication
1411:: E:: Telnet Authentication 1411:: E:: Telnet Authentication
1409:: E:: Telnet Authentication Option 1409:: E:: Telnet Authentication Option
1408:: H:: Telnet Environment Option 1408:: H:: Telnet Environment Option
1321:: I:: The MD5 Message-Digest Algorithm 1321:: I:: The MD5 Message-Digest Algorithm
1320:: I:: The MD4 Message-Digest Algorithm 1320:: I:: The MD4 Message-Digest Algorithm
1319:: I:: The MD2 Message-Digest Algorithm 1319:: I:: The MD2 Message-Digest Algorithm
1281:: I:: Guidelines for the Secure Operation of the Internet 1281:: I:: Guidelines for the Secure Operation of the Internet
1244:: I:: Site Security Handbook 1244:: I:: Site Security Handbook
1186:: I:: The MD4 Message Digest Algorithm 1186:: I:: The MD4 Message Digest Algorithm
1170:: I:: Public Key Standards and Licenses 1170:: I:: Public Key Standards and Licenses
1156:: S:: Management Information Base for Network Management of 1156:: S:: Management Information Base for Network Management of
TCP/IP-based internets TCP/IP-based internets
1115:: H:: "Privacy enhancement for Internet electronic mail 1115:: H:: Privacy enhancement for Internet electronic mail
1114:: H:: Privacy enhancement for Internet electronic mail 1114:: H:: Privacy enhancement for Internet electronic mail
1113:: H:: Privacy enhancement for Internet electronic mail 1113:: H:: Privacy enhancement for Internet electronic mail
1108:: PS:: U.S. Department of Defense Security Options for the 1108:: PS:: U.S. Department of Defense Security Options for the
Internet Protocol Internet Protocol
1040:: :: Privacy enhancement for Internet electronic mail 1040:: :: Privacy enhancement for Internet electronic mail
1038:: :: Draft revised IP security option 1038:: :: Draft revised IP security option
1004:: E:: Distributed-protocol authentication scheme 1004:: E:: Distributed-protocol authentication scheme
989:: :: Privacy enhancement for Internet electronic mail 989:: :: Privacy enhancement for Internet electronic mail
972:: :: Password Generator Protocol 972:: :: Password Generator Protocol
931:: E:: Authentication server 931:: E:: Authentication server
skipping to change at page 1, line 3085 skipping to change at page 1, line 3088
1116:: PS:: Telnet Linemode option 1116:: PS:: Telnet Linemode option
1097:: :: Telnet subliminal-message option 1097:: :: Telnet subliminal-message option
1096:: :: Telnet X display location option 1096:: :: Telnet X display location option
1091:: :: Telnet terminal-type option 1091:: :: Telnet terminal-type option
1080:: :: Telnet remote flow control option 1080:: :: Telnet remote flow control option
1079:: :: Telnet terminal speed option 1079:: :: Telnet terminal speed option
1073:: :: Telnet window size option 1073:: :: Telnet window size option
1053:: :: Telnet X.3 PAD option 1053:: :: Telnet X.3 PAD option
1043:: :: Telnet Data Entry Terminal option 1043:: :: Telnet Data Entry Terminal option
1041:: :: Telnet 3270 regime option 1041:: :: Telnet 3270 regime option
1013:: :: "X Window System Protocol, version 11 1013:: :: X Window System Protocol, version 11
1005:: :: ARPANET AHIP-E Host Access Protocol enhanced AHIP 1005:: :: ARPANET AHIP-E Host Access Protocol enhanced AHIP
946:: :: Telnet terminal location number option 946:: :: Telnet terminal location number option
933:: :: Output marking Telnet option 933:: :: Output marking Telnet option
930:: :: Telnet terminal type option 930:: :: Telnet terminal type option
929:: :: Proposed Host-Front End Protocol 929:: :: Proposed Host-Front End Protocol
907:: S:: Host Access Protocol specification 907:: S:: Host Access Protocol specification
885:: :: Telnet end of record option 885:: :: Telnet end of record option
884:: :: Telnet terminal type option 884:: :: Telnet terminal type option
878:: :: ARPANET 1822L Host Access Protocol 878:: :: ARPANET 1822L Host Access Protocol
861:: :: Telnet extended options 861:: :: Telnet extended options
skipping to change at page 1, line 3125 skipping to change at page 1, line 3128
734:: H:: SUPDUP Protocol 734:: H:: SUPDUP Protocol
732:: :: Telnet Data Entry Terminal option 732:: :: Telnet Data Entry Terminal option
731:: :: Telnet Data Entry Terminal option 731:: :: Telnet Data Entry Terminal option
729:: :: Telnet byte macro option 729:: :: Telnet byte macro option
728:: :: Minor pitfall in the Telnet Protocol 728:: :: Minor pitfall in the Telnet Protocol
727:: :: Telnet logout option 727:: :: Telnet logout option
726:: :: Remote Controlled Transmission and Echoing Telnet option 726:: :: Remote Controlled Transmission and Echoing Telnet option
721:: :: Out-of-band control signals in a Host-to-Host Protocol 721:: :: Out-of-band control signals in a Host-to-Host Protocol
719:: :: Discussion on RCTE 719:: :: Discussion on RCTE
718:: :: Comments on RCTE from the Tenex implementation experience 718:: :: Comments on RCTE from the Tenex implementation experience
703:: :: "July, 1975, survey of New-Protocol Telnet Servers" 703:: :: July, 1975, survey of New-Protocol Telnet Servers
702:: :: "September, 1974, survey of New-Protocol Telnet servers" 702:: :: September, 1974, survey of New-Protocol Telnet servers
701:: :: "August, 1974, survey of New-Protocol Telnet servers" 701:: :: August, 1974, survey of New-Protocol Telnet servers
698:: :: Telnet extended ASCII option 698:: :: Telnet extended ASCII option
688:: :: Tentative schedule for the new Telnet implementation for 688:: :: Tentative schedule for the new Telnet implementation for
the TIP the TIP
679:: :: "February, 1975, survey of New-Protocol Telnet servers" 679:: :: February, 1975, survey of New-Protocol Telnet servers
669:: :: "November, 1974, survey of New-Protocol Telnet servers" 669:: :: November, 1974, survey of New-Protocol Telnet servers
659:: :: Announcing additional Telnet options 659:: :: Announcing additional Telnet options
658:: :: Telnet output linefeed disposition 658:: :: Telnet output linefeed disposition
657:: :: Telnet output vertical tab disposition option 657:: :: Telnet output vertical tab disposition option
656:: :: Telnet output vertical tabstops option 656:: :: Telnet output vertical tabstops option
655:: :: Telnet output formfeed disposition option 655:: :: Telnet output formfeed disposition option
654:: :: Telnet output horizontal tab disposition option 654:: :: Telnet output horizontal tab disposition option
653:: :: Telnet output horizontal tabstops option 653:: :: Telnet output horizontal tabstops option
652:: :: Telnet output carriage-return disposition option 652:: :: Telnet output carriage-return disposition option
651:: :: Revised Telnet status option 651:: :: Revised Telnet status option
647:: :: Proposed protocol for connecting host computers to 647:: :: Proposed protocol for connecting host computers to
skipping to change at page 1, line 3169 skipping to change at page 1, line 3172
435:: :: Telnet issues 435:: :: Telnet issues
431:: :: Update on SMFS login and logout 431:: :: Update on SMFS login and logout
399:: :: SMFS login and logout 399:: :: SMFS login and logout
393:: :: Comments on Telnet Protocol changes 393:: :: Comments on Telnet Protocol changes
386:: :: Letter to TIP users-2 386:: :: Letter to TIP users-2
377:: :: Using TSO via ARPA Network Virtual Terminal 377:: :: Using TSO via ARPA Network Virtual Terminal
365:: :: Letter to all TIP users 365:: :: Letter to all TIP users
364:: :: Serving remote users on the ARPANET 364:: :: Serving remote users on the ARPANET
352:: :: TIP site information form 352:: :: TIP site information form
340:: :: Proposed Telnet changes 340:: :: Proposed Telnet changes
339:: :: "MLTNET 339:: :: MLTNET
328:: :: Suggested Telnet Protocol changes 328:: :: Suggested Telnet Protocol changes
318:: :: [Ad hoc Telnet Protocol] 318:: :: [Ad hoc Telnet Protocol]
311:: :: New console attachments to the USCB host 311:: :: New console attachments to the USCB host
297:: :: TIP message buffers 297:: :: TIP message buffers
296:: :: DS-1 display system 296:: :: DS-1 display system
231:: :: Service center standards for remote usage 231:: :: Service center standards for remote usage
230:: :: Toward reliable operation of minicomputer-based 230:: :: Toward reliable operation of minicomputer-based
terminals on a TIP terminals on a TIP
216:: :: Telnet access to UCSB's On-Line System 216:: :: Telnet access to UCSB's On-Line System
215:: :: "NCP, ICP, and Telnet 215:: :: NCP, ICP, and Telnet
206:: :: User Telnet - description of an initial implementation 206:: :: User Telnet - description of an initial implementation
205:: :: NETCRT - a character display protocol 205:: :: NETCRT - a character display protocol
177:: :: Device independent graphical display description 177:: :: Device independent graphical display description
158:: :: Telnet Protocol 158:: :: Telnet Protocol
139:: :: Discussion of Telnet Protocol 139:: :: Discussion of Telnet Protocol
137:: :: Telnet Protocol - a proposed document 137:: :: Telnet Protocol - a proposed document
110:: :: Conventions for using an IBM 2741 terminal as a 110:: :: Conventions for using an IBM 2741 terminal as a
user console for access to network server hosts user console for access to network server hosts
97:: :: First cut at a proposed Telnet Protocol 97:: :: First cut at a proposed Telnet Protocol
===================================================================== =====================================================================
skipping to change at page 1, line 3205 skipping to change at page 1, line 3207
2101:: I:: IPv4 Address Behaviour Today 2101:: I:: IPv4 Address Behaviour Today
2100:: I:: The Naming of Hosts 2100:: I:: The Naming of Hosts
2099:: I:: Request for Comments Summary RFC Numbers 2000-2099 2099:: I:: Request for Comments Summary RFC Numbers 2000-2099
2083:: I:: PNG (Portable Network Graphics) Specification Version 1.0 2083:: I:: PNG (Portable Network Graphics) Specification Version 1.0
2071:: I:: Network Renumbering Overview 2071:: I:: Network Renumbering Overview
2050:: BC:: INTERNET REGISTRY IP ALLOCATION GUIDELINES 2050:: BC:: INTERNET REGISTRY IP ALLOCATION GUIDELINES
2036:: I:: Observations on the use of Components of the Class 2036:: I:: Observations on the use of Components of the Class
A Address Space within the Internet A Address Space within the Internet
2031:: I:: IETF-ISOC relationship 2031:: I:: IETF-ISOC relationship
2028:: BC:: The Organizations Involved in the IETF Standards Process 2028:: BC:: The Organizations Involved in the IETF Standards Process
2027:: BC:: "IAB and IESG Selection, Confirmation, and Recall Process 2027:: BC:: IAB and IESG Selection, Confirmation, and Recall Process
2026:: BC:: The Internet Standards Process -- Revision 3 2026:: BC:: The Internet Standards Process -- Revision 3
2014:: BC:: IRTF Research Group Guidelines and Procedures 2014:: BC:: IRTF Research Group Guidelines and Procedures
2007:: I:: Catalogue of Network Training Materials 2007:: I:: Catalogue of Network Training Materials
2000:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS 2000:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS
1999:: I:: Request for Comments Summary RFC Numbers 1900-1999 1999:: I:: Request for Comments Summary RFC Numbers 1900-1999
1988:: I:: Conditional Grant of Rights to Specific Hewlett-Packard 1988:: I:: Conditional Grant of Rights to Specific Hewlett-Packard
Patents In Conjunction With the Internet Engineering Patents In Conjunction With the Internet Engineering
Task Force's Internet-Standard Network Management Task Force's Internet-Standard Network Management
Framework Framework
1983:: I:: Internet Users' Glossary 1983:: I:: Internet Users' Glossary
1958:: I:: Architectural Principles of the Internet 1958:: I:: Architectural Principles of the Internet
1952:: I:: GZIP file format specification version 4.3 1952:: I:: GZIP file format specification version 4.3
1951:: I:: DEFLATE Compressed Data Format Specification version 1.3 1951:: I:: DEFLATE Compressed Data Format Specification version 1.3
1950:: I:: ZLIB Compressed Data Format Specification version 3.3 1950:: I:: ZLIB Compressed Data Format Specification version 3.3
1941:: I:: Frequently Asked Questions for Schools 1941:: I:: Frequently Asked Questions for Schools
1935:: I:: "What is the Internet, Anyway?" 1935:: I:: What is the Internet, Anyway?
1920:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS 1920:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS
1900:: I:: Renumbering Needs Work 1900:: I:: Renumbering Needs Work
1899:: I:: Request for Comments Summary RFC Numbers 1800-1899 1899:: I:: Request for Comments Summary RFC Numbers 1800-1899
1882:: I:: The 12-Days of Technology Before Christmas 1882:: I:: The 12-Days of Technology Before Christmas
1880:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS 1880:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS
1879:: I:: Class A Subnet Experiment Results and Recommendations 1879:: I:: Class A Subnet Experiment Results and Recommendations
1875:: I:: UNINETT PCA Policy Statements 1875:: I:: UNINETT PCA Policy Statements
1871:: BC:: Addendum to RFC 1602 -- Variance Procedure 1871:: BC:: Addendum to RFC 1602 -- Variance Procedure
1855:: I:: Netiquette Guidelines 1855:: I:: Netiquette Guidelines
1822:: I:: A Grant of Rights to Use a Specific IBM patent with 1822:: I:: A Grant of Rights to Use a Specific IBM patent with
skipping to change at page 1, line 3244 skipping to change at page 1, line 3246
1816:: I:: U.S. Government Internet Domain Names 1816:: I:: U.S. Government Internet Domain Names
1814:: I:: Unique Addresses are Good 1814:: I:: Unique Addresses are Good
1811:: I:: U.S. Government Internet Domain Names 1811:: I:: U.S. Government Internet Domain Names
1810:: I:: Report on MD5 Performance 1810:: I:: Report on MD5 Performance
1805:: I:: Location-Independent Data/Software Integrity Protocol 1805:: I:: Location-Independent Data/Software Integrity Protocol
1802:: I:: Introducing Project Long Bud 1802:: I:: Introducing Project Long Bud
1800:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS 1800:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS
1799:: I:: Request for Comments Summary RFC Numbers 1700-1799 1799:: I:: Request for Comments Summary RFC Numbers 1700-1799
1797:: E:: Class A Subnet Experiment 1797:: E:: Class A Subnet Experiment
1796:: I:: Not All RFCs are Standards 1796:: I:: Not All RFCs are Standards
1790:: I:: "An Agreement between the Internet Society and Sun 1790:: I:: An Agreement between the Internet Society and Sun
Microsystems, Inc. in the Matter of ONC RPC and Microsystems, Inc. in the Matter of ONC RPC and
XDR Protocols" XDR Protocols
1780:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS 1780:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS
1776:: I:: The Address is the Message 1776:: I:: The Address is the Message
1775:: I:: "To Be ""On"" the Internet" 1775:: I:: To Be "On" the Internet
1758:: I:: NADF Standing Documents 1758:: I:: NADF Standing Documents
1746:: I:: Ways to Define User Expectations 1746:: I:: Ways to Define User Expectations
1739:: I:: A Primer On Internet and TCP/IP Tools 1739:: I:: A Primer On Internet and TCP/IP Tools
1720:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS 1720:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS
1718:: I:: The Tao of IETF - A Guide for New Attendees of the 1718:: I:: The Tao of IETF - A Guide for New Attendees of the
Internet Engineering Task Force Internet Engineering Task Force
1715:: I:: The H Ratio for Address Assignment Efficiency 1715:: I:: The H Ratio for Address Assignment Efficiency
1709:: I:: K-12 Internetworking Guidelines 1709:: I:: K-12 Internetworking Guidelines
1700:: S:: ASSIGNED NUMBERS 1700:: S:: ASSIGNED NUMBERS
1699:: I:: Request for Comments Summary RFC Numbers 1600-1699 1699:: I:: Request for Comments Summary RFC Numbers 1600-1699
1691:: I:: The Document Architecture for the Cornell Digital Library 1691:: I:: The Document Architecture for the Cornell Digital Library
1690:: I:: Introducing the Internet Engineering and Planning 1690:: I:: Introducing the Internet Engineering and Planning
Group (IEPG) Group (IEPG)
1689:: I:: A Status Report on Networked Information Retrieval 1689:: I:: A Status Report on Networked Information Retrieval
1640:: I:: The Process for Organization of Internet Standards 1640:: I:: The Process for Organization of Internet Standards
Working Group (POISED) Working Group (POISED)
1636:: I:: "Report of IAB Workshop on Security in the Internet 1636:: I:: Report of IAB Workshop on Security in the Internet
Architecture - February 8-10, 1994" Architecture - February 8-10, 1994
1635:: I:: How to Use Anonymous FTP 1635:: I:: How to Use Anonymous FTP
1627:: I:: Network 10 Considered Harmful (Some Practices 1627:: I:: Network 10 Considered Harmful (Some Practices
Shouldn't be Codified) Shouldn't be Codified)
1610:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS 1610:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS
1607:: I:: A VIEW FROM THE 21ST CENTURY 1607:: I:: A VIEW FROM THE 21ST CENTURY
1606:: I:: A Historical Perspective On The Usage Of IP Version 9 1606:: I:: A Historical Perspective On The Usage Of IP Version 9
1603:: I:: IETF Working Group Guidelines and Procedures 1603:: I:: IETF Working Group Guidelines and Procedures
1602:: I:: The Internet Standards Process -- Revision 2 y1602:: I:: The Internet Standards Process -- Revision 2
1601:: I:: Charter of the Internet Architecture Board (IAB) 1601:: I:: Charter of the Internet Architecture Board (IAB)
1600:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS 1600:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS
1599:: I:: Request for Comments Summary RFC Numbers 1500 - 1599 1599:: I:: Request for Comments Summary RFC Numbers 1500 - 1599
1597:: I:: Address Allocation for Private Internets 1597:: I:: Address Allocation for Private Internets
1594:: I:: FYI on Questions and Answer Answers to Commonly 1594:: I:: FYI on Questions and Answer Answers to Commonly
asked ``New Internet User'' Questions asked "New Internet User" Questions
1580:: I:: Guide to Network Resource Tools 1580:: I:: Guide to Network Resource Tools
1578:: I:: FYI on Questions and Answers 1578:: I:: FYI on Questions and Answers
1574:: I:: Essential Tools for the OSI Internet 1574:: I:: Essential Tools for the OSI Internet
1550:: I:: IP 1550:: I:: IP
1543:: I:: Instructions to RFC Authors 1543:: I:: Instructions to RFC Authors
1540:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS 1540:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS
1539:: I:: The Tao of IETF - A Guide for New Attendees of the 1539:: I:: The Tao of IETF - A Guide for New Attendees of the
Internet Engineering Task Force Internet Engineering Task Force
1527:: I:: What Should We Plan Given the Dilemma of the Network? 1527:: I:: What Should We Plan Given the Dilemma of the Network?
1501:: I:: OS/2 User Group 1501:: I:: OS/2 User Group
1500:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS 1500:: S:: INTERNET OFFICIAL PROTOCOL STANDARDS
1499:: I:: Request for Comments Summary RFC Numbers 1400-1499 1499:: I:: Request for Comments Summary RFC Numbers 1400-1499
1481:: I:: IAB Recommendation for an Intermediate Strategy to 1481:: I:: IAB Recommendation for an Intermediate Strategy to
Address the Issue of Scaling Address the Issue of Scaling
1467:: I:: Status of CIDR Deployment in the Internet 1467:: I:: Status of CIDR Deployment in the Internet
1463:: I:: FYI on Introducing the Internet--A Short Bibliography 1463:: I:: FYI on Introducing the Internet--A Short Bibliography
of Introductory Internetworking Readings for the of Introductory Internetworking Readings for the
Network Novice Network Novice
1462:: I:: FYI on ``What is the Internet?'' 1462:: I:: FYI on "What is the Internet?"
1438:: I:: Internet Engineering Task Force Statements Of 1438:: I:: Internet Engineering Task Force Statements Of
Boredom (SOBs) Boredom (SOBs)
1432:: I:: Recent Internet Books 1432:: I:: Recent Internet Books
1417:: I:: NADF Standing Documents 1417:: I:: NADF Standing Documents
1410:: S:: IAB OFFICIAL PROTOCOL STANDARDS 1410:: S:: IAB OFFICIAL PROTOCOL STANDARDS
1402:: I:: There's Gold in them thar Networks! Searching for 1402:: I:: There's Gold in them thar Networks! Searching for
Treasure in all the Wrong Places Treasure in all the Wrong Places
1401:: I:: Correspondence between the IAB and DISA on the use 1401:: I:: Correspondence between the IAB and DISA on the use
of DNS throughout the Internet of DNS throughout the Internet
1399:: I:: Request for Comments Summary RFC Numbers 1300-1399 1399:: I:: Request for Comments Summary RFC Numbers 1300-1399
1396:: I:: The Process for Organization of Internet Standards 1396:: I:: The Process for Organization of Internet Standards
Working Group (POISED) Working Group (POISED)
1392:: I:: Internet Users' Glossary 1392:: I:: Internet Users' Glossary
1391:: I:: The Tao of IETF 1391:: I:: The Tao of IETF
1367:: I:: Schedule for IP Address Space Management Guidelines 1367:: I:: Schedule for IP Address Space Management Guidelines
1366:: I:: Guidelines for Management of IP Address Space 1366:: I:: Guidelines for Management of IP Address Space
1360:: S:: IAB OFFICIAL PROTOCOL STANDARDS 1360:: S:: IAB OFFICIAL PROTOCOL STANDARDS
1359:: I:: Connecting to the Internet What Connecting 1359:: I:: Connecting to the Internet What Connecting
Institutions Should Anticipate Institutions Should Anticipate
skipping to change at page 1, line 3323 skipping to change at page 1, line 3326
1392:: I:: Internet Users' Glossary 1392:: I:: Internet Users' Glossary
1391:: I:: The Tao of IETF 1391:: I:: The Tao of IETF
1367:: I:: Schedule for IP Address Space Management Guidelines 1367:: I:: Schedule for IP Address Space Management Guidelines
1366:: I:: Guidelines for Management of IP Address Space 1366:: I:: Guidelines for Management of IP Address Space
1360:: S:: IAB OFFICIAL PROTOCOL STANDARDS 1360:: S:: IAB OFFICIAL PROTOCOL STANDARDS
1359:: I:: Connecting to the Internet What Connecting 1359:: I:: Connecting to the Internet What Connecting
Institutions Should Anticipate Institutions Should Anticipate
1358:: I:: Charter of the Internet Architecture Board (IAB) 1358:: I:: Charter of the Internet Architecture Board (IAB)
1349:: PS:: Type of Service in the Internet Protocol Suite 1349:: PS:: Type of Service in the Internet Protocol Suite
1340:: S:: ASSIGNED NUMBERS 1340:: S:: ASSIGNED NUMBERS
1336:: I:: "Who's Who in the Internet Biographies of IAB, 1336:: I:: Who's Who in the Internet Biographies of IAB,
IESG and IRSG Members" IESG and IRSG Members
1325:: I:: FYI on Questions and Answers Answers to Commonly 1325:: I:: FYI on Questions and Answers Answers to Commonly
asked ``New Internet User'' Questions asked "New Internet User" Questions
1324:: I:: A Discussion on Computer Network Conferencing 1324:: I:: A Discussion on Computer Network Conferencing
1311:: I:: Introduction to the STD Notes 1311:: I:: Introduction to the STD Notes
1310:: I:: The Internet Standards Process 1310:: I:: The Internet Standards Process
1300:: I:: Remembrances of Things Past 1300:: I:: Remembrances of Things Past
1299:: I:: Request for Comments Summary RFC Numbers 1200-1299 1299:: I:: Request for Comments Summary RFC Numbers 1200-1299
1297:: I:: NOC Internal Integrated Trouble Ticket System 1297:: I:: NOC Internal Integrated Trouble Ticket System
Functional Specification Wishlist Functional Specification Wishlist
(``NOC TT REQUIREMENTS'') ("NOC TT REQUIREMENTS")
1296:: I:: Internet Growth (1981-1991) 1296:: I:: Internet Growth (1981-1991)
1295:: I:: User Bill of Rights for entries and listings in the 1295:: I:: User Bill of Rights for entries and listings in the
Public Directory Public Directory
1291:: I:: Mid-Level Networks 1291:: I:: Mid-Level Networks
1290:: I:: There's Gold in them thar Networks! or Searching for 1290:: I:: There's Gold in them thar Networks! or Searching for
Treasure in all the Wrong Places Treasure in all the Wrong Places
1287:: I:: Towards the Future Internet Architecture 1287:: I:: Towards the Future Internet Architecture
1280:: S:: IAB OFFICIAL PROTOCOL STANDARDS 1280:: S:: IAB OFFICIAL PROTOCOL STANDARDS
1261:: I:: Transition of NIC Services 1261:: I:: Transition of NIC Services
1259:: I:: Building The Open Road 1259:: I:: Building The Open Road
1251:: :: "Who's Who in the Internet 1251:: :: Who's Who in the Internet
1250:: S:: IAB Official Protocol Standards 1250:: S:: IAB Official Protocol Standards
1249:: I:: DIXIE Protocol Specification 1249:: I:: DIXIE Protocol Specification
1217:: :: Memo from the Consortium for Slow Commotion Research (CSCR) 1217:: :: Memo from the Consortium for Slow Commotion Research (CSCR)
1216:: :: Gigabit Network Economics and Paradigm Shifts 1216:: :: Gigabit Network Economics and Paradigm Shifts
1208:: :: A Glossary of Networking Terms 1208:: :: A Glossary of Networking Terms
1207:: :: Answers to Commonly asked ``Experienced Internet User'' 1207:: :: Answers to Commonly asked "Experienced Internet User"
Questions Questions
1206:: :: FYI on Questions and Answers - Answers to Commonly 1206:: :: FYI on Questions and Answers - Answers to Commonly
asked ``New Internet User'' Questions asked "New Internet User" Questions
1200:: S:: IAB Official Protocol Standards 1200:: S:: IAB Official Protocol Standards
1199:: I:: Request for Comments Summary RFC Numbers 1100-1199 1199:: I:: Request for Comments Summary RFC Numbers 1100-1199
1198:: I:: FYI on the X Window System 1198:: I:: FYI on the X Window System
1192:: :: Commercialization of the Internet Summary Report 1192:: :: Commercialization of the Internet Summary Report
1181:: :: RIPE Terms of Reference 1181:: :: RIPE Terms of Reference
1180:: :: A TCP/IP Tutorial 1180:: :: A TCP/IP Tutorial
1178:: :: Choosing a Name for Your Computer 1178:: :: Choosing a Name for Your Computer
1177:: :: FYI on Questions and Answers - Answers to Commonly 1177:: :: FYI on Questions and Answers - Answers to Commonly
Asked ``New Internet User'' Questions Asked "New Internet User" Questions
1175:: :: FYI on Where to Start - A Bibliography of 1175:: :: FYI on Where to Start - A Bibliography of
Internetworking Information Internetworking Information
1174:: I:: "IAB Recommended Policy on Distributing Internet 1174:: I:: IAB Recommended Policy on Distributing Internet
Identifier Assignment and IAB Recommended Policy Change Identifier Assignment and IAB Recommended Policy Change
to Internet ""Connected"" Status" to Internet "Connected" Status
1173:: :: "Responsibilities of Host and Network Managers 1173:: :: Responsibilities of Host and Network Managers
Summary of the ""Oral Tradition"" of the Internet" Summary of the "Oral Tradition" of the Internet
1169:: :: Explaining the Role of GOSIP 1169:: :: Explaining the Role of GOSIP
1167:: :: Thoughts on the National Research and Education Network 1167:: :: Thoughts on the National Research and Education Network
1160:: :: The Internet Activities Board 1160:: :: The Internet Activities Board
1152:: :: Workshop Report 1152:: :: Workshop Report
1150:: I:: F.Y.I. on F.Y.I. 1150:: I:: F.Y.I. on F.Y.I.
1149:: :: A Standard for the Transmission of IP Datagrams 1149:: :: A Standard for the Transmission of IP Datagrams
on Avian Carriers on Avian Carriers
1147:: I:: FYI on a Network Management Tool Catalog 1147:: I:: FYI on a Network Management Tool Catalog
1140:: S:: IAB Official Protocol Standards 1140:: S:: IAB Official Protocol Standards
1135:: :: Helminthiasis of the Internet 1135:: :: Helminthiasis of the Internet
skipping to change at page 1, line 3439 skipping to change at page 1, line 3442
900:: :: Assigned Numbers 900:: :: Assigned Numbers
899:: :: Request For Comments summary notes 899:: :: Request For Comments summary notes
880:: S:: Official protocols 880:: S:: Official protocols
873:: :: Illusion of vendor support 873:: :: Illusion of vendor support
870:: :: Assigned numbers 870:: :: Assigned numbers
869:: H:: Host Monitoring Protocol 869:: H:: Host Monitoring Protocol
852:: :: ARPANET short blocking feature 852:: :: ARPANET short blocking feature
847:: :: Summary of Smallberg surveys 847:: :: Summary of Smallberg surveys
846:: :: Who talks TCP? - survey of 22 February 1983 846:: :: Who talks TCP? - survey of 22 February 1983
845:: :: Who talks TCP? - survey of 15 February 1983 845:: :: Who talks TCP? - survey of 15 February 1983
844:: :: "Who talks ICMP, too? - Survey of 18 February 1983" 844:: :: Who talks ICMP, too? - Survey of 18 February 1983
843:: :: Who talks TCP? - survey of 8 February 83 843:: :: Who talks TCP? - survey of 8 February 83
842:: :: Who talks TCP? - survey of 1 February 83 842:: :: Who talks TCP? - survey of 1 February 83
840:: S:: Official protocols 840:: S:: Official protocols
839:: :: Who talks TCP? 839:: :: Who talks TCP?
838:: :: Who talks TCP? 838:: :: Who talks TCP?
837:: :: Who talks TCP? 837:: :: Who talks TCP?
836:: :: Who talks TCP? 836:: :: Who talks TCP?
835:: :: Who talks TCP? 835:: :: Who talks TCP?
834:: :: Who talks TCP? 834:: :: Who talks TCP?
833:: :: Who talks TCP? 833:: :: Who talks TCP?
832:: :: Who talks TCP? 832:: :: Who talks TCP?
831:: :: Backup access to the European side of SATNET 831:: :: Backup access to the European side of SATNET
828:: :: "Data communications 828:: :: Data communications
825:: :: Request for comments on Requests For Comments 825:: :: Request for comments on Requests For Comments
820:: :: Assigned numbers 820:: :: Assigned numbers
817:: :: Modularity and efficiency in protocol implementation 817:: :: Modularity and efficiency in protocol implementation
816:: :: Fault isolation and recovery 816:: :: Fault isolation and recovery
806:: :: Proposed Federal Information Processing Standard 806:: :: Proposed Federal Information Processing Standard
800:: :: Request For Comments summary notes 800:: :: Request For Comments summary notes
794:: :: Pre-emption 794:: :: Pre-emption
790:: :: Assigned numbers 790:: :: Assigned numbers
776:: :: Assigned numbers 776:: :: Assigned numbers
774:: :: Internet Protocol Handbook 774:: :: Internet Protocol Handbook
skipping to change at page 1, line 3507 skipping to change at page 1, line 3510
communication communication
629:: :: Scenario for using the Network Journal 629:: :: Scenario for using the Network Journal
628:: :: Status of RFC numbers and a note on pre-assigned 628:: :: Status of RFC numbers and a note on pre-assigned
journal numbers journal numbers
621:: :: NIC user directories at SRI ARC 621:: :: NIC user directories at SRI ARC
617:: :: Note on socket number assignment 617:: :: Note on socket number assignment
609:: :: Statement of upcoming move of NIC/NLS service 609:: :: Statement of upcoming move of NIC/NLS service
604:: :: Assigned link numbers 604:: :: Assigned link numbers
603:: :: Response to RFC 597 603:: :: Response to RFC 597
602:: :: The stockings were hung by the chimney with care 602:: :: The stockings were hung by the chimney with care
598:: :: "RFC index - December 5, 1973" 598:: :: RFC index - December 5, 1973
597:: :: Host status 597:: :: Host status
590:: :: MULTICS address change 590:: :: MULTICS address change
588:: :: London node is now up 588:: :: London node is now up
585:: :: ARPANET users interest working group meeting 585:: :: ARPANET users interest working group meeting
584:: :: Charter for ARPANET Users Interest Working Group 584:: :: Charter for ARPANET Users Interest Working Group
582:: :: Comments on RFC 580 582:: :: Comments on RFC 580
581:: :: Corrections to RFC 560 581:: :: Corrections to RFC 560
580:: :: Note to protocol designers and implementers 580:: :: Note to protocol designers and implementers
578:: :: Using MIT-Mathlab MACSYMA from MIT-DMS Muddle 578:: :: Using MIT-Mathlab MACSYMA from MIT-DMS Muddle
569:: H:: NETED 569:: H:: NETED
skipping to change at page 1, line 3534 skipping to change at page 1, line 3537
527:: :: ARPAWOCKY 527:: :: ARPAWOCKY
526:: :: Technical meeting 526:: :: Technical meeting
523:: :: SURVEY is in operation again 523:: :: SURVEY is in operation again
519:: :: Resource evaluation 519:: :: Resource evaluation
518:: :: ARPANET accounts 518:: :: ARPANET accounts
515:: :: Specifications for datalanguage 515:: :: Specifications for datalanguage
503:: :: Socket number list 503:: :: Socket number list
496:: :: TNLS quick reference card is available 496:: :: TNLS quick reference card is available
494:: :: Availability of MIX and MIXAL in the Network 494:: :: Availability of MIX and MIXAL in the Network
492:: :: Response to RFC 467 492:: :: Response to RFC 467
491:: :: "What is ""Free""?" 491:: :: What is "Free"?
483:: :: Cancellation of the resource notebook framework meeting 483:: :: Cancellation of the resource notebook framework meeting
474:: :: Announcement of NGWG meeting 474:: :: Announcement of NGWG meeting
464:: :: Resource notebook framework 464:: :: Resource notebook framework
462:: :: Responding to user needs 462:: :: Responding to user needs
457:: :: TIPUG 457:: :: TIPUG
456:: :: Memorandum 456:: :: Memorandum
441:: :: Inter-Entity Communication - an experiment 441:: :: Inter-Entity Communication - an experiment
440:: :: Scheduled network software maintenance 440:: :: Scheduled network software maintenance
439:: :: PARRY encounters the DOCTOR 439:: :: PARRY encounters the DOCTOR
433:: :: Socket number list 433:: :: Socket number list
skipping to change at page 1, line 3583 skipping to change at page 1, line 3586
322:: :: Well known socket numbers 322:: :: Well known socket numbers
321:: :: CBI networking activity at MITRE 321:: :: CBI networking activity at MITRE
320:: :: Workshop on hard copy line printers 320:: :: Workshop on hard copy line printers
319:: :: Network host status 319:: :: Network host status
317:: :: Official Host-Host Protocol modification 317:: :: Official Host-Host Protocol modification
316:: :: ARPA Network Data Management Working Group 316:: :: ARPA Network Data Management Working Group
315:: :: Network host status 315:: :: Network host status
313:: :: Computer based instruction 313:: :: Computer based instruction
305:: :: Unknown host numbers 305:: :: Unknown host numbers
303:: :: ARPA Network mailing lists 303:: :: ARPA Network mailing lists
295:: :: "Report of the Protocol Workshop, 12 October 1971" 295:: :: Report of the Protocol Workshop, 12 October 1971
291:: :: Data management meeting announcement 291:: :: Data management meeting announcement
290:: :: Computer networks and data sharing 290:: :: Computer networks and data sharing
282:: :: Graphics meeting report 282:: :: Graphics meeting report
276:: :: NIC course 276:: :: NIC course
270:: :: Correction to BBN Report No. 1822 NIC NO 7958 270:: :: Correction to BBN Report No. 1822 NIC NO 7958
269:: :: Some experience with file transfer 269:: :: Some experience with file transfer
263:: :: Very Distant Host interface 263:: :: Very Distant Host interface
256:: :: IMPSYS change notification 256:: :: IMPSYS change notification
254:: :: Scenarios for using ARPANET computers 254:: :: Scenarios for using ARPANET computers
253:: :: Second Network Graphics meeting details 253:: :: Second Network Graphics meeting details
skipping to change at page 1, line 3633 skipping to change at page 1, line 3636
185:: :: NIC distribution of manuals and handbooks 185:: :: NIC distribution of manuals and handbooks
182:: :: Compilation of list of relevant site reports 182:: :: Compilation of list of relevant site reports
180:: :: File system questionnaire 180:: :: File system questionnaire
179:: :: Link number assignments 179:: :: Link number assignments
173:: :: Network data management committee meeting announcement 173:: :: Network data management committee meeting announcement
171:: :: Data Transfer Protocol 171:: :: Data Transfer Protocol
170:: :: RFC list by number 170:: :: RFC list by number
169:: :: Computer networks 169:: :: Computer networks
168:: :: ARPA Network mailing lists 168:: :: ARPA Network mailing lists
167:: :: Socket conventions reconsidered 167:: :: Socket conventions reconsidered
164:: :: "Minutes of Network Working Group meeting, 5/16 164:: :: Minutes of Network Working Group meeting, 5/16
through 5/19/71 " through 5/19/71
162:: :: NETBUGGER3 162:: :: NETBUGGER3
160:: :: RFC brief list 160:: :: RFC brief list
157:: :: Invitation to the Second Symposium on Problems in the 157:: :: Invitation to the Second Symposium on Problems in the
Optimization of Data Communications Systems Optimization of Data Communications Systems
155:: :: ARPA Network mailing lists 155:: :: ARPA Network mailing lists
154:: :: Exposition style 154:: :: Exposition style
149:: :: Best laid plans 149:: :: Best laid plans
148:: :: Comments on RFC 123 148:: :: Comments on RFC 123
147:: :: Definition of a socket 147:: :: Definition of a socket
140:: :: Agenda for the May NWG meeting 140:: :: Agenda for the May NWG meeting
skipping to change at page 1, line 3667 skipping to change at page 1, line 3670
118:: :: Recommendations for facility documentation 118:: :: Recommendations for facility documentation
117:: :: Some comments on the official protocol 117:: :: Some comments on the official protocol
116:: :: Structure of the May NWG meeting 116:: :: Structure of the May NWG meeting
115:: :: Some Network Information Center policies on handling 115:: :: Some Network Information Center policies on handling
documents documents
113:: :: Network activity report 113:: :: Network activity report
112:: :: User/Server Site Protocol 112:: :: User/Server Site Protocol
111:: :: Pressure from the chairman 111:: :: Pressure from the chairman
109:: :: Level III Server Protocol for the Lincoln Laboratory 109:: :: Level III Server Protocol for the Lincoln Laboratory
NIC 360/67 Host NIC 360/67 Host
108:: :: "Attendance list at the Urbana NWG meeting, February 108:: :: Attendance list at the Urbana NWG meeting, February
17-19,1971 " 17-19,1971
107:: :: Output of the Host-Host Protocol glitch cleaning committee 107:: :: Output of the Host-Host Protocol glitch cleaning committee
106:: :: User/Server Site Protocol network host questionnaire 106:: :: User/Server Site Protocol network host questionnaire
104:: :: Link 191 104:: :: Link 191
103:: :: Implementation of interrupt keys 103:: :: Implementation of interrupt keys
102:: :: Output of the Host-Host Protocol glitch cleaning committee 102:: :: Output of the Host-Host Protocol glitch cleaning committee
101:: :: "Notes on the Network Working Group meeting, 101:: :: Notes on the Network Working Group meeting,
Urbana, Illinois, February 17, 1971" Urbana, Illinois, February 17, 1971
100:: :: Categorization and guide to NWG/RFCs 100:: :: Categorization and guide to NWG/RFCs
99:: :: Network meeting 99:: :: Network meeting
95:: :: Distribution of NWG/RFC's through the NIC 95:: :: Distribution of NWG/RFC's through the NIC
90:: :: CCN as a network service center 90:: :: CCN as a network service center
89:: :: Some historic moments in networking 89:: :: Some historic moments in networking
87:: :: Topic for discussion at the next Network Working Group 87:: :: Topic for discussion at the next Network Working Group
meeting meeting
85:: :: Network Working Group meeting 85:: :: Network Working Group meeting
84:: :: List of NWG/RFC's 1-80 84:: :: List of NWG/RFC's 1-80
82:: :: Network meeting notes 82:: :: Network meeting notes
81:: :: Request for reference information 81:: :: Request for reference information
78:: :: NCP status report 78:: :: NCP status report
77:: :: Network meeting report 77:: :: Network meeting report
76:: :: Connection by name 76:: :: Connection by name
75:: :: Network meeting 75:: :: Network meeting
74:: :: Specifications for network use of the UCSB On-Line System 74:: :: Specifications for network use of the UCSB On-Line System
73:: :: Response to NWG/RFC 67 73:: :: Response to NWG/RFC 67
72:: :: Proposed moratorium on changes to network protocol 72:: :: Proposed moratorium on changes to network protocol
71:: :: Reallocation in case of input error 71:: :: Reallocation in case of input error
69:: :: Distribution list change for MIT 69:: :: Distribution list change for MIT
68:: :: "Comments on memory allocation control commands 68:: :: Comments on memory allocation control commands
66:: :: NIC - third level ideas and other noise 66:: :: NIC - third level ideas and other noise
64:: :: Getting rid of marking 64:: :: Getting rid of marking
63:: :: Belated network meeting report 63:: :: Belated network meeting report
61:: :: Note on interprocess communication in a resource 61:: :: Note on interprocess communication in a resource
sharing computer network sharing computer network
57:: :: Thoughts and reflections on NWG/RFC 54 57:: :: Thoughts and reflections on NWG/RFC 54
52:: :: Updated distribution list 52:: :: Updated distribution list
51:: :: Proposal for a Network Interchange Language 51:: :: Proposal for a Network Interchange Language
50:: :: Comments on the Meyer proposal 50:: :: Comments on the Meyer proposal
49:: :: Conversations with S. Crocker UCLA 49:: :: Conversations with S. Crocker UCLA
48:: :: Possible protocol plateau 48:: :: Possible protocol plateau
47:: :: BBN's comments on NWG/RFC #33 47:: :: BBN's comments on NWG/RFC #33
46:: :: ARPA Network protocol notes 46:: :: ARPA Network protocol notes
45:: :: New protocol is coming 45:: :: New protocol is coming
44:: :: Comments on NWG/RFC 33 and 36 44:: :: Comments on NWG/RFC 33 and 36
43:: :: Proposed meeting [LIL] 43:: :: Proposed meeting [LIL]
40:: :: More comments on the forthcoming protocol 40:: :: More comments on the forthcoming protocol
39:: :: Comments on protocol re 39:: :: Comments on protocol re
37:: :: "Network meeting epilogue, etc" 37:: :: Network meeting epilogue, etc
36:: :: Protocol notes 36:: :: Protocol notes
35:: :: Network meeting 35:: :: Network meeting
34:: :: Some brief preliminary notes on the Augmentation 34:: :: Some brief preliminary notes on the Augmentation
Research Center clock Research Center clock
31:: :: Binary message forms in computer 31:: :: Binary message forms in computer
30:: :: Documentation conventions 30:: :: Documentation conventions
27:: :: Documentation conventions 27:: :: Documentation conventions
25:: :: No high link numbers 25:: :: No high link numbers
24:: :: Documentation conventions 24:: :: Documentation conventions
21:: :: Network meeting 21:: :: Network meeting
skipping to change at page 1, line 3750 skipping to change at page 1, line 3753
1:: :: Host software 1:: :: Host software
Appendix B: Automatic Script to Implement Methodology Appendix B: Automatic Script to Implement Methodology
#!/usr/bin/perl #!/usr/bin/perl
# Program to read text files (such as RFCs and Internet Drafts) and # Program to read text files (such as RFCs and Internet Drafts) and
# output items that might relate to year 2000 issues, particularly # output items that might relate to year 2000 issues, particularly
# 2-digit years. # 2-digit years.
# Version 1.1a. Slight modification by Philip J. Nesser
# (phil@nesser.com) to split lines from old RFC's that are
# too wide to conform with current RFC standards.
# Version 1.1. By Paul Hoffman (phoffman@imc.org). This is a # Version 1.1. By Paul Hoffman (phoffman@imc.org). This is a
# quick-and-dirty hack and could be written more elegantly and # quick-and-dirty hack and could be written more elegantly and
# more efficiently. There may be bugs in this software. For # more efficiently. There may be bugs in this software. For
# example, there was an off-by-one-line bug in version 1.0. # example, there was an off-by-one-line bug in version 1.0.
# Use this code at your own risk. This code may be freely # Use this code at your own risk. This code may be freely
# redistributed. # redistributed.
# Some people like using disk files, others like STDIN and STDOUT. # Some people like using disk files, others like STDIN and STDOUT.
# This program accomodates both types by setting the $UsageType # This program accomodates both types by setting the $UsageType
# variable. 'file' means input comes from the first argument on # variable. 'file' means input comes from the first argument on
skipping to change at page 1, line 3772 skipping to change at page 1, line 3779
$UsageType = 'file'; # Should be 'file' or 'std' $UsageType = 'file'; # Should be 'file' or 'std'
# @CheckWords is a list of words to look for. This list is used in # @CheckWords is a list of words to look for. This list is used in
# addition to the automatic checking for "yy" on a line without "YYYY". # addition to the automatic checking for "yy" on a line without "YYYY".
# You might want to add "year yyyy" to this list, but then a large # You might want to add "year yyyy" to this list, but then a large
# proportion of the RFCs and drafts get selected # proportion of the RFCs and drafts get selected
@CheckWords = qw(UTCTime two-digit 2-digit 2digit century 1900 2000); @CheckWords = qw(UTCTime two-digit 2-digit 2digit century 1900 2000);
if($UsageType eq 'file') { if($UsageType eq 'file') {
if($ARGV[0] eq '') if($ARGV[0] eq '')
{ die "You must specify the name of the file to open.\n" } { die "You must specify the name of the file to open.\n" }
$InName = $ARGV[0]; $InName = $ARGV[0];
unless(-r $InName) { die "Could not read $InName.\n" } unless(-r $InName) { die "Could not read $InName.\n" }
open(IN, $InName) or die "Could not open $InName.\n"; open(IN, $InName) or die "Could not open $InName.\n";
$OutName = "$InName.out"; $OutName = "$InName.out";
open(OUT, ">$OutName") or die "Could not write to $OutName.\n"; open(OUT, ">$OutName") or die "Could not write to $OutName.\n";
$OutStuff = ''; # Holder for what we're going to print out $OutStuff = ''; # Holder for what we're going to print out
} else { # Do STDIN and STDOUT } else { # Do STDIN and STDOUT
open(IN, "-"); open(OUT, ">-"); open(IN, "-"); open(OUT, ">-");
} }
# Read the whole file into an array. This is a tad wasteful of memory # Read the whole file into an array. This is a tad wasteful of memory
# but makes the output easier. # but makes the output easier.
@All = (); @All = ();
while(<IN>) { push(@All, $_) } while(<IN>) { push(@All, $_) }
$LastLine = $#All; $LastLine = $#All;
# Process the instance of "yy" not followed by "yy" # Process the instance of "yy" not followed by "yy"
for($i = 0; $i <= $LastLine; $i += 1 ) { for($i = 0; $i <= $LastLine; $i += 1 ) {
next unless(grep(/yy/i, $All[$i])); next unless(grep(/yy/i, $All[$i]));
next if(grep(/yyyy/i, $All[$i])); next if(grep(/yyyy/i, $All[$i]));
&PrintFive($i, "'yy' on a line without 'yyyy'"); &PrintFive($i, "'yy' on a line without 'yyyy'");
} }
# Next do the words that should cause extra concern # Next do the words that should cause extra concern
foreach $Word (@CheckWords) { foreach $Word (@CheckWords) {
for($i = 0; $i <= $LastLine; $i += 1 ) { for($i = 0; $i <= $LastLine; $i += 1 ) {
next unless(grep(/$Word/i, $All[$i])); next unless(grep(/$Word/i, $All[$i]));
&PrintFive($i, "$Word"); &PrintFive($i, "$Word");
} }
} }
# All done. If writing to a file, and nothing got written, delete the # All done. If writing to a file, and nothing got written, delete the
# file so that you can quickly scan for the ".out" files. # file so that you can quickly scan for the ".out" files.
# (A better-written program would have waited to do the opens # (A better-written program would have waited to do the opens
# until here so the unlink wouldn't be necessary. Oh, well.) # until here so the unlink wouldn't be necessary. Oh, well.)
if($UsageType eq 'file') { if($UsageType eq 'file') {
if(length($OutStuff) > 0) { if(length($OutStuff) > 0) {
$OutStuff = "+=+=+=+=+= File $InName +=+=+=+=+= \n$OutStuff\n"; $OutStuff = "+=+=+=+=+= File $InName +=+=+=+=+= \n$OutStuff\n
print OUT $OutStuff; close(OUT); print OUT $OutStuff; close(OUT);
} else { # Nothing to put in the .out } else { # Nothing to put in the .out
close(OUT); close(OUT);
unlink($OutName) or die "Couldn't unlink $OutName\n"; unlink($OutName) or die "Couldn't unlink $OutName\n";
} }
} }
exit; exit;
# Print the five lines around the word found # Print the five lines around the word found
sub PrintFive { sub PrintFive {
my $Where = shift(@_); my $Msg = shift(@_); my $Where = shift(@_); my $Msg = shift(@_);
my ($WhereRealLine, $Start, $End, $j); my ($WhereRealLine, $Start, $End, $j);
$WhereRealLine = $Where + 1; $WhereRealLine = $Where + 1;
$OutStuff .= "$Msg found at line $WhereRealLine:\n"; $OutStuff .= "$Msg found at line $WhereRealLine:\n";
$Start = $WhereRealLine - 2; $End = $WhereRealLine + 2; $Start = $WhereRealLine - 2; $End = $WhereRealLine + 2;
if($Where < 2) { $Start = 0 } if($Where < 2) { $Start = 0 }
if($Where > $LastLine - 2) { $End = $LastLine } if($Where > $LastLine - 2) { $End = $LastLine }
for($j = $Start; $j <= $End; $j += 1) { $OutStuff .= "$j: " for($j = $Start; $j <= $End; $j += 1) {
. $All[$j-1] } if (length($All[$j-1]) > 64) {
$OutStuff .= "\n"; $FirstHalf = substr($All[$j-1], 0, 64) . "\n";
$LastHalf = "$j(continued):\t\t" . substr($All[$j-1], 64);
$OutStuff .= "$j: " . $FirstHalf . $LastHalf;
}
else {
$OutStuff .= "$j: " . $All[$j-1]
}
}
$OutStuff .= "\n";
} }
Appendix C: Output of the script in Appendix B on all RFC's from 1 Appendix C: Output of the script in Appendix B on all RFC's from 1
through 2479 through 2479
+=+=+=+=+= File rfc0052.txt +=+=+=+=+= +=+=+=+=+= File rfc0052.txt +=+=+=+=+=
2000 found at line 141: 2000 found at line 141:
139: 139:
140: Chuck Rose Case University 140: Chuck Rose Case University
141: Jennings Computing Center (216) 368-2000 141: Jennings Computing Center (216) 368-2000
142: Case Western Reserve University x2808 142: Case Western Reserve University x2808
143: 10900 Euclid Avenue 143: 10900 Euclid Avenue
+=+=+=+=+= File rfc0090.txt +=+=+=+=+= +=+=+=+=+= File rfc0090.txt +=+=+=+=+=
2000 found at line 71: 2000 found at line 71:
69: consoles); 69: consoles);
70: 70:
71: j) Six data communication ports (3 dial @ 2000 baud, 71: j) Six data communication ports (3 dial @
72: 1 dedicated @ 4800 baud, and 2 dedicated @ 50,000 71(continued): 2000 baud,
72: 1 dedicated @ 4800 baud, and 2 dedicate
72(continued): d @ 50,000
73: baud) for remote batch entry terminals; 73: baud) for remote batch entry terminals;
73(continued):
+=+=+=+=+= File rfc0230.txt +=+=+=+=+= +=+=+=+=+= File rfc0230.txt +=+=+=+=+=
2000 found at line 92: 2000 found at line 92:
90: as for conventional synchronous block communication, since start and 90: as for conventional synchronous block communication, since start
91: stop bits for each character would need to be transmitted. This loss 90(continued): and
91: stop bits for each character would need to be transmitted. This
91(continued): loss
92: is not substantial and does occur now for 2000 bps TIP-terminal 92: is not substantial and does occur now for 2000 bps TIP-terminal
93: communication. 93: communication.
94: 94:
2000 found at line 134: 2000 found at line 134:
132: 92 transmitting sites in the U.S. and Canada were used with standard 132: 92 transmitting sites in the U.S. and Canada were used with stan
133: Bell System Dataphone datasets used at both ends. At both 1200 and 132(continued): dard
134: 2000 bps, approximately 82% of the calls had error rates of 1 error in 133: Bell System Dataphone datasets used at both ends. At both 1200
135: 10^5 bits or better, assuming an equal number of short, medium, and 133(continued): and
134: 2000 bps, approximately 82% of the calls had error rates of 1 er
134(continued): ror in
135: 10^5 bits or better, assuming an equal number of short, medium,
135(continued): and
136: long hauls. 136: long hauls.
+=+=+=+=+= File rfc0241.txt +=+=+=+=+= +=+=+=+=+= File rfc0241.txt +=+=+=+=+=
2000 found at line 32: 2000 found at line 32:
30: justifiable on the basis that the IMP and Host computers were 30: justifiable on the basis that the IMP and Host computers were
31: expected to be either in the same room (up to 30 feet of cable) or, 30(continued):
32: via the Distant Host option, within 2000 feet on well- controlled, 31: expected to be either in the same room (up to 30 feet of cabl
33: shielded cables. A connection through common carrier facilities is 31(continued): e) or,
34: not comparably free of errors. Usage of common- carrier lines for 32: via the Distant Host option, within 2000 feet on well- contro
32(continued): lled,
33: shielded cables. A connection through common carrier facilit
33(continued): ies is
34: not comparably free of errors. Usage of common- carrier line
34(continued): s for
+=+=+=+=+= File rfc0263.txt +=+=+=+=+= +=+=+=+=+= File rfc0263.txt +=+=+=+=+=
2000 found at line 22: 2000 found at line 22:
20: of the occasional desire to interface a Host to some IMP via a 20: of the occasional desire to interface a Host to some IMP via a
21: long-distance connection (where long-distance, in this context, 21: long-distance connection (where long-distance, in this context,
22: is any cable run longer than 2000 feet but may typically be tens 22: is any cable run longer than 2000 feet but may typically be tens
23: of miles) via either a hard-wire or telephone circuit. We believe 22(continued):
24: that any good solution to the general problem of interfacing Hosts 23: of miles) via either a hard-wire or telephone circuit. We belie
23(continued): ve
24: that any good solution to the general problem of interfacing Hos
24(continued): ts
+=+=+=+=+= File rfc0662.txt +=+=+=+=+= +=+=+=+=+= File rfc0662.txt +=+=+=+=+=
2000 found at line 143: 2000 found at line 143:
141: by a rather short cable (approximately 100 feet long.) The CISL Multics is 141: by a rather short cable (approximately 100 feet long.) The CISL
142: connected to the IMP number 6 (port 0) by an approximately l5OO feet long cable. 141(continued): Multics is
143: 8oth IMPs are in close physical proximity (approximately 2000 feet,) and are 142: connected to the IMP number 6 (port 0) by an approximately l5OO
144: connected to each other by a 5O kilobits per second line. The results given 142(continued): feet long cable.
145: above show considerable improvement in the performance with the new IMP DIM. 143: 8oth IMPs are in close physical proximity (approximately 2000 fe
143(continued): et,) and are
144: connected to each other by a 5O kilobits per second line. The re
144(continued): sults given
145: above show considerable improvement in the performance with the
145(continued): new IMP DIM.
+=+=+=+=+= File rfc0713.txt +=+=+=+=+= +=+=+=+=+= File rfc0713.txt +=+=+=+=+=
2000 found at line 830: 2000 found at line 830:
828: succeeding bytes in the stream used to encode the object. 828: succeeding bytes in the stream used to encode the object.
829: 829:
830: A data object requiring 20000 (47040 octal) bytes would 830: A data object requiring 20000 (47040 octal) bytes would
831: appear in the stream as follows. 831: appear in the stream as follows.
832: 832:
2000 found at line 837: 2000 found at line 837:
835: 10000010 -- specifying that the next 2 bytes 835: 10000010 -- specifying that the next 2 bytes
836: contain the stream length 836: contain the stream length
837: 01001110 -- first byte of number 20000 837: 01001110 -- first byte of number 20000
838: 00100000 -- second byte 838: 00100000 -- second byte
839: . 839: .
2000 found at line 845: 2000 found at line 845:
skipping to change at page 1, line 3918 skipping to change at page 1, line 3957
2000 found at line 845: 2000 found at line 845:
843: . 843: .
844: 844:
845: Interpretation of the contents of the 20000 bytes in 845: Interpretation of the contents of the 20000 bytes in
846: the stream can be performed by a module which knows the 846: the stream can be performed by a module which knows the
847: specific format of the non-atomic type specified by DEFGH in 847: specific format of the non-atomic type specified by DEFGH in
+=+=+=+=+= File rfc0724.txt +=+=+=+=+= +=+=+=+=+= File rfc0724.txt +=+=+=+=+=
2-digit found at line 1046: 2-digit found at line 1046:
1044: <4-digit-year> 1044: <4-digit-year>
1045: <slash-date> ::= <numeric-month> "/" <date-of-month> 1045: <slash-date> ::= <numeric-month> "/" <date-of-mo
1046: "/" <2-digit-year> 1045(continued): nth>
1046: "/" <2-digit-ye
1046(continued): ar>
1047: <numeric-month> ::= <one or two decimal digits> 1047: <numeric-month> ::= <one or two decimal digits>
1048: <day-of-month> ::= <one or two decimal digits> 1048: <day-of-month> ::= <one or two decimal digits>
2-digit found at line 1062: 2-digit found at line 1062:
1060: | "December" | "Dec" 1060: | "December" | "Dec"
1061: <4-digit-year> ::= <four decimal digits> 1061: <4-digit-year> ::= <four decimal digits>
1062: <2-digit-year> ::= <two decimal digits> 1062: <2-digit-year> ::= <two decimal digits>
1063: <time> ::= <24-hour-time> "-" <time-zone> 1063: <time> ::= <24-hour-time> "-" <time-zone>
1064: <24-hour-time> ::= <hour> <minute> 1064: <24-hour-time> ::= <hour> <minute>
2-digit found at line 1675: 2-digit found at line 1675:
1673: A. ALPHABETICAL LISTING OF SYNTAX RULES 1673: A. ALPHABETICAL LISTING OF SYNTAX RULES
1674: 1674:
1675: <2-digit-year> ::= <two decimal digits> 1675: <2-digit-year> ::= <two decimal digits>
1676: <4-digit-year> ::= <four decimal digits> 1676: <4-digit-year> ::= <four decimal digits>
1677: <24-hour-time> ::= <hour> <minute> 1677: <24-hour-time> ::= <hour> <minute>
2-digit found at line 1829: 2-digit found at line 1829:
1827: 1827:
1828: <slash-date> ::= <numeric-month> "/" <date-of-month> 1828: <slash-date> ::= <numeric-month> "/" <date-of-month>
1828(continued):
1829: "/" <2-digit-year> 1829: "/" <2-digit-year>
1830: <space> ::= <TELNET ASCII space (decimal 32)> 1830: <space> ::= <TELNET ASCII space (decimal 32)>
1831: 1831:
+=+=+=+=+= File rfc0731.txt +=+=+=+=+= +=+=+=+=+= File rfc0731.txt +=+=+=+=+=
2000 found at line 1571: 2000 found at line 1571:
1569: RFC 728, 1977. 1569: RFC 728, 1977.
1570: 1570:
1571: 9. Hazeltine 2000 Desk Top Display Operating Instructions. 1571: 9. Hazeltine 2000 Desk Top Display Operating Instructions.
1571(continued):
1572: Hazeltine IB-1866A, 1870. 1572: Hazeltine IB-1866A, 1870.
1573: 1573:
+=+=+=+=+= File rfc0732.txt +=+=+=+=+= +=+=+=+=+= File rfc0732.txt +=+=+=+=+=
2000 found at line 1681: 2000 found at line 1681:
1679: 1977. 1679: 1977.
1680: 1680:
1681: 9. Hazeltine 2000 Desk Top Display Operating Instructions. Hazeltine 1681: 9. Hazeltine 2000 Desk Top Display Operating Instructions. H
1681(continued): azeltine
1682: IB-1866A, 1870. 1682: IB-1866A, 1870.
1683: 1683:
+=+=+=+=+= File rfc0733.txt +=+=+=+=+= +=+=+=+=+= File rfc0733.txt +=+=+=+=+=
2-digit found at line 333: 2-digit found at line 333:
331: 331:
332: "<n>(element)" is equivalent to "<n>*<n>(element)"; that is, 332: "<n>(element)" is equivalent to "<n>*<n>(element)"; that is
333: exactly <n> occurrences of (element). Thus 2DIGIT is a 2-digit 332(continued): ,
333: exactly <n> occurrences of (element). Thus 2DIGIT is a 2-digi
333(continued): t
334: number, and 3ALPHA is a string of three alphabetic characters. 334: number, and 3ALPHA is a string of three alphabetic characters.
335: 335:
2digit found at line 333: 2digit found at line 333:
331: 331:
332: "<n>(element)" is equivalent to "<n>*<n>(element)"; that is, 332: "<n>(element)" is equivalent to "<n>*<n>(element)"; that is
333: exactly <n> occurrences of (element). Thus 2DIGIT is a 2-digit 332(continued): ,
333: exactly <n> occurrences of (element). Thus 2DIGIT is a 2-digi
333(continued): t
334: number, and 3ALPHA is a string of three alphabetic characters. 334: number, and 3ALPHA is a string of three alphabetic characters.
335: 335:
2digit found at line 947: 2digit found at line 947:
945: / "Sunday" / "Sun" 945: / "Sunday" / "Sun"
946: 946:
947: date = 1*2DIGIT ["-"] month ; day month year 947: date = 1*2DIGIT ["-"] month ; day month year
948: ["-"] (2DIGIT /4DIGIT) ; e.g. 20 Aug [19]77 948: ["-"] (2DIGIT /4DIGIT) ; e.g. 20 Aug [19]7
948(continued): 7
949: 949:
2digit found at line 948: 2digit found at line 948:
946: 946:
947: date = 1*2DIGIT ["-"] month ; day month year 947: date = 1*2DIGIT ["-"] month ; day month year
948: ["-"] (2DIGIT /4DIGIT) ; e.g. 20 Aug [19]77 948: ["-"] (2DIGIT /4DIGIT) ; e.g. 20 Aug [19]7
948(continued): 7
949: 949:
950: month = "January" / "Jan" / "February" / "Feb" 950: month = "January" / "Jan" / "February" / "Feb"
2digit found at line 967: 2digit found at line 967:
965: ; (seconds optional) 965: ; (seconds optional
965(continued): )
966: 966:
967: hour = 2DIGIT [":"] 2DIGIT [ [":"] 2DIGIT ] 967: hour = 2DIGIT [":"] 2DIGIT [ [":"] 2DIGIT ]
968: ; 0000[00] - 2359[59] 968: ; 0000[00] - 2359[59
968(continued): ]
969: 969:
2digit found at line 1718: 2digit found at line 1718:
1716: CTL = <any TELNET ASCII control character and DEL> 1716: CTL = <any TELNET ASCII control character and DEL>
1717: 1717:
1718: date = 1*2DIGIT ["-"] month ["-"] (2DIGIT /4DIGIT) 1718: date = 1*2DIGIT ["-"] month ["-"] (2DIGIT /4DIGIT)
1719: date-field = "Date" ":" date-time 1719: date-field = "Date" ":" date-time
1720: date-time = [ day-of-week "," ] date time 1720: date-time = [ day-of-week "," ] date time
2digit found at line 1754: 2digit found at line 1754:
1752: host-indicator = 1*( ("at" / "@") node ) 1752: host-indicator = 1*( ("at" / "@") node )
1753: host-phrase = phrase host-indicator 1753: host-phrase = phrase host-indicator
1754: hour = 2DIGIT [":"] 2DIGIT [ [":"] 2DIGIT ] 1754: hour = 2DIGIT [":"] 2DIGIT [ [":"] 2DIGIT ]
1755: HTAB = <TELNET ASCII horizontal-tab> 1755: HTAB = <TELNET ASCII horizontal-tab>
1756: 1756:
+=+=+=+=+= File rfc0734.txt +=+=+=+=+= +=+=+=+=+= File rfc0734.txt +=+=+=+=+=
2000 found at line 184: 2000 found at line 184:
182: Bit name Value Meaning 182: Bit name Value Meaning
183: 183:
184: %TOALT 200000,,0 characters 175 and 176 are converted to 184: %TOALT 200000,,0 characters 175 and 176 are
185: altmode (033) on input. 184(continued): converted to
185: altmode (033) on input.
186: 186:
2000 found at line 264: 2000 found at line 264:
262: NORMALLY OFF. 262: NORMALLY OFF.
263: 263:
264: %TOSA1 2000,,0 characters 001-037 should be displayed 264: %TOSA1 2000,,0 characters 001-037 should
265: using the Stanford/ITS extended ASCII 264(continued): be displayed
266: graphics character set instead of uparrow 265: using the Stanford/ITS extended
265(continued): ASCII
266: graphics character set instead of
266(continued): uparrow
2000 found at line 354: 2000 found at line 354:
352: %TXTOP 4000 This character has the [TOP] key depressed.
352: %TXTOP 4000 This character has the [TOP] key depressed.
353: 353:
354: %TXSFL 2000 Reserved, must be zero. 354: %TXSFL 2000 Reserved, must be zero.
355: 355:
356: %TXSFT 1000 Reserved, must be zero. 356: %TXSFT 1000 Reserved, must be zero.
2000 found at line 634: 2000 found at line 634:
632: Value Key 632: Value Key
633: 633:
634: 2000 Reserved 634: 2000 Reserved
635: 1000 Reserved 635: 1000 Reserved
636: 0400 <META> 636: 0400 <META>
+=+=+=+=+= File rfc0738.txt +=+=+=+=+= +=+=+=+=+= File rfc0738.txt +=+=+=+=+=
1900 found at line 41: 1900 found at line 41:
39: without sending anything. 39: without sending anything.
40: 40:
41: The time is the number of seconds since 0000 (midnight) 1 January 1900 41: The time is the number of seconds since 0000 (midnight) 1 Januar
42: GMT, such that the time 1 is 12:00:01 am on 1 January 1900 GMT; this 41(continued): y 1900
43: base will serve until the year 2036. As a further example, the most 42: GMT, such that the time 1 is 12:00:01 am on 1 January 1900 GMT;
42(continued): this
43: base will serve until the year 2036. As a further example, the
43(continued): most
1900 found at line 42: 1900 found at line 42:
40: 40:
41: The time is the number of seconds since 0000 (midnight) 1 January 1900 41: The time is the number of seconds since 0000 (midnight) 1 Januar
42: GMT, such that the time 1 is 12:00:01 am on 1 January 1900 GMT; this 41(continued): y 1900
43: base will serve until the year 2036. As a further example, the most 42: GMT, such that the time 1 is 12:00:01 am on 1 January 1900 GMT;
44: recent leap year as of this writing began from the time 2,398,291,200 42(continued): this
43: base will serve until the year 2036. As a further example, the
43(continued): most
44: recent leap year as of this writing began from the time 2,398,29
44(continued): 1,200
+=+=+=+=+= File rfc0745.txt +=+=+=+=+= +=+=+=+=+= File rfc0745.txt +=+=+=+=+=
2000 found at line 562: 2000 found at line 562:
560: Circuits, EIA standard RS-422," April 1975; Engineering Dept., 560: Circuits, EIA standard RS-422," April 1975; Engineering Dept.,
561: Electronic Industries Assn., 2001 Eye St., N.W., Washington, D.C., 561: Electronic Industries Assn., 2001 Eye St., N.W., Washington, D.C
561(continued): .,
562: 20006. 562: 20006.
563: 563:
564: REA bulletin 345-67, Rural Electrification Admin., U.S. Dept. of 564: REA bulletin 345-67, Rural Electrification Admin., U.S. Dept. of
564(continued):
+=+=+=+=+= File rfc0746.txt +=+=+=+=+= +=+=+=+=+= File rfc0746.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 341: 'yy' on a line without 'yyyy' found at line 341:
339: %TDGRF ;Enter graphics. 339: %TDGRF ;Enter graphics.
340: %GOCLR ;Clear the screen. 340: %GOCLR ;Clear the screen.
341: %GOMVA xx yy ;Set cursor. 341: %GOMVA xx yy ;Set cursor.
342: %GODLA xx yy ;Draw line from there. 342: %GODLA xx yy ;Draw line from there.
343: << repeat last two commands for each line >> 343: << repeat last two commands for each line >>
'yy' on a line without 'yyyy' found at line 342: 'yy' on a line without 'yyyy' found at line 342:
340: %GOCLR ;Clear the screen. 340: %GOCLR ;Clear the screen.
341: %GOMVA xx yy ;Set cursor. 341: %GOMVA xx yy ;Set cursor.
342: %GODLA xx yy ;Draw line from there. 342: %GODLA xx yy ;Draw line from there.
343: << repeat last two commands for each line >> 343: << repeat last two commands for each line >>
skipping to change at page 1, line 4080 skipping to change at page 1, line 4147
'yy' on a line without 'yyyy' found at line 342: 'yy' on a line without 'yyyy' found at line 342:
340: %GOCLR ;Clear the screen. 340: %GOCLR ;Clear the screen.
341: %GOMVA xx yy ;Set cursor. 341: %GOMVA xx yy ;Set cursor.
342: %GODLA xx yy ;Draw line from there. 342: %GODLA xx yy ;Draw line from there.
343: << repeat last two commands for each line >> 343: << repeat last two commands for each line >>
344: %TDNOP ;Exit graphics. 344: %TDNOP ;Exit graphics.
2000 found at line 859: 2000 found at line 859:
857: %TRGIN 0,,400000 terminal can provide graphics input. 857: %TRGIN 0,,400000 terminal can provide graphics input.
858: 858:
859: %TRGHC 0,,200000 terminal has a hard-copy device to which output can 859: %TRGHC 0,,200000 terminal has a hard-copy device to which outp
859(continued): ut can
860: be diverted. 860: be diverted.
861: 861:
+=+=+=+=+= File rfc0752.txt +=+=+=+=+= +=+=+=+=+= File rfc0752.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 218: 'yy' on a line without 'yyyy' found at line 218:
216: word 4 The name of the site in SIXBIT. 216: word 4 The name of the site in SIXBIT.
217: word 5 The user name who compiled the file, usually in SIXBIT. 217: word 5 The user name who compiled the file, usually in
217(continued): SIXBIT.
218: word 6 Date of compilation as SIXBIT YYMMDD. 218: word 6 Date of compilation as SIXBIT YYMMDD.
219: word 7 Time of compilation as SIXBIT HHMMSS. 219: word 7 Time of compilation as SIXBIT HHMMSS.
220: word 8 Address in file of NAME table. 220: word 8 Address in file of NAME table.
+=+=+=+=+= File rfc0754.txt +=+=+=+=+= +=+=+=+=+= File rfc0754.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 76: 'yy' on a line without 'yyyy' found at line 76:
74: 74:
75: Messages are transmitted as a character string to an address which is 75: Messages are transmitted as a character string to an address whi
76: specified "outside" the message. The destination host ("YYY") is 75(continued): ch is
77: specified to the sending (or user) FTP as the argument of the "open 76: specified "outside" the message. The destination host ("YYY") i
78: connection" command, and the destination user ("XXX") is specified to 76(continued): s
77: specified to the sending (or user) FTP as the argument of the "o
77(continued): pen
78: connection" command, and the destination user ("XXX") is specifi
78(continued): ed to
'yy' on a line without 'yyyy' found at line 81: 'yy' on a line without 'yyyy' found at line 81:
79: the receiving (or server) FTP as the argument of the "MAIL" (or "MLFL") 79: the receiving (or server) FTP as the argument of the "MAIL" (or
80: command. In Tenex, when mail is queued this outside information is 79(continued): "MLFL")
80: command. In Tenex, when mail is queued this outside information
80(continued): is
81: saved in the file name ("[---].XXX@YYY"). 81: saved in the file name ("[---].XXX@YYY").
82: 82:
83: The proposed solutions are briefly characterized. 83: The proposed solutions are briefly characterized.
'yy' on a line without 'yyyy' found at line 239: 'yy' on a line without 'yyyy' found at line 239:
237: 237:
238: 238:
239: "[---].XXX@YYY", not anything from the header. Only the string "XXX" 239: "[---].XXX@YYY", not anything from the header. Only the stri
239(continued): ng "XXX"
240: is passed to the FTP server. 240: is passed to the FTP server.
241: 241:
+=+=+=+=+= File rfc0759.txt +=+=+=+=+= +=+=+=+=+= File rfc0759.txt +=+=+=+=+=
two-digit found at line 1414: two-digit found at line 1414:
1412: yyyy-mm-dd-hh:mm:ss,fff+hh:mm 1412: yyyy-mm-dd-hh:mm:ss,fff+hh:mm
1413: 1413:
1414: Where yyyy is the four-digit year, mm is the two-digit month, dd is 1414: Where yyyy is the four-digit year, mm is the two-digit month
1415: the two-digit day, hh is the two-digit hour in 24 hour time, mm is 1414(continued): , dd is
1416: the two-digit minute, ss is the two-digit second, and fff is the 1415: the two-digit day, hh is the two-digit hour in 24 hour time,
1415(continued): mm is
1416: the two-digit minute, ss is the two-digit second, and fff is
1416(continued): the
two-digit found at line 1415: two-digit found at line 1415:
1413: 1413:
1414: Where yyyy is the four-digit year, mm is the two-digit month, dd is 1414: Where yyyy is the four-digit year, mm is the two-digit month
1415: the two-digit day, hh is the two-digit hour in 24 hour time, mm is 1414(continued): , dd is
1416: the two-digit minute, ss is the two-digit second, and fff is the 1415: the two-digit day, hh is the two-digit hour in 24 hour time,
1417: decimal fraction of the second. To this basic date and time is 1415(continued): mm is
1416: the two-digit minute, ss is the two-digit second, and fff is
1416(continued): the
1417: decimal fraction of the second. To this basic date and time
1417(continued): is
two-digit found at line 1416: two-digit found at line 1416:
1414: Where yyyy is the four-digit year, mm is the two-digit month, dd is 1414: Where yyyy is the four-digit year, mm is the two-digit month
1415: the two-digit day, hh is the two-digit hour in 24 hour time, mm is 1414(continued): , dd is
1416: the two-digit minute, ss is the two-digit second, and fff is the 1415: the two-digit day, hh is the two-digit hour in 24 hour time,
1417: decimal fraction of the second. To this basic date and time is 1415(continued): mm is
1418: appended the offset from Greenwich as plus or minus hh hours and mm 1416: the two-digit minute, ss is the two-digit second, and fff is
1416(continued): the
1417: decimal fraction of the second. To this basic date and time
1417(continued): is
1418: appended the offset from Greenwich as plus or minus hh hours
1418(continued): and mm
+=+=+=+=+= File rfc0767.txt +=+=+=+=+= +=+=+=+=+= File rfc0767.txt +=+=+=+=+=
two-digit found at line 710: two-digit found at line 710:
708: yyyy-mm-dd-hh:mm:ss,fff+hh:mm 708: yyyy-mm-dd-hh:mm:ss,fff+hh:mm
709: 709:
710: Where yyyy is the four-digit year, mm is the two-digit month, dd is
711: the two-digit day, hh is the two-digit hour in 24 hour time, mm is 710: Where yyyy is the four-digit year, mm is the two-digit month
712: the two-digit minute, ss is the two-digit second, and fff is the 710(continued): , dd is
711: the two-digit day, hh is the two-digit hour in 24 hour time,
711(continued): mm is
712: the two-digit minute, ss is the two-digit second, and fff is
712(continued): the
two-digit found at line 711: two-digit found at line 711:
709: 709:
710: Where yyyy is the four-digit year, mm is the two-digit month, dd is 710: Where yyyy is the four-digit year, mm is the two-digit month
711: the two-digit day, hh is the two-digit hour in 24 hour time, mm is 710(continued): , dd is
712: the two-digit minute, ss is the two-digit second, and fff is the 711: the two-digit day, hh is the two-digit hour in 24 hour time,
713: decimal fraction of the second. To this basic date and time is 711(continued): mm is
712: the two-digit minute, ss is the two-digit second, and fff is
712(continued): the
713: decimal fraction of the second. To this basic date and time
713(continued): is
two-digit found at line 712: two-digit found at line 712:
710: Where yyyy is the four-digit year, mm is the two-digit month, dd is 710: Where yyyy is the four-digit year, mm is the two-digit month
711: the two-digit day, hh is the two-digit hour in 24 hour time, mm is 710(continued): , dd is
712: the two-digit minute, ss is the two-digit second, and fff is the 711: the two-digit day, hh is the two-digit hour in 24 hour time,
713: decimal fraction of the second. To this basic date and time is 711(continued): mm is
714: appended the offset from Greenwich as plus or minus hh hours and mm 712: the two-digit minute, ss is the two-digit second, and fff is
712(continued): the
713: decimal fraction of the second. To this basic date and time
713(continued): is
714: appended the offset from Greenwich as plus or minus hh hours
714(continued): and mm
+=+=+=+=+= File rfc0786.txt +=+=+=+=+= +=+=+=+=+= File rfc0786.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 71: 'yy' on a line without 'yyyy' found at line 71:
69: 69:
70: The date-time will be in the default TOPS20 ODTIM format 70: The date-time will be in the default TOPS20 ODTIM forma
70(continued): t
71: "dd-mmm-yy hh:mm:ss" (24 hour time). 71: "dd-mmm-yy hh:mm:ss" (24 hour time).
72: 72:
73: The files will named "arbitrary.NIMAIL.-1", where "arbitrary" will 73: The files will named "arbitrary.NIMAIL.-1", where "arbitra
73(continued): ry" will
+=+=+=+=+= File rfc0788.txt +=+=+=+=+= +=+=+=+=+= File rfc0788.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 1592: 'yy' on a line without 'yyyy' found at line 1592:
1590: <daytime> ::= "at" <SP> <date> <SP> <time> 1590: <daytime> ::= "at" <SP> <date> <SP> <time>
1591: 1591:
1592: <date> ::= <dd> "-" <mon> "-" <yy> 1592: <date> ::= <dd> "-" <mon> "-" <yy>
1593: 1593:
1594: <time> ::= <hh> ":" <mm> ":" <ss> "-" <zone> 1594: <time> ::= <hh> ":" <mm> ":" <ss> "-" <zone>
'yy' on a line without 'yyyy' found at line 1602: 'yy' on a line without 'yyyy' found at line 1602:
1600: "JUL" | "AUG" | "SEP" | "OCT" | "NOV" | "DEC" 1600: "JUL" | "AUG" | "SEP" | "OCT" | "NOV" | "D
1600(continued): EC"
1601: 1601:
1602: <yy> ::= the two decimal integer year of the century in the 1602: <yy> ::= the two decimal integer year of the century
1602(continued): in the
1603: range 01 to 99. 1603: range 01 to 99.
1604: 1604:
century found at line 1602: century found at line 1602:
1600: "JUL" | "AUG" | "SEP" | "OCT" | "NOV" | "DEC" 1600: "JUL" | "AUG" | "SEP" | "OCT" | "NOV" | "D
1600(continued): EC"
1601: 1601:
1602: <yy> ::= the two decimal integer year of the century in the 1602: <yy> ::= the two decimal integer year of the century
1602(continued): in the
1603: range 01 to 99. 1603: range 01 to 99.
1604: 1604:
+=+=+=+=+= File rfc0809.txt +=+=+=+=+= +=+=+=+=+= File rfc0809.txt +=+=+=+=+=
2000 found at line 3349: 2000 found at line 3349:
3347: 3347:
3348: #define WID 0000000 /* Write Image Data */ 3348: #define WID 0000000 /* Write Image Data */
3349: #define WGD 0020000 /* Write Graphic Data */ 3349: #define WGD 0020000 /* Write Graphic Data */
3350: #define WAC 0022000 /* Write AlphanumCh */ 3350: #define WAC 0022000 /* Write AlphanumCh */
3351: 3351:
skipping to change at page 1, line 4243 skipping to change at page 1, line 4351
3407: #define DROPBYTE 0400 /* drop last byte */ 3407: #define DROPBYTE 0400 /* drop last byte */
3408: #define INTERR 02000 /* SPD - Interrupt Enable */ 3408: #define INTERR 02000 /* SPD - Interrupt Enable */
3409: #define TEST 04000 /* SPD - Diagnostic Test */ 3409: #define TEST 04000 /* SPD - Diagnostic Test */
3410: 3410:
+=+=+=+=+= File rfc0810.txt +=+=+=+=+= +=+=+=+=+= File rfc0810.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 146: 'yy' on a line without 'yyyy' found at line 146:
144: , (comma) is used as a data element delimiter 144: , (comma) is used as a data element delimiter
145: 145:
146: XXX/YYY indicates protocol information of the type 146: XXX/YYY indicates protocol information of the type
146(continued):
147: TRANSPORT/SERVICE. 147: TRANSPORT/SERVICE.
148: 148:
+=+=+=+=+= File rfc0820.txt +=+=+=+=+= +=+=+=+=+= File rfc0820.txt +=+=+=+=+=
2000 found at line 674: 2000 found at line 674:
672: 014.000.000.001 311031700035 00 PURDUE-TN [CXK] 672: 014.000.000.001 311031700035 00 PURDUE-TN
673: 014.000.000.002 311060800027 00 UWISC-TN [CXK] 672(continued): [CXK]
674: 014.000.000.003 311030200024 00 UDEL-TN [CXK] 673: 014.000.000.002 311060800027 00 UWISC-TN
675: 014.000.000.004 234219200149 23 UCL-VTEST [PK] 673(continued): [CXK]
676: 014.000.000.005 234219200300 23 UCL-TG [PK] 674: 014.000.000.003 311030200024 00 UDEL-TN
674(continued): [CXK]
675: 014.000.000.004 234219200149 23 UCL-VTEST
675(continued): [PK]
676: 014.000.000.005 234219200300 23 UCL-TG
676(continued): [PK]
+=+=+=+=+= File rfc0821.txt +=+=+=+=+= +=+=+=+=+= File rfc0821.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 1944: 'yy' on a line without 'yyyy' found at line 1944:
1942: <daytime> ::= <SP> <date> <SP> <time> 1942: <daytime> ::= <SP> <date> <SP> <time>
1943: 1943:
1944: <date> ::= <dd> <SP> <mon> <SP> <yy> 1944: <date> ::= <dd> <SP> <mon> <SP> <yy>
1945: 1945:
1946: <time> ::= <hh> ":" <mm> ":" <ss> <SP> <zone> 1946: <time> ::= <hh> ":" <mm> ":" <ss> <SP> <zone>
'yy' on a line without 'yyyy' found at line 1954: 'yy' on a line without 'yyyy' found at line 1954:
1952: "JUL" | "AUG" | "SEP" | "OCT" | "NOV" | "DEC" 1952: "JUL" | "AUG" | "SEP" | "OCT" | "NOV" | "D
1952(continued): EC"
1953: 1953:
1954: <yy> ::= the two decimal integer year of the century in the 1954: <yy> ::= the two decimal integer year of the century
1954(continued): in the
1955: range 00 to 99. 1955: range 00 to 99.
1956: 1956:
century found at line 1954: century found at line 1954:
1952: "JUL" | "AUG" | "SEP" | "OCT" | "NOV" | "DEC" 1952: "JUL" | "AUG" | "SEP" | "OCT" | "NOV" | "D
1952(continued): EC"
1953: 1953:
1954: <yy> ::= the two decimal integer year of the century in the 1954: <yy> ::= the two decimal integer year of the century
1954(continued): in the
1955: range 00 to 99. 1955: range 00 to 99.
1956: 1956:
+=+=+=+=+= File rfc0822.txt +=+=+=+=+= +=+=+=+=+= File rfc0822.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 1635: 'yy' on a line without 'yyyy' found at line 1635:
1633: 5.1. SYNTAX 1633: 5.1. SYNTAX
1634: 1634:
1635: date-time = [ day "," ] date time ; dd mm yy 1635: date-time = [ day "," ] date time ; dd mm yy
1636: ; hh:mm:ss zzz 1636: ; hh:mm:ss zzz
1636(continued):
1637: 1637:
'yy' on a line without 'yyyy' found at line 2701: 'yy' on a line without 'yyyy' found at line 2701:
2699: dates = orig-date ; Original 2699: dates = orig-date ; Original
2700: [ resent-date ] ; Forwarded 2700: [ resent-date ] ; Forwarded
2701: date-time = [ day "," ] date time ; dd mm yy 2701: date-time = [ day "," ] date time ; dd mm yy
2702: ; hh:mm:ss zzz 2702: ; hh:mm:ss zzz
2702(continued):
2703: day = "Mon" / "Tue" / "Wed" / "Thu" 2703: day = "Mon" / "Tue" / "Wed" / "Thu"
2-digit found at line 344: 2-digit found at line 344:
342: 342:
343: "<n>(element)" is equivalent to "<n>*<n>(element)"; that is, 343: "<n>(element)" is equivalent to "<n>*<n>(element)"; th
344: exactly <n> occurrences of (element). Thus 2DIGIT is a 2-digit 343(continued): at is,
345: number, and 3ALPHA is a string of three alphabetic characters. 344: exactly <n> occurrences of (element). Thus 2DIGIT is a 2
344(continued): -digit
345: number, and 3ALPHA is a string of three alphabetic characte
345(continued): rs.
346: 346:
2digit found at line 344: 2digit found at line 344:
342: 342:
343: "<n>(element)" is equivalent to "<n>*<n>(element)"; that is, 343: "<n>(element)" is equivalent to "<n>*<n>(element)"; th
344: exactly <n> occurrences of (element). Thus 2DIGIT is a 2-digit 343(continued): at is,
345: number, and 3ALPHA is a string of three alphabetic characters. 344: exactly <n> occurrences of (element). Thus 2DIGIT is a 2
344(continued): -digit
345: number, and 3ALPHA is a string of three alphabetic characte
345(continued): rs.
346: 346:
2digit found at line 1641: 2digit found at line 1641:
1639: / "Fri" / "Sat" / "Sun" 1639: / "Fri" / "Sat" / "Sun"
1640: 1640:
1641: date = 1*2DIGIT month 2DIGIT ; day month year 1641: date = 1*2DIGIT month 2DIGIT ; day month yea
1642: ; e.g. 20 Jun 82 1641(continued): r
1642: ; e.g. 20 Jun
1642(continued): 82
1643: 1643:
2digit found at line 1650: 2digit found at line 1650:
1648: time = hour zone ; ANSI and Military 1648: time = hour zone ; ANSI and Mili
1648(continued): tary
1649: 1649:
1650: hour = 2DIGIT ":" 2DIGIT [":" 2DIGIT] 1650: hour = 2DIGIT ":" 2DIGIT [":" 2DIGIT]
1651: ; 00:00:00 - 23:59:59 1651: ; 00:00:00 - 23
1651(continued): :59:59
1652: 1652:
2digit found at line 2697: 2digit found at line 2697:
2695: CTL = <any ASCII control ; ( 0- 37, 0.- 31.) 2695: CTL = <any ASCII control ; ( 0- 37, 0.
2696: character and DEL> ; ( 177, 127.) 2695(continued): - 31.)
2697: date = 1*2DIGIT month 2DIGIT ; day month year 2696: character and DEL> ; ( 177,
2698: ; e.g. 20 Jun 82 2696(continued): 127.)
2697: date = 1*2DIGIT month 2DIGIT ; day month yea
2697(continued): r
2698: ; e.g. 20 Jun
2698(continued): 82
2699: dates = orig-date ; Original 2699: dates = orig-date ; Original
2digit found at line 2747: 2digit found at line 2747:
2745: field-name = 1*<any CHAR, excluding CTLs, SPACE, and ":"> 2745: field-name = 1*<any CHAR, excluding CTLs, SPACE, and ":">
2745(continued):
2746: group = phrase ":" [#mailbox] ";" 2746: group = phrase ":" [#mailbox] ";"
2747: hour = 2DIGIT ":" 2DIGIT [":" 2DIGIT] 2747: hour = 2DIGIT ":" 2DIGIT [":" 2DIGIT]
2748: ; 00:00:00 - 23:59:59 2748: ; 00:00:00 - 23
2749: HTAB = <ASCII HT, horizontal-tab> ; ( 11, 9.) 2748(continued): :59:59
2749: HTAB = <ASCII HT, horizontal-tab> ; ( 11,
2749(continued): 9.)
+=+=+=+=+= File rfc0850.txt +=+=+=+=+= +=+=+=+=+= File rfc0850.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 227: 'yy' on a line without 'yyyy' found at line 227:
225: network. One format that is acceptable to both is 225: network. One format that is acceptable to both is
226: 226:
227: Weekday, DD-Mon-YY HH:MM:SS TIMEZONE 227: Weekday, DD-Mon-YY HH:MM:SS TIMEZONE
228: 228:
229: Several examples of valid dates appear in the sample 229: Several examples of valid dates appear in the sample
+=+=+=+=+= File rfc0867.txt +=+=+=+=+= +=+=+=+=+= File rfc0867.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 67: 'yy' on a line without 'yyyy' found at line 67:
65: Another popular syntax is that used in SMTP: 65: Another popular syntax is that used in SMTP:
66: 66:
67: dd mmm yy hh:mm:ss zzz 67: dd mmm yy hh:mm:ss zzz
68: 68:
69: Example: 69: Example:
+=+=+=+=+= File rfc0868.txt +=+=+=+=+= +=+=+=+=+= File rfc0868.txt +=+=+=+=+=
1900 found at line 19: 1900 found at line 19:
17: This protocol provides a site-independent, machine readable date and 17: This protocol provides a site-independent, machine readable date
18: time. The Time service sends back to the originating source the time in 17(continued): and
18: time. The Time service sends back to the originating source the
18(continued): time in
19: seconds since midnight on January first 1900. 19: seconds since midnight on January first 1900.
20: 20:
21: One motivation arises from the fact that not all systems have a 21: One motivation arises from the fact that not all systems have a
1900 found at line 83: 1900 found at line 83:
81: The Time 81: The Time
82: 82:
83: The time is the number of seconds since 00:00 (midnight) 1 January 1900 83: The time is the number of seconds since 00:00 (midnight) 1 Janua
84: GMT, such that the time 1 is 12:00:01 am on 1 January 1900 GMT; this 83(continued): ry 1900
84: GMT, such that the time 1 is 12:00:01 am on 1 January 1900 GMT;
84(continued): this
85: base will serve until the year 2036. 85: base will serve until the year 2036.
1900 found at line 84: 1900 found at line 84:
82: 82:
83: The time is the number of seconds since 00:00 (midnight) 1 January 1900 83: The time is the number of seconds since 00:00 (midnight) 1 Janua
84: GMT, such that the time 1 is 12:00:01 am on 1 January 1900 GMT; this 83(continued): ry 1900
84: GMT, such that the time 1 is 12:00:01 am on 1 January 1900 GMT;
84(continued): this
85: base will serve until the year 2036. 85: base will serve until the year 2036.
86: 86:
+=+=+=+=+= File rfc0869.txt +=+=+=+=+= +=+=+=+=+= File rfc0869.txt +=+=+=+=+=
2000 found at line 1639: 2000 found at line 1639:
1637: 400 HDH 1637: 400 HDH
1638: 1000 Cassette Writer 1638: 1000 Cassette Writer
1639: 2000 Propagation Delay Measurement 1639: 2000 Propagation Delay Measurement
1640: 4000 X25 1640: 4000 X25
1641: 10000 Profile Measurements 1641: 10000 Profile Measurements
skipping to change at page 1, line 4410 skipping to change at page 1, line 4554
+=+=+=+=+= File rfc0884.txt +=+=+=+=+= +=+=+=+=+= File rfc0884.txt +=+=+=+=+=
2000 found at line 236: 2000 found at line 236:
234: GENERAL-TERMINAL-100A 234: GENERAL-TERMINAL-100A
235: HAZELTINE-1500 235: HAZELTINE-1500
236: HAZELTINE-2000 236: HAZELTINE-2000
237: HP-2621 237: HP-2621
238: HP-2640A 238: HP-2640A
+=+=+=+=+= File rfc0899.txt +=+=+=+=+= +=+=+=+=+= File rfc0899.txt +=+=+=+=+=
1900 found at line 337: 1900 found at line 337:
335: provides a site-independent, machine readable date and time. The 335: provides a site-independent, machine readable date and time.
336: Time service sends back to the originating source the time in seconds 335(continued): The
336: Time service sends back to the originating source the time in
336(continued): seconds
337: since midnight on January first 1900. 337: since midnight on January first 1900.
338: 338:
339: 867 Postel May 83 Daytime Protocol 339: 867 Postel May 83 Daytime Protocol
+=+=+=+=+= File rfc0900.txt +=+=+=+=+= +=+=+=+=+= File rfc0900.txt +=+=+=+=+=
2000 found at line 1595: 2000 found at line 1595:
1593: HAZELTINE-1510 1593: HAZELTINE-1510
1594: HAZELTINE-1520 1594: HAZELTINE-1520
1595: HAZELTINE-2000 1595: HAZELTINE-2000
1596: HP-2621 1596: HP-2621
1597: HP-2621A 1597: HP-2621A
+=+=+=+=+= File rfc0909.txt +=+=+=+=+= +=+=+=+=+= File rfc0909.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 859: 'yy' on a line without 'yyyy' found at line 859:
857: responses from the target. A session begins when a host opens a 857: responses from the target. A session begins when a host op
858: transport connection to a target listening on a well known port. 857(continued): ens a
859: LDP uses RDP port number zzz or TCP port number yyy. When the 858: transport connection to a target listening on a well known
860: connection has been established, the host sends a HELLO command, 858(continued): port.
861: and the target replies with a HELLO_REPLY. The HELLO_REPLY 859: LDP uses RDP port number zzz or TCP port number yyy. Whe
859(continued): n the
860: connection has been established, the host sends a HELLO co
860(continued): mmand,
861: and the target replies with a HELLO_REPLY. The HELLO
861(continued): _REPLY
+=+=+=+=+= File rfc0923.txt +=+=+=+=+= +=+=+=+=+= File rfc0923.txt +=+=+=+=+=
2000 found at line 1769: 2000 found at line 1769:
1767: HAZELTINE-1510 1767: HAZELTINE-1510
1768: HAZELTINE-1520 1768: HAZELTINE-1520
1769: HAZELTINE-2000 1769: HAZELTINE-2000
1770: HP-2621 1770: HP-2621
1771: HP-2621A 1771: HP-2621A
+=+=+=+=+= File rfc0937.txt +=+=+=+=+= +=+=+=+=+= File rfc0937.txt +=+=+=+=+=
skipping to change at page 1, line 4467 skipping to change at page 1, line 4618
'yy' on a line without 'yyyy' found at line 159: 'yy' on a line without 'yyyy' found at line 159:
157: ,(comma) is used as a data element delimiter 157: ,(comma) is used as a data element delimiter
158: 158:
159: XXX/YYY indicates protocol information of the type 159: XXX/YYY indicates protocol information of the type
160: TRANSPORT/SERVICE. 160: TRANSPORT/SERVICE.
161: 161:
+=+=+=+=+= File rfc0956.txt +=+=+=+=+= +=+=+=+=+= File rfc0956.txt +=+=+=+=+=
1900 found at line 748: 1900 found at line 748:
746: 746:
747: 3. The data format should be based on the UDP Time format, which 747: 3. The data format should be based on the UDP Time format
748: specifies 32-bit time in seconds since 1 January 1900, but 747(continued): , which
749: extended additional bits for the fractional part of a second. 748: specifies 32-bit time in seconds since 1 January 1900,
748(continued): but
749: extended additional bits for the fractional part of a
749(continued): second.
750: 750:
1900 found at line 826: 1900 found at line 826:
824: experiment the results indicated by UDP and ICMP are compared. In 824: experiment the results indicated by UDP and ICMP are compared
825: the UDP Time protocol time is indicated as a 32-bit field in seconds 824(continued): . In
826: past 0000 UT on 1 January 1900, while in the ICMP Timestamp message 825: the UDP Time protocol time is indicated as a 32-bit field in
827: time is indicated as a 32-bit field in milliseconds past 0000 UT of 825(continued): seconds
826: past 0000 UT on 1 January 1900, while in the ICMP Timestamp m
826(continued): essage
827: time is indicated as a 32-bit field in milliseconds past 0000
827(continued): UT of
828: each day. 828: each day.
2000 found at line 1392: 2000 found at line 1392:
1390: CU-ARPA.CS.CORNELL.EDU -1 -514 1390: CU-ARPA.CS.CORNELL.EDU -1 -514
1391: UCI-ICSE.ARPA -1 -1896 1391: UCI-ICSE.ARPA -1 -1896
1392: UCI-ICSC.ARPA 1 2000 1392: UCI-ICSC.ARPA 1 2000
1393: DCN9.ARPA -7 -6610 1393: DCN9.ARPA -7 -6610
1394: TRANTOR.ARPA 10 10232 1394: TRANTOR.ARPA 10 10232
+=+=+=+=+= File rfc0958.txt +=+=+=+=+= +=+=+=+=+= File rfc0958.txt +=+=+=+=+=
century found at line 41: century found at line 41:
39: NTP provides the protocol mechanisms to synchronize time in principle 39: NTP provides the protocol mechanisms to synchronize time in p
39(continued): rinciple
40: to precisions in the order of nanoseconds while preserving a 40: to precisions in the order of nanoseconds while preserving a
41: non-ambiguous date, at least for this century. The protocol includes 41: non-ambiguous date, at least for this century. The protocol
42: provisions to specify the precision and estimated error of the local 41(continued): includes
43: clock and the characteristics of the reference clock to which it may 42: provisions to specify the precision and estimated error of th
42(continued): e local
43: clock and the characteristics of the reference clock to which
43(continued): it may
1900 found at line 143: 1900 found at line 143:
141: 141:
142: NTP timestamps are represented as a 64-bit fixed-point number, in 142: NTP timestamps are represented as a 64-bit fixed-point number
143: seconds relative to 0000 UT on 1 January 1900. The integer part is 142(continued): , in
144: in the first 32 bits and the fraction part in the last 32 bits, as 143: seconds relative to 0000 UT on 1 January 1900. The integer p
143(continued): art is
144: in the first 32 bits and the fraction part in the last 32 bit
144(continued): s, as
145: shown in the following diagram. 145: shown in the following diagram.
+=+=+=+=+= File rfc0960.txt +=+=+=+=+= +=+=+=+=+= File rfc0960.txt +=+=+=+=+=
2000 found at line 1659: 2000 found at line 1659:
1657: 014.000.000.018 2624-522-80900 52 DFVLR5-X25 [HDC1] 1657: 014.000.000.018 2624-522-80900 52 DFVLR5-X25
1658: 014.000.000.019 2041-170-10000 00 SHAPE-X25 [JFW] 1657(continued): [HDC1]
1659: 014.000.000.020 5052-737-20000 50 UQNET [AXH] 1658: 014.000.000.019 2041-170-10000 00 SHAPE-X25
1660: 014.000.000.021 3020-801-00057 50 DMC-CRC1 [JR17] 1658(continued): [JFW]
1661: 014.000.000.022-014.255.255.254 Unassigned [JBP] 1659: 014.000.000.020 5052-737-20000 50 UQNET
1659(continued): [AXH]
1660: 014.000.000.021 3020-801-00057 50 DMC-CRC1
1660(continued): [JR17]
1661: 014.000.000.022-014.255.255.254 Unassigned
1661(continued): [JBP]
2000 found at line 1984: 2000 found at line 1984:
1982: AEGIS 1982: AEGIS
1983: APOLLO 1983: APOLLO
1984: BS-2000 1984: BS-2000
1985: CEDAR 1985: CEDAR
1986: CGW 1986: CGW
2000 found at line 2350: 2000 found at line 2350:
2348: HAZELTINE-1510 2348: HAZELTINE-1510
skipping to change at page 1, line 4584 skipping to change at page 1, line 4755
386: 5000 SOA <SOA information> 386: 5000 SOA <SOA information>
387: Q.ISI.EDU. 2000 A <address of Q.ISI.EDU.> 387: Q.ISI.EDU. 2000 A <address of Q.ISI.EDU.>
388: XX.MIT.EDU. 2000 A <address of XX.MIT.EDU.> 388: XX.MIT.EDU. 2000 A <address of XX.MIT.EDU.>
389: 389:
390: SOA serials 390: SOA serials
+=+=+=+=+= File rfc0977.txt +=+=+=+=+= +=+=+=+=+= File rfc0977.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 814: 'yy' on a line without 'yyyy' found at line 814:
812: the same format as the LIST command. 812: the same format as the LIST command.
813: 813:
814: The date is sent as 6 digits in the format YYMMDD, where YY is the 814: The date is sent as 6 digits in the format YYMMDD, where YY i
815: last two digits of the year, MM is the two digits of the month (with 814(continued): s the
816: leading zero, if appropriate), and DD is the day of the month (with 815: last two digits of the year, MM is the two digits of the mont
815(continued): h (with
816: leading zero, if appropriate), and DD is the day of the month
816(continued): (with
century found at line 817: century found at line 817:
815: last two digits of the year, MM is the two digits of the month (with 815: last two digits of the year, MM is the two digits of the mont
816: leading zero, if appropriate), and DD is the day of the month (with 815(continued): h (with
817: leading zero, if appropriate). The closest century is assumed as 816: leading zero, if appropriate), and DD is the day of the month
818: part of the year (i.e., 86 specifies 1986, 30 specifies 2030, 99 is 816(continued): (with
817: leading zero, if appropriate). The closest century is assume
817(continued): d as
818: part of the year (i.e., 86 specifies 1986, 30 specifies 2030,
818(continued): 99 is
819: 1999, 00 is 2000). 819: 1999, 00 is 2000).
2000 found at line 819: 2000 found at line 819:
817: leading zero, if appropriate). The closest century is assumed as 817: leading zero, if appropriate). The closest century is assume
818: part of the year (i.e., 86 specifies 1986, 30 specifies 2030, 99 is 817(continued): d as
818: part of the year (i.e., 86 specifies 1986, 30 specifies 2030,
818(continued): 99 is
819: 1999, 00 is 2000). 819: 1999, 00 is 2000).
820: 820:
821: Time must also be specified. It must be as 6 digits HHMMSS with HH 821: Time must also be specified. It must be as 6 digits HHMMSS w
821(continued): ith HH
2000 found at line 1190: 2000 found at line 1190:
1188: 1188:
1189: (client asks for new newsgroups since April 3, 1985) 1189: (client asks for new newsgroups since April 3, 1985)
1190: C: NEWGROUPS 850403 020000 1190: C: NEWGROUPS 850403 020000
1191: 1191:
1192: S: 231 New newsgroups since 03/04/85 02:00:00 follow 1192: S: 231 New newsgroups since 03/04/85 02:00:00 follow
2000 found at line 1275: 2000 found at line 1275:
1273: 1273:
skipping to change at page 1, line 4632 skipping to change at page 1, line 4813
2000 found at line 1283: 2000 found at line 1283:
1281: (client asks for new news articles since 2 am, May 15, 1985) 1281: (client asks for new news articles since 2 am, May 15, 1985)
1282: C: NEWNEWS * 850515 020000 1282: C: NEWNEWS * 850515 020000
1283: S: 230 New news since 850515 020000 follows 1283: S: 230 New news since 850515 020000 follows
1284: S: <1772@foo.UUCP> 1284: S: <1772@foo.UUCP>
1285: S: <87623@baz.UUCP> 1285: S: <87623@baz.UUCP>
+=+=+=+=+= File rfc0985.txt +=+=+=+=+= +=+=+=+=+= File rfc0985.txt +=+=+=+=+=
2000 found at line 505: 2000 found at line 505:
503: Very Distant Host (VDH) methods are not recommended for new 503: Very Distant Host (VDH) methods are not recommended for ne
504: implementations. The Distant Host (DH) method is used when the 503(continued): w
505: host and IMP are separated by not more than about 2000 feet of 504: implementations. The Distant Host (DH) method is used whe
506: cable, while the HDLC Distant Host is used for greater distances 504(continued): n the
507: where a modem is required. Retransmission, resequencing and flow 505: host and IMP are separated by not more than about 2000 fee
505(continued): t of
506: cable, while the HDLC Distant Host is used for greater dis
506(continued): tances
507: where a modem is required. Retransmission, resequencing a
507(continued): nd flow
+=+=+=+=+= File rfc0987.txt +=+=+=+=+= +=+=+=+=+= File rfc0987.txt +=+=+=+=+=
UTCTime found at line 1100: UTCTime found at line 1100:
1098: X.408 (sections 4.2.2 and 5.2.2). 1098: X.408 (sections 4.2.2 and 5.2.2).
1099: 1099:
1100: 3.3.5. UTCTime 1100: 3.3.5. UTCTime
1101: 1101:
1102: Both UTCTime and the RFC 822 822.date-time syntax contain: Year 1102: Both UTCTime and the RFC 822 822.date-time syntax conta
1102(continued): in: Year
UTCTime found at line 1102: UTCTime found at line 1102:
1100: 3.3.5. UTCTime 1100: 3.3.5. UTCTime
1101: 1101:
1102: Both UTCTime and the RFC 822 822.date-time syntax contain: Year 1102: Both UTCTime and the RFC 822 822.date-time syntax conta
1103: (lowest two digits), Month, Day of Month, hour, minute, second 1102(continued): in: Year
1104: (optional), and Timezone. 822.date-time also contains an 1103: (lowest two digits), Month, Day of Month, hour, minute,
1103(continued): second
1104: (optional), and Timezone. 822.date-time also contains
1104(continued): an
UTCTime found at line 1107: UTCTime found at line 1107:
1105: optional day of the week, but this is redundant. Therefore a 1105: optional day of the week, but this is redundant. There
1106: symmetrical mapping can be made between these constructs <5>. 1105(continued): fore a
1107: The UTCTime format which specifies the timezone offset should 1106: symmetrical mapping can be made between these construct
1106(continued): s <5>.
1107: The UTCTime format which specifies the timezone offset
1107(continued): should
1108: be used, in line with CEN/CENELEC recommendations. 1108: be used, in line with CEN/CENELEC recommendations.
1109: 1109:
UTCTime found at line 3395: UTCTime found at line 3395:
3393: 3393:
3394: The extended syntax of zone defined in the JNT Mail Protocol
3395: should be used in the mapping of UTCTime defined in chapter 3. 3394: The extended syntax of zone defined in the JNT Mail Protoc
3394(continued): ol
3395: should be used in the mapping of UTCTime defined in chapte
3395(continued): r 3.
3396: 3396:
3397: 5. Lack of separate 822-P1 originator specification 3397: 5. Lack of separate 822-P1 originator specification
UTCTime found at line 3910: UTCTime found at line 3910:
3908: <5> In practice, a gateway will need to parse various illegal 3908: <5> In practice, a gateway will need to parse various illega
3909: variants on 822.date-time. In cases where 822.date-time cannot 3908(continued): l
3910: be parsed, it is recommended that the derived UTCTime is set to 3909: variants on 822.date-time. In cases where 822.date-time
3909(continued): cannot
3910: be parsed, it is recommended that the derived UTCTime is
3910(continued): set to
3911: the value at the time of translation. 3911: the value at the time of translation.
3912: 3912:
2digit found at line 2785: 2digit found at line 2785:
2783: last-trace ";" 2783: last-trace ";"
2784: "ext" 1*DIGIT 2784: "ext" 1*DIGIT
2785: "flags" 2DIGIT 2785: "flags" 2DIGIT
2786: [ "intended" mailbox ] ";" 2786: [ "intended" mailbox ] ";"
2787: [ "info" printablestring ] 2787: [ "info" printablestring ]
+=+=+=+=+= File rfc0990.txt +=+=+=+=+= +=+=+=+=+= File rfc0990.txt +=+=+=+=+=
2000 found at line 2265: 2000 found at line 2265:
2263: 014.000.000.018 2624-522-80900 52 DFVLR5-X25 [GB7] 2263: 014.000.000.018 2624-522-80900 52 DFVLR5-X25
2264: 014.000.000.019 2041-170-10000 00 SHAPE-X25 [JFW] 2263(continued): [GB7]
2265: 014.000.000.020 5052-737-20000 50 UQNET [AXH] 2264: 014.000.000.019 2041-170-10000 00 SHAPE-X25
2266: 014.000.000.021 3020-801-00057 50 DMC-CRC1 [JR17] 2264(continued): [JFW]
2267: 014.000.000.022 2624-522-80902 77 DFVLRVAX-X25 [GB7] 2265: 014.000.000.020 5052-737-20000 50 UQNET
2265(continued): [AXH]
2266: 014.000.000.021 3020-801-00057 50 DMC-CRC1
2266(continued): [JR17]
2267: 014.000.000.022 2624-522-80902 77 DFVLRVAX-X25
2267(continued): [GB7]
2000 found at line 2584: 2000 found at line 2584:
2582: AEGIS 2582: AEGIS
2583: APOLLO 2583: APOLLO
2584: BS-2000 2584: BS-2000
2585: CEDAR 2585: CEDAR
2586: CGW 2586: CGW
2000 found at line 2945: 2000 found at line 2945:
2943: HAZELTINE-1510 2943: HAZELTINE-1510
skipping to change at page 1, line 4713 skipping to change at page 1, line 4917
+=+=+=+=+= File rfc0996.txt +=+=+=+=+= +=+=+=+=+= File rfc0996.txt +=+=+=+=+=
2000 found at line 76: 2000 found at line 76:
74: 74:
75: Process type: 000027 options: 040000 75: Process type: 000027 options: 040000
76: Subnet: DMV status: 376 hello: 15 timeout: 2000 76: Subnet: DMV status: 376 hello: 15 timeout: 2000
77: Foreign address: [192.5.39.87] max size: 576 77: Foreign address: [192.5.39.87] max size: 576
78: Input packets 3645 Output packets 3690 78: Input packets 3645 Output packets 3690
+=+=+=+=+= File rfc1000.txt +=+=+=+=+= +=+=+=+=+= File rfc1000.txt +=+=+=+=+=
1900 found at line 3105: 1900 found at line 3105:
3103: protocol provides a site-independent, machine readable date and 3103: protocol provides a site-independent, machine readable dat
3104: time. The Time service sends back to the originating source the 3103(continued): e and
3104: time. The Time service sends back to the originating sour
3104(continued): ce the
3105: time in seconds since midnight on January first 1900. 3105: time in seconds since midnight on January first 1900.
3106: 3106:
3107: 867 Postel May 83 Daytime Protocol 3107: 867 Postel May 83 Daytime Protocol
+=+=+=+=+= File rfc1009.txt +=+=+=+=+= +=+=+=+=+= File rfc1009.txt +=+=+=+=+=
2000 found at line 1412: 2000 found at line 1412:
1410: method is used when the host and IMP (the Defense Communication 1410: method is used when the host and IMP (the Defense Communic
1411: Agency calls it a Packet Switch Node or PSN) are separated by not 1410(continued): ation
1412: more than about 2000 feet of cable, while the HDLC Distant Host 1411: Agency calls it a Packet Switch Node or PSN) are separated
1413: (HDH) is used for greater distances where a modem is required. 1411(continued): by not
1414: Under HDH, retransmission, resequencing and flow control are 1412: more than about 2000 feet of cable, while the HDLC Distant
1412(continued): Host
1413: (HDH) is used for greater distances where a modem is requi
1413(continued): red.
1414: Under HDH, retransmission, resequencing and flow control a
1414(continued): re
+=+=+=+=+= File rfc1010.txt +=+=+=+=+= +=+=+=+=+= File rfc1010.txt +=+=+=+=+=
2000 found at line 969: 2000 found at line 969:
967: 014.000.000.018 2624-522-80900 52 DFVLR5-X25 [GB7] 967: 014.000.000.018 2624-522-80900 52 DFVLR5-X25
968: 014.000.000.019 2041-170-10000 00 SHAPE-X25 [JFW] 967(continued): [GB7]
969: 014.000.000.020 5052-737-20000 50 UQNET [AXH] 968: 014.000.000.019 2041-170-10000 00 SHAPE-X25
970: 014.000.000.021 3020-801-00057 50 DMC-CRC1 [JR17] 968(continued): [JFW]
971: 014.000.000.022 2624-522-80902 77 DFVLRVAX-X25 [GB7] 969: 014.000.000.020 5052-737-20000 50 UQNET
969(continued): [AXH]
970: 014.000.000.021 3020-801-00057 50 DMC-CRC1
970(continued): [JR17]
971: 014.000.000.022 2624-522-80902 77 DFVLRVAX-X25
971(continued): [GB7]
2000 found at line 1353: 2000 found at line 1353:
1351: AEGIS 1351: AEGIS
1352: APOLLO 1352: APOLLO
1353: BS-2000 1353: BS-2000
1354: CEDAR 1354: CEDAR
1355: CGW 1355: CGW
2000 found at line 1719: 2000 found at line 1719:
1717: HAZELTINE-1510 1717: HAZELTINE-1510
1718: HAZELTINE-1520 1718: HAZELTINE-1520
1719: HAZELTINE-2000 1719: HAZELTINE-2000
skipping to change at page 1, line 4752 skipping to change at page 1, line 4969
2000 found at line 1719: 2000 found at line 1719:
1717: HAZELTINE-1510 1717: HAZELTINE-1510
1718: HAZELTINE-1520 1718: HAZELTINE-1520
1719: HAZELTINE-2000 1719: HAZELTINE-2000
1720: HP-2621 1720: HP-2621
1721: HP-2621A 1721: HP-2621A
+=+=+=+=+= File rfc1024.txt +=+=+=+=+= +=+=+=+=+= File rfc1024.txt +=+=+=+=+=
1900 found at line 535: 1900 found at line 535:
533: 533:
534: The local system clock, measured in milliseconds since 00:00 1 534: The local system clock, measured in milliseconds since 00:00
535: January 1900 UTC. Assumed to be only a local estimate of the time. 534(continued): 1
536: The value 0 is reserved for an uninitialized clock (For example, an 535: January 1900 UTC. Assumed to be only a local estimate of the
535(continued): time.
536: The value 0 is reserved for an uninitialized clock (For examp
536(continued): le, an
537: uninitialized time-of-day chip.) 537: uninitialized time-of-day chip.)
1900 found at line 546: 1900 found at line 546:
544: A network synchronized clock, which is assumed to be synchronized 544: A network synchronized clock, which is assumed to be synchron
545: across some part of a network. The clock value is measured in 544(continued): ized
546: milliseconds since 00:00 1 January 1900 UTC. Specific information 545: across some part of a network. The clock value is measured i
547: about the synchronization protocol is found in the system variable 545(continued): n
548: dictionary. The value 0 is used to indicate an uninitialized clock. 546: milliseconds since 00:00 1 January 1900 UTC. Specific inform
546(continued): ation
547: about the synchronization protocol is found in the system var
547(continued): iable
548: dictionary. The value 0 is used to indicate an uninitialized
548(continued): clock.
+=+=+=+=+= File rfc1036.txt +=+=+=+=+= +=+=+=+=+= File rfc1036.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 196: 'yy' on a line without 'yyyy' found at line 196:
194: both is: 194: both is:
195: 195:
196: Wdy, DD Mon YY HH:MM:SS TIMEZONE 196: Wdy, DD Mon YY HH:MM:SS TIMEZONE
197: 197:
198: Several examples of valid dates appear in the sample message above. 198: Several examples of valid dates appear in the sample message
198(continued): above.
+=+=+=+=+= File rfc1037.txt +=+=+=+=+= +=+=+=+=+= File rfc1037.txt +=+=+=+=+=
1900 found at line 541: 1900 found at line 541:
539: Date A numeric data token. The date is expressed in 539: Date A numeric data token. The date is expre
540: Universal Time format, which measures a time as 539(continued): ssed in
541: the number of seconds since January 1, 1900, at 540: Universal Time format, which measures a
540(continued): time as
541: the number of seconds since January 1, 1
541(continued): 900, at
542: midnight GMT. 542: midnight GMT.
543: 543:
1900 found at line 2544: 1900 found at line 2544:
2542: The creation date of the file. The date is expressed in Universal 2542: The creation date of the file. The date is expressed in Univ
2543: Time format, which measures a time as the number of seconds since 2542(continued): ersal
2544: January 1, 1900, at midnight GMT. Creation date does not necessarily 2543: Time format, which measures a time as the number of seconds s
2545: mean the time the file system created the directory entry or records 2543(continued): ince
2546: of the file. For systems that support modification or appending to 2544: January 1, 1900, at midnight GMT. Creation date does not nec
2544(continued): essarily
2545: mean the time the file system created the directory entry or
2545(continued): records
2546: of the file. For systems that support modification or append
2546(continued): ing to
+=+=+=+=+= File rfc1038.txt +=+=+=+=+= +=+=+=+=+= File rfc1038.txt +=+=+=+=+=
2000 found at line 317: 2000 found at line 317:
315: 315:
316: The values of this field are assigned by DCA Code R130, Washington, 316: The values of this field are assigned by DCA Code R130, Washi
317: D.C. 20305-2000. Each value corresponds to a requestor who, once 316(continued): ngton,
318: assigned, becomes the authority for the remainder of the option 317: D.C. 20305-2000. Each value corresponds to a requestor who,
317(continued): once
318: assigned, becomes the authority for the remainder of the opti
318(continued): on
319: definition for that value. 319: definition for that value.
+=+=+=+=+= File rfc1050.txt +=+=+=+=+= +=+=+=+=+= File rfc1050.txt +=+=+=+=+=
2000 found at line 323: 2000 found at line 323:
321: 7.3 Program Number Assignment 321: 7.3 Program Number Assignment
322: 322:
323: Program numbers are given out in groups of hexadecimal 20000000 323: Program numbers are given out in groups of hexadecimal 200000
323(continued): 00
324: (decimal 536870912) according to the following chart: 324: (decimal 536870912) according to the following chart:
325: 325:
2000 found at line 327: 2000 found at line 327:
325: 325:
326: 0 - 1fffffff defined by Sun 326: 0 - 1fffffff defined by Sun
327: 20000000 - 3fffffff defined by user 327: 20000000 - 3fffffff defined by user
328: 40000000 - 5fffffff transient 328: 40000000 - 5fffffff transient
329: 60000000 - 7fffffff reserved 329: 60000000 - 7fffffff reserved
+=+=+=+=+= File rfc1057.txt +=+=+=+=+= +=+=+=+=+= File rfc1057.txt +=+=+=+=+=
2000 found at line 339: 2000 found at line 339:
337: 7.3 Program Number Assignment 337: 7.3 Program Number Assignment
338: 338:
339: Program numbers are given out in groups of hexadecimal 20000000 339: Program numbers are given out in groups of hexadecimal 200000
339(continued): 00
340: (decimal 536870912) according to the following chart: 340: (decimal 536870912) according to the following chart:
341: 341:
2000 found at line 343: 2000 found at line 343:
341: 341:
342: 0 - 1fffffff defined by Sun 342: 0 - 1fffffff defined by Sun
343: 20000000 - 3fffffff defined by user 343: 20000000 - 3fffffff defined by user
344: 40000000 - 5fffffff transient 344: 40000000 - 5fffffff transient
345: 60000000 - 7fffffff reserved 345: 60000000 - 7fffffff reserved
+=+=+=+=+= File rfc1059.txt +=+=+=+=+= +=+=+=+=+= File rfc1059.txt +=+=+=+=+=
century found at line 142: century found at line 142:
140: mechanisms to synchronize time in principle to precisions in the 140: mechanisms to synchronize time in principle to precisions in
141: order of nanoseconds while preserving a non-ambiguous date well into 140(continued): the
142: the next century. The protocol includes provisions to specify the 141: order of nanoseconds while preserving a non-ambiguous date we
143: characteristics and estimate the error of the local clock and the 141(continued): ll into
144: time server to which it may be synchronized. It also includes 142: the next century. The protocol includes provisions to specif
142(continued): y the
143: characteristics and estimate the error of the local clock and
143(continued): the
144: time server to which it may be synchronized. It also include
144(continued): s
1900 found at line 574: 1900 found at line 574:
572: frequency to the TA time scale. At 0000 hours on 1 January 1972 the 572: frequency to the TA time scale. At 0000 hours on 1 January 1
573: NTP time scale was set to 2,272,060,800, representing the number of 572(continued): 972 the
574: TA seconds since 0000 hours on 1 January 1900. The insertion of leap 573: NTP time scale was set to 2,272,060,800, representing the num
575: seconds in UTC does not affect the oscillator itself, only the 573(continued): ber of
576: translation between TA and UTC, or conventional civil time. However, 574: TA seconds since 0000 hours on 1 January 1900. The insertion
574(continued): of leap
575: seconds in UTC does not affect the oscillator itself, only th
575(continued): e
576: translation between TA and UTC, or conventional civil time.
576(continued): However,
1900 found at line 649: 1900 found at line 649:
647: main product of the protocol, a special timestamp format has been 647: main product of the protocol, a special timestamp format has
648: established. NTP timestamps are represented as a 64-bit unsigned 647(continued): been
649: fixed-point number, in seconds relative to 0000 UT on 1 January 1900. 648: established. NTP timestamps are represented as a 64-bit unsi
650: The integer part is in the first 32 bits and the fraction part in the 648(continued): gned
649: fixed-point number, in seconds relative to 0000 UT on 1 Janua
649(continued): ry 1900.
650: The integer part is in the first 32 bits and the fraction par
650(continued): t in the
651: last 32 bits, as shown in the following diagram. 651: last 32 bits, as shown in the following diagram.
1900 found at line 690: 1900 found at line 690:
688: the Integer Part) has been set and that the 64-bit field will 688: the Integer Part) has been set and that the 64-bit field will
689: overflow some time in 2036. Should NTP be in use in 2036, some 688(continued):
690: external means will be necessary to qualify time relative to 1900 and 689: overflow some time in 2036. Should NTP be in use in 2036, so
689(continued): me
690: external means will be necessary to qualify time relative to
690(continued): 1900 and
691: time relative to 2036 (and other multiples of 136 years). 691: time relative to 2036 (and other multiples of 136 years).
692: Timestamped data requiring such qualification will be so precious 692: Timestamped data requiring such qualification will be so prec
692(continued): ious
+=+=+=+=+= File rfc1060.txt +=+=+=+=+= +=+=+=+=+= File rfc1060.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 2324: 'yy' on a line without 'yyyy' found at line 2324:
2322: AB-00-03-00-00-00 6004 DEC Local Area Transport (LAT) - old 2322: AB-00-03-00-00-00 6004 DEC Local Area Transport
2323: AB-00-04-00-xx-xx ???? Reserved DEC customer private use 2322(continued): (LAT) - old
2324: AB-00-04-01-xx-yy 6007 DEC Local Area VAX Cluster groups 2323: AB-00-04-00-xx-xx ???? Reserved DEC customer private
2325: System Communication Architecture (SCA) 2323(continued): use
2326: CF-00-00-00-00-00 9000 Ethernet Configuration Test protocol (Loopback) 2324: AB-00-04-01-xx-yy 6007 DEC Local Area VAX Cluster gr
2324(continued): oups
2325: System Communication Architec
2325(continued): ture (SCA)
2326: CF-00-00-00-00-00 9000 Ethernet Configuration Test
2326(continued): protocol (Loopback)
2000 found at line 2729: 2000 found at line 2729:
2727: 014.000.000.018 2624-522-80900 52 FGAN-SIEMENS-X25 [GB7] 2727: 014.000.000.018 2624-522-80900 52 FGAN-SIEMENS-X25
2728: 014.000.000.019 2041-170-10000 00 SHAPE-X25 [JFW] 2727(continued): [GB7]
2729: 014.000.000.020 5052-737-20000 50 UQNET [AXH] 2728: 014.000.000.019 2041-170-10000 00 SHAPE-X25
2730: 014.000.000.021 3020-801-00057 50 DMC-CRC1 [VXT] 2728(continued): [JFW]
2731: 014.000.000.022 2624-522-80329 02 FGAN-FGANFFMVAX-X25 [GB7] 2729: 014.000.000.020 5052-737-20000 50 UQNET
2729(continued): [AXH]
2730: 014.000.000.021 3020-801-00057 50 DMC-CRC1
2730(continued): [VXT]
2731: 014.000.000.022 2624-522-80329 02 FGAN-FGANFFMVAX-X25
2731(continued): [GB7]
2000 found at line 3155: 2000 found at line 3155:
3153: AEGIS MACOS TP3010 3153: AEGIS MACOS TP3010
3154: APOLLO MINOS TRSDOS 3154: APOLLO MINOS TRSDOS
3155: BS-2000 MOS ULTRIX 3155: BS-2000 MOS ULTRIX
3156: CEDAR MPE5 UNIX 3156: CEDAR MPE5 UNIX
3157: CGW MSDOS UNIX-BSD 3157: CGW MSDOS UNIX-BSD
2000 found at line 3508: 2000 found at line 3508:
3506: HAZELTINE-1520 IBM-3278-5-E 3506: HAZELTINE-1520 IBM-3278-5-E
skipping to change at page 1, line 4889 skipping to change at page 1, line 5156
3508: HAZELTINE-2000 IBM-3279-3-E 3508: HAZELTINE-2000 IBM-3279-3-E
3509: HAZELTINE-ESPRIT IMLAC 3509: HAZELTINE-ESPRIT IMLAC
3510: HP-2392 INFOTON-100 3510: HP-2392 INFOTON-100
+=+=+=+=+= File rfc1064.txt +=+=+=+=+= +=+=+=+=+= File rfc1064.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 1321: 'yy' on a line without 'yyyy' found at line 1321:
1319: "NO" SP text_line / "BAD" SP text_line) 1319: "NO" SP text_line / "BAD" SP text_line)
1320: 1320:
1321: date ::= string in form "dd-mmm-yy hh:mm:ss-zzz" 1321: date ::= string in form "dd-mmm-yy hh:mm:ss-zzz"
1322: 1322:
1323: envelope ::= "(" env_date SP env_subject SP env_from SP 1323: envelope ::= "(" env_date SP env_subject SP env_from S
1323(continued): P
+=+=+=+=+= File rfc1085.txt +=+=+=+=+= +=+=+=+=+= File rfc1085.txt +=+=+=+=+=
UTCTime found at line 1501: UTCTime found at line 1501:
1499: 1499:
1500: commonReference 1500: commonReference
1501: UTCTime, 1501: UTCTime,
1502: 1502:
1503: additionalReferenceInformation[0] 1503: additionalReferenceInformation[0]
+=+=+=+=+= File rfc1094.txt +=+=+=+=+= +=+=+=+=+= File rfc1094.txt +=+=+=+=+=
2000 found at line 878: 2000 found at line 878:
876: 876:
877: 0040000 This is a directory; "type" field should be NFDIR. 877: 0040000 This is a directory; "type" field should be NFDIR.
878: 0020000 This is a character special file; "type" field should 877(continued):
878: 0020000 This is a character special file; "type" field sho
878(continued): uld
879: be NFCHR. 879: be NFCHR.
880: 0060000 This is a block special file; "type" field should be 880: 0060000 This is a block special file; "type" field should
880(continued): be
2000 found at line 883: 2000 found at line 883:
881: NFBLK. 881: NFBLK.
882: 0100000 This is a regular file; "type" field should be NFREG. 882: 0100000 This is a regular file; "type" field should be NFR
883: 0120000 This is a symbolic link file; "type" field should be 882(continued): EG.
883: 0120000 This is a symbolic link file; "type" field should
883(continued): be
884: NFLNK. 884: NFLNK.
885: 0140000 This is a named socket; "type" field should be NFNON. 885: 0140000 This is a named socket; "type" field should be NFN
885(continued): ON.
2000 found at line 887: 2000 found at line 887:
885: 0140000 This is a named socket; "type" field should be NFNON. 885: 0140000 This is a named socket; "type" field should be NFN
885(continued): ON.
886: 0004000 Set user id on execution. 886: 0004000 Set user id on execution.
887: 0002000 Set group id on execution. 887: 0002000 Set group id on execution.
888: 0001000 Save swapped text even after use. 888: 0001000 Save swapped text even after use.
889: 0000400 Read permission for owner. 889: 0000400 Read permission for owner.
+=+=+=+=+= File rfc1108.txt +=+=+=+=+= +=+=+=+=+= File rfc1108.txt +=+=+=+=+=
2000 found at line 187: 2000 found at line 187:
185: throughout DoD common user data networks, users of these networks 185: throughout DoD common user data networks, users of these netw
186: should submit requirements for additional Protection Authority Flags 185(continued): orks
187: to DISA DISDB, Washington, D.C. 20305-2000, for review and approval. 186: should submit requirements for additional Protection Authorit
186(continued): y Flags
187: to DISA DISDB, Washington, D.C. 20305-2000, for review and a
187(continued): pproval.
188: Such review and approval should be sought prior to design, 188: Such review and approval should be sought prior to design,
189: development or deployment of any system which would make use of 189: development or deployment of any system which would make use
189(continued): of
2000 found at line 774: 2000 found at line 774:
772: data networks, and to maximize interoperability, each activity should 772: data networks, and to maximize interoperability, each activit
773: submit its plans for the definition and use of an Additional Security 772(continued): y should
774: Info Format Code to DISA DISDB, Washington, D.C. 20305-2000 for 773: submit its plans for the definition and use of an Additional
775: review and approval. DISA DISDB will forward plans to the Internet 773(continued): Security
776: Activities Board for architectural review and, if required, a cleared 774: Info Format Code to DISA DISDB, Washington, D.C. 20305-2000
774(continued): for
775: review and approval. DISA DISDB will forward plans to the In
775(continued): ternet
776: Activities Board for architectural review and, if required, a
776(continued): cleared
+=+=+=+=+= File rfc1114.txt +=+=+=+=+= +=+=+=+=+= File rfc1114.txt +=+=+=+=+=
UTCTime found at line 922: UTCTime found at line 922:
920: issuer Name, 920: issuer Name,
921: list SEQUENCE RCLEntry, 921: list SEQUENCE RCLEntry,
922: lastUpdate UTCTime, 922: lastUpdate UTCTime,
923: nextUpdate UTCTime} 923: nextUpdate UTCTime}
924: 924:
UTCTime found at line 923: UTCTime found at line 923:
skipping to change at page 1, line 4975 skipping to change at page 1, line 5260
UTCTime found at line 1297: UTCTime found at line 1297:
1295: Validity ::= SEQUENCE{ 1295: Validity ::= SEQUENCE{
1296: notBefore UTCTime, 1296: notBefore UTCTime,
1297: notAfter UTCTime} 1297: notAfter UTCTime}
1298: 1298:
1299: SubjectPublicKeyInfo ::= SEQUENCE{ 1299: SubjectPublicKeyInfo ::= SEQUENCE{
+=+=+=+=+= File rfc1117.txt +=+=+=+=+= +=+=+=+=+= File rfc1117.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 4965: 'yy' on a line without 'yyyy' found at line 4965:
4963: jwmanly%amherst.bitnet@MITVMA.MIT.EDU 4963: jwmanly%amherst.bitnet@MITVMA.MIT.EDU
4964: [JWN10] Norris, James W a02jwn1%niu.bitnet@CUNYVM.CUNY.EDU 4964: [JWN10] Norris, James W a02jwn1%niu.bitnet@CUNYVM.CUNY.E
4964(continued): DU
4965: [JY24] Yu, Jessica jyy@MERIT.EDU 4965: [JY24] Yu, Jessica jyy@MERIT.EDU
4966: [JY33] Yoshida, Jun ---none--- 4966: [JY33] Yoshida, Jun ---none---
4967: [KA4] Auerbach, Karl auerbach@CSL.SRI.COM 4967: [KA4] Auerbach, Karl auerbach@CSL.SRI.COM
+=+=+=+=+= File rfc1123.txt +=+=+=+=+= +=+=+=+=+= File rfc1123.txt +=+=+=+=+=
2digit found at line 3239: 2digit found at line 3239:
3237: The syntax for the date is hereby changed to: 3237: The syntax for the date is hereby changed to:
3238: 3238:
3239: date = 1*2DIGIT month 2*4DIGIT 3239: date = 1*2DIGIT month 2*4DIGIT
3240: 3240:
3241: 3241:
century found at line 3253: century found at line 3253:
3251: 3251:
3252: All mail software SHOULD use 4-digit years in dates, to ease 3252: All mail software SHOULD use 4-digit years in dates, to
3252(continued): ease
3253: the transition to the next century. 3253: the transition to the next century.
3254: 3254:
3255: There is a strong trend towards the use of numeric timezone 3255: There is a strong trend towards the use of numeric time
3255(continued): zone
+=+=+=+=+= File rfc1133.txt +=+=+=+=+= +=+=+=+=+= File rfc1133.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 493: 'yy' on a line without 'yyyy' found at line 493:
491: Telephone: 313 936-2655 491: Telephone: 313 936-2655
492: Fax: 313 747-3745 492: Fax: 313 747-3745
493: EMail: jyy@merit.edu 493: EMail: jyy@merit.edu
494: 494:
495: Hans-Werner Braun 495: Hans-Werner Braun
+=+=+=+=+= File rfc1138.txt +=+=+=+=+= +=+=+=+=+= File rfc1138.txt +=+=+=+=+=
UTCTime found at line 1471: UTCTime found at line 1471:
1469: the full BNF easier to parse. 1469: the full BNF easier to parse.
1470: 1470:
skipping to change at page 1, line 5009 skipping to change at page 1, line 5298
493: EMail: jyy@merit.edu 493: EMail: jyy@merit.edu
494: 494:
495: Hans-Werner Braun 495: Hans-Werner Braun
+=+=+=+=+= File rfc1138.txt +=+=+=+=+= +=+=+=+=+= File rfc1138.txt +=+=+=+=+=
UTCTime found at line 1471: UTCTime found at line 1471:
1469: the full BNF easier to parse. 1469: the full BNF easier to parse.
1470: 1470:
1471: 3.3.5. UTCTime 1471: 3.3.5. UTCTime
1472: 1472:
1473: Both UTCTime and the RFC 822 822.date-time syntax contain: Year 1473: Both UTCTime and the RFC 822 822.date-time syntax contain: Y
1473(continued): ear
UTCTime found at line 1473: UTCTime found at line 1473:
1471: 3.3.5. UTCTime 1471: 3.3.5. UTCTime
1472: 1472:
1473: Both UTCTime and the RFC 822 822.date-time syntax contain: Year 1473: Both UTCTime and the RFC 822 822.date-time syntax contain: Y
1474: (lowest two digits), Month, Day of Month, hour, minute, second 1473(continued): ear
1475: (optional), and Timezone. 822.date-time also contains an optional 1474: (lowest two digits), Month, Day of Month, hour, minute, secon
1474(continued): d
1475: (optional), and Timezone. 822.date-time also contains an opt
1475(continued): ional
UTCTime found at line 1482: UTCTime found at line 1482:
1480: In practice, a gateway will need to parse various illegal 1480: In practice, a gateway will need to parse various illega
1480(continued): l
1481: variants on 822.date-time. In cases where 822.date-time 1481: variants on 822.date-time. In cases where 822.date-time
1482: cannot be parsed, it is recommended that the derived UTCTime 1481(continued):
1482: cannot be parsed, it is recommended that the derived UTC
1482(continued): Time
1483: is set to the value at the time of translation. 1483: is set to the value at the time of translation.
1484: 1484:
UTCTime found at line 1485: UTCTime found at line 1485:
1483: is set to the value at the time of translation. 1483: is set to the value at the time of translation.
1484: 1484:
1485: The UTCTime format which specifies the timezone offset should be 1485: The UTCTime format which specifies the timezone offset should
1485(continued): be
1486: used. 1486: used.
1487: 1487:
UTCTime found at line 4469: UTCTime found at line 4469:
4467: 4467:
4468: The extended syntax of zone defined in the JNT Mail Protocol should 4468: The extended syntax of zone defined in the JNT Mail Protocol
4468(continued): should
4469: be used in the mapping of UTCTime defined in Chapter 3. 4469: be used in the mapping of UTCTime defined in Chapter 3.
4470: 4470:
4471: 6. Lack of 822-MTS originator specification 4471: 6. Lack of 822-MTS originator specification
+=+=+=+=+= File rfc1147.txt +=+=+=+=+= +=+=+=+=+= File rfc1147.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 9715: 'yy' on a line without 'yyyy' found at line 9715:
9713: cerns to security and management personnel at DDN facili- 9713: cerns to security and management personnel at DDN faci
9714: ties. It is available online, via kermit or anonymous FTP, 9713(continued): li-
9715: from nic.ddn.mil, in SCC:DDN-SECURITY-yy-nn.TXT (where "yy" 9714: ties. It is available online, via kermit or anonymous
9716: is the year and "nn" is the bulletin number). The SCC pro- 9714(continued): FTP,
9717: vides immediate assistance with DDN-related host security 9715: from nic.ddn.mil, in SCC:DDN-SECURITY-yy-nn.TXT (where
9715(continued): "yy"
9716: is the year and "nn" is the bulletin number). The SCC
9716(continued): pro-
9717: vides immediate assistance with DDN-related host secur
9717(continued): ity
century found at line 1096: century found at line 1096:
1094: "NETMON." These tools were independently developed, are 1094: "NETMON." These tools were independently developed, ar
1095: functionally different, run in different environments, and 1094(continued): e
1096: are no more related than Richard Burton the 19th century 1095: functionally different, run in different environments,
1097: explorer and Richard Burton the 20th century actor. BYU's 1095(continued): and
1098: tool "NETMON" is listed as "NETMON (I)," MITRE's as "NETMON 1096: are no more related than Richard Burton the 19th centu
1096(continued): ry
1097: explorer and Richard Burton the 20th century actor. B
1097(continued): YU's
1098: tool "NETMON" is listed as "NETMON (I)," MITRE's as "N
1098(continued): ETMON
century found at line 1097: century found at line 1097:
1095: functionally different, run in different environments, and 1095: functionally different, run in different environments,
1096: are no more related than Richard Burton the 19th century 1095(continued): and
1097: explorer and Richard Burton the 20th century actor. BYU's 1096: are no more related than Richard Burton the 19th centu
1098: tool "NETMON" is listed as "NETMON (I)," MITRE's as "NETMON 1096(continued): ry
1099: (II)," and the tool from SNMP Research as "NETMON (III)." 1097: explorer and Richard Burton the 20th century actor. B
1097(continued): YU's
1098: tool "NETMON" is listed as "NETMON (I)," MITRE's as "N
1098(continued): ETMON
1099: (II)," and the tool from SNMP Research as "NETMON (III
1099(continued): )."
2000 found at line 4134: 2000 found at line 4134:
4132: libraries), but this has not been done. Curses is very 4132: libraries), but this has not been done. Curses i
4133: slow and cpu intensive on VMS, but the tool has been 4132(continued): s very
4134: run in a window on a VAXstation 2000. Just don't try 4133: slow and cpu intensive on VMS, but the tool has b
4133(continued): een
4134: run in a window on a VAXstation 2000. Just don't
4134(continued): try
4135: to run it on a terminal connected to a 11/750. 4135: to run it on a terminal connected to a 11/750.
4136: 4136:
+=+=+=+=+= File rfc1148.txt +=+=+=+=+= +=+=+=+=+= File rfc1148.txt +=+=+=+=+=
UTCTime found at line 1475: UTCTime found at line 1475:
1473: the full BNF easier to parse. 1473: the full BNF easier to parse.
1474: 1474:
1475: 3.3.5. UTCTime 1475: 3.3.5. UTCTime
1476: 1476:
1477: Both UTCTime and the RFC 822 822.date-time syntax contain: Year 1477: Both UTCTime and the RFC 822 822.date-time syntax contain: Y
1477(continued): ear
UTCTime found at line 1477: UTCTime found at line 1477:
1475: 3.3.5. UTCTime 1475: 3.3.5. UTCTime
1476: 1476:
1477: Both UTCTime and the RFC 822 822.date-time syntax contain: Year 1477: Both UTCTime and the RFC 822 822.date-time syntax contain: Y
1478: (lowest two digits), Month, Day of Month, hour, minute, second 1477(continued): ear
1479: (optional), and Timezone. 822.date-time also contains an optional 1478: (lowest two digits), Month, Day of Month, hour, minute, secon
1478(continued): d
1479: (optional), and Timezone. 822.date-time also contains an opt
1479(continued): ional
UTCTime found at line 1486: UTCTime found at line 1486:
1484: In practice, a gateway will need to parse various illegal 1484: In practice, a gateway will need to parse various illega
1484(continued): l
1485: variants on 822.date-time. In cases where 822.date-time 1485: variants on 822.date-time. In cases where 822.date-time
1486: cannot be parsed, it is recommended that the derived UTCTime 1485(continued):
1486: cannot be parsed, it is recommended that the derived UTC
1486(continued): Time
1487: is set to the value at the time of translation. 1487: is set to the value at the time of translation.
1488: 1488:
UTCTime found at line 1489: UTCTime found at line 1489:
1487: is set to the value at the time of translation. 1487: is set to the value at the time of translation.
1488: 1488:
1489: The UTCTime format which specifies the timezone offset should be 1489: The UTCTime format which specifies the timezone offset should
1489(continued): be
1490: used. 1490: used.
1491: 1491:
UTCTime found at line 4566: UTCTime found at line 4566:
4564: 4564:
4565: The extended syntax of zone defined in the JNT Mail Protocol should 4565: The extended syntax of zone defined in the JNT Mail Protocol
4565(continued): should
4566: be used in the mapping of UTCTime defined in Chapter 3. 4566: be used in the mapping of UTCTime defined in Chapter 3.
4567: 4567:
4568: 6. Lack of 822-MTS originator specification 4568: 6. Lack of 822-MTS originator specification
+=+=+=+=+= File rfc1152.txt +=+=+=+=+= +=+=+=+=+= File rfc1152.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 937: 'yy' on a line without 'yyyy' found at line 937:
935: Reservation Multiple-Access). 935: Reservation Multiple-Access).
936: 936:
937: Finally, Yechiam Yemeni (YY, Columbia University) discussed his work 937: Finally, Yechiam Yemeni (YY, Columbia University) discussed h
938: on a protocol silicon compiler. In order to exploit the potential 937(continued): is work
939: parallelism, he is planning to use one processor per connection. 938: on a protocol silicon compiler. In order to exploit the pote
938(continued): ntial
939: parallelism, he is planning to use one processor per connecti
939(continued): on.
+=+=+=+=+= File rfc1153.txt +=+=+=+=+= +=+=+=+=+= File rfc1153.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 119: 'yy' on a line without 'yyyy' found at line 119:
117: 117:
118: 118:
119: Date: ddd, dd mmm yy hh:mm:ss zzz 119: Date: ddd, dd mmm yy hh:mm:ss zzz
120: From: listname-REQUEST@fqhn 120: From: listname-REQUEST@fqhn
121: Reply-To: listname@fqhn 121: Reply-To: listname@fqhn
'yy' on a line without 'yyyy' found at line 122: 'yy' on a line without 'yyyy' found at line 122:
120: From: listname-REQUEST@fqhn 120: From: listname-REQUEST@fqhn
121: Reply-To: listname@fqhn 121: Reply-To: listname@fqhn
122: Subject: listname Digest Vyy #nn 122: Subject: listname Digest Vyy #nn
123: To: listname@fqhn 123: To: listname@fqhn
124: 124:
'yy' on a line without 'yyyy' found at line 125: 'yy' on a line without 'yyyy' found at line 125:
123: To: listname@fqhn 123: To: listname@fqhn
124: 124:
125: listname Digest ddd, dd mmm yy Volume yy : Issue nn 125: listname Digest ddd, dd mmm yy Volume yy : Iss
125(continued): ue nn
126: 126:
127: Today's Topics: 127: Today's Topics:
'yy' on a line without 'yyyy' found at line 137: 'yy' on a line without 'yyyy' found at line 137:
135: ---------------------------------------------------------------------- 135: ----------------------------------------------------------------
135(continued): ------
136: 136:
137: Date: ddd, dd mmm yy hh:mm:ss zzz 137: Date: ddd, dd mmm yy hh:mm:ss zzz
138: From: Joe User <username@fqhn> 138: From: Joe User <username@fqhn>
139: Subject: Message One Subject 139: Subject: Message One Subject
'yy' on a line without 'yyyy' found at line 147: 'yy' on a line without 'yyyy' found at line 147:
145: ------------------------------ 145: ------------------------------
146: 146:
147: Date: ddd, dd mmm yy hh:mm:ss zzz 147: Date: ddd, dd mmm yy hh:mm:ss zzz
148: From: Jane User <username@fqhn> 148: From: Jane User <username@fqhn>
149: Subject: Message Two Subject 149: Subject: Message Two Subject
skipping to change at page 1, line 5168 skipping to change at page 1, line 5500
321: 321:
322: 03019000 322: 03019000
323: 323:
324: 5. Acknowledgements 324: 5. Acknowledgements
2000 found at line 210: 2000 found at line 210:
208: (1) <nsap> is a hex string defining the nsap, e.g., 208: (1) <nsap> is a hex string defining the nsap, e.g.,
209: 209:
210: "snmp"/NS+4900590800200038bafe00 210: "snmp"/NS+4900590800200038bafe00
211: 211:
212: Similarly, SNMP traps are, by convention, sent to a manager listening 212: Similarly, SNMP traps are, by convention, sent to a manager l
212(continued): istening
2000 found at line 291: 2000 found at line 291:
289: (1) <nsap> is a hex string defining the nsap, e.g., 289: (1) <nsap> is a hex string defining the nsap, e.g.,
290: 290:
291: "snmp"/NS+4900590800200038bafe00 291: "snmp"/NS+4900590800200038bafe00
292: 292:
293: Similarly, SNMP traps are, by convention, sent to a manager listening 293: Similarly, SNMP traps are, by convention, sent to a manager l
293(continued): istening
+=+=+=+=+= File rfc1164.txt +=+=+=+=+= +=+=+=+=+= File rfc1164.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 1267: 'yy' on a line without 'yyyy' found at line 1267:
1265: Phone: (313) 936-3000 1265: Phone: (313) 936-3000
1266: 1266:
1267: Email: JYY@MERIT.EDU 1267: Email: JYY@MERIT.EDU
1268: 1268:
1269: 1269:
+=+=+=+=+= File rfc1166.txt +=+=+=+=+= +=+=+=+=+= File rfc1166.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 8270: 'yy' on a line without 'yyyy' found at line 8270:
8268: [JWN10] Norris, James W. 8268: [JWN10] Norris, James W.
8269: a02jwn1%niu.bitnet@CUNYVM.CUNY.EDU 8269: a02jwn1%niu.bitnet@CUNYVM.CUNY.EDU
8270: [JY24] Yu, Jessica jyy@MERIT.EDU 8270: [JY24] Yu, Jessica jyy@MERIT.EDU
8271: [JY33] Yoshida, Jun ---none--- 8271: [JY33] Yoshida, Jun ---none---
8272: [JY35] Young, Jeff ---none--- 8272: [JY35] Young, Jeff ---none---
+=+=+=+=+= File rfc1167.txt +=+=+=+=+= +=+=+=+=+= File rfc1167.txt +=+=+=+=+=
2000 found at line 89: 2000 found at line 89:
87: are also likely play a role along with Switched Multi-megabit Data 87: are also likely play a role along with Switched Multi-megabit
88: Service (SMDS) provided by telecommunications carriers. It also 87(continued): Data
89: would be fair to ask what role FTS-2000 might play in the system, at 88: Service (SMDS) provided by telecommunications carriers. It a
90: least in support of government access to the NREN, and possibly in 88(continued): lso
89: would be fair to ask what role FTS-2000 might play in the sys
89(continued): tem, at
90: least in support of government access to the NREN, and possib
90(continued): ly in
91: support of national agency network facilities. 91: support of national agency network facilities.
+=+=+=+=+= File rfc1173.txt +=+=+=+=+= +=+=+=+=+= File rfc1173.txt +=+=+=+=+=
century found at line 72: century found at line 72:
70: only choice; I don't see any prospect of either the government or 70: only choice; I don't see any prospect of either the governmen
71: private enterprise building a monolithic, centralized, ubiquitous "Ma 70(continued): t or
71: private enterprise building a monolithic, centralized, ubiqui
71(continued): tous "Ma
72: Datagram" network provider in this century. 72: Datagram" network provider in this century.
73: 73:
74: 2. Responsibilities of Network Managers 74: 2. Responsibilities of Network Managers
+=+=+=+=+= File rfc1176.txt +=+=+=+=+= +=+=+=+=+= File rfc1176.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 1435: 'yy' on a line without 'yyyy' found at line 1435:
1433: "NO" SP text_line / "BAD" SP text_line) 1433: "NO" SP text_line / "BAD" SP text_line)
1434: 1434:
1435: date ::= string in form "dd-mmm-yy hh:mm:ss-zzz" 1435: date ::= string in form "dd-mmm-yy hh:mm:ss-zzz"
1436: 1436:
1437: envelope ::= "(" env_date SP env_subject SP env_from SP 1437: envelope ::= "(" env_date SP env_subject SP env_from S
1437(continued): P
+=+=+=+=+= File rfc1185.txt +=+=+=+=+= +=+=+=+=+= File rfc1185.txt +=+=+=+=+=
2000 found at line 208: 2000 found at line 208:
206: 1.1MBps, no matter how high the theoretical transfer rate of the 206: 1.1MBps, no matter how high the theoretical transfer rate
207: path. This corresponds to cycling the sequence number space in 206(continued): of the
207: path. This corresponds to cycling the sequence number spa
207(continued): ce in
208: Twrap= 2000 secs, which is safe in today's Internet. 208: Twrap= 2000 secs, which is safe in today's Internet.
209: 209:
210: Based on this reasoning, an earlier RFC [McKenzie89] has cautioned 210: Based on this reasoning, an earlier RFC [McKenzie89] has c
210(continued): autioned
+=+=+=+=+= File rfc1190.txt +=+=+=+=+= +=+=+=+=+= File rfc1190.txt +=+=+=+=+=
2000 found at line 7630: 2000 found at line 7630:
7628: link failure 7628: link failure
7629: 7629:
7630: 2000 DefaultRecoveryTimeout Interval between successive 7630: 2000 DefaultRecoveryTimeout Interval between successive
7631: HELLOs to/from active neighbors 7630(continued):
7631: HELLOs to/from active neigh
7631(continued): bors
7632: 7632:
+=+=+=+=+= File rfc1191.txt +=+=+=+=+= +=+=+=+=+= File rfc1191.txt +=+=+=+=+=
2000 found at line 925: 2000 found at line 925:
923: 65535 Hyperchannel RFC 1044 923: 65535 Hyperchannel RFC 1044
924: 65535 924: 65535
925: 32000 Just in case 925: 32000 Just in case
926: 17914 16Mb IBM Token Ring ref. [6] 926: 17914 16Mb IBM Token Ring ref. [6]
927: 17914 927: 17914
skipping to change at page 1, line 5254 skipping to change at page 1, line 5600
2101: 2101:
2102: date ::= string in form "dd-mmm-yy hh:mm:ss-zzz" 2102: date ::= string in form "dd-mmm-yy hh:mm:ss-zzz"
2103: 2103:
2104: envelope ::= "(" env_date SP env_subject SP env_from SP 2104: envelope ::= "(" env_date SP env_subject SP env_from SP
2000 found at line 2614: 2000 found at line 2614:
2612: question. For example: 2612: question. For example:
2613: 2613:
2614: tag42 FETCH 197 BODY 2000:3999 2614: tag42 FETCH 197 BODY 2000:3999
2615: 2615:
2616: would fetch the second two thousand bytes of the body of message 2616: would fetch the second two thousand bytes of the body of
2616(continued): message
+=+=+=+=+= File rfc1207.txt +=+=+=+=+= +=+=+=+=+= File rfc1207.txt +=+=+=+=+=
'yy' on a line without 'yyyy' found at line 136: 'yy' on a line without 'yyyy' found at line 136:
134: directory. Information includes packet counts by NSS and byte 134: directory. Information includes packet counts by NSS and
135: counts for type of use (ftp, smtp, telnet, etc.). Filenames are 134(continued): byte
135: counts for type of use (ftp, smtp, telnet, etc.). Filenam
135(continued): es are
136: of the form 'NSFyy-mm.type'. 136: of the form 'NSFyy-mm.type'.
137: 137:
138: Files are available for anonymous ftp; use 'guest' as the 138: Files are available for anonymous ftp; use 'guest' as the
+=+=+=+=+= File rfc1210.txt +=+=+=+=+= +=+=+=+=+= File rfc1210.txt +=+=+=+=+=
2000 found at line 1548: 2000 found at line 1548:
1546: Franci Bigi (1) 1546: Franci Bigi (1)
1547: CEC 1547: CEC
1548: Rue de la Loi 2000 1548: Rue de la Loi 2000
1549: B-1049 1549: B-1049
1550: Brussels 1550: Brussels
skipping to change at page 1, line 5304