Last Call: draft-ietf-isis-wg-extlsp (Simplified Extension of LSP Space for IS-IS) to Proposed Standard
The IESG has received a request from the IS-IS for IP Internets WG (isis) to consider the following document: - 'Simplified Extension of LSP Space for IS-IS ' 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 [EMAIL PROTECTED] mailing lists by 2008-11-04. Exceptionally, comments may be sent to [EMAIL PROTECTED] 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-isis-wg-extlsp-03.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=14787&rfc_flag=0 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Last Call: draft-ietf-isis-hmac-sha (IS-IS Generic Cryptographic Authentication) to Proposed Standard
The IESG has received a request from the IS-IS for IP Internets WG (isis) to consider the following document: - 'IS-IS Generic Cryptographic Authentication ' 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 [EMAIL PROTECTED] mailing lists by 2008-11-04. Exceptionally, comments may be sent to [EMAIL PROTECTED] 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-isis-hmac-sha-05.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=15013&rfc_flag=0 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 5372 on Payload Format for JPEG 2000 Video: Extensions for Scalability and Main Header Recovery
A new Request for Comments is now available in online RFC libraries. RFC 5372 Title: Payload Format for JPEG 2000 Video: Extensions for Scalability and Main Header Recovery Author: A. Leung, S. Futemma, E. Itakura Status: Standards Track Date: October 2008 Mailbox:[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Pages: 26 Characters: 53150 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-avt-rtp-jpeg2000-beam-11.txt URL:http://www.rfc-editor.org/rfc/rfc5372.txt This memo describes extended uses for the payload header in "RTP Payload Format for JPEG 2000 Video Streams" as specified in RFC 5371, for better support of JPEG 2000 features such as scalability and main header recovery. This memo must be accompanied with a complete implementation of "RTP Payload Format for JPEG 2000 Video Streams". That document is a complete description of the payload header and signaling, this document only describes additional processing for the payload header. There is an additional media type and Session Description Protocol (SDP) marker signaling for implementations of this document. [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 [EMAIL PROTECTED] Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 5371 on RTP Payload Format for JPEG 2000 Video Streams
A new Request for Comments is now available in online RFC libraries. RFC 5371 Title: RTP Payload Format for JPEG 2000 Video Streams Author: S. Futemma, E. Itakura, A. Leung Status: Standards Track Date: October 2008 Mailbox:[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Pages: 31 Characters: 62655 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-avt-rtp-jpeg2000-20.txt URL:http://www.rfc-editor.org/rfc/rfc5371.txt This memo describes an RTP payload format for the ISO/IEC International Standard 15444-1 | ITU-T Rec. T.800, better known as JPEG 2000. JPEG 2000 features are considered in the design of this payload format. JPEG 2000 is a truly scalable compression technology allowing applications to encode once and decode many different ways. The JPEG 2000 video stream is formed by extending from a single image to a series of JPEG 2000 images. [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 [EMAIL PROTECTED] Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 5344 on Presence and Instant Messaging Peering Use Cases
A new Request for Comments is now available in online RFC libraries. RFC 5344 Title: Presence and Instant Messaging Peering Use Cases Author: A. Houri, E. Aoki, S. Parameswar Status: Informational Date: October 2008 Mailbox:[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Pages: 9 Characters: 18389 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-speermint-consolidated-presence-im-usecases-05.txt URL:http://www.rfc-editor.org/rfc/rfc5344.txt This document describes several use cases of peering of non-VoIP (Voice over IP) services between two or more Service Providers. These Service Providers create a peering relationship between themselves, thus enabling their users to collaborate with users on the other Service Provider network. The target of this document is to drive requirements for peering between domains that provide the non-VoIP based collaboration services with presence and, in particular, Instant Messaging (IM). This memo provides information for the Internet community. This document is a product of the Session PEERing for Multimedia INTerconnect 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 [EMAIL PROTECTED] Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 5254 on Requirements for Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3)
A new Request for Comments is now available in online RFC libraries. RFC 5254 Title: Requirements for Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3) Author: N. Bitar, Ed., M. Bocci, Ed., L. Martini, Ed. Status: Informational Date: October 2008 Mailbox:[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Pages: 27 Characters: 64584 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-pwe3-ms-pw-requirements-07.txt URL:http://www.rfc-editor.org/rfc/rfc5254.txt This document describes the necessary requirements to allow a service provider to extend the reach of pseudowires across multiple domains. These domains can be autonomous systems under one provider administrative control, IGP areas in one autonomous system, different autonomous systems under the administrative control of two or more service providers, or administratively established pseudowire domains. This memo provides information for the Internet community. This document is a product of the Pseudo Wire Emulation Edge to Edge 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 [EMAIL PROTECTED] Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Last Call: draft-housley-iesg-rfc3932bis (IESG Procedures for Handling of Independent and IRTF Stream Submissions) to BCP
The IESG has received a request from an individual submitter to consider the following document: - 'IESG Procedures for Handling of Independent and IRTF Stream Submissions ' as a BCP 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 [EMAIL PROTECTED] mailing lists by 2008-11-18. Exceptionally, comments may be sent to [EMAIL PROTECTED] instead. In either case, please retain the beginning of the Subject line to allow automated sorting. We would also like to draw your attention to two documents that are referenced normatively. The first one, RFC 4844, defines the current RFC streams, and it was felt that this RFC should be a normative reference despite its classification as Informational. The second reference, draft-iab-streams-headers-boilerplates, is a document that the IAB will shortly send for public review and eventual publication as an RFC. It is a companion document to draft-housley; the clear indication of the source of an RFC eliminates the need for a mandatory IESG note on all Independent Submission and IRTF Stream documents. The file can be obtained via http://www.ietf.org/internet-drafts/draft-housley-iesg-rfc3932bis-04.txt Differences to RFC 3932 can be found here: http://www.arkko.com/ietf/iesg/rfc3932bisdiff.html IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=17615&rfc_flag=0 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Last Call: draft-ietf-mip4-dsmipv4 (Dual Stack Mobile IPv4) to Proposed Standard
The IESG has received a request from the Mobility for IPv4 WG (mip4) to consider the following document: - 'Dual Stack Mobile IPv4 ' 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 [EMAIL PROTECTED] mailing lists by 2008-11-04. Exceptionally, comments may be sent to [EMAIL PROTECTED] 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-mip4-dsmipv4-07.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=15085&rfc_flag=0 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Call for Comments: On RFC Streams, Headers, and Boilerplates
Dear Colleagues, The IAB intends to publish the following document and invites any comments you might have: "On RFC Streams, Headers, and Boilerplates" draft-iab-streams-headers-boilerplates-03 [1] Abstract RFC documents contain a number of fixed elements such as the title page header, standard boilerplates and copyright/IPR statements. This document describes them and introduces some updates to reflect current usage and requirements of RFC publication. In particular, this updated structure is intended to communicate clearly the source of RFC creation and review. Note that with the clear indication of the source of an RFC eliminates the need for a mandatory IESG note on all Independent Submission and IRTF Stream documents disappears. The implications of this are addressed by 'IESG Procedures for Handling of Independent and IRTF Stream Submissions ' ([2]) which is in "IETF last call" currently. Please provide your feedback before November 14, 2008 For the IAB, --Olaf Kolkman [1] http://tools.ietf.org/id/draft-iab-streams-headers-boilerplates [2] http://tools.ietf.org/id/draft-housley-iesg-rfc3932bis ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
