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

<Pasi.Eronen@nokia.com> Wed, 26 May 2010 06:05 UTC

Return-Path: <Pasi.Eronen@nokia.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 80ECF3A6862 for <syslog@core3.amsl.com>; Tue, 25 May 2010 23:05:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.554
X-Spam-Level:
X-Spam-Status: No, score=-4.554 tagged_above=-999 required=5 tests=[AWL=0.556, BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4]
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 F4Frrv8eG0S6 for <syslog@core3.amsl.com>; Tue, 25 May 2010 23:05:56 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id 079243A66B4 for <syslog@ietf.org>; Tue, 25 May 2010 23:05:55 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-mx03.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o4Q65M9C003414; Wed, 26 May 2010 09:05:40 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 26 May 2010 09:05:22 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.7]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 26 May 2010 09:05:22 +0300
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.106]) by nok-am1mhub-03.mgdnok.nokia.com ([65.54.30.7]) with mapi; Wed, 26 May 2010 08:05:21 +0200
From: Pasi.Eronen@nokia.com
To: tim@evensweb.com, turners@ieca.com, ietfc@btconnect.com
Date: Wed, 26 May 2010 08:03:01 +0200
Thread-Topic: [Syslog] AD review discuss/comments for draft-ietf-syslog-dtls
Thread-Index: Acr8FLlBV0YM+QjuSfWdd2YLJgHcHQAhF/hG
Message-ID: <808FD6E27AD4884E94820BC333B2DB775BC0E0952B@NOK-EUMSG-01.mgdnok.nokia.com>
References: <20100525101440.27134@web2.nyc1.bluetie.com>
In-Reply-To: <20100525101440.27134@web2.nyc1.bluetie.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 26 May 2010 06:05:22.0502 (UTC) FILETIME=[6D281660:01CAFC99]
X-Nokia-AV: Clean
Cc: syslog@ietf.org
Subject: Re: [Syslog] AD review discuss/comments for draft-ietf-syslog-dtls
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, 26 May 2010 06:05:57 -0000

Tim Evens wrote:
> Correct, in RFC5426 the max size is 64K which is the max length in
> UDP.  UDP sizes of greater than MTU are only achievable via IP layer
> fragmentation, as you also indicated.  I'm under the impression that
> DTLS does NOT support IPv4 fragmentation since in RFC4347 it states
> in Section 4.1.1 "Each DTLS record MUST fit within a single
> datagram."

AFAIK when running DTLS over UDP, "datagram" here refers to UDP
datagrams, not IP packets (and one UDP datagram can be split
to several IP packets).

Best regards,
Pasi