The call flow documents do not meet the current criteria defined by
hitchhikers for inclusion. That criteria is:
It is very difficult to enumerate the set of SIP specifications.
This is because there are many protocols that are intimately related
to SIP and used by nearly all SIP implementations, but are not
formally SIP extensions. As such, this document formally defines a
"SIP specification" as:
o Any specification that defines an extension to SIP itself, where
an extension is a mechanism that changes or updates in some way a
behavior specified in RFC 3261
o Any specification that defines an extension to SDP whose primary
purpose is to support SIP
o Any specification that defines a MIME object whose primary purpose
is to support SIP
Example call flows do not meet this criteria.
-Jonathan R.
Peter Saint-Andre wrote:
Brian Stucker wrote:
<snip/>
Sorry to hijack this thread, but I'd like to second a comment that Mary
Barnes made during the WGLC:
http://www1.ietf.org/mail-archive/web/sip/current/msg20981.html
***
It seems that all the call flow BCPs are missing and I do think those
are really important and should be included in this document. The only
BCP (type (B) document) listed in this document is 3PCC. The basic call
flow document (RFC 3665) should be listed in section 3 (Core SIP). The
PSTN call flows (RFC 3666, BCP 76) should be in PSTN Interworking
section 4. The SIPPING NAT scenarios document should be in the NAT
section 6. These docs are all icing on the cake IMHO and help to guide
implementers in using all the other docs.
***
I agree that the call flow documents are very useful and that a
reference to them would be a good thing.
Peter
--
Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza
Cisco Fellow Parsippany, NJ 07054-2711
Cisco Systems
[EMAIL PROTECTED] FAX: (973) 952-5050
http://www.jdrosen.net PHONE: (973) 952-5000
http://www.cisco.com
_______________________________________________
Sip mailing list https://www1.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
