RE: draft-ietf-rmt-bb-fec-raptor-object-02 WG Last Call
"Michael Luby" <[email protected]>
| Newsgroups | gmane.ietf.rmt |
|---|---|
| Message-ID | <200510111513.j9BFD4sC020070@mail> |
Hello Vincent, A reply to your comments below (paragraph that starts with ***). Mike -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Vincent Roca Sent: Tuesday, October 11, 2005 7:18 AM To: [email protected] Cc: Ramakrishna Vedantham; [email protected] Subject: Re: [Rmt] draft-ietf-rmt-bb-fec-raptor-object-02 WG Last Call Hello Mark and al. > I'm reluctant to add significant amounts of new material > at this stage since the draft has been stable for some time > now. Several people have implemented the code from this > specification, so I don't think there is any question that > t is not clear enough to be easily implementable. Also, as a > general rule, tutorial material should be kept separate from > specifications, so perhaps if there is a need for such material > it should be somewhere else? The funny thing is that the first two versions of the I-D used to include many more explanations than the latest one, and understanding the motivations was probably simpler. Then some tables and explanations progressively disappeared from newest versions of the Raptor I-D, I don't know why. *** The two latest versions do contain somewhat less prose than the very first versions of the I-D, and the reason for this is that much of the somewhat imprecise and complicated prose was reduced to a few much simpler and exact specification rules for communicating the information. Thus, the prose that was removed was replaced with something that for a specification is preferable, i.e., exact descriptions of what parameters are passed and how to pass them and the result is actually simpler. The recommendations for setting the parameters are still there, and are expanded general recommendations compared to the original version cited below that were described in tables, and the expanded versions match precisely the original version for the cases where the original version were defined. The evolution of the draft into a more precise, succinct and simpler specification occurred due to close scrutiny within the 3GPP SA4 working group. http://www.inrialpes.fr/planete/people/roca/doc/draft-luby-rmt-bb-fec-raptor -object-00.txt http://www.inrialpes.fr/planete/people/roca/doc/draft-ietf-rmt-bb-fec-raptor -object-00.txt Cheers, Vincent _______________________________________________ Rmt mailing list [email protected] https://www1.ietf.org/mailman/listinfo/rmt