> -----Original Message-----
> From: Balazs Scheidler [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 16, 2008 1:21 PM
> To: Rainer Gerhards
> Cc: Chris Lonvick; [email protected]
> Subject: RE: [Syslog] sequenceId and relaying
> 
> 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.

That comes at no wonder, have a look at A.1:

####
RFC 3164 describes relay behavior.  This document does not specify
relay behavior.  This might be done in a separate document.
####

So details of relay operations are not covered by intension. After the
"name war", this has become a bit hard to grasp because the word relay
is all over the document. But a more prominent statement of
non-applicability was prevented by the "precise vs. imprecise spec war"
roughly two years before that. All of this is reasoning for not touching
anything right now. If we touch once again, we'll most probably blow the
whole effort. I, at least, am not prepared to invest any time more into
that same thing without seeing any progress. (I am open to discussion,
though, on something that may later become the text defining relay
operations).

Rainer
_______________________________________________
Syslog mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/syslog

Reply via email to