Re: Evaluation: draft-ietf-impp-im - Common Profile for Instant Messaging (CPIM)

[Bill Fenner <fenner@research.att.com>]

                      Yes  No-Objection  Discuss  Abstain
Bill Fenner          [   ]     [   ]     [ X ]     [   ]

draft-ietf-impp-im-03.txt uses RFC 822 ABNF (#mailbox).

draft-ietf-impp-cpim-msgfmt-08.txt:
  SEPARATORS uses '<">', which is imprecise where %x22 is precise.
  NAMECHAR uses "%" where it means "%x" so is all syntax errors.
  The first UCS-high uses non-ABNF syntax (ABNF only handles bytes,
   so there is no way to represent %xffffffff)
  It says that it is using a modified ABNF which is case-sensitive.
   The SIP spec used %x syntax for case-sensitive fields, and I think
   that's a good strategy.  Someone who is just looking for the ABNF
   may miss the statement that it's a modified ABNF so might think that
   the fields are case-insensitive.  If the unambiguous form is used then
   this can't happen.
  (extremely minor): The rule Lang-param is referred to as "lang-param" in
   the "Subject-header" production.  Rule names are case-insensitive so
   this is valid, but could be confusing.

draft-ietf-impp-pres-03.txt ABNF is fine.