TIP: Click on subject to list as thread! ANSI
echo: net_dev
to: Paul Edwards
from: Andrew Clarke
date: 1996-11-20 12:59:06
subject: Re: Some changes to FSC-0074

PLEASE DELETE ME FROM YOU MAILING LIST I DON'T KNOW WHO YOU ARE!!!


 On Sunday November 17 1996, Paul Edwards said to andrew clarke:

 PE> >>> LK> ---[ optionalinfo] *
Origin: optionaltext

 LK>>>>> (1:2/3.4{at}fidonet)

 PE> Adding "{at}fidonet" to the origin address is like adding
"{at}fidonet"
 PE> to the INTL line.  Wrong!

 PE> Wrong?  How so?

 PE> You can't go changing an already-defined control line.  You have to
 PE> come up with a new one.  BFN.  Paul.

 PE> Yes, with INTL,

 PE> And all others, too.

 PE> but how is adding {at}fidonet to the origin address changing
 PE> an already-defined control line?

 PE> It was not, and never was, common practice to put a domain in that
 PE> field.

 PE> While it isn't in common use, it is
 PE> specifying the complete network address of the originating system (as

 PE> requested by FTS-4).

 PE> Yes, that doesn't mean you go and take that as giving you carte
 PE> blanche
 PE> authority to change it to whatever you want.  You may as well go and
 PE> stick in the internet address of your fidonet node.  That's the
 PE> complete address too, right.  If the author of FTS-4 had heard about
 PE> domains at the time, he would likely have specified "don't put in the
 PE> domain though, as it's always the current domain".  He hadn't, and
 PE> didn't, and no-one does, and if anyone does, it's of no use anyway.
 PE> If that isn't enough to convince you, nothing will.

 PE> The authors of FSC-74 appear to agree with this.

 PE> The authors of FSC-74 have seen fit to change a lot of common
 PE> practice. I don't actually mind that, as I've got source code to most
 PE> of my software, and have the technical expertise to adjust overnight.
 PE> Changes are often good too.  I've got a long list of changes that I
 PE> would like.  One of which is to adopt RFC-822.  Actually, I must
 PE> confess, I can't handle a change as big as that overnight.

 PE> This is the first time I've heard anybody say that my origin line (or
 PE> the  origin line generated by the Xenia Mailer reader, and no doubt
 PE> numerous  other mail creation software, for that matter) is
 PE> technically invalid, I'd  like to know why.  :-)

 PE> If you can understand why whacking {at}fidonet onto the end of the INTL
 PE> line is not the correct way to solve cross-domain netmail (instead of
 PE> having to come up with the DOMAIN kludge), you understand perfectly my
 PE> argument. I expect you to understand my argument, but I don't expect
 PE> you to agree. Hector doesn't
 PE> understand that a CRC is a bad serial number either.  Who is
 PE> technically correct in both of these arguments is a different matter.
 PE> BFN.  Paul.
 PE> @EOT:

Andrew Clarke

--- Zeus BBS 1.1
* Origin: Metnet-10 lines bbs. Free Internet-web/ftp. 01482 442251 (2:2502/129.0)
SEEN-BY: 13/13 37/100 50/99 102/735 105/103 119/88 129/11 138/146 153/800 920
SEEN-BY: 157/586 200/204 201/505 203/512 992 204/200 209/720 7211 239/1
SEEN-BY: 260/742 261/1137 270/101 102 103 104 211 272/160 280/1 801 282/4073
SEEN-BY: 283/657 292/511 876 320/119 321/1 332/1 334/201 341/70 1002 344/3
SEEN-BY: 345/12 348/105 362/37 367/1 385/100 387/31 396/1 402/311 403/150
SEEN-BY: 405/0 406/100 430/105 440/1 600/348 620/243 626/660 632/348 640/206
SEEN-BY: 640/305 820 821 822 823 700/101 711/409 410 413 430 808 809 934
SEEN-BY: 712/515 713/317 724/10 800/1 2002/2002 2430/1423 2433/225 2601/100
SEEN-BY: 2602/100 2604/104 2613/5 2624/306 2630/1001 3401/308 3611/18 3615/7
SEEN-BY: 3615/50 3838/1 7104/2
@PATH: 2502/129 1000 442/403 255/1 250/107 254/153 106/2000 396/1 270/101
@PATH: 209/720 640/820 711/409 808 934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.