Re: Documentation Edit Request: 2.6 .4. Address Filter Administrative Web Page
Eric Shubert <[email protected]>
| Newsgroups | gmane.comp.security.ipcop.devel |
|---|---|
| Organization | Eric Shubert & Associates |
| Message-ID | <[email protected]> |
On 09/09/2012 08:31 AM, Olaf Westrik wrote:
> On 2012-09-07 16:03, Eric Shubert wrote:
>
>> I googled briefly for something about this in the RFCs, but came up with
>> nothing. If there's something in an RFC about this, I'd like to know
>> what it says.
>
> Last item in this list http://tools.ietf.org/html/rfc2131#section-1.6 is
> probably the closest thing. And yes, network address is a configuration
> parameter.
>
> OTOH the RFCs describe mostly protocol issues, not the nomenclature used
> in specific implementations.
>
>
> Olaf
>
> ------------------------------------------------------------------------------
Just for the record, that link says:
o Support fixed or permanent allocation of configuration
parameters to specific clients.
Given this, I think that using the term 'fixed' is certainly not
incorrect. Personally I prefer 'fixed' over 'reserved'.
I wonder if perhaps MS (Server) introduced the term 'reserved'. I'd be
interested to know when it first came to be applied in this context.
BL, I think the IPCop documentation can be left as is. Thanks to Eric O
for getting it changed!
--
-Eric 'shubes'
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/