![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
I don't see where you get that from. I can think of two cases where we might get such an assertion from an AD:
1. The IETF Last Call did generate dissent.
2. The IETF Last Call generated indifference *and* the proposal, whatever it is, clearly has very wide impact. At that point it seems perfectly legitimate to question whether people really know what that have agreed to by their silence. Now, a better way to handle that is for the concerned AD to send explicit mail to the community during the last call - but if that hasn't happened, I don't see anything illegitimate in a DISCUSS asking for additional community review.
However, since the IETF works by consensus, I don't see how we can take an assertion of non-consensus off the list.
Agree.
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.