[btns] RFC 5387 on Problem and Applicability Statement for Better-Than-Nothing Security (BTNS)

rfc-editor@rfc-editor.org Mon, 17 November 2008 16:01 UTC

Return-Path: <btns-bounces@ietf.org>
X-Original-To: btns-archive-1@ietf.org
Delivered-To: ietfarch-btns-archive-1@core3.amsl.com
Received: from [] (localhost []) by core3.amsl.com (Postfix) with ESMTP id 122C428C0FE; Mon, 17 Nov 2008 08:01:12 -0800 (PST)
X-Original-To: btns@core3.amsl.com
Delivered-To: btns@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 975FD28C1CB; Fri, 14 Nov 2008 13:42:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.499
X-Spam-Status: No, score=-17.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id B64bSdaQnrB8; Fri, 14 Nov 2008 13:42:32 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu []) by core3.amsl.com (Postfix) with ESMTP id B428228C1C9; Fri, 14 Nov 2008 13:42:32 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id 42037175006; Fri, 14 Nov 2008 13:42:33 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20081114214233.42037175006@bosco.isi.edu>
Date: Fri, 14 Nov 2008 13:42:33 -0800 (PST)
X-Mailman-Approved-At: Mon, 17 Nov 2008 08:01:10 -0800
Cc: btns@ietf.org, rfc-editor@rfc-editor.org
Subject: [btns] RFC 5387 on Problem and Applicability Statement for Better-Than-Nothing Security (BTNS)
X-BeenThere: btns@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Better-Than-Nothing-Security Working Group discussion list <btns.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/btns>, <mailto:btns-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/btns>
List-Post: <mailto:btns@ietf.org>
List-Help: <mailto:btns-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/btns>, <mailto:btns-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: btns-bounces@ietf.org
Errors-To: btns-bounces@ietf.org

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

        RFC 5387

        Title:      Problem and Applicability Statement for 
                    Better-Than-Nothing Security (BTNS) 
        Author:     J. Touch, D. Black, Y. Wang
        Status:     Informational
        Date:       November 2008
        Mailbox:    touch@isi.edu, 
        Pages:      28
        Characters: 71707
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-btns-prob-and-applic-07.txt

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

The Internet network security protocol suite, IPsec, requires
authentication, usually of network-layer entities, to enable access
control and provide security services.  This authentication can be
based on mechanisms such as pre-shared symmetric keys, certificates
with associated asymmetric keys, or the use of Kerberos (via
Kerberized Internet Negotiation of Keys (KINK)).  The need to deploy
authentication information and its associated identities can be a
significant obstacle to the use of IPsec.

This document explains the rationale for extending the Internet
network security protocol suite to enable use of IPsec security
services without authentication.  These extensions are intended to
protect communication, providing "better-than-nothing security"
(BTNS).  The extensions may be used on their own (this use is called
Stand-Alone BTNS, or SAB) or may be used to provide network-layer
security that can be authenticated by higher layers in the protocol
stack (this use is called Channel-Bound BTNS, or CBB).  The document
also explains situations for which use of SAB and/or CBB extensions
are applicable.  This memo provides information for the Internet community.

This document is a product of the Better-Than-Nothing Security Working Group of the IETF.

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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
USC/Information Sciences Institute

btns mailing list