[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Deletion of SA



Hi Scott,

I remember you raised the following question in response to my question
regarding SA deletion. But there was no further discussion on this issue.
The issue was that, which SA to be deleted when you receive the delete
payload with multiple SPI. 

At 10:49 AM 3/23/98 -0800, you wrote:
<snip...>
>This issue raises some confusion, and I'm also uncertain as to whether
>the current document adequately addresses it. If there are SA's in both
>directions between H1 and H2, and H1 sends a delete payload to H2,
>which
>SA may it apply to? If we say it only applies to the SA into H1 from H2
>(H1's INBOUND SA), no ambiguity exists. However, there may be ambiguity
>if we permit H1 to also delete SA's which are outbound with respect to
>H1. This is because the delete payload permits multiple SPI's to be
>specified, but gives no mechanism for specifying which SPI is which.
>Since the SPI's are generated independently, they could (in theory, at
>least) be identical.
>
>It seems the only thing permitted by the protocol as it currently
>stands
>is for H1 to delete the INBOUND SA (from H2 to H1), and to send a
>notify
>payload with perhaps NOTIFY-SA-LIFETIME in it to delete the OUTBOUND SA.

Thanks
- Srinu
******************************************************************
* OFFICE ADDRESS :                                               *
* SrinivasRao. B. Kulkarni                                       *
* Rendezvous On Chip Pvt Ltd.                                    *
* First Floor, Plot No. 14,                                      *
* NewVasaviNagar, Kharkhana,                                     *
* SECUNDERABAD - 500015.                                         *
* STATE ANDHRA PRADESH                                           *
* INDIA                                                          *
* Ph : (040) 7742606, 7740406                                    *
* email address : srinu@trinc.com                                *
******************************************************************




Follow-Ups: