Hi Everyone, I've updated our web page and this is a note to let everyone know where we are with the process. http://www.employees.org/~lonvick/index.shtml draft-ietf-syslog-syslog-12.txt has been accepted as an Informational RFC. I've heard back from the RFC Editors that this process usually takes about 2 months before they slap a number on it and place it into the RFC repository. (Yes; they know that this one is _important_ but they're going to stick to their queue anyway. ;-) draft-ieft-syslog-reliable-09.txt is being discussed by the IESG this week. Darren and Marshall made some minor edits (nits and typo's found by people with eagle eyes) but this is fundamentally the same as -07 that was submitted to the IESG. If it passes their review, then it may become an RFC sooner as the RFC Editors process the "standards" submissions before the "informational" submissions. draft-ietf-syslog-auth-00.txt has been taken out of the ID repository. It had a lot of good ideas but we decided during our meeting in San Diego to pursue syslog-sign to provide an "authenticated syslog" as specified in our charter. John is working on some formatting edits to draft-ietf-syslog-sign-01 that I suggested. I'd still like some technical reviews of this especially from people who intend to implement this. Speaking of which, can I get a show of hands of the people on this list who are planning on implementing syslog-reliable? I'll buy beer (or other suitable beverages) in London for them if everyone would like to get together for a discussion there. Some BEEP resources are available here for people just starting to think about it: http://beepcore.org/beepcore/ Many thanks, Chris [Replying to this will go to the list.] [Please use [EMAIL PROTECTED] to ] [reply to me separately. ]
