IETF Logo Mail Archive

Re: [DNSOP] Last Call: <draft-ietf-dnsop-5966bis-04.txt> (DNS Transport over TCP - Implementation Requirements) to Internet Standard

"Wessels, Duane" <dwessels@verisign.com> Mon, 23 November 2015 19:42 UTC

Return-Path: <dwessels@verisign.com>
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 6D8C61B32F6 for <dnsop@ietfa.amsl.com>; Mon, 23 Nov 2015 11:42:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
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 POEtNWRcN3gj for <dnsop@ietfa.amsl.com>; Mon, 23 Nov 2015 11:42:21 -0800 (PST)
Received: from mail-oi0-x263.google.com (mail-oi0-x263.google.com [IPv6:2607:f8b0:4003:c06::263]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00F781B32F2 for <dnsop@ietf.org>; Mon, 23 Nov 2015 11:42:20 -0800 (PST)
Received: by oibl204 with SMTP id l204so12507290oib.3 for <dnsop@ietf.org>; Mon, 23 Nov 2015 11:42:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verisign-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :content-type:content-id:content-transfer-encoding:mime-version; bh=Wp6mejAJ5VWuCYbUJROKamxN62Nb9mrz2Bz0Z0H+qrk=; b=vvjqFaC3DhZiHVtnS2rHS5D57aHkuh24GbPVkMJPjNIgm5oaQ52v/EH/Kh5mTu2RXz HqEXVCu71TPXEDxiaheDJDs5xZNUPJMQQbUVxAv8NNOK+zvrstqzkqi7Q43yiHQ5gExF 1ZsyIIn2pBBYivYvdyIffDOcGjLQ6IeoY+GL4f+nogfYRYZdjf8haFjZiBoyciCpgkC/ co7BEdyIBTp8D8sDqWEOexjVq+Z5Q2x+RTiNsh6aeTk83FBAKVg6LVe8P9BMiwj7cJMR bXAKnAvwT96QPMIdzO8TaXmlnTW4BYk/O+MPy7AjDSpiPndXl8n4m04ga+8rH9eN2/jE ZfCA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:content-type:content-id:content-transfer-encoding :mime-version; bh=Wp6mejAJ5VWuCYbUJROKamxN62Nb9mrz2Bz0Z0H+qrk=; b=BItrcPBP1wkHsCWsaP3bnHZYmDZ44plQ5Qf5cvapWC8sWvBkXyg/qhtpOt+Tafg2RS tlngIhrXgntWgB6nE4Ba2v0KfDXtVlJyLoMTFwT6gBy2VjMVHgBKPkjXpuUE7Z7Y5qkJ zj9bh3aO5yyArUmQ5lePlHhaScFTI3wMkcf+EdvxKPYyEqpLCx1rYUGfKebXPKVs6t/H uxew3GDx5rdwexOcU/6YU1yG0RcrC0hxi1ghO1n/4hm5swXHUpHRyUWKwZkY/9DAMfAg /mbzVErQGTRKdJvmtPA3A0YWnH6jQYd43FoTb+NVOThszOoQdijseiZRz6znml113KtR 3o1w==
X-Gm-Message-State: ALoCoQlAJZieKBnhcv+9CDcKbTLMFcj49FzP1dKccsBDIOKfnAIrc+yijP9ANin3qY6SHOGEfLcVqlRCubZCFqvLJJvE5UIjDQ==
X-Received: by 10.55.31.205 with SMTP id n74mr28941720qkh.50.1448307740137; Mon, 23 Nov 2015 11:42:20 -0800 (PST)
Received: from brn1lxmailout02.verisign.com (brn1lxmailout02.verisign.com. [72.13.63.42]) by smtp-relay.gmail.com with ESMTPS id c15sm1737314qkb.11.2015.11.23.11.42.19 (version=TLS1 cipher=AES128-SHA bits=128/128); Mon, 23 Nov 2015 11:42:20 -0800 (PST)
X-Relaying-Domain: verisign.com
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01 [10.173.152.255]) by brn1lxmailout02.verisign.com (8.13.8/8.13.8) with ESMTP id tANJgJIH028449 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 23 Nov 2015 14:42:19 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Mon, 23 Nov 2015 14:42:17 -0500
From: "Wessels, Duane" <dwessels@verisign.com>
To: Mukund Sivaraman <muks@isc.org>
Thread-Topic: [DNSOP] Last Call: <draft-ietf-dnsop-5966bis-04.txt> (DNS Transport over TCP - Implementation Requirements) to Internet Standard
Thread-Index: AQHRJfb9U0Rd5c58I0i7V1QiSrSo+p6qGhQAgAA75IA=
Date: Mon, 23 Nov 2015 19:42:16 +0000
Message-ID: <15C921FB-043B-40FA-800E-311D52136A20@verisign.com>
References: <20151123135808.2730.32721.idtracker@ietfa.amsl.com> <20151123160748.GA3031@jurassic.l0.malgudi.org>
In-Reply-To: <20151123160748.GA3031@jurassic.l0.malgudi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E80FAB0A85C7B64F81CDC57D0CDEC5DA@verisign.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/XOEgC8UPLHlObAWzSfPN36blEbI>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] Last Call: <draft-ietf-dnsop-5966bis-04.txt> (DNS Transport over TCP - Implementation Requirements) to Internet Standard
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 23 Nov 2015 19:42:22 -0000

> On Nov 23, 2015, at 8:07 AM, Mukund Sivaraman <muks@isc.org> wrote:
> 
> It seems that AXFR messages would have to be sent in order to avoid
> confusion at the client about when a transfer correctly completed
> vs. when it timed out. While they can be multiplexed with other DNS
> messages, the individual messages of a single transfer must not be sent
> out of order.
> 
> Similarly, describe IXFR too.

Hi Mukund,

The document authors have discussed this and we feel the addition of this
paragraph in section 7 addresses the issue that you've raised:

   Note that AXFR [RFC5936] and IXFR [RFC1995] have the property that
   one query message might result in multiple response messages.
   Therefore, those protocols have their own specific ordering
   requirements.

Look reasonable?

DW

v2.23.0 | Report a Bug | By Email