IETF Logo Mail Archive

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

"Bernie Volz (volz)" <volz@cisco.com> Mon, 25 January 2016 19:40 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 CD16F1A005B for <dhcwg@ietfa.amsl.com>; Mon, 25 Jan 2016 11:40:43 -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 bJutlrUjWYKQ for <dhcwg@ietfa.amsl.com>; Mon, 25 Jan 2016 11:40:41 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9771B1A0060 for <dhcwg@ietf.org>; Mon, 25 Jan 2016 11:40:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18343; q=dns/txt; s=iport; t=1453750840; x=1454960440; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=VRfpoQyWu3KY+MYJEEGT0d/XJqyr2SMCUirE6gE6llE=; b=C9joeXxps8XKrjBObcVx41Xh3PuOHbCMKAbePzYu4ZP/xKo9tGt9w8P7 1anXz+4KOieeEtBIKeUYW24laon9enUhGw1IhSyr53KivZ4SZSlzTM94n bNIaKlov1b5h06v46HgOzoQGBITvRC3gr4ixOvJSeih3VkZpoq4Q0meBR M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AEAgBteaZW/4sNJK1egm5MUm0GiFGvf4ITAQ2BY4YPAoFDOBQBAQEBAQEBfwuEQQEBAQQtXAIBCBEEAQEoBzIUCQgBAQQTCIgTvmcBAQEBAQEBAQEBAQEBAQEBAQEBAQEVix+FAYQFBYdghnqIHAGNToFlhESIV4VuiFABHgEBQoIBGIFQaoZAfAEBAQ
X-IronPort-AV: E=Sophos;i="5.22,346,1449532800"; d="scan'208,217";a="231430731"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 25 Jan 2016 19:40:39 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u0PJedst021203 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <dhcwg@ietf.org>; Mon, 25 Jan 2016 19:40:39 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 25 Jan 2016 13:40:38 -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; Mon, 25 Jan 2016 13:40:38 -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: AdFHORD4y95fMyRVQ56UWvb6lX4DVgQbpvJg
Date: Mon, 25 Jan 2016 19:40:38 +0000
Message-ID: <acd163eee61e46d4895e2c3dcdb1d7f4@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.98.1.196]
Content-Type: multipart/alternative; boundary="_000_acd163eee61e46d4895e2c3dcdb1d7f4XCHALN003ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/ytEnG5fZAzdGDD8MSugYlB2CVdM>
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: Mon, 25 Jan 2016 19:40:44 -0000

Just a reminder about requesting agenda slots!

We have only one request:

-          DHCPv6 bis

I would think we MAY want to discuss:

-          Secure DHCPv6 (and draft-li-dhc-secure-dhcpv6-deployment)

-          DHCPv6 Prefix Length Hint Issues (though perhaps we'll just want to try to WGLC this?)

-          Yang model?

-          Failover?

-          Relay Initiated Release (though this would need an update based on the IETF-94 discussions)??


-          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

v2.23.0 | Report a Bug | By Email