Re: [Syslog] Issues for dtls-udp Re: Missing dead peer detection in DTLS (Gerhard Muenz)

fenghongyan <hongyanfeng@huaweisymantec.com> Wed, 05 August 2009 09:17 UTC

Return-Path: <hongyanfeng@huaweisymantec.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 AE5FE3A67ED for <syslog@core3.amsl.com>; Wed, 5 Aug 2009 02:17:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level:
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
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 hWCiHf-OtDlY for <syslog@core3.amsl.com>; Wed, 5 Aug 2009 02:17:55 -0700 (PDT)
Received: from mta2.huaweisymantec.com (unknown [218.17.155.15]) by core3.amsl.com (Postfix) with ESMTP id B62AC3A6B87 for <syslog@ietf.org>; Wed, 5 Aug 2009 02:17:55 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-disposition: inline
Content-type: text/plain; charset="us-ascii"
Received: from hstml02-in.huaweisymantec.com ([172.26.3.42]) by hstga02-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTP id <0KNW00LAPCG3BE90@hstga02-in.huaweisymantec.com> for syslog@ietf.org; Wed, 05 Aug 2009 17:16:51 +0800 (CST)
Received: from huaweisymantec.com ([127.0.0.1]) by hstml02-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTP id <0KNW00CTFCG36410@hstml02-in.huaweisymantec.com> for syslog@ietf.org; Wed, 05 Aug 2009 17:16:51 +0800 (CST)
Received: from [10.27.154.136] by hstml02-in.huaweisymantec.com (mshttpd); Wed, 05 Aug 2009 17:16:51 +0800
From: fenghongyan <hongyanfeng@huaweisymantec.com>
To: Gerhard Muenz <muenz@net.in.tum.de>
Message-id: <fc5fabd5334d.4a79be83@huaweisymantec.com>
Date: Wed, 05 Aug 2009 17:16:51 +0800
X-Mailer: Sun Java(tm) System Messenger Express 6.3-8.03 (built Apr 24 2009; 32bit)
Content-language: zh-CN
X-Accept-Language: zh-CN
Priority: normal
In-reply-to: <4A786066.2080505@net.in.tum.de>
References: <mailman.152.1248807621.17772.syslog@ietf.org> <fc16b80131ef.4a75658d@huaweisymantec.com> <4A75F11B.4050201@net.in.tum.de> <fbc4f6346109.4a78c7e4@huaweisymantec.com> <4A786066.2080505@net.in.tum.de>
Cc: syslog@ietf.org
Subject: Re: [Syslog] Issues for dtls-udp Re: Missing dead peer detection in DTLS (Gerhard Muenz)
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: Wed, 05 Aug 2009 09:17:56 -0000

Hi,
  
>  The definition of IPFIX Transport Sessions allows to distinguish the
>  different sessions. In the case of UDP, the Transport Session is defined
>  by the IP-5-Tuple plus the Observation Domain ID, which is a field in
>  the IPFIX message header.
>  In the case of DTLS/UDP, the Collector needs to maintain the DTLS state
>  for each Exporter.

In the case of UDP, the application can get message through udp directly. 
But for DTLS/UDP, each session maintains the DTLS state for each Exporter, and DTLS has no idea about
which session is for which exporter. Which need application maintains, like using IP-5-Tuple plus the Observation Domain ID
mapping to each session.

>  
>  A good question is when to remove the DTLS state because there is no
>  connection termination. We remove it after a certain time without
>  receiving any packets from the Exporter. However, we cannot be sure if
>  the Exporter has also deleted its DTLS state :(
>  This is another situation where DTLS Heartbeat extension is useful.

I share this opinion. "timeout" can also work for it.

>  > There may many syslog sender send logs to one receiver, which 
> brings up an issue of dtls-udp.
>  > I wrote it in my proposal, in 5.3 as session demultiplexing. 
>  > 
>  > I think if the ipfix collector need support multiple exporter, 
> ipfix need also support session demultiplexing,
>  > but I didn't see that in your proposal, what's your consideration?
>  
>  You talk about draft-mentz-ipfix-dtls-recommendations-00?
>  Note that this draft does not play the same role as
>  draft-feng-syslog-transport-dtls-01 because IPFIX over DTLS/UDP is
>  already standardized in RFC5101.
>  draft-mentz-ipfix-dtls-recommendations-00 only covers DTLS specific
>  implementation problems and might be considered as an update of RFC 5153
>  (IPFIX Implementation Guidelines).
>  
I mean that is the application need to implement when using DTLS/UDP as transport,
which is the issue of DTLS/UDP, I stated in my proposal, but I didn't see you add any comments
on it:(. That is why I asked if you have any other consideration. I asked for your valuable comments.



Thanks
Linda

>  Gerhard
>