IETF Logo Mail Archive

Re: [RAM] Re: Ramblings about "locator"

Tony Li <tli@cisco.com> Thu, 14 June 2007 20:47 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 1HywE2-0002Cf-Am; Thu, 14 Jun 2007 16:47:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HywE0-0002Ca-KJ for ram@iab.org; Thu, 14 Jun 2007 16:47:24 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HywDy-0006wU-9q for ram@iab.org; Thu, 14 Jun 2007 16:47:24 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-3.cisco.com with ESMTP; 14 Jun 2007 13:47:22 -0700
X-IronPort-AV: i="4.16,422,1175497200"; d="scan'208"; a="494288505:sNHT46196626"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5EKlLVo017471; Thu, 14 Jun 2007 13:47:21 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l5EKlDaI020678; Thu, 14 Jun 2007 20:47:13 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); Thu, 14 Jun 2007 13:47:13 -0700
Received: from [171.71.55.99] ([171.71.55.99]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 14 Jun 2007 13:47:13 -0700
In-Reply-To: <8A7E8D43-1C74-4466-A6ED-124D47043B05@extremenetworks.com>
References: <20070614193023.A2F2387361@mercury.lcs.mit.edu> <8A7E8D43-1C74-4466-A6ED-124D47043B05@extremenetworks.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <35B81F87-1B77-47B6-8155-F188AF612AA3@cisco.com>
Content-Transfer-Encoding: 7bit
From: Tony Li <tli@cisco.com>
Subject: Re: [RAM] Re: Ramblings about "locator"
Date: Thu, 14 Jun 2007 13:47:11 -0700
To: RJ Atkinson <rja@extremenetworks.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 14 Jun 2007 20:47:13.0035 (UTC) FILETIME=[2F65F5B0:01C7AEC5]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=815; t=1181854041; x=1182718041; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=tli@cisco.com; z=From:=20Tony=20Li=20<tli@cisco.com> |Subject:=20Re=3A=20[RAM]=20Re=3A=20Ramblings=20about=20=22locator=22 |Sender:=20; bh=HSpSEPqv8tCitq8Eyhfbw6kMVzS81Y/rt/jheuj2yvM=; b=ZzzXKOH9mWDntsuz4F+EX/Cwv9pDjVirktchzcjUq6CupYwCZnJvpRFc2LnVUlLC55TVvR7/ mLW/5ASatZCi6lDBR40Rk4/Nr0hek2NPnmj9A2lk0HdoeXoQECXQv5u+jU2bP4xrAqCw99IEIG ecy6wMzX/2hEfSAptccpbMgoY=;
Authentication-Results: sj-dkim-1; header.From=tli@cisco.com; dkim=pass (sig from cisco.com/sjdkim1004 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, 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 Jun 14, 2007, at 1:30 PM, RJ Atkinson wrote:

> 	You were the person who persuaded me, after some
> resistance on my part, that since the IEEE MAC address
> is used in a lookup table (either a bridge table or an
> IPv6 ND table) to forward the frame/packet, therefore
> the MAC address must have location semantics and so
> could not be a pure Identifier.


If we consider forwarding functionality to be the definition of a  
locator, then we are going to have a very serious issue.  Consider  
other forwarding mechanisms that let you take into account source  
address, port number, protocol number, DSCP, etc. as part of the  
forwarding decision.  If we follow that logic, the phase of the moon  
could also be a locator.  Is that what we want?

I prefer Joel's line of thinking.

Tony



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

v2.23.0 | Report a Bug | By Email