Limited Availability at IETF 120 Headquarter Hotel and Registration Reminder

2024-05-31 Thread IETF Secretariat
# Limited Availability at Headquarter Hotel

The IETF room block at the Hyatt Regency Vancouver (the meeting venue & main 
hotel for IETF 120) and the Sheraton Vancouver Wall Centre (overflow) are sold 
out on 19 and 20 July, with limited availability on 26 July. IETF 120 
participants will only be able to book at the IETF group rate on 19 and 20 July 
if a cancellation within the IETF room block occurs. Rooms remain available on 
21-26 July.

We are continuing to work with the Hyatt Regency Vancouver to determine if 
additional nights can be added, and in the meantime are investigating 
additional options. We will send follow up announcements as more information 
becomes available. If you have questions or concerns related to hotel 
reservations please send an email to supp...@ietf.org. If you plan to cancel 
your reservation for any reason, please send an email to the 120attendees list.

If you are planning to start your IETF meeting week on 19 or 20 July and are 
still looking for accommodation, we recommend you consider booking those nights 
at an alternative hotel. Alternatively, though our room block is sold out, the 
Hyatt may still have limited inventory on those days that you can book at their 
prevailing rate to still take advantage of the exceptional room rate that the 
IETF has on the available dates. There are also properties available on AirBnb 
and Vrbo at rates that might be suitable, as well as the other suggestions that 
have been proposed on the attendees list. 

We sincerely apologize for any inconvenience the limited availability may 
cause. The hotel room block at the Hyatt for IETF 120 was secured several years 
ago, prior to the notable increase in Hackathon participation. Despite 
exhaustive efforts, we were unable to renegotiate the contract to secure 
additional rooms for these nights. This challenge is compounded by the 
exceptional negotiated room rate that we have for IETF 120, and the high demand 
of Vancouver as a destination in July. 

For current information see:

https://www.ietf.org/meeting/120/hotel/

# Registration reminder

Super early registration pricing for IETF 120 Vancouver is available until 
23:59 UTC 3 June. Be sure to register before the deadline passes to avoid a fee 
increase. Register online at: 

https://registration.ietf.org/120/

___
IETF-Announce mailing list -- ietf-announce@ietf.org
To unsubscribe send an email to ietf-announce-le...@ietf.org


RFC 9590 on IMAP Extension for Returning Mailbox METADATA in Extended LIS

2024-05-31 Thread rfc-editor
A new Request for Comments is now available in online RFC libraries.


RFC 9590

Title:  IMAP Extension for Returning Mailbox 
METADATA in Extended LIS 
Author: K. Murchison,
B. Gondwana
Status: Standards Track
Stream: IETF
Date:   May 2024
Mailbox:mu...@fastmailteam.com,
br...@fastmailteam.com
Pages:  6
Updates/Obsoletes/SeeAlso:   None

I-D Tag:draft-ietf-extra-imap-list-metadata-05.txt

URL:https://www.rfc-editor.org/info/rfc9590

DOI:10.17487/RFC9590

This document defines an extension to the Internet Message Access 
Protocol (IMAP) LIST command that allows the client to request
mailbox annotations (metadata), along with other information
typically returned by the LIST command.

This document is a product of the Email mailstore and eXtensions To Revise or 
Amend Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


___
IETF-Announce mailing list -- ietf-announce@ietf.org
To unsubscribe send an email to ietf-announce-le...@ietf.org


RFC 9585 on IMAP Response Code for Command Progress Notifications

2024-05-31 Thread rfc-editor
A new Request for Comments is now available in online RFC libraries.


RFC 9585

Title:  IMAP Response Code for Command 
Progress Notifications 
Author: M. Bettini
Status: Standards Track
Stream: IETF
Date:   May 2024
Mailbox:marco.bett...@open-xchange.com
Pages:  6
Updates/Obsoletes/SeeAlso:   None

I-D Tag:draft-ietf-extra-imap-inprogress-06.txt

URL:https://www.rfc-editor.org/info/rfc9585

DOI:10.17487/RFC9585

This document defines a new IMAP untagged response code,
"INPROGRESS", that provides progress notifications regarding the
status of long-running commands.

This document is a product of the Email mailstore and eXtensions To Revise or 
Amend Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


___
IETF-Announce mailing list -- ietf-announce@ietf.org
To unsubscribe send an email to ietf-announce-le...@ietf.org


RFC 9579 on Use of Password-Based Message Authentication Code 1 (PBMAC1) in PKCS #12 Syntax

2024-05-31 Thread rfc-editor
A new Request for Comments is now available in online RFC libraries.


RFC 9579

Title:  Use of Password-Based Message Authentication 
Code 1 (PBMAC1) in PKCS #12 Syntax
Author: H. Kario
Status: Informational
Stream: IETF
Date:   May 2024
Mailbox:hka...@redhat.com
Pages:  15
Updates:RFC 7292, RFC 8018

I-D Tag:draft-ietf-lamps-pkcs12-pbmac1-08.txt

URL:https://www.rfc-editor.org/info/rfc9579

DOI:10.17487/RFC9579

This document specifies additions and amendments to RFCs 7292 and
8018. It defines a way to use the Password-Based Message
Authentication Code 1 (PBMAC1), defined in RFC 8018, inside the PKCS
#12 syntax. The purpose of this specification is to permit the use of
more modern Password-Based Key Derivation Functions (PBKDFs) and
allow for regulatory compliance.

This document is a product of the Limited Additional Mechanisms for PKIX and 
SMIME Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


___
IETF-Announce mailing list -- ietf-announce@ietf.org
To unsubscribe send an email to ietf-announce-le...@ietf.org