[drinks] DRAFT minutes of the DRINKS design team call on 2012-05-08

[Alexander Mayrhofer <[e-mail]>]

DRINKS Design Team Call DRAFT minutes - May 08 2012, 10am - 11am EST
====================================================================

Participants:
-------------
- Ken Cartwright
- Sumanth Channabasappa 
- Vikas Bhatia
- Alexander Mayrhofer
- Dean Willis


Agenda
------

1/ Document open issues

Action items
------------

0/ Research and describe status of the four remaining issues (as below)

Minutes of the call
-------------------

Sumanth opens the call, proposes in order to address the open issues to:

- list all open items
- get a clear definition of each of them
- decide how to proceed with each item

There was one open item from posting the new docs, which was the discussion
about "peering" (combined with the "route group offer" generalisazion)

Furthermore, the internationalization issue is also still open. Then 
more open items were added in Paris
 
(Sumanth opens up the .rtf notes that he uploaded to the meetings 
material page - they seem to be different from what is shown on the 
tools.ietf.org page.)

Two more issues were discussed in Paris, which makes the total list of 
open issues:

- route group type issue (added during Paris meeting)
- denial of service considerations (added during Paris)
- peering / route group offer generalization 
- internationalization

(Ken noted that i18n is still open - added as fourth items)

The status of each of the items was then discussed.

No concensus was reached on the route group type in Paris - discussion 
about value of that mechanism.

Peering: had a few emails around that, Dean posted a proposal text to the 
mailing list.

Denial of Service: Jeremy presented, we might need additional text in the 
document to address those concerns.

Internationalization: Text proposed, comments from Ken received. 

Vikas an Ken note that they have limited resources during this and 
the next week.

Sumanth proposes that we should assign each item to a participant of the call,
who should then research the current status of the item, so that we 
could address the item with all available information during one of the next 
calls.

Sumanth proposes to take on DoS considerations, Alex proposes taking on i18n.

There is an discussion about what exactly the "Peering / route group offer" 
open item should compromise, and whether that wasn't already solved? There 
is agreement that we won't change the core of the protocol

Ken notes: if we removed it, do we create a "peering protocol" 
without any peering? 
Ken said he didn't like the new intro text, but he can live with it.

Dean: The problems of of how/whether we do peering, and the route record generalization (using URIs) are differnt problems. ("SED data type" thread).

DoS: Ken notes that for example EPP do not mention DoS considerations at all.. Sumanth says that DoS is part of the security considerations in most cases.

Dean: RFC3552 describes how to consider DoS in security consideration sections. 

Alex: summing up the individual issues was to be assigned to a certain person:

- route group type issue (added during Paris meeting) => Alex
- denial of service considerations (added during Paris) => Ken 
- peering / route group offer generalization => Sumanth
- internationalization => Alex

Sumanth originally offered to take the DoS issue, Ken offeres to take 
that one over.

Ken: keep i18n simple. 
Alex: Yes, should be limited to things that are required to ensure interopability.

Next call: next wed at usual time. summarize issues until then.

Call concludes.