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-sip-multiple-refer-02.txt Reviewer: Francis Dupont Review Date: 2007-11-24 IETF LC End Date: 2007-12-10 IESG Telechat date: unknown Summary: Almost Ready Comments: the comments are editorial, i.e., they enter in the kind of things which can be handled by the RFC Editor: - 2 page 3: according to the Introduction the REFER-recipient should be a server, not a user agent, i.e., either I've misunderstood the Introduction or there is a typo. - 5 page 4: NOTIFY requests -> messages (even they are requests (cf RFC 3261) in the common language it seems a bit strange to name them requests) - 6 page 5: I can understand this (punctuation issue?): As described in the Framework and Security Considerations for SIP URI-List Services [I-D.ietf-sipping-uri-services], specifications of individual URI-list services, need to specify a default format for 'recipient-list' bodies used within the particular service. - 6 page 6: XML Formats -> Format? - 8 page 8: the actual list of recipients -> targets? - 10 page 11: add "document" at the end of the first line as the subject of "discusses" - 10 page 11: an URI-list -> a URI-list Regards [EMAIL PROTECTED] _______________________________________________ Gen-art mailing list [email protected] https://www1.ietf.org/mailman/listinfo/gen-art
