Re: [V3] Thoughts on scope for ript

Eric Rescorla <> Mon, 23 March 2020 14:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CD8153A08C7 for <>; Mon, 23 Mar 2020 07:50:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Tqz20B8q8IJK for <>; Mon, 23 Mar 2020 07:49:59 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9EF083A08AD for <>; Mon, 23 Mar 2020 07:49:58 -0700 (PDT)
Received: by with SMTP id r24so14931813ljd.4 for <>; Mon, 23 Mar 2020 07:49:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zCigoqCO8pYn81XHHrh4/LMnQoXwnhAkr1fMi9oBSag=; b=IWNNxcYKd7BjFlm9gmjeFLcsD9x0F5ldxody+yE9Su3Govbjb4DHAJaMGXHoMaazAc VFAFRsloQ/88ih8lJwUIvOV1poeRYDBNCl1ERQLuEPRzqQCjR7QFDhgJZn8A2pTnqNaZ 1cVEWGffg3SHokmQP132WpmG2mwSvvQzJMNQdehhqzSR57PuX3oLpw6BsgnHW7f38SI9 fieqh45ZTlk03Hyi11c5IeFvXoPbkcM1BGbBkNmY7+OQqPDrYFx9+9AJlNkIU7Ve1bYH k25MCFRHaImpeU1SHGoZfxj7AIi3fTh4Sb5Q/Rirdr7Wi0mvFYGB1uwTNtKReJ0aBf3M CVSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zCigoqCO8pYn81XHHrh4/LMnQoXwnhAkr1fMi9oBSag=; b=qhk0fhsQFxp+dciB7FNKYuqNIjusbhWu+dMS/lL8I5fEj4agaGwsHISccxNNsKIi2P I4tOOrvdjHVpTqDxu5QS7Lx/gScuFV1FxEZhwbQ237KSYj4biVTSEROooDtrsekOA7Xv vBcHNNQQuUZE2jO1g5TYZxgpw/getHYHF2YmEX7BcOiJnWBs+nG7ObrYJhlJbauTqHeu zp0ACgIzCuyxLXYHuIyJ3hMrFiT/hA0e+nUR+PA1+GqsexzA8/I7CTpRGIuvku5MFabD 9vrWc/86BmABjKWY4rDeBBVITwNGi3n10nbOsXqBh7IolxGpXNKyJtRkuuGrYGkYsvJA d/+Q==
X-Gm-Message-State: ANhLgQ00GWBsGk6IONPq/aNUDwbuN7PeHVbusk4YGLlGyzsZSIx+DGil xropIzyy9tAmRgkqPHUjGkRfe8MyvmmpMceFqnnYNc2F90A=
X-Google-Smtp-Source: =?utf-8?q?ADFU+vukrq86JOh/P0f4tLMeO1Z7DW3Ia/P6A6r4aBN9?= =?utf-8?q?+Ri3QMxtCviQi2eSbx/HjHAJPg6wxDAHDpUhloldJLkmZwA=3D?=
X-Received: by 2002:a2e:81cc:: with SMTP id s12mr14434257ljg.35.1584974995678; Mon, 23 Mar 2020 07:49:55 -0700 (PDT)
MIME-Version: 1.0
References: =?utf-8?q?=3CBYAPR06MB4391FBC64E195E87003061B8FBF00=40BYAPR06MB4?= =?utf-8?q?391=2Enamprd06=2Eprod=2Eoutlook=2Ecom=3E?=
In-Reply-To: =?utf-8?q?=3CBYAPR06MB4391FBC64E195E87003061B8FBF00=40BYAPR06MB?= =?utf-8?q?4391=2Enamprd06=2Eprod=2Eoutlook=2Ecom=3E?=
From: Eric Rescorla <>
Date: Mon, 23 Mar 2020 07:49:19 -0700
Message-ID: <>
To: Jonathan Rosenberg <>
Cc: "" <>
Content-Type: multipart/alternative; boundary="00000000000098786f05a186bf8e"
Archived-At: <>
Subject: Re: [V3] Thoughts on scope for ript
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 23 Mar 2020 14:50:11 -0000

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.



On Mon, Mar 23, 2020 at 7:21 AM Jonathan Rosenberg <>

> 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