Re: [Taps] Prague agenda planning

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 Policy Management component. The HE algorithm makes 
certain assumptions on what it provides, but it is not part of the HE 
algorithm itself.

Two topics to discuss about the draft would be:
* the interface between the HE algorithm and the policy management
* what should be detailed in the specification of the HE algorithm and 
what should be left open for implementation

Cheers,
Anna

On 2017-06-29 21:53, Aaron Falk wrote:
>
> 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
>         protocols
>       * The ability to separate security handshakes from data encryption
> 3.
>
>     *Socket Intents, Concepts & Communication Granularity*, Phillipp
>
> 4.
>
>     *Application- & System-Specified Policy & TAPS*, Brian? Tommy?
>
> ------------------------------------------------------------------------
>
>   * Michio Honda HotNets paper “PASTE: Network Stacks Must Integrate
>     with NVMM Abstractions
>     <http://www.ht.sfc.keio.ac.jp/%7Emicchie/papers/paste-hotnets16.pdf>”
>       o /“These days I'm working on networking interface for
>         non-volatile main memory (a.k.a. persistent memory and
>         storage-class memory), because with such devices networking
>         stack/API becomes a bottleneck in the end-to-end communication
>         that involves persistent media (disk or SSDs for now). I saw
>         some post-socket discussion in the minutes of the last
>         meeting, so I wonder if this type of work could give some
>         useful information to IETFers who design new transport API
>         standards.”/
>       o Is there interest in this topic? AFAIK, there’s no Internet
>         Draft. I will inquire whether Michio intends to submit one.
>         May end up in TSVAREA
>
>
>
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps