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 43E7F1A00B5
 for <dhcwg@ietfa.amsl.com>; Tue, 21 Jul 2015 04:25:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, 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 XiOujbLj7hev for <dhcwg@ietfa.amsl.com>;
 Tue, 21 Jul 2015 04:25:10 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78])
 (using TLSv1 with cipher RC4-SHA (128/128 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id D8C551A004C
 for <dhcwg@ietf.org>; Tue, 21 Jul 2015 04:25:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
 d=cisco.com; i=@cisco.com; l=1164; q=dns/txt; s=iport;
 t=1437477909; x=1438687509;
 h=from:to:cc:subject:date:message-id:references:
 in-reply-to:content-transfer-encoding:mime-version;
 bh=KuXEnJz0P4usNmOdKNW+u8e2+7GNAQ2I4vDVcyRKlpw=;
 b=hXDamcnzAnSBgxyZ3qDbGc6p91i3ph4y6dQHawhXJNB7wAFmjmRalFW5
 Kdal27hYafLvpSRvuiyBvQQ/0bA2bZchR4dMuROIuZ/KDk18Llk119N3F
 IWaFkPryyve/a+aunsFKmL0dMsyVY/RYzObAPSr0oZl10wjzpHxBBlqsI k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D/BACpK65V/5NdJa1cgxNUabwUgWsKhgECgTY6EgEBAQEBAQGBCoQjAQEBAwEBAQE3NAsFCwIBCBAIHhAnCyUCBA4FGogMCA3JegEBAQEBAQEBAQEBAQEBAQEBAQEBARMEi0yEUzMHAoMVgRQFlFMBjCmBQ4Qcky8mg3xvgksBAQE
X-IronPort-AV: E=Sophos;i="5.15,515,1432598400"; d="scan'208";a="11665556"
Received: from rcdn-core-11.cisco.com ([173.37.93.147])
 by rcdn-iport-7.cisco.com with ESMTP; 21 Jul 2015 11:25:09 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89])
 by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id t6LBP90M007299
 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
 Tue, 21 Jul 2015 11:25:09 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.177]) by
 xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0195.001; Tue, 21
 Jul 2015 06:25:08 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
Thread-Topic: [dhcwg] sunset4 & DHCP4o6
Thread-Index: AQHQw6cFqJdubxs2LUiJNRe+1s13tJ3lyH5L
Date: Tue, 21 Jul 2015 11:25:08 +0000
Message-ID: <613E7178-6C25-43F9-B355-0F47D468ABA2@cisco.com>
References: <201507211117.t6LBH4Cr022993@givry.fdupont.fr>
In-Reply-To: <201507211117.t6LBH4Cr022993@givry.fdupont.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/KJRIifl9OYgH6-dsgiNpHePG2YA>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] sunset4 & DHCP4o6
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: Tue, 21 Jul 2015 11:25:11 -0000

In some cases we may have "special" knowledge. But we don't actively collec=
t news of product/opensource annoucements nor do we think that is an IETF /=
 dhc co-chair responsibilty.

You can certainly send out such announcement or request to collect & post t=
his information.

There are cases where we may actively solicit implementation information, s=
uch as when trying to advance standards or document other implementation da=
ta.

- Bernie (from iPad)

> On Jul 21, 2015, at 7:18 AM, Francis Dupont <Francis.Dupont@fdupont.fr> w=
rote:
>=20
> Looking the slides of the "Gap analysis" at the sunset4+v6ops session
> of IETF 93 it seems a good idea to collect and publish an implementation
> summary for DHCP4o6 (i.e., the list of available and planned implementati=
ons
> of DHCP4o6 clients and servers). IMHO a typical job for the DHC WG.
>=20
> Regards
>=20
> Francis.Dupont@fdupont.fr
>=20
> PS: please post the result in the sunset4 mailing list (i.e., where users
> should be :-).
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

