Re: [payload] Kathleen Moriarty's No Objection on draft-ietf-payload-vp8-17: (with COMMENT)
Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Thu, 17 September 2015 10:46 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 D5F2D1B2BF5; Thu, 17 Sep 2015 03:46:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 KXURGgW1gFAC; Thu, 17 Sep 2015 03:46:10 -0700 (PDT)
Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (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 22DED1B2CA6; Thu, 17 Sep 2015 03:46:10 -0700 (PDT)
Received: by qgez77 with SMTP id z77so8983206qge.1; Thu, 17 Sep 2015 03:46:09 -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=rlfbGOBhlYvLiVfy5rM10fzbYarhDDctnXmNisfi+ik=; b=zb5Nz/GCnPPaZ5D7TXQBTtHULvnQ8PLA4xQCKKvzhWSnjVLGgk7OquOnHia5CY6JBn kDIwlWDxwD8vTqSqKgBp0gqqm8LPwO7QoTRgSPsijXRfEvcy17icfBia47HScOO1hGdF 0YkarsuhZZ/VaY85HVO1O6T69htpL87eY6MaP4wooQH9BFiFFMPWgiaMpb+mlkCJhGk3 lVM/qVXaM91hkRL/1QbeKQCSEDa5JBAh7M7jNy2Tz7cjddbun6jNy4DxWOpJNrMtdpF1 DbmgiEmXM6+Hzm2AVj2XLMAoa4MsYb59okEKYmASPFB7sLh6UlFSFmN8AeB46U/GhmZA Fhxw==
X-Received: by 10.140.152.68 with SMTP id 65mr51055324qhy.16.1442486769291; Thu, 17 Sep 2015 03:46:09 -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 smtp.gmail.com with ESMTPSA id p29sm982089qkp.48.2015.09.17.03.46.08 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Sep 2015 03:46:08 -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="us-ascii"
Mime-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (12H143)
In-Reply-To: <ABD897D8-A55D-4AB3-A84A-FCC136930526@nostrum.com>
Date: Thu, 17 Sep 2015 06:46:07 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <63FAF756-A72B-4682-B401-050D5F460400@gmail.com>
References: <20150917022433.25044.53666.idtracker@ietfa.amsl.com> <ABD897D8-A55D-4AB3-A84A-FCC136930526@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/payload/Ny2Eg3iet6J0C6GFHBH3Du9m0NE>
Cc: "payload-chairs@ietf.org" <payload-chairs@ietf.org>, The IESG <iesg@ietf.org>, "payload@ietf.org" <payload@ietf.org>, "draft-ietf-payload-vp8@ietf.org" <draft-ietf-payload-vp8@ietf.org>
Subject: Re: [payload] Kathleen Moriarty's No Objection on draft-ietf-payload-vp8-17: (with COMMENT)
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: <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, 17 Sep 2015 10:46:12 -0000
Sent from my iPhone > On Sep 17, 2015, at 12:04 AM, Ben Campbell <ben@nostrum.com> wrote: > >> On 16 Sep 2015, at 21:24, Kathleen Moriarty wrote: >> >> Why is this a SHOULD: >> Applications SHOULD use one or more appropriate strong security >> mechanisms. >> >> Wouldn't it be more helpful to point out why you would use specific >> security mechanisms for security considerations? > > Hi Kathleen, > > That's part of the boilerplate for payload drafts. The idea is that the security requirements are specific to the application that uses RTP, not RTP itself or the related payload format. For example, WebRTC requires DTLS-SRTP. There's an open discussion on what should be required for point-to-point RTP sessions signaled via SIP (which I need to push forward.) > > This is discussed further in RFCs 7201 and 7202. > > Thanks! > > Ben. Thanks, Ben! Do you recall which draft we changed that in or was it unrelated, just an incredibly similar sentence? Thanks, Kathleen
- [payload] Kathleen Moriarty's No Objection on dra… Kathleen Moriarty
- Re: [payload] Kathleen Moriarty's No Objection on… Ben Campbell
- Re: [payload] Kathleen Moriarty's No Objection on… Kathleen Moriarty
- Re: [payload] Kathleen Moriarty's No Objection on… Kathleen Moriarty