[dtn-interest] Review of draft-irtf-dtnrg-dgram-clayer-00

David Ros <David.Ros@telecom-bretagne.eu> Thu, 17 January 2013 14:05 UTC

Return-Path: <David.Ros@telecom-bretagne.eu>
X-Original-To: dtn-interest@ietfa.amsl.com
Delivered-To: dtn-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9CC221F862D; Thu, 17 Jan 2013 06:05:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, HELO_EQ_FR=0.35, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L6K3AuZTZER7; Thu, 17 Jan 2013 06:05:47 -0800 (PST)
Received: from zproxy220.enst-bretagne.fr (zproxy220.enst-bretagne.fr [192.108.117.9]) by ietfa.amsl.com (Postfix) with ESMTP id 9DA9D21F8640; Thu, 17 Jan 2013 06:05:45 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by zproxy220.enst-bretagne.fr (Postfix) with ESMTP id B374E34376; Thu, 17 Jan 2013 15:05:43 +0100 (CET)
X-Virus-Scanned: amavisd-new at zproxy220.enst-bretagne.fr
Received: from zproxy220.enst-bretagne.fr ([127.0.0.1]) by localhost (zproxy220.enst-bretagne.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25YyCwUKUcBH; Thu, 17 Jan 2013 15:05:43 +0100 (CET)
Received: from dhcp-salsa-i87.rennes.enst-bretagne.fr (dhcp-salsa-i87.rennes.enst-bretagne.fr [10.35.128.87]) by zproxy220.enst-bretagne.fr (Postfix) with ESMTPSA id 64CA834372; Thu, 17 Jan 2013 15:05:43 +0100 (CET)
From: David Ros <David.Ros@telecom-bretagne.eu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 17 Jan 2013 15:05:43 +0100
Message-Id: <8F7946F1-4FDD-48CE-97E1-54F6BD9931EB@telecom-bretagne.eu>
To: "irsg@irtf.org Steering Group" <irsg@irtf.org>
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
X-Mailman-Approved-At: Thu, 24 Jan 2013 08:06:42 -0800
Cc: dtn-interest@irtf.org
Subject: [dtn-interest] Review of draft-irtf-dtnrg-dgram-clayer-00
X-BeenThere: dtn-interest@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." <dtn-interest.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/dtn-interest>, <mailto:dtn-interest-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/dtn-interest>
List-Post: <mailto:dtn-interest@irtf.org>
List-Help: <mailto:dtn-interest-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/dtn-interest>, <mailto:dtn-interest-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jan 2013 14:05:48 -0000

Hi,

This is the IRSG review of draft-irtf-dtnrg-dgram-clayer-00 as per RFC 5743. This reviewer has only superficial knowledge of DTN and the Bundle and LTP protocols, hence, comments are essentially editorial.

The document describes the use of two datagram-based transport layer protocols, UDP and DCCP, for encapsulating and carrying Bundle and LTP protocol data over the Internet. The document is clear and easy to read.

Remarks / Nits:

- Some RFC 5743-required text is missing, e.g.:

	-- A statement in the abstract identifying the document as a product of the RG.
	-- A paragraph near the beginning (for example, in the introduction) describing the level of RG support for publication.

- The two following sentences seem to be in contradiction with each other:

	-- "the Bundle Protocol described in RFC 5050 [RFC5050], which
   provides __reliable__ transmission of application data blocks" (Section 1)

	and

	-- "the Bundle Protocol offers
   neither congestion control __nor reliability__" (Section 2, par. 2)

	(emphasis added)

- I suggest writing the expression "98%**10" in page 4 as "0.98**10" instead.

- Section 3.1: the acronym "CL" is used without prior (explicit) definition. Even if it's clear from the context what CL means, it wouldn't hurt to spell it out explicitly the first time it appears.

- Section 3.2: I guess it'd be better to write "Bundle" (uppercase B) when talking about the protocol itself? If so, this should be fixed in a few other places (e.g., Section 3.2.1).

- Section "Acknowledgements" is empty.

- Typos:

	-- page 3: /s/it's own/its own
	-- page 4: /s/ segements/segments
	-- page 6: /s/every LTP segments/every LTP segment
	-- page 7: /s/it's way/its way
	-- page 7: /s/it's behavior/its behavior
	-- page 8: /s/its resources/their resources


Best regards,

David.

=================================================================
David ROS
http://www.rennes.enst-bretagne.fr/~dros/

Deadlines really start to press a week or two after they pass. -- John Perry