5.2 Autoconfiguration-Related Variables

There is number of data structures and flags that the Node can hold so it would be related with autoconfiguration.

A host maintains a number of data structures and flags related to autoconfiguration. In the following, we present conceptual variables and show how they are used to perform autoconfiguration. The specific variables are used for demonstration purposes only, and an implementation is not required to have them, so long as its external behavior is consistent with that described in this document..

Hosts maintain the following variables on a per-interface basis:

  ManagedFlag:   

 The flag indicates whether or not addresses are to be configured using the stateful autoconfiguration mechanism. It starts out in a FALSE state.(Copied from the M flag field of the most recently received Router Advertisement message.)

 

 

 

 

OtherConfigFlag: 

. The flag indicates whether or not information other than addresses is to be obtained using the stateful autoconfiguration mechanism. It starts out in a FALSE state. (Copied from the O flag field  of the most recently received Router Advertisement message.)
When the value of the ManagedFlag is TRUE, the value of OtherConfigFlag is implicitely TRUE as well. It is not a valid configuration for a host to use stateful address autoconfiguration to request addresses only, without also accepting other configuration information.

 


  

 

 

 

 

A host also maintains a list of addresses together with their corresponding lifetimes.
The address list contains both autoconfigured addresses and those configured manually.

Back