Subject: [drinks] UPDATED DRAFT minutes of the DRINKS design team call 2012-05-24

From: Alexander Mayrhofer <[email-masked]>
Date: Tue, 29 May 2012 13:21:59 +0000

I've updated the minutes from last weeks design team call - see below: 

- Most importantly, call this week will take place on WED and FRI - contrary to what was given in the last draft minutes
- Secondly, i've updated Sumanth's statement regarding "power of the design team".

thanks & sorry for the confusion,

Alex

DRINKS Design Team Call - DRAFT minutes
=======================================

May 24 2012, 10am - 11am Eastern

Participants
------------

- Dean Willis
- Vikas Bhatia
- Manjul Maharishi
- David Schwartz 
- Alexander Mayrhofer
- Syed Ali
- Ken Cartwright
- Sumanth Channabasappa 

ACTION ITEMS
------------

- Continue discussion of remaining open items
- Provide descriptions of 3 other remaining "main" issues
- Provide arguments for egress route to mailing list (Syed)

Agenda
------

1/ Work on documented open issues

Minutes
-------

Sumanth opens the call, the group decides to go forward with one select issue.

Alex/Sumant explain that there were 4 main issues, and the one currently 
described issue ("Data Type" issue) contains 4 "sub-issues".

Alex proposes to start with the "renaming rte rec to sed rec" sub-issue, but
Vikas explains that his concern about renaming rte rec to sed rec is 
connected to the decision about target/location split, so the two should be 
combined.

Based on that, the agreement is to tackle the egress route first, which is 
being discussed subsequently

David explains that the only purpose of egr route is to rewrite routes 
by the consumer of route recs, so why does that go into the registry?
Says he wanst to make it a more generic concept, in which case it 
would make sense to share via the registry

Vikas is not completely opposed to changes, but wants to ensure that 
the egress route use case is covered, and wants to see what other use 
cases that generic mechanism would cover.

Alex says: concerned that generalization might imply the definition 
of a whole new range of required semantics. 

Dean: Is an egress route mandatory, or optional? When do you use it?

There is extensive discussion around those issues.

Sumanth summarizes: Do we want to have a generic rule or not?
would have to define its use very clearly (likely lots of effort) - 
difference whether we should make changes (a new mechanism) or 
do we just need to clarify what's there?

David says, making it generic makes it shareable, and hence then 
it would "fit" into a registry which very purpose is to share data. 
Is this protocol to provision private data?

Ken: This is a feature that is out there. Document is very clear 
about how it is applied. If unclear, please suggest text on the list.

Vikas: two basic questions - do we want to keep it or not? And if yes, 
seperate question whether we want to generalize it or not? 
Would create totally new use cases that we have been unaware so far.

Sumanth: Q: Does current mechanism solve use case?
David: Yes, but in a inconsistent way for the protocol (private data)

Vikas: Generic mechanism proposed by David does not solve 
the egress use case!

Sumanth: We can discuss and vote within the design team, and propose the results as a recommendation to the DRINKS mailing list. WG participants can then chime in, resulting in a final decision (as the WG). 

Dean: Only concern is the sharing of private date in the registry. Alex agrees.

Syed: Private data: typically contracts in place, and it's an 
*option*. Nobody forced to use it. Plus, IP addresses are typically 
from a private network range.

Sumanth: Let's make a decision, now.

Sumanth: Proposal: Let's keep egr route as it is, and clarify that 
it's optional. Who's in favor / who objects? David is the only 
participant who objects.

Sumanth: 2nd question: Any objection on keeping the scope, and 
not extending? Proposing we don't look at extending it.  No objections

Conclusion: egress route definition will stay in the protocol as 
currently defined, we need to clarify a few points - Syed mentioned
a range of good points, and will send these out of the mailing list.

Next calls: There will be two calls next week, Wed and Fri.

Call concludes.