[RAM] Re: revised draft proposed definitions

Stephane Bortzmeyer <bortzmeyer@nic.fr> Mon, 11 June 2007 20:32 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 1HxqYm-0007V6-Oq; Mon, 11 Jun 2007 16:32:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HxqYl-0007Mr-CF for ram@iab.org; Mon, 11 Jun 2007 16:32:19 -0400
Received: from virtual3.netaktiv.com ([80.67.170.53] helo=mail.bortzmeyer.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HxqYk-0004Hv-01 for ram@iab.org; Mon, 11 Jun 2007 16:32:19 -0400
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 8D38C240826; Mon, 11 Jun 2007 22:32:11 +0200 (CEST)
Received: by mail.sources.org (Postfix, from userid 1000) id 871A5106C4; Mon, 11 Jun 2007 22:30:28 +0200 (CEST)
Date: Mon, 11 Jun 2007 22:30:28 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: RJ Atkinson <rja@extremenetworks.com>
Message-ID: <20070611203028.GA13021@sources.org>
References: <808E6500-97B4-4107-8A2F-36BC913BE196@extremenetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <808E6500-97B4-4107-8A2F-36BC913BE196@extremenetworks.com>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 3.1
User-Agent: Mutt/1.5.9i
X-Spam-Score: 0.1 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: ram@iab.org
Subject: [RAM] Re: revised draft proposed definitions
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 Mon, Jun 11, 2007 at 10:13:44AM -0400,
 RJ Atkinson <rja@extremenetworks.com> wrote 
 a message of 110 lines which said:

> 	Here is a revised draft proposal for terminology,

I understand better when there are examples so let me suggest some and
RAM people will tell me if I understood properly or if I'm completely
and hopelessly lost.

> Identifier:	An object that is used only for identification,
> 		never for forwarding packets or determining location.
> 
> 		Identifiers might exist at different protocol layers.
> 		For example, a fully-qualified domain name is one
> 		sort of Identifier. 

OK

> Locator:	An object that is used only for forwarding packets
> 		or determining location, never for identification.

I was not able to find an example of a global locator, in the current
IETF standards. Does anyone have an existing example?

> Scoped Locator:	A locator that has non-global scope.  Note that
> 		a scoped locator only has location semantics,
> 		never identification semantics.

A MPLS label is a scoped locator. Am I right?
 
> Scoped Identifier:  An identifier with non-global scope.  Note that
> 		a scoped identifier only has identity semantics,
> 		never location semantics.

A non-qualified domain name is OK for a scoped identifier? Or a Local
Scope Identifier (LSI) (RFC 4423)?
 
> Identifier/Locator split:	A class of network protocol that
> 		has no addresses, and only has (pure) identifiers
> 		and (pure) locators.  Proposals in the GSE/8+8
> 		class of solution might be examples of this,
> 		depending on the details of the proposal.

HIP too, no?

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