<?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/62672"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/62671"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/62670"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/62669"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/62668"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/62667"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/62666"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/62665"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/62664"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/62663"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/62662"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/62661"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/62660"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/62659"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/62658"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/62657"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/62656"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/62655"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/62654"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.announce/62653"/>
      </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/62672">
    <title>I-D Action: draft-andrews-dns-no-response-issue-01.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/62672</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.


Title           : A Common Operational Problem in DNS Servers - Failure To Respond.
Author(s)       : M. Andrews
Filename        : draft-andrews-dns-no-response-issue-01.txt
Pages           : 7
Date            : 2013-05-21

Abstract:
   The DNS is a query / response protocol.  Failure to respond to
   queries causes both immediate operational problems and long term
   problems with protocol development.

   This document will identify a number of common classes of queries
   that some servers fail to respond too.  This document will also
   suggest procedures for TLD and other similar zone operators to apply
   to reduce / eliminate the problem.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-andrews-dns-no-response-issue

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-andrews-dns-no-response-issue-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-andrews-dns-no-response-issue-01


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

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2013-05-22T05:05:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/62671">
    <title>I-D Action: draft-ietf-alto-protocol-16.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/62671</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-Layer Traffic Optimization Working Group of the IETF.

Title           : ALTO Protocol
Author(s)       : Richard Alimi
                          Reinaldo Penno
                          Y. Richard Yang
Filename        : draft-ietf-alto-protocol-16.txt
Pages           : 80
Date            : 2013-05-21

Abstract:
   Applications using the Internet already have access to topology
   information of Internet Service Provider (ISP) networks.  For
   example, views to Internet routing tables at looking glass servers
   are available and can be practically downloaded to many application
   clients.  What is missing is knowledge of the underlying network
   topologies from the point of view of ISPs (henceforth referred as
   Providers).  In other words, what a Provider prefers in terms of
   traffic optimization -- and a way to distribute it.

   The Application-Layer Traffic Optimization (ALTO) Service provides
   network information (e.g., basic network location structure and
   preferences of network paths) with the goal of modifying network
   resource consumption patterns while maintaining or improving
   application performance.  The basic information of ALTO is based on
   abstract maps of a network.  These maps provide a simplified view,
   yet enough information about a network for applications to
   effectively utilize them.  Additional services are built on top of
   the maps.

   This document describes a protocol implementing the ALTO Service.
   Although the ALTO Service would primarily be provided by the network
   service providers (e.g., Internet service providers), content service
   providers and third parties could also operate an ALTO service.
   Applications that could use this service are those that have a choice
   to which end points to connect.  Examples of such applications are
   peer-to-peer (P2P) and content delivery networks.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-alto-protocol

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-alto-protocol-16

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-alto-protocol-16


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

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2013-05-22T01:20:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/62670">
    <title>NomCom 2012: Feedback Request - IAB</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/62670</link>
    <description>&lt;pre&gt;The IETF Nominating Committee (NomCom) is currently working to fill the
IAB mid-term vacancy created by the resignation of Spencer Dawkins. The
NomCom is requesting feedback from the community to help us fill this
position. However, the NomCom needs to move quickly to  fill this
vacancy. Therefore, to be useful, the NomCom would greatly appreciate
feedback received on or before Monday, June 3rd.

We appreciate the responses to our previous call for nominations. The
individuals we are currently considering for the IAB mid-term vacancy are:

&lt;/pre&gt;</description>
    <dc:creator>NomCom Chair</dc:creator>
    <dc:date>2013-05-22T00:34:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/62669">
    <title>I-D Action: draft-manral-mpls-rfc3811bis-02.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/62669</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.


Title           : Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management
Author(s)       : Vishwas Manral
                          Tina Tsou
                          Will (Shucheng) Liu
Filename        : draft-manral-mpls-rfc3811bis-02.txt
Pages           : 22
Date            : 2013-05-21

Abstract:
   This memo defines a Management Information Base (MIB) module which
   contains Textual Conventions to represent commonly used Multiprotocol
   Label Switching (MPLS) management information.  The intent is that
   these TEXTUAL CONVENTIONS (TCs) will be imported and used in MPLS
   related MIB modules that would otherwise define their own
   representations.

   This document obsoletes RFC3811 as it addresses the need to support
   IPv6 extended TunnelID's by defining a new TC-
   MplsNewExtendedTunnelID which suggests using IPv4 address of the
   ingress or egress LSR for the tunnel for an IPv6 network.  Changes
   from RFC3811 and the effect of the new TC to other related documents
   are summarized in Section 4 and 5, respectively.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-manral-mpls-rfc3811bis

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-manral-mpls-rfc3811bis-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-manral-mpls-rfc3811bis-02


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

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2013-05-21T19:30:10</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/62668">
    <title>Last Call: &lt;draft-ietf-mmusic-rfc2326bis-34.txt&gt; (Real Time StreamingProtocol 2.0 (RTSP)) to Proposed Standard</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/62668</link>
    <description>&lt;pre&gt;
The IESG has received a request from the Multiparty Multimedia Session
Control WG (mmusic) to consider the following document:
- 'Real Time Streaming Protocol 2.0 (RTSP)'
  &amp;lt;draft-ietf-mmusic-rfc2326bis-34.txt&amp;gt; as 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
ietf&amp;lt; at &amp;gt;ietf.org mailing lists by 2013-06-04. Exceptionally, comments may be
sent to iesg&amp;lt; at &amp;gt;ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This memorandum defines RTSP version 2.0 which obsoletes RTSP version
   1.0 defined in RFC 2326.

   The Real Time Streaming Protocol, or RTSP, is an application-level
   protocol for setup and control of the delivery of data with real-time
   properties.  RTSP provides an extensible framework to enable
   controlled, on-demand delivery of real-time data, such as audio and
   video.  Sources of data can include both live data feeds and stored
   clips.  This protocol is intended to control multiple data delivery
   sessions, provide a means for choosing delivery channels such as UDP,
   multicast UDP and TCP, and provide a means for choosing delivery
   mechanisms based upon RTP (RFC 3550).




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-mmusic-rfc2326bis/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-mmusic-rfc2326bis/ballot/


The following IPR Declarations may be related to this I-D:

   http://datatracker.ietf.org/ipr/2028/
   http://datatracker.ietf.org/ipr/1189/




&lt;/pre&gt;</description>
    <dc:creator>The IESG</dc:creator>
    <dc:date>2013-05-21T19:20:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/62667">
    <title>I-D Action: draft-hao-jpake-00.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/62667</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.


Title           : J-PAKE: Password Authenticated Key Exchange by Juggling
Author(s)       : Feng Hao
Filename        : draft-hao-jpake-00.txt
Pages           : 10
Date            : 2013-05-21

Abstract:
   This document specifies a Password Authenticated Key Exchange by
   Juggling (J-PAKE) protocol.  This protocol allows the establishment
   of a secure end-to-end communication channel between two remote
   parties over an insecure network solely based on a shared password,
   without requiring a Public Key Infrastructure (PKI) or any trusted
   third party.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-hao-jpake

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-hao-jpake-00


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

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2013-05-21T18:36:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/62666">
    <title>I-D Action: draft-turner-application-cms-media-type-01.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/62666</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.


Title           : The application/cms media type
Author(s)       : Sean Turner
                          Russell Housley
                          Jim Schaad
Filename        : draft-turner-application-cms-media-type-01.txt
Pages           : 8
Date            : 2013-05-21

Abstract:
   This document registers the application/cms media types for use with
   the corresponding CMS (Cryptographic Message Syntax) content types.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-turner-application-cms-media-type

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-turner-application-cms-media-type-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-turner-application-cms-media-type-01


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

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2013-05-21T18:31:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/62665">
    <title>I-D Action: draft-ietf-homenet-arch-08.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/62665</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 Home Networking Working Group of the IETF.

Title           : Home Networking Architecture for IPv6
Author(s)       : Tim Chown
                          Jari Arkko
                          Anders Brandt
                          Ole Troan
                          Jason Weil
Filename        : draft-ietf-homenet-arch-08.txt
Pages           : 47
Date            : 2013-05-21

Abstract:
   This text describes evolving networking technology within
   increasingly large residential home networks.  The goal of this
   document is to define a general architecture for IPv6-based home
   networking, describing the associated principles, considerations and
   requirements.  The text briefly highlights specific implications of
   the introduction of IPv6 for home networking, discusses the elements
   of the architecture, and suggests how standard IPv6 mechanisms and
   addressing can be employed in home networking.  The architecture
   describes the need for specific protocol extensions for certain
   additional functionality.  It is assumed that the IPv6 home network
   is not actively managed, and runs as an IPv6-only or dual-stack
   network.  There are no recommendations in this text for the IPv4 part
   of the network.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-homenet-arch

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-homenet-arch-08

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-arch-08


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

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2013-05-21T18:00:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/62664">
    <title>I-D Action: draft-hao-schnorr-00.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/62664</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.


Title           : Schnorr Signature: Non-interactive Zero Knowledge Proof for Discrete Logarithm
Author(s)       : Feng Hao
Filename        : draft-hao-schnorr-00.txt
Pages           : 11
Date            : 2013-05-21

Abstract:
   This document describes the Schnorr signature, a non-interactive
   variant of the three-pass Schnorr identification scheme.  The Schnorr
   signature allows one to prove the knowledge of a discrete logarithm
   without leaking its value.  It can serve as a useful building block
   for many cryptographic protocols to ensure the participants follow
   the protocol specification honestly.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-hao-schnorr

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-hao-schnorr-00


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

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2013-05-21T17:53:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/62663">
    <title>I-D Action: draft-cheng-behave-cgn-cfg-radius-ext-05.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/62663</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.


Title           : RADIUS Extensions for Port Set Configuration and Reporting
Author(s)       : Dean Cheng
                          Jouni Korhonen
                          Mohamed Boucadair
                          Senthil Sivakumar
Filename        : draft-cheng-behave-cgn-cfg-radius-ext-05.txt
Pages           : 23
Date            : 2013-05-21

Abstract:
   This document defines new RADIUS attributes that can be used by a
   device implementing port ranges to communicate with a RADIUS server
   to configure and/or report TCP/UDP port sets and ICMP identifiers
   mapping behavior for specific hosts.  This mechanism can be used in
   various deployment scenarios such as CGN, NAT64, Provider WiFi
   Gateway, etc.

   This document does not make any assumption about the deployment
   context.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-cheng-behave-cgn-cfg-radius-ext

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-cheng-behave-cgn-cfg-radius-ext-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-cheng-behave-cgn-cfg-radius-ext-05


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

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2013-05-21T17:22:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/62662">
    <title>I-D Action: draft-bormann-cbor-00.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/62662</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.


Title           : Concise Binary Object Representation (CBOR)
Author(s)       : Carsten Bormann
                          Paul Hoffman
Filename        : draft-bormann-cbor-00.txt
Pages           : 32
Date            : 2013-05-21

Abstract:
   The Concise Binary Object Representation (CBOR) is a data format
   whose design goals include the possibility of extremely small code
   size, fairly small message size, and extensibility without the need
   for version negotiation.  These design goals make it different from
   earlier binary serializations such as ASN.1 and MessagePack.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-bormann-cbor

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-bormann-cbor-00


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

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2013-05-21T17:06:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/62661">
    <title>I-D Action: draft-turner-application-cms-media-type-00.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/62661</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.


Title           : The application/cms media type
Author(s)       : Sean Turner
                          Russell Housley
                          Jim Schaad
Filename        : draft-turner-application-cms-media-type-00.txt
Pages           : 8
Date            : 2013-05-21

Abstract:
   This document registers the application/cms media types for use with
   the corresponding CMS (Cryptographic Message Syntax) content types.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-turner-application-cms-media-type

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-turner-application-cms-media-type-00


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

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2013-05-21T16:19:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/62660">
    <title>I-D Action: draft-dolmatov-gost34102012-00.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/62660</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.


Title           : GOST R 34.10-2012: Digital Signature Algorithm
Author(s)       : Vasily Dolmatov
                          Alexey Degtyarev
Filename        : draft-dolmatov-gost34102012-00.txt
Pages           : 22
Date            : 2013-05-21

Abstract:
   This document is intended to be a source of information about the
   Russian Federal standard for digital signatures (GOST R 34.10-2012),
   which is one of the Russian cryptographic standard algorithms (called
   GOST algorithms).  Recently, Russian cryptography is being used in
   Internet applications, and this document has been created as
   information for developers and users of GOST R 34.10-2012 for digital
   signature generation and verification.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-dolmatov-gost34102012

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-dolmatov-gost34102012-00


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

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2013-05-21T15:00:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/62659">
    <title>I-D Action: draft-yong-l3vpn-nvgre-vxlan-encap-01.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/62659</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.


Title           : NVGRE and VXLAN Encapsulation for L3VPN Extension
Author(s)       : Lucy Yong
                          Xiaohu Xu
Filename        : draft-yong-l3vpn-nvgre-vxlan-encap-01.txt
Pages           : 7
Date            : 2013-05-21

Abstract:
   This document specifies NVGRE and VXLAN encapsulation for L3VPN
   Extension. Both NVGRE and VXLAN are originally designed for L2
   overlay. The draft proposes the enhancement on both to allow L3
   overlay completely decoupled from the L2 overlay in terms of
   encoding schema and data processing.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-yong-l3vpn-nvgre-vxlan-encap

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-yong-l3vpn-nvgre-vxlan-encap-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-yong-l3vpn-nvgre-vxlan-encap-01


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

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2013-05-21T14:23:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/62658">
    <title>I-D ACTION:draft-wei-paws-database-discovery-01.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/62658</link>
    <description>&lt;pre&gt;A new Internet-Draft is available from the on-line Internet-Drafts directories.


    Title         : PAWS Database Discovery
    Author(s)     : X. Wei, et al
    Filename      : draft-wei-paws-database-discovery
    Pages         : 14 
    Date          : May 21, 2013 
    
   This document provides a Database Discovery mechanism for PAWS.  By
   this mechanism the master device gets the available WSDBs with which
   it should communicate as well as the regulatory domain information.
   The mechanism is based on the LoST protocol .


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-wei-paws-database-discovery-01.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
&lt;/pre&gt;</description>
    <dc:creator>Internet-Drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2013-05-21T14:03:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/62657">
    <title>Last Call: &lt;draft-ietf-mmusic-sdp-miscellaneous-caps-05.txt&gt;(Miscellaneous Capabilities Negotiation in the SessionDescription Protocol (SDP)) to Proposed Standard</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/62657</link>
    <description>&lt;pre&gt;
The IESG has received a request from the Multiparty Multimedia Session
Control WG (mmusic) to consider the following document:
- 'Miscellaneous Capabilities Negotiation in the Session Description
   Protocol (SDP)'
  &amp;lt;draft-ietf-mmusic-sdp-miscellaneous-caps-05.txt&amp;gt; as 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
ietf&amp;lt; at &amp;gt;ietf.org mailing lists by 2013-06-04. Exceptionally, comments may be
sent to iesg&amp;lt; at &amp;gt;ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   SDP has been extended with a capability negotiation mechanism
   framework that allows the endpoints to negotiate transport protocols
   and attributes.  This framework has been extended with a media
   capabilities negotiation mechanism that allows endpoints to negotiate
   additional media-related capabilities.  This negotiation is embedded
   into the widely-used SDP offer/answer procedures.

   This memo extends the SDP capability negotiation framework to allow
   endpoints to negotiate three additional SDP capabilities.  In
   particular, this memo provides a mechanism to negotiate bandwidth
   ('b=' line), connection data ('c=' line), and titles ('i=' line for
   each session or media).




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-miscellaneous-caps/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-miscellaneous-caps/ballot/


No IPR declarations have been submitted directly on this I-D.



&lt;/pre&gt;</description>
    <dc:creator>The IESG</dc:creator>
    <dc:date>2013-05-21T13:54:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/62656">
    <title>I-D Action: draft-zimmermann-tcpm-tcp-rfc4614bis-02.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/62656</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.


Title           : A Roadmap for Transmission Control Protocol (TCP) Specification Documents
Author(s)       : Martin Duke
                          Robert Braden
                          Wesley M. Eddy
                          Ethan Blanton
                          Alexander Zimmermann
Filename        : draft-zimmermann-tcpm-tcp-rfc4614bis-02.txt
Pages           : 48
Date            : 2013-05-21

Abstract:
   This document contains a "roadmap" to the Requests for Comments (RFC)
   documents relating to the Internet's Transmission Control Protocol
   (TCP).  This roadmap provides a brief summary of the documents
   defining TCP and various TCP extensions that have accumulated in the
   RFC series.  This serves as a guide and quick reference for both TCP
   implementers and other parties who desire information contained in
   the TCP-related RFCs.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-zimmermann-tcpm-tcp-rfc4614bis

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-zimmermann-tcpm-tcp-rfc4614bis-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-zimmermann-tcpm-tcp-rfc4614bis-02


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

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2013-05-21T09:46:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/62655">
    <title>I-D Action: draft-ietf-idr-ls-distribution-03.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/62655</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 Inter-Domain Routing Working Group of the IETF.

Title           : North-Bound Distribution of Link-State and TE Information using BGP
Author(s)       : Hannes Gredler
                          Jan Medved
                          Stefano Previdi
                          Adrian Farrel
                          Saikat Ray
Filename        : draft-ietf-idr-ls-distribution-03.txt
Pages           : 43
Date            : 2013-05-21

Abstract:
   In a number of environments, a component external to a network is
   called upon to perform computations based on the network topology and
   current state of the connections within the network, including
   traffic engineering information.  This is information typically
   distributed by IGP routing protocols within the network

   This document describes a mechanism by which links state and traffic
   engineering information can be collected from networks and shared
   with external components using the BGP routing protocol.  This is
   achieved using a new BGP Network Layer Reachability Information
   (NLRI) encoding format.  The mechanism is applicable to physical and
   virtual IGP links.  The mechanism described is subject to policy
   control.

   Applications of this technique include Application Layer Traffic
   Optimization (ALTO) servers, and Path Computation Elements (PCEs).



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-ls-distribution

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-idr-ls-distribution-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-idr-ls-distribution-03


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

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2013-05-21T09:41:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/62654">
    <title>I-D Action: draft-gredler-ospf-label-advertisement-03.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/62654</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.


Title           : Advertising MPLS labels in OSPF
Author(s)       : Hannes Gredler
                          Shane Amante
                          Tom Scholl
                          Luay Jalil
Filename        : draft-gredler-ospf-label-advertisement-03.txt
Pages           : 28
Date            : 2013-05-21

Abstract:
   Historically MPLS label distribution was driven by protocols like
   LDP, RSVP and LBGP.  All of those protocols are session oriented.  In
   order to obtain label binding for a given destination FEC from a
   given router one needs first to establish an LDP/RSVP/LBGP session
   with that router.

   Advertising MPLS labels in IGPs
   [I-D.gredler-rtgwg-igp-label-advertisement] describes several use
   cases where utilizing the flooding machinery of link-state protocols
   for MPLS label distribution allows to obtain the binding without
   requiring to establish an LDP/RSVP/LBGP session with that router.

   This document describes the protocol extension to distribute MPLS
   label bindings by the OSPFv2 and OSPFv3 protocol.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-gredler-ospf-label-advertisement

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-gredler-ospf-label-advertisement-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-gredler-ospf-label-advertisement-03


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

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2013-05-21T09:23:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/62653">
    <title>I-D Action: draft-gredler-isis-label-advertisement-03.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/62653</link>
    <description>&lt;pre&gt;
A New Internet-Draft is available from the on-line Internet-Drafts directories.


Title           : Advertising MPLS labels in IS-IS
Author(s)       : Hannes Gredler
                          Shane Amante
                          Tom Scholl
                          Luay Jalil
Filename        : draft-gredler-isis-label-advertisement-03.txt
Pages           : 25
Date            : 2013-05-21

Abstract:
   Historically MPLS label distribution was driven by protocols like
   LDP, RSVP and LBGP.  All of those protocols are session oriented.  In
   order to obtain a label binding for a given destination FEC from a
   given router one needs first to establish an LDP/RSVP/LBGP session
   with that router.

   Advertising MPLS labels in IGPs
   [I-D.gredler-rtgwg-igp-label-advertisement] describes several use
   cases where utilizing the flooding machinery of link-state protocols
   for MPLS label distribution allows to obtain the binding without
   requiring to establish an LDP/RSVP/LBGP session with that router.

   This document describes the protocol extension to distribute MPLS
   label bindings using the IS-IS protocol.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-gredler-isis-label-advertisement

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-gredler-isis-label-advertisement-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-gredler-isis-label-advertisement-03


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

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2013-05-21T09:23:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.announce/62652">
    <title>I-D Action: draft-ietf-idr-reserved-extended-communities-05.txt</title>
    <link>http://permalink.gmane.org/gmane.ietf.announce/62652</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 Inter-Domain Routing Working Group of the IETF.

Title           : Assigned BGP extended communities
Author(s)       : Bruno Decraene
                          Pierre Francois
Filename        : draft-ietf-idr-reserved-extended-communities-05.txt
Pages           : 6
Date            : 2013-05-21

Abstract:
   This document defines an IANA registry in order to assign non-
   transitive extended communities from.  These are similar to the
   existing well-known BGP communities defined in RFC 1997 but provide a
   control over inter-AS community advertisement as, per RFC RFC 4360,
   they are not transitive across Autonomous System boundaries.

   For that purpose, this document defines the use of the reserved
   Autonomous System number 0.65535 in the non-transitive generic four-
   octet AS specific extended community type.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-reserved-extended-communities

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-idr-reserved-extended-communities-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-idr-reserved-extended-communities-05


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

&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2013-05-21T08:42:48</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>
