Re: [AVTCORE] WG last call on draft-ietf-avtcore-aria-srtp-04

Colin Perkins <csp@csperkins.org> Wed, 28 August 2013 15:21 UTC

Return-Path: <csp@csperkins.org>
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 5B68711E81B6 for <avt@ietfa.amsl.com>; Wed, 28 Aug 2013 08:21:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k3lDvoiQhCWc for <avt@ietfa.amsl.com>; Wed, 28 Aug 2013 08:21:44 -0700 (PDT)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [93.93.130.6]) by ietfa.amsl.com (Postfix) with ESMTP id 1369411E81BD for <avt@ietf.org>; Wed, 28 Aug 2013 08:21:37 -0700 (PDT)
Received: from [130.209.247.112] (port=56801 helo=mangole.dcs.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <csp@csperkins.org>) id 1VEhYm-0004wm-Dt; Wed, 28 Aug 2013 16:21:32 +0100
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <CAMRi9CdoPWZtK-hyRt0=Urz5fh609dXVwrSP+GjHs9gR+rt+wg@mail.gmail.com>
Date: Wed, 28 Aug 2013 16:21:33 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F1E0C2F5-E071-4E84-A135-53B0FCC16508@csperkins.org>
References: <CAMRi9CdoPWZtK-hyRt0=Urz5fh609dXVwrSP+GjHs9gR+rt+wg@mail.gmail.com>
To: Woo-Hwan Kim <whkim5@ensec.re.kr>
X-Mailer: Apple Mail (2.1508)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold = On =
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, draft-ietf-avtcore-aria-srtp@tools.ietf.org, avt@ietf.org
Subject: Re: [AVTCORE] WG last call on draft-ietf-avtcore-aria-srtp-04
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 28 Aug 2013 15:21:50 -0000

On 28 Aug 2013, at 05:29, Woo-Hwan Kim <whkim5@ensec.re.kr> wrote:
> I have searched for the acronym RTCP in several RFC documents.
> RTCP is an acronym for RTP Control Protocol in RFCs 3550 and 3611, but
> it is an acronym for Real-time-Transport Control Protocol in RFCs 3605, 3711, 4585.
> I think any expression is admissible since both of them are widely used and there is no confusion when one or the other is used.
> If necessary, I'll correct the draft.

Please correct it. The expansion in RFC 3550 is definitive. We shouldn't perpetuate the mistakes in other RFCs.

> The byte order for the test vector is the network order (called big endian) which has been adopted by most documents. I'll add a comment in the next revision.

Thanks!
Colin