Re: Multicast in draft version 5 comments

[James Watt <[e-mail]>]

Folks:
  Dlcmi looks too much like Dlci for my over-rested eyes. Now that I'm
unconfused:

1) frDlcmiMulticast was in RFC 1315 (and was read-write there) and
   doesn't need any changes.  It basically tells you whether the 
   attached network can be assumed to be able to do non-unicast VCs.

2) frCircuitMulticast was added this time round and is a per-VC
   object that tells you what the _particular_ VC will do with a frame.

   Alan's proposal is to make this new object match reality, viz:
	a) have values for unicast, p2mp and mp2mp (did I forget one ?) and
        b) have a MAX-ACCESS of read-write.

   As Fred pointed out, if a given DTE doesn't want to use anything but
   unicast, it can use the WRITE-SYNTAX clause to shrink the valid range.

   I suppose we should add a refeference clause pointing to the appropriate
   section of the document that defines the FR multicast support so other
   folks can figure out why this got done.

Did I miss anything ?  If not, this sounds like a reasonable change.

Regards,
-james

ps I seem to have misplaced Alan's message with the updated object
   definition ready for Caralyn to cut and paste...
____________________________________________________________________________
James W. Watt,     [e-mail]                   Ph: [phone]
Newbridge Networks 600 March Rd Kanata ON Canada K2K 2E6 FAX:[phone]