MACRO usage in the WEP documents

Urs Eppenberger <Eppenberger@switch.ch> Mon, 01 June 1992 10:16 UTC

X400-Received: by mta mhs-relay.cs.wisc.edu in /PRMD=XNREN/ADMD= /C=US/; Relayed; Mon, 1 Jun 1992 05:23:11 +0000
Date: Mon, 01 Jun 1992 05:23:11 +0000
X400-Originator: cargille@cs.wisc.edu
X400-Recipients: non-disclosure:;
X400-MTS-Identifier: [/PRMD=XNREN/ADMD= /C=US/; mhs-relay..586:01.05.92.10.23.11]
Priority: Non-Urgent
DL-Expansion-History: ietf-osi-x400ops@cs.wisc.edu ; Mon, 1 Jun 1992 05:23:11 +0000;
From: Urs Eppenberger <Eppenberger@switch.ch>
Message-ID: <459*/S=Eppenberger/O=switch/PRMD=SWITCH/ADMD=ARCOM/C=CH/@MHS>
To: ietf-osi-x400ops <ietf-osi-x400ops@cs.wisc.edu>, rd-mhs-managers <rd-mhs-managers@cosine-mhs.switch.ch>
Subject: MACRO usage in the WEP documents

Dear colleagues,

I'm extending the routing document with the few additional comments I gor
since the last IETF meeting in San Diego.
-> support for a local domain always routed through the WEP
   (for echo, nosuchuser and routing tests)
-> Add a hook in the community documents for flexible extensions of the
   WEP and DOMAIN documents.
-> Add support for MACROS for the connection information

The first item was already well received and it's very easy.

The second one looks nice. It will complicate heavily the generation of
checking tools. Is it worth the effort or are we satisfied with the
functionality provided in the current specifiaction?

The third one has a minimum and a more flexible solution.
HTA proposed to define a limited set of macros in the routing document.
SHK proposed to distribute macro definitions in a separate file.
Any comments to the two proposals?

Many thanks for your help.

Kind regards,

Urs.

MACRO usage in the WEP documents Urs Eppenberger
Re: MACRO usage in the WEP documents Allan Cargille
Re: MACRO usage in the WEP documents Allan Cargille