Re: [rtcweb] References to -overview (Re: Unresolved normative references in IETF RTCWEB WG documents)
Bernard Aboba <bernard_aboba@hotmail.com> Sun, 18 August 2013 21:59 UTC
Return-Path: <bernard_aboba@hotmail.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 06AEA11E8175 for <rtcweb@ietfa.amsl.com>; Sun, 18 Aug 2013 14:59:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level:
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8TIsrrNys6Eq for <rtcweb@ietfa.amsl.com>; Sun, 18 Aug 2013 14:58:57 -0700 (PDT)
Received: from blu0-omc3-s15.blu0.hotmail.com (blu0-omc3-s15.blu0.hotmail.com [65.55.116.90]) by ietfa.amsl.com (Postfix) with ESMTP id 296D411E8159 for <rtcweb@ietf.org>; Sun, 18 Aug 2013 14:58:57 -0700 (PDT)
Received: from BLU405-EAS78 ([65.55.116.72]) by blu0-omc3-s15.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 18 Aug 2013 14:58:56 -0700
X-TMN: [CsxwP5Af13VQujaS8qJ2Sr3Oy/zmBN+9]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU405-EAS78D22C3CB8963FB18951F293410@phx.gbl>
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: 'Harald Alvestrand' <harald@alvestrand.no>
References: <BLU169-W11426A149ADD0123A6BEF4C93460@phx.gbl> <521095EB.7070500@alvestrand.no>
In-Reply-To: <521095EB.7070500@alvestrand.no>
Date: Sun, 18 Aug 2013 14:58:53 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_B50B_01CE9C23.75553570"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQABAgME/MqTPQe2A3p0JQVNnAX3+p02sCfA
Content-Language: en-us
X-OriginalArrivalTime: 18 Aug 2013 21:58:56.0228 (UTC) FILETIME=[22A2DA40:01CE9C5E]
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] References to -overview (Re: Unresolved normative references in IETF RTCWEB WG documents)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Sun, 18 Aug 2013 21:59:02 -0000
Harald said: "In my opinion, the normal case should be that references to -overview are informative, not normative. Documents should be published when they're ready." [BA] Looking over the both RTP usage and security documents, it seems reasonable to convert the normative references to informative in both cases Looking at the RTP usage document, there is no normative language that points to -overview and in fact -overview is only mentioned twice: Section 1 The WebRTC overview [I-D.ietf-rtcweb-overview <http://tools.ietf.org/html/draft-ietf-rtcweb-rtp-usage-07#ref-I-D.ietf-rtcw eb-overview> ] outlines the complete WebRTC framework, of which this memo is a part. [BA] While -overview does reference RTP usage, and the RTP usage document is certainly an important part of WebRTC, I don't think this implies a normative reference to -overview. After all, almost everything in the RTP usage document can (and probably has been) implemented outside of WebRTC. Section 3 Other terms are used according to their definitions from the RTP Specification [RFC3550 <http://tools.ietf.org/html/rfc3550> ] and WebRTC overview [I-D.ietf-rtcweb-overview <http://tools.ietf.org/html/draft-ietf-rtcweb-rtp-usage-07#ref-I-D.ietf-rtcw eb-overview> ] documents. [BA] This sentence doesn't point to specific terms defined in Section 2.4 of -overview that are needed for understanding the RTP usage document, but if there are some, those could be added to the RTP usage document, rather than requiring a normative reference. The security document only has a single reference to -overview: Section 1 The Real-Time Communications on the Web (RTCWEB) working group is tasked with standardizing protocols for real-time communications between Web browsers, generally called "WebRTC" [I-D.ietf-rtcweb-overview <http://tools.ietf.org/html/draft-ietf-rtcweb-security-05#ref-I-D.ietf-rtcwe b-overview> ]. [BA] Since the security documents has its own introductory material, and doesn't reference terminology or other aspects of -overview other than the above, an informative reference seems like it should be fine.
- [rtcweb] Unresolved normative references in IETF … Bernard Aboba
- Re: [rtcweb] Unresolved normative references in I… Muthu Arul Mozhi Perumal (mperumal)
- [rtcweb] References to -overview (Re: Unresolved … Harald Alvestrand
- Re: [rtcweb] References to -overview (Re: Unresol… Bernard Aboba
- Re: [rtcweb] References to -overview (Re: Unresol… Cullen Jennings (fluffy)
- Re: [rtcweb] Unresolved normative references in I… Cullen Jennings (fluffy)