📄 rfc1360.txt
字号:
RFC 1360 IAB Standards September 1992 is needed and if so by whom. RFC Editor decides to publish or not. Of course, in all cases the RFC Editor can request or make minor changes for style, format, and presentation purposes. The IESG has designated the IESG Secretary as its agent for forwarding documents with IESG approval and for registering concerns in response to notifications (5) to the RFC Editor. Documents from Area Directors or Working Group Chairs may be considered in the same way as documents from "other".5.2. The Standards Track Diagram There is a part of the STATUS and STATE categorization that is called the standards track. Actually, only the changes of state are significant to the progression along the standards track, though the status assignments may be changed as well. The states illustrated by single line boxes are temporary states, those illustrated by double line boxes are long term states. A protocol will normally be expected to remain in a temporary state for several months (minimum six months for proposed standard, minimum four months for draft standard). A protocol may be in a long term state for many years. A protocol may enter the standards track only on the recommendation of the IESG and by action of the IAB; and may move from one state to another along the track only on the recommendation of the IESG and by action of the IAB. That is, it takes both the IESG and the IAB to either start a protocol on the track or to move it along. Generally, as the protocol enters the standards track a decision is made as to the eventual STATUS, requirement level or applicability (elective, recommended, or required) the protocol will have, although a somewhat less stringent current status may be assigned, and it then is placed in the the proposed standard STATE with that status. So the initial placement of a protocol is into state 1. At any time the STATUS decision may be revisited.Internet Architecture Board [Page 12]RFC 1360 IAB Standards September 1992 | +<----------------------------------------------+ | ^ V 0 | 4 +-----------+ +===========+ | enter |-->----------------+-------------->|experiment | +-----------+ | +=====+=====+ | | V 1 | +-----------+ V | proposed |-------------->+ +--->+-----+-----+ | | | | | V 2 | +<---+-----+-----+ V | draft std |-------------->+ +--->+-----+-----+ | | | | | V 3 | +<---+=====+=====+ V | standard |-------------->+ +=====+=====+ | | V 5 +=====+=====+ | historic | +===========+ The transition from proposed standard (1) to draft standard (2) can only be by action of the IAB on the recommendation of the IESG and only after the protocol has been proposed standard (1) for at least six months. The transition from draft standard (2) to standard (3) can only be by action of the IAB on the recommendation of the IESG and only after the protocol has been draft standard (2) for at least four months. Occasionally, the decision may be that the protocol is not ready for standardization and will be assigned to the experimental state (4). This is off the standards track, and the protocol may be resubmitted to enter the standards track after further work. There are other paths into the experimental and historic states that do not involve IAB action. Sometimes one protocol is replaced by another and thus becomes historic, or it may happen that a protocol on the standards track is in a sense overtaken by another protocol (or other events) and becomes historic (state 5).Internet Architecture Board [Page 13]RFC 1360 IAB Standards September 19926. The Protocols Subsection 6.1 lists recent RFCs and other changes. Subsections 6.2 - 6.9 list the standards in groups by protocol state.6.1. Recent Changes6.1.1. New RFCs: 1361 - Simple Network Time Protocol (SNTP) This is an information document and does not specify any level of standard. 1360 - This memo. 1359 - Connecting to the Internet What Connecting Institutions Should Anticipate This is an information document and does not specify any level of standard. 1358 - Charter of the Internet Architecture Board (IAB) This is an information document and does not specify any level of standard. 1357 - A Format for E-mailing Bibliographic Records This is an information document and does not specify any level of standard. 1356 - Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode A Proposed Standard protocol. 1355 - Privacy and Accuracy Issues in Network Information Center Databases This is an information document and does not specify any level of standard. 1354 - IP Forwarding Table MIB A Proposed Standard protocol.Internet Architecture Board [Page 14]RFC 1360 IAB Standards September 1992 1353 - Definitions of Managed Objects for Administration of SNMP Parties A Proposed Standard protocol. 1352 - SNMP Security Protocols A Proposed Standard protocol. 1351 - SNMP Administrative Model A Proposed Standard protocol. 1350 - The TFTP Protocol (Revision 2) A Standard protocol. 1349 - Type of Service in the Internet Protocol Suite A Proposed Standard protocol. 1348 - DNS NSAP RRs An Experimental protocol. 1347 - TCP and UDP with Bigger Addresses (TUBA), A Simple Proposal for Internet Addressing and Routing This is an information document and does not specify any level of standard. 1346 - Resource Allocation, Control, and Accounting for the Use of Network Resources This is an information document and does not specify any level of standard. 1345 - Character Mnemonics & Character Sets This is an information document and does not specify any level of standard. 1344 - Implications of MIME for Internet Mail Gateways This is an information document and does not specify any level of standard.Internet Architecture Board [Page 15]RFC 1360 IAB Standards September 1992 1343 - A User Agent Configuration Mechanism For Multimedia Mail Format Information This is an information document and does not specify any level of standard. 1342 - Representation of Non-ASCII Text in Internet Message Headers A Proposed Standard protocol. 1341 - MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies A Proposed Standard protocol. 1340 - Assigned Numbers This is an information document and does not specify any level of standard. 1339 - Remote Mail Checking Protocol An Experimental protocol. 1338 - Supernetting: an Address Assignment and Aggregation Strategy This is an information document and does not specify any level of standard. 1337 - TIME-WAIT Assassination Hazards in TCP This is an information document and does not specify any level of standard. 1336 - Who's Who in the Internet - Biographies of IAB, IESG and IRSG Members This is an information document and does not specify any level of standard. 1335 - A Two-Tier Address Structure for the Internet: A Solution to the Problem of Address Space Exhaustion This is an information document and does not specify any level of standard.Internet Architecture Board [Page 16]RFC 1360 IAB Standards September 1992 1334 - Not yet issued. 1333 - PPP Link Quality Monitoring A Proposed Standard protocol. 1332 - The PPP Internet Protocol Control Protocol (IPCP) A Proposed Standard protocol. 1331 - The Point-to-Point Protocol (PPP) for the Transmission of Multi-protocol Datagrams over Point-to-Point Links A Proposed Standard protocol. 1330 - Recommendations for the Phase I Deployment of OSI Directory Services (X.500) and OSI Message Handling Services (X.400) This is an information document and does not specify any level of standard. 1329 - Thoughts on Address Resolution for Dual MAC FDDI Networks This is an information document and does not specify any level of standard.
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -