From rfc-editor at rfc-editor.org  Tue Jun  3 15:23:41 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue,  3 Jun 2008 15:23:41 -0700 (PDT)
Subject: [rfc-dist] RFC 5194 on Framework for Real-Time Text over IP Using
	the Session Initiation Protocol (SIP)
Message-ID: <20080603222341.4A432135104@bosco.isi.edu>


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

        
        RFC 5194

        Title:      Framework for Real-Time Text over 
                    IP Using the Session Initiation Protocol 
                    (SIP) 
        Author:     A. van Wijk, Ed.,
                    G. Gybels, Ed.
        Status:     Informational
        Date:       June 2008
        Mailbox:    guido.gybels at rnid.org.uk, 
                    arnoud at realtimetext.org
        Pages:      31
        Characters: 68636
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sipping-toip-09.txt

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

This document lists the essential requirements for real-time
Text-over-IP (ToIP) and defines a framework for implementation of all
required functions based on the Session Initiation Protocol (SIP) and
the Real-Time Transport Protocol (RTP).  This includes interworking
between Text-over-IP and existing text telephony on the Public
Switched Telephone Network (PSTN) and other networks.  This memo 
provides information for the Internet community.

This document is a product of the Session Initiation Proposal Investigation Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Tue Jun  3 15:24:03 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue,  3 Jun 2008 15:24:03 -0700 (PDT)
Subject: [rfc-dist] RFC 5240 on Protocol Independent Multicast (PIM)
	Bootstrap Router MIB
Message-ID: <20080603222403.6936B135108@bosco.isi.edu>


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

        
        RFC 5240

        Title:      Protocol Independent Multicast (PIM) Bootstrap 
                    Router MIB 
        Author:     B. Joshi, R. Bijlani
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    bharat_joshi at infosys.com, 
                    rainab at gmail.com
        Pages:      23
        Characters: 42636
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pim-bsr-mib-06.txt

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

This document 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 used for
managing the Bootstrap Router (BSR) mechanism for PIM (Protocol
Independent Multicast).  [STANDARDS TRACK]

This document is a product of the Protocol Independent Multicast Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Tue Jun  3 15:23:53 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue,  3 Jun 2008 15:23:53 -0700 (PDT)
Subject: [rfc-dist] RFC 5236 on Improved Packet Reordering Metrics
Message-ID: <20080603222353.6F96F135106@bosco.isi.edu>


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

        
        RFC 5236

        Title:      Improved Packet Reordering Metrics 
        Author:     A. Jayasumana, N. Piratla,
                    T. Banka, A. Bare,
                    R. Whitner
        Status:     Informational
        Date:       June 2008
        Mailbox:    Anura.Jayasumana at colostate.edu, 
                    Nischal.Piratla at telekom.de, 
                    Tarun.Banka at colostate.edu,
                    abhijit_bare at agilent.com, 
                    rick_whitner at agilent.com
        Pages:      26
        Characters: 57805
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-jayasumana-reorder-density-08.txt

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

This document presents two improved metrics for packet reordering,
namely, Reorder Density (RD) and Reorder Buffer-occupancy Density
(RBD).  A threshold is used to clearly define when a packet is
considered lost, to bound computational complexity at O(N), and to
keep the memory requirement for evaluation independent of N, where N
is the length of the packet sequence.  RD is a comprehensive metric
that captures the characteristics of reordering, while RBD evaluates
the sequences from the point of view of recovery from reordering.

These metrics are simple to compute yet comprehensive in their
characterization of packet reordering.  The measures are robust and
orthogonal to packet loss and duplication.  This memo provides 
information for the Internet community.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Fri Jun  6 17:03:08 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri,  6 Jun 2008 17:03:08 -0700 (PDT)
Subject: [rfc-dist] RFC 5195 on BGP-Based Auto-Discovery for Layer-1 VPNs
Message-ID: <20080607000308.F0C67135881@bosco.isi.edu>


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

        
        RFC 5195

        Title:      BGP-Based Auto-Discovery for Layer-1 VPNs 
        Author:     H. Ould-Brahim, D. Fedyk,
                    Y. Rekhter
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    hbrahim at nortel.com, 
                    yakov at juniper.net, 
                    dwfedyk at nortel.com
        Pages:      10
        Characters: 21480
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l1vpn-bgp-auto-discovery-05.txt

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

The purpose of this document is to define a BGP-based auto-discovery
mechanism for Layer-1 VPNs (L1VPNs).  The
auto-discovery mechanism for L1VPNs allows the provider network
devices to dynamically discover the set of Provider Edges (PEs) having
ports attached to Customer Edge (CE) members of the same VPN.  That
information is necessary for completing the signaling phase of L1VPN
connections.  One main objective of a L1VPN auto-discovery mechanism is
to support the "single-end provisioning" model, where addition of a
new port to a given L1VPN would involve configuration changes only on
the PE that has this port and on the CE that is connected to the PE
via this port.  [STANDARDS TRACK]

This document is a product of the Layer 1 Virtual Private Networks Working
Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Mon Jun  9 15:16:50 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Mon,  9 Jun 2008 15:16:50 -0700 (PDT)
Subject: [rfc-dist] RFC 5256 on Internet Message Access Protocol - SORT and
	THREAD Extensions
Message-ID: <20080609221650.83005135F57@bosco.isi.edu>


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

        
        RFC 5256

        Title:      Internet Message Access Protocol - 
                    SORT and THREAD Extensions 
        Author:     M. Crispin, K. Murchison
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    IMAP+SORT+THREAD at Lingling.Panda.COM, 
                    murch at andrew.cmu.edu
        Pages:      19
        Characters: 40779
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-imapext-sort-20.txt

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

This document describes the base-level server-based sorting and
threading extensions to the IMAP protocol.  These extensions
provide substantial performance improvements for IMAP clients that
offer sorted and threaded views.  [STANDARDS TRACK]

This document is a product of the Internet Message Access Protocol Extension Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Mon Jun  9 15:16:49 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Mon,  9 Jun 2008 15:16:49 -0700 (PDT)
Subject: [rfc-dist] RFC 5255 on Internet Message Access Protocol
	Internationalization
Message-ID: <20080609221649.63ED3135F55@bosco.isi.edu>


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

        
        RFC 5255

        Title:      Internet Message Access Protocol Internationalization 
        Author:     C. Newman, A. Gulbrandsen, A. Melnikov
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    chris.newman at sun.com, 
                    arnt at oryx.com, 
                    Alexey.Melnikov at isode.com
        Pages:      20
        Characters: 41403
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-imapext-i18n-15.txt

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

Internet Message Access Protocol (IMAP) version 4rev1 has basic
support for non-ASCII characters in mailbox names and search
substrings.  It also supports non-ASCII message headers and content
encoded as specified by Multipurpose Internet Mail Extensions
(MIME).  This specification defines a collection of IMAP extensions
that improve international support including language negotiation for 
international error text, translations for namespace prefixes, and 
comparator negotiation for search, sort, and thread.  [STANDARDS TRACK]

This document is a product of the Internet Message Access Protocol Extension Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Mon Jun  9 15:16:48 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Mon,  9 Jun 2008 15:16:48 -0700 (PDT)
Subject: [rfc-dist] RFC 5239 on A Framework for Centralized Conferencing
Message-ID: <20080609221648.11BA9135F53@bosco.isi.edu>


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

        
        RFC 5239

        Title:      A Framework for Centralized Conferencing 
        Author:     M. Barnes, C. Boulton, O. Levin
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    mary.barnes at nortel.com, 
                    cboulton at avaya.com, 
                    oritl at microsoft.com
        Pages:      57
        Characters: 146927
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-xcon-framework-11.txt

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

This document defines the framework for Centralized Conferencing.
The framework allows participants using various call signaling
protocols, such as SIP, H.323, Jabber, Q.931 or ISDN User Part
(ISUP), to exchange media in a centralized unicast conference.  The
Centralized Conferencing Framework defines logical entities and
naming conventions.  The framework also outlines a set of
conferencing protocols, which are complementary to the call signaling
protocols, for building advanced conferencing applications.  The
framework binds all the defined components together for the benefit
of builders of conferencing systems.  [STANDARDS TRACK]

This document is a product of the Centralized Conferencing Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Mon Jun  9 15:16:51 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Mon,  9 Jun 2008 15:16:51 -0700 (PDT)
Subject: [rfc-dist] RFC 5258 on Internet Message Access Protocol version 4 -
	LIST Command Extensions
Message-ID: <20080609221651.CB5BD135F59@bosco.isi.edu>


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

        
        RFC 5258

        Title:      Internet Message Access Protocol version 
                    4 - LIST Command Extensions 
        Author:     B. Leiba, A. Melnikov
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    leiba at watson.ibm.com, 
                    Alexey.Melnikov at isode.com
        Pages:      31
        Characters: 65074
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-imapext-list-extensions-18.txt

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

IMAP4 has two commands for listing mailboxes: LIST and LSUB.  As we
have added extensions, such as Mailbox Referrals, that have required
specialized lists we have had to expand the number of list commands,
since each extension must add its function to both LIST and LSUB, and
these commands are not, as they are defined, extensible.  If we've
needed the extensions to work together, we've had to add a set of
commands to mix the different options, the set increasing in size
with each new extension.  This document describes an extension to the
base LIST command that will allow these additions to be done with
mutually compatible options to the LIST command, avoiding the
exponential increase in specialized list commands.  [STANDARDS TRACK]

This document is a product of the Internet Message Access Protocol Extension Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Wed Jun 11 16:43:17 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 11 Jun 2008 16:43:17 -0700 (PDT)
Subject: [rfc-dist] RFC 5187 on OSPFv3 Graceful Restart
Message-ID: <20080611234317.36E591364FD@bosco.isi.edu>


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

        
        RFC 5187

        Title:      OSPFv3 Graceful Restart 
        Author:     P. Pillay-Esnault, A. Lindem
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    ppe at cisco.com, acee at redback.com
        Pages:      7
        Characters: 14860
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ospf-ospfv3-graceful-restart-08.txt

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

This document describes the OSPFv3 graceful restart.  The OSPFv3
graceful restart is identical to that of OSPFv2 except for the
differences described in this document.  These differences include
the format of the grace Link State Advertisements (LSAs) and other
considerations.  [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.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Wed Jun 11 16:43:25 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 11 Jun 2008 16:43:25 -0700 (PDT)
Subject: [rfc-dist] RFC 5273 on Certificate Management over CMS (CMC):
	Transport Protocols
Message-ID: <20080611234325.8059B136503@bosco.isi.edu>


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

        
        RFC 5273

        Title:      Certificate Management over CMS (CMC): 
                    Transport Protocols 
        Author:     J. Schaad, M. Myers
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    jimsch at nwlink.com, mmyers at fastq.com
        Pages:      7
        Characters: 14030
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pkix-cmc-trans-08.txt

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

This document defines a number of transport mechanisms that are used
to move CMC (Certificate Management over CMS (Cryptographic Message
Syntax)) messages.  The transport mechanisms described in this
document are HTTP, file, mail, and TCP.  [STANDARDS TRACK]

This document is a product of the Public-Key Infrastructure (X.509) Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Wed Jun 11 16:43:29 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 11 Jun 2008 16:43:29 -0700 (PDT)
Subject: [rfc-dist] RFC 5274 on Certificate Managmement Messages over CMS
	(CMC): Complience Requirements
Message-ID: <20080611234329.8C086136506@bosco.isi.edu>


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

        
        RFC 5274

        Title:      Certificate Managmement Messages over CMS 
                    (CMC): Complience Requirements 
        Author:     J. Schaad, M. Myers
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    jimsch at nwlink.com, mmyers at fastq.com
        Pages:      13
        Characters: 27380
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pkix-cmc-compl-05.txt

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

This document provides a set of compliance statements about the CMC
(Certificate Management over CMS) enrollment protocol.  The ASN.1
structures and the transport mechanisms for the CMC enrollment
protocol are covered in other documents.  This document provides the
information needed to make a compliant version of CMC.  [STANDARDS TRACK]

This document is a product of the Public-Key Infrastructure (X.509) Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Wed Jun 11 16:43:24 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 11 Jun 2008 16:43:24 -0700 (PDT)
Subject: [rfc-dist] RFC 5272 on Certificate Management over CMS (CMC)
Message-ID: <20080611234324.55936136501@bosco.isi.edu>


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

        
        RFC 5272

        Title:      Certificate Management over CMS (CMC) 
        Author:     J. Schaad, M. Myers
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    jimsch at nwlink.com, mmyers at fastq.com
        Pages:      83
        Characters: 167138
        Obsoletes:  RFC2797

        I-D Tag:    draft-ietf-pkix-2797-bis-07.txt

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

This document defines the base syntax for CMC, a Certificate
Management protocol using the Cryptographic Message Syntax (CMS).
This protocol addresses two immediate needs within the Internet
Public Key Infrastructure (PKI) community:

1.  The need for an interface to public key certification products
and services based on CMS and PKCS #10 (Public Key Cryptography
Standard), and

2.  The need for a PKI enrollment protocol for encryption only keys
due to algorithm or hardware design.

CMC also requires the use of the transport document and the
requirements usage document along with this document for a full
definition.  [STANDARDS TRACK]

This document is a product of the Public-Key Infrastructure (X.509) Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Wed Jun 11 16:43:32 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 11 Jun 2008 16:43:32 -0700 (PDT)
Subject: [rfc-dist] RFC 5275 on CMS Symmetric Key Management and Distribution
Message-ID: <20080611234332.8DEB5136509@bosco.isi.edu>


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

        
        RFC 5275

        Title:      CMS Symmetric Key Management and 
                    Distribution 
        Author:     S. Turner
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    turners at ieca.com
        Pages:      89
        Characters: 207920
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-smime-symkeydist-10.txt

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

This document describes a mechanism to manage (i.e., set up,
distribute, and rekey) keys used with symmetric cryptographic
algorithms.  Also defined herein is a mechanism to organize users
into groups to support distribution of encrypted content using
symmetric cryptographic algorithms.  The mechanism uses the
Cryptographic Message Syntax (CMS) protocol and Certificate
Management over CMS (CMC) protocol to manage the
symmetric keys.  Any member of the group can then later use this
distributed shared key to decrypt other CMS encrypted objects with
the symmetric key.  This mechanism has been developed to support
Secure/Multipurpose Internet Mail Extensions (S/MIME) Mail List Agents 
(MLAs).  [STANDARDS TRACK]

This document is a product of the S/MIME Mail Security Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Wed Jun 11 16:43:13 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 11 Jun 2008 16:43:13 -0700 (PDT)
Subject: [rfc-dist] RFC 5170 on Low Density Parity Check (LDPC) Staircase
	and Triangle Forward Error Correction (FEC) Schemes
Message-ID: <20080611234313.E01591364FB@bosco.isi.edu>


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

        
        RFC 5170

        Title:      Low Density Parity Check (LDPC) 
                    Staircase and Triangle Forward Error Correction 
                    (FEC) Schemes 
        Author:     V. Roca, C. Neumann, D. Furodet
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    vincent.roca at inria.fr, 
                    christoph.neumann at thomson.net, 
                    david.furodet at st.com
        Pages:      33
        Characters: 68567
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rmt-bb-fec-ldpc-08.txt

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

This document describes two Fully-Specified Forward Error Correction
(FEC) Schemes, Low Density Parity Check (LDPC) Staircase and LDPC
Triangle, and their application to the reliable delivery of data
objects on the packet erasure channel (i.e., a communication path
where packets are either received without any corruption or discarded
during transmission).  These systematic FEC codes belong to the well-
known class of "Low Density Parity Check" codes, and are large block
FEC codes in the sense of RFC 3453.  [STANDARDS TRACK]

This document is a product of the Reliable Multicast Transport Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Wed Jun 11 16:43:22 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 11 Jun 2008 16:43:22 -0700 (PDT)
Subject: [rfc-dist] RFC 5197 on On the Applicability of Various Multimedia
	Internet KEYing (MIKEY) Modes and Extensions
Message-ID: <20080611234322.7B0111364FF@bosco.isi.edu>


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

        
        RFC 5197

        Title:      On the Applicability of Various 
                    Multimedia Internet KEYing (MIKEY) Modes and 
                    Extensions 
        Author:     S. Fries, D. Ignjatic
        Status:     Informational
        Date:       June 2008
        Mailbox:    steffen.fries at siemens.com, 
                    dignjatic at polycom.com
        Pages:      31
        Characters: 76848
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-msec-mikey-applicability-09.txt

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

Multimedia Internet Keying (MIKEY) is a key management protocol that
can be used for %real-time applications.  In particular, it has been
defined focusing on the support of the Secure %Real-time Transport
Protocol (SRTP).  MIKEY itself is standardized within RFC 3830 and
defines four key distribution methods.  Moreover, it is defined to
allow extensions of the protocol.  As MIKEY becomes more and more
accepted, extensions to the base protocol arise, especially in terms
of additional key distribution methods but also in terms of payload
enhancements.

This document provides an overview about the MIKEY base document in
general as well as the existing extensions for MIKEY, which have been
defined or are in the process of definition.  It is intended as an
additional source of information for developers or architects to
provide more insight in use case scenarios and motivations as well as
advantages and disadvantages for the different key distribution
schemes.  The use cases discussed in this document are strongly
related to dedicated SIP call scenarios providing challenges for key
management in general, among them media before Session Description
Protocol (SDP) answer, forking, and shared key conferencing.  This memo 
provides information for the Internet community.

This document is a product of the Multicast Security Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Fri Jun 13 17:11:11 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Fri, 13 Jun 2008 17:11:11 -0700 (PDT)
Subject: [rfc-dist] RFC 5257 on Internet Message Access Protocol - ANNOTATE
	Extension
Message-ID: <20080614001111.A948E136BC8@bosco.isi.edu>


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

        
        RFC 5257

        Title:      Internet Message Access Protocol - 
                    ANNOTATE Extension 
        Author:     C. Daboo, R. Gellens
        Status:     Experimental
        Date:       June 2008
        Mailbox:    cyrus at daboo.name, 
                    randy at qualcomm.com
        Pages:      31
        Characters: 58786
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-imapext-annotate-16.txt

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

The ANNOTATE extension to the Internet Message Access Protocol
permits clients and servers to maintain "meta data" for messages, or
individual message parts, stored in a mailbox on the server.  For
example, this can be used to attach comments and other useful
information to a message.  It is also possible to attach annotations
to specific parts of a message, so that, for example, they could be
marked as seen, or important, or a comment added.

Note that this document was the product of a WG that had good
consensus on how to approach the problem.  Nevertheless, the WG felt
it did not have enough information on implementation and deployment
hurdles to meet all of the requirements of a Proposed Standard.  The
IETF solicits implementations and implementation reports in order to
make further progress.

Implementers should be aware that this specification may change in an
incompatible manner when going to Proposed Standard status.
However, any incompatible changes will result in a new capability
name being used to prevent problems with any deployments of the
experimental extension.  This memo defines an Experimental Protocol 
for the Internet community.

This document is a product of the Internet Message Access Protocol Extension Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Tue Jun 17 15:17:19 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 17 Jun 2008 15:17:19 -0700 (PDT)
Subject: [rfc-dist] RFC 5265 on Mobile IPv4 Traversal across IPsec-Based VPN
	Gateways
Message-ID: <20080617221719.D186A137621@bosco.isi.edu>


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

        
        RFC 5265

        Title:      Mobile IPv4 Traversal across IPsec-Based 
                    VPN Gateways 
        Author:     S. Vaarala, E. Klovning
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    sami.vaarala at iki.fi, 
                    espen at birdstep.com
        Pages:      39
        Characters: 86254
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mip4-vpn-problem-solution-05.txt

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

This document outlines a solution for the Mobile IPv4 (MIPv4) and
IPsec coexistence problem for enterprise users.  The solution
consists of an applicability statement for using Mobile IPv4 and
IPsec for session mobility in corporate remote access scenarios, and
a required mechanism for detecting the trusted internal network
securely.  [STANDARDS TRACK]

This document is a product of the Mobility for IPv4 Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Tue Jun 17 15:17:21 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 17 Jun 2008 15:17:21 -0700 (PDT)
Subject: [rfc-dist] BCP 136,
	RFC 5266 on Secure Connectivity and Mobility Using Mobile IPv4 and
	IKEv2 Mobility and Multihoming (MOBIKE)
Message-ID: <20080617221721.7D2CA137623@bosco.isi.edu>


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

        BCP 136        
        RFC 5266

        Title:      Secure Connectivity and Mobility Using 
                    Mobile IPv4 and IKEv2 Mobility and 
                    Multihoming (MOBIKE) 
        Author:     V. Devarapalli, P. Eronen
        Status:     Best Current Practice
        Date:       June 2008
        Mailbox:    vijay at wichorus.com, 
                    pasi.eronen at nokia.com
        Pages:      15
        Characters: 33186
        See Also:   BCP0136

        I-D Tag:    draft-ietf-mip4-mobike-connectivity-03.txt

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

Enterprise users require mobility and secure connectivity when they
roam and connect to the services offered in the enterprise.  Secure
connectivity is required when the user connects to the enterprise
from an untrusted network.  Mobility is beneficial when the user
moves, either inside or outside the enterprise network, and acquires
a new IP address.  This document describes a solution using Mobile
IPv4 (MIPv4) and mobility extensions to IKEv2 (MOBIKE) to provide
secure connectivity and mobility.  This document specifies an 
Internet Best Current Practices for the Internet Community, and 
requests discussion and suggestions for improvements.

This document is a product of the Mobility for IPv4 Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Tue Jun 17 15:17:17 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 17 Jun 2008 15:17:17 -0700 (PDT)
Subject: [rfc-dist] RFC 5244 on Definition of Events for Channel-Oriented
	Telephony Signalling
Message-ID: <20080617221717.86A6D13761F@bosco.isi.edu>


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

        
        RFC 5244

        Title:      Definition of Events for Channel-Oriented 
                    Telephony Signalling 
        Author:     H. Schulzrinne, T. Taylor
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    schulzrinne at cs.columbia.edu, 
                    tom.taylor at rogers.com
        Pages:      23
        Characters: 55321
        Updates:    RFC4733

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

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

This memo updates RFC 4733 to add event codes for telephony signals
used for channel-associated signalling when carried in the telephony
event RTP payload.  It supersedes and adds to the original assignment
of event codes for this purpose in Section 3.14 of RFC 2833.  As
documented in Appendix A of RFC 4733, some of the RFC 2833 events have
been deprecated because their specification was ambiguous, erroneous,
or redundant.  In fact, the degree of change from Section 3.14 of RFC
2833 is such that implementations of the present document
will be fully backward compatible with RFC 2833 implementations only
in the case of full ABCD-bit signalling.  This document expands and
improves the coverage of signalling systems compared to RFC 2833.  
[STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Tue Jun 17 15:17:19 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 17 Jun 2008 15:17:19 -0700 (PDT)
Subject: [rfc-dist] RFC 5265 on Mobile IPv4 Traversal across IPsec-Based VPN
	Gateways
Message-ID: <20080617221719.D186A137621@bosco.isi.edu>


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

        
        RFC 5265

        Title:      Mobile IPv4 Traversal across IPsec-Based 
                    VPN Gateways 
        Author:     S. Vaarala, E. Klovning
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    sami.vaarala at iki.fi, 
                    espen at birdstep.com
        Pages:      39
        Characters: 86254
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mip4-vpn-problem-solution-05.txt

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

This document outlines a solution for the Mobile IPv4 (MIPv4) and
IPsec coexistence problem for enterprise users.  The solution
consists of an applicability statement for using Mobile IPv4 and
IPsec for session mobility in corporate remote access scenarios, and
a required mechanism for detecting the trusted internal network
securely.  [STANDARDS TRACK]

This document is a product of the Mobility for IPv4 Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

From rfc-editor at rfc-editor.org  Tue Jun 17 15:17:21 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 17 Jun 2008 15:17:21 -0700 (PDT)
Subject: [rfc-dist] BCP 136,
	RFC 5266 on Secure Connectivity and Mobility Using Mobile IPv4
	and	IKEv2 Mobility and Multihoming (MOBIKE)
Message-ID: <20080617221721.7D2CA137623@bosco.isi.edu>


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

        BCP 136        
        RFC 5266

        Title:      Secure Connectivity and Mobility Using 
                    Mobile IPv4 and IKEv2 Mobility and 
                    Multihoming (MOBIKE) 
        Author:     V. Devarapalli, P. Eronen
        Status:     Best Current Practice
        Date:       June 2008
        Mailbox:    vijay at wichorus.com, 
                    pasi.eronen at nokia.com
        Pages:      15
        Characters: 33186
        See Also:   BCP0136

        I-D Tag:    draft-ietf-mip4-mobike-connectivity-03.txt

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

Enterprise users require mobility and secure connectivity when they
roam and connect to the services offered in the enterprise.  Secure
connectivity is required when the user connects to the enterprise
from an untrusted network.  Mobility is beneficial when the user
moves, either inside or outside the enterprise network, and acquires
a new IP address.  This document describes a solution using Mobile
IPv4 (MIPv4) and mobility extensions to IKEv2 (MOBIKE) to provide
secure connectivity and mobility.  This document specifies an 
Internet Best Current Practices for the Internet Community, and 
requests discussion and suggestions for improvements.

This document is a product of the Mobility for IPv4 Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

From rfc-editor at rfc-editor.org  Tue Jun 17 15:17:19 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 17 Jun 2008 15:17:19 -0700 (PDT)
Subject: [rfc-dist] RFC 5265 on Mobile IPv4 Traversal across IPsec-Based VPN
	Gateways
Message-ID: <20080617221719.D186A137621@bosco.isi.edu>


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

        
        RFC 5265

        Title:      Mobile IPv4 Traversal across IPsec-Based 
                    VPN Gateways 
        Author:     S. Vaarala, E. Klovning
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    sami.vaarala at iki.fi, 
                    espen at birdstep.com
        Pages:      39
        Characters: 86254
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mip4-vpn-problem-solution-05.txt

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

This document outlines a solution for the Mobile IPv4 (MIPv4) and
IPsec coexistence problem for enterprise users.  The solution
consists of an applicability statement for using Mobile IPv4 and
IPsec for session mobility in corporate remote access scenarios, and
a required mechanism for detecting the trusted internal network
securely.  [STANDARDS TRACK]

This document is a product of the Mobility for IPv4 Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

From rfc-editor at rfc-editor.org  Tue Jun 17 15:17:21 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 17 Jun 2008 15:17:21 -0700 (PDT)
Subject: [rfc-dist] BCP 136,
	RFC 5266 on Secure Connectivity and Mobility Using Mobile IPv4
	and	IKEv2 Mobility and Multihoming (MOBIKE)
Message-ID: <20080617221721.7D2CA137623@bosco.isi.edu>


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

        BCP 136        
        RFC 5266

        Title:      Secure Connectivity and Mobility Using 
                    Mobile IPv4 and IKEv2 Mobility and 
                    Multihoming (MOBIKE) 
        Author:     V. Devarapalli, P. Eronen
        Status:     Best Current Practice
        Date:       June 2008
        Mailbox:    vijay at wichorus.com, 
                    pasi.eronen at nokia.com
        Pages:      15
        Characters: 33186
        See Also:   BCP0136

        I-D Tag:    draft-ietf-mip4-mobike-connectivity-03.txt

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

Enterprise users require mobility and secure connectivity when they
roam and connect to the services offered in the enterprise.  Secure
connectivity is required when the user connects to the enterprise
from an untrusted network.  Mobility is beneficial when the user
moves, either inside or outside the enterprise network, and acquires
a new IP address.  This document describes a solution using Mobile
IPv4 (MIPv4) and mobility extensions to IKEv2 (MOBIKE) to provide
secure connectivity and mobility.  This document specifies an 
Internet Best Current Practices for the Internet Community, and 
requests discussion and suggestions for improvements.

This document is a product of the Mobility for IPv4 Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

From rfc-editor at rfc-editor.org  Wed Jun 25 16:27:15 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 25 Jun 2008 16:27:15 -0700 (PDT)
Subject: [rfc-dist] RFC 5210 on A Source Address Validation Architecture
	(SAVA) Testbed and Deployment Experience
Message-ID: <20080625232715.E6DF6138CC5@bosco.isi.edu>


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

        
        RFC 5210

        Title:      A Source Address Validation Architecture 
                    (SAVA) Testbed and Deployment Experience 
        Author:     J. Wu, J. Bi,
                    X. Li, G. Ren,
                    K. Xu, M. Williams
        Status:     Experimental
        Date:       June 2008
        Mailbox:    jianping at cernet.edu.cn, junbi at cernet.edu.cn, 
                    xing at cernet.edu.cn, rg03 at mails.tsinghua.edu.cn, 
                    xuke at csnet1.cs.tsinghua.edu.cn, miw at juniper.net
        Pages:      25
        Characters: 58363
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-wu-sava-testbed-experience-06.txt

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

Because the Internet forwards packets according to the IP destination
address, packet forwarding typically takes place without inspection
of the source address and malicious attacks have been launched using
spoofed source addresses.  In an effort to enhance the Internet with
IP source address validation, a prototype implementation of the IP
Source Address Validation Architecture (SAVA) was created and an
evaluation was conducted on an IPv6 network.  This document reports
on the prototype implementation and the test results, as well as the
lessons and insights gained from experimentation.  This memo defines an 
Experimental Protocol for the Internet community.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Wed Jun 25 16:27:24 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 25 Jun 2008 16:27:24 -0700 (PDT)
Subject: [rfc-dist] RFC 5270 on Mobile IPv6 Fast Handovers over IEEE 802.16e
	Networks
Message-ID: <20080625232724.41AF8138CCB@bosco.isi.edu>


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

        
        RFC 5270

        Title:      Mobile IPv6 Fast Handovers over 
                    IEEE 802.16e Networks 
        Author:     H. Jang, J. Jee, Y. Han, S. Park, J. Cha
        Status:     Informational
        Date:       June 2008
        Mailbox:    heejin.jang at gmail.com, 
                    jhjee at etri.re.kr, 
                    yhhan at kut.ac.kr,
                    soohong.park at samsung.com, 
                    jscha at etri.re.kr
        Pages:      18
        Characters: 42358
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mipshop-fh80216e-07.txt

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

This document describes how a Mobile IPv6 Fast Handover can be
implemented on link layers conforming to the IEEE 802.16e suite of
specifications.  The proposed scheme tries to achieve seamless
handover by exploiting the link-layer handover indicators and thereby
synchronizing the IEEE 802.16e handover procedures with the Mobile
IPv6 fast handover procedures efficiently.  This memo provides information 
for the Internet community.

This document is a product of the Mobility for IP: Performance, Signaling and Handoff Optimization Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Wed Jun 25 16:27:26 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 25 Jun 2008 16:27:26 -0700 (PDT)
Subject: [rfc-dist] RFC 5271 on Mobile IPv6 Fast Handovers for 3G CDMA
	Networks
Message-ID: <20080625232726.9DA36138CCD@bosco.isi.edu>


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

        
        RFC 5271

        Title:      Mobile IPv6 Fast Handovers for 
                    3G CDMA Networks 
        Author:     H. Yokota, G. Dommety
        Status:     Informational
        Date:       June 2008
        Mailbox:    yokota at kddilabs.jp, 
                    gdommety at cisco.com
        Pages:      22
        Characters: 49316
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mipshop-3gfh-07.txt

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

Mobile IPv6 is designed to maintain its connectivity while moving
from one network to another.  It is adopted in 3G CDMA networks as a
way to maintain connectivity when the mobile node (MN) moves between
access routers.  However, this handover procedure requires not only
movement detection by the MN, but also the acquisition of a new
Care-of Address and Mobile IPv6 registration with the new care-of
address before the traffic can be sent or received in the target
network.  During this period, packets destined for the mobile node
may be lost, which may not be acceptable for a real-time application
such as Voice over IP (VoIP) or video telephony.  This document
specifies fast handover methods in the 3G CDMA networks in order to
reduce latency and packet loss during handover.  This memo provides 
information for the Internet community.

This document is a product of the Mobility for IP: Performance, Signaling and Handoff Optimization Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Wed Jun 25 16:27:21 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 25 Jun 2008 16:27:21 -0700 (PDT)
Subject: [rfc-dist] RFC 5268 on Mobile IPv6 Fast Handovers
Message-ID: <20080625232721.3C115138CC7@bosco.isi.edu>


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

        
        RFC 5268

        Title:      Mobile IPv6 Fast Handovers 
        Author:     R. Koodli, Ed.
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    rkoodli at starentnetworks.com
        Pages:      48
        Characters: 113090
        Obsoletes:  RFC4068

        I-D Tag:    draft-ietf-mipshop-fmipv6-rfc4068bis-07.txt

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

Mobile IPv6 enables a Mobile Node (MN) to maintain its connectivity to the
Internet when moving from one Access Router to another, a process
referred to as handover.  During handover, there is a period during
which the Mobile Node is unable to send or receive packets because of
link switching delay and IP protocol operations.  This "handover
latency" resulting from standard Mobile IPv6 procedures, namely
movement detection, new Care-of Address configuration, and Binding
Update, is often unacceptable to real-time traffic such as Voice over
IP (VoIP).  Reducing the handover latency could be beneficial to
non-real-time, throughput-sensitive applications as well.  This
document specifies a protocol to improve handover latency due to
Mobile IPv6 procedures.  This document does not address improving the
link switching latency.  [STANDARDS TRACK]

This document is a product of the Mobility for IP: Performance, Signaling and Handoff Optimization Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Wed Jun 25 16:27:22 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 25 Jun 2008 16:27:22 -0700 (PDT)
Subject: [rfc-dist] RFC 5269 on Distributing a Symmetric Fast Mobile IPv6
	(FMIPv6) Handover Key Using SEcure Neighbor Discovery (SEND)
Message-ID: <20080625232722.7AD0C138CC9@bosco.isi.edu>


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

        
        RFC 5269

        Title:      Distributing a Symmetric Fast Mobile 
                    IPv6 (FMIPv6) Handover Key Using SEcure 
                    Neighbor Discovery (SEND) 
        Author:     J. Kempf, R. Koodli
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    kempf at docomolabs-usa.com, 
                    rkoodli at starentnetworks.com
        Pages:      14
        Characters: 32742
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mipshop-handover-key-03.txt

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

Fast Mobile IPv6 requires that a Fast Binding Update is secured
using a security association shared between an Access Router and a
Mobile Node in order to avoid certain attacks.  In this document, a
method for provisioning a shared key from the Access Router to the
Mobile Node is defined to protect this signaling.  The Mobile Node
generates a public/private key pair using the same public key
algorithm as for SEND (RFC 3971).  The Mobile Node sends the public
key to the Access Router.  The Access Router encrypts a shared
handover key using the public key and sends it back to the Mobile
Node.  The Mobile Node decrypts the shared handover key using the
matching private key, and the handover key is then available for
generating an authenticator on a Fast Binding Update.  The Mobile
Node and Access Router use the Router Solicitation for Proxy
Advertisement and Proxy Router Advertisement from Fast Mobile IPv6
for the key exchange.  The key exchange messages are required to
have SEND security; that is, the source address is a
Cryptographically Generated Address (CGA) and the messages are signed
using the CGA private key of the sending node.  This allows the
Access Router, prior to providing the shared handover key, to
verify the authorization of the Mobile Node to claim the address
so that the previous care-of CGA in the Fast Binding Update can
act as the name of the key.  [STANDARDS TRACK]

This document is a product of the Mobility for IP: Performance, Signaling and Handoff Optimization Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Thu Jun 26 15:43:46 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Thu, 26 Jun 2008 15:43:46 -0700 (PDT)
Subject: [rfc-dist] RFC 5209 on Network Endpoint Assessment (NEA): Overview
	and Requirements
Message-ID: <20080626224346.4F1291390E3@bosco.isi.edu>


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

        
        RFC 5209

        Title:      Network Endpoint Assessment (NEA): Overview 
                    and Requirements 
        Author:     P. Sangster, H. Khosravi,
                    M. Mani, K. Narayan,
                    J. Tardo
        Status:     Informational
        Date:       June 2008
        Mailbox:    Paul_Sangster at symantec.com, 
                    hormuzd.m.khosravi at intel.com, 
                    mmani at avaya.com,  kaushik at cisco.com, 
                    joseph.tardo at nevisnetworks.com
        Pages:      53
        Characters: 132227
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nea-requirements-07.txt

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

This document defines the problem statement, scope, and protocol
requirements between the components of the NEA (Network Endpoint
Assessment) reference model.  NEA provides owners of networks (e.g.,
an enterprise offering remote access) a mechanism to evaluate the
posture of a system.  This may take place during the request for
network access and/or subsequently at any time while connected to the
network.  The learned posture information can then be applied to a
variety of compliance-oriented decisions.  The posture information is
frequently useful for detecting systems that are lacking or have
out-of-date security protection mechanisms such as: anti-virus and
host-based firewall software.  In order to provide context for the
requirements, a reference model and terminology are introduced.  This memo provides information for the Internet community.

This document is a product of the Network Endpoint Assessment Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From rfc-editor at rfc-editor.org  Tue Jun 17 15:17:19 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 17 Jun 2008 15:17:19 -0700 (PDT)
Subject: [rfc-dist] RFC 5265 on Mobile IPv4 Traversal across IPsec-Based VPN
	Gateways
Message-ID: <20080617221719.D186A137621@bosco.isi.edu>


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

        
        RFC 5265

        Title:      Mobile IPv4 Traversal across IPsec-Based 
                    VPN Gateways 
        Author:     S. Vaarala, E. Klovning
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    sami.vaarala at iki.fi, 
                    espen at birdstep.com
        Pages:      39
        Characters: 86254
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mip4-vpn-problem-solution-05.txt

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

This document outlines a solution for the Mobile IPv4 (MIPv4) and
IPsec coexistence problem for enterprise users.  The solution
consists of an applicability statement for using Mobile IPv4 and
IPsec for session mobility in corporate remote access scenarios, and
a required mechanism for detecting the trusted internal network
securely.  [STANDARDS TRACK]

This document is a product of the Mobility for IPv4 Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

From rfc-editor at rfc-editor.org  Tue Jun 17 15:17:21 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Tue, 17 Jun 2008 15:17:21 -0700 (PDT)
Subject: [rfc-dist] BCP 136,
	RFC 5266 on Secure Connectivity and Mobility Using Mobile IPv4
	and	IKEv2 Mobility and Multihoming (MOBIKE)
Message-ID: <20080617221721.7D2CA137623@bosco.isi.edu>


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

        BCP 136        
        RFC 5266

        Title:      Secure Connectivity and Mobility Using 
                    Mobile IPv4 and IKEv2 Mobility and 
                    Multihoming (MOBIKE) 
        Author:     V. Devarapalli, P. Eronen
        Status:     Best Current Practice
        Date:       June 2008
        Mailbox:    vijay at wichorus.com, 
                    pasi.eronen at nokia.com
        Pages:      15
        Characters: 33186
        See Also:   BCP0136

        I-D Tag:    draft-ietf-mip4-mobike-connectivity-03.txt

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

Enterprise users require mobility and secure connectivity when they
roam and connect to the services offered in the enterprise.  Secure
connectivity is required when the user connects to the enterprise
from an untrusted network.  Mobility is beneficial when the user
moves, either inside or outside the enterprise network, and acquires
a new IP address.  This document describes a solution using Mobile
IPv4 (MIPv4) and mobility extensions to IKEv2 (MOBIKE) to provide
secure connectivity and mobility.  This document specifies an 
Internet Best Current Practices for the Internet Community, and 
requests discussion and suggestions for improvements.

This document is a product of the Mobility for IPv4 Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

From rfc-editor at rfc-editor.org  Wed Jun 25 16:27:21 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 25 Jun 2008 16:27:21 -0700 (PDT)
Subject: [rfc-dist] RFC 5268 on Mobile IPv6 Fast Handovers
Message-ID: <20080625232721.3C115138CC7@bosco.isi.edu>


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

        
        RFC 5268

        Title:      Mobile IPv6 Fast Handovers 
        Author:     R. Koodli, Ed.
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    rkoodli at starentnetworks.com
        Pages:      48
        Characters: 113090
        Obsoletes:  RFC4068

        I-D Tag:    draft-ietf-mipshop-fmipv6-rfc4068bis-07.txt

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

Mobile IPv6 enables a Mobile Node (MN) to maintain its connectivity to the
Internet when moving from one Access Router to another, a process
referred to as handover.  During handover, there is a period during
which the Mobile Node is unable to send or receive packets because of
link switching delay and IP protocol operations.  This "handover
latency" resulting from standard Mobile IPv6 procedures, namely
movement detection, new Care-of Address configuration, and Binding
Update, is often unacceptable to real-time traffic such as Voice over
IP (VoIP).  Reducing the handover latency could be beneficial to
non-real-time, throughput-sensitive applications as well.  This
document specifies a protocol to improve handover latency due to
Mobile IPv6 procedures.  This document does not address improving the
link switching latency.  [STANDARDS TRACK]

This document is a product of the Mobility for IP: Performance, Signaling and Handoff Optimization Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

From rfc-editor at rfc-editor.org  Wed Jun 25 16:27:22 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 25 Jun 2008 16:27:22 -0700 (PDT)
Subject: [rfc-dist] RFC 5269 on Distributing a Symmetric Fast Mobile IPv6
	(FMIPv6)	Handover Key Using SEcure Neighbor Discovery (SEND)
Message-ID: <20080625232722.7AD0C138CC9@bosco.isi.edu>


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

        
        RFC 5269

        Title:      Distributing a Symmetric Fast Mobile 
                    IPv6 (FMIPv6) Handover Key Using SEcure 
                    Neighbor Discovery (SEND) 
        Author:     J. Kempf, R. Koodli
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    kempf at docomolabs-usa.com, 
                    rkoodli at starentnetworks.com
        Pages:      14
        Characters: 32742
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mipshop-handover-key-03.txt

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

Fast Mobile IPv6 requires that a Fast Binding Update is secured
using a security association shared between an Access Router and a
Mobile Node in order to avoid certain attacks.  In this document, a
method for provisioning a shared key from the Access Router to the
Mobile Node is defined to protect this signaling.  The Mobile Node
generates a public/private key pair using the same public key
algorithm as for SEND (RFC 3971).  The Mobile Node sends the public
key to the Access Router.  The Access Router encrypts a shared
handover key using the public key and sends it back to the Mobile
Node.  The Mobile Node decrypts the shared handover key using the
matching private key, and the handover key is then available for
generating an authenticator on a Fast Binding Update.  The Mobile
Node and Access Router use the Router Solicitation for Proxy
Advertisement and Proxy Router Advertisement from Fast Mobile IPv6
for the key exchange.  The key exchange messages are required to
have SEND security; that is, the source address is a
Cryptographically Generated Address (CGA) and the messages are signed
using the CGA private key of the sending node.  This allows the
Access Router, prior to providing the shared handover key, to
verify the authorization of the Mobile Node to claim the address
so that the previous care-of CGA in the Fast Binding Update can
act as the name of the key.  [STANDARDS TRACK]

This document is a product of the Mobility for IP: Performance, Signaling and Handoff Optimization Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

From rfc-editor at rfc-editor.org  Wed Jun 25 16:27:15 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 25 Jun 2008 16:27:15 -0700 (PDT)
Subject: [rfc-dist] RFC 5210 on A Source Address Validation Architecture
	(SAVA) Testbed	and Deployment Experience
Message-ID: <20080625232715.E6DF6138CC5@bosco.isi.edu>


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

        
        RFC 5210

        Title:      A Source Address Validation Architecture 
                    (SAVA) Testbed and Deployment Experience 
        Author:     J. Wu, J. Bi,
                    X. Li, G. Ren,
                    K. Xu, M. Williams
        Status:     Experimental
        Date:       June 2008
        Mailbox:    jianping at cernet.edu.cn, junbi at cernet.edu.cn, 
                    xing at cernet.edu.cn, rg03 at mails.tsinghua.edu.cn, 
                    xuke at csnet1.cs.tsinghua.edu.cn, miw at juniper.net
        Pages:      25
        Characters: 58363
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-wu-sava-testbed-experience-06.txt

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

Because the Internet forwards packets according to the IP destination
address, packet forwarding typically takes place without inspection
of the source address and malicious attacks have been launched using
spoofed source addresses.  In an effort to enhance the Internet with
IP source address validation, a prototype implementation of the IP
Source Address Validation Architecture (SAVA) was created and an
evaluation was conducted on an IPv6 network.  This document reports
on the prototype implementation and the test results, as well as the
lessons and insights gained from experimentation.  This memo defines an 
Experimental Protocol for the Internet community.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

From rfc-editor at rfc-editor.org  Wed Jun 25 16:27:26 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Wed, 25 Jun 2008 16:27:26 -0700 (PDT)
Subject: [rfc-dist] RFC 5271 on Mobile IPv6 Fast Handovers for 3G CDMA
	Networks
Message-ID: <20080625232726.9DA36138CCD@bosco.isi.edu>


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

        
        RFC 5271

        Title:      Mobile IPv6 Fast Handovers for 
                    3G CDMA Networks 
        Author:     H. Yokota, G. Dommety
        Status:     Informational
        Date:       June 2008
        Mailbox:    yokota at kddilabs.jp, 
                    gdommety at cisco.com
        Pages:      22
        Characters: 49316
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mipshop-3gfh-07.txt

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

Mobile IPv6 is designed to maintain its connectivity while moving
from one network to another.  It is adopted in 3G CDMA networks as a
way to maintain connectivity when the mobile node (MN) moves between
access routers.  However, this handover procedure requires not only
movement detection by the MN, but also the acquisition of a new
Care-of Address and Mobile IPv6 registration with the new care-of
address before the traffic can be sent or received in the target
network.  During this period, packets destined for the mobile node
may be lost, which may not be acceptable for a real-time application
such as Voice over IP (VoIP) or video telephony.  This document
specifies fast handover methods in the 3G CDMA networks in order to
reduce latency and packet loss during handover.  This memo provides 
information for the Internet community.

This document is a product of the Mobility for IP: Performance, Signaling and Handoff Optimization Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

From rfc-editor at rfc-editor.org  Mon Jun 30 18:06:04 2008
From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org)
Date: Mon, 30 Jun 2008 18:06:04 -0700 (PDT)
Subject: [rfc-dist] BCP 138,
	RFC 5248 on A Registry for SMTP Enhanced Mail System Status Codes
Message-ID: <20080701010604.8A0DA13B50C@bosco.isi.edu>


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

        BCP 138        
        RFC 5248

        Title:      A Registry for SMTP Enhanced 
                    Mail System Status Codes 
        Author:     T. Hansen, J. Klensin
        Status:     Best Current Practice
        Date:       June 2008
        Mailbox:    tony+mailesc at maillennium.att.com, 
                    john+ietf at jck.com
        Pages:      11
        Characters: 23845
        Updates:    RFC3463, RFC4468, RFC4954
        See Also:   BCP0138

        I-D Tag:    draft-hansen-4468upd-mailesc-registry-05.txt

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

The specification for enhanced mail system status codes, RFC 3463,
establishes a new code model and lists a collection of status codes.
While it anticipated that more codes would be added over time, it did
not provide an explicit mechanism for registering and tracking those
codes.  This document specifies an IANA registry for mail system
enhanced status codes, and initializes that registry with the codes
so far established in published standards-track documents, as well as
other codes that have become established in the industry.  This document 
specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute