Re: [clue] FW: I-D Action: draft-ietf-clue-rtp-mapping-13.txt

Hi Paul,
Just submitted -14 that I think addresses Magnus concerns
Roni

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
> Sent: שבת 25 פברואר 2017 00:43
> To: Roni Even; clue@ietf.org; Jonathan Lennox
> Cc: Magnus Westerlund
> Subject: Re: [clue] FW: I-D Action: draft-ietf-clue-rtp-mapping-13.txt
> 
> Roni, Jonathan,
> 
> Are you able to change in a way that will satisfy Magnus?
> 
> 	Thanks,
> 	Paul
> 
> On 2/24/17 3:14 AM, Magnus Westerlund wrote:
> > Hi,
> >
> > To be clear, yesterday's posting with remaining issues are applicable
> > on this version.
> >
> > That is actually a shortcoming of RTCWeb Security architecture and
> > there exists an tracked issue for it:
> >
> > https://github.com/rtcweb-wg/security-arch/issues/34
> >
> > So, yes, I would really like to see the communication security section
> > mandate encrypted RTCP. This due to the information included in RTCP
> > about the application. The protection profile mandated does imply
> > equal strength RTCP protection, but if one uses other profiles it
> > might not be as clear cut. So a wording on protecting RTCP at same or
> > similar protection strength to RTP I think is motivated.
> >
> > What I also think is missing in the new text is discussion of RTP
> > header extension encryption, i.e. RFC 6904. I thought the conclusion
> > on the capture ID is that there is no strong generation requirements
> > to ensure they don't contain privacy sensitive information. And it
> > definitely reveals what is happening in the application context to third
> parties.
> > Thus, I think encrypting the RTP header extensions would be good
> > practice in clue situations.
> >
> > I also reacted to the use of "untraceable" in this sentence:
> >
> > CLUE endpoint MUST generate short-term persistent RTCP CNAMES, as
> >    specified in [RFC7022], resulting in untraceable CNAME values.
> >
> > The point of them is that they are not long term persistent and thus
> > can't be used for long term tracking of the user. Writing "untraceable"
> > I would interpret as indicating a stronger user protection then what
> > is actually provided.
> >
> > Cheers
> >
> > Magnus
> >
> > Den 2017-02-13 kl. 10:59, skrev Roni Even:
> >> Hi,
> >> This new version is submitted to address Magnus and Ben comments.
> >> There is a new section Communication security that specifies
> >> normative security for CLUE media.
> >> The security consideration is just considerations and added text
> >> about the CaptureID There are also some editorial and nits changes
> >> Roni
> >>
> >>
> >> -----Original Message-----
> >> From: clue [mailto:clue-bounces@ietf.org] On Behalf Of
> >> internet-drafts@ietf.org
> >> Sent: יום ב 13 פברואר 2017 11:30
> >> To: i-d-announce@ietf.org
> >> Cc: clue@ietf.org
> >> Subject: [clue] I-D Action: draft-ietf-clue-rtp-mapping-13.txt
> >>
> >>
> >> A New Internet-Draft is available from the on-line Internet-Drafts
> >> directories.
> >> This draft is a work item of the ControLling mUltiple streams for
> >> tElepresence of the IETF.
> >>
> >>         Title           : Mapping RTP streams to CLUE Media Captures
> >>         Authors         : Roni Even
> >>                           Jonathan Lennox
> >>     Filename        : draft-ietf-clue-rtp-mapping-13.txt
> >>     Pages           : 14
> >>     Date            : 2017-02-13
> >>
> >> Abstract:
> >>    This document describes how the Real Time transport Protocol (RTP) is
> >>    used in the context of the CLUE protocol (ControLling mUltiple
> >>    streams for tElepresence).  It also describes the mechanisms and
> >>    recommended practice for mapping RTP media streams defined in
> Session
> >>    Description Protocol (SDP) to CLUE Media Captures and defines a new
> >>    RTP header extension (CaptureId).
> >>
> >>
> >> The IETF datatracker status page for this draft is:
> >> https://datatracker.ietf.org/doc/draft-ietf-clue-rtp-mapping/
> >>
> >> There's also a htmlized version available at:
> >> https://tools.ietf.org/html/draft-ietf-clue-rtp-mapping-13
> >>
> >> A diff from the previous version is available at:
> >> https://www.ietf.org/rfcdiff?url2=draft-ietf-clue-rtp-mapping-13
> >>
> >>
> >> Please note that it may take a couple of minutes from the time of
> >> submission until the htmlized version and diff are available at
> >> tools.ietf.org.
> >>
> >> Internet-Drafts are also available by anonymous FTP at:
> >> ftp://ftp.ietf.org/internet-drafts/
> >>
> >> _______________________________________________
> >> clue mailing list
> >> clue@ietf.org
> >> https://www.ietf.org/mailman/listinfo/clue
> >>
> >> _______________________________________________
> >> clue mailing list
> >> clue@ietf.org
> >> https://www.ietf.org/mailman/listinfo/clue
> >>
> > -
> >