On 2007-01-31 18:47, John C Klensin wrote:
--On Wednesday, 31 January, 2007 17:02 + Steven M.
Bellovin [EMAIL PROTECTED] wrote:
On Wed, 31 Jan 2007 11:54:26 -0500
John C Klensin [EMAIL PROTECTED] wrote:
Except for the fact that the material being cited contains the
specifics of license
Christian Vogt wrote:
Eric -
For some reason, in your response, my bulletization of the
list of the new status codes somehow got re-paragraphed -
hopefully my version below does not suffer the same fate.
Oh, no, this was probably one of my Thunderbird extensions for nicer
quotations.
Mark == Mark Andrews [EMAIL PROTECTED] writes:
- 'The syslog Protocol ' draft-ietf-syslog-protocol-19.txt as
a Proposed Standard
Mark draft-ietf-syslog-protocol-19.txt recommends using a
Mark reliable protocol. Existing implementations of syslog do
Mark this and
Hello!
I'm trying to implement the NACK mechanism in the existing SigComp module.
I would like to know what are the expecting actions at the Compressor
side after receiving the NACK message? There are about 25 possible
errors, but I cann't see the easy way to fix all of them in Compressor
On Thu, Feb 01, 2007 at 08:09:29AM -0500, Sam Hartman wrote:
Mark == Mark Andrews [EMAIL PROTECTED] writes:
- 'The syslog Protocol ' draft-ietf-syslog-protocol-19.txt as
a Proposed Standard
Mark draft-ietf-syslog-protocol-19.txt recommends using a
Mark reliable
(Naturally, we understand that there may be ietf-dads,and ietf-spouses...)
My wife (Meaghan), who is coming to IETF68 in Prague wants to know
if there will be other non-participating parents/spouses in Prague.
To quote her: If you had told me that so-and-so was going to be in San Diego,
then
On Thu, 2007-02-01 at 08:31 +1100, Mark Andrews wrote:
- 'The syslog Protocol '
draft-ietf-syslog-protocol-19.txt as a Proposed Standard
draft-ietf-syslog-protocol-19.txt recommends using a reliable
protocol. Existing implementations of syslog do this and
deadlock
I am thinking on how to come this by on the protocol basis, but so far I
have no good clue (except that Baszi is probably right and it is a
purely operational issue). However, I know some problems in this
relation and though it is not a deadlock issue, I would like to share
the scenario for sake
Brian Carpenter wrote:
http://www.ietf.org/IESG/content/ions/drafts/ion-procdocs.html
I liked the I-D better, the xml2rfc HTML output is hard to read.
For an ION you could probably remove the dummy chapters 3 and 4.
Frank
___
Ietf mailing list
Michael Richardson [mailto:[EMAIL PROTECTED] writes:
If there is interest, I will make a list. If someone has a more PC
name, I'll use it.
As we all know, the absolutely most critically important thing about any
project, and a mailing list should be no exception, is its name. It should be
On Thu, Feb 01, 2007 at 10:08:39AM -0800, David W. Hankins wrote:
If you have 50,000 syslog lines to put out, and only enough
network/disk/something bandwidth for 5,000 within the same time
frame, that's a problem.
s/5,000/49,999/
Apologies for the clerical error.
--
David W. Hankins
Isn't IETF childcare the microphone in the big room on
Wed Thurs evenings?
Hallam-Baker, Phillip wrote:
Would this be the place to raise the issue of childcare provision at IETF
meetings?
___
Ietf mailing list
Ietf@ietf.org
Don't tempt fate.
I have seen the effect that a carefully loaded question from a ten year old can
have on such meetings.
That is how William Hague became leader of the British Conservative party.
Sent from my GoodLink Wireless Handheld (www.good.com)
-Original Message-
From:
On Thu, 1 Feb 2007, David W. Hankins wrote:
If you insist on keeping all 50,000 lines of output, there is no
solution to that problem. If you block, that's a big problem as
it ultimatley totally disables the service attempting to log
information. If you write to a growing backing store, well
On Thu, Feb 01, 2007 at 10:30:17PM +0200, Pekka Savola wrote:
It's acceptable for the syslog sender to replace overflowing lines of
syslog (if some messages need to be dropped due to lack of resources)
with a message about rate-limiting, messages being dropped, or
whatever -- just the same
Mark == Mark Andrews [EMAIL PROTECTED] writes:
- 'The syslog Protocol ' draft-ietf-syslog-protocol-19.txt as
a Proposed Standard
Mark draft-ietf-syslog-protocol-19.txt recommends using a
Mark reliable protocol. Existing implementations of syslog do
Mark this
Mark == Mark Andrews [EMAIL PROTECTED] writes:
Mark == Mark Andrews [EMAIL PROTECTED] writes:
- 'The syslog Protocol ' draft-ietf-syslog-protocol-19.txt
as a Proposed Standard
Mark draft-ietf-syslog-protocol-19.txt recommends using a
Mark reliable protocol.
On Thu, Feb 01, 2007 at 10:08:39AM -0800,
David W. Hankins [EMAIL PROTECTED] wrote
a message of 98 lines which said:
If you block, that's a big problem as it ultimatley totally disables
the service attempting to log information.
Wether it is a bug or a feature depends on your requirments.
A new Request for Comments is now available in online RFC libraries.
RFC 4628
Title: RTP Payload Format for H.263
Moving RFC 2190 to Historic Status
Author: R. Even
Status: Informational
Date: January 2007
The IESG has approved the following document:
- 'Extensions to RSVP-TE for Point-to-Multipoint TE LSPs '
draft-ietf-mpls-rsvp-te-p2mp-07.txt as a Proposed Standard
This document is the product of the Multiprotocol Label Switching Working
Group.
The IESG contact persons are Ross Callon and
The IESG has received a request from an individual submitter to consider
the following document:
- 'Use of Hash Algorithms in IKE and IPsec '
draft-hoffman-ike-ipsec-hash-use-05.txt as an Informational RFC
The IESG plans to make a decision in the next few weeks, and solicits
final comments on
21 matches
Mail list logo
