Greetings again:
Loa is reporting that on his list he is now getting subscribe attacks for = email-to-SMS gateway addresses.=C2=A0 He reports that he's received abo= ut 20 of the following types of subscribe requests in the last day:

= 2524063603@mms.att.net

Obviously, flooding cell phones with junk mail is much more in= vasive than random GMail addresses.=C2=A0 Since this attack targets a US-ba= sed carrier, I have applied the same divert-to-secretariat behavior to addr= esses containing the four primary US cellular carrier domains:

txt.att.net

I did a check, and we have exactly zero users on any of= our lists in any of these domains.=C2=A0 (Which makes sense, most IETF lis= t messages are far too long to deal with over SMS.)=C2=A0 I therefore expec= t that this additional step will have no impact on the community.

As an aside, an interesting, if incomplete, resource for gateway a= ddresses is here:=C2=A0 http:= //www.emailtextmessages.com/=C2=A0

I obviously do no= t intend to apply diversion to all of the domains in their list, but I incl= ude it just for interest.

As always, any questions, let m= e know!

Glen

Glen Barney

IT D= irector

AMS (IETF Secretariat)

--001a11330ab4fbf4b1051ff2255f-- From nobody Thu Sep 17 07:42:27 2015 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8845F1A6F4C for ; Thu, 17 Sep 2015 07:42:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.689 X-Spam-Level: X-Spam-Status: No, score=-101.689 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=unavailable 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 V41FJAtnuH37 for ; Thu, 17 Sep 2015 07:42:01 -0700 (PDT) Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id 35DDD1A6F40 for ; Thu, 17 Sep 2015 07:41:55 -0700 (PDT) Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 7E41C1E5A38 for ; Thu, 17 Sep 2015 07:41:11 -0700 (PDT) Received: from mail-oi0-f51.google.com (mail-oi0-f51.google.com [209.85.218.51]) by c8a.amsl.com (Postfix) with ESMTPSA id 570A31E5A28 for ; Thu, 17 Sep 2015 07:41:11 -0700 (PDT) Received: by oiww128 with SMTP id w128so10543468oiw.2 for ; Thu, 17 Sep 2015 07:41:54 -0700 (PDT) X-Received: by 10.202.68.215 with SMTP id r206mr26303951oia.87.1442500914430; Thu, 17 Sep 2015 07:41:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.102.71 with HTTP; Thu, 17 Sep 2015 07:41:35 -0700 (PDT) From: Glen Date: Thu, 17 Sep 2015 07:41:35 -0700 Message-ID: Subject: Mailman subscribe attacks - Cloudflare To: Glen Barney Content-Type: multipart/alternative; boundary=001a113dce6097cd1e051ff26ad5 Archived-At: X-Mailman-Approved-At: Thu, 17 Sep 2015 07:42:27 -0700 X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: glen@amsl.com List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 14:42:02 -0000 --001a113dce6097cd1e051ff26ad5 Content-Type: text/plain; charset=UTF-8 All - As previously noted, one of the reasons we've been unable to just directly block the hosts which are participating in the Mailman attack is because of our use of Cloudflare. Because we are behind Cloudflare, all incoming requests appear (to our IP stack) to be coming from Cloudflare (which, technically, they are.) Cloudflare does pass the remote IP address in a transaction header, but firewalls can't do anything with that. When we began using Cloudflare, we expected that they would detect and block attacks of this type. Their apparent inability to do so, combined with their lack of responsiveness, increases the difficulty we face in dealing with these attacks. As I have mentioned previously, we have reached out to Cloudflare for help with this on several occasions - we have explained the situation to a number of Cloudflare representatives - and we have never received any response or guidance from them at all. Just yesterday, Russ connected me to a new Cloudflare person - I responded to that immediately, but have not heard back from them at all as of yet. I have high hopes that this new contact will work with us, but I mention this again so that you're all aware that we're trying to work within this system. Meanwhile, working independently, one of my engineers has discovered that there may be an automated way to submit IP bans to Cloudflare. He is currently running this down to determine whether such a thing actually exists, and whether its implementation is feasible. Since we have had no communication or support response from Cloudflare, we are, in essence guessing, but we are pursuing this possibility in the hope that we can better fight off the attack in this way. Of course, this is not an ideal solution either: as additional hosts become compromised, the "ban list" will grow. And, once banned, we will no longer know if a particular host is still compromised and/or attacking us, so we will have no way to know if we should "unban" that host. I do not see this as a permanent solution either, but I wanted to make the leadership and tools teams aware of this new possibility, so you all are in the loop as we continue to fight this attack. As pointed out on some threads - we still hope for a more comprehensive, high-level solution to problems of this type, at some point in the future. As always, any questions, let me know. Best regards, Glen Glen Barney IT Director AMS (IETF Secretariat) --001a113dce6097cd1e051ff26ad5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

All -

As previously = noted, one of the reasons we've been unable to just directly block the = hosts which are participating in the Mailman attack is because of our use o= f Cloudflare.=C2=A0 Because we are behind Cloudflare, all incoming requests= appear (to our IP stack) to be coming from Cloudflare (which, technically,= they are.)=C2=A0 Cloudflare does pass the remote IP address in a transacti= on header, but firewalls can't do anything with that.=C2=A0

When we began using Cloudflare, we expected that they would detect and= =20 block attacks of this type.=C2=A0 Their apparent inability to do so,=20 combined with their lack of responsiveness, increases the difficulty we=20 face in dealing with these attacks.=C2=A0 As I have mentioned previously, w= e have reached out to Cloudflare for help with this on several occasions - = we have explained the situation to a number of Cloudflare representatives -= and we have never received any response or guidance from them at all.=C2= =A0 Just yesterday, Russ connected me to a new Cloudflare person - I respon= ded to that immediately, but have not heard back from them at all as of yet= .=C2=A0 I have high hopes that this new contact will work with us, but I me= ntion this again so that you're all aware that we're trying to work= within this system.

Meanwhile, working independently, one of = my engineers has discovered that there may be an automated way to submit IP= bans to Cloudflare.=C2=A0 He is currently running this down to determine w= hether such a thing actually exists, and whether its implementation is feas= ible.=C2=A0 Since we have had no communication or support response from Clo= udflare, we are, in essence guessing, but we are pursuing this possibility = in the hope that we can better fight off the attack in this way.

Of course, this is not an ideal solution either:=C2=A0 as additional hos= ts become compromised, the "ban list" will grow.=C2=A0 And, once = banned, we will no longer know if a particular host is still compromised an= d/or attacking us, so we will have no way to know if we should "unban&= quot; that host.=C2=A0 I do not see this as a permanent solution either, bu= t I wanted to make the leadership and tools teams aware of this new possibi= lity, so you all are in the loop as we continue to fight this attack.
<= br>

As pointed out on some threads - we still hope for a more com= prehensive, high-level solution to problems of this type, at some point in = the future.

As always, any questions, let me know.

Best regards,

Glen

Glen Barney
<= /div>

IT Director

AMS (IETF Secretariat)

--001a113dce6097cd1e051ff26ad5-- From nobody Thu Sep 17 09:20:29 2015 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80EE11B2B62 for ; Thu, 17 Sep 2015 09:20:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 Xxh__QbrLWs4 for ; Thu, 17 Sep 2015 09:20:25 -0700 (PDT) Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 337531B2C46 for ; Thu, 17 Sep 2015 09:20:25 -0700 (PDT) Received: from [192.168.0.102] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id B0A3E18013BE; Thu, 17 Sep 2015 18:20:23 +0200 (CEST) Subject: Re: Draft posted - Standardizing the zeroth and last code point of a registry To: Cullen Jennings , Jeffrey Haas References: <20150604201832.GA29939@pfrc.org> <20150915142414.GA14958@pfrc.org> <34E00961-04B0-4E04-817C-BC7390B768CE@iii.ca> From: Loa Andersson Message-ID: <55FAE845.5040305@pi.nu> Date: Thu, 17 Sep 2015 18:20:21 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <34E00961-04B0-4E04-817C-BC7390B768CE@iii.ca> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Cc: wgchairs@ietf.org X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 16:20:27 -0000 Cullen, two points - this originated as a wg chair discussion, so I think it is reasonable to see if the draft flies with the chairs - but pretty quickly we should have it discussed in a wider group, but I'm not sure which list, any idea? /Loa On 2015-09-17 04:42, Cullen Jennings wrote: > > I like the draft, but seems like there would be a better list to discuss it on. > > >> On Sep 15, 2015, at 8:24 AM, Jeffrey Haas wrote: >> >> On Thu, Jun 04, 2015 at 04:18:32PM -0400, Jeffrey Haas wrote: >>> John Scudder and I were having a brief discussion regarding some BGP code >>> points managed at IANA. Over the course of that discussion, he suggested >>> that I send one of the thoughts to this list to see if it merited a small >>> draft. >> >> I've put together that small draft and would appreciate review. >> >> The long term goal is to get it published as an RFC. I'd suspect this is a >> general area draft. >> >> : A New Internet-Draft is available from the on-line Internet-Drafts >> : directories. >> : >> : >> : Title : Reservation Strategies for the Zeroth and Last >> : Code Points in IETF Registries and for Bit Field Registries >> : Author : Jeffrey Haas >> : Filename : draft-haas-code-point-reservation-bcp-00.txt >> : Pages : 5 >> : Date : 2015-09-15 >> : >> : Abstract: >> : This document describes common code point reservation strategies for >> : the zeroth and last code points in IANA-managed IETF registries and >> : for bit-field registries. The document additionally provides the >> : reasoning to support these strategies and their adoption as Best >> : Current Practices to be applied to all IETF registries. >> : >> : >> : The IETF datatracker status page for this draft is: >> : https://datatracker.ietf.org/doc/draft-haas-code-point-reservation-bcp/ >> : >> : There's also a htmlized version available at: >> : https://tools.ietf.org/html/draft-haas-code-point-reservation-bcp-00 >> : >> > From nobody Thu Sep 17 10:00:41 2015 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB52E1A049A for ; Thu, 17 Sep 2015 10:00:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.732 X-Spam-Level: X-Spam-Status: No, score=0.732 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7, T_FILL_THIS_FORM_SHORT=0.01] 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 vbG_tslb0Sif for ; Thu, 17 Sep 2015 10:00:39 -0700 (PDT) Received: from mail-yk0-f174.google.com (mail-yk0-f174.google.com [209.85.160.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 802DC1A0389 for ; Thu, 17 Sep 2015 10:00:39 -0700 (PDT) Received: by ykdt18 with SMTP id t18so22847171ykd.3 for ; Thu, 17 Sep 2015 10:00:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=rhHRBstEu2h3CeU1zSs9QmwF1FIgxfb08DrjKt25zdE=; b=DfOAZX5sXhNWtBUlxX3tT3cODsCbJdfCB6BurxEBJ97eg7lPhNLtogKlyT2YJ05gFW RDxiK+tdp+MJ/QVhP8c1pKE12MrbwhQpftNBphz4A31tTT0b+tDujK45wzM+ucN1QPBD mjEhxvW0ZL+ugum4i08nrDQbsYhU/4ABEpwXqf15nfvM2CCiB6plltj6JYBzgP+VZaEo qT1lBUx8/tJeE1KtBmIRF13Fu1XwBYW717aKeIKbu48GmHXPVtK7IRNGoY+3y4WVu77k gB2GdBS+G6fOZOiD53jx9lT1B2CFvoeUbqTBNr1/j0X5X9CfOlq2vRThhuSm/LqQ4h1I 696g== X-Gm-Message-State: ALoCoQmPzLXdvJy4iNk7/1mdNeqfU+HuAcbRFA7oAu80iWTgdHmgNZpGjEXFlOuyl7/IUUpplZZF MIME-Version: 1.0 X-Received: by 10.170.117.84 with SMTP id j81mr154015ykb.47.1442509238739; Thu, 17 Sep 2015 10:00:38 -0700 (PDT) Received: by 10.37.52.135 with HTTP; Thu, 17 Sep 2015 10:00:38 -0700 (PDT) Date: Thu, 17 Sep 2015 13:00:38 -0400 Message-ID: Subject: Contact person for Early Allocation? From: Warren Kumari To: WG Chairs Content-Type: text/plain; charset=UTF-8 Archived-At: X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 17:00:40 -0000 Hi all, So, I'm asking for early allocation of a port under the RFC7120 process. The chairs and AD judge that there is consensus, and then the chairs request IANA to make an early allocation. Fine. No worries. RFC6335 (allocating a port) needs an Assignee and a Contact: o Assignee: Name and email address of the party to whom the assignment is made. This is REQUIRED. The Assignee is the organization, company or individual person responsible for the initial assignment... o Contact: Name and email address of the Contact person for the assignment. This is REQUIRED. The Contact person is the responsible person for the Internet community to send questions to. This person is also authorized to submit changes on behalf of the Assignee; in cases of conflict between the Assignee and the Contact, the Assignee decisions take precedence. Additional address information MAY be provided... So, I *think* that the correct thing here is for the chair who is requesting this to be listed as the Assignee and the document author to be the Contact? Or should the WG be the Assignee? Or the IETF? I could not find clear direction here... Thoughts? W -- I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf From nobody Thu Sep 17 10:13:50 2015 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA8F21ACE68 for ; Thu, 17 Sep 2015 10:13:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.311 X-Spam-Level: X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 ljVsbKV1_vAd for ; Thu, 17 Sep 2015 10:13:47 -0700 (PDT) Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 084761ACDD5 for ; Thu, 17 Sep 2015 10:13:46 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id A6316BE5D; Thu, 17 Sep 2015 18:13:39 +0100 (IST) X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N_0MFbIIxVT1; Thu, 17 Sep 2015 18:13:38 +0100 (IST) Received: from [10.87.48.73] (unknown [86.46.24.221]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 15343BE58; Thu, 17 Sep 2015 18:13:38 +0100 (IST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1442510018; bh=LjGclW/OVuRbCyxoqLgRixtGnJ85Z7rjgUxfs6mR0Z4=; h=Subject:To:References:From:Date:In-Reply-To:From; b=4cKPT1RzX5As8SQTBkgB+SrarvDPplFrMSGLPcMHYkFTyOCm7IMZlxzaU0l1WPgOT 21D2nHfRI2uDhM4NCynv8iqQo2MWHZ+qdqxtsRaLZJH5h1E7R+swCEXAvuZ9qP0PiW ynnvnC8QfxZBWbWnivmYgetydrcmkWlR6Oaycb90= Subject: Re: Contact person for Early Allocation? To: Warren Kumari , WG Chairs References: From: Stephen Farrell Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url= Message-ID: <55FAF4C1.7030606@cs.tcd.ie> Date: Thu, 17 Sep 2015 18:13:37 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 17:13:48 -0000 On 17/09/15 18:00, Warren Kumari wrote: > > So, I *think* that the correct thing here is for the chair who is > requesting this to be listed as the Assignee and the document author > to be the Contact? That'd be fine. As would most anything. You then get a year to fix it whenever you make the early allocation permanent. S. > Or should the WG be the Assignee? Or the IETF? > > I could not find clear direction here... From nobody Thu Sep 17 10:45:03 2015 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BB5C1B2EE7 for ; Thu, 17 Sep 2015 10:45:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.178 X-Spam-Level: X-Spam-Status: No, score=-0.178 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, IP_NOT_FRIENDLY=0.334, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 2LNH_pAQIme9 for ; Thu, 17 Sep 2015 10:45:01 -0700 (PDT) Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 5C0DF1B2EE0 for ; Thu, 17 Sep 2015 10:45:01 -0700 (PDT) Received: by slice.pfrc.org (Postfix, from userid 1001) id 4AA001E366; Thu, 17 Sep 2015 13:48:28 -0400 (EDT) Date: Thu, 17 Sep 2015 13:48:28 -0400 From: Jeffrey Haas To: Loa Andersson , Jari Arkko Subject: Re: Draft posted - Standardizing the zeroth and last code point of a registry Message-ID: <20150917174828.GD28574@pfrc.org> References: <20150604201832.GA29939@pfrc.org> <20150915142414.GA14958@pfrc.org> <34E00961-04B0-4E04-817C-BC7390B768CE@iii.ca> <55FAE845.5040305@pi.nu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55FAE845.5040305@pi.nu> User-Agent: Mutt/1.5.21 (2010-09-15) Archived-At: Cc: wgchairs@ietf.org, Cullen Jennings X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 17:45:02 -0000 On Thu, Sep 17, 2015 at 06:20:21PM +0200, Loa Andersson wrote: > two points > > - this originated as a wg chair discussion, so I think it is reasonable > to see if the draft flies with the chairs > - but pretty quickly we should have it discussed in a wider group, but > I'm not sure which list, any idea? I brought the draft back to the list as Loa says it started here. But I think the draft has gotten most of what it needs from wgchairs. The question does remain: How does one take such a general draft forward? I can prod discussion on ietf@ (I'm subscribed, but I seldom pay attention to that inbox). I should prod Jari again about whether this should simply be a general-area draft. I thought I had done so, but I'm having issues tracking down that mail. -- Jeff From nobody Thu Sep 17 13:56:18 2015 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2EAB1A0366 for ; Thu, 17 Sep 2015 13:55:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.688 X-Spam-Level: X-Spam-Status: No, score=-101.688 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_20=-0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=unavailable 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 hFea7wjM2-gg for ; Thu, 17 Sep 2015 13:55:25 -0700 (PDT) Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id 5E99A1A0273 for ; Thu, 17 Sep 2015 13:55:25 -0700 (PDT) Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id ADC781E5A26 for ; Thu, 17 Sep 2015 13:54:40 -0700 (PDT) Received: from mail-oi0-f47.google.com (mail-oi0-f47.google.com [209.85.218.47]) by c8a.amsl.com (Postfix) with ESMTPSA id 8BE091E5A28 for ; Thu, 17 Sep 2015 13:54:40 -0700 (PDT) Received: by oibi136 with SMTP id i136so16552276oib.3 for ; Thu, 17 Sep 2015 13:55:24 -0700 (PDT) X-Received: by 10.202.78.77 with SMTP id c74mr1102812oib.15.1442523324709; Thu, 17 Sep 2015 13:55:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.102.71 with HTTP; Thu, 17 Sep 2015 13:55:05 -0700 (PDT) From: Glen Date: Thu, 17 Sep 2015 13:55:05 -0700 Message-ID: Subject: Mailman subscribe attacks - Cloudflare redux To: Glen Barney Content-Type: multipart/alternative; boundary=001a11c16d505983d2051ff7a212 Archived-At: X-Mailman-Approved-At: Thu, 17 Sep 2015 13:56:10 -0700 X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: glen@amsl.com List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 20:55:27 -0000 --001a11c16d505983d2051ff7a212 Content-Type: text/plain; charset=UTF-8 All - Seven hours ago I reported that we had discovered an API that allows us to automatically block, in Cloudflare, IP addresses from which attacks are coming. The good news: We successfully deployed a script that let us feed data to that API, and began blocking the IP Addresses in the attacking network. The bad news: Cloudflare appears to have a limit of 2000 entries in their blacklist table. We have exceeded that limit. (We have identified almost twice as many IP addresses currently in use as attack sources.) So, unfortunately, that method will not be a good solution here. At the moment, we have successfully blocked all currently-identified attacks using our configurable referral screen, and we will continue to watch for changes in the attack and adapt as possible. I just wanted to make sure everyone was aware of where this potential solution went. Thanks, Glen Glen Barney IT Director AMS (IETF Secretariat) --001a11c16d505983d2051ff7a212 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

All= -

Seven hours ago I reported that we had discovered an API th= at allows us to automatically block, in Cloudflare, IP addresses from which= attacks are coming.

The good news:=C2=A0 We successfully depl= oyed a script that let us feed data to that API, and began blocking the IP = Addresses in the attacking network.

The bad news:=C2=A0 Cloudf= lare appears to have a limit of 2000 entries in their blacklist table.=C2= =A0 We have exceeded that limit.=C2=A0 (We have identified almost twice as = many IP addresses currently in use as attack sources.)

So, unf= ortunately, that method will not be a good solution here.

At t= he moment, we have successfully blocked all currently-identified attacks us= ing our configurable referral screen, and we will continue to watch for cha= nges in the attack and adapt as possible.

I just wanted to mak= e sure everyone was aware of where this potential solution went.

Thanks,

Glen

Glen Barney

IT Director
AMS (IETF Secretariat)

--001a11c16d505983d2051ff7a212-- From nobody Thu Sep 17 16:49:15 2015 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3F061A010D for ; Thu, 17 Sep 2015 16:48:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.587 X-Spam-Level: X-Spam-Status: No, score=-103.587 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=unavailable 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 hweTFcTF9j0V for ; Thu, 17 Sep 2015 16:48:03 -0700 (PDT) Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id 3E4B71A879F for ; Thu, 17 Sep 2015 16:48:02 -0700 (PDT) Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 114B51E5A0A for ; Thu, 17 Sep 2015 16:47:17 -0700 (PDT) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by c8a.amsl.com (Postfix) with ESMTPSA id E48911E5A11 for ; Thu, 17 Sep 2015 16:47:16 -0700 (PDT) Received: by obbzf10 with SMTP id zf10so25858997obb.2 for ; Thu, 17 Sep 2015 16:48:01 -0700 (PDT) X-Received: by 10.182.19.167 with SMTP id g7mr1778958obe.13.1442533681489; Thu, 17 Sep 2015 16:48:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.102.71 with HTTP; Thu, 17 Sep 2015 16:47:42 -0700 (PDT) From: Glen Date: Thu, 17 Sep 2015 16:47:42 -0700 Message-ID: Subject: Mailman attacks - Cloudflare Contact To: Glen Barney Content-Type: multipart/alternative; boundary=001a11c2ea20a96ea0051ffa0b2d Archived-At: X-Mailman-Approved-At: Thu, 17 Sep 2015 16:49:14 -0700 X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: glen@amsl.com List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 23:48:04 -0000 --001a11c2ea20a96ea0051ffa0b2d Content-Type: text/plain; charset=UTF-8 All - Just by way of a final follow-up, I'm very happy to report that, thanks to Russ, I'm now in touch with one of the top people at Cloudflare. I'll be working with them directly to further mitigate the attacks and find a good long-term solution. One of the things we've already found is that they're able to increase the 2000-address limit I reported earlier, and they will be doing that for us shortly. That will enable us to add the remaining IP addresses to the tables and at least get the compromised hosts blocked. We have other ideas we'll be exploring as well, and, hopefully, we can make things better going forward. In the meantime, we'll be watching for any new attack vectors, but please do report any anomalies or new attacks you find to me directly, and we'll do what is needed to get it handled. I personally am on travel tomorrow, so I will not be able to respond immediately to any emails, but my staff will be here and working with Cloudflare to get the remaining hosts blocked. Thank you all for your patience and support during this rather strange and bumpy episode. I'm very hopefully that this is the end of it, or will be very shortly. Best regards, Glen Glen Barney IT Director AMS (IETF Secretariat) --001a11c2ea20a96ea0051ffa0b2d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

All= -

Just by way of a final follow-up, I'm very happy to rep= ort that, thanks to Russ, I'm now in touch with one of the top people a= t Cloudflare.=C2=A0 I'll be working with them directly to further mitig= ate the attacks and find a good long-term solution.

One of the= things we've already found is that they're able to increase the 20= 00-address limit I reported earlier, and they will be doing that for us sho= rtly.=C2=A0 That will enable us to add the remaining IP addresses to the ta= bles and at least get the compromised hosts blocked.

We have o= ther ideas we'll be exploring as well, and, hopefully, we can make thin= gs better going forward.

In the meantime, we'll be watchin= g for any new attack vectors, but please do report any anomalies or new att= acks you find to me directly, and we'll do what is needed to get it han= dled.=C2=A0

I personally am on travel tomorrow, so I will not= be able to respond immediately to any emails, but my staff will be here an= d working with Cloudflare to get the remaining hosts blocked.

= Thank you all for your patience and support during this rather strange and = bumpy episode.=C2=A0 I'm very hopefully that this is the end of it, or = will be very shortly.

Best regards,

Glen

Gle= n Barney

IT Director

AMS (IETF Secretariat)

--001a11c2ea20a96ea0051ffa0b2d-- From nobody Thu Sep 17 16:58:38 2015 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5FA51A87ED for ; Thu, 17 Sep 2015 16:58:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.511 X-Spam-Level: X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 0dS0xFff4jNr for ; Thu, 17 Sep 2015 16:58:32 -0700 (PDT) Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F157C1A1AE8 for ; Thu, 17 Sep 2015 16:58:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=726; q=dns/txt; s=iport; t=1442534312; x=1443743912; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=YoZ2jnZZzrWCLu34EuDto46YlV5ZE9Mkm+6cOxerleM=; b=NvbM14PIsJJblPFU906T/LHsngjhTJ2qZ7E87dKBYNGBWeiE9S8w0A8B wi37pJzhV477NPY4IfCiQtLGhVrlOrm48lHFYLUIFIYf6OWm3XlayPSjv KQaKOzKWNw81fJl+SLHk+C16xyhpPI/O6jAKRkFi5Jfv2TEJL8iC5O1qv 8=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0D/BABUUvtV/5tdJa1dgyOBPapemmcCgUQ7EQEBAQEBAQGBCoQjAQEBAwE6PwULAgEIDgoeEDIlAgQOBYgmCMtuAQEBAQEBAQEBAQEBAQEBAQEBAQEYhnMBgg6CboQzCAEBHTMHgxiBFAEEhT2MfIMoAYpTgjKbGjcshAFxiGuBPwEBAQ X-IronPort-AV: E=Sophos;i="5.17,549,1437436800"; d="scan'208";a="188354990" Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-2.cisco.com with ESMTP; 17 Sep 2015 23:58:31 +0000 Received: from XCH-RCD-017.cisco.com (xch-rcd-017.cisco.com [173.37.102.27]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t8HNwVoj031089 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 17 Sep 2015 23:58:31 GMT Received: from xch-rcd-017.cisco.com (173.37.102.27) by XCH-RCD-017.cisco.com (173.37.102.27) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 17 Sep 2015 18:58:24 -0500 Received: from xhc-aln-x04.cisco.com (173.36.12.78) by xch-rcd-017.cisco.com (173.37.102.27) with Microsoft SMTP Server (TLS) id 15.0.1104.5 via Frontend Transport; Thu, 17 Sep 2015 18:58:24 -0500 Received: from xmb-aln-x15.cisco.com ([169.254.9.140]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.03.0248.002; Thu, 17 Sep 2015 18:58:24 -0500 From: "Alvaro Retana (aretana)" To: Jeffrey Haas Subject: Re: Draft posted - Standardizing the zeroth and last code point of a registry Thread-Topic: Draft posted - Standardizing the zeroth and last code point of a registry Thread-Index: AQHQ78G+IVU4a6LsbEiwfIWu6QaQvJ5AWWQAgADkaYCAABifAIAAE4km Date: Thu, 17 Sep 2015 23:58:23 +0000 Message-ID: References: <20150604201832.GA29939@pfrc.org> <20150915142414.GA14958@pfrc.org> <34E00961-04B0-4E04-817C-BC7390B768CE@iii.ca> <55FAE845.5040305@pi.nu>,<20150917174828.GD28574@pfrc.org> In-Reply-To: <20150917174828.GD28574@pfrc.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Cc: "wgchairs@ietf.org" , Cullen Jennings X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 23:58:33 -0000 Sent from my iPad > On Sep 17, 2015, at 1:45 PM, Jeffrey Haas wrote: >=20 > The question does remain: How does one take such a general draft forward? > I can prod discussion on ietf@ (I'm subscribed, but I seldom pay attentio= n > to that inbox). =20 >=20 > I should prod Jari again about whether this should simply be a general-ar= ea > draft. I thought I had done so, but I'm having issues tracking down that > mail. Jeff: Hi! =20 I think that the ietf@ list would be a good place for discussion. It's sur= prising the number of people who pay attention to it. ;-) I'll give Jari the right if first refusal -- I'd be willing to sponsor this= work. Thanks! Alvaro.= From nobody Fri Sep 18 07:04:30 2015 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD6851B2C32 for ; Fri, 18 Sep 2015 07:04:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.321 X-Spam-Level: X-Spam-Status: No, score=0.321 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, IP_NOT_FRIENDLY=0.334, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 fJ3ocYLSoitk for ; Fri, 18 Sep 2015 07:04:28 -0700 (PDT) Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 0D8B71B2C21 for ; Fri, 18 Sep 2015 07:04:28 -0700 (PDT) Received: by slice.pfrc.org (Postfix, from userid 1001) id 749DE1E366; Fri, 18 Sep 2015 10:07:56 -0400 (EDT) Date: Fri, 18 Sep 2015 10:07:56 -0400 From: Jeffrey Haas To: Warren Kumari Subject: Re: Contact person for Early Allocation? Message-ID: <20150918140756.GG28574@pfrc.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Archived-At: Cc: WG Chairs X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 14:04:28 -0000 Warren, On Thu, Sep 17, 2015 at 01:00:38PM -0400, Warren Kumari wrote: > So, I *think* that the correct thing here is for the chair who is > requesting this to be listed as the Assignee and the document author > to be the Contact? > Or should the WG be the Assignee? Or the IETF? My recommendation is to use the -chairs alias for the following reasons: - It is hopefully a long-lived address. - Those addresses are heavily harvested and will receive a bunch of spam. :-( - The entry is unlikely to be orphaned quite as much. See for example [BFD_Chairs] in the service-names-port-numbers registry. The port # assignments especially are full of nonsense or stale addresses. I once looked into getting a former boss off of his assignment from 10+ years ago, and since his email was no longer active there it seemed to be more pain than it was worth. -- Jeff From nobody Fri Sep 18 07:42:49 2015 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CF8C1B2D26 for ; Fri, 18 Sep 2015 07:42:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.978 X-Spam-Level: X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] 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 SdKawqFZgDwn for ; Fri, 18 Sep 2015 07:42:46 -0700 (PDT) Received: from mail-yk0-f182.google.com (mail-yk0-f182.google.com [209.85.160.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E8E31B2D1A for ; Fri, 18 Sep 2015 07:42:46 -0700 (PDT) Received: by ykft14 with SMTP id t14so48495951ykf.0 for ; Fri, 18 Sep 2015 07:42:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=TcCAltLHPR2QJzjlwUgtj6+iHyL7awBoQTnXnK/pwj4=; b=K/1DkPkgrzETr2/wwra3oG5jtKFnb6r+iCuAv7jZMe8FlEnL4ka4CPTcf0FjBLKGkS GsNNsXUnzRen0f0gJETttigPtvERVy5MDmGmszslJ5TbTVK4KtXGjdEvl8ALpnO6iKNY xCIhBbqA9rMLOMGn6LoPkfFVtRL97QD1IICX/qgRcJbvl4O47WDhfz2o0c82VKKCLDeM 9qCqWERXS8qIrKLHvTxQ5s+wCYQruE90xjnjPs+f2s88oRz1L7q4aPEzihlIywfMC9zt bckJmdo3Ebgro7lIsbkLPKzqBlnvjSfnxKdjMvGt5Wb6wadjZWMg1GJ2QDen7RaC49bD K94g== X-Gm-Message-State: ALoCoQnkLerl53TCjsRR3kLPngNs524Hwh+2l6XqjOFN1RYR3VmhMINQ+/2JLqgdROrZGcYC+S2M MIME-Version: 1.0 X-Received: by 10.170.44.19 with SMTP id 19mr4970995ykm.4.1442587365266; Fri, 18 Sep 2015 07:42:45 -0700 (PDT) Received: by 10.37.52.135 with HTTP; Fri, 18 Sep 2015 07:42:45 -0700 (PDT) In-Reply-To: <20150918140756.GG28574@pfrc.org> References: <20150918140756.GG28574@pfrc.org> Date: Fri, 18 Sep 2015 10:42:45 -0400 Message-ID: Subject: Re: Contact person for Early Allocation? From: Warren Kumari To: Jeffrey Haas Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: WG Chairs X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 14:42:48 -0000 On Fri, Sep 18, 2015 at 10:07 AM, Jeffrey Haas wrote: > Warren, > > On Thu, Sep 17, 2015 at 01:00:38PM -0400, Warren Kumari wrote: >> So, I *think* that the correct thing here is for the chair who is >> requesting this to be listed as the Assignee and the document author >> to be the Contact? >> Or should the WG be the Assignee? Or the IETF? > > My recommendation is to use the -chairs alias for the following reasons: > - It is hopefully a long-lived address. > - Those addresses are heavily harvested and will receive a bunch of spam. > :-( > - The entry is unlikely to be orphaned quite as much. > > See for example [BFD_Chairs] in the service-names-port-numbers registry. Huh, thanks, that sounds clean. I think I'll do that... W > > The port # assignments especially are full of nonsense or stale addresses. > I once looked into getting a former boss off of his assignment from 10+ > years ago, and since his email was no longer active there it seemed to be > more pain than it was worth. > > -- Jeff -- I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf From nobody Fri Sep 18 10:42:55 2015 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FD951A877D; Fri, 18 Sep 2015 10:42:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.3 X-Spam-Level: X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_12=0.6] autolearn=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 EkAqoBx3mxm7; Fri, 18 Sep 2015 10:42:52 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E3971A871A; Fri, 18 Sep 2015 10:42:52 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: IETF Agenda To: "Working Group Chairs" Subject: REMINDER - IETF 94 Working Group/BOF/IRTF Scheduling Deadline Today X-Test-IDTracker: no X-IETF-IDTracker: 6.4.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150918174252.5641.5409.idtracker@ietfa.amsl.com> Date: Fri, 18 Sep 2015 10:42:52 -0700 Archived-At: Cc: irsg@irtf.org X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.15 Reply-To: IETF Agenda List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 17:42:54 -0000 ----------------------------------------------------------------- IETF 94 – Yokohama, Japan Meeting Dates: November 1-6, 2015 ----------------------------------------------------------------- The deadline to submit a session request or BOF proposal is today. The milestones and deadlines for scheduling-related activities are as follows: Cut-off dates are subject to change. • 2015-09-18 (Friday): Cut-off date for requests to schedule Working Group meetings at UTC 23:59. To request a Working Group session, use the IETF Meeting Session Request Tool. • 2015-09-18 (Friday): Cut-off date for BOF proposal requests to Area Directors at UTC 23:59. To request a BOF, please see instructions on Requesting a BOF. • 2015-09-25 (Friday): Cut-off date for Area Directors to approve BOFs at UTC 23:59. • 2015-10-02 (Friday): Preliminary agenda published for comment. • 2015-10-07 (Wednesday): Cut-off date for requests to reschedule Working Group and BOF meetings UTC 23:59. • 2015-10-09 (Friday): Final agenda to be published. • 2015-10-19 (Monday): Draft Working Group agendas due by UTC 23:59, upload using IETF Meeting Materials Management Tool. • 2015-10-26 (Monday): Revised Working Group agendas due by UTC 23:59, upload using IETF Meeting Materials Management Tool. • 2015-12-04 (Friday): Proceedings submission cutoff date by UTC 23:59, upload using IETF Meeting Materials Management Tool. • 2015-12-21 (Monday): Proceedings submission corrections cutoff date by UTC 23:59, upload using IETF Meeting Materials Management Tool. =============================================================== Comprehensive information on requesting meeting sessions is below: 1. Requests to schedule Working Group sessions should be submitted using the "IETF Meeting Session Request Tool," a Web-based tool for submitting all of the information required by the Secretariat to schedule your sessions. The URL for the tool is: https://datatracker.ietf.org/secr/sreq/ Instructions for using the tool are available at: http://www.ietf.org/wg/request-tool-instructions.html If you require an account on this tool, or assistance in using it, then please send a message to ietf-action@ietf.org. If you are unable to use the tool, then you may send your request via e-mail to agenda@ietf.org, with a copy to the appropriate Area Director(s). Requests to schedule BOF sessions must be sent to agenda@ietf.org with a copy to the appropriate Area Director(s). When submitting a Working Group or BOF session request by e-mail, please include the Working Group or BOF acronym in the Subject line. 2. BOFs will NOT be scheduled unless the Area Director approves the BOF. The proponents behind a BOF need to contact a relevant Area Director, preferably well in advance of the BOF approval deadline date. The AD needs to have the full name of the BOF, its acronym, suggested names of chairs, an agenda, full description of the BOF and the information covered in item 4. Please read RFC 5434 for instructions on how to drive a successful BOF effort. The approval depends on, for instance, Internet-Drafts and list discussion on the suggested topic. BOF agenda requests, if approved, will be submitted to the IETF Secretariat by the ADs. 3. A Working Group may request either one or two sessions. If your Working Group requires more than two sessions, then your request must be approved by an Area Director. Additional sessions will be assigned, based on availability, after Wednesday, October 7th, 2015, the cut-off date for requests to reschedule a session. 4. You MUST provide the following information before a Working Group or BOF session will be scheduled: a. Working Group or BOF full name with acronym in brackets: b. AREA under which Working Group or BOF appears: c. CONFLICTS you wish to avoid, please be as specific as possible: d. Expected Attendance: e. Special requests: f. Number of sessions: g. Length of session: 1 hour, 1.5 hours, 2 hours, 2.5 hours For more information on scheduling Working Group and BOF sessions, please refer to RFC 2418 (BCP 25), "IETF Working Group Guidelines and Procedures" (http://www.ietf.org/rfc/rfc2418.txt). =============================================================== Submitting Session Agendas For the convenience of meeting attendees, we ask that you submit the agendas for your Working Group sessions as early as possible. Draft Working Group agendas are due Monday, October 10th, 2015 at UTC 23:59. Revised Working Group agendas are due no later than Monday, October 26th, 2015 at UTC 23:59. The proposed agenda for a BOF session should be submitted along with your request for a session. Please be sure to copy your Area Director on that message. Please submit the agendas for your Working Group sessions using the "IETF Meeting Materials Management Tool," a Web-based tool for making your meeting agenda, minutes, and presentation slides available to the community before, during, and after an IETF meeting. If you are a BOF chair, then you may use the tool to submit a revised agenda as well as other materials for your BOF once the BOF has been approved. The URL for the tool is: https://datatracker.ietf.org/secr/proceedings/ Additional information about this tool is available at: http://www.ietf.org/wg/meeting-materials.html Agendas submitted via the tool will be available to the public on the "IETF Meeting Materials" webpage as soon as they are submitted. The URL for the "IETF 94 Meeting Materials" Web page is: https://datatracker.ietf.org/meeting/94/materials.html If you are a Working Group chair, then you already have accounts on the "IETF Meeting Session Request Tool" and the "IETF Meeting Materials Management Tool." The same User ID and password will work for both tools. If you are a BOF chair who is not also a Working Group chair, then you will be given an account on the "IETF Meeting Materials Management Tool" when your BOF has been approved. If you require assistance in using either tool, or wish to report a bug, then please send a message to: ietf-action@ietf.org. =============================================================== For your convenience please find a list of the IETF Area Directors with their e-mail addresses below: IETF Chair Jari Arkko Applications and Real-Time Area (art) Alissa Cooper Ben Campbell Barry Leiba Internet Area (int) Brian Haberman Terry Manderson Operations & Management Area (ops) Benoit Claise Joel Jaeggli Routing Area (rtg) Alia Atlas Deborah Brungard Alvaro Retana Security Area (sec) Stephen Farrell Kathleen Moriarty Transport Area (tsv) Spencer Dawkins Martin Stiemerling =========================================================== IETF 93 Meeting Attendance Numbers 6lo – 99 6lo (2nd session) - 66 6man - 127 6tisch – 42 abfab - 17 ace - 74 acme - 123 alto - 29 anima – 77 anima (2nd session) - 66 appsawg/apparea - 111 aqm – 73 avtcore - 43 avtext – 35 bess – 107 bier - 59 bmwg – 37 capport (BoF) - 123 ccamp - 38 cdni – 48 cfrg - 120 clue – 13 core - 60 core (2nd session) – 55 cose - 75 dane – 145 dbound – 86 detnet (BoF) - 173 dhc – 40 dime - 13 dispatch - 49 dmm – 43 dnsop - 158 dnssd – 46 dots - 91 dprive – 82 dtn – 27 edunext (BoF) - 47 ecrit - 17 eppext – 37 gaia - 58 grow - 37 homenet – 132 hopsrg (PRG) – do not have numbers yet hrpc - 62 httpauth - 53 httpbis - 84 i2rs – 106 i2rs (2nd session) – do not have numbers yet iccrg (RG) - 66 icnrg (RG) - 115 idr – 134 idr (2nd session) – do not have numbers yet intarea (AG) - 51 ippm – do not have numbers yet ipsecme - 56 irtfopen - 161 isis – 52 l3sm - 43 lime - 26 lisp - 37 lmap – 41 lwig - 29 manet - 23 mboned - 36 mif - 45 mile - 29 mmusic - 38 mmusic (2nd session) – 36 modern - 51 mpls - 63 mpls (2nd session) – 81 mptcp - 63 netconf - 64 netmod – 97 netmod (2nd session) – 85 netvc – 61 netvc (2nd session) - 60 nfsv4 – 10 nfvrg – 141 nmrg - 35 ntp (combined with tictoc) - 22 nvo3 – 108 nwcrg (RG) - 23 oauth – 42 openpgp – do not have numbers yet opsarea – 57 ospf – 32 pals – 36 payload - 26 pce – 68 perc - 60 pim - 36 radext - 16 rmcat – 62 roll - 30 rtcweb - 77 rtcweb (2nd session) - 61 rtgarea - 87 rtgwg – 131 rtgwg (2nd session) - 86 saag - 165 sacm - 38 sacm (2nd session) - 21 sdnrg (RG) – 237 sfc - 117 sidr – 48 softwire - 31 spring – 119 stir – 37 sunset4 (joint with v6ops) – 147 sunset4 (2nd session, joint with v6ops) - 96 supa (BoF) – 132 t2trg (PRG) - 130 taps - 62 tcpinc - 89 tcpm – 67 teas - 57 tictoc (combined with ntp) - 22 tls – 117 tokbind - 33 tram – 34 tram (2nd session) - 29 trans - 44 trill – 17 tsvarea – 54 tsvwg - 71 tsvwg (2nd session) - 61 uta - 56 v6ops (joint with sunset4) - 147 v6ops (2nd session, joint with sunset4) – 96 webpush – 58 xrblock - 12 From nobody Fri Sep 18 11:25:19 2015 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AEA71B3038 for ; Fri, 18 Sep 2015 11:25:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 ABFwbvV7gSA1 for ; Fri, 18 Sep 2015 11:25:17 -0700 (PDT) Received: from [10.23.20.53] (unknown [209.249.118.20]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 032A41B3037 for ; Fri, 18 Sep 2015 11:25:16 -0700 (PDT) From: IETF Chair Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Fwd: Use ietf.org mail aliases instead of tool.ietf.org aliases Date: Fri, 18 Sep 2015 11:25:16 -0700 References: <24CFD2EF-7F88-4D43-955B-D814D082FC12@ietf.org> To: WG Chairs Message-Id: Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) Archived-At: X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 18:25:18 -0000 FYI on this list as well. Begin forwarded message: > From: IETF Chair > Subject: Use ietf.org mail aliases instead of tool.ietf.org aliases > Date: 18 Sep 2015 10:56:35 PDT > To: IETF Announcement List > Cc: IETF > Reply-To: ietf@ietf.org >=20 > I wanted to remind everyone that all mail aliases that we=92ve had on > tools.ietf.org are now available from ietf.org directly. Here are the > aliases for drafts: >=20 > draftname@ietf.org Draft authors (for now, could = change) > draftname.authors@ietf.org Draft authors (explicitly; will not = change) > draftname.chairs@ietf.org WG Chairs (if the draft is a WG draft) > draftname.shepherd@ietf.org The document shepherd, if one has been = assigned > draftname.ad@ietf.org The sponsoring AD, if the draft = has gone to the IESG > draftname.all@ietf.org All of the above, merged into = one alias >=20 > and for other things: >=20 > wgname-chairs@ietf.org WG Chairs > wgname-ads@ietf.org All ADs for the WG's area (not just the = responsible one) > areaname-chairs@ietf.org All WG Chairs in the specified area > areaname-ads@ietf.org All ADs for the specified area >=20 > The tools aliases continue to work, but we would like to migrate to = the use > of the ietf.org ones, and eventually the tools ones will be = discontinued. >=20 > (And I wanted to thank Henrik, the tools team, and the AMS staff for > their work on these very useful services.) >=20 > Jari Arkko, IETF Chair >=20 From nobody Fri Sep 18 11:32:30 2015 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5E5F1B2FD5; Fri, 18 Sep 2015 11:27:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.347 X-Spam-Level: X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=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 TVyxmo6hH5d4; Fri, 18 Sep 2015 11:27:36 -0700 (PDT) Received: from hoffman.proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 550911B2FD0; Fri, 18 Sep 2015 11:27:36 -0700 (PDT) Received: from [10.32.60.124] (142-254-17-123.dsl.dynamic.fusionbroadband.com [142.254.17.123]) (authenticated bits=0) by hoffman.proper.com (8.15.1/8.14.9) with ESMTPSA id t8IIRZAU058436 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 Sep 2015 11:27:35 -0700 (MST) (envelope-from paul.hoffman@vpnc.org) X-Authentication-Warning: hoffman.proper.com: Host 142-254-17-123.dsl.dynamic.fusionbroadband.com [142.254.17.123] claimed to be [10.32.60.124] From: "Paul Hoffman" To: irsg@irtf.org, "Working Group Chairs" Subject: Re: REMINDER - IETF 94 Working Group/BOF/IRTF Scheduling Deadline Today Date: Fri, 18 Sep 2015 11:27:37 -0700 Message-ID: <59BCFDD7-DB30-4411-8584-D0839EB3C8DF@vpnc.org> In-Reply-To: <20150918174252.5641.5409.idtracker@ietfa.amsl.com> References: <20150918174252.5641.5409.idtracker@ietfa.amsl.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Mailer: MailMate (1.9.1r5084) Archived-At: X-Mailman-Approved-At: Fri, 18 Sep 2015 11:32:28 -0700 Cc: IETF Agenda X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 18:27:37 -0000 As a brief follow-up, do note that if your WG/RG is not meeting, there is a way to say that affirmatively, and doing so will help others with their planning. --Paul Hoffman (who has said that IPsecME is not meeting) From nobody Fri Sep 18 11:46:29 2015 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84FE91A88C6 for ; Fri, 18 Sep 2015 11:46:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.431 X-Spam-Level: X-Spam-Status: No, score=-3.431 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_NEUTRAL=0.779, T_RP_MATCHES_RCVD=-0.01] 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 xQ6p_bh0wZh8 for ; Fri, 18 Sep 2015 11:46:27 -0700 (PDT) Received: from out.west.pexch112.icann.org (pfe112-ca-1.pexch112.icann.org [64.78.40.7]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98B511A87B8 for ; Fri, 18 Sep 2015 11:46:20 -0700 (PDT) Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Fri, 18 Sep 2015 11:46:18 -0700 Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1044.021; Fri, 18 Sep 2015 11:46:18 -0700 From: Michelle Cotton To: Warren Kumari , Jeffrey Haas Subject: Re: Contact person for Early Allocation? Thread-Topic: Contact person for Early Allocation? Thread-Index: AQHQ8WpyxSrfLCLSnUONOJiyX4Rkd55CyVkAgAAJuoD//86wgA== Date: Fri, 18 Sep 2015 18:46:17 +0000 Message-ID: References: <20150918140756.GG28574@pfrc.org> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.5.4.150722 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [192.0.32.234] Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3525421575_31569040" MIME-Version: 1.0 Archived-At: Cc: WG Chairs X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 18:46:28 -0000 --B_3525421575_31569040 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Hello, If ultimately the reference will be an RFC, you can use IETF Chair/IESG. There are many examples of this currently in registries. Best regards, Michelle **** Michelle Cotton Protocol Parameters Engagement Manager ICANN On 9/18/15, 7:42 AM, "iesg on behalf of Warren Kumari" wrote: >On Fri, Sep 18, 2015 at 10:07 AM, Jeffrey Haas wrote: >> Warren, >> >> On Thu, Sep 17, 2015 at 01:00:38PM -0400, Warren Kumari wrote: >>> So, I *think* that the correct thing here is for the chair who is >>> requesting this to be listed as the Assignee and the document author >>> to be the Contact? >>> Or should the WG be the Assignee? Or the IETF? >> >> My recommendation is to use the -chairs alias for the following >>reasons: >> - It is hopefully a long-lived address. >> - Those addresses are heavily harvested and will receive a bunch of >>spam. >> :-( >> - The entry is unlikely to be orphaned quite as much. >> >> See for example [BFD_Chairs] in the service-names-port-numbers registry. > > >Huh, thanks, that sounds clean. I think I'll do that... > >W > >> >> The port # assignments especially are full of nonsense or stale >>addresses. >> I once looked into getting a former boss off of his assignment from 10+ >> years ago, and since his email was no longer active there it seemed to >>be >> more pain than it was worth. >> >> -- Jeff > > > >-- >I don't think the execution is relevant when it was obviously a bad >idea in the first place. >This is like putting rabid weasels in your pants, and later expressing >regret at having chosen those particular rabid weasels and that pair >of pants. > ---maf > --B_3525421575_31569040 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" MIITrwYJKoZIhvcNAQcCoIIToDCCE5wCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC EXswggb2MIIF3qADAgECAhAFLoNW3qD4JhFZyohPBtNqMA0GCSqGSIb3DQEBBQUAMGIxCzAJ BgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2Vy dC5jb20xITAfBgNVBAMTGERpZ2lDZXJ0IEFzc3VyZWQgSUQgQ0EtMTAeFw0xMzAzMjAwMDAw MDBaFw0xNjAzMjAxMjAwMDBaMIGfMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5p YTEUMBIGA1UEBxMLTG9zIEFuZ2VsZXMxPDA6BgNVBAoTM0ludGVybmV0IENvcnBvcmF0aW9u IGZvciBBc3NpZ25lZCBOYW1lcyBhbmQgTnVtYmVyczENMAsGA1UECxMESUFOQTEYMBYGA1UE AxMPTWljaGVsbGUgQ290dG9uMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxWwq bCL/Xkl+g9mKzyjxA8YKyTJgMKkfuNPm2Pi5iWmUGpAHkSCUX/YKf1rninFM8JkzffVgInmx juZQRW7lP2796RU0UAUdEsbfDcE5l4dj8h7omA2HkiwvKgxBwegr8VHjzUxOzSetAio5Y2qA Fs7EY97BX6aulzP+tyKi5+7GSBRq+SguiLYETk4FZo8nmyK8E0210+ozwlUQ0VSfkpWluyc/ wQtRo/vQYoM0DPgVaxkE9r20ReyqaE+mxN2pqKl8qoiNMUAnbJIVUSfZhIxS4yoVKNLsOJzo CYSrD6JgNOmzbEOfrTMWMAhh1RCqp5bcaZ4Zlq2lbrIGHzPgSwIDAQABo4IDaDCCA2QwHwYD VR0jBBgwFoAUFQASKxOYspkH7R7for5XDStnAs0wHQYDVR0OBBYEFFcRyKFrxJAiHzozbxx0 fzjeiYmeMCQGA1UdEQQdMBuBGW1pY2hlbGxlLmNvdHRvbkBpY2Fubi5vcmcwDgYDVR0PAQH/ BAQDAgWgMB0GA1UdJQQWMBQGCCsGAQUFBwMEBggrBgEFBQcDAjB9BgNVHR8EdjB0MDigNqA0 hjJodHRwOi8vY3JsMy5kaWdpY2VydC5jb20vRGlnaUNlcnRBc3N1cmVkSURDQS0xLmNybDA4 oDagNIYyaHR0cDovL2NybDQuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0QXNzdXJlZElEQ0EtMS5j cmwwggHFBgNVHSAEggG8MIIBuDCCAbQGCmCGSAGG/WwEAQIwggGkMDoGCCsGAQUFBwIBFi5o dHRwOi8vd3d3LmRpZ2ljZXJ0LmNvbS9zc2wtY3BzLXJlcG9zaXRvcnkuaHRtMIIBZAYIKwYB BQUHAgIwggFWHoIBUgBBAG4AeQAgAHUAcwBlACAAbwBmACAAdABoAGkAcwAgAEMAZQByAHQA aQBmAGkAYwBhAHQAZQAgAGMAbwBuAHMAdABpAHQAdQB0AGUAcwAgAGEAYwBjAGUAcAB0AGEA bgBjAGUAIABvAGYAIAB0AGgAZQAgAEQAaQBnAGkAQwBlAHIAdAAgAEMAUAAvAEMAUABTACAA YQBuAGQAIAB0AGgAZQAgAFIAZQBsAHkAaQBuAGcAIABQAGEAcgB0AHkAIABBAGcAcgBlAGUA bQBlAG4AdAAgAHcAaABpAGMAaAAgAGwAaQBtAGkAdAAgAGwAaQBhAGIAaQBsAGkAdAB5ACAA YQBuAGQAIABhAHIAZQAgAGkAbgBjAG8AcgBwAG8AcgBhAHQAZQBkACAAaABlAHIAZQBpAG4A IABiAHkAIAByAGUAZgBlAHIAZQBuAGMAZQAuMHcGCCsGAQUFBwEBBGswaTAkBggrBgEFBQcw AYYYaHR0cDovL29jc3AuZGlnaWNlcnQuY29tMEEGCCsGAQUFBzAChjVodHRwOi8vY2FjZXJ0 cy5kaWdpY2VydC5jb20vRGlnaUNlcnRBc3N1cmVkSURDQS0xLmNydDAMBgNVHRMBAf8EAjAA MA0GCSqGSIb3DQEBBQUAA4IBAQAzABp5GDSqoV3ty0YLFXRO8ZlHtgsLOP+5AmAS9P0mDEny uO6xbrWK/Oi+9/UfcnYKYUGkFvukHBFLowWakQngPhHLjEhNl2QYC4dbQWLd9z4gZWBWYVzs EreLwUSbRbE3G1r/lkUK3EYO5xAAWtFcv0I4Ixd3//0zxg0ohWW7fm22ypXr8HIBffpptim+ 6oO6X55ME5789phHZZDQt6haEHyMnAQNW2SL6e8cgSL30lPcpStRCXriyXBdoSI+oW83+9u3 SvhjG9WXw8sso9oWMBWo8BhSTERNzLYbxQMazYHW5L/BUBUICTR6l3W96+rjpPZDZVpd9wgR AG54dZ+mMIIGwjCCBaqgAwIBAgIQCgTfIXRdTSuM6jNyBQBQ6TANBgkqhkiG9w0BAQUFADBl MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGln aWNlcnQuY29tMSQwIgYDVQQDExtEaWdpQ2VydCBBc3N1cmVkIElEIFJvb3QgQ0EwHhcNMDYx MTEwMDAwMDAwWhcNMjExMTEwMDAwMDAwWjBiMQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGln aUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQuY29tMSEwHwYDVQQDExhEaWdpQ2Vy dCBBc3N1cmVkIElEIENBLTEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDogi2Z +crCQpWlgHNAcNKeVlRcqcTSQQaPyTP8TUWRXIGf7Syc+BZZ3561JBXCmLm0d0ncicQK2q/L XmvtrbBxMevPOkAMRk2T7It6NggDqww0/hhJgv7HxzFIgHweog+SDlDJxofrNj/YMMP/pvf7 os1vcyP+rFYFkPAyIRaJxnCI+QWXfaPHQ90C6Ds97bFBo+0/vtuVSMTuHrPyvAwrmdDGXRJC geGDboJzPyZLFJCuWWYKxI2+0s4Grq2Eb0iEm09AufFM8q+Y+/bOQF1c9qjxL6/siSLyaxhl scFzrdfx2M8eCnRcQrhofrfVdwonVnwPYqQ/MhRglf0HBKIJAgMBAAGjggNvMIIDazAOBgNV HQ8BAf8EBAMCAYYwOwYDVR0lBDQwMgYIKwYBBQUHAwEGCCsGAQUFBwMCBggrBgEFBQcDAwYI KwYBBQUHAwQGCCsGAQUFBwMIMIIBxgYDVR0gBIIBvTCCAbkwggG1BgtghkgBhv1sAQMABDCC AaQwOgYIKwYBBQUHAgEWLmh0dHA6Ly93d3cuZGlnaWNlcnQuY29tL3NzbC1jcHMtcmVwb3Np dG9yeS5odG0wggFkBggrBgEFBQcCAjCCAVYeggFSAEEAbgB5ACAAdQBzAGUAIABvAGYAIAB0 AGgAaQBzACAAQwBlAHIAdABpAGYAaQBjAGEAdABlACAAYwBvAG4AcwB0AGkAdAB1AHQAZQBz ACAAYQBjAGMAZQBwAHQAYQBuAGMAZQAgAG8AZgAgAHQAaABlACAARABpAGcAaQBDAGUAcgB0 ACAAQwBQAC8AQwBQAFMAIABhAG4AZAAgAHQAaABlACAAUgBlAGwAeQBpAG4AZwAgAFAAYQBy AHQAeQAgAEEAZwByAGUAZQBtAGUAbgB0ACAAdwBoAGkAYwBoACAAbABpAG0AaQB0ACAAbABp AGEAYgBpAGwAaQB0AHkAIABhAG4AZAAgAGEAcgBlACAAaQBuAGMAbwByAHAAbwByAGEAdABl AGQAIABoAGUAcgBlAGkAbgAgAGIAeQAgAHIAZQBmAGUAcgBlAG4AYwBlAC4wDwYDVR0TAQH/ BAUwAwEB/zB9BggrBgEFBQcBAQRxMG8wJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLmRpZ2lj ZXJ0LmNvbTBHBggrBgEFBQcwAoY7aHR0cDovL3d3dy5kaWdpY2VydC5jb20vQ0FDZXJ0cy9E aWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcnQwgYEGA1UdHwR6MHgwOqA4oDaGNGh0dHA6Ly9j cmwzLmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwOqA4oDaGNGh0 dHA6Ly9jcmw0LmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwHQYD VR0OBBYEFBUAEisTmLKZB+0e36K+Vw0rZwLNMB8GA1UdIwQYMBaAFEXroq/0ksuCMS1Ri6en IZ3zbcgPMA0GCSqGSIb3DQEBBQUAA4IBAQCEYU5BHrh2BCq1tu+P8lWFuV1W/gqY5uS9ZYp9 QCnT/LFdRf06uCpbM0skXM25tORzrWFddq10M4pm1SOvTB9ybkXZdUC7ojvPjUkvwEGw4imj UThDUJkUrDMGNWKJfXepUgflbCBXtoG6b7yzwpTtdgKA2XzOhagc7MdDSkuxV89yzt/1JTzL Ik/9n1LRN8sIuzg+4NU+b3kJrVt8MbN3NcPkY/loCpgH50Y4d4TSPpe8CqCorCVPRG6R4dJa r2vvMByNo0RCsxCLI/rX5jV0N6zP66tYH8mII/821AfqNGpH6p2VbJ4pT1Pt4yuVIE4qz5Zg evgsgPCVUs4ploFiMIIDtzCCAp+gAwIBAgIQDOfg5RfYRv6P5WD8G/AwOTANBgkqhkiG9w0B AQUFADBlMQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3 d3cuZGlnaWNlcnQuY29tMSQwIgYDVQQDExtEaWdpQ2VydCBBc3N1cmVkIElEIFJvb3QgQ0Ew HhcNMDYxMTEwMDAwMDAwWhcNMzExMTEwMDAwMDAwWjBlMQswCQYDVQQGEwJVUzEVMBMGA1UE ChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQuY29tMSQwIgYDVQQDExtE aWdpQ2VydCBBc3N1cmVkIElEIFJvb3QgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK AoIBAQCtDhXO5EOAXLGH87dg+XESpa7cJpSIqvTO9SA5KFhgDPiA2qkVlTJhPLWxKISKityf CgyDF3qPkKyK53lTXDGEKvYPmDI2dsze3Tyoou9q+yHyUmHfnyDXH+Kx2f4YZNISW1/5WBg1 vEfNoTb5a3/UsDg+wRvDjDPZ2C8Y/igPs6eD1sNuRMBhNZYW/lmci3Zt1/GiSw0r/wty2p5g 0I6QNcZ4VYcgoc/lbQrISXwxmDNsIumH0DJaoroTghHtORedmTpyoeb6pNnVFzF1roV9Iq4/ AUaG9ih5yLHa5FcXxH4cDrC0kqZWs72yl+2qp/C3xag/lRbQ/6GW6whfGHdPAgMBAAGjYzBh MA4GA1UdDwEB/wQEAwIBhjAPBgNVHRMBAf8EBTADAQH/MB0GA1UdDgQWBBRF66Kv9JLLgjEt UYunpyGd823IDzAfBgNVHSMEGDAWgBRF66Kv9JLLgjEtUYunpyGd823IDzANBgkqhkiG9w0B AQUFAAOCAQEAog683+Lt8ONyc3pklL/3cmbYMuRCdWKuh+vy1dneVrOfzM4UKLkNl2BcEkxY 5NM9g0lFWJc1aRqoR+pWxnmrEthngYTffwk8lOa4JiwgvT2zKIn3X/8i4peEH+ll74fg38Fn SbNd67IJKusm7Xi+fT8r87cmNW1fiQG2SVufAQWbqz0lwcy2f8Lxb4bG+mRo64EtlOtCt/qM Ht1i8b5QZ7dsvfPxH2sMNgcWfzd8qVttevESRmCD1ycEvkvOl77DZypoEd+A5wwzZr8TDRRu 838fYxAe+o0bJW1sj6W3YQGx0qMmoRBxna3iw/nDmVG3KwcIzi7mULKn+gpFL6Lw8jGCAfww ggH4AgEBMHYwYjELMAkGA1UEBhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcGA1UE CxMQd3d3LmRpZ2ljZXJ0LmNvbTEhMB8GA1UEAxMYRGlnaUNlcnQgQXNzdXJlZCBJRCBDQS0x AhAFLoNW3qD4JhFZyohPBtNqMAkGBSsOAwIaBQCgXTAjBgkqhkiG9w0BCQQxFgQUk5AndUSg 4w9UfAUEDWHm37mDUkMwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUx DxcNMTUwOTE4MTg0NjE1WjANBgkqhkiG9w0BAQEFAASCAQAfQ8X7UQ5RZvr9+5psfgs/tsjH 47bz7DdbUygh5sAaw2/KwpTrAttL0vVp0Xv1Iz8lMqIfLo/ClFNMnUePJs9VJWUQONwvds1N 7RkC3cf+N72MFcSrmDe9PpXV/9oSdu7rGtt5gn9HKIq549H20Ie1M5SJ2Lq5XQGjAyQzvD9E 2USG69GhYhVD6YKfKwOX1Y8v6XCiGiOgXss/giR4uR18mrl5DD8WrEBy+XQabBWYjOCNh4i7 isMHY6lcLx67lG+9EaCXGAbTaOVT15z/IrPECb8t2DL2/Q1qnirgnwMhS4cZVPAqyKoB4C6B QOEYlgo7d9oRyz8rs4LxrIsY8YA3 --B_3525421575_31569040-- From nobody Fri Sep 18 11:50:41 2015 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BB5F1B2C1E for ; Fri, 18 Sep 2015 11:50:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.978 X-Spam-Level: X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] 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 xNFsqMs9tbAC for ; Fri, 18 Sep 2015 11:50:38 -0700 (PDT) Received: from mail-yk0-f180.google.com (mail-yk0-f180.google.com [209.85.160.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 866811B2C15 for ; Fri, 18 Sep 2015 11:50:38 -0700 (PDT) Received: by ykdg206 with SMTP id g206so54867566ykd.1 for ; Fri, 18 Sep 2015 11:50:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=ptVvQyPSADA1enI08TIrSk9c72x1VV2/pzmgmUAa1S4=; b=RlaBIvohwHOvpnUAvoBHqkaU66n8Z3KDs3aWd8QVu4O/q+MEGnPSntLgCHfil1HxkM PUDWylAuU+uIRuO63E989D13hJ6AuHimYJc2zri9DetBnd+/LF9k9lmqA0Cmnf0EKTpL RiBPZ1oXu6Shg5tynluXxI2CIzOqt/pduj2/fkM/g9gP2Q3eOHWgNxYjBns5nVkegWUI iG4RJJ4p/qPcAZbu3n6H2RJMT8LOE2f99wCvcEnmlMGKmEYQbEhH1JY5OwjRuvrxHtec W8eIEH0Amwh/IzuewoHgSiH9uuFJ9lo4zeiwj+4M8/i0nZfPdpK+A4zJ4I1K9IDoEPIZ Tk9g== X-Gm-Message-State: ALoCoQn6CLyzeJ1z7dMb7taTrmftl/J+XdUPh4FKBmoHeulNRQXUIzjvFb2iE/O1X9ewCHCMPaJB MIME-Version: 1.0 X-Received: by 10.13.198.71 with SMTP id i68mr5598263ywd.149.1442602237728; Fri, 18 Sep 2015 11:50:37 -0700 (PDT) Received: by 10.37.52.135 with HTTP; Fri, 18 Sep 2015 11:50:37 -0700 (PDT) In-Reply-To: References: <20150918140756.GG28574@pfrc.org> Date: Fri, 18 Sep 2015 14:50:37 -0400 Message-ID: Subject: Re: Contact person for Early Allocation? From: Warren Kumari To: Michelle Cotton Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: WG Chairs X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 18:50:40 -0000 On Fri, Sep 18, 2015 at 2:46 PM, Michelle Cotton wrote: > Hello, > > If ultimately the reference will be an RFC, you can use IETF Chair/IESG. > There are many examples of this currently in registries. I thought that that was more appropriate for *after* the document was approved / after the Early Allocation. I think we have already sent in the request.... W > > Best regards, > > Michelle > > **** > > Michelle Cotton > Protocol Parameters Engagement Manager > ICANN > > > On 9/18/15, 7:42 AM, "iesg on behalf of Warren Kumari" > wrote: > >>On Fri, Sep 18, 2015 at 10:07 AM, Jeffrey Haas wrote: >>> Warren, >>> >>> On Thu, Sep 17, 2015 at 01:00:38PM -0400, Warren Kumari wrote: >>>> So, I *think* that the correct thing here is for the chair who is >>>> requesting this to be listed as the Assignee and the document author >>>> to be the Contact? >>>> Or should the WG be the Assignee? Or the IETF? >>> >>> My recommendation is to use the -chairs alias for the following >>>reasons: >>> - It is hopefully a long-lived address. >>> - Those addresses are heavily harvested and will receive a bunch of >>>spam. >>> :-( >>> - The entry is unlikely to be orphaned quite as much. >>> >>> See for example [BFD_Chairs] in the service-names-port-numbers registry. >> >> >>Huh, thanks, that sounds clean. I think I'll do that... >> >>W >> >>> >>> The port # assignments especially are full of nonsense or stale >>>addresses. >>> I once looked into getting a former boss off of his assignment from 10+ >>> years ago, and since his email was no longer active there it seemed to >>>be >>> more pain than it was worth. >>> >>> -- Jeff >> >> >> >>-- >>I don't think the execution is relevant when it was obviously a bad >>idea in the first place. >>This is like putting rabid weasels in your pants, and later expressing >>regret at having chosen those particular rabid weasels and that pair >>of pants. >> ---maf >> -- I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf From nobody Fri Sep 18 11:52:46 2015 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEB651B3007 for ; Fri, 18 Sep 2015 11:52:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.431 X-Spam-Level: X-Spam-Status: No, score=-3.431 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_NEUTRAL=0.779, T_RP_MATCHES_RCVD=-0.01] 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 0c7DO8lVaNTN for ; Fri, 18 Sep 2015 11:52:39 -0700 (PDT) Received: from out.west.pexch112.icann.org (pfe112-ca-1.pexch112.icann.org [64.78.40.7]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6729F1B2F20 for ; Fri, 18 Sep 2015 11:52:39 -0700 (PDT) Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Fri, 18 Sep 2015 11:52:37 -0700 Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1044.021; Fri, 18 Sep 2015 11:52:37 -0700 From: Michelle Cotton To: Warren Kumari Subject: Re: Contact person for Early Allocation? Thread-Topic: Contact person for Early Allocation? Thread-Index: AQHQ8WpyxSrfLCLSnUONOJiyX4Rkd55CyVkAgAAJuoD//86wgIAAdpGA//+LNIA= Date: Fri, 18 Sep 2015 18:52:36 +0000 Message-ID: References: <20150918140756.GG28574@pfrc.org> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.5.4.150722 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [192.0.32.234] Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3525421955_31558926" MIME-Version: 1.0 Archived-At: Cc: WG Chairs X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 18:52:42 -0000 --B_3525421955_31558926 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit As discussed in earlier threads, we can change it when the document is approved. Thanks, Michelle On 9/18/15, 11:50 AM, "Warren Kumari" wrote: >On Fri, Sep 18, 2015 at 2:46 PM, Michelle Cotton > wrote: >> Hello, >> >> If ultimately the reference will be an RFC, you can use IETF Chair/IESG. >> There are many examples of this currently in registries. > >I thought that that was more appropriate for *after* the document was >approved / after the Early Allocation. I think we have already sent in >the request.... > >W > > >> >> Best regards, >> >> Michelle >> >> **** >> >> Michelle Cotton >> Protocol Parameters Engagement Manager >> ICANN >> >> >> On 9/18/15, 7:42 AM, "iesg on behalf of Warren Kumari" >> wrote: >> >>>On Fri, Sep 18, 2015 at 10:07 AM, Jeffrey Haas wrote: >>>> Warren, >>>> >>>> On Thu, Sep 17, 2015 at 01:00:38PM -0400, Warren Kumari wrote: >>>>> So, I *think* that the correct thing here is for the chair who is >>>>> requesting this to be listed as the Assignee and the document author >>>>> to be the Contact? >>>>> Or should the WG be the Assignee? Or the IETF? >>>> >>>> My recommendation is to use the -chairs alias for the following >>>>reasons: >>>> - It is hopefully a long-lived address. >>>> - Those addresses are heavily harvested and will receive a bunch of >>>>spam. >>>> :-( >>>> - The entry is unlikely to be orphaned quite as much. >>>> >>>> See for example [BFD_Chairs] in the service-names-port-numbers >>>>registry. >>> >>> >>>Huh, thanks, that sounds clean. I think I'll do that... >>> >>>W >>> >>>> >>>> The port # assignments especially are full of nonsense or stale >>>>addresses. >>>> I once looked into getting a former boss off of his assignment from >>>>10+ >>>> years ago, and since his email was no longer active there it seemed to >>>>be >>>> more pain than it was worth. >>>> >>>> -- Jeff >>> >>> >>> >>>-- >>>I don't think the execution is relevant when it was obviously a bad >>>idea in the first place. >>>This is like putting rabid weasels in your pants, and later expressing >>>regret at having chosen those particular rabid weasels and that pair >>>of pants. >>> ---maf >>> > > > >-- >I don't think the execution is relevant when it was obviously a bad >idea in the first place. >This is like putting rabid weasels in your pants, and later expressing >regret at having chosen those particular rabid weasels and that pair >of pants. > ---maf --B_3525421955_31558926 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" MIITrwYJKoZIhvcNAQcCoIIToDCCE5wCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC EXswggb2MIIF3qADAgECAhAFLoNW3qD4JhFZyohPBtNqMA0GCSqGSIb3DQEBBQUAMGIxCzAJ BgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2Vy dC5jb20xITAfBgNVBAMTGERpZ2lDZXJ0IEFzc3VyZWQgSUQgQ0EtMTAeFw0xMzAzMjAwMDAw MDBaFw0xNjAzMjAxMjAwMDBaMIGfMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5p YTEUMBIGA1UEBxMLTG9zIEFuZ2VsZXMxPDA6BgNVBAoTM0ludGVybmV0IENvcnBvcmF0aW9u IGZvciBBc3NpZ25lZCBOYW1lcyBhbmQgTnVtYmVyczENMAsGA1UECxMESUFOQTEYMBYGA1UE AxMPTWljaGVsbGUgQ290dG9uMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxWwq bCL/Xkl+g9mKzyjxA8YKyTJgMKkfuNPm2Pi5iWmUGpAHkSCUX/YKf1rninFM8JkzffVgInmx juZQRW7lP2796RU0UAUdEsbfDcE5l4dj8h7omA2HkiwvKgxBwegr8VHjzUxOzSetAio5Y2qA Fs7EY97BX6aulzP+tyKi5+7GSBRq+SguiLYETk4FZo8nmyK8E0210+ozwlUQ0VSfkpWluyc/ wQtRo/vQYoM0DPgVaxkE9r20ReyqaE+mxN2pqKl8qoiNMUAnbJIVUSfZhIxS4yoVKNLsOJzo CYSrD6JgNOmzbEOfrTMWMAhh1RCqp5bcaZ4Zlq2lbrIGHzPgSwIDAQABo4IDaDCCA2QwHwYD VR0jBBgwFoAUFQASKxOYspkH7R7for5XDStnAs0wHQYDVR0OBBYEFFcRyKFrxJAiHzozbxx0 fzjeiYmeMCQGA1UdEQQdMBuBGW1pY2hlbGxlLmNvdHRvbkBpY2Fubi5vcmcwDgYDVR0PAQH/ BAQDAgWgMB0GA1UdJQQWMBQGCCsGAQUFBwMEBggrBgEFBQcDAjB9BgNVHR8EdjB0MDigNqA0 hjJodHRwOi8vY3JsMy5kaWdpY2VydC5jb20vRGlnaUNlcnRBc3N1cmVkSURDQS0xLmNybDA4 oDagNIYyaHR0cDovL2NybDQuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0QXNzdXJlZElEQ0EtMS5j cmwwggHFBgNVHSAEggG8MIIBuDCCAbQGCmCGSAGG/WwEAQIwggGkMDoGCCsGAQUFBwIBFi5o dHRwOi8vd3d3LmRpZ2ljZXJ0LmNvbS9zc2wtY3BzLXJlcG9zaXRvcnkuaHRtMIIBZAYIKwYB BQUHAgIwggFWHoIBUgBBAG4AeQAgAHUAcwBlACAAbwBmACAAdABoAGkAcwAgAEMAZQByAHQA aQBmAGkAYwBhAHQAZQAgAGMAbwBuAHMAdABpAHQAdQB0AGUAcwAgAGEAYwBjAGUAcAB0AGEA bgBjAGUAIABvAGYAIAB0AGgAZQAgAEQAaQBnAGkAQwBlAHIAdAAgAEMAUAAvAEMAUABTACAA YQBuAGQAIAB0AGgAZQAgAFIAZQBsAHkAaQBuAGcAIABQAGEAcgB0AHkAIABBAGcAcgBlAGUA bQBlAG4AdAAgAHcAaABpAGMAaAAgAGwAaQBtAGkAdAAgAGwAaQBhAGIAaQBsAGkAdAB5ACAA YQBuAGQAIABhAHIAZQAgAGkAbgBjAG8AcgBwAG8AcgBhAHQAZQBkACAAaABlAHIAZQBpAG4A IABiAHkAIAByAGUAZgBlAHIAZQBuAGMAZQAuMHcGCCsGAQUFBwEBBGswaTAkBggrBgEFBQcw AYYYaHR0cDovL29jc3AuZGlnaWNlcnQuY29tMEEGCCsGAQUFBzAChjVodHRwOi8vY2FjZXJ0 cy5kaWdpY2VydC5jb20vRGlnaUNlcnRBc3N1cmVkSURDQS0xLmNydDAMBgNVHRMBAf8EAjAA MA0GCSqGSIb3DQEBBQUAA4IBAQAzABp5GDSqoV3ty0YLFXRO8ZlHtgsLOP+5AmAS9P0mDEny uO6xbrWK/Oi+9/UfcnYKYUGkFvukHBFLowWakQngPhHLjEhNl2QYC4dbQWLd9z4gZWBWYVzs EreLwUSbRbE3G1r/lkUK3EYO5xAAWtFcv0I4Ixd3//0zxg0ohWW7fm22ypXr8HIBffpptim+ 6oO6X55ME5789phHZZDQt6haEHyMnAQNW2SL6e8cgSL30lPcpStRCXriyXBdoSI+oW83+9u3 SvhjG9WXw8sso9oWMBWo8BhSTERNzLYbxQMazYHW5L/BUBUICTR6l3W96+rjpPZDZVpd9wgR AG54dZ+mMIIGwjCCBaqgAwIBAgIQCgTfIXRdTSuM6jNyBQBQ6TANBgkqhkiG9w0BAQUFADBl MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGln aWNlcnQuY29tMSQwIgYDVQQDExtEaWdpQ2VydCBBc3N1cmVkIElEIFJvb3QgQ0EwHhcNMDYx MTEwMDAwMDAwWhcNMjExMTEwMDAwMDAwWjBiMQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGln aUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQuY29tMSEwHwYDVQQDExhEaWdpQ2Vy dCBBc3N1cmVkIElEIENBLTEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDogi2Z +crCQpWlgHNAcNKeVlRcqcTSQQaPyTP8TUWRXIGf7Syc+BZZ3561JBXCmLm0d0ncicQK2q/L XmvtrbBxMevPOkAMRk2T7It6NggDqww0/hhJgv7HxzFIgHweog+SDlDJxofrNj/YMMP/pvf7 os1vcyP+rFYFkPAyIRaJxnCI+QWXfaPHQ90C6Ds97bFBo+0/vtuVSMTuHrPyvAwrmdDGXRJC geGDboJzPyZLFJCuWWYKxI2+0s4Grq2Eb0iEm09AufFM8q+Y+/bOQF1c9qjxL6/siSLyaxhl scFzrdfx2M8eCnRcQrhofrfVdwonVnwPYqQ/MhRglf0HBKIJAgMBAAGjggNvMIIDazAOBgNV HQ8BAf8EBAMCAYYwOwYDVR0lBDQwMgYIKwYBBQUHAwEGCCsGAQUFBwMCBggrBgEFBQcDAwYI KwYBBQUHAwQGCCsGAQUFBwMIMIIBxgYDVR0gBIIBvTCCAbkwggG1BgtghkgBhv1sAQMABDCC AaQwOgYIKwYBBQUHAgEWLmh0dHA6Ly93d3cuZGlnaWNlcnQuY29tL3NzbC1jcHMtcmVwb3Np dG9yeS5odG0wggFkBggrBgEFBQcCAjCCAVYeggFSAEEAbgB5ACAAdQBzAGUAIABvAGYAIAB0 AGgAaQBzACAAQwBlAHIAdABpAGYAaQBjAGEAdABlACAAYwBvAG4AcwB0AGkAdAB1AHQAZQBz ACAAYQBjAGMAZQBwAHQAYQBuAGMAZQAgAG8AZgAgAHQAaABlACAARABpAGcAaQBDAGUAcgB0 ACAAQwBQAC8AQwBQAFMAIABhAG4AZAAgAHQAaABlACAAUgBlAGwAeQBpAG4AZwAgAFAAYQBy AHQAeQAgAEEAZwByAGUAZQBtAGUAbgB0ACAAdwBoAGkAYwBoACAAbABpAG0AaQB0ACAAbABp AGEAYgBpAGwAaQB0AHkAIABhAG4AZAAgAGEAcgBlACAAaQBuAGMAbwByAHAAbwByAGEAdABl AGQAIABoAGUAcgBlAGkAbgAgAGIAeQAgAHIAZQBmAGUAcgBlAG4AYwBlAC4wDwYDVR0TAQH/ BAUwAwEB/zB9BggrBgEFBQcBAQRxMG8wJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLmRpZ2lj ZXJ0LmNvbTBHBggrBgEFBQcwAoY7aHR0cDovL3d3dy5kaWdpY2VydC5jb20vQ0FDZXJ0cy9E aWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcnQwgYEGA1UdHwR6MHgwOqA4oDaGNGh0dHA6Ly9j cmwzLmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwOqA4oDaGNGh0 dHA6Ly9jcmw0LmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwHQYD VR0OBBYEFBUAEisTmLKZB+0e36K+Vw0rZwLNMB8GA1UdIwQYMBaAFEXroq/0ksuCMS1Ri6en IZ3zbcgPMA0GCSqGSIb3DQEBBQUAA4IBAQCEYU5BHrh2BCq1tu+P8lWFuV1W/gqY5uS9ZYp9 QCnT/LFdRf06uCpbM0skXM25tORzrWFddq10M4pm1SOvTB9ybkXZdUC7ojvPjUkvwEGw4imj UThDUJkUrDMGNWKJfXepUgflbCBXtoG6b7yzwpTtdgKA2XzOhagc7MdDSkuxV89yzt/1JTzL Ik/9n1LRN8sIuzg+4NU+b3kJrVt8MbN3NcPkY/loCpgH50Y4d4TSPpe8CqCorCVPRG6R4dJa r2vvMByNo0RCsxCLI/rX5jV0N6zP66tYH8mII/821AfqNGpH6p2VbJ4pT1Pt4yuVIE4qz5Zg evgsgPCVUs4ploFiMIIDtzCCAp+gAwIBAgIQDOfg5RfYRv6P5WD8G/AwOTANBgkqhkiG9w0B AQUFADBlMQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3 d3cuZGlnaWNlcnQuY29tMSQwIgYDVQQDExtEaWdpQ2VydCBBc3N1cmVkIElEIFJvb3QgQ0Ew HhcNMDYxMTEwMDAwMDAwWhcNMzExMTEwMDAwMDAwWjBlMQswCQYDVQQGEwJVUzEVMBMGA1UE ChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQuY29tMSQwIgYDVQQDExtE aWdpQ2VydCBBc3N1cmVkIElEIFJvb3QgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK AoIBAQCtDhXO5EOAXLGH87dg+XESpa7cJpSIqvTO9SA5KFhgDPiA2qkVlTJhPLWxKISKityf CgyDF3qPkKyK53lTXDGEKvYPmDI2dsze3Tyoou9q+yHyUmHfnyDXH+Kx2f4YZNISW1/5WBg1 vEfNoTb5a3/UsDg+wRvDjDPZ2C8Y/igPs6eD1sNuRMBhNZYW/lmci3Zt1/GiSw0r/wty2p5g 0I6QNcZ4VYcgoc/lbQrISXwxmDNsIumH0DJaoroTghHtORedmTpyoeb6pNnVFzF1roV9Iq4/ AUaG9ih5yLHa5FcXxH4cDrC0kqZWs72yl+2qp/C3xag/lRbQ/6GW6whfGHdPAgMBAAGjYzBh MA4GA1UdDwEB/wQEAwIBhjAPBgNVHRMBAf8EBTADAQH/MB0GA1UdDgQWBBRF66Kv9JLLgjEt UYunpyGd823IDzAfBgNVHSMEGDAWgBRF66Kv9JLLgjEtUYunpyGd823IDzANBgkqhkiG9w0B AQUFAAOCAQEAog683+Lt8ONyc3pklL/3cmbYMuRCdWKuh+vy1dneVrOfzM4UKLkNl2BcEkxY 5NM9g0lFWJc1aRqoR+pWxnmrEthngYTffwk8lOa4JiwgvT2zKIn3X/8i4peEH+ll74fg38Fn SbNd67IJKusm7Xi+fT8r87cmNW1fiQG2SVufAQWbqz0lwcy2f8Lxb4bG+mRo64EtlOtCt/qM Ht1i8b5QZ7dsvfPxH2sMNgcWfzd8qVttevESRmCD1ycEvkvOl77DZypoEd+A5wwzZr8TDRRu 838fYxAe+o0bJW1sj6W3YQGx0qMmoRBxna3iw/nDmVG3KwcIzi7mULKn+gpFL6Lw8jGCAfww ggH4AgEBMHYwYjELMAkGA1UEBhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcGA1UE CxMQd3d3LmRpZ2ljZXJ0LmNvbTEhMB8GA1UEAxMYRGlnaUNlcnQgQXNzdXJlZCBJRCBDQS0x AhAFLoNW3qD4JhFZyohPBtNqMAkGBSsOAwIaBQCgXTAjBgkqhkiG9w0BCQQxFgQU9t/MQLL+ 1sZ1FcUlUbfvznxpP0QwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUx DxcNMTUwOTE4MTg1MjM1WjANBgkqhkiG9w0BAQEFAASCAQAEYAtsc+imRSNyOLsDNOjc0BFd CxiN9UJrI1vTRutxydvCOKg3bbtJ7eByctxUqVvvGDEykhZuZFTQfxBJmPyl6IZO4i1zVCaR z2MU/49lnkElbDnFTfwAjx82wZOvStaJX79naCWMPxmeh6AdCl039ypFzuO3JYWwBhTXXqep msURCz0WrSU8xfJi4KVtuGui2Z+iH1itq2fZKQ5YkiC8n8pSkipPgSPe+JU9wh9zHeNK9y7h Sq5pnxKEKPT46OYXzhsodWR2rnhfjXavdS/lLO96atbcBZZOM2pZzyjOsB9eTEUuxowiIKiA gBTZm1adnm2T8p83KkV+ukpzcLzR --B_3525421955_31558926-- From nobody Sat Sep 19 13:42:53 2015 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B10BC1A8A5A; Sat, 19 Sep 2015 13:42:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.51 X-Spam-Level: X-Spam-Status: No, score=-0.51 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, T_RP_MATCHES_RCVD=-0.01] 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 fRd7Kq2Shh3d; Sat, 19 Sep 2015 13:42:50 -0700 (PDT) Received: from mail-out4.uio.no (mail-out4.uio.no [IPv6:2001:700:100:10::15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3B9E1A8A55; Sat, 19 Sep 2015 13:42:49 -0700 (PDT) Received: from mail-mx1.uio.no ([129.240.10.29]) by mail-out4.uio.no with esmtp (Exim 4.80.1) (envelope-from ) id 1ZdOy7-0006T7-5I; Sat, 19 Sep 2015 22:42:47 +0200 Received: from scandic735.host.songnetworks.se ([87.54.0.186] helo=[192.168.55.88]) by mail-mx1.uio.no with esmtpsa (TLSv1:AES128-SHA:128) user michawe (Exim 4.80) (envelope-from ) id 1ZdOy6-0001fv-KY; Sat, 19 Sep 2015 22:42:47 +0200 References: <20150918174252.5641.5409.idtracker@ietfa.amsl.com> <59BCFDD7-DB30-4411-8584-D0839EB3C8DF@vpnc.org> Mime-Version: 1.0 (1.0) In-Reply-To: <59BCFDD7-DB30-4411-8584-D0839EB3C8DF@vpnc.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: X-Mailer: iPhone Mail (11D201) From: Michael Welzl Subject: Re: [irsg] REMINDER - IETF 94 Working Group/BOF/IRTF Scheduling Deadline Today Date: Sat, 19 Sep 2015 22:42:44 +0200 To: Paul Hoffman X-UiO-SPF-Received: X-UiO-Ratelimit-Test: rcpts/h 7 msgs/h 2 sum rcpts/h 11 sum msgs/h 3 total rcpts 33305 max rcpts/h 54 ratelimit 0 X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, MIME_QP_LONG_LINE=0.001, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO) X-UiO-Scanned: 7C30725FBEB2C97E001A1FDC9DF163EBB6188A6B X-UiO-SPAM-Test: remote_host: 87.54.0.186 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 2 total 12 max/h 4 blacklist 0 greylist 0 ratelimit 0 Archived-At: Cc: Working Group Chairs , IETF Agenda , "irsg@irtf.org" X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Sep 2015 20:42:51 -0000 ok: iccrg is not meeting this time Sent from my iPhone > On 18. sep. 2015, at 20:27, "Paul Hoffman" wrote: >=20 > As a brief follow-up, do note that if your WG/RG is not meeting, there is a= way to say that affirmatively, and doing so will help others with their pla= nning. >=20 > --Paul Hoffman (who has said that IPsecME is not meeting) >=20 From nobody Sat Sep 19 13:56:48 2015 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F3D01A90FD; Sat, 19 Sep 2015 13:56:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 uMw0deZ2hZ1a; Sat, 19 Sep 2015 13:56:45 -0700 (PDT) Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F22001A90EF; Sat, 19 Sep 2015 13:56:44 -0700 (PDT) Received: by pacfv12 with SMTP id fv12so81806036pac.2; Sat, 19 Sep 2015 13:56:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=fHCOwaDd/9aqzNiP50B/VrVClyJ7KupGoqxuvPkVhTE=; b=JKhVqh3IWbcFxmmxMDTnOJaX9Ppr6XTL9fTMso2Xskw2Z1nEqb3oH3diJgY0n3uJy7 c1pAi6jf96u1VWBhfbAj0Vab/2Lg7aVX9rAzm/V0IizbgI/v4ClXgssAkj5FEUqaJtWb 8mArFIgJGlsHo5ENnChTuR51ISktO/jO9+CZANW+JtOcj/pVbzBLrSVQgWe+C+Vs7bJh LpM9580x7KFPGw3KtL2Npy273KZrw2tapMNKqwv6etqznDj4IHSxEuPuox5y0/zzsA/D pxAJ/s9gtlcwKLT39qf0zTUj11EWV8kjNGw5+hlIRogq0nnQRjIdQbX470e4uY5SWwey 1NNg== X-Received: by 10.68.68.134 with SMTP id w6mr15104223pbt.61.1442696204579; Sat, 19 Sep 2015 13:56:44 -0700 (PDT) Received: from [192.168.1.205] (c-50-174-103-180.hsd1.ca.comcast.net. [50.174.103.180]) by smtp.gmail.com with ESMTPSA id xm9sm16018341pbc.32.2015.09.19.13.56.43 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 19 Sep 2015 13:56:43 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: [irsg] REMINDER - IETF 94 Working Group/BOF/IRTF Scheduling Deadline Today From: Dorothy Gellert In-Reply-To: Date: Sat, 19 Sep 2015 13:56:42 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20150918174252.5641.5409.idtracker@ietfa.amsl.com> <59BCFDD7-DB30-4411-8584-D0839EB3C8DF@vpnc.org> To: Michael Welzl X-Mailer: Apple Mail (2.2104) Archived-At: Cc: Working Group Chairs , IETF Agenda , Paul Hoffman , "irsg@irtf.org" X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Sep 2015 20:56:46 -0000 Greetings, all, The Dice WG is NOT meeting at IETF #94. =20 Best Regards, Dorothy > On Sep 19, 2015, at 1:42 PM, Michael Welzl wrote: >=20 > ok: iccrg is not meeting this time >=20 > Sent from my iPhone >=20 >> On 18. sep. 2015, at 20:27, "Paul Hoffman" = wrote: >>=20 >> As a brief follow-up, do note that if your WG/RG is not meeting, = there is a way to say that affirmatively, and doing so will help others = with their planning. >>=20 >> --Paul Hoffman (who has said that IPsecME is not meeting) >>=20 >=20 From nobody Sat Sep 19 15:37:37 2015 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B52E21B303C for ; Sat, 19 Sep 2015 15:37:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 OdCO049Z1-B6 for ; Sat, 19 Sep 2015 15:37:23 -0700 (PDT) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A74D21B303B for ; Sat, 19 Sep 2015 15:37:22 -0700 (PDT) Received: by wicge5 with SMTP id ge5so72054419wic.0 for ; Sat, 19 Sep 2015 15:37:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=GCI7wTgJC2Y+0/G23M4qFScSD7k8ktyiiIIIeXoJ5ZY=; b=C8HbP4Tacwgc9otcLgGNH0ZPX9Z7xmWUhXa86bvnX0ZUci2jSXIat+MTB11J6ApLfH 4PLbYvE5y1AZqmtc1Jsxb6qa+EpTPkEm1KfI8K7m0yzdmfGAfwWOWn/406RB+Y441y1p CRrFs9rTNUUyaBTfRiIi+ptJjJK2cZNdFT7rOkmvkFHPg5IO58BcspAGi0jaB/uYbygI kPC+SA2Fa6a/GW8jePm4kWHydGR3O7MjOc5P4m8l3b9WSoWbAtoavqEnvK7kgGuijxb4 bq+nGLjQoMYnCVZPKLy5iq84n19aMPVPyXZ9x/3GckzK2vGyRKzD+Q9/DFZCL4ONb3Ig 8pbA== X-Received: by 10.180.105.135 with SMTP id gm7mr5042873wib.18.1442702241103; Sat, 19 Sep 2015 15:37:21 -0700 (PDT) Received: from [192.168.1.12] ([46.120.13.132]) by smtp.gmail.com with ESMTPSA id cx3sm16009935wjc.27.2015.09.19.15.37.19 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 19 Sep 2015 15:37:19 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: [irsg] REMINDER - IETF 94 Working Group/BOF/IRTF Scheduling Deadline Today From: Yoav Nir In-Reply-To: Date: Sun, 20 Sep 2015 01:37:17 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20150918174252.5641.5409.idtracker@ietfa.amsl.com> <59BCFDD7-DB30-4411-8584-D0839EB3C8DF@vpnc.org>

To: Working Group Chairs X-Mailer: Apple Mail (2.2104) Archived-At: Cc: Paul Hoffman , "irsg@irtf.org" X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Sep 2015 22:37:28 -0000 Neither is HTTP-Auth. > On Sep 19, 2015, at 11:56 PM, Dorothy Gellert = wrote: >=20 > Greetings, all, >=20 > The Dice WG is NOT meeting at IETF #94. =20 >=20 > Best Regards, > Dorothy >=20 >=20 >> On Sep 19, 2015, at 1:42 PM, Michael Welzl = wrote: >>=20 >> ok: iccrg is not meeting this time >>=20 >> Sent from my iPhone >>=20 >>> On 18. sep. 2015, at 20:27, "Paul Hoffman" = wrote: >>>=20 >>> As a brief follow-up, do note that if your WG/RG is not meeting, = there is a way to say that affirmatively, and doing so will help others = with their planning. >>>=20 >>> --Paul Hoffman (who has said that IPsecME is not meeting) >>>=20 >>=20 >=20 From nobody Sat Sep 19 18:55:13 2015 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27C0E1B348E for ; Sat, 19 Sep 2015 18:55:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.977 X-Spam-Level: X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 rf3VS_PT-5ZK for ; Sat, 19 Sep 2015 18:55:09 -0700 (PDT) Received: from mail-yk0-f176.google.com (mail-yk0-f176.google.com [209.85.160.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 758921B348D for ; Sat, 19 Sep 2015 18:55:09 -0700 (PDT) Received: by ykdt18 with SMTP id t18so76772449ykd.3 for ; Sat, 19 Sep 2015 18:55:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=23uKcP9QuJKB/erKcCPRQoTCjImp/Gqrdycaig0t4Yg=; b=EUaQdSgYXkY3G9828JN6N1dgnC87qr0Yvmaje62AKFQ0BOwUHB/8WhQN0MBv6mAx90 ggJ8XYZR1XHyG1CUAGt8P7RCtJSg3QtWgwWxLtoW+rAMVYHo1T2t08MyBchSH+C3haad eGljYPBV1CrxYcBzdARbiVM21g1Rx5x6v3WSXZIrKM1toTg5M58CzhlBzZsozihxnfdH WG0rhjh5llS3lCsL5DzR6Gu/O9Xd4sSvvurtMqKtc5Xd0lTPOUZhjYWFO0QvY/MK64zf 4fEODJnBok1W77YfLuxN445Uj52xWVkURN3ZlPLjZIFsaUgmc6aGySL8ZdcK8XB8XvfE gEJA== X-Gm-Message-State: ALoCoQlR+BeeeZXZQNMc1VOHNwRH+cuOjL7TrlqMuyEWcdDVWs6JwBkIk9iDvqA8eijZAtKUxnoO MIME-Version: 1.0 X-Received: by 10.170.44.19 with SMTP id 19mr11007406ykm.4.1442714108439; Sat, 19 Sep 2015 18:55:08 -0700 (PDT) Received: by 10.37.52.135 with HTTP; Sat, 19 Sep 2015 18:55:08 -0700 (PDT) In-Reply-To: References: <20150918174252.5641.5409.idtracker@ietfa.amsl.com> <59BCFDD7-DB30-4411-8584-D0839EB3C8DF@vpnc.org>