Re: [dhcwg] IETF-97 (Seoul) DHC WG Session - Agenda Requests - DEADLINE 9/26

"Bernie Volz (volz)" <volz@cisco.com> Mon, 19 September 2016 23:02 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 CF2C412B01A for <dhcwg@ietfa.amsl.com>; Mon, 19 Sep 2016 16:02:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.836
X-Spam-Level:
X-Spam-Status: No, score=-16.836 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 pRfchkJ3EIfF for <dhcwg@ietfa.amsl.com>; Mon, 19 Sep 2016 16:01:57 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8B0312B5FB for <dhcwg@ietf.org>; Mon, 19 Sep 2016 15:58:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=33378; q=dns/txt; s=iport; t=1474325937; x=1475535537; h=from:to:subject:date:message-id:mime-version; bh=i2dK3WR2HL1ZjDerIyktBTJ6t9RbLygrbD8KfliYWy0=; b=H7vV8ZKEbttP5/ejt188uCAReEQKoIPU8BbIy6adQuQW0EvbNbYMMvpp MqsrE50c+td0P56rWCUsjdihf+0DLym9d2p8oF0hn4gWr13+0V2lnNQ+z lxLWC4iuNyWCtV/dt8yu1Kd4/kQQM5XO0n+YAH9nzN91t87tjJwGIe9VQ A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DdAQBLbeBX/4YNJK1dGgEBAQECAQEBAQgBAQEBgwczAQEBAQEeV3wHjSypMoIPggMkhXoCgVY4FAECAQEBAQEBAV4cC4RhAQEFHRBeAQgRBAEBIQEGORQJCQEEEwiIQg6hMpwhAQEBAQEBAQEBAQEBAQEBAQEBAQEBFwWLC4QuTIIUgxIFiCwBhz+ELoVVAYYliS+BdYRjiRmHAoVig3oBHjaEanKHAwF+AQEB
X-IronPort-AV: E=Sophos;i="5.30,364,1470700800"; d="scan'208,217";a="148619313"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 19 Sep 2016 22:58:56 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id u8JMwuox019032 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <dhcwg@ietf.org>; Mon, 19 Sep 2016 22:58:56 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 19 Sep 2016 17:58:55 -0500
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.1210.000; Mon, 19 Sep 2016 17:58:55 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] IETF-97 (Seoul) DHC WG Session - Agenda Requests - DEADLINE 9/26
Thread-Index: AdISyQPYUBbncotrSfGNQniBCdnzCA==
Date: Mon, 19 Sep 2016 22:58:55 +0000
Message-ID: <58e2cf3a1ff841be99bc0b652302ee7f@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: [161.44.67.124]
Content-Type: multipart/alternative; boundary="_000_58e2cf3a1ff841be99bc0b652302ee7fXCHALN003ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/6wrhRU1JGW9WvVoYcDIp--Piz-M>
Subject: Re: [dhcwg] IETF-97 (Seoul) DHC WG Session - Agenda Requests - DEADLINE 9/26
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
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, 19 Sep 2016 23:02:02 -0000

Hi:

One more week left before we need to determine how much time to request.

Based on what is there now (much is tentative), it is likely we will only request a 1 hour slot.

Also note that the WGLC on draft-ietf-dhc-dhcpv6-failover-protocol-02, DHCPv6 Failover Protocol, ends 9/20 (tomorrow).


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Sunday, September 11, 2016 11:09 AM
To: dhcwg@ietf.org
Subject: [dhcwg] IETF-97 (Seoul) DHC WG Session - Agenda Requests - DEADLINE 9/26
Importance: High

Reminder to submit session agenda requests.

At present, the only session request we have is to potentially review 3315bis WGLC issues (if not resolved prior to the meeting or consensus building needs higher bandwidth discussion). See https://github.com/dhcwg/wg/wiki/IETF-97-(Seoul)-DHC-WG-Agenda.

At present, we'll either have a short (1 hour meeting is shortest available slot) or none at all unless we get some items to add to the agenda.

The current WG drafts in progress are:

draft-ietf-dhc-dhcpv4-forcerenew-extensions-00, Forcerenew Reconfiguration Extensions for DHCPv4
Appears to be stalled as several attempts to reach the authors have failed. Unless someone speaks up that has interest in this work, we plan to let it die. Expires: November 13, 2016 (just before Seoul).

draft-ietf-dhc-dhcpv6-failover-protocol-02, DHCPv6 Failover Protocol
Presently in WGLC (scheduled to end 9/12)

draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-03, DHCPv6 Prefix Length Hint Issues
Presently scheduled to be WGLC after failover-protocol document finished.

draft-ietf-dhc-dhcpv6-yang-03, YANG Data Model for DHCPv6 Configuration
No apparent progress since just before Berlin. Not sure if there are any outstanding issues to discuss? There were some comments raised in Berlin, especially about options. See https://www.ietf.org/proceedings/96/minutes/minutes-96-dhc.

draft-ietf-dhc-rfc3315bis-05, Dynamic Host Configuration Protocol for IPv6 (DHCPv6) bis
WGLC ended. Issues being worked by co-authors. Awaiting WGLC status report from Ralph Droms.

draft-ietf-dhc-sedhcpv6-13, Secure DHCPv6
No apparent progress since just before Berlin. Only comment during Berlin IETF was to update sequence number to 64-bits.

Also, draft-li-dhc-secure-dhcpv6-deployment has expired and I think it needed some work (moving text from sedhcpv6 into this document to keep this one focused on all deployment issues)?

For the Related Internet-Drafts:

draft-liu-dhc-dhcp-yang-model-05, Yang Data Model for DHCP Protocol
WG may consider after DHCPv6 model (almost) complete.

draft-shen-dhc-client-port-03, Generalized Source UDP Port of DHCP Relay
Likely to have adoption call shortly

draft-templin-dhc-authonly-sedhcpv6-02, Authentication-only Mode for Secure DHCPv6
New.

draft-volz-dhc-relay-server-security-02, Security of Messages Exchanged Between Servers and Relay Agents
Adoption call pending issuance by Tomek.


-          Tomek & Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Tuesday, August 16, 2016 2:03 PM
To: dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Subject: [dhcwg] IETF-97 (Seoul) DHC WG Session - Agenda Requests

Hi:

Please submit agenda requests as soon as you can if you do plan to present at the DHC WG session in Seoul (requests must be submitted by September 26; Tomek or I need to submit the session request by September 30th).

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.

You can view the working agenda at https://github.com/dhcwg/wg/wiki/IETF-97-(Seoul)-DHC-WG-Agenda.

While we are still 3 months from that meeting, the session requests have opened up and we need to know approximately how much time to request.

We have the following WG documents active:

-          draft-ietf-dhc-dhcpv4-forcerenew-extensions-00, Forcerenew Reconfiguration Extensions for DHCPv4

No presentation in Berlin or update to DHC WG about status since update published 2016-05-13

-          draft-ietf-dhc-dhcpv6-failover-protocol-02, DHCPv6 Failover Protocol

Expecting to start WGLC 8/22

-          draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-03, DHCPv6 Prefix Length Hint Issues

Likely to start WGLC soon

-          draft-ietf-dhc-dhcpv6-yang-03, YANG Data Model for DHCPv6 Configuration

Also (related draft list), draft-li-dhc-secure-dhcpv6-deployment-03 , secure DHCPv6 deployment

No update since Berlin (last updated 2016-06-18)

-          draft-ietf-dhc-rfc3315bis-05, Dynamic Host Configuration Protocol for IPv6 (DHCPv6) bis

WGLC in progress (ends 8/22)

-          draft-ietf-dhc-sedhcpv6-13 , Secure DHCPv6

Discussed in Berlin, no update yet


And, the following related drafts:

-          draft-shen-dhc-client-port-02, Generalized Source UDP Port of DHCP Relay

Pending call for option?

-          draft-volz-dhc-relay-server-security-01, Security of Messages Exchanged Between Servers and Relay Agents
Minor update pending, then call for adoption.

Thanks!


-          Tomek & Bernie