RE: Context specific semantics was Re: uncooperative DNSBLs, was several messages
"Hardie, Ted" <hardie@qualcomm.com> Fri, 14 November 2008 15:45 UTC
Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F24133A6808; Fri, 14 Nov 2008 07:45:52 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C343C3A6808 for <ietf@core3.amsl.com>; Fri, 14 Nov 2008 07:45:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.099
X-Spam-Level:
X-Spam-Status: No, score=-106.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 YX38demxaNRt for <ietf@core3.amsl.com>; Fri, 14 Nov 2008 07:45:50 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id E8ECD3A677C for <ietf@ietf.org>; Fri, 14 Nov 2008 07:45:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=hardie@qualcomm.com; q=dns/txt; s=qcdkim; t=1226677550; x=1258213550; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version:x-ironport-av; z=From:=20"Hardie,=20Ted"=20<hardie@qualcomm.com>|To:=20To ny=20Finch=20<dot@dotat.at>|CC:=20Andrew=20Sullivan=20<aj s@shinkuro.com>,=20"ietf@ietf.org"=20<ietf@ietf.org> |Date:=20Fri,=2014=20Nov=202008=2007:45:39=20-0800 |Subject:=20RE:=20Context=20specific=20semantics=20was=20 Re:=20uncooperative=20DNSBLs,=20was=0D=0A=20several=20mes sages|Thread-Topic:=20Context=20specific=20semantics=20wa s=20Re:=20uncooperative=20DNSBLs,=20was=0D=0A=20several =20messages|Thread-Index:=20AclGUjF1PIwVSGsuRwCoTKJmjdtOP AAHFhOA|Message-ID:=20<3C93394994880A4597E4710855851C031E FCBA47@NASANEXMB12.na.qualcomm.com>|References:=20<Pine.L NX.4.33.0811121942450.12067-100000@egate.xpasc.com>=0D=0A =20<20081113112302.38928.qmail@simone.iecc.com>=0D=0A=20< e0c581530811130740g1db5cbfehbcdad361660bf48b@mail.gmail.c om>=0D=0A=20<491C5339.8090801@dcrocker.net>=20<2008111316 3833.GN76118@shinkuro.com>=0D=0A=20<491C699B.4000702@nort el.com>=20<20081113180841.GO76118@shinkuro.com>=0D=0A=20< 491C711C.3030605@leisi.net>=20<20081113183919.GR76118@shi nkuro.com>=0D=0A=20<p06240603c542266a5094@[10.227.68.106] >=0D=0A=20<alpine.LSU.2.00.0811131922190.14367@hermes-1.c si.cam.ac.uk>=0D=0A=20<p06240605c54237e869f2@[10.227.68.1 06]>,<alpine.LSU.2.00.0811141209490.14367@hermes-1.csi.ca m.ac.uk>|In-Reply-To:=20<alpine.LSU.2.00.0811141209490.14 367@hermes-1.csi.cam.ac.uk>|Accept-Language:=20en-US |Content-Language:=20en-US|X-MS-Has-Attach: |X-MS-TNEF-Correlator:|acceptlanguage:=20en-US |Content-Type:=20text/plain=3B=20charset=3D"us-ascii" |Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 300,2777,5433"=3B=20a=3D"12949308"; bh=vhy3RNic6pt9SfIsCiC5g7qTaIT356xmAarCMpzldy4=; b=GGpyE77efDeJYH7VxdNXiQY1KMvWLaKe4E2deyYZ8FSjetslh4Gmfbxv q2/2FRhP2HYJISmDvGMmBPMg0merZ4zx82MCBh5h3JuMS7YuZouQsb5Mg VWzCg/6VfyYxHFCbi2ewxb9qhrIc/w+6mfZrsmd8sbHKevJpFE0FJzx7K g=;
X-IronPort-AV: E=McAfee;i="5300,2777,5433"; a="12949308"
Received: from pdmz-ns-mip.qualcomm.com (HELO ithilien.qualcomm.com) ([199.106.114.10]) by wolverine01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 14 Nov 2008 07:45:50 -0800
Received: from msgtransport04.qualcomm.com (msgtransport04.qualcomm.com [129.46.61.156]) by ithilien.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id mAEFjnVd023422 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 14 Nov 2008 07:45:50 -0800
Received: from nasanexhub06.na.qualcomm.com (nasanexhub06.na.qualcomm.com [129.46.134.254]) by msgtransport04.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id mAEFjaI5007752 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 14 Nov 2008 07:45:49 -0800
Received: from NASANEXMB12.na.qualcomm.com ([10.45.78.33]) by nasanexhub06.na.qualcomm.com ([129.46.134.254]) with mapi; Fri, 14 Nov 2008 07:45:39 -0800
From: "Hardie, Ted" <hardie@qualcomm.com>
To: Tony Finch <dot@dotat.at>
Date: Fri, 14 Nov 2008 07:45:39 -0800
Subject: RE: Context specific semantics was Re: uncooperative DNSBLs, was several messages
Thread-Topic: Context specific semantics was Re: uncooperative DNSBLs, was several messages
Thread-Index: AclGUjF1PIwVSGsuRwCoTKJmjdtOPAAHFhOA
Message-ID: <3C93394994880A4597E4710855851C031EFCBA47@NASANEXMB12.na.qualcomm.com>
References: <Pine.LNX.4.33.0811121942450.12067-100000@egate.xpasc.com> <20081113112302.38928.qmail@simone.iecc.com> <e0c581530811130740g1db5cbfehbcdad361660bf48b@mail.gmail.com> <491C5339.8090801@dcrocker.net> <20081113163833.GN76118@shinkuro.com> <491C699B.4000702@nortel.com> <20081113180841.GO76118@shinkuro.com> <491C711C.3030605@leisi.net> <20081113183919.GR76118@shinkuro.com> <p06240603c542266a5094@[10.227.68.106]> <alpine.LSU.2.00.0811131922190.14367@hermes-1.csi.cam.ac.uk> <p06240605c54237e869f2@[10.227.68.106]>, <alpine.LSU.2.00.0811141209490.14367@hermes-1.csi.cam.ac.uk>
In-Reply-To: <alpine.LSU.2.00.0811141209490.14367@hermes-1.csi.cam.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
________________________________________ From: Tony Finch [fanf2@hermes.cam.ac.uk] On Behalf Of Tony Finch [dot@dotat.at] Sent: Friday, November 14, 2008 4:11 AM To: Hardie, Ted Cc: Andrew Sullivan; ietf@ietf.org Subject: Re: Context specific semantics was Re: uncooperative DNSBLs, was several messages On Thu, 13 Nov 2008, Ted Hardie wrote: > > That's an example in which an A record in this zone has the standard DNS > meaning and the expectation is that you can use it construct a URI. > The other A records have a specific meaning in which the data returned > indicates that indicates something about its reputation in a specific > context (what reputation etc. being context specific). One of these > things is not like the other. Using the same record type for both > creates a need to generate some other context that enables you to figure > out what was really meant. I understand the argument that DNSBLs break the DNS data model. What I don't see is any evidence that this causes interoperability problems. Tony. -- f.anthony.n.finch <dot@dotat.at> http://dotat.at/ VIKING NORTH UTSIRE SOUTH UTSIRE: WEST OR SOUTHWEST 5 OR 6 INCREASING 6 TO GALE 8, OCCASIONALLY SEVERE GALE 9 IN VIKING. ROUGH, BECOMING VERY ROUGH OR HIGH. RAIN THEN SQUALLY SHOWERS. MODERATE OR GOOD, OCCASIONALLY POOR AT FIRST. Since you now have two different meanings for what an A record is, you now need two different code trees that understand what A records are, and those code trees are not interoperable. Standard libraries called in this circumstance won't work, and you'll need some mechanism to disambiguate the context so you know when to call the special library for a-record-in-dsnbl versus the code in a-record-in-standard-dns. At the moment, this is by application, but it may not always stay that way. Since new RRs are substantially easier to get and use than they used to be, Andrew and Olafur have suggested that this work transition to using one, so that the current re-use can be phased out. I support that, and I would be very concerned about the IETF standardizing something that breaks the DNS model. We've started down that path on a couple of occasions, and it hasn't been all that pretty. Having the DNS remain a single namespace with as few context dependencies as we can is pretty important, in my opinion, and the costs to moving back into the standard way of doing things (over time, as they pointed out) does not appear to be onerous, especially if tied to some other transition. regards, Ted Hardie _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- Re: several messages der Mouse
- Re: several messages David Morris
- Re: several messages Dean Anderson
- Re: several messages Randy Presuhn
- Re: several messages David Morris
- Re: several messages Matthias Leisi
- Re: several messages Steve Linford
- Re: several messages Peter Dambier
- Re: several messages Steve Linford
- Re: several messages Keith Moore
- Re: several messages der Mouse
- Re: several messages Chris Lewis
- Re: several messages Mark Andrews
- Re: several messages der Mouse
- Re: several messages Chris Lewis
- Re: several messages David Romerstein
- Re: several messages Randy Presuhn
- Re: several messages Chris Lewis
- Re: several messages David Romerstein
- Re: several messages David Romerstein
- Re: several messages Keith Moore
- Re: several messages Chris Lewis
- Re: several messages Al Iverson
- More anti-spam (was: Re: several messages) John C Klensin
- RE: several messages michael.dillon
- Re: several messages Matthias Leisi
- Re: several messages Mark Andrews
- Re: several messages David Morris
- Re: several messages Al Iverson
- Re: uncooperative DNSBLs, was several messages John Levine
- Re: uncooperative DNSBLs, was several messages Jim Hill
- Re: several messages John C Klensin
- Re: several messages Al Iverson
- RE: several messages Hallam-Baker, Phillip
- Re: uncooperative DNSBLs, was several messages Matthias Leisi
- Re: uncooperative DNSBLs, was several messages Al Iverson
- RE: several messages Anthony Purcell
- Re: uncooperative DNSBLs, was several messages Dave CROCKER
- Re: several messages der Mouse
- Re: uncooperative DNSBLs, was several messages Andrew Sullivan
- Re: uncooperative DNSBLs, was several messages David Romerstein
- Re: uncooperative DNSBLs, was several messages Jim Hill
- Re: several messages Chris Lewis
- Re: uncooperative DNSBLs, was several messages Chris Lewis
- Re: uncooperative DNSBLs, was several messages John C Klensin
- Re: uncooperative DNSBLs, was several messages Dave CROCKER
- Re: uncooperative DNSBLs, was several messages Tony Finch
- Re: uncooperative DNSBLs, was several messages Andrew Sullivan
- Re: uncooperative DNSBLs, was several messages John C Klensin
- Re: uncooperative DNSBLs, was several messages Matthias Leisi
- Re: uncooperative DNSBLs, was several messages Al Iverson
- Re: uncooperative DNSBLs, was several messages Andrew Sullivan
- Re: uncooperative DNSBLs, was several messages John C Klensin
- Re: uncooperative DNSBLs, was several messages Ted Hardie
- Re: uncooperative DNSBLs, was several messages Matthias Leisi
- Re: uncooperative DNSBLs, was several messages Ted Hardie
- Re: uncooperative DNSBLs, was several messages Tony Finch
- Context specific semantics was Re: uncooperative … Ted Hardie
- Clarifying harm to DNS (was: uncooperative DNSBLs… Andrew Sullivan
- Re: Context specific semantics was Re: uncooperat… Ted Hardie
- Re: uncooperative DNSBLs, IETF misinformation (wa… Steve Linford
- RE: Context specific semantics was Re: uncooperat… Hallam-Baker, Phillip
- Re: uncooperative DNSBLs, was several messages Peter Dambier
- Re: uncooperative DNSBLs, was several messages David Romerstein
- Re: uncooperative DNSBLs, was several messages Peter Dambier
- Re: uncooperative DNSBLs, was several messages Keith Moore
- Re: uncooperative DNSBLs, was several messages Chris Lewis
- RE: uncooperative DNSBLs, IETF misinformation (wa… michael.dillon
- Re: uncooperative DNSBLs, IETF misinformation (wa… Steve Linford
- RE: uncooperative DNSBLs, IETF misinformation (wa… michael.dillon
- Re: Context specific semantics was Re: uncooperat… Tony Finch
- Re: Context specific semantics was Re: uncooperat… John Levine
- RE: Context specific semantics was Re: uncooperat… Hardie, Ted
- RE: Context specific semantics was Re: uncooperat… Tony Finch
- Re: several messages Rich Kulawiec
- Re: uncooperative DNSBLs, was several messages Rich Kulawiec
- Re: uncooperative DNSBLs, IETF misinformation (wa… Al Iverson
- Re: Context specific semantics was Re: uncooperat… Ted Hardie
- RE: Context specific semantics was Re: uncooperat… Ted Hardie
- Re: several messages John C Klensin
- Re: several messages Al Iverson
- Re: Context specific semantics was Re: uncooperat… John L
- RE: uncooperative DNSBLs, IETF misinformation (wa… michael.dillon
- Re: uncooperative DNSBLs, IETF misinformation (wa… Al Iverson
- RE: uncooperative DNSBLs, IETF misinformation (wa… michael.dillon
- Re: several messages John C Klensin
- Re: several messages Chris Lewis
- Re: uncooperative DNSBLs, IETF misinformation (wa… Keith Moore
- Re: several messages Al Iverson
- RE: several messages michael.dillon
- Re: uncooperative DNSBLs, IETF misinformation (wa… Al Iverson
- Re: Context specific semantics was Re: uncooperat… Ted Hardie
- Re: Context specific semantics was Re: uncooperat… Douglas Otis
- Re: uncooperative DNSBLs, IETF misinformation (wa… Theodore Tso
- Re: Context specific semantics was Re: uncooperat… Theodore Tso
- Re: uncooperative DNSBLs, IETF misinformation (wa… Chris Lewis
- Re: more bad ideas, was uncooperative DNSBLs, was… John Levine
- Re: more bad ideas, was uncooperative DNSBLs, was… Chris Lewis
- Re: Context specific semantics was Re: uncooperat… John L
- Detecting and disabling bad DNSBLs Peter Dambier
- Re: Detecting and disabling bad DNSBLs Steve Linford
- Re: several messages Pekka Savola
- Re: more bad ideas, was uncooperative DNSBLs, was… Keith Moore
- Re: several messages Rich Kulawiec
- Is USA qualified for 2.3 of draft-palet-ietf-meet… YAO
- RE: [73attendees] Is USA qualified for 2.3 ofdraf… Song Haibin
- Re: several messages Tom.Petch
- Re: [73attendees] Is USA qualified for 2.3 of dra… Phillip Hallam-Baker
- Re: [73attendees] Is USA qualified for 2.3 of dra… james woodyatt
- Re: several messages John C Klensin