Opened 8 years ago

Closed 8 years ago

#22 closed defect (fixed)

a short notice change will affect current meeting times

Reported by: lester Cain Owned by: cyrus@…
Priority: major Milestone:
Component: service Version:
Severity: Active WG Document Keywords:
Cc:

Description

Either the service is to provide timezone data in it's entirety, or it
should identify the fact that it is only really intended to support
'modern day' timezone information. But even here, I don't think proper
consideration has been given to passing on current updates to timezone
information in a reliable manor.

Isn't it sufficient to advertise the "truncation" dates as we do now? I
agree that perhaps we should have a clearer idea of the lower bound

The grey area I'm still looking at here is not 'truncated' data, but
where a short notice change will affect current meeting times. The
result should be a 'changedsince' return, but because there is no clear
indication that the dtstart on one server will be mirrored on a backup
server, the backup machine may not give a response because it had
already updated prior to the recorded dtstart. Living in an area where I
use multiple network connections depending on what is working, I can see
different machines responding and so while ideally one would only access
one server, that can't be guaranteed? Mobile access may use a different
routing to land line?

Am I correct if I understand that 'changesince' is associated to a specify server. Are you suggesting something like a globel version accross the different system a bit like the SOA in DNS?
On the other hand, adopting document as Working Group Document does not mean acceptation of documents as there are. If some limitations are raised, then the WG will need to fix them. Adopting the document means that we believe the modifications for enhancement are smaller than re-designing from scratch a complete protocol. Considering the level of detail we are discussing, I understand you remark as documents coudl be adopted, but may not be the final version, sent to the IESG.

Change History (2)

comment:1 Changed 8 years ago by lear@…

  • Component set to service
  • Owner set to cyrus@…
  • Severity changed from - to Active WG Document

comment:2 Changed 8 years ago by lear@…

  • Resolution set to fixed
  • Status changed from new to closed

This is tied to the version resolution. Will close and address in Issue 32.

Note: See TracTickets for help on using tickets.