Re: [v6ops] Consensus call on draft-ietf-v6ops-mobile-device-profile ?

<mohamed.boucadair@orange.com> Mon, 02 February 2015 08:08 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 C1C6C1A002A for <v6ops@ietfa.amsl.com>; Mon, 2 Feb 2015 00:08:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 K3zwN2IJ7VAO for <v6ops@ietfa.amsl.com>; Mon, 2 Feb 2015 00:08:03 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AA641A000B for <v6ops@ietf.org>; Mon, 2 Feb 2015 00:08:02 -0800 (PST)
Received: from omfeda05.si.francetelecom.fr (unknown [xx.xx.xx.198]) by omfeda11.si.francetelecom.fr (ESMTP service) with ESMTP id C0B211B8182; Mon, 2 Feb 2015 09:08:00 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.55]) by omfeda05.si.francetelecom.fr (ESMTP service) with ESMTP id 88203180072; Mon, 2 Feb 2015 09:08:00 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.231]) by OPEXCLILH03.corporate.adroot.infra.ftgroup ([10.114.31.55]) with mapi id 14.03.0224.002; Mon, 2 Feb 2015 09:08:00 +0100
From: mohamed.boucadair@orange.com
To: Lorenzo Colitti <lorenzo@google.com>, joel jaeggli <joelja@bogus.com>, "v6ops-chairs@tools.ietf.org" <v6ops-chairs@tools.ietf.org>
Thread-Topic: Consensus call on draft-ietf-v6ops-mobile-device-profile ?
Thread-Index: AQHQPreKtyiJoat2D0O2zimQJMaGP5zc/YRA
Date: Mon, 02 Feb 2015 08:07:59 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300490366F@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <CAKD1Yr1hHAVMZbXZuAtNExXw8TqUSDhzGBY5OA2fr9jMZgd9eQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr1hHAVMZbXZuAtNExXw8TqUSDhzGBY5OA2fr9jMZgd9eQ@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.5]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B93300490366FOPEXCLILM23corp_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.2.2.63025
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/RGLTcZcKKsanAzdgiK403hOc560>
Cc: "draft-ietf-v6ops-mobile-device-profile.all@tools.ietf.org" <draft-ietf-v6ops-mobile-device-profile.all@tools.ietf.org>, V6 Ops List <v6ops@ietf.org>
Subject: Re: [v6ops] Consensus call on draft-ietf-v6ops-mobile-device-profile ?
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: Mon, 02 Feb 2015 08:08:07 -0000

Re-,

I’m not a chair nor an AD but, but as an editor of the document, I don’t see what changed since the consensus was declared for this document SEVERAL times.

What’s new in the document that breaks the consensus?

Cheers,
Med

De : Lorenzo Colitti [mailto:lorenzo@google.com]
Envoyé : lundi 2 février 2015 08:12
À : joel jaeggli; v6ops-chairs@tools.ietf.org
Cc : Gert Doering; draft-ietf-v6ops-mobile-device-profile.all@tools.ietf.org; V6 Ops List; BOUCADAIR Mohamed IMT/OLN
Objet : Consensus call on draft-ietf-v6ops-mobile-device-profile ?

[Editing subject for for visibility; +v6ops-chairs since this is their bailiwick]

Forgive me for being ignorant on these procedural points, but... it seems to me that if there is no longer consensus in the WG that this document should be published, then it should not be published - regardless of what procedural steps the document has been through already. Am I mistaken?

If I am correct, then we should make sure that we still have consensus to proceed before we do anything else. The response to this thread suggests that there may not be consensus, but hopefully it deciding the question should be as simple as issuing another consensus call.

Regards,
Lorenzo

On Mon, Feb 2, 2015 at 3:40 PM, <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> wrote:
Hi Joel,

Which consensus are your talking about?: The one for adopting the document as a WG item?, the first one declared by the WG before sending it to the IESG? the second one declared by the WG to send the document to the IESG?, or the IETF consensus that was declared before the IESG starts its review?

Cheers,
Med

-----Message d'origine-----
De : joel jaeggli [mailto:joelja@bogus.com<mailto:joelja@bogus.com>]
Envoyé : samedi 31 janvier 2015 21:49
À : BOUCADAIR Mohamed IMT/OLN; Gert Doering
Cc : draft-ietf-v6ops-mobile-device-profile.all@tools.ietf.org<mailto:draft-ietf-v6ops-mobile-device-profile.all@tools.ietf.org>; V6 Ops List
Objet : Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call

On 1/30/15 4:21 AM, mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com> wrote:
> Re-,
>
> With all due respect, I'm afraid we are not discussing whether the
> document is needed or not but (as I see it) whether the new version
> does not break the WG consensus that was declared for the version
> sent to the IESG. I recall that both the WG and IETF consensus were
> declared for the version sent to the IESG.

One point on that. Part of the reason we are engaged canvasing, is that
Brian's discussed questioned my interpretation of the consensus call.
Given that I conceded from the outset that the call is somewhat narrow,
one of the questions before us as a w.g. and the ietf community is, is
that consensus more unequivocal?  Brian I believe is willing to extended
the benefit of the doubt. So am I, but it's the working groups document...

thanks

joel

> Thank you.
>
> Cheers, Med
>
> -----Message d'origine----- De : Gert Doering [mailto:gert@space.net<mailto:gert@space.net>]
>  Envoyé : vendredi 30 janvier 2015 11:39 À : BOUCADAIR Mohamed
> IMT/OLN Cc : Gert Doering; Ole Troan; Fred Baker (fred);
> draft-ietf-v6ops-mobile-device-profile.all@tools.ietf.org<mailto:draft-ietf-v6ops-mobile-device-profile.all@tools.ietf.org>; V6 Ops
> List Objet : Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last
> call
>
> Hi,
>
> On Fri, Jan 30, 2015 at 09:12:16AM +0000,
> mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com> wrote:
>> Can you please help us identifying technical flaws that you think
>> need to be fixed in the document?
>
> I don't think there is a need for this document, and I can't truly
> see it reflecting WG consensus.  So it's more fundamental than just
> individual technical issues.
>
> For the specifics, everything that Lorenzo said.
>
> Gert Doering -- NetMaster
>

_______________________________________________
v6ops mailing list
v6ops@ietf.org<mailto:v6ops@ietf.org>
https://www.ietf.org/mailman/listinfo/v6ops