Session Initiation Protocol (SIP) Authenticated Identity Body (AIB) Format
RFC 3893

Note: This ballot was opened for revision 03 and is now closed.

(Allison Mankin) Yes

(Harald Alvestrand) (was Discuss) No Objection

Comment (2003-12-18)
No email
send info
Shepherding AD understands problem. I expect to have no problem clearing the DISCUSS when new text arrives.

(Steven Bellovin) (was Discuss) No Objection

(Margaret Cullen) No Objection

(Bill Fenner) No Objection

(Ned Freed) No Objection

Comment (2003-12-12 for -)
No email
send info
No IPR boilerplate

(Ted Hardie) No Objection

Comment (2003-12-16 for -)
No email
send info
I found this text a little unclear:

>  Unsigned AIBs MUST NOT be honored by any recipients.

I'd suggest changing it to say that Unsigned AIBs should be treated according
to the rules set out in Section 7 for AIBs that do not validate; if that doesn't make
sense, then some clarifying text that explains what "MUST NOT be honored" will
imply (identity not displayed?  message discarded?)

In this text:

>   Note that this means that the recipients of the
 >  request, even if they are unable to inspect the AIBF, will still be
  > able to see who signed that body (although it will not necessarily be
  > obvious that the body contains an AIB).

Does it really mean "inspect the AIB Format" or "inspect the AIB?"

An example showing multiple AIBs (Section 4.) would be valuable, I believe.

(Russ Housley) No Objection

Comment (2003-12-16 for -)
No email
send info

(Thomas Narten) No Objection

(Bert Wijnen) No Objection

Comment (2003-12-18 for -)
No email
send info
No Further objections or comments

(Alex Zinin) No Objection

(Jon Peterson) (was Abstain) Recuse