IETF Logo Mail Archive

Topic IPv6

Alexander Nevalennyy <avnevalenniy@gmail.com> Mon, 21 November 2016 12:49 UTC

Return-Path: <avnevalenniy@gmail.com>
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 33772129554 for <ietf@ietfa.amsl.com>; Mon, 21 Nov 2016 04:49:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 EII4HIY6j4g8 for <ietf@ietfa.amsl.com>; Mon, 21 Nov 2016 04:49:22 -0800 (PST)
Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E858C1294E4 for <ietf@ietf.org>; Mon, 21 Nov 2016 04:49:21 -0800 (PST)
Received: by mail-qk0-x22d.google.com with SMTP id n204so348558864qke.2 for <ietf@ietf.org>; Mon, 21 Nov 2016 04:49:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=N/78QIuifqwUzkdZ1xBWL6u86qglbqRbXg9NepfvwWo=; b=D1NSqb98GrJ2Sr7GWvp0cixPWb6UX1YipIztrFFT9mXahLHUV8Ej2gXBtUeaszA6jK TOG+IMIDGd8HD56CdUk/SQzLl+mAULR8vLA/8DQ49kupdd1sh15VKYOSPUak32cQo0W1 OQDQbFCKGojlTX5Nr8j3f+ZOn45gAB9Jam+JHNXX4jkHXdXa51+zyGWYEDb1FguqGZBJ G0HZWaQMW6YTpOActsX5nhym2vtJAp/EZGfNb5EEo7dmRu3wAD20qgAw1DIMJoW6ey0b UvX2NNGCbCnjOBFr33fZjqirSPIe7EszFiPlGezWdIwHVjpJmpfV3Mq3q+PZLZJFMLDa 1l6w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=N/78QIuifqwUzkdZ1xBWL6u86qglbqRbXg9NepfvwWo=; b=g8XJuw8PbpPF+faAregPpYkAkh5FflauYggJxr9LKyEMS3qcAF2iS9v3AEA9KxK8hu qrNCznQnNfsPCXjRCV3ZfgZmoGT+3SwNNuvmvOwTw62MsTEIRvlfmAucBI1RX0vwo6gP ukWjXLz6LiZUTLWToQN8cA1H270oOnJvKT+TSOtCmJHU4FLcTeITWTzMaKpHIwHba2a7 CiLdAOHMqqodEP3Ldhnsgfd25XX8CDFKiz5Vh4giq2gEp/fTIGtIi9gk/zkdi/gLPorS iTNOu4d+55Cg5Ykb/cR7ZeL3dzpsW6VQSUclbpYCbC7QrFctdyg360C7biSkVcXu4wEZ pTmQ==
X-Gm-Message-State: AKaTC01AcQh7+UIUVji1qUTcLARZI6+jWZM+H1RRR5mVPouTgpMRqjRygc3DwC5+KAlWbJ1MiLMOKje9/ri1rg==
X-Received: by 10.55.3.2 with SMTP id 2mr16948390qkd.65.1479732560786; Mon, 21 Nov 2016 04:49:20 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.170.20 with HTTP; Mon, 21 Nov 2016 04:49:20 -0800 (PST)
From: Alexander Nevalennyy <avnevalenniy@gmail.com>
Date: Mon, 21 Nov 2016 15:49:20 +0300
Message-ID: <CAGxDXJ9OR0DWqAfiDH3XMNh12znN9giR9f1-T945e=-ccvcZLA@mail.gmail.com>
Subject: Topic IPv6
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary="001a114c9cc4a5fc5f0541cf1552"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FFkqqqiCyKLC0d29rv4T8fzm8XA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
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 12:49:23 -0000

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

v2.23.0 | Report a Bug | By Email