IETF Logo Mail Archive

Re: [dtn] Various IESG "DISCUSS" positions on draft-ietf-dtn-*

"Taylor, Rick" <rick.taylor@airbus.com> Mon, 10 February 2020 10:30 UTC

Return-Path: <rick.taylor@airbus.com>
X-Original-To: dtn@ietfa.amsl.com
Delivered-To: dtn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C72212011E; Mon, 10 Feb 2020 02:30:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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=airbus.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 AlZMgOwpe0fe; Mon, 10 Feb 2020 02:30:01 -0800 (PST)
Received: from mx1.myeers.net (mx1.myeers.net [87.190.7.230]) (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 4AA8F120123; Mon, 10 Feb 2020 02:29:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=airbus.com; i=@airbus.com; l=3404; q=dns/txt; s=eers-ng2048; t=1581330601; x=1612866601; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version:content-transfer-encoding; z=From:=20"Taylor,=20Rick"=20<rick.taylor@airbus.com>|To: =20"R.=20Atkinson"=20<rja.lists@gmail.com>,=20"dtn@ietf.o rg"=20<dtn@ietf.org>|CC:=20"iesg@ietf.org"=20<iesg@ietf.o rg>|Subject:=20RE:=20[dtn]=20Various=20IESG=20"DISCUSS" =20positions=20on=20draft-ietf-dtn-*|Date:=20Mon,=2010=20 Feb=202020=2010:29:07=20+0000|Message-ID:=20<8d8d9a6d24f6 4c7a8a5c6691d09c17fb@CD1-4BDAG04-P04.cdmail.common.airbus ds.corp>|References:=20<302D5B48-16CB-410D-9E0A-2D4EA38C3 6D7@gmail.com>|In-Reply-To:=20<302D5B48-16CB-410D-9E0A-2D 4EA38C36D7@gmail.com>|MIME-Version:=201.0 |Content-Transfer-Encoding:=20base64; bh=Gp0914MyMBEL0nX2RprMc9Mi3+R8tsvfo0sIszLzCsw=; b=dYoS9kfLIuXfw6j4KoADTwffE8CARTbex4SrXWiiwZdb0KeAs1Ds2vNs D/OsBHUfYHo9+plwndC2cD5ea+ve3KPVlSQvt0dpy7Qh9Nhz8dp9RO7Cl khth5xqNJ3uVCqxucXysrruch+DS7VvoueK3y/NaYIB9Nv7cbN/Y/cj0A lhkFZ5Fb0uvKlkHdYAeFgIb2N+A/S9yNp9/1sKOFn5IGWfGBaX8KzCn1g VwU9yR/2w7uXzeaZdAYKAohENHR5gV6aNiRzmwgN2lOuqKqHFlQSsapqZ 8Ip7USUgW4OH7XN2fk11e/vqtj7nlNnF6R+hJQq8h59BXeZ7mQ4UY5ybS A==;
X-IronPort-AV: E=Sophos;i="5.70,424,1574118000"; d="scan'208";a="128909442"
Received: from ec2-44-225-67-170.us-west-2.compute.amazonaws.com (HELO DE0-03HUB-P01.central.mail.corp) ([44.225.67.170]) by de0-03iro-p01-out.myeers.net with ESMTP/TLS/AES256-SHA; 10 Feb 2020 11:29:26 +0100
Received: from esa2e.demail.de.airbusds.corp (10.67.144.34) by DE0-03HUB-P01.central.mail.corp (44.225.67.172) with Microsoft SMTP Server id 15.0.1497.2; Mon, 10 Feb 2020 11:29:23 +0100
Received: from unknown (HELO CD1-4DDAG04-P02.cdmail.common.airbusds.corp) ([10.67.164.152]) by esa2i.demail.de.airbusds.corp with ESMTP; 10 Feb 2020 11:29:07 +0100
Received: from CD1-4BDAG04-P04.cdmail.common.airbusds.corp (10.67.164.149) by CD1-4DDAG04-P02.cdmail.common.airbusds.corp (10.67.164.152) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 10 Feb 2020 11:29:07 +0100
Received: from CD1-4BDAG04-P04.cdmail.common.airbusds.corp ([10.67.164.149]) by CD1-4BDAG04-P04.cdmail.common.airbusds.corp ([10.67.164.149]) with mapi id 15.00.1473.003; Mon, 10 Feb 2020 11:29:07 +0100
From: "Taylor, Rick" <rick.taylor@airbus.com>
To: "R. Atkinson" <rja.lists@gmail.com>, "dtn@ietf.org" <dtn@ietf.org>
CC: "iesg@ietf.org" <iesg@ietf.org>
Thread-Topic: [dtn] Various IESG "DISCUSS" positions on draft-ietf-dtn-*
Thread-Index: AQHV3rLXGspW9h0CWUu2MFr3aki/ZagUPBTw
Date: Mon, 10 Feb 2020 10:29:07 +0000
Message-ID: <8d8d9a6d24f64c7a8a5c6691d09c17fb@CD1-4BDAG04-P04.cdmail.common.airbusds.corp>
References: <302D5B48-16CB-410D-9E0A-2D4EA38C36D7@gmail.com>
In-Reply-To: <302D5B48-16CB-410D-9E0A-2D4EA38C36D7@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-bromium-msgid: 356e6d1a-2239-43a6-b293-45be3747da26
dlp-product: dlpe-windows
dlp-version: 11.3.2.8
dlp-reaction: no-action
x-titus_label: N
x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiIyIsImlkIjoiNjEwOTBjNjUtNDlkMi00OTI5LThjYzMtYjg5ZTcwNDA3MjIwIiwicHJvcHMiOlt7Im4iOiJMQUJFTCIsInZhbHMiOlt7InZhbHVlIjoiTiJ9XX0seyJuIjoiRGVDIiwidmFscyI6W119LHsibiI6IkwxIiwidmFscyI6W119LHsibiI6IkwyIiwidmFscyI6W119LHsibiI6IkwzIiwidmFscyI6W119LHsibiI6IkNDQVYiLCJ2YWxzIjpbXX0seyJuIjoiTDQiLCJ2YWxzIjpbXX0seyJuIjoiVEJDMSIsInZhbHMiOltdfSx7Im4iOiJUQkMyIiwidmFscyI6W119LHsibiI6IlRCQzMiLCJ2YWxzIjpbXX0seyJuIjoiRUNGIiwidmFscyI6W3sidmFsdWUiOiJOIn1dfSx7Im4iOiJKdXN0aWZpY2F0aW9uUmVhc29uIiwidmFscyI6W3sidmFsdWUiOiIifV19XX0sIlN1YmplY3RMYWJlbHMiOltdLCJUTUNWZXJzaW9uIjoiMTguMS4xOTAyLjE0MCIsIlRydXN0ZWRMYWJlbEhhc2giOiJSUExueWpSUWx2SUROWktjNmdUOHNsc3FvOEt6QlhubHBaTmZNMk9aK3NnVW16MXdiVTNRZWZWT3VsR3RoXC9kOCJ9
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
X-TM-SNTS-SMTP: D76AB0BFB3D546B1ADFA71D31F5717CA597641465DC5A4A57815E20FECB5D1C52000:8
X-GM-Security: forwarded
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/Jp5vWxTPjAzfaHNtKyzUMVjCg-w>
Subject: Re: [dtn] Various IESG "DISCUSS" positions on draft-ietf-dtn-*
X-BeenThere: dtn@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Delay Tolerant Networking \(DTN\) discussion list at the IETF." <dtn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtn>, <mailto:dtn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtn/>
List-Post: <mailto:dtn@ietf.org>
List-Help: <mailto:dtn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtn>, <mailto:dtn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Feb 2020 10:30:03 -0000

Hi Ran,

You make a very valid point.  Can I reach out to the authors in advance of Vancouver, to request that they perhaps present a short piece on what last minute changes have gone in.

Of course, any summaries to the list would be great as well, but I understand it is still a little bit of a moving target.

Cheers,

Rick Taylor

-----Original Message-----
From: dtn [mailto:dtn-bounces@ietf.org] On Behalf Of R. Atkinson
Sent: Saturday, February 8, 2020 7:05 PM
To: dtn@ietf.org
Cc: iesg@ietf.org
Subject: [dtn] Various IESG "DISCUSS" positions on draft-ietf-dtn-*


All,

It is great to see such rapid email list responses answering various questions and seeking to address concerns on various topics — from various IESG members.

I am concerned that we all keep in mind that implementers will be working from the final RFCs — and in many cases will NOT be reading these email responses.

If something is unclear or unexplained in an I-D and an explanation was needed to resolve one of the IESG member’s concerns, then IMHO that should result in the I-D editors/authors editing the relevant I-Ds to embed those clarifications inside the final RFC which WILL be referenced by implementers.

Purely as an example, if there is existing practice of using static routes or using some external specification, the practice ought to be documented and any applicable external specification ought to be both mentioned in the I-D (at least briefly) and also cited.  That way the reader won’t be left wondering how BP possibly could be deployed to the ISS or elsewhere.

Just 2 cents from the peanut gallery. :-)

Cheers,

Ran

_______________________________________________
dtn mailing list
dtn@ietf.org
https://www.ietf.org/mailman/listinfo/dtn
This email and its attachments may contain confidential and/or privileged information.  If you have received them in error you must not use, copy or disclose their content to any person.  Please notify the sender immediately and then delete this email from your system.  This e-mail has been scanned for viruses, but it is the responsibility of the recipient to conduct their own security measures. Airbus Operations Limited is not liable for any loss or damage arising from the receipt or use of this e-mail.

Airbus Operations Limited, a company registered in England and Wales, registration number, 3468788.  Registered office:  Pegasus House, Aerospace Avenue, Filton, Bristol, BS34 7PA, UK.

v2.23.0 | Report a Bug | By Email