From owner-issll@mercury.lcs.mit.edu Thu Oct 7 14:25:11 1999 Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23120 for ; Thu, 7 Oct 1999 14:25:10 -0400 (EDT) Received: (from daemon@localhost) by mercury.lcs.mit.edu (8.9.1/8.9.1) id NAA08060 for issll-outgoing; Thu, 7 Oct 1999 13:16:07 -0400 (EDT) Received: from old-callisto.ftel.co.uk (big-relay-1.ftel.co.uk [192.65.220.123]) by mercury.lcs.mit.edu (8.9.1/8.9.1) with ESMTP id NAA08056 for ; Thu, 7 Oct 1999 13:16:05 -0400 (EDT) Received: (from root@localhost) by old-callisto.ftel.co.uk (8.9.3/8.9.3/Revision:1.42) id SAA22108 for issll@mercury.lcs.mit.edu; Thu, 7 Oct 1999 18:16:04 +0100 (BST) Received: from callisto.ftel.co.uk (root@callisto.ftel.co.uk [172.16.2.99]) by old-callisto.ftel.co.uk (8.9.3/8.9.3/Revision:1.42/scanin/yp) with ESMTP id SAA22103 for ; Thu, 7 Oct 1999 18:16:03 +0100 (BST) Received: from ftel.co.uk (gcope@localhost.ftel.co.uk [127.0.0.1]) by callisto.ftel.co.uk (8.8.7/8.8.7/Revision:1.48/yp) with ESMTP id SAA01860; Thu, 7 Oct 1999 18:15:55 +0100 (BST) Message-ID: <37FCD54B.310B8189@ftel.co.uk> Date: Thu, 07 Oct 1999 18:15:55 +0100 From: Graham Cope X-Mailer: Mozilla 4.04 [en] (X11; I; SunOS 5.7 sun4u) MIME-Version: 1.0 To: fred@cisco.com CC: issll@mercury.lcs.mit.edu Subject: IP aggregation Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-issll@mercury.lcs.mit.edu Precedence: bulk Content-Transfer-Encoding: 7bit Is there any guarantee that the e2e RESV message will follow the same route as the PATH message? As I understand, the Interior nodes ignore the e2e path messages and 'simply forward it as a normal IP datagram'. Hence they won't set up the backward pointer. Hence the RESV may not follow that same path within the interior, and even pop-out at a different aggregating router. Solution is for the Router Alert to ensure that the backward pointer is set, but for RSVP_E2E_IGNORE to ensure that nothing else is done. Thanks, Graham From owner-issll@mercury.lcs.mit.edu Tue Oct 12 09:29:53 1999 Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13819 for ; Tue, 12 Oct 1999 09:29:53 -0400 (EDT) Received: (from daemon@localhost) by mercury.lcs.mit.edu (8.9.1/8.9.1) id IAA22223 for issll-outgoing; Tue, 12 Oct 1999 08:22:49 -0400 (EDT) Received: from rvs.uni-hannover.de (lanai.rvs.uni-hannover.de [130.75.3.211]) by mercury.lcs.mit.edu (8.9.1/8.9.1) with ESMTP id IAA20504 for ; Tue, 12 Oct 1999 08:22:40 -0400 (EDT) Received: from rvs.uni-hannover.de (hawaii.rvs.uni-hannover.de [130.75.3.203]) by rvs.uni-hannover.de (8.9.1/8.9.1) with ESMTP id OAA27010 for ; Tue, 12 Oct 1999 14:21:50 +0200 (MET DST) Message-ID: <380327DE.22746C18@rvs.uni-hannover.de> Date: Tue, 12 Oct 1999 14:21:50 +0200 From: Eduard Siemens Organization: RVS/ University of Hannover X-Mailer: Mozilla 4.04 [en] (X11; I; SunOS 5.6 sun4u) MIME-Version: 1.0 To: issll@mercury.lcs.mit.edu Subject: DS-over ATM and 802 =?iso-8859-1?Q?Netwi=F3rks?= Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-issll@mercury.lcs.mit.edu Precedence: bulk Content-Transfer-Encoding: 7bit Hello, everyone, are there Drafts availible about Mappings Diff-serv on ATM and 802-Networks? Regards, -- Eduard Siemens Uni Hannover Tel. +49 (0)5132 866123 Fax +49 (0)5132 866124 From owner-issll@mercury.lcs.mit.edu Wed Oct 13 17:16:51 1999 Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04631 for ; Wed, 13 Oct 1999 17:16:50 -0400 (EDT) Received: (from daemon@localhost) by mercury.lcs.mit.edu (8.9.1/8.9.1) id QAA08451 for issll-outgoing; Wed, 13 Oct 1999 16:07:02 -0400 (EDT) Received: from e2.ny.us.ibm.com (e2.ny.us.ibm.com [32.97.182.102]) by mercury.lcs.mit.edu (8.9.1/8.9.1) with ESMTP id QAA07047 for ; Wed, 13 Oct 1999 16:07:00 -0400 (EDT) From: lli@us.ibm.com Received: from southrelay02.raleigh.ibm.com (southrelay02.raleigh.ibm.com [9.37.3.209]) by e2.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id QAA46692 for ; Wed, 13 Oct 1999 16:06:02 -0400 Received: from d54mta03.raleigh.ibm.com (d54mta03.raleigh.ibm.com [9.67.228.35]) by southrelay02.raleigh.ibm.com (8.8.8m2/NCO v2.05) with SMTP id QAA40772 for ; Wed, 13 Oct 1999 16:06:19 -0400 Received: by d54mta03.raleigh.ibm.com(Lotus SMTP MTA v4.6.5 (863.2 5-20-1999)) id 85256809.006E7031 ; Wed, 13 Oct 1999 16:06:16 -0400 X-Lotus-FromDomain: IBMUS To: issll@mercury.lcs.mit.edu Message-ID: <85256809.006E6B58.00@d54mta03.raleigh.ibm.com> Date: Wed, 13 Oct 1999 16:06:34 -0400 Subject: question on draft-ietf-issll-rsvp-aggr-00.txt Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-issll@mercury.lcs.mit.edu Precedence: bulk I have the following questions on the rsvp aggregation draft; perhaps someone can clarify them for me... 1. PathErr from deaggregating router to aggregating router: The original PathErr has the following format: [ ] [ ...][ ] ERROR_SPEC contains Does the draft suggest that the be the deaggregating router, the be "NEW-AGGREGATE-NEEDED", and the be unspecified ("0")? I believe the object still contains the original end-to-end session info; Is this correct? I think the aggregating router needs this info to track which original PATH state (there may be many) is associated with this PathErr. 2. Aggregate Path message: Is the draft adding a object, IN ADDITION TO the original object? I think the original object containing end-to-end session info needs to be retained; otherwise the deaggregating router can not correlate the Aggregate Path message with a waiting PATH state, as suggested at the bottom of section 2.3, "To enable correct updating of the ADSPEC, a deaggregating router may wait for the arrival of an aggregate Path before forwarding the E2E Path." Thank you, Liang Li. From owner-issll@mercury.lcs.mit.edu Wed Oct 13 19:24:59 1999 Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06215 for ; Wed, 13 Oct 1999 19:24:59 -0400 (EDT) Received: (from daemon@localhost) by mercury.lcs.mit.edu (8.9.1/8.9.1) id SAA09327 for issll-outgoing; Wed, 13 Oct 1999 18:34:21 -0400 (EDT) Received: from sol.extremenetworks.com (sol.extremenetworks.com [216.52.8.2]) by mercury.lcs.mit.edu (8.9.1/8.9.1) with ESMTP id SAA09356 for ; Wed, 13 Oct 1999 18:34:15 -0400 (EDT) Received: by ftp.extremenetworks.com with Internet Mail Service (5.5.2448.0) id <36G7RZDP>; Wed, 13 Oct 1999 15:33:44 -0700 Message-ID: From: Andrew Smith To: "'Navin kumar Agrawal'" Cc: "issll (E-mail)" , Int-Serv Mailing List Subject: RE: C, D terms of GS Date: Wed, 13 Oct 1999 15:33:39 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-issll@mercury.lcs.mit.edu Precedence: bulk You wrote: > -----Original Message----- > From: Navin kumar Agrawal [mailto:navin@lgsi.co.in] > Sent: Friday, October 01, 1999 4:45 AM > To: Int-Serv Mailing List > Subject: C, D terms of GS ... > In my case, the link layer media is Ethernet but the it is not used in > the conventional shared media form. Meaning, it is used in the > point-to-point form. So I guess, there is no need to implement SBM. I assume you mean "it is used in the full-duplex form" rather than just point-to-point: even if you have a point-to-point link it might be running half-duplex and so there may well be two senders competing for bandwidth. It is only when you go to full-duplex that you have a single sender that can administer the full bandwidth of the link. However, you still should use SBM protocol, even in this case, in order to make sure that the RSVP messages (and hence the correct accounting for bandwidth and resources) get to go through the right nodes along the layer-2 path between the layer-3 sender (or layer-3 router sending onto the subnet) and the layer-3 receiver (or next hop layer-3 router). The implementation of SBM for the full-duplex case is simplified only in the sense that there is no need to elect who is the DSBM for the segment: in this case the answer is always "me". See the documents at http://www.ietf.org/html.charters/issll-charter.html for more details. [this part of the discussion should really be moved to ISSLL list, CC'ed above - let's drop int-serv from this sub-thread]. Andrew **************************************************************** Andrew Smith tel: +1 (408) 579-2821 Extreme Networks fax: +1 (408) 579-3000 3585 Monroe St. http://www.extremenetworks.com Santa Clara CA 95051-1450 em: andrew@extremenetworks.com **************************************************************** From owner-issll@mercury.lcs.mit.edu Fri Oct 15 09:47:12 1999 Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10965 for ; Fri, 15 Oct 1999 09:47:11 -0400 (EDT) Received: (from daemon@localhost) by mercury.lcs.mit.edu (8.9.1/8.9.1) id IAA17773 for issll-outgoing; Fri, 15 Oct 1999 08:29:36 -0400 (EDT) Received: from s2.smtp.oleane.net (s2.smtp.oleane.net [195.25.12.6]) by mercury.lcs.mit.edu (8.9.1/8.9.1) with ESMTP id IAA17743 for ; Fri, 15 Oct 1999 08:29:34 -0400 (EDT) Received: from Dell (dyn-1-1-247.Cor.dialup.oleane.fr [62.161.8.247]) by s2.smtp.oleane.net with SMTP id OAA92798; Fri, 15 Oct 1999 14:27:47 +0200 (CEST) Message-ID: <007e01bf1708$a62234a0$0701a8c0@oleane.com> From: "Peter Lewis" To: Subject: Media Gateway Control Date: Fri, 15 Oct 1999 14:27:05 +0200 Organization: Upperside MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0077_01BF1719.5AF83360" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-issll@mercury.lcs.mit.edu Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0077_01BF1719.5AF83360 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MGCP, Megaco, H.248: performing seamless interoperation between IP and = PSTN networks. The international rendez-vous in Paris, 15-17 December 1999. More infos:=20 http://www.upperside.fr/bamgc.htm ------=_NextPart_000_0077_01BF1719.5AF83360 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
MGCP, Megaco, H.248: performing seamless = interoperation=20 between IP and PSTN
networks. The international rendez-vous in Paris, = 15-17=20 December 1999.

More infos:
http://www.upperside.fr/bamgc.= htm
 
------=_NextPart_000_0077_01BF1719.5AF83360-- From owner-issll@mercury.lcs.mit.edu Wed Oct 20 17:50:17 1999 Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24430 for ; Wed, 20 Oct 1999 17:50:17 -0400 (EDT) Received: (from daemon@localhost) by mercury.lcs.mit.edu (8.9.1/8.9.1) id QAA11708 for issll-outgoing; Wed, 20 Oct 1999 16:52:38 -0400 (EDT) Received: from adn.alcatel.com (postman.adn.alcatel.com [198.205.32.33]) by mercury.lcs.mit.edu (8.9.1/8.9.1) with ESMTP id QAA15898 for ; Wed, 20 Oct 1999 16:52:35 -0400 (EDT) Received: from postal.adn.alcatel.com (postal [198.205.32.56]) by adn.alcatel.com with ESMTP (8.7.6/8.7.1) id QAA24320 for ; Wed, 20 Oct 1999 16:46:01 -0400 (EDT) Received: from adn.alcatel.com ([198.205.44.66]) by postal.adn.alcatel.com (Netscape Messaging Server 3.6) with ESMTP id AAA2A01 for ; Wed, 20 Oct 1999 16:55:50 -0400 Message-ID: <380E3967.25595598@adn.alcatel.com> Date: Wed, 20 Oct 1999 16:51:35 -0500 From: Sudheer Dharanikota Organization: Alcatel USA X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "issll@mercury.lcs.mit.edu" Subject: Status of draft-stoica-diffserv-dps-00.txt Content-Type: multipart/mixed; boundary="------------AA8F96839A517939497B9425" Sender: owner-issll@mercury.lcs.mit.edu Precedence: bulk This is a multi-part message in MIME format. --------------AA8F96839A517939497B9425 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Does anyone know the status of this draft. thank you, sudheer --------------AA8F96839A517939497B9425 Content-Type: text/x-vcard; charset=us-ascii; name="sudheer.dharanikota.vcf" Content-Description: Card for Sudheer Dharanikota Content-Disposition: attachment; filename="sudheer.dharanikota.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Dharanikota;Sudheer tel;fax:703-724-2005 tel;home:703-421-5622 tel;work:703-724-2631 x-mozilla-html:TRUE url:www.alcatel.com org:Alcatel USA adr:;;44983 Knoll Square;Ashburn;VA;20147;USA version:2.1 email;internet:sudheer.dharanikota title:Principle Member of Technical Staff fn:Sudheer Dharanikota end:vcard --------------AA8F96839A517939497B9425-- From owner-issll@mercury.lcs.mit.edu Thu Oct 21 22:22:35 1999 Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18436 for ; Thu, 21 Oct 1999 22:22:35 -0400 (EDT) Received: (from daemon@localhost) by mercury.lcs.mit.edu (8.9.1/8.9.1) id VAA23546 for issll-outgoing; Thu, 21 Oct 1999 21:30:11 -0400 (EDT) Received: from sol.extremenetworks.com (sol.extremenetworks.com [216.52.8.2]) by mercury.lcs.mit.edu (8.9.1/8.9.1) with ESMTP id VAA23498 for ; Thu, 21 Oct 1999 21:30:09 -0400 (EDT) Received: by ftp.extremenetworks.com with Internet Mail Service (5.5.2448.0) id ; Thu, 21 Oct 1999 18:29:39 -0700 Message-ID: From: Andrew Smith To: "issll (E-mail)" Subject: Updated SBM MIB (draft-ietf-issll-is802-sbm-mib-01.txt) Date: Thu, 21 Oct 1999 18:29:33 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-issll@mercury.lcs.mit.edu Precedence: bulk This was submitted today. You can get a pre-release copy from: ftp://ftp.extremenetworks.com/pub/outgoing/docs/andrew/draft-ietf-issll-is80 2-sbm-mib-01.txt It incorporates many helpful suggestions from Carl Kalbfleisch. Open Issues still remaining: (2) How to represent more detailed e.g. per-queue/per-class information. We could use the per-interface tables from RFC2213/RFC2214 int-serv MIBs but we would then need one of these per queue per interface. this might need ifStackTable to group them together. Could also try to use the intSrvflowQueue object for this. (8) Should counters be zeroed whenever a SBM enters I_AM_DSBM state? (Propose: NO) Opinions and other comments to the ISSLL list please. Andrew **************************************************************** Andrew Smith tel: +1 (408) 579-2821 Extreme Networks fax: +1 (408) 579-3000 3585 Monroe St. http://www.extremenetworks.com Santa Clara CA 95051-1450 em: andrew@extremenetworks.com **************************************************************** From owner-issll@mercury.lcs.mit.edu Mon Oct 25 08:03:09 1999 Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05529 for ; Mon, 25 Oct 1999 08:03:09 -0400 (EDT) Received: (from daemon@localhost) by mercury.lcs.mit.edu (8.9.1/8.9.1) id HAA26469 for issll-outgoing; Mon, 25 Oct 1999 07:00:16 -0400 (EDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mercury.lcs.mit.edu (8.9.1/8.9.1) with ESMTP id HAA26298 for ; Mon, 25 Oct 1999 07:00:14 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03285; Mon, 25 Oct 1999 07:00:14 -0400 (EDT) Message-Id: <199910251100.HAA03285@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: issll@mercury.lcs.mit.edu From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-issll-is802-sbm-mib-01.txt Date: Mon, 25 Oct 1999 07:00:13 -0400 Sender: owner-issll@mercury.lcs.mit.edu Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Integrated Services over Specific Link Layers Working Group of the IETF. Title : Definitions of Managed Parameters for SBM network nodes Author(s) : A. Smith, R. Pabbati Filename : draft-ietf-issll-is802-sbm-mib-01.txt Pages : 32 Date : 22-Oct-99 This memo includes a list of manageable parameters for RSVP/SBM server implementations. These are in addition to those already described in RFC 2206 and RFC 2213. Specifically, it describes parameters for control of the base signaling protocols themselves, as well as some of the admission control decisions. These definitions are not intended to be exhaustive but they have been identified as useful for practical implementations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-issll-is802-sbm-mib-01.txt 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-issll-is802-sbm-mib-01.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. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-issll-is802-sbm-mib-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19991022140027.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-issll-is802-sbm-mib-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-issll-is802-sbm-mib-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19991022140027.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-issll@mercury.lcs.mit.edu Tue Oct 26 08:28:06 1999 Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03182 for ; Tue, 26 Oct 1999 08:28:05 -0400 (EDT) Received: (from daemon@localhost) by mercury.lcs.mit.edu (8.9.1/8.9.1) id HAA01515 for issll-outgoing; Tue, 26 Oct 1999 07:23:50 -0400 (EDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mercury.lcs.mit.edu (8.9.1/8.9.1) with ESMTP id HAA01220 for ; Tue, 26 Oct 1999 07:23:48 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01379; Tue, 26 Oct 1999 07:23:46 -0400 (EDT) Message-Id: <199910261123.HAA01379@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: issll@mercury.lcs.mit.edu From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-issll-is802-sbm-mib-01.txt Date: Tue, 26 Oct 1999 07:23:46 -0400 Sender: owner-issll@mercury.lcs.mit.edu Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Integrated Services over Specific Link Layers Working Group of the IETF. Title : Definitions of Managed Parameters for SBM network nodes Author(s) : A. Smith, R. Pabbati Filename : draft-ietf-issll-is802-sbm-mib-01.txt Pages : 32 Date : 22-Oct-99 This memo includes a list of manageable parameters for RSVP/SBM server implementations. These are in addition to those already described in RFC 2206 and RFC 2213. Specifically, it describes parameters for control of the base signaling protocols themselves, as well as some of the admission control decisions. These definitions are not intended to be exhaustive but they have been identified as useful for practical implementations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-issll-is802-sbm-mib-01.txt 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-issll-is802-sbm-mib-01.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. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-issll-is802-sbm-mib-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19991022140027.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-issll-is802-sbm-mib-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-issll-is802-sbm-mib-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19991022140027.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-issll@mercury.lcs.mit.edu Thu Oct 28 08:17:18 1999 Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16857 for ; Thu, 28 Oct 1999 08:17:17 -0400 (EDT) Received: (from daemon@localhost) by mercury.lcs.mit.edu (8.9.1/8.9.1) id HAA19917 for issll-outgoing; Thu, 28 Oct 1999 07:09:34 -0400 (EDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mercury.lcs.mit.edu (8.9.1/8.9.1) with ESMTP id HAA19987 for ; Thu, 28 Oct 1999 07:09:33 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14020; Thu, 28 Oct 1999 07:09:31 -0400 (EDT) Message-Id: <199910281109.HAA14020@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: issll@mercury.lcs.mit.edu From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-issll-dclass-01.txt Date: Thu, 28 Oct 1999 07:09:31 -0400 Sender: owner-issll@mercury.lcs.mit.edu Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Integrated Services over Specific Link Layers Working Group of the IETF. Title : Format of the RSVP DCLASS Object Author(s) : Y. Bernet Filename : draft-ietf-issll-dclass-01.txt Pages : 6 Date : 27-Oct-99 RSVP signaling may be used to request QoS services and enhance the manageability of application traffic's QoS in a differentiated service (diff-serv or DS) network. When using RSVP with DS networks it is useful to be able to carry carry Differentiated Services Code Points (DSCPs) in RSVP message objects. One example of this is the use of RSVP to arrange for the marking of packets with a particular DSCP upstream from the DS network's ingress point, at the sender or at a previous network's egress router. The DCLASS object is used to represent and carry DSCPs within RSVP messages. This draft specifies the format of the DCLASS object and briefly discusses its use. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-issll-dclass-01.txt 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-issll-dclass-01.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. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-issll-dclass-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19991027140430.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-issll-dclass-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-issll-dclass-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19991027140430.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-issll@mercury.lcs.mit.edu Thu Oct 28 08:27:17 1999 Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17216 for ; Thu, 28 Oct 1999 08:27:16 -0400 (EDT) Received: (from daemon@localhost) by mercury.lcs.mit.edu (8.9.1/8.9.1) id HAA06564 for issll-outgoing; Thu, 28 Oct 1999 07:09:39 -0400 (EDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mercury.lcs.mit.edu (8.9.1/8.9.1) with ESMTP id HAA19935 for ; Thu, 28 Oct 1999 07:09:38 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14032; Thu, 28 Oct 1999 07:09:36 -0400 (EDT) Message-Id: <199910281109.HAA14032@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: issll@mercury.lcs.mit.edu From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-issll-is802-sbm-09.txt Date: Thu, 28 Oct 1999 07:09:36 -0400 Sender: owner-issll@mercury.lcs.mit.edu Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Integrated Services over Specific Link Layers Working Group of the IETF. Title : SBM (Subnet Bandwidth Manager): A Protocol for RSVP-based Admission Control over IEEE 802-style networks Author(s) : R. Yavatkar, D. Hoffman, Y. Bernet, F. Baker Filename : draft-ietf-issll-is802-sbm-09.txt Pages : 67 Date : 27-Oct-99 This document describes a signaling method and protocol for RSVP-based admission control over IEEE 802-style LANs. The protocol is designed to work both with the current generation of IEEE 802 LANs as well as with the recent work completed by the IEEE 802.1 committee. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-issll-is802-sbm-09.txt 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-issll-is802-sbm-09.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. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-issll-is802-sbm-09.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19991027140444.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-issll-is802-sbm-09.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-issll-is802-sbm-09.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19991027140444.I-D@ietf.org> --OtherAccess-- --NextPart--