[Syslog] Status of syslog/dtls ISSUES
Chris Lonvick <clonvick@cisco.com> Fri, 18 June 2010 22:23 UTC
Return-Path: <clonvick@cisco.com>
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 A00E83A6970 for <syslog@core3.amsl.com>; Fri, 18 Jun 2010 15:23:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.162
X-Spam-Level:
X-Spam-Status: No, score=-9.162 tagged_above=-999 required=5 tests=[AWL=-0.052, BAYES_05=-1.11, RCVD_IN_DNSWL_HI=-8]
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 fSttTaYXANEW for <syslog@core3.amsl.com>; Fri, 18 Jun 2010 15:23:32 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id B60833A67EA for <syslog@ietf.org>; Fri, 18 Jun 2010 15:23:32 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMGAGaOG0yrR7Hu/2dsb2JhbACScQEBjCJxqECaTYUbBINS
X-IronPort-AV: E=Sophos;i="4.53,441,1272844800"; d="scan'208";a="146774203"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 18 Jun 2010 22:23:38 +0000
Received: from sjc-cde-011.cisco.com (sjc-cde-011.cisco.com [171.69.16.68]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o5IMNcRY025249 for <syslog@ietf.org>; Fri, 18 Jun 2010 22:23:38 GMT
Date: Fri, 18 Jun 2010 15:23:38 -0700
From: Chris Lonvick <clonvick@cisco.com>
To: syslog@ietf.org
Message-ID: <Pine.GSO.4.63.1006181451260.13308@sjc-cde-011.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Subject: [Syslog] Status of syslog/dtls ISSUES
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: Fri, 18 Jun 2010 22:23:34 -0000
Hi Folks, Here's where we stand on the open issues: Issue 1 - COMMENT from Alexy STATUS: One note from Tom Petch on this (combining Issues 1, 2, and 10). See Issue 10. Issue 2 - Fragmentation STATUS: Same as Issue 1. Issue 3 - Text revision from GENART review STATUS: Joe to compose text. Issue 4 - Service code subregistry STATUS: I havn't seen any review on the list but the thread was pretty conclusive. Joe to incorporate text into a new revision. Issue 5 - Reference STATUS: Joe to incorporate text proposed by Tom. Issue 6 - Reference 2 STATUS: Joe to revise ID with proposed text. Issue 7 - text STATUS: Joe to revise ID. Issue 8 - Tim Polk DISCUSS STATUS: Discussed by Tom and David. Joe to incorporate changes. Issue 9, 9a, and 9b - from a Tim Polk COMMENT STATUS: It looks like 9 and 9a have been discussed and Tom has proposed text to resolve them. Sean proposed text on 9b. I'd like some discussion on that. Issue 10 - Jari Arrko DISCUSS STATUS: Same as Issue 1. Is the text proposed by Sean good to cover all of this Issue, Issue 1 and Issue 2? Issue 11 - Adrian Farrel DISCUSS STATUS: CLOSED Issue 12 - nit STATUS: Tom agrees with this, Joe to revise text in a new ID. Issue 13 - DCCP? STATUS: With no discussion, I'm closing this. Just FYI to all, Joe has been swamped with the day job but he'll look at the issues as soon as he can. Thanks, Chris
- [Syslog] Status of syslog/dtls ISSUES Chris Lonvick
- Re: [Syslog] Status of syslog/dtls ISSUES Joseph Salowey (jsalowey)
- Re: [Syslog] Status of syslog/dtls ISSUES David Harrington
- Re: [Syslog] Status of syslog/dtls ISSUES Joseph Salowey (jsalowey)
- Re: [Syslog] Status of syslog/dtls ISSUES David Harrington
- Re: [Syslog] Status of syslog/dtls ISSUES Joseph Salowey (jsalowey)
- Re: [Syslog] Status of syslog/dtls ISSUES David Harrington
- Re: [Syslog] Status of syslog/dtls ISSUES Chris Lonvick
- Re: [Syslog] Status of syslog/dtls ISSUES David Harrington