Re: [Tsvwg] End point and association Address conflict

Randall Stewart <randall@stewart.chicago.il.us> Fri, 26 April 2002 13:59 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 JAA04609 for <tsvwg-archive@odin.ietf.org>; Fri, 26 Apr 2002 09:59:40 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id JAA13185 for tsvwg-archive@odin.ietf.org; Fri, 26 Apr 2002 09:59:43 -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 JAA11729; Fri, 26 Apr 2002 09:31:56 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA11700 for <tsvwg@optimus.ietf.org>; Fri, 26 Apr 2002 09:31:52 -0400 (EDT)
Received: from stewart.chicago.il.us (user166.64.47.24.dsli.com [64.47.24.166]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03468 for <tsvwg@ietf.org>; Fri, 26 Apr 2002 09:31:48 -0400 (EDT)
Received: from stewart.chicago.il.us (stewlap [10.1.1.5]) by stewart.chicago.il.us (8.11.1/8.11.1) with ESMTP id g3QDVTH51431; Fri, 26 Apr 2002 08:31:30 -0500 (CDT) (envelope-from randall@stewart.chicago.il.us)
Message-ID: <3CC956B1.FC0CC9DD@stewart.chicago.il.us>
Date: Fri, 26 Apr 2002 08:31:29 -0500
From: Randall Stewart <randall@stewart.chicago.il.us>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
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
References: <58AEDE27D48F884285007ABF827FF26346A39E@esebe017.NOE.Nokia.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

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...


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