Re: [Syslog] RFC 5848 on Signed Syslog Messages
"David Harrington" <ietfdbh@comcast.net> Thu, 13 May 2010 20:54 UTC
Return-Path: <ietfdbh@comcast.net>
X-Original-To: syslog@core3.amsl.com
Delivered-To: syslog@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 080AA3A6837 for <syslog@core3.amsl.com>; Thu, 13 May 2010 13:54:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.043
X-Spam-Level:
X-Spam-Status: No, score=0.043 tagged_above=-999 required=5 tests=[AWL=-0.558, BAYES_50=0.001, J_CHICKENPOX_93=0.6]
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 cdZHMUIkbdfS for <syslog@core3.amsl.com>; Thu, 13 May 2010 13:54:23 -0700 (PDT)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [76.96.59.227]) by core3.amsl.com (Postfix) with ESMTP id F37893A68F8 for <syslog@ietf.org>; Thu, 13 May 2010 13:54:22 -0700 (PDT)
Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta12.westchester.pa.mail.comcast.net with comcast id H8Ur1e0081wpRvQ5C8uE58; Thu, 13 May 2010 20:54:14 +0000
Received: from Harrington73653 ([67.189.235.106]) by omta18.westchester.pa.mail.comcast.net with comcast id H8uD1e00W2JQnJT3e8uENW; Thu, 13 May 2010 20:54:14 +0000
From: David Harrington <ietfdbh@comcast.net>
To: syslog@ietf.org
References: <20100511192814.5BA6AE0699@rfc-editor.org>
Date: Thu, 13 May 2010 16:54:11 -0400
Message-ID: <002e01caf2de$7077a070$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcrxQJJoK2f6lLp8Q3+ulJ+jNWyY7ABncj1w
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <20100511192814.5BA6AE0699@rfc-editor.org>
Subject: Re: [Syslog] RFC 5848 on Signed Syslog Messages
X-BeenThere: syslog@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Issues in Network Event Logging <syslog.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/syslog>, <mailto:syslog-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/syslog>
List-Post: <mailto:syslog@ietf.org>
List-Help: <mailto:syslog-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/syslog>, <mailto:syslog-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 May 2010 20:54:24 -0000
Congratulations! Work well done. dbh > -----Original Message----- > From: syslog-bounces@ietf.org > [mailto:syslog-bounces@ietf.org] On Behalf Of > rfc-editor@rfc-editor.org > Sent: Tuesday, May 11, 2010 3:28 PM > To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org > Cc: syslog@ietf.org; rfc-editor@rfc-editor.org > Subject: [Syslog] RFC 5848 on Signed Syslog Messages > > > A new Request for Comments is now available in online RFC libraries. > > > RFC 5848 > > Title: Signed Syslog Messages > Author: J. Kelsey, J. Callas, > A. Clemm > Status: Standards Track > Stream: IETF > Date: May 2010 > Mailbox: john.kelsey@nist.gov, > jon@callas.org, > alex@cisco.com > Pages: 40 > Characters: 102805 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-ietf-syslog-sign-29.txt > > URL: http://www.rfc-editor.org/rfc/rfc5848.txt > > This document describes a mechanism to add origin authentication, > message integrity, replay resistance, message sequencing, and > detection of missing messages to the transmitted syslog messages. > This specification is intended to be used in conjunction with the > work defined in RFC 5424, "The Syslog Protocol". [STANDARDS TRACK] > > This document is a product of the Security Issues in Network > Event Logging Working Group of the IETF. > > This is now a Proposed Standard Protocol. > > STANDARDS TRACK: This document specifies an Internet standards track > protocol for the Internet community,and requests discussion > and suggestions > for improvements. Please refer to the current edition of the Internet > Official Protocol Standards (STD 1) for the standardization state and > status of this protocol. Distribution of this memo is unlimited. > > This announcement is sent to the IETF-Announce and rfc-dist lists. > To subscribe or unsubscribe, see > http://www.ietf.org/mailman/listinfo/ietf-announce > http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > > 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 > Association Management Solutions, LLC > > > _______________________________________________ > Syslog mailing list > Syslog@ietf.org > https://www.ietf.org/mailman/listinfo/syslog >
- [Syslog] RFC 5848 on Signed Syslog Messages rfc-editor
- Re: [Syslog] RFC 5848 on Signed Syslog Messages David Harrington
- Re: [Syslog] RFC 5848 on Signed Syslog Messages Chris Lonvick
- Re: [Syslog] RFC 5848 on Signed Syslog Messages Alexander Clemm (alex)