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

"김준웅님(JOONWOONG.KIM)" <joonwoong.kim@sk.com> Thu, 19 March 2020 05:23 UTC

Return-Path: <joonwoong.kim@sk.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 A371C3A225B for <dispatch@ietfa.amsl.com>; Wed, 18 Mar 2020 22:23:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=o365skt.onmicrosoft.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 AI8J-X5i62bn for <dispatch@ietfa.amsl.com>; Wed, 18 Mar 2020 22:23:43 -0700 (PDT)
Received: from secumail2.sktelecom.com (secumail2.sktelecom.com [203.236.20.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCAB23A225A for <dispatch@ietf.org>; Wed, 18 Mar 2020 22:23:42 -0700 (PDT)
Received: from unknown (HELO SKT-MAILPEDGE1.skt.ad) (203.236.20.107) by 203.236.20.243 with ESMTP; 19 Mar 2020 14:23:39 +0900
X-Original-SENDERIP: 203.236.20.107
X-Original-MAILFROM: joonwoong.kim@sk.com
Received: from SKT-MAILPALL2.SKT.AD (203.236.13.5) by owa.sktelecom.com (203.236.20.107) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Thu, 19 Mar 2020 14:23:36 +0900
Received: from SKT-MAILPALL1.SKT.AD (150.19.7.214) by SKT-MAILPALL2.SKT.AD (150.19.7.215) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1847.3; Thu, 19 Mar 2020 14:23:35 +0900
Received: from SKT-MAILPEDGE1.skt.ad (203.236.20.107) by SKT-MAILPALL1.SKT.AD (150.19.7.214) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1847.3 via Frontend Transport; Thu, 19 Mar 2020 14:23:35 +0900
Received: from KOR01-PS2-obe.outbound.protection.outlook.com (104.47.109.57) by owa.sktelecom.com (203.236.20.107) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.1713.5; Thu, 19 Mar 2020 14:23:35 +0900
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=nwlUXUmKZvDFTbuQfe3QGdF3U0+1xZRWFdt4EKjj+8Z6SZX3vy3B1W077eeEOiD2xBZtyme2L7gsOujjOahYprVYL9mZ0QazhbFZOcHDTqBkB1JnHVdUK9rs8nSS1JT/YwF/KvsIZ0VKsZbfJ3DCniYLHLbovLJmqeScWGE3M/HdgRSD/JYZ6az48WaGaLnpS13DfPKZpmLmCaw3ezMuMafYy7zWSxNWQiKki+G/ZdvckSRwpBNMj8m7bne7Jd581iLSwKoEEPq+4Os/foJNvczjY/P3/+Ua1RyEy+Y8ZQcFuF40hFIxZ8txuJAe9dmeSpWmRnh6/lfSt25NNB5gtw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;bh=cLmBYaxtiYvK/NFXtqVV0ZXSHlsTpc5+UO+U7aePphk=; b=AXrvMqt00dUFH79kCnNZwS+mL47MBsOcrEzW/9ZGsUOXNcnEdxu+oVFmzqsvw1lO7gp0ZA7JzkeogS6MWioBTFWOC0czE2tksVcNFAg+DFUU9kTq+qQjQ0LaXByqtbfiX1RxwGfFcztbpGY/WJs4qvrO8G/F9w0ECp29L/aF3FHX7XBmiNIJsqhGZRVVYq54EMIQBls8+5wZ9H9NgwWOLm9PZT3D2hTdl/EtJzA0u+KQGxk2x30pzFu5alXIOk5e7G70mSh/X3VnqyaqPJTaDfj1jxGFtid1AAAwrRrFu8s+3NXGXraHRm7Ukw0ecOWc8Qrq/jIErSHSlXnyd4KnKQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=sktelecom.com; dmarc=pass action=none header.from=sktelecom.com; dkim=pass header.d=sktelecom.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=o365skt.onmicrosoft.com; s=selector2-o365skt-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;bh=cLmBYaxtiYvK/NFXtqVV0ZXSHlsTpc5+UO+U7aePphk=; b=XwI5IdQfKmNu0PPImPvxrNPk8zJnQUnW4IYfkhg30EESEd0gBm21ZsoReP+n+OMSPgvq8SYLdzNIv6BSWCJb9k63FjTFKrwcQ3nCPST77GbMQqtLNNEmRxEQp3CKfM1xdsxmNOLiryzzRqnHeLyQMHEulHh7hvW9CfWhzIw0JKY=
Received: from SL2P216MB0474.KORP216.PROD.OUTLOOK.COM (10.174.47.150) by SL2P216MB0969.KORP216.PROD.OUTLOOK.COM (10.174.123.137) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2835.19; Thu, 19 Mar 2020 05:23:34 +0000
Received: from SL2P216MB0474.KORP216.PROD.OUTLOOK.COM ([fe80::94d1:2f77:3450:44d5]) by SL2P216MB0474.KORP216.PROD.OUTLOOK.COM ([fe80::94d1:2f77:3450:44d5%9]) with mapi id 15.20.2814.021; Thu, 19 Mar 2020 05:23:34 +0000
From: "김준웅님(JOONWOONG.KIM)" <joonwoong.kim@sk.com>
To: Eric Rescorla <ekr@rtfm.com>
CC: "dispatch@ietf.org" <dispatch@ietf.org>, "joonwoong@gmail.com" <joonwoong@gmail.com>
Thread-Topic: [dispatch] Virtual IETF107 - SRT draft is available
Thread-Index: AdX8540PVKCyRS/ETgS+qLbYRQNaXAAWu8aAABr1ZRA=
Date: Thu, 19 Mar 2020 05:23:34 +0000
Message-ID: <SL2P216MB0474D967B9E814F2A36BB010EFF40@SL2P216MB0474.KORP216.PROD.OUTLOOK.COM>
References: <SL2P216MB047407C8AA07BAA52CDF907EEFF70@SL2P216MB0474.KORP216.PROD.OUTLOOK.COM> <CABcZeBMHqbozaucfcdWNqe4jVkVAEDBsjpn31cEvbY6wH1HdHw@mail.gmail.com>
In-Reply-To: <CABcZeBMHqbozaucfcdWNqe4jVkVAEDBsjpn31cEvbY6wH1HdHw@mail.gmail.com>
Accept-Language: ko-KR, en-US
Content-Language: ko-KR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=joonwoong.kim@sktelecom.com;
x-originating-ip: [203.236.9.162]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 99b085e8-ccf1-48e2-8eea-08d7cbc5ab9c
x-ms-traffictypediagnostic: SL2P216MB0969:
x-microsoft-antispam-prvs: <SL2P216MB09699799CFD2B95B0B8408CAEFF40@SL2P216MB0969.KORP216.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0347410860
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(376002)(366004)(346002)(136003)(39860400002)(199004)(81156014)(76116006)(66574012)(966005)(54906003)(186003)(8936002)(4326008)(66476007)(66946007)(64756008)(66556008)(66446008)(33656002)(6916009)(5660300002)(52536014)(55016002)(86362001)(478600001)(8676002)(316002)(7696005)(2906002)(26005)(9686003)(71200400001)(53546011)(81166006)(6506007); DIR:OUT; SFP:1101; SCL:1; SRVR:SL2P216MB0969; H:SL2P216MB0474.KORP216.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1;
received-spf: None (protection.outlook.com: sktelecom.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: rsAYuzqv+jDD8Ef7YWTvn7uo00vzFM67fEuZLz5z/85YVVWhF3pCQ0VZK93TvCnIIw6i6tmS+kThFM+3VYV6Q5GXYA1Ceml3lyB4ygL3D5CgcMuK1521jwVcoFO/XehHFdzvnHhojttfLk9aktJ57V78xbfNnaXSGJ3hvmK3D+P+taXY4awdIK3ocmt+C64qrAk33hbASzoVbvIBKdl2fyCkqtnD1Af+GtdcgGfMb/5QcV9OXsSa9HOCnw34YsFbl0FRo3CtYY9JU9hSMekJRRIYaSvBPfFCNnQH9REGJxLkxKiWZu3AMvhTYzpuXtdyYIPt96Mdwqmv0BXev/zoOK1yLzL6s96tjLTOZWL9IJSQiOwlqUHam3295iZZSojXD8C+LYtKoL49hLmssno9PTWGbqTPOeG7zqfdfm05D/RLlZbzbF/dcKFSMUyp4xFjBcCiLySKpijS27HVbxlarUP3FSIGnIDO5O5180mAOzUv4UwzW057f1Mde0CYapTbyJUWc6pnU4K7XYIfKM92RQ==
x-ms-exchange-antispam-messagedata: KystF5i6AAcrEP/hItPZhCuFhhV5ZB7oF19eFiy6JrG5yF34m5oKkX6DTVJl0lPFmZZr5XY+mtM3BunQd4lftNGuj2CVMRsWSfv8ivSDU3W8zwmO+g+M6ox+xYq2Ou0TW/Di4Ktb3WBm3L77nl6r8A==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_SL2P216MB0474D967B9E814F2A36BB010EFF40SL2P216MB0474KORP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 99b085e8-ccf1-48e2-8eea-08d7cbc5ab9c
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Mar 2020 05:23:34.2965 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5afa09fd-c4be-434d-830d-f4765c449035
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: +qIHOw/d4xVn325UM7L4i3cfgdKT/1aEVehhWgid0KbOLbAI7XkWSQh+cruwzwH4QIOkHUQ9AkbSGZ8K88T2Fg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SL2P216MB0969
X-OriginatorOrg: sktelecom.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/_p6WKCbVDu7IPZcCoJaWlrMT9UA>
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: Thu, 19 Mar 2020 05:23:48 -0000

Hi Eric

Thanks for the question. At this time, we couldn't complete security (encryption) section due to limited time. I think that other sections need improvements as well. Full details on encryption (and key establishment) are available in SRT Technical Overview paper, which is available at:
https://github.com/Haivision/srt/files/2489142/SRT_Protocol_TechnicalOverview_DRAFT_2018-10-17.pdf

SRT supports confidentiality protection of payload with a stream cipher mainly based on AES counter mode as well as key establishment mechanisms. Other modes like GCM could be used instead (for integrity check, for example), but the related procedures were not specified yet and left for the future enhancement. SRT did not provide authentication of peers, although it would be interesting to see if TLS would applicable to SRT. We can think of "secure" for SRT as rather basic but efficient protection of payload for live video delivery, and other security aspects have to be dealt with applications. More complete analysis of security might be needed for future enhancements, hopefully through collaboration with experts in IETF community.

cheers
joonwoong

From: Eric Rescorla <ekr@rtfm.com>
Sent: Thursday, March 19, 2020 1:30 AM
To: 김준웅님(JOONWOONG.KIM)/기술표준화팀 <joonwoong.kim@sktelecom.com>
Cc: dispatch@ietf.org; joonwoong@gmail.com
Subject: Re: [dispatch] Virtual IETF107 - SRT draft is available

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?

-Ekr




On Tue, Mar 17, 2020 at 11:37 PM 김준웅님(JOONWOONG.KIM) <joonwoong.kim@sk.com<mailto: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<mailto:joonwoong.kim@sk.com>


_______________________________________________
dispatch mailing list
dispatch@ietf.org<mailto:dispatch@ietf.org>
https://www.ietf.org/mailman/listinfo/dispatch