[RAM] Re: revised draft proposed definitions

Stephane Bortzmeyer <bortzmeyer@nic.fr> Tue, 12 June 2007 13:44 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 1Hy6fq-0003z7-0U; Tue, 12 Jun 2007 09:44:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy6fp-0003yz-8l for ram@iab.org; Tue, 12 Jun 2007 09:44:41 -0400
Received: from mx2.nic.fr ([192.134.4.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hy6fn-0004EJ-Vm for ram@iab.org; Tue, 12 Jun 2007 09:44:41 -0400
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id E03A21C0107; Tue, 12 Jun 2007 15:44:37 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx2.nic.fr (Postfix) with ESMTP id DAB221C0103; Tue, 12 Jun 2007 15:44:35 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.4.69]) by relay2.nic.fr (Postfix) with ESMTP id D743B58EBE7; Tue, 12 Jun 2007 15:44:35 +0200 (CEST)
Date: Tue, 12 Jun 2007 15:44:35 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Scott W Brim <swb@employees.org>
Message-ID: <20070612134435.GA27174@nic.fr>
References: <808E6500-97B4-4107-8A2F-36BC913BE196@extremenetworks.com> <20070611203028.GA13021@sources.org> <466E989E.6050704@employees.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <466E989E.6050704@employees.org>
X-Operating-System: Debian GNU/Linux 4.0
X-Kernel: Linux 2.6.18-4-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: RJ Atkinson <rja@extremenetworks.com>, 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 Tue, Jun 12, 2007 at 08:59:10AM -0400,
 Scott W Brim <swb@employees.org> wrote 
 a message of 31 lines which said:

> > I was not able to find an example of a global locator, in the
> > current IETF standards. Does anyone have an existing example?
> 
> If your objection is because of NAT, 

No, it is independant of NAT. I said that, currently, it seems that
global "pure" locators (those that are never used for identification)
do not exist in the IETF world. (And, even outside of the IETF realm,
I have trouble naming even one. Street addresses? Longitude/latitude
coordinates for your favorite ICBM?)

> > A MPLS label is a scoped locator. Am I right?
> 
> Connection-oriented packet switching is a very different sort of
> beast.  I think we should restrict this discussion to
> connectionless.

You define MPLS as connection-oriented? This surprises me.

> >> 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?
> 
> Yes, HITs are identifiers (not identities :-p)

The question is not about HITs but about HIP (the protocol). Under the
above definition, is HIP a good example of a "Identifier/Locator
split"? (I would say yes.)

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