Re: [dhcwg] dhc WG last call on draft-ietf-dhc-bcmcv6-option-00.txt

AC Mahendran <mahendra@qualcomm.com> Thu, 10 February 2005 16:43 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15002 for <dhcwg-web-archive@ietf.org>; Thu, 10 Feb 2005 11:43:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzHjL-00083N-5V for dhcwg-web-archive@ietf.org; Thu, 10 Feb 2005 12:03:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CzHEn-000498-D8; Thu, 10 Feb 2005 11:32:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CzH89-00024P-2M for dhcwg@megatron.ietf.org; Thu, 10 Feb 2005 11:25:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13740 for <dhcwg@ietf.org>; Thu, 10 Feb 2005 11:25:22 -0500 (EST)
Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzHSA-0007fc-Qq for dhcwg@ietf.org; Thu, 10 Feb 2005 11:46:08 -0500
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150]) by numenor.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id j1AGOnhP019010 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 10 Feb 2005 08:24:50 -0800 (PST)
Received: from MAHENDRA.qualcomm.com (mahendra.qualcomm.com [129.46.74.166]) by sabrina.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id j1AGOkJr003678; Thu, 10 Feb 2005 08:24:47 -0800 (PST)
Message-Id: <6.1.2.0.2.20050210081942.045e13c0@qcmail1.qualcomm.com>
X-Sender: mahendra@qcmail1.qualcomm.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Thu, 10 Feb 2005 08:24:09 -0800
To: Ralph Droms <rdroms@cisco.com>, dhcwg@ietf.org
From: AC Mahendran <mahendra@qualcomm.com>
Subject: Re: [dhcwg] dhc WG last call on draft-ietf-dhc-bcmcv6-option-00.txt
In-Reply-To: <4.3.2.7.2.20050209155744.02c284a0@flask.cisco.com>
References: <4.3.2.7.2.20050209155744.02c284a0@flask.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-PMX-Version: 4.7.0.111621
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9

I support the progress of both the drafts ( 
draft-ietf-dhc-bcmcv4-option-00.txt & draft-ietf-dhc-bcmcv6-option-00.txt). 
These drafts are very important in the quick deployment of broadcast 
services in 3G wireless environments.

Thanks,
AC

At 12:58 PM 2/9/2005, Ralph Droms wrote:
>This message announces a WG last call on "DHCPv6 Options for Broadcast
>and Multicast Control Servers" <draft-ietf-dhc-bcmcv6-option-00.txt>.
>The last call will conclude at 1700EST on 2005-02-25.
>
>Please respond to this WG last call.  If you support acceptance of the
>document without change, respond with a simple acknowledgment, so that
>support for the document can be assessed.  Lack of discussion does not
>represent positive support.  If there is no expression of support for
>acceptance during the WG last call, the document will not be advanced
>to the IESG.
>
>"DHCPv6 Options for Broadcast and Multicast Control Servers" defines
>new options for Broadcast and Multicast Service controller discovery
>in an IP network.  Broadcast and Multicast service over 3G wireless
>networks are being developed at the time of writing this document.
>Users of this service interact with a controller in the network to
>derive informations that are required to receive broadcast service.
>Dynamic Host Configuration Protocol can be used to configure the
>controller IPv6 addresses in the user's devices.  This document
>defines the related options and option codes.  This draft is available
>as http://www.ietf.org/internet-drafts/draft-ietf-dhc-bcmcv6-option-00.txt
>
>- Ralph Droms
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/dhcwg


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg