Message-Id: <6.2.1.2.2.20050601015442.03f07af0@mail.jefsey.com>
Date: Wed, 01 Jun 2005 01:57:37 +0200
To: Franck Martin <franck@sopac.org>,
	Brian E Carpenter <brc@zurich.ibm.com>
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
In-Reply-To: <429CCF74.70904@sopac.org>
References: <429BD511.4070004@sopac.org> <429C35B6.1070908@zurich.ibm.com>
	<429CCF74.70904@sopac.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
Subject: Re: IETF Newsletter: What's cooking?
Precedence: list
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Frank,
Yes! please have look at http://nicso.org/intldate.txt - It is maintained=
=20
on a daily basis on IANA updates for ccTLDs.
I would love maintaining an equivalent document on IETF. This is for WG-t=
ools?
For example I am unable to understand when last calls are called, what ar=
e=20
the current last calls, what is the URL of the Draft people discuss and=20
never give the URL, etc.
jfc

At 22:56 31/05/2005, Franck Martin wrote:
>Brian,
>Well, Check this old e-mail that I wrote to Fred Baker (ISOC Chair) afte=
r=20
>reading his introduction in the last ISOC Annual Report.
>
>The newsletter could be as simple as listing which RFCs have changed=20
>status, and what are they all about in very simple term
>
>For instance if I take:
>
>4109 Algorithms for Internet Key Exchange version 1 (IKEv1). P.
>     Hoffman. May 2005. (Format: TXT=3D9491 bytes) (Updates RFC2409)
>     (Status: PROPOSED STANDARD)
>
>Each author could bring a simple summary, non technical, with each RFC=20
>submission to answer the following questions:
>What is it for?
>What's has changed since last submission/previous RFCs? (optional)
>Why is it needed?
>How will it change my life?
>
>You cut and paste this information in a monthly/bi-monthly newsletter an=
d=20
>Voila!
>
>-----------------------------
>At 12:21 AM 5/3/2005 +0200, Lynn St.Amour wrote:
>Hi Franck,
>
>thanks for the mail.  I've copied Mirjam as she is working with the IETF=
=20
>looking for ways to increase communications/education wrt IETF's activit=
ies.
>
>Regards,
>Lynn
>
>At 8:50 AM +1200 5/3/05, Franck Martin wrote:
>Fred,
>
>I read with interest the first Annual report of ISOC, I cannot wait to=20
>read the 2004 version!
>
>Your introduction is very instructive as yes ISOC is an IETF organisatio=
n.=20
>This mainly explains why ISOC HQ and chapters are so disconnected.
>
>I see also that ISOC financials are much more healthy since the PIR. It=20
>should give room for improvement.
>
>How to reconnect chapters and ISOC HQ from your point of view.
>
>If ISOC is here to support IETF, and the chapters are here to support IS=
OC=20
>HQ. Then the Chapters must support IETF. Unfortunately the membership is=
=20
>far from being technical people. However these people understand issues.
>
>We would need a monthly brief from IETF sent to all members and what is=20
>cooking in IETF. For instance the recent Domain key proposal was=20
>interesting for the whole community. It could have been explained in or=20
>two paragraphs. I'm sure there are other work in progress that would=20
>interest the community.
>
>You need to do an IETF report, simple, so we know how the IETF is shappi=
ng=20
>the Internet. The Linux community does some kind of bulletins explaining=
=20
>in layman terms the work happening in the kernel, and why a technology i=
s=20
>chosen over another.
>
>With that we will be able to support more the work of the IETF. Therefor=
e=20
>be in synergy with your introduction in the Annual Report.
>
>I suggest you write the first IETF news bulleting, and then "pass the=20
>buck" inside ISOC.
>
>Cheers
>-------------------------------------
>
>Brian E Carpenter wrote:
>
>>Franck,
>>
>>That's a good idea. In fact, it's so good that the IETF's EDU team
>>already has the desire to start a newsletter, with ISOC support. It is
>>not likely to be monthly (too much effort) but it should be regular.
>>
>>     Brian
>>
>>Franck Martin wrote:
>>
>>>I realise the importance of having a newsletter from the IETF that wou=
ld=20
>>>explain every month what is happening in IETF from a non-technical poi=
nt=20
>>>of view.
>>>
>>>The newsletter would be about the protocols which are getting developp=
ed=20
>>>but in non-technical terms (or not too much) so that the general=20
>>>population could understand how the Internet is shapping today.
>>>
>>>At the moment the world is watching how the SPAM issue will be solved,=
=20
>>>if IETF could monthly indicates initiatives taken by IETF in this sens=
e=20
>>>everybody would benefit.
>>>
>>>I see that IETF has a strong link with ISOC, ISOC supports IETF to a=20
>>>large level, however ISOC individual members (most of them are=20
>>>non-technical people) do not know this relationship, nor understand it=
.=20
>>>They also do not understand the day to day activities of IETF.
>>>
>>>Scientific/Technical Vulgarisation is urgently needed!
>>>
>>>In the Pacific Islands many members of the Pacific Islands Chapter of=20
>>>the Internet Society would be interested to learn how IETF is shapping=
=20
>>>the Internet. Speaking with other chapters, they are also strongly int=
erested.
>>>
>>>To pursue the relationship IETF/ISOC and let's say in general=20
>>>IETF/Public I think such monthly newletter is needed (via e-mail it is=
 fine).
>>>
>>>I put humbly this request in front of the Chair of IETF for action.
>>>
>>>Support ISOC individual members and we will support IETF.
>>>
>>>Cheers
>>>
>>>
>>>----------------------------------------------------------------------=
--
>>>
>>>_______________________________________________
>>>Ietf mailing list
>>>Ietf@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/ietf
>
>--
>-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-
>Franck Martin
>franck@sopac.org
>"Toute connaissance est une r=E9ponse =E0 une question"
>G. Bachelard
>
>
>
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www1.ietf.org/mailman/listinfo/ietf


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf