Re: [payload] Update of security template text in draft-ietf-payload-rtp-howto

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Fri, 10 April 2015 12:47 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: payload@ietfa.amsl.com
Delivered-To: payload@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B9381B333B; Fri, 10 Apr 2015 05:47:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001] autolearn=ham
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 qskaxaac8cWO; Fri, 10 Apr 2015 05:47:57 -0700 (PDT)
Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (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 7C7B41B33D8; Fri, 10 Apr 2015 05:47:53 -0700 (PDT)
Received: by qkhg7 with SMTP id g7so28637917qkh.2; Fri, 10 Apr 2015 05:47:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=RlqortXcF+z0Tx7KyFr8jfojBo2R5k+OWOGFHd2H3Qw=; b=T03jCae2qASVae6hUypIAMg8pqaqMLc+s73mLq9zkQ124FoDralsjpvid6pgcuR6kk Q/BPmlB7J2M8mgb/MN+sqJTSx+3ofEj1If+rpq1J255heWCHE25rRtadJav3AlBM0yRa Etzvvm+eMDafZRd9a+o0Z1JjT7QHgFuQRbyaGsSJDtkK+EJ9o+aN3wRS9kIWTlFXoxUD AOKnqn1NZu22Rb95w988R65BZnSsLH9VP/rnGF1vvYM6r5WbQSusPLV5Wiqi87CI8OK+ vcEwg5Rc0d+dCXUb52fISbQvHeyvj+6NIEQSAL80jdBPCqLOqzuEv8sHdp4FQvJn1GRe e1jg==
X-Received: by 10.55.31.90 with SMTP id f87mr2357764qkf.38.1428670072791; Fri, 10 Apr 2015 05:47:52 -0700 (PDT)
Received: from [192.168.1.3] (209-6-114-252.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com. [209.6.114.252]) by mx.google.com with ESMTPSA id x66sm1527619qha.6.2015.04.10.05.47.51 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 10 Apr 2015 05:47:51 -0700 (PDT)
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Google-Original-From: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (11D257)
In-Reply-To: <5527B105.5000305@ericsson.com>
Date: Fri, 10 Apr 2015 08:47:50 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <158277FA-817F-4192-9339-3DDA565E2607@gmail.com>
References: <55277811.70905@ericsson.com> <E3FFC107-6CCE-4A01-B86B-659431D5BD34@live555.com> <5527B105.5000305@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/payload/No-MWRs4AfXtJV7xpYr8dAKfnNU>
Cc: IESG <iesg@ietf.org>, "payload@ietf.org" <payload@ietf.org>
Subject: Re: [payload] Update of security template text in draft-ietf-payload-rtp-howto
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 10 Apr 2015 12:47:59 -0000

Thank you, Magnus.

I think the new text represents the current considerations well.  The recommendation to use one or more strong security mechanism works for me.

Best regards,
Kathleen 

Sent from my iPhone

> On Apr 10, 2015, at 7:16 AM, Magnus Westerlund <magnus.westerlund@ericsson.com> wrote:
> 
> Thanks,
> 
> will happily apply this editorial fixes.
> 
> /Magnus
> 
>> On 2015-04-10 11:10, Ross Finlayson wrote:
>> This looks good.  However, fixing some minor nits:
>> 
>>> NEW:
>>> 
>>>  RTP packets using the payload format defined in this specification
>>>  are subject to the security considerations discussed in the RTP
>>>  specification [RFC3550] , and in any applicable RTP profile such as
>>>  RTP/AVP [RFC3551], RTP/AVPF [RFC4585], RTP/SAVP [RFC3711] or RTP/
>>>  SAVPF [RFC5124].  However, as "Securing the RTP Protocol Framework:
>>>  Why RTP Does Not Mandate a Single Media Security Solution" [RFC7202]
>>>  discusses it is not an RTP payload formats responsibility to discuss
>> 
>> Add a comma after “discusses’.  Also: “formats” -> “format’s”
>> 
>>>  or mandate what solutions are used to meet the basic security goals
>>>  like confidentiality, integrity and source authenticity for RTP in
>>>  general.  This responsibility lays on anyone using RTP in an
>>>  application.  They can find guidance on available security mechanisms
>>>  and important considerations in Options for Securing RTP Sessions
>>>  [RFC7201].  Applications SHOULD use one or more appropriate strong
>>>  security mechanisms.  The rest of the this security consideration
>> 
>> Remove “the”.  Also, perhaps, add “section” before the following:
>> 
>>>  discusses the security impacting properties of the payload format
>>>  itself.
>> 
>> 
>>    Ross.
> 
> 
> -- 
> 
> Magnus Westerlund
> 
> ----------------------------------------------------------------------
> Services, Media and Network features, Ericsson Research EAB/TXM
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> Färögatan 6                 | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>