IETF Logo Mail Archive

Re: [Sipbrandy] WGLC: draft-ietf-sipbrandy-rtpsec-03

"Peterson, Jon" <jon.peterson@team.neustar> Thu, 11 January 2018 17:04 UTC

Return-Path: <prvs=8549ee2806=jon.peterson@team.neustar>
X-Original-To: sipbrandy@ietfa.amsl.com
Delivered-To: sipbrandy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF0DF12EBE2 for <sipbrandy@ietfa.amsl.com>; Thu, 11 Jan 2018 09:04:01 -0800 (PST)
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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=team.neustar
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 FazwiHU31NlT for <sipbrandy@ietfa.amsl.com>; Thu, 11 Jan 2018 09:03:59 -0800 (PST)
Received: from mx0b-0018ba01.pphosted.com (mx0b-0018ba01.pphosted.com [67.231.157.90]) (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 C26F912D947 for <sipbrandy@ietf.org>; Thu, 11 Jan 2018 09:03:59 -0800 (PST)
Received: from pps.filterd (m0078668.ppops.net [127.0.0.1]) by mx0b-0018ba01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w0BH3Kkm020690; Thu, 11 Jan 2018 12:03:57 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=team.neustar; h=from : to : subject : date : message-id : content-type : content-id : content-transfer-encoding : mime-version; s=selector1; bh=JjgvcZCIeAji4sACEcS++ZN50SL04tg1mpWpqv8JFGM=; b=lhhcZAMYndqEWExWfBXcT5tiAWJjKfcrAXCMDSWOxDO55eCVtyhRigjbRhSJHCKPh9Ph 6BWyZio+yLdi3N2hevnQ13JS0W8Bt2G7NEgiLy/wlyM6f+IyF6+PK0kCU1CxVEvYXAKN gHjcHdDIJLS+dsZujU14FrzKYSXSGeCOIhh5GLHPmr6yaGZ/FM6pDyjZfxF28CkGXwpL 4dQ0EuUmOIUF8m5tBSTM1hVUPJKNfcDmPtbLJ7WEq3dAI/OuKRwpXd0jaexiFZM7yyTf DDiMEes5PyNLS7RQ9PcrFOATORj/6cJkVUiJqJTC3VacJPjQ0F69/2jvQ3ZcCavXkpyF tQ==
Received: from stntexhc12.cis.neustar.com ([156.154.17.216]) by mx0b-0018ba01.pphosted.com with ESMTP id 2fdabhjxyv-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 11 Jan 2018 12:03:57 -0500
Received: from STNTEXMB11.cis.neustar.com ([169.254.1.47]) by stntexhc12.cis.neustar.com ([::1]) with mapi id 14.03.0279.002; Thu, 11 Jan 2018 12:03:56 -0500
From: "Peterson, Jon" <jon.peterson@team.neustar>
To: Russ Housley <housley@vigilsec.com>, "sipbrandy@ietf.org" <sipbrandy@ietf.org>
Thread-Topic: [Sipbrandy] WGLC: draft-ietf-sipbrandy-rtpsec-03
Thread-Index: AQHTiv4pTxaQmrhrbEygpflIxnrr7g==
Date: Thu, 11 Jan 2018 17:03:56 +0000
Message-ID: <D67CD676.1F5199%jon.peterson@neustar.biz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [10.96.12.106]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <FDEEC96AD5AD534CA3F894ED25B1B5B2@neustar.biz>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-01-11_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1801110234
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipbrandy/4Tc01a1wikeFm5UqTNQjId45rdE>
Subject: Re: [Sipbrandy] WGLC: draft-ietf-sipbrandy-rtpsec-03
X-BeenThere: sipbrandy@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: SIPBRANDY working group discussion list <sipbrandy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipbrandy>, <mailto:sipbrandy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipbrandy/>
List-Post: <mailto:sipbrandy@ietf.org>
List-Help: <mailto:sipbrandy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipbrandy>, <mailto:sipbrandy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jan 2018 17:04:02 -0000

Thanks for these notes Russ:

>Major:
>
>In Section 4.3, I do not know what is meant by "STIR Profile for media
>confidentiality".

I think we've been using that language as the name for this entire effort:
as a way to leverage STIR through a particular extension with its
incumbent behavior to get media confidentiality. Since media
confidentiality was definitely not a requirement of STIR initially, this
is effectively a profile, a narrow use case applying STIR to something
slightly different. I think SHAKEN set the precedent for profiling STIR
through an extension, and we are just following that. I'm not sure how to
make that more clear, though.

>
>Minor:
>
>I think the discussion in the first paragraph of Section 3.1 should be
>slightly expanded to be clear that we are not talking about integrity
>protection of SDP k= records.  I'd prefer a MUST NOT statement.

Fine by me. 

>
>In Section 4.1: s/SIP endpoints must acquire/SIP endpoints MUST acquire/

So... I don't think this language is stipulating implementation behavior
as such - it is expressing a practical necessity rather than something we
would test conformance with, I think? The spec then goes on to discuss the
actual protocol mechanisms you might use to actually acquire credentials.
If the "must" is annoying I can paraphrase to "as a matter of practical
necessity need to". Or maybe I need more RFC8174 sensitivity training.

>
>In Section 4.2: 
>   s/should be discarded/SHOULD be discarded/
>   s/should be generated/SHOULD be generated/

These ones however I think you're right, we are talking about
implementation behavior.

>
>Nits:

... Will zap those nits. Thanks!

Jon Peterson
Neustar, Inc.

>
>
>
>> On Dec 12, 2017, at 8:46 AM, Gonzalo Camarillo
>><Gonzalo.Camarillo@ericsson.com> wrote:
>> 
>> Folks,
>> 
>> I would like to start a WGLC on the following draft. This WGLC will
>> end on January 12th:
>> 
>> https://datatracker.ietf.org/doc/draft-ietf-sipbrandy-rtpsec/
>> 
>> Thanks,
>> 
>> Gonzalo
>
>_______________________________________________
>Sipbrandy mailing list
>Sipbrandy@ietf.org
>https://www.ietf.org/mailman/listinfo/sipbrandy

v2.23.0 | Report a Bug | By Email