RE: [Tsvwg] End point and association Address conflict

"Balani, Sandeep" <s_balani@trillium.com> Fri, 26 April 2002 17:29 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13931 for <tsvwg-archive@odin.ietf.org>; Fri, 26 Apr 2002 13:29:48 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id NAA08026 for tsvwg-archive@odin.ietf.org; Fri, 26 Apr 2002 13:29:50 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA26655; Fri, 26 Apr 2002 13:07:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA26624 for <tsvwg@ns.ietf.org>; Fri, 26 Apr 2002 13:07:17 -0400 (EDT)
Received: from caduceus.fm.intel.com (fmr02.intel.com [192.55.52.25]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10966 for <tsvwg@ietf.org>; Fri, 26 Apr 2002 13:07:12 -0400 (EDT)
Received: from talaria.fm.intel.com (talaria.fm.intel.com [10.1.192.39]) by caduceus.fm.intel.com (8.11.6/8.11.6/d: outer.mc, v 1.41 2002/04/22 23:29:17 root Exp $) with ESMTP id g3QH6IT07698 for <tsvwg@ietf.org>; Fri, 26 Apr 2002 17:06:18 GMT
Received: from fmsmsxvs042.fm.intel.com (fmsmsxv042-1.fm.intel.com [132.233.48.110]) by talaria.fm.intel.com (8.11.6/8.11.6/d: inner.mc, v 1.16 2002/04/15 17:47:00 root Exp $) with SMTP id g3QH9JU20720 for <tsvwg@ietf.org>; Fri, 26 Apr 2002 17:09:19 GMT
Received: from FMSMSX018.fm.intel.com ([132.233.42.197]) by fmsmsxvs042.fm.intel.com (NAVGW 2.5.1.16) with SMTP id M2002042610111312263 ; Fri, 26 Apr 2002 10:11:14 -0700
Received: by fmsmsx018.fm.intel.com with Internet Mail Service (5.5.2653.19) id <2WWTMZLX>; Fri, 26 Apr 2002 10:06:59 -0700
Message-ID: <F1CE15E08172D4119247009027AE9D50191173A6@FMSMSX37>
From: "Balani, Sandeep" <s_balani@trillium.com>
To: 'Randall Stewart' <randall@stewart.chicago.il.us>, "Balani, Sandeep" <s_balani@trillium.com>
Cc: Ivan.Arias-Rodriguez@nokia.com, qxie1@email.mot.com, "Khan, Mohammad" <mo_khan@trillium.com>, tsvwg@ietf.org
Subject: RE: [Tsvwg] End point and association Address conflict
Date: Fri, 26 Apr 2002 10:06:48 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: tsvwg-admin@ietf.org
Errors-To: tsvwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Transport Area Working Group <tsvwg.ietf.org>
X-BeenThere: tsvwg@ietf.org

my comments..

-----Original Message-----
From: Randall Stewart [mailto:randall@stewart.chicago.il.us]
Sent: Friday, April 26, 2002 9:45 AM
To: Balani, Sandeep
Cc: Ivan.Arias-Rodriguez@nokia.com; qxie1@email.mot.com; Khan, Mohammad;
tsvwg@ietf.org
Subject: Re: [Tsvwg] End point and association Address conflict


"Balani, Sandeep" wrote:
> 
> Hi All,
>   My comments inline...
> 
> -sandeep
> 
> -----Original Message-----
> From: Randall Stewart [mailto:randall@stewart.chicago.il.us]
> Sent: Friday, April 26, 2002 6:31 AM
> To: Ivan.Arias-Rodriguez@nokia.com
> Cc: s_balani@trillium.com; qxie1@email.mot.com; mo_khan@trillium.com;
> tsvwg@ietf.org
> Subject: Re: [Tsvwg] End point and association Address conflict
> 
> Ivan.Arias-Rodriguez@nokia.com wrote:
> >
> >         Hi Sandeep!
> >
> >         See my comment inline...
> >
> > > hi all,
> > >
> > > My comments inline,
> > >
> > >
> > >       Randy, see my comment inline...
> > >
> > > > Ivan.Arias-Rodriguez@nokia.com wrote:
> > > > >
> > > > >         Hi all!
> > > > >
> > > > >         Well, now I realized that I had a somehow different
> > > > view about what was a legal addition... thanks for your comments.
> > > > >
> > > > >         Now I have another doubt... Imagine that we have an
> > > > endpoint E1 with addresses IPa, IPb and port 1. We have an
> > > > association A1 that only uses IPa, whose peer is IPz and port
> > > > 65535. Thus the association A1 can be represented as [(IPa;
> > > > Port1), (IPz; Port 65535)]. What happens now if we receive an
> > > > INIT from IPz/65535 directed to IPb/1?
> > > >
> > > > A question...
> > > >
> > > > Why did you not include IPb in the INIT or INIT-ACK that
> > > setup A1. You
> > > > are
> > > > supposed to tell the peer of all your addresses that are
> > > bound to your
> > > > endpoint. I think this is the big flaw in your question..
> > >
> > >       I did, but later on I deleted it using the AddIP
> > > extension... :-) So
> > > now I don't use it anymore...
> > >
> > > [ sandeep ] I think this is very interesting proble :-)
> > >  What i think we can do is When u are doing DELETEIP for IPb, If no
> > > association is using IPb as source address we should remover IPb from
> > > Endpoint E1. This way we will not have any such problem.
> > >
> > > What do u think ????
> >
> >         No, I don't think this is a good solution... Remember that there
> can be >many associations in that endpoint, and that they might be using
IPb
> as A1 did >>once... I don't think you can erase that address from the
> endpoint...
> 
> Hmm.. maybe the real solution is you MUST NOT use the DELETE unless
> you are also deleting it from the endpoint.
> 
> So... if you do a DELETE IP-B you MUST first delete it from the
> endpoint. Then you MAY delete it from any association... ones you
> don't delete it from will have to have a variant list of addresses
> that it has ...
> 
> That way everything still works for those that DO NOT delete IP-B and
> your problem goes away...
> 
> Of course your problem STILL exists when you HOT-PLUG in a card
> and have an existing association and NO ADD-IP extension...
> 
> [ Sandeep ]   Can we delete an IP address from an Endpoint first & then
> delete It from Association. According  to the procedure, Between the time
we
> have send ASCONF( Delete IPb) & the time we receive ASCONF-ACK(Delete IPb)
> we should accept all packets destined to IPb ????
> 

I would think it would be ok.. remember the Endpoint is only
used for basic things like new assocaitions... the actual
"what addresses are in the association" can be kept in association
specific instances...

[ Sandeep ] I probably don't understand this point.  But i don't agree with
this 100%.  
This may be very implemenataion specific but For all incoming DATAGRAM i
should check if the Endpoint exist or Not, If Endpoint does not exist i will
not proceed .. So in case i deleted the IPb Address from the Endpoint, I
will never be able to accept the packet for that association which has IPb
in its source address. 

Moreover i think that its illegal to have a Source Address not present in
Endpoint & present in Association ( if that's the case ) ???  


> Also deleting an IP address from an Endpoint means, Deleting it from
> multiple associations simultaneously ( Or One-By-One ) , What if on One
> association  this DeleteIP procedure fails ???

Well.. I don't see an issue.. so you are stuck with a deleted IP address
in your assocaition. 

A) Chances are you won't receive packets on it (since it is off the
   machine).

B) If it is NOT off the machine your code STILL should work in that
   it had better be keeping a list of addresses on the association that
   are valid... (when there is a deviant case such as this).


> 
> This may be prevented if We can put such recommendation which Randall
> indicated in earlier mail, I.e. DELETEIP procedure is only recommended in
> cases when NIC card assocaited with that Ip address is actually going
down.
> In that case we have to remove IP address from  Association & Endpoint .

Yes.. but you still can end up with a IP address stuck in your
association if the peer does not do ADD-IP.. 



> 
> I am really not sure whether the statment I made in previous mail should
be
> assumed TRUE/Correct  : "  An Association Can Use SUBSET of IP Addresses
> from its Endpoint ".
> 
> What do u guys think ??????

I think you CAN do this but it WILL cause you grief.. if by using
a subset you are saying making a decision that I am NOT going
to include IP-C in my address list (even though it is reachable
and should have normally been included).


R

-- 
Randall R. Stewart
randall@stewart.chicago.il.us 815-342-5222 (cell phone)

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg