> On Tue, 11 Dec 2007, Ned Freed wrote: > > > > So keep the MUST for aliases but lose it for lists? I could live with that > > too but it would probably force a recycle. > I thought that removing requirements is OK during document progression. Removing capabilities and features is fine - encouraged even. This is removing a restriction, which could be seen as adding any number of capabilities. That's arguably not OK, although the determination is of course up to the IESG. Ned _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf