
From nobody Wed Apr 30 05:49:23 2014
Return-Path: <adamson@us.ibm.com>
X-Original-To: ietfmibs@ietfa.amsl.com
Delivered-To: ietfmibs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3F341A6F71 for <ietfmibs@ietfa.amsl.com>; Wed, 30 Apr 2014 05:49:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.151
X-Spam-Level: 
X-Spam-Status: No, score=-6.151 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XT3tUq42Abac for <ietfmibs@ietfa.amsl.com>; Wed, 30 Apr 2014 05:49:06 -0700 (PDT)
Received: from e38.co.us.ibm.com (e38.co.us.ibm.com [32.97.110.159]) by ietfa.amsl.com (Postfix) with ESMTP id EC7AA1A6F70 for <ietfmibs@ietf.org>; Wed, 30 Apr 2014 05:49:05 -0700 (PDT)
Received: from /spool/local by e38.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietfmibs@ietf.org> from <adamson@us.ibm.com>; Wed, 30 Apr 2014 06:49:04 -0600
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e38.co.us.ibm.com (192.168.1.138) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Wed, 30 Apr 2014 06:49:02 -0600
Received: from b03cxnp08027.gho.boulder.ibm.com (b03cxnp08027.gho.boulder.ibm.com [9.17.130.19]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 808081FF003D for <ietfmibs@ietf.org>; Wed, 30 Apr 2014 06:49:01 -0600 (MDT)
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by b03cxnp08027.gho.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s3UCm6Kp7340332 for <ietfmibs@ietf.org>; Wed, 30 Apr 2014 14:48:14 +0200
Received: from d03av02.boulder.ibm.com (localhost [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s3UCmSmc008769 for <ietfmibs@ietf.org>; Wed, 30 Apr 2014 06:48:29 -0600
Received: from d03nm118.boulder.ibm.com (d03nm118.boulder.ibm.com [9.63.40.219]) by d03av02.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s3UCmSxp008100 for <ietfmibs@ietf.org>; Wed, 30 Apr 2014 06:48:28 -0600
X-KeepSent: CD6DB2DE:EBE3065B-87257CCA:004609D1; type=4; name=$KeepSent
To: ietfmibs@ietf.org
X-Mailer: Lotus Notes Release 8.5.3FP5SHF238 December 19, 2013
Message-ID: <OFCD6DB2DE.EBE3065B-ON87257CCA.004609D1-85257CCA.004650F7@us.ibm.com>
From: Kristine Adamson <adamson@us.ibm.com>
Date: Wed, 30 Apr 2014 08:48:03 -0400
X-MIMETrack: Serialize by Router on D03NM118/03/M/IBM(Release 9.0.1IF1|November 26, 2013) at 04/30/2014 06:48:28
MIME-Version: 1.0
Content-type: multipart/alternative;  Boundary="0__=08BBF659DFD58F418f9e8a93df938690918c08BBF659DFD58F41"
Content-Disposition: inline
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14043012-1344-0000-0000-0000013EDFBA
Archived-At: http://mailarchive.ietf.org/arch/msg/ietfmibs/W60supBgtpiNj6oUsHMs0rdyhN8
Subject: [IETFMIBS] Notifications - can MIB objects be added to an existing notification?
X-BeenThere: ietfmibs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF MIB Discussion list <ietfmibs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietfmibs>, <mailto:ietfmibs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietfmibs/>
List-Post: <mailto:ietfmibs@ietf.org>
List-Help: <mailto:ietfmibs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietfmibs>, <mailto:ietfmibs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 12:49:09 -0000

--0__=08BBF659DFD58F418f9e8a93df938690918c08BBF659DFD58F41
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: quoted-printable



Hello,
   Can someone tell me if MIB objects can be added to an existing
notification?  I have looked at RFC2578 and RFC4181 but I cannot easily=

determine from these documents whether this is permissible.  If MIB obj=
ects
can be added to a notification, can you tell me where this is documente=
d?

Thanks for your time,


Kristine Adamson
IBM z/OS Communications Server: TCP/IP Development
Phone: (919) 254-7911   T/L 444-7911
Internet e-mail:adamson@us.ibm.com=

--0__=08BBF659DFD58F418f9e8a93df938690918c08BBF659DFD58F41
Content-type: text/html; charset=US-ASCII
Content-Disposition: inline
Content-transfer-encoding: quoted-printable

<html><body>
<p><font size=3D"2" face=3D"sans-serif">Hello,</font><br>
<font size=3D"2" face=3D"sans-serif">&nbsp; &nbsp;Can someone tell me i=
f MIB objects can be added to an existing notification? &nbsp;I have lo=
oked at RFC2578 and RFC4181 but I cannot easily determine from these do=
cuments whether this is permissible. &nbsp;If MIB objects can be added =
to a notification, can you tell me where this is documented?</font><br>=

<br>
<font size=3D"2" face=3D"sans-serif">Thanks for your time, </font><br>
<font size=3D"2" face=3D"sans-serif"><br>
<br>
Kristine Adamson<br>
IBM z/OS Communications Server: TCP/IP Development<br>
Phone: (919) 254-7911 &nbsp; T/L 444-7911<br>
Internet e-mail:adamson@us.ibm.com<br>
</font></body></html>=

--0__=08BBF659DFD58F418f9e8a93df938690918c08BBF659DFD58F41--


From nobody Wed Apr 30 05:55:10 2014
Return-Path: <dromasca@avaya.com>
X-Original-To: ietfmibs@ietfa.amsl.com
Delivered-To: ietfmibs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E7701A0829 for <ietfmibs@ietfa.amsl.com>; Wed, 30 Apr 2014 05:55:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.25
X-Spam-Level: 
X-Spam-Status: No, score=-3.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id upeJgZOLb5DW for <ietfmibs@ietfa.amsl.com>; Wed, 30 Apr 2014 05:55:07 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 1C6561A081B for <ietfmibs@ietf.org>; Wed, 30 Apr 2014 05:55:07 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgoFAIvxYFPGmAcV/2dsb2JhbABWA4JCIyFPV7xkIAGHPYEjFnSCJQEBAQEDEhtKEAICAQgNBAQBAQsdBxsXFAkIAgQBEggaiB8BmwSuKhcEjhwhFgERgh12gRUEiUuWZothgXKBP4Ir
X-IronPort-AV: E=Sophos; i="4.97,958,1389762000"; d="scan'208,217"; a="60254013"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by co300216-co-outbound.net.avaya.com with ESMTP; 30 Apr 2014 08:55:05 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 30 Apr 2014 08:39:10 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.03.0174.001; Wed, 30 Apr 2014 14:55:03 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Kristine Adamson <adamson@us.ibm.com>, "ietfmibs@ietf.org" <ietfmibs@ietf.org>
Thread-Topic: [IETFMIBS] Notifications - can MIB objects be added to an existing	notification?
Thread-Index: AQHPZHKj4zmQRx/3Q0OgS/KjhasB+5sqHcSg
Date: Wed, 30 Apr 2014 12:55:02 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C7CCD88@AZ-FFEXMB04.global.avaya.com>
References: <OFCD6DB2DE.EBE3065B-ON87257CCA.004609D1-85257CCA.004650F7@us.ibm.com>
In-Reply-To: <OFCD6DB2DE.EBE3065B-ON87257CCA.004609D1-85257CCA.004650F7@us.ibm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA5C7CCD88AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietfmibs/Sh1xwuB5fUt53agN0FLHrUFKHB4
Subject: Re: [IETFMIBS] Notifications - can MIB objects be added to an existing	notification?
X-BeenThere: ietfmibs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF MIB Discussion list <ietfmibs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietfmibs>, <mailto:ietfmibs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietfmibs/>
List-Post: <mailto:ietfmibs@ietf.org>
List-Help: <mailto:ietfmibs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietfmibs>, <mailto:ietfmibs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 12:55:09 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C7CCD88AZFFEXMB04globa_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

See section 8.1 in RFC 2578:


=D8  Note that an agent is allowed, at its own discretion, to append as

=D8     many additional objects as it considers useful to the end of the

=D8     notification (i.e., after the objects defined by the OBJECTS clause=
).

=D8


Regards,

Dan


From: IETFMIBS [mailto:ietfmibs-bounces@ietf.org] On Behalf Of Kristine Ada=
mson
Sent: Wednesday, April 30, 2014 3:48 PM
To: ietfmibs@ietf.org
Subject: [IETFMIBS] Notifications - can MIB objects be added to an existing=
 notification?


Hello,
   Can someone tell me if MIB objects can be added to an existing notificat=
ion?  I have looked at RFC2578 and RFC4181 but I cannot easily determine fr=
om these documents whether this is permissible.  If MIB objects can be adde=
d to a notification, can you tell me where this is documented?

Thanks for your time,


Kristine Adamson
IBM z/OS Communications Server: TCP/IP Development
Phone: (919) 254-7911   T/L 444-7911
Internet e-mail:adamson@us.ibm.com

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C7CCD88AZFFEXMB04globa_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:321275556;
	mso-list-type:hybrid;
	mso-list-template-ids:1554042998 901185066 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:\F0D8;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:Arial;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">See section 8.1 in RFC 25=
78:
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"font-size:10.0pt;font-family:W=
ingdings"><span style=3D"mso-list:Ignore">=D8<span style=3D"font:7.0pt &quo=
t;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">Note that an agent is all=
owed, at its own discretion, to append as<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"font-size:10.0pt;font-family:W=
ingdings"><span style=3D"mso-list:Ignore">=D8<span style=3D"font:7.0pt &quo=
t;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;many ad=
ditional objects as it considers useful to the end of the<o:p></o:p></span>=
</p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"font-size:10.0pt;font-family:W=
ingdings"><span style=3D"mso-list:Ignore">=D8<span style=3D"font:7.0pt &quo=
t;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;notific=
ation (i.e., after the objects defined by the OBJECTS clause).<o:p></o:p></=
span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"font-size:10.0pt;font-family:W=
ingdings"><span style=3D"mso-list:Ignore">=D8<span style=3D"font:7.0pt &quo=
t;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Regards,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Dan<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> IETFMIBS=
 [mailto:ietfmibs-bounces@ietf.org]
<b>On Behalf Of </b>Kristine Adamson<br>
<b>Sent:</b> Wednesday, April 30, 2014 3:48 PM<br>
<b>To:</b> ietfmibs@ietf.org<br>
<b>Subject:</b> [IETFMIBS] Notifications - can MIB objects be added to an e=
xisting notification?<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans=
-serif&quot;">Hello,</span><br>
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;">&nbsp; &nbsp;Can someone tell me if MIB objects can be added to =
an existing notification? &nbsp;I have looked at RFC2578 and RFC4181 but I =
cannot easily determine from these documents whether this is permissible.
 &nbsp;If MIB objects can be added to a notification, can you tell me where=
 this is documented?</span><br>
<br>
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;">Thanks for your time,
</span><br>
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;"><br>
<br>
Kristine Adamson<br>
IBM z/OS Communications Server: TCP/IP Development<br>
Phone: (919) 254-7911 &nbsp; T/L 444-7911<br>
Internet e-mail:adamson@us.ibm.com</span><o:p></o:p></p>
</div>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C7CCD88AZFFEXMB04globa_--


From nobody Wed Apr 30 06:02:00 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: ietfmibs@ietfa.amsl.com
Delivered-To: ietfmibs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C24151A081B for <ietfmibs@ietfa.amsl.com>; Wed, 30 Apr 2014 06:01:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.151
X-Spam-Level: 
X-Spam-Status: No, score=-10.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kCMrTlQMnpRg for <ietfmibs@ietfa.amsl.com>; Wed, 30 Apr 2014 06:01:36 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) by ietfa.amsl.com (Postfix) with ESMTP id E76861A0684 for <ietfmibs@ietf.org>; Wed, 30 Apr 2014 06:01:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3008; q=dns/txt; s=iport; t=1398862895; x=1400072495; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=SYZDtugLlKP4jycpTkWkmzo/FTO6Wn6gDI4R5OSXvN8=; b=kuni2VtbG6eQA5vUU0oUUEkoXrGtcT33b2VKpI+i6vzeE1XLfNdRaoeH Gf4reciS8YPPn3YWeerQsfhIb/H1cAYXPTTJWESRssX1Kpctijvki3WJM 8RyAJ8G9mkWElRxA6vh0C8nT9KJ+ofF9sXcGodND+/mZrqthcAOPHiQQG U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqQEAPLyYFOtJssW/2dsb2JhbABWA4NVvVsBhmxRgTh0giYBAQQBAQFrCRACCwQdJQ8CCgwwBgEMBgIBAYg9DckhEwQEjj0XEYQoBJknhmKMCYFygUE7
X-IronPort-AV: E=Sophos; i="4.97,958,1389744000"; d="scan'208,217"; a="28213800"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 30 Apr 2014 13:01:34 +0000
Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s3UD1XHh008816; Wed, 30 Apr 2014 13:01:33 GMT
Message-ID: <5360F42D.40408@cisco.com>
Date: Wed, 30 Apr 2014 15:01:33 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Kristine Adamson <adamson@us.ibm.com>, ietfmibs@ietf.org
References: <OFCD6DB2DE.EBE3065B-ON87257CCA.004609D1-85257CCA.004650F7@us.ibm.com>
In-Reply-To: <OFCD6DB2DE.EBE3065B-ON87257CCA.004609D1-85257CCA.004650F7@us.ibm.com>
Content-Type: multipart/alternative; boundary="------------060800050204090308040305"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietfmibs/BOPvYdbZTDpHVDG3eA54D9R59DA
Subject: Re: [IETFMIBS] Notifications - can MIB objects be added to an existing notification?
X-BeenThere: ietfmibs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF MIB Discussion list <ietfmibs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietfmibs>, <mailto:ietfmibs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietfmibs/>
List-Post: <mailto:ietfmibs@ietf.org>
List-Help: <mailto:ietfmibs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietfmibs>, <mailto:ietfmibs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 13:01:44 -0000

This is a multi-part message in MIME format.
--------------060800050204090308040305
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Kristine,

I believe that RFC 2981 allows that.

Regards, Benoit
>
> Hello,
>    Can someone tell me if MIB objects can be added to an existing 
> notification?  I have looked at RFC2578 and RFC4181 but I cannot 
> easily determine from these documents whether this is permissible.  If 
> MIB objects can be added to a notification, can you tell me where this 
> is documented?
>
> Thanks for your time,
>
>
> Kristine Adamson
> IBM z/OS Communications Server: TCP/IP Development
> Phone: (919) 254-7911   T/L 444-7911
> Internet e-mail:adamson@us.ibm.com
>
>
> _______________________________________________
> IETFMIBS mailing list
> IETFMIBS@ietf.org
> https://www.ietf.org/mailman/listinfo/ietfmibs


--------------060800050204090308040305
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Kristine,<br>
      <br>
      I believe that RFC 2981 allows that.<br>
      <br>
      Regards, Benoit<br>
    </div>
    <blockquote
cite="mid:OFCD6DB2DE.EBE3065B-ON87257CCA.004609D1-85257CCA.004650F7@us.ibm.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <p><font face="sans-serif" size="2">Hello,</font><br>
        <font face="sans-serif" size="2">&nbsp; &nbsp;Can someone tell me if MIB
          objects can be added to an existing notification? &nbsp;I have
          looked at RFC2578 and RFC4181 but I cannot easily determine
          from these documents whether this is permissible. &nbsp;If MIB
          objects can be added to a notification, can you tell me where
          this is documented?</font><br>
        <br>
        <font face="sans-serif" size="2">Thanks for your time, </font><br>
        <font face="sans-serif" size="2"><br>
          <br>
          Kristine Adamson<br>
          IBM z/OS Communications Server: TCP/IP Development<br>
          Phone: (919) 254-7911 &nbsp; T/L 444-7911<br>
          Internet <a class="moz-txt-link-abbreviated" href="mailto:e-mail:adamson@us.ibm.com">e-mail:adamson@us.ibm.com</a><br>
        </font>
        <br>
      </p>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
IETFMIBS mailing list
<a class="moz-txt-link-abbreviated" href="mailto:IETFMIBS@ietf.org">IETFMIBS@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ietfmibs">https://www.ietf.org/mailman/listinfo/ietfmibs</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------060800050204090308040305--

