Re: MARS last call: packet formats

Grenville Armitage <gja@thumper.bellcore.com> Sat, 04 November 1995 00:41 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00393; 3 Nov 95 19:41 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa00389; 3 Nov 95 19:41 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 TAA14494; Fri, 3 Nov 1995 19:15:19 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id TAA02888 for rolc-out; Fri, 3 Nov 1995 19:24:46 -0500
Received: from guelah.nexen.com (guelah.nexen.com [204.249.96.19]) by maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id TAA02876 for <rolc@nexen.com>; Fri, 3 Nov 1995 19:24:43 -0500
Received: from thumper.bellcore.com (thumper.bellcore.com [128.96.41.1]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id TAA14482 for <rolc@nexen.com>; Fri, 3 Nov 1995 19:11:37 -0500
Received: from thumper (localhost [127.0.0.1]) by thumper.bellcore.com (8.6.9/8.6.10) with ESMTP id TAA17907; Fri, 3 Nov 1995 19:20:04 -0500
Message-Id: <199511040020.TAA17907@thumper.bellcore.com>
To: James Watt <james@ca.newbridge.com>
cc: ip-atm@matmos.hpl.hp.com, rolc@nexen.com, gja@thumper.bellcore.com
Subject: Re: MARS last call: packet formats
In-reply-to: Your message of Fri, 03 Nov 1995 18:46:25 -0500. <199511032346.SAA11839@thor.ca.newbridge.com>
Date: Fri, 03 Nov 1995 19:20:00 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Grenville Armitage <gja@thumper.bellcore.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/

[James wrote...]
>>A couple of questions:
>>1) is there anyone that believes we need 2 packet formats ?
>>2) what is the most expedient way to converge on a single packet format ?

People contemplating question (2) may be interested in this
text I tossed together last week:

http://gump.bellcore.com:8000/~gja/ipatm-ipmc/nhrp-to-mars-v2

It provides examples of NHRP messages (as they stood in the
published nhrp-04.txt ID) morf'd into close functional/semantic
equivalents based on the generic control message structure
in ipmc-08.

As a disclaimer, it does not represent any changes that may have
been wrought on NHRP during the last few weeks of discussions.
However, the basic principle stands, and any modifications can
be similarly represented in the morf'd form.

As a further disclaimer, this does not in any way merge the
functions, scopes, or roles of the respective (MARS and NHRP)
protocols. It simply provides a common platform for representing
protocol types, protocol addresses, NBMA/'hardware' addresses,
and extensions lists.

cheers,
gja
_________________________________________________________________________
Grenville Armitage, Research Scientist,      MRE 2P-255, 445 South Street
Internetworking Research Group, Bellcore.      Morristown, NJ, 07960, USA
(email) gja@thumper.bellcore.com  (voice) +1 201 829 2635 {.. 2504 (fax)}
        (www) http://gump.bellcore.com:8000/~gja/home.html