Hi.
Per earlier notes, Randy and I have an update to 4409 just about
ready to go. To reprise some comments in those notes, the
revision reflects all of the changes proposed in the (now
expired) pre-evaluation document. It also contains changes that
reflect...
- some additional reference updates
- a few (stupid but inconsequential) changes needed to
make the revision go through the current version of
XML2RFC.
- more proof of the principal that a careful editorial
examination of substantially any document, after one has
not looked at it for a while, will identify text that
could be improved.
There is also some proposed text to insert a clarification into
4409bis about the appropriateness of encoding changes and other
changes that might be useful in an EAI context. My reading of
4409 is that those changes have always been permitted in
Submission Servers but it seemed worthwhile to insert additional
text to avoid any possible confusion and/or attempts at
protocol-lawyering.
The key text is below. I'd appreciate if it the WG would
comment on it (and suggest improvements if needed) before we
post the actual draft (which I hope is otherwise routine).
> 6.5. Adjust Character Encodings
> Subject to limits imposed by other protocols and
> specifications, the MSA MAY convert among character sets or
> string encodings to improve message usefulness, likelihood
> of delivery, or conformance with other specifications or
> recommendations. Such conversions MAY include, when
> necessary, replacement of addresses whose encoding does not
> conform to RFC 5321 with ones that do, using information
> available out to band.
--john
_______________________________________________
yam mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/yam
