Q: Should we put all the assigned numbers and names in this page or have a child page (with known URL) for each category? - A: There aren't many, so let's put them all here for now. We can define permalinks, e.g. for DHCP sub-options, that all point here for now and could move later.
Q: How should we reference WTs and TRs? - A: TR-xxx implies Issue 1 and the latest Amendment / Corrigendum unless otherwise stated (causes a problem for TR-124 etc that use Issues for what should be Amendments).
Q: Should we mention deprecated TRs at all, e.g. TR-064, TR-133, TR-098, TR-181 Issue 1? Q: This will be a public page. Should we include WTs? - A: Yes. No sensitive information is likely to leak, and this is easier than maintaining a separate internal list. [Barbara Stark says: Hmm. I'm not sure I agree. But it's not about leakage; it's about the fact the assignment shouldn't be considered assigned until the document is approved.]
Q: Why have you reserved various ranges? - A: To imply that codes will always be assigned to TRs in groups of 10. WT-301i2 is anomalous and might naturally expect instead to use 31-40. [Barbara Stark says: I think this is an extremely wasteful policy. There are only 8 bits in the field which means a max of 256 options. At 10 per TR, we run out after 25 TRs. I would prefer to simply assign sequentially, as needed.]
|