[tcpm] draft-ietf-tcpm-tcp-ao-crypto-02 posted

Gregory Lebovitz <gregory.ietf@gmail.com> Wed, 10 February 2010 10:53 UTC

Return-Path: <gregory.ietf@gmail.com>
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD54928C11C for <tcpm@core3.amsl.com>; Wed, 10 Feb 2010 02:53:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.409
X-Spam-Level:
X-Spam-Status: No, score=-102.409 tagged_above=-999 required=5 tests=[AWL=0.189, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z9pkov-qD7GN for <tcpm@core3.amsl.com>; Wed, 10 Feb 2010 02:53:19 -0800 (PST)
Received: from mail-bw0-f219.google.com (mail-bw0-f219.google.com [209.85.218.219]) by core3.amsl.com (Postfix) with ESMTP id 9254128C1D0 for <tcpm@ietf.org>; Wed, 10 Feb 2010 02:53:19 -0800 (PST)
Received: by bwz19 with SMTP id 19so1762613bwz.28 for <tcpm@ietf.org>; Wed, 10 Feb 2010 02:54:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type; bh=PQUg/MJUTWUD9iyF32gnDUCzE/zlAswIViO4CoiCazw=; b=sE4kUH5seCWQLSSXP8CL8lLYzfVyPNt8yEmq8XD5GgfJFzRz7F1/AyyShyU5WuPLax gnN0NO7fgIEwWiroXhzg1ugirHuz6G8HyxrZRsvVX8gzhpZg3MBSV1CWFM2uKcDPSnQj 3WwWlFMrU28D33vJ9G91nRoHN5hQg1aDSHyDc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=giI9bgJxH7VVIoiKqFEY9862Rvb3muILgiTtfdYGpI2GsqCB3VrG4TUxrFqXj6AgGE S+E1nNaGHVH5/yNmdUzQ/LZS8U4XYArLkBAbkTOzUwtY+MOlMe9jM126plVILtzvsp6r vYFyk7diM843Tc648elNHcyxogl6inXUqYmqI=
MIME-Version: 1.0
Received: by 10.204.140.18 with SMTP id g18mr47197bku.47.1265799265968; Wed, 10 Feb 2010 02:54:25 -0800 (PST)
Date: Wed, 10 Feb 2010 02:54:25 -0800
Message-ID: <f1548841002100254n26d23d41l98466c44c0906c83@mail.gmail.com>
From: Gregory Lebovitz <gregory.ietf@gmail.com>
To: tcpm@ietf.org, "Eddy, Wesley M. (GRC-RCN0)[Verizon]" <Wesley.M.Eddy@nasa.gov>
Content-Type: multipart/alternative; boundary="0015174c3b0e9ae181047f3cdb59"
Cc: David Borman <david.borman@windriver.com>
Subject: [tcpm] draft-ietf-tcpm-tcp-ao-crypto-02 posted
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2010 10:53:20 -0000

Team,
The updated version, tcp-ao-crypto-02, is now posted.

http://tools.ietf.org/html/draft-ietf-tcpm-tcp-ao-crypto-02

<http://tools.ietf.org/html/draft-ietf-tcpm-tcp-ao-crypto-02>Let's get these
documents rolling to IESG.

Gregory.
PS - xml2rfc is messed up right now. The Trust has released new boilerplates
ahead of the tools team, AGAIN!! I had to manually hack the .txt and trial
and error it for 2.5 hrs to get it to upload.

---------- Forwarded message ----------
From: IETF I-D Submission Tool <idsubmission@ietf.org>
Date: Wed, Feb 10, 2010 at 2:45 AM
Subject: New Version Notification for draft-ietf-tcpm-tcp-ao-crypto-02
To: gregory.ietf@gmail.com
Cc: ekr@rtfm.com



A new version of I-D, draft-ietf-tcpm-tcp-ao-crypto-02.txt has been
successfuly submitted by Gregory Lebovitz and posted to the IETF repository.

Filename:        draft-ietf-tcpm-tcp-ao-crypto
Revision:        02
Title:           Cryptographic Algorithms for TCP's Authentication Option,
TCP-AO
Creation_date:   2010-02-10
WG ID:           tcpm
Number_of_pages: 19

Abstract:
The TCP Authentication Option, TCP-AO, relies on security algorithms
to provide authentication between two end-points.  There are many
such algorithms available, and two TCP-AO systems cannot interoperate
unless they are using the same algorithms.  This document specifies
the algorithms and attributes that can be used in TCP-AO's current
manual keying mechanism.



The IETF Secretariat.





-- 
----
IETF related email from
Gregory M. Lebovitz
Juniper Networks