Thanks for agreeing to update the document. I would be happy to contribute to 
discussions related to the update. Please include me on the appropriate point 
to point exchanges. 

Thanks, Ross

-----Original Message-----
From: lisp [mailto:[email protected]] On Behalf Of Damien Saucez
Sent: Tuesday, May 27, 2014 12:06 PM
To: LISP mailing list list
Subject: Re: [lisp] Restarting last call on LISP threats

Dear all,

Thank you all for the passion you put in discussing the threats
document.  We have read all the arguments and arrived to the
conclusion that the threat document needs to be reshaped so to clear
all misunderstandings.  We will provide a new version for early July
that does not exclude any scenarios.  Actually most of problems
pinpointed are already covered somehow in the document but
precisions/rephrasing have to be done to make things clear.

For the sake of efficiency, while writing the new proposal in the
coming weeks, we will make point-to-point exchanges with the different
people that contributed to the discussion so to be sure that we
address all their comments.

Thanks,

Damien Saucez

On 27 May 2014, at 17:12, Joel M. Halpern <[email protected]> wrote:

> Can we please not get into a debate about how well BCP38 is or is not 
> deployed, whether violations are remotely detectable, ...This is NOT the 
> working group for that.
> 
> For our purposes, given that source address forging is known to occur, we 
> have to allow it in the threat analysis.
> 
> Yours,
> Joel
> 
> On 5/27/14, 11:04 AM, Dino Farinacci wrote:
>> 
>>> Also, recall that large BCP38 holes exist in today's internet.
>> 
>> And I am going to repeat again, this is not a binary statement. That is, if 
>> a BCP38 hole exists in one part of the network, source spoofing can still be 
>> detected in other parts of the network.
>> 
>> Dino
>> 
>> 

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

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

Reply via email to