headers
Internet-Drafts | 3 Jun 2003 13:46
Picon
Favicon

I-D ACTION:draft-ietf-disman-alarm-mib-13.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Distributed Management Working Group of the IETF.

	Title		: Alarm MIB
	Author(s)	: S. Chisholm, D. Romascanu
	Filename	: draft-ietf-disman-alarm-mib-13.txt
	Pages		: 66
	Date		: 2003-6-2
	
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes management objects used for defining
and storing alarms.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-disman-alarm-mib-13.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-disman-alarm-mib-13.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Wijnen, Bert (Bert | 6 Jun 2003 15:31
Picon
Favicon

AD review of: draft-ietf-disman-conditionmib-08.txt

Here is my review of rev 8.

If you want, we can issue IETF Last Call, and then you may
consider these comments as IETF Last Call Comments, that you
better address rigth after such an IETF Last Call.

More or less serious:

- I see
    IANAItuProbableCauseOrZero ::= TEXTUAL-CONVENTION
      STATUS  current
      DESCRIPTION
       "This TC can take any value of IANAItuProbableCause or 0.
        IANAItuProbableCause is defined in the IANA-ITU-ALARM-TC
        module in the Alarm MIB document (see RFC zzzz)."
      REFERENCE
        "RFC zzzz - Alarm MIB, Chisholm, S. and D. Romascanu, mmm 2002."
    -- RFC Ed.: replace zzzz with the RFC number of the Alarm MIB document, 
    --          replace mmm with the actual month, and remove this notice.
  And so I wonder. That IANA mantained MIB module will be extracted from
  the document, and after that, the authoritative version will be at
  the iana web site as follows: 
       http://www.iana.org/assignments/ianaitualarmtc-mib   
  Now putting a url into the REF clause is not good either, but maybe
  something aka:
      REFERENCE
        "IANA-ITU-ALARM-TC MIB module as maintained at the IANA web site.
         The initial module was also published in RFC zzzz."
  However, you do want to add that 
        http://www.iana.org/assignments/ianaitualarmtc-mib
(Continue reading)

Permalink | Reply | 0 comments |
headers
Lam, Hing-Kam (Kam | 10 Jun 2003 07:51
Picon
Favicon

RE: AD review of: draft-ietf-disman-conditionmib-08.txt

Hi,

I prefer to have these comments addressed before issuing an IETF Last Call. However, due to work
obligation, I won't be able to start working on version -09 until next week. I hope this is acceptable.

Regards,
Kam 

> -----Original Message-----
> From: Wijnen, Bert (Bert) 
> Sent: Friday, June 06, 2003 9:32 AM
> To: Lam, Hing-Kam (Kam); 'a_n_huynh <at> yahoo.com'; 'David Perkins'
> Cc: Disman (E-mail) (E-mail)
> Subject: AD review of: draft-ietf-disman-conditionmib-08.txt
> 
> 
> Here is my review of rev 8.
> 
> If you want, we can issue IETF Last Call, and then you may
> consider these comments as IETF Last Call Comments, that you
> better address rigth after such an IETF Last Call.
> 
> More or less serious:
> 
> - I see
>     IANAItuProbableCauseOrZero ::= TEXTUAL-CONVENTION
>       STATUS  current
>       DESCRIPTION
>        "This TC can take any value of IANAItuProbableCause or 0.
>         IANAItuProbableCause is defined in the IANA-ITU-ALARM-TC
(Continue reading)

Permalink | Reply | 0 comments |
headers
Internet-Drafts | 11 Jun 2003 13:53
Picon
Favicon

I-D ACTION:draft-ietf-disman-alarm-mib-14.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Distributed Management Working Group of the IETF.

	Title		: Alarm MIB
	Author(s)	: S. Chisholm, D. Romascanu
	Filename	: draft-ietf-disman-alarm-mib-14.txt
	Pages		: 66
	Date		: 2003-6-10
	
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes management objects used for defining
and storing alarms.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-disman-alarm-mib-14.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-disman-alarm-mib-14.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Randy Presuhn | 12 Jun 2003 18:48
Picon

Should Disman meet in Vienna?

Hi -

Here's a status update, some helpful hints, and a question.
Please forgive the length of this post.

The alarm documents are rapidly cycling back and forth between
the editors and our AD, fixing things as required by
http://www.ietf.org/ietf/1id-guidelines.txt
http://www.ietf.org/ID-nits.html
http://www.ietf.org/internet-drafts/draft-rfc-editor-rfc2223bis-05.txt
http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-guidelines-01.txt
It would have been nice if we had taken care of this stuff before WG last call,
but we'll just have to keep that in mind for the future.

I've seen practically no discussion of any of the other disman WG
documents:  updates to expression, event, log, or script MIBs.

I have not received any requests for consideration of new topics,
nor have I seen any discussion on the WG mailing list that would
indicate interest.

The deadline for scheduling WG sessions in Vienna is fast approaching.

Paul Hoffman offers this advice for folks considering attending
the face-to-face meetings:

> - Newcomers can learn a lot ahead of time by reading the Tao of the
> IETF at <http://www.ietf.org/tao.html>. The newcomer orientation on
> Sunday (this year, at 1PM) is useful, but it is even more useful if
> they have read the Tao first.
(Continue reading)

Permalink | Reply | 501 comments |
headers
Ramanathan Kavasseri | 13 Jun 2003 00:07
Picon
Favicon

Re: Should Disman meet in Vienna?


Randy Presuhn wrote:
> Hi -
> 
> Here's a status update, some helpful hints, and a question.
> Please forgive the length of this post.
> 
> The alarm documents are rapidly cycling back and forth between
> the editors and our AD, fixing things as required by
> http://www.ietf.org/ietf/1id-guidelines.txt
> http://www.ietf.org/ID-nits.html
> http://www.ietf.org/internet-drafts/draft-rfc-editor-rfc2223bis-05.txt
> http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-guidelines-01.txt
> It would have been nice if we had taken care of this stuff before WG last call,
> but we'll just have to keep that in mind for the future.
> 
> I've seen practically no discussion of any of the other disman WG
> documents:  updates to expression, event, log, or script MIBs.
> 

I've been miles behind in my editing work. Apologies for that.
I'll post these docs by the end of the week...

Ram

> I have not received any requests for consideration of new topics,
> nor have I seen any discussion on the WG mailing list that would
> indicate interest.
> 
> The deadline for scheduling WG sessions in Vienna is fast approaching.
(Continue reading)

Permalink | Reply | 501 comments |
headers
Randy Presuhn | 13 Jun 2003 18:24
Picon

To-do items left over from San Francisco

Hi -

I looked through the minutes from our meeting in San Francisco, and
it looks like the following items remain to be done:

| 1. Sharon Chisholm tasked with drafting a "Thank You" message to the
| ITU-T Liaison, and sending the draft to the DISMAN wg.

Sharon?

| 8. For Script MIB and Schedule MIB - Randy to look at a questionnaire
| for implementation requests on these MIBs.

Mea culpa.

| 9. Remops MIB - if anyone is interested in assiting with edits, to
| contact RP on the disman mailing list.
|
| 10. Octet String in Remops MIB for payload - has a constraint related to
| ipv4 - computes
| pkt size - ipv4 hdr size. Need description clarification on what the
| object should do (return an error or silently truncate payload size)
| when transport type is ipv6 - Randy Presuhn suggested silently
| truncating. Need further
| discussion on the mailing list. This action item is assigned to Randy
| Presunhn.

Juergen Quittek accepted the job of handling
the edits.  Juergen, where are we?
(Continue reading)

Permalink | Reply | 5 comments |
headers
Juergen Quittek | 13 Jun 2003 20:03
Picon

Re: To-do items left over from San Francisco

Hi Randy,

-- Randy Presuhn wrote on 13 June 2003 09:24 -0700:

> Hi -
>
> I looked through the minutes from our meeting in San Francisco, and
> it looks like the following items remain to be done:
>
>| 1. Sharon Chisholm tasked with drafting a "Thank You" message to the
>| ITU-T Liaison, and sending the draft to the DISMAN wg.
>
> Sharon?
>
>| 8. For Script MIB and Schedule MIB - Randy to look at a questionnaire
>| for implementation requests on these MIBs.
>
> Mea culpa.
>
>| 9. Remops MIB - if anyone is interested in assiting with edits, to
>| contact RP on the disman mailing list.
>|
>| 10. Octet String in Remops MIB for payload - has a constraint related to
>| ipv4 - computes
>| pkt size - ipv4 hdr size. Need description clarification on what the
>| object should do (return an error or silently truncate payload size)
>| when transport type is ipv6 - Randy Presuhn suggested silently
>| truncating. Need further
>| discussion on the mailing list. This action item is assigned to Randy
>| Presunhn.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Randy Presuhn | 13 Jun 2003 20:05
Picon

Re: To-do items left over from San Francisco

Hi -

> From: "Juergen Quittek" <quittek <at> ccrle.nec.de>
> To: "Randy Presuhn" <randy_presuhn <at> mindspring.com>; "Disman (E-mail)" <disman <at> ietf.org>
> Cc: "Ram Kavasseri" <ramk <at> cisco.com>; "Sharon Chisholm" <schishol <at> nortelnetworks.com>; "Wes
Hardaker" <hardaker <at> tislabs.com>
> Sent: Friday, June 13, 2003 11:03 AM
> Subject: Re: To-do items left over from San Francisco

....
> >| 10. Octet String in Remops MIB for payload - has a constraint related to
> >| ipv4 - computes
> >| pkt size - ipv4 hdr size. Need description clarification on what the
> >| object should do (return an error or silently truncate payload size)
> >| when transport type is ipv6 - Randy Presuhn suggested silently
> >| truncating. Need further
> >| discussion on the mailing list. This action item is assigned to Randy
> >| Presunhn.
> >
> > Juergen Quittek accepted the job of handling
> > the edits.  Juergen, where are we?
>
> I collected all remops issues from the mailing list since
> publication of the RFC incluing the issue on the RFC errata
> web page.
>
> I will reply on your suggestion in a separate message.
...

Great!  Thanks for the quick response.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Randy Presuhn | 13 Jun 2003 20:04
Picon

Re: To-do items left over from San Francisco

Hi -

> From: "Ramanathan Kavasseri" <ramk <at> cisco.com>
> To: "Randy Presuhn" <randy_presuhn <at> mindspring.com>
> Cc: "Disman (E-mail)" <disman <at> ietf.org>; "Sharon Chisholm" <schishol <at> nortelnetworks.com>;
<quittek <at> ccrle.nec.de>; "Wes Hardaker"
<hardaker <at> tislabs.com>
> Sent: Friday, June 13, 2003 10:31 AM
> Subject: Re: [Disman] To-do items left over from San Francisco
>

> I was about to post the revised event mib draft, but realized
> that I don't have Bob Stewart's latest contact information.
>
> The info in the draft still points to "Cisco Systems, Inc.",
> which isn't true anymore.
>
> Anyone have a more upto-date address? Or an alternative suggestion?
...

I think the solution adopted in http://www.ietf.org/rfc/rfc3410.txt
is fine.

Randy
Permalink | Reply | 0 comments |

Gmane