[6lo] comments on draft-hou-6lo-plc-04

["Chenlihao (Lihao, IP Technology Research Dept NW)" <[e-mail]>]

Hello authors,

I think this draft gives a good guideline for IPv6 adaptation on PLC. The draft has a quite complete description. However, some points need to be clarified. Please find my comments below.

- The preface of the section 3 is not well organized. The content of the two paragraphs seems to be relevant, but the features of the same PLC technology are not in the same paragraph.

- It is reasonable that different PLC technologies have different terminologies, but the draft should build up a mapping between them. For example, in section 4.3, 1901.1 uses NID and TEI, while 1901.2 uses PAN ID and Device ID.

- For Fragmentation and Reassembly, the draft says that "the number of data octets of the PHY payload can change dynamically based on channel conditions", thus even for IEEE 1901.1 and 1901.2, the MTU can be lower than 1280 bytes. But the second paragraph says that fragmentation and assembly MUST NOT be used. Any contradiction here?

- The "charging station to EV communication" use case may not be appropriate for using ADOV-RPL in PLC tree network. Since the charging station and the EV are directly connected to each other, it should be parent to child communication instead of P2P.


Cheers,
Lihao