Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)
draft-ietf-sipping-3pcc-06
Revision differences
Document history
| Date | Rev. | By | Action |
|---|---|---|---|
|
2004-01-20
|
06 | Amy Vezza | State Changes to RFC Ed Queue from Approved-announcement sent by Amy Vezza |
|
2004-01-20
|
06 | Amy Vezza | IESG state changed to Approved-announcement sent |
|
2004-01-20
|
06 | Amy Vezza | IESG has approved the document |
|
2004-01-20
|
06 | (System) | Ballot writeup text was added |
|
2004-01-20
|
06 | (System) | Last call text was added |
|
2004-01-20
|
06 | (System) | Ballot approval text was added |
|
2004-01-20
|
06 | Allison Mankin | State Changes to Approved-announcement to be sent from IESG Evaluation::AD Followup by Allison Mankin |
|
2004-01-06
|
06 | (System) | New version available: draft-ietf-sipping-3pcc-06.txt |
|
2003-12-26
|
06 | Allison Mankin | State Changes to IESG Evaluation::AD Followup from IESG Evaluation::Revised ID Needed by Allison Mankin |
|
2003-12-26
|
06 | Allison Mankin | [Note]: '-06 contains revs to address the comments.' added by Allison Mankin |
|
2003-12-14
|
06 | Allison Mankin | State Changes to IESG Evaluation::Revised ID Needed from IESG Evaluation::AD Followup by Allison Mankin |
|
2003-12-14
|
06 | Allison Mankin | [Note]: '0.0.0.0 needs to stay because SDP implementation will crash if they cannot resolve an FQDN (.invalid). This rev was made but the Discuss comments … [Note]: '0.0.0.0 needs to stay because SDP implementation will crash if they cannot resolve an FQDN (.invalid). This rev was made but the Discuss comments were not noted (there was a lapse in communications - AD lapse, mainly) so this document still needs revs...I propose that Erik''s comments be addressed by asking Thomas and Margaret to vet the responses, but that we not require a full new review by Margaret. ' added by Allison Mankin |
|
2003-12-14
|
06 | Allison Mankin | [Note]: '0.0.0.0 needs to stay because SDP implementation will crash if they cannot resolve an FQDN (.invalid). This rev was made but the Discuss comments … [Note]: '0.0.0.0 needs to stay because SDP implementation will crash if they cannot resolve an FQDN (.invalid). This rev was made but the Discuss comments were not noted (there was a lapse in communications - AD lapse, mainly) so this document still needs revs...I propose that Erik''s comments be addressed by asking Thomas and Margaret to vet the responses, but that we not require a full new review by Margaret. ' added by Allison Mankin |
|
2003-12-14
|
06 | Allison Mankin | 0.0.0.0 needs to stay because SDP implementation will crash if they cannot resolve an FQDN (.invalid). This rev was made but the Discuss comments were … 0.0.0.0 needs to stay because SDP implementation will crash if they cannot resolve an FQDN (.invalid). This rev was made but the Discuss comments were not noted (there was a lapse in communications - AD lapse, mainly) so this document still needs revs...I propose that Erik's comments be addressed by asking Thomas and Margaret to vet the responses, but that we not require a full new review by Margaret. |
|
2003-11-02
|
06 | Allison Mankin | State Changes to IESG Evaluation::AD Followup from IESG Evaluation - Defer::Revised ID Needed by Allison Mankin |
|
2003-10-28
|
05 | (System) | New version available: draft-ietf-sipping-3pcc-05.txt |
|
2003-07-10
|
06 | Amy Vezza | State Changes to IESG Evaluation - Defer :: Revised ID Needed from IESG Evaluation by Vezza, Amy |
|
2003-07-03
|
06 | Allison Mankin | State Changes to IESG Evaluation from IESG Evaluation :: Revised ID Needed by Mankin, Allison |
|
2003-07-03
|
04 | (System) | New version available: draft-ietf-sipping-3pcc-04.txt |
|
2003-06-24
|
06 | Allison Mankin | State Changes to IESG Evaluation :: Revised ID Needed from IESG Evaluation :: AD Followup by Mankin, Allison |
|
2003-06-24
|
06 | Allison Mankin | Revision coming to change usage of 0.0.0.0, which is against RFC 1122 (means this host) to an fqdn like xxx.invalid, if authors and WG support … Revision coming to change usage of 0.0.0.0, which is against RFC 1122 (means this host) to an fqdn like xxx.invalid, if authors and WG support the solution, recommended by a quorum of IESG and IAB - this is the last fix needed before agenda again...2003-06-23. |
|
2003-06-24
|
06 | Allison Mankin | Sent this for new security look to Ekr after an IESG discussion of identities, and we agreed it needs to caveat usage of identities between … Sent this for new security look to Ekr after an IESG discussion of identities, and we agreed it needs to caveat usage of identities between controller and party it controls for. Working on way to convey this to authors to proceed with writeup and go back to process in IESG. [Note from Allison - 2002-10-22] The identity improvements were conveyed in various discussions. Rev 03 covered them. |
|
2003-03-06
|
03 | (System) | New version available: draft-ietf-sipping-3pcc-03.txt |
|
2002-11-01
|
06 | Allison Mankin | State Changes to IESG Evaluation :: AD Followup from Expert Review by Mankin, Allison |
|
2002-10-22
|
06 | Allison Mankin | State Changes to Expert Review -- 0 from AD Evaluation -- Point Raised - writeup needed by mankin |
|
2002-06-05
|
06 | Stephen Coya | State changes to Wait for Writeup from Last Call Issued by IETF Secretariat |
|
2002-06-05
|
02 | (System) | New version available: draft-ietf-sipping-3pcc-02.txt |
|
2002-05-29
|
01 | (System) | New version available: draft-ietf-sipping-3pcc-01.txt |
|
2002-05-20
|
06 | (System) | Last call sent |
|
2002-05-15
|
06 | Stephen Coya | Draft Added by scoya |
|
2002-05-10
|
00 | (System) | New version available: draft-ietf-sipping-3pcc-00.txt |