Re: sequenceId and relaying
Balazs Scheidler <[email protected]>
| Newsgroups | gmane.ietf.syslog |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 2008-07-16 at 11:07 +0200, Rainer Gerhards wrote: > Hi all, > > the intent is end-to-end. It got mangled during the "name wars" of syslog application/sender/receiver/originator etc. To restore the original meaning, we could do (during auth48 if there is consensus): > > ### > The "sequenceId" parameter tracks the sequence in which the ***originator*** submits > ### > > Anything beyond this is for the next version. I violently object any change that brings us out of the RFC editor publishing queue after we have finally reached this state after years and years... I say this even though I tend to agree to Bazsi on many points. This is ok for me at this point of time, I'll act accordingly. However I see some ambiguities with relays and how relays are permitted to change messages, especially with syslog-sign in mind. -- Bazsi _______________________________________________ Syslog mailing list [email protected] https://www.ietf.org/mailman/listinfo/syslog