Re: [6lo] Adoption call for 6lo Applicability and Usecases

I agree on the adoption of the document.
Regards,

                    Diego

2016-10-10 19:50 GMT-03:00 samita Chakrabarti <samitac.ietf@gmail.com>:

> Hi Take,
>
>
>
> It is great to hear from you on the 6lo list. Input from practical
> deployment is quite valuable especially if your organization is considering
>  6lo stack.
>
> There are couple of ways to contribute:
>
>
>
> 1)      Providing suggested text on the draft and working with the
> co-authors and 6lo-chairs  to update the document
>
> OR
>
> 2)      Writing a separate short draft with the suggested texts or
> use-case scenarios  which can be used as the input to the 6lo Applicability
> & usecase document
>
>
>
> I know  we talked sometime ago off-line, if you have any further questions
> let me and Gabriel know.
>
>
>
> Regards,
>
> -Samita
>
>
>
> *From:* Take Aanstoot [mailto:take@modio.se]
> *Sent:* Saturday, October 8, 2016 2:21 AM
> *To:* Yong-Geun Hong <yonggeun.hong@gmail.com>
> *Cc:* Samita Chakrabarti <samitac.ietf@gmail.com>; Pascal Thubert
> (pthubert) <pthubert@cisco.com>; 6lo@ietf.org
> *Subject:* Re: [6lo] Adoption call for 6lo Applicability and Usecases
>
>
>
> Dear People,
>
> Without the deep technical knowledge as you other people I want to give
> some feedback from the field where we today are trapped in a nightmare of
> standards, telco-standards and "standards". We work with wireless, plc and
> rs485, knx, profibus, M-bus and what have you.
>
> This is my first post to an IETF mailinglist so please if someone wants to
> guide me on the proper way to submit parts of this if it is not totally
> bogus.
>
>
>
> The draft is a really nice oversight over 6lo in diverse use-cases, really
> nice as a quick reference on where to continue. We (modio) will probably
> make a flowchart thing based on this document and rfc6568 where you can put
> in your use-case and based on that get to know what could be appropriate
> 6lo-solutions instead of today's old standards and de facto standards.
>
> I am missing the following chapters, even though the standards are not
> there yet I feel it should be mentioned so they will not be forgotten.
>
> 6loPLC, now primarily G3-PLC and Prime, needs a chapter in 3.foo and 6.foo
>
> LPWAN on low frequency (somewhere between 60-600 Mhz).
>
> People are testing nowadays in Europe on the following available
> frequencies:
> -2.4GHz, crowded, short range, crowded, worldwide, crowded, poor
> penetration, crowded.
>
> -868 MHz, getting crowded, only 20kHz, poor hardware support.
>
> -433MHz (and in some countries other small bands between 398 - 465 MHz),
> long range, reliable, few channels, frequency allocations are specific to
> particular countries, 10kbit/s, still expensive modules.
>
> 27 and 40MHz HF, cheap, simple, long range, crowded, low data rates,
> crowded, large antennas needed
>
>
>
> For LPWAN to succeed we need more frequencies, both public ones and
> private ones booked through your local radio frequency authority. This
> should be named in the draft and also recommendations of what type of radio
> to run on these frequencies.
>
> It would be nice to state in this draft that in most part of the world
> 174-230 MHz VHF is more or less empty or run a very deprecated radio
> broadcasting standard which will probably be decommissioned during the next
> few years and that it would be nice to reserve a big part of it for IoT
> use, both public and bookable/buyable private channels. That would be the
> difference between happy go lucky LPWAN on existing channels and a
> worldwide break through for reliable serious applications LPWAN.
>
>
>
> 5 Design space:
>
> New bullet:
>
> Update firmware requirements: Most 6 lo uses case will need a mechanism
> for updating firmware. In these cases support for over the are updates are
> required, probably in a broadcast mode when bandwith is low and the number
> of identical devices is high.
>
>
>
> Security Requirements: (Actual text: Some 6lo use case can transfer some
> important and personal data between 6lo nodes.  In this case, high-level
> security support is required.)
> 6lo will be used for important data between nodes, eventually someone will
> also know how to make today's not important data very important. High level
> security support is required.
>
> 6.4 use case of MS/TP
>
> I can probably write something there if interest exists.
>
> 6.6 use case of LTE MTC
>
> Mentions LTE MTC very briefly and then talks mostly about LoRa. Mayby
> change topic.
>
>
>
> Are you still with me?
>
> Regards, Take
>
>
> --
>
> Take Aanstoot
>
> CEO
>
> Modio AB
> +254 70 646 2344
> +46 13 46 555 62
>
> take@modio.se
>
>
>
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org
> https://www.ietf.org/mailman/listinfo/6lo
>
>

-- 
DIEGO DUJOVNE
Profesor Asociado
Escuela de Informática y Telecomunicaciones
Facultad de Ingeniería - Universidad Diego Portales - Chile
www.ingenieria.udp.cl
(56 2) 676 8125