Re: multilateral agreements

"Harald T. Alvestrand" <Harald.T.Alvestrand@uninett.no> Mon, 07 March 1994 09:08 UTC

To: "Kevin E. Jordan" <Kevin.E.Jordan@cdc.com>
cc: mhs-ds@mercury.udev.cdc.com
Subject: Re: multilateral agreements
In-reply-to: Your message of "Thu, 03 Mar 1994 09:02:58 CST." <2d75fc2347f9002@mercury.udev.cdc.com>
Date: Mon, 07 Mar 1994 09:51:19 +0100
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Harald T. Alvestrand" <Harald.T.Alvestrand@uninett.no>
Message-Id: <2d7aeb24232e002@zeus.cdc.com>

Kevin,
there is a problem with changing the syntax of the existing
BilateralTable attribute: I can't find it.
Figure 7 of chap 18 gives the OBJECT CLASS of the
mtaBilateralTableEntry, and the text points to the "bilateralTable"
entry which is defined in figure 18.

Figure 18 is a set of object identifier assignments; the
at-bilateral-table is assigned there.

Since this text is not in the document (?????, Steve????),
I think the simplest change would be to put into it
(forgive my bad ASN.1 :-)

bilateralTable ATTRIBUTE
   WITH ATTRIBUTE-SYNTAX DistinguishedName
   MULTI VALUE
   ::= at-bilateral-table

That would give anyone enough information to find both the
truly private table and any shared ones.
The only disadvantage I can see is that it cannot impose
sequencing on the access to the tables (same argument as goes
with the routingTreeList attribute).

What do you think? Does it break existing code?

                    Harald A

multilateral agreements Kevin E. Jordan
Re: multilateral agreements Harald T. Alvestrand