Document: draft-motonori-dualstack-smtp-requirement-01.txt
Revieiwer: Mark Allman
Date: 18 August 2004

   
Token: Bert Wijnen


This document needs a editorial pass or two to clean up the writing,
define the acronyms, etc.

I also think this document could be re-written to be much more concise
and to the point.  The goal outlined in the abstract / intro is to call
out some of the gotchas of running SMTP in a world with IPv4 and IPv6
From operational experience.  This sounds like a very nice goal.  But,
most of the document is just outlining the standard steps one would
take.  It seems to me that a simple list of things that one might not
Just Do would be more useful.  Or, to explcitly call out things that
have been operational headaches.  E.g., most of the list in section 3 is
just standard operating procedure.  It's just how things would be done.
There are a few nuggets in there, but I wonder if they are buried too
deeply for anyone to really dig them out of this document.  So, I really
question the value of this i-d progressing.

(That said, I don't think it is dangerous or unsafe or anything like
that ... I just wonder about the usefulness.)

allman