Impending Publication: draft-iab-secmech-02.txt

Leslie Daigle <leslie@thinkingcat.com> Tue, 11 March 2003 16:55 UTC

Received: from ran.ietf.org (ran.ietf.org [10.27.6.60]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27309; Tue, 11 Mar 2003 11:55:25 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10) id 18sn1N-0000II-00 for ietf-announce-list@ran.ietf.org; Tue, 11 Mar 2003 11:54:33 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org) by ran.ietf.org with esmtp (Exim 4.10) id 18sn0z-0000Gq-00 for all-ietf@ran.ietf.org; Tue, 11 Mar 2003 11:54:09 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26747 for <all-ietf>; Tue, 11 Mar 2003 11:42:44 -0500 (EST)
Message-Id: <200303111642.LAA26747@ietf.org>
From: Leslie Daigle <leslie@thinkingcat.com>
To: IETF-Announce:;
Subject: Impending Publication: draft-iab-secmech-02.txt
Date: Tue, 11 Mar 2003 11:42:43 -0500
Sender: owner-ietf-announce@ietf.org
Precedence: bulk

The IAB is ready to ask the RFC-Editor to publish

                   Security Mechanisms for the Internet
                          draft-iab-secmech-02.txt

as an Informational RFC.  This document is part survey of issues,
and part advice for IETF protocol development.  The IAB would
like to ensure that the IETF community has had an opportunity to
read it and comment before its publication.

The IAB solicits comments by March 28, 2003.  Please send
comments to the IAB (iab@iab.org), care of the document editor
(Charlie_Kaufman@notesdev.ibm.com), or to ietf@ietf.org.
The document can be found at

http://www.ietf.org/internet-drafts/draft-iab-secmech-02.txt

    Abstract

    Security must be built into Internet Protocols for those protocols to
    offer their services securely. Many security problems can be traced
    to improper implementations. However, even a proper implementation
    will have security problems if the fundamental protocol is itself
    exploitable.  Exactly how security should be implemented in a
    protocol will vary, because of the structure of the protocol itself.
    However, there are many protocols for which standard Internet
    security mechanisms, already developed, may be applicable.  The
    precise one that is appropriate in any given situation can vary.  We
    review a number of different choices, explaining the properties of
    each.


Leslie Daigle
For the IAB