Re: Topic IPv6
JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Mon, 21 November 2016 13:00 UTC
Return-Path: <prvs=113363ceea=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78A081295DB for <ietf@ietfa.amsl.com>; Mon, 21 Nov 2016 05:00:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102
X-Spam-Level:
X-Spam-Status: No, score=-102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uzldb5Min1mQ for <ietf@ietfa.amsl.com>; Mon, 21 Nov 2016 05:00:54 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCA521295AC for <ietf@ietf.org>; Mon, 21 Nov 2016 05:00:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1479733250; x=1480338050; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=a6VQ22gzjNvBcZnC3PWHJXxJl 23tF/0o6ttAWhkdfMM=; b=jSoInWFMh+5JoOWP+82jbCC1TH235ay/eA3MYmh7b he22z/5UGd6gF3yzTT6SLW8972vNJ7TNyCgsMzGOpMol5jgPE+Rn+r+odLD8bEdW UQ3nLhbdMRSKlhrP6ikdaK3jhi93RFuvjlGKIs3iquYtDZMsLz9X282kN8YeqJAy Dc=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=qdlxnVZV+WAE6Gf+NM8qFJeI6iFeP/c+wstqw0o0OF5OaZSYJ34wSjzs/anL Ui92nlx7ThyhPpI3GRk6TZqBz+Ic6D2AYLo+z7B5JNA124vBJBozou59M cl1GF7L58Us/e9Jt2xDv2HOoLO+MjZMq+LE4CQElAYmGSZXj2R4Xrg=;
X-MDAV-Processed: mail.consulintel.es, Mon, 21 Nov 2016 14:00:50 +0100
X-Spam-Processed: mail.consulintel.es, Mon, 21 Nov 2016 14:00:49 +0100
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005234155.msg for <ietf@ietf.org>; Mon, 21 Nov 2016 14:00:49 +0100
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:161121:md50005234155::vtkxMGu/PphD5ads:00000ds4
X-Return-Path: prvs=113363ceea=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.1c.1.161117
Date: Mon, 21 Nov 2016 14:00:45 +0100
Subject: Re: Topic IPv6
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: ietf@ietf.org
Message-ID: <C2D3FB09-D078-4D7A-8FE5-422EB004CC0F@consulintel.es>
Thread-Topic: Topic IPv6
References: <CAGxDXJ9OR0DWqAfiDH3XMNh12znN9giR9f1-T945e=-ccvcZLA@mail.gmail.com>
In-Reply-To: <CAGxDXJ9OR0DWqAfiDH3XMNh12znN9giR9f1-T945e=-ccvcZLA@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/arYbMkt6_Cm9yn9IfdDWeI8YwlE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Nov 2016 13:00:55 -0000
Hi Alexander, My takes on your points: 1. This will be against privacy … Even if the IETF want to do that, not sure if law in different countries will accept it. 2. The addressing space, for both IPv4 and IPv6 can’t depend on geographical allocation. ISPs can be multinational, etc. 3. SLAAC is already present in IPv6, not sure what do you mean here. 4. I don’t think this is in the scope of IETF … Basically, all the topics that you are proposing here may be related to different WGs, and I don’t think (very personal opinion), they are good ideas at all … even do, I’m sure others will provide inputs and if you want to keep going on, as suggested in my first email, read the IETF TAO and documents for newcomers, to understand the IETF process and start with the work. If you have link to documents that you presented in other places, it will be probably good to provide the links (don’t attach documents). Regards, Jordi -----Mensaje original----- De: ietf <ietf-bounces@ietf.org> en nombre de Alexander Nevalennyy <avnevalenniy@gmail.com> Responder a: <avnevalenniy@gmail.com> Fecha: lunes, 21 de noviembre de 2016, 13:49 Para: <ietf@ietf.org> Asunto: Topic IPv6 Hi Jordi, I have presented my ideas at some forums already. I would like to share my ideas to be fit in topic and mail list. I will be happy if somebody advice section of conversation. My ideas (simply), all parts must be used together: 1. Denying NAT technology in way of stopping all anonymous action in the Internet. I am not sure how is possible to change different RFC. 2. Dividing pool of IPv6 between countries like it done in telephone industry. For example prefix for Los-Angeles 1213::/16, Moscow 7495::/16 3. Usage SLAAC for all devices making IPv6 address 4. Making international deals to regulate Internet job (ICANN maybe like regulator and Interpol like central cyber - police) Something like that... Regards, Alexander Nevalenniy ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
- Topic IPv6 Alexander Nevalennyy
- Re: Topic IPv6 JORDI PALET MARTINEZ
- Topic IPv6 Alexander Nevalennyy
- Re: Topic IPv6 JORDI PALET MARTINEZ
- Topic IPv6 Alexander Nevalennyy
- Re: Topic IPv6 Stephane Bortzmeyer
- Re: Topic IPv6 Harald Alvestrand
- Re: Topic IPv6 Stewart Bryant
- Re: Topic IPv6 Alexander Nevalennyy
- Re: Topic IPv6 Stephane Bortzmeyer
- Re: Topic IPv6 Alexander Nevalennyy
- Re: Topic IPv6 Alexander Nevalennyy
- Re: Topic IPv6 shogunx
- Re: Topic IPv6 Stewart Bryant
- Re: Topic IPv6 shogunx
- RE: Topic IPv6 Tony Hain
- RE: Topic IPv6 Michael Froomkin - U.Miami School of Law
- RE: Topic IPv6 Tony Hain
- Re: Topic IPv6 Brian E Carpenter
- Re: Topic IPv6 Brian E Carpenter
- Re: Topic IPv6 Alexander Nevalennyy
- Re: Topic IPv6 Jari Arkko
- Re: Topic IPv6 Jari Arkko