IETF Process Evolution: PESCI team members
I've picked the following PESCI team members from the various volunteers and nominees: Harald Alvestrand Scott Brim Elwyn Davies Adrian Farrel Michael Richardson Thanks to everybody who was willing to serve at short notice. As a reminder, PESCI's immediate tasks are: - review recent discussions on IETF process changes - identify a concise set of goals and principles for process change - publish these for comment and seek IETF debate and rough consensus and the cutoff date for our first draft is October 17. As noted previously, the open mailing list is [EMAIL PROTECTED] (see https://www1.ietf.org/mailman/listinfo/pesci-discuss) You can write privately to the team at [EMAIL PROTECTED] If you've lost track of the background to PESCI, see http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg01567.html ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
BCP 111, RFC 4181 on Guidelines for Authors and Reviewers of MIB Documents
A new Request for Comments is now available in online RFC libraries. BCP 111 RFC 4181 Title: Guidelines for Authors and Reviewers of MIB Documents Author(s): C. Heard, Ed. Status: Best Current Practice Date: September 2005 Mailbox:[EMAIL PROTECTED] Pages: 42 Characters: 102521 SeeAlso:BCP0111 I-D Tag:draft-ietf-ops-mib-review-guidelines-04.txt URL:ftp://ftp.rfc-editor.org/in-notes/rfc4181.txt This memo provides guidelines for authors and reviewers of IETF standards-track specifications containing MIB modules. Applicable portions may be used as a basis for reviews of other MIB documents. This document is a product of the Operations Management Open Area of the IETF. 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 list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to [EMAIL PROTECTED] Requests to be added to or deleted from the RFC-DIST distribution list should be sent to [EMAIL PROTECTED] Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to [EMAIL PROTECTED] with the message body help: ways_to_get_rfcs. For example: To: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to [EMAIL PROTECTED] Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. ftp://ftp.isi.edu/in-notes/rfc4181.txt ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
RFC 4165 on Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Peer-to-Peer Adaptation Layer (M2PA)
A new Request for Comments is now available in online RFC libraries. RFC 4165 Title: Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Peer-to-Peer Adaptation Layer (M2PA) Author(s): T. George, B. Bidulock, R. Dantu, H. Schwarzbauer, K. Morneault Status: Standards Track Date: September 2005 Mailbox:[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Pages: 53 Characters: 114669 Updates/Obsoletes/SeeAlso:None I-D Tag:draft-ietf-sigtran-m2pa-13.txt URL:ftp://ftp.rfc-editor.org/in-notes/rfc4165.txt This document defines a protocol supporting the transport of Signaling System Number 7 (SS7) Message Transfer Part (MTP) Level 3 signaling messages over Internet Protocol (IP) using the services of the Stream Control Transmission Protocol (SCTP). This protocol would be used between SS7 Signaling Points using the MTP Level 3 protocol. The SS7 Signaling Points may also use standard SS7 links using the SS7 MTP Level 2 to provide transport of MTP Level 3 signaling messages. The protocol operates in a manner similar to MTP Level 2 so as to provide peer-to-peer communication between SS7 endpoints. This document is a product of the Signaling Transport Working Group of the IETF. This is now a Proposed Standard Protocol. 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 [EMAIL PROTECTED] Requests to be added to or deleted from the RFC-DIST distribution list should be sent to [EMAIL PROTECTED] Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to [EMAIL PROTECTED] with the message body help: ways_to_get_rfcs. For example: To: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to [EMAIL PROTECTED] Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. ftp://ftp.isi.edu/in-notes/rfc4165.txt ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
