Last Call: draft-ietf-softwire-bgp-te-attribute (BGP Traffic Engineering Attribute) to Proposed Standard
The IESG has received a request from the Softwires WG (softwire) to consider the following document: - 'BGP Traffic Engineering Attribute ' draft-ietf-softwire-bgp-te-attribute-03.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 [EMAIL PROTECTED] mailing lists by 2008-12-15. 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-softwire-bgp-te-attribute-03.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_iddTag=16874rfc_flag=0 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Last Call: draft-ietf-softwire-encaps-ipsec (BGP IPSec Tunnel Encapsulation Attribute) to Proposed Standard
The IESG has received a request from the Softwires WG (softwire) to consider the following document: - 'BGP IPSec Tunnel Encapsulation Attribute ' draft-ietf-softwire-encaps-ipsec-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 [EMAIL PROTECTED] mailing lists by 2008-12-15. 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-softwire-encaps-ipsec-01.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_iddTag=17131rfc_flag=0 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Last Call: draft-ietf-softwire-encaps-safi (BGP Encapsulation SAFI and BGP Tunnel Encapsulation Attribute) to Proposed Standard
The IESG has received a request from the Softwires WG (softwire) to consider the following document: - 'BGP Encapsulation SAFI and BGP Tunnel Encapsulation Attribute ' draft-ietf-softwire-encaps-safi-03.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 [EMAIL PROTECTED] mailing lists by 2008-12-15. 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-softwire-encaps-safi-03.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_iddTag=16879rfc_flag=0 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Last Call: draft-ietf-softwire-hs-framework-l2tpv2 (Softwire Hub Spoke Deployment Framework with L2TPv2) to Proposed Standard
The IESG has received a request from the Softwires WG (softwire) to consider the following document: - 'Softwire Hub Spoke Deployment Framework with L2TPv2 ' draft-ietf-softwire-hs-framework-l2tpv2-10.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 [EMAIL PROTECTED] mailing lists by 2008-12-15. 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-softwire-hs-framework-l2tpv2-10.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_iddTag=14882rfc_flag=0 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Last Call: draft-ietf-softwire-mesh-framework (Softwire Mesh Framework) to Proposed Standard
The IESG has received a request from the Softwires WG (softwire) to consider the following document: - 'Softwire Mesh Framework ' draft-ietf-softwire-mesh-framework-05.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 [EMAIL PROTECTED] mailing lists by 2008-12-15. 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-softwire-mesh-framework-05.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_iddTag=15920rfc_flag=0 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Last Call: draft-ietf-softwire-v4nlri-v6nh (Advertising an IPv4 NLRI with an IPv6 Next Hop) to Proposed Standard
The IESG has received a request from the Softwires WG (softwire) to consider the following document: - 'Advertising an IPv4 NLRI with an IPv6 Next Hop ' draft-ietf-softwire-v4nlri-v6nh-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 [EMAIL PROTECTED] mailing lists by 2008-12-15. 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-softwire-v4nlri-v6nh-01.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_iddTag=17135rfc_flag=0 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Protocol Action: 'Network Address Translation (NAT) Behavioral Requirements for the Datagram Congestion Control Protocol' to BCP
The IESG has approved the following document: - 'Network Address Translation (NAT) Behavioral Requirements for the Datagram Congestion Control Protocol ' draft-ietf-behave-dccp-05.txt as a BCP This document is the product of the Behavior Engineering for Hindrance Avoidance Working Group. The IESG contact persons are Magnus Westerlund and Lars Eggert. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-behave-dccp-05.txt Technical Summary This document defines a set of requirements for DCCP-capable NATs that would allow certain applications, such as streaming applications to operate consistently. Working Group Summary There is consensus in the working group to publish this document. Document Quality There are no known implementations. This was WG last called and reviewed by the DCCP WG. There are two normative reference to documents (draft-ietf-behave-nat-icmp and draft-ietf-dccp-simul-open) not yet published but that doesn't preclude progressing this document until it ends up in the RFC-editor's queue. ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Please comment on IAOC candidates for IAB selection
As described in BCP 101 (RFC 4071) and BCP 113 (RFC 4333), the IESG and the IAB each select one person for a two-year IAOC term in alternate years. This year, the IAB will select one person for a term beginning in March 2009. Following the call for nominations, which ran from 3 November 2008 through 26 November 2008, the IAB contacted each person that was nominated, asking them to accept or reject the nomination by 30 November 2008. At this point, three people have indicated a willingness to serve. They are: Bob Hinden Scott Bradner Henk Uijterwaal The IAB is actively soliciting confidential comments on these people and their ability to serve on the IAOC. The IAB needs to receive these comments by 6 January 2009 in order to make a selection on or before 15 January 2009. Please send comments to [EMAIL PROTECTED] Note that the NomCom will also be selecting a person to serve on the IAOC for a two year term. This process is orthogonal, the IAB is not privy to comments you might have submitted to the NomCom. On Behalf of the IAB, -- Olaf Kolkman ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Last Call: draft-arkko-arp-iana-rules (IANA Allocation Guidelines for the Address Resolution Protocol (ARP)) to Informational RFC
The IESG has received a request from an individual submitter to consider the following document: - 'IANA Allocation Guidelines for the Address Resolution Protocol (ARP)' draft-arkko-arp-iana-rules-05.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 [EMAIL PROTECTED] mailing lists by 2008-12-29. Exceptionally, comments may be sent to [EMAIL PROTECTED] instead. In either case, please retain the beginning of the Subject line to allow automated sorting. This is a second Last Call. The IESG would in particular like to draw your attention to the following two issues. Impact to specifications other than ARP: Earlier reviews and a search of the RFC series have uncovered a number of uses of the ARP values in other protocols, including specialized forms of ARP for certain link layers, DHCP, and one DNS Resource Record. The IANA rules for ARP will also affect the use of these numbers in these other protocols, and as a result the document updates several other RFCs. Downref notice: Two of the normative references are to Informational RFCs (RFC 1329 and RFC 2176). The normative reference was needed as this document updates the IANA rules relating to these RFCs. The file can be obtained via http://www.ietf.org/internet-drafts/draft-arkko-arp-iana-rules-04.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_iddTag=17805rfc_flag=0 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
