KNX vs IP

[Steven]

IP is only a medium.
It only specifies the Network Layer of a communication, and not a
complete communication system.
For reference: KNX specifies everything from the lowest Physical Layer
to the highest Application Layer.

That being said, it is thus clear that with IP, you can transfer a
telegram along a network and route it, but nothing else.
IP furst of all does not define a medium. It runs on radio waves (RF
WLAN), Ethernet, optical fibre. That is the first choice that the
author has to make: do you install 10 MBit/s, 100 MBits (Cate 5, Cate
5e ....). But that is more a power of IP than a weakness.
But for the higher levels of the communication stack, IP does not
define anything. That is why we all know higher level protocols on top
of IP, like:
- http to transfer text
- ftp to transfer files
- POP and SMTP for e-mail....
So, IP is not enough. To be able to do something (read the internet,
send/receive e-mails), you need additional protocols.
Also for doing home and building automation on IP, you will thus need
additional protocols on top of and using IP. This can for instance be
KNX IP, we all the good things of KNX from Twisted Pair: an open
protocol, a standard, Interworking, only a single tool to learn and
more than one provider.



On 8 sep, 00:21, airliner <fbourg...@gmail.com> wrote:
> http://www.maison-domotique.com/edito.php?edito=19
>
> bonne lecture...
>
> ps : connaissez vous des produits?