• RFC3074 - DHC Load Balancing Algorithm This document proposes a method of algorithmic load balancing. [STANDARDS TRACK]
• RFC3073 - Portable Font Resource (PFR) - application/font-tdpfr MIME Sub-type Registration This document describes the registration of the Multipurpose Internet Mail Extensions (MIME) sub-type application/font-tdpfr. The encoding is defined by the PFR Specification. This memo provides information for the Internet community.
• RFC3072 - Structured Data Exchange Format (SDXF) This specification describes an all-purpose interchange format for use as a file format or for net-working. This memo provides information for the Internet community.
• RFC3071 - Reflections on the DNS, RFC 1591, and Categories of Domains This document is being published primarily for historical context and comparative purposes, essentially to document some thoughts about how 1591 might have been interpreted and adjusted by the Internet Assigned Numbers Authority (IANA) and ICANN to better reflect today's world while retaining characteristics and policies that have proven to be effective in supporting Internet growth and stability. This memo provides information for the Internet community.
• RFC3070 - Layer Two Tunneling Protocol (L2TP) over Frame Relay This document describes how L2TP is implemented over Frame Relay Permanent Virtual Circuits (PVCs) and Switched Virtual Circuits (SVCs). [STANDARDS TRACK]
• RFC3069 - VLAN Aggregation for Efficient IP Address Allocation This document introduces the concept of Virtual Local Area Network (VLAN) aggregation as it relates to IPv4 address allocation. This memo provides information for the Internet community.
• RFC3068 - An Anycast Prefix for 6to4 Relay Routers This memo introduces a "6to4 anycast address" in order to simplify the configuration of 6to4 routers. It also defines how this address will be used by 6to4 relay routers, how the corresponding "6to4 anycast prefix" will be advertised in the IGP and in the EGP. The memo documents the reservation by IANA (Internet Assigned Numbers Authority) of the "6to4 relay anycast prefix." [STANDARDS TRACK]
• RFC3067 - TERENA'S Incident Object Description and Exchange Format Requirements The purpose of the Incident Object Description and Exchange Format is to define a common data format for the description, archiving and exchange of information about incidents between CSIRTs (Computer Security Incident Response Teams) (including alert, incident in investigation, archiving, statistics, reporting, etc.). This document describes the high-level requirements for such a description and exchange format, including the reasons for those requirements. This memo provides information for the Internet community.
• RFC3066 - Tags for the Identification of Languages This document describes a language tag for use in cases where it is desired to indicate the language used in an information object, how to register values for use in this language tag, and a construct for matching such language tags. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
• RFC3065 - Autonomous System Confederations for BGP This document describes an extension to BGP which may be used to create a confederation of autonomous systems that is represented as a single autonomous system to BGP peers external to the confederation, thereby removing the "full mesh" requirement. The intention of this extension is to aid in policy administration and reduce the management complexity of maintaining a large autonomous system. [STANDARDS TRACK]
• RFC3064 - MGCP CAS Packages This document contains a collection of media gateway Channel Associated Signaling (CAS) packages for R1 CAS, North American CAS, CAS PBX interconnect as well as basic FXO support. This memo provides information for the Internet community.
• RFC3063 - MPLS Loop Prevention Mechanism This paper presents a simple mechanism, based on "threads", which can be used to prevent Multiprotocol Label Switching (MPLS) from setting up label switched path (LSPs) which have loops. This memo defines an Experimental Protocol for the Internet community.
• RFC3062 - LDAP Password Modify Extended Operation This document describes an LDAP extended operation to allow modification of user passwords which is not dependent upon the form of the authentication identity nor the password storage mechanism used. [STANDARDS TRACK]
• RFC3061 - A URN Namespace of Object Identifiers This document describes a Uniform Resource Name (URN) namespace that contains Object Identifiers (OIDs). This memo provides information for the Internet community.
• RFC3060 - Policy Core Information Model -- Version 1 Specification This document presents the object-oriented information model for representing policy information developed jointly in the IETF Policy Framework WG and as extensions to the Common Information Model (CIM) activity in the Distributed Management Task Force (DMTF). [STANDARDS TRACK]
• RFC3059 - Attribute List Extension for the Service Location Protocol This document specifies a SLPv2 extension which allows a User Agent (UA) to request a service's attributes be included as an extension to Service Reply messages. This will eliminate the need for multiple round trip messages for a UA to acquire all service information. [STANDARDS TRACK]
• RFC3058 - Use of the IDEA Encryption Algorithm in CMS This memo specifies how to incorporate International Data Encryption Algorithm (IDEA) into CMS or S/MIME as an additional strong algorithm for symmetric encryption. This memo provides information for the Internet community.
• RFC3057 - ISDN Q.921-User Adaptation Layer This document defines a protocol for backhauling of ISDN Q.921 User messages over IP using the Stream Control Transmission Protocol (SCTP). This protocol would be used between a Signaling Gateway (SG) and Media Gateway Controller (MGC). [STANDARDS TRACK]
• RFC3056 - Connection of IPv6 Domains via IPv4 Clouds This memo specifies an optional interim mechanism for IPv6 sites to communicate with each other over the IPv4 network without explicit tunnel setup, and for them to communicate with native IPv6 domains via relay routers. [STANDARDS TRACK]
• RFC3055 - Management Information Base for the PINT Services Architecture This memo describes a proposed Management Information Base (MIB) for the PSTN/Internet Interworking (PINT) Services Architecture. [STANDARDS TRACK]
• RFC3054 - Megaco IP Phone Media Gateway Application Profile This document specifies a particular application of the Megaco/H.248 Protocol for control of Internet telephones and similar appliances: the Megaco IP Phone Media Gateway. This memo provides information for the Internet community.
• RFC3053 - IPv6 Tunnel Broker The motivation for the development of the tunnel broker model is to help early IPv6 adopters to hook up to an existing IPv6 network (e.g., the 6bone) and to get stable, permanent IPv6 addresses and DNS names. The concept of the tunnel broker was first presented at Orlando's IETF in December 1998. Two implementations were demonstrated during the Grenoble IPng & NGtrans interim meeting in February 1999. This memo provides information for the Internet community.
• RFC3052 - Service Management Architectures Issues and Review The purpose of this document is to explore the problems of defining a Service management framework and to examine some of the issues that still need to be resolved. This memo provides information for the Internet community.
• RFC3051 - IP Payload Compression Using ITU-T V.44 Packet Method This document describes a compression method based on the data compression algorithm described in International Telecommunication Union (ITU-T) Recommendation V.44. This document defines the application of V.44 Packet Method to the Internet Protocol (IP) Payload Compression Protocol (RFC 2393). This memo provides information for the Internet community.
• RFC3050 - Common Gateway Interface for SIP This document defines a SIP CGI interface for providing SIP services on a SIP server. This memo provides information for the Internet community.

Książki warte uwagi