Starting my replies with this thread ... Dow Street allegedly wrote on 04 09 2009 3:07 AM: > At the risk of making things even more confused...it seems we have at > least the following things that we are trying to talk about: > > 1. landscape - an object or system with a notion of distance > > 2. a point on a landscape > > 3. a name for a point on a landscape > > 4. an object that is attached to a point on the landscape > > 5. a name for an object that is attached to a point on a landscape > > 6. a map of a landscape describing which points are named what > > 7. a name for a section of a landscape (i.e., a collection of points on > a landscape)
I like this list. It is a superset of the one I sent out. However, in addition, you need a name for "a thing that forwarding uses", for example Noel's forwarding selector: a "field in the packets which the routers look at to decide where to send the packet next". Something can "name a location" (i.e. point of attachment) but not be present in the packet as the packet crosses the Internet. Even if it is present a forwarder might not use it in deciding how to forward the packet. I think we can all agree now that the term 'locator' is terribly confusing. A sensor senses, a resistor resists ... but a 'locator' does not locate, rather it is a name that may or may not be used by a function that actually does locate. But we're stuck with it. Now let's be sure to limit how 'locator' is used so that it is actually useful. It names an attachment point (not an endpoint). _______________________________________________ rrg mailing list [email protected] http://www.irtf.org/mailman/listinfo/rrg
