rfc-editor | 1 Sep 03:04 2009

RFC 5616 on Streaming Internet Messaging Attachments


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5616

        Title:      Streaming Internet Messaging Attachments 
        Author:     N. Cook
        Status:     Informational
        Date:       August 2009
        Mailbox:    neil.cook <at> noware.co.uk
        Pages:      28
        Characters: 65579
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-lemonade-streaming-13.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5616.txt

This document describes a method for streaming multimedia attachments
received by a resource- and/or network-constrained device from an
IMAP server.  It allows such clients, which often have limits in
storage space and bandwidth, to play video and audio email content.

The document describes a profile for making use of the URLAUTH-
authorized IMAP URLs (RFC 5092), the Network Announcement SIP Media
Service (RFC 4240), and the Media Server Control Markup Language (RFC
5022).  This memo provides information for the Internet community.

This document is a product of the Enhancements to Internet email to support diverse service environments
(Continue reading)

rfc-editor | 1 Sep 03:04 2009

RFC 5640 on Load-Balancing for Mesh Softwires


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5640

        Title:      Load-Balancing for Mesh Softwires 
        Author:     C. Filsfils, P. Mohapatra,
                    C. Pignataro
        Status:     Standards Track
        Date:       August 2009
        Mailbox:    cfilsfil <at> cisco.com, 
                    pmohapat <at> cisco.com, 
                    cpignata <at> cisco.com
        Pages:      6
        Characters: 12250
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-softwire-lb-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5640.txt

Payloads transported over a Softwire mesh service (as defined by BGP
Encapsulation Subsequent Address Family Identifier (SAFI) information
exchange) often carry a number of identifiable, distinct flows.  It
can, in some circumstances, be desirable to distribute these flows
over the equal cost multiple paths (ECMPs) that exist in the packet
switched network.  Currently, the payload of a packet entering the
Softwire can only be interpreted by the ingress and egress routers.
Thus, the load-balancing decision of a core router is only based on
(Continue reading)

rfc-editor | 1 Sep 03:04 2009

RFC 5641 on Layer 2 Tunneling Protocol Version 3 (L2TPv3) Extended Circuit Status Values


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5641

        Title:      Layer 2 Tunneling Protocol Version 
                    3 (L2TPv3) Extended Circuit Status Values 
        Author:     N. McGill, C. Pignataro
        Status:     Standards Track
        Date:       August 2009
        Mailbox:    nmcgill <at> cisco.com, 
                    cpignata <at> cisco.com
        Pages:      11
        Characters: 23133
        Updates:    RFC3931, RFC4349, RFC4454, RFC4591, RFC4719

        I-D Tag:    draft-ietf-l2tpext-circuit-status-extensions-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5641.txt

This document defines additional Layer 2 Tunneling Protocol Version 3
(L2TPv3) bit values to be used within the "Circuit Status" Attribute
Value Pair (AVP) to communicate finer-grained error states for
Attachment Circuits (ACs) and pseudowires (PWs).  It also generalizes
the Active bit and deprecates the use of the New bit in the Circuit
Status AVP, updating RFC 3931, RFC 4349, RFC 4454, RFC 4591, and RFC
4719.  [STANDARDS TRACK]

This document is a product of the Layer Two Tunneling Protocol Extensions Working Group of the IETF.
(Continue reading)

rfc-editor | 1 Sep 03:05 2009

RFC 5643 on Management Information Base for OSPFv3


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5643

        Title:      Management Information Base for OSPFv3 
        Author:     D. Joyal, Ed.,
                    V. Manral, Ed.
        Status:     Standards Track
        Date:       August 2009
        Mailbox:    djoyal <at> nortel.com, 
                    vishwas <at> ipinfusion.com
        Pages:      95
        Characters: 192945
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ospf-ospfv3-mib-15.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5643.txt

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in IPv6-based internets.  In
particular, it defines objects for managing the Open Shortest Path
First (OSPF) Routing Protocol for IPv6, otherwise known as OSPF
version 3 (OSPFv3).  [STANDARDS TRACK]

This document is a product of the Open Shortest Path First IGP Working Group of the IETF.

This is now a Proposed Standard Protocol.
(Continue reading)

rfc-editor | 1 Sep 03:05 2009

RFC 5647 on AES Galois Counter Mode for the Secure Shell Transport Layer Protocol


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5647

        Title:      AES Galois Counter Mode for 
                    the Secure Shell Transport Layer Protocol 
        Author:     K. Igoe, J. Solinas
        Status:     Informational
        Date:       August 2009
        Mailbox:    kmigoe <at> nsa.gov, 
                    jasolin <at> orion.ncsc.mil
        Pages:      10
        Characters: 20990
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-igoe-secsh-aes-gcm-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5647.txt

Secure shell (SSH) is a secure remote-login protocol.  SSH
provides for algorithms that provide authentication, key agreement,
confidentiality, and data-integrity services.  The purpose of this
document is to show how the AES Galois Counter Mode can be used to
provide both confidentiality and data integrity to the SSH Transport
Layer Protocol.  This memo provides information for the Internet 
community.

INFORMATIONAL: This memo provides information for the Internet community.
(Continue reading)

rfc-editor | 1 Sep 03:05 2009

STD 69, RFC 5730 on Extensible Provisioning Protocol (EPP)


A new Request for Comments is now available in online RFC libraries.

        STD 69        
        RFC 5730

        Title:      Extensible Provisioning Protocol (EPP) 
        Author:     S. Hollenbeck
        Status:     Standards Track
        Date:       August 2009
        Mailbox:    shollenbeck <at> verisign.com
        Pages:      67
        Characters: 134464
        Obsoletes:  RFC4930
        See Also:   STD0069

        I-D Tag:    draft-hollenbeck-rfc4930bis-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5730.txt

This document describes an application-layer client-server protocol
for the provisioning and management of objects stored in a shared
central repository.  Specified in XML, the protocol defines generic
object management operations and an extensible framework that maps
protocol operations to objects.  This document includes a protocol
specification, an object mapping template, and an XML media type
registration.  This document obsoletes RFC 4930.  [STANDARDS TRACK]

This is now a Standard Protocol.

(Continue reading)

rfc-editor | 1 Sep 03:05 2009

STD 69, RFC 5731 on Extensible Provisioning Protocol (EPP) Domain Name Mapping


A new Request for Comments is now available in online RFC libraries.

        STD 69        
        RFC 5731

        Title:      Extensible Provisioning Protocol (EPP) Domain 
                    Name Mapping 
        Author:     S. Hollenbeck
        Status:     Standards Track
        Date:       August 2009
        Mailbox:    shollenbeck <at> verisign.com
        Pages:      44
        Characters: 87764
        Obsoletes:  RFC4931
        See Also:   STD0069

        I-D Tag:    draft-hollenbeck-rfc4931bis-01.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5731.txt

This document describes an Extensible Provisioning Protocol (EPP)
mapping for the provisioning and management of Internet domain names
stored in a shared central repository.  Specified in XML, the mapping
defines EPP command syntax and semantics as applied to domain names.
This document obsoletes RFC 4931.  [STANDARDS TRACK]

This is now a Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
(Continue reading)

rfc-editor | 1 Sep 03:06 2009

STD 69, RFC 5732 on Extensible Provisioning Protocol (EPP) Host Mapping


A new Request for Comments is now available in online RFC libraries.

        STD 69        
        RFC 5732

        Title:      Extensible Provisioning Protocol (EPP) Host 
                    Mapping 
        Author:     S. Hollenbeck
        Status:     Standards Track
        Date:       August 2009
        Mailbox:    shollenbeck <at> verisign.com
        Pages:      29
        Characters: 56219
        Obsoletes:  RFC4932
        See Also:   STD0069

        I-D Tag:    draft-hollenbeck-rfc4932bis-01.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5732.txt

This document describes an Extensible Provisioning Protocol (EPP)
mapping for the provisioning and management of Internet host names
stored in a shared central repository.  Specified in XML, the mapping
defines EPP command syntax and semantics as applied to host names.
This document obsoletes RFC 4932.  [STANDARDS TRACK]

This is now a Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
(Continue reading)

rfc-editor | 1 Sep 03:06 2009

RFC 69, RFC 5733 on Extensible Provisioning Protocol (EPP) Contact Mapping


A new Request for Comments is now available in online RFC libraries.

        RFC 69        
        RFC 5733

        Title:      Extensible Provisioning Protocol (EPP) Contact 
                    Mapping 
        Author:     S. Hollenbeck
        Status:     Standards Track
        Date:       August 2009
        Mailbox:    shollenbeck <at> verisign.com
        Pages:      41
        Characters: 80698
        Obsoletes:  RFC4933
        See Also:   RFC0069

        I-D Tag:    draft-hollenbeck-rfc4933bis-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5733.txt

This document describes an Extensible Provisioning Protocol (EPP)
mapping for the provisioning and management of individual or
organizational social information identifiers (known as "contacts")
stored in a shared central repository.  Specified in Extensible
Markup Language (XML), the mapping defines EPP command syntax and
semantics as applied to contacts.  This document obsoletes RFC 4933.  
[STANDARDS TRACK]

This is now a Standard Protocol.
(Continue reading)

rfc-editor | 1 Sep 03:06 2009

STD 69, RFC 5734 on Extensible Provisioning Protocol (EPP) Transport over TCP


A new Request for Comments is now available in online RFC libraries.

        STD 69        
        RFC 5734

        Title:      Extensible Provisioning Protocol (EPP) Transport 
                    over TCP 
        Author:     S. Hollenbeck
        Status:     Standards Track
        Date:       August 2009
        Mailbox:    shollenbeck <at> verisign.com
        Pages:      13
        Characters: 27887
        Obsoletes:  RFC4934
        See Also:   STD0069

        I-D Tag:    draft-hollenbeck-rfc4934bis-01.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5734.txt

This document describes how an Extensible Provisioning Protocol (EPP)
session is mapped onto a single Transmission Control Protocol (TCP)
connection.  This mapping requires use of the Transport Layer
Security (TLS) protocol to protect information exchanged between an
EPP client and an EPP server.  This document obsoletes RFC 4934. 
[STANDARDS TRACK]

This is now a Standard Protocol.

(Continue reading)


Gmane