[EAI] Ticket status, EAI, June 15, 2007
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[EAI] Ticket status, EAI, June 15, 2007



The following tickets are open on the EAI issue tracker:

1483 SMTPEXT 2.7: Non-ASCII in response texts Text proposed in -06, no later discussion.

1484 SMTPEXT 2.2: More exact definition of action choices Text proposed in -06, no later discussion.

1485 UTF8HDR 4.6/DSN: Choice of body part for transport of UTF8SMTP messages
MIME type message/something is proposed, no clear consensus. Poll will be
sent.

1486 SMTPEXT 2.7.2: Message retry Text proposed in -06, no later discussion.

1487 UTF8HDR 4.2: Does this specification update MIME? Proposed resolution: Yes. Say so in introduction.

1488 UTF8HDR 4.2: List MIME headers that are modified? Proposed resolution: Yes. We need an intro saying how we handle the
difference in grammars.
Propose to merge this with 1487.


1490 UTF8HDR 4.2: Including Content-Description to picture (grammar)
Propose to merge this with 1487.

1491 UTF8HDR 4.2: Extending MIME (ABNF grammar) Propose to merge this with 1487.

1492 SMTPEXT 2.7.3: <uFor> syntax Text proposed in -06, no later discussion.

1493 SMTPEXT 2.4: Redefining of RCPT TO and MAIL FROM commands (ABNF
grammar)
Text proposed in -06, no later discussion.

1494 UTF8HDR 4.4: <angle-addr> should include <obs-angle-addr> Proposed resolution: Yes; UTF-8 format needs to be an additional
alternative (=/) on angle-addr.


1495 SMTPEXT 2.5/2.6: Reply code used on DATA
Text proposed in -06.

1496 DOWNGRADE: Specify a simpler downgrade procedure?
No discussion so far.

For the "text proposed in -06" tickets, we will interpret silence as "this
is good enough", and resolve the tickets in a week or so. For the issues
with no proposed solution, discussion is needed.

           harald, for the chairs



_______________________________________________
IMA mailing list
IMA at ietf.org
https://www1.ietf.org/mailman/listinfo/ima




Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.