Subject: RE: [NSIS] GIST API primitive SetStateLifetime

From: "Hancock, Robert" <[email-masked]>
Date: Fri, 23 Feb 2007 16:07:01 -0000

hi,

I agree it's a little strange. The background rationale 
is that the presence of the SID in the triplet is really
to avoid blind attacks on the routing state, not that
you actually want the routing state to be different for
different SIDs. however, you do have to refresh the state
for each SID, so it is conceivable that the lifetimes 
could be different. i've added it to the API with a note
that it can be wildcarded.

r. 

> -----Original Message-----
> From: Christian Dickmann [mailto:[email-masked]] 
> Sent: 14 November 2006 01:19
> To: [email-masked]
> Subject: [NSIS] GIST API primitive SetStateLifetime
> 
> Hi,
> 
> I have a question regarding the SetStateLifetime ( NSLPID, 
> MRI, State-Lifetime ) primitive of the GIST API.
> Why is there no session ID present here? The key for GIST 
> routing state is the 3-tupel (NSLPID, MRI, SID), thus the 
> SetStateLifetime primitive potentially effects multiple 
> routing states at a time.
> 
> Regards,
> Christian Dickmann
> 
> 
> _______________________________________________
> nsis mailing list
> [email-masked]
> https://www1.ietf.org/mailman/listinfo/nsis
> 

_______________________________________________
nsis mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/nsis