Re: [dhcwg] Reminder - Call for Agenda Items for IETF-88 (Vancouver)

"Bernie Volz (volz)" <volz@cisco.com> Wed, 16 October 2013 14:38 UTC

Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6594011E82EC for <dhcwg@ietfa.amsl.com>; Wed, 16 Oct 2013 07:38:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XtSkDqrxeK4D for <dhcwg@ietfa.amsl.com>; Wed, 16 Oct 2013 07:38:34 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 052A011E82F4 for <dhcwg@ietf.org>; Wed, 16 Oct 2013 07:37:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=66111; q=dns/txt; s=iport; t=1381934271; x=1383143871; h=from:to:subject:date:message-id:mime-version; bh=qg23StrV0JWdz4BeN8J6/gkC6dfCxP2z37HfrWNGdLs=; b=N2Eg8AZBN7rrCm+pXAnms0b16rp/ChleEYCC4R1QSudR6FmZc9gy6Pix 6AKJUttUhmd7iPyoBkSIUqcED+95LJxBhUOvB8ZkxStnCkDWNT+0NKyck hsmhY7y/NW5IMtDZ0V52XnDouEqz8FBPDuGqttJAgYZkb8owsIpTELVCe 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlkHABykXlKtJV2Y/2dsb2JhbABagkNEOFK5RIhLgR0WbQeCJQEBAQQdEEEdAQgRBAEBCxYBBigRFAkJAQQTCAESh1kDDwydOpdeDYlrjGOBJQuBDQ8eCgeDGYEGA4VQjleBdIMYix2FNoMkgWgIFyI
X-IronPort-AV: E=Sophos; i="4.93,508,1378857600"; d="scan'208,217"; a="269799460"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-9.cisco.com with ESMTP; 16 Oct 2013 14:37:45 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r9GEbjXN015487 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Wed, 16 Oct 2013 14:37:45 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.27]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.02.0318.004; Wed, 16 Oct 2013 09:37:44 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Reminder - Call for Agenda Items for IETF-88 (Vancouver)
Thread-Index: Ac7KfMJe1YUp8FMwSq+GYgQfVvVphQ==
Date: Wed, 16 Oct 2013 14:37:44 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1AD1E4B5@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.86.255.77]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1AD1E4B5xmbrcdx04ciscoc_"
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 16 Oct 2013 07:41:25 -0700
Subject: Re: [dhcwg] Reminder - Call for Agenda Items for IETF-88 (Vancouver)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 16 Oct 2013 14:38:42 -0000

Hi:

Just a reminder to submit agenda items (see earlier email below for details on what you need to provide).

>From the requests so far received and assuming we accept them all and stick to the requested times (which past history has shown rarely happens), we would use up 100 of out 150 minutes. I suspect we have a pretty full agenda as it stands now.

Tomek and I plan to review the requests this coming Monday (Oct 21st) at 11 AM EDT. Requests received after this time will only be accommodated on a time-available basis.

The requests so far (in pretty much the order in which they were received and NOT in the order they may appear on the agenda) are below. This also includes the details in the request (not yet cleaned up for the agenda). If you requested time, please check it is in the list below.

The chairs (and AD) reserve the right to add "high priority" items they deem important to assure forward progress by the WG.


-          Tomek & Bernie

WG Status and Administration - 10 minutes
Requested by: co-chairs
RFC-3315bis Design Team formation - 20 minutes
Requested by: Tomek
I'd like to request a 20 minutes slot for RFC3315bis work. There's no draft yet. I will be the presenter. This time is needed, because 3315bis is in the charter and advancement of the DHCPv6 protocol is one of primary goals of this WG.
This will be more or less a follow-up discussion to the discussion that will happen soon on the mailing list (will send out an initial proposal in couple days). I'd like to discuss the following issues:
*         clarify the goal of the 3315bis work
*         scope of work:
o    coming up with a list of RFCs and drafts that we want to merge
o    coming up with a proposed list of changes + justifications why they are necessary
*         call for volunteers
*         work organisation (a "design" or "editors" team? where to store intermediate draft revisions?)
Route Problem at Relay during DHCPv6 Prefix Delegation - 10 minutes
Requested by: Alexandru Petrescu alexandru.petrescu@gmail.com<mailto:alexandru.petrescu@gmail.com>
*         Title: "Route Problem at Relay during DHCPv6 Prefix Delegation"
*         Authors: under discussion, committed M. Boucadair, L. Yeh and A. Petrescu.
*         Time needed: 5-10 min.
*         Why time needed: because several diverging opinions were expressed with respect to the problem form, and to the kind of solution (draft-stenberg, snoop-or-not, routing protoocol). We already discussed publicly, but in private people seem to diverge.
DHCP access network identifier - 10 minutes
Requested by: Shwetha Bhandari shwethab@cisco.com<mailto:shwethab@cisco.com>
We need 5 mins slot to present the revision we are planning on draft-ietf-dhc-access-network-identifier-00.txt and request for feed back.
*         Draft name or topic - DHCP access network identifier
*         Who will present - Shwetha Bhandari
*         How much time is needed - 5 mins
*         Why is time needed (tell us why you can't get what you need by posting on the mailing list) and what will be covered - We will start the discussion on -01 on the mailer. If there is sufficient feedback received over the mailer to progress the draft then this slot can be dropped. IF the mailer is quiet then as it is a wg draft we may want to poll the audience during the meeting to help review this.
We are revising the draft to address offline review comments received for a specific suboption/option to disambiguate it. We will also send the details of change -01 to the wg as soon as we submit the same tentatively end of this week.
Secure DHCPv6 - 10 minutes
Requested by: Sheng Jiang jiangsheng@huawei.com<mailto:jiangsheng@huawei.com>
Yes, I would like to present this in the Vancouver. 10 minutes for presentation should be fine.
Stateless Reconfiguration - 15 minutes
Requested by: Sheng Jiang jiangsheng@huawei.com<mailto:jiangsheng@huawei.com>
I'd like to request a 15 minutes slot for reconfiguration in stateless DHCPv6 work, as URI below. I will be the presenter. This time is needed, because this is an un-support issue in current stateless DHCPv6. It is definitely in the scope of DHC WG.
http://www.ietf.org/internet-drafts/draft-jiang-dhc-stateless-reconfiguration-00.txt
The authors would like to get reviews by the WG, particularly on whether this problem are valid. We are also open for discussion regarding to solution design. Several design questions are listed in the document for WG to decide.
Handling Unknown DHCPv6 Messages - 10 minutes
Requested by: Qi Sun sunqi.csnet.thu@gmail.com<mailto:sunqi.csnet.thu@gmail.com>
*         Name: Handling Unknown DHCPv6 Messages
*         Presenter: Qi Sun
*         Time: 5 min
*         Why: This draft describes how a DHCPv6 node handles messages with unkonwn types, which RFC3315 isn't specific about. This document is on the milestone.
*         What will be covered: Updates on the definition of the 'valid message', and the text causing debates.
Address Registration - 10 minutes
Requested by: Sheng Jiang jiangsheng@huawei.com<mailto:jiangsheng@huawei.com>
We'd like to request a 10 minutes slot for address registration work, as URI below. Suresh will be the presenter for now. This time is needed, because this is a chartered item and the draft has made magnificent changes from previous version.
http://tools.ietf.org/html/draft-ietf-dhc-addr-registration
The authors would like to call comments and reviewers for the current version.


From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Sunday, October 06, 2013 3:25 PM
To: dhcwg@ietf.org
Subject: [dhcwg] Call for Agenda Items for IETF-88 (Vancouver)
Importance: High

Hi:

The Vancouver IETF is not that far off (Nov 3-8). See http://www.ietf.org/meeting/88/index.html for more details, including venue information and important dates.

The preliminary agenda has the DHC WG is scheduled for TUESDAY, November 5 from 0900-1130 PST.

Please also note:

  *   2013-10-07 (Monday): Working Group Chair approval for initial document (Version -00) submissions appreciated by UTC 24:00.
  *   2013-10-11 (Friday): Final agenda to be published.
  *   2013-10-21 (Monday): Internet Draft submission cut-off (for all drafts, including -00) by UTC 24:00, upload using IETF ID Submission Tool<https://datatracker.ietf.org/submit/>.
We are starting the call for agenda items. The co-chairs will finalize the agenda about two weeks before the meeting and will give priority to items as follows (in this order):


1.       WG documents with active working group discussion or that are deemed critical (i.e., have upcoming milestones)

2.       WG documents with little or no discussion (provided there is a strong reason for the discussion ... i.e., a higher bandwidth discussion is needed)

3.       Non WG documents with active working group discussion

4.       Non WG documents with little or no discussion

We will limit the number of presentations to reduce the chance that we don't get to them all.

Please be sure to focus your presentations on issues that need discussion or input (new work can include an overview, but the focus should be on issues needing resolution). Status updates can be sent to the mailing list.

If you would like time, please indicate:

-          Draft name or topic

-          Who will present

-          How much time is needed

-          Why is time needed (tell us why you can't get what you need by posting on the mailing list) and what will be covered

Thanks.


-          Tomek & Bernie