Re: [dtn-interest] Review for TCP CL

Simon Perreault <simon.perreault@viagenie.ca> Tue, 28 August 2012 17:25 UTC

Return-Path: <simon.perreault@viagenie.ca>
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 AE82C21F84F3 for <dtn-interest@ietfa.amsl.com>; Tue, 28 Aug 2012 10:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.535
X-Spam-Level:
X-Spam-Status: No, score=-2.535 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, NO_RELAYS=-0.001]
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 K2teHOgRaKgp for <dtn-interest@ietfa.amsl.com>; Tue, 28 Aug 2012 10:25:16 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id F1FEB21F84D4 for <dtn-interest@irtf.org>; Tue, 28 Aug 2012 10:25:15 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:f927:f074:2e02:9ab4]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 79F18425F0 for <dtn-interest@irtf.org>; Tue, 28 Aug 2012 13:25:14 -0400 (EDT)
Message-ID: <503CFEF9.5020403@viagenie.ca>
Date: Tue, 28 Aug 2012 13:25:13 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120717 Thunderbird/14.0
MIME-Version: 1.0
To: dtn-interest@irtf.org
References: <5EE81C5C4CFFF4418C5EAD12F49D64EE0674EDA9@IMCMBX01.MITRE.ORG>
In-Reply-To: <5EE81C5C4CFFF4418C5EAD12F49D64EE0674EDA9@IMCMBX01.MITRE.ORG>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Subject: Re: [dtn-interest] Review for TCP CL
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: Tue, 28 Aug 2012 17:25:16 -0000

Le 2012-08-28 10:35, Scott, Keith L. a écrit :
> Looks good.  A few quick comments:
>
> Section 1
>
> Second Paragraph
>
> "...(CLA) to send and receive bundles using an underlying internet
> protocol." -- This isn't quite true; the CLA can in fact use an
> underlying link (or even, I suppose, raw physical) service.  This IS
> brought out better in section 2.1 where the CLA '...sends and receives
> bundles utilizing the service of some 'native' link, network, or
> internet protocol.' Maybe Section1 paragraph2 could pretty much reflect
> this:
>
> "...(CLA) to send and receive bundles using the service of some 'native'
> link, network, or internet protocol."

ok, fixed.

> Third Paragraph
>
> "...the TCPCL reside above the transport layer, i.e., at the application
> layer."
>
>              Would you consider:
>
> "...the TCPCL reside above the transport layer of the Internet model,
> i.e., at the application layer."
>
> I think the figure does a good job of showing the relationship; but
> assigning BP to a 'layer' in the Internet model is always tricky and a
> little extra verbosity might help.

Per Vin't follow-up comment, I fixed that with: "In particular, when BP 
is using TCP as its bearer with TCPCL as its convergence layer, both BP 
and TCPCL reside at the application layer of the Internet model."

> Section 4.2
>
> "...the magic string is to provide a some protection..." -- '...a
> some...' needs fixing.

ok, fixed.

> The 'should' in 'This negotiation should proceed in the following
> manner:' should be SHOULD?

Actually it should be MUST because things will completely break if you 
don't follow this. I can't think of any exception case.

> "Bundle refusal to interrupt transmission of a bundle may only be used
> iff both peers indicate support for it in their contact header."
>
>              Maybe reword as:
>
> "The bundle refusal capability may only be used iff both peers..."
>
>              Or
>
> "The capability that allows a receiver to refuse reception of a bundle
> may only be used iff both peers..."

ok, fixed using your first suggestion.

> Authors' Addresses:
>
> Does somebody have a more recent address for Mike Demmer?

I don't...

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca