IETF Logo Mail Archive

[v6ops] Reused deprecated prefix (0200::/7)

Александр Иванов <saiv46@yandex.ru> Sun, 23 May 2021 09:47 UTC

Return-Path: <saiv46@yandex.ru>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 065003A0E13 for <v6ops@ietfa.amsl.com>; Sun, 23 May 2021 02:47:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.468
X-Spam-Level:
X-Spam-Status: No, score=-1.468 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_SBL=0.5, URIBL_SBL_A=0.1] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yandex.ru
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 yUrBxyyfxaDP for <v6ops@ietfa.amsl.com>; Sun, 23 May 2021 02:47:51 -0700 (PDT)
Received: from forward103j.mail.yandex.net (forward103j.mail.yandex.net [5.45.198.246]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 496D23A0E11 for <v6ops@ietf.org>; Sun, 23 May 2021 02:47:51 -0700 (PDT)
Received: from myt5-b609f73587e5.qloud-c.yandex.net (myt5-b609f73587e5.qloud-c.yandex.net [IPv6:2a02:6b8:c12:598e:0:640:b609:f735]) by forward103j.mail.yandex.net (Yandex) with ESMTP id C4ACD67414CB for <v6ops@ietf.org>; Sun, 23 May 2021 12:47:46 +0300 (MSK)
Received: from mail.yandex.ru (mail.yandex.ru [176.215.237.83]) by myt5-b609f73587e5.qloud-c.yandex.net (mxback/Yandex) with HTTP id hlUhYV2JnW21-lkJuQGjs; Sun, 23 May 2021 12:47:46 +0300
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1621763266; bh=+l9PFgJmVXf3f8Uim8FyyexzGD0sSg7lPPXNeGovHfc=; h=Message-Id:Date:Subject:To:From; b=aUlrE92eQOeDLN2sPhhy9iBmFeRF/ICS904z8h62LxNh5dRpmRcEaMy9C6YP7iAZx ITcp7vSai2NUXyfM0MWgFeU0Kmmn9kQ8hpHUfcC0cNGCbTZm21LlkQyPGuNgfU0WYj IlfUZ9SjMFHDqwc52EVWhXvILjgnx9fUOVg8M6+I=
Authentication-Results: myt5-b609f73587e5.qloud-c.yandex.net; dkim=pass header.i=@yandex.ru
Received: by myt6-4204cefb5b39.qloud-c.yandex.net with HTTP; Sun, 23 May 2021 12:47:46 +0300
From: Александр Иванов <saiv46@yandex.ru>
To: "v6ops@ietf.org" <v6ops@ietf.org>
MIME-Version: 1.0
X-Mailer: Yamail [ http://yandex.ru ] 5.0
Date: Sun, 23 May 2021 12:47:46 +0300
Message-Id: <367011621762088@mail.yandex.ru>
Content-Transfer-Encoding: 8bit
Content-Type: text/html; charset="utf-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/dNQKOpvwuY_M-oD5lBnBO1vZzHc>
Subject: [v6ops] Reused deprecated prefix (0200::/7)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 23 May 2021 09:47:56 -0000

Hello, v6ops maillist members,

I want to talk about the 0200::/7 prefix, which is officially deprecated (RFC4048), but actually used from 2017 to now.

There's a project called Yggdrasil Network - a self-arranging encrypted IPv6 network (https://yggdrasil-network.github.io/)" rel="noopener noreferrer nofollow" target="_blank">https://yggdrasil-network.github.io/) which utilizes this deprecated prefix ...and its network already has members that use it for business purposes.

How do you think about allocating that prefix as a software-routed global unicast address? A future RFC can be merged with draft-horley-v6ops-expand-doc-00.

I highly appreciate any feedback and help for new to the IETF.

Regards,
~ Alexander Ivanov, Russia

v2.23.0 | Report a Bug | By Email