January 2001

• RFC3019: IP Version 6 Management Information Base for The Multicast Listener Discovery Protocol.
• RFC3022: Traditional IP Network Address Translator (Traditional NAT).
• RFC3023: XML Media Types.
• RFC3024: Reverse Tunneling for Mobile IP, revised.
• RFC3026: Liaison to IETF/ISOC on
• RFC3027: Protocol Complications with the IP Network Address Translator.
• RFC3028: Sieve: A Mail Filtering Language.
• RFC3031: Multiprotocol Label Switching Architecture.
• RFC3032: MPLS Label Stack Encoding.
• RFC3033: 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.
• RFC3034: Use of Label Switching on Frame Relay Networks Specification.
• RFC3035: MPLS using LDP and ATM VC Switching.
• RFC3036: LDP Specification.
• RFC3037: LDP Applicability.
• RFC3038: VCID Notification over ATM link for
• RFC3039: Internet X.509 Public Key Infrastructure Qualified Certificates Profile.
• RFC3040: Internet Web Replication and Caching Taxonomy.
• RFC3041: Privacy Extensions for Stateless Address Autoconfiguration in IPv6.
• RFC3042: Enhancing TCP's Loss Recovery Using Limited Transmit.
• RFC3043: The Network Solutions Personal Internet Name (PIN): A URN Namespace for People and Organizations.
• RFC3044: Using The ISSN (International Serial Standard Number) as URN (Uniform Resource Names) within an ISSN-URN Namespace.
• RFC3045: Storing Vendor Information in the LDAP root
• RFC3046: DHCP Relay Agent Information Option.
• RFC3047: RTP Payload Format for ITU-T Recommendation G.722.1.
• RFC3048: Reliable Multicast Transport Building Blocks for One-to-Many Bulk-Data Transfer.
• RFC3049: TN3270E Service Location and Session Balancing.
• RFC3050: Common Gateway Interface for
• RFC3051: IP Payload Compression Using ITU-T V.44 Packet Method.
• RFC3052: Service Management Architectures Issues and Review.
• RFC3053: IPv6 Tunnel Broker.
• RFC3054: Megaco IP Phone Media Gateway Application Profile.
• RFC3066: Tags for the Identification of Languages.

February 2001

• RFC3025: Mobile IP Vendor/Organization-Specific Extensions.
• RFC3029: Internet X.509 Public Key Infrastructure Data Validation and Certification Server Protocols.
• RFC3055: Management Information Base for the PINT Services Architecture.
• RFC3056: Connection of IPv6 Domains via IPv4 Clouds.
• RFC3057: ISDN Q.921-User Adaptation Layer.
• RFC3058: Use of the IDEA Encryption Algorithm in
• RFC3059: Attribute List Extension for the Service Location Protocol.
• RFC3060: Policy Core Information Model -- Version 1 Specification.
• RFC3061: A URN Namespace of Object Identifiers.
• RFC3062: LDAP Password Modify Extended Operation.
• RFC3063: MPLS Loop Prevention Mechanism.
• RFC3064: MGCP CAS Packages.
• RFC3065: Autonomous System Confederations for
• RFC3067: TERENA'S Incident Object Description and Exchange Format Requirements.
• RFC3069: VLAN Aggregation for Efficient IP Address Allocation.
• RFC3070: Layer Two Tunneling Protocol (L2TP) over Frame Relay.
• RFC3071: Reflections on the DNS, RFC 1591, and Categories of Domains.
• RFC3074: DHC Load Balancing Algorithm.

March 2001

• RFC2919: List-Id: A Structured Field and Namespace for the Identification of Mailing Lists.
• RFC3072: Structured Data Exchange Format (SDXF).
• RFC3073: Portable Font Resource (PFR) - application/font-tdpfr MIME Sub-type Registration.
• RFC3075: XML-Signature Syntax and Processing.
• RFC3076: Canonical XML Version 1.0.
• RFC3077: A Link-Layer Tunneling Mechanism for Unidirectional Links.
• RFC3078: Microsoft Point-To-Point Encryption (MPPE) Protocol.
• RFC3079: Deriving Keys for use with Microsoft Point-to-Point Encryption (MPPE).
• RFC3080: The Blocks Extensible Exchange Protocol Core.
• RFC3081: Mapping the BEEP Core onto
• RFC3082: Notification and Subscription for
• RFC3083: Baseline Privacy Interface Management Information Base for DOCSIS Compliant Cable Modems and Cable Modem Termination Systems.
• RFC3084: COPS Usage for Policy Provisioning (COPS-PR).
• RFC3085: URN Namespace for NewsML Resources.
• RFC3090: DNS Security Extension Clarification on Zone Status.

April 2001

• RFC2821: Simple Mail Transfer Protocol.
• RFC2822: Internet Message Format.
• RFC2961: RSVP Refresh Overhead Reduction Extensions.
• RFC3086: Definition of Differentiated Services Per Domain Behaviors and Rules for their Specification.
• RFC3087: Control of Service Context using SIP Request-URI.
• RFC3088: OpenLDAP Root Service An experimental LDAP referral service.
• RFC3089: A SOCKS-based IPv6/IPv4 Gateway Mechanism.
• RFC3091: Pi Digit Generation Protocol.
• RFC3092: Etymology of "Foo".
• RFC3093: Firewall Enhancement Protocol (FEP).
• RFC3094: Tekelec's Transport Adapter Layer Interface.
• RFC3097: RSVP Cryptographic Authentication -- Updated Message Type Value.
• RFC3098: How to Advertise Responsibly Using E-Mail and Newsgroups or - how NOT to $$$$$ MAKE ENEMIES FAST! $$$$$.
• RFC3106: ECML v1.1: Field Specifications for E-Commerce.
• RFC3115: Mobile IP Vendor/Organization-Specific Extensions.

May 2001

• RFC2800: Internet Official Protocol Standards.
• RFC2899: Request for Comments Summary RFC Numbers 2800-2899.
• RFC3107: Carrying Label Information in BGP-4.
• RFC3108: Conventions for the use of the Session Description Protocol (SDP) for ATM Bearer Connections.
• RFC3109: Request to Move STD 39 to Historic Status.
• RFC3110: RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS).
• RFC3111: Service Location Protocol Modifications for IPv6.
• RFC3112: LDAP Authentication Password Schema.

June 2001

• RFC3068: An Anycast Prefix for 6to4 Relay Routers.
• RFC3113: 3GPP-IETF Standardization Collaboration.
• RFC3116: Methodology for ATM Benchmarking.
• RFC3118: Authentication for DHCP Messages.
• RFC3119: A More Loss-Tolerant RTP Payload Format for MP3 Audio.
• RFC3120: A URN Namespace for XML.org.
• RFC3121: A URN Namespace for
• RFC3122: Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification.
• RFC3123: A DNS RR Type for Lists of Address Prefixes (APL RR).
• RFC3124: The Congestion Manager.
• RFC3127: Authentication, Authorization, and Accounting: Protocol Evaluation.
• RFC3128: Protection Against a Variant of the Tiny Fragment Attack (RFC 1858).
• RFC3129: Requirements for Kerberized Internet Negotiation of Keys.
• RFC3130: Notes from the State-Of-The-Technology:
• RFC3131: 3GPP2-IETF Standardization Collaboration.
• RFC3132: Dormant Mode Host Alerting ("IP Paging") Problem Statement.
• RFC3133: Terminology for Frame Relay Benchmarking.
• RFC3134: Terminology for ATM ABR Benchmarking.
• RFC3135: Performance Enhancing Proxies Intended to Mitigate Link-Related Degradations.
• RFC3136: The SPIRITS Architecture.
• RFC3137: OSPF Stub Router Advertisement.
• RFC3138: Extended Assignments in 233/8.
• RFC3139: Requirements for Configuration Management of IP-based Networks.
• RFC3140: Per Hop Behavior Identification Codes.
• RFC3141: CDMA2000 Wireless Data Requirements for AAA. T. Hiller, P. Walsh, X. Chen, M. Munson, G. Dommety, S. Sivalingham, B. Lim, P. McCann, H. Shiino, B. Hirschman, S. Manning, R. Hsu, H. Koo, M. Lipford, P. Calhoun, C. Lo, E. Jaques, E. Campbell, Y.Xu,S.Baba,T.Ayaki,T.Seki,A.Hameed.
• RFC3142: An IPv6-to-IPv4 Transport Relay Translator.
• RFC3143: Known HTTP Proxy/Caching Problems.

July 2001

• RFC3095: RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed.
• RFC3096: Requirements for robust IP/UDP/RTP header compression.
• RFC3145: L2TP Disconnect Cause Information.
• RFC3147: Generic Routing Encapsulation over CLNS Networks.
• RFC3148: A Framework for Defining Empirical Bulk Transfer Capacity Metrics.
• RFC3150: End-to-end Performance Implications of Slow Links.

August 2001

• RFC2900: Internet Official Protocol Standards.
• RFC2999: Request for Comments Summary RFC Numbers 2900-2999.
• RFC3144: Remote Monitoring MIB Extensions for Interface Parameters Monitoring.
• RFC3151: A URN Namespace for Public Identifiers.
• RFC3152: Delegation of IP6.ARPA.
• RFC3153: PPP Multiplexing.
• RFC3154: Requirements and Functional Architecture for an IP Host Alerting Protocol.
• RFC3155: End-to-end Performance Implications of Links with Errors.
• RFC3156: MIME Security with OpenPGP.
• RFC3157: Securely Available Credentials - Requirements.
• RFC3158: RTP Testing Strategies.
• RFC3159: Structure of Policy Provisioning Information (SPPI).
• RFC3160: The Tao of IETF - A Novice's Guide to the Internet Engineering Task Force.
• RFC3161: Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP).
• RFC3162: RADIUS and IPv6.
• RFC3163: ISO/IEC 9798-3 Authentication SASL Mechanism.
• RFC3164: The BSD Syslog Protocol.
• RFC3165: Definitions of Managed Objects for the Delegation of Management Scripts.
• RFC3166: Request to Move RFC 1403 to Historic Status.
• RFC3167: Request to Move RFC 1745 to Historic Status.
• RFC3171: IANA Guidelines for IPv4 Multicast Address Assignments.

September 2001

• RFC3125: Electronic Signature Policies.
• RFC3126: Electronic Signature Formats for long term electronic signatures.
• RFC3149: MGCP Business Phone Packages.
• RFC3168: The Addition of Explicit Congestion Notification (ECN) to
• RFC3169: Criteria for Evaluating Network Access Server Protocols.
• RFC3170: IP Multicast Applications: Challenges and Solutions.
• RFC3172: Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa").
• RFC3173: IP Payload Compression Protocol (IPComp).
• RFC3174: US Secure Hash Algorithm 1 (SHA1).
• RFC3175: Aggregation of RSVP for IPv4 and IPv6 Reservations.
• RFC3176: InMon Corporation's sFlow: A Method for Monitoring Traffic in Switched and Routed Networks.
• RFC3177: IAB/IESG Recommendations on IPv6 Address Allocations to Sites. IAB,
• RFC3180: GLOP Addressing in 233/8.

October 2001

• RFC3102: Realm Specific IP: Framework.
• RFC3103: Realm Specific IP: Protocol Specification.
• RFC3104: RSIP Support for End-to-end IPsec.
• RFC3105: Finding an RSIP Server with
• RFC3146: Transmission of IPv6 Packets over IEEE 1394 Networks.
• RFC3178: IPv6 Multihoming Support at Site Exit Routers.
• RFC3179: Script MIB Extensibility Protocol Version 1.1.
• RFC3181: Signaled Preemption Priority Policy Element.
• RFC3182: Identity Representation for
• RFC3183: Domain Security Services using S/MIME.
• RFC3184: IETF Guidelines for Conduct.
• RFC3185: Reuse of CMS Content Encryption Keys.
• RFC3187: Using International Standard Book Numbers as Uniform Resource Names.
• RFC3188: Using National Bibliography Numbers as Uniform Resource Names.
• RFC3191: Minimal GSTN address format in Internet Mail.
• RFC3192: Minimal FAX address format in Internet Mail.

November 2001

• RFC3000: Internet Official Protocol Standards.
• RFC3099: Request for Comments Summary RFC Numbers 3000-3099.
• RFC3117: On the Design of Application Protocols.
• RFC3193: Securing L2TP using IPsec.
• RFC3194: The H-Density Ratio for Address Assignment Efficiency An Update on the H ratio.
• RFC3195: Reliable Delivery for syslog.
• RFC3196: Internet Printing Protocol/1.1: Implementor's Guide.
• RFC3197: Applicability Statement for DNS MIB Extensions.
• RFC3198: Terminology for Policy-Based Management.