From mailnull@www1.ietf.org Sun Sep 1 09:00:45 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18234 for ; Sun, 1 Sep 2002 09:00:45 -0400 (EDT) From: mailnull@www1.ietf.org Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g81D1o408066 for diffserv-archive@odin.ietf.org; Sun, 1 Sep 2002 09:01:50 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g81D1oo08062 for ; Sun, 1 Sep 2002 09:01:50 -0400 Date: Sun, 01 Sep 2002 09:01:50 -0400 Message-ID: <20020901130150.1916.37181.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder To: diffserv-archive@optimus.ietf.org X-No-Archive: yes X-Ack: no Sender: sip-admin@ietf.org Errors-To: sip-admin@ietf.org X-BeenThere: sip@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, diffserv-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@. Thanks! Passwords for diffserv-archive@optimus.ietf.org: List Password // URL ---- -------- diffserv@ietf.org 7ujhy6 https://www1.ietf.org/mailman/options/diffserv/diffserv-archive%40optimus.ietf.org From mailnull@www1.ietf.org Sun Sep 1 10:31:07 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21433 for ; Sun, 1 Sep 2002 10:31:07 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g81EWBU26074 for diffserv-archive@odin.ietf.org; Sun, 1 Sep 2002 10:32:11 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g81E86o25403; Sun, 1 Sep 2002 10:08:06 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g81Dsdo24607 for ; Sun, 1 Sep 2002 09:54:39 -0400 Received: from mail-gw2.hursley.ibm.com (mail-gw2.hursley.ibm.com [194.196.110.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20674 for ; Sun, 1 Sep 2002 09:53:04 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=mail-gw2.hursley.ibm.com) by mail-gw2.hursley.ibm.com with esmtp (Exim 4.10) id 17lVB5-00026m-00; Sun, 01 Sep 2002 14:54:11 +0100 Received: from [9.20.45.103] (helo=sp15en17.hursley.ibm.com) by mail-gw2.hursley.ibm.com with esmtp (Exim 4.10) id 17lVB5-00026h-00; Sun, 01 Sep 2002 14:54:11 +0100 Received: from hursley.ibm.com (gsine06.us.sine.ibm.com [9.14.6.46]) by sp15en17.hursley.ibm.com (AIX4.3/8.9.3/8.9.3) with ESMTP id OAA17376; Sun, 1 Sep 2002 14:54:00 +0100 Message-ID: <3D721BFE.56E9A88F@hursley.ibm.com> Date: Sun, 01 Sep 2002 15:54:06 +0200 From: Brian E Carpenter Organization: IBM X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,fr,de MIME-Version: 1.0 To: Dan Grossman CC: Andrew Smith , diffserv@ietf.org Subject: Re: [Diffserv] Re: Fwd: RE: Fwd: Re: authors 48 hours: RFC 3289 NOW AVAILABLE References: <00f601c24fce$d19511a0$1400000a@ANDREWLAPTOP> <3D6F7988.27285361@dma.isg.mot.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: diffserv-admin@ietf.org Errors-To: diffserv-admin@ietf.org X-BeenThere: diffserv@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Dan, if it was just clarifications maybe... but this is errata, hence we choose between the RFC-Ed errata page or a new RFC. Brian Dan Grossman wrote: > > Why don't we do with the MIB what we did with RFC 2474, 2475, 2597 and 2598: start a draft > (can a concluded WG have a WG draft?) that captures clarifications to the MIB? > > Andrew Smith wrote: > > > I'm not convinced that now is the right time to be updating this MIB > > and/or the RFC that includes it. Some of Tom Irwin's first set of > > comments fix errors but some (and all of his second set of comments) are > > clarifications, as were most of mine from May 3th 2002 (below). If we > > must, then I'd suggest just fixing the syntax errors in the MIB module. > > But don't things like this usually wait for a "natural" refresh cycle > > e.g. an attempt to move an RFC to Draft standard? I'd hate to > > destabilise anyone's plans to implement the current RFC. We've got > > published/archived fixes on the record so I don't see the urgency to > > update (other than tidiness). And it's quite likely that we'd be able to > > remove 20 pages or more with the benefit of another year or so more > > implementation experience. > > > > Just my thoughts - I don't have any significant stake in any current > > implementation plans so it really ought to be up to others to say what > > they want done. > > > > Andrew Smith > > > > -----Original Message----- > > From: diffserv-admin@ietf.org [mailto:diffserv-admin@ietf.org] On Behalf > > Of Fred Baker > > Sent: Thursday, August 29, 2002 6:35 PM > > To: Kwok Ho Chan > > Cc: ah_smith@acm.org; diffserv@ietf.org > > Subject: [Diffserv] Re: Fwd: RE: Fwd: Re: authors 48 hours: RFC > > 3289 NOW AVAILABLE > > > > At 07:45 PM 8/29/2002 -0400, Kwok Ho Chan wrote: > > >Fred: > > >Are you referring to the attached E-Mail? > > > > yes. I would like all comments edited into the new document to have at > > least been seen by the working group. I don't think we'll get a lot of > > commentary, but people should have the opportunity. > > > > >-- Kwok -- > > > > > >>From: "Andrew Smith" > > >>To: "Brian E Carpenter" , "Fred Baker" > > >>, > > >> "Chan, Kwok-Ho [BL60:470:EXCH]" > > >>Cc: , , > > >> "Dan Grossman" > > >>Subject: RE: Fwd: Re: authors 48 hours: RFC > > >>3289 NOW AVAILABLE > > >>Date: Thu, 30 May 2002 12:20:51 -0700 > > >>X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) > > >>Importance: Normal > > >>X-SMTP-HELO: falcon.mail.pas.earthlink.net > > >>X-SMTP-MAIL-FROM: ah_smith@acm.org > > >>X-SMTP-RCPT-TO: khchan@nortelnetworks.com > > >>X-SMTP-PEER-INFO: falcon.mail.pas.earthlink.net [207.217.120.74] > > >> > > >>I just found out about the "48 hours" today: most of these comments > > are > > >>probably (way) too late but there are some editorial things buried in > > here > > >>that might be helpful at this late stage: > > >> > > >>Please change my contact info: > > >> OLD: > > >> > > >> A. Smith > > >> Allegro > > Networks > > >> NEW: > > >> A. Smith > > >> Harbour > > Networks > > >> > > >>11. Authors' Addresses > > >> > > >>OLD: > > >> Andrew Smith > > >> Allegro Networks > > >> 6399 San Ignacio Ave > > >> San Jose, CA 95119 > > >> > > >> EMail: andrew@allegronetworks.com > > >> NEW: > > >> Andrew Smith > > >> Harbour Networks > > >> Jiuling Building > > >> 21 North Xisanhuan Ave. > > >> Beijing, 100089, PRC > > >> > > >> EMail: ah_smith@acm.org > > >> > > >> > > >> > > >>3.5.3. diffServMinRateTable - The Minimum Rate Table: The description > > (both > > >>here and in the comments in the MIB module and in the DESCRIPTION > > clauses) > > >>is unclear on when the Rate and when the Priority parameters are to be > > used > > >>and what is their combined effect: > > >> > > >> "When the output rate of a queue or scheduler must be given a > > minimum > > >> rate or a priority, this is done using the diffServMinRateTable. > > >> Rates may be expressed as absolute rates, or as a fraction of > > >> ifSpeed, and imply the use of a rate-based scheduler such as WFQ > > or > > >> WRR. The use of a priority implies the use of a Priority > > Scheduler. > > >> Only one of the Absolute or Relative rates needs to be set; the > > other > > >> takes the relevant value as a result. Excess capacity is > > distributed > > >> proportionally among the inputs to a scheduler using the assured > > >> rate. More complex functionality may be described by augmenting > > this > > >> MIB." > > >> > > >>I thought that the type of scheduler was implied by > > diffServSchedulerMethod, > > >>not by "use of a priority". And if you're doing strict priority > > scheduling, > > >>neither of Absolute or Relative rates needs to be set, right? Text > > above > > >>seems to imply otherwise. See also below. > > >> > > >>3.5.5 There's no reference to figure 4. Perhaps it should be from the > > >>paragraph at the bottom of p18? > > >> > > >>3.5.5 Is there a way to keep this set of diagrams closer to (in-line > > with) > > >>the text describing them, or at least, on the same page? I know it > > wastes > > >>paper/bytes but would add to clarity. > > >> > > >>3.5.5 I find some of this relatively new text confusing (this is the > > first > > >>time I've seen it so tell me if I'm too late with the following > > comments). > > >>Specifically: > > >> > > >> "For representing a Strict Priority scheduler, each scheduler > > input is > > >> assigned a priority with respect to all the other inputs feeding > > the > > >> same scheduler, with default values for the other parameters. > > >> Higher-priority traffic that is not being delayed for shaping will > > be > > >> serviced before a lower-priority input. An example is found in > > >> Figure 2." > > >> > > >>Clearer (or, at least, more accurate) is: > > >> > > >> "For representing a Strict Priority scheduler, the > > >>diffServSchedulerMethod is set to diffServSchedulerPriority and the > > >>prededing queue or scheduler feeding this scheduler input is assigned > > a > > >>priority in its associated diffServMinRateEntry with respect to all > > the > > >>other inputs feeding the same scheduler (the value of the other > > parameters > > >>in this entry are irrelevant). Traffic from higher-priority inputs to > > this > > >>scheduler will be serviced before that from lower-priority inputs. An > > >>example is found in Figure 2." > > >> > > >>Figures 3, 4 and 5: suggest you use more specific labels in some of > > the > > >>boxes to remove confusion: > > >>- figure 3, replace "Rate" with "MaxRate" in each box; > > >>- figure 4, put something in the empty boxes e.g. "n/a" or leave them > > out. > > >>Replace "Shaping Rate" with "MaxRate" - we have no parameter called > > shaping > > >>rate. > > >> > > >>3.5.5: suggest you lose the NOTE and its text, just above figure 4, or > > at > > >>least join it up with the following paragraph. > > >> > > >>3.5.5: last paragraph should be part of 3.6 really. And glue Figure 6 > > to > > >>this paragraph for clarity. > > >> > > >>3.6: change "four AF classes" to "four AF classes, each with 3 levels > > of > > >>drop precedence or 'colours'". We must be clear that this is just an > > example > > >>of an AF implementation that chooses to do 4 classes, each with 3 > > colours. > > >> > > >>3.6: Suggest you use the same example scenario for figures 6 and 7 - > > it's > > >>confusing to use different example scenarios. Figure 7 introduces a > > new kind > > >>of "hybrid" notation for the first time (we've always gone > > left-to-right > > >>before, not top-to-bottom - I preferred the former for clarity): I > > suggest > > >>it needs some words to explain the notation (rhetorical questions: > > what do > > >>the lines imply when they don't have arrowheads? what are the 2 or 3 > > >>different lines exiting from the meters? These are all deducible from > > the > > >>following text but it's made harder work due to the new notation. BTW, > > >>there's an arrow missing out of the back/bottom/right Action box. > > >> > > >>3.6: suggest you add the "everything else" case that you discuss in > > the text > > >>to figure 7. > > >> > > >>3.6.: there's no reference to figure 7 in the text. > > >> > > >>3.6 and 3.7: actually, I'm not sure why these sections are here in > > this > > >>document - a few years ago, we took out similar "tutorial" material > > and put > > >>it in the Model draft. There's nothing in these sections that is > > specific to > > >>the MIB. The right thing to have in this document is the "translation" > > of an > > >>example like this into the structures and linkages used by the MIB but > > these > > >>sections do not help with this. We had such material in draft-09 and > > it has > > >>disappeared (I'm not saying 3.6 and 3.7 aren't useful material but it > > just > > >>does not belong in this document) - I think this is a backward step. > > >> > > >>Anyhow, I'm probably too late to the party with most of these comments > > - I > > >>should have reviewed it when the IESG last call was in progress (I > > didn't > > >>realise so much had changed since -09 which was the last version that > > I > > >>reviewed properly). > > >> > > >>Andrew > > >> > > >> > > >> > > >> > > >>-----Original Message----- > > >>From: Brian E Carpenter [mailto:brian@hursley.ibm.com] > > >>Sent: Thursday, May 30, 2002 5:56 AM > > >>To: Fred Baker > > >>Cc: knichols@packetdesign.com; rfc-editor@rfc-editor.org; Andrew > > Smith; > > >>Kwok Ho Chan > > >>Subject: Re: Fwd: Re: authors 48 hours: RFC > > >>3289 NOW AVAILABLE > > >> > > >> > > >>OK, in view of Kwok's response we can give it another day or say, but > > >>then... > > >> > > >> Brian > > >> > > >>Fred Baker wrote: > > >> > > > >> > You may need to make an executive decision here. Andrew and Kwok > > are AWOL. > > >> > > > >> > >Date: Wed, 29 May 2002 19:50:58 GMT > > >> > >To: khchan@nortelnetworks.com, andrew@allegronetworks.com > > >> > >Subject: Re: authors 48 hours: RFC 3289 > > >> > > NOW AVAILABLE > > >> > >Cc: rfc-editor@rfc-editor.org, mankin@ISI.EDU, sob@harvard.edu, > > >> > > bwijnen@lucent.com, fred@cisco.com > > >> > >From: rfc-editor@rfc-editor.org > > >> > >X-Sun-Charset: US-ASCII > > >> > > > > >> > >Kwok Ho and Andrew, > > >> > > > > >> > >We still have not heard from you regarding this document. Please > > let > > >> > >us know if there are any corrections required. > > >> > > > > >> > >We are waiting to hear from you. > > >> > > > > >> > >RFC Editor > > >> > > > > >> > > > > >> > >----- Begin Included Message ----- > > >> > > > > >> > > >From rfc-ed@ISI.EDU Thu May 23 16:22:59 2002 > > >> > >Date: Thu, 23 May 2002 23:22:45 GMT > > >> > >To: rfc-editor@rfc-editor.org, fred@cisco.com > > >> > >Subject: Re: authors 48 hours: RFC 3289 > > >> > > NOW AVAILABLE > > >> > >Cc: khchan@nortelnetworks.com, andrew@allegronetworks.com, > > >>mankin@ISI.EDU, > > >> > > sob@harvard.edu, bwijnen@lucent.com > > >> > >From: rfc-editor@rfc-editor.org > > >> > >X-Sun-Charset: US-ASCII > > >> > >X-AntiVirus: scanned by AMaViS 0.2.1 > > >> > >Content-Length: 3636 > > >> > > > > >> > >Kwok Ho and Andrew, > > >> > > > > >> > >Please let us know if the document is ready to be published. > > >> > > > > >> > >We are awaiting your reply. > > >> > > > > >> > >Thank you. > > >> > > > > >> > >RFC Editor > > >> > > > > >> > > > > >> > > > From rfc-ed@ISI.EDU Tue May 21 09:25:15 2002 > > >> > > > Date: Tue, 21 May 2002 16:24:54 GMT > > >> > > > To: rfc-editor@rfc-editor.org, fred@cisco.com > > >> > > > Subject: Re: authors 48 hours: RFC 3289 > > >> > > > NOW AVAILABLE > > >> > > > Cc: khchan@nortelnetworks.com, andrew@allegronetworks.com, > > >>mankin@ISI.EDU, > > >> > > > sob@harvard.edu, bwijnen@lucent.com > > >> > > > From: rfc-editor@rfc-editor.org > > >> > > > X-Sun-Charset: US-ASCII > > >> > > > X-AntiVirus: scanned by AMaViS 0.2.1 > > >> > > > Content-Length: 2866 > > >> > > > > > >> > > > Authors, > > >> > > > > > >> > > > We have not heard any further from you regarding this document. > > We > > >> > > > would appreciate a confirmation that the document is ready to > > be > > >> > > > published as it now appears at: > > >> > > > > > >> > > > ftp://ftp.isi.edu/in-notes/authors/rfc3289.txt > > >> > > > > > >> > > > We will wait to hear from you before continuing on. > > >> > > > > > >> > > > Thank you. > > >> > > > > > >> > > > RFC Editor > > >> > > > > > >> > > > > > >> > > > > From rfc-ed@ISI.EDU Mon May 13 11:51:19 2002 > > >> > > > > Date: Mon, 13 May 2002 18:50:53 GMT > > >> > > > > To: rfc-editor@rfc-editor.org, fred@cisco.com > > >> > > > > Subject: Re: authors 48 hours: RFC 3289 > > >> > > > > NOW AVAILABLE > > >> > > > > Cc: khchan@nortelnetworks.com, andrew@allegronetworks.com, > > >> > > mankin@ISI.EDU, > > >> > > > > sob@harvard.edu, bwijnen@lucent.com > > >> > > > > From: rfc-editor@rfc-editor.org > > >> > > > > X-Sun-Charset: US-ASCII > > >> > > > > X-AntiVirus: scanned by AMaViS 0.2.1 > > >> > > > > Content-Length: 1984 > > >> > > > > > > >> > > > > Fred, > > >> > > > > > > >> > > > > Thank you for bringing this to our attention. It now parses > > >> > > > > successfully. > > >> > > > > > > >> > > > > We have updated your contact information in the authors > > address > > >> > > > > section, as well as within the mib. > > >> > > > > > > >> > > > > Please let us know if there are any further corrections > > required. > > >>We > > >> > > > > will wait to hear from you. > > >> > > > > > > >> > > > > Thank you. > > >> > > > > > > >> > > > > RFC editor > > >> > > > > > > >> > > > > > > >> > > > > > From fred@cisco.com Fri May 10 01:03:56 2002 > > >> > > > > > X-Sender: fred@mira-sjcm-4.cisco.com > > >> > > > > > X-Mailer: QUALCOMM Windows Eudora Version 5.1 > > >> > > > > > Date: Fri, 10 May 2002 16:03:24 +0800 > > >> > > > > > To: rfc-editor@rfc-editor.org > > >> > > > > > From: Fred Baker > > >> > > > > > Subject: Re: authors 48 hours: RFC 3289 > > >> > > > > > NOW AVAILABLE > > >> > > > > > Cc: khchan@nortelnetworks.com, andrew@allegronetworks.com, > > >> > > > > > rfc-editor@rfc-editor.org, mankin@ISI.EDU, > > sob@harvard.edu, > > >> > > > > > bwijnen@lucent.com > > >> > > > > > Mime-Version: 1.0 > > >> > > > > > X-AntiVirus: scanned by AMaViS 0.2.1 > > >> > > > > > > > >> > > > > > At 10:37 PM 5/9/2002 +0000, rfc-editor@rfc-editor.org > > wrote: > > >> > > > > > >FYI: > > >> > > > > > > > > >> > > > > > >W: f(rfc3289.mi2), (42,1) Textual convention "Dscp" > > defined but > > >> > > not used > > >> > > > > > >W: f(rfc3289.mi2), (52,1) Textual convention "DscpOrAny" > > defined > > >>but > > >> > > > > > >not used > > >> > > > > > > > >> > > > > > these two warnings come up because the TCs are in a > > separate MIB > > >> > > Module > > >> > > > > > from the main mib, and are imported into it. They are fine. > > >> > > > > > > > >> > > > > > My contact information has changed slightly; I have a new > > physical > > >> > > address. > > >> > > > > > > > >> > > > > > > > >>/===================================================================== > > / > > >> > > > > > | Fred Baker | 1121 Via Del > > Rey > > >>| > > >> > > > > > | Cisco Fellow | Santa Barbara, > > >>California | > > >> > > > > > +--------------------------------+ 93117 USA > > >>| > > >> > > > > > | Nothing will ever be attempted,| phone: +1-805-681-0115 > > >>| > > >> > > > > > | if all possible objections must| fax: +1-413-473-2403 > > >>| > > >> > > > > > | be first overcome. | > > >>| > > >> > > > > > | Dr. Johnson, Rasselas, 1759| > > >>| > > >> > > > > > > > >>/===================================================================== > > / > > >> > > > > > > > >> > > > > > > >> > > > > > >> > > > > >> > > > > >> > >----- End Included Message ----- > > > > > > > _______________________________________________ > > diffserv mailing list > > diffserv@ietf.org > > https://www1.ietf.org/mailman/listinfo/diffserv > > Archive: > > http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillis > > t.html > > > > _______________________________________________ > > diffserv mailing list > > diffserv@ietf.org > > https://www1.ietf.org/mailman/listinfo/diffserv > > Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html > > _______________________________________________ > diffserv mailing list > diffserv@ietf.org > https://www1.ietf.org/mailman/listinfo/diffserv > Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Brian E Carpenter Distinguished Engineer, Internet Standards & Technology, IBM On assignment at the IBM Zurich Laboratory, Switzerland _______________________________________________ diffserv mailing list diffserv@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html From mailnull@www1.ietf.org Wed Sep 11 17:45:13 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26066 for ; Wed, 11 Sep 2002 17:45:13 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8BLkVe13330 for diffserv-archive@odin.ietf.org; Wed, 11 Sep 2002 17:46:31 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BLF4v11137; Wed, 11 Sep 2002 17:15:04 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BL23v10311 for ; Wed, 11 Sep 2002 17:02:03 -0400 Received: from cs.tut.fi (root@varis.cs.tut.fi [130.230.4.42]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24562 for ; Wed, 11 Sep 2002 17:00:15 -0400 (EDT) Received: from kiuru.cs.tut.fi (daemon@kiuru.cs.tut.fi [130.230.4.18]) by cs.tut.fi (8.8.8/8.8.8) with ESMTP id AAA02838 for ; Thu, 12 Sep 2002 00:01:53 +0300 (EET DST) Received: (from juzi@localhost) by kiuru.cs.tut.fi (8.11.6+Sun/8.8.4) id g8BL1rv00139; Thu, 12 Sep 2002 00:01:53 +0300 (EET DST) X-Authentication-Warning: kiuru.cs.tut.fi: juzi set sender to juzi@kiuru.cs.tut.fi using -f To: diffserv@ietf.org From: Lemponen Jussi Date: 12 Sep 2002 00:01:53 +0300 Message-ID: Lines: 11 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [Diffserv] parameters section missing from the Diffserv PIB Sender: diffserv-admin@ietf.org Errors-To: diffserv-admin@ietf.org X-BeenThere: diffserv@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , Reading through draft-ietf-diffserv-pib-09.txt, I noticed that the parameters section in the PIB itself is missing. The descriptions for attributes dsTBParamType and dsIfSchedulerCapsServiceDisc do still imply that some parameter definitions should be there. Jussi Lemponen Tampere University of Technology Institute of Communications Engineering _______________________________________________ diffserv mailing list diffserv@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html From mailnull@www1.ietf.org Wed Sep 11 18:55:39 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27691 for ; Wed, 11 Sep 2002 18:55:39 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8BMuvt16972 for diffserv-archive@odin.ietf.org; Wed, 11 Sep 2002 18:56:57 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BMZwv15277; Wed, 11 Sep 2002 18:35:58 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BMTEv15060 for ; Wed, 11 Sep 2002 18:29:14 -0400 Received: from hoemail2.firewall.lucent.com ([192.11.226.163]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26794 for ; Wed, 11 Sep 2002 18:27:26 -0400 (EDT) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g8BMSb722360 for ; Wed, 11 Sep 2002 18:28:37 -0400 (EDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Thu, 12 Sep 2002 00:28:36 +0200 Message-ID: From: "Wijnen, Bert (Bert)" To: Lemponen Jussi , diffserv@ietf.org Subject: RE: [Diffserv] parameters section missing from the Diffserv PIB Date: Thu, 12 Sep 2002 00:28:33 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: diffserv-admin@ietf.org Errors-To: diffserv-admin@ietf.org X-BeenThere: diffserv@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , I think they are the parameters that have been sepcified and identified in the diffserv MIB (RFC3289) Thanks, Bert > -----Original Message----- > From: Lemponen Jussi [mailto:juzi@cs.tut.fi] > Sent: woensdag 11 september 2002 23:02 > To: diffserv@ietf.org > Subject: [Diffserv] parameters section missing from the Diffserv PIB > > > > > Reading through draft-ietf-diffserv-pib-09.txt, I noticed that > the parameters section in the PIB itself is missing. The descriptions > for attributes dsTBParamType and dsIfSchedulerCapsServiceDisc do still > imply that some parameter definitions should be there. > > > Jussi Lemponen > Tampere University of Technology > Institute of Communications Engineering > _______________________________________________ > diffserv mailing list > diffserv@ietf.org > https://www1.ietf.org/mailman/listinfo/diffserv > Archive: > http://www.ietf.org/mail-archive/working-groups/diffserv/curre nt/maillist.html _______________________________________________ diffserv mailing list diffserv@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html From mailnull@www1.ietf.org Thu Sep 12 04:59:40 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17032 for ; Thu, 12 Sep 2002 04:59:40 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8C90pp23917 for diffserv-archive@odin.ietf.org; Thu, 12 Sep 2002 05:00:51 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8C8mlv23267; Thu, 12 Sep 2002 04:48:47 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8C7W9v18668 for ; Thu, 12 Sep 2002 03:32:09 -0400 Received: from smail2.alcatel.fr (colt-na6.alcatel.fr [62.23.212.6]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA15261 for ; Thu, 12 Sep 2002 03:30:17 -0400 (EDT) Received: from medine.ms.alcatel.fr (medine.ms.alcatel.fr [193.105.117.1]) by smail2.alcatel.fr (ALCANET/NETFR) with ESMTP id g8C7TfCv015014; Thu, 12 Sep 2002 09:29:41 +0200 Received: from ms.ms.alcatel.fr (ms.ms.alcatel.fr [188.9.12.93]) by medine.ms.alcatel.fr (8.8.8/8.8.8/aar-1.2) with ESMTP id JAA10967; Thu, 12 Sep 2002 09:29:35 +0200 (MET DST) Received: from athos.dinsunnet (athos [188.9.12.98]) by ms.ms.alcatel.fr (8.8.7/8.8.7/aar-1.0) with ESMTP id JAA25100; Thu, 12 Sep 2002 09:30:52 +0200 (MET DST) Received: from alcatel.fr by athos.dinsunnet (8.9.1b+Sun/SMI-SVR4) id JAA22881; Thu, 12 Sep 2002 09:33:23 +0200 (MET DST) Message-ID: <3D8042E2.80400@alcatel.fr> Date: Thu, 12 Sep 2002 09:31:46 +0200 From: Yacine El Mghazli Organization: Alcate R&I User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: fr-fr MIME-Version: 1.0 To: "Wijnen, Bert (Bert)" CC: Lemponen Jussi , diffserv@ietf.org, "rap@ops.ietf.org" Subject: Re: [Diffserv] parameters section missing from the Diffserv PIB References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-milter (http://amavis.org/) Content-Transfer-Encoding: 7bit Sender: diffserv-admin@ietf.org Errors-To: diffserv-admin@ietf.org X-BeenThere: diffserv@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit I was wondering about this point: how are the OIDs identified in the MIB senseful within the PIB ? my understanding is that the PIB is an AUTONOMOUS named data structure... in this context, what is the meaning of an OID referencing nothing in the PIB itself ? thank you for your explanations, yacine Wijnen, Bert (Bert) wrote: > I think they are the parameters that have been sepcified and identified > in the diffserv MIB (RFC3289) > > Thanks, > Bert > > >>-----Original Message----- >>From: Lemponen Jussi [mailto:juzi@cs.tut.fi] >>Sent: woensdag 11 september 2002 23:02 >>To: diffserv@ietf.org >>Subject: [Diffserv] parameters section missing from the Diffserv PIB >> >> >> >> >>Reading through draft-ietf-diffserv-pib-09.txt, I noticed that >>the parameters section in the PIB itself is missing. The descriptions >>for attributes dsTBParamType and dsIfSchedulerCapsServiceDisc do still >>imply that some parameter definitions should be there. >> >> >>Jussi Lemponen >>Tampere University of Technology >>Institute of Communications Engineering >>_______________________________________________ >>diffserv mailing list >>diffserv@ietf.org >>https://www1.ietf.org/mailman/listinfo/diffserv >>Archive: >>http://www.ietf.org/mail-archive/working-groups/diffserv/curre >> > nt/maillist.html > _______________________________________________ > diffserv mailing list > diffserv@ietf.org > https://www1.ietf.org/mailman/listinfo/diffserv > Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html > > > _______________________________________________ diffserv mailing list diffserv@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html From mailnull@www1.ietf.org Thu Sep 12 08:33:45 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21043 for ; Thu, 12 Sep 2002 08:33:45 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8CCYvX02327 for diffserv-archive@odin.ietf.org; Thu, 12 Sep 2002 08:34:57 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CCI2v01543; Thu, 12 Sep 2002 08:18:02 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CC8Mv01259 for ; Thu, 12 Sep 2002 08:08:22 -0400 Received: from mail-gw2.hursley.ibm.com (mail-gw2.hursley.ibm.com [194.196.110.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20256 for ; Thu, 12 Sep 2002 08:06:40 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=mail-gw2.hursley.ibm.com) by mail-gw2.hursley.ibm.com with esmtp (Exim 4.10) id 17pSlC-0001gP-00; Thu, 12 Sep 2002 13:07:50 +0100 Received: from [9.20.45.103] (helo=sp15en17.hursley.ibm.com) by mail-gw2.hursley.ibm.com with esmtp (Exim 4.10) id 17pSlC-0001gK-00; Thu, 12 Sep 2002 13:07:50 +0100 Received: from hursley.ibm.com (dhcp23-199.zurich.ibm.com [9.4.23.199]) by sp15en17.hursley.ibm.com (AIX4.3/8.9.3/8.9.3) with ESMTP id NAA45108; Thu, 12 Sep 2002 13:07:49 +0100 Message-ID: <3D8083A5.87DDD12F@hursley.ibm.com> Date: Thu, 12 Sep 2002 14:08:05 +0200 From: Brian E Carpenter Organization: IBM X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,fr,de MIME-Version: 1.0 To: "Wijnen, Bert (Bert)" CC: Lemponen Jussi , diffserv@ietf.org Subject: Re: [Diffserv] parameters section missing from the Diffserv PIB References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: diffserv-admin@ietf.org Errors-To: diffserv-admin@ietf.org X-BeenThere: diffserv@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Bert, Are you saying this is a bug in the text? If so, we need to tell the RFC Editor PDQ. Brian "Wijnen, Bert (Bert)" wrote: > > I think they are the parameters that have been sepcified and identified > in the diffserv MIB (RFC3289) > > Thanks, > Bert > > > -----Original Message----- > > From: Lemponen Jussi [mailto:juzi@cs.tut.fi] > > Sent: woensdag 11 september 2002 23:02 > > To: diffserv@ietf.org > > Subject: [Diffserv] parameters section missing from the Diffserv PIB > > > > > > > > > > Reading through draft-ietf-diffserv-pib-09.txt, I noticed that > > the parameters section in the PIB itself is missing. The descriptions > > for attributes dsTBParamType and dsIfSchedulerCapsServiceDisc do still > > imply that some parameter definitions should be there. > > > > > > Jussi Lemponen > > Tampere University of Technology > > Institute of Communications Engineering _______________________________________________ diffserv mailing list diffserv@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html From mailnull@www1.ietf.org Thu Sep 12 14:33:11 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02603 for ; Thu, 12 Sep 2002 14:33:10 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8CIYQZ22275 for diffserv-archive@odin.ietf.org; Thu, 12 Sep 2002 14:34:26 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CII4v21578; Thu, 12 Sep 2002 14:18:05 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CI4Vv20691 for ; Thu, 12 Sep 2002 14:04:31 -0400 Received: from auemail1.firewall.lucent.com ([192.11.223.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01477 for ; Thu, 12 Sep 2002 14:02:44 -0400 (EDT) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by auemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g8CI3rp29928 for ; Thu, 12 Sep 2002 14:03:53 -0400 (EDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Thu, 12 Sep 2002 20:03:52 +0200 Message-ID: From: "Wijnen, Bert (Bert)" To: "'Brian E Carpenter'" , "Wijnen, Bert (Bert)" Cc: Lemponen Jussi , diffserv@ietf.org Subject: RE: [Diffserv] parameters section missing from the Diffserv PIB Date: Thu, 12 Sep 2002 20:03:50 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: diffserv-admin@ietf.org Errors-To: diffserv-admin@ietf.org X-BeenThere: diffserv@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , No, this is not a bug. The PIB consciously re-uses some OIDs from the MIB. I think this is a GOOD THING. And the PIB text actually states that the OIDs to identify the types are defined in the MIB, so people are given a ptr as to where to look for them. Thanks, Bert > -----Original Message----- > From: Brian E Carpenter [mailto:brian@hursley.ibm.com] > Sent: donderdag 12 september 2002 14:08 > To: Wijnen, Bert (Bert) > Cc: Lemponen Jussi; diffserv@ietf.org > Subject: Re: [Diffserv] parameters section missing from the > Diffserv PIB > > > Bert, > > Are you saying this is a bug in the text? If so, we need > to tell the RFC Editor PDQ. > > Brian > > "Wijnen, Bert (Bert)" wrote: > > > > I think they are the parameters that have been sepcified > and identified > > in the diffserv MIB (RFC3289) > > > > Thanks, > > Bert > > > > > -----Original Message----- > > > From: Lemponen Jussi [mailto:juzi@cs.tut.fi] > > > Sent: woensdag 11 september 2002 23:02 > > > To: diffserv@ietf.org > > > Subject: [Diffserv] parameters section missing from the > Diffserv PIB > > > > > > > > > > > > > > > Reading through draft-ietf-diffserv-pib-09.txt, I noticed that > > > the parameters section in the PIB itself is missing. The > descriptions > > > for attributes dsTBParamType and > dsIfSchedulerCapsServiceDisc do still > > > imply that some parameter definitions should be there. > > > > > > > > > Jussi Lemponen > > > Tampere University of Technology > > > Institute of Communications Engineering > _______________________________________________ diffserv mailing list diffserv@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html From mailnull@www1.ietf.org Thu Sep 12 14:43:27 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02960 for ; Thu, 12 Sep 2002 14:43:27 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8CIigc23294 for diffserv-archive@odin.ietf.org; Thu, 12 Sep 2002 14:44:42 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CISfv21921; Thu, 12 Sep 2002 14:28:41 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CI95v21367 for ; Thu, 12 Sep 2002 14:09:05 -0400 Received: from auemail1.firewall.lucent.com ([192.11.223.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01625 for ; Thu, 12 Sep 2002 14:07:20 -0400 (EDT) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by auemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g8CI8Qp01758 for ; Thu, 12 Sep 2002 14:08:26 -0400 (EDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Thu, 12 Sep 2002 20:08:25 +0200 Message-ID: From: "Wijnen, Bert (Bert)" To: "'Yacine El Mghazli'" , "Wijnen, Bert (Bert)" Cc: Lemponen Jussi , diffserv@ietf.org, rap@ops.ietf.org Subject: RE: [Diffserv] parameters section missing from the Diffserv PIB Date: Thu, 12 Sep 2002 20:07:25 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: diffserv-admin@ietf.org Errors-To: diffserv-admin@ietf.org X-BeenThere: diffserv@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , The DIFFSERV MIB specifies some OIDs that identify specific algorithms. These algorithms are the same no matter if they are used by a MIB or by a PIB. So using one OID to identify the same thing instead of two OIDs identifying the same thing, seems the right thing to do to me, don't you think so too? Actually your Diffserv MIB and/or PIB authors/editors should be answering these questions... Thanks, Bert > -----Original Message----- > From: Yacine El Mghazli [mailto:yacine.el_mghazli@alcatel.fr] > Sent: donderdag 12 september 2002 9:32 > To: Wijnen, Bert (Bert) > Cc: Lemponen Jussi; diffserv@ietf.org; rap@ops.ietf.org > Subject: Re: [Diffserv] parameters section missing from the > Diffserv PIB > > > I was wondering about this point: > > how are the OIDs identified in the MIB senseful within the PIB ? > > my understanding is that the PIB is an AUTONOMOUS named data > structure... in this context, what is the meaning of an OID > referencing > nothing in the PIB itself ? > > thank you for your explanations, > yacine > > > > Wijnen, Bert (Bert) wrote: > > > I think they are the parameters that have been sepcified > and identified > > in the diffserv MIB (RFC3289) > > > > Thanks, > > Bert > > > > > >>-----Original Message----- > >>From: Lemponen Jussi [mailto:juzi@cs.tut.fi] > >>Sent: woensdag 11 september 2002 23:02 > >>To: diffserv@ietf.org > >>Subject: [Diffserv] parameters section missing from the Diffserv PIB > >> > >> > >> > >> > >>Reading through draft-ietf-diffserv-pib-09.txt, I noticed that > >>the parameters section in the PIB itself is missing. The > descriptions > >>for attributes dsTBParamType and > dsIfSchedulerCapsServiceDisc do still > >>imply that some parameter definitions should be there. > >> > >> > >>Jussi Lemponen > >>Tampere University of Technology > >>Institute of Communications Engineering > >>_______________________________________________ > >>diffserv mailing list > >>diffserv@ietf.org > >>https://www1.ietf.org/mailman/listinfo/diffserv > >>Archive: > >>http://www.ietf.org/mail-archive/working-groups/diffserv/curre > >> > > nt/maillist.html > > _______________________________________________ > > diffserv mailing list > > diffserv@ietf.org > > https://www1.ietf.org/mailman/listinfo/diffserv > > Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html > > > _______________________________________________ diffserv mailing list diffserv@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html _______________________________________________ diffserv mailing list diffserv@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html From mailnull@www1.ietf.org Thu Sep 12 15:06:22 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03920 for ; Thu, 12 Sep 2002 15:06:22 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8CJ7cH24886 for diffserv-archive@odin.ietf.org; Thu, 12 Sep 2002 15:07:38 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CIqdv23527; Thu, 12 Sep 2002 14:52:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CIgfv23211 for ; Thu, 12 Sep 2002 14:42:41 -0400 Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02854 for ; Thu, 12 Sep 2002 14:40:55 -0400 (EDT) Received: from zbl6c012.us.nortel.com (zbl6c012.us.nortel.com [132.245.205.62]) by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g8CIfJt04099; Thu, 12 Sep 2002 14:41:19 -0400 (EDT) Received: from zbl6c002.us.nortel.com (zbl6c002.corpeast.baynetworks.com [132.245.205.52]) by zbl6c012.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RPMDN7WQ; Thu, 12 Sep 2002 14:41:22 -0400 Received: from tweedy.NortelNetworks.com (tweedy.engeast.baynetworks.com [192.32.135.157]) by zbl6c002.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id NSA9NWZV; Thu, 12 Sep 2002 14:41:20 -0400 Message-Id: <5.0.0.25.0.20020912142746.0254f470@zbl6c002.corpeast.baynetworks.com> X-Sender: khchan@zbl6c002.corpeast.baynetworks.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Thu, 12 Sep 2002 14:39:10 -0400 To: Yacine El Mghazli From: Kwok Ho Chan Subject: Re: [Diffserv] parameters section missing from the Diffserv PIB Cc: "Wijnen, Bert (Bert)" , Lemponen Jussi , diffserv@ietf.org, "rap@ops.ietf.org" In-Reply-To: <3D8042E2.80400@alcatel.fr> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: diffserv-admin@ietf.org Errors-To: diffserv-admin@ietf.org X-BeenThere: diffserv@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , Yacine, Jussi: The Diffserv PIB already IMPORT Dscp and IfDirection from different modules of the Diffserv MIB. So I did not think there is any issue to also reused the definitions for dsTBParamType and dsIfSchedulerCapsServiceDisc from the Diffserv MIB as advised during IESG review. The Diffserv PIB's references to the Diffserv MIB are clearly specified as: dsIfSchedulerCapsServiceDisc OBJECT-TYPE SYNTAX AutonomousType STATUS current DESCRIPTION "The scheduling discipline for which the set of capabilities specified in this object apply. Object identifiers for several general purpose and well-known scheduling disciplines are shared with and defined in the Diffserv MIB. These include diffServSchedulerPriority, diffServSchedulerWRR, diffServSchedulerWFQ." and dsTBParamType OBJECT-TYPE SYNTAX AutonomousType STATUS current DESCRIPTION "The Metering algorithm associated with the Token-Bucket parameters. zeroDotZero indicates this is unknown. Standard values for generic algorithms are as follows: diffServTBParamSimpleTokenBucket, diffServTBParamAvgRate, diffServTBParamSrTCMBlind, diffServTBParamSrTCMAware, diffServTBParamTrTCMBlind, diffServTBParamTrTCMAware, diffServTBParamTswTCM These are specified in the Diffserv MIB." respectively. I believe the above text is clear. Please advise if improvement can be made. Thanks! -- Kwok -- At 09:31 AM 9/12/02 +0200, Yacine El Mghazli wrote: >I was wondering about this point: > >how are the OIDs identified in the MIB senseful within the PIB ? > >my understanding is that the PIB is an AUTONOMOUS named data structure... >in this context, what is the meaning of an OID referencing nothing in the >PIB itself ? > >thank you for your explanations, >yacine > > > >Wijnen, Bert (Bert) wrote: > >>I think they are the parameters that have been sepcified and identified >>in the diffserv MIB (RFC3289) >>Thanks, >>Bert >> >>>-----Original Message----- >>>From: Lemponen Jussi [mailto:juzi@cs.tut.fi] >>>Sent: woensdag 11 september 2002 23:02 >>>To: diffserv@ietf.org >>>Subject: [Diffserv] parameters section missing from the Diffserv PIB >>> >>> >>> >>> >>>Reading through draft-ietf-diffserv-pib-09.txt, I noticed that >>>the parameters section in the PIB itself is missing. The descriptions >>>for attributes dsTBParamType and dsIfSchedulerCapsServiceDisc do still >>>imply that some parameter definitions should be there. >>> >>> >>>Jussi Lemponen >>>Tampere University of Technology >>>Institute of Communications Engineering >>>_______________________________________________ >>>diffserv mailing list >>>diffserv@ietf.org >>>https://www1.ietf.org/mailman/listinfo/diffserv >>>Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/curre >>nt/maillist.html >>_______________________________________________ >>diffserv mailing list >>diffserv@ietf.org >>https://www1.ietf.org/mailman/listinfo/diffserv >>Archive: >>http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html >> > > _______________________________________________ diffserv mailing list diffserv@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html From mailnull@www1.ietf.org Fri Sep 13 04:25:28 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28316 for ; Fri, 13 Sep 2002 04:25:28 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8D8QoJ08395 for diffserv-archive@odin.ietf.org; Fri, 13 Sep 2002 04:26:50 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8D83mv06970; Fri, 13 Sep 2002 04:03:48 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8D7siv06336 for ; Fri, 13 Sep 2002 03:54:44 -0400 Received: from smail2.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27840 for ; Fri, 13 Sep 2002 03:52:51 -0400 (EDT) Received: from medine.ms.alcatel.fr (medine.ms.alcatel.fr [193.105.117.1]) by smail2.alcatel.fr (ALCANET/NETFR) with ESMTP id g8D7qBCv002904; Fri, 13 Sep 2002 09:52:11 +0200 Received: from ms.ms.alcatel.fr (ms.ms.alcatel.fr [188.9.12.93]) by medine.ms.alcatel.fr (8.8.8/8.8.8/aar-1.2) with ESMTP id JAA14121; Fri, 13 Sep 2002 09:52:11 +0200 (MET DST) Received: from athos.dinsunnet (athos [188.9.12.98]) by ms.ms.alcatel.fr (8.8.7/8.8.7/aar-1.0) with ESMTP id JAA14776; Fri, 13 Sep 2002 09:53:20 +0200 (MET DST) Received: from alcatel.fr by athos.dinsunnet (8.9.1b+Sun/SMI-SVR4) id JAA26388; Fri, 13 Sep 2002 09:55:59 +0200 (MET DST) Message-ID: <3D8199AF.6080004@alcatel.fr> Date: Fri, 13 Sep 2002 09:54:23 +0200 From: Yacine El Mghazli Organization: Alcate R&I User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: fr-fr MIME-Version: 1.0 To: Kwok Ho Chan CC: "Wijnen, Bert (Bert)" , Lemponen Jussi , diffserv@ietf.org, "rap@ops.ietf.org" Subject: Re: [Diffserv] parameters section missing from the Diffserv PIB References: <5.0.0.25.0.20020912142746.0254f470@zbl6c002.corpeast.baynetworks.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-milter (http://amavis.org/) Content-Transfer-Encoding: 7bit Sender: diffserv-admin@ietf.org Errors-To: diffserv-admin@ietf.org X-BeenThere: diffserv@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Kwok Ho Chan wrote: > Yacine, Jussi: > The Diffserv PIB already IMPORT Dscp and IfDirection from different > modules of > the Diffserv MIB. So I did not think there is any issue to also reused > the definitions ok for reuse but here we're talking about OIDs... my question is: what is the signification of MIB-specific OIDs within a PIB ? in the previous versions of the PIB draft, these were identified by PRIDS, they pointed towards a PRC within the same PIB... how does it work now ? thanks, yacine > for dsTBParamType and dsIfSchedulerCapsServiceDisc from the Diffserv MIB as > advised during IESG review. > > The Diffserv PIB's references to the Diffserv MIB are clearly specified as: > > dsIfSchedulerCapsServiceDisc OBJECT-TYPE > SYNTAX AutonomousType > STATUS current > DESCRIPTION > "The scheduling discipline for which the set of capabilities > specified in this object apply. Object identifiers for several > general purpose and well-known scheduling disciplines are > shared with and defined in the Diffserv MIB. > > These include diffServSchedulerPriority, > diffServSchedulerWRR, diffServSchedulerWFQ." > > and > > dsTBParamType OBJECT-TYPE > SYNTAX AutonomousType > STATUS current > DESCRIPTION > "The Metering algorithm associated with the > Token-Bucket parameters. zeroDotZero indicates this > is unknown. > Standard values for generic algorithms are as follows: > diffServTBParamSimpleTokenBucket, diffServTBParamAvgRate, > diffServTBParamSrTCMBlind, diffServTBParamSrTCMAware, > diffServTBParamTrTCMBlind, diffServTBParamTrTCMAware, > diffServTBParamTswTCM > > These are specified in the Diffserv MIB." > > respectively. > > I believe the above text is clear. > Please advise if improvement can be made. > Thanks! > -- Kwok -- > > > At 09:31 AM 9/12/02 +0200, Yacine El Mghazli wrote: > >> I was wondering about this point: >> >> how are the OIDs identified in the MIB senseful within the PIB ? >> >> my understanding is that the PIB is an AUTONOMOUS named data >> structure... in this context, what is the meaning of an OID >> referencing nothing in the PIB itself ? >> >> thank you for your explanations, >> yacine >> >> >> >> Wijnen, Bert (Bert) wrote: >> >>> I think they are the parameters that have been sepcified and >>> identified in the diffserv MIB (RFC3289) >>> Thanks, >>> Bert >>> >>>> -----Original Message----- >>>> From: Lemponen Jussi [mailto:juzi@cs.tut.fi] >>>> Sent: woensdag 11 september 2002 23:02 >>>> To: diffserv@ietf.org >>>> Subject: [Diffserv] parameters section missing from the Diffserv PIB >>>> >>>> >>>> >>>> >>>> Reading through draft-ietf-diffserv-pib-09.txt, I noticed that >>>> the parameters section in the PIB itself is missing. The descriptions >>>> for attributes dsTBParamType and dsIfSchedulerCapsServiceDisc do still >>>> imply that some parameter definitions should be there. >>>> >>>> >>>> Jussi Lemponen >>>> Tampere University of Technology >>>> Institute of Communications Engineering >>>> _______________________________________________ >>>> diffserv mailing list >>>> diffserv@ietf.org >>>> https://www1.ietf.org/mailman/listinfo/diffserv >>>> Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/curre >>> >>> nt/maillist.html >>> _______________________________________________ >>> diffserv mailing list >>> diffserv@ietf.org >>> https://www1.ietf.org/mailman/listinfo/diffserv >>> Archive: >>> http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html >>> >>> >> >> > > _______________________________________________ diffserv mailing list diffserv@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html From mailnull@www1.ietf.org Fri Sep 13 13:48:27 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13523 for ; Fri, 13 Sep 2002 13:48:26 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8DHnhl06223 for diffserv-archive@odin.ietf.org; Fri, 13 Sep 2002 13:49:43 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8DHUev05020; Fri, 13 Sep 2002 13:30:40 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8DHJLv04664 for ; Fri, 13 Sep 2002 13:19:22 -0400 Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12694 for ; Fri, 13 Sep 2002 13:17:35 -0400 (EDT) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g8DHIk718965 for ; Fri, 13 Sep 2002 13:18:47 -0400 (EDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Fri, 13 Sep 2002 19:18:46 +0200 Message-ID: From: "Wijnen, Bert (Bert)" To: Yacine El Mghazli , Kwok Ho Chan Cc: "Wijnen, Bert (Bert)" , Lemponen Jussi , diffserv@ietf.org, rap@ops.ietf.org Subject: RE: [Diffserv] parameters section missing from the Diffserv PIB Date: Fri, 13 Sep 2002 19:18:41 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: diffserv-admin@ietf.org Errors-To: diffserv-admin@ietf.org X-BeenThere: diffserv@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , > Kwok Ho Chan wrote: > > > Yacine, Jussi: > > The Diffserv PIB already IMPORT Dscp and IfDirection from different > > modules of > > the Diffserv MIB. So I did not think there is any issue to > > also reused the definitions > > > > ok for reuse but here we're talking about OIDs... > my question is: what is the signification of MIB-specific > OIDs within a PIB ? > I suspect that you have NOT yet gone to the diffserv MIB to take a look as to what those OIDs are representing. Once you do that, I think it should be pretty clear. Bert > In the previous versions of the PIB draft, these were identified by > PRIDS, they pointed towards a PRC within the same PIB... how does it > work now ? > No, this is incorrect. In earlier versions, they were OBJECT IDENTIFIERS which basically DUPLICATED what was already in the MIB. And because of that duplication I (in my role of PIB/MIB reviewer) recommended that the OIDs from the MIB should be re-used. Bert > thanks, > yacine > > > > for dsTBParamType and dsIfSchedulerCapsServiceDisc from the > Diffserv MIB as > > advised during IESG review. > > > > The Diffserv PIB's references to the Diffserv MIB are > clearly specified as: > > > > dsIfSchedulerCapsServiceDisc OBJECT-TYPE > > SYNTAX AutonomousType > > STATUS current > > DESCRIPTION > > "The scheduling discipline for which the set of > capabilities > > specified in this object apply. Object identifiers > for several > > general purpose and well-known scheduling disciplines are > > shared with and defined in the Diffserv MIB. > > > > These include diffServSchedulerPriority, > > diffServSchedulerWRR, diffServSchedulerWFQ." > > > > and > > > > dsTBParamType OBJECT-TYPE > > SYNTAX AutonomousType > > STATUS current > > DESCRIPTION > > "The Metering algorithm associated with the > > Token-Bucket parameters. zeroDotZero indicates this > > is unknown. > > Standard values for generic algorithms are as follows: > > diffServTBParamSimpleTokenBucket, diffServTBParamAvgRate, > > diffServTBParamSrTCMBlind, diffServTBParamSrTCMAware, > > diffServTBParamTrTCMBlind, diffServTBParamTrTCMAware, > > diffServTBParamTswTCM > > > > These are specified in the Diffserv MIB." > > > > respectively. > > > > I believe the above text is clear. > > Please advise if improvement can be made. > > Thanks! > > -- Kwok -- > > > > > > At 09:31 AM 9/12/02 +0200, Yacine El Mghazli wrote: > > > >> I was wondering about this point: > >> > >> how are the OIDs identified in the MIB senseful within the PIB ? > >> > >> my understanding is that the PIB is an AUTONOMOUS named data > >> structure... in this context, what is the meaning of an OID > >> referencing nothing in the PIB itself ? > >> > >> thank you for your explanations, > >> yacine > >> > >> > >> > >> Wijnen, Bert (Bert) wrote: > >> > >>> I think they are the parameters that have been sepcified and > >>> identified in the diffserv MIB (RFC3289) > >>> Thanks, > >>> Bert > >>> > >>>> -----Original Message----- > >>>> From: Lemponen Jussi [mailto:juzi@cs.tut.fi] > >>>> Sent: woensdag 11 september 2002 23:02 > >>>> To: diffserv@ietf.org > >>>> Subject: [Diffserv] parameters section missing from the > Diffserv PIB > >>>> > >>>> > >>>> > >>>> > >>>> Reading through draft-ietf-diffserv-pib-09.txt, I noticed that > >>>> the parameters section in the PIB itself is missing. The > descriptions > >>>> for attributes dsTBParamType and > dsIfSchedulerCapsServiceDisc do still > >>>> imply that some parameter definitions should be there. > >>>> > >>>> > >>>> Jussi Lemponen > >>>> Tampere University of Technology > >>>> Institute of Communications Engineering > >>>> _______________________________________________ > >>>> diffserv mailing list > >>>> diffserv@ietf.org > >>>> https://www1.ietf.org/mailman/listinfo/diffserv > >>>> Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/curre >>> >>> nt/maillist.html >>> _______________________________________________ >>> diffserv mailing list >>> diffserv@ietf.org >>> https://www1.ietf.org/mailman/listinfo/diffserv >>> Archive: >>> http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html >>> >>> >> >> > > _______________________________________________ diffserv mailing list diffserv@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html From mailnull@www1.ietf.org Fri Sep 13 13:58:06 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13917 for ; Fri, 13 Sep 2002 13:58:06 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8DHxNN06965 for diffserv-archive@odin.ietf.org; Fri, 13 Sep 2002 13:59:23 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8DHm6v06161; Fri, 13 Sep 2002 13:48:06 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8DHNAv04805 for ; Fri, 13 Sep 2002 13:23:10 -0400 Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12776 for ; Fri, 13 Sep 2002 13:21:23 -0400 (EDT) Received: from zbl6c012.us.nortel.com (zbl6c012.us.nortel.com [132.245.205.62]) by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g8DHLkr13708; Fri, 13 Sep 2002 13:21:46 -0400 (EDT) Received: from zbl6c002.us.nortel.com (zbl6c002.corpeast.baynetworks.com [132.245.205.52]) by zbl6c012.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RPMD3K70; Fri, 13 Sep 2002 13:21:47 -0400 Received: from tweedy.NortelNetworks.com (TWEEDY [192.32.135.157]) by zbl6c002.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id NSA9N8CR; Fri, 13 Sep 2002 13:20:58 -0400 Message-Id: <5.0.0.25.0.20020913100731.02463530@zbl6c002.corpeast.baynetworks.com> X-Sender: khchan@zbl6c002.corpeast.baynetworks.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Fri, 13 Sep 2002 13:18:46 -0400 To: Yacine El Mghazli From: Kwok Ho Chan Subject: Re: [Diffserv] parameters section missing from the Diffserv PIB Cc: "Kwok-Ho Chan" , "Wijnen, Bert (Bert)" , Lemponen Jussi , diffserv@ietf.org, "rap@ops.ietf.org" In-Reply-To: <3D8199AF.6080004@alcatel.fr> References: <5.0.0.25.0.20020912142746.0254f470@zbl6c002.corpeast.baynetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: diffserv-admin@ietf.org Errors-To: diffserv-admin@ietf.org X-BeenThere: diffserv@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , Yacine: Please see response embedded below. Thanks! -- Kwok -- At 09:54 AM 9/13/02 +0200, Yacine El Mghazli wrote: >Kwok Ho Chan wrote: > >>Yacine, Jussi: >>The Diffserv PIB already IMPORT Dscp and IfDirection from different >>modules of >>the Diffserv MIB. So I did not think there is any issue to also reused >>the definitions > > > >ok for reuse but here we're talking about OIDs... >my question is: what is the signification of MIB-specific OIDs within a PIB ? These "OBJECT-IDENTITY" are just constant values used to represent a standardized parameter (more like a global #define in C). They are just as if the "OBJECT-IDENTITY" is defined in a PIB. We are thinking of new PIBs reusing technology dependent definitions in either existing PIBs or MIBs, whenever possible. Hope this answered your concerns. >in the previous versions of the PIB draft, these were identified by PRIDS, >they pointed towards a PRC within the same PIB... how does it work now ? In DSPIB-06, IfSchedulerCapsServiceDisc and TBParamType were of type "OBJECT IDENTIFIER", referencing objects of type "OBJECT-IDENTITY", for example qosTBParamSimpleTokenBucket and qosSchedulerPriority. Now they are of type "AutonomousType" which are TCs with syntax of "OBJECT IDENTIFIER", as defined in RFC 2579 (SNMPv2-TC). Referencing objects of type "OBJECT-IDENTITY", for example diffServTBParamSimpleTokenBucket and diffServSchedulerPriority. Hence there is no change from the compiler point of view, and no change from a usage point of view. This is not related to PRIDS. >thanks, >yacine > > >>for dsTBParamType and dsIfSchedulerCapsServiceDisc from the Diffserv MIB as >>advised during IESG review. >>The Diffserv PIB's references to the Diffserv MIB are clearly specified as: >> dsIfSchedulerCapsServiceDisc OBJECT-TYPE >> SYNTAX AutonomousType >> STATUS current >> DESCRIPTION >> "The scheduling discipline for which the set of capabilities >> specified in this object apply. Object identifiers for several >> general purpose and well-known scheduling disciplines are >> shared with and defined in the Diffserv MIB. >> These include diffServSchedulerPriority, >> diffServSchedulerWRR, diffServSchedulerWFQ." >>and >> dsTBParamType OBJECT-TYPE >> SYNTAX AutonomousType >> STATUS current >> DESCRIPTION >> "The Metering algorithm associated with the >> Token-Bucket parameters. zeroDotZero indicates this >> is unknown. >> Standard values for generic algorithms are as follows: >> diffServTBParamSimpleTokenBucket, diffServTBParamAvgRate, >> diffServTBParamSrTCMBlind, diffServTBParamSrTCMAware, >> diffServTBParamTrTCMBlind, diffServTBParamTrTCMAware, >> diffServTBParamTswTCM >> These are specified in the Diffserv MIB." >>respectively. >>I believe the above text is clear. >>Please advise if improvement can be made. >>Thanks! >>-- Kwok -- >> >>At 09:31 AM 9/12/02 +0200, Yacine El Mghazli wrote: >> >>>I was wondering about this point: >>> >>>how are the OIDs identified in the MIB senseful within the PIB ? >>> >>>my understanding is that the PIB is an AUTONOMOUS named data >>>structure... in this context, what is the meaning of an OID referencing >>>nothing in the PIB itself ? >>> >>>thank you for your explanations, >>>yacine >>> >>> >>> >>>Wijnen, Bert (Bert) wrote: >>> >>>>I think they are the parameters that have been sepcified and identified >>>>in the diffserv MIB (RFC3289) >>>>Thanks, >>>>Bert >>>> >>>>>-----Original Message----- >>>>>From: Lemponen Jussi [mailto:juzi@cs.tut.fi] >>>>>Sent: woensdag 11 september 2002 23:02 >>>>>To: diffserv@ietf.org >>>>>Subject: [Diffserv] parameters section missing from the Diffserv PIB >>>>> >>>>> >>>>> >>>>> >>>>>Reading through draft-ietf-diffserv-pib-09.txt, I noticed that >>>>>the parameters section in the PIB itself is missing. The descriptions >>>>>for attributes dsTBParamType and dsIfSchedulerCapsServiceDisc do still >>>>>imply that some parameter definitions should be there. >>>>> >>>>> >>>>>Jussi Lemponen >>>>>Tampere University of Technology >>>>>Institute of Communications Engineering >>>>>_______________________________________________ >>>>>diffserv mailing list >>>>>diffserv@ietf.org >>>>>https://www1.ietf.org/mailman/listinfo/diffserv >>>>>Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/curre >>>> >>>>nt/maillist.html >>>>_______________________________________________ >>>>diffserv mailing list >>>>diffserv@ietf.org >>>>https://www1.ietf.org/mailman/listinfo/diffserv >>>>Archive: >>>>http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html >>> > _______________________________________________ diffserv mailing list diffserv@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html From mailnull@www1.ietf.org Mon Sep 16 08:56:59 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03137 for ; Mon, 16 Sep 2002 08:56:59 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8GCwFp28848 for diffserv-archive@odin.ietf.org; Mon, 16 Sep 2002 08:58:15 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8GCiAv28183; Mon, 16 Sep 2002 08:44:10 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8GCVIv27293 for ; Mon, 16 Sep 2002 08:31:18 -0400 Received: from smail3.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02165 for ; Mon, 16 Sep 2002 08:29:31 -0400 (EDT) Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163]) by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id g8GCP8iB010209; Mon, 16 Sep 2002 14:25:08 +0200 Received: from alcatel.fr ([139.54.208.223]) by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a) with ESMTP id 2002091614300497:4676 ; Mon, 16 Sep 2002 14:30:04 +0200 Message-ID: <3D85CDCF.6FA54246@alcatel.fr> Date: Mon, 16 Sep 2002 14:25:51 +0200 From: Yacine.El_Mghazli@alcatel.fr Organization: Alcatel X-Mailer: Mozilla 4.7 [fr] (WinNT; I) X-Accept-Language: fr MIME-Version: 1.0 To: "Wijnen, Bert (Bert)" Cc: Kwok Ho Chan , Lemponen Jussi , diffserv@ietf.org, rap@ops.ietf.org Subject: Re: [Diffserv] parameters section missing from the Diffserv PIB References: X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at 09/16/2002 14:30:05, Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at 09/16/2002 14:30:08 Content-Type: text/plain; charset=iso-8859-1 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g8GCVIv27294 Sender: diffserv-admin@ietf.org Errors-To: diffserv-admin@ietf.org X-BeenThere: diffserv@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit please see bellow "Wijnen, Bert (Bert)" a écrit : > > > Kwok Ho Chan wrote: > > > > > Yacine, Jussi: > > > The Diffserv PIB already IMPORT Dscp and IfDirection from different > > > modules of > > > the Diffserv MIB. So I did not think there is any issue to > > > also reused the definitions > > > > > > > > ok for reuse but here we're talking about OIDs... > > my question is: what is the signification of MIB-specific > > OIDs within a PIB ? > > > I suspect that you have NOT yet gone to the diffserv MIB to take > a look as to what those OIDs are representing. Once you do that, > I think it should be pretty clear. > I suspect that you suspect easily... let me know if I cant ask questions about things I dont understand (be sure I looked for answers before asking on the list). ** example: diffServTBParamSimpleTokenBucket OID = mib-2.97.3.1 this OID has a meaning in the MIB tree, but it has not in the PIB tree. it seems that it's just a pointer towards the MIB and I was wondering about the conssistency with the PIB namespace. thank you Kwok for your explanations yacine > Bert > > In the previous versions of the PIB draft, these were identified by > > PRIDS, they pointed towards a PRC within the same PIB... how does it > > work now ? > > > No, this is incorrect. In earlier versions, they were OBJECT IDENTIFIERS > which basically DUPLICATED what was already in the MIB. And because of > that duplication I (in my role of PIB/MIB reviewer) recommended that the > OIDs from the MIB should be re-used. > > Bert > > thanks, > > yacine > > > > > > > for dsTBParamType and dsIfSchedulerCapsServiceDisc from the > > Diffserv MIB as > > > advised during IESG review. > > > > > > The Diffserv PIB's references to the Diffserv MIB are > > clearly specified as: > > > > > > dsIfSchedulerCapsServiceDisc OBJECT-TYPE > > > SYNTAX AutonomousType > > > STATUS current > > > DESCRIPTION > > > "The scheduling discipline for which the set of > > capabilities > > > specified in this object apply. Object identifiers > > for several > > > general purpose and well-known scheduling disciplines are > > > shared with and defined in the Diffserv MIB. > > > > > > These include diffServSchedulerPriority, > > > diffServSchedulerWRR, diffServSchedulerWFQ." > > > > > > and > > > > > > dsTBParamType OBJECT-TYPE > > > SYNTAX AutonomousType > > > STATUS current > > > DESCRIPTION > > > "The Metering algorithm associated with the > > > Token-Bucket parameters. zeroDotZero indicates this > > > is unknown. > > > Standard values for generic algorithms are as follows: > > > diffServTBParamSimpleTokenBucket, diffServTBParamAvgRate, > > > diffServTBParamSrTCMBlind, diffServTBParamSrTCMAware, > > > diffServTBParamTrTCMBlind, diffServTBParamTrTCMAware, > > > diffServTBParamTswTCM > > > > > > These are specified in the Diffserv MIB." > > > > > > respectively. > > > > > > I believe the above text is clear. > > > Please advise if improvement can be made. > > > Thanks! > > > -- Kwok -- > > > > > > > > > At 09:31 AM 9/12/02 +0200, Yacine El Mghazli wrote: > > > > > >> I was wondering about this point: > > >> > > >> how are the OIDs identified in the MIB senseful within the PIB ? > > >> > > >> my understanding is that the PIB is an AUTONOMOUS named data > > >> structure... in this context, what is the meaning of an OID > > >> referencing nothing in the PIB itself ? > > >> > > >> thank you for your explanations, > > >> yacine > > >> > > >> > > >> > > >> Wijnen, Bert (Bert) wrote: > > >> > > >>> I think they are the parameters that have been sepcified and > > >>> identified in the diffserv MIB (RFC3289) > > >>> Thanks, > > >>> Bert > > >>> > > >>>> -----Original Message----- > > >>>> From: Lemponen Jussi [mailto:juzi@cs.tut.fi] > > >>>> Sent: woensdag 11 september 2002 23:02 > > >>>> To: diffserv@ietf.org > > >>>> Subject: [Diffserv] parameters section missing from the > > Diffserv PIB > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> Reading through draft-ietf-diffserv-pib-09.txt, I noticed that > > >>>> the parameters section in the PIB itself is missing. The > > descriptions > > >>>> for attributes dsTBParamType and > > dsIfSchedulerCapsServiceDisc do still > > >>>> imply that some parameter definitions should be there. > > >>>> > > >>>> > > >>>> Jussi Lemponen > > >>>> Tampere University of Technology > > >>>> Institute of Communications Engineering > > >>>> _______________________________________________ > > >>>> diffserv mailing list > > >>>> diffserv@ietf.org > > >>>> https://www1.ietf.org/mailman/listinfo/diffserv > > >>>> Archive: > http://www.ietf.org/mail-archive/working-groups/diffserv/curre > >>> > >>> nt/maillist.html > >>> _______________________________________________ > >>> diffserv mailing list > >>> diffserv@ietf.org > >>> https://www1.ietf.org/mailman/listinfo/diffserv > >>> Archive: > >>> http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html > >>> > >>> > >> > >> > > > > _______________________________________________ diffserv mailing list diffserv@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html From mailnull@www1.ietf.org Mon Sep 16 20:27:01 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20631 for ; Mon, 16 Sep 2002 20:27:01 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8H0SNh32726 for diffserv-archive@odin.ietf.org; Mon, 16 Sep 2002 20:28:23 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8H0H5v32369; Mon, 16 Sep 2002 20:17:09 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8H07cv32158 for ; Mon, 16 Sep 2002 20:07:38 -0400 Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20322 for ; Mon, 16 Sep 2002 20:05:46 -0400 (EDT) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g8H070o17214 for ; Mon, 16 Sep 2002 20:07:00 -0400 (EDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Tue, 17 Sep 2002 02:06:59 +0200 Message-ID: From: "Wijnen, Bert (Bert)" To: Yacine.El_Mghazli@alcatel.fr Cc: Kwok Ho Chan , Lemponen Jussi , diffserv@ietf.org, rap@ops.ietf.org Subject: RE: [Diffserv] parameters section missing from the Diffserv PIB Date: Tue, 17 Sep 2002 02:06:58 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: diffserv-admin@ietf.org Errors-To: diffserv-admin@ietf.org X-BeenThere: diffserv@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , > > > ok for reuse but here we're talking about OIDs... > > > my question is: what is the signification of MIB-specific > > > OIDs within a PIB ? > > > > > I suspect that you have NOT yet gone to the diffserv MIB to take > > a look as to what those OIDs are representing. Once you do that, > > I think it should be pretty clear. > > > > I suspect that you suspect easily... let me know if I cant ask questions > about things I dont understand (be sure I looked for answers before > asking on the list). > You can ask question. No problem with that... but on the following: > ** example: > diffServTBParamSimpleTokenBucket OID = mib-2.97.3.1 > this OID has a meaning in the MIB tree, but it has not in the PIB tree. > it seems that it's just a pointer towards the MIB and I was wondering > about the conssistency with the PIB namespace. > It seems quite obvious to me (and I think Kwok also tried to explain), the descrition says: diffServTBParamSimpleTokenBucket OBJECT-IDENTITY STATUS current DESCRIPTION "Two Parameter Token Bucket Meter as described in the Informal Differentiated Services Model section 5.2.3." ::= { diffServTBMeters 1 } So, this is an OBJECT-IDENTITY. See RFC2578, sect 6 for an explantion of what it is used for. In this case, it identifies (by OID) a specific type of Token Bucket Meter. Such a meter can be used in a MIB, but it can also be used in a PIB. And when you want to indicate that you are using this type of meter, then you can indicate so by using the above OID in the appropriate object (attribute), no matter if that object is defined in a MIB or in a PIB. Typically the OID is the value that is assigned to a object with a SYNTAX of AutonomousType (as is the case in both the MIB and the PIB). Hope this helps more. Bert > thank you Kwok for your explanations > yacine > > > > Bert > > > In the previous versions of the PIB draft, these were > identified by > > > PRIDS, they pointed towards a PRC within the same PIB... > how does it > > > work now ? > > > > > No, this is incorrect. In earlier versions, they were > OBJECT IDENTIFIERS > > which basically DUPLICATED what was already in the MIB. And > because of > > that duplication I (in my role of PIB/MIB reviewer) > recommended that the > > OIDs from the MIB should be re-used. > > > > Bert > > > thanks, > > > yacine > > > > > > > > > > for dsTBParamType and dsIfSchedulerCapsServiceDisc from the > > > Diffserv MIB as > > > > advised during IESG review. > > > > > > > > The Diffserv PIB's references to the Diffserv MIB are > > > clearly specified as: > > > > > > > > dsIfSchedulerCapsServiceDisc OBJECT-TYPE > > > > SYNTAX AutonomousType > > > > STATUS current > > > > DESCRIPTION > > > > "The scheduling discipline for which the set of > > > capabilities > > > > specified in this object apply. Object identifiers > > > for several > > > > general purpose and well-known scheduling > disciplines are > > > > shared with and defined in the Diffserv MIB. > > > > > > > > These include diffServSchedulerPriority, > > > > diffServSchedulerWRR, diffServSchedulerWFQ." > > > > > > > > and > > > > > > > > dsTBParamType OBJECT-TYPE > > > > SYNTAX AutonomousType > > > > STATUS current > > > > DESCRIPTION > > > > "The Metering algorithm associated with the > > > > Token-Bucket parameters. zeroDotZero indicates this > > > > is unknown. > > > > Standard values for generic algorithms are as follows: > > > > diffServTBParamSimpleTokenBucket, > diffServTBParamAvgRate, > > > > diffServTBParamSrTCMBlind, diffServTBParamSrTCMAware, > > > > diffServTBParamTrTCMBlind, diffServTBParamTrTCMAware, > > > > diffServTBParamTswTCM > > > > > > > > These are specified in the Diffserv MIB." > > > > > > > > respectively. > > > > > > > > I believe the above text is clear. > > > > Please advise if improvement can be made. > > > > Thanks! > > > > -- Kwok -- > > > > > > > > > > > > At 09:31 AM 9/12/02 +0200, Yacine El Mghazli wrote: > > > > > > > >> I was wondering about this point: > > > >> > > > >> how are the OIDs identified in the MIB senseful within > the PIB ? > > > >> > > > >> my understanding is that the PIB is an AUTONOMOUS named data > > > >> structure... in this context, what is the meaning of an OID > > > >> referencing nothing in the PIB itself ? > > > >> > > > >> thank you for your explanations, > > > >> yacine > > > >> > > > >> > > > >> > > > >> Wijnen, Bert (Bert) wrote: > > > >> > > > >>> I think they are the parameters that have been sepcified and > > > >>> identified in the diffserv MIB (RFC3289) > > > >>> Thanks, > > > >>> Bert > > > >>> > > > >>>> -----Original Message----- > > > >>>> From: Lemponen Jussi [mailto:juzi@cs.tut.fi] > > > >>>> Sent: woensdag 11 september 2002 23:02 > > > >>>> To: diffserv@ietf.org > > > >>>> Subject: [Diffserv] parameters section missing from the > > > Diffserv PIB > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> Reading through draft-ietf-diffserv-pib-09.txt, I > noticed that > > > >>>> the parameters section in the PIB itself is missing. The > > > descriptions > > > >>>> for attributes dsTBParamType and > > > dsIfSchedulerCapsServiceDisc do still > > > >>>> imply that some parameter definitions should be there. > > > >>>> > > > >>>> > > > >>>> Jussi Lemponen > > > >>>> Tampere University of Technology > > > >>>> Institute of Communications Engineering > > > >>>> _______________________________________________ > > > >>>> diffserv mailing list > > > >>>> diffserv@ietf.org > > > >>>> https://www1.ietf.org/mailman/listinfo/diffserv > > > >>>> Archive: > > http://www.ietf.org/mail-archive/working-groups/diffserv/curre > > >>> > > >>> nt/maillist.html > > >>> _______________________________________________ > > >>> diffserv mailing list > > >>> diffserv@ietf.org > > >>> https://www1.ietf.org/mailman/listinfo/diffserv > > >>> Archive: > > >>> http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html > >>> > >>> > >> > >> > > > > _______________________________________________ diffserv mailing list diffserv@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html From mailnull@www1.ietf.org Thu Sep 19 14:18:51 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17201 for ; Thu, 19 Sep 2002 14:18:51 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8JIKDR28071 for diffserv-archive@odin.ietf.org; Thu, 19 Sep 2002 14:20:13 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JI2dv26180; Thu, 19 Sep 2002 14:02:40 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JHjwv25640 for ; Thu, 19 Sep 2002 13:45:58 -0400 Received: from asura.bits-pilani.ac.in ([202.54.26.114]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15835 for ; Thu, 19 Sep 2002 13:44:05 -0400 (EDT) Received: from prithvi.bits-pilani.ac.in (prithvi.bits-pilani.ac.in [172.17.0.4]) by asura.bits-pilani.ac.in (8.11.2/8.9.3) with ESMTP id g8JHnSi31791 for ; Thu, 19 Sep 2002 23:19:28 +0530 Date: Thu, 19 Sep 2002 23:13:10 +0530 (IST) From: Sachin Prasad To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Diffserv] Ingress Node Working Sender: diffserv-admin@ietf.org Errors-To: diffserv-admin@ietf.org X-BeenThere: diffserv@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , Dear all, I am working on one project over diff serve and want to know in detail about working of ingress node and what are the working blocks in ingress node. Thanks and Regards, ********************** Sachin Prasad GN - 116, BITS Pilani. 333031 PH-(0159)7642781 ********************** _______________________________________________ diffserv mailing list diffserv@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html From mailnull@www1.ietf.org Fri Sep 20 03:42:46 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA15518 for ; Fri, 20 Sep 2002 03:42:46 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8K7iD513137 for diffserv-archive@odin.ietf.org; Fri, 20 Sep 2002 03:44:13 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8K7Ouv11933; Fri, 20 Sep 2002 03:24:56 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8K7Fav11664 for ; Fri, 20 Sep 2002 03:15:36 -0400 Received: from mail-gw2.hursley.ibm.com (mail-gw2.hursley.ibm.com [194.196.110.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA15076 for ; Fri, 20 Sep 2002 03:13:37 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=mail-gw2.hursley.ibm.com) by mail-gw2.hursley.ibm.com with esmtp (Exim 4.10) id 17sI06-0005Z6-00; Fri, 20 Sep 2002 08:14:54 +0100 Received: from [9.20.45.103] (helo=sp15en17.hursley.ibm.com) by mail-gw2.hursley.ibm.com with esmtp (Exim 4.10) id 17sI05-0005Z1-00; Fri, 20 Sep 2002 08:14:53 +0100 Received: from hursley.ibm.com (dhcp22-199.zurich.ibm.com [9.4.22.199]) by sp15en17.hursley.ibm.com (AIX4.3/8.9.3/8.9.3) with ESMTP id IAA69528; Fri, 20 Sep 2002 08:14:52 +0100 Message-ID: <3D8ACAF6.5C2F89E2@hursley.ibm.com> Date: Fri, 20 Sep 2002 09:15:02 +0200 From: Brian E Carpenter Organization: IBM X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,fr,de MIME-Version: 1.0 To: Sachin Prasad CC: diffserv@ietf.org Subject: Re: [Diffserv] Ingress Node Working References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: diffserv-admin@ietf.org Errors-To: diffserv-admin@ietf.org X-BeenThere: diffserv@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Please take this sort of question to the diffserv implementation list. See http://www.tip.csiro.au/dsimplementation/ Brian Carpenter diffserv co-chair Sachin Prasad wrote: > > Dear all, > > I am working on one project over diff serve and want to know in detail > about working of ingress node and what are the working blocks in ingress > node. > > Thanks and Regards, > > ********************** > Sachin Prasad > GN - 116, > BITS Pilani. > 333031 > PH-(0159)7642781 > ********************** _______________________________________________ diffserv mailing list diffserv@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html