I-D Action:draft-lha-des-die-die-die-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : Deprecate DES support for Kerberos
	Author(s)       : L. Astrand
	Filename        : draft-lha-des-die-die-die-01.txt
	Pages           : 10
	Date            : 2009-08-02

A long long time ago DES was standardized.  Some 30 years later
(2003) is was withdrawn as a standard by NIST, today 6 years later,
its time for DES to finally die.  By 2008 it was possible to brute
force DES keys in 6.4 days using less than USD 10k worth of hardware.
So by 2008 DES had passed its sell-by date.  Use in Kerberos should
therefore stop.1.  Requirements Notation

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].2.  Background

Kerberos 5 was defined in [RFC1510] and updated in [RFC4120], the
Kerberos crypto system is defined by [RFC3961] and includes support
for DES encryption types.  This document move all of the DES
encryption and related checksum types to historic.

DES was withdrawn in [DES-Transition-Plan] by NIST.  IETF have also
published its the position in [RFC4772], which in the recommendation
summery is made very clear: "don't use DES".3.  Recommendations

This document removes the mandatory-to-implement types from
[RFC4120]: Encryption: DES-CBC-MD5

I-D Action:draft-irtf-mobopts-mmcastv6-ps-08.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : Multicast Mobility in MIPv6: Problem Statement and Brief Survey
	Author(s)       : G. Fairhurst
	Filename        : draft-irtf-mobopts-mmcastv6-ps-08.txt
	Pages           : 34
	Date            : 2009-08-02

This document discusses current mobility extensions to IP layer 
multicast. It describes problems arising from mobile group 
communication in general, the case of multicast listener mobility, 
and for mobile senders using Any Source Multicast and Source Specific 
Multicast. Characteristic aspects of multicast routing and deployment 
issues for fixed IPv6 networks are summarized. Specific properties 
and interplays with the underlying network access are surveyed with 
respect to the relevant technologies in the wireless domain. It 
outlines the principal approaches to multicast mobility, together 
with a comprehensive exploration of the mobile multicast problem and 
solution space. This document concludes with a conceptual roadmap for 
initial steps in standardization for use by future mobile multicast 
protocol designers. This document is a product of the IP Mobility 
Optimizations (MobOpts) Research Group.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-irtf-mobopts-mmcastv6-ps-08.txt

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

Below is the data which will enable a MIME compliant mail reader

I-D Action:draft-ietf-dime-diameter-qos-10.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Diameter Maintenance and Extensions Working Group of the IETF.

	Title           : Diameter Quality of Service Application
	Author(s)       : D. Sun, et al.
	Filename        : draft-ietf-dime-diameter-qos-10.txt
	Pages           : 58
	Date            : 2009-08-02

This document describes the framework, messages and procedures for
the Diameter Quality of Service (QoS) application.  The Diameter QoS
application allows network elements to interact with Diameter servers
when allocating QoS resources in the network.  In particular, two
modes of operation -- Pull and Push -- are defined.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dime-diameter-qos-10.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
I-D-Announce mailing list
I-D-Announce <at> ietf.org

I-D Action:draft-sheffer-ipsecme-ikev2-gtc-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : Using EAP-GTC for Simple User Authentication in IKEv2
	Author(s)       : Y. Sheffer
	Filename        : draft-sheffer-ipsecme-ikev2-gtc-01.txt
	Pages           : 8
	Date            : 2009-08-02

Despite many years of effort, simple username-password authentication
is still prevalent.  In many cases a password is the only credential
available to the end user.  IKEv2 uses EAP as a sub-protocol for user
authentication.  This provides a well-specified and extensible
architecture.  To this day EAP does not provide a simple password-
based authentication method.  The only existing password
authentication methods either require the peer to know the password
in advance (EAP-MD5), or are needlessly complex when used within
IKEv2 (e.g.  PEAP).  This document codifies the common practice of
using EAP-GTC for this type of authentication, with the goal of
achieving maximum interoperability.  The various security issues are
extensively analyzed.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-sheffer-ipsecme-ikev2-gtc-01.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

I-D Action:draft-ietf-mboned-addrarch-06.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the MBONE Deployment Working Group of the IETF.

	Title           : Overview of the Internet Multicast Addressing Architecture
	Author(s)       : P. Savola
	Filename        : draft-ietf-mboned-addrarch-06.txt
	Pages           : 16
	Date            : 2009-08-03

The lack of up-to-date documentation on IP multicast address
allocation and assignment procedures has caused a great deal of
confusion.  To clarify the situation, this memo describes the
allocation and assignment techniques and mechanisms currently (as of
this writing) in use.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mboned-addrarch-06.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
I-D-Announce mailing list
I-D-Announce <at> ietf.org

I-D Action:draft-ietf-mboned-multiaaa-framework-09.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the MBONE Deployment Working Group of the IETF.

	Title           : Requirements for Multicast AAA coordinated between Content Provider(s) and Network Service Provider(s)
	Author(s)       : T. Hayashi, et al.
	Filename        : draft-ietf-mboned-multiaaa-framework-09.txt
	Pages           : 22
	Date            : 2009-08-03

IP multicast-based services, such as TV broadcasting or
videoconferencing raise the issue of making sure that potential
customers are fully entitled to access the corresponding contents.
There is indeed a need for service and content providers to identify
users (if not authenticate, especially within the context of
enforcing electronic payment schemes) and to retrieve statistical
information for accounting purposes, as far as content and network
usage are concerned.  This memo describes the framework for
specifying the Authorization, Authentication and Accounting (AAA)
capabilities that could be activated within the context of the
deployment and the operation of IP multicast-based services.  This
framework addresses the requirements presented in "Requirements for
Accounting, Authentication and Authorization in Well Managed IP
Multicasting Services" [I-D.ietf-mboned-maccnt-req].  The memo
provides a basic AAA enabled model as well as an extended fully
enabled model with resource and admission control coordination.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mboned-multiaaa-framework-09.txt

Internet-Drafts are also available by anonymous FTP at:

I-D Action:draft-ietf-pcn-marking-behaviour-05.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Congestion and Pre-Congestion Notification Working Group of the IETF.

	Title           : Metering and marking behaviour of PCN-nodes
	Author(s)       : P. Eardley
	Filename        : draft-ietf-pcn-marking-behaviour-05.txt
	Pages           : 25
	Date            : 2009-08-03

The objective of Pre-Congestion Notification (PCN) is to protect the
quality of service (QoS) of inelastic flows within a Diffserv domain,
in a simple, scalable, and robust fashion.  This document defines the
two metering and marking behaviours of PCN-nodes.  Threshold-metering
and -marking marks all PCN-packets if the rate of PCN-traffic is
greater than a configured rate ("PCN-threshold-rate").  Excess-
traffic-metering and -marking marks a proportion of PCN-packets, such
that the amount marked equals the rate of PCN-traffic in excess of a
configured rate ("PCN-excess-rate").  The level of marking allows
PCN-boundary-nodes to make decisions about whether to admit or
terminate PCN-flows.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pcn-marking-behaviour-05.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

Last Call: draft-ietf-ntp-dhcpv6-ntp-opt (Network Time Protocol (NTP) Server Option for DHCPv6) to Proposed Standard

The IESG has received a request from the Network Time Protocol WG (ntp) 
to consider the following document:

- 'Network Time Protocol (NTP) Server Option for DHCPv6 '
   <draft-ietf-ntp-dhcpv6-ntp-opt-04.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf <at> ietf.org mailing lists by 2009-08-17. Exceptionally, 
comments may be sent to iesg <at> ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-ntp-dhcpv6-ntp-opt-04.txt

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

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

Last Call: draft-ietf-vcarddav-webdav-mkcol (Extended MKCOL for WebDAV) to Proposed Standard

The IESG has received a request from the vCard and CardDAV WG (vcarddav) 
to consider the following document:

- 'Extended MKCOL for WebDAV '
   <draft-ietf-vcarddav-webdav-mkcol-05.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf <at> ietf.org mailing lists by 2009-08-17. Exceptionally, 
comments may be sent to iesg <at> ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-vcarddav-webdav-mkcol-05.txt

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

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

I-D Action:draft-atlas-icmp-unnumbered-07.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : Extending ICMP for Interface and Next-hop Identification
	Author(s)       : R. Bonica, et al.
	Filename        : draft-atlas-icmp-unnumbered-07.txt
	Pages           : 17
	Date            : 2009-08-03

This memo defines a data structure that can be appended to selected
ICMP messages.  The ICMP extension defined herein can be used
identify any combination of the following: the IP interface upon
which a datagram arrived, the sub-IP component of an IP interface
upon which a datagram arrived, the IP interface through which the
datagram would have been for forwarded had it been forwardable, the
IP next hop to which the datagram would have been forwarded.

Devices can use this ICMP extension to identify interfaces and their
components by any combination of the following: ifIndex, IPv4
address, IPv6 address, name and MTU.  ICMP-aware devices can use
these extensions to identify both numbered and unnumbered interfaces.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-atlas-icmp-unnumbered-07.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.