resolution_overtaken by events type_cleanup | by fenner@research.att.com
The use of a seperate table for irtf groups means that not only is the lookup complicated, some functionality is missing - e.g., if we want to track the irtf rg of an I-D, we could with an acronym in the group_acronym field, except we can't since they're in a different space. If we want to express conflicts with irtf rg's, we could with the acronym ID, except we can't since they're in a different space.
I don't see any win from using the seperate ID for the irtf acronym, and several disadvantages.
Issue migrated from trac:71 at 2022-03-04 00:35:40 +0000
resolution_overtaken by eventstype_cleanup| by fenner@research.att.comThe use of a seperate table for irtf groups means that not only is the lookup complicated, some functionality is missing - e.g., if we want to track the irtf rg of an I-D, we could with an acronym in the group_acronym field, except we can't since they're in a different space. If we want to express conflicts with irtf rg's, we could with the acronym ID, except we can't since they're in a different space.
I don't see any win from using the seperate ID for the irtf acronym, and several disadvantages.
Issue migrated from trac:71 at 2022-03-04 00:35:40 +0000