Last Call: (IDNA2008 and Unicode 12.0.0) to Proposed Standard
The IESG has received a request from an individual submitter to consider the following document: - 'IDNA2008 and Unicode 12.0.0' 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 2021-11-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 This document describes the changes between Unicode 6.2.0 and Unicode 12.0.0 in the context of IDNA2008. Some additions and changes have been made in the Unicode Standard that affect the values produced by the algorithm IDNA2008 specifies. IDNA2008 allows adding exceptions to the algorithm for backward compatibility; however, this document does not add any such exceptions. This document provides the necessary tables to IANA to make its database consisstent with Unicode 12.0.0. To improve understanding, this document describes systems that are being used as alternatives to those that conform to IDNA2008. TO BE REMOVED AT TIME OF PUBLICATION AS AN RFC: This document is discussed on the i18n-disc...@ietf.org mailing list of the IETF. The file can be obtained via https://datatracker.ietf.org/doc/draft-faltstrom-unicode12/ No IPR declarations have been submitted directly on this I-D. The document contains these normative downward references. See RFC 3967 for additional information: rfc6912: Principles for Unicode Code Point Inclusion in Labels in the DNS (Informational - Internet Architecture Board (IAB)) rfc5895: Mapping Characters for Internationalized Domain Names in Applications (IDNA) 2008 (Informational - Independent Submission) rfc5894: Internationalized Domain Names for Applications (IDNA): Background, Explanation, and Rationale (Informational - Internet Engineering Task Force (IETF)) ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Last Call: (BGP Extended Community Registries Update) to Proposed Standard
The IESG has received a request from the Inter-Domain Routing WG (idr) to consider the following document: - 'BGP Extended Community Registries Update' 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 2021-10-26. 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 updates several BGP Extended Community registries in order to replace the "Experimental Use" registration procedure in some entries, since their use is clearly not experimental and thus misleading. This document updates RFC7153. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ext-com-registry/ 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
Last Call: (Interoperability Profile for Relay User Equipment) to Proposed Standard
The IESG has received a request from the Relay User Machine WG (rum) to
consider the following document: - 'Interoperability Profile for Relay User
Equipment'
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 2021-10-26. 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
Video Relay Service (VRS) is a term used to describe a method by
which a hearing person can communicate with a deaf, hard of hearing
or hearing impaired user using an interpreter ("Communications
Assistant") connected via a videophone to the deaf/HoH user and an
audio telephone call to the hearing user. The CA interprets using
sign language on the videophone link and voice on the telephone link.
Often the interpreters may be employed by a company or agency termed
a "provider" in this document. The provider also provides a video
service that allows users to connect video devices to their service,
and subsequently to CAs and other deaf/HoH users. It is desirable
that the videophones used by the deaf, hard of hearing or hearing
impaired user conform to a standard so that any device may be used
with any provider and that direct video calls between deaf, hard of
hearing or hearing impaired users work. This document describes the
interface between a videophone and a provider.
The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-rum-rue/
The following IPR Declarations may be related to this I-D:
https://datatracker.ietf.org/ipr/5120/
https://datatracker.ietf.org/ipr/5121/
https://datatracker.ietf.org/ipr/5122/
https://datatracker.ietf.org/ipr/5123/
https://datatracker.ietf.org/ipr/5124/
https://datatracker.ietf.org/ipr/5125/
https://datatracker.ietf.org/ipr/5126/
https://datatracker.ietf.org/ipr/5127/
https://datatracker.ietf.org/ipr/5128/
https://datatracker.ietf.org/ipr/5129/
https://datatracker.ietf.org/ipr/5130/
https://datatracker.ietf.org/ipr/5131/
https://datatracker.ietf.org/ipr/5132/
https://datatracker.ietf.org/ipr/3705/
https://datatracker.ietf.org/ipr/3706/
https://datatracker.ietf.org/ipr/3707/
https://datatracker.ietf.org/ipr/3708/
https://datatracker.ietf.org/ipr/3709/
https://datatracker.ietf.org/ipr/3710/
https://datatracker.ietf.org/ipr/3711/
https://datatracker.ietf.org/ipr/3712/
https://datatracker.ietf.org/ipr/3713/
https://datatracker.ietf.org/ipr/3714/
https://datatracker.ietf.org/ipr/3716/
https://datatracker.ietf.org/ipr/3717/
https://datatracker.ietf.org/ipr/3718/
https://datatracker.ietf.org/ipr/3719/
https://datatracker.ietf.org/ipr/3720/
https://datatracker.ietf.org/ipr/3721/
https://datatracker.ietf.org/ipr/3722/
https://datatracker.ietf.org/ipr/3723/
https://datatracker.ietf.org/ipr/3724/
https://datatracker.ietf.org/ipr/3725/
https://datatracker.ietf.org/ipr/3726/
https://datatracker.ietf.org/ipr/3727/
https://datatracker.ietf.org/ipr/3728/
https://datatracker.ietf.org/ipr/3729/
https://datatracker.ietf.org/ipr/3730/
https://datatracker.ietf.org/ipr/3731/
https://datatracker.ietf.org/ipr/3732/
https://datatracker.ietf.org/ipr/3733/
https://datatracker.ietf.org/ipr/3734/
https://datatracker.ietf.org/ipr/3735/
https://datatracker.ietf.org/ipr/3736/
https://datatracker.ietf.org/ipr/3737/
https://datatracker.ietf.org/ipr/3738/
https://datatracker.ietf.org/ipr/3739/
https://datatracker.ietf.org/ipr/3740/
https://datatracker.ietf.org/ipr/3755/
https://datatracker.ietf.org/ipr/4783/
https://datatracker.ietf.org/ipr/4784/
https://datatracker.ietf.org/ipr/4785/
https://datatracker.ietf.org/ipr/4786/
https://datatracker.ietf.org/ipr/4787/
https://datatracker.ietf.org/ipr/4788/
https://datatracker.ietf.org/ipr/4789/
https://datatracker.ietf.org/ipr/4790/
https://datatracker.ietf.org/ipr/4791/
https://datatracker.ietf.org/ipr/4792/
https://datatracker.ietf.org/ipr/4793/
https://datatracker.ietf.org/ipr/4794/
https://datatracker.ietf.org/ipr/4795/
https://datatracker.ietf.org/ipr/4796/
https://datatracker.ietf.org/ipr/4797/
https://datatracker.ietf.org/ipr/4798/
https://datatracker.ietf.org/ipr/4799/
https://datatracker.ietf.org/ipr/4800/
https://datatracker.ietf.org/ipr/4801/
https://datatracker.ietf.org/ipr/4802/
https://datatracker.ietf.org/ipr/4803/
https://datatracker.ietf.org/ipr/4804/
https://datatracker.ietf.org/ipr/4805/
https://datatracker.ietf.org/ipr/4806/
https://datatracker.ietf.org/ipr/4807/
https://datatracker.ietf.org/ipr/4808/
https://datatracker.ietf.org/ipr/4809/
https://datatracker.ietf.org/ipr/4810/
https://datatracker.ietf.org/ipr/4811/
Protocol Action: 'Registry Maintenance Notification for the Extensible Provisioning Protocol (EPP)' to Proposed Standard (draft-ietf-regext-epp-registry-maintenance-19.txt)
The IESG has approved the following document: - 'Registry Maintenance Notification for the Extensible Provisioning Protocol (EPP)' (draft-ietf-regext-epp-registry-maintenance-19.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-epp-registry-maintenance/ Technical Summary This document describes an Extensible Provision Protocol (EPP) extension called "Registry Maintenance Notification", used by EPP servers to notify EPP clients and allow EPP clients to query EPP servers on maintenance events. Working Group Summary This work originated in the Technical Operations subcommittee of registries and registrars in ICANN's Generic Names Supporting Organization (GNSO). Since it is an EPP protocol extension it was submitted to the REGEXT working group for consideration as a Proposed Standard. As the work was developed within its community of interest, the specification arrived mostly complete. There was minor discussion of a few details and without objection the working group agreed to Proposed Standard status for the specification. Document Quality The document was reviewed by EPP experts among the working group members and found to be excellent quality. The document represents strong consensus of a few individuals, with no objection from anyone else. Personnel The document shepherd is James Galvin. 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: 'Revised IANA Considerations for DNSSEC' to Proposed Standard (draft-ietf-dnsop-dnssec-iana-cons-05.txt)
The IESG has approved the following document: - 'Revised IANA Considerations for DNSSEC' (draft-ietf-dnsop-dnssec-iana-cons-05.txt) as Proposed Standard This document is the product of the Domain Name System Operations Working Group. The IESG contact persons are Warren Kumari and Robert Wilton. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-dnsop-dnssec-iana-cons/ Technical Summary This document changes the review requirements needed to get DNSSEC algorithms and resource records added to IANA registries. It updates RFC 6014 to include hash algorithms for DS records and NSEC3 parameters. It also updates RFC 5155 and RFC 6014, which have requirements for DNSSEC algorithms, and updates RFC 8624 to say that algorithms that are described in RFCs that are not on standards track are only at the "MAY" level of implementation recommendation. The rationale for these changes is to bring the requirements for DS records and for the hash algorithms used in NSEC3 in line with the requirements for all other DNSSEC algorithms. Working Group Summary There was a lot of debate and discussion when it was first introduced. There was a feeling that loosening the requirements on adding new DNSSEC algorithms would lead to algorithms not getting implemented, algorithms designed around national/"vanity" crypto, etc. This was resolved with some discussion. Document Quality The document changes the registration policy for an IANA registry, to better align with other registries. It is a process document and so there are no implementations, it is written appropriately for the intended audience, etc. Personnel Tim Wicinski is the DS Warren Kumari is RAD! (nope, still not old...) ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
BCP 226, RFC 9137 on Considerations for Cancellation of IETF Meetings
A new Request for Comments is now available in online RFC libraries. BCP 226 RFC 9137 Title: Considerations for Cancellation of IETF Meetings Author: M. Duke Status: Best Current Practice Stream: IETF Date: October 2021 Mailbox:martin.h.d...@gmail.com Pages: 7 See Also: BCP 226 I-D Tag:draft-ietf-shmoo-cancel-meeting-06.txt URL:https://www.rfc-editor.org/info/rfc9137 DOI:10.17487/RFC9137 The IETF ordinarily holds three in-person meetings per year to discuss issues and advance the Internet. However, various events can make a planned in-person meeting infeasible. This document provides criteria to aid the IETF Administration LLC (IETF LLC), the Internet Engineering Steering Group (IESG), and the Chair of the Internet Research Task Force (IRTF) in deciding to relocate, virtualize, postpone, or cancel an in-person IETF meeting. This document is a product of the Stay Home Meet Only Online Working Group of the IETF. BCP: This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 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 https://www.ietf.org/mailman/listinfo/ietf-announce
