On Fri, 26 Feb 2016, Valery Smyslov wrote:
thank you for providing more details.
However, it is not clear from this description what UE should do if it has a
data to be sent,
but it received no protected data for some perion of time. Section 2.4. of
RFC 7296 suggests that
the IKEv2 impl
From: Valery Smyslov [mailto:sva...@gmail.com]
Sent: Friday, February 26, 2016 2:27 PM
To: Ivo Sedlacek; Tero Kivinen; Paul Wouters
Cc: ipsec@ietf.org; frederic.fir...@etsi.org
Subject: Re: [IPsec] IANA allocation of TIMEOUT_PERIOD_FOR_LIVENESS_CHECK
Hi Ivo,
thank you for providing more details.
Howeve
.
- Original Message -
From: Ivo Sedlacek
To: Tero Kivinen ; Paul Wouters
Cc: ipsec@ietf.org ; frederic.fir...@etsi.org
Sent: Thursday, February 25, 2016 6:58 PM
Subject: Re: [IPsec] IANA allocation of TIMEOUT_PERIOD_FOR_LIVENESS_CHECK
Hello,
In case you are interested in
f.org; frederic.fir...@etsi.org
Subject: Re: [IPsec] IANA allocation of TIMEOUT_PERIOD_FOR_LIVENESS_CHECK
Ivo Sedlacek writes:
> 3GPP spec expects that if the client (User Equipment) supports the
> TIMEOUT_PERIOD_FOR_LIVENESS_CHECK configuration attribute, then the
> client (User Equipment)
Ivo Sedlacek writes:
> 3GPP spec expects that if the client (User Equipment) supports the
> TIMEOUT_PERIOD_FOR_LIVENESS_CHECK configuration attribute, then the client
> (User Equipment) *enforces* the timer value indicated in the
> TIMEOUT_PERIOD_FOR_LIVENESS_CHECK configuration attribute in CFG_RE
Paul Wouters writes:
> On Thu, 25 Feb 2016, Tero Kivinen wrote:
>
> > It is notify from the server to client. I.e. client sends empty
> > TIMEOUT_PERIOD_FOR_LIVENESS_CHECK in the CFG_REQUEST and server will
> > send value in seconds inside its TIMEOUT_PERIOD_FOR_LIVENESS_CHECK in
> > CFG_REPLY. I.
Hello,
In case you are interested in detailed procedures of the 3GPP specification, I
have copied them at the end of this mail.
> > I am confused. Is this a notify of the server to the client, or a
> > configuration item by the server instructing client behaviour?
>
> It is notify from th
Hello,
> > I am confused. Is this a notify of the server to the client, or a
> > configuration item by the server instructing client behaviour?
>
> It is notify from the server to client. I.e. client sends empty
> TIMEOUT_PERIOD_FOR_LIVENESS_CHECK in the CFG_REQUEST and
> server will send valu
On Thu, 25 Feb 2016, Tero Kivinen wrote:
It is notify from the server to client. I.e. client sends empty
TIMEOUT_PERIOD_FOR_LIVENESS_CHECK in the CFG_REQUEST and server will
send value in seconds inside its TIMEOUT_PERIOD_FOR_LIVENESS_CHECK in
CFG_REPLY. I.e. the server asks client to use follow
Valery Smyslov writes:
> > I am thinking of saying "go ahead" for IANA for this allocation even
> > when this do change the IKEv2 bit, as I think there are
> > implementations using same interpretation out there, and I think this
> > configuration attribute is mostly harmless. If we would have done
Paul Wouters writes:
> On Thu, 25 Feb 2016, Tero Kivinen wrote:
>
> > I as an IANA expert got request from 3gpp to allocate new
> > configuration attribute called TIMEOUT_PERIOD_FOR_LIVENESS_CHECK for
> > IKEv2. This is used to set the timeout after which the UE will do
> > liveness check with oth
Hi,
I as an IANA expert got request from 3gpp to allocate new
configuration attribute called TIMEOUT_PERIOD_FOR_LIVENESS_CHECK for
IKEv2. This is used to set the timeout after which the UE will do
liveness check with other end if no cryptographically protected IKEv2
or IPSec messages are not rec
On Thu, 25 Feb 2016, Tero Kivinen wrote:
I as an IANA expert got request from 3gpp to allocate new
configuration attribute called TIMEOUT_PERIOD_FOR_LIVENESS_CHECK for
IKEv2. This is used to set the timeout after which the UE will do
liveness check with other end if no cryptographically protecte
I as an IANA expert got request from 3gpp to allocate new
configuration attribute called TIMEOUT_PERIOD_FOR_LIVENESS_CHECK for
IKEv2. This is used to set the timeout after which the UE will do
liveness check with other end if no cryptographically protected IKEv2
or IPSec messages are not received.
14 matches
Mail list logo