headers
The IESG | 26 Nov 2007 16:29
Picon
Favicon

Protocol Action: 'Transmission of IPv6 via the IPv6 CS over IEEE 802.16 Networks' to Proposed Standard

The IESG has approved the following document:

- 'Transmission of IPv6 via the IPv6 CS over IEEE 802.16 Networks '
   <draft-ietf-16ng-ipv6-over-ipv6cs-11.txt> as a Proposed Standard

This document is the product of the IP over IEEE 802.16 Networks Working 
Group. 

The IESG contact persons are Jari Arkko and Mark Townsley.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-16ng-ipv6-over-ipv6cs-11.txt

Technical Summary

  This document specifies the addressing and operation of IPv6 over
  the IPv6 specific part of the packet CS for hosts served by a
  network that utilizes the IEEE Std 802.16 air interface. It
  recommends the assignment of a unique prefix (or prefixes) to each
  host and allows the host to use multiple identifiers within that
  prefix, including support for randomly generated identifiers.

Working Group Summary

  There was much initial debate about the link model to adopt.
  The interim made it clear that the "per-MS" prefix was
  preferable. Beyond that, there has been debate about how much
  802.16-specific details to include (e.g., on network entry
  procedure) for clarity.
(Continue reading)

Permalink | Reply | 0 comments |
headers
The IESG | 26 Nov 2007 17:13
Picon
Favicon

Document Action: 'Aggregation of DiffServ Service Classes' to Informational RFC

The IESG has approved the following document:

- 'Aggregation of DiffServ Service Classes '
   <draft-ietf-tsvwg-diffserv-class-aggr-07.txt> as an Informational RFC

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

The IESG contact persons are Magnus Westerlund and Lars Eggert.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-diffserv-class-aggr-07.txt

Technical Summary

  In the core of a high capacity network, service differentiation may
   still be needed to support applications' utilization of the network.
   Applications with similar traffic characteristics and performance
   requirements are mapped into diffserv service classes based on end-
   to-end behavior requirements of the applications as indicated by
   Diffserv Service Classes [5].  However, some network segments may be
   configured in such a way that a single forwarding treatment may
   satisfy the traffic characteristics and performance requirements of
   two or more service classes.  In these cases, it may be desirable to
   aggregate two or more Diffserv Service Classes [5] into a single
   forwarding treatment.  This document provides guidelines for the
   aggregation of Diffserv Service Classes [5] into forwarding
   treatments.

Working Group Summary
(Continue reading)

Permalink | Reply | 0 comments |
headers
IESG Secretary | 26 Nov 2007 18:15
Picon
Favicon

WG Action: RECHARTER: IP Flow Information Export WG (ipfix)

The IP Flow Information Export (ipfix) working group in the Operations
and Management Area of the IETF has been rechartered. For additional 
information, please contact the Area Directors or the working group 
Chairs.

+++

IP Flow Information Export (ipfix) 
=================================== 

Current Status: Active Working Group 

Chair(s): 
Nevil Brownlee <n.brownlee <at> auckland.ac.nz> 
Juergen Quittek <quittek <at> nw.neclab.eu> 

Operations and Management Area Director(s): 
Dan Romascanu <dromasca <at> avaya.com> 
Ronald Bonica <rbonica <at> juniper.net> 

Operations and Management Area Advisor: 
Dan Romascanu <dromasca <at> avaya.com> 

Mailing Lists: 
General Discussion: ipfix <at> ietf.org 
To Subscribe: http://www1.ietf.org/mailman/listinfo/ipfix 
Archive: http://www1.ietf.org/mail-archive/web/ipfix/current/index.html 

Description of Working Group:
(Continue reading)

Permalink | Reply | 0 comments |
headers
IESG Secretary | 26 Nov 2007 18:15
Picon
Favicon

WG Action: RECHARTER: Network Configuration WG (netconf)

The Network Configuration (netconf) working group in the Operations and
Management Area of the IETF has been rechartered. For additional
information, please contact the Area Directors or the working group 
Chairs.

+++

Network Configuration (netconf) 
================================ 

Current Status: Active Working Group 

Chair(s): 
Andy Bierman <ietf <at> andybierman.com> 
Simon Linen <simon <at> switch.ch> 

Operations and Management Area Director(s): 
Dan Romascanu <dromasca <at> avaya.com> 
Ronald Bonica <rbonica <at> juniper.net> 

Operations and Management Area Advisor: 
Dan Romascanu <dromasca <at> avaya.com> 

Technical Advisor(s): 
Wesley Hardaker <hardaker <at> tislabs.com> 

Mailing Lists: 
General Discussion: netconf <at> ops.ietf.org 
To Subscribe: netconf-request <at> ops.ietf.org 
In Body: in msg body: subscribe
(Continue reading)

Permalink | Reply | 0 comments |
headers
The IESG | 26 Nov 2007 18:16
Picon
Favicon

Document Action: 'State of Peer-to-Peer(P2P) Communication Across Network Address Translators(NATs)' to Informational RFC

The IESG has approved the following document:

- 'State of Peer-to-Peer(P2P) Communication Across Network Address 
   Translators(NATs) '
   <draft-ietf-behave-p2p-state-06.txt> as an Informational RFC

This document is the product of the Behavior Engineering for Hindrance 
Avoidance Working Group. 

The IESG contact persons are Magnus Westerlund and Lars Eggert.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-behave-p2p-state-06.txt

Technical Summary

This memo documents the various methods known to be in use by
applications to establish direct UDP or TCP communication in the
presence of Network Address Translators (NATs).

Working Group Summary

Agreeing on RFC3489 terminology (which is well known) versus
RFC4787 terminology (which is more accurate but longer) involved some
controversy. Consensus was to use RFC4787 terminology.

Document Quality

This document have had descent review in the WG. The techniques in this
document are implemented in various software that traverses NATs.
(Continue reading)

Permalink | Reply | 0 comments |
headers
The IESG | 26 Nov 2007 18:18
Picon
Favicon

Protocol Action: 'Extended Secure RTP Profile for RTCP-based Feedback (RTP/SAVPF)' to Proposed Standard

The IESG has approved the following document:

- 'Extended Secure RTP Profile for RTCP-based Feedback (RTP/SAVPF) '
   <draft-ietf-avt-profile-savpf-12.txt> as a Proposed Standard

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

The IESG contact persons is Cullen Jennings.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-profile-savpf-12.txt

Technical Summary

This memo specifies an RTP profile that combines the features of SRTP 
(SAVP) and the Extended Profile for RTCP-based Feedback (AVPF). Thus 
allowing SRTP's security functions, encryption and integrity protection 
to be used in session which requires more timely RTCP feedback than what 
AVP provides. Rules for how multiple profiles may be offered in SDP 
under offer/answer are also defined.

 Working Group Summary

There is consensus in the WG to publish this document.

Protocol Quality

The combination of the two profiles are basically orthogonal. Thus no 
new algorithms or other advanced features was needed to be define for 
this profile. The main new functionality is the signalling solution
(Continue reading)

Permalink | Reply | 0 comments |
headers
The IESG | 26 Nov 2007 18:22
Picon
Favicon

Protocol Action: 'A Telephony Gateway REgistration Protocol (TGREP)' to Proposed Standard

The IESG has approved the following document:

- 'A Telephony Gateway REgistration Protocol (TGREP) '
   <draft-ietf-iptel-tgrep-09.txt> as a Proposed Standard

This document is the product of the IP Telephony Working Group. 

The IESG contact persons are Cullen Jennings and Jon Peterson.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-iptel-tgrep-09.txt

Technical Summary

Telephony Gateway Registration Protocol (TGREP) is a companion
protocol to Telephony Routing over IP (TRIP, RFC 3219). TRIP itself is
a variation on BGP used to distribute routes to telephony gateways
between administrative domains. TGREP is an intra-domain protocol that
allows a gateway to feed its routes to a TRIP entity, which can then
distribute them inter-domain via TRIP. TGREP is identical to TRIP
itself in terms of state machinery and protocol messages. However, it
adds additional processing steps not needed in TRIP, and adds
attributes that are unique to intra-domain route propagation (such as
available capacity). 

Working Group Summary

The draft is a charter item of the IP Telephony (iptel) working group,
and is targeted for Proposed Standard. Work began in March of
2000. The document was adopted as a working group item in December
(Continue reading)

Permalink | Reply | 0 comments |
headers
The IESG | 26 Nov 2007 18:25
Picon
Favicon

Document Action: 'Reclassification of RFC 3525 to Historic' to Informational RFC

The IESG has approved the following document:

- 'Reclassification of RFC 3525 to Historic '
   <draft-taylor-megaco-obsol3525-01.txt> as an Informational RFC

This document has been reviewed in the IETF but is not the product of an
IETF Working Group. 

The IESG contact person is Cullen Jennings.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-taylor-megaco-obsol3525-01.txt

Technical Summary

 This document reclassifies RFC 3525, Gateway Control Protocol
 Version to Historic Status.  

Working Group Summary

 The WG has closed but main contributors to WG were consulted. 

Protocol Quality

 Reviewed by Cullen Jennings. 

IANA Note

Please replace all references to RFC 3525 in "Megaco/H.248 Packages"
registry to instead point at this document.  Also the pointer to these
(Continue reading)

Permalink | Reply | 0 comments |
headers
The IESG | 26 Nov 2007 18:52
Picon
Favicon

Protocol Action: 'URI Fragment Identifiers for the text/plain Media Type' to Proposed Standard

The IESG has approved the following document:

- 'URI Fragment Identifiers for the text/plain Media Type '
   <draft-wilde-text-fragment-09.txt> as a Proposed Standard

This document has been reviewed in the IETF but is not the product of an
IETF Working Group. 

The IESG contact person is Chris Newman.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-wilde-text-fragment-09.txt

Technical Summary

   This memo defines URI fragment identifiers for text/plain MIME
   entities.  These fragment identifiers make it possible to refer to
   parts of a text/plain MIME entity, either identified by character
   position or range, or by line position or range.  Fragment
   identifiers may also contain hash information to make them more
   robust.

Working Group Summary

 This was the product of an individual submitter.

Protocol Quality

 This was reviewed for the IESG by Chris Newman.  Substantive review
 comments were provided by many contributors.  Secdir review was
(Continue reading)

Permalink | Reply | 0 comments |
headers
Internet-Drafts | 26 Nov 2007 20:15
Picon
Favicon

I-D ACTION:draft-badra-ecdhe-tls-psk-01.txt

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

	Title		: ECDHE_PSK Ciphersuites for TLS
	Author(s)	: M. Badra
	Filename	: draft-badra-ecdhe-tls-psk-01.txt
	Pages		: 5
	Date		: 2007-11-26
	
This document updates RFC 4785 and RFC 4279 and specifies a set of 
   ciphersuites that use an Elliptic Curve Diffie-Hellman exchange 
   authenticated with a pre-shared key. These ciphersuites provides 
   Perfect Forward Secrecy. It specifies as well one authentication-
   only ciphersuites (with no encryption). This ciphersuite is useful 
   when authentication and integrity protection is desired, but 
   confidentiality is not needed or not permitted. 

   The reader is expected to become familiar with RFC 4785 and RFC 4279 
   prior to studying this document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-badra-ecdhe-tls-psk-01.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the
(Continue reading)

Permalink | Reply | 0 comments |

Gmane