RE: wg review of draft-ietf-ipcdn-docsisevent-mib-03.txt

Nakanishi Greg-MGI8179 <[email protected]>
Newsgroups gmane.ietf.ipcdn
Message-ID <D5A7E45D575DD61180130002A5DB377C05FA43F3@ca25exm01>
OK, will change the object names to end in 'Notification' in the next rev of the draft.

Thanks, greg

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Randy Presuhn
Sent: Saturday, May 15, 2004 10:08 AM
To: Ipcdn List \(E-mail\)
Subject: Re: [ipcdn] wg review of draft-ietf-ipcdn-docsisevent-mib-03.txt


Hi -

> From: "Nakanishi Greg-MGI8179" <[email protected]>
> To: "'Eduardo Cardona'" <[email protected]>; "Raftus, David" 
> <[email protected]>; "Ipcdn List (E-mail)"
<[email protected]>
> Sent: Friday, May 14, 2004 2:52 PM
> Subject: RE: [ipcdn] wg review of 
> draft-ietf-ipcdn-docsisevent-mib-03.txt
...
> Let's wait to hear what the MIB doctors say about the object name. I'm 
> OK with changing the name, if that's the recommendation.
...

I agree that there don't seem to be any advantages to retaining the old name.

Current practice strongly favors referring to these things as notifications.  Not only can RFC 3413 dynamically control whether these things show up on the wire as informs or traps, but there's also the possibility that they may end up being logged (locally or
remotely) using, for example, RFC 3014.

Randy



_______________________________________________
IPCDN mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ipcdn
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.