![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
regards, Lakshminath
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 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 "close of business, ET", and I was kinda hoping that whatever time we picked would be "close of business, a little further west" :-)
... especially if we were headed toward using the same cutoff TIME for all IETF cutoffs (BOF requests, WG meeting requests, registration, ID cutoffs, etc) ...
Thanks,
Spencer
I'd note that all the reference times in this message were in the same timezone just not at the same time. I submit that I really hate having to convert the offset from my current timezone in someone else's particularly when I can't remember when their daylight savings time begins or ends. however the challenge really is that they're not all in my calender rather than than that I need to calculate the offset because software will happily do that for me.
Thanks,
Spencer
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.