Mapping and Interworking of Diversion Information between Diversion and History-Info Headers in the Session Initiation Protocol (SIP)
draft-mohali-diversion-history-info-07
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2010-08-10
|
07 | Cindy Morgan | State changed to RFC Ed Queue from Approved-announcement sent by Cindy Morgan |
2010-07-19
|
07 | Cindy Morgan | IESG state changed to Approved-announcement sent |
2010-07-19
|
07 | Cindy Morgan | IESG has approved the document |
2010-07-19
|
07 | Cindy Morgan | Closed "Approve" ballot |
2010-07-18
|
07 | Adrian Farrel | [Ballot Position Update] Position for Adrian Farrel has been changed to No Objection from Discuss by Adrian Farrel |
2010-07-18
|
07 | Adrian Farrel | [Ballot comment] The authors have included text in the Introduction that is very satisfactory and I have cleared my Discuss. I should have liked to … [Ballot comment] The authors have included text in the Introduction that is very satisfactory and I have cleared my Discuss. I should have liked to also see some note in the Abstract, but this is a non-blocking Comment that I leave to the authors to consider. Suitable text might be... This document does not recommend further implementation or deployment of the Diversion header. |
2010-07-18
|
07 | Adrian Farrel | [Ballot discuss] |
2010-07-02
|
07 | (System) | New version available: draft-mohali-diversion-history-info-07.txt |
2010-07-02
|
07 | (System) | Removed from agenda for telechat - 2010-07-01 |
2010-07-01
|
07 | Cindy Morgan | State Changes to IESG Evaluation::AD Followup from IESG Evaluation by Cindy Morgan |
2010-07-01
|
07 | Sean Turner | [Ballot Position Update] Position for Sean Turner has been changed to No Objection from Discuss by Sean Turner |
2010-07-01
|
07 | Sean Turner | [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: … [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off 3) Section 3.1: r/header:/header. ? 4) Section 7.4: There are some line breaks missing between paragraphs. 5) The period at the end of the line is invalid ABNF according to the BAP tool: cause-param = "cause" EQUAL Status-Code. ^ remove 6) Section 3.1: I don't think the final "," is supposed to be there: History-Info: ... index=1.1.1, ^ remove this 7) General: Shouldn't 2119 language be used in this document (and need a normative reference to 2119 and the boilerplate)? Especially in Section 5, 6, and 7.4? 8) Section 7.1: remove last "," ? History-Info: ... ;index=1.1.1.1, ^ remove this 9) Please add pointers to the security considerations in [RFC4244] and [RFC5806]. Something like: The security considerations in [RFC4244] and [RFC50806] apply. |
2010-07-01
|
07 | Sean Turner | [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: … [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off 3) Section 3.1: r/header:/header. ? 4) Section 7.4: There are some line breaks missing between paragraphs. 5) The period at the end of the line is invalid ABNF according to the BAP tool: cause-param = "cause" EQUAL Status-Code. ^ remove 6) Section 3.1: I don't think the final "," is supposed to be there: History-Info: ... index=1.1.1, ^ remove this 7) General: Shouldn't 2119 language be used in this document (and need a normative reference to 2119 and the boilerplate)? Especially in Section 5, 6, and 7.4? 8) Section 7.1: remove last "," ? History-Info: ... ;index=1.1.1.1, ^ remove this 9) Please add pointers to the security considerations in [RFC4244] and [RFC5806]. Something like: The security considerations in [RFC4244] and [RFC50806] apply. |
2010-07-01
|
07 | Sean Turner | [Ballot discuss] |
2010-07-01
|
07 | Jari Arkko | [Ballot Position Update] New position, No Objection, has been recorded by Jari Arkko |
2010-06-30
|
07 | Ron Bonica | [Ballot Position Update] New position, No Objection, has been recorded by Ron Bonica |
2010-06-30
|
07 | Sean Turner | [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: … [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off 3) Section 3.1: r/header:/header. ? 4) Section 7.4: There are some line breaks missing between paragraphs. |
2010-06-30
|
07 | Sean Turner | [Ballot discuss] 1) The period at the end of the line is invalid ABNF according to the BAP tool: cause-param = "cause" EQUAL Status-Code. … [Ballot discuss] 1) The period at the end of the line is invalid ABNF according to the BAP tool: cause-param = "cause" EQUAL Status-Code. ^ remove 2) Section 3.1: I don't think the final "," is supposed to be there: History-Info: ... index=1.1.1, ^ remove this 2) General: Shouldn't 2119 language be used in this document (and need a normative reference to 2119 and the boilerplate)? Especially in Section 5, 6, and 7.4? 3) Section 7.1: remove last "," ? History-Info: ... ;index=1.1.1.1, ^ remove this 4) Please add pointers to the security considerations in [RFC4244] and [RFC5806]. Something like: The security considerations in [RFC4244] and [RFC50806] apply. |
2010-06-30
|
07 | Sean Turner | [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: … [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off 3) Section 3.1: r/header:/header. ? 4) Section 7.4: There are some line breaks missing between paragraphs. |
2010-06-30
|
07 | Sean Turner | [Ballot discuss] 1) The period is invalid ABNF: cause-param = "cause" EQUAL Status-Code. … [Ballot discuss] 1) The period is invalid ABNF: cause-param = "cause" EQUAL Status-Code. ^ remove 2) Section 3.1: I don't think the final "," is supposed to be there: History-Info: ... index=1.1.1, ^ remove this 2) General: Shouldn't 2119 language be used in this document (and need a normative reference to 2119 and the boilerplate)? Especially in Section 5, 6, and 7.4? 3) Section 7.1: remove last "," ? History-Info: ... ;index=1.1.1.1, ^ remove this 4) Please add pointers to the security considerations in [RFC4244] and [RFC5806]. Something like: The security considerations in [RFC4244] and [RFC50806] apply. |
2010-06-30
|
07 | Sean Turner | [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: … [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off 3) Section 3.1: r/header:/header. ? 4) Section 7.4: There are some line breaks missing between paragraphs. |
2010-06-30
|
07 | Sean Turner | [Ballot discuss] 1) The period is invalid ABNF: cause-param = "cause" EQUAL Status-Code. … [Ballot discuss] 1) The period is invalid ABNF: cause-param = "cause" EQUAL Status-Code. ^ remove 2) Section 3.1: I don't think the final "," is supposed to be there: History-Info: ... index=1.1.1, ^ remove this 2) General: Shouldn't 2119 language be used in this document (and need a normative reference to 2119 and the boilerplate)? Especially in Section 5, 6, and 7.4? 3) Section 7.1: remove last "," ? History-Info: ... ;index=1.1.1.1, ^ remove 4) Please add pointers to the security considerations in [RFC4244] and [RFC5806]. Something like: The security considerations in [RFC4244] and [RFC50806] apply. |
2010-06-30
|
07 | Sean Turner | [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: … [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off 3) Section 3.1: r/header:/header. ? 4) Section 7.4: There are some line breaks missing between paragraphs. |
2010-06-30
|
07 | Sean Turner | [Ballot discuss] 1) The period is invalid ABNF: cause-param = "cause" EQUAL Status-Code. … [Ballot discuss] 1) The period is invalid ABNF: cause-param = "cause" EQUAL Status-Code. ^ remove 2) Section 3.1: I don't think the final "," is supposed to be there: History-Info: ;index=1, ;index=1.1, ; index=1.1.1, ^ remove this 2) General: Shouldn't 2119 language be used in this document (and need a normative reference to 2119 and the boilerplate)? Especially in Section 5, 6, and 7.4? 3) Section 7.1: remove last "," ? History-Info: ; index=1, ;index=1.1, ;index=1.1.1, ;index=1.1.1.1, ^ remove 4) Please add pointers to the security considerations in [RFC4244] and [RFC5806]. Something like: The security considerations in [RFC4244] and [RFC50806] apply. |
2010-06-30
|
07 | Sean Turner | [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: … [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off 3) Section 3.1: r/header:/header. ? 4) Section 7.4: There are some line breaks missing between paragraphs. |
2010-06-30
|
07 | Sean Turner | [Ballot discuss] 1) The period is invalid ABNF: cause-param = "cause" EQUAL Status-Code. … [Ballot discuss] 1) The period is invalid ABNF: cause-param = "cause" EQUAL Status-Code. ^ remove 2) Section 3.1: I don't think the final "," is supposed to be there: History-Info: ;index=1, ;index=1.1, ; index=1.1.1, ^ remove this 2) General: Shouldn't 2119 language be used in this document (and need a normative reference to 2119 and the boilerplate)? Especially in Section 5, 6, and 7.4? 3) Section 7.1: remove last "," ? History-Info: ; index=1, ;index=1.1, ;index=1.1.1, ;index=1.1.1.1, ^ remove 4) Please add pointers to the security considerations in [RFC4244] and [RFC5806]. Something like: The security considerations in [RFC4244] and [RFC50806] apply. |
2010-06-30
|
07 | Sean Turner | [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: … [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off 3) Section 3.1: r/header:/header. ? 4) Section 7.4: There are some line breaks missing between paragraphs. |
2010-06-30
|
07 | Sean Turner | [Ballot discuss] 1) The period is invalid ABNF: cause-param = "cause" EQUAL Status-Code. … [Ballot discuss] 1) The period is invalid ABNF: cause-param = "cause" EQUAL Status-Code. ^ remove 2) Section 3.1: I don't think the final "," is supposed to be there: History-Info: ;index=1, ;index=1.1, ; index=1.1.1, ^ remove this 2) General: Shouldn't 2119 language be used in this document (and need a normative reference to 2119 and the boilerplate)? Especially in Section 5, 6, and 7.4? 3) Section 7.1: remove last "," ? History-Info: ; index=1, ;index=1.1, ;index=1.1.1, ;index=1.1.1.1, ^ remove 4) Please add pointers to the security considerations in [RFC4244] and [RFC5806]. Something like: The security considerations in [RFC4244] and [RFC50806] apply. |
2010-06-30
|
07 | Sean Turner | [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: … [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off 3) Section 3.1: r/header:/header. ? 4) Section 7.4: There are some line breaks missing between paragraphs. |
2010-06-30
|
07 | Sean Turner | [Ballot discuss] 1) The period is invalid ABNF: cause-param = "cause" EQUAL Status-Code. … [Ballot discuss] 1) The period is invalid ABNF: cause-param = "cause" EQUAL Status-Code. ^ remove 2) Section 3.1: I don't think the final "," is supposed to be there: History-Info: ;index=1, ;index=1.1, ; index=1.1.1, ^ remove this 2) General: Shouldn't 2119 language be used in this document (and need a normative reference to 2119 and the boilerplate)? Especially in Section 5, 6, and 7.4? 3) Section 7.1: remove last "," ? History-Info: ; index=1, ;index=1.1, ;index=1.1.1, ;index=1.1.1.1, ^ remove 4) Please add pointers to the security considerations in [RFC4244] and [RFC5806]. Something like: The security considerations in [RFC4244] and [RFC50806] apply. |
2010-06-30
|
07 | Sean Turner | [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: … [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off |
2010-06-30
|
07 | Sean Turner | [Ballot discuss] 1) Section 3.1: I don't think the final "," is supposed to be there: History-Info: ;index=1, ;index=1.1, ; index=1.1.1, … [Ballot discuss] 1) Section 3.1: I don't think the final "," is supposed to be there: History-Info: ;index=1, ;index=1.1, ; index=1.1.1, ^ remove this |
2010-06-30
|
07 | Sean Turner | [Ballot Position Update] Position for Sean Turner has been changed to Discuss from No Objection by Sean Turner |
2010-06-30
|
07 | Sean Turner | [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: … [Ballot comment] 1) Section 1.2: r/deploye/deploy 2) Section 3: Remove line: OLD: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off NEW: diverting_user2_addr; reason="user-busy"; counter=1; privacy=full, diverting_user1_addr; reason="unconditional"; counter=1; privacy=off |
2010-06-30
|
07 | Amanda Baber | IANA understands that, upon approval of this document, there are no IANA Actions that need to be completed. |
2010-06-30
|
07 | Sean Turner | [Ballot Position Update] New position, No Objection, has been recorded by Sean Turner |
2010-06-30
|
07 | Dan Romascanu | [Ballot Position Update] New position, No Objection, has been recorded by Dan Romascanu |
2010-06-30
|
07 | Russ Housley | [Ballot Position Update] New position, No Objection, has been recorded by Russ Housley |
2010-06-30
|
07 | Gonzalo Camarillo | [Ballot Position Update] New position, No Objection, has been recorded by Gonzalo Camarillo |
2010-06-30
|
07 | Stewart Bryant | [Ballot comment] I agree with Adrian's Discuss |
2010-06-30
|
07 | Stewart Bryant | [Ballot Position Update] New position, No Objection, has been recorded by Stewart Bryant |
2010-06-30
|
07 | Adrian Farrel | [Ballot discuss] Discuss for consideration by the IESG. What is our position on an RFC that encourages the use of an alternative to an IETF … [Ballot discuss] Discuss for consideration by the IESG. What is our position on an RFC that encourages the use of an alternative to an IETF specification? While I understand the benefit of interworking being specificed, wouldn't it be better to have - a clear statement that the new implementation and deployment of the Diversion header is strongly discouraged - a stronger note that this work is intended to enable the migration from non-standard implementations and deployment toward IETF specification-based implementations and deployment. |
2010-06-30
|
07 | Adrian Farrel | [Ballot Position Update] New position, Discuss, has been recorded by Adrian Farrel |
2010-06-28
|
07 | Peter Saint-Andre | [Ballot Position Update] New position, No Objection, has been recorded by Peter Saint-Andre |
2010-06-28
|
07 | Robert Sparks | State Changes to IESG Evaluation from Publication Requested by Robert Sparks |
2010-06-28
|
07 | Robert Sparks | Placed on agenda for telechat - 2010-07-01 by Robert Sparks |
2010-06-28
|
07 | Robert Sparks | Note field has been cleared by Robert Sparks |
2010-06-28
|
07 | Robert Sparks | [Ballot Position Update] New position, Yes, has been recorded for Robert Sparks |
2010-06-28
|
07 | Robert Sparks | Ballot has been issued by Robert Sparks |
2010-06-28
|
07 | Robert Sparks | Created "Approve" ballot |
2010-06-28
|
07 | (System) | Ballot writeup text was added |
2010-06-28
|
07 | (System) | Last call text was added |
2010-06-28
|
07 | (System) | Ballot approval text was added |
2010-06-28
|
06 | (System) | New version available: draft-mohali-diversion-history-info-06.txt |
2010-05-20
|
07 | Cindy Morgan | Responsible AD has been changed to Robert Sparks from Russ Housley |
2010-05-20
|
07 | Cindy Morgan | Area acronymn has been changed to rai from gen |
2010-05-19
|
07 | Amy Vezza | Draft Added by Amy Vezza in state Publication Requested |
2010-02-03
|
05 | (System) | New version available: draft-mohali-diversion-history-info-05.txt |
2009-06-24
|
04 | (System) | New version available: draft-mohali-diversion-history-info-04.txt |
2009-05-04
|
03 | (System) | New version available: draft-mohali-diversion-history-info-03.txt |
2009-02-12
|
02 | (System) | New version available: draft-mohali-diversion-history-info-02.txt |
2008-11-01
|
01 | (System) | New version available: draft-mohali-diversion-history-info-01.txt |
2008-07-11
|
00 | (System) | New version available: draft-mohali-diversion-history-info-00.txt |