Re: [dhcwg] WG Session @ IETF-95 (Buenos Aires) Agenda Requests - Deadline 2/14/2016

"Bernie Volz (volz)" <volz@cisco.com> Wed, 13 January 2016 17:18 UTC

Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDC821B2B40 for <dhcwg@ietfa.amsl.com>; Wed, 13 Jan 2016 09:18:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, 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 0LanbGvEKFA8 for <dhcwg@ietfa.amsl.com>; Wed, 13 Jan 2016 09:18:47 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA9A71B2B3E for <dhcwg@ietf.org>; Wed, 13 Jan 2016 09:18:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18760; q=dns/txt; s=iport; t=1452705526; x=1453915126; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=PEH7edfncO3f3SLXN4ODM/f/LchnuB2LeuB47VFnJSA=; b=W/jer80VPoqCrNkSB8ojzcsat1D+wLKUCla2P3vpw2nke4RI1enEwTfP AmTEbFf9ITGVMvLwiZY4K8HbrV18DC+z7Bcot3CuG80nvz15R+EeQbJeB aa2QxDSYtgl0FPHlmcrntH1AiDOS0fgfvRzTm2sQB136CSjXUiNhFMiKe E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AWAgBHhpZW/4MNJK1egm5MUm0GhTaDHrEDghMBDYFkIoQWgVcCgTs4FAEBAQEBAQF/C4Q0AQEBBC1cAgEIEQQBASEHBzIUCQgBAQQTCIgmDsBRAQEBAQEBAQEBAQEBAQEBAQEBAQEBGItVhQ2EMAWHb4cGiCABhUKIEIFlSoN6iF6FaIhtAREPAQFCgWAxHIFdcgGFE4EIAQEB
X-IronPort-AV: E=Sophos; i="5.22,290,1449532800"; d="scan'208,217"; a="66573368"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 13 Jan 2016 17:18:45 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u0DHIjew009728 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <dhcwg@ietf.org>; Wed, 13 Jan 2016 17:18:45 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 13 Jan 2016 11:18:44 -0600
Received: from xch-aln-003.cisco.com ([173.36.7.13]) by XCH-ALN-003.cisco.com ([173.36.7.13]) with mapi id 15.00.1104.009; Wed, 13 Jan 2016 11:18:44 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: WG Session @ IETF-95 (Buenos Aires) Agenda Requests - Deadline 2/14/2016
Thread-Index: AdFHORD4y95fMyRVQ56UWvb6lX4DVgG6yemw
Date: Wed, 13 Jan 2016 17:18:44 +0000
Message-ID: <94bd6379777449dd82d513d749bfe746@XCH-ALN-003.cisco.com>
References: <005134edeb9e4550b55a23776afaef15@XCH-ALN-003.cisco.com>
In-Reply-To: <005134edeb9e4550b55a23776afaef15@XCH-ALN-003.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.86.254.87]
Content-Type: multipart/alternative; boundary="_000_94bd6379777449dd82d513d749bfe746XCHALN003ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/pzSjyJ7R7pGPCJcsDluENrl7Cdo>
Subject: Re: [dhcwg] WG Session @ IETF-95 (Buenos Aires) Agenda Requests - Deadline 2/14/2016
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2016 17:18:53 -0000

The DHCPv6 bis team requests some time to discuss open issues (still TBD, see http://trac.tools.ietf.org/group/dhcpv6bis/report/1 for current list).

Title Of Session: DHCPv6 bis update and issues
Presenter: TBD (Tomek, Bernie, or others from the bis team)
Related Drafts: draft-ietf-dhc-rfc3315bis
Time Required: 20 minutes (this is a guess at this time)
Purpose of Session: Provide a quick update as to status of draft and discuss open issues that need WG input

We do expect to publish at least one, if not two, updates to the draft-ietf-dhc-rfc3315bis document before the WG meeting.


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Monday, January 04, 2016 4:45 PM
To: dhcwg@ietf.org
Subject: [dhcwg] WG Session @ IETF-95 (Buenos Aires) Agenda Requests - Deadline 2/14/2016
Importance: High

Hi:

The scheduling requests for meeting slots for IETF-95 in Buenos Aires have opened up (we must submit a request before 2/19/2016).

Our plan for IETF-95 will be the same as we did for IETF-94:

-                      We are encouraging agenda requests NOW thru February 14th, 2016 (this will give us a few days to organize the agenda and decide on the session length request).

-                      We will submit our time request for IETF-95 based on the RECEIVED agenda requests (by the February 14th deadline).

-                      Requests after February 14th will most likely be REJECTED (once the time slot is filled). In the past we have been more accommodating, but because of the pressure on IETF meeting time, we are being asked to justify our time slot request. And meeting time should be used to discuss and resolve issues, not present overviews of drafts or status updates.

Therefore, please submit requests as soon as you can (and well before 2/14) if you do plan to present at the DHC WG session in Buenos Aires.

As in the past, please provide:

Title Of Session:
Presenter:
Related Drafts:
Time Required:
Purpose of Session:

We do want to remind those requesting time that you should focus on discussing key issues that need resolution to move a draft forward.

We are 3 months from that next meeting.


-          Tomek & Bernie