Re: [sunset4] Action required: IETF 89 London agenda

"George, Wes" <wesley.george@twcable.com> Wed, 22 January 2014 14:14 UTC

Return-Path: <wesley.george@twcable.com>
X-Original-To: sunset4@ietfa.amsl.com
Delivered-To: sunset4@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6E401A011E for <sunset4@ietfa.amsl.com>; Wed, 22 Jan 2014 06:14:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.911
X-Spam-Level: ****
X-Spam-Status: No, score=4.911 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, SUSPICIOUS_RECIPS=2.51] 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 U4U-C9NbC9R8 for <sunset4@ietfa.amsl.com>; Wed, 22 Jan 2014 06:13:57 -0800 (PST)
Received: from cdcipgw02.twcable.com (cdcipgw02.twcable.com [165.237.91.111]) by ietfa.amsl.com (Postfix) with ESMTP id 503591A00B6 for <sunset4@ietf.org>; Wed, 22 Jan 2014 06:13:57 -0800 (PST)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos; i="4.95,699,1384318800"; d="scan'208,217"; a="58368632"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdcipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 22 Jan 2014 09:13:37 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Wed, 22 Jan 2014 09:13:55 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: "sunset4@ietf.org" <sunset4@ietf.org>
Date: Wed, 22 Jan 2014 09:13:54 -0500
Thread-Topic: [sunset4] Action required: IETF 89 London agenda
Thread-Index: Ac8XfC8mG5y6P9cTRe2u0Lsk8Xfeww==
Message-ID: <CF053A4B.AB52%wesley.george@twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.9.131030
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CF053A4BAB52wesleygeorgetwcablecom_"
MIME-Version: 1.0
Cc: "draft-chen-sunset4-cgn-port-allocation@tools.ietf.org" <draft-chen-sunset4-cgn-port-allocation@tools.ietf.org>, "draft-hazeyama-sunset4-dns-a-filter@tools.ietf.org" <draft-hazeyama-sunset4-dns-a-filter@tools.ietf.org>, "draft-perreault-sunset4-noipv4@tools.ietf.org" <draft-perreault-sunset4-noipv4@tools.ietf.org>, "draft-tsou-behave-natx4-log-reduction@tools.ietf.org" <draft-tsou-behave-natx4-log-reduction@tools.ietf.org>, "draft-ietf-sunset4-gapanalysis@tools.ietf.org" <draft-ietf-sunset4-gapanalysis@tools.ietf.org>, "draft-donley-behave-deterministic-cgn@tools.ietf.org" <draft-donley-behave-deterministic-cgn@tools.ietf.org>
Subject: Re: [sunset4] Action required: IETF 89 London agenda
X-BeenThere: sunset4@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: sunset4 working group discussion list <sunset4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sunset4>, <mailto:sunset4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sunset4/>
List-Post: <mailto:sunset4@ietf.org>
List-Help: <mailto:sunset4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sunset4>, <mailto:sunset4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 14:14:00 -0000

After consulting with the AD, we have requested a 1 hour timeslot.

Draft submission deadline for London is 14 February, slightly more than 3 weeks from now.

It would be extremely helpful for the draft authors to reach out to their colleagues in the IETF and request reviews of their updated drafts on the Sunset4 list, so that we can get some discussion going prior to the meeting. While a meeting can be used as a high bandwidth channel to get work done, we need to be better about using the list in between meetings.

Thanks,

Wes


From: <George>, "George, Wes" <wesley.george@twcable.com<mailto:wesley.george@twcable.com>>
Date: Thursday, January 9, 2014 at 9:45 AM
To: "sunset4@ietf.org<mailto:sunset4@ietf.org>" <sunset4@ietf.org<mailto:sunset4@ietf.org>>
Cc: "draft-chen-sunset4-cgn-port-allocation@tools.ietf.org<mailto:draft-chen-sunset4-cgn-port-allocation@tools.ietf.org>" <draft-chen-sunset4-cgn-port-allocation@tools.ietf.org<mailto:draft-chen-sunset4-cgn-port-allocation@tools.ietf.org>>, "draft-hazeyama-sunset4-dns-a-filter@tools.ietf.org<mailto:draft-hazeyama-sunset4-dns-a-filter@tools.ietf.org>" <draft-hazeyama-sunset4-dns-a-filter@tools.ietf.org<mailto:draft-hazeyama-sunset4-dns-a-filter@tools.ietf.org>>, "draft-perreault-sunset4-noipv4@tools.ietf.org<mailto:draft-perreault-sunset4-noipv4@tools.ietf.org>" <draft-perreault-sunset4-noipv4@tools.ietf.org<mailto:draft-perreault-sunset4-noipv4@tools.ietf.org>>, "draft-tsou-behave-natx4-log-reduction@tools.ietf.org<mailto:draft-tsou-behave-natx4-log-reduction@tools.ietf.org>" <draft-tsou-behave-natx4-log-reduction@tools.ietf.org<mailto:draft-tsou-behave-natx4-log-reduction@tools.ietf.org>>, "draft-ietf-sunset4-gapanalysis@tools.ietf.org<mailto:draft-ietf-sunset4-gapanalysis@tools.ietf.org>" <draft-ietf-sunset4-gapanalysis@tools.ietf.org<mailto:draft-ietf-sunset4-gapanalysis@tools.ietf.org>>, "draft-ietf-sunset4-noipv4@tools.ietf.org<mailto:draft-ietf-sunset4-noipv4@tools.ietf.org>" <draft-ietf-sunset4-noipv4@tools.ietf.org<mailto:draft-ietf-sunset4-noipv4@tools.ietf.org>>, "draft-donley-behave-deterministic-cgn@tools.ietf.org<mailto:draft-donley-behave-deterministic-cgn@tools.ietf.org>" <draft-donley-behave-deterministic-cgn@tools.ietf.org<mailto:draft-donley-behave-deterministic-cgn@tools.ietf.org>>
Subject: [sunset4] Action required: IETF 89 London agenda

Folks, we need to request a meeting timeslot for London by 17th January. Our last meeting was cancelled at the last minute due to a lack of items to discuss, and there has been no updates on any of the drafts and no discussion on-list since IETF88 (and only limited discussion prior to that), so I haven’t been in a hurry to request one for London.

At least one of the WG drafts expires soon, and all of the individual drafts that have *-sunset4-* in their name are expiring. We are still awaiting a revised draft on NAT64 port allocation that integrates the different drafts into one so that it can be discussed, I do not know what the status of the other individual drafts are.

We need to see some activity, and your co-chairs could use some guidance on whether or not we should request a timeslot, and if so, how long? I’m inclined to request an hour so that we have a meeting if we need it, but I don’t want to burn timeslots unnecessarily because scheduling is already enough of a hassle.

So I’m asking that those who wish to participate respond within the next week with potential agenda items and a plan to address the stagnant drafts at least 6 weeks before IETF so that we can restore some forward momentum in this WG and not continue to be active only during face to face meetings.


Thanks,

Wes George

Anything below this line has been added by my company’s mail server, I have no control over it.
-----------

________________________________
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.