Just a guy in Vermont trying to connect all the dots...
Author's posts
Feb 26
TDYR #112 – Getting Ready For IETF 89 Next Week In London
Feb 26
6 Sessions About IPv6 At IETF 89 Next Week In London
As you might expect, IETF 89 next week in London will be filled with activity related to IPv6. My colleague Phil Roberts writes today in “Rough Guide to IETF 89: All About IPv6“:
While the standard for IPv6 has long-since been finished, there are ongoing discussions in the IETF of maintenance issues in the protocols, IPv6 operational issues and management, and possible uses in home networks and very large-scale networks (of small scale devices). Many of these discussions will happen next week in London next week.
Phil goes on to write a bit more in detail about what is happening within the 6man and v6ops working groups at IETF 89 next week.
Given our focus on IPv6 here at Deploy360, it should come as no surprise that you’ll be able to find our team at pretty much all of the working groups focused around IPv6. We’ll be in homenet looking at IPv6 in home networks, v6ops discussing operational issues, 6man to look at maintenance of the IPv6 specification, sunset4 to talk about how we phase out IPv4 and 6lo and 6tisch to look at IPv6 in low power or resource-constrained networks. Beyond these groups, of course, there will be many others that discussion IPv6, but these are the main groups we’ll be focusing on.
Relevant Working Groups
homenet (Home Networking) WG
Tuesday, March 4, 2014, 0900-1130 UTC, Sovereign Room
Agenda: https://datatracker.ietf.org/meeting/89/agenda/homenet/ (not yet posted)
Documents: https://datatracker.ietf.org/wg/homenet/
Charter: https://datatracker.ietf.org/doc/charter-ietf-homenet/
6man (IPv6 Maintenance) WG
Tuesday, March 4, 2014, 1610-1840 UTC, Viscount Room
Agenda: https://datatracker.ietf.org/meeting/89/agenda/6man/
Documents: https://datatracker.ietf.org/wg/6man/
Charter: https://datatracker.ietf.org/doc/charter-ietf-6man/
v6ops (IPv6 Operations) WG
Wednesday, March 5, 2014, 0900-1130 UTC, Sovereign Room
Thursday, March 6, 2014, 1300-1500 UTC, Sovereign Room
Agenda: https://datatracker.ietf.org/meeting/89/agenda/v6ops/
Documents: https://datatracker.ietf.org/wg/v6ops/
Charter: https://datatracker.ietf.org/wg/v6ops/charter/
6lo (IPv6 over Networks of Resource Constrained Nodes) WG
Wednesday, March 5, 2014, 1520-1730 UTC, Balmoral Room
Agenda: https://datatracker.ietf.org/meeting/89/agenda/6lo/
Documents: https://datatracker.ietf.org/wg/6lo/
Charter: https://datatracker.ietf.org/doc/charter-ietf-6lo/
sunset4 (Sunsetting IPv4) WG
Thursday, March 6, 2014, 0900-1130 UTC, Palace C
Agenda: https://datatracker.ietf.org/meeting/89/agenda/sunset4/(combined with the Multiple Interface (mif) WG meeting)
Documents: https://datatracker.ietf.org/wg/sunset4/
Charter: http://tools.ietf.org/wg/sunset4/charters
6tisch (IPv6 over TSCH mode of 802.16e4)
Thursday, March 6, 2014, 1300-1500 UTC, Buckingham Room
Agenda: https://datatracker.ietf.org/meeting/89/agenda/6tisch/
Documents: https://datatracker.ietf.org/wg/6tisch/
Charter: https://datatracker.ietf.org/doc/charter-ietf-6tisch/
Remote Participation
You don’t have to be in London to participate in the meetings of IETF 89. You can also:
- Listen to live audio streams.
- Participate in Jabber chat rooms to ask questions.
- Download the slides planned for each session.
- Listen and watch “Meetecho” conferencing sessions that provide an integrated view of slides, audio, chat and video.
Information about how to participate can be found on the IETF 89 Remote Participation page. Keep in mind that times for London are in UTC.
Feb 25
TDYR #111 – New Report Out About Protecting Against DDoS Attacks On DNS
Feb 25
What Devices And Software Support The Opus Audio Codec? Here Is A List
What devices support the Opus audio codec? What softphones? hardphones? call servers? Obviously given that Opus is the "mandatory to implement" audio codec for WebRTC, it will be in many web browsers... but what other I was asked this question by a colleague recently and when I couldn't easily find a list on the Opus codec web site, I turned to the VUC community inside of Google+ and posted there. The great folks there naturally were a huge help, and quickly came up with this list:
- Web browsers supporting WebRTC:
- Google Chrome
- Mozilla Firefox
- Softphones:
- Blink
- Counterpath Bria
- Jitsi
- Linphone
- Mumble
- (Maybe Skype? They talked about it.)
- "Hard" IP phones:
- Mobile applications:
- Acrobits (iOS)
- Counterpath Bria (iOS)
- csipsimple (Android)
- Switches / Call Servers / IP-PBXs:
What other devices or software supports the Opus codec? (Or what other lists are out there listing devices supporting the Opus codec?) Please do let me know either by comments here or on social media.
Thanks!
P.S. If you don't understand WHY the Opus codec matters so much, please read my earlier post on this topic.
If you found this post interesting or useful, please consider either:
- following me on Twitter;
- adding me to a circle on Google+;
- following me on App.net
- subscribing to my email newsletter; or
- subscribing to the RSS feed
Feb 25
SSAC Issues New Report On DDoS Attacks Against DNS
What can be done to prevent Distributed Denial of Service (DDoS) attacks against the DNS infrastructure? What can individuals or organizations who operate DNS servers do to their own systems to help reduce the threat of DDoS attacks? ICANN’s Security and Stability Advisory Committee (SSAC) took on this issue recently and released a new report this week: “SAC065: SSAC Advisory on DDoS Attacks Leveraging DNS Infrastructure“. It is available as a free PDF download in English.
While the report is not about DNSSEC, per se, it is about the overall issue of “DNS security” and outlines steps that can be taken to reduce the potential of DNS-based DDoS attacks. This is critical if we are to get DNSSEC more widely deployed because there are some DNS server operators who have pushed back about DNSSEC citing concerns about the larger size of DNSSEC packets could help amplify DDoS attacks.
The recommendations for the industry include the following (with the report providing more detail on each):
Recommendation 2: All types of network operators should take immediate steps to prevent network address spoofing.
Recommendation 3: Recursive DNS server operators should take immediate steps to secure open recursive DNS servers.
Recommendation 4: Authoritative DNS server operators should investigate deploying authoritative response rate limiting.
Recommendation 5: DNS operators should put in place operational processes to ensure that their DNS software is regularly updated and communicate with their software vendors to keep abreast of latest developments.
Recommendation 6: Manufacturers and/or configurators of customer premise networking equipment, including home networking equipment, should take immediate steps to secure these devices and ensure that they are field upgradable when new software is available to fix security vulnerabilities, and aggressively replacing the installed base of non-upgradeable devices with upgradeable devices.
We agree with those recommendations and definitely encourage people to read the SSAC report and implement as many recommendations as possible.
Working together we can make the Internet more secure!
Feb 24
TypePad To Start Using Akismet To Fight Blog Comment Spam
All my new blogs and other sites are over on WordPress where I've been very happy with the anti-spam services that I get from Akismet. (And some day I'd like to move this blog and Disruptive Telephony over to WordPress, too - if only I can carve out the considerable time that will be involved with the move.)
I'm pleased to see TypePad moving this way. It may not be enough to get me to stop using full moderation on my articles... but hopefully it should mean fewer spam comments to look at in the admin interface.
If you found this post interesting or useful, please consider either:
- following me on Twitter;
- adding me to a circle on Google+;
- following me on App.net;
- subscribing to my email newsletter; or
- subscribing to the RSS feed.
Feb 24
TDYR #110 – The Power Of Hacker News And Reddit To Drive Attention To Your Content
Feb 24
3 Sessions About Securing BGP At IETF89 Next Week
Next week at IETF 89 in London there will be a good bit of discussion around the security and resilience of the Internet’s routing infrastructure. Given our interest in securing BGP, members of our team will be attending the SIDR, GROW and IDR Working Groups next week and engaging in other routing discussions as well.
My colleague Andrei Robachevsky wrote about routing as part of the IETF 89 “Rough Guide” today and explained some of the activities that will be happening during the week. I’d encourage you to read his post as he goes into some detail about the different drafts that are being considered by the three working groups.
Relevant Working Groups
SIDR (Secure Inter-Domain Routing)
Tuesday, March 4, 0900-1130 UTC, Balmoral Room
WG Agenda: https://datatracker.ietf.org/meeting/89/agenda/sidr/
Documents: https://datatracker.ietf.org/wg/sidr/
Charter: https://datatracker.ietf.org/wg/sidr/charter/
GROW (Global Routing Operations)
Tuesday, March 4, 1300-1400 UTC, Blenheim Room
WG Agenda: https://datatracker.ietf.org/meeting/89/agenda/grow/ (not yet available)
Documents: https://datatracker.ietf.org/wg/grow/
Charter: https://datatracker.ietf.org/wg/grow/charter/
IDR (Inter-Domain Routing Working Group)
Thursday, March 6, 1300-1500 UTC, Blenheim Room
WG Agenda: https://datatracker.ietf.org/meeting/89/agenda/idr
Documents: https://datatracker.ietf.org/wg/idr/
Charter: https://datatracker.ietf.org/wg/idr/charter/
Remote Participation
You don’t have to be in London to participate in the meetings of IETF 89. You can also:
- Listen to live audio streams.
- Participate in Jabber chat rooms to ask questions.
- Download the slides planned for each session.
- Listen and watch “Meetecho” conferencing sessions that provide an integrated view of slides, audio, chat and video.
Information about how to participate can be found on the IETF 89 Remote Participation page. Keep in mind that times for London are in UTC.
Feb 24
