Re: [tae] The internet architecture

Keith Moore <moore@network-heretics.com> Fri, 05 December 2008 16:38 UTC

Return-Path: <tae-bounces@ietf.org>
X-Original-To: tae-archive@ietf.org
Delivered-To: ietfarch-tae-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 063DF3A6C94; Fri, 5 Dec 2008 08:38:38 -0800 (PST)
X-Original-To: tae@core3.amsl.com
Delivered-To: tae@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C3EA3A6C91 for <tae@core3.amsl.com>; Fri, 5 Dec 2008 08:38:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.203
X-Spam-Level:
X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[AWL=-0.204, BAYES_00=-2.599, J_CHICKENPOX_93=0.6]
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 vIZORaeGu6Cj for <tae@core3.amsl.com>; Fri, 5 Dec 2008 08:38:35 -0800 (PST)
Received: from m1.imap-partners.net (m1.imap-partners.net [64.13.152.131]) by core3.amsl.com (Postfix) with ESMTP id 763563A6C8B for <tae@ietf.org>; Fri, 5 Dec 2008 08:38:35 -0800 (PST)
Received: from lust.indecency.org (adsl-242-100-137.tys.bellsouth.net [74.242.100.137]) by m1.imap-partners.net (MOS 3.10.3-GA) with ESMTP id BFC34932 (AUTH admin@network-heretics.com) for tae@ietf.org; Fri, 5 Dec 2008 08:38:29 -0800 (PST)
Message-ID: <49395903.3040501@network-heretics.com>
Date: Fri, 05 Dec 2008 11:38:27 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105)
MIME-Version: 1.0
To: Henning Schulzrinne <hgs@cs.columbia.edu>
References: <C15AE32B-E564-4C93-86FF-40EF203E673A@mpi-sws.org> <49382030.5020704@network-heretics.com> <200812051425.mB5EPKEG032766@cichlid.raleigh.ibm.com> <C80424AA-311B-4852-AC9A-152715B53548@cs.columbia.edu>
In-Reply-To: <C80424AA-311B-4852-AC9A-152715B53548@cs.columbia.edu>
Cc: Thomas Narten <narten@us.ibm.com>, tae@ietf.org, IETF discussion list <ietf@ietf.org>
Subject: Re: [tae] The internet architecture
X-BeenThere: tae@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Architecture Evolution <tae.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tae>, <mailto:tae-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tae>
List-Post: <mailto:tae@ietf.org>
List-Help: <mailto:tae-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tae>, <mailto:tae-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tae-bounces@ietf.org
Errors-To: tae-bounces@ietf.org

Henning Schulzrinne wrote:
>>
>>
>> Wouldn't it have been nice if the de facto APIs in use today were more
>> along the lines of ConnectTo(DNS name, service/port).
> 
> This certainly seems to be the way that "modern" APIs are heading. If
> I'm not mistaken, Java, PHP, Perl, Tcl, Python and most other scripting
> languages have a socket-like API that does not expose IP addresses, but
> rather connects directly to DNS names. 

and yet, people wonder why so many network applications are still
written in C, despite all of the security issues associated with weak
typing, explicit memory management, and lack of bounds checking on array
references.

(people also need to realize that using a "modern" API makes it _harder_
to get an application to work well in a mixed IPv4/IPv6 environment.)

> Thus, we're well on
> our way towards the goal of making (some) application oblivious to
> addresses. 

and we're also well on our way towards the goal of having everything run
over HTTP.

> I suspect that one reason for the popularity of these languages is
> exactly that programmers don't want to bother remembering when to
> use ntohs().

probably so.  I can't exactly blame them for that.

Keith

_______________________________________________
tae mailing list
tae@ietf.org
https://www.ietf.org/mailman/listinfo/tae