Dan York

Just a guy in Vermont trying to connect all the dots...

Author's posts

TDYR 354 – Colon Cancer, Colonoscopies, Vermont, and Recovering from Surgery

It's been a while since I recorded an episode... and that had a great amount to do with being diagnosed with colon cancer after a routine screening colonoscopy. In this episode I talk about that test, the difficult choices, the surgery... all set in the context of also moving to Vermont! More info on my blog at: - http://www.danyork.com/2018/08/the-big-c-returns-as-colon-cancer-and-with-me-this-time.html - http://www.danyork.com/2018/09/post-surgery-recovery-every-day-brings-a-series-of-small-victories.html

Post-surgery recovery: Every day brings a series of small victories

Church street september 2018

I put on pants today.

Shorts, even.

With a belt!

This was a BIG deal.

It's not that I haven't been wearing pants 😉 ... but that I've only been able to wear running pants with an elastic waste since leaving the hospital on Thursady. My stomach was too bloated from the surgery and it hurt too much to wear anything else.

Until today.

Another small victory!

Never having had surgery before, I'm learning what countless others have learned before me - that each day brings a series of small victories, without hopefully any major defeats along the way.

To follow on my previous post, I did go in for surgery for colon cancer last Tuesday, August 28th. Technically, I guess it was a "Sigmoid Colon Resection" because I was diagnosed with "Malignant Neoplasm Of Sigmoid Colon", but let's put that in plain language...

"They found a small bit of cancer in my colon and so they went in and cut out about 12 inches of my colon and re-attached the other sections to each other."

A high-tech fix of my internal plumbing. Slice out a bad section and re-connect the other open ends.

I went in at 11am and woke up several hours later in a hospital bed feeling like someone had stabbed me and cut me in the stomach! I also apparently had a rather pleasant conversation with my family... of which I remember absolutely nothing! Some time later when the anesthesia fully wore off, I was able to see them all and remember.

I was in the hospital all day on Wednesday but then by Thursday morning I was able to go home!

All along the way it was this series of small but ever-so-important victories! Passing gas and pooping turned out to be the first critical steps... which makes sense given that you want to be sure the pipes got all reconnected.

Then it was walking around the hospital floor, eating solid food, drinking lots of water, etc.

After coming home it was climbing the steps... taking a long, slow, slow, slow walk around the neighborhood. Trying to find some comfortable way to sleep. And so on.

Then it moved on to walking at a more normal pace and moving around more regularly. Saturday we walked around Church Street (photo above) and the Burlington Farmers Market. Sunday I drove the minivan and we took the ferry across Lake Champlain to visit Essex, NY. Today I put on pants. 😊

It's not all normal, of course. I tire easily and have needed afternoon naps. I'm still not sleeping through the night. And I have metal staples protruding from my stomach that I have to be very careful about! While I can eat almost everything, a big restriction is on raw fruits and vegetables, which is something I enjoy eating. (Raw fruits and vegetables (except bananas) turn out to be harder to digest, particularly the skins, and the doctors want only soft things passing through my newly-reconnected colon. (Cooked and mushy vegetables are fine.))

I'm very amazed and obviously pleased at how the recovery is going. The doctors had said that patients were generally in the hospital for 1-5 days, with most people being in 2-3 days... I'm glad I wound up on the low end of that. I'm also pleased that so far I've been able to manage the pain using only the Tylenol and have not had to use any narcotics/opiods.

Thank you to the many who have held me in their thoughts and prayers, or sent positive thoughts, or who just sent me nice messages. All seems good so far.

Tomorrow I'll try being back at work for a bit. Somewhere in here I'll get the staples out (10 days-ish).

Each day a few more victories!

Now, we just wait for the biopsies, which should come "in a week or so". Sigh...

Call for Participation – ICANN DNSSEC Workshop at ICANN63 Barcelona

Do you have a great idea about DNSSEC or DANE that you’d like to share with the wider community? If so, and you’re planning to be in Barcelona, Spain for ICANN63 in October 2018, submit a proposal to present your idea at the DNSSEC Workshop!

Send a brief (1-2 sentence) description of your proposed presentation to dnssec-barcelona@isoc.org by Friday, 07 September 2018.

For more information, read the full Call for Participation below.

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 ICANN63 meeting held from 20-25 October 2018 in Barcelona, Spain. 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 Policy Forum in Panama City, Panama on 25 June 2018. The presentations and transcripts are available at:https://62.schedule.icann.org/meetings/699560, and https://62.schedule.icann.org/meetings/699556
At ICANN63 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. Post KSK Rollover
Following the Root Key Rollover, we would like to bring together a panel of people who can talk about lessons learned from this KSK Rollover and lessons learned for the next time
3. 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-barcelona@isoc.org by **07 September 2018 **
We hope that you can join us.
Thank you,
Kathy Schnitt
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

The post Call for Participation – ICANN DNSSEC Workshop at ICANN63 Barcelona appeared first on Internet Society.

The Big C Returns As Colon Cancer… and with me this time

BTV harbor

---

"I'm sorry, but unfortunately one of your polyps tested positive for colon cancer."

Not the phone call you want to receive at 4:00pm on a Friday afternoon. Especially one week before you are about to buy a house in Vermont and start the process of relocating your family - and leaving behind your friends, other family members, and your whole "support system"! 

In truth, not a phone call you EVER want to receive.

But I did get that call on June 29, 2018. And after many more tests, discussions and agonizing analysis, I'll be entering the hospital in a week, on August 28, to have my "sigmoid" removed - something I honestly didn't even know I had until about three weeks ago!

So a key message to all my friends and readers (and the "TL;DR" summary for this very long post):

Get your colonoscopy when you turn 50!

Don't delay. Don't wait. Just do it.

Here in the USA when we hit the magical age of 50[1], the healthcare system strongly recommends that we get a whole suite of various tests done. Perhaps the least favorite of those is the "screening colonoscopy", largely because the preparation is a huge, uncomfortable process. And, let's be honest, who really wants to have a metal probe stuck up their bottom?

But do it.

I almost didn't. As it was, I delayed doing it for 8 months. And with our decision to uproot our lives and move to Vermont, it was EXTREMELY tempting to push it off and "just wait until we are settled" ... which probably would have been next year... or the year after... or who knows when.

Had I delayed, the one very small cancerous "polyp" might have spread to much more of my colon. Or it might have spread ("metastasized" in cancer-speak) into other parts of my body and re-appeared as lung cancer or liver cancer or brain cancer or something else. (Or, in the annoying ways of cancer, it might not have done anything and just still been there alone - but do you want to take that chance?)

I was lucky. The test worked. The cancer was found very early. By all signs after the surgery next week I should be good to go for a long time ahead.

So don't wait. Just do it.


The longer story...

When the doctor at the Cheshire Medical Center in Keene, NH, did my colonoscopy, he found three small "polyps". Think of a polyp as a tiny growth shaped kind of like a lollipop. And by "tiny", all of these were 2-5 millimeters in width - not much more than a couple of hairs!

This was on Wednesday, June 27. The doctor thought they all looked small and, while we had to wait for the tests ("biopsies"), his initial reaction was that they did NOT look like they were cancerous. (They looked "benign" in medical lingo.)

So I went home with the attitude "Okay... done the colonoscopy thing. I can now forget about this until the next one in 10 years and focus on packing more boxes."

After all, other than needing to lose maybe 30 pounds, I'm in good physical condition. I have no medical issues. I'm not on any medications. I run a good bit - and past tests have shown my heart in good shape. All my routine physical tests and blood work at 50 show me to be in good health.

Except, it turns out, for that one damn polyp.

That call on Friday (two days later) led to a rush of tests the following week - a MRI, more blood tests, and a "flexible sigmoidoscopy" (a mini-colonoscopy where they just go in a little ways... and you can be conscious and watch it on the computer monitor!). Lori and I had all the agony of the question - "shall we pull the plug on this whole Vermont move?" It was INSANELY stressful.

The good news was - everything came back negative. No markers in my blood for cancer. No cancer found in any of the biopsies of the additional samples they took in the colon wall around where the polyp was found.

In theory, the one polyp they found might have been ALL the cancer in my body!

Now that they removed it, I might be "cancer free".

However... the cancer was unfortunately not just in the main "head" part of the polyp, it was also all the way down the "stem" (think of a lollipop). 

It could have gone into the wall of the colon, somewhere beyond where they were able to sample. It could have gone out into the lymph nodes surrounding the colon - and could hang out there for a while before it goes somewhere else in my body. There were no signs of it anywhere, but the current state of our technology is such that we can't really know.

And... apparently the precise kind of cancer they found was a more aggressive one that could "metastasize" into other forms of cancer elsewhere in my body.

So, after being reviewed by my new set of doctors at the UVM Medical Center in Burlington, VT, and after more tests (including another video tour of my lower colon), the surgeon presented a rather binary choice:

  • DO NOTHING and just keep monitoring it. There is a small 2-5% chance that the cancer could come back. Or, to flip that around, there is a 95 - 98% chance that I have no more cancer and could live the rest of my life without ever being affected by this particular cancer.
     
  • HAVE SURGERY to remove the "sigmoid" (lower part of what I thought was all the "colon") and reconnect the other parts of the colon. This will allow them to completely test the colon walls and surrounding lymph nodes in the removed section to see if there is any more cancer. BUT... it comes with it's own 2-3% chance that there could be complications with the surgery - and some of those could be nasty.

He said he's had patients make either choice - and it really comes down to my own personal comfort level with either the surgery or living with the risk.

Ugh. Did I mention that I'm in otherwise good health? And so do I really want to mess that up by having people go in, cut me up, and re-arrange my plumbing?

But the choice is clear to me. Lori and I have been down this road before. We both learned far more than we ever imagined about cancer after she was diagnosed with breast cancer in 2011 - and after she had surgery and subsequent rounds of chemotherapy and more.

We live every day with the specter of her cancer looming in the background. Unlike what they tell me about my colon cancer after surgery, her cancer could come back at any time. And in some other form. You're never really "cured" of breast cancer. Even after all she has done - and the absolute hell she has put her body through, it could still be there lurking. So you learn to be grateful for every day you have.

So, hell yeah, I want to know, even with all my many concerns about the surgery (and never having had surgery before). I don't want a second specter lurking around.

From what I've now learned, colon cancer is much more localized than breast cancer or other forms. If they go in, take out the sigmoid and the surrounding lymph nodes, they can test it all and give me fairly solid results.

In the best case, they find nothing and I can be reasonably sure they got it all. I'll be as close to "cancer free" as someone with colon cancer can be. (There are NO guarantees.)

In the worst case, they find more cancer cells and then we will have to talk chemotherapy or something else.

Either way, we'll know more.

So one week from today I'll be entering the UVM Medical Center. They say I will need to stay there for typically 2-3 days to recover. (Visitors will be welcome!) In theory I'll be able to resume everything I've been doing - and by 3-4 weeks out I should be more or less back to usual activities. I'll now be getting more monitoring and more frequent colonoscopies (oh, joy!), but the theory goes that, in the best case, this should be the end of it.

The good news out of this (as I have to keep reminding myself!) is that the screening colonoscopy WORKED!

The test found the cancer early. Because of that, there is a very strong chance that after this surgery I'll be all set and won't have to worry about this again. I'll be alive and able to live for as many decades (or days) as I have ahead of me. I'll be able to watch my daughters grow up and to live long with Lori.

I'm so grateful to the doctors and technicians - and for the fact that I have access to tests like this (and insurance that covers it). And perhaps most of all... for the fact that I didn't delay having the test even more than I already had.

 

I write all of this story because, as a writer, this is HOW I process things. The act of putting words down on a screen... the act of naming in words those fears... those actions are how my brain makes things real.

I share this publicly in the hopes that perhaps MY story will help someone else take actions that may help them live a longer life. (Even if you make a different choice than I did.)

So, again, I will say to anyone reading - if you are recommended to get a colonoscopy, DO IT!


[1] The American Cancer Society is now (May 2018) recommending that colon cancer screening start at age 45 versus 50, but I don't know that that recommendation has yet made its way out to healthcare providers and insurance companies.

Image: a photo I took of the Burlington harbor. I just thought I'd use it as a reminder of the beauty of life around me.

Moose and bear – the perils of Vermont highways

C85C451D-5899-4D2A-BCA3-F37350C76ADB“BEAR CROSSING - STAY ALERT”  The bright yellow sign shouts its warning to me from the side of Interstate 91. I am in the middle of Vermont. There are few people here. Most of the time I-91 has walls of trees on either side, occasionally broken by amazing mountain views  or scenic views of small towns. 

And so we are warned of bears and... moose!

“MOOSE CROSSING - NEXT 5 MILES”

I have seen the photos of damage caused by moose. You have a 2,000 pound animal on thin, spindley legs. Knock out the legs and the main bulk of the body comes crashing down on you! New Hampshire has regular warnings about the number of people who have died due to moose collisions up in the northern part of the state. 

Bears, though, are new. Not sure what I would do if I saw one.  😬

The fascinating flow of free stuff from in front of our house

442E4587-C31C-477B-9FB3-9A8187133085“FREE” says the sign pinned to the telephone pole in front of our house. And as we put out items, they usually disappear within a few hours. 

It’s been a fascinating aspect of living where we do in Keene, New Hampshire. We live on a fairly busy cross street, and so a good number of people are driving by. 

And they do stop and take the stuff we put on the street. All of it. 

Maybe it is part of being a college town. Maybe it is the huge number of people we see going to yard sales. Maybe it is Yankee frugality. Maybe it is just human nature. 

But it has been fun - and incredibly useful. Just put it out on the grassy strip between the sidewalk and the road... and wait a bit. 

And ALL sorts of things. Just yesterday I put out two plastic shelving units from our shed that had gas and oil stains. I honestly thought I would be bringing them to the dump... but no, I looked an hour or so later and they were gone. 

I will miss this culture of picking up free stuff. Our new home in Vermont is in a quieter neighborhood with very little traffic... so this won’t work. 

Meanwhile, at least for the next few days, I will keep putting stuff out there... 🙂

Revisiting a Not-So-New Rule – No Social Media Usage Until I Have Created Something New

Being a writer not being distracted

I woke up this morning frustrated that I simply haven’t been writing across my various sites. In theory I am a “writer”, but I haven’t been writing! And as I wrote in My 3 Words for 2018: “because if I don't write... the stories build up inside of me until they want to explode like a pressure cooker without a relief valve. Writing is my relief valve. I need to do it.

So I said to myself- I know, I will impose a new rule on myself... no social media usage until I publish something new! A blog post, a podcast episode (such as my The Dan York Report short audio segments), an article on some site (ex CircleID), a longer update on a social site... something.... anything.... BEFORE I get sucked into the vortex of social media updates. 

And I will start with a blog post like this one...

Except... I discovered I WROTE THE EXACT SAME POST TWO YEARS AGO! July 24, 2016, to be precise.

And... I noted that on day #2, July 25, 2016, I had already failed. ☹️

So this morning’s great idea turns out to be nothing new. 

In fact, I can go back 10 years ago, to a post in September 2008, where I wrote about Jeremiah Owyang’s “Pay yourself first” philosophy. Or may many other posts about struggling with consistent writing.

Now, maybe this rule is like the “no sweets today” diet rule that turns out to be an aspiration that just doesn’t happen. And maybe EVERY day is too high a goal. Maybe every other day. But I have to do something, or consumption will win over creation. 

Unless, of course, I want to reframe my own perspective and think of myself as an “occasional writer”... and just accept only writing now and then  

I am not quite ready for that. Let’s see how I do this year!

 

TDYR 353 – Podcasting as a Team-building Exercise?

How can you use podcasting or live online radio as a team-building exercise? What happens when you take 16 people, 10 of whom have never done anything with audio, and tell them that in 4 hours they have to stream an hour of live audio on the public Internet? In this episode, Neville Hobson and I talk about exactly this experience! This segment with Neville was actually my weekly report into the For Immediate Release (FIR) podcast hosted by Shel Holtz. It was part of FIR #146 on July 16, 2018. You can hear the entire show at https://firpodcastnetwork.com/fir-146-is-business-dropping-the-e-in-peso/ You can learn more about Neville at: http://www.nevillehobson.com https://twitter.com/jangles The company that did the exercise we talked about is at http://liveat3.today

TDYR 352 – Excited for the start of IETF 102 in Montreal

The 102nd meeting of the Internet Engineering Task Force (IETF) starts today in Montreal with over 1,000 engineers coming together from around the world to make the Internet work better. It’s an amazing event and I give a preview in this episode. Visit https://www.ietf.org/live to follow along this week.

Rough Guide to IETF 102: DNSSEC, DNS Security and Privacy

DNS privacy will receive a large focus in the latter half of the IETF 102 week with attention in the DPRIVE, DNSSD, and OPSEC working groups. In an interesting bit of scheduling (which is always challenging), most of the DNS sessions are Wednesday through Friday. As part of our Rough Guide to IETF 102, here’s a quick view on what’s happening in the world of DNS.

Given that IETF 102 is in Montreal, Canada, all times below are Eastern Daylight Time (EDT), which is UTC-4.

IETF 102 Hackathon

The “DNS team” has become a regular feature of the IETF Hackathons and the Montreal meeting is no different. The IETF 102 Hackathon wiki outlines the work that will start tomorrow (scroll down to see it). Major security/privacy projects include:

Anyone is welcome to join the DNS team for part or all of that event.

DNS Operations (DNSOP)

The DNS sessions at IETF 102 start on Wednesday morning from 9:30am – 12noon with the DNS Operations (DNSOP) Working Group. Paul Wouters and Ondrej Sury will be speaking about “Algorithm Implementation Requirements and Usage Guidance for DNSSEC“, where they will be offering updated guidance around what cryptographic algorithms should be used for different aspects of DNSSEC.  Shumon Huque will be bringing the latest updates to draft-huque-dnsop-multi-provider-dnssec, exploring how to deploy DNSSEC in environments where multiple DNS providers are in use. Paul Wouters will also bring a new draft, draft-pwouters-powerbind, which introduces a new flag for DNSSEC keys that can address a potential attack. Given the critical role DNS plays, the DNSOP agenda has many other drafts up for discussion and action. The DNSOP working group also has a second meeting block on Thursday from 18:10-19:10.

DNS PRIVate Exchange (DPRIVE)

The DPRIVE working group meets Wednesday afternoon from 13:30-15:00 EDT.  As shown on the agenda, there will be three major blocks of discussion. After some initial discussion of current work on existing DNS privacy policies, there will be a larger discussion about some new work called “Oblivious DNS” that aims to make DNS privacy protection even stronger. This work originated in a paper at Princeton University – https://odns.cs.princeton.edu/ – and now is captured in draft-annee-dprive-oblivious-dns. It should be quite an interesting discussion!

The third major area will continue discussion about how to add privacy to the communication between a DNS recursive resolver and the authoritative DNS server for a given domain.  This is work outside the current  DPRIVE Working Group charter and so the group will be discussing whether to ask to expand their mandate to cover this new work.

Extensions for Scalable DNS Service Discovery (DNSSD)

Privacy will also get attention at the DNSSD Working Group on Thursday morning from 9:30-12:00 EDT.  DNSSD focuses on how to make device discovery easier across multiple networks. For instance, helping you find available printers on not just your own network, but also on other networks to which your network is connected. However in doing so the current mechanisms expose a great deal of information. The agenda allocates 65 minutes to Christian Huitema to guide a discussion around the way forward. Drafts under discussion include:

There are other drafts under discussion at DNSSD, but these are the ones probably most of interest to readers of this article.

DNS Resolver Identification and Use (DRIU)

IETF 102 will feature a number of Birds-of-a-Feather (BOF) sessions, and one in particular relates to DNS security. The quick description is:

The IETF has added additional methods for DNS stub resolvers to get to recursive resolvers (notably DNS-over-TLS, RFC 7858), and is about to add another (DNS-over-HTTPS, from the DOH Working Group). As these have been developed, questions have been raised about how to identify these resolvers from protocols such as DHCP and DHCPv6, what the security properties these transports have in various configurations (such as between strict security and opportunistic security), and what it means for a user who has multiple resolvers configured when the elements of the configured set have different transports and security properties.

The DRIU session will be on Thursday from 15:50-17:50, right before the second DNSOP session (although in a different room).

Operational Security Capabilities for IP Network Infrastructure

In the very last slot on Friday afternoon from 11:50-13:20, the OPSEC working group will feature Benno Overeinder speaking about “Recommendations for DNS Privacy Service Operators. This document outlines things DNS operators should thing about when considering offering “DNS privacy” services. It builds on the work coming out of the DPRIVE working group and the experience gained from the IETF Hackathon and the real-world deployment of these new protocols.

DNSSEC Coordination informal breakfast meeting

As a final note, on Friday morning before the sessions start we are planning an informal gathering of people involved with DNSSEC. We’ve done this at many of the IETF meetings over the past few years and it’s been a good way to connect and talk about various projects. True to the “informal” nature, we’re not sure of the location and time yet (and we are not sure if it will involve food or just be a meeting). If you would like to join us, please drop me an email or join the dnssec-coord mailing list.

Other Working Groups

DANE and DNSSEC will also appear in the TLS Working Group’s Monday meeting. The draft-ietf-tls-dnssec-chain-extension will be presented as a potential way to make DANE work faster by allowing both DANE and DNSSEC records to be transmitted in a single exchange, thus reducing the time involved with DANE transactions. Given the key role DNS plays in the Internet in general, you can also expect DNS to appear in other groups throughout the week.

P.S. For more information about DNSSEC and DANE and how you can get them deployed for your networks and domains, please see our Deploy360 site:

Relevant Working Groups at IETF 102:

DNSOP (DNS Operations) WG
Wednesday, 18 July 2018, 9:30-12:00 EDT, Laurier
Thursday, 19 July 2018, 18:10-19:10 EDT, Place du Canada

Agenda: https://datatracker.ietf.org/meeting/102/agenda/dnsop/
Documents: https://datatracker.ietf.org/wg/dnsop/
Charter: http://tools.ietf.org/wg/dnsop/charters/

DPRIVE (DNS PRIVate Exchange) WG
Wednesday, 18 July 2018, 13:30-15:00 EDT, Place du Canada
Agenda: https://datatracker.ietf.org/meeting/102/agenda/dprive/
Documents: https://datatracker.ietf.org/wg/dprive/
Charter: http://tools.ietf.org/wg/dprive/charters/

DNSSD (Extensions for Scalable DNS Service Discovery) WG
Thursday, 19 July 2018, 9:30-12:00 EDT, Duluth
Agenda: https://datatracker.ietf.org/meeting/102/agenda/dnssd/
Documents: https://datatracker.ietf.org/wg/dnssd/
Charter: http://tools.ietf.org/wg/dnssd/charters/

DRIU (DNS Resolver Identification and Use) BOF
Thursday, 19 July 2018, 15:50-17:50 EDT, Viger
Agenda: https://datatracker.ietf.org/meeting/102/materials/agenda-102-driu

OPSEC (Operational Security Capabilities for IP Network Infrastructure) WG
Friday, 20 July 2018, 11:50-13:20 EDT, Viger
Agenda: https://datatracker.ietf.org/meeting/102/agenda/opsec/
Documents: https://datatracker.ietf.org/wg/opsec/
Charter: http://tools.ietf.org/wg/doh/charters/

Follow Us

It will be a busy week in Montreal, and whether you plan to be there or join remotely, there’s much to monitor. Read the full series of Rough Guide to IETF 102 posts, and follow us on the Internet Society blog, Twitter, or Facebook using #IETF102 to keep up with the latest news.

The post Rough Guide to IETF 102: DNSSEC, DNS Security and Privacy appeared first on Internet Society.