On 1/28/19, 2:08 PM, "Job Snijders" wrote:
Can you create RPKI ROAs for the 68.80.0.0/13?
That is the most unambiguous, programmatically verifiable statement
Comcast can make about what the rouing intentions of its prefixes are.
Job,
Working on plans for 2019.
Verizon has resolved the issue. Thanks everyone.
On 1/28/19, 1:49 PM, "NANOG on behalf of Smith, Courtney"
wrote:
Verizon (AS701) is currently originating 68.80.240.0/24. This is part of
68.80.0.0/13 allocated to Comcast (AS7922). We have reached out to Verizon to
stop the announcemen
Dear Courtney,
(This suggestion does not address the immediate issue at hand)
On Mon, Jan 28, 2019 at 06:47:29PM +, Smith, Courtney wrote:
> Verizon (AS701) is currently originating 68.80.240.0/24. This is part
> of 68.80.0.0/13 allocated to Comcast (AS7922). We have reached out to
> Verizo
Guessing there's an awesome LOA in someone's file folder for this event.
On Mon, Jan 28, 2019 at 10:48 AM Smith, Courtney
wrote:
> Verizon (AS701) is currently originating 68.80.240.0/24. This is part of
> 68.80.0.0/13 allocated to Comcast (AS7922). We have reached out to
> Verizon to stop the
Verizon (AS701) is currently originating 68.80.240.0/24. This is part of
68.80.0.0/13 allocated to Comcast (AS7922). We have reached out to Verizon to
stop the announcement. Until that occurs, we request you block the
68.80.240.0/24 announcement. Thanks.
route-views>show clock
18:35:15.335
5 matches
Mail list logo
