Thanks for catching these errors. I'll change the musts to should. Consistency is hard.
Stephen > -----Original Message----- > From: Paul Hoffman [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 25, 2006 10:22 AM > To: Stephen Hayes (TX/EUS); [email protected] > Subject: RE: [Techspec] Post-edit tracking > > > At 11:41 PM -0500 5/24/06, Stephen Hayes (TX/EUS) wrote: > >All the requirements use the "should" language. It is hard to > >actually mandate anything since what the publisher will do is > >ultimately determined by the contract. > > Some of the requirements still say "must". It's fine to demote them, > but if you don't, this one should be promoted to "must". > > o Req-POSTEDIT-2 - All changes made to post-approval documents > should be tracked and the changes must be signed off on by the > appropriate technical representatives as defined in the IETF > processes. > > o Req-INDEX-3 - Meta information associated with a published > document must be stored and updated as its status changes. > > o Req-INDEX-4 - The archive must be sufficiently secure > to prevent > the modification of published documents by external parties. > > > --Paul Hoffman, Director > --VPN Consortium > _______________________________________________ Techspec mailing list [email protected] https://www1.ietf.org/mailman/listinfo/techspec
