[rtcweb] Referring to 5245bis or 5245?

Sean Turner <sean@sn3rd.com> Thu, 18 May 2017 14:18 UTC

Return-Path: <sean@sn3rd.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 8299212EAB8 for <rtcweb@ietfa.amsl.com>; Thu, 18 May 2017 07:18:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.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 q4OHDRniZ9NZ for <rtcweb@ietfa.amsl.com>; Thu, 18 May 2017 07:18:35 -0700 (PDT)
Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28E8412EAC0 for <rtcweb@ietf.org>; Thu, 18 May 2017 07:13:00 -0700 (PDT)
Received: by mail-io0-x231.google.com with SMTP id k91so29245426ioi.1 for <rtcweb@ietf.org>; Thu, 18 May 2017 07:13:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=/6OcuArrwGZ9wnpmFJLAyeGgUSECNZ/BUzFmgnpCYPY=; b=HoHxB09SsVyi/vzhyjfxklz9KPOA02qTh/gWAB2pEUyFL7SSRB+eUFZie2tA9N4MHU MrRq3JGP/8LGK+6oOetrbX9NGXtVvewncytEe1aVQjDheSSETD2xgGPkrXd55x0Ic4kR 64mk2IzZQrBG+Xpk/w6umL/lncwdLyBH4rPM8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=/6OcuArrwGZ9wnpmFJLAyeGgUSECNZ/BUzFmgnpCYPY=; b=HJNrGxh0hlLoA6qtXZ680AWCV/rgYKWZoo8FAASK68qdXRaZbuBqXuVLzCHomW2WF6 ltJVIOt0GS19zaogpBDPDxLrS4yB5Jr382S+jPUNcowc+Ffsex2zq+Mx7llraB/KxNRz 6lw7Lw+zitk8nMyUqeWYWKkYqvPPM6fTraOSN/n7eC7mNsQ6pCd1lQruXbReG9OAhrMv ZI0rX0pMkUMX//9671i69IDiqZNIhD6hNSp4GoGFzDA5b7itrhtybiT7NpuJ2Qe52zL0 NNr6a4bBMQMUVNgCKVmxYVz3NvDNDVA27R3XLr9XPcooMh6NQBEvw50dXVucfhzD1dIr 4jCg==
X-Gm-Message-State: AODbwcALKZnuUhmarTrxNnN6XY/BIQPx4m5ZhUn65Uc7gr18yeMwOHQM JMxHVw5sRJhld7bKU1QNOw==
X-Received: by 10.107.128.216 with SMTP id k85mr4609917ioi.115.1495116779220; Thu, 18 May 2017 07:12:59 -0700 (PDT)
Received: from [5.5.33.138] (vpn.snozzages.com. [204.42.252.17]) by smtp.gmail.com with ESMTPSA id b62sm2621580itc.16.2017.05.18.07.12.58 for <rtcweb@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 18 May 2017 07:12:58 -0700 (PDT)
From: Sean Turner <sean@sn3rd.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Message-Id: <4C1F0FE7-F7E6-47F7-922D-057E4E7FA466@sn3rd.com>
Date: Thu, 18 May 2017 10:12:53 -0400
To: RTCWeb IETF <rtcweb@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/6_utg2GAFQB1a_G9_TBz03-niX8>
Subject: [rtcweb] Referring to 5245bis or 5245?
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: Thu, 18 May 2017 14:18:36 -0000

ekr’s discuss on draft-ietf-rtcweb-overview has raised whether drafts should refer to RFC 5245 or draft-ietf-ice-rfc5245bis.  We only need to normatively refer to 5245bis if a technical part of 5245bis needs to be read and implemented in order to implement the referring draft.  We have 7 drafts that refer to RFC 5245 and 2  that refer to draft-ietf-rfc5245bis:

draft-ietf-rtcweb-overview: As noted in my response to ekr’s discuss position [0], the chairs believe that the reference to “ICE” in the ICE Agent definition should be to RFC 5245.

draft-ietf-rtcweb-transports: Likewise, the chairs believer that a reference to RFC 5245 is also appropriate in transports.  This draft was changed in version -17 to refer to 5245bis.  From GH: "The drafts -bundle and -dualstack-fairness both depend on 5245bis according to Cullen's chart in 'rtcweb-deps-13', and we already have a normative dependency from -transport on these.  So consistency of the bundle is improved by referencing 5245bis."

spt

[0] https://mailarchive.ietf.org/arch/msg/rtcweb/GWdXRIO68FZwVtzzqugnELKeaY8