Re: Reply on Semi MAJOR (was Comments on Multicast Draft)
James Watt <james@newbridge.com> Mon, 25 September 1995 23:18 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20435;
25 Sep 95 19:18 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa20431;
25 Sep 95 19:18 EDT
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.97.5]) by
guelah.nexen.com (8.6.12/8.6.12) with ESMTP id SAA27146;
Mon, 25 Sep 1995 18:56:54 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id
SAA08881 for rolc-out; Mon, 25 Sep 1995 18:58:28 -0400
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 SAA08871 for
<rolc@nexen.com>; Mon, 25 Sep 1995 18:58:21 -0400
Received: from ns.newbridge.com (ns.Newbridge.Com [192.75.23.67]) by
nexen.nexen.com (8.6.12/8.6.12) with ESMTP id SAA29982 for <rolc@nexen.com>;
Mon, 25 Sep 1995 18:58:19 -0400
Received: (from adm@localhost) by ns.newbridge.com (8.6.12/8.6.12) id SAA24596;
Mon, 25 Sep 1995 18:53:31 -0400
Received: from portero(192.75.23.66) by ns via smap (V1.3)
id sma024573; Mon Sep 25 18:53:08 1995
Received: from thor.ca.Newbridge.com (thor.ca.newbridge.com [138.120.100.14])
by kanmaster.ca.newbridge.com (8.6.12/8.6.12) with SMTP id SAA26150;
Mon, 25 Sep 1995 18:53:07 -0400
Received: from fields.newbridge by thor.ca.Newbridge.com (4.1/SMI-4.0)
id AA05332; Mon, 25 Sep 95 18:53:06 EDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: James Watt <james@newbridge.com>
Message-Id: <9509252253.AA05332@thor.ca.Newbridge.com>
Subject: Re: Reply on Semi MAJOR (was Comments on Multicast Draft)
To: Grenville Armitage <gja@thumper.bellcore.com>
Date: Mon, 25 Sep 1995 18:53:06 -0400 (EDT)
Cc: jhalpern@ca.newbridge.com, ip-atm@matmos.hpl.hp.com,
gja@thumper.bellcore.com, rolc@nexen.com
In-Reply-To: <199509242150.RAA17404@thumper.bellcore.com> from "Grenville
Armitage" at Sep 24, 95 05:50:24 pm
X-Mailer: ELM [version 2.4 PL22]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1446
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/
Grenville Armitage writes: +----------- | ... edited version of an exchange between Joel and Grenville ... |>> |>> If we consider that MARS is supposed to be a Multi-Protocol |>> mechanism, then the pkt$pro mechanism seems quite awkward. Any |>> protocol that does not have an Ethertype needs to be "defined" |>> to have some other value. If we used a different ID space, |>> we could avoid this problem. | | ... | |Taking off my artificial "IETF only" blinkers for a moment I could |suggest that one solution would be for the IP-ATM working group |to pre-delegate part of the ar$pro space to a group we know is hoping |to interoperate (and who _will_ attempt to apply this spec to a |non-ethertype protocol of interest): | |e.g. new text: | | 0x0000 to 0x03FF Reserved for future use by the IETF. | 0x0400 to 0x05FF Designated for use by the ATM Forum. | 0x0600 to 0xFFFF Protocols defined by the equivalent Ethertypes. +------ Or what about biting the bullet and using 6 bytes: one for an NLPID and 5 for the rest (e.g. SNAP when the NLPID = 80). This should be enough to cover anything and everything. While I think of it, this applies to NHRP too... Regards, Comments ? -james ____________________________________________________________________________ James W. Watt, james@newbridge.com Ph: +1 613 591-3600 Newbridge Networks 600 March Rd Kanata ON Canada K2K 2E6 FAX:+1 613 591-3680