From cfinss@dial.pipex.com Fri Mar 13 11:50:58 2009 Return-Path: X-Original-To: ietfmibs@core3.amsl.com Delivered-To: ietfmibs@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E481E3A6B26 for ; Fri, 13 Mar 2009 11:50:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.103 X-Spam-Level: X-Spam-Status: No, score=-2.103 tagged_above=-999 required=5 tests=[AWL=0.496, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MvCmim9M3M9H for ; Fri, 13 Mar 2009 11:50:58 -0700 (PDT) Received: from mk-outboundfilter-5.mail.uk.tiscali.com (mk-outboundfilter-5.mail.uk.tiscali.com [212.74.114.1]) by core3.amsl.com (Postfix) with ESMTP id CC1AF3A6AA4 for ; Fri, 13 Mar 2009 11:50:57 -0700 (PDT) X-Trace: 139967101/mk-outboundfilter-5.mail.uk.tiscali.com/PIPEX/$PIPEX-ACCEPTED/pipex-customers/62.188.19.55/None/cfinss@dial.pipex.com X-SBRS: None X-RemoteIP: 62.188.19.55 X-IP-MAIL-FROM: cfinss@dial.pipex.com X-MUA: Microsoft Outlook Express 6.00.2800.1106Produced By Microsoft MimeOLE V6.00.2800.1106 X-IP-BHB: Once X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhsFAPNHukk+vBM3/2dsb2JhbACDJEOKDcJzB4N3Bg X-IronPort-AV: E=Sophos;i="4.38,359,1233532800"; d="scan'208";a="139967101" X-IP-Direction: IN Received: from 1cust55.tnt2.lnd3.gbr.da.uu.net (HELO allison) ([62.188.19.55]) by smtp.pipex.tiscali.co.uk with SMTP; 13 Mar 2009 18:51:33 +0000 Message-ID: <004201c9a404$1b173520$0601a8c0@allison> From: "tom.petch" To: "Randy Presuhn" , References: <007301c9983c$34e125c0$6801a8c0@oemcomputer><006b01c9989b$b09e7fa0$6801a8c0@oemcomputer> <01d301c99912$9954c3a0$6801a8c0@oemcomputer> Date: Fri, 13 Mar 2009 18:49:39 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: Re: [IETFMIBS] Message Encoding for SNMPv3 X-BeenThere: ietfmibs@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: "tom.petch" List-Id: IETF MIB Discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2009 18:50:59 -0000 ----- Original Message ----- From: "Randy Presuhn" To: Sent: Friday, February 27, 2009 8:35 PM Subject: Re: [IETFMIBS] Message Encoding for SNMPv3 > From: "Hamid Mukhtar" > > To: "Randy Presuhn" > > Cc: > > Sent: Thursday, February 26, 2009 11:55 PM > > Subject: Re: [IETFMIBS] Message Encoding for SNMPv3 > > > > On Fri, Feb 27, 2009 at 2:24 PM, Randy Presuhn > > wrote: > > > Hi - > > > > > >> From: "Hamid Mukhtar" > > >> To: "Randy Presuhn" > > >> Cc: > > >> Sent: Thursday, February 26, 2009 5:08 PM > > >> Subject: Re: [IETFMIBS] Message Encoding for SNMPv3 > > > ... > > >> Just for my knowledge, Is the use of proxy-forwarder applications > > >> restricted to forwarding the four basic types only or they can be used > > >> for other proxy related applications too. > > > > > > I'm not sure what you mean by "the four basic types". > > > > > > > RFC 3413 in its section 3.5 identifies four basic types of proxy > > forwarder applications. > > No, it does not. Section 3.5 describes the handling of four message > types to be handled by a proxy application. > > > You specified that the proxy forwarder (as > > defined in RFC 3413) uses a "narrow sense" of the term proxy. For my > > understanding I just need to clarify what you mean by narrow sense. Do > > you mean that the only translation a proxy forwarder can do as an > > intermediate entity is between SNMP versions. Thus the SNMPv3 proxy > > forwarders cannot be used to translate between SNMP and non-SNMP > > protocols (for instance a protocol which uses XML instead of BER > > encoding). > > See RFC 3413 section 1.5. This paragraph sums it up: > > To avoid such confusion, this document uses the term "proxy" with a > much more tightly defined meaning. The term "proxy" is used in this > document to refer to a proxy forwarder application which forwards > either SNMP messages without regard for what managed objects are > contained within those messages. This definition is most closely > related to the first definition above. Note, however, that in the > SNMP architecture [RFC3411], a proxy forwarder is actually an > application, and need not be associated with what is traditionally > thought of as an SNMP agent. Randy I read that and thought - well it may be right but is it grammatical? Where is the 'or' to the 'either'? RFC2263 has " either SNMP requests, notifications, and responses without regard for what managed objects are contained within requests or notifications." which is somewhat less ungrammatical. RFC1905 has a proxy but not that wording draft-ietf-snmpv3-appl-01.txt is the same as RFC2263 but snmpv3-appl-00.txt has " either SNMP requests or notifications without regard for what managed" Now it makes sense:-) Tom Petch > Randy > > _______________________________________________ > IETFMIBS mailing list > IETFMIBS@ietf.org > https://www.ietf.org/mailman/listinfo/ietfmibs From ietfdbh@comcast.net Mon Mar 23 20:29:48 2009 Return-Path: X-Original-To: ietfmibs@core3.amsl.com Delivered-To: ietfmibs@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C51B73A6B15 for ; Mon, 23 Mar 2009 20:29:48 -0700 (PDT) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER, Non-encoded 8-bit data (char AE hex): Subject: SALE 73% OFF on VIAGRA\256 \n X-Spam-Flag: NO X-Spam-Score: -19.564 X-Spam-Level: X-Spam-Status: No, score=-19.564 tagged_above=-999 required=5 tests=[BAYES_99=3.5, DRUGS_ERECTILE=1, DRUG_ED_CAPS=0.322, GB_I_LETTER=-2, GB_PHARMACY=1, HELO_EQ_DSL=1.129, HELO_EQ_PL=1.135, HOST_EQ_PL=1.95, HTML_FONT_FACE_BAD=0.884, HTML_IMAGE_RATIO_04=0.172, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_HTML_ONLY=1.457, MONEY_BACK=0.001, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, SARE_UNI=0.591, SUBJECT_NEEDS_ENCODING=0.001, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c5WL2AstT7lW for ; Mon, 23 Mar 2009 20:29:48 -0700 (PDT) Received: from gak178.internetdsl.tpnet.pl (gak178.internetdsl.tpnet.pl [83.12.10.178]) by core3.amsl.com (Postfix) with SMTP id 6AB8B3A68EB for ; Mon, 23 Mar 2009 20:29:47 -0700 (PDT) Content-Return: allowed X-Mailer: CME-V6.5.4.3; MSN Received: (qmail 13253 by uid 335); Tue, 24 Mar 2009 04:30:39 +0100 Message-Id: <20090324053039.13255.qmail@gak178.internetdsl.tpnet.pl> To: Subject: SALE 73% OFF on VIAGRA® From: MIME-Version: 1.0 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Date: Mon, 23 Mar 2009 20:29:47 -0700 (PDT) X-BeenThere: ietfmibs@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF MIB Discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Mar 2009 03:29:48 -0000 Victoria's Secret
Must-Have Looks For Summer. If you are unable to see the images in this email, please click here.
Catalogue Quick Order Forward to a Friend



SPECIAL OFFER DETAILS:
*Easy Monthly Payments *No Risk 30-Day Money Back Guarantee

This special offer is available for only 3 days. Discounts are included in final prices.


You are receiving this email because you have subscribed to the Pharmacy® newsletter with the following address: ietfmibs@ietf.org.

Unsubscribe | Privacy policy | Contact us

© 2008 Pharmacy All rights reserved.