Re: [V3] Thoughts on scope for ript

Hi Jonathan,

As I said in my review [0] I don't think that the current draft achieves
this, and I think it's lead to a number of fairly misguided design
decisions (with byways being perhaps the most obvious).

More to the point, the future is bigger than the past. H3 is not widely
deployed yet, and so we should think about how we want things to look, not
tie ourselves in knots trying to fit the precise current environment copied
onto H3.

-Ekr

[0] https://mailarchive.ietf.org/arch/msg/v3/V2BuGEZJpEMcAKcYLNHDMtV3i70/

On Mon, Mar 23, 2020 at 7:21 AM Jonathan Rosenberg <jdrosen@five9.com>
wrote:

> With our BoF coming up this Thursday, I thought the time is right to
> restart discussions with a focus in particular on SCOPE of the effort.
>
> For me its defined entirely by the GOAL. The goal is:
>
> It is possible to implement a ript server in public cloud, such that it is
> nothing more than a web application as far as public cloud is concerned,
> and therefore works with web-centric features such as Kubernetes, global
> http load balancers, and service meshes - to name a few. The server
> implements everything needed to make and receive voice and video calls.
>
> I do think the scope needs to be inclusive of server to server peering,
> not just client to server. The client-to-server stuff defines the core, but
> for me I'm really interested in building an alternative to sip trunking and
> that requires solving for additional things (inbound load balancing,
> inbound authentication, number routing). I think those can easily be in a
> separate draft but I think they should be in scope.
>
> Thx,
> Jonathan R.
>
> --
> Jonathan Rosenberg
> CTO and Head of AI, Five9
>
>
> ________________________________
>
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain
> confidential information of Five9 and/or its affiliated entities. Access by
> the intended recipient only is authorized. Any liability arising from any
> party acting, or refraining from acting, on any information contained in
> this e-mail is hereby excluded. If you are not the intended recipient,
> please notify the sender immediately, destroy the original transmission and
> its attachments and do not disclose the contents to any other person, use
> it for any purpose, or store or copy the information in any medium.
> Copyright in this e-mail and any attachments belongs to Five9 and/or its
> affiliated entities.
>
> --
> V3 mailing list
> V3@ietf.org
> https://www.ietf.org/mailman/listinfo/v3
>