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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 13 February 2017 14:00 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 9A38C129678 for <ipv6@ietfa.amsl.com>; Mon, 13 Feb 2017 06:00:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.352
X-Spam-Level:
X-Spam-Status: No, score=-5.352 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=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 ZK2hHPuhWO1J for <ipv6@ietfa.amsl.com>; Mon, 13 Feb 2017 06:00:39 -0800 (PST)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A69D129582 for <ipv6@ietf.org>; Mon, 13 Feb 2017 06:00:35 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id v1DE0WSl021661 for <ipv6@ietf.org>; Mon, 13 Feb 2017 15:00:32 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 6140B208DFC for <ipv6@ietf.org>; Mon, 13 Feb 2017 15:00:32 +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 4E854208DF8 for <ipv6@ietf.org>; Mon, 13 Feb 2017 15:00:32 +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 v1DE0WLQ005593 for <ipv6@ietf.org>; Mon, 13 Feb 2017 15:00:32 +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>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <4bae904b-e02f-6e7c-a039-cec339b03b9c@gmail.com>
Date: Mon, 13 Feb 2017 15:00:00 +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: <C9FDAEB9-9F79-4186-9C48-5F44E5E07235@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/QKHkW-6QjrTQnOb_mU04pjncn-o>
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: Mon, 13 Feb 2017 14:00:41 -0000


Le 11/02/2017 à 18:28, Bob Hinden a écrit :
> Hi,
>
> <draft-ietf-6man-default-iids-16.txt> is currently in AUTH48.
> According to the datatracker it has been in the RFC Editor queue for
> 54 days.  Everything is done, except there is an impasse over a
> change to the Acknowledgement Section.  One of the authors has
> proposed adding:
>
> Fernando Gont would like to thank Nelida Garcia and Guillermo Daniel
>  Gont for their love and support, and Jorge Oscar Gont and Diego
> Armando Maradona for their inspiration.
>
> Some of the other authors don’t think this change is appropriate for
> AUTH48, but the author proposing this has insisted on adding this
> text.
>
> 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.

I do not support this, because it's late.

But I will ask whether some goal-line comm technology involves IPv6? 
And whether genealogy "DOI-like" references exist?

Alex

>
> Thanks,
>
> Bob (Document Shepard)
>
>
>
> --------------------------------------------------------------------
>  IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>