Re: [sipcore] Help with two SIP-related errataRe: [sipcore] Help with two SIP-related errata
R.Jesske
2023-08-08
sipcore
None
/arch/msg/sipcore/jiChJ3Ajk0qwdmw01L2PD_LQ98Q/
3340656
2077493
Re: [sipcore] Help with two SIP-related errataRe: [sipcore] Help with two SIP-related errata
Christer Holmberg
2023-08-08
sipcore
None
/arch/msg/sipcore/1omt4vwk-NmntnjRslAxdviHass/
3340650
2077493
Re: [sipcore] Help with two SIP-related errataRe: [sipcore] Help with two SIP-related errata
Christer Holmberg
2023-08-08
sipcore
None
/arch/msg/sipcore/NX7p9WpLQjjq4LD1Dy51goy6Pu8/
3340649
2077493
Re: [sipcore] Help with two SIP-related errataRe: [sipcore] Help with two SIP-related errata
Robert Sparks
2023-08-07
sipcore
None
/arch/msg/sipcore/eXD0fINN6qX73mC5r6V_x_hkAC0/
3340284
2077493
Re: [sipcore] Help with two SIP-related errataRe: [sipcore] Help with two SIP-related errata
Robert Sparks
2023-08-07
sipcore
None
/arch/msg/sipcore/f2TWFXMpsL165EZ1jahycUqisRU/
3340281
2077493
[sipcore] Help with two SIP-related errata[sipcore] Help with two SIP-related errata
Lars Eggert
2023-08-04
sipcore
None
/arch/msg/sipcore/Opl--znxofE0UlJ-E44EVs5zBmo/
3339091
2077493
Last Call: <draft-ietf-sipcore-name-addr-guidance-01.txt> (Clarifications for when to use the name-addr production in SIP messages) to Proposed StandardLast Call: <draft-ietf-sipcore-name-addr-guidance-01.txt> (Clarifications for when to use the name-addr production in SIP messages) to Proposed Standard
The IESG
2017-05-18
ietf-announce
None
/arch/msg/ietf-announce/Znc5xRgK0PIyRBAXgcDQ5Z5CME4/
2393782
1704587
[sipcore] Last Call: <draft-ietf-sipcore-name-addr-guidance-01.txt> (Clarifications for when to use the name-addr production in SIP messages) to Proposed Standard[sipcore] Last Call: <draft-ietf-sipcore-name-addr-guidance-01.txt> (Clarifications for when to use the name-addr production in SIP messages) to Proposed Standard
The IESG
2017-05-18
sipcore
None
/arch/msg/sipcore/zhIv_5k-4Ud8eZ6e9v2l-5qdZSo/
2393783
1704588
[sipcore] name-addr vs addr-spec requirements (was Re: [Technical Errata Reported] RFC5318 (4651))[sipcore] name-addr vs addr-spec requirements (was Re: [Technical Errata Reported] RFC5318 (4651))
Robert Sparks
2016-03-30
sipcore
None
/arch/msg/sipcore/OZN1Eey88Ksex8fia20fCZH_8qE/
2185676
1615630
Re: [sipcore] [Technical Errata Reported] RFC5318 (4651)Re: [sipcore] [Technical Errata Reported] RFC5318 (4651)
Ben Campbell
2016-03-30
sipcore
None
/arch/msg/sipcore/SUl7XOamfL3LGtl5BKEuenURZYY/
2185541
1615630
RFC 5318 on The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)RFC 5318 on The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)
rfc-editor
2008-12-08
ietf-announce
None
/arch/msg/ietf-announce/QTXxXEzqti0hdIjrS8YctlF6Iqc/
668038
1372857
[rfc-dist] RFC 5318 on The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)[rfc-dist] RFC 5318 on The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)
rfc-editor@rfc-editor.org
2008-12-08
rfc-dist
None
/arch/msg/rfc-dist/1VqWbieHH1z1E0DGDhYKV7BsPso/
2272243
1570878