Re: [Pidloc] [DMM] Fwd: New Version Notification for draft-herbert-intarea-ams-00.txt

Tom Herbert <tom@quantonium.net> Tue, 29 January 2019 19:24 UTC

Return-Path: <tom@quantonium.net>
X-Original-To: pidloc@ietfa.amsl.com
Delivered-To: pidloc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D9D2130FD7 for <pidloc@ietfa.amsl.com>; Tue, 29 Jan 2019 11:24:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.042
X-Spam-Level:
X-Spam-Status: No, score=-2.042 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=quantonium-net.20150623.gappssmtp.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 hLqn2aM3afW2 for <pidloc@ietfa.amsl.com>; Tue, 29 Jan 2019 11:24:48 -0800 (PST)
Received: from mail-it1-x135.google.com (mail-it1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) (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 B52BE130FE1 for <pidloc@ietf.org>; Tue, 29 Jan 2019 11:24:48 -0800 (PST)
Received: by mail-it1-x135.google.com with SMTP id z20so6397190itc.3 for <pidloc@ietf.org>; Tue, 29 Jan 2019 11:24:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quantonium-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6ge62Lz2qOnY3l3Is7bO1kLzrVk8edkubx5fr8VZ2SI=; b=oKROj53KPNBAG0SLuaazfUkBLo/VIlhe/+5esx8cpqJeLkatOZl+2ZNnq3xcEnvPw0 MHdFfdyxNoTrCfwqwIm7mdvmThwPqaFTTW6b8qoIhg9ILH7zBKOxQm6ouaEXZa0yaXbh 4up8OOwpya/XlsTfciP6YUG8Xe9e2CQovohM4rAAV0VKDAfCl3uoB0udD6EK/TjAO2br hHVgBMe8VK9AJKD8wfBeNn/pxKfar9eCxmhlHFq4MMI/vCZVfdVF5dcZ0WYwkqAlcD48 /P46WOZ+75boWe6Op5YeQIawrDF1O2bg8qa4+dir6hZe7Y+wjctkx+x5orE6rl94nU3v khPA==
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=6ge62Lz2qOnY3l3Is7bO1kLzrVk8edkubx5fr8VZ2SI=; b=OPRebZ+mjPmEVT2jix4YKsA9qKJ4Th3cHfEvlSvJirWiIT++HhYhb9GvOxVK1m23Bb iECjRnEHeUt0t9DDl0UVKoCXwFkD4k3uV8zQt87HEzN+hX+7XskzwfqWoi3oNcQuj6C8 VnK4acBs9byYxGrZ32oBMjfCbKPKltlNXujvQTUTJABXf4I49YjiBmfwEddIagjhObEF TbIGrDoaWqfqGAfmlVva13qhMCppI0d/z3tOaghVk0chGBT1zN8vjAfKirI8C1m8A2tf 2IfScEc/MJU5kVHCva+/XxiVX/ucWM1BSxVbiVly9nnOIkIIZvbfBk7/HhoqoNaerr2P UuAw==
X-Gm-Message-State: AHQUAuYizyT6c8Fa5HkjhYN7/5Of89d8ykCYPRaMtYbZTFLdGeS9Z8fH NUu2NESKMgbrwNjx2eCEJ05KXtCKIG51Q2L1ja70Dg==
X-Google-Smtp-Source: ALg8bN7WHacqFeo9nVPEhdLTp6xVDy85Eb3He+gzoYpB5XFHLqAbf9FduA/gc2XgX1aXRrLhLCDc5NdNuKmSU+gMX7Y=
X-Received: by 2002:a24:7284:: with SMTP id x126mr13748179itc.15.1548789887797; Tue, 29 Jan 2019 11:24:47 -0800 (PST)
MIME-Version: 1.0
References: <154871730925.2863.111474039018096073.idtracker@ietfa.amsl.com> <CAPDqMer2teQty5RU6GtMuW6sj_HgPHbVKUPcSvj=bWuRe2MCnw@mail.gmail.com> <7be91a164bda4144a12c6c693bae7106@boeing.com> <CAPDqMeqqLx42x_1c3=grWSoryGRS-v8xKP_yiXDO_cpB-JDYew@mail.gmail.com> <2e0c578499cb4761ac113a264f3992a0@boeing.com> <CAPDqMeqg3iRPZjw=sEGuXXeQiw9HVXUROep42Dhs16hgFkN5MA@mail.gmail.com> <47b7c55f5dfa4867ac1763e2c76f3ff0@boeing.com>
In-Reply-To: <47b7c55f5dfa4867ac1763e2c76f3ff0@boeing.com>
From: Tom Herbert <tom@quantonium.net>
Date: Tue, 29 Jan 2019 11:24:36 -0800
Message-ID: <CAPDqMer=xm1CjkkS1EJAm22-rAzWvGHkzpOnbdiEX48gd73DNw@mail.gmail.com>
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
Cc: Vikram Siwach <vsiwach@gmail.com>, "pidloc@ietf.org" <pidloc@ietf.org>, dmm <dmm@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pidloc/qlCuusDDHaNyHPaJQ4qUWx-idH4>
Subject: Re: [Pidloc] [DMM] Fwd: New Version Notification for draft-herbert-intarea-ams-00.txt
X-BeenThere: pidloc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <pidloc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pidloc>, <mailto:pidloc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pidloc/>
List-Post: <mailto:pidloc@ietf.org>
List-Help: <mailto:pidloc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pidloc>, <mailto:pidloc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jan 2019 19:24:53 -0000

On Tue, Jan 29, 2019 at 10:25 AM Templin (US), Fred L
<Fred.L.Templin@boeing.com>; wrote:
>
> Hi Tom,
>
> > -----Original Message-----
> > From: Pidloc [mailto:pidloc-bounces@ietf.org] On Behalf Of Tom Herbert
> > Sent: Tuesday, January 29, 2019 9:36 AM
> > To: Templin (US), Fred L <Fred.L.Templin@boeing.com>;
> > Cc: Vikram Siwach <vsiwach@gmail.com>;; pidloc@ietf.org; dmm <dmm@ietf.org>;
> > Subject: Re: [Pidloc] [DMM] Fwd: New Version Notification for draft-herbert-intarea-ams-00.txt
> >
> > On Tue, Jan 29, 2019 at 8:46 AM Templin (US), Fred L
> > <Fred.L.Templin@boeing.com>; wrote:
> > >
> > > Hi Tom,
> > >
> > > Please read 'draft-templin-rtgwg-scalable-bgp' (only 7 pages). It emphasizes
> > > the scalability considerations from 'draft-templin-intarea-6706bis' that we
> > > omitted from 'draft-ietf-rtgwg-atn-bgp', and also shows that the use cases
> > > are not limited to civil aviation. The purpose is to present a condensed
> > > version of the AERO routing system that has been around for many years.
> > >
> > > In 'draft-templin-rtgwg-scalable-bgp', we show that a BGP overlay can be
> > > organized to support 1B or more de-aggregated MNP prefixes. So, please
> > > have a look at that with the mindset that we are not addressing just the
> > > civil aviation use case but are broadly considering other use cases.
> > >
> > Okay, thanks for the explanation. It might be helpful if you could
> > recast draft-ietf-rtgwg-atn-bgp to be more of a general solution.
>
> Good input, but for that one we really were chartered to focus specifically
> on the aviation use case. Even so, the document says:
>
>    "In this way, each set of c-ASBRs maintains
>    separate routing and forwarding tables so that scaling is distributed
>    across multiple c-ASBR sets instead of concentrated in a single
>    c-ASBR set.  For example, a first c-ASBR set could aggregate an MSP
>    segment A::/32, a second set could aggregate B::/32, a third could
>    aggregate C::/32, etc.  The union of all MSP segments would then
>    constitute the collective MSP(s) for the entire ATN/IPS."
>
> The A::/32, B::/32, C::/32 I think correspond to what your document calls
> "shards", but there is no implied maximum number in the doc so there
> could be thousands. But, in terms of the architecture, all three documents
> ('scalable-bgp', 'atn-bgp' and AERO) really say the same thing - scalable
> deaggregation.
>
I see. I think the atn may be nicely describing the sharding referred
to in AMS. AMS employs caches to ensure direct path for critical
communications. From that POV maybe they are complementary.

> > I looked at draft-templin-rtgwg-scalable-bgp. There's a lot discussion
> > about scalability of c-ASBR but not so much about s-ABSR. I'm
> > primarily interested in the latter because that is where the solution
> > will be providing the oprimizations we want for low latency. While
> > with c-ASBRs we could expect them to have scaling properties similar
> > core routers, I would expect that s-ASBR devices will exhibit a lot
> > more variety and have a wider range of scalability.
>
> The document is very careful to differentiate scaling considerations of
> s-ASBRs independently of the scaling considerations of the stub AS.
> The s-ASBR is the entity that connects the stub AS to the overlay, but
> there may be many other entities inside the stub AS whose job it is
> to coordinate with the mobile nodes.
>
> > For instance, it's
> > conceivable that we might want the functionality incorporated into a
> > low powered device in the base station of a microcell, or incorporated
> > into MEC servers as I mentioned previously. I assume a BGP solution
> > would require all s-ASBRs to hold all the routes for the sub-MNPs as
> > well as being able to consume the rate of mobile events within the
> > sub-MNP.
>
> Other elements inside the stub AS can do the fine-grained mobility
> signaling with the mobile nodes, while the s-ASBR can be deployed in
> such a fashion that all it ever does is send unidirectional BGP updates
> to c-ASBRs.
>
> > So to me, the obvious question is if such a device were only
> > communicating with, say, a 1000 nodes at any givent time, then does it
> > really make sense to give them all the information about the 1M or so
> > nodes in the sub-MNP, or can we just give them the information that is
> > currently useful to them?
>
> The stub ASes accept mobile node customers up to a certain maximum.
> So, if there are currently only 1K customers then there are currently only
> 1K routes. But, let's assume that each stub AS can accept up to 1M mobile
> node customers at a time. Then, if there are 1K stub ASes we achieve our
> 1B MNP goal.
>
> It is also important to understand that the stub AS does not correspond to a
> single sub-MSP aggregated prefix (e.g., 2001:db8::/44). The stub AS will accept
> the MNPs of mobile nodes that are covered by any sub-MSP so routing in the
> stub AS (as well as in the system as a whole) is completely de-aggregated.
>
Sure, but isn't there sub-optimal routing when a node moves to an area
covered by a different stub AS. In that case wouldn't packets be
routed to the home s-ABSR and then forwarded to the remote location.
And even if each stub AS were to support up to 1M nodes, a large
densely populated urban area might have an order of magnitude more
devices which means that the city needs to be divided up into several
areas corresponding to stub-ASs and MNPs. Entropy of motion implies
that a steady state will be reached where a fairly large portion of
users are outside the geographic area corresponging to their MNP so
communications are subject to the triangular routing.

So I think the atn solution might be good to scale the number of
nodes, but sub-optimal routing is going to be problematic for critical
low latency applications. For those, I maintain we always want them to
the most direct route available (e.g. anchorless routing), hence the
value of a cache.

> Thanks for the questions, and let me know if you have any others.
>
> Regard s- Fred
>
> > Do you have any thoughts along these lines?
> >
> > Tom
> >
> > > Thanks - Fred
> > >
> > > > -----Original Message-----
> > > > From: Tom Herbert [mailto:tom@quantonium.net]
> > > > Sent: Tuesday, January 29, 2019 8:33 AM
> > > > To: Templin (US), Fred L <Fred.L.Templin@boeing.com>;
> > > > Cc: dmm <dmm@ietf.org>;; pidloc@ietf.org; Vikram Siwach <vsiwach@gmail.com>;
> > > > Subject: Re: [DMM] Fwd: New Version Notification for draft-herbert-intarea-ams-00.txt
> > > >
> > > > On Tue, Jan 29, 2019 at 7:35 AM Templin (US), Fred L
> > > > <Fred.L.Templin@boeing.com>; wrote:
> > > > >
> > > > > Hi Tom,
> > > > >
> > > > > I read it, and I do not think it is different from the system described
> > > > > in 'draft-ietf-rtgwg-atn-bgp'.
> > > > >
> > > > Hi Fred,
> > > >
> > > > Thanks for the comment. I have read draft-ietf-rtgwg-atn-bgp also. I
> > > > think that the hub and spoke architecture will end up being similar,
> > > > but I'm not sure that this is exactly the same thing. One difference
> > > > is that draft-ietf-rtgwg-atn-bgp is targeted to particular
> > > > application, whereas draft-herbert-intarea-ams endeavours to be
> > > > general purposes. There are differences especially in scalability. For
> > > > instance, rtgwg-atn-bgp mentions network with millions of routes, and
> > > > in draft-herbert-intarea-ams the target is to support networks with
> > > > billions of active addresses for IoT networks. And if we do get to
> > > > unique address per flow, then the total number of addresses to be
> > > > managed is much more (hence why hidden aggregation becomes
> > > > interesting).
> > > >
> > > > Another consideration is MEC servers providing services to UEs at they
> > > > edge. If they participate in the routing/mapping system (as an ASBR-s
> > > > in draft-ietf-rtgwg-atn-bgp and AMS-F in AMS) then the end device can
> > > > perform overlay routing itself. That is very efficient for lowest
> > > > latency. There may be many MEC servers and each one might only be
> > > > communicating with a small subset of all possible nodes. This seems to
> > > > motivate a working set cache to that limits the number of mappings as
> > > > well as the amount of control plane communications.
> > > >
> > > > Tom
> > > >
> > > > > Fred
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: dmm [mailto:dmm-bounces@ietf.org] On Behalf Of Tom Herbert
> > > > > > Sent: Monday, January 28, 2019 3:36 PM
> > > > > > To: dmm <dmm@ietf.org>;; pidloc@ietf.org
> > > > > > Cc: Vikram Siwach <vsiwach@gmail.com>;
> > > > > > Subject: [DMM] Fwd: New Version Notification for draft-herbert-intarea-ams-00.txt
> > > > > >
> > > > > > Hello,
> > > > > >
> > > > > > We've posted a first draft of Address Mapping System (AMS). We
> > > > > > anticipate that this can be applied to mobile networks to provide
> > > > > > optimized overlay routing. In particular, this design provides for
> > > > > > anchorless routing (in the form of anchor bypass) and otherwise
> > > > > > facilitates meeting several requirements for optimizing the mobile
> > > > > > user plane as described in section 1.0 of
> > > > > > draft-bogineni-dmm-optimized-mobile-user-plane-01.  AMS is agnostic to
> > > > > > the underlaying overlay protocol and should be compatible with most of
> > > > > > those being discussed. Another goal of AMS is to not require replacing
> > > > > > exsiting control planes, but can work in concert with them. For
> > > > > > example, the draft discusses how AMS might work with 5G.
> > > > > >
> > > > > > Tom
> > > > > >
> > > > > > ---------- Forwarded message ---------
> > > > > > From: <internet-drafts@ietf.org>;
> > > > > > Date: Mon, Jan 28, 2019 at 3:15 PM
> > > > > > Subject: New Version Notification for draft-herbert-intarea-ams-00.txt
> > > > > > To: Vikram Siwach <tom@quantonium.net>;
> > > > > >
> > > > > >
> > > > > >
> > > > > > A new version of I-D, draft-herbert-intarea-ams-00.txt
> > > > > > has been successfully submitted by Tom Herbert and posted to the
> > > > > > IETF repository.
> > > > > >
> > > > > > Name:           draft-herbert-intarea-ams
> > > > > > Revision:       00
> > > > > > Title:          Address Mapping System
> > > > > > Document date:  2019-01-28
> > > > > > Group:          Individual Submission
> > > > > > Pages:          47
> > > > > > URL:
> > > > > > https://www.ietf.org/internet-drafts/draft-herbert-intarea-ams-00.txt
> > > > > > Status:         https://datatracker.ietf.org/doc/draft-herbert-intarea-ams/
> > > > > > Htmlized:       https://tools.ietf.org/html/draft-herbert-intarea-ams-00
> > > > > > Htmlized:       https://datatracker.ietf.org/doc/html/draft-herbert-intarea-ams
> > > > > >
> > > > > >
> > > > > > Abstract:
> > > > > >    This document describes the Address Mapping System that is a generic,
> > > > > >    extensible, and scalable system for mapping network addresses to
> > > > > >    other network addresses. The Address Mapping System is intended to be
> > > > > >    used in conjunction with overlay techniques which facilitate
> > > > > >    transmission of packets across overlay networks. Information returned
> > > > > >    by the Address Mapping System can include the particular network
> > > > > >    overlay method and instructions related to the method.  The Address
> > > > > >    Mapping System has a number of potential use cases networking
> > > > > >    including identifier-locator protocols, network virtualization, and
> > > > > >    promotion of privacy.
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Please note that it may take a couple of minutes from the time of submission
> > > > > > until the htmlized version and diff are available at tools.ietf.org.
> > > > > >
> > > > > > The IETF Secretariat
> > > > > >
> > > > > > _______________________________________________
> > > > > > dmm mailing list
> > > > > > dmm@ietf.org
> > > > > > https://www.ietf.org/mailman/listinfo/dmm
> >
> > --
> > Pidloc mailing list
> > Pidloc@ietf.org
> > https://www.ietf.org/mailman/listinfo/pidloc