[Adslmib] RFC 6765 on xDSL Multi-Pair Bonding (G.Bond) MIB

rfc-editor@rfc-editor.org Mon, 25 February 2013 15:11 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: adslmib@ietfa.amsl.com
Delivered-To: adslmib@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B56621F9481; Mon, 25 Feb 2013 07:11:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.05
X-Spam-Level:
X-Spam-Status: No, score=-102.05 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cjZuGMDFD2fE; Mon, 25 Feb 2013 07:11:20 -0800 (PST)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id F263121F946B; Mon, 25 Feb 2013 07:11:19 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 8D13C72E114; Mon, 25 Feb 2013 07:10:11 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130225151011.8D13C72E114@rfc-editor.org>
Date: Mon, 25 Feb 2013 07:10:11 -0800
Cc: adslmib@ietf.org, rfc-editor@rfc-editor.org
Subject: [Adslmib] RFC 6765 on xDSL Multi-Pair Bonding (G.Bond) MIB
X-BeenThere: adslmib@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: ADSLMIB <adslmib.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/adslmib>, <mailto:adslmib-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/adslmib>
List-Post: <mailto:adslmib@ietf.org>
List-Help: <mailto:adslmib-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/adslmib>, <mailto:adslmib-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 15:11:20 -0000

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

        
        RFC 6765

        Title:      xDSL Multi-Pair Bonding (G.Bond) MIB 
        Author:     E. Beili, M. Morgenstern
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2013
        Mailbox:    edward.beili@actelis.com, 
                    moti.morgenstern@ecitele.com
        Pages:      73
        Characters: 154301
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-adslmib-gbond-mib-11.txt

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

This document defines a Management Information Base (MIB) module for
use with network management protocols in TCP/IP-based internets.
This document defines an extension to the Interfaces Group MIB with a
set of common objects for managing multi-pair bonded Digital
Subscriber Line (xDSL) interfaces, as defined in ITU-T
Recommendations G.998.1, G.998.2, and G.998.3.  The textual
conventions defining the bonding schemes are contained in a separate
MIB module maintained by Internet Assigned Numbers Authority (IANA).
The MIB modules specific to each bonding technology are defined in
G9981-MIB, G9982-MIB, and G9983-MIB, respectively.

This document is a product of the ADSL MIB Working Group of the IETF.

This is now a Proposed Standard.

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-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC