Timeline


and

17/09/10:

17:45 Ticket #22 (Punctuation inside of quoted text is potentially confusing.) closed by worley@…
duplicate: Incorporated into Ticket #43.
17:44 Ticket #26 (Wording nit) closed by worley@…
duplicate: Incorporated into Ticket #43.
17:43 Ticket #17 (Unclear phrasing) closed by worley@…
duplicate: Incorporated into Ticket #43.
17:42 Ticket #31 (Section 6.1 rules) closed by worley@…
duplicate: Incorporated into Ticket #43.
17:41 Ticket #33 (Confusing text in section 6.1) closed by worley@…
duplicate: Incorporated into Ticket #43.
17:40 Ticket #36 (Clarify wording) closed by worley@…
duplicate: Incorporated into Ticket #43.
17:40 Ticket #39 (Correct use of "define") closed by worley@…
duplicate: Incorporated into Ticket #43.
17:38 Ticket #30 (Section 6.1 formatting nits) closed by worley@…
duplicate
17:35 Ticket #43 (Small fixes) created by worley@…
This ticket is a collection of items that are either editorial nits …

31/08/10:

18:35 Ticket #42 (Backwards compatibility) created by worley@…
A particularly common backwards compatibility problem will be the …
18:28 Ticket #41 (Why does only "mp" have a value?) created by worley@…
There seems to be no reason to restrict the "mp-value", the …
18:22 Ticket #40 (Clarify mp-value) created by worley@…
In section 6.3.5, the rules for the value part of the mp parameter of …
18:21 Ticket #39 (Correct use of "define") created by worley@…
Section 6.3.1 para 5 is: The following defines the ABNF for the …
18:19 Ticket #38 (How is the mapping of a GRUU into its UA Contact marked?) created by worley@…
It seems that a common case is the mapping of a GRUU into its UA's …
18:16 Ticket #37 (Clarify use of rc vs. mp) created by worley@…
Section 6.3.1 para 3 defines two values for "hit". There are three …
18:12 Ticket #36 (Clarify wording) created by worley@…
Section 6.3.1 para 1 starts: This specification defines a new …
18:10 Ticket #35 ("target parameter" is used but seems to have no meaning) created by worley@…
In various places reference is made to a "target parameter" for …
18:08 Ticket #34 (Semantics of History-Info values need to be documented explicitly) created by worley@…
The draft doesn't give a clear specification of History-Info *as a …
18:02 Ticket #33 (Confusing text in section 6.1) created by worley@…
I see the sentence "The following summarizes the syntax..." -- this …
18:00 Ticket #32 (Section 6.1 para 2 phrasing) created by worley@…
The following sentence is not clear -- how does "parameters required …
17:58 Ticket #31 (Section 6.1 rules) created by worley@…
In section 6.1 is: The following rules apply: o There MUST be …
17:55 Ticket #30 (Section 6.1 formatting nits) created by worley@…
Stray double-quote: History-Info is a header field as defined by …
17:51 Ticket #29 (B2BUAs passing H-I through?) created by worley@…
In sections 4.1 and 4.2.1 there is text suggesting that B2BUAs that …
17:48 Ticket #28 (UACs should add H-I if they implement it) created by worley@…
In section 4.1 is: Normally, UACs are not expected to include a …
17:44 Ticket #27 (Functionality of "Supported: histinfo" is not clear) created by worley@…
The functionality of "Supported: histinfo" is not clear. It seems …
17:42 Ticket #26 (Wording nit) created by worley@…
In section 5.2 is "SHOULD forward captured History-Info in subsequent, …
17:39 Ticket #25 (Proxy adding H-I must create element 1.) created by worley@…
In section 5.1.1 Step 1, this should specify that if History-Info is …
17:37 Ticket #24 (Redirect servers) created by worley@…
In section 4.3, I see: A redirect server MUST NOT add any new …
17:34 Ticket #23 (Which elements a particular normative passage applies to) created by worley@…
In regard to the general notes in section 4.1: Prior to any …
17:29 Ticket #22 (Punctuation inside of quoted text is potentially confusing.) created by worley@…
This: A UAC that does not want an hi-entry added due to privacy …
17:28 Ticket #21 ("request not associated with an established dialog") created by worley@…
The phrase "request not associated with an established dialog" is used …
17:26 Ticket #20 (Handling canceled forks) created by worley@…
Concerning this part of section 3 figure 1: | | …
17:22 Ticket #19 (Show 487 response to CANCEL) created by worley@…
In section 3 figure 1, I think this would be clearer if the 487 …
17:20 Ticket #18 (Awkward description) created by worley@…
This para in section 3 is awkward: This specification defines …
17:18 Ticket #17 (Unclear phrasing) created by worley@…
In section 3 is the odd phrase "any valid response" -- are there …

30/08/10:

20:15 Ticket #16 (Privacy behavior is confusing) created by hkaplan@…
[I'm submitting this ticket because when I read the draft the first …
19:20 Ticket #15 (Section 7 item 5 is wrong) created by hkaplan@…
Section 7 item 5 says: 5. Entry with the index that matches …
19:14 Ticket #14 (Section 7 item 4 is useless or misleading) created by hkaplan@…
Section 7 item 4 says: 4. Entry prior to first entry with …
19:08 Ticket #13 (Section 7 item 2 is not complete) created by hkaplan@…
Section 7 item 2 says: 2. Entry prior to last entry with …
19:02 Ticket #12 (Section 7 on Application Considerations needs work) created by hkaplan@…
The thing I fear the most about H-I is that different UAS will process …
18:39 Ticket #11 (H-I does not provide a "stronger security solution for SIP") created by hkaplan@…
Section 3 has the following bullet point: o A stronger security …
18:33 Ticket #10 (Convert all SHOULDs to MUST) created by hkaplan@…
I know this isn't something we have a rule for, but ISTM that "SHOULD" …
18:24 Ticket #9 (What should an SBC do when it resolves registered contacts?) created by hkaplan@…
In many deployments, SBC's perform a registration caching model, …
18:17 Ticket #8 (It's not clear when a Proxy should/should-not add H-I for "internal" stuff) created by hkaplan@…
Section 5.1 says: Retargeting is an iterative process, i.e., a …

26/08/10:

17:27 Ticket #7 (Request timeouts are 408, NOT 487 status codes) created by hkaplan@…
Section 6.3.3 says: If a request has timed out (instead of being …
17:02 Ticket #6 (Editorial: incorrect 6.3.4 rule 4 explanatory text) created by hkaplan@…
Section 6.3.4 rule 4 says: 4. Retargeting based upon a …
16:49 Ticket #5 (Privacy value of "session" should NOT apply to H-I headers) created by hkaplan@…
4424 (and 4424bis) have the H-I headers removed/anonymized with …

25/08/10:

23:46 Ticket #4 (The new "hit" parameter is gonna cause problems) created by hkaplan@…
If I understand it right, this draft creates a new SIP/SIPS URI param …
23:14 Ticket #3 (Gaps in H-I headers should NOT be treated as "malicious") created by hkaplan@…
Section 4.1 and 4.2.1 both say "The entries SHOULD be evaluated to …
23:03 Ticket #2 (Editorial: section 2 is really confusing) created by hkaplan@…
Section 2 "Conventions and terminology" defines two terms: "retarget" …
22:19 Ticket #1 (Editorial: section 3 is not an "Overview of Operations") created by hkaplan@…
Section 3 is titled "Overview of Operations". Of its 4 pages, it has …
Note: See TracTimeline for information about the timeline view.