IETF Logo Mail Archive

Re: [RAM] revised draft proposed definitions

Russ White <riw@cisco.com> Tue, 12 June 2007 10:58 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 1Hy44y-0003ns-5b; Tue, 12 Jun 2007 06:58:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy44x-0003nn-Gi for ram@iab.org; Tue, 12 Jun 2007 06:58:27 -0400
Received: from xmail09.myhosting.com ([168.144.250.252]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hy44w-00086T-7h for ram@iab.org; Tue, 12 Jun 2007 06:58:27 -0400
Received: (qmail 16486 invoked from network); 12 Jun 2007 10:58:25 -0000
Received: from unknown (HELO [192.168.100.205]) (Authenticated-user:_russ@riw.us@[65.190.218.139]) (envelope-sender <riw@cisco.com>) by xmail09.myhosting.com (qmail-ldap-1.03) with ESMTPA for <tli@cisco.com>; 12 Jun 2007 10:58:25 -0000
Message-ID: <466E7C4A.3000002@cisco.com>
Date: Tue, 12 Jun 2007 06:58:18 -0400
From: Russ White <riw@cisco.com>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
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>
X-Enigmail-Version: 0.95.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> Ok, but a locator does NOT denote reachability.  Thus, a locator is a
> string of bits that indicates a topological location.

I think we should, perhaps, leave reachability out? It seems like both a
locator and and id indicate some element of reachability (?). IE, if you
have a locator, and no ID, then there is nothing to reach, but if you
have an id, and no locator, there is no place to reach it at.

I don't see an easy way to separate these two concepts?

:-)

Russ

- --
riw@cisco.com CCIE <>< Grace Alone

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGbnxKER27sUhU9OQRAs2PAJwJbxwsG3EzaXJMnNAnxxmwM6FzQACgpp4v
0Ny5AI4HZXIpi6v0sCupqiM=
=gwoh
-----END PGP SIGNATURE-----

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

v2.23.0 | Report a Bug | By Email