IETF Logo Mail Archive

Re: [DMM] BGP-based DMM for civil aviation

Erik Kline <ek@loon.co> Mon, 07 January 2019 22:26 UTC

Return-Path: <ek@google.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B5E612E036 for <dmm@ietfa.amsl.com>; Mon, 7 Jan 2019 14:26:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.499
X-Spam-Level:
X-Spam-Status: No, score=-9.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=loon.co
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 8VEcSmdRSpqd for <dmm@ietfa.amsl.com>; Mon, 7 Jan 2019 14:26:04 -0800 (PST)
Received: from mail-it1-x12e.google.com (mail-it1-x12e.google.com [IPv6:2607:f8b0:4864:20::12e]) (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 F29C212DDA3 for <dmm@ietf.org>; Mon, 7 Jan 2019 14:26:03 -0800 (PST)
Received: by mail-it1-x12e.google.com with SMTP id p197so3447277itp.0 for <dmm@ietf.org>; Mon, 07 Jan 2019 14:26:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=loon.co; s=google; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=O0QQFtPxhghhU0bSB+rmE0GZAMcQ+Up/mfNcLYS+NzU=; b=kHvxLRcc58muSQN2sGr82/dxYnyfKnYHRZ1choGmS4p4Ub6rVkA/sVN1H2fM4ZRuMf U/MKMUnGMzP/fvHlM2eiiv6v9gD75tFUjAOY5n4mDrTmmwYrPHf/g8NftKYHaRr2pX7n k9Vp2LouC2cgS8IpgXOpY7xpFJXTAiu22QgKs=
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:reply-to :from:date:message-id:subject:to:cc; bh=O0QQFtPxhghhU0bSB+rmE0GZAMcQ+Up/mfNcLYS+NzU=; b=T2TZTl6gIsqP7CpYsdAhJwEjT/1xs+TF/1tKOcnZO3dhfgqmitOhSv4/YEG72GYcUL CwONFp7Ns3IXbbYVXX4gKGyjoHk4Dpi/AAwHfOBdoJ9HtYCy1cJHoZ5q3M8VdeJYHQuB FuiXcq7TSAJKEDC5zzVEf68HXpSL9kbog4nLaN4pVhT+dHq4ey/xkquvvlxgNCQRyeiV JBjdzRzeE4aDYUFyu0mppJCE+KdZgrYT0DaAcK5f+Si352GWgGbfd/ZOY+bo4D18FiKE My5KWRDOKlyXwMfLjiEAfXzt7rO3pBVMMWyuFXvDkfXB3k+aNPnkkKZZRqMR25dC/0+w ejzg==
X-Gm-Message-State: AJcUukdyhQbcVWCYxM29mVDTgb6g5yzOSQPhe6xCJ17JgDIyjlTjYekS mLWJHDIe8XVta1a/x8eWfBmRmwZgh1cpQ/bgWQqlIQ==
X-Google-Smtp-Source: ALg8bN7e5/OC0JkL+r4reciTb4I1jDLB+tGzDHeyAe8UcKVrjpyfJpQZ4tFujAvV0B4BSGZL+JyJPi9nLPscdrpz7Gk=
X-Received: by 2002:a24:f30b:: with SMTP id t11mr7396578ith.40.1546899962891; Mon, 07 Jan 2019 14:26:02 -0800 (PST)
MIME-Version: 1.0
References: <44917fda8b414d45bed4cd40b1590b29@boeing.com>
In-Reply-To: <44917fda8b414d45bed4cd40b1590b29@boeing.com>
Reply-To: ek@loon.co
From: Erik Kline <ek@loon.co>
Date: Mon, 07 Jan 2019 14:25:51 -0800
Message-ID: <CAAedzxqk7xbrbXYce6izpDCv2YVv54e5ySV2sTYRYw7eFwCEMQ@mail.gmail.com>
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
Cc: "dmm@ietf.org" <dmm@ietf.org>, RTGWG <rtgwg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cb65ce057ee5b602"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/u6zv5cW-SFZ_01KYgSgRUOXvgzs>
Subject: Re: [DMM] BGP-based DMM for civil aviation
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2019 22:26:06 -0000

Fred,

Happy New Year.

I'm not currently tracking rtgwg, so perhaps this is already addressed in
discussion of there.  (And perhaps I should move dmm@ to bcc...)

How does a MNP-bearing node (client) locate candidate s-ASBRs (similarly
how does it locate a proxy)? And does the client try to form an eBGP
session with the s-ASBR or use something else?

I was also not clear on where administrative boundaries are in the various
diagrams (though I assumed at least that c-ASBRs are within the MSP-owners
administrative domain).

Thanks,
-Erik

On Wed, 2 Jan 2019 at 12:37, Templin (US), Fred L <Fred.L.Templin@boeing.com>
wrote:

> Hello, and Happy New Year,
>
> We have articulated what is essentially a Distributed Mobility Management
> (DMM)
> service for the next-generation civil aviation Aeronautical
> Telecommunications
> Network with Internet Protocol Services (ATN/IPS):
>
> https://datatracker.ietf.org/doc/draft-ietf-rtgwg-atn-bgp/
>
> This work tracks the progress of the International Civil Aviation
> Organization
> (ICAO), and is a working group item of the IETF RTGWG.
>
> The way it works is that there is a hub-and-spokes BGP overlay routing
> service
> that interconnects potentially many mobility anchor points. Each anchor
> point is
> responsible for mobility management for a constituent set of mobile nodes
> (e.g., aircraft), such that the system as a whole supports large-scale DMM.
>
> We think this document is in the correct home in RTGWG, but I just thought
> I would start out the year by sensitizing the DMM community. Any thoughts
> or comments are welcome.
>
> Thanks - Fred
> _______________________________________________
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm
>

v2.23.0 | Report a Bug | By Email