Re: VLSM Tree Routing Protocol and others

Mark Smith <markzzzsmith@gmail.com> Fri, 20 November 2020 06:34 UTC

Return-Path: <markzzzsmith@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 CD3033A1954; Thu, 19 Nov 2020 22:34:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.597
X-Spam-Level:
X-Spam-Status: No, score=-0.597 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_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 KEt9wQx-hk5F; Thu, 19 Nov 2020 22:34:02 -0800 (PST)
Received: from mail-oi1-x22c.google.com (mail-oi1-x22c.google.com [IPv6:2607:f8b0:4864:20::22c]) (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 6B2103A191F; Thu, 19 Nov 2020 22:33:58 -0800 (PST)
Received: by mail-oi1-x22c.google.com with SMTP id f11so9326469oij.6; Thu, 19 Nov 2020 22:33:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=G5QXXXQdU0eGQ1rs7DAb0DiAGpyuCug5VLckV+hT6nc=; b=avV0NIjEzgyVikQynjPETpJWTcx1pXaEm0j98SdYlVn3gZ8j8felo20pY2hTkMjxLC qB65QvDa6Hg4tctGFRNRoAD64g7vA+dB9zVnB7GDrL2zqwViP4SLZ/BnTXcNAGrAVXLt SsVmZuyT0Umik3WXweO/aivq1V2YcMzeDMk2o2E2xkMON19OOECQlh7FkA23Il1d2bA6 +0w0RAbPpg8727xlnqneGeO3bPyfYXn9h96pLEvTgEwcX5y7NWyrQ0cgTYSf4vCUzc7D KtbSmOtxMyUGZlojzwHGTiTymTmsk+DjGIzuw5qSRXiPmfrD5RoUAiLmlwuDWo8IUyiN AThg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=G5QXXXQdU0eGQ1rs7DAb0DiAGpyuCug5VLckV+hT6nc=; b=lmxLb1nVpDnpqDnxpFEBEBVTxfiTldarG3bWICCUdtaoczTpkU8mMNKZmDSTOKL9CP AWLdEW63AiMwz2OrquYixOq8xGx+gXGtiYOvRWupfpcY7o8hYOWdDBSMG6MtHbGQ/Mo7 Jp7+YbCs+QKaxF7eNHYdfdQ9JZSylJpMQ5Ttpa6cfznv8tfIQrFY5ZXwJ569qVFCzvbb /P6upyINU0TOXK0mAxZvVrLQ837nlYi4RP7p9aUl4bFKSDvp5HPlh/mpJ/eK/ysPXcO9 +2sef/BS+DLKgCXZPVkTp96qk6L3Sv7s5C7KKMlPD8+tfXgq48YNdGEFXo32Mk+uOx9T J44w==
X-Gm-Message-State: AOAM532Og1KCEiVPuLNErX1e/FdLEKpPkTGp6C+JD2g4vB3+iWUR0GlX V9jICBaonW8SdSofIvvEmKCXRiC0Lo++EsbOaRc=
X-Google-Smtp-Source: ABdhPJy6iIs8Yh+YK5kUyqGIURY1gORzXa/bSaV33KDu0w5HK/zJEZ1aHy2dCzZbrxgGOuJwza2mKX4g/NQdFzNICrk=
X-Received: by 2002:aca:c4c4:: with SMTP id u187mr4338148oif.54.1605854037632; Thu, 19 Nov 2020 22:33:57 -0800 (PST)
MIME-Version: 1.0
References: <CAPTMOtJNz0jvSib2t_hNSO+JXb2dT8F85D5G4UZviZvnJ-AAfg@mail.gmail.com>
In-Reply-To: <CAPTMOtJNz0jvSib2t_hNSO+JXb2dT8F85D5G4UZviZvnJ-AAfg@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Fri, 20 Nov 2020 17:33:45 +1100
Message-ID: <CAO42Z2z405048fUBLQM0xCJBAz_i1gCz2bJBTZOZQZSRmVbx5Q@mail.gmail.com>
Subject: Re: VLSM Tree Routing Protocol and others
To: shyam bandyopadhyay <shyamb66@gmail.com>
Cc: Nevil Brownlee <rfc-ise@rfc-editor.org>, The IESG <iesg@ietf.org>, rtgwg@ietf.org
Content-Type: multipart/alternative; boundary="000000000000796a9105b484073e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/GHgQzZOYLtd7z6LVKnqXSaUOSy0>
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:34:04 -0000

Has it been implemented and then deployed? Has it been proven to work?

On Fri, 20 Nov 2020, 17:29 shyam bandyopadhyay, <shyamb66@gmail.com> wrote:

> 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
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>