📄 rfc2699.txt
字号:
use with network management protocols in the Internet community.[STANDARDS-TRACK]2664 Plzak Aug 1999 FYI on Questions and Answers Answers to Commonly Asked "New Internet User" QuestionsThis memo provides an overview to the new Internet User. The intendedaudience is the common Internet user of today, thus it attempts toprovide a more consumer oriented approach to the Internet rather thangoing into any depth about a topic. This memo provides information forthe Internet community.2663 Srisuresh Aug 1999 IP Network Address Translator (NAT) Terminology and ConsiderationsThis document attempts to describe the operation of NAT devices and theassociated considerations in general, and to define the terminology usedto identify various flavors of NAT. This memo provides information forthe Internet community.2662 Bathrick Aug 1999 Definitions of Managed Objects for the ADSL LinesThis document defines a standard SNMP MIB for ADSL lines based on theADSL Forum standard data model. [STANDARDS-TRACK]Ginoza Informational [Page 8]RFC 2699 Summary of 2600-2699 May 20002661 Townsley Aug 1999 Layer Two Tunneling Protocol "L2TP"This document describes the Layer Two Tunneling Protocol (L2TP).[STANDARDS-TRACK]2660 Rescorla Aug 1999 The Secure HyperText Transfer ProtocolThis memo describes a syntax for securing messages sent using theHypertext Transfer Protocol (HTTP), which forms the basis for the WorldWide Web. This memo defines an Experimental Protocol for the Internetcommunity.2659 Rescorla Aug 1999 Security Extensions For HTMLThis memo describes a syntax for embedding S-HTTP negotiation parametersin HTML documents. This memo defines an Experimental Protocol for theInternet community.2658 McKay Aug 1999 RTP Payload Format for PureVoice(tm) AudioThis document describes the RTP payload format for PureVoice(tm) Audio.[STANDARDS-TRACK]2657 Hedberg Aug 1999 LDAPv2 Client vs. the Index MeshLDAPv2 clients as implemented according to RFC 1777 have no notion onreferral. The integration between such a client and an Index Mesh, asdefined by the Common Indexing Protocol, heavily depends on referralsand therefore needs to be handled in a special way. This documentdefines one possible way of doing this. This memo defines anExperimental Protocol for the Internet community.Ginoza Informational [Page 9]RFC 2699 Summary of 2600-2699 May 20002656 Hardie Aug 1999 Registration Procedures for SOIF Template TypeThe registration procedure described in this document is specific toSOIF template types. This memo defines an Experimental Protocol for theInternet community.2655 Hardie Aug 1999 CIP Index Object Format for SOIF ObjectsThis document describes SOIF, the Summary Object Interchange Format, asan index object type in the context of the CIP framework. This memodefines an Experimental Protocol for the Internet community.2654 Hedberg Aug 1999 A Tagged Index Object for use in the Common Indexing ProtocolThis document defines a mechanism by which information servers canexchange indices of information from their databases by making use ofthe Common Indexing Protocol (CIP). This document defines the structureof the index information being exchanged, as well as the appropriatemeanings for the headers that are defined in the Common IndexingProtocol. This memo defines an Experimental Protocol for the Internetcommunity.2653 Allen Aug 1999 CIP Transport ProtocolsThis document specifies three protocols for transporting CIP requests,responses and index objects, utilizing TCP, mail, and HTTP.[STANDARDS-TRACK]2652 Allen Aug 1999 MIME Object Definitions for the Common Indexing Protocol (CIP)This document describes the definitions of those objects as well as themethods and requirements needed to define a new index type.[STANDARDS-TRACK]Ginoza Informational [Page 10]RFC 2699 Summary of 2600-2699 May 20002651 Allen Aug 1999 The Architecture of the Common Indexing Protocol (CIP)This document describes the CIP framework, including its architectureand the protocol specifics of exchanging indices. [STANDARDS-TRACK]2650 Meyer Aug 1999 Using RPSL in PracticeThis document is a tutorial on using the Routing Policy SpecificationLanguage (RPSL) to describe routing policies in the Internet RoutingRegistry (IRR). This memo provides information for the Internetcommunity.2649 Greenblatt Aug 1999 An LDAP Control and Schema for Holding Operation SignaturesThis document describes an LDAP message control which allows for theretrieval of digitally signed information. This document defines an LDAPv3 based mechanism for signing directory operations in order to create asecure journal of changes that have been made to each directory entry.This memo defines an Experimental Protocol for the Internet community.2648 Moats Aug 1999 A URN Namespace for IETF DocumentsThis document proposes the "ietf" namespace, which consists of the RFCfamily of documents (RFCs, STDs, FYIs, and BCPs) developed by the IETFand published by the RFC Editor and the minutes of working groups (WG)and birds of a feather (BOF) meetings that occur during IETFconferences. [STANDARDS-TRACK]2647 Newman Aug 1999 Benchmarking Terminology for Firewall PerformanceThis document defines terms used in measuring the performance offirewalls. It extends the terminology already used for benchmarkingrouters and switches with definitions specific to firewalls.[STANDARDS-TRACK]Ginoza Informational [Page 11]RFC 2699 Summary of 2600-2699 May 20002646 Gellens Aug 1999 The Text/Plain Format ParameterThis memo proposes a new parameter to be used with Text/Plain, and, inthe presence of this parameter, the use of trailing whitespace toindicate flowed lines. This results in an encoding which appears asnormal Text/Plain in older implementations, since it is in fact normalText/Plain. [STANDARDS-TRACK]2645 Gellens Aug 1999 ON-DEMAND MAIL RELAY (ODMR) SMTP with Dynamic IP AddressesThis memo proposes a new service, On-Demand Mail Relay (ODMR), which isa profile of SMTP, providing for a secure, extensible, easy to implementapproach to the problem. [STANDARDS-TRACK]2644 Bradner Aug 1999 Benchmarking Methodology for Network Interconnect DevicesThis document discusses and defines a number of tests that may be usedto describe the performance characteristics of a network interconnectingdevice. In addition to defining the tests this document also describesspecific formats for reporting the results of the tests. This memoprovides information for the Internet community.2643 Ruffen Aug 1999 Cabletron's SecureFast VLAN Operational ModelCabletron's SecureFast VLAN (SFVLAN) product implements a distributedconnection-oriented switching protocol that provides fast forwarding ofdata packets at the MAC layer. The product uses the concept of virtualLANs (VLANs) to determine the validity of call connection requests andto scope the broadcast of certain flooded messages. This memo providesinformation for the Internet community.2642 Kane Aug 1999 Cabletron's VLS Protocol SpecificationVLSP provides support for equal-cost multipath routing, and recalculatesroutes quickly in the face of topological changes, utilizing a minimumof routing protocol traffic. This memo provides information for theInternet community.Ginoza Informational [Page 12]RFC 2699 Summary of 2600-2699 May 20002641 Hamilton Aug 1999 Cabletron's VlanHello Protocol SpecificationThe VlanHello protocol is part of the InterSwitch Message Protocol(ISMP) which provides interswitch communication between switches runningCabletron's SecureFast VLAN (SFVLAN) product. Switches use theVlanHello protocol to discover their neighboring switches and establishthe topology of the switch fabric. This memo provides information forthe Internet community.2640 Curtin Jul 1999 Internationalization of the File transfer ProtocolThis document addresses the internationalization (I18n) of FTP, whichincludes supporting the multiple character sets and languages foundthroughout the Internet community. This is achieved by extending theFTP specification and giving recommendations for properinternationalization support. [STANDARDS-TRACK]2639 Hastings Jul 1999 Internet Printing Protocol/1.0: Implementer's GuideThis document contains information that supplements the IPP Model andSemantics and the IPP Transport and Encoding documents. It is intendedto help implementers understand IPP/1.0 and some of the considerationsthat may assist them in the design of their client and/or IPP objectimplementations. This memo provides information for the Internetcommunity.2638 Nichols Jul 1999 A Two-bit Differentiated Services Architecture for the InternetThis document presents a differentiated services architecture for theinternet. This memo provides information for the Internet community.Ginoza Informational [Page 13]RFC 2699 Summary of 2600-2699 May 20002637 Hamzeh Jul 1999 Point-to-Point Tunneling Protocol (PPTP)This document specifies a protocol which allows the Point to PointProtocol (PPP) to be tunneled through an IP network. This memo providesinformation for the Internet community.2636 Gellens Jul 1999 Wireless Device Configuration (OTASP/OTAPA) via ACAPThis paper describes a viable and attractive means to provideOTASP/OTAPA via IS-707, using the ACAP protocol. This memo providesinformation for the Internet community.2635 Hambridge Jun 1999 DON'T SPEW A Set of Guidelines for Mass Unsolicited Mailings and PostingsThis document explains why mass unsolicited electronic mail messages areharmful in the Internetworking community. This memo providesinformation for the Internet community.2634 Hoffman Jun 1999 Enhanced Security Services for S/MIMEThis document describes four optional security service extensions forS/MIME. [STANDARDS-TRACK]2633 Ramsdell Jun 1999 S/MIME Version 3 Message SpecificationThis document describes a protocol for adding cryptographic signatureand encryption services to MIME data. [STANDARDS-TRACK]Ginoza Informational [Page 14]RFC 2699 Summary of 2600-2699 May 20002632 Ramsdell Jun 1999 S/MIME Version 3 Certificate HandlingS/MIME (Secure/Multipurpose Internet Mail Extensions), provides a methodto send and receive secure MIME messages. Before using a public key toprovide security services, the S/MIME agent MUST certify that the publickey is valid. S/MIME agents MUST use PKIX certificates to validatepublic keys as described in the Internet X.509 Public Key Infrastructure(PKIX) Certificate and CRL Profile. [STANDARDS-TRACK]2631 Rescorla Jun 1999 Diffie-Hellman Key Agreement MethodThis document standardizes one particular Diffie-Hellman variant, basedon the ANSI X9.42 draft, developed by the ANSI X9F1 working group.[STANDARDS-TRACK]2630 Housley Jun 1999 Cryptographic Message SyntaxThis document describes the Cryptographic Message Syntax. This syntaxis used to digitally sign, digest, authenticate, or encrypt arbitrarymessages. [STANDARDS-TRACK]2629 Rose Jun 1999 Writing I-Ds and RFCs using XMLThis memo presents a technique for using XML (Extensible MarkupLanguage) as a source format for documents in the Internet-Drafts (I-Ds)and Request for Comments (RFC) series. This memo provides informationfor the Internet community.
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -