Re: [TERNLI] Request for review -NiTS rev -07

Gorry Fairhurst <> Thu, 15 February 2007 10:17 UTC

Received: from [] ( by with esmtp (Exim 4.43) id 1HHdgN-0005oR-Pf; Thu, 15 Feb 2007 05:17:43 -0500
Received: from [] ( by with esmtp (Exim 4.43) id 1HHdgL-0005nl-TV; Thu, 15 Feb 2007 05:17:41 -0500
Received: from [2001:630:241:204:203:baff:fe9a:8c9b] ( by with esmtp (Exim 4.43) id 1HHdgK-0001lu-Bz; Thu, 15 Feb 2007 05:17:41 -0500
Received: from [] ( []) by (8.13.4/8.13.4) with ESMTP id l1FAHGwG022020; Thu, 15 Feb 2007 10:17:16 GMT
Message-ID: <>
Date: Thu, 15 Feb 2007 10:19:59 +0000
From: Gorry Fairhurst <>
Organization: University of Aberdeen, UK
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bernard Aboba <>
Subject: Re: [TERNLI] Request for review -NiTS rev -07
References: <>
In-Reply-To: <>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-Spam-Status: No
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport-Enhancing Refinements to the Network Layer Interface <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>

Here are some NiTs to be considered by the authors in their next revison,

Best wishes,


Bernard Aboba wrote:

> The IAB is considering publication of "Architectural Implications of Link 
> Indications", and would interested in feedback from the transport 
> community. 
> The latest version of the document can be found here prior to appearance 
> on the I-D archive:
> Feedback can be sent to 


1.1 Routable Address
     /In this specification, the term "routable address" refers to any
      IPv4 address other than an IPv4 Link-Local address./
- Why so IPv4 centric?
- I don't see why the discussion in the document does not also relate to
IPv6 addresses, and if we can we should make general guidance for IP,
rather than version-specific guidance, please provide IPv6 reference.
- Many of the later examples are taken from IPv4, which is fine, but it
would be good to see up-front that these issues also apply to IPv6 
(which they seem to).
/characteristics which/
should be:
/characteristics that/
/Link indication/
should be:
/Link Indication/
/Operable address/
should be:
/Operable Address/
/Routable address/
should be:
/Routable Address/
/In this specification,/
- In this document? - this is not a protocol spec.
/sent out an interface/
- The English here does not read well for a british reader, could this be
"by an interface"?
/sent on an outgoing interface/
Section 1.4.1
/indications may not result in a/
- can be misread by some English-speaking readers as MUST NOT...
I suggest:
/indications do not necessarily result in a/
    /Link indications such
    "Link Up"/"Link Down" or changes in rate/
- insert "as" after "such".
Section 1.4.2 Transport Layer
/bottleneck bandwidth is already/
- It's not clear which bottleneck here.
should be:
/bandwidth of the bottleneck on the end-to-end path is already/
1.4.2.  Transport Layer
- I prefer adding the word "received"
/The Transport layer processes link indications differently for/
Could it be:
/The Transport layer processes received link indications differently for/
Section 2.1
/avoid use of link models/
- insert 'the'
/avoid the use of link models/
Section 2.3.2,
/The problem was caused by an invalid /
- This paragraph break seems to be wrong - perhaps this is part of the
previous para?
Section 2.6
/   Duplicate Address Detection (DAD)./
- cite?
[RFC4429] Moore, N., "Optimistic Duplicate Address Detection (DAD) for
IPv6", RFC 4429, April 2006.
Section 2.7
/  transport parameters for the original interface (MTU, congestion state)/
- the MSS (derived from link MTU, or PMTU)...
A.1.2 Smart Link Layer Proposals

Consider adding?:

    [RFC3366] provides advice to the designers of digital
    communication equipment and link-layer protocols employing link-layer
    Automatic Repeat reQuest (ARQ) techniques for IP. It discusses the use
    of ARQ, timers, persistency in retransmission and the challenges that
    arise from sharing links between multiple flows and in differentiation
    transport flow requirements.