Re: [sipcore] privacy handlingRe: [sipcore] privacy handling
Mary Barnes
2010-08-31
sipcore
/arch/msg/sipcore/JJPFf7pu9NoWufskyoL4EuxM9wg/
1356912
1616332
Re: [sipcore] Tracker EtiquetteRe: [sipcore] Tracker Etiquette
Paul Kyzivat
2010-08-31
sipcore
/arch/msg/sipcore/FJElZH7S7t62oI0H_ZiJ37WshX4/
1356911
1616305
Re: [sipcore] privacy handlingRe: [sipcore] privacy handling
Paul Kyzivat
2010-08-31
sipcore
/arch/msg/sipcore/M9vkvWLmxV3-Wnf6T3Or-id8VoE/
1356910
1616332
Re: [sipcore] privacy handlingRe: [sipcore] privacy handling
Mary Barnes
2010-08-31
sipcore
/arch/msg/sipcore/LpW152Q3qOK_AjpbMyY8XOTcIeo/
1356909
1616332
Re: [sipcore] Tracker EtiquetteRe: [sipcore] Tracker Etiquette
James M. Polk
2010-08-31
sipcore
/arch/msg/sipcore/5yoit7sgFYD0HXv3eHX_D7vlETs/
1356908
1616305
[sipcore] Tracker Etiquette[sipcore] Tracker Etiquette
Adam Roach
2010-08-31
sipcore
/arch/msg/sipcore/WmX99mDPP0Vy5clBO1G1HA5yAQQ/
1356907
1616305
Re: [sipcore] #34: Semantics of History-Info values need to be documented explicitlyRe: [sipcore] #34: Semantics of History-Info values need to be documented explicitly
Mary Barnes
2010-08-31
sipcore
/arch/msg/sipcore/KBUmFp7WGwhUO7f1V1b46P4LDCA/
1356906
1616314
Re: [sipcore] #29: B2BUAs passing H-I through?Re: [sipcore] #29: B2BUAs passing H-I through?
Mary Barnes
2010-08-31
sipcore
/arch/msg/sipcore/WIMt5Lvsis0NrvuQcvNszfl7biA/
1356905
1616319
Re: [sipcore] #2: Editorial: section 2 is really confusingRe: [sipcore] #2: Editorial: section 2 is really confusing
Mary Barnes
2010-08-31
sipcore
/arch/msg/sipcore/-WegWXoCUYcqykXBuWrVM1G8exc/
1356904
1616349
Re: [sipcore] #2: Editorial: section 2 is really confusingRe: [sipcore] #2: Editorial: section 2 is really confusing
Worley, Dale R (Dale)
2010-08-31
sipcore
/arch/msg/sipcore/YeWyU0ssyELYN4UDndk8lF9xWrs/
1356903
1616349
[sipcore] #42: Backwards compatibility[sipcore] #42: Backwards compatibility
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/HUgh6ervKVyaiiwtzTo0QkPuQTQ/
1356902
1616306
[sipcore] #41: Why does only "mp" have a value?[sipcore] #41: Why does only "mp" have a value?
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/BxqERM6FwRdwfgh27xNxN_Ihkiw/
1356901
1616307
[sipcore] #40: Clarify mp-value[sipcore] #40: Clarify mp-value
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/pK8urZGXbSpkmvYNlNmDt2X52PA/
1356900
1616308
[sipcore] #39: Correct use of "define"[sipcore] #39: Correct use of "define"
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/pzRBuqSQYfuCDBzyujJDWFdQ-rE/
1356899
1616309
[sipcore] #38: How is the mapping of a GRUU into its UA Contact marked?[sipcore] #38: How is the mapping of a GRUU into its UA Contact marked?
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/nfDC7MPxcWH-oOHxCbSs36jUfwI/
1356898
1616310
[sipcore] #37: Clarify use of rc vs. mp[sipcore] #37: Clarify use of rc vs. mp
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/jleRc4DNA5AVHmgYYwX33ww0my8/
1356897
1616311
[sipcore] #36: Clarify wording[sipcore] #36: Clarify wording
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/esLxFx2Vo3edlkHV8A0JSE4lyUo/
1356896
1616312
[sipcore] #35: "target parameter" is used but seems to have no meaning[sipcore] #35: "target parameter" is used but seems to have no meaning
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/7BOJpIEsXbwmmx-TxoEFrBxeFxM/
1356895
1616313
[sipcore] #34: Semantics of History-Info values need to be documented explicitly[sipcore] #34: Semantics of History-Info values need to be documented explicitly
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/-ghTneDzjvNTGMAwY5WqATuyB8s/
1356894
1616314
[sipcore] #33: Confusing text in section 6.1[sipcore] #33: Confusing text in section 6.1
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/hnzu8-TkTonxV5HxMNDffMQ6sJ4/
1356893
1616315
[sipcore] #32: Section 6.1 para 2 phrasing[sipcore] #32: Section 6.1 para 2 phrasing
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/zkSIjyPFMGkSgCjm535VemTrKp0/
1356892
1616316
[sipcore] #31: Section 6.1 rules[sipcore] #31: Section 6.1 rules
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/A7DWkbI4dJgSa3zO4tnwP9lrQzc/
1356891
1616317
[sipcore] #30: Section 6.1 formatting nits[sipcore] #30: Section 6.1 formatting nits
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/wPX5CEIWAUfPquc7f7HP_QnQmSk/
1356890
1616318
[sipcore] #29: B2BUAs passing H-I through?[sipcore] #29: B2BUAs passing H-I through?
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/thKOEmXHXiaz2Ui7DKfTvo9mHGA/
1356889
1616319
[sipcore] #28: UACs should add H-I if they implement it[sipcore] #28: UACs should add H-I if they implement it
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/JCS5U1d9lDw_kaJzkinHlp6kDAM/
1356888
1616320
[sipcore] #27: Functionality of "Supported: histinfo" is not clear[sipcore] #27: Functionality of "Supported: histinfo" is not clear
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/Ps0y8TIYnV_1XlctwEVch023p_k/
1356887
1616321
[sipcore] #26: Wording nit[sipcore] #26: Wording nit
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/LVq8FG4JDJoS0hI8iV9VRqFveHw/
1356886
1616322
[sipcore] #25: Proxy adding H-I must create element 1.[sipcore] #25: Proxy adding H-I must create element 1.
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/qtqN2t2CbPmRPMpXEaBsYnb9frI/
1356885
1616323
[sipcore] #24: Redirect servers[sipcore] #24: Redirect servers
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/WalCoQz56rCyH0lmVbwTpROby94/
1356884
1616324
[sipcore] #23: Which elements a particular normative passage applies to[sipcore] #23: Which elements a particular normative passage applies to
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/TvfGfgy_TQnOsVx0lJX2IuSIFvY/
1356883
1616325
[sipcore] #22: Punctuation inside of quoted text is potentially confusing.[sipcore] #22: Punctuation inside of quoted text is potentially confusing.
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/5imli1MQR8X48sV0HbziVMiedxs/
1356882
1616326
[sipcore] #21: "request not associated with an established dialog"[sipcore] #21: "request not associated with an established dialog"
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/I78qHtva2fEJ7oapCl-Dv09hjmY/
1356881
1616327
[sipcore] #20: Handling canceled forks[sipcore] #20: Handling canceled forks
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/OLiLA-wCnpmJReRLOLyYVk_P604/
1356880
1616328
[sipcore] #19: Show 487 response to CANCEL[sipcore] #19: Show 487 response to CANCEL
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/YEeXI1vyAYZBzih3xk_e04yzbc0/
1356879
1616329
[sipcore] #18: Awkward description[sipcore] #18: Awkward description
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/b4tXPj4wApgmR64xW6LPMTyglXo/
1356878
1616330
Re: [sipcore] privacy handlingRe: [sipcore] privacy handling
Paul Kyzivat
2010-08-31
sipcore
/arch/msg/sipcore/dPmvijZdXPItbhezeIX0kTAuFxs/
1356877
1616332
[sipcore] #17: Unclear phrasing[sipcore] #17: Unclear phrasing
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/fnO5rcgyqgK-xpppAOA-DrYz0Ds/
1356876
1616331
Re: [sipcore] privacy handlingRe: [sipcore] privacy handling
Worley, Dale R (Dale)
2010-08-31
sipcore
/arch/msg/sipcore/vSYd7uXtusNkOTieTF2gFyrtcy4/
1356875
1616332
Re: [sipcore] REMINDER: Re: WGLC: draft-ietf-sipcore-rfc4244bisRe: [sipcore] REMINDER: Re: WGLC: draft-ietf-sipcore-rfc4244bis
Elwell, John
2010-08-31
sipcore
/arch/msg/sipcore/oF00ymHTR6ki2O537Q987vGbcyk/
1356874
1616143
Re: [sipcore] #8: It's not clear when a Proxy should/should-not add H-I for "internal" stuffRe: [sipcore] #8: It's not clear when a Proxy should/should-not add H-I for "internal" stuff
Worley, Dale R (Dale)
2010-08-31
sipcore
/arch/msg/sipcore/NNiSJTVQ5ImbQnqrOW6FnZCYP5s/
1356873
1616342