> On 19 Apr 2018, at 16:26, Aaron Falk wrote:
>
> Updated:
>
> First Priority: maprg dispatch tcpm iccrg tsvwg ippm rmcat tsvarea quic panrg
> tls
> Second Priority: tcpinc mptcp saag mmusic tram irtfopen
>
I have drafts in AVTCORE and RTCWEB, so it’d be good if they could be on the
list.
-
Hi Aaron,
I’m also an author/editor for capport and ipsecme, so I’d like to add those to
the list if possible.
Thanks,
Tommy
> On Apr 19, 2018, at 8:26 AM, Aaron Falk wrote:
>
> Updated:
>
> First Priority: maprg dispatch tcpm iccrg tsvwg ippm rmcat tsvarea quic panrg
> tls
> Second Priorit
Updated:
First Priority: maprg dispatch tcpm iccrg tsvwg ippm rmcat tsvarea quic
panrg tls
Second Priority: tcpinc mptcp saag mmusic tram irtfopen
Any other input?
--aaron
On 17 Apr 2018, at 11:46, Christopher Wood wrote:
On Tue, Apr 17, 2018 at 8:39 AM Brian Trammell (IETF)
wrote:
O
On Tue, Apr 17, 2018 at 8:39 AM Brian Trammell (IETF)
wrote:
> > On 17 Apr 2018, at 17:22, Aaron Falk wrote:
> >
> > Hi Folks-
> >
> > We should update our conflict list for scheduling TAPS meetings during
the IETF week. Here’s the algorithm I’d like you to consider:
> >
> > • If you are
> On 17 Apr 2018, at 17:22, Aaron Falk wrote:
>
> Hi Folks-
>
> We should update our conflict list for scheduling TAPS meetings during the
> IETF week. Here’s the algorithm I’d like you to consider:
>
> • If you are an author/editor in TAPS and an author/editor or chair in
> another w
ACK - works for me, I'd love to add: intarea (as a contributor, and
TSVWG reviewer).
My own conflicts map to what you have:
First Priority: maprg tcpm iccrg tsvwg tsvarea
Second Priority: rmcat, quic
Gorry
On 17/04/2018, 16:22, Aaron Falk wrote:
Hi Folks-
We should update our conflict lis
Hi Folks-
We should update our conflict list for scheduling TAPS meetings during
the IETF week. Here’s the algorithm I’d like you to consider:
* If you are an author/editor in TAPS and an author/editor or chair in
another wg, that is a first priority conflict
* If you are a contributor to TA