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/[email protected]/
[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 ]
Eliot Lear
lear at lear.ch
Mon Oct 26 16:08:53 CET 2020
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 -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/iot-wg/attachments/20201026/a7b621df/attachment.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 ]