IETF Logo Mail Archive

Re: Domain Centric Administration, RE: draft-ietf-v6ops-natpt-to-historic-00.txt

Keith Moore <moore@cs.utk.edu> Tue, 03 July 2007 15:52 UTC

Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5kfz-0005Hr-Kc; Tue, 03 Jul 2007 11:52:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5kfx-0005HG-BB for ietf@ietf.org; Tue, 03 Jul 2007 11:52:25 -0400
Received: from shu.cs.utk.edu ([160.36.56.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5kf1-0001QS-Jv for ietf@ietf.org; Tue, 03 Jul 2007 11:52:25 -0400
Received: from localhost (localhost [127.0.0.1]) by shu.cs.utk.edu (Postfix) with ESMTP id BC0D81EE1EF; Tue, 3 Jul 2007 11:51:26 -0400 (EDT)
X-Virus-Scanned: by amavisd-new with ClamAV and SpamAssasin at cs.utk.edu
Received: from shu.cs.utk.edu ([127.0.0.1]) by localhost (bes.cs.utk.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kmPnPEMrNG2p; Tue, 3 Jul 2007 11:51:26 -0400 (EDT)
Received: from lust.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182]) by shu.cs.utk.edu (Postfix) with ESMTP id 879AC1EE1DB; Tue, 3 Jul 2007 11:51:25 -0400 (EDT)
Message-ID: <468A707D.3090200@cs.utk.edu>
Date: Tue, 03 Jul 2007 11:51:25 -0400
From: Keith Moore <moore@cs.utk.edu>
User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604)
MIME-Version: 1.0
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
References: <198A730C2044DE4A96749D13E167AD37012F692F@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012F692F@MOU1WNEXMB04.vcorp.ad.vrsn.com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=E1473978
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: Melinda Shore <mshore@cisco.com>, Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org
Subject: Re: Domain Centric Administration, RE: draft-ietf-v6ops-natpt-to-historic-00.txt
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

> If the application layer is required to take notice of what is going on at the lower levels its because the layering was botched.
>   
no, it just means that all lower-level network services weren't designed
to provide exactly the same set of services and semantics to higher
layers. 

in the IP stack, we expect link layers to be diverse, we expect IP
service to be fairly uniform, precisely so that things layered on top of
IP don't have to worry about it.  expecting all applications to support
multiple transport protocols adds complexity where it is almost never
needed.


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email