[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sipping] Offer/answer LS: How to document it



Hi,

I don't think we need to move the offer/answer draft to the SIP WG.

The purpose of the draft is simply to clarify, not to specify protocol procedures. That is why I said that even if we document the decission regarding the re-INVITE fallback issue in the offer/answer draft, in addition we still need to also document it in some normative SIP document.

Regards,

Christer




-----Alkuperäinen viesti-----
Lähettäjä: Brett Tate [mailto:brett at broadsoft.com]
Lähetetty: to 7.8.2008 19:53
Vastaanottaja: Christer Holmberg; sipping LIST
Aihe: RE: [Sipping] Offer/answer LS: How to document it
 
> Is it too late to get it into draft-ietf-sipping-sip-offeranswer, 
> where it is still listed as an open issue (in addtion we of 
> course also needs to get it into normative text)?

Draft-ietf-sipping-sip-offeranswer currently has several open issues.
If there are to be normative updates to the SIP RFCs, it should likely
occur within the SIP WG.  Additionally, I'd prefer all the open issues
mentioned within draft-ietf-sipping-sip-offeranswer be addressed at the
same time.  I have no preference between 1) allowing
draft-ietf-sipping-sip-offeranswer to proceed with open issues or 2)
moving the draft to the SIP working group so the open issues can be
resolved.

_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sip at ietf.org for new developments of core SIP