>First, a process issue. The header says that this is aimed for the >standards track, and that it updates RFC 4408. The chairs are more >experienced than I in the arcana of IETF process rules, but I think >this is going to be tricky, isn't it?
EAI moved from experimental to standards track without any trouble. So long as there's a reasonable motivation, which there clearly is in this case, I wouldn't expect any more pushback than we usually have with mail security RFCs. R's, John _______________________________________________ marf mailing list [email protected] https://www.ietf.org/mailman/listinfo/marf
