RFC 5110 on Overview of the Internet Multicast Routing Architecture
rfc-editor@rfc-editor.org Fri, 01 February 2008 01:00 UTC
Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietfarch-ietf-announce-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2321028C158; Thu, 31 Jan 2008 17:00:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level:
X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZeYq1bNXH9tD; Thu, 31 Jan 2008 17:00:35 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1843428C109; Thu, 31 Jan 2008 17:00:35 -0800 (PST)
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 16B3528C109; Thu, 31 Jan 2008 17:00:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M9OOESLM6nEs; Thu, 31 Jan 2008 17:00:32 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 5585028C0EE; Thu, 31 Jan 2008 17:00:32 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id EF61710C789; Thu, 31 Jan 2008 16:32:23 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5110 on Overview of the Internet Multicast Routing Architecture
From: rfc-editor@rfc-editor.org
Message-Id: <20080201003223.EF61710C789@bosco.isi.edu>
Date: Thu, 31 Jan 2008 16:32:23 -0800
Cc: mboned@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ietf-announce.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries. RFC 5110 Title: Overview of the Internet Multicast Routing Architecture Author: P. Savola Status: Informational Date: January 2008 Mailbox: psavola@funet.fi Pages: 25 Characters: 56217 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mboned-routingarch-12.txt URL: http://www.rfc-editor.org/rfc/rfc5110.txt This document describes multicast routing architectures that are currently deployed on the Internet. This document briefly describes those protocols and references their specifications. This memo also reclassifies several older RFCs to Historic. These RFCs describe multicast routing protocols that were never widely deployed or have fallen into disuse. This memo provides information for the Internet community. This document is a product of the MBONE Deployment 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 list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org http://www.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Thu Jan 31 17:22:17 2008 Return-Path: <ietf-announce-bounces@ietf.org> X-Original-To: ietfarch-ietf-announce-archive@core3.amsl.com Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D11E33A680C; Thu, 31 Jan 2008 17:22:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.207 X-Spam-Level: X-Spam-Status: No, score=-17.207 tagged_above=-999 required=5 tests=[AWL=-0.208, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28Tz4g8VUH-R; Thu, 31 Jan 2008 17:22:17 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A58403A67B0; Thu, 31 Jan 2008 17:22:16 -0800 (PST) X-Original-To: ietf-announce@core3.amsl.com Delivered-To: ietf-announce@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C63403A6780 for <ietf-announce@core3.amsl.com>; Thu, 31 Jan 2008 17:22:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sLlY4Zn18l+S for <ietf-announce@core3.amsl.com>; Thu, 31 Jan 2008 17:22:14 -0800 (PST) Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 1F1FA3A67B0 for <ietf-announce@ietf.org>; Thu, 31 Jan 2008 17:22:14 -0800 (PST) Received: by bosco.isi.edu (Postfix, from userid 70) id 0E3BF10C7A7; Thu, 31 Jan 2008 17:23:48 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org Subject: RFC 5116 on An Interface and Algorithms for Authenticated Encryption From: rfc-editor@rfc-editor.org Message-Id: <20080201012348.0E3BF10C7A7@bosco.isi.edu> Date: Thu, 31 Jan 2008 17:23:48 -0800 (PST) Cc: rfc-editor@rfc-editor.org X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: <ietf-announce.ietf.org> List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe> List-Post: <mailto:ietf-announce@ietf.org> List-Help: <mailto:ietf-announce-request@ietf.org?subject=help> List-Subscribe: <http://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ietf-announce-bounces@ietf.org Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 5116 Title: An Interface and Algorithms for Authenticated Encryption Author: D. McGrew Status: Standards Track Date: January 2008 Mailbox: mcgrew@cisco.com Pages: 22 Characters: 50539 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-mcgrew-auth-enc-05.txt URL: http://www.rfc-editor.org/rfc/rfc5116.txt This document defines algorithms for Authenticated Encryption with Associated Data (AEAD), and defines a uniform interface and a registry for such algorithms. The interface and registry can be used as an application-independent set of cryptoalgorithm suites. This approach provides advantages in efficiency and security, and promotes the reuse of crypto implementations. [STANDARDS TRACK] 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 list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org http://www.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Thu Jan 31 17:22:49 2008 Return-Path: <ietf-announce-bounces@ietf.org> X-Original-To: ietfarch-ietf-announce-archive@core3.amsl.com Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9950628C1B6 for <ietfarch-ietf-announce-archive@core3.amsl.com>; Thu, 31 Jan 2008 17:22:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.168 X-Spam-Level: X-Spam-Status: No, score=-17.168 tagged_above=-999 required=5 tests=[AWL=-0.169, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j3MUIK5trWXG; Thu, 31 Jan 2008 17:22:48 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9FDE228C197; Thu, 31 Jan 2008 17:22:48 -0800 (PST) X-Original-To: ietf-announce@core3.amsl.com Delivered-To: ietf-announce@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE9FE28C197 for <ietf-announce@core3.amsl.com>; Thu, 31 Jan 2008 17:22:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LscJhgjEQJPg for <ietf-announce@core3.amsl.com>; Thu, 31 Jan 2008 17:22:46 -0800 (PST) Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id D8A5728C133 for <ietf-announce@ietf.org>; Thu, 31 Jan 2008 17:22:40 -0800 (PST) Received: by bosco.isi.edu (Postfix, from userid 70) id CDB2910C7A9; Thu, 31 Jan 2008 17:24:14 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org Subject: STD 68, RFC 5234 on Augmented BNF for Syntax Specifications: ABNF From: rfc-editor@rfc-editor.org Message-Id: <20080201012414.CDB2910C7A9@bosco.isi.edu> Date: Thu, 31 Jan 2008 17:24:14 -0800 (PST) Cc: rfc-editor@rfc-editor.org X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: <ietf-announce.ietf.org> List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe> List-Post: <mailto:ietf-announce@ietf.org> List-Help: <mailto:ietf-announce-request@ietf.org?subject=help> List-Subscribe: <http://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ietf-announce-bounces@ietf.org Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. STD 68 RFC 5234 Title: Augmented BNF for Syntax Specifications: ABNF Author: D. Crocker, Ed., P. Overell Status: Standards Track Date: January 2008 Mailbox: dcrocker@bbiw.net, paul.overell@thus.net Pages: 16 Characters: 26359 Obsoletes: RFC4234 See Also: STD0068 I-D Tag: draft-crocker-rfc4234bis-01.txt URL: http://www.rfc-editor.org/rfc/rfc5234.txt Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS TRACK] This is now a 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 list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org http://www.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Thu Jan 31 17:22:55 2008 Return-Path: <ietf-announce-bounces@ietf.org> X-Original-To: ietfarch-ietf-announce-archive@core3.amsl.com Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D0BB528C1E9 for <ietfarch-ietf-announce-archive@core3.amsl.com>; Thu, 31 Jan 2008 17:22:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.442 X-Spam-Level: X-Spam-Status: No, score=-17.442 tagged_above=-999 required=5 tests=[AWL=0.157, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WeOlbBxNdkz5; Thu, 31 Jan 2008 17:22:55 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4E18E28C1C8; Thu, 31 Jan 2008 17:22:54 -0800 (PST) X-Original-To: ietf-announce@core3.amsl.com Delivered-To: ietf-announce@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1139228C133; Thu, 31 Jan 2008 17:22:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5R3SJTlZ5UcC; Thu, 31 Jan 2008 17:22:52 -0800 (PST) Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 7B6E328C1B0; Thu, 31 Jan 2008 17:22:49 -0800 (PST) Received: by bosco.isi.edu (Postfix, from userid 70) id 6F6CE10C7AB; Thu, 31 Jan 2008 17:24:23 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org Subject: RFC 5117 on RTP Topologies From: rfc-editor@rfc-editor.org Message-Id: <20080201012423.6F6CE10C7AB@bosco.isi.edu> Date: Thu, 31 Jan 2008 17:24:23 -0800 (PST) Cc: avt@ietf.org, rfc-editor@rfc-editor.org X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: <ietf-announce.ietf.org> List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe> List-Post: <mailto:ietf-announce@ietf.org> List-Help: <mailto:ietf-announce-request@ietf.org?subject=help> List-Subscribe: <http://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ietf-announce-bounces@ietf.org Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 5117 Title: RTP Topologies Author: M. Westerlund, S. Wenger Status: Informational Date: January 2008 Mailbox: magnus.westerlund@ericsson.com, stewe@stewe.org Pages: 21 Characters: 50293 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-avt-topologies-07.txt URL: http://www.rfc-editor.org/rfc/rfc5117.txt This document discusses multi-endpoint topologies used in Real-time Transport Protocol (RTP)-based environments. In particular, centralized topologies commonly employed in the video conferencing industry are mapped to the RTP terminology. This memo provides information for the Internet community. This document is a product of the Audio/Video Transport 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 list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org http://www.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Thu Jan 31 17:23:12 2008 Return-Path: <ietf-announce-bounces@ietf.org> X-Original-To: ietfarch-ietf-announce-archive@core3.amsl.com Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD2E028C1FB for <ietfarch-ietf-announce-archive@core3.amsl.com>; Thu, 31 Jan 2008 17:23:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.467 X-Spam-Level: X-Spam-Status: No, score=-17.467 tagged_above=-999 required=5 tests=[AWL=0.132, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZZ9g5TbPXSQ3; Thu, 31 Jan 2008 17:23:11 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 66CF728C1FF; Thu, 31 Jan 2008 17:23:04 -0800 (PST) X-Original-To: ietf-announce@core3.amsl.com Delivered-To: ietf-announce@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 16F4728C1FF for <ietf-announce@core3.amsl.com>; Thu, 31 Jan 2008 17:23:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nFw83EH3xJBK for <ietf-announce@core3.amsl.com>; Thu, 31 Jan 2008 17:23:02 -0800 (PST) Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id C322928C197 for <ietf-announce@ietf.org>; Thu, 31 Jan 2008 17:22:57 -0800 (PST) Received: by bosco.isi.edu (Postfix, from userid 70) id B67F010C7AD; Thu, 31 Jan 2008 17:24:31 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org Subject: RFC 5176 on Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS) From: rfc-editor@rfc-editor.org Message-Id: <20080201012431.B67F010C7AD@bosco.isi.edu> Date: Thu, 31 Jan 2008 17:24:31 -0800 (PST) Cc: radiusext@ops.ietf.org, rfc-editor@rfc-editor.org X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: <ietf-announce.ietf.org> List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe> List-Post: <mailto:ietf-announce@ietf.org> List-Help: <mailto:ietf-announce-request@ietf.org?subject=help> List-Subscribe: <http://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ietf-announce-bounces@ietf.org Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 5176 Title: Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS) Author: M. Chiba, G. Dommety, M. Eklund, D. Mitton, B. Aboba Status: Informational Date: January 2008 Mailbox: mchiba@cisco.com, gdommety@cisco.com, meklund@cisco.com, david@mitton.com, bernarda@microsoft.com Pages: 34 Characters: 79541 Obsoletes: RFC3576 See-Also: I-D Tag: draft-ietf-radext-rfc3576bis-13.txt URL: http://www.rfc-editor.org/rfc/rfc5176.txt This document describes a currently deployed extension to the Remote Authentication Dial In User Service (RADIUS) protocol, allowing dynamic changes to a user session, as implemented by network access server products. This includes support for disconnecting users and changing authorizations applicable to a user session. This memo provides information for the Internet community. This document is a product of the RADIUS EXTensions 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 list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org http://www.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Thu Jan 31 17:23:25 2008 Return-Path: <ietf-announce-bounces@ietf.org> X-Original-To: ietfarch-ietf-announce-archive@core3.amsl.com Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B83D228C263 for <ietfarch-ietf-announce-archive@core3.amsl.com>; Thu, 31 Jan 2008 17:23:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.16 X-Spam-Level: X-Spam-Status: No, score=-17.16 tagged_above=-999 required=5 tests=[AWL=-0.161, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ur4VBF+9eyQo; Thu, 31 Jan 2008 17:23:24 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 30E4428C201; Thu, 31 Jan 2008 17:23:17 -0800 (PST) X-Original-To: ietf-announce@core3.amsl.com Delivered-To: ietf-announce@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3F6A828C1FF; Thu, 31 Jan 2008 17:23:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d4wUrmF5GLFP; Thu, 31 Jan 2008 17:23:14 -0800 (PST) Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 965CD28C211; Thu, 31 Jan 2008 17:23:06 -0800 (PST) Received: by bosco.isi.edu (Postfix, from userid 70) id 88CC210C7AF; Thu, 31 Jan 2008 17:24:40 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org Subject: RFC 5101 on Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information From: rfc-editor@rfc-editor.org Message-Id: <20080201012440.88CC210C7AF@bosco.isi.edu> Date: Thu, 31 Jan 2008 17:24:40 -0800 (PST) Cc: ipfix@ietf.org, rfc-editor@rfc-editor.org X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: <ietf-announce.ietf.org> List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe> List-Post: <mailto:ietf-announce@ietf.org> List-Help: <mailto:ietf-announce-request@ietf.org?subject=help> List-Subscribe: <http://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ietf-announce-bounces@ietf.org Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 5101 Title: Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information Author: B. Claise, Ed. Status: Standards Track Date: January 2008 Mailbox: bclaise@cisco.com Pages: 63 Characters: 147196 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ipfix-protocol-26.txt URL: http://www.rfc-editor.org/rfc/rfc5101.txt This document specifies the IP Flow Information Export (IPFIX) protocol that serves for transmitting IP Traffic Flow information over the network. In order to transmit IP Traffic Flow information from an Exporting Process to an information Collecting Process, a common representation of flow data and a standard means of communicating them is required. This document describes how the IPFIX Data and Template Records are carried over a number of transport protocols from an IPFIX Exporting Process to an IPFIX Collecting Process. [STANDARDS TRACK] This document is a product of the IP Flow Information Export 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 list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org http://www.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Thu Jan 31 17:30:01 2008 Return-Path: <ietf-announce-bounces@ietf.org> X-Original-To: ietfarch-ietf-announce-archive@core3.amsl.com Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 73EE928C350 for <ietfarch-ietf-announce-archive@core3.amsl.com>; Thu, 31 Jan 2008 17:30:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.124 X-Spam-Level: X-Spam-Status: No, score=-17.124 tagged_above=-999 required=5 tests=[AWL=-0.125, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xt+KPaPCckDJ; Thu, 31 Jan 2008 17:30:00 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 15C2B28C242; Thu, 31 Jan 2008 17:23:21 -0800 (PST) X-Original-To: ietf-announce@core3.amsl.com Delivered-To: ietf-announce@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B28D28C23D; Thu, 31 Jan 2008 17:23:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uGiLm33HoVor; Thu, 31 Jan 2008 17:23:19 -0800 (PST) Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 97D6F28C1CD; Thu, 31 Jan 2008 17:23:14 -0800 (PST) Received: by bosco.isi.edu (Postfix, from userid 70) id 8CAA310C7B1; Thu, 31 Jan 2008 17:24:48 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org Subject: RFC 5102 on Information Model for IP Flow Information Export From: rfc-editor@rfc-editor.org Message-Id: <20080201012448.8CAA310C7B1@bosco.isi.edu> Date: Thu, 31 Jan 2008 17:24:48 -0800 (PST) Cc: ipfix@ietf.org, rfc-editor@rfc-editor.org X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: <ietf-announce.ietf.org> List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe> List-Post: <mailto:ietf-announce@ietf.org> List-Help: <mailto:ietf-announce-request@ietf.org?subject=help> List-Subscribe: <http://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ietf-announce-bounces@ietf.org Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 5102 Title: Information Model for IP Flow Information Export Author: J. Quittek, S. Bryant, B. Claise, P. Aitken, J. Meyer Status: Standards Track Date: January 2008 Mailbox: quittek@netlab.nec.de, stbryant@cisco.com, bclaise@cisco.com, paitken@cisco.com, jemeyer@paypal.com Pages: 171 Characters: 335617 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ipfix-info-15.txt URL: http://www.rfc-editor.org/rfc/rfc5102.txt This memo defines an information model for the IP Flow Information eXport (IPFIX) protocol. It is used by the IPFIX protocol for encoding measured traffic information and information related to the traffic Observation Point, the traffic Metering Process, and the Exporting Process. Although developed for the IPFIX protocol, the model is defined in an open way that easily allows using it in other protocols, interfaces, and applications. [STANDARDS TRACK] This document is a product of the IP Flow Information Export 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 list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org http://www.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Thu Jan 31 17:32:09 2008 Return-Path: <ietf-announce-bounces@ietf.org> X-Original-To: ietfarch-ietf-announce-archive@core3.amsl.com Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0987528C474 for <ietfarch-ietf-announce-archive@core3.amsl.com>; Thu, 31 Jan 2008 17:32:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.106 X-Spam-Level: X-Spam-Status: No, score=-17.106 tagged_above=-999 required=5 tests=[AWL=-0.107, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nrwdpCCScSgc; Thu, 31 Jan 2008 17:32:08 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CF8D628C279; Thu, 31 Jan 2008 17:23:41 -0800 (PST) X-Original-To: ietf-announce@core3.amsl.com Delivered-To: ietf-announce@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C769028C23A; Thu, 31 Jan 2008 17:23:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D3-0FuZ6R44p; Thu, 31 Jan 2008 17:23:40 -0800 (PST) Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 221D228C1FA; Thu, 31 Jan 2008 17:23:22 -0800 (PST) Received: by bosco.isi.edu (Postfix, from userid 70) id 1599B10C7B3; Thu, 31 Jan 2008 17:24:56 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org Subject: RFC 5103 on Bidirectional Flow Export Using IP Flow Information Export (IPFIX) From: rfc-editor@rfc-editor.org Message-Id: <20080201012456.1599B10C7B3@bosco.isi.edu> Date: Thu, 31 Jan 2008 17:24:56 -0800 (PST) Cc: ipfix@ietf.org, rfc-editor@rfc-editor.org X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: <ietf-announce.ietf.org> List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe> List-Post: <mailto:ietf-announce@ietf.org> List-Help: <mailto:ietf-announce-request@ietf.org?subject=help> List-Subscribe: <http://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ietf-announce-bounces@ietf.org Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 5103 Title: Bidirectional Flow Export Using IP Flow Information Export (IPFIX) Author: B. Trammell, E. Boschi Status: Standards Track Date: January 2008 Mailbox: bht@cert.org, elisa.boschi@hitachi-eu.com Pages: 24 Characters: 53534 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ipfix-biflow-05.txt URL: http://www.rfc-editor.org/rfc/rfc5103.txt This document describes an efficient method for exporting bidirectional flow (Biflow) information using the IP Flow Information Export (IPFIX) protocol, representing each Biflow using a single Flow Record. [STANDARDS TRACK] This document is a product of the IP Flow Information Export 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 list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org http://www.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Thu Jan 31 18:07:54 2008 Return-Path: <ietf-announce-bounces@ietf.org> X-Original-To: ietfarch-ietf-announce-archive@core3.amsl.com Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E18E128C2C4 for <ietfarch-ietf-announce-archive@core3.amsl.com>; Thu, 31 Jan 2008 18:07:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zTxVH3NsvicX; Thu, 31 Jan 2008 18:07:54 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0BFEB28C285; Thu, 31 Jan 2008 18:07:54 -0800 (PST) X-Original-To: ietf-announce@ietf.org Delivered-To: ietf-announce@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id 15D8528C27B; Thu, 31 Jan 2008 18:07:52 -0800 (PST) Mime-Version: 1.0 To: IETF Announcement list <ietf-announce@ietf.org> Cc: From: IETF Administrative Director <iad@ietf.org> Subject: IT Transition Message-Id: <20080201020752.15D8528C27B@core3.amsl.com> Date: Thu, 31 Jan 2008 18:07:52 -0800 (PST) X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: <ietf-announce.ietf.org> List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe> List-Post: <mailto:ietf-announce@ietf.org> List-Help: <mailto:ietf-announce-request@ietf.org?subject=help> List-Subscribe: <http://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ietf-announce-bounces@ietf.org Errors-To: ietf-announce-bounces@ietf.org All IT services have been transitioned. As previously reported, please bear in mind that the AMS setup is not the same as the NSS setup. Some changes were necessary as part of the transition. It is possible there will be some issues that need attention as the community begins to use the services in their new production environment. The good news is that all services, except jabber, are now available on both IPv4 and IPv6. This includes the web, ftp, email, and rsync for those who mirror internet-drafts. The status that you need to know is as follows. 1. Reminder, iab and iesg mailing lists have been moved to be in their respective domains. This may affect your filtering but should not effect distribution. 2. As it turns out we did not move the irtf mailing lists into irtf.org. In order to do this we need to be hosting the irtf.org web site for mailman to work properly. Since this site is an independent site we have set this aside for now. 3. We have also noticed that GMail.com is blocking the IETF servers' email delivery. They started this 5 minutes after email was enabled. We have already filed the appropriate reports and hope for a resolution in 24-48 hours. Please tell your friends on GMail.com that they are not getting IETF email. 4. Finally, site automation is not enabled at this time. This means that "static" web pages or files that are automatically generated, e.g., http://www.ietf.org/internet-drafts/1id-index.txt, are not current. This is a priority work item and will be completed as soon as possible. We would appreciate it if IETF participants would report any discrepancies or problems immediately to ietf-action@ietf.org as they examine web pages or services of importance to them. AMS will address all concerns as quickly as they can. We will keep the community informed if there are major concerns or delays. On behalf of AMS and the transition team thank you for your support and patience. Ray Pelletier IETF Administrative Director _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org http://www.ietf.org/mailman/listinfo/ietf-announce