IETF Logo Mail Archive

Re: [dnsext] draft-bellis-dnsext-dnsproxy-00

Edward Lewis <Ed.Lewis@neustar.biz> Tue, 04 November 2008 09:56 UTC

Return-Path: <owner-namedroppers@ops.ietf.org>
X-Original-To: ietfarch-namedroppers-archive-gleetwall6@core3.amsl.com
Delivered-To: ietfarch-namedroppers-archive-gleetwall6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F30AE3A6783; Tue, 4 Nov 2008 01:56:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.093
X-Spam-Level:
X-Spam-Status: No, score=-0.093 tagged_above=-999 required=5 tests=[AWL=0.402, 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 auBLAQSa0pwF; Tue, 4 Nov 2008 01:56:03 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 32E0C3A69EC; Tue, 4 Nov 2008 01:55:42 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1KxIZG-000Bdg-4q for namedroppers-data@psg.com; Tue, 04 Nov 2008 09:51:22 +0000
Received: from [66.92.146.20] (helo=stora.ogud.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <Ed.Lewis@neustar.biz>) id 1KxIZA-000Bd1-FT for namedroppers@ops.ietf.org; Tue, 04 Nov 2008 09:51:18 +0000
Received: from [41.179.11.208] (ns.md.ogud.com [10.20.30.6]) by stora.ogud.com (8.14.2/8.14.2) with ESMTP id mA49p1DG057196; Tue, 4 Nov 2008 04:51:02 -0500 (EST) (envelope-from Ed.Lewis@neustar.biz)
Mime-Version: 1.0
Message-Id: <a06240800c535c9f33c6b@[41.179.11.208]>
In-Reply-To: <OF0155F3C0.931840D8-ON802574F7.0033CA35-802574F7.00348666@nominet.org.uk>
References: <OF7E3816AF.C6D6EB41-ON802574F6.0076B6C3-802574F6.0077AF4E@nominet.org.uk> <4910067D.6070606@nlnetlabs.nl> <OF0155F3C0.931840D8-ON802574F7.0033CA35-802574F7.00348666@nominet.org.uk>
Date: Tue, 04 Nov 2008 11:50:52 +0200
To: namedroppers@ops.ietf.org
From: Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Re: [dnsext] draft-bellis-dnsext-dnsproxy-00
Cc: ed.lewis@neustar.biz
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Scanned-By: MIMEDefang 2.64 on 10.20.30.4
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>

At 9:33 +0000 11/4/08, Ray.Bellis@nominet.org.uk wrote:

>>  Yes.
>
>Has anyone ever looked to find out why this happens?

I know of one case - back when there was the hard limit of 512, one 
implementation would truncate at that and not at the end of the last 
complete RR.  Why?  All conjecture, but it is faster than clipping 
back to the last useable byte of data.

One thing to keep in mind.  When considering the receipt of data from 
the network, don't engineer to what makes sense, engineer to what 
could possibly come in.  As in the robustness principle "liberal in 
what you accept."  That doesn't mean you have to accept and digest 
what's come in, but admit that FORMERRs will happen on the remote end 
or at intermediate boxes and write code that won't barf on it.
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                                +1-571-434-5468
NeuStar

Never confuse activity with progress.  Activity pays more.

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>

v2.23.0 | Report a Bug | By Email