📄 rfc2399.txt
字号:
This document defines the Session Description Protocol, SDP. SDP isintended for describing multimedia sessions for the purposes of sessionannouncement, session invitation, and other forms of multimedia sessioninitiation. [STANDARDS-TRACK]2326 Schulzrinne Apr 1998 Real Time Streaming Protocol (RTSP)The Real Time Streaming Protocol, or RTSP, is an application-levelprotocol for control over the delivery of data with real-timeproperties. RTSP provides an extensible framework to enable controlled,on-demand delivery of real-time data, such as audio and video.[STANDARDS-TRACK]2325 Slavitch 1 Apr 1998 Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2This memo defines an extension to the Management Information Base (MIB)for use with network management protocols in the Internet community. Inparticular, it defines objects for the management of coffee-brewing andmaintenance devices. This memo provides information for the Internetcommunity. It does not specify an Internet standard of any kind.Ramos Informational [Page 16]RFC 2399 Summary of 2300-2399 January 19992324 Masinter 1 Apr 1998 Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)This document describes HTCPCP, a protocol for controlling, monitoring,and diagnosing coffee pots. This memo provides information for theInternet community. It does not specify an Internet standard of anykind.2323 Ramos 1 Apr 1998 IETF Identification and Security GuidelinesThis RFC is meant to represent a guideline by which the IETF conferencesmay run more effeciently with regards to identification and securityprotocols, with specific attention paid to a particular sub-group withinthe IETF: "facial hairius extremis". This memo provides information forthe Internet community. It does not specify an Internet standard of anykind.2322 van den Hout 1 Apr 1998 Management of IP numbers by peg-dhcpThis RFC describes a protocol to dynamically hand out ip-numbers onfield networks and small events that don't necessarily have a clearorganisational body. This memo provides information for the Internetcommunity. It does not specify an Internet standard of any kind.2321 Bressen 1 Apr 1998 RITA -- The Reliable Internetwork Troubleshooting AgentA Description of the usage of Nondeterministic Troubleshooting andDiagnostic Methodologies as applied to today's complex nondeterministicnetworks and environments. This memo provides information for theInternet community. It does not specify an Internet standard of anykind.2320 Greene Apr 1998 Definitions of Managed Objects for Classical IP and ARP Over ATM Using SMIv2The purpose of this memo is to define the Management Information Base(MIB) for supporting Classical IP and ARP over ATM as specified inClassical IP and ARP over ATM. [STANDARDS-TRACK]Ramos Informational [Page 17]RFC 2399 Summary of 2300-2399 January 19992319 KOI8-U WG Apr 1998 Ukrainian Character Set KOI8-UThis document provides information about character encoding KOI8-U (KOI8Ukrainian) wich is a de-facto standard in Ukrainian Internet community.This memo provides information for the Internet community. It does notspecify an Internet standard of any kind.2318 Lie Mar 1998 The text/css Media TypeThis memo provides information about the text/css Media Type. This memoprovides information for the Internet community. It does not specify anInternet standard of any kind.2317 Eidnes Mar 1998 Classless IN-ADDR.ARPA delegationThis document describes a way to do IN-ADDR.ARPA delegation on non-octetboundaries for address spaces covering fewer than 256 addresses. Thisdocument specifies an Internet Best Current Practices for the InternetCommunity, and requests discussion and suggestions for improvements.2316 Bellovin Apr 1998 Report of the IAB Security Architecture WorkshopOn 3-5 March 1997, the IAB held a security architecture workshop at BellLabs in Murray Hill, NJ. We identified the core security components ofthe architecture, and specified several documents that need to bewritten. Most importantly, we agreed that security was not optional,and that it needed to be designed in from the beginning. This memoprovides information for the Internet community. It does not specify anInternet standard of any kind.2315 Kaliski Mar 1998 PKCS #7: Cryptographic Message Syntax Version 1.5This document describes a general syntax for data that may havecryptography applied to it, such as digital signatures and digitalenvelopes. This memo provides information for the Internet community.It does not specify an Internet standard of any kind.Ramos Informational [Page 18]RFC 2399 Summary of 2300-2399 January 19992314 Kaliski Mar 1998 PKCS #10: Certification Request Syntax Version 1.5This document describes a syntax for certification requests. This memoprovides information for the Internet community. It does not specify anInternet standard of any kind.2313 Kaliski Mar 1998 PKCS #1: RSA Encryption Version 1.5This document describes a method for encrypting data using the RSApublic-key cryptosystem. This memo provides information for theInternet community. It does not specify an Internet standard of anykind.2312 Dusse Mar 1998 S/MIME Version 2 Certificate HandlingThis memo describes the mechanisms S/MIME uses to create and validatekeys using certificates. This memo provides information for theInternet community. It does not specify an Internet standard of anykind.2311 Dusse Mar 1998 S/MIME Version 2 Message SpecificationThis document describes a protocol for adding cryptographic signatureand encryption services to MIME data. This memo provides informationfor the Internet community. It does not specify an Internet standard ofany kind.2310 Holtman Apr 1998 The Safe Response Header FieldThis document defines a HTTP response header field called Safe, whichcan be used to indicate that repeating a HTTP request is safe. Thismemo defines an Experimental Protocol for the Internet community. Itdoes not specify an Internet standard of any kind. Discussion andsuggestions for improvement are requested.Ramos Informational [Page 19]RFC 2399 Summary of 2300-2399 January 19992309 Braden Apr 1998 Recommendations on Queue Management and Congestion Avoidance in the InternetThis memo presents two recommendations to the Internet communityconcerning measures to improve and preserve Internet performance. Itpresents a strong recommendation for testing, standardization, andwidespread deployment of active queue management in routers, to improvethe performance of today's Internet. It also urges a concerted effortof research, measurement, and ultimate deployment of router mechanismsto protect the Internet from flows that are not sufficiently responsiveto congestion notification. This memo provides information for theInternet community. It does not specify an Internet standard of anykind.2308 Andrews Mar 1998 Negative Caching of DNS Queries (DNS NCACHE)RFC1034 provided a description of how to cache negative responses. Ithowever had a fundamental flaw in that it did not allow a name server tohand out those cached responses to other resolvers, thereby greatlyreducing the effect of the caching. This document addresses issuesraise in the light of experience and replaces RFC1034 Section 4.3.4.[STANDARDS-TRACK]2307 Howard Mar 1998 An Approach for Using LDAP as a Network Information ServiceThis document describes an experimental mechanism for mapping entitiesrelated to TCP/IP and the UNIX system into X.500 entries so that theymay be resolved with the Lightweight Directory Access Protocol[RFC2251]. This memo defines an Experimental Protocol for the Internetcommunity. It does not specify an Internet standard of any kind.Discussion and suggestions for improvement are requested.2306 Parsons Mar 1998 Tag Image File Format (TIFF) - F Profile for FacsimileThis document describes in detail the definition of TIFF-F that is usedto store facsimile images. This memo provides information for theInternet community. It does not specify an Internet standard of anykind.Ramos Informational [Page 20]RFC 2399 Summary of 2300-2399 January 19992305 Toyoda Mar 1998 A Simple Mode of Facsimile Using Internet MailThis specification provides for "simple mode" carriage of facsimile dataover the Internet. [STANDARDS-TRACK]2304 Allocchio Mar 1998 Minimal FAX address format in Internet MailThis memo describes the MINIMAL addressing method and standardextensions to encode FAX addresses in e-mail addresses. [STANDARDS-TRACK]2303 Allocchio Mar 1998 Minimal PSTN address format in Internet MailThis memo describes the MINIMAL addressing method to encode PSTNaddresses into e-mail addresses and the standard extension mechanism toallow definition of further standard elements. [STANDARDS-TRACK]2302 Parsons Mar 1998 Tag Image File Format (TIFF) - image/tiff MIME Sub-type RegistrationThis document describes the registration of the MIME sub-typeimage/tiff. [STANDARDS-TRACK]2301 McIntyre Mar 1998 File Format for Internet FaxThis document describes the TIFF (Tag Image File Format) representationof image data specified by the ITU-T Recommendations for black-and-whiteand color facsimile. [STANDARDS-TRACK]2300 IAB May 1998 INTERNET OFFICIAL PROTOCOL STANDARDSA discussion of the standardization process and the RFC document seriesis presented first, followed by an explanation of the terms. Sections6.2 - 6.10 contain the lists of protocols in each stage ofstandardization. Finally are pointers to references and contacts forfurther information. [STANDARDS-TRACK]Ramos Informational [Page 21]RFC 2399 Summary of 2300-2399 January 1999Security Considerations There are no security issues in this Informational RFC.Author's Address Alegre Ramos University of Southern California Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292 Phone: (310) 822-1511 EMail: ramos@isi.eduRamos Informational [Page 22]RFC 2399 Summary of 2300-2399 January 1999Full Copyright Statement Copyright (C) The Internet Society (1999). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.Ramos Informational [Page 23]
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -