IETF Logo Mail Archive

Re: [dhcwg] Call for adoption: draft-mrugalski-softwire-dhcpv4-over-v6-option-01

Mathias Samuelson <Mathias.Samuelson@nominum.com> Thu, 27 September 2012 02:29 UTC

Return-Path: <Mathias.Samuelson@nominum.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 0AB2B21F8624 for <dhcwg@ietfa.amsl.com>; Wed, 26 Sep 2012 19:29:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4lf6LMX5bkau for <dhcwg@ietfa.amsl.com>; Wed, 26 Sep 2012 19:29:17 -0700 (PDT)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by ietfa.amsl.com (Postfix) with ESMTP id 36A0621F861C for <dhcwg@ietf.org>; Wed, 26 Sep 2012 19:29:17 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob122.postini.com ([64.18.6.12]) with SMTP ID DSNKUGO5/Pxh8DTqcp18Y0B0SV1tvGrwFwDR@postini.com; Wed, 26 Sep 2012 19:29:17 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 4BC111B82B3 for <dhcwg@ietf.org>; Wed, 26 Sep 2012 19:29:16 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 4333A19005C for <dhcwg@ietf.org>; Wed, 26 Sep 2012 19:29:16 -0700 (PDT) (envelope-from Mathias.Samuelson@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0247.003; Wed, 26 Sep 2012 19:29:13 -0700
From: Mathias Samuelson <Mathias.Samuelson@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] Call for adoption: draft-mrugalski-softwire-dhcpv4-over-v6-option-01
Thread-Index: AQHNnAwoksIIq5rbSkG4M+kw2Zj+pZed7QAA
Date: Thu, 27 Sep 2012 02:29:12 +0000
Message-ID: <83AC8034-9D2A-46D8-AAF8-EAD29DD790F7@nominum.com>
References: <EDE04BE3-EF07-4CD2-B8D9-D82A570E8C19@nominum.com>
In-Reply-To: <EDE04BE3-EF07-4CD2-B8D9-D82A570E8C19@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <44DE7D8BAF90E5448109F46336B7D098@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: dhcwg WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Call for adoption: draft-mrugalski-softwire-dhcpv4-over-v6-option-01
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: Thu, 27 Sep 2012 02:29:18 -0000

I've read this draft and support adopting it as WG work.

Mathias

Ps Btw, since this is my first post here I figured I'd introduce myself - I'm in product management at Nominum and is working on DHCP stuff! Hi all!

On Sep 26, 2012, at 10:27 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> The authors have requested that the working group adopt draft-mrugalski-softwire-dhcpv4-over-v6-option as a working group work item.   The document is within the scope of the current charter.   It describes a DHCPv6 option that is used to configure client relay agents (draft-ietf-dhc-dhcpv4-over-ipv6).
> 
> If you think the working group should be working on such an option, please respond to this message by saying so.   If you think we should not, please say that.
> 
> We will evaluate consensus on or after October 10.
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email