on.
>
>
> This starts a Call for Adoption for draft-bellis-dnsop-session-signal
>
> The draft is available here:
> https://datatracker.ietf.org/doc/draft-bellis-dnsop-session-signal/
>
> Please review this draft to see if you think it is suitable for adoption
> by DNSOP, and
On Fri, Jul 22, 2016 at 6:39 PM, Tim Wicinski <tjw.i...@gmail.com> wrote:
> This starts a Call for Adoption for draft-bellis-dnsop-session-signal
>
> The draft is available here:
> https://datatracker.ietf.org/doc/draft-bellis-dnsop-session-signal/
>
> Please review this d
s to
> adopt it, work on it, etc.
>
> It appears they have simplified it in the -01 version.
>
>
> This starts a Call for Adoption for draft-bellis-dnsop-session-signal
>
> The draft is available here:
> https://datatracker.ietf.org/doc/draft-bellis-dnsop-session-signal/
>
On 26/07/2016 16:03, Shane Kerr wrote:
> I think the document itself needs some work (such as more detailed
> motivation statement, some use cases, probably getting rid of "terminate
> session", and so on).
>
> At first I thought that this should stay in homenet, but it does use a
> lot of DNS
plified it in the -01 version.
>
>
> This starts a Call for Adoption for draft-bellis-dnsop-session-signal
>
> The draft is available here:
> https://datatracker.ietf.org/doc/draft-bellis-dnsop-session-signal/
>
> Please review this draft to see if you think it is suitable for
they have simplified it in the -01 version.
>
>
> This starts a Call for Adoption for draft-bellis-dnsop-session-signal
>
> The draft is available here:
> https://datatracker.ietf.org/doc/draft-bellis-dnsop-session-signal/
>
> Please review this draft to see if you