Subj : Test for links etc
To   : Vince Coen
From : Kees van Eeten
Date : Thu May 08 2014 02:08 pm

  Hello Vince!

07 Mai 14 23:49, you wrote to me:

VC>>> The flag INA is the primary source for an IP address. In fact
VC>>> according to my reading of the nodelist summary near the bottom
VC>>> of it INA is the only flag that relates to such.

VC>>> If you know of another method please let me know.

VC> I meant other method of storing the IP address within the NODELIST other
VC> than after INA:

Yes, but that is defying the purpose of the INA flag.

Then there is what is acceptable to makenl and not at least to your ZC.

Makenl accepts an IP address in the phonefield. That is a no-no in Z2 and
only a few remain in Z1, where they are redundant, as a hostname is also
presented in the system namefield or as an attribute of one of the flags.

Makenl accepts an IP address or hostname as an attribute to  IBN: this is
used in Z1, but not accepted in Z2.

Makenl has no concern with the systen name field. For historical reasons,
this field has been overloaded, by holding the DNS hostname of the system.
With the wider use of the INA: flag, many are returning to the folklore
of reusing the system namefield for a personal touch to the node, or
adding info about the administrative function of the node.

I do not expect the net to return to putting the DNS hostname in the
system name field, because MBSE does not support the INA: flag.

On the other hand MBSE is one of the reasons to have the INA: as it
supports three IP protocols.

Kees


--- FPD v2.9.040207  GoldED+/LNX 1.1.5--b20130910
* Origin: As for me, all I know is that, I know nothing. (2:280/5006.4)

You are viewing proxied material from vert.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.