[dhcwg] FW: I-D ACTION:draft-joshi-dhc-l2ra-00.txt

Bharat Joshi <bharat_joshi@infosys.com> Tue, 13 November 2007 16:28 UTC

Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrycN-00029w-78; Tue, 13 Nov 2007 11:28:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrycL-00029l-6q for dhcwg@ietf.org; Tue, 13 Nov 2007 11:28:01 -0500
Received: from sfovwl03.inf.com ([216.251.50.9] helo=SFOVWL03.infosys.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IrycH-0002cQ-SA for dhcwg@ietf.org; Tue, 13 Nov 2007 11:28:01 -0500
Received: from INDHUBBHS02.ad.infosys.com ([192.168.200.82]) by SFOVWL03.infosys.com with InterScan Message Security Suite; Tue, 13 Nov 2007 08:26:30 -0800
Received: from blrkechub04.ad.infosys.com ([10.66.236.44]) by INDHUBBHS02.ad.infosys.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 13 Nov 2007 21:57:54 +0530
Received: from BLRKECMBX02.ad.infosys.com ([10.66.236.22]) by blrkechub04.ad.infosys.com ([10.66.236.44]) with mapi; Tue, 13 Nov 2007 21:57:54 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Date: Tue, 13 Nov 2007 21:57:52 +0530
Thread-Topic: I-D ACTION:draft-joshi-dhc-l2ra-00.txt
Thread-Index: AcgmCsF7YiAGpKS/TiCYcWjtaDPqBwABhDcs
Message-ID: <31D55C4D55BEED48A4459EB64567589A0ADFF09687@BLRKECMBX02.ad.infosys.com>
References: <E1IrxTi-000212-Dd@stiedprstage1.ietf.org>
In-Reply-To: <E1IrxTi-000212-Dd@stiedprstage1.ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/mixed; boundary="_003_31D55C4D55BEED48A4459EB64567589A0ADFF09687BLRKECMBX02ad_"
MIME-Version: 1.0
X-OriginalArrivalTime: 13 Nov 2007 16:27:54.0710 (UTC) FILETIME=[24B3F760:01C82612]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Subject: [dhcwg] FW: I-D ACTION:draft-joshi-dhc-l2ra-00.txt
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>
Errors-To: dhcwg-bounces@ietf.org

Hi,

       Based on the feedback received in last IETF and on mailing list, we have created a document that provides information on Layer 2 Relay Agent functionality and describes the changes in DHCP server, Relay Agents because of the introduction of Layer 2 Relay Agent in different network scenarios.

      Please review this document and let us know your comments/suggestions.

Thanks & Regards,
Bharat
________________________________________
From: Internet-Drafts@ietf.org [Internet-Drafts@ietf.org]
Sent: Tuesday, November 13, 2007 8:45 PM
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-joshi-dhc-l2ra-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories.


        Title           : Layer 2 Relay Agent Information
        Author(s)       : B. Joshi, P. Kurapati
        Filename        : draft-joshi-dhc-l2ra-00.txt
        Pages           : 18
        Date            : 2007-11-13

   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 closest Layer 2
   device to append 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 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-joshi-dhc-l2ra-00.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then
"get draft-joshi-dhc-l2ra-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
        mailserv@ietf.org.
In the body type:
        "FILE /internet-drafts/draft-joshi-dhc-l2ra-00.txt".

NOTE:   The mail server at ietf.org can return the document in
        MIME-encoded form by using the "mpack" utility.  To use this
        feature, insert the command "ENCODING mime" before the "FILE"
        command.  To decode the response(s), you will need "munpack" or
        a MIME-compliant mail reader.  Different MIME-compliant mail readers
        exhibit different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have been split
        up into multiple messages), so check your local documentation on
        how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.


**************** 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***
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg