Re: [RAM] Re: revised draft proposed definitions
Scott W Brim <swb@employees.org> Tue, 12 June 2007 12:59 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 1Hy5yV-0007DC-8G; Tue, 12 Jun 2007 08:59:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy5yU-0007D6-On for ram@iab.org; Tue, 12 Jun 2007 08:59:54 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hy5yU-0002C8-Au for ram@iab.org; Tue, 12 Jun 2007 08:59:54 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-1.cisco.com with ESMTP; 12 Jun 2007 05:59:53 -0700
X-IronPort-AV: i="4.16,411,1175497200"; d="scan'208"; a="2651976:sNHT20838426"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5CCxr95032150; Tue, 12 Jun 2007 05:59:53 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5CCxc24004976; Tue, 12 Jun 2007 12:59:49 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 12 Jun 2007 05:59:45 -0700
Received: from [10.21.66.92] ([10.21.66.92]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 12 Jun 2007 05:59:44 -0700
Message-ID: <466E989E.6050704@employees.org>
Date: Tue, 12 Jun 2007 08:59:10 -0400
From: Scott W Brim <swb@employees.org>
Organization: Cisco Systems, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070326 Thunderbird/2.0.0.0 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Subject: Re: [RAM] Re: revised draft proposed definitions
References: <808E6500-97B4-4107-8A2F-36BC913BE196@extremenetworks.com> <20070611203028.GA13021@sources.org>
In-Reply-To: <20070611203028.GA13021@sources.org>
X-Enigmail-Version: 0.95.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Jun 2007 12:59:44.0821 (UTC) FILETIME=[8C88A650:01C7ACF1]
Authentication-Results: sj-dkim-2; header.From=swb@employees.org; dkim=neutral
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
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 06/11/2007 16:30 PM, Stephane Bortzmeyer allegedly wrote: >> 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? If your objection is because of NAT, then I have to agree that you cannot *know* if a locator is global in scope, although things work better if they are. >> 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? Connection-oriented packet switching is a very different sort of beast. I think we should restrict this discussion to connectionless. What a label does is it selects how the packet should be processed next. >> 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) _______________________________________________ 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