<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi<div><br></div><div>Greetings from the frenzied LA meeting. Being awash in traffic I didn’t notice the bounces in my spam folder or that my messages weren’t in the respective folders, but <a href="mailto:ncuc-ec@lists.ncuc.org">ncuc-ec@lists.ncuc.org</a> and <a href="mailto:ncuc-discuss@lists.ncuc.org">ncuc-discuss@lists.ncuc.org</a> aren’t accepting mail from my subscribed address <a href="mailto:wjdrake@gmail.com">wjdrake@gmail.com</a>. I just looked at the archives for both and see that the last messages delivered by the lists from anyone are from 7 October. So e.g. messages I sent to <a href="mailto:ncuc-ec@lists.ncuc.org">ncuc-ec@lists.ncuc.org</a> on 11 October and to <a href="mailto:ncuc-discuss@lists.ncuc.org">ncuc-discuss@lists.ncuc.org</a> on 8, 12 and 13 October about items like our Constituency Day meeting, NCSG PC representation, CROP funding, etc. didn’t go through, which is a bit of a pressing problem.</div><div><div><br></div><div>Are any of the tech wizards assembled here able to determine what’s going on?</div><div><br></div><div>Thanks,</div><div><br></div><div>Bill </div><div> <br><div><div>Begin forwarded message:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>From: </b></span><span style="font-family:'Helvetica';">Mail Delivery Subsystem <<a href="mailto:mailer-daemon@googlemail.com">mailer-daemon@googlemail.com</a>><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>Subject: </b></span><span style="font-family:'Helvetica';"><b>Delivery Status Notification (Failure)</b><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>Date: </b></span><span style="font-family:'Helvetica';">October 15, 2014 at 9:25:24 AM PDT<br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>To: </b></span><span style="font-family:'Helvetica';"><a href="mailto:wjdrake@gmail.com">wjdrake@gmail.com</a><br></span></div><br><div>Delivery to the following recipient failed permanently:<br><br> <a href="mailto:ncuc-ec@lists.ncuc.org">ncuc-ec@lists.ncuc.org</a><br><br>Technical details of permanent failure: <br>The recipient server did not accept our requests to connect. Learn more at <a href="http://support.google.com/mail/bin/answer.py?answer=7720">http://support.google.com/mail/bin/answer.py?answer=7720</a> <br>[(0) <a href="http://lists.ncuc.org">lists.ncuc.org</a>. [92.243.29.158]:25: Connection refused]<br><br>----- Original message -----<br><br>DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;<br> d=<a href="http://gmail.com">gmail.com</a>; s=20120113;<br> h=subject:mime-version:content-type:from:in-reply-to:date:cc<br> :message-id:references:to;<br> bh=Nn2e561OXYlSbzehR92y13xtsIvfYektR4Xu/Dul2ZA=;<br> b=ab7XtVvisUPWPdhxxvyEu8AZX0zzI8lSYatY44tR4f/wAsFPoRD0lq6OT9OXI8gu+j<br> e1Dt6Yt/aBrBXbTKMy2CCKLxlJCRNBwcSS8FQMuGZ6DpWymnQUZeo3MJ7Xx5x5hI/Diz<br> mdu7z+5UvEzYhcXgHqu766dVmlOkDx8Kf+Yv2r+LmL1GsTuHrHRnKKZkC87hht9sVg9l<br> eUJbcm/cRFftzMFAzeiDvKoSv1NOHqcIgvQPs8JtLtEvTuq4PRBGaKyOCVQWHne6m2/g<br> 86BhQEISAjAQV+3rfC92grabxMlGPam9Dn36Ndgy5ewTcxBHeNxjqmIFw+Wr55JzisrM<br> VyoA==<br>X-Received: by 10.66.66.202 with SMTP id h10mr19312756pat.22.1413143791569;<br> Sun, 12 Oct 2014 12:56:31 -0700 (PDT)<br>Return-Path: <<a href="mailto:wjdrake@gmail.com">wjdrake@gmail.com</a>><br>Received: from [172.20.3.46] ([69.63.220.2])<br> by <a href="http://mx.google.com">mx.google.com</a> with ESMTPSA id uc7sm9211438pbc.10.2014.10.12.12.56.30<br> for <multiple recipients><br> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);<br> Sun, 12 Oct 2014 12:56:31 -0700 (PDT)<br>Subject: Re: CFP: NCUC reps to the NCSG PC<br>Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))<br>Content-Type: multipart/alternative; boundary="Apple-Mail=_D2BE5C34-C9EA-4379-8E03-1621A072363B"<br>From: William Drake <<a href="mailto:wjdrake@gmail.com">wjdrake@gmail.com</a>><br>In-Reply-To: <<a href="mailto:34A26823-EE0F-4DA2-8AC2-F2FCD6E284C1@gmail.com">34A26823-EE0F-4DA2-8AC2-F2FCD6E284C1@gmail.com</a>><br>Date: Sun, 12 Oct 2014 12:57:36 -0700<br>Cc: "Exec. Comm" <<a href="mailto:ncuc-ec@lists.ncuc.org">ncuc-ec@lists.ncuc.org</a>><br>Message-Id: <<a href="mailto:52EC39C6-BD2B-4D31-9154-6DA0CEF88D82@gmail.com">52EC39C6-BD2B-4D31-9154-6DA0CEF88D82@gmail.com</a>><br>References: <<a href="mailto:34A26823-EE0F-4DA2-8AC2-F2FCD6E284C1@gmail.com">34A26823-EE0F-4DA2-8AC2-F2FCD6E284C1@gmail.com</a>><br>To: NCUC-discuss <<a href="mailto:ncuc-discuss@lists.ncuc.org">ncuc-discuss@lists.ncuc.org</a>><br>X-Mailer: Apple Mail (2.1878.6)<br><br>Hi<br><br>We need to appoint two new NCUC reps to the NCSG Policy Committee. These are important positions and a good way to get worked into the process and even prepare to subsequently transition to other leadership positions such as on the Council, as Stephanie and Marilia have done.<br><br>The PC meets later today, and Maria just sent the agenda to the NCSG discuss list. I sent the message below several weeks ago and have not received any expressions of interest, so I guess I will report to the PC that we will now move to a Plan B and try to directly recruit people ASAP. I'll swing back to you with info on the results of that when we have it.<br><br>Best<br><br>Bill<br><br><br>On Sep 20, 2014, at 1:58 AM, William Drake <<a href="mailto:wjdrake@gmail.com">wjdrake@gmail.com</a>> wrote:<br><br><blockquote type="cite">Hello<br><br>Early in the year, after consultation with members, the NCUC PC appointed Stephanie Perrin and Marilia Maciel to serve as our representatives on the NCSG PC. As you will know, both of these successful reps have recently been elected to the GNSO Council, so we will need to replace them. This message is to solicit expressions of interest in filling these roles. It is hoped that we can make a final selection and have new people in place by the Annual Meeting in Los Angeles; the NCSG PC meets on Sunday 12 October.<br><br>These are two of the very most important positions we have in NCUC. According to the NCSG charter, <br><br>----------------------------------------------------------------------------------------------------------------------<br><br>2.5 The Policy Committee<br><br>The NCSG Policy Committee is responsible for:<br><br><span class="Apple-tab-span" style="white-space:pre"> </span>* Discussion and development of substantive policies and statements issued in the name of the NCSG. This activity will require coordination with the membership and the Constituencies;<br><br><span class="Apple-tab-span" style="white-space:pre"> </span>* Organize policy initiatives on behalf of NCSG membership, including PDP initiatives from the membership;<br><br><span class="Apple-tab-span" style="white-space:pre"> </span>* Provide policy research and guidance to NCSG representatives on the GNSO Council;<br><br></blockquote><br>----- Message truncated -----<br><br></div></blockquote></div><br></div></div></body></html>