Re: [RAM] revised draft proposed definitions
Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 12 June 2007 08:38 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 1Hy1tN-0007HJ-FF; Tue, 12 Jun 2007 04:38:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy1tM-0007HA-9y for ram@iab.org; Tue, 12 Jun 2007 04:38:20 -0400
Received: from ug-out-1314.google.com ([66.249.92.173]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hy1tL-0001q6-Tg for ram@iab.org; Tue, 12 Jun 2007 04:38:20 -0400
Received: by ug-out-1314.google.com with SMTP id m2so118668uge for <ram@iab.org>; Tue, 12 Jun 2007 01:38:19 -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=Hezz4Q6vqRRzfHYts3fkl4qJ7ihYe5lMKXPauImTDhPF/BURi1dgSdH1QAQY7IK0v7R2cNuPiJqjYRbhhfNJoFqX09J81nOfbhxwoQksxjQSBEVCWBohbpjl2v6w9zWmdNnQKg8r18h/yxILx45gdxCj98rNmj9nWx+c/4zOzX8=
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=X2d52ydDoL/ANQmL/E+2x0HFqbxQDdeyGLC/1KmjS3szPyGOe6kKKOcvT1yHft0LJT22RCdZ/wL3TAcHddFXT7EuEJXzHO3+dfWKqsGpeZUVTNe44zG0sfCFGyPkpVCsnjPkITxk5w9n5Kqkw8qQ01eauaVYFa5TTnezq5zRBRY=
Received: by 10.82.178.11 with SMTP id a11mr12750993buf.1181637499059; Tue, 12 Jun 2007 01:38:19 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1]) by mx.google.com with ESMTP id h7sm688863nfh.2007.06.12.01.38.18 (version=SSLv3 cipher=RC4-MD5); Tue, 12 Jun 2007 01:38:18 -0700 (PDT)
Message-ID: <466E5B78.4090501@gmail.com>
Date: Tue, 12 Jun 2007 10:38:16 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Tony Li <tli@cisco.com>
Subject: Re: [RAM] revised draft proposed definitions
References: <808E6500-97B4-4107-8A2F-36BC913BE196@extremenetworks.com> <466D69FC.3010003@cisco.com> <715690CE-8527-4123-9A09-101FC7EDF5EC@cisco.com>
In-Reply-To: <715690CE-8527-4123-9A09-101FC7EDF5EC@cisco.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: RJ Atkinson <rja@extremenetworks.com>, 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-11 22:05, Tony Li wrote: ... > That still fails the test of describing what things are. What we want > is to take a constructive approach: > > An identifier is an element of a namespace. There is a 1:1 mapping > between the namespace and the entities being enumerated. > > >>> Locator: An object that is used only for forwarding packets >>> or determining location, never for identification. >> >> Same comment only in reverse ;-) "A locator denotes presence at a >> specific point in the network. When one's location within a network >> changes, one locator changes". > > > Ok, but a locator does NOT denote reachability. Thus, a locator is a > string of bits that indicates a topological location. It seems relevant to paste in the definitions I use in draft-carpenter-idloc-map-cons. I strongly agree with Tony that we must relate the notion of ID to a specific namespace. We may differ slightly on Loc: Locator: A binary quantity (not necessarily an IP Address) that can be used by a routing or forwarding device to decide where to send a packet. Identifier: A binary quantity (not necessarily an IP Address) that can be used by a Stack "A" to uniquely identify another Stack "B" both for bilateral communication and for informing a third Stack "C" that it should communicate with Stack "B". (Note that there is an assumption in this definition that a Stack is the entity we require to identify; in this era of virtualized servers with failover capabilities, and of mobile clients, this seems to be a reasonable assumption.) Namespace: a set of natural numbers, each of which is referred to as a name. Since it is a set, by definition each name is unique and thus the namespace is unambiguous. Locators and Identifiers must belong to specific namespaces. Namespace Context: the context within which a given namespace retains its uniqueness property. (For example, the Namespace Context of the Namespace created by [RFC1918] is a single Internet site.) Brian _______________________________________________ RAM mailing list RAM@iab.org https://www1.ietf.org/mailman/listinfo/ram
- [RAM] revised draft proposed definitions RJ Atkinson
- Re: [RAM] revised draft proposed definitions Eliot Lear
- Re: [RAM] revised draft proposed definitions Tony Li
- [RAM] Re: revised draft proposed definitions Stephane Bortzmeyer
- Re: [RAM] revised draft proposed definitions HeinerHummel
- Re: [RAM] Re: revised draft proposed definitions Brian E Carpenter
- Re: [RAM] revised draft proposed definitions Brian E Carpenter
- Re: [RAM] revised draft proposed definitions Russ White
- Re: [RAM] revised draft proposed definitions RJ Atkinson
- Re: [RAM] revised draft proposed definitions JFC Morfin
- Re: [RAM] Re: revised draft proposed definitions Scott W Brim
- Re: [RAM] revised draft proposed definitions Russ White
- [RAM] Re: revised draft proposed definitions Stephane Bortzmeyer
- Re: [RAM] revised draft proposed definitions Noel Chiappa
- Re: [RAM] revised draft proposed definitions Russ White
- Re: [RAM] revised draft proposed definitions Tony Li
- Re: [RAM] revised draft proposed definitions Michael