Re: [AVTCORE] [payload] I-D Action: draft-ietf-payload-tetra-03.txt

"Roni Even (A)" <roni.even@huawei.com> Thu, 12 December 2019 13:25 UTC

Return-Path: <roni.even@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B96B12011B; Thu, 12 Dec 2019 05:25:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 mntEC-_2hoFq; Thu, 12 Dec 2019 05:25:49 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 22701120013; Thu, 12 Dec 2019 05:25:49 -0800 (PST)
Received: from lhreml709-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id E3F79A1C8B534642A9C8; Thu, 12 Dec 2019 13:25:43 +0000 (GMT)
Received: from lhreml734-chm.china.huawei.com (10.201.108.85) by lhreml709-cah.china.huawei.com (10.201.108.32) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 12 Dec 2019 13:25:43 +0000
Received: from lhreml734-chm.china.huawei.com (10.201.108.85) by lhreml734-chm.china.huawei.com (10.201.108.85) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Thu, 12 Dec 2019 13:25:43 +0000
Received: from DGGEMM406-HUB.china.huawei.com (10.3.20.214) by lhreml734-chm.china.huawei.com (10.201.108.85) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Thu, 12 Dec 2019 13:25:43 +0000
Received: from DGGEMM526-MBX.china.huawei.com ([169.254.8.101]) by DGGEMM406-HUB.china.huawei.com ([10.3.20.214]) with mapi id 14.03.0439.000; Thu, 12 Dec 2019 21:25:39 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: REISENBAUER Andreas <Andreas.Reisenbauer@frequentis.com>, "Tuominen, Antti" <antti.tuominen@airbus.com>, "draft-ietf-payload-tetra@ietf.org" <draft-ietf-payload-tetra@ietf.org>, "payload@ietf.org" <payload@ietf.org>
CC: "Klaus-Peter Höhnsch (klaus-peter.hoehnsch@t- systems.com)" <klaus-peter.hoehnsch@t-systems.com>, "Brandhuber Udo (ubrandhuber@EUROFUNK.COM)" <ubrandhuber@EUROFUNK.COM>, "Joachim Hagedorn (joachim@hagedorn-infosysteme.de)" <joachim@hagedorn-infosysteme.de>
Thread-Topic: [payload] I-D Action: draft-ietf-payload-tetra-03.txt
Thread-Index: AQHVQ+U620ADAVEItUK/Il0SZOTEI6bcwk2AgNqT9uA=
Date: Thu, 12 Dec 2019 13:25:39 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD27D3520C@dggemm526-mbx.china.huawei.com>
References: <156416792249.7563.6910208155358173908@ietfa.amsl.com> <2c3e8f9e6fca4e8d99ddf1cf5c5c233c@frequentis.com>
In-Reply-To: <2c3e8f9e6fca4e8d99ddf1cf5c5c233c@frequentis.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.202.67]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/jhyAsycj1fqIPWSo_0fbZI1e6a4>
Subject: Re: [AVTCORE] [payload] I-D Action: draft-ietf-payload-tetra-03.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Dec 2019 13:25:51 -0000

Hi Andreas,
Before sending the document to publication I would like to clarify the difference between this document and the ETSI one. My understanding is that the difference is in the payload header as specified in section 4.

I think it is time to send the document to publication but since it has been sometime since the last WGLC I will have a short WGLC before publication  request

Let me know if this is OK with you
Roni Even 
AVTcore co-chair

> -----Original Message-----
> From: REISENBAUER Andreas
> [mailto:Andreas.Reisenbauer@frequentis.com]
> Sent: Friday, July 26, 2019 10:27 PM
> To: Tuominen, Antti; draft-ietf-payload-tetra@ietf.org; payload@ietf.org;
> Roni Even (A)
> Cc: Klaus-Peter Höhnsch (klaus-peter.hoehnsch@t-systems.com);
> Brandhuber Udo (ubrandhuber@EUROFUNK.COM); Joachim Hagedorn
> (joachim@hagedorn-infosysteme.de)
> Subject: FW: [payload] I-D Action: draft-ietf-payload-tetra-03.txt
> 
> Hi Antti, Roni, payload working group
> 
> I did an update of the draft-ietf-tetra. Thanks a lot for your comments Antti -
> according your feedback we changed references from the historical ETSI TS
> 100 392-3-6 to ETSI TS 100 392-3-8. Indeed we did not change the control bit
> structure. As it is well defined in our draft-ietf-payload-tetra we do not need
> a bit equivalency to any ETSI standard.
> 
> According Antti's comment regarding, it seems a bit superfluous to specify
> another slightly different format:
> There is one single specification (ETSI TS 100 392-3-8 ) addressing both circuit
> switched lines as well as for transport via RTP and it specifically addresses the
> application of a TETRA Intersystem Interface rather than a generic TETRA
> audio payload for RTP. Because of this fact the cited standard is little more
> TDM-stylish rather than pure RTP. There are attributes included as part of the
> payload which are either superfluous or at least confusing for pure RTP
> communications (e.g. call reference, traffic type which identifies codec,
> frame number – supposed to handle slipped frames in SDH). For this reasons
> we (the authors) of this draft think it is worth to specify a pure IP way to
> propagate TETRA payload via RTP and therefore ask IANA to register
> “audio/TETRA” as a valid payload type according the specification given here.
> 
> Best regards
> Andreas
> 
> 
> -----Original Message-----
> From: payload <payload-bounces@ietf.org> On Behalf Of internet-
> drafts@ietf.org
> Sent: Freitag, 26. Juli 2019 21:05
> To: i-d-announce@ietf.org
> Cc: payload@ietf.org
> Subject: [payload] I-D Action: draft-ietf-payload-tetra-03.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Audio/Video Transport Payloads WG of the
> IETF.
> 
>         Title           : RTP Payload Format for the TETRA Audio Codec
>         Authors         : Andreas Reisenbauer
>                           Udo Brandhuber
>                           Joachim Hagedorn
>                           Klaus-Peter Höhnsch
>                           Stefan Wenk
> 	Filename        : draft-ietf-payload-tetra-03.txt
> 	Pages           : 15
> 	Date            : 2019-07-26
> 
> Abstract:
>    This document specifies a Real-time Transport Protocol (RTP) payload
>    format for TETRA encoded speech signals.  The payload format is
>    designed to be able to interoperate with existing TETRA transport
>    formats on non-IP networks.  A media type registration is included,
>    specifying the use of the RTP payload format and the storage format.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-payload-tetra/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-payload-tetra-03
> https://datatracker.ietf.org/doc/html/draft-ietf-payload-tetra-03
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-payload-tetra-03
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> payload mailing list
> payload@ietf.org
> https://www.ietf.org/mailman/listinfo/payload