On Thu, Oct 13, 2011 at 7:07 PM, Danny Mayer wrote:
> On 10/13/2011 2:28 PM, Kevin Gross wrote:
>> Definitely important issues for some synchronization protocols but it
>> seems though two-step 1588 would work through such a connection. The
>> followup message will contain an accurate (and encrypt
On 10/13/2011 2:28 PM, Kevin Gross wrote:
> Definitely important issues for some synchronization protocols but it
> seems though two-step 1588 would work through such a connection. The
> followup message will contain an accurate (and encrypted) timestamp.
> Encryption delays would not result in sig
Definitely important issues for some synchronization protocols but it seems
though two-step 1588 would work through such a connection. The followup
message will contain an accurate (and encrypted) timestamp. Encryption
delays would not result in significant loss of accuracy with respect to an
unenc
> "Yoav" == Yoav Nir writes:
Yoav> A little. Also like GET-VPN and AC-VPN and Provider-1
Yoav> (apologies to all the vendors I've missed)
Yoav> Those are some of the incompatible solutions by individual
Yoav> vendors.
And RFC4322.
FreeSWAN has a number of local controls whe
I am going on vacation, but I did want to post these before.
Sorry if I cannot take part in the ensuing discussion.
Overall, this is a good start for an important set of problems.
But I would have liked the document to be clearer/deeper before we
can discuss it seri
