Subject
From
Date
List
[sipcore] #10: Convert all SHOULDs to MUST[sipcore] #10: Convert all SHOULDs to MUST
sipcore issue tracker
2010-08-30
sipcore
/arch/msg/sipcore/dxPOTAii4d9J3iMuYiap7BZE9w4/
1356844
1616340
Re: [sipcore] #10: Convert all SHOULDs to MUSTRe: [sipcore] #10: Convert all SHOULDs to MUST
Dean Willis
2010-08-30
sipcore
/arch/msg/sipcore/N9ter35rQbjzlsbU8TVvDJ1W58M/
1356853
1616340
Re: [sipcore] #10: Convert all SHOULDs to MUSTRe: [sipcore] #10: Convert all SHOULDs to MUST
Hadriel Kaplan
2010-08-30
sipcore
/arch/msg/sipcore/-WAUiDCvwLx1RQh2g0kg7aHUHKg/
1356856
1616340
Re: [sipcore] #10: Convert all SHOULDs to MUSTRe: [sipcore] #10: Convert all SHOULDs to MUST
Paul Kyzivat
2010-08-30
sipcore
/arch/msg/sipcore/dCZpf74y_Z-B946aCtjojyMxujY/
1356859
1616340
Re: [sipcore] #10: Convert all SHOULDs to MUSTRe: [sipcore] #10: Convert all SHOULDs to MUST
Mary Barnes
2010-08-30
sipcore
/arch/msg/sipcore/MhfyjBt1KgnmX-voh0eo-92LxJE/
1356861
1616340
Re: [sipcore] #10: Convert all SHOULDs to MUSTRe: [sipcore] #10: Convert all SHOULDs to MUST
Paul Kyzivat
2010-08-30
sipcore
/arch/msg/sipcore/B1MitshB-5joFwYXgExy3c5IYUc/
1356867
1616340
Re: [sipcore] #10: Convert all SHOULDs to MUSTRe: [sipcore] #10: Convert all SHOULDs to MUST
Elwell, John
2010-09-01
sipcore
/arch/msg/sipcore/SzHX-L6LGkdY6CBlwTrHDNMyf4M/
1356926
1616340
Re: [sipcore] #10: Convert all SHOULDs to MUSTRe: [sipcore] #10: Convert all SHOULDs to MUST
Mary Barnes
2010-10-13
sipcore
/arch/msg/sipcore/xpSueHDfqIjT3ixBt_eHeVCUjNU/
1357144
1616340
[sipcore] #9: What should an SBC do when it resolves registered contacts?[sipcore] #9: What should an SBC do when it resolves registered contacts?
sipcore issue tracker
2010-08-30
sipcore
/arch/msg/sipcore/jhTvoqCelfG254tvKpSs5vQvucc/
1356843
1616341
Re: [sipcore] #9: What should an SBC do when it resolves registered contacts?Re: [sipcore] #9: What should an SBC do when it resolves registered contacts?
Paul Kyzivat
2010-08-30
sipcore
/arch/msg/sipcore/kxOMdIekyDQv1NGxSdEPBZr-ti4/
1356845
1616341
Re: [sipcore] #9: What should an SBC do when it resolves registered contacts?Re: [sipcore] #9: What should an SBC do when it resolves registered contacts?
Hadriel Kaplan
2010-08-30
sipcore
/arch/msg/sipcore/rVDyNIVUDJzqQJmlnfEm2Z1XbOE/
1356851
1616341
Re: [sipcore] #9: What should an SBC do when it resolves registered contacts?Re: [sipcore] #9: What should an SBC do when it resolves registered contacts?
Paul Kyzivat
2010-08-30
sipcore
/arch/msg/sipcore/HJ1dKzwILPmkjwzscuu9cKelRqU/
1356852
1616341
Re: [sipcore] #9: What should an SBC do when it resolves registered contacts?Re: [sipcore] #9: What should an SBC do when it resolves registered contacts?
Hadriel Kaplan
2010-08-30
sipcore
/arch/msg/sipcore/uZShoWV_juIqlDc4Hyr4Zwrvh3o/
1356855
1616341
Re: [sipcore] #9: What should an SBC do when it resolves registered contacts?Re: [sipcore] #9: What should an SBC do when it resolves registered contacts?
Paul Kyzivat
2010-08-30
sipcore
/arch/msg/sipcore/j_JwxWucpkB3xR01vafJmJ9Ko88/
1356857
1616341
Re: [sipcore] #9: What should an SBC do when it resolves registered contacts?Re: [sipcore] #9: What should an SBC do when it resolves registered contacts?
Mary Barnes
2010-10-13
sipcore
/arch/msg/sipcore/CUHMNGkVSZqb-QI6Bx7vF3b9r0Y/
1357149
1616341
[sipcore] #8: It's not clear when a Proxy should/should-not add H-I for "internal" stuff[sipcore] #8: It's not clear when a Proxy should/should-not add H-I for "internal" stuff
sipcore issue tracker
2010-08-30
sipcore
/arch/msg/sipcore/EiQBRlmdT0x5wRhrwR_3tmiFSx0/
1356842
1616342
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
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
Shida Schubert
2010-09-01
sipcore
/arch/msg/sipcore/4MRhb53FJGCdIy8SP_dXy-YjsJ8/
1356938
1616342
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-09-02
sipcore
/arch/msg/sipcore/CG661FTJpe3ArrczfDOP5InNHuA/
1356950
1616342
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
Mary Barnes
2010-09-02
sipcore
/arch/msg/sipcore/Q7YevIc96wvLNne-fYIJisuym6U/
1356952
1616342
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
Mary Barnes
2010-10-13
sipcore
/arch/msg/sipcore/BnKEOadviNoCh_EQaWGUoH0xWtA/
1357150
1616342
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
Hadriel Kaplan
2010-09-02
sipcore
/arch/msg/sipcore/6WkEcSZgf7C8Z3n5ojI50k0OWRQ/
1356957
1616342
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-09-02
sipcore
/arch/msg/sipcore/C48ELJ4QbVMjgF3ZZlFIgagwoAY/
1356962
1616342
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
Mary Barnes
2010-10-13
sipcore
/arch/msg/sipcore/jfE104Unfe4AuXs2tq_x4s-lMC0/
1357147
1616342
[sipcore] Comments on draft-barnes-sipcore-rfc4244bis-callflows-00[sipcore] Comments on draft-barnes-sipcore-rfc4244bis-callflows-00
Hadriel Kaplan
2010-08-30
sipcore
/arch/msg/sipcore/hnLwuoeKq2D46SvUAIPYOSrZ-ls/
1356841
1616343
[sipcore] #7: Request timeouts are 408, NOT 487 status codes[sipcore] #7: Request timeouts are 408, NOT 487 status codes
sipcore issue tracker
2010-08-26
sipcore
/arch/msg/sipcore/eb4SIawVOjb7jjWjQclAkxeIKy0/
1356830
1616344
Re: [sipcore] #7: Request timeouts are 408, NOT 487 status codesRe: [sipcore] #7: Request timeouts are 408, NOT 487 status codes
Mary Barnes
2010-08-28
sipcore
/arch/msg/sipcore/zPoygkrdHK0JO7iT1gsixa5HQ9k/
1356837
1616344
[sipcore] #6: Editorial: incorrect 6.3.4 rule 4 explanatory text[sipcore] #6: Editorial: incorrect 6.3.4 rule 4 explanatory text
sipcore issue tracker
2010-08-26
sipcore
/arch/msg/sipcore/3N-4mkMhQwagD3xEUp7QvI7UR0Y/
1356829
1616345
Re: [sipcore] #6: Editorial: incorrect 6.3.4 rule 4 explanatory textRe: [sipcore] #6: Editorial: incorrect 6.3.4 rule 4 explanatory text
Mary Barnes
2010-08-28
sipcore
/arch/msg/sipcore/XShYh73j5d0G9Xwk1qKDVN7R3a4/
1356836
1616345
[sipcore] #5: Privacy value of "session" should NOT apply to H-I headers[sipcore] #5: Privacy value of "session" should NOT apply to H-I headers
sipcore issue tracker
2010-08-26
sipcore
/arch/msg/sipcore/rztQp0G7DjUpX808sTNHiKvHYUY/
1356828
1616346
Re: [sipcore] #5: Privacy value of "session" should NOT apply to H-I headersRe: [sipcore] #5: Privacy value of "session" should NOT apply to H-I headers
Mary Barnes
2010-08-28
sipcore
/arch/msg/sipcore/lJxMb6a9bUToqlfxALUbHG_Q-AY/
1356835
1616346
[sipcore] #4: The new "hit" parameter is gonna cause problems[sipcore] #4: The new "hit" parameter is gonna cause problems
sipcore issue tracker
2010-08-25
sipcore
/arch/msg/sipcore/SgI-lxHIi8E47qixm_2XusWoYUA/
1356826
1616347
Re: [sipcore] #4: The new "hit" parameter is gonna cause problemsRe: [sipcore] #4: The new "hit" parameter is gonna cause problems
Mary Barnes
2010-08-28
sipcore
/arch/msg/sipcore/zfo61_GpzW6IhYXyFGnX3z_qr1k/
1356834
1616347
Re: [sipcore] #4: The new "hit" parameter is gonna cause problemsRe: [sipcore] #4: The new "hit" parameter is gonna cause problems
Paul Kyzivat
2010-08-30
sipcore
/arch/msg/sipcore/hMwQNHO4v45AZky-mIPpovN4Slc/
1356838
1616347
Re: [sipcore] #4: The new "hit" parameter is gonna cause problemsRe: [sipcore] #4: The new "hit" parameter is gonna cause problems
Hadriel Kaplan
2010-08-30
sipcore
/arch/msg/sipcore/t9mAdM0d3fYgamU0XupnCmwQiSs/
1356839
1616347
Re: [sipcore] #4: The new "hit" parameter is gonna cause problemsRe: [sipcore] #4: The new "hit" parameter is gonna cause problems
Hadriel Kaplan
2010-08-30
sipcore
/arch/msg/sipcore/9j3sbtPjkJ8DQs8n1JtZeWX6pyY/
1356858
1616347
Re: [sipcore] #4: The new "hit" parameter is gonna cause problemsRe: [sipcore] #4: The new "hit" parameter is gonna cause problems
Elwell, John
2010-09-01
sipcore
/arch/msg/sipcore/bsnsjf06urNK3zXvIKfRLBNUMTY/
1356930
1616347
Re: [sipcore] #4: The new "hit" parameter is gonna cause problemsRe: [sipcore] #4: The new "hit" parameter is gonna cause problems
Mary Barnes
2010-10-13
sipcore
/arch/msg/sipcore/bnWIZxv61X4UqzoJrvFVTRSjSSc/
1357143
1616347
Re: [sipcore] #4: The new "hit" parameter is gonna cause problemsRe: [sipcore] #4: The new "hit" parameter is gonna cause problems
sipcore issue tracker
2010-08-31
sipcore
/arch/msg/sipcore/Q-QutzRCJs9jc2mB20ahv9Z-Qno/
1356871
1616347
[sipcore] #3: Gaps in H-I headers should NOT be treated as "malicious"[sipcore] #3: Gaps in H-I headers should NOT be treated as "malicious"
sipcore issue tracker
2010-08-25
sipcore
/arch/msg/sipcore/TAkcw-aK3UwD6aZ8hma2THUhVns/
1356825
1616348