<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.huang-dhc-relay-ps" target="https://datatracker.ietf.org/doc/html/draft-huang-dhc-relay-ps-00">
   <front>
      <title>Problem Statement for DHCP Relay Agent</title>
      <author initials="L." surname="Huang" fullname="Lu Huang">
         <organization>China Mobile</organization>
      </author>
      <author initials="H." surname="Deng" fullname="DENG Hui">
         <organization>China Mobile</organization>
      </author>
      <author initials="P." surname="Kurapati" fullname="Pavan Kurapati">
         <organization>Infosys Technologies</organization>
      </author>
      <author initials="B." surname="Joshi" fullname="Bharat Joshi">
         <organization>Infosys Technologies</organization>
      </author>
      <date month="July" day="5" year="2009" />
      <abstract>
	 <t>RFC 3046 allows only the first Relay Agent to append Relay Agent
Information option.  In some networks, Layer 2 Relay Agents and Layer
3 Relay Agents are deployed but only Layer 2 Relay Agent appends the
Relay Agent Information option.  This document describes two pretty
common network scenarios that uses Layer 2 and Layer 3 Relay Agents
and their unique requirements where either DHCP server or Relay Agent
need more information to handle DHCP messages.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-huang-dhc-relay-ps-00" />
   
</reference>
