idnits 2.17.1 draft-iab-considerations-03.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3426 5 Title: General Architectural and Policy Considerations 6 Author(s): S. Floyd 7 Status: Informational 8 Date: November 2002 9 Mailbox: iab@iab.org 10 Pages: 23 11 Characters: 54868 12 Updates/Obsoletes/SeeAlso: None 14 I-D Tag: draft-iab-considerations-03.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3426.txt 18 This document suggests general architectural and policy questions 19 that the IETF community has to address when working on new standards 20 and protocols. We note that this document contains questions to be 21 addressed, as opposed to guidelines or architectural principles to be 22 followed. 24 This memo provides information for the Internet community. It does 25 not specify an Internet standard of any kind. Distribution of this 26 memo is unlimited. 28 This announcement is sent to the IETF list and the RFC-DIST list. 29 Requests to be added to or deleted from the IETF distribution list 30 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 31 added to or deleted from the RFC-DIST distribution list should 32 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 34 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 35 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 36 help: ways_to_get_rfcs. For example: 38 To: rfc-info@RFC-EDITOR.ORG 39 Subject: getting rfcs 41 help: ways_to_get_rfcs 43 Requests for special distribution should be addressed to either the 44 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 45 specifically noted otherwise on the RFC itself, all RFCs are for 46 unlimited distribution.echo 47 Submissions for Requests for Comments should be sent to 48 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 49 Authors, for further information.