"Velt, R. (Ronald) in 't" <Ronald.intVelt@tno.nl> Thu, 22 May 2014 19:28 UTC
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E95611A01E1 for <firstname.lastname@example.org>; Thu, 22 May 2014 12:28:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Status: No, score=1.443 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RP_MATCHES_RCVD=-0.651] autolearn=no
Received: from mail.ietf.org ([184.108.40.206]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CfeTZ1ubMFHV for <email@example.com>; Thu, 22 May 2014 12:28:15 -0700 (PDT)
Received: from fromintouta.tno.nl (fromintouta.tno.nl [220.127.116.11]) by ietfa.amsl.com (Postfix) with ESMTP id 2B0601A02EA for <firstname.lastname@example.org>; Thu, 22 May 2014 12:28:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.98,888,1392159600"; d="scan'208";a="25989292"
Received: from unknown (HELO mail.tno.nl) ([18.104.22.168]) by mailhost1a.tno.nl with ESMTP; 22 May 2014 21:28:10 +0200
Received: from EXC-MBX03.tsn.tno.nl ([fe80::e969:1300:fb9f:7e12]) by EXC-CASHUB02.tsn.tno.nl ([fe80::8c02:de2a:3094:171%14]) with mapi id 14.03.0174.001; Thu, 22 May 2014 21:28:10 +0200
From: "Velt, R. (Ronald) in 't" <Ronald.intVelt@tno.nl>
To: "email@example.com" <firstname.lastname@example.org>
Date: Thu, 22 May 2014 19:28:09 +0000
Accept-Language: en-US, nl-NL
Content-Type: text/plain; charset="us-ascii"
Subject: [dtn-interest] TCPCL
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:email@example.com?subject=unsubscribe>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/dtn-interest>, <mailto:firstname.lastname@example.org?subject=subscribe>
X-List-Received-Date: Thu, 22 May 2014 19:28:17 -0000
Hi, The Delay Tolerant Networking TCP Convergence Layer Protocol I-D (draft-irtf-dtnrg-tcp-clayer-09) has been with the RFC Editor for a while and is now in AUTH48 state. It may, therefore, be a tad late for comments, even if they are fairly minor ones. But perhaps not entirely too late. Maybe some of the perceived flaws mentioned below can, if confirmed, still be repaired. - Page 3, 2nd paragraph: "Bundling Protocol" should be "Bundle Protocol" - Page 5, item "Connection Parameters": "Section Section 4.2" should be "Section 4.2" (Probably already detected and dealt with by the RFC Editor) - Page 8, Figure 2, left-side part of the figure, under node A: * 1st DATA_SEGMENT: "Bundle Data 0..L1" should be "Bundle Data 0..(L1 - 1)" * 2nd DATA_SEGMENT: "Bundle Data L1..L2" should be "Bundle Data L1..(L1 + L2 - 1)" * 3rd DATA_SEGMENT: "Bundle Data L2..L3" should be "Bundle Data (L1 + L2)..(L1 + L2 + L3 - 1)" - Page 11, Section 4.2: The fourth paragraph of this section and following indented part discusses the effect of Contact Header Flags on parameter negotiation, but makes no mention of the LENGTH flag. The reader is kept in the dark w.r.t. the interpretation of this flag until section 5.5. For the sake of completeness, it could be stated that there is no parameter negotiation associated with the sending of LENGTH messages. - Page 14, 2nd paragraph, last sentence: Is this really stating that if a node is able to receive a segment of arbitrary size, then it MUST be able to receive segments of any size up to and including the bundle size? Or is the intended meaning that if a node is able to receive a segment of a certain size, it MUST be able to receive smaller segments as well? (In which case the "<= X" at the end of the sentence should be "<= Y"). (Not sure about this one!!) - Page 17,second paragraph under Figure 7, last sentence: "The receiver MUST be prepared for this ..." should be "The sender MUST be prepared for this ..." (I.e., the _sender_ of the LENGTH message and subsequent DATA_SEGMENT message, when _receiving_ a BUNDLE_REFUSE message). - Page 17, section 5.6, third paragraph: "(as described in Table2, ..." => closing parenthesis missing. (Probably already detected and dealt with by the RFC Editor) - Throughout the document: a quantity of 8 bits is alternatingly referred to as "byte" or "octet". It would be better to pick one or the other and use the chosen term consistently. Thanks, Ronald in 't Velt Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. TNO aanvaardt geen aansprakelijkheid voor de inhoud van deze e-mail, de wijze waarop u deze gebruikt en voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages.