<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Eric,<br>
</p>
<div class="moz-cite-prefix">On 26.10.20 14:33, Eric van Uden via
iot-wg wrote:<br>
</div>
<blockquote type="cite"
cite="mid:OF28DBD1B4.084C8468-ONC125860D.004A1DE5-C125860D.004A7C79@avm.de">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<span style=" font-size:10pt;font-family:Courier New">Hi Eliot,</span>
<br>
<br>
<span style=" font-size:10pt;font-family:Courier New">I´m refering
to the Stacked Router concept, so one CPE instead of two
(stacked) In this
case, the CPE</span>
<br>
</blockquote>
<p><br>
</p>
<p>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.<br>
</p>
<p>Does this make sense?</p>
<p>Eliot<br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
</body>
</html>