I dissent - WEP/RELAY terminology needs to be aligned
Urs Eppenberger <Eppenberger@switch.ch> Fri, 19 March 1993 13:29 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01323; 19 Mar 93 8:29 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id ac01279; 19 Mar 93 8:29 EST
Received: from mhs-relay.cs.wisc.edu by CNRI.Reston.VA.US id aa11360; 19 Mar 93 2:35 EST
X400-Received: by mta mhs-relay.cs.wisc.edu in /PRMD=XNREN/ADMD= /C=US/; Relayed; Fri, 19 Mar 1993 01:24:25 +0000
Date: Fri, 19 Mar 1993 01:24:25 +0000
X400-Originator: cargille@cs.wisc.edu
X400-Recipients: non-disclosure:;
X400-MTS-Identifier: [/PRMD=XNREN/ADMD= /C=US/; mhs-relay..982:19.02.93.07.24.25]
Priority: Non-Urgent
DL-Expansion-History: ietf-osi-x400ops@cs.wisc.edu ; Fri, 19 Mar 1993 01:24:24 +0000;
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Urs Eppenberger <Eppenberger@switch.ch>
Message-ID: <1214*/S=Eppenberger/O=switch/PRMD=SWITCH/ADMD=ARCOM/C=CH/@MHS>
To: Allan Cargille <Allan.Cargille@cs.wisc.edu>
Cc: wg-msg <wg-msg@rare.nl>, ietf-osi-x400ops <ietf-osi-x400ops@cs.wisc.edu>
In-Reply-To: <930318165911*/S=O/O=switch/PRMD=SWITCH/ADMD=ARCOM/C=CH/@MHS>
Subject: I dissent - WEP/RELAY terminology needs to be aligned
> From: Allan Cargille <S=Cargille;G=Allan;OU=cs;O=uw-madison;P=xnren;C=us> > To: <S=EPPENBERGER;OU=VERW;O=SWITCH;P=SWITCH;A=ARCOM;C=CH>, > <S=huizer;G=Erik;O=surfnet;P=surf;A=400net;C=nl>, > <S=Hansen;G=Alf;OU=Delab;O=Sintef;P=uninett;C=no>, > <S=Alvestrand;G=Harald;OU=delab;O=sintef;P=uninett;C=no> > Cc: Allan C. <S=Cargille;G=Allan;OU=cs;O=uw-madison;P=xnren;C=US>, > <S=wg-msg;O=RARE;P=surf;A=400net;C=nl>, > <S=ietf-osi-x400ops;OU=cs;O=uw-madison;P=xnren;C=us> > Subject: I dissent - WEP/RELAY terminology needs to be aligned Even if I receive the message three times, I do still not agree. > Hello everyone, > > I am very unhappy that Alf's PRMD Requirements document and Urs' > Routing document are both being progressed with different terminology > for "well-known MTAs that serve X.400 domains." I do not feel that > there is consensus on this issue. I feel strongly that it is > technically defective to advance them with different names. ^^^^^^^^^^^ the name of a document type has no technical evidence at all. > > Alf's paper uses the traditional name "WEP". Urs' paper uses the more > generic term "RELAY". Alf's paper is about the GO-MHS community. Mine is generic. It is very important to make this difference. > As I have stated in the past, I prefer the term WEP because, although > cryptic, it is specific. The word "RELAY" is used for application ^^^^^^^^ this is exactly why I do not want to use it in the generic routing document definition > relays, transport relays, SMTP mail relays, and gateways of all kinds. > Therefore I continue to vote for the term WEP. If the community feels > that it is important to use a term other than WEP, I would suggest > something more descriptive than RELAY. I would vote for a two-word > key such as RELAY-MTA, or HUB-MTA. > > However, once again, I do not think it is critical *whatever* they are > called. I just think it is a horrible (alleged) "solution" to advance > the two documents with different terms for the same thing. I have not > heard anyone other than Urs (no offense intended, Urs) agree that it > makes sense to advance them with different names. I would like to hear somebody who is not in the GO-MHS community, because he would have a somwhat neutral opinion on that. tired, Urs.
- I dissent - WEP/RELAY terminology needs to be ali… Allan Cargille
- I dissent - WEP/RELAY terminology needs to be ali… Urs Eppenberger
- Re: I dissent - WEP/RELAY terminology needs to be… Marko.Kaittola