[rfc-i] FYI 36, RFC 4949 on Internet Security Glossary, Version 2

Bob Braden braden at ISI.EDU
Tue Aug 21 09:26:32 PDT 2007

Getting this one published has been quite a large, lengthy,
and meticulous enterprise, by both its author and the RFC Editor.
It is equivalent in length to 12 average RFCs!  We are relieved
to have it finally published.

RFC Editor/bb

----- Begin Included Message -----

>From rfc-ed at ISI.EDU  Mon Aug 20 17:12:15 2007
X-Spam-Status: No, score=-18.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,
	NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=ham version=3.1.0
To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org
Subject: FYI 36, RFC 4949 on Internet Security Glossary, Version 2
From: rfc-editor at rfc-editor.org
Cc: rfc-editor at rfc-editor.org
Date: Mon, 20 Aug 2007 17:09:15 -0700 (PDT)
X-ISI-4-43-8-MailScanner: Found to be clean, Found to be clean

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

        RFC 4949

        Title:      Internet Security Glossary, Version 2 
        Author:     R. Shirey
        Status:     Informational
        Date:       August 2007
        Mailbox:    rwshirey4949 at verizon.net
        Pages:      365
        Characters: 867626

        I-D Tag:    draft-shirey-secgloss-v2-08.txt

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

This Glossary provides definitions, abbreviations, and explanations
of terminology for information system security. The 334 pages of
entries offer recommendations to improve the comprehensibility of
written material that is generated in the Internet Standards Process
(RFC 2026). The recommendations follow the principles that such
writing should (a) use the same term or definition whenever the same
concept is mentioned; (b) use terms in their plainest, dictionary
sense; (c) use terms that are already well-established in open
publications; and (d) avoid terms that either favor a particular
vendor or favor a particular technology or mechanism over other,
competing techniques that already exist or could be developed.  This 
memo provides information for the Internet community.

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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

The RFC Editor Team
USC/Information Sciences Institute


----- End Included Message -----

More information about the rfc-interest mailing list