The second day at IETF 94 in Yokohama is all about home networking and secure routing for the Deploy360 team.
Not to mention of course the evening social event which is also a chance to come and say hello .
NOTE: If you are unable to attend IETF 94 in person, there are multiple ways to participate remotely.
The homenet (Home Networking)Working Group is meeting during the 0900-1130 UTC+9 block to continue its work on IPv6 based protocols for residential networks. This is usually one of the best attended working groups and this session will be focused on autoconfiguration, naming architecture and service discovery, as well as multiple interfacing support in home-type scenarios. No less than eight new drafts are up for discussion here, as well as updates to another seven, so expect an active session.
Running in parallel with homenet is the spring (Source Packet Routing in Networking) Working Group that’s looking into how to specify explicit packet forwarding paths to take advantage of certain network characteristics. Whilst similar mechanisms are already employed in MPLS traffic engineering, spring is also considering the use of IPv6 as a data plane.
There’s a bit of gap until the secure routing session, so the more politically conscious may want to check out the proposed hrpc (Human Rights Protocol Considerations) Research Group. Although not an obvious subject for the IETF, this group aims to look at how protocols can be developed to protect the Internet as a human rights enabling environment. IP, DNS, HTTP, P2P, XMPP and VPN protocols are up for specific discussion, so there are obvious IPv6, DNSSEC and TLS implications here.
The sidr (Secure Inter-Domain Routing) Working Group is running a split session in the 17.10-18.40 UTC+9 block today, but continuing on Friday during the 09.00-11.30 block. Today’s session is primarily devoted to the operational issues in deploying RPKI, and in particular referencing the experience of the Regional Internet Registries. These concerns include the consequences of mismatched resources in the digital certificate chain, when resources are transferred to a new holder in a different registry, and the handling RKPI validation locally when the CA authority is inaccessible. Four drafts that seek to address these issues are up discussion this evening.
At the same time as SIDR, the DBOUND Working Group will meet .We monitor this WG primarily because the “boundaries” of how you look at domain names can impact other security mechanisms such as TLS certificates. The DBOUND problem statement gives a good view into what the group is trying to do.
Then don’t forget the social event over at the Yokohama Bay Hotel Tokyu, starting at 19.00!
For more background, please read the Rough Guide to IETF 94 from Andrei, Mat, Karen, Dan and myself.
Relevant Working Groups:
- homenet (Home Networking) WG
Tuesday, 3 November 0900-1130, Room 502
Agenda: https://datatracker.ietf.org/meeting/94/agenda/homenet/
Documents: https://datatracker.ietf.org/wg/homenet/documents/
Charter: https://datatracker.ietf.org/wg/homenet/charter/
- spring (Source Packet Routing in Networking) WG
Tuesday, 3 November 0900-1030, Room 303
Agenda: https://datatracker.ietf.org/meeting/94/agenda/spring/
Documents: https://datatracker.ietf.org/wg/spring/documents/
Charter: https://datatracker.ietf.org/wg/spring/charter/
- sidr (Secure Inter-Domain Routing) WG
Tuesday, 3 November 1710-1840, Room 304
Agenda: https://datatracker.ietf.org/meeting/94/agenda/sidr/
Documents: https://datatracker.ietf.org/wg/sidr/documents/
Charter: https://datatracker.ietf.org/wg/sidr/charter/ - dbound (Domain Boundaries) WG
Tuesday, 3 November 2015, 1710-1840 JST, Room 303
Agenda: https://datatracker.ietf.org/meeting/94/agenda/dbound/
Documents: https://datatracker.ietf.org/wg/dbound/
Charter: https://datatracker.ietf.org/group/dbound/about/