![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
As a more general observation, the whole XML2RFC family of tools seem to have been designed and optimized for producing RFCs. To the extent to which I have complaints personally (and I have few -- I'm generally quite happy with it) it is because, while the RFC Editor produces RFCs, most of us spend most of our time producing and revising I-Ds. It is much better now than it was when the project got started, but, IMO, the places where it comes up short are in tools for working collaboratively, and developing and tracking changes, on a document that is a work in progress rather that one at the last pre-publication stages.
Dave. -- Dave Cridland - mailto:dave at cridland.net - xmpp:dwd at jabber.org - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/ - http://dave.cridland.net/ Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.