And since the key material is in an RLOC-record which is covered by LISP-sec 
authentication, we are covered. 

Dino


> On Dec 5, 2014, at 2:52 PM, Fabio Maino <[email protected]> wrote:
> 
>> On 12/5/14, 2:08 PM, Stephen Farrell wrote:
>> 
>>> On 05/12/14 21:45, Fabio Maino wrote:
>>> On 12/5/14, 9:36 AM, Dino Farinacci wrote:
>>>>> Hi Dino,
>>>>> I have no problems with the control plane part. An encap with
>>>>> multiprotocol support would allow to do IPsec encap before LISP
>>>>> encap, and could be used with the unauthenticated DH mechanism that
>>>>> you propose.
>>>> Well draft-farinacci-lisp-crypto-01 with LISP-SEC can give you an
>>>> authenticated DH mechanism as well.
>>> yes, but the DH mechanism itself is unauthenticated.
>> There is no problem in figuring out a way to bind a DH and
>> an authentication exchange. That's been done many times in
>> different protocols.
>> 
>> S.
>> 
> 
> Absolutely, and LISP-SEC is indeed one of the way to do it.
> 
> Fabio

_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp

Reply via email to