[payload] draft-ietf-payload-flexible-fec-scheme-14 notes

Giridhar Mandyam <mandyam@qti.qualcomm.com> Thu, 03 January 2019 20:49 UTC

Return-Path: <mandyam@qti.qualcomm.com>
X-Original-To: payload@ietfa.amsl.com
Delivered-To: payload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5322131312; Thu, 3 Jan 2019 12:49:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level:
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.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 nmgdCEqJpMT4; Thu, 3 Jan 2019 12:49:44 -0800 (PST)
Received: from alexa-out-sd-01.qualcomm.com (alexa-out-sd-01.qualcomm.com [199.106.114.38]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C48FD131330; Thu, 3 Jan 2019 12:49:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1546548583; x=1578084583; h=from:to:subject:date:message-id:mime-version; bh=fsIhb5/gKJ6SCzk4Yefq0H/q5UscN2sGG0SnRs/4VKk=; b=U1Sf3axcxJoz5BXK3uRkFYlJqDRgzEcQY9D9qDOJAPz+s3yrVwPrXkwR lKfhJBlSjzvEQJgneGKztYIhgpb02mPgZMDu37Bi0QdXzhb6xf/3xYJ9w 6j4apl0qOHo0a+kHVYECu6UvVTEa4YI+UxqwjyMB+W7DMIUYoLl/KhCk5 E=;
X-IronPort-AV: E=Sophos; i="5.56,436,1539673200"; d="scan'208,217"; a="20115807"
Received: from unknown (HELO ironmsg-SD-alpha.qualcomm.com) ([10.53.140.30]) by alexa-out-sd-01.qualcomm.com with ESMTP; 03 Jan 2019 12:49:42 -0800
X-IronPort-AV: E=McAfee;i="5900,7806,9125"; a="320294740"
Received: from nasanexm01h.na.qualcomm.com ([10.85.0.34]) by ironmsg-SD-alpha.qualcomm.com with ESMTP/TLS/AES256-SHA; 03 Jan 2019 12:49:42 -0800
Received: from NASANEXM01C.na.qualcomm.com (10.85.0.83) by NASANEXM01H.na.qualcomm.com (10.85.0.34) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 3 Jan 2019 12:49:42 -0800
Received: from NASANEXM01C.na.qualcomm.com ([10.85.0.83]) by NASANEXM01C.na.qualcomm.com ([10.85.0.83]) with mapi id 15.00.1395.000; Thu, 3 Jan 2019 12:49:42 -0800
From: Giridhar Mandyam <mandyam@qti.qualcomm.com>
To: "draft-ietf-payload-flexible-fec-scheme.all@ietf.org" <draft-ietf-payload-flexible-fec-scheme.all@ietf.org>, "payload@ietf.org" <payload@ietf.org>
Thread-Topic: draft-ietf-payload-flexible-fec-scheme-14 notes
Thread-Index: AdSjpbyCoL1+LHhrRfypJF1xMdVwaQ==
Date: Thu, 03 Jan 2019 20:49:41 +0000
Message-ID: <c98b67a013d94d1d9fe62504153b83b6@NASANEXM01C.na.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.80.80.8]
Content-Type: multipart/alternative; boundary="_000_c98b67a013d94d1d9fe62504153b83b6NASANEXM01Cnaqualcommco_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/payload/KcIELXe6tGuETjVjwjHu9XEK-HA>
Subject: [payload] draft-ietf-payload-flexible-fec-scheme-14 notes
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Payloads working group discussion list <payload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/payload>, <mailto:payload-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/payload/>
List-Post: <mailto:payload@ietf.org>
List-Help: <mailto:payload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/payload>, <mailto:payload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2019 20:49:52 -0000

Hello All,
Please note that this latest version is in response to the AD review and covers the review provided in [1]-[4].

There are a couple of substantive changes based on AD review (versus version -13) of which the group should be aware:


  1.  Sec. 4.2.1.  Under the description of the SSRC field, the following requirement was previously a SHOULD:  “"The repair streams’ SSRC’s CNAME MUST be identical to the CNAME of the source RTP stream(s) that this repair stream protects.”
  2.  Sec. 5.1.  All media types are no longer provisionally registered.

In addition, there were a couple of re-wordings that were not directly covered in my latest review response [4]:


  1.  Under Figures 10 and 12 the description of the Repair Payload has been changed:  “The Repair "Payload", which follows the FEC Header, includes repair of everything following the fixed 12-byte RTP header of each source packet, including any CSRC identifier list and header extensions if present.”
  2.  In Sec. 5.2.2, the references to RTSP were further clarified:  “In declarative usage, like SDP in the Real-time Streaming Protocol (RTSP, for RTSP 1.0 see [RFC2326] and for RTSP 2.0 see [RFC7826]) …”

I hope this addresses all concerns.  However, if it does not, please make myself and all co-editors aware of any necessary modifications.  I would much rather submit another I.-D. version than an errata on an RFC.

Thanks,
-Giri Mandyam

[1] https://mailarchive.ietf.org/arch/msg/payload/tT4lQ_oVsDWuRmcFn7OImwy87oo
[2] https://mailarchive.ietf.org/arch/msg/payload/vfiVlSDhj-WY985KJ4Kinmjzxds
[3] https://mailarchive.ietf.org/arch/msg/payload/kx_C9UjQpE2ItfCYkE3eJMgKSPk
[4] https://mailarchive.ietf.org/arch/msg/payload/t-JKXuPvIeJ9VDbqw7pDwyc9vfA