[dhcwg] dhc WG last call on draft-ietf-dhc-l2ra-02
Ralph Droms <rdroms@cisco.com> Tue, 07 October 2008 18:07 UTC
Return-Path: <dhcwg-bounces@ietf.org>
X-Original-To: dhcwg-archive@megatron.ietf.org
Delivered-To: ietfarch-dhcwg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A47543A67F7; Tue, 7 Oct 2008 11:07:35 -0700 (PDT)
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9BB073A6849 for <dhcwg@core3.amsl.com>; Tue, 7 Oct 2008 11:07:34 -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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zy6iYeMWeCP2 for <dhcwg@core3.amsl.com>; Tue, 7 Oct 2008 11:07:33 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 943423A67F3 for <dhcwg@ietf.org>; Tue, 7 Oct 2008 11:07:33 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,373,1220227200"; d="scan'208";a="23542400"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 07 Oct 2008 18:08:12 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m97I8CEm025217; Tue, 7 Oct 2008 14:08:12 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m97I89vl011879; Tue, 7 Oct 2008 18:08:12 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 7 Oct 2008 14:08:09 -0400
Received: from dhcp-161-44-112-80.cisco.com ([161.44.112.80]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 7 Oct 2008 14:08:08 -0400
Message-Id: <8338AA95-6B7B-49D8-BCBF-97F5C117AE78@cisco.com>
From: Ralph Droms <rdroms@cisco.com>
To: DHC WG <dhcwg@ietf.org>
Mime-Version: 1.0 (Apple Message framework v924)
Date: Tue, 07 Oct 2008 14:07:57 -0400
X-Mailer: Apple Mail (2.924)
X-OriginalArrivalTime: 07 Oct 2008 18:08:08.0798 (UTC) FILETIME=[A748B7E0:01C928A7]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1746; t=1223402892; x=1224266892; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rdroms@cisco.com; z=From:=20Ralph=20Droms=20<rdroms@cisco.com> |Subject:=20dhc=20WG=20last=20call=20on=20draft-ietf-dhc-l2 ra-02 |Sender:=20 |To:=20DHC=20WG=20<dhcwg@ietf.org>; bh=yG6frSo4RnQiSO7skJd3+5lSIdYnGtIUYmf/gxNbkVc=; b=kqtX9TKVbYawwKRV3YNrnYuDcXUcQv7ryM0QMJVard4sWj57cRfmYHgEpg JU5os9fO8lJMTM6csLRCOGmi3dPdCDy++V+dJ+h8QS0Mb1B/GuhU0YlDnXBC StEH742ScO;
Authentication-Results: rtp-dkim-1; header.From=rdroms@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
Cc: Dhc Chairs <dhc-chairs@tools.ietf.org>
Subject: [dhcwg] dhc WG last call on draft-ietf-dhc-l2ra-02
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
This message announces a WG last call on "Layer 2 Relay Agent Information" <draft-ietf-dhc-l2ra-02>. The last call will conclude at 1700PDT October 20, 2008. draft-ietf-dhc-l2ra-02 has been revised based on comments received during the previous WG last call on draft-ietf-dhc-l2ra-01 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. Note that there was insufficient response to the previous WG last call to support advancing the document to the IESG. draft-ietf-dhc-l2ra-01 describes the network scenarios where a Layer 2 Relay Agent is in use and how it handles DHCP messages. In some networks, DHCP servers rely on Relay Agent Information option appended by Relay Agents for IP address and other parameter assignment policies. This works fine when end hosts are directly connected to Relay Agents. In some network configurations, one or more Layer 2 devices may reside between DHCP clients and Relay agent. In these network scenarios, it is difficult to use the Relay Agent Information option for IP address and other parameter assignment policies effectively. So there is a need for the device that is closest to the end hosts to append Relay Agent Information option in DHCP messages. These devices are typically known as Layer 2 Relay Agents. This draft is available as http://www.ietf.org/internet-drafts/draft-ietf-dhc-l2ra-02.txt - John Brzozowski, Ralph Droms dhc WG chairs _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg