Re: [DNSOP] Application level DNS message fragmentation

Mukund Sivaraman <muks@isc.org> Tue, 09 December 2014 08:31 UTC

Return-Path: <muks@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CD6A1A0195 for <dnsop@ietfa.amsl.com>; Tue, 9 Dec 2014 00:31:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VCbjT1QAdWuv for <dnsop@ietfa.amsl.com>; Tue, 9 Dec 2014 00:31:18 -0800 (PST)
Received: from mail.banu.com (mail.banu.com [46.4.129.225]) by ietfa.amsl.com (Postfix) with ESMTP id 76F411A00FB for <dnsop@ietf.org>; Tue, 9 Dec 2014 00:31:18 -0800 (PST)
Received: from totoro.home.mukund.org (unknown [115.118.76.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.banu.com (Postfix) with ESMTPSA id 6C35CE6008A; Tue, 9 Dec 2014 08:31:16 +0000 (GMT)
Date: Tue, 09 Dec 2014 14:01:13 +0530
From: Mukund Sivaraman <muks@isc.org>
To: Paul Vixie <paul@redbarn.org>
Message-ID: <20141209083113.GB28876@totoro.home.mukund.org>
References: <20141208083212.GA13206@totoro.home.mukund.org> <54868E4B.9060608@redbarn.org> <20141209055839.CBC242529C28@rock.dv.isc.org> <548691D0.4090509@redbarn.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="oLBj+sq0vYjzfsbl"
Content-Disposition: inline
In-Reply-To: <548691D0.4090509@redbarn.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/BAz0tWvUT-SjiJrIu-gtoZ0yws8
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] Application level DNS message fragmentation
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Dec 2014 08:31:20 -0000

Hi Paul

On Mon, Dec 08, 2014 at 10:08:16PM -0800, Paul Vixie wrote:
> let's find out:
> 
> http://ietfreport.isoc.org/idref/draft-vixie-dnsext-edns2/

This draft mentions this feature as TCP only. The use case I was
thinking of was in getting DNS messages over UDP through, not larger
than 1<<16 message sizes. Because there is no sequence in UDP, it'd also
need the index and count in every segment/fragment.

I didn't mention label sequence compression in the prior message. In the
case of fragments over UDP, message compression would occur as before
(RFC 1035) where OFFSET is valid within a datagram (fragment).  As
offsets do not cross datagram boundaries, this would aid simple
implemementation.

		Mukund