Re: [rtcweb] I-D Action: draft-ietf-rtcweb-ip-handling-01.txt

Alissa Cooper <alissa@cooperw.in> Sat, 02 April 2016 01:13 UTC

Return-Path: <alissa@cooperw.in>
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 8850312D51B for <rtcweb@ietfa.amsl.com>; Fri, 1 Apr 2016 18:13:55 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=4c7qY8CQ; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=Uzp3yro0
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 WErZaE0EIrcK for <rtcweb@ietfa.amsl.com>; Fri, 1 Apr 2016 18:13:50 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DBB312D50F for <rtcweb@ietf.org>; Fri, 1 Apr 2016 18:13:50 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id DA1DB20792 for <rtcweb@ietf.org>; Fri, 1 Apr 2016 21:13:49 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 01 Apr 2016 21:13:49 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=xhJ7M /7IL6dIlWNkTPbBjmx7Nis=; b=4c7qY8CQJE2g8xl1IJIlGk0tn83IPQ1ZREHIe Gg7etvNLg4PL5lkHRIz0lRQLlxn0PkOjqhAq6wVI0fOC6csDu+ORdLeuWN5gGkxE nm69556sKq2M7zgj7rPJfVzlg1tBYdPGN3ikgA+c2GRQ5Oz+/c0neIa+xaTFP0+o xycK3M=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=xhJ7M/7IL6dIlWNkTPbBjmx7Nis=; b=Uzp3y ro0DBQVyLz5jLGZFoGOS/KGFod4ee2Og0K5U54TJ++sESozNL4yNmxw4oft8PeBw SeFfek8IBYPt5c4K8dVWuZD2gwfnnhWjl/Q1VYUsBqHhEkX9OjSlNiC3qMmguO/0 PuQGSuX2/qQhM3lTKVDqm66RQVpiesj/fFlTvE=
X-Sasl-enc: iLgXwLoVerhU8SVKXCGY9EdYjk7GlYpF3xm7Wrlj1J98 1459559629
Received: from [192.168.11.140] (ip-64-134-25-43.public.wayport.net [64.134.25.43]) by mail.messagingengine.com (Postfix) with ESMTPA id 54E19C00016; Fri, 1 Apr 2016 21:13:49 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_9D75D0A5-63F8-4B1F-B2A8-BB0C3975BF7C"
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <CA+9kkMCsT43ZCSdq8gdKXu1k4pJgbf0ab5tE=dDiFfrTT2gtkA@mail.gmail.com>
Date: Fri, 01 Apr 2016 20:13:48 -0500
Message-Id: <B2B472F4-317C-421C-8E42-BC505DB7F516@cooperw.in>
References: <20160320223116.8946.76840.idtracker@ietfa.amsl.com> <949EF20990823C4C85C18D59AA11AD8BADEAFFC7@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CA+9kkMCsT43ZCSdq8gdKXu1k4pJgbf0ab5tE=dDiFfrTT2gtkA@mail.gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/28YcOj9DmdS139Lgz21QMWxvXMw>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-ip-handling-01.txt
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 02 Apr 2016 01:13:55 -0000

> On Mar 22, 2016, at 6:10 PM, Ted Hardie <ted.ietf@gmail.com> wrote:
> 
> Speaking as an individual, rather than chair:
> 
> On Tue, Mar 22, 2016 at 3:31 AM, Drage, Keith (Nokia - GB) <keith.drage@nokia.com <mailto:keith.drage@nokia.com>> wrote:
> The header of this document says "standards track".
> 
> The title of the document says "recommendations" which would equate to a normative document of SHOULD strength
> 
> The abstract says "best practices"
> 
> Throughout the document I detected lots of lower case usage of RFC 2119 terms but did not see any upper case usage (but may have missed it).
> 
> All of which leaves me confused.
> 
> Would the chairs like to clarify the intent of this document in terms of document type?
> 
> Regards
> 
> Keith Drage
> 
> 
> I don't think this document describes any new protocol mechanisms, so the lack of upper case RFC 2119 terms seems to me personally fairly natural.  What it does instead is lay out the results of doing IP address handling in specific modes, along with a recommendation on which would make a reasonable default. 
> 
> Clearly it could have been part of JSEP, which would have made it part of a standards track doc.  The value to me of it being separate is that the advice can be revised independently of the core protocol specification.  To that extent, it is somewhere between "Applicability statement" and "BCP" in our formal terminology, with a thumb very slightly on the scale toward BCP. Ultimately, though, I am willing to be guided by our ADs or the community about the exact status. 

I could see an argument for either standards track or BCP and don’t have a strong feeling either way. In either case some adjustments would be necessary to make clear the normativity or non-normativity of the guidance.

Alissa

> The high order bits are the advice and its decomposability.
> 
> regards,
> 
> Ted 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb