Re: [dhcwg] IETF-94 (Yokohama) Agenda Requests - DEADLINE 9/10/2015!

"Bernie Volz (volz)" <volz@cisco.com> Sat, 29 August 2015 01:58 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 D3A0B1A879B for <dhcwg@ietfa.amsl.com>; Fri, 28 Aug 2015 18:58:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 W_5Ko1Buxl6r for <dhcwg@ietfa.amsl.com>; Fri, 28 Aug 2015 18:58:17 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 461751B2B21 for <dhcwg@ietf.org>; Fri, 28 Aug 2015 18:58:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=25398; q=dns/txt; s=iport; t=1440813497; x=1442023097; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=PGW5dU1rY3ZSwfI7f9gV+p/84hdVsAPI3GA5j49IYvU=; b=HgTEiiGQ6z3zg2292qAF8v9+R+5GzQHS0yuYvt2HU05B2Mr4stUcLT2j Bh06KsooUOy1eniBBtS4FaqUTYG4u2/rPTJ/xA+PtM+Wa2DXo+LkzztnU XcjOqMAH45LoWQwqrUb+IW55wh5VZ1MDiHikT/iTn+xEZgrjZZkeUhxNO U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DVBACBEOFV/4oNJK1dgk5NVGkGvVQqAQmBeIV7AoEzOBQBAQEBAQEBfwuEIwEBAQQtQRsCAQgRBAEBCxYHBzIUCQgBAQQTCIgmDcUvAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4tihEYULQoBgxiBFAWHL4ZrhyUBhQWJN0aDbIw2hEmDbBEVg39xAYFHgQUBAQE
X-IronPort-AV: E=Sophos; i="5.17,428,1437436800"; d="scan'208,217"; a="24511328"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-5.cisco.com with ESMTP; 29 Aug 2015 01:58:15 +0000
Received: from XCH-ALN-017.cisco.com (xch-aln-017.cisco.com [173.36.7.27]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id t7T1wFJc026024 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <dhcwg@ietf.org>; Sat, 29 Aug 2015 01:58:15 GMT
Received: from xch-aln-017.cisco.com (173.36.7.27) by XCH-ALN-017.cisco.com (173.36.7.27) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 28 Aug 2015 20:58:14 -0500
Received: from xhc-aln-x07.cisco.com (173.36.12.81) by xch-aln-017.cisco.com (173.36.7.27) with Microsoft SMTP Server (TLS) id 15.0.1104.5 via Frontend Transport; Fri, 28 Aug 2015 20:58:14 -0500
Received: from xmb-rcd-x04.cisco.com ([169.254.8.103]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0248.002; Fri, 28 Aug 2015 20:58:14 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: IETF-94 (Yokohama) Agenda Requests - DEADLINE 9/10/2015!
Thread-Index: AdDan6aiodQMmW9ZTeyaDkPju2sV9gHXgtxA
Date: Sat, 29 Aug 2015 01:58:13 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1CC5B659@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CC46783@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1CC46783@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.98.1.198]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1CC5B659xmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/WkumgI3jLdrb1Tis90nQAfgv2EU>
Subject: Re: [dhcwg] IETF-94 (Yokohama) Agenda Requests - DEADLINE 9/10/2015!
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: Sat, 29 Aug 2015 01:58:21 -0000

Hi:

Just a friendly reminder - deadline for agenda time requests is 9/10/2015.

And thanks much to those that have already submitted requests! We probably already have about 90 minutes of time on the agenda; there are a few placeholders items that we'll need to finalize.

You can monitor development of the agenda at https://github.com/dhcwg/wg/wiki/IETF-94-(Yokohama)-DHC-WG-Agenda.


-          Tomek & Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Wednesday, August 19, 2015 12:55 PM
To: dhcwg@ietf.org
Subject: Re: [dhcwg] IETF-94 (Yokohama) Agenda Requests - DEADLINE 9/10/2015!
Importance: High

Hi:

An update on this issue ...

Our plan for IETF-94 is as follows:

-          We are encouraging agenda requests NOW thru September 10th, 2015.

-          We will submit our time request for IETF-94 based on the RECEIVED agenda requests (by the September 18th time request deadline).

-          Requests after September 10th 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.

So, again, please do send in requests for slots now to that we can plan accordingly. (See below for what should be in your request.)


The DRAFT agenda at present looks as follows:

1. Co-Chairs - Administrativia (Agenda Bashing, WG Status, ...) - 5 minutes
2. DHCPv6bis update & issues discussion, dhcpv6bis team - 15 minutes

There was one additional request received (DHCPv4 YANG model, 10 minutes), but we are in discussions on this item as we would prefer to focus on v6 work items (i.e., DHCPv6 YANG model - perhaps once that sees good progress, we can look at whether a DHCPv4 YANG model is appropriate).

Potential areas that received good support recently or have issues outstanding include:

-          DHCPv6 YANG model

-          DHCPv6 Prefix Length hint issues (also http://trac.tools.ietf.org/group/dhcpv6bis/ticket/114)

-          DHCPv6bis issues (ORO handling)

-          DHCPv6 encryption

-          DHCPv6 relay initiated release
We would encourage the authors of these documents to strongly consider agenda requests. Of course, if you have a document update pending, please publish and/or initiate discussion on the WG mailing list if not already started to resolve any open issues.


-          Tomek & Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Tuesday, August 04, 2015 11:08 AM
To: dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Subject: [dhcwg] IETF-94 (Yokohama) Agenda Requests

Hi:

The scheduling requests for meeting slots for IETF-94 in Yokohama have opened up (we must submit a request before 9/18/2015).

While we have not yet received guidance from the Int ADs as to any change in process for scheduling requests, we are assuming that to request long time slot (2 or 2.5 hours) we will need an agenda that indicates we need that time.

Therefore, please submit requests as soon as you can (and well before 9/18) if you do plan to present at the DHC WG session in Yokohama.

As previously, 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.

I understand that  this seems early, but we are under 3 months from that next meeting!


-          Tomek & Bernie