Tim Wicinski Reappointed to the Community Coordination Group (CCG)
The IAB has re-appointed Tim Wicinski to the Community Coordination Group for the 2024-2026 term. The IAB thanks him for his willingness to continue to serve the community in this capacity. The IAB would also like to thank everyone who provided feedback during this process. On behalf of the IAB, Cindy Morgan IAB Executive Administrative Manager On Tue, 14 May 2024 17:49 UTC, IAB Executive Administrative Manager wrote: > On behalf of the IETF, the IAB appoints three representatives to the > Community Coordination Group (CCG), which provides advice and > guidance to the IETF Trust in matters related to the IANA trademarks > and the IANA domain names. The process for appointing these > representatives is outlined in RFC 8090 [1]. > > The current IETF-selected members of the CCG and their terms of > appointment are: > > - Russ Housley, 2019-2025 > - Barry Leiba, 2019-2025 > - Tim Wicinski, 2020-2024 > > Tim Wicinski's term ends this year, and he has indicated that he is > willing to continue in this role for the upcoming 2024-2026 term. > Russ Housley and Barry Leiba's terms continue through the end of > 2025. > > The IAB is now soliciting input from the community on the incumbent > up for potential reappointment: Tim Wicinski [2] > > Please send your remarks in confidence to iab-ch...@iab.org and > ex...@iab.org by Tuesday 2024-06-11 at 2359 UTC. We thank you in > advance for your help. > > On behalf of the IAB, >Cindy Morgan >IAB Executive Administrative Manager > > [1] https://www.rfc-editor.org/info/rfc8090 > [2] https://datatracker.ietf.org/person/Tim%20Wicinski ___ IETF-Announce mailing list -- ietf-announce@ietf.org To unsubscribe send an email to ietf-announce-le...@ietf.org
Last Call: (The DNS Zone Version (ZONEVERSION) Option) to Informational RFC
The IESG has received a request from the Domain Name System Operations WG (dnsop) to consider the following document: - 'The DNS Zone Version (ZONEVERSION) Option' as Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the last-c...@ietf.org mailing lists by 2024-07-16. Exceptionally, comments may be sent to i...@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract The DNS ZONEVERSION option is a way for DNS clients to request, and for authoritative DNS servers to provide, information regarding the version of the zone from which a response is generated. The Serial field from the Start Of Authority (SOA) resource record is a good example of a zone's version, and the only one defined by this specification. Additional version types may be defined by future specifications. Including zone version data in a response simplifies and improves the quality of debugging and diagnostics since the version and the DNS answer are provided atomically. This can be especially useful for zones and DNS providers that leverage IP anycast or multiple backend systems. It functions similarly to the DNS Name Server Identifier (NSID) option [RFC5001]. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-dnsop-zoneversion/ No IPR declarations have been submitted directly on this I-D. ___ IETF-Announce mailing list -- ietf-announce@ietf.org To unsubscribe send an email to ietf-announce-le...@ietf.org
Last Call: (The DNS Zone Version (ZONEVERSION) Option) to Informational RFC
The IESG has received a request from the Domain Name System Operations WG (dnsop) to consider the following document: - 'The DNS Zone Version (ZONEVERSION) Option' as Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the last-c...@ietf.org mailing lists by 2024-07-16. Exceptionally, comments may be sent to i...@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract The DNS ZONEVERSION option is a way for DNS clients to request, and for authoritative DNS servers to provide, information regarding the version of the zone from which a response is generated. The Serial field from the Start Of Authority (SOA) resource record is a good example of a zone's version, and the only one defined by this specification. Additional version types may be defined by future specifications. Including zone version data in a response simplifies and improves the quality of debugging and diagnostics since the version and the DNS answer are provided atomically. This can be especially useful for zones and DNS providers that leverage IP anycast or multiple backend systems. It functions similarly to the DNS Name Server Identifier (NSID) option [RFC5001]. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-dnsop-zoneversion/ No IPR declarations have been submitted directly on this I-D. ___ IETF-Announce mailing list -- ietf-announce@ietf.org To unsubscribe send an email to ietf-announce-le...@ietf.org
List of open positions to be filled by NomCom,
Here is the list of positions that NomCom has been asked to fill. IETF LLC Board (three-year term): 1 position Jonathan Livingwood is term limited, can’t be reelected and a new nominee is needed. IETF Trust (three-year term): 1 position Kathleen Moriarty has served two terms There is no clear guidance on term limits for IETF Trust in rfc8714 Section 2. The draft-leiba-term-limit-guidance-00.html is an initial document that is trying to provide guidance on term limits, so community input is appreciated. Per RFC 8713 NomCom can consider length of service when evaluating an incumbent, and will take the number of terms into the account. IAB (two-year term): 6 positions following people are for renewal Dhruv Dhody, Huawei Wes Hardaker, USC/ISI Suresh Krishnan, Cisco Alvaro Retana, Futurewei David Schinazi, Google Christopher Wood, Apple IESG (two year term): 8 positions Applications and Real Time (ART) AD: 1 position Internet (INT) AD: 1 position Operations and Management (OPS) AD: 1 position (OPS AD) Routing (RTG) AD: 2 position Security (SEC) AD: 1 position WIT AD (one year term) and (two year term): 2 positions At the moment, with exception of Jonathan Livingwood, I have not been informed if any of the existing people in mentioned leadership positions will seek reelection or not for the positions being filled. Dean Bogdanovic nomcom-chair-2...@ietf.org ___ IETF-Announce mailing list -- ietf-announce@ietf.org To unsubscribe send an email to ietf-announce-le...@ietf.org
