Session Initiation Protocol (SIP) Public Switched Telephone Network (PSTN) Call Flows
RFC 3666
also known as BCP 76
Revision differences
Document history
Date | By | Action |
---|---|---|
2023-12-12
|
(System) | Imported membership of rfc3666 in bcp76 via sync to the rfc-index |
2023-12-12
|
(System) | No history of BCP76 is currently available in the datatracker before this point |
2020-01-21
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
2015-10-14
|
(System) | Notify list changed from , , to , |
2011-11-15
|
(System) | Posted related IPR disclosure: Hitachi, Ltd.'s Statement about IPR related to RFC 3666 |
2011-05-25
|
(System) | Posted related IPR disclosure: Hitachi, Ltd.'s Statement about IPR related to RFC 3666 |
2010-10-04
|
(System) | Posted related IPR disclosure: Hitachi, Ltd.'s Statement about IPR related to RFC 3666 |
2010-03-23
|
(System) | Posted related IPR disclosure: Hitachi, Ltd.'s Statement about IPR related to RFC 3666 |
2004-01-08
|
(System) | Last call text was added |
2004-01-08
|
Amy Vezza | State Changes to RFC Published from RFC Ed Queue by Amy Vezza |
2004-01-08
|
Amy Vezza | [Note]: 'Discuss comments regarding the normative status to be a BCP, need for an ENUM example in the PSTN call flows - revision was made … [Note]: 'Discuss comments regarding the normative status to be a BCP, need for an ENUM example in the PSTN call flows - revision was made and doc to return to IESG agenda.' added by Amy Vezza |
2004-01-05
|
(System) | RFC published |