GGC need portal access restored

[Seth Mattinen via NANOG]

I also need someone at GGC to contact me ASAP; a tech showed up on site 
to replace hardware in a node and I've come to find out my portal access 
is no longer available and I can't place it into maintenance mode.


~Seth

[NANOG-announce] Reminder to Submit Presentations for NANOG 88

[Cat Gurinsky]

NANOG Community,

The NANOG Program Committee (PC) would like to remind you that we are
accepting proposals for in-person or live remote presentations at all
sessions of NANOG 88, a hybrid meeting, taking place in Seattle, Washington
on 12-14 Jun 2023. Below is a summary of key details and dates from the
Call For Presentations on the NANOG website, which can be found at
https://www.nanog.org/program/call-presentations/.

Requested Topics:

Based on feedback from our survey results, we have seen numerous requests
for the following topics:

   -

   Network Automation - practical uses, how to get started
   -

   Network Future - forecast for changes in technology, design, applications
   -

   Research & Education - what research is happening now in network
   operations
   -

   Security - developments in, problems/solutions, various protocols of
   -

   Tutorials - all levels, IPv6, BGP, Segment Routing, DNS, MPLS, VXLAN


We are looking to schedule over 1,600 minutes of content between General
Session and Breakout Rooms for NANOG 88, and have confirmed 300 minutes
already - so don’t wait! Presentation abstracts and draft slides should be
submitted no later than Monday, 24 Apr 2023 to be considered for NANOG 88.

Presentations may cover current technologies, soon-to-be deployed
technologies, and industry innovation. Vendors are welcome to submit talks
which cover relevant technologies and capabilities, but presentations
should not be promotional, or discuss proprietary solutions.


The primary speaker, moderator, or author should submit a presentation
proposal and abstract via the Program Committee Tool at:
https://www.nanog.org/meetings/submit-presentation/


   -

   Sign in with your Profile Account
   -

   Select the type of talk you propose to present, and complete the form


Timeline for submission and proposal review:

   -

   Submitter enters abstract (and draft slides if possible) in the Program
   Committee Tool prior to the deadline for slide submission.
   -

   PC performs initial review and assigns a “shepherd” to help develop the
   submission — typically within 2 weeks.
   -

   Submitter develops draft slides of talk if not already submitted with
   the initial proposal. Please submit initial draft slides early — the PC
   does not evaluate submissions until draft slides are available for review.
   NANOG Staff is available to assist with slide templates upon request from
   the submitter.
   -

   Panel and Track submissions should provide a topic list and
   intended/confirmed participants in the abstract.
   -

   PC reviews the slides and continues to work with Submitter as needed to
   develop the topic.
   -

   FINAL SUBMISSION DEADLINE Draft presentation slides should be submitted
   prior to the published deadline for slides (24 Apr 2023).
   -

   PC evaluates submissions to determine presentations for the agenda
   (posted on 26 May 2023).
   -

   Submitters notified.
   -

   Agenda assembled and posted.
   -

   Final presentation slides must be submitted prior to the published
   deadline for slides (5 Jun 2023 for in person + live remote presentations).


If you think you have an interesting topic but want feedback or suggestions
for developing an idea into a presentation, please email the PC (
nano...@nanog.org), and a representative will respond to you in a timely
manner. Otherwise, submit your talk, tutorial, track, or panel proposal to
the Program Committee Tool at your earliest convenience. We look forward to
reviewing your submission!
NANOG 88 Calendar of Events

Date

Event/Deadline

Wed, 21 Mar 2023

CFP Reminder Announcement

Mon, 24 Apr 2023

DRAFT Presentation Slides Due

Mon, 15 May 2023

Topics List Published

Fri, 26 May 2023

Meeting Agenda Published

Mon, 5 Jun 2023

Final Slides DUE

Sun, 11 Jun 2023

On-Site Lightning Talk Submissions Open


Final slides for accepted presentations must be submitted by Monday, 5 Jun
2023. Materials received after that date may be updated on the website
after the completion of the conference.

We look forward to seeing you in February!

Sincerely,

Cat Gurinsky

Program Committee Chair

Sent on behalf of the NANOG PC
___
NANOG-announce mailing list
NANOG-announce@nanog.org
https://mailman.nanog.org/mailman/listinfo/nanog-announce

Reminder to Submit Presentations for NANOG 88

[Cat Gurinsky]

NANOG Community,

The NANOG Program Committee (PC) would like to remind you that we are
accepting proposals for in-person or live remote presentations at all
sessions of NANOG 88, a hybrid meeting, taking place in Seattle, Washington
on 12-14 Jun 2023. Below is a summary of key details and dates from the
Call For Presentations on the NANOG website, which can be found at
https://www.nanog.org/program/call-presentations/.

Requested Topics:

Based on feedback from our survey results, we have seen numerous requests
for the following topics:

   -

   Network Automation - practical uses, how to get started
   -

   Network Future - forecast for changes in technology, design, applications
   -

   Research & Education - what research is happening now in network
   operations
   -

   Security - developments in, problems/solutions, various protocols of
   -

   Tutorials - all levels, IPv6, BGP, Segment Routing, DNS, MPLS, VXLAN


We are looking to schedule over 1,600 minutes of content between General
Session and Breakout Rooms for NANOG 88, and have confirmed 300 minutes
already - so don’t wait! Presentation abstracts and draft slides should be
submitted no later than Monday, 24 Apr 2023 to be considered for NANOG 88.

Presentations may cover current technologies, soon-to-be deployed
technologies, and industry innovation. Vendors are welcome to submit talks
which cover relevant technologies and capabilities, but presentations
should not be promotional, or discuss proprietary solutions.


The primary speaker, moderator, or author should submit a presentation
proposal and abstract via the Program Committee Tool at:
https://www.nanog.org/meetings/submit-presentation/


   -

   Sign in with your Profile Account
   -

   Select the type of talk you propose to present, and complete the form


Timeline for submission and proposal review:

   -

   Submitter enters abstract (and draft slides if possible) in the Program
   Committee Tool prior to the deadline for slide submission.
   -

   PC performs initial review and assigns a “shepherd” to help develop the
   submission — typically within 2 weeks.
   -

   Submitter develops draft slides of talk if not already submitted with
   the initial proposal. Please submit initial draft slides early — the PC
   does not evaluate submissions until draft slides are available for review.
   NANOG Staff is available to assist with slide templates upon request from
   the submitter.
   -

   Panel and Track submissions should provide a topic list and
   intended/confirmed participants in the abstract.
   -

   PC reviews the slides and continues to work with Submitter as needed to
   develop the topic.
   -

   FINAL SUBMISSION DEADLINE Draft presentation slides should be submitted
   prior to the published deadline for slides (24 Apr 2023).
   -

   PC evaluates submissions to determine presentations for the agenda
   (posted on 26 May 2023).
   -

   Submitters notified.
   -

   Agenda assembled and posted.
   -

   Final presentation slides must be submitted prior to the published
   deadline for slides (5 Jun 2023 for in person + live remote presentations).


If you think you have an interesting topic but want feedback or suggestions
for developing an idea into a presentation, please email the PC (
nano...@nanog.org), and a representative will respond to you in a timely
manner. Otherwise, submit your talk, tutorial, track, or panel proposal to
the Program Committee Tool at your earliest convenience. We look forward to
reviewing your submission!
NANOG 88 Calendar of Events

Date

Event/Deadline

Wed, 21 Mar 2023

CFP Reminder Announcement

Mon, 24 Apr 2023

DRAFT Presentation Slides Due

Mon, 15 May 2023

Topics List Published

Fri, 26 May 2023

Meeting Agenda Published

Mon, 5 Jun 2023

Final Slides DUE

Sun, 11 Jun 2023

On-Site Lightning Talk Submissions Open


Final slides for accepted presentations must be submitted by Monday, 5 Jun
2023. Materials received after that date may be updated on the website
after the completion of the conference.

We look forward to seeing you in February!

Sincerely,

Cat Gurinsky

Program Committee Chair

Sent on behalf of the NANOG PC

Re: Spamhaus flags any IP announced by our ASN as a criminal network

[August Yang via NANOG]

Firstly, it's worth noting that AS47158 was registered to 
ORG-IL649-RIPE, which was not a LIR.


Additionally, LIRs do not assign ASNs to end users whereas RIPE does. 
NIR in certain regions is another story.


End user may enter into a sponsorship agreement with LIR to receive ASN 
assignment, still directly from NCC.


It's important to note that ASNs and IP resources have quite different 
assignment policies, so the involvement of IP brokers is not relevant in 
this particular case.


On 2023-03-21 2:33 p.m., George Toma wrote:
Well that's for end users. The company in question seems to be a 
Telecom operator.
The RIPE model is a very strange and confusing one, where ISPs 
basically become LIRs and they themselves assign ASNs and IPs, and 
there are 23000 LIRs in ARIN. Basically any ISP , webhosting company, 
datacenter or even a trading company can become a LIR.


It's a very strange model which had just cost me 15 minutes of my time 
to just dig into and get some basic understanding of it. I would not 
put my hand in the fire that the OP is a LIR or not, but they are an 
ISP so I would assume they are LIR and as such can reassign the IPs,a 
nd if they are not LIR they can become one.


Anyway many of IP renting companies such as IPXO are RIPE-based, and 
those who are ARIN or APNIC based also have subnets from RIPE region. 
If RIPE was against subletting, the whole market would not exist with 
RIPE subnets.


Regards
George



On Tue, Mar 21, 2023 at 2:17 PM  wrote:

RIPE NCC Requirements: End User Assignment Agreement states:

“End User may not sub-assign resources to third parties.”

Best regards,
August Yang

On 2023-03-21 13:12, George Toma wrote:
> I do not believe ASN sharing is illegal or prohibited, it's not
> prohibited in LACNIC and in APNIC policy I also could not find
> anything about ASN sharing, only
>
> APNIC policy states:
> "2.3. Autonomous System (AS)An Autonomous System (AS) is a connected
> group of one or more IP prefixes run by one or more network
operators
> under a single and clearly defined routing policy.
> 2.3.1. Autonomous System Number (ASN)
> An Autonomous System Number (ASN) is a unique two- or four-byte
number
> associated with an AS. The ASN is used as an identifier to allow the
> AS to exchange dynamic routing information with other Autonomous
> Systems."
>
> Nothing prohibiting ASN sharing and 2.3 specifically states "run by
> one or more network operators... single routing policy"
>
> Regards
> George
>
> On Tue, Mar 21, 2023 at 8:00 AM  wrote:
>
>> Message: 19
>> Date: Mon, 20 Mar 2023 16:24:09 -0400
>> From: ay...@august.tw
>> To: Collider 
>> Cc: nanog@nanog.org
>> Subject: Re: Spamhaus flags any IP announced by our ASN as a
>> criminal
>> network
>> Message-ID: <5b7ed1b1fbff65dfc63d188c2e1f9...@august.tw>
>> Content-Type: text/plain; charset=UTF-8; format=flowed
>>
>> Several Huize ASNs, e.g. AS47158 and AS141011, were revoked due to
>> RIR
>> policy violations, which include prohibited sharing of ASNs with
>> third
>> parties, IP hijacking, and malicious path prepending.
>>
>> Given this history, it is not surprising that Spamhaus would
>> blacklist
>> IP addresses associated with their ASN. In my opinion, such action
>> is
>> well-justified.
>>
>> Best regards,
>> August Yang


--
Best regards
August Yang

smime.p7s
Description: S/MIME Cryptographic Signature

Anyone from Google Global Cache ?

[George Toma]

Hello,

Is there someone on this list from the Google Global Cache program (GGC)
who could contact me off-list? If so I would greatly appreciate that.

I would need a favor to get some information and look up a case because the
responses to the tickets in the ISP portal I am getting are not giving me
any meaningful answers.

Thank you

Regards
George Toma

Re: Spamhaus flags any IP announced by our ASN as a criminal network

[George Toma]

Well that's for end users. The company in question seems to be a Telecom
operator.
The RIPE model is a very strange and confusing one, where ISPs basically
become LIRs and they themselves assign ASNs and IPs, and there are 23000
LIRs in ARIN. Basically any ISP , webhosting company, datacenter or even a
trading company can become a LIR.

It's a very strange model which had just cost me 15 minutes of my time to
just dig into and get some basic understanding of it. I would not put my
hand in the fire that the OP is a LIR or not, but they are an ISP so I
would assume they are LIR and as such can reassign the IPs,a nd if they are
not LIR they can become one.

Anyway many of IP renting companies such as IPXO are RIPE-based, and those
who are ARIN or APNIC based also have subnets from RIPE region. If RIPE was
against subletting, the whole market would not exist with RIPE subnets.

Regards
George



On Tue, Mar 21, 2023 at 2:17 PM  wrote:

> RIPE NCC Requirements: End User Assignment Agreement states:
>
> “End User may not sub-assign resources to third parties.”
>
> Best regards,
> August Yang
>
> On 2023-03-21 13:12, George Toma wrote:
> > I do not believe ASN sharing is illegal or prohibited, it's not
> > prohibited in LACNIC and in APNIC policy I also could not find
> > anything about ASN sharing, only
> >
> > APNIC policy states:
> > "2.3. Autonomous System (AS)An Autonomous System (AS) is a connected
> > group of one or more IP prefixes run by one or more network operators
> > under a single and clearly defined routing policy.
> > 2.3.1. Autonomous System Number (ASN)
> > An Autonomous System Number (ASN) is a unique two- or four-byte number
> > associated with an AS. The ASN is used as an identifier to allow the
> > AS to exchange dynamic routing information with other Autonomous
> > Systems."
> >
> > Nothing prohibiting ASN sharing and 2.3 specifically states "run by
> > one or more network operators... single routing policy"
> >
> > Regards
> > George
> >
> > On Tue, Mar 21, 2023 at 8:00 AM  wrote:
> >
> >> Message: 19
> >> Date: Mon, 20 Mar 2023 16:24:09 -0400
> >> From: ay...@august.tw
> >> To: Collider 
> >> Cc: nanog@nanog.org
> >> Subject: Re: Spamhaus flags any IP announced by our ASN as a
> >> criminal
> >> network
> >> Message-ID: <5b7ed1b1fbff65dfc63d188c2e1f9...@august.tw>
> >> Content-Type: text/plain; charset=UTF-8; format=flowed
> >>
> >> Several Huize ASNs, e.g. AS47158 and AS141011, were revoked due to
> >> RIR
> >> policy violations, which include prohibited sharing of ASNs with
> >> third
> >> parties, IP hijacking, and malicious path prepending.
> >>
> >> Given this history, it is not surprising that Spamhaus would
> >> blacklist
> >> IP addresses associated with their ASN. In my opinion, such action
> >> is
> >> well-justified.
> >>
> >> Best regards,
> >> August Yang
>

Re: Spamhaus flags any IP announced by our ASN as a criminal network

[August Yang via NANOG]

RIPE NCC Requirements: End User Assignment Agreement states:

“End User may not sub-assign resources to third parties.”

Best regards,
August Yang

On 2023-03-21 13:12, George Toma wrote:

I do not believe ASN sharing is illegal or prohibited, it's not
prohibited in LACNIC and in APNIC policy I also could not find
anything about ASN sharing, only

APNIC policy states:
"2.3. Autonomous System (AS)An Autonomous System (AS) is a connected
group of one or more IP prefixes run by one or more network operators
under a single and clearly defined routing policy.
2.3.1. Autonomous System Number (ASN)
An Autonomous System Number (ASN) is a unique two- or four-byte number
associated with an AS. The ASN is used as an identifier to allow the
AS to exchange dynamic routing information with other Autonomous
Systems."

Nothing prohibiting ASN sharing and 2.3 specifically states "run by
one or more network operators... single routing policy"

Regards
George

On Tue, Mar 21, 2023 at 8:00 AM  wrote:


Message: 19
Date: Mon, 20 Mar 2023 16:24:09 -0400
From: ay...@august.tw
To: Collider 
Cc: nanog@nanog.org
Subject: Re: Spamhaus flags any IP announced by our ASN as a
criminal
network
Message-ID: <5b7ed1b1fbff65dfc63d188c2e1f9...@august.tw>
Content-Type: text/plain; charset=UTF-8; format=flowed

Several Huize ASNs, e.g. AS47158 and AS141011, were revoked due to
RIR
policy violations, which include prohibited sharing of ASNs with
third
parties, IP hijacking, and malicious path prepending.

Given this history, it is not surprising that Spamhaus would
blacklist
IP addresses associated with their ASN. In my opinion, such action
is
well-justified.

Best regards,
August Yang

Re: Spamhaus flags any IP announced by our ASN as a criminal network

[George Toma]

I do not believe ASN sharing is illegal or prohibited, it's not prohibited
in LACNIC and in APNIC policy I also could not find anything about ASN
sharing, only

APNIC policy states:
"2.3. Autonomous System (AS)
An Autonomous System (AS) is a connected group of one or more IP prefixes
run by one or more network operators under a single and clearly defined
routing policy.
2.3.1. Autonomous System Number (ASN)
An Autonomous System Number (ASN) is a unique two- or four-byte number
associated with an AS. The ASN is used as an identifier to allow the AS to
exchange dynamic routing information with other Autonomous Systems."

Nothing prohibiting ASN sharing and 2.3 specifically states "run by one or
more network operators... single routing policy"


Regards
George


On Tue, Mar 21, 2023 at 8:00 AM  wrote:

> Message: 19
> Date: Mon, 20 Mar 2023 16:24:09 -0400
> From: ay...@august.tw
> To: Collider 
> Cc: nanog@nanog.org
> Subject: Re: Spamhaus flags any IP announced by our ASN as a criminal
> network
> Message-ID: <5b7ed1b1fbff65dfc63d188c2e1f9...@august.tw>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> Several Huize ASNs, e.g. AS47158 and AS141011, were revoked due to RIR
> policy violations, which include prohibited sharing of ASNs with third
> parties, IP hijacking, and malicious path prepending.
>
> Given this history, it is not surprising that Spamhaus would blacklist
> IP addresses associated with their ASN. In my opinion, such action is
> well-justified.
>
> Best regards,
> August Yang
>

Re: Spamhaus flags any IP announced by our ASN as a criminal

[Roberto Navarro]

Why not?

DUHL from sorbs is very similar to PBL from spamhaus.

A decade  ago, when I was working on a mid size hosting company we used
duhl from sorbs as a way to force residential customers to use submission
instead of smtp to connect to the server. It proved more useful than any
documentation or tutorial we could provide our new customers.

Obviously, it was not the only dnsbl list we were using. In fact, we paying
for multiple bl feeds that we were consolidating on our own list.

Regards,

El mar, 21 mar 2023 a las 13:55, Martin Hotze ()
escribió:

> > Date: Mon, 20 Mar 2023 14:15:08 -0700
> > From: Randy Bush 
> > Subject: Re: Spamhaus flags any IP announced by our ASN as a criminal
> network
> >
> (...)
> >
> > we reject automagically on spamhaus, mail-abuse.org, and sorbs.  really
> > appreciate their services.
> >
> > randy
> >
>
> Sorbs? Really? *doh*
>
> #m
>
>

-- 
 
Algunos de nuestros sites:
 
    

C/ San Vicente Mártir, 220 Oficina 1 - 46007 
Valencia
Tel 963 417 912 - www.ontecnia.com 

 
De acuerdo con la normativa sobre protección de datos de carácter personal, 
le indicamos que los datos que nos ha facilitado y nos facilite en un 
futuro serán incluidos en nuestros ficheros, previamente inscritos en la 
Agencia Española de Protección de Datos, y utilizados para finalidades 
relacionadas con la prestación de nuestros servicios. Dichos datos serán 
tratados con la debida confidencialidad sin que, fuera de los casos 
legalmente previstos, vayan a ser cedidos a terceros sin su autorización. 
En cualquier caso, podrá ejercer los derechos de acceso, rectificación, 
oposición y cancelación, dirigiéndose por escrito a Ontecnia Media 
Networks, S.L., con domicilio en Valencia, calle San Vicente Mártir, 220, 
Oficina 1, CP 46007 o a través de la dirección h...@ontecnia.com 
.

Re: Spamhaus flags any IP announced by our ASN as a criminal network

[Barry Raveendran Greene]

Hi Brandon,Your next actions are to level up the security of your network, your organization, and your team. I’ll craft up a post with a checklist you can use. If you don’t do this, then people on your team, your company, and your customers will continue to be “danger do not go there” listed. Spamhaus is not the only one providing easy tools to help organizations deploy “danger do not go there” list. Step 1 on the list …. Deploy Exploitable Port Filtering on the edge of your network ….Filtering Exploitable Ports and Minimizing Risk from the Internet and from Your Customerssenki.orgThe other steps I’ll put into a blog post. BarryOn Mar 21, 2023, at 07:10, Brandon Zhi  wrote:Our person in charge has consulted with their previous person in charge, and their response is this."problem began long before February 18th.  The problem was that in 2022 they added our prefix 87.251.79.0/24 to the black list, and said that if there were no complaints for 30-60 days, the record would be deleted.  we agreed, almost a year has passed, the record has remained.  They tried several times to put pressure on our providers, but we always record any termination of the contract with large fines, not a single provider has done this, we pay a lot of money for the Internet, and no one wants to take risks, now spamhouse pressure on"Actually, I didn’t know what a spamhouse was before this month, until we announced the IP in vultr They claim they've been working on the issue, but I've found that they don't respond to emails very well (I can only judge from this). Usually though, I tell them to take down the content, and then the content gets a different provider.Also, it's not clear to me whether we need to reply to emails sent from the spamhouse system. They claim that they took care of the content, but I personally think it's because they didn't respond to the email that spamhouse thinks they're not doing itOn 2023年3月21日周二 上午5:15 Randy Bush  wrote:>> I don't think any ISP would reject an IP that is on the Spamhaus
>> list.
> you, clearly, have been living under several rocks for a very long
> time.

we reject automagically on spamhaus, mail-abuse.org, and sorbs.  really
appreciate their services.

randy

Looking for someone at ipligence and/or Washington Gas

[Glenn McGurrin via NANOG]

I'm recently become a customer of Washington Gas but their website won't 
let me see anything claiming I'm in the Netherlands and so they are 
blocking me.  I'm not sure how the geolocation data got screwed up, as 
far as I can tell this IP block has never been there and every 
geolocation provider except for ipligence shows it in pretty much the 
right spot near Washington DC.  Phone call to Washington Gas says email 
their support, their support has an auto reply saying they will get back 
to me but never does, I've just send the 3rd email there, the first two 
being the 17th and 23rd of February, so the 24-48 hours their 
autoresponder claims is clearly a joke.  I've also submitted a contact 
to ipligence as they seem to be the geolocation provider in use as they 
are the only one with the bad geolocation data and it matches what 
Washington Gas claims, but no response there either and their site still 
shows the bad data more than a month later.


I've added the one person I could find at Washington Gas via searching 
around to the second and third requests but it seems no one is even 
looking at their email and they will not help via the phone saying it's 
a different department and to email, at this point I'm not sure what to 
do other than reach out here to hopefully find someone with a clue, try 
publicly calling out on twitter, and possibly file a complaint with the 
regulators as that seems the only way they might bother to even reply.


If anyone at either company is here please contact me or if anyone has a 
contact at either company I can try please let me know.


Thanks,
Glenn

equifax technical contact

[Dennis Burgess]

If a Equifax.com tech/engineer can contact me off-list that would be great, or 
if someone has a number/email that would be great as well ..

Thanx in advance.


[LTI-Full_175px]
Dennis Burgess

Mikrotik : Trainer, Network Associate, Routing Engineer, Wireless Engineer, 
Traffic Control Engineer, Inter-Networking Engineer, Security Engineer, 
Enterprise Wireless Engineer
Hurricane Electric: IPv6 Sage Level
Cambium: ePMP

Author of "Learn RouterOS- Second Edition"
Link Technologies, Inc -- Mikrotik & WISP Support Services
Office: 314-735-0270  Website: 
http://www.linktechs.net
Create Wireless Coverage's with www.towercoverage.com
Need MikroTik Cloud Management: https://cloud.linktechs.net
How did we do today?
[Gold 
Star][Green
 
Light][Yellow
 
Light][Red
 
Light]

Re: Spamhaus flags any IP announced by our ASN as a criminal

[Martin Hotze]

> Date: Mon, 20 Mar 2023 14:15:08 -0700
> From: Randy Bush 
> Subject: Re: Spamhaus flags any IP announced by our ASN as a criminal network
>
(...)
>
> we reject automagically on spamhaus, mail-abuse.org, and sorbs.  really
> appreciate their services.
>
> randy
>

Sorbs? Really? *doh*

#m