IETF Logo Mail Archive

Re: changes in draft-ietf-ippcp-protocol-04.txt

Naganand Doraswamy <naganand@BayNetworks.COM> Wed, 17 December 1997 16:31 UTC

Return-Path: naganand@BayNetworks.COM
Received: from puli.cisco.com (puli.cisco.com [171.69.1.174]) by ftp-eng.cisco.com (8.8.5-Cisco.1/8.6.5) with SMTP id IAA29070 for <ippcp-archive-file@ftp-eng.cisco.com>; Wed, 17 Dec 1997 08:31:58 -0800 (PST)
Received: from hubbub.cisco.com (mailgate-sj-1.cisco.com [198.92.30.31]) by puli.cisco.com (8.6.12/8.6.5) with ESMTP id IAA19595 for <extdom.ippcp@aliashost.cisco.com>; Wed, 17 Dec 1997 08:31:28 -0800
Received: from proxy1.cisco.com (proxy1.cisco.com [192.31.7.88]) by hubbub.cisco.com (8.8.4-Cisco.1/CISCO.GATE.1.1) with ESMTP id IAA19487 for <ippcp@external.cisco.com>; Wed, 17 Dec 1997 08:30:45 -0800 (PST)
Received: (from smap@localhost) by proxy1.cisco.com (8.8.7/8.8.5) id IAA23438 for <ippcp@external.cisco.com>; Wed, 17 Dec 1997 08:30:44 -0800 (PST)
Received: from ns1.baynetworks.com(134.177.3.20) by proxy1.cisco.com via smap (V2.0) id xma023428; Wed, 17 Dec 97 16:30:40 GMT
Received: from mailhost.BayNetworks.COM (screen2r.BayNetworks.COM [134.177.3.1]) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id IAA19948; Wed, 17 Dec 1997 08:20:33 -0800 (PST)
Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id IAA21295; Wed, 17 Dec 1997 08:20:33 -0800 (PST)
Received: from span.engeast (span [192.32.243.28]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with SMTP id LAA19250; Wed, 17 Dec 1997 11:20:32 -0500 for
Received: from span (localhost) by span.engeast (4.1/SMI-4.1) id AA02890; Wed, 17 Dec 97 11:24:56 EST
Sender: naganand@BayNetworks.COM
Message-Id: <3497FCD8.500F9F30@baynetworks.com>
Date: Wed, 17 Dec 1997 11:24:56 -0500
From: Naganand Doraswamy <naganand@BayNetworks.COM>
X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 4.1.4 sun4m)
Mime-Version: 1.0
To: Avram Shacham <shacham@cisco.com>
Cc: ippcp@external.cisco.com
Subject: Re: changes in draft-ietf-ippcp-protocol-04.txt
References: <2.2.32.19971216224535.00715a34@pita.cisco.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Avram,

I am little bit confused about the usage of CPI in the new draft. The
receiver allocates the CPI and it has to unique. Now we can say the
uniqueness is based on the tuple <src, dst, protocol, CPI> in which case
things work fine. However, if the uniqueness is based just on <dst,
protocol, CPI> then the receiving host (which is <dst> above) will not
be able to use the same CPI for two hosts A and B.

Thanks,
 
--Naganand

---------------------------------------------------------------

Naganand Doraswamy		(508)916-1323 (O)				
Bay Architecture Lab		(508)670-8153 (F)
Bay Networks, Inc.
3 Federal St, BL3-04
Billerica, MA 01821

v2.23.0 | Report a Bug | By Email