Responses inline below.
Pascal Thubert (pthubert) <[email protected]> wrote:
> The title implies the document specifies a forwarding mechanism, but
> it does not, it merely provides discussion of two mechanisms in other
> docs (RFC 4944 and draft-ietf-lwig-6lowpan-virtual-reassembly). I
> would recommend at least changing the title to be more clear as to the
> purpose of the doc.
A suggestion would help : )
Does "On Forwarding 6LoWPAN Fragments over a Multihop IPv6 Network" go the
right way?
Sure. Other possibilities in case you like them better than that one:
· “6LoWPAN Fragment Forwarding Techniques: Discussion and Tradeoffs”
· “An Analysis of Various 6LoWPAN Fragment Forwarding Mechanisms”
Etc.
> Technical confusion
> -------------------
> 1) Page 3 says the reassembly buffer contains "the link-layer address
> that node B uses to forward the
> fragments". I cannot tell whether this is referring to B's link-layer
> address that it received the fragment on, or B's link-layer address that it
> uses as a source link-layer address for forwarding it on, or the link-layer
> address of the next hop to which B forwards.
The latter. B needs to send all the fragments with the same source link-layer
address because that's part of the index for the datagram in C. Proposed change:
"
the Link-Layer address that node B uses as source to forward the fragments
"
Ok
> 2) Page 3 also says the reassembly buffer contains "the link-layer
> address of the next hop that is resolved
> on the first fragment". I found this similarly confusing. What does it
> mean to resolve something "on" the first fragment? Does it mean "during
> processing of the first fragment"? Maybe I missed it, but I couldn't find
> in RFC 4944 anywhere that says that it would do next-hop resolution before
> the datagram can be reassembled. That would seem like a waste, if the
> fragments are then discarded (e.g., due to timer expiry) without actually
> doing any forwarding.
>
RFC 4944 reassembles and then routes. We make the routing decision on the first
fragment before we receive the second fragment, forward the first fragment and
store that state. Unsure how to reword, your suggestion would be appreciated.
When you say “We made”, who is “we”? RFC 4944? If so, cite a specific section,
since making the routing decision on receipt of the first fragment, rather than
the last,
seems non-intuitive and wasteful. If that’s what the RFC says, then you can
point it out
since this doc is (from my understanding) about discussing issues and tradeoffs
with other mechanisms.
The waste is that if you choose to discard the datagram rather than forward it,
your efforts in doing the lookup are a waste of cycles, and a waste of space to
store the result.
If you have a constrained node where every byte of storage is precious, having
to store another
link-layer address can be burdensome, as opposed to a mechanism that only does
the lookup
post reassembly, and has no such storage requirements, thus is lighter weight
and arguably
better for constrained nodes.
I would encourage adding such discussion into this doc.
> 5) Section 3 explains that "the first fragment must always be
> forwarded first", but does not explain
> what the behavior is if a fragment other than the first fragment is
> received
> before the first fragment. Figure 1 shows that the fragments can be
> received
> out of order, since there fragment 6 is received before 5, which is
> received
> before 4. Presumably it is either queued or dropped. If it's queued,
> then
> section 4 is insufficient, which talks about an attacker generating a large
> number of bogus "fragment 1" fragments, since if you queue the first
> fragment received even if it's not "fragment 1", then the same attack
> presumably exists, it's not specific to "fragment 1" packets.
>
6LoWPAN does not mandate that all the fragments are sent in order, thus Fig1.
But fragment 1 is sent first Quoting section 5.5 of Rfc 4944 "
The first
link fragment
SHALL contain the first fragment header as defined below.
1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1 1 0 0 0| datagram_size | datagram_tag |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: First Fragment
The second and subsequent link fragments (up to and including the
last) SHALL contain a fragmentation header that conforms to the
format shown below.
1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1 1 1 0 0| datagram_size | datagram_tag |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|datagram_offset|
+-+-+-+-+-+-+-+-+
Figure 5: Subsequent Fragments "
The first fragment is the one with the IPv6 address of the destination that
enables to find the next hop that the other fragments will use. So it is always
available before a fragment can be forwarded. So it is easy to mandate that we
forward it first.
The text we’re discussing is about the order of receipt, not the order in which
they are sent.
Even if it’s forwarded first, it does not mean it was received first (e.g.,
whether due to packet loss
or whatever other reason).
If we do that then the only way for a next fragment to arrive first is that the
first fragment was lost in the transmission by the previous node. The first
fragment may be queued for retries in the previous hop but that's a really bad
idea.
Regarding “that’s a really bad idea”… if this draft is the one discussing
tradeoffs and variations, then perhaps
it should explain why “that’s a really bad idea”.
Proposal:
* we add text on the above to clarify
* we mandate that on a link with ARQ, the node only forwards a next fragment if
the first was acknowledged.
* we clarify that a next fragment that is received with no state from a first
fragment for that datagram should be dropped.
If by “clarify”, you mean by reference to normative text in the RFC that
specifies it, then ok.
[…]
> Abstract has "to the virtual Reassembly Buffer", which seems incorrect
> both in terms of capitalization (since sectoin 3 has VRB) and grammar.
> Suggest "to using virtual reassembly buffers".
I think we meant to the VRB draft. Applied your recommendation in the meantime:
"
This method reduces the latency and increases end-to-end reliability in
route-over forwarding.
It is the companion to using virtual reassembly buffers which is a pure
implementation technique.
"
Does that read well?
Ok.
Dave
_______________________________________________
6lo mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lo
