Hi,
Some comments: 1. Would it be good to add some words to section 2, saying that "For backward compabiltiy, this document does not forbid legacy usage of INFO with no info-package, as described in section 6.", or something like that... 2. Section 4.1 says: The text: "The initiating UA of the first INVITE MUST be prepared to receive multiple INFO requests, as the first INVITE may fork." ...should be modified with something like: "The initiation UA of the first INVITE MUST be prepared to receive INFO requests from multiple remote destinations, as the INVITE may fork." 3. In section 4.1, would it be good to add some explicit words about the fact that it is allowed for the UAS to send INFO during the early dialog? RFC3311 says the following for UPDATE: "The UPDATE request is constructed as would any other request within an existing dialog, as described in Section 12.2.1 of RFC 3261. It MAY be sent for both early and confirmed dialogs, and MAY be sent by either caller or callee." ...so I think we could say something similar for INFO. Regards, Christer > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Eric Burger > Sent: 6. tammikuuta 2009 14:24 > To: IETF SIP List > Subject: [Sip] INFO Stunning Silence > > I know, we are just back from vacation. However, for a > document that generated over 300 e-mails, I'm surprised there > isn't another flood. > > Check out: > http://tools.ietf.org/html/draft-ietf-sip-info-events-02 > > _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [email protected] for questions on current sip Use [email protected] for new developments on the application of sip
