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; Sat, 25 Jun 2005 03:26:54 +0200 X-Sieve: CMU Sieve 2.2 Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id C2D4361B65 for ; Sat, 25 Jun 2005 03:26:54 +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 15568-06 for ; Sat, 25 Jun 2005 03:26:50 +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 F362161AF3 for ; Sat, 25 Jun 2005 03:26:44 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DlzMm-00025A-67; Fri, 24 Jun 2005 21:21:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DlzMj-00024s-AQ; Fri, 24 Jun 2005 21:21:49 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17698; Fri, 24 Jun 2005 21:21:47 -0400 (EDT) Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DlzlJ-0004wW-N2; Fri, 24 Jun 2005 21:47:17 -0400 Received: from ver78-2-82-241-91-24.fbx.proxad.net ([82.241.91.24] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1DlzMY-0004Ia-EN; Fri, 24 Jun 2005 18:21:38 -0700 Message-Id: <6.2.1.2.2.20050625014553.0500f930@mail.jefsey.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Sat, 25 Jun 2005 03:21:32 +0200 To: "Steve Silverman" , "Ralph Droms" , "IESG" From: "JFC (Jefsey) Morfin" In-Reply-To: References: <1119652896.5791.21.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; 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 - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jefsey.com X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Cc: lroberts@packet.cc, IETF Announcement list Subject: RE: IANA Action: Assignment of an IPV6 Hop-by-hop Option 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 At 01:11 25/06/2005, Steve Silverman wrote: >At a recent meeting, Dr. Roberts said that this option had been >approved as a recommendation by an ITU Study Group. He didn't >indicate which SG or what the rec. number would be. He said he had an >ISP that wanted to deploy this function. >If all this is true, would it not be reasonable for IANA to assign a >code to an ITU approved option to avoid incompatible codepoint use? > >If IANA doesn't support ITU work, this might be construed as a reason >to move the IANA function to an ITU Study Group or another >administrative body that might be neutral with respect to the various >standards bodies. Dear Brian Carpenter, Michelle Cotton, Leslie Daigle, Bill Fenner, Barbara Fuller, Ted Hardie, Sam Hartman, Scott Hollenbeck, Russ Housley, David Kessens, Allison Mankin, Dave Meyer, Jon Peterson, Joyce K. Reynolds, Barbara Roseman, Mark Townsley, Amy Vezza, Margaret Wasserman, Bert Wijnen, Alex Zinin, What is the IANA? - is it the 35 649 341 chars concatenation of the results of the RFC IANA considerations parts plus the names and numbers ICANN files? - is it the to be urgently distributed common parameters and reference repository for the needs of the Global Internet Community? Networking by essence is to share parameters. Is this some want to rule a IANA registrar in their business field? The days of centralised IANA (and power) are over: network development means that every relational space of exchanges needs a common clearing house for its networking. We urgently need to understand what it means in term of IANA policy, organisation, architecture. The IANA must be distributed and its policy totally reviewed. Consistence with ISO 11179 insured.... When the very founder of the ARPANET is refused to register a parameter (whatever it is, whatever the purpose, whatever the reason) what are the chances of one of the 800 millions common users who will also to register manythings. Under the current urgent need to address the questions above, did you not see this is not even forcing an ITU alt-IANA, this is forcing balkanisation, pulverisation? If an idea is good you will not block it in denying it a parameter registration. If an idea is bad you will create it support in denying it. You will let it die in treating it equal. jfc _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf