Hello Phil,

>> If one had both types of connection available (pots and ion) this
>> would work:

>> ,38,<> ga te.net,IBN,ITN,IFT

> Ummm, interesting. Think I may just use that.

Just don't put the funny space in the domain name 

> IBN, ITN and IFT would be fine,
> but my ITX listing uses a different addy. You just tack that on the end?

Yes, it would.. here's a copy of the proposal for the flag as posted in
Z1C, so you can read the exact details :)

====================cut here===============================
Z1C message #15917 from Ross Cassell to All.
   Entered on 11th November, 2002 at 18:34, 115 lines.

Subject: Nodelist Proposal
==========================
Hello All!

A Proposal. (Revision #2)

To allow the listing of a systems Internet address in the Fidonet St Louis
Format Nodelist, in order to minimise character usage based on constraints
in "some" nodelist processing software. This proposal is to fill
in the gaps until other proposals and software can be developed, tested and
deployed which can address the limitations of existing software and enhance
the networks utilisation of the Internet.

Many ways used to list a systems internet address have been to place a URL
in the bbs name field, location field or a IP address in the telephone
number field. In the absence of the prior, system internet addresses have
been placed with the appropriate internet proptocol flag, I will use binkp
flag as an example:

ibn:some_system.com:

(Where  is omitted if the default service port is used)

Those that offer several different internet protocols as a means to connect
with them, and if they so chose to list a dns name with each protocol flag,
run the risk of having a listing that would exceed the char length
constraint of some nodelist processors. While it can be argued validly that
these programs are "broken", they werent "broken" 2,3
or 5 + years ago.

What I propose is to have a flag, whose sole purpose is to provide a home
for a systems internet address, which would leave the Internet protocol
flags be, in order for those flags to only define the systems capability to
host the protocol they represent and optionally define a non-standard
service port that that system might be having the daemon hosting that
protocol listenning on.

INA (InterNet Address)

Usage:

,INA: or ,

Conventions:

* Must be listed before all other Internet Protocol Flags.

* If IP address is shown here, it must be a static IP.

* If IP address is shown here, IP cannot be a reserved IP address set aside for
  private use, such as but not limited to: 192.168.x.x, nor can IP address be
  the local loopback (localhost) IP address of 127.0.0.1.

* A FQDN must be listed here if the IP address is dynamically assigned.

* Sysop choice as to which to use, if a FQDN or static IP is available.

All other considerations:

This flag along with the other Internet Protocol Flags themselves cannot be
flown if the system CANNOT host INBOUND connections. (Nodes using email
tunneling protocols excluded)

If when using this flag, where most but not all protocols use the defined
system internet address, the protocol that requires a different internet
address that does not resolve to the same IP address or machine as the
rest, can still have the unique address defined with it as what has been
done in the past, like so:

,IBN::,

When doing so, these flags must be at the end of the nodes internet info,
to reflect a supercession of Internet addresses.

So instead of having this:

,IBN:some-address.com,IFT:some_address.com,ITN:some_address.com:60177,
IFC:some_address.com

We have 90 characters used to define that which can be conveyed like so:

,INA:some_address.com,IBN,IFT,ITN:60177,IFC

inside 43 characters for a savings of 47 characters while conveying the
SAME EXACT INFORMATION.

I further feel defining things this way would make it easier for coders to
develop programs that could more readily and reliably harvest this info for
usage elsewhere. If these proposals fly, the BBS Name and location fields
can be returned to what they were intended for.

Revision History:

#1 [11-10-2002]

* Changed URL (Universal Resource Locater) to DNA (Domain Name Address),
  to accomodate "literal meanings".

* Withdrew NNTP flag proposal pending a later date.

#2 [11-11-2002]

* Withdrew IPA, DNA flag proposals and replaced them with one flag proposal to
  achieve same goal, new flag proposal is "INA".

==
Ross
BBS -> http://www.the-estar.com - telnet://the-estar.com
rosscassell{at}mailshell.com | ICQ = 5305939 ... You Are Oppressed Only In
Your Own Mind, By Your Own Mind.
-+- GoldED+/W32 1.1.5-21006
 ! Origin: The Eastern Star (1:123/456)

==========================cut here====================


> Have a nice day!

I'll try, but it's SNOWING outside :)

This flag is going to be tested for the next 6 months, btw, so that should
give us plenty of time to see how beneficial they'll be.  Thanks for adding
them to your entry Phil :)

Take care,
Janis

--- BBBS/LiI v4.01 Flag-4