![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Keith Moore <moore at network-heretics.com> writes: > So it's not a question of whether DNS is less reliable than IP (it is), > or even whether the reliability of DNS + IP is less than that of IP > alone (it is). It's a question of whether increasing reliance on DNS by > trying to get apps and other things to use DNS names exclusively, makes > those apps and other things less reliable. No. Your argument seems to be "because relying even more on DNS than we do today makes things more brittle, BAD, BAD BAD, we cannot go there." The more relevant engineering question is whether the benefits of such an approach outweigh the downsides. Sure there are downsides. But there are also real potential benefits. Some of them potentially From ietf-bounces at ietf.org Fri Dec 5 06:35:26 2008 Return-Path: <ietf-bounces at ietf.org> X-Original-To: ietf-archive at megatron.ietf.org Delivered-To: ietfarch-ietf-archive at core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D5F1428C14F; Fri, 5 Dec 2008 06:35:25 -0800 (PST) X-Original-To: ietf at core3.amsl.com Delivered-To: ietf at core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6393628C14D; Fri, 5 Dec 2008 06:35:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.965 X-Spam-Level: X-Spam-Status: No, score=-5.965 tagged_above=-999 required=5 tests=[AWL=0.634, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 DqSVAmkgAeXa; Fri, 5 Dec 2008 06:35:23 -0800 (PST) Received: from e1.ny.us.ibm.com (e1.ny.us.ibm.com [32.97.182.141]) by core3.amsl.com (Postfix) with ESMTP id 6CA9428C149; Fri, 5 Dec 2008 06:35:23 -0800 (PST) Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e1.ny.us.ibm.com (8.13.1/8.13.1) with ESMTP id mB5EYjxb019029; Fri, 5 Dec 2008 09:34:45 -0500 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id mB5EZIQk179902; Fri, 5 Dec 2008 09:35:18 -0500 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id mB5EZHtM021930; Fri, 5 Dec 2008 09:35:17 -0500 Received: from cichlid.raleigh.ibm.com (sig-9-65-205-212.mts.ibm.com [9.65.205.212]) by d01av03.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id mB5EZGHu021895 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Dec 2008 09:35:17 -0500 Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.2/8.12.5) with ESMTP id mB5EZFNp007644; Fri, 5 Dec 2008 09:35:15 -0500 Message-Id: <200812051435.mB5EZFNp007644 at cichlid.raleigh.ibm.com> To: Keith Moore <moore at network-heretics.com> Subject: Re: The internet architecture In-reply-to: <49384BCF.2080600 at network-heretics.com> References: <C15AE32B-E564-4C93-86FF-40EF203E673A at mpi-sws.org> <49382030.5020704 at network-heretics.com> <2788466ED3E31C418E9ACC5C316615572FFBEF at mou1wnexmb09.vcorp.ad.vrsn.com> <49384BCF.2080600 at network-heretics.com> Comments: In-reply-to Keith Moore <moore at network-heretics.com> message dated "Thu, 04 Dec 2008 16:29:51 -0500." Date: Fri, 05 Dec 2008 09:35:15 -0500 From: Thomas Narten <narten at us.ibm.com> Cc: tae at ietf.org, ietf at ietf.org, Bryan Ford <brynosaurus at gmail.com> X-BeenThere: ietf at 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 at ietf.org?subject=unsubscribe> List-Post: <mailto:ietf at ietf.org> List-Help: <mailto:ietf-request at ietf.org?subject=help> List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request at ietf.org?subject=subscribe> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ietf-bounces at ietf.org Errors-To: ietf-bounces at ietf.org Keith Moore <moore at network-heretics.com> writes: > So it's not a question of whether DNS is less reliable than IP (it is), > or even whether the reliability of DNS + IP is less than that of IP > alone (it is). It's a question of whether increasing reliance on DNS by > trying to get apps and other things to use DNS names exclusively, makes > those apps and other things less reliable. No. Your argument seems to be "because relying even more on DNS than we do today makes things more brittle, BAD, BAD BAD, we cannot go there." The more relevant engineering question is whether the benefits of such an approach outweigh the downsides. Sure there are downsides. But there are also real potential benefits. Some of them potentially game chagame changers in terms of addressing real deficiencies in what we have today. It may well be that having applications be more brittle would be an acceptable cost for getting a viable multihoming approach that address the route scalability problem. (All depends on what "more brittle" really means.) But the only way to answer such questions in a productive manner is to look pretty closely at a complete architecture/solution together with experience from real implementation/usage. Thomas _______________________________________________ Ietf mailing list Ietf at ietf.org https://www.ietf.org/mailman/listinfo/ietf ngers in terms of addressing real deficiencies in what we have today. It may well be that having applications be more brittle would be an acceptable cost for getting a viable multihoming approach that address the route scalability problem. (All depends on what "more brittle" really means.) But the only way to answer such questions in a productive manner is to look pretty closely at a complete architecture/solution together with experience from real implementation/usage. Thomas _______________________________________________ Ietf mailing list Ietf at ietf.org https://www.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.