Hi 6lo WG and all,I support the adoption. As a graduate student of Beijing 
University of Posts and Telecommunications, which has been paying continuous 
attention to the research and development of 6lo, I have my own understanding 
after reading this draft.In the current architecture of network, the limitation 
of address length, the over centralized design of networking and the high 
overhead of routing protocol itself hinder the construction of large-scale LLN. 
It’s glad to see alternative method is adopted to dynamically build the 
network, which not only breaks the limitations of IP address, but also 
eliminates certain routing overhead. It will make the system designers pay less 
energy to the addressing and routing part. Considering LLN’s characteristics in 
practical applications, it may need to consider more. I don’t know whether are 
they belongs to L2 or L3 scope. But it worth my continuous attention to the 
progress of this draft. And I am interested in building a demo to verify extra 
considerations. The adoption and consensus to the solution would be 
helpful.Regards,Zhen 
Zhang______________________________________________________________________________________________From:
 6lo <6lo-boun...@ietf.org&gt; On Behalf Of Pascal Thubert (pthubert) Sent: 
Wed,&nbsp;03&nbsp;August&nbsp;2022&nbsp;07:01&nbsp;UTC To: Jing Wang 
<wangjin...@chinamobile.com&gt;Cc: Carles Gomez Montenegro 
<carle...@entel.upc.edu&gt;du&gt;; 6lo <6lo@ietf.org&gt;Subject: Re: [6lo] Call 
for WG adoption of draft-li-6lo-native-short-address-03Hi Pascal and all, As we 
know, the discussion of whether routing in LLN networks should run at Layer 2 
or Layer 3 (network layer) has become a very sensitive issue for a  long time. 
With the advent of multiple low-power link layer technologies, such as IEEE 
802.15.4, Wi-Fi, and PLC, network layer routing is clearly required. However, 
the separation of mesh-under and route-over processes induces suboptimal routes 
and (L2 and L3) duplicated re-route overhead. This draft’s topological 
addressing method can integrate address and route information into a single 
place. It will help to run IP layer on various link layer technologies and 
meanwhile avoid above duplicated re-route issues. Thanks Pascal for continuous 
advices and comments. As author of this draft, I want to state support of this 
adoption. Regards, Guangpeng Li From: 6lo <6lo-boun...@ietf.org&gt; On Behalf 
Of Pascal Thubert (pthubert) Sent: Wednesday, August 3, 2022 12:37 PM To: Jing 
Wang <wangjin...@chinamobile.com&gt;Cc: Carles Gomez Montenegro 
<carle...@entel.upc.edu&gt;du&gt;; 6lo <6lo@ietf.org&gt;Subject: Re: [6lo] Call 
for WG adoption of draft-li-6lo-native-short-address-03 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 
<wangjin...@chinamobile.com<mailto:wangjin...@chinamobile.com&gt;&gt; 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:carle...@entel.upc.edu&gt; Date: 2022-08-01 22:58 To: 
6lo<mailto:6lo@ietf.org&gt; 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 
6lo@ietf.org<mailto:6lo@ietf.org&gt;https://www.ietf.org/mailman/listinfo/6lo_______________________________________________
 6lo mailing list 
6lo@ietf.org<mailto:6lo@ietf.org&gt;https://www.ietf.org/mailman/listinfo/6lo








ZZ


zz...@foxmail.com
_______________________________________________
6lo mailing list
6lo@ietf.org
https://www.ietf.org/mailman/listinfo/6lo
              • ... Liguangpeng (Roc, Network Technology Laboratory)
              • ... Pascal Thubert (pthubert)
              • ... Michael Richardson
              • ... Liguangpeng (Roc, Network Technology Laboratory)
              • ... Pascal Thubert (pthubert)
              • ... Liguangpeng (Roc, Network Technology Laboratory)
          • Re: [6lo... Alexander Pelov
          • Re: [6lo... Michael Richardson
          • Re: [6lo... Michael Richardson
  • Re: [6lo] Call for WG ado... Zhen Zhang

Reply via email to