On 2007-11-26, at 22:11, ext Henrik Levkowetz wrote:
I agree on the general sentiment of *one* deadline time.
I'd prefer it expressed in a TZ which iCalendar files and most
calendar
applications understand right off, though. UTC sounds good to me.
Let me put in a plug for
Phillip,
Looks to me as if the cut off is start of business for the RFC Editor.
That makes sense to me, no matter how much you try to change the cut
off you can't make it any later than the point where the editor needs
to start work.
No, the RFC Editor does not edit drafts after the cutoff,
Spencer Dawkins wrote:
Laksminath's note is more detailed, but it's roughly what I was thinking
at about 2 PM EST today :-(
I'm sure there's an opportunity for us to pick a time zone for IETF 71
cutoffs!
you mean like UTC?
I'd note that all the reference times in this message were in the
Spencer Dawkins wrote:
Laksminath's note is more detailed, but it's roughly what I was thinking
at about 2 PM EST today :-(
I'm sure there's an opportunity for us to pick a time zone for IETF 71
cutoffs!
you mean like UTC?
:-)
OK, guilty. My point was that the cutoff time seemed to be
From my point of view, it can be any timezone as long as the cutoff
time is the same in all cases. While we are on topic, I propose to use
AOE as defined by IEEE (I think 802.16).
regards,
Lakshminath
On 11/26/2007 10:33 AM, Spencer Dawkins wrote:
Spencer Dawkins wrote:
Laksminath's note
At Mon, 26 Nov 2007 10:39:03 -0800,
Lakshminath Dondeti wrote:
From my point of view, it can be any timezone as long as the cutoff
time is the same in all cases. While we are on topic, I propose to use
AOE as defined by IEEE (I think 802.16).
AOE == UTC-1200. UTC seems much more natural.
Just in case you are not familiar with AOE, it stands for Anywhere on
Earth (See http://www.ieee802.org/16/aoe.html)
regards,
Lakshminath
On 11/26/2007 10:39 AM, Lakshminath Dondeti wrote:
From my point of view, it can be any timezone as long as the cutoff
time is the same in all cases.
Yeah, I can deal with any TZ actually (AOE is one suggestion and I think
most intuitive, UTC is another), but can't handle the varying cutoff
times :).
On why AOE is intuitive, everyone gets to treat the deadline with their
own TZ substituted for AOE (the actual deadline for most people would
On 2007-11-26 19:55 Lakshminath Dondeti said the following:
Yeah, I can deal with any TZ actually (AOE is one suggestion and I think
most intuitive, UTC is another), but can't handle the varying cutoff
times :).
On why AOE is intuitive, everyone gets to treat the deadline with their
]
Sent: Mon 26/11/2007 1:33 PM
To: Joel Jaeggli
Cc: IETF Discussion
Subject: Re: Our deadlines are dizzyingly complex and confusing
Spencer Dawkins wrote:
Laksminath's note is more detailed, but it's roughly what I was thinking
at about 2 PM EST today :-(
I'm sure there's an opportunity for us
From: Lakshminath Dondeti [EMAIL PROTECTED]
Just in case you are not familiar with AOE, it stands for Anywhere on
Earth (See http://www.ieee802.org/16/aoe.html)
Cool concept: the deadline [time] has not passed if, anywhere on earth, the
deadline date has not yet passed. I like it.
And, just to keep Henrik sane, it looks like
http://en.wikipedia.org/wiki/List_of_time_zones#UTC.E2.88.9212.2C_Y should
be a real time zone that calendaring systems could understand (as opposed to
AOE) - did I get this right?
Spencer
From: Lakshminath Dondeti [EMAIL PROTECTED]
Hi,
I just found out that I missed the deadline for early-bird registration
and payment. I registered early, but was planning to pay just in time,
but alas the deadline has passed. I was thinking that the deadline is
later in the day, end of the business day Eastern time.
We have
Laksminath's note is more detailed, but it's roughly what I was thinking at
about 2 PM EST today :-(
I'm sure there's an opportunity for us to pick a time zone for IETF 71
cutoffs!
Thanks,
Spencer
Hi,
I just found out that I missed the deadline for early-bird registration
and payment.
14 matches
Mail list logo
