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

Simon Perreault <simon.perreault@viagenie.ca> Mon, 13 January 2014 15:50 UTC

Return-Path: <simon.perreault@viagenie.ca>
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 D69771AE17D for <sunset4@ietfa.amsl.com>; Mon, 13 Jan 2014 07:50:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level:
X-Spam-Status: No, score=-2.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] 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 Lumn7B3mNRwV for <sunset4@ietfa.amsl.com>; Mon, 13 Jan 2014 07:50:52 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id E3EB21AE134 for <sunset4@ietf.org>; Mon, 13 Jan 2014 07:50:51 -0800 (PST)
Received: from porto.nomis80.org (ringo.viagenie.ca [IPv6:2620:0:230:c000:3e97:eff:fe0b:dd8a]) by jazz.viagenie.ca (Postfix) with ESMTPSA id CA9C2468E9; Mon, 13 Jan 2014 10:50:40 -0500 (EST)
Message-ID: <52D40B50.4040201@viagenie.ca>
Date: Mon, 13 Jan 2014 10:50:40 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "George, Wes" <wesley.george@twcable.com>, "sunset4@ietf.org" <sunset4@ietf.org>
References: <CEF4201E.9F2D%wesley.george@twcable.com>
In-Reply-To: <CEF4201E.9F2D%wesley.george@twcable.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
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: Mon, 13 Jan 2014 15:50:54 -0000

Le 2014-01-09 09:45, George, Wes a écrit :
> 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.

draft-ietf-sunset4-gapanalysis will get a minor update before it expires 
(in two days).

As for draft-ietf-sunset4-noipv4, I don't have anything on my to-do list 
for a new revision. So it would expire in two days unless I submit a 
no-changes update.

IMHO, a good way to get feedback is WGLC.

Right now there would not be much to discuss about those two drafts in 
London.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca