This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/iot-wg@ripe.net/
[iot-wg] IoT BCOP TF Document - Call for comments
- Previous message (by thread): [iot-wg] IoT BCOP TF Document - Call for comments
- Next message (by thread): [iot-wg] IoT BCOP TF Document - Call for comments
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Steinhäuser
ps at embedd.com
Tue Oct 27 09:13:34 CET 2020
Hi Eric, besides the more modern protocol design (TR-369 uses the same latest TR-181 datamodel on the CPE like TR-069) the major difference is that TR-369 allows several „controllers“ with different levels of access while TR-069 only knows one „controller“ - the ACS. Because of this design it’s possible that i.e. a smartphone app the customer uses acts as one possible controller for a TR-369 enabled CPE. - Peter > Am 26.10.2020 um 16:34 schrieb Eric van Uden via iot-wg <iot-wg at ripe.net>: > > Hi Eliot, > > I have to confess, at the moment I have no experience with TR369. I am glad that I understand TR69 a little. ;-) What I do know about TR369 is that it is a good basis to keep a better eye on things in the future and to make decisions based on the information from the CPE. > > > Best regards, > > Eric van Uden > > AVM ICT GmbH > Country Manager Netherlands > Mr. van Coothlaan 10 > 6602 GT Wijchen > Nederland > Phone +31 24 6485381 > Mobile +31 622 948356 > e.vanuden at avm.de > > Bezoek onze website op http://nl.avm.de/ <http://nl.avm.de/> , vind ons leuk op Facebook <https://www.facebook.com/fritzboxnederlands> of bekijk onze Google +-pagina <https://plus.google.com/115631098113092982023/videos> en Youtube-kanaal. <https://www.youtube.com/user/fritzboxnederlands> > > AVM GmbH for International Communication Technology, Alt-Moabit 95, 10559 Berlin, Germany > HRB 48220 AG Charlottenburg, CEO (Geschäftsführer): Johannes Nill > > > > Von: "Eliot Lear" <lear at lear.ch> > An: e.vanuden at avm.de > Kopie: iot-wg at ripe.net > Datum: 26-10-2020 16:08 > Betreff: Re: [iot-wg] IoT BCOP TF Document - Call for comments > > > > Hi Eric, > On 26.10.20 14:33, Eric van Uden via iot-wg wrote: > Hi Eliot, > > I´m refering to the Stacked Router concept, so one CPE instead of two (stacked) In this case, the CPE > > Thanks. It is better for a single provider to interface with the user. Stacked CPE should certainly not be required, but nor should it be prohibited. If I don't like the pizza box my provider gives me, I might want to put something in front of it. In that case, the maker of that something might take responsibility for communicating with me about what is going on in my network. This has an impact as to whether or not everything can be done in, say, TR.369. > Does this make sense? > Eliot > > > > > _______________________________________________ > iot-wg mailing list > iot-wg at ripe.net > https://mailman.ripe.net/ Peter Steinhäuser, CEO embeDD GmbH · Alter Postplatz 2 · 6370 Stans · Switzerland Phone: +41 (41) 784 95 85 · Fax: +41 (41) 784 95 64 -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/iot-wg/attachments/20201027/4937e91b/attachment-0001.html>
- Previous message (by thread): [iot-wg] IoT BCOP TF Document - Call for comments
- Next message (by thread): [iot-wg] IoT BCOP TF Document - Call for comments
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ iot-wg Archives ]