[Syslog] survey

Hi, The survey was summarized at IETF 60 in the following presentation: http://www3.ietf.org/proceedings/04aug/slides/isms-1.pdf Dave Harrington [EMAIL PROTECTED] ___ Syslog mailing list Syslog@lists.ietf.org

[Syslog] RE: draft-ietf-syslog-sign-18.txt

recognizes only Chris since he was chair during the work on that document. I should probably be added in case the rfc-ditor needs to contact me, such as for AUTH48. My contact information is David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] Huawei Technologies (USA) 1700 Alma Drive, Suite 100 Plano

RE: [Syslog] Secure transport alternatives

Hi Darren, I don't know them well enough to comment. Are you willing to write one or two drafts proposing these as possible solutions so the WG can evaluate them as alternatives? David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: [EMAIL

RE: [Syslog] IESG secure transport requirement can be quicklysolved...

whether to have you publish as an individual or WG draft. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: Rainer Gerhards [mailto:[EMAIL PROTECTED] Sent: Thursday, June 22, 2006 11:09 AM To: David Harrington; Chris Lonvick Cc: [EMAIL

RE: [Syslog] Secure transport alternatives

Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, June 22, 2006 6:14 AM To: Miao Fuyou Cc: 'David Harrington'; 'Rainer Gerhards'; [EMAIL PROTECTED] Subject: Re: [Syslog] Secure

RE: [Syslog] Decisions to make about the Huawei IPR claim

to this WG should be involved in that discussion, which is likely to be centered in the OPS area. This WG is about security for syslog, and we should focus our efforts on solving the security problems, whether with tls or ssh or beep, and publish. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED

RE: [Syslog] Decisions to make about the Huawei IPR claim

-related issues, and I think those discussions belong in the OPS area rather than the Security area. dbh -Original Message- From: Anton Okmianski (aokmians) [mailto:[EMAIL PROTECTED] Sent: Friday, June 30, 2006 3:43 PM To: David Harrington; Rainer Gerhards; Chris Lonvick (clonvick

[Syslog] FW: Initial Logging capabiltiies document

FYI. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of patrick cain Sent: Wednesday, July 05, 2006 10:33 AM To: [EMAIL PROTECTED] Subject: Initial Logging capabiltiies document Hi, I promised to get out a version of the logging capabiltiies document.

RE: [Syslog] Decisions to make about the Huawei IPR claim

propose text worded as you wish to see it, and ask for WG comments. If Chris feels there is WG consensus on the wording, then that wording would go into the document, without being slightly modified. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message

RE: [Syslog] FW: Posting of draft-ietf-syslog-device-mib-08.txt

or not, so we can plan to get the work completed by the November deadline. Thanks, David Harrington [EMAIL PROTECTED] co-chair, Syslog WG -Original Message- From: IETF Secretariat [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 25, 2006 3:50 PM To: Glenn M. Keeni Cc: David

RE: [Syslog] delineated datagrams

. There is ongoing discussion about the framing in the netconf notification protocol, and the possibility of interleaving notifications and request/responses within a session or channel. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: Chris Lonvick

[Syslog] timeline

-ietf-syslog-transport-udp, so you can get started ahead of time to do these reviews if you want. WGLCs will probably start Monday Aug 14. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] co-chair, Syslog WG ___ Syslog mailing

RE: [Syslog] delineated datagrams

the Montreal Netconf Interim minutes currently available on the netconf mailing list for more details. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: Tom Petch [mailto:[EMAIL PROTECTED] Sent: Monday, August 14, 2006 6:36 AM To: David

RE: [Syslog] syslog WG Timeline

please identify your ibjections, preferably with suggested text that would make it acceptable. Thanks, David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] co-chair, Syslog WG -Original Message- From: Chris Lonvick [mailto:[EMAIL PROTECTED] Sent: Friday, August 11

RE: [Syslog] Syslog-sign -protocol

Hi, When can we get an updated revision of syslog-sign? Our current timeline calls for starting WGLC Aug 28. The changes sound sufficiently large that we should definitely try to review the changes before we start a last call on the document. David Harrington [EMAIL PROTECTED] [EMAIL

[Syslog] WGLC: protocol

it to acknowledge the IASA rather than the Internet Society. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog

[Syslog] MIB document decision

should also be compared to the functionality described in -protocol-, -udp-, and -tls- documents to make sure the defaults are consistent, and the management functionality adequate. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED

[Syslog] Consensus: octet-counting

Hi, [speaking as co-chair] Chris and I have reviewed the discussions and have reached the conclusion that the WG consensus is to use octet-counting rather a special character for delineating messages in a TLS transport. Miao and Yuzhi, please update the syslog-tls draft accordingly. David

FW: [Syslog] Working Group Last Call: protocol and udp documents

Hi, I haven't seen many reviews for the WGLC. Come on people, we're trying to finally get this work finished. Please put away your apathy and do some reviews. Dbh co-chair, Syslog WG -Original Message- From: David Harrington [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 15, 2006 2

[Syslog] Working Group Last Calls

Hi, The WGLC for -protocol-17 and -udp-07 documents will end later today. Please review and comment on these documents today. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Syslog mailing list Syslog@lists.ietf.org https

[Syslog] WGLC: protocol, part 2

be noted in this document. It is more approrpiately mentioned in a transport mapping that addresses transport over IPv6. I prefer to eliminate it here. A.6 and A.8 are related; it would be good to have them next to each other. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL

[Syslog] WGLC: sysog-sign, part 1

- can you specify the range of characters included in printable ASCII? --- I will be sending another review as I read through the document for content and grammar. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Syslog

[Syslog] RE: I-D submission draft-ietf-syslog-device-mib-09.txt

Hi Glenn, I have not yet seen revision -09- announced, and it is not yet available from the I-D repository. Can you check on the progress of this please? I seem to have some problems getting email to you using the [EMAIL PROTECTED]; if there is another address I can use to contact you, please

[Syslog] WG timeline

submit all final-WGLC-modified drafts to internet-drafts Nov 30 submit documents to the IESG. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo

[Syslog] Dbh Review of -mib-09, part 1

? Across reboots of the SNMP system? If it is not persistent, but the table is, what should the SNMP agent do - delete the references? Change the references to match the new SWRunIndex? David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED

[Syslog] -mib-, part 3

-specific setting (since some transports already have congestion avoidance), or a system-wide setting. I think the WG should discuss how they want to handle this. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Syslog mailing

[Syslog] WGLC: syslog-sign

-19 was published we also had a discussion of APP-NAME, et al. so that needs to be addressed in -20. And there are a few editorial fixes I mentioned. Can you publish a sign-20 soon? There have been quite a few changes since -18-, so I think we'll need to do another WGLC. Thanks, David Harrington

[Syslog] Review of Mib-10, part 1

for an example). David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog

[Syslog] All editors

, David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog

RE: [Syslog] Updated Syslog-tls Document

-Original Message- From: Rainer Gerhards [mailto:[EMAIL PROTECTED] Sent: Thursday, November 23, 2006 2:48 AM To: Miao Fuyou; [EMAIL PROTECTED] Subject: RE: [Syslog] Updated Syslog-tls Document - 5.1 == When confidentiality is

[Syslog] Proposed schedule

that it may take as long as late January to complete the document, run another WG last call (in non-holiday weeks), and make adjustments to be ready for submission to the IESG. Good work everybody, and thanks for staying involved to get these documents to completion. David Harrington [EMAIL

RE: [Syslog] Shepherding document for udp-08

Hi, Yes, I/we should correct this. Do we have any information about vendors that have implemented the current UDP specification? dbh -Original Message- From: Rainer Gerhards [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 22, 2006 6:29 AM To: David Harrington; [EMAIL

RE: [Syslog] Updated Syslog-tls Document

That wording satisfies me. dbh -Original Message- From: Miao Fuyou [mailto:[EMAIL PROTECTED] Sent: Monday, November 27, 2006 9:07 PM To: 'David Harrington'; 'Rainer Gerhards'; [EMAIL PROTECTED] Subject: RE: [Syslog] Updated Syslog-tls Document I am changing the sentence

[Syslog] Udp shepreherding document.

Hi, Here is the revised shepherding document for -udp-08 I modified the section. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Shepherding document for syslog-transport-udp-08 (1.a) Who is the Document Shepherd for this document? Has the Document

[Syslog] Shepherding document for draft-ietf-syslog-transport-udp-08

Hi Sam, Please publish draft-ietf-syslog-transport-udp-08 as a Proposed Standard RFC. Attached is the shepherding document for draft-ietf-syslog-transport-udp-08, including the Document Announcement Write-Up and contact information. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL

[Syslog] Shepherding document for -sign-

Hi, Here is the preliminary shperherding document for -sign- It is complete through revision -19-, and -20- should become available this week so I can finalize. Comments welcome. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Shepherding document for syslog-sign (1

[Syslog] revisions going forward

of the IESG to perform their reviews. That is the point at which we can publish a revision. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog

[Syslog] Dbh re-Review of -mib-11, part 1

? If it is not persistent, but the table is, what should the SNMP agent do - delete the references? Change the references to match the new SWRunIndex? David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Syslog

[Syslog] Review of mib-11, part 3

shown as [RFCPROT] or the RFC editor may overlook it. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog

[Syslog] Working Group Last Call: syslog-sign-20

://www.ietf.org/internet-drafts/draft-ietf-syslog-sign-18.txt It is recommended that reviewers especially consider the changes made between the two revisions, although the complete document should also be reviewed. Thanks, David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] co-chair

[Syslog] WGLC sign-20 comments, part 1

for interoperability and should be capitalized keywords. 3) /A device needs to hence support persisting previous reboot session ID across reboots./The reboot session ID must be persistent across reboots./ More later. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED

[Syslog] Syslog-mib-11

(e.g., daemon) that operates via one address/port? David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog

[Syslog] Notification compliance

Hi, Dbh If the intention is to leave out the notification, I would like to know why this is desirable. Glenn The reason is to retain the possibility of a compliant implementation that does not support notifications. This still does not explain why this is desirable. Who wants this

[Syslog] severity

back from the IESG and make changes to PRI. If the WG accepts the 0-7, but thinks the draft is not clear and unambiguous, then we could provide clarifying text as part of WGLC without pulling the draft back from the IESG. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED

RE: [Syslog] Syslog-mib-11

description clause will get the explanation to the users. I would not object to **also** having it discussed in the introductory text sections. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: Rainer Gerhards [mailto:[EMAIL PROTECTED] Sent

[Syslog] transportDomain and transportAddress

transport address of type TransportAddressIPv4? David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog

[Syslog] TLS TransportDomain

transportDomains, but if so, then the naming convention from RFC3417 is application protocoltransport protocolDomain, such as snmpUDPDomain. With our byte-count header for syslog/TLS, a syslogTLSDomain might alert an application that there will be byte-counts in the stream. David Harrington [EMAIL PROTECTED

[Syslog] SyslogService

Hi Glenn, -Original Message- From: Glenn M. Keeni [mailto:[EMAIL PROTECTED] 1.7 12) SyslogService - can we make this just a service name. The port semantics are really ambiguous. How do distinguish a UDP port# from a TCP port#? Not fixed. Response.

[Syslog] allowed

encountered, but not which problems have been encountered. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Syslog mailing list Syslog@lists.ietf.org https

[Syslog] syslEntCtlConfFileName

-Original Message- From: Glenn M. Keeni [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 13, 2006 6:45 AM To: [EMAIL PROTECTED] Subject: Re: [Syslog] Dbh re-Review of -mib-11, part 1,2,3 2.2 6) syslEntCtlConfFileName - using lots of abbreviations in the name

RE: [Syslog] Dbh re-Review of -mib-11, part 1,2,3

-Original Message- From: Glenn M. Keeni [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 13, 2006 6:45 AM To: [EMAIL PROTECTED] Subject: Re: [Syslog] Dbh re-Review of -mib-11, part 1,2,3 Hi, I have pruned the list of comments and renumbered them. The following starts

[Syslog] Mib-12

Hi Glenn, Once you finish updating the document with the issues we agree on, can you publish a mib-12 so we narrow the discussion to the few remaining issues? Thanks, David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Syslog

RE: [Syslog] Dbh re-Review of -mib-11, part 3

understanding what the use case is, I **CANNOT** understand the implications of their designs, and why an implemneter is required to support them, or how an implementer is expected to utilize them. How can we possibly declare these to be part of an industry-wide standard? David Harrington [EMAIL PROTECTED

[Syslog] RE: Framing...

Lonvick; David Harrington; Miao Fuyou Subject: Framing... Hi all, I just wonder if we have reached consensus to change the octet counter to just cover the SYSLOG-MSG len. I have to admit that I am hesitant to release the open source software with the wrong framing. I know

RE: [Syslog] RFC 3164

If members of the syslog community want to provide updated information about observed on-the-wire syslog messages, they should feel free to write such an informational document and have it published by the IETF. However, that is not part of the charter of our work, and should not be a WG item,

[Syslog] Syslog-mib-12

**reference** Diagram 1 in [RFCPROT], and the Terminology of Section 3 of [RFCPROT], and then explain how the terminology in the mib module relates to the [RFCPROT] terminology and diagram? David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] co-chair, Syslog WG -Original Message

[Syslog] Rfc3164 and mib

Hi, The consensus of the WG is to obsolete rfc3164. Therefore, it should not be referenced in the MIB document. The MIB document only references it in the introduction, so this has no effect. Glenn, please remove all reference to RFC3164 from the mib document. David Harrington [EMAIL PROTECTED

RE: [Syslog] TransportDomain issue

to be modeled for 1) a syslog receiver, 2) a syslog sender, and 3) a syslog relay. Glenn? Tom? Others? David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] co-chair, Syslog WG -Original Message- From: Juergen Schoenwaelder [mailto:[EMAIL PROTECTED] Sent: Thursday, December

[Syslog] Conclusion of Working Group Last Call: syslog-sign-20

Hi, This message officially concludes the Syslog Working Group Last Call for the following document: http://www.ietf.org/internet-drafts/draft-ietf-syslog-sign-20.txt The chairs and the editor will review the comments and determine which actions should be taken. Thanks, David Harrington

RE: [Syslog] Syslog Protocol doubts

Or we could simply reiterate Postel's law: In general, an implementation must be conservative in its sending behavior, and liberal in its receiving behavior. That is, it must be careful to send well-formed datagrams, but must accept any datagram that it can interpret (e.g., not object to

RE: [Syslog] Syslog Protocol doubts

Hi, [speaking as co-chair] Let's make this more concrete. What specific changes to which specific documents are you requesting? David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: tom.petch [mailto:[EMAIL PROTECTED] Sent: Saturday

[Syslog] MIB Issue #1 - one or multiple? Seeking consensus

with this, please say so. The chairs will make a determination of consensus, and this issue will be closed. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] co-chair, Syslog WG -Original Message- From: Glenn M. Keeni [mailto:[EMAIL PROTECTED] Sent: Friday, January 12

RE: [Syslog] MIB Issue #1 - one or multiple? Seeking consensus

Hi, [speaking as co-chair] MIB Issue#1 is not about whether Windows is a real operating system. If you want to have that discussion feel free, but please do it elsewhere - it is inappropriate for the syslog WG, and it is certainly off-topic for MIB Issue#1. David Harrington [EMAIL PROTECTED

RE: [Syslog] Mib-13

. The IPCDN event messaging MIB already has a dependency on these TCs. I discussed this with the other MIB Doctors and they concur this would be an appropriate thing to do. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED

[Syslog] RFC3195bis

schedule soon. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Co-chair, syslog WG ___ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog

RE: [Syslog] 3195bis before syslog-sign

explicitly shows the agreement from last year. The next steps are to complete syslog-sign and syslog-mib. That is what we are attempting to do, by resolving some dependency problems between syslog-sign and RFC3195, as discussed in my other email. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED

RE: [Syslog] RFC3195bis

whether to accept the draft as a WG item at this point? Thanks, David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: Eliot Lear [mailto:[EMAIL PROTECTED] Sent: Saturday, January 27, 2007 9:35 AM To: David Harrington Cc: [EMAIL PROTECTED

RE: [Syslog] An early last call comment on protocol-19

-compliant implementations? Would that satisfy the needs of both Sam and Tom and others in the WG? Are there technical reasons why implementations MUST NOT support BCP047, but only ISO? David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: Sam Hartman

[Syslog] FW: draft-ietf-syslog-protocol: Reliable delivery consideredharmful.

Forwraded from ietf@ietf.org; please include ietf@ietf.org in responses. dbh -Original Message- From: Stephane Bortzmeyer [mailto:[EMAIL PROTECTED] Sent: Friday, February 02, 2007 2:32 AM To: David W. Hankins Cc: ietf@ietf.org Subject: Re: draft-ietf-syslog-protocol: Reliable delivery

[Syslog] FW: draft-ietf-syslog-protocol: Reliable delivery consideredharmful.

Forwarded from ietf@ietf.org; please include ietf@ietf.org in any responses. dbh -Original Message- From: Eliot Lear [mailto:[EMAIL PROTECTED] Sent: Friday, February 02, 2007 9:04 AM To: Pekka Savola Cc: ietf@ietf.org Subject: Re: draft-ietf-syslog-protocol: Reliable delivery

[Syslog] FW: draft-ietf-syslog-protocol: Reliable delivery consideredharmful.

Forwarded from ietf@ietf.org; please include ietf@ietf.org in any responses. dbh -Original Message- From: Stephane Bortzmeyer [mailto:[EMAIL PROTECTED] Sent: Monday, February 05, 2007 5:33 AM To: David W. Hankins Cc: ietf@ietf.org Subject: Re: draft-ietf-syslog-protocol: Reliable

[Syslog] FW: draft-ietf-syslog-protocol: Reliable delivery consideredharmful.

Forwarded from ietf@ietf.org; please include ietf@ietf.org in any responses. dbh -Original Message- From: David W. Hankins [mailto:[EMAIL PROTECTED] Sent: Friday, February 02, 2007 1:00 PM To: ietf@ietf.org Subject: Re: draft-ietf-syslog-protocol: Reliable delivery consideredharmful.

[Syslog] FW: draft-ietf-syslog-protocol: Reliable delivery consideredharmful.

Forwarded from ietf@ietf.org; please include ietf@ietf.org in any responses. dbh -Original Message- From: Stephane Bortzmeyer [mailto:[EMAIL PROTECTED] Sent: Monday, February 05, 2007 5:33 AM To: David W. Hankins Cc: ietf@ietf.org Subject: Re: draft-ietf-syslog-protocol: Reliable

[Syslog] Chris

Hi, FYI. Chris is travelling heavily for work at this point, so has not had time to participate much in the recent discussions. He begs your indulgence, and hopes to get back into participation mode in the next few weeks. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED

[Syslog] Mib issues and resolutions

, the list of names for people who specifically took a posiiton on the issue, and what you percieve to be the WG consensus on the issues based on the stated positions? As we near the end of the work on these documents, we will need these summaries for AD review. Thanks, David Harrington [EMAIL

[Syslog] RE: syslog-sign

future extsnions are handled as per 2434. Authors' addresses are listed twice in the document. Can Informational documents be Normative? dbh -Original Message- From: Alexander Clemm (alex) [mailto:[EMAIL PROTECTED] Sent: Monday, March 12, 2007 6:08 PM To: David Harrington Cc: Chris

[Syslog] Note to editors

recognizes the IETF Trust. Thanks, David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog

RE: [Syslog] Note to editors

:52 PM To: Alexander Clemm ((alex)) Cc: David Harrington; [EMAIL PROTECTED] Subject: Re: [Syslog] Note to editors On Mar 13, 2007, at 11:17 AM, Alexander Clemm ((alex)) wrote: David, I am using the xml2rfc tool, which inserts these automatically. However, the copyright statement

RE: [Syslog] Note to editors

PROTECTED] Sent: Tuesday, March 13, 2007 8:42 PM To: 'Alexander Clemm (alex)'; 'David Harrington'; [EMAIL PROTECTED] Subject: RE: [Syslog] Note to editors Hi, I reckon this happens because the date in the front part of the XML file is not updated. date day=28 month=February year=2007

[Syslog] new scheduke

, final WG proof, then shepherd tls to rfc editor april - WGLC for sign-21 april - submit sign to iesg april - WG review of mib-15 may - WGLC for mib-16 june - submit mib to iesg may - WG review for bis june - WGLC for bis july - submit bis to iesg Thanks, David Harrington [EMAIL PROTECTED

[Syslog] SDE proposals

, the syslog WG in the Security Area is not the correct WG to host this work. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] co-chair, syslog WG ___ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo

[Syslog] syslog data modeling

on the correlation needs of operators, input from network management modeling experts in the OPS area, in cooperation with the syslog implementers from the current syslog WG. If you agree and would be willing to work on developing standardized SDEs for syslog, please email me at [EMAIL PROTECTED] David

RE: [Syslog] FINAL review of draft-ietf-syslog-protocol

that is closer to done. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] co-chair, Syslog WG -Original Message- From: Chris Lonvick [mailto:[EMAIL PROTECTED] Sent: Friday, May 11, 2007 9:35 AM To: tom.petch Cc: [EMAIL PROTECTED] Subject: Re: [Syslog] FINAL review

RE: Layer diagram mib counters - was:Re: [Syslog] Commentson draft-ietf-syslog-protocol-20

Hi, The IETF Management Framework makes a distcinction between management information and protocols used to carry information. The content layer provides an interface to the underlying instrumentation. A content layer concept is used in the Netconf architecture to represent this, and we carried

[Syslog] tc-mib poll

-normative set of facilities and severities? 3) Whether normative or non-normative, which is more important? efficient allocation of the limited facility values, or backwards compatibility with existing (and historic) implementations? Thanks David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL

[Syslog] protocol document review

at this point. We definitely want your reviews to help us advance a good enough specification onto the standards track. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] co-chair, Syslog WG ___ Syslog mailing list Syslog

RE: [Syslog] New -protocol document - your comments needed by 25 June

Hi, Would it be helpful to identify where in the architecture the facility exists? I think some people think the originator is the thing that asks syslog to send a message (is that the facility?), while others think the syslog thing that creates the syslog message (e.g. syslogd) is the

[Syslog] NomCom request for volunteers

From: Lakshminath Dondeti To: IETF Announcement Date: June 4, 2007 Subject: Nomcom 2007-8: First Call for Volunteers -- -- Folks, If you have attended 3 out of the past 5 IETF meetings, you are eligible to serve on

[Syslog] Working Group Last Call: syslog-sign-22

not look acceptable please identify your objections, preferably with suggested text that would make it acceptable. Thanks, David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] co-chair, Syslog WG ___ Syslog mailing list Syslog@lists.ietf.org https

[Syslog] Working Group Last Call: syslog-sign-22

-Original Message- From: David Harrington [mailto:[EMAIL PROTECTED] Sent: Thursday, July 12, 2007 1:02 PM To: [EMAIL PROTECTED] Cc: 'IETF discussion list' Subject: Working Group Last Call: syslog-sign-22 Hi, This message is to remind readers about the Syslog Working Group Last Call

[Syslog] syslog-tc-mib-02

suggest updating the ID number to 23, and turning the NOTE into an RFC editor's note. 9. I have checked the MIB module using libsmi, and the document using idnits, and the document looks good. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED

[Syslog] shepherd doc for syslog-sign

Hi Sam, We believe the syslog-sign document is ready for AD review and consideration for advancement to Proposed Standard. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] shepherding submission for syslog-sign Having passed a WG Last Call, and been updated to meet the comments from

[Syslog] WGLC: draft-ietf-syslog-tc-mib-02.txt

for these documents will end November 23. Thanks, David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] co-chair, Syslog WG ___ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog

[Syslog] WGLC: draft-ietf-syslog-tc-mib-02.txt

review. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog

[Syslog] WGLC: draft-ietf-syslog-tc-mib-02

this situation. For improved accuracy, the foobar application can also include an APPNAME SDE in the message identifying itself as the foobar application. Thanks, David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Syslog mailing list Syslog

RE: [Syslog] transport-tls-11 review

Hi, Let me remind the WG that this document is in IESG review. We are no longer doing fine-tuning/wordsmithing. We are fixing the problems raised by the IESG. So unless the wording is **broken** we shouldn't be trying to fix it now. What IESG-raised issues are we responding to? dbh

RE: [Syslog] Documenting the configuration of syslog

Hi, [as co-chair] This discussion started between Chris and I concerning the remaining charter item of submitting the Syslog Device MIB. The existing MIB has been rather controversial, and has knobs for configuring syslog using the MIB, when osme implementers say they have no demand for a MIB

RE: [Syslog] Documenting the configuration of syslog

Hi, [as contributor] Traditionally, standards are based on some level of agreement across multiple implementations about what should be standardized. I have looked at syslog MIB modules from multiple vendors and have not found any that model the same concepts that the current syslog MIB models.