Re: Adding a new OSI layer
- From: chrb81@xxxxxxxxx
- Date: 19 Mar 2007 06:01:55 -0700
Hi Josef,
It's my understanding of the concepts of IOS/OSI Layers that thisThen we share the same understanding. But things become complicated in
cannot, should not and must not be done: each layer should be
autonomous.
terms of heterogeneous links. Just take a look at 802.21 - they
propose a cross-layer approach. The classical ISO/OSI model is not
optimal for everything...
Besides: you cannot add to something that hasn't been created yet: when
the session layer has created its PDU it will hand it to the Transport
layer which will then stick its own header/trailer to it.
| app. header | app data |
prepend with layer 5 header:
| l5 header | app. header | app data |
choose an appropriate transport layer protocol within layer 5:
| l4 header | l5 header | app. header | app data |
continue regularly with layer 3...
Anyway, I'm not proposing this architecture. In fact, I also think its
not a good idea.
I'm just spending some thoughts on how you could implement it...
I guess that it should belong to the OS (kernel).Maybe that small parts of the session layer should go into the kernel,
but I don't think that the bulk of it needs to.
Thanks for your inputs.
Christian
.
- References:
- Adding a new OSI layer
- From: chrb81
- Re: Adding a new OSI layer
- From: phil-news-nospam
- Re: Adding a new OSI layer
- From: chrb81
- Re: Adding a new OSI layer
- From: Josef Moellers
- Re: Adding a new OSI layer
- From: chrb81
- Re: Adding a new OSI layer
- From: Josef Moellers
- Re: Adding a new OSI layer
- From: chrb81
- Re: Adding a new OSI layer
- From: Josef Moellers
- Adding a new OSI layer
- Prev by Date: Re: Adding a new OSI layer
- Next by Date: Re: Linux kernel, possible useless continue
- Previous by thread: Re: Adding a new OSI layer
- Next by thread: Re: Adding a new OSI layer
- Index(es):
Relevant Pages
|