Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call- "harmfully broad"?

<mohamed.boucadair@orange.com> Thu, 19 February 2015 12:32 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F29F21A8FD7 for <v6ops@ietfa.amsl.com>; Thu, 19 Feb 2015 04:32:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.298
X-Spam-Level:
X-Spam-Status: No, score=-0.298 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MANGLED_AVOID=2.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=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 Hg91a_0STS-W for <v6ops@ietfa.amsl.com>; Thu, 19 Feb 2015 04:32:07 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9FDF1A8FD3 for <v6ops@ietf.org>; Thu, 19 Feb 2015 04:32:06 -0800 (PST)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 3F6D418C105; Thu, 19 Feb 2015 13:32:01 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.56]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 1AEB14C072; Thu, 19 Feb 2015 13:32:01 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.231]) by OPEXCLILH04.corporate.adroot.infra.ftgroup ([10.114.31.56]) with mapi id 14.03.0224.002; Thu, 19 Feb 2015 13:32:01 +0100
From: <mohamed.boucadair@orange.com>
To: Lorenzo Colitti <lorenzo@google.com>, "Heatley, Nick" <nick.heatley@ee.co.uk>
Thread-Topic: [v6ops] draft-ietf-v6ops-mobile-device-profile last call- "harmfully broad"?
Thread-Index: AQHQTC2TixBJZ1L350WogIuKXDMPO5z34qow
Date: Thu, 19 Feb 2015 12:32:01 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300490E4E7@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <787AE7BB302AE849A7480A190F8B9330049091C2@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CAKD1Yr2yDnwPDHgsq3Wi3UOzKY7KrqSpBMbBttJ5qAAu6ijOAw@mail.gmail.com> <54DDF02C.8020903@gmail.com> <2D09D61DDFA73D4C884805CC7865E61130F231B4@GAALPA1MSGUSRBF.ITServices.sbc.com> <6536E263028723489CCD5B6821D4B21303DEA706@UK30S005EXS06.EEAD.EEINT.CO.UK> <CAKD1Yr0j23E-UMdL2Ujv5nrpbbUa9rgPE_6AhbHLn0JeOZ9Edg@mail.gmail.com> <355A1FFC-9F92-4D61-985D-4C5FC6EC69EC@eircom.net> <CAKD1Yr2PX81czTwUZzaMtgPc9vhvP=oL++UZByGzxmkq_B=DMA@mail.gmail.com> <6536E263028723489CCD5B6821D4B21303E07EE2@UK30S005EXS06.EEAD.EEINT.CO.UK> <CAKD1Yr0Zkic6-ydV-u==xjDGdY9GYWb8KwciBPnfk8zO=6FFqQ@mail.gmail.com> <CAKD1Yr0qS-Vg-XB7mNWwephkkL5rCG+NJO7uDJg_4W3LT+Q9Ew@mail.gmail.com> <6536E263028723489CCD5B6821D4B21303E088AE@UK30S005EXS06.EEAD.EEINT.CO.UK> <CAKD1Yr00Ri8hQMsJcSqMAw+g_T-mU8GxG1G8rTHgo=McaKdW8Q@mail.gmail.com> <6536E263028723489CCD5B6821D4B21303E08E9C@UK30S005EXS06.EEAD.EEINT.CO.UK> <787AE7BB302AE849A7480A190F8B93300490D690@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CAD6AjGQ_K2kJCfFbhUxHK4p_5UXAsRpgoeYNtcbg4D+dOq5_4Q@mail.gmail.com> <787AE7BB302AE849A7480A190F8B93300490DAE5@OPEXCLILM23.corporate.adroot.infra.ftgroup> <6536E263028723489CCD5B6821D4B21303E097FB@UK30S005EXS06.EEAD.EEINT.CO.UK> <CAKD1Yr38vF3TKHjKY7zyUBS78B7G6-MCy=57f8aF-tjuk30A4A@mail.gmail.com>
In-Reply-To: <CAKD1Yr38vF3TKHjKY7zyUBS78B7G6-MCy=57f8aF-tjuk30A4A@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.3]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B93300490E4E7OPEXCLILM23corp_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.2.19.110025
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/Y387qrsJhVXF1xvceXUm1Xf2Vus>
Cc: "IPv6 Ops WG \(v6ops@ietf.org\)" <v6ops@ietf.org>
Subject: Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call- "harmfully broad"?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Feb 2015 12:32:09 -0000

Re-,

Thank you for the kind suggestion but I’m all optimist the I-D can be published in the IETF stream. If the IETF consensus was declared once, I’d hope this will happen for this version having a restricted scope (https://datatracker.ietf.org/doc/draft-ietf-v6ops-mobile-device-profile/)

It is obvious there is a void filled by this draft. It is built on existing RFCs already published in this area. This document is not original in its ambition nor it is different in its structure.

Technical issues can always be fixed (or at worse recorded), disagreements can be acknowledged, compromises can be found, the scope can be adjusted, etc.

Cheers,
Med

De : Lorenzo Colitti [mailto:lorenzo@google.com]
Envoyé : jeudi 19 février 2015 11:20
À : Heatley, Nick
Cc : BOUCADAIR Mohamed IMT/OLN; Ca By; IPv6 Ops WG (v6ops@ietf.org)
Objet : Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call- "harmfully broad"?

On Thu, Feb 19, 2015 at 6:14 PM, Heatley, Nick <nick.heatley@ee.co.uk<mailto:nick.heatley@ee.co.uk>> wrote:
If another body could be accountable for the document, that it represents the views of a suitable collective (mobile operators), but the technical content was filtered via IETF, that would be ideal, no?
I have no idea how to engineer such an outcome, but if it could be done then this work should not be wasted – could be a “GSMA sponsored RFC”?

You could make it an independent submission, and say that it represents the recommendations of the authors (see RFC 4846 for a description of the process, or RFC 6732 for an example of such an independent submission RFC).

If what you're after is IETF expertise, then I think the document has had plenty of exposure to that already, given it's been in the WG for over a year and a half.