headers
rfc-editor | 1 Feb 2008 01:32
Favicon

RFC 5110 on Overview of the Internet Multicast Routing Architecture


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

        
        RFC 5110

        Title:      Overview of the Internet Multicast 
                    Routing Architecture 
        Author:     P. Savola
        Status:     Informational
        Date:       January 2008
        Mailbox:    psavola <at> funet.fi
        Pages:      25
        Characters: 56217
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mboned-routingarch-12.txt

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

This document describes multicast routing architectures that are
currently deployed on the Internet.  This document briefly describes
those protocols and references their specifications.

This memo also reclassifies several older RFCs to Historic.  These
RFCs describe multicast routing protocols that were never widely
deployed or have fallen into disuse.  This memo provides information for the Internet community.

This document is a product of the MBONE Deployment
Working Group of the IETF.
(Continue reading)

Permalink | Reply | 0 comments |
headers
rfc-editor | 1 Feb 2008 02:23
Favicon

RFC 5116 on An Interface and Algorithms for Authenticated Encryption


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

        
        RFC 5116

        Title:      An Interface and Algorithms for 
                    Authenticated Encryption 
        Author:     D. McGrew
        Status:     Standards Track
        Date:       January 2008
        Mailbox:    mcgrew <at> cisco.com
        Pages:      22
        Characters: 50539
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-mcgrew-auth-enc-05.txt

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

This document defines algorithms for Authenticated Encryption with
Associated Data (AEAD), and defines a uniform interface and a
registry for such algorithms.  The interface and registry can be used
as an application-independent set of cryptoalgorithm suites.  This
approach provides advantages in efficiency and security, and promotes
the reuse of crypto implementations.  [STANDARDS TRACK]

This is now a Proposed Standard Protocol.

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

Permalink | Reply | 0 comments |
headers
rfc-editor | 1 Feb 2008 02:24
Favicon

STD 68, RFC 5234 on Augmented BNF for Syntax Specifications: ABNF


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

        STD 68        
        RFC 5234

        Title:      Augmented BNF for Syntax Specifications: 
                    ABNF 
        Author:     D. Crocker, Ed.,
                    P. Overell
        Status:     Standards Track
        Date:       January 2008
        Mailbox:    dcrocker <at> bbiw.net, 
                    paul.overell <at> thus.net
        Pages:      16
        Characters: 26359
        Obsoletes:  RFC4234
        See Also:   STD0068

        I-D Tag:    draft-crocker-rfc4234bis-01.txt

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

Internet technical specifications often need to define a formal
syntax.  Over the years, a modified version of Backus-Naur Form
(BNF), called Augmented BNF (ABNF), has been popular among many
Internet specifications.  The current specification documents ABNF.
It balances compactness and simplicity with reasonable
representational power.  The differences between standard BNF and
ABNF involve naming rules, repetition, alternatives,
(Continue reading)

Permalink | Reply | 1 comment |
headers
rfc-editor | 1 Feb 2008 02:24
Favicon

RFC 5101 on Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information


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

        
        RFC 5101

        Title:      Specification of the IP Flow 
                    Information Export (IPFIX) Protocol for the 
                    Exchange of IP Traffic Flow Information 
        Author:     B. Claise, Ed.
        Status:     Standards Track
        Date:       January 2008
        Mailbox:    bclaise <at> cisco.com
        Pages:      63
        Characters: 147196
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ipfix-protocol-26.txt

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

This document specifies the IP Flow Information Export (IPFIX)
protocol that serves for transmitting IP Traffic Flow information over
the network.  In order to transmit IP Traffic Flow information from an
Exporting Process to an information Collecting Process, a common
representation of flow data and a standard means of communicating them
is required.  This document describes how the IPFIX Data and Template
Records are carried over a number of transport protocols from an IPFIX
Exporting Process to an IPFIX Collecting Process.  [STANDARDS TRACK]
(Continue reading)

Permalink | Reply | 0 comments |
headers
rfc-editor | 1 Feb 2008 02:24
Favicon

RFC 5176 on Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS)


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

        
        RFC 5176

        Title:      Dynamic Authorization Extensions to Remote 
                    Authentication Dial In User Service (RADIUS) 
        Author:     M. Chiba, G. Dommety,
                    M. Eklund, D. Mitton,
                    B. Aboba
        Status:     Informational
        Date:       January 2008
        Mailbox:    mchiba <at> cisco.com, 
                    gdommety <at> cisco.com, 
                    meklund <at> cisco.com,  david <at> mitton.com, 
                    bernarda <at> microsoft.com
        Pages:      34
        Characters: 79541
        Obsoletes:  RFC3576
        See-Also:   

        I-D Tag:    draft-ietf-radext-rfc3576bis-13.txt

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

This document describes a currently deployed extension to the Remote
Authentication Dial In User Service (RADIUS) protocol, allowing
dynamic changes to a user session, as implemented by network access
server products.  This includes support for disconnecting users and
(Continue reading)

Permalink | Reply | 0 comments |
headers
rfc-editor | 1 Feb 2008 02:24
Favicon

RFC 5117 on RTP Topologies


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

        
        RFC 5117

        Title:      RTP Topologies 
        Author:     M. Westerlund, S. Wenger
        Status:     Informational
        Date:       January 2008
        Mailbox:    magnus.westerlund <at> ericsson.com, 
                    stewe <at> stewe.org
        Pages:      21
        Characters: 50293
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avt-topologies-07.txt

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

This document discusses multi-endpoint topologies used in Real-time
Transport Protocol (RTP)-based environments.  In particular,
centralized topologies commonly employed in the video conferencing
industry are mapped to the RTP terminology.  This memo provides 
information for the Internet community.

This document is a product of the Audio/Video Transport
Working Group of the IETF.

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

Permalink | Reply | 0 comments |
headers
rfc-editor | 1 Feb 2008 02:24
Favicon

RFC 5102 on Information Model for IP Flow Information Export


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

        
        RFC 5102

        Title:      Information Model for IP Flow 
                    Information Export 
        Author:     J. Quittek, S. Bryant,
                    B. Claise, P. Aitken,
                    J. Meyer
        Status:     Standards Track
        Date:       January 2008
        Mailbox:    quittek <at> netlab.nec.de, 
                    stbryant <at> cisco.com, 
                    bclaise <at> cisco.com,  paitken <at> cisco.com, 
                    jemeyer <at> paypal.com
        Pages:      171
        Characters: 335617
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ipfix-info-15.txt

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

This memo defines an information model for the IP Flow Information
eXport (IPFIX) protocol.  It is used by the IPFIX protocol for
encoding measured traffic information and information related to the
traffic Observation Point, the traffic Metering Process, and the
Exporting Process.  Although developed for the IPFIX protocol, the
(Continue reading)

Permalink | Reply | 0 comments |
headers
rfc-editor | 1 Feb 2008 02:24
Favicon

RFC 5103 on Bidirectional Flow Export Using IP Flow Information Export (IPFIX)


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

        
        RFC 5103

        Title:      Bidirectional Flow Export Using IP 
                    Flow Information Export (IPFIX) 
        Author:     B. Trammell, E. Boschi
        Status:     Standards Track
        Date:       January 2008
        Mailbox:    bht <at> cert.org, 
                    elisa.boschi <at> hitachi-eu.com
        Pages:      24
        Characters: 53534
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ipfix-biflow-05.txt

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

This document describes an efficient method for exporting
bidirectional flow (Biflow) information using the IP Flow Information
Export (IPFIX) protocol, representing each Biflow using a single Flow
Record.  [STANDARDS TRACK]

This document is a product of the IP Flow Information Export
Working Group of the IETF.

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

Permalink | Reply | 0 comments |
headers
IETF Administrative Director | 1 Feb 2008 03:07
Picon
Favicon

IT Transition

All IT services have been transitioned.  As previously reported,
please bear in mind that the AMS setup is not the same as the NSS
setup.  Some changes were necessary as part of the transition.  It
is possible there will be some issues that need attention as the
community begins to use the services in their new production
environment.

The good news is that all services, except jabber, are now available
on both IPv4 and IPv6.  This includes the web, ftp, email, and
rsync for those who mirror internet-drafts.

The status that you need to know is as follows.

1. Reminder, iab and iesg mailing lists have been moved to be in
   their respective domains.  This may affect your filtering but
   should not effect distribution.

2. As it turns out we did not move the irtf mailing lists into
   irtf.org.  In order to do this we need to be hosting the irtf.org
   web site for mailman to work properly.  Since this site is an
   independent site we have set this aside for now.

3. We have also noticed that GMail.com is blocking the IETF servers'
   email delivery.  They started this 5 minutes after email was
   enabled.  We have already filed the appropriate reports and hope
   for a resolution in 24-48 hours.  Please tell your friends on
   GMail.com that they are not getting IETF email.

4. Finally, site automation is not enabled at this time.  This means
   that "static" web pages or files that are automatically
(Continue reading)

Permalink | Reply | 1 comment |
headers
IESG Secretary | 1 Feb 2008 18:31
Picon
Favicon

WG Review: Cga & Send maIntenance (csi)

A new IETF working group has been proposed in the Internet Area.  
The IESG has not made any determination as yet.  The following 
draft charter was submitted, and is provided for informational 
purposes only.  Please send your comments to the IESG mailing 
list (iesg <at> ietf.org) by February 7, 2008.

Cga & Send maIntenance (csi)
============================
Current Status: Proposed Working Group

Chair(s):
TBD

Internet Area Area Director(s):
Jari Arkko <jari.arkko <at> piuha.net>
Mark Townsley <townsley <at> cisco.com>

Description:

Proposed charter for Cga & Send maIntenance (CSI) BOF

The Secure Neighbor Discovery (SEND) protocol defined by 
RFC 3971 provides security mechanisms protecting different 
functions of the Neighbor Discovery (ND) protocol defined 
by RFC 2461. This includes address resolution (discovering 
link layer address of another node attached to the link), 
router discovery (discovering routers attached to the link), 
and neighbor unreachability detection (detecting that a node 
attached to the link is no longer reachable). SEND protection 
of address resolution and neighbor unreachability detection
(Continue reading)

Permalink | Reply | 0 comments |

Gmane