Ok cool. My suggestion is going to be that we setup a Special Interest Group (SIG) around the
packet.com work. This SIG would exist for a short time and we would funnel all the related
packet.com work through it for the time being, at least in term of what resources are being used and how. Then, once we felt everything was well understood in terms of how we organize and use the
packet.com infrastructure we would disband it and work would continue as normal in the teams that are using the infrastructure. I'll mention this at the community and TSC meetings this week.