Protocol Action: 'The tel URI for Telephone Numbers' to Proposed Standard
The IESG has approved the following document: - 'The tel URI for Telephone Numbers ' draft-ietf-iptel-rfc2806bis-09.txt as a Proposed Standard This document is the product of the IP Telephony Working Group. The IESG contact persons are Jon Peterson and Allison Mankin. Technical Summary This document defines a tel URI scheme for telephone numbers and thereby revises the original definition given in RFC2806. This revision eliminates all vestiges of dial string usage of the tel URI in favor of a model where a tel URI is always a globally unique identifier. It also clarifies the use of tel URIs as the user portion of SIP URIs. Working Group Summary The IPTEL working group supported this revision to RFC2806. Protocol Quality This document was reviewed for the IESG by Jon Peterson. RFC Editor Note: Section 3, 2nd paragraph: OLD: If the reserved characters +, ;, =, and ? are used as delimiters between components of the tel URI, they MUST NOT percent-encoded. NEW: If the reserved characters +, ;, =, and ? are used as delimiters between components of the tel URI, they MUST NOT be percent-encoded. ^^ ___ IETF-Announce mailing list [EMAIL PROTECTED] https://www1.ietf.org/mailman/listinfo/ietf-announce
Protocol Action: 'Session Timers in the Session Initiation Protocol (SIP)' to Proposed Standard
The IESG has approved the following document: - 'Session Timers in the Session Initiation Protocol (SIP) ' draft-ietf-sip-session-timer-15.txt as a Proposed Standard This document is the product of the Session Initiation Protocol Working Group. The IESG contact persons are Allison Mankin and Jon Peterson. Technical Summary This document defines an extension to the Session Initiation Protocol (SIP). This extension allows for a periodic refresh of SIP sessions through a re-INVITE or UPDATE request. The refresh allows both user agents and proxies to determine if the SIP session is still active (primarily to decide whether to clean up state associated with it). The extension defines two new header fields, Session-Expires, which conveys the lifetime of the session, and Min-SE, which conveys the minimum allowed value for the session timer. It advises for a usage of thirty minutes for the minimum at this time, and it recommends use of the session timer extension the sips URI (TLS is used for each hop) so that a hacker cannot lower the timer and minimum. Working Group Summary There was strong support for this document by the working group. The function is important to SIP because of stateful proxies and forking, it had been handled ad hoc. The draft was one of the earliest ones of the WG. It was delayed waiting for an extensive revision to comply with RFC 3261. Protocol Quality The draft had a thorough review on the working group mailing list. Some implementations are in development. It was reviewed for the IESG by Allison Mankin. ___ IETF-Announce mailing list [EMAIL PROTECTED] https://www1.ietf.org/mailman/listinfo/ietf-announce
RFC 3845 on DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format
A new Request for Comments is now available in online RFC libraries. RFC 3845 Title: DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format Author(s): J. Schlyter, Ed. Status: Standards Track Date: August 2004 Mailbox:[EMAIL PROTECTED] Pages: 7 Characters: 14793 Updates:3755, 2535 I-D Tag:draft-ietf-dnsext-nsec-rdata-06.txt URL:ftp://ftp.rfc-editor.org/in-notes/rfc3845.txt This document redefines the wire format of the Type Bit Map field in the DNS NextSECure (NSEC) resource record RDATA format to cover the full resource record (RR) type space. This document is a product of the DNS Extensions Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to [EMAIL PROTECTED] Requests to be added to or deleted from the RFC-DIST distribution list should be sent to [EMAIL PROTECTED] Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to [EMAIL PROTECTED] with the message body help: ways_to_get_rfcs. For example: To: [EMAIL PROTECTED] Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to [EMAIL PROTECTED] Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to [EMAIL PROTECTED] Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. ftp://ftp.isi.edu/in-notes/rfc3845.txt ___ IETF-Announce mailing list [EMAIL PROTECTED] https://www1.ietf.org/mailman/listinfo/ietf-announce
RFC 3860 on Common Profile for Instant Messaging (CPIM)
A new Request for Comments is now available in online RFC libraries. RFC 3860 Title: Common Profile for Instant Messaging (CPIM) Author(s): J. Peterson Status: Standards Track Date: August 2004 Mailbox:[EMAIL PROTECTED] Pages: 13 Characters: 26486 Updates/Obsoletes/SeeAlso:None I-D Tag:draft-ietf-impp-im-04.txt URL:ftp://ftp.rfc-editor.org/in-notes/rfc3860.txt At the time this document was written, numerous instant messaging protocols were in use, and little interoperability between services based on these protocols has been achieved. This specification defines common semantics and data formats for instant messaging to facilitate the creation of gateways between instant messaging services. This document is a product of the Instant Messaging and Presence Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to [EMAIL PROTECTED] Requests to be added to or deleted from the RFC-DIST distribution list should be sent to [EMAIL PROTECTED] Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to [EMAIL PROTECTED] with the message body help: ways_to_get_rfcs. For example: To: [EMAIL PROTECTED] Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to [EMAIL PROTECTED] Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to [EMAIL PROTECTED] Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. ftp://ftp.isi.edu/in-notes/rfc3860.txt ___ IETF-Announce mailing list [EMAIL PROTECTED] https://www1.ietf.org/mailman/listinfo/ietf-announce
RFC 3859 on Common Profile for Presence (CPP)
A new Request for Comments is now available in online RFC libraries. RFC 3859 Title: Common Profile for Presence (CPP) Author(s): J. Peterson Status: Standards Track Date: August 2004 Mailbox:[EMAIL PROTECTED] Pages: 15 Characters: 30537 Updates/Obsoletes/SeeAlso:None I-D Tag:draft-ietf-impp-pres-04.txt URL:ftp://ftp.rfc-editor.org/in-notes/rfc3859.txt At the time this document was written, numerous presence protocols were in use (largely as components of commercial instant messaging services), and little interoperability between services based on these protocols has been achieved. This specification defines common semantics and data formats for presence to facilitate the creation of gateways between presence services. This document is a product of the Instant Messaging and Presence Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to [EMAIL PROTECTED] Requests to be added to or deleted from the RFC-DIST distribution list should be sent to [EMAIL PROTECTED] Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to [EMAIL PROTECTED] with the message body help: ways_to_get_rfcs. For example: To: [EMAIL PROTECTED] Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to [EMAIL PROTECTED] Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to [EMAIL PROTECTED] Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. ftp://ftp.isi.edu/in-notes/rfc3859.txt ___ IETF-Announce mailing list [EMAIL PROTECTED] https://www1.ietf.org/mailman/listinfo/ietf-announce
RFC 3861 on Address Resolution for Instant Messaging and Presence
A new Request for Comments is now available in online RFC libraries. RFC 3861 Title: Address Resolution for Instant Messaging and Presence Author(s): J. Peterson Status: Standards Track Date: August 2004 Mailbox:[EMAIL PROTECTED] Pages: 8 Characters: 15764 Updates/Obsoletes/SeeAlso:None I-D Tag:draft-ietf-impp-srv-04.txt URL:ftp://ftp.rfc-editor.org/in-notes/rfc3861.txt Presence and instant messaging are defined in RFC 2778. The Common Profiles for Presence and Instant Messaging define two Universal Resource Identifier (URI) schemes: \'im' for INSTANT INBOXes and 'pres' for PRESENTITIES. This document provides guidance for locating the resources associated with URIs that employ these schemes. This document is a product of the Instant Messaging and Presence Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to [EMAIL PROTECTED] Requests to be added to or deleted from the RFC-DIST distribution list should be sent to [EMAIL PROTECTED] Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to [EMAIL PROTECTED] with the message body help: ways_to_get_rfcs. For example: To: [EMAIL PROTECTED] Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to [EMAIL PROTECTED] Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to [EMAIL PROTECTED] Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. ftp://ftp.isi.edu/in-notes/rfc3861.txt ___ IETF-Announce mailing list [EMAIL PROTECTED] https://www1.ietf.org/mailman/listinfo/ietf-announce
RFC 3862 on Common Presence and Instant Messaging (CPIM): Message Format
A new Request for Comments is now available in online RFC libraries. RFC 3862 Title: Common Presence and Instant Messaging (CPIM): Message Format Author(s): G. Klyne, D. Atkins Status: Standards Track Date: August 2004 Mailbox:[EMAIL PROTECTED], [EMAIL PROTECTED] Pages: 30 Characters: 56133 Updates/Obsoletes/SeeAlso:None I-D Tag:draft-ietf-impp-cpim-msgfmt-09.txt URL:ftp://ftp.rfc-editor.org/in-notes/rfc3862.txt This memo defines the MIME content type 'Message/CPIM', a message format for protocols that conform to the Common Profile for Instant Messaging (CPIM) specification. This document is a product of the Instant Messaging and Presence Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to [EMAIL PROTECTED] Requests to be added to or deleted from the RFC-DIST distribution list should be sent to [EMAIL PROTECTED] Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to [EMAIL PROTECTED] with the message body help: ways_to_get_rfcs. For example: To: [EMAIL PROTECTED] Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to [EMAIL PROTECTED] Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to [EMAIL PROTECTED] Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. ftp://ftp.isi.edu/in-notes/rfc3862.txt ___ IETF-Announce mailing list [EMAIL PROTECTED] https://www1.ietf.org/mailman/listinfo/ietf-announce
RFC 3863 on Presence Information Data Format (PIDF)
A new Request for Comments is now available in online RFC libraries. RFC 3863 Title: Presence Information Data Format (PIDF) Author(s): H. Sugano, S. Fujimoto, G. Klyne, A. Bateman, W. Carr, J. Peterson Status: Standards Track Date: August 2004 Mailbox:[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Pages: 28 Characters: 56956 Updates/Obsoletes/SeeAlso:None I-D Tag:draft-ietf-impp-cpim-pidf-08.txt URL:ftp://ftp.rfc-editor.org/in-notes/rfc3863.txt This memo specifies the Common Profile for Presence (CPP) Presence Information Data Format (PIDF) as a common presence data format for CPP-compliant Presence protocols, and also defines a new media type application/pidf+xml to represent the XML MIME entity for PIDF. This document is a product of the Instant Messaging and Presence Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to [EMAIL PROTECTED] Requests to be added to or deleted from the RFC-DIST distribution list should be sent to [EMAIL PROTECTED] Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to [EMAIL PROTECTED] with the message body help: ways_to_get_rfcs. For example: To: [EMAIL PROTECTED] Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to [EMAIL PROTECTED] Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to [EMAIL PROTECTED] Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. ftp://ftp.isi.edu/in-notes/rfc3863.txt ___ IETF-Announce mailing list [EMAIL PROTECTED] https://www1.ietf.org/mailman/listinfo/ietf-announce
