Hello everyone ... and apologies if this has been discussed already.

Looking at the nodelist flags IBN, IFC, IFT, ITN, and IVM, and how they're used in my current nodelist, I see them used as-is, and I see them used with a :port_number construct.

That makes sense.

I see the INA flag being used to signal a node's "Internet address", like "INA:my.spiffy.server.whatever".

That makes sense.

Looking at the end of the nodelist, I see comments regarding these flags, and that there's optional data in the form <flag>[:IP addres]

That does not make sense.

Looking at current practice, it seems I should implement the things above that make sense, and ignore the things that do not ;-)


-joho

---
* Origin: future hacker central (2:201/4609)

Hi Joaquim,

On 2025-02-12 13:14:46, you wrote to All:

Hello everyone ... and apologies if this has been discussed already.

Looking at the nodelist flags IBN, IFC, IFT, ITN, and IVM, and how they're used in my current nodelist, I see them used as-is, and I see them used with a
:port_number construct.

That makes sense.

I see the INA flag being used to signal a node's "Internet address", like "INA:my.spiffy.server.whatever".

That makes sense.

Looking at the end of the nodelist, I see comments regarding these flags, and
that there's optional data in the form <flag>[:IP addres]

This form has its purpose! The INA flag applies to all the other Ixx flags on a line. But if you want to use different host names for different Ixx flags, you can do so after the specific Ixx flag.
Also if you just have one Ixx flag and one host name: The Ixx:<fqdn>[:port] form is shorter.

That does not make sense.

Looking at current practice, it seems I should implement the things above that
make sense, and ignore the things that do not ;-)

Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

12 Feb 2025 13:14, you wrote to All:

Looking at the end of the nodelist, I see comments regarding these
flags, and that there's optional data in the form <flag>[:IP addres]

That does not make sense.

Looking at current practice, it seems I should implement the things
above that make sense, and ignore the things that do not ;-)

I suggest you check FTS-5001.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234)

Joaquim Homrighausen -> All skrev 2025-02-12 13:14:

Looking at current practice, it seems I should implement the things
above that make sense, and ignore the things that do not ;-)

That makes sense. :)

--

Everything happens for a reason. Sometimes the reason is you're stupid and make bad decisions.

..

--- Mozilla/5.0 (Windows; U; Windows NT 6.1; sv-SE; rv:1.9.1.5) Gecko/20091121
* Origin: news://eljaco.se:4119 (2:203/2)

* On Wed 12 Feb 2025 13.54, <Wilfred van Velzen> wrote:

This form has its purpose! The INA flag applies to all the other
Ixx flags on a line. But if you want to use different host names
for different Ixx flags, you can do so after the specific Ixx
flag.

OK ... is this a realistic use case?

Also if you just have one Ixx flag and one host name: The Ixx:<fqdn>[:port] form is shorter.

Uhm ...

ITN:12345,INA:cloud.cherry
ITN:cloud.cherry:12345

Yes, we saved all of four characters ;-)


-joho

---
* Origin: future hacker central (2:201/4609)

Hi Joaquim,

On 2025-02-12 16:05:12, you wrote to me:

This form has its purpose! The INA flag applies to all the other
Ixx flags on a line. But if you want to use different host names
for different Ixx flags, you can do so after the specific Ixx
flag.

OK ... is this a realistic use case?

That doesn't matter. It's a valid use case, so someone could use it now or in the future for his nodelist entry. So software using the nodelist should be able to handle it.

I did a grep. There currently are a few nodes that have more then one IBN:<fqdn> entry, but not multiple mixed Ixx:<fqdn> flags.

Also if you just have one Ixx flag and one host name: The
Ixx:<fqdn>[:port] form is shorter.

Uhm ...

ITN:12345,INA:cloud.cherry
ITN:cloud.cherry:12345

Yes, we saved all of four characters ;-)

This used to be important! ;-)


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

Re: Re: Nodelist flags for "Internet connectivity"
By: Wilfred van Velzen to Joaquim Homrighausen on Wed Feb 12 2025 01:54 pm

Howdy,

This form has its purpose! The INA flag applies to all the other Ixx flags on a line. But if you want to use different host names for different Ixx flags, you can do so after the specific Ixx flag.

I'm curious.

In which use case would I want to use a different hostname for each flag/protocol?


...ëîåï
--- SBBSecho 3.23-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)

Hi deon,

On 2025-02-13 08:17:22, you wrote to me:

This form has its purpose! The INA flag applies to all the other Ixx
flags on a line. But if you want to use different host names for
different Ixx flags, you can do so after the specific Ixx flag.

I'm curious.

In which use case would I want to use a different hostname for each flag/protocol?

I don't know. People think of the strangest setups. Maybe someone wants to run frontdoor on a dos/windows machine for ITN, and IBN on a linux machine, behind a different hostname.

The point is you can do this according to the current FTS-5001 established standard. So someone might do this at some point in time, for whatever reason. So software that processes the nodelist should be able to handle it.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

Hello Wilfred,

On Wednesday February 12 2025 16:26, you wrote to Joaquim Homrighausen:

OK ... is this a realistic use case?

That doesn't matter. It's a valid use case, so someone could use it
now or in the future for his nodelist entry. So software using the nodelist should be able to handle it.

I did a grep. There currently are a few nodes that have more then one IBN:<fqdn> entry, but not multiple mixed Ixx:<fqdn> flags.

At he time the documentation was written there actually were nodes that had different addresses for different protocols.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nieuw Schnøørd (2:280/5555)

Hello Wilfred,

On Wednesday February 12 2025 16:26, you wrote to Joaquim Homrighausen:

ITN:12345,INA:cloud.cherry
ITN:cloud.cherry:12345

Yes, we saved all of four characters ;-)

This used to be important! ;-)

Also: the practise of having the host name in the protocol flag was first. It existed before the INA flag.

The INA flag was introduced to avoid having to repeat the same host name for every protocol flag. At the time repeating the host name for every protocol caused problems because of a bug in MakeNl that limited line length to 152? characters.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nieuw Schnøørd (2:280/5555)