Re: [apps-discuss] Feedback on draft-moonesamy-rfc2369bis-01 and draft-moonesamy-rfc2919bis-01

[Alessandro Vesely <[e-mail]>]

Hi SM,
hope you don't mind my taking this occasion to ask some questions.

On 04.01.2012 21:18, S Moonesamy wrote:
> 
> I would appreciate some feedback on draft-moonesamy-rfc2369bis-01

(I'd only s/e-mail/email/ in Section 3.8, per
http://www.rfc-editor.org/rfc-style-guide/terms-online.txt)

> The changes from  RFC 2919 are:
> [...]
> 
>   o  Added a paragraph in the appendix about subject tags

Nice addition.  Would it make sense to promote that from appendix to a new
"Definitions" section?  (I don't dare suggesting that it should match the
list-label...)

Defining what is a /list/ that a List-Id identifies would be another
candidate addition.  And also what is a /nested list/, maybe.  The point is
that it is not clear whether this header field should be used also for
commercial newsletters and similar stuff.

I'm not aware of the deployment of "list-id" as suggested in the paragraph of
Section 5:

   It is suggested, but not required, that List Identifiers be created
   under a subdomain of "list-id" within any given domain.  This can
   help to reduce internal conflicts between the administrators of the
   subdomains of large organizations.  For example, List Identifiers at
   "example.com" are generated in the subdomain of "list-
   id.example.com".

Is it actually used or is it merely an example?

Instead, I found no normative statement that matches the authority on a given
domain that is mentioned in Section 2.  Should there be a SOA under
list-id-namespace?  I wonder whether there is a claim of responsibility
implied in adding List-Id to a bulk message.