Created
July 9, 2020 21:17
-
-
Save 166MMX/292244d470c5e9b9fb47acb530d6ae02 to your computer and use it in GitHub Desktop.
rfc-ref
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| #!/bn/sh | |
| # https://www.rfc-editor.org/rfc/rfc-ref.txt | |
| perl -n -e 'local $\ = "\n",$,=";";/^(RFC[0-9]+) \|\s+((((, )?(RFC|RTR)[0-9]+)+)|(NIC [0-9]+))?\s+\| (.*), "(.*)"(, (RTR [0-9]+))?(, (FYI [0-9]+))?(, (BCP [0-9]+))?(, (STD [0-9]+))?(, (RFC [0-9]+))?(, (DOI [0-9]+\.[0-9]+\/RFC[0-9]+))?, ((January|February|March|April|May|June|July|August|September|October|November|December)( [0-9]{1,2})? [0-9]{4}), <(https?:\/\/.*)>\./; print $1,$2,$8,$9,$11,$13,$15,$17,$19,$21,$23,$25' rfc-ref.txt >rfc-ref.csv |
We can't make this file beautiful and searchable because it's too large.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| ;;;;;;;;;;; | |
| ;;;;;;;;;;; | |
| ;;;;;;;;;;; | |
| ;;;;;;;;;;; | |
| RFC0001;;Crocker, S.;Host Software;;;;;RFC 1;DOI 10.17487/RFC0001;April;https://www.rfc-editor.org/info/rfc1 | |
| RFC0002;;Duvall, B.;Host software;;;;;RFC 2;DOI 10.17487/RFC0002;April;https://www.rfc-editor.org/info/rfc2 | |
| RFC0003;RFC0010;Crocker, S.;Documentation conventions;;;;;RFC 3;DOI 10.17487/RFC0003;April;https://www.rfc-editor.org/info/rfc3 | |
| RFC0004;;Shapiro, E.;Network timetable;;;;;RFC 4;DOI 10.17487/RFC0004;March;https://www.rfc-editor.org/info/rfc4 | |
| RFC0005;;Rulifson, J.;Decode Encode Language (DEL);;;;;RFC 5;DOI 10.17487/RFC0005;June;https://www.rfc-editor.org/info/rfc5 | |
| RFC0006;;Crocker, S.;Conversation with Bob Kahn;;;;;RFC 6;DOI 10.17487/RFC0006;April;https://www.rfc-editor.org/info/rfc6 | |
| RFC0007;;Deloche, G.;Host-IMP interface;;;;;RFC 7;DOI 10.17487/RFC0007;May;https://www.rfc-editor.org/info/rfc7 | |
| RFC0008;;Deloche, G.;ARPA Network Functional Specifications;;;;;RFC 8;DOI 10.17487/RFC0008;May;https://www.rfc-editor.org/info/rfc8 | |
| RFC0009;;Deloche, G.;Host Software;;;;;RFC 9;DOI 10.17487/RFC0009;May;https://www.rfc-editor.org/info/rfc9 | |
| RFC0010;RFC0016;Crocker, S.;Documentation conventions;;;;;RFC 10;DOI 10.17487/RFC0010;July;https://www.rfc-editor.org/info/rfc10 | |
| RFC0011;RFC0033;Deloche, G.;Implementation of the Host - Host Software Procedures in GORDO;;;;;RFC 11;DOI 10.17487/RFC0011;August;https://www.rfc-editor.org/info/rfc11 | |
| RFC0012;;Wingfield, M.;IMP-Host interface flow diagrams;;;;;RFC 12;DOI 10.17487/RFC0012;August;https://www.rfc-editor.org/info/rfc12 | |
| RFC0013;;Cerf, V.;Zero Text Length EOF Message;;;;;RFC 13;DOI 10.17487/RFC0013;August;https://www.rfc-editor.org/info/rfc13 | |
| RFC0015;;Carr, C.;Network subsystem for time sharing hosts;;;;;RFC 15;DOI 10.17487/RFC0015;September;https://www.rfc-editor.org/info/rfc15 | |
| RFC0016;RFC0024;Crocker, S.;M.I.T;;;;;RFC 16;DOI 10.17487/RFC0016;August;https://www.rfc-editor.org/info/rfc16 | |
| RFC0017;;Kreznar, J.;Some questions re: Host-IMP Protocol;;;;;RFC 17;DOI 10.17487/RFC0017;August;https://www.rfc-editor.org/info/rfc17 | |
| RFC0018;;Cerf, V.;IMP-IMP and HOST-HOST Control Links;;;;;RFC 18;DOI 10.17487/RFC0018;September;https://www.rfc-editor.org/info/rfc18 | |
| RFC0019;;Kreznar, J.;Two protocol suggestions to reduce congestion at swap bound nodes;;;;;RFC 19;DOI 10.17487/RFC0019;October;https://www.rfc-editor.org/info/rfc19 | |
| RFC0020;;Cerf, V.;ASCII format for network interchange;;;;STD 80;RFC 20;DOI 10.17487/RFC0020;October;https://www.rfc-editor.org/info/rfc20 | |
| RFC0021;;Cerf, V.;Network meeting;;;;;RFC 21;DOI 10.17487/RFC0021;October;https://www.rfc-editor.org/info/rfc21 | |
| RFC0022;;Cerf, V.;Host-host control message formats;;;;;RFC 22;DOI 10.17487/RFC0022;October;https://www.rfc-editor.org/info/rfc22 | |
| RFC0023;;Gregg, G.;Transmission of Multiple Control Messages;;;;;RFC 23;DOI 10.17487/RFC0023;October;https://www.rfc-editor.org/info/rfc23 | |
| RFC0024;;Crocker, S.;Documentation Conventions;;;;;RFC 24;DOI 10.17487/RFC0024;November;https://www.rfc-editor.org/info/rfc24 | |
| RFC0025;;Crocker, S.;No High Link Numbers;;;;;RFC 25;DOI 10.17487/RFC0025;October;https://www.rfc-editor.org/info/rfc25 | |
| RFC0027;;Crocker, S.;Documentation Conventions;;;;;RFC 27;DOI 10.17487/RFC0027;December;https://www.rfc-editor.org/info/rfc27 | |
| RFC0028;;English, W.;Time Standards;;;;;RFC 28;DOI 10.17487/RFC0028;January;https://www.rfc-editor.org/info/rfc28 | |
| RFC0029;;Kahn, R.;Response to RFC 28;;;;;RFC 29;DOI 10.17487/RFC0029;January;https://www.rfc-editor.org/info/rfc29 | |
| RFC0030;;Crocker, S.;Documentation Conventions;;;;;RFC 30;DOI 10.17487/RFC0030;February;https://www.rfc-editor.org/info/rfc30 | |
| RFC0031;;Bobrow, D. and W. Sutherland;Binary Message Forms in Computer;;;;;RFC 31;DOI 10.17487/RFC0031;February;https://www.rfc-editor.org/info/rfc31 | |
| RFC0032;;Cole, J.;Some Thoughts on SRI's Proposed Real Time Clock;;;;;RFC 32;DOI 10.17487/RFC0032;February;https://www.rfc-editor.org/info/rfc32 | |
| RFC0033;;Crocker, S.;New Host-Host Protocol;;;;;RFC 33;DOI 10.17487/RFC0033;February;https://www.rfc-editor.org/info/rfc33 | |
| RFC0034;;English, W.;Some Brief Preliminary Notes on the Augmentation Research Center Clock;;;;;RFC 34;DOI 10.17487/RFC0034;February;https://www.rfc-editor.org/info/rfc34 | |
| RFC0035;;Crocker, S.;Network Meeting;;;;;RFC 35;DOI 10.17487/RFC0035;March;https://www.rfc-editor.org/info/rfc35 | |
| RFC0036;;Crocker, S.;Protocol Notes;;;;;RFC 36;DOI 10.17487/RFC0036;March;https://www.rfc-editor.org/info/rfc36 | |
| RFC0037;;Crocker, S.;Network Meeting Epilogue, etc;;;;;RFC 37;DOI 10.17487/RFC0037;March;https://www.rfc-editor.org/info/rfc37 | |
| RFC0038;;Wolfe, S.;Comments on Network Protocol from NWG/RFC #36;;;;;RFC 38;DOI 10.17487/RFC0038;March;https://www.rfc-editor.org/info/rfc38 | |
| RFC0039;;Harslem, E. and J. Heafner;Comments on Protocol Re: NWG/RFC #36;;;;;RFC 39;DOI 10.17487/RFC0039;March;https://www.rfc-editor.org/info/rfc39 | |
| RFC0040;;Harslem, E. and J. Heafner;More Comments on the Forthcoming Protocol;;;;;RFC 40;DOI 10.17487/RFC0040;March;https://www.rfc-editor.org/info/rfc40 | |
| RFC0041;;Melvin, J.;IMP-IMP Teletype Communication;;;;;RFC 41;DOI 10.17487/RFC0041;March;https://www.rfc-editor.org/info/rfc41 | |
| RFC0042;;Ancona, E.;Message Data Types;;;;;RFC 42;DOI 10.17487/RFC0042;March;https://www.rfc-editor.org/info/rfc42 | |
| RFC0043;;Nemeth, A.;Proposed Meeting;;;;;RFC 43;DOI 10.17487/RFC0043;April;https://www.rfc-editor.org/info/rfc43 | |
| RFC0044;;Shoshani, A., Long, R., and A. Landsberg;Comments on NWG/RFC 33 and 36;;;;;RFC 44;DOI 10.17487/RFC0044;April;https://www.rfc-editor.org/info/rfc44 | |
| RFC0045;;Postel, J. and S. Crocker;New Protocol is Coming;;;;;RFC 45;DOI 10.17487/RFC0045;April;https://www.rfc-editor.org/info/rfc45 | |
| RFC0046;;Meyer, E.;ARPA Network protocol notes;;;;;RFC 46;DOI 10.17487/RFC0046;April;https://www.rfc-editor.org/info/rfc46 | |
| RFC0047;;Postel, J. and S. Crocker;BBN's Comments on NWG/RFC #33;;;;;RFC 47;DOI 10.17487/RFC0047;April;https://www.rfc-editor.org/info/rfc47 | |
| RFC0048;;Postel, J. and S. Crocker;Possible protocol plateau;;;;;RFC 48;DOI 10.17487/RFC0048;April;https://www.rfc-editor.org/info/rfc48 | |
| RFC0049;;Meyer, E.;Conversations with S. Crocker (UCLA);;;;;RFC 49;DOI 10.17487/RFC0049;April;https://www.rfc-editor.org/info/rfc49 | |
| RFC0050;;Harslen, E. and J. Heafner;Comments on the Meyer Proposal;;;;;RFC 50;DOI 10.17487/RFC0050;April;https://www.rfc-editor.org/info/rfc50 | |
| RFC0051;;Elie, M.;Proposal for a Network Interchange Language;;;;;RFC 51;DOI 10.17487/RFC0051;May;https://www.rfc-editor.org/info/rfc51 | |
| RFC0052;;Postel, J. and S. Crocker;Updated distribution list;;;;;RFC 52;DOI 10.17487/RFC0052;July;https://www.rfc-editor.org/info/rfc52 | |
| RFC0053;;Crocker, S.;Official protocol mechanism;;;;;RFC 53;DOI 10.17487/RFC0053;June;https://www.rfc-editor.org/info/rfc53 | |
| RFC0054;;Crocker, S., Postel, J., Newkirk, J., and M. Kraley;Official Protocol Proffering;;;;;RFC 54;DOI 10.17487/RFC0054;June;https://www.rfc-editor.org/info/rfc54 | |
| RFC0055;;Newkirk, J., Kraley, M., Postel, J., and S. Crocker;Prototypical implementation of the NCP;;;;;RFC 55;DOI 10.17487/RFC0055;June;https://www.rfc-editor.org/info/rfc55 | |
| RFC0056;;Belove, E., Black, D., Flegal, R., and L. Farquar;Third Level Protocol: Logger Protocol;;;;;RFC 56;DOI 10.17487/RFC0056;June;https://www.rfc-editor.org/info/rfc56 | |
| RFC0057;;Kraley, M. and J. Newkirk;Thoughts and Reflections on NWG/RFC 54;;;;;RFC 57;DOI 10.17487/RFC0057;June;https://www.rfc-editor.org/info/rfc57 | |
| RFC0058;;Skinner, T.;Logical Message Synchronization;;;;;RFC 58;DOI 10.17487/RFC0058;June;https://www.rfc-editor.org/info/rfc58 | |
| RFC0059;;Meyer, E.;Flow Control - Fixed Versus Demand Allocation;;;;;RFC 59;DOI 10.17487/RFC0059;June;https://www.rfc-editor.org/info/rfc59 | |
| RFC0060;;Kalin, R.;A Simplified NCP Protocol;;;;;RFC 60;DOI 10.17487/RFC0060;July;https://www.rfc-editor.org/info/rfc60 | |
| RFC0061;RFC0062;Walden, D.;Note on Interprocess Communication in a Resource Sharing Computer Network;;;;;RFC 61;DOI 10.17487/RFC0061;July;https://www.rfc-editor.org/info/rfc61 | |
| RFC0062;;Walden, D.;Systems for Interprocess Communication in a Resource Sharing Computer Network;;;;;RFC 62;DOI 10.17487/RFC0062;August;https://www.rfc-editor.org/info/rfc62 | |
| RFC0063;;Cerf, V.;Belated Network Meeting Report;;;;;RFC 63;DOI 10.17487/RFC0063;July;https://www.rfc-editor.org/info/rfc63 | |
| RFC0064;;Elie, M.;Getting rid of marking;;;;;RFC 64;DOI 10.17487/RFC0064;July;https://www.rfc-editor.org/info/rfc64 | |
| RFC0065;;Walden, D.;Comments on Host/Host Protocol document #1;;;;;RFC 65;DOI 10.17487/RFC0065;August;https://www.rfc-editor.org/info/rfc65 | |
| RFC0066;RFC0123;Crocker, S.;NIC - third level ideas and other noise;;;;;RFC 66;DOI 10.17487/RFC0066;August;https://www.rfc-editor.org/info/rfc66 | |
| RFC0067;;Crowther, W.;Proposed Change to Host/IMP Spec to Eliminate Marking;;;;;RFC 67;DOI 10.17487/RFC0067;January;https://www.rfc-editor.org/info/rfc67 | |
| RFC0068;;Elie, M.;Comments on Memory Allocation Control Commands: CEASE, ALL, GVB, RET, and RFNM;;;;;RFC 68;DOI 10.17487/RFC0068;August;https://www.rfc-editor.org/info/rfc68 | |
| RFC0069;;Bhushan, A.;Distribution List Change for MIT;;;;;RFC 69;DOI 10.17487/RFC0069;September;https://www.rfc-editor.org/info/rfc69 | |
| RFC0070;;Crocker, S.;Note on Padding;;;;;RFC 70;DOI 10.17487/RFC0070;October;https://www.rfc-editor.org/info/rfc70 | |
| RFC0071;;Schipper, T.;Reallocation in Case of Input Error;;;;;RFC 71;DOI 10.17487/RFC0071;September;https://www.rfc-editor.org/info/rfc71 | |
| RFC0072;;Bressler, R.;Proposed Moratorium on Changes to Network Protocol;;;;;RFC 72;DOI 10.17487/RFC0072;September;https://www.rfc-editor.org/info/rfc72 | |
| RFC0073;;Crocker, S.;Response to NWG/RFC 67;;;;;RFC 73;DOI 10.17487/RFC0073;September;https://www.rfc-editor.org/info/rfc73 | |
| RFC0074;;White, J.;Specifications for Network Use of the UCSB On-Line System;;;;;RFC 74;DOI 10.17487/RFC0074;October;https://www.rfc-editor.org/info/rfc74 | |
| RFC0075;;Crocker, S.;Network Meeting;;;;;RFC 75;DOI 10.17487/RFC0075;October;https://www.rfc-editor.org/info/rfc75 | |
| RFC0076;;Bouknight, J., Madden, J., and G. Grossman;Connection by name: User oriented protocol;;;;;RFC 76;DOI 10.17487/RFC0076;October;https://www.rfc-editor.org/info/rfc76 | |
| RFC0077;;Postel, J.;Network meeting report;;;;;RFC 77;DOI 10.17487/RFC0077;November;https://www.rfc-editor.org/info/rfc77 | |
| RFC0078;;Harslem, E., Heafner, J., and J. White;NCP Status Report: UCSB/Rand;;;;;RFC 78;DOI 10.17487/RFC0078;October;https://www.rfc-editor.org/info/rfc78 | |
| RFC0079;;Meyer, E.;Logger Protocol error;;;;;RFC 79;DOI 10.17487/RFC0079;November;https://www.rfc-editor.org/info/rfc79 | |
| RFC0080;RFC0123;Harslem, E. and J. Heafner;Protocols and Data Formats;;;;;RFC 80;DOI 10.17487/RFC0080;December;https://www.rfc-editor.org/info/rfc80 | |
| RFC0081;;Bouknight, J.;Request for Reference Information;;;;;RFC 81;DOI 10.17487/RFC0081;December;https://www.rfc-editor.org/info/rfc81 | |
| RFC0082;;Meyer, E.;Network Meeting Notes;;;;;RFC 82;DOI 10.17487/RFC0082;December;https://www.rfc-editor.org/info/rfc82 | |
| RFC0083;;Anderson, R., Harslem, E., and J. Heafner;Language-machine for data reconfiguration;;;;;RFC 83;DOI 10.17487/RFC0083;December;https://www.rfc-editor.org/info/rfc83 | |
| RFC0084;;North, J.;List of NWG/RFC's 1-80;;;;;RFC 84;DOI 10.17487/RFC0084;December;https://www.rfc-editor.org/info/rfc84 | |
| RFC0085;;Crocker, S.;Network Working Group meeting;;;;;RFC 85;DOI 10.17487/RFC0085;December;https://www.rfc-editor.org/info/rfc85 | |
| RFC0086;;Crocker, S.;Proposal for a Network Standard Format for a Data Stream to Control Graphics Display;;;;;RFC 86;DOI 10.17487/RFC0086;January;https://www.rfc-editor.org/info/rfc86 | |
| RFC0087;;Vezza, A.;Topic for Discussion at the Next Network Working Group Meeting;;;;;RFC 87;DOI 10.17487/RFC0087;January;https://www.rfc-editor.org/info/rfc87 | |
| RFC0088;RFC0189;Braden, R. and S. Wolfe;NETRJS: A third level protocol for Remote Job Entry;;;;;RFC 88;DOI 10.17487/RFC0088;January;https://www.rfc-editor.org/info/rfc88 | |
| RFC0089;;Metcalfe, R.;Some historic moments in networking;;;;;RFC 89;DOI 10.17487/RFC0089;January;https://www.rfc-editor.org/info/rfc89 | |
| RFC0090;;Braden, R.;CCN as a Network Service Center;;;;;RFC 90;DOI 10.17487/RFC0090;January;https://www.rfc-editor.org/info/rfc90 | |
| RFC0091;;Mealy, G.;Proposed User-User Protocol;;;;;RFC 91;DOI 10.17487/RFC0091;December;https://www.rfc-editor.org/info/rfc91 | |
| RFC0093;;McKenzie, A.;Initial Connection Protocol;;;;;RFC 93;DOI 10.17487/RFC0093;January;https://www.rfc-editor.org/info/rfc93 | |
| RFC0094;;Harslem, E. and J. Heafner;Some thoughts on Network Graphics;;;;;RFC 94;DOI 10.17487/RFC0094;February;https://www.rfc-editor.org/info/rfc94 | |
| RFC0095;RFC0155;Crocker, S.;Distribution of NWG/RFC's through the NIC;;;;;RFC 95;DOI 10.17487/RFC0095;February;https://www.rfc-editor.org/info/rfc95 | |
| RFC0096;;Watson, R.;An Interactive Network Experiment to Study Modes of Access the Network Information Center;;;;;RFC 96;DOI 10.17487/RFC0096;February;https://www.rfc-editor.org/info/rfc96 | |
| RFC0097;;Melvin, J. and R. Watson;First Cut at a Proposed Telnet Protocol;;;;;RFC 97;DOI 10.17487/RFC0097;February;https://www.rfc-editor.org/info/rfc97 | |
| RFC0098;;Meyer, E. and T. Skinner;Logger Protocol Proposal;;;;;RFC 98;DOI 10.17487/RFC0098;February;https://www.rfc-editor.org/info/rfc98 | |
| RFC0099;;Karp, P.;Network Meeting;;;;;RFC 99;DOI 10.17487/RFC0099;February;https://www.rfc-editor.org/info/rfc99 | |
| RFC0100;;Karp, P.;Categorization and guide to NWG/RFCs;;;;;RFC 100;DOI 10.17487/RFC0100;February;https://www.rfc-editor.org/info/rfc100 | |
| RFC0101;;Watson, R.;Notes on the Network Working Group meeting, Urbana, Illinois, February 17, 1971;;;;;RFC 101;DOI 10.17487/RFC0101;February;https://www.rfc-editor.org/info/rfc101 | |
| RFC0102;;Crocker, S.;Output of the Host-Host Protocol glitch cleaning committee;;;;;RFC 102;DOI 10.17487/RFC0102;February;https://www.rfc-editor.org/info/rfc102 | |
| RFC0103;;Kalin, R.;Implementation of Interrupt Keys;;;;;RFC 103;DOI 10.17487/RFC0103;February;https://www.rfc-editor.org/info/rfc103 | |
| RFC0104;;Postel, J. and S. Crocker;Link 191;;;;;RFC 104;DOI 10.17487/RFC0104;February;https://www.rfc-editor.org/info/rfc104 | |
| RFC0105;;White, J.;Network Specifications for Remote Job Entry and Remote Job Output Retrieval at UCSB;;;;;RFC 105;DOI 10.17487/RFC0105;March;https://www.rfc-editor.org/info/rfc105 | |
| RFC0106;;O'Sullivan, T.;User/Server Site Protocol Network Host Questionnaire;;;;;RFC 106;DOI 10.17487/RFC0106;March;https://www.rfc-editor.org/info/rfc106 | |
| RFC0107;;Bressler, R., Crocker, S., Crowther, W., Grossman, G., Tomlinson, R., and J. White;Output of the Host-Host Protocol Glitch Cleaning Committee;;;;;RFC 107;DOI 10.17487/RFC0107;March;https://www.rfc-editor.org/info/rfc107 | |
| RFC0108;;Watson, R.;Attendance list at the Urbana NWG meeting, February 17-19, 1971;;;;;RFC 108;DOI 10.17487/RFC0108;March;https://www.rfc-editor.org/info/rfc108 | |
| RFC0109;;Winett, J.;Level III Server Protocol for the Lincoln Laboratory 360/67 Host;;;;;RFC 109;DOI 10.17487/RFC0109;March;https://www.rfc-editor.org/info/rfc109 | |
| RFC0110;;Winett, J.;Conventions for Using an IBM 2741 Terminal as a User Console for Access to Network Server Hosts;;;;;RFC 110;DOI 10.17487/RFC0110;March;https://www.rfc-editor.org/info/rfc110 | |
| RFC0111;;Crocker, S.;Pressure from the Chairman;;;;;RFC 111;DOI 10.17487/RFC0111;March;https://www.rfc-editor.org/info/rfc111 | |
| RFC0112;;O'Sullivan, T.;User/Server Site Protocol: Network Host Questionnaire;;;;;RFC 112;DOI 10.17487/RFC0112;April;https://www.rfc-editor.org/info/rfc112 | |
| RFC0113;;Harslem, E., Heafner, J., and J. White;Network activity report: UCSB Rand;;;;;RFC 113;DOI 10.17487/RFC0113;April;https://www.rfc-editor.org/info/rfc113 | |
| RFC0114;;Bhushan, A.;File Transfer Protocol;;;;;RFC 114;DOI 10.17487/RFC0114;April;https://www.rfc-editor.org/info/rfc114 | |
| RFC0115;;Watson, R. and J. North;Some Network Information Center policies on handling documents;;;;;RFC 115;DOI 10.17487/RFC0115;April;https://www.rfc-editor.org/info/rfc115 | |
| RFC0116;;Crocker, S.;Structure of the May NWG Meeting;;;;;RFC 116;DOI 10.17487/RFC0116;April;https://www.rfc-editor.org/info/rfc116 | |
| RFC0117;;Wong, J.;Some comments on the official protocol;;;;;RFC 117;DOI 10.17487/RFC0117;April;https://www.rfc-editor.org/info/rfc117 | |
| RFC0118;;Watson, R.;Recommendations for facility documentation;;;;;RFC 118;DOI 10.17487/RFC0118;April;https://www.rfc-editor.org/info/rfc118 | |
| RFC0119;;Krilanovich, M.;Network Fortran Subprograms;;;;;RFC 119;DOI 10.17487/RFC0119;April;https://www.rfc-editor.org/info/rfc119 | |
| RFC0120;;Krilanovich, M.;Network PL1 subprograms;;;;;RFC 120;DOI 10.17487/RFC0120;April;https://www.rfc-editor.org/info/rfc120 | |
| RFC0121;;Krilanovich, M.;Network on-line operators;;;;;RFC 121;DOI 10.17487/RFC0121;April;https://www.rfc-editor.org/info/rfc121 | |
| RFC0122;;White, J.;Network specifications for UCSB's Simple-Minded File System;;;;;RFC 122;DOI 10.17487/RFC0122;April;https://www.rfc-editor.org/info/rfc122 | |
| RFC0123;RFC0165;Crocker, S.;Proffered Official ICP;;;;;RFC 123;DOI 10.17487/RFC0123;April;https://www.rfc-editor.org/info/rfc123 | |
| RFC0124;;Melvin, J.;Typographical error in RFC 107;;;;;RFC 124;DOI 10.17487/RFC0124;April;https://www.rfc-editor.org/info/rfc124 | |
| RFC0125;;McConnell, J.;Response to RFC 86: Proposal for Network Standard Format for a Graphics Data Stream;;;;;RFC 125;DOI 10.17487/RFC0125;April;https://www.rfc-editor.org/info/rfc125 | |
| RFC0126;;McConnell, J.;Graphics Facilities at Ames Research Center;;;;;RFC 126;DOI 10.17487/RFC0126;April;https://www.rfc-editor.org/info/rfc126 | |
| RFC0127;RFC0145;Postel, J.;Comments on RFC 123;;;;;RFC 127;DOI 10.17487/RFC0127;April;https://www.rfc-editor.org/info/rfc127 | |
| RFC0128;;Postel, J.;Bytes;;;;;RFC 128;DOI 10.17487/RFC0128;April;https://www.rfc-editor.org/info/rfc128 | |
| RFC0129;;Harslem, E., Heafner, J., and E. Meyer;Request for comments on socket name structure;;;;;RFC 129;DOI 10.17487/RFC0129;April;https://www.rfc-editor.org/info/rfc129 | |
| RFC0130;;Heafner, J.;Response to RFC 111: Pressure from the chairman;;;;;RFC 130;DOI 10.17487/RFC0130;April;https://www.rfc-editor.org/info/rfc130 | |
| RFC0131;;Harslem, E. and J. Heafner;Response to RFC 116: May NWG meeting;;;;;RFC 131;DOI 10.17487/RFC0131;April;https://www.rfc-editor.org/info/rfc131 | |
| RFC0132;RFC0154;White, J.;Typographical Error in RFC 107;;;;;RFC 132;DOI 10.17487/RFC0132;April;https://www.rfc-editor.org/info/rfc132 | |
| RFC0133;;Sunberg, R.;File Transfer and Error Recovery;;;;;RFC 133;DOI 10.17487/RFC0133;April;https://www.rfc-editor.org/info/rfc133 | |
| RFC0134;;Vezza, A.;Network Graphics meeting;;;;;RFC 134;DOI 10.17487/RFC0134;April;https://www.rfc-editor.org/info/rfc134 | |
| RFC0135;;Hathaway, W.;Response to NWG/RFC 110;;;;;RFC 135;DOI 10.17487/RFC0135;April;https://www.rfc-editor.org/info/rfc135 | |
| RFC0136;;Kahn, R.;Host accounting and administrative procedures;;;;;RFC 136;DOI 10.17487/RFC0136;April;https://www.rfc-editor.org/info/rfc136 | |
| RFC0137;;O'Sullivan, T.;Telnet Protocol - a proposed document;;;;;RFC 137;DOI 10.17487/RFC0137;April;https://www.rfc-editor.org/info/rfc137 | |
| RFC0138;;Anderson, R., Cerf, V., Harslem, E., Heafner, J., Madden, J., Metcalfe, R., Shoshani, A., White, J., and D. Wood;Status report on proposed Data Reconfiguration Service;;;;;RFC 138;DOI 10.17487/RFC0138;April;https://www.rfc-editor.org/info/rfc138 | |
| RFC0139;;O'Sullivan, T.;Discussion of Telnet Protocol;;;;;RFC 139;DOI 10.17487/RFC0139;May;https://www.rfc-editor.org/info/rfc139 | |
| RFC0140;;Crocker, S.;Agenda for the May NWG meeting;;;;;RFC 140;DOI 10.17487/RFC0140;May;https://www.rfc-editor.org/info/rfc140 | |
| RFC0141;;Harslem, E. and J. Heafner;Comments on RFC 114: A File Transfer Protocol;;;;;RFC 141;DOI 10.17487/RFC0141;April;https://www.rfc-editor.org/info/rfc141 | |
| RFC0142;;Kline, C. and J. Wong;Time-Out Mechanism in the Host-Host Protocol;;;;;RFC 142;DOI 10.17487/RFC0142;May;https://www.rfc-editor.org/info/rfc142 | |
| RFC0143;RFC0165;Naylor, W., Wong, J., Kline, C., and J. Postel;Regarding proffered official ICP;;;;;RFC 143;DOI 10.17487/RFC0143;May;https://www.rfc-editor.org/info/rfc143 | |
| RFC0144;;Shoshani, A.;Data sharing on computer networks;;;;;RFC 144;DOI 10.17487/RFC0144;April;https://www.rfc-editor.org/info/rfc144 | |
| RFC0145;RFC0165;Postel, J.;Initial Connection Protocol Control Commands;;;;;RFC 145;DOI 10.17487/RFC0145;May;https://www.rfc-editor.org/info/rfc145 | |
| RFC0146;;Karp, P., McKay, D., and D. Wood;Views on issues relevant to data sharing on computer networks;;;;;RFC 146;DOI 10.17487/RFC0146;May;https://www.rfc-editor.org/info/rfc146 | |
| RFC0147;;Winett, J.;Definition of a socket;;;;;RFC 147;DOI 10.17487/RFC0147;May;https://www.rfc-editor.org/info/rfc147 | |
| RFC0148;;Bhushan, A.;Comments on RFC 123;;;;;RFC 148;DOI 10.17487/RFC0148;May;https://www.rfc-editor.org/info/rfc148 | |
| RFC0149;;Crocker, S.;Best Laid Plans;;;;;RFC 149;DOI 10.17487/RFC0149;May;https://www.rfc-editor.org/info/rfc149 | |
| RFC0150;;Kalin, R.;Use of IPC Facilities: A Working Paper;;;;;RFC 150;DOI 10.17487/RFC0150;May;https://www.rfc-editor.org/info/rfc150 | |
| RFC0151;;Shoshani, A.;Comments on a proffered official ICP: RFCs 123, 127;;;;;RFC 151;DOI 10.17487/RFC0151;May;https://www.rfc-editor.org/info/rfc151 | |
| RFC0152;;Wilber, M.;SRI Artificial Intelligence status report;;;;;RFC 152;DOI 10.17487/RFC0152;May;https://www.rfc-editor.org/info/rfc152 | |
| RFC0153;;Melvin, J. and R. Watson;SRI ARC-NIC status;;;;;RFC 153;DOI 10.17487/RFC0153;May;https://www.rfc-editor.org/info/rfc153 | |
| RFC0154;;Crocker, S.;Exposition Style;;;;;RFC 154;DOI 10.17487/RFC0154;May;https://www.rfc-editor.org/info/rfc154 | |
| RFC0155;RFC0168;North, J.;ARPA Network mailing lists;;;;;RFC 155;DOI 10.17487/RFC0155;May;https://www.rfc-editor.org/info/rfc155 | |
| RFC0156;;Bouknight, J.;Status of the Illinois site: Response to RFC 116;;;;;RFC 156;DOI 10.17487/RFC0156;April;https://www.rfc-editor.org/info/rfc156 | |
| RFC0157;;Cerf, V.;Invitation to the Second Symposium on Problems in the Optimization of Data Communications Systems;;;;;RFC 157;DOI 10.17487/RFC0157;May;https://www.rfc-editor.org/info/rfc157 | |
| RFC0158;RFC0495;O'Sullivan, T.;Telnet Protocol: A Proposed Document;;;;;RFC 158;DOI 10.17487/RFC0158;May;https://www.rfc-editor.org/info/rfc158 | |
| RFC0160;RFC0200, RFC0999;Network Information Center. Stanford Research Institute;RFC brief list;;;;;RFC 160;DOI 10.17487/RFC0160;May;https://www.rfc-editor.org/info/rfc160 | |
| RFC0161;;Shoshani, A.;Solution to the race condition in the ICP;;;;;RFC 161;DOI 10.17487/RFC0161;May;https://www.rfc-editor.org/info/rfc161 | |
| RFC0162;;Kampe, M.;NETBUGGER3;;;;;RFC 162;DOI 10.17487/RFC0162;May;https://www.rfc-editor.org/info/rfc162 | |
| RFC0163;;Cerf, V.;Data transfer protocols;;;;;RFC 163;DOI 10.17487/RFC0163;May;https://www.rfc-editor.org/info/rfc163 | |
| RFC0164;;Heafner, J.;Minutes of Network Working Group meeting, 5/16 through 5/19/71;;;;;RFC 164;DOI 10.17487/RFC0164;May;https://www.rfc-editor.org/info/rfc164 | |
| RFC0165;;Postel, J.;Proffered Official Initial Connection Protocol;;;;;RFC 165;DOI 10.17487/RFC0165;May;https://www.rfc-editor.org/info/rfc165 | |
| RFC0166;;Anderson, R., Cerf, V., Harslem, E., Heafner, J., Madden, J., Metcalfe, R., Shoshani, A., White, J., and D. Wood;Data Reconfiguration Service: An implementation specification;;;;;RFC 166;DOI 10.17487/RFC0166;May;https://www.rfc-editor.org/info/rfc166 | |
| RFC0167;;Bhushan, A., Metcalfe, R., and J. Winett;Socket conventions reconsidered;;;;;RFC 167;DOI 10.17487/RFC0167;May;https://www.rfc-editor.org/info/rfc167 | |
| RFC0168;RFC0211;North, J.;ARPA Network mailing lists;;;;;RFC 168;DOI 10.17487/RFC0168;May;https://www.rfc-editor.org/info/rfc168 | |
| RFC0169;;Crocker, S.;COMPUTER NETWORKS;;;;;RFC 169;DOI 10.17487/RFC0169;May;https://www.rfc-editor.org/info/rfc169 | |
| RFC0170;RFC0200;Network Information Center. Stanford Research Institute;RFC List by Number;;;;;RFC 170;DOI 10.17487/RFC0170;June;https://www.rfc-editor.org/info/rfc170 | |
| RFC0171;RFC0264;Bhushan, A., Braden, B., Crowther, W., Harslem, E., Heafner, J., McKenize, A., Melvin, J., Sundberg, B., Watson, D., and J. White;The Data Transfer Protocol;;;;;RFC 171;DOI 10.17487/RFC0171;June;https://www.rfc-editor.org/info/rfc171 | |
| RFC0172;RFC0265;Bhushan, A., Braden, B., Crowther, W., Harslem, E., Heafner, J., McKenzie, A., Melvin, J., Sundberg, B., Watson, D., and J. White;The File Transfer Protocol;;;;;RFC 172;DOI 10.17487/RFC0172;June;https://www.rfc-editor.org/info/rfc172 | |
| RFC0173;;Karp, P. and D. McKay;Network Data Management Committee Meeting Announcement;;;;;RFC 173;DOI 10.17487/RFC0173;June;https://www.rfc-editor.org/info/rfc173 | |
| RFC0174;;Postel, J. and V. Cerf;UCLA - Computer Science Graphics Overview;;;;;RFC 174;DOI 10.17487/RFC0174;June;https://www.rfc-editor.org/info/rfc174 | |
| RFC0175;;Harslem, E. and J. Heafner;Comments on "Socket Conventions Reconsidered";;;;;RFC 175;DOI 10.17487/RFC0175;June;https://www.rfc-editor.org/info/rfc175 | |
| RFC0176;;Bhushan, A., Kanodia, R., Metcalfe, R., and J. Postel;Comments on "Byte size for connections";;;;;RFC 176;DOI 10.17487/RFC0176;June;https://www.rfc-editor.org/info/rfc176 | |
| RFC0177;;McConnell, J.;Device independent graphical display description;;;;;RFC 177;DOI 10.17487/RFC0177;June;https://www.rfc-editor.org/info/rfc177 | |
| RFC0178;;Cotton, I.;Network graphic attention handling;;;;;RFC 178;DOI 10.17487/RFC0178;June;https://www.rfc-editor.org/info/rfc178 | |
| RFC0179;;McKenzie, A.;Link Number Assignments;;;;;RFC 179;DOI 10.17487/RFC0179;June;https://www.rfc-editor.org/info/rfc179 | |
| RFC0180;;McKenzie, A.;File system questionnaire;;;;;RFC 180;DOI 10.17487/RFC0180;June;https://www.rfc-editor.org/info/rfc180 | |
| RFC0181;;McConnell, J.;Modifications to RFC 177;;;;;RFC 181;DOI 10.17487/RFC0181;July;https://www.rfc-editor.org/info/rfc181 | |
| RFC0182;;North, J.;Compilation of list of relevant site reports;;;;;RFC 182;DOI 10.17487/RFC0182;June;https://www.rfc-editor.org/info/rfc182 | |
| RFC0183;;Winett, J.;EBCDIC Codes and Their Mapping to ASCII;;;;;RFC 183;DOI 10.17487/RFC0183;July;https://www.rfc-editor.org/info/rfc183 | |
| RFC0184;;Kelley, K.;Proposed graphic display modes;;;;;RFC 184;DOI 10.17487/RFC0184;July;https://www.rfc-editor.org/info/rfc184 | |
| RFC0185;;North, J.;NIC distribution of manuals and handbooks;;;;;RFC 185;DOI 10.17487/RFC0185;July;https://www.rfc-editor.org/info/rfc185 | |
| RFC0186;;Michener, J.;Network graphics loader;;;;;RFC 186;DOI 10.17487/RFC0186;July;https://www.rfc-editor.org/info/rfc186 | |
| RFC0187;;McKay, D. and D. Karp;Network/440 Protocol Concept;;;;;RFC 187;DOI 10.17487/RFC0187;July;https://www.rfc-editor.org/info/rfc187 | |
| RFC0188;;Karp, P. and D. McKay;Data management meeting announcement;;;;;RFC 188;DOI 10.17487/RFC0188;January;https://www.rfc-editor.org/info/rfc188 | |
| RFC0189;RFC0599;Braden, R.;Interim NETRJS specifications;;;;;RFC 189;DOI 10.17487/RFC0189;July;https://www.rfc-editor.org/info/rfc189 | |
| RFC0190;;Deutsch, L.;DEC PDP-10-IMLAC communications system;;;;;RFC 190;DOI 10.17487/RFC0190;July;https://www.rfc-editor.org/info/rfc190 | |
| RFC0191;;Irby, C.;Graphics implementation and conceptualization at Augmentation Research Center;;;;;RFC 191;DOI 10.17487/RFC0191;July;https://www.rfc-editor.org/info/rfc191 | |
| RFC0192;;Watson, R.;Some factors which a Network Graphics Protocol must consider;;;;;RFC 192;DOI 10.17487/RFC0192;July;https://www.rfc-editor.org/info/rfc192 | |
| RFC0193;RFC0198;Harslem, E. and J. Heafner;NETWORK CHECKOUT;;;;;RFC 193;DOI 10.17487/RFC0193;July;https://www.rfc-editor.org/info/rfc193 | |
| RFC0194;;Cerf, V., Harslem, E., Heafner, J., Metcalfe, B., and J. White;The Data Reconfiguration Service -- Compiler/Interpreter Implementation Notes;;;;;RFC 194;DOI 10.17487/RFC0194;July;https://www.rfc-editor.org/info/rfc194 | |
| RFC0195;;Mealy, G.;Data computers-data descriptions and access language;;;;;RFC 195;DOI 10.17487/RFC0195;July;https://www.rfc-editor.org/info/rfc195 | |
| RFC0196;RFC0221;Watson, R.;Mail Box Protocol;;;;;RFC 196;DOI 10.17487/RFC0196;July;https://www.rfc-editor.org/info/rfc196 | |
| RFC0197;;Shoshani, A. and E. Harslem;Initial Connection Protocol - Reviewed;;;;;RFC 197;DOI 10.17487/RFC0197;July;https://www.rfc-editor.org/info/rfc197 | |
| RFC0198;RFC0214;Heafner, J.;Site Certification - Lincoln Labs 360/67;;;;;RFC 198;DOI 10.17487/RFC0198;July;https://www.rfc-editor.org/info/rfc198 | |
| RFC0199;;Williams, T.;Suggestions for a Network Data-Tablet Graphics Protocol;;;;;RFC 199;DOI 10.17487/RFC0199;July;https://www.rfc-editor.org/info/rfc199 | |
| RFC0200;NIC 7724;North, J.;RFC list by number;;;;;RFC 200;DOI 10.17487/RFC0200;August;https://www.rfc-editor.org/info/rfc200 | |
| RFC0202;;Wolfe, S. and J. Postel;Possible Deadlock in ICP;;;;;RFC 202;DOI 10.17487/RFC0202;July;https://www.rfc-editor.org/info/rfc202 | |
| RFC0203;;Kalin, R.;Achieving reliable communication;;;;;RFC 203;DOI 10.17487/RFC0203;August;https://www.rfc-editor.org/info/rfc203 | |
| RFC0204;;Postel, J.;Sockets in use;;;;;RFC 204;DOI 10.17487/RFC0204;August;https://www.rfc-editor.org/info/rfc204 | |
| RFC0205;;Braden, R.;NETCRT - a character display protocol;;;;;RFC 205;DOI 10.17487/RFC0205;August;https://www.rfc-editor.org/info/rfc205 | |
| RFC0206;;White, J.;A User TELNET Description of an Initial Implementation;;;;;RFC 206;DOI 10.17487/RFC0206;August;https://www.rfc-editor.org/info/rfc206 | |
| RFC0207;RFC0212;Vezza, A.;September Network Working Group meeting;;;;;RFC 207;DOI 10.17487/RFC0207;August;https://www.rfc-editor.org/info/rfc207 | |
| RFC0208;;McKenzie, A.;Address tables;;;;;RFC 208;DOI 10.17487/RFC0208;August;https://www.rfc-editor.org/info/rfc208 | |
| RFC0209;;Cosell, B.;Host/IMP interface documentation;;;;;RFC 209;DOI 10.17487/RFC0209;August;https://www.rfc-editor.org/info/rfc209 | |
| RFC0210;;Conrad, W.;Improvement of Flow Control;;;;;RFC 210;DOI 10.17487/RFC0210;August;https://www.rfc-editor.org/info/rfc210 | |
| RFC0211;RFC0300;North, J.;ARPA Network Mailing Lists;;;;;RFC 211;DOI 10.17487/RFC0211;August;https://www.rfc-editor.org/info/rfc211 | |
| RFC0212;;Information Sciences Institute University of Southern California;NWG meeting on network usage;;;;;RFC 212;DOI 10.17487/RFC0212;August;https://www.rfc-editor.org/info/rfc212 | |
| RFC0213;;Cosell, B.;IMP System change notification;;;;;RFC 213;DOI 10.17487/RFC0213;August;https://www.rfc-editor.org/info/rfc213 | |
| RFC0214;;Harslem, E.;Network checkpoint;;;;;RFC 214;DOI 10.17487/RFC0214;August;https://www.rfc-editor.org/info/rfc214 | |
| RFC0215;;McKenzie, A.;NCP, ICP, and Telnet: The Terminal IMP implementation;;;;;RFC 215;DOI 10.17487/RFC0215;August;https://www.rfc-editor.org/info/rfc215 | |
| RFC0216;;White, J.;Telnet Access to UCSB's On-Line System;;;;;RFC 216;DOI 10.17487/RFC0216;September;https://www.rfc-editor.org/info/rfc216 | |
| RFC0217;;White, J.;Specifications changes for OLS, RJE/RJOR, and SMFS;;;;;RFC 217;DOI 10.17487/RFC0217;September;https://www.rfc-editor.org/info/rfc217 | |
| RFC0218;;Cosell, B.;Changing the IMP status reporting facility;;;;;RFC 218;DOI 10.17487/RFC0218;September;https://www.rfc-editor.org/info/rfc218 | |
| RFC0219;;Winter, R.;User's View of the Datacomputer;;;;;RFC 219;DOI 10.17487/RFC0219;September;https://www.rfc-editor.org/info/rfc219 | |
| RFC0221;RFC0278;Watson, R.;Mail Box Protocol: Version 2;;;;;RFC 221;DOI 10.17487/RFC0221;August;https://www.rfc-editor.org/info/rfc221 | |
| RFC0222;;Metcalfe, R.;Subject: System programmer's workshop;;;;;RFC 222;DOI 10.17487/RFC0222;September;https://www.rfc-editor.org/info/rfc222 | |
| RFC0223;;Melvin, J. and R. Watson;Network Information Center schedule for network users;;;;;RFC 223;DOI 10.17487/RFC0223;September;https://www.rfc-editor.org/info/rfc223 | |
| RFC0224;;McKenzie, A.;Comments on Mailbox Protocol;;;;;RFC 224;DOI 10.17487/RFC0224;September;https://www.rfc-editor.org/info/rfc224 | |
| RFC0225;;Harslem, E. and R. Stoughton;Rand/UCSB network graphics experiment;;;;;RFC 225;DOI 10.17487/RFC0225;September;https://www.rfc-editor.org/info/rfc225 | |
| RFC0226;RFC0247;Karp, P.;Standardization of host mnemonics;;;;;RFC 226;DOI 10.17487/RFC0226;September;https://www.rfc-editor.org/info/rfc226 | |
| RFC0227;;Heafner, J. and E. Harslem;Data transfer rates (Rand/UCLA);;;;;RFC 227;DOI 10.17487/RFC0227;September;https://www.rfc-editor.org/info/rfc227 | |
| RFC0228;;Walden, D.;Clarification;;;;;RFC 228;DOI 10.17487/RFC0228;September;https://www.rfc-editor.org/info/rfc228 | |
| RFC0229;RFC0236;Postel, J.;Standard host names;;;;;RFC 229;DOI 10.17487/RFC0229;September;https://www.rfc-editor.org/info/rfc229 | |
| RFC0230;;Pyke, T.;Toward reliable operation of minicomputer-based terminals on a TIP;;;;;RFC 230;DOI 10.17487/RFC0230;September;https://www.rfc-editor.org/info/rfc230 | |
| RFC0231;;Heafner, J. and E. Harslem;Service center standards for remote usage: A user's view;;;;;RFC 231;DOI 10.17487/RFC0231;September;https://www.rfc-editor.org/info/rfc231 | |
| RFC0232;;Vezza, A.;Postponement of network graphics meeting;;;;;RFC 232;DOI 10.17487/RFC0232;September;https://www.rfc-editor.org/info/rfc232 | |
| RFC0233;;Bhushan, A. and R. Metcalfe;Standardization of host call letters;;;;;RFC 233;DOI 10.17487/RFC0233;September;https://www.rfc-editor.org/info/rfc233 | |
| RFC0234;;Vezza, A.;Network Working Group meeting schedule;;;;;RFC 234;DOI 10.17487/RFC0234;October;https://www.rfc-editor.org/info/rfc234 | |
| RFC0235;RFC0240;Westheimer, E.;Site status;;;;;RFC 235;DOI 10.17487/RFC0235;September;https://www.rfc-editor.org/info/rfc235 | |
| RFC0236;;Postel, J.;Standard host names;;;;;RFC 236;DOI 10.17487/RFC0236;September;https://www.rfc-editor.org/info/rfc236 | |
| RFC0237;RFC0273;Watson, R.;NIC view of standard host names;;;;;RFC 237;DOI 10.17487/RFC0237;October;https://www.rfc-editor.org/info/rfc237 | |
| RFC0238;;Braden, R.;Comments on DTP and FTP proposals;;;;;RFC 238;DOI 10.17487/RFC0238;September;https://www.rfc-editor.org/info/rfc238 | |
| RFC0239;;Braden, R.;Host mnemonics proposed in RFC 226 (NIC 7625);;;;;RFC 239;DOI 10.17487/RFC0239;September;https://www.rfc-editor.org/info/rfc239 | |
| RFC0240;RFC0252;McKenzie, A.;Site Status;;;;;RFC 240;DOI 10.17487/RFC0240;September;https://www.rfc-editor.org/info/rfc240 | |
| RFC0241;;McKenzie, A.;Connecting computers to MLC ports;;;;;RFC 241;DOI 10.17487/RFC0241;September;https://www.rfc-editor.org/info/rfc241 | |
| RFC0242;;Haibt, L. and A. Mullery;Data Descriptive Language for Shared Data;;;;;RFC 242;DOI 10.17487/RFC0242;July;https://www.rfc-editor.org/info/rfc242 | |
| RFC0243;RFC0290;Mullery, A.;Network and data sharing bibliography;;;;;RFC 243;DOI 10.17487/RFC0243;October;https://www.rfc-editor.org/info/rfc243 | |
| RFC0245;;Falls, C.;Reservations for Network Group meeting;;;;;RFC 245;DOI 10.17487/RFC0245;October;https://www.rfc-editor.org/info/rfc245 | |
| RFC0246;;Vezza, A.;Network Graphics meeting;;;;;RFC 246;DOI 10.17487/RFC0246;October;https://www.rfc-editor.org/info/rfc246 | |
| RFC0247;;Karp, P.;Proffered set of standard host names;;;;;RFC 247;DOI 10.17487/RFC0247;October;https://www.rfc-editor.org/info/rfc247 | |
| RFC0249;;Borelli, R.;Coordination of equipment and supplies purchase;;;;;RFC 249;DOI 10.17487/RFC0249;October;https://www.rfc-editor.org/info/rfc249 | |
| RFC0250;;Brodie, H.;Some thoughts on file transfer;;;;;RFC 250;DOI 10.17487/RFC0250;October;https://www.rfc-editor.org/info/rfc250 | |
| RFC0251;;Stern, D.;Weather data;;;;;RFC 251;DOI 10.17487/RFC0251;October;https://www.rfc-editor.org/info/rfc251 | |
| RFC0252;RFC0255;Westheimer, E.;Network host status;;;;;RFC 252;DOI 10.17487/RFC0252;October;https://www.rfc-editor.org/info/rfc252 | |
| RFC0253;;Moorer, J.;Second Network Graphics meeting details;;;;;RFC 253;DOI 10.17487/RFC0253;October;https://www.rfc-editor.org/info/rfc253 | |
| RFC0254;;Bhushan, A.;Scenarios for using ARPANET computers;;;;;RFC 254;DOI 10.17487/RFC0254;October;https://www.rfc-editor.org/info/rfc254 | |
| RFC0255;RFC0266;Westheimer, E.;Status of network hosts;;;;;RFC 255;DOI 10.17487/RFC0255;October;https://www.rfc-editor.org/info/rfc255 | |
| RFC0256;;Cosell, B.;IMPSYS change notification;;;;;RFC 256;DOI 10.17487/RFC0256;November;https://www.rfc-editor.org/info/rfc256 | |
| RFC0263;;McKenzie, A.;"Very Distant" Host interface;;;;;RFC 263;DOI 10.17487/RFC0263;December;https://www.rfc-editor.org/info/rfc263 | |
| RFC0264;RFC0354;Bhushan, A., Braden, B., Crowther, W., Harslem, E., Heafner, J., McKenize, A., Sundberg, B., Watson, D., and J. White;The Data Transfer Protocol;;;;;RFC 264;DOI 10.17487/RFC0264;January;https://www.rfc-editor.org/info/rfc264 | |
| RFC0265;RFC0354;Bhushan, A., Braden, B., Crowther, W., Harslem, E., Heafner, J., McKenzie, A., Melvin, J., Sundberg, B., Watson, D., and J. White;The File Transfer Protocol;;;;;RFC 265;DOI 10.17487/RFC0265;November;https://www.rfc-editor.org/info/rfc265 | |
| RFC0266;RFC0267;Westheimer, E.;Network host status;;;;;RFC 266;DOI 10.17487/RFC0266;November;https://www.rfc-editor.org/info/rfc266 | |
| RFC0267;RFC0287;Westheimer, E.;Network Host Status;;;;;RFC 267;DOI 10.17487/RFC0267;November;https://www.rfc-editor.org/info/rfc267 | |
| RFC0268;;Postel, J.;Graphics facilities information;;;;;RFC 268;DOI 10.17487/RFC0268;November;https://www.rfc-editor.org/info/rfc268 | |
| RFC0269;;Brodie, H.;Some Experience with File Transfer;;;;;RFC 269;DOI 10.17487/RFC0269;December;https://www.rfc-editor.org/info/rfc269 | |
| RFC0270;;McKenzie, A.;Correction to BBN Report No. 1822 (NIC NO 7958);;;;;RFC 270;DOI 10.17487/RFC0270;January;https://www.rfc-editor.org/info/rfc270 | |
| RFC0271;;Cosell, B.;IMP System change notifications;;;;;RFC 271;DOI 10.17487/RFC0271;January;https://www.rfc-editor.org/info/rfc271 | |
| RFC0273;;Watson, R.;More on standard host names;;;;;RFC 273;DOI 10.17487/RFC0273;October;https://www.rfc-editor.org/info/rfc273 | |
| RFC0274;;Forman, E.;Establishing a local guide for network usage;;;;;RFC 274;DOI 10.17487/RFC0274;November;https://www.rfc-editor.org/info/rfc274 | |
| RFC0276;;Watson, R.;NIC course;;;;;RFC 276;DOI 10.17487/RFC0276;November;https://www.rfc-editor.org/info/rfc276 | |
| RFC0278;;Bhushan, A., Braden, R., Harslem, E., Heafner, J., McKenzie, A., Melvin, J., Sundberg, R., Watson, R., and J. White;Revision of the Mail Box Protocol;;;;;RFC 278;DOI 10.17487/RFC0278;November;https://www.rfc-editor.org/info/rfc278 | |
| RFC0280;;Watson, R.;A Draft of Host Names;;;;;RFC 280;DOI 10.17487/RFC0280;November;https://www.rfc-editor.org/info/rfc280 | |
| RFC0281;;McKenzie, A.;Suggested addition to File Transfer Protocol;;;;;RFC 281;DOI 10.17487/RFC0281;December;https://www.rfc-editor.org/info/rfc281 | |
| RFC0282;;Padlipsky, M.;Graphics meeting report;;;;;RFC 282;DOI 10.17487/RFC0282;December;https://www.rfc-editor.org/info/rfc282 | |
| RFC0283;;Braden, R.;NETRJT: Remote Job Service Protocol for TIPS;;;;;RFC 283;DOI 10.17487/RFC0283;December;https://www.rfc-editor.org/info/rfc283 | |
| RFC0285;;Huff, D.;Network graphics;;;;;RFC 285;DOI 10.17487/RFC0285;December;https://www.rfc-editor.org/info/rfc285 | |
| RFC0286;;Forman, E.;Network Library Information System;;;;;RFC 286;DOI 10.17487/RFC0286;December;https://www.rfc-editor.org/info/rfc286 | |
| RFC0287;RFC0288;Westheimer, E.;Status of Network Hosts;;;;;RFC 287;DOI 10.17487/RFC0287;December;https://www.rfc-editor.org/info/rfc287 | |
| RFC0288;RFC0293;Westheimer, E.;Network host status;;;;;RFC 288;DOI 10.17487/RFC0288;January;https://www.rfc-editor.org/info/rfc288 | |
| RFC0289;RFC0384;Watson, R.;What we hope is an official list of host names;;;;;RFC 289;DOI 10.17487/RFC0289;December;https://www.rfc-editor.org/info/rfc289 | |
| RFC0290;;Mullery, A.;Computer networks and data sharing: A bibliography;;;;;RFC 290;DOI 10.17487/RFC0290;January;https://www.rfc-editor.org/info/rfc290 | |
| RFC0291;;McKay, D.;Data Management Meeting Announcement;;;;;RFC 291;DOI 10.17487/RFC0291;January;https://www.rfc-editor.org/info/rfc291 | |
| RFC0292;RFC0493;Michener, J., Cotton, I., Kelley, K., Liddle, D., and E. Meyer;Graphics Protocol: Level 0 only;;;;;RFC 292;DOI 10.17487/RFC0292;January;https://www.rfc-editor.org/info/rfc292 | |
| RFC0293;RFC0298;Westheimer, E.;Network Host Status;;;;;RFC 293;DOI 10.17487/RFC0293;January;https://www.rfc-editor.org/info/rfc293 | |
| RFC0294;;Bhushan, A.;The Use of "Set Data Type" Transaction in File Transfer Protocol;;;;;RFC 294;DOI 10.17487/RFC0294;January;https://www.rfc-editor.org/info/rfc294 | |
| RFC0295;;Postel, J.;Report of the Protocol Workshop, 12 October 1971;;;;;RFC 295;DOI 10.17487/RFC0295;January;https://www.rfc-editor.org/info/rfc295 | |
| RFC0296;;Liddle, D.;DS-1 Display System;;;;;RFC 296;DOI 10.17487/RFC0296;January;https://www.rfc-editor.org/info/rfc296 | |
| RFC0297;;Walden, D.;TIP Message Buffers;;;;;RFC 297;DOI 10.17487/RFC0297;January;https://www.rfc-editor.org/info/rfc297 | |
| RFC0298;RFC0306;Westheimer, E.;Network host status;;;;;RFC 298;DOI 10.17487/RFC0298;February;https://www.rfc-editor.org/info/rfc298 | |
| RFC0299;;Hopkin, D.;Information Management System;;;;;RFC 299;DOI 10.17487/RFC0299;February;https://www.rfc-editor.org/info/rfc299 | |
| RFC0300;RFC0303;North, J.;ARPA Network mailing lists;;;;;RFC 300;DOI 10.17487/RFC0300;January;https://www.rfc-editor.org/info/rfc300 | |
| RFC0301;;Alter, R.;BBN IMP (#5) and NCC Schedule March 4, 1971;;;;;RFC 301;DOI 10.17487/RFC0301;February;https://www.rfc-editor.org/info/rfc301 | |
| RFC0302;;Bryan, R.;Exercising The ARPANET;;;;;RFC 302;DOI 10.17487/RFC0302;February;https://www.rfc-editor.org/info/rfc302 | |
| RFC0303;RFC0329;Network Information Center. Stanford Research Institute;ARPA Network mailing lists;;;;;RFC 303;DOI 10.17487/RFC0303;March;https://www.rfc-editor.org/info/rfc303 | |
| RFC0304;;McKay, D.;Data Management System Proposal for the ARPA Network;;;;;RFC 304;DOI 10.17487/RFC0304;February;https://www.rfc-editor.org/info/rfc304 | |
| RFC0305;;Alter, R.;Unknown Host Numbers;;;;;RFC 305;DOI 10.17487/RFC0305;February;https://www.rfc-editor.org/info/rfc305 | |
| RFC0306;RFC0315;Westheimer, E.;Network host status;;;;;RFC 306;DOI 10.17487/RFC0306;February;https://www.rfc-editor.org/info/rfc306 | |
| RFC0307;;Harslem, E.;Using network Remote Job Entry;;;;;RFC 307;DOI 10.17487/RFC0307;February;https://www.rfc-editor.org/info/rfc307 | |
| RFC0308;;Seriff, M.;ARPANET host availability data;;;;;RFC 308;DOI 10.17487/RFC0308;March;https://www.rfc-editor.org/info/rfc308 | |
| RFC0309;;Bhushan, A.;Data and File Transfer Workshop Announcement;;;;;RFC 309;DOI 10.17487/RFC0309;March;https://www.rfc-editor.org/info/rfc309 | |
| RFC0310;;Bhushan, A.;Another Look at Data and File Transfer Protocols;;;;;RFC 310;DOI 10.17487/RFC0310;April;https://www.rfc-editor.org/info/rfc310 | |
| RFC0311;;Bryan, R.;New Console Attachments to the USCB Host;;;;;RFC 311;DOI 10.17487/RFC0311;February;https://www.rfc-editor.org/info/rfc311 | |
| RFC0312;;McKenzie, A.;Proposed Change in IMP-to-Host Protocol;;;;;RFC 312;DOI 10.17487/RFC0312;March;https://www.rfc-editor.org/info/rfc312 | |
| RFC0313;;O'Sullivan, T.;Computer based instruction;;;;;RFC 313;DOI 10.17487/RFC0313;March;https://www.rfc-editor.org/info/rfc313 | |
| RFC0314;;Cotton, I.;Network Graphics Working Group Meeting;;;;;RFC 314;DOI 10.17487/RFC0314;March;https://www.rfc-editor.org/info/rfc314 | |
| RFC0315;RFC0319;Westheimer, E.;Network Host Status;;;;;RFC 315;DOI 10.17487/RFC0315;March;https://www.rfc-editor.org/info/rfc315 | |
| RFC0316;;McKay, D. and A. Mullery;ARPA Network Data Management Working Group;;;;;RFC 316;DOI 10.17487/RFC0316;February;https://www.rfc-editor.org/info/rfc316 | |
| RFC0317;RFC0604;Postel, J.;Official Host-Host Protocol Modification: Assigned Link Numbers;;;;;RFC 317;DOI 10.17487/RFC0317;March;https://www.rfc-editor.org/info/rfc317 | |
| RFC0318;;Postel, J.;Telnet Protocols;;;;;RFC 318;DOI 10.17487/RFC0318;April;https://www.rfc-editor.org/info/rfc318 | |
| RFC0319;;Westheimer, E.;Network Host Status;;;;;RFC 319;DOI 10.17487/RFC0319;March;https://www.rfc-editor.org/info/rfc319 | |
| RFC0320;;Reddy, R.;Workshop on Hard Copy Line Graphics;;;;;RFC 320;DOI 10.17487/RFC0320;March;https://www.rfc-editor.org/info/rfc320 | |
| RFC0321;;Karp, P.;CBI Networking Activity at MITRE;;;;;RFC 321;DOI 10.17487/RFC0321;March;https://www.rfc-editor.org/info/rfc321 | |
| RFC0322;;Cerf, V. and J. Postel;Well known socket numbers;;;;;RFC 322;DOI 10.17487/RFC0322;March;https://www.rfc-editor.org/info/rfc322 | |
| RFC0323;;Cerf, V.;Formation of Network Measurement Group (NMG);;;;;RFC 323;DOI 10.17487/RFC0323;March;https://www.rfc-editor.org/info/rfc323 | |
| RFC0324;;Postel, J.;RJE Protocol meeting;;;;;RFC 324;DOI 10.17487/RFC0324;April;https://www.rfc-editor.org/info/rfc324 | |
| RFC0325;;Hicks, G.;Network Remote Job Entry program - NETRJS;;;;;RFC 325;DOI 10.17487/RFC0325;April;https://www.rfc-editor.org/info/rfc325 | |
| RFC0326;RFC0330;Westheimer, E.;Network Host Status;;;;;RFC 326;DOI 10.17487/RFC0326;April;https://www.rfc-editor.org/info/rfc326 | |
| RFC0327;;Bhushan, A.;Data and File Transfer workshop notes;;;;;RFC 327;DOI 10.17487/RFC0327;April;https://www.rfc-editor.org/info/rfc327 | |
| RFC0328;;Postel, J.;Suggested Telnet Protocol Changes;;;;;RFC 328;DOI 10.17487/RFC0328;April;https://www.rfc-editor.org/info/rfc328 | |
| RFC0329;RFC0363;Network Information Center. Stanford Research Institute;ARPA Network Mailing Lists;;;;;RFC 329;DOI 10.17487/RFC0329;May;https://www.rfc-editor.org/info/rfc329 | |
| RFC0330;;Westheimer, E.;Network Host Status;;;;;RFC 330;DOI 10.17487/RFC0330;April;https://www.rfc-editor.org/info/rfc330 | |
| RFC0331;RFC0343;McQuillan, J.;IMP System Change Notification;;;;;RFC 331;DOI 10.17487/RFC0331;April;https://www.rfc-editor.org/info/rfc331 | |
| RFC0332;RFC0342;Westheimer, E.;Network Host Status;;;;;RFC 332;DOI 10.17487/RFC0332;April;https://www.rfc-editor.org/info/rfc332 | |
| RFC0333;;Bressler, R., Murphy, D., and D. Walden;Proposed experiment with a Message Switching Protocol;;;;;RFC 333;DOI 10.17487/RFC0333;May;https://www.rfc-editor.org/info/rfc333 | |
| RFC0334;;McKenzie, A.;Network Use on May 8;;;;;RFC 334;DOI 10.17487/RFC0334;May;https://www.rfc-editor.org/info/rfc334 | |
| RFC0335;;Bryan, R.;New Interface - IMP/360;;;;;RFC 335;DOI 10.17487/RFC0335;May;https://www.rfc-editor.org/info/rfc335 | |
| RFC0336;;Cotton, I.;Level 0 Graphic Input Protocol;;;;;RFC 336;DOI 10.17487/RFC0336;May;https://www.rfc-editor.org/info/rfc336 | |
| RFC0338;;Braden, R.;EBCDIC/ASCII Mapping for Network RJE;;;;;RFC 338;DOI 10.17487/RFC0338;May;https://www.rfc-editor.org/info/rfc338 | |
| RFC0339;;Thomas, R.;MLTNET: A "Multi Telnet" Subsystem for Tenex;;;;;RFC 339;DOI 10.17487/RFC0339;May;https://www.rfc-editor.org/info/rfc339 | |
| RFC0340;;O'Sullivan, T.;Proposed Telnet Changes;;;;;RFC 340;DOI 10.17487/RFC0340;May;https://www.rfc-editor.org/info/rfc340 | |
| RFC0342;RFC0344;Westheimer, E.;Network Host Status;;;;;RFC 342;DOI 10.17487/RFC0342;May;https://www.rfc-editor.org/info/rfc342 | |
| RFC0343;RFC0359;McKenzie, A.;IMP System change notification;;;;;RFC 343;DOI 10.17487/RFC0343;May;https://www.rfc-editor.org/info/rfc343 | |
| RFC0344;RFC0353;Westheimer, E.;Network Host Status;;;;;RFC 344;DOI 10.17487/RFC0344;May;https://www.rfc-editor.org/info/rfc344 | |
| RFC0345;;Kelley, K.;Interest in Mixed Integer Programming (MPSX on NIC 360/91 at CCN);;;;;RFC 345;DOI 10.17487/RFC0345;May;https://www.rfc-editor.org/info/rfc345 | |
| RFC0346;;Postel, J.;Satellite Considerations;;;;;RFC 346;DOI 10.17487/RFC0346;May;https://www.rfc-editor.org/info/rfc346 | |
| RFC0347;;Postel, J.;Echo process;;;;;RFC 347;DOI 10.17487/RFC0347;May;https://www.rfc-editor.org/info/rfc347 | |
| RFC0348;;Postel, J.;Discard Process;;;;;RFC 348;DOI 10.17487/RFC0348;May;https://www.rfc-editor.org/info/rfc348 | |
| RFC0349;RFC0433;Postel, J.;Proposed Standard Socket Numbers;;;;;RFC 349;DOI 10.17487/RFC0349;May;https://www.rfc-editor.org/info/rfc349 | |
| RFC0350;;Stoughton, R.;User Accounts for UCSB On-Line System;;;;;RFC 350;DOI 10.17487/RFC0350;May;https://www.rfc-editor.org/info/rfc350 | |
| RFC0351;;Crocker, D.;Graphics information form for the ARPANET graphics resources notebook;;;;;RFC 351;DOI 10.17487/RFC0351;June;https://www.rfc-editor.org/info/rfc351 | |
| RFC0352;;Crocker, D.;TIP Site Information Form;;;;;RFC 352;DOI 10.17487/RFC0352;June;https://www.rfc-editor.org/info/rfc352 | |
| RFC0353;RFC0362;Westheimer, E.;Network host status;;;;;RFC 353;DOI 10.17487/RFC0353;June;https://www.rfc-editor.org/info/rfc353 | |
| RFC0354;RFC0542;Bhushan, A.;File Transfer Protocol;;;;;RFC 354;DOI 10.17487/RFC0354;July;https://www.rfc-editor.org/info/rfc354 | |
| RFC0355;;Davidson, J.;Response to NWG/RFC 346;;;;;RFC 355;DOI 10.17487/RFC0355;June;https://www.rfc-editor.org/info/rfc355 | |
| RFC0356;;Alter, R.;ARPA Network Control Center;;;;;RFC 356;DOI 10.17487/RFC0356;June;https://www.rfc-editor.org/info/rfc356 | |
| RFC0357;;Davidson, J.;Echoing strategy for satellite links;;;;;RFC 357;DOI 10.17487/RFC0357;June;https://www.rfc-editor.org/info/rfc357 | |
| RFC0359;;Walden, D.;Status of the Release of the New IMP System (2600);;;;;RFC 359;DOI 10.17487/RFC0359;June;https://www.rfc-editor.org/info/rfc359 | |
| RFC0360;RFC0407;Holland, C.;Proposed Remote Job Entry Protocol;;;;;RFC 360;DOI 10.17487/RFC0360;June;https://www.rfc-editor.org/info/rfc360 | |
| RFC0361;;Bressler, R.;Deamon Processes on Host 106;;;;;RFC 361;DOI 10.17487/RFC0361;July;https://www.rfc-editor.org/info/rfc361 | |
| RFC0362;RFC0366;Westheimer, E.;Network Host Status;;;;;RFC 362;DOI 10.17487/RFC0362;June;https://www.rfc-editor.org/info/rfc362 | |
| RFC0363;RFC0402;Network Information Center. Stanford Research Institute;ARPA Network mailing lists;;;;;RFC 363;DOI 10.17487/RFC0363;August;https://www.rfc-editor.org/info/rfc363 | |
| RFC0364;;Abrams, M.;Serving remote users on the ARPANET;;;;;RFC 364;DOI 10.17487/RFC0364;July;https://www.rfc-editor.org/info/rfc364 | |
| RFC0365;;Walden, D.;Letter to All TIP Users;;;;;RFC 365;DOI 10.17487/RFC0365;July;https://www.rfc-editor.org/info/rfc365 | |
| RFC0366;RFC0367;Westheimer, E.;Network Host Status;;;;;RFC 366;DOI 10.17487/RFC0366;July;https://www.rfc-editor.org/info/rfc366 | |
| RFC0367;RFC0370;Westheimer, E.;Network host status;;;;;RFC 367;DOI 10.17487/RFC0367;July;https://www.rfc-editor.org/info/rfc367 | |
| RFC0368;;Braden, R.;Comments on "Proposed Remote Job Entry Protocol";;;;;RFC 368;DOI 10.17487/RFC0368;July;https://www.rfc-editor.org/info/rfc368 | |
| RFC0369;;Pickens, J.;Evaluation of ARPANET services January-March, 1972;;;;;RFC 369;DOI 10.17487/RFC0369;July;https://www.rfc-editor.org/info/rfc369 | |
| RFC0370;;Westheimer, E.;Network Host Status;;;;;RFC 370;DOI 10.17487/RFC0370;July;https://www.rfc-editor.org/info/rfc370 | |
| RFC0371;;Kahn, R.;Demonstration at International Computer Communications Conference;;;;;RFC 371;DOI 10.17487/RFC0371;July;https://www.rfc-editor.org/info/rfc371 | |
| RFC0372;;Watson, R.;Notes on a Conversation with Bob Kahn on the ICCC;;;;;RFC 372;DOI 10.17487/RFC0372;July;https://www.rfc-editor.org/info/rfc372 | |
| RFC0373;;McCarthy, J.;Arbitrary Character Sets;;;;;RFC 373;DOI 10.17487/RFC0373;July;https://www.rfc-editor.org/info/rfc373 | |
| RFC0374;;McKenzie, A.;IMP System Announcement;;;;;RFC 374;DOI 10.17487/RFC0374;July;https://www.rfc-editor.org/info/rfc374 | |
| RFC0376;;Westheimer, E.;Network Host Status;;;;;RFC 376;DOI 10.17487/RFC0376;August;https://www.rfc-editor.org/info/rfc376 | |
| RFC0377;;Braden, R.;Using TSO via ARPA Network Virtual Terminal;;;;;RFC 377;DOI 10.17487/RFC0377;August;https://www.rfc-editor.org/info/rfc377 | |
| RFC0378;RFC0391;McKenzie, A.;Traffic statistics (July 1972);;;;;RFC 378;DOI 10.17487/RFC0378;August;https://www.rfc-editor.org/info/rfc378 | |
| RFC0379;;Braden, R.;Using TSO at CCN;;;;;RFC 379;DOI 10.17487/RFC0379;August;https://www.rfc-editor.org/info/rfc379 | |
| RFC0381;;McQuillan, J.;Three aids to improved network operation;;;;;RFC 381;DOI 10.17487/RFC0381;July;https://www.rfc-editor.org/info/rfc381 | |
| RFC0382;;McDaniel, L.;Mathematical Software on the ARPA Network;;;;;RFC 382;DOI 10.17487/RFC0382;August;https://www.rfc-editor.org/info/rfc382 | |
| RFC0384;;North, J.;Official site idents for organizations in the ARPA Network;;;;;RFC 384;DOI 10.17487/RFC0384;August;https://www.rfc-editor.org/info/rfc384 | |
| RFC0385;;Bhushan, A.;Comments on the File Transfer Protocol;;;;;RFC 385;DOI 10.17487/RFC0385;August;https://www.rfc-editor.org/info/rfc385 | |
| RFC0386;;Cosell, B. and D. Walden;Letter to TIP users-2;;;;;RFC 386;DOI 10.17487/RFC0386;August;https://www.rfc-editor.org/info/rfc386 | |
| RFC0387;;Kelley, K. and J. Meir;Some experiences in implementing Network Graphics Protocol Level 0;;;;;RFC 387;DOI 10.17487/RFC0387;August;https://www.rfc-editor.org/info/rfc387 | |
| RFC0388;;Cerf, V.;NCP statistics;;;;;RFC 388;DOI 10.17487/RFC0388;August;https://www.rfc-editor.org/info/rfc388 | |
| RFC0389;RFC0423;Noble, B.;UCLA Campus Computing Network Liaison Staff for ARPA Network;;;;;RFC 389;DOI 10.17487/RFC0389;August;https://www.rfc-editor.org/info/rfc389 | |
| RFC0390;;Braden, R.;TSO Scenario;;;;;RFC 390;DOI 10.17487/RFC0390;September;https://www.rfc-editor.org/info/rfc390 | |
| RFC0391;;McKenzie, A.;Traffic statistics (August 1972);;;;;RFC 391;DOI 10.17487/RFC0391;September;https://www.rfc-editor.org/info/rfc391 | |
| RFC0392;;Hicks, G. and B. Wessler;Measurement of host costs for transmitting network data;;;;;RFC 392;DOI 10.17487/RFC0392;September;https://www.rfc-editor.org/info/rfc392 | |
| RFC0393;;Winett, J.;Comments on Telnet Protocol Changes;;;;;RFC 393;DOI 10.17487/RFC0393;October;https://www.rfc-editor.org/info/rfc393 | |
| RFC0394;;McQuillan, J.;Two Proposed Changes to the IMP-Host Protocol;;;;;RFC 394;DOI 10.17487/RFC0394;September;https://www.rfc-editor.org/info/rfc394 | |
| RFC0395;;McQuillan, J.;Switch Settings on IMPs and TIPs;;;;;RFC 395;DOI 10.17487/RFC0395;October;https://www.rfc-editor.org/info/rfc395 | |
| RFC0396;;Bunch, S.;Network Graphics Working Group Meeting - Second Iteration;;;;;RFC 396;DOI 10.17487/RFC0396;November;https://www.rfc-editor.org/info/rfc396 | |
| RFC0398;;Pickens, J. and E. Faeh;UCSB Online Graphics;;;;;RFC 398;DOI 10.17487/RFC0398;September;https://www.rfc-editor.org/info/rfc398 | |
| RFC0399;RFC0431;Krilanovich, M.;SMFS Login and Logout;;;;;RFC 399;DOI 10.17487/RFC0399;September;https://www.rfc-editor.org/info/rfc399 | |
| RFC0400;;McKenzie, A.;Traffic Statistics (September 1972);;;;;RFC 400;DOI 10.17487/RFC0400;October;https://www.rfc-editor.org/info/rfc400 | |
| RFC0401;;Hansen, J.;Conversion of NGP-0 Coordinates to Device Specific Coordinates;;;;;RFC 401;DOI 10.17487/RFC0401;October;https://www.rfc-editor.org/info/rfc401 | |
| RFC0402;;North, J.;ARPA Network Mailing Lists;;;;;RFC 402;DOI 10.17487/RFC0402;October;https://www.rfc-editor.org/info/rfc402 | |
| RFC0403;;Hicks, G.;Desirability of a Network 1108 Service;;;;;RFC 403;DOI 10.17487/RFC0403;January;https://www.rfc-editor.org/info/rfc403 | |
| RFC0404;;McKenzie, A.;Host Address Changes Involving Rand and ISI;;;;;RFC 404;DOI 10.17487/RFC0404;October;https://www.rfc-editor.org/info/rfc404 | |
| RFC0405;;McKenzie, A.;Correction to RFC 404;;;;;RFC 405;DOI 10.17487/RFC0405;October;https://www.rfc-editor.org/info/rfc405 | |
| RFC0406;;McQuillan, J.;Scheduled IMP Software Releases;;;;;RFC 406;DOI 10.17487/RFC0406;October;https://www.rfc-editor.org/info/rfc406 | |
| RFC0407;;Bressler, R., Guida, R., and A. McKenzie;Remote Job Entry Protocol;;;;;RFC 407;DOI 10.17487/RFC0407;October;https://www.rfc-editor.org/info/rfc407 | |
| RFC0408;;Owen, A. and J. Postel;NETBANK;;;;;RFC 408;DOI 10.17487/RFC0408;October;https://www.rfc-editor.org/info/rfc408 | |
| RFC0409;;White, J.;Tenex interface to UCSB's Simple-Minded File System;;;;;RFC 409;DOI 10.17487/RFC0409;December;https://www.rfc-editor.org/info/rfc409 | |
| RFC0410;;McQuillan, J.;Removal of the 30-Second Delay When Hosts Come Up;;;;;RFC 410;DOI 10.17487/RFC0410;November;https://www.rfc-editor.org/info/rfc410 | |
| RFC0411;;Padlipsky, M.;New MULTICS Network Software Features;;;;;RFC 411;DOI 10.17487/RFC0411;November;https://www.rfc-editor.org/info/rfc411 | |
| RFC0412;;Hicks, G.;User FTP Documentation;;;;;RFC 412;DOI 10.17487/RFC0412;November;https://www.rfc-editor.org/info/rfc412 | |
| RFC0413;;McKenzie, A.;Traffic statistics (October 1972);;;;;RFC 413;DOI 10.17487/RFC0413;November;https://www.rfc-editor.org/info/rfc413 | |
| RFC0414;;Bhushan, A.;File Transfer Protocol (FTP) status and further comments;;;;;RFC 414;DOI 10.17487/RFC0414;December;https://www.rfc-editor.org/info/rfc414 | |
| RFC0415;;Murray, H.;Tenex bandwidth;;;;;RFC 415;DOI 10.17487/RFC0415;November;https://www.rfc-editor.org/info/rfc415 | |
| RFC0416;;Norton, J.;ARC System Will Be Unavailable for Use During Thanksgiving Week;;;;;RFC 416;DOI 10.17487/RFC0416;November;https://www.rfc-editor.org/info/rfc416 | |
| RFC0417;;Postel, J. and C. Kline;Link usage violation;;;;;RFC 417;DOI 10.17487/RFC0417;December;https://www.rfc-editor.org/info/rfc417 | |
| RFC0418;;Hathaway, W.;Server File Transfer Under TSS/360 At NASA-Ames Research Center;;;;;RFC 418;DOI 10.17487/RFC0418;November;https://www.rfc-editor.org/info/rfc418 | |
| RFC0419;;Vezza, A.;To: Network liaisons and station agents;;;;;RFC 419;DOI 10.17487/RFC0419;December;https://www.rfc-editor.org/info/rfc419 | |
| RFC0420;;Murray, H.;CCA ICCC weather demo;;;;;RFC 420;DOI 10.17487/RFC0420;January;https://www.rfc-editor.org/info/rfc420 | |
| RFC0421;;McKenzie, A.;Software Consulting Service for Network Users;;;;;RFC 421;DOI 10.17487/RFC0421;November;https://www.rfc-editor.org/info/rfc421 | |
| RFC0422;;McKenzie, A.;Traffic statistics (November 1972);;;;;RFC 422;DOI 10.17487/RFC0422;December;https://www.rfc-editor.org/info/rfc422 | |
| RFC0423;;Noble, B.;UCLA Campus Computing Network Liaison Staff for ARPANET;;;;;RFC 423;DOI 10.17487/RFC0423;December;https://www.rfc-editor.org/info/rfc423 | |
| RFC0425;;Bressler, R.;"But my NCP costs $500 a day";;;;;RFC 425;DOI 10.17487/RFC0425;December;https://www.rfc-editor.org/info/rfc425 | |
| RFC0426;;Thomas, R.;Reconnection Protocol;;;;;RFC 426;DOI 10.17487/RFC0426;January;https://www.rfc-editor.org/info/rfc426 | |
| RFC0429;;Postel, J.;Character Generator Process;;;;;RFC 429;DOI 10.17487/RFC0429;December;https://www.rfc-editor.org/info/rfc429 | |
| RFC0430;;Braden, R.;Comments on File Transfer Protocol;;;;;RFC 430;DOI 10.17487/RFC0430;February;https://www.rfc-editor.org/info/rfc430 | |
| RFC0431;;Krilanovich, M.;Update on SMFS Login and Logout;;;;;RFC 431;DOI 10.17487/RFC0431;December;https://www.rfc-editor.org/info/rfc431 | |
| RFC0432;;Neigus, N.;Network logical map;;;;;RFC 432;DOI 10.17487/RFC0432;December;https://www.rfc-editor.org/info/rfc432 | |
| RFC0433;RFC0503;Postel, J.;Socket number list;;;;;RFC 433;DOI 10.17487/RFC0433;December;https://www.rfc-editor.org/info/rfc433 | |
| RFC0434;RFC0447;McKenzie, A.;IMP/TIP memory retrofit schedule;;;;;RFC 434;DOI 10.17487/RFC0434;January;https://www.rfc-editor.org/info/rfc434 | |
| RFC0435;;Cosell, B. and D. Walden;Telnet issues;;;;;RFC 435;DOI 10.17487/RFC0435;January;https://www.rfc-editor.org/info/rfc435 | |
| RFC0436;;Krilanovich, M.;Announcement of RJS at UCSB;;;;;RFC 436;DOI 10.17487/RFC0436;January;https://www.rfc-editor.org/info/rfc436 | |
| RFC0437;;Faeh, E.;Data Reconfiguration Service at UCSB;;;;;RFC 437;DOI 10.17487/RFC0437;June;https://www.rfc-editor.org/info/rfc437 | |
| RFC0438;;Thomas, R. and R. Clements;FTP server-server interaction;;;;;RFC 438;DOI 10.17487/RFC0438;January;https://www.rfc-editor.org/info/rfc438 | |
| RFC0439;;Cerf, V.;PARRY encounters the DOCTOR;;;;;RFC 439;DOI 10.17487/RFC0439;January;https://www.rfc-editor.org/info/rfc439 | |
| RFC0440;;Walden, D.;Scheduled network software maintenance;;;;;RFC 440;DOI 10.17487/RFC0440;January;https://www.rfc-editor.org/info/rfc440 | |
| RFC0441;;Bressler, R. and R. Thomas;Inter-Entity Communication - an experiment;;;;;RFC 441;DOI 10.17487/RFC0441;January;https://www.rfc-editor.org/info/rfc441 | |
| RFC0442;;Cerf, V.;Current flow-control scheme for IMPSYS;;;;;RFC 442;DOI 10.17487/RFC0442;January;https://www.rfc-editor.org/info/rfc442 | |
| RFC0443;;McKenzie, A.;Traffic statistics (December 1972);;;;;RFC 443;DOI 10.17487/RFC0443;January;https://www.rfc-editor.org/info/rfc443 | |
| RFC0445;;McKenzie, A.;IMP/TIP preventive maintenance schedule;;;;;RFC 445;DOI 10.17487/RFC0445;January;https://www.rfc-editor.org/info/rfc445 | |
| RFC0446;;Deutsch, L.;Proposal to consider a network program resource notebook;;;;;RFC 446;DOI 10.17487/RFC0446;January;https://www.rfc-editor.org/info/rfc446 | |
| RFC0447;RFC0476;McKenzie, A.;IMP/TIP memory retrofit schedule;;;;;RFC 447;DOI 10.17487/RFC0447;January;https://www.rfc-editor.org/info/rfc447 | |
| RFC0448;;Braden, R.;Print files in FTP;;;;;RFC 448;DOI 10.17487/RFC0448;February;https://www.rfc-editor.org/info/rfc448 | |
| RFC0449;;Walden, D.;Current flow-control scheme for IMPSYS;;;;;RFC 449;DOI 10.17487/RFC0449;January;https://www.rfc-editor.org/info/rfc449 | |
| RFC0450;;Padlipsky, M.;MULTICS sampling timeout change;;;;;RFC 450;DOI 10.17487/RFC0450;February;https://www.rfc-editor.org/info/rfc450 | |
| RFC0451;;Padlipsky, M.;Tentative proposal for a Unified User Level Protocol;;;;;RFC 451;DOI 10.17487/RFC0451;February;https://www.rfc-editor.org/info/rfc451 | |
| RFC0452;;Winett, J.;TELNET Command at Host LL;;;;;RFC 452;DOI 10.17487/RFC0452;February;https://www.rfc-editor.org/info/rfc452 | |
| RFC0453;;Kudlick, M.;Meeting announcement to discuss a network mail system;;;;;RFC 453;DOI 10.17487/RFC0453;February;https://www.rfc-editor.org/info/rfc453 | |
| RFC0454;;McKenzie, A.;File Transfer Protocol - meeting announcement and a new proposed document;;;;;RFC 454;DOI 10.17487/RFC0454;February;https://www.rfc-editor.org/info/rfc454 | |
| RFC0455;;McKenzie, A.;Traffic statistics (January 1973);;;;;RFC 455;DOI 10.17487/RFC0455;February;https://www.rfc-editor.org/info/rfc455 | |
| RFC0456;;Kudlick, M.;Memorandum: Date change of mail meeting;;;;;RFC 456;DOI 10.17487/RFC0456;February;https://www.rfc-editor.org/info/rfc456 | |
| RFC0457;;Walden, D.;TIPUG;;;;;RFC 457;DOI 10.17487/RFC0457;February;https://www.rfc-editor.org/info/rfc457 | |
| RFC0458;;Bressler, R. and R. Thomas;Mail retrieval via FTP;;;;;RFC 458;DOI 10.17487/RFC0458;February;https://www.rfc-editor.org/info/rfc458 | |
| RFC0459;;Kantrowitz, W.;Network questionnaires;;;;;RFC 459;DOI 10.17487/RFC0459;February;https://www.rfc-editor.org/info/rfc459 | |
| RFC0460;;Kline, C.;NCP survey;;;;;RFC 460;DOI 10.17487/RFC0460;February;https://www.rfc-editor.org/info/rfc460 | |
| RFC0461;;McKenzie, A.;Telnet Protocol meeting announcement;;;;;RFC 461;DOI 10.17487/RFC0461;February;https://www.rfc-editor.org/info/rfc461 | |
| RFC0462;;Iseli, J. and D. Crocker;Responding to user needs;;;;;RFC 462;DOI 10.17487/RFC0462;February;https://www.rfc-editor.org/info/rfc462 | |
| RFC0463;;Bhushan, A.;FTP comments and response to RFC 430;;;;;RFC 463;DOI 10.17487/RFC0463;February;https://www.rfc-editor.org/info/rfc463 | |
| RFC0464;;Kudlick, M.;Resource notebook framework;;;;;RFC 464;DOI 10.17487/RFC0464;February;https://www.rfc-editor.org/info/rfc464 | |
| RFC0466;;Winett, J.;Telnet logger/server for host LL-67;;;;;RFC 466;DOI 10.17487/RFC0466;February;https://www.rfc-editor.org/info/rfc466 | |
| RFC0467;;Burchfiel, J. and R. Tomlinson;Proposed change to Host-Host Protocol: Resynchronization of connection status;;;;;RFC 467;DOI 10.17487/RFC0467;February;https://www.rfc-editor.org/info/rfc467 | |
| RFC0468;;Braden, R.;FTP data compression;;;;;RFC 468;DOI 10.17487/RFC0468;March;https://www.rfc-editor.org/info/rfc468 | |
| RFC0469;;Kudlick, M.;Network mail meeting summary;;;;;RFC 469;DOI 10.17487/RFC0469;March;https://www.rfc-editor.org/info/rfc469 | |
| RFC0470;;Thomas, R.;Change in socket for TIP news facility;;;;;RFC 470;DOI 10.17487/RFC0470;March;https://www.rfc-editor.org/info/rfc470 | |
| RFC0471;;Thomas, R.;Workshop on multi-site executive programs;;;;;RFC 471;DOI 10.17487/RFC0471;March;https://www.rfc-editor.org/info/rfc471 | |
| RFC0472;;Bunch, S.;Illinois' reply to Maxwell's request for graphics information (NIC 14925);;;;;RFC 472;DOI 10.17487/RFC0472;March;https://www.rfc-editor.org/info/rfc472 | |
| RFC0473;;Walden, D.;MIX and MIXAL?;;;;;RFC 473;DOI 10.17487/RFC0473;February;https://www.rfc-editor.org/info/rfc473 | |
| RFC0474;;Bunch, S.;Announcement of NGWG meeting: Call for papers;;;;;RFC 474;DOI 10.17487/RFC0474;March;https://www.rfc-editor.org/info/rfc474 | |
| RFC0475;;Bhushan, A.;FTP and Network Mail System;;;;;RFC 475;DOI 10.17487/RFC0475;March;https://www.rfc-editor.org/info/rfc475 | |
| RFC0476;;McKenzie, A.;IMP/TIP memory retrofit schedule (rev 2);;;;;RFC 476;DOI 10.17487/RFC0476;March;https://www.rfc-editor.org/info/rfc476 | |
| RFC0477;;Krilanovich, M.;Remote Job Service at UCSB;;;;;RFC 477;DOI 10.17487/RFC0477;May;https://www.rfc-editor.org/info/rfc477 | |
| RFC0478;;Bressler, R. and R. Thomas;FTP server-server interaction - II;;;;;RFC 478;DOI 10.17487/RFC0478;March;https://www.rfc-editor.org/info/rfc478 | |
| RFC0479;;White, J.;Use of FTP by the NIC Journal;;;;;RFC 479;DOI 10.17487/RFC0479;March;https://www.rfc-editor.org/info/rfc479 | |
| RFC0480;;White, J.;Host-dependent FTP parameters;;;;;RFC 480;DOI 10.17487/RFC0480;March;https://www.rfc-editor.org/info/rfc480 | |
| RFC0482;;McKenzie, A.;Traffic statistics (February 1973);;;;;RFC 482;DOI 10.17487/RFC0482;March;https://www.rfc-editor.org/info/rfc482 | |
| RFC0483;;Kudlick, M.;Cancellation of the resource notebook framework meeting;;;;;RFC 483;DOI 10.17487/RFC0483;March;https://www.rfc-editor.org/info/rfc483 | |
| RFC0485;;Pickens, J.;MIX and MIXAL at UCSB;;;;;RFC 485;DOI 10.17487/RFC0485;March;https://www.rfc-editor.org/info/rfc485 | |
| RFC0486;;Bressler, R.;Data transfer revisited;;;;;RFC 486;DOI 10.17487/RFC0486;March;https://www.rfc-editor.org/info/rfc486 | |
| RFC0487;;Bressler, R.;Free file transfer;;;;;RFC 487;DOI 10.17487/RFC0487;April;https://www.rfc-editor.org/info/rfc487 | |
| RFC0488;;Auerbach, M.;NLS classes at network sites;;;;;RFC 488;DOI 10.17487/RFC0488;March;https://www.rfc-editor.org/info/rfc488 | |
| RFC0489;;Postel, J.;Comment on resynchronization of connection status proposal;;;;;RFC 489;DOI 10.17487/RFC0489;March;https://www.rfc-editor.org/info/rfc489 | |
| RFC0490;;Pickens, J.;Surrogate RJS for UCLA-CCN;;;;;RFC 490;DOI 10.17487/RFC0490;March;https://www.rfc-editor.org/info/rfc490 | |
| RFC0491;;Padlipsky, M.;What is "Free"?;;;;;RFC 491;DOI 10.17487/RFC0491;April;https://www.rfc-editor.org/info/rfc491 | |
| RFC0492;;Meyer, E.;Response to RFC 467;;;;;RFC 492;DOI 10.17487/RFC0492;April;https://www.rfc-editor.org/info/rfc492 | |
| RFC0493;;Michener, J., Cotton, I., Kelley, K., Liddle, D., and E. Meyer;GRAPHICS PROTOCOL;;;;;RFC 493;DOI 10.17487/RFC0493;April;https://www.rfc-editor.org/info/rfc493 | |
| RFC0494;;Walden, D.;Availability of MIX and MIXAL in the Network;;;;;RFC 494;DOI 10.17487/RFC0494;April;https://www.rfc-editor.org/info/rfc494 | |
| RFC0495;;McKenzie, A.;Telnet Protocol specifications;;;;;RFC 495;DOI 10.17487/RFC0495;May;https://www.rfc-editor.org/info/rfc495 | |
| RFC0496;;Auerbach, M.;TNLS quick reference card is available;;;;;RFC 496;DOI 10.17487/RFC0496;April;https://www.rfc-editor.org/info/rfc496 | |
| RFC0497;;McKenzie, A.;Traffic Statistics (March 1973);;;;;RFC 497;DOI 10.17487/RFC0497;April;https://www.rfc-editor.org/info/rfc497 | |
| RFC0498;;Braden, R.;On mail service to CCN;;;;;RFC 498;DOI 10.17487/RFC0498;April;https://www.rfc-editor.org/info/rfc498 | |
| RFC0499;;Reussow, B.;Harvard's network RJE;;;;;RFC 499;DOI 10.17487/RFC0499;April;https://www.rfc-editor.org/info/rfc499 | |
| RFC0500;;Shoshani, A. and I. Spiegler;Integration of data management systems on a computer network;;;;;RFC 500;DOI 10.17487/RFC0500;April;https://www.rfc-editor.org/info/rfc500 | |
| RFC0501;;Pogran, K.;Un-muddling "free file transfer";;;;;RFC 501;DOI 10.17487/RFC0501;May;https://www.rfc-editor.org/info/rfc501 | |
| RFC0503;RFC0739;Neigus, N. and J. Postel;Socket number list;;;;;RFC 503;DOI 10.17487/RFC0503;April;https://www.rfc-editor.org/info/rfc503 | |
| RFC0504;;Thomas, R.;Distributed resources workshop announcement;;;;;RFC 504;DOI 10.17487/RFC0504;April;https://www.rfc-editor.org/info/rfc504 | |
| RFC0505;;Padlipsky, M.;Two solutions to a file transfer access problem;;;;;RFC 505;DOI 10.17487/RFC0505;June;https://www.rfc-editor.org/info/rfc505 | |
| RFC0506;;Padlipsky, M.;FTP command naming problem;;;;;RFC 506;DOI 10.17487/RFC0506;June;https://www.rfc-editor.org/info/rfc506 | |
| RFC0508;;Pfeifer, L. and J. McAfee;Real-time data transmission on the ARPANET;;;;;RFC 508;DOI 10.17487/RFC0508;May;https://www.rfc-editor.org/info/rfc508 | |
| RFC0509;;McKenzie, A.;Traffic statistics (April 1973);;;;;RFC 509;DOI 10.17487/RFC0509;April;https://www.rfc-editor.org/info/rfc509 | |
| RFC0510;;White, J.;Request for network mailbox addresses;;;;;RFC 510;DOI 10.17487/RFC0510;May;https://www.rfc-editor.org/info/rfc510 | |
| RFC0511;;North, J.;Enterprise phone service to NIC from ARPANET sites;;;;;RFC 511;DOI 10.17487/RFC0511;May;https://www.rfc-editor.org/info/rfc511 | |
| RFC0512;;Hathaway, W.;More on lost message detection;;;;;RFC 512;DOI 10.17487/RFC0512;May;https://www.rfc-editor.org/info/rfc512 | |
| RFC0513;;Hathaway, W.;Comments on the new Telnet specifications;;;;;RFC 513;DOI 10.17487/RFC0513;May;https://www.rfc-editor.org/info/rfc513 | |
| RFC0514;;Kantrowitz, W.;Network make-work;;;;;RFC 514;DOI 10.17487/RFC0514;June;https://www.rfc-editor.org/info/rfc514 | |
| RFC0515;;Winter, R.;Specifications for Datalanguage, Version 0/9;;;;;RFC 515;DOI 10.17487/RFC0515;June;https://www.rfc-editor.org/info/rfc515 | |
| RFC0516;;Postel, J.;Lost message detection;;;;;RFC 516;DOI 10.17487/RFC0516;May;https://www.rfc-editor.org/info/rfc516 | |
| RFC0518;;Vaughan, N. and E. Feinler;ARPANET accounts;;;;;RFC 518;DOI 10.17487/RFC0518;June;https://www.rfc-editor.org/info/rfc518 | |
| RFC0519;;Pickens, J.;Resource Evaluation;;;;;RFC 519;DOI 10.17487/RFC0519;June;https://www.rfc-editor.org/info/rfc519 | |
| RFC0520;;Day, J.;Memo to FTP group: Proposal for File Access Protocol;;;;;RFC 520;DOI 10.17487/RFC0520;June;https://www.rfc-editor.org/info/rfc520 | |
| RFC0521;;McKenzie, A.;Restricted use of IMP DDT;;;;;RFC 521;DOI 10.17487/RFC0521;May;https://www.rfc-editor.org/info/rfc521 | |
| RFC0522;;McKenzie, A.;Traffic Statistics (May 1973);;;;;RFC 522;DOI 10.17487/RFC0522;June;https://www.rfc-editor.org/info/rfc522 | |
| RFC0523;;Bhushan, A.;SURVEY is in operation again;;;;;RFC 523;DOI 10.17487/RFC0523;June;https://www.rfc-editor.org/info/rfc523 | |
| RFC0524;;White, J.;Proposed Mail Protocol;;;;;RFC 524;DOI 10.17487/RFC0524;June;https://www.rfc-editor.org/info/rfc524 | |
| RFC0525;;Parrish, W. and J. Pickens;MIT-MATHLAB meets UCSB-OLS -an example of resource sharing;;;;;RFC 525;DOI 10.17487/RFC0525;June;https://www.rfc-editor.org/info/rfc525 | |
| RFC0526;;Pratt, W.;Technical meeting: Digital image processing software systems;;;;;RFC 526;DOI 10.17487/RFC0526;June;https://www.rfc-editor.org/info/rfc526 | |
| RFC0527;;Merryman, R.;ARPAWOCKY;;;;;RFC 527;DOI 10.17487/RFC0527;May;https://www.rfc-editor.org/info/rfc527 | |
| RFC0528;;McQuillan, J.;Software checksumming in the IMP and network reliability;;;;;RFC 528;DOI 10.17487/RFC0528;June;https://www.rfc-editor.org/info/rfc528 | |
| RFC0529;;McKenzie, A., Thomas, R., Tomlinson, R., and K. Pogran;Note on protocol synch sequences;;;;;RFC 529;DOI 10.17487/RFC0529;June;https://www.rfc-editor.org/info/rfc529 | |
| RFC0530;;Bhushan, A.;Report on the Survey Project;;;;;RFC 530;DOI 10.17487/RFC0530;June;https://www.rfc-editor.org/info/rfc530 | |
| RFC0531;;Padlipsky, M.;Feast or famine? A response to two recent RFC's about network information;;;;;RFC 531;DOI 10.17487/RFC0531;June;https://www.rfc-editor.org/info/rfc531 | |
| RFC0532;;Merryman, R.;UCSD-CC Server-FTP facility;;;;;RFC 532;DOI 10.17487/RFC0532;July;https://www.rfc-editor.org/info/rfc532 | |
| RFC0533;;Walden, D.;Message-ID numbers;;;;;RFC 533;DOI 10.17487/RFC0533;July;https://www.rfc-editor.org/info/rfc533 | |
| RFC0534;;Walden, D.;Lost message detection;;;;;RFC 534;DOI 10.17487/RFC0534;July;https://www.rfc-editor.org/info/rfc534 | |
| RFC0535;;Thomas, R.;Comments on File Access Protocol;;;;;RFC 535;DOI 10.17487/RFC0535;July;https://www.rfc-editor.org/info/rfc535 | |
| RFC0537;;Bunch, S.;Announcement of NGG meeting July 16-17;;;;;RFC 537;DOI 10.17487/RFC0537;June;https://www.rfc-editor.org/info/rfc537 | |
| RFC0538;;McKenzie, A.;Traffic statistics (June 1973);;;;;RFC 538;DOI 10.17487/RFC0538;July;https://www.rfc-editor.org/info/rfc538 | |
| RFC0539;;Crocker, D. and J. Postel;Thoughts on the mail protocol proposed in RFC 524;;;;;RFC 539;DOI 10.17487/RFC0539;July;https://www.rfc-editor.org/info/rfc539 | |
| RFC0542;RFC0765;Neigus, N.;File Transfer Protocol;;;;;RFC 542;DOI 10.17487/RFC0542;August;https://www.rfc-editor.org/info/rfc542 | |
| RFC0543;;Meyer, N.;Network journal submission and delivery;;;;;RFC 543;DOI 10.17487/RFC0543;July;https://www.rfc-editor.org/info/rfc543 | |
| RFC0544;;Meyer, N. and K. Kelley;Locating on-line documentation at SRI-ARC;;;;;RFC 544;DOI 10.17487/RFC0544;July;https://www.rfc-editor.org/info/rfc544 | |
| RFC0545;;Pickens, J.;Of what quality be the UCSB resources evaluators?;;;;;RFC 545;DOI 10.17487/RFC0545;July;https://www.rfc-editor.org/info/rfc545 | |
| RFC0546;;Thomas, R.;Tenex load averages for July 1973;;;;;RFC 546;DOI 10.17487/RFC0546;August;https://www.rfc-editor.org/info/rfc546 | |
| RFC0547;;Walden, D.;Change to the Very Distant Host specification;;;;;RFC 547;DOI 10.17487/RFC0547;August;https://www.rfc-editor.org/info/rfc547 | |
| RFC0548;;Walden, D.;Hosts using the IMP Going Down message;;;;;RFC 548;DOI 10.17487/RFC0548;August;https://www.rfc-editor.org/info/rfc548 | |
| RFC0549;;Michener, J.;Minutes of Network Graphics Group meeting, 15-17 July 1973;;;;;RFC 549;DOI 10.17487/RFC0549;July;https://www.rfc-editor.org/info/rfc549 | |
| RFC0550;;Deutsch, L.;NIC NCP experiment;;;;;RFC 550;DOI 10.17487/RFC0550;August;https://www.rfc-editor.org/info/rfc550 | |
| RFC0551;;Feinroth, Y. and R. Fink;NYU, ANL, and LBL Joining the Net;;;;;RFC 551;DOI 10.17487/RFC0551;August;https://www.rfc-editor.org/info/rfc551 | |
| RFC0552;;Owen, A.;Single access to standard protocols;;;;;RFC 552;DOI 10.17487/RFC0552;July;https://www.rfc-editor.org/info/rfc552 | |
| RFC0553;;Irby, C. and K. Victor;Draft design for a text/graphics protocol;;;;;RFC 553;DOI 10.17487/RFC0553;July;https://www.rfc-editor.org/info/rfc553 | |
| RFC0555;;White, J.;Responses to critiques of the proposed mail protocol;;;;;RFC 555;DOI 10.17487/RFC0555;July;https://www.rfc-editor.org/info/rfc555 | |
| RFC0556;;McKenzie, A.;Traffic Statistics (July 1973);;;;;RFC 556;DOI 10.17487/RFC0556;August;https://www.rfc-editor.org/info/rfc556 | |
| RFC0557;;Wessler, B.;REVELATIONS IN NETWORK HOST MEASUREMENTS;;;;;RFC 557;DOI 10.17487/RFC0557;August;https://www.rfc-editor.org/info/rfc557 | |
| RFC0559;;Bushan, A.;Comments on The New Telnet Protocol and its Implementation;;;;;RFC 559;DOI 10.17487/RFC0559;August;https://www.rfc-editor.org/info/rfc559 | |
| RFC0560;;Crocker, D. and J. Postel;Remote Controlled Transmission and Echoing Telnet option;;;;;RFC 560;DOI 10.17487/RFC0560;August;https://www.rfc-editor.org/info/rfc560 | |
| RFC0561;;Bhushan, A., Pogran, K., Tomlinson, R., and J. White;Standardizing Network Mail Headers;;;;;RFC 561;DOI 10.17487/RFC0561;September;https://www.rfc-editor.org/info/rfc561 | |
| RFC0562;;McKenzie, A.;Modifications to the TELNET Specification;;;;;RFC 562;DOI 10.17487/RFC0562;August;https://www.rfc-editor.org/info/rfc562 | |
| RFC0563;;Davidson, J.;Comments on the RCTE Telnet option;;;;;RFC 563;DOI 10.17487/RFC0563;August;https://www.rfc-editor.org/info/rfc563 | |
| RFC0565;;Cantor, D.;Storing network survey data at the datacomputer;;;;;RFC 565;DOI 10.17487/RFC0565;August;https://www.rfc-editor.org/info/rfc565 | |
| RFC0566;;McKenzie, A.;Traffic statistics (August 1973);;;;;RFC 566;DOI 10.17487/RFC0566;September;https://www.rfc-editor.org/info/rfc566 | |
| RFC0567;;Deutsch, L.;Cross Country Network Bandwidth;;;;;RFC 567;DOI 10.17487/RFC0567;September;https://www.rfc-editor.org/info/rfc567 | |
| RFC0568;;McQuillan, J.;Response to RFC 567 - cross country network bandwidth;;;;;RFC 568;DOI 10.17487/RFC0568;September;https://www.rfc-editor.org/info/rfc568 | |
| RFC0569;;Padlipsky, M.;NETED: A Common Editor for the ARPA Network;;;;;RFC 569;DOI 10.17487/RFC0569;October;https://www.rfc-editor.org/info/rfc569 | |
| RFC0570;;Pickens, J.;Experimental input mapping between NVT ASCII and UCSB On Line System;;;;;RFC 570;DOI 10.17487/RFC0570;October;https://www.rfc-editor.org/info/rfc570 | |
| RFC0571;;Braden, R.;TENEX FTP PROBLEM;;;;;RFC 571;DOI 10.17487/RFC0571;November;https://www.rfc-editor.org/info/rfc571 | |
| RFC0573;;Bhushan, A.;DATA AND FILE TRANSFER - SOME MEASUREMENT RESULTS;;;;;RFC 573;DOI 10.17487/RFC0573;September;https://www.rfc-editor.org/info/rfc573 | |
| RFC0574;;Krilanovich, M.;Announcement of a Mail Facility at UCSB;;;;;RFC 574;DOI 10.17487/RFC0574;September;https://www.rfc-editor.org/info/rfc574 | |
| RFC0576;;Victor, K.;Proposal for modifying linking;;;;;RFC 576;DOI 10.17487/RFC0576;September;https://www.rfc-editor.org/info/rfc576 | |
| RFC0577;;Crocker, D.;Mail priority;;;;;RFC 577;DOI 10.17487/RFC0577;October;https://www.rfc-editor.org/info/rfc577 | |
| RFC0578;;Bhushan, A. and N. Ryan;Using MIT-Mathlab MACSYMA from MIT-DMS Muddle;;;;;RFC 578;DOI 10.17487/RFC0578;October;https://www.rfc-editor.org/info/rfc578 | |
| RFC0579;;McKenzie, A.;Traffic statistics (September 1973);;;;;RFC 579;DOI 10.17487/RFC0579;November;https://www.rfc-editor.org/info/rfc579 | |
| RFC0580;;Postel, J.;Note to Protocol Designers and Implementers;;;;;RFC 580;DOI 10.17487/RFC0580;October;https://www.rfc-editor.org/info/rfc580 | |
| RFC0581;;Crocker, D. and J. Postel;Corrections to RFC 560: Remote Controlled Transmission and Echoing Telnet Option;;;;;RFC 581;DOI 10.17487/RFC0581;November;https://www.rfc-editor.org/info/rfc581 | |
| RFC0582;;Clements, R.;Comments on RFC 580: Machine readable protocols;;;;;RFC 582;DOI 10.17487/RFC0582;November;https://www.rfc-editor.org/info/rfc582 | |
| RFC0584;;Iseli, J., Crocker, D., and N. Neigus;Charter for ARPANET Users Interest Working Group;;;;;RFC 584;DOI 10.17487/RFC0584;November;https://www.rfc-editor.org/info/rfc584 | |
| RFC0585;;Crocker, D., Neigus, N., Feinler, E., and J. Iseli;ARPANET users interest working group meeting;;;;;RFC 585;DOI 10.17487/RFC0585;November;https://www.rfc-editor.org/info/rfc585 | |
| RFC0586;;McKenzie, A.;Traffic statistics (October 1973);;;;;RFC 586;DOI 10.17487/RFC0586;November;https://www.rfc-editor.org/info/rfc586 | |
| RFC0587;;Postel, J.;Announcing New Telnet Options;;;;;RFC 587;DOI 10.17487/RFC0587;November;https://www.rfc-editor.org/info/rfc587 | |
| RFC0588;;Stokes, A.;London Node Is Now Up;;;;;RFC 588;DOI 10.17487/RFC0588;October;https://www.rfc-editor.org/info/rfc588 | |
| RFC0589;;Braden, R.;CCN NETRJS server messages to remote user;;;;;RFC 589;DOI 10.17487/RFC0589;November;https://www.rfc-editor.org/info/rfc589 | |
| RFC0590;;Padlipsky, M.;MULTICS address change;;;;;RFC 590;DOI 10.17487/RFC0590;November;https://www.rfc-editor.org/info/rfc590 | |
| RFC0591;;Walden, D.;Addition to the Very Distant Host specifications;;;;;RFC 591;DOI 10.17487/RFC0591;November;https://www.rfc-editor.org/info/rfc591 | |
| RFC0592;;Watson, R.;Some thoughts on system design to facilitate resource sharing;;;;;RFC 592;DOI 10.17487/RFC0592;November;https://www.rfc-editor.org/info/rfc592 | |
| RFC0593;;McKenzie, A. and J. Postel;Telnet and FTP implementation schedule change;;;;;RFC 593;DOI 10.17487/RFC0593;November;https://www.rfc-editor.org/info/rfc593 | |
| RFC0594;;Burchfiel, J.;Speedup of Host-IMP interface;;;;;RFC 594;DOI 10.17487/RFC0594;December;https://www.rfc-editor.org/info/rfc594 | |
| RFC0595;;Hathaway, W.;Second thoughts in defense of the Telnet Go-Ahead;;;;;RFC 595;DOI 10.17487/RFC0595;December;https://www.rfc-editor.org/info/rfc595 | |
| RFC0596;;Taft, E.;Second thoughts on Telnet Go-Ahead;;;;;RFC 596;DOI 10.17487/RFC0596;December;https://www.rfc-editor.org/info/rfc596 | |
| RFC0597;;Neigus, N. and E. Feinler;Host status;;;;;RFC 597;DOI 10.17487/RFC0597;December;https://www.rfc-editor.org/info/rfc597 | |
| RFC0598;;Network Information Center. Stanford Research Institute;RFC index - December 5, 1973;;;;;RFC 598;DOI 10.17487/RFC0598;December;https://www.rfc-editor.org/info/rfc598 | |
| RFC0599;RFC0740;Braden, R.;Update on NETRJS;;;;;RFC 599;DOI 10.17487/RFC0599;December;https://www.rfc-editor.org/info/rfc599 | |
| RFC0600;;Berggreen, A.;Interfacing an Illinois plasma terminal to the ARPANET;;;;;RFC 600;DOI 10.17487/RFC0600;November;https://www.rfc-editor.org/info/rfc600 | |
| RFC0601;;McKenzie, A.;Traffic statistics (November 1973);;;;;RFC 601;DOI 10.17487/RFC0601;December;https://www.rfc-editor.org/info/rfc601 | |
| RFC0602;;Metcalfe, R.;"The stockings were hung by the chimney with care";;;;;RFC 602;DOI 10.17487/RFC0602;December;https://www.rfc-editor.org/info/rfc602 | |
| RFC0603;;Burchfiel, J.;Response to RFC 597: Host status;;;;;RFC 603;DOI 10.17487/RFC0603;December;https://www.rfc-editor.org/info/rfc603 | |
| RFC0604;RFC0739;Postel, J.;Assigned link numbers;;;;;RFC 604;DOI 10.17487/RFC0604;December;https://www.rfc-editor.org/info/rfc604 | |
| RFC0606;;Deutsch, L.;Host names on-line;;;;;RFC 606;DOI 10.17487/RFC0606;December;https://www.rfc-editor.org/info/rfc606 | |
| RFC0607;RFC0624;Krilanovich, M. and G. Gregg;Comments on the File Transfer Protocol;;;;;RFC 607;DOI 10.17487/RFC0607;January;https://www.rfc-editor.org/info/rfc607 | |
| RFC0608;RFC0810;Kudlick, M.;Host names on-line;;;;;RFC 608;DOI 10.17487/RFC0608;January;https://www.rfc-editor.org/info/rfc608 | |
| RFC0609;;Ferguson, B.;Statement of upcoming move of NIC/NLS service;;;;;RFC 609;DOI 10.17487/RFC0609;January;https://www.rfc-editor.org/info/rfc609 | |
| RFC0610;;Winter, R., Hill, J., and W. Greiff;Further datalanguage design concepts;;;;;RFC 610;DOI 10.17487/RFC0610;December;https://www.rfc-editor.org/info/rfc610 | |
| RFC0611;;Walden, D.;Two changes to the IMP/Host Protocol to improve user/network communications;;;;;RFC 611;DOI 10.17487/RFC0611;February;https://www.rfc-editor.org/info/rfc611 | |
| RFC0612;;McKenzie, A.;Traffic statistics (December 1973);;;;;RFC 612;DOI 10.17487/RFC0612;January;https://www.rfc-editor.org/info/rfc612 | |
| RFC0613;;McKenzie, A.;Network connectivity: A response to RFC 603;;;;;RFC 613;DOI 10.17487/RFC0613;January;https://www.rfc-editor.org/info/rfc613 | |
| RFC0614;;Pogran, K. and N. Neigus;Response to RFC 607: "Comments on the File Transfer Protocol";;;;;RFC 614;DOI 10.17487/RFC0614;January;https://www.rfc-editor.org/info/rfc614 | |
| RFC0615;RFC0645;Crocker, D.;Proposed Network Standard Data Pathname syntax;;;;;RFC 615;DOI 10.17487/RFC0615;March;https://www.rfc-editor.org/info/rfc615 | |
| RFC0616;;Walden, D.;LATEST NETWORK MAPS;;;;;RFC 616;DOI 10.17487/RFC0616;February;https://www.rfc-editor.org/info/rfc616 | |
| RFC0617;;Taft, E.;Note on socket number assignment;;;;;RFC 617;DOI 10.17487/RFC0617;February;https://www.rfc-editor.org/info/rfc617 | |
| RFC0618;;Taft, E.;Few observations on NCP statistics;;;;;RFC 618;DOI 10.17487/RFC0618;February;https://www.rfc-editor.org/info/rfc618 | |
| RFC0619;;Naylor, W. and H. Opderbeck;Mean round-trip times in the ARPANET;;;;;RFC 619;DOI 10.17487/RFC0619;March;https://www.rfc-editor.org/info/rfc619 | |
| RFC0620;;Ferguson, B.;Request for monitor host table updates;;;;;RFC 620;DOI 10.17487/RFC0620;March;https://www.rfc-editor.org/info/rfc620 | |
| RFC0621;;Kudlick, M.;NIC user directories at SRI ARC;;;;;RFC 621;DOI 10.17487/RFC0621;March;https://www.rfc-editor.org/info/rfc621 | |
| RFC0622;;McKenzie, A.;Scheduling IMP/TIP down time;;;;;RFC 622;DOI 10.17487/RFC0622;March;https://www.rfc-editor.org/info/rfc622 | |
| RFC0623;;Krilanovich, M.;Comments on on-line host name service;;;;;RFC 623;DOI 10.17487/RFC0623;February;https://www.rfc-editor.org/info/rfc623 | |
| RFC0624;;Krilanovich, M., Gregg, G., Hathaway, W., and J. White;Comments on the File Transfer Protocol;;;;;RFC 624;DOI 10.17487/RFC0624;February;https://www.rfc-editor.org/info/rfc624 | |
| RFC0625;;Kudlick, M. and E. Feinler;On-line hostnames service;;;;;RFC 625;DOI 10.17487/RFC0625;March;https://www.rfc-editor.org/info/rfc625 | |
| RFC0626;;Kleinrock, L. and H. Opderbeck;On a possible lockup condition in IMP subnet due to message sequencing;;;;;RFC 626;DOI 10.17487/RFC0626;March;https://www.rfc-editor.org/info/rfc626 | |
| RFC0627;;Kudlick, M. and E. Feinler;ASCII text file of hostnames;;;;;RFC 627;DOI 10.17487/RFC0627;March;https://www.rfc-editor.org/info/rfc627 | |
| RFC0628;;Keeney, M.;Status of RFC numbers and a note on pre-assigned journal numbers;;;;;RFC 628;DOI 10.17487/RFC0628;March;https://www.rfc-editor.org/info/rfc628 | |
| RFC0629;;North, J.;Scenario for using the Network Journal;;;;;RFC 629;DOI 10.17487/RFC0629;March;https://www.rfc-editor.org/info/rfc629 | |
| RFC0630;;Sussman, J.;FTP error code usage for more reliable mail service;;;;;RFC 630;DOI 10.17487/RFC0630;April;https://www.rfc-editor.org/info/rfc630 | |
| RFC0631;;Danthine, A.;International meeting on minicomputers and data communication: Call for papers;;;;;RFC 631;DOI 10.17487/RFC0631;April;https://www.rfc-editor.org/info/rfc631 | |
| RFC0632;;Opderbeck, H.;Throughput degradations for single packet messages;;;;;RFC 632;DOI 10.17487/RFC0632;May;https://www.rfc-editor.org/info/rfc632 | |
| RFC0633;RFC0638;McKenzie, A.;IMP/TIP preventive maintenance schedule;;;;;RFC 633;DOI 10.17487/RFC0633;March;https://www.rfc-editor.org/info/rfc633 | |
| RFC0634;;McKenzie, A.;Change in network address for Haskins Lab;;;;;RFC 634;DOI 10.17487/RFC0634;April;https://www.rfc-editor.org/info/rfc634 | |
| RFC0635;;Cerf, V.;Assessment of ARPANET protocols;;;;;RFC 635;DOI 10.17487/RFC0635;April;https://www.rfc-editor.org/info/rfc635 | |
| RFC0636;;Burchfiel, J., Cosell, B., Tomlinson, R., and D. Walden;TIP/Tenex reliability improvements;;;;;RFC 636;DOI 10.17487/RFC0636;June;https://www.rfc-editor.org/info/rfc636 | |
| RFC0637;;McKenzie, A.;Change of network address for SU-DSL;;;;;RFC 637;DOI 10.17487/RFC0637;April;https://www.rfc-editor.org/info/rfc637 | |
| RFC0638;;McKenzie, A.;IMP/TIP preventive maintenance schedule;;;;;RFC 638;DOI 10.17487/RFC0638;April;https://www.rfc-editor.org/info/rfc638 | |
| RFC0640;;Postel, J.;Revised FTP reply codes;;;;;RFC 640;DOI 10.17487/RFC0640;June;https://www.rfc-editor.org/info/rfc640 | |
| RFC0642;;Burchfiel, J.;Ready line philosophy and implementation;;;;;RFC 642;DOI 10.17487/RFC0642;July;https://www.rfc-editor.org/info/rfc642 | |
| RFC0643;;Mader, E.;Network Debugging Protocol;;;;;RFC 643;DOI 10.17487/RFC0643;July;https://www.rfc-editor.org/info/rfc643 | |
| RFC0644;;Thomas, R.;On the problem of signature authentication for network mail;;;;;RFC 644;DOI 10.17487/RFC0644;July;https://www.rfc-editor.org/info/rfc644 | |
| RFC0645;;Crocker, D.;Network Standard Data Specification syntax;;;;;RFC 645;DOI 10.17487/RFC0645;June;https://www.rfc-editor.org/info/rfc645 | |
| RFC0647;;Padlipsky, M.;Proposed protocol for connecting host computers to ARPA-like networks via front end processors;;;;;RFC 647;DOI 10.17487/RFC0647;November;https://www.rfc-editor.org/info/rfc647 | |
| RFC0651;RFC0859;Crocker, D.;Revised Telnet status option;;;;;RFC 651;DOI 10.17487/RFC0651;October;https://www.rfc-editor.org/info/rfc651 | |
| RFC0652;;Crocker, D.;Telnet output carriage-return disposition option;;;;;RFC 652;DOI 10.17487/RFC0652;October;https://www.rfc-editor.org/info/rfc652 | |
| RFC0653;;Crocker, D.;Telnet output horizontal tabstops option;;;;;RFC 653;DOI 10.17487/RFC0653;October;https://www.rfc-editor.org/info/rfc653 | |
| RFC0654;;Crocker, D.;Telnet output horizontal tab disposition option;;;;;RFC 654;DOI 10.17487/RFC0654;October;https://www.rfc-editor.org/info/rfc654 | |
| RFC0655;;Crocker, D.;Telnet output formfeed disposition option;;;;;RFC 655;DOI 10.17487/RFC0655;October;https://www.rfc-editor.org/info/rfc655 | |
| RFC0656;;Crocker, D.;Telnet output vertical tabstops option;;;;;RFC 656;DOI 10.17487/RFC0656;October;https://www.rfc-editor.org/info/rfc656 | |
| RFC0657;;Crocker, D.;Telnet output vertical tab disposition option;;;;;RFC 657;DOI 10.17487/RFC0657;October;https://www.rfc-editor.org/info/rfc657 | |
| RFC0658;;Crocker, D.;Telnet output linefeed disposition;;;;;RFC 658;DOI 10.17487/RFC0658;October;https://www.rfc-editor.org/info/rfc658 | |
| RFC0659;;Postel, J.;Announcing additional Telnet options;;;;;RFC 659;DOI 10.17487/RFC0659;October;https://www.rfc-editor.org/info/rfc659 | |
| RFC0660;;Walden, D.;Some changes to the IMP and the IMP/Host interface;;;;;RFC 660;DOI 10.17487/RFC0660;October;https://www.rfc-editor.org/info/rfc660 | |
| RFC0661;;Postel, J.;Protocol information;;;;;RFC 661;DOI 10.17487/RFC0661;November;https://www.rfc-editor.org/info/rfc661 | |
| RFC0662;;Kanodia, R.;Performance improvement in ARPANET file transfers from Multics;;;;;RFC 662;DOI 10.17487/RFC0662;November;https://www.rfc-editor.org/info/rfc662 | |
| RFC0663;;Kanodia, R.;Lost message detection and recovery protocol;;;;;RFC 663;DOI 10.17487/RFC0663;November;https://www.rfc-editor.org/info/rfc663 | |
| RFC0666;;Padlipsky, M.;Specification of the Unified User-Level Protocol;;;;;RFC 666;DOI 10.17487/RFC0666;November;https://www.rfc-editor.org/info/rfc666 | |
| RFC0667;;Chipman, S.;Host Ports;;;;;RFC 667;DOI 10.17487/RFC0667;December;https://www.rfc-editor.org/info/rfc667 | |
| RFC0669;;Dodds, D.;November, 1974, survey of New-Protocol Telnet servers;;;;;RFC 669;DOI 10.17487/RFC0669;December;https://www.rfc-editor.org/info/rfc669 | |
| RFC0671;;Schantz, R.;Note on Reconnection Protocol;;;;;RFC 671;DOI 10.17487/RFC0671;December;https://www.rfc-editor.org/info/rfc671 | |
| RFC0672;;Schantz, R.;Multi-site data collection facility;;;;;RFC 672;DOI 10.17487/RFC0672;December;https://www.rfc-editor.org/info/rfc672 | |
| RFC0674;;Postel, J. and J. White;Procedure call documents: Version 2;;;;;RFC 674;DOI 10.17487/RFC0674;December;https://www.rfc-editor.org/info/rfc674 | |
| RFC0675;RFC7805;Cerf, V., Dalal, Y., and C. Sunshine;Specification of Internet Transmission Control Program;;;;;RFC 675;DOI 10.17487/RFC0675;December;https://www.rfc-editor.org/info/rfc675 | |
| RFC0677;;Johnson, P. and R. Thomas;Maintenance of duplicate databases;;;;;RFC 677;DOI 10.17487/RFC0677;January;https://www.rfc-editor.org/info/rfc677 | |
| RFC0678;;Postel, J.;Standard file formats;;;;;RFC 678;DOI 10.17487/RFC0678;December;https://www.rfc-editor.org/info/rfc678 | |
| RFC0679;;Dodds, D.;February, 1975, survey of New-Protocol Telnet servers;;;;;RFC 679;DOI 10.17487/RFC0679;February;https://www.rfc-editor.org/info/rfc679 | |
| RFC0680;;Myer, T. and D. Henderson;Message Transmission Protocol;;;;;RFC 680;DOI 10.17487/RFC0680;April;https://www.rfc-editor.org/info/rfc680 | |
| RFC0681;;Holmgren, S.;Network UNIX;;;;;RFC 681;DOI 10.17487/RFC0681;March;https://www.rfc-editor.org/info/rfc681 | |
| RFC0683;;Clements, R.;FTPSRV - Tenex extension for paged files;;;;;RFC 683;DOI 10.17487/RFC0683;April;https://www.rfc-editor.org/info/rfc683 | |
| RFC0684;;Schantz, R.;Commentary on procedure calling as a network protocol;;;;;RFC 684;DOI 10.17487/RFC0684;April;https://www.rfc-editor.org/info/rfc684 | |
| RFC0685;;Beeler, M.;Response time in cross network debugging;;;;;RFC 685;DOI 10.17487/RFC0685;April;https://www.rfc-editor.org/info/rfc685 | |
| RFC0686;;Harvey, B.;Leaving well enough alone;;;;;RFC 686;DOI 10.17487/RFC0686;May;https://www.rfc-editor.org/info/rfc686 | |
| RFC0687;RFC0704;Walden, D.;IMP/Host and Host/IMP Protocol changes;;;;;RFC 687;DOI 10.17487/RFC0687;June;https://www.rfc-editor.org/info/rfc687 | |
| RFC0688;;Walden, D.;Tentative schedule for the new Telnet implementation for the TIP;;;;;RFC 688;DOI 10.17487/RFC0688;June;https://www.rfc-editor.org/info/rfc688 | |
| RFC0689;;Clements, R.;Tenex NCP finite state machine for connections;;;;;RFC 689;DOI 10.17487/RFC0689;May;https://www.rfc-editor.org/info/rfc689 | |
| RFC0690;;Postel, J.;Comments on the proposed Host/IMP Protocol changes;;;;;RFC 690;DOI 10.17487/RFC0690;June;https://www.rfc-editor.org/info/rfc690 | |
| RFC0691;;Harvey, B.;One more try on the FTP;;;;;RFC 691;DOI 10.17487/RFC0691;June;https://www.rfc-editor.org/info/rfc691 | |
| RFC0692;;Wolfe, S.;Comments on IMP/Host Protocol changes (RFCs 687 and 690);;;;;RFC 692;DOI 10.17487/RFC0692;June;https://www.rfc-editor.org/info/rfc692 | |
| RFC0694;;Postel, J.;Protocol information;;;;;RFC 694;DOI 10.17487/RFC0694;June;https://www.rfc-editor.org/info/rfc694 | |
| RFC0695;;Krilanovich, M.;Official change in Host-Host Protocol;;;;;RFC 695;DOI 10.17487/RFC0695;July;https://www.rfc-editor.org/info/rfc695 | |
| RFC0696;;Cerf, V.;Comments on the IMP/Host and Host/IMP Protocol changes;;;;;RFC 696;DOI 10.17487/RFC0696;July;https://www.rfc-editor.org/info/rfc696 | |
| RFC0697;;Lieb, J.;CWD command of FTP;;;;;RFC 697;DOI 10.17487/RFC0697;July;https://www.rfc-editor.org/info/rfc697 | |
| RFC0698;RFC5198;Mock, T.;Telnet extended ASCII option;;;;;RFC 698;DOI 10.17487/RFC0698;July;https://www.rfc-editor.org/info/rfc698 | |
| RFC0699;;Postel, J. and J. Vernon;Request For Comments summary notes: 600-699;;;;;RFC 699;DOI 10.17487/RFC0699;November;https://www.rfc-editor.org/info/rfc699 | |
| RFC0700;;Mader, E., Plummer, W., and R. Tomlinson;Protocol experiment;;;;;RFC 700;DOI 10.17487/RFC0700;August;https://www.rfc-editor.org/info/rfc700 | |
| RFC0701;;Dodds, D.;August, 1974, survey of New-Protocol Telnet servers;;;;;RFC 701;DOI 10.17487/RFC0701;August;https://www.rfc-editor.org/info/rfc701 | |
| RFC0702;;Dodds, D.;September, 1974, survey of New-Protocol Telnet servers;;;;;RFC 702;DOI 10.17487/RFC0702;September;https://www.rfc-editor.org/info/rfc702 | |
| RFC0703;;Dodds, D.;July, 1975, survey of New-Protocol Telnet Servers;;;;;RFC 703;DOI 10.17487/RFC0703;July;https://www.rfc-editor.org/info/rfc703 | |
| RFC0704;;Santos, P.;IMP/Host and Host/IMP Protocol change;;;;;RFC 704;DOI 10.17487/RFC0704;September;https://www.rfc-editor.org/info/rfc704 | |
| RFC0705;;Bryan, R.;Front-end Protocol B6700 version;;;;;RFC 705;DOI 10.17487/RFC0705;November;https://www.rfc-editor.org/info/rfc705 | |
| RFC0706;;Postel, J.;On the junk mail problem;;;;;RFC 706;DOI 10.17487/RFC0706;November;https://www.rfc-editor.org/info/rfc706 | |
| RFC0707;;White, J.;High-level framework for network-based resource sharing;;;;;RFC 707;DOI 10.17487/RFC0707;December;https://www.rfc-editor.org/info/rfc707 | |
| RFC0708;;White, J.;Elements of a Distributed Programming System;;;;;RFC 708;DOI 10.17487/RFC0708;January;https://www.rfc-editor.org/info/rfc708 | |
| RFC0712;;Donnelley, J.;Distributed Capability Computing System (DCCS);;;;;RFC 712;DOI 10.17487/RFC0712;February;https://www.rfc-editor.org/info/rfc712 | |
| RFC0713;;Haverty, J.;MSDTP-Message Services Data Transmission Protocol;;;;;RFC 713;DOI 10.17487/RFC0713;April;https://www.rfc-editor.org/info/rfc713 | |
| RFC0714;;McKenzie, A.;Host-Host Protocol for an ARPANET-Type Network;;;;;RFC 714;DOI 10.17487/RFC0714;April;https://www.rfc-editor.org/info/rfc714 | |
| RFC0716;;Walden, D. and J. Levin;Interim Revision to Appendix F of BBN 1822;;;;;RFC 716;DOI 10.17487/RFC0716;May;https://www.rfc-editor.org/info/rfc716 | |
| RFC0717;;Postel, J.;Assigned Network Numbers;;;;;RFC 717;DOI 10.17487/RFC0717;July;https://www.rfc-editor.org/info/rfc717 | |
| RFC0718;;Postel, J.;Comments on RCTE from the Tenex Implementation Experience;;;;;RFC 718;DOI 10.17487/RFC0718;June;https://www.rfc-editor.org/info/rfc718 | |
| RFC0719;;Postel, J.;Discussion on RCTE;;;;;RFC 719;DOI 10.17487/RFC0719;July;https://www.rfc-editor.org/info/rfc719 | |
| RFC0720;;Crocker, D.;Address Specification Syntax for Network Mail;;;;;RFC 720;DOI 10.17487/RFC0720;August;https://www.rfc-editor.org/info/rfc720 | |
| RFC0721;RFC7805;Garlick, L.;Out-of-Band Control Signals in a Host-to-Host Protocol;;;;;RFC 721;DOI 10.17487/RFC0721;September;https://www.rfc-editor.org/info/rfc721 | |
| RFC0722;;Haverty, J.;Thoughts on Interactions in Distributed Services;;;;;RFC 722;DOI 10.17487/RFC0722;September;https://www.rfc-editor.org/info/rfc722 | |
| RFC0724;RFC0733;Crocker, D., Pogran, K., Vittal, J., and D. Henderson;Proposed official standard for the format of ARPA Network messages;;;;;RFC 724;DOI 10.17487/RFC0724;May;https://www.rfc-editor.org/info/rfc724 | |
| RFC0725;;Day, J. and G. Grossman;RJE protocol for a resource sharing network;;;;;RFC 725;DOI 10.17487/RFC0725;March;https://www.rfc-editor.org/info/rfc725 | |
| RFC0726;;Postel, J. and D. Crocker;Remote Controlled Transmission and Echoing Telnet option;;;;;RFC 726;DOI 10.17487/RFC0726;March;https://www.rfc-editor.org/info/rfc726 | |
| RFC0727;;Crispin, M.;Telnet logout option;;;;;RFC 727;DOI 10.17487/RFC0727;April;https://www.rfc-editor.org/info/rfc727 | |
| RFC0728;;Day, J.;Minor pitfall in the Telnet Protocol;;;;;RFC 728;DOI 10.17487/RFC0728;April;https://www.rfc-editor.org/info/rfc728 | |
| RFC0729;RFC0735;Crocker, D.;Telnet byte macro option;;;;;RFC 729;DOI 10.17487/RFC0729;May;https://www.rfc-editor.org/info/rfc729 | |
| RFC0730;;Postel, J.;Extensible field addressing;;;;;RFC 730;DOI 10.17487/RFC0730;May;https://www.rfc-editor.org/info/rfc730 | |
| RFC0731;RFC0732;Day, J.;Telnet Data Entry Terminal option;;;;;RFC 731;DOI 10.17487/RFC0731;June;https://www.rfc-editor.org/info/rfc731 | |
| RFC0732;;Day, J.;Telnet Data Entry Terminal option;;;;;RFC 732;DOI 10.17487/RFC0732;September;https://www.rfc-editor.org/info/rfc732 | |
| RFC0733;RFC0822;Crocker, D., Vittal, J., Pogran, K., and D. Henderson;Standard for the format of ARPA network text messages;;;;;RFC 733;DOI 10.17487/RFC0733;November;https://www.rfc-editor.org/info/rfc733 | |
| RFC0734;;Crispin, M.;SUPDUP Protocol;;;;;RFC 734;DOI 10.17487/RFC0734;October;https://www.rfc-editor.org/info/rfc734 | |
| RFC0735;;Crocker, D. and R. Gumpertz;Revised Telnet byte macro option;;;;;RFC 735;DOI 10.17487/RFC0735;November;https://www.rfc-editor.org/info/rfc735 | |
| RFC0736;;Crispin, M.;Telnet SUPDUP option;;;;;RFC 736;DOI 10.17487/RFC0736;October;https://www.rfc-editor.org/info/rfc736 | |
| RFC0737;;Harrenstien, K.;FTP extension: XSEN;;;;;RFC 737;DOI 10.17487/RFC0737;October;https://www.rfc-editor.org/info/rfc737 | |
| RFC0738;;Harrenstien, K.;Time server;;;;;RFC 738;DOI 10.17487/RFC0738;October;https://www.rfc-editor.org/info/rfc738 | |
| RFC0739;RFC0750;Postel, J.;Assigned numbers;;;;;RFC 739;DOI 10.17487/RFC0739;November;https://www.rfc-editor.org/info/rfc739 | |
| RFC0740;;Braden, R.;NETRJS Protocol;;;;;RFC 740;DOI 10.17487/RFC0740;November;https://www.rfc-editor.org/info/rfc740 | |
| RFC0741;;Cohen, D.;Specifications for the Network Voice Protocol (NVP);;;;;RFC 741;DOI 10.17487/RFC0741;November;https://www.rfc-editor.org/info/rfc741 | |
| RFC0742;RFC1288, RFC1196, RFC1194;Harrenstien, K.;NAME/FINGER Protocol;;;;;RFC 742;DOI 10.17487/RFC0742;December;https://www.rfc-editor.org/info/rfc742 | |
| RFC0743;;Harrenstien, K.;FTP extension: XRSQ/XRCP;;;;;RFC 743;DOI 10.17487/RFC0743;December;https://www.rfc-editor.org/info/rfc743 | |
| RFC0744;;Sattley, J.;MARS - a Message Archiving and Retrieval Service;;;;;RFC 744;DOI 10.17487/RFC0744;January;https://www.rfc-editor.org/info/rfc744 | |
| RFC0745;;Beeler, M.;JANUS interface specifications;;;;;RFC 745;DOI 10.17487/RFC0745;March;https://www.rfc-editor.org/info/rfc745 | |
| RFC0746;;Stallman, R.;SUPDUP graphics extension;;;;;RFC 746;DOI 10.17487/RFC0746;March;https://www.rfc-editor.org/info/rfc746 | |
| RFC0747;;Crispin, M.;Recent extensions to the SUPDUP Protocol;;;;;RFC 747;DOI 10.17487/RFC0747;March;https://www.rfc-editor.org/info/rfc747 | |
| RFC0748;;Crispin, M.;Telnet randomly-lose option;;;;;RFC 748;DOI 10.17487/RFC0748;April;https://www.rfc-editor.org/info/rfc748 | |
| RFC0749;;Greenberg, B.;Telnet SUPDUP-Output option;;;;;RFC 749;DOI 10.17487/RFC0749;September;https://www.rfc-editor.org/info/rfc749 | |
| RFC0750;RFC0755;Postel, J.;Assigned numbers;;;;;RFC 750;DOI 10.17487/RFC0750;September;https://www.rfc-editor.org/info/rfc750 | |
| RFC0751;;Lebling, P.;Survey of FTP mail and MLFL;;;;;RFC 751;DOI 10.17487/RFC0751;December;https://www.rfc-editor.org/info/rfc751 | |
| RFC0752;;Crispin, M.;Universal host table;;;;;RFC 752;DOI 10.17487/RFC0752;January;https://www.rfc-editor.org/info/rfc752 | |
| RFC0753;;Postel, J.;Internet Message Protocol;;;;;RFC 753;DOI 10.17487/RFC0753;March;https://www.rfc-editor.org/info/rfc753 | |
| RFC0754;;Postel, J.;Out-of-net host addresses for mail;;;;;RFC 754;DOI 10.17487/RFC0754;April;https://www.rfc-editor.org/info/rfc754 | |
| RFC0755;RFC0758;Postel, J.;Assigned numbers;;;;;RFC 755;DOI 10.17487/RFC0755;May;https://www.rfc-editor.org/info/rfc755 | |
| RFC0756;;Pickens, J., Feinler, E., and J. Mathis;NIC name server - a datagram-based information utility;;;;;RFC 756;DOI 10.17487/RFC0756;July;https://www.rfc-editor.org/info/rfc756 | |
| RFC0757;;Deutsch, D.;Suggested solution to the naming, addressing, and delivery problem for ARPANET message systems;;;;;RFC 757;DOI 10.17487/RFC0757;September;https://www.rfc-editor.org/info/rfc757 | |
| RFC0758;RFC0762;Postel, J.;Assigned numbers;;;;;RFC 758;DOI 10.17487/RFC0758;August;https://www.rfc-editor.org/info/rfc758 | |
| RFC0759;;Postel, J.;Internet Message Protocol;;;;;RFC 759;DOI 10.17487/RFC0759;August;https://www.rfc-editor.org/info/rfc759 | |
| RFC0760;RFC0791;Postel, J.;DoD standard Internet Protocol;;;;;RFC 760;DOI 10.17487/RFC0760;January;https://www.rfc-editor.org/info/rfc760 | |
| RFC0761;RFC0793, RFC7805;Postel, J.;DoD standard Transmission Control Protocol;;;;;RFC 761;DOI 10.17487/RFC0761;January;https://www.rfc-editor.org/info/rfc761 | |
| RFC0762;RFC0770;Postel, J.;Assigned numbers;;;;;RFC 762;DOI 10.17487/RFC0762;January;https://www.rfc-editor.org/info/rfc762 | |
| RFC0763;;Abrams, M.;Role mailboxes;;;;;RFC 763;DOI 10.17487/RFC0763;May;https://www.rfc-editor.org/info/rfc763 | |
| RFC0764;RFC0854;Postel, J.;Telnet Protocol specification;;;;;RFC 764;DOI 10.17487/RFC0764;June;https://www.rfc-editor.org/info/rfc764 | |
| RFC0765;RFC0959;Postel, J.;File Transfer Protocol specification;;;;;RFC 765;DOI 10.17487/RFC0765;June;https://www.rfc-editor.org/info/rfc765 | |
| RFC0766;RFC0774;Postel, J.;Internet Protocol Handbook: Table of contents;;;;;RFC 766;DOI 10.17487/RFC0766;July;https://www.rfc-editor.org/info/rfc766 | |
| RFC0767;;Postel, J.;Structured format for transmission of multi-media documents;;;;;RFC 767;DOI 10.17487/RFC0767;August;https://www.rfc-editor.org/info/rfc767 | |
| RFC0768;;Postel, J.;User Datagram Protocol;;;;STD 6;RFC 768;DOI 10.17487/RFC0768;August;https://www.rfc-editor.org/info/rfc768 | |
| RFC0769;;Postel, J.;Rapicom 450 facsimile file format;;;;;RFC 769;DOI 10.17487/RFC0769;September;https://www.rfc-editor.org/info/rfc769 | |
| RFC0770;RFC0776;Postel, J.;Assigned numbers;;;;;RFC 770;DOI 10.17487/RFC0770;September;https://www.rfc-editor.org/info/rfc770 | |
| RFC0771;;Cerf, V. and J. Postel;Mail transition plan;;;;;RFC 771;DOI 10.17487/RFC0771;September;https://www.rfc-editor.org/info/rfc771 | |
| RFC0772;RFC0780;Sluizer, S. and J. Postel;Mail Transfer Protocol;;;;;RFC 772;DOI 10.17487/RFC0772;September;https://www.rfc-editor.org/info/rfc772 | |
| RFC0773;;Cerf, V.;Comments on NCP/TCP mail service transition strategy;;;;;RFC 773;DOI 10.17487/RFC0773;October;https://www.rfc-editor.org/info/rfc773 | |
| RFC0774;;Postel, J.;Internet Protocol Handbook: Table of contents;;;;;RFC 774;DOI 10.17487/RFC0774;October;https://www.rfc-editor.org/info/rfc774 | |
| RFC0775;;Mankins, D., Franklin, D., and A. Owen;Directory oriented FTP commands;;;;;RFC 775;DOI 10.17487/RFC0775;December;https://www.rfc-editor.org/info/rfc775 | |
| RFC0776;RFC0790;Postel, J.;Assigned numbers;;;;;RFC 776;DOI 10.17487/RFC0776;January;https://www.rfc-editor.org/info/rfc776 | |
| RFC0777;RFC0792;Postel, J.;Internet Control Message Protocol;;;;;RFC 777;DOI 10.17487/RFC0777;April;https://www.rfc-editor.org/info/rfc777 | |
| RFC0778;;Mills, D.;DCNET Internet Clock Service;;;;;RFC 778;DOI 10.17487/RFC0778;April;https://www.rfc-editor.org/info/rfc778 | |
| RFC0779;;Killian, E.;Telnet send-location option;;;;;RFC 779;DOI 10.17487/RFC0779;April;https://www.rfc-editor.org/info/rfc779 | |
| RFC0780;RFC0788;Sluizer, S. and J. Postel;Mail Transfer Protocol;;;;;RFC 780;DOI 10.17487/RFC0780;May;https://www.rfc-editor.org/info/rfc780 | |
| RFC0781;;Su, Z.;Specification of the Internet Protocol (IP) timestamp option;;;;;RFC 781;DOI 10.17487/RFC0781;May;https://www.rfc-editor.org/info/rfc781 | |
| RFC0782;;Nabielsky, J. and A. Skelton;Virtual Terminal management model;;;;;RFC 782;DOI 10.17487/RFC0782;January;https://www.rfc-editor.org/info/rfc782 | |
| RFC0783;RFC1350;Sollins, K.;TFTP Protocol (revision 2);;;;;RFC 783;DOI 10.17487/RFC0783;June;https://www.rfc-editor.org/info/rfc783 | |
| RFC0784;;Sluizer, S. and J. Postel;Mail Transfer Protocol: ISI TOPS20 implementation;;;;;RFC 784;DOI 10.17487/RFC0784;July;https://www.rfc-editor.org/info/rfc784 | |
| RFC0785;;Sluizer, S. and J. Postel;Mail Transfer Protocol: ISI TOPS20 file definitions;;;;;RFC 785;DOI 10.17487/RFC0785;July;https://www.rfc-editor.org/info/rfc785 | |
| RFC0786;;Sluizer, S. and J. Postel;Mail Transfer Protocol: ISI TOPS20 MTP-NIMAIL interface;;;;;RFC 786;DOI 10.17487/RFC0786;July;https://www.rfc-editor.org/info/rfc786 | |
| RFC0787;;Chapin, A.;Connectionless data transmission survey/tutorial;;;;;RFC 787;DOI 10.17487/RFC0787;July;https://www.rfc-editor.org/info/rfc787 | |
| RFC0788;RFC0821;Postel, J.;Simple Mail Transfer Protocol;;;;;RFC 788;DOI 10.17487/RFC0788;November;https://www.rfc-editor.org/info/rfc788 | |
| RFC0789;;Rosen, E.;Vulnerabilities of network control protocols: An example;;;;;RFC 789;DOI 10.17487/RFC0789;July;https://www.rfc-editor.org/info/rfc789 | |
| RFC0790;RFC0820;Postel, J.;Assigned numbers;;;;;RFC 790;DOI 10.17487/RFC0790;September;https://www.rfc-editor.org/info/rfc790 | |
| RFC0791;;Postel, J.;Internet Protocol;;;;STD 5;RFC 791;DOI 10.17487/RFC0791;September;https://www.rfc-editor.org/info/rfc791 | |
| RFC0792;;Postel, J.;Internet Control Message Protocol;;;;STD 5;RFC 792;DOI 10.17487/RFC0792;September;https://www.rfc-editor.org/info/rfc792 | |
| RFC0793;;Postel, J.;Transmission Control Protocol;;;;STD 7;RFC 793;DOI 10.17487/RFC0793;September;https://www.rfc-editor.org/info/rfc793 | |
| RFC0794;;Cerf, V.;Pre-emption;;;;;RFC 794;DOI 10.17487/RFC0794;September;https://www.rfc-editor.org/info/rfc794 | |
| RFC0795;;Postel, J.;Service mappings;;;;;RFC 795;DOI 10.17487/RFC0795;September;https://www.rfc-editor.org/info/rfc795 | |
| RFC0796;;Postel, J.;Address mappings;;;;;RFC 796;DOI 10.17487/RFC0796;September;https://www.rfc-editor.org/info/rfc796 | |
| RFC0797;;Katz, A.;Format for Bitmap files;;;;;RFC 797;DOI 10.17487/RFC0797;September;https://www.rfc-editor.org/info/rfc797 | |
| RFC0798;;Katz, A.;Decoding facsimile data from the Rapicom 450;;;;;RFC 798;DOI 10.17487/RFC0798;September;https://www.rfc-editor.org/info/rfc798 | |
| RFC0799;;Mills, D.;Internet name domains;;;;;RFC 799;DOI 10.17487/RFC0799;September;https://www.rfc-editor.org/info/rfc799 | |
| RFC0800;;Postel, J. and J. Vernon;Request For Comments summary notes: 700-799;;;;;RFC 800;DOI 10.17487/RFC0800;November;https://www.rfc-editor.org/info/rfc800 | |
| RFC0801;;Postel, J.;NCP/TCP transition plan;;;;;RFC 801;DOI 10.17487/RFC0801;November;https://www.rfc-editor.org/info/rfc801 | |
| RFC0802;RFC0851;Malis, A.;ARPANET 1822L Host Access Protocol;;;;;RFC 802;DOI 10.17487/RFC0802;November;https://www.rfc-editor.org/info/rfc802 | |
| RFC0803;;Agarwal, A., O'Connor, M., and D. Mills;Dacom 450/500 facsimile data transcoding;;;;;RFC 803;DOI 10.17487/RFC0803;November;https://www.rfc-editor.org/info/rfc803 | |
| RFC0804;;International Telegraph and Telephone Consultative Committee of the International Telecommunication Union;CCITT draft recommendation T.4;;;;;RFC 804;DOI 10.17487/RFC0804;January;https://www.rfc-editor.org/info/rfc804 | |
| RFC0805;;Postel, J.;Computer mail meeting notes;;;;;RFC 805;DOI 10.17487/RFC0805;February;https://www.rfc-editor.org/info/rfc805 | |
| RFC0806;RFC0841;National Bureau of Standards;Proposed Federal Information Processing Standard: Specification for message format for computer based message systems;;;;;RFC 806;DOI 10.17487/RFC0806;September;https://www.rfc-editor.org/info/rfc806 | |
| RFC0807;;Postel, J.;Multimedia mail meeting notes;;;;;RFC 807;DOI 10.17487/RFC0807;February;https://www.rfc-editor.org/info/rfc807 | |
| RFC0808;;Postel, J.;Summary of computer mail services meeting held at BBN on 10 January 1979;;;;;RFC 808;DOI 10.17487/RFC0808;March;https://www.rfc-editor.org/info/rfc808 | |
| RFC0809;;Chang, T.;UCL facsimile system;;;;;RFC 809;DOI 10.17487/RFC0809;February;https://www.rfc-editor.org/info/rfc809 | |
| RFC0810;RFC0952;Feinler, E., Harrenstien, K., Su, Z., and V. White;DoD Internet host table specification;;;;;RFC 810;DOI 10.17487/RFC0810;March;https://www.rfc-editor.org/info/rfc810 | |
| RFC0811;RFC0953;Harrenstien, K., White, V., and E. Feinler;Hostnames Server;;;;;RFC 811;DOI 10.17487/RFC0811;March;https://www.rfc-editor.org/info/rfc811 | |
| RFC0812;RFC0954, RFC3912;Harrenstien, K. and V. White;NICNAME/WHOIS;;;;;RFC 812;DOI 10.17487/RFC0812;March;https://www.rfc-editor.org/info/rfc812 | |
| RFC0813;RFC7805;Clark, D.;Window and Acknowledgement Strategy in TCP;;;;;RFC 813;DOI 10.17487/RFC0813;July;https://www.rfc-editor.org/info/rfc813 | |
| RFC0814;;Clark, D.;Name, addresses, ports, and routes;;;;;RFC 814;DOI 10.17487/RFC0814;July;https://www.rfc-editor.org/info/rfc814 | |
| RFC0815;;Clark, D.;IP datagram reassembly algorithms;;;;;RFC 815;DOI 10.17487/RFC0815;July;https://www.rfc-editor.org/info/rfc815 | |
| RFC0816;RFC7805;Clark, D.;Fault isolation and recovery;;;;;RFC 816;DOI 10.17487/RFC0816;July;https://www.rfc-editor.org/info/rfc816 | |
| RFC0817;;Clark, D.;Modularity and efficiency in protocol implementation;;;;;RFC 817;DOI 10.17487/RFC0817;July;https://www.rfc-editor.org/info/rfc817 | |
| RFC0818;;Postel, J.;Remote User Telnet service;;;;;RFC 818;DOI 10.17487/RFC0818;November;https://www.rfc-editor.org/info/rfc818 | |
| RFC0819;;Su, Z. and J. Postel;The Domain Naming Convention for Internet User Applications;;;;;RFC 819;DOI 10.17487/RFC0819;August;https://www.rfc-editor.org/info/rfc819 | |
| RFC0820;RFC0870;Postel, J.;Assigned numbers;;;;;RFC 820;DOI 10.17487/RFC0820;August;https://www.rfc-editor.org/info/rfc820 | |
| RFC0821;RFC2821;Postel, J.;Simple Mail Transfer Protocol;;;;STD 10;RFC 821;DOI 10.17487/RFC0821;August;https://www.rfc-editor.org/info/rfc821 | |
| RFC0822;RFC2822;Crocker, D.;STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES;;;;STD 11;RFC 822;DOI 10.17487/RFC0822;August;https://www.rfc-editor.org/info/rfc822 | |
| RFC0823;;Hinden, R. and A. Sheltzer;DARPA Internet gateway;;;;;RFC 823;DOI 10.17487/RFC0823;September;https://www.rfc-editor.org/info/rfc823 | |
| RFC0824;;MacGregor, W. and D. Tappan;CRONUS Virtual Local Network;;;;;RFC 824;DOI 10.17487/RFC0824;August;https://www.rfc-editor.org/info/rfc824 | |
| RFC0825;RFC1111, RFC1543, RFC2223;Postel, J.;Request for comments on Requests For Comments;;;;;RFC 825;DOI 10.17487/RFC0825;November;https://www.rfc-editor.org/info/rfc825 | |
| RFC0826;;Plummer, D.;An Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware;;;;STD 37;RFC 826;DOI 10.17487/RFC0826;November;https://www.rfc-editor.org/info/rfc826 | |
| RFC0827;;Rosen, E.;Exterior Gateway Protocol (EGP);;;;;RFC 827;DOI 10.17487/RFC0827;October;https://www.rfc-editor.org/info/rfc827 | |
| RFC0828;;Owen, K.;Data communications: IFIP's international "network" of experts;;;;;RFC 828;DOI 10.17487/RFC0828;August;https://www.rfc-editor.org/info/rfc828 | |
| RFC0829;;Cerf, V.;Packet satellite technology reference sources;;;;;RFC 829;DOI 10.17487/RFC0829;November;https://www.rfc-editor.org/info/rfc829 | |
| RFC0830;;Su, Z.;Distributed system for Internet name service;;;;;RFC 830;DOI 10.17487/RFC0830;October;https://www.rfc-editor.org/info/rfc830 | |
| RFC0831;;Braden, R.;Backup access to the European side of SATNET;;;;;RFC 831;DOI 10.17487/RFC0831;December;https://www.rfc-editor.org/info/rfc831 | |
| RFC0832;RFC0833;Smallberg, D.;Who talks TCP?;;;;;RFC 832;DOI 10.17487/RFC0832;December;https://www.rfc-editor.org/info/rfc832 | |
| RFC0833;RFC0834;Smallberg, D.;Who talks TCP?;;;;;RFC 833;DOI 10.17487/RFC0833;December;https://www.rfc-editor.org/info/rfc833 | |
| RFC0834;RFC0835;Smallberg, D.;Who talks TCP?;;;;;RFC 834;DOI 10.17487/RFC0834;December;https://www.rfc-editor.org/info/rfc834 | |
| RFC0835;RFC0836;Smallberg, D.;Who talks TCP?;;;;;RFC 835;DOI 10.17487/RFC0835;December;https://www.rfc-editor.org/info/rfc835 | |
| RFC0836;RFC0837;Smallberg, D.;Who talks TCP?;;;;;RFC 836;DOI 10.17487/RFC0836;January;https://www.rfc-editor.org/info/rfc836 | |
| RFC0837;RFC0838;Smallberg, D.;Who talks TCP?;;;;;RFC 837;DOI 10.17487/RFC0837;January;https://www.rfc-editor.org/info/rfc837 | |
| RFC0838;RFC0839;Smallberg, D.;Who talks TCP?;;;;;RFC 838;DOI 10.17487/RFC0838;January;https://www.rfc-editor.org/info/rfc838 | |
| RFC0839;RFC0842;Smallberg, D.;Who talks TCP?;;;;;RFC 839;DOI 10.17487/RFC0839;January;https://www.rfc-editor.org/info/rfc839 | |
| RFC0840;RFC0880;Postel, J.;Official protocols;;;;;RFC 840;DOI 10.17487/RFC0840;April;https://www.rfc-editor.org/info/rfc840 | |
| RFC0841;;National Bureau of Standards;Specification for message format for Computer Based Message Systems;;;;;RFC 841;DOI 10.17487/RFC0841;January;https://www.rfc-editor.org/info/rfc841 | |
| RFC0842;RFC0843;Smallberg, D.;Who talks TCP? - survey of 1 February 83;;;;;RFC 842;DOI 10.17487/RFC0842;February;https://www.rfc-editor.org/info/rfc842 | |
| RFC0843;RFC0845;Smallberg, D.;Who talks TCP? - survey of 8 February 83;;;;;RFC 843;DOI 10.17487/RFC0843;February;https://www.rfc-editor.org/info/rfc843 | |
| RFC0844;;Clements, R.;Who talks ICMP, too? - Survey of 18 February 1983;;;;;RFC 844;DOI 10.17487/RFC0844;February;https://www.rfc-editor.org/info/rfc844 | |
| RFC0845;RFC0846;Smallberg, D.;Who talks TCP? - survey of 15 February 1983;;;;;RFC 845;DOI 10.17487/RFC0845;February;https://www.rfc-editor.org/info/rfc845 | |
| RFC0846;RFC0847;Smallberg, D.;Who talks TCP? - survey of 22 February 1983;;;;;RFC 846;DOI 10.17487/RFC0846;February;https://www.rfc-editor.org/info/rfc846 | |
| RFC0847;;Westine, A., Smallberg, D., and J. Postel;Summary of Smallberg surveys;;;;;RFC 847;DOI 10.17487/RFC0847;February;https://www.rfc-editor.org/info/rfc847 | |
| RFC0848;;Smallberg, D.;Who provides the "little" TCP services?;;;;;RFC 848;DOI 10.17487/RFC0848;March;https://www.rfc-editor.org/info/rfc848 | |
| RFC0849;;Crispin, M.;Suggestions for improved host table distribution;;;;;RFC 849;DOI 10.17487/RFC0849;May;https://www.rfc-editor.org/info/rfc849 | |
| RFC0850;RFC1036;Horton, M.;Standard for interchange of USENET messages;;;;;RFC 850;DOI 10.17487/RFC0850;June;https://www.rfc-editor.org/info/rfc850 | |
| RFC0851;RFC0878;Malis, A.;ARPANET 1822L Host Access Protocol;;;;;RFC 851;DOI 10.17487/RFC0851;April;https://www.rfc-editor.org/info/rfc851 | |
| RFC0852;;Malis, A.;ARPANET short blocking feature;;;;;RFC 852;DOI 10.17487/RFC0852;April;https://www.rfc-editor.org/info/rfc852 | |
| RFC0854;;Postel, J. and J. Reynolds;Telnet Protocol Specification;;;;STD 8;RFC 854;DOI 10.17487/RFC0854;May;https://www.rfc-editor.org/info/rfc854 | |
| RFC0855;;Postel, J. and J. Reynolds;Telnet Option Specifications;;;;STD 8;RFC 855;DOI 10.17487/RFC0855;May;https://www.rfc-editor.org/info/rfc855 | |
| RFC0856;;Postel, J. and J. Reynolds;Telnet Binary Transmission;;;;STD 27;RFC 856;DOI 10.17487/RFC0856;May;https://www.rfc-editor.org/info/rfc856 | |
| RFC0857;;Postel, J. and J. Reynolds;Telnet Echo Option;;;;STD 28;RFC 857;DOI 10.17487/RFC0857;May;https://www.rfc-editor.org/info/rfc857 | |
| RFC0858;;Postel, J. and J. Reynolds;Telnet Suppress Go Ahead Option;;;;STD 29;RFC 858;DOI 10.17487/RFC0858;May;https://www.rfc-editor.org/info/rfc858 | |
| RFC0859;;Postel, J. and J. Reynolds;Telnet Status Option;;;;STD 30;RFC 859;DOI 10.17487/RFC0859;May;https://www.rfc-editor.org/info/rfc859 | |
| RFC0860;;Postel, J. and J. Reynolds;Telnet Timing Mark Option;;;;STD 31;RFC 860;DOI 10.17487/RFC0860;May;https://www.rfc-editor.org/info/rfc860 | |
| RFC0861;;Postel, J. and J. Reynolds;Telnet Extended Options: List Option;;;;STD 32;RFC 861;DOI 10.17487/RFC0861;May;https://www.rfc-editor.org/info/rfc861 | |
| RFC0862;;Postel, J.;Echo Protocol;;;;STD 20;RFC 862;DOI 10.17487/RFC0862;May;https://www.rfc-editor.org/info/rfc862 | |
| RFC0863;;Postel, J.;Discard Protocol;;;;STD 21;RFC 863;DOI 10.17487/RFC0863;May;https://www.rfc-editor.org/info/rfc863 | |
| RFC0864;;Postel, J.;Character Generator Protocol;;;;STD 22;RFC 864;DOI 10.17487/RFC0864;May;https://www.rfc-editor.org/info/rfc864 | |
| RFC0865;;Postel, J.;Quote of the Day Protocol;;;;STD 23;RFC 865;DOI 10.17487/RFC0865;May;https://www.rfc-editor.org/info/rfc865 | |
| RFC0866;;Postel, J.;Active users;;;;STD 24;RFC 866;DOI 10.17487/RFC0866;May;https://www.rfc-editor.org/info/rfc866 | |
| RFC0867;;Postel, J.;Daytime Protocol;;;;STD 25;RFC 867;DOI 10.17487/RFC0867;May;https://www.rfc-editor.org/info/rfc867 | |
| RFC0868;;Postel, J. and K. Harrenstien;Time Protocol;;;;STD 26;RFC 868;DOI 10.17487/RFC0868;May;https://www.rfc-editor.org/info/rfc868 | |
| RFC0869;;Hinden, R.;Host Monitoring Protocol;;;;;RFC 869;DOI 10.17487/RFC0869;December;https://www.rfc-editor.org/info/rfc869 | |
| RFC0870;RFC0900;Reynolds, J. and J. Postel;Assigned numbers;;;;;RFC 870;DOI 10.17487/RFC0870;October;https://www.rfc-editor.org/info/rfc870 | |
| RFC0871;;Padlipsky, M.;Perspective on the ARPANET reference model;;;;;RFC 871;DOI 10.17487/RFC0871;September;https://www.rfc-editor.org/info/rfc871 | |
| RFC0872;;Padlipsky, M.;TCP-on-a-LAN;;;;;RFC 872;DOI 10.17487/RFC0872;September;https://www.rfc-editor.org/info/rfc872 | |
| RFC0873;;Padlipsky, M.;Illusion of vendor support;;;;;RFC 873;DOI 10.17487/RFC0873;September;https://www.rfc-editor.org/info/rfc873 | |
| RFC0874;;Padlipsky, M.;Critique of X.25;;;;;RFC 874;DOI 10.17487/RFC0874;September;https://www.rfc-editor.org/info/rfc874 | |
| RFC0875;;Padlipsky, M.;Gateways, architectures, and heffalumps;;;;;RFC 875;DOI 10.17487/RFC0875;September;https://www.rfc-editor.org/info/rfc875 | |
| RFC0876;;Smallberg, D.;Survey of SMTP implementations;;;;;RFC 876;DOI 10.17487/RFC0876;September;https://www.rfc-editor.org/info/rfc876 | |
| RFC0877;RFC1356;Korb, J.;Standard for the transmission of IP datagrams over public data networks;;;;;RFC 877;DOI 10.17487/RFC0877;September;https://www.rfc-editor.org/info/rfc877 | |
| RFC0878;;Malis, A.;ARPANET 1822L Host Access Protocol;;;;;RFC 878;DOI 10.17487/RFC0878;December;https://www.rfc-editor.org/info/rfc878 | |
| RFC0879;RFC7805;Postel, J.;The TCP Maximum Segment Size and Related Topics;;;;;RFC 879;DOI 10.17487/RFC0879;November;https://www.rfc-editor.org/info/rfc879 | |
| RFC0880;RFC0901;Reynolds, J. and J. Postel;Official protocols;;;;;RFC 880;DOI 10.17487/RFC0880;October;https://www.rfc-editor.org/info/rfc880 | |
| RFC0881;;Postel, J.;Domain names plan and schedule;;;;;RFC 881;DOI 10.17487/RFC0881;November;https://www.rfc-editor.org/info/rfc881 | |
| RFC0882;RFC1034, RFC1035;Mockapetris, P.;Domain names: Concepts and facilities;;;;;RFC 882;DOI 10.17487/RFC0882;November;https://www.rfc-editor.org/info/rfc882 | |
| RFC0883;RFC1034, RFC1035;Mockapetris, P.;Domain names: Implementation specification;;;;;RFC 883;DOI 10.17487/RFC0883;November;https://www.rfc-editor.org/info/rfc883 | |
| RFC0884;RFC0930;Solomon, M. and E. Wimmers;Telnet terminal type option;;;;;RFC 884;DOI 10.17487/RFC0884;December;https://www.rfc-editor.org/info/rfc884 | |
| RFC0885;;Postel, J.;Telnet end of record option;;;;;RFC 885;DOI 10.17487/RFC0885;December;https://www.rfc-editor.org/info/rfc885 | |
| RFC0886;;Rose, M.;Proposed standard for message header munging;;;;;RFC 886;DOI 10.17487/RFC0886;December;https://www.rfc-editor.org/info/rfc886 | |
| RFC0887;;Accetta, M.;Resource Location Protocol;;;;;RFC 887;DOI 10.17487/RFC0887;December;https://www.rfc-editor.org/info/rfc887 | |
| RFC0888;;Seamonson, L. and E. Rosen;"STUB" Exterior Gateway Protocol;;;;;RFC 888;DOI 10.17487/RFC0888;January;https://www.rfc-editor.org/info/rfc888 | |
| RFC0889;;Mills, D.;Internet Delay Experiments;;;;;RFC 889;DOI 10.17487/RFC0889;December;https://www.rfc-editor.org/info/rfc889 | |
| RFC0890;;Postel, J.;Exterior Gateway Protocol implementation schedule;;;;;RFC 890;DOI 10.17487/RFC0890;February;https://www.rfc-editor.org/info/rfc890 | |
| RFC0891;;Mills, D.;DCN Local-Network Protocols;;;;STD 44;RFC 891;DOI 10.17487/RFC0891;December;https://www.rfc-editor.org/info/rfc891 | |
| RFC0892;RFC0905;International Organization for Standardization;ISO Transport Protocol specification;;;;;RFC 892;DOI 10.17487/RFC0892;December;https://www.rfc-editor.org/info/rfc892 | |
| RFC0893;;Leffler, S. and M. Karels;Trailer encapsulations;;;;;RFC 893;DOI 10.17487/RFC0893;April;https://www.rfc-editor.org/info/rfc893 | |
| RFC0894;;Hornig, C.;A Standard for the Transmission of IP Datagrams over Ethernet Networks;;;;STD 41;RFC 894;DOI 10.17487/RFC0894;April;https://www.rfc-editor.org/info/rfc894 | |
| RFC0895;;Postel, J.;Standard for the transmission of IP datagrams over experimental Ethernet networks;;;;STD 42;RFC 895;DOI 10.17487/RFC0895;April;https://www.rfc-editor.org/info/rfc895 | |
| RFC0896;RFC7805;Nagle, J.;Congestion Control in IP/TCP Internetworks;;;;;RFC 896;DOI 10.17487/RFC0896;January;https://www.rfc-editor.org/info/rfc896 | |
| RFC0897;;Postel, J.;Domain name system implementation schedule;;;;;RFC 897;DOI 10.17487/RFC0897;February;https://www.rfc-editor.org/info/rfc897 | |
| RFC0898;;Hinden, R., Postel, J., Muuss, M., and J. Reynolds;Gateway special interest group meeting notes;;;;;RFC 898;DOI 10.17487/RFC0898;April;https://www.rfc-editor.org/info/rfc898 | |
| RFC0899;;Postel, J. and A. Westine;Request For Comments summary notes: 800-899;;;;;RFC 899;DOI 10.17487/RFC0899;May;https://www.rfc-editor.org/info/rfc899 | |
| RFC0900;RFC0923;Reynolds, J. and J. Postel;Assigned Numbers;;;;;RFC 900;DOI 10.17487/RFC0900;June;https://www.rfc-editor.org/info/rfc900 | |
| RFC0901;RFC0924;Reynolds, J. and J. Postel;Official ARPA-Internet protocols;;;;;RFC 901;DOI 10.17487/RFC0901;June;https://www.rfc-editor.org/info/rfc901 | |
| RFC0902;;Reynolds, J. and J. Postel;ARPA Internet Protocol policy;;;;;RFC 902;DOI 10.17487/RFC0902;July;https://www.rfc-editor.org/info/rfc902 | |
| RFC0903;;Finlayson, R., Mann, T., Mogul, J., and M. Theimer;A Reverse Address Resolution Protocol;;;;STD 38;RFC 903;DOI 10.17487/RFC0903;June;https://www.rfc-editor.org/info/rfc903 | |
| RFC0904;;Mills, D.;Exterior Gateway Protocol formal specification;;;;;RFC 904;DOI 10.17487/RFC0904;April;https://www.rfc-editor.org/info/rfc904 | |
| RFC0905;;ISO;ISO Transport Protocol specification ISO DP 8073;;;;;RFC 905;DOI 10.17487/RFC0905;April;https://www.rfc-editor.org/info/rfc905 | |
| RFC0906;;Finlayson, R.;Bootstrap loading using TFTP;;;;;RFC 906;DOI 10.17487/RFC0906;June;https://www.rfc-editor.org/info/rfc906 | |
| RFC0907;;Bolt Beranek and Newman Laboratories;Host Access Protocol specification;;;;STD 40;RFC 907;DOI 10.17487/RFC0907;July;https://www.rfc-editor.org/info/rfc907 | |
| RFC0908;;Velten, D., Hinden, R., and J. Sax;Reliable Data Protocol;;;;;RFC 908;DOI 10.17487/RFC0908;July;https://www.rfc-editor.org/info/rfc908 | |
| RFC0909;;Welles, C. and W. Milliken;Loader Debugger Protocol;;;;;RFC 909;DOI 10.17487/RFC0909;July;https://www.rfc-editor.org/info/rfc909 | |
| RFC0910;;Forsdick, H.;Multimedia mail meeting notes;;;;;RFC 910;DOI 10.17487/RFC0910;August;https://www.rfc-editor.org/info/rfc910 | |
| RFC0911;;Kirton, P.;EGP Gateway under Berkeley UNIX 4.2;;;;;RFC 911;DOI 10.17487/RFC0911;August;https://www.rfc-editor.org/info/rfc911 | |
| RFC0912;RFC0931;St. Johns, M.;Authentication service;;;;;RFC 912;DOI 10.17487/RFC0912;September;https://www.rfc-editor.org/info/rfc912 | |
| RFC0913;;Lottor, M.;Simple File Transfer Protocol;;;;;RFC 913;DOI 10.17487/RFC0913;September;https://www.rfc-editor.org/info/rfc913 | |
| RFC0914;;Farber, D., Delp, G., and T. Conte;Thinwire protocol for connecting personal computers to the Internet;;;;;RFC 914;DOI 10.17487/RFC0914;September;https://www.rfc-editor.org/info/rfc914 | |
| RFC0915;;Elvy, M. and R. Nedved;Network mail path service;;;;;RFC 915;DOI 10.17487/RFC0915;December;https://www.rfc-editor.org/info/rfc915 | |
| RFC0916;;Finn, G.;Reliable Asynchronous Transfer Protocol (RATP);;;;;RFC 916;DOI 10.17487/RFC0916;October;https://www.rfc-editor.org/info/rfc916 | |
| RFC0917;;Mogul, J.;Internet subnets;;;;;RFC 917;DOI 10.17487/RFC0917;October;https://www.rfc-editor.org/info/rfc917 | |
| RFC0918;RFC0937;Reynolds, J.;Post Office Protocol;;;;;RFC 918;DOI 10.17487/RFC0918;October;https://www.rfc-editor.org/info/rfc918 | |
| RFC0919;;Mogul, J.;Broadcasting Internet Datagrams;;;;STD 5;RFC 919;DOI 10.17487/RFC0919;October;https://www.rfc-editor.org/info/rfc919 | |
| RFC0920;;Postel, J. and J. Reynolds;Domain requirements;;;;;RFC 920;DOI 10.17487/RFC0920;October;https://www.rfc-editor.org/info/rfc920 | |
| RFC0921;;Postel, J.;Domain name system implementation schedule - revised;;;;;RFC 921;DOI 10.17487/RFC0921;October;https://www.rfc-editor.org/info/rfc921 | |
| RFC0922;;Mogul, J.;Broadcasting Internet datagrams in the presence of subnets;;;;STD 5;RFC 922;DOI 10.17487/RFC0922;October;https://www.rfc-editor.org/info/rfc922 | |
| RFC0923;RFC0943;Reynolds, J. and J. Postel;Assigned numbers;;;;;RFC 923;DOI 10.17487/RFC0923;October;https://www.rfc-editor.org/info/rfc923 | |
| RFC0924;RFC0944;Reynolds, J. and J. Postel;Official ARPA-Internet protocols for connecting personal computers to the Internet;;;;;RFC 924;DOI 10.17487/RFC0924;October;https://www.rfc-editor.org/info/rfc924 | |
| RFC0925;;Postel, J.;Multi-LAN address resolution;;;;;RFC 925;DOI 10.17487/RFC0925;October;https://www.rfc-editor.org/info/rfc925 | |
| RFC0926;RFC0994;International Organization for Standardization;Protocol for providing the connectionless mode network services;;;;;RFC 926;DOI 10.17487/RFC0926;December;https://www.rfc-editor.org/info/rfc926 | |
| RFC0927;;Anderson, B.;TACACS user identification Telnet option;;;;;RFC 927;DOI 10.17487/RFC0927;December;https://www.rfc-editor.org/info/rfc927 | |
| RFC0928;;Padlipsky, M.;Introduction to proposed DoD standard H-FP;;;;;RFC 928;DOI 10.17487/RFC0928;December;https://www.rfc-editor.org/info/rfc928 | |
| RFC0929;;Lilienkamp, J., Mandell, R., and M. Padlipsky;Proposed Host-Front End Protocol;;;;;RFC 929;DOI 10.17487/RFC0929;December;https://www.rfc-editor.org/info/rfc929 | |
| RFC0930;RFC1091;Solomon, M. and E. Wimmers;Telnet terminal type option;;;;;RFC 930;DOI 10.17487/RFC0930;January;https://www.rfc-editor.org/info/rfc930 | |
| RFC0931;RFC1413;St. Johns, M.;Authentication server;;;;;RFC 931;DOI 10.17487/RFC0931;January;https://www.rfc-editor.org/info/rfc931 | |
| RFC0932;;Clark, D.;Subnetwork addressing scheme;;;;;RFC 932;DOI 10.17487/RFC0932;January;https://www.rfc-editor.org/info/rfc932 | |
| RFC0933;;Silverman, S.;Output marking Telnet option;;;;;RFC 933;DOI 10.17487/RFC0933;January;https://www.rfc-editor.org/info/rfc933 | |
| RFC0934;;Rose, M. and E. Stefferud;Proposed standard for message encapsulation;;;;;RFC 934;DOI 10.17487/RFC0934;January;https://www.rfc-editor.org/info/rfc934 | |
| RFC0935;;Robinson, J.;Reliable link layer protocols;;;;;RFC 935;DOI 10.17487/RFC0935;January;https://www.rfc-editor.org/info/rfc935 | |
| RFC0936;;Karels, M.;Another Internet subnet addressing scheme;;;;;RFC 936;DOI 10.17487/RFC0936;February;https://www.rfc-editor.org/info/rfc936 | |
| RFC0937;;Butler, M., Postel, J., Chase, D., Goldberger, J., and J. Reynolds;Post Office Protocol: Version 2;;;;;RFC 937;DOI 10.17487/RFC0937;February;https://www.rfc-editor.org/info/rfc937 | |
| RFC0938;;Miller, T.;Internet Reliable Transaction Protocol functional and interface specification;;;;;RFC 938;DOI 10.17487/RFC0938;February;https://www.rfc-editor.org/info/rfc938 | |
| RFC0939;;National Research Council;Executive summary of the NRC report on transport protocols for Department of Defense data networks;;;;;RFC 939;DOI 10.17487/RFC0939;February;https://www.rfc-editor.org/info/rfc939 | |
| RFC0940;;Gateway Algorithms and Data Structures Task Force;Toward an Internet standard scheme for subnetting;;;;;RFC 940;DOI 10.17487/RFC0940;April;https://www.rfc-editor.org/info/rfc940 | |
| RFC0941;;International Organization for Standardization;Addendum to the network service definition covering network layer addressing;;;;;RFC 941;DOI 10.17487/RFC0941;April;https://www.rfc-editor.org/info/rfc941 | |
| RFC0942;;National Research Council;Transport protocols for Department of Defense data networks;;;;;RFC 942;DOI 10.17487/RFC0942;February;https://www.rfc-editor.org/info/rfc942 | |
| RFC0943;RFC0960;Reynolds, J. and J. Postel;Assigned numbers;;;;;RFC 943;DOI 10.17487/RFC0943;April;https://www.rfc-editor.org/info/rfc943 | |
| RFC0944;RFC0961;Reynolds, J. and J. Postel;Official ARPA-Internet protocols;;;;;RFC 944;DOI 10.17487/RFC0944;April;https://www.rfc-editor.org/info/rfc944 | |
| RFC0945;RFC1039;Postel, J.;DoD statement on the NRC report;;;;;RFC 945;DOI 10.17487/RFC0945;May;https://www.rfc-editor.org/info/rfc945 | |
| RFC0946;;Nedved, R.;Telnet terminal location number option;;;;;RFC 946;DOI 10.17487/RFC0946;May;https://www.rfc-editor.org/info/rfc946 | |
| RFC0947;;Lebowitz, K. and D. Mankins;Multi-network broadcasting within the Internet;;;;;RFC 947;DOI 10.17487/RFC0947;June;https://www.rfc-editor.org/info/rfc947 | |
| RFC0948;RFC1042;Winston, I.;Two methods for the transmission of IP datagrams over IEEE 802.3 networks;;;;;RFC 948;DOI 10.17487/RFC0948;June;https://www.rfc-editor.org/info/rfc948 | |
| RFC0949;;Padlipsky, M.;FTP unique-named store command;;;;;RFC 949;DOI 10.17487/RFC0949;July;https://www.rfc-editor.org/info/rfc949 | |
| RFC0950;;Mogul, J. and J. Postel;Internet Standard Subnetting Procedure;;;;STD 5;RFC 950;DOI 10.17487/RFC0950;August;https://www.rfc-editor.org/info/rfc950 | |
| RFC0951;;Croft, W. and J. Gilmore;Bootstrap Protocol;;;;;RFC 951;DOI 10.17487/RFC0951;September;https://www.rfc-editor.org/info/rfc951 | |
| RFC0952;;Harrenstien, K., Stahl, M., and E. Feinler;DoD Internet host table specification;;;;;RFC 952;DOI 10.17487/RFC0952;October;https://www.rfc-editor.org/info/rfc952 | |
| RFC0953;;Harrenstien, K., Stahl, M., and E. Feinler;Hostname Server;;;;;RFC 953;DOI 10.17487/RFC0953;October;https://www.rfc-editor.org/info/rfc953 | |
| RFC0954;RFC3912;Harrenstien, K., Stahl, M., and E. Feinler;NICNAME/WHOIS;;;;;RFC 954;DOI 10.17487/RFC0954;October;https://www.rfc-editor.org/info/rfc954 | |
| RFC0955;;Braden, R.;Towards a transport service for transaction processing applications;;;;;RFC 955;DOI 10.17487/RFC0955;September;https://www.rfc-editor.org/info/rfc955 | |
| RFC0956;;Mills, D.;Algorithms for synchronizing network clocks;;;;;RFC 956;DOI 10.17487/RFC0956;September;https://www.rfc-editor.org/info/rfc956 | |
| RFC0957;;Mills, D.;Experiments in network clock synchronization;;;;;RFC 957;DOI 10.17487/RFC0957;September;https://www.rfc-editor.org/info/rfc957 | |
| RFC0958;RFC1059, RFC1119, RFC1305;Mills, D.;Network Time Protocol (NTP);;;;;RFC 958;DOI 10.17487/RFC0958;September;https://www.rfc-editor.org/info/rfc958 | |
| RFC0959;;Postel, J. and J. Reynolds;File Transfer Protocol;;;;STD 9;RFC 959;DOI 10.17487/RFC0959;October;https://www.rfc-editor.org/info/rfc959 | |
| RFC0960;RFC0990;Reynolds, J. and J. Postel;Assigned numbers;;;;;RFC 960;DOI 10.17487/RFC0960;December;https://www.rfc-editor.org/info/rfc960 | |
| RFC0961;RFC0991;Reynolds, J. and J. Postel;Official ARPA-Internet protocols;;;;;RFC 961;DOI 10.17487/RFC0961;December;https://www.rfc-editor.org/info/rfc961 | |
| RFC0962;;Padlipsky, M.;TCP-4 prime;;;;;RFC 962;DOI 10.17487/RFC0962;November;https://www.rfc-editor.org/info/rfc962 | |
| RFC0963;;Sidhu, D.;Some problems with the specification of the Military Standard Internet Protocol;;;;;RFC 963;DOI 10.17487/RFC0963;November;https://www.rfc-editor.org/info/rfc963 | |
| RFC0964;;Sidhu, D. and T. Blumer;Some problems with the specification of the Military Standard Transmission Control Protocol;;;;;RFC 964;DOI 10.17487/RFC0964;November;https://www.rfc-editor.org/info/rfc964 | |
| RFC0965;;Aguilar, L.;Format for a graphical communication protocol;;;;;RFC 965;DOI 10.17487/RFC0965;December;https://www.rfc-editor.org/info/rfc965 | |
| RFC0966;RFC0988;Deering, S. and D. Cheriton;Host groups: A multicast extension to the Internet Protocol;;;;;RFC 966;DOI 10.17487/RFC0966;December;https://www.rfc-editor.org/info/rfc966 | |
| RFC0967;;Padlipsky, M.;All victims together;;;;;RFC 967;DOI 10.17487/RFC0967;December;https://www.rfc-editor.org/info/rfc967 | |
| RFC0968;;Cerf, V.;Twas the night before start-up;;;;;RFC 968;DOI 10.17487/RFC0968;December;https://www.rfc-editor.org/info/rfc968 | |
| RFC0969;RFC0998;Clark, D., Lambert, M., and L. Zhang;NETBLT: A bulk data transfer protocol;;;;;RFC 969;DOI 10.17487/RFC0969;December;https://www.rfc-editor.org/info/rfc969 | |
| RFC0970;;Nagle, J.;On Packet Switches With Infinite Storage;;;;;RFC 970;DOI 10.17487/RFC0970;December;https://www.rfc-editor.org/info/rfc970 | |
| RFC0971;;DeSchon, A.;Survey of data representation standards;;;;;RFC 971;DOI 10.17487/RFC0971;January;https://www.rfc-editor.org/info/rfc971 | |
| RFC0972;;Wancho, F.;Password Generator Protocol;;;;;RFC 972;DOI 10.17487/RFC0972;January;https://www.rfc-editor.org/info/rfc972 | |
| RFC0973;RFC1034, RFC1035;Mockapetris, P.;Domain system changes and observations;;;;;RFC 973;DOI 10.17487/RFC0973;January;https://www.rfc-editor.org/info/rfc973 | |
| RFC0974;RFC2821;Partridge, C.;Mail routing and the domain system;;;;STD 10;RFC 974;DOI 10.17487/RFC0974;January;https://www.rfc-editor.org/info/rfc974 | |
| RFC0975;;Mills, D.;Autonomous confederations;;;;;RFC 975;DOI 10.17487/RFC0975;February;https://www.rfc-editor.org/info/rfc975 | |
| RFC0976;;Horton, M.;UUCP mail interchange format standard;;;;;RFC 976;DOI 10.17487/RFC0976;February;https://www.rfc-editor.org/info/rfc976 | |
| RFC0977;RFC3977;Kantor, B. and P. Lapsley;Network News Transfer Protocol;;;;;RFC 977;DOI 10.17487/RFC0977;February;https://www.rfc-editor.org/info/rfc977 | |
| RFC0978;;Reynolds, J., Gillman, R., Brackenridge, W., Witkowski, A., and J. Postel;Voice File Interchange Protocol (VFIP);;;;;RFC 978;DOI 10.17487/RFC0978;February;https://www.rfc-editor.org/info/rfc978 | |
| RFC0979;;Malis, A.;PSN End-to-End functional specification;;;;;RFC 979;DOI 10.17487/RFC0979;March;https://www.rfc-editor.org/info/rfc979 | |
| RFC0980;;Jacobsen, O. and J. Postel;Protocol document order information;;;;;RFC 980;DOI 10.17487/RFC0980;March;https://www.rfc-editor.org/info/rfc980 | |
| RFC0981;;Mills, D.;Experimental multiple-path routing algorithm;;;;;RFC 981;DOI 10.17487/RFC0981;March;https://www.rfc-editor.org/info/rfc981 | |
| RFC0982;;Braun, H.;Guidelines for the specification of the structure of the Domain Specific Part (DSP) of the ISO standard NSAP address;;;;;RFC 982;DOI 10.17487/RFC0982;April;https://www.rfc-editor.org/info/rfc982 | |
| RFC0983;RFC1006;Cass, D. and M. Rose;ISO transport arrives on top of the TCP;;;;;RFC 983;DOI 10.17487/RFC0983;April;https://www.rfc-editor.org/info/rfc983 | |
| RFC0984;RFC0993;Clark, D. and M. Lambert;PCMAIL: A distributed mail system for personal computers;;;;;RFC 984;DOI 10.17487/RFC0984;May;https://www.rfc-editor.org/info/rfc984 | |
| RFC0985;RFC1009;National Science Foundation and Network Technical Advisory Group;Requirements for Internet gateways - draft;;;;;RFC 985;DOI 10.17487/RFC0985;May;https://www.rfc-editor.org/info/rfc985 | |
| RFC0986;RFC1069;Callon, R. and H. Braun;Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol;;;;;RFC 986;DOI 10.17487/RFC0986;June;https://www.rfc-editor.org/info/rfc986 | |
| RFC0987;RFC2156, RFC1327;Kille, S.;Mapping between X.400 and RFC 822;;;;;RFC 987;DOI 10.17487/RFC0987;June;https://www.rfc-editor.org/info/rfc987 | |
| RFC0988;RFC1054, RFC1112;Deering, S.;Host extensions for IP multicasting;;;;;RFC 988;DOI 10.17487/RFC0988;July;https://www.rfc-editor.org/info/rfc988 | |
| RFC0989;RFC1040, RFC1113;Linn, J.;Privacy enhancement for Internet electronic mail: Part I: Message encipherment and authentication procedures;;;;;RFC 989;DOI 10.17487/RFC0989;February;https://www.rfc-editor.org/info/rfc989 | |
| RFC0990;RFC1010;Reynolds, J. and J. Postel;Assigned numbers;;;;;RFC 990;DOI 10.17487/RFC0990;November;https://www.rfc-editor.org/info/rfc990 | |
| RFC0991;RFC1011;Reynolds, J. and J. Postel;Official ARPA-Internet protocols;;;;;RFC 991;DOI 10.17487/RFC0991;November;https://www.rfc-editor.org/info/rfc991 | |
| RFC0992;;Birman, K. and T. Joseph;On communication support for fault tolerant process groups;;;;;RFC 992;DOI 10.17487/RFC0992;November;https://www.rfc-editor.org/info/rfc992 | |
| RFC0993;RFC1056;Clark, D. and M. Lambert;PCMAIL: A distributed mail system for personal computers;;;;;RFC 993;DOI 10.17487/RFC0993;December;https://www.rfc-editor.org/info/rfc993 | |
| RFC0994;;International Organization for Standardization;Final text of DIS 8473, Protocol for Providing the Connectionless-mode Network Service;;;;;RFC 994;DOI 10.17487/RFC0994;March;https://www.rfc-editor.org/info/rfc994 | |
| RFC0995;;International Organization for Standardization;End System to Intermediate System Routing Exchange Protocol for use in conjunction with ISO 8473;;;;;RFC 995;DOI 10.17487/RFC0995;April;https://www.rfc-editor.org/info/rfc995 | |
| RFC0996;;Mills, D.;Statistics server;;;;;RFC 996;DOI 10.17487/RFC0996;February;https://www.rfc-editor.org/info/rfc996 | |
| RFC0997;RFC1020, RFC1117;Reynolds, J. and J. Postel;Internet numbers;;;;;RFC 997;DOI 10.17487/RFC0997;March;https://www.rfc-editor.org/info/rfc997 | |
| RFC0998;;Clark, D., Lambert, M., and L. Zhang;NETBLT: A bulk data transfer protocol;;;;;RFC 998;DOI 10.17487/RFC0998;March;https://www.rfc-editor.org/info/rfc998 | |
| RFC0999;RFC1000;Westine, A. and J. Postel;Requests For Comments summary notes: 900-999;;;;;RFC 999;DOI 10.17487/RFC0999;April;https://www.rfc-editor.org/info/rfc999 | |
| RFC1000;;Reynolds, J. and J. Postel;Request For Comments reference guide;;;;;RFC 1000;DOI 10.17487/RFC1000;August;https://www.rfc-editor.org/info/rfc1000 | |
| RFC1001;;NetBIOS Working Group in the Defense Advanced Research Projects Agency, Internet Activities Board, and End-to-End Services Task Force;Protocol standard for a NetBIOS service on a TCP/UDP transport: Concepts and methods;;;;STD 19;RFC 1001;DOI 10.17487/RFC1001;March;https://www.rfc-editor.org/info/rfc1001 | |
| RFC1002;;NetBIOS Working Group in the Defense Advanced Research Projects Agency, Internet Activities Board, and End-to-End Services Task Force;Protocol standard for a NetBIOS service on a TCP/UDP transport: Detailed specifications;;;;STD 19;RFC 1002;DOI 10.17487/RFC1002;March;https://www.rfc-editor.org/info/rfc1002 | |
| RFC1003;;Katz, A.;Issues in defining an equations representation standard;;;;;RFC 1003;DOI 10.17487/RFC1003;March;https://www.rfc-editor.org/info/rfc1003 | |
| RFC1004;;Mills, D.;Distributed-protocol authentication scheme;;;;;RFC 1004;DOI 10.17487/RFC1004;April;https://www.rfc-editor.org/info/rfc1004 | |
| RFC1005;;Khanna, A. and A. Malis;ARPANET AHIP-E Host Access Protocol (enhanced AHIP);;;;;RFC 1005;DOI 10.17487/RFC1005;May;https://www.rfc-editor.org/info/rfc1005 | |
| RFC1006;;Rose, M. and D. Cass;ISO Transport Service on top of the TCP Version: 3;;;;STD 35;RFC 1006;DOI 10.17487/RFC1006;May;https://www.rfc-editor.org/info/rfc1006 | |
| RFC1007;;McCoy, W.;Military supplement to the ISO Transport Protocol;;;;;RFC 1007;DOI 10.17487/RFC1007;June;https://www.rfc-editor.org/info/rfc1007 | |
| RFC1008;;McCoy, W.;Implementation guide for the ISO Transport Protocol;;;;;RFC 1008;DOI 10.17487/RFC1008;June;https://www.rfc-editor.org/info/rfc1008 | |
| RFC1009;RFC1812;Braden, R. and J. Postel;Requirements for Internet gateways;;;;;RFC 1009;DOI 10.17487/RFC1009;June;https://www.rfc-editor.org/info/rfc1009 | |
| RFC1010;RFC1060;Reynolds, J. and J. Postel;Assigned numbers;;;;;RFC 1010;DOI 10.17487/RFC1010;May;https://www.rfc-editor.org/info/rfc1010 | |
| RFC1011;;Reynolds, J. and J. Postel;Official Internet protocols;;;;;RFC 1011;DOI 10.17487/RFC1011;May;https://www.rfc-editor.org/info/rfc1011 | |
| RFC1012;;Reynolds, J. and J. Postel;Bibliography of Request For Comments 1 through 999;;;;;RFC 1012;DOI 10.17487/RFC1012;June;https://www.rfc-editor.org/info/rfc1012 | |
| RFC1013;;Scheifler, R.;X Window System Protocol, version 11: Alpha update April 1987;;;;;RFC 1013;DOI 10.17487/RFC1013;June;https://www.rfc-editor.org/info/rfc1013 | |
| RFC1014;;Sun Microsystems;XDR: External Data Representation standard;;;;;RFC 1014;DOI 10.17487/RFC1014;June;https://www.rfc-editor.org/info/rfc1014 | |
| RFC1015;;Leiner, B.;Implementation plan for interagency research Internet;;;;;RFC 1015;DOI 10.17487/RFC1015;July;https://www.rfc-editor.org/info/rfc1015 | |
| RFC1016;;Prue, W. and J. Postel;Something a Host Could Do with Source Quench: The Source Quench Introduced Delay (SQuID);;;;;RFC 1016;DOI 10.17487/RFC1016;July;https://www.rfc-editor.org/info/rfc1016 | |
| RFC1017;;Leiner, B.;Network requirements for scientific research: Internet task force on scientific computing;;;;;RFC 1017;DOI 10.17487/RFC1017;August;https://www.rfc-editor.org/info/rfc1017 | |
| RFC1018;;McKenzie, A.;Some comments on SQuID;;;;;RFC 1018;DOI 10.17487/RFC1018;August;https://www.rfc-editor.org/info/rfc1018 | |
| RFC1019;;Arnon, D.;Report of the Workshop on Environments for Computational Mathematics;;;;;RFC 1019;DOI 10.17487/RFC1019;September;https://www.rfc-editor.org/info/rfc1019 | |
| RFC1020;RFC1062, RFC1117, RFC1166;Romano, S. and M. Stahl;Internet numbers;;;;;RFC 1020;DOI 10.17487/RFC1020;November;https://www.rfc-editor.org/info/rfc1020 | |
| RFC1021;;Partridge, C. and G. Trewitt;High-level Entity Management System (HEMS);;;;;RFC 1021;DOI 10.17487/RFC1021;October;https://www.rfc-editor.org/info/rfc1021 | |
| RFC1022;;Partridge, C. and G. Trewitt;High-level Entity Management Protocol (HEMP);;;;;RFC 1022;DOI 10.17487/RFC1022;October;https://www.rfc-editor.org/info/rfc1022 | |
| RFC1023;RFC1076;Trewitt, G. and C. Partridge;HEMS monitoring and control language;;;;;RFC 1023;DOI 10.17487/RFC1023;October;https://www.rfc-editor.org/info/rfc1023 | |
| RFC1024;;Partridge, C. and G. Trewitt;HEMS variable definitions;;;;;RFC 1024;DOI 10.17487/RFC1024;October;https://www.rfc-editor.org/info/rfc1024 | |
| RFC1025;;Postel, J.;TCP and IP bake off;;;;;RFC 1025;DOI 10.17487/RFC1025;September;https://www.rfc-editor.org/info/rfc1025 | |
| RFC1026;RFC2156, RFC1327;Kille, S.;Addendum to RFC 987: (Mapping between X.400 and RFC-822);;;;;RFC 1026;DOI 10.17487/RFC1026;September;https://www.rfc-editor.org/info/rfc1026 | |
| RFC1027;;Carl-Mitchell, S. and J. Quarterman;Using ARP to implement transparent subnet gateways;;;;;RFC 1027;DOI 10.17487/RFC1027;October;https://www.rfc-editor.org/info/rfc1027 | |
| RFC1028;;Davin, J., Case, J., Fedor, M., and M. Schoffstall;Simple Gateway Monitoring Protocol;;;;;RFC 1028;DOI 10.17487/RFC1028;November;https://www.rfc-editor.org/info/rfc1028 | |
| RFC1029;;Parr, G.;More fault tolerant approach to address resolution for a Multi-LAN system of Ethernets;;;;;RFC 1029;DOI 10.17487/RFC1029;May;https://www.rfc-editor.org/info/rfc1029 | |
| RFC1030;;Lambert, M.;On testing the NETBLT Protocol over divers networks;;;;;RFC 1030;DOI 10.17487/RFC1030;November;https://www.rfc-editor.org/info/rfc1030 | |
| RFC1031;;Lazear, W.;MILNET name domain transition;;;;;RFC 1031;DOI 10.17487/RFC1031;November;https://www.rfc-editor.org/info/rfc1031 | |
| RFC1032;;Stahl, M.;Domain administrators guide;;;;;RFC 1032;DOI 10.17487/RFC1032;November;https://www.rfc-editor.org/info/rfc1032 | |
| RFC1033;;Lottor, M.;Domain Administrators Operations Guide;;;;;RFC 1033;DOI 10.17487/RFC1033;November;https://www.rfc-editor.org/info/rfc1033 | |
| RFC1034;;Mockapetris, P.;Domain names - concepts and facilities;;;;STD 13;RFC 1034;DOI 10.17487/RFC1034;November;https://www.rfc-editor.org/info/rfc1034 | |
| RFC1035;;Mockapetris, P.;Domain names - implementation and specification;;;;STD 13;RFC 1035;DOI 10.17487/RFC1035;November;https://www.rfc-editor.org/info/rfc1035 | |
| RFC1036;RFC5536, RFC5537;Horton, M. and R. Adams;Standard for interchange of USENET messages;;;;;RFC 1036;DOI 10.17487/RFC1036;December;https://www.rfc-editor.org/info/rfc1036 | |
| RFC1037;;Greenberg, B. and S. Keene;NFILE - a file access protocol;;;;;RFC 1037;DOI 10.17487/RFC1037;December;https://www.rfc-editor.org/info/rfc1037 | |
| RFC1038;RFC1108;St. Johns, M.;Draft revised IP security option;;;;;RFC 1038;DOI 10.17487/RFC1038;January;https://www.rfc-editor.org/info/rfc1038 | |
| RFC1039;;Latham, D.;DoD statement on Open Systems Interconnection protocols;;;;;RFC 1039;DOI 10.17487/RFC1039;January;https://www.rfc-editor.org/info/rfc1039 | |
| RFC1040;RFC1113;Linn, J.;Privacy enhancement for Internet electronic mail: Part I: Message encipherment and authentication procedures;;;;;RFC 1040;DOI 10.17487/RFC1040;January;https://www.rfc-editor.org/info/rfc1040 | |
| RFC1041;;Rekhter, Y.;Telnet 3270 regime option;;;;;RFC 1041;DOI 10.17487/RFC1041;January;https://www.rfc-editor.org/info/rfc1041 | |
| RFC1042;;Postel, J. and J. Reynolds;Standard for the transmission of IP datagrams over IEEE 802 networks;;;;STD 43;RFC 1042;DOI 10.17487/RFC1042;February;https://www.rfc-editor.org/info/rfc1042 | |
| RFC1043;;Yasuda, A. and T. Thompson;Telnet Data Entry Terminal option: DODIIS implementation;;;;;RFC 1043;DOI 10.17487/RFC1043;February;https://www.rfc-editor.org/info/rfc1043 | |
| RFC1044;;Hardwick, K. and J. Lekashman;Internet Protocol on Network System's HYPERchannel: Protocol Specification;;;;STD 45;RFC 1044;DOI 10.17487/RFC1044;February;https://www.rfc-editor.org/info/rfc1044 | |
| RFC1045;;Cheriton, D.;VMTP: Versatile Message Transaction Protocol: Protocol specification;;;;;RFC 1045;DOI 10.17487/RFC1045;February;https://www.rfc-editor.org/info/rfc1045 | |
| RFC1046;;Prue, W. and J. Postel;Queuing algorithm to provide type-of-service for IP links;;;;;RFC 1046;DOI 10.17487/RFC1046;February;https://www.rfc-editor.org/info/rfc1046 | |
| RFC1047;;Partridge, C.;Duplicate messages and SMTP;;;;;RFC 1047;DOI 10.17487/RFC1047;February;https://www.rfc-editor.org/info/rfc1047 | |
| RFC1048;RFC1084, RFC1395, RFC1497, RFC1533;Prindeville, P.;BOOTP vendor information extensions;;;;;RFC 1048;DOI 10.17487/RFC1048;February;https://www.rfc-editor.org/info/rfc1048 | |
| RFC1049;;Sirbu, M.;Content-type header field for Internet messages;;;;;RFC 1049;DOI 10.17487/RFC1049;March;https://www.rfc-editor.org/info/rfc1049 | |
| RFC1050;RFC1057;Sun Microsystems;RPC: Remote Procedure Call Protocol specification;;;;;RFC 1050;DOI 10.17487/RFC1050;April;https://www.rfc-editor.org/info/rfc1050 | |
| RFC1051;RFC1201;Prindeville, P.;Standard for the transmission of IP datagrams and ARP packets over ARCNET networks;;;;;RFC 1051;DOI 10.17487/RFC1051;March;https://www.rfc-editor.org/info/rfc1051 | |
| RFC1052;;Cerf, V.;IAB recommendations for the development of Internet network management standards;;;;;RFC 1052;DOI 10.17487/RFC1052;April;https://www.rfc-editor.org/info/rfc1052 | |
| RFC1053;;Levy, S. and T. Jacobson;Telnet X.3 PAD option;;;;;RFC 1053;DOI 10.17487/RFC1053;April;https://www.rfc-editor.org/info/rfc1053 | |
| RFC1054;RFC1112;Deering, S.;Host extensions for IP multicasting;;;;;RFC 1054;DOI 10.17487/RFC1054;May;https://www.rfc-editor.org/info/rfc1054 | |
| RFC1055;;Romkey, J.;Nonstandard for transmission of IP datagrams over serial lines: SLIP;;;;STD 47;RFC 1055;DOI 10.17487/RFC1055;June;https://www.rfc-editor.org/info/rfc1055 | |
| RFC1056;;Lambert, M.;PCMAIL: A distributed mail system for personal computers;;;;;RFC 1056;DOI 10.17487/RFC1056;June;https://www.rfc-editor.org/info/rfc1056 | |
| RFC1057;;Sun Microsystems;RPC: Remote Procedure Call Protocol specification: Version 2;;;;;RFC 1057;DOI 10.17487/RFC1057;June;https://www.rfc-editor.org/info/rfc1057 | |
| RFC1058;;Hedrick, C.;Routing Information Protocol;;;;;RFC 1058;DOI 10.17487/RFC1058;June;https://www.rfc-editor.org/info/rfc1058 | |
| RFC1059;RFC1119, RFC1305;Mills, D.;Network Time Protocol (version 1) specification and implementation;;;;;RFC 1059;DOI 10.17487/RFC1059;July;https://www.rfc-editor.org/info/rfc1059 | |
| RFC1060;RFC1340;Reynolds, J. and J. Postel;Assigned numbers;;;;;RFC 1060;DOI 10.17487/RFC1060;March;https://www.rfc-editor.org/info/rfc1060 | |
| RFC1062;RFC1117, RFC1166;Romano, S., Stahl, M., and M. Recker;Internet numbers;;;;;RFC 1062;DOI 10.17487/RFC1062;August;https://www.rfc-editor.org/info/rfc1062 | |
| RFC1063;RFC1191;Mogul, J., Kent, C., Partridge, C., and K. McCloghrie;IP MTU discovery options;;;;;RFC 1063;DOI 10.17487/RFC1063;July;https://www.rfc-editor.org/info/rfc1063 | |
| RFC1064;RFC1176, RFC1203;Crispin, M.;Interactive Mail Access Protocol: Version 2;;;;;RFC 1064;DOI 10.17487/RFC1064;July;https://www.rfc-editor.org/info/rfc1064 | |
| RFC1065;RFC1155;McCloghrie, K. and M. Rose;Structure and identification of management information for TCP/IP-based internets;;;;;RFC 1065;DOI 10.17487/RFC1065;August;https://www.rfc-editor.org/info/rfc1065 | |
| RFC1066;RFC1156;McCloghrie, K. and M. Rose;Management Information Base for network management of TCP/IP-based internets;;;;;RFC 1066;DOI 10.17487/RFC1066;August;https://www.rfc-editor.org/info/rfc1066 | |
| RFC1067;RFC1098;Case, J., Fedor, M., Schoffstall, M., and J. Davin;Simple Network Management Protocol;;;;;RFC 1067;DOI 10.17487/RFC1067;August;https://www.rfc-editor.org/info/rfc1067 | |
| RFC1068;;DeSchon, A. and R. Braden;Background File Transfer Program (BFTP);;;;;RFC 1068;DOI 10.17487/RFC1068;August;https://www.rfc-editor.org/info/rfc1068 | |
| RFC1069;;Callon, R. and H. Braun;Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol;;;;;RFC 1069;DOI 10.17487/RFC1069;February;https://www.rfc-editor.org/info/rfc1069 | |
| RFC1070;;Hagens, R., Hall, N., and M. Rose;Use of the Internet as a subnetwork for experimentation with the OSI network layer;;;;;RFC 1070;DOI 10.17487/RFC1070;February;https://www.rfc-editor.org/info/rfc1070 | |
| RFC1071;;Braden, R., Borman, D., and C. Partridge;Computing the Internet checksum;;;;;RFC 1071;DOI 10.17487/RFC1071;September;https://www.rfc-editor.org/info/rfc1071 | |
| RFC1072;RFC1323, RFC2018, RFC6247;Jacobson, V. and R. Braden;TCP extensions for long-delay paths;;;;;RFC 1072;DOI 10.17487/RFC1072;October;https://www.rfc-editor.org/info/rfc1072 | |
| RFC1073;;Waitzman, D.;Telnet window size option;;;;;RFC 1073;DOI 10.17487/RFC1073;October;https://www.rfc-editor.org/info/rfc1073 | |
| RFC1074;;Rekhter, J.;NSFNET backbone SPF based Interior Gateway Protocol;;;;;RFC 1074;DOI 10.17487/RFC1074;October;https://www.rfc-editor.org/info/rfc1074 | |
| RFC1075;;Waitzman, D., Partridge, C., and S. Deering;Distance Vector Multicast Routing Protocol;;;;;RFC 1075;DOI 10.17487/RFC1075;November;https://www.rfc-editor.org/info/rfc1075 | |
| RFC1076;;Trewitt, G. and C. Partridge;HEMS monitoring and control language;;;;;RFC 1076;DOI 10.17487/RFC1076;November;https://www.rfc-editor.org/info/rfc1076 | |
| RFC1077;;Leiner, B.;Critical issues in high bandwidth networking;;;;;RFC 1077;DOI 10.17487/RFC1077;November;https://www.rfc-editor.org/info/rfc1077 | |
| RFC1078;RFC7805;Lottor, M.;TCP port service Multiplexer (TCPMUX);;;;;RFC 1078;DOI 10.17487/RFC1078;November;https://www.rfc-editor.org/info/rfc1078 | |
| RFC1079;;Hedrick, C.;Telnet terminal speed option;;;;;RFC 1079;DOI 10.17487/RFC1079;December;https://www.rfc-editor.org/info/rfc1079 | |
| RFC1080;RFC1372;Hedrick, C.;Telnet remote flow control option;;;;;RFC 1080;DOI 10.17487/RFC1080;November;https://www.rfc-editor.org/info/rfc1080 | |
| RFC1081;RFC1225;Rose, M.;Post Office Protocol: Version 3;;;;;RFC 1081;DOI 10.17487/RFC1081;November;https://www.rfc-editor.org/info/rfc1081 | |
| RFC1082;;Rose, M.;Post Office Protocol: Version 3: Extended service offerings;;;;;RFC 1082;DOI 10.17487/RFC1082;November;https://www.rfc-editor.org/info/rfc1082 | |
| RFC1083;RFC1100;Defense Advanced Research Projects Agency and Internet Activities Board;IAB official protocol standards;;;;;RFC 1083;DOI 10.17487/RFC1083;December;https://www.rfc-editor.org/info/rfc1083 | |
| RFC1084;RFC1395, RFC1497, RFC1533;Reynolds, J.;BOOTP vendor information extensions;;;;;RFC 1084;DOI 10.17487/RFC1084;December;https://www.rfc-editor.org/info/rfc1084 | |
| RFC1085;;Rose, M.;ISO presentation services on top of TCP/IP based internets;;;;;RFC 1085;DOI 10.17487/RFC1085;December;https://www.rfc-editor.org/info/rfc1085 | |
| RFC1086;;Onions, J. and M. Rose;ISO-TP0 bridge between TCP and X.25;;;;;RFC 1086;DOI 10.17487/RFC1086;December;https://www.rfc-editor.org/info/rfc1086 | |
| RFC1087;;Defense Advanced Research Projects Agency and Internet Activities Board;Ethics and the Internet;;;;;RFC 1087;DOI 10.17487/RFC1087;January;https://www.rfc-editor.org/info/rfc1087 | |
| RFC1088;;McLaughlin, L.;Standard for the transmission of IP datagrams over NetBIOS networks;;;;STD 48;RFC 1088;DOI 10.17487/RFC1088;February;https://www.rfc-editor.org/info/rfc1088 | |
| RFC1089;RFC4789;Schoffstall, M., Davin, C., Fedor, M., and J. Case;SNMP over Ethernet;;;;;RFC 1089;DOI 10.17487/RFC1089;February;https://www.rfc-editor.org/info/rfc1089 | |
| RFC1090;;Ullmann, R.;SMTP on X.25;;;;;RFC 1090;DOI 10.17487/RFC1090;February;https://www.rfc-editor.org/info/rfc1090 | |
| RFC1091;;VanBokkelen, J.;Telnet terminal-type option;;;;;RFC 1091;DOI 10.17487/RFC1091;February;https://www.rfc-editor.org/info/rfc1091 | |
| RFC1092;;Rekhter, J.;EGP and policy based routing in the new NSFNET backbone;;;;;RFC 1092;DOI 10.17487/RFC1092;February;https://www.rfc-editor.org/info/rfc1092 | |
| RFC1093;;Braun, H.;NSFNET routing architecture;;;;;RFC 1093;DOI 10.17487/RFC1093;February;https://www.rfc-editor.org/info/rfc1093 | |
| RFC1094;;Nowicki, B.;NFS: Network File System Protocol specification;;;;;RFC 1094;DOI 10.17487/RFC1094;March;https://www.rfc-editor.org/info/rfc1094 | |
| RFC1095;RFC1189;Warrier, U. and L. Besaw;Common Management Information Services and Protocol over TCP/IP (CMOT);;;;;RFC 1095;DOI 10.17487/RFC1095;April;https://www.rfc-editor.org/info/rfc1095 | |
| RFC1096;;Marcy, G.;Telnet X display location option;;;;;RFC 1096;DOI 10.17487/RFC1096;March;https://www.rfc-editor.org/info/rfc1096 | |
| RFC1097;;Miller, B.;Telnet subliminal-message option;;;;;RFC 1097;DOI 10.17487/RFC1097;April;https://www.rfc-editor.org/info/rfc1097 | |
| RFC1098;RFC1157;Case, J., Fedor, M., Schoffstall, M., and J. Davin;Simple Network Management Protocol (SNMP);;;;;RFC 1098;DOI 10.17487/RFC1098;April;https://www.rfc-editor.org/info/rfc1098 | |
| RFC1099;;Reynolds, J.;Request for Comments Summary: RFC Numbers 1000-1099;;;;;RFC 1099;DOI 10.17487/RFC1099;December;https://www.rfc-editor.org/info/rfc1099 | |
| RFC1100;RFC1130;Defense Advanced Research Projects Agency and Internet Activities Board;IAB official protocol standards;;;;;RFC 1100;DOI 10.17487/RFC1100;April;https://www.rfc-editor.org/info/rfc1100 | |
| RFC1101;;Mockapetris, P.;DNS encoding of network names and other types;;;;;RFC 1101;DOI 10.17487/RFC1101;April;https://www.rfc-editor.org/info/rfc1101 | |
| RFC1102;;Clark, D.;Policy routing in Internet protocols;;;;;RFC 1102;DOI 10.17487/RFC1102;May;https://www.rfc-editor.org/info/rfc1102 | |
| RFC1103;RFC1188;Katz, D.;Proposed standard for the transmission of IP datagrams over FDDI Networks;;;;;RFC 1103;DOI 10.17487/RFC1103;June;https://www.rfc-editor.org/info/rfc1103 | |
| RFC1104;;Braun, H.;Models of policy based routing;;;;;RFC 1104;DOI 10.17487/RFC1104;June;https://www.rfc-editor.org/info/rfc1104 | |
| RFC1105;RFC1163;Lougheed, K. and Y. Rekhter;Border Gateway Protocol (BGP);;;;;RFC 1105;DOI 10.17487/RFC1105;June;https://www.rfc-editor.org/info/rfc1105 | |
| RFC1106;RFC6247;Fox, R.;TCP big window and NAK options;;;;;RFC 1106;DOI 10.17487/RFC1106;June;https://www.rfc-editor.org/info/rfc1106 | |
| RFC1107;;Sollins, K.;Plan for Internet directory services;;;;;RFC 1107;DOI 10.17487/RFC1107;July;https://www.rfc-editor.org/info/rfc1107 | |
| RFC1108;;Kent, S.;U.S. Department of Defense Security Options for the Internet Protocol;;;;;RFC 1108;DOI 10.17487/RFC1108;November;https://www.rfc-editor.org/info/rfc1108 | |
| RFC1109;;Cerf, V.;Report of the second Ad Hoc Network Management Review Group;;;;;RFC 1109;DOI 10.17487/RFC1109;August;https://www.rfc-editor.org/info/rfc1109 | |
| RFC1110;RFC6247;McKenzie, A.;Problem with the TCP big window option;;;;;RFC 1110;DOI 10.17487/RFC1110;August;https://www.rfc-editor.org/info/rfc1110 | |
| RFC1111;RFC1543, RFC2223;Postel, J.;Request for comments on Request for Comments: Instructions to RFC authors;;;;;RFC 1111;DOI 10.17487/RFC1111;August;https://www.rfc-editor.org/info/rfc1111 | |
| RFC1112;;Deering, S.;Host extensions for IP multicasting;;;;STD 5;RFC 1112;DOI 10.17487/RFC1112;August;https://www.rfc-editor.org/info/rfc1112 | |
| RFC1113;RFC1421;Linn, J.;Privacy enhancement for Internet electronic mail: Part I - message encipherment and authentication procedures;;;;;RFC 1113;DOI 10.17487/RFC1113;August;https://www.rfc-editor.org/info/rfc1113 | |
| RFC1114;RFC1422;Kent, S. and J. Linn;Privacy enhancement for Internet electronic mail: Part II - certificate-based key management;;;;;RFC 1114;DOI 10.17487/RFC1114;August;https://www.rfc-editor.org/info/rfc1114 | |
| RFC1115;RFC1423;Linn, J.;Privacy enhancement for Internet electronic mail: Part III - algorithms, modes, and identifiers;;;;;RFC 1115;DOI 10.17487/RFC1115;August;https://www.rfc-editor.org/info/rfc1115 | |
| RFC1116;RFC1184;Borman, D.;Telnet Linemode option;;;;;RFC 1116;DOI 10.17487/RFC1116;August;https://www.rfc-editor.org/info/rfc1116 | |
| RFC1117;RFC1166;Romano, S., Stahl, M., and M. Recker;Internet numbers;;;;;RFC 1117;DOI 10.17487/RFC1117;August;https://www.rfc-editor.org/info/rfc1117 | |
| RFC1118;;Krol, E.;Hitchhikers guide to the Internet;;;;;RFC 1118;DOI 10.17487/RFC1118;September;https://www.rfc-editor.org/info/rfc1118 | |
| RFC1119;RFC1305;Mills, D.;Network Time Protocol (version 2) specification and implementation;;;;;RFC 1119;DOI 10.17487/RFC1119;September;https://www.rfc-editor.org/info/rfc1119 | |
| RFC1120;RFC1160;Cerf, V.;Internet Activities Board;;;;;RFC 1120;DOI 10.17487/RFC1120;September;https://www.rfc-editor.org/info/rfc1120 | |
| RFC1121;;Postel, J., Kleinrock, L., Cerf, V., and B. Boehm;Act one - the poems;;;;;RFC 1121;DOI 10.17487/RFC1121;September;https://www.rfc-editor.org/info/rfc1121 | |
| RFC1122;;Braden, R., Ed.;Requirements for Internet Hosts - Communication Layers;;;;STD 3;RFC 1122;DOI 10.17487/RFC1122;October;https://www.rfc-editor.org/info/rfc1122 | |
| RFC1123;;Braden, R., Ed.;Requirements for Internet Hosts - Application and Support;;;;STD 3;RFC 1123;DOI 10.17487/RFC1123;October;https://www.rfc-editor.org/info/rfc1123 | |
| RFC1124;;Leiner, B.;Policy issues in interconnecting networks;;;;;RFC 1124;DOI 10.17487/RFC1124;September;https://www.rfc-editor.org/info/rfc1124 | |
| RFC1125;;Estrin, D.;Policy requirements for inter Administrative Domain routing;;;;;RFC 1125;DOI 10.17487/RFC1125;November;https://www.rfc-editor.org/info/rfc1125 | |
| RFC1126;;Little, M.;Goals and functional requirements for inter-autonomous system routing;;;;;RFC 1126;DOI 10.17487/RFC1126;October;https://www.rfc-editor.org/info/rfc1126 | |
| RFC1127;;Braden, R.;Perspective on the Host Requirements RFCs;;;;;RFC 1127;DOI 10.17487/RFC1127;October;https://www.rfc-editor.org/info/rfc1127 | |
| RFC1128;;Mills, D.;Measured performance of the Network Time Protocol in the Internet system;;;;;RFC 1128;DOI 10.17487/RFC1128;October;https://www.rfc-editor.org/info/rfc1128 | |
| RFC1129;;Mills, D.;Internet Time Synchronization: The Network Time Protocol;;;;;RFC 1129;DOI 10.17487/RFC1129;October;https://www.rfc-editor.org/info/rfc1129 | |
| RFC1130;RFC1140;Defense Advanced Research Projects Agency and Internet Activities Board;IAB official protocol standards;;;;;RFC 1130;DOI 10.17487/RFC1130;October;https://www.rfc-editor.org/info/rfc1130 | |
| RFC1131;RFC1247;Moy, J.;OSPF specification;;;;;RFC 1131;DOI 10.17487/RFC1131;October;https://www.rfc-editor.org/info/rfc1131 | |
| RFC1132;;McLaughlin, L.;Standard for the transmission of 802.2 packets over IPX networks;;;;STD 49;RFC 1132;DOI 10.17487/RFC1132;November;https://www.rfc-editor.org/info/rfc1132 | |
| RFC1133;;Yu, J. and H. Braun;Routing between the NSFNET and the DDN;;;;;RFC 1133;DOI 10.17487/RFC1133;November;https://www.rfc-editor.org/info/rfc1133 | |
| RFC1134;RFC1171;Perkins, D.;Point-to-Point Protocol: A proposal for multi-protocol transmission of datagrams over Point-to-Point links;;;;;RFC 1134;DOI 10.17487/RFC1134;November;https://www.rfc-editor.org/info/rfc1134 | |
| RFC1135;;Reynolds, J.;Helminthiasis of the Internet;;;;;RFC 1135;DOI 10.17487/RFC1135;December;https://www.rfc-editor.org/info/rfc1135 | |
| RFC1136;;Hares, S. and D. Katz;Administrative Domains and Routing Domains: A model for routing in the Internet;;;;;RFC 1136;DOI 10.17487/RFC1136;December;https://www.rfc-editor.org/info/rfc1136 | |
| RFC1137;;Kille, S.;Mapping between full RFC 822 and RFC 822 with restricted encoding;;;;;RFC 1137;DOI 10.17487/RFC1137;December;https://www.rfc-editor.org/info/rfc1137 | |
| RFC1138;RFC2156, RFC1327;Kille, S.;Mapping between X.400(1988) / ISO 10021 and RFC 822;;;;;RFC 1138;DOI 10.17487/RFC1138;December;https://www.rfc-editor.org/info/rfc1138 | |
| RFC1139;RFC1574, RFC1575;Hagens, R.;Echo function for ISO 8473;;;;;RFC 1139;DOI 10.17487/RFC1139;January;https://www.rfc-editor.org/info/rfc1139 | |
| RFC1140;RFC1200;Defense Advanced Research Projects Agency and Internet Activities Board;IAB official protocol standards;;;;;RFC 1140;DOI 10.17487/RFC1140;May;https://www.rfc-editor.org/info/rfc1140 | |
| RFC1141;;Mallory, T. and A. Kullberg;Incremental updating of the Internet checksum;;;;;RFC 1141;DOI 10.17487/RFC1141;January;https://www.rfc-editor.org/info/rfc1141 | |
| RFC1142;RFC7142;Oran, D., Ed.;OSI IS-IS Intra-domain Routing Protocol;;;;;RFC 1142;DOI 10.17487/RFC1142;February;https://www.rfc-editor.org/info/rfc1142 | |
| RFC1143;;Bernstein, D.;The Q Method of Implementing TELNET Option Negotiation;;;;;RFC 1143;DOI 10.17487/RFC1143;February;https://www.rfc-editor.org/info/rfc1143 | |
| RFC1144;;Jacobson, V.;Compressing TCP/IP Headers for Low-Speed Serial Links;;;;;RFC 1144;DOI 10.17487/RFC1144;February;https://www.rfc-editor.org/info/rfc1144 | |
| RFC1145;RFC1146, RFC6247;Zweig, J. and C. Partridge;TCP alternate checksum options;;;;;RFC 1145;DOI 10.17487/RFC1145;February;https://www.rfc-editor.org/info/rfc1145 | |
| RFC1146;RFC6247;Zweig, J. and C. Partridge;TCP alternate checksum options;;;;;RFC 1146;DOI 10.17487/RFC1146;March;https://www.rfc-editor.org/info/rfc1146 | |
| RFC1147;RFC1470;Stine, R.;FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices;;;;;RFC 1147;DOI 10.17487/RFC1147;April;https://www.rfc-editor.org/info/rfc1147 | |
| RFC1148;RFC2156, RFC1327;Kille, S.;Mapping between X.400(1988) / ISO 10021 and RFC 822;;;;;RFC 1148;DOI 10.17487/RFC1148;March;https://www.rfc-editor.org/info/rfc1148 | |
| RFC1149;;Waitzman, D.;Standard for the transmission of IP datagrams on avian carriers;;;;;RFC 1149;DOI 10.17487/RFC1149;April;https://www.rfc-editor.org/info/rfc1149 | |
| RFC1150;RFC6360;Malkin, G. and J. Reynolds;FYI on FYI: Introduction to the FYI Notes;;;;;RFC 1150;DOI 10.17487/RFC1150;March;https://www.rfc-editor.org/info/rfc1150 | |
| RFC1151;;Partridge, C. and R. Hinden;Version 2 of the Reliable Data Protocol (RDP);;;;;RFC 1151;DOI 10.17487/RFC1151;April;https://www.rfc-editor.org/info/rfc1151 | |
| RFC1152;;Partridge, C.;Workshop report: Internet research steering group workshop on very-high-speed networks;;;;;RFC 1152;DOI 10.17487/RFC1152;April;https://www.rfc-editor.org/info/rfc1152 | |
| RFC1153;;Wancho, F.;Digest message format;;;;;RFC 1153;DOI 10.17487/RFC1153;April;https://www.rfc-editor.org/info/rfc1153 | |
| RFC1154;RFC1505;Robinson, D. and R. Ullmann;Encoding header field for internet messages;;;;;RFC 1154;DOI 10.17487/RFC1154;April;https://www.rfc-editor.org/info/rfc1154 | |
| RFC1155;;Rose, M. and K. McCloghrie;Structure and identification of management information for TCP/IP-based internets;;;;STD 16;RFC 1155;DOI 10.17487/RFC1155;May;https://www.rfc-editor.org/info/rfc1155 | |
| RFC1156;;McCloghrie, K. and M. Rose;Management Information Base for network management of TCP/IP-based internets;;;;;RFC 1156;DOI 10.17487/RFC1156;May;https://www.rfc-editor.org/info/rfc1156 | |
| RFC1157;;Case, J., Fedor, M., Schoffstall, M., and J. Davin;Simple Network Management Protocol (SNMP);;;;;RFC 1157;DOI 10.17487/RFC1157;May;https://www.rfc-editor.org/info/rfc1157 | |
| RFC1158;RFC1213;Rose, M.;Management Information Base for network management of TCP/IP-based internets: MIB-II;;;;;RFC 1158;DOI 10.17487/RFC1158;May;https://www.rfc-editor.org/info/rfc1158 | |
| RFC1159;RFC1312;Nelson, R.;Message Send Protocol;;;;;RFC 1159;DOI 10.17487/RFC1159;June;https://www.rfc-editor.org/info/rfc1159 | |
| RFC1160;;Cerf, V.;Internet Activities Board;;;;;RFC 1160;DOI 10.17487/RFC1160;May;https://www.rfc-editor.org/info/rfc1160 | |
| RFC1161;RFC1418;Rose, M.;SNMP over OSI;;;;;RFC 1161;DOI 10.17487/RFC1161;June;https://www.rfc-editor.org/info/rfc1161 | |
| RFC1162;RFC1238;Satz, G.;Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542) Management Information Base;;;;;RFC 1162;DOI 10.17487/RFC1162;June;https://www.rfc-editor.org/info/rfc1162 | |
| RFC1163;RFC1267;Lougheed, K. and Y. Rekhter;Border Gateway Protocol (BGP);;;;;RFC 1163;DOI 10.17487/RFC1163;June;https://www.rfc-editor.org/info/rfc1163 | |
| RFC1164;RFC1268;Honig, J., Katz, D., Mathis, M., Rekhter, Y., and J. Yu;Application of the Border Gateway Protocol in the Internet;;;;;RFC 1164;DOI 10.17487/RFC1164;June;https://www.rfc-editor.org/info/rfc1164 | |
| RFC1165;;Crowcroft, J. and J. Onions;Network Time Protocol (NTP) over the OSI Remote Operations Service;;;;;RFC 1165;DOI 10.17487/RFC1165;June;https://www.rfc-editor.org/info/rfc1165 | |
| RFC1166;;Kirkpatrick, S., Stahl, M., and M. Recker;Internet numbers;;;;;RFC 1166;DOI 10.17487/RFC1166;July;https://www.rfc-editor.org/info/rfc1166 | |
| RFC1167;;Cerf, V.;Thoughts on the National Research and Education Network;;;;;RFC 1167;DOI 10.17487/RFC1167;July;https://www.rfc-editor.org/info/rfc1167 | |
| RFC1168;;Westine, A., DeSchon, A., Postel, J., and C. Ward;Intermail and Commercial Mail Relay services;;;;;RFC 1168;DOI 10.17487/RFC1168;July;https://www.rfc-editor.org/info/rfc1168 | |
| RFC1169;;Cerf, V. and K. Mills;Explaining the role of GOSIP;;;;;RFC 1169;DOI 10.17487/RFC1169;August;https://www.rfc-editor.org/info/rfc1169 | |
| RFC1170;;Fougner, R.;Public key standards and licenses;;;;;RFC 1170;DOI 10.17487/RFC1170;January;https://www.rfc-editor.org/info/rfc1170 | |
| RFC1171;RFC1331;Perkins, D.;Point-to-Point Protocol for the transmission of multi-protocol datagrams over Point-to-Point links;;;;;RFC 1171;DOI 10.17487/RFC1171;July;https://www.rfc-editor.org/info/rfc1171 | |
| RFC1172;RFC1331, RFC1332;Perkins, D. and R. Hobby;Point-to-Point Protocol (PPP) initial configuration options;;;;;RFC 1172;DOI 10.17487/RFC1172;July;https://www.rfc-editor.org/info/rfc1172 | |
| RFC1173;;VanBokkelen, J.;Responsibilities of host and network managers: A summary of the "oral tradition" of the Internet;;;;;RFC 1173;DOI 10.17487/RFC1173;August;https://www.rfc-editor.org/info/rfc1173 | |
| RFC1174;;Cerf, V.;IAB recommended policy on distributing internet identifier assignment and IAB recommended policy change to internet "connected" status;;;;;RFC 1174;DOI 10.17487/RFC1174;August;https://www.rfc-editor.org/info/rfc1174 | |
| RFC1175;;Bowers, K., LaQuey, T., Reynolds, J., Roubicek, K., Stahl, M., and A. Yuan;FYI on where to start: A bibliography of internetworking information;;FYI 3;;;RFC 1175;DOI 10.17487/RFC1175;August;https://www.rfc-editor.org/info/rfc1175 | |
| RFC1176;;Crispin, M.;Interactive Mail Access Protocol: Version 2;;;;;RFC 1176;DOI 10.17487/RFC1176;August;https://www.rfc-editor.org/info/rfc1176 | |
| RFC1177;RFC1206;Malkin, G., Marine, A., and J. Reynolds;FYI on Questions and Answers: Answers to commonly asked "new internet user" questions;;;;;RFC 1177;DOI 10.17487/RFC1177;August;https://www.rfc-editor.org/info/rfc1177 | |
| RFC1178;;Libes, D.;Choosing a name for your computer;;FYI 5;;;RFC 1178;DOI 10.17487/RFC1178;August;https://www.rfc-editor.org/info/rfc1178 | |
| RFC1179;;McLaughlin, L.;Line printer daemon protocol;;;;;RFC 1179;DOI 10.17487/RFC1179;August;https://www.rfc-editor.org/info/rfc1179 | |
| RFC1180;;Socolofsky, T. and C. Kale;TCP/IP tutorial;;;;;RFC 1180;DOI 10.17487/RFC1180;January;https://www.rfc-editor.org/info/rfc1180 | |
| RFC1181;;Blokzijl, R.;RIPE Terms of Reference;;;;;RFC 1181;DOI 10.17487/RFC1181;September;https://www.rfc-editor.org/info/rfc1181 | |
| RFC1183;;Everhart, C., Mamakos, L., Ullmann, R., and P. Mockapetris;New DNS RR Definitions;;;;;RFC 1183;DOI 10.17487/RFC1183;October;https://www.rfc-editor.org/info/rfc1183 | |
| RFC1184;;Borman, D.;Telnet Linemode Option;;;;;RFC 1184;DOI 10.17487/RFC1184;October;https://www.rfc-editor.org/info/rfc1184 | |
| RFC1185;RFC1323;Jacobson, V., Braden, R., and L. Zhang;TCP Extension for High-Speed Paths;;;;;RFC 1185;DOI 10.17487/RFC1185;October;https://www.rfc-editor.org/info/rfc1185 | |
| RFC1186;RFC1320;Rivest, R.;MD4 Message Digest Algorithm;;;;;RFC 1186;DOI 10.17487/RFC1186;October;https://www.rfc-editor.org/info/rfc1186 | |
| RFC1187;;Rose, M., McCloghrie, K., and J. Davin;Bulk Table Retrieval with the SNMP;;;;;RFC 1187;DOI 10.17487/RFC1187;October;https://www.rfc-editor.org/info/rfc1187 | |
| RFC1188;;Katz, D.;Proposed Standard for the Transmission of IP Datagrams over FDDI Networks;;;;;RFC 1188;DOI 10.17487/RFC1188;October;https://www.rfc-editor.org/info/rfc1188 | |
| RFC1189;;Warrier, U., Besaw, L., LaBarre, L., and B. Handspicker;Common Management Information Services and Protocols for the Internet (CMOT and CMIP);;;;;RFC 1189;DOI 10.17487/RFC1189;October;https://www.rfc-editor.org/info/rfc1189 | |
| RFC1190;RFC1819;Topolcic, C.;Experimental Internet Stream Protocol: Version 2 (ST-II);;;;;RFC 1190;DOI 10.17487/RFC1190;October;https://www.rfc-editor.org/info/rfc1190 | |
| RFC1191;;Mogul, J. and S. Deering;Path MTU discovery;;;;;RFC 1191;DOI 10.17487/RFC1191;November;https://www.rfc-editor.org/info/rfc1191 | |
| RFC1192;;Kahin, B.;Commercialization of the Internet summary report;;;;;RFC 1192;DOI 10.17487/RFC1192;November;https://www.rfc-editor.org/info/rfc1192 | |
| RFC1193;;Ferrari, D.;Client requirements for real-time communication services;;;;;RFC 1193;DOI 10.17487/RFC1193;November;https://www.rfc-editor.org/info/rfc1193 | |
| RFC1194;RFC1196, RFC1288;Zimmerman, D.;Finger User Information Protocol;;;;;RFC 1194;DOI 10.17487/RFC1194;November;https://www.rfc-editor.org/info/rfc1194 | |
| RFC1195;;Callon, R.;Use of OSI IS-IS for routing in TCP/IP and dual environments;;;;;RFC 1195;DOI 10.17487/RFC1195;December;https://www.rfc-editor.org/info/rfc1195 | |
| RFC1196;RFC1288;Zimmerman, D.;Finger User Information Protocol;;;;;RFC 1196;DOI 10.17487/RFC1196;December;https://www.rfc-editor.org/info/rfc1196 | |
| RFC1197;;Sherman, M.;Using ODA for translating multimedia information;;;;;RFC 1197;DOI 10.17487/RFC1197;December;https://www.rfc-editor.org/info/rfc1197 | |
| RFC1198;;Scheifler, R.;FYI on the X window system;;FYI 6;;;RFC 1198;DOI 10.17487/RFC1198;January;https://www.rfc-editor.org/info/rfc1198 | |
| RFC1199;;Reynolds, J.;Request for Comments Summary Notes: 1100-1199;;;;;RFC 1199;DOI 10.17487/RFC1199;December;https://www.rfc-editor.org/info/rfc1199 | |
| RFC1200;RFC1250;Defense Advanced Research Projects Agency and Internet Activities Board;IAB official protocol standards;;;;;RFC 1200;DOI 10.17487/RFC1200;April;https://www.rfc-editor.org/info/rfc1200 | |
| RFC1201;;Provan, D.;Transmitting IP traffic over ARCNET networks;;;;STD 46;RFC 1201;DOI 10.17487/RFC1201;February;https://www.rfc-editor.org/info/rfc1201 | |
| RFC1202;;Rose, M.;Directory Assistance service;;;;;RFC 1202;DOI 10.17487/RFC1202;February;https://www.rfc-editor.org/info/rfc1202 | |
| RFC1203;;Rice, J.;Interactive Mail Access Protocol: Version 3;;;;;RFC 1203;DOI 10.17487/RFC1203;February;https://www.rfc-editor.org/info/rfc1203 | |
| RFC1204;;Yeh, S. and D. Lee;Message Posting Protocol (MPP);;;;;RFC 1204;DOI 10.17487/RFC1204;February;https://www.rfc-editor.org/info/rfc1204 | |
| RFC1205;;Chmielewski, P.;5250 Telnet interface;;;;;RFC 1205;DOI 10.17487/RFC1205;February;https://www.rfc-editor.org/info/rfc1205 | |
| RFC1206;RFC1325;Malkin, G. and A. Marine;FYI on Questions and Answers: Answers to commonly asked "new Internet user" questions;;;;;RFC 1206;DOI 10.17487/RFC1206;February;https://www.rfc-editor.org/info/rfc1206 | |
| RFC1207;;Malkin, G., Marine, A., and J. Reynolds;FYI on Questions and Answers: Answers to commonly asked "experienced Internet user" questions;;FYI 7;;;RFC 1207;DOI 10.17487/RFC1207;February;https://www.rfc-editor.org/info/rfc1207 | |
| RFC1208;;Jacobsen, O. and D. Lynch;A Glossary of Networking Terms;;;;;RFC 1208;DOI 10.17487/RFC1208;March;https://www.rfc-editor.org/info/rfc1208 | |
| RFC1209;;Piscitello, D. and J. Lawrence;The Transmission of IP Datagrams over the SMDS Service;;;;STD 52;RFC 1209;DOI 10.17487/RFC1209;March;https://www.rfc-editor.org/info/rfc1209 | |
| RFC1210;;Cerf, V., Kirstein, P., and B. Randell;Network and infrastructure user requirements for transatlantic research collaboration: Brussels, July 16-18, and Washington July 24-25, 1990;;;;;RFC 1210;DOI 10.17487/RFC1210;March;https://www.rfc-editor.org/info/rfc1210 | |
| RFC1211;;Westine, A. and J. Postel;Problems with the maintenance of large mailing lists;;;;;RFC 1211;DOI 10.17487/RFC1211;March;https://www.rfc-editor.org/info/rfc1211 | |
| RFC1212;;Rose, M. and K. McCloghrie;Concise MIB definitions;;;;STD 16;RFC 1212;DOI 10.17487/RFC1212;March;https://www.rfc-editor.org/info/rfc1212 | |
| RFC1213;;McCloghrie, K. and M. Rose;Management Information Base for Network Management of TCP/IP-based internets: MIB-II;;;;STD 17;RFC 1213;DOI 10.17487/RFC1213;March;https://www.rfc-editor.org/info/rfc1213 | |
| RFC1214;;LaBarre, L.;OSI internet management: Management Information Base;;;;;RFC 1214;DOI 10.17487/RFC1214;April;https://www.rfc-editor.org/info/rfc1214 | |
| RFC1215;;Rose, M.;Convention for defining traps for use with the SNMP;;;;;RFC 1215;DOI 10.17487/RFC1215;March;https://www.rfc-editor.org/info/rfc1215 | |
| RFC1216;;Richard, P. and P. Kynikos;Gigabit network economics and paradigm shifts;;;;;RFC 1216;DOI 10.17487/RFC1216;April;https://www.rfc-editor.org/info/rfc1216 | |
| RFC1217;;Cerf, V.;Memo from the Consortium for Slow Commotion Research (CSCR);;;;;RFC 1217;DOI 10.17487/RFC1217;April;https://www.rfc-editor.org/info/rfc1217 | |
| RFC1218;RFC1255, RFC1417;North American Directory Forum;Naming scheme for c=US;;;;;RFC 1218;DOI 10.17487/RFC1218;April;https://www.rfc-editor.org/info/rfc1218 | |
| RFC1219;;Tsuchiya, P.;On the assignment of subnet numbers;;;;;RFC 1219;DOI 10.17487/RFC1219;April;https://www.rfc-editor.org/info/rfc1219 | |
| RFC1220;RFC1638;Baker, F.;Point-to-Point Protocol extensions for bridging;;;;;RFC 1220;DOI 10.17487/RFC1220;April;https://www.rfc-editor.org/info/rfc1220 | |
| RFC1221;;Edmond, W.;Host Access Protocol (HAP) specification: Version 2;;;;;RFC 1221;DOI 10.17487/RFC1221;April;https://www.rfc-editor.org/info/rfc1221 | |
| RFC1222;;Braun, H. and Y. Rekhter;Advancing the NSFNET routing architecture;;;;;RFC 1222;DOI 10.17487/RFC1222;May;https://www.rfc-editor.org/info/rfc1222 | |
| RFC1223;;Halpern, J.;OSI CLNS and LLC1 protocols on Network Systems HYPERchannel;;;;;RFC 1223;DOI 10.17487/RFC1223;May;https://www.rfc-editor.org/info/rfc1223 | |
| RFC1224;;Steinberg, L.;Techniques for managing asynchronously generated alerts;;;;;RFC 1224;DOI 10.17487/RFC1224;May;https://www.rfc-editor.org/info/rfc1224 | |
| RFC1225;RFC1460;Rose, M.;Post Office Protocol: Version 3;;;;;RFC 1225;DOI 10.17487/RFC1225;May;https://www.rfc-editor.org/info/rfc1225 | |
| RFC1226;;Kantor, B.;Internet protocol encapsulation of AX.25 frames;;;;;RFC 1226;DOI 10.17487/RFC1226;May;https://www.rfc-editor.org/info/rfc1226 | |
| RFC1227;;Rose, M.;SNMP MUX protocol and MIB;;;;;RFC 1227;DOI 10.17487/RFC1227;May;https://www.rfc-editor.org/info/rfc1227 | |
| RFC1228;RFC1592;Carpenter, G. and B. Wijnen;SNMP-DPI: Simple Network Management Protocol Distributed Program Interface;;;;;RFC 1228;DOI 10.17487/RFC1228;May;https://www.rfc-editor.org/info/rfc1228 | |
| RFC1229;RFC1573;McCloghrie, K.;Extensions to the generic-interface MIB;;;;;RFC 1229;DOI 10.17487/RFC1229;May;https://www.rfc-editor.org/info/rfc1229 | |
| RFC1230;;McCloghrie, K. and R. Fox;IEEE 802.4 Token Bus MIB;;;;;RFC 1230;DOI 10.17487/RFC1230;May;https://www.rfc-editor.org/info/rfc1230 | |
| RFC1231;RFC1743, RFC1748;McCloghrie, K., Fox, R., and E. Decker;IEEE 802.5 Token Ring MIB;;;;;RFC 1231;DOI 10.17487/RFC1231;May;https://www.rfc-editor.org/info/rfc1231 | |
| RFC1232;RFC1406;Baker, F. and C. Kolb;Definitions of managed objects for the DS1 Interface type;;;;;RFC 1232;DOI 10.17487/RFC1232;May;https://www.rfc-editor.org/info/rfc1232 | |
| RFC1233;RFC1407;Cox, T. and K. Tesink;Definitions of managed objects for the DS3 Interface type;;;;;RFC 1233;DOI 10.17487/RFC1233;May;https://www.rfc-editor.org/info/rfc1233 | |
| RFC1234;;Provan, D.;Tunneling IPX traffic through IP networks;;;;;RFC 1234;DOI 10.17487/RFC1234;June;https://www.rfc-editor.org/info/rfc1234 | |
| RFC1235;;Ioannidis, J. and G. Maguire;Coherent File Distribution Protocol;;;;;RFC 1235;DOI 10.17487/RFC1235;June;https://www.rfc-editor.org/info/rfc1235 | |
| RFC1236;;Morales, L. and P. Hasse;IP to X.121 address mapping for DDN;;;;;RFC 1236;DOI 10.17487/RFC1236;June;https://www.rfc-editor.org/info/rfc1236 | |
| RFC1237;RFC1629;Colella, R., Gardner, E., and R. Callon;Guidelines for OSI NSAP Allocation in the Internet;;;;;RFC 1237;DOI 10.17487/RFC1237;July;https://www.rfc-editor.org/info/rfc1237 | |
| RFC1238;;Satz, G.;CLNS MIB for use with Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542);;;;;RFC 1238;DOI 10.17487/RFC1238;June;https://www.rfc-editor.org/info/rfc1238 | |
| RFC1239;;Reynolds, J.;Reassignment of experimental MIBs to standard MIBs;;;;;RFC 1239;DOI 10.17487/RFC1239;June;https://www.rfc-editor.org/info/rfc1239 | |
| RFC1240;;Shue, C., Haggerty, W., and K. Dobbins;OSI connectionless transport services on top of UDP: Version 1;;;;;RFC 1240;DOI 10.17487/RFC1240;June;https://www.rfc-editor.org/info/rfc1240 | |
| RFC1241;;Woodburn, R. and D. Mills;Scheme for an internet encapsulation protocol: Version 1;;;;;RFC 1241;DOI 10.17487/RFC1241;July;https://www.rfc-editor.org/info/rfc1241 | |
| RFC1242;;Bradner, S.;Benchmarking Terminology for Network Interconnection Devices;;;;;RFC 1242;DOI 10.17487/RFC1242;July;https://www.rfc-editor.org/info/rfc1242 | |
| RFC1243;RFC1742;Waldbusser, S.;AppleTalk Management Information Base;;;;;RFC 1243;DOI 10.17487/RFC1243;July;https://www.rfc-editor.org/info/rfc1243 | |
| RFC1244;RFC2196;Holbrook, J. and J. Reynolds;Site Security Handbook;;;;;RFC 1244;DOI 10.17487/RFC1244;July;https://www.rfc-editor.org/info/rfc1244 | |
| RFC1245;;Moy, J.;OSPF Protocol Analysis;;;;;RFC 1245;DOI 10.17487/RFC1245;July;https://www.rfc-editor.org/info/rfc1245 | |
| RFC1246;;Moy, J.;Experience with the OSPF Protocol;;;;;RFC 1246;DOI 10.17487/RFC1246;July;https://www.rfc-editor.org/info/rfc1246 | |
| RFC1247;RFC1583;Moy, J.;OSPF Version 2;;;;;RFC 1247;DOI 10.17487/RFC1247;July;https://www.rfc-editor.org/info/rfc1247 | |
| RFC1248;RFC1252;Baker, F. and R. Coltun;OSPF Version 2 Management Information Base;;;;;RFC 1248;DOI 10.17487/RFC1248;July;https://www.rfc-editor.org/info/rfc1248 | |
| RFC1249;;Howes, T., Smith, M., and B. Beecher;DIXIE Protocol Specification;;;;;RFC 1249;DOI 10.17487/RFC1249;August;https://www.rfc-editor.org/info/rfc1249 | |
| RFC1250;RFC2200, RFC1280;Postel, J.;IAB Official Protocol Standards;;;;;RFC 1250;DOI 10.17487/RFC1250;August;https://www.rfc-editor.org/info/rfc1250 | |
| RFC1251;RFC1336;Malkin, G.;Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members;;;;;RFC 1251;DOI 10.17487/RFC1251;August;https://www.rfc-editor.org/info/rfc1251 | |
| RFC1252;RFC1253;Baker, F. and R. Coltun;OSPF Version 2 Management Information Base;;;;;RFC 1252;DOI 10.17487/RFC1252;August;https://www.rfc-editor.org/info/rfc1252 | |
| RFC1253;RFC1850;Baker, F. and R. Coltun;OSPF Version 2 Management Information Base;;;;;RFC 1253;DOI 10.17487/RFC1253;August;https://www.rfc-editor.org/info/rfc1253 | |
| RFC1254;;Mankin, A. and K. Ramakrishnan;Gateway Congestion Control Survey;;;;;RFC 1254;DOI 10.17487/RFC1254;August;https://www.rfc-editor.org/info/rfc1254 | |
| RFC1255;RFC1417;The North American Directory Forum;A Naming Scheme for c=US;;;;;RFC 1255;DOI 10.17487/RFC1255;September;https://www.rfc-editor.org/info/rfc1255 | |
| RFC1256;;Deering, S., Ed.;ICMP Router Discovery Messages;;;;;RFC 1256;DOI 10.17487/RFC1256;September;https://www.rfc-editor.org/info/rfc1256 | |
| RFC1257;;Partridge, C.;Isochronous applications do not require jitter-controlled networks;;;;;RFC 1257;DOI 10.17487/RFC1257;September;https://www.rfc-editor.org/info/rfc1257 | |
| RFC1258;RFC1282;Kantor, B.;BSD Rlogin;;;;;RFC 1258;DOI 10.17487/RFC1258;September;https://www.rfc-editor.org/info/rfc1258 | |
| RFC1259;;Kapor, M.;Building the open road: The NREN as test-bed for the national public network;;;;;RFC 1259;DOI 10.17487/RFC1259;September;https://www.rfc-editor.org/info/rfc1259 | |
| RFC1261;;Williamson, S. and L. Nobile;Transition of Nic Services;;;;;RFC 1261;DOI 10.17487/RFC1261;September;https://www.rfc-editor.org/info/rfc1261 | |
| RFC1262;;Cerf, V.;Guidelines for Internet Measurement Activities;;;;;RFC 1262;DOI 10.17487/RFC1262;October;https://www.rfc-editor.org/info/rfc1262 | |
| RFC1263;;O'Malley, S. and L. Peterson;TCP Extensions Considered Harmful;;;;;RFC 1263;DOI 10.17487/RFC1263;October;https://www.rfc-editor.org/info/rfc1263 | |
| RFC1264;RFC4794;Hinden, R.;Internet Engineering Task Force Internet Routing Protocol Standardization Criteria;;;;;RFC 1264;DOI 10.17487/RFC1264;October;https://www.rfc-editor.org/info/rfc1264 | |
| RFC1265;;Rekhter, Y.;BGP Protocol Analysis;;;;;RFC 1265;DOI 10.17487/RFC1265;October;https://www.rfc-editor.org/info/rfc1265 | |
| RFC1266;;Rekhter, Y.;Experience with the BGP Protocol;;;;;RFC 1266;DOI 10.17487/RFC1266;October;https://www.rfc-editor.org/info/rfc1266 | |
| RFC1267;;Lougheed, K. and Y. Rekhter;Border Gateway Protocol 3 (BGP-3);;;;;RFC 1267;DOI 10.17487/RFC1267;October;https://www.rfc-editor.org/info/rfc1267 | |
| RFC1268;RFC1655;Rekhter, Y. and P. Gross;Application of the Border Gateway Protocol in the Internet;;;;;RFC 1268;DOI 10.17487/RFC1268;October;https://www.rfc-editor.org/info/rfc1268 | |
| RFC1269;RFC4273;Willis, S. and J. Burruss;Definitions of Managed Objects for the Border Gateway Protocol: Version 3;;;;;RFC 1269;DOI 10.17487/RFC1269;October;https://www.rfc-editor.org/info/rfc1269 | |
| RFC1270;;Kastenholz, F.;SNMP Communications Services;;;;;RFC 1270;DOI 10.17487/RFC1270;October;https://www.rfc-editor.org/info/rfc1270 | |
| RFC1271;RFC1757;Waldbusser, S.;Remote Network Monitoring Management Information Base;;;;;RFC 1271;DOI 10.17487/RFC1271;November;https://www.rfc-editor.org/info/rfc1271 | |
| RFC1272;;Mills, C., Hirsh, D., and G. Ruth;Internet Accounting: Background;;;;;RFC 1272;DOI 10.17487/RFC1272;November;https://www.rfc-editor.org/info/rfc1272 | |
| RFC1273;;Schwartz, M.;Measurement Study of Changes in Service-Level Reachability in the Global TCP/IP Internet: Goals, Experimental Design, Implementation, and Policy Considerations;;;;;RFC 1273;DOI 10.17487/RFC1273;November;https://www.rfc-editor.org/info/rfc1273 | |
| RFC1274;RFC4524;Barker, P. and S. Kille;The COSINE and Internet X.500 Schema;;;;;RFC 1274;DOI 10.17487/RFC1274;November;https://www.rfc-editor.org/info/rfc1274 | |
| RFC1275;;Hardcastle-Kille, S.;Replication Requirements to provide an Internet Directory using X.500;;;;;RFC 1275;DOI 10.17487/RFC1275;November;https://www.rfc-editor.org/info/rfc1275 | |
| RFC1276;;Hardcastle-Kille, S.;Replication and Distributed Operations extensions to provide an Internet Directory using X.500;;;;;RFC 1276;DOI 10.17487/RFC1276;November;https://www.rfc-editor.org/info/rfc1276 | |
| RFC1277;;Hardcastle-Kille, S.;Encoding Network Addresses to Support Operation over Non-OSI Lower Layers;;;;;RFC 1277;DOI 10.17487/RFC1277;November;https://www.rfc-editor.org/info/rfc1277 | |
| RFC1278;;Hardcastle-Kille, S.;A string encoding of Presentation Address;;;;;RFC 1278;DOI 10.17487/RFC1278;November;https://www.rfc-editor.org/info/rfc1278 | |
| RFC1279;;Hardcastle-Kille, S.;X.500 and Domains;;;;;RFC 1279;DOI 10.17487/RFC1279;November;https://www.rfc-editor.org/info/rfc1279 | |
| RFC1280;RFC1360;Postel, J.;IAB Official Protocol Standards;;;;;RFC 1280;DOI 10.17487/RFC1280;March;https://www.rfc-editor.org/info/rfc1280 | |
| RFC1281;;Pethia, R., Crocker, S., and B. Fraser;Guidelines for the Secure Operation of the Internet;;;;;RFC 1281;DOI 10.17487/RFC1281;November;https://www.rfc-editor.org/info/rfc1281 | |
| RFC1282;;Kantor, B.;BSD Rlogin;;;;;RFC 1282;DOI 10.17487/RFC1282;December;https://www.rfc-editor.org/info/rfc1282 | |
| RFC1283;RFC1418;Rose, M.;SNMP over OSI;;;;;RFC 1283;DOI 10.17487/RFC1283;December;https://www.rfc-editor.org/info/rfc1283 | |
| RFC1284;RFC1398;Cook, J., Ed.;Definitions of Managed Objects for the Ethernet-like Interface Types;;;;;RFC 1284;DOI 10.17487/RFC1284;December;https://www.rfc-editor.org/info/rfc1284 | |
| RFC1285;;Case, J.;FDDI Management Information Base;;;;;RFC 1285;DOI 10.17487/RFC1285;January;https://www.rfc-editor.org/info/rfc1285 | |
| RFC1286;RFC1493, RFC1525;Decker, E., Langille, P., Rijsinghani, A., and K. McCloghrie;Definitions of Managed Objects for Bridges;;;;;RFC 1286;DOI 10.17487/RFC1286;December;https://www.rfc-editor.org/info/rfc1286 | |
| RFC1287;;Clark, D., Chapin, L., Cerf, V., Braden, R., and R. Hobby;Towards the Future Internet Architecture;;;;;RFC 1287;DOI 10.17487/RFC1287;December;https://www.rfc-editor.org/info/rfc1287 | |
| RFC1288;;Zimmerman, D.;The Finger User Information Protocol;;;;;RFC 1288;DOI 10.17487/RFC1288;December;https://www.rfc-editor.org/info/rfc1288 | |
| RFC1289;RFC1559;Saperia, J.;DECnet Phase IV MIB Extensions;;;;;RFC 1289;DOI 10.17487/RFC1289;December;https://www.rfc-editor.org/info/rfc1289 | |
| RFC1290;RFC1402;Martin, J.;There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places;;;;;RFC 1290;DOI 10.17487/RFC1290;December;https://www.rfc-editor.org/info/rfc1290 | |
| RFC1291;;Aggarwal, V.;Mid-Level Networks Potential Technical Services;;;;;RFC 1291;DOI 10.17487/RFC1291;December;https://www.rfc-editor.org/info/rfc1291 | |
| RFC1292;RFC1632;Lang, R. and R. Wright;A Catalog of Available X.500 Implementations;;;;;RFC 1292;DOI 10.17487/RFC1292;January;https://www.rfc-editor.org/info/rfc1292 | |
| RFC1293;RFC2390;Bradley, T. and C. Brown;Inverse Address Resolution Protocol;;;;;RFC 1293;DOI 10.17487/RFC1293;January;https://www.rfc-editor.org/info/rfc1293 | |
| RFC1294;RFC1490, RFC2427;Bradley, T., Brown, C., and A. Malis;Multiprotocol Interconnect over Frame Relay;;;;;RFC 1294;DOI 10.17487/RFC1294;January;https://www.rfc-editor.org/info/rfc1294 | |
| RFC1295;RFC1417;The North American Directory Forum;User Bill of Rights for entries and listings in the Public Directory;;;;;RFC 1295;DOI 10.17487/RFC1295;January;https://www.rfc-editor.org/info/rfc1295 | |
| RFC1296;;Lottor, M.;Internet Growth (1981-1991);;;;;RFC 1296;DOI 10.17487/RFC1296;January;https://www.rfc-editor.org/info/rfc1296 | |
| RFC1297;;Johnson, D.;NOC Internal Integrated Trouble Ticket System Functional Specification Wishlist ("NOC TT REQUIREMENTS");;;;;RFC 1297;DOI 10.17487/RFC1297;January;https://www.rfc-editor.org/info/rfc1297 | |
| RFC1298;RFC1420;Wormley, R. and S. Bostock;SNMP over IPX;;;;;RFC 1298;DOI 10.17487/RFC1298;February;https://www.rfc-editor.org/info/rfc1298 | |
| RFC1299;;Kennedy, M.;Summary of 1200-1299;;;;;RFC 1299;DOI 10.17487/RFC1299;January;https://www.rfc-editor.org/info/rfc1299 | |
| RFC1300;;Greenfield, S.;Remembrances of Things Past;;;;;RFC 1300;DOI 10.17487/RFC1300;February;https://www.rfc-editor.org/info/rfc1300 | |
| RFC1301;;Armstrong, S., Freier, A., and K. Marzullo;Multicast Transport Protocol;;;;;RFC 1301;DOI 10.17487/RFC1301;February;https://www.rfc-editor.org/info/rfc1301 | |
| RFC1302;;Sitzler, D., Smith, P., and A. Marine;Building a Network Information Services Infrastructure;;FYI 12;;;RFC 1302;DOI 10.17487/RFC1302;February;https://www.rfc-editor.org/info/rfc1302 | |
| RFC1303;;McCloghrie, K. and M. Rose;A Convention for Describing SNMP-based Agents;;;;;RFC 1303;DOI 10.17487/RFC1303;February;https://www.rfc-editor.org/info/rfc1303 | |
| RFC1304;RFC1694;Cox, T., Ed., and K. Tesink, Ed.;Definitions of Managed Objects for the SIP Interface Type;;;;;RFC 1304;DOI 10.17487/RFC1304;February;https://www.rfc-editor.org/info/rfc1304 | |
| RFC1305;RFC5905;Mills, D.;Network Time Protocol (Version 3) Specification, Implementation and Analysis;;;;;RFC 1305;DOI 10.17487/RFC1305;March;https://www.rfc-editor.org/info/rfc1305 | |
| RFC1306;;Nicholson, A. and J. Young;Experiences Supporting By-Request Circuit-Switched T3 Networks;;;;;RFC 1306;DOI 10.17487/RFC1306;March;https://www.rfc-editor.org/info/rfc1306 | |
| RFC1307;;Young, J. and A. Nicholson;Dynamically Switched Link Control Protocol;;;;;RFC 1307;DOI 10.17487/RFC1307;March;https://www.rfc-editor.org/info/rfc1307 | |
| RFC1308;;Weider, C. and J. Reynolds;Executive Introduction to Directory Services Using the X.500 Protocol;;FYI 13;;;RFC 1308;DOI 10.17487/RFC1308;March;https://www.rfc-editor.org/info/rfc1308 | |
| RFC1309;;Weider, C., Reynolds, J., and S. Heker;Technical Overview of Directory Services Using the X.500 Protocol;;FYI 14;;;RFC 1309;DOI 10.17487/RFC1309;March;https://www.rfc-editor.org/info/rfc1309 | |
| RFC1310;RFC1602;Chapin, L.;The Internet Standards Process;;;;;RFC 1310;DOI 10.17487/RFC1310;March;https://www.rfc-editor.org/info/rfc1310 | |
| RFC1311;;Postel, J.;Introduction to the STD Notes;;;;;RFC 1311;DOI 10.17487/RFC1311;March;https://www.rfc-editor.org/info/rfc1311 | |
| RFC1312;;Nelson, R. and G. Arnold;Message Send Protocol 2;;;;;RFC 1312;DOI 10.17487/RFC1312;April;https://www.rfc-editor.org/info/rfc1312 | |
| RFC1313;;Partridge, C.;Today's Programming for KRFC AM 1313 Internet Talk Radio;;;;;RFC 1313;DOI 10.17487/RFC1313;April;https://www.rfc-editor.org/info/rfc1313 | |
| RFC1314;;Katz, A. and D. Cohen;A File Format for the Exchange of Images in the Internet;;;;;RFC 1314;DOI 10.17487/RFC1314;April;https://www.rfc-editor.org/info/rfc1314 | |
| RFC1315;RFC2115;Brown, C., Baker, F., and C. Carvalho;Management Information Base for Frame Relay DTEs;;;;;RFC 1315;DOI 10.17487/RFC1315;April;https://www.rfc-editor.org/info/rfc1315 | |
| RFC1316;RFC1658;Stewart, B.;Definitions of Managed Objects for Character Stream Devices;;;;;RFC 1316;DOI 10.17487/RFC1316;April;https://www.rfc-editor.org/info/rfc1316 | |
| RFC1317;RFC1659;Stewart, B.;Definitions of Managed Objects for RS-232-like Hardware Devices;;;;;RFC 1317;DOI 10.17487/RFC1317;April;https://www.rfc-editor.org/info/rfc1317 | |
| RFC1318;RFC1660;Stewart, B.;Definitions of Managed Objects for Parallel-printer-like Hardware Devices;;;;;RFC 1318;DOI 10.17487/RFC1318;April;https://www.rfc-editor.org/info/rfc1318 | |
| RFC1319;RFC6149;Kaliski, B.;The MD2 Message-Digest Algorithm;;;;;RFC 1319;DOI 10.17487/RFC1319;April;https://www.rfc-editor.org/info/rfc1319 | |
| RFC1320;RFC6150;Rivest, R.;The MD4 Message-Digest Algorithm;;;;;RFC 1320;DOI 10.17487/RFC1320;April;https://www.rfc-editor.org/info/rfc1320 | |
| RFC1321;;Rivest, R.;The MD5 Message-Digest Algorithm;;;;;RFC 1321;DOI 10.17487/RFC1321;April;https://www.rfc-editor.org/info/rfc1321 | |
| RFC1322;;Estrin, D., Rekhter, Y., and S. Hotz;A Unified Approach to Inter-Domain Routing;;;;;RFC 1322;DOI 10.17487/RFC1322;May;https://www.rfc-editor.org/info/rfc1322 | |
| RFC1323;RFC7323;Jacobson, V., Braden, R., and D. Borman;TCP Extensions for High Performance;;;;;RFC 1323;DOI 10.17487/RFC1323;May;https://www.rfc-editor.org/info/rfc1323 | |
| RFC1324;;Reed, D.;A Discussion on Computer Network Conferencing;;;;;RFC 1324;DOI 10.17487/RFC1324;May;https://www.rfc-editor.org/info/rfc1324 | |
| RFC1325;RFC1594;Malkin, G. and A. Marine;FYI on Questions and Answers Answers to Commonly asked "New Internet User" Questions;;;;;RFC 1325;DOI 10.17487/RFC1325;May;https://www.rfc-editor.org/info/rfc1325 | |
| RFC1326;;Tsuchiya, P.;Mutual Encapsulation Considered Dangerous;;;;;RFC 1326;DOI 10.17487/RFC1326;May;https://www.rfc-editor.org/info/rfc1326 | |
| RFC1327;RFC2156;Hardcastle-Kille, S.;Mapping between X.400(1988) / ISO 10021 and RFC 822;;;;;RFC 1327;DOI 10.17487/RFC1327;May;https://www.rfc-editor.org/info/rfc1327 | |
| RFC1328;;Hardcastle-Kille, S.;X.400 1988 to 1984 downgrading;;;;;RFC 1328;DOI 10.17487/RFC1328;May;https://www.rfc-editor.org/info/rfc1328 | |
| RFC1329;;Kuehn, P.;Thoughts on Address Resolution for Dual MAC FDDI Networks;;;;;RFC 1329;DOI 10.17487/RFC1329;May;https://www.rfc-editor.org/info/rfc1329 | |
| RFC1330;;ESCC X.500/X.400 Task Force, ESnet Site Coordinating Comittee (ESCC), and Energy Sciences Network (ESnet);Recommendations for the Phase I Deployment of OSI Directory Services (X.500) and OSI Message Handling Services (X.400) within the ESNET Community;;;;;RFC 1330;DOI 10.17487/RFC1330;May;https://www.rfc-editor.org/info/rfc1330 | |
| RFC1331;RFC1548;Simpson, W.;The Point-to-Point Protocol (PPP) for the Transmission of Multi-protocol Datagrams over Point-to-Point Links;;;;;RFC 1331;DOI 10.17487/RFC1331;May;https://www.rfc-editor.org/info/rfc1331 | |
| RFC1332;;McGregor, G.;The PPP Internet Protocol Control Protocol (IPCP);;;;;RFC 1332;DOI 10.17487/RFC1332;May;https://www.rfc-editor.org/info/rfc1332 | |
| RFC1333;RFC1989;Simpson, W.;PPP Link Quality Monitoring;;;;;RFC 1333;DOI 10.17487/RFC1333;May;https://www.rfc-editor.org/info/rfc1333 | |
| RFC1334;RFC1994;Lloyd, B. and W. Simpson;PPP Authentication Protocols;;;;;RFC 1334;DOI 10.17487/RFC1334;October;https://www.rfc-editor.org/info/rfc1334 | |
| RFC1335;;Wang, Z. and J. Crowcroft;A Two-Tier Address Structure for the Internet: A Solution to the Problem of Address Space Exhaustion;;;;;RFC 1335;DOI 10.17487/RFC1335;May;https://www.rfc-editor.org/info/rfc1335 | |
| RFC1336;;Malkin, G.;Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members;;FYI 9;;;RFC 1336;DOI 10.17487/RFC1336;May;https://www.rfc-editor.org/info/rfc1336 | |
| RFC1337;;Braden, R.;TIME-WAIT Assassination Hazards in TCP;;;;;RFC 1337;DOI 10.17487/RFC1337;May;https://www.rfc-editor.org/info/rfc1337 | |
| RFC1338;RFC1519;Fuller, V., Li, T., Yu, J., and K. Varadhan;Supernetting: an Address Assignment and Aggregation Strategy;;;;;RFC 1338;DOI 10.17487/RFC1338;June;https://www.rfc-editor.org/info/rfc1338 | |
| RFC1339;;Dorner, S. and P. Resnick;Remote Mail Checking Protocol;;;;;RFC 1339;DOI 10.17487/RFC1339;June;https://www.rfc-editor.org/info/rfc1339 | |
| RFC1340;RFC1700;Reynolds, J. and J. Postel;Assigned Numbers;;;;;RFC 1340;DOI 10.17487/RFC1340;July;https://www.rfc-editor.org/info/rfc1340 | |
| RFC1341;RFC1521;Borenstein, N. and N. Freed;MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies;;;;;RFC 1341;DOI 10.17487/RFC1341;June;https://www.rfc-editor.org/info/rfc1341 | |
| RFC1342;RFC1522;Moore, K.;Representation of Non-ASCII Text in Internet Message Headers;;;;;RFC 1342;DOI 10.17487/RFC1342;June;https://www.rfc-editor.org/info/rfc1342 | |
| RFC1343;;Borenstein, N.;A User Agent Configuration Mechanism for Multimedia Mail Format Information;;;;;RFC 1343;DOI 10.17487/RFC1343;June;https://www.rfc-editor.org/info/rfc1343 | |
| RFC1344;;Borenstein, N.;Implications of MIME for Internet Mail Gateways;;;;;RFC 1344;DOI 10.17487/RFC1344;June;https://www.rfc-editor.org/info/rfc1344 | |
| RFC1345;;Simonsen, K.;Character Mnemonics and Character Sets;;;;;RFC 1345;DOI 10.17487/RFC1345;June;https://www.rfc-editor.org/info/rfc1345 | |
| RFC1346;;Jones, P.;Resource Allocation, Control, and Accounting for the Use of Network Resources;;;;;RFC 1346;DOI 10.17487/RFC1346;June;https://www.rfc-editor.org/info/rfc1346 | |
| RFC1347;;Callon, R.;TCP and UDP with Bigger Addresses (TUBA), A Simple Proposal for Internet Addressing and Routing;;;;;RFC 1347;DOI 10.17487/RFC1347;June;https://www.rfc-editor.org/info/rfc1347 | |
| RFC1348;RFC1637;Manning, B.;DNS NSAP RRs;;;;;RFC 1348;DOI 10.17487/RFC1348;July;https://www.rfc-editor.org/info/rfc1348 | |
| RFC1349;RFC2474;Almquist, P.;Type of Service in the Internet Protocol Suite;;;;;RFC 1349;DOI 10.17487/RFC1349;July;https://www.rfc-editor.org/info/rfc1349 | |
| RFC1350;;Sollins, K.;The TFTP Protocol (Revision 2);;;;STD 33;RFC 1350;DOI 10.17487/RFC1350;July;https://www.rfc-editor.org/info/rfc1350 | |
| RFC1351;;Davin, J., Galvin, J., and K. McCloghrie;SNMP Administrative Model;;;;;RFC 1351;DOI 10.17487/RFC1351;July;https://www.rfc-editor.org/info/rfc1351 | |
| RFC1352;;Galvin, J., McCloghrie, K., and J. Davin;SNMP Security Protocols;;;;;RFC 1352;DOI 10.17487/RFC1352;July;https://www.rfc-editor.org/info/rfc1352 | |
| RFC1353;;McCloghrie, K., Davin, J., and J. Galvin;Definitions of Managed Objects for Administration of SNMP Parties;;;;;RFC 1353;DOI 10.17487/RFC1353;July;https://www.rfc-editor.org/info/rfc1353 | |
| RFC1354;RFC2096;Baker, F.;IP Forwarding Table MIB;;;;;RFC 1354;DOI 10.17487/RFC1354;July;https://www.rfc-editor.org/info/rfc1354 | |
| RFC1355;;Curran, J. and A. Marine;Privacy and Accuracy Issues in Network Information Center Databases;;FYI 15;;;RFC 1355;DOI 10.17487/RFC1355;August;https://www.rfc-editor.org/info/rfc1355 | |
| RFC1356;;Malis, A., Robinson, D., and R. Ullmann;Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode;;;;;RFC 1356;DOI 10.17487/RFC1356;August;https://www.rfc-editor.org/info/rfc1356 | |
| RFC1357;RFC1807;Cohen, D.;A Format for E-mailing Bibliographic Records;;;;;RFC 1357;DOI 10.17487/RFC1357;July;https://www.rfc-editor.org/info/rfc1357 | |
| RFC1358;RFC1601;Chapin, L.;Charter of the Internet Architecture Board (IAB);;;;;RFC 1358;DOI 10.17487/RFC1358;August;https://www.rfc-editor.org/info/rfc1358 | |
| RFC1359;;ACM SIGUCCS;Connecting to the Internet - What Connecting Institutions Should Anticipate;;FYI 16;;;RFC 1359;DOI 10.17487/RFC1359;August;https://www.rfc-editor.org/info/rfc1359 | |
| RFC1360;RFC1410;Postel, J.;IAB Official Protocol Standards;;;;;RFC 1360;DOI 10.17487/RFC1360;September;https://www.rfc-editor.org/info/rfc1360 | |
| RFC1361;RFC1769;Mills, D.;Simple Network Time Protocol (SNTP);;;;;RFC 1361;DOI 10.17487/RFC1361;August;https://www.rfc-editor.org/info/rfc1361 | |
| RFC1362;RFC1634;Allen, M.;Novell IPX over Various WAN Media (IPXWAN);;;;;RFC 1362;DOI 10.17487/RFC1362;September;https://www.rfc-editor.org/info/rfc1362 | |
| RFC1363;;Partridge, C.;A Proposed Flow Specification;;;;;RFC 1363;DOI 10.17487/RFC1363;September;https://www.rfc-editor.org/info/rfc1363 | |
| RFC1364;RFC1403;Varadhan, K.;BGP OSPF Interaction;;;;;RFC 1364;DOI 10.17487/RFC1364;September;https://www.rfc-editor.org/info/rfc1364 | |
| RFC1365;;Siyan, K.;An IP Address Extension Proposal;;;;;RFC 1365;DOI 10.17487/RFC1365;September;https://www.rfc-editor.org/info/rfc1365 | |
| RFC1366;RFC1466;Gerich, E.;Guidelines for Management of IP Address Space;;;;;RFC 1366;DOI 10.17487/RFC1366;October;https://www.rfc-editor.org/info/rfc1366 | |
| RFC1367;RFC1467;Topolcic, C.;Schedule for IP Address Space Management Guidelines;;;;;RFC 1367;DOI 10.17487/RFC1367;October;https://www.rfc-editor.org/info/rfc1367 | |
| RFC1368;RFC1516;McMaster, D. and K. McCloghrie;Definition of Managed Objects for IEEE 802.3 Repeater Devices;;;;;RFC 1368;DOI 10.17487/RFC1368;October;https://www.rfc-editor.org/info/rfc1368 | |
| RFC1369;;Kastenholz, F.;Implementation Notes and Experience for the Internet Ethernet MIB;;;;;RFC 1369;DOI 10.17487/RFC1369;October;https://www.rfc-editor.org/info/rfc1369 | |
| RFC1370;;Internet Architecture Board and L. Chapin;Applicability Statement for OSPF;;;;;RFC 1370;DOI 10.17487/RFC1370;October;https://www.rfc-editor.org/info/rfc1370 | |
| RFC1371;;Gross, P.;Choosing a Common IGP for the IP Internet;;;;;RFC 1371;DOI 10.17487/RFC1371;October;https://www.rfc-editor.org/info/rfc1371 | |
| RFC1372;;Hedrick, C. and D. Borman;Telnet Remote Flow Control Option;;;;;RFC 1372;DOI 10.17487/RFC1372;October;https://www.rfc-editor.org/info/rfc1372 | |
| RFC1373;;Tignor, T.;Portable DUAs;;;;;RFC 1373;DOI 10.17487/RFC1373;October;https://www.rfc-editor.org/info/rfc1373 | |
| RFC1374;RFC2834;Renwick, J. and A. Nicholson;IP and ARP on HIPPI;;;;;RFC 1374;DOI 10.17487/RFC1374;October;https://www.rfc-editor.org/info/rfc1374 | |
| RFC1375;;Robinson, P.;Suggestion for New Classes of IP Addresses;;;;;RFC 1375;DOI 10.17487/RFC1375;October;https://www.rfc-editor.org/info/rfc1375 | |
| RFC1376;RFC1762;Senum, S.;The PPP DECnet Phase IV Control Protocol (DNCP);;;;;RFC 1376;DOI 10.17487/RFC1376;November;https://www.rfc-editor.org/info/rfc1376 | |
| RFC1377;;Katz, D.;The PPP OSI Network Layer Control Protocol (OSINLCP);;;;;RFC 1377;DOI 10.17487/RFC1377;November;https://www.rfc-editor.org/info/rfc1377 | |
| RFC1378;;Parker, B.;The PPP AppleTalk Control Protocol (ATCP);;;;;RFC 1378;DOI 10.17487/RFC1378;November;https://www.rfc-editor.org/info/rfc1378 | |
| RFC1379;RFC6247;Braden, R.;Extending TCP for Transactions -- Concepts;;;;;RFC 1379;DOI 10.17487/RFC1379;November;https://www.rfc-editor.org/info/rfc1379 | |
| RFC1380;;Gross, P. and P. Almquist;IESG Deliberations on Routing and Addressing;;;;;RFC 1380;DOI 10.17487/RFC1380;November;https://www.rfc-editor.org/info/rfc1380 | |
| RFC1381;;Throop, D. and F. Baker;SNMP MIB Extension for X.25 LAPB;;;;;RFC 1381;DOI 10.17487/RFC1381;November;https://www.rfc-editor.org/info/rfc1381 | |
| RFC1382;;Throop, D., Ed.;SNMP MIB Extension for the X.25 Packet Layer;;;;;RFC 1382;DOI 10.17487/RFC1382;November;https://www.rfc-editor.org/info/rfc1382 | |
| RFC1383;;Huitema, C.;An Experiment in DNS Based IP Routing;;;;;RFC 1383;DOI 10.17487/RFC1383;December;https://www.rfc-editor.org/info/rfc1383 | |
| RFC1384;RFC1617, RTR0011;Barker, P. and S. Hardcastle-Kille;Naming Guidelines for Directory Pilots;;;;;RFC 1384;DOI 10.17487/RFC1384;January;https://www.rfc-editor.org/info/rfc1384 | |
| RFC1385;RFC6814;Wang, Z.;EIP: The Extended Internet Protocol;;;;;RFC 1385;DOI 10.17487/RFC1385;November;https://www.rfc-editor.org/info/rfc1385 | |
| RFC1386;RFC1480;Cooper, A. and J. Postel;The US Domain;;;;;RFC 1386;DOI 10.17487/RFC1386;December;https://www.rfc-editor.org/info/rfc1386 | |
| RFC1387;RFC1721;Malkin, G.;RIP Version 2 Protocol Analysis;;;;;RFC 1387;DOI 10.17487/RFC1387;January;https://www.rfc-editor.org/info/rfc1387 | |
| RFC1388;RFC1723;Malkin, G.;RIP Version 2 Carrying Additional Information;;;;;RFC 1388;DOI 10.17487/RFC1388;January;https://www.rfc-editor.org/info/rfc1388 | |
| RFC1389;RFC1724;Malkin, G. and F. Baker;RIP Version 2 MIB Extensions;;;;;RFC 1389;DOI 10.17487/RFC1389;January;https://www.rfc-editor.org/info/rfc1389 | |
| RFC1390;;Katz, D.;Transmission of IP and ARP over FDDI Networks;;;;STD 36;RFC 1390;DOI 10.17487/RFC1390;January;https://www.rfc-editor.org/info/rfc1390 | |
| RFC1391;RFC1539;Malkin, G.;The Tao of the IETF: A Guide for New Attendees of the Internet Engineering Task Force;;;;;RFC 1391;DOI 10.17487/RFC1391;January;https://www.rfc-editor.org/info/rfc1391 | |
| RFC1392;RFC1983;Malkin, G. and T. LaQuey Parker;Internet Users' Glossary;;;;;RFC 1392;DOI 10.17487/RFC1392;January;https://www.rfc-editor.org/info/rfc1392 | |
| RFC1393;RFC6814;Malkin, G.;Traceroute Using an IP Option;;;;;RFC 1393;DOI 10.17487/RFC1393;January;https://www.rfc-editor.org/info/rfc1393 | |
| RFC1394;;Robinson, P.;Relationship of Telex Answerback Codes to Internet Domains;;;;;RFC 1394;DOI 10.17487/RFC1394;January;https://www.rfc-editor.org/info/rfc1394 | |
| RFC1395;RFC1497, RFC1533;Reynolds, J.;BOOTP Vendor Information Extensions;;;;;RFC 1395;DOI 10.17487/RFC1395;January;https://www.rfc-editor.org/info/rfc1395 | |
| RFC1396;;Crocker, S.;The Process for Organization of Internet Standards Working Group (POISED);;;;;RFC 1396;DOI 10.17487/RFC1396;January;https://www.rfc-editor.org/info/rfc1396 | |
| RFC1397;;Haskin, D.;Default Route Advertisement In BGP2 and BGP3 Version of The Border Gateway Protocol;;;;;RFC 1397;DOI 10.17487/RFC1397;January;https://www.rfc-editor.org/info/rfc1397 | |
| RFC1398;RFC1623;Kastenholz, F.;Definitions of Managed Objects for the Ethernet-Like Interface Types;;;;;RFC 1398;DOI 10.17487/RFC1398;January;https://www.rfc-editor.org/info/rfc1398 | |
| RFC1399;;Elliott, J.;Summary of 1300-1399;;;;;RFC 1399;DOI 10.17487/RFC1399;January;https://www.rfc-editor.org/info/rfc1399 | |
| RFC1400;;Williamson, S.;Transition and Modernization of the Internet Registration Service;;;;;RFC 1400;DOI 10.17487/RFC1400;March;https://www.rfc-editor.org/info/rfc1400 | |
| RFC1401;;Internet Architecture Board;Correspondence between the IAB and DISA on the use of DNS;;;;;RFC 1401;DOI 10.17487/RFC1401;January;https://www.rfc-editor.org/info/rfc1401 | |
| RFC1402;;Martin, J.;There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places;;FYI 10;;;RFC 1402;DOI 10.17487/RFC1402;January;https://www.rfc-editor.org/info/rfc1402 | |
| RFC1403;;Varadhan, K.;BGP OSPF Interaction;;;;;RFC 1403;DOI 10.17487/RFC1403;January;https://www.rfc-editor.org/info/rfc1403 | |
| RFC1404;RFC1857;Stockman, B.;A Model for Common Operational Statistics;;;;;RFC 1404;DOI 10.17487/RFC1404;January;https://www.rfc-editor.org/info/rfc1404 | |
| RFC1405;RFC2162;Allocchio, C.;Mapping between X.400(1984/1988) and Mail-11 (DECnet mail);;;;;RFC 1405;DOI 10.17487/RFC1405;January;https://www.rfc-editor.org/info/rfc1405 | |
| RFC1406;RFC2495;Baker, F., Ed., and J. Watt, Ed.;Definitions of Managed Objects for the DS1 and E1 Interface Types;;;;;RFC 1406;DOI 10.17487/RFC1406;January;https://www.rfc-editor.org/info/rfc1406 | |
| RFC1407;RFC2496;Cox, T. and K. Tesink;Definitions of Managed Objects for the DS3/E3 Interface Type;;;;;RFC 1407;DOI 10.17487/RFC1407;January;https://www.rfc-editor.org/info/rfc1407 | |
| RFC1408;;Borman, D., Ed.;Telnet Environment Option;;;;;RFC 1408;DOI 10.17487/RFC1408;January;https://www.rfc-editor.org/info/rfc1408 | |
| RFC1409;RFC1416;Borman, D., Ed.;Telnet Authentication Option;;;;;RFC 1409;DOI 10.17487/RFC1409;January;https://www.rfc-editor.org/info/rfc1409 | |
| RFC1410;RFC1500;Postel, J., Ed.;IAB Official Protocol Standards;;;;;RFC 1410;DOI 10.17487/RFC1410;March;https://www.rfc-editor.org/info/rfc1410 | |
| RFC1411;;Borman, D., Ed.;Telnet Authentication: Kerberos Version 4;;;;;RFC 1411;DOI 10.17487/RFC1411;January;https://www.rfc-editor.org/info/rfc1411 | |
| RFC1412;;Alagappan, K.;Telnet Authentication: SPX;;;;;RFC 1412;DOI 10.17487/RFC1412;January;https://www.rfc-editor.org/info/rfc1412 | |
| RFC1413;;St. Johns, M.;Identification Protocol;;;;;RFC 1413;DOI 10.17487/RFC1413;February;https://www.rfc-editor.org/info/rfc1413 | |
| RFC1414;;St. Johns, M. and M. Rose;Identification MIB;;;;;RFC 1414;DOI 10.17487/RFC1414;February;https://www.rfc-editor.org/info/rfc1414 | |
| RFC1415;;Mindel, J. and R. Slaski;FTP-FTAM Gateway Specification;;;;;RFC 1415;DOI 10.17487/RFC1415;January;https://www.rfc-editor.org/info/rfc1415 | |
| RFC1416;RFC2941;Borman, D., Ed.;Telnet Authentication Option;;;;;RFC 1416;DOI 10.17487/RFC1416;February;https://www.rfc-editor.org/info/rfc1416 | |
| RFC1417;RFC1758;The North American Directory Forum;NADF Standing Documents: A Brief Overview;;;;;RFC 1417;DOI 10.17487/RFC1417;February;https://www.rfc-editor.org/info/rfc1417 | |
| RFC1418;;Rose, M.;SNMP over OSI;;;;;RFC 1418;DOI 10.17487/RFC1418;March;https://www.rfc-editor.org/info/rfc1418 | |
| RFC1419;;Minshall, G. and M. Ritter;SNMP over AppleTalk;;;;;RFC 1419;DOI 10.17487/RFC1419;March;https://www.rfc-editor.org/info/rfc1419 | |
| RFC1420;;Bostock, S.;SNMP over IPX;;;;;RFC 1420;DOI 10.17487/RFC1420;March;https://www.rfc-editor.org/info/rfc1420 | |
| RFC1421;;Linn, J.;Privacy Enhancement for Internet Electronic Mail: Part I: Message Encryption and Authentication Procedures;;;;;RFC 1421;DOI 10.17487/RFC1421;February;https://www.rfc-editor.org/info/rfc1421 | |
| RFC1422;;Kent, S.;Privacy Enhancement for Internet Electronic Mail: Part II: Certificate-Based Key Management;;;;;RFC 1422;DOI 10.17487/RFC1422;February;https://www.rfc-editor.org/info/rfc1422 | |
| RFC1423;;Balenson, D.;Privacy Enhancement for Internet Electronic Mail: Part III: Algorithms, Modes, and Identifiers;;;;;RFC 1423;DOI 10.17487/RFC1423;February;https://www.rfc-editor.org/info/rfc1423 | |
| RFC1424;;Kaliski, B.;Privacy Enhancement for Internet Electronic Mail: Part IV: Key Certification and Related Services;;;;;RFC 1424;DOI 10.17487/RFC1424;February;https://www.rfc-editor.org/info/rfc1424 | |
| RFC1425;RFC1651;Klensin, J., Freed, N., Ed., Rose, M., Stefferud, E., and D. Crocker;SMTP Service Extensions;;;;;RFC 1425;DOI 10.17487/RFC1425;February;https://www.rfc-editor.org/info/rfc1425 | |
| RFC1426;RFC1652;Klensin, J., Freed, N., Ed., Rose, M., Stefferud, E., and D. Crocker;SMTP Service Extension for 8bit-MIMEtransport;;;;;RFC 1426;DOI 10.17487/RFC1426;February;https://www.rfc-editor.org/info/rfc1426 | |
| RFC1427;RFC1653;Klensin, J., Freed, N., Ed., and K. Moore;SMTP Service Extension for Message Size Declaration;;;;;RFC 1427;DOI 10.17487/RFC1427;February;https://www.rfc-editor.org/info/rfc1427 | |
| RFC1428;;Vaudreuil, G.;Transition of Internet Mail from Just-Send-8 to 8bit-SMTP/MIME;;;;;RFC 1428;DOI 10.17487/RFC1428;February;https://www.rfc-editor.org/info/rfc1428 | |
| RFC1429;;Thomas, E.;Listserv Distribute Protocol;;;;;RFC 1429;DOI 10.17487/RFC1429;February;https://www.rfc-editor.org/info/rfc1429 | |
| RFC1430;;Hardcastle-Kille, S., Huizer, E., Cerf, V., Hobby, R., and S. Kent;A Strategic Plan for Deploying an Internet X.500 Directory Service;;;;;RFC 1430;DOI 10.17487/RFC1430;February;https://www.rfc-editor.org/info/rfc1430 | |
| RFC1431;;Barker, P.;DUA Metrics (OSI-DS 33 (v2));;;;;RFC 1431;DOI 10.17487/RFC1431;February;https://www.rfc-editor.org/info/rfc1431 | |
| RFC1432;;Quarterman, J.;Recent Internet Books;;;;;RFC 1432;DOI 10.17487/RFC1432;March;https://www.rfc-editor.org/info/rfc1432 | |
| RFC1433;;Garrett, J., Hagan, J., and J. Wong;Directed ARP;;;;;RFC 1433;DOI 10.17487/RFC1433;March;https://www.rfc-editor.org/info/rfc1433 | |
| RFC1434;RFC1795;Dixon, R. and D. Kushi;Data Link Switching: Switch-to-Switch Protocol;;;;;RFC 1434;DOI 10.17487/RFC1434;March;https://www.rfc-editor.org/info/rfc1434 | |
| RFC1435;;Knowles, S.;IESG Advice from Experience with Path MTU Discovery;;;;;RFC 1435;DOI 10.17487/RFC1435;March;https://www.rfc-editor.org/info/rfc1435 | |
| RFC1436;;Anklesaria, F., McCahill, M., Lindner, P., Johnson, D., Torrey, D., and B. Albert;The Internet Gopher Protocol (a distributed document search and retrieval protocol);;;;;RFC 1436;DOI 10.17487/RFC1436;March;https://www.rfc-editor.org/info/rfc1436 | |
| RFC1437;;Borenstein, N. and M. Linimon;The Extension of MIME Content-Types to a New Medium;;;;;RFC 1437;DOI 10.17487/RFC1437;April;https://www.rfc-editor.org/info/rfc1437 | |
| RFC1438;;Lyman Chapin, A. and C. Huitema;Internet Engineering Task Force Statements Of Boredom (SOBs);;;;;RFC 1438;DOI 10.17487/RFC1438;April;https://www.rfc-editor.org/info/rfc1438 | |
| RFC1439;;Finseth, C.;The Uniqueness of Unique Identifiers;;;;;RFC 1439;DOI 10.17487/RFC1439;March;https://www.rfc-editor.org/info/rfc1439 | |
| RFC1440;;Troth, R.;SIFT/UFT: Sender-Initiated/Unsolicited File Transfer;;;;;RFC 1440;DOI 10.17487/RFC1440;July;https://www.rfc-editor.org/info/rfc1440 | |
| RFC1441;;Case, J., McCloghrie, K., Rose, M., and S. Waldbusser;Introduction to version 2 of the Internet-standard Network Management Framework;;;;;RFC 1441;DOI 10.17487/RFC1441;April;https://www.rfc-editor.org/info/rfc1441 | |
| RFC1442;RFC1902;Case, J., McCloghrie, K., Rose, M., and S. Waldbusser;Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2);;;;;RFC 1442;DOI 10.17487/RFC1442;April;https://www.rfc-editor.org/info/rfc1442 | |
| RFC1443;RFC1903;Case, J., McCloghrie, K., Rose, M., and S. Waldbusser;Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2);;;;;RFC 1443;DOI 10.17487/RFC1443;April;https://www.rfc-editor.org/info/rfc1443 | |
| RFC1444;RFC1904;Case, J., McCloghrie, K., Rose, M., and S. Waldbusser;Conformance Statements for version 2 of the Simple Network Management Protocol (SNMPv2);;;;;RFC 1444;DOI 10.17487/RFC1444;April;https://www.rfc-editor.org/info/rfc1444 | |
| RFC1445;;Galvin, J. and K. McCloghrie;Administrative Model for version 2 of the Simple Network Management Protocol (SNMPv2);;;;;RFC 1445;DOI 10.17487/RFC1445;April;https://www.rfc-editor.org/info/rfc1445 | |
| RFC1446;;Galvin, J. and K. McCloghrie;Security Protocols for version 2 of the Simple Network Management Protocol (SNMPv2);;;;;RFC 1446;DOI 10.17487/RFC1446;April;https://www.rfc-editor.org/info/rfc1446 | |
| RFC1447;;McCloghrie, K. and J. Galvin;Party MIB for version 2 of the Simple Network Management Protocol (SNMPv2);;;;;RFC 1447;DOI 10.17487/RFC1447;April;https://www.rfc-editor.org/info/rfc1447 | |
| RFC1448;RFC1905;Case, J., McCloghrie, K., Rose, M., and S. Waldbusser;Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2);;;;;RFC 1448;DOI 10.17487/RFC1448;April;https://www.rfc-editor.org/info/rfc1448 | |
| RFC1449;RFC1906;Case, J., McCloghrie, K., Rose, M., and S. Waldbusser;Transport Mappings for version 2 of the Simple Network Management Protocol (SNMPv2);;;;;RFC 1449;DOI 10.17487/RFC1449;April;https://www.rfc-editor.org/info/rfc1449 | |
| RFC1450;RFC1907;Case, J., McCloghrie, K., Rose, M., and S. Waldbusser;Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2);;;;;RFC 1450;DOI 10.17487/RFC1450;April;https://www.rfc-editor.org/info/rfc1450 | |
| RFC1451;;Case, J., McCloghrie, K., Rose, M., and S. Waldbusser;Manager-to-Manager Management Information Base;;;;;RFC 1451;DOI 10.17487/RFC1451;April;https://www.rfc-editor.org/info/rfc1451 | |
| RFC1452;RFC1908;Case, J., McCloghrie, K., Rose, M., and S. Waldbusser;Coexistence between version 1 and version 2 of the Internet-standard Network Management Framework;;;;;RFC 1452;DOI 10.17487/RFC1452;April;https://www.rfc-editor.org/info/rfc1452 | |
| RFC1453;;Chimiak, W.;A Comment on Packet Video Remote Conferencing and the Transport/Network Layers;;;;;RFC 1453;DOI 10.17487/RFC1453;April;https://www.rfc-editor.org/info/rfc1453 | |
| RFC1454;;Dixon, T.;Comparison of Proposals for Next Version of IP;;;;;RFC 1454;DOI 10.17487/RFC1454;May;https://www.rfc-editor.org/info/rfc1454 | |
| RFC1455;RFC2474;Eastlake 3rd, D.;Physical Link Security Type of Service;;;;;RFC 1455;DOI 10.17487/RFC1455;May;https://www.rfc-editor.org/info/rfc1455 | |
| RFC1456;;Vietnamese Standardization Working Group;Conventions for Encoding the Vietnamese Language VISCII: VIetnamese Standard Code for Information Interchange VIQR: VIetnamese Quoted-Readable Specification;;;;;RFC 1456;DOI 10.17487/RFC1456;May;https://www.rfc-editor.org/info/rfc1456 | |
| RFC1457;;Housley, R.;Security Label Framework for the Internet;;;;;RFC 1457;DOI 10.17487/RFC1457;May;https://www.rfc-editor.org/info/rfc1457 | |
| RFC1458;;Braudes, R. and S. Zabele;Requirements for Multicast Protocols;;;;;RFC 1458;DOI 10.17487/RFC1458;May;https://www.rfc-editor.org/info/rfc1458 | |
| RFC1459;;Oikarinen, J. and D. Reed;Internet Relay Chat Protocol;;;;;RFC 1459;DOI 10.17487/RFC1459;May;https://www.rfc-editor.org/info/rfc1459 | |
| RFC1460;RFC1725;Rose, M.;Post Office Protocol - Version 3;;;;;RFC 1460;DOI 10.17487/RFC1460;June;https://www.rfc-editor.org/info/rfc1460 | |
| RFC1461;;Throop, D.;SNMP MIB extension for Multiprotocol Interconnect over X.25;;;;;RFC 1461;DOI 10.17487/RFC1461;May;https://www.rfc-editor.org/info/rfc1461 | |
| RFC1462;;Krol, E. and E. Hoffman;FYI on "What is the Internet?";;FYI 20;;;RFC 1462;DOI 10.17487/RFC1462;May;https://www.rfc-editor.org/info/rfc1462 | |
| RFC1463;;Hoffman, E. and L. Jackson;FYI on Introducing the Internet-- A Short Bibliography of Introductory Internetworking Readings;;FYI 19;;;RFC 1463;DOI 10.17487/RFC1463;May;https://www.rfc-editor.org/info/rfc1463 | |
| RFC1464;;Rosenbaum, R.;Using the Domain Name System To Store Arbitrary String Attributes;;;;;RFC 1464;DOI 10.17487/RFC1464;May;https://www.rfc-editor.org/info/rfc1464 | |
| RFC1465;;Eppenberger, D.;Routing Coordination for X.400 MHS Services Within a Multi Protocol / Multi Network Environment Table Format V3 for Static Routing;;;;;RFC 1465;DOI 10.17487/RFC1465;May;https://www.rfc-editor.org/info/rfc1465 | |
| RFC1466;RFC2050;Gerich, E.;Guidelines for Management of IP Address Space;;;;;RFC 1466;DOI 10.17487/RFC1466;May;https://www.rfc-editor.org/info/rfc1466 | |
| RFC1467;;Topolcic, C.;Status of CIDR Deployment in the Internet;;;;;RFC 1467;DOI 10.17487/RFC1467;August;https://www.rfc-editor.org/info/rfc1467 | |
| RFC1468;;Murai, J., Crispin, M., and E. van der Poel;Japanese Character Encoding for Internet Messages;;;;;RFC 1468;DOI 10.17487/RFC1468;June;https://www.rfc-editor.org/info/rfc1468 | |
| RFC1469;;Pusateri, T.;IP Multicast over Token-Ring Local Area Networks;;;;;RFC 1469;DOI 10.17487/RFC1469;June;https://www.rfc-editor.org/info/rfc1469 | |
| RFC1470;;Enger, R. and J. Reynolds;FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices;;FYI 2;;;RFC 1470;DOI 10.17487/RFC1470;June;https://www.rfc-editor.org/info/rfc1470 | |
| RFC1471;;Kastenholz, F.;The Definitions of Managed Objects for the Link Control Protocol of the Point-to-Point Protocol;;;;;RFC 1471;DOI 10.17487/RFC1471;June;https://www.rfc-editor.org/info/rfc1471 | |
| RFC1472;;Kastenholz, F.;The Definitions of Managed Objects for the Security Protocols of the Point-to-Point Protocol;;;;;RFC 1472;DOI 10.17487/RFC1472;June;https://www.rfc-editor.org/info/rfc1472 | |
| RFC1473;;Kastenholz, F.;The Definitions of Managed Objects for the IP Network Control Protocol of the Point-to-Point Protocol;;;;;RFC 1473;DOI 10.17487/RFC1473;June;https://www.rfc-editor.org/info/rfc1473 | |
| RFC1474;;Kastenholz, F.;The Definitions of Managed Objects for the Bridge Network Control Protocol of the Point-to-Point Protocol;;;;;RFC 1474;DOI 10.17487/RFC1474;June;https://www.rfc-editor.org/info/rfc1474 | |
| RFC1475;RFC6814;Ullmann, R.;TP/IX: The Next Internet;;;;;RFC 1475;DOI 10.17487/RFC1475;June;https://www.rfc-editor.org/info/rfc1475 | |
| RFC1476;;Ullmann, R.;RAP: Internet Route Access Protocol;;;;;RFC 1476;DOI 10.17487/RFC1476;June;https://www.rfc-editor.org/info/rfc1476 | |
| RFC1477;;Steenstrup, M.;IDPR as a Proposed Standard;;;;;RFC 1477;DOI 10.17487/RFC1477;July;https://www.rfc-editor.org/info/rfc1477 | |
| RFC1478;;Steenstrup, M.;An Architecture for Inter-Domain Policy Routing;;;;;RFC 1478;DOI 10.17487/RFC1478;June;https://www.rfc-editor.org/info/rfc1478 | |
| RFC1479;;Steenstrup, M.;Inter-Domain Policy Routing Protocol Specification: Version 1;;;;;RFC 1479;DOI 10.17487/RFC1479;July;https://www.rfc-editor.org/info/rfc1479 | |
| RFC1480;;Cooper, A. and J. Postel;The US Domain;;;;;RFC 1480;DOI 10.17487/RFC1480;June;https://www.rfc-editor.org/info/rfc1480 | |
| RFC1481;;Huitema, C.;IAB Recommendation for an Intermediate Strategy to Address the Issue of Scaling;;;;;RFC 1481;DOI 10.17487/RFC1481;July;https://www.rfc-editor.org/info/rfc1481 | |
| RFC1482;;Knopper, M. and S. Richardson;Aggregation Support in the NSFNET Policy-Based Routing Database;;;;;RFC 1482;DOI 10.17487/RFC1482;June;https://www.rfc-editor.org/info/rfc1482 | |
| RFC1483;RFC2684;Juha Heinanen;Multiprotocol Encapsulation over ATM Adaptation Layer 5;;;;;RFC 1483;DOI 10.17487/RFC1483;July;https://www.rfc-editor.org/info/rfc1483 | |
| RFC1484;RFC1781, RFC3494;Hardcastle-Kille, S.;Using the OSI Directory to achieve User Friendly Naming (OSI-DS 24 (v1.2));;;;;RFC 1484;DOI 10.17487/RFC1484;July;https://www.rfc-editor.org/info/rfc1484 | |
| RFC1485;RFC1779, RFC3494;Hardcastle-Kille, S.;A String Representation of Distinguished Names (OSI-DS 23 (v5));;;;;RFC 1485;DOI 10.17487/RFC1485;July;https://www.rfc-editor.org/info/rfc1485 | |
| RFC1486;RFC1528, RFC1529;Rose, M. and C. Malamud;An Experiment in Remote Printing;;;;;RFC 1486;DOI 10.17487/RFC1486;July;https://www.rfc-editor.org/info/rfc1486 | |
| RFC1487;RFC1777, RFC3494;Yeong, W., Howes, T., and S. Kille;X.500 Lightweight Directory Access Protocol;;;;;RFC 1487;DOI 10.17487/RFC1487;July;https://www.rfc-editor.org/info/rfc1487 | |
| RFC1488;RFC1778;Howes, T., Kille, S., Yeong, W., and C. Robbins;The X.500 String Representation of Standard Attribute Syntaxes;;;;;RFC 1488;DOI 10.17487/RFC1488;July;https://www.rfc-editor.org/info/rfc1488 | |
| RFC1489;;Chernov, A.;Registration of a Cyrillic Character Set;;;;;RFC 1489;DOI 10.17487/RFC1489;July;https://www.rfc-editor.org/info/rfc1489 | |
| RFC1490;RFC2427;Bradley, T., Brown, C., and A. Malis;Multiprotocol Interconnect over Frame Relay;;;;;RFC 1490;DOI 10.17487/RFC1490;July;https://www.rfc-editor.org/info/rfc1490 | |
| RFC1491;;Weider, C. and R. Wright;A Survey of Advanced Usages of X.500;;FYI 21;;;RFC 1491;DOI 10.17487/RFC1491;July;https://www.rfc-editor.org/info/rfc1491 | |
| RFC1492;;Finseth, C.;An Access Control Protocol, Sometimes Called TACACS;;;;;RFC 1492;DOI 10.17487/RFC1492;July;https://www.rfc-editor.org/info/rfc1492 | |
| RFC1493;RFC4188;Decker, E., Langille, P., Rijsinghani, A., and K. McCloghrie;Definitions of Managed Objects for Bridges;;;;;RFC 1493;DOI 10.17487/RFC1493;July;https://www.rfc-editor.org/info/rfc1493 | |
| RFC1494;;Alvestrand, H. and S. Thompson;Equivalences between 1988 X.400 and RFC-822 Message Bodies;;;;;RFC 1494;DOI 10.17487/RFC1494;August;https://www.rfc-editor.org/info/rfc1494 | |
| RFC1495;RFC2156;Alvestrand, H., Kille, S., Miles, R., Rose, M., and S. Thompson;Mapping between X.400 and RFC-822 Message Bodies;;;;;RFC 1495;DOI 10.17487/RFC1495;August;https://www.rfc-editor.org/info/rfc1495 | |
| RFC1496;;Alvestrand, H., Romaguera, J., and K. Jordan;Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messages;;;;;RFC 1496;DOI 10.17487/RFC1496;August;https://www.rfc-editor.org/info/rfc1496 | |
| RFC1497;RFC1533;Reynolds, J.;BOOTP Vendor Information Extensions;;;;;RFC 1497;DOI 10.17487/RFC1497;August;https://www.rfc-editor.org/info/rfc1497 | |
| RFC1498;;Saltzer, J.;On the Naming and Binding of Network Destinations;;;;;RFC 1498;DOI 10.17487/RFC1498;August;https://www.rfc-editor.org/info/rfc1498 | |
| RFC1499;;Elliott, J.;Summary of 1400-1499;;;;;RFC 1499;DOI 10.17487/RFC1499;January;https://www.rfc-editor.org/info/rfc1499 | |
| RFC1500;RFC1540;Postel, J.;Internet Official Protocol Standards;;;;;RFC 1500;DOI 10.17487/RFC1500;August;https://www.rfc-editor.org/info/rfc1500 | |
| RFC1501;;Brunsen, E.;OS/2 User Group;;;;;RFC 1501;DOI 10.17487/RFC1501;August;https://www.rfc-editor.org/info/rfc1501 | |
| RFC1502;;Alvestrand, H.;X.400 Use of Extended Character Sets;;;;;RFC 1502;DOI 10.17487/RFC1502;August;https://www.rfc-editor.org/info/rfc1502 | |
| RFC1503;;McCloghrie, K. and M. Rose;Algorithms for Automating Administration in SNMPv2 Managers;;;;;RFC 1503;DOI 10.17487/RFC1503;August;https://www.rfc-editor.org/info/rfc1503 | |
| RFC1504;;Oppenheimer, A.;Appletalk Update-Based Routing Protocol: Enhanced Appletalk Routing;;;;;RFC 1504;DOI 10.17487/RFC1504;August;https://www.rfc-editor.org/info/rfc1504 | |
| RFC1505;;Costanzo, A., Robinson, D., and R. Ullmann;Encoding Header Field for Internet Messages;;;;;RFC 1505;DOI 10.17487/RFC1505;August;https://www.rfc-editor.org/info/rfc1505 | |
| RFC1506;;Houttuin, J.;A Tutorial on Gatewaying between X.400 and Internet Mail;;;;;RFC 1506;DOI 10.17487/RFC1506;August;https://www.rfc-editor.org/info/rfc1506 | |
| RFC1507;;Kaufman, C.;DASS - Distributed Authentication Security Service;;;;;RFC 1507;DOI 10.17487/RFC1507;September;https://www.rfc-editor.org/info/rfc1507 | |
| RFC1508;RFC2078;Linn, J.;Generic Security Service Application Program Interface;;;;;RFC 1508;DOI 10.17487/RFC1508;September;https://www.rfc-editor.org/info/rfc1508 | |
| RFC1509;RFC2744;Wray, J.;Generic Security Service API : C-bindings;;;;;RFC 1509;DOI 10.17487/RFC1509;September;https://www.rfc-editor.org/info/rfc1509 | |
| RFC1510;RFC4120, RFC6649;Kohl, J. and C. Neuman;The Kerberos Network Authentication Service (V5);;;;;RFC 1510;DOI 10.17487/RFC1510;September;https://www.rfc-editor.org/info/rfc1510 | |
| RFC1511;;Linn, J.;Common Authentication Technology Overview;;;;;RFC 1511;DOI 10.17487/RFC1511;September;https://www.rfc-editor.org/info/rfc1511 | |
| RFC1512;;Case, J. and A. Rijsinghani;FDDI Management Information Base;;;;;RFC 1512;DOI 10.17487/RFC1512;September;https://www.rfc-editor.org/info/rfc1512 | |
| RFC1513;;Waldbusser, S.;Token Ring Extensions to the Remote Network Monitoring MIB;;;;;RFC 1513;DOI 10.17487/RFC1513;September;https://www.rfc-editor.org/info/rfc1513 | |
| RFC1514;RFC2790;Grillo, P. and S. Waldbusser;Host Resources MIB;;;;;RFC 1514;DOI 10.17487/RFC1514;September;https://www.rfc-editor.org/info/rfc1514 | |
| RFC1515;RFC3636;McMaster, D., McCloghrie, K., and S. Roberts;Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs);;;;;RFC 1515;DOI 10.17487/RFC1515;September;https://www.rfc-editor.org/info/rfc1515 | |
| RFC1516;RFC2108;McMaster, D. and K. McCloghrie;Definitions of Managed Objects for IEEE 802.3 Repeater Devices;;;;;RFC 1516;DOI 10.17487/RFC1516;September;https://www.rfc-editor.org/info/rfc1516 | |
| RFC1517;;Internet Engineering Steering Group and R. Hinden;Applicability Statement for the Implementation of Classless Inter-Domain Routing (CIDR);;;;;RFC 1517;DOI 10.17487/RFC1517;September;https://www.rfc-editor.org/info/rfc1517 | |
| RFC1518;;Rekhter, Y. and T. Li;An Architecture for IP Address Allocation with CIDR;;;;;RFC 1518;DOI 10.17487/RFC1518;September;https://www.rfc-editor.org/info/rfc1518 | |
| RFC1519;RFC4632;Fuller, V., Li, T., Yu, J., and K. Varadhan;Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy;;;;;RFC 1519;DOI 10.17487/RFC1519;September;https://www.rfc-editor.org/info/rfc1519 | |
| RFC1520;;Rekhter, Y. and C. Topolcic;Exchanging Routing Information Across Provider Boundaries in the CIDR Environment;;;;;RFC 1520;DOI 10.17487/RFC1520;September;https://www.rfc-editor.org/info/rfc1520 | |
| RFC1521;RFC2045, RFC2046, RFC2047, RFC2048, RFC2049;Borenstein, N. and N. Freed;MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies;;;;;RFC 1521;DOI 10.17487/RFC1521;September;https://www.rfc-editor.org/info/rfc1521 | |
| RFC1522;RFC2045, RFC2046, RFC2047, RFC2048, RFC2049;Moore, K.;MIME (Multipurpose Internet Mail Extensions) Part Two: Message Header Extensions for Non-ASCII Text;;;;;RFC 1522;DOI 10.17487/RFC1522;September;https://www.rfc-editor.org/info/rfc1522 | |
| RFC1523;RFC1563, RFC1896;Borenstein, N.;The text/enriched MIME Content-type;;;;;RFC 1523;DOI 10.17487/RFC1523;September;https://www.rfc-editor.org/info/rfc1523 | |
| RFC1524;;Borenstein, N.;A User Agent Configuration Mechanism For Multimedia Mail Format Information;;;;;RFC 1524;DOI 10.17487/RFC1524;September;https://www.rfc-editor.org/info/rfc1524 | |
| RFC1525;;Decker, E., McCloghrie, K., Langille, P., and A. Rijsinghani;Definitions of Managed Objects for Source Routing Bridges;;;;;RFC 1525;DOI 10.17487/RFC1525;September;https://www.rfc-editor.org/info/rfc1525 | |
| RFC1526;;Piscitello, D.;Assignment of System Identifiers for TUBA/CLNP Hosts;;;;;RFC 1526;DOI 10.17487/RFC1526;September;https://www.rfc-editor.org/info/rfc1526 | |
| RFC1527;;Cook, G.;What Should We Plan Given the Dilemma of the Network?;;;;;RFC 1527;DOI 10.17487/RFC1527;September;https://www.rfc-editor.org/info/rfc1527 | |
| RFC1528;;Malamud, C. and M. Rose;Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Technical Procedures;;;;;RFC 1528;DOI 10.17487/RFC1528;October;https://www.rfc-editor.org/info/rfc1528 | |
| RFC1529;;Malamud, C. and M. Rose;Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Administrative Policies;;;;;RFC 1529;DOI 10.17487/RFC1529;October;https://www.rfc-editor.org/info/rfc1529 | |
| RFC1530;;Malamud, C. and M. Rose;Principles of Operation for the TPC.INT Subdomain: General Principles and Policy;;;;;RFC 1530;DOI 10.17487/RFC1530;October;https://www.rfc-editor.org/info/rfc1530 | |
| RFC1531;RFC1541;Droms, R.;Dynamic Host Configuration Protocol;;;;;RFC 1531;DOI 10.17487/RFC1531;October;https://www.rfc-editor.org/info/rfc1531 | |
| RFC1532;RFC1542;Wimer, W.;Clarifications and Extensions for the Bootstrap Protocol;;;;;RFC 1532;DOI 10.17487/RFC1532;October;https://www.rfc-editor.org/info/rfc1532 | |
| RFC1533;RFC2132;Alexander, S. and R. Droms;DHCP Options and BOOTP Vendor Extensions;;;;;RFC 1533;DOI 10.17487/RFC1533;October;https://www.rfc-editor.org/info/rfc1533 | |
| RFC1534;;Droms, R.;Interoperation Between DHCP and BOOTP;;;;;RFC 1534;DOI 10.17487/RFC1534;October;https://www.rfc-editor.org/info/rfc1534 | |
| RFC1535;;Gavron, E.;A Security Problem and Proposed Correction With Widely Deployed DNS Software;;;;;RFC 1535;DOI 10.17487/RFC1535;October;https://www.rfc-editor.org/info/rfc1535 | |
| RFC1536;;Kumar, A., Postel, J., Neuman, C., Danzig, P., and S. Miller;Common DNS Implementation Errors and Suggested Fixes;;;;;RFC 1536;DOI 10.17487/RFC1536;October;https://www.rfc-editor.org/info/rfc1536 | |
| RFC1537;RFC1912;Beertema, P.;Common DNS Data File Configuration Errors;;;;;RFC 1537;DOI 10.17487/RFC1537;October;https://www.rfc-editor.org/info/rfc1537 | |
| RFC1538;;Behl, W., Sterling, B., and W. Teskey;Advanced SNA/IP : A Simple SNA Transport Protocol;;;;;RFC 1538;DOI 10.17487/RFC1538;October;https://www.rfc-editor.org/info/rfc1538 | |
| RFC1539;RFC1718;Malkin, G.;The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force;;;;;RFC 1539;DOI 10.17487/RFC1539;October;https://www.rfc-editor.org/info/rfc1539 | |
| RFC1540;RFC1600;Postel, J.;Internet Official Protocol Standards;;;;;RFC 1540;DOI 10.17487/RFC1540;October;https://www.rfc-editor.org/info/rfc1540 | |
| RFC1541;RFC2131;Droms, R.;Dynamic Host Configuration Protocol;;;;;RFC 1541;DOI 10.17487/RFC1541;October;https://www.rfc-editor.org/info/rfc1541 | |
| RFC1542;;Wimer, W.;Clarifications and Extensions for the Bootstrap Protocol;;;;;RFC 1542;DOI 10.17487/RFC1542;October;https://www.rfc-editor.org/info/rfc1542 | |
| RFC1543;RFC2223;Postel, J.;Instructions to RFC Authors;;;;;RFC 1543;DOI 10.17487/RFC1543;October;https://www.rfc-editor.org/info/rfc1543 | |
| RFC1544;RFC1864;Rose, M.;The Content-MD5 Header Field;;;;;RFC 1544;DOI 10.17487/RFC1544;November;https://www.rfc-editor.org/info/rfc1544 | |
| RFC1545;RFC1639;Piscitello, D.;FTP Operation Over Big Address Records (FOOBAR);;;;;RFC 1545;DOI 10.17487/RFC1545;November;https://www.rfc-editor.org/info/rfc1545 | |
| RFC1546;;Partridge, C., Mendez, T., and W. Milliken;Host Anycasting Service;;;;;RFC 1546;DOI 10.17487/RFC1546;November;https://www.rfc-editor.org/info/rfc1546 | |
| RFC1547;;Perkins, D.;Requirements for an Internet Standard Point-to-Point Protocol;;;;;RFC 1547;DOI 10.17487/RFC1547;December;https://www.rfc-editor.org/info/rfc1547 | |
| RFC1548;RFC1661;Simpson, W.;The Point-to-Point Protocol (PPP);;;;;RFC 1548;DOI 10.17487/RFC1548;December;https://www.rfc-editor.org/info/rfc1548 | |
| RFC1549;RFC1662;Simpson, W., Ed.;PPP in HDLC Framing;;;;;RFC 1549;DOI 10.17487/RFC1549;December;https://www.rfc-editor.org/info/rfc1549 | |
| RFC1550;;Bradner, S. and A. Mankin;IP: Next Generation (IPng) White Paper Solicitation;;;;;RFC 1550;DOI 10.17487/RFC1550;December;https://www.rfc-editor.org/info/rfc1550 | |
| RFC1551;RFC1634;Allen, M.;Novell IPX Over Various WAN Media (IPXWAN);;;;;RFC 1551;DOI 10.17487/RFC1551;December;https://www.rfc-editor.org/info/rfc1551 | |
| RFC1552;;Simpson, W.;The PPP Internetworking Packet Exchange Control Protocol (IPXCP);;;;;RFC 1552;DOI 10.17487/RFC1552;December;https://www.rfc-editor.org/info/rfc1552 | |
| RFC1553;;Mathur, S. and M. Lewis;Compressing IPX Headers Over WAN Media (CIPX);;;;;RFC 1553;DOI 10.17487/RFC1553;December;https://www.rfc-editor.org/info/rfc1553 | |
| RFC1554;;Ohta, M. and K. Handa;ISO-2022-JP-2: Multilingual Extension of ISO-2022-JP;;;;;RFC 1554;DOI 10.17487/RFC1554;December;https://www.rfc-editor.org/info/rfc1554 | |
| RFC1555;;Nussbacher, H. and Y. Bourvine;Hebrew Character Encoding for Internet Messages;;;;;RFC 1555;DOI 10.17487/RFC1555;December;https://www.rfc-editor.org/info/rfc1555 | |
| RFC1556;;Nussbacher, H.;Handling of Bi-directional Texts in MIME;;;;;RFC 1556;DOI 10.17487/RFC1556;December;https://www.rfc-editor.org/info/rfc1556 | |
| RFC1557;;Choi, U., Chon, K., and H. Park;Korean Character Encoding for Internet Messages;;;;;RFC 1557;DOI 10.17487/RFC1557;December;https://www.rfc-editor.org/info/rfc1557 | |
| RFC1558;RFC1960;Howes, T.;A String Representation of LDAP Search Filters;;;;;RFC 1558;DOI 10.17487/RFC1558;December;https://www.rfc-editor.org/info/rfc1558 | |
| RFC1559;;Saperia, J.;DECnet Phase IV MIB Extensions;;;;;RFC 1559;DOI 10.17487/RFC1559;December;https://www.rfc-editor.org/info/rfc1559 | |
| RFC1560;;Leiner, B. and Y. Rekhter;The MultiProtocol Internet;;;;;RFC 1560;DOI 10.17487/RFC1560;December;https://www.rfc-editor.org/info/rfc1560 | |
| RFC1561;;Piscitello, D.;Use of ISO CLNP in TUBA Environments;;;;;RFC 1561;DOI 10.17487/RFC1561;December;https://www.rfc-editor.org/info/rfc1561 | |
| RFC1562;;Michaelson, G. and M. Prior;Naming Guidelines for the AARNet X.500 Directory Service;;;;;RFC 1562;DOI 10.17487/RFC1562;December;https://www.rfc-editor.org/info/rfc1562 | |
| RFC1563;RFC1896;Borenstein, N.;The text/enriched MIME Content-type;;;;;RFC 1563;DOI 10.17487/RFC1563;January;https://www.rfc-editor.org/info/rfc1563 | |
| RFC1564;;Barker, P. and R. Hedberg;DSA Metrics (OSI-DS 34 (v3));;;;;RFC 1564;DOI 10.17487/RFC1564;January;https://www.rfc-editor.org/info/rfc1564 | |
| RFC1565;RFC2248;Kille, S. and N. Freed;Network Services Monitoring MIB;;;;;RFC 1565;DOI 10.17487/RFC1565;January;https://www.rfc-editor.org/info/rfc1565 | |
| RFC1566;RFC2249, RFC2789;Kille, S. and N. Freed;Mail Monitoring MIB;;;;;RFC 1566;DOI 10.17487/RFC1566;January;https://www.rfc-editor.org/info/rfc1566 | |
| RFC1567;RFC2605;Mansfield, G. and S. Kille;X.500 Directory Monitoring MIB;;;;;RFC 1567;DOI 10.17487/RFC1567;January;https://www.rfc-editor.org/info/rfc1567 | |
| RFC1568;RFC1645;Gwinn, A.;Simple Network Paging Protocol - Version 1(b);;;;;RFC 1568;DOI 10.17487/RFC1568;January;https://www.rfc-editor.org/info/rfc1568 | |
| RFC1569;RFC1703;Rose, M.;Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical Procedures;;;;;RFC 1569;DOI 10.17487/RFC1569;January;https://www.rfc-editor.org/info/rfc1569 | |
| RFC1570;;Simpson, W., Ed.;PPP LCP Extensions;;;;;RFC 1570;DOI 10.17487/RFC1570;January;https://www.rfc-editor.org/info/rfc1570 | |
| RFC1571;;Borman, D.;Telnet Environment Option Interoperability Issues;;;;;RFC 1571;DOI 10.17487/RFC1571;January;https://www.rfc-editor.org/info/rfc1571 | |
| RFC1572;;Alexander, S., Ed.;Telnet Environment Option;;;;;RFC 1572;DOI 10.17487/RFC1572;January;https://www.rfc-editor.org/info/rfc1572 | |
| RFC1573;RFC2233;McCloghrie, K. and F. Kastenholz;Evolution of the Interfaces Group of MIB-II;;;;;RFC 1573;DOI 10.17487/RFC1573;January;https://www.rfc-editor.org/info/rfc1573 | |
| RFC1574;;Hares, S. and C. Wittbrodt;Essential Tools for the OSI Internet;;;;;RFC 1574;DOI 10.17487/RFC1574;February;https://www.rfc-editor.org/info/rfc1574 | |
| RFC1575;;Hares, S. and C. Wittbrodt;An Echo Function for CLNP (ISO 8473);;;;;RFC 1575;DOI 10.17487/RFC1575;February;https://www.rfc-editor.org/info/rfc1575 | |
| RFC1576;;Penner, J.;TN3270 Current Practices;;;;;RFC 1576;DOI 10.17487/RFC1576;January;https://www.rfc-editor.org/info/rfc1576 | |
| RFC1577;RFC2225;Laubach, M.;Classical IP and ARP over ATM;;;;;RFC 1577;DOI 10.17487/RFC1577;January;https://www.rfc-editor.org/info/rfc1577 | |
| RFC1578;RFC1941;Sellers, J.;FYI on Questions and Answers - Answers to Commonly Asked "Primary and Secondary School Internet User" Questions;;;;;RFC 1578;DOI 10.17487/RFC1578;February;https://www.rfc-editor.org/info/rfc1578 | |
| RFC1579;;Bellovin, S.;Firewall-Friendly FTP;;;;;RFC 1579;DOI 10.17487/RFC1579;February;https://www.rfc-editor.org/info/rfc1579 | |
| RFC1580;;EARN Staff;Guide to Network Resource Tools;;FYI 23;;;RFC 1580;DOI 10.17487/RFC1580;March;https://www.rfc-editor.org/info/rfc1580 | |
| RFC1581;;Meyer, G.;Protocol Analysis for Extensions to RIP to Support Demand Circuits;;;;;RFC 1581;DOI 10.17487/RFC1581;February;https://www.rfc-editor.org/info/rfc1581 | |
| RFC1582;;Meyer, G.;Extensions to RIP to Support Demand Circuits;;;;;RFC 1582;DOI 10.17487/RFC1582;February;https://www.rfc-editor.org/info/rfc1582 | |
| RFC1583;RFC2178;Moy, J.;OSPF Version 2;;;;;RFC 1583;DOI 10.17487/RFC1583;March;https://www.rfc-editor.org/info/rfc1583 | |
| RFC1584;;Moy, J.;Multicast Extensions to OSPF;;;;;RFC 1584;DOI 10.17487/RFC1584;March;https://www.rfc-editor.org/info/rfc1584 | |
| RFC1585;;Moy, J.;MOSPF: Analysis and Experience;;;;;RFC 1585;DOI 10.17487/RFC1585;March;https://www.rfc-editor.org/info/rfc1585 | |
| RFC1586;;deSouza, O. and M. Rodrigues;Guidelines for Running OSPF Over Frame Relay Networks;;;;;RFC 1586;DOI 10.17487/RFC1586;March;https://www.rfc-editor.org/info/rfc1586 | |
| RFC1587;RFC3101;Coltun, R. and V. Fuller;The OSPF NSSA Option;;;;;RFC 1587;DOI 10.17487/RFC1587;March;https://www.rfc-editor.org/info/rfc1587 | |
| RFC1588;;Postel, J. and C. Anderson;White Pages Meeting Report;;;;;RFC 1588;DOI 10.17487/RFC1588;February;https://www.rfc-editor.org/info/rfc1588 | |
| RFC1589;;Mills, D.;A Kernel Model for Precision Timekeeping;;;;;RFC 1589;DOI 10.17487/RFC1589;March;https://www.rfc-editor.org/info/rfc1589 | |
| RFC1590;RFC2045, RFC2046, RFC2047, RFC2048, RFC2049;Postel, J.;Media Type Registration Procedure;;;;;RFC 1590;DOI 10.17487/RFC1590;March;https://www.rfc-editor.org/info/rfc1590 | |
| RFC1591;;Postel, J.;Domain Name System Structure and Delegation;;;;;RFC 1591;DOI 10.17487/RFC1591;March;https://www.rfc-editor.org/info/rfc1591 | |
| RFC1592;;Wijnen, B., Carpenter, G., Curran, K., Sehgal, A., and G. Waters;Simple Network Management Protocol Distributed Protocol Interface Version 2.0;;;;;RFC 1592;DOI 10.17487/RFC1592;March;https://www.rfc-editor.org/info/rfc1592 | |
| RFC1593;;McKenzie, W. and J. Cheng;SNA APPN Node MIB;;;;;RFC 1593;DOI 10.17487/RFC1593;March;https://www.rfc-editor.org/info/rfc1593 | |
| RFC1594;RFC2664;Marine, A., Reynolds, J., and G. Malkin;FYI on Questions and Answers - Answers to Commonly asked "New Internet User" Questions;;;;;RFC 1594;DOI 10.17487/RFC1594;March;https://www.rfc-editor.org/info/rfc1594 | |
| RFC1595;RFC2558;Brown, T. and K. Tesink;Definitions of Managed Objects for the SONET/SDH Interface Type;;;;;RFC 1595;DOI 10.17487/RFC1595;March;https://www.rfc-editor.org/info/rfc1595 | |
| RFC1596;RFC1604;Brown, T., Ed.;Definitions of Managed Objects for Frame Relay Service;;;;;RFC 1596;DOI 10.17487/RFC1596;March;https://www.rfc-editor.org/info/rfc1596 | |
| RFC1597;RFC1918;Rekhter, Y., Moskowitz, B., Karrenberg, D., and G. de Groot;Address Allocation for Private Internets;;;;;RFC 1597;DOI 10.17487/RFC1597;March;https://www.rfc-editor.org/info/rfc1597 | |
| RFC1598;;Simpson, W.;PPP in X.25;;;;;RFC 1598;DOI 10.17487/RFC1598;March;https://www.rfc-editor.org/info/rfc1598 | |
| RFC1599;;Kennedy, M.;Summary of 1500-1599;;;;;RFC 1599;DOI 10.17487/RFC1599;January;https://www.rfc-editor.org/info/rfc1599 | |
| RFC1600;RFC1610;Postel, J.;Internet Official Protocol Standards;;;;;RFC 1600;DOI 10.17487/RFC1600;March;https://www.rfc-editor.org/info/rfc1600 | |
| RFC1601;RFC2850;Huitema, C.;Charter of the Internet Architecture Board (IAB);;;;;RFC 1601;DOI 10.17487/RFC1601;March;https://www.rfc-editor.org/info/rfc1601 | |
| RFC1602;RFC2026;Internet Architecture Board and Internet Engineering Steering Group;The Internet Standards Process -- Revision 2;;;;;RFC 1602;DOI 10.17487/RFC1602;March;https://www.rfc-editor.org/info/rfc1602 | |
| RFC1603;RFC2418;Huizer, E. and D. Crocker;IETF Working Group Guidelines and Procedures;;;;;RFC 1603;DOI 10.17487/RFC1603;March;https://www.rfc-editor.org/info/rfc1603 | |
| RFC1604;RFC2954;Brown, T., Ed.;Definitions of Managed Objects for Frame Relay Service;;;;;RFC 1604;DOI 10.17487/RFC1604;March;https://www.rfc-editor.org/info/rfc1604 | |
| RFC1605;;Shakespeare, W.;SONET to Sonnet Translation;;;;;RFC 1605;DOI 10.17487/RFC1605;April;https://www.rfc-editor.org/info/rfc1605 | |
| RFC1606;;Onions, J.;A Historical Perspective On The Usage Of IP Version 9;;;;;RFC 1606;DOI 10.17487/RFC1606;April;https://www.rfc-editor.org/info/rfc1606 | |
| RFC1607;;Cerf, V.;A VIEW FROM THE 21ST CENTURY;;;;;RFC 1607;DOI 10.17487/RFC1607;April;https://www.rfc-editor.org/info/rfc1607 | |
| RFC1608;;Johannsen, T., Mansfield, G., Kosters, M., and S. Sataluri;Representing IP Information in the X.500 Directory;;;;;RFC 1608;DOI 10.17487/RFC1608;March;https://www.rfc-editor.org/info/rfc1608 | |
| RFC1609;;Mansfield, G., Johannsen, T., and M. Knopper;Charting Networks in the X.500 Directory;;;;;RFC 1609;DOI 10.17487/RFC1609;March;https://www.rfc-editor.org/info/rfc1609 | |
| RFC1610;RFC1720;Postel, J.;Internet Official Protocol Standards;;;;;RFC 1610;DOI 10.17487/RFC1610;July;https://www.rfc-editor.org/info/rfc1610 | |
| RFC1611;;Austein, R. and J. Saperia;DNS Server MIB Extensions;;;;;RFC 1611;DOI 10.17487/RFC1611;May;https://www.rfc-editor.org/info/rfc1611 | |
| RFC1612;;Austein, R. and J. Saperia;DNS Resolver MIB Extensions;;;;;RFC 1612;DOI 10.17487/RFC1612;May;https://www.rfc-editor.org/info/rfc1612 | |
| RFC1613;;Forster, J., Satz, G., Glick, G., and R. Day;cisco Systems X.25 over TCP (XOT);;;;;RFC 1613;DOI 10.17487/RFC1613;May;https://www.rfc-editor.org/info/rfc1613 | |
| RFC1614;;Adie, C.;Network Access to Multimedia Information;;;;;RFC 1614;DOI 10.17487/RFC1614;May;https://www.rfc-editor.org/info/rfc1614 | |
| RFC1615;;Houttuin, J. and J. Craigie;Migrating from X.400(84) to X.400(88);;;;;RFC 1615;DOI 10.17487/RFC1615;May;https://www.rfc-editor.org/info/rfc1615 | |
| RFC1616;;RARE WG-MSG Task Force 88, Huizer, E., Ed., and J. Romaguera, Ed.;X.400(1988) for the Academic and Research Community in Europe;;;;;RFC 1616;DOI 10.17487/RFC1616;May;https://www.rfc-editor.org/info/rfc1616 | |
| RFC1617;;Barker, P., Kille, S., and T. Lenggenhager;Naming and Structuring Guidelines for X.500 Directory Pilots;;;;;RFC 1617;DOI 10.17487/RFC1617;May;https://www.rfc-editor.org/info/rfc1617 | |
| RFC1618;;Simpson, W.;PPP over ISDN;;;;;RFC 1618;DOI 10.17487/RFC1618;May;https://www.rfc-editor.org/info/rfc1618 | |
| RFC1619;RFC2615;Simpson, W.;PPP over SONET/SDH;;;;;RFC 1619;DOI 10.17487/RFC1619;May;https://www.rfc-editor.org/info/rfc1619 | |
| RFC1620;;Braden, B., Postel, J., and Y. Rekhter;Internet Architecture Extensions for Shared Media;;;;;RFC 1620;DOI 10.17487/RFC1620;May;https://www.rfc-editor.org/info/rfc1620 | |
| RFC1621;;Francis, P.;Pip Near-term Architecture;;;;;RFC 1621;DOI 10.17487/RFC1621;May;https://www.rfc-editor.org/info/rfc1621 | |
| RFC1622;;Francis, P.;Pip Header Processing;;;;;RFC 1622;DOI 10.17487/RFC1622;May;https://www.rfc-editor.org/info/rfc1622 | |
| RFC1623;RFC1643;Kastenholz, F.;Definitions of Managed Objects for the Ethernet-like Interface Types;;;;;RFC 1623;DOI 10.17487/RFC1623;May;https://www.rfc-editor.org/info/rfc1623 | |
| RFC1624;;Rijsinghani, A., Ed.;Computation of the Internet Checksum via Incremental Update;;;;;RFC 1624;DOI 10.17487/RFC1624;May;https://www.rfc-editor.org/info/rfc1624 | |
| RFC1625;;St. Pierre, M., Fullton, J., Gamiel, K., Goldman, J., Kahle, B., Kunze, J., Morris, H., and F. Schiettecatte;WAIS over Z39.50-1988;;;;;RFC 1625;DOI 10.17487/RFC1625;June;https://www.rfc-editor.org/info/rfc1625 | |
| RFC1626;RFC2225;Atkinson, R.;Default IP MTU for use over ATM AAL5;;;;;RFC 1626;DOI 10.17487/RFC1626;May;https://www.rfc-editor.org/info/rfc1626 | |
| RFC1627;RFC1918;Lear, E., Fair, E., Crocker, D., and T. Kessler;Network 10 Considered Harmful (Some Practices Shouldn't be Codified);;;;;RFC 1627;DOI 10.17487/RFC1627;July;https://www.rfc-editor.org/info/rfc1627 | |
| RFC1628;;Case, J., Ed.;UPS Management Information Base;;;;;RFC 1628;DOI 10.17487/RFC1628;May;https://www.rfc-editor.org/info/rfc1628 | |
| RFC1629;;Colella, R., Callon, R., Gardner, E., and Y. Rekhter;Guidelines for OSI NSAP Allocation in the Internet;;;;;RFC 1629;DOI 10.17487/RFC1629;May;https://www.rfc-editor.org/info/rfc1629 | |
| RFC1630;;Berners-Lee, T.;Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web;;;;;RFC 1630;DOI 10.17487/RFC1630;June;https://www.rfc-editor.org/info/rfc1630 | |
| RFC1631;RFC3022;Egevang, K. and P. Francis;The IP Network Address Translator (NAT);;;;;RFC 1631;DOI 10.17487/RFC1631;May;https://www.rfc-editor.org/info/rfc1631 | |
| RFC1632;RFC2116;Getchell, A., Ed., and S. Sataluri, Ed.;A Revised Catalog of Available X.500 Implementations;;;;;RFC 1632;DOI 10.17487/RFC1632;May;https://www.rfc-editor.org/info/rfc1632 | |
| RFC1633;;Braden, R., Clark, D., and S. Shenker;Integrated Services in the Internet Architecture: an Overview;;;;;RFC 1633;DOI 10.17487/RFC1633;June;https://www.rfc-editor.org/info/rfc1633 | |
| RFC1634;;Allen, M.;Novell IPX Over Various WAN Media (IPXWAN);;;;;RFC 1634;DOI 10.17487/RFC1634;May;https://www.rfc-editor.org/info/rfc1634 | |
| RFC1635;;Deutsch, P., Emtage, A., and A. Marine;How to Use Anonymous FTP;;FYI 24;;;RFC 1635;DOI 10.17487/RFC1635;May;https://www.rfc-editor.org/info/rfc1635 | |
| RFC1636;;Braden, R., Clark, D., Crocker, S., and C. Huitema;Report of IAB Workshop on Security in the Internet Architecture - February 8-10, 1994;;;;;RFC 1636;DOI 10.17487/RFC1636;June;https://www.rfc-editor.org/info/rfc1636 | |
| RFC1637;RFC1706;Manning, B. and R. Colella;DNS NSAP Resource Records;;;;;RFC 1637;DOI 10.17487/RFC1637;June;https://www.rfc-editor.org/info/rfc1637 | |
| RFC1638;RFC2878;Baker, F. and R. Bowen;PPP Bridging Control Protocol (BCP);;;;;RFC 1638;DOI 10.17487/RFC1638;June;https://www.rfc-editor.org/info/rfc1638 | |
| RFC1639;;Piscitello, D.;FTP Operation Over Big Address Records (FOOBAR);;;;;RFC 1639;DOI 10.17487/RFC1639;June;https://www.rfc-editor.org/info/rfc1639 | |
| RFC1640;;Crocker, S.;The Process for Organization of Internet Standards Working Group (POISED);;;;;RFC 1640;DOI 10.17487/RFC1640;June;https://www.rfc-editor.org/info/rfc1640 | |
| RFC1641;;Goldsmith, D. and M. Davis;Using Unicode with MIME;;;;;RFC 1641;DOI 10.17487/RFC1641;July;https://www.rfc-editor.org/info/rfc1641 | |
| RFC1642;RFC2152;Goldsmith, D. and M. Davis;UTF-7 - A Mail-Safe Transformation Format of Unicode;;;;;RFC 1642;DOI 10.17487/RFC1642;July;https://www.rfc-editor.org/info/rfc1642 | |
| RFC1643;RFC3638;Kastenholz, F.;Definitions of Managed Objects for the Ethernet-like Interface Types;;;;;RFC 1643;DOI 10.17487/RFC1643;July;https://www.rfc-editor.org/info/rfc1643 | |
| RFC1644;RFC6247;Braden, R.;T/TCP -- TCP Extensions for Transactions Functional Specification;;;;;RFC 1644;DOI 10.17487/RFC1644;July;https://www.rfc-editor.org/info/rfc1644 | |
| RFC1645;RFC1861;Gwinn, A.;Simple Network Paging Protocol - Version 2;;;;;RFC 1645;DOI 10.17487/RFC1645;July;https://www.rfc-editor.org/info/rfc1645 | |
| RFC1646;;Graves, C., Butts, T., and M. Angel;TN3270 Extensions for LUname and Printer Selection;;;;;RFC 1646;DOI 10.17487/RFC1646;July;https://www.rfc-editor.org/info/rfc1646 | |
| RFC1647;RFC2355;Kelly, B.;TN3270 Enhancements;;;;;RFC 1647;DOI 10.17487/RFC1647;July;https://www.rfc-editor.org/info/rfc1647 | |
| RFC1648;;Cargille, A.;Postmaster Convention for X.400 Operations;;;;;RFC 1648;DOI 10.17487/RFC1648;July;https://www.rfc-editor.org/info/rfc1648 | |
| RFC1649;;Hagens, R. and A. Hansen;Operational Requirements for X.400 Management Domains in the GO-MHS Community;;;;;RFC 1649;DOI 10.17487/RFC1649;July;https://www.rfc-editor.org/info/rfc1649 | |
| RFC1650;RFC2358;Kastenholz, F.;Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2;;;;;RFC 1650;DOI 10.17487/RFC1650;August;https://www.rfc-editor.org/info/rfc1650 | |
| RFC1651;RFC1869;Klensin, J., Freed, N., Rose, M., Stefferud, E., and D. Crocker;SMTP Service Extensions;;;;;RFC 1651;DOI 10.17487/RFC1651;July;https://www.rfc-editor.org/info/rfc1651 | |
| RFC1652;RFC6152;Klensin, J., Freed, N., Rose, M., Stefferud, E., and D. Crocker;SMTP Service Extension for 8bit-MIMEtransport;;;;;RFC 1652;DOI 10.17487/RFC1652;July;https://www.rfc-editor.org/info/rfc1652 | |
| RFC1653;RFC1870;Klensin, J., Freed, N., and K. Moore;SMTP Service Extension for Message Size Declaration;;;;;RFC 1653;DOI 10.17487/RFC1653;July;https://www.rfc-editor.org/info/rfc1653 | |
| RFC1654;RFC1771;Rekhter, Y., Ed., and T. Li, Ed.;A Border Gateway Protocol 4 (BGP-4);;;;;RFC 1654;DOI 10.17487/RFC1654;July;https://www.rfc-editor.org/info/rfc1654 | |
| RFC1655;RFC1772;Rekhter, Y., Ed., and P. Gross, Ed.;Application of the Border Gateway Protocol in the Internet;;;;;RFC 1655;DOI 10.17487/RFC1655;July;https://www.rfc-editor.org/info/rfc1655 | |
| RFC1656;RFC1773;Traina, P.;BGP-4 Protocol Document Roadmap and Implementation Experience;;;;;RFC 1656;DOI 10.17487/RFC1656;July;https://www.rfc-editor.org/info/rfc1656 | |
| RFC1657;RFC4273;Willis, S., Burruss, J., and J. Chu, Ed.;Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2;;;;;RFC 1657;DOI 10.17487/RFC1657;July;https://www.rfc-editor.org/info/rfc1657 | |
| RFC1658;;Stewart, B.;Definitions of Managed Objects for Character Stream Devices using SMIv2;;;;;RFC 1658;DOI 10.17487/RFC1658;July;https://www.rfc-editor.org/info/rfc1658 | |
| RFC1659;;Stewart, B.;Definitions of Managed Objects for RS-232-like Hardware Devices using SMIv2;;;;;RFC 1659;DOI 10.17487/RFC1659;July;https://www.rfc-editor.org/info/rfc1659 | |
| RFC1660;;Stewart, B.;Definitions of Managed Objects for Parallel-printer-like Hardware Devices using SMIv2;;;;;RFC 1660;DOI 10.17487/RFC1660;July;https://www.rfc-editor.org/info/rfc1660 | |
| RFC1661;;Simpson, W., Ed.;The Point-to-Point Protocol (PPP);;;;STD 51;RFC 1661;DOI 10.17487/RFC1661;July;https://www.rfc-editor.org/info/rfc1661 | |
| RFC1662;;Simpson, W., Ed.;PPP in HDLC-like Framing;;;;STD 51;RFC 1662;DOI 10.17487/RFC1662;July;https://www.rfc-editor.org/info/rfc1662 | |
| RFC1663;;Rand, D.;PPP Reliable Transmission;;;;;RFC 1663;DOI 10.17487/RFC1663;July;https://www.rfc-editor.org/info/rfc1663 | |
| RFC1664;RFC2163;Allocchio, C., Bonito, A., Cole, B., Giordano, S., and R. Hagens;Using the Internet DNS to Distribute RFC1327 Mail Address Mapping Tables;;;;;RFC 1664;DOI 10.17487/RFC1664;August;https://www.rfc-editor.org/info/rfc1664 | |
| RFC1665;RFC1666;Kielczewski, Z., Ed., Kostick, D., Ed., and K. Shih, Ed.;Definitions of Managed Objects for SNA NAUs using SMIv2;;;;;RFC 1665;DOI 10.17487/RFC1665;July;https://www.rfc-editor.org/info/rfc1665 | |
| RFC1666;;Kielczewski, Z., Ed., Kostick, D., Ed., and K. Shih, Ed.;Definitions of Managed Objects for SNA NAUs using SMIv2;;;;;RFC 1666;DOI 10.17487/RFC1666;August;https://www.rfc-editor.org/info/rfc1666 | |
| RFC1667;;Symington, S., Wood, D., and M. Pullen;Modeling and Simulation Requirements for IPng;;;;;RFC 1667;DOI 10.17487/RFC1667;August;https://www.rfc-editor.org/info/rfc1667 | |
| RFC1668;;Estrin, D., Li, T., and Y. Rekhter;Unified Routing Requirements for IPng;;;;;RFC 1668;DOI 10.17487/RFC1668;August;https://www.rfc-editor.org/info/rfc1668 | |
| RFC1669;;Curran, J.;Market Viability as a IPng Criteria;;;;;RFC 1669;DOI 10.17487/RFC1669;August;https://www.rfc-editor.org/info/rfc1669 | |
| RFC1670;;Heagerty, D.;Input to IPng Engineering Considerations;;;;;RFC 1670;DOI 10.17487/RFC1670;August;https://www.rfc-editor.org/info/rfc1670 | |
| RFC1671;;Carpenter, B.;IPng White Paper on Transition and Other Considerations;;;;;RFC 1671;DOI 10.17487/RFC1671;August;https://www.rfc-editor.org/info/rfc1671 | |
| RFC1672;;Brownlee, N.;Accounting Requirements for IPng;;;;;RFC 1672;DOI 10.17487/RFC1672;August;https://www.rfc-editor.org/info/rfc1672 | |
| RFC1673;;Skelton, R.;Electric Power Research Institute Comments on IPng;;;;;RFC 1673;DOI 10.17487/RFC1673;August;https://www.rfc-editor.org/info/rfc1673 | |
| RFC1674;;Taylor, M.;A Cellular Industry View of IPng;;;;;RFC 1674;DOI 10.17487/RFC1674;August;https://www.rfc-editor.org/info/rfc1674 | |
| RFC1675;;Bellovin, S.;Security Concerns for IPng;;;;;RFC 1675;DOI 10.17487/RFC1675;August;https://www.rfc-editor.org/info/rfc1675 | |
| RFC1676;;Ghiselli, A., Salomoni, D., and C. Vistoli;INFN Requirements for an IPng;;;;;RFC 1676;DOI 10.17487/RFC1676;August;https://www.rfc-editor.org/info/rfc1676 | |
| RFC1677;;Adamson, B.;Tactical Radio Frequency Communication Requirements for IPng;;;;;RFC 1677;DOI 10.17487/RFC1677;August;https://www.rfc-editor.org/info/rfc1677 | |
| RFC1678;;Britton, E. and J. Tavs;IPng Requirements of Large Corporate Networks;;;;;RFC 1678;DOI 10.17487/RFC1678;August;https://www.rfc-editor.org/info/rfc1678 | |
| RFC1679;;Green, D., Irey, P., Marlow, D., and K. O'Donoghue;HPN Working Group Input to the IPng Requirements Solicitation;;;;;RFC 1679;DOI 10.17487/RFC1679;August;https://www.rfc-editor.org/info/rfc1679 | |
| RFC1680;;Brazdziunas, C.;IPng Support for ATM Services;;;;;RFC 1680;DOI 10.17487/RFC1680;August;https://www.rfc-editor.org/info/rfc1680 | |
| RFC1681;;Bellovin, S.;On Many Addresses per Host;;;;;RFC 1681;DOI 10.17487/RFC1681;August;https://www.rfc-editor.org/info/rfc1681 | |
| RFC1682;;Bound, J.;IPng BSD Host Implementation Analysis;;;;;RFC 1682;DOI 10.17487/RFC1682;August;https://www.rfc-editor.org/info/rfc1682 | |
| RFC1683;;Clark, R., Ammar, M., and K. Calvert;Multiprotocol Interoperability In IPng;;;;;RFC 1683;DOI 10.17487/RFC1683;August;https://www.rfc-editor.org/info/rfc1683 | |
| RFC1684;;Jurg, P.;Introduction to White Pages Services based on X.500;;;;;RFC 1684;DOI 10.17487/RFC1684;August;https://www.rfc-editor.org/info/rfc1684 | |
| RFC1685;;Alvestrand, H.;Writing X.400 O/R Names;RTR 12;;;;RFC 1685;DOI 10.17487/RFC1685;August;https://www.rfc-editor.org/info/rfc1685 | |
| RFC1686;;Vecchi, M.;IPng Requirements: A Cable Television Industry Viewpoint;;;;;RFC 1686;DOI 10.17487/RFC1686;August;https://www.rfc-editor.org/info/rfc1686 | |
| RFC1687;;Fleischman, E.;A Large Corporate User's View of IPng;;;;;RFC 1687;DOI 10.17487/RFC1687;August;https://www.rfc-editor.org/info/rfc1687 | |
| RFC1688;;Simpson, W.;IPng Mobility Considerations;;;;;RFC 1688;DOI 10.17487/RFC1688;August;https://www.rfc-editor.org/info/rfc1688 | |
| RFC1689;;Foster, J., Ed.;A Status Report on Networked Information Retrieval: Tools and Groups;;FYI 25;;;RFC 1689;DOI 10.17487/RFC1689;August;https://www.rfc-editor.org/info/rfc1689 | |
| RFC1690;;Huston, G.;Introducing the Internet Engineering and Planning Group (IEPG);;;;;RFC 1690;DOI 10.17487/RFC1690;August;https://www.rfc-editor.org/info/rfc1690 | |
| RFC1691;;Turner, W.;The Document Architecture for the Cornell Digital Library;;;;;RFC 1691;DOI 10.17487/RFC1691;August;https://www.rfc-editor.org/info/rfc1691 | |
| RFC1692;;Cameron, P., Crocker, D., Cohen, D., and J. Postel;Transport Multiplexing Protocol (TMux);;;;;RFC 1692;DOI 10.17487/RFC1692;August;https://www.rfc-editor.org/info/rfc1692 | |
| RFC1693;RFC6247;Connolly, T., Amer, P., and P. Conrad;An Extension to TCP : Partial Order Service;;;;;RFC 1693;DOI 10.17487/RFC1693;November;https://www.rfc-editor.org/info/rfc1693 | |
| RFC1694;;Brown, T., Ed., and K. Tesink, Ed.;Definitions of Managed Objects for SMDS Interfaces using SMIv2;;;;;RFC 1694;DOI 10.17487/RFC1694;August;https://www.rfc-editor.org/info/rfc1694 | |
| RFC1695;RFC2515;Ahmed, M., Ed., and K. Tesink, Ed.;Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2;;;;;RFC 1695;DOI 10.17487/RFC1695;August;https://www.rfc-editor.org/info/rfc1695 | |
| RFC1696;;Barnes, J., Brown, L., Royston, R., and S. Waldbusser;Modem Management Information Base (MIB) using SMIv2;;;;;RFC 1696;DOI 10.17487/RFC1696;August;https://www.rfc-editor.org/info/rfc1696 | |
| RFC1697;;Brower, D., Ed., Purvy, B., Daniel, A., Sinykin, M., and J. Smith;Relational Database Management System (RDBMS) Management Information Base (MIB) using SMIv2;;;;;RFC 1697;DOI 10.17487/RFC1697;August;https://www.rfc-editor.org/info/rfc1697 | |
| RFC1698;;Furniss, P.;Octet Sequences for Upper-Layer OSI to Support Basic Communications Applications;;;;;RFC 1698;DOI 10.17487/RFC1698;October;https://www.rfc-editor.org/info/rfc1698 | |
| RFC1699;;Elliott, J.;Summary of 1600-1699;;;;;RFC 1699;DOI 10.17487/RFC1699;January;https://www.rfc-editor.org/info/rfc1699 | |
| RFC1700;RFC3232;Reynolds, J. and J. Postel;Assigned Numbers;;;;;RFC 1700;DOI 10.17487/RFC1700;October;https://www.rfc-editor.org/info/rfc1700 | |
| RFC1701;;Hanks, S., Li, T., Farinacci, D., and P. Traina;Generic Routing Encapsulation (GRE);;;;;RFC 1701;DOI 10.17487/RFC1701;October;https://www.rfc-editor.org/info/rfc1701 | |
| RFC1702;;Hanks, S., Li, T., Farinacci, D., and P. Traina;Generic Routing Encapsulation over IPv4 networks;;;;;RFC 1702;DOI 10.17487/RFC1702;October;https://www.rfc-editor.org/info/rfc1702 | |
| RFC1703;;Rose, M.;Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical Procedures;;;;;RFC 1703;DOI 10.17487/RFC1703;October;https://www.rfc-editor.org/info/rfc1703 | |
| RFC1704;;Haller, N. and R. Atkinson;On Internet Authentication;;;;;RFC 1704;DOI 10.17487/RFC1704;October;https://www.rfc-editor.org/info/rfc1704 | |
| RFC1705;;Carlson, R. and D. Ficarella;Six Virtual Inches to the Left: The Problem with IPng;;;;;RFC 1705;DOI 10.17487/RFC1705;October;https://www.rfc-editor.org/info/rfc1705 | |
| RFC1706;;Manning, B. and R. Colella;DNS NSAP Resource Records;;;;;RFC 1706;DOI 10.17487/RFC1706;October;https://www.rfc-editor.org/info/rfc1706 | |
| RFC1707;;McGovern, M. and R. Ullmann;CATNIP: Common Architecture for the Internet;;;;;RFC 1707;DOI 10.17487/RFC1707;October;https://www.rfc-editor.org/info/rfc1707 | |
| RFC1708;;Gowin, D.;NTP PICS PROFORMA - For the Network Time Protocol Version 3;;;;;RFC 1708;DOI 10.17487/RFC1708;October;https://www.rfc-editor.org/info/rfc1708 | |
| RFC1709;;Gargano, J. and D. Wasley;K-12 Internetworking Guidelines;;FYI 26;;;RFC 1709;DOI 10.17487/RFC1709;November;https://www.rfc-editor.org/info/rfc1709 | |
| RFC1710;;Hinden, R.;Simple Internet Protocol Plus White Paper;;;;;RFC 1710;DOI 10.17487/RFC1710;October;https://www.rfc-editor.org/info/rfc1710 | |
| RFC1711;;Houttuin, J.;Classifications in E-mail Routing;;;;;RFC 1711;DOI 10.17487/RFC1711;October;https://www.rfc-editor.org/info/rfc1711 | |
| RFC1712;;Farrell, C., Schulze, M., Pleitner, S., and D. Baldoni;DNS Encoding of Geographical Location;;;;;RFC 1712;DOI 10.17487/RFC1712;November;https://www.rfc-editor.org/info/rfc1712 | |
| RFC1713;;Romao, A.;Tools for DNS debugging;;FYI 27;;;RFC 1713;DOI 10.17487/RFC1713;November;https://www.rfc-editor.org/info/rfc1713 | |
| RFC1714;RFC2167;Williamson, S. and M. Kosters;Referral Whois Protocol (RWhois);;;;;RFC 1714;DOI 10.17487/RFC1714;November;https://www.rfc-editor.org/info/rfc1714 | |
| RFC1715;;Huitema, C.;The H Ratio for Address Assignment Efficiency;;;;;RFC 1715;DOI 10.17487/RFC1715;November;https://www.rfc-editor.org/info/rfc1715 | |
| RFC1716;RFC1812;Almquist, P. and F. Kastenholz;Towards Requirements for IP Routers;;;;;RFC 1716;DOI 10.17487/RFC1716;November;https://www.rfc-editor.org/info/rfc1716 | |
| RFC1717;RFC1990;Sklower, K., Lloyd, B., McGregor, G., and D. Carr;The PPP Multilink Protocol (MP);;;;;RFC 1717;DOI 10.17487/RFC1717;November;https://www.rfc-editor.org/info/rfc1717 | |
| RFC1718;RFC3160;IETF Secretariat and G. Malkin;The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force;;;;;RFC 1718;DOI 10.17487/RFC1718;November;https://www.rfc-editor.org/info/rfc1718 | |
| RFC1719;;Gross, P.;A Direction for IPng;;;;;RFC 1719;DOI 10.17487/RFC1719;December;https://www.rfc-editor.org/info/rfc1719 | |
| RFC1720;RFC1780;Postel, J.;Internet Official Protocol Standards;;;;;RFC 1720;DOI 10.17487/RFC1720;November;https://www.rfc-editor.org/info/rfc1720 | |
| RFC1721;;Malkin, G.;RIP Version 2 Protocol Analysis;;;;;RFC 1721;DOI 10.17487/RFC1721;November;https://www.rfc-editor.org/info/rfc1721 | |
| RFC1722;;Malkin, G.;RIP Version 2 Protocol Applicability Statement;;;;STD 57;RFC 1722;DOI 10.17487/RFC1722;November;https://www.rfc-editor.org/info/rfc1722 | |
| RFC1723;RFC2453;Malkin, G.;RIP Version 2 - Carrying Additional Information;;;;;RFC 1723;DOI 10.17487/RFC1723;November;https://www.rfc-editor.org/info/rfc1723 | |
| RFC1724;;Malkin, G. and F. Baker;RIP Version 2 MIB Extension;;;;;RFC 1724;DOI 10.17487/RFC1724;November;https://www.rfc-editor.org/info/rfc1724 | |
| RFC1725;RFC1939;Myers, J. and M. Rose;Post Office Protocol - Version 3;;;;;RFC 1725;DOI 10.17487/RFC1725;November;https://www.rfc-editor.org/info/rfc1725 | |
| RFC1726;;Partridge, C. and F. Kastenholz;Technical Criteria for Choosing IP The Next Generation (IPng);;;;;RFC 1726;DOI 10.17487/RFC1726;December;https://www.rfc-editor.org/info/rfc1726 | |
| RFC1727;;Weider, C. and P. Deutsch;A Vision of an Integrated Internet Information Service;;;;;RFC 1727;DOI 10.17487/RFC1727;December;https://www.rfc-editor.org/info/rfc1727 | |
| RFC1728;;Weider, C.;Resource Transponders;;;;;RFC 1728;DOI 10.17487/RFC1728;December;https://www.rfc-editor.org/info/rfc1728 | |
| RFC1729;;Lynch, C.;Using the Z39.50 Information Retrieval Protocol;;;;;RFC 1729;DOI 10.17487/RFC1729;December;https://www.rfc-editor.org/info/rfc1729 | |
| RFC1730;RFC2060, RFC2061;Crispin, M.;Internet Message Access Protocol - Version 4;;;;;RFC 1730;DOI 10.17487/RFC1730;December;https://www.rfc-editor.org/info/rfc1730 | |
| RFC1731;;Myers, J.;IMAP4 Authentication Mechanisms;;;;;RFC 1731;DOI 10.17487/RFC1731;December;https://www.rfc-editor.org/info/rfc1731 | |
| RFC1732;;Crispin, M.;IMAP4 Compatibility with IMAP2 and IMAP2bis;;;;;RFC 1732;DOI 10.17487/RFC1732;December;https://www.rfc-editor.org/info/rfc1732 | |
| RFC1733;;Crispin, M.;Distributed Electronic Mail Models in IMAP4;;;;;RFC 1733;DOI 10.17487/RFC1733;December;https://www.rfc-editor.org/info/rfc1733 | |
| RFC1734;RFC5034;Myers, J.;POP3 AUTHentication command;;;;;RFC 1734;DOI 10.17487/RFC1734;December;https://www.rfc-editor.org/info/rfc1734 | |
| RFC1735;;Heinanen, J. and R. Govindan;NBMA Address Resolution Protocol (NARP);;;;;RFC 1735;DOI 10.17487/RFC1735;December;https://www.rfc-editor.org/info/rfc1735 | |
| RFC1736;;Kunze, J.;Functional Recommendations for Internet Resource Locators;;;;;RFC 1736;DOI 10.17487/RFC1736;February;https://www.rfc-editor.org/info/rfc1736 | |
| RFC1737;;Sollins, K. and L. Masinter;Functional Requirements for Uniform Resource Names;;;;;RFC 1737;DOI 10.17487/RFC1737;December;https://www.rfc-editor.org/info/rfc1737 | |
| RFC1738;RFC4248, RFC4266;Berners-Lee, T., Masinter, L., and M. McCahill;Uniform Resource Locators (URL);;;;;RFC 1738;DOI 10.17487/RFC1738;December;https://www.rfc-editor.org/info/rfc1738 | |
| RFC1739;RFC2151;Kessler, G. and S. Shepard;A Primer On Internet and TCP/IP Tools;;;;;RFC 1739;DOI 10.17487/RFC1739;December;https://www.rfc-editor.org/info/rfc1739 | |
| RFC1740;;Faltstrom, P., Crocker, D., and E. Fair;MIME Encapsulation of Macintosh Files - MacMIME;;;;;RFC 1740;DOI 10.17487/RFC1740;December;https://www.rfc-editor.org/info/rfc1740 | |
| RFC1741;;Faltstrom, P., Crocker, D., and E. Fair;MIME Content Type for BinHex Encoded Files;;;;;RFC 1741;DOI 10.17487/RFC1741;December;https://www.rfc-editor.org/info/rfc1741 | |
| RFC1742;;Waldbusser, S. and K. Frisa;AppleTalk Management Information Base II;;;;;RFC 1742;DOI 10.17487/RFC1742;January;https://www.rfc-editor.org/info/rfc1742 | |
| RFC1743;RFC1748;McCloghrie, K. and E. Decker;IEEE 802.5 MIB using SMIv2;;;;;RFC 1743;DOI 10.17487/RFC1743;December;https://www.rfc-editor.org/info/rfc1743 | |
| RFC1744;;Huston, G.;Observations on the Management of the Internet Address Space;;;;;RFC 1744;DOI 10.17487/RFC1744;December;https://www.rfc-editor.org/info/rfc1744 | |
| RFC1745;;Varadhan, K., Hares, S., and Y. Rekhter;BGP4/IDRP for IP---OSPF Interaction;;;;;RFC 1745;DOI 10.17487/RFC1745;December;https://www.rfc-editor.org/info/rfc1745 | |
| RFC1746;;Manning, B. and D. Perkins;Ways to Define User Expectations;;;;;RFC 1746;DOI 10.17487/RFC1746;December;https://www.rfc-editor.org/info/rfc1746 | |
| RFC1747;;Hilgeman, J., Nix, S., Bartky, A., and W. Clark, Ed.;Definitions of Managed Objects for SNA Data Link Control (SDLC) using SMIv2;;;;;RFC 1747;DOI 10.17487/RFC1747;January;https://www.rfc-editor.org/info/rfc1747 | |
| RFC1748;;McCloghrie, K. and E. Decker;IEEE 802.5 MIB using SMIv2;;;;;RFC 1748;DOI 10.17487/RFC1748;December;https://www.rfc-editor.org/info/rfc1748 | |
| RFC1749;;McCloghrie, K., Baker, F., and E. Decker;IEEE 802.5 Station Source Routing MIB using SMIv2;;;;;RFC 1749;DOI 10.17487/RFC1749;December;https://www.rfc-editor.org/info/rfc1749 | |
| RFC1750;RFC4086;Eastlake 3rd, D., Crocker, S., and J. Schiller;Randomness Recommendations for Security;;;;;RFC 1750;DOI 10.17487/RFC1750;December;https://www.rfc-editor.org/info/rfc1750 | |
| RFC1751;;McDonald, D.;A Convention for Human-Readable 128-bit Keys;;;;;RFC 1751;DOI 10.17487/RFC1751;December;https://www.rfc-editor.org/info/rfc1751 | |
| RFC1752;;Bradner, S. and A. Mankin;The Recommendation for the IP Next Generation Protocol;;;;;RFC 1752;DOI 10.17487/RFC1752;January;https://www.rfc-editor.org/info/rfc1752 | |
| RFC1753;;Chiappa, N.;IPng Technical Requirements Of the Nimrod Routing and Addressing Architecture;;;;;RFC 1753;DOI 10.17487/RFC1753;December;https://www.rfc-editor.org/info/rfc1753 | |
| RFC1754;;Laubach, M.;IP over ATM Working Group's Recommendations for the ATM Forum's Multiprotocol BOF Version 1;;;;;RFC 1754;DOI 10.17487/RFC1754;January;https://www.rfc-editor.org/info/rfc1754 | |
| RFC1755;;Perez, M., Liaw, F., Mankin, A., Hoffman, E., Grossman, D., and A. Malis;ATM Signaling Support for IP over ATM;;;;;RFC 1755;DOI 10.17487/RFC1755;February;https://www.rfc-editor.org/info/rfc1755 | |
| RFC1756;;Rinne, T.;Remote Write Protocol - Version 1.0;;;;;RFC 1756;DOI 10.17487/RFC1756;January;https://www.rfc-editor.org/info/rfc1756 | |
| RFC1757;RFC2819;Waldbusser, S.;Remote Network Monitoring Management Information Base;;;;;RFC 1757;DOI 10.17487/RFC1757;February;https://www.rfc-editor.org/info/rfc1757 | |
| RFC1758;;The North American Directory Forum;NADF Standing Documents: A Brief Overview;;;;;RFC 1758;DOI 10.17487/RFC1758;February;https://www.rfc-editor.org/info/rfc1758 | |
| RFC1759;RFC3805;Smith, R., Wright, F., Hastings, T., Zilles, S., and J. Gyllenskog;Printer MIB;;;;;RFC 1759;DOI 10.17487/RFC1759;March;https://www.rfc-editor.org/info/rfc1759 | |
| RFC1760;;Haller, N.;The S/KEY One-Time Password System;;;;;RFC 1760;DOI 10.17487/RFC1760;February;https://www.rfc-editor.org/info/rfc1760 | |
| RFC1761;;Callaghan, B. and R. Gilligan;Snoop Version 2 Packet Capture File Format;;;;;RFC 1761;DOI 10.17487/RFC1761;February;https://www.rfc-editor.org/info/rfc1761 | |
| RFC1762;;Senum, S.;The PPP DECnet Phase IV Control Protocol (DNCP);;;;;RFC 1762;DOI 10.17487/RFC1762;March;https://www.rfc-editor.org/info/rfc1762 | |
| RFC1763;;Senum, S.;The PPP Banyan Vines Control Protocol (BVCP);;;;;RFC 1763;DOI 10.17487/RFC1763;March;https://www.rfc-editor.org/info/rfc1763 | |
| RFC1764;;Senum, S.;The PPP XNS IDP Control Protocol (XNSCP);;;;;RFC 1764;DOI 10.17487/RFC1764;March;https://www.rfc-editor.org/info/rfc1764 | |
| RFC1765;;Moy, J.;OSPF Database Overflow;;;;;RFC 1765;DOI 10.17487/RFC1765;March;https://www.rfc-editor.org/info/rfc1765 | |
| RFC1766;RFC3066, RFC3282;Alvestrand, H.;Tags for the Identification of Languages;;;;;RFC 1766;DOI 10.17487/RFC1766;March;https://www.rfc-editor.org/info/rfc1766 | |
| RFC1767;;Crocker, D.;MIME Encapsulation of EDI Objects;;;;;RFC 1767;DOI 10.17487/RFC1767;March;https://www.rfc-editor.org/info/rfc1767 | |
| RFC1768;;Marlow, D.;Host Group Extensions for CLNP Multicasting;;;;;RFC 1768;DOI 10.17487/RFC1768;March;https://www.rfc-editor.org/info/rfc1768 | |
| RFC1769;RFC2030, RFC4330;Mills, D.;Simple Network Time Protocol (SNTP);;;;;RFC 1769;DOI 10.17487/RFC1769;March;https://www.rfc-editor.org/info/rfc1769 | |
| RFC1770;RFC6814;Graff, C.;IPv4 Option for Sender Directed Multi-Destination Delivery;;;;;RFC 1770;DOI 10.17487/RFC1770;March;https://www.rfc-editor.org/info/rfc1770 | |
| RFC1771;RFC4271;Rekhter, Y. and T. Li;A Border Gateway Protocol 4 (BGP-4);;;;;RFC 1771;DOI 10.17487/RFC1771;March;https://www.rfc-editor.org/info/rfc1771 | |
| RFC1772;;Rekhter, Y. and P. Gross;Application of the Border Gateway Protocol in the Internet;;;;;RFC 1772;DOI 10.17487/RFC1772;March;https://www.rfc-editor.org/info/rfc1772 | |
| RFC1773;;Traina, P.;Experience with the BGP-4 protocol;;;;;RFC 1773;DOI 10.17487/RFC1773;March;https://www.rfc-editor.org/info/rfc1773 | |
| RFC1774;;Traina, P., Ed.;BGP-4 Protocol Analysis;;;;;RFC 1774;DOI 10.17487/RFC1774;March;https://www.rfc-editor.org/info/rfc1774 | |
| RFC1775;;Crocker, D.;To Be "On" the Internet;;;;;RFC 1775;DOI 10.17487/RFC1775;March;https://www.rfc-editor.org/info/rfc1775 | |
| RFC1776;;Crocker, S.;The Address is the Message;;;;;RFC 1776;DOI 10.17487/RFC1776;April;https://www.rfc-editor.org/info/rfc1776 | |
| RFC1777;RFC3494;Yeong, W., Howes, T., and S. Kille;Lightweight Directory Access Protocol;;;;;RFC 1777;DOI 10.17487/RFC1777;March;https://www.rfc-editor.org/info/rfc1777 | |
| RFC1778;RFC3494;Howes, T., Kille, S., Yeong, W., and C. Robbins;The String Representation of Standard Attribute Syntaxes;;;;;RFC 1778;DOI 10.17487/RFC1778;March;https://www.rfc-editor.org/info/rfc1778 | |
| RFC1779;RFC2253, RFC3494;Kille, S.;A String Representation of Distinguished Names;;;;;RFC 1779;DOI 10.17487/RFC1779;March;https://www.rfc-editor.org/info/rfc1779 | |
| RFC1780;RFC1800;Postel, J., Ed.;Internet Official Protocol Standards;;;;;RFC 1780;DOI 10.17487/RFC1780;March;https://www.rfc-editor.org/info/rfc1780 | |
| RFC1781;RFC3494;Kille, S.;Using the OSI Directory to Achieve User Friendly Naming;;;;;RFC 1781;DOI 10.17487/RFC1781;March;https://www.rfc-editor.org/info/rfc1781 | |
| RFC1782;RFC2347;Malkin, G. and A. Harkin;TFTP Option Extension;;;;;RFC 1782;DOI 10.17487/RFC1782;March;https://www.rfc-editor.org/info/rfc1782 | |
| RFC1783;RFC2348;Malkin, G. and A. Harkin;TFTP Blocksize Option;;;;;RFC 1783;DOI 10.17487/RFC1783;March;https://www.rfc-editor.org/info/rfc1783 | |
| RFC1784;RFC2349;Malkin, G. and A. Harkin;TFTP Timeout Interval and Transfer Size Options;;;;;RFC 1784;DOI 10.17487/RFC1784;March;https://www.rfc-editor.org/info/rfc1784 | |
| RFC1785;;Malkin, G. and A. Harkin;TFTP Option Negotiation Analysis;;;;;RFC 1785;DOI 10.17487/RFC1785;March;https://www.rfc-editor.org/info/rfc1785 | |
| RFC1786;;Bates, T., Gerich, E., Joncheray, L., Jouanigot, J-M., Karrenberg, D., Terpstra, M., and J. Yu;Representation of IP Routing Policies in a Routing Registry (ripe-81++);;;;;RFC 1786;DOI 10.17487/RFC1786;March;https://www.rfc-editor.org/info/rfc1786 | |
| RFC1787;;Rekhter, Y.;Routing in a Multi-provider Internet;;;;;RFC 1787;DOI 10.17487/RFC1787;April;https://www.rfc-editor.org/info/rfc1787 | |
| RFC1788;RFC6918;Simpson, W.;ICMP Domain Name Messages;;;;;RFC 1788;DOI 10.17487/RFC1788;April;https://www.rfc-editor.org/info/rfc1788 | |
| RFC1789;;Yang, C.;INETPhone: Telephone Services and Servers on Internet;;;;;RFC 1789;DOI 10.17487/RFC1789;April;https://www.rfc-editor.org/info/rfc1789 | |
| RFC1790;;Cerf, V.;An Agreement between the Internet Society and Sun Microsystems, Inc. in the Matter of ONC RPC and XDR Protocols;;;;;RFC 1790;DOI 10.17487/RFC1790;April;https://www.rfc-editor.org/info/rfc1790 | |
| RFC1791;;Sung, T.;TCP And UDP Over IPX Networks With Fixed Path MTU;;;;;RFC 1791;DOI 10.17487/RFC1791;April;https://www.rfc-editor.org/info/rfc1791 | |
| RFC1792;;Sung, T.;TCP/IPX Connection Mib Specification;;;;;RFC 1792;DOI 10.17487/RFC1792;April;https://www.rfc-editor.org/info/rfc1792 | |
| RFC1793;;Moy, J.;Extending OSPF to Support Demand Circuits;;;;;RFC 1793;DOI 10.17487/RFC1793;April;https://www.rfc-editor.org/info/rfc1793 | |
| RFC1794;;Brisco, T.;DNS Support for Load Balancing;;;;;RFC 1794;DOI 10.17487/RFC1794;April;https://www.rfc-editor.org/info/rfc1794 | |
| RFC1795;;Wells, L. and A. Bartky, Ed.;Data Link Switching: Switch-to-Switch Protocol AIW DLSw RIG: DLSw Closed Pages, DLSw Standard Version 1;;;;;RFC 1795;DOI 10.17487/RFC1795;April;https://www.rfc-editor.org/info/rfc1795 | |
| RFC1796;;Huitema, C., Postel, J., and S. Crocker;Not All RFCs are Standards;;;;;RFC 1796;DOI 10.17487/RFC1796;April;https://www.rfc-editor.org/info/rfc1796 | |
| RFC1797;;Internet Assigned Numbers Authority (IANA);Class A Subnet Experiment;;;;;RFC 1797;DOI 10.17487/RFC1797;April;https://www.rfc-editor.org/info/rfc1797 | |
| RFC1798;RFC3352;Young, A.;Connection-less Lightweight X.500 Directory Access Protocol;;;;;RFC 1798;DOI 10.17487/RFC1798;June;https://www.rfc-editor.org/info/rfc1798 | |
| RFC1799;;Kennedy, M.;Request for Comments Summary RFC Numbers 1700-1799;;;;;RFC 1799;DOI 10.17487/RFC1799;January;https://www.rfc-editor.org/info/rfc1799 | |
| RFC1800;RFC1880;Postel, J., Ed.;Internet Official Protocol Standards;;;;;RFC 1800;DOI 10.17487/RFC1800;July;https://www.rfc-editor.org/info/rfc1800 | |
| RFC1801;;Kille, S.;MHS use of the X.500 Directory to support MHS Routing;;;;;RFC 1801;DOI 10.17487/RFC1801;June;https://www.rfc-editor.org/info/rfc1801 | |
| RFC1802;;Alvestrand, H., Jordan, K., Langlois, S., and J. Romaguera;Introducing Project Long Bud: Internet Pilot Project for the Deployment of X.500 Directory Information in Support of X.400 Routing;;;;;RFC 1802;DOI 10.17487/RFC1802;June;https://www.rfc-editor.org/info/rfc1802 | |
| RFC1803;;Wright, R., Getchell, A., Howes, T., Sataluri, S., Yee, P., and W. Yeong;Recommendations for an X.500 Production Directory Service;;;;;RFC 1803;DOI 10.17487/RFC1803;June;https://www.rfc-editor.org/info/rfc1803 | |
| RFC1804;;Mansfield, G., Rajeev, P., Raghavan, S., and T. Howes;Schema Publishing in X.500 Directory;;;;;RFC 1804;DOI 10.17487/RFC1804;June;https://www.rfc-editor.org/info/rfc1804 | |
| RFC1805;;Rubin, A.;Location-Independent Data/Software Integrity Protocol;;;;;RFC 1805;DOI 10.17487/RFC1805;June;https://www.rfc-editor.org/info/rfc1805 | |
| RFC1806;RFC2183;Troost, R. and S. Dorner;Communicating Presentation Information in Internet Messages: The Content-Disposition Header;;;;;RFC 1806;DOI 10.17487/RFC1806;June;https://www.rfc-editor.org/info/rfc1806 | |
| RFC1807;;Lasher, R. and D. Cohen;A Format for Bibliographic Records;;;;;RFC 1807;DOI 10.17487/RFC1807;June;https://www.rfc-editor.org/info/rfc1807 | |
| RFC1808;RFC3986;Fielding, R.;Relative Uniform Resource Locators;;;;;RFC 1808;DOI 10.17487/RFC1808;June;https://www.rfc-editor.org/info/rfc1808 | |
| RFC1809;;Partridge, C.;Using the Flow Label Field in IPv6;;;;;RFC 1809;DOI 10.17487/RFC1809;June;https://www.rfc-editor.org/info/rfc1809 | |
| RFC1810;;Touch, J.;Report on MD5 Performance;;;;;RFC 1810;DOI 10.17487/RFC1810;June;https://www.rfc-editor.org/info/rfc1810 | |
| RFC1811;RFC1816;Federal Networking Council;U.S. Government Internet Domain Names;;;;;RFC 1811;DOI 10.17487/RFC1811;June;https://www.rfc-editor.org/info/rfc1811 | |
| RFC1812;;Baker, F., Ed.;Requirements for IP Version 4 Routers;;;;;RFC 1812;DOI 10.17487/RFC1812;June;https://www.rfc-editor.org/info/rfc1812 | |
| RFC1813;;Callaghan, B., Pawlowski, B., and P. Staubach;NFS Version 3 Protocol Specification;;;;;RFC 1813;DOI 10.17487/RFC1813;June;https://www.rfc-editor.org/info/rfc1813 | |
| RFC1814;;Gerich, E.;Unique Addresses are Good;;;;;RFC 1814;DOI 10.17487/RFC1814;June;https://www.rfc-editor.org/info/rfc1814 | |
| RFC1815;;Ohta, M.;Character Sets ISO-10646 and ISO-10646-J-1;;;;;RFC 1815;DOI 10.17487/RFC1815;July;https://www.rfc-editor.org/info/rfc1815 | |
| RFC1816;RFC2146;Federal Networking Council;U.S. Government Internet Domain Names;;;;;RFC 1816;DOI 10.17487/RFC1816;August;https://www.rfc-editor.org/info/rfc1816 | |
| RFC1817;;Rekhter, Y.;CIDR and Classful Routing;;;;;RFC 1817;DOI 10.17487/RFC1817;August;https://www.rfc-editor.org/info/rfc1817 | |
| RFC1818;;Postel, J., Li, T., and Y. Rekhter;Best Current Practices;;;;;RFC 1818;DOI 10.17487/RFC1818;August;https://www.rfc-editor.org/info/rfc1818 | |
| RFC1819;;Delgrossi, L., Ed., and L. Berger, Ed.;Internet Stream Protocol Version 2 (ST2) Protocol Specification - Version ST2+;;;;;RFC 1819;DOI 10.17487/RFC1819;August;https://www.rfc-editor.org/info/rfc1819 | |
| RFC1820;RFC1844;Huizer, E.;Multimedia E-mail (MIME) User Agent Checklist;;;;;RFC 1820;DOI 10.17487/RFC1820;August;https://www.rfc-editor.org/info/rfc1820 | |
| RFC1821;;Borden, M., Crawley, E., Davie, B., and S. Batsell;Integration of Real-time Services in an IP-ATM Network Architecture;;;;;RFC 1821;DOI 10.17487/RFC1821;August;https://www.rfc-editor.org/info/rfc1821 | |
| RFC1822;;Lowe, J.;A Grant of Rights to Use a Specific IBM patent with Photuris;;;;;RFC 1822;DOI 10.17487/RFC1822;August;https://www.rfc-editor.org/info/rfc1822 | |
| RFC1823;;Howes, T. and M. Smith;The LDAP Application Program Interface;;;;;RFC 1823;DOI 10.17487/RFC1823;August;https://www.rfc-editor.org/info/rfc1823 | |
| RFC1824;;Danisch, H.;The Exponential Security System TESS: An Identity-Based Cryptographic Protocol for Authenticated Key-Exchange (E.I.S.S.-Report 1995/4);;;;;RFC 1824;DOI 10.17487/RFC1824;August;https://www.rfc-editor.org/info/rfc1824 | |
| RFC1825;RFC2401;Atkinson, R.;Security Architecture for the Internet Protocol;;;;;RFC 1825;DOI 10.17487/RFC1825;August;https://www.rfc-editor.org/info/rfc1825 | |
| RFC1826;RFC2402;Atkinson, R.;IP Authentication Header;;;;;RFC 1826;DOI 10.17487/RFC1826;August;https://www.rfc-editor.org/info/rfc1826 | |
| RFC1827;RFC2406;Atkinson, R.;IP Encapsulating Security Payload (ESP);;;;;RFC 1827;DOI 10.17487/RFC1827;August;https://www.rfc-editor.org/info/rfc1827 | |
| RFC1828;;Metzger, P. and W. Simpson;IP Authentication using Keyed MD5;;;;;RFC 1828;DOI 10.17487/RFC1828;August;https://www.rfc-editor.org/info/rfc1828 | |
| RFC1829;;Karn, P., Metzger, P., and W. Simpson;The ESP DES-CBC Transform;;;;;RFC 1829;DOI 10.17487/RFC1829;August;https://www.rfc-editor.org/info/rfc1829 | |
| RFC1830;RFC3030;Vaudreuil, G.;SMTP Service Extensions for Transmission of Large and Binary MIME Messages;;;;;RFC 1830;DOI 10.17487/RFC1830;August;https://www.rfc-editor.org/info/rfc1830 | |
| RFC1831;RFC5531;Srinivasan, R.;RPC: Remote Procedure Call Protocol Specification Version 2;;;;;RFC 1831;DOI 10.17487/RFC1831;August;https://www.rfc-editor.org/info/rfc1831 | |
| RFC1832;RFC4506;Srinivasan, R.;XDR: External Data Representation Standard;;;;;RFC 1832;DOI 10.17487/RFC1832;August;https://www.rfc-editor.org/info/rfc1832 | |
| RFC1833;;Srinivasan, R.;Binding Protocols for ONC RPC Version 2;;;;;RFC 1833;DOI 10.17487/RFC1833;August;https://www.rfc-editor.org/info/rfc1833 | |
| RFC1834;;Gargano, J. and K. Weiss;Whois and Network Information Lookup Service, Whois++;;;;;RFC 1834;DOI 10.17487/RFC1834;August;https://www.rfc-editor.org/info/rfc1834 | |
| RFC1835;;Deutsch, P., Schoultz, R., Faltstrom, P., and C. Weider;Architecture of the WHOIS++ service;;;;;RFC 1835;DOI 10.17487/RFC1835;August;https://www.rfc-editor.org/info/rfc1835 | |
| RFC1836;RFC2294;Kille, S.;Representing the O/R Address hierarchy in the X.500 Directory Information Tree;;;;;RFC 1836;DOI 10.17487/RFC1836;August;https://www.rfc-editor.org/info/rfc1836 | |
| RFC1837;RFC2293;Kille, S.;Representing Tables and Subtrees in the X.500 Directory;;;;;RFC 1837;DOI 10.17487/RFC1837;August;https://www.rfc-editor.org/info/rfc1837 | |
| RFC1838;RFC2164;Kille, S.;Use of the X.500 Directory to support mapping between X.400 and RFC 822 Addresses;;;;;RFC 1838;DOI 10.17487/RFC1838;August;https://www.rfc-editor.org/info/rfc1838 | |
| RFC1841;;Chapman, J., Coli, D., Harvey, A., Jensen, B., and K. Rowett;PPP Network Control Protocol for LAN Extension;;;;;RFC 1841;DOI 10.17487/RFC1841;September;https://www.rfc-editor.org/info/rfc1841 | |
| RFC1842;;Wei, Y., Zhang, Y., Li, J., Ding, J., and Y. Jiang;ASCII Printable Characters-Based Chinese Character Encoding for Internet Messages;;;;;RFC 1842;DOI 10.17487/RFC1842;August;https://www.rfc-editor.org/info/rfc1842 | |
| RFC1843;;Lee, F.;HZ - A Data Format for Exchanging Files of Arbitrarily Mixed Chinese and ASCII characters;;;;;RFC 1843;DOI 10.17487/RFC1843;August;https://www.rfc-editor.org/info/rfc1843 | |
| RFC1844;;Huizer, E.;Multimedia E-mail (MIME) User Agent Checklist;;;;;RFC 1844;DOI 10.17487/RFC1844;August;https://www.rfc-editor.org/info/rfc1844 | |
| RFC1845;;Crocker, D., Freed, N., and A. Cargille;SMTP Service Extension for Checkpoint/Restart;;;;;RFC 1845;DOI 10.17487/RFC1845;September;https://www.rfc-editor.org/info/rfc1845 | |
| RFC1846;;Durand, A. and F. Dupont;SMTP 521 Reply Code;;;;;RFC 1846;DOI 10.17487/RFC1846;September;https://www.rfc-editor.org/info/rfc1846 | |
| RFC1847;;Galvin, J., Murphy, S., Crocker, S., and N. Freed;Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted;;;;;RFC 1847;DOI 10.17487/RFC1847;October;https://www.rfc-editor.org/info/rfc1847 | |
| RFC1848;;Crocker, S., Freed, N., Galvin, J., and S. Murphy;MIME Object Security Services;;;;;RFC 1848;DOI 10.17487/RFC1848;October;https://www.rfc-editor.org/info/rfc1848 | |
| RFC1849;RFC5536, RFC5537;Spencer, H.;"Son of 1036": News Article Format and Transmission;;;;;RFC 1849;DOI 10.17487/RFC1849;March;https://www.rfc-editor.org/info/rfc1849 | |
| RFC1850;RFC4750;Baker, F. and R. Coltun;OSPF Version 2 Management Information Base;;;;;RFC 1850;DOI 10.17487/RFC1850;November;https://www.rfc-editor.org/info/rfc1850 | |
| RFC1851;;Karn, P., Metzger, P., and W. Simpson;The ESP Triple DES Transform;;;;;RFC 1851;DOI 10.17487/RFC1851;September;https://www.rfc-editor.org/info/rfc1851 | |
| RFC1852;RFC2841;Metzger, P. and W. Simpson;IP Authentication using Keyed SHA;;;;;RFC 1852;DOI 10.17487/RFC1852;September;https://www.rfc-editor.org/info/rfc1852 | |
| RFC1853;;Simpson, W.;IP in IP Tunneling;;;;;RFC 1853;DOI 10.17487/RFC1853;October;https://www.rfc-editor.org/info/rfc1853 | |
| RFC1854;RFC2197;Freed, N.;SMTP Service Extension for Command Pipelining;;;;;RFC 1854;DOI 10.17487/RFC1854;October;https://www.rfc-editor.org/info/rfc1854 | |
| RFC1855;;Hambridge, S.;Netiquette Guidelines;;FYI 28;;;RFC 1855;DOI 10.17487/RFC1855;October;https://www.rfc-editor.org/info/rfc1855 | |
| RFC1856;;Clark, H.;The Opstat Client-Server Model for Statistics Retrieval;;;;;RFC 1856;DOI 10.17487/RFC1856;September;https://www.rfc-editor.org/info/rfc1856 | |
| RFC1857;;Lambert, M.;A Model for Common Operational Statistics;;;;;RFC 1857;DOI 10.17487/RFC1857;October;https://www.rfc-editor.org/info/rfc1857 | |
| RFC1858;;Ziemba, G., Reed, D., and P. Traina;Security Considerations for IP Fragment Filtering;;;;;RFC 1858;DOI 10.17487/RFC1858;October;https://www.rfc-editor.org/info/rfc1858 | |
| RFC1859;;Pouffary, Y.;ISO Transport Class 2 Non-use of Explicit Flow Control over TCP RFC1006 extension;;;;;RFC 1859;DOI 10.17487/RFC1859;October;https://www.rfc-editor.org/info/rfc1859 | |
| RFC1860;RFC1878;Pummill, T. and B. Manning;Variable Length Subnet Table For IPv4;;;;;RFC 1860;DOI 10.17487/RFC1860;October;https://www.rfc-editor.org/info/rfc1860 | |
| RFC1861;;Gwinn, A.;Simple Network Paging Protocol - Version 3 -Two-Way Enhanced;;;;;RFC 1861;DOI 10.17487/RFC1861;October;https://www.rfc-editor.org/info/rfc1861 | |
| RFC1862;;McCahill, M., Romkey, J., Schwartz, M., Sollins, K., Verschuren, T., and C. Weider;Report of the IAB Workshop on Internet Information Infrastructure, October 12-14, 1994;;;;;RFC 1862;DOI 10.17487/RFC1862;November;https://www.rfc-editor.org/info/rfc1862 | |
| RFC1863;RFC4223;Haskin, D.;A BGP/IDRP Route Server alternative to a full mesh routing;;;;;RFC 1863;DOI 10.17487/RFC1863;October;https://www.rfc-editor.org/info/rfc1863 | |
| RFC1864;;Myers, J. and M. Rose;The Content-MD5 Header Field;;;;;RFC 1864;DOI 10.17487/RFC1864;October;https://www.rfc-editor.org/info/rfc1864 | |
| RFC1865;;Houser, W., Griffin, J., and C. Hage;EDI Meets the Internet Frequently Asked Questions about Electronic Data Interchange (EDI) on the Internet;;;;;RFC 1865;DOI 10.17487/RFC1865;January;https://www.rfc-editor.org/info/rfc1865 | |
| RFC1866;RFC2854;Berners-Lee, T. and D. Connolly;Hypertext Markup Language - 2.0;;;;;RFC 1866;DOI 10.17487/RFC1866;November;https://www.rfc-editor.org/info/rfc1866 | |
| RFC1867;RFC2854;Nebel, E. and L. Masinter;Form-based File Upload in HTML;;;;;RFC 1867;DOI 10.17487/RFC1867;November;https://www.rfc-editor.org/info/rfc1867 | |
| RFC1868;;Malkin, G.;ARP Extension - UNARP;;;;;RFC 1868;DOI 10.17487/RFC1868;November;https://www.rfc-editor.org/info/rfc1868 | |
| RFC1869;RFC2821;Klensin, J., Freed, N., Rose, M., Stefferud, E., and D. Crocker;SMTP Service Extensions;;;;STD 10;RFC 1869;DOI 10.17487/RFC1869;November;https://www.rfc-editor.org/info/rfc1869 | |
| RFC1870;;Klensin, J., Freed, N., and K. Moore;SMTP Service Extension for Message Size Declaration;;;;STD 10;RFC 1870;DOI 10.17487/RFC1870;November;https://www.rfc-editor.org/info/rfc1870 | |
| RFC1871;RFC2026;Postel, J.;Addendum to RFC 1602 -- Variance Procedure;;;;;RFC 1871;DOI 10.17487/RFC1871;November;https://www.rfc-editor.org/info/rfc1871 | |
| RFC1872;RFC2112;Levinson, E.;The MIME Multipart/Related Content-type;;;;;RFC 1872;DOI 10.17487/RFC1872;December;https://www.rfc-editor.org/info/rfc1872 | |
| RFC1873;;Levinson, E.;Message/External-Body Content-ID Access Type;;;;;RFC 1873;DOI 10.17487/RFC1873;December;https://www.rfc-editor.org/info/rfc1873 | |
| RFC1874;;Levinson, E.;SGML Media Types;;;;;RFC 1874;DOI 10.17487/RFC1874;December;https://www.rfc-editor.org/info/rfc1874 | |
| RFC1875;;Berge, N.;UNINETT PCA Policy Statements;;;;;RFC 1875;DOI 10.17487/RFC1875;December;https://www.rfc-editor.org/info/rfc1875 | |
| RFC1876;;Davis, C., Vixie, P., Goodwin, T., and I. Dickinson;A Means for Expressing Location Information in the Domain Name System;;;;;RFC 1876;DOI 10.17487/RFC1876;January;https://www.rfc-editor.org/info/rfc1876 | |
| RFC1877;;Cobb, S.;PPP Internet Protocol Control Protocol Extensions for Name Server Addresses;;;;;RFC 1877;DOI 10.17487/RFC1877;December;https://www.rfc-editor.org/info/rfc1877 | |
| RFC1878;;Pummill, T. and B. Manning;Variable Length Subnet Table For IPv4;;;;;RFC 1878;DOI 10.17487/RFC1878;December;https://www.rfc-editor.org/info/rfc1878 | |
| RFC1879;;Manning, B., Ed.;Class A Subnet Experiment Results and Recommendations;;;;;RFC 1879;DOI 10.17487/RFC1879;January;https://www.rfc-editor.org/info/rfc1879 | |
| RFC1880;RFC1920;Postel, J., Ed.;Internet Official Protocol Standards;;;;;RFC 1880;DOI 10.17487/RFC1880;November;https://www.rfc-editor.org/info/rfc1880 | |
| RFC1881;;IAB and IESG;IPv6 Address Allocation Management;;;;;RFC 1881;DOI 10.17487/RFC1881;December;https://www.rfc-editor.org/info/rfc1881 | |
| RFC1882;;Hancock, B.;The 12-Days of Technology Before Christmas;;;;;RFC 1882;DOI 10.17487/RFC1882;December;https://www.rfc-editor.org/info/rfc1882 | |
| RFC1883;RFC2460;Deering, S. and R. Hinden;Internet Protocol, Version 6 (IPv6) Specification;;;;;RFC 1883;DOI 10.17487/RFC1883;December;https://www.rfc-editor.org/info/rfc1883 | |
| RFC1884;RFC2373;Hinden, R., Ed., and S. Deering, Ed.;IP Version 6 Addressing Architecture;;;;;RFC 1884;DOI 10.17487/RFC1884;December;https://www.rfc-editor.org/info/rfc1884 | |
| RFC1885;RFC2463;Conta, A. and S. Deering;Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6);;;;;RFC 1885;DOI 10.17487/RFC1885;December;https://www.rfc-editor.org/info/rfc1885 | |
| RFC1886;RFC3596;Thomson, S. and C. Huitema;DNS Extensions to support IP version 6;;;;;RFC 1886;DOI 10.17487/RFC1886;December;https://www.rfc-editor.org/info/rfc1886 | |
| RFC1887;;Rekhter, Y., Ed., and T. Li, Ed.;An Architecture for IPv6 Unicast Address Allocation;;;;;RFC 1887;DOI 10.17487/RFC1887;December;https://www.rfc-editor.org/info/rfc1887 | |
| RFC1888;RFC4048;Bound, J., Carpenter, B., Harrington, D., Houldsworth, J., and A. Lloyd;OSI NSAPs and IPv6;;;;;RFC 1888;DOI 10.17487/RFC1888;August;https://www.rfc-editor.org/info/rfc1888 | |
| RFC1889;RFC3550;Audio-Video Transport Working Group, Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson;RTP: A Transport Protocol for Real-Time Applications;;;;;RFC 1889;DOI 10.17487/RFC1889;January;https://www.rfc-editor.org/info/rfc1889 | |
| RFC1890;RFC3551;Audio-Video Transport Working Group and H. Schulzrinne;RTP Profile for Audio and Video Conferences with Minimal Control;;;;;RFC 1890;DOI 10.17487/RFC1890;January;https://www.rfc-editor.org/info/rfc1890 | |
| RFC1891;RFC3461;Moore, K.;SMTP Service Extension for Delivery Status Notifications;;;;;RFC 1891;DOI 10.17487/RFC1891;January;https://www.rfc-editor.org/info/rfc1891 | |
| RFC1892;RFC3462;Vaudreuil, G.;The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages;;;;;RFC 1892;DOI 10.17487/RFC1892;January;https://www.rfc-editor.org/info/rfc1892 | |
| RFC1893;RFC3463;Vaudreuil, G.;Enhanced Mail System Status Codes;;;;;RFC 1893;DOI 10.17487/RFC1893;January;https://www.rfc-editor.org/info/rfc1893 | |
| RFC1894;RFC3464;Moore, K. and G. Vaudreuil;An Extensible Message Format for Delivery Status Notifications;;;;;RFC 1894;DOI 10.17487/RFC1894;January;https://www.rfc-editor.org/info/rfc1894 | |
| RFC1895;;Levinson, E.;The Application/CALS-1840 Content-type;;;;;RFC 1895;DOI 10.17487/RFC1895;February;https://www.rfc-editor.org/info/rfc1895 | |
| RFC1896;;Resnick, P. and A. Walker;The text/enriched MIME Content-type;;;;;RFC 1896;DOI 10.17487/RFC1896;February;https://www.rfc-editor.org/info/rfc1896 | |
| RFC1897;RFC2471;Hinden, R. and J. Postel;IPv6 Testing Address Allocation;;;;;RFC 1897;DOI 10.17487/RFC1897;January;https://www.rfc-editor.org/info/rfc1897 | |
| RFC1898;;Eastlake 3rd, D., Boesch, B., Crocker, S., and M. Yesil;CyberCash Credit Card Protocol Version 0.8;;;;;RFC 1898;DOI 10.17487/RFC1898;February;https://www.rfc-editor.org/info/rfc1898 | |
| RFC1899;;Elliott, J.;Request for Comments Summary RFC Numbers 1800-1899;;;;;RFC 1899;DOI 10.17487/RFC1899;January;https://www.rfc-editor.org/info/rfc1899 | |
| RFC1900;;Carpenter, B. and Y. Rekhter;Renumbering Needs Work;;;;;RFC 1900;DOI 10.17487/RFC1900;February;https://www.rfc-editor.org/info/rfc1900 | |
| RFC1901;;Case, J., McCloghrie, K., Rose, M., and S. Waldbusser;Introduction to Community-based SNMPv2;;;;;RFC 1901;DOI 10.17487/RFC1901;January;https://www.rfc-editor.org/info/rfc1901 | |
| RFC1902;RFC2578;Case, J., McCloghrie, K., Rose, M., and S. Waldbusser;Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2);;;;;RFC 1902;DOI 10.17487/RFC1902;January;https://www.rfc-editor.org/info/rfc1902 | |
| RFC1903;RFC2579;Case, J., McCloghrie, K., Rose, M., and S. Waldbusser;Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2);;;;;RFC 1903;DOI 10.17487/RFC1903;January;https://www.rfc-editor.org/info/rfc1903 | |
| RFC1904;RFC2580;Case, J., McCloghrie, K., Rose, M., and S. Waldbusser;Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2);;;;;RFC 1904;DOI 10.17487/RFC1904;January;https://www.rfc-editor.org/info/rfc1904 | |
| RFC1905;RFC3416;Case, J., McCloghrie, K., Rose, M., and S. Waldbusser;Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2);;;;;RFC 1905;DOI 10.17487/RFC1905;January;https://www.rfc-editor.org/info/rfc1905 | |
| RFC1906;RFC3417;Case, J., McCloghrie, K., Rose, M., and S. Waldbusser;Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2);;;;;RFC 1906;DOI 10.17487/RFC1906;January;https://www.rfc-editor.org/info/rfc1906 | |
| RFC1907;RFC3418;Case, J., McCloghrie, K., Rose, M., and S. Waldbusser;Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2);;;;;RFC 1907;DOI 10.17487/RFC1907;January;https://www.rfc-editor.org/info/rfc1907 | |
| RFC1908;RFC2576;Case, J., McCloghrie, K., Rose, M., and S. Waldbusser;Coexistence between Version 1 and Version 2 of the Internet-standard Network Management Framework;;;;;RFC 1908;DOI 10.17487/RFC1908;January;https://www.rfc-editor.org/info/rfc1908 | |
| RFC1909;;McCloghrie, K., Ed.;An Administrative Infrastructure for SNMPv2;;;;;RFC 1909;DOI 10.17487/RFC1909;February;https://www.rfc-editor.org/info/rfc1909 | |
| RFC1910;;Waters, G., Ed.;User-based Security Model for SNMPv2;;;;;RFC 1910;DOI 10.17487/RFC1910;February;https://www.rfc-editor.org/info/rfc1910 | |
| RFC1911;RFC2421, RFC2422, RFC2423;Vaudreuil, G.;Voice Profile for Internet Mail;;;;;RFC 1911;DOI 10.17487/RFC1911;February;https://www.rfc-editor.org/info/rfc1911 | |
| RFC1912;;Barr, D.;Common DNS Operational and Configuration Errors;;;;;RFC 1912;DOI 10.17487/RFC1912;February;https://www.rfc-editor.org/info/rfc1912 | |
| RFC1913;;Weider, C., Fullton, J., and S. Spero;Architecture of the Whois++ Index Service;;;;;RFC 1913;DOI 10.17487/RFC1913;February;https://www.rfc-editor.org/info/rfc1913 | |
| RFC1914;;Faltstrom, P., Schoultz, R., and C. Weider;How to Interact with a Whois++ Mesh;;;;;RFC 1914;DOI 10.17487/RFC1914;February;https://www.rfc-editor.org/info/rfc1914 | |
| RFC1915;;Kastenholz, F.;Variance for The PPP Compression Control Protocol and The PPP Encryption Control Protocol;;;BCP 3;;RFC 1915;DOI 10.17487/RFC1915;February;https://www.rfc-editor.org/info/rfc1915 | |
| RFC1916;;Berkowitz, H., Ferguson, P., Leland, W., and P. Nesser;Enterprise Renumbering: Experience and Information Solicitation;;;;;RFC 1916;DOI 10.17487/RFC1916;February;https://www.rfc-editor.org/info/rfc1916 | |
| RFC1917;;Nesser II, P.;An Appeal to the Internet Community to Return Unused IP Networks (Prefixes) to the IANA;;;BCP 4;;RFC 1917;DOI 10.17487/RFC1917;February;https://www.rfc-editor.org/info/rfc1917 | |
| RFC1918;;Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G., and E. Lear;Address Allocation for Private Internets;;;BCP 5;;RFC 1918;DOI 10.17487/RFC1918;February;https://www.rfc-editor.org/info/rfc1918 | |
| RFC1919;;Chatel, M.;Classical versus Transparent IP Proxies;;;;;RFC 1919;DOI 10.17487/RFC1919;March;https://www.rfc-editor.org/info/rfc1919 | |
| RFC1920;RFC2000;Postel, J.;Internet Official Protocol Standards;;;;;RFC 1920;DOI 10.17487/RFC1920;March;https://www.rfc-editor.org/info/rfc1920 | |
| RFC1921;;Dujonc, J.;TNVIP Protocol;;;;;RFC 1921;DOI 10.17487/RFC1921;March;https://www.rfc-editor.org/info/rfc1921 | |
| RFC1922;;Zhu, HF., Hu, DY., Wang, ZG., Kao, TC., Chang, WCH., and M. Crispin;Chinese Character Encoding for Internet Messages;;;;;RFC 1922;DOI 10.17487/RFC1922;March;https://www.rfc-editor.org/info/rfc1922 | |
| RFC1923;;Halpern, J. and S. Bradner;RIPv1 Applicability Statement for Historic Status;;;;;RFC 1923;DOI 10.17487/RFC1923;March;https://www.rfc-editor.org/info/rfc1923 | |
| RFC1924;;Elz, R.;A Compact Representation of IPv6 Addresses;;;;;RFC 1924;DOI 10.17487/RFC1924;April;https://www.rfc-editor.org/info/rfc1924 | |
| RFC1925;;Callon, R.;The Twelve Networking Truths;;;;;RFC 1925;DOI 10.17487/RFC1925;April;https://www.rfc-editor.org/info/rfc1925 | |
| RFC1926;;Eriksson, J.;An Experimental Encapsulation of IP Datagrams on Top of ATM;;;;;RFC 1926;DOI 10.17487/RFC1926;April;https://www.rfc-editor.org/info/rfc1926 | |
| RFC1927;;Rogers, C.;Suggested Additional MIME Types for Associating Documents;;;;;RFC 1927;DOI 10.17487/RFC1927;April;https://www.rfc-editor.org/info/rfc1927 | |
| RFC1928;;Leech, M., Ganis, M., Lee, Y., Kuris, R., Koblas, D., and L. Jones;SOCKS Protocol Version 5;;;;;RFC 1928;DOI 10.17487/RFC1928;March;https://www.rfc-editor.org/info/rfc1928 | |
| RFC1929;;Leech, M.;Username/Password Authentication for SOCKS V5;;;;;RFC 1929;DOI 10.17487/RFC1929;March;https://www.rfc-editor.org/info/rfc1929 | |
| RFC1930;;Hawkinson, J. and T. Bates;Guidelines for creation, selection, and registration of an Autonomous System (AS);;;BCP 6;;RFC 1930;DOI 10.17487/RFC1930;March;https://www.rfc-editor.org/info/rfc1930 | |
| RFC1931;;Brownell, D.;Dynamic RARP Extensions for Automatic Network Address Acquisition;;;;;RFC 1931;DOI 10.17487/RFC1931;April;https://www.rfc-editor.org/info/rfc1931 | |
| RFC1932;;Cole, R., Shur, D., and C. Villamizar;IP over ATM: A Framework Document;;;;;RFC 1932;DOI 10.17487/RFC1932;April;https://www.rfc-editor.org/info/rfc1932 | |
| RFC1933;RFC2893;Gilligan, R. and E. Nordmark;Transition Mechanisms for IPv6 Hosts and Routers;;;;;RFC 1933;DOI 10.17487/RFC1933;April;https://www.rfc-editor.org/info/rfc1933 | |
| RFC1934;;Smith, K.;Ascend's Multilink Protocol Plus (MP+);;;;;RFC 1934;DOI 10.17487/RFC1934;April;https://www.rfc-editor.org/info/rfc1934 | |
| RFC1935;;Quarterman, J. and S. Carl-Mitchell;What is the Internet, Anyway?;;;;;RFC 1935;DOI 10.17487/RFC1935;April;https://www.rfc-editor.org/info/rfc1935 | |
| RFC1936;;Touch, J. and B. Parham;Implementing the Internet Checksum in Hardware;;;;;RFC 1936;DOI 10.17487/RFC1936;April;https://www.rfc-editor.org/info/rfc1936 | |
| RFC1937;;Rekhter, Y. and D. Kandlur;"Local/Remote" Forwarding Decision in Switched Data Link Subnetworks;;;;;RFC 1937;DOI 10.17487/RFC1937;May;https://www.rfc-editor.org/info/rfc1937 | |
| RFC1938;RFC2289;Haller, N. and C. Metz;A One-Time Password System;;;;;RFC 1938;DOI 10.17487/RFC1938;May;https://www.rfc-editor.org/info/rfc1938 | |
| RFC1939;;Myers, J. and M. Rose;Post Office Protocol - Version 3;;;;STD 53;RFC 1939;DOI 10.17487/RFC1939;May;https://www.rfc-editor.org/info/rfc1939 | |
| RFC1940;;Estrin, D., Li, T., Rekhter, Y., Varadhan, K., and D. Zappala;Source Demand Routing: Packet Format and Forwarding Specification (Version 1);;;;;RFC 1940;DOI 10.17487/RFC1940;May;https://www.rfc-editor.org/info/rfc1940 | |
| RFC1941;;Sellers, J. and J. Robichaux;Frequently Asked Questions for Schools;;FYI 22;;;RFC 1941;DOI 10.17487/RFC1941;May;https://www.rfc-editor.org/info/rfc1941 | |
| RFC1942;RFC2854;Raggett, D.;HTML Tables;;;;;RFC 1942;DOI 10.17487/RFC1942;May;https://www.rfc-editor.org/info/rfc1942 | |
| RFC1943;;Jennings, B.;Building an X.500 Directory Service in the US;;;;;RFC 1943;DOI 10.17487/RFC1943;May;https://www.rfc-editor.org/info/rfc1943 | |
| RFC1944;RFC2544;Bradner, S. and J. McQuaid;Benchmarking Methodology for Network Interconnect Devices;;;;;RFC 1944;DOI 10.17487/RFC1944;May;https://www.rfc-editor.org/info/rfc1944 | |
| RFC1945;;Berners-Lee, T., Fielding, R., and H. Frystyk;Hypertext Transfer Protocol -- HTTP/1.0;;;;;RFC 1945;DOI 10.17487/RFC1945;May;https://www.rfc-editor.org/info/rfc1945 | |
| RFC1946;;Jackowski, S.;Native ATM Support for ST2+;;;;;RFC 1946;DOI 10.17487/RFC1946;May;https://www.rfc-editor.org/info/rfc1946 | |
| RFC1947;;Spinellis, D.;Greek Character Encoding for Electronic Mail Messages;;;;;RFC 1947;DOI 10.17487/RFC1947;May;https://www.rfc-editor.org/info/rfc1947 | |
| RFC1948;RFC6528;Bellovin, S.;Defending Against Sequence Number Attacks;;;;;RFC 1948;DOI 10.17487/RFC1948;May;https://www.rfc-editor.org/info/rfc1948 | |
| RFC1949;;Ballardie, A.;Scalable Multicast Key Distribution;;;;;RFC 1949;DOI 10.17487/RFC1949;May;https://www.rfc-editor.org/info/rfc1949 | |
| RFC1950;;Deutsch, P. and J-L. Gailly;ZLIB Compressed Data Format Specification version 3.3;;;;;RFC 1950;DOI 10.17487/RFC1950;May;https://www.rfc-editor.org/info/rfc1950 | |
| RFC1951;;Deutsch, P.;DEFLATE Compressed Data Format Specification version 1.3;;;;;RFC 1951;DOI 10.17487/RFC1951;May;https://www.rfc-editor.org/info/rfc1951 | |
| RFC1952;;Deutsch, P.;GZIP file format specification version 4.3;;;;;RFC 1952;DOI 10.17487/RFC1952;May;https://www.rfc-editor.org/info/rfc1952 | |
| RFC1953;;Newman, P., Edwards, W., Hinden, R., Hoffman, E., Ching Liaw, F., Lyon, T., and G. Minshall;Ipsilon Flow Management Protocol Specification for IPv4 Version 1.0;;;;;RFC 1953;DOI 10.17487/RFC1953;May;https://www.rfc-editor.org/info/rfc1953 | |
| RFC1954;;Newman, P., Edwards, W., Hinden, R., Hoffman, E., Ching Liaw, F., Lyon, T., and G. Minshall;Transmission of Flow Labelled IPv4 on ATM Data Links Ipsilon Version 1.0;;;;;RFC 1954;DOI 10.17487/RFC1954;May;https://www.rfc-editor.org/info/rfc1954 | |
| RFC1955;;Hinden, R.;New Scheme for Internet Routing and Addressing (ENCAPS) for IPNG;;;;;RFC 1955;DOI 10.17487/RFC1955;June;https://www.rfc-editor.org/info/rfc1955 | |
| RFC1956;;Engebretson, D. and R. Plzak;Registration in the MIL Domain;;;;;RFC 1956;DOI 10.17487/RFC1956;June;https://www.rfc-editor.org/info/rfc1956 | |
| RFC1957;;Nelson, R.;Some Observations on Implementations of the Post Office Protocol (POP3);;;;;RFC 1957;DOI 10.17487/RFC1957;June;https://www.rfc-editor.org/info/rfc1957 | |
| RFC1958;;Carpenter, B., Ed.;Architectural Principles of the Internet;;;;;RFC 1958;DOI 10.17487/RFC1958;June;https://www.rfc-editor.org/info/rfc1958 | |
| RFC1959;RFC2255;Howes, T. and M. Smith;An LDAP URL Format;;;;;RFC 1959;DOI 10.17487/RFC1959;June;https://www.rfc-editor.org/info/rfc1959 | |
| RFC1960;RFC2254;Howes, T.;A String Representation of LDAP Search Filters;;;;;RFC 1960;DOI 10.17487/RFC1960;June;https://www.rfc-editor.org/info/rfc1960 | |
| RFC1961;;McMahon, P.;GSS-API Authentication Method for SOCKS Version 5;;;;;RFC 1961;DOI 10.17487/RFC1961;June;https://www.rfc-editor.org/info/rfc1961 | |
| RFC1962;;Rand, D.;The PPP Compression Control Protocol (CCP);;;;;RFC 1962;DOI 10.17487/RFC1962;June;https://www.rfc-editor.org/info/rfc1962 | |
| RFC1963;;Schneider, K. and S. Venters;PPP Serial Data Transport Protocol (SDTP);;;;;RFC 1963;DOI 10.17487/RFC1963;August;https://www.rfc-editor.org/info/rfc1963 | |
| RFC1964;;Linn, J.;The Kerberos Version 5 GSS-API Mechanism;;;;;RFC 1964;DOI 10.17487/RFC1964;June;https://www.rfc-editor.org/info/rfc1964 | |
| RFC1965;RFC3065;Traina, P.;Autonomous System Confederations for BGP;;;;;RFC 1965;DOI 10.17487/RFC1965;June;https://www.rfc-editor.org/info/rfc1965 | |
| RFC1966;RFC4456;Bates, T. and R. Chandra;BGP Route Reflection An alternative to full mesh IBGP;;;;;RFC 1966;DOI 10.17487/RFC1966;June;https://www.rfc-editor.org/info/rfc1966 | |
| RFC1967;;Schneider, K. and R. Friend;PPP LZS-DCP Compression Protocol (LZS-DCP);;;;;RFC 1967;DOI 10.17487/RFC1967;August;https://www.rfc-editor.org/info/rfc1967 | |
| RFC1968;;Meyer, G.;The PPP Encryption Control Protocol (ECP);;;;;RFC 1968;DOI 10.17487/RFC1968;June;https://www.rfc-editor.org/info/rfc1968 | |
| RFC1969;RFC2419;Sklower, K. and G. Meyer;The PPP DES Encryption Protocol (DESE);;;;;RFC 1969;DOI 10.17487/RFC1969;June;https://www.rfc-editor.org/info/rfc1969 | |
| RFC1970;RFC2461;Narten, T., Nordmark, E., and W. Simpson;Neighbor Discovery for IP Version 6 (IPv6);;;;;RFC 1970;DOI 10.17487/RFC1970;August;https://www.rfc-editor.org/info/rfc1970 | |
| RFC1971;RFC2462;Thomson, S. and T. Narten;IPv6 Stateless Address Autoconfiguration;;;;;RFC 1971;DOI 10.17487/RFC1971;August;https://www.rfc-editor.org/info/rfc1971 | |
| RFC1972;RFC2464;Crawford, M.;A Method for the Transmission of IPv6 Packets over Ethernet Networks;;;;;RFC 1972;DOI 10.17487/RFC1972;August;https://www.rfc-editor.org/info/rfc1972 | |
| RFC1973;;Simpson, W.;PPP in Frame Relay;;;;;RFC 1973;DOI 10.17487/RFC1973;June;https://www.rfc-editor.org/info/rfc1973 | |
| RFC1974;;Friend, R. and W. Simpson;PPP Stac LZS Compression Protocol;;;;;RFC 1974;DOI 10.17487/RFC1974;August;https://www.rfc-editor.org/info/rfc1974 | |
| RFC1975;;Schremp, D., Black, J., and J. Weiss;PPP Magnalink Variable Resource Compression;;;;;RFC 1975;DOI 10.17487/RFC1975;August;https://www.rfc-editor.org/info/rfc1975 | |
| RFC1976;;Schneider, K. and S. Venters;PPP for Data Compression in Data Circuit-Terminating Equipment (DCE);;;;;RFC 1976;DOI 10.17487/RFC1976;August;https://www.rfc-editor.org/info/rfc1976 | |
| RFC1977;;Schryver, V.;PPP BSD Compression Protocol;;;;;RFC 1977;DOI 10.17487/RFC1977;August;https://www.rfc-editor.org/info/rfc1977 | |
| RFC1978;;Rand, D.;PPP Predictor Compression Protocol;;;;;RFC 1978;DOI 10.17487/RFC1978;August;https://www.rfc-editor.org/info/rfc1978 | |
| RFC1979;;Woods, J.;PPP Deflate Protocol;;;;;RFC 1979;DOI 10.17487/RFC1979;August;https://www.rfc-editor.org/info/rfc1979 | |
| RFC1980;RFC2854;Seidman, J.;A Proposed Extension to HTML : Client-Side Image Maps;;;;;RFC 1980;DOI 10.17487/RFC1980;August;https://www.rfc-editor.org/info/rfc1980 | |
| RFC1981;RFC8201;McCann, J., Deering, S., and J. Mogul;Path MTU Discovery for IP version 6;;;;;RFC 1981;DOI 10.17487/RFC1981;August;https://www.rfc-editor.org/info/rfc1981 | |
| RFC1982;;Elz, R. and R. Bush;Serial Number Arithmetic;;;;;RFC 1982;DOI 10.17487/RFC1982;August;https://www.rfc-editor.org/info/rfc1982 | |
| RFC1983;;Malkin, G., Ed.;Internet Users' Glossary;;FYI 18;;;RFC 1983;DOI 10.17487/RFC1983;August;https://www.rfc-editor.org/info/rfc1983 | |
| RFC1984;;IAB and IESG;IAB and IESG Statement on Cryptographic Technology and the Internet;;;BCP 200;;RFC 1984;DOI 10.17487/RFC1984;August;https://www.rfc-editor.org/info/rfc1984 | |
| RFC1985;;De Winter, J.;SMTP Service Extension for Remote Message Queue Starting;;;;;RFC 1985;DOI 10.17487/RFC1985;August;https://www.rfc-editor.org/info/rfc1985 | |
| RFC1986;;Polites, W., Wollman, W., Woo, D., and R. Langan;Experiments with a Simple File Transfer Protocol for Radio Links using Enhanced Trivial File Transfer Protocol (ETFTP);;;;;RFC 1986;DOI 10.17487/RFC1986;August;https://www.rfc-editor.org/info/rfc1986 | |
| RFC1987;;Newman, P., Edwards, W., Hinden, R., Hoffman, E., Ching Liaw, F., Lyon, T., and G. Minshall;Ipsilon's General Switch Management Protocol Specification Version 1.1;;;;;RFC 1987;DOI 10.17487/RFC1987;August;https://www.rfc-editor.org/info/rfc1987 | |
| RFC1988;;McAnally, G., Gilbert, D., and J. Flick;Conditional Grant of Rights to Specific Hewlett-Packard Patents In Conjunction With the Internet Engineering Task Force's Internet-Standard Network Management Framework;;;;;RFC 1988;DOI 10.17487/RFC1988;August;https://www.rfc-editor.org/info/rfc1988 | |
| RFC1989;;Simpson, W.;PPP Link Quality Monitoring;;;;;RFC 1989;DOI 10.17487/RFC1989;August;https://www.rfc-editor.org/info/rfc1989 | |
| RFC1990;;Sklower, K., Lloyd, B., McGregor, G., Carr, D., and T. Coradetti;The PPP Multilink Protocol (MP);;;;;RFC 1990;DOI 10.17487/RFC1990;August;https://www.rfc-editor.org/info/rfc1990 | |
| RFC1991;RFC4880;Atkins, D., Stallings, W., and P. Zimmermann;PGP Message Exchange Formats;;;;;RFC 1991;DOI 10.17487/RFC1991;August;https://www.rfc-editor.org/info/rfc1991 | |
| RFC1992;;Castineyra, I., Chiappa, N., and M. Steenstrup;The Nimrod Routing Architecture;;;;;RFC 1992;DOI 10.17487/RFC1992;August;https://www.rfc-editor.org/info/rfc1992 | |
| RFC1993;;Barbir, A., Carr, D., and W. Simpson;PPP Gandalf FZA Compression Protocol;;;;;RFC 1993;DOI 10.17487/RFC1993;August;https://www.rfc-editor.org/info/rfc1993 | |
| RFC1994;;Simpson, W.;PPP Challenge Handshake Authentication Protocol (CHAP);;;;;RFC 1994;DOI 10.17487/RFC1994;August;https://www.rfc-editor.org/info/rfc1994 | |
| RFC1995;;Ohta, M.;Incremental Zone Transfer in DNS;;;;;RFC 1995;DOI 10.17487/RFC1995;August;https://www.rfc-editor.org/info/rfc1995 | |
| RFC1996;;Vixie, P.;A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY);;;;;RFC 1996;DOI 10.17487/RFC1996;August;https://www.rfc-editor.org/info/rfc1996 | |
| RFC1997;;Chandra, R., Traina, P., and T. Li;BGP Communities Attribute;;;;;RFC 1997;DOI 10.17487/RFC1997;August;https://www.rfc-editor.org/info/rfc1997 | |
| RFC1998;;Chen, E. and T. Bates;An Application of the BGP Community Attribute in Multi-home Routing;;;;;RFC 1998;DOI 10.17487/RFC1998;August;https://www.rfc-editor.org/info/rfc1998 | |
| RFC1999;;Elliott, J.;Request for Comments Summary RFC Numbers 1900-1999;;;;;RFC 1999;DOI 10.17487/RFC1999;January;https://www.rfc-editor.org/info/rfc1999 | |
| RFC2000;RFC2200;Postel, J., Ed.;Internet Official Protocol Standards;;;;;RFC 2000;DOI 10.17487/RFC2000;February;https://www.rfc-editor.org/info/rfc2000 | |
| RFC2001;RFC2581;Stevens, W.;TCP Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery Algorithms;;;;;RFC 2001;DOI 10.17487/RFC2001;January;https://www.rfc-editor.org/info/rfc2001 | |
| RFC2002;RFC3220;Perkins, C., Ed.;IP Mobility Support;;;;;RFC 2002;DOI 10.17487/RFC2002;October;https://www.rfc-editor.org/info/rfc2002 | |
| RFC2003;;Perkins, C.;IP Encapsulation within IP;;;;;RFC 2003;DOI 10.17487/RFC2003;October;https://www.rfc-editor.org/info/rfc2003 | |
| RFC2004;;Perkins, C.;Minimal Encapsulation within IP;;;;;RFC 2004;DOI 10.17487/RFC2004;October;https://www.rfc-editor.org/info/rfc2004 | |
| RFC2005;;Solomon, J.;Applicability Statement for IP Mobility Support;;;;;RFC 2005;DOI 10.17487/RFC2005;October;https://www.rfc-editor.org/info/rfc2005 | |
| RFC2006;;Cong, D., Hamlen, M., and C. Perkins;The Definitions of Managed Objects for IP Mobility Support using SMIv2;;;;;RFC 2006;DOI 10.17487/RFC2006;October;https://www.rfc-editor.org/info/rfc2006 | |
| RFC2007;;Foster, J., Isaacs, M., and M. Prior;Catalogue of Network Training Materials;;FYI 29;;;RFC 2007;DOI 10.17487/RFC2007;October;https://www.rfc-editor.org/info/rfc2007 | |
| RFC2008;;Rekhter, Y. and T. Li;Implications of Various Address Allocation Policies for Internet Routing;;;BCP 7;;RFC 2008;DOI 10.17487/RFC2008;October;https://www.rfc-editor.org/info/rfc2008 | |
| RFC2009;;Imielinski, T. and J. Navas;GPS-Based Addressing and Routing;;;;;RFC 2009;DOI 10.17487/RFC2009;November;https://www.rfc-editor.org/info/rfc2009 | |
| RFC2010;RFC2870;Manning, B. and P. Vixie;Operational Criteria for Root Name Servers;;;;;RFC 2010;DOI 10.17487/RFC2010;October;https://www.rfc-editor.org/info/rfc2010 | |
| RFC2011;RFC4293;McCloghrie, K., Ed.;SNMPv2 Management Information Base for the Internet Protocol using SMIv2;;;;;RFC 2011;DOI 10.17487/RFC2011;November;https://www.rfc-editor.org/info/rfc2011 | |
| RFC2012;RFC4022;McCloghrie, K., Ed.;SNMPv2 Management Information Base for the Transmission Control Protocol using SMIv2;;;;;RFC 2012;DOI 10.17487/RFC2012;November;https://www.rfc-editor.org/info/rfc2012 | |
| RFC2013;RFC4113;McCloghrie, K., Ed.;SNMPv2 Management Information Base for the User Datagram Protocol using SMIv2;;;;;RFC 2013;DOI 10.17487/RFC2013;November;https://www.rfc-editor.org/info/rfc2013 | |
| RFC2014;;Weinrib, A. and J. Postel;IRTF Research Group Guidelines and Procedures;;;BCP 8;;RFC 2014;DOI 10.17487/RFC2014;October;https://www.rfc-editor.org/info/rfc2014 | |
| RFC2015;;Elkins, M.;MIME Security with Pretty Good Privacy (PGP);;;;;RFC 2015;DOI 10.17487/RFC2015;October;https://www.rfc-editor.org/info/rfc2015 | |
| RFC2016;;Daigle, L., Deutsch, P., Heelan, B., Alpaugh, C., and M. Maclachlan;Uniform Resource Agents (URAs);;;;;RFC 2016;DOI 10.17487/RFC2016;October;https://www.rfc-editor.org/info/rfc2016 | |
| RFC2017;;Freed, N., Moore, K., and A. Cargille;Definition of the URL MIME External-Body Access-Type;;;;;RFC 2017;DOI 10.17487/RFC2017;October;https://www.rfc-editor.org/info/rfc2017 | |
| RFC2018;;Mathis, M., Mahdavi, J., Floyd, S., and A. Romanow;TCP Selective Acknowledgment Options;;;;;RFC 2018;DOI 10.17487/RFC2018;October;https://www.rfc-editor.org/info/rfc2018 | |
| RFC2019;RFC2467;Crawford, M.;Transmission of IPv6 Packets Over FDDI;;;;;RFC 2019;DOI 10.17487/RFC2019;October;https://www.rfc-editor.org/info/rfc2019 | |
| RFC2020;;Flick, J.;IEEE 802.12 Interface MIB;;;;;RFC 2020;DOI 10.17487/RFC2020;October;https://www.rfc-editor.org/info/rfc2020 | |
| RFC2021;RFC4502;Waldbusser, S.;Remote Network Monitoring Management Information Base Version 2 using SMIv2;;;;;RFC 2021;DOI 10.17487/RFC2021;January;https://www.rfc-editor.org/info/rfc2021 | |
| RFC2022;;Armitage, G.;Support for Multicast over UNI 3.0/3.1 based ATM Networks;;;;;RFC 2022;DOI 10.17487/RFC2022;November;https://www.rfc-editor.org/info/rfc2022 | |
| RFC2023;RFC2472;Haskin, D. and E. Allen;IP Version 6 over PPP;;;;;RFC 2023;DOI 10.17487/RFC2023;October;https://www.rfc-editor.org/info/rfc2023 | |
| RFC2024;;Chen, D., Ed., Gayek, P., and S. Nix;Definitions of Managed Objects for Data Link Switching using SMIv2;;;;;RFC 2024;DOI 10.17487/RFC2024;October;https://www.rfc-editor.org/info/rfc2024 | |
| RFC2025;;Adams, C.;The Simple Public-Key GSS-API Mechanism (SPKM);;;;;RFC 2025;DOI 10.17487/RFC2025;October;https://www.rfc-editor.org/info/rfc2025 | |
| RFC2026;;Bradner, S.;The Internet Standards Process -- Revision 3;;;BCP 9;;RFC 2026;DOI 10.17487/RFC2026;October;https://www.rfc-editor.org/info/rfc2026 | |
| RFC2027;RFC2282;Galvin, J.;IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees;;;;;RFC 2027;DOI 10.17487/RFC2027;October;https://www.rfc-editor.org/info/rfc2027 | |
| RFC2028;;Hovey, R. and S. Bradner;The Organizations Involved in the IETF Standards Process;;;BCP 11;;RFC 2028;DOI 10.17487/RFC2028;October;https://www.rfc-editor.org/info/rfc2028 | |
| RFC2029;;Speer, M. and D. Hoffman;RTP Payload Format of Sun's CellB Video Encoding;;;;;RFC 2029;DOI 10.17487/RFC2029;October;https://www.rfc-editor.org/info/rfc2029 | |
| RFC2030;RFC4330;Mills, D.;Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI;;;;;RFC 2030;DOI 10.17487/RFC2030;October;https://www.rfc-editor.org/info/rfc2030 | |
| RFC2031;RFC8712;Huizer, E.;IETF-ISOC relationship;;;;;RFC 2031;DOI 10.17487/RFC2031;October;https://www.rfc-editor.org/info/rfc2031 | |
| RFC2032;RFC4587;Turletti, T. and C. Huitema;RTP Payload Format for H.261 Video Streams;;;;;RFC 2032;DOI 10.17487/RFC2032;October;https://www.rfc-editor.org/info/rfc2032 | |
| RFC2033;;Myers, J.;Local Mail Transfer Protocol;;;;;RFC 2033;DOI 10.17487/RFC2033;October;https://www.rfc-editor.org/info/rfc2033 | |
| RFC2034;;Freed, N.;SMTP Service Extension for Returning Enhanced Error Codes;;;;;RFC 2034;DOI 10.17487/RFC2034;October;https://www.rfc-editor.org/info/rfc2034 | |
| RFC2035;RFC2435;Berc, L., Fenner, W., Frederick, R., and S. McCanne;RTP Payload Format for JPEG-compressed Video;;;;;RFC 2035;DOI 10.17487/RFC2035;October;https://www.rfc-editor.org/info/rfc2035 | |
| RFC2036;;Huston, G.;Observations on the use of Components of the Class A Address Space within the Internet;;;;;RFC 2036;DOI 10.17487/RFC2036;October;https://www.rfc-editor.org/info/rfc2036 | |
| RFC2037;RFC2737;McCloghrie, K. and A. Bierman;Entity MIB using SMIv2;;;;;RFC 2037;DOI 10.17487/RFC2037;October;https://www.rfc-editor.org/info/rfc2037 | |
| RFC2038;RFC2250;Hoffman, D., Fernando, G., and V. Goyal;RTP Payload Format for MPEG1/MPEG2 Video;;;;;RFC 2038;DOI 10.17487/RFC2038;October;https://www.rfc-editor.org/info/rfc2038 | |
| RFC2039;;Kalbfleisch, C.;Applicability of Standards Track MIBs to Management of World Wide Web Servers;;;;;RFC 2039;DOI 10.17487/RFC2039;November;https://www.rfc-editor.org/info/rfc2039 | |
| RFC2040;;Baldwin, R. and R. Rivest;The RC5, RC5-CBC, RC5-CBC-Pad, and RC5-CTS Algorithms;;;;;RFC 2040;DOI 10.17487/RFC2040;October;https://www.rfc-editor.org/info/rfc2040 | |
| RFC2041;;Noble, B., Nguyen, G., Satyanarayanan, M., and R. Katz;Mobile Network Tracing;;;;;RFC 2041;DOI 10.17487/RFC2041;October;https://www.rfc-editor.org/info/rfc2041 | |
| RFC2042;;Manning, B.;Registering New BGP Attribute Types;;;;;RFC 2042;DOI 10.17487/RFC2042;January;https://www.rfc-editor.org/info/rfc2042 | |
| RFC2043;;Fuqua, A.;The PPP SNA Control Protocol (SNACP);;;;;RFC 2043;DOI 10.17487/RFC2043;October;https://www.rfc-editor.org/info/rfc2043 | |
| RFC2044;RFC2279;Yergeau, F.;UTF-8, a transformation format of Unicode and ISO 10646;;;;;RFC 2044;DOI 10.17487/RFC2044;October;https://www.rfc-editor.org/info/rfc2044 | |
| RFC2045;;Freed, N. and N. Borenstein;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies;;;;;RFC 2045;DOI 10.17487/RFC2045;November;https://www.rfc-editor.org/info/rfc2045 | |
| RFC2046;;Freed, N. and N. Borenstein;Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types;;;;;RFC 2046;DOI 10.17487/RFC2046;November;https://www.rfc-editor.org/info/rfc2046 | |
| RFC2047;;Moore, K.;MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text;;;;;RFC 2047;DOI 10.17487/RFC2047;November;https://www.rfc-editor.org/info/rfc2047 | |
| RFC2048;RFC4288, RFC4289;Freed, N., Klensin, J., and J. Postel;Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures;;;;;RFC 2048;DOI 10.17487/RFC2048;November;https://www.rfc-editor.org/info/rfc2048 | |
| RFC2049;;Freed, N. and N. Borenstein;Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples;;;;;RFC 2049;DOI 10.17487/RFC2049;November;https://www.rfc-editor.org/info/rfc2049 | |
| RFC2050;RFC7020;Hubbard, K., Kosters, M., Conrad, D., Karrenberg, D., and J. Postel;Internet Registry IP Allocation Guidelines;;;;;RFC 2050;DOI 10.17487/RFC2050;November;https://www.rfc-editor.org/info/rfc2050 | |
| RFC2051;;Allen, M., Clouston, B., Kielczewski, Z., Kwan, W., and B. Moore;Definitions of Managed Objects for APPC using SMIv2;;;;;RFC 2051;DOI 10.17487/RFC2051;October;https://www.rfc-editor.org/info/rfc2051 | |
| RFC2052;RFC2782;Gulbrandsen, A. and P. Vixie;A DNS RR for specifying the location of services (DNS SRV);;;;;RFC 2052;DOI 10.17487/RFC2052;October;https://www.rfc-editor.org/info/rfc2052 | |
| RFC2053;;Der-Danieliantz, E.;The AM (Armenia) Domain;;;;;RFC 2053;DOI 10.17487/RFC2053;October;https://www.rfc-editor.org/info/rfc2053 | |
| RFC2054;;Callaghan, B.;WebNFS Client Specification;;;;;RFC 2054;DOI 10.17487/RFC2054;October;https://www.rfc-editor.org/info/rfc2054 | |
| RFC2055;;Callaghan, B.;WebNFS Server Specification;;;;;RFC 2055;DOI 10.17487/RFC2055;October;https://www.rfc-editor.org/info/rfc2055 | |
| RFC2056;;Denenberg, R., Kunze, J., and D. Lynch;Uniform Resource Locators for Z39.50;;;;;RFC 2056;DOI 10.17487/RFC2056;November;https://www.rfc-editor.org/info/rfc2056 | |
| RFC2057;;Bradner, S.;Source Directed Access Control on the Internet;;;;;RFC 2057;DOI 10.17487/RFC2057;November;https://www.rfc-editor.org/info/rfc2057 | |
| RFC2058;RFC2138;Rigney, C., Rubens, A., Simpson, W., and S. Willens;Remote Authentication Dial In User Service (RADIUS);;;;;RFC 2058;DOI 10.17487/RFC2058;January;https://www.rfc-editor.org/info/rfc2058 | |
| RFC2059;RFC2139;Rigney, C.;RADIUS Accounting;;;;;RFC 2059;DOI 10.17487/RFC2059;January;https://www.rfc-editor.org/info/rfc2059 | |
| RFC2060;RFC3501;Crispin, M.;Internet Message Access Protocol - Version 4rev1;;;;;RFC 2060;DOI 10.17487/RFC2060;December;https://www.rfc-editor.org/info/rfc2060 | |
| RFC2061;;Crispin, M.;IMAP4 Compatibility with IMAP2bis;;;;;RFC 2061;DOI 10.17487/RFC2061;December;https://www.rfc-editor.org/info/rfc2061 | |
| RFC2062;;Crispin, M.;Internet Message Access Protocol - Obsolete Syntax;;;;;RFC 2062;DOI 10.17487/RFC2062;December;https://www.rfc-editor.org/info/rfc2062 | |
| RFC2063;RFC2722;Brownlee, N., Mills, C., and G. Ruth;Traffic Flow Measurement: Architecture;;;;;RFC 2063;DOI 10.17487/RFC2063;January;https://www.rfc-editor.org/info/rfc2063 | |
| RFC2064;RFC2720;Brownlee, N.;Traffic Flow Measurement: Meter MIB;;;;;RFC 2064;DOI 10.17487/RFC2064;January;https://www.rfc-editor.org/info/rfc2064 | |
| RFC2065;RFC2535;Eastlake 3rd, D. and C. Kaufman;Domain Name System Security Extensions;;;;;RFC 2065;DOI 10.17487/RFC2065;January;https://www.rfc-editor.org/info/rfc2065 | |
| RFC2066;;Gellens, R.;TELNET CHARSET Option;;;;;RFC 2066;DOI 10.17487/RFC2066;January;https://www.rfc-editor.org/info/rfc2066 | |
| RFC2067;;Renwick, J.;IP over HIPPI;;;;;RFC 2067;DOI 10.17487/RFC2067;January;https://www.rfc-editor.org/info/rfc2067 | |
| RFC2068;RFC2616;Fielding, R., Gettys, J., Mogul, J., Frystyk, H., and T. Berners-Lee;Hypertext Transfer Protocol -- HTTP/1.1;;;;;RFC 2068;DOI 10.17487/RFC2068;January;https://www.rfc-editor.org/info/rfc2068 | |
| RFC2069;RFC2617;Franks, J., Hallam-Baker, P., Hostetler, J., Leach, P., Luotonen, A., Sink, E., and L. Stewart;An Extension to HTTP : Digest Access Authentication;;;;;RFC 2069;DOI 10.17487/RFC2069;January;https://www.rfc-editor.org/info/rfc2069 | |
| RFC2070;RFC2854;Yergeau, F., Nicol, G., Adams, G., and M. Duerst;Internationalization of the Hypertext Markup Language;;;;;RFC 2070;DOI 10.17487/RFC2070;January;https://www.rfc-editor.org/info/rfc2070 | |
| RFC2071;;Ferguson, P. and H. Berkowitz;Network Renumbering Overview: Why would I want it and what is it anyway?;;;;;RFC 2071;DOI 10.17487/RFC2071;January;https://www.rfc-editor.org/info/rfc2071 | |
| RFC2072;;Berkowitz, H.;Router Renumbering Guide;;;;;RFC 2072;DOI 10.17487/RFC2072;January;https://www.rfc-editor.org/info/rfc2072 | |
| RFC2073;RFC2374;Rekhter, Y., Lothberg, P., Hinden, R., Deering, S., and J. Postel;An IPv6 Provider-Based Unicast Address Format;;;;;RFC 2073;DOI 10.17487/RFC2073;January;https://www.rfc-editor.org/info/rfc2073 | |
| RFC2074;RFC2895;Bierman, A. and R. Iddon;Remote Network Monitoring MIB Protocol Identifiers;;;;;RFC 2074;DOI 10.17487/RFC2074;January;https://www.rfc-editor.org/info/rfc2074 | |
| RFC2075;;Partridge, C.;IP Echo Host Service;;;;;RFC 2075;DOI 10.17487/RFC2075;January;https://www.rfc-editor.org/info/rfc2075 | |
| RFC2076;;Palme, J.;Common Internet Message Headers;;;;;RFC 2076;DOI 10.17487/RFC2076;February;https://www.rfc-editor.org/info/rfc2076 | |
| RFC2077;;Nelson, S., Parks, C., and Mitra;The Model Primary Content Type for Multipurpose Internet Mail Extensions;;;;;RFC 2077;DOI 10.17487/RFC2077;January;https://www.rfc-editor.org/info/rfc2077 | |
| RFC2078;RFC2743;Linn, J.;Generic Security Service Application Program Interface, Version 2;;;;;RFC 2078;DOI 10.17487/RFC2078;January;https://www.rfc-editor.org/info/rfc2078 | |
| RFC2079;;Smith, M.;Definition of an X.500 Attribute Type and an Object Class to Hold Uniform Resource Identifiers (URIs);;;;;RFC 2079;DOI 10.17487/RFC2079;January;https://www.rfc-editor.org/info/rfc2079 | |
| RFC2080;;Malkin, G. and R. Minnear;RIPng for IPv6;;;;;RFC 2080;DOI 10.17487/RFC2080;January;https://www.rfc-editor.org/info/rfc2080 | |
| RFC2081;;Malkin, G.;RIPng Protocol Applicability Statement;;;;;RFC 2081;DOI 10.17487/RFC2081;January;https://www.rfc-editor.org/info/rfc2081 | |
| RFC2082;RFC4822;Baker, F. and R. Atkinson;RIP-2 MD5 Authentication;;;;;RFC 2082;DOI 10.17487/RFC2082;January;https://www.rfc-editor.org/info/rfc2082 | |
| RFC2083;;Boutell, T.;PNG (Portable Network Graphics) Specification Version 1.0;;;;;RFC 2083;DOI 10.17487/RFC2083;March;https://www.rfc-editor.org/info/rfc2083 | |
| RFC2084;;Bossert, G., Cooper, S., and W. Drummond;Considerations for Web Transaction Security;;;;;RFC 2084;DOI 10.17487/RFC2084;January;https://www.rfc-editor.org/info/rfc2084 | |
| RFC2085;;Oehler, M. and R. Glenn;HMAC-MD5 IP Authentication with Replay Prevention;;;;;RFC 2085;DOI 10.17487/RFC2085;February;https://www.rfc-editor.org/info/rfc2085 | |
| RFC2086;RFC4314;Myers, J.;IMAP4 ACL extension;;;;;RFC 2086;DOI 10.17487/RFC2086;January;https://www.rfc-editor.org/info/rfc2086 | |
| RFC2087;;Myers, J.;IMAP4 QUOTA extension;;;;;RFC 2087;DOI 10.17487/RFC2087;January;https://www.rfc-editor.org/info/rfc2087 | |
| RFC2088;RFC7888;Myers, J.;IMAP4 non-synchronizing literals;;;;;RFC 2088;DOI 10.17487/RFC2088;January;https://www.rfc-editor.org/info/rfc2088 | |
| RFC2089;RFC2576;Wijnen, B. and D. Levi;V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent;;;;;RFC 2089;DOI 10.17487/RFC2089;January;https://www.rfc-editor.org/info/rfc2089 | |
| RFC2090;;Emberson, A.;TFTP Multicast Option;;;;;RFC 2090;DOI 10.17487/RFC2090;February;https://www.rfc-editor.org/info/rfc2090 | |
| RFC2091;;Meyer, G. and S. Sherry;Triggered Extensions to RIP to Support Demand Circuits;;;;;RFC 2091;DOI 10.17487/RFC2091;January;https://www.rfc-editor.org/info/rfc2091 | |
| RFC2092;;Sherry, S. and G. Meyer;Protocol Analysis for Triggered RIP;;;;;RFC 2092;DOI 10.17487/RFC2092;January;https://www.rfc-editor.org/info/rfc2092 | |
| RFC2093;;Harney, H. and C. Muckenhirn;Group Key Management Protocol (GKMP) Specification;;;;;RFC 2093;DOI 10.17487/RFC2093;July;https://www.rfc-editor.org/info/rfc2093 | |
| RFC2094;;Harney, H. and C. Muckenhirn;Group Key Management Protocol (GKMP) Architecture;;;;;RFC 2094;DOI 10.17487/RFC2094;July;https://www.rfc-editor.org/info/rfc2094 | |
| RFC2095;RFC2195;Klensin, J., Catoe, R., and P. Krumviede;IMAP/POP AUTHorize Extension for Simple Challenge/Response;;;;;RFC 2095;DOI 10.17487/RFC2095;January;https://www.rfc-editor.org/info/rfc2095 | |
| RFC2096;RFC4292;Baker, F.;IP Forwarding Table MIB;;;;;RFC 2096;DOI 10.17487/RFC2096;January;https://www.rfc-editor.org/info/rfc2096 | |
| RFC2097;;Pall, G.;The PPP NetBIOS Frames Control Protocol (NBFCP);;;;;RFC 2097;DOI 10.17487/RFC2097;January;https://www.rfc-editor.org/info/rfc2097 | |
| RFC2098;;Katsube, Y., Nagami, K., and H. Esaki;Toshiba's Router Architecture Extensions for ATM : Overview;;;;;RFC 2098;DOI 10.17487/RFC2098;February;https://www.rfc-editor.org/info/rfc2098 | |
| RFC2099;;Elliott, J.;Request for Comments Summary RFC Numbers 2000-2099;;;;;RFC 2099;DOI 10.17487/RFC2099;March;https://www.rfc-editor.org/info/rfc2099 | |
| RFC2100;;Ashworth, J.;The Naming of Hosts;;;;;RFC 2100;DOI 10.17487/RFC2100;April;https://www.rfc-editor.org/info/rfc2100 | |
| RFC2101;;Carpenter, B., Crowcroft, J., and Y. Rekhter;IPv4 Address Behaviour Today;;;;;RFC 2101;DOI 10.17487/RFC2101;February;https://www.rfc-editor.org/info/rfc2101 | |
| RFC2102;;Ramanathan, R.;Multicast Support for Nimrod : Requirements and Solution Approaches;;;;;RFC 2102;DOI 10.17487/RFC2102;February;https://www.rfc-editor.org/info/rfc2102 | |
| RFC2103;;Ramanathan, R.;Mobility Support for Nimrod : Challenges and Solution Approaches;;;;;RFC 2103;DOI 10.17487/RFC2103;February;https://www.rfc-editor.org/info/rfc2103 | |
| RFC2104;;Krawczyk, H., Bellare, M., and R. Canetti;HMAC: Keyed-Hashing for Message Authentication;;;;;RFC 2104;DOI 10.17487/RFC2104;February;https://www.rfc-editor.org/info/rfc2104 | |
| RFC2105;;Rekhter, Y., Davie, B., Katz, D., Rosen, E., and G. Swallow;Cisco Systems' Tag Switching Architecture Overview;;;;;RFC 2105;DOI 10.17487/RFC2105;February;https://www.rfc-editor.org/info/rfc2105 | |
| RFC2106;RFC2114;Chiang, S., Lee, J., and H. Yasuda;Data Link Switching Remote Access Protocol;;;;;RFC 2106;DOI 10.17487/RFC2106;February;https://www.rfc-editor.org/info/rfc2106 | |
| RFC2107;;Hamzeh, K.;Ascend Tunnel Management Protocol - ATMP;;;;;RFC 2107;DOI 10.17487/RFC2107;February;https://www.rfc-editor.org/info/rfc2107 | |
| RFC2108;;de Graaf, K., Romascanu, D., McMaster, D., and K. McCloghrie;Definitions of Managed Objects for IEEE 802.3 Repeater Devices using SMIv2;;;;;RFC 2108;DOI 10.17487/RFC2108;February;https://www.rfc-editor.org/info/rfc2108 | |
| RFC2109;RFC2965;Kristol, D. and L. Montulli;HTTP State Management Mechanism;;;;;RFC 2109;DOI 10.17487/RFC2109;February;https://www.rfc-editor.org/info/rfc2109 | |
| RFC2110;RFC2557;Palme, J. and A. Hopmann;MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML);;;;;RFC 2110;DOI 10.17487/RFC2110;March;https://www.rfc-editor.org/info/rfc2110 | |
| RFC2111;RFC2392;Levinson, E.;Content-ID and Message-ID Uniform Resource Locators;;;;;RFC 2111;DOI 10.17487/RFC2111;March;https://www.rfc-editor.org/info/rfc2111 | |
| RFC2112;RFC2387;Levinson, E.;The MIME Multipart/Related Content-type;;;;;RFC 2112;DOI 10.17487/RFC2112;March;https://www.rfc-editor.org/info/rfc2112 | |
| RFC2113;;Katz, D.;IP Router Alert Option;;;;;RFC 2113;DOI 10.17487/RFC2113;February;https://www.rfc-editor.org/info/rfc2113 | |
| RFC2114;;Chiang, S., Lee, J., and H. Yasuda;Data Link Switching Client Access Protocol;;;;;RFC 2114;DOI 10.17487/RFC2114;February;https://www.rfc-editor.org/info/rfc2114 | |
| RFC2115;;Brown, C. and F. Baker;Management Information Base for Frame Relay DTEs Using SMIv2;;;;;RFC 2115;DOI 10.17487/RFC2115;September;https://www.rfc-editor.org/info/rfc2115 | |
| RFC2116;;Apple, C. and K. Rossen;X.500 Implementations Catalog-96;;FYI 11;;;RFC 2116;DOI 10.17487/RFC2116;April;https://www.rfc-editor.org/info/rfc2116 | |
| RFC2117;RFC2362;Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S., Handley, M., Jacobson, V., Liu, C., Sharma, P., and L. Wei;Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification;;;;;RFC 2117;DOI 10.17487/RFC2117;June;https://www.rfc-editor.org/info/rfc2117 | |
| RFC2118;;Pall, G.;Microsoft Point-To-Point Compression (MPPC) Protocol;;;;;RFC 2118;DOI 10.17487/RFC2118;March;https://www.rfc-editor.org/info/rfc2118 | |
| RFC2119;;Bradner, S.;Key words for use in RFCs to Indicate Requirement Levels;;;BCP 14;;RFC 2119;DOI 10.17487/RFC2119;March;https://www.rfc-editor.org/info/rfc2119 | |
| RFC2120;;Chadwick, D.;Managing the X.500 Root Naming Context;;;;;RFC 2120;DOI 10.17487/RFC2120;March;https://www.rfc-editor.org/info/rfc2120 | |
| RFC2121;;Armitage, G.;Issues affecting MARS Cluster Size;;;;;RFC 2121;DOI 10.17487/RFC2121;March;https://www.rfc-editor.org/info/rfc2121 | |
| RFC2122;;Mavrakis, D., Layec, H., and K. Kartmann;VEMMI URL Specification;;;;;RFC 2122;DOI 10.17487/RFC2122;March;https://www.rfc-editor.org/info/rfc2122 | |
| RFC2123;;Brownlee, N.;Traffic Flow Measurement: Experiences with NeTraMet;;;;;RFC 2123;DOI 10.17487/RFC2123;March;https://www.rfc-editor.org/info/rfc2123 | |
| RFC2124;;Amsden, P., Amweg, J., Calato, P., Bensley, S., and G. Lyons;Cabletron's Light-weight Flow Admission Protocol Specification Version 1.0;;;;;RFC 2124;DOI 10.17487/RFC2124;March;https://www.rfc-editor.org/info/rfc2124 | |
| RFC2125;;Richards, C. and K. Smith;The PPP Bandwidth Allocation Protocol (BAP) / The PPP Bandwidth Allocation Control Protocol (BACP);;;;;RFC 2125;DOI 10.17487/RFC2125;March;https://www.rfc-editor.org/info/rfc2125 | |
| RFC2126;;Pouffary, Y. and A. Young;ISO Transport Service on top of TCP (ITOT);;;;;RFC 2126;DOI 10.17487/RFC2126;March;https://www.rfc-editor.org/info/rfc2126 | |
| RFC2127;;Roeck, G., Ed.;ISDN Management Information Base using SMIv2;;;;;RFC 2127;DOI 10.17487/RFC2127;March;https://www.rfc-editor.org/info/rfc2127 | |
| RFC2128;;Roeck, G., Ed.;Dial Control Management Information Base using SMIv2;;;;;RFC 2128;DOI 10.17487/RFC2128;March;https://www.rfc-editor.org/info/rfc2128 | |
| RFC2129;;Nagami, K., Katsube, Y., Shobatake, Y., Mogi, A., Matsuzawa, S., Jinmei, T., and H. Esaki;Toshiba's Flow Attribute Notification Protocol (FANP) Specification;;;;;RFC 2129;DOI 10.17487/RFC2129;April;https://www.rfc-editor.org/info/rfc2129 | |
| RFC2130;;Weider, C., Preston, C., Simonsen, K., Alvestrand, H., Atkinson, R., Crispin, M., and P. Svanberg;The Report of the IAB Character Set Workshop held 29 February - 1 March, 1996;;;;;RFC 2130;DOI 10.17487/RFC2130;April;https://www.rfc-editor.org/info/rfc2130 | |
| RFC2131;;Droms, R.;Dynamic Host Configuration Protocol;;;;;RFC 2131;DOI 10.17487/RFC2131;March;https://www.rfc-editor.org/info/rfc2131 | |
| RFC2132;;Alexander, S. and R. Droms;DHCP Options and BOOTP Vendor Extensions;;;;;RFC 2132;DOI 10.17487/RFC2132;March;https://www.rfc-editor.org/info/rfc2132 | |
| RFC2133;RFC2553;Gilligan, R., Thomson, S., Bound, J., and W. Stevens;Basic Socket Interface Extensions for IPv6;;;;;RFC 2133;DOI 10.17487/RFC2133;April;https://www.rfc-editor.org/info/rfc2133 | |
| RFC2134;;ISOC Board of Trustees;Articles of Incorporation of Internet Society;;;;;RFC 2134;DOI 10.17487/RFC2134;April;https://www.rfc-editor.org/info/rfc2134 | |
| RFC2135;;ISOC Board of Trustees;Internet Society By-Laws;;;;;RFC 2135;DOI 10.17487/RFC2135;April;https://www.rfc-editor.org/info/rfc2135 | |
| RFC2136;;Vixie, P., Ed., Thomson, S., Rekhter, Y., and J. Bound;Dynamic Updates in the Domain Name System (DNS UPDATE);;;;;RFC 2136;DOI 10.17487/RFC2136;April;https://www.rfc-editor.org/info/rfc2136 | |
| RFC2137;RFC3007;Eastlake 3rd, D.;Secure Domain Name System Dynamic Update;;;;;RFC 2137;DOI 10.17487/RFC2137;April;https://www.rfc-editor.org/info/rfc2137 | |
| RFC2138;RFC2865;Rigney, C., Rubens, A., Simpson, W., and S. Willens;Remote Authentication Dial In User Service (RADIUS);;;;;RFC 2138;DOI 10.17487/RFC2138;April;https://www.rfc-editor.org/info/rfc2138 | |
| RFC2139;RFC2866;Rigney, C.;RADIUS Accounting;;;;;RFC 2139;DOI 10.17487/RFC2139;April;https://www.rfc-editor.org/info/rfc2139 | |
| RFC2140;;Touch, J.;TCP Control Block Interdependence;;;;;RFC 2140;DOI 10.17487/RFC2140;April;https://www.rfc-editor.org/info/rfc2140 | |
| RFC2141;RFC8141;Moats, R.;URN Syntax;;;;;RFC 2141;DOI 10.17487/RFC2141;May;https://www.rfc-editor.org/info/rfc2141 | |
| RFC2142;;Crocker, D.;Mailbox Names for Common Services, Roles and Functions;;;;;RFC 2142;DOI 10.17487/RFC2142;May;https://www.rfc-editor.org/info/rfc2142 | |
| RFC2143;;Elliston, B.;Encapsulating IP with the Small Computer System Interface;;;;;RFC 2143;DOI 10.17487/RFC2143;May;https://www.rfc-editor.org/info/rfc2143 | |
| RFC2144;;Adams, C.;The CAST-128 Encryption Algorithm;;;;;RFC 2144;DOI 10.17487/RFC2144;May;https://www.rfc-editor.org/info/rfc2144 | |
| RFC2145;RFC7230;Mogul, J., Fielding, R., Gettys, J., and H. Frystyk;Use and Interpretation of HTTP Version Numbers;;;;;RFC 2145;DOI 10.17487/RFC2145;May;https://www.rfc-editor.org/info/rfc2145 | |
| RFC2146;;Federal Networking Council;U.S. Government Internet Domain Names;;;;;RFC 2146;DOI 10.17487/RFC2146;May;https://www.rfc-editor.org/info/rfc2146 | |
| RFC2147;RFC2675;Borman, D.;TCP and UDP over IPv6 Jumbograms;;;;;RFC 2147;DOI 10.17487/RFC2147;May;https://www.rfc-editor.org/info/rfc2147 | |
| RFC2148;;Alvestrand, H. and P. Jurg;Deployment of the Internet White Pages Service;;;BCP 15;;RFC 2148;DOI 10.17487/RFC2148;September;https://www.rfc-editor.org/info/rfc2148 | |
| RFC2149;;Talpade, R. and M. Ammar;Multicast Server Architectures for MARS-based ATM multicasting;;;;;RFC 2149;DOI 10.17487/RFC2149;May;https://www.rfc-editor.org/info/rfc2149 | |
| RFC2150;;Max, J. and W. Stickle;Humanities and Arts: Sharing Center Stage on the Internet;;FYI 31;;;RFC 2150;DOI 10.17487/RFC2150;October;https://www.rfc-editor.org/info/rfc2150 | |
| RFC2151;;Kessler, G. and S. Shepard;A Primer On Internet and TCP/IP Tools and Utilities;;FYI 30;;;RFC 2151;DOI 10.17487/RFC2151;June;https://www.rfc-editor.org/info/rfc2151 | |
| RFC2152;;Goldsmith, D. and M. Davis;UTF-7 A Mail-Safe Transformation Format of Unicode;;;;;RFC 2152;DOI 10.17487/RFC2152;May;https://www.rfc-editor.org/info/rfc2152 | |
| RFC2153;;Simpson, W.;PPP Vendor Extensions;;;;;RFC 2153;DOI 10.17487/RFC2153;May;https://www.rfc-editor.org/info/rfc2153 | |
| RFC2154;;Murphy, S., Badger, M., and B. Wellington;OSPF with Digital Signatures;;;;;RFC 2154;DOI 10.17487/RFC2154;June;https://www.rfc-editor.org/info/rfc2154 | |
| RFC2155;RFC2455;Clouston, B. and B. Moore;Definitions of Managed Objects for APPN using SMIv2;;;;;RFC 2155;DOI 10.17487/RFC2155;June;https://www.rfc-editor.org/info/rfc2155 | |
| RFC2156;;Kille, S.;MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME;;;;;RFC 2156;DOI 10.17487/RFC2156;January;https://www.rfc-editor.org/info/rfc2156 | |
| RFC2157;;Alvestrand, H.;Mapping between X.400 and RFC-822/MIME Message Bodies;;;;;RFC 2157;DOI 10.17487/RFC2157;January;https://www.rfc-editor.org/info/rfc2157 | |
| RFC2158;;Alvestrand, H.;X.400 Image Body Parts;;;;;RFC 2158;DOI 10.17487/RFC2158;January;https://www.rfc-editor.org/info/rfc2158 | |
| RFC2159;;Alvestrand, H.;A MIME Body Part for FAX;;;;;RFC 2159;DOI 10.17487/RFC2159;January;https://www.rfc-editor.org/info/rfc2159 | |
| RFC2160;;Alvestrand, H.;Carrying PostScript in X.400 and MIME;;;;;RFC 2160;DOI 10.17487/RFC2160;January;https://www.rfc-editor.org/info/rfc2160 | |
| RFC2161;;Alvestrand, H.;A MIME Body Part for ODA;;;;;RFC 2161;DOI 10.17487/RFC2161;January;https://www.rfc-editor.org/info/rfc2161 | |
| RFC2162;;Allocchio, C.;MaXIM-11 - Mapping between X.400 / Internet mail and Mail-11 mail;;;;;RFC 2162;DOI 10.17487/RFC2162;January;https://www.rfc-editor.org/info/rfc2162 | |
| RFC2163;;Allocchio, C.;Using the Internet DNS to Distribute MIXER Conformant Global Address Mapping (MCGAM);;;;;RFC 2163;DOI 10.17487/RFC2163;January;https://www.rfc-editor.org/info/rfc2163 | |
| RFC2164;;Kille, S.;Use of an X.500/LDAP directory to support MIXER address mapping;;;;;RFC 2164;DOI 10.17487/RFC2164;January;https://www.rfc-editor.org/info/rfc2164 | |
| RFC2165;;Veizades, J., Guttman, E., Perkins, C., and S. Kaplan;Service Location Protocol;;;;;RFC 2165;DOI 10.17487/RFC2165;June;https://www.rfc-editor.org/info/rfc2165 | |
| RFC2166;;Bryant, D. and P. Brittain;APPN Implementer's Workshop Closed Pages Document DLSw v2.0 Enhancements;;;;;RFC 2166;DOI 10.17487/RFC2166;June;https://www.rfc-editor.org/info/rfc2166 | |
| RFC2167;;Williamson, S., Kosters, M., Blacka, D., Singh, J., and K. Zeilstra;Referral Whois (RWhois) Protocol V1.5;;;;;RFC 2167;DOI 10.17487/RFC2167;June;https://www.rfc-editor.org/info/rfc2167 | |
| RFC2168;RFC3401, RFC3402, RFC3403, RFC3404;Daniel, R. and M. Mealling;Resolution of Uniform Resource Identifiers using the Domain Name System;;;;;RFC 2168;DOI 10.17487/RFC2168;June;https://www.rfc-editor.org/info/rfc2168 | |
| RFC2169;;Daniel, R.;A Trivial Convention for using HTTP in URN Resolution;;;;;RFC 2169;DOI 10.17487/RFC2169;June;https://www.rfc-editor.org/info/rfc2169 | |
| RFC2170;;Almesberger, W., Le Boudec, J., and P. Oechslin;Application REQuested IP over ATM (AREQUIPA);;;;;RFC 2170;DOI 10.17487/RFC2170;July;https://www.rfc-editor.org/info/rfc2170 | |
| RFC2171;;Murakami, K. and M. Maruyama;MAPOS - Multiple Access Protocol over SONET/SDH Version 1;;;;;RFC 2171;DOI 10.17487/RFC2171;June;https://www.rfc-editor.org/info/rfc2171 | |
| RFC2172;;Maruyama, M. and K. Murakami;MAPOS Version 1 Assigned Numbers;;;;;RFC 2172;DOI 10.17487/RFC2172;June;https://www.rfc-editor.org/info/rfc2172 | |
| RFC2173;;Murakami, K. and M. Maruyama;A MAPOS version 1 Extension - Node Switch Protocol;;;;;RFC 2173;DOI 10.17487/RFC2173;June;https://www.rfc-editor.org/info/rfc2173 | |
| RFC2174;;Murakami, K. and M. Maruyama;A MAPOS version 1 Extension - Switch-Switch Protocol;;;;;RFC 2174;DOI 10.17487/RFC2174;June;https://www.rfc-editor.org/info/rfc2174 | |
| RFC2175;;Murakami, K. and M. Maruyama;MAPOS 16 - Multiple Access Protocol over SONET/SDH with 16 Bit Addressing;;;;;RFC 2175;DOI 10.17487/RFC2175;June;https://www.rfc-editor.org/info/rfc2175 | |
| RFC2176;;Murakami, K. and M. Maruyama;IPv4 over MAPOS Version 1;;;;;RFC 2176;DOI 10.17487/RFC2176;June;https://www.rfc-editor.org/info/rfc2176 | |
| RFC2177;;Leiba, B.;IMAP4 IDLE command;;;;;RFC 2177;DOI 10.17487/RFC2177;June;https://www.rfc-editor.org/info/rfc2177 | |
| RFC2178;RFC2328;Moy, J.;OSPF Version 2;;;;;RFC 2178;DOI 10.17487/RFC2178;July;https://www.rfc-editor.org/info/rfc2178 | |
| RFC2179;;Gwinn, A.;Network Security For Trade Shows;;;;;RFC 2179;DOI 10.17487/RFC2179;July;https://www.rfc-editor.org/info/rfc2179 | |
| RFC2180;;Gahrns, M.;IMAP4 Multi-Accessed Mailbox Practice;;;;;RFC 2180;DOI 10.17487/RFC2180;July;https://www.rfc-editor.org/info/rfc2180 | |
| RFC2181;;Elz, R. and R. Bush;Clarifications to the DNS Specification;;;;;RFC 2181;DOI 10.17487/RFC2181;July;https://www.rfc-editor.org/info/rfc2181 | |
| RFC2182;;Elz, R., Bush, R., Bradner, S., and M. Patton;Selection and Operation of Secondary DNS Servers;;;BCP 16;;RFC 2182;DOI 10.17487/RFC2182;July;https://www.rfc-editor.org/info/rfc2182 | |
| RFC2183;;Troost, R., Dorner, S., and K. Moore, Ed.;Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field;;;;;RFC 2183;DOI 10.17487/RFC2183;August;https://www.rfc-editor.org/info/rfc2183 | |
| RFC2184;RFC2231;Freed, N. and K. Moore;MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations;;;;;RFC 2184;DOI 10.17487/RFC2184;August;https://www.rfc-editor.org/info/rfc2184 | |
| RFC2185;;Callon, R. and D. Haskin;Routing Aspects of IPv6 Transition;;;;;RFC 2185;DOI 10.17487/RFC2185;September;https://www.rfc-editor.org/info/rfc2185 | |
| RFC2186;;Wessels, D. and K. Claffy;Internet Cache Protocol (ICP), version 2;;;;;RFC 2186;DOI 10.17487/RFC2186;September;https://www.rfc-editor.org/info/rfc2186 | |
| RFC2187;;Wessels, D. and K. Claffy;Application of Internet Cache Protocol (ICP), version 2;;;;;RFC 2187;DOI 10.17487/RFC2187;September;https://www.rfc-editor.org/info/rfc2187 | |
| RFC2188;;Banan, M., Taylor, M., and J. Cheng;AT&T/Neda's Efficient Short Remote Operations (ESRO) Protocol Specification Version 1.2;;;;;RFC 2188;DOI 10.17487/RFC2188;September;https://www.rfc-editor.org/info/rfc2188 | |
| RFC2189;;Ballardie, A.;Core Based Trees (CBT version 2) Multicast Routing -- Protocol Specification --;;;;;RFC 2189;DOI 10.17487/RFC2189;September;https://www.rfc-editor.org/info/rfc2189 | |
| RFC2190;;Zhu, C.;RTP Payload Format for H.263 Video Streams;;;;;RFC 2190;DOI 10.17487/RFC2190;September;https://www.rfc-editor.org/info/rfc2190 | |
| RFC2191;;Armitage, G.;VENUS - Very Extensive Non-Unicast Service;;;;;RFC 2191;DOI 10.17487/RFC2191;September;https://www.rfc-editor.org/info/rfc2191 | |
| RFC2192;RFC5092;Newman, C.;IMAP URL Scheme;;;;;RFC 2192;DOI 10.17487/RFC2192;September;https://www.rfc-editor.org/info/rfc2192 | |
| RFC2193;;Gahrns, M.;IMAP4 Mailbox Referrals;;;;;RFC 2193;DOI 10.17487/RFC2193;September;https://www.rfc-editor.org/info/rfc2193 | |
| RFC2194;;Aboba, B., Lu, J., Alsop, J., Ding, J., and W. Wang;Review of Roaming Implementations;;;;;RFC 2194;DOI 10.17487/RFC2194;September;https://www.rfc-editor.org/info/rfc2194 | |
| RFC2195;;Klensin, J., Catoe, R., and P. Krumviede;IMAP/POP AUTHorize Extension for Simple Challenge/Response;;;;;RFC 2195;DOI 10.17487/RFC2195;September;https://www.rfc-editor.org/info/rfc2195 | |
| RFC2196;;Fraser, B.;Site Security Handbook;;FYI 8;;;RFC 2196;DOI 10.17487/RFC2196;September;https://www.rfc-editor.org/info/rfc2196 | |
| RFC2197;RFC2920;Freed, N.;SMTP Service Extension for Command Pipelining;;;;;RFC 2197;DOI 10.17487/RFC2197;September;https://www.rfc-editor.org/info/rfc2197 | |
| RFC2198;;Perkins, C., Kouvelas, I., Hodson, O., Hardman, V., Handley, M., Bolot, J., Vega-Garcia, A., and S. Fosse-Parisis;RTP Payload for Redundant Audio Data;;;;;RFC 2198;DOI 10.17487/RFC2198;September;https://www.rfc-editor.org/info/rfc2198 | |
| RFC2199;;Ramos, A.;Request for Comments Summary RFC Numbers 2100-2199;;;;;RFC 2199;DOI 10.17487/RFC2199;January;https://www.rfc-editor.org/info/rfc2199 | |
| RFC2200;RFC2300;Postel, J.;Internet Official Protocol Standards;;;;;RFC 2200;DOI 10.17487/RFC2200;June;https://www.rfc-editor.org/info/rfc2200 | |
| RFC2201;;Ballardie, A.;Core Based Trees (CBT) Multicast Routing Architecture;;;;;RFC 2201;DOI 10.17487/RFC2201;September;https://www.rfc-editor.org/info/rfc2201 | |
| RFC2202;;Cheng, P. and R. Glenn;Test Cases for HMAC-MD5 and HMAC-SHA-1;;;;;RFC 2202;DOI 10.17487/RFC2202;September;https://www.rfc-editor.org/info/rfc2202 | |
| RFC2203;;Eisler, M., Chiu, A., and L. Ling;RPCSEC_GSS Protocol Specification;;;;;RFC 2203;DOI 10.17487/RFC2203;September;https://www.rfc-editor.org/info/rfc2203 | |
| RFC2204;RFC5024;Nash, D.;ODETTE File Transfer Protocol;;;;;RFC 2204;DOI 10.17487/RFC2204;September;https://www.rfc-editor.org/info/rfc2204 | |
| RFC2205;;Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S. Jamin;Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification;;;;;RFC 2205;DOI 10.17487/RFC2205;September;https://www.rfc-editor.org/info/rfc2205 | |
| RFC2206;;Baker, F., Krawczyk, J., and A. Sastry;RSVP Management Information Base using SMIv2;;;;;RFC 2206;DOI 10.17487/RFC2206;September;https://www.rfc-editor.org/info/rfc2206 | |
| RFC2207;;Berger, L. and T. O'Malley;RSVP Extensions for IPSEC Data Flows;;;;;RFC 2207;DOI 10.17487/RFC2207;September;https://www.rfc-editor.org/info/rfc2207 | |
| RFC2208;;Mankin, A., Ed., Baker, F., Braden, B., Bradner, S., O'Dell, M., Romanow, A., Weinrib, A., and L. Zhang;Resource ReSerVation Protocol (RSVP) -- Version 1 Applicability Statement Some Guidelines on Deployment;;;;;RFC 2208;DOI 10.17487/RFC2208;September;https://www.rfc-editor.org/info/rfc2208 | |
| RFC2209;;Braden, R. and L. Zhang;Resource ReSerVation Protocol (RSVP) -- Version 1 Message Processing Rules;;;;;RFC 2209;DOI 10.17487/RFC2209;September;https://www.rfc-editor.org/info/rfc2209 | |
| RFC2210;;Wroclawski, J.;The Use of RSVP with IETF Integrated Services;;;;;RFC 2210;DOI 10.17487/RFC2210;September;https://www.rfc-editor.org/info/rfc2210 | |
| RFC2211;;Wroclawski, J.;Specification of the Controlled-Load Network Element Service;;;;;RFC 2211;DOI 10.17487/RFC2211;September;https://www.rfc-editor.org/info/rfc2211 | |
| RFC2212;;Shenker, S., Partridge, C., and R. Guerin;Specification of Guaranteed Quality of Service;;;;;RFC 2212;DOI 10.17487/RFC2212;September;https://www.rfc-editor.org/info/rfc2212 | |
| RFC2213;;Baker, F., Krawczyk, J., and A. Sastry;Integrated Services Management Information Base using SMIv2;;;;;RFC 2213;DOI 10.17487/RFC2213;September;https://www.rfc-editor.org/info/rfc2213 | |
| RFC2214;;Baker, F., Krawczyk, J., and A. Sastry;Integrated Services Management Information Base Guaranteed Service Extensions using SMIv2;;;;;RFC 2214;DOI 10.17487/RFC2214;September;https://www.rfc-editor.org/info/rfc2214 | |
| RFC2215;;Shenker, S. and J. Wroclawski;General Characterization Parameters for Integrated Service Network Elements;;;;;RFC 2215;DOI 10.17487/RFC2215;September;https://www.rfc-editor.org/info/rfc2215 | |
| RFC2216;;Shenker, S. and J. Wroclawski;Network Element Service Specification Template;;;;;RFC 2216;DOI 10.17487/RFC2216;September;https://www.rfc-editor.org/info/rfc2216 | |
| RFC2217;;Clark, G.;Telnet Com Port Control Option;;;;;RFC 2217;DOI 10.17487/RFC2217;October;https://www.rfc-editor.org/info/rfc2217 | |
| RFC2218;;Genovese, T. and B. Jennings;A Common Schema for the Internet White Pages Service;;;;;RFC 2218;DOI 10.17487/RFC2218;October;https://www.rfc-editor.org/info/rfc2218 | |
| RFC2219;;Hamilton, M. and R. Wright;Use of DNS Aliases for Network Services;;;BCP 17;;RFC 2219;DOI 10.17487/RFC2219;October;https://www.rfc-editor.org/info/rfc2219 | |
| RFC2220;;Guenther, R.;The Application/MARC Content-type;;;;;RFC 2220;DOI 10.17487/RFC2220;October;https://www.rfc-editor.org/info/rfc2220 | |
| RFC2221;;Gahrns, M.;IMAP4 Login Referrals;;;;;RFC 2221;DOI 10.17487/RFC2221;October;https://www.rfc-editor.org/info/rfc2221 | |
| RFC2222;RFC4422, RFC4752;Myers, J.;Simple Authentication and Security Layer (SASL);;;;;RFC 2222;DOI 10.17487/RFC2222;October;https://www.rfc-editor.org/info/rfc2222 | |
| RFC2223;RFC7322;Postel, J. and J. Reynolds;Instructions to RFC Authors;;;;;RFC 2223;DOI 10.17487/RFC2223;October;https://www.rfc-editor.org/info/rfc2223 | |
| RFC2224;;Callaghan, B.;NFS URL Scheme;;;;;RFC 2224;DOI 10.17487/RFC2224;October;https://www.rfc-editor.org/info/rfc2224 | |
| RFC2225;;Laubach, M. and J. Halpern;Classical IP and ARP over ATM;;;;;RFC 2225;DOI 10.17487/RFC2225;April;https://www.rfc-editor.org/info/rfc2225 | |
| RFC2226;;Smith, T. and G. Armitage;IP Broadcast over ATM Networks;;;;;RFC 2226;DOI 10.17487/RFC2226;October;https://www.rfc-editor.org/info/rfc2226 | |
| RFC2227;;Mogul, J. and P. Leach;Simple Hit-Metering and Usage-Limiting for HTTP;;;;;RFC 2227;DOI 10.17487/RFC2227;October;https://www.rfc-editor.org/info/rfc2227 | |
| RFC2228;;Horowitz, M. and S. Lunt;FTP Security Extensions;;;;;RFC 2228;DOI 10.17487/RFC2228;October;https://www.rfc-editor.org/info/rfc2228 | |
| RFC2229;;Faith, R. and B. Martin;A Dictionary Server Protocol;;;;;RFC 2229;DOI 10.17487/RFC2229;October;https://www.rfc-editor.org/info/rfc2229 | |
| RFC2230;;Atkinson, R.;Key Exchange Delegation Record for the DNS;;;;;RFC 2230;DOI 10.17487/RFC2230;November;https://www.rfc-editor.org/info/rfc2230 | |
| RFC2231;;Freed, N. and K. Moore;MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations;;;;;RFC 2231;DOI 10.17487/RFC2231;November;https://www.rfc-editor.org/info/rfc2231 | |
| RFC2232;;Clouston, B., Ed., and B. Moore, Ed.;Definitions of Managed Objects for DLUR using SMIv2;;;;;RFC 2232;DOI 10.17487/RFC2232;November;https://www.rfc-editor.org/info/rfc2232 | |
| RFC2233;RFC2863;McCloghrie, K. and F. Kastenholz;The Interfaces Group MIB using SMIv2;;;;;RFC 2233;DOI 10.17487/RFC2233;November;https://www.rfc-editor.org/info/rfc2233 | |
| RFC2234;RFC4234;Crocker, D., Ed., and P. Overell;Augmented BNF for Syntax Specifications: ABNF;;;;;RFC 2234;DOI 10.17487/RFC2234;November;https://www.rfc-editor.org/info/rfc2234 | |
| RFC2235;;Zakon, R.;Hobbes' Internet Timeline;;FYI 32;;;RFC 2235;DOI 10.17487/RFC2235;November;https://www.rfc-editor.org/info/rfc2235 | |
| RFC2236;;Fenner, W.;Internet Group Management Protocol, Version 2;;;;;RFC 2236;DOI 10.17487/RFC2236;November;https://www.rfc-editor.org/info/rfc2236 | |
| RFC2237;;Tamaru, K.;Japanese Character Encoding for Internet Messages;;;;;RFC 2237;DOI 10.17487/RFC2237;November;https://www.rfc-editor.org/info/rfc2237 | |
| RFC2238;;Clouston, B., Ed., and B. Moore, Ed.;Definitions of Managed Objects for HPR using SMIv2;;;;;RFC 2238;DOI 10.17487/RFC2238;November;https://www.rfc-editor.org/info/rfc2238 | |
| RFC2239;RFC2668;de Graaf, K., Romascanu, D., McMaster, D., McCloghrie, K., and S. Roberts;Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2;;;;;RFC 2239;DOI 10.17487/RFC2239;November;https://www.rfc-editor.org/info/rfc2239 | |
| RFC2240;RFC2352;Vaughan, O.;A Legal Basis for Domain Name Allocation;;;;;RFC 2240;DOI 10.17487/RFC2240;November;https://www.rfc-editor.org/info/rfc2240 | |
| RFC2241;;Provan, D.;DHCP Options for Novell Directory Services;;;;;RFC 2241;DOI 10.17487/RFC2241;November;https://www.rfc-editor.org/info/rfc2241 | |
| RFC2242;;Droms, R. and K. Fong;NetWare/IP Domain Name and Information;;;;;RFC 2242;DOI 10.17487/RFC2242;November;https://www.rfc-editor.org/info/rfc2242 | |
| RFC2243;;Metz, C.;OTP Extended Responses;;;;;RFC 2243;DOI 10.17487/RFC2243;November;https://www.rfc-editor.org/info/rfc2243 | |
| RFC2244;;Newman, C. and J. Myers;ACAP -- Application Configuration Access Protocol;;;;;RFC 2244;DOI 10.17487/RFC2244;November;https://www.rfc-editor.org/info/rfc2244 | |
| RFC2245;RFC4505;Newman, C.;Anonymous SASL Mechanism;;;;;RFC 2245;DOI 10.17487/RFC2245;November;https://www.rfc-editor.org/info/rfc2245 | |
| RFC2246;RFC4346;Dierks, T. and C. Allen;The TLS Protocol Version 1.0;;;;;RFC 2246;DOI 10.17487/RFC2246;January;https://www.rfc-editor.org/info/rfc2246 | |
| RFC2247;;Kille, S., Wahl, M., Grimstad, A., Huber, R., and S. Sataluri;Using Domains in LDAP/X.500 Distinguished Names;;;;;RFC 2247;DOI 10.17487/RFC2247;January;https://www.rfc-editor.org/info/rfc2247 | |
| RFC2248;RFC2788;Freed, N. and S. Kille;Network Services Monitoring MIB;;;;;RFC 2248;DOI 10.17487/RFC2248;January;https://www.rfc-editor.org/info/rfc2248 | |
| RFC2249;RFC2789;Freed, N. and S. Kille;Mail Monitoring MIB;;;;;RFC 2249;DOI 10.17487/RFC2249;January;https://www.rfc-editor.org/info/rfc2249 | |
| RFC2250;;Hoffman, D., Fernando, G., Goyal, V., and M. Civanlar;RTP Payload Format for MPEG1/MPEG2 Video;;;;;RFC 2250;DOI 10.17487/RFC2250;January;https://www.rfc-editor.org/info/rfc2250 | |
| RFC2251;RFC4510, RFC4511, RFC4513, RFC4512;Wahl, M., Howes, T., and S. Kille;Lightweight Directory Access Protocol (v3);;;;;RFC 2251;DOI 10.17487/RFC2251;December;https://www.rfc-editor.org/info/rfc2251 | |
| RFC2252;RFC4510, RFC4517, RFC4523, RFC4512;Wahl, M., Coulbeck, A., Howes, T., and S. Kille;Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions;;;;;RFC 2252;DOI 10.17487/RFC2252;December;https://www.rfc-editor.org/info/rfc2252 | |
| RFC2253;RFC4510, RFC4514;Wahl, M., Kille, S., and T. Howes;Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names;;;;;RFC 2253;DOI 10.17487/RFC2253;December;https://www.rfc-editor.org/info/rfc2253 | |
| RFC2254;RFC4510, RFC4515;Howes, T.;The String Representation of LDAP Search Filters;;;;;RFC 2254;DOI 10.17487/RFC2254;December;https://www.rfc-editor.org/info/rfc2254 | |
| RFC2255;RFC4510, RFC4516;Howes, T. and M. Smith;The LDAP URL Format;;;;;RFC 2255;DOI 10.17487/RFC2255;December;https://www.rfc-editor.org/info/rfc2255 | |
| RFC2256;RFC4517, RFC4519, RFC4523, RFC4512, RFC4510;Wahl, M.;A Summary of the X.500(96) User Schema for use with LDAPv3;;;;;RFC 2256;DOI 10.17487/RFC2256;December;https://www.rfc-editor.org/info/rfc2256 | |
| RFC2257;RFC2741;Daniele, M., Wijnen, B., and D. Francisco;Agent Extensibility (AgentX) Protocol Version 1;;;;;RFC 2257;DOI 10.17487/RFC2257;January;https://www.rfc-editor.org/info/rfc2257 | |
| RFC2258;;Ordille, J.;Internet Nomenclator Project;;;;;RFC 2258;DOI 10.17487/RFC2258;January;https://www.rfc-editor.org/info/rfc2258 | |
| RFC2259;;Elliott, J. and J. Ordille;Simple Nomenclator Query Protocol (SNQP);;;;;RFC 2259;DOI 10.17487/RFC2259;January;https://www.rfc-editor.org/info/rfc2259 | |
| RFC2260;;Bates, T. and Y. Rekhter;Scalable Support for Multi-homed Multi-provider Connectivity;;;;;RFC 2260;DOI 10.17487/RFC2260;January;https://www.rfc-editor.org/info/rfc2260 | |
| RFC2261;RFC2271;Harrington, D., Presuhn, R., and B. Wijnen;An Architecture for Describing SNMP Management Frameworks;;;;;RFC 2261;DOI 10.17487/RFC2261;January;https://www.rfc-editor.org/info/rfc2261 | |
| RFC2262;RFC2272;Case, J., Harrington, D., Presuhn, R., and B. Wijnen;Message Processing and Dispatching for the Simple Network Management Protocol (SNMP);;;;;RFC 2262;DOI 10.17487/RFC2262;January;https://www.rfc-editor.org/info/rfc2262 | |
| RFC2263;RFC2273;Levi, D., Meyer, P., and B. Stewart;SNMPv3 Applications;;;;;RFC 2263;DOI 10.17487/RFC2263;January;https://www.rfc-editor.org/info/rfc2263 | |
| RFC2264;RFC2274;Blumenthal, U. and B. Wijnen;User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3);;;;;RFC 2264;DOI 10.17487/RFC2264;January;https://www.rfc-editor.org/info/rfc2264 | |
| RFC2265;RFC2275;Wijnen, B., Presuhn, R., and K. McCloghrie;View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP);;;;;RFC 2265;DOI 10.17487/RFC2265;January;https://www.rfc-editor.org/info/rfc2265 | |
| RFC2266;;Flick, J.;Definitions of Managed Objects for IEEE 802.12 Repeater Devices;;;;;RFC 2266;DOI 10.17487/RFC2266;January;https://www.rfc-editor.org/info/rfc2266 | |
| RFC2267;RFC2827;Ferguson, P. and D. Senie;Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing;;;;;RFC 2267;DOI 10.17487/RFC2267;January;https://www.rfc-editor.org/info/rfc2267 | |
| RFC2268;;Rivest, R.;A Description of the RC2(r) Encryption Algorithm;;;;;RFC 2268;DOI 10.17487/RFC2268;March;https://www.rfc-editor.org/info/rfc2268 | |
| RFC2269;;Armitage, G.;Using the MARS Model in non-ATM NBMA Networks;;;;;RFC 2269;DOI 10.17487/RFC2269;January;https://www.rfc-editor.org/info/rfc2269 | |
| RFC2270;;Stewart, J., Bates, T., Chandra, R., and E. Chen;Using a Dedicated AS for Sites Homed to a Single Provider;;;;;RFC 2270;DOI 10.17487/RFC2270;January;https://www.rfc-editor.org/info/rfc2270 | |
| RFC2271;RFC2571;Harrington, D., Presuhn, R., and B. Wijnen;An Architecture for Describing SNMP Management Frameworks;;;;;RFC 2271;DOI 10.17487/RFC2271;January;https://www.rfc-editor.org/info/rfc2271 | |
| RFC2272;RFC2572;Case, J., Harrington, D., Presuhn, R., and B. Wijnen;Message Processing and Dispatching for the Simple Network Management Protocol (SNMP);;;;;RFC 2272;DOI 10.17487/RFC2272;January;https://www.rfc-editor.org/info/rfc2272 | |
| RFC2273;RFC2573;Levi, D., Meyer, P., and B. Stewart;SNMPv3 Applications;;;;;RFC 2273;DOI 10.17487/RFC2273;January;https://www.rfc-editor.org/info/rfc2273 | |
| RFC2274;RFC2574;Blumenthal, U. and B. Wijnen;User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3);;;;;RFC 2274;DOI 10.17487/RFC2274;January;https://www.rfc-editor.org/info/rfc2274 | |
| RFC2275;RFC2575;Wijnen, B., Presuhn, R., and K. McCloghrie;View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP);;;;;RFC 2275;DOI 10.17487/RFC2275;January;https://www.rfc-editor.org/info/rfc2275 | |
| RFC2276;;Sollins, K.;Architectural Principles of Uniform Resource Name Resolution;;;;;RFC 2276;DOI 10.17487/RFC2276;January;https://www.rfc-editor.org/info/rfc2276 | |
| RFC2277;;Alvestrand, H.;IETF Policy on Character Sets and Languages;;;BCP 18;;RFC 2277;DOI 10.17487/RFC2277;January;https://www.rfc-editor.org/info/rfc2277 | |
| RFC2278;RFC2978;Freed, N. and J. Postel;IANA Charset Registration Procedures;;;;;RFC 2278;DOI 10.17487/RFC2278;January;https://www.rfc-editor.org/info/rfc2278 | |
| RFC2279;RFC3629;Yergeau, F.;UTF-8, a transformation format of ISO 10646;;;;;RFC 2279;DOI 10.17487/RFC2279;January;https://www.rfc-editor.org/info/rfc2279 | |
| RFC2280;RFC2622;Alaettinoglu, C., Bates, T., Gerich, E., Karrenberg, D., Meyer, D., Terpstra, M., and C. Villamizar;Routing Policy Specification Language (RPSL);;;;;RFC 2280;DOI 10.17487/RFC2280;January;https://www.rfc-editor.org/info/rfc2280 | |
| RFC2281;;Li, T., Cole, B., Morton, P., and D. Li;Cisco Hot Standby Router Protocol (HSRP);;;;;RFC 2281;DOI 10.17487/RFC2281;March;https://www.rfc-editor.org/info/rfc2281 | |
| RFC2282;RFC2727;Galvin, J.;IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees;;;;;RFC 2282;DOI 10.17487/RFC2282;February;https://www.rfc-editor.org/info/rfc2282 | |
| RFC2283;RFC2858;Bates, T., Chandra, R., Katz, D., and Y. Rekhter;Multiprotocol Extensions for BGP-4;;;;;RFC 2283;DOI 10.17487/RFC2283;February;https://www.rfc-editor.org/info/rfc2283 | |
| RFC2284;RFC3748;Blunk, L. and J. Vollbrecht;PPP Extensible Authentication Protocol (EAP);;;;;RFC 2284;DOI 10.17487/RFC2284;March;https://www.rfc-editor.org/info/rfc2284 | |
| RFC2285;;Mandeville, R.;Benchmarking Terminology for LAN Switching Devices;;;;;RFC 2285;DOI 10.17487/RFC2285;February;https://www.rfc-editor.org/info/rfc2285 | |
| RFC2286;;Kapp, J.;Test Cases for HMAC-RIPEMD160 and HMAC-RIPEMD128;;;;;RFC 2286;DOI 10.17487/RFC2286;February;https://www.rfc-editor.org/info/rfc2286 | |
| RFC2287;;Krupczak, C. and J. Saperia;Definitions of System-Level Managed Objects for Applications;;;;;RFC 2287;DOI 10.17487/RFC2287;February;https://www.rfc-editor.org/info/rfc2287 | |
| RFC2288;;Lynch, C., Preston, C., and R. Daniel;Using Existing Bibliographic Identifiers as Uniform Resource Names;;;;;RFC 2288;DOI 10.17487/RFC2288;February;https://www.rfc-editor.org/info/rfc2288 | |
| RFC2289;;Haller, N., Metz, C., Nesser, P., and M. Straw;A One-Time Password System;;;;STD 61;RFC 2289;DOI 10.17487/RFC2289;February;https://www.rfc-editor.org/info/rfc2289 | |
| RFC2290;;Solomon, J. and S. Glass;Mobile-IPv4 Configuration Option for PPP IPCP;;;;;RFC 2290;DOI 10.17487/RFC2290;February;https://www.rfc-editor.org/info/rfc2290 | |
| RFC2291;;Slein, J., Vitali, F., Whitehead, E., and D. Durand;Requirements for a Distributed Authoring and Versioning Protocol for the World Wide Web;;;;;RFC 2291;DOI 10.17487/RFC2291;February;https://www.rfc-editor.org/info/rfc2291 | |
| RFC2292;RFC3542;Stevens, W. and M. Thomas;Advanced Sockets API for IPv6;;;;;RFC 2292;DOI 10.17487/RFC2292;February;https://www.rfc-editor.org/info/rfc2292 | |
| RFC2293;;Kille, S.;Representing Tables and Subtrees in the X.500 Directory;;;;;RFC 2293;DOI 10.17487/RFC2293;March;https://www.rfc-editor.org/info/rfc2293 | |
| RFC2294;;Kille, S.;Representing the O/R Address hierarchy in the X.500 Directory Information Tree;;;;;RFC 2294;DOI 10.17487/RFC2294;March;https://www.rfc-editor.org/info/rfc2294 | |
| RFC2295;;Holtman, K. and A. Mutz;Transparent Content Negotiation in HTTP;;;;;RFC 2295;DOI 10.17487/RFC2295;March;https://www.rfc-editor.org/info/rfc2295 | |
| RFC2296;;Holtman, K. and A. Mutz;HTTP Remote Variant Selection Algorithm -- RVSA/1.0;;;;;RFC 2296;DOI 10.17487/RFC2296;March;https://www.rfc-editor.org/info/rfc2296 | |
| RFC2297;;Newman, P., Edwards, W., Hinden, R., Hoffman, E., Ching Liaw, F., Lyon, T., and G. Minshall;Ipsilon's General Switch Management Protocol Specification Version 2.0;;;;;RFC 2297;DOI 10.17487/RFC2297;March;https://www.rfc-editor.org/info/rfc2297 | |
| RFC2298;RFC3798;Fajman, R.;An Extensible Message Format for Message Disposition Notifications;;;;;RFC 2298;DOI 10.17487/RFC2298;March;https://www.rfc-editor.org/info/rfc2298 | |
| RFC2299;;Ramos, A.;Request for Comments Summary;;;;;RFC 2299;DOI 10.17487/RFC2299;January;https://www.rfc-editor.org/info/rfc2299 | |
| RFC2300;RFC2400;Postel, J.;Internet Official Protocol Standards;;;;;RFC 2300;DOI 10.17487/RFC2300;May;https://www.rfc-editor.org/info/rfc2300 | |
| RFC2301;RFC3949;McIntyre, L., Zilles, S., Buckley, R., Venable, D., Parsons, G., and J. Rafferty;File Format for Internet Fax;;;;;RFC 2301;DOI 10.17487/RFC2301;March;https://www.rfc-editor.org/info/rfc2301 | |
| RFC2302;RFC3302;Parsons, G., Rafferty, J., and S. Zilles;Tag Image File Format (TIFF) - image/tiff MIME Sub-type Registration;;;;;RFC 2302;DOI 10.17487/RFC2302;March;https://www.rfc-editor.org/info/rfc2302 | |
| RFC2303;RFC3191;Allocchio, C.;Minimal PSTN address format in Internet Mail;;;;;RFC 2303;DOI 10.17487/RFC2303;March;https://www.rfc-editor.org/info/rfc2303 | |
| RFC2304;RFC3192;Allocchio, C.;Minimal FAX address format in Internet Mail;;;;;RFC 2304;DOI 10.17487/RFC2304;March;https://www.rfc-editor.org/info/rfc2304 | |
| RFC2305;RFC3965;Toyoda, K., Ohno, H., Murai, J., and D. Wing;A Simple Mode of Facsimile Using Internet Mail;;;;;RFC 2305;DOI 10.17487/RFC2305;March;https://www.rfc-editor.org/info/rfc2305 | |
| RFC2306;;Parsons, G. and J. Rafferty;Tag Image File Format (TIFF) - F Profile for Facsimile;;;;;RFC 2306;DOI 10.17487/RFC2306;March;https://www.rfc-editor.org/info/rfc2306 | |
| RFC2307;;Howard, L.;An Approach for Using LDAP as a Network Information Service;;;;;RFC 2307;DOI 10.17487/RFC2307;March;https://www.rfc-editor.org/info/rfc2307 | |
| RFC2308;;Andrews, M.;Negative Caching of DNS Queries (DNS NCACHE);;;;;RFC 2308;DOI 10.17487/RFC2308;March;https://www.rfc-editor.org/info/rfc2308 | |
| RFC2309;RFC7567;Braden, B., Clark, D., Crowcroft, J., Davie, B., Deering, S., Estrin, D., Floyd, S., Jacobson, V., Minshall, G., Partridge, C., Peterson, L., Ramakrishnan, K., Shenker, S., Wroclawski, J., and L. Zhang;Recommendations on Queue Management and Congestion Avoidance in the Internet;;;;;RFC 2309;DOI 10.17487/RFC2309;April;https://www.rfc-editor.org/info/rfc2309 | |
| RFC2310;;Holtman, K.;The Safe Response Header Field;;;;;RFC 2310;DOI 10.17487/RFC2310;April;https://www.rfc-editor.org/info/rfc2310 | |
| RFC2311;;Dusse, S., Hoffman, P., Ramsdell, B., Lundblade, L., and L. Repka;S/MIME Version 2 Message Specification;;;;;RFC 2311;DOI 10.17487/RFC2311;March;https://www.rfc-editor.org/info/rfc2311 | |
| RFC2312;;Dusse, S., Hoffman, P., Ramsdell, B., and J. Weinstein;S/MIME Version 2 Certificate Handling;;;;;RFC 2312;DOI 10.17487/RFC2312;March;https://www.rfc-editor.org/info/rfc2312 | |
| RFC2313;RFC2437;Kaliski, B.;PKCS #1: RSA Encryption Version 1.5;;;;;RFC 2313;DOI 10.17487/RFC2313;March;https://www.rfc-editor.org/info/rfc2313 | |
| RFC2314;RFC2986;Kaliski, B.;PKCS #10: Certification Request Syntax Version 1.5;;;;;RFC 2314;DOI 10.17487/RFC2314;March;https://www.rfc-editor.org/info/rfc2314 | |
| RFC2315;;Kaliski, B.;PKCS #7: Cryptographic Message Syntax Version 1.5;;;;;RFC 2315;DOI 10.17487/RFC2315;March;https://www.rfc-editor.org/info/rfc2315 | |
| RFC2316;;Bellovin, S.;Report of the IAB Security Architecture Workshop;;;;;RFC 2316;DOI 10.17487/RFC2316;April;https://www.rfc-editor.org/info/rfc2316 | |
| RFC2317;;Eidnes, H., de Groot, G., and P. Vixie;Classless IN-ADDR.ARPA delegation;;;BCP 20;;RFC 2317;DOI 10.17487/RFC2317;March;https://www.rfc-editor.org/info/rfc2317 | |
| RFC2318;;Lie, H., Bos, B., and C. Lilley;The text/css Media Type;;;;;RFC 2318;DOI 10.17487/RFC2318;March;https://www.rfc-editor.org/info/rfc2318 | |
| RFC2319;;KOI8-U Working Group;Ukrainian Character Set KOI8-U;;;;;RFC 2319;DOI 10.17487/RFC2319;April;https://www.rfc-editor.org/info/rfc2319 | |
| RFC2320;;Greene, M., Luciani, J., White, K., and T. Kuo;Definitions of Managed Objects for Classical IP and ARP Over ATM Using SMIv2 (IPOA-MIB);;;;;RFC 2320;DOI 10.17487/RFC2320;April;https://www.rfc-editor.org/info/rfc2320 | |
| RFC2321;;Bressen, A.;RITA -- The Reliable Internetwork Troubleshooting Agent;;;;;RFC 2321;DOI 10.17487/RFC2321;April;https://www.rfc-editor.org/info/rfc2321 | |
| RFC2322;;van den Hout, K., Koopal, A., and R. van Mook;Management of IP numbers by peg-dhcp;;;;;RFC 2322;DOI 10.17487/RFC2322;April;https://www.rfc-editor.org/info/rfc2322 | |
| RFC2323;;Ramos, A.;IETF Identification and Security Guidelines;;;;;RFC 2323;DOI 10.17487/RFC2323;April;https://www.rfc-editor.org/info/rfc2323 | |
| RFC2324;;Masinter, L.;Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0);;;;;RFC 2324;DOI 10.17487/RFC2324;April;https://www.rfc-editor.org/info/rfc2324 | |
| RFC2325;;Slavitch, M.;Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2;;;;;RFC 2325;DOI 10.17487/RFC2325;April;https://www.rfc-editor.org/info/rfc2325 | |
| RFC2326;RFC7826;Schulzrinne, H., Rao, A., and R. Lanphier;Real Time Streaming Protocol (RTSP);;;;;RFC 2326;DOI 10.17487/RFC2326;April;https://www.rfc-editor.org/info/rfc2326 | |
| RFC2327;RFC4566;Handley, M. and V. Jacobson;SDP: Session Description Protocol;;;;;RFC 2327;DOI 10.17487/RFC2327;April;https://www.rfc-editor.org/info/rfc2327 | |
| RFC2328;;Moy, J.;OSPF Version 2;;;;STD 54;RFC 2328;DOI 10.17487/RFC2328;April;https://www.rfc-editor.org/info/rfc2328 | |
| RFC2329;;Moy, J.;OSPF Standardization Report;;;;;RFC 2329;DOI 10.17487/RFC2329;April;https://www.rfc-editor.org/info/rfc2329 | |
| RFC2330;;Paxson, V., Almes, G., Mahdavi, J., and M. Mathis;Framework for IP Performance Metrics;;;;;RFC 2330;DOI 10.17487/RFC2330;May;https://www.rfc-editor.org/info/rfc2330 | |
| RFC2331;;Maher, M.;ATM Signalling Support for IP over ATM - UNI Signalling 4.0 Update;;;;;RFC 2331;DOI 10.17487/RFC2331;April;https://www.rfc-editor.org/info/rfc2331 | |
| RFC2332;;Luciani, J., Katz, D., Piscitello, D., Cole, B., and N. Doraswamy;NBMA Next Hop Resolution Protocol (NHRP);;;;;RFC 2332;DOI 10.17487/RFC2332;April;https://www.rfc-editor.org/info/rfc2332 | |
| RFC2333;;Cansever, D.;NHRP Protocol Applicability Statement;;;;;RFC 2333;DOI 10.17487/RFC2333;April;https://www.rfc-editor.org/info/rfc2333 | |
| RFC2334;;Luciani, J., Armitage, G., Halpern, J., and N. Doraswamy;Server Cache Synchronization Protocol (SCSP);;;;;RFC 2334;DOI 10.17487/RFC2334;April;https://www.rfc-editor.org/info/rfc2334 | |
| RFC2335;;Luciani, J.;A Distributed NHRP Service Using SCSP;;;;;RFC 2335;DOI 10.17487/RFC2335;April;https://www.rfc-editor.org/info/rfc2335 | |
| RFC2336;;Luciani, J.;Classical IP and ARP over ATM to NHRP Transition;;;;;RFC 2336;DOI 10.17487/RFC2336;July;https://www.rfc-editor.org/info/rfc2336 | |
| RFC2337;;Farinacci, D., Meyer, D., and Y. Rekhter;Intra-LIS IP multicast among routers over ATM using Sparse Mode PIM;;;;;RFC 2337;DOI 10.17487/RFC2337;April;https://www.rfc-editor.org/info/rfc2337 | |
| RFC2338;RFC3768;Knight, S., Weaver, D., Whipple, D., Hinden, R., Mitzel, D., Hunt, P., Higginson, P., Shand, M., and A. Lindem;Virtual Router Redundancy Protocol;;;;;RFC 2338;DOI 10.17487/RFC2338;April;https://www.rfc-editor.org/info/rfc2338 | |
| RFC2339;;The Internet Society and Sun Microsystems;An Agreement Between the Internet Society, the IETF, and Sun Microsystems, Inc. in the matter of NFS V.4 Protocols;;;;;RFC 2339;DOI 10.17487/RFC2339;May;https://www.rfc-editor.org/info/rfc2339 | |
| RFC2340;;Jamoussi, B., Jamieson, D., Williston, D., and S. Gabe;Nortel's Virtual Network Switching (VNS) Overview;;;;;RFC 2340;DOI 10.17487/RFC2340;May;https://www.rfc-editor.org/info/rfc2340 | |
| RFC2341;;Valencia, A., Littlewood, M., and T. Kolar;Cisco Layer Two Forwarding (Protocol) "L2F";;;;;RFC 2341;DOI 10.17487/RFC2341;May;https://www.rfc-editor.org/info/rfc2341 | |
| RFC2342;;Gahrns, M. and C. Newman;IMAP4 Namespace;;;;;RFC 2342;DOI 10.17487/RFC2342;May;https://www.rfc-editor.org/info/rfc2342 | |
| RFC2343;;Civanlar, M., Cash, G., and B. Haskell;RTP Payload Format for Bundled MPEG;;;;;RFC 2343;DOI 10.17487/RFC2343;May;https://www.rfc-editor.org/info/rfc2343 | |
| RFC2344;RFC3024;Montenegro, G., Ed.;Reverse Tunneling for Mobile IP;;;;;RFC 2344;DOI 10.17487/RFC2344;May;https://www.rfc-editor.org/info/rfc2344 | |
| RFC2345;;Klensin, J., Wolf, T., and G. Oglesby;Domain Names and Company Name Retrieval;;;;;RFC 2345;DOI 10.17487/RFC2345;May;https://www.rfc-editor.org/info/rfc2345 | |
| RFC2346;;Palme, J.;Making Postscript and PDF International;;;;;RFC 2346;DOI 10.17487/RFC2346;May;https://www.rfc-editor.org/info/rfc2346 | |
| RFC2347;;Malkin, G. and A. Harkin;TFTP Option Extension;;;;;RFC 2347;DOI 10.17487/RFC2347;May;https://www.rfc-editor.org/info/rfc2347 | |
| RFC2348;;Malkin, G. and A. Harkin;TFTP Blocksize Option;;;;;RFC 2348;DOI 10.17487/RFC2348;May;https://www.rfc-editor.org/info/rfc2348 | |
| RFC2349;;Malkin, G. and A. Harkin;TFTP Timeout Interval and Transfer Size Options;;;;;RFC 2349;DOI 10.17487/RFC2349;May;https://www.rfc-editor.org/info/rfc2349 | |
| RFC2350;;Brownlee, N. and E. Guttman;Expectations for Computer Security Incident Response;;;BCP 21;;RFC 2350;DOI 10.17487/RFC2350;June;https://www.rfc-editor.org/info/rfc2350 | |
| RFC2351;;Robert, A.;Mapping of Airline Reservation, Ticketing, and Messaging Traffic over IP;;;;;RFC 2351;DOI 10.17487/RFC2351;May;https://www.rfc-editor.org/info/rfc2351 | |
| RFC2352;;Vaughan, O.;A Convention For Using Legal Names as Domain Names;;;;;RFC 2352;DOI 10.17487/RFC2352;May;https://www.rfc-editor.org/info/rfc2352 | |
| RFC2353;;Dudley, G.;APPN/HPR in IP Networks APPN Implementers' Workshop Closed Pages Document;;;;;RFC 2353;DOI 10.17487/RFC2353;May;https://www.rfc-editor.org/info/rfc2353 | |
| RFC2354;;Perkins, C. and O. Hodson;Options for Repair of Streaming Media;;;;;RFC 2354;DOI 10.17487/RFC2354;June;https://www.rfc-editor.org/info/rfc2354 | |
| RFC2355;;Kelly, B.;TN3270 Enhancements;;;;;RFC 2355;DOI 10.17487/RFC2355;June;https://www.rfc-editor.org/info/rfc2355 | |
| RFC2356;;Montenegro, G. and V. Gupta;Sun's SKIP Firewall Traversal for Mobile IP;;;;;RFC 2356;DOI 10.17487/RFC2356;June;https://www.rfc-editor.org/info/rfc2356 | |
| RFC2357;;Mankin, A., Romanow, A., Bradner, S., and V. Paxson;IETF Criteria for Evaluating Reliable Multicast Transport and Application Protocols;;;;;RFC 2357;DOI 10.17487/RFC2357;June;https://www.rfc-editor.org/info/rfc2357 | |
| RFC2358;RFC2665;Flick, J. and J. Johnson;Definitions of Managed Objects for the Ethernet-like Interface Types;;;;;RFC 2358;DOI 10.17487/RFC2358;June;https://www.rfc-editor.org/info/rfc2358 | |
| RFC2359;RFC4315;Myers, J.;IMAP4 UIDPLUS extension;;;;;RFC 2359;DOI 10.17487/RFC2359;June;https://www.rfc-editor.org/info/rfc2359 | |
| RFC2360;;Scott, G.;Guide for Internet Standards Writers;;;BCP 22;;RFC 2360;DOI 10.17487/RFC2360;June;https://www.rfc-editor.org/info/rfc2360 | |
| RFC2361;;Fleischman, E.;WAVE and AVI Codec Registries;;;;;RFC 2361;DOI 10.17487/RFC2361;June;https://www.rfc-editor.org/info/rfc2361 | |
| RFC2362;RFC4601, RFC5059;Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S., Handley, M., Jacobson, V., Liu, C., Sharma, P., and L. Wei;Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification;;;;;RFC 2362;DOI 10.17487/RFC2362;June;https://www.rfc-editor.org/info/rfc2362 | |
| RFC2363;;Gross, G., Kaycee, M., Li, A., Malis, A., and J. Stephens;PPP Over FUNI;;;;;RFC 2363;DOI 10.17487/RFC2363;July;https://www.rfc-editor.org/info/rfc2363 | |
| RFC2364;;Gross, G., Kaycee, M., Li, A., Malis, A., and J. Stephens;PPP Over AAL5;;;;;RFC 2364;DOI 10.17487/RFC2364;July;https://www.rfc-editor.org/info/rfc2364 | |
| RFC2365;;Meyer, D.;Administratively Scoped IP Multicast;;;BCP 23;;RFC 2365;DOI 10.17487/RFC2365;July;https://www.rfc-editor.org/info/rfc2365 | |
| RFC2366;RFC2417;Chung, C. and M. Greene;Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM Networks;;;;;RFC 2366;DOI 10.17487/RFC2366;July;https://www.rfc-editor.org/info/rfc2366 | |
| RFC2367;;McDonald, D., Metz, C., and B. Phan;PF_KEY Key Management API, Version 2;;;;;RFC 2367;DOI 10.17487/RFC2367;July;https://www.rfc-editor.org/info/rfc2367 | |
| RFC2368;RFC6068;Hoffman, P., Masinter, L., and J. Zawinski;The mailto URL scheme;;;;;RFC 2368;DOI 10.17487/RFC2368;July;https://www.rfc-editor.org/info/rfc2368 | |
| RFC2369;;Neufeld, G. and J. Baer;The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields;;;;;RFC 2369;DOI 10.17487/RFC2369;July;https://www.rfc-editor.org/info/rfc2369 | |
| RFC2370;RFC5250;Coltun, R.;The OSPF Opaque LSA Option;;;;;RFC 2370;DOI 10.17487/RFC2370;July;https://www.rfc-editor.org/info/rfc2370 | |
| RFC2371;;Lyon, J., Evans, K., and J. Klein;Transaction Internet Protocol Version 3.0;;;;;RFC 2371;DOI 10.17487/RFC2371;July;https://www.rfc-editor.org/info/rfc2371 | |
| RFC2372;;Evans, K., Klein, J., and J. Lyon;Transaction Internet Protocol - Requirements and Supplemental Information;;;;;RFC 2372;DOI 10.17487/RFC2372;July;https://www.rfc-editor.org/info/rfc2372 | |
| RFC2373;RFC3513;Hinden, R. and S. Deering;IP Version 6 Addressing Architecture;;;;;RFC 2373;DOI 10.17487/RFC2373;July;https://www.rfc-editor.org/info/rfc2373 | |
| RFC2374;RFC3587;Hinden, R., O'Dell, M., and S. Deering;An IPv6 Aggregatable Global Unicast Address Format;;;;;RFC 2374;DOI 10.17487/RFC2374;July;https://www.rfc-editor.org/info/rfc2374 | |
| RFC2375;;Hinden, R. and S. Deering;IPv6 Multicast Address Assignments;;;;;RFC 2375;DOI 10.17487/RFC2375;July;https://www.rfc-editor.org/info/rfc2375 | |
| RFC2376;RFC3023;Whitehead, E. and M. Murata;XML Media Types;;;;;RFC 2376;DOI 10.17487/RFC2376;July;https://www.rfc-editor.org/info/rfc2376 | |
| RFC2377;;Grimstad, A., Huber, R., Sataluri, S., and M. Wahl;Naming Plan for Internet Directory-Enabled Applications;;;;;RFC 2377;DOI 10.17487/RFC2377;September;https://www.rfc-editor.org/info/rfc2377 | |
| RFC2378;;Hedberg, R. and P. Pomes;The CCSO Nameserver (Ph) Architecture;;;;;RFC 2378;DOI 10.17487/RFC2378;September;https://www.rfc-editor.org/info/rfc2378 | |
| RFC2379;;Berger, L.;RSVP over ATM Implementation Guidelines;;;BCP 24;;RFC 2379;DOI 10.17487/RFC2379;August;https://www.rfc-editor.org/info/rfc2379 | |
| RFC2380;;Berger, L.;RSVP over ATM Implementation Requirements;;;;;RFC 2380;DOI 10.17487/RFC2380;August;https://www.rfc-editor.org/info/rfc2380 | |
| RFC2381;;Garrett, M. and M. Borden;Interoperation of Controlled-Load Service and Guaranteed Service with ATM;;;;;RFC 2381;DOI 10.17487/RFC2381;August;https://www.rfc-editor.org/info/rfc2381 | |
| RFC2382;;Crawley, E., Ed., Berger, L., Berson, S., Baker, F., Borden, M., and J. Krawczyk;A Framework for Integrated Services and RSVP over ATM;;;;;RFC 2382;DOI 10.17487/RFC2382;August;https://www.rfc-editor.org/info/rfc2382 | |
| RFC2383;;Suzuki, M.;ST2+ over ATM Protocol Specification - UNI 3.1 Version;;;;;RFC 2383;DOI 10.17487/RFC2383;August;https://www.rfc-editor.org/info/rfc2383 | |
| RFC2384;;Gellens, R.;POP URL Scheme;;;;;RFC 2384;DOI 10.17487/RFC2384;August;https://www.rfc-editor.org/info/rfc2384 | |
| RFC2385;RFC5925;Heffernan, A.;Protection of BGP Sessions via the TCP MD5 Signature Option;;;;;RFC 2385;DOI 10.17487/RFC2385;August;https://www.rfc-editor.org/info/rfc2385 | |
| RFC2386;;Crawley, E., Nair, R., Rajagopalan, B., and H. Sandick;A Framework for QoS-based Routing in the Internet;;;;;RFC 2386;DOI 10.17487/RFC2386;August;https://www.rfc-editor.org/info/rfc2386 | |
| RFC2387;;Levinson, E.;The MIME Multipart/Related Content-type;;;;;RFC 2387;DOI 10.17487/RFC2387;August;https://www.rfc-editor.org/info/rfc2387 | |
| RFC2388;RFC7578;Masinter, L.;Returning Values from Forms: multipart/form-data;;;;;RFC 2388;DOI 10.17487/RFC2388;August;https://www.rfc-editor.org/info/rfc2388 | |
| RFC2389;;Hethmon, P. and R. Elz;Feature negotiation mechanism for the File Transfer Protocol;;;;;RFC 2389;DOI 10.17487/RFC2389;August;https://www.rfc-editor.org/info/rfc2389 | |
| RFC2390;;Bradley, T., Brown, C., and A. Malis;Inverse Address Resolution Protocol;;;;;RFC 2390;DOI 10.17487/RFC2390;September;https://www.rfc-editor.org/info/rfc2390 | |
| RFC2391;;Srisuresh, P. and D. Gan;Load Sharing using IP Network Address Translation (LSNAT);;;;;RFC 2391;DOI 10.17487/RFC2391;August;https://www.rfc-editor.org/info/rfc2391 | |
| RFC2392;;Levinson, E.;Content-ID and Message-ID Uniform Resource Locators;;;;;RFC 2392;DOI 10.17487/RFC2392;August;https://www.rfc-editor.org/info/rfc2392 | |
| RFC2393;RFC3173;Shacham, A., Monsour, R., Pereira, R., and M. Thomas;IP Payload Compression Protocol (IPComp);;;;;RFC 2393;DOI 10.17487/RFC2393;December;https://www.rfc-editor.org/info/rfc2393 | |
| RFC2394;;Pereira, R.;IP Payload Compression Using DEFLATE;;;;;RFC 2394;DOI 10.17487/RFC2394;December;https://www.rfc-editor.org/info/rfc2394 | |
| RFC2395;;Friend, R. and R. Monsour;IP Payload Compression Using LZS;;;;;RFC 2395;DOI 10.17487/RFC2395;December;https://www.rfc-editor.org/info/rfc2395 | |
| RFC2396;RFC3986;Berners-Lee, T., Fielding, R., and L. Masinter;Uniform Resource Identifiers (URI): Generic Syntax;;;;;RFC 2396;DOI 10.17487/RFC2396;August;https://www.rfc-editor.org/info/rfc2396 | |
| RFC2397;;Masinter, L.;The "data" URL scheme;;;;;RFC 2397;DOI 10.17487/RFC2397;August;https://www.rfc-editor.org/info/rfc2397 | |
| RFC2398;;Parker, S. and C. Schmechel;Some Testing Tools for TCP Implementors;;FYI 33;;;RFC 2398;DOI 10.17487/RFC2398;August;https://www.rfc-editor.org/info/rfc2398 | |
| RFC2399;;Ramos, A.;Request for Comments Summary;;;;;RFC 2399;DOI 10.17487/RFC2399;January;https://www.rfc-editor.org/info/rfc2399 | |
| RFC2400;RFC2500;Postel, J. and J. Reynolds;Internet Official Protocol Standards;;;;;RFC 2400;DOI 10.17487/RFC2400;September;https://www.rfc-editor.org/info/rfc2400 | |
| RFC2401;RFC4301;Kent, S. and R. Atkinson;Security Architecture for the Internet Protocol;;;;;RFC 2401;DOI 10.17487/RFC2401;November;https://www.rfc-editor.org/info/rfc2401 | |
| RFC2402;RFC4302, RFC4305;Kent, S. and R. Atkinson;IP Authentication Header;;;;;RFC 2402;DOI 10.17487/RFC2402;November;https://www.rfc-editor.org/info/rfc2402 | |
| RFC2403;;Madson, C. and R. Glenn;The Use of HMAC-MD5-96 within ESP and AH;;;;;RFC 2403;DOI 10.17487/RFC2403;November;https://www.rfc-editor.org/info/rfc2403 | |
| RFC2404;;Madson, C. and R. Glenn;The Use of HMAC-SHA-1-96 within ESP and AH;;;;;RFC 2404;DOI 10.17487/RFC2404;November;https://www.rfc-editor.org/info/rfc2404 | |
| RFC2405;;Madson, C. and N. Doraswamy;The ESP DES-CBC Cipher Algorithm With Explicit IV;;;;;RFC 2405;DOI 10.17487/RFC2405;November;https://www.rfc-editor.org/info/rfc2405 | |
| RFC2406;RFC4303, RFC4305;Kent, S. and R. Atkinson;IP Encapsulating Security Payload (ESP);;;;;RFC 2406;DOI 10.17487/RFC2406;November;https://www.rfc-editor.org/info/rfc2406 | |
| RFC2407;RFC4306;Piper, D.;The Internet IP Security Domain of Interpretation for ISAKMP;;;;;RFC 2407;DOI 10.17487/RFC2407;November;https://www.rfc-editor.org/info/rfc2407 | |
| RFC2408;RFC4306;Maughan, D., Schertler, M., Schneider, M., and J. Turner;Internet Security Association and Key Management Protocol (ISAKMP);;;;;RFC 2408;DOI 10.17487/RFC2408;November;https://www.rfc-editor.org/info/rfc2408 | |
| RFC2409;RFC4306;Harkins, D. and D. Carrel;The Internet Key Exchange (IKE);;;;;RFC 2409;DOI 10.17487/RFC2409;November;https://www.rfc-editor.org/info/rfc2409 | |
| RFC2410;;Glenn, R. and S. Kent;The NULL Encryption Algorithm and Its Use With IPsec;;;;;RFC 2410;DOI 10.17487/RFC2410;November;https://www.rfc-editor.org/info/rfc2410 | |
| RFC2411;RFC6071;Thayer, R., Doraswamy, N., and R. Glenn;IP Security Document Roadmap;;;;;RFC 2411;DOI 10.17487/RFC2411;November;https://www.rfc-editor.org/info/rfc2411 | |
| RFC2412;;Orman, H.;The OAKLEY Key Determination Protocol;;;;;RFC 2412;DOI 10.17487/RFC2412;November;https://www.rfc-editor.org/info/rfc2412 | |
| RFC2413;RFC5013;Weibel, S., Kunze, J., Lagoze, C., and M. Wolf;Dublin Core Metadata for Resource Discovery;;;;;RFC 2413;DOI 10.17487/RFC2413;September;https://www.rfc-editor.org/info/rfc2413 | |
| RFC2414;RFC3390;Allman, M., Floyd, S., and C. Partridge;Increasing TCP's Initial Window;;;;;RFC 2414;DOI 10.17487/RFC2414;September;https://www.rfc-editor.org/info/rfc2414 | |
| RFC2415;;Poduri, K. and K. Nichols;Simulation Studies of Increased Initial TCP Window Size;;;;;RFC 2415;DOI 10.17487/RFC2415;September;https://www.rfc-editor.org/info/rfc2415 | |
| RFC2416;;Shepard, T. and C. Partridge;When TCP Starts Up With Four Packets Into Only Three Buffers;;;;;RFC 2416;DOI 10.17487/RFC2416;September;https://www.rfc-editor.org/info/rfc2416 | |
| RFC2417;;Chung, C. and M. Greene;Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM Networks;;;;;RFC 2417;DOI 10.17487/RFC2417;September;https://www.rfc-editor.org/info/rfc2417 | |
| RFC2418;;Bradner, S.;IETF Working Group Guidelines and Procedures;;;BCP 25;;RFC 2418;DOI 10.17487/RFC2418;September;https://www.rfc-editor.org/info/rfc2418 | |
| RFC2419;;Sklower, K. and G. Meyer;The PPP DES Encryption Protocol, Version 2 (DESE-bis);;;;;RFC 2419;DOI 10.17487/RFC2419;September;https://www.rfc-editor.org/info/rfc2419 | |
| RFC2420;;Kummert, H.;The PPP Triple-DES Encryption Protocol (3DESE);;;;;RFC 2420;DOI 10.17487/RFC2420;September;https://www.rfc-editor.org/info/rfc2420 | |
| RFC2421;RFC3801;Vaudreuil, G. and G. Parsons;Voice Profile for Internet Mail - version 2;;;;;RFC 2421;DOI 10.17487/RFC2421;September;https://www.rfc-editor.org/info/rfc2421 | |
| RFC2422;RFC3802;Vaudreuil, G. and G. Parsons;Toll Quality Voice - 32 kbit/s ADPCM MIME Sub-type Registration;;;;;RFC 2422;DOI 10.17487/RFC2422;September;https://www.rfc-editor.org/info/rfc2422 | |
| RFC2423;RFC3801;Vaudreuil, G. and G. Parsons;VPIM Voice Message MIME Sub-type Registration;;;;;RFC 2423;DOI 10.17487/RFC2423;September;https://www.rfc-editor.org/info/rfc2423 | |
| RFC2424;RFC3803;Vaudreuil, G. and G. Parsons;Content Duration MIME Header Definition;;;;;RFC 2424;DOI 10.17487/RFC2424;September;https://www.rfc-editor.org/info/rfc2424 | |
| RFC2425;RFC6350;Howes, T., Smith, M., and F. Dawson;A MIME Content-Type for Directory Information;;;;;RFC 2425;DOI 10.17487/RFC2425;September;https://www.rfc-editor.org/info/rfc2425 | |
| RFC2426;RFC6350;Dawson, F. and T. Howes;vCard MIME Directory Profile;;;;;RFC 2426;DOI 10.17487/RFC2426;September;https://www.rfc-editor.org/info/rfc2426 | |
| RFC2427;;Brown, C. and A. Malis;Multiprotocol Interconnect over Frame Relay;;;;STD 55;RFC 2427;DOI 10.17487/RFC2427;September;https://www.rfc-editor.org/info/rfc2427 | |
| RFC2428;;Allman, M., Ostermann, S., and C. Metz;FTP Extensions for IPv6 and NATs;;;;;RFC 2428;DOI 10.17487/RFC2428;September;https://www.rfc-editor.org/info/rfc2428 | |
| RFC2429;RFC4629;Bormann, C., Cline, L., Deisher, G., Gardos, T., Maciocco, C., Newell, D., Ott, J., Sullivan, G., Wenger, S., and C. Zhu;RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+);;;;;RFC 2429;DOI 10.17487/RFC2429;October;https://www.rfc-editor.org/info/rfc2429 | |
| RFC2430;;Li, T. and Y. Rekhter;A Provider Architecture for Differentiated Services and Traffic Engineering (PASTE);;;;;RFC 2430;DOI 10.17487/RFC2430;October;https://www.rfc-editor.org/info/rfc2430 | |
| RFC2431;;Tynan, D.;RTP Payload Format for BT.656 Video Encoding;;;;;RFC 2431;DOI 10.17487/RFC2431;October;https://www.rfc-editor.org/info/rfc2431 | |
| RFC2432;;Dubray, K.;Terminology for IP Multicast Benchmarking;;;;;RFC 2432;DOI 10.17487/RFC2432;October;https://www.rfc-editor.org/info/rfc2432 | |
| RFC2433;;Zorn, G. and S. Cobb;Microsoft PPP CHAP Extensions;;;;;RFC 2433;DOI 10.17487/RFC2433;October;https://www.rfc-editor.org/info/rfc2433 | |
| RFC2434;RFC5226;Narten, T. and H. Alvestrand;Guidelines for Writing an IANA Considerations Section in RFCs;;;;;RFC 2434;DOI 10.17487/RFC2434;October;https://www.rfc-editor.org/info/rfc2434 | |
| RFC2435;;Berc, L., Fenner, W., Frederick, R., McCanne, S., and P. Stewart;RTP Payload Format for JPEG-compressed Video;;;;;RFC 2435;DOI 10.17487/RFC2435;October;https://www.rfc-editor.org/info/rfc2435 | |
| RFC2436;RFC3356;Brett, R., Bradner, S., and G. Parsons;Collaboration between ISOC/IETF and ITU-T;;;;;RFC 2436;DOI 10.17487/RFC2436;October;https://www.rfc-editor.org/info/rfc2436 | |
| RFC2437;RFC3447;Kaliski, B. and J. Staddon;PKCS #1: RSA Cryptography Specifications Version 2.0;;;;;RFC 2437;DOI 10.17487/RFC2437;October;https://www.rfc-editor.org/info/rfc2437 | |
| RFC2438;;O'Dell, M., Alvestrand, H., Wijnen, B., and S. Bradner;Advancement of MIB specifications on the IETF Standards Track;;;BCP 27;;RFC 2438;DOI 10.17487/RFC2438;October;https://www.rfc-editor.org/info/rfc2438 | |
| RFC2439;;Villamizar, C., Chandra, R., and R. Govindan;BGP Route Flap Damping;;;;;RFC 2439;DOI 10.17487/RFC2439;November;https://www.rfc-editor.org/info/rfc2439 | |
| RFC2440;RFC4880;Callas, J., Donnerhacke, L., Finney, H., and R. Thayer;OpenPGP Message Format;;;;;RFC 2440;DOI 10.17487/RFC2440;November;https://www.rfc-editor.org/info/rfc2440 | |
| RFC2441;;Cohen, D.;Working with Jon, Tribute delivered at UCLA, October 30, 1998;;;;;RFC 2441;DOI 10.17487/RFC2441;November;https://www.rfc-editor.org/info/rfc2441 | |
| RFC2442;;Freed, N., Newman, D., Belissent, J., and M. Hoy;The Batch SMTP Media Type;;;;;RFC 2442;DOI 10.17487/RFC2442;November;https://www.rfc-editor.org/info/rfc2442 | |
| RFC2443;;Luciani, J. and A. Gallo;A Distributed MARS Service Using SCSP;;;;;RFC 2443;DOI 10.17487/RFC2443;November;https://www.rfc-editor.org/info/rfc2443 | |
| RFC2444;;Newman, C.;The One-Time-Password SASL Mechanism;;;;;RFC 2444;DOI 10.17487/RFC2444;October;https://www.rfc-editor.org/info/rfc2444 | |
| RFC2445;RFC5545;Dawson, F. and D. Stenerson;Internet Calendaring and Scheduling Core Object Specification (iCalendar);;;;;RFC 2445;DOI 10.17487/RFC2445;November;https://www.rfc-editor.org/info/rfc2445 | |
| RFC2446;RFC5546;Silverberg, S., Mansour, S., Dawson, F., and R. Hopson;iCalendar Transport-Independent Interoperability Protocol (iTIP) Scheduling Events, BusyTime, To-dos and Journal Entries;;;;;RFC 2446;DOI 10.17487/RFC2446;November;https://www.rfc-editor.org/info/rfc2446 | |
| RFC2447;RFC6047;Dawson, F., Mansour, S., and S. Silverberg;iCalendar Message-Based Interoperability Protocol (iMIP);;;;;RFC 2447;DOI 10.17487/RFC2447;November;https://www.rfc-editor.org/info/rfc2447 | |
| RFC2448;;Civanlar, M., Cash, G., and B. Haskell;AT&T's Error Resilient Video Transmission Technique;;;;;RFC 2448;DOI 10.17487/RFC2448;November;https://www.rfc-editor.org/info/rfc2448 | |
| RFC2449;;Gellens, R., Newman, C., and L. Lundblade;POP3 Extension Mechanism;;;;;RFC 2449;DOI 10.17487/RFC2449;November;https://www.rfc-editor.org/info/rfc2449 | |
| RFC2450;;Hinden, R.;Proposed TLA and NLA Assignment Rule;;;;;RFC 2450;DOI 10.17487/RFC2450;December;https://www.rfc-editor.org/info/rfc2450 | |
| RFC2451;;Pereira, R. and R. Adams;The ESP CBC-Mode Cipher Algorithms;;;;;RFC 2451;DOI 10.17487/RFC2451;November;https://www.rfc-editor.org/info/rfc2451 | |
| RFC2452;RFC4022, RFC8096;Daniele, M.;IP Version 6 Management Information Base for the Transmission Control Protocol;;;;;RFC 2452;DOI 10.17487/RFC2452;December;https://www.rfc-editor.org/info/rfc2452 | |
| RFC2453;;Malkin, G.;RIP Version 2;;;;STD 56;RFC 2453;DOI 10.17487/RFC2453;November;https://www.rfc-editor.org/info/rfc2453 | |
| RFC2454;RFC4113, RFC8096;Daniele, M.;IP Version 6 Management Information Base for the User Datagram Protocol;;;;;RFC 2454;DOI 10.17487/RFC2454;December;https://www.rfc-editor.org/info/rfc2454 | |
| RFC2455;;Clouston, B. and B. Moore;Definitions of Managed Objects for APPN;;;;;RFC 2455;DOI 10.17487/RFC2455;November;https://www.rfc-editor.org/info/rfc2455 | |
| RFC2456;;Clouston, B. and B. Moore;Definitions of Managed Objects for APPN TRAPS;;;;;RFC 2456;DOI 10.17487/RFC2456;November;https://www.rfc-editor.org/info/rfc2456 | |
| RFC2457;;Clouston, B. and B. Moore;Definitions of Managed Objects for Extended Border Node;;;;;RFC 2457;DOI 10.17487/RFC2457;November;https://www.rfc-editor.org/info/rfc2457 | |
| RFC2458;;Lu, H., Krishnaswamy, M., Conroy, L., Bellovin, S., Burg, F., DeSimone, A., Tewani, K., Davidson, P., Schulzrinne, H., and K. Vishwanathan;Toward the PSTN/Internet Inter-Networking--Pre-PINT Implementations;;;;;RFC 2458;DOI 10.17487/RFC2458;November;https://www.rfc-editor.org/info/rfc2458 | |
| RFC2459;RFC3280;Housley, R., Ford, W., Polk, W., and D. Solo;Internet X.509 Public Key Infrastructure Certificate and CRL Profile;;;;;RFC 2459;DOI 10.17487/RFC2459;January;https://www.rfc-editor.org/info/rfc2459 | |
| RFC2460;RFC8200;Deering, S. and R. Hinden;Internet Protocol, Version 6 (IPv6) Specification;;;;;RFC 2460;DOI 10.17487/RFC2460;December;https://www.rfc-editor.org/info/rfc2460 | |
| RFC2461;RFC4861;Narten, T., Nordmark, E., and W. Simpson;Neighbor Discovery for IP Version 6 (IPv6);;;;;RFC 2461;DOI 10.17487/RFC2461;December;https://www.rfc-editor.org/info/rfc2461 | |
| RFC2462;RFC4862;Thomson, S. and T. Narten;IPv6 Stateless Address Autoconfiguration;;;;;RFC 2462;DOI 10.17487/RFC2462;December;https://www.rfc-editor.org/info/rfc2462 | |
| RFC2463;RFC4443;Conta, A. and S. Deering;Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification;;;;;RFC 2463;DOI 10.17487/RFC2463;December;https://www.rfc-editor.org/info/rfc2463 | |
| RFC2464;;Crawford, M.;Transmission of IPv6 Packets over Ethernet Networks;;;;;RFC 2464;DOI 10.17487/RFC2464;December;https://www.rfc-editor.org/info/rfc2464 | |
| RFC2465;RFC4293, RFC8096;Haskin, D. and S. Onishi;Management Information Base for IP Version 6: Textual Conventions and General Group;;;;;RFC 2465;DOI 10.17487/RFC2465;December;https://www.rfc-editor.org/info/rfc2465 | |
| RFC2466;RFC4293, RFC8096;Haskin, D. and S. Onishi;Management Information Base for IP Version 6: ICMPv6 Group;;;;;RFC 2466;DOI 10.17487/RFC2466;December;https://www.rfc-editor.org/info/rfc2466 | |
| RFC2467;;Crawford, M.;Transmission of IPv6 Packets over FDDI Networks;;;;;RFC 2467;DOI 10.17487/RFC2467;December;https://www.rfc-editor.org/info/rfc2467 | |
| RFC2468;;Cerf, V.;I REMEMBER IANA;;;;;RFC 2468;DOI 10.17487/RFC2468;October;https://www.rfc-editor.org/info/rfc2468 | |
| RFC2469;;Narten, T. and C. Burton;A Caution On The Canonical Ordering Of Link-Layer Addresses;;;;;RFC 2469;DOI 10.17487/RFC2469;December;https://www.rfc-editor.org/info/rfc2469 | |
| RFC2470;;Crawford, M., Narten, T., and S. Thomas;Transmission of IPv6 Packets over Token Ring Networks;;;;;RFC 2470;DOI 10.17487/RFC2470;December;https://www.rfc-editor.org/info/rfc2470 | |
| RFC2471;RFC3701;Hinden, R., Fink, R., and J. Postel;IPv6 Testing Address Allocation;;;;;RFC 2471;DOI 10.17487/RFC2471;December;https://www.rfc-editor.org/info/rfc2471 | |
| RFC2472;RFC5072, RFC5172;Haskin, D. and E. Allen;IP Version 6 over PPP;;;;;RFC 2472;DOI 10.17487/RFC2472;December;https://www.rfc-editor.org/info/rfc2472 | |
| RFC2473;;Conta, A. and S. Deering;Generic Packet Tunneling in IPv6 Specification;;;;;RFC 2473;DOI 10.17487/RFC2473;December;https://www.rfc-editor.org/info/rfc2473 | |
| RFC2474;;Nichols, K., Blake, S., Baker, F., and D. Black;Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers;;;;;RFC 2474;DOI 10.17487/RFC2474;December;https://www.rfc-editor.org/info/rfc2474 | |
| RFC2475;;Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z., and W. Weiss;An Architecture for Differentiated Services;;;;;RFC 2475;DOI 10.17487/RFC2475;December;https://www.rfc-editor.org/info/rfc2475 | |
| RFC2476;RFC4409;Gellens, R. and J. Klensin;Message Submission;;;;;RFC 2476;DOI 10.17487/RFC2476;December;https://www.rfc-editor.org/info/rfc2476 | |
| RFC2477;;Aboba, B. and G. Zorn;Criteria for Evaluating Roaming Protocols;;;;;RFC 2477;DOI 10.17487/RFC2477;January;https://www.rfc-editor.org/info/rfc2477 | |
| RFC2478;RFC4178;Baize, E. and D. Pinkas;The Simple and Protected GSS-API Negotiation Mechanism;;;;;RFC 2478;DOI 10.17487/RFC2478;December;https://www.rfc-editor.org/info/rfc2478 | |
| RFC2479;;Adams, C.;Independent Data Unit Protection Generic Security Service Application Program Interface (IDUP-GSS-API);;;;;RFC 2479;DOI 10.17487/RFC2479;December;https://www.rfc-editor.org/info/rfc2479 | |
| RFC2480;;Freed, N.;Gateways and MIME Security Multiparts;;;;;RFC 2480;DOI 10.17487/RFC2480;January;https://www.rfc-editor.org/info/rfc2480 | |
| RFC2481;RFC3168;Ramakrishnan, K. and S. Floyd;A Proposal to add Explicit Congestion Notification (ECN) to IP;;;;;RFC 2481;DOI 10.17487/RFC2481;January;https://www.rfc-editor.org/info/rfc2481 | |
| RFC2482;RFC6082;Whistler, K. and G. Adams;Language Tagging in Unicode Plain Text;;;;;RFC 2482;DOI 10.17487/RFC2482;January;https://www.rfc-editor.org/info/rfc2482 | |
| RFC2483;;Mealling, M. and R. Daniel;URI Resolution Services Necessary for URN Resolution;;;;;RFC 2483;DOI 10.17487/RFC2483;January;https://www.rfc-editor.org/info/rfc2483 | |
| RFC2484;;Zorn, G.;PPP LCP Internationalization Configuration Option;;;;;RFC 2484;DOI 10.17487/RFC2484;January;https://www.rfc-editor.org/info/rfc2484 | |
| RFC2485;;Drach, S.;DHCP Option for The Open Group's User Authentication Protocol;;;;;RFC 2485;DOI 10.17487/RFC2485;January;https://www.rfc-editor.org/info/rfc2485 | |
| RFC2486;RFC4282;Aboba, B. and M. Beadles;The Network Access Identifier;;;;;RFC 2486;DOI 10.17487/RFC2486;January;https://www.rfc-editor.org/info/rfc2486 | |
| RFC2487;RFC3207;Hoffman, P.;SMTP Service Extension for Secure SMTP over TLS;;;;;RFC 2487;DOI 10.17487/RFC2487;January;https://www.rfc-editor.org/info/rfc2487 | |
| RFC2488;;Allman, M., Glover, D., and L. Sanchez;Enhancing TCP Over Satellite Channels using Standard Mechanisms;;;BCP 28;;RFC 2488;DOI 10.17487/RFC2488;January;https://www.rfc-editor.org/info/rfc2488 | |
| RFC2489;RFC2939;Droms, R.;Procedure for Defining New DHCP Options;;;BCP 29;;RFC 2489;DOI 10.17487/RFC2489;January;https://www.rfc-editor.org/info/rfc2489 | |
| RFC2490;;Pullen, M., Malghan, R., Lavu, L., Duan, G., Ma, J., and H. Nah;A Simulation Model for IP Multicast with RSVP;;;;;RFC 2490;DOI 10.17487/RFC2490;January;https://www.rfc-editor.org/info/rfc2490 | |
| RFC2491;;Armitage, G., Schulter, P., Jork, M., and G. Harter;IPv6 over Non-Broadcast Multiple Access (NBMA) networks;;;;;RFC 2491;DOI 10.17487/RFC2491;January;https://www.rfc-editor.org/info/rfc2491 | |
| RFC2492;;Armitage, G., Schulter, P., and M. Jork;IPv6 over ATM Networks;;;;;RFC 2492;DOI 10.17487/RFC2492;January;https://www.rfc-editor.org/info/rfc2492 | |
| RFC2493;RFC3593;Tesink, K., Ed.;Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals;;;;;RFC 2493;DOI 10.17487/RFC2493;January;https://www.rfc-editor.org/info/rfc2493 | |
| RFC2494;;Fowler, D., Ed.;Definitions of Managed Objects for the DS0 and DS0 Bundle Interface Type;;;;;RFC 2494;DOI 10.17487/RFC2494;January;https://www.rfc-editor.org/info/rfc2494 | |
| RFC2495;RFC3895;Fowler, D., Ed.;Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types;;;;;RFC 2495;DOI 10.17487/RFC2495;January;https://www.rfc-editor.org/info/rfc2495 | |
| RFC2496;RFC3896;Fowler, D., Ed.;Definitions of Managed Object for the DS3/E3 Interface Type;;;;;RFC 2496;DOI 10.17487/RFC2496;January;https://www.rfc-editor.org/info/rfc2496 | |
| RFC2497;;Souvatzis, I.;Transmission of IPv6 Packets over ARCnet Networks;;;;;RFC 2497;DOI 10.17487/RFC2497;January;https://www.rfc-editor.org/info/rfc2497 | |
| RFC2498;RFC2678;Mahdavi, J. and V. Paxson;IPPM Metrics for Measuring Connectivity;;;;;RFC 2498;DOI 10.17487/RFC2498;January;https://www.rfc-editor.org/info/rfc2498 | |
| RFC2499;;Ramos, A.;Request for Comments Summary;;;;;RFC 2499;DOI 10.17487/RFC2499;July;https://www.rfc-editor.org/info/rfc2499 | |
| RFC2500;RFC2600;Reynolds, J. and R. Braden;Internet Official Protocol Standards;;;;;RFC 2500;DOI 10.17487/RFC2500;June;https://www.rfc-editor.org/info/rfc2500 | |
| RFC2501;;Corson, S. and J. Macker;Mobile Ad hoc Networking (MANET): Routing Protocol Performance Issues and Evaluation Considerations;;;;;RFC 2501;DOI 10.17487/RFC2501;January;https://www.rfc-editor.org/info/rfc2501 | |
| RFC2502;;Pullen, M., Myjak, M., and C. Bouwens;Limitations of Internet Protocol Suite for Distributed Simulation the Large Multicast Environment;;;;;RFC 2502;DOI 10.17487/RFC2502;February;https://www.rfc-editor.org/info/rfc2502 | |
| RFC2503;;Moulton, R. and M. Needleman;MIME Types for Use with the ISO ILL Protocol;;;;;RFC 2503;DOI 10.17487/RFC2503;February;https://www.rfc-editor.org/info/rfc2503 | |
| RFC2504;;Guttman, E., Leong, L., and G. Malkin;Users' Security Handbook;;FYI 34;;;RFC 2504;DOI 10.17487/RFC2504;February;https://www.rfc-editor.org/info/rfc2504 | |
| RFC2505;;Lindberg, G.;Anti-Spam Recommendations for SMTP MTAs;;;BCP 30;;RFC 2505;DOI 10.17487/RFC2505;February;https://www.rfc-editor.org/info/rfc2505 | |
| RFC2506;;Holtman, K., Mutz, A., and T. Hardie;Media Feature Tag Registration Procedure;;;BCP 31;;RFC 2506;DOI 10.17487/RFC2506;March;https://www.rfc-editor.org/info/rfc2506 | |
| RFC2507;;Degermark, M., Nordgren, B., and S. Pink;IP Header Compression;;;;;RFC 2507;DOI 10.17487/RFC2507;February;https://www.rfc-editor.org/info/rfc2507 | |
| RFC2508;;Casner, S. and V. Jacobson;Compressing IP/UDP/RTP Headers for Low-Speed Serial Links;;;;;RFC 2508;DOI 10.17487/RFC2508;February;https://www.rfc-editor.org/info/rfc2508 | |
| RFC2509;RFC3544;Engan, M., Casner, S., and C. Bormann;IP Header Compression over PPP;;;;;RFC 2509;DOI 10.17487/RFC2509;February;https://www.rfc-editor.org/info/rfc2509 | |
| RFC2510;RFC4210;Adams, C. and S. Farrell;Internet X.509 Public Key Infrastructure Certificate Management Protocols;;;;;RFC 2510;DOI 10.17487/RFC2510;March;https://www.rfc-editor.org/info/rfc2510 | |
| RFC2511;RFC4211;Myers, M., Adams, C., Solo, D., and D. Kemp;Internet X.509 Certificate Request Message Format;;;;;RFC 2511;DOI 10.17487/RFC2511;March;https://www.rfc-editor.org/info/rfc2511 | |
| RFC2512;;McCloghrie, K., Heinanen, J., Greene, W., and A. Prasad;Accounting Information for ATM Networks;;;;;RFC 2512;DOI 10.17487/RFC2512;February;https://www.rfc-editor.org/info/rfc2512 | |
| RFC2513;;McCloghrie, K., Heinanen, J., Greene, W., and A. Prasad;Managed Objects for Controlling the Collection and Storage of Accounting Information for Connection-Oriented Networks;;;;;RFC 2513;DOI 10.17487/RFC2513;February;https://www.rfc-editor.org/info/rfc2513 | |
| RFC2514;;Noto, M., Spiegel, E., and K. Tesink;Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management;;;;;RFC 2514;DOI 10.17487/RFC2514;February;https://www.rfc-editor.org/info/rfc2514 | |
| RFC2515;;Tesink, K., Ed.;Definitions of Managed Objects for ATM Management;;;;;RFC 2515;DOI 10.17487/RFC2515;February;https://www.rfc-editor.org/info/rfc2515 | |
| RFC2516;;Mamakos, L., Lidl, K., Evarts, J., Carrel, D., Simone, D., and R. Wheeler;A Method for Transmitting PPP Over Ethernet (PPPoE);;;;;RFC 2516;DOI 10.17487/RFC2516;February;https://www.rfc-editor.org/info/rfc2516 | |
| RFC2517;;Moats, R. and R. Huber;Building Directories from DNS: Experiences from WWWSeeker;;;;;RFC 2517;DOI 10.17487/RFC2517;February;https://www.rfc-editor.org/info/rfc2517 | |
| RFC2518;RFC4918;Goland, Y., Whitehead, E., Faizi, A., Carter, S., and D. Jensen;HTTP Extensions for Distributed Authoring -- WEBDAV;;;;;RFC 2518;DOI 10.17487/RFC2518;February;https://www.rfc-editor.org/info/rfc2518 | |
| RFC2519;;Chen, E. and J. Stewart;A Framework for Inter-Domain Route Aggregation;;;;;RFC 2519;DOI 10.17487/RFC2519;February;https://www.rfc-editor.org/info/rfc2519 | |
| RFC2520;;Luciani, J., Suzuki, H., Doraswamy, N., and D. Horton;NHRP with Mobile NHCs;;;;;RFC 2520;DOI 10.17487/RFC2520;February;https://www.rfc-editor.org/info/rfc2520 | |
| RFC2521;;Karn, P. and W. Simpson;ICMP Security Failures Messages;;;;;RFC 2521;DOI 10.17487/RFC2521;March;https://www.rfc-editor.org/info/rfc2521 | |
| RFC2522;;Karn, P. and W. Simpson;Photuris: Session-Key Management Protocol;;;;;RFC 2522;DOI 10.17487/RFC2522;March;https://www.rfc-editor.org/info/rfc2522 | |
| RFC2523;;Karn, P. and W. Simpson;Photuris: Extended Schemes and Attributes;;;;;RFC 2523;DOI 10.17487/RFC2523;March;https://www.rfc-editor.org/info/rfc2523 | |
| RFC2524;;Banan, M.;Neda's Efficient Mail Submission and Delivery (EMSD) Protocol Specification Version 1.3;;;;;RFC 2524;DOI 10.17487/RFC2524;February;https://www.rfc-editor.org/info/rfc2524 | |
| RFC2525;;Paxson, V., Allman, M., Dawson, S., Fenner, W., Griner, J., Heavens, I., Lahey, K., Semke, J., and B. Volz;Known TCP Implementation Problems;;;;;RFC 2525;DOI 10.17487/RFC2525;March;https://www.rfc-editor.org/info/rfc2525 | |
| RFC2526;;Johnson, D. and S. Deering;Reserved IPv6 Subnet Anycast Addresses;;;;;RFC 2526;DOI 10.17487/RFC2526;March;https://www.rfc-editor.org/info/rfc2526 | |
| RFC2527;RFC3647;Chokhani, S. and W. Ford;Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices Framework;;;;;RFC 2527;DOI 10.17487/RFC2527;March;https://www.rfc-editor.org/info/rfc2527 | |
| RFC2528;;Housley, R. and W. Polk;Internet X.509 Public Key Infrastructure Representation of Key Exchange Algorithm (KEA) Keys in Internet X.509 Public Key Infrastructure Certificates;;;;;RFC 2528;DOI 10.17487/RFC2528;March;https://www.rfc-editor.org/info/rfc2528 | |
| RFC2529;;Carpenter, B. and C. Jung;Transmission of IPv6 over IPv4 Domains without Explicit Tunnels;;;;;RFC 2529;DOI 10.17487/RFC2529;March;https://www.rfc-editor.org/info/rfc2529 | |
| RFC2530;;Wing, D.;Indicating Supported Media Features Using Extensions to DSN and MDN;;;;;RFC 2530;DOI 10.17487/RFC2530;March;https://www.rfc-editor.org/info/rfc2530 | |
| RFC2531;RFC2879;Klyne, G. and L. McIntyre;Content Feature Schema for Internet Fax;;;;;RFC 2531;DOI 10.17487/RFC2531;March;https://www.rfc-editor.org/info/rfc2531 | |
| RFC2532;;Masinter, L. and D. Wing;Extended Facsimile Using Internet Mail;;;;;RFC 2532;DOI 10.17487/RFC2532;March;https://www.rfc-editor.org/info/rfc2532 | |
| RFC2533;;Klyne, G.;A Syntax for Describing Media Feature Sets;;;;;RFC 2533;DOI 10.17487/RFC2533;March;https://www.rfc-editor.org/info/rfc2533 | |
| RFC2534;;Masinter, L., Wing, D., Mutz, A., and K. Holtman;Media Features for Display, Print, and Fax;;;;;RFC 2534;DOI 10.17487/RFC2534;March;https://www.rfc-editor.org/info/rfc2534 | |
| RFC2535;RFC4033, RFC4034, RFC4035;Eastlake 3rd, D.;Domain Name System Security Extensions;;;;;RFC 2535;DOI 10.17487/RFC2535;March;https://www.rfc-editor.org/info/rfc2535 | |
| RFC2536;;Eastlake 3rd, D.;DSA KEYs and SIGs in the Domain Name System (DNS);;;;;RFC 2536;DOI 10.17487/RFC2536;March;https://www.rfc-editor.org/info/rfc2536 | |
| RFC2537;RFC3110;Eastlake 3rd, D.;RSA/MD5 KEYs and SIGs in the Domain Name System (DNS);;;;;RFC 2537;DOI 10.17487/RFC2537;March;https://www.rfc-editor.org/info/rfc2537 | |
| RFC2538;RFC4398;Eastlake 3rd, D. and O. Gudmundsson;Storing Certificates in the Domain Name System (DNS);;;;;RFC 2538;DOI 10.17487/RFC2538;March;https://www.rfc-editor.org/info/rfc2538 | |
| RFC2539;;Eastlake 3rd, D.;Storage of Diffie-Hellman Keys in the Domain Name System (DNS);;;;;RFC 2539;DOI 10.17487/RFC2539;March;https://www.rfc-editor.org/info/rfc2539 | |
| RFC2540;;Eastlake 3rd, D.;Detached Domain Name System (DNS) Information;;;;;RFC 2540;DOI 10.17487/RFC2540;March;https://www.rfc-editor.org/info/rfc2540 | |
| RFC2541;RFC4641;Eastlake 3rd, D.;DNS Security Operational Considerations;;;;;RFC 2541;DOI 10.17487/RFC2541;March;https://www.rfc-editor.org/info/rfc2541 | |
| RFC2542;;Masinter, L.;Terminology and Goals for Internet Fax;;;;;RFC 2542;DOI 10.17487/RFC2542;March;https://www.rfc-editor.org/info/rfc2542 | |
| RFC2543;RFC3261, RFC3262, RFC3263, RFC3264, RFC3265;Handley, M., Schulzrinne, H., Schooler, E., and J. Rosenberg;SIP: Session Initiation Protocol;;;;;RFC 2543;DOI 10.17487/RFC2543;March;https://www.rfc-editor.org/info/rfc2543 | |
| RFC2544;;Bradner, S. and J. McQuaid;Benchmarking Methodology for Network Interconnect Devices;;;;;RFC 2544;DOI 10.17487/RFC2544;March;https://www.rfc-editor.org/info/rfc2544 | |
| RFC2545;;Marques, P. and F. Dupont;Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing;;;;;RFC 2545;DOI 10.17487/RFC2545;March;https://www.rfc-editor.org/info/rfc2545 | |
| RFC2546;RFC2772;Durand, A. and B. Buclin;6Bone Routing Practice;;;;;RFC 2546;DOI 10.17487/RFC2546;March;https://www.rfc-editor.org/info/rfc2546 | |
| RFC2547;RFC4364;Rosen, E. and Y. Rekhter;BGP/MPLS VPNs;;;;;RFC 2547;DOI 10.17487/RFC2547;March;https://www.rfc-editor.org/info/rfc2547 | |
| RFC2548;;Zorn, G.;Microsoft Vendor-specific RADIUS Attributes;;;;;RFC 2548;DOI 10.17487/RFC2548;March;https://www.rfc-editor.org/info/rfc2548 | |
| RFC2549;;Waitzman, D.;IP over Avian Carriers with Quality of Service;;;;;RFC 2549;DOI 10.17487/RFC2549;April;https://www.rfc-editor.org/info/rfc2549 | |
| RFC2550;;Glassman, S., Manasse, M., and J. Mogul;Y10K and Beyond;;;;;RFC 2550;DOI 10.17487/RFC2550;April;https://www.rfc-editor.org/info/rfc2550 | |
| RFC2551;;Bradner, S.;The Roman Standards Process -- Revision III;;;;;RFC 2551;DOI 10.17487/RFC2551;April;https://www.rfc-editor.org/info/rfc2551 | |
| RFC2552;;Blinov, M., Bessonov, M., and C. Clissmann;Architecture for the Information Brokerage in the ACTS Project GAIA;;;;;RFC 2552;DOI 10.17487/RFC2552;April;https://www.rfc-editor.org/info/rfc2552 | |
| RFC2553;RFC3493;Gilligan, R., Thomson, S., Bound, J., and W. Stevens;Basic Socket Interface Extensions for IPv6;;;;;RFC 2553;DOI 10.17487/RFC2553;March;https://www.rfc-editor.org/info/rfc2553 | |
| RFC2554;RFC4954;Myers, J.;SMTP Service Extension for Authentication;;;;;RFC 2554;DOI 10.17487/RFC2554;March;https://www.rfc-editor.org/info/rfc2554 | |
| RFC2555;;RFC Editor, et al.;30 Years of RFCs;;;;;RFC 2555;DOI 10.17487/RFC2555;April;https://www.rfc-editor.org/info/rfc2555 | |
| RFC2556;;Bradner, S.;OSI connectionless transport services on top of UDP Applicability Statement for Historic Status;;;;;RFC 2556;DOI 10.17487/RFC2556;March;https://www.rfc-editor.org/info/rfc2556 | |
| RFC2557;;Palme, J., Hopmann, A., and N. Shelness;MIME Encapsulation of Aggregate Documents, such as HTML (MHTML);;;;;RFC 2557;DOI 10.17487/RFC2557;March;https://www.rfc-editor.org/info/rfc2557 | |
| RFC2558;RFC3592;Tesink, K.;Definitions of Managed Objects for the SONET/SDH Interface Type;;;;;RFC 2558;DOI 10.17487/RFC2558;March;https://www.rfc-editor.org/info/rfc2558 | |
| RFC2559;RFC3494;Boeyen, S., Howes, T., and P. Richard;Internet X.509 Public Key Infrastructure Operational Protocols - LDAPv2;;;;;RFC 2559;DOI 10.17487/RFC2559;April;https://www.rfc-editor.org/info/rfc2559 | |
| RFC2560;RFC6960;Myers, M., Ankney, R., Malpani, A., Galperin, S., and C. Adams;X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP;;;;;RFC 2560;DOI 10.17487/RFC2560;June;https://www.rfc-editor.org/info/rfc2560 | |
| RFC2561;;White, K. and R. Moore;Base Definitions of Managed Objects for TN3270E Using SMIv2;;;;;RFC 2561;DOI 10.17487/RFC2561;April;https://www.rfc-editor.org/info/rfc2561 | |
| RFC2562;;White, K. and R. Moore;Definitions of Protocol and Managed Objects for TN3270E Response Time Collection Using SMIv2 (TN3270E-RT-MIB);;;;;RFC 2562;DOI 10.17487/RFC2562;April;https://www.rfc-editor.org/info/rfc2562 | |
| RFC2563;;Troll, R.;DHCP Option to Disable Stateless Auto-Configuration in IPv4 Clients;;;;;RFC 2563;DOI 10.17487/RFC2563;May;https://www.rfc-editor.org/info/rfc2563 | |
| RFC2564;;Kalbfleisch, C., Krupczak, C., Presuhn, R., and J. Saperia;Application Management MIB;;;;;RFC 2564;DOI 10.17487/RFC2564;May;https://www.rfc-editor.org/info/rfc2564 | |
| RFC2565;RFC2910;Herriot, R., Ed., Butler, S., Moore, P., and R. Turner;Internet Printing Protocol/1.0: Encoding and Transport;;;;;RFC 2565;DOI 10.17487/RFC2565;April;https://www.rfc-editor.org/info/rfc2565 | |
| RFC2566;RFC2911;deBry, R., Hastings, T., Herriot, R., Isaacson, S., and P. Powell;Internet Printing Protocol/1.0: Model and Semantics;;;;;RFC 2566;DOI 10.17487/RFC2566;April;https://www.rfc-editor.org/info/rfc2566 | |
| RFC2567;;Wright, F.;Design Goals for an Internet Printing Protocol;;;;;RFC 2567;DOI 10.17487/RFC2567;April;https://www.rfc-editor.org/info/rfc2567 | |
| RFC2568;;Zilles, S.;Rationale for the Structure of the Model and Protocol for the Internet Printing Protocol;;;;;RFC 2568;DOI 10.17487/RFC2568;April;https://www.rfc-editor.org/info/rfc2568 | |
| RFC2569;;Herriot, R., Ed., Hastings, T., Jacobs, N., and J. Martin;Mapping between LPD and IPP Protocols;;;;;RFC 2569;DOI 10.17487/RFC2569;April;https://www.rfc-editor.org/info/rfc2569 | |
| RFC2570;RFC3410;Case, J., Mundy, R., Partain, D., and B. Stewart;Introduction to Version 3 of the Internet-standard Network Management Framework;;;;;RFC 2570;DOI 10.17487/RFC2570;April;https://www.rfc-editor.org/info/rfc2570 | |
| RFC2571;RFC3411;Wijnen, B., Harrington, D., and R. Presuhn;An Architecture for Describing SNMP Management Frameworks;;;;;RFC 2571;DOI 10.17487/RFC2571;April;https://www.rfc-editor.org/info/rfc2571 | |
| RFC2572;RFC3412;Case, J., Harrington, D., Presuhn, R., and B. Wijnen;Message Processing and Dispatching for the Simple Network Management Protocol (SNMP);;;;;RFC 2572;DOI 10.17487/RFC2572;April;https://www.rfc-editor.org/info/rfc2572 | |
| RFC2573;RFC3413;Levi, D., Meyer, P., and B. Stewart;SNMP Applications;;;;;RFC 2573;DOI 10.17487/RFC2573;April;https://www.rfc-editor.org/info/rfc2573 | |
| RFC2574;RFC3414;Blumenthal, U. and B. Wijnen;User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3);;;;;RFC 2574;DOI 10.17487/RFC2574;April;https://www.rfc-editor.org/info/rfc2574 | |
| RFC2575;RFC3415;Wijnen, B., Presuhn, R., and K. McCloghrie;View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP);;;;;RFC 2575;DOI 10.17487/RFC2575;April;https://www.rfc-editor.org/info/rfc2575 | |
| RFC2576;RFC3584;Frye, R., Levi, D., Routhier, S., and B. Wijnen;Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework;;;;;RFC 2576;DOI 10.17487/RFC2576;March;https://www.rfc-editor.org/info/rfc2576 | |
| RFC2577;;Allman, M. and S. Ostermann;FTP Security Considerations;;;;;RFC 2577;DOI 10.17487/RFC2577;May;https://www.rfc-editor.org/info/rfc2577 | |
| RFC2578;;McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed.;Structure of Management Information Version 2 (SMIv2);;;;STD 58;RFC 2578;DOI 10.17487/RFC2578;April;https://www.rfc-editor.org/info/rfc2578 | |
| RFC2579;;McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed.;Textual Conventions for SMIv2;;;;STD 58;RFC 2579;DOI 10.17487/RFC2579;April;https://www.rfc-editor.org/info/rfc2579 | |
| RFC2580;;McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed.;Conformance Statements for SMIv2;;;;STD 58;RFC 2580;DOI 10.17487/RFC2580;April;https://www.rfc-editor.org/info/rfc2580 | |
| RFC2581;RFC5681;Allman, M., Paxson, V., and W. Stevens;TCP Congestion Control;;;;;RFC 2581;DOI 10.17487/RFC2581;April;https://www.rfc-editor.org/info/rfc2581 | |
| RFC2582;RFC3782;Floyd, S. and T. Henderson;The NewReno Modification to TCP's Fast Recovery Algorithm;;;;;RFC 2582;DOI 10.17487/RFC2582;April;https://www.rfc-editor.org/info/rfc2582 | |
| RFC2583;;Carlson, R. and L. Winkler;Guidelines for Next Hop Client (NHC) Developers;;;;;RFC 2583;DOI 10.17487/RFC2583;May;https://www.rfc-editor.org/info/rfc2583 | |
| RFC2584;;Clouston, B. and B. Moore;Definitions of Managed Objects for APPN/HPR in IP Networks;;;;;RFC 2584;DOI 10.17487/RFC2584;May;https://www.rfc-editor.org/info/rfc2584 | |
| RFC2585;;Housley, R. and P. Hoffman;Internet X.509 Public Key Infrastructure Operational Protocols: FTP and HTTP;;;;;RFC 2585;DOI 10.17487/RFC2585;May;https://www.rfc-editor.org/info/rfc2585 | |
| RFC2586;;Salsman, J. and H. Alvestrand;The Audio/L16 MIME content type;;;;;RFC 2586;DOI 10.17487/RFC2586;May;https://www.rfc-editor.org/info/rfc2586 | |
| RFC2587;RFC4523;Boeyen, S., Howes, T., and P. Richard;Internet X.509 Public Key Infrastructure LDAPv2 Schema;;;;;RFC 2587;DOI 10.17487/RFC2587;June;https://www.rfc-editor.org/info/rfc2587 | |
| RFC2588;;Finlayson, R.;IP Multicast and Firewalls;;;;;RFC 2588;DOI 10.17487/RFC2588;May;https://www.rfc-editor.org/info/rfc2588 | |
| RFC2589;;Yaacovi, Y., Wahl, M., and T. Genovese;Lightweight Directory Access Protocol (v3): Extensions for Dynamic Directory Services;;;;;RFC 2589;DOI 10.17487/RFC2589;May;https://www.rfc-editor.org/info/rfc2589 | |
| RFC2590;;Conta, A., Malis, A., and M. Mueller;Transmission of IPv6 Packets over Frame Relay Networks Specification;;;;;RFC 2590;DOI 10.17487/RFC2590;May;https://www.rfc-editor.org/info/rfc2590 | |
| RFC2591;RFC3231;Levi, D. and J. Schoenwaelder;Definitions of Managed Objects for Scheduling Management Operations;;;;;RFC 2591;DOI 10.17487/RFC2591;May;https://www.rfc-editor.org/info/rfc2591 | |
| RFC2592;RFC3165;Levi, D. and J. Schoenwaelder;Definitions of Managed Objects for the Delegation of Management Script;;;;;RFC 2592;DOI 10.17487/RFC2592;May;https://www.rfc-editor.org/info/rfc2592 | |
| RFC2593;RFC3179;Schoenwaelder, J. and J. Quittek;Script MIB Extensibility Protocol Version 1.0;;;;;RFC 2593;DOI 10.17487/RFC2593;May;https://www.rfc-editor.org/info/rfc2593 | |
| RFC2594;;Hazewinkel, H., Kalbfleisch, C., and J. Schoenwaelder;Definitions of Managed Objects for WWW Services;;;;;RFC 2594;DOI 10.17487/RFC2594;May;https://www.rfc-editor.org/info/rfc2594 | |
| RFC2595;;Newman, C.;Using TLS with IMAP, POP3 and ACAP;;;;;RFC 2595;DOI 10.17487/RFC2595;June;https://www.rfc-editor.org/info/rfc2595 | |
| RFC2596;RFC3866;Wahl, M. and T. Howes;Use of Language Codes in LDAP;;;;;RFC 2596;DOI 10.17487/RFC2596;May;https://www.rfc-editor.org/info/rfc2596 | |
| RFC2597;;Heinanen, J., Baker, F., Weiss, W., and J. Wroclawski;Assured Forwarding PHB Group;;;;;RFC 2597;DOI 10.17487/RFC2597;June;https://www.rfc-editor.org/info/rfc2597 | |
| RFC2598;RFC3246;Jacobson, V., Nichols, K., and K. Poduri;An Expedited Forwarding PHB;;;;;RFC 2598;DOI 10.17487/RFC2598;June;https://www.rfc-editor.org/info/rfc2598 | |
| RFC2599;;DeLaCruz, A.;Request for Comments Summary RFC Numbers 2500-2599;;;;;RFC 2599;DOI 10.17487/RFC2599;March;https://www.rfc-editor.org/info/rfc2599 | |
| RFC2600;RFC2700;Reynolds, J. and R. Braden;Internet Official Protocol Standards;;;;;RFC 2600;DOI 10.17487/RFC2600;March;https://www.rfc-editor.org/info/rfc2600 | |
| RFC2601;;Davison, M.;ILMI-Based Server Discovery for ATMARP;;;;;RFC 2601;DOI 10.17487/RFC2601;June;https://www.rfc-editor.org/info/rfc2601 | |
| RFC2602;;Davison, M.;ILMI-Based Server Discovery for MARS;;;;;RFC 2602;DOI 10.17487/RFC2602;June;https://www.rfc-editor.org/info/rfc2602 | |
| RFC2603;;Davison, M.;ILMI-Based Server Discovery for NHRP;;;;;RFC 2603;DOI 10.17487/RFC2603;June;https://www.rfc-editor.org/info/rfc2603 | |
| RFC2604;RFC2636;Gellens, R.;Wireless Device Configuration (OTASP/OTAPA) via ACAP;;;;;RFC 2604;DOI 10.17487/RFC2604;June;https://www.rfc-editor.org/info/rfc2604 | |
| RFC2605;;Mansfield, G. and S. Kille;Directory Server Monitoring MIB;;;;;RFC 2605;DOI 10.17487/RFC2605;June;https://www.rfc-editor.org/info/rfc2605 | |
| RFC2606;;Eastlake 3rd, D. and A. Panitz;Reserved Top Level DNS Names;;;BCP 32;;RFC 2606;DOI 10.17487/RFC2606;June;https://www.rfc-editor.org/info/rfc2606 | |
| RFC2607;;Aboba, B. and J. Vollbrecht;Proxy Chaining and Policy Implementation in Roaming;;;;;RFC 2607;DOI 10.17487/RFC2607;June;https://www.rfc-editor.org/info/rfc2607 | |
| RFC2608;;Guttman, E., Perkins, C., Veizades, J., and M. Day;Service Location Protocol, Version 2;;;;;RFC 2608;DOI 10.17487/RFC2608;June;https://www.rfc-editor.org/info/rfc2608 | |
| RFC2609;;Guttman, E., Perkins, C., and J. Kempf;Service Templates and Service: Schemes;;;;;RFC 2609;DOI 10.17487/RFC2609;June;https://www.rfc-editor.org/info/rfc2609 | |
| RFC2610;;Perkins, C. and E. Guttman;DHCP Options for Service Location Protocol;;;;;RFC 2610;DOI 10.17487/RFC2610;June;https://www.rfc-editor.org/info/rfc2610 | |
| RFC2611;RFC3406;Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom;URN Namespace Definition Mechanisms;;;BCP 33;;RFC 2611;DOI 10.17487/RFC2611;June;https://www.rfc-editor.org/info/rfc2611 | |
| RFC2612;;Adams, C. and J. Gilchrist;The CAST-256 Encryption Algorithm;;;;;RFC 2612;DOI 10.17487/RFC2612;June;https://www.rfc-editor.org/info/rfc2612 | |
| RFC2613;;Waterman, R., Lahaye, B., Romascanu, D., and S. Waldbusser;Remote Network Monitoring MIB Extensions for Switched Networks Version 1.0;;;;;RFC 2613;DOI 10.17487/RFC2613;June;https://www.rfc-editor.org/info/rfc2613 | |
| RFC2614;;Kempf, J. and E. Guttman;An API for Service Location;;;;;RFC 2614;DOI 10.17487/RFC2614;June;https://www.rfc-editor.org/info/rfc2614 | |
| RFC2615;;Malis, A. and W. Simpson;PPP over SONET/SDH;;;;;RFC 2615;DOI 10.17487/RFC2615;June;https://www.rfc-editor.org/info/rfc2615 | |
| RFC2616;RFC7230, RFC7231, RFC7232, RFC7233, RFC7234, RFC7235;Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee;Hypertext Transfer Protocol -- HTTP/1.1;;;;;RFC 2616;DOI 10.17487/RFC2616;June;https://www.rfc-editor.org/info/rfc2616 | |
| RFC2617;RFC7235, RFC7615, RFC7616, RFC7617;Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., Leach, P., Luotonen, A., and L. Stewart;HTTP Authentication: Basic and Digest Access Authentication;;;;;RFC 2617;DOI 10.17487/RFC2617;June;https://www.rfc-editor.org/info/rfc2617 | |
| RFC2618;RFC4668;Aboba, B. and G. Zorn;RADIUS Authentication Client MIB;;;;;RFC 2618;DOI 10.17487/RFC2618;June;https://www.rfc-editor.org/info/rfc2618 | |
| RFC2619;RFC4669;Zorn, G. and B. Aboba;RADIUS Authentication Server MIB;;;;;RFC 2619;DOI 10.17487/RFC2619;June;https://www.rfc-editor.org/info/rfc2619 | |
| RFC2620;RFC4670;Aboba, B. and G. Zorn;RADIUS Accounting Client MIB;;;;;RFC 2620;DOI 10.17487/RFC2620;June;https://www.rfc-editor.org/info/rfc2620 | |
| RFC2621;RFC4671;Zorn, G. and B. Aboba;RADIUS Accounting Server MIB;;;;;RFC 2621;DOI 10.17487/RFC2621;June;https://www.rfc-editor.org/info/rfc2621 | |
| RFC2622;;Alaettinoglu, C., Villamizar, C., Gerich, E., Kessens, D., Meyer, D., Bates, T., Karrenberg, D., and M. Terpstra;Routing Policy Specification Language (RPSL);;;;;RFC 2622;DOI 10.17487/RFC2622;June;https://www.rfc-editor.org/info/rfc2622 | |
| RFC2623;;Eisler, M.;NFS Version 2 and Version 3 Security Issues and the NFS Protocol's Use of RPCSEC_GSS and Kerberos V5;;;;;RFC 2623;DOI 10.17487/RFC2623;June;https://www.rfc-editor.org/info/rfc2623 | |
| RFC2624;;Shepler, S.;NFS Version 4 Design Considerations;;;;;RFC 2624;DOI 10.17487/RFC2624;June;https://www.rfc-editor.org/info/rfc2624 | |
| RFC2625;RFC4338;Rajagopal, M., Bhagwat, R., and W. Rickard;IP and ARP over Fibre Channel;;;;;RFC 2625;DOI 10.17487/RFC2625;June;https://www.rfc-editor.org/info/rfc2625 | |
| RFC2626;;Nesser II, P.;The Internet and the Millennium Problem (Year 2000);;;;;RFC 2626;DOI 10.17487/RFC2626;June;https://www.rfc-editor.org/info/rfc2626 | |
| RFC2627;;Wallner, D., Harder, E., and R. Agee;Key Management for Multicast: Issues and Architectures;;;;;RFC 2627;DOI 10.17487/RFC2627;June;https://www.rfc-editor.org/info/rfc2627 | |
| RFC2628;;Smyslov, V.;Simple Cryptographic Program Interface (Crypto API);;;;;RFC 2628;DOI 10.17487/RFC2628;June;https://www.rfc-editor.org/info/rfc2628 | |
| RFC2629;RFC7749;Rose, M.;Writing I-Ds and RFCs using XML;;;;;RFC 2629;DOI 10.17487/RFC2629;June;https://www.rfc-editor.org/info/rfc2629 | |
| RFC2630;RFC3369, RFC3370;Housley, R.;Cryptographic Message Syntax;;;;;RFC 2630;DOI 10.17487/RFC2630;June;https://www.rfc-editor.org/info/rfc2630 | |
| RFC2631;;Rescorla, E.;Diffie-Hellman Key Agreement Method;;;;;RFC 2631;DOI 10.17487/RFC2631;June;https://www.rfc-editor.org/info/rfc2631 | |
| RFC2632;RFC3850;Ramsdell, B., Ed.;S/MIME Version 3 Certificate Handling;;;;;RFC 2632;DOI 10.17487/RFC2632;June;https://www.rfc-editor.org/info/rfc2632 | |
| RFC2633;RFC3851;Ramsdell, B., Ed.;S/MIME Version 3 Message Specification;;;;;RFC 2633;DOI 10.17487/RFC2633;June;https://www.rfc-editor.org/info/rfc2633 | |
| RFC2634;;Hoffman, P., Ed.;Enhanced Security Services for S/MIME;;;;;RFC 2634;DOI 10.17487/RFC2634;June;https://www.rfc-editor.org/info/rfc2634 | |
| RFC2635;;Hambridge, S. and A. Lunde;DON'T SPEW A Set of Guidelines for Mass Unsolicited Mailings and Postings (spam*);;FYI 35;;;RFC 2635;DOI 10.17487/RFC2635;June;https://www.rfc-editor.org/info/rfc2635 | |
| RFC2636;;Gellens, R.;Wireless Device Configuration (OTASP/OTAPA) via ACAP;;;;;RFC 2636;DOI 10.17487/RFC2636;July;https://www.rfc-editor.org/info/rfc2636 | |
| RFC2637;;Hamzeh, K., Pall, G., Verthein, W., Taarud, J., Little, W., and G. Zorn;Point-to-Point Tunneling Protocol (PPTP);;;;;RFC 2637;DOI 10.17487/RFC2637;July;https://www.rfc-editor.org/info/rfc2637 | |
| RFC2638;;Nichols, K., Jacobson, V., and L. Zhang;A Two-bit Differentiated Services Architecture for the Internet;;;;;RFC 2638;DOI 10.17487/RFC2638;July;https://www.rfc-editor.org/info/rfc2638 | |
| RFC2639;RFC3196;Hastings, T. and C. Manros;Internet Printing Protocol/1.0: Implementer's Guide;;;;;RFC 2639;DOI 10.17487/RFC2639;July;https://www.rfc-editor.org/info/rfc2639 | |
| RFC2640;;Curtin, B.;Internationalization of the File Transfer Protocol;;;;;RFC 2640;DOI 10.17487/RFC2640;July;https://www.rfc-editor.org/info/rfc2640 | |
| RFC2641;;Hamilton, D. and D. Ruffen;Cabletron's VlanHello Protocol Specification Version 4;;;;;RFC 2641;DOI 10.17487/RFC2641;August;https://www.rfc-editor.org/info/rfc2641 | |
| RFC2642;;Kane, L.;Cabletron's VLS Protocol Specification;;;;;RFC 2642;DOI 10.17487/RFC2642;August;https://www.rfc-editor.org/info/rfc2642 | |
| RFC2643;;Ruffen, D., Len, T., and J. Yanacek;Cabletron's SecureFast VLAN Operational Model;;;;;RFC 2643;DOI 10.17487/RFC2643;August;https://www.rfc-editor.org/info/rfc2643 | |
| RFC2644;;Senie, D.;Changing the Default for Directed Broadcasts in Routers;;;BCP 34;;RFC 2644;DOI 10.17487/RFC2644;August;https://www.rfc-editor.org/info/rfc2644 | |
| RFC2645;;Gellens, R.;ON-DEMAND MAIL RELAY (ODMR) SMTP with Dynamic IP Addresses;;;;;RFC 2645;DOI 10.17487/RFC2645;August;https://www.rfc-editor.org/info/rfc2645 | |
| RFC2646;RFC3676;Gellens, R., Ed.;The Text/Plain Format Parameter;;;;;RFC 2646;DOI 10.17487/RFC2646;August;https://www.rfc-editor.org/info/rfc2646 | |
| RFC2647;;Newman, D.;Benchmarking Terminology for Firewall Performance;;;;;RFC 2647;DOI 10.17487/RFC2647;August;https://www.rfc-editor.org/info/rfc2647 | |
| RFC2648;;Moats, R.;A URN Namespace for IETF Documents;;;;;RFC 2648;DOI 10.17487/RFC2648;August;https://www.rfc-editor.org/info/rfc2648 | |
| RFC2649;;Greenblatt, B. and P. Richard;An LDAP Control and Schema for Holding Operation Signatures;;;;;RFC 2649;DOI 10.17487/RFC2649;August;https://www.rfc-editor.org/info/rfc2649 | |
| RFC2650;;Meyer, D., Schmitz, J., Orange, C., Prior, M., and C. Alaettinoglu;Using RPSL in Practice;;;;;RFC 2650;DOI 10.17487/RFC2650;August;https://www.rfc-editor.org/info/rfc2650 | |
| RFC2651;;Allen, J. and M. Mealling;The Architecture of the Common Indexing Protocol (CIP);;;;;RFC 2651;DOI 10.17487/RFC2651;August;https://www.rfc-editor.org/info/rfc2651 | |
| RFC2652;;Allen, J. and M. Mealling;MIME Object Definitions for the Common Indexing Protocol (CIP);;;;;RFC 2652;DOI 10.17487/RFC2652;August;https://www.rfc-editor.org/info/rfc2652 | |
| RFC2653;;Allen, J., Leach, P., and R. Hedberg;CIP Transport Protocols;;;;;RFC 2653;DOI 10.17487/RFC2653;August;https://www.rfc-editor.org/info/rfc2653 | |
| RFC2654;;Hedberg, R., Greenblatt, B., Moats, R., and M. Wahl;A Tagged Index Object for use in the Common Indexing Protocol;;;;;RFC 2654;DOI 10.17487/RFC2654;August;https://www.rfc-editor.org/info/rfc2654 | |
| RFC2655;;Hardie, T., Bowman, M., Hardy, D., Schwartz, M., and D. Wessels;CIP Index Object Format for SOIF Objects;;;;;RFC 2655;DOI 10.17487/RFC2655;August;https://www.rfc-editor.org/info/rfc2655 | |
| RFC2656;;Hardie, T.;Registration Procedures for SOIF Template Types;;;;;RFC 2656;DOI 10.17487/RFC2656;August;https://www.rfc-editor.org/info/rfc2656 | |
| RFC2657;;Hedberg, R.;LDAPv2 Client vs. the Index Mesh;;;;;RFC 2657;DOI 10.17487/RFC2657;August;https://www.rfc-editor.org/info/rfc2657 | |
| RFC2658;;McKay, K.;RTP Payload Format for PureVoice(tm) Audio;;;;;RFC 2658;DOI 10.17487/RFC2658;August;https://www.rfc-editor.org/info/rfc2658 | |
| RFC2659;;Rescorla, E. and A. Schiffman;Security Extensions For HTML;;;;;RFC 2659;DOI 10.17487/RFC2659;August;https://www.rfc-editor.org/info/rfc2659 | |
| RFC2660;;Rescorla, E. and A. Schiffman;The Secure HyperText Transfer Protocol;;;;;RFC 2660;DOI 10.17487/RFC2660;August;https://www.rfc-editor.org/info/rfc2660 | |
| RFC2661;;Townsley, W., Valencia, A., Rubens, A., Pall, G., Zorn, G., and B. Palter;Layer Two Tunneling Protocol "L2TP";;;;;RFC 2661;DOI 10.17487/RFC2661;August;https://www.rfc-editor.org/info/rfc2661 | |
| RFC2662;;Bathrick, G. and F. Ly;Definitions of Managed Objects for the ADSL Lines;;;;;RFC 2662;DOI 10.17487/RFC2662;August;https://www.rfc-editor.org/info/rfc2662 | |
| RFC2663;;Srisuresh, P. and M. Holdrege;IP Network Address Translator (NAT) Terminology and Considerations;;;;;RFC 2663;DOI 10.17487/RFC2663;August;https://www.rfc-editor.org/info/rfc2663 | |
| RFC2664;;Plzak, R., Wells, A., and E. Krol;FYI on Questions and Answers - Answers to Commonly Asked "New Internet User" Questions;;FYI 4;;;RFC 2664;DOI 10.17487/RFC2664;August;https://www.rfc-editor.org/info/rfc2664 | |
| RFC2665;RFC3635;Flick, J. and J. Johnson;Definitions of Managed Objects for the Ethernet-like Interface Types;;;;;RFC 2665;DOI 10.17487/RFC2665;August;https://www.rfc-editor.org/info/rfc2665 | |
| RFC2666;;Flick, J.;Definitions of Object Identifiers for Identifying Ethernet Chip Sets;;;;;RFC 2666;DOI 10.17487/RFC2666;August;https://www.rfc-editor.org/info/rfc2666 | |
| RFC2667;RFC4087;Thaler, D.;IP Tunnel MIB;;;;;RFC 2667;DOI 10.17487/RFC2667;August;https://www.rfc-editor.org/info/rfc2667 | |
| RFC2668;RFC3636;Smith, A., Flick, J., de Graaf, K., Romascanu, D., McMaster, D., McCloghrie, K., and S. Roberts;Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs);;;;;RFC 2668;DOI 10.17487/RFC2668;August;https://www.rfc-editor.org/info/rfc2668 | |
| RFC2669;RFC4639;St. Johns, M., Ed.;DOCSIS Cable Device MIB Cable Device Management Information Base for DOCSIS compliant Cable Modems and Cable Modem Termination Systems;;;;;RFC 2669;DOI 10.17487/RFC2669;August;https://www.rfc-editor.org/info/rfc2669 | |
| RFC2670;RFC4546;St. Johns, M., Ed.;Radio Frequency (RF) Interface Management Information Base for MCNS/DOCSIS compliant RF interfaces;;;;;RFC 2670;DOI 10.17487/RFC2670;August;https://www.rfc-editor.org/info/rfc2670 | |
| RFC2671;RFC6891;Vixie, P.;Extension Mechanisms for DNS (EDNS0);;;;;RFC 2671;DOI 10.17487/RFC2671;August;https://www.rfc-editor.org/info/rfc2671 | |
| RFC2672;RFC6672;Crawford, M.;Non-Terminal DNS Name Redirection;;;;;RFC 2672;DOI 10.17487/RFC2672;August;https://www.rfc-editor.org/info/rfc2672 | |
| RFC2673;RFC6891;Crawford, M.;Binary Labels in the Domain Name System;;;;;RFC 2673;DOI 10.17487/RFC2673;August;https://www.rfc-editor.org/info/rfc2673 | |
| RFC2674;RFC4363;Bell, E., Smith, A., Langille, P., Rijhsinghani, A., and K. McCloghrie;Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions;;;;;RFC 2674;DOI 10.17487/RFC2674;August;https://www.rfc-editor.org/info/rfc2674 | |
| RFC2675;;Borman, D., Deering, S., and R. Hinden;IPv6 Jumbograms;;;;;RFC 2675;DOI 10.17487/RFC2675;August;https://www.rfc-editor.org/info/rfc2675 | |
| RFC2676;;Apostolopoulos, G., Kama, S., Williams, D., Guerin, R., Orda, A., and T. Przygienda;QoS Routing Mechanisms and OSPF Extensions;;;;;RFC 2676;DOI 10.17487/RFC2676;August;https://www.rfc-editor.org/info/rfc2676 | |
| RFC2677;;Greene, M., Cucchiara, J., and J. Luciani;Definitions of Managed Objects for the NBMA Next Hop Resolution Protocol (NHRP);;;;;RFC 2677;DOI 10.17487/RFC2677;August;https://www.rfc-editor.org/info/rfc2677 | |
| RFC2678;;Mahdavi, J. and V. Paxson;IPPM Metrics for Measuring Connectivity;;;;;RFC 2678;DOI 10.17487/RFC2678;September;https://www.rfc-editor.org/info/rfc2678 | |
| RFC2679;RFC7679;Almes, G., Kalidindi, S., and M. Zekauskas;A One-way Delay Metric for IPPM;;;;;RFC 2679;DOI 10.17487/RFC2679;September;https://www.rfc-editor.org/info/rfc2679 | |
| RFC2680;RFC7680;Almes, G., Kalidindi, S., and M. Zekauskas;A One-way Packet Loss Metric for IPPM;;;;;RFC 2680;DOI 10.17487/RFC2680;September;https://www.rfc-editor.org/info/rfc2680 | |
| RFC2681;;Almes, G., Kalidindi, S., and M. Zekauskas;A Round-trip Delay Metric for IPPM;;;;;RFC 2681;DOI 10.17487/RFC2681;September;https://www.rfc-editor.org/info/rfc2681 | |
| RFC2682;;Widjaja, I. and A. Elwalid;Performance Issues in VC-Merge Capable ATM LSRs;;;;;RFC 2682;DOI 10.17487/RFC2682;September;https://www.rfc-editor.org/info/rfc2682 | |
| RFC2683;;Leiba, B.;IMAP4 Implementation Recommendations;;;;;RFC 2683;DOI 10.17487/RFC2683;September;https://www.rfc-editor.org/info/rfc2683 | |
| RFC2684;;Grossman, D. and J. Heinanen;Multiprotocol Encapsulation over ATM Adaptation Layer 5;;;;;RFC 2684;DOI 10.17487/RFC2684;September;https://www.rfc-editor.org/info/rfc2684 | |
| RFC2685;;Fox, B. and B. Gleeson;Virtual Private Networks Identifier;;;;;RFC 2685;DOI 10.17487/RFC2685;September;https://www.rfc-editor.org/info/rfc2685 | |
| RFC2686;;Bormann, C.;The Multi-Class Extension to Multi-Link PPP;;;;;RFC 2686;DOI 10.17487/RFC2686;September;https://www.rfc-editor.org/info/rfc2686 | |
| RFC2687;;Bormann, C.;PPP in a Real-time Oriented HDLC-like Framing;;;;;RFC 2687;DOI 10.17487/RFC2687;September;https://www.rfc-editor.org/info/rfc2687 | |
| RFC2688;;Jackowski, S., Putzolu, D., Crawley, E., and B. Davie;Integrated Services Mappings for Low Speed Networks;;;;;RFC 2688;DOI 10.17487/RFC2688;September;https://www.rfc-editor.org/info/rfc2688 | |
| RFC2689;;Bormann, C.;Providing Integrated Services over Low-bitrate Links;;;;;RFC 2689;DOI 10.17487/RFC2689;September;https://www.rfc-editor.org/info/rfc2689 | |
| RFC2690;;Bradner, S.;A Proposal for an MOU-Based ICANN Protocol Support Organization;;;;;RFC 2690;DOI 10.17487/RFC2690;September;https://www.rfc-editor.org/info/rfc2690 | |
| RFC2691;;Bradner, S.;A Memorandum of Understanding for an ICANN Protocol Support Organization;;;;;RFC 2691;DOI 10.17487/RFC2691;September;https://www.rfc-editor.org/info/rfc2691 | |
| RFC2692;;Ellison, C.;SPKI Requirements;;;;;RFC 2692;DOI 10.17487/RFC2692;September;https://www.rfc-editor.org/info/rfc2692 | |
| RFC2693;;Ellison, C., Frantz, B., Lampson, B., Rivest, R., Thomas, B., and T. Ylonen;SPKI Certificate Theory;;;;;RFC 2693;DOI 10.17487/RFC2693;September;https://www.rfc-editor.org/info/rfc2693 | |
| RFC2694;;Srisuresh, P., Tsirtsis, G., Akkiraju, P., and A. Heffernan;DNS extensions to Network Address Translators (DNS_ALG);;;;;RFC 2694;DOI 10.17487/RFC2694;September;https://www.rfc-editor.org/info/rfc2694 | |
| RFC2695;;Chiu, A.;Authentication Mechanisms for ONC RPC;;;;;RFC 2695;DOI 10.17487/RFC2695;September;https://www.rfc-editor.org/info/rfc2695 | |
| RFC2696;;Weider, C., Herron, A., Anantha, A., and T. Howes;LDAP Control Extension for Simple Paged Results Manipulation;;;;;RFC 2696;DOI 10.17487/RFC2696;September;https://www.rfc-editor.org/info/rfc2696 | |
| RFC2697;;Heinanen, J. and R. Guerin;A Single Rate Three Color Marker;;;;;RFC 2697;DOI 10.17487/RFC2697;September;https://www.rfc-editor.org/info/rfc2697 | |
| RFC2698;;Heinanen, J. and R. Guerin;A Two Rate Three Color Marker;;;;;RFC 2698;DOI 10.17487/RFC2698;September;https://www.rfc-editor.org/info/rfc2698 | |
| RFC2699;;Ginoza, S.;Request for Comments Summary RFC Numbers 2600-2699;;;;;RFC 2699;DOI 10.17487/RFC2699;May;https://www.rfc-editor.org/info/rfc2699 | |
| RFC2700;RFC2800;Reynolds, J. and R. Braden;Internet Official Protocol Standards;;;;;RFC 2700;DOI 10.17487/RFC2700;August;https://www.rfc-editor.org/info/rfc2700 | |
| RFC2701;;Malkin, G.;Nortel Networks Multi-link Multi-node PPP Bundle Discovery Protocol;;;;;RFC 2701;DOI 10.17487/RFC2701;September;https://www.rfc-editor.org/info/rfc2701 | |
| RFC2702;;Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., and J. McManus;Requirements for Traffic Engineering Over MPLS;;;;;RFC 2702;DOI 10.17487/RFC2702;September;https://www.rfc-editor.org/info/rfc2702 | |
| RFC2703;;Klyne, G.;Protocol-independent Content Negotiation Framework;;;;;RFC 2703;DOI 10.17487/RFC2703;September;https://www.rfc-editor.org/info/rfc2703 | |
| RFC2704;;Blaze, M., Feigenbaum, J., Ioannidis, J., and A. Keromytis;The KeyNote Trust-Management System Version 2;;;;;RFC 2704;DOI 10.17487/RFC2704;September;https://www.rfc-editor.org/info/rfc2704 | |
| RFC2705;RFC3435;Arango, M., Dugan, A., Elliott, I., Huitema, C., and S. Pickett;Media Gateway Control Protocol (MGCP) Version 1.0;;;;;RFC 2705;DOI 10.17487/RFC2705;October;https://www.rfc-editor.org/info/rfc2705 | |
| RFC2706;RFC3106;Eastlake 3rd, D. and T. Goldstein;ECML v1: Field Names for E-Commerce;;;;;RFC 2706;DOI 10.17487/RFC2706;October;https://www.rfc-editor.org/info/rfc2706 | |
| RFC2707;;Bergman, R., Hastings, T., Isaacson, S., and H. Lewis;Job Monitoring MIB - V1.0;;;;;RFC 2707;DOI 10.17487/RFC2707;November;https://www.rfc-editor.org/info/rfc2707 | |
| RFC2708;;Bergman, R.;Job Submission Protocol Mapping Recommendations for the Job Monitoring MIB;;;;;RFC 2708;DOI 10.17487/RFC2708;November;https://www.rfc-editor.org/info/rfc2708 | |
| RFC2709;;Srisuresh, P.;Security Model with Tunnel-mode IPsec for NAT Domains;;;;;RFC 2709;DOI 10.17487/RFC2709;October;https://www.rfc-editor.org/info/rfc2709 | |
| RFC2710;;Deering, S., Fenner, W., and B. Haberman;Multicast Listener Discovery (MLD) for IPv6;;;;;RFC 2710;DOI 10.17487/RFC2710;October;https://www.rfc-editor.org/info/rfc2710 | |
| RFC2711;;Partridge, C. and A. Jackson;IPv6 Router Alert Option;;;;;RFC 2711;DOI 10.17487/RFC2711;October;https://www.rfc-editor.org/info/rfc2711 | |
| RFC2712;;Medvinsky, A. and M. Hur;Addition of Kerberos Cipher Suites to Transport Layer Security (TLS);;;;;RFC 2712;DOI 10.17487/RFC2712;October;https://www.rfc-editor.org/info/rfc2712 | |
| RFC2713;;Ryan, V., Seligman, S., and R. Lee;Schema for Representing Java(tm) Objects in an LDAP Directory;;;;;RFC 2713;DOI 10.17487/RFC2713;October;https://www.rfc-editor.org/info/rfc2713 | |
| RFC2714;;Ryan, V., Lee, R., and S. Seligman;Schema for Representing CORBA Object References in an LDAP Directory;;;;;RFC 2714;DOI 10.17487/RFC2714;October;https://www.rfc-editor.org/info/rfc2714 | |
| RFC2715;;Thaler, D.;Interoperability Rules for Multicast Routing Protocols;;;;;RFC 2715;DOI 10.17487/RFC2715;October;https://www.rfc-editor.org/info/rfc2715 | |
| RFC2716;RFC5216;Aboba, B. and D. Simon;PPP EAP TLS Authentication Protocol;;;;;RFC 2716;DOI 10.17487/RFC2716;October;https://www.rfc-editor.org/info/rfc2716 | |
| RFC2717;RFC4395;Petke, R. and I. King;Registration Procedures for URL Scheme Names;;;;;RFC 2717;DOI 10.17487/RFC2717;November;https://www.rfc-editor.org/info/rfc2717 | |
| RFC2718;RFC4395;Masinter, L., Alvestrand, H., Zigmond, D., and R. Petke;Guidelines for new URL Schemes;;;;;RFC 2718;DOI 10.17487/RFC2718;November;https://www.rfc-editor.org/info/rfc2718 | |
| RFC2719;;Ong, L., Rytina, I., Garcia, M., Schwarzbauer, H., Coene, L., Lin, H., Juhasz, I., Holdrege, M., and C. Sharp;Framework Architecture for Signaling Transport;;;;;RFC 2719;DOI 10.17487/RFC2719;October;https://www.rfc-editor.org/info/rfc2719 | |
| RFC2720;;Brownlee, N.;Traffic Flow Measurement: Meter MIB;;;;;RFC 2720;DOI 10.17487/RFC2720;October;https://www.rfc-editor.org/info/rfc2720 | |
| RFC2721;;Brownlee, N.;RTFM: Applicability Statement;;;;;RFC 2721;DOI 10.17487/RFC2721;October;https://www.rfc-editor.org/info/rfc2721 | |
| RFC2722;;Brownlee, N., Mills, C., and G. Ruth;Traffic Flow Measurement: Architecture;;;;;RFC 2722;DOI 10.17487/RFC2722;October;https://www.rfc-editor.org/info/rfc2722 | |
| RFC2723;;Brownlee, N.;SRL: A Language for Describing Traffic Flows and Specifying Actions for Flow Groups;;;;;RFC 2723;DOI 10.17487/RFC2723;October;https://www.rfc-editor.org/info/rfc2723 | |
| RFC2724;;Handelman, S., Stibler, S., Brownlee, N., and G. Ruth;RTFM: New Attributes for Traffic Flow Measurement;;;;;RFC 2724;DOI 10.17487/RFC2724;October;https://www.rfc-editor.org/info/rfc2724 | |
| RFC2725;;Villamizar, C., Alaettinoglu, C., Meyer, D., and S. Murphy;Routing Policy System Security;;;;;RFC 2725;DOI 10.17487/RFC2725;December;https://www.rfc-editor.org/info/rfc2725 | |
| RFC2726;;Zsako, J.;PGP Authentication for RIPE Database Updates;;;;;RFC 2726;DOI 10.17487/RFC2726;December;https://www.rfc-editor.org/info/rfc2726 | |
| RFC2727;RFC3777;Galvin, J.;IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees;;;;;RFC 2727;DOI 10.17487/RFC2727;February;https://www.rfc-editor.org/info/rfc2727 | |
| RFC2728;;Panabaker, R., Wegerif, S., and D. Zigmond;The Transmission of IP Over the Vertical Blanking Interval of a Television Signal;;;;;RFC 2728;DOI 10.17487/RFC2728;November;https://www.rfc-editor.org/info/rfc2728 | |
| RFC2729;;Bagnall, P., Briscoe, R., and A. Poppitt;Taxonomy of Communication Requirements for Large-scale Multicast Applications;;;;;RFC 2729;DOI 10.17487/RFC2729;December;https://www.rfc-editor.org/info/rfc2729 | |
| RFC2730;;Hanna, S., Patel, B., and M. Shah;Multicast Address Dynamic Client Allocation Protocol (MADCAP);;;;;RFC 2730;DOI 10.17487/RFC2730;December;https://www.rfc-editor.org/info/rfc2730 | |
| RFC2731;RFC5791;Kunze, J.;Encoding Dublin Core Metadata in HTML;;;;;RFC 2731;DOI 10.17487/RFC2731;December;https://www.rfc-editor.org/info/rfc2731 | |
| RFC2732;RFC3986;Hinden, R., Carpenter, B., and L. Masinter;Format for Literal IPv6 Addresses in URL's;;;;;RFC 2732;DOI 10.17487/RFC2732;December;https://www.rfc-editor.org/info/rfc2732 | |
| RFC2733;RFC5109;Rosenberg, J. and H. Schulzrinne;An RTP Payload Format for Generic Forward Error Correction;;;;;RFC 2733;DOI 10.17487/RFC2733;December;https://www.rfc-editor.org/info/rfc2733 | |
| RFC2734;;Johansson, P.;IPv4 over IEEE 1394;;;;;RFC 2734;DOI 10.17487/RFC2734;December;https://www.rfc-editor.org/info/rfc2734 | |
| RFC2735;;Fox, B. and B. Petri;NHRP Support for Virtual Private Networks;;;;;RFC 2735;DOI 10.17487/RFC2735;December;https://www.rfc-editor.org/info/rfc2735 | |
| RFC2736;;Handley, M. and C. Perkins;Guidelines for Writers of RTP Payload Format Specifications;;;BCP 36;;RFC 2736;DOI 10.17487/RFC2736;December;https://www.rfc-editor.org/info/rfc2736 | |
| RFC2737;RFC4133;McCloghrie, K. and A. Bierman;Entity MIB (Version 2);;;;;RFC 2737;DOI 10.17487/RFC2737;December;https://www.rfc-editor.org/info/rfc2737 | |
| RFC2738;;Klyne, G.;Corrections to "A Syntax for Describing Media Feature Sets";;;;;RFC 2738;DOI 10.17487/RFC2738;December;https://www.rfc-editor.org/info/rfc2738 | |
| RFC2739;;Small, T., Hennessy, D., and F. Dawson;Calendar Attributes for vCard and LDAP;;;;;RFC 2739;DOI 10.17487/RFC2739;January;https://www.rfc-editor.org/info/rfc2739 | |
| RFC2740;RFC5340;Coltun, R., Ferguson, D., and J. Moy;OSPF for IPv6;;;;;RFC 2740;DOI 10.17487/RFC2740;December;https://www.rfc-editor.org/info/rfc2740 | |
| RFC2741;;Daniele, M., Wijnen, B., Ellison, M., and D. Francisco;Agent Extensibility (AgentX) Protocol Version 1;;;;;RFC 2741;DOI 10.17487/RFC2741;January;https://www.rfc-editor.org/info/rfc2741 | |
| RFC2742;;Heintz, L., Gudur, S., and M. Ellison;Definitions of Managed Objects for Extensible SNMP Agents;;;;;RFC 2742;DOI 10.17487/RFC2742;January;https://www.rfc-editor.org/info/rfc2742 | |
| RFC2743;;Linn, J.;Generic Security Service Application Program Interface Version 2, Update 1;;;;;RFC 2743;DOI 10.17487/RFC2743;January;https://www.rfc-editor.org/info/rfc2743 | |
| RFC2744;;Wray, J.;Generic Security Service API Version 2 : C-bindings;;;;;RFC 2744;DOI 10.17487/RFC2744;January;https://www.rfc-editor.org/info/rfc2744 | |
| RFC2745;;Terzis, A., Braden, B., Vincent, S., and L. Zhang;RSVP Diagnostic Messages;;;;;RFC 2745;DOI 10.17487/RFC2745;January;https://www.rfc-editor.org/info/rfc2745 | |
| RFC2746;;Terzis, A., Krawczyk, J., Wroclawski, J., and L. Zhang;RSVP Operation Over IP Tunnels;;;;;RFC 2746;DOI 10.17487/RFC2746;January;https://www.rfc-editor.org/info/rfc2746 | |
| RFC2747;;Baker, F., Lindell, B., and M. Talwar;RSVP Cryptographic Authentication;;;;;RFC 2747;DOI 10.17487/RFC2747;January;https://www.rfc-editor.org/info/rfc2747 | |
| RFC2748;;Durham, D., Ed., Boyle, J., Cohen, R., Herzog, S., Rajan, R., and A. Sastry;The COPS (Common Open Policy Service) Protocol;;;;;RFC 2748;DOI 10.17487/RFC2748;January;https://www.rfc-editor.org/info/rfc2748 | |
| RFC2749;;Herzog, S., Ed., Boyle, J., Cohen, R., Durham, D., Rajan, R., and A. Sastry;COPS usage for RSVP;;;;;RFC 2749;DOI 10.17487/RFC2749;January;https://www.rfc-editor.org/info/rfc2749 | |
| RFC2750;;Herzog, S.;RSVP Extensions for Policy Control;;;;;RFC 2750;DOI 10.17487/RFC2750;January;https://www.rfc-editor.org/info/rfc2750 | |
| RFC2751;RFC3181;Herzog, S.;Signaled Preemption Priority Policy Element;;;;;RFC 2751;DOI 10.17487/RFC2751;January;https://www.rfc-editor.org/info/rfc2751 | |
| RFC2752;RFC3182;Yadav, S., Yavatkar, R., Pabbati, R., Ford, P., Moore, T., and S. Herzog;Identity Representation for RSVP;;;;;RFC 2752;DOI 10.17487/RFC2752;January;https://www.rfc-editor.org/info/rfc2752 | |
| RFC2753;;Yavatkar, R., Pendarakis, D., and R. Guerin;A Framework for Policy-based Admission Control;;;;;RFC 2753;DOI 10.17487/RFC2753;January;https://www.rfc-editor.org/info/rfc2753 | |
| RFC2754;RFC6254;Alaettinoglu, C., Villamizar, C., and R. Govindan;RPS IANA Issues;;;;;RFC 2754;DOI 10.17487/RFC2754;January;https://www.rfc-editor.org/info/rfc2754 | |
| RFC2755;;Chiu, A., Eisler, M., and B. Callaghan;Security Negotiation for WebNFS;;;;;RFC 2755;DOI 10.17487/RFC2755;January;https://www.rfc-editor.org/info/rfc2755 | |
| RFC2756;;Vixie, P. and D. Wessels;Hyper Text Caching Protocol (HTCP/0.0);;;;;RFC 2756;DOI 10.17487/RFC2756;January;https://www.rfc-editor.org/info/rfc2756 | |
| RFC2757;;Montenegro, G., Dawkins, S., Kojo, M., Magret, V., and N. Vaidya;Long Thin Networks;;;;;RFC 2757;DOI 10.17487/RFC2757;January;https://www.rfc-editor.org/info/rfc2757 | |
| RFC2758;;White, K.;Definitions of Managed Objects for Service Level Agreements Performance Monitoring;;;;;RFC 2758;DOI 10.17487/RFC2758;February;https://www.rfc-editor.org/info/rfc2758 | |
| RFC2759;;Zorn, G.;Microsoft PPP CHAP Extensions, Version 2;;;;;RFC 2759;DOI 10.17487/RFC2759;January;https://www.rfc-editor.org/info/rfc2759 | |
| RFC2760;;Allman, M., Ed., Dawkins, S., Glover, D., Griner, J., Tran, D., Henderson, T., Heidemann, J., Touch, J., Kruse, H., Ostermann, S., Scott, K., and J. Semke;Ongoing TCP Research Related to Satellites;;;;;RFC 2760;DOI 10.17487/RFC2760;February;https://www.rfc-editor.org/info/rfc2760 | |
| RFC2761;;Dunn, J. and C. Martin;Terminology for ATM Benchmarking;;;;;RFC 2761;DOI 10.17487/RFC2761;February;https://www.rfc-editor.org/info/rfc2761 | |
| RFC2762;;Rosenberg, J. and H. Schulzrinne;Sampling of the Group Membership in RTP;;;;;RFC 2762;DOI 10.17487/RFC2762;February;https://www.rfc-editor.org/info/rfc2762 | |
| RFC2763;RFC5301;Shen, N. and H. Smit;Dynamic Hostname Exchange Mechanism for IS-IS;;;;;RFC 2763;DOI 10.17487/RFC2763;February;https://www.rfc-editor.org/info/rfc2763 | |
| RFC2764;;Gleeson, B., Lin, A., Heinanen, J., Armitage, G., and A. Malis;A Framework for IP Based Virtual Private Networks;;;;;RFC 2764;DOI 10.17487/RFC2764;February;https://www.rfc-editor.org/info/rfc2764 | |
| RFC2765;RFC6145;Nordmark, E.;Stateless IP/ICMP Translation Algorithm (SIIT);;;;;RFC 2765;DOI 10.17487/RFC2765;February;https://www.rfc-editor.org/info/rfc2765 | |
| RFC2766;RFC4966;Tsirtsis, G. and P. Srisuresh;Network Address Translation - Protocol Translation (NAT-PT);;;;;RFC 2766;DOI 10.17487/RFC2766;February;https://www.rfc-editor.org/info/rfc2766 | |
| RFC2767;RFC6535;Tsuchiya, K., Higuchi, H., and Y. Atarashi;Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS);;;;;RFC 2767;DOI 10.17487/RFC2767;February;https://www.rfc-editor.org/info/rfc2767 | |
| RFC2768;;Aiken, B., Strassner, J., Carpenter, B., Foster, I., Lynch, C., Mambretti, J., Moore, R., and B. Teitelbaum;Network Policy and Services: A Report of a Workshop on Middleware;;;;;RFC 2768;DOI 10.17487/RFC2768;February;https://www.rfc-editor.org/info/rfc2768 | |
| RFC2769;;Villamizar, C., Alaettinoglu, C., Govindan, R., and D. Meyer;Routing Policy System Replication;;;;;RFC 2769;DOI 10.17487/RFC2769;February;https://www.rfc-editor.org/info/rfc2769 | |
| RFC2770;RFC3180;Meyer, D. and P. Lothberg;GLOP Addressing in 233/8;;;;;RFC 2770;DOI 10.17487/RFC2770;February;https://www.rfc-editor.org/info/rfc2770 | |
| RFC2771;;Finlayson, R.;An Abstract API for Multicast Address Allocation;;;;;RFC 2771;DOI 10.17487/RFC2771;February;https://www.rfc-editor.org/info/rfc2771 | |
| RFC2772;;Rockell, R. and R. Fink;6Bone Backbone Routing Guidelines;;;;;RFC 2772;DOI 10.17487/RFC2772;February;https://www.rfc-editor.org/info/rfc2772 | |
| RFC2773;;Housley, R., Yee, P., and W. Nace;Encryption using KEA and SKIPJACK;;;;;RFC 2773;DOI 10.17487/RFC2773;February;https://www.rfc-editor.org/info/rfc2773 | |
| RFC2774;;Nielsen, H., Leach, P., and S. Lawrence;An HTTP Extension Framework;;;;;RFC 2774;DOI 10.17487/RFC2774;February;https://www.rfc-editor.org/info/rfc2774 | |
| RFC2775;;Carpenter, B.;Internet Transparency;;;;;RFC 2775;DOI 10.17487/RFC2775;February;https://www.rfc-editor.org/info/rfc2775 | |
| RFC2776;;Handley, M., Thaler, D., and R. Kermode;Multicast-Scope Zone Announcement Protocol (MZAP);;;;;RFC 2776;DOI 10.17487/RFC2776;February;https://www.rfc-editor.org/info/rfc2776 | |
| RFC2777;RFC3797;Eastlake 3rd, D.;Publicly Verifiable Nomcom Random Selection;;;;;RFC 2777;DOI 10.17487/RFC2777;February;https://www.rfc-editor.org/info/rfc2777 | |
| RFC2778;;Day, M., Rosenberg, J., and H. Sugano;A Model for Presence and Instant Messaging;;;;;RFC 2778;DOI 10.17487/RFC2778;February;https://www.rfc-editor.org/info/rfc2778 | |
| RFC2779;;Day, M., Aggarwal, S., Mohr, G., and J. Vincent;Instant Messaging / Presence Protocol Requirements;;;;;RFC 2779;DOI 10.17487/RFC2779;February;https://www.rfc-editor.org/info/rfc2779 | |
| RFC2780;;Bradner, S. and V. Paxson;IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers;;;BCP 37;;RFC 2780;DOI 10.17487/RFC2780;March;https://www.rfc-editor.org/info/rfc2780 | |
| RFC2781;;Hoffman, P. and F. Yergeau;UTF-16, an encoding of ISO 10646;;;;;RFC 2781;DOI 10.17487/RFC2781;February;https://www.rfc-editor.org/info/rfc2781 | |
| RFC2782;;Gulbrandsen, A., Vixie, P., and L. Esibov;A DNS RR for specifying the location of services (DNS SRV);;;;;RFC 2782;DOI 10.17487/RFC2782;February;https://www.rfc-editor.org/info/rfc2782 | |
| RFC2783;;Mogul, J., Mills, D., Brittenson, J., Stone, J., and U. Windl;Pulse-Per-Second API for UNIX-like Operating Systems, Version 1.0;;;;;RFC 2783;DOI 10.17487/RFC2783;March;https://www.rfc-editor.org/info/rfc2783 | |
| RFC2784;;Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. Traina;Generic Routing Encapsulation (GRE);;;;;RFC 2784;DOI 10.17487/RFC2784;March;https://www.rfc-editor.org/info/rfc2784 | |
| RFC2785;;Zuccherato, R.;Methods for Avoiding the "Small-Subgroup" Attacks on the Diffie-Hellman Key Agreement Method for S/MIME;;;;;RFC 2785;DOI 10.17487/RFC2785;March;https://www.rfc-editor.org/info/rfc2785 | |
| RFC2786;;St. Johns, M.;Diffie-Helman USM Key Management Information Base and Textual Convention;;;;;RFC 2786;DOI 10.17487/RFC2786;March;https://www.rfc-editor.org/info/rfc2786 | |
| RFC2787;RFC6527;Jewell, B. and D. Chuang;Definitions of Managed Objects for the Virtual Router Redundancy Protocol;;;;;RFC 2787;DOI 10.17487/RFC2787;March;https://www.rfc-editor.org/info/rfc2787 | |
| RFC2788;;Freed, N. and S. Kille;Network Services Monitoring MIB;;;;;RFC 2788;DOI 10.17487/RFC2788;March;https://www.rfc-editor.org/info/rfc2788 | |
| RFC2789;;Freed, N. and S. Kille;Mail Monitoring MIB;;;;;RFC 2789;DOI 10.17487/RFC2789;March;https://www.rfc-editor.org/info/rfc2789 | |
| RFC2790;;Waldbusser, S. and P. Grillo;Host Resources MIB;;;;;RFC 2790;DOI 10.17487/RFC2790;March;https://www.rfc-editor.org/info/rfc2790 | |
| RFC2791;;Yu, J.;Scalable Routing Design Principles;;;;;RFC 2791;DOI 10.17487/RFC2791;July;https://www.rfc-editor.org/info/rfc2791 | |
| RFC2792;;Blaze, M., Ioannidis, J., and A. Keromytis;DSA and RSA Key and Signature Encoding for the KeyNote Trust Management System;;;;;RFC 2792;DOI 10.17487/RFC2792;March;https://www.rfc-editor.org/info/rfc2792 | |
| RFC2793;RFC4103;Hellstrom, G.;RTP Payload for Text Conversation;;;;;RFC 2793;DOI 10.17487/RFC2793;May;https://www.rfc-editor.org/info/rfc2793 | |
| RFC2794;;Calhoun, P. and C. Perkins;Mobile IP Network Access Identifier Extension for IPv4;;;;;RFC 2794;DOI 10.17487/RFC2794;March;https://www.rfc-editor.org/info/rfc2794 | |
| RFC2795;;Christey, S.;The Infinite Monkey Protocol Suite (IMPS);;;;;RFC 2795;DOI 10.17487/RFC2795;April;https://www.rfc-editor.org/info/rfc2795 | |
| RFC2796;RFC4456;Bates, T., Chandra, R., and E. Chen;BGP Route Reflection - An Alternative to Full Mesh IBGP;;;;;RFC 2796;DOI 10.17487/RFC2796;April;https://www.rfc-editor.org/info/rfc2796 | |
| RFC2797;RFC5272;Myers, M., Liu, X., Schaad, J., and J. Weinstein;Certificate Management Messages over CMS;;;;;RFC 2797;DOI 10.17487/RFC2797;April;https://www.rfc-editor.org/info/rfc2797 | |
| RFC2798;;Smith, M.;Definition of the inetOrgPerson LDAP Object Class;;;;;RFC 2798;DOI 10.17487/RFC2798;April;https://www.rfc-editor.org/info/rfc2798 | |
| RFC2799;;Ginoza, S.;Request for Comments Summary RFC Numbers 2700-2799;;;;;RFC 2799;DOI 10.17487/RFC2799;September;https://www.rfc-editor.org/info/rfc2799 | |
| RFC2800;RFC2900;Reynolds, J., Braden, R., and S. Ginoza;Internet Official Protocol Standards;;;;;RFC 2800;DOI 10.17487/RFC2800;May;https://www.rfc-editor.org/info/rfc2800 | |
| RFC2801;;Burdett, D.;Internet Open Trading Protocol - IOTP Version 1.0;;;;;RFC 2801;DOI 10.17487/RFC2801;April;https://www.rfc-editor.org/info/rfc2801 | |
| RFC2802;;Davidson, K. and Y. Kawatsura;Digital Signatures for the v1.0 Internet Open Trading Protocol (IOTP);;;;;RFC 2802;DOI 10.17487/RFC2802;April;https://www.rfc-editor.org/info/rfc2802 | |
| RFC2803;;Maruyama, H., Tamura, K., and N. Uramoto;Digest Values for DOM (DOMHASH);;;;;RFC 2803;DOI 10.17487/RFC2803;April;https://www.rfc-editor.org/info/rfc2803 | |
| RFC2804;;IAB and IESG;IETF Policy on Wiretapping;;;;;RFC 2804;DOI 10.17487/RFC2804;May;https://www.rfc-editor.org/info/rfc2804 | |
| RFC2805;;Greene, N., Ramalho, M., and B. Rosen;Media Gateway Control Protocol Architecture and Requirements;;;;;RFC 2805;DOI 10.17487/RFC2805;April;https://www.rfc-editor.org/info/rfc2805 | |
| RFC2806;RFC3966;Vaha-Sipila, A.;URLs for Telephone Calls;;;;;RFC 2806;DOI 10.17487/RFC2806;April;https://www.rfc-editor.org/info/rfc2806 | |
| RFC2807;;Reagle, J.;XML Signature Requirements;;;;;RFC 2807;DOI 10.17487/RFC2807;July;https://www.rfc-editor.org/info/rfc2807 | |
| RFC2808;;Nystrom, M.;The SecurID(r) SASL Mechanism;;;;;RFC 2808;DOI 10.17487/RFC2808;April;https://www.rfc-editor.org/info/rfc2808 | |
| RFC2809;;Aboba, B. and G. Zorn;Implementation of L2TP Compulsory Tunneling via RADIUS;;;;;RFC 2809;DOI 10.17487/RFC2809;April;https://www.rfc-editor.org/info/rfc2809 | |
| RFC2810;;Kalt, C.;Internet Relay Chat: Architecture;;;;;RFC 2810;DOI 10.17487/RFC2810;April;https://www.rfc-editor.org/info/rfc2810 | |
| RFC2811;;Kalt, C.;Internet Relay Chat: Channel Management;;;;;RFC 2811;DOI 10.17487/RFC2811;April;https://www.rfc-editor.org/info/rfc2811 | |
| RFC2812;;Kalt, C.;Internet Relay Chat: Client Protocol;;;;;RFC 2812;DOI 10.17487/RFC2812;April;https://www.rfc-editor.org/info/rfc2812 | |
| RFC2813;;Kalt, C.;Internet Relay Chat: Server Protocol;;;;;RFC 2813;DOI 10.17487/RFC2813;April;https://www.rfc-editor.org/info/rfc2813 | |
| RFC2814;;Yavatkar, R., Hoffman, D., Bernet, Y., Baker, F., and M. Speer;SBM (Subnet Bandwidth Manager): A Protocol for RSVP-based Admission Control over IEEE 802-style networks;;;;;RFC 2814;DOI 10.17487/RFC2814;May;https://www.rfc-editor.org/info/rfc2814 | |
| RFC2815;;Seaman, M., Smith, A., Crawley, E., and J. Wroclawski;Integrated Service Mappings on IEEE 802 Networks;;;;;RFC 2815;DOI 10.17487/RFC2815;May;https://www.rfc-editor.org/info/rfc2815 | |
| RFC2816;;Ghanwani, A., Pace, J., Srinivasan, V., Smith, A., and M. Seaman;A Framework for Integrated Services Over Shared and Switched IEEE 802 LAN Technologies;;;;;RFC 2816;DOI 10.17487/RFC2816;May;https://www.rfc-editor.org/info/rfc2816 | |
| RFC2817;;Khare, R. and S. Lawrence;Upgrading to TLS Within HTTP/1.1;;;;;RFC 2817;DOI 10.17487/RFC2817;May;https://www.rfc-editor.org/info/rfc2817 | |
| RFC2818;;Rescorla, E.;HTTP Over TLS;;;;;RFC 2818;DOI 10.17487/RFC2818;May;https://www.rfc-editor.org/info/rfc2818 | |
| RFC2819;;Waldbusser, S.;Remote Network Monitoring Management Information Base;;;;STD 59;RFC 2819;DOI 10.17487/RFC2819;May;https://www.rfc-editor.org/info/rfc2819 | |
| RFC2820;;Stokes, E., Byrne, D., Blakley, B., and P. Behera;Access Control Requirements for LDAP;;;;;RFC 2820;DOI 10.17487/RFC2820;May;https://www.rfc-editor.org/info/rfc2820 | |
| RFC2821;RFC5321;Klensin, J., Ed.;Simple Mail Transfer Protocol;;;;;RFC 2821;DOI 10.17487/RFC2821;April;https://www.rfc-editor.org/info/rfc2821 | |
| RFC2822;RFC5322;Resnick, P., Ed.;Internet Message Format;;;;;RFC 2822;DOI 10.17487/RFC2822;April;https://www.rfc-editor.org/info/rfc2822 | |
| RFC2823;;Carlson, J., Langner, P., Hernandez-Valencia, E., and J. Manchester;PPP over Simple Data Link (SDL) using SONET/SDH with ATM-like framing;;;;;RFC 2823;DOI 10.17487/RFC2823;May;https://www.rfc-editor.org/info/rfc2823 | |
| RFC2824;;Lennox, J. and H. Schulzrinne;Call Processing Language Framework and Requirements;;;;;RFC 2824;DOI 10.17487/RFC2824;May;https://www.rfc-editor.org/info/rfc2824 | |
| RFC2825;;IAB and L. Daigle, Ed.;A Tangled Web: Issues of I18N, Domain Names, and the Other Internet protocols;;;;;RFC 2825;DOI 10.17487/RFC2825;May;https://www.rfc-editor.org/info/rfc2825 | |
| RFC2826;;Internet Architecture Board;IAB Technical Comment on the Unique DNS Root;;;;;RFC 2826;DOI 10.17487/RFC2826;May;https://www.rfc-editor.org/info/rfc2826 | |
| RFC2827;;Ferguson, P. and D. Senie;Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing;;;BCP 38;;RFC 2827;DOI 10.17487/RFC2827;May;https://www.rfc-editor.org/info/rfc2827 | |
| RFC2828;RFC4949;Shirey, R.;Internet Security Glossary;;;;;RFC 2828;DOI 10.17487/RFC2828;May;https://www.rfc-editor.org/info/rfc2828 | |
| RFC2829;RFC4513, RFC4510;Wahl, M., Alvestrand, H., Hodges, J., and R. Morgan;Authentication Methods for LDAP;;;;;RFC 2829;DOI 10.17487/RFC2829;May;https://www.rfc-editor.org/info/rfc2829 | |
| RFC2830;RFC4511, RFC4513, RFC4510;Hodges, J., Morgan, R., and M. Wahl;Lightweight Directory Access Protocol (v3): Extension for Transport Layer Security;;;;;RFC 2830;DOI 10.17487/RFC2830;May;https://www.rfc-editor.org/info/rfc2830 | |
| RFC2831;RFC6331;Leach, P. and C. Newman;Using Digest Authentication as a SASL Mechanism;;;;;RFC 2831;DOI 10.17487/RFC2831;May;https://www.rfc-editor.org/info/rfc2831 | |
| RFC2832;;Hollenbeck, S. and M. Srivastava;NSI Registry Registrar Protocol (RRP) Version 1.1.0;;;;;RFC 2832;DOI 10.17487/RFC2832;May;https://www.rfc-editor.org/info/rfc2832 | |
| RFC2833;RFC4733, RFC4734;Schulzrinne, H. and S. Petrack;RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals;;;;;RFC 2833;DOI 10.17487/RFC2833;May;https://www.rfc-editor.org/info/rfc2833 | |
| RFC2834;;Pittet, J.-M.;ARP and IP Broadcast over HIPPI-800;;;;;RFC 2834;DOI 10.17487/RFC2834;May;https://www.rfc-editor.org/info/rfc2834 | |
| RFC2835;;Pittet, J.-M.;IP and ARP over HIPPI-6400 (GSN);;;;;RFC 2835;DOI 10.17487/RFC2835;May;https://www.rfc-editor.org/info/rfc2835 | |
| RFC2836;RFC3140;Brim, S., Carpenter, B., and F. Le Faucheur;Per Hop Behavior Identification Codes;;;;;RFC 2836;DOI 10.17487/RFC2836;May;https://www.rfc-editor.org/info/rfc2836 | |
| RFC2837;RFC4044;Teow, K.;Definitions of Managed Objects for the Fabric Element in Fibre Channel Standard;;;;;RFC 2837;DOI 10.17487/RFC2837;May;https://www.rfc-editor.org/info/rfc2837 | |
| RFC2838;;Zigmond, D. and M. Vickers;Uniform Resource Identifiers for Television Broadcasts;;;;;RFC 2838;DOI 10.17487/RFC2838;May;https://www.rfc-editor.org/info/rfc2838 | |
| RFC2839;;da Cruz, F. and J. Altman;Internet Kermit Service;;;;;RFC 2839;DOI 10.17487/RFC2839;May;https://www.rfc-editor.org/info/rfc2839 | |
| RFC2840;;Altman, J. and F. da Cruz;TELNET KERMIT OPTION;;;;;RFC 2840;DOI 10.17487/RFC2840;May;https://www.rfc-editor.org/info/rfc2840 | |
| RFC2841;;Metzger, P. and W. Simpson;IP Authentication using Keyed SHA1 with Interleaved Padding (IP-MAC);;;;;RFC 2841;DOI 10.17487/RFC2841;November;https://www.rfc-editor.org/info/rfc2841 | |
| RFC2842;RFC3392;Chandra, R. and J. Scudder;Capabilities Advertisement with BGP-4;;;;;RFC 2842;DOI 10.17487/RFC2842;May;https://www.rfc-editor.org/info/rfc2842 | |
| RFC2843;;Droz, P. and T. Przygienda;Proxy-PAR;;;;;RFC 2843;DOI 10.17487/RFC2843;May;https://www.rfc-editor.org/info/rfc2843 | |
| RFC2844;;Przygienda, T., Droz, P., and R. Haas;OSPF over ATM and Proxy-PAR;;;;;RFC 2844;DOI 10.17487/RFC2844;May;https://www.rfc-editor.org/info/rfc2844 | |
| RFC2845;;Vixie, P., Gudmundsson, O., Eastlake 3rd, D., and B. Wellington;Secret Key Transaction Authentication for DNS (TSIG);;;;;RFC 2845;DOI 10.17487/RFC2845;May;https://www.rfc-editor.org/info/rfc2845 | |
| RFC2846;;Allocchio, C.;GSTN Address Element Extensions in E-mail Services;;;;;RFC 2846;DOI 10.17487/RFC2846;June;https://www.rfc-editor.org/info/rfc2846 | |
| RFC2847;;Eisler, M.;LIPKEY - A Low Infrastructure Public Key Mechanism Using SPKM;;;;;RFC 2847;DOI 10.17487/RFC2847;June;https://www.rfc-editor.org/info/rfc2847 | |
| RFC2848;;Petrack, S. and L. Conroy;The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call Services;;;;;RFC 2848;DOI 10.17487/RFC2848;June;https://www.rfc-editor.org/info/rfc2848 | |
| RFC2849;;Good, G.;The LDAP Data Interchange Format (LDIF) - Technical Specification;;;;;RFC 2849;DOI 10.17487/RFC2849;June;https://www.rfc-editor.org/info/rfc2849 | |
| RFC2850;;Internet Architecture Board and B. Carpenter, Ed.;Charter of the Internet Architecture Board (IAB);;;BCP 39;;RFC 2850;DOI 10.17487/RFC2850;May;https://www.rfc-editor.org/info/rfc2850 | |
| RFC2851;RFC3291;Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder;Textual Conventions for Internet Network Addresses;;;;;RFC 2851;DOI 10.17487/RFC2851;June;https://www.rfc-editor.org/info/rfc2851 | |
| RFC2852;;Newman, D.;Deliver By SMTP Service Extension;;;;;RFC 2852;DOI 10.17487/RFC2852;June;https://www.rfc-editor.org/info/rfc2852 | |
| RFC2853;RFC5653;Kabat, J. and M. Upadhyay;Generic Security Service API Version 2 : Java Bindings;;;;;RFC 2853;DOI 10.17487/RFC2853;June;https://www.rfc-editor.org/info/rfc2853 | |
| RFC2854;;Connolly, D. and L. Masinter;The 'text/html' Media Type;;;;;RFC 2854;DOI 10.17487/RFC2854;June;https://www.rfc-editor.org/info/rfc2854 | |
| RFC2855;;Fujisawa, K.;DHCP for IEEE 1394;;;;;RFC 2855;DOI 10.17487/RFC2855;June;https://www.rfc-editor.org/info/rfc2855 | |
| RFC2856;;Bierman, A., McCloghrie, K., and R. Presuhn;Textual Conventions for Additional High Capacity Data Types;;;;;RFC 2856;DOI 10.17487/RFC2856;June;https://www.rfc-editor.org/info/rfc2856 | |
| RFC2857;;Keromytis, A. and N. Provos;The Use of HMAC-RIPEMD-160-96 within ESP and AH;;;;;RFC 2857;DOI 10.17487/RFC2857;June;https://www.rfc-editor.org/info/rfc2857 | |
| RFC2858;RFC4760;Bates, T., Rekhter, Y., Chandra, R., and D. Katz;Multiprotocol Extensions for BGP-4;;;;;RFC 2858;DOI 10.17487/RFC2858;June;https://www.rfc-editor.org/info/rfc2858 | |
| RFC2859;;Fang, W., Seddigh, N., and B. Nandy;A Time Sliding Window Three Colour Marker (TSWTCM);;;;;RFC 2859;DOI 10.17487/RFC2859;June;https://www.rfc-editor.org/info/rfc2859 | |
| RFC2860;;Carpenter, B., Baker, F., and M. Roberts;Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority;;;;;RFC 2860;DOI 10.17487/RFC2860;June;https://www.rfc-editor.org/info/rfc2860 | |
| RFC2861;RFC7661;Handley, M., Padhye, J., and S. Floyd;TCP Congestion Window Validation;;;;;RFC 2861;DOI 10.17487/RFC2861;June;https://www.rfc-editor.org/info/rfc2861 | |
| RFC2862;;Civanlar, M. and G. Cash;RTP Payload Format for Real-Time Pointers;;;;;RFC 2862;DOI 10.17487/RFC2862;June;https://www.rfc-editor.org/info/rfc2862 | |
| RFC2863;;McCloghrie, K. and F. Kastenholz;The Interfaces Group MIB;;;;;RFC 2863;DOI 10.17487/RFC2863;June;https://www.rfc-editor.org/info/rfc2863 | |
| RFC2864;;McCloghrie, K. and G. Hanson;The Inverted Stack Table Extension to the Interfaces Group MIB;;;;;RFC 2864;DOI 10.17487/RFC2864;June;https://www.rfc-editor.org/info/rfc2864 | |
| RFC2865;;Rigney, C., Willens, S., Rubens, A., and W. Simpson;Remote Authentication Dial In User Service (RADIUS);;;;;RFC 2865;DOI 10.17487/RFC2865;June;https://www.rfc-editor.org/info/rfc2865 | |
| RFC2866;;Rigney, C.;RADIUS Accounting;;;;;RFC 2866;DOI 10.17487/RFC2866;June;https://www.rfc-editor.org/info/rfc2866 | |
| RFC2867;;Zorn, G., Aboba, B., and D. Mitton;RADIUS Accounting Modifications for Tunnel Protocol Support;;;;;RFC 2867;DOI 10.17487/RFC2867;June;https://www.rfc-editor.org/info/rfc2867 | |
| RFC2868;;Zorn, G., Leifer, D., Rubens, A., Shriver, J., Holdrege, M., and I. Goyret;RADIUS Attributes for Tunnel Protocol Support;;;;;RFC 2868;DOI 10.17487/RFC2868;June;https://www.rfc-editor.org/info/rfc2868 | |
| RFC2869;;Rigney, C., Willats, W., and P. Calhoun;RADIUS Extensions;;;;;RFC 2869;DOI 10.17487/RFC2869;June;https://www.rfc-editor.org/info/rfc2869 | |
| RFC2870;RFC7720;Bush, R., Karrenberg, D., Kosters, M., and R. Plzak;Root Name Server Operational Requirements;;;;;RFC 2870;DOI 10.17487/RFC2870;June;https://www.rfc-editor.org/info/rfc2870 | |
| RFC2871;;Rosenberg, J. and H. Schulzrinne;A Framework for Telephony Routing over IP;;;;;RFC 2871;DOI 10.17487/RFC2871;June;https://www.rfc-editor.org/info/rfc2871 | |
| RFC2872;;Bernet, Y. and R. Pabbati;Application and Sub Application Identity Policy Element for Use with RSVP;;;;;RFC 2872;DOI 10.17487/RFC2872;June;https://www.rfc-editor.org/info/rfc2872 | |
| RFC2873;;Xiao, X., Hannan, A., Paxson, V., and E. Crabbe;TCP Processing of the IPv4 Precedence Field;;;;;RFC 2873;DOI 10.17487/RFC2873;June;https://www.rfc-editor.org/info/rfc2873 | |
| RFC2874;;Crawford, M. and C. Huitema;DNS Extensions to Support IPv6 Address Aggregation and Renumbering;;;;;RFC 2874;DOI 10.17487/RFC2874;July;https://www.rfc-editor.org/info/rfc2874 | |
| RFC2875;RFC6955;Prafullchandra, H. and J. Schaad;Diffie-Hellman Proof-of-Possession Algorithms;;;;;RFC 2875;DOI 10.17487/RFC2875;July;https://www.rfc-editor.org/info/rfc2875 | |
| RFC2876;;Pawling, J.;Use of the KEA and SKIPJACK Algorithms in CMS;;;;;RFC 2876;DOI 10.17487/RFC2876;July;https://www.rfc-editor.org/info/rfc2876 | |
| RFC2877;RFC4777;Murphy Jr., T., Rieth, P., and J. Stevens;5250 Telnet Enhancements;;;;;RFC 2877;DOI 10.17487/RFC2877;July;https://www.rfc-editor.org/info/rfc2877 | |
| RFC2878;RFC3518;Higashiyama, M. and F. Baker;PPP Bridging Control Protocol (BCP);;;;;RFC 2878;DOI 10.17487/RFC2878;July;https://www.rfc-editor.org/info/rfc2878 | |
| RFC2879;;Klyne, G. and L. McIntyre;Content Feature Schema for Internet Fax (V2);;;;;RFC 2879;DOI 10.17487/RFC2879;August;https://www.rfc-editor.org/info/rfc2879 | |
| RFC2880;;McIntyre, L. and G. Klyne;Internet Fax T.30 Feature Mapping;;;;;RFC 2880;DOI 10.17487/RFC2880;August;https://www.rfc-editor.org/info/rfc2880 | |
| RFC2881;;Mitton, D. and M. Beadles;Network Access Server Requirements Next Generation (NASREQNG) NAS Model;;;;;RFC 2881;DOI 10.17487/RFC2881;July;https://www.rfc-editor.org/info/rfc2881 | |
| RFC2882;;Mitton, D.;Network Access Servers Requirements: Extended RADIUS Practices;;;;;RFC 2882;DOI 10.17487/RFC2882;July;https://www.rfc-editor.org/info/rfc2882 | |
| RFC2883;;Floyd, S., Mahdavi, J., Mathis, M., and M. Podolsky;An Extension to the Selective Acknowledgement (SACK) Option for TCP;;;;;RFC 2883;DOI 10.17487/RFC2883;July;https://www.rfc-editor.org/info/rfc2883 | |
| RFC2884;;Hadi Salim, J. and U. Ahmed;Performance Evaluation of Explicit Congestion Notification (ECN) in IP Networks;;;;;RFC 2884;DOI 10.17487/RFC2884;July;https://www.rfc-editor.org/info/rfc2884 | |
| RFC2885;RFC3015;Cuervo, F., Greene, N., Huitema, C., Rayhan, A., Rosen, B., and J. Segers;Megaco Protocol version 0.8;;;;;RFC 2885;DOI 10.17487/RFC2885;August;https://www.rfc-editor.org/info/rfc2885 | |
| RFC2886;RFC3015;Taylor, T.;Megaco Errata;;;;;RFC 2886;DOI 10.17487/RFC2886;August;https://www.rfc-editor.org/info/rfc2886 | |
| RFC2887;;Handley, M., Floyd, S., Whetten, B., Kermode, R., Vicisano, L., and M. Luby;The Reliable Multicast Design Space for Bulk Data Transfer;;;;;RFC 2887;DOI 10.17487/RFC2887;August;https://www.rfc-editor.org/info/rfc2887 | |
| RFC2888;;Srisuresh, P.;Secure Remote Access with L2TP;;;;;RFC 2888;DOI 10.17487/RFC2888;August;https://www.rfc-editor.org/info/rfc2888 | |
| RFC2889;;Mandeville, R. and J. Perser;Benchmarking Methodology for LAN Switching Devices;;;;;RFC 2889;DOI 10.17487/RFC2889;August;https://www.rfc-editor.org/info/rfc2889 | |
| RFC2890;;Dommety, G.;Key and Sequence Number Extensions to GRE;;;;;RFC 2890;DOI 10.17487/RFC2890;September;https://www.rfc-editor.org/info/rfc2890 | |
| RFC2891;;Howes, T., Wahl, M., and A. Anantha;LDAP Control Extension for Server Side Sorting of Search Results;;;;;RFC 2891;DOI 10.17487/RFC2891;August;https://www.rfc-editor.org/info/rfc2891 | |
| RFC2892;;Tsiang, D. and G. Suwala;The Cisco SRP MAC Layer Protocol;;;;;RFC 2892;DOI 10.17487/RFC2892;August;https://www.rfc-editor.org/info/rfc2892 | |
| RFC2893;RFC4213;Gilligan, R. and E. Nordmark;Transition Mechanisms for IPv6 Hosts and Routers;;;;;RFC 2893;DOI 10.17487/RFC2893;August;https://www.rfc-editor.org/info/rfc2893 | |
| RFC2894;;Crawford, M.;Router Renumbering for IPv6;;;;;RFC 2894;DOI 10.17487/RFC2894;August;https://www.rfc-editor.org/info/rfc2894 | |
| RFC2895;;Bierman, A., Bucci, C., and R. Iddon;Remote Network Monitoring MIB Protocol Identifier Reference;;;;;RFC 2895;DOI 10.17487/RFC2895;August;https://www.rfc-editor.org/info/rfc2895 | |
| RFC2896;;Bierman, A., Bucci, C., and R. Iddon;Remote Network Monitoring MIB Protocol Identifier Macros;;;;;RFC 2896;DOI 10.17487/RFC2896;August;https://www.rfc-editor.org/info/rfc2896 | |
| RFC2897;;Cromwell, D.;Proposal for an MGCP Advanced Audio Package;;;;;RFC 2897;DOI 10.17487/RFC2897;August;https://www.rfc-editor.org/info/rfc2897 | |
| RFC2898;RFC8018;Kaliski, B.;PKCS #5: Password-Based Cryptography Specification Version 2.0;;;;;RFC 2898;DOI 10.17487/RFC2898;September;https://www.rfc-editor.org/info/rfc2898 | |
| RFC2899;;Ginoza, S.;Request for Comments Summary RFC Numbers 2800-2899;;;;;RFC 2899;DOI 10.17487/RFC2899;May;https://www.rfc-editor.org/info/rfc2899 | |
| RFC2900;RFC3000;Reynolds, J., Braden, R., and S. Ginoza;Internet Official Protocol Standards;;;;;RFC 2900;DOI 10.17487/RFC2900;August;https://www.rfc-editor.org/info/rfc2900 | |
| RFC2901;;Wenzel, Z., Klensin, J., Bush, R., and S. Huter;Guide to Administrative Procedures of the Internet Infrastructure;;FYI 37;;;RFC 2901;DOI 10.17487/RFC2901;August;https://www.rfc-editor.org/info/rfc2901 | |
| RFC2902;;Deering, S., Hares, S., Perkins, C., and R. Perlman;Overview of the 1998 IAB Routing Workshop;;;;;RFC 2902;DOI 10.17487/RFC2902;August;https://www.rfc-editor.org/info/rfc2902 | |
| RFC2903;;de Laat, C., Gross, G., Gommans, L., Vollbrecht, J., and D. Spence;Generic AAA Architecture;;;;;RFC 2903;DOI 10.17487/RFC2903;August;https://www.rfc-editor.org/info/rfc2903 | |
| RFC2904;;Vollbrecht, J., Calhoun, P., Farrell, S., Gommans, L., Gross, G., de Bruijn, B., de Laat, C., Holdrege, M., and D. Spence;AAA Authorization Framework;;;;;RFC 2904;DOI 10.17487/RFC2904;August;https://www.rfc-editor.org/info/rfc2904 | |
| RFC2905;;Vollbrecht, J., Calhoun, P., Farrell, S., Gommans, L., Gross, G., de Bruijn, B., de Laat, C., Holdrege, M., and D. Spence;AAA Authorization Application Examples;;;;;RFC 2905;DOI 10.17487/RFC2905;August;https://www.rfc-editor.org/info/rfc2905 | |
| RFC2906;;Farrell, S., Vollbrecht, J., Calhoun, P., Gommans, L., Gross, G., de Bruijn, B., de Laat, C., Holdrege, M., and D. Spence;AAA Authorization Requirements;;;;;RFC 2906;DOI 10.17487/RFC2906;August;https://www.rfc-editor.org/info/rfc2906 | |
| RFC2907;;Kermode, R.;MADCAP Multicast Scope Nesting State Option;;;;;RFC 2907;DOI 10.17487/RFC2907;September;https://www.rfc-editor.org/info/rfc2907 | |
| RFC2908;RFC6308;Thaler, D., Handley, M., and D. Estrin;The Internet Multicast Address Allocation Architecture;;;;;RFC 2908;DOI 10.17487/RFC2908;September;https://www.rfc-editor.org/info/rfc2908 | |
| RFC2909;;Radoslavov, P., Estrin, D., Govindan, R., Handley, M., Kumar, S., and D. Thaler;The Multicast Address-Set Claim (MASC) Protocol;;;;;RFC 2909;DOI 10.17487/RFC2909;September;https://www.rfc-editor.org/info/rfc2909 | |
| RFC2910;RFC8010;Herriot, R., Ed., Butler, S., Moore, P., Turner, R., and J. Wenn;Internet Printing Protocol/1.1: Encoding and Transport;;;;;RFC 2910;DOI 10.17487/RFC2910;September;https://www.rfc-editor.org/info/rfc2910 | |
| RFC2911;RFC8011;Hastings, T., Ed., Herriot, R., deBry, R., Isaacson, S., and P. Powell;Internet Printing Protocol/1.1: Model and Semantics;;;;;RFC 2911;DOI 10.17487/RFC2911;September;https://www.rfc-editor.org/info/rfc2911 | |
| RFC2912;;Klyne, G.;Indicating Media Features for MIME Content;;;;;RFC 2912;DOI 10.17487/RFC2912;September;https://www.rfc-editor.org/info/rfc2912 | |
| RFC2913;;Klyne, G.;MIME Content Types in Media Feature Expressions;;;;;RFC 2913;DOI 10.17487/RFC2913;September;https://www.rfc-editor.org/info/rfc2913 | |
| RFC2914;;Floyd, S.;Congestion Control Principles;;;BCP 41;;RFC 2914;DOI 10.17487/RFC2914;September;https://www.rfc-editor.org/info/rfc2914 | |
| RFC2915;RFC3401, RFC3402, RFC3403, RFC3404;Mealling, M. and R. Daniel;The Naming Authority Pointer (NAPTR) DNS Resource Record;;;;;RFC 2915;DOI 10.17487/RFC2915;September;https://www.rfc-editor.org/info/rfc2915 | |
| RFC2916;RFC3761;Faltstrom, P.;E.164 number and DNS;;;;;RFC 2916;DOI 10.17487/RFC2916;September;https://www.rfc-editor.org/info/rfc2916 | |
| RFC2917;;Muthukrishnan, K. and A. Malis;A Core MPLS IP VPN Architecture;;;;;RFC 2917;DOI 10.17487/RFC2917;September;https://www.rfc-editor.org/info/rfc2917 | |
| RFC2918;;Chen, E.;Route Refresh Capability for BGP-4;;;;;RFC 2918;DOI 10.17487/RFC2918;September;https://www.rfc-editor.org/info/rfc2918 | |
| RFC2919;;Chandhok, R. and G. Wenger;List-Id: A Structured Field and Namespace for the Identification of Mailing Lists;;;;;RFC 2919;DOI 10.17487/RFC2919;March;https://www.rfc-editor.org/info/rfc2919 | |
| RFC2920;;Freed, N.;SMTP Service Extension for Command Pipelining;;;;STD 60;RFC 2920;DOI 10.17487/RFC2920;September;https://www.rfc-editor.org/info/rfc2920 | |
| RFC2921;;Fink, B.;6BONE pTLA and pNLA Formats (pTLA);;;;;RFC 2921;DOI 10.17487/RFC2921;September;https://www.rfc-editor.org/info/rfc2921 | |
| RFC2922;;Bierman, A. and K. Jones;Physical Topology MIB;;;;;RFC 2922;DOI 10.17487/RFC2922;September;https://www.rfc-editor.org/info/rfc2922 | |
| RFC2923;;Lahey, K.;TCP Problems with Path MTU Discovery;;;;;RFC 2923;DOI 10.17487/RFC2923;September;https://www.rfc-editor.org/info/rfc2923 | |
| RFC2924;;Brownlee, N. and A. Blount;Accounting Attributes and Record Formats;;;;;RFC 2924;DOI 10.17487/RFC2924;September;https://www.rfc-editor.org/info/rfc2924 | |
| RFC2925;RFC4560;White, K.;Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations;;;;;RFC 2925;DOI 10.17487/RFC2925;September;https://www.rfc-editor.org/info/rfc2925 | |
| RFC2926;;Kempf, J., Moats, R., and P. St. Pierre;Conversion of LDAP Schemas to and from SLP Templates;;;;;RFC 2926;DOI 10.17487/RFC2926;September;https://www.rfc-editor.org/info/rfc2926 | |
| RFC2927;;Wahl, M.;MIME Directory Profile for LDAP Schema;;;;;RFC 2927;DOI 10.17487/RFC2927;September;https://www.rfc-editor.org/info/rfc2927 | |
| RFC2928;;Hinden, R., Deering, S., Fink, R., and T. Hain;Initial IPv6 Sub-TLA ID Assignments;;;;;RFC 2928;DOI 10.17487/RFC2928;September;https://www.rfc-editor.org/info/rfc2928 | |
| RFC2929;RFC5395;Eastlake 3rd, D., Brunner-Williams, E., and B. Manning;Domain Name System (DNS) IANA Considerations;;;;;RFC 2929;DOI 10.17487/RFC2929;September;https://www.rfc-editor.org/info/rfc2929 | |
| RFC2930;;Eastlake 3rd, D.;Secret Key Establishment for DNS (TKEY RR);;;;;RFC 2930;DOI 10.17487/RFC2930;September;https://www.rfc-editor.org/info/rfc2930 | |
| RFC2931;;Eastlake 3rd, D.;DNS Request and Transaction Signatures ( SIG(0)s );;;;;RFC 2931;DOI 10.17487/RFC2931;September;https://www.rfc-editor.org/info/rfc2931 | |
| RFC2932;RFC5132;McCloghrie, K., Farinacci, D., and D. Thaler;IPv4 Multicast Routing MIB;;;;;RFC 2932;DOI 10.17487/RFC2932;October;https://www.rfc-editor.org/info/rfc2932 | |
| RFC2933;RFC5519;McCloghrie, K., Farinacci, D., and D. Thaler;Internet Group Management Protocol MIB;;;;;RFC 2933;DOI 10.17487/RFC2933;October;https://www.rfc-editor.org/info/rfc2933 | |
| RFC2934;;McCloghrie, K., Farinacci, D., Thaler, D., and B. Fenner;Protocol Independent Multicast MIB for IPv4;;;;;RFC 2934;DOI 10.17487/RFC2934;October;https://www.rfc-editor.org/info/rfc2934 | |
| RFC2935;;Eastlake 3rd, D. and C. Smith;Internet Open Trading Protocol (IOTP) HTTP Supplement;;;;;RFC 2935;DOI 10.17487/RFC2935;September;https://www.rfc-editor.org/info/rfc2935 | |
| RFC2936;;Eastlake 3rd, D., Smith, C., and D. Soroka;HTTP MIME Type Handler Detection;;;;;RFC 2936;DOI 10.17487/RFC2936;September;https://www.rfc-editor.org/info/rfc2936 | |
| RFC2937;;Smith, C.;The Name Service Search Option for DHCP;;;;;RFC 2937;DOI 10.17487/RFC2937;September;https://www.rfc-editor.org/info/rfc2937 | |
| RFC2938;;Klyne, G. and L. Masinter;Identifying Composite Media Features;;;;;RFC 2938;DOI 10.17487/RFC2938;September;https://www.rfc-editor.org/info/rfc2938 | |
| RFC2939;;Droms, R.;Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types;;;BCP 43;;RFC 2939;DOI 10.17487/RFC2939;September;https://www.rfc-editor.org/info/rfc2939 | |
| RFC2940;;Smith, A., Partain, D., and J. Seligson;Definitions of Managed Objects for Common Open Policy Service (COPS) Protocol Clients;;;;;RFC 2940;DOI 10.17487/RFC2940;October;https://www.rfc-editor.org/info/rfc2940 | |
| RFC2941;;Ts'o, T., Ed., and J. Altman;Telnet Authentication Option;;;;;RFC 2941;DOI 10.17487/RFC2941;September;https://www.rfc-editor.org/info/rfc2941 | |
| RFC2942;;Ts'o, T.;Telnet Authentication: Kerberos Version 5;;;;;RFC 2942;DOI 10.17487/RFC2942;September;https://www.rfc-editor.org/info/rfc2942 | |
| RFC2943;;Housley, R., Horting, T., and P. Yee;TELNET Authentication Using DSA;;;;;RFC 2943;DOI 10.17487/RFC2943;September;https://www.rfc-editor.org/info/rfc2943 | |
| RFC2944;;Wu, T.;Telnet Authentication: SRP;;;;;RFC 2944;DOI 10.17487/RFC2944;September;https://www.rfc-editor.org/info/rfc2944 | |
| RFC2945;;Wu, T.;The SRP Authentication and Key Exchange System;;;;;RFC 2945;DOI 10.17487/RFC2945;September;https://www.rfc-editor.org/info/rfc2945 | |
| RFC2946;;Ts'o, T.;Telnet Data Encryption Option;;;;;RFC 2946;DOI 10.17487/RFC2946;September;https://www.rfc-editor.org/info/rfc2946 | |
| RFC2947;;Altman, J.;Telnet Encryption: DES3 64 bit Cipher Feedback;;;;;RFC 2947;DOI 10.17487/RFC2947;September;https://www.rfc-editor.org/info/rfc2947 | |
| RFC2948;;Altman, J.;Telnet Encryption: DES3 64 bit Output Feedback;;;;;RFC 2948;DOI 10.17487/RFC2948;September;https://www.rfc-editor.org/info/rfc2948 | |
| RFC2949;;Altman, J.;Telnet Encryption: CAST-128 64 bit Output Feedback;;;;;RFC 2949;DOI 10.17487/RFC2949;September;https://www.rfc-editor.org/info/rfc2949 | |
| RFC2950;;Altman, J.;Telnet Encryption: CAST-128 64 bit Cipher Feedback;;;;;RFC 2950;DOI 10.17487/RFC2950;September;https://www.rfc-editor.org/info/rfc2950 | |
| RFC2951;;Housley, R., Horting, T., and P. Yee;TELNET Authentication Using KEA and SKIPJACK;;;;;RFC 2951;DOI 10.17487/RFC2951;September;https://www.rfc-editor.org/info/rfc2951 | |
| RFC2952;;Ts'o, T.;Telnet Encryption: DES 64 bit Cipher Feedback;;;;;RFC 2952;DOI 10.17487/RFC2952;September;https://www.rfc-editor.org/info/rfc2952 | |
| RFC2953;;Ts'o, T.;Telnet Encryption: DES 64 bit Output Feedback;;;;;RFC 2953;DOI 10.17487/RFC2953;September;https://www.rfc-editor.org/info/rfc2953 | |
| RFC2954;;Rehbehn, K. and D. Fowler;Definitions of Managed Objects for Frame Relay Service;;;;;RFC 2954;DOI 10.17487/RFC2954;October;https://www.rfc-editor.org/info/rfc2954 | |
| RFC2955;;Rehbehn, K., Nicklass, O., and G. Mouradian;Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function;;;;;RFC 2955;DOI 10.17487/RFC2955;October;https://www.rfc-editor.org/info/rfc2955 | |
| RFC2956;;Kaat, M.;Overview of 1999 IAB Network Layer Workshop;;;;;RFC 2956;DOI 10.17487/RFC2956;October;https://www.rfc-editor.org/info/rfc2956 | |
| RFC2957;;Daigle, L. and P. Faltstrom;The application/whoispp-query Content-Type;;;;;RFC 2957;DOI 10.17487/RFC2957;October;https://www.rfc-editor.org/info/rfc2957 | |
| RFC2958;;Daigle, L. and P. Faltstrom;The application/whoispp-response Content-type;;;;;RFC 2958;DOI 10.17487/RFC2958;October;https://www.rfc-editor.org/info/rfc2958 | |
| RFC2959;;Baugher, M., Strahm, B., and I. Suconick;Real-Time Transport Protocol Management Information Base;;;;;RFC 2959;DOI 10.17487/RFC2959;October;https://www.rfc-editor.org/info/rfc2959 | |
| RFC2960;RFC4960;Stewart, R., Xie, Q., Morneault, K., Sharp, C., Schwarzbauer, H., Taylor, T., Rytina, I., Kalla, M., Zhang, L., and V. Paxson;Stream Control Transmission Protocol;;;;;RFC 2960;DOI 10.17487/RFC2960;October;https://www.rfc-editor.org/info/rfc2960 | |
| RFC2961;;Berger, L., Gan, D., Swallow, G., Pan, P., Tommasi, F., and S. Molendini;RSVP Refresh Overhead Reduction Extensions;;;;;RFC 2961;DOI 10.17487/RFC2961;April;https://www.rfc-editor.org/info/rfc2961 | |
| RFC2962;;Raz, D., Schoenwaelder, J., and B. Sugla;An SNMP Application Level Gateway for Payload Address Translation;;;;;RFC 2962;DOI 10.17487/RFC2962;October;https://www.rfc-editor.org/info/rfc2962 | |
| RFC2963;;Bonaventure, O. and S. De Cnodder;A Rate Adaptive Shaper for Differentiated Services;;;;;RFC 2963;DOI 10.17487/RFC2963;October;https://www.rfc-editor.org/info/rfc2963 | |
| RFC2964;;Moore, K. and N. Freed;Use of HTTP State Management;;;BCP 44;;RFC 2964;DOI 10.17487/RFC2964;October;https://www.rfc-editor.org/info/rfc2964 | |
| RFC2965;RFC6265;Kristol, D. and L. Montulli;HTTP State Management Mechanism;;;;;RFC 2965;DOI 10.17487/RFC2965;October;https://www.rfc-editor.org/info/rfc2965 | |
| RFC2966;RFC5302;Li, T., Przygienda, T., and H. Smit;Domain-wide Prefix Distribution with Two-Level IS-IS;;;;;RFC 2966;DOI 10.17487/RFC2966;October;https://www.rfc-editor.org/info/rfc2966 | |
| RFC2967;;Daigle, L. and R. Hedberg;TISDAG - Technical Infrastructure for Swedish Directory Access Gateways;;;;;RFC 2967;DOI 10.17487/RFC2967;October;https://www.rfc-editor.org/info/rfc2967 | |
| RFC2968;;Daigle, L. and T. Eklof;Mesh of Multiple DAG servers - Results from TISDAG;;;;;RFC 2968;DOI 10.17487/RFC2968;October;https://www.rfc-editor.org/info/rfc2968 | |
| RFC2969;;Eklof, T. and L. Daigle;Wide Area Directory Deployment - Experiences from TISDAG;;;;;RFC 2969;DOI 10.17487/RFC2969;October;https://www.rfc-editor.org/info/rfc2969 | |
| RFC2970;;Daigle, L. and T. Eklof;Architecture for Integrated Directory Services - Result from TISDAG;;;;;RFC 2970;DOI 10.17487/RFC2970;October;https://www.rfc-editor.org/info/rfc2970 | |
| RFC2971;;Showalter, T.;IMAP4 ID extension;;;;;RFC 2971;DOI 10.17487/RFC2971;October;https://www.rfc-editor.org/info/rfc2971 | |
| RFC2972;;Popp, N., Mealling, M., Masinter, L., and K. Sollins;Context and Goals for Common Name Resolution;;;;;RFC 2972;DOI 10.17487/RFC2972;October;https://www.rfc-editor.org/info/rfc2972 | |
| RFC2973;;Balay, R., Katz, D., and J. Parker;IS-IS Mesh Groups;;;;;RFC 2973;DOI 10.17487/RFC2973;October;https://www.rfc-editor.org/info/rfc2973 | |
| RFC2974;;Handley, M., Perkins, C., and E. Whelan;Session Announcement Protocol;;;;;RFC 2974;DOI 10.17487/RFC2974;October;https://www.rfc-editor.org/info/rfc2974 | |
| RFC2975;;Aboba, B., Arkko, J., and D. Harrington;Introduction to Accounting Management;;;;;RFC 2975;DOI 10.17487/RFC2975;October;https://www.rfc-editor.org/info/rfc2975 | |
| RFC2976;RFC6086;Donovan, S.;The SIP INFO Method;;;;;RFC 2976;DOI 10.17487/RFC2976;October;https://www.rfc-editor.org/info/rfc2976 | |
| RFC2977;;Glass, S., Hiller, T., Jacobs, S., and C. Perkins;Mobile IP Authentication, Authorization, and Accounting Requirements;;;;;RFC 2977;DOI 10.17487/RFC2977;October;https://www.rfc-editor.org/info/rfc2977 | |
| RFC2978;;Freed, N. and J. Postel;IANA Charset Registration Procedures;;;BCP 19;;RFC 2978;DOI 10.17487/RFC2978;October;https://www.rfc-editor.org/info/rfc2978 | |
| RFC2979;;Freed, N.;Behavior of and Requirements for Internet Firewalls;;;;;RFC 2979;DOI 10.17487/RFC2979;October;https://www.rfc-editor.org/info/rfc2979 | |
| RFC2980;;Barber, S.;Common NNTP Extensions;;;;;RFC 2980;DOI 10.17487/RFC2980;October;https://www.rfc-editor.org/info/rfc2980 | |
| RFC2981;;Kavasseri, R., Ed.;Event MIB;;;;;RFC 2981;DOI 10.17487/RFC2981;October;https://www.rfc-editor.org/info/rfc2981 | |
| RFC2982;;Kavasseri, R., Ed.;Distributed Management Expression MIB;;;;;RFC 2982;DOI 10.17487/RFC2982;October;https://www.rfc-editor.org/info/rfc2982 | |
| RFC2983;;Black, D.;Differentiated Services and Tunnels;;;;;RFC 2983;DOI 10.17487/RFC2983;October;https://www.rfc-editor.org/info/rfc2983 | |
| RFC2984;;Adams, C.;Use of the CAST-128 Encryption Algorithm in CMS;;;;;RFC 2984;DOI 10.17487/RFC2984;October;https://www.rfc-editor.org/info/rfc2984 | |
| RFC2985;;Nystrom, M. and B. Kaliski;PKCS #9: Selected Object Classes and Attribute Types Version 2.0;;;;;RFC 2985;DOI 10.17487/RFC2985;November;https://www.rfc-editor.org/info/rfc2985 | |
| RFC2986;;Nystrom, M. and B. Kaliski;PKCS #10: Certification Request Syntax Specification Version 1.7;;;;;RFC 2986;DOI 10.17487/RFC2986;November;https://www.rfc-editor.org/info/rfc2986 | |
| RFC2987;;Hoffman, P.;Registration of Charset and Languages Media Features Tags;;;;;RFC 2987;DOI 10.17487/RFC2987;November;https://www.rfc-editor.org/info/rfc2987 | |
| RFC2988;RFC6298;Paxson, V. and M. Allman;Computing TCP's Retransmission Timer;;;;;RFC 2988;DOI 10.17487/RFC2988;November;https://www.rfc-editor.org/info/rfc2988 | |
| RFC2989;;Aboba, B., Calhoun, P., Glass, S., Hiller, T., McCann, P., Shiino, H., Walsh, P., Zorn, G., Dommety, G., Perkins, C., Patil, B., Mitton, D., Manning, S., Beadles, M., Chen, X., Sivalingham, S., Hameed, A., Munson, M., Jacobs, S., Lim, B., Hirschman, B., Hsu, R., Koo, H., Lipford, M., Campbell, E., Xu, Y., Baba, S., and E. Jaques;Criteria for Evaluating AAA Protocols for Network Access;;;;;RFC 2989;DOI 10.17487/RFC2989;November;https://www.rfc-editor.org/info/rfc2989 | |
| RFC2990;;Huston, G.;Next Steps for the IP QoS Architecture;;;;;RFC 2990;DOI 10.17487/RFC2990;November;https://www.rfc-editor.org/info/rfc2990 | |
| RFC2991;;Thaler, D. and C. Hopps;Multipath Issues in Unicast and Multicast Next-Hop Selection;;;;;RFC 2991;DOI 10.17487/RFC2991;November;https://www.rfc-editor.org/info/rfc2991 | |
| RFC2992;;Hopps, C.;Analysis of an Equal-Cost Multi-Path Algorithm;;;;;RFC 2992;DOI 10.17487/RFC2992;November;https://www.rfc-editor.org/info/rfc2992 | |
| RFC2993;;Hain, T.;Architectural Implications of NAT;;;;;RFC 2993;DOI 10.17487/RFC2993;November;https://www.rfc-editor.org/info/rfc2993 | |
| RFC2994;;Ohta, H. and M. Matsui;A Description of the MISTY1 Encryption Algorithm;;;;;RFC 2994;DOI 10.17487/RFC2994;November;https://www.rfc-editor.org/info/rfc2994 | |
| RFC2995;;Lu, H., Ed., Faynberg, I., Voelker, J., Weissman, M., Zhang, W., Rhim, S., Hwang, J., Ago, S., Moeenuddin, S., Hadvani, S., Nyckelgard, S., Yoakum, J., and L. Robart;Pre-Spirits Implementations of PSTN-initiated Services;;;;;RFC 2995;DOI 10.17487/RFC2995;November;https://www.rfc-editor.org/info/rfc2995 | |
| RFC2996;;Bernet, Y.;Format of the RSVP DCLASS Object;;;;;RFC 2996;DOI 10.17487/RFC2996;November;https://www.rfc-editor.org/info/rfc2996 | |
| RFC2997;;Bernet, Y., Smith, A., and B. Davie;Specification of the Null Service Type;;;;;RFC 2997;DOI 10.17487/RFC2997;November;https://www.rfc-editor.org/info/rfc2997 | |
| RFC2998;;Bernet, Y., Ford, P., Yavatkar, R., Baker, F., Zhang, L., Speer, M., Braden, R., Davie, B., Wroclawski, J., and E. Felstaine;A Framework for Integrated Services Operation over Diffserv Networks;;;;;RFC 2998;DOI 10.17487/RFC2998;November;https://www.rfc-editor.org/info/rfc2998 | |
| RFC2999;;Ginoza, S.;Request for Comments Summary RFC Numbers 2900-2999;;;;;RFC 2999;DOI 10.17487/RFC2999;August;https://www.rfc-editor.org/info/rfc2999 | |
| RFC3000;RFC3300;Reynolds, J., Braden, R., Ginoza, S., and L. Shiota;Internet Official Protocol Standards;;;;;RFC 3000;DOI 10.17487/RFC3000;November;https://www.rfc-editor.org/info/rfc3000 | |
| RFC3001;RFC3061;Mealling, M.;A URN Namespace of Object Identifiers;;;;;RFC 3001;DOI 10.17487/RFC3001;November;https://www.rfc-editor.org/info/rfc3001 | |
| RFC3002;;Mitzel, D.;Overview of 2000 IAB Wireless Internetworking Workshop;;;;;RFC 3002;DOI 10.17487/RFC3002;December;https://www.rfc-editor.org/info/rfc3002 | |
| RFC3003;;Nilsson, M.;The audio/mpeg Media Type;;;;;RFC 3003;DOI 10.17487/RFC3003;November;https://www.rfc-editor.org/info/rfc3003 | |
| RFC3004;;Stump, G., Droms, R., Gu, Y., Vyaghrapuri, R., Demirtjis, A., Beser, B., and J. Privat;The User Class Option for DHCP;;;;;RFC 3004;DOI 10.17487/RFC3004;November;https://www.rfc-editor.org/info/rfc3004 | |
| RFC3005;;Harris, S.;IETF Discussion List Charter;;;BCP 45;;RFC 3005;DOI 10.17487/RFC3005;November;https://www.rfc-editor.org/info/rfc3005 | |
| RFC3006;;Davie, B., Iturralde, C., Oran, D., Casner, S., and J. Wroclawski;Integrated Services in the Presence of Compressible Flows;;;;;RFC 3006;DOI 10.17487/RFC3006;November;https://www.rfc-editor.org/info/rfc3006 | |
| RFC3007;;Wellington, B.;Secure Domain Name System (DNS) Dynamic Update;;;;;RFC 3007;DOI 10.17487/RFC3007;November;https://www.rfc-editor.org/info/rfc3007 | |
| RFC3008;RFC4035, RFC4033, RFC4034;Wellington, B.;Domain Name System Security (DNSSEC) Signing Authority;;;;;RFC 3008;DOI 10.17487/RFC3008;November;https://www.rfc-editor.org/info/rfc3008 | |
| RFC3009;RFC5109;Rosenberg, J. and H. Schulzrinne;Registration of parityfec MIME types;;;;;RFC 3009;DOI 10.17487/RFC3009;November;https://www.rfc-editor.org/info/rfc3009 | |
| RFC3010;RFC3530;Shepler, S., Callaghan, B., Robinson, D., Thurlow, R., Beame, C., Eisler, M., and D. Noveck;NFS version 4 Protocol;;;;;RFC 3010;DOI 10.17487/RFC3010;December;https://www.rfc-editor.org/info/rfc3010 | |
| RFC3011;;Waters, G.;The IPv4 Subnet Selection Option for DHCP;;;;;RFC 3011;DOI 10.17487/RFC3011;November;https://www.rfc-editor.org/info/rfc3011 | |
| RFC3012;RFC4721;Perkins, C. and P. Calhoun;Mobile IPv4 Challenge/Response Extensions;;;;;RFC 3012;DOI 10.17487/RFC3012;November;https://www.rfc-editor.org/info/rfc3012 | |
| RFC3013;;Killalea, T.;Recommended Internet Service Provider Security Services and Procedures;;;BCP 46;;RFC 3013;DOI 10.17487/RFC3013;November;https://www.rfc-editor.org/info/rfc3013 | |
| RFC3014;;Kavasseri, R.;Notification Log MIB;;;;;RFC 3014;DOI 10.17487/RFC3014;November;https://www.rfc-editor.org/info/rfc3014 | |
| RFC3015;RFC3525;Cuervo, F., Greene, N., Rayhan, A., Huitema, C., Rosen, B., and J. Segers;Megaco Protocol Version 1.0;;;;;RFC 3015;DOI 10.17487/RFC3015;November;https://www.rfc-editor.org/info/rfc3015 | |
| RFC3016;RFC6416;Kikuchi, Y., Nomura, T., Fukunaga, S., Matsui, Y., and H. Kimata;RTP Payload Format for MPEG-4 Audio/Visual Streams;;;;;RFC 3016;DOI 10.17487/RFC3016;November;https://www.rfc-editor.org/info/rfc3016 | |
| RFC3017;;Riegel, M. and G. Zorn;XML DTD for Roaming Access Phone Book;;;;;RFC 3017;DOI 10.17487/RFC3017;December;https://www.rfc-editor.org/info/rfc3017 | |
| RFC3018;;Bogdanov, A.;Unified Memory Space Protocol Specification;;;;;RFC 3018;DOI 10.17487/RFC3018;December;https://www.rfc-editor.org/info/rfc3018 | |
| RFC3019;RFC5519;Haberman, B. and R. Worzella;IP Version 6 Management Information Base for The Multicast Listener Discovery Protocol;;;;;RFC 3019;DOI 10.17487/RFC3019;January;https://www.rfc-editor.org/info/rfc3019 | |
| RFC3020;;Pate, P., Lynch, B., and K. Rehbehn;Definitions of Managed Objects for Monitoring and Controlling the UNI/NNI Multilink Frame Relay Function;;;;;RFC 3020;DOI 10.17487/RFC3020;December;https://www.rfc-editor.org/info/rfc3020 | |
| RFC3021;;Retana, A., White, R., Fuller, V., and D. McPherson;Using 31-Bit Prefixes on IPv4 Point-to-Point Links;;;;;RFC 3021;DOI 10.17487/RFC3021;December;https://www.rfc-editor.org/info/rfc3021 | |
| RFC3022;;Srisuresh, P. and K. Egevang;Traditional IP Network Address Translator (Traditional NAT);;;;;RFC 3022;DOI 10.17487/RFC3022;January;https://www.rfc-editor.org/info/rfc3022 | |
| RFC3023;RFC7303;Murata, M., St. Laurent, S., and D. Kohn;XML Media Types;;;;;RFC 3023;DOI 10.17487/RFC3023;January;https://www.rfc-editor.org/info/rfc3023 | |
| RFC3024;;Montenegro, G., Ed.;Reverse Tunneling for Mobile IP, revised;;;;;RFC 3024;DOI 10.17487/RFC3024;January;https://www.rfc-editor.org/info/rfc3024 | |
| RFC3025;RFC3115;Dommety, G. and K. Leung;Mobile IP Vendor/Organization-Specific Extensions;;;;;RFC 3025;DOI 10.17487/RFC3025;February;https://www.rfc-editor.org/info/rfc3025 | |
| RFC3026;;Blane, R.;Liaison to IETF/ISOC on ENUM;;;;;RFC 3026;DOI 10.17487/RFC3026;January;https://www.rfc-editor.org/info/rfc3026 | |
| RFC3027;;Holdrege, M. and P. Srisuresh;Protocol Complications with the IP Network Address Translator;;;;;RFC 3027;DOI 10.17487/RFC3027;January;https://www.rfc-editor.org/info/rfc3027 | |
| RFC3028;RFC5228, RFC5429;Showalter, T.;Sieve: A Mail Filtering Language;;;;;RFC 3028;DOI 10.17487/RFC3028;January;https://www.rfc-editor.org/info/rfc3028 | |
| RFC3029;;Adams, C., Sylvester, P., Zolotarev, M., and R. Zuccherato;Internet X.509 Public Key Infrastructure Data Validation and Certification Server Protocols;;;;;RFC 3029;DOI 10.17487/RFC3029;February;https://www.rfc-editor.org/info/rfc3029 | |
| RFC3030;;Vaudreuil, G.;SMTP Service Extensions for Transmission of Large and Binary MIME Messages;;;;;RFC 3030;DOI 10.17487/RFC3030;December;https://www.rfc-editor.org/info/rfc3030 | |
| RFC3031;;Rosen, E., Viswanathan, A., and R. Callon;Multiprotocol Label Switching Architecture;;;;;RFC 3031;DOI 10.17487/RFC3031;January;https://www.rfc-editor.org/info/rfc3031 | |
| RFC3032;;Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci, D., Li, T., and A. Conta;MPLS Label Stack Encoding;;;;;RFC 3032;DOI 10.17487/RFC3032;January;https://www.rfc-editor.org/info/rfc3032 | |
| RFC3033;;Suzuki, M.;The Assignment of the Information Field and Protocol Identifier in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet Protocol;;;;;RFC 3033;DOI 10.17487/RFC3033;January;https://www.rfc-editor.org/info/rfc3033 | |
| RFC3034;;Conta, A., Doolan, P., and A. Malis;Use of Label Switching on Frame Relay Networks Specification;;;;;RFC 3034;DOI 10.17487/RFC3034;January;https://www.rfc-editor.org/info/rfc3034 | |
| RFC3035;;Davie, B., Lawrence, J., McCloghrie, K., Rosen, E., Swallow, G., Rekhter, Y., and P. Doolan;MPLS using LDP and ATM VC Switching;;;;;RFC 3035;DOI 10.17487/RFC3035;January;https://www.rfc-editor.org/info/rfc3035 | |
| RFC3036;RFC5036;Andersson, L., Doolan, P., Feldman, N., Fredette, A., and B. Thomas;LDP Specification;;;;;RFC 3036;DOI 10.17487/RFC3036;January;https://www.rfc-editor.org/info/rfc3036 | |
| RFC3037;;Thomas, B. and E. Gray;LDP Applicability;;;;;RFC 3037;DOI 10.17487/RFC3037;January;https://www.rfc-editor.org/info/rfc3037 | |
| RFC3038;;Nagami, K., Katsube, Y., Demizu, N., Esaki, H., and P. Doolan;VCID Notification over ATM link for LDP;;;;;RFC 3038;DOI 10.17487/RFC3038;January;https://www.rfc-editor.org/info/rfc3038 | |
| RFC3039;RFC3739;Santesson, S., Polk, W., Barzin, P., and M. Nystrom;Internet X.509 Public Key Infrastructure Qualified Certificates Profile;;;;;RFC 3039;DOI 10.17487/RFC3039;January;https://www.rfc-editor.org/info/rfc3039 | |
| RFC3040;;Cooper, I., Melve, I., and G. Tomlinson;Internet Web Replication and Caching Taxonomy;;;;;RFC 3040;DOI 10.17487/RFC3040;January;https://www.rfc-editor.org/info/rfc3040 | |
| RFC3041;RFC4941;Narten, T. and R. Draves;Privacy Extensions for Stateless Address Autoconfiguration in IPv6;;;;;RFC 3041;DOI 10.17487/RFC3041;January;https://www.rfc-editor.org/info/rfc3041 | |
| RFC3042;;Allman, M., Balakrishnan, H., and S. Floyd;Enhancing TCP's Loss Recovery Using Limited Transmit;;;;;RFC 3042;DOI 10.17487/RFC3042;January;https://www.rfc-editor.org/info/rfc3042 | |
| RFC3043;;Mealling, M.;The Network Solutions Personal Internet Name (PIN): A URN Namespace for People and Organizations;;;;;RFC 3043;DOI 10.17487/RFC3043;January;https://www.rfc-editor.org/info/rfc3043 | |
| RFC3044;RFC8254;Rozenfeld, S.;Using The ISSN (International Serial Standard Number) as URN (Uniform Resource Names) within an ISSN-URN Namespace;;;;;RFC 3044;DOI 10.17487/RFC3044;January;https://www.rfc-editor.org/info/rfc3044 | |
| RFC3045;;Meredith, M.;Storing Vendor Information in the LDAP root DSE;;;;;RFC 3045;DOI 10.17487/RFC3045;January;https://www.rfc-editor.org/info/rfc3045 | |
| RFC3046;;Patrick, M.;DHCP Relay Agent Information Option;;;;;RFC 3046;DOI 10.17487/RFC3046;January;https://www.rfc-editor.org/info/rfc3046 | |
| RFC3047;RFC5577;Luthi, P.;RTP Payload Format for ITU-T Recommendation G.722.1;;;;;RFC 3047;DOI 10.17487/RFC3047;January;https://www.rfc-editor.org/info/rfc3047 | |
| RFC3048;;Whetten, B., Vicisano, L., Kermode, R., Handley, M., Floyd, S., and M. Luby;Reliable Multicast Transport Building Blocks for One-to-Many Bulk-Data Transfer;;;;;RFC 3048;DOI 10.17487/RFC3048;January;https://www.rfc-editor.org/info/rfc3048 | |
| RFC3049;;Naugle, J., Kasthurirangan, K., and G. Ledford;TN3270E Service Location and Session Balancing;;;;;RFC 3049;DOI 10.17487/RFC3049;January;https://www.rfc-editor.org/info/rfc3049 | |
| RFC3050;;Lennox, J., Schulzrinne, H., and J. Rosenberg;Common Gateway Interface for SIP;;;;;RFC 3050;DOI 10.17487/RFC3050;January;https://www.rfc-editor.org/info/rfc3050 | |
| RFC3051;;Heath, J. and J. Border;IP Payload Compression Using ITU-T V.44 Packet Method;;;;;RFC 3051;DOI 10.17487/RFC3051;January;https://www.rfc-editor.org/info/rfc3051 | |
| RFC3052;;Eder, M. and S. Nag;Service Management Architectures Issues and Review;;;;;RFC 3052;DOI 10.17487/RFC3052;January;https://www.rfc-editor.org/info/rfc3052 | |
| RFC3053;;Durand, A., Fasano, P., Guardini, I., and D. Lento;IPv6 Tunnel Broker;;;;;RFC 3053;DOI 10.17487/RFC3053;January;https://www.rfc-editor.org/info/rfc3053 | |
| RFC3054;;Blatherwick, P., Bell, R., and P. Holland;Megaco IP Phone Media Gateway Application Profile;;;;;RFC 3054;DOI 10.17487/RFC3054;January;https://www.rfc-editor.org/info/rfc3054 | |
| RFC3055;;Krishnaswamy, M. and D. Romascanu;Management Information Base for the PINT Services Architecture;;;;;RFC 3055;DOI 10.17487/RFC3055;February;https://www.rfc-editor.org/info/rfc3055 | |
| RFC3056;;Carpenter, B. and K. Moore;Connection of IPv6 Domains via IPv4 Clouds;;;;;RFC 3056;DOI 10.17487/RFC3056;February;https://www.rfc-editor.org/info/rfc3056 | |
| RFC3057;RFC4233;Morneault, K., Rengasami, S., Kalla, M., and G. Sidebottom;ISDN Q.921-User Adaptation Layer;;;;;RFC 3057;DOI 10.17487/RFC3057;February;https://www.rfc-editor.org/info/rfc3057 | |
| RFC3058;;Teiwes, S., Hartmann, P., and D. Kuenzi;Use of the IDEA Encryption Algorithm in CMS;;;;;RFC 3058;DOI 10.17487/RFC3058;February;https://www.rfc-editor.org/info/rfc3058 | |
| RFC3059;;Guttman, E.;Attribute List Extension for the Service Location Protocol;;;;;RFC 3059;DOI 10.17487/RFC3059;February;https://www.rfc-editor.org/info/rfc3059 | |
| RFC3060;;Moore, B., Ellesson, E., Strassner, J., and A. Westerinen;Policy Core Information Model -- Version 1 Specification;;;;;RFC 3060;DOI 10.17487/RFC3060;February;https://www.rfc-editor.org/info/rfc3060 | |
| RFC3061;;Mealling, M.;A URN Namespace of Object Identifiers;;;;;RFC 3061;DOI 10.17487/RFC3061;February;https://www.rfc-editor.org/info/rfc3061 | |
| RFC3062;;Zeilenga, K.;LDAP Password Modify Extended Operation;;;;;RFC 3062;DOI 10.17487/RFC3062;February;https://www.rfc-editor.org/info/rfc3062 | |
| RFC3063;;Ohba, Y., Katsube, Y., Rosen, E., and P. Doolan;MPLS Loop Prevention Mechanism;;;;;RFC 3063;DOI 10.17487/RFC3063;February;https://www.rfc-editor.org/info/rfc3063 | |
| RFC3064;;Foster, B.;MGCP CAS Packages;;;;;RFC 3064;DOI 10.17487/RFC3064;February;https://www.rfc-editor.org/info/rfc3064 | |
| RFC3065;RFC5065;Traina, P., McPherson, D., and J. Scudder;Autonomous System Confederations for BGP;;;;;RFC 3065;DOI 10.17487/RFC3065;February;https://www.rfc-editor.org/info/rfc3065 | |
| RFC3066;RFC4646, RFC4647;Alvestrand, H.;Tags for the Identification of Languages;;;;;RFC 3066;DOI 10.17487/RFC3066;January;https://www.rfc-editor.org/info/rfc3066 | |
| RFC3067;;Arvidsson, J., Cormack, A., Demchenko, Y., and J. Meijer;TERENA'S Incident Object Description and Exchange Format Requirements;;;;;RFC 3067;DOI 10.17487/RFC3067;February;https://www.rfc-editor.org/info/rfc3067 | |
| RFC3068;RFC7526;Huitema, C.;An Anycast Prefix for 6to4 Relay Routers;;;;;RFC 3068;DOI 10.17487/RFC3068;June;https://www.rfc-editor.org/info/rfc3068 | |
| RFC3069;;McPherson, D. and B. Dykes;VLAN Aggregation for Efficient IP Address Allocation;;;;;RFC 3069;DOI 10.17487/RFC3069;February;https://www.rfc-editor.org/info/rfc3069 | |
| RFC3070;;Rawat, V., Tio, R., Nanji, S., and R. Verma;Layer Two Tunneling Protocol (L2TP) over Frame Relay;;;;;RFC 3070;DOI 10.17487/RFC3070;February;https://www.rfc-editor.org/info/rfc3070 | |
| RFC3071;;Klensin, J.;Reflections on the DNS, RFC 1591, and Categories of Domains;;;;;RFC 3071;DOI 10.17487/RFC3071;February;https://www.rfc-editor.org/info/rfc3071 | |
| RFC3072;;Wildgrube, M.;Structured Data Exchange Format (SDXF);;;;;RFC 3072;DOI 10.17487/RFC3072;March;https://www.rfc-editor.org/info/rfc3072 | |
| RFC3073;;Collins, J.;Portable Font Resource (PFR) - application/font-tdpfr MIME Sub-type Registration;;;;;RFC 3073;DOI 10.17487/RFC3073;March;https://www.rfc-editor.org/info/rfc3073 | |
| RFC3074;;Volz, B., Gonczi, S., Lemon, T., and R. Stevens;DHC Load Balancing Algorithm;;;;;RFC 3074;DOI 10.17487/RFC3074;February;https://www.rfc-editor.org/info/rfc3074 | |
| RFC3075;RFC3275;Eastlake 3rd, D., Reagle, J., and D. Solo;XML-Signature Syntax and Processing;;;;;RFC 3075;DOI 10.17487/RFC3075;March;https://www.rfc-editor.org/info/rfc3075 | |
| RFC3076;;Boyer, J.;Canonical XML Version 1.0;;;;;RFC 3076;DOI 10.17487/RFC3076;March;https://www.rfc-editor.org/info/rfc3076 | |
| RFC3077;;Duros, E., Dabbous, W., Izumiyama, H., Fujii, N., and Y. Zhang;A Link-Layer Tunneling Mechanism for Unidirectional Links;;;;;RFC 3077;DOI 10.17487/RFC3077;March;https://www.rfc-editor.org/info/rfc3077 | |
| RFC3078;;Pall, G. and G. Zorn;Microsoft Point-To-Point Encryption (MPPE) Protocol;;;;;RFC 3078;DOI 10.17487/RFC3078;March;https://www.rfc-editor.org/info/rfc3078 | |
| RFC3079;;Zorn, G.;Deriving Keys for use with Microsoft Point-to-Point Encryption (MPPE);;;;;RFC 3079;DOI 10.17487/RFC3079;March;https://www.rfc-editor.org/info/rfc3079 | |
| RFC3080;;Rose, M.;The Blocks Extensible Exchange Protocol Core;;;;;RFC 3080;DOI 10.17487/RFC3080;March;https://www.rfc-editor.org/info/rfc3080 | |
| RFC3081;;Rose, M.;Mapping the BEEP Core onto TCP;;;;;RFC 3081;DOI 10.17487/RFC3081;March;https://www.rfc-editor.org/info/rfc3081 | |
| RFC3082;;Kempf, J. and J. Goldschmidt;Notification and Subscription for SLP;;;;;RFC 3082;DOI 10.17487/RFC3082;March;https://www.rfc-editor.org/info/rfc3082 | |
| RFC3083;;Woundy, R.;Baseline Privacy Interface Management Information Base for DOCSIS Compliant Cable Modems and Cable Modem Termination Systems;;;;;RFC 3083;DOI 10.17487/RFC3083;March;https://www.rfc-editor.org/info/rfc3083 | |
| RFC3084;;Chan, K., Seligson, J., Durham, D., Gai, S., McCloghrie, K., Herzog, S., Reichmeyer, F., Yavatkar, R., and A. Smith;COPS Usage for Policy Provisioning (COPS-PR);;;;;RFC 3084;DOI 10.17487/RFC3084;March;https://www.rfc-editor.org/info/rfc3084 | |
| RFC3085;;Coates, A., Allen, D., and D. Rivers-Moore;URN Namespace for NewsML Resources;;;;;RFC 3085;DOI 10.17487/RFC3085;March;https://www.rfc-editor.org/info/rfc3085 | |
| RFC3086;;Nichols, K. and B. Carpenter;Definition of Differentiated Services Per Domain Behaviors and Rules for their Specification;;;;;RFC 3086;DOI 10.17487/RFC3086;April;https://www.rfc-editor.org/info/rfc3086 | |
| RFC3087;;Campbell, B. and R. Sparks;Control of Service Context using SIP Request-URI;;;;;RFC 3087;DOI 10.17487/RFC3087;April;https://www.rfc-editor.org/info/rfc3087 | |
| RFC3088;;Zeilenga, K.;OpenLDAP Root Service An experimental LDAP referral service;;;;;RFC 3088;DOI 10.17487/RFC3088;April;https://www.rfc-editor.org/info/rfc3088 | |
| RFC3089;;Kitamura, H.;A SOCKS-based IPv6/IPv4 Gateway Mechanism;;;;;RFC 3089;DOI 10.17487/RFC3089;April;https://www.rfc-editor.org/info/rfc3089 | |
| RFC3090;RFC4033, RFC4034, RFC4035;Lewis, E.;DNS Security Extension Clarification on Zone Status;;;;;RFC 3090;DOI 10.17487/RFC3090;March;https://www.rfc-editor.org/info/rfc3090 | |
| RFC3091;;Kennedy, H.;Pi Digit Generation Protocol;;;;;RFC 3091;DOI 10.17487/RFC3091;April;https://www.rfc-editor.org/info/rfc3091 | |
| RFC3092;;Eastlake 3rd, D., Manros, C., and E. Raymond;Etymology of "Foo";;;;;RFC 3092;DOI 10.17487/RFC3092;April;https://www.rfc-editor.org/info/rfc3092 | |
| RFC3093;;Gaynor, M. and S. Bradner;Firewall Enhancement Protocol (FEP);;;;;RFC 3093;DOI 10.17487/RFC3093;April;https://www.rfc-editor.org/info/rfc3093 | |
| RFC3094;;Sprague, D., Benedyk, R., Brendes, D., and J. Keller;Tekelec's Transport Adapter Layer Interface;;;;;RFC 3094;DOI 10.17487/RFC3094;April;https://www.rfc-editor.org/info/rfc3094 | |
| RFC3095;;Bormann, C., Burmeister, C., Degermark, M., Fukushima, H., Hannu, H., Jonsson, L-E., Hakenberg, R., Koren, T., Le, K., Liu, Z., Martensson, A., Miyazaki, A., Svanbro, K., Wiebke, T., Yoshimura, T., and H. Zheng;RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed;;;;;RFC 3095;DOI 10.17487/RFC3095;July;https://www.rfc-editor.org/info/rfc3095 | |
| RFC3096;;Degermark, M., Ed.;Requirements for robust IP/UDP/RTP header compression;;;;;RFC 3096;DOI 10.17487/RFC3096;July;https://www.rfc-editor.org/info/rfc3096 | |
| RFC3097;;Braden, R. and L. Zhang;RSVP Cryptographic Authentication -- Updated Message Type Value;;;;;RFC 3097;DOI 10.17487/RFC3097;April;https://www.rfc-editor.org/info/rfc3097 | |
| RFC3098;;Gavin, T., Eastlake 3rd, D., and S. Hambridge;How to Advertise Responsibly Using E-Mail and Newsgroups or - how NOT to $$$$$ MAKE ENEMIES FAST! $$$$$;;FYI 38;;;RFC 3098;DOI 10.17487/RFC3098;April;https://www.rfc-editor.org/info/rfc3098 | |
| RFC3099;;Ginoza, S.;Request for Comments Summary RFC Numbers 3000-3099;;;;;RFC 3099;DOI 10.17487/RFC3099;November;https://www.rfc-editor.org/info/rfc3099 | |
| RFC3101;;Murphy, P.;The OSPF Not-So-Stubby Area (NSSA) Option;;;;;RFC 3101;DOI 10.17487/RFC3101;January;https://www.rfc-editor.org/info/rfc3101 | |
| RFC3102;;Borella, M., Lo, J., Grabelsky, D., and G. Montenegro;Realm Specific IP: Framework;;;;;RFC 3102;DOI 10.17487/RFC3102;October;https://www.rfc-editor.org/info/rfc3102 | |
| RFC3103;;Borella, M., Grabelsky, D., Lo, J., and K. Taniguchi;Realm Specific IP: Protocol Specification;;;;;RFC 3103;DOI 10.17487/RFC3103;October;https://www.rfc-editor.org/info/rfc3103 | |
| RFC3104;;Montenegro, G. and M. Borella;RSIP Support for End-to-end IPsec;;;;;RFC 3104;DOI 10.17487/RFC3104;October;https://www.rfc-editor.org/info/rfc3104 | |
| RFC3105;;Kempf, J. and G. Montenegro;Finding an RSIP Server with SLP;;;;;RFC 3105;DOI 10.17487/RFC3105;October;https://www.rfc-editor.org/info/rfc3105 | |
| RFC3106;;Eastlake 3rd, D. and T. Goldstein;ECML v1.1: Field Specifications for E-Commerce;;;;;RFC 3106;DOI 10.17487/RFC3106;April;https://www.rfc-editor.org/info/rfc3106 | |
| RFC3107;RFC8277;Rekhter, Y. and E. Rosen;Carrying Label Information in BGP-4;;;;;RFC 3107;DOI 10.17487/RFC3107;May;https://www.rfc-editor.org/info/rfc3107 | |
| RFC3108;;Kumar, R. and M. Mostafa;Conventions for the use of the Session Description Protocol (SDP) for ATM Bearer Connections;;;;;RFC 3108;DOI 10.17487/RFC3108;May;https://www.rfc-editor.org/info/rfc3108 | |
| RFC3109;;Braden, R., Bush, R., and J. Klensin;Request to Move STD 39 to Historic Status;;;;;RFC 3109;DOI 10.17487/RFC3109;May;https://www.rfc-editor.org/info/rfc3109 | |
| RFC3110;;Eastlake 3rd, D.;RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS);;;;;RFC 3110;DOI 10.17487/RFC3110;May;https://www.rfc-editor.org/info/rfc3110 | |
| RFC3111;;Guttman, E.;Service Location Protocol Modifications for IPv6;;;;;RFC 3111;DOI 10.17487/RFC3111;May;https://www.rfc-editor.org/info/rfc3111 | |
| RFC3112;;Zeilenga, K.;LDAP Authentication Password Schema;;;;;RFC 3112;DOI 10.17487/RFC3112;May;https://www.rfc-editor.org/info/rfc3112 | |
| RFC3113;;Rosenbrock, K., Sanmugam, R., Bradner, S., and J. Klensin;3GPP-IETF Standardization Collaboration;;;;;RFC 3113;DOI 10.17487/RFC3113;June;https://www.rfc-editor.org/info/rfc3113 | |
| RFC3114;;Nicolls, W.;Implementing Company Classification Policy with the S/MIME Security Label;;;;;RFC 3114;DOI 10.17487/RFC3114;May;https://www.rfc-editor.org/info/rfc3114 | |
| RFC3115;;Dommety, G. and K. Leung;Mobile IP Vendor/Organization-Specific Extensions;;;;;RFC 3115;DOI 10.17487/RFC3115;April;https://www.rfc-editor.org/info/rfc3115 | |
| RFC3116;;Dunn, J. and C. Martin;Methodology for ATM Benchmarking;;;;;RFC 3116;DOI 10.17487/RFC3116;June;https://www.rfc-editor.org/info/rfc3116 | |
| RFC3117;;Rose, M.;On the Design of Application Protocols;;;;;RFC 3117;DOI 10.17487/RFC3117;November;https://www.rfc-editor.org/info/rfc3117 | |
| RFC3118;;Droms, R., Ed., and W. Arbaugh, Ed.;Authentication for DHCP Messages;;;;;RFC 3118;DOI 10.17487/RFC3118;June;https://www.rfc-editor.org/info/rfc3118 | |
| RFC3119;RFC5219;Finlayson, R.;A More Loss-Tolerant RTP Payload Format for MP3 Audio;;;;;RFC 3119;DOI 10.17487/RFC3119;June;https://www.rfc-editor.org/info/rfc3119 | |
| RFC3120;;Best, K. and N. Walsh;A URN Namespace for XML.org;;;;;RFC 3120;DOI 10.17487/RFC3120;June;https://www.rfc-editor.org/info/rfc3120 | |
| RFC3121;;Best, K. and N. Walsh;A URN Namespace for OASIS;;;;;RFC 3121;DOI 10.17487/RFC3121;June;https://www.rfc-editor.org/info/rfc3121 | |
| RFC3122;;Conta, A.;Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification;;;;;RFC 3122;DOI 10.17487/RFC3122;June;https://www.rfc-editor.org/info/rfc3122 | |
| RFC3123;;Koch, P.;A DNS RR Type for Lists of Address Prefixes (APL RR);;;;;RFC 3123;DOI 10.17487/RFC3123;June;https://www.rfc-editor.org/info/rfc3123 | |
| RFC3124;;Balakrishnan, H. and S. Seshan;The Congestion Manager;;;;;RFC 3124;DOI 10.17487/RFC3124;June;https://www.rfc-editor.org/info/rfc3124 | |
| RFC3125;;Ross, J., Pinkas, D., and N. Pope;Electronic Signature Policies;;;;;RFC 3125;DOI 10.17487/RFC3125;September;https://www.rfc-editor.org/info/rfc3125 | |
| RFC3126;RFC5126;Pinkas, D., Ross, J., and N. Pope;Electronic Signature Formats for long term electronic signatures;;;;;RFC 3126;DOI 10.17487/RFC3126;September;https://www.rfc-editor.org/info/rfc3126 | |
| RFC3127;;Mitton, D., St.Johns, M., Barkley, S., Nelson, D., Patil, B., Stevens, M., and B. Wolff;Authentication, Authorization, and Accounting: Protocol Evaluation;;;;;RFC 3127;DOI 10.17487/RFC3127;June;https://www.rfc-editor.org/info/rfc3127 | |
| RFC3128;;Miller, I.;Protection Against a Variant of the Tiny Fragment Attack (RFC 1858);;;;;RFC 3128;DOI 10.17487/RFC3128;June;https://www.rfc-editor.org/info/rfc3128 | |
| RFC3129;;Thomas, M.;Requirements for Kerberized Internet Negotiation of Keys;;;;;RFC 3129;DOI 10.17487/RFC3129;June;https://www.rfc-editor.org/info/rfc3129 | |
| RFC3130;;Lewis, E.;Notes from the State-Of-The-Technology: DNSSEC;;;;;RFC 3130;DOI 10.17487/RFC3130;June;https://www.rfc-editor.org/info/rfc3130 | |
| RFC3131;;Bradner, S., Calhoun, P., Cuschieri, H., Dennett, S., Flynn, G., Lipford, M., and M. McPheters;3GPP2-IETF Standardization Collaboration;;;;;RFC 3131;DOI 10.17487/RFC3131;June;https://www.rfc-editor.org/info/rfc3131 | |
| RFC3132;;Kempf, J.;Dormant Mode Host Alerting ("IP Paging") Problem Statement;;;;;RFC 3132;DOI 10.17487/RFC3132;June;https://www.rfc-editor.org/info/rfc3132 | |
| RFC3133;;Dunn, J. and C. Martin;Terminology for Frame Relay Benchmarking;;;;;RFC 3133;DOI 10.17487/RFC3133;June;https://www.rfc-editor.org/info/rfc3133 | |
| RFC3134;;Dunn, J. and C. Martin;Terminology for ATM ABR Benchmarking;;;;;RFC 3134;DOI 10.17487/RFC3134;June;https://www.rfc-editor.org/info/rfc3134 | |
| RFC3135;;Border, J., Kojo, M., Griner, J., Montenegro, G., and Z. Shelby;Performance Enhancing Proxies Intended to Mitigate Link-Related Degradations;;;;;RFC 3135;DOI 10.17487/RFC3135;June;https://www.rfc-editor.org/info/rfc3135 | |
| RFC3136;;Slutsman, L., Ed., Faynberg, I., Lu, H., and M. Weissman;The SPIRITS Architecture;;;;;RFC 3136;DOI 10.17487/RFC3136;June;https://www.rfc-editor.org/info/rfc3136 | |
| RFC3137;RFC6987;Retana, A., Nguyen, L., White, R., Zinin, A., and D. McPherson;OSPF Stub Router Advertisement;;;;;RFC 3137;DOI 10.17487/RFC3137;June;https://www.rfc-editor.org/info/rfc3137 | |
| RFC3138;RFC5771;Meyer, D.;Extended Assignments in 233/8;;;;;RFC 3138;DOI 10.17487/RFC3138;June;https://www.rfc-editor.org/info/rfc3138 | |
| RFC3139;;Sanchez, L., McCloghrie, K., and J. Saperia;Requirements for Configuration Management of IP-based Networks;;;;;RFC 3139;DOI 10.17487/RFC3139;June;https://www.rfc-editor.org/info/rfc3139 | |
| RFC3140;;Black, D., Brim, S., Carpenter, B., and F. Le Faucheur;Per Hop Behavior Identification Codes;;;;;RFC 3140;DOI 10.17487/RFC3140;June;https://www.rfc-editor.org/info/rfc3140 | |
| RFC3141;;Hiller, T., Walsh, P., Chen, X., Munson, M., Dommety, G., Sivalingham, S., Lim, B., McCann, P., Shiino, H., Hirschman, B., Manning, S., Hsu, R., Koo, H., Lipford, M., Calhoun, P., Lo, C., Jaques, E., Campbell, E., Xu, Y., Baba, S., Ayaki, T., Seki, T., and A. Hameed;CDMA2000 Wireless Data Requirements for AAA;;;;;RFC 3141;DOI 10.17487/RFC3141;June;https://www.rfc-editor.org/info/rfc3141 | |
| RFC3142;;Hagino, J. and K. Yamamoto;An IPv6-to-IPv4 Transport Relay Translator;;;;;RFC 3142;DOI 10.17487/RFC3142;June;https://www.rfc-editor.org/info/rfc3142 | |
| RFC3143;;Cooper, I. and J. Dilley;Known HTTP Proxy/Caching Problems;;;;;RFC 3143;DOI 10.17487/RFC3143;June;https://www.rfc-editor.org/info/rfc3143 | |
| RFC3144;;Romascanu, D.;Remote Monitoring MIB Extensions for Interface Parameters Monitoring;;;;;RFC 3144;DOI 10.17487/RFC3144;August;https://www.rfc-editor.org/info/rfc3144 | |
| RFC3145;;Verma, R., Verma, M., and J. Carlson;L2TP Disconnect Cause Information;;;;;RFC 3145;DOI 10.17487/RFC3145;July;https://www.rfc-editor.org/info/rfc3145 | |
| RFC3146;;Fujisawa, K. and A. Onoe;Transmission of IPv6 Packets over IEEE 1394 Networks;;;;;RFC 3146;DOI 10.17487/RFC3146;October;https://www.rfc-editor.org/info/rfc3146 | |
| RFC3147;;Christian, P.;Generic Routing Encapsulation over CLNS Networks;;;;;RFC 3147;DOI 10.17487/RFC3147;July;https://www.rfc-editor.org/info/rfc3147 | |
| RFC3148;;Mathis, M. and M. Allman;A Framework for Defining Empirical Bulk Transfer Capacity Metrics;;;;;RFC 3148;DOI 10.17487/RFC3148;July;https://www.rfc-editor.org/info/rfc3148 | |
| RFC3149;;Srinath, A., Levendel, G., Fritz, K., and R. Kalyanaram;MGCP Business Phone Packages;;;;;RFC 3149;DOI 10.17487/RFC3149;September;https://www.rfc-editor.org/info/rfc3149 | |
| RFC3150;;Dawkins, S., Montenegro, G., Kojo, M., and V. Magret;End-to-end Performance Implications of Slow Links;;;BCP 48;;RFC 3150;DOI 10.17487/RFC3150;July;https://www.rfc-editor.org/info/rfc3150 | |
| RFC3151;;Walsh, N., Cowan, J., and P. Grosso;A URN Namespace for Public Identifiers;;;;;RFC 3151;DOI 10.17487/RFC3151;August;https://www.rfc-editor.org/info/rfc3151 | |
| RFC3152;RFC3596;Bush, R.;Delegation of IP6.ARPA;;;BCP 49;;RFC 3152;DOI 10.17487/RFC3152;August;https://www.rfc-editor.org/info/rfc3152 | |
| RFC3153;;Pazhyannur, R., Ali, I., and C. Fox;PPP Multiplexing;;;;;RFC 3153;DOI 10.17487/RFC3153;August;https://www.rfc-editor.org/info/rfc3153 | |
| RFC3154;;Kempf, J., Castelluccia, C., Mutaf, P., Nakajima, N., Ohba, Y., Ramjee, R., Saifullah, Y., Sarikaya, B., and X. Xu;Requirements and Functional Architecture for an IP Host Alerting Protocol;;;;;RFC 3154;DOI 10.17487/RFC3154;August;https://www.rfc-editor.org/info/rfc3154 | |
| RFC3155;;Dawkins, S., Montenegro, G., Kojo, M., Magret, V., and N. Vaidya;End-to-end Performance Implications of Links with Errors;;;BCP 50;;RFC 3155;DOI 10.17487/RFC3155;August;https://www.rfc-editor.org/info/rfc3155 | |
| RFC3156;;Elkins, M., Del Torto, D., Levien, R., and T. Roessler;MIME Security with OpenPGP;;;;;RFC 3156;DOI 10.17487/RFC3156;August;https://www.rfc-editor.org/info/rfc3156 | |
| RFC3157;;Arsenault, A. and S. Farrell;Securely Available Credentials - Requirements;;;;;RFC 3157;DOI 10.17487/RFC3157;August;https://www.rfc-editor.org/info/rfc3157 | |
| RFC3158;;Perkins, C., Rosenberg, J., and H. Schulzrinne;RTP Testing Strategies;;;;;RFC 3158;DOI 10.17487/RFC3158;August;https://www.rfc-editor.org/info/rfc3158 | |
| RFC3159;;McCloghrie, K., Fine, M., Seligson, J., Chan, K., Hahn, S., Sahita, R., Smith, A., and F. Reichmeyer;Structure of Policy Provisioning Information (SPPI);;;;;RFC 3159;DOI 10.17487/RFC3159;August;https://www.rfc-editor.org/info/rfc3159 | |
| RFC3160;RFC4677;Harris, S.;The Tao of IETF - A Novice's Guide to the Internet Engineering Task Force;;;;;RFC 3160;DOI 10.17487/RFC3160;August;https://www.rfc-editor.org/info/rfc3160 | |
| RFC3161;;Adams, C., Cain, P., Pinkas, D., and R. Zuccherato;Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP);;;;;RFC 3161;DOI 10.17487/RFC3161;August;https://www.rfc-editor.org/info/rfc3161 | |
| RFC3162;;Aboba, B., Zorn, G., and D. Mitton;RADIUS and IPv6;;;;;RFC 3162;DOI 10.17487/RFC3162;August;https://www.rfc-editor.org/info/rfc3162 | |
| RFC3163;;Zuccherato, R. and M. Nystrom;ISO/IEC 9798-3 Authentication SASL Mechanism;;;;;RFC 3163;DOI 10.17487/RFC3163;August;https://www.rfc-editor.org/info/rfc3163 | |
| RFC3164;RFC5424;Lonvick, C.;The BSD Syslog Protocol;;;;;RFC 3164;DOI 10.17487/RFC3164;August;https://www.rfc-editor.org/info/rfc3164 | |
| RFC3165;;Levi, D. and J. Schoenwaelder;Definitions of Managed Objects for the Delegation of Management Scripts;;;;;RFC 3165;DOI 10.17487/RFC3165;August;https://www.rfc-editor.org/info/rfc3165 | |
| RFC3166;;Meyer, D. and J. Scudder;Request to Move RFC 1403 to Historic Status;;;;;RFC 3166;DOI 10.17487/RFC3166;August;https://www.rfc-editor.org/info/rfc3166 | |
| RFC3167;;Meyer, D. and J. Scudder;Request to Move RFC 1745 to Historic Status;;;;;RFC 3167;DOI 10.17487/RFC3167;August;https://www.rfc-editor.org/info/rfc3167 | |
| RFC3168;;Ramakrishnan, K., Floyd, S., and D. Black;The Addition of Explicit Congestion Notification (ECN) to IP;;;;;RFC 3168;DOI 10.17487/RFC3168;September;https://www.rfc-editor.org/info/rfc3168 | |
| RFC3169;;Beadles, M. and D. Mitton;Criteria for Evaluating Network Access Server Protocols;;;;;RFC 3169;DOI 10.17487/RFC3169;September;https://www.rfc-editor.org/info/rfc3169 | |
| RFC3170;;Quinn, B. and K. Almeroth;IP Multicast Applications: Challenges and Solutions;;;;;RFC 3170;DOI 10.17487/RFC3170;September;https://www.rfc-editor.org/info/rfc3170 | |
| RFC3171;RFC5771;Albanna, Z., Almeroth, K., Meyer, D., and M. Schipper;IANA Guidelines for IPv4 Multicast Address Assignments;;;;;RFC 3171;DOI 10.17487/RFC3171;August;https://www.rfc-editor.org/info/rfc3171 | |
| RFC3172;;Huston, G., Ed.;Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa");;;BCP 52;;RFC 3172;DOI 10.17487/RFC3172;September;https://www.rfc-editor.org/info/rfc3172 | |
| RFC3173;;Shacham, A., Monsour, B., Pereira, R., and M. Thomas;IP Payload Compression Protocol (IPComp);;;;;RFC 3173;DOI 10.17487/RFC3173;September;https://www.rfc-editor.org/info/rfc3173 | |
| RFC3174;;Eastlake 3rd, D. and P. Jones;US Secure Hash Algorithm 1 (SHA1);;;;;RFC 3174;DOI 10.17487/RFC3174;September;https://www.rfc-editor.org/info/rfc3174 | |
| RFC3175;;Baker, F., Iturralde, C., Le Faucheur, F., and B. Davie;Aggregation of RSVP for IPv4 and IPv6 Reservations;;;;;RFC 3175;DOI 10.17487/RFC3175;September;https://www.rfc-editor.org/info/rfc3175 | |
| RFC3176;;Phaal, P., Panchen, S., and N. McKee;InMon Corporation's sFlow: A Method for Monitoring Traffic in Switched and Routed Networks;;;;;RFC 3176;DOI 10.17487/RFC3176;September;https://www.rfc-editor.org/info/rfc3176 | |
| RFC3177;RFC6177;IAB and IESG;IAB/IESG Recommendations on IPv6 Address Allocations to Sites;;;;;RFC 3177;DOI 10.17487/RFC3177;September;https://www.rfc-editor.org/info/rfc3177 | |
| RFC3178;;Hagino, J. and H. Snyder;IPv6 Multihoming Support at Site Exit Routers;;;;;RFC 3178;DOI 10.17487/RFC3178;October;https://www.rfc-editor.org/info/rfc3178 | |
| RFC3179;;Schoenwaelder, J. and J. Quittek;Script MIB Extensibility Protocol Version 1.1;;;;;RFC 3179;DOI 10.17487/RFC3179;October;https://www.rfc-editor.org/info/rfc3179 | |
| RFC3180;;Meyer, D. and P. Lothberg;GLOP Addressing in 233/8;;;BCP 53;;RFC 3180;DOI 10.17487/RFC3180;September;https://www.rfc-editor.org/info/rfc3180 | |
| RFC3181;;Herzog, S.;Signaled Preemption Priority Policy Element;;;;;RFC 3181;DOI 10.17487/RFC3181;October;https://www.rfc-editor.org/info/rfc3181 | |
| RFC3182;;Yadav, S., Yavatkar, R., Pabbati, R., Ford, P., Moore, T., Herzog, S., and R. Hess;Identity Representation for RSVP;;;;;RFC 3182;DOI 10.17487/RFC3182;October;https://www.rfc-editor.org/info/rfc3182 | |
| RFC3183;;Dean, T. and W. Ottaway;Domain Security Services using S/MIME;;;;;RFC 3183;DOI 10.17487/RFC3183;October;https://www.rfc-editor.org/info/rfc3183 | |
| RFC3184;RFC7154;Harris, S.;IETF Guidelines for Conduct;;;;;RFC 3184;DOI 10.17487/RFC3184;October;https://www.rfc-editor.org/info/rfc3184 | |
| RFC3185;;Farrell, S. and S. Turner;Reuse of CMS Content Encryption Keys;;;;;RFC 3185;DOI 10.17487/RFC3185;October;https://www.rfc-editor.org/info/rfc3185 | |
| RFC3186;;Shimizu, S., Kawano, T., Murakami, K., and E. Beier;MAPOS/PPP Tunneling mode;;;;;RFC 3186;DOI 10.17487/RFC3186;December;https://www.rfc-editor.org/info/rfc3186 | |
| RFC3187;RFC8254;Hakala, J. and H. Walravens;Using International Standard Book Numbers as Uniform Resource Names;;;;;RFC 3187;DOI 10.17487/RFC3187;October;https://www.rfc-editor.org/info/rfc3187 | |
| RFC3188;RFC8458;Hakala, J.;Using National Bibliography Numbers as Uniform Resource Names;;;;;RFC 3188;DOI 10.17487/RFC3188;October;https://www.rfc-editor.org/info/rfc3188 | |
| RFC3189;RFC6469;Kobayashi, K., Ogawa, A., Casner, S., and C. Bormann;RTP Payload Format for DV (IEC 61834) Video;;;;;RFC 3189;DOI 10.17487/RFC3189;January;https://www.rfc-editor.org/info/rfc3189 | |
| RFC3190;;Kobayashi, K., Ogawa, A., Casner, S., and C. Bormann;RTP Payload Format for 12-bit DAT Audio and 20- and 24-bit Linear Sampled Audio;;;;;RFC 3190;DOI 10.17487/RFC3190;January;https://www.rfc-editor.org/info/rfc3190 | |
| RFC3191;;Allocchio, C.;Minimal GSTN address format in Internet Mail;;;;;RFC 3191;DOI 10.17487/RFC3191;October;https://www.rfc-editor.org/info/rfc3191 | |
| RFC3192;;Allocchio, C.;Minimal FAX address format in Internet Mail;;;;;RFC 3192;DOI 10.17487/RFC3192;October;https://www.rfc-editor.org/info/rfc3192 | |
| RFC3193;;Patel, B., Aboba, B., Dixon, W., Zorn, G., and S. Booth;Securing L2TP using IPsec;;;;;RFC 3193;DOI 10.17487/RFC3193;November;https://www.rfc-editor.org/info/rfc3193 | |
| RFC3194;;Durand, A. and C. Huitema;The H-Density Ratio for Address Assignment Efficiency An Update on the H ratio;;;;;RFC 3194;DOI 10.17487/RFC3194;November;https://www.rfc-editor.org/info/rfc3194 | |
| RFC3195;;New, D. and M. Rose;Reliable Delivery for syslog;;;;;RFC 3195;DOI 10.17487/RFC3195;November;https://www.rfc-editor.org/info/rfc3195 | |
| RFC3196;;Hastings, T., Manros, C., Zehler, P., Kugler, C., and H. Holst;Internet Printing Protocol/1.1: Implementor's Guide;;;;;RFC 3196;DOI 10.17487/RFC3196;November;https://www.rfc-editor.org/info/rfc3196 | |
| RFC3197;;Austein, R.;Applicability Statement for DNS MIB Extensions;;;;;RFC 3197;DOI 10.17487/RFC3197;November;https://www.rfc-editor.org/info/rfc3197 | |
| RFC3198;;Westerinen, A., Schnizlein, J., Strassner, J., Scherling, M., Quinn, B., Herzog, S., Huynh, A., Carlson, M., Perry, J., and S. Waldbusser;Terminology for Policy-Based Management;;;;;RFC 3198;DOI 10.17487/RFC3198;November;https://www.rfc-editor.org/info/rfc3198 | |
| RFC3199;;Ginoza, S.;Request for Comments Summary RFC Numbers 3100-3199;;;;;RFC 3199;DOI 10.17487/RFC3199;February;https://www.rfc-editor.org/info/rfc3199 | |
| RFC3201;;Steinberger, R. and O. Nicklass;Definitions of Managed Objects for Circuit to Interface Translation;;;;;RFC 3201;DOI 10.17487/RFC3201;January;https://www.rfc-editor.org/info/rfc3201 | |
| RFC3202;;Steinberger, R. and O. Nicklass;Definitions of Managed Objects for Frame Relay Service Level Definitions;;;;;RFC 3202;DOI 10.17487/RFC3202;January;https://www.rfc-editor.org/info/rfc3202 | |
| RFC3203;;T'Joens, Y., Hublet, C., and P. De Schrijver;DHCP reconfigure extension;;;;;RFC 3203;DOI 10.17487/RFC3203;December;https://www.rfc-editor.org/info/rfc3203 | |
| RFC3204;;Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet, F., Watson, M., and M. Zonoun;MIME media types for ISUP and QSIG Objects;;;;;RFC 3204;DOI 10.17487/RFC3204;December;https://www.rfc-editor.org/info/rfc3204 | |
| RFC3205;;Moore, K.;On the use of HTTP as a Substrate;;;BCP 56;;RFC 3205;DOI 10.17487/RFC3205;February;https://www.rfc-editor.org/info/rfc3205 | |
| RFC3206;;Gellens, R.;The SYS and AUTH POP Response Codes;;;;;RFC 3206;DOI 10.17487/RFC3206;February;https://www.rfc-editor.org/info/rfc3206 | |
| RFC3207;;Hoffman, P.;SMTP Service Extension for Secure SMTP over Transport Layer Security;;;;;RFC 3207;DOI 10.17487/RFC3207;February;https://www.rfc-editor.org/info/rfc3207 | |
| RFC3208;;Speakman, T., Crowcroft, J., Gemmell, J., Farinacci, D., Lin, S., Leshchiner, D., Luby, M., Montgomery, T., Rizzo, L., Tweedly, A., Bhaskar, N., Edmonstone, R., Sumanasekera, R., and L. Vicisano;PGM Reliable Transport Protocol Specification;;;;;RFC 3208;DOI 10.17487/RFC3208;December;https://www.rfc-editor.org/info/rfc3208 | |
| RFC3209;;Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., and G. Swallow;RSVP-TE: Extensions to RSVP for LSP Tunnels;;;;;RFC 3209;DOI 10.17487/RFC3209;December;https://www.rfc-editor.org/info/rfc3209 | |
| RFC3210;;Awduche, D., Hannan, A., and X. Xiao;Applicability Statement for Extensions to RSVP for LSP-Tunnels;;;;;RFC 3210;DOI 10.17487/RFC3210;December;https://www.rfc-editor.org/info/rfc3210 | |
| RFC3211;RFC3369, RFC3370;Gutmann, P.;Password-based Encryption for CMS;;;;;RFC 3211;DOI 10.17487/RFC3211;December;https://www.rfc-editor.org/info/rfc3211 | |
| RFC3212;;Jamoussi, B., Ed., Andersson, L., Callon, R., Dantu, R., Wu, L., Doolan, P., Worster, T., Feldman, N., Fredette, A., Girish, M., Gray, E., Heinanen, J., Kilty, T., and A. Malis;Constraint-Based LSP Setup using LDP;;;;;RFC 3212;DOI 10.17487/RFC3212;January;https://www.rfc-editor.org/info/rfc3212 | |
| RFC3213;;Ash, J., Girish, M., Gray, E., Jamoussi, B., and G. Wright;Applicability Statement for CR-LDP;;;;;RFC 3213;DOI 10.17487/RFC3213;January;https://www.rfc-editor.org/info/rfc3213 | |
| RFC3214;;Ash, J., Lee, Y., Ashwood-Smith, P., Jamoussi, B., Fedyk, D., Skalecki, D., and L. Li;LSP Modification Using CR-LDP;;;;;RFC 3214;DOI 10.17487/RFC3214;January;https://www.rfc-editor.org/info/rfc3214 | |
| RFC3215;;Boscher, C., Cheval, P., Wu, L., and E. Gray;LDP State Machine;;;;;RFC 3215;DOI 10.17487/RFC3215;January;https://www.rfc-editor.org/info/rfc3215 | |
| RFC3216;;Elliott, C., Harrington, D., Jason, J., Schoenwaelder, J., Strauss, F., and W. Weiss;SMIng Objectives;;;;;RFC 3216;DOI 10.17487/RFC3216;December;https://www.rfc-editor.org/info/rfc3216 | |
| RFC3217;;Housley, R.;Triple-DES and RC2 Key Wrapping;;;;;RFC 3217;DOI 10.17487/RFC3217;December;https://www.rfc-editor.org/info/rfc3217 | |
| RFC3218;;Rescorla, E.;Preventing the Million Message Attack on Cryptographic Message Syntax;;;;;RFC 3218;DOI 10.17487/RFC3218;January;https://www.rfc-editor.org/info/rfc3218 | |
| RFC3219;;Rosenberg, J., Salama, H., and M. Squire;Telephony Routing over IP (TRIP);;;;;RFC 3219;DOI 10.17487/RFC3219;January;https://www.rfc-editor.org/info/rfc3219 | |
| RFC3220;RFC3344;Perkins, C., Ed.;IP Mobility Support for IPv4;;;;;RFC 3220;DOI 10.17487/RFC3220;January;https://www.rfc-editor.org/info/rfc3220 | |
| RFC3221;;Huston, G.;Commentary on Inter-Domain Routing in the Internet;;;;;RFC 3221;DOI 10.17487/RFC3221;December;https://www.rfc-editor.org/info/rfc3221 | |
| RFC3222;;Trotter, G.;Terminology for Forwarding Information Base (FIB) based Router Performance;;;;;RFC 3222;DOI 10.17487/RFC3222;December;https://www.rfc-editor.org/info/rfc3222 | |
| RFC3224;;Guttman, E.;Vendor Extensions for Service Location Protocol, Version 2;;;;;RFC 3224;DOI 10.17487/RFC3224;January;https://www.rfc-editor.org/info/rfc3224 | |
| RFC3225;;Conrad, D.;Indicating Resolver Support of DNSSEC;;;;;RFC 3225;DOI 10.17487/RFC3225;December;https://www.rfc-editor.org/info/rfc3225 | |
| RFC3226;;Gudmundsson, O.;DNSSEC and IPv6 A6 aware server/resolver message size requirements;;;;;RFC 3226;DOI 10.17487/RFC3226;December;https://www.rfc-editor.org/info/rfc3226 | |
| RFC3227;;Brezinski, D. and T. Killalea;Guidelines for Evidence Collection and Archiving;;;BCP 55;;RFC 3227;DOI 10.17487/RFC3227;February;https://www.rfc-editor.org/info/rfc3227 | |
| RFC3228;;Fenner, B.;IANA Considerations for IPv4 Internet Group Management Protocol (IGMP);;;BCP 57;;RFC 3228;DOI 10.17487/RFC3228;February;https://www.rfc-editor.org/info/rfc3228 | |
| RFC3229;;Mogul, J., Krishnamurthy, B., Douglis, F., Feldmann, A., Goland, Y., van Hoff, A., and D. Hellerstein;Delta encoding in HTTP;;;;;RFC 3229;DOI 10.17487/RFC3229;January;https://www.rfc-editor.org/info/rfc3229 | |
| RFC3230;;Mogul, J. and A. Van Hoff;Instance Digests in HTTP;;;;;RFC 3230;DOI 10.17487/RFC3230;January;https://www.rfc-editor.org/info/rfc3230 | |
| RFC3231;;Levi, D. and J. Schoenwaelder;Definitions of Managed Objects for Scheduling Management Operations;;;;;RFC 3231;DOI 10.17487/RFC3231;January;https://www.rfc-editor.org/info/rfc3231 | |
| RFC3232;;Reynolds, J., Ed.;Assigned Numbers: RFC 1700 is Replaced by an On-line Database;;;;;RFC 3232;DOI 10.17487/RFC3232;January;https://www.rfc-editor.org/info/rfc3232 | |
| RFC3233;;Hoffman, P. and S. Bradner;Defining the IETF;;;BCP 58;;RFC 3233;DOI 10.17487/RFC3233;February;https://www.rfc-editor.org/info/rfc3233 | |
| RFC3234;;Carpenter, B. and S. Brim;Middleboxes: Taxonomy and Issues;;;;;RFC 3234;DOI 10.17487/RFC3234;February;https://www.rfc-editor.org/info/rfc3234 | |
| RFC3235;;Senie, D.;Network Address Translator (NAT)-Friendly Application Design Guidelines;;;;;RFC 3235;DOI 10.17487/RFC3235;January;https://www.rfc-editor.org/info/rfc3235 | |
| RFC3236;;Baker, M. and P. Stark;The 'application/xhtml+xml' Media Type;;;;;RFC 3236;DOI 10.17487/RFC3236;January;https://www.rfc-editor.org/info/rfc3236 | |
| RFC3237;;Tuexen, M., Xie, Q., Stewart, R., Shore, M., Ong, L., Loughney, J., and M. Stillman;Requirements for Reliable Server Pooling;;;;;RFC 3237;DOI 10.17487/RFC3237;January;https://www.rfc-editor.org/info/rfc3237 | |
| RFC3238;;Floyd, S. and L. Daigle;IAB Architectural and Policy Considerations for Open Pluggable Edge Services;;;;;RFC 3238;DOI 10.17487/RFC3238;January;https://www.rfc-editor.org/info/rfc3238 | |
| RFC3239;;Kugler, C., Lewis, H., and T. Hastings;Internet Printing Protocol (IPP): Requirements for Job, Printer, and Device Administrative Operations;;;;;RFC 3239;DOI 10.17487/RFC3239;February;https://www.rfc-editor.org/info/rfc3239 | |
| RFC3240;;Clunie, D. and E. Cordonnier;Digital Imaging and Communications in Medicine (DICOM) - Application/dicom MIME Sub-type Registration;;;;;RFC 3240;DOI 10.17487/RFC3240;February;https://www.rfc-editor.org/info/rfc3240 | |
| RFC3241;;Bormann, C.;Robust Header Compression (ROHC) over PPP;;;;;RFC 3241;DOI 10.17487/RFC3241;April;https://www.rfc-editor.org/info/rfc3241 | |
| RFC3242;RFC4362;Jonsson, L-E. and G. Pelletier;RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTP;;;;;RFC 3242;DOI 10.17487/RFC3242;April;https://www.rfc-editor.org/info/rfc3242 | |
| RFC3243;;Jonsson, L-E.;RObust Header Compression (ROHC): Requirements and Assumptions for 0-byte IP/UDP/RTP Compression;;;;;RFC 3243;DOI 10.17487/RFC3243;April;https://www.rfc-editor.org/info/rfc3243 | |
| RFC3244;;Swift, M., Trostle, J., and J. Brezak;Microsoft Windows 2000 Kerberos Change Password and Set Password Protocols;;;;;RFC 3244;DOI 10.17487/RFC3244;February;https://www.rfc-editor.org/info/rfc3244 | |
| RFC3245;;Klensin, J., Ed., and IAB;The History and Context of Telephone Number Mapping (ENUM) Operational Decisions: Informational Documents Contributed to ITU-T Study Group 2 (SG2);;;;;RFC 3245;DOI 10.17487/RFC3245;March;https://www.rfc-editor.org/info/rfc3245 | |
| RFC3246;;Davie, B., Charny, A., Bennet, J., Benson, K., Le Boudec, J., Courtney, W., Davari, S., Firoiu, V., and D. Stiliadis;An Expedited Forwarding PHB (Per-Hop Behavior);;;;;RFC 3246;DOI 10.17487/RFC3246;March;https://www.rfc-editor.org/info/rfc3246 | |
| RFC3247;;Charny, A., Bennet, J., Benson, K., Boudec, J., Chiu, A., Courtney, W., Davari, S., Firoiu, V., Kalmanek, C., and K. Ramakrishnan;Supplemental Information for the New Definition of the EF PHB (Expedited Forwarding Per-Hop Behavior);;;;;RFC 3247;DOI 10.17487/RFC3247;March;https://www.rfc-editor.org/info/rfc3247 | |
| RFC3248;;Armitage, G., Carpenter, B., Casati, A., Crowcroft, J., Halpern, J., Kumar, B., and J. Schnizlein;A Delay Bound alternative revision of RFC 2598;;;;;RFC 3248;DOI 10.17487/RFC3248;March;https://www.rfc-editor.org/info/rfc3248 | |
| RFC3249;;Cancio, V., Moldovan, M., Tamura, H., and D. Wing;Implementers Guide for Facsimile Using Internet Mail;;;;;RFC 3249;DOI 10.17487/RFC3249;September;https://www.rfc-editor.org/info/rfc3249 | |
| RFC3250;RFC3950;McIntyre, L., Parsons, G., and J. Rafferty;Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type Registration;;;;;RFC 3250;DOI 10.17487/RFC3250;September;https://www.rfc-editor.org/info/rfc3250 | |
| RFC3251;;Rajagopalan, B.;Electricity over IP;;;;;RFC 3251;DOI 10.17487/RFC3251;April;https://www.rfc-editor.org/info/rfc3251 | |
| RFC3252;;Kennedy, H.;Binary Lexical Octet Ad-hoc Transport;;;;;RFC 3252;DOI 10.17487/RFC3252;April;https://www.rfc-editor.org/info/rfc3252 | |
| RFC3253;;Clemm, G., Amsden, J., Ellison, T., Kaler, C., and J. Whitehead;Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning);;;;;RFC 3253;DOI 10.17487/RFC3253;March;https://www.rfc-editor.org/info/rfc3253 | |
| RFC3254;;Alvestrand, H.;Definitions for talking about directories;;;;;RFC 3254;DOI 10.17487/RFC3254;April;https://www.rfc-editor.org/info/rfc3254 | |
| RFC3255;;Jones, N. and C. Murton;Extending Point-to-Point Protocol (PPP) over Synchronous Optical NETwork/Synchronous Digital Hierarchy (SONET/SDH) with virtual concatenation, high order and low order payloads;;;;;RFC 3255;DOI 10.17487/RFC3255;April;https://www.rfc-editor.org/info/rfc3255 | |
| RFC3256;;Jones, D. and R. Woundy;The DOCSIS (Data-Over-Cable Service Interface Specifications) Device Class DHCP (Dynamic Host Configuration Protocol) Relay Agent Information Sub-option;;;;;RFC 3256;DOI 10.17487/RFC3256;April;https://www.rfc-editor.org/info/rfc3256 | |
| RFC3257;;Coene, L.;Stream Control Transmission Protocol Applicability Statement;;;;;RFC 3257;DOI 10.17487/RFC3257;April;https://www.rfc-editor.org/info/rfc3257 | |
| RFC3258;;Hardie, T.;Distributing Authoritative Name Servers via Shared Unicast Addresses;;;;;RFC 3258;DOI 10.17487/RFC3258;April;https://www.rfc-editor.org/info/rfc3258 | |
| RFC3259;;Ott, J., Perkins, C., and D. Kutscher;A Message Bus for Local Coordination;;;;;RFC 3259;DOI 10.17487/RFC3259;April;https://www.rfc-editor.org/info/rfc3259 | |
| RFC3260;;Grossman, D.;New Terminology and Clarifications for Diffserv;;;;;RFC 3260;DOI 10.17487/RFC3260;April;https://www.rfc-editor.org/info/rfc3260 | |
| RFC3261;;Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M., and E. Schooler;SIP: Session Initiation Protocol;;;;;RFC 3261;DOI 10.17487/RFC3261;June;https://www.rfc-editor.org/info/rfc3261 | |
| RFC3262;;Rosenberg, J. and H. Schulzrinne;Reliability of Provisional Responses in Session Initiation Protocol (SIP);;;;;RFC 3262;DOI 10.17487/RFC3262;June;https://www.rfc-editor.org/info/rfc3262 | |
| RFC3263;;Rosenberg, J. and H. Schulzrinne;Session Initiation Protocol (SIP): Locating SIP Servers;;;;;RFC 3263;DOI 10.17487/RFC3263;June;https://www.rfc-editor.org/info/rfc3263 | |
| RFC3264;;Rosenberg, J. and H. Schulzrinne;An Offer/Answer Model with Session Description Protocol (SDP);;;;;RFC 3264;DOI 10.17487/RFC3264;June;https://www.rfc-editor.org/info/rfc3264 | |
| RFC3265;RFC6665;Roach, A.;Session Initiation Protocol (SIP)-Specific Event Notification;;;;;RFC 3265;DOI 10.17487/RFC3265;June;https://www.rfc-editor.org/info/rfc3265 | |
| RFC3266;RFC4566;Olson, S., Camarillo, G., and A. Roach;Support for IPv6 in Session Description Protocol (SDP);;;;;RFC 3266;DOI 10.17487/RFC3266;June;https://www.rfc-editor.org/info/rfc3266 | |
| RFC3267;RFC4867;Sjoberg, J., Westerlund, M., Lakaniemi, A., and Q. Xie;Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs;;;;;RFC 3267;DOI 10.17487/RFC3267;June;https://www.rfc-editor.org/info/rfc3267 | |
| RFC3268;RFC5246;Chown, P.;Advanced Encryption Standard (AES) Ciphersuites for Transport Layer Security (TLS);;;;;RFC 3268;DOI 10.17487/RFC3268;June;https://www.rfc-editor.org/info/rfc3268 | |
| RFC3269;;Kermode, R. and L. Vicisano;Author Guidelines for Reliable Multicast Transport (RMT) Building Blocks and Protocol Instantiation documents;;;;;RFC 3269;DOI 10.17487/RFC3269;April;https://www.rfc-editor.org/info/rfc3269 | |
| RFC3270;;Le Faucheur, F., Wu, L., Davie, B., Davari, S., Vaananen, P., Krishnan, R., Cheval, P., and J. Heinanen;Multi-Protocol Label Switching (MPLS) Support of Differentiated Services;;;;;RFC 3270;DOI 10.17487/RFC3270;May;https://www.rfc-editor.org/info/rfc3270 | |
| RFC3271;;Cerf, V.;The Internet is for Everyone;;;;;RFC 3271;DOI 10.17487/RFC3271;April;https://www.rfc-editor.org/info/rfc3271 | |
| RFC3272;;Awduche, D., Chiu, A., Elwalid, A., Widjaja, I., and X. Xiao;Overview and Principles of Internet Traffic Engineering;;;;;RFC 3272;DOI 10.17487/RFC3272;May;https://www.rfc-editor.org/info/rfc3272 | |
| RFC3273;;Waldbusser, S.;Remote Network Monitoring Management Information Base for High Capacity Networks;;;;;RFC 3273;DOI 10.17487/RFC3273;July;https://www.rfc-editor.org/info/rfc3273 | |
| RFC3274;;Gutmann, P.;Compressed Data Content Type for Cryptographic Message Syntax (CMS);;;;;RFC 3274;DOI 10.17487/RFC3274;June;https://www.rfc-editor.org/info/rfc3274 | |
| RFC3275;;Eastlake 3rd, D., Reagle, J., and D. Solo;(Extensible Markup Language) XML-Signature Syntax and Processing;;;;;RFC 3275;DOI 10.17487/RFC3275;March;https://www.rfc-editor.org/info/rfc3275 | |
| RFC3276;RFC4319;Ray, B. and R. Abbi;Definitions of Managed Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair High-Speed Digital Subscriber Line (SHDSL) Lines Processing;;;;;RFC 3276;DOI 10.17487/RFC3276;May;https://www.rfc-editor.org/info/rfc3276 | |
| RFC3277;;McPherson, D.;Intermediate System to Intermediate System (IS-IS) Transient Blackhole Avoidance;;;;;RFC 3277;DOI 10.17487/RFC3277;April;https://www.rfc-editor.org/info/rfc3277 | |
| RFC3278;RFC5753;Blake-Wilson, S., Brown, D., and P. Lambert;Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS);;;;;RFC 3278;DOI 10.17487/RFC3278;April;https://www.rfc-editor.org/info/rfc3278 | |
| RFC3279;;Bassham, L., Polk, W., and R. Housley;Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile;;;;;RFC 3279;DOI 10.17487/RFC3279;April;https://www.rfc-editor.org/info/rfc3279 | |
| RFC3280;RFC5280;Housley, R., Polk, W., Ford, W., and D. Solo;Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile;;;;;RFC 3280;DOI 10.17487/RFC3280;April;https://www.rfc-editor.org/info/rfc3280 | |
| RFC3281;RFC5755;Farrell, S. and R. Housley;An Internet Attribute Certificate Profile for Authorization;;;;;RFC 3281;DOI 10.17487/RFC3281;April;https://www.rfc-editor.org/info/rfc3281 | |
| RFC3282;;Alvestrand, H.;Content Language Headers;;;;;RFC 3282;DOI 10.17487/RFC3282;May;https://www.rfc-editor.org/info/rfc3282 | |
| RFC3283;;Mahoney, B., Babics, G., and A. Taler;Guide to Internet Calendaring;;;;;RFC 3283;DOI 10.17487/RFC3283;June;https://www.rfc-editor.org/info/rfc3283 | |
| RFC3284;;Korn, D., MacDonald, J., Mogul, J., and K. Vo;The VCDIFF Generic Differencing and Compression Data Format;;;;;RFC 3284;DOI 10.17487/RFC3284;June;https://www.rfc-editor.org/info/rfc3284 | |
| RFC3285;RFC5385;Gahrns, M. and T. Hain;Using Microsoft Word to create Internet Drafts and RFCs;;;;;RFC 3285;DOI 10.17487/RFC3285;May;https://www.rfc-editor.org/info/rfc3285 | |
| RFC3286;;Ong, L. and J. Yoakum;An Introduction to the Stream Control Transmission Protocol (SCTP);;;;;RFC 3286;DOI 10.17487/RFC3286;May;https://www.rfc-editor.org/info/rfc3286 | |
| RFC3287;;Bierman, A.;Remote Monitoring MIB Extensions for Differentiated Services;;;;;RFC 3287;DOI 10.17487/RFC3287;July;https://www.rfc-editor.org/info/rfc3287 | |
| RFC3288;RFC4227;O'Tuathail, E. and M. Rose;Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP);;;;;RFC 3288;DOI 10.17487/RFC3288;June;https://www.rfc-editor.org/info/rfc3288 | |
| RFC3289;;Baker, F., Chan, K., and A. Smith;Management Information Base for the Differentiated Services Architecture;;;;;RFC 3289;DOI 10.17487/RFC3289;May;https://www.rfc-editor.org/info/rfc3289 | |
| RFC3290;;Bernet, Y., Blake, S., Grossman, D., and A. Smith;An Informal Management Model for Diffserv Routers;;;;;RFC 3290;DOI 10.17487/RFC3290;May;https://www.rfc-editor.org/info/rfc3290 | |
| RFC3291;RFC4001;Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder;Textual Conventions for Internet Network Addresses;;;;;RFC 3291;DOI 10.17487/RFC3291;May;https://www.rfc-editor.org/info/rfc3291 | |
| RFC3292;;Doria, A., Hellstrand, F., Sundell, K., and T. Worster;General Switch Management Protocol (GSMP) V3;;;;;RFC 3292;DOI 10.17487/RFC3292;June;https://www.rfc-editor.org/info/rfc3292 | |
| RFC3293;;Worster, T., Doria, A., and J. Buerkle;General Switch Management Protocol (GSMP) Packet Encapsulations for Asynchronous Transfer Mode (ATM), Ethernet and Transmission Control Protocol (TCP);;;;;RFC 3293;DOI 10.17487/RFC3293;June;https://www.rfc-editor.org/info/rfc3293 | |
| RFC3294;;Doria, A. and K. Sundell;General Switch Management Protocol (GSMP) Applicability;;;;;RFC 3294;DOI 10.17487/RFC3294;June;https://www.rfc-editor.org/info/rfc3294 | |
| RFC3295;;Sjostrand, H., Buerkle, J., and B. Srinivasan;Definitions of Managed Objects for the General Switch Management Protocol (GSMP);;;;;RFC 3295;DOI 10.17487/RFC3295;June;https://www.rfc-editor.org/info/rfc3295 | |
| RFC3296;;Zeilenga, K.;Named Subordinate References in Lightweight Directory Access Protocol (LDAP) Directories;;;;;RFC 3296;DOI 10.17487/RFC3296;July;https://www.rfc-editor.org/info/rfc3296 | |
| RFC3297;;Klyne, G., Iwazaki, R., and D. Crocker;Content Negotiation for Messaging Services based on Email;;;;;RFC 3297;DOI 10.17487/RFC3297;July;https://www.rfc-editor.org/info/rfc3297 | |
| RFC3298;;Faynberg, I., Gato, J., Lu, H., and L. Slutsman;Service in the Public Switched Telephone Network/Intelligent Network (PSTN/IN) Requesting InTernet Service (SPIRITS) Protocol Requirements;;;;;RFC 3298;DOI 10.17487/RFC3298;August;https://www.rfc-editor.org/info/rfc3298 | |
| RFC3299;;Ginoza, S.;Request for Comments Summary RFC Numbers 3200-3299;;;;;RFC 3299;DOI 10.17487/RFC3299;December;https://www.rfc-editor.org/info/rfc3299 | |
| RFC3300;RFC3600;Reynolds, J., Braden, R., Ginoza, S., and A. De La Cruz;Internet Official Protocol Standards;;;;;RFC 3300;DOI 10.17487/RFC3300;November;https://www.rfc-editor.org/info/rfc3300 | |
| RFC3301;;T'Joens, Y., Crivellari, P., and B. Sales;Layer Two Tunnelling Protocol (L2TP): ATM access network extensions;;;;;RFC 3301;DOI 10.17487/RFC3301;June;https://www.rfc-editor.org/info/rfc3301 | |
| RFC3302;;Parsons, G. and J. Rafferty;Tag Image File Format (TIFF) - image/tiff MIME Sub-type Registration;;;;;RFC 3302;DOI 10.17487/RFC3302;September;https://www.rfc-editor.org/info/rfc3302 | |
| RFC3303;;Srisuresh, P., Kuthan, J., Rosenberg, J., Molitor, A., and A. Rayhan;Middlebox communication architecture and framework;;;;;RFC 3303;DOI 10.17487/RFC3303;August;https://www.rfc-editor.org/info/rfc3303 | |
| RFC3304;;Swale, R., Mart, P., Sijben, P., Brim, S., and M. Shore;Middlebox Communications (midcom) Protocol Requirements;;;;;RFC 3304;DOI 10.17487/RFC3304;August;https://www.rfc-editor.org/info/rfc3304 | |
| RFC3305;;Mealling, M., Ed., and R. Denenberg, Ed.;Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations;;;;;RFC 3305;DOI 10.17487/RFC3305;August;https://www.rfc-editor.org/info/rfc3305 | |
| RFC3306;;Haberman, B. and D. Thaler;Unicast-Prefix-based IPv6 Multicast Addresses;;;;;RFC 3306;DOI 10.17487/RFC3306;August;https://www.rfc-editor.org/info/rfc3306 | |
| RFC3307;;Haberman, B.;Allocation Guidelines for IPv6 Multicast Addresses;;;;;RFC 3307;DOI 10.17487/RFC3307;August;https://www.rfc-editor.org/info/rfc3307 | |
| RFC3308;;Calhoun, P., Luo, W., McPherson, D., and K. Peirce;Layer Two Tunneling Protocol (L2TP) Differentiated Services Extension;;;;;RFC 3308;DOI 10.17487/RFC3308;November;https://www.rfc-editor.org/info/rfc3308 | |
| RFC3309;RFC4960;Stone, J., Stewart, R., and D. Otis;Stream Control Transmission Protocol (SCTP) Checksum Change;;;;;RFC 3309;DOI 10.17487/RFC3309;September;https://www.rfc-editor.org/info/rfc3309 | |
| RFC3310;;Niemi, A., Arkko, J., and V. Torvinen;Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA);;;;;RFC 3310;DOI 10.17487/RFC3310;September;https://www.rfc-editor.org/info/rfc3310 | |
| RFC3311;;Rosenberg, J.;The Session Initiation Protocol (SIP) UPDATE Method;;;;;RFC 3311;DOI 10.17487/RFC3311;October;https://www.rfc-editor.org/info/rfc3311 | |
| RFC3312;;Camarillo, G., Ed., Marshall, W., Ed., and J. Rosenberg;Integration of Resource Management and Session Initiation Protocol (SIP);;;;;RFC 3312;DOI 10.17487/RFC3312;October;https://www.rfc-editor.org/info/rfc3312 | |
| RFC3313;;Marshall, W., Ed.;Private Session Initiation Protocol (SIP) Extensions for Media Authorization;;;;;RFC 3313;DOI 10.17487/RFC3313;January;https://www.rfc-editor.org/info/rfc3313 | |
| RFC3314;;Wasserman, M., Ed.;Recommendations for IPv6 in Third Generation Partnership Project (3GPP) Standards;;;;;RFC 3314;DOI 10.17487/RFC3314;September;https://www.rfc-editor.org/info/rfc3314 | |
| RFC3315;RFC8415;Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney;Dynamic Host Configuration Protocol for IPv6 (DHCPv6);;;;;RFC 3315;DOI 10.17487/RFC3315;July;https://www.rfc-editor.org/info/rfc3315 | |
| RFC3316;RFC7066;Arkko, J., Kuijpers, G., Soliman, H., Loughney, J., and J. Wiljakka;Internet Protocol Version 6 (IPv6) for Some Second and Third Generation Cellular Hosts;;;;;RFC 3316;DOI 10.17487/RFC3316;April;https://www.rfc-editor.org/info/rfc3316 | |
| RFC3317;;Chan, K., Sahita, R., Hahn, S., and K. McCloghrie;Differentiated Services Quality of Service Policy Information Base;;;;;RFC 3317;DOI 10.17487/RFC3317;March;https://www.rfc-editor.org/info/rfc3317 | |
| RFC3318;;Sahita, R., Ed., Hahn, S., Chan, K., and K. McCloghrie;Framework Policy Information Base;;;;;RFC 3318;DOI 10.17487/RFC3318;March;https://www.rfc-editor.org/info/rfc3318 | |
| RFC3319;;Schulzrinne, H. and B. Volz;Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers;;;;;RFC 3319;DOI 10.17487/RFC3319;July;https://www.rfc-editor.org/info/rfc3319 | |
| RFC3320;;Price, R., Bormann, C., Christoffersson, J., Hannu, H., Liu, Z., and J. Rosenberg;Signaling Compression (SigComp);;;;;RFC 3320;DOI 10.17487/RFC3320;January;https://www.rfc-editor.org/info/rfc3320 | |
| RFC3321;;Hannu, H., Christoffersson, J., Forsgren, S., Leung, K.-C., Liu, Z., and R. Price;Signaling Compression (SigComp) - Extended Operations;;;;;RFC 3321;DOI 10.17487/RFC3321;January;https://www.rfc-editor.org/info/rfc3321 | |
| RFC3322;;Hannu, H.;Signaling Compression (SigComp) Requirements & Assumptions;;;;;RFC 3322;DOI 10.17487/RFC3322;January;https://www.rfc-editor.org/info/rfc3322 | |
| RFC3323;;Peterson, J.;A Privacy Mechanism for the Session Initiation Protocol (SIP);;;;;RFC 3323;DOI 10.17487/RFC3323;November;https://www.rfc-editor.org/info/rfc3323 | |
| RFC3324;;Watson, M.;Short Term Requirements for Network Asserted Identity;;;;;RFC 3324;DOI 10.17487/RFC3324;November;https://www.rfc-editor.org/info/rfc3324 | |
| RFC3325;;Jennings, C., Peterson, J., and M. Watson;Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks;;;;;RFC 3325;DOI 10.17487/RFC3325;November;https://www.rfc-editor.org/info/rfc3325 | |
| RFC3326;;Schulzrinne, H., Oran, D., and G. Camarillo;The Reason Header Field for the Session Initiation Protocol (SIP);;;;;RFC 3326;DOI 10.17487/RFC3326;December;https://www.rfc-editor.org/info/rfc3326 | |
| RFC3327;;Willis, D. and B. Hoeneisen;Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts;;;;;RFC 3327;DOI 10.17487/RFC3327;December;https://www.rfc-editor.org/info/rfc3327 | |
| RFC3329;;Arkko, J., Torvinen, V., Camarillo, G., Niemi, A., and T. Haukka;Security Mechanism Agreement for the Session Initiation Protocol (SIP);;;;;RFC 3329;DOI 10.17487/RFC3329;January;https://www.rfc-editor.org/info/rfc3329 | |
| RFC3330;RFC5735;IANA;Special-Use IPv4 Addresses;;;;;RFC 3330;DOI 10.17487/RFC3330;September;https://www.rfc-editor.org/info/rfc3330 | |
| RFC3331;;Morneault, K., Dantu, R., Sidebottom, G., Bidulock, B., and J. Heitz;Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Adaptation Layer;;;;;RFC 3331;DOI 10.17487/RFC3331;September;https://www.rfc-editor.org/info/rfc3331 | |
| RFC3332;RFC4666;Sidebottom, G., Ed., Morneault, K., Ed., and J. Pastor-Balbas, Ed.;Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA);;;;;RFC 3332;DOI 10.17487/RFC3332;September;https://www.rfc-editor.org/info/rfc3332 | |
| RFC3334;;Zseby, T., Zander, S., and C. Carle;Policy-Based Accounting;;;;;RFC 3334;DOI 10.17487/RFC3334;October;https://www.rfc-editor.org/info/rfc3334 | |
| RFC3335;;Harding, T., Drummond, R., and C. Shih;MIME-based Secure Peer-to-Peer Business Data Interchange over the Internet;;;;;RFC 3335;DOI 10.17487/RFC3335;September;https://www.rfc-editor.org/info/rfc3335 | |
| RFC3336;;Thompson, B., Koren, T., and B. Buffam;PPP Over Asynchronous Transfer Mode Adaptation Layer 2 (AAL2);;;;;RFC 3336;DOI 10.17487/RFC3336;December;https://www.rfc-editor.org/info/rfc3336 | |
| RFC3337;;Thompson, B., Koren, T., and B. Buffam;Class Extensions for PPP over Asynchronous Transfer Mode Adaptation Layer 2;;;;;RFC 3337;DOI 10.17487/RFC3337;December;https://www.rfc-editor.org/info/rfc3337 | |
| RFC3338;RFC6535;Lee, S., Shin, M-K., Kim, Y-J., Nordmark, E., and A. Durand;Dual Stack Hosts Using "Bump-in-the-API" (BIA);;;;;RFC 3338;DOI 10.17487/RFC3338;October;https://www.rfc-editor.org/info/rfc3338 | |
| RFC3339;;Klyne, G. and C. Newman;Date and Time on the Internet: Timestamps;;;;;RFC 3339;DOI 10.17487/RFC3339;July;https://www.rfc-editor.org/info/rfc3339 | |
| RFC3340;;Rose, M., Klyne, G., and D. Crocker;The Application Exchange Core;;;;;RFC 3340;DOI 10.17487/RFC3340;July;https://www.rfc-editor.org/info/rfc3340 | |
| RFC3341;;Rose, M., Klyne, G., and D. Crocker;The Application Exchange (APEX) Access Service;;;;;RFC 3341;DOI 10.17487/RFC3341;July;https://www.rfc-editor.org/info/rfc3341 | |
| RFC3342;;Dixon, E., Franklin, H., Kint, J., Klyne, G., New, D., Pead, S., Rose, M., and M. Schwartz;The Application Exchange (APEX) Option Party Pack, Part Deux!;;;;;RFC 3342;DOI 10.17487/RFC3342;July;https://www.rfc-editor.org/info/rfc3342 | |
| RFC3343;;Rose, M., Klyne, G., and D. Crocker;The Application Exchange (APEX) Presence Service;;;;;RFC 3343;DOI 10.17487/RFC3343;April;https://www.rfc-editor.org/info/rfc3343 | |
| RFC3344;RFC5944;Perkins, C., Ed.;IP Mobility Support for IPv4;;;;;RFC 3344;DOI 10.17487/RFC3344;August;https://www.rfc-editor.org/info/rfc3344 | |
| RFC3345;;McPherson, D., Gill, V., Walton, D., and A. Retana;Border Gateway Protocol (BGP) Persistent Route Oscillation Condition;;;;;RFC 3345;DOI 10.17487/RFC3345;August;https://www.rfc-editor.org/info/rfc3345 | |
| RFC3346;;Boyle, J., Gill, V., Hannan, A., Cooper, D., Awduche, D., Christian, B., and W. Lai;Applicability Statement for Traffic Engineering with MPLS;;;;;RFC 3346;DOI 10.17487/RFC3346;August;https://www.rfc-editor.org/info/rfc3346 | |
| RFC3347;;Krueger, M. and R. Haagens;Small Computer Systems Interface protocol over the Internet (iSCSI) Requirements and Design Considerations;;;;;RFC 3347;DOI 10.17487/RFC3347;July;https://www.rfc-editor.org/info/rfc3347 | |
| RFC3348;;Gahrns, M. and R. Cheng;The Internet Message Action Protocol (IMAP4) Child Mailbox Extension;;;;;RFC 3348;DOI 10.17487/RFC3348;July;https://www.rfc-editor.org/info/rfc3348 | |
| RFC3349;;Rose, M.;A Transient Prefix for Identifying Profiles under Development by the Working Groups of the Internet Engineering Task Force;;;BCP 59;;RFC 3349;DOI 10.17487/RFC3349;July;https://www.rfc-editor.org/info/rfc3349 | |
| RFC3351;;Charlton, N., Gasson, M., Gybels, G., Spanner, M., and A. van Wijk;User Requirements for the Session Initiation Protocol (SIP) in Support of Deaf, Hard of Hearing and Speech-impaired Individuals;;;;;RFC 3351;DOI 10.17487/RFC3351;August;https://www.rfc-editor.org/info/rfc3351 | |
| RFC3352;;Zeilenga, K.;Connection-less Lightweight Directory Access Protocol (CLDAP) to Historic Status;;;;;RFC 3352;DOI 10.17487/RFC3352;March;https://www.rfc-editor.org/info/rfc3352 | |
| RFC3353;;Ooms, D., Sales, B., Livens, W., Acharya, A., Griffoul, F., and F. Ansari;Overview of IP Multicast in a Multi-Protocol Label Switching (MPLS) Environment;;;;;RFC 3353;DOI 10.17487/RFC3353;August;https://www.rfc-editor.org/info/rfc3353 | |
| RFC3354;;Eastlake 3rd, D.;Internet Open Trading Protocol Version 2 Requirements;;;;;RFC 3354;DOI 10.17487/RFC3354;August;https://www.rfc-editor.org/info/rfc3354 | |
| RFC3355;;Singh, A., Turner, R., Tio, R., and S. Nanji;Layer Two Tunnelling Protocol (L2TP) Over ATM Adaptation Layer 5 (AAL5);;;;;RFC 3355;DOI 10.17487/RFC3355;August;https://www.rfc-editor.org/info/rfc3355 | |
| RFC3356;RFC6756;Fishman, G. and S. Bradner;Internet Engineering Task Force and International Telecommunication Union - Telecommunications Standardization Sector Collaboration Guidelines;;;;;RFC 3356;DOI 10.17487/RFC3356;August;https://www.rfc-editor.org/info/rfc3356 | |
| RFC3357;;Koodli, R. and R. Ravikanth;One-way Loss Pattern Sample Metrics;;;;;RFC 3357;DOI 10.17487/RFC3357;August;https://www.rfc-editor.org/info/rfc3357 | |
| RFC3358;;Przygienda, T.;Optional Checksums in Intermediate System to Intermediate System (ISIS);;;;;RFC 3358;DOI 10.17487/RFC3358;August;https://www.rfc-editor.org/info/rfc3358 | |
| RFC3359;;Przygienda, T.;Reserved Type, Length and Value (TLV) Codepoints in Intermediate System to Intermediate System;;;;;RFC 3359;DOI 10.17487/RFC3359;August;https://www.rfc-editor.org/info/rfc3359 | |
| RFC3360;;Floyd, S.;Inappropriate TCP Resets Considered Harmful;;;BCP 60;;RFC 3360;DOI 10.17487/RFC3360;August;https://www.rfc-editor.org/info/rfc3360 | |
| RFC3361;;Schulzrinne, H.;Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers;;;;;RFC 3361;DOI 10.17487/RFC3361;August;https://www.rfc-editor.org/info/rfc3361 | |
| RFC3362;;Parsons, G.;Real-time Facsimile (T.38) - image/t38 MIME Sub-type Registration;;;;;RFC 3362;DOI 10.17487/RFC3362;August;https://www.rfc-editor.org/info/rfc3362 | |
| RFC3363;;Bush, R., Durand, A., Fink, B., Gudmundsson, O., and T. Hain;Representing Internet Protocol version 6 (IPv6) Addresses in the Domain Name System (DNS);;;;;RFC 3363;DOI 10.17487/RFC3363;August;https://www.rfc-editor.org/info/rfc3363 | |
| RFC3364;;Austein, R.;Tradeoffs in Domain Name System (DNS) Support for Internet Protocol version 6 (IPv6);;;;;RFC 3364;DOI 10.17487/RFC3364;August;https://www.rfc-editor.org/info/rfc3364 | |
| RFC3365;;Schiller, J.;Strong Security Requirements for Internet Engineering Task Force Standard Protocols;;;BCP 61;;RFC 3365;DOI 10.17487/RFC3365;August;https://www.rfc-editor.org/info/rfc3365 | |
| RFC3366;;Fairhurst, G. and L. Wood;Advice to link designers on link Automatic Repeat reQuest (ARQ);;;BCP 62;;RFC 3366;DOI 10.17487/RFC3366;August;https://www.rfc-editor.org/info/rfc3366 | |
| RFC3367;;Popp, N., Mealling, M., and M. Moseley;Common Name Resolution Protocol (CNRP);;;;;RFC 3367;DOI 10.17487/RFC3367;August;https://www.rfc-editor.org/info/rfc3367 | |
| RFC3368;;Mealling, M.;The 'go' URI Scheme for the Common Name Resolution Protocol;;;;;RFC 3368;DOI 10.17487/RFC3368;August;https://www.rfc-editor.org/info/rfc3368 | |
| RFC3369;RFC3852;Housley, R.;Cryptographic Message Syntax (CMS);;;;;RFC 3369;DOI 10.17487/RFC3369;August;https://www.rfc-editor.org/info/rfc3369 | |
| RFC3370;;Housley, R.;Cryptographic Message Syntax (CMS) Algorithms;;;;;RFC 3370;DOI 10.17487/RFC3370;August;https://www.rfc-editor.org/info/rfc3370 | |
| RFC3371;;Caves, E., Calhoun, P., and R. Wheeler;Layer Two Tunneling Protocol "L2TP" Management Information Base;;;;;RFC 3371;DOI 10.17487/RFC3371;August;https://www.rfc-editor.org/info/rfc3371 | |
| RFC3372;;Vemuri, A. and J. Peterson;Session Initiation Protocol for Telephones (SIP-T): Context and Architectures;;;BCP 63;;RFC 3372;DOI 10.17487/RFC3372;September;https://www.rfc-editor.org/info/rfc3372 | |
| RFC3373;RFC5303;Katz, D. and R. Saluja;Three-Way Handshake for Intermediate System to Intermediate System (IS-IS) Point-to-Point Adjacencies;;;;;RFC 3373;DOI 10.17487/RFC3373;September;https://www.rfc-editor.org/info/rfc3373 | |
| RFC3374;;Kempf, J., Ed.;Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access Network;;;;;RFC 3374;DOI 10.17487/RFC3374;September;https://www.rfc-editor.org/info/rfc3374 | |
| RFC3375;;Hollenbeck, S.;Generic Registry-Registrar Protocol Requirements;;;;;RFC 3375;DOI 10.17487/RFC3375;September;https://www.rfc-editor.org/info/rfc3375 | |
| RFC3376;;Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. Thyagarajan;Internet Group Management Protocol, Version 3;;;;;RFC 3376;DOI 10.17487/RFC3376;October;https://www.rfc-editor.org/info/rfc3376 | |
| RFC3377;RFC4510;Hodges, J. and R. Morgan;Lightweight Directory Access Protocol (v3): Technical Specification;;;;;RFC 3377;DOI 10.17487/RFC3377;September;https://www.rfc-editor.org/info/rfc3377 | |
| RFC3378;;Housley, R. and S. Hollenbeck;EtherIP: Tunneling Ethernet Frames in IP Datagrams;;;;;RFC 3378;DOI 10.17487/RFC3378;September;https://www.rfc-editor.org/info/rfc3378 | |
| RFC3379;;Pinkas, D. and R. Housley;Delegated Path Validation and Delegated Path Discovery Protocol Requirements;;;;;RFC 3379;DOI 10.17487/RFC3379;September;https://www.rfc-editor.org/info/rfc3379 | |
| RFC3380;;Hastings, T., Herriot, R., Kugler, C., and H. Lewis;Internet Printing Protocol (IPP): Job and Printer Set Operations;;;;;RFC 3380;DOI 10.17487/RFC3380;September;https://www.rfc-editor.org/info/rfc3380 | |
| RFC3381;RFC8011;Hastings, T., Lewis, H., and R. Bergman;Internet Printing Protocol (IPP): Job Progress Attributes;;;;;RFC 3381;DOI 10.17487/RFC3381;September;https://www.rfc-editor.org/info/rfc3381 | |
| RFC3382;RFC8010, RFC8011;deBry, R., Hastings, T., Herriot, R., Ocke, K., and P. Zehler;Internet Printing Protocol (IPP): The 'collection' attribute syntax;;;;;RFC 3382;DOI 10.17487/RFC3382;September;https://www.rfc-editor.org/info/rfc3382 | |
| RFC3383;RFC4520;Zeilenga, K.;Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP);;;;;RFC 3383;DOI 10.17487/RFC3383;September;https://www.rfc-editor.org/info/rfc3383 | |
| RFC3384;;Stokes, E., Weiser, R., Moats, R., and R. Huber;Lightweight Directory Access Protocol (version 3) Replication Requirements;;;;;RFC 3384;DOI 10.17487/RFC3384;October;https://www.rfc-editor.org/info/rfc3384 | |
| RFC3385;;Sheinwald, D., Satran, J., Thaler, P., and V. Cavanna;Internet Protocol Small Computer System Interface (iSCSI) Cyclic Redundancy Check (CRC)/Checksum Considerations;;;;;RFC 3385;DOI 10.17487/RFC3385;September;https://www.rfc-editor.org/info/rfc3385 | |
| RFC3386;;Lai, W., Ed., and D. McDysan, Ed.;Network Hierarchy and Multilayer Survivability;;;;;RFC 3386;DOI 10.17487/RFC3386;November;https://www.rfc-editor.org/info/rfc3386 | |
| RFC3387;;Eder, M., Chaskar, H., and S. Nag;Considerations from the Service Management Research Group (SMRG) on Quality of Service (QoS) in the IP Network;;;;;RFC 3387;DOI 10.17487/RFC3387;September;https://www.rfc-editor.org/info/rfc3387 | |
| RFC3388;RFC5888;Camarillo, G., Eriksson, G., Holler, J., and H. Schulzrinne;Grouping of Media Lines in the Session Description Protocol (SDP);;;;;RFC 3388;DOI 10.17487/RFC3388;December;https://www.rfc-editor.org/info/rfc3388 | |
| RFC3389;;Zopf, R.;Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN);;;;;RFC 3389;DOI 10.17487/RFC3389;September;https://www.rfc-editor.org/info/rfc3389 | |
| RFC3390;;Allman, M., Floyd, S., and C. Partridge;Increasing TCP's Initial Window;;;;;RFC 3390;DOI 10.17487/RFC3390;October;https://www.rfc-editor.org/info/rfc3390 | |
| RFC3391;;Herriot, R.;The MIME Application/Vnd.pwg-multiplexed Content-Type;;;;;RFC 3391;DOI 10.17487/RFC3391;December;https://www.rfc-editor.org/info/rfc3391 | |
| RFC3392;RFC5492;Chandra, R. and J. Scudder;Capabilities Advertisement with BGP-4;;;;;RFC 3392;DOI 10.17487/RFC3392;November;https://www.rfc-editor.org/info/rfc3392 | |
| RFC3393;;Demichelis, C. and P. Chimento;IP Packet Delay Variation Metric for IP Performance Metrics (IPPM);;;;;RFC 3393;DOI 10.17487/RFC3393;November;https://www.rfc-editor.org/info/rfc3393 | |
| RFC3394;;Schaad, J. and R. Housley;Advanced Encryption Standard (AES) Key Wrap Algorithm;;;;;RFC 3394;DOI 10.17487/RFC3394;September;https://www.rfc-editor.org/info/rfc3394 | |
| RFC3395;;Bierman, A., Bucci, C., Dietz, R., and A. Warth;Remote Network Monitoring MIB Protocol Identifier Reference Extensions;;;;;RFC 3395;DOI 10.17487/RFC3395;September;https://www.rfc-editor.org/info/rfc3395 | |
| RFC3396;;Lemon, T. and S. Cheshire;Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4);;;;;RFC 3396;DOI 10.17487/RFC3396;November;https://www.rfc-editor.org/info/rfc3396 | |
| RFC3397;;Aboba, B. and S. Cheshire;Dynamic Host Configuration Protocol (DHCP) Domain Search Option;;;;;RFC 3397;DOI 10.17487/RFC3397;November;https://www.rfc-editor.org/info/rfc3397 | |
| RFC3398;;Camarillo, G., Roach, A., Peterson, J., and L. Ong;Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping;;;;;RFC 3398;DOI 10.17487/RFC3398;December;https://www.rfc-editor.org/info/rfc3398 | |
| RFC3401;;Mealling, M.;Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS;;;;;RFC 3401;DOI 10.17487/RFC3401;October;https://www.rfc-editor.org/info/rfc3401 | |
| RFC3402;;Mealling, M.;Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm;;;;;RFC 3402;DOI 10.17487/RFC3402;October;https://www.rfc-editor.org/info/rfc3402 | |
| RFC3403;;Mealling, M.;Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database;;;;;RFC 3403;DOI 10.17487/RFC3403;October;https://www.rfc-editor.org/info/rfc3403 | |
| RFC3404;;Mealling, M.;Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI);;;;;RFC 3404;DOI 10.17487/RFC3404;October;https://www.rfc-editor.org/info/rfc3404 | |
| RFC3405;;Mealling, M.;Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARPA Assignment Procedures;;;BCP 65;;RFC 3405;DOI 10.17487/RFC3405;October;https://www.rfc-editor.org/info/rfc3405 | |
| RFC3406;RFC8141;Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom;Uniform Resource Names (URN) Namespace Definition Mechanisms;;;;;RFC 3406;DOI 10.17487/RFC3406;October;https://www.rfc-editor.org/info/rfc3406 | |
| RFC3407;;Andreasen, F.;Session Description Protocol (SDP) Simple Capability Declaration;;;;;RFC 3407;DOI 10.17487/RFC3407;October;https://www.rfc-editor.org/info/rfc3407 | |
| RFC3408;;Liu, Z. and K. Le;Zero-byte Support for Bidirectional Reliable Mode (R-mode) in Extended Link-Layer Assisted RObust Header Compression (ROHC) Profile;;;;;RFC 3408;DOI 10.17487/RFC3408;December;https://www.rfc-editor.org/info/rfc3408 | |
| RFC3409;;Svanbro, K.;Lower Layer Guidelines for Robust RTP/UDP/IP Header Compression;;;;;RFC 3409;DOI 10.17487/RFC3409;December;https://www.rfc-editor.org/info/rfc3409 | |
| RFC3410;;Case, J., Mundy, R., Partain, D., and B. Stewart;Introduction and Applicability Statements for Internet-Standard Management Framework;;;;;RFC 3410;DOI 10.17487/RFC3410;December;https://www.rfc-editor.org/info/rfc3410 | |
| RFC3411;;Harrington, D., Presuhn, R., and B. Wijnen;An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks;;;;STD 62;RFC 3411;DOI 10.17487/RFC3411;December;https://www.rfc-editor.org/info/rfc3411 | |
| RFC3412;;Case, J., Harrington, D., Presuhn, R., and B. Wijnen;Message Processing and Dispatching for the Simple Network Management Protocol (SNMP);;;;STD 62;RFC 3412;DOI 10.17487/RFC3412;December;https://www.rfc-editor.org/info/rfc3412 | |
| RFC3413;;Levi, D., Meyer, P., and B. Stewart;Simple Network Management Protocol (SNMP) Applications;;;;STD 62;RFC 3413;DOI 10.17487/RFC3413;December;https://www.rfc-editor.org/info/rfc3413 | |
| RFC3414;;Blumenthal, U. and B. Wijnen;User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3);;;;STD 62;RFC 3414;DOI 10.17487/RFC3414;December;https://www.rfc-editor.org/info/rfc3414 | |
| RFC3415;;Wijnen, B., Presuhn, R., and K. McCloghrie;View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP);;;;STD 62;RFC 3415;DOI 10.17487/RFC3415;December;https://www.rfc-editor.org/info/rfc3415 | |
| RFC3416;;Presuhn, R., Ed.;Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP);;;;STD 62;RFC 3416;DOI 10.17487/RFC3416;December;https://www.rfc-editor.org/info/rfc3416 | |
| RFC3417;;Presuhn, R., Ed.;Transport Mappings for the Simple Network Management Protocol (SNMP);;;;STD 62;RFC 3417;DOI 10.17487/RFC3417;December;https://www.rfc-editor.org/info/rfc3417 | |
| RFC3418;;Presuhn, R., Ed.;Management Information Base (MIB) for the Simple Network Management Protocol (SNMP);;;;STD 62;RFC 3418;DOI 10.17487/RFC3418;December;https://www.rfc-editor.org/info/rfc3418 | |
| RFC3419;;Daniele, M. and J. Schoenwaelder;Textual Conventions for Transport Addresses;;;;;RFC 3419;DOI 10.17487/RFC3419;December;https://www.rfc-editor.org/info/rfc3419 | |
| RFC3420;;Sparks, R.;Internet Media Type message/sipfrag;;;;;RFC 3420;DOI 10.17487/RFC3420;November;https://www.rfc-editor.org/info/rfc3420 | |
| RFC3421;;Zhao, W., Schulzrinne, H., Guttman, E., Bisdikian, C., and W. Jerome;Select and Sort Extensions for the Service Location Protocol (SLP);;;;;RFC 3421;DOI 10.17487/RFC3421;November;https://www.rfc-editor.org/info/rfc3421 | |
| RFC3422;;Okamoto, O., Maruyama, M., and T. Sajima;Forwarding Media Access Control (MAC) Frames over Multiple Access Protocol over Synchronous Optical Network/Synchronous Digital Hierarchy (MAPOS);;;;;RFC 3422;DOI 10.17487/RFC3422;November;https://www.rfc-editor.org/info/rfc3422 | |
| RFC3423;;Zhang, K. and E. Elkin;XACCT's Common Reliable Accounting for Network Element (CRANE) Protocol Specification Version 1.0;;;;;RFC 3423;DOI 10.17487/RFC3423;November;https://www.rfc-editor.org/info/rfc3423 | |
| RFC3424;;Daigle, L., Ed., and IAB;IAB Considerations for UNilateral Self-Address Fixing (UNSAF) Across Network Address Translation;;;;;RFC 3424;DOI 10.17487/RFC3424;November;https://www.rfc-editor.org/info/rfc3424 | |
| RFC3425;;Lawrence, D.;Obsoleting IQUERY;;;;;RFC 3425;DOI 10.17487/RFC3425;November;https://www.rfc-editor.org/info/rfc3425 | |
| RFC3426;;Floyd, S.;General Architectural and Policy Considerations;;;;;RFC 3426;DOI 10.17487/RFC3426;November;https://www.rfc-editor.org/info/rfc3426 | |
| RFC3427;RFC5727;Mankin, A., Bradner, S., Mahy, R., Willis, D., Ott, J., and B. Rosen;Change Process for the Session Initiation Protocol (SIP);;;;;RFC 3427;DOI 10.17487/RFC3427;December;https://www.rfc-editor.org/info/rfc3427 | |
| RFC3428;;Campbell, B., Ed., Rosenberg, J., Schulzrinne, H., Huitema, C., and D. Gurle;Session Initiation Protocol (SIP) Extension for Instant Messaging;;;;;RFC 3428;DOI 10.17487/RFC3428;December;https://www.rfc-editor.org/info/rfc3428 | |
| RFC3429;;Ohta, H.;Assignment of the 'OAM Alert Label' for Multiprotocol Label Switching Architecture (MPLS) Operation and Maintenance (OAM) Functions;;;;;RFC 3429;DOI 10.17487/RFC3429;November;https://www.rfc-editor.org/info/rfc3429 | |
| RFC3430;;Schoenwaelder, J.;Simple Network Management Protocol Over Transmission Control Protocol Transport Mapping;;;;;RFC 3430;DOI 10.17487/RFC3430;December;https://www.rfc-editor.org/info/rfc3430 | |
| RFC3431;RFC5231;Segmuller, W.;Sieve Extension: Relational Tests;;;;;RFC 3431;DOI 10.17487/RFC3431;December;https://www.rfc-editor.org/info/rfc3431 | |
| RFC3432;;Raisanen, V., Grotefeld, G., and A. Morton;Network performance measurement with periodic streams;;;;;RFC 3432;DOI 10.17487/RFC3432;November;https://www.rfc-editor.org/info/rfc3432 | |
| RFC3433;;Bierman, A., Romascanu, D., and K. Norseth;Entity Sensor Management Information Base;;;;;RFC 3433;DOI 10.17487/RFC3433;December;https://www.rfc-editor.org/info/rfc3433 | |
| RFC3434;;Bierman, A. and K. McCloghrie;Remote Monitoring MIB Extensions for High Capacity Alarms;;;;;RFC 3434;DOI 10.17487/RFC3434;December;https://www.rfc-editor.org/info/rfc3434 | |
| RFC3435;;Andreasen, F. and B. Foster;Media Gateway Control Protocol (MGCP) Version 1.0;;;;;RFC 3435;DOI 10.17487/RFC3435;January;https://www.rfc-editor.org/info/rfc3435 | |
| RFC3436;;Jungmaier, A., Rescorla, E., and M. Tuexen;Transport Layer Security over Stream Control Transmission Protocol;;;;;RFC 3436;DOI 10.17487/RFC3436;December;https://www.rfc-editor.org/info/rfc3436 | |
| RFC3437;;Palter, W. and W. Townsley;Layer-Two Tunneling Protocol Extensions for PPP Link Control Protocol Negotiation;;;;;RFC 3437;DOI 10.17487/RFC3437;December;https://www.rfc-editor.org/info/rfc3437 | |
| RFC3438;;Townsley, W.;Layer Two Tunneling Protocol (L2TP) Internet Assigned Numbers Authority (IANA) Considerations Update;;;BCP 68;;RFC 3438;DOI 10.17487/RFC3438;December;https://www.rfc-editor.org/info/rfc3438 | |
| RFC3439;;Bush, R. and D. Meyer;Some Internet Architectural Guidelines and Philosophy;;;;;RFC 3439;DOI 10.17487/RFC3439;December;https://www.rfc-editor.org/info/rfc3439 | |
| RFC3440;;Ly, F. and G. Bathrick;Definitions of Extension Managed Objects for Asymmetric Digital Subscriber Lines;;;;;RFC 3440;DOI 10.17487/RFC3440;December;https://www.rfc-editor.org/info/rfc3440 | |
| RFC3441;;Kumar, R.;Asynchronous Transfer Mode (ATM) Package for the Media Gateway Control Protocol (MGCP);;;;;RFC 3441;DOI 10.17487/RFC3441;January;https://www.rfc-editor.org/info/rfc3441 | |
| RFC3442;;Lemon, T., Cheshire, S., and B. Volz;The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4;;;;;RFC 3442;DOI 10.17487/RFC3442;December;https://www.rfc-editor.org/info/rfc3442 | |
| RFC3443;;Agarwal, P. and B. Akyol;Time To Live (TTL) Processing in Multi-Protocol Label Switching (MPLS) Networks;;;;;RFC 3443;DOI 10.17487/RFC3443;January;https://www.rfc-editor.org/info/rfc3443 | |
| RFC3444;;Pras, A. and J. Schoenwaelder;On the Difference between Information Models and Data Models;;;;;RFC 3444;DOI 10.17487/RFC3444;January;https://www.rfc-editor.org/info/rfc3444 | |
| RFC3445;RFC4033, RFC4034, RFC4035;Massey, D. and S. Rose;Limiting the Scope of the KEY Resource Record (RR);;;;;RFC 3445;DOI 10.17487/RFC3445;December;https://www.rfc-editor.org/info/rfc3445 | |
| RFC3446;;Kim, D., Meyer, D., Kilmer, H., and D. Farinacci;Anycast Rendevous Point (RP) mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP);;;;;RFC 3446;DOI 10.17487/RFC3446;January;https://www.rfc-editor.org/info/rfc3446 | |
| RFC3447;RFC8017;Jonsson, J. and B. Kaliski;Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1;;;;;RFC 3447;DOI 10.17487/RFC3447;February;https://www.rfc-editor.org/info/rfc3447 | |
| RFC3448;RFC5348;Handley, M., Floyd, S., Padhye, J., and J. Widmer;TCP Friendly Rate Control (TFRC): Protocol Specification;;;;;RFC 3448;DOI 10.17487/RFC3448;January;https://www.rfc-editor.org/info/rfc3448 | |
| RFC3449;;Balakrishnan, H., Padmanabhan, V., Fairhurst, G., and M. Sooriyabandara;TCP Performance Implications of Network Path Asymmetry;;;BCP 69;;RFC 3449;DOI 10.17487/RFC3449;December;https://www.rfc-editor.org/info/rfc3449 | |
| RFC3450;RFC5775;Luby, M., Gemmell, J., Vicisano, L., Rizzo, L., and J. Crowcroft;Asynchronous Layered Coding (ALC) Protocol Instantiation;;;;;RFC 3450;DOI 10.17487/RFC3450;December;https://www.rfc-editor.org/info/rfc3450 | |
| RFC3451;RFC5651;Luby, M., Gemmell, J., Vicisano, L., Rizzo, L., Handley, M., and J. Crowcroft;Layered Coding Transport (LCT) Building Block;;;;;RFC 3451;DOI 10.17487/RFC3451;December;https://www.rfc-editor.org/info/rfc3451 | |
| RFC3452;RFC5052, RFC5445;Luby, M., Vicisano, L., Gemmell, J., Rizzo, L., Handley, M., and J. Crowcroft;Forward Error Correction (FEC) Building Block;;;;;RFC 3452;DOI 10.17487/RFC3452;December;https://www.rfc-editor.org/info/rfc3452 | |
| RFC3453;;Luby, M., Vicisano, L., Gemmell, J., Rizzo, L., Handley, M., and J. Crowcroft;The Use of Forward Error Correction (FEC) in Reliable Multicast;;;;;RFC 3453;DOI 10.17487/RFC3453;December;https://www.rfc-editor.org/info/rfc3453 | |
| RFC3454;RFC7564;Hoffman, P. and M. Blanchet;Preparation of Internationalized Strings ("stringprep");;;;;RFC 3454;DOI 10.17487/RFC3454;December;https://www.rfc-editor.org/info/rfc3454 | |
| RFC3455;RFC7315;Garcia-Martin, M., Henrikson, E., and D. Mills;Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP);;;;;RFC 3455;DOI 10.17487/RFC3455;January;https://www.rfc-editor.org/info/rfc3455 | |
| RFC3456;;Patel, B., Aboba, B., Kelly, S., and V. Gupta;Dynamic Host Configuration Protocol (DHCPv4) Configuration of IPsec Tunnel Mode;;;;;RFC 3456;DOI 10.17487/RFC3456;January;https://www.rfc-editor.org/info/rfc3456 | |
| RFC3457;;Kelly, S. and S. Ramamoorthi;Requirements for IPsec Remote Access Scenarios;;;;;RFC 3457;DOI 10.17487/RFC3457;January;https://www.rfc-editor.org/info/rfc3457 | |
| RFC3458;;Burger, E., Candell, E., Eliot, C., and G. Klyne;Message Context for Internet Mail;;;;;RFC 3458;DOI 10.17487/RFC3458;January;https://www.rfc-editor.org/info/rfc3458 | |
| RFC3459;;Burger, E.;Critical Content Multi-purpose Internet Mail Extensions (MIME) Parameter;;;;;RFC 3459;DOI 10.17487/RFC3459;January;https://www.rfc-editor.org/info/rfc3459 | |
| RFC3460;;Moore, B., Ed.;Policy Core Information Model (PCIM) Extensions;;;;;RFC 3460;DOI 10.17487/RFC3460;January;https://www.rfc-editor.org/info/rfc3460 | |
| RFC3461;;Moore, K.;Simple Mail Transfer Protocol (SMTP) Service Extension for Delivery Status Notifications (DSNs);;;;;RFC 3461;DOI 10.17487/RFC3461;January;https://www.rfc-editor.org/info/rfc3461 | |
| RFC3462;RFC6522;Vaudreuil, G.;The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages;;;;;RFC 3462;DOI 10.17487/RFC3462;January;https://www.rfc-editor.org/info/rfc3462 | |
| RFC3463;;Vaudreuil, G.;Enhanced Mail System Status Codes;;;;;RFC 3463;DOI 10.17487/RFC3463;January;https://www.rfc-editor.org/info/rfc3463 | |
| RFC3464;;Moore, K. and G. Vaudreuil;An Extensible Message Format for Delivery Status Notifications;;;;;RFC 3464;DOI 10.17487/RFC3464;January;https://www.rfc-editor.org/info/rfc3464 | |
| RFC3465;;Allman, M.;TCP Congestion Control with Appropriate Byte Counting (ABC);;;;;RFC 3465;DOI 10.17487/RFC3465;February;https://www.rfc-editor.org/info/rfc3465 | |
| RFC3466;RFC7336;Day, M., Cain, B., Tomlinson, G., and P. Rzewski;A Model for Content Internetworking (CDI);;;;;RFC 3466;DOI 10.17487/RFC3466;February;https://www.rfc-editor.org/info/rfc3466 | |
| RFC3467;;Klensin, J.;Role of the Domain Name System (DNS);;;;;RFC 3467;DOI 10.17487/RFC3467;February;https://www.rfc-editor.org/info/rfc3467 | |
| RFC3468;;Andersson, L. and G. Swallow;The Multiprotocol Label Switching (MPLS) Working Group decision on MPLS signaling protocols;;;;;RFC 3468;DOI 10.17487/RFC3468;February;https://www.rfc-editor.org/info/rfc3468 | |
| RFC3469;;Sharma, V., Ed., and F. Hellstrand, Ed.;Framework for Multi-Protocol Label Switching (MPLS)-based Recovery;;;;;RFC 3469;DOI 10.17487/RFC3469;February;https://www.rfc-editor.org/info/rfc3469 | |
| RFC3470;;Hollenbeck, S., Rose, M., and L. Masinter;Guidelines for the Use of Extensible Markup Language (XML) within IETF Protocols;;;BCP 70;;RFC 3470;DOI 10.17487/RFC3470;January;https://www.rfc-editor.org/info/rfc3470 | |
| RFC3471;;Berger, L., Ed.;Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description;;;;;RFC 3471;DOI 10.17487/RFC3471;January;https://www.rfc-editor.org/info/rfc3471 | |
| RFC3472;;Ashwood-Smith, P., Ed., and L. Berger, Ed.;Generalized Multi-Protocol Label Switching (GMPLS) Signaling Constraint-based Routed Label Distribution Protocol (CR-LDP) Extensions;;;;;RFC 3472;DOI 10.17487/RFC3472;January;https://www.rfc-editor.org/info/rfc3472 | |
| RFC3473;;Berger, L., Ed.;Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions;;;;;RFC 3473;DOI 10.17487/RFC3473;January;https://www.rfc-editor.org/info/rfc3473 | |
| RFC3474;;Lin, Z. and D. Pendarakis;Documentation of IANA assignments for Generalized MultiProtocol Label Switching (GMPLS) Resource Reservation Protocol - Traffic Engineering (RSVP-TE) Usage and Extensions for Automatically Switched Optical Network (ASON);;;;;RFC 3474;DOI 10.17487/RFC3474;March;https://www.rfc-editor.org/info/rfc3474 | |
| RFC3475;;Aboul-Magd, O.;Documentation of IANA assignments for Constraint-Based LSP setup using LDP (CR-LDP) Extensions for Automatic Switched Optical Network (ASON);;;;;RFC 3475;DOI 10.17487/RFC3475;March;https://www.rfc-editor.org/info/rfc3475 | |
| RFC3476;;Rajagopalan, B.;Documentation of IANA Assignments for Label Distribution Protocol (LDP), Resource ReSerVation Protocol (RSVP), and Resource ReSerVation Protocol-Traffic Engineering (RSVP-TE) Extensions for Optical UNI Signaling;;;;;RFC 3476;DOI 10.17487/RFC3476;March;https://www.rfc-editor.org/info/rfc3476 | |
| RFC3477;;Kompella, K. and Y. Rekhter;Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE);;;;;RFC 3477;DOI 10.17487/RFC3477;January;https://www.rfc-editor.org/info/rfc3477 | |
| RFC3478;;Leelanivas, M., Rekhter, Y., and R. Aggarwal;Graceful Restart Mechanism for Label Distribution Protocol;;;;;RFC 3478;DOI 10.17487/RFC3478;February;https://www.rfc-editor.org/info/rfc3478 | |
| RFC3479;;Farrel, A., Ed.;Fault Tolerance for the Label Distribution Protocol (LDP);;;;;RFC 3479;DOI 10.17487/RFC3479;February;https://www.rfc-editor.org/info/rfc3479 | |
| RFC3480;;Kompella, K., Rekhter, Y., and A. Kullberg;Signalling Unnumbered Links in CR-LDP (Constraint-Routing Label Distribution Protocol);;;;;RFC 3480;DOI 10.17487/RFC3480;February;https://www.rfc-editor.org/info/rfc3480 | |
| RFC3481;;Inamura, H., Ed., Montenegro, G., Ed., Ludwig, R., Gurtov, A., and F. Khafizov;TCP over Second (2.5G) and Third (3G) Generation Wireless Networks;;;BCP 71;;RFC 3481;DOI 10.17487/RFC3481;February;https://www.rfc-editor.org/info/rfc3481 | |
| RFC3482;;Foster, M., McGarry, T., and J. Yu;Number Portability in the Global Switched Telephone Network (GSTN): An Overview;;;;;RFC 3482;DOI 10.17487/RFC3482;February;https://www.rfc-editor.org/info/rfc3482 | |
| RFC3483;;Rawlins, D., Kulkarni, A., Bokaemper, M., and K. Chan;Framework for Policy Usage Feedback for Common Open Policy Service with Policy Provisioning (COPS-PR);;;;;RFC 3483;DOI 10.17487/RFC3483;March;https://www.rfc-editor.org/info/rfc3483 | |
| RFC3484;RFC6724;Draves, R.;Default Address Selection for Internet Protocol version 6 (IPv6);;;;;RFC 3484;DOI 10.17487/RFC3484;February;https://www.rfc-editor.org/info/rfc3484 | |
| RFC3485;;Garcia-Martin, M., Bormann, C., Ott, J., Price, R., and A. Roach;The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp);;;;;RFC 3485;DOI 10.17487/RFC3485;February;https://www.rfc-editor.org/info/rfc3485 | |
| RFC3486;;Camarillo, G.;Compressing the Session Initiation Protocol (SIP);;;;;RFC 3486;DOI 10.17487/RFC3486;February;https://www.rfc-editor.org/info/rfc3486 | |
| RFC3487;;Schulzrinne, H.;Requirements for Resource Priority Mechanisms for the Session Initiation Protocol (SIP);;;;;RFC 3487;DOI 10.17487/RFC3487;February;https://www.rfc-editor.org/info/rfc3487 | |
| RFC3488;;Wu, I. and T. Eckert;Cisco Systems Router-port Group Management Protocol (RGMP);;;;;RFC 3488;DOI 10.17487/RFC3488;February;https://www.rfc-editor.org/info/rfc3488 | |
| RFC3489;RFC5389;Rosenberg, J., Weinberger, J., Huitema, C., and R. Mahy;STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs);;;;;RFC 3489;DOI 10.17487/RFC3489;March;https://www.rfc-editor.org/info/rfc3489 | |
| RFC3490;RFC5890, RFC5891;Faltstrom, P., Hoffman, P., and A. Costello;Internationalizing Domain Names in Applications (IDNA);;;;;RFC 3490;DOI 10.17487/RFC3490;March;https://www.rfc-editor.org/info/rfc3490 | |
| RFC3491;RFC5891;Hoffman, P. and M. Blanchet;Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN);;;;;RFC 3491;DOI 10.17487/RFC3491;March;https://www.rfc-editor.org/info/rfc3491 | |
| RFC3492;;Costello, A.;Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA);;;;;RFC 3492;DOI 10.17487/RFC3492;March;https://www.rfc-editor.org/info/rfc3492 | |
| RFC3493;;Gilligan, R., Thomson, S., Bound, J., McCann, J., and W. Stevens;Basic Socket Interface Extensions for IPv6;;;;;RFC 3493;DOI 10.17487/RFC3493;February;https://www.rfc-editor.org/info/rfc3493 | |
| RFC3494;;Zeilenga, K.;Lightweight Directory Access Protocol version 2 (LDAPv2) to Historic Status;;;;;RFC 3494;DOI 10.17487/RFC3494;March;https://www.rfc-editor.org/info/rfc3494 | |
| RFC3495;;Beser, B. and P. Duffy, Ed.;Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client Configuration;;;;;RFC 3495;DOI 10.17487/RFC3495;March;https://www.rfc-editor.org/info/rfc3495 | |
| RFC3496;;Malis, A. and T. Hsiao;Protocol Extension for Support of Asynchronous Transfer Mode (ATM) Service Class-aware Multiprotocol Label Switching (MPLS) Traffic Engineering;;;;;RFC 3496;DOI 10.17487/RFC3496;March;https://www.rfc-editor.org/info/rfc3496 | |
| RFC3497;;Gharai, L., Perkins, C., Goncher, G., and A. Mankin;RTP Payload Format for Society of Motion Picture and Television Engineers (SMPTE) 292M Video;;;;;RFC 3497;DOI 10.17487/RFC3497;March;https://www.rfc-editor.org/info/rfc3497 | |
| RFC3498;;Kuhfeld, J., Johnson, J., and M. Thatcher;Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) Architectures;;;;;RFC 3498;DOI 10.17487/RFC3498;March;https://www.rfc-editor.org/info/rfc3498 | |
| RFC3499;;Ginoza, S.;Request for Comments Summary RFC Numbers 3400-3499;;;;;RFC 3499;DOI 10.17487/RFC3499;December;https://www.rfc-editor.org/info/rfc3499 | |
| RFC3501;;Crispin, M.;INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1;;;;;RFC 3501;DOI 10.17487/RFC3501;March;https://www.rfc-editor.org/info/rfc3501 | |
| RFC3502;;Crispin, M.;Internet Message Access Protocol (IMAP) - MULTIAPPEND Extension;;;;;RFC 3502;DOI 10.17487/RFC3502;March;https://www.rfc-editor.org/info/rfc3502 | |
| RFC3503;;Melnikov, A.;Message Disposition Notification (MDN) profile for Internet Message Access Protocol (IMAP);;;;;RFC 3503;DOI 10.17487/RFC3503;March;https://www.rfc-editor.org/info/rfc3503 | |
| RFC3504;;Eastlake, D.;Internet Open Trading Protocol (IOTP) Version 1, Errata;;;;;RFC 3504;DOI 10.17487/RFC3504;March;https://www.rfc-editor.org/info/rfc3504 | |
| RFC3505;;Eastlake, D.;Electronic Commerce Modeling Language (ECML): Version 2 Requirements;;;;;RFC 3505;DOI 10.17487/RFC3505;March;https://www.rfc-editor.org/info/rfc3505 | |
| RFC3506;;Fujimura, K. and D. Eastlake;Requirements and Design for Voucher Trading System (VTS);;;;;RFC 3506;DOI 10.17487/RFC3506;March;https://www.rfc-editor.org/info/rfc3506 | |
| RFC3507;;Elson, J. and A. Cerpa;Internet Content Adaptation Protocol (ICAP);;;;;RFC 3507;DOI 10.17487/RFC3507;April;https://www.rfc-editor.org/info/rfc3507 | |
| RFC3508;;Levin, O.;H.323 Uniform Resource Locator (URL) Scheme Registration;;;;;RFC 3508;DOI 10.17487/RFC3508;April;https://www.rfc-editor.org/info/rfc3508 | |
| RFC3509;;Zinin, A., Lindem, A., and D. Yeung;Alternative Implementations of OSPF Area Border Routers;;;;;RFC 3509;DOI 10.17487/RFC3509;April;https://www.rfc-editor.org/info/rfc3509 | |
| RFC3510;;Herriot, R. and I. McDonald;Internet Printing Protocol/1.1: IPP URL Scheme;;;;;RFC 3510;DOI 10.17487/RFC3510;April;https://www.rfc-editor.org/info/rfc3510 | |
| RFC3511;;Hickman, B., Newman, D., Tadjudin, S., and T. Martin;Benchmarking Methodology for Firewall Performance;;;;;RFC 3511;DOI 10.17487/RFC3511;April;https://www.rfc-editor.org/info/rfc3511 | |
| RFC3512;;MacFaden, M., Partain, D., Saperia, J., and W. Tackabury;Configuring Networks and Devices with Simple Network Management Protocol (SNMP);;;;;RFC 3512;DOI 10.17487/RFC3512;April;https://www.rfc-editor.org/info/rfc3512 | |
| RFC3513;RFC4291;Hinden, R. and S. Deering;Internet Protocol Version 6 (IPv6) Addressing Architecture;;;;;RFC 3513;DOI 10.17487/RFC3513;April;https://www.rfc-editor.org/info/rfc3513 | |
| RFC3514;;Bellovin, S.;The Security Flag in the IPv4 Header;;;;;RFC 3514;DOI 10.17487/RFC3514;April;https://www.rfc-editor.org/info/rfc3514 | |
| RFC3515;;Sparks, R.;The Session Initiation Protocol (SIP) Refer Method;;;;;RFC 3515;DOI 10.17487/RFC3515;April;https://www.rfc-editor.org/info/rfc3515 | |
| RFC3516;;Nerenberg, L.;IMAP4 Binary Content Extension;;;;;RFC 3516;DOI 10.17487/RFC3516;April;https://www.rfc-editor.org/info/rfc3516 | |
| RFC3517;RFC6675;Blanton, E., Allman, M., Fall, K., and L. Wang;A Conservative Selective Acknowledgment (SACK)-based Loss Recovery Algorithm for TCP;;;;;RFC 3517;DOI 10.17487/RFC3517;April;https://www.rfc-editor.org/info/rfc3517 | |
| RFC3518;;Higashiyama, M., Baker, F., and T. Liao;Point-to-Point Protocol (PPP) Bridging Control Protocol (BCP);;;;;RFC 3518;DOI 10.17487/RFC3518;April;https://www.rfc-editor.org/info/rfc3518 | |
| RFC3519;;Levkowetz, H. and S. Vaarala;Mobile IP Traversal of Network Address Translation (NAT) Devices;;;;;RFC 3519;DOI 10.17487/RFC3519;April;https://www.rfc-editor.org/info/rfc3519 | |
| RFC3520;;Hamer, L-N., Gage, B., Kosinski, B., and H. Shieh;Session Authorization Policy Element;;;;;RFC 3520;DOI 10.17487/RFC3520;April;https://www.rfc-editor.org/info/rfc3520 | |
| RFC3521;;Hamer, L-N., Gage, B., and H. Shieh;Framework for Session Set-up with Media Authorization;;;;;RFC 3521;DOI 10.17487/RFC3521;April;https://www.rfc-editor.org/info/rfc3521 | |
| RFC3522;;Ludwig, R. and M. Meyer;The Eifel Detection Algorithm for TCP;;;;;RFC 3522;DOI 10.17487/RFC3522;April;https://www.rfc-editor.org/info/rfc3522 | |
| RFC3523;;Polk, J.;Internet Emergency Preparedness (IEPREP) Telephony Topology Terminology;;;;;RFC 3523;DOI 10.17487/RFC3523;April;https://www.rfc-editor.org/info/rfc3523 | |
| RFC3524;;Camarillo, G. and A. Monrad;Mapping of Media Streams to Resource Reservation Flows;;;;;RFC 3524;DOI 10.17487/RFC3524;April;https://www.rfc-editor.org/info/rfc3524 | |
| RFC3525;RFC5125;Groves, C., Ed., Pantaleo, M., Ed., Anderson, T., Ed., and T. Taylor, Ed.;Gateway Control Protocol Version 1;;;;;RFC 3525;DOI 10.17487/RFC3525;June;https://www.rfc-editor.org/info/rfc3525 | |
| RFC3526;;Kivinen, T. and M. Kojo;More Modular Exponential (MODP) Diffie-Hellman groups for Internet Key Exchange (IKE);;;;;RFC 3526;DOI 10.17487/RFC3526;May;https://www.rfc-editor.org/info/rfc3526 | |
| RFC3527;;Kinnear, K., Stapp, M., Johnson, R., and J. Kumarasamy;Link Selection sub-option for the Relay Agent Information Option for DHCPv4;;;;;RFC 3527;DOI 10.17487/RFC3527;April;https://www.rfc-editor.org/info/rfc3527 | |
| RFC3528;;Zhao, W., Schulzrinne, H., and E. Guttman;Mesh-enhanced Service Location Protocol (mSLP);;;;;RFC 3528;DOI 10.17487/RFC3528;April;https://www.rfc-editor.org/info/rfc3528 | |
| RFC3529;;Harold, W.;Using Extensible Markup Language-Remote Procedure Calling (XML-RPC) in Blocks Extensible Exchange Protocol (BEEP);;;;;RFC 3529;DOI 10.17487/RFC3529;April;https://www.rfc-editor.org/info/rfc3529 | |
| RFC3530;RFC7530;Shepler, S., Callaghan, B., Robinson, D., Thurlow, R., Beame, C., Eisler, M., and D. Noveck;Network File System (NFS) version 4 Protocol;;;;;RFC 3530;DOI 10.17487/RFC3530;April;https://www.rfc-editor.org/info/rfc3530 | |
| RFC3531;;Blanchet, M.;A Flexible Method for Managing the Assignment of Bits of an IPv6 Address Block;;;;;RFC 3531;DOI 10.17487/RFC3531;April;https://www.rfc-editor.org/info/rfc3531 | |
| RFC3532;;Anderson, T. and J. Buerkle;Requirements for the Dynamic Partitioning of Switching Elements;;;;;RFC 3532;DOI 10.17487/RFC3532;May;https://www.rfc-editor.org/info/rfc3532 | |
| RFC3533;;Pfeiffer, S.;The Ogg Encapsulation Format Version 0;;;;;RFC 3533;DOI 10.17487/RFC3533;May;https://www.rfc-editor.org/info/rfc3533 | |
| RFC3534;RFC5334;Walleij, L.;The application/ogg Media Type;;;;;RFC 3534;DOI 10.17487/RFC3534;May;https://www.rfc-editor.org/info/rfc3534 | |
| RFC3535;;Schoenwaelder, J.;Overview of the 2002 IAB Network Management Workshop;;;;;RFC 3535;DOI 10.17487/RFC3535;May;https://www.rfc-editor.org/info/rfc3535 | |
| RFC3536;RFC6365;Hoffman, P.;Terminology Used in Internationalization in the IETF;;;;;RFC 3536;DOI 10.17487/RFC3536;May;https://www.rfc-editor.org/info/rfc3536 | |
| RFC3537;;Schaad, J. and R. Housley;Wrapping a Hashed Message Authentication Code (HMAC) key with a Triple-Data Encryption Standard (DES) Key or an Advanced Encryption Standard (AES) Key;;;;;RFC 3537;DOI 10.17487/RFC3537;May;https://www.rfc-editor.org/info/rfc3537 | |
| RFC3538;;Kawatsura, Y.;Secure Electronic Transaction (SET) Supplement for the v1.0 Internet Open Trading Protocol (IOTP);;;;;RFC 3538;DOI 10.17487/RFC3538;June;https://www.rfc-editor.org/info/rfc3538 | |
| RFC3539;;Aboba, B. and J. Wood;Authentication, Authorization and Accounting (AAA) Transport Profile;;;;;RFC 3539;DOI 10.17487/RFC3539;June;https://www.rfc-editor.org/info/rfc3539 | |
| RFC3540;;Spring, N., Wetherall, D., and D. Ely;Robust Explicit Congestion Notification (ECN) Signaling with Nonces;;;;;RFC 3540;DOI 10.17487/RFC3540;June;https://www.rfc-editor.org/info/rfc3540 | |
| RFC3541;;Walsh, A.;A Uniform Resource Name (URN) Namespace for the Web3D Consortium (Web3D);;;;;RFC 3541;DOI 10.17487/RFC3541;May;https://www.rfc-editor.org/info/rfc3541 | |
| RFC3542;;Stevens, W., Thomas, M., Nordmark, E., and T. Jinmei;Advanced Sockets Application Program Interface (API) for IPv6;;;;;RFC 3542;DOI 10.17487/RFC3542;May;https://www.rfc-editor.org/info/rfc3542 | |
| RFC3543;;Glass, S. and M. Chandra;Registration Revocation in Mobile IPv4;;;;;RFC 3543;DOI 10.17487/RFC3543;August;https://www.rfc-editor.org/info/rfc3543 | |
| RFC3544;;Koren, T., Casner, S., and C. Bormann;IP Header Compression over PPP;;;;;RFC 3544;DOI 10.17487/RFC3544;July;https://www.rfc-editor.org/info/rfc3544 | |
| RFC3545;;Koren, T., Casner, S., Geevarghese, J., Thompson, B., and P. Ruddy;Enhanced Compressed RTP (CRTP) for Links with High Delay, Packet Loss and Reordering;;;;;RFC 3545;DOI 10.17487/RFC3545;July;https://www.rfc-editor.org/info/rfc3545 | |
| RFC3546;RFC4366;Blake-Wilson, S., Nystrom, M., Hopwood, D., Mikkelsen, J., and T. Wright;Transport Layer Security (TLS) Extensions;;;;;RFC 3546;DOI 10.17487/RFC3546;June;https://www.rfc-editor.org/info/rfc3546 | |
| RFC3547;RFC6407;Baugher, M., Weis, B., Hardjono, T., and H. Harney;The Group Domain of Interpretation;;;;;RFC 3547;DOI 10.17487/RFC3547;July;https://www.rfc-editor.org/info/rfc3547 | |
| RFC3548;RFC4648;Josefsson, S., Ed.;The Base16, Base32, and Base64 Data Encodings;;;;;RFC 3548;DOI 10.17487/RFC3548;July;https://www.rfc-editor.org/info/rfc3548 | |
| RFC3549;;Salim, J., Khosravi, H., Kleen, A., and A. Kuznetsov;Linux Netlink as an IP Services Protocol;;;;;RFC 3549;DOI 10.17487/RFC3549;July;https://www.rfc-editor.org/info/rfc3549 | |
| RFC3550;;Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson;RTP: A Transport Protocol for Real-Time Applications;;;;STD 64;RFC 3550;DOI 10.17487/RFC3550;July;https://www.rfc-editor.org/info/rfc3550 | |
| RFC3551;;Schulzrinne, H. and S. Casner;RTP Profile for Audio and Video Conferences with Minimal Control;;;;STD 65;RFC 3551;DOI 10.17487/RFC3551;July;https://www.rfc-editor.org/info/rfc3551 | |
| RFC3552;;Rescorla, E. and B. Korver;Guidelines for Writing RFC Text on Security Considerations;;;BCP 72;;RFC 3552;DOI 10.17487/RFC3552;July;https://www.rfc-editor.org/info/rfc3552 | |
| RFC3553;;Mealling, M., Masinter, L., Hardie, T., and G. Klyne;An IETF URN Sub-namespace for Registered Protocol Parameters;;;BCP 73;;RFC 3553;DOI 10.17487/RFC3553;June;https://www.rfc-editor.org/info/rfc3553 | |
| RFC3554;;Bellovin, S., Ioannidis, J., Keromytis, A., and R. Stewart;On the Use of Stream Control Transmission Protocol (SCTP) with IPsec;;;;;RFC 3554;DOI 10.17487/RFC3554;July;https://www.rfc-editor.org/info/rfc3554 | |
| RFC3555;RFC4855, RFC4856;Casner, S. and P. Hoschka;MIME Type Registration of RTP Payload Formats;;;;;RFC 3555;DOI 10.17487/RFC3555;July;https://www.rfc-editor.org/info/rfc3555 | |
| RFC3556;;Casner, S.;Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth;;;;;RFC 3556;DOI 10.17487/RFC3556;July;https://www.rfc-editor.org/info/rfc3556 | |
| RFC3557;;Xie, Q., Ed.;RTP Payload Format for European Telecommunications Standards Institute (ETSI) European Standard ES 201 108 Distributed Speech Recognition Encoding;;;;;RFC 3557;DOI 10.17487/RFC3557;July;https://www.rfc-editor.org/info/rfc3557 | |
| RFC3558;;Li, A.;RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV);;;;;RFC 3558;DOI 10.17487/RFC3558;July;https://www.rfc-editor.org/info/rfc3558 | |
| RFC3559;;Thaler, D.;Multicast Address Allocation MIB;;;;;RFC 3559;DOI 10.17487/RFC3559;June;https://www.rfc-editor.org/info/rfc3559 | |
| RFC3560;;Housley, R.;Use of the RSAES-OAEP Key Transport Algorithm in Cryptographic Message Syntax (CMS);;;;;RFC 3560;DOI 10.17487/RFC3560;July;https://www.rfc-editor.org/info/rfc3560 | |
| RFC3561;;Perkins, C., Belding-Royer, E., and S. Das;Ad hoc On-Demand Distance Vector (AODV) Routing;;;;;RFC 3561;DOI 10.17487/RFC3561;July;https://www.rfc-editor.org/info/rfc3561 | |
| RFC3562;;Leech, M.;Key Management Considerations for the TCP MD5 Signature Option;;;;;RFC 3562;DOI 10.17487/RFC3562;July;https://www.rfc-editor.org/info/rfc3562 | |
| RFC3563;;Zinin, A.;Cooperative Agreement Between the ISOC/IETF and ISO/IEC Joint Technical Committee 1/Sub Committee 6 (JTC1/SC6) on IS-IS Routing Protocol Development;;;;;RFC 3563;DOI 10.17487/RFC3563;July;https://www.rfc-editor.org/info/rfc3563 | |
| RFC3564;;Le Faucheur, F. and W. Lai;Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering;;;;;RFC 3564;DOI 10.17487/RFC3564;July;https://www.rfc-editor.org/info/rfc3564 | |
| RFC3565;;Schaad, J.;Use of the Advanced Encryption Standard (AES) Encryption Algorithm in Cryptographic Message Syntax (CMS);;;;;RFC 3565;DOI 10.17487/RFC3565;July;https://www.rfc-editor.org/info/rfc3565 | |
| RFC3566;;Frankel, S. and H. Herbert;The AES-XCBC-MAC-96 Algorithm and Its Use With IPsec;;;;;RFC 3566;DOI 10.17487/RFC3566;September;https://www.rfc-editor.org/info/rfc3566 | |
| RFC3567;RFC5304;Li, T. and R. Atkinson;Intermediate System to Intermediate System (IS-IS) Cryptographic Authentication;;;;;RFC 3567;DOI 10.17487/RFC3567;July;https://www.rfc-editor.org/info/rfc3567 | |
| RFC3568;;Barbir, A., Cain, B., Nair, R., and O. Spatscheck;Known Content Network (CN) Request-Routing Mechanisms;;;;;RFC 3568;DOI 10.17487/RFC3568;July;https://www.rfc-editor.org/info/rfc3568 | |
| RFC3569;;Bhattacharyya, S., Ed.;An Overview of Source-Specific Multicast (SSM);;;;;RFC 3569;DOI 10.17487/RFC3569;July;https://www.rfc-editor.org/info/rfc3569 | |
| RFC3570;RFC6770;Rzewski, P., Day, M., and D. Gilletti;Content Internetworking (CDI) Scenarios;;;;;RFC 3570;DOI 10.17487/RFC3570;July;https://www.rfc-editor.org/info/rfc3570 | |
| RFC3571;;Rawlins, D., Kulkarni, A., Ho Chan, K., Bokaemper, M., and D. Dutt;Framework Policy Information Base for Usage Feedback;;;;;RFC 3571;DOI 10.17487/RFC3571;August;https://www.rfc-editor.org/info/rfc3571 | |
| RFC3572;;Ogura, T., Maruyama, M., and T. Yoshida;Internet Protocol Version 6 over MAPOS (Multiple Access Protocol Over SONET/SDH);;;;;RFC 3572;DOI 10.17487/RFC3572;July;https://www.rfc-editor.org/info/rfc3572 | |
| RFC3573;;Goyret, I.;Signalling of Modem-On-Hold status in Layer 2 Tunneling Protocol (L2TP);;;;;RFC 3573;DOI 10.17487/RFC3573;July;https://www.rfc-editor.org/info/rfc3573 | |
| RFC3574;;Soininen, J., Ed.;Transition Scenarios for 3GPP Networks;;;;;RFC 3574;DOI 10.17487/RFC3574;August;https://www.rfc-editor.org/info/rfc3574 | |
| RFC3575;;Aboba, B.;IANA Considerations for RADIUS (Remote Authentication Dial In User Service);;;;;RFC 3575;DOI 10.17487/RFC3575;July;https://www.rfc-editor.org/info/rfc3575 | |
| RFC3576;RFC5176;Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B. Aboba;Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS);;;;;RFC 3576;DOI 10.17487/RFC3576;July;https://www.rfc-editor.org/info/rfc3576 | |
| RFC3577;;Waldbusser, S., Cole, R., Kalbfleisch, C., and D. Romascanu;Introduction to the Remote Monitoring (RMON) Family of MIB Modules;;;;;RFC 3577;DOI 10.17487/RFC3577;August;https://www.rfc-editor.org/info/rfc3577 | |
| RFC3578;;Camarillo, G., Roach, A., Peterson, J., and L. Ong;Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP);;;;;RFC 3578;DOI 10.17487/RFC3578;August;https://www.rfc-editor.org/info/rfc3578 | |
| RFC3579;;Aboba, B. and P. Calhoun;RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP);;;;;RFC 3579;DOI 10.17487/RFC3579;September;https://www.rfc-editor.org/info/rfc3579 | |
| RFC3580;;Congdon, P., Aboba, B., Smith, A., Zorn, G., and J. Roese;IEEE 802.1X Remote Authentication Dial In User Service (RADIUS) Usage Guidelines;;;;;RFC 3580;DOI 10.17487/RFC3580;September;https://www.rfc-editor.org/info/rfc3580 | |
| RFC3581;;Rosenberg, J. and H. Schulzrinne;An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing;;;;;RFC 3581;DOI 10.17487/RFC3581;August;https://www.rfc-editor.org/info/rfc3581 | |
| RFC3582;;Abley, J., Black, B., and V. Gill;Goals for IPv6 Site-Multihoming Architectures;;;;;RFC 3582;DOI 10.17487/RFC3582;August;https://www.rfc-editor.org/info/rfc3582 | |
| RFC3583;;Chaskar, H., Ed.;Requirements of a Quality of Service (QoS) Solution for Mobile IP;;;;;RFC 3583;DOI 10.17487/RFC3583;September;https://www.rfc-editor.org/info/rfc3583 | |
| RFC3584;;Frye, R., Levi, D., Routhier, S., and B. Wijnen;Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework;;;BCP 74;;RFC 3584;DOI 10.17487/RFC3584;August;https://www.rfc-editor.org/info/rfc3584 | |
| RFC3585;;Jason, J., Rafalow, L., and E. Vyncke;IPsec Configuration Policy Information Model;;;;;RFC 3585;DOI 10.17487/RFC3585;August;https://www.rfc-editor.org/info/rfc3585 | |
| RFC3586;;Blaze, M., Keromytis, A., Richardson, M., and L. Sanchez;IP Security Policy (IPSP) Requirements;;;;;RFC 3586;DOI 10.17487/RFC3586;August;https://www.rfc-editor.org/info/rfc3586 | |
| RFC3587;;Hinden, R., Deering, S., and E. Nordmark;IPv6 Global Unicast Address Format;;;;;RFC 3587;DOI 10.17487/RFC3587;August;https://www.rfc-editor.org/info/rfc3587 | |
| RFC3588;RFC6733;Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko;Diameter Base Protocol;;;;;RFC 3588;DOI 10.17487/RFC3588;September;https://www.rfc-editor.org/info/rfc3588 | |
| RFC3589;;Loughney, J.;Diameter Command Codes for Third Generation Partnership Project (3GPP) Release 5;;;;;RFC 3589;DOI 10.17487/RFC3589;September;https://www.rfc-editor.org/info/rfc3589 | |
| RFC3590;;Haberman, B.;Source Address Selection for the Multicast Listener Discovery (MLD) Protocol;;;;;RFC 3590;DOI 10.17487/RFC3590;September;https://www.rfc-editor.org/info/rfc3590 | |
| RFC3591;;Lam, H-K., Stewart, M., and A. Huynh;Definitions of Managed Objects for the Optical Interface Type;;;;;RFC 3591;DOI 10.17487/RFC3591;September;https://www.rfc-editor.org/info/rfc3591 | |
| RFC3592;;Tesink, K.;Definitions of Managed Objects for the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface Type;;;;;RFC 3592;DOI 10.17487/RFC3592;September;https://www.rfc-editor.org/info/rfc3592 | |
| RFC3593;;Tesink, K., Ed.;Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals;;;;;RFC 3593;DOI 10.17487/RFC3593;September;https://www.rfc-editor.org/info/rfc3593 | |
| RFC3594;;Duffy, P.;PacketCable Security Ticket Control Sub-Option for the DHCP CableLabs Client Configuration (CCC) Option;;;;;RFC 3594;DOI 10.17487/RFC3594;September;https://www.rfc-editor.org/info/rfc3594 | |
| RFC3595;;Wijnen, B.;Textual Conventions for IPv6 Flow Label;;;;;RFC 3595;DOI 10.17487/RFC3595;September;https://www.rfc-editor.org/info/rfc3595 | |
| RFC3596;;Thomson, S., Huitema, C., Ksinant, V., and M. Souissi;DNS Extensions to Support IP Version 6;;;;STD 88;RFC 3596;DOI 10.17487/RFC3596;October;https://www.rfc-editor.org/info/rfc3596 | |
| RFC3597;;Gustafsson, A.;Handling of Unknown DNS Resource Record (RR) Types;;;;;RFC 3597;DOI 10.17487/RFC3597;September;https://www.rfc-editor.org/info/rfc3597 | |
| RFC3598;RFC5233;Murchison, K.;Sieve Email Filtering -- Subaddress Extension;;;;;RFC 3598;DOI 10.17487/RFC3598;September;https://www.rfc-editor.org/info/rfc3598 | |
| RFC3599;;Ginoza, S.;Request for Comments Summary RFC Numbers 3500-3599;;;;;RFC 3599;DOI 10.17487/RFC3599;December;https://www.rfc-editor.org/info/rfc3599 | |
| RFC3600;RFC3700;Reynolds, J., Ed., and S. Ginoza, Ed.;Internet Official Protocol Standards;;;;;RFC 3600;DOI 10.17487/RFC3600;November;https://www.rfc-editor.org/info/rfc3600 | |
| RFC3601;;Allocchio, C.;Text String Notation for Dial Sequences and Global Switched Telephone Network (GSTN) / E.164 Addresses;;;;;RFC 3601;DOI 10.17487/RFC3601;September;https://www.rfc-editor.org/info/rfc3601 | |
| RFC3602;;Frankel, S., Glenn, R., and S. Kelly;The AES-CBC Cipher Algorithm and Its Use with IPsec;;;;;RFC 3602;DOI 10.17487/RFC3602;September;https://www.rfc-editor.org/info/rfc3602 | |
| RFC3603;RFC5503;Marshall, W., Ed., and F. Andreasen, Ed.;Private Session Initiation Protocol (SIP) Proxy-to-Proxy Extensions for Supporting the PacketCable Distributed Call Signaling Architecture;;;;;RFC 3603;DOI 10.17487/RFC3603;October;https://www.rfc-editor.org/info/rfc3603 | |
| RFC3604;;Khosravi, H., Kullgren, G., Shew, S., Sadler, J., and A. Watanabe;Requirements for Adding Optical Support to the General Switch Management Protocol version 3 (GSMPv3);;;;;RFC 3604;DOI 10.17487/RFC3604;October;https://www.rfc-editor.org/info/rfc3604 | |
| RFC3605;;Huitema, C.;Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP);;;;;RFC 3605;DOI 10.17487/RFC3605;October;https://www.rfc-editor.org/info/rfc3605 | |
| RFC3606;;Ly, F., Noto, M., Smith, A., Spiegel, E., and K. Tesink;Definitions of Supplemental Managed Objects for ATM Interface;;;;;RFC 3606;DOI 10.17487/RFC3606;November;https://www.rfc-editor.org/info/rfc3606 | |
| RFC3607;;Leech, M.;Chinese Lottery Cryptanalysis Revisited: The Internet as a Codebreaking Tool;;;;;RFC 3607;DOI 10.17487/RFC3607;September;https://www.rfc-editor.org/info/rfc3607 | |
| RFC3608;;Willis, D. and B. Hoeneisen;Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration;;;;;RFC 3608;DOI 10.17487/RFC3608;October;https://www.rfc-editor.org/info/rfc3608 | |
| RFC3609;;Bonica, R., Kompella, K., and D. Meyer;Tracing Requirements for Generic Tunnels;;;;;RFC 3609;DOI 10.17487/RFC3609;September;https://www.rfc-editor.org/info/rfc3609 | |
| RFC3610;;Whiting, D., Housley, R., and N. Ferguson;Counter with CBC-MAC (CCM);;;;;RFC 3610;DOI 10.17487/RFC3610;September;https://www.rfc-editor.org/info/rfc3610 | |
| RFC3611;;Friedman, T., Ed., Caceres, R., Ed., and A. Clark, Ed.;RTP Control Protocol Extended Reports (RTCP XR);;;;;RFC 3611;DOI 10.17487/RFC3611;November;https://www.rfc-editor.org/info/rfc3611 | |
| RFC3612;;Farrel, A.;Applicability Statement for Restart Mechanisms for the Label Distribution Protocol (LDP);;;;;RFC 3612;DOI 10.17487/RFC3612;September;https://www.rfc-editor.org/info/rfc3612 | |
| RFC3613;;Morgan, R. and K. Hazelton;Definition of a Uniform Resource Name (URN) Namespace for the Middleware Architecture Committee for Education (MACE);;;;;RFC 3613;DOI 10.17487/RFC3613;October;https://www.rfc-editor.org/info/rfc3613 | |
| RFC3614;;Smith, J.;A Uniform Resource Name (URN) Namespace for the Motion Picture Experts Group (MPEG);;;;;RFC 3614;DOI 10.17487/RFC3614;September;https://www.rfc-editor.org/info/rfc3614 | |
| RFC3615;;Gustin, J. and A. Goyens;A Uniform Resource Name (URN) Namespace for SWIFT Financial Messaging;;;;;RFC 3615;DOI 10.17487/RFC3615;September;https://www.rfc-editor.org/info/rfc3615 | |
| RFC3616;;Bellifemine, F., Constantinescu, I., and S. Willmott;A Uniform Resource Name (URN) Namespace for Foundation for Intelligent Physical Agents (FIPA);;;;;RFC 3616;DOI 10.17487/RFC3616;September;https://www.rfc-editor.org/info/rfc3616 | |
| RFC3617;;Lear, E.;Uniform Resource Identifier (URI) Scheme and Applicability Statement for the Trivial File Transfer Protocol (TFTP);;;;;RFC 3617;DOI 10.17487/RFC3617;October;https://www.rfc-editor.org/info/rfc3617 | |
| RFC3618;;Fenner, B., Ed., and D. Meyer, Ed.;Multicast Source Discovery Protocol (MSDP);;;;;RFC 3618;DOI 10.17487/RFC3618;October;https://www.rfc-editor.org/info/rfc3618 | |
| RFC3619;;Shah, S. and M. Yip;Extreme Networks' Ethernet Automatic Protection Switching (EAPS) Version 1;;;;;RFC 3619;DOI 10.17487/RFC3619;October;https://www.rfc-editor.org/info/rfc3619 | |
| RFC3620;;New, D.;The TUNNEL Profile;;;;;RFC 3620;DOI 10.17487/RFC3620;October;https://www.rfc-editor.org/info/rfc3620 | |
| RFC3621;;Berger, A. and D. Romascanu;Power Ethernet MIB;;;;;RFC 3621;DOI 10.17487/RFC3621;December;https://www.rfc-editor.org/info/rfc3621 | |
| RFC3622;;Mealling, M.;A Uniform Resource Name (URN) Namespace for the Liberty Alliance Project;;;;;RFC 3622;DOI 10.17487/RFC3622;February;https://www.rfc-editor.org/info/rfc3622 | |
| RFC3623;;Moy, J., Pillay-Esnault, P., and A. Lindem;Graceful OSPF Restart;;;;;RFC 3623;DOI 10.17487/RFC3623;November;https://www.rfc-editor.org/info/rfc3623 | |
| RFC3624;;Foster, B., Auerbach, D., and F. Andreasen;The Media Gateway Control Protocol (MGCP) Bulk Audit Package;;;;;RFC 3624;DOI 10.17487/RFC3624;November;https://www.rfc-editor.org/info/rfc3624 | |
| RFC3625;;Gellens, R. and H. Garudadri;The QCP File Format and Media Types for Speech Data;;;;;RFC 3625;DOI 10.17487/RFC3625;September;https://www.rfc-editor.org/info/rfc3625 | |
| RFC3626;;Clausen, T., Ed., and P. Jacquet, Ed.;Optimized Link State Routing Protocol (OLSR);;;;;RFC 3626;DOI 10.17487/RFC3626;October;https://www.rfc-editor.org/info/rfc3626 | |
| RFC3627;RFC6547;Savola, P.;Use of /127 Prefix Length Between Routers Considered Harmful;;;;;RFC 3627;DOI 10.17487/RFC3627;September;https://www.rfc-editor.org/info/rfc3627 | |
| RFC3628;;Pinkas, D., Pope, N., and J. Ross;Policy Requirements for Time-Stamping Authorities (TSAs);;;;;RFC 3628;DOI 10.17487/RFC3628;November;https://www.rfc-editor.org/info/rfc3628 | |
| RFC3629;;Yergeau, F.;UTF-8, a transformation format of ISO 10646;;;;STD 63;RFC 3629;DOI 10.17487/RFC3629;November;https://www.rfc-editor.org/info/rfc3629 | |
| RFC3630;;Katz, D., Kompella, K., and D. Yeung;Traffic Engineering (TE) Extensions to OSPF Version 2;;;;;RFC 3630;DOI 10.17487/RFC3630;September;https://www.rfc-editor.org/info/rfc3630 | |
| RFC3631;;Bellovin, S., Ed., Schiller, J., Ed., and C. Kaufman, Ed.;Security Mechanisms for the Internet;;;;;RFC 3631;DOI 10.17487/RFC3631;December;https://www.rfc-editor.org/info/rfc3631 | |
| RFC3632;;Hollenbeck, S., Veeramachaneni, S., and S. Yalamanchilli;VeriSign Registry Registrar Protocol (RRP) Version 2.0.0;;;;;RFC 3632;DOI 10.17487/RFC3632;November;https://www.rfc-editor.org/info/rfc3632 | |
| RFC3633;RFC8415;Troan, O. and R. Droms;IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6;;;;;RFC 3633;DOI 10.17487/RFC3633;December;https://www.rfc-editor.org/info/rfc3633 | |
| RFC3634;;Luehrs, K., Woundy, R., Bevilacqua, J., and N. Davoust;Key Distribution Center (KDC) Server Address Sub-option for the Dynamic Host Configuration Protocol (DHCP) CableLabs Client Configuration (CCC) Option;;;;;RFC 3634;DOI 10.17487/RFC3634;December;https://www.rfc-editor.org/info/rfc3634 | |
| RFC3635;;Flick, J.;Definitions of Managed Objects for the Ethernet-like Interface Types;;;;;RFC 3635;DOI 10.17487/RFC3635;September;https://www.rfc-editor.org/info/rfc3635 | |
| RFC3636;RFC4836;Flick, J.;Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs);;;;;RFC 3636;DOI 10.17487/RFC3636;September;https://www.rfc-editor.org/info/rfc3636 | |
| RFC3637;;Heard, C., Ed.;Definitions of Managed Objects for the Ethernet WAN Interface Sublayer;;;;;RFC 3637;DOI 10.17487/RFC3637;September;https://www.rfc-editor.org/info/rfc3637 | |
| RFC3638;;Flick, J. and C. Heard;Applicability Statement for Reclassification of RFC 1643 to Historic Status;;;;;RFC 3638;DOI 10.17487/RFC3638;September;https://www.rfc-editor.org/info/rfc3638 | |
| RFC3639;;St. Johns, M., Ed., Huston, G., Ed., and IAB;Considerations on the use of a Service Identifier in Packet Headers;;;;;RFC 3639;DOI 10.17487/RFC3639;October;https://www.rfc-editor.org/info/rfc3639 | |
| RFC3640;;van der Meer, J., Mackie, D., Swaminathan, V., Singer, D., and P. Gentric;RTP Payload Format for Transport of MPEG-4 Elementary Streams;;;;;RFC 3640;DOI 10.17487/RFC3640;November;https://www.rfc-editor.org/info/rfc3640 | |
| RFC3641;;Legg, S.;Generic String Encoding Rules (GSER) for ASN.1 Types;;;;;RFC 3641;DOI 10.17487/RFC3641;October;https://www.rfc-editor.org/info/rfc3641 | |
| RFC3642;;Legg, S.;Common Elements of Generic String Encoding Rules (GSER) Encodings;;;;;RFC 3642;DOI 10.17487/RFC3642;October;https://www.rfc-editor.org/info/rfc3642 | |
| RFC3643;;Weber, R., Rajagopal, M., Travostino, F., O'Donnell, M., Monia, C., and M. Merhar;Fibre Channel (FC) Frame Encapsulation;;;;;RFC 3643;DOI 10.17487/RFC3643;December;https://www.rfc-editor.org/info/rfc3643 | |
| RFC3644;;Snir, Y., Ramberg, Y., Strassner, J., Cohen, R., and B. Moore;Policy Quality of Service (QoS) Information Model;;;;;RFC 3644;DOI 10.17487/RFC3644;November;https://www.rfc-editor.org/info/rfc3644 | |
| RFC3645;;Kwan, S., Garg, P., Gilroy, J., Esibov, L., Westhead, J., and R. Hall;Generic Security Service Algorithm for Secret Key Transaction Authentication for DNS (GSS-TSIG);;;;;RFC 3645;DOI 10.17487/RFC3645;October;https://www.rfc-editor.org/info/rfc3645 | |
| RFC3646;;Droms, R., Ed.;DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6);;;;;RFC 3646;DOI 10.17487/RFC3646;December;https://www.rfc-editor.org/info/rfc3646 | |
| RFC3647;;Chokhani, S., Ford, W., Sabett, R., Merrill, C., and S. Wu;Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices Framework;;;;;RFC 3647;DOI 10.17487/RFC3647;November;https://www.rfc-editor.org/info/rfc3647 | |
| RFC3648;;Whitehead, J. and J. Reschke, Ed.;Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol;;;;;RFC 3648;DOI 10.17487/RFC3648;December;https://www.rfc-editor.org/info/rfc3648 | |
| RFC3649;;Floyd, S.;HighSpeed TCP for Large Congestion Windows;;;;;RFC 3649;DOI 10.17487/RFC3649;December;https://www.rfc-editor.org/info/rfc3649 | |
| RFC3650;;Sun, S., Lannom, L., and B. Boesch;Handle System Overview;;;;;RFC 3650;DOI 10.17487/RFC3650;November;https://www.rfc-editor.org/info/rfc3650 | |
| RFC3651;;Sun, S., Reilly, S., and L. Lannom;Handle System Namespace and Service Definition;;;;;RFC 3651;DOI 10.17487/RFC3651;November;https://www.rfc-editor.org/info/rfc3651 | |
| RFC3652;;Sun, S., Reilly, S., Lannom, L., and J. Petrone;Handle System Protocol (ver 2.1) Specification;;;;;RFC 3652;DOI 10.17487/RFC3652;November;https://www.rfc-editor.org/info/rfc3652 | |
| RFC3653;;Boyer, J., Hughes, M., and J. Reagle;XML-Signature XPath Filter 2.0;;;;;RFC 3653;DOI 10.17487/RFC3653;December;https://www.rfc-editor.org/info/rfc3653 | |
| RFC3654;;Khosravi, H., Ed., and T. Anderson, Ed.;Requirements for Separation of IP Control and Forwarding;;;;;RFC 3654;DOI 10.17487/RFC3654;November;https://www.rfc-editor.org/info/rfc3654 | |
| RFC3655;RFC4033, RFC4034, RFC4035;Wellington, B. and O. Gudmundsson;Redefinition of DNS Authenticated Data (AD) bit;;;;;RFC 3655;DOI 10.17487/RFC3655;November;https://www.rfc-editor.org/info/rfc3655 | |
| RFC3656;;Siemborski, R.;The Mailbox Update (MUPDATE) Distributed Mailbox Database Protocol;;;;;RFC 3656;DOI 10.17487/RFC3656;December;https://www.rfc-editor.org/info/rfc3656 | |
| RFC3657;;Moriai, S. and A. Kato;Use of the Camellia Encryption Algorithm in Cryptographic Message Syntax (CMS);;;;;RFC 3657;DOI 10.17487/RFC3657;January;https://www.rfc-editor.org/info/rfc3657 | |
| RFC3658;RFC4033, RFC4034, RFC4035;Gudmundsson, O.;Delegation Signer (DS) Resource Record (RR);;;;;RFC 3658;DOI 10.17487/RFC3658;December;https://www.rfc-editor.org/info/rfc3658 | |
| RFC3659;;Hethmon, P.;Extensions to FTP;;;;;RFC 3659;DOI 10.17487/RFC3659;March;https://www.rfc-editor.org/info/rfc3659 | |
| RFC3660;;Foster, B. and F. Andreasen;Basic Media Gateway Control Protocol (MGCP) Packages;;;;;RFC 3660;DOI 10.17487/RFC3660;December;https://www.rfc-editor.org/info/rfc3660 | |
| RFC3661;;Foster, B. and C. Sivachelvan;Media Gateway Control Protocol (MGCP) Return Code Usage;;;;;RFC 3661;DOI 10.17487/RFC3661;December;https://www.rfc-editor.org/info/rfc3661 | |
| RFC3662;RFC8622;Bless, R., Nichols, K., and K. Wehrle;A Lower Effort Per-Domain Behavior (PDB) for Differentiated Services;;;;;RFC 3662;DOI 10.17487/RFC3662;December;https://www.rfc-editor.org/info/rfc3662 | |
| RFC3663;;Newton, A.;Domain Administrative Data in Lightweight Directory Access Protocol (LDAP);;;;;RFC 3663;DOI 10.17487/RFC3663;December;https://www.rfc-editor.org/info/rfc3663 | |
| RFC3664;RFC4434;Hoffman, P.;The AES-XCBC-PRF-128 Algorithm for the Internet Key Exchange Protocol (IKE);;;;;RFC 3664;DOI 10.17487/RFC3664;January;https://www.rfc-editor.org/info/rfc3664 | |
| RFC3665;;Johnston, A., Donovan, S., Sparks, R., Cunningham, C., and K. Summers;Session Initiation Protocol (SIP) Basic Call Flow Examples;;;BCP 75;;RFC 3665;DOI 10.17487/RFC3665;December;https://www.rfc-editor.org/info/rfc3665 | |
| RFC3666;;Johnston, A., Donovan, S., Sparks, R., Cunningham, C., and K. Summers;Session Initiation Protocol (SIP) Public Switched Telephone Network (PSTN) Call Flows;;;BCP 76;;RFC 3666;DOI 10.17487/RFC3666;December;https://www.rfc-editor.org/info/rfc3666 | |
| RFC3667;RFC3978;Bradner, S.;IETF Rights in Contributions;;;;;RFC 3667;DOI 10.17487/RFC3667;February;https://www.rfc-editor.org/info/rfc3667 | |
| RFC3668;RFC3979;Bradner, S.;Intellectual Property Rights in IETF Technology;;;;;RFC 3668;DOI 10.17487/RFC3668;February;https://www.rfc-editor.org/info/rfc3668 | |
| RFC3669;;Brim, S.;Guidelines for Working Groups on Intellectual Property Issues;;;;;RFC 3669;DOI 10.17487/RFC3669;February;https://www.rfc-editor.org/info/rfc3669 | |
| RFC3670;;Moore, B., Durham, D., Strassner, J., Westerinen, A., and W. Weiss;Information Model for Describing Network Device QoS Datapath Mechanisms;;;;;RFC 3670;DOI 10.17487/RFC3670;January;https://www.rfc-editor.org/info/rfc3670 | |
| RFC3671;;Zeilenga, K.;Collective Attributes in the Lightweight Directory Access Protocol (LDAP);;;;;RFC 3671;DOI 10.17487/RFC3671;December;https://www.rfc-editor.org/info/rfc3671 | |
| RFC3672;;Zeilenga, K.;Subentries in the Lightweight Directory Access Protocol (LDAP);;;;;RFC 3672;DOI 10.17487/RFC3672;December;https://www.rfc-editor.org/info/rfc3672 | |
| RFC3673;;Zeilenga, K.;Lightweight Directory Access Protocol version 3 (LDAPv3): All Operational Attributes;;;;;RFC 3673;DOI 10.17487/RFC3673;December;https://www.rfc-editor.org/info/rfc3673 | |
| RFC3674;RFC4512;Zeilenga, K.;Feature Discovery in Lightweight Directory Access Protocol (LDAP);;;;;RFC 3674;DOI 10.17487/RFC3674;December;https://www.rfc-editor.org/info/rfc3674 | |
| RFC3675;;Eastlake 3rd, D.;.sex Considered Dangerous;;;;;RFC 3675;DOI 10.17487/RFC3675;February;https://www.rfc-editor.org/info/rfc3675 | |
| RFC3676;;Gellens, R.;The Text/Plain Format and DelSp Parameters;;;;;RFC 3676;DOI 10.17487/RFC3676;February;https://www.rfc-editor.org/info/rfc3676 | |
| RFC3677;;Daigle, L., Ed., and Internet Architecture Board;IETF ISOC Board of Trustee Appointment Procedures;;;BCP 77;;RFC 3677;DOI 10.17487/RFC3677;December;https://www.rfc-editor.org/info/rfc3677 | |
| RFC3678;;Thaler, D., Fenner, B., and B. Quinn;Socket Interface Extensions for Multicast Source Filters;;;;;RFC 3678;DOI 10.17487/RFC3678;January;https://www.rfc-editor.org/info/rfc3678 | |
| RFC3679;;Droms, R.;Unused Dynamic Host Configuration Protocol (DHCP) Option Codes;;;;;RFC 3679;DOI 10.17487/RFC3679;January;https://www.rfc-editor.org/info/rfc3679 | |
| RFC3680;;Rosenberg, J.;A Session Initiation Protocol (SIP) Event Package for Registrations;;;;;RFC 3680;DOI 10.17487/RFC3680;March;https://www.rfc-editor.org/info/rfc3680 | |
| RFC3681;;Bush, R. and R. Fink;Delegation of E.F.F.3.IP6.ARPA;;;BCP 80;;RFC 3681;DOI 10.17487/RFC3681;January;https://www.rfc-editor.org/info/rfc3681 | |
| RFC3682;RFC5082;Gill, V., Heasley, J., and D. Meyer;The Generalized TTL Security Mechanism (GTSM);;;;;RFC 3682;DOI 10.17487/RFC3682;February;https://www.rfc-editor.org/info/rfc3682 | |
| RFC3683;;Rose, M.;A Practice for Revoking Posting Rights to IETF Mailing Lists;;;BCP 83;;RFC 3683;DOI 10.17487/RFC3683;March;https://www.rfc-editor.org/info/rfc3683 | |
| RFC3684;;Ogier, R., Templin, F., and M. Lewis;Topology Dissemination Based on Reverse-Path Forwarding (TBRPF);;;;;RFC 3684;DOI 10.17487/RFC3684;February;https://www.rfc-editor.org/info/rfc3684 | |
| RFC3685;RFC5235;Daboo, C.;SIEVE Email Filtering: Spamtest and VirusTest Extensions;;;;;RFC 3685;DOI 10.17487/RFC3685;February;https://www.rfc-editor.org/info/rfc3685 | |
| RFC3686;;Housley, R.;Using Advanced Encryption Standard (AES) Counter Mode With IPsec Encapsulating Security Payload (ESP);;;;;RFC 3686;DOI 10.17487/RFC3686;January;https://www.rfc-editor.org/info/rfc3686 | |
| RFC3687;;Legg, S.;Lightweight Directory Access Protocol (LDAP) and X.500 Component Matching Rules;;;;;RFC 3687;DOI 10.17487/RFC3687;February;https://www.rfc-editor.org/info/rfc3687 | |
| RFC3688;;Mealling, M.;The IETF XML Registry;;;BCP 81;;RFC 3688;DOI 10.17487/RFC3688;January;https://www.rfc-editor.org/info/rfc3688 | |
| RFC3689;;Carlberg, K. and R. Atkinson;General Requirements for Emergency Telecommunication Service (ETS);;;;;RFC 3689;DOI 10.17487/RFC3689;February;https://www.rfc-editor.org/info/rfc3689 | |
| RFC3690;;Carlberg, K. and R. Atkinson;IP Telephony Requirements for Emergency Telecommunication Service (ETS);;;;;RFC 3690;DOI 10.17487/RFC3690;February;https://www.rfc-editor.org/info/rfc3690 | |
| RFC3691;;Melnikov, A.;Internet Message Access Protocol (IMAP) UNSELECT command;;;;;RFC 3691;DOI 10.17487/RFC3691;February;https://www.rfc-editor.org/info/rfc3691 | |
| RFC3692;;Narten, T.;Assigning Experimental and Testing Numbers Considered Useful;;;BCP 82;;RFC 3692;DOI 10.17487/RFC3692;January;https://www.rfc-editor.org/info/rfc3692 | |
| RFC3693;;Cuellar, J., Morris, J., Mulligan, D., Peterson, J., and J. Polk;Geopriv Requirements;;;;;RFC 3693;DOI 10.17487/RFC3693;February;https://www.rfc-editor.org/info/rfc3693 | |
| RFC3694;;Danley, M., Mulligan, D., Morris, J., and J. Peterson;Threat Analysis of the Geopriv Protocol;;;;;RFC 3694;DOI 10.17487/RFC3694;February;https://www.rfc-editor.org/info/rfc3694 | |
| RFC3695;RFC5445;Luby, M. and L. Vicisano;Compact Forward Error Correction (FEC) Schemes;;;;;RFC 3695;DOI 10.17487/RFC3695;February;https://www.rfc-editor.org/info/rfc3695 | |
| RFC3696;;Klensin, J.;Application Techniques for Checking and Transformation of Names;;;;;RFC 3696;DOI 10.17487/RFC3696;February;https://www.rfc-editor.org/info/rfc3696 | |
| RFC3697;RFC6437;Rajahalme, J., Conta, A., Carpenter, B., and S. Deering;IPv6 Flow Label Specification;;;;;RFC 3697;DOI 10.17487/RFC3697;March;https://www.rfc-editor.org/info/rfc3697 | |
| RFC3698;;Zeilenga, K., Ed.;Lightweight Directory Access Protocol (LDAP): Additional Matching Rules;;;;;RFC 3698;DOI 10.17487/RFC3698;February;https://www.rfc-editor.org/info/rfc3698 | |
| RFC3700;RFC5000;Reynolds, J., Ed., and S. Ginoza, Ed.;Internet Official Protocol Standards;;;;;RFC 3700;DOI 10.17487/RFC3700;July;https://www.rfc-editor.org/info/rfc3700 | |
| RFC3701;;Fink, R. and R. Hinden;6bone (IPv6 Testing Address Allocation) Phaseout;;;;;RFC 3701;DOI 10.17487/RFC3701;March;https://www.rfc-editor.org/info/rfc3701 | |
| RFC3702;;Loughney, J. and G. Camarillo;Authentication, Authorization, and Accounting Requirements for the Session Initiation Protocol (SIP);;;;;RFC 3702;DOI 10.17487/RFC3702;February;https://www.rfc-editor.org/info/rfc3702 | |
| RFC3703;;Strassner, J., Moore, B., Moats, R., and E. Ellesson;Policy Core Lightweight Directory Access Protocol (LDAP) Schema;;;;;RFC 3703;DOI 10.17487/RFC3703;February;https://www.rfc-editor.org/info/rfc3703 | |
| RFC3704;;Baker, F. and P. Savola;Ingress Filtering for Multihomed Networks;;;BCP 84;;RFC 3704;DOI 10.17487/RFC3704;March;https://www.rfc-editor.org/info/rfc3704 | |
| RFC3705;;Ray, B. and R. Abbi;High Capacity Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals;;;;;RFC 3705;DOI 10.17487/RFC3705;February;https://www.rfc-editor.org/info/rfc3705 | |
| RFC3706;;Huang, G., Beaulieu, S., and D. Rochefort;A Traffic-Based Method of Detecting Dead Internet Key Exchange (IKE) Peers;;;;;RFC 3706;DOI 10.17487/RFC3706;February;https://www.rfc-editor.org/info/rfc3706 | |
| RFC3707;;Newton, A.;Cross Registry Internet Service Protocol (CRISP) Requirements;;;;;RFC 3707;DOI 10.17487/RFC3707;February;https://www.rfc-editor.org/info/rfc3707 | |
| RFC3708;;Blanton, E. and M. Allman;Using TCP Duplicate Selective Acknowledgement (DSACKs) and Stream Control Transmission Protocol (SCTP) Duplicate Transmission Sequence Numbers (TSNs) to Detect Spurious Retransmissions;;;;;RFC 3708;DOI 10.17487/RFC3708;February;https://www.rfc-editor.org/info/rfc3708 | |
| RFC3709;;Santesson, S., Housley, R., and T. Freeman;Internet X.509 Public Key Infrastructure: Logotypes in X.509 Certificates;;;;;RFC 3709;DOI 10.17487/RFC3709;February;https://www.rfc-editor.org/info/rfc3709 | |
| RFC3710;;Alvestrand, H.;An IESG charter;;;;;RFC 3710;DOI 10.17487/RFC3710;February;https://www.rfc-editor.org/info/rfc3710 | |
| RFC3711;;Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. Norrman;The Secure Real-time Transport Protocol (SRTP);;;;;RFC 3711;DOI 10.17487/RFC3711;March;https://www.rfc-editor.org/info/rfc3711 | |
| RFC3712;RFC7612;Fleming, P. and I. McDonald;Lightweight Directory Access Protocol (LDAP): Schema for Printer Services;;;;;RFC 3712;DOI 10.17487/RFC3712;February;https://www.rfc-editor.org/info/rfc3712 | |
| RFC3713;;Matsui, M., Nakajima, J., and S. Moriai;A Description of the Camellia Encryption Algorithm;;;;;RFC 3713;DOI 10.17487/RFC3713;April;https://www.rfc-editor.org/info/rfc3713 | |
| RFC3714;;Floyd, S., Ed., and J. Kempf, Ed.;IAB Concerns Regarding Congestion Control for Voice Traffic in the Internet;;;;;RFC 3714;DOI 10.17487/RFC3714;March;https://www.rfc-editor.org/info/rfc3714 | |
| RFC3715;;Aboba, B. and W. Dixon;IPsec-Network Address Translation (NAT) Compatibility Requirements;;;;;RFC 3715;DOI 10.17487/RFC3715;March;https://www.rfc-editor.org/info/rfc3715 | |
| RFC3716;;IAB Advisory Committee;IETF in the Large: Administration and Execution;;;;;RFC 3716;DOI 10.17487/RFC3716;March;https://www.rfc-editor.org/info/rfc3716 | |
| RFC3717;;Rajagopalan, B., Luciani, J., and D. Awduche;IP over Optical Networks: A Framework;;;;;RFC 3717;DOI 10.17487/RFC3717;March;https://www.rfc-editor.org/info/rfc3717 | |
| RFC3718;;McGowan, R.;A Summary of Unicode Consortium Procedures, Policies, Stability, and Public Access;;;;;RFC 3718;DOI 10.17487/RFC3718;February;https://www.rfc-editor.org/info/rfc3718 | |
| RFC3719;;Parker, J., Ed.;Recommendations for Interoperable Networks using Intermediate System to Intermediate System (IS-IS);;;;;RFC 3719;DOI 10.17487/RFC3719;February;https://www.rfc-editor.org/info/rfc3719 | |
| RFC3720;RFC7143;Satran, J., Meth, K., Sapuntzakis, C., Chadalapaka, M., and E. Zeidner;Internet Small Computer Systems Interface (iSCSI);;;;;RFC 3720;DOI 10.17487/RFC3720;April;https://www.rfc-editor.org/info/rfc3720 | |
| RFC3721;;Bakke, M., Hafner, J., Hufferd, J., Voruganti, K., and M. Krueger;Internet Small Computer Systems Interface (iSCSI) Naming and Discovery;;;;;RFC 3721;DOI 10.17487/RFC3721;April;https://www.rfc-editor.org/info/rfc3721 | |
| RFC3722;;Bakke, M.;String Profile for Internet Small Computer Systems Interface (iSCSI) Names;;;;;RFC 3722;DOI 10.17487/RFC3722;April;https://www.rfc-editor.org/info/rfc3722 | |
| RFC3723;;Aboba, B., Tseng, J., Walker, J., Rangan, V., and F. Travostino;Securing Block Storage Protocols over IP;;;;;RFC 3723;DOI 10.17487/RFC3723;April;https://www.rfc-editor.org/info/rfc3723 | |
| RFC3724;;Kempf, J., Ed., Austein, R., Ed., and IAB;The Rise of the Middle and the Future of End-to-End: Reflections on the Evolution of the Internet Architecture;;;;;RFC 3724;DOI 10.17487/RFC3724;March;https://www.rfc-editor.org/info/rfc3724 | |
| RFC3725;;Rosenberg, J., Peterson, J., Schulzrinne, H., and G. Camarillo;Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP);;;BCP 85;;RFC 3725;DOI 10.17487/RFC3725;April;https://www.rfc-editor.org/info/rfc3725 | |
| RFC3726;;Brunner, M., Ed.;Requirements for Signaling Protocols;;;;;RFC 3726;DOI 10.17487/RFC3726;April;https://www.rfc-editor.org/info/rfc3726 | |
| RFC3727;;Legg, S.;ASN.1 Module Definition for the LDAP and X.500 Component Matching Rules;;;;;RFC 3727;DOI 10.17487/RFC3727;February;https://www.rfc-editor.org/info/rfc3727 | |
| RFC3728;;Ray, B. and R. Abbi;Definitions of Managed Objects for Very High Speed Digital Subscriber Lines (VDSL);;;;;RFC 3728;DOI 10.17487/RFC3728;February;https://www.rfc-editor.org/info/rfc3728 | |
| RFC3729;;Waldbusser, S.;Application Performance Measurement MIB;;;;;RFC 3729;DOI 10.17487/RFC3729;March;https://www.rfc-editor.org/info/rfc3729 | |
| RFC3730;RFC4930;Hollenbeck, S.;Extensible Provisioning Protocol (EPP);;;;;RFC 3730;DOI 10.17487/RFC3730;March;https://www.rfc-editor.org/info/rfc3730 | |
| RFC3731;RFC4931;Hollenbeck, S.;Extensible Provisioning Protocol (EPP) Domain Name Mapping;;;;;RFC 3731;DOI 10.17487/RFC3731;March;https://www.rfc-editor.org/info/rfc3731 | |
| RFC3732;RFC4932;Hollenbeck, S.;Extensible Provisioning Protocol (EPP) Host Mapping;;;;;RFC 3732;DOI 10.17487/RFC3732;March;https://www.rfc-editor.org/info/rfc3732 | |
| RFC3733;RFC4933;Hollenbeck, S.;Extensible Provisioning Protocol (EPP) Contact Mapping;;;;;RFC 3733;DOI 10.17487/RFC3733;March;https://www.rfc-editor.org/info/rfc3733 | |
| RFC3734;RFC4934;Hollenbeck, S.;Extensible Provisioning Protocol (EPP) Transport Over TCP;;;;;RFC 3734;DOI 10.17487/RFC3734;March;https://www.rfc-editor.org/info/rfc3734 | |
| RFC3735;;Hollenbeck, S.;Guidelines for Extending the Extensible Provisioning Protocol (EPP);;;;;RFC 3735;DOI 10.17487/RFC3735;March;https://www.rfc-editor.org/info/rfc3735 | |
| RFC3736;RFC8415;Droms, R.;Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6;;;;;RFC 3736;DOI 10.17487/RFC3736;April;https://www.rfc-editor.org/info/rfc3736 | |
| RFC3737;;Wijnen, B. and A. Bierman;IANA Guidelines for the Registry of Remote Monitoring (RMON) MIB modules;;;;;RFC 3737;DOI 10.17487/RFC3737;April;https://www.rfc-editor.org/info/rfc3737 | |
| RFC3738;;Luby, M. and V. Goyal;Wave and Equation Based Rate Control (WEBRC) Building Block;;;;;RFC 3738;DOI 10.17487/RFC3738;April;https://www.rfc-editor.org/info/rfc3738 | |
| RFC3739;;Santesson, S., Nystrom, M., and T. Polk;Internet X.509 Public Key Infrastructure: Qualified Certificates Profile;;;;;RFC 3739;DOI 10.17487/RFC3739;March;https://www.rfc-editor.org/info/rfc3739 | |
| RFC3740;;Hardjono, T. and B. Weis;The Multicast Group Security Architecture;;;;;RFC 3740;DOI 10.17487/RFC3740;March;https://www.rfc-editor.org/info/rfc3740 | |
| RFC3741;;Boyer, J., Eastlake 3rd, D., and J. Reagle;Exclusive XML Canonicalization, Version 1.0;;;;;RFC 3741;DOI 10.17487/RFC3741;March;https://www.rfc-editor.org/info/rfc3741 | |
| RFC3742;;Floyd, S.;Limited Slow-Start for TCP with Large Congestion Windows;;;;;RFC 3742;DOI 10.17487/RFC3742;March;https://www.rfc-editor.org/info/rfc3742 | |
| RFC3743;;Konishi, K., Huang, K., Qian, H., and Y. Ko;Joint Engineering Team (JET) Guidelines for Internationalized Domain Names (IDN) Registration and Administration for Chinese, Japanese, and Korean;;;;;RFC 3743;DOI 10.17487/RFC3743;April;https://www.rfc-editor.org/info/rfc3743 | |
| RFC3744;;Clemm, G., Reschke, J., Sedlar, E., and J. Whitehead;Web Distributed Authoring and Versioning (WebDAV) Access Control Protocol;;;;;RFC 3744;DOI 10.17487/RFC3744;May;https://www.rfc-editor.org/info/rfc3744 | |
| RFC3745;;Singer, D., Clark, R., and D. Lee;MIME Type Registrations for JPEG 2000 (ISO/IEC 15444);;;;;RFC 3745;DOI 10.17487/RFC3745;April;https://www.rfc-editor.org/info/rfc3745 | |
| RFC3746;;Yang, L., Dantu, R., Anderson, T., and R. Gopal;Forwarding and Control Element Separation (ForCES) Framework;;;;;RFC 3746;DOI 10.17487/RFC3746;April;https://www.rfc-editor.org/info/rfc3746 | |
| RFC3747;;Hazewinkel, H., Ed., and D. Partain, Ed.;The Differentiated Services Configuration MIB;;;;;RFC 3747;DOI 10.17487/RFC3747;April;https://www.rfc-editor.org/info/rfc3747 | |
| RFC3748;;Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H. Levkowetz, Ed.;Extensible Authentication Protocol (EAP);;;;;RFC 3748;DOI 10.17487/RFC3748;June;https://www.rfc-editor.org/info/rfc3748 | |
| RFC3749;;Hollenbeck, S.;Transport Layer Security Protocol Compression Methods;;;;;RFC 3749;DOI 10.17487/RFC3749;May;https://www.rfc-editor.org/info/rfc3749 | |
| RFC3750;;Huitema, C., Austein, R., Satapati, S., and R. van der Pol;Unmanaged Networks IPv6 Transition Scenarios;;;;;RFC 3750;DOI 10.17487/RFC3750;April;https://www.rfc-editor.org/info/rfc3750 | |
| RFC3751;;Bradner, S.;Omniscience Protocol Requirements;;;;;RFC 3751;DOI 10.17487/RFC3751;April;https://www.rfc-editor.org/info/rfc3751 | |
| RFC3752;;Barbir, A., Burger, E., Chen, R., McHenry, S., Orman, H., and R. Penno;Open Pluggable Edge Services (OPES) Use Cases and Deployment Scenarios;;;;;RFC 3752;DOI 10.17487/RFC3752;April;https://www.rfc-editor.org/info/rfc3752 | |
| RFC3753;;Manner, J., Ed., and M. Kojo, Ed.;Mobility Related Terminology;;;;;RFC 3753;DOI 10.17487/RFC3753;June;https://www.rfc-editor.org/info/rfc3753 | |
| RFC3754;;Bless, R. and K. Wehrle;IP Multicast in Differentiated Services (DS) Networks;;;;;RFC 3754;DOI 10.17487/RFC3754;April;https://www.rfc-editor.org/info/rfc3754 | |
| RFC3755;RFC4033, RFC4034, RFC4035;Weiler, S.;Legacy Resolver Compatibility for Delegation Signer (DS);;;;;RFC 3755;DOI 10.17487/RFC3755;May;https://www.rfc-editor.org/info/rfc3755 | |
| RFC3756;;Nikander, P., Ed., Kempf, J., and E. Nordmark;IPv6 Neighbor Discovery (ND) Trust Models and Threats;;;;;RFC 3756;DOI 10.17487/RFC3756;May;https://www.rfc-editor.org/info/rfc3756 | |
| RFC3757;RFC4033, RFC4034, RFC4035;Kolkman, O., Schlyter, J., and E. Lewis;Domain Name System KEY (DNSKEY) Resource Record (RR) Secure Entry Point (SEP) Flag;;;;;RFC 3757;DOI 10.17487/RFC3757;April;https://www.rfc-editor.org/info/rfc3757 | |
| RFC3758;;Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P. Conrad;Stream Control Transmission Protocol (SCTP) Partial Reliability Extension;;;;;RFC 3758;DOI 10.17487/RFC3758;May;https://www.rfc-editor.org/info/rfc3758 | |
| RFC3759;;Jonsson, L-E.;RObust Header Compression (ROHC): Terminology and Channel Mapping Examples;;;;;RFC 3759;DOI 10.17487/RFC3759;April;https://www.rfc-editor.org/info/rfc3759 | |
| RFC3760;;Gustafson, D., Just, M., and M. Nystrom;Securely Available Credentials (SACRED) - Credential Server Framework;;;;;RFC 3760;DOI 10.17487/RFC3760;April;https://www.rfc-editor.org/info/rfc3760 | |
| RFC3761;RFC6116, RFC6117;Faltstrom, P. and M. Mealling;The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM);;;;;RFC 3761;DOI 10.17487/RFC3761;April;https://www.rfc-editor.org/info/rfc3761 | |
| RFC3762;;Levin, O.;Telephone Number Mapping (ENUM) Service Registration for H.323;;;;;RFC 3762;DOI 10.17487/RFC3762;April;https://www.rfc-editor.org/info/rfc3762 | |
| RFC3763;;Shalunov, S. and B. Teitelbaum;One-way Active Measurement Protocol (OWAMP) Requirements;;;;;RFC 3763;DOI 10.17487/RFC3763;April;https://www.rfc-editor.org/info/rfc3763 | |
| RFC3764;;Peterson, J.;enumservice registration for Session Initiation Protocol (SIP) Addresses-of-Record;;;;;RFC 3764;DOI 10.17487/RFC3764;April;https://www.rfc-editor.org/info/rfc3764 | |
| RFC3765;;Huston, G.;NOPEER Community for Border Gateway Protocol (BGP) Route Scope Control;;;;;RFC 3765;DOI 10.17487/RFC3765;April;https://www.rfc-editor.org/info/rfc3765 | |
| RFC3766;;Orman, H. and P. Hoffman;Determining Strengths For Public Keys Used For Exchanging Symmetric Keys;;;BCP 86;;RFC 3766;DOI 10.17487/RFC3766;April;https://www.rfc-editor.org/info/rfc3766 | |
| RFC3767;;Farrell, S., Ed.;Securely Available Credentials Protocol;;;;;RFC 3767;DOI 10.17487/RFC3767;June;https://www.rfc-editor.org/info/rfc3767 | |
| RFC3768;RFC5798;Hinden, R., Ed.;Virtual Router Redundancy Protocol (VRRP);;;;;RFC 3768;DOI 10.17487/RFC3768;April;https://www.rfc-editor.org/info/rfc3768 | |
| RFC3769;;Miyakawa, S. and R. Droms;Requirements for IPv6 Prefix Delegation;;;;;RFC 3769;DOI 10.17487/RFC3769;June;https://www.rfc-editor.org/info/rfc3769 | |
| RFC3770;RFC4334;Housley, R. and T. Moore;Certificate Extensions and Attributes Supporting Authentication in Point-to-Point Protocol (PPP) and Wireless Local Area Networks (WLAN);;;;;RFC 3770;DOI 10.17487/RFC3770;May;https://www.rfc-editor.org/info/rfc3770 | |
| RFC3771;RFC4511, RFC4510;Harrison, R. and K. Zeilenga;The Lightweight Directory Access Protocol (LDAP) Intermediate Response Message;;;;;RFC 3771;DOI 10.17487/RFC3771;April;https://www.rfc-editor.org/info/rfc3771 | |
| RFC3772;;Carlson, J. and R. Winslow;Point-to-Point Protocol (PPP) Vendor Protocol;;;;;RFC 3772;DOI 10.17487/RFC3772;May;https://www.rfc-editor.org/info/rfc3772 | |
| RFC3773;;Candell, E.;High-Level Requirements for Internet Voice Mail;;;;;RFC 3773;DOI 10.17487/RFC3773;June;https://www.rfc-editor.org/info/rfc3773 | |
| RFC3774;;Davies, E., Ed.;IETF Problem Statement;;;;;RFC 3774;DOI 10.17487/RFC3774;May;https://www.rfc-editor.org/info/rfc3774 | |
| RFC3775;RFC6275;Johnson, D., Perkins, C., and J. Arkko;Mobility Support in IPv6;;;;;RFC 3775;DOI 10.17487/RFC3775;June;https://www.rfc-editor.org/info/rfc3775 | |
| RFC3776;;Arkko, J., Devarapalli, V., and F. Dupont;Using IPsec to Protect Mobile IPv6 Signaling Between Mobile Nodes and Home Agents;;;;;RFC 3776;DOI 10.17487/RFC3776;June;https://www.rfc-editor.org/info/rfc3776 | |
| RFC3777;RFC7437;Galvin, J., Ed.;IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees;;;;;RFC 3777;DOI 10.17487/RFC3777;June;https://www.rfc-editor.org/info/rfc3777 | |
| RFC3778;RFC8118;Taft, E., Pravetz, J., Zilles, S., and L. Masinter;The application/pdf Media Type;;;;;RFC 3778;DOI 10.17487/RFC3778;May;https://www.rfc-editor.org/info/rfc3778 | |
| RFC3779;;Lynn, C., Kent, S., and K. Seo;X.509 Extensions for IP Addresses and AS Identifiers;;;;;RFC 3779;DOI 10.17487/RFC3779;June;https://www.rfc-editor.org/info/rfc3779 | |
| RFC3780;;Strauss, F. and J. Schoenwaelder;SMIng - Next Generation Structure of Management Information;;;;;RFC 3780;DOI 10.17487/RFC3780;May;https://www.rfc-editor.org/info/rfc3780 | |
| RFC3781;;Strauss, F. and J. Schoenwaelder;Next Generation Structure of Management Information (SMIng) Mappings to the Simple Network Management Protocol (SNMP);;;;;RFC 3781;DOI 10.17487/RFC3781;May;https://www.rfc-editor.org/info/rfc3781 | |
| RFC3782;RFC6582;Floyd, S., Henderson, T., and A. Gurtov;The NewReno Modification to TCP's Fast Recovery Algorithm;;;;;RFC 3782;DOI 10.17487/RFC3782;April;https://www.rfc-editor.org/info/rfc3782 | |
| RFC3783;;Chadalapaka, M. and R. Elliott;Small Computer Systems Interface (SCSI) Command Ordering Considerations with iSCSI;;;;;RFC 3783;DOI 10.17487/RFC3783;May;https://www.rfc-editor.org/info/rfc3783 | |
| RFC3784;RFC5305;Smit, H. and T. Li;Intermediate System to Intermediate System (IS-IS) Extensions for Traffic Engineering (TE);;;;;RFC 3784;DOI 10.17487/RFC3784;June;https://www.rfc-editor.org/info/rfc3784 | |
| RFC3785;;Le Faucheur, F., Uppili, R., Vedrenne, A., Merckx, P., and T. Telkamp;Use of Interior Gateway Protocol (IGP) Metric as a second MPLS Traffic Engineering (TE) Metric;;;BCP 87;;RFC 3785;DOI 10.17487/RFC3785;May;https://www.rfc-editor.org/info/rfc3785 | |
| RFC3786;RFC5311;Hermelin, A., Previdi, S., and M. Shand;Extending the Number of Intermediate System to Intermediate System (IS-IS) Link State PDU (LSP) Fragments Beyond the 256 Limit;;;;;RFC 3786;DOI 10.17487/RFC3786;May;https://www.rfc-editor.org/info/rfc3786 | |
| RFC3787;;Parker, J., Ed.;Recommendations for Interoperable IP Networks using Intermediate System to Intermediate System (IS-IS);;;;;RFC 3787;DOI 10.17487/RFC3787;May;https://www.rfc-editor.org/info/rfc3787 | |
| RFC3788;;Loughney, J., Tuexen, M., Ed., and J. Pastor-Balbas;Security Considerations for Signaling Transport (SIGTRAN) Protocols;;;;;RFC 3788;DOI 10.17487/RFC3788;June;https://www.rfc-editor.org/info/rfc3788 | |
| RFC3789;;Nesser, P., II, and A. Bergstrom, Ed.;Introduction to the Survey of IPv4 Addresses in Currently Deployed IETF Standards Track and Experimental Documents;;;;;RFC 3789;DOI 10.17487/RFC3789;June;https://www.rfc-editor.org/info/rfc3789 | |
| RFC3790;;Mickles, C., Ed., and P. Nesser, II;Survey of IPv4 Addresses in Currently Deployed IETF Internet Area Standards Track and Experimental Documents;;;;;RFC 3790;DOI 10.17487/RFC3790;June;https://www.rfc-editor.org/info/rfc3790 | |
| RFC3791;;Olvera, C. and P. Nesser, II;Survey of IPv4 Addresses in Currently Deployed IETF Routing Area Standards Track and Experimental Documents;;;;;RFC 3791;DOI 10.17487/RFC3791;June;https://www.rfc-editor.org/info/rfc3791 | |
| RFC3792;;Nesser, P., II, and A. Bergstrom, Ed.;Survey of IPv4 Addresses in Currently Deployed IETF Security Area Standards Track and Experimental Documents;;;;;RFC 3792;DOI 10.17487/RFC3792;June;https://www.rfc-editor.org/info/rfc3792 | |
| RFC3793;;Nesser, P., II, and A. Bergstrom, Ed.;Survey of IPv4 Addresses in Currently Deployed IETF Sub-IP Area Standards Track and Experimental Documents;;;;;RFC 3793;DOI 10.17487/RFC3793;June;https://www.rfc-editor.org/info/rfc3793 | |
| RFC3794;;Nesser, P., II, and A. Bergstrom, Ed.;Survey of IPv4 Addresses in Currently Deployed IETF Transport Area Standards Track and Experimental Documents;;;;;RFC 3794;DOI 10.17487/RFC3794;June;https://www.rfc-editor.org/info/rfc3794 | |
| RFC3795;;Sofia, R. and P. Nesser, II;Survey of IPv4 Addresses in Currently Deployed IETF Application Area Standards Track and Experimental Documents;;;;;RFC 3795;DOI 10.17487/RFC3795;June;https://www.rfc-editor.org/info/rfc3795 | |
| RFC3796;;Nesser, P., II, and A. Bergstrom, Ed.;Survey of IPv4 Addresses in Currently Deployed IETF Operations & Management Area Standards Track and Experimental Documents;;;;;RFC 3796;DOI 10.17487/RFC3796;June;https://www.rfc-editor.org/info/rfc3796 | |
| RFC3797;;Eastlake 3rd, D.;Publicly Verifiable Nominations Committee (NomCom) Random Selection;;;;;RFC 3797;DOI 10.17487/RFC3797;June;https://www.rfc-editor.org/info/rfc3797 | |
| RFC3798;RFC8098;Hansen, T., Ed., and G. Vaudreuil, Ed.;Message Disposition Notification;;;;;RFC 3798;DOI 10.17487/RFC3798;May;https://www.rfc-editor.org/info/rfc3798 | |
| RFC3801;;Vaudreuil, G. and G. Parsons;Voice Profile for Internet Mail - version 2 (VPIMv2);;;;;RFC 3801;DOI 10.17487/RFC3801;June;https://www.rfc-editor.org/info/rfc3801 | |
| RFC3802;;Vaudreuil, G. and G. Parsons;Toll Quality Voice - 32 kbit/s Adaptive Differential Pulse Code Modulation (ADPCM) MIME Sub-type Registration;;;;;RFC 3802;DOI 10.17487/RFC3802;June;https://www.rfc-editor.org/info/rfc3802 | |
| RFC3803;;Vaudreuil, G. and G. Parsons;Content Duration MIME Header Definition;;;;;RFC 3803;DOI 10.17487/RFC3803;June;https://www.rfc-editor.org/info/rfc3803 | |
| RFC3804;;Parsons, G.;Voice Profile for Internet Mail (VPIM) Addressing;;;;;RFC 3804;DOI 10.17487/RFC3804;June;https://www.rfc-editor.org/info/rfc3804 | |
| RFC3805;;Bergman, R., Lewis, H., and I. McDonald;Printer MIB v2;;;;;RFC 3805;DOI 10.17487/RFC3805;June;https://www.rfc-editor.org/info/rfc3805 | |
| RFC3806;;Bergman, R., Lewis, H., and I. McDonald;Printer Finishing MIB;;;;;RFC 3806;DOI 10.17487/RFC3806;June;https://www.rfc-editor.org/info/rfc3806 | |
| RFC3807;;Weilandt, E., Khanchandani, N., and S. Rao;V5.2-User Adaptation Layer (V5UA);;;;;RFC 3807;DOI 10.17487/RFC3807;June;https://www.rfc-editor.org/info/rfc3807 | |
| RFC3808;;McDonald, I.;IANA Charset MIB;;;;;RFC 3808;DOI 10.17487/RFC3808;June;https://www.rfc-editor.org/info/rfc3808 | |
| RFC3809;;Nagarajan, A., Ed.;Generic Requirements for Provider Provisioned Virtual Private Networks (PPVPN);;;;;RFC 3809;DOI 10.17487/RFC3809;June;https://www.rfc-editor.org/info/rfc3809 | |
| RFC3810;;Vida, R., Ed., and L. Costa, Ed.;Multicast Listener Discovery Version 2 (MLDv2) for IPv6;;;;;RFC 3810;DOI 10.17487/RFC3810;June;https://www.rfc-editor.org/info/rfc3810 | |
| RFC3811;;Nadeau, T., Ed., and J. Cucchiara, Ed.;Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management;;;;;RFC 3811;DOI 10.17487/RFC3811;June;https://www.rfc-editor.org/info/rfc3811 | |
| RFC3812;;Srinivasan, C., Viswanathan, A., and T. Nadeau;Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB);;;;;RFC 3812;DOI 10.17487/RFC3812;June;https://www.rfc-editor.org/info/rfc3812 | |
| RFC3813;;Srinivasan, C., Viswanathan, A., and T. Nadeau;Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB);;;;;RFC 3813;DOI 10.17487/RFC3813;June;https://www.rfc-editor.org/info/rfc3813 | |
| RFC3814;;Nadeau, T., Srinivasan, C., and A. Viswanathan;Multiprotocol Label Switching (MPLS) Forwarding Equivalence Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE) Management Information Base (MIB);;;;;RFC 3814;DOI 10.17487/RFC3814;June;https://www.rfc-editor.org/info/rfc3814 | |
| RFC3815;;Cucchiara, J., Sjostrand, H., and J. Luciani;Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP);;;;;RFC 3815;DOI 10.17487/RFC3815;June;https://www.rfc-editor.org/info/rfc3815 | |
| RFC3816;;Quittek, J., Stiemerling, M., and H. Hartenstein;Definitions of Managed Objects for RObust Header Compression (ROHC);;;;;RFC 3816;DOI 10.17487/RFC3816;June;https://www.rfc-editor.org/info/rfc3816 | |
| RFC3817;;Townsley, W. and R. da Silva;Layer 2 Tunneling Protocol (L2TP) Active Discovery Relay for PPP over Ethernet (PPPoE);;;;;RFC 3817;DOI 10.17487/RFC3817;June;https://www.rfc-editor.org/info/rfc3817 | |
| RFC3818;;Schryver, V.;IANA Considerations for the Point-to-Point Protocol (PPP);;;BCP 88;;RFC 3818;DOI 10.17487/RFC3818;June;https://www.rfc-editor.org/info/rfc3818 | |
| RFC3819;;Karn, P., Ed., Bormann, C., Fairhurst, G., Grossman, D., Ludwig, R., Mahdavi, J., Montenegro, G., Touch, J., and L. Wood;Advice for Internet Subnetwork Designers;;;BCP 89;;RFC 3819;DOI 10.17487/RFC3819;July;https://www.rfc-editor.org/info/rfc3819 | |
| RFC3820;;Tuecke, S., Welch, V., Engert, D., Pearlman, L., and M. Thompson;Internet X.509 Public Key Infrastructure (PKI) Proxy Certificate Profile;;;;;RFC 3820;DOI 10.17487/RFC3820;June;https://www.rfc-editor.org/info/rfc3820 | |
| RFC3821;;Rajagopal, M., Rodriguez, E., and R. Weber;Fibre Channel Over TCP/IP (FCIP);;;;;RFC 3821;DOI 10.17487/RFC3821;July;https://www.rfc-editor.org/info/rfc3821 | |
| RFC3822;;Peterson, D.;Finding Fibre Channel over TCP/IP (FCIP) Entities Using Service Location Protocol version 2 (SLPv2);;;;;RFC 3822;DOI 10.17487/RFC3822;July;https://www.rfc-editor.org/info/rfc3822 | |
| RFC3823;;Kovitz, B.;MIME Media Type for the Systems Biology Markup Language (SBML);;;;;RFC 3823;DOI 10.17487/RFC3823;June;https://www.rfc-editor.org/info/rfc3823 | |
| RFC3824;;Peterson, J., Liu, H., Yu, J., and B. Campbell;Using E.164 numbers with the Session Initiation Protocol (SIP);;;;;RFC 3824;DOI 10.17487/RFC3824;June;https://www.rfc-editor.org/info/rfc3824 | |
| RFC3825;RFC6225;Polk, J., Schnizlein, J., and M. Linsner;Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information;;;;;RFC 3825;DOI 10.17487/RFC3825;July;https://www.rfc-editor.org/info/rfc3825 | |
| RFC3826;;Blumenthal, U., Maino, F., and K. McCloghrie;The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model;;;;;RFC 3826;DOI 10.17487/RFC3826;June;https://www.rfc-editor.org/info/rfc3826 | |
| RFC3827;;Sarcar, K.;Additional Snoop Datalink Types;;;;;RFC 3827;DOI 10.17487/RFC3827;June;https://www.rfc-editor.org/info/rfc3827 | |
| RFC3828;;Larzon, L-A., Degermark, M., Pink, S., Jonsson, L-E., Ed., and G. Fairhurst, Ed.;The Lightweight User Datagram Protocol (UDP-Lite);;;;;RFC 3828;DOI 10.17487/RFC3828;July;https://www.rfc-editor.org/info/rfc3828 | |
| RFC3829;;Weltman, R., Smith, M., and M. Wahl;Lightweight Directory Access Protocol (LDAP) Authorization Identity Request and Response Controls;;;;;RFC 3829;DOI 10.17487/RFC3829;July;https://www.rfc-editor.org/info/rfc3829 | |
| RFC3830;;Arkko, J., Carrara, E., Lindholm, F., Naslund, M., and K. Norrman;MIKEY: Multimedia Internet KEYing;;;;;RFC 3830;DOI 10.17487/RFC3830;August;https://www.rfc-editor.org/info/rfc3830 | |
| RFC3831;RFC4338;DeSanti, C.;Transmission of IPv6 Packets over Fibre Channel;;;;;RFC 3831;DOI 10.17487/RFC3831;July;https://www.rfc-editor.org/info/rfc3831 | |
| RFC3832;;Zhao, W., Schulzrinne, H., Guttman, E., Bisdikian, C., and W. Jerome;Remote Service Discovery in the Service Location Protocol (SLP) via DNS SRV;;;;;RFC 3832;DOI 10.17487/RFC3832;July;https://www.rfc-editor.org/info/rfc3832 | |
| RFC3833;;Atkins, D. and R. Austein;Threat Analysis of the Domain Name System (DNS);;;;;RFC 3833;DOI 10.17487/RFC3833;August;https://www.rfc-editor.org/info/rfc3833 | |
| RFC3834;;Moore, K.;Recommendations for Automatic Responses to Electronic Mail;;;;;RFC 3834;DOI 10.17487/RFC3834;August;https://www.rfc-editor.org/info/rfc3834 | |
| RFC3835;;Barbir, A., Penno, R., Chen, R., Hofmann, M., and H. Orman;An Architecture for Open Pluggable Edge Services (OPES);;;;;RFC 3835;DOI 10.17487/RFC3835;August;https://www.rfc-editor.org/info/rfc3835 | |
| RFC3836;;Beck, A., Hofmann, M., Orman, H., Penno, R., and A. Terzis;Requirements for Open Pluggable Edge Services (OPES) Callout Protocols;;;;;RFC 3836;DOI 10.17487/RFC3836;August;https://www.rfc-editor.org/info/rfc3836 | |
| RFC3837;;Barbir, A., Batuner, O., Srinivas, B., Hofmann, M., and H. Orman;Security Threats and Risks for Open Pluggable Edge Services (OPES);;;;;RFC 3837;DOI 10.17487/RFC3837;August;https://www.rfc-editor.org/info/rfc3837 | |
| RFC3838;;Barbir, A., Batuner, O., Beck, A., Chan, T., and H. Orman;Policy, Authorization, and Enforcement Requirements of the Open Pluggable Edge Services (OPES);;;;;RFC 3838;DOI 10.17487/RFC3838;August;https://www.rfc-editor.org/info/rfc3838 | |
| RFC3839;;Castagno, R. and D. Singer;MIME Type Registrations for 3rd Generation Partnership Project (3GPP) Multimedia files;;;;;RFC 3839;DOI 10.17487/RFC3839;July;https://www.rfc-editor.org/info/rfc3839 | |
| RFC3840;;Rosenberg, J., Schulzrinne, H., and P. Kyzivat;Indicating User Agent Capabilities in the Session Initiation Protocol (SIP);;;;;RFC 3840;DOI 10.17487/RFC3840;August;https://www.rfc-editor.org/info/rfc3840 | |
| RFC3841;;Rosenberg, J., Schulzrinne, H., and P. Kyzivat;Caller Preferences for the Session Initiation Protocol (SIP);;;;;RFC 3841;DOI 10.17487/RFC3841;August;https://www.rfc-editor.org/info/rfc3841 | |
| RFC3842;;Mahy, R.;A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP);;;;;RFC 3842;DOI 10.17487/RFC3842;August;https://www.rfc-editor.org/info/rfc3842 | |
| RFC3843;;Jonsson, L-E. and G. Pelletier;RObust Header Compression (ROHC): A Compression Profile for IP;;;;;RFC 3843;DOI 10.17487/RFC3843;June;https://www.rfc-editor.org/info/rfc3843 | |
| RFC3844;;Davies, E., Ed., and J. Hofmann, Ed.;IETF Problem Resolution Process;;;;;RFC 3844;DOI 10.17487/RFC3844;August;https://www.rfc-editor.org/info/rfc3844 | |
| RFC3845;RFC4033, RFC4034, RFC4035;Schlyter, J., Ed.;DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format;;;;;RFC 3845;DOI 10.17487/RFC3845;August;https://www.rfc-editor.org/info/rfc3845 | |
| RFC3846;;Johansson, F. and T. Johansson;Mobile IPv4 Extension for Carrying Network Access Identifiers;;;;;RFC 3846;DOI 10.17487/RFC3846;June;https://www.rfc-editor.org/info/rfc3846 | |
| RFC3847;RFC5306;Shand, M. and L. Ginsberg;Restart Signaling for Intermediate System to Intermediate System (IS-IS);;;;;RFC 3847;DOI 10.17487/RFC3847;July;https://www.rfc-editor.org/info/rfc3847 | |
| RFC3848;;Newman, C.;ESMTP and LMTP Transmission Types Registration;;;;;RFC 3848;DOI 10.17487/RFC3848;July;https://www.rfc-editor.org/info/rfc3848 | |
| RFC3849;;Huston, G., Lord, A., and P. Smith;IPv6 Address Prefix Reserved for Documentation;;;;;RFC 3849;DOI 10.17487/RFC3849;July;https://www.rfc-editor.org/info/rfc3849 | |
| RFC3850;RFC5750;Ramsdell, B., Ed.;Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Certificate Handling;;;;;RFC 3850;DOI 10.17487/RFC3850;July;https://www.rfc-editor.org/info/rfc3850 | |
| RFC3851;RFC5751;Ramsdell, B., Ed.;Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification;;;;;RFC 3851;DOI 10.17487/RFC3851;July;https://www.rfc-editor.org/info/rfc3851 | |
| RFC3852;RFC5652;Housley, R.;Cryptographic Message Syntax (CMS);;;;;RFC 3852;DOI 10.17487/RFC3852;July;https://www.rfc-editor.org/info/rfc3852 | |
| RFC3853;;Peterson, J.;S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP);;;;;RFC 3853;DOI 10.17487/RFC3853;July;https://www.rfc-editor.org/info/rfc3853 | |
| RFC3854;;Hoffman, P., Bonatti, C., and A. Eggen;Securing X.400 Content with Secure/Multipurpose Internet Mail Extensions (S/MIME);;;;;RFC 3854;DOI 10.17487/RFC3854;July;https://www.rfc-editor.org/info/rfc3854 | |
| RFC3855;;Hoffman, P. and C. Bonatti;Transporting Secure/Multipurpose Internet Mail Extensions (S/MIME) Objects in X.400;;;;;RFC 3855;DOI 10.17487/RFC3855;July;https://www.rfc-editor.org/info/rfc3855 | |
| RFC3856;;Rosenberg, J.;A Presence Event Package for the Session Initiation Protocol (SIP);;;;;RFC 3856;DOI 10.17487/RFC3856;August;https://www.rfc-editor.org/info/rfc3856 | |
| RFC3857;;Rosenberg, J.;A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP);;;;;RFC 3857;DOI 10.17487/RFC3857;August;https://www.rfc-editor.org/info/rfc3857 | |
| RFC3858;;Rosenberg, J.;An Extensible Markup Language (XML) Based Format for Watcher Information;;;;;RFC 3858;DOI 10.17487/RFC3858;August;https://www.rfc-editor.org/info/rfc3858 | |
| RFC3859;;Peterson, J.;Common Profile for Presence (CPP);;;;;RFC 3859;DOI 10.17487/RFC3859;August;https://www.rfc-editor.org/info/rfc3859 | |
| RFC3860;;Peterson, J.;Common Profile for Instant Messaging (CPIM);;;;;RFC 3860;DOI 10.17487/RFC3860;August;https://www.rfc-editor.org/info/rfc3860 | |
| RFC3861;;Peterson, J.;Address Resolution for Instant Messaging and Presence;;;;;RFC 3861;DOI 10.17487/RFC3861;August;https://www.rfc-editor.org/info/rfc3861 | |
| RFC3862;;Klyne, G. and D. Atkins;Common Presence and Instant Messaging (CPIM): Message Format;;;;;RFC 3862;DOI 10.17487/RFC3862;August;https://www.rfc-editor.org/info/rfc3862 | |
| RFC3863;;Sugano, H., Fujimoto, S., Klyne, G., Bateman, A., Carr, W., and J. Peterson;Presence Information Data Format (PIDF);;;;;RFC 3863;DOI 10.17487/RFC3863;August;https://www.rfc-editor.org/info/rfc3863 | |
| RFC3864;;Klyne, G., Nottingham, M., and J. Mogul;Registration Procedures for Message Header Fields;;;BCP 90;;RFC 3864;DOI 10.17487/RFC3864;September;https://www.rfc-editor.org/info/rfc3864 | |
| RFC3865;;Malamud, C.;A No Soliciting Simple Mail Transfer Protocol (SMTP) Service Extension;;;;;RFC 3865;DOI 10.17487/RFC3865;September;https://www.rfc-editor.org/info/rfc3865 | |
| RFC3866;;Zeilenga, K., Ed.;Language Tags and Ranges in the Lightweight Directory Access Protocol (LDAP);;;;;RFC 3866;DOI 10.17487/RFC3866;July;https://www.rfc-editor.org/info/rfc3866 | |
| RFC3867;;Kawatsura, Y., Hiroya, M., and H. Beykirch;Payment Application Programmers Interface (API) for v1.0 Internet Open Trading Protocol (IOTP);;;;;RFC 3867;DOI 10.17487/RFC3867;November;https://www.rfc-editor.org/info/rfc3867 | |
| RFC3868;;Loughney, J., Ed., Sidebottom, G., Coene, L., Verwimp, G., Keller, J., and B. Bidulock;Signalling Connection Control Part User Adaptation Layer (SUA);;;;;RFC 3868;DOI 10.17487/RFC3868;October;https://www.rfc-editor.org/info/rfc3868 | |
| RFC3869;;Atkinson, R., Ed., Floyd, S., Ed., and Internet Architecture Board;IAB Concerns and Recommendations Regarding Internet Research and Evolution;;;;;RFC 3869;DOI 10.17487/RFC3869;August;https://www.rfc-editor.org/info/rfc3869 | |
| RFC3870;;Swartz, A.;application/rdf+xml Media Type Registration;;;;;RFC 3870;DOI 10.17487/RFC3870;September;https://www.rfc-editor.org/info/rfc3870 | |
| RFC3871;;Jones, G., Ed.;Operational Security Requirements for Large Internet Service Provider (ISP) IP Network Infrastructure;;;;;RFC 3871;DOI 10.17487/RFC3871;September;https://www.rfc-editor.org/info/rfc3871 | |
| RFC3872;;Zinman, D., Walker, D., and J. Jiang;Management Information Base for Telephony Routing over IP (TRIP);;;;;RFC 3872;DOI 10.17487/RFC3872;September;https://www.rfc-editor.org/info/rfc3872 | |
| RFC3873;;Pastor, J. and M. Belinchon;Stream Control Transmission Protocol (SCTP) Management Information Base (MIB);;;;;RFC 3873;DOI 10.17487/RFC3873;September;https://www.rfc-editor.org/info/rfc3873 | |
| RFC3874;;Housley, R.;A 224-bit One-way Hash Function: SHA-224;;;;;RFC 3874;DOI 10.17487/RFC3874;September;https://www.rfc-editor.org/info/rfc3874 | |
| RFC3875;;Robinson, D. and K. Coar;The Common Gateway Interface (CGI) Version 1.1;;;;;RFC 3875;DOI 10.17487/RFC3875;October;https://www.rfc-editor.org/info/rfc3875 | |
| RFC3876;;Chadwick, D. and S. Mullan;Returning Matched Values with the Lightweight Directory Access Protocol version 3 (LDAPv3);;;;;RFC 3876;DOI 10.17487/RFC3876;September;https://www.rfc-editor.org/info/rfc3876 | |
| RFC3877;;Chisholm, S. and D. Romascanu;Alarm Management Information Base (MIB);;;;;RFC 3877;DOI 10.17487/RFC3877;September;https://www.rfc-editor.org/info/rfc3877 | |
| RFC3878;;Lam, H., Huynh, A., and D. Perkins;Alarm Reporting Control Management Information Base (MIB);;;;;RFC 3878;DOI 10.17487/RFC3878;September;https://www.rfc-editor.org/info/rfc3878 | |
| RFC3879;;Huitema, C. and B. Carpenter;Deprecating Site Local Addresses;;;;;RFC 3879;DOI 10.17487/RFC3879;September;https://www.rfc-editor.org/info/rfc3879 | |
| RFC3880;;Lennox, J., Wu, X., and H. Schulzrinne;Call Processing Language (CPL): A Language for User Control of Internet Telephony Services;;;;;RFC 3880;DOI 10.17487/RFC3880;October;https://www.rfc-editor.org/info/rfc3880 | |
| RFC3881;;Marshall, G.;Security Audit and Access Accountability Message XML Data Definitions for Healthcare Applications;;;;;RFC 3881;DOI 10.17487/RFC3881;September;https://www.rfc-editor.org/info/rfc3881 | |
| RFC3882;;Turk, D.;Configuring BGP to Block Denial-of-Service Attacks;;;;;RFC 3882;DOI 10.17487/RFC3882;September;https://www.rfc-editor.org/info/rfc3882 | |
| RFC3883;;Rao, S., Zinin, A., and A. Roy;Detecting Inactive Neighbors over OSPF Demand Circuits (DC);;;;;RFC 3883;DOI 10.17487/RFC3883;October;https://www.rfc-editor.org/info/rfc3883 | |
| RFC3884;;Touch, J., Eggert, L., and Y. Wang;Use of IPsec Transport Mode for Dynamic Routing;;;;;RFC 3884;DOI 10.17487/RFC3884;September;https://www.rfc-editor.org/info/rfc3884 | |
| RFC3885;;Allman, E. and T. Hansen;SMTP Service Extension for Message Tracking;;;;;RFC 3885;DOI 10.17487/RFC3885;September;https://www.rfc-editor.org/info/rfc3885 | |
| RFC3886;;Allman, E.;An Extensible Message Format for Message Tracking Responses;;;;;RFC 3886;DOI 10.17487/RFC3886;September;https://www.rfc-editor.org/info/rfc3886 | |
| RFC3887;;Hansen, T.;Message Tracking Query Protocol;;;;;RFC 3887;DOI 10.17487/RFC3887;September;https://www.rfc-editor.org/info/rfc3887 | |
| RFC3888;;Hansen, T.;Message Tracking Model and Requirements;;;;;RFC 3888;DOI 10.17487/RFC3888;September;https://www.rfc-editor.org/info/rfc3888 | |
| RFC3890;;Westerlund, M.;A Transport Independent Bandwidth Modifier for the Session Description Protocol (SDP);;;;;RFC 3890;DOI 10.17487/RFC3890;September;https://www.rfc-editor.org/info/rfc3890 | |
| RFC3891;;Mahy, R., Biggs, B., and R. Dean;The Session Initiation Protocol (SIP) "Replaces" Header;;;;;RFC 3891;DOI 10.17487/RFC3891;September;https://www.rfc-editor.org/info/rfc3891 | |
| RFC3892;;Sparks, R.;The Session Initiation Protocol (SIP) Referred-By Mechanism;;;;;RFC 3892;DOI 10.17487/RFC3892;September;https://www.rfc-editor.org/info/rfc3892 | |
| RFC3893;;Peterson, J.;Session Initiation Protocol (SIP) Authenticated Identity Body (AIB) Format;;;;;RFC 3893;DOI 10.17487/RFC3893;September;https://www.rfc-editor.org/info/rfc3893 | |
| RFC3894;;Degener, J.;Sieve Extension: Copying Without Side Effects;;;;;RFC 3894;DOI 10.17487/RFC3894;October;https://www.rfc-editor.org/info/rfc3894 | |
| RFC3895;RFC4805;Nicklass, O., Ed.;Definitions of Managed Objects for the DS1, E1, DS2, and E2 Interface Types;;;;;RFC 3895;DOI 10.17487/RFC3895;September;https://www.rfc-editor.org/info/rfc3895 | |
| RFC3896;;Nicklass, O., Ed.;Definitions of Managed Objects for the DS3/E3 Interface Type;;;;;RFC 3896;DOI 10.17487/RFC3896;September;https://www.rfc-editor.org/info/rfc3896 | |
| RFC3897;;Barbir, A.;Open Pluggable Edge Services (OPES) Entities and End Points Communication;;;;;RFC 3897;DOI 10.17487/RFC3897;September;https://www.rfc-editor.org/info/rfc3897 | |
| RFC3898;;Kalusivalingam, V.;Network Information Service (NIS) Configuration Options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6);;;;;RFC 3898;DOI 10.17487/RFC3898;October;https://www.rfc-editor.org/info/rfc3898 | |
| RFC3901;;Durand, A. and J. Ihren;DNS IPv6 Transport Operational Guidelines;;;BCP 91;;RFC 3901;DOI 10.17487/RFC3901;September;https://www.rfc-editor.org/info/rfc3901 | |
| RFC3902;;Baker, M. and M. Nottingham;The "application/soap+xml" media type;;;;;RFC 3902;DOI 10.17487/RFC3902;September;https://www.rfc-editor.org/info/rfc3902 | |
| RFC3903;;Niemi, A., Ed.;Session Initiation Protocol (SIP) Extension for Event State Publication;;;;;RFC 3903;DOI 10.17487/RFC3903;October;https://www.rfc-editor.org/info/rfc3903 | |
| RFC3904;;Huitema, C., Austein, R., Satapati, S., and R. van der Pol;Evaluation of IPv6 Transition Mechanisms for Unmanaged Networks;;;;;RFC 3904;DOI 10.17487/RFC3904;September;https://www.rfc-editor.org/info/rfc3904 | |
| RFC3905;;See, V., Ed.;A Template for IETF Patent Disclosures and Licensing Declarations;;;;;RFC 3905;DOI 10.17487/RFC3905;September;https://www.rfc-editor.org/info/rfc3905 | |
| RFC3906;;Shen, N. and H. Smit;Calculating Interior Gateway Protocol (IGP) Routes Over Traffic Engineering Tunnels;;;;;RFC 3906;DOI 10.17487/RFC3906;October;https://www.rfc-editor.org/info/rfc3906 | |
| RFC3909;;Zeilenga, K.;Lightweight Directory Access Protocol (LDAP) Cancel Operation;;;;;RFC 3909;DOI 10.17487/RFC3909;October;https://www.rfc-editor.org/info/rfc3909 | |
| RFC3910;;Gurbani, V., Ed., Brusilovsky, A., Faynberg, I., Gato, J., Lu, H., and M. Unmehopa;The SPIRITS (Services in PSTN requesting Internet Services) Protocol;;;;;RFC 3910;DOI 10.17487/RFC3910;October;https://www.rfc-editor.org/info/rfc3910 | |
| RFC3911;;Mahy, R. and D. Petrie;The Session Initiation Protocol (SIP) "Join" Header;;;;;RFC 3911;DOI 10.17487/RFC3911;October;https://www.rfc-editor.org/info/rfc3911 | |
| RFC3912;;Daigle, L.;WHOIS Protocol Specification;;;;;RFC 3912;DOI 10.17487/RFC3912;September;https://www.rfc-editor.org/info/rfc3912 | |
| RFC3913;;Thaler, D.;Border Gateway Multicast Protocol (BGMP): Protocol Specification;;;;;RFC 3913;DOI 10.17487/RFC3913;September;https://www.rfc-editor.org/info/rfc3913 | |
| RFC3914;;Barbir, A. and A. Rousskov;Open Pluggable Edge Services (OPES) Treatment of IAB Considerations;;;;;RFC 3914;DOI 10.17487/RFC3914;October;https://www.rfc-editor.org/info/rfc3914 | |
| RFC3915;;Hollenbeck, S.;Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP);;;;;RFC 3915;DOI 10.17487/RFC3915;September;https://www.rfc-editor.org/info/rfc3915 | |
| RFC3916;;Xiao, X., Ed., McPherson, D., Ed., and P. Pate, Ed.;Requirements for Pseudo-Wire Emulation Edge-to-Edge (PWE3);;;;;RFC 3916;DOI 10.17487/RFC3916;September;https://www.rfc-editor.org/info/rfc3916 | |
| RFC3917;;Quittek, J., Zseby, T., Claise, B., and S. Zander;Requirements for IP Flow Information Export (IPFIX);;;;;RFC 3917;DOI 10.17487/RFC3917;October;https://www.rfc-editor.org/info/rfc3917 | |
| RFC3918;;Stopp, D. and B. Hickman;Methodology for IP Multicast Benchmarking;;;;;RFC 3918;DOI 10.17487/RFC3918;October;https://www.rfc-editor.org/info/rfc3918 | |
| RFC3919;;Stephan, E. and J. Palet;Remote Network Monitoring (RMON) Protocol Identifiers for IPv6 and Multi Protocol Label Switching (MPLS);;;;;RFC 3919;DOI 10.17487/RFC3919;October;https://www.rfc-editor.org/info/rfc3919 | |
| RFC3920;RFC6120;Saint-Andre, P., Ed.;Extensible Messaging and Presence Protocol (XMPP): Core;;;;;RFC 3920;DOI 10.17487/RFC3920;October;https://www.rfc-editor.org/info/rfc3920 | |
| RFC3921;RFC6121;Saint-Andre, P., Ed.;Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence;;;;;RFC 3921;DOI 10.17487/RFC3921;October;https://www.rfc-editor.org/info/rfc3921 | |
| RFC3922;;Saint-Andre, P.;Mapping the Extensible Messaging and Presence Protocol (XMPP) to Common Presence and Instant Messaging (CPIM);;;;;RFC 3922;DOI 10.17487/RFC3922;October;https://www.rfc-editor.org/info/rfc3922 | |
| RFC3923;;Saint-Andre, P.;End-to-End Signing and Object Encryption for the Extensible Messaging and Presence Protocol (XMPP);;;;;RFC 3923;DOI 10.17487/RFC3923;October;https://www.rfc-editor.org/info/rfc3923 | |
| RFC3924;;Baker, F., Foster, B., and C. Sharp;Cisco Architecture for Lawful Intercept in IP Networks;;;;;RFC 3924;DOI 10.17487/RFC3924;October;https://www.rfc-editor.org/info/rfc3924 | |
| RFC3925;;Littlefield, J.;Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4);;;;;RFC 3925;DOI 10.17487/RFC3925;October;https://www.rfc-editor.org/info/rfc3925 | |
| RFC3926;RFC6726;Paila, T., Luby, M., Lehtonen, R., Roca, V., and R. Walsh;FLUTE - File Delivery over Unidirectional Transport;;;;;RFC 3926;DOI 10.17487/RFC3926;October;https://www.rfc-editor.org/info/rfc3926 | |
| RFC3927;;Cheshire, S., Aboba, B., and E. Guttman;Dynamic Configuration of IPv4 Link-Local Addresses;;;;;RFC 3927;DOI 10.17487/RFC3927;May;https://www.rfc-editor.org/info/rfc3927 | |
| RFC3928;;Megginson, R., Ed., Smith, M., Natkovich, O., and J. Parham;Lightweight Directory Access Protocol (LDAP) Client Update Protocol (LCUP);;;;;RFC 3928;DOI 10.17487/RFC3928;October;https://www.rfc-editor.org/info/rfc3928 | |
| RFC3929;;Hardie, T.;Alternative Decision Making Processes for Consensus-Blocked Decisions in the IETF;;;;;RFC 3929;DOI 10.17487/RFC3929;October;https://www.rfc-editor.org/info/rfc3929 | |
| RFC3930;;Eastlake 3rd, D.;The Protocol versus Document Points of View in Computer Protocols;;;;;RFC 3930;DOI 10.17487/RFC3930;October;https://www.rfc-editor.org/info/rfc3930 | |
| RFC3931;;Lau, J., Ed., Townsley, M., Ed., and I. Goyret, Ed.;Layer Two Tunneling Protocol - Version 3 (L2TPv3);;;;;RFC 3931;DOI 10.17487/RFC3931;March;https://www.rfc-editor.org/info/rfc3931 | |
| RFC3932;RFC5742;Alvestrand, H.;The IESG and RFC Editor Documents: Procedures;;;;;RFC 3932;DOI 10.17487/RFC3932;October;https://www.rfc-editor.org/info/rfc3932 | |
| RFC3933;;Klensin, J. and S. Dawkins;A Model for IETF Process Experiments;;;BCP 93;;RFC 3933;DOI 10.17487/RFC3933;November;https://www.rfc-editor.org/info/rfc3933 | |
| RFC3934;;Wasserman, M.;Updates to RFC 2418 Regarding the Management of IETF Mailing Lists;;;BCP 25;;RFC 3934;DOI 10.17487/RFC3934;October;https://www.rfc-editor.org/info/rfc3934 | |
| RFC3935;;Alvestrand, H.;A Mission Statement for the IETF;;;BCP 95;;RFC 3935;DOI 10.17487/RFC3935;October;https://www.rfc-editor.org/info/rfc3935 | |
| RFC3936;;Kompella, K. and J. Lang;Procedures for Modifying the Resource reSerVation Protocol (RSVP);;;BCP 96;;RFC 3936;DOI 10.17487/RFC3936;October;https://www.rfc-editor.org/info/rfc3936 | |
| RFC3937;;Steidl, M.;A Uniform Resource Name (URN) Namespace for the International Press Telecommunications Council (IPTC);;;;;RFC 3937;DOI 10.17487/RFC3937;October;https://www.rfc-editor.org/info/rfc3937 | |
| RFC3938;;Hansen, T.;Video-Message Message-Context;;;;;RFC 3938;DOI 10.17487/RFC3938;October;https://www.rfc-editor.org/info/rfc3938 | |
| RFC3939;;Parsons, G. and J. Maruszak;Calling Line Identification for Voice Mail Messages;;;;;RFC 3939;DOI 10.17487/RFC3939;December;https://www.rfc-editor.org/info/rfc3939 | |
| RFC3940;RFC5740;Adamson, B., Bormann, C., Handley, M., and J. Macker;Negative-acknowledgment (NACK)-Oriented Reliable Multicast (NORM) Protocol;;;;;RFC 3940;DOI 10.17487/RFC3940;November;https://www.rfc-editor.org/info/rfc3940 | |
| RFC3941;RFC5401;Adamson, B., Bormann, C., Handley, M., and J. Macker;Negative-Acknowledgment (NACK)-Oriented Reliable Multicast (NORM) Building Blocks;;;;;RFC 3941;DOI 10.17487/RFC3941;November;https://www.rfc-editor.org/info/rfc3941 | |
| RFC3942;;Volz, B.;Reclassifying Dynamic Host Configuration Protocol version 4 (DHCPv4) Options;;;;;RFC 3942;DOI 10.17487/RFC3942;November;https://www.rfc-editor.org/info/rfc3942 | |
| RFC3943;;Friend, R.;Transport Layer Security (TLS) Protocol Compression Using Lempel-Ziv-Stac (LZS);;;;;RFC 3943;DOI 10.17487/RFC3943;November;https://www.rfc-editor.org/info/rfc3943 | |
| RFC3944;;Johnson, T., Okubo, S., and S. Campos;H.350 Directory Services;;;;;RFC 3944;DOI 10.17487/RFC3944;December;https://www.rfc-editor.org/info/rfc3944 | |
| RFC3945;;Mannie, E., Ed.;Generalized Multi-Protocol Label Switching (GMPLS) Architecture;;;;;RFC 3945;DOI 10.17487/RFC3945;October;https://www.rfc-editor.org/info/rfc3945 | |
| RFC3946;RFC4606;Mannie, E. and D. Papadimitriou;Generalized Multi-Protocol Label Switching (GMPLS) Extensions for Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) Control;;;;;RFC 3946;DOI 10.17487/RFC3946;October;https://www.rfc-editor.org/info/rfc3946 | |
| RFC3947;;Kivinen, T., Swander, B., Huttunen, A., and V. Volpe;Negotiation of NAT-Traversal in the IKE;;;;;RFC 3947;DOI 10.17487/RFC3947;January;https://www.rfc-editor.org/info/rfc3947 | |
| RFC3948;;Huttunen, A., Swander, B., Volpe, V., DiBurro, L., and M. Stenberg;UDP Encapsulation of IPsec ESP Packets;;;;;RFC 3948;DOI 10.17487/RFC3948;January;https://www.rfc-editor.org/info/rfc3948 | |
| RFC3949;;Buckley, R., Venable, D., McIntyre, L., Parsons, G., and J. Rafferty;File Format for Internet Fax;;;;;RFC 3949;DOI 10.17487/RFC3949;February;https://www.rfc-editor.org/info/rfc3949 | |
| RFC3950;;McIntyre, L., Parsons, G., and J. Rafferty;Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type Registration;;;;;RFC 3950;DOI 10.17487/RFC3950;February;https://www.rfc-editor.org/info/rfc3950 | |
| RFC3951;;Andersen, S., Duric, A., Astrom, H., Hagen, R., Kleijn, W., and J. Linden;Internet Low Bit Rate Codec (iLBC);;;;;RFC 3951;DOI 10.17487/RFC3951;December;https://www.rfc-editor.org/info/rfc3951 | |
| RFC3952;;Duric, A. and S. Andersen;Real-time Transport Protocol (RTP) Payload Format for internet Low Bit Rate Codec (iLBC) Speech;;;;;RFC 3952;DOI 10.17487/RFC3952;December;https://www.rfc-editor.org/info/rfc3952 | |
| RFC3953;;Peterson, J.;Telephone Number Mapping (ENUM) Service Registration for Presence Services;;;;;RFC 3953;DOI 10.17487/RFC3953;January;https://www.rfc-editor.org/info/rfc3953 | |
| RFC3954;;Claise, B., Ed.;Cisco Systems NetFlow Services Export Version 9;;;;;RFC 3954;DOI 10.17487/RFC3954;October;https://www.rfc-editor.org/info/rfc3954 | |
| RFC3955;;Leinen, S.;Evaluation of Candidate Protocols for IP Flow Information Export (IPFIX);;;;;RFC 3955;DOI 10.17487/RFC3955;October;https://www.rfc-editor.org/info/rfc3955 | |
| RFC3956;;Savola, P. and B. Haberman;Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address;;;;;RFC 3956;DOI 10.17487/RFC3956;November;https://www.rfc-editor.org/info/rfc3956 | |
| RFC3957;;Perkins, C. and P. Calhoun;Authentication, Authorization, and Accounting (AAA) Registration Keys for Mobile IPv4;;;;;RFC 3957;DOI 10.17487/RFC3957;March;https://www.rfc-editor.org/info/rfc3957 | |
| RFC3958;;Daigle, L. and A. Newton;Domain-Based Application Service Location Using SRV RRs and the Dynamic Delegation Discovery Service (DDDS);;;;;RFC 3958;DOI 10.17487/RFC3958;January;https://www.rfc-editor.org/info/rfc3958 | |
| RFC3959;;Camarillo, G.;The Early Session Disposition Type for the Session Initiation Protocol (SIP);;;;;RFC 3959;DOI 10.17487/RFC3959;December;https://www.rfc-editor.org/info/rfc3959 | |
| RFC3960;;Camarillo, G. and H. Schulzrinne;Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP);;;;;RFC 3960;DOI 10.17487/RFC3960;December;https://www.rfc-editor.org/info/rfc3960 | |
| RFC3961;;Raeburn, K.;Encryption and Checksum Specifications for Kerberos 5;;;;;RFC 3961;DOI 10.17487/RFC3961;February;https://www.rfc-editor.org/info/rfc3961 | |
| RFC3962;;Raeburn, K.;Advanced Encryption Standard (AES) Encryption for Kerberos 5;;;;;RFC 3962;DOI 10.17487/RFC3962;February;https://www.rfc-editor.org/info/rfc3962 | |
| RFC3963;;Devarapalli, V., Wakikawa, R., Petrescu, A., and P. Thubert;Network Mobility (NEMO) Basic Support Protocol;;;;;RFC 3963;DOI 10.17487/RFC3963;January;https://www.rfc-editor.org/info/rfc3963 | |
| RFC3964;;Savola, P. and C. Patel;Security Considerations for 6to4;;;;;RFC 3964;DOI 10.17487/RFC3964;December;https://www.rfc-editor.org/info/rfc3964 | |
| RFC3965;;Toyoda, K., Ohno, H., Murai, J., and D. Wing;A Simple Mode of Facsimile Using Internet Mail;;;;;RFC 3965;DOI 10.17487/RFC3965;December;https://www.rfc-editor.org/info/rfc3965 | |
| RFC3966;;Schulzrinne, H.;The tel URI for Telephone Numbers;;;;;RFC 3966;DOI 10.17487/RFC3966;December;https://www.rfc-editor.org/info/rfc3966 | |
| RFC3967;;Bush, R. and T. Narten;Clarifying when Standards Track Documents may Refer Normatively to Documents at a Lower Level;;;BCP 97;;RFC 3967;DOI 10.17487/RFC3967;December;https://www.rfc-editor.org/info/rfc3967 | |
| RFC3968;;Camarillo, G.;The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP);;;BCP 98;;RFC 3968;DOI 10.17487/RFC3968;December;https://www.rfc-editor.org/info/rfc3968 | |
| RFC3969;;Camarillo, G.;The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP);;;BCP 99;;RFC 3969;DOI 10.17487/RFC3969;December;https://www.rfc-editor.org/info/rfc3969 | |
| RFC3970;;Kompella, K.;A Traffic Engineering (TE) MIB;;;;;RFC 3970;DOI 10.17487/RFC3970;January;https://www.rfc-editor.org/info/rfc3970 | |
| RFC3971;;Arkko, J., Ed., Kempf, J., Zill, B., and P. Nikander;SEcure Neighbor Discovery (SEND);;;;;RFC 3971;DOI 10.17487/RFC3971;March;https://www.rfc-editor.org/info/rfc3971 | |
| RFC3972;;Aura, T.;Cryptographically Generated Addresses (CGA);;;;;RFC 3972;DOI 10.17487/RFC3972;March;https://www.rfc-editor.org/info/rfc3972 | |
| RFC3973;;Adams, A., Nicholas, J., and W. Siadak;Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised);;;;;RFC 3973;DOI 10.17487/RFC3973;January;https://www.rfc-editor.org/info/rfc3973 | |
| RFC3974;;Nakamura, M. and J. Hagino;SMTP Operational Experience in Mixed IPv4/v6 Environments;;;;;RFC 3974;DOI 10.17487/RFC3974;January;https://www.rfc-editor.org/info/rfc3974 | |
| RFC3975;;Huston, G., Ed., and I. Leuca, Ed.;OMA-IETF Standardization Collaboration;;;;;RFC 3975;DOI 10.17487/RFC3975;January;https://www.rfc-editor.org/info/rfc3975 | |
| RFC3976;;Gurbani, V., Haerens, F., and V. Rastogi;Interworking SIP and Intelligent Network (IN) Applications;;;;;RFC 3976;DOI 10.17487/RFC3976;January;https://www.rfc-editor.org/info/rfc3976 | |
| RFC3977;;Feather, C.;Network News Transfer Protocol (NNTP);;;;;RFC 3977;DOI 10.17487/RFC3977;October;https://www.rfc-editor.org/info/rfc3977 | |
| RFC3978;RFC5378;Bradner, S., Ed.;IETF Rights in Contributions;;;;;RFC 3978;DOI 10.17487/RFC3978;March;https://www.rfc-editor.org/info/rfc3978 | |
| RFC3979;RFC8179;Bradner, S., Ed.;Intellectual Property Rights in IETF Technology;;;;;RFC 3979;DOI 10.17487/RFC3979;March;https://www.rfc-editor.org/info/rfc3979 | |
| RFC3980;RFC7143;Krueger, M., Chadalapaka, M., and R. Elliott;T11 Network Address Authority (NAA) Naming Format for iSCSI Node Names;;;;;RFC 3980;DOI 10.17487/RFC3980;February;https://www.rfc-editor.org/info/rfc3980 | |
| RFC3981;;Newton, A. and M. Sanz;IRIS: The Internet Registry Information Service (IRIS) Core Protocol;;;;;RFC 3981;DOI 10.17487/RFC3981;January;https://www.rfc-editor.org/info/rfc3981 | |
| RFC3982;;Newton, A. and M. Sanz;IRIS: A Domain Registry (dreg) Type for the Internet Registry Information Service (IRIS);;;;;RFC 3982;DOI 10.17487/RFC3982;January;https://www.rfc-editor.org/info/rfc3982 | |
| RFC3983;;Newton, A. and M. Sanz;Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP);;;;;RFC 3983;DOI 10.17487/RFC3983;January;https://www.rfc-editor.org/info/rfc3983 | |
| RFC3984;RFC6184;Wenger, S., Hannuksela, M., Stockhammer, T., Westerlund, M., and D. Singer;RTP Payload Format for H.264 Video;;;;;RFC 3984;DOI 10.17487/RFC3984;February;https://www.rfc-editor.org/info/rfc3984 | |
| RFC3985;;Bryant, S., Ed., and P. Pate, Ed.;Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture;;;;;RFC 3985;DOI 10.17487/RFC3985;March;https://www.rfc-editor.org/info/rfc3985 | |
| RFC3986;;Berners-Lee, T., Fielding, R., and L. Masinter;Uniform Resource Identifier (URI): Generic Syntax;;;;STD 66;RFC 3986;DOI 10.17487/RFC3986;January;https://www.rfc-editor.org/info/rfc3986 | |
| RFC3987;;Duerst, M. and M. Suignard;Internationalized Resource Identifiers (IRIs);;;;;RFC 3987;DOI 10.17487/RFC3987;January;https://www.rfc-editor.org/info/rfc3987 | |
| RFC3988;;Black, B. and K. Kompella;Maximum Transmission Unit Signalling Extensions for the Label Distribution Protocol;;;;;RFC 3988;DOI 10.17487/RFC3988;January;https://www.rfc-editor.org/info/rfc3988 | |
| RFC3989;RFC5189;Stiemerling, M., Quittek, J., and T. Taylor;Middlebox Communications (MIDCOM) Protocol Semantics;;;;;RFC 3989;DOI 10.17487/RFC3989;February;https://www.rfc-editor.org/info/rfc3989 | |
| RFC3990;;O'Hara, B., Calhoun, P., and J. Kempf;Configuration and Provisioning for Wireless Access Points (CAPWAP) Problem Statement;;;;;RFC 3990;DOI 10.17487/RFC3990;February;https://www.rfc-editor.org/info/rfc3990 | |
| RFC3991;;Foster, B. and F. Andreasen;Media Gateway Control Protocol (MGCP) Redirect and Reset Package;;;;;RFC 3991;DOI 10.17487/RFC3991;February;https://www.rfc-editor.org/info/rfc3991 | |
| RFC3992;;Foster, B. and F. Andreasen;Media Gateway Control Protocol (MGCP) Lockstep State Reporting Mechanism;;;;;RFC 3992;DOI 10.17487/RFC3992;February;https://www.rfc-editor.org/info/rfc3992 | |
| RFC3993;;Johnson, R., Palaniappan, T., and M. Stapp;Subscriber-ID Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option;;;;;RFC 3993;DOI 10.17487/RFC3993;March;https://www.rfc-editor.org/info/rfc3993 | |
| RFC3994;;Schulzrinne, H.;Indication of Message Composition for Instant Messaging;;;;;RFC 3994;DOI 10.17487/RFC3994;January;https://www.rfc-editor.org/info/rfc3994 | |
| RFC3995;;Herriot, R. and T. Hastings;Internet Printing Protocol (IPP): Event Notifications and Subscriptions;;;;;RFC 3995;DOI 10.17487/RFC3995;March;https://www.rfc-editor.org/info/rfc3995 | |
| RFC3996;;Herriot, R., Hastings, T., and H. Lewis;Internet Printing Protocol (IPP): The 'ippget' Delivery Method for Event Notifications;;;;;RFC 3996;DOI 10.17487/RFC3996;March;https://www.rfc-editor.org/info/rfc3996 | |
| RFC3997;;Hastings, T., Ed., deBry, R., and H. Lewis;Internet Printing Protocol (IPP): Requirements for IPP Notifications;;;;;RFC 3997;DOI 10.17487/RFC3997;March;https://www.rfc-editor.org/info/rfc3997 | |
| RFC3998;;Kugler, C., Lewis, H., and T. Hastings, Ed.;Internet Printing Protocol (IPP): Job and Printer Administrative Operations;;;;;RFC 3998;DOI 10.17487/RFC3998;March;https://www.rfc-editor.org/info/rfc3998 | |
| RFC4001;;Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder;Textual Conventions for Internet Network Addresses;;;;;RFC 4001;DOI 10.17487/RFC4001;February;https://www.rfc-editor.org/info/rfc4001 | |
| RFC4002;;Brandner, R., Conroy, L., and R. Stastny;IANA Registration for Enumservice 'web' and 'ft';;;;;RFC 4002;DOI 10.17487/RFC4002;February;https://www.rfc-editor.org/info/rfc4002 | |
| RFC4003;;Berger, L.;GMPLS Signaling Procedure for Egress Control;;;;;RFC 4003;DOI 10.17487/RFC4003;February;https://www.rfc-editor.org/info/rfc4003 | |
| RFC4004;;Calhoun, P., Johansson, T., Perkins, C., Hiller, T., Ed., and P. McCann;Diameter Mobile IPv4 Application;;;;;RFC 4004;DOI 10.17487/RFC4004;August;https://www.rfc-editor.org/info/rfc4004 | |
| RFC4005;RFC7155;Calhoun, P., Zorn, G., Spence, D., and D. Mitton;Diameter Network Access Server Application;;;;;RFC 4005;DOI 10.17487/RFC4005;August;https://www.rfc-editor.org/info/rfc4005 | |
| RFC4006;RFC8506;Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J. Loughney;Diameter Credit-Control Application;;;;;RFC 4006;DOI 10.17487/RFC4006;August;https://www.rfc-editor.org/info/rfc4006 | |
| RFC4007;;Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and B. Zill;IPv6 Scoped Address Architecture;;;;;RFC 4007;DOI 10.17487/RFC4007;March;https://www.rfc-editor.org/info/rfc4007 | |
| RFC4008;RFC7658;Rohit, R., Srisuresh, P., Raghunarayan, R., Pai, N., and C. Wang;Definitions of Managed Objects for Network Address Translators (NAT);;;;;RFC 4008;DOI 10.17487/RFC4008;March;https://www.rfc-editor.org/info/rfc4008 | |
| RFC4009;RFC4269;Park, J., Lee, S., Kim, J., and J. Lee;The SEED Encryption Algorithm;;;;;RFC 4009;DOI 10.17487/RFC4009;February;https://www.rfc-editor.org/info/rfc4009 | |
| RFC4010;;Park, J., Lee, S., Kim, J., and J. Lee;Use of the SEED Encryption Algorithm in Cryptographic Message Syntax (CMS);;;;;RFC 4010;DOI 10.17487/RFC4010;February;https://www.rfc-editor.org/info/rfc4010 | |
| RFC4011;;Waldbusser, S., Saperia, J., and T. Hongal;Policy Based Management MIB;;;;;RFC 4011;DOI 10.17487/RFC4011;March;https://www.rfc-editor.org/info/rfc4011 | |
| RFC4012;;Blunk, L., Damas, J., Parent, F., and A. Robachevsky;Routing Policy Specification Language next generation (RPSLng);;;;;RFC 4012;DOI 10.17487/RFC4012;March;https://www.rfc-editor.org/info/rfc4012 | |
| RFC4013;RFC7613;Zeilenga, K.;SASLprep: Stringprep Profile for User Names and Passwords;;;;;RFC 4013;DOI 10.17487/RFC4013;February;https://www.rfc-editor.org/info/rfc4013 | |
| RFC4014;;Droms, R. and J. Schnizlein;Remote Authentication Dial-In User Service (RADIUS) Attributes Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Information Option;;;;;RFC 4014;DOI 10.17487/RFC4014;February;https://www.rfc-editor.org/info/rfc4014 | |
| RFC4015;;Ludwig, R. and A. Gurtov;The Eifel Response Algorithm for TCP;;;;;RFC 4015;DOI 10.17487/RFC4015;February;https://www.rfc-editor.org/info/rfc4015 | |
| RFC4016;;Parthasarathy, M.;Protocol for Carrying Authentication and Network Access (PANA) Threat Analysis and Security Requirements;;;;;RFC 4016;DOI 10.17487/RFC4016;March;https://www.rfc-editor.org/info/rfc4016 | |
| RFC4017;;Stanley, D., Walker, J., and B. Aboba;Extensible Authentication Protocol (EAP) Method Requirements for Wireless LANs;;;;;RFC 4017;DOI 10.17487/RFC4017;March;https://www.rfc-editor.org/info/rfc4017 | |
| RFC4018;;Bakke, M., Hufferd, J., Voruganti, K., Krueger, M., and T. Sperry;Finding Internet Small Computer Systems Interface (iSCSI) Targets and Name Servers by Using Service Location Protocol version 2 (SLPv2);;;;;RFC 4018;DOI 10.17487/RFC4018;April;https://www.rfc-editor.org/info/rfc4018 | |
| RFC4019;;Pelletier, G.;RObust Header Compression (ROHC): Profiles for User Datagram Protocol (UDP) Lite;;;;;RFC 4019;DOI 10.17487/RFC4019;April;https://www.rfc-editor.org/info/rfc4019 | |
| RFC4020;RFC7120;Kompella, K. and A. Zinin;Early IANA Allocation of Standards Track Code Points;;;;;RFC 4020;DOI 10.17487/RFC4020;February;https://www.rfc-editor.org/info/rfc4020 | |
| RFC4021;;Klyne, G. and J. Palme;Registration of Mail and MIME Header Fields;;;;;RFC 4021;DOI 10.17487/RFC4021;March;https://www.rfc-editor.org/info/rfc4021 | |
| RFC4022;;Raghunarayan, R., Ed.;Management Information Base for the Transmission Control Protocol (TCP);;;;;RFC 4022;DOI 10.17487/RFC4022;March;https://www.rfc-editor.org/info/rfc4022 | |
| RFC4023;;Worster, T., Rekhter, Y., and E. Rosen, Ed.;Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE);;;;;RFC 4023;DOI 10.17487/RFC4023;March;https://www.rfc-editor.org/info/rfc4023 | |
| RFC4024;;Parsons, G. and J. Maruszak;Voice Messaging Client Behaviour;;;;;RFC 4024;DOI 10.17487/RFC4024;July;https://www.rfc-editor.org/info/rfc4024 | |
| RFC4025;;Richardson, M.;A Method for Storing IPsec Keying Material in DNS;;;;;RFC 4025;DOI 10.17487/RFC4025;March;https://www.rfc-editor.org/info/rfc4025 | |
| RFC4026;;Andersson, L. and T. Madsen;Provider Provisioned Virtual Private Network (VPN) Terminology;;;;;RFC 4026;DOI 10.17487/RFC4026;March;https://www.rfc-editor.org/info/rfc4026 | |
| RFC4027;;Josefsson, S.;Domain Name System Media Types;;;;;RFC 4027;DOI 10.17487/RFC4027;April;https://www.rfc-editor.org/info/rfc4027 | |
| RFC4028;;Donovan, S. and J. Rosenberg;Session Timers in the Session Initiation Protocol (SIP);;;;;RFC 4028;DOI 10.17487/RFC4028;April;https://www.rfc-editor.org/info/rfc4028 | |
| RFC4029;;Lind, M., Ksinant, V., Park, S., Baudot, A., and P. Savola;Scenarios and Analysis for Introducing IPv6 into ISP Networks;;;;;RFC 4029;DOI 10.17487/RFC4029;March;https://www.rfc-editor.org/info/rfc4029 | |
| RFC4030;;Stapp, M. and T. Lemon;The Authentication Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option;;;;;RFC 4030;DOI 10.17487/RFC4030;March;https://www.rfc-editor.org/info/rfc4030 | |
| RFC4031;;Carugi, M., Ed., and D. McDysan, Ed.;Service Requirements for Layer 3 Provider Provisioned Virtual Private Networks (PPVPNs);;;;;RFC 4031;DOI 10.17487/RFC4031;April;https://www.rfc-editor.org/info/rfc4031 | |
| RFC4032;;Camarillo, G. and P. Kyzivat;Update to the Session Initiation Protocol (SIP) Preconditions Framework;;;;;RFC 4032;DOI 10.17487/RFC4032;March;https://www.rfc-editor.org/info/rfc4032 | |
| RFC4033;;Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose;DNS Security Introduction and Requirements;;;;;RFC 4033;DOI 10.17487/RFC4033;March;https://www.rfc-editor.org/info/rfc4033 | |
| RFC4034;;Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose;Resource Records for the DNS Security Extensions;;;;;RFC 4034;DOI 10.17487/RFC4034;March;https://www.rfc-editor.org/info/rfc4034 | |
| RFC4035;;Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose;Protocol Modifications for the DNS Security Extensions;;;;;RFC 4035;DOI 10.17487/RFC4035;March;https://www.rfc-editor.org/info/rfc4035 | |
| RFC4036;;Sawyer, W.;Management Information Base for Data Over Cable Service Interface Specification (DOCSIS) Cable Modem Termination Systems for Subscriber Management;;;;;RFC 4036;DOI 10.17487/RFC4036;April;https://www.rfc-editor.org/info/rfc4036 | |
| RFC4037;;Rousskov, A.;Open Pluggable Edge Services (OPES) Callout Protocol (OCP) Core;;;;;RFC 4037;DOI 10.17487/RFC4037;March;https://www.rfc-editor.org/info/rfc4037 | |
| RFC4038;;Shin, M-K., Ed., Hong, Y-G., Hagino, J., Savola, P., and E. Castro;Application Aspects of IPv6 Transition;;;;;RFC 4038;DOI 10.17487/RFC4038;March;https://www.rfc-editor.org/info/rfc4038 | |
| RFC4039;;Park, S., Kim, P., and B. Volz;Rapid Commit Option for the Dynamic Host Configuration Protocol version 4 (DHCPv4);;;;;RFC 4039;DOI 10.17487/RFC4039;March;https://www.rfc-editor.org/info/rfc4039 | |
| RFC4040;;Kreuter, R.;RTP Payload Format for a 64 kbit/s Transparent Call;;;;;RFC 4040;DOI 10.17487/RFC4040;April;https://www.rfc-editor.org/info/rfc4040 | |
| RFC4041;;Farrel, A.;Requirements for Morality Sections in Routing Area Drafts;;;;;RFC 4041;DOI 10.17487/RFC4041;April;https://www.rfc-editor.org/info/rfc4041 | |
| RFC4042;;Crispin, M.;UTF-9 and UTF-18 Efficient Transformation Formats of Unicode;;;;;RFC 4042;DOI 10.17487/RFC4042;April;https://www.rfc-editor.org/info/rfc4042 | |
| RFC4043;;Pinkas, D. and T. Gindin;Internet X.509 Public Key Infrastructure Permanent Identifier;;;;;RFC 4043;DOI 10.17487/RFC4043;May;https://www.rfc-editor.org/info/rfc4043 | |
| RFC4044;;McCloghrie, K.;Fibre Channel Management MIB;;;;;RFC 4044;DOI 10.17487/RFC4044;May;https://www.rfc-editor.org/info/rfc4044 | |
| RFC4045;;Bourdon, G.;Extensions to Support Efficient Carrying of Multicast Traffic in Layer-2 Tunneling Protocol (L2TP);;;;;RFC 4045;DOI 10.17487/RFC4045;April;https://www.rfc-editor.org/info/rfc4045 | |
| RFC4046;;Baugher, M., Canetti, R., Dondeti, L., and F. Lindholm;Multicast Security (MSEC) Group Key Management Architecture;;;;;RFC 4046;DOI 10.17487/RFC4046;April;https://www.rfc-editor.org/info/rfc4046 | |
| RFC4047;;Allen, S. and D. Wells;MIME Sub-type Registrations for Flexible Image Transport System (FITS);;;;;RFC 4047;DOI 10.17487/RFC4047;April;https://www.rfc-editor.org/info/rfc4047 | |
| RFC4048;;Carpenter, B.;RFC 1888 Is Obsolete;;;;;RFC 4048;DOI 10.17487/RFC4048;April;https://www.rfc-editor.org/info/rfc4048 | |
| RFC4049;RFC6019;Housley, R.;BinaryTime: An Alternate Format for Representing Date and Time in ASN.1;;;;;RFC 4049;DOI 10.17487/RFC4049;April;https://www.rfc-editor.org/info/rfc4049 | |
| RFC4050;;Blake-Wilson, S., Karlinger, G., Kobayashi, T., and Y. Wang;Using the Elliptic Curve Signature Algorithm (ECDSA) for XML Digital Signatures;;;;;RFC 4050;DOI 10.17487/RFC4050;April;https://www.rfc-editor.org/info/rfc4050 | |
| RFC4051;RFC6931;Eastlake 3rd, D.;Additional XML Security Uniform Resource Identifiers (URIs);;;;;RFC 4051;DOI 10.17487/RFC4051;April;https://www.rfc-editor.org/info/rfc4051 | |
| RFC4052;;Daigle, L., Ed., and Internet Architecture Board;IAB Processes for Management of IETF Liaison Relationships;;;BCP 102;;RFC 4052;DOI 10.17487/RFC4052;April;https://www.rfc-editor.org/info/rfc4052 | |
| RFC4053;;Trowbridge, S., Bradner, S., and F. Baker;Procedures for Handling Liaison Statements to and from the IETF;;;BCP 103;;RFC 4053;DOI 10.17487/RFC4053;April;https://www.rfc-editor.org/info/rfc4053 | |
| RFC4054;;Strand, J., Ed., and A. Chiu, Ed.;Impairments and Other Constraints on Optical Layer Routing;;;;;RFC 4054;DOI 10.17487/RFC4054;May;https://www.rfc-editor.org/info/rfc4054 | |
| RFC4055;;Schaad, J., Kaliski, B., and R. Housley;Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile;;;;;RFC 4055;DOI 10.17487/RFC4055;June;https://www.rfc-editor.org/info/rfc4055 | |
| RFC4056;;Schaad, J.;Use of the RSASSA-PSS Signature Algorithm in Cryptographic Message Syntax (CMS);;;;;RFC 4056;DOI 10.17487/RFC4056;June;https://www.rfc-editor.org/info/rfc4056 | |
| RFC4057;;Bound, J., Ed.;IPv6 Enterprise Network Scenarios;;;;;RFC 4057;DOI 10.17487/RFC4057;June;https://www.rfc-editor.org/info/rfc4057 | |
| RFC4058;;Yegin, A., Ed., Ohba, Y., Penno, R., Tsirtsis, G., and C. Wang;Protocol for Carrying Authentication for Network Access (PANA) Requirements;;;;;RFC 4058;DOI 10.17487/RFC4058;May;https://www.rfc-editor.org/info/rfc4058 | |
| RFC4059;;Linsenbardt, D., Pontius, S., and A. Sturgeon;Internet X.509 Public Key Infrastructure Warranty Certificate Extension;;;;;RFC 4059;DOI 10.17487/RFC4059;May;https://www.rfc-editor.org/info/rfc4059 | |
| RFC4060;;Xie, Q. and D. Pearce;RTP Payload Formats for European Telecommunications Standards Institute (ETSI) European Standard ES 202 050, ES 202 211, and ES 202 212 Distributed Speech Recognition Encoding;;;;;RFC 4060;DOI 10.17487/RFC4060;May;https://www.rfc-editor.org/info/rfc4060 | |
| RFC4061;;Manral, V., White, R., and A. Shaikh;Benchmarking Basic OSPF Single Router Control Plane Convergence;;;;;RFC 4061;DOI 10.17487/RFC4061;April;https://www.rfc-editor.org/info/rfc4061 | |
| RFC4062;;Manral, V., White, R., and A. Shaikh;OSPF Benchmarking Terminology and Concepts;;;;;RFC 4062;DOI 10.17487/RFC4062;April;https://www.rfc-editor.org/info/rfc4062 | |
| RFC4063;;Manral, V., White, R., and A. Shaikh;Considerations When Using Basic OSPF Convergence Benchmarks;;;;;RFC 4063;DOI 10.17487/RFC4063;April;https://www.rfc-editor.org/info/rfc4063 | |
| RFC4064;;Patel, A. and K. Leung;Experimental Message, Extensions, and Error Codes for Mobile IPv4;;;;;RFC 4064;DOI 10.17487/RFC4064;May;https://www.rfc-editor.org/info/rfc4064 | |
| RFC4065;;Kempf, J.;Instructions for Seamoby and Experimental Mobility Protocol IANA Allocations;;;;;RFC 4065;DOI 10.17487/RFC4065;July;https://www.rfc-editor.org/info/rfc4065 | |
| RFC4066;;Liebsch, M., Ed., Singh, A., Ed., Chaskar, H., Funato, D., and E. Shim;Candidate Access Router Discovery (CARD);;;;;RFC 4066;DOI 10.17487/RFC4066;July;https://www.rfc-editor.org/info/rfc4066 | |
| RFC4067;;Loughney, J., Ed., Nakhjiri, M., Perkins, C., and R. Koodli;Context Transfer Protocol (CXTP);;;;;RFC 4067;DOI 10.17487/RFC4067;July;https://www.rfc-editor.org/info/rfc4067 | |
| RFC4068;RFC5268;Koodli, R., Ed.;Fast Handovers for Mobile IPv6;;;;;RFC 4068;DOI 10.17487/RFC4068;July;https://www.rfc-editor.org/info/rfc4068 | |
| RFC4069;;Dodge, M. and B. Ray;Definitions of Managed Object Extensions for Very High Speed Digital Subscriber Lines (VDSL) Using Single Carrier Modulation (SCM) Line Coding;;;;;RFC 4069;DOI 10.17487/RFC4069;May;https://www.rfc-editor.org/info/rfc4069 | |
| RFC4070;;Dodge, M. and B. Ray;Definitions of Managed Object Extensions for Very High Speed Digital Subscriber Lines (VDSL) Using Multiple Carrier Modulation (MCM) Line Coding;;;;;RFC 4070;DOI 10.17487/RFC4070;May;https://www.rfc-editor.org/info/rfc4070 | |
| RFC4071;RFC8711;Austein, R., Ed., and B. Wijnen, Ed.;Structure of the IETF Administrative Support Activity (IASA);;;;;RFC 4071;DOI 10.17487/RFC4071;April;https://www.rfc-editor.org/info/rfc4071 | |
| RFC4072;;Eronen, P., Ed., Hiller, T., and G. Zorn;Diameter Extensible Authentication Protocol (EAP) Application;;;;;RFC 4072;DOI 10.17487/RFC4072;August;https://www.rfc-editor.org/info/rfc4072 | |
| RFC4073;;Housley, R.;Protecting Multiple Contents with the Cryptographic Message Syntax (CMS);;;;;RFC 4073;DOI 10.17487/RFC4073;May;https://www.rfc-editor.org/info/rfc4073 | |
| RFC4074;;Morishita, Y. and T. Jinmei;Common Misbehavior Against DNS Queries for IPv6 Addresses;;;;;RFC 4074;DOI 10.17487/RFC4074;May;https://www.rfc-editor.org/info/rfc4074 | |
| RFC4075;;Kalusivalingam, V.;Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6;;;;;RFC 4075;DOI 10.17487/RFC4075;May;https://www.rfc-editor.org/info/rfc4075 | |
| RFC4076;;Chown, T., Venaas, S., and A. Vijayabhaskar;Renumbering Requirements for Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6);;;;;RFC 4076;DOI 10.17487/RFC4076;May;https://www.rfc-editor.org/info/rfc4076 | |
| RFC4077;;Roach, A.;A Negative Acknowledgement Mechanism for Signaling Compression;;;;;RFC 4077;DOI 10.17487/RFC4077;May;https://www.rfc-editor.org/info/rfc4077 | |
| RFC4078;;Earnshaw, N., Aoki, S., Ashley, A., and W. Kameyama;The TV-Anytime Content Reference Identifier (CRID);;;;;RFC 4078;DOI 10.17487/RFC4078;May;https://www.rfc-editor.org/info/rfc4078 | |
| RFC4079;;Peterson, J.;A Presence Architecture for the Distribution of GEOPRIV Location Objects;;;;;RFC 4079;DOI 10.17487/RFC4079;July;https://www.rfc-editor.org/info/rfc4079 | |
| RFC4080;;Hancock, R., Karagiannis, G., Loughney, J., and S. Van den Bosch;Next Steps in Signaling (NSIS): Framework;;;;;RFC 4080;DOI 10.17487/RFC4080;June;https://www.rfc-editor.org/info/rfc4080 | |
| RFC4081;;Tschofenig, H. and D. Kroeselberg;Security Threats for Next Steps in Signaling (NSIS);;;;;RFC 4081;DOI 10.17487/RFC4081;June;https://www.rfc-editor.org/info/rfc4081 | |
| RFC4082;;Perrig, A., Song, D., Canetti, R., Tygar, J., and B. Briscoe;Timed Efficient Stream Loss-Tolerant Authentication (TESLA): Multicast Source Authentication Transform Introduction;;;;;RFC 4082;DOI 10.17487/RFC4082;June;https://www.rfc-editor.org/info/rfc4082 | |
| RFC4083;;Garcia-Martin, M.;Input 3rd-Generation Partnership Project (3GPP) Release 5 Requirements on the Session Initiation Protocol (SIP);;;;;RFC 4083;DOI 10.17487/RFC4083;May;https://www.rfc-editor.org/info/rfc4083 | |
| RFC4084;;Klensin, J.;Terminology for Describing Internet Connectivity;;;BCP 104;;RFC 4084;DOI 10.17487/RFC4084;May;https://www.rfc-editor.org/info/rfc4084 | |
| RFC4085;;Plonka, D.;Embedding Globally-Routable Internet Addresses Considered Harmful;;;BCP 105;;RFC 4085;DOI 10.17487/RFC4085;June;https://www.rfc-editor.org/info/rfc4085 | |
| RFC4086;;Eastlake 3rd, D., Schiller, J., and S. Crocker;Randomness Requirements for Security;;;BCP 106;;RFC 4086;DOI 10.17487/RFC4086;June;https://www.rfc-editor.org/info/rfc4086 | |
| RFC4087;;Thaler, D.;IP Tunnel MIB;;;;;RFC 4087;DOI 10.17487/RFC4087;June;https://www.rfc-editor.org/info/rfc4087 | |
| RFC4088;;Black, D., McCloghrie, K., and J. Schoenwaelder;Uniform Resource Identifier (URI) Scheme for the Simple Network Management Protocol (SNMP);;;;;RFC 4088;DOI 10.17487/RFC4088;June;https://www.rfc-editor.org/info/rfc4088 | |
| RFC4089;;Hollenbeck, S., Ed., and IAB and IESG;IAB and IESG Recommendation for IETF Administrative Restructuring;;;;;RFC 4089;DOI 10.17487/RFC4089;May;https://www.rfc-editor.org/info/rfc4089 | |
| RFC4090;;Pan, P., Ed., Swallow, G., Ed., and A. Atlas, Ed.;Fast Reroute Extensions to RSVP-TE for LSP Tunnels;;;;;RFC 4090;DOI 10.17487/RFC4090;May;https://www.rfc-editor.org/info/rfc4090 | |
| RFC4091;RFC5245;Camarillo, G. and J. Rosenberg;The Alternative Network Address Types (ANAT) Semantics for the Session Description Protocol (SDP) Grouping Framework;;;;;RFC 4091;DOI 10.17487/RFC4091;June;https://www.rfc-editor.org/info/rfc4091 | |
| RFC4092;RFC5245;Camarillo, G. and J. Rosenberg;Usage of the Session Description Protocol (SDP) Alternative Network Address Types (ANAT) Semantics in the Session Initiation Protocol (SIP);;;;;RFC 4092;DOI 10.17487/RFC4092;June;https://www.rfc-editor.org/info/rfc4092 | |
| RFC4093;;Adrangi, F., Ed., and H. Levkowetz, Ed.;Problem Statement: Mobile IPv4 Traversal of Virtual Private Network (VPN) Gateways;;;;;RFC 4093;DOI 10.17487/RFC4093;August;https://www.rfc-editor.org/info/rfc4093 | |
| RFC4094;;Manner, J. and X. Fu;Analysis of Existing Quality-of-Service Signaling Protocols;;;;;RFC 4094;DOI 10.17487/RFC4094;May;https://www.rfc-editor.org/info/rfc4094 | |
| RFC4095;;Malamud, C.;Attaching Meaning to Solicitation Class Keywords;;;;;RFC 4095;DOI 10.17487/RFC4095;May;https://www.rfc-editor.org/info/rfc4095 | |
| RFC4096;;Malamud, C.;Policy-Mandated Labels Such as "Adv:" in Email Subject Headers Considered Ineffective At Best;;;;;RFC 4096;DOI 10.17487/RFC4096;May;https://www.rfc-editor.org/info/rfc4096 | |
| RFC4097;;Barnes, M., Ed.;Middlebox Communications (MIDCOM) Protocol Evaluation;;;;;RFC 4097;DOI 10.17487/RFC4097;June;https://www.rfc-editor.org/info/rfc4097 | |
| RFC4098;;Berkowitz, H., Davies, E., Ed., Hares, S., Krishnaswamy, P., and M. Lepp;Terminology for Benchmarking BGP Device Convergence in the Control Plane;;;;;RFC 4098;DOI 10.17487/RFC4098;June;https://www.rfc-editor.org/info/rfc4098 | |
| RFC4101;;Rescorla, E. and IAB;Writing Protocol Models;;;;;RFC 4101;DOI 10.17487/RFC4101;June;https://www.rfc-editor.org/info/rfc4101 | |
| RFC4102;;Jones, P.;Registration of the text/red MIME Sub-Type;;;;;RFC 4102;DOI 10.17487/RFC4102;June;https://www.rfc-editor.org/info/rfc4102 | |
| RFC4103;;Hellstrom, G. and P. Jones;RTP Payload for Text Conversation;;;;;RFC 4103;DOI 10.17487/RFC4103;June;https://www.rfc-editor.org/info/rfc4103 | |
| RFC4104;;Pana, M., Ed., Reyes, A., Barba, A., Moron, D., and M. Brunner;Policy Core Extension Lightweight Directory Access Protocol Schema (PCELS);;;;;RFC 4104;DOI 10.17487/RFC4104;June;https://www.rfc-editor.org/info/rfc4104 | |
| RFC4105;;Le Roux, J.-L., Ed., Vasseur, J.-P., Ed., and J. Boyle, Ed.;Requirements for Inter-Area MPLS Traffic Engineering;;;;;RFC 4105;DOI 10.17487/RFC4105;June;https://www.rfc-editor.org/info/rfc4105 | |
| RFC4106;;Viega, J. and D. McGrew;The Use of Galois/Counter Mode (GCM) in IPsec Encapsulating Security Payload (ESP);;;;;RFC 4106;DOI 10.17487/RFC4106;June;https://www.rfc-editor.org/info/rfc4106 | |
| RFC4107;;Bellovin, S. and R. Housley;Guidelines for Cryptographic Key Management;;;BCP 107;;RFC 4107;DOI 10.17487/RFC4107;June;https://www.rfc-editor.org/info/rfc4107 | |
| RFC4108;;Housley, R.;Using Cryptographic Message Syntax (CMS) to Protect Firmware Packages;;;;;RFC 4108;DOI 10.17487/RFC4108;August;https://www.rfc-editor.org/info/rfc4108 | |
| RFC4109;;Hoffman, P.;Algorithms for Internet Key Exchange version 1 (IKEv1);;;;;RFC 4109;DOI 10.17487/RFC4109;May;https://www.rfc-editor.org/info/rfc4109 | |
| RFC4110;;Callon, R. and M. Suzuki;A Framework for Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs);;;;;RFC 4110;DOI 10.17487/RFC4110;July;https://www.rfc-editor.org/info/rfc4110 | |
| RFC4111;;Fang, L., Ed.;Security Framework for Provider-Provisioned Virtual Private Networks (PPVPNs);;;;;RFC 4111;DOI 10.17487/RFC4111;July;https://www.rfc-editor.org/info/rfc4111 | |
| RFC4112;;Eastlake 3rd, D.;Electronic Commerce Modeling Language (ECML) Version 2 Specification;;;;;RFC 4112;DOI 10.17487/RFC4112;June;https://www.rfc-editor.org/info/rfc4112 | |
| RFC4113;;Fenner, B. and J. Flick;Management Information Base for the User Datagram Protocol (UDP);;;;;RFC 4113;DOI 10.17487/RFC4113;June;https://www.rfc-editor.org/info/rfc4113 | |
| RFC4114;;Hollenbeck, S.;E.164 Number Mapping for the Extensible Provisioning Protocol (EPP);;;;;RFC 4114;DOI 10.17487/RFC4114;June;https://www.rfc-editor.org/info/rfc4114 | |
| RFC4115;;Aboul-Magd, O. and S. Rabie;A Differentiated Service Two-Rate, Three-Color Marker with Efficient Handling of in-Profile Traffic;;;;;RFC 4115;DOI 10.17487/RFC4115;July;https://www.rfc-editor.org/info/rfc4115 | |
| RFC4116;;Abley, J., Lindqvist, K., Davies, E., Black, B., and V. Gill;IPv4 Multihoming Practices and Limitations;;;;;RFC 4116;DOI 10.17487/RFC4116;July;https://www.rfc-editor.org/info/rfc4116 | |
| RFC4117;;Camarillo, G., Burger, E., Schulzrinne, H., and A. van Wijk;Transcoding Services Invocation in the Session Initiation Protocol (SIP) Using Third Party Call Control (3pcc);;;;;RFC 4117;DOI 10.17487/RFC4117;June;https://www.rfc-editor.org/info/rfc4117 | |
| RFC4118;;Yang, L., Zerfos, P., and E. Sadot;Architecture Taxonomy for Control and Provisioning of Wireless Access Points (CAPWAP);;;;;RFC 4118;DOI 10.17487/RFC4118;June;https://www.rfc-editor.org/info/rfc4118 | |
| RFC4119;;Peterson, J.;A Presence-based GEOPRIV Location Object Format;;;;;RFC 4119;DOI 10.17487/RFC4119;December;https://www.rfc-editor.org/info/rfc4119 | |
| RFC4120;;Neuman, C., Yu, T., Hartman, S., and K. Raeburn;The Kerberos Network Authentication Service (V5);;;;;RFC 4120;DOI 10.17487/RFC4120;July;https://www.rfc-editor.org/info/rfc4120 | |
| RFC4121;;Zhu, L., Jaganathan, K., and S. Hartman;The Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Mechanism: Version 2;;;;;RFC 4121;DOI 10.17487/RFC4121;July;https://www.rfc-editor.org/info/rfc4121 | |
| RFC4122;;Leach, P., Mealling, M., and R. Salz;A Universally Unique IDentifier (UUID) URN Namespace;;;;;RFC 4122;DOI 10.17487/RFC4122;July;https://www.rfc-editor.org/info/rfc4122 | |
| RFC4123;;Schulzrinne, H. and C. Agboh;Session Initiation Protocol (SIP)-H.323 Interworking Requirements;;;;;RFC 4123;DOI 10.17487/RFC4123;July;https://www.rfc-editor.org/info/rfc4123 | |
| RFC4124;;Le Faucheur, F., Ed.;Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering;;;;;RFC 4124;DOI 10.17487/RFC4124;June;https://www.rfc-editor.org/info/rfc4124 | |
| RFC4125;;Le Faucheur, F. and W. Lai;Maximum Allocation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering;;;;;RFC 4125;DOI 10.17487/RFC4125;June;https://www.rfc-editor.org/info/rfc4125 | |
| RFC4126;;Ash, J.;Max Allocation with Reservation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering & Performance Comparisons;;;;;RFC 4126;DOI 10.17487/RFC4126;June;https://www.rfc-editor.org/info/rfc4126 | |
| RFC4127;;Le Faucheur, F., Ed.;Russian Dolls Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering;;;;;RFC 4127;DOI 10.17487/RFC4127;June;https://www.rfc-editor.org/info/rfc4127 | |
| RFC4128;;Lai, W.;Bandwidth Constraints Models for Differentiated Services (Diffserv)-aware MPLS Traffic Engineering: Performance Evaluation;;;;;RFC 4128;DOI 10.17487/RFC4128;June;https://www.rfc-editor.org/info/rfc4128 | |
| RFC4129;;Mukundan, R., Morneault, K., and N. Mangalpally;Digital Private Network Signaling System (DPNSS)/Digital Access Signaling System 2 (DASS 2) Extensions to the IUA Protocol;;;;;RFC 4129;DOI 10.17487/RFC4129;September;https://www.rfc-editor.org/info/rfc4129 | |
| RFC4130;;Moberg, D. and R. Drummond;MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2 (AS2);;;;;RFC 4130;DOI 10.17487/RFC4130;July;https://www.rfc-editor.org/info/rfc4130 | |
| RFC4131;;Green, S., Ozawa, K., Cardona, E., Ed., and A. Katsnelson;Management Information Base for Data Over Cable Service Interface Specification (DOCSIS) Cable Modems and Cable Modem Termination Systems for Baseline Privacy Plus;;;;;RFC 4131;DOI 10.17487/RFC4131;September;https://www.rfc-editor.org/info/rfc4131 | |
| RFC4132;RFC5932;Moriai, S., Kato, A., and M. Kanda;Addition of Camellia Cipher Suites to Transport Layer Security (TLS);;;;;RFC 4132;DOI 10.17487/RFC4132;July;https://www.rfc-editor.org/info/rfc4132 | |
| RFC4133;RFC6933;Bierman, A. and K. McCloghrie;Entity MIB (Version 3);;;;;RFC 4133;DOI 10.17487/RFC4133;August;https://www.rfc-editor.org/info/rfc4133 | |
| RFC4134;;Hoffman, P., Ed.;Examples of S/MIME Messages;;;;;RFC 4134;DOI 10.17487/RFC4134;July;https://www.rfc-editor.org/info/rfc4134 | |
| RFC4135;;Choi, JH. and G. Daley;Goals of Detecting Network Attachment in IPv6;;;;;RFC 4135;DOI 10.17487/RFC4135;August;https://www.rfc-editor.org/info/rfc4135 | |
| RFC4136;;Pillay-Esnault, P.;OSPF Refresh and Flooding Reduction in Stable Topologies;;;;;RFC 4136;DOI 10.17487/RFC4136;July;https://www.rfc-editor.org/info/rfc4136 | |
| RFC4137;;Vollbrecht, J., Eronen, P., Petroni, N., and Y. Ohba;State Machines for Extensible Authentication Protocol (EAP) Peer and Authenticator;;;;;RFC 4137;DOI 10.17487/RFC4137;August;https://www.rfc-editor.org/info/rfc4137 | |
| RFC4138;;Sarolahti, P. and M. Kojo;Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP and the Stream Control Transmission Protocol (SCTP);;;;;RFC 4138;DOI 10.17487/RFC4138;August;https://www.rfc-editor.org/info/rfc4138 | |
| RFC4139;;Papadimitriou, D., Drake, J., Ash, J., Farrel, A., and L. Ong;Requirements for Generalized MPLS (GMPLS) Signaling Usage and Extensions for Automatically Switched Optical Network (ASON);;;;;RFC 4139;DOI 10.17487/RFC4139;July;https://www.rfc-editor.org/info/rfc4139 | |
| RFC4140;RFC5380;Soliman, H., Castelluccia, C., El Malki, K., and L. Bellier;Hierarchical Mobile IPv6 Mobility Management (HMIPv6);;;;;RFC 4140;DOI 10.17487/RFC4140;August;https://www.rfc-editor.org/info/rfc4140 | |
| RFC4141;;Toyoda, K. and D. Crocker;SMTP and MIME Extensions for Content Conversion;;;;;RFC 4141;DOI 10.17487/RFC4141;November;https://www.rfc-editor.org/info/rfc4141 | |
| RFC4142;;Crocker, D. and G. Klyne;Full-mode Fax Profile for Internet Mail (FFPIM);;;;;RFC 4142;DOI 10.17487/RFC4142;November;https://www.rfc-editor.org/info/rfc4142 | |
| RFC4143;;Toyoda, K. and D. Crocker;Facsimile Using Internet Mail (IFAX) Service of ENUM;;;;;RFC 4143;DOI 10.17487/RFC4143;November;https://www.rfc-editor.org/info/rfc4143 | |
| RFC4144;;Eastlake 3rd, D.;How to Gain Prominence and Influence in Standards Organizations;;;;;RFC 4144;DOI 10.17487/RFC4144;September;https://www.rfc-editor.org/info/rfc4144 | |
| RFC4145;;Yon, D. and G. Camarillo;TCP-Based Media Transport in the Session Description Protocol (SDP);;;;;RFC 4145;DOI 10.17487/RFC4145;September;https://www.rfc-editor.org/info/rfc4145 | |
| RFC4146;;Gellens, R.;Simple New Mail Notification;;;;;RFC 4146;DOI 10.17487/RFC4146;August;https://www.rfc-editor.org/info/rfc4146 | |
| RFC4147;;Huston, G.;Proposed Changes to the Format of the IANA IPv6 Registry;;;;;RFC 4147;DOI 10.17487/RFC4147;August;https://www.rfc-editor.org/info/rfc4147 | |
| RFC4148;RFC6248;Stephan, E.;IP Performance Metrics (IPPM) Metrics Registry;;;BCP 108;;RFC 4148;DOI 10.17487/RFC4148;August;https://www.rfc-editor.org/info/rfc4148 | |
| RFC4149;;Kalbfleisch, C., Cole, R., and D. Romascanu;Definition of Managed Objects for Synthetic Sources for Performance Monitoring Algorithms;;;;;RFC 4149;DOI 10.17487/RFC4149;August;https://www.rfc-editor.org/info/rfc4149 | |
| RFC4150;;Dietz, R. and R. Cole;Transport Performance Metrics MIB;;;;;RFC 4150;DOI 10.17487/RFC4150;August;https://www.rfc-editor.org/info/rfc4150 | |
| RFC4151;;Kindberg, T. and S. Hawke;The 'tag' URI Scheme;;;;;RFC 4151;DOI 10.17487/RFC4151;October;https://www.rfc-editor.org/info/rfc4151 | |
| RFC4152;;Tesink, K. and R. Fox;A Uniform Resource Name (URN) Namespace for the Common Language Equipment Identifier (CLEI) Code;;;;;RFC 4152;DOI 10.17487/RFC4152;August;https://www.rfc-editor.org/info/rfc4152 | |
| RFC4153;;Fujimura, K., Terada, M., and D. Eastlake 3rd;XML Voucher: Generic Voucher Language;;;;;RFC 4153;DOI 10.17487/RFC4153;September;https://www.rfc-editor.org/info/rfc4153 | |
| RFC4154;;Terada, M. and K. Fujimura;Voucher Trading System Application Programming Interface (VTS-API);;;;;RFC 4154;DOI 10.17487/RFC4154;September;https://www.rfc-editor.org/info/rfc4154 | |
| RFC4155;;Hall, E.;The application/mbox Media Type;;;;;RFC 4155;DOI 10.17487/RFC4155;September;https://www.rfc-editor.org/info/rfc4155 | |
| RFC4156;;Hoffman, P.;The wais URI Scheme;;;;;RFC 4156;DOI 10.17487/RFC4156;August;https://www.rfc-editor.org/info/rfc4156 | |
| RFC4157;;Hoffman, P.;The prospero URI Scheme;;;;;RFC 4157;DOI 10.17487/RFC4157;August;https://www.rfc-editor.org/info/rfc4157 | |
| RFC4158;;Cooper, M., Dzambasow, Y., Hesse, P., Joseph, S., and R. Nicholas;Internet X.509 Public Key Infrastructure: Certification Path Building;;;;;RFC 4158;DOI 10.17487/RFC4158;September;https://www.rfc-editor.org/info/rfc4158 | |
| RFC4159;;Huston, G.;Deprecation of "ip6.int";;;BCP 109;;RFC 4159;DOI 10.17487/RFC4159;August;https://www.rfc-editor.org/info/rfc4159 | |
| RFC4160;;Mimura, K., Yokoyama, K., Satoh, T., Kanaide, C., and C. Allocchio;Internet Fax Gateway Requirements;;;;;RFC 4160;DOI 10.17487/RFC4160;August;https://www.rfc-editor.org/info/rfc4160 | |
| RFC4161;;Mimura, K., Yokoyama, K., Satoh, T., Watanabe, K., and C. Kanaide;Guidelines for Optional Services for Internet Fax Gateways;;;;;RFC 4161;DOI 10.17487/RFC4161;August;https://www.rfc-editor.org/info/rfc4161 | |
| RFC4162;;Lee, H., Yoon, J., and J. Lee;Addition of SEED Cipher Suites to Transport Layer Security (TLS);;;;;RFC 4162;DOI 10.17487/RFC4162;August;https://www.rfc-editor.org/info/rfc4162 | |
| RFC4163;;Jonsson, L-E.;RObust Header Compression (ROHC): Requirements on TCP/IP Header Compression;;;;;RFC 4163;DOI 10.17487/RFC4163;August;https://www.rfc-editor.org/info/rfc4163 | |
| RFC4164;;Pelletier, G.;RObust Header Compression (ROHC): Context Replication for ROHC Profiles;;;;;RFC 4164;DOI 10.17487/RFC4164;August;https://www.rfc-editor.org/info/rfc4164 | |
| RFC4165;;George, T., Bidulock, B., Dantu, R., Schwarzbauer, H., and K. Morneault;Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Peer-to-Peer Adaptation Layer (M2PA);;;;;RFC 4165;DOI 10.17487/RFC4165;September;https://www.rfc-editor.org/info/rfc4165 | |
| RFC4166;;Coene, L. and J. Pastor-Balbas;Telephony Signalling Transport over Stream Control Transmission Protocol (SCTP) Applicability Statement;;;;;RFC 4166;DOI 10.17487/RFC4166;February;https://www.rfc-editor.org/info/rfc4166 | |
| RFC4167;;Lindem, A.;Graceful OSPF Restart Implementation Report;;;;;RFC 4167;DOI 10.17487/RFC4167;October;https://www.rfc-editor.org/info/rfc4167 | |
| RFC4168;;Rosenberg, J., Schulzrinne, H., and G. Camarillo;The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP);;;;;RFC 4168;DOI 10.17487/RFC4168;October;https://www.rfc-editor.org/info/rfc4168 | |
| RFC4169;;Torvinen, V., Arkko, J., and M. Naslund;Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA) Version-2;;;;;RFC 4169;DOI 10.17487/RFC4169;November;https://www.rfc-editor.org/info/rfc4169 | |
| RFC4170;;Thompson, B., Koren, T., and D. Wing;Tunneling Multiplexed Compressed RTP (TCRTP);;;BCP 110;;RFC 4170;DOI 10.17487/RFC4170;November;https://www.rfc-editor.org/info/rfc4170 | |
| RFC4171;;Tseng, J., Gibbons, K., Travostino, F., Du Laney, C., and J. Souza;Internet Storage Name Service (iSNS);;;;;RFC 4171;DOI 10.17487/RFC4171;September;https://www.rfc-editor.org/info/rfc4171 | |
| RFC4172;;Monia, C., Mullendore, R., Travostino, F., Jeong, W., and M. Edwards;iFCP - A Protocol for Internet Fibre Channel Storage Networking;;;;;RFC 4172;DOI 10.17487/RFC4172;September;https://www.rfc-editor.org/info/rfc4172 | |
| RFC4173;;Sarkar, P., Missimer, D., and C. Sapuntzakis;Bootstrapping Clients using the Internet Small Computer System Interface (iSCSI) Protocol;;;;;RFC 4173;DOI 10.17487/RFC4173;September;https://www.rfc-editor.org/info/rfc4173 | |
| RFC4174;;Monia, C., Tseng, J., and K. Gibbons;The IPv4 Dynamic Host Configuration Protocol (DHCP) Option for the Internet Storage Name Service;;;;;RFC 4174;DOI 10.17487/RFC4174;September;https://www.rfc-editor.org/info/rfc4174 | |
| RFC4175;;Gharai, L. and C. Perkins;RTP Payload Format for Uncompressed Video;;;;;RFC 4175;DOI 10.17487/RFC4175;September;https://www.rfc-editor.org/info/rfc4175 | |
| RFC4176;;El Mghazli, Y., Ed., Nadeau, T., Boucadair, M., Chan, K., and A. Gonguet;Framework for Layer 3 Virtual Private Networks (L3VPN) Operations and Management;;;;;RFC 4176;DOI 10.17487/RFC4176;October;https://www.rfc-editor.org/info/rfc4176 | |
| RFC4177;;Huston, G.;Architectural Approaches to Multi-homing for IPv6;;;;;RFC 4177;DOI 10.17487/RFC4177;September;https://www.rfc-editor.org/info/rfc4177 | |
| RFC4178;;Zhu, L., Leach, P., Jaganathan, K., and W. Ingersoll;The Simple and Protected Generic Security Service Application Program Interface (GSS-API) Negotiation Mechanism;;;;;RFC 4178;DOI 10.17487/RFC4178;October;https://www.rfc-editor.org/info/rfc4178 | |
| RFC4179;;Kang, S.;Using Universal Content Identifier (UCI) as Uniform Resource Names (URN);;;;;RFC 4179;DOI 10.17487/RFC4179;October;https://www.rfc-editor.org/info/rfc4179 | |
| RFC4180;;Shafranovich, Y.;Common Format and MIME Type for Comma-Separated Values (CSV) Files;;;;;RFC 4180;DOI 10.17487/RFC4180;October;https://www.rfc-editor.org/info/rfc4180 | |
| RFC4181;;Heard, C., Ed.;Guidelines for Authors and Reviewers of MIB Documents;;;BCP 111;;RFC 4181;DOI 10.17487/RFC4181;September;https://www.rfc-editor.org/info/rfc4181 | |
| RFC4182;;Rosen, E.;Removing a Restriction on the use of MPLS Explicit NULL;;;;;RFC 4182;DOI 10.17487/RFC4182;September;https://www.rfc-editor.org/info/rfc4182 | |
| RFC4183;;Warnicke, E.;A Suggested Scheme for DNS Resolution of Networks and Gateways;;;;;RFC 4183;DOI 10.17487/RFC4183;September;https://www.rfc-editor.org/info/rfc4183 | |
| RFC4184;;Link, B., Hager, T., and J. Flaks;RTP Payload Format for AC-3 Audio;;;;;RFC 4184;DOI 10.17487/RFC4184;October;https://www.rfc-editor.org/info/rfc4184 | |
| RFC4185;;Klensin, J.;National and Local Characters for DNS Top Level Domain (TLD) Names;;;;;RFC 4185;DOI 10.17487/RFC4185;October;https://www.rfc-editor.org/info/rfc4185 | |
| RFC4186;;Haverinen, H., Ed., and J. Salowey, Ed.;Extensible Authentication Protocol Method for Global System for Mobile Communications (GSM) Subscriber Identity Modules (EAP-SIM);;;;;RFC 4186;DOI 10.17487/RFC4186;January;https://www.rfc-editor.org/info/rfc4186 | |
| RFC4187;;Arkko, J. and H. Haverinen;Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA);;;;;RFC 4187;DOI 10.17487/RFC4187;January;https://www.rfc-editor.org/info/rfc4187 | |
| RFC4188;;Norseth, K., Ed., and E. Bell, Ed.;Definitions of Managed Objects for Bridges;;;;;RFC 4188;DOI 10.17487/RFC4188;September;https://www.rfc-editor.org/info/rfc4188 | |
| RFC4189;;Ono, K. and S. Tachimoto;Requirements for End-to-Middle Security for the Session Initiation Protocol (SIP);;;;;RFC 4189;DOI 10.17487/RFC4189;October;https://www.rfc-editor.org/info/rfc4189 | |
| RFC4190;;Carlberg, K., Brown, I., and C. Beard;Framework for Supporting Emergency Telecommunications Service (ETS) in IP Telephony;;;;;RFC 4190;DOI 10.17487/RFC4190;November;https://www.rfc-editor.org/info/rfc4190 | |
| RFC4191;;Draves, R. and D. Thaler;Default Router Preferences and More-Specific Routes;;;;;RFC 4191;DOI 10.17487/RFC4191;November;https://www.rfc-editor.org/info/rfc4191 | |
| RFC4192;;Baker, F., Lear, E., and R. Droms;Procedures for Renumbering an IPv6 Network without a Flag Day;;;;;RFC 4192;DOI 10.17487/RFC4192;September;https://www.rfc-editor.org/info/rfc4192 | |
| RFC4193;;Hinden, R. and B. Haberman;Unique Local IPv6 Unicast Addresses;;;;;RFC 4193;DOI 10.17487/RFC4193;October;https://www.rfc-editor.org/info/rfc4193 | |
| RFC4194;;Strombergson, J., Walleij, L., and P. Faltstrom;The S Hexdump Format;;;;;RFC 4194;DOI 10.17487/RFC4194;October;https://www.rfc-editor.org/info/rfc4194 | |
| RFC4195;;Kameyama, W.;A Uniform Resource Name (URN) Namespace for the TV-Anytime Forum;;;;;RFC 4195;DOI 10.17487/RFC4195;October;https://www.rfc-editor.org/info/rfc4195 | |
| RFC4196;;Lee, H., Yoon, J., Lee, S., and J. Lee;The SEED Cipher Algorithm and Its Use with IPsec;;;;;RFC 4196;DOI 10.17487/RFC4196;October;https://www.rfc-editor.org/info/rfc4196 | |
| RFC4197;;Riegel, M., Ed.;Requirements for Edge-to-Edge Emulation of Time Division Multiplexed (TDM) Circuits over Packet Switching Networks;;;;;RFC 4197;DOI 10.17487/RFC4197;October;https://www.rfc-editor.org/info/rfc4197 | |
| RFC4198;;Tessman, D.;A Uniform Resource Name (URN) Namespace for Federated Content;;;;;RFC 4198;DOI 10.17487/RFC4198;November;https://www.rfc-editor.org/info/rfc4198 | |
| RFC4201;;Kompella, K., Rekhter, Y., and L. Berger;Link Bundling in MPLS Traffic Engineering (TE);;;;;RFC 4201;DOI 10.17487/RFC4201;October;https://www.rfc-editor.org/info/rfc4201 | |
| RFC4202;;Kompella, K., Ed., and Y. Rekhter, Ed.;Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS);;;;;RFC 4202;DOI 10.17487/RFC4202;October;https://www.rfc-editor.org/info/rfc4202 | |
| RFC4203;;Kompella, K., Ed., and Y. Rekhter, Ed.;OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS);;;;;RFC 4203;DOI 10.17487/RFC4203;October;https://www.rfc-editor.org/info/rfc4203 | |
| RFC4204;;Lang, J., Ed.;Link Management Protocol (LMP);;;;;RFC 4204;DOI 10.17487/RFC4204;October;https://www.rfc-editor.org/info/rfc4204 | |
| RFC4205;RFC5307;Kompella, K., Ed., and Y. Rekhter, Ed.;Intermediate System to Intermediate System (IS-IS) Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS);;;;;RFC 4205;DOI 10.17487/RFC4205;October;https://www.rfc-editor.org/info/rfc4205 | |
| RFC4206;;Kompella, K. and Y. Rekhter;Label Switched Paths (LSP) Hierarchy with Generalized Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE);;;;;RFC 4206;DOI 10.17487/RFC4206;October;https://www.rfc-editor.org/info/rfc4206 | |
| RFC4207;;Lang, J. and D. Papadimitriou;Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy (SDH) Encoding for Link Management Protocol (LMP) Test Messages;;;;;RFC 4207;DOI 10.17487/RFC4207;October;https://www.rfc-editor.org/info/rfc4207 | |
| RFC4208;;Swallow, G., Drake, J., Ishimatsu, H., and Y. Rekhter;Generalized Multiprotocol Label Switching (GMPLS) User-Network Interface (UNI): Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Support for the Overlay Model;;;;;RFC 4208;DOI 10.17487/RFC4208;October;https://www.rfc-editor.org/info/rfc4208 | |
| RFC4209;;Fredette, A., Ed., and J. Lang, Ed.;Link Management Protocol (LMP) for Dense Wavelength Division Multiplexing (DWDM) Optical Line Systems;;;;;RFC 4209;DOI 10.17487/RFC4209;October;https://www.rfc-editor.org/info/rfc4209 | |
| RFC4210;;Adams, C., Farrell, S., Kause, T., and T. Mononen;Internet X.509 Public Key Infrastructure Certificate Management Protocol (CMP);;;;;RFC 4210;DOI 10.17487/RFC4210;September;https://www.rfc-editor.org/info/rfc4210 | |
| RFC4211;;Schaad, J.;Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF);;;;;RFC 4211;DOI 10.17487/RFC4211;September;https://www.rfc-editor.org/info/rfc4211 | |
| RFC4212;;Blinov, M. and C. Adams;Alternative Certificate Formats for the Public-Key Infrastructure Using X.509 (PKIX) Certificate Management Protocols;;;;;RFC 4212;DOI 10.17487/RFC4212;October;https://www.rfc-editor.org/info/rfc4212 | |
| RFC4213;;Nordmark, E. and R. Gilligan;Basic Transition Mechanisms for IPv6 Hosts and Routers;;;;;RFC 4213;DOI 10.17487/RFC4213;October;https://www.rfc-editor.org/info/rfc4213 | |
| RFC4214;RFC5214;Templin, F., Gleeson, T., Talwar, M., and D. Thaler;Intra-Site Automatic Tunnel Addressing Protocol (ISATAP);;;;;RFC 4214;DOI 10.17487/RFC4214;October;https://www.rfc-editor.org/info/rfc4214 | |
| RFC4215;;Wiljakka, J., Ed.;Analysis on IPv6 Transition in Third Generation Partnership Project (3GPP) Networks;;;;;RFC 4215;DOI 10.17487/RFC4215;October;https://www.rfc-editor.org/info/rfc4215 | |
| RFC4216;;Zhang, R., Ed., and J.-P. Vasseur, Ed.;MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements;;;;;RFC 4216;DOI 10.17487/RFC4216;November;https://www.rfc-editor.org/info/rfc4216 | |
| RFC4217;;Ford-Hutchinson, P.;Securing FTP with TLS;;;;;RFC 4217;DOI 10.17487/RFC4217;October;https://www.rfc-editor.org/info/rfc4217 | |
| RFC4218;;Nordmark, E. and T. Li;Threats Relating to IPv6 Multihoming Solutions;;;;;RFC 4218;DOI 10.17487/RFC4218;October;https://www.rfc-editor.org/info/rfc4218 | |
| RFC4219;;Lear, E.;Things Multihoming in IPv6 (MULTI6) Developers Should Think About;;;;;RFC 4219;DOI 10.17487/RFC4219;October;https://www.rfc-editor.org/info/rfc4219 | |
| RFC4220;;Dubuc, M., Nadeau, T., and J. Lang;Traffic Engineering Link Management Information Base;;;;;RFC 4220;DOI 10.17487/RFC4220;November;https://www.rfc-editor.org/info/rfc4220 | |
| RFC4221;;Nadeau, T., Srinivasan, C., and A. Farrel;Multiprotocol Label Switching (MPLS) Management Overview;;;;;RFC 4221;DOI 10.17487/RFC4221;November;https://www.rfc-editor.org/info/rfc4221 | |
| RFC4222;;Choudhury, G., Ed.;Prioritized Treatment of Specific OSPF Version 2 Packets and Congestion Avoidance;;;BCP 112;;RFC 4222;DOI 10.17487/RFC4222;October;https://www.rfc-editor.org/info/rfc4222 | |
| RFC4223;;Savola, P.;Reclassification of RFC 1863 to Historic;;;;;RFC 4223;DOI 10.17487/RFC4223;October;https://www.rfc-editor.org/info/rfc4223 | |
| RFC4224;;Pelletier, G., Jonsson, L-E., and K. Sandlund;RObust Header Compression (ROHC): ROHC over Channels That Can Reorder Packets;;;;;RFC 4224;DOI 10.17487/RFC4224;January;https://www.rfc-editor.org/info/rfc4224 | |
| RFC4225;;Nikander, P., Arkko, J., Aura, T., Montenegro, G., and E. Nordmark;Mobile IP Version 6 Route Optimization Security Design Background;;;;;RFC 4225;DOI 10.17487/RFC4225;December;https://www.rfc-editor.org/info/rfc4225 | |
| RFC4226;;M'Raihi, D., Bellare, M., Hoornaert, F., Naccache, D., and O. Ranen;HOTP: An HMAC-Based One-Time Password Algorithm;;;;;RFC 4226;DOI 10.17487/RFC4226;December;https://www.rfc-editor.org/info/rfc4226 | |
| RFC4227;;O'Tuathail, E. and M. Rose;Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP);;;;;RFC 4227;DOI 10.17487/RFC4227;January;https://www.rfc-editor.org/info/rfc4227 | |
| RFC4228;;Rousskov, A.;Requirements for an IETF Draft Submission Toolset;;;;;RFC 4228;DOI 10.17487/RFC4228;December;https://www.rfc-editor.org/info/rfc4228 | |
| RFC4229;;Nottingham, M. and J. Mogul;HTTP Header Field Registrations;;;;;RFC 4229;DOI 10.17487/RFC4229;December;https://www.rfc-editor.org/info/rfc4229 | |
| RFC4230;;Tschofenig, H. and R. Graveman;RSVP Security Properties;;;;;RFC 4230;DOI 10.17487/RFC4230;December;https://www.rfc-editor.org/info/rfc4230 | |
| RFC4231;;Nystrom, M.;Identifiers and Test Vectors for HMAC-SHA-224, HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512;;;;;RFC 4231;DOI 10.17487/RFC4231;December;https://www.rfc-editor.org/info/rfc4231 | |
| RFC4233;;Morneault, K., Rengasami, S., Kalla, M., and G. Sidebottom;Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer;;;;;RFC 4233;DOI 10.17487/RFC4233;January;https://www.rfc-editor.org/info/rfc4233 | |
| RFC4234;RFC5234;Crocker, D., Ed., and P. Overell;Augmented BNF for Syntax Specifications: ABNF;;;;;RFC 4234;DOI 10.17487/RFC4234;October;https://www.rfc-editor.org/info/rfc4234 | |
| RFC4235;;Rosenberg, J., Schulzrinne, H., and R. Mahy, Ed.;An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP);;;;;RFC 4235;DOI 10.17487/RFC4235;November;https://www.rfc-editor.org/info/rfc4235 | |
| RFC4236;;Rousskov, A. and M. Stecher;HTTP Adaptation with Open Pluggable Edge Services (OPES);;;;;RFC 4236;DOI 10.17487/RFC4236;November;https://www.rfc-editor.org/info/rfc4236 | |
| RFC4237;;Vaudreuil, G.;Voice Messaging Directory Service;;;;;RFC 4237;DOI 10.17487/RFC4237;October;https://www.rfc-editor.org/info/rfc4237 | |
| RFC4238;;Vaudreuil, G.;Voice Message Routing Service;;;;;RFC 4238;DOI 10.17487/RFC4238;October;https://www.rfc-editor.org/info/rfc4238 | |
| RFC4239;;McRae, S. and G. Parsons;Internet Voice Messaging (IVM);;;;;RFC 4239;DOI 10.17487/RFC4239;November;https://www.rfc-editor.org/info/rfc4239 | |
| RFC4240;;Burger, E., Ed., Van Dyke, J., and A. Spitzer;Basic Network Media Services with SIP;;;;;RFC 4240;DOI 10.17487/RFC4240;December;https://www.rfc-editor.org/info/rfc4240 | |
| RFC4241;;Shirasaki, Y., Miyakawa, S., Yamasaki, T., and A. Takenouchi;A Model of IPv6/IPv4 Dual Stack Internet Access Service;;;;;RFC 4241;DOI 10.17487/RFC4241;December;https://www.rfc-editor.org/info/rfc4241 | |
| RFC4242;RFC8415;Venaas, S., Chown, T., and B. Volz;Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6);;;;;RFC 4242;DOI 10.17487/RFC4242;November;https://www.rfc-editor.org/info/rfc4242 | |
| RFC4243;;Stapp, M., Johnson, R., and T. Palaniappan;Vendor-Specific Information Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option;;;;;RFC 4243;DOI 10.17487/RFC4243;December;https://www.rfc-editor.org/info/rfc4243 | |
| RFC4244;RFC7044;Barnes, M., Ed.;An Extension to the Session Initiation Protocol (SIP) for Request History Information;;;;;RFC 4244;DOI 10.17487/RFC4244;November;https://www.rfc-editor.org/info/rfc4244 | |
| RFC4245;;Levin, O. and R. Even;High-Level Requirements for Tightly Coupled SIP Conferencing;;;;;RFC 4245;DOI 10.17487/RFC4245;November;https://www.rfc-editor.org/info/rfc4245 | |
| RFC4246;;Dolan, M.;International Standard Audiovisual Number (ISAN) URN Definition;;;;;RFC 4246;DOI 10.17487/RFC4246;February;https://www.rfc-editor.org/info/rfc4246 | |
| RFC4247;;Ash, J., Goode, B., Hand, J., and R. Zhang;Requirements for Header Compression over MPLS;;;;;RFC 4247;DOI 10.17487/RFC4247;November;https://www.rfc-editor.org/info/rfc4247 | |
| RFC4248;;Hoffman, P.;The telnet URI Scheme;;;;;RFC 4248;DOI 10.17487/RFC4248;October;https://www.rfc-editor.org/info/rfc4248 | |
| RFC4249;;Lilly, B.;Implementer-Friendly Specification of Message and MIME-Part Header Fields and Field Components;;;;;RFC 4249;DOI 10.17487/RFC4249;January;https://www.rfc-editor.org/info/rfc4249 | |
| RFC4250;;Lehtinen, S. and C. Lonvick, Ed.;The Secure Shell (SSH) Protocol Assigned Numbers;;;;;RFC 4250;DOI 10.17487/RFC4250;January;https://www.rfc-editor.org/info/rfc4250 | |
| RFC4251;;Ylonen, T. and C. Lonvick, Ed.;The Secure Shell (SSH) Protocol Architecture;;;;;RFC 4251;DOI 10.17487/RFC4251;January;https://www.rfc-editor.org/info/rfc4251 | |
| RFC4252;;Ylonen, T. and C. Lonvick, Ed.;The Secure Shell (SSH) Authentication Protocol;;;;;RFC 4252;DOI 10.17487/RFC4252;January;https://www.rfc-editor.org/info/rfc4252 | |
| RFC4253;;Ylonen, T. and C. Lonvick, Ed.;The Secure Shell (SSH) Transport Layer Protocol;;;;;RFC 4253;DOI 10.17487/RFC4253;January;https://www.rfc-editor.org/info/rfc4253 | |
| RFC4254;;Ylonen, T. and C. Lonvick, Ed.;The Secure Shell (SSH) Connection Protocol;;;;;RFC 4254;DOI 10.17487/RFC4254;January;https://www.rfc-editor.org/info/rfc4254 | |
| RFC4255;;Schlyter, J. and W. Griffin;Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints;;;;;RFC 4255;DOI 10.17487/RFC4255;January;https://www.rfc-editor.org/info/rfc4255 | |
| RFC4256;;Cusack, F. and M. Forssen;Generic Message Exchange Authentication for the Secure Shell Protocol (SSH);;;;;RFC 4256;DOI 10.17487/RFC4256;January;https://www.rfc-editor.org/info/rfc4256 | |
| RFC4257;;Bernstein, G., Mannie, E., Sharma, V., and E. Gray;Framework for Generalized Multi-Protocol Label Switching (GMPLS)-based Control of Synchronous Digital Hierarchy/Synchronous Optical Networking (SDH/SONET) Networks;;;;;RFC 4257;DOI 10.17487/RFC4257;December;https://www.rfc-editor.org/info/rfc4257 | |
| RFC4258;;Brungard, D., Ed.;Requirements for Generalized Multi-Protocol Label Switching (GMPLS) Routing for the Automatically Switched Optical Network (ASON);;;;;RFC 4258;DOI 10.17487/RFC4258;November;https://www.rfc-editor.org/info/rfc4258 | |
| RFC4259;;Montpetit, M.-J., Fairhurst, G., Clausen, H., Collini-Nocker, B., and H. Linder;A Framework for Transmission of IP Datagrams over MPEG-2 Networks;;;;;RFC 4259;DOI 10.17487/RFC4259;November;https://www.rfc-editor.org/info/rfc4259 | |
| RFC4260;;McCann, P.;Mobile IPv6 Fast Handovers for 802.11 Networks;;;;;RFC 4260;DOI 10.17487/RFC4260;November;https://www.rfc-editor.org/info/rfc4260 | |
| RFC4261;;Walker, J. and A. Kulkarni, Ed.;Common Open Policy Service (COPS) Over Transport Layer Security (TLS);;;;;RFC 4261;DOI 10.17487/RFC4261;December;https://www.rfc-editor.org/info/rfc4261 | |
| RFC4262;;Santesson, S.;X.509 Certificate Extension for Secure/Multipurpose Internet Mail Extensions (S/MIME) Capabilities;;;;;RFC 4262;DOI 10.17487/RFC4262;December;https://www.rfc-editor.org/info/rfc4262 | |
| RFC4263;;Lilly, B.;Media Subtype Registration for Media Type text/troff;;;;;RFC 4263;DOI 10.17487/RFC4263;January;https://www.rfc-editor.org/info/rfc4263 | |
| RFC4264;;Griffin, T. and G. Huston;BGP Wedgies;;;;;RFC 4264;DOI 10.17487/RFC4264;November;https://www.rfc-editor.org/info/rfc4264 | |
| RFC4265;;Schliesser, B. and T. Nadeau;Definition of Textual Conventions for Virtual Private Network (VPN) Management;;;;;RFC 4265;DOI 10.17487/RFC4265;November;https://www.rfc-editor.org/info/rfc4265 | |
| RFC4266;;Hoffman, P.;The gopher URI Scheme;;;;;RFC 4266;DOI 10.17487/RFC4266;November;https://www.rfc-editor.org/info/rfc4266 | |
| RFC4267;;Froumentin, M.;The W3C Speech Interface Framework Media Types: application/voicexml+xml, application/ssml+xml, application/srgs, application/srgs+xml, application/ccxml+xml, and application/pls+xml;;;;;RFC 4267;DOI 10.17487/RFC4267;November;https://www.rfc-editor.org/info/rfc4267 | |
| RFC4268;;Chisholm, S. and D. Perkins;Entity State MIB;;;;;RFC 4268;DOI 10.17487/RFC4268;November;https://www.rfc-editor.org/info/rfc4268 | |
| RFC4269;;Lee, H., Lee, S., Yoon, J., Cheon, D., and J. Lee;The SEED Encryption Algorithm;;;;;RFC 4269;DOI 10.17487/RFC4269;December;https://www.rfc-editor.org/info/rfc4269 | |
| RFC4270;;Hoffman, P. and B. Schneier;Attacks on Cryptographic Hashes in Internet Protocols;;;;;RFC 4270;DOI 10.17487/RFC4270;November;https://www.rfc-editor.org/info/rfc4270 | |
| RFC4271;;Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed.;A Border Gateway Protocol 4 (BGP-4);;;;;RFC 4271;DOI 10.17487/RFC4271;January;https://www.rfc-editor.org/info/rfc4271 | |
| RFC4272;;Murphy, S.;BGP Security Vulnerabilities Analysis;;;;;RFC 4272;DOI 10.17487/RFC4272;January;https://www.rfc-editor.org/info/rfc4272 | |
| RFC4273;;Haas, J., Ed., and S. Hares, Ed.;Definitions of Managed Objects for BGP-4;;;;;RFC 4273;DOI 10.17487/RFC4273;January;https://www.rfc-editor.org/info/rfc4273 | |
| RFC4274;;Meyer, D. and K. Patel;BGP-4 Protocol Analysis;;;;;RFC 4274;DOI 10.17487/RFC4274;January;https://www.rfc-editor.org/info/rfc4274 | |
| RFC4275;;Hares, S. and D. Hares;BGP-4 MIB Implementation Survey;;;;;RFC 4275;DOI 10.17487/RFC4275;January;https://www.rfc-editor.org/info/rfc4275 | |
| RFC4276;;Hares, S. and A. Retana;BGP-4 Implementation Report;;;;;RFC 4276;DOI 10.17487/RFC4276;January;https://www.rfc-editor.org/info/rfc4276 | |
| RFC4277;;McPherson, D. and K. Patel;Experience with the BGP-4 Protocol;;;;;RFC 4277;DOI 10.17487/RFC4277;January;https://www.rfc-editor.org/info/rfc4277 | |
| RFC4278;;Bellovin, S. and A. Zinin;Standards Maturity Variance Regarding the TCP MD5 Signature Option (RFC 2385) and the BGP-4 Specification;;;;;RFC 4278;DOI 10.17487/RFC4278;January;https://www.rfc-editor.org/info/rfc4278 | |
| RFC4279;;Eronen, P., Ed., and H. Tschofenig, Ed.;Pre-Shared Key Ciphersuites for Transport Layer Security (TLS);;;;;RFC 4279;DOI 10.17487/RFC4279;December;https://www.rfc-editor.org/info/rfc4279 | |
| RFC4280;;Chowdhury, K., Yegani, P., and L. Madour;Dynamic Host Configuration Protocol (DHCP) Options for Broadcast and Multicast Control Servers;;;;;RFC 4280;DOI 10.17487/RFC4280;November;https://www.rfc-editor.org/info/rfc4280 | |
| RFC4281;RFC6381;Gellens, R., Singer, D., and P. Frojdh;The Codecs Parameter for "Bucket" Media Types;;;;;RFC 4281;DOI 10.17487/RFC4281;November;https://www.rfc-editor.org/info/rfc4281 | |
| RFC4282;RFC7542;Aboba, B., Beadles, M., Arkko, J., and P. Eronen;The Network Access Identifier;;;;;RFC 4282;DOI 10.17487/RFC4282;December;https://www.rfc-editor.org/info/rfc4282 | |
| RFC4283;;Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury;Mobile Node Identifier Option for Mobile IPv6 (MIPv6);;;;;RFC 4283;DOI 10.17487/RFC4283;November;https://www.rfc-editor.org/info/rfc4283 | |
| RFC4284;;Adrangi, F., Lortz, V., Bari, F., and P. Eronen;Identity Selection Hints for the Extensible Authentication Protocol (EAP);;;;;RFC 4284;DOI 10.17487/RFC4284;January;https://www.rfc-editor.org/info/rfc4284 | |
| RFC4285;;Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury;Authentication Protocol for Mobile IPv6;;;;;RFC 4285;DOI 10.17487/RFC4285;January;https://www.rfc-editor.org/info/rfc4285 | |
| RFC4286;;Haberman, B. and J. Martin;Multicast Router Discovery;;;;;RFC 4286;DOI 10.17487/RFC4286;December;https://www.rfc-editor.org/info/rfc4286 | |
| RFC4287;;Nottingham, M., Ed., and R. Sayre, Ed.;The Atom Syndication Format;;;;;RFC 4287;DOI 10.17487/RFC4287;December;https://www.rfc-editor.org/info/rfc4287 | |
| RFC4288;RFC6838;Freed, N. and J. Klensin;Media Type Specifications and Registration Procedures;;;;;RFC 4288;DOI 10.17487/RFC4288;December;https://www.rfc-editor.org/info/rfc4288 | |
| RFC4289;;Freed, N. and J. Klensin;Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures;;;BCP 13;;RFC 4289;DOI 10.17487/RFC4289;December;https://www.rfc-editor.org/info/rfc4289 | |
| RFC4290;;Klensin, J.;Suggested Practices for Registration of Internationalized Domain Names (IDN);;;;;RFC 4290;DOI 10.17487/RFC4290;December;https://www.rfc-editor.org/info/rfc4290 | |
| RFC4291;;Hinden, R. and S. Deering;IP Version 6 Addressing Architecture;;;;;RFC 4291;DOI 10.17487/RFC4291;February;https://www.rfc-editor.org/info/rfc4291 | |
| RFC4292;;Haberman, B.;IP Forwarding Table MIB;;;;;RFC 4292;DOI 10.17487/RFC4292;April;https://www.rfc-editor.org/info/rfc4292 | |
| RFC4293;;Routhier, S., Ed.;Management Information Base for the Internet Protocol (IP);;;;;RFC 4293;DOI 10.17487/RFC4293;April;https://www.rfc-editor.org/info/rfc4293 | |
| RFC4294;RFC6434;Loughney, J., Ed.;IPv6 Node Requirements;;;;;RFC 4294;DOI 10.17487/RFC4294;April;https://www.rfc-editor.org/info/rfc4294 | |
| RFC4295;;Keeni, G., Koide, K., Nagami, K., and S. Gundavelli;Mobile IPv6 Management Information Base;;;;;RFC 4295;DOI 10.17487/RFC4295;April;https://www.rfc-editor.org/info/rfc4295 | |
| RFC4296;;Bailey, S. and T. Talpey;The Architecture of Direct Data Placement (DDP) and Remote Direct Memory Access (RDMA) on Internet Protocols;;;;;RFC 4296;DOI 10.17487/RFC4296;December;https://www.rfc-editor.org/info/rfc4296 | |
| RFC4297;;Romanow, A., Mogul, J., Talpey, T., and S. Bailey;Remote Direct Memory Access (RDMA) over IP Problem Statement;;;;;RFC 4297;DOI 10.17487/RFC4297;December;https://www.rfc-editor.org/info/rfc4297 | |
| RFC4298;;Chen, J.-H., Lee, W., and J. Thyssen;RTP Payload Format for BroadVoice Speech Codecs;;;;;RFC 4298;DOI 10.17487/RFC4298;December;https://www.rfc-editor.org/info/rfc4298 | |
| RFC4301;;Kent, S. and K. Seo;Security Architecture for the Internet Protocol;;;;;RFC 4301;DOI 10.17487/RFC4301;December;https://www.rfc-editor.org/info/rfc4301 | |
| RFC4302;;Kent, S.;IP Authentication Header;;;;;RFC 4302;DOI 10.17487/RFC4302;December;https://www.rfc-editor.org/info/rfc4302 | |
| RFC4303;;Kent, S.;IP Encapsulating Security Payload (ESP);;;;;RFC 4303;DOI 10.17487/RFC4303;December;https://www.rfc-editor.org/info/rfc4303 | |
| RFC4304;;Kent, S.;Extended Sequence Number (ESN) Addendum to IPsec Domain of Interpretation (DOI) for Internet Security Association and Key Management Protocol (ISAKMP);;;;;RFC 4304;DOI 10.17487/RFC4304;December;https://www.rfc-editor.org/info/rfc4304 | |
| RFC4305;RFC4835;Eastlake 3rd, D.;Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH);;;;;RFC 4305;DOI 10.17487/RFC4305;December;https://www.rfc-editor.org/info/rfc4305 | |
| RFC4306;RFC5996;Kaufman, C., Ed.;Internet Key Exchange (IKEv2) Protocol;;;;;RFC 4306;DOI 10.17487/RFC4306;December;https://www.rfc-editor.org/info/rfc4306 | |
| RFC4307;RFC8247;Schiller, J.;Cryptographic Algorithms for Use in the Internet Key Exchange Version 2 (IKEv2);;;;;RFC 4307;DOI 10.17487/RFC4307;December;https://www.rfc-editor.org/info/rfc4307 | |
| RFC4308;;Hoffman, P.;Cryptographic Suites for IPsec;;;;;RFC 4308;DOI 10.17487/RFC4308;December;https://www.rfc-editor.org/info/rfc4308 | |
| RFC4309;;Housley, R.;Using Advanced Encryption Standard (AES) CCM Mode with IPsec Encapsulating Security Payload (ESP);;;;;RFC 4309;DOI 10.17487/RFC4309;December;https://www.rfc-editor.org/info/rfc4309 | |
| RFC4310;RFC5910;Hollenbeck, S.;Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP);;;;;RFC 4310;DOI 10.17487/RFC4310;December;https://www.rfc-editor.org/info/rfc4310 | |
| RFC4311;;Hinden, R. and D. Thaler;IPv6 Host-to-Router Load Sharing;;;;;RFC 4311;DOI 10.17487/RFC4311;November;https://www.rfc-editor.org/info/rfc4311 | |
| RFC4312;;Kato, A., Moriai, S., and M. Kanda;The Camellia Cipher Algorithm and Its Use With IPsec;;;;;RFC 4312;DOI 10.17487/RFC4312;December;https://www.rfc-editor.org/info/rfc4312 | |
| RFC4313;;Oran, D.;Requirements for Distributed Control of Automatic Speech Recognition (ASR), Speaker Identification/Speaker Verification (SI/SV), and Text-to-Speech (TTS) Resources;;;;;RFC 4313;DOI 10.17487/RFC4313;December;https://www.rfc-editor.org/info/rfc4313 | |
| RFC4314;;Melnikov, A.;IMAP4 Access Control List (ACL) Extension;;;;;RFC 4314;DOI 10.17487/RFC4314;December;https://www.rfc-editor.org/info/rfc4314 | |
| RFC4315;;Crispin, M.;Internet Message Access Protocol (IMAP) - UIDPLUS extension;;;;;RFC 4315;DOI 10.17487/RFC4315;December;https://www.rfc-editor.org/info/rfc4315 | |
| RFC4316;;Reschke, J.;Datatypes for Web Distributed Authoring and Versioning (WebDAV) Properties;;;;;RFC 4316;DOI 10.17487/RFC4316;December;https://www.rfc-editor.org/info/rfc4316 | |
| RFC4317;;Johnston, A. and R. Sparks;Session Description Protocol (SDP) Offer/Answer Examples;;;;;RFC 4317;DOI 10.17487/RFC4317;December;https://www.rfc-editor.org/info/rfc4317 | |
| RFC4318;;Levi, D. and D. Harrington;Definitions of Managed Objects for Bridges with Rapid Spanning Tree Protocol;;;;;RFC 4318;DOI 10.17487/RFC4318;December;https://www.rfc-editor.org/info/rfc4318 | |
| RFC4319;;Sikes, C., Ray, B., and R. Abbi;Definitions of Managed Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair High-Speed Digital Subscriber Line (SHDSL) Lines;;;;;RFC 4319;DOI 10.17487/RFC4319;December;https://www.rfc-editor.org/info/rfc4319 | |
| RFC4320;;Sparks, R.;Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction;;;;;RFC 4320;DOI 10.17487/RFC4320;January;https://www.rfc-editor.org/info/rfc4320 | |
| RFC4321;;Sparks, R.;Problems Identified Associated with the Session Initiation Protocol's (SIP) Non-INVITE Transaction;;;;;RFC 4321;DOI 10.17487/RFC4321;January;https://www.rfc-editor.org/info/rfc4321 | |
| RFC4322;;Richardson, M. and D. Redelmeier;Opportunistic Encryption using the Internet Key Exchange (IKE);;;;;RFC 4322;DOI 10.17487/RFC4322;December;https://www.rfc-editor.org/info/rfc4322 | |
| RFC4323;;Patrick, M. and W. Murwin;Data Over Cable System Interface Specification Quality of Service Management Information Base (DOCSIS-QoS MIB);;;;;RFC 4323;DOI 10.17487/RFC4323;January;https://www.rfc-editor.org/info/rfc4323 | |
| RFC4324;;Royer, D., Babics, G., and S. Mansour;Calendar Access Protocol (CAP);;;;;RFC 4324;DOI 10.17487/RFC4324;December;https://www.rfc-editor.org/info/rfc4324 | |
| RFC4325;RFC5280;Santesson, S. and R. Housley;Internet X.509 Public Key Infrastructure Authority Information Access Certificate Revocation List (CRL) Extension;;;;;RFC 4325;DOI 10.17487/RFC4325;December;https://www.rfc-editor.org/info/rfc4325 | |
| RFC4326;;Fairhurst, G. and B. Collini-Nocker;Unidirectional Lightweight Encapsulation (ULE) for Transmission of IP Datagrams over an MPEG-2 Transport Stream (TS);;;;;RFC 4326;DOI 10.17487/RFC4326;December;https://www.rfc-editor.org/info/rfc4326 | |
| RFC4327;RFC4631;Dubuc, M., Nadeau, T., Lang, J., and E. McGinnis;Link Management Protocol (LMP) Management Information Base (MIB);;;;;RFC 4327;DOI 10.17487/RFC4327;January;https://www.rfc-editor.org/info/rfc4327 | |
| RFC4328;;Papadimitriou, D., Ed.;Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control;;;;;RFC 4328;DOI 10.17487/RFC4328;January;https://www.rfc-editor.org/info/rfc4328 | |
| RFC4329;;Hoehrmann, B.;Scripting Media Types;;;;;RFC 4329;DOI 10.17487/RFC4329;April;https://www.rfc-editor.org/info/rfc4329 | |
| RFC4330;RFC5905;Mills, D.;Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI;;;;;RFC 4330;DOI 10.17487/RFC4330;January;https://www.rfc-editor.org/info/rfc4330 | |
| RFC4331;;Korver, B. and L. Dusseault;Quota and Size Properties for Distributed Authoring and Versioning (DAV) Collections;;;;;RFC 4331;DOI 10.17487/RFC4331;February;https://www.rfc-editor.org/info/rfc4331 | |
| RFC4332;;Leung, K., Patel, A., Tsirtsis, G., and E. Klovning;Cisco's Mobile IPv4 Host Configuration Extensions;;;;;RFC 4332;DOI 10.17487/RFC4332;December;https://www.rfc-editor.org/info/rfc4332 | |
| RFC4333;RFC8711;Huston, G., Ed., and B. Wijnen, Ed.;The IETF Administrative Oversight Committee (IAOC) Member Selection Guidelines and Process;;;;;RFC 4333;DOI 10.17487/RFC4333;December;https://www.rfc-editor.org/info/rfc4333 | |
| RFC4334;;Housley, R. and T. Moore;Certificate Extensions and Attributes Supporting Authentication in Point-to-Point Protocol (PPP) and Wireless Local Area Networks (WLAN);;;;;RFC 4334;DOI 10.17487/RFC4334;February;https://www.rfc-editor.org/info/rfc4334 | |
| RFC4335;;Galbraith, J. and P. Remaker;The Secure Shell (SSH) Session Channel Break Extension;;;;;RFC 4335;DOI 10.17487/RFC4335;January;https://www.rfc-editor.org/info/rfc4335 | |
| RFC4336;;Floyd, S., Handley, M., and E. Kohler;Problem Statement for the Datagram Congestion Control Protocol (DCCP);;;;;RFC 4336;DOI 10.17487/RFC4336;March;https://www.rfc-editor.org/info/rfc4336 | |
| RFC4337;;Y Lim and D. Singer;MIME Type Registration for MPEG-4;;;;;RFC 4337;DOI 10.17487/RFC4337;March;https://www.rfc-editor.org/info/rfc4337 | |
| RFC4338;;DeSanti, C., Carlson, C., and R. Nixon;Transmission of IPv6, IPv4, and Address Resolution Protocol (ARP) Packets over Fibre Channel;;;;;RFC 4338;DOI 10.17487/RFC4338;January;https://www.rfc-editor.org/info/rfc4338 | |
| RFC4339;;Jeong, J., Ed.;IPv6 Host Configuration of DNS Server Information Approaches;;;;;RFC 4339;DOI 10.17487/RFC4339;February;https://www.rfc-editor.org/info/rfc4339 | |
| RFC4340;;Kohler, E., Handley, M., and S. Floyd;Datagram Congestion Control Protocol (DCCP);;;;;RFC 4340;DOI 10.17487/RFC4340;March;https://www.rfc-editor.org/info/rfc4340 | |
| RFC4341;;Floyd, S. and E. Kohler;Profile for Datagram Congestion Control Protocol (DCCP) Congestion Control ID 2: TCP-like Congestion Control;;;;;RFC 4341;DOI 10.17487/RFC4341;March;https://www.rfc-editor.org/info/rfc4341 | |
| RFC4342;;Floyd, S., Kohler, E., and J. Padhye;Profile for Datagram Congestion Control Protocol (DCCP) Congestion Control ID 3: TCP-Friendly Rate Control (TFRC);;;;;RFC 4342;DOI 10.17487/RFC4342;March;https://www.rfc-editor.org/info/rfc4342 | |
| RFC4343;;Eastlake 3rd, D.;Domain Name System (DNS) Case Insensitivity Clarification;;;;;RFC 4343;DOI 10.17487/RFC4343;January;https://www.rfc-editor.org/info/rfc4343 | |
| RFC4344;;Bellare, M., Kohno, T., and C. Namprempre;The Secure Shell (SSH) Transport Layer Encryption Modes;;;;;RFC 4344;DOI 10.17487/RFC4344;January;https://www.rfc-editor.org/info/rfc4344 | |
| RFC4345;;Harris, B.;Improved Arcfour Modes for the Secure Shell (SSH) Transport Layer Protocol;;;;;RFC 4345;DOI 10.17487/RFC4345;January;https://www.rfc-editor.org/info/rfc4345 | |
| RFC4346;RFC5246;Dierks, T. and E. Rescorla;The Transport Layer Security (TLS) Protocol Version 1.1;;;;;RFC 4346;DOI 10.17487/RFC4346;April;https://www.rfc-editor.org/info/rfc4346 | |
| RFC4347;RFC6347;Rescorla, E. and N. Modadugu;Datagram Transport Layer Security;;;;;RFC 4347;DOI 10.17487/RFC4347;April;https://www.rfc-editor.org/info/rfc4347 | |
| RFC4348;;Ahmadi, S.;Real-Time Transport Protocol (RTP) Payload Format for the Variable-Rate Multimode Wideband (VMR-WB) Audio Codec;;;;;RFC 4348;DOI 10.17487/RFC4348;January;https://www.rfc-editor.org/info/rfc4348 | |
| RFC4349;;Pignataro, C. and M. Townsley;High-Level Data Link Control (HDLC) Frames over Layer 2 Tunneling Protocol, Version 3 (L2TPv3);;;;;RFC 4349;DOI 10.17487/RFC4349;February;https://www.rfc-editor.org/info/rfc4349 | |
| RFC4350;;Hendrikx, F. and C. Wallis;A Uniform Resource Name (URN) Formal Namespace for the New Zealand Government;;;;;RFC 4350;DOI 10.17487/RFC4350;February;https://www.rfc-editor.org/info/rfc4350 | |
| RFC4351;;Hellstrom, G. and P. Jones;Real-Time Transport Protocol (RTP) Payload for Text Conversation Interleaved in an Audio Stream;;;;;RFC 4351;DOI 10.17487/RFC4351;January;https://www.rfc-editor.org/info/rfc4351 | |
| RFC4352;;Sjoberg, J., Westerlund, M., Lakaniemi, A., and S. Wenger;RTP Payload Format for the Extended Adaptive Multi-Rate Wideband (AMR-WB+) Audio Codec;;;;;RFC 4352;DOI 10.17487/RFC4352;January;https://www.rfc-editor.org/info/rfc4352 | |
| RFC4353;;Rosenberg, J.;A Framework for Conferencing with the Session Initiation Protocol (SIP);;;;;RFC 4353;DOI 10.17487/RFC4353;February;https://www.rfc-editor.org/info/rfc4353 | |
| RFC4354;;Garcia-Martin, M.;A Session Initiation Protocol (SIP) Event Package and Data Format for Various Settings in Support for the Push-to-Talk over Cellular (PoC) Service;;;;;RFC 4354;DOI 10.17487/RFC4354;January;https://www.rfc-editor.org/info/rfc4354 | |
| RFC4355;;Brandner, R., Conroy, L., and R. Stastny;IANA Registration for Enumservices email, fax, mms, ems, and sms;;;;;RFC 4355;DOI 10.17487/RFC4355;January;https://www.rfc-editor.org/info/rfc4355 | |
| RFC4356;;Gellens, R.;Mapping Between the Multimedia Messaging Service (MMS) and Internet Mail;;;;;RFC 4356;DOI 10.17487/RFC4356;January;https://www.rfc-editor.org/info/rfc4356 | |
| RFC4357;;Popov, V., Kurepkin, I., and S. Leontiev;Additional Cryptographic Algorithms for Use with GOST 28147-89, GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 Algorithms;;;;;RFC 4357;DOI 10.17487/RFC4357;January;https://www.rfc-editor.org/info/rfc4357 | |
| RFC4358;;Smith, D.;A Uniform Resource Name (URN) Namespace for the Open Mobile Alliance (OMA);;;;;RFC 4358;DOI 10.17487/RFC4358;January;https://www.rfc-editor.org/info/rfc4358 | |
| RFC4359;;Weis, B.;The Use of RSA/SHA-1 Signatures within Encapsulating Security Payload (ESP) and Authentication Header (AH);;;;;RFC 4359;DOI 10.17487/RFC4359;January;https://www.rfc-editor.org/info/rfc4359 | |
| RFC4360;;Sangli, S., Tappan, D., and Y. Rekhter;BGP Extended Communities Attribute;;;;;RFC 4360;DOI 10.17487/RFC4360;February;https://www.rfc-editor.org/info/rfc4360 | |
| RFC4361;;Lemon, T. and B. Sommerfeld;Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4);;;;;RFC 4361;DOI 10.17487/RFC4361;February;https://www.rfc-editor.org/info/rfc4361 | |
| RFC4362;;Jonsson, L-E., Pelletier, G., and K. Sandlund;RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTP;;;;;RFC 4362;DOI 10.17487/RFC4362;January;https://www.rfc-editor.org/info/rfc4362 | |
| RFC4363;;Levi, D. and D. Harrington;Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering, and Virtual LAN Extensions;;;;;RFC 4363;DOI 10.17487/RFC4363;January;https://www.rfc-editor.org/info/rfc4363 | |
| RFC4364;;Rosen, E. and Y. Rekhter;BGP/MPLS IP Virtual Private Networks (VPNs);;;;;RFC 4364;DOI 10.17487/RFC4364;February;https://www.rfc-editor.org/info/rfc4364 | |
| RFC4365;;Rosen, E.;Applicability Statement for BGP/MPLS IP Virtual Private Networks (VPNs);;;;;RFC 4365;DOI 10.17487/RFC4365;February;https://www.rfc-editor.org/info/rfc4365 | |
| RFC4366;RFC5246, RFC6066;Blake-Wilson, S., Nystrom, M., Hopwood, D., Mikkelsen, J., and T. Wright;Transport Layer Security (TLS) Extensions;;;;;RFC 4366;DOI 10.17487/RFC4366;April;https://www.rfc-editor.org/info/rfc4366 | |
| RFC4367;;Rosenberg, J., Ed., and IAB;What's in a Name: False Assumptions about DNS Names;;;;;RFC 4367;DOI 10.17487/RFC4367;February;https://www.rfc-editor.org/info/rfc4367 | |
| RFC4368;;Nadeau, T. and S. Hegde;Multiprotocol Label Switching (MPLS) Label-Controlled Asynchronous Transfer Mode (ATM) and Frame-Relay Management Interface Definition;;;;;RFC 4368;DOI 10.17487/RFC4368;January;https://www.rfc-editor.org/info/rfc4368 | |
| RFC4369;RFC6173;Gibbons, K., Monia, C., Tseng, J., and F. Travostino;Definitions of Managed Objects for Internet Fibre Channel Protocol (iFCP);;;;;RFC 4369;DOI 10.17487/RFC4369;January;https://www.rfc-editor.org/info/rfc4369 | |
| RFC4370;;Weltman, R.;Lightweight Directory Access Protocol (LDAP) Proxied Authorization Control;;;;;RFC 4370;DOI 10.17487/RFC4370;February;https://www.rfc-editor.org/info/rfc4370 | |
| RFC4371;RFC8714;Carpenter, B., Ed., and L. Lynch, Ed.;BCP 101 Update for IPR Trust;;;;;RFC 4371;DOI 10.17487/RFC4371;January;https://www.rfc-editor.org/info/rfc4371 | |
| RFC4372;;Adrangi, F., Lior, A., Korhonen, J., and J. Loughney;Chargeable User Identity;;;;;RFC 4372;DOI 10.17487/RFC4372;January;https://www.rfc-editor.org/info/rfc4372 | |
| RFC4373;;Harrison, R., Sermersheim, J., and Y. Dong;Lightweight Directory Access Protocol (LDAP) Bulk Update/Replication Protocol (LBURP);;;;;RFC 4373;DOI 10.17487/RFC4373;January;https://www.rfc-editor.org/info/rfc4373 | |
| RFC4374;;McCobb, G.;The application/xv+xml Media Type;;;;;RFC 4374;DOI 10.17487/RFC4374;January;https://www.rfc-editor.org/info/rfc4374 | |
| RFC4375;;Carlberg, K.;Emergency Telecommunications Services (ETS) Requirements for a Single Administrative Domain;;;;;RFC 4375;DOI 10.17487/RFC4375;January;https://www.rfc-editor.org/info/rfc4375 | |
| RFC4376;;Koskelainen, P., Ott, J., Schulzrinne, H., and X. Wu;Requirements for Floor Control Protocols;;;;;RFC 4376;DOI 10.17487/RFC4376;February;https://www.rfc-editor.org/info/rfc4376 | |
| RFC4377;;Nadeau, T., Morrow, M., Swallow, G., Allan, D., and S. Matsushima;Operations and Management (OAM) Requirements for Multi-Protocol Label Switched (MPLS) Networks;;;;;RFC 4377;DOI 10.17487/RFC4377;February;https://www.rfc-editor.org/info/rfc4377 | |
| RFC4378;;Allan, D., Ed., and T. Nadeau, Ed.;A Framework for Multi-Protocol Label Switching (MPLS) Operations and Management (OAM);;;;;RFC 4378;DOI 10.17487/RFC4378;February;https://www.rfc-editor.org/info/rfc4378 | |
| RFC4379;RFC8029;Kompella, K. and G. Swallow;Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures;;;;;RFC 4379;DOI 10.17487/RFC4379;February;https://www.rfc-editor.org/info/rfc4379 | |
| RFC4380;;Huitema, C.;Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs);;;;;RFC 4380;DOI 10.17487/RFC4380;February;https://www.rfc-editor.org/info/rfc4380 | |
| RFC4381;;Behringer, M.;Analysis of the Security of BGP/MPLS IP Virtual Private Networks (VPNs);;;;;RFC 4381;DOI 10.17487/RFC4381;February;https://www.rfc-editor.org/info/rfc4381 | |
| RFC4382;;Nadeau, T., Ed., and H. van der Linde, Ed.;MPLS/BGP Layer 3 Virtual Private Network (VPN) Management Information Base;;;;;RFC 4382;DOI 10.17487/RFC4382;February;https://www.rfc-editor.org/info/rfc4382 | |
| RFC4383;;Baugher, M. and E. Carrara;The Use of Timed Efficient Stream Loss-Tolerant Authentication (TESLA) in the Secure Real-time Transport Protocol (SRTP);;;;;RFC 4383;DOI 10.17487/RFC4383;February;https://www.rfc-editor.org/info/rfc4383 | |
| RFC4384;;Meyer, D.;BGP Communities for Data Collection;;;BCP 114;;RFC 4384;DOI 10.17487/RFC4384;February;https://www.rfc-editor.org/info/rfc4384 | |
| RFC4385;;Bryant, S., Swallow, G., Martini, L., and D. McPherson;Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for Use over an MPLS PSN;;;;;RFC 4385;DOI 10.17487/RFC4385;February;https://www.rfc-editor.org/info/rfc4385 | |
| RFC4386;;Boeyen, S. and P. Hallam-Baker;Internet X.509 Public Key Infrastructure Repository Locator Service;;;;;RFC 4386;DOI 10.17487/RFC4386;February;https://www.rfc-editor.org/info/rfc4386 | |
| RFC4387;;Gutmann, P., Ed.;Internet X.509 Public Key Infrastructure Operational Protocols: Certificate Store Access via HTTP;;;;;RFC 4387;DOI 10.17487/RFC4387;February;https://www.rfc-editor.org/info/rfc4387 | |
| RFC4388;;Woundy, R. and K. Kinnear;Dynamic Host Configuration Protocol (DHCP) Leasequery;;;;;RFC 4388;DOI 10.17487/RFC4388;February;https://www.rfc-editor.org/info/rfc4388 | |
| RFC4389;;Thaler, D., Talwar, M., and C. Patel;Neighbor Discovery Proxies (ND Proxy);;;;;RFC 4389;DOI 10.17487/RFC4389;April;https://www.rfc-editor.org/info/rfc4389 | |
| RFC4390;;Kashyap, V.;Dynamic Host Configuration Protocol (DHCP) over InfiniBand;;;;;RFC 4390;DOI 10.17487/RFC4390;April;https://www.rfc-editor.org/info/rfc4390 | |
| RFC4391;;Chu, J. and V. Kashyap;Transmission of IP over InfiniBand (IPoIB);;;;;RFC 4391;DOI 10.17487/RFC4391;April;https://www.rfc-editor.org/info/rfc4391 | |
| RFC4392;;Kashyap, V.;IP over InfiniBand (IPoIB) Architecture;;;;;RFC 4392;DOI 10.17487/RFC4392;April;https://www.rfc-editor.org/info/rfc4392 | |
| RFC4393;;Garudadri, H.;MIME Type Registrations for 3GPP2 Multimedia Files;;;;;RFC 4393;DOI 10.17487/RFC4393;March;https://www.rfc-editor.org/info/rfc4393 | |
| RFC4394;;Fedyk, D., Aboul-Magd, O., Brungard, D., Lang, J., and D. Papadimitriou;A Transport Network View of the Link Management Protocol (LMP);;;;;RFC 4394;DOI 10.17487/RFC4394;February;https://www.rfc-editor.org/info/rfc4394 | |
| RFC4395;RFC7595;Hansen, T., Hardie, T., and L. Masinter;Guidelines and Registration Procedures for New URI Schemes;;;;;RFC 4395;DOI 10.17487/RFC4395;February;https://www.rfc-editor.org/info/rfc4395 | |
| RFC4396;;Rey, J. and Y. Matsui;RTP Payload Format for 3rd Generation Partnership Project (3GPP) Timed Text;;;;;RFC 4396;DOI 10.17487/RFC4396;February;https://www.rfc-editor.org/info/rfc4396 | |
| RFC4397;;Bryskin, I. and A. Farrel;A Lexicography for the Interpretation of Generalized Multiprotocol Label Switching (GMPLS) Terminology within the Context of the ITU-T's Automatically Switched Optical Network (ASON) Architecture;;;;;RFC 4397;DOI 10.17487/RFC4397;February;https://www.rfc-editor.org/info/rfc4397 | |
| RFC4398;;Josefsson, S.;Storing Certificates in the Domain Name System (DNS);;;;;RFC 4398;DOI 10.17487/RFC4398;March;https://www.rfc-editor.org/info/rfc4398 | |
| RFC4401;;Williams, N.;A Pseudo-Random Function (PRF) API Extension for the Generic Security Service Application Program Interface (GSS-API);;;;;RFC 4401;DOI 10.17487/RFC4401;February;https://www.rfc-editor.org/info/rfc4401 | |
| RFC4402;RFC7802;Williams, N.;A Pseudo-Random Function (PRF) for the Kerberos V Generic Security Service Application Program Interface (GSS-API) Mechanism;;;;;RFC 4402;DOI 10.17487/RFC4402;February;https://www.rfc-editor.org/info/rfc4402 | |
| RFC4403;;Bergeson, B., Boogert, K., and V. Nanjundaswamy;Lightweight Directory Access Protocol (LDAP) Schema for Universal Description, Discovery, and Integration version 3 (UDDIv3);;;;;RFC 4403;DOI 10.17487/RFC4403;February;https://www.rfc-editor.org/info/rfc4403 | |
| RFC4404;;Natarajan, R. and A. Rijhsinghani;Definitions of Managed Objects for Fibre Channel Over TCP/IP (FCIP);;;;;RFC 4404;DOI 10.17487/RFC4404;February;https://www.rfc-editor.org/info/rfc4404 | |
| RFC4405;;Allman, E. and H. Katz;SMTP Service Extension for Indicating the Responsible Submitter of an E-Mail Message;;;;;RFC 4405;DOI 10.17487/RFC4405;April;https://www.rfc-editor.org/info/rfc4405 | |
| RFC4406;;Lyon, J. and M. Wong;Sender ID: Authenticating E-Mail;;;;;RFC 4406;DOI 10.17487/RFC4406;April;https://www.rfc-editor.org/info/rfc4406 | |
| RFC4407;;Lyon, J.;Purported Responsible Address in E-Mail Messages;;;;;RFC 4407;DOI 10.17487/RFC4407;April;https://www.rfc-editor.org/info/rfc4407 | |
| RFC4408;RFC7208;Wong, M. and W. Schlitt;Sender Policy Framework (SPF) for Authorizing Use of Domains in E-Mail, Version 1;;;;;RFC 4408;DOI 10.17487/RFC4408;April;https://www.rfc-editor.org/info/rfc4408 | |
| RFC4409;RFC6409;Gellens, R. and J. Klensin;Message Submission for Mail;;;;;RFC 4409;DOI 10.17487/RFC4409;April;https://www.rfc-editor.org/info/rfc4409 | |
| RFC4410;;Pullen, M., Zhao, F., and D. Cohen;Selectively Reliable Multicast Protocol (SRMP);;;;;RFC 4410;DOI 10.17487/RFC4410;February;https://www.rfc-editor.org/info/rfc4410 | |
| RFC4411;;Polk, J.;Extending the Session Initiation Protocol (SIP) Reason Header for Preemption Events;;;;;RFC 4411;DOI 10.17487/RFC4411;February;https://www.rfc-editor.org/info/rfc4411 | |
| RFC4412;;Schulzrinne, H. and J. Polk;Communications Resource Priority for the Session Initiation Protocol (SIP);;;;;RFC 4412;DOI 10.17487/RFC4412;February;https://www.rfc-editor.org/info/rfc4412 | |
| RFC4413;;West, M. and S. McCann;TCP/IP Field Behavior;;;;;RFC 4413;DOI 10.17487/RFC4413;March;https://www.rfc-editor.org/info/rfc4413 | |
| RFC4414;;Newton, A.;An ENUM Registry Type for the Internet Registry Information Service (IRIS);;;;;RFC 4414;DOI 10.17487/RFC4414;February;https://www.rfc-editor.org/info/rfc4414 | |
| RFC4415;;Brandner, R., Conroy, L., and R. Stastny;IANA Registration for Enumservice Voice;;;;;RFC 4415;DOI 10.17487/RFC4415;February;https://www.rfc-editor.org/info/rfc4415 | |
| RFC4416;;Wong, J., Ed.;Goals for Internet Messaging to Support Diverse Service Environments;;;;;RFC 4416;DOI 10.17487/RFC4416;February;https://www.rfc-editor.org/info/rfc4416 | |
| RFC4417;;Resnick, P., Ed., and P. Saint-Andre, Ed.;Report of the 2004 IAB Messaging Workshop;;;;;RFC 4417;DOI 10.17487/RFC4417;February;https://www.rfc-editor.org/info/rfc4417 | |
| RFC4418;;Krovetz, T., Ed.;UMAC: Message Authentication Code using Universal Hashing;;;;;RFC 4418;DOI 10.17487/RFC4418;March;https://www.rfc-editor.org/info/rfc4418 | |
| RFC4419;;Friedl, M., Provos, N., and W. Simpson;Diffie-Hellman Group Exchange for the Secure Shell (SSH) Transport Layer Protocol;;;;;RFC 4419;DOI 10.17487/RFC4419;March;https://www.rfc-editor.org/info/rfc4419 | |
| RFC4420;RFC5420;Farrel, A., Ed., Papadimitriou, D., Vasseur, J.-P., and A. Ayyangar;Encoding of Attributes for Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) Establishment Using Resource ReserVation Protocol-Traffic Engineering (RSVP-TE);;;;;RFC 4420;DOI 10.17487/RFC4420;February;https://www.rfc-editor.org/info/rfc4420 | |
| RFC4421;;Perkins, C.;RTP Payload Format for Uncompressed Video: Additional Colour Sampling Modes;;;;;RFC 4421;DOI 10.17487/RFC4421;February;https://www.rfc-editor.org/info/rfc4421 | |
| RFC4422;;Melnikov, A., Ed., and K. Zeilenga, Ed.;Simple Authentication and Security Layer (SASL);;;;;RFC 4422;DOI 10.17487/RFC4422;June;https://www.rfc-editor.org/info/rfc4422 | |
| RFC4423;;Moskowitz, R. and P. Nikander;Host Identity Protocol (HIP) Architecture;;;;;RFC 4423;DOI 10.17487/RFC4423;May;https://www.rfc-editor.org/info/rfc4423 | |
| RFC4424;;Ahmadi, S.;Real-Time Transport Protocol (RTP) Payload Format for the Variable-Rate Multimode Wideband (VMR-WB) Extension Audio Codec;;;;;RFC 4424;DOI 10.17487/RFC4424;February;https://www.rfc-editor.org/info/rfc4424 | |
| RFC4425;;Klemets, A.;RTP Payload Format for Video Codec 1 (VC-1);;;;;RFC 4425;DOI 10.17487/RFC4425;February;https://www.rfc-editor.org/info/rfc4425 | |
| RFC4426;;Lang, J., Ed., Rajagopalan, B., Ed., and D. Papadimitriou, Ed.;Generalized Multi-Protocol Label Switching (GMPLS) Recovery Functional Specification;;;;;RFC 4426;DOI 10.17487/RFC4426;March;https://www.rfc-editor.org/info/rfc4426 | |
| RFC4427;;Mannie, E., Ed., and D. Papadimitriou, Ed.;Recovery (Protection and Restoration) Terminology for Generalized Multi-Protocol Label Switching (GMPLS);;;;;RFC 4427;DOI 10.17487/RFC4427;March;https://www.rfc-editor.org/info/rfc4427 | |
| RFC4428;;Papadimitriou, D., Ed., and E. Mannie, Ed.;Analysis of Generalized Multi-Protocol Label Switching (GMPLS)-based Recovery Mechanisms (including Protection and Restoration);;;;;RFC 4428;DOI 10.17487/RFC4428;March;https://www.rfc-editor.org/info/rfc4428 | |
| RFC4429;;Moore, N.;Optimistic Duplicate Address Detection (DAD) for IPv6;;;;;RFC 4429;DOI 10.17487/RFC4429;April;https://www.rfc-editor.org/info/rfc4429 | |
| RFC4430;;Sakane, S., Kamada, K., Thomas, M., and J. Vilhuber;Kerberized Internet Negotiation of Keys (KINK);;;;;RFC 4430;DOI 10.17487/RFC4430;March;https://www.rfc-editor.org/info/rfc4430 | |
| RFC4431;;Andrews, M. and S. Weiler;The DNSSEC Lookaside Validation (DLV) DNS Resource Record;;;;;RFC 4431;DOI 10.17487/RFC4431;February;https://www.rfc-editor.org/info/rfc4431 | |
| RFC4432;;Harris, B.;RSA Key Exchange for the Secure Shell (SSH) Transport Layer Protocol;;;;;RFC 4432;DOI 10.17487/RFC4432;March;https://www.rfc-editor.org/info/rfc4432 | |
| RFC4433;;Kulkarni, M., Patel, A., and K. Leung;Mobile IPv4 Dynamic Home Agent (HA) Assignment;;;;;RFC 4433;DOI 10.17487/RFC4433;March;https://www.rfc-editor.org/info/rfc4433 | |
| RFC4434;;Hoffman, P.;The AES-XCBC-PRF-128 Algorithm for the Internet Key Exchange Protocol (IKE);;;;;RFC 4434;DOI 10.17487/RFC4434;February;https://www.rfc-editor.org/info/rfc4434 | |
| RFC4435;;Nomura, Y., Walsh, R., Luoma, J-P., Asaeda, H., and H. Schulzrinne;A Framework for the Usage of Internet Media Guides (IMGs);;;;;RFC 4435;DOI 10.17487/RFC4435;April;https://www.rfc-editor.org/info/rfc4435 | |
| RFC4436;;Aboba, B., Carlson, J., and S. Cheshire;Detecting Network Attachment in IPv4 (DNAv4);;;;;RFC 4436;DOI 10.17487/RFC4436;March;https://www.rfc-editor.org/info/rfc4436 | |
| RFC4437;;Whitehead, J., Clemm, G., and J. Reschke, Ed.;Web Distributed Authoring and Versioning (WebDAV) Redirect Reference Resources;;;;;RFC 4437;DOI 10.17487/RFC4437;March;https://www.rfc-editor.org/info/rfc4437 | |
| RFC4438;;DeSanti, C., Gaonkar, V., Vivek, H., McCloghrie, K., and S. Gai;Fibre-Channel Name Server MIB;;;;;RFC 4438;DOI 10.17487/RFC4438;April;https://www.rfc-editor.org/info/rfc4438 | |
| RFC4439;;DeSanti, C., Gaonkar, V., McCloghrie, K., and S. Gai;Fibre Channel Fabric Address Manager MIB;;;;;RFC 4439;DOI 10.17487/RFC4439;March;https://www.rfc-editor.org/info/rfc4439 | |
| RFC4440;;Floyd, S., Ed., Paxson, V., Ed., Falk, A., Ed., and IAB;IAB Thoughts on the Role of the Internet Research Task Force (IRTF);;;;;RFC 4440;DOI 10.17487/RFC4440;March;https://www.rfc-editor.org/info/rfc4440 | |
| RFC4441;RFC7241;Aboba, B., Ed.;The IEEE 802/IETF Relationship;;;;;RFC 4441;DOI 10.17487/RFC4441;March;https://www.rfc-editor.org/info/rfc4441 | |
| RFC4442;;Fries, S. and H. Tschofenig;Bootstrapping Timed Efficient Stream Loss-Tolerant Authentication (TESLA);;;;;RFC 4442;DOI 10.17487/RFC4442;March;https://www.rfc-editor.org/info/rfc4442 | |
| RFC4443;;Conta, A., Deering, S., and M. Gupta, Ed.;Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification;;;;STD 89;RFC 4443;DOI 10.17487/RFC4443;March;https://www.rfc-editor.org/info/rfc4443 | |
| RFC4444;;Parker, J., Ed.;Management Information Base for Intermediate System to Intermediate System (IS-IS);;;;;RFC 4444;DOI 10.17487/RFC4444;April;https://www.rfc-editor.org/info/rfc4444 | |
| RFC4445;;Welch, J. and J. Clark;A Proposed Media Delivery Index (MDI);;;;;RFC 4445;DOI 10.17487/RFC4445;April;https://www.rfc-editor.org/info/rfc4445 | |
| RFC4446;;Martini, L.;IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3);;;BCP 116;;RFC 4446;DOI 10.17487/RFC4446;April;https://www.rfc-editor.org/info/rfc4446 | |
| RFC4447;RFC8077;Martini, L., Ed., Rosen, E., El-Aawar, N., Smith, T., and G. Heron;Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP);;;;;RFC 4447;DOI 10.17487/RFC4447;April;https://www.rfc-editor.org/info/rfc4447 | |
| RFC4448;;Martini, L., Ed., Rosen, E., El-Aawar, N., and G. Heron;Encapsulation Methods for Transport of Ethernet over MPLS Networks;;;;;RFC 4448;DOI 10.17487/RFC4448;April;https://www.rfc-editor.org/info/rfc4448 | |
| RFC4449;;Perkins, C.;Securing Mobile IPv6 Route Optimization Using a Static Shared Key;;;;;RFC 4449;DOI 10.17487/RFC4449;June;https://www.rfc-editor.org/info/rfc4449 | |
| RFC4450;;Lear, E. and H. Alvestrand;Getting Rid of the Cruft: Report from an Experiment in Identifying and Reclassifying Obsolete Standards Documents;;;;;RFC 4450;DOI 10.17487/RFC4450;March;https://www.rfc-editor.org/info/rfc4450 | |
| RFC4451;;McPherson, D. and V. Gill;BGP MULTI_EXIT_DISC (MED) Considerations;;;;;RFC 4451;DOI 10.17487/RFC4451;March;https://www.rfc-editor.org/info/rfc4451 | |
| RFC4452;;Van de Sompel, H., Hammond, T., Neylon, E., and S. Weibel;The "info" URI Scheme for Information Assets with Identifiers in Public Namespaces;;;;;RFC 4452;DOI 10.17487/RFC4452;April;https://www.rfc-editor.org/info/rfc4452 | |
| RFC4453;;Rosenberg, J., Camarillo, G., Ed., and D. Willis;Requirements for Consent-Based Communications in the Session Initiation Protocol (SIP);;;;;RFC 4453;DOI 10.17487/RFC4453;April;https://www.rfc-editor.org/info/rfc4453 | |
| RFC4454;;Singh, S., Townsley, M., and C. Pignataro;Asynchronous Transfer Mode (ATM) over Layer 2 Tunneling Protocol Version 3 (L2TPv3);;;;;RFC 4454;DOI 10.17487/RFC4454;May;https://www.rfc-editor.org/info/rfc4454 | |
| RFC4455;;Hallak-Stamler, M., Bakke, M., Lederman, Y., Krueger, M., and K. McCloghrie;Definition of Managed Objects for Small Computer System Interface (SCSI) Entities;;;;;RFC 4455;DOI 10.17487/RFC4455;April;https://www.rfc-editor.org/info/rfc4455 | |
| RFC4456;;Bates, T., Chen, E., and R. Chandra;BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP);;;;;RFC 4456;DOI 10.17487/RFC4456;April;https://www.rfc-editor.org/info/rfc4456 | |
| RFC4457;;Camarillo, G. and G. Blanco;The Session Initiation Protocol (SIP) P-User-Database Private-Header (P-Header);;;;;RFC 4457;DOI 10.17487/RFC4457;April;https://www.rfc-editor.org/info/rfc4457 | |
| RFC4458;;Jennings, C., Audet, F., and J. Elwell;Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR);;;;;RFC 4458;DOI 10.17487/RFC4458;April;https://www.rfc-editor.org/info/rfc4458 | |
| RFC4459;;Savola, P.;MTU and Fragmentation Issues with In-the-Network Tunneling;;;;;RFC 4459;DOI 10.17487/RFC4459;April;https://www.rfc-editor.org/info/rfc4459 | |
| RFC4460;;Stewart, R., Arias-Rodriguez, I., Poon, K., Caro, A., and M. Tuexen;Stream Control Transmission Protocol (SCTP) Specification Errata and Issues;;;;;RFC 4460;DOI 10.17487/RFC4460;April;https://www.rfc-editor.org/info/rfc4460 | |
| RFC4461;;Yasukawa, S., Ed.;Signaling Requirements for Point-to-Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs);;;;;RFC 4461;DOI 10.17487/RFC4461;April;https://www.rfc-editor.org/info/rfc4461 | |
| RFC4462;;Hutzelman, J., Salowey, J., Galbraith, J., and V. Welch;Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol;;;;;RFC 4462;DOI 10.17487/RFC4462;May;https://www.rfc-editor.org/info/rfc4462 | |
| RFC4463;;Shanmugham, S., Monaco, P., and B. Eberman;A Media Resource Control Protocol (MRCP) Developed by Cisco, Nuance, and Speechworks;;;;;RFC 4463;DOI 10.17487/RFC4463;April;https://www.rfc-editor.org/info/rfc4463 | |
| RFC4464;;Surtees, A. and M. West;Signaling Compression (SigComp) Users' Guide;;;;;RFC 4464;DOI 10.17487/RFC4464;May;https://www.rfc-editor.org/info/rfc4464 | |
| RFC4465;;Surtees, A. and M. West;Signaling Compression (SigComp) Torture Tests;;;;;RFC 4465;DOI 10.17487/RFC4465;June;https://www.rfc-editor.org/info/rfc4465 | |
| RFC4466;;Melnikov, A. and C. Daboo;Collected Extensions to IMAP4 ABNF;;;;;RFC 4466;DOI 10.17487/RFC4466;April;https://www.rfc-editor.org/info/rfc4466 | |
| RFC4467;;Crispin, M.;Internet Message Access Protocol (IMAP) - URLAUTH Extension;;;;;RFC 4467;DOI 10.17487/RFC4467;May;https://www.rfc-editor.org/info/rfc4467 | |
| RFC4468;;Newman, C.;Message Submission BURL Extension;;;;;RFC 4468;DOI 10.17487/RFC4468;May;https://www.rfc-editor.org/info/rfc4468 | |
| RFC4469;;Resnick, P.;Internet Message Access Protocol (IMAP) CATENATE Extension;;;;;RFC 4469;DOI 10.17487/RFC4469;April;https://www.rfc-editor.org/info/rfc4469 | |
| RFC4470;;Weiler, S. and J. Ihren;Minimally Covering NSEC Records and DNSSEC On-line Signing;;;;;RFC 4470;DOI 10.17487/RFC4470;April;https://www.rfc-editor.org/info/rfc4470 | |
| RFC4471;;Sisson, G. and B. Laurie;Derivation of DNS Name Predecessor and Successor;;;;;RFC 4471;DOI 10.17487/RFC4471;September;https://www.rfc-editor.org/info/rfc4471 | |
| RFC4472;;Durand, A., Ihren, J., and P. Savola;Operational Considerations and Issues with IPv6 DNS;;;;;RFC 4472;DOI 10.17487/RFC4472;April;https://www.rfc-editor.org/info/rfc4472 | |
| RFC4473;;Nomura, Y., Walsh, R., Luoma, J-P., Ott, J., and H. Schulzrinne;Requirements for Internet Media Guides (IMGs);;;;;RFC 4473;DOI 10.17487/RFC4473;May;https://www.rfc-editor.org/info/rfc4473 | |
| RFC4474;RFC8224;Peterson, J. and C. Jennings;Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP);;;;;RFC 4474;DOI 10.17487/RFC4474;August;https://www.rfc-editor.org/info/rfc4474 | |
| RFC4475;;Sparks, R., Ed., Hawrylyshen, A., Johnston, A., Rosenberg, J., and H. Schulzrinne;Session Initiation Protocol (SIP) Torture Test Messages;;;;;RFC 4475;DOI 10.17487/RFC4475;May;https://www.rfc-editor.org/info/rfc4475 | |
| RFC4476;;Francis, C. and D. Pinkas;Attribute Certificate (AC) Policies Extension;;;;;RFC 4476;DOI 10.17487/RFC4476;May;https://www.rfc-editor.org/info/rfc4476 | |
| RFC4477;;Chown, T., Venaas, S., and C. Strauf;Dynamic Host Configuration Protocol (DHCP): IPv4 and IPv6 Dual-Stack Issues;;;;;RFC 4477;DOI 10.17487/RFC4477;May;https://www.rfc-editor.org/info/rfc4477 | |
| RFC4478;;Nir, Y.;Repeated Authentication in Internet Key Exchange (IKEv2) Protocol;;;;;RFC 4478;DOI 10.17487/RFC4478;April;https://www.rfc-editor.org/info/rfc4478 | |
| RFC4479;;Rosenberg, J.;A Data Model for Presence;;;;;RFC 4479;DOI 10.17487/RFC4479;July;https://www.rfc-editor.org/info/rfc4479 | |
| RFC4480;;Schulzrinne, H., Gurbani, V., Kyzivat, P., and J. Rosenberg;RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF);;;;;RFC 4480;DOI 10.17487/RFC4480;July;https://www.rfc-editor.org/info/rfc4480 | |
| RFC4481;;Schulzrinne, H.;Timed Presence Extensions to the Presence Information Data Format (PIDF) to Indicate Status Information for Past and Future Time Intervals;;;;;RFC 4481;DOI 10.17487/RFC4481;July;https://www.rfc-editor.org/info/rfc4481 | |
| RFC4482;;Schulzrinne, H.;CIPID: Contact Information for the Presence Information Data Format;;;;;RFC 4482;DOI 10.17487/RFC4482;July;https://www.rfc-editor.org/info/rfc4482 | |
| RFC4483;;Burger, E., Ed.;A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages;;;;;RFC 4483;DOI 10.17487/RFC4483;May;https://www.rfc-editor.org/info/rfc4483 | |
| RFC4484;;Peterson, J., Polk, J., Sicker, D., and H. Tschofenig;Trait-Based Authorization Requirements for the Session Initiation Protocol (SIP);;;;;RFC 4484;DOI 10.17487/RFC4484;August;https://www.rfc-editor.org/info/rfc4484 | |
| RFC4485;;Rosenberg, J. and H. Schulzrinne;Guidelines for Authors of Extensions to the Session Initiation Protocol (SIP);;;;;RFC 4485;DOI 10.17487/RFC4485;May;https://www.rfc-editor.org/info/rfc4485 | |
| RFC4486;;Chen, E. and V. Gillet;Subcodes for BGP Cease Notification Message;;;;;RFC 4486;DOI 10.17487/RFC4486;April;https://www.rfc-editor.org/info/rfc4486 | |
| RFC4487;;Le, F., Faccin, S., Patil, B., and H. Tschofenig;Mobile IPv6 and Firewalls: Problem Statement;;;;;RFC 4487;DOI 10.17487/RFC4487;May;https://www.rfc-editor.org/info/rfc4487 | |
| RFC4488;;Levin, O.;Suppression of Session Initiation Protocol (SIP) REFER Method Implicit Subscription;;;;;RFC 4488;DOI 10.17487/RFC4488;May;https://www.rfc-editor.org/info/rfc4488 | |
| RFC4489;;Park, J-S., Shin, M-K., and H-J. Kim;A Method for Generating Link-Scoped IPv6 Multicast Addresses;;;;;RFC 4489;DOI 10.17487/RFC4489;April;https://www.rfc-editor.org/info/rfc4489 | |
| RFC4490;;Leontiev, S., Ed., and G. Chudov, Ed.;Using the GOST 28147-89, GOST R 34.11-94, GOST R 34.10-94, and GOST R 34.10-2001 Algorithms with Cryptographic Message Syntax (CMS);;;;;RFC 4490;DOI 10.17487/RFC4490;May;https://www.rfc-editor.org/info/rfc4490 | |
| RFC4491;;Leontiev, S., Ed., and D. Shefanovski, Ed.;Using the GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 Algorithms with the Internet X.509 Public Key Infrastructure Certificate and CRL Profile;;;;;RFC 4491;DOI 10.17487/RFC4491;May;https://www.rfc-editor.org/info/rfc4491 | |
| RFC4492;RFC8422;Blake-Wilson, S., Bolyard, N., Gupta, V., Hawk, C., and B. Moeller;Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security (TLS);;;;;RFC 4492;DOI 10.17487/RFC4492;May;https://www.rfc-editor.org/info/rfc4492 | |
| RFC4493;;Song, JH., Poovendran, R., Lee, J., and T. Iwata;The AES-CMAC Algorithm;;;;;RFC 4493;DOI 10.17487/RFC4493;June;https://www.rfc-editor.org/info/rfc4493 | |
| RFC4494;;Song, JH., Poovendran, R., and J. Lee;The AES-CMAC-96 Algorithm and Its Use with IPsec;;;;;RFC 4494;DOI 10.17487/RFC4494;June;https://www.rfc-editor.org/info/rfc4494 | |
| RFC4495;;Polk, J. and S. Dhesikan;A Resource Reservation Protocol (RSVP) Extension for the Reduction of Bandwidth of a Reservation Flow;;;;;RFC 4495;DOI 10.17487/RFC4495;May;https://www.rfc-editor.org/info/rfc4495 | |
| RFC4496;;Stecher, M. and A. Barbir;Open Pluggable Edge Services (OPES) SMTP Use Cases;;;;;RFC 4496;DOI 10.17487/RFC4496;May;https://www.rfc-editor.org/info/rfc4496 | |
| RFC4497;;Elwell, J., Derks, F., Mourot, P., and O. Rousseau;Interworking between the Session Initiation Protocol (SIP) and QSIG;;;BCP 117;;RFC 4497;DOI 10.17487/RFC4497;May;https://www.rfc-editor.org/info/rfc4497 | |
| RFC4498;;Keeni, G.;The Managed Object Aggregation MIB;;;;;RFC 4498;DOI 10.17487/RFC4498;May;https://www.rfc-editor.org/info/rfc4498 | |
| RFC4501;;Josefsson, S.;Domain Name System Uniform Resource Identifiers;;;;;RFC 4501;DOI 10.17487/RFC4501;May;https://www.rfc-editor.org/info/rfc4501 | |
| RFC4502;;Waldbusser, S.;Remote Network Monitoring Management Information Base Version 2;;;;;RFC 4502;DOI 10.17487/RFC4502;May;https://www.rfc-editor.org/info/rfc4502 | |
| RFC4503;;Boesgaard, M., Vesterager, M., and E. Zenner;A Description of the Rabbit Stream Cipher Algorithm;;;;;RFC 4503;DOI 10.17487/RFC4503;May;https://www.rfc-editor.org/info/rfc4503 | |
| RFC4504;;Sinnreich, H., Ed., Lass, S., and C. Stredicke;SIP Telephony Device Requirements and Configuration;;;;;RFC 4504;DOI 10.17487/RFC4504;May;https://www.rfc-editor.org/info/rfc4504 | |
| RFC4505;;Zeilenga, K.;Anonymous Simple Authentication and Security Layer (SASL) Mechanism;;;;;RFC 4505;DOI 10.17487/RFC4505;June;https://www.rfc-editor.org/info/rfc4505 | |
| RFC4506;;Eisler, M., Ed.;XDR: External Data Representation Standard;;;;STD 67;RFC 4506;DOI 10.17487/RFC4506;May;https://www.rfc-editor.org/info/rfc4506 | |
| RFC4507;RFC5077;Salowey, J., Zhou, H., Eronen, P., and H. Tschofenig;Transport Layer Security (TLS) Session Resumption without Server-Side State;;;;;RFC 4507;DOI 10.17487/RFC4507;May;https://www.rfc-editor.org/info/rfc4507 | |
| RFC4508;;Levin, O. and A. Johnston;Conveying Feature Tags with the Session Initiation Protocol (SIP) REFER Method;;;;;RFC 4508;DOI 10.17487/RFC4508;May;https://www.rfc-editor.org/info/rfc4508 | |
| RFC4509;;Hardaker, W.;Use of SHA-256 in DNSSEC Delegation Signer (DS) Resource Records (RRs);;;;;RFC 4509;DOI 10.17487/RFC4509;May;https://www.rfc-editor.org/info/rfc4509 | |
| RFC4510;;Zeilenga, K., Ed.;Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map;;;;;RFC 4510;DOI 10.17487/RFC4510;June;https://www.rfc-editor.org/info/rfc4510 | |
| RFC4511;;Sermersheim, J., Ed.;Lightweight Directory Access Protocol (LDAP): The Protocol;;;;;RFC 4511;DOI 10.17487/RFC4511;June;https://www.rfc-editor.org/info/rfc4511 | |
| RFC4512;;Zeilenga, K., Ed.;Lightweight Directory Access Protocol (LDAP): Directory Information Models;;;;;RFC 4512;DOI 10.17487/RFC4512;June;https://www.rfc-editor.org/info/rfc4512 | |
| RFC4513;;Harrison, R., Ed.;Lightweight Directory Access Protocol (LDAP): Authentication Methods and Security Mechanisms;;;;;RFC 4513;DOI 10.17487/RFC4513;June;https://www.rfc-editor.org/info/rfc4513 | |
| RFC4514;;Zeilenga, K., Ed.;Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished Names;;;;;RFC 4514;DOI 10.17487/RFC4514;June;https://www.rfc-editor.org/info/rfc4514 | |
| RFC4515;;Smith, M., Ed., and T. Howes;Lightweight Directory Access Protocol (LDAP): String Representation of Search Filters;;;;;RFC 4515;DOI 10.17487/RFC4515;June;https://www.rfc-editor.org/info/rfc4515 | |
| RFC4516;;Smith, M., Ed., and T. Howes;Lightweight Directory Access Protocol (LDAP): Uniform Resource Locator;;;;;RFC 4516;DOI 10.17487/RFC4516;June;https://www.rfc-editor.org/info/rfc4516 | |
| RFC4517;;Legg, S., Ed.;Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules;;;;;RFC 4517;DOI 10.17487/RFC4517;June;https://www.rfc-editor.org/info/rfc4517 | |
| RFC4518;;Zeilenga, K.;Lightweight Directory Access Protocol (LDAP): Internationalized String Preparation;;;;;RFC 4518;DOI 10.17487/RFC4518;June;https://www.rfc-editor.org/info/rfc4518 | |
| RFC4519;;Sciberras, A., Ed.;Lightweight Directory Access Protocol (LDAP): Schema for User Applications;;;;;RFC 4519;DOI 10.17487/RFC4519;June;https://www.rfc-editor.org/info/rfc4519 | |
| RFC4520;;Zeilenga, K.;Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP);;;BCP 64;;RFC 4520;DOI 10.17487/RFC4520;June;https://www.rfc-editor.org/info/rfc4520 | |
| RFC4521;;Zeilenga, K.;Considerations for Lightweight Directory Access Protocol (LDAP) Extensions;;;BCP 118;;RFC 4521;DOI 10.17487/RFC4521;June;https://www.rfc-editor.org/info/rfc4521 | |
| RFC4522;;Legg, S.;Lightweight Directory Access Protocol (LDAP): The Binary Encoding Option;;;;;RFC 4522;DOI 10.17487/RFC4522;June;https://www.rfc-editor.org/info/rfc4522 | |
| RFC4523;;Zeilenga, K.;Lightweight Directory Access Protocol (LDAP) Schema Definitions for X.509 Certificates;;;;;RFC 4523;DOI 10.17487/RFC4523;June;https://www.rfc-editor.org/info/rfc4523 | |
| RFC4524;;Zeilenga, K., Ed.;COSINE LDAP/X.500 Schema;;;;;RFC 4524;DOI 10.17487/RFC4524;June;https://www.rfc-editor.org/info/rfc4524 | |
| RFC4525;;Zeilenga, K.;Lightweight Directory Access Protocol (LDAP) Modify-Increment Extension;;;;;RFC 4525;DOI 10.17487/RFC4525;June;https://www.rfc-editor.org/info/rfc4525 | |
| RFC4526;;Zeilenga, K.;Lightweight Directory Access Protocol (LDAP) Absolute True and False Filters;;;;;RFC 4526;DOI 10.17487/RFC4526;June;https://www.rfc-editor.org/info/rfc4526 | |
| RFC4527;;Zeilenga, K.;Lightweight Directory Access Protocol (LDAP) Read Entry Controls;;;;;RFC 4527;DOI 10.17487/RFC4527;June;https://www.rfc-editor.org/info/rfc4527 | |
| RFC4528;;Zeilenga, K.;Lightweight Directory Access Protocol (LDAP) Assertion Control;;;;;RFC 4528;DOI 10.17487/RFC4528;June;https://www.rfc-editor.org/info/rfc4528 | |
| RFC4529;;Zeilenga, K.;Requesting Attributes by Object Class in the Lightweight Directory Access Protocol;;;;;RFC 4529;DOI 10.17487/RFC4529;June;https://www.rfc-editor.org/info/rfc4529 | |
| RFC4530;;Zeilenga, K.;Lightweight Directory Access Protocol (LDAP) entryUUID Operational Attribute;;;;;RFC 4530;DOI 10.17487/RFC4530;June;https://www.rfc-editor.org/info/rfc4530 | |
| RFC4531;;Zeilenga, K.;Lightweight Directory Access Protocol (LDAP) Turn Operation;;;;;RFC 4531;DOI 10.17487/RFC4531;June;https://www.rfc-editor.org/info/rfc4531 | |
| RFC4532;;Zeilenga, K.;Lightweight Directory Access Protocol (LDAP) "Who am I?" Operation;;;;;RFC 4532;DOI 10.17487/RFC4532;June;https://www.rfc-editor.org/info/rfc4532 | |
| RFC4533;;Zeilenga, K. and J. Choi;The Lightweight Directory Access Protocol (LDAP) Content Synchronization Operation;;;;;RFC 4533;DOI 10.17487/RFC4533;June;https://www.rfc-editor.org/info/rfc4533 | |
| RFC4534;;A Colegrove and H Harney;Group Security Policy Token v1;;;;;RFC 4534;DOI 10.17487/RFC4534;June;https://www.rfc-editor.org/info/rfc4534 | |
| RFC4535;;Harney, H., Meth, U., Colegrove, A., and G. Gross;GSAKMP: Group Secure Association Key Management Protocol;;;;;RFC 4535;DOI 10.17487/RFC4535;June;https://www.rfc-editor.org/info/rfc4535 | |
| RFC4536;;Hoschka, P.;The application/smil and application/smil+xml Media Types;;;;;RFC 4536;DOI 10.17487/RFC4536;July;https://www.rfc-editor.org/info/rfc4536 | |
| RFC4537;;Zhu, L., Leach, P., and K. Jaganathan;Kerberos Cryptosystem Negotiation Extension;;;;;RFC 4537;DOI 10.17487/RFC4537;June;https://www.rfc-editor.org/info/rfc4537 | |
| RFC4538;;Rosenberg, J.;Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP);;;;;RFC 4538;DOI 10.17487/RFC4538;June;https://www.rfc-editor.org/info/rfc4538 | |
| RFC4539;;Edwards, T.;Media Type Registration for the Society of Motion Picture and Television Engineers (SMPTE) Material Exchange Format (MXF);;;;;RFC 4539;DOI 10.17487/RFC4539;May;https://www.rfc-editor.org/info/rfc4539 | |
| RFC4540;;Stiemerling, M., Quittek, J., and C. Cadar;NEC's Simple Middlebox Configuration (SIMCO) Protocol Version 3.0;;;;;RFC 4540;DOI 10.17487/RFC4540;May;https://www.rfc-editor.org/info/rfc4540 | |
| RFC4541;;Christensen, M., Kimball, K., and F. Solensky;Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches;;;;;RFC 4541;DOI 10.17487/RFC4541;May;https://www.rfc-editor.org/info/rfc4541 | |
| RFC4542;;Baker, F. and J. Polk;Implementing an Emergency Telecommunications Service (ETS) for Real-Time Services in the Internet Protocol Suite;;;;;RFC 4542;DOI 10.17487/RFC4542;May;https://www.rfc-editor.org/info/rfc4542 | |
| RFC4543;;McGrew, D. and J. Viega;The Use of Galois Message Authentication Code (GMAC) in IPsec ESP and AH;;;;;RFC 4543;DOI 10.17487/RFC4543;May;https://www.rfc-editor.org/info/rfc4543 | |
| RFC4544;RFC7147;Bakke, M., Krueger, M., McSweeney, T., and J. Muchow;Definitions of Managed Objects for Internet Small Computer System Interface (iSCSI);;;;;RFC 4544;DOI 10.17487/RFC4544;May;https://www.rfc-editor.org/info/rfc4544 | |
| RFC4545;;Bakke, M. and J. Muchow;Definitions of Managed Objects for IP Storage User Identity Authorization;;;;;RFC 4545;DOI 10.17487/RFC4545;May;https://www.rfc-editor.org/info/rfc4545 | |
| RFC4546;;Raftus, D. and E. Cardona;Radio Frequency (RF) Interface Management Information Base for Data over Cable Service Interface Specifications (DOCSIS) 2.0 Compliant RF Interfaces;;;;;RFC 4546;DOI 10.17487/RFC4546;June;https://www.rfc-editor.org/info/rfc4546 | |
| RFC4547;;Ahmad, A. and G. Nakanishi;Event Notification Management Information Base for Data over Cable Service Interface Specifications (DOCSIS)-Compliant Cable Modems and Cable Modem Termination Systems;;;;;RFC 4547;DOI 10.17487/RFC4547;June;https://www.rfc-editor.org/info/rfc4547 | |
| RFC4548;;Gray, E., Rutemiller, J., and G. Swallow;Internet Code Point (ICP) Assignments for NSAP Addresses;;;;;RFC 4548;DOI 10.17487/RFC4548;May;https://www.rfc-editor.org/info/rfc4548 | |
| RFC4549;;Melnikov, A., Ed.;Synchronization Operations for Disconnected IMAP4 Clients;;;;;RFC 4549;DOI 10.17487/RFC4549;June;https://www.rfc-editor.org/info/rfc4549 | |
| RFC4550;RFC5550;Maes, S. and A. Melnikov;Internet Email to Support Diverse Service Environments (Lemonade) Profile;;;;;RFC 4550;DOI 10.17487/RFC4550;June;https://www.rfc-editor.org/info/rfc4550 | |
| RFC4551;RFC7162;Melnikov, A. and S. Hole;IMAP Extension for Conditional STORE Operation or Quick Flag Changes Resynchronization;;;;;RFC 4551;DOI 10.17487/RFC4551;June;https://www.rfc-editor.org/info/rfc4551 | |
| RFC4552;;Gupta, M. and N. Melam;Authentication/Confidentiality for OSPFv3;;;;;RFC 4552;DOI 10.17487/RFC4552;June;https://www.rfc-editor.org/info/rfc4552 | |
| RFC4553;;Vainshtein, A., Ed., and YJ. Stein, Ed.;Structure-Agnostic Time Division Multiplexing (TDM) over Packet (SAToP);;;;;RFC 4553;DOI 10.17487/RFC4553;June;https://www.rfc-editor.org/info/rfc4553 | |
| RFC4554;;Chown, T.;Use of VLANs for IPv4-IPv6 Coexistence in Enterprise Networks;;;;;RFC 4554;DOI 10.17487/RFC4554;June;https://www.rfc-editor.org/info/rfc4554 | |
| RFC4555;;Eronen, P.;IKEv2 Mobility and Multihoming Protocol (MOBIKE);;;;;RFC 4555;DOI 10.17487/RFC4555;June;https://www.rfc-editor.org/info/rfc4555 | |
| RFC4556;;Zhu, L. and B. Tung;Public Key Cryptography for Initial Authentication in Kerberos (PKINIT);;;;;RFC 4556;DOI 10.17487/RFC4556;June;https://www.rfc-editor.org/info/rfc4556 | |
| RFC4557;;Zhu, L., Jaganathan, K., and N. Williams;Online Certificate Status Protocol (OCSP) Support for Public Key Cryptography for Initial Authentication in Kerberos (PKINIT);;;;;RFC 4557;DOI 10.17487/RFC4557;June;https://www.rfc-editor.org/info/rfc4557 | |
| RFC4558;;Ali, Z., Rahman, R., Prairie, D., and D. Papadimitriou;Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification Statement;;;;;RFC 4558;DOI 10.17487/RFC4558;June;https://www.rfc-editor.org/info/rfc4558 | |
| RFC4559;;Jaganathan, K., Zhu, L., and J. Brezak;SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows;;;;;RFC 4559;DOI 10.17487/RFC4559;June;https://www.rfc-editor.org/info/rfc4559 | |
| RFC4560;;Quittek, J., Ed., and K. White, Ed.;Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations;;;;;RFC 4560;DOI 10.17487/RFC4560;June;https://www.rfc-editor.org/info/rfc4560 | |
| RFC4561;;Vasseur, J.-P., Ed., Ali, Z., and S. Sivabalan;Definition of a Record Route Object (RRO) Node-Id Sub-Object;;;;;RFC 4561;DOI 10.17487/RFC4561;June;https://www.rfc-editor.org/info/rfc4561 | |
| RFC4562;;Melsen, T. and S. Blake;MAC-Forced Forwarding: A Method for Subscriber Separation on an Ethernet Access Network;;;;;RFC 4562;DOI 10.17487/RFC4562;June;https://www.rfc-editor.org/info/rfc4562 | |
| RFC4563;;Carrara, E., Lehtovirta, V., and K. Norrman;The Key ID Information Type for the General Extension Payload in Multimedia Internet KEYing (MIKEY);;;;;RFC 4563;DOI 10.17487/RFC4563;June;https://www.rfc-editor.org/info/rfc4563 | |
| RFC4564;;Govindan, S., Ed., Cheng, H., Yao, ZH., Zhou, WH., and L. Yang;Objectives for Control and Provisioning of Wireless Access Points (CAPWAP);;;;;RFC 4564;DOI 10.17487/RFC4564;July;https://www.rfc-editor.org/info/rfc4564 | |
| RFC4565;;Loher, D., Nelson, D., Volinsky, O., and B. Sarikaya;Evaluation of Candidate Control and Provisioning of Wireless Access Points (CAPWAP) Protocols;;;;;RFC 4565;DOI 10.17487/RFC4565;July;https://www.rfc-editor.org/info/rfc4565 | |
| RFC4566;;Handley, M., Jacobson, V., and C. Perkins;SDP: Session Description Protocol;;;;;RFC 4566;DOI 10.17487/RFC4566;July;https://www.rfc-editor.org/info/rfc4566 | |
| RFC4567;;Arkko, J., Lindholm, F., Naslund, M., Norrman, K., and E. Carrara;Key Management Extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP);;;;;RFC 4567;DOI 10.17487/RFC4567;July;https://www.rfc-editor.org/info/rfc4567 | |
| RFC4568;;Andreasen, F., Baugher, M., and D. Wing;Session Description Protocol (SDP) Security Descriptions for Media Streams;;;;;RFC 4568;DOI 10.17487/RFC4568;July;https://www.rfc-editor.org/info/rfc4568 | |
| RFC4569;;Camarillo, G.;Internet Assigned Number Authority (IANA) Registration of the Message Media Feature Tag;;;;;RFC 4569;DOI 10.17487/RFC4569;July;https://www.rfc-editor.org/info/rfc4569 | |
| RFC4570;;Quinn, B. and R. Finlayson;Session Description Protocol (SDP) Source Filters;;;;;RFC 4570;DOI 10.17487/RFC4570;July;https://www.rfc-editor.org/info/rfc4570 | |
| RFC4571;;Lazzaro, J.;Framing Real-time Transport Protocol (RTP) and RTP Control Protocol (RTCP) Packets over Connection-Oriented Transport;;;;;RFC 4571;DOI 10.17487/RFC4571;July;https://www.rfc-editor.org/info/rfc4571 | |
| RFC4572;RFC8122;Lennox, J.;Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP);;;;;RFC 4572;DOI 10.17487/RFC4572;July;https://www.rfc-editor.org/info/rfc4572 | |
| RFC4573;;Even, R. and A. Lochbaum;MIME Type Registration for RTP Payload Format for H.224;;;;;RFC 4573;DOI 10.17487/RFC4573;July;https://www.rfc-editor.org/info/rfc4573 | |
| RFC4574;;Levin, O. and G. Camarillo;The Session Description Protocol (SDP) Label Attribute;;;;;RFC 4574;DOI 10.17487/RFC4574;August;https://www.rfc-editor.org/info/rfc4574 | |
| RFC4575;;Rosenberg, J., Schulzrinne, H., and O. Levin, Ed.;A Session Initiation Protocol (SIP) Event Package for Conference State;;;;;RFC 4575;DOI 10.17487/RFC4575;August;https://www.rfc-editor.org/info/rfc4575 | |
| RFC4576;;Rosen, E., Psenak, P., and P. Pillay-Esnault;Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs);;;;;RFC 4576;DOI 10.17487/RFC4576;June;https://www.rfc-editor.org/info/rfc4576 | |
| RFC4577;;Rosen, E., Psenak, P., and P. Pillay-Esnault;OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs);;;;;RFC 4577;DOI 10.17487/RFC4577;June;https://www.rfc-editor.org/info/rfc4577 | |
| RFC4578;;Johnston, M. and S. Venaas, Ed.;Dynamic Host Configuration Protocol (DHCP) Options for the Intel Preboot eXecution Environment (PXE);;;;;RFC 4578;DOI 10.17487/RFC4578;November;https://www.rfc-editor.org/info/rfc4578 | |
| RFC4579;;Johnston, A. and O. Levin;Session Initiation Protocol (SIP) Call Control - Conferencing for User Agents;;;BCP 119;;RFC 4579;DOI 10.17487/RFC4579;August;https://www.rfc-editor.org/info/rfc4579 | |
| RFC4580;;Volz, B.;Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Subscriber-ID Option;;;;;RFC 4580;DOI 10.17487/RFC4580;June;https://www.rfc-editor.org/info/rfc4580 | |
| RFC4581;;Bagnulo, M. and J. Arkko;Cryptographically Generated Addresses (CGA) Extension Field Format;;;;;RFC 4581;DOI 10.17487/RFC4581;October;https://www.rfc-editor.org/info/rfc4581 | |
| RFC4582;;Camarillo, G., Ott, J., and K. Drage;The Binary Floor Control Protocol (BFCP);;;;;RFC 4582;DOI 10.17487/RFC4582;November;https://www.rfc-editor.org/info/rfc4582 | |
| RFC4583;;Camarillo, G.;Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams;;;;;RFC 4583;DOI 10.17487/RFC4583;November;https://www.rfc-editor.org/info/rfc4583 | |
| RFC4584;;Chakrabarti, S. and E. Nordmark;Extension to Sockets API for Mobile IPv6;;;;;RFC 4584;DOI 10.17487/RFC4584;July;https://www.rfc-editor.org/info/rfc4584 | |
| RFC4585;;Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey;Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF);;;;;RFC 4585;DOI 10.17487/RFC4585;July;https://www.rfc-editor.org/info/rfc4585 | |
| RFC4586;;Burmeister, C., Hakenberg, R., Miyazaki, A., Ott, J., Sato, N., and S. Fukunaga;Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback: Results of the Timing Rule Simulations;;;;;RFC 4586;DOI 10.17487/RFC4586;July;https://www.rfc-editor.org/info/rfc4586 | |
| RFC4587;;Even, R.;RTP Payload Format for H.261 Video Streams;;;;;RFC 4587;DOI 10.17487/RFC4587;August;https://www.rfc-editor.org/info/rfc4587 | |
| RFC4588;;Rey, J., Leon, D., Miyazaki, A., Varsa, V., and R. Hakenberg;RTP Retransmission Payload Format;;;;;RFC 4588;DOI 10.17487/RFC4588;July;https://www.rfc-editor.org/info/rfc4588 | |
| RFC4589;;Schulzrinne, H. and H. Tschofenig;Location Types Registry;;;;;RFC 4589;DOI 10.17487/RFC4589;July;https://www.rfc-editor.org/info/rfc4589 | |
| RFC4590;RFC5090;Sterman, B., Sadolevsky, D., Schwartz, D., Williams, D., and W. Beck;RADIUS Extension for Digest Authentication;;;;;RFC 4590;DOI 10.17487/RFC4590;July;https://www.rfc-editor.org/info/rfc4590 | |
| RFC4591;;Townsley, M., Wilkie, G., Booth, S., Bryant, S., and J. Lau;Frame Relay over Layer 2 Tunneling Protocol Version 3 (L2TPv3);;;;;RFC 4591;DOI 10.17487/RFC4591;August;https://www.rfc-editor.org/info/rfc4591 | |
| RFC4592;;Lewis, E.;The Role of Wildcards in the Domain Name System;;;;;RFC 4592;DOI 10.17487/RFC4592;July;https://www.rfc-editor.org/info/rfc4592 | |
| RFC4593;;Barbir, A., Murphy, S., and Y. Yang;Generic Threats to Routing Protocols;;;;;RFC 4593;DOI 10.17487/RFC4593;October;https://www.rfc-editor.org/info/rfc4593 | |
| RFC4594;;Babiarz, J., Chan, K., and F. Baker;Configuration Guidelines for DiffServ Service Classes;;;;;RFC 4594;DOI 10.17487/RFC4594;August;https://www.rfc-editor.org/info/rfc4594 | |
| RFC4595;;Maino, F. and D. Black;Use of IKEv2 in the Fibre Channel Security Association Management Protocol;;;;;RFC 4595;DOI 10.17487/RFC4595;July;https://www.rfc-editor.org/info/rfc4595 | |
| RFC4596;;Rosenberg, J. and P. Kyzivat;Guidelines for Usage of the Session Initiation Protocol (SIP) Caller Preferences Extension;;;;;RFC 4596;DOI 10.17487/RFC4596;July;https://www.rfc-editor.org/info/rfc4596 | |
| RFC4597;;Even, R. and N. Ismail;Conferencing Scenarios;;;;;RFC 4597;DOI 10.17487/RFC4597;August;https://www.rfc-editor.org/info/rfc4597 | |
| RFC4598;;Link, B.;Real-time Transport Protocol (RTP) Payload Format for Enhanced AC-3 (E-AC-3) Audio;;;;;RFC 4598;DOI 10.17487/RFC4598;July;https://www.rfc-editor.org/info/rfc4598 | |
| RFC4601;RFC7761;Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas;Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised);;;;;RFC 4601;DOI 10.17487/RFC4601;August;https://www.rfc-editor.org/info/rfc4601 | |
| RFC4602;;Pusateri, T.;Protocol Independent Multicast - Sparse Mode (PIM-SM) IETF Proposed Standard Requirements Analysis;;;;;RFC 4602;DOI 10.17487/RFC4602;August;https://www.rfc-editor.org/info/rfc4602 | |
| RFC4603;;Zorn, G., Weber, G., and R. Foltak;Additional Values for the NAS-Port-Type Attribute;;;;;RFC 4603;DOI 10.17487/RFC4603;July;https://www.rfc-editor.org/info/rfc4603 | |
| RFC4604;;Holbrook, H., Cain, B., and B. Haberman;Using Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Protocol Version 2 (MLDv2) for Source-Specific Multicast;;;;;RFC 4604;DOI 10.17487/RFC4604;August;https://www.rfc-editor.org/info/rfc4604 | |
| RFC4605;;Fenner, B., He, H., Haberman, B., and H. Sandick;Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding ("IGMP/MLD Proxying");;;;;RFC 4605;DOI 10.17487/RFC4605;August;https://www.rfc-editor.org/info/rfc4605 | |
| RFC4606;;Mannie, E. and D. Papadimitriou;Generalized Multi-Protocol Label Switching (GMPLS) Extensions for Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) Control;;;;;RFC 4606;DOI 10.17487/RFC4606;August;https://www.rfc-editor.org/info/rfc4606 | |
| RFC4607;;Holbrook, H. and B. Cain;Source-Specific Multicast for IP;;;;;RFC 4607;DOI 10.17487/RFC4607;August;https://www.rfc-editor.org/info/rfc4607 | |
| RFC4608;;Meyer, D., Rockell, R., and G. Shepherd;Source-Specific Protocol Independent Multicast in 232/8;;;BCP 120;;RFC 4608;DOI 10.17487/RFC4608;August;https://www.rfc-editor.org/info/rfc4608 | |
| RFC4609;;Savola, P., Lehtonen, R., and D. Meyer;Protocol Independent Multicast - Sparse Mode (PIM-SM) Multicast Routing Security Issues and Enhancements;;;;;RFC 4609;DOI 10.17487/RFC4609;October;https://www.rfc-editor.org/info/rfc4609 | |
| RFC4610;;Farinacci, D. and Y. Cai;Anycast-RP Using Protocol Independent Multicast (PIM);;;;;RFC 4610;DOI 10.17487/RFC4610;August;https://www.rfc-editor.org/info/rfc4610 | |
| RFC4611;;McBride, M., Meylor, J., and D. Meyer;Multicast Source Discovery Protocol (MSDP) Deployment Scenarios;;;BCP 121;;RFC 4611;DOI 10.17487/RFC4611;August;https://www.rfc-editor.org/info/rfc4611 | |
| RFC4612;;Jones, P. and H. Tamura;Real-Time Facsimile (T.38) - audio/t38 MIME Sub-type Registration;;;;;RFC 4612;DOI 10.17487/RFC4612;August;https://www.rfc-editor.org/info/rfc4612 | |
| RFC4613;;Frojdh, P., Lindgren, U., and M. Westerlund;Media Type Registrations for Downloadable Sounds for Musical Instrument Digital Interface (MIDI);;;;;RFC 4613;DOI 10.17487/RFC4613;September;https://www.rfc-editor.org/info/rfc4613 | |
| RFC4614;RFC7414;Duke, M., Braden, R., Eddy, W., and E. Blanton;A Roadmap for Transmission Control Protocol (TCP) Specification Documents;;;;;RFC 4614;DOI 10.17487/RFC4614;September;https://www.rfc-editor.org/info/rfc4614 | |
| RFC4615;;Song, J., Poovendran, R., Lee, J., and T. Iwata;The Advanced Encryption Standard-Cipher-based Message Authentication Code-Pseudo-Random Function-128 (AES-CMAC-PRF-128) Algorithm for the Internet Key Exchange Protocol (IKE);;;;;RFC 4615;DOI 10.17487/RFC4615;August;https://www.rfc-editor.org/info/rfc4615 | |
| RFC4616;;Zeilenga, K., Ed.;The PLAIN Simple Authentication and Security Layer (SASL) Mechanism;;;;;RFC 4616;DOI 10.17487/RFC4616;August;https://www.rfc-editor.org/info/rfc4616 | |
| RFC4617;;Kornijenko, J.;A Uniform Resource Name (URN) Formal Namespace for the Latvian National Government Integration Project;;;;;RFC 4617;DOI 10.17487/RFC4617;August;https://www.rfc-editor.org/info/rfc4617 | |
| RFC4618;;Martini, L., Rosen, E., Heron, G., and A. Malis;Encapsulation Methods for Transport of PPP/High-Level Data Link Control (HDLC) over MPLS Networks;;;;;RFC 4618;DOI 10.17487/RFC4618;September;https://www.rfc-editor.org/info/rfc4618 | |
| RFC4619;;Martini, L., Ed., Kawa, C., Ed., and A. Malis, Ed.;Encapsulation Methods for Transport of Frame Relay over Multiprotocol Label Switching (MPLS) Networks;;;;;RFC 4619;DOI 10.17487/RFC4619;September;https://www.rfc-editor.org/info/rfc4619 | |
| RFC4620;;Crawford, M. and B. Haberman, Ed.;IPv6 Node Information Queries;;;;;RFC 4620;DOI 10.17487/RFC4620;August;https://www.rfc-editor.org/info/rfc4620 | |
| RFC4621;;Kivinen, T. and H. Tschofenig;Design of the IKEv2 Mobility and Multihoming (MOBIKE) Protocol;;;;;RFC 4621;DOI 10.17487/RFC4621;August;https://www.rfc-editor.org/info/rfc4621 | |
| RFC4622;RFC5122;Saint-Andre, P.;Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP);;;;;RFC 4622;DOI 10.17487/RFC4622;July;https://www.rfc-editor.org/info/rfc4622 | |
| RFC4623;;Malis, A. and M. Townsley;Pseudowire Emulation Edge-to-Edge (PWE3) Fragmentation and Reassembly;;;;;RFC 4623;DOI 10.17487/RFC4623;August;https://www.rfc-editor.org/info/rfc4623 | |
| RFC4624;;Fenner, B. and D. Thaler;Multicast Source Discovery Protocol (MSDP) MIB;;;;;RFC 4624;DOI 10.17487/RFC4624;October;https://www.rfc-editor.org/info/rfc4624 | |
| RFC4625;;DeSanti, C., McCloghrie, K., Kode, S., and S. Gai;Fibre Channel Routing Information MIB;;;;;RFC 4625;DOI 10.17487/RFC4625;September;https://www.rfc-editor.org/info/rfc4625 | |
| RFC4626;;DeSanti, C., Gaonkar, V., McCloghrie, K., and S. Gai;MIB for Fibre Channel's Fabric Shortest Path First (FSPF) Protocol;;;;;RFC 4626;DOI 10.17487/RFC4626;September;https://www.rfc-editor.org/info/rfc4626 | |
| RFC4627;RFC7159;Crockford, D.;The application/json Media Type for JavaScript Object Notation (JSON);;;;;RFC 4627;DOI 10.17487/RFC4627;July;https://www.rfc-editor.org/info/rfc4627 | |
| RFC4628;;Even, R.;RTP Payload Format for H.263 Moving RFC 2190 to Historic Status;;;;;RFC 4628;DOI 10.17487/RFC4628;January;https://www.rfc-editor.org/info/rfc4628 | |
| RFC4629;;Ott, J., Bormann, C., Sullivan, G., Wenger, S., and R. Even, Ed.;RTP Payload Format for ITU-T Rec. H.263 Video;;;;;RFC 4629;DOI 10.17487/RFC4629;January;https://www.rfc-editor.org/info/rfc4629 | |
| RFC4630;RFC5280;Housley, R. and S. Santesson;Update to DirectoryString Processing in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile;;;;;RFC 4630;DOI 10.17487/RFC4630;August;https://www.rfc-editor.org/info/rfc4630 | |
| RFC4631;;Dubuc, M., Nadeau, T., Lang, J., McGinnis, E., and A. Farrel;Link Management Protocol (LMP) Management Information Base (MIB);;;;;RFC 4631;DOI 10.17487/RFC4631;September;https://www.rfc-editor.org/info/rfc4631 | |
| RFC4632;;Fuller, V. and T. Li;Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan;;;BCP 122;;RFC 4632;DOI 10.17487/RFC4632;August;https://www.rfc-editor.org/info/rfc4632 | |
| RFC4633;;Hartman, S.;Experiment in Long-Term Suspensions From Internet Engineering Task Force (IETF) Mailing Lists;;;;;RFC 4633;DOI 10.17487/RFC4633;August;https://www.rfc-editor.org/info/rfc4633 | |
| RFC4634;RFC6234;Eastlake 3rd, D. and T. Hansen;US Secure Hash Algorithms (SHA and HMAC-SHA);;;;;RFC 4634;DOI 10.17487/RFC4634;July;https://www.rfc-editor.org/info/rfc4634 | |
| RFC4635;;Eastlake 3rd, D.;HMAC SHA (Hashed Message Authentication Code, Secure Hash Algorithm) TSIG Algorithm Identifiers;;;;;RFC 4635;DOI 10.17487/RFC4635;August;https://www.rfc-editor.org/info/rfc4635 | |
| RFC4636;;Perkins, C.;Foreign Agent Error Extension for Mobile IPv4;;;;;RFC 4636;DOI 10.17487/RFC4636;October;https://www.rfc-editor.org/info/rfc4636 | |
| RFC4638;;Arberg, P., Kourkouzelis, D., Duckett, M., Anschutz, T., and J. Moisand;Accommodating a Maximum Transit Unit/Maximum Receive Unit (MTU/MRU) Greater Than 1492 in the Point-to-Point Protocol over Ethernet (PPPoE);;;;;RFC 4638;DOI 10.17487/RFC4638;September;https://www.rfc-editor.org/info/rfc4638 | |
| RFC4639;;Woundy, R. and K. Marez;Cable Device Management Information Base for Data-Over-Cable Service Interface Specification (DOCSIS) Compliant Cable Modems and Cable Modem Termination Systems;;;;;RFC 4639;DOI 10.17487/RFC4639;December;https://www.rfc-editor.org/info/rfc4639 | |
| RFC4640;;Patel, A., Ed., and G. Giaretta, Ed.;Problem Statement for bootstrapping Mobile IPv6 (MIPv6);;;;;RFC 4640;DOI 10.17487/RFC4640;September;https://www.rfc-editor.org/info/rfc4640 | |
| RFC4641;RFC6781;Kolkman, O. and R. Gieben;DNSSEC Operational Practices;;;;;RFC 4641;DOI 10.17487/RFC4641;September;https://www.rfc-editor.org/info/rfc4641 | |
| RFC4642;;Murchison, K., Vinocur, J., and C. Newman;Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP);;;;;RFC 4642;DOI 10.17487/RFC4642;October;https://www.rfc-editor.org/info/rfc4642 | |
| RFC4643;;Vinocur, J. and K. Murchison;Network News Transfer Protocol (NNTP) Extension for Authentication;;;;;RFC 4643;DOI 10.17487/RFC4643;October;https://www.rfc-editor.org/info/rfc4643 | |
| RFC4644;;Vinocur, J. and K. Murchison;Network News Transfer Protocol (NNTP) Extension for Streaming Feeds;;;;;RFC 4644;DOI 10.17487/RFC4644;October;https://www.rfc-editor.org/info/rfc4644 | |
| RFC4645;;Ewell, D.;Initial Language Subtag Registry;;;;;RFC 4645;DOI 10.17487/RFC4645;September;https://www.rfc-editor.org/info/rfc4645 | |
| RFC4646;RFC5646;Phillips, A. and M. Davis;Tags for Identifying Languages;;;;;RFC 4646;DOI 10.17487/RFC4646;September;https://www.rfc-editor.org/info/rfc4646 | |
| RFC4647;;Phillips, A. and M. Davis;Matching of Language Tags;;;BCP 47;;RFC 4647;DOI 10.17487/RFC4647;September;https://www.rfc-editor.org/info/rfc4647 | |
| RFC4648;;Josefsson, S.;The Base16, Base32, and Base64 Data Encodings;;;;;RFC 4648;DOI 10.17487/RFC4648;October;https://www.rfc-editor.org/info/rfc4648 | |
| RFC4649;;Volz, B.;Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Remote-ID Option;;;;;RFC 4649;DOI 10.17487/RFC4649;August;https://www.rfc-editor.org/info/rfc4649 | |
| RFC4650;;Euchner, M.;HMAC-Authenticated Diffie-Hellman for Multimedia Internet KEYing (MIKEY);;;;;RFC 4650;DOI 10.17487/RFC4650;September;https://www.rfc-editor.org/info/rfc4650 | |
| RFC4651;;Vogt, C. and J. Arkko;A Taxonomy and Analysis of Enhancements to Mobile IPv6 Route Optimization;;;;;RFC 4651;DOI 10.17487/RFC4651;February;https://www.rfc-editor.org/info/rfc4651 | |
| RFC4652;;Papadimitriou, D., Ed., Ong, L., Sadler, J., Shew, S., and D. Ward;Evaluation of Existing Routing Protocols against Automatic Switched Optical Network (ASON) Routing Requirements;;;;;RFC 4652;DOI 10.17487/RFC4652;October;https://www.rfc-editor.org/info/rfc4652 | |
| RFC4653;;Bhandarkar, S., Reddy, A., Allman, M., and E. Blanton;Improving the Robustness of TCP to Non-Congestion Events;;;;;RFC 4653;DOI 10.17487/RFC4653;August;https://www.rfc-editor.org/info/rfc4653 | |
| RFC4654;;Widmer, J. and M. Handley;TCP-Friendly Multicast Congestion Control (TFMCC): Protocol Specification;;;;;RFC 4654;DOI 10.17487/RFC4654;August;https://www.rfc-editor.org/info/rfc4654 | |
| RFC4655;;Farrel, A., Vasseur, J.-P., and J. Ash;A Path Computation Element (PCE)-Based Architecture;;;;;RFC 4655;DOI 10.17487/RFC4655;August;https://www.rfc-editor.org/info/rfc4655 | |
| RFC4656;;Shalunov, S., Teitelbaum, B., Karp, A., Boote, J., and M. Zekauskas;A One-way Active Measurement Protocol (OWAMP);;;;;RFC 4656;DOI 10.17487/RFC4656;September;https://www.rfc-editor.org/info/rfc4656 | |
| RFC4657;;Ash, J., Ed., and J. Le Roux, Ed.;Path Computation Element (PCE) Communication Protocol Generic Requirements;;;;;RFC 4657;DOI 10.17487/RFC4657;September;https://www.rfc-editor.org/info/rfc4657 | |
| RFC4659;;De Clercq, J., Ooms, D., Carugi, M., and F. Le Faucheur;BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN;;;;;RFC 4659;DOI 10.17487/RFC4659;September;https://www.rfc-editor.org/info/rfc4659 | |
| RFC4660;;Khartabil, H., Leppanen, E., Lonnfors, M., and J. Costa-Requena;Functional Description of Event Notification Filtering;;;;;RFC 4660;DOI 10.17487/RFC4660;September;https://www.rfc-editor.org/info/rfc4660 | |
| RFC4661;;Khartabil, H., Leppanen, E., Lonnfors, M., and J. Costa-Requena;An Extensible Markup Language (XML)-Based Format for Event Notification Filtering;;;;;RFC 4661;DOI 10.17487/RFC4661;September;https://www.rfc-editor.org/info/rfc4661 | |
| RFC4662;;Roach, A., Campbell, B., and J. Rosenberg;A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists;;;;;RFC 4662;DOI 10.17487/RFC4662;August;https://www.rfc-editor.org/info/rfc4662 | |
| RFC4663;;Harrington, D.;Transferring MIB Work from IETF Bridge MIB WG to IEEE 802.1 WG;;;;;RFC 4663;DOI 10.17487/RFC4663;September;https://www.rfc-editor.org/info/rfc4663 | |
| RFC4664;;Andersson, L., Ed., and E. Rosen, Ed.;Framework for Layer 2 Virtual Private Networks (L2VPNs);;;;;RFC 4664;DOI 10.17487/RFC4664;September;https://www.rfc-editor.org/info/rfc4664 | |
| RFC4665;;Augustyn, W., Ed., and Y. Serbest, Ed.;Service Requirements for Layer 2 Provider-Provisioned Virtual Private Networks;;;;;RFC 4665;DOI 10.17487/RFC4665;September;https://www.rfc-editor.org/info/rfc4665 | |
| RFC4666;;Morneault, K., Ed., and J. Pastor-Balbas, Ed.;Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA);;;;;RFC 4666;DOI 10.17487/RFC4666;September;https://www.rfc-editor.org/info/rfc4666 | |
| RFC4667;;Luo, W.;Layer 2 Virtual Private Network (L2VPN) Extensions for Layer 2 Tunneling Protocol (L2TP);;;;;RFC 4667;DOI 10.17487/RFC4667;September;https://www.rfc-editor.org/info/rfc4667 | |
| RFC4668;;Nelson, D.;RADIUS Authentication Client MIB for IPv6;;;;;RFC 4668;DOI 10.17487/RFC4668;August;https://www.rfc-editor.org/info/rfc4668 | |
| RFC4669;;Nelson, D.;RADIUS Authentication Server MIB for IPv6;;;;;RFC 4669;DOI 10.17487/RFC4669;August;https://www.rfc-editor.org/info/rfc4669 | |
| RFC4670;;Nelson, D.;RADIUS Accounting Client MIB for IPv6;;;;;RFC 4670;DOI 10.17487/RFC4670;August;https://www.rfc-editor.org/info/rfc4670 | |
| RFC4671;;Nelson, D.;RADIUS Accounting Server MIB for IPv6;;;;;RFC 4671;DOI 10.17487/RFC4671;August;https://www.rfc-editor.org/info/rfc4671 | |
| RFC4672;;De Cnodder, S., Jonnala, N., and M. Chiba;RADIUS Dynamic Authorization Client MIB;;;;;RFC 4672;DOI 10.17487/RFC4672;September;https://www.rfc-editor.org/info/rfc4672 | |
| RFC4673;;De Cnodder, S., Jonnala, N., and M. Chiba;RADIUS Dynamic Authorization Server MIB;;;;;RFC 4673;DOI 10.17487/RFC4673;September;https://www.rfc-editor.org/info/rfc4673 | |
| RFC4674;;Le Roux, J., Ed.;Requirements for Path Computation Element (PCE) Discovery;;;;;RFC 4674;DOI 10.17487/RFC4674;October;https://www.rfc-editor.org/info/rfc4674 | |
| RFC4675;;Congdon, P., Sanchez, M., and B. Aboba;RADIUS Attributes for Virtual LAN and Priority Support;;;;;RFC 4675;DOI 10.17487/RFC4675;September;https://www.rfc-editor.org/info/rfc4675 | |
| RFC4676;RFC4776;Schulzrinne, H.;Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information;;;;;RFC 4676;DOI 10.17487/RFC4676;October;https://www.rfc-editor.org/info/rfc4676 | |
| RFC4677;RFC6722;Hoffman, P. and S. Harris;The Tao of IETF - A Novice's Guide to the Internet Engineering Task Force;;;;;RFC 4677;DOI 10.17487/RFC4677;September;https://www.rfc-editor.org/info/rfc4677 | |
| RFC4678;;Bivens, A.;Server/Application State Protocol v1;;;;;RFC 4678;DOI 10.17487/RFC4678;September;https://www.rfc-editor.org/info/rfc4678 | |
| RFC4679;;Mammoliti, V., Zorn, G., Arberg, P., and R. Rennison;DSL Forum Vendor-Specific RADIUS Attributes;;;;;RFC 4679;DOI 10.17487/RFC4679;September;https://www.rfc-editor.org/info/rfc4679 | |
| RFC4680;;Santesson, S.;TLS Handshake Message for Supplemental Data;;;;;RFC 4680;DOI 10.17487/RFC4680;October;https://www.rfc-editor.org/info/rfc4680 | |
| RFC4681;;Santesson, S., Medvinsky, A., and J. Ball;TLS User Mapping Extension;;;;;RFC 4681;DOI 10.17487/RFC4681;October;https://www.rfc-editor.org/info/rfc4681 | |
| RFC4682;;Nechamkin, E. and J-F. Mule;Multimedia Terminal Adapter (MTA) Management Information Base for PacketCable- and IPCablecom-Compliant Devices;;;;;RFC 4682;DOI 10.17487/RFC4682;December;https://www.rfc-editor.org/info/rfc4682 | |
| RFC4683;;Park, J., Lee, J., . Lee, H., Park, S., and T. Polk;Internet X.509 Public Key Infrastructure Subject Identification Method (SIM);;;;;RFC 4683;DOI 10.17487/RFC4683;October;https://www.rfc-editor.org/info/rfc4683 | |
| RFC4684;;Marques, P., Bonica, R., Fang, L., Martini, L., Raszuk, R., Patel, K., and J. Guichard;Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs);;;;;RFC 4684;DOI 10.17487/RFC4684;November;https://www.rfc-editor.org/info/rfc4684 | |
| RFC4685;;Snell, J.;Atom Threading Extensions;;;;;RFC 4685;DOI 10.17487/RFC4685;September;https://www.rfc-editor.org/info/rfc4685 | |
| RFC4686;;Fenton, J.;Analysis of Threats Motivating DomainKeys Identified Mail (DKIM);;;;;RFC 4686;DOI 10.17487/RFC4686;September;https://www.rfc-editor.org/info/rfc4686 | |
| RFC4687;;Yasukawa, S., Farrel, A., King, D., and T. Nadeau;Operations and Management (OAM) Requirements for Point-to-Multipoint MPLS Networks;;;;;RFC 4687;DOI 10.17487/RFC4687;September;https://www.rfc-editor.org/info/rfc4687 | |
| RFC4688;;Rushing, S.;A Uniform Resource Name (URN) Namespace for Aerospace and Defence Industries Association of Europe (ASD) Specification 1000D;;;;;RFC 4688;DOI 10.17487/RFC4688;October;https://www.rfc-editor.org/info/rfc4688 | |
| RFC4689;;Poretsky, S., Perser, J., Erramilli, S., and S. Khurana;Terminology for Benchmarking Network-layer Traffic Control Mechanisms;;;;;RFC 4689;DOI 10.17487/RFC4689;October;https://www.rfc-editor.org/info/rfc4689 | |
| RFC4690;;Klensin, J., Faltstrom, P., Karp, C., and IAB;Review and Recommendations for Internationalized Domain Names (IDNs);;;;;RFC 4690;DOI 10.17487/RFC4690;September;https://www.rfc-editor.org/info/rfc4690 | |
| RFC4691;;Andersson, L., Ed.;Guidelines for Acting as an IETF Liaison to Another Organization;;;;;RFC 4691;DOI 10.17487/RFC4691;October;https://www.rfc-editor.org/info/rfc4691 | |
| RFC4692;;Huston, G.;Considerations on the IPv6 Host Density Metric;;;;;RFC 4692;DOI 10.17487/RFC4692;October;https://www.rfc-editor.org/info/rfc4692 | |
| RFC4693;RFC6393;Alvestrand, H.;IETF Operational Notes;;;;;RFC 4693;DOI 10.17487/RFC4693;October;https://www.rfc-editor.org/info/rfc4693 | |
| RFC4694;;Yu, J.;Number Portability Parameters for the "tel" URI;;;;;RFC 4694;DOI 10.17487/RFC4694;October;https://www.rfc-editor.org/info/rfc4694 | |
| RFC4695;RFC6295;Lazzaro, J. and J. Wawrzynek;RTP Payload Format for MIDI;;;;;RFC 4695;DOI 10.17487/RFC4695;November;https://www.rfc-editor.org/info/rfc4695 | |
| RFC4696;;Lazzaro, J. and J. Wawrzynek;An Implementation Guide for RTP MIDI;;;;;RFC 4696;DOI 10.17487/RFC4696;November;https://www.rfc-editor.org/info/rfc4696 | |
| RFC4697;;Larson, M. and P. Barber;Observed DNS Resolution Misbehavior;;;BCP 123;;RFC 4697;DOI 10.17487/RFC4697;October;https://www.rfc-editor.org/info/rfc4697 | |
| RFC4698;;Gunduz, E., Newton, A., and S. Kerr;IRIS: An Address Registry (areg) Type for the Internet Registry Information Service;;;;;RFC 4698;DOI 10.17487/RFC4698;October;https://www.rfc-editor.org/info/rfc4698 | |
| RFC4701;;Stapp, M., Lemon, T., and A. Gustafsson;A DNS Resource Record (RR) for Encoding Dynamic Host Configuration Protocol (DHCP) Information (DHCID RR);;;;;RFC 4701;DOI 10.17487/RFC4701;October;https://www.rfc-editor.org/info/rfc4701 | |
| RFC4702;;Stapp, M., Volz, B., and Y. Rekhter;The Dynamic Host Configuration Protocol (DHCP) Client Fully Qualified Domain Name (FQDN) Option;;;;;RFC 4702;DOI 10.17487/RFC4702;October;https://www.rfc-editor.org/info/rfc4702 | |
| RFC4703;;Stapp, M. and B. Volz;Resolution of Fully Qualified Domain Name (FQDN) Conflicts among Dynamic Host Configuration Protocol (DHCP) Clients;;;;;RFC 4703;DOI 10.17487/RFC4703;October;https://www.rfc-editor.org/info/rfc4703 | |
| RFC4704;;Volz, B.;The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option;;;;;RFC 4704;DOI 10.17487/RFC4704;October;https://www.rfc-editor.org/info/rfc4704 | |
| RFC4705;;Housley, R. and A. Corry;GigaBeam High-Speed Radio Link Encryption;;;;;RFC 4705;DOI 10.17487/RFC4705;October;https://www.rfc-editor.org/info/rfc4705 | |
| RFC4706;;Morgenstern, M., Dodge, M., Baillie, S., and U. Bonollo;Definitions of Managed Objects for Asymmetric Digital Subscriber Line 2 (ADSL2);;;;;RFC 4706;DOI 10.17487/RFC4706;November;https://www.rfc-editor.org/info/rfc4706 | |
| RFC4707;;Grau, P., Heinau, V., Schlichting, H., and R. Schuettler;Netnews Administration System (NAS);;;;;RFC 4707;DOI 10.17487/RFC4707;October;https://www.rfc-editor.org/info/rfc4707 | |
| RFC4708;;Miller, A.;CellML Media Type;;;;;RFC 4708;DOI 10.17487/RFC4708;October;https://www.rfc-editor.org/info/rfc4708 | |
| RFC4709;;Reschke, J.;Mounting Web Distributed Authoring and Versioning (WebDAV) Servers;;;;;RFC 4709;DOI 10.17487/RFC4709;October;https://www.rfc-editor.org/info/rfc4709 | |
| RFC4710;;Siddiqui, A., Romascanu, D., and E. Golovinsky;Real-time Application Quality-of-Service Monitoring (RAQMON) Framework;;;;;RFC 4710;DOI 10.17487/RFC4710;October;https://www.rfc-editor.org/info/rfc4710 | |
| RFC4711;;Siddiqui, A., Romascanu, D., and E. Golovinsky;Real-time Application Quality-of-Service Monitoring (RAQMON) MIB;;;;;RFC 4711;DOI 10.17487/RFC4711;October;https://www.rfc-editor.org/info/rfc4711 | |
| RFC4712;;Siddiqui, A., Romascanu, D., Golovinsky, E., Rahman, M., and Y. Kim;Transport Mappings for Real-time Application Quality-of-Service Monitoring (RAQMON) Protocol Data Unit (PDU);;;;;RFC 4712;DOI 10.17487/RFC4712;October;https://www.rfc-editor.org/info/rfc4712 | |
| RFC4713;;Lee, X., Mao, W., Chen, E., Hsu, N., and J. Klensin;Registration and Administration Recommendations for Chinese Domain Names;;;;;RFC 4713;DOI 10.17487/RFC4713;October;https://www.rfc-editor.org/info/rfc4713 | |
| RFC4714;;Mankin, A. and S. Hayes;Requirements for IETF Technical Publication Service;;;;;RFC 4714;DOI 10.17487/RFC4714;October;https://www.rfc-editor.org/info/rfc4714 | |
| RFC4715;;Munakata, M., Schubert, S., and T. Ohba;The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI;;;;;RFC 4715;DOI 10.17487/RFC4715;November;https://www.rfc-editor.org/info/rfc4715 | |
| RFC4716;;Galbraith, J. and R. Thayer;The Secure Shell (SSH) Public Key File Format;;;;;RFC 4716;DOI 10.17487/RFC4716;November;https://www.rfc-editor.org/info/rfc4716 | |
| RFC4717;;Martini, L., Jayakumar, J., Bocci, M., El-Aawar, N., Brayley, J., and G. Koleyni;Encapsulation Methods for Transport of Asynchronous Transfer Mode (ATM) over MPLS Networks;;;;;RFC 4717;DOI 10.17487/RFC4717;December;https://www.rfc-editor.org/info/rfc4717 | |
| RFC4718;RFC5996;Eronen, P. and P. Hoffman;IKEv2 Clarifications and Implementation Guidelines;;;;;RFC 4718;DOI 10.17487/RFC4718;October;https://www.rfc-editor.org/info/rfc4718 | |
| RFC4719;;Aggarwal, R., Ed., Townsley, M., Ed., and M. Dos Santos, Ed.;Transport of Ethernet Frames over Layer 2 Tunneling Protocol Version 3 (L2TPv3);;;;;RFC 4719;DOI 10.17487/RFC4719;November;https://www.rfc-editor.org/info/rfc4719 | |
| RFC4720;;Malis, A., Allan, D., and N. Del Regno;Pseudowire Emulation Edge-to-Edge (PWE3) Frame Check Sequence Retention;;;;;RFC 4720;DOI 10.17487/RFC4720;November;https://www.rfc-editor.org/info/rfc4720 | |
| RFC4721;;Perkins, C., Calhoun, P., and J. Bharatia;Mobile IPv4 Challenge/Response Extensions (Revised);;;;;RFC 4721;DOI 10.17487/RFC4721;January;https://www.rfc-editor.org/info/rfc4721 | |
| RFC4722;RFC5022;Van Dyke, J., Burger, E., Ed., and A. Spitzer;Media Server Control Markup Language (MSCML) and Protocol;;;;;RFC 4722;DOI 10.17487/RFC4722;November;https://www.rfc-editor.org/info/rfc4722 | |
| RFC4723;;Kosonen, T. and T. White;Registration of Media Type audio/mobile-xmf;;;;;RFC 4723;DOI 10.17487/RFC4723;December;https://www.rfc-editor.org/info/rfc4723 | |
| RFC4724;;Sangli, S., Chen, E., Fernando, R., Scudder, J., and Y. Rekhter;Graceful Restart Mechanism for BGP;;;;;RFC 4724;DOI 10.17487/RFC4724;January;https://www.rfc-editor.org/info/rfc4724 | |
| RFC4725;;Mayrhofer, A. and B. Hoeneisen;ENUM Validation Architecture;;;;;RFC 4725;DOI 10.17487/RFC4725;November;https://www.rfc-editor.org/info/rfc4725 | |
| RFC4726;;Farrel, A., Vasseur, J.-P., and A. Ayyangar;A Framework for Inter-Domain Multiprotocol Label Switching Traffic Engineering;;;;;RFC 4726;DOI 10.17487/RFC4726;November;https://www.rfc-editor.org/info/rfc4726 | |
| RFC4727;;Fenner, B.;Experimental Values In IPv4, IPv6, ICMPv4, ICMPv6, UDP, and TCP Headers;;;;;RFC 4727;DOI 10.17487/RFC4727;November;https://www.rfc-editor.org/info/rfc4727 | |
| RFC4728;;Johnson, D., Hu, Y., and D. Maltz;The Dynamic Source Routing Protocol (DSR) for Mobile Ad Hoc Networks for IPv4;;;;;RFC 4728;DOI 10.17487/RFC4728;February;https://www.rfc-editor.org/info/rfc4728 | |
| RFC4729;;Abel, M.;A Uniform Resource Name (URN) Namespace for the Near Field Communication (NFC) Forum;;;;;RFC 4729;DOI 10.17487/RFC4729;November;https://www.rfc-editor.org/info/rfc4729 | |
| RFC4730;;Burger, E. and M. Dolly;A Session Initiation Protocol (SIP) Event Package for Key Press Stimulus (KPML);;;;;RFC 4730;DOI 10.17487/RFC4730;November;https://www.rfc-editor.org/info/rfc4730 | |
| RFC4731;;Melnikov, A. and D. Cridland;IMAP4 Extension to SEARCH Command for Controlling What Kind of Information Is Returned;;;;;RFC 4731;DOI 10.17487/RFC4731;November;https://www.rfc-editor.org/info/rfc4731 | |
| RFC4732;;Handley, M., Ed., Rescorla, E., Ed., and IAB;Internet Denial-of-Service Considerations;;;;;RFC 4732;DOI 10.17487/RFC4732;December;https://www.rfc-editor.org/info/rfc4732 | |
| RFC4733;;Schulzrinne, H. and T. Taylor;RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals;;;;;RFC 4733;DOI 10.17487/RFC4733;December;https://www.rfc-editor.org/info/rfc4733 | |
| RFC4734;;Schulzrinne, H. and T. Taylor;Definition of Events for Modem, Fax, and Text Telephony Signals;;;;;RFC 4734;DOI 10.17487/RFC4734;December;https://www.rfc-editor.org/info/rfc4734 | |
| RFC4735;;Taylor, T.;Example Media Types for Use in Documentation;;;;;RFC 4735;DOI 10.17487/RFC4735;October;https://www.rfc-editor.org/info/rfc4735 | |
| RFC4736;;Vasseur, JP., Ed., Ikejiri, Y., and R. Zhang;Reoptimization of Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Loosely Routed Label Switched Path (LSP);;;;;RFC 4736;DOI 10.17487/RFC4736;November;https://www.rfc-editor.org/info/rfc4736 | |
| RFC4737;;Morton, A., Ciavattone, L., Ramachandran, G., Shalunov, S., and J. Perser;Packet Reordering Metrics;;;;;RFC 4737;DOI 10.17487/RFC4737;November;https://www.rfc-editor.org/info/rfc4737 | |
| RFC4738;;Ignjatic, D., Dondeti, L., Audet, F., and P. Lin;MIKEY-RSA-R: An Additional Mode of Key Distribution in Multimedia Internet KEYing (MIKEY);;;;;RFC 4738;DOI 10.17487/RFC4738;November;https://www.rfc-editor.org/info/rfc4738 | |
| RFC4739;;Eronen, P. and J. Korhonen;Multiple Authentication Exchanges in the Internet Key Exchange (IKEv2) Protocol;;;;;RFC 4739;DOI 10.17487/RFC4739;November;https://www.rfc-editor.org/info/rfc4739 | |
| RFC4740;;Garcia-Martin, M., Ed., Belinchon, M., Pallares-Lopez, M., Canales-Valenzuela, C., and K. Tammi;Diameter Session Initiation Protocol (SIP) Application;;;;;RFC 4740;DOI 10.17487/RFC4740;November;https://www.rfc-editor.org/info/rfc4740 | |
| RFC4741;RFC6241;Enns, R., Ed.;NETCONF Configuration Protocol;;;;;RFC 4741;DOI 10.17487/RFC4741;December;https://www.rfc-editor.org/info/rfc4741 | |
| RFC4742;RFC6242;Wasserman, M. and T. Goddard;Using the NETCONF Configuration Protocol over Secure SHell (SSH);;;;;RFC 4742;DOI 10.17487/RFC4742;December;https://www.rfc-editor.org/info/rfc4742 | |
| RFC4743;;Goddard, T.;Using NETCONF over the Simple Object Access Protocol (SOAP);;;;;RFC 4743;DOI 10.17487/RFC4743;December;https://www.rfc-editor.org/info/rfc4743 | |
| RFC4744;;Lear, E. and K. Crozier;Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP);;;;;RFC 4744;DOI 10.17487/RFC4744;December;https://www.rfc-editor.org/info/rfc4744 | |
| RFC4745;;Schulzrinne, H., Tschofenig, H., Morris, J., Cuellar, J., Polk, J., and J. Rosenberg;Common Policy: A Document Format for Expressing Privacy Preferences;;;;;RFC 4745;DOI 10.17487/RFC4745;February;https://www.rfc-editor.org/info/rfc4745 | |
| RFC4746;;Clancy, T. and W. Arbaugh;Extensible Authentication Protocol (EAP) Password Authenticated Exchange;;;;;RFC 4746;DOI 10.17487/RFC4746;November;https://www.rfc-editor.org/info/rfc4746 | |
| RFC4747;;Kipp, S., Ramkumar, G., and K. McCloghrie;The Virtual Fabrics MIB;;;;;RFC 4747;DOI 10.17487/RFC4747;November;https://www.rfc-editor.org/info/rfc4747 | |
| RFC4748;RFC5378;Bradner, S., Ed.;RFC 3978 Update to Recognize the IETF Trust;;;;;RFC 4748;DOI 10.17487/RFC4748;October;https://www.rfc-editor.org/info/rfc4748 | |
| RFC4749;;Sollaud, A.;RTP Payload Format for the G.729.1 Audio Codec;;;;;RFC 4749;DOI 10.17487/RFC4749;October;https://www.rfc-editor.org/info/rfc4749 | |
| RFC4750;;Joyal, D., Ed., Galecki, P., Ed., Giacalone, S., Ed., Coltun, R., and F. Baker;OSPF Version 2 Management Information Base;;;;;RFC 4750;DOI 10.17487/RFC4750;December;https://www.rfc-editor.org/info/rfc4750 | |
| RFC4752;;Melnikov, A., Ed.;The Kerberos V5 ("GSSAPI") Simple Authentication and Security Layer (SASL) Mechanism;;;;;RFC 4752;DOI 10.17487/RFC4752;November;https://www.rfc-editor.org/info/rfc4752 | |
| RFC4753;RFC5903;Fu, D. and J. Solinas;ECP Groups For IKE and IKEv2;;;;;RFC 4753;DOI 10.17487/RFC4753;January;https://www.rfc-editor.org/info/rfc4753 | |
| RFC4754;;Fu, D. and J. Solinas;IKE and IKEv2 Authentication Using the Elliptic Curve Digital Signature Algorithm (ECDSA);;;;;RFC 4754;DOI 10.17487/RFC4754;January;https://www.rfc-editor.org/info/rfc4754 | |
| RFC4755;;Kashyap, V.;IP over InfiniBand: Connected Mode;;;;;RFC 4755;DOI 10.17487/RFC4755;December;https://www.rfc-editor.org/info/rfc4755 | |
| RFC4756;RFC5956;Li, A.;Forward Error Correction Grouping Semantics in Session Description Protocol;;;;;RFC 4756;DOI 10.17487/RFC4756;November;https://www.rfc-editor.org/info/rfc4756 | |
| RFC4757;;Jaganathan, K., Zhu, L., and J. Brezak;The RC4-HMAC Kerberos Encryption Types Used by Microsoft Windows;;;;;RFC 4757;DOI 10.17487/RFC4757;December;https://www.rfc-editor.org/info/rfc4757 | |
| RFC4758;;Nystroem, M.;Cryptographic Token Key Initialization Protocol (CT-KIP) Version 1.0 Revision 1;;;;;RFC 4758;DOI 10.17487/RFC4758;November;https://www.rfc-editor.org/info/rfc4758 | |
| RFC4759;;Stastny, R., Shockey, R., and L. Conroy;The ENUM Dip Indicator Parameter for the "tel" URI;;;;;RFC 4759;DOI 10.17487/RFC4759;December;https://www.rfc-editor.org/info/rfc4759 | |
| RFC4760;;Bates, T., Chandra, R., Katz, D., and Y. Rekhter;Multiprotocol Extensions for BGP-4;;;;;RFC 4760;DOI 10.17487/RFC4760;January;https://www.rfc-editor.org/info/rfc4760 | |
| RFC4761;;Kompella, K., Ed., and Y. Rekhter, Ed.;Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling;;;;;RFC 4761;DOI 10.17487/RFC4761;January;https://www.rfc-editor.org/info/rfc4761 | |
| RFC4762;;Lasserre, M., Ed., and V. Kompella, Ed.;Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling;;;;;RFC 4762;DOI 10.17487/RFC4762;January;https://www.rfc-editor.org/info/rfc4762 | |
| RFC4763;;Vanderveen, M. and H. Soliman;Extensible Authentication Protocol Method for Shared-secret Authentication and Key Establishment (EAP-SAKE);;;;;RFC 4763;DOI 10.17487/RFC4763;November;https://www.rfc-editor.org/info/rfc4763 | |
| RFC4764;;Bersani, F. and H. Tschofenig;The EAP-PSK Protocol: A Pre-Shared Key Extensible Authentication Protocol (EAP) Method;;;;;RFC 4764;DOI 10.17487/RFC4764;January;https://www.rfc-editor.org/info/rfc4764 | |
| RFC4765;;Debar, H., Curry, D., and B. Feinstein;The Intrusion Detection Message Exchange Format (IDMEF);;;;;RFC 4765;DOI 10.17487/RFC4765;March;https://www.rfc-editor.org/info/rfc4765 | |
| RFC4766;;Wood, M. and M. Erlinger;Intrusion Detection Message Exchange Requirements;;;;;RFC 4766;DOI 10.17487/RFC4766;March;https://www.rfc-editor.org/info/rfc4766 | |
| RFC4767;;Feinstein, B. and G. Matthews;The Intrusion Detection Exchange Protocol (IDXP);;;;;RFC 4767;DOI 10.17487/RFC4767;March;https://www.rfc-editor.org/info/rfc4767 | |
| RFC4768;;Hartman, S.;Desired Enhancements to Generic Security Services Application Program Interface (GSS-API) Version 3 Naming;;;;;RFC 4768;DOI 10.17487/RFC4768;December;https://www.rfc-editor.org/info/rfc4768 | |
| RFC4769;;Livingood, J. and R. Shockey;IANA Registration for an Enumservice Containing Public Switched Telephone Network (PSTN) Signaling Information;;;;;RFC 4769;DOI 10.17487/RFC4769;November;https://www.rfc-editor.org/info/rfc4769 | |
| RFC4770;RFC6350;Jennings, C. and J. Reschke, Ed.;vCard Extensions for Instant Messaging (IM);;;;;RFC 4770;DOI 10.17487/RFC4770;January;https://www.rfc-editor.org/info/rfc4770 | |
| RFC4771;;Lehtovirta, V., Naslund, M., and K. Norrman;Integrity Transform Carrying Roll-Over Counter for the Secure Real-time Transport Protocol (SRTP);;;;;RFC 4771;DOI 10.17487/RFC4771;January;https://www.rfc-editor.org/info/rfc4771 | |
| RFC4772;;Kelly, S.;Security Implications of Using the Data Encryption Standard (DES);;;;;RFC 4772;DOI 10.17487/RFC4772;December;https://www.rfc-editor.org/info/rfc4772 | |
| RFC4773;RFC6890;Huston, G.;Administration of the IANA Special Purpose IPv6 Address Block;;;;;RFC 4773;DOI 10.17487/RFC4773;December;https://www.rfc-editor.org/info/rfc4773 | |
| RFC4774;;Floyd, S.;Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field;;;BCP 124;;RFC 4774;DOI 10.17487/RFC4774;November;https://www.rfc-editor.org/info/rfc4774 | |
| RFC4775;;Bradner, S., Carpenter, B., Ed., and T. Narten;Procedures for Protocol Extensions and Variations;;;BCP 125;;RFC 4775;DOI 10.17487/RFC4775;December;https://www.rfc-editor.org/info/rfc4775 | |
| RFC4776;;Schulzrinne, H.;Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information;;;;;RFC 4776;DOI 10.17487/RFC4776;November;https://www.rfc-editor.org/info/rfc4776 | |
| RFC4777;;Murphy Jr., T., Rieth, P., and J. Stevens;IBM's iSeries Telnet Enhancements;;;;;RFC 4777;DOI 10.17487/RFC4777;November;https://www.rfc-editor.org/info/rfc4777 | |
| RFC4778;;Kaeo, M.;Operational Security Current Practices in Internet Service Provider Environments;;;;;RFC 4778;DOI 10.17487/RFC4778;January;https://www.rfc-editor.org/info/rfc4778 | |
| RFC4779;;Asadullah, S., Ahmed, A., Popoviciu, C., Savola, P., and J. Palet;ISP IPv6 Deployment Scenarios in Broadband Access Networks;;;;;RFC 4779;DOI 10.17487/RFC4779;January;https://www.rfc-editor.org/info/rfc4779 | |
| RFC4780;;Lingle, K., Mule, J-F., Maeng, J., and D. Walker;Management Information Base for the Session Initiation Protocol (SIP);;;;;RFC 4780;DOI 10.17487/RFC4780;April;https://www.rfc-editor.org/info/rfc4780 | |
| RFC4781;;Rekhter, Y. and R. Aggarwal;Graceful Restart Mechanism for BGP with MPLS;;;;;RFC 4781;DOI 10.17487/RFC4781;January;https://www.rfc-editor.org/info/rfc4781 | |
| RFC4782;;Floyd, S., Allman, M., Jain, A., and P. Sarolahti;Quick-Start for TCP and IP;;;;;RFC 4782;DOI 10.17487/RFC4782;January;https://www.rfc-editor.org/info/rfc4782 | |
| RFC4783;;Berger, L., Ed.;GMPLS - Communication of Alarm Information;;;;;RFC 4783;DOI 10.17487/RFC4783;December;https://www.rfc-editor.org/info/rfc4783 | |
| RFC4784;;Carroll, C. and F. Quick;Verizon Wireless Dynamic Mobile IP Key Update for cdma2000(R) Networks;;;;;RFC 4784;DOI 10.17487/RFC4784;June;https://www.rfc-editor.org/info/rfc4784 | |
| RFC4785;;Blumenthal, U. and P. Goel;Pre-Shared Key (PSK) Ciphersuites with NULL Encryption for Transport Layer Security (TLS);;;;;RFC 4785;DOI 10.17487/RFC4785;January;https://www.rfc-editor.org/info/rfc4785 | |
| RFC4786;;Abley, J. and K. Lindqvist;Operation of Anycast Services;;;BCP 126;;RFC 4786;DOI 10.17487/RFC4786;December;https://www.rfc-editor.org/info/rfc4786 | |
| RFC4787;;Audet, F., Ed., and C. Jennings;Network Address Translation (NAT) Behavioral Requirements for Unicast UDP;;;BCP 127;;RFC 4787;DOI 10.17487/RFC4787;January;https://www.rfc-editor.org/info/rfc4787 | |
| RFC4788;;Xie, Q. and R. Kapoor;Enhancements to RTP Payload Formats for EVRC Family Codecs;;;;;RFC 4788;DOI 10.17487/RFC4788;January;https://www.rfc-editor.org/info/rfc4788 | |
| RFC4789;;Schoenwaelder, J. and T. Jeffree;Simple Network Management Protocol (SNMP) over IEEE 802 Networks;;;;;RFC 4789;DOI 10.17487/RFC4789;November;https://www.rfc-editor.org/info/rfc4789 | |
| RFC4790;;Newman, C., Duerst, M., and A. Gulbrandsen;Internet Application Protocol Collation Registry;;;;;RFC 4790;DOI 10.17487/RFC4790;March;https://www.rfc-editor.org/info/rfc4790 | |
| RFC4791;;Daboo, C., Desruisseaux, B., and L. Dusseault;Calendaring Extensions to WebDAV (CalDAV);;;;;RFC 4791;DOI 10.17487/RFC4791;March;https://www.rfc-editor.org/info/rfc4791 | |
| RFC4792;;Legg, S.;Encoding Instructions for the Generic String Encoding Rules (GSER);;;;;RFC 4792;DOI 10.17487/RFC4792;January;https://www.rfc-editor.org/info/rfc4792 | |
| RFC4793;;Nystroem, M.;The EAP Protected One-Time Password Protocol (EAP-POTP);;;;;RFC 4793;DOI 10.17487/RFC4793;February;https://www.rfc-editor.org/info/rfc4793 | |
| RFC4794;;Fenner, B.;RFC 1264 Is Obsolete;;;;;RFC 4794;DOI 10.17487/RFC4794;December;https://www.rfc-editor.org/info/rfc4794 | |
| RFC4795;;Aboba, B., Thaler, D., and L. Esibov;Link-local Multicast Name Resolution (LLMNR);;;;;RFC 4795;DOI 10.17487/RFC4795;January;https://www.rfc-editor.org/info/rfc4795 | |
| RFC4796;;Hautakorpi, J. and G. Camarillo;The Session Description Protocol (SDP) Content Attribute;;;;;RFC 4796;DOI 10.17487/RFC4796;February;https://www.rfc-editor.org/info/rfc4796 | |
| RFC4797;;Rekhter, Y., Bonica, R., and E. Rosen;Use of Provider Edge to Provider Edge (PE-PE) Generic Routing Encapsulation (GRE) or IP in BGP/MPLS IP Virtual Private Networks;;;;;RFC 4797;DOI 10.17487/RFC4797;January;https://www.rfc-editor.org/info/rfc4797 | |
| RFC4798;;De Clercq, J., Ooms, D., Prevost, S., and F. Le Faucheur;Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE);;;;;RFC 4798;DOI 10.17487/RFC4798;February;https://www.rfc-editor.org/info/rfc4798 | |
| RFC4801;;Nadeau, T., Ed., and A. Farrel, Ed.;Definitions of Textual Conventions for Generalized Multiprotocol Label Switching (GMPLS) Management;;;;;RFC 4801;DOI 10.17487/RFC4801;February;https://www.rfc-editor.org/info/rfc4801 | |
| RFC4802;;Nadeau, T., Ed., and A. Farrel, Ed.;Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base;;;;;RFC 4802;DOI 10.17487/RFC4802;February;https://www.rfc-editor.org/info/rfc4802 | |
| RFC4803;;Nadeau, T., Ed., and A. Farrel, Ed.;Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR) Management Information Base;;;;;RFC 4803;DOI 10.17487/RFC4803;February;https://www.rfc-editor.org/info/rfc4803 | |
| RFC4804;;Le Faucheur, F., Ed.;Aggregation of Resource ReSerVation Protocol (RSVP) Reservations over MPLS TE/DS-TE Tunnels;;;;;RFC 4804;DOI 10.17487/RFC4804;February;https://www.rfc-editor.org/info/rfc4804 | |
| RFC4805;;Nicklass, O., Ed.;Definitions of Managed Objects for the DS1, J1, E1, DS2, and E2 Interface Types;;;;;RFC 4805;DOI 10.17487/RFC4805;March;https://www.rfc-editor.org/info/rfc4805 | |
| RFC4806;;Myers, M. and H. Tschofenig;Online Certificate Status Protocol (OCSP) Extensions to IKEv2;;;;;RFC 4806;DOI 10.17487/RFC4806;February;https://www.rfc-editor.org/info/rfc4806 | |
| RFC4807;;Baer, M., Charlet, R., Hardaker, W., Story, R., and C. Wang;IPsec Security Policy Database Configuration MIB;;;;;RFC 4807;DOI 10.17487/RFC4807;March;https://www.rfc-editor.org/info/rfc4807 | |
| RFC4808;;Bellovin, S.;Key Change Strategies for TCP-MD5;;;;;RFC 4808;DOI 10.17487/RFC4808;March;https://www.rfc-editor.org/info/rfc4808 | |
| RFC4809;;Bonatti, C., Ed., Turner, S., Ed., and G. Lebovitz, Ed.;Requirements for an IPsec Certificate Management Profile;;;;;RFC 4809;DOI 10.17487/RFC4809;February;https://www.rfc-editor.org/info/rfc4809 | |
| RFC4810;;Wallace, C., Pordesch, U., and R. Brandner;Long-Term Archive Service Requirements;;;;;RFC 4810;DOI 10.17487/RFC4810;March;https://www.rfc-editor.org/info/rfc4810 | |
| RFC4811;;Nguyen, L., Roy, A., and A. Zinin;OSPF Out-of-Band Link State Database (LSDB) Resynchronization;;;;;RFC 4811;DOI 10.17487/RFC4811;March;https://www.rfc-editor.org/info/rfc4811 | |
| RFC4812;;Nguyen, L., Roy, A., and A. Zinin;OSPF Restart Signaling;;;;;RFC 4812;DOI 10.17487/RFC4812;March;https://www.rfc-editor.org/info/rfc4812 | |
| RFC4813;RFC5613;Friedman, B., Nguyen, L., Roy, A., Yeung, D., and A. Zinin;OSPF Link-Local Signaling;;;;;RFC 4813;DOI 10.17487/RFC4813;March;https://www.rfc-editor.org/info/rfc4813 | |
| RFC4814;;Newman, D. and T. Player;Hash and Stuffing: Overlooked Factors in Network Device Benchmarking;;;;;RFC 4814;DOI 10.17487/RFC4814;March;https://www.rfc-editor.org/info/rfc4814 | |
| RFC4815;;Jonsson, L-E., Sandlund, K., Pelletier, G., and P. Kremer;RObust Header Compression (ROHC): Corrections and Clarifications to RFC 3095;;;;;RFC 4815;DOI 10.17487/RFC4815;February;https://www.rfc-editor.org/info/rfc4815 | |
| RFC4816;;Malis, A., Martini, L., Brayley, J., and T. Walsh;Pseudowire Emulation Edge-to-Edge (PWE3) Asynchronous Transfer Mode (ATM) Transparent Cell Transport Service;;;;;RFC 4816;DOI 10.17487/RFC4816;February;https://www.rfc-editor.org/info/rfc4816 | |
| RFC4817;;Townsley, M., Pignataro, C., Wainner, S., Seely, T., and J. Young;Encapsulation of MPLS over Layer 2 Tunneling Protocol Version 3;;;;;RFC 4817;DOI 10.17487/RFC4817;March;https://www.rfc-editor.org/info/rfc4817 | |
| RFC4818;;Salowey, J. and R. Droms;RADIUS Delegated-IPv6-Prefix Attribute;;;;;RFC 4818;DOI 10.17487/RFC4818;April;https://www.rfc-editor.org/info/rfc4818 | |
| RFC4819;;Galbraith, J., Van Dyke, J., and J. Bright;Secure Shell Public Key Subsystem;;;;;RFC 4819;DOI 10.17487/RFC4819;March;https://www.rfc-editor.org/info/rfc4819 | |
| RFC4820;;Tuexen, M., Stewart, R., and P. Lei;Padding Chunk and Parameter for the Stream Control Transmission Protocol (SCTP);;;;;RFC 4820;DOI 10.17487/RFC4820;March;https://www.rfc-editor.org/info/rfc4820 | |
| RFC4821;;Mathis, M. and J. Heffner;Packetization Layer Path MTU Discovery;;;;;RFC 4821;DOI 10.17487/RFC4821;March;https://www.rfc-editor.org/info/rfc4821 | |
| RFC4822;;Atkinson, R. and M. Fanto;RIPv2 Cryptographic Authentication;;;;;RFC 4822;DOI 10.17487/RFC4822;February;https://www.rfc-editor.org/info/rfc4822 | |
| RFC4823;;Harding, T. and R. Scott;FTP Transport for Secure Peer-to-Peer Business Data Interchange over the Internet;;;;;RFC 4823;DOI 10.17487/RFC4823;April;https://www.rfc-editor.org/info/rfc4823 | |
| RFC4824;;Hofmueller, J., Ed., Bachmann, A., Ed., and IO. zmoelnig, Ed.;The Transmission of IP Datagrams over the Semaphore Flag Signaling System (SFSS);;;;;RFC 4824;DOI 10.17487/RFC4824;April;https://www.rfc-editor.org/info/rfc4824 | |
| RFC4825;;Rosenberg, J.;The Extensible Markup Language (XML) Configuration Access Protocol (XCAP);;;;;RFC 4825;DOI 10.17487/RFC4825;May;https://www.rfc-editor.org/info/rfc4825 | |
| RFC4826;;Rosenberg, J.;Extensible Markup Language (XML) Formats for Representing Resource Lists;;;;;RFC 4826;DOI 10.17487/RFC4826;May;https://www.rfc-editor.org/info/rfc4826 | |
| RFC4827;;Isomaki, M. and E. Leppanen;An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Manipulating Presence Document Contents;;;;;RFC 4827;DOI 10.17487/RFC4827;May;https://www.rfc-editor.org/info/rfc4827 | |
| RFC4828;;Floyd, S. and E. Kohler;TCP Friendly Rate Control (TFRC): The Small-Packet (SP) Variant;;;;;RFC 4828;DOI 10.17487/RFC4828;April;https://www.rfc-editor.org/info/rfc4828 | |
| RFC4829;;de Oliveira, J., Ed., Vasseur, JP., Ed., Chen, L., and C. Scoglio;Label Switched Path (LSP) Preemption Policies for MPLS Traffic Engineering;;;;;RFC 4829;DOI 10.17487/RFC4829;April;https://www.rfc-editor.org/info/rfc4829 | |
| RFC4830;;Kempf, J., Ed.;Problem Statement for Network-Based Localized Mobility Management (NETLMM);;;;;RFC 4830;DOI 10.17487/RFC4830;April;https://www.rfc-editor.org/info/rfc4830 | |
| RFC4831;;Kempf, J., Ed.;Goals for Network-Based Localized Mobility Management (NETLMM);;;;;RFC 4831;DOI 10.17487/RFC4831;April;https://www.rfc-editor.org/info/rfc4831 | |
| RFC4832;;Vogt, C. and J. Kempf;Security Threats to Network-Based Localized Mobility Management (NETLMM);;;;;RFC 4832;DOI 10.17487/RFC4832;April;https://www.rfc-editor.org/info/rfc4832 | |
| RFC4833;;Lear, E. and P. Eggert;Timezone Options for DHCP;;;;;RFC 4833;DOI 10.17487/RFC4833;April;https://www.rfc-editor.org/info/rfc4833 | |
| RFC4834;;Morin, T., Ed.;Requirements for Multicast in Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs);;;;;RFC 4834;DOI 10.17487/RFC4834;April;https://www.rfc-editor.org/info/rfc4834 | |
| RFC4835;RFC7321;Manral, V.;Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH);;;;;RFC 4835;DOI 10.17487/RFC4835;April;https://www.rfc-editor.org/info/rfc4835 | |
| RFC4836;;Beili, E.;Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs);;;;;RFC 4836;DOI 10.17487/RFC4836;April;https://www.rfc-editor.org/info/rfc4836 | |
| RFC4837;;Khermosh, L.;Managed Objects of Ethernet Passive Optical Networks (EPON);;;;;RFC 4837;DOI 10.17487/RFC4837;July;https://www.rfc-editor.org/info/rfc4837 | |
| RFC4838;;Cerf, V., Burleigh, S., Hooke, A., Torgerson, L., Durst, R., Scott, K., Fall, K., and H. Weiss;Delay-Tolerant Networking Architecture;;;;;RFC 4838;DOI 10.17487/RFC4838;April;https://www.rfc-editor.org/info/rfc4838 | |
| RFC4839;;Conboy, G., Rivlin, J., and J. Ferraiolo;Media Type Registrations for the Open eBook Publication Structure (OEBPS) Package File (OPF);;;;;RFC 4839;DOI 10.17487/RFC4839;April;https://www.rfc-editor.org/info/rfc4839 | |
| RFC4840;;Aboba, B., Ed., Davies, E., and D. Thaler;Multiple Encapsulation Methods Considered Harmful;;;;;RFC 4840;DOI 10.17487/RFC4840;April;https://www.rfc-editor.org/info/rfc4840 | |
| RFC4841;;Heard, C., Ed.;RFC 4181 Update to Recognize the IETF Trust;;;BCP 111;;RFC 4841;DOI 10.17487/RFC4841;March;https://www.rfc-editor.org/info/rfc4841 | |
| RFC4842;;Malis, A., Pate, P., Cohen, R., Ed., and D. Zelig;Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet (CEP);;;;;RFC 4842;DOI 10.17487/RFC4842;April;https://www.rfc-editor.org/info/rfc4842 | |
| RFC4843;RFC7343;Nikander, P., Laganier, J., and F. Dupont;An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers (ORCHID);;;;;RFC 4843;DOI 10.17487/RFC4843;April;https://www.rfc-editor.org/info/rfc4843 | |
| RFC4844;RFC8729;Daigle, L., Ed., and Internet Architecture Board;The RFC Series and RFC Editor;;;;;RFC 4844;DOI 10.17487/RFC4844;July;https://www.rfc-editor.org/info/rfc4844 | |
| RFC4845;;Daigle, L., Ed., and Internet Architecture Board;Process for Publication of IAB RFCs;;;;;RFC 4845;DOI 10.17487/RFC4845;July;https://www.rfc-editor.org/info/rfc4845 | |
| RFC4846;;Klensin, J., Ed., and D. Thaler, Ed.;Independent Submissions to the RFC Editor;;;;;RFC 4846;DOI 10.17487/RFC4846;July;https://www.rfc-editor.org/info/rfc4846 | |
| RFC4847;;Takeda, T., Ed.;Framework and Requirements for Layer 1 Virtual Private Networks;;;;;RFC 4847;DOI 10.17487/RFC4847;April;https://www.rfc-editor.org/info/rfc4847 | |
| RFC4848;;Daigle, L.;Domain-Based Application Service Location Using URIs and the Dynamic Delegation Discovery Service (DDDS);;;;;RFC 4848;DOI 10.17487/RFC4848;April;https://www.rfc-editor.org/info/rfc4848 | |
| RFC4849;;Congdon, P., Sanchez, M., and B. Aboba;RADIUS Filter Rule Attribute;;;;;RFC 4849;DOI 10.17487/RFC4849;April;https://www.rfc-editor.org/info/rfc4849 | |
| RFC4850;RFC7143;Wysochanski, D.;Declarative Public Extension Key for Internet Small Computer Systems Interface (iSCSI) Node Architecture;;;;;RFC 4850;DOI 10.17487/RFC4850;April;https://www.rfc-editor.org/info/rfc4850 | |
| RFC4851;;Cam-Winget, N., McGrew, D., Salowey, J., and H. Zhou;The Flexible Authentication via Secure Tunneling Extensible Authentication Protocol Method (EAP-FAST);;;;;RFC 4851;DOI 10.17487/RFC4851;May;https://www.rfc-editor.org/info/rfc4851 | |
| RFC4852;;Bound, J., Pouffary, Y., Klynsma, S., Chown, T., and D. Green;IPv6 Enterprise Network Analysis - IP Layer 3 Focus;;;;;RFC 4852;DOI 10.17487/RFC4852;April;https://www.rfc-editor.org/info/rfc4852 | |
| RFC4853;;Housley, R.;Cryptographic Message Syntax (CMS) Multiple Signer Clarification;;;;;RFC 4853;DOI 10.17487/RFC4853;April;https://www.rfc-editor.org/info/rfc4853 | |
| RFC4854;;Saint-Andre, P.;A Uniform Resource Name (URN) Namespace for Extensions to the Extensible Messaging and Presence Protocol (XMPP);;;;;RFC 4854;DOI 10.17487/RFC4854;April;https://www.rfc-editor.org/info/rfc4854 | |
| RFC4855;;Casner, S.;Media Type Registration of RTP Payload Formats;;;;;RFC 4855;DOI 10.17487/RFC4855;February;https://www.rfc-editor.org/info/rfc4855 | |
| RFC4856;;Casner, S.;Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences;;;;;RFC 4856;DOI 10.17487/RFC4856;February;https://www.rfc-editor.org/info/rfc4856 | |
| RFC4857;;Fogelstroem, E., Jonsson, A., and C. Perkins;Mobile IPv4 Regional Registration;;;;;RFC 4857;DOI 10.17487/RFC4857;June;https://www.rfc-editor.org/info/rfc4857 | |
| RFC4858;;Levkowetz, H., Meyer, D., Eggert, L., and A. Mankin;Document Shepherding from Working Group Last Call to Publication;;;;;RFC 4858;DOI 10.17487/RFC4858;May;https://www.rfc-editor.org/info/rfc4858 | |
| RFC4859;;Farrel, A.;Codepoint Registry for the Flags Field in the Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Session Attribute Object;;;;;RFC 4859;DOI 10.17487/RFC4859;April;https://www.rfc-editor.org/info/rfc4859 | |
| RFC4860;;Le Faucheur, F., Davie, B., Bose, P., Christou, C., and M. Davenport;Generic Aggregate Resource ReSerVation Protocol (RSVP) Reservations;;;;;RFC 4860;DOI 10.17487/RFC4860;May;https://www.rfc-editor.org/info/rfc4860 | |
| RFC4861;;Narten, T., Nordmark, E., Simpson, W., and H. Soliman;Neighbor Discovery for IP version 6 (IPv6);;;;;RFC 4861;DOI 10.17487/RFC4861;September;https://www.rfc-editor.org/info/rfc4861 | |
| RFC4862;;Thomson, S., Narten, T., and T. Jinmei;IPv6 Stateless Address Autoconfiguration;;;;;RFC 4862;DOI 10.17487/RFC4862;September;https://www.rfc-editor.org/info/rfc4862 | |
| RFC4863;;Martini, L. and G. Swallow;Wildcard Pseudowire Type;;;;;RFC 4863;DOI 10.17487/RFC4863;May;https://www.rfc-editor.org/info/rfc4863 | |
| RFC4864;;Van de Velde, G., Hain, T., Droms, R., Carpenter, B., and E. Klein;Local Network Protection for IPv6;;;;;RFC 4864;DOI 10.17487/RFC4864;May;https://www.rfc-editor.org/info/rfc4864 | |
| RFC4865;;White, G. and G. Vaudreuil;SMTP Submission Service Extension for Future Message Release;;;;;RFC 4865;DOI 10.17487/RFC4865;May;https://www.rfc-editor.org/info/rfc4865 | |
| RFC4866;;Arkko, J., Vogt, C., and W. Haddad;Enhanced Route Optimization for Mobile IPv6;;;;;RFC 4866;DOI 10.17487/RFC4866;May;https://www.rfc-editor.org/info/rfc4866 | |
| RFC4867;;Sjoberg, J., Westerlund, M., Lakaniemi, A., and Q. Xie;RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs;;;;;RFC 4867;DOI 10.17487/RFC4867;April;https://www.rfc-editor.org/info/rfc4867 | |
| RFC4868;;Kelly, S. and S. Frankel;Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 with IPsec;;;;;RFC 4868;DOI 10.17487/RFC4868;May;https://www.rfc-editor.org/info/rfc4868 | |
| RFC4869;RFC6379;Law, L. and J. Solinas;Suite B Cryptographic Suites for IPsec;;;;;RFC 4869;DOI 10.17487/RFC4869;May;https://www.rfc-editor.org/info/rfc4869 | |
| RFC4870;RFC4871;Delany, M.;Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys);;;;;RFC 4870;DOI 10.17487/RFC4870;May;https://www.rfc-editor.org/info/rfc4870 | |
| RFC4871;RFC6376;Allman, E., Callas, J., Delany, M., Libbey, M., Fenton, J., and M. Thomas;DomainKeys Identified Mail (DKIM) Signatures;;;;;RFC 4871;DOI 10.17487/RFC4871;May;https://www.rfc-editor.org/info/rfc4871 | |
| RFC4872;;Lang, J., Ed., Rekhter, Y., Ed., and D. Papadimitriou, Ed.;RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery;;;;;RFC 4872;DOI 10.17487/RFC4872;May;https://www.rfc-editor.org/info/rfc4872 | |
| RFC4873;;Berger, L., Bryskin, I., Papadimitriou, D., and A. Farrel;GMPLS Segment Recovery;;;;;RFC 4873;DOI 10.17487/RFC4873;May;https://www.rfc-editor.org/info/rfc4873 | |
| RFC4874;;Lee, CY., Farrel, A., and S. De Cnodder;Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering (RSVP-TE);;;;;RFC 4874;DOI 10.17487/RFC4874;April;https://www.rfc-editor.org/info/rfc4874 | |
| RFC4875;;Aggarwal, R., Ed., Papadimitriou, D., Ed., and S. Yasukawa, Ed.;Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs);;;;;RFC 4875;DOI 10.17487/RFC4875;May;https://www.rfc-editor.org/info/rfc4875 | |
| RFC4876;;Neal-Joslin, B., Ed., Howard, L., and M. Ansari;A Configuration Profile Schema for Lightweight Directory Access Protocol (LDAP)-Based Agents;;;;;RFC 4876;DOI 10.17487/RFC4876;May;https://www.rfc-editor.org/info/rfc4876 | |
| RFC4877;;Devarapalli, V. and F. Dupont;Mobile IPv6 Operation with IKEv2 and the Revised IPsec Architecture;;;;;RFC 4877;DOI 10.17487/RFC4877;April;https://www.rfc-editor.org/info/rfc4877 | |
| RFC4878;;Squire, M.;Definitions and Managed Objects for Operations, Administration, and Maintenance (OAM) Functions on Ethernet-Like Interfaces;;;;;RFC 4878;DOI 10.17487/RFC4878;June;https://www.rfc-editor.org/info/rfc4878 | |
| RFC4879;RFC8179;Narten, T.;Clarification of the Third Party Disclosure Procedure in RFC 3979;;;;;RFC 4879;DOI 10.17487/RFC4879;April;https://www.rfc-editor.org/info/rfc4879 | |
| RFC4880;;Callas, J., Donnerhacke, L., Finney, H., Shaw, D., and R. Thayer;OpenPGP Message Format;;;;;RFC 4880;DOI 10.17487/RFC4880;November;https://www.rfc-editor.org/info/rfc4880 | |
| RFC4881;;El Malki, K., Ed.;Low-Latency Handoffs in Mobile IPv4;;;;;RFC 4881;DOI 10.17487/RFC4881;June;https://www.rfc-editor.org/info/rfc4881 | |
| RFC4882;;Koodli, R.;IP Address Location Privacy and Mobile IPv6: Problem Statement;;;;;RFC 4882;DOI 10.17487/RFC4882;May;https://www.rfc-editor.org/info/rfc4882 | |
| RFC4883;;Feher, G., Nemeth, K., Korn, A., and I. Cselenyi;Benchmarking Terminology for Resource Reservation Capable Routers;;;;;RFC 4883;DOI 10.17487/RFC4883;July;https://www.rfc-editor.org/info/rfc4883 | |
| RFC4884;;Bonica, R., Gan, D., Tappan, D., and C. Pignataro;Extended ICMP to Support Multi-Part Messages;;;;;RFC 4884;DOI 10.17487/RFC4884;April;https://www.rfc-editor.org/info/rfc4884 | |
| RFC4885;;Ernst, T. and H-Y. Lach;Network Mobility Support Terminology;;;;;RFC 4885;DOI 10.17487/RFC4885;July;https://www.rfc-editor.org/info/rfc4885 | |
| RFC4886;;Ernst, T.;Network Mobility Support Goals and Requirements;;;;;RFC 4886;DOI 10.17487/RFC4886;July;https://www.rfc-editor.org/info/rfc4886 | |
| RFC4887;;Thubert, P., Wakikawa, R., and V. Devarapalli;Network Mobility Home Network Models;;;;;RFC 4887;DOI 10.17487/RFC4887;July;https://www.rfc-editor.org/info/rfc4887 | |
| RFC4888;;Ng, C., Thubert, P., Watari, M., and F. Zhao;Network Mobility Route Optimization Problem Statement;;;;;RFC 4888;DOI 10.17487/RFC4888;July;https://www.rfc-editor.org/info/rfc4888 | |
| RFC4889;;Ng, C., Zhao, F., Watari, M., and P. Thubert;Network Mobility Route Optimization Solution Space Analysis;;;;;RFC 4889;DOI 10.17487/RFC4889;July;https://www.rfc-editor.org/info/rfc4889 | |
| RFC4890;;Davies, E. and J. Mohacsi;Recommendations for Filtering ICMPv6 Messages in Firewalls;;;;;RFC 4890;DOI 10.17487/RFC4890;May;https://www.rfc-editor.org/info/rfc4890 | |
| RFC4891;;Graveman, R., Parthasarathy, M., Savola, P., and H. Tschofenig;Using IPsec to Secure IPv6-in-IPv4 Tunnels;;;;;RFC 4891;DOI 10.17487/RFC4891;May;https://www.rfc-editor.org/info/rfc4891 | |
| RFC4892;;Woolf, S. and D. Conrad;Requirements for a Mechanism Identifying a Name Server Instance;;;;;RFC 4892;DOI 10.17487/RFC4892;June;https://www.rfc-editor.org/info/rfc4892 | |
| RFC4893;RFC6793;Vohra, Q. and E. Chen;BGP Support for Four-octet AS Number Space;;;;;RFC 4893;DOI 10.17487/RFC4893;May;https://www.rfc-editor.org/info/rfc4893 | |
| RFC4894;;Hoffman, P.;Use of Hash Algorithms in Internet Key Exchange (IKE) and IPsec;;;;;RFC 4894;DOI 10.17487/RFC4894;May;https://www.rfc-editor.org/info/rfc4894 | |
| RFC4895;;Tuexen, M., Stewart, R., Lei, P., and E. Rescorla;Authenticated Chunks for the Stream Control Transmission Protocol (SCTP);;;;;RFC 4895;DOI 10.17487/RFC4895;August;https://www.rfc-editor.org/info/rfc4895 | |
| RFC4896;;Surtees, A., West, M., and A. Roach;Signaling Compression (SigComp) Corrections and Clarifications;;;;;RFC 4896;DOI 10.17487/RFC4896;June;https://www.rfc-editor.org/info/rfc4896 | |
| RFC4897;;Klensin, J. and S. Hartman;Handling Normative References to Standards-Track Documents;;;BCP 97;;RFC 4897;DOI 10.17487/RFC4897;June;https://www.rfc-editor.org/info/rfc4897 | |
| RFC4898;;Mathis, M., Heffner, J., and R. Raghunarayan;TCP Extended Statistics MIB;;;;;RFC 4898;DOI 10.17487/RFC4898;May;https://www.rfc-editor.org/info/rfc4898 | |
| RFC4901;;Ash, J., Ed., Hand, J., Ed., and A. Malis, Ed.;Protocol Extensions for Header Compression over MPLS;;;;;RFC 4901;DOI 10.17487/RFC4901;June;https://www.rfc-editor.org/info/rfc4901 | |
| RFC4902;;Stecher, M.;Integrity, Privacy, and Security in Open Pluggable Edge Services (OPES) for SMTP;;;;;RFC 4902;DOI 10.17487/RFC4902;May;https://www.rfc-editor.org/info/rfc4902 | |
| RFC4903;;Thaler, D.;Multi-Link Subnet Issues;;;;;RFC 4903;DOI 10.17487/RFC4903;June;https://www.rfc-editor.org/info/rfc4903 | |
| RFC4904;;Gurbani, V. and C. Jennings;Representing Trunk Groups in tel/sip Uniform Resource Identifiers (URIs);;;;;RFC 4904;DOI 10.17487/RFC4904;June;https://www.rfc-editor.org/info/rfc4904 | |
| RFC4905;;Martini, L., Ed., Rosen, E., Ed., and N. El-Aawar, Ed.;Encapsulation Methods for Transport of Layer 2 Frames over MPLS Networks;;;;;RFC 4905;DOI 10.17487/RFC4905;June;https://www.rfc-editor.org/info/rfc4905 | |
| RFC4906;;Martini, L., Ed., Rosen, E., Ed., and N. El-Aawar, Ed.;Transport of Layer 2 Frames Over MPLS;;;;;RFC 4906;DOI 10.17487/RFC4906;June;https://www.rfc-editor.org/info/rfc4906 | |
| RFC4907;;Aboba, B., Ed.;Architectural Implications of Link Indications;;;;;RFC 4907;DOI 10.17487/RFC4907;June;https://www.rfc-editor.org/info/rfc4907 | |
| RFC4908;;Nagami, K., Uda, S., Ogashiwa, N., Esaki, H., Wakikawa, R., and H. Ohnishi;Multi-homing for small scale fixed network Using Mobile IP and NEMO;;;;;RFC 4908;DOI 10.17487/RFC4908;June;https://www.rfc-editor.org/info/rfc4908 | |
| RFC4909;RFC5410, RFC6309;Dondeti, L., Ed., Castleford, D., and F. Hartung;Multimedia Internet KEYing (MIKEY) General Extension Payload for Open Mobile Alliance BCAST LTKM/STKM Transport;;;;;RFC 4909;DOI 10.17487/RFC4909;June;https://www.rfc-editor.org/info/rfc4909 | |
| RFC4910;;Legg, S. and D. Prager;Robust XML Encoding Rules (RXER) for Abstract Syntax Notation One (ASN.1);;;;;RFC 4910;DOI 10.17487/RFC4910;July;https://www.rfc-editor.org/info/rfc4910 | |
| RFC4911;;Legg, S.;Encoding Instructions for the Robust XML Encoding Rules (RXER);;;;;RFC 4911;DOI 10.17487/RFC4911;July;https://www.rfc-editor.org/info/rfc4911 | |
| RFC4912;;Legg, S.;Abstract Syntax Notation X (ASN.X);;;;;RFC 4912;DOI 10.17487/RFC4912;July;https://www.rfc-editor.org/info/rfc4912 | |
| RFC4913;;Legg, S.;Abstract Syntax Notation X (ASN.X) Representation of Encoding Instructions for the Generic String Encoding Rules (GSER);;;;;RFC 4913;DOI 10.17487/RFC4913;July;https://www.rfc-editor.org/info/rfc4913 | |
| RFC4914;;Legg, S.;Abstract Syntax Notation X (ASN.X) Representation of Encoding Instructions for the XML Encoding Rules (XER);;;;;RFC 4914;DOI 10.17487/RFC4914;July;https://www.rfc-editor.org/info/rfc4914 | |
| RFC4915;;Psenak, P., Mirtorabi, S., Roy, A., Nguyen, L., and P. Pillay-Esnault;Multi-Topology (MT) Routing in OSPF;;;;;RFC 4915;DOI 10.17487/RFC4915;June;https://www.rfc-editor.org/info/rfc4915 | |
| RFC4916;;Elwell, J.;Connected Identity in the Session Initiation Protocol (SIP);;;;;RFC 4916;DOI 10.17487/RFC4916;June;https://www.rfc-editor.org/info/rfc4916 | |
| RFC4917;;Sastry, V., Leung, K., and A. Patel;Mobile IPv4 Message String Extension;;;;;RFC 4917;DOI 10.17487/RFC4917;June;https://www.rfc-editor.org/info/rfc4917 | |
| RFC4918;;Dusseault, L., Ed.;HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV);;;;;RFC 4918;DOI 10.17487/RFC4918;June;https://www.rfc-editor.org/info/rfc4918 | |
| RFC4919;;Kushalnagar, N., Montenegro, G., and C. Schumacher;IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs): Overview, Assumptions, Problem Statement, and Goals;;;;;RFC 4919;DOI 10.17487/RFC4919;August;https://www.rfc-editor.org/info/rfc4919 | |
| RFC4920;;Farrel, A., Ed., Satyanarayana, A., Iwata, A., Fujita, N., and G. Ash;Crankback Signaling Extensions for MPLS and GMPLS RSVP-TE;;;;;RFC 4920;DOI 10.17487/RFC4920;July;https://www.rfc-editor.org/info/rfc4920 | |
| RFC4923;;Baker, F. and P. Bose;Quality of Service (QoS) Signaling in a Nested Virtual Private Network;;;;;RFC 4923;DOI 10.17487/RFC4923;August;https://www.rfc-editor.org/info/rfc4923 | |
| RFC4924;;Aboba, B., Ed., and E. Davies;Reflections on Internet Transparency;;;;;RFC 4924;DOI 10.17487/RFC4924;July;https://www.rfc-editor.org/info/rfc4924 | |
| RFC4925;;Li, X., Ed., Dawkins, S., Ed., Ward, D., Ed., and A. Durand, Ed.;Softwire Problem Statement;;;;;RFC 4925;DOI 10.17487/RFC4925;July;https://www.rfc-editor.org/info/rfc4925 | |
| RFC4926;;Kalin, T. and M.Molina;A URN Namespace for GEANT;;;;;RFC 4926;DOI 10.17487/RFC4926;July;https://www.rfc-editor.org/info/rfc4926 | |
| RFC4927;;Le Roux, J.-L., Ed.;Path Computation Element Communication Protocol (PCECP) Specific Requirements for Inter-Area MPLS and GMPLS Traffic Engineering;;;;;RFC 4927;DOI 10.17487/RFC4927;June;https://www.rfc-editor.org/info/rfc4927 | |
| RFC4928;;Swallow, G., Bryant, S., and L. Andersson;Avoiding Equal Cost Multipath Treatment in MPLS Networks;;;BCP 128;;RFC 4928;DOI 10.17487/RFC4928;June;https://www.rfc-editor.org/info/rfc4928 | |
| RFC4929;;Andersson, L., Ed., and A. Farrel, Ed.;Change Process for Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Protocols and Procedures;;;BCP 129;;RFC 4929;DOI 10.17487/RFC4929;June;https://www.rfc-editor.org/info/rfc4929 | |
| RFC4930;RFC5730;Hollenbeck, S.;Extensible Provisioning Protocol (EPP);;;;;RFC 4930;DOI 10.17487/RFC4930;May;https://www.rfc-editor.org/info/rfc4930 | |
| RFC4931;RFC5731;Hollenbeck, S.;Extensible Provisioning Protocol (EPP) Domain Name Mapping;;;;;RFC 4931;DOI 10.17487/RFC4931;May;https://www.rfc-editor.org/info/rfc4931 | |
| RFC4932;RFC5732;Hollenbeck, S.;Extensible Provisioning Protocol (EPP) Host Mapping;;;;;RFC 4932;DOI 10.17487/RFC4932;May;https://www.rfc-editor.org/info/rfc4932 | |
| RFC4933;RFC5733;Hollenbeck, S.;Extensible Provisioning Protocol (EPP) Contact Mapping;;;;;RFC 4933;DOI 10.17487/RFC4933;May;https://www.rfc-editor.org/info/rfc4933 | |
| RFC4934;RFC5734;Hollenbeck, S.;Extensible Provisioning Protocol (EPP) Transport Over TCP;;;;;RFC 4934;DOI 10.17487/RFC4934;May;https://www.rfc-editor.org/info/rfc4934 | |
| RFC4935;;DeSanti, C., Vivek, H., McCloghrie, K., and S. Gai;Fibre Channel Fabric Configuration Server MIB;;;;;RFC 4935;DOI 10.17487/RFC4935;August;https://www.rfc-editor.org/info/rfc4935 | |
| RFC4936;;DeSanti, C., Vivek, H., McCloghrie, K., and S. Gai;Fibre Channel Zone Server MIB;;;;;RFC 4936;DOI 10.17487/RFC4936;August;https://www.rfc-editor.org/info/rfc4936 | |
| RFC4937;;Arberg, P. and V. Mammoliti;IANA Considerations for PPP over Ethernet (PPPoE);;;;;RFC 4937;DOI 10.17487/RFC4937;June;https://www.rfc-editor.org/info/rfc4937 | |
| RFC4938;RFC5578;Berry, B. and H. Holgate;PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics;;;;;RFC 4938;DOI 10.17487/RFC4938;June;https://www.rfc-editor.org/info/rfc4938 | |
| RFC4939;;Gibbons, K., Ramkumar, G., and S. Kipp;Definitions of Managed Objects for iSNS (Internet Storage Name Service);;;;;RFC 4939;DOI 10.17487/RFC4939;July;https://www.rfc-editor.org/info/rfc4939 | |
| RFC4940;;Kompella, K. and B. Fenner;IANA Considerations for OSPF;;;BCP 130;;RFC 4940;DOI 10.17487/RFC4940;July;https://www.rfc-editor.org/info/rfc4940 | |
| RFC4941;;Narten, T., Draves, R., and S. Krishnan;Privacy Extensions for Stateless Address Autoconfiguration in IPv6;;;;;RFC 4941;DOI 10.17487/RFC4941;September;https://www.rfc-editor.org/info/rfc4941 | |
| RFC4942;;Davies, E., Krishnan, S., and P. Savola;IPv6 Transition/Co-existence Security Considerations;;;;;RFC 4942;DOI 10.17487/RFC4942;September;https://www.rfc-editor.org/info/rfc4942 | |
| RFC4943;;Roy, S., Durand, A., and J. Paugh;IPv6 Neighbor Discovery On-Link Assumption Considered Harmful;;;;;RFC 4943;DOI 10.17487/RFC4943;September;https://www.rfc-editor.org/info/rfc4943 | |
| RFC4944;;Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler;Transmission of IPv6 Packets over IEEE 802.15.4 Networks;;;;;RFC 4944;DOI 10.17487/RFC4944;September;https://www.rfc-editor.org/info/rfc4944 | |
| RFC4945;;Korver, B.;The Internet IP Security PKI Profile of IKEv1/ISAKMP, IKEv2, and PKIX;;;;;RFC 4945;DOI 10.17487/RFC4945;August;https://www.rfc-editor.org/info/rfc4945 | |
| RFC4946;;Snell, J.;Atom License Extension;;;;;RFC 4946;DOI 10.17487/RFC4946;July;https://www.rfc-editor.org/info/rfc4946 | |
| RFC4947;;Fairhurst, G. and M. Montpetit;Address Resolution Mechanisms for IP Datagrams over MPEG-2 Networks;;;;;RFC 4947;DOI 10.17487/RFC4947;July;https://www.rfc-editor.org/info/rfc4947 | |
| RFC4948;;Andersson, L., Davies, E., and L. Zhang;Report from the IAB workshop on Unwanted Traffic March 9-10, 2006;;;;;RFC 4948;DOI 10.17487/RFC4948;August;https://www.rfc-editor.org/info/rfc4948 | |
| RFC4949;;Shirey, R.;Internet Security Glossary, Version 2;;FYI 36;;;RFC 4949;DOI 10.17487/RFC4949;August;https://www.rfc-editor.org/info/rfc4949 | |
| RFC4950;;Bonica, R., Gan, D., Tappan, D., and C. Pignataro;ICMP Extensions for Multiprotocol Label Switching;;;;;RFC 4950;DOI 10.17487/RFC4950;August;https://www.rfc-editor.org/info/rfc4950 | |
| RFC4951;;Jain, V., Ed.;Fail Over Extensions for Layer 2 Tunneling Protocol (L2TP) "failover";;;;;RFC 4951;DOI 10.17487/RFC4951;August;https://www.rfc-editor.org/info/rfc4951 | |
| RFC4952;RFC6530;Klensin, J. and Y. Ko;Overview and Framework for Internationalized Email;;;;;RFC 4952;DOI 10.17487/RFC4952;July;https://www.rfc-editor.org/info/rfc4952 | |
| RFC4953;;Touch, J.;Defending TCP Against Spoofing Attacks;;;;;RFC 4953;DOI 10.17487/RFC4953;July;https://www.rfc-editor.org/info/rfc4953 | |
| RFC4954;;Siemborski, R., Ed., and A. Melnikov, Ed.;SMTP Service Extension for Authentication;;;;;RFC 4954;DOI 10.17487/RFC4954;July;https://www.rfc-editor.org/info/rfc4954 | |
| RFC4955;;Blacka, D.;DNS Security (DNSSEC) Experiments;;;;;RFC 4955;DOI 10.17487/RFC4955;July;https://www.rfc-editor.org/info/rfc4955 | |
| RFC4956;;Arends, R., Kosters, M., and D. Blacka;DNS Security (DNSSEC) Opt-In;;;;;RFC 4956;DOI 10.17487/RFC4956;July;https://www.rfc-editor.org/info/rfc4956 | |
| RFC4957;;Krishnan, S., Ed., Montavont, N., Njedjou, E., Veerepalli, S., and A. Yegin, Ed.;Link-Layer Event Notifications for Detecting Network Attachments;;;;;RFC 4957;DOI 10.17487/RFC4957;August;https://www.rfc-editor.org/info/rfc4957 | |
| RFC4958;;Carlberg, K.;A Framework for Supporting Emergency Telecommunications Services (ETS) within a Single Administrative Domain;;;;;RFC 4958;DOI 10.17487/RFC4958;July;https://www.rfc-editor.org/info/rfc4958 | |
| RFC4959;;Siemborski, R. and A. Gulbrandsen;IMAP Extension for Simple Authentication and Security Layer (SASL) Initial Client Response;;;;;RFC 4959;DOI 10.17487/RFC4959;September;https://www.rfc-editor.org/info/rfc4959 | |
| RFC4960;;Stewart, R., Ed.;Stream Control Transmission Protocol;;;;;RFC 4960;DOI 10.17487/RFC4960;September;https://www.rfc-editor.org/info/rfc4960 | |
| RFC4961;;Wing, D.;Symmetric RTP / RTP Control Protocol (RTCP);;;BCP 131;;RFC 4961;DOI 10.17487/RFC4961;July;https://www.rfc-editor.org/info/rfc4961 | |
| RFC4962;;Housley, R. and B. Aboba;Guidance for Authentication, Authorization, and Accounting (AAA) Key Management;;;BCP 132;;RFC 4962;DOI 10.17487/RFC4962;July;https://www.rfc-editor.org/info/rfc4962 | |
| RFC4963;;Heffner, J., Mathis, M., and B. Chandler;IPv4 Reassembly Errors at High Data Rates;;;;;RFC 4963;DOI 10.17487/RFC4963;July;https://www.rfc-editor.org/info/rfc4963 | |
| RFC4964;;Allen, A., Ed., Holm, J., and T. Hallin;The P-Answer-State Header Extension to the Session Initiation Protocol for the Open Mobile Alliance Push to Talk over Cellular;;;;;RFC 4964;DOI 10.17487/RFC4964;September;https://www.rfc-editor.org/info/rfc4964 | |
| RFC4965;;Mule, J-F. and W. Townsley;CableLabs - IETF Standardization Collaboration;;;;;RFC 4965;DOI 10.17487/RFC4965;September;https://www.rfc-editor.org/info/rfc4965 | |
| RFC4966;;Aoun, C. and E. Davies;Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status;;;;;RFC 4966;DOI 10.17487/RFC4966;July;https://www.rfc-editor.org/info/rfc4966 | |
| RFC4967;;Rosen, B.;Dial String Parameter for the Session Initiation Protocol Uniform Resource Identifier;;;;;RFC 4967;DOI 10.17487/RFC4967;July;https://www.rfc-editor.org/info/rfc4967 | |
| RFC4968;;Madanapalli, S., Ed.;Analysis of IPv6 Link Models for 802.16 Based Networks;;;;;RFC 4968;DOI 10.17487/RFC4968;August;https://www.rfc-editor.org/info/rfc4968 | |
| RFC4969;;Mayrhofer, A.;IANA Registration for vCard Enumservice;;;;;RFC 4969;DOI 10.17487/RFC4969;August;https://www.rfc-editor.org/info/rfc4969 | |
| RFC4970;RFC7770;Lindem, A., Ed., Shen, N., Vasseur, JP., Aggarwal, R., and S. Shaffer;Extensions to OSPF for Advertising Optional Router Capabilities;;;;;RFC 4970;DOI 10.17487/RFC4970;July;https://www.rfc-editor.org/info/rfc4970 | |
| RFC4971;RFC7981;Vasseur, JP., Ed., Shen, N., Ed., and R. Aggarwal, Ed.;Intermediate System to Intermediate System (IS-IS) Extensions for Advertising Router Information;;;;;RFC 4971;DOI 10.17487/RFC4971;July;https://www.rfc-editor.org/info/rfc4971 | |
| RFC4972;;Vasseur, JP., Ed., Leroux, JL., Ed., Yasukawa, S., Previdi, S., Psenak, P., and P. Mabbey;Routing Extensions for Discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic Engineering (TE) Mesh Membership;;;;;RFC 4972;DOI 10.17487/RFC4972;July;https://www.rfc-editor.org/info/rfc4972 | |
| RFC4973;;Srisuresh, P. and P. Joseph;OSPF-xTE: Experimental Extension to OSPF for Traffic Engineering;;;;;RFC 4973;DOI 10.17487/RFC4973;July;https://www.rfc-editor.org/info/rfc4973 | |
| RFC4974;;Papadimitriou, D. and A. Farrel;Generalized MPLS (GMPLS) RSVP-TE Signaling Extensions in Support of Calls;;;;;RFC 4974;DOI 10.17487/RFC4974;August;https://www.rfc-editor.org/info/rfc4974 | |
| RFC4975;;Campbell, B., Ed., Mahy, R., Ed., and C. Jennings, Ed.;The Message Session Relay Protocol (MSRP);;;;;RFC 4975;DOI 10.17487/RFC4975;September;https://www.rfc-editor.org/info/rfc4975 | |
| RFC4976;;Jennings, C., Mahy, R., and A. Roach;Relay Extensions for the Message Sessions Relay Protocol (MSRP);;;;;RFC 4976;DOI 10.17487/RFC4976;September;https://www.rfc-editor.org/info/rfc4976 | |
| RFC4977;;Tsirtsis, G. and H. Soliman;Problem Statement: Dual Stack Mobility;;;;;RFC 4977;DOI 10.17487/RFC4977;August;https://www.rfc-editor.org/info/rfc4977 | |
| RFC4978;;Gulbrandsen, A.;The IMAP COMPRESS Extension;;;;;RFC 4978;DOI 10.17487/RFC4978;August;https://www.rfc-editor.org/info/rfc4978 | |
| RFC4979;;Mayrhofer, A.;IANA Registration for Enumservice 'XMPP';;;;;RFC 4979;DOI 10.17487/RFC4979;August;https://www.rfc-editor.org/info/rfc4979 | |
| RFC4980;;Ng, C., Ernst, T., Paik, E., and M. Bagnulo;Analysis of Multihoming in Network Mobility Support;;;;;RFC 4980;DOI 10.17487/RFC4980;October;https://www.rfc-editor.org/info/rfc4980 | |
| RFC4981;;Risson, J. and T. Moors;Survey of Research towards Robust Peer-to-Peer Networks: Search Methods;;;;;RFC 4981;DOI 10.17487/RFC4981;September;https://www.rfc-editor.org/info/rfc4981 | |
| RFC4982;;Bagnulo, M. and J. Arkko;Support for Multiple Hash Algorithms in Cryptographically Generated Addresses (CGAs);;;;;RFC 4982;DOI 10.17487/RFC4982;July;https://www.rfc-editor.org/info/rfc4982 | |
| RFC4983;;DeSanti, C., Vivek, H., McCloghrie, K., and S. Gai;Fibre Channel Registered State Change Notification (RSCN) MIB;;;;;RFC 4983;DOI 10.17487/RFC4983;August;https://www.rfc-editor.org/info/rfc4983 | |
| RFC4984;;Meyer, D., Ed., Zhang, L., Ed., and K. Fall, Ed.;Report from the IAB Workshop on Routing and Addressing;;;;;RFC 4984;DOI 10.17487/RFC4984;September;https://www.rfc-editor.org/info/rfc4984 | |
| RFC4985;;Santesson, S.;Internet X.509 Public Key Infrastructure Subject Alternative Name for Expression of Service Name;;;;;RFC 4985;DOI 10.17487/RFC4985;August;https://www.rfc-editor.org/info/rfc4985 | |
| RFC4986;;Eland, H., Mundy, R., Crocker, S., and S. Krishnaswamy;Requirements Related to DNS Security (DNSSEC) Trust Anchor Rollover;;;;;RFC 4986;DOI 10.17487/RFC4986;August;https://www.rfc-editor.org/info/rfc4986 | |
| RFC4987;;Eddy, W.;TCP SYN Flooding Attacks and Common Mitigations;;;;;RFC 4987;DOI 10.17487/RFC4987;August;https://www.rfc-editor.org/info/rfc4987 | |
| RFC4988;;Koodli, R. and C. Perkins;Mobile IPv4 Fast Handovers;;;;;RFC 4988;DOI 10.17487/RFC4988;October;https://www.rfc-editor.org/info/rfc4988 | |
| RFC4990;;Shiomoto, K., Papneja, R., and R. Rabbat;Use of Addresses in Generalized Multiprotocol Label Switching (GMPLS) Networks;;;;;RFC 4990;DOI 10.17487/RFC4990;September;https://www.rfc-editor.org/info/rfc4990 | |
| RFC4991;;Newton, A.;A Common Schema for Internet Registry Information Service Transfer Protocols;;;;;RFC 4991;DOI 10.17487/RFC4991;August;https://www.rfc-editor.org/info/rfc4991 | |
| RFC4992;;Newton, A.;XML Pipelining with Chunks for the Internet Registry Information Service;;;;;RFC 4992;DOI 10.17487/RFC4992;August;https://www.rfc-editor.org/info/rfc4992 | |
| RFC4993;;Newton, A.;A Lightweight UDP Transfer Protocol for the Internet Registry Information Service;;;;;RFC 4993;DOI 10.17487/RFC4993;August;https://www.rfc-editor.org/info/rfc4993 | |
| RFC4994;;Zeng, S., Volz, B., Kinnear, K., and J. Brzozowski;DHCPv6 Relay Agent Echo Request Option;;;;;RFC 4994;DOI 10.17487/RFC4994;September;https://www.rfc-editor.org/info/rfc4994 | |
| RFC4995;RFC5795;Jonsson, L-E., Pelletier, G., and K. Sandlund;The RObust Header Compression (ROHC) Framework;;;;;RFC 4995;DOI 10.17487/RFC4995;July;https://www.rfc-editor.org/info/rfc4995 | |
| RFC4996;RFC6846;Pelletier, G., Sandlund, K., Jonsson, L-E., and M. West;RObust Header Compression (ROHC): A Profile for TCP/IP (ROHC-TCP);;;;;RFC 4996;DOI 10.17487/RFC4996;July;https://www.rfc-editor.org/info/rfc4996 | |
| RFC4997;;Finking, R. and G. Pelletier;Formal Notation for RObust Header Compression (ROHC-FN);;;;;RFC 4997;DOI 10.17487/RFC4997;July;https://www.rfc-editor.org/info/rfc4997 | |
| RFC4998;;Gondrom, T., Brandner, R., and U. Pordesch;Evidence Record Syntax (ERS);;;;;RFC 4998;DOI 10.17487/RFC4998;August;https://www.rfc-editor.org/info/rfc4998 | |
| RFC5000;RFC7100;RFC Editor;Internet Official Protocol Standards;;;;;RFC 5000;DOI 10.17487/RFC5000;May;https://www.rfc-editor.org/info/rfc5000 | |
| RFC5001;;Austein, R.;DNS Name Server Identifier (NSID) Option;;;;;RFC 5001;DOI 10.17487/RFC5001;August;https://www.rfc-editor.org/info/rfc5001 | |
| RFC5002;;Camarillo, G. and G. Blanco;The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header);;;;;RFC 5002;DOI 10.17487/RFC5002;August;https://www.rfc-editor.org/info/rfc5002 | |
| RFC5003;;Metz, C., Martini, L., Balus, F., and J. Sugimoto;Attachment Individual Identifier (AII) Types for Aggregation;;;;;RFC 5003;DOI 10.17487/RFC5003;September;https://www.rfc-editor.org/info/rfc5003 | |
| RFC5004;;Chen, E. and S. Sangli;Avoid BGP Best Path Transitions from One External to Another;;;;;RFC 5004;DOI 10.17487/RFC5004;September;https://www.rfc-editor.org/info/rfc5004 | |
| RFC5005;;Nottingham, M.;Feed Paging and Archiving;;;;;RFC 5005;DOI 10.17487/RFC5005;September;https://www.rfc-editor.org/info/rfc5005 | |
| RFC5006;RFC6106;Jeong, J., Ed., Park, S., Beloeil, L., and S. Madanapalli;IPv6 Router Advertisement Option for DNS Configuration;;;;;RFC 5006;DOI 10.17487/RFC5006;September;https://www.rfc-editor.org/info/rfc5006 | |
| RFC5007;;Brzozowski, J., Kinnear, K., Volz, B., and S. Zeng;DHCPv6 Leasequery;;;;;RFC 5007;DOI 10.17487/RFC5007;September;https://www.rfc-editor.org/info/rfc5007 | |
| RFC5008;RFC6318;Housley, R. and J. Solinas;Suite B in Secure/Multipurpose Internet Mail Extensions (S/MIME);;;;;RFC 5008;DOI 10.17487/RFC5008;September;https://www.rfc-editor.org/info/rfc5008 | |
| RFC5009;;Ejza, R.;Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early Media;;;;;RFC 5009;DOI 10.17487/RFC5009;September;https://www.rfc-editor.org/info/rfc5009 | |
| RFC5010;;Kinnear, K., Normoyle, M., and M. Stapp;The Dynamic Host Configuration Protocol Version 4 (DHCPv4) Relay Agent Flags Suboption;;;;;RFC 5010;DOI 10.17487/RFC5010;September;https://www.rfc-editor.org/info/rfc5010 | |
| RFC5011;;StJohns, M.;Automated Updates of DNS Security (DNSSEC) Trust Anchors;;;;STD 74;RFC 5011;DOI 10.17487/RFC5011;September;https://www.rfc-editor.org/info/rfc5011 | |
| RFC5012;;Schulzrinne, H. and R. Marshall, Ed.;Requirements for Emergency Context Resolution with Internet Technologies;;;;;RFC 5012;DOI 10.17487/RFC5012;January;https://www.rfc-editor.org/info/rfc5012 | |
| RFC5013;;Kunze, J. and T. Baker;The Dublin Core Metadata Element Set;;;;;RFC 5013;DOI 10.17487/RFC5013;August;https://www.rfc-editor.org/info/rfc5013 | |
| RFC5014;;Nordmark, E., Chakrabarti, S., and J. Laganier;IPv6 Socket API for Source Address Selection;;;;;RFC 5014;DOI 10.17487/RFC5014;September;https://www.rfc-editor.org/info/rfc5014 | |
| RFC5015;;Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano;Bidirectional Protocol Independent Multicast (BIDIR-PIM);;;;;RFC 5015;DOI 10.17487/RFC5015;October;https://www.rfc-editor.org/info/rfc5015 | |
| RFC5016;;Thomas, M.;Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol;;;;;RFC 5016;DOI 10.17487/RFC5016;October;https://www.rfc-editor.org/info/rfc5016 | |
| RFC5017;;McWalter, D., Ed.;MIB Textual Conventions for Uniform Resource Identifiers (URIs);;;;;RFC 5017;DOI 10.17487/RFC5017;September;https://www.rfc-editor.org/info/rfc5017 | |
| RFC5018;;Camarillo, G.;Connection Establishment in the Binary Floor Control Protocol (BFCP);;;;;RFC 5018;DOI 10.17487/RFC5018;September;https://www.rfc-editor.org/info/rfc5018 | |
| RFC5019;;Deacon, A. and R. Hurst;The Lightweight Online Certificate Status Protocol (OCSP) Profile for High-Volume Environments;;;;;RFC 5019;DOI 10.17487/RFC5019;September;https://www.rfc-editor.org/info/rfc5019 | |
| RFC5020;;Zeilenga, K.;The Lightweight Directory Access Protocol (LDAP) entryDN Operational Attribute;;;;;RFC 5020;DOI 10.17487/RFC5020;August;https://www.rfc-editor.org/info/rfc5020 | |
| RFC5021;;Josefsson, S.;Extended Kerberos Version 5 Key Distribution Center (KDC) Exchanges over TCP;;;;;RFC 5021;DOI 10.17487/RFC5021;August;https://www.rfc-editor.org/info/rfc5021 | |
| RFC5022;;Van Dyke, J., Burger, E., Ed., and A. Spitzer;Media Server Control Markup Language (MSCML) and Protocol;;;;;RFC 5022;DOI 10.17487/RFC5022;September;https://www.rfc-editor.org/info/rfc5022 | |
| RFC5023;;Gregorio, J., Ed., and B. de hOra, Ed.;The Atom Publishing Protocol;;;;;RFC 5023;DOI 10.17487/RFC5023;October;https://www.rfc-editor.org/info/rfc5023 | |
| RFC5024;;Friend, I.;ODETTE File Transfer Protocol 2.0;;;;;RFC 5024;DOI 10.17487/RFC5024;November;https://www.rfc-editor.org/info/rfc5024 | |
| RFC5025;;Rosenberg, J.;Presence Authorization Rules;;;;;RFC 5025;DOI 10.17487/RFC5025;December;https://www.rfc-editor.org/info/rfc5025 | |
| RFC5026;;Giaretta, G., Ed., Kempf, J., and V. Devarapalli, Ed.;Mobile IPv6 Bootstrapping in Split Scenario;;;;;RFC 5026;DOI 10.17487/RFC5026;October;https://www.rfc-editor.org/info/rfc5026 | |
| RFC5027;;Andreasen, F. and D. Wing;Security Preconditions for Session Description Protocol (SDP) Media Streams;;;;;RFC 5027;DOI 10.17487/RFC5027;October;https://www.rfc-editor.org/info/rfc5027 | |
| RFC5028;;Mahy, R.;A Telephone Number Mapping (ENUM) Service Registration for Instant Messaging (IM) Services;;;;;RFC 5028;DOI 10.17487/RFC5028;October;https://www.rfc-editor.org/info/rfc5028 | |
| RFC5029;;Vasseur, JP. and S. Previdi;Definition of an IS-IS Link Attribute Sub-TLV;;;;;RFC 5029;DOI 10.17487/RFC5029;September;https://www.rfc-editor.org/info/rfc5029 | |
| RFC5030;;Nakhjiri, M., Ed., Chowdhury, K., Lior, A., and K. Leung;Mobile IPv4 RADIUS Requirements;;;;;RFC 5030;DOI 10.17487/RFC5030;October;https://www.rfc-editor.org/info/rfc5030 | |
| RFC5031;;Schulzrinne, H.;A Uniform Resource Name (URN) for Emergency and Other Well-Known Services;;;;;RFC 5031;DOI 10.17487/RFC5031;January;https://www.rfc-editor.org/info/rfc5031 | |
| RFC5032;;Burger, E., Ed.;WITHIN Search Extension to the IMAP Protocol;;;;;RFC 5032;DOI 10.17487/RFC5032;September;https://www.rfc-editor.org/info/rfc5032 | |
| RFC5033;;Floyd, S. and M. Allman;Specifying New Congestion Control Algorithms;;;BCP 133;;RFC 5033;DOI 10.17487/RFC5033;August;https://www.rfc-editor.org/info/rfc5033 | |
| RFC5034;;Siemborski, R. and A. Menon-Sen;The Post Office Protocol (POP3) Simple Authentication and Security Layer (SASL) Authentication Mechanism;;;;;RFC 5034;DOI 10.17487/RFC5034;July;https://www.rfc-editor.org/info/rfc5034 | |
| RFC5035;;Schaad, J.;Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility;;;;;RFC 5035;DOI 10.17487/RFC5035;August;https://www.rfc-editor.org/info/rfc5035 | |
| RFC5036;;Andersson, L., Ed., Minei, I., Ed., and B. Thomas, Ed.;LDP Specification;;;;;RFC 5036;DOI 10.17487/RFC5036;October;https://www.rfc-editor.org/info/rfc5036 | |
| RFC5037;;Andersson, L., Ed., Minei, I., Ed., and B. Thomas, Ed.;Experience with the Label Distribution Protocol (LDP);;;;;RFC 5037;DOI 10.17487/RFC5037;October;https://www.rfc-editor.org/info/rfc5037 | |
| RFC5038;;Thomas, B. and L. Andersson;The Label Distribution Protocol (LDP) Implementation Survey Results;;;;;RFC 5038;DOI 10.17487/RFC5038;October;https://www.rfc-editor.org/info/rfc5038 | |
| RFC5039;;Rosenberg, J. and C. Jennings;The Session Initiation Protocol (SIP) and Spam;;;;;RFC 5039;DOI 10.17487/RFC5039;January;https://www.rfc-editor.org/info/rfc5039 | |
| RFC5040;;Recio, R., Metzler, B., Culley, P., Hilland, J., and D. Garcia;A Remote Direct Memory Access Protocol Specification;;;;;RFC 5040;DOI 10.17487/RFC5040;October;https://www.rfc-editor.org/info/rfc5040 | |
| RFC5041;;Shah, H., Pinkerton, J., Recio, R., and P. Culley;Direct Data Placement over Reliable Transports;;;;;RFC 5041;DOI 10.17487/RFC5041;October;https://www.rfc-editor.org/info/rfc5041 | |
| RFC5042;;Pinkerton, J. and E. Deleganes;Direct Data Placement Protocol (DDP) / Remote Direct Memory Access Protocol (RDMAP) Security;;;;;RFC 5042;DOI 10.17487/RFC5042;October;https://www.rfc-editor.org/info/rfc5042 | |
| RFC5043;;Bestler, C., Ed., and R. Stewart, Ed.;Stream Control Transmission Protocol (SCTP) Direct Data Placement (DDP) Adaptation;;;;;RFC 5043;DOI 10.17487/RFC5043;October;https://www.rfc-editor.org/info/rfc5043 | |
| RFC5044;;Culley, P., Elzur, U., Recio, R., Bailey, S., and J. Carrier;Marker PDU Aligned Framing for TCP Specification;;;;;RFC 5044;DOI 10.17487/RFC5044;October;https://www.rfc-editor.org/info/rfc5044 | |
| RFC5045;;Bestler, C., Ed., and L. Coene;Applicability of Remote Direct Memory Access Protocol (RDMA) and Direct Data Placement (DDP);;;;;RFC 5045;DOI 10.17487/RFC5045;October;https://www.rfc-editor.org/info/rfc5045 | |
| RFC5046;RFC7145;Ko, M., Chadalapaka, M., Hufferd, J., Elzur, U., Shah, H., and P. Thaler;Internet Small Computer System Interface (iSCSI) Extensions for Remote Direct Memory Access (RDMA);;;;;RFC 5046;DOI 10.17487/RFC5046;October;https://www.rfc-editor.org/info/rfc5046 | |
| RFC5047;;Chadalapaka, M., Hufferd, J., Satran, J., and H. Shah;DA: Datamover Architecture for the Internet Small Computer System Interface (iSCSI);;;;;RFC 5047;DOI 10.17487/RFC5047;October;https://www.rfc-editor.org/info/rfc5047 | |
| RFC5048;RFC7143;Chadalapaka, M., Ed.;Internet Small Computer System Interface (iSCSI) Corrections and Clarifications;;;;;RFC 5048;DOI 10.17487/RFC5048;October;https://www.rfc-editor.org/info/rfc5048 | |
| RFC5049;;Bormann, C., Liu, Z., Price, R., and G. Camarillo, Ed.;Applying Signaling Compression (SigComp) to the Session Initiation Protocol (SIP);;;;;RFC 5049;DOI 10.17487/RFC5049;December;https://www.rfc-editor.org/info/rfc5049 | |
| RFC5050;;Scott, K. and S. Burleigh;Bundle Protocol Specification;;;;;RFC 5050;DOI 10.17487/RFC5050;November;https://www.rfc-editor.org/info/rfc5050 | |
| RFC5051;;Crispin, M.;i;unicode-casemap - Simple Unicode Collation Algorithm;;;;;RFC 5051;DOI 10.17487/RFC5051;October;https://www.rfc-editor.org/info/rfc5051 | |
| RFC5052;;Watson, M., Luby, M., and L. Vicisano;Forward Error Correction (FEC) Building Block;;;;;RFC 5052;DOI 10.17487/RFC5052;August;https://www.rfc-editor.org/info/rfc5052 | |
| RFC5053;;Luby, M., Shokrollahi, A., Watson, M., and T. Stockhammer;Raptor Forward Error Correction Scheme for Object Delivery;;;;;RFC 5053;DOI 10.17487/RFC5053;October;https://www.rfc-editor.org/info/rfc5053 | |
| RFC5054;;Taylor, D., Wu, T., Mavrogiannopoulos, N., and T. Perrin;Using the Secure Remote Password (SRP) Protocol for TLS Authentication;;;;;RFC 5054;DOI 10.17487/RFC5054;November;https://www.rfc-editor.org/info/rfc5054 | |
| RFC5055;;Freeman, T., Housley, R., Malpani, A., Cooper, D., and W. Polk;Server-Based Certificate Validation Protocol (SCVP);;;;;RFC 5055;DOI 10.17487/RFC5055;December;https://www.rfc-editor.org/info/rfc5055 | |
| RFC5056;;Williams, N.;On the Use of Channel Bindings to Secure Channels;;;;;RFC 5056;DOI 10.17487/RFC5056;November;https://www.rfc-editor.org/info/rfc5056 | |
| RFC5057;;Sparks, R.;Multiple Dialog Usages in the Session Initiation Protocol;;;;;RFC 5057;DOI 10.17487/RFC5057;November;https://www.rfc-editor.org/info/rfc5057 | |
| RFC5058;;Boivie, R., Feldman, N., Imai, Y., Livens, W., and D. Ooms;Explicit Multicast (Xcast) Concepts and Options;;;;;RFC 5058;DOI 10.17487/RFC5058;November;https://www.rfc-editor.org/info/rfc5058 | |
| RFC5059;;Bhaskar, N., Gall, A., Lingard, J., and S. Venaas;Bootstrap Router (BSR) Mechanism for Protocol Independent Multicast (PIM);;;;;RFC 5059;DOI 10.17487/RFC5059;January;https://www.rfc-editor.org/info/rfc5059 | |
| RFC5060;;Sivaramu, R., Lingard, J., McWalter, D., Joshi, B., and A. Kessler;Protocol Independent Multicast MIB;;;;;RFC 5060;DOI 10.17487/RFC5060;January;https://www.rfc-editor.org/info/rfc5060 | |
| RFC5061;;Stewart, R., Xie, Q., Tuexen, M., Maruyama, S., and M. Kozuka;Stream Control Transmission Protocol (SCTP) Dynamic Address Reconfiguration;;;;;RFC 5061;DOI 10.17487/RFC5061;September;https://www.rfc-editor.org/info/rfc5061 | |
| RFC5062;;Stewart, R., Tuexen, M., and G. Camarillo;Security Attacks Found Against the Stream Control Transmission Protocol (SCTP) and Current Countermeasures;;;;;RFC 5062;DOI 10.17487/RFC5062;September;https://www.rfc-editor.org/info/rfc5062 | |
| RFC5063;;Satyanarayana, A., Ed., and R. Rahman, Ed.;Extensions to GMPLS Resource Reservation Protocol (RSVP) Graceful Restart;;;;;RFC 5063;DOI 10.17487/RFC5063;October;https://www.rfc-editor.org/info/rfc5063 | |
| RFC5064;;Duerst, M.;The Archived-At Message Header Field;;;;;RFC 5064;DOI 10.17487/RFC5064;December;https://www.rfc-editor.org/info/rfc5064 | |
| RFC5065;;Traina, P., McPherson, D., and J. Scudder;Autonomous System Confederations for BGP;;;;;RFC 5065;DOI 10.17487/RFC5065;August;https://www.rfc-editor.org/info/rfc5065 | |
| RFC5066;;Beili, E.;Ethernet in the First Mile Copper (EFMCu) Interfaces MIB;;;;;RFC 5066;DOI 10.17487/RFC5066;November;https://www.rfc-editor.org/info/rfc5066 | |
| RFC5067;;Lind, S. and P. Pfautz;Infrastructure ENUM Requirements;;;;;RFC 5067;DOI 10.17487/RFC5067;November;https://www.rfc-editor.org/info/rfc5067 | |
| RFC5068;;Hutzler, C., Crocker, D., Resnick, P., Allman, E., and T. Finch;Email Submission Operations: Access and Accountability Requirements;;;BCP 134;;RFC 5068;DOI 10.17487/RFC5068;November;https://www.rfc-editor.org/info/rfc5068 | |
| RFC5069;;Taylor, T., Ed., Tschofenig, H., Schulzrinne, H., and M. Shanmugam;Security Threats and Requirements for Emergency Call Marking and Mapping;;;;;RFC 5069;DOI 10.17487/RFC5069;January;https://www.rfc-editor.org/info/rfc5069 | |
| RFC5070;RFC7970;Danyliw, R., Meijer, J., and Y. Demchenko;The Incident Object Description Exchange Format;;;;;RFC 5070;DOI 10.17487/RFC5070;December;https://www.rfc-editor.org/info/rfc5070 | |
| RFC5071;;Hankins, D.;Dynamic Host Configuration Protocol Options Used by PXELINUX;;;;;RFC 5071;DOI 10.17487/RFC5071;December;https://www.rfc-editor.org/info/rfc5071 | |
| RFC5072;;Varada, S., Ed., Haskins, D., and E. Allen;IP Version 6 over PPP;;;;;RFC 5072;DOI 10.17487/RFC5072;September;https://www.rfc-editor.org/info/rfc5072 | |
| RFC5073;;Vasseur, J., Ed., and J. Le Roux, Ed.;IGP Routing Protocol Extensions for Discovery of Traffic Engineering Node Capabilities;;;;;RFC 5073;DOI 10.17487/RFC5073;December;https://www.rfc-editor.org/info/rfc5073 | |
| RFC5074;;Weiler, S.;DNSSEC Lookaside Validation (DLV);;;;;RFC 5074;DOI 10.17487/RFC5074;November;https://www.rfc-editor.org/info/rfc5074 | |
| RFC5075;RFC5175;Haberman, B., Ed., and R. Hinden;IPv6 Router Advertisement Flags Option;;;;;RFC 5075;DOI 10.17487/RFC5075;November;https://www.rfc-editor.org/info/rfc5075 | |
| RFC5076;;Hoeneisen, B.;ENUM Validation Information Mapping for the Extensible Provisioning Protocol;;;;;RFC 5076;DOI 10.17487/RFC5076;December;https://www.rfc-editor.org/info/rfc5076 | |
| RFC5077;RFC8446;Salowey, J., Zhou, H., Eronen, P., and H. Tschofenig;Transport Layer Security (TLS) Session Resumption without Server-Side State;;;;;RFC 5077;DOI 10.17487/RFC5077;January;https://www.rfc-editor.org/info/rfc5077 | |
| RFC5078;RFC7437;Dawkins, S.;IAB and IESG Selection, Confirmation, and Recall Process: Revision of the Nominating and Recall Committees Timeline;;;;;RFC 5078;DOI 10.17487/RFC5078;October;https://www.rfc-editor.org/info/rfc5078 | |
| RFC5079;;Rosenberg, J.;Rejecting Anonymous Requests in the Session Initiation Protocol (SIP);;;;;RFC 5079;DOI 10.17487/RFC5079;December;https://www.rfc-editor.org/info/rfc5079 | |
| RFC5080;;Nelson, D. and A. DeKok;Common Remote Authentication Dial In User Service (RADIUS) Implementation Issues and Suggested Fixes;;;;;RFC 5080;DOI 10.17487/RFC5080;December;https://www.rfc-editor.org/info/rfc5080 | |
| RFC5081;RFC6091;Mavrogiannopoulos, N.;Using OpenPGP Keys for Transport Layer Security (TLS) Authentication;;;;;RFC 5081;DOI 10.17487/RFC5081;November;https://www.rfc-editor.org/info/rfc5081 | |
| RFC5082;;Gill, V., Heasley, J., Meyer, D., Savola, P., Ed., and C. Pignataro;The Generalized TTL Security Mechanism (GTSM);;;;;RFC 5082;DOI 10.17487/RFC5082;October;https://www.rfc-editor.org/info/rfc5082 | |
| RFC5083;;Housley, R.;Cryptographic Message Syntax (CMS) Authenticated-Enveloped-Data Content Type;;;;;RFC 5083;DOI 10.17487/RFC5083;November;https://www.rfc-editor.org/info/rfc5083 | |
| RFC5084;;Housley, R.;Using AES-CCM and AES-GCM Authenticated Encryption in the Cryptographic Message Syntax (CMS);;;;;RFC 5084;DOI 10.17487/RFC5084;November;https://www.rfc-editor.org/info/rfc5084 | |
| RFC5085;;Nadeau, T., Ed., and C. Pignataro, Ed.;Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires;;;;;RFC 5085;DOI 10.17487/RFC5085;December;https://www.rfc-editor.org/info/rfc5085 | |
| RFC5086;;Vainshtein, A., Ed., Sasson, I., Metz, E., Frost, T., and P. Pate;Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation Service over Packet Switched Network (CESoPSN);;;;;RFC 5086;DOI 10.17487/RFC5086;December;https://www.rfc-editor.org/info/rfc5086 | |
| RFC5087;;Y(J). Stein, Shashoua, R., Insler, R., and M. Anavi;Time Division Multiplexing over IP (TDMoIP);;;;;RFC 5087;DOI 10.17487/RFC5087;December;https://www.rfc-editor.org/info/rfc5087 | |
| RFC5088;;Le Roux, JL., Ed., Vasseur, JP., Ed., Ikejiri, Y., and R. Zhang;OSPF Protocol Extensions for Path Computation Element (PCE) Discovery;;;;;RFC 5088;DOI 10.17487/RFC5088;January;https://www.rfc-editor.org/info/rfc5088 | |
| RFC5089;;Le Roux, JL., Ed., Vasseur, JP., Ed., Ikejiri, Y., and R. Zhang;IS-IS Protocol Extensions for Path Computation Element (PCE) Discovery;;;;;RFC 5089;DOI 10.17487/RFC5089;January;https://www.rfc-editor.org/info/rfc5089 | |
| RFC5090;;Sterman, B., Sadolevsky, D., Schwartz, D., Williams, D., and W. Beck;RADIUS Extension for Digest Authentication;;;;;RFC 5090;DOI 10.17487/RFC5090;February;https://www.rfc-editor.org/info/rfc5090 | |
| RFC5091;;Boyen, X. and L. Martin;Identity-Based Cryptography Standard (IBCS) #1: Supersingular Curve Implementations of the BF and BB1 Cryptosystems;;;;;RFC 5091;DOI 10.17487/RFC5091;December;https://www.rfc-editor.org/info/rfc5091 | |
| RFC5092;;Melnikov, A., Ed., and C. Newman;IMAP URL Scheme;;;;;RFC 5092;DOI 10.17487/RFC5092;November;https://www.rfc-editor.org/info/rfc5092 | |
| RFC5093;;Hunt, G.;BT's eXtended Network Quality RTP Control Protocol Extended Reports (RTCP XR XNQ);;;;;RFC 5093;DOI 10.17487/RFC5093;December;https://www.rfc-editor.org/info/rfc5093 | |
| RFC5094;;Devarapalli, V., Patel, A., and K. Leung;Mobile IPv6 Vendor Specific Option;;;;;RFC 5094;DOI 10.17487/RFC5094;December;https://www.rfc-editor.org/info/rfc5094 | |
| RFC5095;;Abley, J., Savola, P., and G. Neville-Neil;Deprecation of Type 0 Routing Headers in IPv6;;;;;RFC 5095;DOI 10.17487/RFC5095;December;https://www.rfc-editor.org/info/rfc5095 | |
| RFC5096;;Devarapalli, V.;Mobile IPv6 Experimental Messages;;;;;RFC 5096;DOI 10.17487/RFC5096;December;https://www.rfc-editor.org/info/rfc5096 | |
| RFC5097;;Renker, G. and G. Fairhurst;MIB for the UDP-Lite protocol;;;;;RFC 5097;DOI 10.17487/RFC5097;January;https://www.rfc-editor.org/info/rfc5097 | |
| RFC5098;;Beacham, G., Kumar, S., and S. Channabasappa;Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs);;;;;RFC 5098;DOI 10.17487/RFC5098;February;https://www.rfc-editor.org/info/rfc5098 | |
| RFC5101;RFC7011;Claise, B., Ed.;Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information;;;;;RFC 5101;DOI 10.17487/RFC5101;January;https://www.rfc-editor.org/info/rfc5101 | |
| RFC5102;RFC7012;Quittek, J., Bryant, S., Claise, B., Aitken, P., and J. Meyer;Information Model for IP Flow Information Export;;;;;RFC 5102;DOI 10.17487/RFC5102;January;https://www.rfc-editor.org/info/rfc5102 | |
| RFC5103;;Trammell, B. and E. Boschi;Bidirectional Flow Export Using IP Flow Information Export (IPFIX);;;;;RFC 5103;DOI 10.17487/RFC5103;January;https://www.rfc-editor.org/info/rfc5103 | |
| RFC5104;;Wenger, S., Chandra, U., Westerlund, M., and B. Burman;Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF);;;;;RFC 5104;DOI 10.17487/RFC5104;February;https://www.rfc-editor.org/info/rfc5104 | |
| RFC5105;;Lendl, O.;ENUM Validation Token Format Definition;;;;;RFC 5105;DOI 10.17487/RFC5105;December;https://www.rfc-editor.org/info/rfc5105 | |
| RFC5106;;Tschofenig, H., Kroeselberg, D., Pashalidis, A., Ohba, Y., and F. Bersani;The Extensible Authentication Protocol-Internet Key Exchange Protocol version 2 (EAP-IKEv2) Method;;;;;RFC 5106;DOI 10.17487/RFC5106;February;https://www.rfc-editor.org/info/rfc5106 | |
| RFC5107;;Johnson, R., Kumarasamy, J., Kinnear, K., and M. Stapp;DHCP Server Identifier Override Suboption;;;;;RFC 5107;DOI 10.17487/RFC5107;February;https://www.rfc-editor.org/info/rfc5107 | |
| RFC5109;;Li, A., Ed.;RTP Payload Format for Generic Forward Error Correction;;;;;RFC 5109;DOI 10.17487/RFC5109;December;https://www.rfc-editor.org/info/rfc5109 | |
| RFC5110;;Savola, P.;Overview of the Internet Multicast Routing Architecture;;;;;RFC 5110;DOI 10.17487/RFC5110;January;https://www.rfc-editor.org/info/rfc5110 | |
| RFC5111;;Aboba, B. and L. Dondeti;Experiment in Exploratory Group Formation within the Internet Engineering Task Force (IETF);;;;;RFC 5111;DOI 10.17487/RFC5111;January;https://www.rfc-editor.org/info/rfc5111 | |
| RFC5112;;Garcia-Martin, M.;The Presence-Specific Static Dictionary for Signaling Compression (Sigcomp);;;;;RFC 5112;DOI 10.17487/RFC5112;January;https://www.rfc-editor.org/info/rfc5112 | |
| RFC5113;;Arkko, J., Aboba, B., Korhonen, J., Ed., and F. Bari;Network Discovery and Selection Problem;;;;;RFC 5113;DOI 10.17487/RFC5113;January;https://www.rfc-editor.org/info/rfc5113 | |
| RFC5114;;Lepinski, M. and S. Kent;Additional Diffie-Hellman Groups for Use with IETF Standards;;;;;RFC 5114;DOI 10.17487/RFC5114;January;https://www.rfc-editor.org/info/rfc5114 | |
| RFC5115;;Carlberg, K. and P. O'Hanlon;Telephony Routing over IP (TRIP) Attribute for Resource Priority;;;;;RFC 5115;DOI 10.17487/RFC5115;January;https://www.rfc-editor.org/info/rfc5115 | |
| RFC5116;;McGrew, D.;An Interface and Algorithms for Authenticated Encryption;;;;;RFC 5116;DOI 10.17487/RFC5116;January;https://www.rfc-editor.org/info/rfc5116 | |
| RFC5117;RFC7667;Westerlund, M. and S. Wenger;RTP Topologies;;;;;RFC 5117;DOI 10.17487/RFC5117;January;https://www.rfc-editor.org/info/rfc5117 | |
| RFC5118;;Gurbani, V., Boulton, C., and R. Sparks;Session Initiation Protocol (SIP) Torture Test Messages for Internet Protocol Version 6 (IPv6);;;;;RFC 5118;DOI 10.17487/RFC5118;February;https://www.rfc-editor.org/info/rfc5118 | |
| RFC5119;;Edwards, T.;A Uniform Resource Name (URN) Namespace for the Society of Motion Picture and Television Engineers (SMPTE);;;;;RFC 5119;DOI 10.17487/RFC5119;February;https://www.rfc-editor.org/info/rfc5119 | |
| RFC5120;;Przygienda, T., Shen, N., and N. Sheth;M-ISIS: Multi Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs);;;;;RFC 5120;DOI 10.17487/RFC5120;February;https://www.rfc-editor.org/info/rfc5120 | |
| RFC5121;;Patil, B., Xia, F., Sarikaya, B., Choi, JH., and S. Madanapalli;Transmission of IPv6 via the IPv6 Convergence Sublayer over IEEE 802.16 Networks;;;;;RFC 5121;DOI 10.17487/RFC5121;February;https://www.rfc-editor.org/info/rfc5121 | |
| RFC5122;;Saint-Andre, P.;Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP);;;;;RFC 5122;DOI 10.17487/RFC5122;February;https://www.rfc-editor.org/info/rfc5122 | |
| RFC5123;;White, R. and B. Akyol;Considerations in Validating the Path in BGP;;;;;RFC 5123;DOI 10.17487/RFC5123;February;https://www.rfc-editor.org/info/rfc5123 | |
| RFC5124;;Ott, J. and E. Carrara;Extended Secure RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/SAVPF);;;;;RFC 5124;DOI 10.17487/RFC5124;February;https://www.rfc-editor.org/info/rfc5124 | |
| RFC5125;;Taylor, T.;Reclassification of RFC 3525 to Historic;;;;;RFC 5125;DOI 10.17487/RFC5125;February;https://www.rfc-editor.org/info/rfc5125 | |
| RFC5126;;Pinkas, D., Pope, N., and J. Ross;CMS Advanced Electronic Signatures (CAdES);;;;;RFC 5126;DOI 10.17487/RFC5126;March;https://www.rfc-editor.org/info/rfc5126 | |
| RFC5127;;Chan, K., Babiarz, J., and F. Baker;Aggregation of Diffserv Service Classes;;;;;RFC 5127;DOI 10.17487/RFC5127;February;https://www.rfc-editor.org/info/rfc5127 | |
| RFC5128;;Srisuresh, P., Ford, B., and D. Kegel;State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs);;;;;RFC 5128;DOI 10.17487/RFC5128;March;https://www.rfc-editor.org/info/rfc5128 | |
| RFC5129;;Davie, B., Briscoe, B., and J. Tay;Explicit Congestion Marking in MPLS;;;;;RFC 5129;DOI 10.17487/RFC5129;January;https://www.rfc-editor.org/info/rfc5129 | |
| RFC5130;;Previdi, S., Shand, M., Ed., and C. Martin;A Policy Control Mechanism in IS-IS Using Administrative Tags;;;;;RFC 5130;DOI 10.17487/RFC5130;February;https://www.rfc-editor.org/info/rfc5130 | |
| RFC5131;;McWalter, D., Ed.;A MIB Textual Convention for Language Tags;;;;;RFC 5131;DOI 10.17487/RFC5131;December;https://www.rfc-editor.org/info/rfc5131 | |
| RFC5132;;McWalter, D., Thaler, D., and A. Kessler;IP Multicast MIB;;;;;RFC 5132;DOI 10.17487/RFC5132;December;https://www.rfc-editor.org/info/rfc5132 | |
| RFC5133;;Tuexen, M. and K. Morneault;Terminal Endpoint Identifier (TEI) Query Request Number Change;;;;;RFC 5133;DOI 10.17487/RFC5133;December;https://www.rfc-editor.org/info/rfc5133 | |
| RFC5134;;Mealling, M.;A Uniform Resource Name Namespace for the EPCglobal Electronic Product Code (EPC) and Related Standards;;;;;RFC 5134;DOI 10.17487/RFC5134;January;https://www.rfc-editor.org/info/rfc5134 | |
| RFC5135;;Wing, D. and T. Eckert;IP Multicast Requirements for a Network Address Translator (NAT) and a Network Address Port Translator (NAPT);;;BCP 135;;RFC 5135;DOI 10.17487/RFC5135;February;https://www.rfc-editor.org/info/rfc5135 | |
| RFC5136;;Chimento, P. and J. Ishac;Defining Network Capacity;;;;;RFC 5136;DOI 10.17487/RFC5136;February;https://www.rfc-editor.org/info/rfc5136 | |
| RFC5137;;Klensin, J.;ASCII Escaping of Unicode Characters;;;BCP 137;;RFC 5137;DOI 10.17487/RFC5137;February;https://www.rfc-editor.org/info/rfc5137 | |
| RFC5138;;Cox, S.;A Uniform Resource Name (URN) Namespace for the Commission for the Management and Application of Geoscience Information (CGI);;;;;RFC 5138;DOI 10.17487/RFC5138;February;https://www.rfc-editor.org/info/rfc5138 | |
| RFC5139;;Thomson, M. and J. Winterbottom;Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO);;;;;RFC 5139;DOI 10.17487/RFC5139;February;https://www.rfc-editor.org/info/rfc5139 | |
| RFC5140;;Bangalore, M., Kumar, R., Rosenberg, J., Salama, H., and D. Shah;A Telephony Gateway REgistration Protocol (TGREP);;;;;RFC 5140;DOI 10.17487/RFC5140;March;https://www.rfc-editor.org/info/rfc5140 | |
| RFC5141;;Goodwin, J. and H. Apel;A Uniform Resource Name (URN) Namespace for the International Organization for Standardization (ISO);;;;;RFC 5141;DOI 10.17487/RFC5141;March;https://www.rfc-editor.org/info/rfc5141 | |
| RFC5142;;Haley, B., Devarapalli, V., Deng, H., and J. Kempf;Mobility Header Home Agent Switch Message;;;;;RFC 5142;DOI 10.17487/RFC5142;January;https://www.rfc-editor.org/info/rfc5142 | |
| RFC5143;RFC4842;Malis, A., Brayley, J., Shirron, J., Martini, L., and S. Vogelsang;Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation Service over MPLS (CEM) Encapsulation;;;;;RFC 5143;DOI 10.17487/RFC5143;February;https://www.rfc-editor.org/info/rfc5143 | |
| RFC5144;;Newton, A. and M. Sanz;A Domain Availability Check (DCHK) Registry Type for the Internet Registry Information Service (IRIS);;;;;RFC 5144;DOI 10.17487/RFC5144;February;https://www.rfc-editor.org/info/rfc5144 | |
| RFC5145;;Shiomoto, K., Ed.;Framework for MPLS-TE to GMPLS Migration;;;;;RFC 5145;DOI 10.17487/RFC5145;March;https://www.rfc-editor.org/info/rfc5145 | |
| RFC5146;;Kumaki, K., Ed.;Interworking Requirements to Support Operation of MPLS-TE over GMPLS Networks;;;;;RFC 5146;DOI 10.17487/RFC5146;March;https://www.rfc-editor.org/info/rfc5146 | |
| RFC5147;;Wilde, E. and M. Duerst;URI Fragment Identifiers for the text/plain Media Type;;;;;RFC 5147;DOI 10.17487/RFC5147;April;https://www.rfc-editor.org/info/rfc5147 | |
| RFC5148;;Clausen, T., Dearlove, C., and B. Adamson;Jitter Considerations in Mobile Ad Hoc Networks (MANETs);;;;;RFC 5148;DOI 10.17487/RFC5148;February;https://www.rfc-editor.org/info/rfc5148 | |
| RFC5149;;Korhonen, J., Nilsson, U., and V. Devarapalli;Service Selection for Mobile IPv6;;;;;RFC 5149;DOI 10.17487/RFC5149;February;https://www.rfc-editor.org/info/rfc5149 | |
| RFC5150;;Ayyangar, A., Kompella, K., Vasseur, JP., and A. Farrel;Label Switched Path Stitching with Generalized Multiprotocol Label Switching Traffic Engineering (GMPLS TE);;;;;RFC 5150;DOI 10.17487/RFC5150;February;https://www.rfc-editor.org/info/rfc5150 | |
| RFC5151;;Farrel, A., Ed., Ayyangar, A., and JP. Vasseur;Inter-Domain MPLS and GMPLS Traffic Engineering -- Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions;;;;;RFC 5151;DOI 10.17487/RFC5151;February;https://www.rfc-editor.org/info/rfc5151 | |
| RFC5152;;Vasseur, JP., Ed., Ayyangar, A., Ed., and R. Zhang;A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs);;;;;RFC 5152;DOI 10.17487/RFC5152;February;https://www.rfc-editor.org/info/rfc5152 | |
| RFC5153;;Boschi, E., Mark, L., Quittek, J., Stiemerling, M., and P. Aitken;IP Flow Information Export (IPFIX) Implementation Guidelines;;;;;RFC 5153;DOI 10.17487/RFC5153;April;https://www.rfc-editor.org/info/rfc5153 | |
| RFC5154;;Jee, J., Ed., Madanapalli, S., and J. Mandin;IP over IEEE 802.16 Problem Statement and Goals;;;;;RFC 5154;DOI 10.17487/RFC5154;April;https://www.rfc-editor.org/info/rfc5154 | |
| RFC5155;;Laurie, B., Sisson, G., Arends, R., and D. Blacka;DNS Security (DNSSEC) Hashed Authenticated Denial of Existence;;;;;RFC 5155;DOI 10.17487/RFC5155;March;https://www.rfc-editor.org/info/rfc5155 | |
| RFC5156;RFC6890;Blanchet, M.;Special-Use IPv6 Addresses;;;;;RFC 5156;DOI 10.17487/RFC5156;April;https://www.rfc-editor.org/info/rfc5156 | |
| RFC5157;RFC7707;Chown, T.;IPv6 Implications for Network Scanning;;;;;RFC 5157;DOI 10.17487/RFC5157;March;https://www.rfc-editor.org/info/rfc5157 | |
| RFC5158;;Huston, G.;6to4 Reverse DNS Delegation Specification;;;;;RFC 5158;DOI 10.17487/RFC5158;March;https://www.rfc-editor.org/info/rfc5158 | |
| RFC5159;;Dondeti, L., Ed., and A. Jerichow;Session Description Protocol (SDP) Attributes for Open Mobile Alliance (OMA) Broadcast (BCAST) Service and Content Protection;;;;;RFC 5159;DOI 10.17487/RFC5159;March;https://www.rfc-editor.org/info/rfc5159 | |
| RFC5160;;Levis, P. and M. Boucadair;Considerations of Provider-to-Provider Agreements for Internet-Scale Quality of Service (QoS);;;;;RFC 5160;DOI 10.17487/RFC5160;March;https://www.rfc-editor.org/info/rfc5160 | |
| RFC5161;;Gulbrandsen, A., Ed., and A. Melnikov, Ed.;The IMAP ENABLE Extension;;;;;RFC 5161;DOI 10.17487/RFC5161;March;https://www.rfc-editor.org/info/rfc5161 | |
| RFC5162;RFC7162;Melnikov, A., Cridland, D., and C. Wilson;IMAP4 Extensions for Quick Mailbox Resynchronization;;;;;RFC 5162;DOI 10.17487/RFC5162;March;https://www.rfc-editor.org/info/rfc5162 | |
| RFC5163;;Fairhurst, G. and B. Collini-Nocker;Extension Formats for Unidirectional Lightweight Encapsulation (ULE) and the Generic Stream Encapsulation (GSE);;;;;RFC 5163;DOI 10.17487/RFC5163;April;https://www.rfc-editor.org/info/rfc5163 | |
| RFC5164;;Melia, T., Ed.;Mobility Services Transport: Problem Statement;;;;;RFC 5164;DOI 10.17487/RFC5164;March;https://www.rfc-editor.org/info/rfc5164 | |
| RFC5165;;Reed, C.;A Uniform Resource Name (URN) Namespace for the Open Geospatial Consortium (OGC);;;;;RFC 5165;DOI 10.17487/RFC5165;April;https://www.rfc-editor.org/info/rfc5165 | |
| RFC5166;;Floyd, S., Ed.;Metrics for the Evaluation of Congestion Control Mechanisms;;;;;RFC 5166;DOI 10.17487/RFC5166;March;https://www.rfc-editor.org/info/rfc5166 | |
| RFC5167;;Dolly, M. and R. Even;Media Server Control Protocol Requirements;;;;;RFC 5167;DOI 10.17487/RFC5167;March;https://www.rfc-editor.org/info/rfc5167 | |
| RFC5168;;Levin, O., Even, R., and P. Hagendorf;XML Schema for Media Control;;;;;RFC 5168;DOI 10.17487/RFC5168;March;https://www.rfc-editor.org/info/rfc5168 | |
| RFC5169;;Clancy, T., Nakhjiri, M., Narayanan, V., and L. Dondeti;Handover Key Management and Re-Authentication Problem Statement;;;;;RFC 5169;DOI 10.17487/RFC5169;March;https://www.rfc-editor.org/info/rfc5169 | |
| RFC5170;;Roca, V., Neumann, C., and D. Furodet;Low Density Parity Check (LDPC) Staircase and Triangle Forward Error Correction (FEC) Schemes;;;;;RFC 5170;DOI 10.17487/RFC5170;June;https://www.rfc-editor.org/info/rfc5170 | |
| RFC5171;;Foschiano, M.;Cisco Systems UniDirectional Link Detection (UDLD) Protocol;;;;;RFC 5171;DOI 10.17487/RFC5171;April;https://www.rfc-editor.org/info/rfc5171 | |
| RFC5172;;Varada, S., Ed.;Negotiation for IPv6 Datagram Compression Using IPv6 Control Protocol;;;;;RFC 5172;DOI 10.17487/RFC5172;March;https://www.rfc-editor.org/info/rfc5172 | |
| RFC5173;;Degener, J. and P. Guenther;Sieve Email Filtering: Body Extension;;;;;RFC 5173;DOI 10.17487/RFC5173;April;https://www.rfc-editor.org/info/rfc5173 | |
| RFC5174;;Evain, J-P.;A Uniform Resource Name (URN) Namespace for the European Broadcasting Union (EBU);;;;;RFC 5174;DOI 10.17487/RFC5174;May;https://www.rfc-editor.org/info/rfc5174 | |
| RFC5175;;Haberman, B., Ed., and R. Hinden;IPv6 Router Advertisement Flags Option;;;;;RFC 5175;DOI 10.17487/RFC5175;March;https://www.rfc-editor.org/info/rfc5175 | |
| RFC5176;;Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B. Aboba;Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS);;;;;RFC 5176;DOI 10.17487/RFC5176;January;https://www.rfc-editor.org/info/rfc5176 | |
| RFC5177;;Leung, K., Dommety, G., Narayanan, V., and A. Petrescu;Network Mobility (NEMO) Extensions for Mobile IPv4;;;;;RFC 5177;DOI 10.17487/RFC5177;April;https://www.rfc-editor.org/info/rfc5177 | |
| RFC5178;;Williams, N. and A. Melnikov;Generic Security Service Application Program Interface (GSS-API) Internationalization and Domain-Based Service Names and Name Type;;;;;RFC 5178;DOI 10.17487/RFC5178;May;https://www.rfc-editor.org/info/rfc5178 | |
| RFC5179;;Williams, N.;Generic Security Service Application Program Interface (GSS-API) Domain-Based Service Names Mapping for the Kerberos V GSS Mechanism;;;;;RFC 5179;DOI 10.17487/RFC5179;May;https://www.rfc-editor.org/info/rfc5179 | |
| RFC5180;;Popoviciu, C., Hamza, A., Van de Velde, G., and D. Dugatkin;IPv6 Benchmarking Methodology for Network Interconnect Devices;;;;;RFC 5180;DOI 10.17487/RFC5180;May;https://www.rfc-editor.org/info/rfc5180 | |
| RFC5181;;Shin, M-K., Ed., Han, Y-H., Kim, S-E., and D. Premec;IPv6 Deployment Scenarios in 802.16 Networks;;;;;RFC 5181;DOI 10.17487/RFC5181;May;https://www.rfc-editor.org/info/rfc5181 | |
| RFC5182;;Melnikov, A.;IMAP Extension for Referencing the Last SEARCH Result;;;;;RFC 5182;DOI 10.17487/RFC5182;March;https://www.rfc-editor.org/info/rfc5182 | |
| RFC5183;;Freed, N.;Sieve Email Filtering: Environment Extension;;;;;RFC 5183;DOI 10.17487/RFC5183;May;https://www.rfc-editor.org/info/rfc5183 | |
| RFC5184;;Teraoka, F., Gogo, K., Mitsuya, K., Shibui, R., and K. Mitani;Unified Layer 2 (L2) Abstractions for Layer 3 (L3)-Driven Fast Handover;;;;;RFC 5184;DOI 10.17487/RFC5184;May;https://www.rfc-editor.org/info/rfc5184 | |
| RFC5185;;Mirtorabi, S., Psenak, P., Lindem, A., Ed., and A. Oswal;OSPF Multi-Area Adjacency;;;;;RFC 5185;DOI 10.17487/RFC5185;May;https://www.rfc-editor.org/info/rfc5185 | |
| RFC5186;;Haberman, B. and J. Martin;Internet Group Management Protocol Version 3 (IGMPv3) / Multicast Listener Discovery Version 2 (MLDv2) and Multicast Routing Protocol Interaction;;;;;RFC 5186;DOI 10.17487/RFC5186;May;https://www.rfc-editor.org/info/rfc5186 | |
| RFC5187;;Pillay-Esnault, P. and A. Lindem;OSPFv3 Graceful Restart;;;;;RFC 5187;DOI 10.17487/RFC5187;June;https://www.rfc-editor.org/info/rfc5187 | |
| RFC5188;;Desineni, H. and Q. Xie;RTP Payload Format for the Enhanced Variable Rate Wideband Codec (EVRC-WB) and the Media Subtype Updates for EVRC-B Codec;;;;;RFC 5188;DOI 10.17487/RFC5188;February;https://www.rfc-editor.org/info/rfc5188 | |
| RFC5189;;Stiemerling, M., Quittek, J., and T. Taylor;Middlebox Communication (MIDCOM) Protocol Semantics;;;;;RFC 5189;DOI 10.17487/RFC5189;March;https://www.rfc-editor.org/info/rfc5189 | |
| RFC5190;;Quittek, J., Stiemerling, M., and P. Srisuresh;Definitions of Managed Objects for Middlebox Communication;;;;;RFC 5190;DOI 10.17487/RFC5190;March;https://www.rfc-editor.org/info/rfc5190 | |
| RFC5191;;Forsberg, D., Ohba, Y., Ed., Patil, B., Tschofenig, H., and A. Yegin;Protocol for Carrying Authentication for Network Access (PANA);;;;;RFC 5191;DOI 10.17487/RFC5191;May;https://www.rfc-editor.org/info/rfc5191 | |
| RFC5192;;Morand, L., Yegin, A., Kumar, S., and S. Madanapalli;DHCP Options for Protocol for Carrying Authentication for Network Access (PANA) Authentication Agents;;;;;RFC 5192;DOI 10.17487/RFC5192;May;https://www.rfc-editor.org/info/rfc5192 | |
| RFC5193;;Jayaraman, P., Lopez, R., Ohba, Y., Ed., Parthasarathy, M., and A. Yegin;Protocol for Carrying Authentication for Network Access (PANA) Framework;;;;;RFC 5193;DOI 10.17487/RFC5193;May;https://www.rfc-editor.org/info/rfc5193 | |
| RFC5194;;van Wijk, A., Ed., and G. Gybels, Ed.;Framework for Real-Time Text over IP Using the Session Initiation Protocol (SIP);;;;;RFC 5194;DOI 10.17487/RFC5194;June;https://www.rfc-editor.org/info/rfc5194 | |
| RFC5195;;Ould-Brahim, H., Fedyk, D., and Y. Rekhter;BGP-Based Auto-Discovery for Layer-1 VPNs;;;;;RFC 5195;DOI 10.17487/RFC5195;June;https://www.rfc-editor.org/info/rfc5195 | |
| RFC5196;;Lonnfors, M. and K. Kiss;Session Initiation Protocol (SIP) User Agent Capability Extension to Presence Information Data Format (PIDF);;;;;RFC 5196;DOI 10.17487/RFC5196;September;https://www.rfc-editor.org/info/rfc5196 | |
| RFC5197;;Fries, S. and D. Ignjatic;On the Applicability of Various Multimedia Internet KEYing (MIKEY) Modes and Extensions;;;;;RFC 5197;DOI 10.17487/RFC5197;June;https://www.rfc-editor.org/info/rfc5197 | |
| RFC5198;;Klensin, J. and M. Padlipsky;Unicode Format for Network Interchange;;;;;RFC 5198;DOI 10.17487/RFC5198;March;https://www.rfc-editor.org/info/rfc5198 | |
| RFC5201;RFC7401;Moskowitz, R., Nikander, P., Jokela, P., Ed., and T. Henderson;Host Identity Protocol;;;;;RFC 5201;DOI 10.17487/RFC5201;April;https://www.rfc-editor.org/info/rfc5201 | |
| RFC5202;RFC7402;Jokela, P., Moskowitz, R., and P. Nikander;Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP);;;;;RFC 5202;DOI 10.17487/RFC5202;April;https://www.rfc-editor.org/info/rfc5202 | |
| RFC5203;RFC8003;Laganier, J., Koponen, T., and L. Eggert;Host Identity Protocol (HIP) Registration Extension;;;;;RFC 5203;DOI 10.17487/RFC5203;April;https://www.rfc-editor.org/info/rfc5203 | |
| RFC5204;RFC8004;Laganier, J. and L. Eggert;Host Identity Protocol (HIP) Rendezvous Extension;;;;;RFC 5204;DOI 10.17487/RFC5204;April;https://www.rfc-editor.org/info/rfc5204 | |
| RFC5205;RFC8005;Nikander, P. and J. Laganier;Host Identity Protocol (HIP) Domain Name System (DNS) Extensions;;;;;RFC 5205;DOI 10.17487/RFC5205;April;https://www.rfc-editor.org/info/rfc5205 | |
| RFC5206;RFC8046;Nikander, P., Henderson, T., Ed., Vogt, C., and J. Arkko;End-Host Mobility and Multihoming with the Host Identity Protocol;;;;;RFC 5206;DOI 10.17487/RFC5206;April;https://www.rfc-editor.org/info/rfc5206 | |
| RFC5207;;Stiemerling, M., Quittek, J., and L. Eggert;NAT and Firewall Traversal Issues of Host Identity Protocol (HIP) Communication;;;;;RFC 5207;DOI 10.17487/RFC5207;April;https://www.rfc-editor.org/info/rfc5207 | |
| RFC5208;RFC5958;Kaliski, B.;Public-Key Cryptography Standards (PKCS) #8: Private-Key Information Syntax Specification Version 1.2;;;;;RFC 5208;DOI 10.17487/RFC5208;May;https://www.rfc-editor.org/info/rfc5208 | |
| RFC5209;;Sangster, P., Khosravi, H., Mani, M., Narayan, K., and J. Tardo;Network Endpoint Assessment (NEA): Overview and Requirements;;;;;RFC 5209;DOI 10.17487/RFC5209;June;https://www.rfc-editor.org/info/rfc5209 | |
| RFC5210;;Wu, J., Bi, J., Li, X., Ren, G., Xu, K., and M. Williams;A Source Address Validation Architecture (SAVA) Testbed and Deployment Experience;;;;;RFC 5210;DOI 10.17487/RFC5210;June;https://www.rfc-editor.org/info/rfc5210 | |
| RFC5211;;Curran, J.;An Internet Transition Plan;;;;;RFC 5211;DOI 10.17487/RFC5211;July;https://www.rfc-editor.org/info/rfc5211 | |
| RFC5212;;Shiomoto, K., Papadimitriou, D., Le Roux, JL., Vigoureux, M., and D. Brungard;Requirements for GMPLS-Based Multi-Region and Multi-Layer Networks (MRN/MLN);;;;;RFC 5212;DOI 10.17487/RFC5212;July;https://www.rfc-editor.org/info/rfc5212 | |
| RFC5213;;Gundavelli, S., Ed., Leung, K., Devarapalli, V., Chowdhury, K., and B. Patil;Proxy Mobile IPv6;;;;;RFC 5213;DOI 10.17487/RFC5213;August;https://www.rfc-editor.org/info/rfc5213 | |
| RFC5214;;Templin, F., Gleeson, T., and D. Thaler;Intra-Site Automatic Tunnel Addressing Protocol (ISATAP);;;;;RFC 5214;DOI 10.17487/RFC5214;March;https://www.rfc-editor.org/info/rfc5214 | |
| RFC5215;;Barbato, L.;RTP Payload Format for Vorbis Encoded Audio;;;;;RFC 5215;DOI 10.17487/RFC5215;August;https://www.rfc-editor.org/info/rfc5215 | |
| RFC5216;;Simon, D., Aboba, B., and R. Hurst;The EAP-TLS Authentication Protocol;;;;;RFC 5216;DOI 10.17487/RFC5216;March;https://www.rfc-editor.org/info/rfc5216 | |
| RFC5217;;Shimaoka, M., Ed., Hastings, N., and R. Nielsen;Memorandum for Multi-Domain Public Key Infrastructure Interoperability;;;;;RFC 5217;DOI 10.17487/RFC5217;July;https://www.rfc-editor.org/info/rfc5217 | |
| RFC5218;;Thaler, D. and B. Aboba;What Makes for a Successful Protocol?;;;;;RFC 5218;DOI 10.17487/RFC5218;July;https://www.rfc-editor.org/info/rfc5218 | |
| RFC5219;;Finlayson, R.;A More Loss-Tolerant RTP Payload Format for MP3 Audio;;;;;RFC 5219;DOI 10.17487/RFC5219;February;https://www.rfc-editor.org/info/rfc5219 | |
| RFC5220;;Matsumoto, A., Fujisaki, T., Hiromi, R., and K. Kanayama;Problem Statement for Default Address Selection in Multi-Prefix Environments: Operational Issues of RFC 3484 Default Rules;;;;;RFC 5220;DOI 10.17487/RFC5220;July;https://www.rfc-editor.org/info/rfc5220 | |
| RFC5221;;Matsumoto, A., Fujisaki, T., Hiromi, R., and K. Kanayama;Requirements for Address Selection Mechanisms;;;;;RFC 5221;DOI 10.17487/RFC5221;July;https://www.rfc-editor.org/info/rfc5221 | |
| RFC5222;;Hardie, T., Newton, A., Schulzrinne, H., and H. Tschofenig;LoST: A Location-to-Service Translation Protocol;;;;;RFC 5222;DOI 10.17487/RFC5222;August;https://www.rfc-editor.org/info/rfc5222 | |
| RFC5223;;Schulzrinne, H., Polk, J., and H. Tschofenig;Discovering Location-to-Service Translation (LoST) Servers Using the Dynamic Host Configuration Protocol (DHCP);;;;;RFC 5223;DOI 10.17487/RFC5223;August;https://www.rfc-editor.org/info/rfc5223 | |
| RFC5224;;Brenner, M.;Diameter Policy Processing Application;;;;;RFC 5224;DOI 10.17487/RFC5224;March;https://www.rfc-editor.org/info/rfc5224 | |
| RFC5225;;Pelletier, G. and K. Sandlund;RObust Header Compression Version 2 (ROHCv2): Profiles for RTP, UDP, IP, ESP and UDP-Lite;;;;;RFC 5225;DOI 10.17487/RFC5225;April;https://www.rfc-editor.org/info/rfc5225 | |
| RFC5226;RFC8126;Narten, T. and H. Alvestrand;Guidelines for Writing an IANA Considerations Section in RFCs;;;;;RFC 5226;DOI 10.17487/RFC5226;May;https://www.rfc-editor.org/info/rfc5226 | |
| RFC5227;;Cheshire, S.;IPv4 Address Conflict Detection;;;;;RFC 5227;DOI 10.17487/RFC5227;July;https://www.rfc-editor.org/info/rfc5227 | |
| RFC5228;;Guenther, P., Ed., and T. Showalter, Ed.;Sieve: An Email Filtering Language;;;;;RFC 5228;DOI 10.17487/RFC5228;January;https://www.rfc-editor.org/info/rfc5228 | |
| RFC5229;;Homme, K.;Sieve Email Filtering: Variables Extension;;;;;RFC 5229;DOI 10.17487/RFC5229;January;https://www.rfc-editor.org/info/rfc5229 | |
| RFC5230;;Showalter, T. and N. Freed, Ed.;Sieve Email Filtering: Vacation Extension;;;;;RFC 5230;DOI 10.17487/RFC5230;January;https://www.rfc-editor.org/info/rfc5230 | |
| RFC5231;;Segmuller, W. and B. Leiba;Sieve Email Filtering: Relational Extension;;;;;RFC 5231;DOI 10.17487/RFC5231;January;https://www.rfc-editor.org/info/rfc5231 | |
| RFC5232;;Melnikov, A.;Sieve Email Filtering: Imap4flags Extension;;;;;RFC 5232;DOI 10.17487/RFC5232;January;https://www.rfc-editor.org/info/rfc5232 | |
| RFC5233;;Murchison, K.;Sieve Email Filtering: Subaddress Extension;;;;;RFC 5233;DOI 10.17487/RFC5233;January;https://www.rfc-editor.org/info/rfc5233 | |
| RFC5234;;Crocker, D., Ed., and P. Overell;Augmented BNF for Syntax Specifications: ABNF;;;;STD 68;RFC 5234;DOI 10.17487/RFC5234;January;https://www.rfc-editor.org/info/rfc5234 | |
| RFC5235;;Daboo, C.;Sieve Email Filtering: Spamtest and Virustest Extensions;;;;;RFC 5235;DOI 10.17487/RFC5235;January;https://www.rfc-editor.org/info/rfc5235 | |
| RFC5236;;Jayasumana, A., Piratla, N., Banka, T., Bare, A., and R. Whitner;Improved Packet Reordering Metrics;;;;;RFC 5236;DOI 10.17487/RFC5236;June;https://www.rfc-editor.org/info/rfc5236 | |
| RFC5237;;Arkko, J. and S. Bradner;IANA Allocation Guidelines for the Protocol Field;;;BCP 37;;RFC 5237;DOI 10.17487/RFC5237;February;https://www.rfc-editor.org/info/rfc5237 | |
| RFC5238;;Phelan, T.;Datagram Transport Layer Security (DTLS) over the Datagram Congestion Control Protocol (DCCP);;;;;RFC 5238;DOI 10.17487/RFC5238;May;https://www.rfc-editor.org/info/rfc5238 | |
| RFC5239;;Barnes, M., Boulton, C., and O. Levin;A Framework for Centralized Conferencing;;;;;RFC 5239;DOI 10.17487/RFC5239;June;https://www.rfc-editor.org/info/rfc5239 | |
| RFC5240;;Joshi, B. and R. Bijlani;Protocol Independent Multicast (PIM) Bootstrap Router MIB;;;;;RFC 5240;DOI 10.17487/RFC5240;June;https://www.rfc-editor.org/info/rfc5240 | |
| RFC5241;;Falk, A. and S. Bradner;Naming Rights in IETF Protocols;;;;;RFC 5241;DOI 10.17487/RFC5241;April;https://www.rfc-editor.org/info/rfc5241 | |
| RFC5242;;Klensin, J. and H. Alvestrand;A Generalized Unified Character Code: Western European and CJK Sections;;;;;RFC 5242;DOI 10.17487/RFC5242;April;https://www.rfc-editor.org/info/rfc5242 | |
| RFC5243;;Ogier, R.;OSPF Database Exchange Summary List Optimization;;;;;RFC 5243;DOI 10.17487/RFC5243;May;https://www.rfc-editor.org/info/rfc5243 | |
| RFC5244;;Schulzrinne, H. and T. Taylor;Definition of Events for Channel-Oriented Telephony Signalling;;;;;RFC 5244;DOI 10.17487/RFC5244;June;https://www.rfc-editor.org/info/rfc5244 | |
| RFC5245;RFC8445;Rosenberg, J.;Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols;;;;;RFC 5245;DOI 10.17487/RFC5245;April;https://www.rfc-editor.org/info/rfc5245 | |
| RFC5246;RFC8446;Dierks, T. and E. Rescorla;The Transport Layer Security (TLS) Protocol Version 1.2;;;;;RFC 5246;DOI 10.17487/RFC5246;August;https://www.rfc-editor.org/info/rfc5246 | |
| RFC5247;;Aboba, B., Simon, D., and P. Eronen;Extensible Authentication Protocol (EAP) Key Management Framework;;;;;RFC 5247;DOI 10.17487/RFC5247;August;https://www.rfc-editor.org/info/rfc5247 | |
| RFC5248;;Hansen, T. and J. Klensin;A Registry for SMTP Enhanced Mail System Status Codes;;;BCP 138;;RFC 5248;DOI 10.17487/RFC5248;June;https://www.rfc-editor.org/info/rfc5248 | |
| RFC5249;;Harrington, D., Ed.;Templates for Internet-Drafts Containing MIB Modules;;;BCP 139;;RFC 5249;DOI 10.17487/RFC5249;July;https://www.rfc-editor.org/info/rfc5249 | |
| RFC5250;;Berger, L., Bryskin, I., Zinin, A., and R. Coltun;The OSPF Opaque LSA Option;;;;;RFC 5250;DOI 10.17487/RFC5250;July;https://www.rfc-editor.org/info/rfc5250 | |
| RFC5251;;Fedyk, D., Ed., Rekhter, Y., Ed., Papadimitriou, D., Rabbat, R., and L. Berger;Layer 1 VPN Basic Mode;;;;;RFC 5251;DOI 10.17487/RFC5251;July;https://www.rfc-editor.org/info/rfc5251 | |
| RFC5252;;Bryskin, I. and L. Berger;OSPF-Based Layer 1 VPN Auto-Discovery;;;;;RFC 5252;DOI 10.17487/RFC5252;July;https://www.rfc-editor.org/info/rfc5252 | |
| RFC5253;;Takeda, T., Ed.;Applicability Statement for Layer 1 Virtual Private Network (L1VPN) Basic Mode;;;;;RFC 5253;DOI 10.17487/RFC5253;July;https://www.rfc-editor.org/info/rfc5253 | |
| RFC5254;;Bitar, N., Ed., Bocci, M., Ed., and L. Martini, Ed.;Requirements for Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3);;;;;RFC 5254;DOI 10.17487/RFC5254;October;https://www.rfc-editor.org/info/rfc5254 | |
| RFC5255;;Newman, C., Gulbrandsen, A., and A. Melnikov;Internet Message Access Protocol Internationalization;;;;;RFC 5255;DOI 10.17487/RFC5255;June;https://www.rfc-editor.org/info/rfc5255 | |
| RFC5256;;Crispin, M. and K. Murchison;Internet Message Access Protocol - SORT and THREAD Extensions;;;;;RFC 5256;DOI 10.17487/RFC5256;June;https://www.rfc-editor.org/info/rfc5256 | |
| RFC5257;;Daboo, C. and R. Gellens;Internet Message Access Protocol - ANNOTATE Extension;;;;;RFC 5257;DOI 10.17487/RFC5257;June;https://www.rfc-editor.org/info/rfc5257 | |
| RFC5258;;Leiba, B. and A. Melnikov;Internet Message Access Protocol version 4 - LIST Command Extensions;;;;;RFC 5258;DOI 10.17487/RFC5258;June;https://www.rfc-editor.org/info/rfc5258 | |
| RFC5259;;Melnikov, A., Ed., and P. Coates, Ed.;Internet Message Access Protocol - CONVERT Extension;;;;;RFC 5259;DOI 10.17487/RFC5259;July;https://www.rfc-editor.org/info/rfc5259 | |
| RFC5260;;Freed, N.;Sieve Email Filtering: Date and Index Extensions;;;;;RFC 5260;DOI 10.17487/RFC5260;July;https://www.rfc-editor.org/info/rfc5260 | |
| RFC5261;;Urpalainen, J.;An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors;;;;;RFC 5261;DOI 10.17487/RFC5261;September;https://www.rfc-editor.org/info/rfc5261 | |
| RFC5262;;Lonnfors, M., Leppanen, E., Khartabil, H., and J. Urpalainen;Presence Information Data Format (PIDF) Extension for Partial Presence;;;;;RFC 5262;DOI 10.17487/RFC5262;September;https://www.rfc-editor.org/info/rfc5262 | |
| RFC5263;;Lonnfors, M., Costa-Requena, J., Leppanen, E., and H. Khartabil;Session Initiation Protocol (SIP) Extension for Partial Notification of Presence Information;;;;;RFC 5263;DOI 10.17487/RFC5263;September;https://www.rfc-editor.org/info/rfc5263 | |
| RFC5264;;Niemi, A., Lonnfors, M., and E. Leppanen;Publication of Partial Presence Information;;;;;RFC 5264;DOI 10.17487/RFC5264;September;https://www.rfc-editor.org/info/rfc5264 | |
| RFC5265;;Vaarala, S. and E. Klovning;Mobile IPv4 Traversal across IPsec-Based VPN Gateways;;;;;RFC 5265;DOI 10.17487/RFC5265;June;https://www.rfc-editor.org/info/rfc5265 | |
| RFC5266;;Devarapalli, V. and P. Eronen;Secure Connectivity and Mobility Using Mobile IPv4 and IKEv2 Mobility and Multihoming (MOBIKE);;;BCP 136;;RFC 5266;DOI 10.17487/RFC5266;June;https://www.rfc-editor.org/info/rfc5266 | |
| RFC5267;;Cridland, D. and C. King;Contexts for IMAP4;;;;;RFC 5267;DOI 10.17487/RFC5267;July;https://www.rfc-editor.org/info/rfc5267 | |
| RFC5268;RFC5568;Koodli, R., Ed.;Mobile IPv6 Fast Handovers;;;;;RFC 5268;DOI 10.17487/RFC5268;June;https://www.rfc-editor.org/info/rfc5268 | |
| RFC5269;;Kempf, J. and R. Koodli;Distributing a Symmetric Fast Mobile IPv6 (FMIPv6) Handover Key Using SEcure Neighbor Discovery (SEND);;;;;RFC 5269;DOI 10.17487/RFC5269;June;https://www.rfc-editor.org/info/rfc5269 | |
| RFC5270;;Jang, H., Jee, J., Han, Y., Park, S., and J. Cha;Mobile IPv6 Fast Handovers over IEEE 802.16e Networks;;;;;RFC 5270;DOI 10.17487/RFC5270;June;https://www.rfc-editor.org/info/rfc5270 | |
| RFC5271;;Yokota, H. and G. Dommety;Mobile IPv6 Fast Handovers for 3G CDMA Networks;;;;;RFC 5271;DOI 10.17487/RFC5271;June;https://www.rfc-editor.org/info/rfc5271 | |
| RFC5272;;Schaad, J. and M. Myers;Certificate Management over CMS (CMC);;;;;RFC 5272;DOI 10.17487/RFC5272;June;https://www.rfc-editor.org/info/rfc5272 | |
| RFC5273;;Schaad, J. and M. Myers;Certificate Management over CMS (CMC): Transport Protocols;;;;;RFC 5273;DOI 10.17487/RFC5273;June;https://www.rfc-editor.org/info/rfc5273 | |
| RFC5274;;Schaad, J. and M. Myers;Certificate Management Messages over CMS (CMC): Compliance Requirements;;;;;RFC 5274;DOI 10.17487/RFC5274;June;https://www.rfc-editor.org/info/rfc5274 | |
| RFC5275;;Turner, S.;CMS Symmetric Key Management and Distribution;;;;;RFC 5275;DOI 10.17487/RFC5275;June;https://www.rfc-editor.org/info/rfc5275 | |
| RFC5276;;Wallace, C.;Using the Server-Based Certificate Validation Protocol (SCVP) to Convey Long-Term Evidence Records;;;;;RFC 5276;DOI 10.17487/RFC5276;August;https://www.rfc-editor.org/info/rfc5276 | |
| RFC5277;;Chisholm, S. and H. Trevino;NETCONF Event Notifications;;;;;RFC 5277;DOI 10.17487/RFC5277;July;https://www.rfc-editor.org/info/rfc5277 | |
| RFC5278;;Livingood, J. and D. Troshynski;IANA Registration of Enumservices for Voice and Video Messaging;;;;;RFC 5278;DOI 10.17487/RFC5278;July;https://www.rfc-editor.org/info/rfc5278 | |
| RFC5279;;Monrad, A. and S. Loreto;A Uniform Resource Name (URN) Namespace for the 3rd Generation Partnership Project (3GPP);;;;;RFC 5279;DOI 10.17487/RFC5279;July;https://www.rfc-editor.org/info/rfc5279 | |
| RFC5280;;Cooper, D., Santesson, S., Farrell, S., Boeyen, S., Housley, R., and W. Polk;Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile;;;;;RFC 5280;DOI 10.17487/RFC5280;May;https://www.rfc-editor.org/info/rfc5280 | |
| RFC5281;;Funk, P. and S. Blake-Wilson;Extensible Authentication Protocol Tunneled Transport Layer Security Authenticated Protocol Version 0 (EAP-TTLSv0);;;;;RFC 5281;DOI 10.17487/RFC5281;August;https://www.rfc-editor.org/info/rfc5281 | |
| RFC5282;;Black, D. and D. McGrew;Using Authenticated Encryption Algorithms with the Encrypted Payload of the Internet Key Exchange version 2 (IKEv2) Protocol;;;;;RFC 5282;DOI 10.17487/RFC5282;August;https://www.rfc-editor.org/info/rfc5282 | |
| RFC5283;;Decraene, B., Le Roux, JL., and I. Minei;LDP Extension for Inter-Area Label Switched Paths (LSPs);;;;;RFC 5283;DOI 10.17487/RFC5283;July;https://www.rfc-editor.org/info/rfc5283 | |
| RFC5284;;Swallow, G. and A. Farrel;User-Defined Errors for RSVP;;;;;RFC 5284;DOI 10.17487/RFC5284;August;https://www.rfc-editor.org/info/rfc5284 | |
| RFC5285;RFC8285;Singer, D. and H. Desineni;A General Mechanism for RTP Header Extensions;;;;;RFC 5285;DOI 10.17487/RFC5285;July;https://www.rfc-editor.org/info/rfc5285 | |
| RFC5286;;Atlas, A., Ed., and A. Zinin, Ed.;Basic Specification for IP Fast Reroute: Loop-Free Alternates;;;;;RFC 5286;DOI 10.17487/RFC5286;September;https://www.rfc-editor.org/info/rfc5286 | |
| RFC5287;;Vainshtein, A. and Y(J). Stein;Control Protocol Extensions for the Setup of Time-Division Multiplexing (TDM) Pseudowires in MPLS Networks;;;;;RFC 5287;DOI 10.17487/RFC5287;August;https://www.rfc-editor.org/info/rfc5287 | |
| RFC5288;;Salowey, J., Choudhury, A., and D. McGrew;AES Galois Counter Mode (GCM) Cipher Suites for TLS;;;;;RFC 5288;DOI 10.17487/RFC5288;August;https://www.rfc-editor.org/info/rfc5288 | |
| RFC5289;;Rescorla, E.;TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode (GCM);;;;;RFC 5289;DOI 10.17487/RFC5289;August;https://www.rfc-editor.org/info/rfc5289 | |
| RFC5290;;Floyd, S. and M. Allman;Comments on the Usefulness of Simple Best-Effort Traffic;;;;;RFC 5290;DOI 10.17487/RFC5290;July;https://www.rfc-editor.org/info/rfc5290 | |
| RFC5291;;Chen, E. and Y. Rekhter;Outbound Route Filtering Capability for BGP-4;;;;;RFC 5291;DOI 10.17487/RFC5291;August;https://www.rfc-editor.org/info/rfc5291 | |
| RFC5292;;Chen, E. and S. Sangli;Address-Prefix-Based Outbound Route Filter for BGP-4;;;;;RFC 5292;DOI 10.17487/RFC5292;August;https://www.rfc-editor.org/info/rfc5292 | |
| RFC5293;;Degener, J. and P. Guenther;Sieve Email Filtering: Editheader Extension;;;;;RFC 5293;DOI 10.17487/RFC5293;August;https://www.rfc-editor.org/info/rfc5293 | |
| RFC5294;;Savola, P. and J. Lingard;Host Threats to Protocol Independent Multicast (PIM);;;;;RFC 5294;DOI 10.17487/RFC5294;August;https://www.rfc-editor.org/info/rfc5294 | |
| RFC5295;;Salowey, J., Dondeti, L., Narayanan, V., and M. Nakhjiri;Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK);;;;;RFC 5295;DOI 10.17487/RFC5295;August;https://www.rfc-editor.org/info/rfc5295 | |
| RFC5296;RFC6696;Narayanan, V. and L. Dondeti;EAP Extensions for EAP Re-authentication Protocol (ERP);;;;;RFC 5296;DOI 10.17487/RFC5296;August;https://www.rfc-editor.org/info/rfc5296 | |
| RFC5297;;Harkins, D.;Synthetic Initialization Vector (SIV) Authenticated Encryption Using the Advanced Encryption Standard (AES);;;;;RFC 5297;DOI 10.17487/RFC5297;October;https://www.rfc-editor.org/info/rfc5297 | |
| RFC5298;;Takeda, T., Ed., Farrel, A., Ed., Ikejiri, Y., and JP. Vasseur;Analysis of Inter-Domain Label Switched Path (LSP) Recovery;;;;;RFC 5298;DOI 10.17487/RFC5298;August;https://www.rfc-editor.org/info/rfc5298 | |
| RFC5301;;McPherson, D. and N. Shen;Dynamic Hostname Exchange Mechanism for IS-IS;;;;;RFC 5301;DOI 10.17487/RFC5301;October;https://www.rfc-editor.org/info/rfc5301 | |
| RFC5302;;Li, T., Smit, H., and T. Przygienda;Domain-Wide Prefix Distribution with Two-Level IS-IS;;;;;RFC 5302;DOI 10.17487/RFC5302;October;https://www.rfc-editor.org/info/rfc5302 | |
| RFC5303;;Katz, D., Saluja, R., and D. Eastlake 3rd;Three-Way Handshake for IS-IS Point-to-Point Adjacencies;;;;;RFC 5303;DOI 10.17487/RFC5303;October;https://www.rfc-editor.org/info/rfc5303 | |
| RFC5304;;Li, T. and R. Atkinson;IS-IS Cryptographic Authentication;;;;;RFC 5304;DOI 10.17487/RFC5304;October;https://www.rfc-editor.org/info/rfc5304 | |
| RFC5305;;Li, T. and H. Smit;IS-IS Extensions for Traffic Engineering;;;;;RFC 5305;DOI 10.17487/RFC5305;October;https://www.rfc-editor.org/info/rfc5305 | |
| RFC5306;RFC8706;Shand, M. and L. Ginsberg;Restart Signaling for IS-IS;;;;;RFC 5306;DOI 10.17487/RFC5306;October;https://www.rfc-editor.org/info/rfc5306 | |
| RFC5307;;Kompella, K., Ed., and Y. Rekhter, Ed.;IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS);;;;;RFC 5307;DOI 10.17487/RFC5307;October;https://www.rfc-editor.org/info/rfc5307 | |
| RFC5308;;Hopps, C.;Routing IPv6 with IS-IS;;;;;RFC 5308;DOI 10.17487/RFC5308;October;https://www.rfc-editor.org/info/rfc5308 | |
| RFC5309;;Shen, N., Ed., and A. Zinin, Ed.;Point-to-Point Operation over LAN in Link State Routing Protocols;;;;;RFC 5309;DOI 10.17487/RFC5309;October;https://www.rfc-editor.org/info/rfc5309 | |
| RFC5310;;Bhatia, M., Manral, V., Li, T., Atkinson, R., White, R., and M. Fanto;IS-IS Generic Cryptographic Authentication;;;;;RFC 5310;DOI 10.17487/RFC5310;February;https://www.rfc-editor.org/info/rfc5310 | |
| RFC5311;;McPherson, D., Ed., Ginsberg, L., Previdi, S., and M. Shand;Simplified Extension of Link State PDU (LSP) Space for IS-IS;;;;;RFC 5311;DOI 10.17487/RFC5311;February;https://www.rfc-editor.org/info/rfc5311 | |
| RFC5316;;Chen, M., Zhang, R., and X. Duan;ISIS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering;;;;;RFC 5316;DOI 10.17487/RFC5316;December;https://www.rfc-editor.org/info/rfc5316 | |
| RFC5317;;Bryant, S., Ed., and L. Andersson, Ed.;Joint Working Team (JWT) Report on MPLS Architectural Considerations for a Transport Profile;;;;;RFC 5317;DOI 10.17487/RFC5317;February;https://www.rfc-editor.org/info/rfc5317 | |
| RFC5318;;Hautakorpi, J. and G. Camarillo;The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header);;;;;RFC 5318;DOI 10.17487/RFC5318;December;https://www.rfc-editor.org/info/rfc5318 | |
| RFC5320;;Templin, F., Ed.;The Subnetwork Encapsulation and Adaptation Layer (SEAL);;;;;RFC 5320;DOI 10.17487/RFC5320;February;https://www.rfc-editor.org/info/rfc5320 | |
| RFC5321;;Klensin, J.;Simple Mail Transfer Protocol;;;;;RFC 5321;DOI 10.17487/RFC5321;October;https://www.rfc-editor.org/info/rfc5321 | |
| RFC5322;;Resnick, P., Ed.;Internet Message Format;;;;;RFC 5322;DOI 10.17487/RFC5322;October;https://www.rfc-editor.org/info/rfc5322 | |
| RFC5323;;Reschke, J., Ed., Reddy, S., Davis, J., and A. Babich;Web Distributed Authoring and Versioning (WebDAV) SEARCH;;;;;RFC 5323;DOI 10.17487/RFC5323;November;https://www.rfc-editor.org/info/rfc5323 | |
| RFC5324;;DeSanti, C., Maino, F., and K. McCloghrie;MIB for Fibre-Channel Security Protocols (FC-SP);;;;;RFC 5324;DOI 10.17487/RFC5324;September;https://www.rfc-editor.org/info/rfc5324 | |
| RFC5325;;Burleigh, S., Ramadas, M., and S. Farrell;Licklider Transmission Protocol - Motivation;;;;;RFC 5325;DOI 10.17487/RFC5325;September;https://www.rfc-editor.org/info/rfc5325 | |
| RFC5326;;Ramadas, M., Burleigh, S., and S. Farrell;Licklider Transmission Protocol - Specification;;;;;RFC 5326;DOI 10.17487/RFC5326;September;https://www.rfc-editor.org/info/rfc5326 | |
| RFC5327;;Farrell, S., Ramadas, M., and S. Burleigh;Licklider Transmission Protocol - Security Extensions;;;;;RFC 5327;DOI 10.17487/RFC5327;September;https://www.rfc-editor.org/info/rfc5327 | |
| RFC5328;;Adolf, A. and P. MacAvock;A Uniform Resource Name (URN) Namespace for the Digital Video Broadcasting Project (DVB);;;;;RFC 5328;DOI 10.17487/RFC5328;September;https://www.rfc-editor.org/info/rfc5328 | |
| RFC5329;;Ishiguro, K., Manral, V., Davey, A., and A. Lindem, Ed.;Traffic Engineering Extensions to OSPF Version 3;;;;;RFC 5329;DOI 10.17487/RFC5329;September;https://www.rfc-editor.org/info/rfc5329 | |
| RFC5330;;Vasseur, JP., Ed., Meyer, M., Kumaki, K., and A. Bonda;A Link-Type sub-TLV to Convey the Number of Traffic Engineering Label Switched Paths Signalled with Zero Reserved Bandwidth across a Link;;;;;RFC 5330;DOI 10.17487/RFC5330;October;https://www.rfc-editor.org/info/rfc5330 | |
| RFC5331;;Aggarwal, R., Rekhter, Y., and E. Rosen;MPLS Upstream Label Assignment and Context-Specific Label Space;;;;;RFC 5331;DOI 10.17487/RFC5331;August;https://www.rfc-editor.org/info/rfc5331 | |
| RFC5332;;Eckert, T., Rosen, E., Ed., Aggarwal, R., and Y. Rekhter;MPLS Multicast Encapsulations;;;;;RFC 5332;DOI 10.17487/RFC5332;August;https://www.rfc-editor.org/info/rfc5332 | |
| RFC5333;;Mahy, R. and B. Hoeneisen;IANA Registration of Enumservices for Internet Calendaring;;;;;RFC 5333;DOI 10.17487/RFC5333;October;https://www.rfc-editor.org/info/rfc5333 | |
| RFC5334;;Goncalves, I., Pfeiffer, S., and C. Montgomery;Ogg Media Types;;;;;RFC 5334;DOI 10.17487/RFC5334;September;https://www.rfc-editor.org/info/rfc5334 | |
| RFC5335;RFC6532;Yang, A., Ed.;Internationalized Email Headers;;;;;RFC 5335;DOI 10.17487/RFC5335;September;https://www.rfc-editor.org/info/rfc5335 | |
| RFC5336;RFC6531;Yao, J., Ed., and W. Mao, Ed.;SMTP Extension for Internationalized Email Addresses;;;;;RFC 5336;DOI 10.17487/RFC5336;September;https://www.rfc-editor.org/info/rfc5336 | |
| RFC5337;RFC6533;Newman, C. and A. Melnikov, Ed.;Internationalized Delivery Status and Disposition Notifications;;;;;RFC 5337;DOI 10.17487/RFC5337;September;https://www.rfc-editor.org/info/rfc5337 | |
| RFC5338;;Henderson, T., Nikander, P., and M. Komu;Using the Host Identity Protocol with Legacy Applications;;;;;RFC 5338;DOI 10.17487/RFC5338;September;https://www.rfc-editor.org/info/rfc5338 | |
| RFC5339;;Le Roux, JL., Ed., and D. Papadimitriou, Ed.;Evaluation of Existing GMPLS Protocols against Multi-Layer and Multi-Region Networks (MLN/MRN);;;;;RFC 5339;DOI 10.17487/RFC5339;September;https://www.rfc-editor.org/info/rfc5339 | |
| RFC5340;;Coltun, R., Ferguson, D., Moy, J., and A. Lindem;OSPF for IPv6;;;;;RFC 5340;DOI 10.17487/RFC5340;July;https://www.rfc-editor.org/info/rfc5340 | |
| RFC5341;;Jennings, C. and V. Gurbani;The Internet Assigned Number Authority (IANA) tel Uniform Resource Identifier (URI) Parameter Registry;;;;;RFC 5341;DOI 10.17487/RFC5341;September;https://www.rfc-editor.org/info/rfc5341 | |
| RFC5342;RFC7042;Eastlake 3rd, D.;IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters;;;;;RFC 5342;DOI 10.17487/RFC5342;September;https://www.rfc-editor.org/info/rfc5342 | |
| RFC5343;;Schoenwaelder, J.;Simple Network Management Protocol (SNMP) Context EngineID Discovery;;;;STD 78;RFC 5343;DOI 10.17487/RFC5343;September;https://www.rfc-editor.org/info/rfc5343 | |
| RFC5344;;Houri, A., Aoki, E., and S. Parameswar;Presence and Instant Messaging Peering Use Cases;;;;;RFC 5344;DOI 10.17487/RFC5344;October;https://www.rfc-editor.org/info/rfc5344 | |
| RFC5345;;Schoenwaelder, J.;Simple Network Management Protocol (SNMP) Traffic Measurements and Trace Exchange Formats;;;;;RFC 5345;DOI 10.17487/RFC5345;October;https://www.rfc-editor.org/info/rfc5345 | |
| RFC5346;;Lim, J., Kim, W., Park, C., and L. Conroy;Operational Requirements for ENUM-Based Softswitch Use;;;;;RFC 5346;DOI 10.17487/RFC5346;October;https://www.rfc-editor.org/info/rfc5346 | |
| RFC5347;;Andreasen, F. and D. Hancock;Media Gateway Control Protocol Fax Package;;;;;RFC 5347;DOI 10.17487/RFC5347;October;https://www.rfc-editor.org/info/rfc5347 | |
| RFC5348;;Floyd, S., Handley, M., Padhye, J., and J. Widmer;TCP Friendly Rate Control (TFRC): Protocol Specification;;;;;RFC 5348;DOI 10.17487/RFC5348;September;https://www.rfc-editor.org/info/rfc5348 | |
| RFC5349;;Zhu, L., Jaganathan, K., and K. Lauter;Elliptic Curve Cryptography (ECC) Support for Public Key Cryptography for Initial Authentication in Kerberos (PKINIT);;;;;RFC 5349;DOI 10.17487/RFC5349;September;https://www.rfc-editor.org/info/rfc5349 | |
| RFC5350;;Manner, J. and A. McDonald;IANA Considerations for the IPv4 and IPv6 Router Alert Options;;;;;RFC 5350;DOI 10.17487/RFC5350;September;https://www.rfc-editor.org/info/rfc5350 | |
| RFC5351;;Lei, P., Ong, L., Tuexen, M., and T. Dreibholz;An Overview of Reliable Server Pooling Protocols;;;;;RFC 5351;DOI 10.17487/RFC5351;September;https://www.rfc-editor.org/info/rfc5351 | |
| RFC5352;;Stewart, R., Xie, Q., Stillman, M., and M. Tuexen;Aggregate Server Access Protocol (ASAP);;;;;RFC 5352;DOI 10.17487/RFC5352;September;https://www.rfc-editor.org/info/rfc5352 | |
| RFC5353;;Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A. Silverton;Endpoint Handlespace Redundancy Protocol (ENRP);;;;;RFC 5353;DOI 10.17487/RFC5353;September;https://www.rfc-editor.org/info/rfc5353 | |
| RFC5354;;Stewart, R., Xie, Q., Stillman, M., and M. Tuexen;Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP) Parameters;;;;;RFC 5354;DOI 10.17487/RFC5354;September;https://www.rfc-editor.org/info/rfc5354 | |
| RFC5355;;Stillman, M., Ed., Gopal, R., Guttman, E., Sengodan, S., and M. Holdrege;Threats Introduced by Reliable Server Pooling (RSerPool) and Requirements for Security in Response to Threats;;;;;RFC 5355;DOI 10.17487/RFC5355;September;https://www.rfc-editor.org/info/rfc5355 | |
| RFC5356;;Dreibholz, T. and M. Tuexen;Reliable Server Pooling Policies;;;;;RFC 5356;DOI 10.17487/RFC5356;September;https://www.rfc-editor.org/info/rfc5356 | |
| RFC5357;;Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J. Babiarz;A Two-Way Active Measurement Protocol (TWAMP);;;;;RFC 5357;DOI 10.17487/RFC5357;October;https://www.rfc-editor.org/info/rfc5357 | |
| RFC5358;;Damas, J. and F. Neves;Preventing Use of Recursive Nameservers in Reflector Attacks;;;BCP 140;;RFC 5358;DOI 10.17487/RFC5358;October;https://www.rfc-editor.org/info/rfc5358 | |
| RFC5359;;Johnston, A., Ed., Sparks, R., Cunningham, C., Donovan, S., and K. Summers;Session Initiation Protocol Service Examples;;;BCP 144;;RFC 5359;DOI 10.17487/RFC5359;October;https://www.rfc-editor.org/info/rfc5359 | |
| RFC5360;;Rosenberg, J., Camarillo, G., Ed., and D. Willis;A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP);;;;;RFC 5360;DOI 10.17487/RFC5360;October;https://www.rfc-editor.org/info/rfc5360 | |
| RFC5361;;Camarillo, G.;A Document Format for Requesting Consent;;;;;RFC 5361;DOI 10.17487/RFC5361;October;https://www.rfc-editor.org/info/rfc5361 | |
| RFC5362;;Camarillo, G.;The Session Initiation Protocol (SIP) Pending Additions Event Package;;;;;RFC 5362;DOI 10.17487/RFC5362;October;https://www.rfc-editor.org/info/rfc5362 | |
| RFC5363;;Camarillo, G. and A. Roach;Framework and Security Considerations for Session Initiation Protocol (SIP) URI-List Services;;;;;RFC 5363;DOI 10.17487/RFC5363;October;https://www.rfc-editor.org/info/rfc5363 | |
| RFC5364;;Garcia-Martin, M. and G. Camarillo;Extensible Markup Language (XML) Format Extension for Representing Copy Control Attributes in Resource Lists;;;;;RFC 5364;DOI 10.17487/RFC5364;October;https://www.rfc-editor.org/info/rfc5364 | |
| RFC5365;;Garcia-Martin, M. and G. Camarillo;Multiple-Recipient MESSAGE Requests in the Session Initiation Protocol (SIP);;;;;RFC 5365;DOI 10.17487/RFC5365;October;https://www.rfc-editor.org/info/rfc5365 | |
| RFC5366;;Camarillo, G. and A. Johnston;Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP);;;;;RFC 5366;DOI 10.17487/RFC5366;October;https://www.rfc-editor.org/info/rfc5366 | |
| RFC5367;;Camarillo, G., Roach, A., and O. Levin;Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP);;;;;RFC 5367;DOI 10.17487/RFC5367;October;https://www.rfc-editor.org/info/rfc5367 | |
| RFC5368;;Camarillo, G., Niemi, A., Isomaki, M., Garcia-Martin, M., and H. Khartabil;Referring to Multiple Resources in the Session Initiation Protocol (SIP);;;;;RFC 5368;DOI 10.17487/RFC5368;October;https://www.rfc-editor.org/info/rfc5368 | |
| RFC5369;;Camarillo, G.;Framework for Transcoding with the Session Initiation Protocol (SIP);;;;;RFC 5369;DOI 10.17487/RFC5369;October;https://www.rfc-editor.org/info/rfc5369 | |
| RFC5370;;Camarillo, G.;The Session Initiation Protocol (SIP) Conference Bridge Transcoding Model;;;;;RFC 5370;DOI 10.17487/RFC5370;October;https://www.rfc-editor.org/info/rfc5370 | |
| RFC5371;;Futemma, S., Itakura, E., and A. Leung;RTP Payload Format for JPEG 2000 Video Streams;;;;;RFC 5371;DOI 10.17487/RFC5371;October;https://www.rfc-editor.org/info/rfc5371 | |
| RFC5372;;Leung, A., Futemma, S., and E. Itakura;Payload Format for JPEG 2000 Video: Extensions for Scalability and Main Header Recovery;;;;;RFC 5372;DOI 10.17487/RFC5372;October;https://www.rfc-editor.org/info/rfc5372 | |
| RFC5373;;Willis, D., Ed., and A. Allen;Requesting Answering Modes for the Session Initiation Protocol (SIP);;;;;RFC 5373;DOI 10.17487/RFC5373;November;https://www.rfc-editor.org/info/rfc5373 | |
| RFC5374;;Weis, B., Gross, G., and D. Ignjatic;Multicast Extensions to the Security Architecture for the Internet Protocol;;;;;RFC 5374;DOI 10.17487/RFC5374;November;https://www.rfc-editor.org/info/rfc5374 | |
| RFC5375;;Van de Velde, G., Popoviciu, C., Chown, T., Bonness, O., and C. Hahn;IPv6 Unicast Address Assignment Considerations;;;;;RFC 5375;DOI 10.17487/RFC5375;December;https://www.rfc-editor.org/info/rfc5375 | |
| RFC5376;;Bitar, N., Zhang, R., and K. Kumaki;Inter-AS Requirements for the Path Computation Element Communication Protocol (PCECP);;;;;RFC 5376;DOI 10.17487/RFC5376;November;https://www.rfc-editor.org/info/rfc5376 | |
| RFC5377;RFC8721;Halpern, J., Ed.;Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF Documents;;;;;RFC 5377;DOI 10.17487/RFC5377;November;https://www.rfc-editor.org/info/rfc5377 | |
| RFC5378;;Bradner, S., Ed., and J. Contreras, Ed.;Rights Contributors Provide to the IETF Trust;;;BCP 78;;RFC 5378;DOI 10.17487/RFC5378;November;https://www.rfc-editor.org/info/rfc5378 | |
| RFC5379;;Munakata, M., Schubert, S., and T. Ohba;Guidelines for Using the Privacy Mechanism for SIP;;;;;RFC 5379;DOI 10.17487/RFC5379;February;https://www.rfc-editor.org/info/rfc5379 | |
| RFC5380;;Soliman, H., Castelluccia, C., ElMalki, K., and L. Bellier;Hierarchical Mobile IPv6 (HMIPv6) Mobility Management;;;;;RFC 5380;DOI 10.17487/RFC5380;October;https://www.rfc-editor.org/info/rfc5380 | |
| RFC5381;;Iijima, T., Atarashi, Y., Kimura, H., Kitani, M., and H. Okita;Experience of Implementing NETCONF over SOAP;;;;;RFC 5381;DOI 10.17487/RFC5381;October;https://www.rfc-editor.org/info/rfc5381 | |
| RFC5382;;Guha, S., Ed., Biswas, K., Ford, B., Sivakumar, S., and P. Srisuresh;NAT Behavioral Requirements for TCP;;;BCP 142;;RFC 5382;DOI 10.17487/RFC5382;October;https://www.rfc-editor.org/info/rfc5382 | |
| RFC5383;;Gellens, R.;Deployment Considerations for Lemonade-Compliant Mobile Email;;;BCP 143;;RFC 5383;DOI 10.17487/RFC5383;October;https://www.rfc-editor.org/info/rfc5383 | |
| RFC5384;;Boers, A., Wijnands, I., and E. Rosen;The Protocol Independent Multicast (PIM) Join Attribute Format;;;;;RFC 5384;DOI 10.17487/RFC5384;November;https://www.rfc-editor.org/info/rfc5384 | |
| RFC5385;;Touch, J.;Version 2.0 Microsoft Word Template for Creating Internet Drafts and RFCs;;;;;RFC 5385;DOI 10.17487/RFC5385;February;https://www.rfc-editor.org/info/rfc5385 | |
| RFC5386;;Williams, N. and M. Richardson;Better-Than-Nothing Security: An Unauthenticated Mode of IPsec;;;;;RFC 5386;DOI 10.17487/RFC5386;November;https://www.rfc-editor.org/info/rfc5386 | |
| RFC5387;;Touch, J., Black, D., and Y. Wang;Problem and Applicability Statement for Better-Than-Nothing Security (BTNS);;;;;RFC 5387;DOI 10.17487/RFC5387;November;https://www.rfc-editor.org/info/rfc5387 | |
| RFC5388;;Niccolini, S., Tartarelli, S., Quittek, J., Dietz, T., and M. Swany;Information Model and XML Data Model for Traceroute Measurements;;;;;RFC 5388;DOI 10.17487/RFC5388;December;https://www.rfc-editor.org/info/rfc5388 | |
| RFC5389;RFC8489;Rosenberg, J., Mahy, R., Matthews, P., and D. Wing;Session Traversal Utilities for NAT (STUN);;;;;RFC 5389;DOI 10.17487/RFC5389;October;https://www.rfc-editor.org/info/rfc5389 | |
| RFC5390;;Rosenberg, J.;Requirements for Management of Overload in the Session Initiation Protocol;;;;;RFC 5390;DOI 10.17487/RFC5390;December;https://www.rfc-editor.org/info/rfc5390 | |
| RFC5391;;Sollaud, A.;RTP Payload Format for ITU-T Recommendation G.711.1;;;;;RFC 5391;DOI 10.17487/RFC5391;November;https://www.rfc-editor.org/info/rfc5391 | |
| RFC5392;;Chen, M., Zhang, R., and X. Duan;OSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering;;;;;RFC 5392;DOI 10.17487/RFC5392;January;https://www.rfc-editor.org/info/rfc5392 | |
| RFC5393;;Sparks, R., Ed., Lawrence, S., Hawrylyshen, A., and B. Campen;Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies;;;;;RFC 5393;DOI 10.17487/RFC5393;December;https://www.rfc-editor.org/info/rfc5393 | |
| RFC5394;;Bryskin, I., Papadimitriou, D., Berger, L., and J. Ash;Policy-Enabled Path Computation Framework;;;;;RFC 5394;DOI 10.17487/RFC5394;December;https://www.rfc-editor.org/info/rfc5394 | |
| RFC5395;RFC6195;Eastlake 3rd, D.;Domain Name System (DNS) IANA Considerations;;;;;RFC 5395;DOI 10.17487/RFC5395;November;https://www.rfc-editor.org/info/rfc5395 | |
| RFC5396;;Huston, G. and G. Michaelson;Textual Representation of Autonomous System (AS) Numbers;;;;;RFC 5396;DOI 10.17487/RFC5396;December;https://www.rfc-editor.org/info/rfc5396 | |
| RFC5397;;Sanchez, W. and C. Daboo;WebDAV Current Principal Extension;;;;;RFC 5397;DOI 10.17487/RFC5397;December;https://www.rfc-editor.org/info/rfc5397 | |
| RFC5398;;Huston, G.;Autonomous System (AS) Number Reservation for Documentation Use;;;;;RFC 5398;DOI 10.17487/RFC5398;December;https://www.rfc-editor.org/info/rfc5398 | |
| RFC5401;;Adamson, B., Bormann, C., Handley, M., and J. Macker;Multicast Negative-Acknowledgment (NACK) Building Blocks;;;;;RFC 5401;DOI 10.17487/RFC5401;November;https://www.rfc-editor.org/info/rfc5401 | |
| RFC5402;;Harding, T., Ed.;Compressed Data within an Internet Electronic Data Interchange (EDI) Message;;;;;RFC 5402;DOI 10.17487/RFC5402;February;https://www.rfc-editor.org/info/rfc5402 | |
| RFC5403;;Eisler, M.;RPCSEC_GSS Version 2;;;;;RFC 5403;DOI 10.17487/RFC5403;February;https://www.rfc-editor.org/info/rfc5403 | |
| RFC5404;;Westerlund, M. and I. Johansson;RTP Payload Format for G.719;;;;;RFC 5404;DOI 10.17487/RFC5404;January;https://www.rfc-editor.org/info/rfc5404 | |
| RFC5405;RFC8085;Eggert, L. and G. Fairhurst;Unicast UDP Usage Guidelines for Application Designers;;;;;RFC 5405;DOI 10.17487/RFC5405;November;https://www.rfc-editor.org/info/rfc5405 | |
| RFC5406;;Bellovin, S.;Guidelines for Specifying the Use of IPsec Version 2;;;BCP 146;;RFC 5406;DOI 10.17487/RFC5406;February;https://www.rfc-editor.org/info/rfc5406 | |
| RFC5407;;Hasebe, M., Koshiko, J., Suzuki, Y., Yoshikawa, T., and P. Kyzivat;Example Call Flows of Race Conditions in the Session Initiation Protocol (SIP);;;BCP 147;;RFC 5407;DOI 10.17487/RFC5407;December;https://www.rfc-editor.org/info/rfc5407 | |
| RFC5408;;Appenzeller, G., Martin, L., and M. Schertler;Identity-Based Encryption Architecture and Supporting Data Structures;;;;;RFC 5408;DOI 10.17487/RFC5408;January;https://www.rfc-editor.org/info/rfc5408 | |
| RFC5409;;Martin, L. and M. Schertler;Using the Boneh-Franklin and Boneh-Boyen Identity-Based Encryption Algorithms with the Cryptographic Message Syntax (CMS);;;;;RFC 5409;DOI 10.17487/RFC5409;January;https://www.rfc-editor.org/info/rfc5409 | |
| RFC5410;;Jerichow, A., Ed., and L. Piron;Multimedia Internet KEYing (MIKEY) General Extension Payload for Open Mobile Alliance BCAST 1.0;;;;;RFC 5410;DOI 10.17487/RFC5410;January;https://www.rfc-editor.org/info/rfc5410 | |
| RFC5411;;Rosenberg, J.;A Hitchhiker's Guide to the Session Initiation Protocol (SIP);;;;;RFC 5411;DOI 10.17487/RFC5411;February;https://www.rfc-editor.org/info/rfc5411 | |
| RFC5412;;Calhoun, P., Suri, R., Cam-Winget, N., Williams, M., Hares, S., O'Hara, B., and S. Kelly;Lightweight Access Point Protocol;;;;;RFC 5412;DOI 10.17487/RFC5412;February;https://www.rfc-editor.org/info/rfc5412 | |
| RFC5413;;Narasimhan, P., Harkins, D., and S. Ponnuswamy;SLAPP: Secure Light Access Point Protocol;;;;;RFC 5413;DOI 10.17487/RFC5413;February;https://www.rfc-editor.org/info/rfc5413 | |
| RFC5414;RFC5415;Iino, S., Govindan, S., Sugiura, M., and H. Cheng;Wireless LAN Control Protocol (WiCoP);;;;;RFC 5414;DOI 10.17487/RFC5414;February;https://www.rfc-editor.org/info/rfc5414 | |
| RFC5415;;Calhoun, P., Ed., Montemurro, M., Ed., and D. Stanley, Ed.;Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification;;;;;RFC 5415;DOI 10.17487/RFC5415;March;https://www.rfc-editor.org/info/rfc5415 | |
| RFC5416;;Calhoun, P., Ed., Montemurro, M., Ed., and D. Stanley, Ed.;Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Binding for IEEE 802.11;;;;;RFC 5416;DOI 10.17487/RFC5416;March;https://www.rfc-editor.org/info/rfc5416 | |
| RFC5417;;Calhoun, P.;Control And Provisioning of Wireless Access Points (CAPWAP) Access Controller DHCP Option;;;;;RFC 5417;DOI 10.17487/RFC5417;March;https://www.rfc-editor.org/info/rfc5417 | |
| RFC5418;;Kelly, S. and T. Clancy;Control And Provisioning of Wireless Access Points (CAPWAP) Threat Analysis for IEEE 802.11 Deployments;;;;;RFC 5418;DOI 10.17487/RFC5418;March;https://www.rfc-editor.org/info/rfc5418 | |
| RFC5419;;Patil, B. and G. Dommety;Why the Authentication Data Suboption is Needed for Mobile IPv6 (MIPv6);;;;;RFC 5419;DOI 10.17487/RFC5419;January;https://www.rfc-editor.org/info/rfc5419 | |
| RFC5420;;Farrel, A., Ed., Papadimitriou, D., Vasseur, JP., and A. Ayyangar;Encoding of Attributes for MPLS LSP Establishment Using Resource Reservation Protocol Traffic Engineering (RSVP-TE);;;;;RFC 5420;DOI 10.17487/RFC5420;February;https://www.rfc-editor.org/info/rfc5420 | |
| RFC5421;;Cam-Winget, N. and H. Zhou;Basic Password Exchange within the Flexible Authentication via Secure Tunneling Extensible Authentication Protocol (EAP-FAST);;;;;RFC 5421;DOI 10.17487/RFC5421;March;https://www.rfc-editor.org/info/rfc5421 | |
| RFC5422;;Cam-Winget, N., McGrew, D., Salowey, J., and H. Zhou;Dynamic Provisioning Using Flexible Authentication via Secure Tunneling Extensible Authentication Protocol (EAP-FAST);;;;;RFC 5422;DOI 10.17487/RFC5422;March;https://www.rfc-editor.org/info/rfc5422 | |
| RFC5423;;Gellens, R. and C. Newman;Internet Message Store Events;;;;;RFC 5423;DOI 10.17487/RFC5423;March;https://www.rfc-editor.org/info/rfc5423 | |
| RFC5424;;Gerhards, R.;The Syslog Protocol;;;;;RFC 5424;DOI 10.17487/RFC5424;March;https://www.rfc-editor.org/info/rfc5424 | |
| RFC5425;;Miao, F., Ed., Ma, Y., Ed., and J. Salowey, |
View raw
(Sorry about that, but we can’t show files that are this big right now.)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment