Okay...I think perhaps I will make this a seperate Thread.
> > Any luck on an XML implementation for network packets?
>
> "Luck" in what sense?
Well. perhaps I shouldn't have used the word Luck. I ment to say, is there
any form
of a DTD with the intention of represent Network Segment/Packet
transmission.
> Nobody's actively working on implementing it at present, as far as I
> know; we're still in the early discussion stage, so it's not as if
> there's likely to be anly "luck" in the short term in the sense of any
> implementation showing up.
>
> > Would this need to be sort of a generic XML implementation (Net-ML) or a
> > protocol specific( TCP-ML, IP-ML)
>
> Generic.
I have some background in network programming, but not extensive, so work
with me a little bit here..heck...this might even should be moved to an XML
or Networking mailing list or news group of some type.
So for generic representation of network traffic, would it be safe to say, a
network packet would be something like (with some being optional):
Packet/Frame
-premable
- header
* dest address
* src address
-frame type
-frame data
-CRC
which might turn into something like
<packet>
<header>
<address who="source" format="ethernet">00:c0:4f:6b:9f:e0 </address>
<address who="destination" format="ethernet">00:c0:4f:30:20:11
</address>
</header>
<frame type="blah">
frame data of some type
<frame>
<CRC> </CRC>
</packet>
and/or
<packet>
<address who="source" format="ip">192.168.44.1 </address>
<address who="destination" format="ip">192.168.68.1 </address>
<frame type="blah">
frame data of some type
<frame>
</packet>
I'm just babbling here (and restating a lot)...so tell me if I'm heading in
the right direction.
Eric Bresie
ebresie@xxxxxxx