Nico Sabbi wrote:
We could make it an addendum, have the broadcast stuff kept in compatible mode and just first help me converting the current nut in rfc (I don't have much time lately so help IS needed) and start pushing it there.
addendums, extension and spec specializations are the recipe for disaster, whatever direction NUT chooses. A unified NUT spec encompassing *from the very start* everything needed is the only sane way to proceed, IMO
From my experience lots of discussion and some informed input happens once you submit anything to ietf. The way NUT is done adding optional fields and detail them in an appendix wouldn't cause that many issues.
considering that for broadcast we are discussing synchronization hints fields that could be completely disregarded once you have the file stored. lu -- Luca Barbato Gentoo Council Member Gentoo/linux Gentoo/PPC http://dev.gentoo.org/~lu_zero