RE: warning suggestions for draft-bberry-pppoe-credit
"Stan Ratliff \(sratliff\)" <[email protected]>
| Newsgroups | gmane.ietf.pppext |
|---|---|
| Message-ID | <7FB7EE0A621BA44B8B69E5F0A09DC76401170791@xmb-rtp-208.amer.cisco.com> |
James/All -- When viewed in the context of 802.11 radios, I would agree that the applicability of this draft is suspect. However, when viewed in the context of TDMA radios, that point-to-point characteristics, this RFC does seem applicable. It allows the radio vendors to do what they do best, and at the same time, allows router vendors to do the same. Propagation of the P2P characteristics of TDMA links back into the router allows the router to allocate QoS queues on a radio link-by-radio link basis, giving good granularity and control. So, at the worst, I would like to see some text in the draft that states the applicability to TDMA-like radios, as opposed to what you have here. Regards, Stan >-----Original Message----- >From: [email protected] [mailto:[email protected]] >On Behalf Of James Carlson >Sent: Thursday, December 08, 2005 10:27 AM >To: [email protected] >Subject: [Pppext] warning suggestions for draft-bberry-pppoe-credit > >Our AD has asked for some suggested warning text that can be added to >this draft, as the author has asked for it to be published as an >Informational RFC. (Please -- no matter which side of this divide >you're on -- direct your flames to /dev/null. Yes, I and the rest of >the folks here know all of the arguments on both sides. We don't need >to go over the issues again.) > >Here's my suggestion. Feel free to suggest better wording. > > "The PPP Extensions Working Group (pppext) has reservations about > the desirability of the feature described in this document. In > particular, it solves a general problem at an inappropriate layer > and it may have unpredictable interactions with higher and lower > level protocols. The consensus of the working group is that > implementors would be better advised either to seek ways of making > the underlying radio link suitable for general Ethernet-like use, or > to abandon the incomplete emulation of Ethernet entirely." > >-- >James Carlson, KISS Network ><[email protected]> >Sun Microsystems / 1 Network Drive 71.232W Vox +1 >781 442 2084 >MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 >781 442 1677 > >_______________________________________________ >Pppext mailing list >[email protected] >https://www1.ietf.org/mailman/listinfo/pppext > _______________________________________________ Pppext mailing list [email protected] https://www1.ietf.org/mailman/listinfo/pppext