search

hassanakbar4 / tractive-again

0 stars 0 forks source link

irtf groups should use acronym table too #71

Closed hassanakbar4 closed 3 years ago

hassanakbar4 commented 17 years ago

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 2021-10-29 15:27:23 +0500

hassanakbar4 commented 17 years ago

@henrik@levkowetz.com changed component from ` toBase templates`

hassanakbar4 commented 17 years ago

@henrik@levkowetz.com changed milestone from ` toFixDatabase`

hassanakbar4 commented 17 years ago

@henrik@levkowetz.com removed owner (was ``)

hassanakbar4 commented 11 years ago

@rjsparks@nostrum.com commented

Going out on a limb and marking this obe

hassanakbar4 commented 11 years ago

@rjsparks@nostrum.com changed status from new to closed

hassanakbar4 commented 11 years ago

@rjsparks@nostrum.com changed resolution from ` toovertaken by events`

hassanakbar4 commented 11 years ago

@rjsparks@nostrum.com edited the issue description