IETF Logo Mail Archive

Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-02.txt

"Gaurav Halwasia (ghalwasi)" <ghalwasi@cisco.com> Fri, 21 September 2012 11:13 UTC

Return-Path: <ghalwasi@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 6102B21F8508 for <dhcwg@ietfa.amsl.com>; Fri, 21 Sep 2012 04:13:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.179
X-Spam-Level:
X-Spam-Status: No, score=-10.179 tagged_above=-999 required=5 tests=[AWL=0.420, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 vuS3XcTRNjpl for <dhcwg@ietfa.amsl.com>; Fri, 21 Sep 2012 04:12:59 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 9258421F842A for <dhcwg@ietf.org>; Fri, 21 Sep 2012 04:12:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2214; q=dns/txt; s=iport; t=1348225979; x=1349435579; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=D4ejuBh285/UeWLZiBkJfgW+DqxMpEdpCENNXADjvzk=; b=ZjculZ6dESZJz8ps4Ygbn63rArBf7SEM5sKHeArJqEHN3/h+GyWxHr8h Nrr6dxHKu3eHcCkhhgmeYOXalUvdL7dFOyoEglKMiy3443o+gu72lJx9K 7Q+OvWbL+gbEYmk0G99g4VRg7DElSUSt//J6kIOW1uN6iZRbCqmTvyEbZ 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAFdLXFCtJV2d/2dsb2JhbABFvhCBCIIgAQEBBAEBAQ8BJzQXBAIBCBEEAQELFAkHJwsUCQgCBBMIARmHYwuZD6AVixyFRmADlnmNJIFpgmeCFw
X-IronPort-AV: E=Sophos;i="4.80,462,1344211200"; d="scan'208";a="123931018"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-8.cisco.com with ESMTP; 21 Sep 2012 11:12:59 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id q8LBCxRg017158 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Fri, 21 Sep 2012 11:12:59 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.33]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.02.0298.004; Fri, 21 Sep 2012 06:12:58 -0500
From: "Gaurav Halwasia (ghalwasi)" <ghalwasi@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-02.txt
Thread-Index: AQHNl+S9NIcNYjKE+0GFA4wX5IPS9peUoiDQ
Date: Fri, 21 Sep 2012 11:12:57 +0000
Message-ID: <90903C21C73202418A48BFBE80AEE5EB1926050F@xmb-aln-x06.cisco.com>
References: <20120921103403.10090.70019.idtracker@ietfa.amsl.com>
In-Reply-To: <20120921103403.10090.70019.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.142.100.142]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19200.001
x-tm-as-result: No--29.767200-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-02.txt
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: Fri, 21 Sep 2012 11:13:00 -0000

Hi DHC WG Members,

Thanks for your support/comments on this document. We have published a new version after taking care of the review comments from the last WGLC. Following are the main points which are clarified in this document:-

1.) Explicitly mentioned what Relay Agents are going to include in Client Link-layer Address option based upon the text suggested by Ted and other WG members.

2.) Also added some text on the behavior of the DHCPv6 server in case of directly connected clients.

Thanks,
Gaurav
-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
Sent: Friday, September 21, 2012 4:04 PM
To: i-d-announce@ietf.org
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-02.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

	Title           : Client Link-layer Address Option in DHCPv6
	Author(s)       : Gaurav Halwasia
                          Shwetha Bhandari
                          Wojciech Dec
	Filename        : draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-02.txt
	Pages           : 6
	Date            : 2012-09-21

Abstract:
   This document specifies the format and mechanism that is to be used
   for encoding client link-layer address in DHCPv6 relay forward
   messages by defining a new DHCPv6 Client Link-layer Address option.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-02


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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

v2.29.0 | Report a Bug | By Email | System Status