IETF Logo Mail Archive

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

"Dan Wing" <dwing@cisco.com> Mon, 03 November 2008 19:58 UTC

Return-Path: <owner-namedroppers@ops.ietf.org>
X-Original-To: ietfarch-dnsext-archive@core3.amsl.com
Delivered-To: ietfarch-dnsext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 534BD3A6933; Mon, 3 Nov 2008 11:58:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.474
X-Spam-Level:
X-Spam-Status: No, score=-5.474 tagged_above=-999 required=5 tests=[AWL=-0.979, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, 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 eQIsv9mQv7d7; Mon, 3 Nov 2008 11:58:36 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 542673A69EC; Mon, 3 Nov 2008 11:58:36 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1Kx5Uz-000HMb-Qt for namedroppers-data@psg.com; Mon, 03 Nov 2008 19:54:05 +0000
Received: from [171.71.176.70] (helo=sj-iport-1.cisco.com) by psg.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.69 (FreeBSD)) (envelope-from <dwing@cisco.com>) id 1Kx5Uu-000HLo-JF for namedroppers@ops.ietf.org; Mon, 03 Nov 2008 19:54:03 +0000
X-IronPort-AV: E=Sophos;i="4.33,538,1220227200"; d="scan'208";a="99585842"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-1.cisco.com with ESMTP; 03 Nov 2008 19:54:00 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id mA3JrxOg007965; Mon, 3 Nov 2008 11:53:59 -0800
Received: from dwingwxp01 ([10.32.240.195]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id mA3JrxZY001274; Mon, 3 Nov 2008 19:53:59 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Nicholas Weaver' <nweaver@ICSI.Berkeley.EDU>
Cc: Ray.Bellis@nominet.org.uk, namedroppers@ops.ietf.org, 'bert hubert' <bert.hubert@netherlabs.nl>
References: <OFDEB3E292.34C937FA-ON802574EF.005C7131-802574EF.005D153A@nominet.org.uk> <OFCF9D79AB.6203C74E-ON802574F6.005713B9-802574F6.005724A5@nominet.org.uk> <20081103174613.GA27149@outpost.ds9a.nl> <OFF06D2D25.C41A52AD-ON802574F6.0061EC03-802574F6.006247DD@nominet.org.uk> <20081103190014.GB27149@outpost.ds9a.nl> <0127DE81-27BB-4127-9DC0-2ED25DBE572B@icsi.berkeley.edu>
Subject: RE: [dnsext] draft-bellis-dnsext-dnsproxy-00
Date: Mon, 03 Nov 2008 11:53:59 -0800
Message-ID: <013301c93ded$e9c2efe0$c3f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <0127DE81-27BB-4127-9DC0-2ED25DBE572B@icsi.berkeley.edu>
Thread-Index: Ack96uH/6rwsbCKTTOO0wMEA4wBDNQAApSlg
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1784; t=1225742039; x=1226606039; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dwing@cisco.com; z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com> |Subject:=20RE=3A=20[dnsext]=20draft-bellis-dnsext-dnsproxy -00 |Sender:=20; bh=LtCkQRtPrOQigyudWd5XosvHjoS+uV9cBk9RlKlIIlE=; b=FXUyWSkG85SlnNWvOmmAi262VeEscy5KDI3JZeq8f5/Joj7Ybqp5B3x/Tk WDu0CpbO3bd9QNYKKDi1scPSRA3o3IYvsHCMCVZWjtOUrlmxLO3f0WftwaBX /mt4oKB3Pu;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; );
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>

 

> -----Original Message-----
> From: owner-namedroppers@ops.ietf.org 
> [mailto:owner-namedroppers@ops.ietf.org] On Behalf Of Nicholas Weaver
> Sent: Monday, November 03, 2008 11:31 AM
> To: bert hubert
> Cc: Nicholas Weaver; Ray.Bellis@nominet.org.uk; 
> namedroppers@ops.ietf.org
> Subject: Re: [dnsext] draft-bellis-dnsext-dnsproxy-00
> 
> 
> On Nov 3, 2008, at 11:00 AM, bert hubert wrote:
> >
> > That would be good - this also argues for not adding heaps 
> of other  
> > stuff to
> > the RFC - I think everybody would like to have his pet DNS 
> difficulty
> > included, but overall that would not help achieve greater 
> compliance.
> 
> I think the most important behavior is "Get Outta the Way!"
> 
> Namely, any such device MUST not block direct access to an arbitrary  
> remote DNS server from an end-host, with the packet payload 
> unchanged, and SHOULD not change the UDP SRC port selected by 
> the end-host.

Preserving the UDP source port is not possible if there are two hosts 
behind a NAT and those two hosts use the same UDP source port.  

-d


> There will always be cases where the policy on any in-path device is  
> incorrect.  Therefore the most important policy that a NAT or 
> similar  
> device should have with regards to DNS traffic is the ability to  
> bypass any proxying or other such manipulation.
> 
> This is, IMO, absolutely essential, because everything else can be  
> worked around as long as the stub resolver can access whatever  
> external resources it deems necessary.
> 
> 
> --
> 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/>


--
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