http://blog.gmane.org/gmane.ietf.announce hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.ietf.announce/62758 <pre> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF. Title : Definition of Managed Objects for the Optimized Link State Routing Protocol version 2 Author(s) : Ulrich Herberg Robert G. Cole Thomas Heide Clausen Filename : draft-ietf-manet-olsrv2-mib-09.txt Pages : 83 Date : 2013-05-25 Abstract: This document defines the Management Information Base (MIB) module for configuring and managing the Optimized Link State Routing protocol version 2 (OLSRv2). The OLSRv2-MIB module is structured into configuration information, state information, performance information, and notifications. This additional state and performance information is useful to troubleshoot problems and performance issues of the routing protocol. Two levels of compliance allow this MIB module to be deployed o</pre> internet-drafts< at >ietf.org 2013-05-25T21:54:02 http://comments.gmane.org/gmane.ietf.announce/62757 <pre> A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Object Identifier Registry for the Long-Term Archive and Notary Services (LTANS) Working Group Author(s) : Russ Housley Filename : draft-housley-ltans-oids-00.txt Pages : 7 Date : 2013-05-25 Abstract: When the Long-Term Archive and Notary Services (LTANS) Working Group was chartered, an object identifier arc was set aside for use by that working group. This document describes the object identifiers that were assigned, and it establishes IANA allocation policies for any future assignments within that arc. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-housley-ltans-oids There's also a htmlized version available at: http://tools.ietf.org/html/draft-housley-ltans-oids-00 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ </pre> internet-drafts< at >ietf.org 2013-05-25T21:23:35 http://comments.gmane.org/gmane.ietf.announce/62756 <pre> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Internet Area Working Group Working Group of the IETF. Title : Using the IPv6 Flow Label for Server Load Balancing Author(s) : Brian Carpenter Sheng Jiang Willy Tarreau Filename : draft-ietf-intarea-flow-label-balancing-01.txt Pages : 12 Date : 2013-05-25 Abstract: This document describes how the IPv6 flow label as currently specified can be used to enhance layer 3/4 load distribution and balancing for large server farms. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-intarea-flow-label-balancing There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-intarea-flow-label-balancing-01 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-intarea-flow-label-balancing-01</pre> internet-drafts< at >ietf.org 2013-05-25T20:05:55 http://comments.gmane.org/gmane.ietf.announce/62755 <pre> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IPv6 Maintenance Working Group of the IETF. Title : Significance of IPv6 Interface Identifiers Author(s) : Brian Carpenter Sheng Jiang Filename : draft-ietf-6man-ug-01.txt Pages : 11 Date : 2013-05-24 Abstract: The IPv6 addressing architecture includes a unicast interface identifier that is used in the creation of many IPv6 addresses. Interface identifiers are formed by a variety of methods. This document clarifies that the bits in an interface identifier have no generic meaning and that the identifier should be treated as an opaque value. In particular, RFC 4291 defines a method by which the Universal and Group bits of an IEEE link-layer address are mapped into an IPv6 unicast interface identifier. This document clarifies that those bits apply only to interface identifiers that are derived</pre> internet-drafts< at >ietf.org 2013-05-25T04:23:55 http://comments.gmane.org/gmane.ietf.announce/62754 <pre> A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : PCP Considerations for WebRTC Usage Author(s) : Reinaldo Penno Tirumaleswar Reddy Dan Wing Mohamed Boucadair Filename : draft-penno-rtcweb-pcp-00.txt Pages : 16 Date : 2013-05-24 Abstract: This document describes the motivations for WebRTC applications to be PCP-aware and the benefits provided by PCP-capable NATs and Firewalls. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-penno-rtcweb-pcp There's also a htmlized version available at: http://tools.ietf.org/html/draft-penno-rtcweb-pcp-00 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ </pre> internet-drafts< at >ietf.org 2013-05-25T02:39:15 http://comments.gmane.org/gmane.ietf.announce/62753 <pre> A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : PCP Extension for Third Party Authorization Author(s) : Dan Wing Tirumaleswar Reddy Prashanth Patil Reinaldo Penno Filename : draft-wing-pcp-third-party-authz-00.txt Pages : 14 Date : 2013-05-24 Abstract: It is often desirable for an application server to permit a flow across a firewall, as happens today when a firewall includes an Application Layer Gateway (ALG) function. However, an ALG has several weaknesses. This document describes a cryptographic technique for an application server to permit a flow across a firewall. This technique uses OAuth and a new PCP option. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-wing-pcp-third-party-authz There's also a htmlized version available at: http://tools.ietf.org/html/draft-wing</pre> internet-drafts< at >ietf.org 2013-05-25T02:28:26 http://comments.gmane.org/gmane.ietf.announce/62752 <pre> A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : NVGRE Router Alert Option Author(s) : Kanwar Singh Pradeep Jain Florin Balus Wim Henderickx Filename : draft-singh-nvo3-nvgre-router-alert-00.txt Pages : 12 Date : 2013-05-24 Abstract: This proposal describes a new option to achieve a mechanism which alerts NVGRE egress End Point to more closely examine the contents of the packet encapsulated under NVGRE header. This option is useful for case(s) where a given frame encapsulated within a given NVGRE segment responsible for carrying data between two different End Systems contains some control information (e.g OAM information) that may require special handling/processing at NVGRE egress End Point. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-singh-nvo3-nvgre-router-alert There</pre> internet-drafts< at >ietf.org 2013-05-25T02:11:13 http://comments.gmane.org/gmane.ietf.announce/62751 <pre> A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : VxLAN Router Alert Option Author(s) : Kanwar Singh Pradeep Jain Florin Balus Wim Henderickx Filename : draft-singh-nvo3-vxlan-router-alert-00.txt Pages : 12 Date : 2013-05-24 Abstract: This proposal describes a new option to achieve a mechanism which alerts VxLAN terminating VTEP to more closely examine the contents of the packet encapsulated under VxLAN header. This option is useful for case(s) where a given frame encapsulated within a given VXLAN segment responsible for carrying data between two different End Systems contains some control information (e.g OAM information) that may require special handling/processing by terminating VTEP. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-singh-nvo3-vxlan-router-alert There's als</pre> internet-drafts< at >ietf.org 2013-05-25T02:07:30 http://comments.gmane.org/gmane.ietf.announce/62750 <pre> The IESG has received a request from the Path Computation Element WG (pce) to consider the following document: - 'Requirements for GMPLS applications of PCE' &lt;draft-ietf-pce-gmpls-aps-req-07.txt&gt; as 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 ietf&lt; at &gt;ietf.org mailing lists by 2013-06-07. Exceptionally, comments may be sent to iesg&lt; at &gt;ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract The initial effort of the PCE WG is specifically focused on MPLS (Multi-protocol label switching). As a next step, this draft describes functional requirements for GMPLS (Generalized MPLS) application of PCE (Path computation element). The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-pce-gmpls-aps-req/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-pce-gmpls-aps-req/ballot/ The f</pre> The IESG 2013-05-25T01:26:29 http://comments.gmane.org/gmane.ietf.announce/62749 <pre> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Open Shortest Path First IGP Working Group of the IETF. Title : Routing for IPv4-embedded IPv6 Packets Author(s) : Dean Cheng Mohamed Boucadair Alvaro Retana Filename : draft-ietf-ospf-ipv4-embedded-ipv6-routing-13.txt Pages : 16 Date : 2013-05-24 Abstract: This document describes a routing scenario where IPv4 packets are transported over an IPv6 network, based on RFCs 6145 and 6052, along with a separate OSPFv3 routing table for IPv4-embedded IPv6 routes in the IPv6 network. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-ospf-ipv4-embedded-ipv6-routing There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-ospf-ipv4-embedded-ipv6-routing-13 A diff from the previous version is available at: http://www.</pre> internet-drafts< at >ietf.org 2013-05-25T00:35:53 http://comments.gmane.org/gmane.ietf.announce/62748 <pre>A new Request for Comments is now available in online RFC libraries. RFC 6952 Title: Analysis of BGP, LDP, PCEP, and MSDP Issues According to the Keying and Authentication for Routing Protocols (KARP) Design Guide Author: M. Jethanandani, K. Patel, L. Zheng Status: Informational Stream: IETF Date: May 2013 Mailbox: mjethanandani&lt; at &gt;gmail.com, keyupate&lt; at &gt;cisco.com, vero.zheng&lt; at &gt;huawei.com Pages: 17 Characters: 37969 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-karp-routing-tcp-analysis-07.txt URL: http://www.rfc-editor.org/rfc/rfc6952.txt This document analyzes TCP-based routing protocols, the Border Gateway Protocol (BGP), the Label Distribution Protocol (LDP), the Path Computation Element Communication Protocol (PCEP), and the Multic</pre> rfc-editor< at >rfc-editor.org 2013-05-24T23:21:19 http://comments.gmane.org/gmane.ietf.announce/62747 <pre>A new Request for Comments is now available in online RFC libraries. RFC 6958 Title: RTP Control Protocol (RTCP) Extended Report (XR) Block for Burst/Gap Loss Metric Reporting Author: A. Clark, S. Zhang, J. Zhao, Q. Wu, Ed. Status: Standards Track Stream: IETF Date: May 2013 Mailbox: alan.d.clark&lt; at &gt;telchemy.com, zhangyx&lt; at &gt;sttri.com.cn, zhaojing&lt; at &gt;sttri.com.cn, sunseawq&lt; at &gt;huawei.com Pages: 16 Characters: 31057 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-xrblock-rtcp-xr-burst-gap-loss-12.txt URL: http://www.rfc-editor.org/rfc/rfc6958.txt This document defines an RTP Control Protocol (RTCP) Extended Report (XR) Block that allows the reporting of burst and gap loss metrics for use in a range of RTP applications. This document is a produc</pre> rfc-editor< at >rfc-editor.org 2013-05-24T23:21:05 http://comments.gmane.org/gmane.ietf.announce/62746 <pre> A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : OSPFTE extension to support GMPLS for Flex Grid Author(s) : Abinder Dhillon Iftekhar Hussain Rajan Rao Marco Sosa Filename : draft-dhillon-ccamp-super-channel-ospfte-ext-05.txt Pages : 12 Date : 2013-05-24 Abstract: This document specifies the extension to TELINK LSA of OSPF routing protocol [RFC4203] [3] in support of GMPLS [1] for flex-grid networks [2]. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-dhillon-ccamp-super-channel-ospfte-ext There's also a htmlized version available at: http://tools.ietf.org/html/draft-dhillon-ccamp-super-channel-ospfte-ext-05 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-dhillon-ccamp-super-channel-ospfte-ext-05 Internet-Drafts are also available by anonymou</pre> internet-drafts< at >ietf.org 2013-05-24T22:59:25 http://comments.gmane.org/gmane.ietf.announce/62745 <pre> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Web Authorization Protocol Working Group of the IETF. Title : OAuth 2.0 Dynamic Client Registration Protocol Author(s) : Justin Richer John Bradley Michael B. Jones Maciej Machulak Filename : draft-ietf-oauth-dyn-reg-11.txt Pages : 34 Date : 2013-05-24 Abstract: This specification defines an endpoint and protocol for dynamic registration of OAuth 2.0 Clients at an Authorization Server and methods for the dynamically registered client to manage its registration. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-oauth-dyn-reg There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-oauth-dyn-reg-11 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=dra</pre> internet-drafts< at >ietf.org 2013-05-24T20:36:38 http://comments.gmane.org/gmane.ietf.announce/62744 <pre>A new Request for Comments is now available in online RFC libraries. RFC 6933 Title: Entity MIB (Version 4) Author: A. Bierman, D. Romascanu, J. Quittek, M. Chandramouli Status: Standards Track Stream: IETF Date: May 2013 Mailbox: andy&lt; at &gt;yumaworks.com, dromasca&lt; at &gt;avaya.com, quittek&lt; at &gt;neclab.eu, moulchan&lt; at &gt;cisco.com Pages: 76 Characters: 165278 Obsoletes: RFC 4133 I-D Tag: draft-ietf-eman-rfc4133bis-06.txt URL: http://www.rfc-editor.org/rfc/rfc6933.txt This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing multiple logical and physical entities managed by a single Simple Network Management Protocol (SNMP) agent. This document specifies version</pre> rfc-editor< at >rfc-editor.org 2013-05-24T20:09:48 http://comments.gmane.org/gmane.ietf.announce/62743 <pre>A new Request for Comments is now available in online RFC libraries. BCP 183 RFC 6963 Title: A Uniform Resource Name (URN) Namespace for Examples Author: P. Saint-Andre Status: Best Current Practice Stream: IETF Date: May 2013 Mailbox: psaintan&lt; at &gt;cisco.com Pages: 7 Characters: 11749 See Also: BCP 183 I-D Tag: draft-saintandre-urn-example-05.txt URL: http://www.rfc-editor.org/rfc/rfc6963.txt This document defines a Uniform Resource Name (URN) namespace identifier enabling the generation of URNs that are appropriate for use in documentation and in URN-related testing and experimentation. BCP: This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-d</pre> rfc-editor< at >rfc-editor.org 2013-05-24T19:57:53 http://comments.gmane.org/gmane.ietf.announce/62742 <pre>The IESG has approved the following document: - 'A Framework for IP and MPLS Fast Reroute Using Not-via Addresses' (draft-ietf-rtgwg-ipfrr-notvia-addresses-11.txt) as Informational RFC This document is the product of the Routing Area Working Group. The IESG contact persons are Adrian Farrel and Stewart Bryant. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-rtgwg-ipfrr-notvia-addresses/ Technical Summary This document presents a framework for providing fast reroute in an IP or MPLS network through encapsulation and forwarding to "not-via" addresses. The general approach described uses a single level of encapsulation and could be used to protect unicast, multicast, and LDP traffic against link, router, and shared risk group failure, regardless of network topology and metrics. The mechanisms presented in this document are purely illustrative of the general approach and do not constitute a protocol specification. The document represents a snapsh</pre> The IESG 2013-05-24T19:11:26 http://comments.gmane.org/gmane.ietf.announce/62741 <pre>The IESG has approved the following document: - 'Framework for Loop-free convergence using oFIB' (draft-ietf-rtgwg-ordered-fib-12.txt) as Informational RFC This document is the product of the Routing Area Working Group. The IESG contact persons are Adrian Farrel and Stewart Bryant. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-rtgwg-ordered-fib/ Technical Summary This document describes the framework of a mechanism for use in conjunction with link state routing protocols which prevents the transient loops which would otherwise occur during topology changes. It does this by correctly sequencing the forwarding information base (FIB) updates on the routers. This mechanism can be used in the case of non-urgent link or node shutdowns and restarts or link metric changes. It can also be used in conjunction with a fast re-route mechanism which converts a sudden link or node failure into a non-urgent topology change. This is possible where a com</pre> The IESG 2013-05-24T19:08:48 http://comments.gmane.org/gmane.ietf.announce/62740 <pre> A new IETF non-working group email list has been created. List address: 6lo&lt; at &gt;ietf.org Archive: http://www.ietf.org/mail-archive/web/6lo/ To subscribe: https://www.ietf.org/mailman/listinfo/6lo Purpose: Since it was set up in 2005, the 6LoWPAN WG has created specifications for building IPv6 networks out of devices that use the IEEE 802.15.4 wireless network standard. This work has culminated in the recent publication of RFC 6775, 6LoWPAN-ND, and the 6LoWPAN WG is shutting down. This does not mean the work in this space is done. Indeed, 6LoWPAN produced one more document that isn't even about 802.15.4: draft-ietf-6lowpan-btle-12.txt, the equivalent of 6LoWPAN for the low energy mode of the Bluetooth 4.0 specification, is now in IESG processing, waiting for the assignment of a number from the Bluetooth SIG. A number of related drafts want to apply 6LoWPAN technology to other constrained node network layer 2 specifications: </pre> IETF Secretariat 2013-05-24T18:18:40 http://comments.gmane.org/gmane.ietf.announce/62739 <pre> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Routing Area Working Group Working Group of the IETF. Title : Framework for Loop-free convergence using oFIB Author(s) : Mike Shand Stewart Bryant Stefano Previdi Clarence Filsfils Pierre Francois Olivier Bonaventure Filename : draft-ietf-rtgwg-ordered-fib-12.txt Pages : 27 Date : 2013-05-24 Abstract: This document describes an illustrative framework of a mechanism for use in conjunction with link state routing protocols which prevents the transient loops which would otherwise occur during topology changes. It does this by correctly sequencing the forwarding information base (FIB) updates on the routers. This mechanism can be used in the case of non-urgent (management action) link or node shutdo</pre> internet-drafts< at >ietf.org 2013-05-24T17:35:49 http://comments.gmane.org/gmane.ietf.announce/62738 <pre> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Routing Area Working Group Working Group of the IETF. Title : Framework for Loop-free convergence using oFIB Author(s) : Mike Shand Stewart Bryant Stefano Previdi Clarence Filsfils Pierre Francois Olivier Bonaventure Filename : draft-ietf-rtgwg-ordered-fib-11.txt Pages : 26 Date : 2013-05-24 Abstract: This document describes an illustrative framework of a mechanism for use in conjunction with link state routing protocols which prevents the transient loops which would otherwise occur during topology changes. It does this by correctly sequencing the forwarding information base (FIB) updates on the routers. This mechanism can be used in the case of non-urgent (management action) link or node shutdo</pre> internet-drafts< at >ietf.org 2013-05-24T17:26:41 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.ietf.announce