Internationalized Delivery Status and Disposition Notifications
draft-ietf-eai-dsn-06
Yes
(Lisa Dusseault)
No Objection
(Cullen Jennings)
(Dan Romascanu)
(David Ward)
(Lars Eggert)
(Mark Townsley)
(Pasi Eronen)
(Ron Bonica)
(Ross Callon)
Recuse
(Chris Newman)
Note: This ballot was opened for revision 06 and is now closed.
Lisa Dusseault Former IESG member
Yes
Yes
()
Unknown
Cullen Jennings Former IESG member
No Objection
No Objection
()
Unknown
Dan Romascanu Former IESG member
No Objection
No Objection
()
Unknown
David Ward Former IESG member
No Objection
No Objection
()
Unknown
Jari Arkko Former IESG member
No Objection
No Objection
(2008-07-03)
Unknown
ABNF compiles. But only after changing indents in Section 4 to be the same as those in Section 3 (two vs. three spaces). No time to check whether this is a real problem or something that Bill's parser just does...
Lars Eggert Former IESG member
No Objection
No Objection
()
Unknown
Magnus Westerlund Former IESG member
No Objection
No Objection
(2008-07-03)
Unknown
I think the ABNF could be improved and be made easier to verify. I know there are a lot of baggage in the ABNF usage in RFC 2821 and RFC 2822. However, I think the following improvement could be done: - Put in the equivalent of import clause for different rules. What I mean is that for a rule defined in another document, like "atext" xtext = <xtext is defined in [RFC3461]> That way a reader know from where it is comming. That is especially important when it comes to extension clauses, i.e. =/ constructions. It will also not show up as undefined in parsing. Thus allowing one to easier verify the real undefines from the ones that are imported from other documents.
Mark Townsley Former IESG member
No Objection
No Objection
()
Unknown
Pasi Eronen Former IESG member
No Objection
No Objection
()
Unknown
Ron Bonica Former IESG member
No Objection
No Objection
()
Unknown
Ross Callon Former IESG member
No Objection
No Objection
()
Unknown
Chris Newman Former IESG member
Recuse
Recuse
()
Unknown