Hi Phil,
isn't the initial registration token such a credential, which allows to
co-relate different instances of the same software?
regards,
Torsten.
Phil Hunt schrieb:
>Finally i believe the bb+ doesn't have the issue because they are
>solving with an initial authn credential that cont
Finally i believe the bb+ doesn't have the issue because they are solving with
an initial authn credential that contains the same info.
My feeling is that this functionality needs to be standardized one way or
another.
Phil
On 2013-06-03, at 19:16, Derek Atkins wrote:
> Phil,
>
> Phil Hun
Arg iphone types...
See below
Phil
On 2013-06-03, at 20:34, Phil Hunt wrote:
> From an operational security and change management perspective it is
> absolutely critical to know what clients should be of the same software type
> and version.
>
> We have customers that will want to be able t
>From an operational security and change management perspective it is
>absolutely critical to know what clients should be of the same software type
>and version.
We have customers that will want to be able to approve what 3rd party software
is used on their service.
If the spec doesn't suppo
Phil,
Phil Hunt writes:
> Not quite. I will call you.
>
> I am saying we are transitioning from the old public client model. The new
> model proposes quasi-confidential characteristics but in some respects is
> missing key information from the public model. Namely that a group of clients
> are
Justin Richer writes:
> I think the concern here is that rotation of client credential is not
> something discussed before. Before we put it in the spec we should
> consider the reasons for doing it and what problems it solves.
>
> The client doesn't get to choose when its credentials
Stephen,
I feel it should be MANDATORY to implement TLS1.2, especially since NIST is
in the process of deprecating TLS1.0 as a supported version.
Best regards,
Don
Donald F. Coffin
Founder/CTO
REMI Networks
22751 El Prado Suite 6216
Rancho Santa Margarita, CA 92688-3836
Phone: (949) 636-8
