Pekka Savola wrote:
I guess [EMAIL PROTECTED] should be listed on
https://datatracker.ietf.org/public/nwg_list.cgi
I've submitted it, let's see what Scott and Paul think, bye
___
Ietf mailing list
Ietf@ietf.org
Just for fun, you could try http://rtg.ietf.org/~fenner/ietf/ietf-63.ics ;
this is a completely independent implementation of the same mapping so
may have a completely different failure mode ;-)
Bill
___
Ietf mailing list
Ietf@ietf.org
This draft (available at
http://www.ietf.org/internet-drafts/draft-klensin-nomcom-term-00.txt)
does a reasonable job of balancing between current-generation
leadership continuity and next-generation leadership development.
I have previously expressed the opinion that an absolute prohibition
It reads in to Thunderbird OK, but the result is less pretty than
Eliot's effort. Eliot's version appears to lay out the multiple events
in a partcular timeslot evenly across the available space, whereas
Bill's results in different sized blocks and in some cases some of the
events appear to
IETF 63 Attendees:
The members of the IAOC will be holding regular office hours at the IETF
meeting in Paris. Members will be available between 3:45PM and 4:45PM on
Tuesday, Wednesday, and Thursday (August 2-4) in room 325M on the third
floor mezzanine above Hall Bordeaux. For a plan of the third
Hi Elwyn,
--On July 27, 2005 12:06:58 AM +0100 Elwyn Davies [EMAIL PROTECTED]
wrote:
It reads in to Thunderbird OK, but the result is less pretty than Eliot's
effort. Eliot's version appears to lay out the multiple events in a
partcular timeslot evenly across the available space, whereas
One important (IMHO) issue is that Bill's ics does not use timezone info
for the times.
This was a conscious decision. I think the obvious answer is to have
two versions, one with timezone and one without.
Couple of other points:
- Some lines were longer than 72 characters
Erk, I forgot
It reads in to Thunderbird OK, but the result is less pretty than
Eliot's effort. Eliot's version appears to lay out the multiple events
in a partcular timeslot evenly across the available space, whereas
Bill's results in different sized blocks and in some cases some of the
events appear to
Spencer,
At 03:18 PM 07/26/2005, Spencer Dawkins wrote:
This draft (available at
http://www.ietf.org/internet-drafts/draft-klensin-nomcom-term-00.txt )
does a reasonable job of balancing between current-generation leadership
continuity and next-generation leadership development.
I have
Spencer
Let me add my agreement to this ID as a good idea with balance.
At 05:18 PM 7/26/2005 -0500, Spencer Dawkins wrote:
This draft (available at
http://www.ietf.org/internet-drafts/draft-klensin-nomcom-term-00.txt)
does a reasonable job of balancing between current-generation leadership
I too like this draft and agree that having most IESG members serve for
two terms is ideal and making it more the exception that people serve
for three or four terms. I also like the flexibility it gives the
NOMCOM without creating strict term limits.
When someone is needed for more than
The IESG has approved the following document:
- 'HTTP Header Field Registrations '
draft-nottingham-hdrreg-http-05.txt as an Informational RFC
This document has been reviewed in the IETF but is not the product of an
IETF Working Group.
The IESG contact person is Scott Hollenbeck.
A URL of
12 matches
Mail list logo
