RFC 2322:Management of IP numbers by peg-dhcp
RFC-Ref

client


Click on the red underlined text to get to the source

... It can also provide some fixed additional fields global for all clients like netmask and even autoproxyconfigs. It does not depend on a particular ip-stack. ...


... The server can hand out two parts to the client, the peg and a paper with additional fields fixed for the site the server is running for. We will describe both here. ...


... The pegs and the IP-numbers are issued at the server to the client. Normally the client has to visit the server personally. Depending on ...
... IP-numbers are issued at the server to the client. Normally the client has to visit the server personally. Depending on how secure and controlled you want the process, the client has to ask ...
... Normally the client has to visit the server personally. Depending on how secure and controlled you want the process, the client has to ask for a peg to a responsible person, or he or she can just get a peg from store himself. ...


... However, if a client decides that it doesn't need an IP-number anymore it can bring the peg back to the server. ...
... If the server is not manned (the client has to help themselves), the only thing possible is that the client just places the peg back into ...
... If the server is not manned (the client has to help themselves), the only thing possible is that the client just places the peg back into the pool. ...


... The client side. ...


... On the client side all sorts of clients exist and cooperate freely. Due to the human factor of the clients ...
... On the client side all sorts of clients exist and cooperate freely. Due to the human factor of the clients transferring information from ...
... client side all sorts of clients exist and cooperate freely. Due to the human factor of the clients transferring information from peg to IP stack, the information can be misinterpreted, which could ...



Google
Web
RFC-Ref