<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.ietf.announce">
    <title>gmane.ietf.announce</title>
    <link>http://blog.gmane.org/gmane.ietf.announce</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/54615"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/54614"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/54613"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/54612"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/54611"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/54610"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/54609"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/54608"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/54607"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/54606"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/54605"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/54604"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/54603"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/54602"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/54601"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/54600"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/54599"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/54598"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/54597"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/54596"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/54615">
    <title>I-D Action: draft-ietf-mptcp-multiaddressed-08.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/54615</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multipath TCP Working Group of the IETF.

Title           : TCP Extensions for Multipath Operation with Multiple Addresses
Author(s)       : Alan Ford
                          Costin Raiciu
                          Mark Handley
                          Olivier Bonaventure
Filename        : draft-ietf-mptcp-multiaddressed-08.txt
Pages           : 62
Date            : 2012-05-25

   TCP/IP communication is currently restricted to a single path per
   connection, yet multiple paths often exist between peers.  The
   simultaneous use of these multiple paths for a TCP/IP session would
   improve resource usage within the network, and thus improve user
   experience through higher throughput and improved resilience to
   network failure.

   Multipath TCP provides the ability to simultaneously use multiple
   paths between peers.  This document presents a set of extensions to
   traditional TCP to support multipath operation.  The protocol offers
   the same type of service to applications as TCP (i.e. reliable
   bytestream), and provides the components necessary to establish and
   use multiple TCP flows across potentially disjoint paths.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mptcp-multiaddressed-08.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-mptcp-multiaddressed-08.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-mptcp-multiaddressed/

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-05-25T10:15:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/54614">
    <title>I-D Action: draft-georgiades-opsawg-intercar-oam-req-02.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/54614</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.

Title           : Inter-Carrier OAM Requirements
Author(s)       : Michael Georgiades
                          Filippo Cugini
                          David Berechya
                          Oscar Gonzalez
Filename        : draft-georgiades-opsawg-intercar-oam-req-02.txt
Pages           : 13
Date            : 2012-05-25

   This draft specifies requirements for inter-carrier OAM supporting
   end-to-end OAM functionality and mechanisms development in a multi-
   operator environment. It reviews the already proposed OAM
   requirements addressed in IETF [RFC5706, RFC5860], ITU-T [Y.1730],
   MEF [MEFOAM] and IEEE [IEEE1, IEEE2] which were mainly proposed on a
   per transport technology basis. This document specifies additional
   requirements for the inter-carrier OAM operations.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-georgiades-opsawg-intercar-oam-req-02.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-georgiades-opsawg-intercar-oam-req-02.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-georgiades-opsawg-intercar-oam-req/

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-05-25T08:11:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/54613">
    <title>I-D Action: draft-ietf-netmod-routing-cfg-03.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/54613</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the NETCONF Data Modeling Language Working Group of the IETF.

Title           : A YANG Data Model for Routing Configuration
Author(s)       : Ladislav Lhotka
Filename        : draft-ietf-netmod-routing-cfg-03.txt
Pages           : 62
Date            : 2012-05-25

   This document contains a specification of three YANG modules.
   Together they form the core routing data model which serves as a
   framework for configuring a routing subsystem.  It is therefore
   expected that this module will be augmented by additional YANG
   modules defining data models for individual routing protocols and
   other related functions.  The core routing data model provides common
   building blocks for such configurations - router instances, routes,
   routing tables, routing protocols and route filters.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-netmod-routing-cfg-03.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-netmod-routing-cfg-03.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-netmod-routing-cfg/

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-05-25T07:53:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/54612">
    <title>I-D Action: draft-ietf-appsawg-media-type-regs-10.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/54612</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Applications Area Working Group Working Group of the IETF.

Title           : Media Type Specifications and Registration Procedures
Author(s)       : Ned Freed
                          John C. Klensin
                          Tony Hansen
Filename        : draft-ietf-appsawg-media-type-regs-10.txt
Pages           : 32
Date            : 2012-05-24

   This document defines procedures for the specification and
   registration of media types for use in HTTP, MIME and other Internet
   protocols.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-appsawg-media-type-regs-10.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-appsawg-media-type-regs-10.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-appsawg-media-type-regs/

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-05-25T05:47:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/54611">
    <title>I-D Action: draft-bryan-ftp-range-06.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/54611</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.

Title           : File Transfer Protocol RANG Command for Octet Ranges
Author(s)       : Anthony Bryan
                          Tatsuhiro Tsujikawa
                          Daniel Stenberg
Filename        : draft-bryan-ftp-range-06.txt
Pages           : 12
Date            : 2012-05-24

   The File Transfer Protocol offers the REST command to designate a
   starting point for a transfer, but does not currently offer any
   method to specify an end point.  This document specifies a new FTP
   RANG command to be used by clients to designate a start and end point
   to permit restarts and repairs of interrupted data transfers in
   STREAM mode.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-bryan-ftp-range-06.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-bryan-ftp-range-06.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-bryan-ftp-range/

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-05-24T23:36:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/54610">
    <title>I-D Action: draft-haleplidis-forces-openflow-lib-00.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/54610</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.

Title           : Forwarding and Control Element Separation (ForCES) OpenFlow Model Library
Author(s)       : Evangelos Haleplidis
                          Omar Cherkaoui
                          Susan Hares
                          Weiming Wang
Filename        : draft-haleplidis-forces-openflow-lib-00.txt
Pages           : 92
Date            : 2012-05-24

   This document describes the OpenFlow switch in Logical Function
   Blocks (LFBs) used in the Forwarding and Control Element Separation
   (ForCES).  The LFB classes are defined according to the ForCES
   Forwading Element (FE) model and ForCES protocol specifications.  The
   library includes the descriptions of the OpenFlow LFBs and the XML
   definitions.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-haleplidis-forces-openflow-lib-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-haleplidis-forces-openflow-lib-00.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-haleplidis-forces-openflow-lib/

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-05-24T22:17:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/54609">
    <title>I-D Action: draft-dhillon-ccamp-super-channel-ospfte-ext-03.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/54609</link>
    <description>&lt;pre&gt;
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-03.txt
Pages           : 12
Date            : 2012-05-24

   This document specifies the extension to TELINK LSA of OSPF routing
   protocol [RFC4203] [3] in support of GMPLS [1] for flex-grid
   networks [2].




A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-dhillon-ccamp-super-channel-ospfte-ext-03.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-dhillon-ccamp-super-channel-ospfte-ext-03.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-dhillon-ccamp-super-channel-ospfte-ext/

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-05-24T21:41:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/54608">
    <title>Vancouver IETF Codesprint</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/54608</link>
    <description>&lt;pre&gt;Vancouver IETF Codesprint

When:  Saturday, 28 July 2012, starting at 9:30 AM

Where: IETF Hotel

What:  A bunch of hackers get together to work on code for the
    IETF.  All code will become part of the open source IETF tools.

Who:   Hopefully you can help

Many of the results of previous codesprint activities are being used every day by the IETF community.  Shortly before the Paris meeting, we transitioned to a new database schema.  It makes many tasks much easier.  Of course, the transition left some 'shim code' that should be cleaned up.  Please come to the codesprint and work to polish or improve existing tools, fix bugs, or make altogether new tools.  All efforts are appreciated and most welcome.

Steve Conte will be helping with advance planning.  Henrik Levkowetz will be coordinating the event in Vancouver.  You can find more information here:

   http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF84Sprint

If you are able to participate, please sign up on the wiki at:

   http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF84SprintSignUp

Please support the tools development effort,
  Russ


&lt;/pre&gt;</description>
    <dc:creator>IETF Chair</dc:creator>
    <dc:date>2012-05-24T19:38:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/54607">
    <title>I-D Action: draft-allman-tcpm-rto-consider-01.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/54607</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.

Title           : Retransmission Timeout Considerations
Author(s)       : Mark Allman
Filename        : draft-allman-tcpm-rto-consider-01.txt
Pages           : 6
Date            : 2012-05-24

    This document provides for high-level guidance for retransmission
    timeout schemes appropriate for general use in the Internet.

Terminology

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-allman-tcpm-rto-consider-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-allman-tcpm-rto-consider-01.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-allman-tcpm-rto-consider/

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-05-24T19:32:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/54606">
    <title>I-D Action: draft-ietf-abfab-arch-02.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/54606</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application Bridging for Federated Access Beyond web Working Group of the IETF.

Title           : Application Bridging for Federated Access Beyond Web (ABFAB) Architecture
Author(s)       : Josh Howlett
                          Sam Hartman
                          Hannes Tschofenig
                          Eliot Lear
                          Jim Schaad
Filename        : draft-ietf-abfab-arch-02.txt
Pages           : 40
Date            : 2012-05-24

   Over the last decade a substantial amount of work has occurred in the
   space of federated access management.  Most of this effort has
   focused on two use-cases: network and web-based access.  However, the
   solutions to these use-cases that have been proposed and deployed
   tend to have few common building blocks in common.

   This memo describes an architecture that makes use of extensions to
   the commonly used security mechanisms for both federated and non-
   federated access management, including the Remote Authentication Dial
   In User Service (RADIUS) and the Diameter protocol, the Generic
   Security Service (GSS), the GS2 family, the Extensible Authentication
   Protocol (EAP) and the Security Assertion Markup Language (SAML).
   The architecture addresses the problem of federated access management
   to primarily non-web-based services, in a manner that will scale to
   large numbers of identity providers, relying parties, and
   federations.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-abfab-arch-02.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-abfab-arch-02.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-abfab-arch/

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-05-24T18:07:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/54605">
    <title>I-D Action: draft-generic-v6ops-tunmtu-01.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/54605</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.

Title           : Generic Tunnel MTU Determination
Author(s)       : Fred L. Templin
Filename        : draft-generic-v6ops-tunmtu-01.txt
Pages           : 8
Date            : 2012-05-24

   The tunnel MTU for popular IP-in-IP tunneling mechanisms is currently
   recommended to be set to 1500 (or less) minus the length of the
   encapsulation headers when static MTU determination is used.  This is
   to avoid IP fragmentation within the tunnel, but requires the tunnel
   ingress to either fragment any IP packet larger than the MTU or drop
   the packet and return an ICMP Packet Too Big (PTB) message.  Concerns
   for operational issues with both IPv4 and IPv6 Path MTU Discovery
   point to the possibility of MTU-related black holes when a packet is
   dropped due to an MTU restriction.  Fortunately, the "Internet cell
   size" is 1500 bytes, i.e., the minimum MTU configured by the vast
   majority of links in the Internet.  We also note that these same
   considerations apply to the encapsulation of any combination of IP-
   within-IP protocol versions.  This document therefore presents a
   method to boost the tunnel MTU to larger values.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-generic-v6ops-tunmtu-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-generic-v6ops-tunmtu-01.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-generic-v6ops-tunmtu/

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-05-24T17:54:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/54604">
    <title>I-D Action: draft-vandesompel-memento-04.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/54604</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.

Title           : HTTP framework for time-based access to resource states -- Memento
Author(s)       : Herbert VandeSompel
                          Michael Nelson
                          Robert Sanderson
Filename        : draft-vandesompel-memento-04.txt
Pages           : 47
Date            : 2012-05-24

   The HTTP-based Memento framework bridges the present and past Web by
   interlinking current resources with resources that encapsulate their
   past.  It facilitates obtaining representations of prior states of a
   resource, available from archival resources in Web archives or
   version resources in content management systems, by leveraging the
   resource's URI and a preferred datetime.  To this end, the framework
   introduces datetime negotiation (a variation on content negotiation),
   and new Relation Types for the HTTP "Link" header aimed at
   interlinking resources with their archival/version resources.  It
   also introduces various discovery mechanisms that further support
   bridging the present and past Web.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-vandesompel-memento-04.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-vandesompel-memento-04.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-vandesompel-memento/

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-05-24T17:49:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/54603">
    <title>New Non-WG Mailing List: core-parameters -- CORE parameters review</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/54603</link>
    <description>&lt;pre&gt;
A new IETF non-working group email list has been created.

List address: core-parameters&amp;lt; at &amp;gt;ietf.org
Archive: http://www.ietf.org/mail-archive/web/core-parameters/
To subscribe: https://www.ietf.org/mailman/listinfo/core-parameters

Purpose: The list will serve as the discussion list for expert review
of registrations for CORE-related parameters.

For additional information, please contact the list administrators.

&lt;/pre&gt;</description>
    <dc:creator>IETF Secretariat</dc:creator>
    <dc:date>2012-05-24T15:12:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/54602">
    <title>I-D Action: draft-ietf-cdni-use-cases-06.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/54602</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Content Delivery Networks Interconnection Working Group of the IETF.

Title           : Use Cases for Content Delivery Network Interconnection
Author(s)       : Gilles Bertrand
                          Stephan Emile
                          Trevor Burbridge
                          Philip Eardley
                          Kevin J. Ma
                          Grant Watson
Filename        : draft-ietf-cdni-use-cases-06.txt
Pages           : 16
Date            : 2012-05-24

   Content Delivery Networks (CDNs) are commonly used for improving the
   End User experience of a content delivery service, at a reasonable
   cost.  This document focuses on use cases that correspond to
   identified industry needs and that are expected to be realized once
   open interfaces and protocols supporting interconnection of CDNs are
   specified and implemented.  The document can be used to guide the
   definition of the requirements to be supported by CDN Interconnection
   (CDNI) interfaces.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-cdni-use-cases-06.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-cdni-use-cases-06.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-cdni-use-cases/

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-05-24T14:06:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/54601">
    <title>I-D Action: draft-vandevelde-idr-remote-next-hop-00.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/54601</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.

Title           : BGP Remote-Next-Hop
Author(s)       : Gunter Van de Velde
                          Keyur Patel
Filename        : draft-vandevelde-idr-remote-next-hop-00.txt
Pages           : 8
Date            : 2012-05-24

   The BGP Remote-Next-Hop optional transitive attribute, provides an
   additional level of recursive route-lookup.  The BGP Remote-Next-Hop
   attribute can be used, both on the public Internet infrastructure and
   within public or private Autonomous Systems (AS).  The usage of BGP
   Remote-Next-Hop operates as ships-in-the-night and does not require
   any capability exchange for any BGP Session.  BGP Remote-Next-Hop is
   providing the distribution of one or more Location Identifiers
   assigned to a particular BGP prefix or an NLRI.  To secure the BGP
   prefix or NLRI entry BGP security mechanisms, either RPKI or other
   BGP mechanisms can be utilized.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-vandevelde-idr-remote-next-hop-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-vandevelde-idr-remote-next-hop-00.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-vandevelde-idr-remote-next-hop/

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-05-24T12:49:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/54600">
    <title>I-D Action: draft-ietf-abfab-gss-eap-07.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/54600</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application Bridging for Federated Access Beyond web Working Group of the IETF.

Title           : A GSS-API Mechanism for the Extensible Authentication Protocol
Author(s)       : Sam Hartman
                          Josh Howlett
Filename        : draft-ietf-abfab-gss-eap-07.txt
Pages           : 40
Date            : 2012-05-24

   This document defines protocols, procedures, and conventions to be
   employed by peers implementing the Generic Security Service
   Application Program Interface (GSS-API) when using the EAP mechanism.
   Through the GS2 family of mechanisms, these protocols also define how
   Simple Authentication and Security Layer (SASL, RFC 4422)
   applications use the Extensible Authentication Protocol.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-abfab-gss-eap-07.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-abfab-gss-eap-07.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-abfab-gss-eap/

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-05-24T11:54:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/54599">
    <title>I-D Action: draft-ietf-emu-chbind-16.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/54599</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the EAP Method Update Working Group of the IETF.

Title           : Channel Binding Support for EAP Methods
Author(s)       : Sam Hartman
                          T. Charles Clancy
                          Katrin Hoeper
Filename        : draft-ietf-emu-chbind-16.txt
Pages           : 33
Date            : 2012-05-24

   This document defines how to implement channel bindings for
   Extensible Authentication Protocol (EAP) methods to address the lying
   Network Access Service (NAS) as well as the lying provider problem.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-emu-chbind-16.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-emu-chbind-16.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-emu-chbind/

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-05-24T10:41:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/54598">
    <title>I-D Action: draft-ietf-behave-nat64-discovery-heuristic-09.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/54598</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Behavior Engineering for Hindrance Avoidance Working Group of the IETF.

Title           : Discovery of IPv6 Prefix Used for IPv6 Address Synthesis
Author(s)       : Teemu Savolainen
                          Jouni Korhonen
                          Dan Wing
Filename        : draft-ietf-behave-nat64-discovery-heuristic-09.txt
Pages           : 14
Date            : 2012-05-24

   This document describes a method for detecting presence of DNS64 and
   for learning IPv6 prefix used for protocol translation on an access
   network.  The method depends on existence of a well-known IPv4-only
   domain name "ipv4only.arpa".  The information learned enables nodes
   to perform local IPv6 address synthesis and to potentially avoid
   traversal through NAT64 on dual-stack accesses and multi-interface
   deployments.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-behave-nat64-discovery-heuristic-09.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-behave-nat64-discovery-heuristic-09.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-behave-nat64-discovery-heuristic/

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-05-24T10:13:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/54597">
    <title>I-D Action: draft-xu-mpls-in-udp-01.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/54597</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.

Title           : Encapsulating MPLS in UDP
Author(s)       : Xiaohu Xu
                          Marshall Eubanks
                          Lucy Yong
                          Nischal Sheth
                          Zhenbin Li
Filename        : draft-xu-mpls-in-udp-01.txt
Pages           : 8
Date            : 2012-05-24

   This document specifies one additional IP-based encapsulation
   technology for MPLS packets referred to as MPLS-in-UDP, which is
   intended to facilitate load-balancing the traffic of various MPLS
   applications such as MPLS-based L2VPN and L3VPN in the core of IP-
   enabled packet switch networks.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-xu-mpls-in-udp-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-xu-mpls-in-udp-01.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-xu-mpls-in-udp/

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-05-24T09:22:10</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/54596">
    <title>I-D Action: draft-zahariadis-roll-metrics-composition-03.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/54596</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.

Title           : Design Guidelines for Routing Metrics Composition in LLN
Author(s)       : Theodore Zahariadis
                          Panos Trakadas
Filename        : draft-zahariadis-roll-metrics-composition-03.txt
Pages           : 21
Date            : 2012-05-24

   This document specifies the guidelines for designing efficient
   composite routing metrics to be applied to the Routing for Low Power
   and Lossy Networks (RPL) routing protocol.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-zahariadis-roll-metrics-composition-03.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-zahariadis-roll-metrics-composition-03.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-zahariadis-roll-metrics-composition/

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-05-24T08:29:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/54595">
    <title>I-D Action: draft-bi-savi-problem-03.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/54595</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.

Title           : Problem Statement of SAVI Beyond the First Hop
Author(s)       : Jun Bi
                          Bingyang Liu
Filename        : draft-bi-savi-problem-03.txt
Pages           : 9
Date            : 2012-05-23

   IETF Source Address Validation Improvements (SAVI) working group is
   chartered for source address validation within the first hop from the
   end hosts, i.e. preventing a node from spoofing the IP source address
   of another node in the same IP link.  However, since SAVI requires
   the edge routers or switches to be upgraded, the deployment of SAVI
   will need a long time.  During this transition period, some
   techniques for source address validation beyond the first hop
   (SAVI-BF) may be needed to complement SAVI.  In the document, we
   analyze the problems of the current SAVI-BF technique, and discuss
   the directions we can explore to improve SAVI-BF.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-bi-savi-problem-03.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-bi-savi-problem-03.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-bi-savi-problem/

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-05-24T06:34:46</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.ietf.announce">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.ietf.announce</link>
  </textinput>
</rdf:RDF>

