Re: [rtcweb] Addressing WGLC comments for draft-ietf-rtcweb-security-arch? (was Re: WGLC for draft-ietf-rtcweb-security-arch) - SDP O/A structure

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 23 May 2018 13:11 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0979912DA6C for <rtcweb@ietfa.amsl.com>; Wed, 23 May 2018 06:11:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 cwPM8lNPqlkV for <rtcweb@ietfa.amsl.com>; Wed, 23 May 2018 06:11:58 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 79718124D6C for <rtcweb@ietf.org>; Wed, 23 May 2018 06:11:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1527081068; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=ThQ05Ykw4es4czHuLq2qjO5l4F+UBglayUMyIFp835M=; b=OiyNTIePx+wCKcxGzpYxkEezA1jeyNHObab06m06nSNp6h2K9TVS5m63evfljrVQ kofHBVtrhATaKQzUKkkjIQtxdmrbmKMyUChUXA68aiwzaNst6eFxTK8xjdQcK3AG WZyvh7Ok8YeSFjWYRR1q5K1JKD+iI7rztExELQr9NfE=;
X-AuditID: c1b4fb3a-77c239c00000451c-3d-5b05686cd195
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.183.39]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id B0.65.17692.C68650B5; Wed, 23 May 2018 15:11:08 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.29]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.03.0382.000; Wed, 23 May 2018 15:10:55 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Sean Turner <sean@sn3rd.com>
CC: Martin Thomson <martin.thomson@gmail.com>, Eric Rescorla <ekr@rtfm.com>, RTCWeb IETF <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Addressing WGLC comments for draft-ietf-rtcweb-security-arch? (was Re: WGLC for draft-ietf-rtcweb-security-arch) - SDP O/A structure
Thread-Index: AdPylxr2uLzTa8s0T76r47ULvo8kYw==
Date: Wed, 23 May 2018 13:10:54 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72F02D42@ESESSMB109.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.171]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrCLMWRmVeSWpSXmKPExsUyM2K7um5OBmu0weJ/BhYrXp9jt7h25h+j xdp/7ewWV1Y1MjuweOycdZfdY8mSn0wekx+3MXscPMgYwBLFZZOSmpNZllqkb5fAlfFiwS7W giN8FfdffmdrYJzC18XIwSEhYCJxZ6F7FyMXh5DAEUaJ4x1XWLoYOYGcxYwS356YgNSwCVhI dP/TBgmLCChINB19wApiMwvkSCz708oC0issMI9RovHoX2aIovmMEp2feSBsPYkJDQ1gM1kE VCX2TdoK1swr4Ctx7OsSsDijgJjE91NrmCCGikvcejIfzJYQEJBYsuc8M4QtKvHy8T9WCFtJ 4sTDRmaQ25gFNCXW79KHaFWUmNL9kB1ivKDEyZlPWCYwCs9CMnUWQscsJB2zkHQsYGRZxSha nFpcnJtuZKSXWpSZXFycn6eXl1qyiREYFwe3/LbawXjwueMhRgEORiUe3gVprNFCrIllxZW5 hxglOJiVRHhDY4BCvCmJlVWpRfnxRaU5qcWHGKU5WJTEeZ3SLKKEBNITS1KzU1MLUotgskwc nFINjKJhWRGJjyZl72Z/3lW9VfHfJaWdF14onH+5bcknj6pgp2OSa7uWTPMu2HlyzoW3U1L5 J37XnDh/ZmApZ9Cr3buj/s/stJDvS614rfyz9HLo8kXKS/T53/JJxrA5H/Is1t+tHntRX3V/ /r705oo3L3SnT1stK76L4ZvI6VtlE3cVNb2vE59s902JpTgj0VCLuag4EQBT+VUAhwIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/_PL5qtgqaMkRTXW6Y5fvmmEPau8>
Subject: Re: [rtcweb] Addressing WGLC comments for draft-ietf-rtcweb-security-arch? (was Re: WGLC for draft-ietf-rtcweb-security-arch) - SDP O/A structure
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 13:11:59 -0000

Hi,

...

>> , the structure we normally use is:
>> 
>> x.  SDP XXX Attribute    <--- This section defines the attribute
>> y.  SDP Offer/Answer Procedures
>> y.1.  General
>> y.2.  Generating the Initial SDP Offer 
>> y.3.  Generating the Answer 
>> y.4.  Offerer Processing of the SDP Answer 
>> y.5.  Modifying the Session
>
> Luckily, there are a bunch of SDP attributes defined and some follow this structure and some don’t ;)

Lately we have been very strict that they do follow the structure. 

Now, based on recent discussions related to BUNDLE, there may be some changes to this structure (or, at least the terminology used), but until that happens we should use it.

Especially when it comes to "initial SDP offer", it is useful to clarify that the text refers to the offer in which the attribute is first included. It may be the initial offer of a session, but also a subsequent offer.

> I’ll admit that I’m a little hesitant to suggest that we do a major editorial revision because the draft has basically had the same layout for 2+ years. 

Personally, as I haven't been following the security work very closely, I unfortunately didn't realize that we are defining an SDP attribute in the security architecture document, which is the reason I didn't comment earlier. I am sorry for that.

Regards,

Christer