Return-Path: Received: from murder ([unix socket]) by eikenes.alvestrand.no (Cyrus v2.2.8-Mandrake-RPM-2.2.8-4.2.101mdk) with LMTPA; Tue, 31 May 2005 12:03:50 +0200 X-Sieve: CMU Sieve 2.2 Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id ED11261B50 for ; Tue, 31 May 2005 12:03:49 +0200 (CEST) Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23604-04 for ; Tue, 31 May 2005 12:03:44 +0200 (CEST) X-Greylist: domain auto-whitelisted by SQLgrey-1.4.8 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by eikenes.alvestrand.no (Postfix) with ESMTP id 47A0061AF3 for ; Tue, 31 May 2005 12:03:35 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dd3XN-0005iT-Oy; Tue, 31 May 2005 05:59:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dd3XL-0005iG-7G for ietf@megatron.ietf.org; Tue, 31 May 2005 05:59:51 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23005 for ; Tue, 31 May 2005 05:59:48 -0400 (EDT) Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dd3qr-0006iE-IW for ietf@ietf.org; Tue, 31 May 2005 06:20:06 -0400 Received: from [82.241.91.24] (helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1Dd3X8-0006hW-0B; Tue, 31 May 2005 02:59:38 -0700 Message-Id: <6.2.1.2.2.20050531090353.03f24800@mail.jefsey.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Tue, 31 May 2005 11:59:24 +0200 To: Franck Martin , ietf@ietf.org From: "JFC (Jefsey) Morfin" In-Reply-To: <429BD511.4070004@sopac.org> References: <429BD511.4070004@sopac.org> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - montage.altserver.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - jefsey.com X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id FAA23005 Cc: Subject: Re: IETF Newsletter: What's cooking? X-BeenThere: ietf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF-Discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ietf-bounces@ietf.org Errors-To: ietf-bounces@ietf.org X-Virus-Scanned: amavisd-new at alvestrand.no Dear Franck, your proposition is a key issue for the stability of the Internet. If IET= F=20 does not provide exposition and recognition to its Members and to its=20 solutions, the quality of the Membership decreases (RFC 3774), solutions=20 will be/are worked outside and will not be consistent (within and outside= =20 of the IETF). The problem is who will run the newsletter? With which=20 authority? In any case it can only be a _report_ by third informed parties (they MUS= T=20 not commit the IETF). If you consider the problem and the budget of vario= us=20 formulas, it look like there are only two long term, viable, stable and=20 exciting solutions: 1. a multilingual technical internet paper magazine, sponsoring local=20 Internet shows and conferences. This should be coupled with the RFC Edito= r,=20 for speed and mutual editing services, etc. It would also contribute to t= he=20 administration of the Internet standard process. It would also be the rig= ht=20 place for an "Internet Book", an organised updated compendium of the RFC=20 states of the art. This would be some kind of revolution (as it would=20 introduced readers feed-back and quality control), with public's comments= =20 Selections and IESG decisions, and multicultural positions. This can only= =20 be something organised by the IASA granting an exclusive right to use IET= F=20 name, logo, etc. 2. a GPL effort to maintain an Internet Book and Sources by a dedicated=20 group. But this would probably lead to an independent innovative effort. This does not mean that Drafts authors could not contribute. But it would= =20 be in addition to the Internet standard process. Due to the special needs= =20 of SOPAC, may be could you be interested in participating to such a secon= d=20 approach. This could permit to plug-in customised standards for special=20 situations like yours, without disrupting the global architecture. This is in tune with the questions I rose about experimentation and=20 ccTLD/LIC's needs not currently supported by IETF and part of the Draft I= =20 prepare. I will have a questionaire sent to ccTLD/LICs. If the issue is o= f=20 interest to you, you welcome. jfc At 05:08 31/05/2005, Franck Martin wrote: >I realise the importance of having a newsletter from the IETF that would= =20 >explain every month what is happening in IETF from a non-technical point= =20 >of view. > >The newsletter would be about the protocols which are getting developped= =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, i= f=20 >IETF could monthly indicates initiatives taken by IETF in this sense=20 >everybody would benefit. > >I see that IETF has a strong link with ISOC, ISOC supports IETF to a lar= ge=20 >level, however ISOC individual members (most of them are non-technical=20 >people) do not know this relationship, nor understand it. They also do n= ot=20 >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 th= e=20 >Internet Society would be interested to learn how IETF is shapping the=20 >Internet. Speaking with other chapters, they are also strongly intereste= d. > >To pursue the relationship IETF/ISOC and let's say in general IETF/Publi= c=20 >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 > >-- >-=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