<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
In my opinion you can, just that the participants are not
willing to do so due, in part, to the lack of acceptance of BCP38.<br>
<pre class="moz-signature" cols="72">-----
Alain Hebert <a class="moz-txt-link-abbreviated" href="mailto:ahebert@pubnix.net">ahebert@pubnix.net</a>
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911 <a class="moz-txt-link-freetext" href="http://www.pubnix.net">http://www.pubnix.net</a> Fax: 514-990-9443
</pre>
<div class="moz-cite-prefix">On 2020-03-14 07:35,
<a class="moz-txt-link-abbreviated" href="mailto:nanog@jack.fr.eu.org">nanog@jack.fr.eu.org</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:0b035cde-df72-d73b-5dcf-395948396652@jack.fr.eu.org">
<pre class="moz-quote-pre" wrap="">This is the issue (and the leitmotiv) of forged packets: you cannot
trace their origin in real world situation
On 3/14/20 12:03 PM, Jean | ddostest.me via NANOG wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Hi Bill,
can you post some forged packets please? You can send them offlist if
you prefer.
It seems to be similar to what Octopus experience few weeks ago on this
list.
Thanks
Jean St-Laurent | CISSP #634103
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
</blockquote>
<br>
</body>
</html>