[dhcwg] No DHC WG meeting @ IETF-103 (Bangkok)

"Bernie Volz (volz)" <volz@cisco.com> Mon, 24 September 2018 14:21 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 61834130DFC; Mon, 24 Sep 2018 07:21:57 -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_DKIMWL_WL_HIGH=-0.01, 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 elRDEMyz4AMw; Mon, 24 Sep 2018 07:21:55 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 330F3130DE6; Mon, 24 Sep 2018 07:21:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14110; q=dns/txt; s=iport; t=1537798915; x=1539008515; h=from:to:cc:subject:date:message-id:mime-version; bh=l/PMvYdEyT0GR70xdc7oyDF/cFTSRsG+aGZdDAeasto=; b=LlWpu8P7+aQKKH+HOwOxglRa8qEVQODcxJSWwcG6QZZ2WJfGVLIoYXRU +r3LfAXC1WMyG3aCGIbx+qSYcxiKRY07/GkuvfmKG+u91hmdLYxJqG5uP sjz4ul6FRZ2Hnbq2expqtCDFcBXqCT2riDNAuPXxm+dlEYAbQMMxr+NXM A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A8AAC08ahb/5hdJa1aHAEBAQQBAQcEAQGBUYEXd2V/Mot/jCiTIIU8gXoLJ4RFg1shNBgBAwEBAgEBAm0cAQuFXBBMEgGBACYBBA4NgxqBHWQPo1CEKwEHB4VGBYp4F4IAgRKEU4E2JAIDAYc1Aog2BoUuU3iNSgkChkGJXh+PLIJRiSmIaAIRFIElHTiBVXAVgyiLFYU+jQmBHgEB
X-IronPort-AV: E=Sophos;i="5.54,298,1534809600"; d="scan'208,217";a="175340820"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Sep 2018 14:21:54 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by rcdn-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id w8OELskZ007219 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 24 Sep 2018 14:21:54 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.1395.4; Mon, 24 Sep 2018 09:21:53 -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.1395.000; Mon, 24 Sep 2018 09:21:53 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
CC: "dhc-ads@ietf.org" <dhc-ads@ietf.org>
Thread-Topic: No DHC WG meeting @ IETF-103 (Bangkok)
Thread-Index: AdRUDrzWdMj1mxazQ3qZn8VHVMpoAA==
Date: Mon, 24 Sep 2018 14:21:53 +0000
Message-ID: <56d4ed8792cb40b1b4310a6612aae9ce@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.195]
Content-Type: multipart/alternative; boundary="_000_56d4ed8792cb40b1b4310a6612aae9ceXCHALN003ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.37.102.15, xch-rcd-005.cisco.com
X-Outbound-Node: rcdn-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/dcvJ68nI3ZNBrd1mgR1mInImA4s>
Subject: [dhcwg] No DHC WG meeting @ IETF-103 (Bangkok)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
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, 24 Sep 2018 14:21:58 -0000

Hi:

Due to receiving only a single agenda request for the DHC WG @ IETF-103, Tomek and I have decided that we will not meet in Bangkok for IETF-103.

The one session request was by Lin He for draft-ren-dhc-problem-statement-of-mredhcpv6 (now expired Related Internet Draft). I sent some comments about this draft to the authors (and WG) and it has not been republished. This would most likely just be an information document if the WG ever decided to adopt it.

The status of the active WG documents is as follows:


1.       Softwire Provisioning using DHCPv4 Over DHCPv6 (draft-ietf-dhc-dhcp4o6-saddr-opt-04<https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcp4o6-saddr-opt/>) is progressing and on the IESG telechat (2018-10-11). There were some useful comments received during the directorate reviews and an updated version is needed (ideally before the telechat).

2.       YANG Data Model for DHCPv6 Configuration (draft-ietf-dhc-dhcpv6-yang-07<https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-yang/>) has recently been updated.

3.       Dynamic Host Configuration Protocol for IPv6 (DHCPv6) bis (draft-ietf-dhc-rfc3315bis-13<https://datatracker.ietf.org/doc/draft-ietf-dhc-rfc3315bis/>) is in AUTH48 and is awaiting final approval from several authors. It will hopefully be published soon.

There are 2 Related Internet Drafts:

1.       Link-Layer Addresses Assignment Mechanism for DHCPv6  (draft-bvtm-dhc-mac-assign-01) should shortly be updated with Carlos Jesús Bernardos Cano as an added author. This was presented at IETF-101<https://datatracker.ietf.org/meeting/101/materials/slides-101-dhc-mac-addresses-assignment-for-dhcpv6-01> and likely the authors will request a call for adoption sometime later this year/early next.

2.       DHCPv6 Options for private DNS Discovery (draft-pusateri-dhc-dns-driu-00). I have no additional information on this document.

For now, the WG will continue to advance the 3 active WG documents and, after a suitable period after the publication of the RFC331bis RFC, work to advance DHCPv6 to Internet Standard. (See the WG charter for full details.)

The chairs do intend to request a DHC WG session at IETF-104 (Prague) as we should meet occasionally, if much less frequently.


-          Bernie and Tomek