Hello Gordon, Gordon Lennox wrote:
I don’t think we seriously disagree. :-)
But I see two sides this discussion : what people/companies/organisations of the sort kind of represented here think and can maybe do and what others, particularly policy makers and legislators, might do and what we might like them to do / not do.
Good to collect the viewpoints. All need ot be tackled in some way. So have a good overview of them is essential to get at the end a working/accepted (technically and societal) solution. I gave a few in my former e-mail, but I am sure there are many viewpoints to gather in this IOT environment.But again I hope we can limited/aggregated/etc. them. All the best, Victor
So if we argue a naive end-to-end - circuits? - then we leave them with the impression that they can selectively allow/prioritise/block. Basically the little paper that Patrik and I put together says that even one terminal going to one web-site involves a lot more than one “connection”. And we know that blocking some random “connection“ can result in a lot of unforeseen and unintended collateral damage.
Basically I would rather use engineering terminology than marketing terminology.
Gordon
On 12 Apr 2017, at 10:08, Giuliano Peritore <g.peritore@panservice.it> wrote:
Hi Gordon,
just a tip to clarify my thoughts:
But the end-to-end idea seems to take us back to a connection - a circuit? - between two end points. Maybe two end networks makes a little bit more sense? And yet we here know that is not the case.
End-to-end means that any end network should have the possibility to communicate with any other end network that wants to allow that.
The number of networks involved. The number of name servers involved. The number of content servers involved.
This is allowed, but not *imposed* by end-to-end. It's end to end that allows to build such complex services... but also to create simple ones.
So a “thing” on a network may be having quite a rich conversation with very many servers out there. It is not simple end-to-end, device to server.
It's end-to-end IP communication and internetworking, on the top of which the ecosystem built services, on levels higher than L3. If this was not the case the DNS would have been a network function and you couldn't have you DNS server at home or in your plant or in a cloud-only provider. The end-to-end communication principle allowed services to evolve, to have the services and protocols we today have. It allows you to conceive and build new services. And two nodes can choose to communicate between them without all the clutter of "many servers out there".
And then your access provider - many provide services only some provide access! — may not be as obvious as you think. You will have more than one. I am not sure how many. Correct, but when it comes to market it has to be stated very clear if one company is selling "access" or "services" or... "fenced access 'service'".
Thanks for your thoughts.
-- Giuliano Peritore - g.peritore@panservice.it Direzione Generale - Panservice Servizi professionali per Internet ed il Networking Telefono: +39 0773 410020 - Fax +39 0773 470219 Numero verde: 800 901492 - http://www.panservice.it
_______________________________________________ iot-discussion mailing list iot-discussion@ripe.net https://lists.ripe.net/mailman/listinfo/iot-discussion
-- Victor Reijs Network Development Manager and International Relations HEAnet CLG, Ireland’s National Education and Research Network 1st Floor, 5 George’s Dock, IFSC, Dublin D01 X8N7, Ireland +353 (0)1 6609040 victor.reijs@heanet.ie www.heanet.ie Registered in Ireland, No. 275301. CRA No. 20036270 (w)