headers
rfc-editor | 1 Mar 2007 06:08
Favicon

RFC 4855 on Media Type Registration of RTP Payload Formats


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

        
        RFC 4855

        Title:      Media Type Registration of RTP 
                    Payload Formats 
        Author:     S. Casner
        Status:     Standards Track
        Date:       February 2007
        Mailbox:    casner <at> acm.org
        Pages:      11
        Characters: 24404
        Obsoletes:  RFC3555
        See-Also:   

        I-D Tag:    draft-ietf-avt-rfc3555bis-05.txt

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

This document specifies the procedure to register RTP payload
formats as audio, video, or other media subtype names.  This is
useful in a text-based format description or control protocol to
identify the type of an RTP transmission.  [STANDARDS TRACK]

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

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

Permalink | Reply | 0 comments |
headers
rfc-editor | 1 Mar 2007 06:10
Favicon

RFC 4822 on RIPv2 Cryptographic Authentication


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

        
        RFC 4822

        Title:      RIPv2 Cryptographic Authentication 
        Author:     R. Atkinson, M. Fanto
        Status:     Standards Track
        Date:       February 2007
        Mailbox:    rja <at> extremenetworks.com, 
                    mattjf <at> umd.edu
        Pages:      22
        Characters: 53828

        I-D Tag:    draft-rja-ripv2-auth-06.txt

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

This note describes a revision to the RIPv2 Cryptographic
Authentication mechanism originally specified in RFC 2082.  This
document obsoletes RFC 2082 and updates RFC 2453.  This
document adds details of how the SHA family of hash algorithms can be
used with RIPv2 Cryptographic Authentication, whereas the original
document only specified the use of Keyed-MD5.  Also, this document
clarifies a potential issue with an active attack on this mechanism
and adds significant text to the Security Considerations section.  
[STANDARDS TRACK]

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

Permalink | Reply | 0 comments |
headers
rfc-editor | 1 Mar 2007 06:07
Favicon

RFC 4809 on Requirements for an IPsec Certificate Management Profile


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

        
        RFC 4809

        Title:      Requirements for an IPsec Certificate 
                    Management Profile 
        Author:     C. Bonatti, Ed.,
                    S. Turner, Ed.,
                    G. Lebovitz, Ed.
        Status:     Informational
        Date:       February 2007
        Mailbox:    Bonattic <at> ieca.com, 
                    Turners <at> ieca.com, 
                    gregory.ietf <at> gmail.com
        Pages:      45
        Characters: 98400
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pki4ipsec-mgmt-profile-rqts-07.txt

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

This informational document describes and identifies the requirements
for transactions to handle Public Key Certificate (PKC) lifecycle
transactions between Internet Protocol Security (IPsec) Virtual
Private Network (VPN) Systems using Internet Key Exchange (IKE)
(versions 1 and 2) and Public Key Infrastructure (PKI) Systems.  These
requirements are designed to meet the needs of enterprise-scale IPsec
(Continue reading)

Permalink | Reply | 0 comments |
headers
rfc-editor | 1 Mar 2007 06:08
Favicon

RFC 4803 on Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR) Management Information Base


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

        
        RFC 4803

        Title:      Generalized Multiprotocol Label Switching (GMPLS) 
                    Label Switching Router (LSR) Management Information 
                    Base 
        Author:     T. Nadeau, Ed., A. Farrel, Ed.
        Status:     Standards Track
        Date:       February 2007
        Mailbox:    tnadeau <at> cisco.com, 
                    adrian <at> olddog.co.uk
        Pages:      42
        Characters: 79925
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ccamp-gmpls-lsr-mib-15.txt

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

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects to configure and/or
monitor a Generalized Multiprotocol Label Switching (GMPLS) Label
Switching Router (LSR).  [STANDARDS TRACK]

This document is a product of the Common Control and Measurement Plane
Working Group of the IETF.
(Continue reading)

Permalink | Reply | 0 comments |
headers
rfc-editor | 1 Mar 2007 06:09
Favicon

RFC 4802 on Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base


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

        
        RFC 4802

        Title:      Generalized Multiprotocol Label Switching (GMPLS) 
                    Traffic Engineering Management Information Base 
        Author:     T. Nadeau, Ed., A. Farrel, Ed.
        Status:     Standards Track
        Date:       February 2007
        Mailbox:    tnadeau <at> cisco.com, 
                    adrian <at> olddog.co.uk
        Pages:      60
        Characters: 118164
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ccamp-gmpls-te-mib-16.txt

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

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects for Generalized
Multiprotocol Label Switching (GMPLS)-based traffic engineering.
[STANDARDS TRACK]

This document is a product of the Common Control and Measurement Plane
Working Group of the IETF.
(Continue reading)

Permalink | Reply | 0 comments |
headers
rfc-editor | 1 Mar 2007 06:08
Favicon

RFC 4856 on Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences


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

        
        RFC 4856

        Title:      Media Type Registration of Payload 
                    Formats in the RTP Profile for 
                    Audio and Video Conferences 
        Author:     S. Casner
        Status:     Standards Track
        Date:       February 2007
        Mailbox:    casner <at> acm.org
        Pages:      29
        Characters: 45881
        Obsoletes:  RFC3555
        See-Also:   

        I-D Tag:    draft-ietf-avt-rfc3555bis-part2-02.txt

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

This document specifies media type registrations for the RTP
payload formats defined in the RTP Profile for Audio and Video
Conferences.  Some of these may also be used for transfer modes
other than RTP.  [STANDARDS TRACK]

This document is a product of the Audio/Video Transport
Working Group of the IETF.
(Continue reading)

Permalink | Reply | 0 comments |
headers
rfc-editor | 1 Mar 2007 06:10
Favicon

RFC 4801 on Definitions of Textual Conventions for Generalized Multiprotocol Label Switching (GMPLS) Management


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

        
        RFC 4801

        Title:      Definitions of Textual Conventions for 
                    Generalized Multiprotocol Label Switching (GMPLS) 
                    Management 
        Author:     T. Nadeau, Ed.,
                    A. Farrel, Ed.
        Status:     Standards Track
        Date:       February 2007
        Mailbox:    tnadeau <at> cisco.com, 
                    adrian <at> olddog.co.uk
        Pages:      9
        Characters: 16347
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ccamp-gmpls-tc-mib-11.txt

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

This document defines a Management Information Base (MIB) module
that contains textual conventions (TCs) to represent commonly used
Generalized Multiprotocol Label Switching (GMPLS) management
information.  The intent is that these textual conventions will
be imported and used in GMPLS-related MIB modules that would
otherwise define their own representations.  [STANDARDS TRACK]
(Continue reading)

Permalink | Reply | 0 comments |
headers
The IESG | 1 Mar 2007 17:32
Picon
Favicon

Last Call: draft-ietf-behave-tcp (NAT Behavioral Requirements for TCP) to BCP

The IESG has received a request from the Behavior Engineering for 
Hindrance Avoidance WG (behave) to consider the following document:

- 'NAT Behavioral Requirements for TCP '
   <draft-ietf-behave-tcp-05.txt> as a BCP

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 <at> ietf.org mailing lists by 2007-03-15. Exceptionally, 
comments may be sent to iesg <at> ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-behave-tcp-05.txt

IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=14296&rfc_flag=0

_______________________________________________
IETF-Announce mailing list
IETF-Announce <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce
Permalink | Reply | 0 comments |
headers
The IESG | 1 Mar 2007 17:36
Picon
Favicon

Last Call: draft-ietf-v6ops-natpt-to-historic (Reasons to Move NAT-PT to Historic Status) to Informational RFC

The IESG has received a request from the IPv6 Operations WG (v6ops) to 
consider the following document:

- 'Reasons to Move NAT-PT to Historic Status '
   <draft-ietf-v6ops-natpt-to-historic-00.txt> as an Informational RFC

This document recommends that the IESG reclassifies RFC 2766 from
Standards Track to Historic.

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 <at> ietf.org mailing lists by 2007-03-15. Exceptionally, 
comments may be sent to iesg <at> ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-natpt-to-historic-00.txt

IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=15702&rfc_flag=0

_______________________________________________
IETF-Announce mailing list
IETF-Announce <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce
Permalink | Reply | 0 comments |
headers
The IESG | 1 Mar 2007 17:27
Picon
Favicon

Protocol Action: 'Authenticated Chunks for Stream Control Transmission Protocol (SCTP)' to Proposed Standard

The IESG has approved the following document:

- 'Authenticated Chunks for Stream Control Transmission Protocol (SCTP) '
   <draft-ietf-tsvwg-sctp-auth-08.txt> as a Proposed Standard

This document is the product of the Transport Area Working Group Working 
Group. 

The IESG contact persons are Magnus Westerlund and Lars Eggert.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-sctp-auth-08.txt

Technical Summary

This document describes a new chunk type, several parameters and
procedures for SCTP. This new chunk type can be used to authenticate SCTP
chunks by using shared keys between the sender and receiver. The new
parameters are used to establish the shared keys. Using TLS as defined in
RFC3436 (TLS over SCTP) does not help with this requirement because it
only secures SCTP user data. Therefore an SCTP extension is created by
this document which provides a mechanism for deriving shared keys for each
association. These association shared keys are derived from endpoint pair
shared keys, which are configured and might be empty, and data which is
exchanged during the SCTP association setup. The extension presented in
this document allows an SCTP sender to sign chunks using shared keys
between the sender and receiver. The receiver can then verify that the
chunks are sent from the sender and not from a malicious attacker as long
as the attacker does not know an association shared key.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane