Re: [Roll] useofrplinfo version 5

[Cenk Gündogan <[e-mail]>]

Hello Peter,

 > Other question: how does the last 6LR know that the next node is a 
not_Raf?

I would try to answer this question in the following way:

I expect routes that were found _not_ with RPL, but e.g. configured
manually or through any other mechanism to be marked somehow differently
than routes that were accumulated with DAOs.
How to mark routes "differently" seems to be implementation specific.
(but this information would be used to fill in the `E` flag of Transit 
Options
in DAOs later).

So, if a rpl router forwards a packet downwards (storing-mode), it somehow
needs to know whether the (dst;next-hop) pair in a forwarding table
is rpl-born or not. If it is not rpl-born, then the IPIP header
containing the RPI must be removed before continuing the forwarding process,
otherwise the IPIP+RPI is re-added and targeted to the next-hop.

You probably noticed that I used many "somehows" and generalized a lot 
in the text above,
but this process looks very blurry to me.
Any RPL veterans available to make things clearer?

Cenk

On 07/06/2016 02:14 PM, peter van der Stok wrote:
> Hi Authors,
>
> Below my review of the document.
>
> Although the subject is tedious, the draft looks important to me to 
> assure inter-operability between implementations
>
> This version was much more readable than the first one. So, I mostly 
> signal nits and typos.
> It is important that someone with more implementation experience also 
> carefully reviews the document to signal missing text.
>
> Below my comments,
>
> Peter
>
> ______________________________________________________________________________________ 
>
>
> Review of RPLinfo version 05.
> Intro, last line, change to: “… type 3 {RFC6554], an efficient 
> IP-in-IP technique, and use cases …”.
> Section 3, Figure 1 is not referred to in the text.
> Page 5: Reorder phrases: first the phrase “In the figure 2,…” followed 
> by the phrase “The numbers …”
> Page 5, line 3: leaf -> leafs
> Page 5, line 7: “is mentioned as well as” -> “is often named”
> Page 6, figure 3 is not referred to.
> Page 7, phrase 2, “This is a fundamental” -> “A fundamental”
> Page 8, line 8,”to add to remove” -> “to add or remove”
> Page 8, line 22, “In tables” -> “In table 1”
> Page 8, line 25, complete -> extensive
> Section 5, phrase 1 change to: “In storing mode (fully stateful), the 
> sender cannot determine whether the destination is RPL-capable and 
> thus ….”
> Section 5, line 9, indicates when (when to be added)
> Page 9, last line; don’t understand: “and are the RPL root node.”
> Page 10, line 6: remove: “in order to be able to”
> Section 5.2, line 3, insert -> inserts; send ->sends
> Section 5.3 and section 5.2: If the 6LBR does not know whether 
> destination is Raf or not_Raf in section 5.3, then this is also the 
> case in section 5.2. Question why is the IPv6-in-IPv6 header not also 
> used in section 5.2. The problem for the 6LBR is the same.
> The text in section 5.3 seems to suggest that at each 6LR the 
> IPv6-in-IPv6 is removed and then re-added again. I would expect the 
> row re-added headers be filled in under 6LR.
> Other question: how does the last 6LR know that the next node is a 
> not_Raf?
> Section 5.4: IP-in-IP is removed and re-added in 6LRs? This also 
> refers to the following sections 5.x
> Section 5.8 and section 5.6; same question as for section 5.3 and 
> section 5.2.
> Section 5.9, line 11, sending 6LN to (“6LN to” added)
> Section 5.10, line 4, remove “sends”
> Page 16, “Alternatively, …. Compress.” I miss a lot of context to 
> understand this paragraph.
> Section 5.11, line 5, addresses -> addressed
> Section 5.11, line 6, subject of “must send” misses.
> Section 5.12, The phrase “The IP-in-IP header must be addressed on a 
> hop-by-hop basis” suggests that the header is removed and re-inserted 
> at every hop. Nevertheless, that is not mentioned in the accompanying 
> table. This is the same question I have for earlier sections 5.x.
> Section 6.1, In the table, why does the 6LBR add RPI? 6LBR is the 
> destination!
> Section 6.2, “the traffic originates with an RPL aware node”. What do 
> you mean? 6LBR is RPL aware? The destination is known to 6LBR because 
> destination is RPL aware? Or something else?
> Section 6.3, My interpretation: In 6LBR the RH3 is added and modified 
> in each consecutive 6LR until it is fully consumed and removed in the 
> last 6LR.
> Section 6.3, You cite several alternatives. I suggest to only mention 
> the solution without RPI.
> Section 6.5, line 3, remoted -> removed
> Identical to storing mode case (please mention section).
> Section 6.6 same remark about RPI as section 6.3
> Sections 6.7 – 6.12, Here you use 6LN for not-RPL aware node, while in 
> earlier section 6.x you use IPv6 node. Why?
> Section 7.1, line 6, stiaution -> approach
> Section 7.1, line 10; what is a “single code path”?
> Section 7.2, line 1, This -> In
> Section 7.2 line 3, all DODAG nodes, (added DODAG)
> Section 7.2, line 12, “intermediate 6LN nodes” should be “intermediate 
> IPv6 nodes”? If not, I don’t understand the phrase.
> Section 7.2, line 20, there are -> there is
>
>