<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Fred,<br>
<br>
It seems to me the journal is a kind of "Trip Report": We ent to IETF,
we talked about that and that, we created this group, we made xxx
RFCs,....<br>
<br>
And it is still too technical. The technical part still need to stay.<br>
<br>
Add a part that describes in layman terms a specific RFC or a group of
RFC.<br>
<br>
I see there is a group in IETF involved in SPAM. Can someone explain
what is happening? Which technology are being looked at? What does it
require to change on the client application.... What are the different
players? Who is supporting what technology? Advantages and problems
with one technology over the other? Where to go from now? etc....<br>
<br>
I still need to finish to read the journal, but I like it as first
issue. I just see it is still for technical people...<br>
<br>
We need to find the "Hubert Reeves" of the Internet.<br>
<br>
Cheers<br>
<br>
<br>
<br>
Fred Baker wrote:
<blockquote cite="mid033AA40E-2A7B-4AC2-9468-7B1DA881D584@cisco.com"
type="cite">What specifically do you want changed, Franck? The journal
is *not* for IETF members - they already know what's being discussed on
the mailing lists they follow. It is for, at least the web site says,
people that have an interest in following the issues discussed in the
body, which might include but is in no sense limited to prospective new
participants.
<div><br>
<div>
<div>On Oct 10, 2005, at 8:13 PM, Franck Martin wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"> I'm welcoming the IETF journal, this was
long overdue.<br>
<br>
I just browsed quickly through it and I find it still very very
technical with no sections for the Internet user on the street. It
stills looks to me a collection of progress reports from the various
IETF related groups.<br>
<br>
We learn that things are happening, but we don't know why. We need some
background information.<br>
<br>
I think I have a different audience view. The IETF journal should be
directed towards the Internet Users and all ISOC members and not to the
IETF members exclusively, or ISOC is not doing its role of advocacy.<br>
<br>
I hope to see a change in next IETF journal release.<br>
<br>
Cheers<br>
<br>
-------- Original Message --------
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<th align="right" nowrap="nowrap" valign="baseline">Subject: </th>
<td>[ISOC-members-announce] Announcing the IETF Journal - a
new ISOC Publication</td>
</tr>
<tr>
<th align="right" nowrap="nowrap" valign="baseline">Date: </th>
<td>Fri, 7 Oct 2005 10:45:24 -0400</td>
</tr>
<tr>
<th align="right" nowrap="nowrap" valign="baseline">From: </th>
<td>David McAuley <a class="moz-txt-link-rfc2396E"
href="mailto:mcauley@isoc.org"><mcauley@isoc.org></a></td>
</tr>
<tr>
<th align="right" nowrap="nowrap" valign="baseline">To: </th>
<td><a class="moz-txt-link-rfc2396E"
href="mailto:isoc-members-announce@elists.isoc.org"><isoc-members-announce@elists.isoc.org></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>Dear Members:
ISOC is pleased to announce the "IETF Journal", a new Internet Society
publication produced in cooperation with the Internet Engineering Task
Force. Our aim is to provide an easily understandable overview of what's
happening in the world of Internet standards with a particular focus on the
activities of the IETF Working Groups (WG). Each issue of the "IETF Journal"
will highlight some of the hot issues being discussed in IETF meetings and
in the IETF mailing lists. Our first issue takes a look back at the recent
63rd meeting of the IETF in Paris.
<a class="moz-txt-link-freetext"
href="http://ietfjournal.isoc.org/">http://ietfjournal.isoc.org/</a>
Best wishes to you all.
David
David McAuley
Membership Director
Internet Society
703-326-9880, ext 104
703-963-5887 (mobile)
<a class="moz-txt-link-abbreviated" href="mailto:mcauley@isoc.org">mcauley@isoc.org</a>
_______________________________________________
ISOC-members-announce mailing list
<a class="moz-txt-link-abbreviated"
href="mailto:ISOC-members-announce@elists.isoc.org">ISOC-members-announce@elists.isoc.org</a>
<a class="moz-txt-link-freetext"
href="http://elists.isoc.org/mailman/listinfo/isoc-members-announce">http://elists.isoc.org/mailman/listinfo/isoc-members-announce</a>
To unsubscribe, send a blank message to: <a
class="moz-txt-link-abbreviated"
href="mailto:isoc-members-announce-leave@elists.isoc.org">isoc-members-announce-leave@elists.isoc.org</a>
Please note that by leaving this membership list you will also be resigning ISOC membership.
</pre>
<br>
<pre class="moz-signature" cols="72">--
Franck Martin
ICT Specialist
<a class="moz-txt-link-abbreviated" href="mailto:franck@sopac.org">franck@sopac.org</a>
SOPAC, Fiji
GPG Key fingerprint = 44A4 8AE4 392A 3B92 FDF9 D9C6 BE79 9E60 81D9 1320
"Toute connaissance est une reponse a une question" G.Bachelard
</pre>
<div style="margin: 0px;">_______________________________________________</div>
<div style="margin: 0px;">Chapter-delegates mailing list</div>
<div style="margin: 0px;"><a
href="mailto:Chapter-delegates@elists.isoc.org">Chapter-delegates@elists.isoc.org</a></div>
<div style="margin: 0px;"><a
href="http://elists.isoc.org/mailman/listinfo/chapter-delegates">http://elists.isoc.org/mailman/listinfo/chapter-delegates</a></div>
<br class="Apple-interchange-newline">
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Franck Martin
ICT Specialist
<a class="moz-txt-link-abbreviated" href="mailto:franck@sopac.org">franck@sopac.org</a>
SOPAC, Fiji
GPG Key fingerprint = 44A4 8AE4 392A 3B92 FDF9 D9C6 BE79 9E60 81D9 1320
"Toute connaissance est une reponse a une question" G.Bachelard
</pre>
</body>
</html>