On Tue, Oct 27, 2009 at 2:45 PM, Scott Brim <[email protected]> wrote: > I thought the concepts came out very clear in the end. See our > definitions on the wiki. How to implement identification functions, > e.g. with stack names or what, wasn't resolved, but we know what the > classes of functions are so RRG can model it.
Hi Scott, http://trac.tools.ietf.org/group/irtf/trac/wiki/RRGTerminology I thought they were crap and I wasn't alone. Heck, the locator definition is so vague it barely means anything at all. More to the point, it means virtually anything the reader wants it to mean, regardless of what the writer intended. Do you really want to risk using those terms when more precise words can convey your meaning? >> "layer-4 and higher references to the communicating endpoints are >> strongly bound to the packet elements used for layer-3 forwarding >> decisions, such that practically speaking one can not change >> independent of the other. The pivot point for a solution would be >> weakening that binding until it's no stronger than the binding to the >> packet's layer-2 elements." > Well, "opaque" is a pretty good word for that text :-). For me > identification and function feel clear but I'll ponder this. In return, > please ponder how you're going to deal with confusion about what layer 3 > and layer 4 are. Alright. Does it make things clearer if I rewrite it as: "References to the communicating endpoints found in TCP, UDP and higher layer parts of a given protocol are strongly bound to some packet elements used for IP layer forwarding decisions, such that practically speaking one can not change independent of the other. The pivot point for a solution would be weakening that binding until it's no stronger than the binding between IP or higher layer packet elements and the packet's ethernet or other link-local elements." 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
