Hello Carles

I have reviewed the work carefully.

I believe that we can achieve short packets with 6lo and SCHC so that piece is 
not an essential progress. So 6lo as an INT areaWg does not need it.The 
essential progress is meshing without routing. It’s probably hard to justify it 
at the routing area though the authors could try.

My feeling is that the idea is interesting but has a very narrow applicability, 
which is in essence the opposite of IP. The progress applies only to very 
specific L2 networks. This tells me that it is really an L2 technology and 
should be used for MAC not IP.

Bottom line is that I do not believe that the work belongs to the IETF.  I do 
not support adoption at 6lo.


Regards,

Pascal

Le 2 août 2022 à 18:01, Jing Wang <[email protected]> a écrit :


Hi WG,

    I support the adoption call. In my opinion, this can help enlarge scope of 
IP network, considering it may consume less resource of constrained nodes.

BR,
Jing Wang

From: Carles Gomez Montenegro<mailto:[email protected]>
Date: 2022-08-01 22:58
To: 6lo<mailto:[email protected]>
Subject: [6lo] Call for WG adoption of draft-li-6lo-native-short-address-03
Dear 6lo WG,

This message starts a call for WG adoption for
draft-li-6lo-native-short-address-03.

(Link below:
https://datatracker.ietf.org/doc/html/draft-li-6lo-native-short-address-03)

Considering that some folks may be on vacation currently or in the next
few days, the call will end on the 22nd of August, EOB.

Please state whether you are in favor of adopting this document.

Also, any comments you may have, and/or expressions of interest to review
the document, will be very much appreciated.

Thanks,

Shwetha and Carles

_______________________________________________
6lo mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lo
_______________________________________________
6lo mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lo
_______________________________________________
6lo mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lo

Reply via email to