New Non-WG Mailing List: KEYTRANS (Key Transparency)
A new IETF non-working group email list has been created. List address: keytr...@ietf.org Archive: https://mailarchive.ietf.org/arch/browse/keytrans/ To subscribe: https://www.ietf.org/mailman/listinfo/keytrans Purpose: Key Transparency (KT) is a safe, publicly-auditable way to distribute cryptographically-sensitive data like public keys. It builds on top of previous protocols, primarily Certificate Transparency, in ways that make it more suitable for the use-case of end-to-end encryption. Importantly, users can efficiently search a KT server for only the entries that are relevant to them and check that the server responded honestly. KT servers can also better preserve their users' privacy, by controlling when or if one user is allowed to learn another user's data. This mailing list will support the planned IETF 116 BoF, KEYTRANS, on the topic. This list belongs to IETF area: SEC For additional information, please contact the list administrators. ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
WG Action: Formed Computing-Aware Traffic Steering (cats)
A new IETF WG has been formed in the Routing Area. For additional information, please contact the Area Directors or the WG Chairs. Note that the WG Review message for this group was sent out under the name Computing-Aware Networking (can), but the charter was approved as Computing-Aware Traffic Steering (cats). Computing-Aware Traffic Steering (cats) --- Current status: Proposed WG Chairs: Peng Liu Adrian Farrel Assigned Area Director: John Scudder Routing Area Directors: Alvaro Retana John Scudder Andrew Alston Mailing list: Address: c...@ietf.org To subscribe: https://www.ietf.org/mailman/listinfo/cats/ Archive: https://mailarchive.ietf.org/arch/browse/cats/ Group page: https://datatracker.ietf.org/group/cats/ Charter: https://datatracker.ietf.org/doc/charter-ietf-cats/ Computing-Aware Traffic Steering (cats) Many service architectures create multiple service instances. These instances are often geographically distributed to multiple sites, and a single site may support multiple instances of a service. The services are provided on computing platforms and are generically referred to as "compute services". The CATS (Computing-Aware Traffic Steering) working group (WG) is chartered to consider the problem of how the network edge can steer traffic between clients of a service and sites offering the service. Since, for some services (for example, the evolution of networked AR/VR, and deployment of autonomous and networked vehicles), the performance experienced by clients will depend on both network metrics such as bandwidth and latency, and compute metrics such as processing, storage capabilities, and capacity, there is a need for a solution that can optimize how a network edge node steers traffic based on these metrics, as appropriate to the service. Although the specific optimization function will likely differ between services, implementations, and deployments, there is a need for a general framework for the distribution of compute and network metrics and transport of traffic from network edge to service instance. It also is likely that some set of common metrics can be identified. The CATS WG will concern itself with these issues. The IETF is working on exposing network conditions to endpoints (notably ALTO) and load balancing/service selection at layers 4 and 7 (for example, related to the selection of SIP servers). Specific characteristics that may distinguish CATS from other work include the desire to integrate both network and compute conditions in the optimization function that informs the steering applied by the network edge nodes, and the desire to operate that function on nodes within the service provider's network, logically separated from service operation. Exposure of network and compute conditions to applications is not in the scope of CATS. Because of their experience and prior work in collecting and exposing network conditions for use in selecting paths and servers, the CATS WG will seek advice and expertise from the ART and TSV areas. The assumed model for the CATS WG is an overlay network, where a network edge node makes a decision based on the metrics of interest, and then steers the traffic to a node that serves a service instance, for example using a tunnel. The CATS WG will focus on single domain models. Architectures that require the underlay network to be service-aware are out of scope. The CATS WG will analyze the problem in further detail and produce an architecture for a solution. Ideally, that architecture will be one that can be instantiated using existing technologies. The CATS WG is chartered to work on the following items: o Groundwork may be documented via a set of informational Internet- Drafts, not necessarily for publication as RFCs: * Problem statement for the need to consider both network and computing resource status. * Use cases for steering traffic from applications that have critical SLAs that would benefit from the integrated consideration of network and computing resource status. * Requirements for commonly agreed computing metrics and their distribution across the overlay network, as well as the appropriate frequency and scope of distribution. o Overall CATS framework & architecture: * This work encompasses the various building blocks and their interactions, realizing a CATS control and data plane that addresses the identified problems and requirements in the groundwork, including methods for distributing necessary information to utilize the identified metrics in CATS use cases. This will also cover OAM, scalability, and security aspects. o Additional groundwork to include: * Analyze the suitability and usefulness of computing and networking metrics for traffic steering decisions in CATS with a CATS metrics ontology as a possible outcome. * Analyze methods for distributing the necessar
Last Call: (JSContact: A JSON representation of contact data) to Proposed Standard
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-03-17. 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. ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Document Action: 'Considerations for Assigning a new Recommended DiffServ Codepoint (DSCP)' to Informational RFC (draft-ietf-tsvwg-dscp-considerations-13.txt)
The IESG has approved the following document: - 'Considerations for Assigning a new Recommended DiffServ Codepoint (DSCP)' (draft-ietf-tsvwg-dscp-considerations-13.txt) as Informational RFC This document is the product of the Transport Area Working Group. The IESG contact persons are Zaheduzzaman Sarker and Martin Duke. A URL of this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-tsvwg-dscp-considerations/ Technical Summary This document discusses considerations for assigning a new recommended DiffServ Code Point (DSCP) for a new standard Per Hop Behavior (PHB). It considers the common observed remarking behaviors that the DiffServ field might be subjected to along an Internet path. It also notes some implications of using a specific DSCP. Working Group Summary This draft is supported by the portion of the tsvwg working group that is familiar with and interested in Diffserv. The draft has received significant review and critique from a number of Diffserv experts, including the draft shepherd. There is clear consensus in the WG to document these lessons learned, and this draft has not been controversial in the WG. Document Quality This informational draft does not have a protocol to implement. Personnel The Shepherd is David Black. The AD is Martin Duke. ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
IETF 116 Final Agenda
IETF 116 Yokohama, Japan March 25-31, 2023 Hosted By: WIDE The IETF 116 Final Agenda is now available. https://datatracker.ietf.org/meeting/116/agenda https://datatracker.ietf.org/meeting/116/agenda.txt While this is considered the final agenda, changes may be made to the agenda up to and during the meeting. Updates will be reflected on the datatracker agenda pages. IETF 116 Information: https://www.ietf.org/how/meetings/116/ Register online at: https://registration.ietf.org/116/ Side Meetings At IETF 116, two rooms in the conference center will be made available for public side meetings. For the second time, the IETF will provide some AV support for these side meetings. Each room will contain a 360-degree video camera with microphone and speaker to assist remote participation. You will still be responsible for setting up your own conferencing bridge and Meetecho will not be available. There will be instructions in the room and more details available on the wiki at https://wiki.ietf.org/meeting/116/sidemeetings. Don’t forget to register for these exciting IETF 116 events! Hackathon - 25-26 March, 2023 Onsite signup: https://registration.ietf.org/116/new/hackathon_onsite/ Remote signup: https://registration.ietf.org/116/new/hackathon_remote/ More information: https://www.ietf.org/how/runningcode/hackathons/116-hackathon/ Keep up to date by subscribing to: https://www.ietf.org/mailman/listinfo/hackathon Code Sprint - Saturday 25 March, 2023 More information and signups: https://notes.ietf.org/notes-ietf-116-tools# ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
