Butt status: at home

that is the end of my #ietf105 trip, with bonus #baseball and a smidgen of actual work tacked on the side.

Gelato has been obtained at #ietf105, again

And now IXoT (Incremental zone transfer over TLS) and XoD (zone transfer over DSO). #DNS #acronyms #IETF105

Every #IETF meeting, we invent new acronyms. Now, in the #DPRIVE working group (#DNS #privacy), we hear about XoT (Zone transfer - aXfr - over TLS). #IETF105.

Q. Recommandations for #IETF on #privacy: encrypt everything, avoid creating metadata, don't leave things unspecified (diversity means leakage). #IETF105​

A. This view is a reflection of the #deathcult a #openweb path is the only option that might not pass through disaster #OMN

Gallery of horrors: testing real #RDAP servers in the field. The list of possible bugs is long. "This was done by a lazy developer. I'm sorry if you are the developer and are in the room." #IETF105

Now, #RDAP drafts (RDAP is the protocol that will try to replace #whois). The most problematic is the RDAP extension to do reverse searches ("find all domains registered by Coca-Cola"). #IETF105

There are nine escrow agents for #ICANN TLDs. (And three #EBERO, the emergency registries that may use the escrow data to resume the service for a failed registry.) The standard format is in use for several years, time to publish the RFC. #IETF105

First, discussion about data #escrow. (For instance, the agreement between the french governement and the .fr registry requires escrowing the data, to allow a recovery if the registry fails.) #IETF105

Bonjour, Montréal ! Fourth day of #IETF105 https://www.ietf.org/how/meetings/105/

For me today, RegExt (#EPP, #RDAP and other registry-related stuff) and DPRIVE (#DNS #privacy).

@dada 21° à Montréal. On gèle. (17 ° dans les salles de réunions de l'hôtel #IETF105)

Some remarks that seem common in the discussion about the #RFC editor crisis: the RFC editor model (RFC 6635) is too complicated, IETF particicipants were not informed of what was happening, and of the crisis (this changed this morning with the message "RSOC apology"), misunderstandings were many...

#IETF105

Wow, 15 people in line to give opinions about the #RFC editor. #IETF105

Now, the discussion about the #RFC editor. Olaf Kolkman reminds us of RFC 6635, which describes the RFC Editor model. "The RFC editor turns Internet-Drafts into RFCs".

#IETF105

But of course, it will depend on the new RFC editor. The current one stepped down, following an internal crisis, and will leave at the end of 2019. (Standing ovation for Heather.)

#IETF105

#RFC report by Heather Flanagan. v3 format (with XML, pictures and Unicode) will be deployed this autumn (if running code runs).

#IETF105

Statistics for #IETF105 : 1079 participants onsite (from 48 countries) 147 beginners.

Hackathon : 280 onsite (biggest IETF hackathon), 42 projects.

Recommandations for #IETF on #privacy: encrypt everything, avoid creating metadata, don't leave things unspecified (diversity means leakage). #IETF105

"If data exists, it's available to governments." #IETF105

Now, Bellovin on stage mentioning old Jewish biblical texts about #privacy.

#IETF105