- Test - lists.nanog.org

Re: Announcing Peering-LAN prefixes to customers
by John Kristoff 16 Jan '19

16 Jan '19

On Wed, 16 Jan 2019 16:39:32 +0000 Christoffer Hansen <christoffer(a)netravnen.de> wrote: > You could do the same trick. But with data fetched from PeeringDB via > the public API. Works well. I think that is essentially what the service does, but in a BGP feed and maintained for you, kind of like the bogons service. John

1 0

Call for Participation -- ICANN DNSSEC Workshop at ICANN64 Kobe, Japan
by Jacques Latour 16 Jan '19

16 Jan '19

Call for Participation -- ICANN DNSSEC Workshop at ICANN64 Kobe, Japan The DNSSEC Deployment Initiative and the Internet Society Deploy360 Programme, in cooperation with the ICANN Security and Stability Advisory Committee (SSAC), are planning a DNSSEC Workshop during the ICANN64 meeting held from 09-14 March 2019 in Kobe, Japan. The DNSSEC Workshop has been a part of ICANN meetings for several years and has provided a forum for both experienced and new people to meet, present and discuss current and future DNSSEC deployments. For reference, the most recent session was held at the ICANN Annual General Meeting in Barcelona, Spain, on 24 October 2018. The presentations and transcripts are available at: https://63.schedule.icann.org/meetings/901549, and https://63.schedule.icann.org/meetings/901554, and https://63.schedule.icann.org/meetings/901555. At ICANN64 we are particularly interested in live demonstrations of uses of DNSSEC, DS automation or DANE. Examples might include: * DNSSEC automation and deployment using CDS, CDNSKEY, and CSYNC * DNSSEC/DANE validation in browsers and in applications * Secure email / email encryption using DNSSEC, OPENPGPKEY, or S/MIME * DNSSEC signing solutions and innovation (monitoring, managing, validation) * Tools for automating the generation of DNSSEC/DANE records * Extending DNSSEC/DANE with authentication, SSH, XMPP, SMTP, S/MIME or PGP/GPG and other protocols Our interest is to provide current examples of the state of development and to show real-world examples of how DNSSEC and DANE related innovation can be used to increase the overall security of the Internet. We are open to presentations and demonstrations related to any topic associated with DNSSEC and DANE. Examples of the types of topics we are seeking include: 1. DNSSEC Panel (Regional and Global) For this panel, we are seeking participation from those who have been involved in DNSSEC deployment in the region and also from those who have not deployed DNSSEC but who have a keen interest in the challenges and benefits of deployment. In particular, we will consider the following questions: Are you interested in reporting on DNSSEC validation of your ISPs? What can DNSSEC do for you? What doesn't it do? What are the internal tradeoffs to implementing DNSSEC? What did you learn in your deployment of DNSSEC? We are interested in presentations from both people involved with the signing of domains and people involved with the deployment of DNSSEC-validating DNS resolvers. 2. DS Automation We are looking at innovative ways to automate the parent child synchronization CDS / CDNSKEY and methods to bootstrap new or existing domains. We are also interested in development or plans related to CSYNC, which are aimed at keeping the glue up to date. We would like to hear from DNS Operators what their current thoughts on CDS/CDNSKEY automation are. 3. DNSSEC/DANE Support in the browsers We would be interested in hearing from browser develop what their plans are in terms of supporting DNSSEC/DANE validation. 4. DANE Automation For DNSSEC to reach massive deployment levels it is clear that a higher level of automation is required than is currently available. There also is strong interest for DANE usage within web transactions as well as for securing email and Voice-over-IP (VoIP). We are seeking presentations on topics such as: * How can the industry use DANE and other DNSSEC applications as a mechanism for creating a more secure Internet? * What tools, systems and services are available to help automate DNSSEC key management? * Can you provide an analysis of current tools/services and identify gaps? * What are some of the new and innovative uses of DANE and other DNSSEC applications in new areas or industries? * What tools and services are now available that can support DANE usage? We would be particularly interested in any live demonstrations of DNSSEC / DANE application automation and services. Demonstrations of new tools that make the setup of DNSSEC or DANE more automated would also be welcome. If you are interested in participating, please send a brief (1-2 sentence) description of your proposed presentation to dnssec-kobe(a)isoc.org' before ** 07 February 2019 ** We hope that you can join us. Thank you, Jacques Latour On behalf of the DNSSEC Workshop Program Committee: Jean Robert Hountomey, AfricaCERT Jacques Latour, .CA Russ Mundy, Parsons Ondřej Filip, CZ.NIC Yoshiro Yoneya, JPRS Dan York, Internet Society Mark Elkins, DNS/ZACR

1 0

Fwd: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting
by Christoffer Hansen 16 Jan '19

16 Jan '19

Sent to NANOG, Anyone from NETFLIX subscribed? Could you please fix the below type notification e-mails to ALSO be available if one ONLY USES PLAIN-TEXT email clients? Currently the notice information is formatted in such a way the PLAIN-TEXT section is completely EMPTY. ONLY the HTML section contains information. (E-mail client on my case is Thunderbird) -- Cheers Christoffer -------- Forwarded Message -------- Subject: (Netflix/***) Scheduled Open Connect Appliance upgrade is starting Resent-From: *** Date: *** Jan 2019 *** From: Netflix <info(a)mailer.netflix.com> Reply-To: no_reply(a)netflix.com To: *** Netflix Hello ***, The scheduled upgrade of your Open Connect Appliance(s) (OCAs) is beginning now. The list of affected appliances is: IP Address Name Facility *** *** ***

31 61

Re: the e-mail of the future is the e-mail oft the past, was Enough port 26 talk...
by John R. Levine 16 Jan '19

16 Jan '19

> And you won't really have a choice because unless you're willing to go > full Ted Kaczynski one in a hundred of those emails will be very, very > important to you ... Yeah. E-mail remains the only scheme where the two parties don't have to be introduced first, don't have to be online at the same time, and you can check for it in one place (if you want to, or you can sort and file to your heart's content.) I've stopped being surprised that enthusiasts who tell me that the IM or online conferencing silver bullet du jour will kill e-mail never understand this. R's, John

8 7

Re: plaintext email?
by valdis.kletnieks＠vt.edu 15 Jan '19

15 Jan '19

Without reading further... which of your recent postings is this a reply to? Obviously you already know, because you said you don't need to see the text to know the context... Nope, it wasn't the one about how things became quoted text. On Tue, 15 Jan 2019 13:36:38 -0500, bzs(a)theworld.com said: > I use Emacs/VM for email. It's quite good at, for example, splitting > the screen so I can look ahead (or behind) in the message if I've lost > track of some context, or even opening multiple related msgs (even if > already filed) simultaneously to go back and review what's been said > already, or forward even to see if one is about to say something which > has already been adequately addressed. And how many times did you have to hit control-alt-meta-cokebottle to trace out which one this was really a reply to?

2 1

ASNs decimation in ZW this morning
by C. A. Fillekes 15 Jan '19

15 Jan '19

So @meileaben on twitter this morning notes: Many #*Zimbabwe* <https://twitter.com/hashtag/Zimbabwe?src=hash> Internet routes withdrawn around 9:30 UTC amidst civil unrest in the country. near-realtime on #*RIPEstat* <https://twitter.com/hashtag/RIPEstat?src=hash> here: https://stat.ripe.net/ZW <https://t.co/sgJ4O3310z> # *OpenNetworkIntelligence* <https://twitter.com/hashtag/OpenNetworkIntelligence?src=hash> # *ZimbabweShutdown* <https://twitter.com/hashtag/ZimbabweShutdown?src=hash> https://twitter.com/meileaben/status/1085118237157851136 wondering if anyone here has additional info on that. Looing at stat.ripe.net/ZW now it looks as though one (out of an original 18, current 9) ASN has recovered, but kind of curious as to what exactly happened there.

2 2

Cable/Wireless-Tower Map for the San Francisco Bay Coastside?
by Yosem Companys 15 Jan '19

15 Jan '19

Hey All, Does anyone know whether there's a map that shows the cable/wireless-tower map for the San Francisco Bay Coastside (i.e., from Montara to Half Moon Bay)? A few days ago, a truck hit a PG&E post on Highway 92, which traverses from San Mateo to Half Moon Bay. The accident caused the post to fall to the ground. The Coastside has one Comcast-owned, fiber-optic cable that crosses the mountains from Silicon Valley to the Coastside. I guess the cable must run on PG&E posts because not only did the accident cause a blackout in some areas of the Coastside but also the entire Coastside was left without almost any Cable TV, Internet, or mobile phone connectivity for practically 24 hours. I only have anecdotal evidence, but it seems that there was no Comcast or Verizon service whatsoever because Verizon leases the fiber-optic line from Comcast. It also seems that DirecTV and AT&T were not affected, and the theories vary as to why. Perhaps AT&T uses a combination of copper wire and wireless to service the area. DirecTV allegedly leases connectivity from AT&T. I've also heard that Sprint PCS paid the owner of a building near the El Granada post office to use it to relay a mobile signal from there. But when I asked on Nextdoor about the incident no one mentioned Sprint. In prior discussions, Coastside residents say they avoid Sprint and AT&T due to their spotty service. And I know nothing about T-Mobile. The reason I ask is because this is not the first time that Coastside residents have been left without mobile service, cable TV, and Internet connectivity. In fact, it seems to be a frequent phenomenon, making me wonder that if the infrastructure here is so fragile what would happen in the case of the "Big One" or, God forbid, a Tsunami or major storm surge. I understand that there's a plan for emergency responders to maintain Internet and mobile connectivity that includes microwave connectivity, but I have yet to obtain the details. So I'm trying to get as much data as I can to help local decision-makers figure out how to make the Coastside more resilient before the next disaster strikes. Thanks, Yosem

3 2

CAT-TP Protocol?
by Richard 14 Jan '19

14 Jan '19

If anyone can confirm my suspicion of what CAT-TP is I would be grateful. It is the first time I have seen it on a customer's network. I think it is for manipulating SIM cards, but I have been mistaken before. Off list replies are fine. Thanks, Richard Golodner

2 1

SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request]
by Viruthagiri Thirumavalavan 14 Jan '19

14 Jan '19

Hello NANOG, Belated new year wishes. I would like to gather some feedback from you all. I'm trying to propose two things to the Internet Standard and it's related to SMTP. (1) STARTTLS downgrade protection in a dead simple way (2) SMTPS (Implicit TLS) on a new port (26). This is totally optional. I posted my proposal in IETF mailing list. I got very good feedback there. Some support my proposal. Many are against it. I would love to know where you stand on this proposal. Let me give you the abstract first. ----- SMTP is still suffering from downgrade attacks like STRIPTLS. While we have "Opportunistic TLS", we still don't have "Implicit TLS" in the SMTP. Don't take this in the wrong way. We do have "Implicit TLS" for "SMTP Submission" on port 465. But we don't have a secure port 25 alternative. i.e. The real SMTPS Both MTA-STS and MTA-DANE tries to fix the STARTTLS downgrade issue. However the implementation is not simple. The former requires a HTTPS server and the latter requires DNSSEC to even get started. This proposal fixes STARTTLS downgrade issue and propose a new port 26, an "Implicit TLS" alternative for port 25 and recommends the MX server to signal the port via a prefix. This proposal offers two ways. (1) STARTTLS Prefix Use this prefix only to deal with STARTTLS downgrade issue. e.g. mx1.example.com should be prefixed like starttls-mx1.example.com. Where "starttls-" says "Our port 25 supports Opportunistic TLS. So if STARTTLS command not found in the EHLO response or certificate is invalid, then drop the connection". (2) SMTPS Prefix Use this prefix if you wanna support Implicit TLS on port 26 and Opportunistic TLS on port 25. e.g. mx1.example.com should be prefixed like smtps-mx1.example.com. Where "smtps-" says "We prefer if you connect to our SMTPS in port 26. But we also accept mails in port 25. And our port 25 supports Opportunistic TLS. So if STARTTLS command not found in the EHLO response or certificate is invalid, then drop the connection". In "starttls-" prefix port 25 *MUST* support encryption with *valid SSL* certificates. In "smtps-" prefix, *BOTH* port 26 and port 25 *MUST* support encryption with *valid SSL* certificates. Note: You need to enable DNSSEC to prevent MX record spoofing. My proposal highly recommends DNSSEC. Not mandates that. ------- What IETF Mailing list thinks? - "Implicit TLS doesn't offer any additional security than a downgrade protected STARTTLS. Let's not waste a port." What I think? - Implicit TLS still fall under the "best practices". So it will send out the positive vibe that IETF still cares about email security. What the world thinks? - https://gist.github.com/mistergiri/138fc46ae401b7492662a32409edb07f What do you all think? - https://medium.com/@dombox/smtp-over-tls-on-port-26-efc67e8a99ce -- Best Regards, Viruthagiri Thirumavalavan Dombox, Inc.

25 62

Could Someone From Yahoo Mail Please Contact Me
by Matt Hoppes 14 Jan '19

14 Jan '19

Our customers who use yahoo.com e-mail addresses are saying they aren't receiving invoices from our billing system. I checked our mail logs and I'm getting this: Jan 12 16:11:34 account postfix/smtp[9802]: 1FA906C0E61: host mta7.am0.yahoodns.net[98.136.101.117] said: 421 4.7.0 [TSS04] Messages temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command) The link suggests several things to do and we've waited over 48 hours and still can't get invoices through. The invoice server is definitely not compromised, and honestly I can't imagine there would be enough complaints to trigger a global block of that IP address, and we only have a small number of customers using @epix.net e-mail addresses. Thanks!

5 5