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

["Peterson, Jon" <jon.peterson@neustar.biz>]

Thanks for the read Bill,

>                       Yes  No-Objection  Discuss  Abstain
> Bill Fenner          [   ]     [   ]     [ X ]     [   ]
> 
> draft-ietf-impp-im-03.txt uses RFC 822 ABNF (#mailbox).
> 

Doh, someone caught this at the last minute in impp-pres-03, but I gather it
wasn't fixed in impp-im-03. I'm happy to chop off the #.

> 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.

We'll have to get Graham to address these.

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

- J