[Idr] Barry Leiba's Yes on draft-ietf-idr-rfc8203bis-07: (with COMMENT)
Barry Leiba via Datatracker <noreply@ietf.org> Thu, 08 October 2020 03:38 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 02D253A0ED6; Wed, 7 Oct 2020 20:38:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Barry Leiba via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-idr-rfc8203bis@ietf.org, idr-chairs@ietf.org, idr@ietf.org, Susan Hares <shares@ndzh.com>, aretana.ietf@gmail.com, shares@ndzh.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Barry Leiba <barryleiba@computer.org>
Message-ID: <160212832599.7255.18200569186812477056@ietfa.amsl.com>
Date: Wed, 07 Oct 2020 20:38:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/PwLE9lUQ1Ejs5zEjxUS1SHLUXfk>
Subject: [Idr] Barry Leiba's Yes on draft-ietf-idr-rfc8203bis-07: (with COMMENT)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Oct 2020 03:38:46 -0000
Barry Leiba has entered the following ballot position for draft-ietf-idr-rfc8203bis-07: Yes When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-idr-rfc8203bis/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- It would help if the document said, right up in the Introduction, that the purpose of this is to increase the valid length of the Shutdown Communication to 255 octets, up from 128, because 128 turned out not to be enough for translation of reasonable strings into some languages, such as Russian. Such a statement might have made it clearer to the IESG, and perhaps to other reviewers, and will likely help other readers understand why this update is being made. To respond to Alissa's comment about what we might do to avoid this in future is that it's correct that an Internationalization review probably would not have picked up that 128 octets might not be enough for, say, Russian translation of common messages. I guess we could try doing sample translations before settling on maximum field lengths. I suspect that the effort is likely not worth it, given how infrequently this has turned out to be a problem so far. I don't see other I18N issues with this document. I have one text suggestion, as this point has been confusing to people in the past: OLD Note that when the Shutdown Communication contains multibyte characters, the number of characters will be less than the length value. NEW Note that UTF-8 often encodes a single Unicode character as multiple octets. When the Shutdown Communication contains such multibyte characters, the length value (in UTF-8 octets) will be greater than the number of Unicode characters. END
- [Idr] Barry Leiba's Yes on draft-ietf-idr-rfc8203… Barry Leiba via Datatracker