Re: [dtn] [EXTERNAL] Alexey Melnikov's Discuss on draft-ietf-dtn-bpbis-22: (with DISCUSS and COMMENT)

"Burleigh, Scott C (US 312B)" <scott.c.burleigh@jpl.nasa.gov> Mon, 10 February 2020 17:08 UTC

Return-Path: <scott.c.burleigh@jpl.nasa.gov>
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 BD08E12080C; Mon, 10 Feb 2020 09:08:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 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_MED=-2.3, 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=jpl.nasa.gov
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 VnDpqNkEpdCj; Mon, 10 Feb 2020 09:08:23 -0800 (PST)
Received: from ppa02.jpl.nasa.gov (ppa02.jpl.nasa.gov [128.149.137.113]) (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 D3674120808; Mon, 10 Feb 2020 09:08:23 -0800 (PST)
Received: from pps.filterd (ppa02.jpl.nasa.gov [127.0.0.1]) by ppa02.jpl.nasa.gov (8.16.0.27/8.16.0.27) with SMTP id 01AH577J141393; Mon, 10 Feb 2020 09:08:15 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jpl.nasa.gov; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=InSight1906; bh=3CMx9SSo3f5miNORUCUs3EWDRpA+2Q3Fim0dYwEby48=; b=GOSrcxvO4dvDvDS0zSP+6Nn8gfwvPhOgBFE+E5rfVSpFjgSphCnyWAismK8/gGucacQ7 XUFR492TnBYAEnawPajkpfxq/Cmod8umRimgNDFmoB5vh1ayXcVZeVhHxSwkEcmurN08 yLbj6YEwyQr7EDKqViLtGIFBsENh2828wtabCOzBREMe99Tw7X8WviGWo2UZtJvx9QJ7 8v+BRuxKzt2T9J3iOPmPD+QjnR5YbC2nDxpevvexX+mf5AJbsjrh+BnUd0R7p6OV1Zp6 zixw+QikZOuNcmmPMqL8EZNdrlB1tknOUPk+XK55yr1rlznBdTJhlFCOAvein4hlzPts Vg==
Received: from mail.jpl.nasa.gov (altphysenclup02.jpl.nasa.gov [128.149.137.53]) by ppa02.jpl.nasa.gov with ESMTP id 2y1w1wwjfd-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 10 Feb 2020 09:08:15 -0800
Received: from ap-embx16-sp30.RES.AD.JPL (ap-embx16-sp30.jpl.nasa.gov [128.149.137.85]) by smtp.jpl.nasa.gov (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id 01AH8EZX010238 (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128 bits) verified FAIL); Mon, 10 Feb 2020 09:08:14 -0800
Received: from ap-embx16-sp10.RES.AD.JPL (2002:8095:8953::8095:8953) by ap-embx16-sp30.RES.AD.JPL (2002:8095:8955::8095:8955) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Mon, 10 Feb 2020 09:08:14 -0800
Received: from ap-embx16-sp10.RES.AD.JPL ([fe80::4:f430:47b5:767b]) by ap-embx16-sp10.RES.AD.JPL ([fe80::4:f430:47b5:767b%17]) with mapi id 15.01.1591.008; Mon, 10 Feb 2020 09:08:13 -0800
From: "Burleigh, Scott C (US 312B)" <scott.c.burleigh@jpl.nasa.gov>
To: Alexey Melnikov <aamelnikov@fastmail.fm>, The IESG <iesg@ietf.org>
CC: "draft-ietf-dtn-bpbis@ietf.org" <draft-ietf-dtn-bpbis@ietf.org>, "Fred Templin" <fred.l.templin@boeing.com>, "dtn-chairs@ietf.org" <dtn-chairs@ietf.org>, "dtn@ietf.org" <dtn@ietf.org>, Benjamin Schwartz <bemasc@google.com>
Thread-Topic: [EXTERNAL] Alexey Melnikov's Discuss on draft-ietf-dtn-bpbis-22: (with DISCUSS and COMMENT)
Thread-Index: AQHV3cAf/EV+zd5l1kmkJpo2T1jPyKgP4JaQgACrUoD//4PDAIAEyFUA///VFjA=
Date: Mon, 10 Feb 2020 17:08:13 +0000
Message-ID: <d1941a6c0e344ea48a4a8a9bf1aaea12@jpl.nasa.gov>
References: <158108452583.11606.5428367878223035583.idtracker@ietfa.amsl.com> <b77a3734d0ae427c920962e438c16a60@jpl.nasa.gov> <32b82572-64ad-4b22-b4bc-9c2dd779172d@www.fastmail.com> <00dfa2dda9b344ebbd87705b34e74a79@jpl.nasa.gov> <cf2df2e0-7c28-40f5-8b7e-62877fb54668@www.fastmail.com>
In-Reply-To: <cf2df2e0-7c28-40f5-8b7e-62877fb54668@www.fastmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [207.151.104.72]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Source-IP: ap-embx16-sp30.jpl.nasa.gov [128.149.137.85]
X-Source-Sender: scott.c.burleigh@jpl.nasa.gov
X-AUTH: Authorized
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2020-02-10_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=873 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1911140001 definitions=main-2002100129
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/2TAoyk9QzkkJXO5xYpXzRxm9gtc>
Subject: Re: [dtn] [EXTERNAL] Alexey Melnikov's Discuss on draft-ietf-dtn-bpbis-22: (with DISCUSS and COMMENT)
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 17:08:26 -0000

Thanks, Alexey.  I would expect an implementer who is coding section 5.9 of the spec would normally read section 5.8 as well, but maybe not.  I will gladly add some clarifying text in the Reassembly section as well.

Scott

-----Original Message-----
From: Alexey Melnikov <aamelnikov@fastmail.fm> 
Sent: Monday, February 10, 2020 3:39 AM
To: Burleigh, Scott C (US 312B) <scott.c.burleigh@jpl.nasa.gov>ov>; The IESG <iesg@ietf.org>
Cc: draft-ietf-dtn-bpbis@ietf.org; Fred Templin <fred.l.templin@boeing.com>om>; dtn-chairs@ietf.org; dtn@ietf.org; Benjamin Schwartz <bemasc@google.com>
Subject: Re: [EXTERNAL] Alexey Melnikov's Discuss on draft-ietf-dtn-bpbis-22: (with DISCUSS and COMMENT)

Hi Scott,
Quickly replying to a single issue:

On Sat, Feb 8, 2020, at 12:45 AM, Burleigh, Scott C (US 312B) wrote:
> > ## Section 5.8
> > 
> > Clarity: The insistence, here and earlier, that a bundle is only 
> > fragmented into two packets, and that this can then be performed 
> > recursively, seems unhelpful.  Bundles can be fragmented into 
> > arbitrarily many pieces, and this binary subdivision concept is not 
> > actually present in the protocol.  I suggest removing it from the 
> > text as well.
> > 
> > 		Why is this unhelpful?  It's the formal procedure by which bundles 
> > are fragmented.  Let's not remove it.
> 
> I think saying that a bundle can only be fragmented into 2 pieces is a 
> lie, because the algorithm says that it can be fragmented into more 
> than 2. I found this text to be confusing as well. Just say that it 
> can be fragmented into 2 or more non overlapping fragments.
> 
> 	***	It is absolutely not a lie.  A bundle can be fragmented into 
> exactly 2 pieces, each of which is a bundle.  There is no defined 
> mechanism for fragmenting a single 		bundle into 3 pieces, or 4, other 
> than the recursive exercise of the binary fragmentation mechanism 
> defined in detail in section 5.8.  But I will try to make this
> 		clearer in the text.

Think of it from the point of view of a receiving system: if there were several nodes before it, it can't rely on only being 2 fragments, it has to expect arbitrary number of them.

So the text you have is possibly helpful for the sending system, but not for the receiving one.

Best Regards,
Alexey