Robert,
This is a very good first draft. I agree that "-> Trying to progress
3261 and dependencies including widely
implemented small updates (such as rport [RFC3581] and the non-
INVITE fixes [RFC4320])"
is probably about the right level.
As a general point, each SIP RFC that is not normatively referenced and
mandated by RFC 3261 is an optional part of SIP. So some "core" things
like support for receipt of REFER and support for receipt of Replaces
cannot be assumed. This has encouraged B2BUAs to use 3PCC techniques to
cover common functions such as call transfer. Another non-mandatory
capability is support of receipt of UPDATE, which is a much cleaner way
of doing things like session timer refresh, for example (avoids a
further SDP offer-answer exchange). Maybe it can't be included in the
scope of advancement to Draft Standard, but mandating some of these
things (at least support on receipt) might be worth considering.
I haven't thought about it in detail, but some initial comments:
- I am sure we will find quite a few things that have to be taken out,
because of lack of implementation. One big one might be S/MIME.
- If we no longer include RFC 2543 compatibility, we might also consider
incorporating those aspects of RFC 4916 that allow the From URI to
change mid-dialog (but not the SIP Identity bits).
- I was surprised to see RFC 3204 in the dependencies, but it seems it
is just for the handling parameter. Perhaps that could just be moved
into the Draft Standard rather than trying to move RFC 3204 to Draft.
- I am sure the implementation report will need some explicit statements
on SIPS.
- SDP is now RFC 4566 (mentioned in 1.2 but not in section 2).
- Under extensibility mechanisms, handling of unknown bodies or body
parts.
- " - Demonstrate that someone will cut and paste this list into some
inappropriate place without reading it before it's had review"
- this will probably be the easiest one to demonstrate!
John
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Robert Sparks
> Sent: 02 July 2008 23:11
> To: [email protected] List
> Subject: [Sip] Steps to Draft
>
> Please look over
> http://www.ietf.org/internet-drafts/draft-sparks-sip-steps-to-
> draft-00.txt
>
> as input into our discussion on advancing SIP to Draft.
>
> Thanks,
>
> RjS
>
> _______________________________________________
> 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
>
_______________________________________________
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
