[NTLUG:Discuss] DHCP

Burton Strauss Burton_Strauss at comcast.net
Thu Sep 8 14:48:41 CDT 2005


Sure ... There's a rhythm to reading these - you need two wrap your head
around the definitions of the capitalized terms.  AFAIK they are defined in
EVERY RFC.

1.4 Requirements

   Throughout this document, the words that are used to define the
   significance of particular requirements are capitalized.  These words
   are:

      o "MUST"

        This word or the adjective "REQUIRED" means that the
        item is an absolute requirement of this specification.

      o "MUST NOT"

        This phrase means that the item is an absolute prohibition
        of this specification.

      o "SHOULD"

        This word or the adjective "RECOMMENDED" means that there
        may exist valid reasons in particular circumstances to ignore
        this item, but the full implications should be understood and
        the case carefully weighed before choosing a different course.

      o "SHOULD NOT"

        This phrase means that there may exist valid reasons in
        particular circumstances when the listed behavior is acceptable
        or even useful, but the full implications should be understood
        and the case carefully weighed before implementing any behavior
        described with this label.

      o "MAY"

        This word or the adjective "OPTIONAL" means that this item is
        truly optional.  One vendor may choose to include the item
        because a particular marketplace requires it or because it
        enhances the product, for example; another vendor may omit the
        same item.

-----Burton
 

-----Original Message-----
From: discuss-bounces at ntlug.org [mailto:discuss-bounces at ntlug.org] On Behalf
Of Johnny Cybermyth
Sent: Thursday, September 08, 2005 1:57 PM
To: Burton.Strauss at comcast.net; NTLUG Discussion List
Subject: Re: [NTLUG:Discuss] DHCP

Thanks for the link.  I'd never read any of the spec, only dealt with
various implementations.

Burton Strauss wrote:
> It should not be a problem as according to best practices per the RFC 
> the assigned address should be tested a couple of times to prevent
conflict.
> 
> But it's certainly not a good idea.  A badly implemented DHCP server 
> could choose not to perform the tests - SHOULD in RFC parlance isn't
required.
> 
> http://www.faqs.org/rfcs/rfc2131.html

_______________________________________________
https://ntlug.org/mailman/listinfo/discuss





More information about the Discuss mailing list