On Sat, Apr 4, 2009 at 11:50 AM, Noel Chiappa <[email protected]> wrote: > > From: William Herrin <[email protected]> > > > Address: Any element in a network packet used to calculate the packet's > > next hop. > > That would make an MPLS tag an "address". Somehow I don't think so.
Why not? What characteristics of what you think of as an address are missing from the typical use of an MPLS tag? > (Not to > mention the TOS field, if anyone is still using TOS-dependent routing.) Was TOS ever used in the dynamic part of a routing protocol? If TOS is used in the forwarding decision within a particular scope then it is part of an address within that scope. If that scope happens to be a static route on a single piece of equipment (or a static nudge to a dynamic route) then it's well outside the RRG's area of interest. The same goes for Linux Virtual Server (LVS) which routes packets based on the TCP transport ID. The TCP transport ID is an address within that scope, but the scope is limited to a single server cluster. > If we really need a name for some particular crisp definition (such as the > one above), pick a new word/phrase, don't try and morph an existing word. If the chair is amenable to that idea, so am I. At the moment I'm endeavoring to remove the fuzz from the existing terms as the chair requested. Regards, Bill Herrin -- William D. Herrin ................ [email protected] [email protected] 3005 Crane Dr. ...................... Web: <http://bill.herrin.us/> Falls Church, VA 22042-3004 _______________________________________________ rrg mailing list [email protected] http://www.irtf.org/mailman/listinfo/rrg
