Last Call: draft-ietf-6lowpan-routing-requirements (Problem Statement and Requirements for 6LoWPAN Routing) to Informational RFC
The IESG has received a request from the IPv6 over Low power WPAN WG (6lowpan) to consider the following document: - 'Problem Statement and Requirements for 6LoWPAN Routing ' draft-ietf-6lowpan-routing-requirements-06.txt as an Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the i...@ietf.org mailing lists by 2010-05-13. Exceptionally, comments may be sent to i...@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-6lowpan-routing-requirements-06.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_iddTag=18009rfc_flag=0 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Document Action: 'VoIP SIP Peering Use Cases' to Informational RFC
The IESG has approved the following document: - 'VoIP SIP Peering Use Cases ' draft-ietf-speermint-voip-consolidated-usecases-18.txt as an Informational RFC This document is the product of the Session PEERing for Multimedia INTerconnect Working Group. The IESG contact persons are Gonzalo Camarillo and Robert Sparks. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-speermint-voip-consolidated-usecases-18.txt Technical Summary This document attempts to capture Voice over IP (VoIP) use cases for SIP peering. These use cases will assist in identifying requirements and other issues to be considered for future work in the working group. This informational document is intended to support the development of session peering requirements, architecture, and the message flows. Working Group Summary There is consensus in the WG to publish this document. Several Working Group Last Calls have been issued, and we have finally achieved consensus and resolved all concerns. All changes suggested by the WG have been made to this draft. A NITS review has also been performed by our secretary, and those changes made as well. Document Quality Good quality - no issues Personnel Document Shepherd: Daryl Malas Responsible AD: Gonzalo Camarillo IANA Experts Required: No ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Last Call: rfc4049 (BinaryTime: An alternate format for representing date and time in ASN.1) to Proposed Standard
The IESG has received a request from an individual submitter to consider the following document: - 'BinaryTime: An alternate format for representing date and time in ASN.1 ' RFC 4049 as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the i...@ietf.org mailing lists by 2010-05-27. Exceptionally, comments may be sent to i...@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/rfc/rfc4049.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_iddTag=4049rfc_flag=1 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 5245 on Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols
A new Request for Comments is now available in online RFC libraries. RFC 5245 Title: Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols Author: J. Rosenberg Status: Standards Track Stream: IETF Date: April 2010 Mailbox:jdro...@jdrosen.net Pages: 117 Characters: 285120 Obsoletes: RFC4091, RFC4092 I-D Tag:draft-ietf-mmusic-ice-19.txt URL:http://www.rfc-editor.org/rfc/rfc5245.txt This document describes a protocol for Network Address Translator (NAT) traversal for UDP-based multimedia sessions established with the offer/answer model. This protocol is called Interactive Connectivity Establishment (ICE). ICE makes use of the Session Traversal Utilities for NAT (STUN) protocol and its extension, Traversal Using Relay NAT (TURN). ICE can be used by any protocol utilizing the offer/answer model, such as the Session Initiation Protocol (SIP). [STANDARDS TRACK] This document is a product of the Multiparty Multimedia Session Control Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 5761 on Multiplexing RTP Data and Control Packets on a Single Port
A new Request for Comments is now available in online RFC libraries. RFC 5761 Title: Multiplexing RTP Data and Control Packets on a Single Port Author: C. Perkins, M. Westerlund Status: Standards Track Stream: IETF Date: April 2010 Mailbox:c...@csperkins.org, magnus.westerl...@ericsson.com Pages: 13 Characters: 31778 Updates:RFC3550, RFC3551 I-D Tag:draft-ietf-avt-rtp-and-rtcp-mux-07.txt URL:http://www.rfc-editor.org/rfc/rfc5761.txt This memo discusses issues that arise when multiplexing RTP data packets and RTP Control Protocol (RTCP) packets on a single UDP port. It updates RFC 3550 and RFC 3551 to describe when such multiplexing is and is not appropriate, and it explains how the Session Description Protocol (SDP) can be used to signal multiplexed sessions. [STANDARDS TRACK] This document is a product of the Audio/Video Transport Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 5762 on RTP and the Datagram Congestion Control Protocol (DCCP)
A new Request for Comments is now available in online RFC libraries. RFC 5762 Title: RTP and the Datagram Congestion Control Protocol (DCCP) Author: C. Perkins Status: Standards Track Stream: IETF Date: April 2010 Mailbox:c...@csperkins.org Pages: 16 Characters: 37537 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-dccp-rtp-07.txt URL:http://www.rfc-editor.org/rfc/rfc5762.txt The Real-time Transport Protocol (RTP) is a widely used transport for real-time multimedia on IP networks. The Datagram Congestion Control Protocol (DCCP) is a transport protocol that provides desirable services for real-time applications. This memo specifies a mapping of RTP onto DCCP, along with associated signalling, such that real- time applications can make use of the services provided by DCCP. [STANDARDS TRACK] This document is a product of the Datagram Congestion Control Protocol Working Group of the IETF. STANDARDS TRACK: 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 5767 on User-Agent-Driven Privacy Mechanism for SIP
A new Request for Comments is now available in online RFC libraries. RFC 5767 Title: User-Agent-Driven Privacy Mechanism for SIP Author: M. Munakata, S. Schubert, T. Ohba Status: Informational Stream: IETF Date: April 2010 Mailbox:munakata.may...@lab.ntt.co.jp, sh...@ntt-at.com, ohba.tak...@lab.ntt.co.jp Pages: 11 Characters: 23270 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-sip-ua-privacy-08.txt URL:http://www.rfc-editor.org/rfc/rfc5767.txt This document defines a guideline for a User Agent (UA) to generate an anonymous Session Initiation Protocol (SIP) message by utilizing mechanisms such as Globally Routable User Agent URIs (GRUUs) and Traversal Using Relays around NAT (TURN) without the need for a privacy service defined in RFC 3323. This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Session Initiation Protocol Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 5768 on Indicating Support for Interactive Connectivity Establishment (ICE) in the Session Initiation Protocol (SIP)
A new Request for Comments is now available in online RFC libraries. RFC 5768 Title: Indicating Support for Interactive Connectivity Establishment (ICE) in the Session Initiation Protocol (SIP) Author: J. Rosenberg Status: Standards Track Stream: IETF Date: April 2010 Mailbox:jdro...@jdrosen.net Pages: 6 Characters: 12962 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-sip-ice-option-tag-02.txt URL:http://www.rfc-editor.org/rfc/rfc5768.txt This specification defines a media feature tag and an option tag for use with the Session Initiation Protocol (SIP). The media feature tag allows a User Agent (UA) to communicate to its registrar that it supports ICE. The option tag allows a UA to require support for ICE in order for a call to proceed. [STANDARDS TRACK] This document is a product of the Session Initiation Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 5769 on Test Vectors for Session Traversal Utilities for NAT (STUN)
A new Request for Comments is now available in online RFC libraries. RFC 5769 Title: Test Vectors for Session Traversal Utilities for NAT (STUN) Author: R. Denis-Courmont Status: Informational Stream: IETF Date: April 2010 Mailbox:remi.denis-courm...@nokia.com Pages: 11 Characters: 15407 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-behave-stun-test-vectors-04.txt URL:http://www.rfc-editor.org/rfc/rfc5769.txt The Session Traversal Utilities for NAT (STUN) protocol defines several STUN attributes. The content of some of these -- FINGERPRINT, MESSAGE-INTEGRITY, and XOR-MAPPED-ADDRESS -- involve binary-logical operations (hashing, xor). This document provides test vectors for those attributes. This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Behavior Engineering for Hindrance Avoidance Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 5853 on Requirements from Session Initiation Protocol (SIP) Session Border Control (SBC) Deployments
A new Request for Comments is now available in online RFC libraries. RFC 5853 Title: Requirements from Session Initiation Protocol (SIP) Session Border Control (SBC) Deployments Author: J. Hautakorpi, Ed., G. Camarillo, R. Penfield, A. Hawrylyshen, M. Bhatia Status: Informational Stream: IETF Date: April 2010 Mailbox:jani.hautako...@ericsson.com, gonzalo.camari...@ericsson.com, bpenfi...@acmepacket.com, alan.i...@polyphase.ca, mbha...@3clogic.com Pages: 26 Characters: 60476 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-sipping-sbc-funcs-09.txt URL:http://www.rfc-editor.org/rfc/rfc5853.txt This document describes functions implemented in Session Initiation Protocol (SIP) intermediaries known as Session Border Controllers (SBCs). The goal of this document is to describe the commonly provided functions of SBCs. A special focus is given to those practices that are viewed to be in conflict with SIP architectural principles. This document also explores the underlying requirements of network operators that have led to the use of these functions and practices in order to identify protocol requirements and determine whether those requirements are satisfied by existing specifications or if additional standards work is required. This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Session Initiation Proposal Investigation Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
