Re: Best list for IETF last calls [was: Weekly posting summary for ietf@ietf.org]

2013-06-08 Thread Glen Zorn
On 06/08/2013 02:52 AM, Brian E Carpenter wrote: Rule 1 for complex and divergent mail threads is to change the Subject header when the subject changes. If you don't do that, your mail is rather likely to get junked. I think that IETF last call threads should stay on the main IETF discussion

RE: Best list for IETF last calls [was: Weekly posting summary for ietf@ietf.org]

2013-06-08 Thread l.wood
I believe that last calls must stay on this ietf list. Any last-call-only list must be *in addition* to the ietf list, with all announcements crossposted, and anyone sensitive to general discussion can subscribe to that instead. Last calls need wide exposure. (I'm acked in at least one RFC as

Re: Weekly posting summary for ietf@ietf.org

2013-06-08 Thread Ray Pelletier
On Jun 7, 2013, at 10:49 AM, Thomas Narten wrote: What the weekly stats really ought to tally up is the readers/postings ratio, so that folk would get more direct feedback as to whether what they are posting is actually being read... My strong suspicion would be that there is strong

Re: Best list for IETF last calls [was: Weekly posting summary for ietf@ietf.org]

2013-06-08 Thread Ray Pelletier
On Jun 8, 2013, at 6:09 AM, l.w...@surrey.ac.uk l.w...@surrey.ac.uk wrote: I believe that last calls must stay on this ietf list. Any last-call-only list must be *in addition* to the ietf list, with all announcements crossposted, and anyone sensitive to general discussion can subscribe

Re: Last Call: draft-ietf-manet-nhdp-sec-threats-03.txt (Security Threats for NHDP) to Informational RFC

2013-06-08 Thread John E Drake
AB, This may surprise you, but not everyone cares what you think. John Sent from my iPhone On Jun 8, 2013, at 1:51 AM, Abdussalam Baryun abdussalambar...@gmail.com wrote: Dear Routing Area AD, I had many comments/issues regarding your area always addressed to you and including this

ietf@ietf.org is a failure (was: Weekly posting summary for ietf@ietf.org)

2013-06-08 Thread SM
At 15:58 07-06-2013, John C Klensin wrote: And it is getting to that conclusion from the above that often troubles me about the posting summary list rankings. Assuming a significant issues shows up on the list, whether in conjunction with a Last Call or something else. Posting a comment and

Re: ietf@ietf.org is a failure

2013-06-08 Thread Melinda Shore
On 6/8/13 10:09 AM, SM wrote: As an off-topic comment, there are are alternative ways in making a decision; the best judgement of the most experienced or IETF Consensus. I don't think it's off-topic. Consensus (rough or otherwise) requires that at some point people can live with decisions with

Re: ietf@ietf.org is a failure

2013-06-08 Thread Brian E Carpenter
On 09/06/2013 07:55, Melinda Shore wrote: On 6/8/13 10:09 AM, SM wrote: As an off-topic comment, there are are alternative ways in making a decision; the best judgement of the most experienced or IETF Consensus. I don't think it's off-topic. Consensus (rough or otherwise) requires that at

Re: ietf@ietf.org is a failure

2013-06-08 Thread Andy Bierman
Hi, I'm not sure how the desire for IETF Last Call discussions to be on a dedicated and constrained mailing list in any way implies that this generalized and unconstrained list is somehow a failure. Filtering by subject line is unreliable. For example, please provide a filter that will not have

Re: ietf@ietf.org is a failure

2013-06-08 Thread Brian E Carpenter
On 09/06/2013 13:20, Andy Bierman wrote: Hi, I'm not sure how the desire for IETF Last Call discussions to be on a dedicated and constrained mailing list in any way implies that this generalized and unconstrained list is somehow a failure. Filtering by subject line is unreliable. For