IETF Logo Mail Archive

Re: [secdir] Secdir last call review of draft-ietf-rtcweb-sdp-11

Benjamin Kaduk <kaduk@mit.edu> Thu, 21 May 2020 07:40 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 409A53A0A97; Thu, 21 May 2020 00:40:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 p7tJyxDpDJXa; Thu, 21 May 2020 00:40:37 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 4C8B03A0A9C; Thu, 21 May 2020 00:40:36 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 04L7eUZw032666 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 21 May 2020 03:40:33 -0400
Date: Thu, 21 May 2020 00:40:29 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Francesca Palombini <francesca.palombini@ericsson.com>
Cc: "draft-ietf-rtcweb-sdp.all@ietf.org" <draft-ietf-rtcweb-sdp.all@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
Message-ID: <20200521074029.GI58497@kduck.mit.edu>
References: <158773486767.10860.13207279734771599599@ietfa.amsl.com> <ab722f98c63f40d38cbfb8d3c6f8d490@cert.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <ab722f98c63f40d38cbfb8d3c6f8d490@cert.org>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/9xc49RpuhzwHWKI-WJw3YPo-w-w>
Subject: Re: [secdir] Secdir last call review of draft-ietf-rtcweb-sdp-11
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 May 2020 07:40:41 -0000

Seconded -- it was a long one and the extra eyes appreciated.

I spent a little too much time trying to understand the SDP and think I
spotted some Discuss-worth inconsistencies.  I also suggested that the note
early on that some values are shown as shorter/less-random than usual for
the purposes of the examples, might be repeated in the security
considerations.

-Ben

On Tue, May 19, 2020 at 09:46:40PM +0000, Roman Danyliw wrote:
> Hi Francesca, thank you for this review.  I entered a No Objection ballot.
> 
> Regards,
> Roman
> 
> > -----Original Message-----
> > From: secdir <secdir-bounces@ietf.org> On Behalf Of Francesca Palombini via
> > Datatracker
> > Sent: Friday, April 24, 2020 9:28 AM
> > To: secdir@ietf.org
> > Cc: draft-ietf-rtcweb-sdp.all@ietf.org; last-call@ietf.org
> > Subject: [secdir] Secdir last call review of draft-ietf-rtcweb-sdp-11
> > 
> > Reviewer: Francesca Palombini
> > Review result: Ready
> > 
> > I have reviewed this document as part of the security directorate's ongoing
> > effort to review all IETF documents being processed by the IESG.  These
> > comments were written primarily for the benefit of the security area directors.
> > Document editors and WG chairs should treat these comments just like any
> > other last call comments.
> > 
> > The summary of the review is Ready.
> > 
> > This document provides an informational reference for examples of the Session
> > Description Protocol (SDP) Offer/Answer exchange mechanism, for the most
> > common Rtcweb use-cases.
> > 
> > The security considerations section points to documents describing the security
> > architecture for WebRTC as a whole, which is appropriate for such an
> > informational document.
> > 
> > 
> > _______________________________________________
> > secdir mailing list
> > secdir@ietf.org
> > https://www.ietf.org/mailman/listinfo/secdir
> > wiki: http://tools.ietf.org/area/sec/trac/wiki/SecDirReview
> 
> _______________________________________________
> secdir mailing list
> secdir@ietf.org
> https://www.ietf.org/mailman/listinfo/secdir
> wiki: http://tools.ietf.org/area/sec/trac/wiki/SecDirReview

v2.23.0 | Report a Bug | By Email