> And we've always stated that if that happens, at that point the document > should be removed from YAM's initial charter. Work on it can continue "off > the charts" as individual work or be postponed until after the initial YAM > charter is finished, but the YAM WG won't be spending its cycles on it > during the initial charter time period. The difference is that I'm saying that dealing with things like security considerations should NOT kick the document off the charter... at least not immediately. I think it's reasonable that we might get to a point in reviewing and adding/updating security considerations, where we think it's time to kick the document off. But I don't think it should happen just because we need to contemplate adding a security considerations section. Barry
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.