The IP over ATM Mailing List Archive by date[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] ipmc-07.txt
Jim, I'm just sorting out my mail-log from the ipmc-07 last call and noticed that I'd failed to conclude this thread between us. (the thread is appended). I'd actually modify your suggested text a little further: "Except as described in section 6.2.4, after performing any required database updates non-registration MARS_JOIN and MARS_LEAVE messages are retransmitted on ClusterControlVC. The following fields are modified just prior to retransmission: - ar$flags.copy is set to 1. - ar$msn is set to the current Cluster Sequence Number for ClusterControlVC (Section 5.1.4.2). The MARS retransmits MARS_JOIN and MARS_LEAVE messages even if they resulted in no change to the database." Does this seem ok? cheers, gja >>Yes, the problem is "exactly as they arrived". >>Does something like this make any sense... >> >>"Except as described in section 6.2.4 and after performing >>any required database updates, non-registration MARS_JOIN >>and MARS_LEAVE messages are retransmitted on ClusterControlVC >>with ar$flags.copy set to 1". >> >>I believe this may be better because it does not imply that >>the ONLY change to the message is the variable ar$flags.copy. >> >>Jim Rubas. >> >>========================================================================= >>Received: from thumper.bellcore.com by watson.ibm.com (IBM VM SMTP V2R3) >> with TCP; Wed, 27 Sep 95 23:25:18 EDT >>Received: from thumper (localhost [127.0.0.1]) by thumper.bellcore.com (8.6.9 /8.6.10) with ESMTP id XAA21347; Wed, 27 Sep 1995 >>23:24:55 -0400 >>Message-Id: <199509280324.XAA21347@thumper.bellcore.com> >>To: rubas@watson.ibm.com >>cc: ip-atm@matmos.hpl.hp.com, gja@thumper.bellcore.com >>Subject: Re: ipmc-07.txt >>In-reply-to: Your message of Wed, 27 Sep 1995 15:19:32 -0400. >> <199509271930.AA089570258@matmos.hpl.hp.com> >>Date: Wed, 27 Sep 1995 23:24:54 -0400 >>From: Grenville Armitage <gja@thumper.bellcore.com> >> >> >>Jim, >> >>Are you referring to the fact that one para says "..exactly >>as they arrived.." and the other says we modify the ar$msn >>field as the MARS_JOIN/LEAVE passes through? Any text that >>would be clearer? >> >>>>Section 6.1.2 states: >>>>"Except as described in section 6.2.4, non-registration >>>>MARS_JOIN and MARS_LEAVE messages are retransmitted on >>>>ClusterControlVC exactly as they arrived (although with >>>>ar$flags.copy set to 1), after performing any required >>>>database updates". >>>> >>>>However, Section 5.1.4.2 states: >>>>"The current CSN is copied into the ar$msn field of MARS >>>>messages being sent to cluster members, whether out >>>>ClusterControlVC or on an point to point VC". >> >>thanks, >>gja |
|