Re: RFC 4319 on Definitions of Managed Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair High-Speed Digital Subscriber Line (SHDSL) Lines
Rajesh Abbi <[email protected]>
| Newsgroups | gmane.ietf.adslmib |
|---|---|
| Message-ID | <[email protected]> |
Great job Clay. Thanks to Bob for shepherding this through the long drawn out process ... -Rajesh Clay Sikes wrote: > Today, RFC 4319, Definitions of Managed Objects for High Bit-Rate DSL > - 2nd generation (HDSL2) and Single-Pair High-Speed Digital Subscriber > Line (SHDSL) Lines, was announced. I want to take an opportunity to > thank some folks who were instrumental in getting the I-D to an RFC. > > Bob Ray and Rajesh Abbi for allowing me to take editorial leadership > on the I-D. Bob was my mentor and encourager through out the > process. Bert Wijnen and Randy Presuhn for their extensive review > which provided a ton of comments and guidance on change. Michael > Sneed and Bob Ray (Bob put on many hats in the process) for their > Working Group Chair support. C.M. Heard for his MIB Doctor Review and > guidance, particularly with the Conformance and Compliance sections. > Finally, the RFC Editor, who at least one was Alba Regalado-Palacios; > they answered may questions and did an amazing job with the final edit. > > I have thoroughly enjoyed this opportunity and am thankful for all the > neat stuff I learned. > > Thanks to all! > > - Clay Sikes > > > On 12/15/2005 8:39 PM, [email protected] wrote: > >>A new Request for Comments is now available in online RFC libraries. >> >> >> RFC 4319 >> >> Title: Definitions of Managed Objects for >> High Bit-Rate DSL - 2nd generation (HDSL2) and >> Single-Pair High-Speed Digital Subscriber Line >> (SHDSL) Lines >> Author(s): C. Sikes, B. Ray, R. Abbi >> Status: Standards Track >> Date: December 2005 >> Mailbox: [email protected], [email protected], >> [email protected] >> Pages: 75 >> Characters: 146995 >> Obsoletes: 3276 >> >> I-D Tag: draft-ietf-adslmib-gshdslbis-11.txt >> >> URL: ftp://ftp.rfc-editor.org/in-notes/rfc4319.txt >> >> >>This document defines a Management Information Base (MIB) module for >>use with network management protocols in the Internet community. In >>particular, it describes objects used for managing High Bit-Rate >>Digital Subscriber Line (DSL) - 2nd generation (HDSL2) and >>Single-Pair High-Speed Digital Subscriber Line (SHDSL) interfaces. >>This document introduces extensions to several objects and textual >>conventions defined in HDSL2-SHDSL-Line MIB (RFC 3276). This >>document obsoletes RFC 3276. >> >>This document is a product of the ADSL MIB 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. >> >> >>------------------------------------------------------------------------ >> >>_______________________________________________ >>Adslmib mailing list >>[email protected] >>https://www1.ietf.org/mailman/listinfo/adslmib >> >> >------------------------------------------------------------------------ > >_______________________________________________ >Adslmib mailing list >[email protected] >https://www1.ietf.org/mailman/listinfo/adslmib > > _______________________________________________ Adslmib mailing list [email protected] https://www1.ietf.org/mailman/listinfo/adslmib