IETF Logo Mail Archive

RE: Tsvart early review of draft-ietf-rtgwg-atn-bgp-13

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Mon, 14 February 2022 18:00 UTC

Return-Path: <Fred.L.Templin@boeing.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 E23863A089F; Mon, 14 Feb 2022 10:00:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.099
X-Spam-Level:
X-Spam-Status: No, score=-7.099 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, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=boeing.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 esiRPeTxIUnY; Mon, 14 Feb 2022 10:00:47 -0800 (PST)
Received: from clt-mbsout-01.mbs.boeing.net (clt-mbsout-01.mbs.boeing.net [130.76.144.162]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD7143A07B5; Mon, 14 Feb 2022 10:00:44 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 21EI0eig010884; Mon, 14 Feb 2022 13:00:42 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1644861643; bh=ivkuD14i/mM0RoEdTuH9IpXHnoHca8450A+hj/GrmVM=; h=From:To:CC:Subject:Date:From; b=upveqnVjOCAM26FoiZR5aUd4Wfom4qbxa94Gytqv71o/OFjaxVQgPtJrcR9l/u+pA EPYbseLRCFZR1jHEsWshalKUNP5Qv1EUlTfWCqskokrbZu7RXTE2ucCubsRICC4OFm mhyuFVwgWyXmTNFCjsbDgge8FAA0GJmILNIrDc4lRI74L3gPZTjKuu+NqcFPoFoJxX P+ZaNVpr6MAvwYVL1kjONWobvBTI2f4Fd3oMmNyHyQQiEtWIink0lhr/ocAzvvUWRh 0E7JFTw9eh50+KZOIW9s/Q59N+XqyWXHJ5VQmEquejeI6mSlh8NQgcHdR4PVpEemr5 0tLpc02GaW6kg==
Received: from XCH16-07-10.nos.boeing.com (xch16-07-10.nos.boeing.com [144.115.66.112]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 21EI0YPv010772 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 14 Feb 2022 13:00:34 -0500
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-10.nos.boeing.com (144.115.66.112) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2375.18; Mon, 14 Feb 2022 10:00:33 -0800
Received: from XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8]) by XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8%2]) with mapi id 15.01.2375.018; Mon, 14 Feb 2022 10:00:33 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Michael Tüxen <tuexen@fh-muenster.de>, "tsv-art@ietf.org" <tsv-art@ietf.org>, "int-dir@ietf.org" <int-dir@ietf.org>, IETF SecDir <secdir@ietf.org>, "ops-dir@ietf.org" <ops-dir@ietf.org>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>
CC: "draft-ietf-rtgwg-atn-bgp.all@ietf.org" <draft-ietf-rtgwg-atn-bgp.all@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: Tsvart early review of draft-ietf-rtgwg-atn-bgp-13
Thread-Topic: Tsvart early review of draft-ietf-rtgwg-atn-bgp-13
Thread-Index: Adghy5/WpRmMiAyBQPiv/EhXVQAz0Q==
Date: Mon, 14 Feb 2022 18:00:33 +0000
Message-ID: <6de3a2c362904d8883dd719ea9f13efc@boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: 2C51A66FD559329D9C1AD66410996E4892EDA1CAA05A87E42295CC96F121415E2000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/TWD5-dOIVfO2dQTSuYHtOPOZjS0>
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: Mon, 14 Feb 2022 18:00:53 -0000

Michael, I felt addressing your comment was important enough to warrant a new
draft update:

https://datatracker.ietf.org/doc/draft-ietf-rtgwg-atn-bgp/

In the process, I also added a new figure in the introduction as recommended
by another reviewer who correctly pointed out that a figure would make the
document easier to understand.

Thanks to all for the comments,

Fred

> -----Original Message-----
> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Michael Tüxen via Datatracker
> Sent: Friday, February 11, 2022 12:23 PM
> To: tsv-art@ietf.org
> Cc: draft-ietf-rtgwg-atn-bgp.all@ietf.org; rtgwg@ietf.org
> Subject: [EXTERNAL] Tsvart early review of draft-ietf-rtgwg-atn-bgp-13
> 
> EXT email: be mindful of links/attachments.
> 
> 
> 
> Reviewer: Michael Tüxen
> Review result: Ready
> 
> The document mentions that some data links used by aircrafts today only provide
> a bandwidth in the order of 32 Kbps. Any protocols using these links should be
> parametrised for that bandwidth and parametrisation might not be the default
> one used in todays links used in the Internet. However, if I understand the
> document correctly, the BGP communication described in this document is not
> using these links and therefore I see no issues with respect to transport
> protocol considerations.
> 
> 
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg

v2.23.0 | Report a Bug | By Email