IETF Logo Mail Archive

Re: [RAM] Crisper Terminology

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 09 June 2007 06:42 UTC

Return-path: <ram-bounces@iab.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hwuee-0008VN-BV; Sat, 09 Jun 2007 02:42:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hwueb-0008Nd-Fc for ram@iab.org; Sat, 09 Jun 2007 02:42:30 -0400
Received: from ug-out-1314.google.com ([66.249.92.169]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwueZ-0004ED-6p for ram@iab.org; Sat, 09 Jun 2007 02:42:28 -0400
Received: by ug-out-1314.google.com with SMTP id m2so1197305uge for <ram@iab.org>; Fri, 08 Jun 2007 23:42:26 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=QZRDXwVLWfVdixZr8MhcCac928E0dFWc5GBV6tlRs0LxLU4FFlAtv6tm1sYeeNcWLkIGjtnDRM/ogOQgNQby3Q9Gk08VaV6bLDGfH+mdcE1S0ZTUkHF5Fk9wZ3TC+OPxaeXvsX584majkUO7fmc6firecjSjaLwgWfnlZ4xbeVg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=ovZz0luyctlYpT1oQ2UTGOcRar2+XODPJB/eTylsk5nYKFzvIcStF/1w0Fk/L/BEELNmT1AqJzCuJTcvOUazuIs8refBQifkqNTPGpQGkyfsrdZI2yemQ5tnx2MkUCDKvgkrXKR0BCa78l/TD3CaegqoEIpEv908+VRc8LRuOPk=
Received: by 10.66.249.8 with SMTP id w8mr2528311ugh.1181371346349; Fri, 08 Jun 2007 23:42:26 -0700 (PDT)
Received: from ?192.168.1.101? ( [213.103.155.32]) by mx.google.com with ESMTP id w40sm2353521ugc.2007.06.08.23.42.23 (version=SSLv3 cipher=RC4-MD5); Fri, 08 Jun 2007 23:42:23 -0700 (PDT)
Message-ID: <466A4BCE.4010208@gmail.com>
Date: Sat, 09 Jun 2007 08:42:22 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: RJ Atkinson <rja@extremenetworks.com>
Subject: Re: [RAM] Crisper Terminology
References: <20070608162021.1266686AF0@mercury.lcs.mit.edu> <1061608D-5E5D-45E9-965C-9E66B4C41E95@extremenetworks.com>
In-Reply-To: <1061608D-5E5D-45E9-965C-9E66B4C41E95@extremenetworks.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: ram@iab.org
X-BeenThere: ram@iab.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing and Addressing Mailing List <ram.iab.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ram>
List-Post: <mailto:ram@iab.org>
List-Help: <mailto:ram-request@iab.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=subscribe>
Errors-To: ram-bounces@iab.org

On 2007-06-08 19:25, RJ Atkinson wrote:
...
> There is a perfectly good a name for objects with both identification
> and location semantics.  This community generally calls them addresses.

I'd be tempted to agree with that, but I just had occasion to
review draft-ietf-ccamp-gmpls-addressing-07.txt, and found my head
spinning rapidly on exactly this question.

> For example, the existing TCP implementations use an IP address
> as the endpoint name for TCP purposes.

Well, if we use OSI formalism, we'd have to say that the transport
address is the network address concatenated with the port number.
There was a fairly clear model for layered endpoint addressing in
OSI, and it still a valid thinking aid IMHO.

     Brian

_______________________________________________
RAM mailing list
RAM@iab.org
https://www1.ietf.org/mailman/listinfo/ram

v2.23.0 | Report a Bug | By Email