Re: comments on forward and reverse transit nhs record extensions.

"Eric W. Gray" <gray@ctron.com> Mon, 20 May 1996 13:47 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa12865; 20 May 96 9:47 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa12859; 20 May 96 9:47 EDT
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.97.5]) by guelah.nexen.com (8.7.3/8.7.3) with ESMTP id JAA07621; Mon, 20 May 1996 09:42:15 -0400 (EDT)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id JAA23145 for rolc-out; Mon, 20 May 1996 09:30:35 -0400 (EDT)
Received: from guelah.nexen.com (guelah.nexen.com [204.249.96.19]) by maelstrom.nexen.com (8.7.3/8.7.3) with ESMTP id JAA23136 for <rolc@nexen.com>; Mon, 20 May 1996 09:30:32 -0400 (EDT)
Received: from gatekeeper.ctron.com (ctron.com [134.141.197.25]) by guelah.nexen.com (8.7.3/8.7.3) with SMTP id JAA07562 for <rolc@nexen.com>; Mon, 20 May 1996 09:30:31 -0400 (EDT)
Received: (from news@localhost) by gatekeeper.ctron.com (8.6.12/8.6.9) id JAA18960; Mon, 20 May 1996 09:30:51 -0400
Received: from stealth.ctron.com(134.141.5.107) by gatekeeper via smap (V1.3mjr) id sma018913; Mon May 20 09:30:24 1996
Received: from olympus.ctron.com by stealth.ctron.com (4.1/SMI-4.1) id AA03420; Mon, 20 May 96 09:21:50 EDT
Received: from blarney (blarney.ctron.com [134.141.66.40]) by olympus.ctron.com (8.6.12/8.6.9) with ESMTP id JAA06205; Mon, 20 May 1996 09:29:15 -0400
Received: from blarney by blarney via SMTP (940816.SGI.8.6.9/930416.SGI) id JAA03067; Mon, 20 May 1996 09:30:12 -0400
Message-Id: <31A073E0.167E@ctron.com>
Date: Mon, 20 May 1996 09:30:08 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Eric W. Gray" <gray@ctron.com>
Organization: Cabletron Systems, Inc.
X-Mailer: Mozilla 2.0 (X11; I; IRIX 5.3 IP12)
Mime-Version: 1.0
To: Rajesh Varadarajan <rvaradar@fore.com>
Cc: rolc@nexen.com
Subject: Re: comments on forward and reverse transit nhs record extensions.
References: <199605162210.SAA23806@dolphin.fore.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Orig-Sender: owner-rolc@nexen.com
Precedence: bulk
X-Info: [Un]Subscribe to rolc-request@nexen.com, submissions to rolc@nexen.com
X-Info: Email archive at ftp://ietf.cnri.reston.va.us/ietf-mail-archive/rolc/
X-Info: Hypermail archive at http://cell-relay.indiana.edu/mail/archives/rolc/
X-Info: FTP archive at ftp://ftp.nexen.com/pub/rolc/

Rajesh,

	As it is now, only Vendor Private Extensions are allowed to be
repeated (and that mostly because VPEs may be added by devices made by
different vendors in the same query/response path).  This makes for a
significant simplification for most extensions because once you have
hadnled it, you can forget it.

	Are you sure that the "simplification" you seek is worth the 
complexity it adds?

--
Eric Gray

You wrote:
> 
> jim,
> 
>         I'm not sure if this has been discussed before here goes anyway...
> 
>         In the forward and reverse transit record extensions, it is required
> for transit NHS's to append a forward/reverse transit element at the end of the
> set of elements already existing in the extension.
> 
>         This would require transit NHS's to insert their data into NHRP packets
> being forwarded (i.e. other extension data  might exist after this one). It would
> be nicer if multiple occurences of the forward/reverse record extensions were
> allowed to be in the NHRP packet rather that having the elements to be inserted
> at the end of the extension. (i.e., each forward/reverse record extension will
> have the one forward/reverse record element).
> 
> Thanks,
> rajesh