Any pointers on where i can get the LTE standard for femto?

I was under the impression that this would also be used by 1588 for
delivering a solution for frequency distribution, when we need to
provide security between the master and the boundary clocks, etc.

On Fri, Dec 3, 2010 at 6:30 AM, Greg Dowd <[email protected]> wrote:
> I believe the goal was not to suggest a method for adding security but a 
> method for handling the security imposed by the LTE standard for femto.
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of 
> Jack Kohn
> Sent: Thursday, December 02, 2010 4:49 PM
> To: Xie Lei
> Cc: [email protected]
> Subject: Re: [TICTOC] The draft for IPsec synchronization security
>
> Xie,
>
> Is there a reason why you cant use the Security mechanism described in
> Annex K of IEEE std 1588-2008?
>
> Jack
>
> On Mon, Nov 15, 2010 at 12:30 PM, Xie Lei <[email protected]> wrote:
>>
>>
>> Hi Jack
>>
>> Thanks for your information, i had discussed with RFC5840 authors in IETF
>> 79# meeting. It is possible to use RFC5840 to fulfill this synchronization
>> requirements. I will follow the progress and provide more information to
>> Tictoc group.
>>
>> BR
>>
>> Rock
>>
>> ----- Original Message -----
>> From: Jack Kohn
>> To: [email protected] ; [email protected]
>> Sent: Saturday, November 13, 2010 12:30 PM
>> Subject: RE: The draft for IPsec synchronization security
>> Xie:
>>
>> While i understand your motivation to secure the timing packets, you
>> really dont need the extensions that you have defined in the below
>> draft. You must look at RFC 5840 that extends ESP and see how that can
>> be used for achieving the same functionality as you desire.
>>
>> Jack
>>
>>> Hi Yaakov and all
>>> Huawei has submitted one draft for IPSec synchronization security, you can
>>> find it in following link
>>>
>>> http://www.ietf.org/id/draft-xu-tictoc-ipsec-security-for-synchronization-00.txt
>>>
>>> We also attach one discussion document in this email, i hope we can
>>> present it in IETF Beijing meeting.
>>>
>>> BR
>>> Rock
> _______________________________________________
> TICTOC mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/tictoc
>
_______________________________________________
TICTOC mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/tictoc

Reply via email to