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] #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
[sipcore] #16: Privacy behavior is confusing[sipcore] #16: Privacy behavior is confusing
sipcore issue tracker
2010-08-30
sipcore
/arch/msg/sipcore/GwhF9FddySsxwEZZruqHqN4AYTA/
1356854
1616334
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] #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/rVDyNIVUDJzqQJmlnfEm2Z1XbOE/
1356851
1616341
[sipcore] #15: Section 7 item 5 is wrong[sipcore] #15: Section 7 item 5 is wrong
sipcore issue tracker
2010-08-30
sipcore
/arch/msg/sipcore/XhJQc0ACrP9VTpdDUtWGimlFc4Y/
1356850
1616335
[sipcore] #14: Section 7 item 4 is useless or misleading[sipcore] #14: Section 7 item 4 is useless or misleading
sipcore issue tracker
2010-08-30
sipcore
/arch/msg/sipcore/nM8x-yrDWmFNIT3jLmYZHHhOElk/
1356849
1616336
[sipcore] #13: Section 7 item 2 is not complete[sipcore] #13: Section 7 item 2 is not complete
sipcore issue tracker
2010-08-30
sipcore
/arch/msg/sipcore/Gy8_21uhCGvS6HOFEmqgPtvLdAs/
1356848
1616337
[sipcore] #12: Section 7 on Application Considerations needs work[sipcore] #12: Section 7 on Application Considerations needs work
sipcore issue tracker
2010-08-30
sipcore
/arch/msg/sipcore/aap554JdaIRSgy0zU_6Wb7ie3Og/
1356847
1616338
[sipcore] #11: H-I does not provide a "stronger security solution for SIP"[sipcore] #11: H-I does not provide a "stronger security solution for SIP"
sipcore issue tracker
2010-08-30
sipcore
/arch/msg/sipcore/dFi0nuzAMrnU_O5ExcdYBItQVxg/
1356846
1616339
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
[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
[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
[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
[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
Re: [sipcore] #2: Editorial: section 2 is really confusingRe: [sipcore] #2: Editorial: section 2 is really confusing
Hadriel Kaplan
2010-08-30
sipcore
/arch/msg/sipcore/_VNkPEYivgQSyzKZVCGM9bxYfDc/
1356840
1616349
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
Paul Kyzivat
2010-08-30
sipcore
/arch/msg/sipcore/hMwQNHO4v45AZky-mIPpovN4Slc/
1356838
1616347
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
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
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
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] #3: Gaps in H-I headers should NOT be treated as "malicious"Re: [sipcore] #3: Gaps in H-I headers should NOT be treated as "malicious"
Mary Barnes
2010-08-28
sipcore
/arch/msg/sipcore/xXuspm80PXMdEdLlFd_eqq2SR5g/
1356833
1616348
Re: [sipcore] #2: Editorial: section 2 is really confusingRe: [sipcore] #2: Editorial: section 2 is really confusing
Mary Barnes
2010-08-28
sipcore
/arch/msg/sipcore/Wel4yzdqWlR-dYQKBozIxRTcWas/
1356832
1616349
Re: [sipcore] #1: Editorial: section 3 is not an "Overview of Operations"Re: [sipcore] #1: Editorial: section 3 is not an "Overview of Operations"
Mary Barnes
2010-08-28
sipcore
/arch/msg/sipcore/HwEvdVx65OXZw2i0_opQHccixVM/
1356831
1616350
[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
[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
[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] REMINDER: Re: WGLC: draft-ietf-sipcore-rfc4244bisRe: [sipcore] REMINDER: Re: WGLC: draft-ietf-sipcore-rfc4244bis
Paul Kyzivat
2010-08-26
sipcore
/arch/msg/sipcore/iOvnD8OvW2X0qBPwTCDiSuHP-Is/
1356827
1616143
[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
[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
[sipcore] #2: Editorial: section 2 is really confusing[sipcore] #2: Editorial: section 2 is really confusing
sipcore issue tracker
2010-08-25
sipcore
/arch/msg/sipcore/vywu4SIOSaq4lHjXnIk6XFI18fM/
1356824
1616349
[sipcore] #1: Editorial: section 3 is not an "Overview of Operations"[sipcore] #1: Editorial: section 3 is not an "Overview of Operations"
sipcore issue tracker
2010-08-25
sipcore
/arch/msg/sipcore/78RU9AFZDZ7KCJDAJLU_mxXJ3lA/
1356823
1616350
Re: [sipcore] REMINDER: Re: WGLC: draft-ietf-sipcore-rfc4244bisRe: [sipcore] REMINDER: Re: WGLC: draft-ietf-sipcore-rfc4244bis
Mary Barnes
2010-08-25
sipcore
/arch/msg/sipcore/YRGpS6Z3zMSprkkzHLqx2sig-ug/
1356822
1616143
Re: [sipcore] REMINDER: Re: WGLC: draft-ietf-sipcore-rfc4244bisRe: [sipcore] REMINDER: Re: WGLC: draft-ietf-sipcore-rfc4244bis
Paul Kyzivat
2010-08-25
sipcore
/arch/msg/sipcore/xYqEQjs8GVlyp4YOJ-BCgtH-2CY/
1356821
1616143
Re: [sipcore] REMINDER: Re: WGLC: draft-ietf-sipcore-rfc4244bisRe: [sipcore] REMINDER: Re: WGLC: draft-ietf-sipcore-rfc4244bis
Mary Barnes
2010-08-25
sipcore
/arch/msg/sipcore/dMpuufaMmKknpwNJ3MArEODv_us/
1356820
1616143
Re: [sipcore] REMINDER: Re: WGLC: draft-ietf-sipcore-rfc4244bisRe: [sipcore] REMINDER: Re: WGLC: draft-ietf-sipcore-rfc4244bis
Mary Barnes
2010-08-25
sipcore
/arch/msg/sipcore/fWG3Oxg67CarJtEn-agHWqYZ2tw/
1356819
1616143
Re: [sipcore] REMINDER: Re: WGLC: draft-ietf-sipcore-rfc4244bisRe: [sipcore] REMINDER: Re: WGLC: draft-ietf-sipcore-rfc4244bis
Paul Kyzivat
2010-08-25
sipcore
/arch/msg/sipcore/1MJIZOBqwAExId3j8iqAJIvMga0/
1356818
1616143
[sipcore] REMINDER: Re: WGLC: draft-ietf-sipcore-rfc4244bis[sipcore] REMINDER: Re: WGLC: draft-ietf-sipcore-rfc4244bis
Adam Roach
2010-08-25
sipcore
/arch/msg/sipcore/HAuK33bLVD7nTa2qEhwkzQl6iQs/
1356817
1616143