New title for "Re: MARS last call: packet formats (fwd)"

Andrew Smith <asmith@baynetworks.com> Wed, 15 November 1995 05:58 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06820; 15 Nov 95 0:58 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa06815; 15 Nov 95 0:58 EST
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id AAA09268; Wed, 15 Nov 1995 00:30:08 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id AAA02190 for rolc-out; Wed, 15 Nov 1995 00:43:56 -0500
Received: from nexen.nexen.com (nexen.nexen.com [204.249.96.18]) by maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id AAA02181; Wed, 15 Nov 1995 00:43:53 -0500
Received: from lightning.synoptics.com (lightning.synoptics.com [134.177.3.18]) by nexen.nexen.com (8.6.12/8.6.12) with SMTP id AAA27671; Wed, 15 Nov 1995 00:41:20 -0500
Received: from pobox.synoptics.com ([134.177.1.95]) by lightning.synoptics.com (4.1/SMI-4.1) id AA02307; Tue, 14 Nov 95 21:37:47 PST
Received: from milliways-le0.engwest (milliways-le0.synoptics.com) by pobox.synoptics.com (4.1/SMI-4.1) id AA07474; Tue, 14 Nov 95 21:39:12 PST
Received: by milliways-le0.engwest (4.1/SMI-4.1) id AA09432; Tue, 14 Nov 95 21:39:10 PST
Date: Tue, 14 Nov 95 21:39:10 PST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Andrew Smith <asmith@baynetworks.com>
Message-Id: <9511150539.AA09432@milliways-le0.engwest>
To: yakov@cisco.com, luciani@nexen.com
Subject: New title for "Re: MARS last call: packet formats (fwd)"
Cc: rolc@nexen.com
X-Orig-Sender: owner-rolc@nexen.com
Precedence: bulk
X-Info: Submissions to rolc@nexen.com
X-Info: [Un]Subscribe requests to rolc-request@nexen.com
X-Info: Archives for rolc via ftp://ietf.cnri.reston.va.us/ietf-mail-archive/rolc/

OK, OK, break it up you guys. The party's over: last call finished Monday.
You can't discuss this subject any more unless you change the title. You'll 
have to find a new "Subject:" for this thread.

> Yakov,
> 
> > > on a single packet format for both NHRP and IP-MC.  I would welcome more
> > > comments from the group as to:
> > > 
> > > a) whether or not this is desireable and
> > 
> > It certainly would be nice to have this as a goal.
> > 
> > > b) how we should get to a single format.
> > 
> > IMHO as a first step we should settle on a single format for the
> > Registration message. If other folks think this is a reasonable first
> > step, then I'd like to get some feedback on whether it would be
> > reasonable to use the IP-MC packet format for registering both
> > multicast and unicast addresses.
> 
> I disagree.  I do not want to see different packet types

etc. etc. etc.  :-)


Andrew

********************************************************************************
Andrew Smith					TEL:	+1 408 764 1574
Technology Synergy Unit				FAX:	+1 408 988 5525
Bay Networks, Inc.				E-m:	asmith@baynetworks.com
Santa Clara, CA
********************************************************************************