IETF 116 General Information, Social Event, and Childcare
General Information for IETF 116 When booking your hotel, please be aware that the Intercontinental Yokohama Grand (the primary IETF hotel) is a ten minute walk from the meeting venue, PACIFICO Yokohama North. This meeting venue is different from the venue for IETF 94. Please refer to the map [1] for more information. The IETF 116 Welcome Reception will take place over three hours (versus the typical two) from 1700-2000 on Sunday, March 26th at the PACIFICO Yokohama North. Featuring a number of demonstrations from WIDE members, the reception will also include more robust food and beverage options. Social Event The IETF 116 social event will take place on Thursday, March 30th. Please note the day change, as social events are typically held on Tuesdays of the meeting week. Thanks to our host WIDE, we are excited to announce that our social will be held at the Osanbashi Hall. It promises to be a very special evening, with more details to come soon! Childcare Thanks to the generous support of our Diversity and Inclusion Gold sponsors, Akamai, Cisco and Huawei, and Bronze sponsors Comcast, ICANN, and Identity Digital, we are excited to offer onsite childcare at IETF 116 in Yokohama. After a well run service at IETF 115 in London, we are excited to announce that Rose Event Nannies [2] will once again be joining us to provide childcare. This service is offered free of charge to registered IETF participants and initially provides space for up to ten children. We strongly encourage advance sign up to give us sufficient time to investigate adding more space if this service becomes fully booked. Profiles and photos of the nannies that will be caring for your child(ren) during IETF 116 are now available online. Additional information and the link to the form to sign up for the childcare services are also available via the FAQ [3] page. This is the IETF’s third time offering childcare at a meeting, following the last successful edition at IETF 115. We would like to hear from parents how to make this service as useful as possible. We are open to exploring additional or alternative forms of childcare support for future meetings. Please send your suggestions directly to supp...@ietf.org or to the public admin-discuss list. [4] [1]https://www.google.com/maps/d/u/0/viewer?mid=1bfjk4dz0vxG6jcixJkqaaV_pcA90L4c&ll=35.45612263743427%2C139.63493745&z=14 [2] https://www.roseeventnannies.co.uk/ [3] https://www.ietf.org/how/meetings/116/childcare/ [4] https://www.ietf.org/mailman/listinfo/admin-discuss ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Protocol Action: 'Content Delivery Network Interconnection (CDNI) Footprint Types: Subdivision Code and Footprint Union' to Proposed Standard (draft-ietf-cdni-additional-footprint-types-11.txt)
The IESG has approved the following document: - 'Content Delivery Network Interconnection (CDNI) Footprint Types: Subdivision Code and Footprint Union' (draft-ietf-cdni-additional-footprint-types-11.txt) as Proposed Standard This document is the product of the Content Delivery Networks Interconnection Working Group. The IESG contact persons are Murray Kucherawy and Francesca Palombini. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-cdni-additional-footprint-types/ Technical Summary Open Caching architecture is a use case of Content Delivery Networks Interconnection (CDNI) in which the commercial Content Delivery Network (CDN) is the upstream CDN (uCDN) and the ISP caching layer serves as the downstream CDN (dCDN). This document supplements the CDNI Metadata Footprint Types defined in RFC 8006. The Footprint Types defined in this document can be used for Footprint objects as part of the Metadata interface (MI) defined in RFC 8006 or the Footprint & Capabilities Advertisement interface (FCI) defined in RFC 8008. The document also updates RFC 9241 with relevant ALTO entity domain types. The defined Footprint Types are derived from requirements raised by Open Caching but are also applicable to CDNI use cases in general. Working Group Summary The contents of the document have been reviewed by the CDNI WG, with discussion on the list and during our IETF sessions. There was fairly broad consensus. There was extensive discussion about the semantics of footprint combination (both the original intent of the authors and what the actual implementation should be). Accepting the shepherd's assertion on the original intent (as an original author), the wg came to a solution to meet implementation needs. Approaching WGLC, a question was raised as to whether an even more granular footprint should be specified (i.e., coordinate boundary-based vs ISO3166-2). It was not clear that a use case existed yet for the more granular footprint, but existing commercial need for ISO3166-2 was expressed, so the wg chose to more forward with the simpler solution for now (with the option to revisit more granular footprint options in the future). During WGLC, RFC9241 made it through the RFCEditor queue and the WG consulted with them wrt the impact a new footprint type would have on RFC9241. Multiple options were discussed on the list and at IETF114, and it was decided to incorporate ALTO IANA registrations in this document to allow RFC9241 to use the new ISO3166-2 footprint type as well. Document Quality The WG has reviewed the new footprint types and agreed that they are reasonable and valuable. We are requesting publication as "Proposed Standard" as the footprint types extend the exiting RFC8006 proposed standard. As one of the primary authors of both RFC8006 and RFC8008, and acting as both the expert reviewer and shepherd, the shepherd feels that the contents are straight forward and inline with the purposes and goals of RFC8006 and RFC8008. The shepherd's understanding is that SVTA vendors have implemented these extensions. Personnel Document Shepherd: Kevin J. Ma Responsible AD: Francesca Palombini ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
