For the record, the changes you describe address all of my concerns. Thanks,
Ben. On Mar 28, 2008, at 7:34 PM, Barry Leiba wrote: > (Removed [EMAIL PROTECTED]) > > Thanks, Ben, for the review. > >> "URI headers with hname >> "received" are considered unsafe, and will be ignored." >> >> Was that intended to be MUST be ignored? > > Yes; I missed that one in a recent change from non-2119 language to > 2119 language. I think I can fix that in AUTH48, unless there's a > reason to put out another rev of the draft. > >> IDNITS reports that draft-ietf-sieve-variables has been published >> as RFC 5229. >> Also, the [Notify] reference describes a very outdated version of >> that draft > > Thanks; both of those will be fixed by the RFC Editor, so it won't > matter. But I'll run through the references during AUTH48, and make > sure it all looks OK. > >> Although one can get away with this when the noun in question is the >> document being referenced, as in "...notations are as in [Sieve] >> section 1.1 >> ...", I find it visually disruptive to read "The [Notify] extension >> to the >> [Sieve] mail filtering language...". My brain keeps stopping to >> wonder what is >> with all the square brackets--it is not immediately clear from >> context that the >> brackets are there to denote references. > > Yes, it's s style thing here. Thanks for questioning it, but I > think I'll leave it. I find this sort of thing even more > disruptive: "The Notify extension [Notify] to the Sieve mail > filtering language [Sieve]..." But, of course, it's all personal > preference. > > Barry > _______________________________________________ Gen-art mailing list [email protected] https://www.ietf.org/mailman/listinfo/gen-art
