NomCom 2023 Clarification on IETF Nomination Deadline

[NomCom Chair 2023]

All,

Several people have noted an inconsistency in nomination deadlines in recent 
emails.

For the IETF chair, the deadline is 2023-10-31.
For all other open positions, the deadline is 2023-10-12.

The NomCom will announce nominees after the respective deadlines pass, after 
which we will request feedback.

Ideally, we'd be announcing nominees at the same time, but we're giving IETF 
chair nominees a little longer to work out whether they will accept, given the 
shorter notice period for that position and the magnitude of what they are 
being asked to accept.

Thanks,
Martin Thomson
nomcom-chair-2...@ietf.org

___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Last Call: (JSContact: A JSON representation of contact data) to Proposed Standard

[The IESG]

The IESG has received a request from the Calendaring Extensions WG (calext)
to consider the following document: - 'JSContact: A JSON representation of
contact data'
   as Proposed Standard

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 2023-10-12. 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


   This specification defines a data model and JSON representation of
   contact card information that can be used for data storage and
   exchange in address book or directory applications.  It aims to be an
   alternative to the vCard data format and to be unambiguous,
   extendable and simple to process.  In contrast to the JSON-based
   jCard format, it is not a direct mapping from the vCard data model
   and expands semantics where appropriate.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-calext-jscontact/



No IPR declarations have been submitted directly on this I-D.


This is the second IETF LC on this document.  Substantial changes were made to 
the document in response to IESG Review of -09 and a post-IESG Review ARTART 
review. 




___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Last Call: (Precision Availability Metrics for Services Governed by Service Level Objectives (SLOs)) to Informational RFC

[The IESG]

The IESG has received a request from the IP Performance Measurement WG (ippm)
to consider the following document: - 'Precision Availability Metrics for
Services Governed by Service Level
   Objectives (SLOs)'
   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 2023-10-12. 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


   This document defines a set of metrics for networking services with
   performance requirements expressed as Service Level Objectives (SLO).
   These metrics, referred to as Precision Availability Metrics (PAM),
   are useful for defining and monitoring SLOs.  For example, PAM can be
   used by providers and/or customers of an IETF Network Slice Service
   to assess whether the service is provided in compliance with its
   defined SLOs.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-ippm-pam/



No IPR declarations have been submitted directly on this I-D.





___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Formal IESG Teleconference Webex and Dial-in Information: 5 October 2023

[IESG Secretary]

All members of the community are welcome to attend formal IESG
telechats as observers. Observers are not invited to participate in the
discussion.

The next formal IESG telechat will be held on Thursday, October 5,
2023 at 07:00 US/Canada Pacific (14:00 UTC). The meeting is scheduled
for two hours (07:00-09:00 US/Canada Pacific). Webex and Dial-in information
is at the bottom of this message.

The agenda for the upcoming telechat can be found at


A calendar of upcoming public telechats can be downloaded or subscribed
to at:
https://calendar.google.com/calendar/ical/ietf.org_egdabaf39ch5v8a13dt39mvee4%40group.calendar.google.com/public/basic.ics


Topic: IESG Formal Telechat
Date: October 5, 2023
Time: 07:00 US/Canada Pacific
09:00 US/Canada Central
10:00 US/Canada Eastern
14:00 UTC
15:00 United Kingdom
16:00 Germany, France, Belgium, Sweden
17:00 Finland
17:00 Kenya
19:30 India

---
JOIN WEBEX MEETING
https://ietf.webex.com/ietf/j.php?MTID=md68c9487454a70b3bb298efa7b181143
Meeting number: 2427 431 7054
Meeting password: 12345

JOIN BY PHONE
1-650-479-3208 Call-in toll number (US/Canada)
Access code: 2427 431 7054

___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Last Call: (IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters) to Best Current Practice

[The IESG]

The IESG has received a request from the Internet Area Working Group WG
(intarea) to consider the following document: - 'IANA Considerations and IETF
Protocol and Documentation Usage for IEEE
   802 Parameters'
   as Best Current Practice

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 2023-10-12. 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


   Some IETF protocols make use of Ethernet frame formats and IEEE 802
   parameters.  This document discusses several aspects of such
   parameters and their use in IETF protocols, specifies IANA
   considerations for assignment of points under the IANA OUI
   (Organizationally Unique Identifier), and provides some values for
   use in documentation.  This document obsoletes RFC 7042.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-intarea-rfc7042bis/

The IESG will also welcome feedback on one specific topic raised by the 
responsible AD:
https://mailarchive.ietf.org/arch/msg/int-area/uf7MZFktoQKohLXlhkCBK01-tGM/

No IPR declarations have been submitted directly on this I-D.





___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Protocol Action: 'JSONPath: Query expressions for JSON' to Proposed Standard (draft-ietf-jsonpath-base-21.txt)

[The IESG]

The IESG has approved the following document:
- 'JSONPath: Query expressions for JSON'
  (draft-ietf-jsonpath-base-21.txt) as Proposed Standard

This document is the product of the JSON Path 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-jsonpath-base/




Technical Summary

   JSONPath defines a string syntax for selecting and extracting JSON
   (RFC 8259) values from a JSON value.

Working Group Summary

   This is a relatively small but functional working group.  Consensus was 
solid.
   Nothing unusual here in terms of procedure or contention. 

Document Quality

   There is a large number of JSONPath implementations, including at least one 
for
   every popular programming language. The goal of this WG was to produce a
   specification such that JSONPath expressions conforming to it will have a 
high
   probability of interoperating across a large number of these implementations.

Personnel

   The Document Shepherd for this document is Tim Bray. The Responsible
   Area Director is Murray Kucherawy.

___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Protocol Action: 'Registration Data Access Protocol (RDAP) Reverse Search' to Proposed Standard (draft-ietf-regext-rdap-reverse-search-25.txt)

[The IESG]

The IESG has approved the following document:
- 'Registration Data Access Protocol (RDAP) Reverse Search'
  (draft-ietf-regext-rdap-reverse-search-25.txt) as Proposed Standard

This document is the product of the Registration Protocols Extensions 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-regext-rdap-reverse-search/




Technical Summary

   The Registration Data Access Protocol (RDAP) does not include query
   capabilities for finding the list of domains related to a set of
   entities matching a given search pattern.  Considering that an RDAP
   entity can be associated with any defined object class and other
   relationships between RDAP object classes exist, a reverse search can
   be applied to other use cases besides the classic domain-entity
   scenario.  This document describes an RDAP extension that allows
   servers to provide a reverse search feature based on the relationship
   defined in RDAP between an object class for search and any related
   object class.  The reverse search based on the domain-entity
   relationship is treated as a particular case.

Working Group Summary

   The working group is medium-sized overall but has a limited number
   of vocal participants.  That small community achieved consensus.  Processing
   appears to have been typical.

Document Quality

   Section 11 identifies existing implementations.

   All appropriate reviews have been completed, especially
   early IANA activity.

Personnel

   The Document Shepherd for this document is Tom Harrison. The Responsible
   Area Director is Murray Kucherawy.

___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce