Re: [Taps] updated agenda - Re: Transport Services (taps) WG Virtual Meeting: 2019-05-08

Could we please add some time to discuss the parameters and defaults - 
Phil has been trying to get these into shape for some time and the text 
in the iD has evolved to a place where decisions now need to be made, 
and I'd really rather this was not pushed to the end of the agenda as 
"other issues".

In API, this relates to (this may also finally touch implementation):

Default for Use 0-RTT session establishment #314
Default for Control checksum coverage #315
The recommended default and can we specify rather than recommend? #317
Section 7 default #319

Gorry

On 07/05/2019, 19:52, Aaron Falk wrote:
>
> Collating the input from the thread. Who will lead the discussion on 
> the implementation draft?
>
> --aaron
>
> Agenda:
>
>  1. Framing - Tommy
>       * See https://github.com/ietf-tapswg/api-drafts/pull/323
>  2. Implementation draft - ??
>       * See https://datatracker.ietf.org/doc/draft-ietf-taps-impl/
>  3. Yang Model - Jake
>       * See
>         https://github.com/GrumpyOldTroll/python-asyncio-taps/blob/master/PyTAPS/modules/ietf-taps-api.yang
>  4. ARCH & API issue scrub & assign - Brian
>       * See https://github.com/ietf-tapswg/issues
>
>
>
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps