Re: Status of <draft-ietf-6man-default-iids-16.txt> in AUTH48

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 22 February 2017 10:53 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 1B389129697 for <ipv6@ietfa.amsl.com>; Wed, 22 Feb 2017 02:53:45 -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 jGRDvJsJQsnO for <ipv6@ietfa.amsl.com>; Wed, 22 Feb 2017 02:53:43 -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 960E212968C for <ipv6@ietf.org>; Wed, 22 Feb 2017 02:53:43 -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 v1MArfrJ016594 for <ipv6@ietf.org>; Wed, 22 Feb 2017 11:53:41 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id B0A0A205023 for <ipv6@ietf.org>; Wed, 22 Feb 2017 11:53:41 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id A6FFF2040B0 for <ipv6@ietf.org>; Wed, 22 Feb 2017 11:53:41 +0100 (CET)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v1MArfXS007040 for <ipv6@ietf.org>; Wed, 22 Feb 2017 11:53:41 +0100
Subject: Re: Status of <draft-ietf-6man-default-iids-16.txt> in AUTH48
To: ipv6@ietf.org
References: <C9FDAEB9-9F79-4186-9C48-5F44E5E07235@gmail.com> <E580FFBB-7A17-4B48-92CC-E95BB9887743@gmail.com> <5F61B219-A2C2-471E-9DB0-3B604D101317@ericsson.com> <c5e05727-f05f-b451-0066-9dcffd65d231@si6networks.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <a40fa94e-9944-8be3-d3b5-f8a41ccd93f6@gmail.com>
Date: Wed, 22 Feb 2017 11:53:34 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <c5e05727-f05f-b451-0066-9dcffd65d231@si6networks.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/EygCXs93LNoYZC8wdQxk3_7LPoY>
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, 22 Feb 2017 10:53:45 -0000

Hi Fernando,

For my part, I think there may be a risk of too much binding of personal
matters to professional matters.  In some cases, distinct values could
be leveraged more if separated, in other cases if converged.  That too 
are facets of privacy :-)

Alex

Le 22/02/2017 à 01:23, Fernando Gont a écrit :
> On 02/21/2017 05:44 PM, Suresh Krishnan wrote:
>>
>>> On Feb 21, 2017, at 2:43 PM, Bob Hinden <bob.hinden@gmail.com>
>>> wrote:
>>>
>>> Hi,
>>>
>>> I went through the responses to the call regarding
>>> <draft-ietf-6man-default-iids-16.txt> .  The question in the
>>> email was:
>>>
>>> Please respond with either support or non-support for this
>>> proposed change by 18 February 2017.  I think it is unfortunate
>>> to add extra delay over this change, but after consulting with
>>> our AD, I think the best course is to ask the working group.
>>>
>>> My summary of the responses is:
>>>
>>> Fred Baker                 non-support Lorenzo Colitti
>>> non-support Enno Rey                   support t.pech
>>> non-support Brian Carpenter            Doesn’t think it’s a w.g.
>>> decision Joel Halpern               non-support Sander Steffan
>>> support Roland Bless               non-support Alexandre Petrescu
>>> non-support 神明達哉                    Didn’t indicate a position
>>>
>>> By my count there is 6 non-support and 2 in support of the
>>> acknowledgement paragraph (not counting the response from the
>>> authors Fernando and Alissa).
>>>
>>> Based on this, Suresh should notify the RFC Editor to remove the
>>> acknowledgement paragraph.
>>
>> Thanks Bob. Will let the RFC Editor know and proceed with
>> publication.
>
> Just out of curiosity:
>
> Is a statement like "I do not support" *without any rationale* of
> value?
>
> And, are statements like "I do not support this, because we only do X
> in the 'Acnkowledgements' section" of any value, when it should be
> obvious to anyone that RFCs have contained virtually *anything*? --
> please check the "Acknowledgements" section of RFC1812 for an
> example, but there are many others.
>
> I ask because, essentially, folks that have argued against the
> Acknowledgement I added fall into one of these two camps: no
> rationale for objecting (other than "I do not support", "too late")
> or claiming that Acks follow "guidelines" that evidence shows that
> it's not true.
>
> As noted, I will go with whatever the wg decides. But I'm curious
> about the above.
>
> Thanks,
>