Hello,

I would like to have some feedback on draft-moonesamy-rfc2369bis-04, draft-moonesamy-rfc2919bis-04 and draft-moonesamy-list-sequence-header-00.

http://www.ietf.org/internet-drafts/draft-moonesamy-rfc2369bis-04.txt http://www.ietf.org/internet-drafts/draft-moonesamy-rfc2919bis-04.txt http://www.ietf.org/internet-drafts/draft-moonesamy-list-sequence-header-00....

The changes between RFC 2369 and draft-moonesamy-rfc2369bis-04 are:

o  URL changed to URI

o  Replaced MTAs with mailing list managers in the sentence: "MTAs
   generating the header fields SHOULD".

o  Replaced MTAs with mailing list managers in the sentence: "MTAs
   MUST NOT insert whitespace within the brackets" in Section 2

o  In Section 2, client application SHOULD ignore whitespace within
   brackets

o  Updated references

o  Added informative reference to RFC 5064

And between RFC 2919 and draft-moonesamy-rfc2919bis-04 are:

o  Removed text about the domain name system and domain ownership in
   Section 2

o  "localhost" replaced with "invalid"

o  Replaced MTAs with mailing list managers in the sentence: "MTAs
   MUST NOT insert whitespace within the brackets" in Section 3

o  Case independence in Section 6 changed to case insensitivity for
   ASCII

o  Added a paragraph in the appendix about subject tags

o  Updated references

draft-moonesamy-list-sequence-header-00 provides a standard location for identifying the sequence position of an individual message for a mailing list.

Thanks, S. Moonesamy