AWS - IP Address is Blocked?

[Ryan Hamel]

Hello,

 

I have a public IP address in the Dallas area receiving HTTP 403 errors
whenever they visit ANY website powered by AWS, which is impacting quite a
significant chunk of connectivity. If anyone has a way of contacting AWS's
support team about getting this IP address removed from their block list or
explain what is happening, I would greatly appreciate if you could contact
me off list.

 

Thank you very much for your time.

 

Ryan Hamel

Re: Serious Juniper Hardware EoL Announcements

[Mark Tinka]

So there have been some developments re: this thread.

As it pertains to the both the MX204 and MX10003, Juniper have made the 
following amendments:


 * EoS = 2023.
 * End of new features = 2024.
 * End of bug fixes = 2028.
 * End of critical features = 2028.
 * EoL = 2029.

FWIW.

Mark.

PC Picks: NANOG 85 + N86 Call for Presentations

[Nanog News]

*PC Picks: NANOG 85 *
*Program Committee Picks Their Favorite Talks at NANOG 85*

*Hours of ground-breaking industry talks, right at your fingertips!*

Not sure where to start in watching your recap of NANOG 85? Don't fret. We
saved you the time and asked the NANOG Programming Committee (PC) to select
their favorite talks.

*READ NOW  *

*NANOG 86: Call for Presentations!  *
*NANOG PC is Now Accepting Proposals for NANOG 86 *

NANOG 86 will take place in Hollywood, CA, on 17-19 Oct 2022.

*Requested Topics: *

   - Network Automation
   - Tutorials (IPv6, BGP, Segment Routing, DNS)
   - Security (developments in, problems/solutions, various protocols)

The PC is looking to schedule 1,020 minutes of content for NANOG 86 and has
confirmed 135 minutes already - so don't wait!

*LEARN MORE  *

*Survey: Next Steps for COVID-19*
Please take a quick minute to complete our one-question survey regarding
the next steps for COVID-19 and attendance at upcoming meetings.

*TAKE SURVEY
*

[NANOG-announce] PC Picks: NANOG 85 + N86 Call for Presentations

[Nanog News]

*PC Picks: NANOG 85 *
*Program Committee Picks Their Favorite Talks at NANOG 85*

*Hours of ground-breaking industry talks, right at your fingertips!*

Not sure where to start in watching your recap of NANOG 85? Don't fret. We
saved you the time and asked the NANOG Programming Committee (PC) to select
their favorite talks.

*READ NOW  *

*NANOG 86: Call for Presentations!  *
*NANOG PC is Now Accepting Proposals for NANOG 86 *

NANOG 86 will take place in Hollywood, CA, on 17-19 Oct 2022.

*Requested Topics: *

   - Network Automation
   - Tutorials (IPv6, BGP, Segment Routing, DNS)
   - Security (developments in, problems/solutions, various protocols)

The PC is looking to schedule 1,020 minutes of content for NANOG 86 and has
confirmed 135 minutes already - so don't wait!

*LEARN MORE  *

*Survey: Next Steps for COVID-19*
Please take a quick minute to complete our one-question survey regarding
the next steps for COVID-19 and attendance at upcoming meetings.

*TAKE SURVEY
*
___
NANOG-announce mailing list
NANOG-announce@nanog.org
https://mailman.nanog.org/mailman/listinfo/nanog-announce

Re: Hardware & Software IPv6 Only

[William Herrin]

On Wed, Jun 29, 2022 at 10:00 AM Alejandro Acosta
 wrote:
>Sorry for the noise. Hopefully this is a good place to ask.
>
>Are there any IPv6 Only hardware you are aware of?. And IPv6 Only
> software too?
>
>If so and you don't mind you can contact me off-list.

Hello,

I've written some off-Internet IPv6-only software. There are generally
only two reasons to do so:

1. You need the software to self-address a link local Interface. IPv4
doesn't do this well. It's useful for experiments in self-constructing
networks.

2. You're doing something funky with networking that has to live in a
large address space.

Since the IPv6 software APIs are 100% backward compatible with IPv4
there aren't a whole lot of other reasons to write software that's
IPv6-only.

Regards,
Bill Herrin



-- 
William Herrin
b...@herrin.us
https://bill.herrin.us/

Hardware & Software IPv6 Only

[Alejandro Acosta]

Hello,

  Sorry for the noise. Hopefully this is a good place to ask.

  Are there any IPv6 Only hardware you are aware of?. And IPv6 Only 
software too?


  If so and you don't mind you can contact me off-list.


Thanks,


Alejandro,

de facto standard or convention to IRR AS-SET representing BGP Roles of rfc9234

[Douglas Fischer]

I begin my questioning by mentioning the recent moves towards
standardization of BGP Roles made formalized initially by RFC 9234, and
also by what is proposed with the ASPA that we should see soon.

And from what I can see, it makes a lot of sense to have an IRR
representation through AS-SET of the list of ASNs that you would have a
neighborhood relationship in each role.

This is done with the objective of being able to make public (if desired)
the type of relationship that each ASN with its Peers, and also to be able
to build, and publish (if desired) in a better elaborated way the Routing
Policies of each ASN.

In view of this, I was wondering if:
Any kind of standardization for the naming of these AS-SETs that would
represent this group of peers had already been considered?

Something that came to my mind would be to use the strings proposed by
RFC9234 for the IANA REGISTRY and use it as a suffix for the AS-SET name.
AS:AS-ROLE-

Exemplifying:

as-set: AS65123:AS-ROLE-PROVIDER
descr: ASN list of Transit Upstream(Providers) of AS65123.

as-set: AS65123:AS-ROLE-CUSTOMER
descr: ASN list of Transit Downstream(CUSTOMER) of AS65123.

as-set: AS65123:AS-ROLE-PEER
descr: ASN list of Networks that AS65123 do some kind of peering.

as-set: AS65123:AS-ROLE-RS
descr: ASN list of Route-Servers with which AS65123 has a BGP neighborhood.

as-set: AS65123:AS-ROLE-RS-CLIENT
descr: ASN list of Route-Server Clients the route-servers of AS65123.



Any thoughts or considerations on this?


-- 
Douglas Fernando Fischer
Engº de Controle e Automação