Re: [dispatch] Virtual IETF107 - SRT draft is available

Eric Rescorla <> Wed, 18 March 2020 16:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 778253A182C for <>; Wed, 18 Mar 2020 09:30:48 -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 J4jLVDfT2UsF for <>; Wed, 18 Mar 2020 09:30:46 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::12b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DA8B83A07AD for <>; Wed, 18 Mar 2020 09:30:45 -0700 (PDT)
Received: by with SMTP id f3so10680563lfc.1 for <>; Wed, 18 Mar 2020 09:30:45 -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=6c1WMXz5pZJAJFZpab4Ri5sbubq27yKqaUp6e+nQ3tA=; b=Y2m+8GWdsjeW6MoKkua58ZvxgBFXznFWbC6OlJ+MCS2vfiqRw2Sl0mxZffE17R07oo 7vDz0e3EFmbppoo2Iw98DrXTQKnYl2lJumQOpFlVIbK/BaCN8tGizDQ7eZZx8PHXV9Pz ujq+5ueomkP3YI3hbSAnmdzCDi+zWso5JtHT8XVbQRCIgvSyS4B/hiD4thA4VH2ICiji GvgUXw9YCBkKvjp8O9yq/vJ+dW37t3vGPpqrGE889TIJOQ7fqYUn1TPP+swkLIHrRSPS q0FMw4XYHEMh6yTUT2NBEYMYXN9MZkBg7wXZ72vuVd4L+oEBRD5EcDdMRIYS+A7jS+ac ta1g==
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=6c1WMXz5pZJAJFZpab4Ri5sbubq27yKqaUp6e+nQ3tA=; b=mVBaqQ2/hP4SnTolkux0+Q+xhVjEjMIaDnc82/6kP5HW5A3eHx/Ej3ee3ee7sCZ606 t+uPoATK1NVUb3ZZSYVx6M6f7KjhzMhBHzgseiynx/UKiYut0hOFnr2WJwUWd/6mdfDo KORQj+X6HJyAIpvIXyP3+lVdoTVwNhAtC/eGjx325i4yg34HAS4rPjlOucqLlgwowHck kZXIDnma97E5GDMm9YGtePEEsdWHuwH/JS5nLor5bjLp7xSHCAROq5AQihdk0SRwFmZz pgDtLjtNX9XMHrdPWH57rz/0hYwKEUnDkkU5UmDspq8NktqOjL5snb/4/Zx1WHXvJqeT XUgg==
X-Gm-Message-State: ANhLgQ2lt/vmHaDDH3sze9cQtZxMtDD9d/Zc2lf+nY+5T/dW8PCHEiiH AecMM+vWSzNWhBYvs1McI+9aDDYCilXOLCassFwy3g==
X-Google-Smtp-Source: ADFU+vvoqQ7NHtLBoxQUv0HtFNrg7Oh+3V/TpfFRvnbt9E/8asxdir7+ICV9ba9VIf2ceqBzoPBfMdd9ZXjNSppDp2U=
X-Received: by 2002:ac2:593a:: with SMTP id v26mr3403848lfi.109.1584549044011; Wed, 18 Mar 2020 09:30:44 -0700 (PDT)
MIME-Version: 1.0
References: <SL2P216MB047407C8AA07BAA52CDF907EEFF70@SL2P216MB0474.KORP216.PROD.OUTLOOK.COM>
In-Reply-To: <SL2P216MB047407C8AA07BAA52CDF907EEFF70@SL2P216MB0474.KORP216.PROD.OUTLOOK.COM>
From: Eric Rescorla <>
Date: Wed, 18 Mar 2020 09:30:07 -0700
Message-ID: <>
To: "김준웅님(JOONWOONG.KIM)" <>
Cc: "" <>, "" <>
Content-Type: multipart/alternative; boundary="000000000000e5db2705a1239210"
Archived-At: <>
Subject: Re: [dispatch] Virtual IETF107 - SRT draft is available
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 18 Mar 2020 16:30:50 -0000

Despite the title "secure" the description of encryption is rather thin.
For instance, it appears that data packets can be "encrypted" but this does
not describe how AFAICT. Is there a complete description somewhere? What
are the desired security properties of this protocol?


On Tue, Mar 17, 2020 at 11:37 PM 김준웅님(JOONWOONG.KIM) <>

> Hi all
> I would like to draw you attention to SRT draft which is added in the last
> minute to the agenda of DISPATCH session, coming week (if time is allowed
> after existing agenda items are handled):
> SRT (Secure Reliable Transport) protocol is a user level protocol
> optimized for low-latency live video contribution based on UDT and UDP,
> over different network conditions. While it has been rather successfully
> deployed by some industries, we would like to make it an Internet standard
> and further collaborate in IETF communities for enhancements, which would
> be beneficial to Internet community and Industries.
> The draft was originally submitted for MOPS WG of IETF 107 for
> discussions, but now there will not be any MOPS meeting until late April.
> Therefore we would like to discuss this draft in DISPATCH, which might be
> more appropriate venue to find out where and how a new protocol draft can
> be handled. I appreciate DISPATCH leaderships and members, for kind
> consideration.
> If you need more clarification about SRT protocol or our intention, please
> let me know. Any comments or discussions before the meeting would be
> helpful as well. In the meantime, you can find more information about SRT
> here (white papers, simple video clips, and open source code):
> Thanks so much for reading and your help in advance.
> thanks
> Joonwoong
> ==
> Joonwoong Kim | Global Standardization | SK Telecom mailto:
> _______________________________________________
> dispatch mailing list