Scott,
On 2009-02-22 10:16, Scott Brim wrote: > Excerpts from Brian E Carpenter on Wed, Feb 18, 2009 01:58:26PM +1300: ... > Whether a given identifier is considered to be a name or an > address is dependent on several factors including the perspective > (and location) of the entity that is using (or mapping to) that > identifier. The same identifier can be considered an address to > one entity and a name to a different entity because their > perspective is different. Absolutely true. ... >>> 3.1.2. Translation >> Reading further, it occurred to me that this really should >> be called Map & Translate > > I don't see why. Suppose I'm doing GSE. I have a simple algorithm > for swapping the upper bits of an address field, and the algorithm is > always the same. Is that really mapping? I don't know of any > proposals that do actual mapping and then translating. I agree that in most cases the mapping is algorithmic or trivial. But if you classify shim6 here, it's actually building a small map for each ULID (~=EID) that it handles. ... >> (NAT is just swapping RLOC and EID, for example, but NAPT is >> munging EIDs together before doing the swap.) > > I don't know what you mean, munging EIDs together. Do you mean > that it uses pieces from different headers? No, I mean that it folds many EIDs into one RLOC, using the port numbers to demultiplex. Brian _______________________________________________ rrg mailing list [email protected] http://www.irtf.org/mailman/listinfo/rrg
