[arch-d] Hybrid UniMulticast Routing research : reasonable approach ?

Alexey Eromenko <al4321@gmail.com> Mon, 18 January 2016 15:11 UTC

Return-Path: <al4321@gmail.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A86DF1B382A for <architecture-discuss@ietfa.amsl.com>; Mon, 18 Jan 2016 07:11:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 bOZADSasuBFc for <architecture-discuss@ietfa.amsl.com>; Mon, 18 Jan 2016 07:11:27 -0800 (PST)
Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (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 627F71B3802 for <architecture-discuss@ietf.org>; Mon, 18 Jan 2016 07:11:27 -0800 (PST)
Received: by mail-io0-x22f.google.com with SMTP id g73so359702284ioe.3 for <architecture-discuss@ietf.org>; Mon, 18 Jan 2016 07:11:27 -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:content-type; bh=pfe66keEes/SHr2kAHKmUnfPcSbo/yo+00vVw3T2PXA=; b=Y31HgSAX1ktLXFMLOytXg1jpBKFHKk/Y3SQe/s8EpBip/Aqxl49UVBNx1IivK4TJnS V/DScpulUbzCOpOaWajTP7oMNx2UipVnbtkedkxzsHwNuz4muCNlxXsfISfFJFB6+EGA KcFmA1trBU/fd2glaNAKuIXTgtI8osq5ZWNvfGepZdnLGbYG7hztBLzoM0Cp2k7lgMSb 5BTXRYqpqJF1o8XjmMSbHnVAqaHShf2YXnSo4guOk9YEmcD5n4Ay4XTTM8doPdCmCuCI tlJVZgzwrgQVApRx7PoZhrdQsXRPBrvESfVHsSbpbIKXzEU0T4GGIeZyCtJR6IBlJS2c WQ4g==
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 :content-type; bh=pfe66keEes/SHr2kAHKmUnfPcSbo/yo+00vVw3T2PXA=; b=QYzobKOKIlj4zFe/b+dBkmEG8+A4Y+WVdR+jQu3Gz8xUw/lN/dwBGzX9MhLmTu+Ldd 6dg2I3sP6fR2zOXzphFfLUcI4MKSD1y0Iik9PKwTaQLwezCkHsSoVdKO6Mg/f8ztvBDQ 5p36GFC0Ewtqq9RNk75mvWppXd/agN8G7eP+MaJJt1Z+Z1hzXakHj2j7hrY/xvedwN2P tjfa6rTQTpWFQW1czpw8MdOLUQ/YXr0V8me9exzEE9gSKg4JwfPyGndjGCxBItPMsn8m 74tDYo9tw7h0J+f9x9iuWHlqsf2TvQtG6s9ubU/fq6hYBvfK0kkh1ITmjjNK67dZ4IAP C5RQ==
X-Gm-Message-State: ALoCoQlXVcnN7k12RoLVUF5Aw5ADZJ2Rw6yxFQJNrUj2cQ3MTPP8vwUqKqO6BGPtaG5oCZQ90l5/B1usQkDbT2jWtS69Me/OyA==
X-Received: by 10.107.26.129 with SMTP id a123mr25798110ioa.131.1453129886870; Mon, 18 Jan 2016 07:11:26 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.136.194 with HTTP; Mon, 18 Jan 2016 07:11:07 -0800 (PST)
From: Alexey Eromenko <al4321@gmail.com>
Date: Mon, 18 Jan 2016 17:11:07 +0200
Message-ID: <CAOJ6w=Gmowei-tpYXdf-8k6d9HyXj81L7e6-tsCa5AriBUOaeg@mail.gmail.com>
To: architecture-discuss@ietf.org
Content-Type: multipart/alternative; boundary="001a113fe4beb8302a05299d2a70"
Archived-At: <http://mailarchive.ietf.org/arch/msg/architecture-discuss/_Aj8Z65kPJVQB_Ftxa28XZv5ZQI>
Subject: [arch-d] Hybrid UniMulticast Routing research : reasonable approach ?
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jan 2016 15:11:28 -0000

Rex Buddenberg, rightfully complained, that I don't offer any Multicast
innovation in my IP-FF protocol stack.

IP-FF is not just a copy-paste on existing TCP/IP ideas, but it is an
innovation attempt across all the Internet stack,
where I attempt to improve the Internet at various places, and see what
sticks.

After some Multicast research, I have came out with a very different
approach. Not even close to traditional Multicast.
Hybrid Unicast + Multicast routing, called UniMulticast Routing.

That is: if a destination is visible in Multicast Routing table, it is
routed using Multicast approach, but if it is not in routing table, then it
is routing using Unicast. This implies, that we need source address and two
(!) destination addresses in IP header:
Multicast group address as well as Unicast address. Group address can be
sent inside IP options.

This new approach requires some new protocols: namely IGMPv4, and Enhanced
PIM to work.

Here is my new research paper on this approach:
https://docs.google.com/document/d/1NbDEaItYCrVNgYwOsNF6cps7dCO_VgLzb9bWLxXu3b0/edit?usp=sharing

It is incomplete, but gives a rough idea on my approach.

Is this reasonable ?
-- 
-Alexey Eromenko "Technologov"