IETF Logo Mail Archive

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

"Drage, Keith (Nokia - GB)" <keith.drage@nokia.com> Tue, 22 March 2016 10:32 UTC

Return-Path: <keith.drage@nokia.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 CF58712D673 for <rtcweb@ietfa.amsl.com>; Tue, 22 Mar 2016 03:32:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level:
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 V2uhL-H_rwjC for <rtcweb@ietfa.amsl.com>; Tue, 22 Mar 2016 03:31:57 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (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 E892812D728 for <rtcweb@ietf.org>; Tue, 22 Mar 2016 03:31:54 -0700 (PDT)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id BDD55C7FF7FE6 for <rtcweb@ietf.org>; Tue, 22 Mar 2016 10:31:50 +0000 (GMT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u2MAVqhc029370 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <rtcweb@ietf.org>; Tue, 22 Mar 2016 10:31:52 GMT
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u2MAVVNL012849 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <rtcweb@ietf.org>; Tue, 22 Mar 2016 11:31:52 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.185]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Tue, 22 Mar 2016 11:31:47 +0100
From: "Drage, Keith (Nokia - GB)" <keith.drage@nokia.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] I-D Action: draft-ietf-rtcweb-ip-handling-01.txt
Thread-Index: AQHRgvg79H6EjfH6EUm6FTBySzZ8HZ9kqXjQ
Date: Tue, 22 Mar 2016 10:31:46 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8BADEAFFC7@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <20160320223116.8946.76840.idtracker@ietfa.amsl.com>
In-Reply-To: <20160320223116.8946.76840.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/UYXeIvdRih3Mp7ox_VnkGdFIBxs>
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: Tue, 22 Mar 2016 10:32:01 -0000

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

-----Original Message-----
From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of EXT internet-drafts@ietf.org
Sent: 20 March 2016 22:31
To: i-d-announce@ietf.org
Cc: rtcweb@ietf.org
Subject: [rtcweb] I-D Action: draft-ietf-rtcweb-ip-handling-01.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Real-Time Communication in WEB-browsers of the IETF.

        Title           : WebRTC IP Address Handling Recommendations
        Authors         : Justin Uberti
                          Guo-wei Shieh
	Filename        : draft-ietf-rtcweb-ip-handling-01.txt
	Pages           : 8
	Date            : 2016-03-20

Abstract:
   This document provides best practices for how IP addresses should be
   handled by WebRTC applications.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtcweb-ip-handling/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-rtcweb-ip-handling-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-rtcweb-ip-handling-01


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email