Version 1315 (modified by spencerdawkins.ietf@…, 8 months ago) (diff)


Informal Telechat - December 13, 2018

Web Ex URL (updated 2015-09-09):

PLEASE NOTE: The current calendar subscription URL is at (updated 12/14/2016):

Note: If no items have been added to this wiki 24 hours before the telechat, then the telechat is cancelled. ADs should feel free to add items after that time, as long as there is *something* on the agenda 24 hours in advance.

1. Administrivia

1.1 Roll Call

1.2 Bash the Agenda

2. Document Discussions

2.x Issue (... who ...)

3. Management Issues

3.1 Agenda experiments for IETF 104 (Liz)

3.2 Disclosure of funding sources (Alissa)

3.3 IESG statement on minimal personal data in IANA registries (Alissa)

See mailing list thread and try to come to closure.

3.4 IESG WG Chairs Email - Plenary discussion on WG meeting conduct (Deborah)

See mailing list thread and try to come to closure.

3.x Issue (... who ...)

4. WG News (all)

Any news that would have a cross-WG or cross-area impact?

4.1 IPv6 Extension Headers (Spencer)

Discussion of "Tsvart last call review of draft-ietf-opsec-ipv6-eh-filtering-06" is pointing to a disconnect between what we're thinking for protocol extensions and what operators are thinking about protecting their networks.

This is a positive outcome (see Warren's e-mail about ways to respond), but I wanted to make sure people were aware of that discussion.

Link to Warren's e-mail:

4.2 Transport Proxies discussion in TSVAREA at IETF 103 (Spencer)

We had really productive discussions in TSVAREA at IETF 103 that included "requirements for inconspicuous HTTP proxying" -

  • Secure proxied traffic - The integrity, confidentiality, and authenticity of the proxied traffic is guaranteed
  • Proxied traffic blends in - The proxied traffic ideally looks like web browsing traffic
  • Similar performance characteristics - The performance characteristics of the original traffic should be retained as much as possible
  • Proxy authentication - The proxy can only be used by authorized clients
  • Active probing resistance - The proxy cannot be identified as a proxy and ideally looks like a normal web server

This seems helpful in moving forth any conversations we have about "operators and encrypted traffic", but it's strongly cross-area (TSV, ART, SEC, OPS, at a minimum).

Mirja and I were asked "where should this conversation continue"? I'm happy to do that on TSVAREA, but it's likely that MOST of the people who need to see it, aren't subscribed there.

Minutes at

5. Executive Sessions

5.x Issue (... who ...)

6. Parking place

6.x Issue (... who ...)

Editing hints

When adding a management issue to Section 3, use the following Wiki markup:

=== 3.1 Talk about the Weather ===

A sunny day, today!

Do not use any other Wiki markup or features on this page (above the line) -- this page will be parsed by the AD Dashboard tool in the future.

Use triple braces { and } on their own lines to ensure the text appears without formatting but in a grey box. Like so:

The quick brown fox says .....

Note that this page is public, and all the old versions are available, too.