Last Call: draft-ietf-rmt-bb-lct-revised (Layered Coding Transport (LCT) Building Block) to Proposed Standard

2009-04-01 Thread The IESG
The IESG has received a request from the Reliable Multicast Transport WG
(rmt) to consider the following document:

- 'Layered Coding Transport (LCT) Building Block '
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
i...@ietf.org mailing lists by 2009-04-15. Exceptionally, 
comments may be sent to i...@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-rmt-bb-lct-revised-09.txt


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

The following IPR Declarations may be related to this I-D:



___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce


Last Call: draft-ietf-isms-secshell (Secure Shell Transport Model for SNMP) to Proposed Standard

2009-04-01 Thread The IESG
The IESG has received a request from the Integrated Security Model for 
SNMP WG (isms) to consider the following document:

- 'Secure Shell Transport Model for SNMP '
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
i...@ietf.org mailing lists by 2009-04-15. Exceptionally, 
comments may be sent to i...@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-isms-secshell-15.txt


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

The following IPR Declarations may be related to this I-D:



___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce


Last Call: draft-ietf-isms-tmsm (Transport Subsystem for the Simple Network Management Protocol (SNMP)) to Proposed Standard

2009-04-01 Thread The IESG
The IESG has received a request from the Integrated Security Model for 
SNMP WG (isms) to consider the following document:

- 'Transport Subsystem for the Simple Network Management Protocol (SNMP)
'
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
i...@ietf.org mailing lists by 2009-04-15. Exceptionally, 
comments may be sent to i...@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-isms-tmsm-16.txt


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

The following IPR Declarations may be related to this I-D:



___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce


Last Call: draft-ietf-isms-transport-security-model (Transport Security Model for SNMP) to Proposed Standard

2009-04-01 Thread The IESG
The IESG has received a request from the Integrated Security Model for 
SNMP WG (isms) to consider the following document:

- 'Transport Security Model for SNMP '
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
i...@ietf.org mailing lists by 2009-04-15. Exceptionally, 
comments may be sent to i...@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-isms-transport-security-model-12.txt


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

The following IPR Declarations may be related to this I-D:



___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce


IETF NomCom Changes Discussion

2009-04-01 Thread IETF Chair
Several changes to the NomCom process were discussed during the plenary
session last Wednesday.  The minutes have been posted so that anyone that
was not at the plenary session can catch up.  The minutes can be found
here:

http://www.ietf.org/proceedings/09mar/minutes/plenaryw.txt

The discussion will continue on the ietf-nom...@ietf.org mail list.

Thanks,
  Russ
___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce


RFC 5513 on IANA Considerations for Three Letter Acronyms

2009-04-01 Thread rfc-editor

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


RFC 5513

Title:  IANA Considerations for Three Letter 
Acronyms 
Author: A. Farrel
Status: Informational
Date:   1 April 2009
Mailbox:adr...@olddog.co.uk
Pages:  7
Characters: 13931
Updates/Obsoletes/SeeAlso:   None

I-D Tag:draft-farrel-iana-tla-registry-00.txt

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

Three Letter Acronyms (TLAs) are commonly used to identify components
of networks or protocols as designed or specified within the IETF.  A
common concern is that one acronym may have multiple expansions.
While this may not have been an issue in the past, network
convergence means that protocols that did not previously operate
together are now found in close proximity.  This results in
contention for acronyms, and confusion in interpretation.  Such
confusion has the potential to degrade the performance of the
Internet as misunderstandings lead to misconfiguration or other
operating errors.

Given the growing use of TLAs and the relatively small number
available, this document specifies a Badly Construed Proposal (BCP) for the
management of a registry of TLAs within the IETF, and the procedures
for the allocation of new TLAs from the registry.  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-edi...@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@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce


RFC 5514 on IPv6 over Social Networks

2009-04-01 Thread rfc-editor

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


RFC 5514

Title:  IPv6 over Social Networks 
Author: E. Vyncke
Status: Experimental
Date:   1 April 2009
Mailbox:evyn...@cisco.com
Pages:  6
Characters: 10127
Updates/Obsoletes/SeeAlso:   None

I-D Tag:draft-vyncke-ip-over-social-network-01.txt

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


There is a lack of IPv6 utilization in early 2009; this is partly
linked to the fact that the number of IPv6 nodes is rather low.  This
document proposes to vastly increase the number of IPv6 hosts by
transforming all Social Networking platforms into IPv6 networks.
This will immediately add millions of IPv6 hosts to the existing IPv6
Internet.  This document includes sections on addressing and
transport of IPv6 over a Social Network.  A working prototype has
been developed.  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-edi...@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@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce


Protocol Action: 'A Session Description Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer' to Proposed Standard

2009-04-01 Thread The IESG
The IESG has approved the following document:

- 'A Session Description Protocol (SDP) Offer/Answer Mechanism to Enable 
   File Transfer '
as a Proposed Standard

This document is the product of the Multiparty Multimedia Session Control 
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-mmusic-file-transfer-mech-11.txt

Technical summary:

The document defines extensions to the SDP offer/answer model
to enable file transfer as part of SDP-negotiated multimedia
sessions.  It also specifies using MSRP for the actual file
transmission.

Working Group summary:

The MMUSIC WG has firm consenses on publishing this document
as Proposed Standard.

Document quality:

The document is considered ready for publication.

An early interoperability test of independent implementations
from various major vendors on an image sharing specification
(which uses the file transfer I-D as a basis) took place
already in 2007 under the auspices of the GSM Association.
The interop event provided useful input for this and other
specifications.

Personnel:

The document shepherd is Joerg Ott, the responsible AD is
Cullen Jennings.

___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce


RFC 5428 on Management Event Management Information Base (MIB) for PacketCable- and IPCablecom-Compliant Devices

2009-04-01 Thread rfc-editor

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


RFC 5428

Title:  Management Event Management Information Base 
(MIB) for PacketCable- and IPCablecom-Compliant
Devices 
Author: S. Channabasappa, W. De Ketelaere,
E. Nechamkin
Status: Standards Track
Date:   April 2009
Mailbox:suma...@cablelabs.com, 
deketela...@tcomlabs.com, 
enecham...@broadcom.com
Pages:  37
Characters: 78139
Updates/Obsoletes/SeeAlso:   None

I-D Tag:draft-ietf-ipcdn-pktc-eventmess-14.txt

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

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it defines a basic set of managed objects for Simple
Network Management Protocol (SNMP)-based management of events that
can be generated by PacketCable- and IPCablecom-compliant Multimedia
Terminal Adapter devices.  [STANDARDS TRACK]

This document is a product of the IP over Cable Data Network 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-edi...@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@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce