Last Call: draft-ietf-rmt-pi-alc-revised (Asynchronous Layered Coding (ALC) Protocol Instantiation) to Proposed Standard
The IESG has received a request from the Reliable Multicast Transport WG (rmt) to consider the following document: - 'Asynchronous Layered Coding (ALC) Protocol Instantiation ' draft-ietf-rmt-pi-alc-revised-08.txt as a Proposed Standard This document has a normative reference to RFC 3738: Wave and Equation Based Rate Control (WEBRC) Building Block an Experimental RFC. Please consider the appropriateness of this downward reference. See RFC 3967 for additional information about this. 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 2009-09-22. 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-rmt-pi-alc-revised-08.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_iddTag=13396rfc_flag=0 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Document Action: 'Application of Ethernet Pseudowires to MPLS Transport Networks' to Informational RFC
The IESG has approved the following document: - 'Application of Ethernet Pseudowires to MPLS Transport Networks ' draft-ietf-pwe3-mpls-transport-04.txt as an Informational RFC This document is the product of the Pseudowire Emulation Edge to Edge Working Group. The IESG contact persons are Ralph Droms and Jari Arkko. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pwe3-mpls-transport-04.txt Technical Summary A requirement has been identified by the operator community for the transparent carriage of the MPLS(-TP) network of one party over the MPLS(-TP) network of another party. This document describes a method of satisfying this need using the existing PWE3 Ethernet pseudowire standard RFC4448. Working Group Summary The draft originated as a response to the work that was then going on in the ITU to apply MPLS to transport networks. It reflected a desire to illustrate how IETF defined pseudowires could be applied to the problem of packet transport. Since that time, the development of MPLS-TP has proceeded in the IETF in close cooperation with the ITU-T. This draft addresses a sub-set of the MPLS-TP requirements using a limited set of existing MPLS and Pseudowire functionality, as defined in the IETF, but is not intended as a comprehensive standard for MPLS-TP per-se. The draft was widely reviewed by participants in the IETF MPLS-TP effort, as well as the MPLS and PWE3 WGs. Document Quality There are no concerns about protocol quality. There are understood to be implementations of this protocol. Personnel Who is the Document Shepherd for this document? Who is the Responsible Area Director? If the document requires IANA experts(s), insert 'The IANA Expert(s) for the registries in this document are TO BE ADDED BY THE AD.' RFC Editor Note Please make the following two changes to draft-ietf-pwe3-mpls-transport-04.txt before publication. === Abstract OLD A requirement has been identified by the operator community for the transparent carriage of the MPLS(-TP) network of one party over the MPLS(-TP) network of another party. This document describes a method of satisfying this need using the existing PWE3 Ethernet pseudowire standard RFC4448. NEW Ethernet pseudowires are widely deployed to support packet transport of Ethernet services. These services in-turn provide transport for a variety of client networks e.g. IP and MPLS. This document uses procedures defined in the existing IETF specifications of Ethernet pseudowires carried over MPLS networks. Many of the requirements for the services provided by the mechanisms explained in this document, are also recognized by the MPLS transport profile (MPLS-TP) design effort formed jointly by the IETF and ITU-T. The solution described here does not address all of the MPLS-TP requirements, but it provides a viable form of packet transport service using tools that are already available. This document also serves as an indication that existing MPLS techniques form an appropriate basis for the design of a fully- featured packet transport solution addressing all of the requirements of MPLS-TP. === Section 1 OLD The operator community has identified the need for the transparent carriage of the MPLS(-TP) network of one party over the MPLS(-TP) network of another party [I-D.ietf-mpls-tp-requirements]. This document describes one mechanism to satisfy this requirement using existing IETF standards such as PWE3 Ethernet pseudowire standard [RFC4448] . The mechanism described here fulfills the MPLS-TP requirements for transparent carriage (MPLS-TP requirements 30 31) of the Ethernet data plane. The key purpose of this document is to demonstrate that there is an existing IETF mechanism with known implementations that satisfies the requirements posed by the operator community. It is recognised that it is possible to design a more efficient method of satisfying the requirements, and the IETF anticipates that improved solutions will be proposed in the future. NEW Ethernet pseudowires are widely deployed to support packet transport of Ethernet services. These services in-turn provide transport for a variety of client networks e.g. IP and MPLS. This document uses procedures defined in the existing IETF specifications of Ethernet pseudowires carried over MPLS networks. Many of the requirements for the services provided by the mechanisms explained in this document, are also recognized by the MPLS transport profile (MPLS-TP) design effort formed jointly by the IETF and ITU-T [I-D.ietf-mpls-tp-requirements]. For example, the ability to operate solely with netowrk management control, the ability to use Operations, Adminstration and Maintenance (OAM) that does not rely on IP forwarding, and the ability to provide light-weight proactive connection verification (CV) functionality. The
Last Call: draft-ietf-dime-diameter-cmd-iana (Updated IANA Considerations for Diameter Command Code Allocations) to Proposed Standard
The IESG has received a request from the Diameter Maintenance and Extensions WG (dime) to consider the following document: - 'Updated IANA Considerations for Diameter Command Code Allocations ' draft-ietf-dime-diameter-cmd-iana-01.txt 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 2009-09-22. 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-dime-diameter-cmd-iana-01.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_iddTag=18633rfc_flag=0 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Last Call: draft-ietf-dnsext-dnssec-rsasha256 (Use of SHA-2 algorithms with RSA in DNSKEY and RRSIG Resource Records for DNSSEC) to Proposed Standard
The IESG has received a request from the DNS Extensions WG (dnsext) to consider the following document: - 'Use of SHA-2 algorithms with RSA in DNSKEY and RRSIG Resource Records for DNSSEC ' draft-ietf-dnsext-dnssec-rsasha256-14.txt 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 2009-09-22. 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-dnsext-dnssec-rsasha256-14.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_iddTag=14237rfc_flag=0 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Last Call: draft-ietf-mipshop-pfmipv6 (Fast Handovers for Proxy Mobile IPv6) to Proposed Standard
The IESG has received a request from the Mobility for IP: Performance, Signaling and Handoff Optimization WG (mipshop) to consider the following document: - 'Fast Handovers for Proxy Mobile IPv6 ' draft-ietf-mipshop-pfmipv6-09.txt 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 2009-09-22. 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-mipshop-pfmipv6-09.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_iddTag=17914rfc_flag=0 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Last Call: draft-ietf-nfsv4-federated-fs-reqts (Requirements for Federated File Systems) to Informational RFC
The IESG has received a request from the Network File System Version 4 WG (nfsv4) to consider the following document: - 'Requirements for Federated File Systems ' draft-ietf-nfsv4-federated-fs-reqts-03.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 2009-09-22. 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-nfsv4-federated-fs-reqts-03.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_iddTag=17723rfc_flag=0 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
