VLSM Tree Routing Protocol and others

shyam bandyopadhyay <shyamb66@gmail.com> Fri, 20 November 2020 06:29 UTC

Return-Path: <shyamb66@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B02093A1912; Thu, 19 Nov 2020 22:29:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 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, SPF_HELO_NONE=0.001, 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 Z0c6736kSy4s; Thu, 19 Nov 2020 22:29:28 -0800 (PST)
Received: from mail-qk1-x744.google.com (mail-qk1-x744.google.com [IPv6:2607:f8b0:4864:20::744]) (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 317763A1908; Thu, 19 Nov 2020 22:29:28 -0800 (PST)
Received: by mail-qk1-x744.google.com with SMTP id d9so8010208qke.8; Thu, 19 Nov 2020 22:29:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=LUe4PGHJ/4iH3DpbYeIvqNGbwJ6HM3VjNmvsDyrAXOU=; b=p9p6AENPjboCYaZ0yhi/zlMPvTAFICm4TacdMGNskEZgP+5Rn7Y8iWdZ9+rX7Ebbof gVi3DX6PBIKG6A+mstRgHaK5q75d3fHT33C9QEG5VflqWVNH2tpLkMpulF0zrRhIHPYB YVOcm/bq0YKMjwtUf5NyiwZl9eppBOt9dEXPC/RUSdEq74k4T7At40ROaibjFo+p0p9r 9+3zqLkYNvyCH0pzQUbPyWxo+XamT7MAtyhucaOuy+/b2X44Yf89vjON4Atbf/Mz+uiv WS+h2Ckds5AdZAZwpWU/6VfKOkK46BACz7r4qu3/WlaiIaNMAs06ggxITqWwjHixyLRd fjDg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=LUe4PGHJ/4iH3DpbYeIvqNGbwJ6HM3VjNmvsDyrAXOU=; b=dJMiH31+qYWKT66Xc2wieFj7V7n0Fv2fyjqoYd3gGK6MGzxYMPH5g2g8HULjTDVFnP F8wOhYQAVJLjIV+/ulXWGUj+mjqdnaTjYvGlTXtYaPSZ42DxjCO8Zv86hjOU1aqfcVeM JCk0YVYlGhaDbvcs1OYf7kGuvEpJeFMZY/v8nBqp/rwQD8+NbeWa5XWe9c32h0RyT64i 5tH5jMmxV0LOexlFu3UoPWtMUeJ5jc8Xl3n9mu285JhqoelF1g4+2VoX+Nkq3rQpFAdn 74/To5neWKsOMNaER1D4V8hBpD6x1yw8bfzN8UlklRkFumxsBYoTEMc7nVCbiOXCfoxd ilUQ==
X-Gm-Message-State: AOAM531263atDZ5t9BRErHY1UuBVgV3v8bmkfeQybuogM8PH8hbdGDZ1 gp0OQFx0g7SLDoqfTTBmZT+8gtv9E24NSwpJIOzYcV5Gi6P7za8IauY=
X-Google-Smtp-Source: ABdhPJxbe28eE+q8mttwJP9VuuQkkU+6cFT5mj/mUXcCVmlGuXRmEqTw7lnCNuUFn14d3HlFPFn0zCDUTgam4zLbpHs=
X-Received: by 2002:a37:a58e:: with SMTP id o136mr14727627qke.290.1605853767313; Thu, 19 Nov 2020 22:29:27 -0800 (PST)
MIME-Version: 1.0
From: shyam bandyopadhyay <shyamb66@gmail.com>
Date: Fri, 20 Nov 2020 11:59:01 +0530
Message-ID: <CAPTMOtJNz0jvSib2t_hNSO+JXb2dT8F85D5G4UZviZvnJ-AAfg@mail.gmail.com>
Subject: VLSM Tree Routing Protocol and others
To: Nevil Brownlee <rfc-ise@rfc-editor.org>, iesg@ietf.org, rtgwg@ietf.org
Content-Type: multipart/alternative; boundary="0000000000005caf1305b483f7f6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/lggbYGv_IA4Yaj3c5QPSWBhDeFg>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Nov 2020 06:29:30 -0000

Dear Adrian,

I would like to appeal once again to consider the following drafts
to be published under the Independent Submission stream.

1. draft-shyam-vlsmtrp: This is a routing protocol applicable inside a
provider network where it
appears to be in the form of a tree and distribution of address space takes
place with the approach of
VLSM. It covers routing as well as all related aspects that are required as
a substitute of BGP inside VLSM tree.

2. draft-shyam-hipi: This is a protocol to identify hosts uniquely with
provider independent addresses
where customers' networks are connected to more than one service provider.
It is based on the
approach of DNS and can be considered as an alternative to HIP.

3. draft-shyam-site-multi: It provides a solution for site multihoming of
stub networks.
This is based on the principle of "default routing based on the
source domain of the source address of the outgoing traffic". Out of all
the possible paths between source and destination, it goes through the
path selection criterion on end to end basis. It provides a mechanism to
switch over to an alternate route on link failure.

As I had said earlier, draft-shyam-site-multi, draft-shyam-hipi and
draft-shyam-vlsmtrp
has got reference to draft-shyam-real-ip-framework which is a proposed
framework that can
be considered for the ease of routing and for the convenience of
distribution.But, they can exist on their own irrespective of the framework
supported. draft-shyam-vlsmtrp and draft-shyam-hipi expects distribution of
address space the way it appears in draft-shyam-real-ip-framework.

Thanks,
Shyam