Hi.
--On Wednesday, July 20, 2011 11:43 -0700 S Moonesamy
<[email protected]> wrote:
> Hi John,
> At 09:35 AM 7/20/2011, John C Klensin wrote:
>> I believe that I have already responded to that note at least
>> once. A newly-constructed summary of the three issues listed
>> in that note follows:
>>
>> (1) "SHOULD for RFC 6186". Such a normative requirement would
>...
> After reading the YAM Charter and the WGLC comments, my advice
> is no action on this.
Ok. From the above and as far as I know, the only two changes
needed for -01 are:
* The text about "aliases" discussed earlier. The real
issue is exactly what RFC 5321 prohibits when it
prohibits the use of aliases. IMO, that problem needs
to be addressed there, not in 4409bis. But, modulo that
concern, the text is, IMO, now clear about what
Submission servers are expected/ permitted to do.
* A few small typographical errors, mostly resulting
from the 4409-> 4409bis conversion, that were not caught
earlier.
Unless you identify something else, I will get -01 posted as
soon after the posting window reopens Monday as I can manage. I
believe the specification is then ready for IETF Last Call.
john
_______________________________________________
yam mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/yam
