[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nanog
Subject:    Re:  Redhat contact
From:       Guillaume Tournat via NANOG <nanog () nanog ! org>
Date:       2020-09-18 16:41:23
Message-ID: 9FC1A2B3-3E86-449C-A2A9-A78C987EC215 () ironie ! org
[Download RAW message or body]


Hello

You may contact distributors instead, such as Arrow or TechData. 

Best regards

> > Le 18 sept. 2020 à 17:51, Eric Litvin <eric@lumaoptics.net> a écrit :
> 
> Hi,  I need to get in contact with someone in the sales team at Redhat but they are \
> not replying either to my emails or phone calls. Do you know anyone working for \
> Redhat whom we can call? Please dm me.  
> Thanks
> 
> Eric  Sent from my iPhone
> 
> > > On Sep 18, 2020, at 7:48 AM, Wilco Baan Hofman <wilco@baanhofman.nl> wrote:
> > 
> > 
> > > On 18/09/2020 12:07, Mark Tinka wrote:
> > > 
> > > 
> > > There was a time when the use-case for MACSec was to move banks away
> > > from running their own DWDM/FC networks, and letting operators do it.
> > 
> > Well, the other use case is access networks with 802.1x. With 802.1x as
> > long as the port stays up the session cookie (whatever is set as
> > authenticated) is the MAC address. So once a port is authenticated, it's
> > really easy to spoof a MAC and still be on the network.
> > 
> > With WPA2 enterprise on WiFi, this problem does not exist, because then
> > there is a cryptographic session. MACsec fixes that gap on wired.
> > 
> > Not all that relevant for long-distance links though :)
> > 
> > -- Wilco


[Attachment #3 (text/html)]

<html><head><meta http-equiv="content-type" content="text/html; \
charset=utf-8"></head><body dir="auto"><div dir="ltr"><meta \
http-equiv="content-type" content="text/html; charset=utf-8"><div \
dir="ltr">Hello</div><div dir="ltr"><br></div><div dir="ltr">You may contact \
distributors instead, such as Arrow or TechData.&nbsp;</div><div \
dir="ltr"><br></div><div dir="ltr">Best regards</div><div dir="ltr"><br><blockquote \
type="cite">Le 18 sept. 2020 Ã  17:51, Eric Litvin &lt;eric@lumaoptics.net&gt; a \
écrit&nbsp;:<br><br></blockquote></div><blockquote type="cite"><div \
dir="ltr"><meta http-equiv="content-type" content="text/html; \
charset=utf-8"><br><div dir="ltr"><div class="gmail_default" \
style="-webkit-text-size-adjust: auto; font-family: tahoma, sans-serif;">Hi, &nbsp;I \
need to get in contact with someone in the sales team at Redhat but they are not \
replying either to my emails or phone calls. Do you know anyone working for Redhat \
whom we can call? Please dm me.&nbsp;</div><div class="gmail_default" \
style="-webkit-text-size-adjust: auto; font-family: tahoma, \
sans-serif;"><br></div><div class="gmail_default" style="-webkit-text-size-adjust: \
auto; font-family: tahoma, sans-serif;">Thanks</div><div class="gmail_default" \
style="-webkit-text-size-adjust: auto; font-family: tahoma, \
sans-serif;"><br></div><span style="font-family: tahoma, sans-serif; \
-webkit-text-size-adjust: auto;">Eric &nbsp;</span>Sent from my iPhone</div><div \
dir="ltr"><br><blockquote type="cite">On Sep 18, 2020, at 7:48 AM, Wilco Baan Hofman \
&lt;wilco@baanhofman.nl&gt; wrote:<br><br></blockquote></div><blockquote \
type="cite"><div dir="ltr"><span></span><br><span></span><br><span>On 18/09/2020 \
12:07, Mark Tinka wrote:</span><br><span></span><br><blockquote \
type="cite"><span></span><br></blockquote><blockquote type="cite"><span>There was a \
time when the use-case for MACSec was to move banks \
away</span><br></blockquote><blockquote type="cite"><span>from running their own \
DWDM/FC networks, and letting operators do it.</span><br></blockquote><blockquote \
type="cite"><span></span><br></blockquote><span></span><br><span>Well, the other use \
case is access networks with 802.1x. With 802.1x as</span><br><span>long as the port \
stays up the session cookie (whatever is set as</span><br><span>authenticated) is the \
MAC address. So once a port is authenticated, it's</span><br><span>really easy to \
spoof a MAC and still be on the network.</span><br><span></span><br><span>With WPA2 \
enterprise on WiFi, this problem does not exist, because then</span><br><span>there \
is a cryptographic session. MACsec fixes that gap on \
wired.</span><br><span></span><br><span>Not all that relevant for long-distance links \
though :)</span><br><span></span><br><span>-- \
Wilco</span><br></div></blockquote></div></blockquote></div></body></html>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic