[Flexip] New Non-WG Mailing List: FlexIP

IETF Secretariat <ietf-secretariat@ietf.org> Tue, 27 November 2018 17:43 UTC

Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: flexip@ietf.org
Delivered-To: flexip@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BDE4128766; Tue, 27 Nov 2018 09:43:37 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: flexip@ietf.org, liguangpeng@huawei.com, rgm@labs.htt-consult.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.89.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <154334061723.21429.4961526034424292333.idtracker@ietfa.amsl.com>
Date: Tue, 27 Nov 2018 09:43:37 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/flexip/-OcAw1SEbN7dxpcgLP3CeUjd7js>
X-Mailman-Approved-At: Tue, 27 Nov 2018 10:08:56 -0800
Subject: [Flexip] New Non-WG Mailing List: FlexIP
X-BeenThere: flexip@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Flexible Internet addressing and Flexible routing <flexip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/flexip>, <mailto:flexip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/flexip/>
List-Post: <mailto:flexip@ietf.org>
List-Help: <mailto:flexip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/flexip>, <mailto:flexip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2018 17:43:38 -0000

A new IETF non-working group email list has been created.

List address: flexip@ietf.org
Archive: https://mailarchive.ietf.org/arch/browse/flexip/
To subscribe: https://www.ietf.org/mailman/listinfo/flexip

Devices need to know how to connect to the right network.  Within the IETF alone, The Flexible Address Space is divided between an unbounded little endian Global Address Part and an unbounded big endian Local Address Part. This allows the public network to grow and route as needed and for the local or private networks to use addressing and that makes the most sense within each network. Privacy can be included in both parts by use of a MapID. Routing is manged in a Multi-Entrance-Trie.

This list belong IETF area: INT(ernet)

For additional information, please contact the list administrators.