Subject: RFC 4846 on Independent Submissions to the RFC Editor

From: [email-masked]
Date: Wed, 18 Jul 2007 17:12:02 -0700 (PDT)

A new Request for Comments is now available in online RFC libraries.

        RFC 4846

        Title:      Independent Submissions to the RFC 

                    Editor 

        Author:     J. Klensin, Ed.,

                    D. Thaler, Ed.

        Status:     Informational

        Date:       July 2007

        Mailbox:    [email-masked], 

                    [email-masked]

        Pages:      16

        Characters: 36562

        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-iab-rfc-independent-00.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4846.txt

There is a long-standing tradition in the Internet community,

predating the Internet Engineering Task Force (IETF) by many years,

of use of the RFC Series to publish materials that are not rooted in

the IETF standards process and its review and approval mechanisms.

These documents, known as "Independent Submissions", serve a number

of important functions for the Internet community, both inside and

outside of the community of active IETF participants.  This document

discusses the Independent Submission model and some reasons why it is

important.  It then describes editorial and processing norms that can

be used for Independent Submissions as the community goes forward

into new relationships between the IETF community and its primary

technical publisher.  This memo provides information for the Internet 

community.

This document is a product of the Internet Architecture Board.

INFORMATIONAL: This memo provides information for the Internet community. 

It does not specify an Internet standard of any kind. Distribution

of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.

Requests to be added to or deleted from the IETF distribution list

should be sent to [email-masked].  Requests to be

added to or deleted from the RFC-DIST distribution list should

be sent to [email-masked].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending

an EMAIL message to [email-masked] with the message body 

help: ways_to_get_rfcs. For example:

        To: [email-masked]

        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the

author of the RFC in question, or to [email-masked].  Unless

specifically noted otherwise on the RFC itself, all RFCs are for

unlimited distribution.

Submissions for Requests for Comments should be sent to

[email-masked].  Please consult RFC 2223, Instructions to RFC

Authors, for further information.

The RFC Editor Team

USC/Information Sciences Institute

...

_______________________________________________
IETF-Announce mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ietf-announce