I have been selected as the General Area Review Team (Gen-ART) reviewer for this draft (for background on Gen-ART, please see http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html). Please resolve these comments along with any other Last Call comments you may receive. Document: draft-ietf-sipping-capacity-attribute-05.txt Reviewer: Brian Carpenter Review Date: 2007-12-04 IETF LC End Date: 2007-12-20 IESG Telechat date: (if known) Summary: Almost ready, one formal problem Comments: Section 4 (but this also affects other sections): ... URI-list servers can use URIs tagged with the 'anonymize' attribute for routing SIP requests, but MUST convert them to an anonymized URI (such as sip:anonymous@anonymous.invalid) in recipient-history lists. I think that to be watertight, the anonymous URI should be well-defined, i.e. not 'such as' but simply 'MUST be sip:anonymous@anonymous.invalid'. Also, but less important: There's a booby-trap in blind-copied email, namely sending a reply-all without noticing that you've been blind-copied. Would it be useful to add a 'blind-copy' attribute for Bcc recipients, so that they can easily know about it?