Updated.
0. **Agenda Bash & Working Group Status**, Aaron Falk & Zahed Sarker, 10
min
1. **Minimal Set of Transport Services for TAPS Systems**, Naeem Khademi
(presenting for authors), 20 min
* `draft-gjessing-taps-minset-05.txt`
* What’s new: the abstract API
2. **Transport Security P
I don’t have a preference. I was assuming
1. frame the topic
2. look at a few applications / use cases
3. discuss / wrestle / free-for-all
but I’m also ok with
1. example 1, 2, 3
2. abstract / summarize some questions
3. discuss / wrestle / free-for-all
I’ll leave whoever wants to take the fr
As did I. But if we want to separate the discussions more explicitly, I'm happy
to throw together five minutes of slides to frame the discussion in a
proposal-neutral way; I think we'll need at least twenty for the discussion
though.
Cheers,
Brian
> On 06 Jul 2017, at 17:20, Mirja Kühlewind
I believe the idea was actually to have the policy after the socket intents
talk; maybe even after HE?
Mirja
> Am 06.07.2017 um 16:56 schrieb Aaron Falk :
>
> Updated. Still need a policy framing preso (#4) and timing.
>
> • Minimal Set of Transport Services for TAPS Systems, Naeem Khad
Updated. Still need a policy framing preso (#4) and timing.
1. **Minimal Set of Transport Services for TAPS Systems**, Naeem Khademi
(presenting for authors)
* `draft-gjessing-taps-minset-05.txt`
* What’s new: the abstract API
2. **Transport Security Protocol Survey**, Tommy Pauly
* At
1. **`draft-gjessing-taps-minset-05.txt`**
* There’s been some interesting discussion on the draft. Are
there any specific topics we should set aside time to discuss?
I think it makes sense for this presentation to focus on what’s new:
the abstract API that we designed. I think this
> On Jul 5, 2017, at 6:42 PM, Aaron Falk wrote:
>
>
>
> On 29 Jun 2017, at 16:53, Michael Welzl wrote:
>
>>> 1. **`draft-gjessing-taps-minset-05.txt`**
>>>
>>>* There’s been some interesting discussion on the draft. Are there any
>>> specific topics we should set aside time to discuss?
Updated:
1. **Minimal Set of Transport Services for TAPS Systems** [[XX who will
present? XX]]
* `draft-gjessing-taps-minset-05.txt`
* Open issues to finalize doc
2. **Transport Security Protocol Survey**, Tommy Pauly
* At the meeting in Chicago, the question of how security protocols
On 29 Jun 2017, at 16:53, Michael Welzl wrote:
1. **`draft-gjessing-taps-minset-05.txt`**
* There’s been some interesting discussion on the draft. Are
there any specific topics we should set aside time to discuss?
I appreciated this discussion much, but personally I don’t think
kn
Hi Aaron, all,
We plan to submit an update to the happy-eyeballs draft before the
cut-off and would like to add that to the agenda as well. The update
aims to address the feedback received so far.
I think it fits nicely with the policy discussion. The HE framework in
the draft includes a Po
Hi All,
On Thu, Jun 29, 2017 at 10:09 PM, Michael Welzl wrote:
> I think it's time to level up and have a discussion about "policy" and how
> it relates to TAPS.
>
> I'm going to leave the definition of "policy" here deliberately vague with
> the hope that we can start to build some terminology
Hi all,
> On Jun 29, 2017, at 7:09 PM, Tommy Pauly wrote:
>
>
>
>> On Jun 29, 2017, at 9:07 AM, Brian Trammell (IETF) wrote:
>>
>> hi Aaron,
>>
>>> On 29 Jun 2017, at 17:36, Aaron Falk wrote:
>>>
>>> Updating. Our agenda time is much more productive if we can home in on
>>> specific que
Hi,
In line:
> On Jun 29, 2017, at 9:53 PM, Aaron Falk wrote:
>
> Updated:
>
> draft-gjessing-taps-minset-05.txt
>
> There’s been some interesting discussion on the draft. Are there any specific
> topics we should set aside time to discuss?
I appreciated this discussion much, but personall
Updated:
1. **`draft-gjessing-taps-minset-05.txt`**
* There’s been some interesting discussion on the draft. Are there
any specific topics we should set aside time to discuss?
2. **Transport Security Protocol Survey**, Tommy
- The common features/interface presented by various security
> On Jun 29, 2017, at 9:07 AM, Brian Trammell (IETF) wrote:
>
> hi Aaron,
>
>> On 29 Jun 2017, at 17:36, Aaron Falk wrote:
>>
>> Updating. Our agenda time is much more productive if we can home in on
>> specific questions to discuss rather than just give document overviews.
>> Authors & ot
Hi Aaron,
> On 29. Jun 2017, at 18:07, Brian Trammell (IETF) wrote:
>
> hi Aaron,
>
>> On 29 Jun 2017, at 17:36, Aaron Falk wrote:
>>
>> Updating. Our agenda time is much more productive if we can home in on
>> specific questions to discuss rather than just give document overviews.
>> Autho
hi Aaron,
> On 29 Jun 2017, at 17:36, Aaron Falk wrote:
>
> Updating. Our agenda time is much more productive if we can home in on
> specific questions to discuss rather than just give document overviews.
> Authors & other folk: what’s interesting, unclear, or controversial here?
I think it's
Updating. Our agenda time is much more productive if we can home in on
specific questions to discuss rather than just give document overviews.
Authors & other folk: what’s interesting, unclear, or controversial
here?
* `draft-gjessing-taps-minset-05.txt`
* There’s been some interesting di
… and the latest version of the minset draft excludes security from the final
minset, mentioning that this will be addressed in a separate draft (which
should be this one).
Cheers,
Michael
> On Jun 27, 2017, at 11:33 PM, Tommy Pauly wrote:
>
> Yes, we’d like to add this as a WG item once pub
Yes, we’d like to add this as a WG item once published. This is based on the
conversation had at the meeting in Chicago about wanting a draft to include
Security protocols for TAPS API considerations.
Thanks,
Tommy
> On Jun 27, 2017, at 1:44 PM, Aaron Falk wrote:
>
> Cool. Are you proposing t
Cool. Are you proposing this as a wg item?
--aaron
On 27 Jun 2017, at 16:22, Tommy Pauly wrote:
Hi Aaron,
We have a draft we’ll be publishing in the next week that does a
survey of Transport Security protocols, and the interfaces they expose
to the transport layer as well as applications.
Hi Aaron,
We have a draft we’ll be publishing in the next week that does a survey of
Transport Security protocols, and the interfaces they expose to the transport
layer as well as applications. We’d like to have a slot to discuss this topic
with the WG.
Thanks,
Tommy
> On Jun 27, 2017, at 12:
Here the short list of topics recently raised for our next meeting and
some questions/comments. Please respond and suggest any other topics.
* `draft-gjessing-taps-minset-05.txt`
* There’s been some interesting discussion on the draft. Are there
any specific topics we should set aside time
23 matches
Mail list logo
