Balazs Scheidler wrote:
> I'd like to suggest to extend the model in the proposal above, so that
> messages can travel several hops, not just a single relay station.
I had attempted to make it clear that this was the case, but I guess I was a
little too brief in doing so. I'll use your diagram in the next draft to
clarify it.
> where '...' indicates several relay hosts. This would involve changing the
> COOKED BEEP DTD.
The formats you suggest seem to be implying that people might want to track
all the relays a particular entry came through. Is this really a useful
thing to know for each entry? I would think knowing where the message
started, and looking at the configuration for each intermediate relay, would
be sufficint.
I'm concerned that in a long chain of relays, each would have to parse and
modify the entries. Without this information, either the device or the first
relay can attach the information, and then it's there. Maybe there's a
better way of representing this.
I'm also mildly concerned about the compatibility of XML with your proposed
format changes, but that's easier to work out once I understand the reason
for wanting this information.
> And as you may see I'd suggest using originFQDN and originIP instead of
> deviceFQDN and deviceIP.
These terms are from the syslog draft, actually. They represent the FQDN and
IP of the "device" that created the entry, rather than any of the relays
along the way.
> Otherwise I like the proposal.
Thank you!
--
Darren New / Senior MTS & Free Radical / Invisible Worlds Inc.
San Diego, CA, USA (PST). Cryptokeys on demand.
The tragedy of the commons applies to monitizing eyeballs, too.
