That seems a rather odd claim. We've been very straightforward in our plans for updating these docs every step of the way, including by suggesting to the WG which ones needed to be updated, calling to adopt their update, asking for volunteers to do so, etc.
Jason
On 10/20/18, 5:27 PM, "iasa20 on behalf of John C Klensin" <iasa20-bounces@xxxxxxxx on behalf of john-ietf@xxxxxxx> wrote:
Frankly, the only good reason I can see for generating all of
these IASA2 documents just to change terminology is to create
enough noise that the community doesn't notice and pay attention
to changes that actually might be controversial. I trust and
assume that is not the intent of anyone involved.
john
_______________________________________________
iasa20 mailing list
iasa20@xxxxxxxx
https://www.ietf.org/mailman/listinfo/iasa20
