• Zone 1 NCs updated to MakeNL_NG

    From Michiel van der Vlist@2:280/5555 to Kees van Eeten on Fri Jul 27 01:25:03 2018
    Hello Kees,

    On Wednesday January 30 2013 12:34, you wrote to Janis Kracht:

    140 :waiting for changes to O2/2 version 153

    The net carries four nodes, that have the Pvt, tag.
    Only one is bound to change when allowunpub is implemented.
    The other three are Pvt in the original sence if its use.
    Again the question, should this be a showstopper.?

    No net or region - no matter how big or small - should be a show stopper.

    When the ZC's are ready - and it appears they are - there is no need to wait for the lower echelons. Segments from regions or nets that have not made the transition will be processed as they are. No problem, No show stopper.


    Cheers, Michiel

    --- GoldED+/W32-MINGW 1.1.5-b20110320
    * Origin: http://www.vlist.org (2:280/5555)
  • From Kees van Eeten@2:280/5003.4 to Janis Kracht on Fri Jul 27 01:25:03 2018
    Hello Janis!

    Please allow me to comment.

    28 Jan 13 19:34, you wrote to All:

    R10
    213 waiting for confirmation

    Net 213 has one node. That carries u all zero phone number.
    The only reason the nethost needs a new makenl_ng is to be able
    to change the all zero's by -Unpublished-
    However the hostnames hor net Nethost and the only netmember resolve
    to the same IP address, cold both be the same system?
    This cannot be a showstopper for the ZC's to change the AllowUnpub flag.


    R17
    140 :waiting for changes to O2/2 version 153

    The net carries four nodes, that have the Pvt, tag.
    Only one is bound to change when allowunpub is implemented.
    The other three are Pvt in the original sence if its use.
    Again the question, should this be a showstopper.?

    Kees

    --- FPD v2.9.040207 GoldED+/LNX 1.1.5
    * Origin: My views are moderated by a virtual Penguin (2:280/5003.4)