Re: IPv6 options defined outside of 6man

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 16 November 2016 09:47 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 268061293DF for <ipv6@ietfa.amsl.com>; Wed, 16 Nov 2016 01:47:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level:
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 YXmOVNZbM1tg for <ipv6@ietfa.amsl.com>; Wed, 16 Nov 2016 01:47:17 -0800 (PST)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30C8312969A for <ipv6@ietf.org>; Wed, 16 Nov 2016 01:47:16 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id uAG9lEDt023234 for <ipv6@ietf.org>; Wed, 16 Nov 2016 10:47:14 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 0EA2120399E for <ipv6@ietf.org>; Wed, 16 Nov 2016 10:47:14 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id EEA4D203409 for <ipv6@ietf.org>; Wed, 16 Nov 2016 10:47:13 +0100 (CET)
Received: from [132.166.84.142] ([132.166.84.142]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id uAG9lCr4008458 for <ipv6@ietf.org>; Wed, 16 Nov 2016 10:47:13 +0100
Subject: Re: IPv6 options defined outside of 6man
To: ipv6@ietf.org
References: <alpine.DEB.2.02.1611160858330.14320@uplift.swm.pp.se>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <a83e7449-2ee6-3842-e3ce-fa51ffc6e9bc@gmail.com>
Date: Wed, 16 Nov 2016 18:47:11 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.02.1611160858330.14320@uplift.swm.pp.se>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/6UBrAwghLpxeXLRa25sv4QJ75Zg>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Nov 2016 09:47:19 -0000


Le 16/11/2016 à 17:16, Mikael Abrahamsson a écrit :
>
> Hi,
>
> I just the other day noticed that RFC7710 defines RA type for captive
> portal URI along DHCPv4 and DHCPv6 options for the same use.
>
> http://www.iana.org/assignments/icmpv6-parameters/icmpv6-parameters.xhtml#icmpv6-parameters-5
> lists the options currently defined.
>
> This option was discussed briefly in 6man in March 2015, and then I saw
> no announcement of this actually being approved.
>
> I found out in IDR the other day that any IETF working group can ask
> IANA to allocate numbers in any registries, and normally this goes to
> respective AD and WG who would then normally either allocate an expert
> to review, and/or have the entire WG review it.
>
> I previously thought respective WG "owned" certain IANA option space
> they typically work with. This is not the case. Even people in IDR
> thought IDR "owned" certain IANA option space, and they were also wrong.
>
> So do we here in 6man want some kind of process and consensus calling
> before this review is concluded and we say "no objection" when other WGs
> define IPv6 related options?

This would be reasonable to do, I think.

>
> I believe DHC working group does this, they bring up options for
> discussions there before they're ACKed.

I agree, as long as it gets constructive feedback from 6man.

Alex


>
> Thoughts?
>