[mile] Alexey Melnikov's Yes on draft-ietf-mile-rfc5070-bis-22: (with COMMENT)

"Alexey Melnikov" <aamelnikov@fastmail.fm> Sat, 28 May 2016 16:57 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: The IESG <iesg@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160528165720.20106.29300.idtracker@ietfa.amsl.com>
Date: Sat, 28 May 2016 09:57:20 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/0Y8yeTlX0PVnr0ybAIzU910ppos>
Cc: mile-chairs@tools.ietf.org, mile-chairs@ietf.org, mile@ietf.org, draft-ietf-mile-rfc5070-bis@ietf.org
Subject: [mile] Alexey Melnikov's Yes on draft-ietf-mile-rfc5070-bis-22: (with COMMENT)

Alexey Melnikov has entered the following ballot position for
draft-ietf-mile-rfc5070-bis-22: 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-mile-rfc5070-bis/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

In 3.29.3.1: there is still a reference to RFC 822 (should be RFC 5322)

In 4.1: it would be good to point to the W3C XML document about rules for
escaping special characters. Otherwise readers might just think that all
cases are covered in this section.

[mile] Alexey Melnikov's Yes on draft-ietf-mile-r… Alexey Melnikov