[dhcwg] FW: I-D Action: draft-ietf-dhc-l2ra-06.txt

Bharat Joshi <bharat_joshi@infosys.com> Wed, 25 January 2012 14:10 UTC

Return-Path: <bharat_joshi@infosys.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 D6A3021F86D3 for <dhcwg@ietfa.amsl.com>; Wed, 25 Jan 2012 06:10:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level:
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ncpj6LpBOn13 for <dhcwg@ietfa.amsl.com>; Wed, 25 Jan 2012 06:10:30 -0800 (PST)
Received: from KECGATE08.infosys.com (kecgate08.infosys.com [122.98.10.33]) by ietfa.amsl.com (Postfix) with ESMTP id 7B21D21F86BB for <dhcwg@ietf.org>; Wed, 25 Jan 2012 06:10:29 -0800 (PST)
X-TM-IMSS-Message-ID: <48b7f240000d0a16@infosys.com>
Received: from blrkechub01.ad.infosys.com ([10.66.236.41]) by infosys.com ([122.98.10.33]) with ESMTP (TREND IMSS SMTP Service 7.1) id 48b7f240000d0a16 ; Wed, 25 Jan 2012 19:40:18 +0530
Received: from BLRKECMBX02.ad.infosys.com ([10.66.236.25]) by blrkechub01.ad.infosys.com ([10.66.236.41]) with mapi; Wed, 25 Jan 2012 19:40:15 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Date: Wed, 25 Jan 2012 19:39:24 +0530
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-l2ra-06.txt
Thread-Index: Aczbat8Nsk3rirSfQ5+yksdtLhp7lAAABHO2
Message-ID: <31D55C4D55BEED48A4459EB64567589A118C41DA05@BLRKECMBX02.ad.infosys.com>
References: <20120125140844.31841.10158.idtracker@ietfa.amsl.com>
In-Reply-To: <20120125140844.31841.10158.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [dhcwg] FW: I-D Action: draft-ietf-dhc-l2ra-06.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: Wed, 25 Jan 2012 14:10:31 -0000

This draft has expired and so I just submitted a new revision. There is no new changes from the last revision.

If you have not reviewed it yet, please review the same and let us know your comments.

Regards,
Bharat
________________________________________
From: dhcwg-bounces@ietf.org [dhcwg-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org [internet-drafts@ietf.org]
Sent: Wednesday, January 25, 2012 7:38 PM
To: i-d-announce@ietf.org
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-l2ra-06.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           : Layer 2 Relay Agent Information
        Author(s)       : Bharat Joshi
                          Pavan Kurapati
        Filename        : draft-ietf-dhc-l2ra-06.txt
        Pages           : 13
        Date            : 2012-01-25

   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 a Relay Agent Information option
   in DHCP messages.  These devices are typically known as Layer 2 Relay
   Agents.

   This document aims to describe the network scenarios where a Layer 2
   Relay Agent is in use and also how it handles DHCP messages.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-l2ra-06.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-dhc-l2ra-06.txt

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

**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are not 
to copy, disclose, or distribute this e-mail or its contents to any other person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys has taken 
every reasonable precaution to minimize this risk, but is not liable for any damage 
you may sustain as a result of any virus in this e-mail. You should carry out your 
own virus checks before opening the e-mail or attachment. Infosys reserves the 
right to monitor and review the content of all messages sent to or from this e-mail 
address. Messages sent to or from this e-mail address may be stored on the 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***