On 19/03/2018 23:46, Russ Housley wrote: > We hoping to add a replaced-by feature to the datatracker to help people track these name changes. The tools team is looking for a volunteer to write the code... That would be good. There are often good reasons for a name change between BOF and WG; IPDECIDE became IPNGWG became IPV6 became 6MAN. Brian > > Russ > > >> On Mar 19, 2018, at 6:07 AM, Michael Richardson <mcr+ietf@xxxxxxxxxxxx> wrote: >> >> >> I was looking for the ANIMA, IETF-90 (Toronto) slides. >> IETF91 was the earliest... aha, it was a BOF in Toronto... and finally >> I realized it was called UCAN when it was a BOF. >> >> Is there some reason why we do not keep the same database entry >> so that BOF materials that lead to a WG can be seen on the materials >> and agenda page for the WG? >> >> If there is some reason the same entry is not kept, is there some pointer on >> the WG status page that points to the BOF that I've missed? >> >> -- >> ] Never tell me the odds! | ipv6 mesh networks [ >> ] Michael Richardson, Sandelman Software Works | network architect [ >> ] mcr@xxxxxxxxxxxx http://www.sandelman.ca/ | ruby on rails [ >
