comments on forward and reverse transit nhs record extensions.
Rajesh Varadarajan <rvaradar@fore.com> Thu, 16 May 1996 22:30 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa26923; 16 May 96 18:30 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa26918; 16 May 96 18:30 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 SAA26368; Thu, 16 May 1996 18:23:47 -0400 (EDT)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id SAA12473 for rolc-out; Thu, 16 May 1996 18:10:46 -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 SAA12464 for <rolc@nexen.com>; Thu, 16 May 1996 18:10:41 -0400 (EDT)
Received: from fore.com (mailhub.fore.com [192.88.243.4]) by guelah.nexen.com (8.7.3/8.7.3) with ESMTP id SAA26282 for <rolc@nexen.com>; Thu, 16 May 1996 18:10:39 -0400 (EDT)
Received: from dolphin.fore.com ([192.88.243.27]) by fore.com (8.7.3/8.6.11) with ESMTP id SAA27995 for <rolc@nexen.com>; Thu, 16 May 1996 18:07:25 -0400 (EDT)
Received: from dcdolphin.dc.fore.com ([198.29.27.59]) by dolphin.fore.com (8.7.3/3.4W4) with ESMTP id SAA23806 for <rolc@nexen.com>; Thu, 16 May 1996 18:10:33 -0400 (EDT)
Message-Id: <199605162210.SAA23806@dolphin.fore.com>
To: rolc@nexen.com
Subject: comments on forward and reverse transit nhs record extensions.
Date: Thu, 16 May 1996 18:14:53 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Rajesh Varadarajan <rvaradar@fore.com>
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/
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
- comments on forward and reverse transit nhs recor… Rajesh Varadarajan
- Re: comments on forward and reverse transit nhs r… Eric W. Gray