NetworkWorkingGroupM.

Patrick
RequestforComments:3046MotorolaBCS
Category:StandardsTrackJanuary2001

DHCPRelayAgentInformationOption
StatusofthisMemo
ThisdocumentspecifiesanInternetstandardstrackprotocolforthe
Internetcommunity,andrequestsdiscussionandsuggestionsfor
improvements.Pleaserefertothecurrenteditionofthe"Internet
OfficialProtocolStandards"(STD1)forthestandardizationstate
andstatusofthisprotocol.Distributionofthismemoisunlimited.
CopyrightNotice
Copyright(C)TheInternetSociety(2001).AllRightsReserved.
Abstract
NewerhighspeedpublicInternetaccesstechnologiescallfora
highspeedmodemtohavealocalareanetwork(LAN)attachmenttoone
ormorecustomerpremisehosts.Itisadvantageoustousethe
DynamicHostConfigurationProtocol(DHCP)asdefinedinRFC2131to
assigncustomerpremisehostIPaddressesinthisenvironment.
However,anumberofsecurityandscalingproblemsarisewithsuch
"public"DHCPuse.ThisdocumentdescribesanewDHCPoptionto
addresstheseissues.ThisoptionextendsthesetofDHCPoptionsas
definedinRFC2132.
ThenewoptioniscalledtheRelayAgentInformationoptionandis
insertedbytheDHCPrelayagentwhenforwardingclientoriginated
DHCPpacketstoaDHCPserver.ServersrecognizingtheRelayAgent
InformationoptionmayusetheinformationtoimplementIPaddressor
otherparameterassignmentpolicies.TheDHCPServerechoesthe
optionbackverbatimtotherelayagentinservertoclientreplies,
andtherelayagentstripstheoptionbeforeforwardingthereplyto
theclient.
The"RelayAgentInformation"optionisorganizedasasingleDHCP
optionthatcontainsoneormore"suboptions"thatconvey
informationknownbytherelayagent.Theinitialsuboptionsare
definedforarelayagentthatiscolocatedinapubliccircuit
accessunit.Theseincludea"circuitID"fortheincomingcircuit,
anda"remoteID"whichprovidesatrustedidentifierfortheremote
highspeedmodem.

PatrickStandardsTrack[Page1]


RFC3046DHCPRelayAgentInformationOptionJanuary2001

TableofContents
1Introduction...........................................2
1.1HighSpeedCircuitSwitchedDataNetworks..............2
1.2DHCPRelayAgentintheCircuitAccessEquipment.......4
2.0RelayAgentInformationOption.........................5
2.1AgentOperation........................................6
2.1.1ReforwardedDHCPrequests............................7
2.2ServerOperation.......................................7
3.0RelayAgentInformationSuboptions.....................8
3.1AgentCircuitID.......................................8
3.2AgentRemoteID........................................9
4.0IssuesResolved........................................9
5.0SecurityConsiderations................................10
6.0IANAConsiderations....................................11
7.0IntellectualPropertyNotice...........................12
8.0References.............................................12
9.0Glossary...............................................13
10.0Author'sAddress......................................13
11.0FullCopyrightStatement.............................14
1Introduction
1.1HighSpeedCircuitSwitchedDataNetworks
PublicAccesstotheInternetisusuallyviaacircuitswitcheddata
network.Today,thisisprimarilyimplementedwithdialupmodems
connectingtoaRemoteAccessServer.Buthigherspeedcircuit
accessnetworksalsoincludeISDN,ATM,FrameRelay,andCableData
Networks.Allofthesenetworkscanbecharacterizedasa"star"
topologywheremultipleusersconnecttoa"circuitaccessunit"via
switchedorpermanentcircuits.
Withdialupmodems,onlyasinglehostPCattemptstoconnecttothe
centralpoint.ThePPPprotocoliswidelyusedtoassignIP
addressestobeusedbythesinglehostPC.
Thenewerhighspeedcircuittechnologies,however,frequently
provideaLANinterface(especiallyEthernet)tooneormorehost
PCs.ItisdesirabletosupportcentralizedassignmentoftheIP
addressesofhostcomputersconnectingonsuchcircuitsviaDHCP.
TheDHCPservercanbe,butusuallyisnot,coimplementedwiththe
centralizedcircuitconcentrationaccessdevice.TheDHCPserveris
oftenconnectedasaseparateserveronthe"CentralLAN"towhich
thecentralaccessdevice(ordevices)attach.

PatrickStandardsTrack[Page2]


RFC3046DHCPRelayAgentInformationOptionJanuary2001

AcommonphysicalmodelforhighspeedInternetcircuitaccessis
showninFigure1,below.
++|
Central|Circuit|ckt1Modem1Host|HostA
LAN||Access|Lan|HostB
||Unit1||HostC
||||
||(relayagent)|...
++|++
|DHCP||
|Server||
++|
|
|++
++||Circuit|ckt1Modem2HostHostD
|Other|||Access|Lan
|Servers|||Unit2|
|(Web,||||ckt2Modem3HostHostE
|DNS)|||(relayagent)|...Lan
||++
++
Figure1:DHCPHighSpeedCircuitAccessModel
Notethatinthismodel,the"modem"connectstoaLANattheuser
site,ratherthantoasinglehost.Multiplehostsareimplemented
atthissite.Althoughitiscertainlypossibletoimplementafull
IProuterattheusersite,thisrequiresarelativelyexpensive
pieceofequipment(comparedtotypicalmodemcosts).Furthermore,a
routerrequiresanIPaddressnotonlyforeveryhost,butforthe
routeritself.Finally,ausersiderouterrequiresadedicated
LogicalIPSubnet(LIS)foreachuser.Whilethismodelis
appropriateforrelativelysmallcorporatenetworkingenvironments,
itisnotappropriateforlarge,publicaccessednetworks.Inthis
scenario,itisadvantageoustoimplementanIPnetworkingmodelthat
doesnotallocateanIPaddressforthemodem(orothernetworking
equipmentdeviceattheusersite),andespeciallynotanentireLIS
fortheusersideLAN.
NotethatusingthismethodtoobtainIPaddressesmeansthatIP
addressescanonlybeobtainedwhilecommunicationtothecentral
siteisavailable.SomehostlaninstallationsmayusealocalDHCP
serverorothermethodstoobtainIPaddressesforinhouseuse.

PatrickStandardsTrack[Page3]


RFC3046DHCPRelayAgentInformationOptionJanuary2001

1.2DHCPRelayAgentintheCircuitAccessUnit
ItisdesirabletouseDHCPtoassigntheIPaddressesforpublic
highspeedcircuitaccess.Anumberofcircuitaccessunits(e.g.,
RAS's,cablemodemterminationsystems,ADSLaccessunits,etc)
connecttoaLAN(orlocalinternet)towhichisattachedaDHCP
server.
Forscalingandsecurityreasons,itisadvantageoustoimplementa
"routerhop"atthecircuitaccessunit,muchlikehighcapacity
RAS'sdotoday.Thecircuitaccessequipmentactsasbotharouter
tothecircuitsandastheDHCPrelayagent.
TheadvantagesofcolocatingtheDHCPrelayagentwiththecircuit
accessequipmentare:
DHCPbroadcastrepliescanberoutedtoonlythepropercircuit,
avoiding,say,thereplicationoftheDCHPreplybroadcastonto
thousandsofaccesscircuits
Thesamemechanismusedtoidentifytheremoteconnectionofthe
circuit(e.g.,auserIDrequestedbyaRemoteAccessServeracting
asthecircuitaccessequipment)maybeusedasahostidentifierby
DHCP,andusedforparameterassignment.Thisincludescentralized
assignmentofIPaddressestohosts.Thisprovidesasecureremote
IDfromatrustedsourcetherelayagent.
AnumberofissuesarisewhenforwardingDHCPrequestsfromhosts
connectingpubliclyaccessedhighspeedcircuitswithLANconnections
atthehost.ManyofthesearesecurityissuesarisingfromDHCP
clientrequestsfromuntrustedsources.Howdoestherelayagent
knowtowhichcircuittoforwardreplies?Howdoesthesystem
preventDHCPIPexhaustionattacks?Thisiswhenanattacker
requestsallavailableIPaddressesfromaDHCPserverbysending
requestswithfabricatedclientMACaddresses.HowcananIPaddress
orLISbepermanentlyassignedtoaparticularuserormodem?How
doesoneprevent"spoofing"ofclientidentifierfieldsusedto
assignIPaddresses?Howdoesonepreventdenialofserviceby
"spoofing"otherclient'sMACaddresses?
Alloftheseissuesmaybeaddressedbyhavingthecircuitaccess
equipment,whichisatrustedcomponent,addinformationtoDHCP
clientrequeststhatitforwardstotheDHCPserver.

PatrickStandardsTrack[Page4]


RFC3046DHCPRelayAgentInformationOptionJanuary2001

2.0RelayAgentInformationOption
ThisdocumentdefinesanewDHCPOptioncalledtheRelayAgent
InformationOption.Itisa"container"optionforspecificagent
suppliedsuboptions.TheformatoftheRelayAgentInformation
optionis:
CodeLenAgentInformationField
+++++++...++
|82|N|i1|i2|i3|i4||iN|
+++++++...++
ThelengthNgivesthetotalnumberofoctetsintheAgent
InformationField.TheAgentInformationfieldconsistsofa
sequenceofSubOpt/Length/Valuetuplesforeachsuboption,encoded
inthefollowingmanner:
SubOptLenSuboptionValue
+++++++...++
|1|N|s1|s2|s3|s4||sN|
+++++++...++
SubOptLenSuboptionValue
+++++++...++
|2|N|i1|i2|i3|i4||iN|
+++++++...++
No"pad"suboptionisdefined,andtheInformationfieldshallNOT
beterminatedwitha255suboption.ThelengthNoftheDHCPAgent
InformationOptionshallincludeallbytesofthesuboption
code/length/valuetuples.Sinceatleastonesuboptionmustbe
defined,theminimumRelayAgentInformationlengthistwo(2).The
lengthNofthesuboptionsshallbethenumberofoctetsinonly
thatsuboption'svaluefield.Asuboptionlengthmaybezero.The
suboptionsneednotappearinsuboptioncodeorder.
TheinitialassignmentofDHCPRelayAgentSuboptionsisasfollows:
DHCPAgentSubOptionDescription
SuboptionCode

1AgentCircuitIDSuboption
2AgentRemoteIDSuboption

PatrickStandardsTrack[Page5]


RFC3046DHCPRelayAgentInformationOptionJanuary2001

2.1AgentOperation
OveralladdingoftheDHCPrelayagentoptionSHOULDbeconfigurable,
andSHOULDbedisabledbydefault.RelayagentsSHOULDhaveseparate
configurablesforeachsuboptiontocontrolwhetheritisaddedto
clienttoserverpackets.
ADHCPrelayagentaddingaRelayAgentInformationfieldSHALLadd
itasthelastoption(butbefore'EndOption'255,ifpresent)in
theDHCPoptionsfieldofanyrecognizedBOOTPorDHCPpacket
forwardedfromaclienttoaserver.
RelayagentsreceivingaDHCPpacketfromanuntrustedcircuitwith
giaddrsettozero(indicatingthattheyarethefirsthoprouter)
butwithaRelayAgentInformationoptionalreadypresentinthe
packetSHALLdiscardthepacketandincrementanerrorcount.A
trustedcircuitmaycontainatrusteddownstream(closertoclient)
networkelement(bridge)betweentherelayagentandtheclientthat
MAYaddarelayagentoptionbutnotsetthegiaddrfield.Inthis
case,therelayagentdoesNOTadda"second"relayagentoption,but
forwardstheDHCPpacketpernormalDHCPrelayagentoperations,
settingthegiaddrfieldasitdeemsappropriate.
Themechanismsfordistinguishingbetween"trusted"and"untrusted"
circuitsarespecifictothetypeofcircuitterminationequipment,
andmayinvolvelocaladministration.Forexample,aCableModem
TerminationSystemmayconsiderupstreampacketsfrommostcable
modemsas"untrusted",butanATMswitchterminatingVCsswitched
throughaDSLAMmayconsidersuchVCsas"trusted"andacceptarelay
agentoptionaddedbytheDSLAM.
RelayagentsMAYhaveaconfigurableforthemaximumsizeoftheDHCP
packettobecreatedafterappendingtheAgentInformationoption.
Packetswhich,afterappendingtheRelayAgentInformationoption,
wouldexceedthisconfiguredmaximumsizeshallbeforwardedWITHOUT
addingtheAgentInformationoption.AnerrorcounterSHOULDbe
incrementedinthiscase.Intheabsenceofthisconfigurable,the
agentSHALLNOTincreaseaforwardedDHCPpacketsizetoexceedthe
MTUoftheinterfaceonwhichitisforwarded.
TheRelayAgentInformationoptionechoedbyaserverMUSTberemoved
byeithertherelayagentorthetrusteddownstreamnetworkelement
whichaddeditwhenforwardingaservertoclientresponsebackto
theclient.

PatrickStandardsTrack[Page6]


RFC3046DHCPRelayAgentInformationOptionJanuary2001

TheagentSHALLNOTaddan"OptionOverload"optiontothepacketor
usethe"file"or"sname"fieldsforaddingRelayAgentInformation
option.ItSHALLNOTparseorremoveRelayAgentInformationoptions
thatmayappearinthesnameorfilefieldsofaservertoclient
packetforwardedthroughtheagent.
Theoperationofrelayagentsforspecificsuboptionsisspecified
withthatsuboption.
RelayagentsareNOTrequiredtomonitorormodifyclientoriginated
DHCPpacketsaddressedtoaserverunicastaddress.Thisincludes
theDHCPREQUESTsentwhenenteringtheRENEWINGstate.
RelayagentsMUSTNOTmodifyDHCPpacketsthatusetheIPSEC
AuthenticationHeaderorIPSECEncapsulatingSecurityPayload[6].
2.1.1ReforwardedDHCPrequests
ADHCPrelayagentmayreceiveaclientDHCPpacketforwardedfroma
BOOTP/DHCPrelayagentclosertotheclient.Suchapacketwillhave
giaddrasnonzero,andmayormaynotalreadyhaveaDHCPRelay
Agentoptioninit.
RelayagentsconfiguredtoaddaRelayAgentoptionwhichreceivea
clientDHCPpacketwithanonzerogiaddrSHALLdiscardthepacketif
thegiaddrspoofsagiaddraddressimplementedbythelocalagent
itself.
Otherwise,therelayagentSHALLforwardanyreceivedDHCPpacket
withavalidnonzerogiaddrWITHOUTaddinganyrelayagentoptions.
PerRFC2131,itshallalsoNOTmodifythegiaddrvalue.
2.2ServerOperation
DHCPserversunawareoftheRelayAgentInformationoptionwill
ignoretheoptionuponreceiveandwillnotechoitbackon
responses.Thisisthespecifiedserverbehaviorforunknown
options.
DHCPserversclaimingtosupporttheRelayAgentInformationoption
SHALLechotheentirecontentsoftheRelayAgentInformationoption
inallreplies.ServersSHOULDcopytheRelayAgentInformation
optionasthelastDHCPoptionintheresponse.ServersSHALLNOT
placetheechoedRelayAgentInformationoptionintheoverloaded
snameorfilefields.IfaserverisunabletocopyafullRelay
AgentInformationfieldintoaresponse,itSHALLsendtheresponse
withouttheRelayInformationField,andSHOULDincrementanerror
counterforthesituation.

PatrickStandardsTrack[Page7]


RFC3046DHCPRelayAgentInformationOptionJanuary2001

TheoperationofDHCPserversforspecificsuboptionsisspecified
withthatsuboption.
NotethatDHCPrelayagentsarenotrequiredtomonitorunicastDHCP
messagessentdirectlybetweentheclientandserver(i.e.,those
thataren'tsentviaarelayagent).However,somerelayagentsMAY
chosetodosuchmonitoringandaddrelayagentoptions.
Consequently,serversSHOULDbepreparedtohandlerelayagent
optionsinunicastmessages,butMUSTNOTexpectthemtoalwaysbe
there.
3.0RelayAgentInformationSuboptions
3.1AgentCircuitIDSuboption
ThissuboptionMAYbeaddedbyDHCPrelayagentswhichterminate
switchedorpermanentcircuits.Itencodesanagentlocalidentifier
ofthecircuitfromwhichaDHCPclienttoserverpacketwas
received.ItisintendedforusebyagentsinrelayingDHCP
responsesbacktothepropercircuit.Possibleusesofthisfield
include:
Routerinterfacenumber
SwitchingHubportnumber
RemoteAccessServerportnumber
FrameRelayDLCI
ATMvirtualcircuitnumber
CableDatavirtualcircuitnumber
ServersMAYusetheCircuitIDforIPandotherparameterassignment
policies.TheCircuitIDSHOULDbeconsideredanopaquevalue,with
policiesbasedonexactstringmatchonlythatis,theCircuitID
SHOULDNOTbeinternallyparsedbytheserver.
TheDHCPserverSHOULDreporttheAgentCircuitIDvalueofcurrent
leasesinstatisticalreports(includingitsMIB)andinlogs.Since
theCircuitIDislocalonlytoaparticularrelayagent,acircuit
IDshouldbequalifiedwiththegiaddrvaluethatidentifiesthe
relayagent.
SubOptLenCircuitID
+++++++++
|1|n|c1|c2|c3|c4|c5|c6|...
+++++++++

PatrickStandardsTrack[Page8]


RFC3046DHCPRelayAgentInformationOptionJanuary2001

3.2AgentRemoteIDSuboption
ThissuboptionMAYbeaddedbyDHCPrelayagentswhichterminate
switchedorpermanentcircuitsandhavemechanismstoidentifythe
remotehostendofthecircuit.TheRemoteIDfieldmaybeusedto
encode,forinstance:
a"callerID"telephonenumberfordialupconnection
a"username"promptedforbyaRemoteAccessServer
aremotecallerATMaddress
a"modemID"ofacabledatamodem
theremoteIPaddressofapointtopointlink
aremoteX.25addressforX.25connections
TheremoteIDMUSTbegloballyunique.
DHCPserversMAYusethisoptiontoselectparametersspecificto
particularusers,hosts,orsubscribermodems.TheoptionSHOULDbe
consideredanopaquevalue,withpoliciesbasedonexactstringmatch
onlythatis,theoptionSHOULDNOTbeinternallyparsedbythe
server.
TherelayagentMAYusethisfieldinadditiontoorinsteadofthe
AgentCircuitIDfieldtoselectthecircuitonwhichtoforwardthe
DHCPreply(e.g.,Offer,Ack,orNak).DHCPserversSHOULDreport
thisvalueinanyreportsorMIBsassociatedwithaparticular
client.
SubOptLenAgentRemoteID
+++++++++
|2|n|r1|r2|r3|r4|r5|r6|...
+++++++++
4.0IssuesResolved
TheDHCPrelayagentoptionresolvesseveralissuesinanenvironment
inwhichuntrustedhostsaccesstheinternetviaacircuitbased
publicnetwork.ThisresolutionassumesthatallDHCPprotocol
trafficbythepublichoststraversetheDHCPrelayagentandthat
theIPnetworkbetweentheDHCPrelayagentandtheDHCPserveris
uncompromised.
BroadcastForwarding
Thecircuitaccessequipmentforwardsthenormallybroadcasted
DHCPresponseonlyonthecircuitindicatedintheAgentCircuit
ID.

PatrickStandardsTrack[Page9]


RFC3046DHCPRelayAgentInformationOptionJanuary2001

DHCPAddressExhaustion
Ingeneral,theDHCPservermaybeextendedtomaintainadatabase
withthe"triplet"of
(clientIPaddress,clientMACaddress,clientremoteID)
TheDHCPserverSHOULDimplementpoliciesthatrestrictthenumber
ofIPaddressestobeassignedtoasingleremoteID.
StaticAssignment
TheDHCPservermayusetheremoteIDtoselecttheIPaddressto
beassigned.ItmaypermitstaticassignmentofIPaddressesto
particularremoteIDs,anddisallowanaddressrequestfroman
unauthorizedremoteID.
IPSpoofing
ThecircuitaccessdevicemayassociatetheIPaddressassignedby
aDHCPserverinaforwardedDHCPAckpacketwiththecircuitto
whichitwasforwarded.ThecircuitaccessdeviceMAYprevent
forwardingofIPpacketswithsourceIPaddressesotherthan
thoseithasassociatedwiththereceivingcircuit.Thisprevents
simpleIPspoofingattacksontheCentralLAN,andIPspoofingof
otherhosts.
ClientIdentifierSpoofing
ByusingtheagentsuppliedAgentRemoteIDoption,theuntrusted
andasyetunstandardizedclientidentifierfieldneednotbeused
bytheDHCPserver.
MACAddressSpoofing
ByassociatingaMACaddresswithanAgentRemoteID,theDHCP
servercanpreventofferinganIPaddresstoanattackerspoofing
thesameMACaddressonadifferentremoteID.
5.0SecurityConsiderations
DHCPascurrentlydefinedprovidesnoauthenticationorsecurity
mechanisms.Potentialexposurestoattackarediscussedinsection7
oftheDHCPprotocolspecificationinRFC2131[1].
Thisdocumentintroducesmechanismstoaddressseveralsecurity
attacksontheoperationofIPaddressassignment,includingIP
spoofing,ClientIDspoofing,MACaddressspoofing,andDHCPserver

PatrickStandardsTrack[Page10]


RFC3046DHCPRelayAgentInformationOptionJanuary2001

addressexhaustion.Itreliesonanimpliedtrustedrelationship
betweentheDHCPRelayAgentandtheDHCPserver,withanassumed
untrustedDHCPclient.Itintroducesanewidentifer,the"Remote
ID",thatisalsoassumedtobetrusted.TheRemoteIDisprovided
bytheaccessnetworkormodemandnotbyclientpremiseequipment.
CryptographicorothertechniquestoauthenticatetheremoteIDare
certainlypossibleandencouraged,butarebeyondthescopeofthis
document.
Thisoptionistargetedtowardsenvironmentsinwhichthenetwork
infrastructuretherelayagent,theDHCPserver,andtheentire
networkinwhichthosetwodevicesresideistrustedandsecure.
Asusedinthisdocument,theword"trusted"impliesthat
unauthorizedDHCPtrafficcannotenterthetrustednetworkexcept
throughsecuredandtrustedrelayagentsandthatalldevices
internaltothenetworkaresecureandtrusted.Potentialdeployers
ofthisoptionshouldgivecarefulconsiderationtothepotential
securityvulnerabilitiesthatarepresentinthismodelbefore
deployingthisoptioninactualnetworks.
NotethatanyfuturemechanismsforauthenticatingDHCPclientto
servercommunicationsmusttakecaretoomittheDHCPRelayAgent
optionfromserverauthenticationcalculations.Thiswasthe
principalreasonfororganizingtheDHCPRelayAgentOptionasa
singleoptionwithsuboptions,andforrequiringtherelayagentto
removetheoptionbeforeforwardingtotheclient.
Whileitisbeyondthescopeofthisdocumenttospecifythegeneral
forwardingalgorithmofpublicdatacircuitaccessunits,notethat
automaticreforwardingofIPorARPbroadcastpacketsbackdownstream
exposesseriousIPsecurityrisks.Forexample,ifanupstream
broadcastDHCPDISCOVERorDHCPREQUESTwererebroadcastback
downstream,anypublichostmayeasilyspoofthedesiredDHCPserver.
6.0IANAConsiderations
IANAisrequiredtomaintainanewnumberspaceof"DHCPRelayAgent
Suboptions",locatedintheBOOTPDHCPParametersRegistry.The
initialsuboptionsaredescribedinsection2.0ofthisdocument.
IANAassignsfutureDHCPRelayAgentSuboptionswitha"IETF
Consensus"policyasdescribedinRFC2434[3].Futureproposed
suboptionsaretobereferencedsymbolicallyintheInternetDrafts
thatdescribethem,andshallbeassignednumericcodesbyIANAwhen
approvedforpublicationasanRFC.

PatrickStandardsTrack[Page11]


RFC3046DHCPRelayAgentInformationOptionJanuary2001

7.0IntellectualPropertyNotices
Thissectioncontainstwonoticesasrequiredby[5]forstandards
trackdocuments.
TheIETFtakesnopositionregardingthevalidityorscopeofany
intellectualpropertyorotherrightsthatmightbeclaimedto
pertaintotheimplementationoruseofthetechnologydescribedin
thisdocumentortheextenttowhichanylicenseundersuchrights
mightormightnotbeavailableneitherdoesitrepresentthatit
hasmadeanyefforttoidentifyanysuchrights.Informationonthe
IETF'sprocedureswithrespecttorightsinstandardstrackand
standardsrelateddocumentationcanbefoundinBCP11.Copiesof
claimsofrightsmadeavailableforpublicationandanyassurancesof
licensestobemadeavailable,ortheresultofanattemptmadeto
obtainagenerallicenseorpermissionfortheuseofsuch
proprietaryrightsbyimplementorsorusersofthisspecificationcan
beobtainedfromtheIETFSecretariat.
TheIETFhasbeennotifiedofintellectualpropertyrightsclaimedin
regardtosomeorallofthespecificationcontainedinthis
document.Formoreinformationconsulttheonlinelistofclaimed
rights.
8.0References
[1]Droms,R.,"DynamicHostConfigurationProtocol",RFC2131,
March1997.
[2]Alexander,S.andR.Droms,"DHCPOptionsandBOOTPVendor
Extension",RFC2132,March1997.
[3]Narten,T.andH.Alvestrand,"GuidelinesforWritinganIANA
ConsiderationsSectioninRFCs",BCP26,RFC2434,October1998.
[4]Bradner,S.,"KeywordsforuseinRFCstoIndicateRequirement
Levels",BCP14,RFC2119,March1997.
[5]Bradner,S.,"TheInternetStandardsProcessRevision3",BCP
9,RFC2026,October1996.
[6]Kent,S.andR.Atkinson,"SecurityArchitectureforthe
InternetProtocol",RFC2401,November1998.

PatrickStandardsTrack[Page12]


RFC3046DHCPRelayAgentInformationOptionJanuary2001

9.0Glossary
DSLAMDigitalSubscriberLinkAccessMultiplexer
IANAInternetAssignedNumbersAuthority
LISLogicalIPSubnet
MACMessageAuthenticationCode
RASRemoteAccessServer
10.0Author'sAddress
MichaelPatrick
MotorolaBroadbandCommunicationsSector
20CabotBlvd.,MSM430
Mansfield,MA02048
Phone:(508)2615707
EMail:michael.patrick@motorola.com

PatrickStandardsTrack[Page13]


RFC3046DHCPRelayAgentInformationOptionJanuary2001

11.0FullCopyrightStatement
Copyright(C)TheInternetSociety(2001).AllRightsReserved.
Thisdocumentandtranslationsofitmaybecopiedandfurnishedto
others,andderivativeworksthatcommentonorotherwiseexplainit
orassistinitsimplementationmaybeprepared,copied,published
anddistributed,inwholeorinpart,withoutrestrictionofany
kind,providedthattheabovecopyrightnoticeandthisparagraphare
includedonallsuchcopiesandderivativeworks.However,this
documentitselfmaynotbemodifiedinanyway,suchasbyremoving
thecopyrightnoticeorreferencestotheInternetSocietyorother
Internetorganizations,exceptasneededforthepurposeof
developingInternetstandardsinwhichcasetheproceduresfor
copyrightsdefinedintheInternetStandardsprocessmustbe
followed,orasrequiredtotranslateitintolanguagesotherthan
English.
Thelimitedpermissionsgrantedaboveareperpetualandwillnotbe
revokedbytheInternetSocietyoritssuccessorsorassigns.
Thisdocumentandtheinformationcontainedhereinisprovidedonan
"ASIS"basisandTHEINTERNETSOCIETYANDTHEINTERNETENGINEERING
TASKFORCEDISCLAIMSALLWARRANTIES,EXPRESSORIMPLIED,INCLUDING
BUTNOTLIMITEDTOANYWARRANTYTHATTHEUSEOFTHEINFORMATION
HEREINWILLNOTINFRINGEANYRIGHTSORANYIMPLIEDWARRANTIESOF
MERCHANTABILITYORFITNESSFORAPARTICULARPURPOSE.
Acknowledgement
FundingfortheRFCEditorfunctioniscurrentlyprovidedbythe
InternetSociety.

PatrickStandardsTrack[Page14]