On 2018 Dec 09 19:04:02, you wrote to Carol Shenkenberger:
CS>> Not if we align them. Take what is in existing use, see what the
CS>> differences are, then what tools already use them and see what works.
MR> The FTSC documented one:
MR> - if there's an address in the IBN flag use that one and only that one
the phrase "only that one" does not appear in FTS-5001.006... yes, if there's a
domain attached to the IBN flag, use it...
i think that the two examples given using two of the same flag should be
expanded to show how to use two or more other flags with attached domains as
well... i don't understand why this is so hard...
MR> - if the IBN flag doesn't include an address take all the addresses
MR> from all INA flags
yes...
MR> The undocumented standard:
MR> - take all addresses in IBN and INA flags
that's not undocumented... if there are domains listed on the flags, they are
all taken and considered for the final output... the decision making tree for
that is different for different mailers... some are protocol oriented, some do
not recognise INA, some use INA as well as the domains attached to other
flags...
MR> Q: How ports are handled by the undocumented standard? If we have
MR> INA:my-bbs.ddns.org and IBN:my-bbs.dyndns.com:8080 for example, does the
MR> port number also apply the the address in the INA flag?
CS>> This isn't a really common thing to see (a site with 2 lookup
CS>> addresses). I'd say most of us with 2 have a reason for it. Mine is
CS>> backup connectivity for the most part. I've had one or the other go
CS>> off for a bit and with the game league (Battlenet) that can get nasty
CS>> fast.
MR> Over here most of the distribution nodes have several FQDNs for
resilience.
MR> If one dyn-DNS service fails the node is still reachable via its second
MR> FQDN.
that's exactly what xxcarol is doing with her INA/IBN entries...
)\/(ark
Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... My kid wanted a watch for Christmas, so we let him.
---
* Origin: (1:3634/12.73)
|