Re: [101attendees] Registration for IETF 102, Montreal

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Sat, 21 April 2018 06:55 UTC

Return-Path: <prvs=1649f5781d=jordi.palet@consulintel.es>
X-Original-To: 101attendees@ietfa.amsl.com
Delivered-To: 101attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B6F5120724 for <101attendees@ietfa.amsl.com>; Fri, 20 Apr 2018 23:55:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 RNRvniN_I_tq for <101attendees@ietfa.amsl.com>; Fri, 20 Apr 2018 23:55:15 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 015C01200C1 for <101attendees@ietf.org>; Fri, 20 Apr 2018 23:55:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1524293713; x=1524898513; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type:Content-transfer-encoding; bh=TiG8tszN 8yVaEYgj2NrtsthMToGjZDR1EresfGRNL5E=; b=DvTpIBu1+GdS7FLmu5xtxq5V S5WX+itet+VWWPhzD76jrKRB5yL6UHrhAYEKP1+fPCSaeojLUcEFE5SwhFMW4F6y mxUI7rxHnmbl+wjm2c8fWzl1inn8pPOFiNj9ONWltMEMAwRco7+bE0DeBJQ+zDZl xMdunjBF68uX3fLmgUg=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Sat, 21 Apr 2018 08:55:13 +0200
X-Spam-Processed: mail.consulintel.es, Sat, 21 Apr 2018 08:55:12 +0200
Received: from [10.10.10.129] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50005755431.msg for <101attendees@ietf.org>; Sat, 21 Apr 2018 08:55:11 +0200
X-MDRemoteIP: 2001:470:1f09:495:1893:a9ef:252e:27c9
X-MDHelo: [10.10.10.129]
X-MDArrival-Date: Sat, 21 Apr 2018 08:55:11 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1649f5781d=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: 101attendees@ietf.org
User-Agent: Microsoft-MacOutlook/10.c.0.180410
Date: Sat, 21 Apr 2018 08:55:07 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "101attendees@ietf.org" <101attendees@ietf.org>
Message-ID: <06BF3999-605B-4280-960B-4F67A8F8D447@consulintel.es>
Thread-Topic: [101attendees] Registration for IETF 102, Montreal
References: <m28t9ik478.wl-randy@psg.com> <20180420024502.71E5D254669E@ary.qy> <5C4D8E08-625B-40F3-BB8F-047D3AEFCBF1@cable.comcast.com> <23444.1524262042@obiwan.sandelman.ca>
In-Reply-To: <23444.1524262042@obiwan.sandelman.ca>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/101attendees/Fo4aKHMVrUm9nrTjWg72S0q1jTM>
Subject: Re: [101attendees] Registration for IETF 102, Montreal
X-BeenThere: 101attendees@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mailing list of IETF 101 attendees that have opted in on this list <101attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/101attendees>, <mailto:101attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/101attendees/>
List-Post: <mailto:101attendees@ietf.org>
List-Help: <mailto:101attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/101attendees>, <mailto:101attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Apr 2018 06:55:18 -0000

Technical issues?

We are engineers we can solve them!

Regards,
Jordi
 
 
-----Mensaje original-----
De: 101attendees <101attendees-bounces@ietf.org> en nombre de Michael Richardson <mcr@sandelman.ca>
Fecha: sábado, 21 de abril de 2018, 0:07
Para: "101attendees@ietf.org" <101attendees@ietf.org>
Asunto: Re: [101attendees] Registration for IETF 102, Montreal

    Livingood, Jason <Jason_Livingood@comcast.com> wrote:
        > I'm vaguely curious why we hold back registration until 10
        > weeks. Why not open it 1 day after the end of the prior meeting? Or
        > open it 364 days before each meeting or whatever? This seems to
        > regularly recur as a question - so there must be a way to remove the
        > friction / take the issue off the table...
    
    We have been discussing this in the IAOC finance sub-cmte.
    (I think it's I* retreat week this week, btw.  They might be slow to answer)
    
    There are apparently technical issues with having more than one meeting
    registration open at the same time.  I don't know what it is.
    There are apparently other issues that prevent the secretariat from
    being able to automatically open registration for N+1 the day after
    meeting N.  I don't know what they are...
    
    -- 
    ]               Never tell me the odds!                 | ipv6 mesh networks [ 
    ]   Michael Richardson, Sandelman Software Works        | network architect  [ 
    ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [ 
    	
    
    _______________________________________________
    101attendees mailing list
    101attendees@ietf.org
    https://www.ietf.org/mailman/listinfo/101attendees
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.