Re: [Syslog] AD review discuss/comments for draft-ietf-syslog-dtls -DCCP and UDP

"David Harrington" <ietfdbh@comcast.net> Mon, 24 May 2010 18:38 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 CA9023A7175 for <syslog@core3.amsl.com>; Mon, 24 May 2010 11:38:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.136
X-Spam-Level: **
X-Spam-Status: No, score=2.136 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FRT_STRONG2=1.535, J_CHICKENPOX_15=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 gxdnuZP3OvJl for <syslog@core3.amsl.com>; Mon, 24 May 2010 11:38:54 -0700 (PDT)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by core3.amsl.com (Postfix) with ESMTP id 2D2E63A6FDC for <syslog@ietf.org>; Mon, 24 May 2010 11:34:41 -0700 (PDT)
Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by qmta05.westchester.pa.mail.comcast.net with comcast id MPhZ1e0031uE5Es55WaahJ; Mon, 24 May 2010 18:34:34 +0000
Received: from Harrington73653 ([207.59.110.215]) by omta16.westchester.pa.mail.comcast.net with comcast id MWaE1e00G4eszMr3cWaK5A; Mon, 24 May 2010 18:34:32 +0000
From: David Harrington <ietfdbh@comcast.net>
To: "'t.petch'" <ietfc@btconnect.com>, jsalowey@cisco.com, 'Chris Lonvick' <clonvick@cisco.com>
References: <002f01caf9ce$1c28de20$4001a8c0@gateway.2wire.net>
Date: Mon, 24 May 2010 14:34:12 -0400
Message-ID: <093e01cafb6f$bf41c2a0$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
In-Reply-To: <002f01caf9ce$1c28de20$4001a8c0@gateway.2wire.net>
Thread-Index: Acr53DDHyOvFQXIhTZCZb1hCmtLy2gBkxFew
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Cc: 'syslog' <syslog@ietf.org>
Subject: Re: [Syslog] AD review discuss/comments for draft-ietf-syslog-dtls -DCCP and UDP
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: Mon, 24 May 2010 18:38:54 -0000

Hi,

Lars provided advice quite a while back. I concur with his advice.

Implementers MUST implement support for DCCP (which should require
minimal changes from support for UDP),
so that if DCCP is available, and the operator chooses to use DCCPP,
the implementation will work with DCCP.

I view this as very similar to our standard security posture - stroing
security is MUST implement, so it is available if the operator wants
it. The operator is not required to use it.

dbh
 

> -----Original Message-----
> From: syslog-bounces@ietf.org 
> [mailto:syslog-bounces@ietf.org] On Behalf Of t.petch
> Sent: Saturday, May 22, 2010 12:44 PM
> To: jsalowey@cisco.com; Chris Lonvick
> Cc: syslog
> Subject: [Syslog] AD review discuss/comments for 
> draft-ietf-syslog-dtls -DCCP and UDP
> 
> Another issue that came up from the IESG is the relative 
> roles of UDP and DCCP
> as a substrate.  In this context, the discussions on tsvwg 
> which Lars is
> steering about SCTP, DCCP and UDP make interesting reading, with
some
> contributors asserting that the only way to get a packet 
> through a complex
> network is with UDP, that SCTP and DCCP are (comparative) 
> failures that just
> don't get recognised widely enough.
> 
> Certainly my (limited) view is that UDP is the MUST HAVE, the 
> one that will give
> maximum interoperability so while DCCP is technically 
> superior, making it the
> MUST implement will simply cause this I-D to be ignored by most.
> 
> I haven't seen any response from Lars on this issue.
> 
> Tom Petch
> 
> _______________________________________________
> Syslog mailing list
> Syslog@ietf.org
> https://www.ietf.org/mailman/listinfo/syslog
>