IETF Logo Mail Archive

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

Ben Campbell <ben@nostrum.com> Wed, 18 March 2020 16:08 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A55DA3A05A0 for <dispatch@ietfa.amsl.com>; Wed, 18 Mar 2020 09:08:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.079
X-Spam-Level:
X-Spam-Status: No, score=-2.079 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GIW9eZQfYbXz for <dispatch@ietfa.amsl.com>; Wed, 18 Mar 2020 09:08:22 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18A0A3A17F6 for <dispatch@ietf.org>; Wed, 18 Mar 2020 09:08:22 -0700 (PDT)
Received: from [192.168.127.239] (mta-70-120-123-175.stx.rr.com [70.120.123.175] (may be forged)) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 02IG8AKA065463 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 18 Mar 2020 11:08:12 -0500 (CDT) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1584547693; bh=ddrMGqUA3f0wQc8VDF5yZAMkA85jjT1MLi2RcCJjrSo=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=Ye8pL6AV8Wh94zqiV0cRUhbNez+B/0vJ5aqrmwewPXUDMDO5G3fW3OWOpBkR9H3V9 Jkr8I642u4GT1TarpGto7HFwpuGn16ABPHggBkz/KA4ZclvSQHdLR06yXiwkpT93ge ylLWzW+xEj5UvKmAH/t0ghBXp1TEgfDyIUnLlOJ0=
X-Authentication-Warning: raven.nostrum.com: Host mta-70-120-123-175.stx.rr.com [70.120.123.175] (may be forged) claimed to be [192.168.127.239]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <5DC9DFEB-7B44-402B-BD10-5A6B27F11145@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_738AD594-E2DF-464B-8F07-FED88760FBE6"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
Date: Wed, 18 Mar 2020 11:07:56 -0500
In-Reply-To: <SL2P216MB047407C8AA07BAA52CDF907EEFF70@SL2P216MB0474.KORP216.PROD.OUTLOOK.COM>
Cc: Patrick McManus <patrick.ducksong@gmail.com>
To: "dispatch@ietf.org" <dispatch@ietf.org>
References: <SL2P216MB047407C8AA07BAA52CDF907EEFF70@SL2P216MB0474.KORP216.PROD.OUTLOOK.COM>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/CAYOLI7941UyrvbwaezBAKpuAAI>
Subject: Re: [dispatch] Virtual IETF107 - SRT draft is available
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Mar 2020 16:08:24 -0000

Hi All,

The chairs would like to see comments about what an appropriate discussion venue for this draft would be. It seems like it sits on the border between TSV and ART.

Thanks!

Ben.

> On Mar 18, 2020, at 1:37 AM, 김준웅님(JOONWOONG.KIM) <joonwoong.kim@sk.com> wrote:
> 
> 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):
> 
> https://datatracker.ietf.org/doc/draft-sharabayko-mops-srt/
> 
> 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):
> https://www.srtalliance.org/
> http://www3.haivision.com/srt-open-source-wp
> https://github.com/Haivision/srt
> 
> Thanks so much for reading and your help in advance.
> 
> thanks
> Joonwoong
> ==
> Joonwoong Kim | Global Standardization | SK Telecom mailto:joonwoong.kim@sk.com
> 
> 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch

v2.23.0 | Report a Bug | By Email