SEDATE Minutes

Mark gave the notewell and intro.

Chairs will decide whether this group has more to do after this doc.

Carsten presenting slides

Introduction, Recent History, Status and Documents, Chairs, 3 min.

Document, draft-ietf-sedate-datetime-extended-06, Ujjwal Sharma, Carsten
Bormann (GitHub:
https://github.com/ietf-wg-sedate/draft-ietf-sedate-datetime-extended/ )
45 min.

If needed, liaison to ISO/TC154. Mike Douglass, 7 min.

AOB, 5 min.

• We found an issue with RFC3339
• No floating times

Nothing generates -00:00 since ISO8601:2000 disallowed it.

Ujwall:

• When we started this group, there were ambitions to revamp 3339 -
  add extended years, etc.
• This faced a lot of resistance, and we decided to go with a more
  conservative approach.
• While I'm with you that the charter restricts us, there is a reason
  why the charter is explicit on this.

Francesca:

• was going to say what Ujwall said.
• want to know if there will be resistance to consensus on changing
  RFC3339

Carsten:

• surprised that there was no discussion that questioned what we were
  trying to do.
• once people saw what we wanted, there was no pushback.
• my assessment, not strong opposition

Mark:

• as chair we need to be clear about two things.
• could document in current draft that this exists. Use that to
  support background to rechartering.
• two tasks, current

Bron:

• the issue with 3339 was that people didn't want to break existing
  parsers.
• propose that we document this issue in this draft, publish with a
  "MUST NOT generate in this format".
• THEN we recharter.

Carsten:

• we have a problem that in 8000 years this won't work. Intention here
  is a common format for libraries like temporal, etc.

Francesca:

• talk to ISO?

Mike:

• ISO committee is sort of wrapping up. Got in fairly late.
• If we put together a message I can pass it across and see what
  happens.

Carsten:

• what we're fixing isn't stuff we imported from 8601, it's our own
  invented interpretation of things from 8601.
• From the point of view of TC154, we're getting more compliant.

Mike:

• don't know that it's something that effects 8601.
• SUMMARY: existing SEDATE document is in last call, haven't heard any
  objections to moving that document forward. Are there any?
• Chairs should work with AD to start discussion about conservative
  rechartering of SEDATE to take care of problem in 3339. Maybe go to
  list with proposed charter text.
• If we do this, we should communicate to ISO that we've found the
  problem, it's our problem, and let them know what we're doing to fix
  it.
• If we're going to persue revising charter, want that by next IETF.

No other business, done 21 minutes early.