RFC:
• RFC13: Zero Text Length EOF Message.
• RFC35: Network Meeting.
• RFC36: Protocol Notes.
• RFC37: Network Meeting Epilogue, etc.
• RFC39: Comments on Protocol Re: NWG/RFC #36.
• RFC44: Comments on NWG/RFC 33 and 36.
• RFC47: BBN's Comments on NWG/RFC #33.
• RFC49: Conversations with S. Crocker (UCLA).
• RFC54: Official Protocol Proffering.
• RFC55: Prototypical implementation of the
• RFC57: Thoughts and Reflections on NWG/RFC 54.
• RFC72: Proposed Moratorium on Changes to Network Protocol.
• RFC73: Response to NWG/RFC 67.
• RFC79: Logger Protocol error.
• RFC83: Language-machine for data reconfiguration.
• RFC93: Initial Connection Protocol.
• RFC95: Distribution of NWG/RFC's through the
• RFC101: Notes on the Network Working Group meeting, Urbana, Illinois, February 17, 1971.
• RFC103: Implementation of Interrupt Keys.
• RFC111: Pressure from the Chairman.
• RFC124: Typographical error in RFC 107.
• RFC127: Comments on RFC 123.
• RFC130: Response to RFC 111: Pressure from the chairman.
• RFC131: Response to RFC 116: May NWG meeting.
• RFC132: Typographical Error in RFC 107.
• RFC135: Response to NWG/RFC 110.
• RFC141: Comments on RFC 114: A File Transfer Protocol.
• RFC145: Initial Connection Protocol Control Commands.
• RFC146: Views on issues relevant to data sharing on computer networks.
• RFC148: Comments on RFC 123.
• RFC151: Comments on a proffered official ICP: RFCs 123, 127.
• RFC155: ARPA Network mailing lists.
• RFC156: Status of the Illinois site: Response to RFC 116.
• RFC160: RFC brief list. Network Information Center. Stanford Research Institute.
• RFC161: Solution to the race condition in the
• RFC164: Minutes of Network Working Group meeting, 5/16 through 5/19/71.
• RFC168: ARPA Network mailing lists.
• RFC170: RFC List by Number. Network Information Center. Stanford Research Institute.
• RFC174: UCLA - Computer Science Graphics Overview.
• RFC175: Comments on "Socket Conventions Reconsidered".
• RFC181: Modifications to RFC 177.
• RFC182: Compilation of list of relevant site reports.
• RFC185: NIC distribution of manuals and handbooks.
• RFC191: Graphics implementation and conceptualization at Augmentation Research Center.
• RFC194: The Data Reconfiguration Service -- Compiler/Interpreter Implementation Notes.
• RFC198: Site Certification - Lincoln Labs 360/67.
• RFC200: RFC list by number.
• RFC217: Specifications changes for OLS, RJE/RJOR, and
• RFC227: Data transfer rates (Rand/UCLA).
• RFC228: Clarification.
• RFC232: Postponement of network graphics meeting.
• RFC233: Standardization of host call letters.
• RFC238: Comments on DTP and FTP proposals.
• RFC239: Host mnemonics proposed in RFC 226 (NIC 7625).
• RFC247: Proffered set of standard host names.
• RFC252: Network host status.
• RFC255: Status of network hosts.
• RFC256: IMPSYS change notification.
• RFC266: Network host status.
• RFC267: Network Host Status.
• RFC276: NIC course.
• RFC278: Revision of the Mail Box Protocol.
• RFC280: A Draft of Host Names.
• RFC289: What we hope is an official list of host names.
• RFC295: Report of the Protocol Workshop, 12 October 1971.
• RFC300: ARPA Network mailing lists.
• RFC302: Exercising The
• RFC303: ARPA Network mailing lists. Network Information Center. Stanford Research Institute.
• RFC305: Unknown Host Numbers.
• RFC309: Data and File Transfer Workshop Announcement.
• RFC321: CBI Networking Activity at
• RFC329: ARPA Network Mailing Lists. Network Information Center. Stanford Research Institute.
• RFC331: IMP System Change Notification.
• RFC334: Network Use on May 8.
• RFC335: New Interface - IMP/360.
• RFC340: Proposed Telnet Changes.
• RFC343: IMP System change notification.
• RFC346: Satellite Considerations.
• RFC350: User Accounts for UCSB On-Line System.
• RFC352: TIP Site Information Form.
• RFC355: Response to NWG/RFC 346.
• RFC359: Status of the Release of the New IMP System (2600).
• RFC361: Deamon Processes on Host 106.
• RFC363: ARPA Network mailing lists. Network Information Center. Stanford Research Institute.
• RFC371: Demonstration at International Computer Communications Conference.
• RFC372: Notes on a Conversation with Bob Kahn on the
• RFC376: Network Host Status.
• RFC382: Mathematical Software on the ARPA Network.
• RFC385: Comments on the File Transfer Protocol.
• RFC387: Some experiences in implementing Network Graphics Protocol Level 0.
• RFC388: NCP statistics.
• RFC395: Switch Settings on IMPs and TIPs.
• RFC396: Network Graphics Working Group Meeting - Second Iteration.
• RFC398: ICP Sockets.
• RFC399: SMFS Login and Logout.
• RFC402: ARPA Network Mailing Lists.
• RFC404: Host Address Changes Involving Rand and
• RFC405: Correction to RFC 404.
• RFC408: NETBANK.
• RFC414: File Transfer Protocol (FTP) status and further comments.
• RFC429: Character Generator Process.
• RFC430: Comments on File Transfer Protocol.
• RFC431: Update on SMFS Login and Logout.
• RFC433: Socket number list.
• RFC434: IMP/TIP memory retrofit schedule.
• RFC435: Telnet issues.
• RFC436: Announcement of RJS at
• RFC438: FTP server-server interaction.
• RFC440: Scheduled network software maintenance.
• RFC445: IMP/TIP preventive maintenance schedule.
• RFC446: Proposal to consider a network program resource notebook.
• RFC447: IMP/TIP memory retrofit schedule.
• RFC448: Print files in
• RFC449: Current flow-control scheme for
• RFC453: Meeting announcement to discuss a network mail system.
• RFC456: Memorandum: Date change of mail meeting.
• RFC457: TIPUG.
• RFC459: Network questionnaires.
• RFC460: NCP survey.
• RFC461: Telnet Protocol meeting announcement.
• RFC462: Responding to user needs.
• RFC463: FTP comments and response to RFC 430.
• RFC464: Resource notebook framework.
• RFC472: Illinois' reply to Maxwell's request for graphics information (NIC 14925).
• RFC474: Announcement of NGWG meeting: Call for papers.
• RFC476: IMP/TIP memory retrofit schedule (rev 2).
• RFC478: FTP server-server interaction -
• RFC480: Host-dependent FTP parameters.
• RFC483: Cancellation of the resource notebook framework meeting.
• RFC485: MIX and MIXAL at
• RFC486: Data transfer revisited.
• RFC488: NLS classes at network sites.
• RFC490: Surrogate RJS for UCLA-CCN.
• RFC491: What is "Free"?.
• RFC492: Response to RFC 467.
• RFC494: Availability of MIX and MIXAL in the Network.
• RFC496: TNLS quick reference card is available.
• RFC504: Distributed resources workshop announcement.
• RFC505: Two solutions to a file transfer access problem.
• RFC513: Comments on the new Telnet specifications.
• RFC514: Network make-work.
• RFC523: SURVEY is in operation again.
• RFC531: Feast or famine? A response to two recent RFC's about network information.
• RFC534: Lost message detection.
• RFC539: Thoughts on the mail protocol proposed in RFC 524.
• RFC545: Of what quality be the UCSB resources evaluators?.
• RFC548: Hosts using the IMP Going Down message.
• RFC552: Single access to standard protocols.
• RFC555: Responses to critiques of the proposed mail protocol.
• RFC561: Standardizing Network Mail Headers.
• RFC568: Response to RFC 567 - cross country network bandwidth.
• RFC580: Note to Protocol Designers and Implementers.
• RFC582: Comments on RFC 580: Machine readable protocols.
• RFC599: Update on
• RFC601: Traffic statistics (November 1973).
• RFC603: Response to RFC 597: Host status.
• RFC608: Host names on-line.
• RFC613: Network connectivity: A response to RFC 603.
• RFC621: NIC user directories at SRI
• RFC623: Comments on on-line host name service.
• RFC625: On-line hostnames service.
• RFC627: ASCII text file of hostnames.
• RFC628: Status of RFC numbers and a note on pre-assigned journal numbers.
• RFC634: Change in network address for Haskins Lab.
• RFC637: Change of network address for SU-DSL.
• RFC638: IMP/TIP preventive maintenance schedule.
• RFC659: Announcing additional Telnet options.
• RFC683: FTPSRV - Tenex extension for paged files.
• RFC688: Tentative schedule for the new Telnet implementation for the
• RFC690: Comments on the proposed Host/IMP Protocol changes.
• RFC691: One more try on the
• RFC692: Comments on IMP/Host Protocol changes (RFCs 687 and 690).
• RFC699: Request For Comments summary notes: 600-699.
• RFC736: Telnet SUPDUP option.
• RFC739: Assigned numbers.
• RFC747: Recent extensions to the SUPDUP Protocol.
• RFC750: Assigned numbers.
• RFC755: Assigned numbers.
• RFC757: Suggested solution to the naming, addressing, and delivery problem for ARPANET message systems.
• RFC758: Assigned numbers.
• RFC762: Assigned numbers.
• RFC768: User Datagram Protocol.
• RFC770: Assigned numbers.
• RFC775: Directory oriented FTP commands.
• RFC776: Assigned numbers.
• RFC777: Internet Control Message Protocol.
• RFC790: Assigned numbers.
• RFC800: Request For Comments summary notes: 700-799.
• RFC810: DoD Internet host table specification.
• RFC811: Hostnames Server.
• RFC812: NICNAME/WHOIS.
• RFC820: Assigned numbers.
• RFC825: Request for comments on Requests For Comments.
• RFC840: Official protocols.
• RFC847: Summary of Smallberg surveys.
• RFC870: Assigned numbers.
• RFC873: Illusion of vendor support.
• RFC874: Critique of X.25.
• RFC880: Official protocols.
• RFC882: Domain names: Concepts and facilities.
• RFC894: Standard for the transmission of IP datagrams over Ethernet networks.
• RFC895: Standard for the transmission of IP datagrams over experimental Ethernet networks.
• RFC899: Request For Comments summary notes: 800-899.
• RFC900: Assigned Numbers.
• RFC901: Official ARPA-Internet protocols.
• RFC906: Bootstrap loading using
• RFC921: Domain name system implementation schedule - revised.
• RFC923: Assigned numbers.
• RFC924: Official ARPA-Internet protocols for connecting personal computers to the Internet.
• RFC937: Post Office Protocol: Version 2.
• RFC940: Toward an Internet standard scheme for subnetting. Gateway Algorithms and Data Structures Task Force.
• RFC943: Assigned numbers.
• RFC944: Official ARPA-Internet protocols.
• RFC952: DoD Internet host table specification.
• RFC953: Hostname Server.
• RFC954: NICNAME/WHOIS.
• RFC959: File Transfer Protocol.
• RFC960: Assigned numbers.
• RFC961: Official ARPA-Internet protocols.
• RFC967: All victims together.
• RFC976: UUCP mail interchange format standard.
• RFC980: Protocol document order information.
• RFC985: Requirements for Internet gateways - draft. National Science Foundation, Network Technical Advisory Group.
• RFC987: Mapping between X.400 and RFC 822.
• RFC989: Privacy enhancement for Internet electronic mail: Part I: Message encipherment and authentication procedures.
• RFC990: Assigned numbers.
• RFC991: Official ARPA-Internet protocols.
• RFC999: Requests For Comments summary notes: 900-999.
• RFC1000: Request For Comments reference guide.
• RFC1010: Assigned numbers.
• RFC1011: Official Internet protocols.
• RFC1012: Bibliography of Request For Comments 1 through 999.
• RFC1018: Some comments on SQuID.
• RFC1020: Internet numbers.
• RFC1023: HEMS monitoring and control language.
• RFC1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822).
• RFC1031: MILNET name domain transition.
• RFC1032: Domain administrators guide.
• RFC1033: Domain administrators operations guide.
• RFC1034: Domain names - concepts and facilities.
• RFC1035: Domain names - implementation and specification.
• RFC1036: Standard for interchange of USENET messages.
• RFC1040: Privacy enhancement for Internet electronic mail: Part I: Message encipherment and authentication procedures.
• RFC1060: Assigned numbers.
• RFC1062: Internet numbers.
• RFC1064: Interactive Mail Access Protocol: Version 2.
• RFC1069: Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol.
• RFC1083: IAB official protocol standards. Defense Advanced Research Projects Agency, Internet Activities Board.
• RFC1084: BOOTP vendor information extensions.
• RFC1099: Request for Comments Summary: RFC Numbers 1000-1099.
• RFC1100: IAB official protocol standards. Defense Advanced Research Projects Agency, Internet Activities Board.
• RFC1101: DNS encoding of network names and other types.
• RFC1109: Report of the second Ad Hoc Network Management Review Group.
• RFC1111: Request for comments on Request for Comments: Instructions to RFC authors.
• RFC1113: Privacy enhancement for Internet electronic mail: Part I - message encipherment and authentication procedures.
• RFC1114: Privacy enhancement for Internet electronic mail: Part II - certificate-based key management.
• RFC1115: Privacy enhancement for Internet electronic mail: Part III - algorithms, modes, and identifiers.
• RFC1118: Hitchhikers guide to the Internet.
• RFC1120: Internet Activities Board.
• RFC1123: Requirements for Internet Hosts - Application and Support.
• RFC1127: Perspective on the Host Requirements RFCs.
• RFC1128: Measured performance of the Network Time Protocol in the Internet system.
• RFC1130: IAB official protocol standards. Defense Advanced Research Projects Agency, Internet Activities Board.
• RFC1131: OSPF specification.
• RFC1137: Mapping between full RFC 822 and RFC 822 with restricted encoding.
• RFC1138: Mapping between X.400(1988) / ISO 10021 and RFC 822.
• RFC1140: IAB official protocol standards. Defense Advanced Research Projects Agency, Internet Activities Board.
• RFC1141: Incremental updating of the Internet checksum.
• RFC1143: The Q Method of Implementing TELNET Option Negotiation.
• RFC1148: Mapping between X.400(1988) / ISO 10021 and RFC 822.
• RFC1150: FYI on FYI: Introduction to the FYI Notes.
• RFC1151: Version 2 of the Reliable Data Protocol (RDP).
• RFC1154: Encoding header field for internet messages.
• RFC1160: Internet Activities Board.
• RFC1175: FYI on where to start: A bibliography of internetworking information.
• RFC1176: Interactive Mail Access Protocol: Version 2.
• RFC1177: FYI on Questions and Answers: Answers to commonly asked "new internet user" questions.
• RFC1183: New DNS RR Definitions.
• RFC1184: Telnet Linemode Option.
• RFC1194: Finger User Information Protocol.
• RFC1196: Finger User Information Protocol.
• RFC1199: Request for Comments Summary Notes: 1100-1199.
• RFC1200: IAB official protocol standards. Defense Advanced Research Projects Agency, Internet Activities Board.
• RFC1201: Transmitting IP traffic over ARCNET networks.
• RFC1203: Interactive Mail Access Protocol: Version 3.
• RFC1205: 5250 Telnet interface.
• RFC1206: FYI on Questions and Answers: Answers to commonly asked "new Internet user" questions.
• RFC1207: FYI on Questions and Answers: Answers to commonly asked "experienced Internet user" questions.
• RFC1229: Extensions to the generic-interface
• RFC1239: Reassignment of experimental MIBs to standard MIBs.
• RFC1248: OSPF Version 2 Management Information Base.
• RFC1250: IAB Official Protocol Standards.
• RFC1251: Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members.
• RFC1252: OSPF Version 2 Management Information Base.
• RFC1253: OSPF Version 2 Management Information Base.
• RFC1263: TCP Extensions Considered Harmful.
• RFC1276: Replication and Distributed Operations extensions to provide an Internet Directory using X.500.
• RFC1277: Encoding Network Addresses to Support Operation over Non-OSI Lower Layers.
• RFC1280: IAB Official Protocol Standards.
• RFC1283: SNMP over
• RFC1288: The Finger User Information Protocol.
• RFC1290: There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places.
• RFC1291: Mid-Level Networks Potential Technical Services.
• RFC1299: Summary of 1200-1299.
• RFC1304: Definitions of Managed Objects for the SIP Interface Type.
• RFC1311: Introduction to the STD Notes.
• RFC1315: Management Information Base for Frame Relay DTEs.
• RFC1316: Definitions of Managed Objects for Character Stream Devices.
• RFC1323: TCP Extensions for High Performance.
• RFC1325: FYI on Questions and Answers Answers to Commonly asked "New Internet User" Questions.
• RFC1327: Mapping between X.400(1988) / ISO 10021 and RFC 822.
• RFC1328: X.400 1988 to 1984 downgrading.
• RFC1332: The PPP Internet Protocol Control Protocol (IPCP).
• RFC1336: Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members.
• RFC1340: Assigned Numbers.
• RFC1341: MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies.
• RFC1348: DNS NSAP RRs.
• RFC1349: Type of Service in the Internet Protocol Suite.
• RFC1356: Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode.
• RFC1359: Connecting to the Internet - What Connecting Institutions Should Anticipate. ACM SIGUCCS.
• RFC1360: IAB Official Protocol Standards.
• RFC1361: Simple Network Time Protocol (SNTP).
• RFC1389: RIP Version 2 MIB Extensions.
• RFC1390: Transmission of IP and ARP over FDDI Networks.
• RFC1391: The Tao of the IETF: A Guide for New Attendees of the Internet Engineering Task Force.
• RFC1395: BOOTP Vendor Information Extensions.
• RFC1398: Definitions of Managed Objects for the Ethernet-Like Interface Types.
• RFC1399: Summary of 1300-1399.
• RFC1402: There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places.
• RFC1410: IAB Official Protocol Standards.
• RFC1414: Identification
• RFC1418: SNMP over
• RFC1420: SNMP over
• RFC1421: Privacy Enhancement for Internet Electronic Mail: Part I: Message Encryption and Authentication Procedures.
• RFC1422: Privacy Enhancement for Internet Electronic Mail: Part II: Certificate-Based Key Management.
• RFC1425: SMTP Service Extensions. J. Klensin, WG Chair,
• RFC1426: SMTP Service Extension for 8bit-MIMEtransport. J. Klensin, WG Chair,
• RFC1430: A Strategic Plan for Deploying an Internet X.500 Directory Service.
• RFC1455: Physical Link Security Type of Service.
• RFC1460: Post Office Protocol - Version 3.
• RFC1461: SNMP MIB extension for Multiprotocol Interconnect over X.25.
• RFC1471: The Definitions of Managed Objects for the Link Control Protocol of the Point-to-Point Protocol.
• RFC1487: X.500 Lightweight Directory Access Protocol.
• RFC1494: Equivalences between 1988 X.400 and RFC-822 Message Bodies.
• RFC1495: Mapping between X.400 and RFC-822 Message Bodies.
• RFC1496: Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messages.
• RFC1497: BOOTP Vendor Information Extensions.
• RFC1499: Summary of 1400-1499.
• RFC1500: Internet Official Protocol Standards.
• RFC1502: X.400 Use of Extended Character Sets.
• RFC1506: A Tutorial on Gatewaying between X.400 and Internet Mail.
• RFC1515: Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs).
• RFC1517: Applicability Statement for the Implementation of Classless Inter-Domain Routing (CIDR). Internet Engineering Steering Group,
• RFC1521: MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies.
• RFC1533: DHCP Options and BOOTP Vendor Extensions.
• RFC1539: The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force.
• RFC1540: Internet Official Protocol Standards.
• RFC1543: Instructions to RFC Authors.
• RFC1550: IP: Next Generation (IPng) White Paper Solicitation.
• RFC1561: Use of ISO CLNP in TUBA Environments.
• RFC1578: FYI on Questions and Answers - Answers to Commonly Asked "Primary and Secondary School Internet User" Questions.
• RFC1594: FYI on Questions and Answers - Answers to Commonly asked "New Internet User" Questions.
• RFC1599: Summary of 1500-1599.
• RFC1600: Internet Official Protocol Standards.
• RFC1602: The Internet Standards Process -- Revision 2. Internet Architecture Board, Internet Engineering Steering Group.
• RFC1610: Internet Official Protocol Standards.
• RFC1616: X.400(1988) for the Academic and Research Community in Europe. RARE WG-MSG Task Force 88,
• RFC1624: Computation of the Internet Checksum via Incremental Update.
• RFC1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified).
• RFC1632: A Revised Catalog of Available X.500 Implementations.
• RFC1648: Postmaster Convention for X.400 Operations.
• RFC1649: Operational Requirements for X.400 Management Domains in the GO-MHS Community.
• RFC1699: Summary of 1600-1699.
• RFC1700: Assigned Numbers.
• RFC1701: Generic Routing Encapsulation (GRE).
• RFC1718: The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force. IETF Secretariat,
• RFC1720: Internet Official Protocol Standards.
• RFC1721: RIP Version 2 Protocol Analysis.
• RFC1738: Uniform Resource Locators (URL).
• RFC1739: A Primer On Internet and TCP/IP Tools.
• RFC1755: ATM Signaling Support for IP over
• RFC1780: Internet Official Protocol Standards.
• RFC1796: Not All RFCs are Standards.
• RFC1799: Request for Comments Summary RFC Numbers 1700-1799.
• RFC1800: Internet Official Protocol Standards.
• RFC1806: Communicating Presentation Information in Internet Messages: The Content-Disposition Header.
• RFC1810: Report on MD5 Performance.
• RFC1814: Unique Addresses are Good.
• RFC1818: Best Current Practices.
• RFC1828: IP Authentication using Keyed MD5.
• RFC1838: Use of the X.500 Directory to support mapping between X.400 and RFC 822 Addresses.
• RFC1876: A Means for Expressing Location Information in the Domain Name System.
• RFC1879: Class A Subnet Experiment Results and Recommendations.
• RFC1880: Internet Official Protocol Standards.
• RFC1899: Request for Comments Summary RFC Numbers 1800-1899.
• RFC1912: Common DNS Operational and Configuration Errors.
• RFC1915: Variance for The PPP Compression Control Protocol and The PPP Encryption Control Protocol.
• RFC1920: Internet Official Protocol Standards.
• RFC1983: Internet Users' Glossary.
• RFC1999: Request for Comments Summary RFC Numbers 1900-1999.
• RFC2034: SMTP Service Extension for Returning Enhanced Error Codes.
• RFC2042: Registering New BGP Attribute Types.
• RFC2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies.
• RFC2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types.
• RFC2048: Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures.
• RFC2049: Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples.
• RFC2074: Remote Network Monitoring MIB Protocol Identifiers.
• RFC2076: Common Internet Message Headers.
• RFC2099: Request for Comments Summary RFC Numbers 2000-2099.
• RFC2101: IPv4 Address Behaviour Today.
• RFC2110: MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML).
• RFC2116: X.500 Implementations Catalog-96.
• RFC2119: Key words for use in RFCs to Indicate Requirement Levels.
• RFC2130: The Report of the IAB Character Set Workshop held 29 February - 1 March, 1996.
• RFC2151: A Primer On Internet and TCP/IP Tools and Utilities.
• RFC2152: UTF-7 A Mail-Safe Transformation Format of Unicode.
• RFC2156: MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME.
• RFC2157: Mapping between X.400 and RFC-822/MIME Message Bodies.
• RFC2164: Use of an X.500/LDAP directory to support MIXER address mapping.
• RFC2183: Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field.
• RFC2184: MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations.
• RFC2200: Internet Official Protocol Standards.
• RFC2219: Use of DNS Aliases for Network Services.
• RFC2223: Instructions to RFC Authors.
• RFC2231: MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations.
• RFC2237: Japanese Character Encoding for Internet Messages.
• RFC2252: Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions.
• RFC2255: The LDAP URL Format.
• RFC2278: IANA Charset Registration Procedures.
• RFC2299: Request for Comments Summary.
• RFC2360: Guide for Internet Standards Writers.
• RFC2368: The mailto URL scheme.
• RFC2400: Internet Official Protocol Standards.
• RFC2403: The Use of HMAC-MD5-96 within ESP and
• RFC2434: Guidelines for Writing an IANA Considerations Section in RFCs.
• RFC2442: The Batch SMTP Media Type.
• RFC2447: iCalendar Message-Based Interoperability Protocol (iMIP).
• RFC2484: PPP LCP Internationalization Configuration Option.
• RFC2499: Request for Comments Summary.
• RFC2537: RSA/MD5 KEYs and SIGs in the Domain Name System (DNS).
• RFC2555: 30 Years of RFCs. RFC Editor, et al..
• RFC2556: OSI connectionless transport services on top of UDP Applicability Statement for Historic Status.
• RFC2591: Definitions of Managed Objects for Scheduling Management Operations.
• RFC2599: Request for Comments Summary RFC Numbers 2500-2599.
• RFC2600: Internet Official Protocol Standards.
• RFC2624: NFS Version 4 Design Considerations.
• RFC2626: The Internet and the Millennium Problem (Year 2000).
• RFC2629: Writing I-Ds and RFCs using
• RFC2683: IMAP4 Implementation Recommendations.
• RFC2699: Request for Comments Summary RFC Numbers 2600-2699.
• RFC2700: Internet Official Protocol Standards.
• RFC2718: Guidelines for new URL Schemes.
• RFC2758: Definitions of Managed Objects for Service Level Agreements Performance Monitoring.
• RFC2775: Internet Transparency.
• RFC2784: Generic Routing Encapsulation (GRE).
• RFC2799: Request for Comments Summary RFC Numbers 2700-2799.
• RFC2800: Internet Official Protocol Standards.
• RFC2821: Simple Mail Transfer Protocol.
• RFC2828: Internet Security Glossary.
• RFC2831: Using Digest Authentication as a SASL Mechanism.
• RFC2850: Charter of the Internet Architecture Board (IAB). Internet Architecture Board,
• RFC2851: Textual Conventions for Internet Network Addresses.
• RFC2854: The 'text/html' Media Type.
• RFC2868: RADIUS Attributes for Tunnel Protocol Support.
• RFC2877: 5250 Telnet Enhancements. T. Murphy, Jr.,
• RFC2896: Remote Network Monitoring MIB Protocol Identifier Macros.
• RFC2899: Request for Comments Summary RFC Numbers 2800-2899.
• RFC2900: Internet Official Protocol Standards.
• RFC2901: Guide to Administrative Procedures of the Internet Infrastructure.
• RFC2929: Domain Name System (DNS) IANA Considerations.
• RFC2935: Internet Open Trading Protocol (IOTP) HTTP Supplement.
• RFC2959: Real-Time Transport Protocol Management Information Base.
• RFC2978: IANA Charset Registration Procedures.
• RFC2980: Common NNTP Extensions.
• RFC2989: Criteria for Evaluating AAA Protocols for Network Access. B. Aboba, P. Calhoun, S. Glass, T. Hiller, P. McCann, H. Shiino, G. Zorn, G. Dommety, C.Perkins,B.Patil,D.Mitton,S.Manning,M.Beadles,P.Walsh,X.Chen,S.Sivalingham, A.Hameed,M.Munson,S.Jacobs,B.Lim,B.Hirschman, R.Hsu, Y.Xu, E.Campell, S.Baba, E.Jaques.
• RFC2993: Architectural Implications of
• RFC2999: Request for Comments Summary RFC Numbers 2900-2999.
• RFC3000: Internet Official Protocol Standards.
• RFC3013: Recommended Internet Service Provider Security Services and Procedures.
• RFC3071: Reflections on the DNS, RFC 1591, and Categories of Domains.
• RFC3090: DNS Security Extension Clarification on Zone Status.
• RFC3092: Etymology of "Foo".
• RFC3097: RSVP Cryptographic Authentication -- Updated Message Type Value.
• RFC3099: Request for Comments Summary RFC Numbers 3000-3099.
• RFC3117: On the Design of Application Protocols.
• RFC3130: Notes from the State-Of-The-Technology:
• RFC3138: Extended Assignments in 233/8.
• RFC3140: Per Hop Behavior Identification Codes.
• RFC3144: Remote Monitoring MIB Extensions for Interface Parameters Monitoring.
• RFC3160: The Tao of IETF - A Novice's Guide to the Internet Engineering Task Force.
• RFC3166: Request to Move RFC 1403 to Historic Status.
• RFC3167: Request to Move RFC 1745 to Historic Status.
• RFC3176: InMon Corporation's sFlow: A Method for Monitoring Traffic in Switched and Routed Networks.
• RFC3178: IPv6 Multihoming Support at Site Exit Routers.
• RFC3180: GLOP Addressing in 233/8.
• RFC3199: Request for Comments Summary RFC Numbers 3100-3199.
• RFC3231: Definitions of Managed Objects for Scheduling Management Operations.
• RFC3232: Assigned Numbers: RFC 1700 is Replaced by an On-line Database.
• RFC3234: Middleboxes: Taxonomy and Issues.
• RFC3245: The History and Context of Telephone Number Mapping (ENUM) Operational Decisions: Informational Documents Contributed to ITU-T Study Group 2 (SG2).
• RFC3248: A Delay Bound alternative revision of RFC 2598.
• RFC3249: Implementers Guide for Facsimile Using Internet Mail.
• RFC3260: New Terminology and Clarifications for Diffserv.
• RFC3282: Content Language Headers.
• RFC3283: Guide to Internet Calendaring.
• RFC3285: Using Microsoft Word to create Internet Drafts and RFCs.
• RFC3289: Management Information Base for the Differentiated Services Architecture.
• RFC3291: Textual Conventions for Internet Network Addresses.
• RFC3299: Request for Comments Summary RFC Numbers 3200-3299.
• RFC3300: Internet Official Protocol Standards.
• RFC3305: Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations.
• RFC3316: Internet Protocol Version 6 (IPv6) for Some Second and Third Generation Cellular Hosts.
• RFC3335: MIME-based Secure Peer-to-Peer Business Data Interchange over the Internet.
• RFC3354: Internet Open Trading Protocol Version 2 Requirements.
• RFC3356: Internet Engineering Task Force and International Telecommunication Union - Telecommunications Standardization Sector Collaboration Guidelines.
• RFC3377: Lightweight Directory Access Protocol (v3): Technical Specification.
• RFC3401: Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive
• RFC3406: Uniform Resource Names (URN) Namespace Definition Mechanisms.
• RFC3417: Transport Mappings for the Simple Network Management Protocol (SNMP).
• RFC3458: Message Context for Internet Mail.
• RFC3468: The Multiprotocol Label Switching (MPLS) Working Group decision on MPLS signaling protocols.
• RFC3481: TCP over Second (2.5G) and Third (3G) Generation Wireless Networks.
• RFC3494: Lightweight Directory Access Protocol version 2 (LDAPv2) to Historic Status.
• RFC3499: Request for Comments Summary RFC Numbers 3400-3499.
• RFC3501: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1.
• RFC3503: Message Disposition Notification (MDN) profile for Internet Message Access Protocol (IMAP).
• RFC3520: Session Authorization Policy Element.
• RFC3525: Gateway Control Protocol Version 1.
• RFC3551: RTP Profile for Audio and Video Conferences with Minimal Control.
• RFC3553: An IETF URN Sub-namespace for Registered Protocol Parameters.
• RFC3555: MIME Type Registration of RTP Payload Formats.
• RFC3562: Key Management Considerations for the TCP MD5 Signature Option.
• RFC3599: Request for Comments Summary RFC Numbers 3500-3599.
• RFC3600: Internet Official Protocol Standards.
• RFC3632: VeriSign Registry Registrar Protocol (RRP) Version 2.0.0.
• RFC3638: Applicability Statement for Reclassification of RFC 1643 to Historic Status.
• RFC3655: Redefinition of DNS Authenticated Data (AD) bit.
• RFC3667: IETF Rights in Contributions.
• RFC3668: Intellectual Property Rights in IETF Technology.
• RFC3675: .sex Considered Dangerous.
• RFC3679: Unused Dynamic Host Configuration Protocol (DHCP) Option Codes.
• RFC3700: Internet Official Protocol Standards.
• RFC3705: High Capacity Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals.
• RFC3716: The IETF in the Large: Administration and Execution. IAB Advisory Committee.
• RFC3761: The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM).
• RFC3764: enumservice registration for Session Initiation Protocol (SIP) Addresses-of-Record.
• RFC3787: Recommendations for Interoperable IP Networks using Intermediate System to Intermediate System (IS-IS).
• RFC3790: Survey of IPv4 Addresses in Currently Deployed IETF Internet Area Standards Track and Experimental Documents.
• RFC3791: Survey of IPv4 Addresses in Currently Deployed IETF Routing Area Standards Track and Experimental Documents.
• RFC3792: Survey of IPv4 Addresses in Currently Deployed IETF Security Area Standards Track and Experimental Documents.
• RFC3793: Survey of IPv4 Addresses in Currently Deployed IETF Sub-IP Area Standards Track and Experimental Documents.
• RFC3794: Survey of IPv4 Addresses in Currently Deployed IETF Transport Area Standards Track and Experimental Documents.
• RFC3795: Survey of IPv4 Addresses in Currently Deployed IETF Application Area Standards Track and Experimental Documents.
• RFC3796: Survey of IPv4 Addresses in Currently Deployed IETF Operations & Management Area Standards Track and Experimental Documents.
• RFC3797: Publicly Verifiable Nominations Committee (NomCom) Random Selection.
• RFC3805: Printer MIB v2.
• RFC3828: The Lightweight User Datagram Protocol (UDP-Lite).
• RFC3856: A Presence Event Package for the Session Initiation Protocol (SIP).
• RFC3861: Address Resolution for Instant Messaging and Presence.
• RFC3864: Registration Procedures for Message Header Fields.
• RFC3869: IAB Concerns and Recommendations Regarding Internet Research and Evolution. R. Atkinson, Ed., S. Floyd, Ed., Internet Architecture Board.
• RFC3885: SMTP Service Extension for Message Tracking.
• RFC3886: An Extensible Message Format for Message Tracking Responses.
• RFC3919: Remote Network Monitoring (RMON) Protocol Identifiers for IPv6 and Multi Protocol Label Switching (MPLS).
• RFC3932: The IESG and RFC Editor Documents: Procedures.
• RFC3934: Updates to RFC 2418 Regarding the Management of IETF Mailing Lists.
• RFC3942: Reclassifying Dynamic Host Configuration Protocol version 4 (DHCPv4) Options.
• RFC3944: H.350 Directory Services.
• RFC3967: Clarifying when Standards Track Documents may Refer Normatively to Documents at a Lower Level.
• RFC3968: The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP).
• RFC3969: The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP).
• RFC3974: SMTP Operational Experience in Mixed IPv4/v6 Environments.
• RFC3978: IETF Rights in Contributions.
• RFC3979: Intellectual Property Rights in IETF Technology.
• RFC4001: Textual Conventions for Internet Network Addresses.
• RFC4021: Registration of Mail and MIME Header Fields.
• RFC4025: A Method for Storing IPsec Keying Material in
• RFC4027: Domain Name System Media Types.
• RFC4032: Update to the Session Initiation Protocol (SIP) Preconditions Framework.
• RFC4048: RFC 1888 Is Obsolete.
• RFC4083: Input 3rd-Generation Partnership Project (3GPP) Release 5 Requirements on the Session Initiation Protocol (SIP).
• RFC4095: Attaching Meaning to Solicitation Class Keywords.
• RFC4102: Registration of the text/red MIME Sub-Type.
• RFC4115: A Differentiated Service Two-Rate, Three-Color Marker with Efficient Handling of in-Profile Traffic.
• RFC4123: Session Initiation Protocol (SIP)-H.323 Interworking Requirements.
• RFC4130: MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2 (AS2).
• RFC4149: Definition of Managed Objects for Synthetic Sources for Performance Monitoring Algorithms.
• RFC4155: The application/mbox Media Type.
• RFC4180: Common Format and MIME Type for Comma-Separated Values (CSV) Files.
• RFC4181: Guidelines for Authors and Reviewers of MIB Documents.
• RFC4183: A Suggested Scheme for DNS Resolution of Networks and Gateways.
• RFC4214: Intra-Site Automatic Tunnel Addressing Protocol (ISATAP).
• RFC4217: Securing FTP with
• RFC4223: Reclassification of RFC 1863 to Historic.
• RFC4240: Basic Network Media Services with
• RFC4241: A Model of IPv6/IPv4 Dual Stack Internet Access Service.
• RFC4263: Media Subtype Registration for Media Type text/troff.
• RFC4273: Definitions of Managed Objects for BGP-4.
• RFC4278: Standards Maturity Variance Regarding the TCP MD5 Signature Option (RFC 2385) and the BGP-4 Specification.
• RFC4282: The Network Access Identifier.
• RFC4290: Suggested Practices for Registration of Internationalized Domain Names (IDN).
• RFC4294: IPv6 Node Requirements.
• RFC4314: IMAP4 Access Control List (ACL) Extension.
• RFC4367: What's in a Name: False Assumptions about DNS Names.
• RFC4398: Storing Certificates in the Domain Name System (DNS).
• RFC4407: Purported Responsible Address in E-Mail Messages.
• RFC4416: Goals for Internet Messaging to Support Diverse Service Environments.
• RFC4424: Real-Time Transport Protocol (RTP) Payload Format for the Variable-Rate Multimode Wideband (VMR-WB) Extension Audio Codec.
• RFC4450: Getting Rid of the Cruft: Report from an Experiment in Identifying and Reclassifying Obsolete Standards Documents.
• RFC4466: Collected Extensions to IMAP4
• RFC4468: Message Submission BURL Extension.
• RFC4470: Minimally Covering NSEC Records and DNSSEC On-line Signing.
• RFC4485: Guidelines for Authors of Extensions to the Session Initiation Protocol (SIP).
• RFC4501: Domain Name System Uniform Resource Identifiers.
• RFC4510: Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map.
• RFC4512: Lightweight Directory Access Protocol (LDAP): Directory Information Models.
• RFC4515: Lightweight Directory Access Protocol (LDAP): String Representation of Search Filters.
• RFC4516: Lightweight Directory Access Protocol (LDAP): Uniform Resource Locator.
• RFC4520: Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP).
• RFC4521: Considerations for Lightweight Directory Access Protocol (LDAP) Extensions.
• RFC4524: COSINE LDAP/X.500 Schema.
• RFC4560: Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations.
• RFC4566: SDP: Session Description Protocol.
• RFC4569: Internet Assigned Number Authority (IANA) Registration of the Message Media Feature Tag.
• RFC4587: RTP Payload Format for H.261 Video Streams.
• RFC4614: A Roadmap for Transmission Control Protocol (TCP) Specification Documents.
• RFC4633: Experiment in Long-Term Suspensions From Internet Engineering Task Force (IETF) Mailing Lists.
• RFC4639: Cable Device Management Information Base for Data-Over-Cable Service Interface Specification (DOCSIS) Compliant Cable Modems and Cable Modem Termination Systems.
• RFC4648: The Base16, Base32, and Base64 Data Encodings.
• RFC4669: RADIUS Authentication Server MIB for IPv6.
• RFC4676: Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information.
• RFC4677: The Tao of IETF - A Novice's Guide to the Internet Engineering Task Force.
• RFC4693: IETF Operational Notes.
• RFC4713: Registration and Administration Recommendations for Chinese Domain Names.
• RFC4731: IMAP4 Extension to SEARCH Command for Controlling What Kind of Information Is Returned.
• RFC4748: RFC 3978 Update to Recognize the IETF Trust.
• RFC4769: IANA Registration for an Enumservice Containing Public Switched Telephone Network (PSTN) Signaling Information.
• RFC4776: Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information.
• RFC4789: Simple Network Management Protocol (SNMP) over IEEE 802 Networks.