RFC 2626
The Internet and the Millennium Problem (Year 2000)
2digit found at line 876: 874: date2 = 2DIGIT "-" month "-" 2DIGIT 875: ; day-month-year (e.g., 02-Jun-82) 876: date3 = month SP ( 2DIGIT | ( SP 1DIGIT )) 877: ; month day (e.g., Jun 2) 878: 2digit found at line 879: 877: ; month day (e.g., Jun 2) 878: 879: time = 2DIGIT ":" 2DIGIT ":" 2DIGIT 880: ; 00:00:00 - 23:59:59 881: +=+=+=+=+= File rfc1967.txt +=+=+=+=+= 'yy' on a line without 'yyyy' found at line 276: 274: +-----+----....................----+ 275: 276: where: C0 and 80 are representative LZS-DCP headers; nn, 276(continued): xx, yy, 277: and zz are values determined by the packet's conte 277(continued): xt. 278: +=+=+=+=+= File rfc1980.txt +=+=+=+=+= century found at line 301: 299: ALT="Our products"> 300: <AREA SHAPE=RECT COORDS="0,51,100,100 HREF="technology.htm 300(continued): l" 301: ALT="Technology for the next century"> 302: </MAP> 303: +=+=+=+=+= File rfc1997.txt +=+=+=+=+= 2000 found at line 130: 128: 690 may define research, educational and commercial community 128(continued): values 129: that may be used for policy routing as defined by the operato 129(continued): rs of 130: that AS using community attribute values 0x02B20000 through 131: 0x02B2FFFF). 132:
+=+=+=+=+= File rfc1999.txt +=+=+=+=+= 1900 found at line 14: 12: Request for Comments Summary 13: 14: RFC Numbers 1900-1999 15: 16: Status of This Memo 1900 found at line 18: 16: Status of This Memo 17: 18: This RFC is a slightly annotated list of the 100 RFCs from RF 18(continued): C 1900 19: through RFCs 1999. This is a status report on these RFCs. T 19(continued): his memo 20: provides information for the Internet community. It does not 20(continued): specify 1900 found at line 60: 58: Elliott Informational 58(continued): [Page 1] 59: 60: RFC 1999 Summary of 1900-1999 Janu 60(continued): ary 1997 61: 62: 1900 found at line 116: 114: Elliott Informational 114(continued): [Page 2] 115: 116: RFC 1999 Summary of 1900-1999 Janu 116(continued): ary 1997 117: 118: 1900 found at line 172: 170: Elliott Informational 170(continued): [Page 3] 171: 172: RFC 1999 Summary of 1900-1999 Janu 172(continued): ary 1997 173: 174: 1900 found at line 228: 226: Elliott Informational 226(continued): [Page 4]
227: 228: RFC 1999 Summary of 1900-1999 Janu 228(continued): ary 1997 229: 230: 1900 found at line 284: 282: Elliott Informational 282(continued): [Page 5] 283: 284: RFC 1999 Summary of 1900-1999 Janu 284(continued): ary 1997 285: 286: 1900 found at line 340: 338: Elliott Informational 338(continued): [Page 6] 339: 340: RFC 1999 Summary of 1900-1999 Janu 340(continued): ary 1997 341: 342: 1900 found at line 396: 394: Elliott Informational 394(continued): [Page 7] 395: 396: RFC 1999 Summary of 1900-1999 Janu 396(continued): ary 1997 397: 398: 1900 found at line 452: 450: Elliott Informational 450(continued): [Page 8] 451: 452: RFC 1999 Summary of 1900-1999 Janu 452(continued): ary 1997 453: 454: 1900 found at line 508: 506: Elliott Informational 506(continued): [Page 9] 507:
508: RFC 1999 Summary of 1900-1999 Janu 508(continued): ary 1997 509: 510: 1900 found at line 564: 562: Elliott Informational [ 562(continued): Page 10] 563: 564: RFC 1999 Summary of 1900-1999 Janu 564(continued): ary 1997 565: 566: 1900 found at line 620: 618: Elliott Informational [ 618(continued): Page 11] 619: 620: RFC 1999 Summary of 1900-1999 Janu 620(continued): ary 1997 621: 622: 1900 found at line 676: 674: Elliott Informational [ 674(continued): Page 12] 675: 676: RFC 1999 Summary of 1900-1999 Janu 676(continued): ary 1997 677: 678: 1900 found at line 732: 730: Elliott Informational [ 730(continued): Page 13] 731: 732: RFC 1999 Summary of 1900-1999 Janu 732(continued): ary 1997 733: 734: 1900 found at line 788: 786: Elliott Informational [ 786(continued): Page 14] 787:
788: RFC 1999 Summary of 1900-1999 Janu 788(continued): ary 1997 789: 790: 1900 found at line 844: 842: Elliott Informational [ 842(continued): Page 15] 843: 844: RFC 1999 Summary of 1900-1999 Janu 844(continued): ary 1997 845: 846: 1900 found at line 900: 898: Elliott Informational [ 898(continued): Page 16] 899: 900: RFC 1999 Summary of 1900-1999 Janu 900(continued): ary 1997 901: 902: 1900 found at line 956: 954: Elliott Informational [ 954(continued): Page 17] 955: 956: RFC 1999 Summary of 1900-1999 Janu 956(continued): ary 1997 957: 958: 1900 found at line 1012: 1010: Elliott Informational [ 1010(continued): Page 18] 1011: 1012: RFC 1999 Summary of 1900-1999 Janu 1012(continued): ary 1997 1013: 1014: 1900 found at line 1068: 1066: Elliott Informational [ 1066(continued): Page 19] 1067:
1068: RFC 1999 Summary of 1900-1999 Janu 1068(continued): ary 1997 1069: 1070: 1900 found at line 1095: 1093: 1094: 1095: 1900 Carpenter Feb 96 Renumbering Needs Work 1096: 1097: Hosts in an IP network are identified by IP addresses, and the I 1097(continued): P +=+=+=+=+= File rfc2000.txt +=+=+=+=+= 'yy' on a line without 'yyyy' found at line 3070: 3068: The text version is sent. 3068(continued): 3069: 3070: file /ftp/rfc/rfcnnnn.yyy where 'nnnn' is the RFC n 3070(continued): umber. 3071: and 'yyy' is 'txt' or 'ps 3071(continued): '. 3072: 'yy' on a line without 'yyyy' found at line 3071: 3069: 3070: file /ftp/rfc/rfcnnnn.yyy where 'nnnn' is the RFC n 3070(continued): umber. 3071: and 'yyy' is 'txt' or 'ps 3071(continued): '. 3072: 3073: help to get information on how 3073(continued): to use 1900 found at line 1264: 1262: This memo. 1263: 1264: 1999 - Request for Comments Summary RFC Numbers 1900-1999 1265: 1266: This is an information document and does not specif 1266(continued): y any 2000 found at line 8: 6: 7: Network Working Group Internet Architectu 7(continued): re Board 8: Request for Comments: 2000 J. Postel 8(continued): , Editor
9: Obsoletes: 1920, 1880, 1800, 1780, 1720, Febru 9(continued): ary 1997 10: 1610, 1600, 1540, 1500, 1410, 1360, 2000 found at line 60: 58: Internet Architecture Board Standards Track 58(continued): [Page 1] 59: 60: RFC 2000 Internet Standards Febru 60(continued): ary 1997 61: 62: 2000 found at line 116: 114: Internet Architecture Board Standards Track 114(continued): [Page 2] 115: 116: RFC 2000 Internet Standards Febru 116(continued): ary 1997 117: 118: 2000 found at line 172: 170: Internet Architecture Board Standards Track 170(continued): [Page 3] 171: 172: RFC 2000 Internet Standards Febru 172(continued): ary 1997 173: 174: 2000 found at line 228: 226: Internet Architecture Board Standards Track 226(continued): [Page 4] 227: 228: RFC 2000 Internet Standards Febru 228(continued): ary 1997 229: 230: 2000 found at line 284: 282: Internet Architecture Board Standards Track 282(continued): [Page 5] 283: 284: RFC 2000 Internet Standards Febru 284(continued): ary 1997 285: 286:
2000 found at line 340: 338: Internet Architecture Board Standards Track 338(continued): [Page 6] 339: 340: RFC 2000 Internet Standards Febru 340(continued): ary 1997 341: 342: 2000 found at line 396: 394: Internet Architecture Board Standards Track 394(continued): [Page 7] 395: 396: RFC 2000 Internet Standards Febru 396(continued): ary 1997 397: 398: 2000 found at line 452: 450: Internet Architecture Board Standards Track 450(continued): [Page 8] 451: 452: RFC 2000 Internet Standards Febru 452(continued): ary 1997 453: 454: 2000 found at line 508: 506: Internet Architecture Board Standards Track 506(continued): [Page 9] 507: 508: RFC 2000 Internet Standards Febru 508(continued): ary 1997 509: 510: 2000 found at line 564: 562: Internet Architecture Board Standards Track [ 562(continued): Page 10] 563: 564: RFC 2000 Internet Standards Febru 564(continued): ary 1997 565: 566: 2000 found at line 620: 618: Internet Architecture Board Standards Track [ 618(continued): Page 11]
619: 620: RFC 2000 Internet Standards Febru 620(continued): ary 1997 621: 622: 2000 found at line 676: 674: Internet Architecture Board Standards Track [ 674(continued): Page 12] 675: 676: RFC 2000 Internet Standards Febru 676(continued): ary 1997 677: 678: 2000 found at line 732: 730: Internet Architecture Board Standards Track [ 730(continued): Page 13] 731: 732: RFC 2000 Internet Standards Febru 732(continued): ary 1997 733: 734: 2000 found at line 788: 786: Internet Architecture Board Standards Track [ 786(continued): Page 14] 787: 788: RFC 2000 Internet Standards Febru 788(continued): ary 1997 789: 790: 2000 found at line 844: 842: Internet Architecture Board Standards Track [ 842(continued): Page 15] 843: 844: RFC 2000 Internet Standards Febru 844(continued): ary 1997 845: 846: 2000 found at line 900: 898: Internet Architecture Board Standards Track [ 898(continued): Page 16] 899:
900: RFC 2000 Internet Standards Febru 900(continued): ary 1997 901: 902: 2000 found at line 956: 954: Internet Architecture Board Standards Track [ 954(continued): Page 17] 955: 956: RFC 2000 Internet Standards Febru 956(continued): ary 1997 957: 958: 2000 found at line 1012: 1010: Internet Architecture Board Standards Track [ 1010(continued): Page 18] 1011: 1012: RFC 2000 Internet Standards Febru 1012(continued): ary 1997 1013: 1014: 2000 found at line 1068: 1066: Internet Architecture Board Standards Track [ 1066(continued): Page 19] 1067: 1068: RFC 2000 Internet Standards Febru 1068(continued): ary 1997 1069: 1070: 2000 found at line 1124: 1122: Internet Architecture Board Standards Track [ 1122(continued): Page 20] 1123: 1124: RFC 2000 Internet Standards Febru 1124(continued): ary 1997 1125: 1126: 2000 found at line 1180: 1178: Internet Architecture Board Standards Track [ 1178(continued): Page 21] 1179:
1180: RFC 2000 Internet Standards Febru 1180(continued): ary 1997 1181: 1182: 2000 found at line 1236: 1234: Internet Architecture Board Standards Track [ 1234(continued): Page 22] 1235: 1236: RFC 2000 Internet Standards Febru 1236(continued): ary 1997 1237: 1238: 2000 found at line 1260: 1258: A Proposed Standard protocol. 1259: 1260: 2000 - Internet Official Protocol Standards 1261: 1262: This memo. 2000 found at line 1292: 1290: Internet Architecture Board Standards Track [ 1290(continued): Page 23] 1291: 1292: RFC 2000 Internet Standards Febru 1292(continued): ary 1997 1293: 1294: 2000 found at line 1348: 1346: Internet Architecture Board Standards Track [ 1346(continued): Page 24] 1347: 1348: RFC 2000 Internet Standards Febru 1348(continued): ary 1997 1349: 1350: 2000 found at line 1404: 1402: Internet Architecture Board Standards Track [ 1402(continued): Page 25] 1403: 1404: RFC 2000 Internet Standards Febru 1404(continued): ary 1997 1405: 1406:
2000 found at line 1460: 1458: Internet Architecture Board Standards Track [ 1458(continued): Page 26] 1459: 1460: RFC 2000 Internet Standards Febru 1460(continued): ary 1997 1461: 1462: 2000 found at line 1516: 1514: Internet Architecture Board Standards Track [ 1514(continued): Page 27] 1515: 1516: RFC 2000 Internet Standards Febru 1516(continued): ary 1997 1517: 1518: 2000 found at line 1572: 1570: Internet Architecture Board Standards Track [ 1570(continued): Page 28] 1571: 1572: RFC 2000 Internet Standards Febru 1572(continued): ary 1997 1573: 1574: 2000 found at line 1628: 1626: Internet Architecture Board Standards Track [ 1626(continued): Page 29] 1627: 1628: RFC 2000 Internet Standards Febru 1628(continued): ary 1997 1629: 1630: 2000 found at line 1684: 1682: Internet Architecture Board Standards Track [ 1682(continued): Page 30] 1683: 1684: RFC 2000 Internet Standards Febru 1684(continued): ary 1997 1685: 1686: 2000 found at line 1740: 1738: Internet Architecture Board Standards Track [ 1738(continued): Page 31]
1739: 1740: RFC 2000 Internet Standards Febru 1740(continued): ary 1997 1741: 1742: 2000 found at line 1796: 1794: Internet Architecture Board Standards Track [ 1794(continued): Page 32] 1795: 1796: RFC 2000 Internet Standards Febru 1796(continued): ary 1997 1797: 1798: 2000 found at line 1852: 1850: Internet Architecture Board Standards Track [ 1850(continued): Page 33] 1851: 1852: RFC 2000 Internet Standards Febru 1852(continued): ary 1997 1853: 1854: 2000 found at line 1859: 1857: Protocol Name Status R 1857(continued): FC STD * 1858: ======== ===================================== ======== == 1858(continued): == === = 1859: -------- Internet Official Protocol Standards Req 20 1859(continued): 00 1 1860: -------- Assigned Numbers Req 17 1860(continued): 00 2 1861: -------- Host Requirements - Communications Req 11 1861(continued): 22 3 2000 found at line 1908: 1906: Internet Architecture Board Standards Track [ 1906(continued): Page 34] 1907: 1908: RFC 2000 Internet Standards Febru 1908(continued): ary 1997 1909: 1910: 2000 found at line 1964: 1962: Internet Architecture Board Standards Track [ 1962(continued): Page 35]
1963: 1964: RFC 2000 Internet Standards Febru 1964(continued): ary 1997 1965: 1966: 2000 found at line 2020: 2018: Internet Architecture Board Standards Track [ 2018(continued): Page 36] 2019: 2020: RFC 2000 Internet Standards Febru 2020(continued): ary 1997 2021: 2022: 2000 found at line 2076: 2074: Internet Architecture Board Standards Track [ 2074(continued): Page 37] 2075: 2076: RFC 2000 Internet Standards Febru 2076(continued): ary 1997 2077: 2078: 2000 found at line 2132: 2130: Internet Architecture Board Standards Track [ 2130(continued): Page 38] 2131: 2132: RFC 2000 Internet Standards Febru 2132(continued): ary 1997 2133: 2134: 2000 found at line 2188: 2186: Internet Architecture Board Standards Track [ 2186(continued): Page 39] 2187: 2188: RFC 2000 Internet Standards Febru 2188(continued): ary 1997 2189: 2190: 2000 found at line 2244: 2242: Internet Architecture Board Standards Track [ 2242(continued): Page 40] 2243: 2244: RFC 2000 Internet Standards Febru 2244(continued): ary 1997
2245: 2246: 2000 found at line 2300: 2298: Internet Architecture Board Standards Track [ 2298(continued): Page 41] 2299: 2300: RFC 2000 Internet Standards Febru 2300(continued): ary 1997 2301: 2302: 2000 found at line 2356: 2354: Internet Architecture Board Standards Track [ 2354(continued): Page 42] 2355: 2356: RFC 2000 Internet Standards Febru 2356(continued): ary 1997 2357: 2358: 2000 found at line 2412: 2410: Internet Architecture Board Standards Track [ 2410(continued): Page 43] 2411: 2412: RFC 2000 Internet Standards Febru 2412(continued): ary 1997 2413: 2414: 2000 found at line 2468: 2466: Internet Architecture Board Standards Track [ 2466(continued): Page 44] 2467: 2468: RFC 2000 Internet Standards Febru 2468(continued): ary 1997 2469: 2470: 2000 found at line 2524: 2522: Internet Architecture Board Standards Track [ 2522(continued): Page 45] 2523: 2524: RFC 2000 Internet Standards Febru 2524(continued): ary 1997 2525: 2526:
2000 found at line 2580: 2578: Internet Architecture Board Standards Track [ 2578(continued): Page 46] 2579: 2580: RFC 2000 Internet Standards Febru 2580(continued): ary 1997 2581: 2582: 2000 found at line 2636: 2634: Internet Architecture Board Standards Track [ 2634(continued): Page 47] 2635: 2636: RFC 2000 Internet Standards Febru 2636(continued): ary 1997 2637: 2638: 2000 found at line 2692: 2690: Internet Architecture Board Standards Track [ 2690(continued): Page 48] 2691: 2692: RFC 2000 Internet Standards Febru 2692(continued): ary 1997 2693: 2694: 2000 found at line 2748: 2746: Internet Architecture Board Standards Track [ 2746(continued): Page 49] 2747: 2748: RFC 2000 Internet Standards Febru 2748(continued): ary 1997 2749: 2750: 2000 found at line 2804: 2802: Internet Architecture Board Standards Track [ 2802(continued): Page 50] 2803: 2804: RFC 2000 Internet Standards Febru 2804(continued): ary 1997 2805: 2806: 2000 found at line 2860: 2858: Internet Architecture Board Standards Track [ 2858(continued): Page 51]
2859: 2860: RFC 2000 Internet Standards Febru 2860(continued): ary 1997 2861: 2862: 2000 found at line 2916: 2914: Internet Architecture Board Standards Track [ 2914(continued): Page 52] 2915: 2916: RFC 2000 Internet Standards Febru 2916(continued): ary 1997 2917: 2918: 2000 found at line 2972: 2970: Internet Architecture Board Standards Track [ 2970(continued): Page 53] 2971: 2972: RFC 2000 Internet Standards Febru 2972(continued): ary 1997 2973: 2974: 2000 found at line 3028: 3026: Internet Architecture Board Standards Track [ 3026(continued): Page 54] 3027: 3028: RFC 2000 Internet Standards Febru 3028(continued): ary 1997 3029: 3030: 2000 found at line 3084: 3082: Internet Architecture Board Standards Track [ 3082(continued): Page 55] 3083: 3084: RFC 2000 Internet Standards Febru 3084(continued): ary 1997 3085: 3086: +=+=+=+=+= File rfc2007.txt +=+=+=+=+= 2000 found at line 1156: 1154: 1155: Access-Type: gopher
1156: URL: <URL:gopher://gopher.cic.net:2000/11/hunt> 1157: 1158: Access-Type: www +=+=+=+=+= File rfc2015.txt +=+=+=+=+= 'yy' on a line without 'yyyy' found at line 153: 151: 152: hIwDY32hYGCE8MkBA/wOu7d45aUxF4Q0RKJprD3v5Z9K1YcRJ2fve87lMlD 152(continued): lx4Oj 153: eW4GDdBfLbJE7VUpp13N19GL8e/AqbyyjHH4aS0YoTk10QQ9nnRvjY8nZL3 153(continued): MPXSZ 154: g9VGQxFeGqzykzmykU6A26MSMexR4ApeeON6xzZWfo+0yOqAq6lb46wsvld 154(continued): Z96YA 155: AABH78hyX7YX4uT1tNCWEIIBoqqvCeIMpp7UQ2IzBrXg6GtukS8NxbukLea 155(continued): mqVW3 +=+=+=+=+= File rfc2025.txt +=+=+=+=+= UTCTime found at line 751: 749: context-id Random-Integer, -- see Section 6.3 749(continued): 750: pvno BIT STRING, -- protocol versio 750(continued): n number 751: timestamp UTCTime OPTIONAL, -- mandatory for S 751(continued): PKM-2 752: randSrc Random-Integer, 753: targ-name Name, UTCTime found at line 923: 921: context-id Random-Integer, -- see Section 6.3 922: pvno [0] BIT STRING OPTIONAL, -- prot. versio 922(continued): n number 923: timestamp UTCTime OPTIONAL, -- mandatory for S 923(continued): PKM-2 924: randTarg Random-Integer, 925: src-name [1] Name OPTIONAL, UTCTime found at line 2159: 2157: context-id Random-Integer, 2158: pvno BIT STRING, 2159: timestamp UTCTime OPTIONAL, -- mandatory for S 2159(continued): PKM-2 2160: randSrc Random-Integer, 2161: targ-name Name, UTCTime found at line 2248: 2246: 2247: pvno [0] BIT STRING OPTIONAL, 2248: timestamp UTCTime OPTIONAL, -- mandatory for S
2248(continued): PKM-2
2249: randTarg Random-Integer,
2250: src-name [1] Name OPTIONAL,
UTCTime found at line 2459:
2457:
2458: Validity ::= SEQUENCE {
2459: notBefore UTCTime,
2460: notAfter UTCTime
2461: }
UTCTime found at line 2460:
2458: Validity ::= SEQUENCE {
2459: notBefore UTCTime,
2460: notAfter UTCTime
2461: }
2462:
UTCTime found at line 2493:
2491: signature AlgorithmIdentifier,
2492: issuer Name,
2493: thisUpdate UTCTime,
2494: nextUpdate UTCTime OPTIONAL,
2495: revokedCertificates SEQUENCE OF SEQUENCE {
UTCTime found at line 2494:
2492: issuer Name,
2493: thisUpdate UTCTime,
2494: nextUpdate UTCTime OPTIONAL,
2495: revokedCertificates SEQUENCE OF SEQUENCE {
2496: userCertificate CertificateSerialNumber,
UTCTime found at line 2497:
2495: revokedCertificates SEQUENCE OF SEQUENCE {
2496: userCertificate CertificateSerialNumber,
2497: revocationDate UTCTime } OPTION
2497(continued): AL
2498: }
2499:
+=+=+=+=+= File rfc2028.txt +=+=+=+=+=
2000 found at line 320:
318: Digital Equipment Corporation
319: 1401 H Street NW
320: Washington DC 20005
321:
322: Phone: +1 202 383 5615
+=+=+=+=+= File rfc2030.txt +=+=+=+=+= 1900 found at line 321: 319: main product of the protocol, a special timestamp format has 319(continued): been 320: established. NTP timestamps are represented as a 64-bit unsig 320(continued): ned 321: fixed-point number, in seconds relative to 0h on 1 January 19 321(continued): 00. The 322: integer part is in the first 32 bits and the fraction part in 322(continued): the 323: last 32 bits. In the fraction part, the non-significant low o 323(continued): rder can 1900 found at line 362: 360: 64-bit field will overflow some time in 2036 (second 4,294,96 360(continued): 7,296). 361: Should NTP or SNTP be in use in 2036, some external means wil 361(continued): l be 362: necessary to qualify time relative to 1900 and time relative 362(continued): to 2036 363: (and other multiples of 136 years). There will exist a 200-pi 363(continued): cosecond 364: interval, henceforth ignored, every 136 years when the 64-bit 364(continued): field 1900 found at line 375: 373: following convention: If bit 0 is set, the UTC time is in 373(continued): the 374: range 1968-2036 and UTC time is reckoned from 0h 0m 0s UTC 374(continued): on 1 375: January 1900. If bit 0 is not set, the time is in the rang 375(continued): e 2036- 376: 2104 and UTC time is reckoned from 6h 28m 16s UTC on 7 Feb 376(continued): ruary 377: 2036. Note that when calculating the correspondence, 2000 377(continued): is not a 2000 found at line 377: 375: January 1900. If bit 0 is not set, the time is in the rang 375(continued): e 2036- 376: 2104 and UTC time is reckoned from 6h 28m 16s UTC on 7 Feb 376(continued): ruary 377: 2036. Note that when calculating the correspondence, 2000 377(continued): is not a 378: leap year. Note also that leap seconds are not counted in 378(continued): the 379: reckoning.
+=+=+=+=+= File rfc2048.txt +=+=+=+=+= 'yy' on a line without 'yyyy' found at line 738: 736: 737: To: ietf-types@iana.org 738: Subject: Registration of MIME media type XXX/YYY 739: 740: MIME media type name: +=+=+=+=+= File rfc2050.txt +=+=+=+=+= 1900 found at line 638: 636: [RFC 1814] Gerich, E., "Unique Addresses are Good", June 1995 636(continued): . 637: 638: [RFC 1900] Carpenter, B., and Y. Rekhter, "Renumbering Needs 638(continued): Work", 639: February 1996. 640: +=+=+=+=+= File rfc2052.txt +=+=+=+=+= 1900 found at line 420: 418: Errors", RFC 1912, February 1996. 419: 420: RFC 1900: Carpenter, B., and Y. Rekhter, "Renumbering Needs W 420(continued): ork", 421: RFC 1900, February 1996. 422: 1900 found at line 421: 419: 420: RFC 1900: Carpenter, B., and Y. Rekhter, "Renumbering Needs W 420(continued): ork", 421: RFC 1900, February 1996. 422: 423: RFC 1920: Postel, J., "INTERNET OFFICIAL PROTOCOL STANDARDS", 423(continued): +=+=+=+=+= File rfc2060.txt +=+=+=+=+= 2digit found at line 3782: 3780: date ::= date_text / <"> date_text <"> 3781: 3782: date_day ::= 1*2digit 3783: ;; Day of month 3784: 2digit found at line 3785: 3783: ;; Day of month 3784:
3785: date_day_fixed ::= (SPACE digit) / 2digit 3786: ;; Fixed-format version of date_day 3787: 2digit found at line 4101: 4099: TEXT_CHAR ::= <any CHAR except CR and LF> 4100: 4101: time ::= 2digit ":" 2digit ":" 2digit 4102: ;; Hours minutes seconds 4103: +=+=+=+=+= File rfc2062.txt +=+=+=+=+= 2digit found at line 330: 328: ::= partial 329: 330: date_year_old ::= 2digit 331: ;; (year - 1900) 332: 1900 found at line 331: 329: 330: date_year_old ::= 2digit 331: ;; (year - 1900) 332: 333: date_time_old ::= <"> date_day_fixed "-" date_month "-" dat 333(continued): e_year +=+=+=+=+= File rfc2063.txt +=+=+=+=+= 2000 found at line 716: 714: 715: start time = 1 start time = 715(continued): 1 716: Usage record N: flow count = 2000 flow count = 200 716(continued): 0 (done) 717: 718: start time = 1 start time = 718(continued): 5 2000 found at line 725: 723: 724: In the continuing flow case, the same flow was reported when 724(continued): its 725: count was 2000, and again at 3000: the total count to date i 725(continued): s 3000. 726: In the OLD/NEW case, the old flow had a count of 2000. Its r 726(continued): ecord 727:
2000 found at line 726: 724: In the continuing flow case, the same flow was reported when 724(continued): its 725: count was 2000, and again at 3000: the total count to date i 725(continued): s 3000. 726: In the OLD/NEW case, the old flow had a count of 2000. Its r 726(continued): ecord 727: 728: +=+=+=+=+= File rfc2068.txt +=+=+=+=+= 2-digit found at line 772: 770: Specific repetition: "<n>(element)" is equivalent to 771: "<n>*<n>(element)"; that is, exactly <n> occurrences of (el 771(continued): ement). 772: Thus 2DIGIT is a 2-digit number, and 3ALPHA is a string of 772(continued): three 773: alphabetic characters. 774: 2digit found at line 772: 770: Specific repetition: "<n>(element)" is equivalent to 771: "<n>*<n>(element)"; that is, exactly <n> occurrences of (el 771(continued): ement). 772: Thus 2DIGIT is a 2-digit number, and 3ALPHA is a string of 772(continued): three 773: alphabetic characters. 774: 2digit found at line 1163: 1161: asctime-date = wkday SP date3 SP time SP 4DIGIT 1162: 1163: date1 = 2DIGIT SP month SP 4DIGIT 1164: ; day month year (e.g., 02 Jun 1982) 1165: date2 = 2DIGIT "-" month "-" 2DIGIT 2digit found at line 1165: 1163: date1 = 2DIGIT SP month SP 4DIGIT 1164: ; day month year (e.g., 02 Jun 1982) 1165: date2 = 2DIGIT "-" month "-" 2DIGIT 1166: ; day-month-year (e.g., 02-Jun-82) 1167: date3 = month SP ( 2DIGIT | ( SP 1DIGIT ))
2digit found at line 1167: 1165: date2 = 2DIGIT "-" month "-" 2DIGIT 1166: ; day-month-year (e.g., 02-Jun-82) 1167: date3 = month SP ( 2DIGIT | ( SP 1DIGIT )) 1168: ; month day (e.g., Jun 2) 1169: 2digit found at line 1170: 1168: ; month day (e.g., Jun 2) 1169: 1170: time = 2DIGIT ":" 2DIGIT ":" 2DIGIT 1171: ; 00:00:00 - 23:59:59 1172: 2digit found at line 7652: 7650: 7651: warning-value = warn-code SP warn-agent SP warn-text 7652: warn-code = 2DIGIT 7653: warn-agent = ( host [ ":" port ] ) | pseudonym 7654: ; the name or pseudonym of the server 7654(continued): adding 1900 found at line 1083: 1081: for TCP connections on that port of that host, and the Reques 1081(continued): t-URI 1082: for the resource is abs_path. The use of IP addresses in URL' 1082(continued): s SHOULD 1083: be avoided whenever possible (see RFC 1900 [24]). If the abs_ 1083(continued): path is 1084: not present in the URL, it MUST be given as "/" when used as 1084(continued): a 1085: Request-URI for a resource (section 5.1.2). 1900 found at line 8249: 8247: 8248: [24] Carpenter, B., and Y. Rekhter, "Renumbering Needs Work", 8248(continued): RFC 8249: 1900, IAB, February 1996. 8250: 8251: [25] Deutsch, P., "GZIP file format specification version 4.3 8251(continued): ." RFC 2000 found at line 8453: 8451: o HTTP/1.1 clients and caches should assume that an RFC-850 d 8451(continued): ate 8452: which appears to be more than 50 years in the future is in 8452(continued): fact
8453: in the past (this helps solve the "year 2000" problem). 8454: 8455: +=+=+=+=+= File rfc2071.txt +=+=+=+=+= 1900 found at line 738: 736: December 1995. 737: 738: [16] Carpenter, B., and Y. Rekhter, "Renumbering Needs Work", R 738(continued): FC 1900, 739: February 1996. 740: +=+=+=+=+= File rfc2072.txt +=+=+=+=+= 1900 found at line 206: 204: Many discussions of renumbering emphasize interactions among 205: organizations' numbering plans and those of the global Intern 205(continued): et 206: [RFC1900]. There can be equally strong motivations for renum 206(continued): bering 207: in organizations that never connect to the global Internet. 208: 1900 found at line 209: 207: in organizations that never connect to the global Internet. 208: 209: According to RFC1900, "Unless and until viable alternatives a 209(continued): re 210: developed, extended deployment of Classless Inter-Domain Rout 210(continued): ing 211: (CIDR) is vital to keep the Internet routing system alive and 211(continued): to 1900 found at line 2606: 2604: February 1996. 2605: 2606: [RFC1900] Carpenter, B., and Y. Rekhter, "Renumbering Needs Wo 2606(continued): rk", RFC 2607: 1900, February 1996. 2608: 1900 found at line 2607: 2605: 2606: [RFC1900] Carpenter, B., and Y. Rekhter, "Renumbering Needs Wo 2606(continued): rk", RFC 2607: 1900, February 1996.
2608: 2609: [RPS] Alaettinoglu, C., Bates, T., Gerich, E., Terpstra, M., a 2609(continued): nd C. +=+=+=+=+= File rfc2074.txt +=+=+=+=+= 2000 found at line 2041: 2039: From [RFC1831]: 2040: 2041: Program numbers are given out in groups of hexadecimal 20 2041(continued): 000000 2042: (decimal 536870912) according to the following chart: 2043: 2000 found at line 2045: 2043: 2044: 0 - 1fffffff defined by rpc@sun.com 2045: 20000000 - 3fffffff defined by user 2046: 40000000 - 5fffffff transient 2047: 60000000 - 7fffffff reserved +=+=+=+=+= File rfc2077.txt +=+=+=+=+= 'yy' on a line without 'yyyy' found at line 315: 313: Subject: model data file 314: 315: I1ZSTUwgVjEuMCBhc2NpaQojIFRoaXMgZmlsZSB3YXMgIGdlbmVyY.. 315(continued): . 316: byBDb21tdW5pY2F0aW9ucwojIGh0dHA6Ly93d3cuY2hhY28uY29tC.. 316(continued): . 317: IyB1c2VkIGluIHJvb20gMTkyICh0ZXN0IHJvb20pCiAgIAojIFRvc.. 317(continued): . +=+=+=+=+= File rfc2095.txt +=+=+=+=+= 'yy' on a line without 'yyyy' found at line 131: 129: C: A0001 AUTHENTICATE CRAM-MD5 130: S: + PDE4OTYuNjk3MTcwOTUyQHBvc3RvZmZpY2UucmVzdG9uLm1jaS5uZX 130(continued): Q+ 131: C: dGltIGI5MTNhNjAyYzdlZGE3YTQ5NWI0ZTZlNzMzNGQzODkw 132: S: A0001 OK CRAM authentication successful 133: 'yy' on a line without 'yyyy' found at line 161: 159: AUTHENTICATE command (or the similar POP3 AUTH command), y 159(continued): ielding 160: 161: dGltIGI5MTNhNjAyYzdlZGE3YTQ5NWI0ZTZlNzMzNGQzODkw 162: 163:
+=+=+=+=+= File rfc2096.txt +=+=+=+=+= 1900 found at line 134: 132: 133: ipForward MODULE-IDENTITY 134: LAST-UPDATED "9609190000Z" -- Thu Sep 26 16:34:47 PDT 19 134(continued): 96 135: ORGANIZATION "IETF OSPF Working Group" 136: CONTACT-INFO 1900 found at line 147: 145: DESCRIPTION 146: "The MIB module for the display of CIDR multipath IP 146(continued): Routes." 147: REVISION "9609190000Z" 148: DESCRIPTION 149: "Revisions made by the OSPF WG." +=+=+=+=+= File rfc2099.txt +=+=+=+=+= 2000 found at line 14: 12: Request for Comments Summary 13: 14: RFC Numbers 2000-2099 15: 16: Status of This Memo 2000 found at line 18: 16: Status of This Memo 17: 18: This RFC is a slightly annotated list of the 100 RFCs from RF 18(continued): C 2000 19: through RFCs 2099. This is a status report on these RFCs. T 19(continued): his memo 20: provides information for the Internet community. It does not 20(continued): specify 2000 found at line 60: 58: Elliott Informational 58(continued): [Page 1] 59: 60: RFC 2099 Summary of 2000-2099 Ma 60(continued): rch 1997 61: 62: 2000 found at line 116: 114: Elliott Informational 114(continued): [Page 2] 115:
116: RFC 2099 Summary of 2000-2099 Ma 116(continued): rch 1997 117: 118: 2000 found at line 172: 170: Elliott Informational 170(continued): [Page 3] 171: 172: RFC 2099 Summary of 2000-2099 Ma 172(continued): rch 1997 173: 174: 2000 found at line 228: 226: Elliott Informational 226(continued): [Page 4] 227: 228: RFC 2099 Summary of 2000-2099 Ma 228(continued): rch 1997 229: 230: 2000 found at line 284: 282: Elliott Informational 282(continued): [Page 5] 283: 284: RFC 2099 Summary of 2000-2099 Ma 284(continued): rch 1997 285: 286: 2000 found at line 340: 338: Elliott Informational 338(continued): [Page 6] 339: 340: RFC 2099 Summary of 2000-2099 Ma 340(continued): rch 1997 341: 342: 2000 found at line 396: 394: Elliott Informational 394(continued): [Page 7] 395: 396: RFC 2099 Summary of 2000-2099 Ma
396(continued): rch 1997 397: 398: 2000 found at line 452: 450: Elliott Informational 450(continued): [Page 8] 451: 452: RFC 2099 Summary of 2000-2099 Ma 452(continued): rch 1997 453: 454: 2000 found at line 508: 506: Elliott Informational 506(continued): [Page 9] 507: 508: RFC 2099 Summary of 2000-2099 Ma 508(continued): rch 1997 509: 510: 2000 found at line 564: 562: Elliott Informational [ 562(continued): Page 10] 563: 564: RFC 2099 Summary of 2000-2099 Ma 564(continued): rch 1997 565: 566: 2000 found at line 620: 618: Elliott Informational [ 618(continued): Page 11] 619: 620: RFC 2099 Summary of 2000-2099 Ma 620(continued): rch 1997 621: 622: 2000 found at line 676: 674: Elliott Informational [ 674(continued): Page 12] 675: 676: RFC 2099 Summary of 2000-2099 Ma 676(continued): rch 1997 677: 678:
2000 found at line 732: 730: Elliott Informational [ 730(continued): Page 13] 731: 732: RFC 2099 Summary of 2000-2099 Ma 732(continued): rch 1997 733: 734: 2000 found at line 788: 786: Elliott Informational [ 786(continued): Page 14] 787: 788: RFC 2099 Summary of 2000-2099 Ma 788(continued): rch 1997 789: 790: 2000 found at line 844: 842: Elliott Informational [ 842(continued): Page 15] 843: 844: RFC 2099 Summary of 2000-2099 Ma 844(continued): rch 1997 845: 846: 2000 found at line 900: 898: Elliott Informational [ 898(continued): Page 16] 899: 900: RFC 2099 Summary of 2000-2099 Ma 900(continued): rch 1997 901: 902: 2000 found at line 956: 954: Elliott Informational [ 954(continued): Page 17] 955: 956: RFC 2099 Summary of 2000-2099 Ma 956(continued): rch 1997 957: 958: 2000 found at line 1012: 1010: Elliott Informational [ 1010(continued): Page 18]
(next page on part 8)
