[EAI] Fw: [apps-discuss] draft-ietf-eai-rfc5337bis-dsn-01.txt
"Jiankang YAO" <yaojk@cnnic.cn> Thu, 16 December 2010 00:55 UTC
Return-Path: <yaojk@cnnic.cn>
X-Original-To: ima@core3.amsl.com
Delivered-To: ima@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CE2BC28C12C for <ima@core3.amsl.com>; Wed, 15 Dec 2010 16:55:04 -0800 (PST)
X-Quarantine-ID: <ShYzYxo6n6dV>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: -99.424
X-Spam-Level:
X-Spam-Status: No, score=-99.424 tagged_above=-999 required=5 tests=[AWL=0.619, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ShYzYxo6n6dV for <ima@core3.amsl.com>; Wed, 15 Dec 2010 16:55:04 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id 7424A28C0EC for <ima@ietf.org>; Wed, 15 Dec 2010 16:55:03 -0800 (PST)
Received: (eyou send program); Thu, 16 Dec 2010 08:56:45 +0800
Message-ID: <492461005.02134@cnnic.cn>
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown (HELO lenovo47e041cf) (127.0.0.1) by 127.0.0.1 with SMTP; Thu, 16 Dec 2010 08:56:45 +0800
Message-ID: <652CD190BA6C4FAABF95456B7B76B97A@LENOVO47E041CF>
From: Jiankang YAO <yaojk@cnnic.cn>
To: ima@ietf.org
Date: Thu, 16 Dec 2010 08:56:57 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Subject: [EAI] Fw: [apps-discuss] draft-ietf-eai-rfc5337bis-dsn-01.txt
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Dec 2010 00:55:04 -0000
----- Original Message ----- From: "Ted Hardie" <ted.ietf@gmail.com> To: <apps-discuss@ietf.org>; "Alexey Melnikov" <alexey.melnikov@isode.com>; "Peter Saint-Andre" <stpeter@stpeter.im>; <tony+eaidsn@maillennium.att.com>; <chris.newman@oracle.com> Sent: Thursday, December 16, 2010 4:30 AM Subject: [apps-discuss] draft-ietf-eai-rfc5337bis-dsn-01.txt I have been selected as an Applications Area Review Team reviewer for this draft (for background on apps-review, please see http://www.apps.ietf.org/content/applications-area-review-team); note that Eliot Lear is also reviewing this draft as part of this Team. Please resolve these comments along with any other Last Call comments you may receive. Please wait for direction from your document shepherd or AD before posting a new version of the draft. Document: draft-ietf-eai-rfc5337bis-dsn-01.txt Title: Internationalized Delivery Status and Disposition Notifications Reviewer: Ted Hardie Review Date: December 15, 2010 Summary: Reviewers were asked to look specifically at the ABNF; it appears to me correct and the output from abnfgen seemed sensible. Eliot and Dave Crocker have already discussed the citation issue. There are two other issues which I feel should be resolved. Major Issues: The document says: NOTE: The only issue for which there is (as yet) no consensus yet is whether to change the name of the Address Type from "UTF-8" to something different, such as "UTF8", to reflect the fact that the "<addr <addr>>" address syntax is no longer permitted. Reviewing the mailing list there appeared to be one participant advocating change (SM) and one "not an exciting question" (Shawn Steele) and one noting a problem with changing it (Martin Dürst). 5335bis in the current version still calls this UTF-8; I believe that should govern this spec's usage and this note should be removed. A note to the RFC Editor to update this document if the nomenclature changes in the normative reference should do this; if not, then I believe that the IESG can permit a change by later adding a new RFC Editor note while it is in queue. Minor Issues: The document says: The ability to encode characters with the EmbeddedUnicodeChar encodings should be viewed as a transitional mechanism. It is hoped that as systems lacking support for UTF8SMTP become less common over time, these encodings can eventually be phased out. Transitional mechanisms generally live a long, long time, and this one seems likely to me to live at least to the end of my career. I would personally suggest striking this text, but it does no harm if left in. Nits: Chris Newman's address in the draft appears to be old. _______________________________________________ apps-discuss mailing list apps-discuss@ietf.org https://www.ietf.org/mailman/listinfo/apps-discuss
- [EAI] [apps-discuss] draft-ietf-eai-rfc5337bis-ds… Shawn Steele
- [EAI] Fw: [apps-discuss] draft-ietf-eai-rfc5337bi… Jiankang YAO