From veerendranatharv@huawei.com Thu Jun 27 23:58:04 2013 Return-Path: X-Original-To: rip@ietfa.amsl.com Delivered-To: rip@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 621B621F9D7A for ; Thu, 27 Jun 2013 23:58:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.999 X-Spam-Level: X-Spam-Status: No, score=-3.999 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id erhaPXSZr-9Y for ; Thu, 27 Jun 2013 23:57:53 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 477FC21F9D5F for ; Thu, 27 Jun 2013 23:57:53 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AUM08063; Fri, 28 Jun 2013 06:57:51 +0000 (GMT) Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 28 Jun 2013 07:56:52 +0100 Received: from SZXEML455-HUB.china.huawei.com (10.82.67.198) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 28 Jun 2013 07:57:50 +0100 Received: from blrprnc06ns (10.18.96.95) by SZXEML455-HUB.china.huawei.com (10.82.67.198) with Microsoft SMTP Server id 14.1.323.7; Fri, 28 Jun 2013 14:57:45 +0800 From: Vallem Veerendranatha Reddy To: Date: Fri, 28 Jun 2013 12:27:44 +0530 Message-ID: <000001ce73cc$cadb85f0$609291d0$@com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01CE73FA.E493C1F0" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac5zzMoQUihViRwcRZ+5z12nY/sXrg== Content-Language: en-us X-Originating-IP: [10.18.96.95] X-CFilter-Loop: Reflected Subject: [rip] Regarding RIP authentication support through MIB X-BeenThere: rip@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Routing Information Protocol Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jun 2013 06:58:04 -0000 ------=_NextPart_000_0001_01CE73FA.E493C1F0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Dear All, As per RFC 4822 (RIPv2 cryptographic authentication), RIP can support multiple crypto authentications along with MD5 authentication like HMAC-SHA256. But to get the authentication information through SNMP (MIB), as per RFC 1724 , there is no filed to support new authentications. Please let us know whether any new updated INA values for new authentication algorithms or 3 can be modified to "crypto" (same as OSPF). rip2IfConfAuthType OBJECT-TYPE SYNTAX INTEGER { noAuthentication (1), simplePassword (2), md5 (3) } MAX-ACCESS read-create Thanks & Regards, Veerendranath Huawei Technologies India Pvt Ltd. Leela Galleria, Banaglore,India. ------=_NextPart_000_0001_01CE73FA.E493C1F0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear = All,

As per RFC 4822 (RIPv2 = cryptographic authentication), RIP can support multiple crypto = authentications along with MD5 authentication like = HMAC-SHA256.

But to get the = authentication information through SNMP (MIB), as per RFC 1724 , there = is no filed to support new authentications.

Please let us know whether any new updated INA values = for new authentication algorithms or 3 can be modified to = “crypto” (same as OSPF).

rip2IfConfAuthType = OBJECT-TYPE

SYNTAX = INTEGER {

&= nbsp; noAuthentication = (1),

&= nbsp; simplePassword = (2),

&= nbsp; md5 = (3)

&= nbsp; }

MAX-ACCESS = read-create

Thanks & = Regards,

Veerendranath =

Huawei Technologies = India Pvt Ltd.

Leela = Galleria,

Banaglore,India.

------=_NextPart_000_0001_01CE73FA.E493C1F0--