dime-0----Page:2
1 2 3
|
Short Summary Current revision: http://www.ietf.org/internet-drafts/draft-ietf-dime-app-design-guide-05.txt Change history since last IETF (Rev 02) Rev 03 Added text explaining which app-id should be used when a command code is being reused Rev 04 Editorial fixes Added recommendation that app writers should clearly specify the use case for optional AVPs that are designed to be piggybacked to existing applications Explain the relaxation of restriction when AVPs with its M-bit set and embedded within a Grouped AVP would cause the Grouped AVP to have its M-bit set Rev 05 Editorial review Clearly state that ABNFs specifying a minimum count of at least one(1) for an optional AVP is illegal; updated to match bis Explained new command code allocation process, specifically the changes to accommodate the new vendor specific command code space Text is now more explicit on the informational status of Vendor-Id Updated description of split-accounting model to fix the case where the Acct-Application-Id is not matching the app-id in the header; updated to match bis Rev 06 (Pending) Added a section on the safe use of the M-bit (when to set it) |