From rsvp-owner@ISI.EDU  Thu Jun  1 16:49:11 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03313
	for <rsvp-archive@lists.ietf.org>; Thu, 1 Jun 2000 16:49:10 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id LAA18532
	for rsvp-outgoing; Thu, 1 Jun 2000 11:36:32 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id LAA18527
	for <rsvp@zephyr.isi.edu>; Thu, 1 Jun 2000 11:36:31 -0700 (PDT)
Received: from sol.extremenetworks.com (sol.extremenetworks.com [216.52.8.2])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id LAA25529
	for <rsvp@isi.edu>; Thu, 1 Jun 2000 11:37:04 -0700 (PDT)
Received: by SOL with Internet Mail Service (5.5.2650.21)
	id <L7XSTW4G>; Thu, 1 Jun 2000 11:33:22 -0700
Message-ID: <808F64DDB492D3119D3C00508B5D8D733EC90F@SOL>
From: Andrew Smith <andrew@extremenetworks.com>
To: "rap (E-mail)" <rap@iphighway.com>,
        "rsvp@isi. edu (E-mail)"
	 <rsvp@ISI.EDU>
Cc: "'Scott Bradner'" <sob@harvard.edu>, "'Bert Wijnen'" <bwijnen@lucent.com>,
        "Randy Bush (E-mail)" <randy@psg.com>,
        "'mankin@east.isi.edu'"
	 <mankin@ISI.EDU>
Subject: Editorial snafus in RFC 2751 and RFC 2752
Date: Thu, 1 Jun 2000 11:33:20 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-rsvp@ISI.EDU
Precedence: bulk


It has come to our attention that there was an editorial snafu that occurred
sometime last summer during the various edits of the Internet Drafts from
the RAP WG that became RFC 2751 and RFC 2752. At that time, we had an
informal co-ordination of the P-Type assignments within the POLICY_DATA RSVP
object and we messed up and these got switched around before WG and IETF
approval and RFC publication.
 
Unfortunately, people have been implementing these drafts for a while now
and, in fact, there have been significant numbers of copies of
implementation shipped to customers using the original assignments which are
incompatible with the assignments in the RFCs. This leads to headaches.

The assignments in question are as follows:
================================================================
RFC 2752            Identity Representation for RSVP        January 2000

  P-Type (Identity Type)
       Type of identity information contained in this Policy Element
       supplied as the Policy element type (P-type). The Internet
       Assigned Numbers Authority (IANA) acts as a registry for policy
       element types for identity as described in the [POL-EXT].
       Initially, the registry contains the following P-Types for
       identity:

       1   AUTH_USER       Authentication scheme to identify users

       2   AUTH_APP        Authentication scheme to identify
                           applications
=================================================================

RFC 2751      Signaled Preemption Priority Policy Element   January 2000

   P-Type: 16 bits
      PREEMPTION_PRI  = 3

=================================================================

The original assignments, prior to last summer, were as follows:

1  PREEMPTION_PRI
2  AUTH_USER
3  AUTH_APP

===============================================================

So, what to do about this? The "correct" answer is to say that people were
stupid to ship product before the RFCs were out and that they should fix
things themselves. However, this would cause serious deployment headaches
that could easily affect the larger choice of whether or not to deploy
RSVP-based products in a customers network. And it is a bad way to reward
the implementers whose early experiences led to *significantly* better
protocol-definition documents.

It is up to the RAP WG, as the sponsor of these RFCs, to determine what the
best course of action is, in consultation with the RSVP WG of course. If we,
the WG, were to recommend to change the RFCs back to the original P-Type
values (and re-issue these 2 RFCs) then I hope that the IESG would be
sympathetic (I guess we should ask them first really ... I did ask Scott
Bradner and he suggested that the WG should first come to a decision as to
what it wants to do).

So, please express your opinions ASAP to the RAP mailing list on this
potential change. We will try to gauge the consensus to determine our next
steps, if any.

Thank you,

Andrew Smith
RAP WG co-chair




From rsvp-owner@ISI.EDU  Thu Jun  1 21:40:13 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08462
	for <rsvp-archive@lists.ietf.org>; Thu, 1 Jun 2000 21:40:13 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id QAA03312
	for rsvp-outgoing; Thu, 1 Jun 2000 16:33:43 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id QAA03306
	for <rsvp@zephyr.isi.edu>; Thu, 1 Jun 2000 16:33:41 -0700 (PDT)
Received: from public5.sta.net.cn (public5.sta.net.cn [202.96.199.234])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id QAA09419
	for <rsvp@isi.edu>; Thu, 1 Jun 2000 16:34:02 -0700 (PDT)
Received: from virgo2 (branch-1-i147.sta.net.cn [61.129.20.147])
	by public5.sta.net.cn (8.9.3/8.9.3) with SMTP id HAA10707;
	Fri, 2 Jun 2000 07:17:35 +0800 (CST)
Message-Id: <200006012317.HAA10707@public5.sta.net.cn>
From: webmaster <xbctd@hotmail.com>
To: 038 <xbctd@hotmail.com>
Date: Fri, 02 Jun 2000 07:31:24 +0800
Subject: 快来领取！！！
Reply-To: webmaster@myvirgo.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Priority: 3
Sender: owner-rsvp@ISI.EDU
Precedence: bulk
Content-Transfer-Encoding: 7bit

亲爱的朋友:
您的好友向您诚意推荐MyVirgo.com.
在第二轮活动中，已经有50名会员获得我们的大奖！！！
您的朋友已经为您在我们举办的第三轮疯狂大抽奖活动报了名
您只需要到
http://www.myvirgo.com/register/regform2.html
注册，就可以参加。
奖品丰厚，有：
Apple iBOOK G3 手提电脑
SONY PlayStation 2
JVC White Magic MD随身听
CASIO G-Shock 新款手表
国际知名化妆品
如果您对本活动有任何疑问,欢迎给我们来信:
webmaster@myvirgo.com

------------------------------------------
This message was sent to you by
Name: webmaster
Email Address: xbctd@hotmail.com
IP Address: VIRGO2
------------------------------------------

Using Aureate Group Mail Free Edition
Find out more about this product and try it 
for free at: http://www.group-mail.com/1



From rsvp-owner@ISI.EDU  Thu Jun  1 22:21:00 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09727
	for <rsvp-archive@lists.ietf.org>; Thu, 1 Jun 2000 22:20:59 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id RAA07835
	for rsvp-outgoing; Thu, 1 Jun 2000 17:45:31 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id RAA07830
	for <rsvp@zephyr.isi.edu>; Thu, 1 Jun 2000 17:45:29 -0700 (PDT)
Received: from mail3.sh163.net ([202.96.194.134])
	by venera.isi.edu (8.9.3/8.9.3) with SMTP id RAA12655
	for <rsvp@isi.edu>; Thu, 1 Jun 2000 17:45:58 -0700 (PDT)
Message-Id: <200006020045.RAA12655@venera.isi.edu>
Received: (Rockmail 2468 invoked from network); 1 Jun 2000 03:41:41 -0000
Received: from branch-1-j96.sta.net.cn (HELO virgo3) ([61.129.21.96]) (envelope-sender <xbctd@hotmail.com>)
          by 202.96.194.134 (Rockmail) with SMTP
          for <rsview@china.com>; 1 Jun 2000 03:41:41 -0000
From: webmaster <xbctd@hotmail.com>
To: 038 <xbctd@hotmail.com>
Date: Thu, 01 Jun 2000 11:49:32 +0800
Subject: 快来领取！！！
Reply-To: webmaster@myvirgo.com
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=XX64E56461-008564E5XX
Content-Transfer-Encoding: 7bit
X-Priority: 3
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

This is a Multipart MIME message. Since your mail reader
does not understand this format, some or all of this message may not be legible.

--XX64E56461-008564E5XX
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

=C7=D7=B0=AE=B5=C4=C5=F3=D3=D1:
=C4=FA=B5=C4=BA=C3=D3=D1=CF=F2=C4=FA=B3=CF=D2=E2=CD=C6=BC=F6MyVirgo.com.
=D4=DA=B5=DA=B6=FE=C2=D6=BB=EE=B6=AF=D6=D0=A3=AC=D2=D1=BE=AD=D3=D050=C3=FB=
=BB=E1=D4=B1=BB=F1=B5=C3=CE=D2=C3=C7=B5=C4=B4=F3=BD=B1=A3=A1=A3=A1=A3=A1
=C4=FA=B5=C4=C5=F3=D3=D1=D2=D1=BE=AD=CE=AA=C4=FA=D4=DA=CE=D2=C3=C7=BE=D9=B0=
=EC=B5=C4=B5=DA=C8=FD=C2=D6=B7=E8=BF=F1=B4=F3=B3=E9=BD=B1=BB=EE=B6=AF=B1=A8=
=C1=CB=C3=FB
=C4=FA=D6=BB=D0=E8=D2=AA=B5=BD
http://www.myvirgo.com/register/regform2.html
=D7=A2=B2=E1=A3=AC=BE=CD=BF=C9=D2=D4=B2=CE=BC=D3=A1=A3
=BD=B1=C6=B7=B7=E1=BA=F1=A3=AC=D3=D0=A3=BA
Apple iBOOK G3 =CA=D6=CC=E1=B5=E7=C4=D4
SONY PlayStation 2
JVC White Magic MD=CB=E6=C9=ED=CC=FD
CASIO G-Shock =D0=C2=BF=EE=CA=D6=B1=ED
=B9=FA=BC=CA=D6=AA=C3=FB=BB=AF=D7=B1=C6=B7
=C8=E7=B9=FB=C4=FA=B6=D4=B1=BE=BB=EE=B6=AF=D3=D0=C8=CE=BA=CE=D2=C9=CE=CA,=
=BB=B6=D3=AD=B8=F8=CE=D2=C3=C7=C0=B4=D0=C5:
webmaster@myvirgo.com

------------------------------------------
This message was sent to you by
Name: webmaster
Email Address: xbctd@hotmail.com
IP Address: VIRGO3
------------------------------------------

Using Aureate Group Mail Free Edition
Find out more about this product and try it=20
for free at: http://www.group-mail.com/1

--XX64E56461-008564E5XX--



From rsvp-owner@ISI.EDU  Fri Jun  2 04:11:13 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26257
	for <rsvp-archive@lists.ietf.org>; Fri, 2 Jun 2000 04:11:12 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id XAA21069
	for rsvp-outgoing; Thu, 1 Jun 2000 23:03:23 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id XAA21064
	for <rsvp@zephyr.isi.edu>; Thu, 1 Jun 2000 23:03:22 -0700 (PDT)
Received: from dfssl.exchange.microsoft.com ([131.107.88.59])
	by venera.isi.edu (8.9.3/8.9.3) with SMTP id XAA23418
	for <rsvp@isi.edu>; Thu, 1 Jun 2000 23:03:56 -0700 (PDT)
Received: from 172.30.236.11 by dfssl.exchange.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 01 Jun 2000 21:53:40 -0700 (Pacific Daylight Time)
Received: from STAY.platinum.corp.microsoft.com ([172.30.236.91]) by yuri.dns.microsoft.com with Microsoft SMTPSVC(5.0.2195.2023);
	 Thu, 1 Jun 2000 21:43:50 -0700
content-class: urn:content-classes:message
Subject: RE: Editorial snafus in RFC 2751 and RFC 2752
Date: Thu, 1 Jun 2000 14:15:13 -0700
Message-ID: <078292D50C98D2118D090008C7E9C6A60EE7A410@STAY.platinum.corp.microsoft.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFCC0E.79B43588"
Thread-Topic: Editorial snafus in RFC 2751 and RFC 2752
Thread-Index: Ab/L+EStD0ju2oxgToWQDIEl+W1GeQAFvrQw
From: "Yoram Bernet" <yoramb@Exchange.Microsoft.com>
To: "Andrew Smith" <andrew@extremenetworks.com>,
        "rap (E-mail)" <rap@iphighway.com>,
        "rsvp@isi. edu (E-mail)" <rsvp@ISI.EDU>
X-MimeOLE: Produced By Microsoft Exchange V6.0.4382.0
Cc: "Scott Bradner" <sob@harvard.edu>, "Bert Wijnen" <bwijnen@lucent.com>,
        "Randy Bush (E-mail)" <randy@psg.com>,
        "mankin@east.isi.edu" <mankin@ISI.EDU>
X-OriginalArrivalTime: 02 Jun 2000 04:43:50.0409 (UTC) FILETIME=[258B2F90:01BFCC4D]
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

This is a multi-part message in MIME format.

------_=_NextPart_001_01BFCC0E.79B43588
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Thanks Andrew...

Not surprisingly, I vote to change the RFCs. Isn't proposed standard
status supposed to be ammenable to changes?

Y

> -----Original Message-----
> From: Andrew Smith [mailto:andrew@extremenetworks.com]
> Sent: Thursday, June 01, 2000 11:33 AM
> To: rap (E-mail); rsvp@isi. edu (E-mail)
> Cc: 'Scott Bradner'; 'Bert Wijnen'; Randy Bush (E-mail);
> 'mankin@east.isi.edu'
> Subject: Editorial snafus in RFC 2751 and RFC 2752
>=20
>=20
>=20
> It has come to our attention that there was an editorial=20
> snafu that occurred
> sometime last summer during the various edits of the Internet=20
> Drafts from
> the RAP WG that became RFC 2751 and RFC 2752. At that time, we had an
> informal co-ordination of the P-Type assignments within the=20
> POLICY_DATA RSVP
> object and we messed up and these got switched around before=20
> WG and IETF
> approval and RFC publication.
> =20
> Unfortunately, people have been implementing these drafts for=20
> a while now
> and, in fact, there have been significant numbers of copies of
> implementation shipped to customers using the original=20
> assignments which are
> incompatible with the assignments in the RFCs. This leads to=20
> headaches.
>=20
> The assignments in question are as follows:
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> RFC 2752            Identity Representation for RSVP       =20
> January 2000
>=20
>   P-Type (Identity Type)
>        Type of identity information contained in this Policy Element
>        supplied as the Policy element type (P-type). The Internet
>        Assigned Numbers Authority (IANA) acts as a registry for policy
>        element types for identity as described in the [POL-EXT].
>        Initially, the registry contains the following P-Types for
>        identity:
>=20
>        1   AUTH_USER       Authentication scheme to identify users
>=20
>        2   AUTH_APP        Authentication scheme to identify
>                            applications
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> RFC 2751      Signaled Preemption Priority Policy Element  =20
> January 2000
>=20
>    P-Type: 16 bits
>       PREEMPTION_PRI  =3D 3
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> The original assignments, prior to last summer, were as follows:
>=20
> 1  PREEMPTION_PRI
> 2  AUTH_USER
> 3  AUTH_APP
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> So, what to do about this? The "correct" answer is to say=20
> that people were
> stupid to ship product before the RFCs were out and that they=20
> should fix
> things themselves. However, this would cause serious=20
> deployment headaches
> that could easily affect the larger choice of whether or not to deploy
> RSVP-based products in a customers network. And it is a bad=20
> way to reward
> the implementers whose early experiences led to *significantly* better
> protocol-definition documents.
>=20
> It is up to the RAP WG, as the sponsor of these RFCs, to=20
> determine what the
> best course of action is, in consultation with the RSVP WG of=20
> course. If we,
> the WG, were to recommend to change the RFCs back to the=20
> original P-Type
> values (and re-issue these 2 RFCs) then I hope that the IESG would be
> sympathetic (I guess we should ask them first really ... I=20
> did ask Scott
> Bradner and he suggested that the WG should first come to a=20
> decision as to
> what it wants to do).
>=20
> So, please express your opinions ASAP to the RAP mailing list on this
> potential change. We will try to gauge the consensus to=20
> determine our next
> steps, if any.
>=20
> Thank you,
>=20
> Andrew Smith
> RAP WG co-chair
>=20

------_=_NextPart_001_01BFCC0E.79B43588
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4382.0">
<TITLE>RE: Editorial snafus in RFC 2751 and RFC 2752</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Thanks Andrew...</FONT>
</P>

<P><FONT SIZE=3D2>Not surprisingly, I vote to change the RFCs. Isn't =
proposed standard status supposed to be ammenable to changes?</FONT>
</P>

<P><FONT SIZE=3D2>Y</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>

<BR><FONT SIZE=3D2>&gt; From: Andrew Smith [<A =
HREF=3D"mailto:andrew@extremenetworks.com">mailto:andrew@extremenetworks.=
com</A>]</FONT>

<BR><FONT SIZE=3D2>&gt; Sent: Thursday, June 01, 2000 11:33 AM</FONT>

<BR><FONT SIZE=3D2>&gt; To: rap (E-mail); rsvp@isi. edu (E-mail)</FONT>

<BR><FONT SIZE=3D2>&gt; Cc: 'Scott Bradner'; 'Bert Wijnen'; Randy Bush =
(E-mail);</FONT>

<BR><FONT SIZE=3D2>&gt; 'mankin@east.isi.edu'</FONT>

<BR><FONT SIZE=3D2>&gt; Subject: Editorial snafus in RFC 2751 and RFC =
2752</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; It has come to our attention that there was an =
editorial </FONT>

<BR><FONT SIZE=3D2>&gt; snafu that occurred</FONT>

<BR><FONT SIZE=3D2>&gt; sometime last summer during the various edits of =
the Internet </FONT>

<BR><FONT SIZE=3D2>&gt; Drafts from</FONT>

<BR><FONT SIZE=3D2>&gt; the RAP WG that became RFC 2751 and RFC 2752. At =
that time, we had an</FONT>

<BR><FONT SIZE=3D2>&gt; informal co-ordination of the P-Type assignments =
within the </FONT>

<BR><FONT SIZE=3D2>&gt; POLICY_DATA RSVP</FONT>

<BR><FONT SIZE=3D2>&gt; object and we messed up and these got switched =
around before </FONT>

<BR><FONT SIZE=3D2>&gt; WG and IETF</FONT>

<BR><FONT SIZE=3D2>&gt; approval and RFC publication.</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp; </FONT>

<BR><FONT SIZE=3D2>&gt; Unfortunately, people have been implementing =
these drafts for </FONT>

<BR><FONT SIZE=3D2>&gt; a while now</FONT>

<BR><FONT SIZE=3D2>&gt; and, in fact, there have been significant =
numbers of copies of</FONT>

<BR><FONT SIZE=3D2>&gt; implementation shipped to customers using the =
original </FONT>

<BR><FONT SIZE=3D2>&gt; assignments which are</FONT>

<BR><FONT SIZE=3D2>&gt; incompatible with the assignments in the RFCs. =
This leads to </FONT>

<BR><FONT SIZE=3D2>&gt; headaches.</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; The assignments in question are as =
follows:</FONT>

<BR><FONT SIZE=3D2>&gt; =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>

<BR><FONT SIZE=3D2>&gt; RFC =
2752&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Identity Representation for =
RSVP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT>

<BR><FONT SIZE=3D2>&gt; January 2000</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; P-Type (Identity Type)</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type =
of identity information contained in this Policy Element</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
supplied as the Policy element type (P-type). The Internet</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Assigned Numbers Authority (IANA) acts as a registry for policy</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
element types for identity as described in the [POL-EXT].</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Initially, the registry contains the following P-Types for</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
identity:</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
1&nbsp;&nbsp; AUTH_USER&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Authentication scheme to identify users</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2&nbsp;&nbsp; AUTH_APP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Authentication scheme to identify</FONT>

<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; applications</FONT>

<BR><FONT SIZE=3D2>&gt; =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; RFC 2751&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Signaled =
Preemption Priority Policy Element&nbsp;&nbsp; </FONT>

<BR><FONT SIZE=3D2>&gt; January 2000</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; P-Type: 16 bits</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
PREEMPTION_PRI&nbsp; =3D 3</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; The original assignments, prior to last summer, =
were as follows:</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; 1&nbsp; PREEMPTION_PRI</FONT>

<BR><FONT SIZE=3D2>&gt; 2&nbsp; AUTH_USER</FONT>

<BR><FONT SIZE=3D2>&gt; 3&nbsp; AUTH_APP</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; So, what to do about this? The =
&quot;correct&quot; answer is to say </FONT>

<BR><FONT SIZE=3D2>&gt; that people were</FONT>

<BR><FONT SIZE=3D2>&gt; stupid to ship product before the RFCs were out =
and that they </FONT>

<BR><FONT SIZE=3D2>&gt; should fix</FONT>

<BR><FONT SIZE=3D2>&gt; things themselves. However, this would cause =
serious </FONT>

<BR><FONT SIZE=3D2>&gt; deployment headaches</FONT>

<BR><FONT SIZE=3D2>&gt; that could easily affect the larger choice of =
whether or not to deploy</FONT>

<BR><FONT SIZE=3D2>&gt; RSVP-based products in a customers network. And =
it is a bad </FONT>

<BR><FONT SIZE=3D2>&gt; way to reward</FONT>

<BR><FONT SIZE=3D2>&gt; the implementers whose early experiences led to =
*significantly* better</FONT>

<BR><FONT SIZE=3D2>&gt; protocol-definition documents.</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; It is up to the RAP WG, as the sponsor of these =
RFCs, to </FONT>

<BR><FONT SIZE=3D2>&gt; determine what the</FONT>

<BR><FONT SIZE=3D2>&gt; best course of action is, in consultation with =
the RSVP WG of </FONT>

<BR><FONT SIZE=3D2>&gt; course. If we,</FONT>

<BR><FONT SIZE=3D2>&gt; the WG, were to recommend to change the RFCs =
back to the </FONT>

<BR><FONT SIZE=3D2>&gt; original P-Type</FONT>

<BR><FONT SIZE=3D2>&gt; values (and re-issue these 2 RFCs) then I hope =
that the IESG would be</FONT>

<BR><FONT SIZE=3D2>&gt; sympathetic (I guess we should ask them first =
really ... I </FONT>

<BR><FONT SIZE=3D2>&gt; did ask Scott</FONT>

<BR><FONT SIZE=3D2>&gt; Bradner and he suggested that the WG should =
first come to a </FONT>

<BR><FONT SIZE=3D2>&gt; decision as to</FONT>

<BR><FONT SIZE=3D2>&gt; what it wants to do).</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; So, please express your opinions ASAP to the RAP =
mailing list on this</FONT>

<BR><FONT SIZE=3D2>&gt; potential change. We will try to gauge the =
consensus to </FONT>

<BR><FONT SIZE=3D2>&gt; determine our next</FONT>

<BR><FONT SIZE=3D2>&gt; steps, if any.</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; Thank you,</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; Andrew Smith</FONT>

<BR><FONT SIZE=3D2>&gt; RAP WG co-chair</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BFCC0E.79B43588--


From rsvp-owner@ISI.EDU  Fri Jun  2 14:19:13 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08977
	for <rsvp-archive@lists.ietf.org>; Fri, 2 Jun 2000 14:19:12 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id JAA15373
	for rsvp-outgoing; Fri, 2 Jun 2000 09:37:13 -0700 (PDT)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id JAA15367
	for <rsvp@zephyr.isi.edu>; Fri, 2 Jun 2000 09:37:12 -0700 (PDT)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id JAA04323;
	Fri, 2 Jun 2000 09:37:27 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id QAA24263;
	Fri, 2 Jun 2000 16:37:27 GMT
Date: Fri, 2 Jun 2000 16:37:27 GMT
Message-Id: <200006021637.QAA24263@gra.isi.edu>
To: andrew@extremenetworks.com, rap@iphighway.com, rsvp@ISI.EDU,
        yoramb@exchange.microsoft.com
Subject: RE: Editorial snafus in RFC 2751 and RFC 2752
Cc: sob@harvard.edu, bwijnen@lucent.com, randy@psg.com, mankin@ISI.EDU,
        rfc-ed@ISI.EDU
X-Sun-Charset: US-ASCII
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

  *> 
  *> Thanks Andrew... 
  *> 
  *> Not surprisingly, I vote to change the RFCs. Isn't proposed standard
  *> status supposed to be ammenable to changes? 
  *> 
  *> Y 

Yoram,

Surely you realize, RFCs DO NOT CHANGE, ever, once they are published.
What you *can* do is to publish a new RFC that obsoletes the bad one.

Such a procedure is hardly unknown in the history of the
Internet ;-)

Bob Braden (wearing his RFC Editor)


From rsvp-owner@ISI.EDU  Fri Jun  2 16:22:24 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12496
	for <rsvp-archive@lists.ietf.org>; Fri, 2 Jun 2000 16:22:22 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id LAA21613
	for rsvp-outgoing; Fri, 2 Jun 2000 11:44:54 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id LAA21608
	for <rsvp@zephyr.isi.edu>; Fri, 2 Jun 2000 11:44:53 -0700 (PDT)
Received: from bmailnj.iphighway.com ([63.89.157.130])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id LAA21875;
	Fri, 2 Jun 2000 11:45:03 -0700 (PDT)
Received: from brmnj-fw (63.89.157.129 [63.89.157.129]) by bmailnj.iphighway.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id L1GT5MNR; Fri, 2 Jun 2000 14:41:15 -0400
Message-Id: <4.3.1.2.20000602144055.0271bef0@bmailnj.brm.com>
X-Sender: herzog@bmailnj.brm.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Fri, 02 Jun 2000 14:43:51 -0400
To: Bob Braden <braden@ISI.EDU>, andrew@extremenetworks.com, rap@iphighway.com,
        rsvp@ISI.EDU, yoramb@exchange.microsoft.com
From: Shai Herzog <herzog@iphighway.com>
Subject: RE: Editorial snafus in RFC 2751 and RFC 2752
Cc: sob@harvard.edu, bwijnen@lucent.com, randy@psg.com, mankin@ISI.EDU,
        rfc-ed@ISI.EDU
In-Reply-To: <200006021637.QAA24263@gra.isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

I agree.

Seems that having two copies of RFCs 2751 floating around with different
values would be very confusing (even if it was permitted since RFCs don't
have version numbers like IDs).

If we decide to change the values to reflect actual deployed implementations
I think we should re-issue these RFCs with new numbers and obsolete the old
ones.

my 2c

Shai

At 04:37 PM 6/2/2000, Bob Braden wrote:
>   *>
>   *> Thanks Andrew...
>   *>
>   *> Not surprisingly, I vote to change the RFCs. Isn't proposed standard
>   *> status supposed to be ammenable to changes?
>   *>
>   *> Y
>
>Yoram,
>
>Surely you realize, RFCs DO NOT CHANGE, ever, once they are published.
>What you *can* do is to publish a new RFC that obsoletes the bad one.
>
>Such a procedure is hardly unknown in the history of the
>Internet ;-)
>
>Bob Braden (wearing his RFC Editor)


__________________________________________________________________
Shai Herzog, Founder & CTO   IPHighway Inc.   Tel : (914) 654-4810
55 New York Avenue                            Fax : (914) 654-0209
Framingham, MA 01701                          Main: (508) 620-1141




                              



From rsvp-owner@ISI.EDU  Fri Jun  2 16:33:23 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12768
	for <rsvp-archive@lists.ietf.org>; Fri, 2 Jun 2000 16:33:22 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id MAA22371
	for rsvp-outgoing; Fri, 2 Jun 2000 12:00:00 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id LAA22364
	for <rsvp@zephyr.isi.edu>; Fri, 2 Jun 2000 11:59:58 -0700 (PDT)
Received: from bmailnj.iphighway.com ([63.89.157.130])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id MAA22973;
	Fri, 2 Jun 2000 12:00:28 -0700 (PDT)
Received: from brmnj-fw (63.89.157.129 [63.89.157.129]) by bmailnj.iphighway.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id L1GT5M3D; Fri, 2 Jun 2000 14:56:46 -0400
Message-Id: <4.3.1.2.20000602144725.0271bef0@bmailnj.brm.com>
X-Sender: herzog@bmailnj.brm.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Fri, 02 Jun 2000 14:59:47 -0400
To: Bob Braden <braden@ISI.EDU>, andrew@extremenetworks.com, rap@iphighway.com,
        rsvp@ISI.EDU, yoramb@exchange.microsoft.com
From: Shai Herzog <herzog@iphighway.com>
Subject: RE: Editorial snafus in RFC 2751 and RFC 2752
Cc: sob@harvard.edu, bwijnen@lucent.com, randy@psg.com, mankin@ISI.EDU,
        rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

On second thought, I question the procedure where a draft with an IANA
clause (with number registration) can become RFC before its values are
actually recorded with IANA. Since the motivation for using IANA is to
prevent numbering blunders, allowing RFCs to be published pre-IANA registration
is crippling the mechanism.

In fact, I've just visited http://www.iana.org/numbers.htm#C only to
find out that COPS client numbers have yet to be registered with IANA, even
though the RFCs have been around for quite some time.

So, my suggestion is to have a pre-RFC registry with IANA, that follows
an I-D since creation (if it has an IANA clause). When the draft goes
to last call, its IANA registry goes with it. When the draft is approved,
the registry is moved to the "production" IANA registry.

2c (+2c) = my 4c ;-)

Shai

-----
Date: Fri, 02 Jun 2000 14:43:51 -0400
To: Bob Braden <braden@ISI.EDU>, andrew@extremenetworks.com, 
rap@iphighway.com, rsvp@ISI.EDU, yoramb@exchange.microsoft.com
From: Shai Herzog <herzog@iphighway.com>
Subject: RE: Editorial snafus in RFC 2751 and RFC 2752
Cc: sob@harvard.edu, bwijnen@lucent.com, randy@psg.com, mankin@ISI.EDU, 
rfc-ed@ISI.EDU

I agree.

Seems that having two copies of RFCs 2751 floating around with different
values would be very confusing (even if it was permitted since RFCs don't
have version numbers like IDs).

If we decide to change the values to reflect actual deployed implementations
I think we should re-issue these RFCs with new numbers and obsolete the old
ones.

my 2c

Shai

At 04:37 PM 6/2/2000, Bob Braden wrote:
   *>
   *> Thanks Andrew...
   *>
   *> Not surprisingly, I vote to change the RFCs. Isn't proposed standard
   *> status supposed to be ammenable to changes?
   *>
   *> Y

Yoram,

Surely you realize, RFCs DO NOT CHANGE, ever, once they are published.
What you *can* do is to publish a new RFC that obsoletes the bad one.

Such a procedure is hardly unknown in the history of the
Internet ;-)

Bob Braden (wearing his RFC Editor)

__________________________________________________________________
Shai Herzog, Founder & CTO   IPHighway Inc.   Tel : (914) 654-4810
55 New York Avenue                            Fax : (914) 654-0209
Framingham, MA 01701                          Main: (508) 620-1141




                              



From rsvp-owner@ISI.EDU  Sat Jun  3 04:18:09 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04749
	for <rsvp-archive@lists.ietf.org>; Sat, 3 Jun 2000 04:18:08 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id XAA19881
	for rsvp-outgoing; Fri, 2 Jun 2000 23:32:48 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id XAA19876
	for <rsvp@zephyr.isi.edu>; Fri, 2 Jun 2000 23:32:47 -0700 (PDT)
Received: from news.ethome.net.tw (sgi1.ethome.net.tw [202.178.244.131])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id XAA15565
	for <rsvp@isi.edu>; Fri, 2 Jun 2000 23:33:19 -0700 (PDT)
From: amd123443@cheerful.com
Received: from ysh (202.c146.ethome.net.tw [202.178.146.202])
	by news.ethome.net.tw (8.8.8/8.8.8) with SMTP id OAA28708854;
	Sat, 3 Jun 2000 14:23:25 +0800 (TAIST)
To: somebody@kitty.com
Date: 琍戳せ, 03 せる 2000 14:32:23 +0800
Message-Id: <36680.605829085645400.457@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=big5
Content-Transfer-Encoding: 8bit
Sender: owner-rsvp@ISI.EDU
Precedence: bulk
Content-Transfer-Encoding: 8bit


癸約獺璝硑Θ眤耑,и綠產弧羘╆簆,獺ン度祇癳Ω,璝硑Θ眤ぃ
獽,穛叫ǎ教....谅谅!!



承碔计絏Τそいゅ呼 
」Μ筿秎獽ΤΜ

辨穦尺舧承碔硂呼ウまぇ矪碞琌蛤セぃ惠暗ぐ或璶┪滤Μ?
写I筿秎ン約獽ΤΜ硂狝叭琌Ч禣ぃノ踞み璶竒パ呼祅癘Θ
穦

http://www.sharerich.com/chi/asp/joinframe.asp?rid=74280


」纚

禣爹Θ承碔穦穦Μㄢ獺ㄤいΞ〃
舧Θ承碔穦〃獺いΤ摸禬硈挡ゲ斗硂禬硈挡衡痷タЧΘ祅癘祘?
恰G

http://www.sharerich.com/chi/asp/confirmframe.asp?MemberID=计&Pass=计

」承碔崩滤璸购琌笲

讽祅癘Θ〃承碔〃穦碞Τ舦匡拒钡ΜㄇΤ砍届τΤノ戈癟Μ硂ㄇ?
臧T穦Μ瞷厨и穦筿秎ンよΑ禣腊р戈癟癳筿秎絚ず
и嘿硂ㄇ戈癟〃て筿秎ン約〃┪〃匡筿秎〃–讽Μパ承碔祇〃?
锕q秎〃穦眔翠刽0.1じ厨иョ躬纘崩滤克ねΘ〃承碔〃穦и嘿?
oㄇパ崩滤祅癘穦〃滤〃讽滤–Μ続〃匡筿秎〃
穦眔翠刽0.05じ厨〃滤〃计ヘ琌⊿Τ

」–眖承碔寥翠刽$130,000

痷琌虏虫ぃ筁ミ祅癘Θ穦崩滤15狟ねΘ穦躬纘㎝妓?
V崩滤狟ね把獽Τ诀穦暗

-----------------


   辨穦尺舧承碔硂呼. まぇ矪, 碞琌蛤セぃ惠暗ぐ或,
璶┪滤Μ承碔筿秎ン約, 獽ΤΜ!

硂狝叭琌禣, ぃノ踞み! 狦祅癘Θ穦, 叫琵и崩滤,
候癘祅癘崩滤逆ず恶и穦絪腹.

http://www.sharerich.com/chi/asp/joinframe.asp?rid=74280

и穦絪腹琌 : 74280




From rsvp-owner@ISI.EDU  Sat Jun  3 23:38:32 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16370
	for <rsvp-archive@lists.ietf.org>; Sat, 3 Jun 2000 23:38:31 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id SAA02199
	for rsvp-outgoing; Sat, 3 Jun 2000 18:42:35 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id SAA02193
	for <rsvp@zephyr.isi.edu>; Sat, 3 Jun 2000 18:42:32 -0700 (PDT)
Received: from mtiwmhc22.worldnet.att.net (mtiwmhc22.worldnet.att.net [204.127.131.47])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id SAA17637;
	Sat, 3 Jun 2000 18:43:05 -0700 (PDT)
Received: from who ([12.88.205.10]) by mtiwmhc22.worldnet.att.net
          (InterMail vM.4.01.02.39 201-229-119-122) with SMTP
          id <20000604014237.LNJX6885.mtiwmhc22.worldnet.att.net@who>;
          Sun, 4 Jun 2000 01:42:37 +0000
From: "Gregg C Levine" <hansolofalcon@worldnet.att.net>
To: "RSVP" <rsvp@ISI.EDU>, "Owner-Rsvp" <owner-rsvp@ISI.EDU>
Subject: Spam in Chinese
Date: Sat, 3 Jun 2000 21:42:19 -0400
Message-ID: <NEBBILPGILJOMAFJGIPAEEKJCDAA.hansolofalcon@worldnet.att.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Disposition-Notification-To: "Gregg C Levine" <hansolofalcon@worldnet.att.net>
Sender: owner-rsvp@ISI.EDU
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello from Gregg C Levine usually with Jedi Knight Computers
Did anyone receive an item of junk electronic mail in Chinese? Isn't the
mailling list supposed to be protected against spam? This is the second go
round for this blasted nuisance, can it be stopped before it becomes a
third?
Gregg C Levine mailto:hansolofalcon@worldnet.att.net
"Use the Force, Luke." Obi-Wan Kenobi
"Trust in the Force, Luke, and wait." Obi-Wan Kenobi



From rsvp-owner@ISI.EDU  Mon Jun  5 09:35:15 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02062
	for <rsvp-archive@lists.ietf.org>; Mon, 5 Jun 2000 09:35:15 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id EAA11216
	for rsvp-outgoing; Mon, 5 Jun 2000 04:34:31 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id EAA11211
	for <rsvp@zephyr.isi.edu>; Mon, 5 Jun 2000 04:34:29 -0700 (PDT)
Received: from ms1.yuemei.com.tw (host1.2037756.gcn.net.tw [203.77.56.1])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id EAA13071
	for <rsvp@isi.edu>; Mon, 5 Jun 2000 04:35:00 -0700 (PDT)
Message-Id: <200006051135.EAA13071@venera.isi.edu>
Received: from ms1.yuemei.com.tw (localhost [127.0.0.1]) by ms1.yuemei.com.tw with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id M1DN3TVT; Mon, 5 Jun 2000 19:26:28 +0800
Received: from 210.243.75.171 by ms1.yuemei.com.tw (InterScan E-Mail VirusWall NT); Mon, 05 Jun 2000 19:25:58 +0800
From: "weekend" <weekend@netvigator.com.tw>
Reply-To: ivan@mail.fuda.com.tw
Subject: 腳(候硄)
To: john@yungli.com.tw
X-Mailer: DiffondiCool V3,1,6,0 (W95/NT) (Build: Oct 18 1999)
Mime-Version: 1.0
Date: Thu, 04 May 2000 15:57:00 +0800
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

龟びΓ,╈さぱр 5 / 23 穝穝ヘ魁燿齳齵燿鶤鶤燿齵齳燿
呼隔,临Τ皘絬!!ㄉノ齳齵
-----------http://top.ms/abccd----------





From rsvp-owner@ISI.EDU  Mon Jun  5 12:44:23 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05977
	for <rsvp-archive@lists.ietf.org>; Mon, 5 Jun 2000 12:44:22 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id HAA19759
	for rsvp-outgoing; Mon, 5 Jun 2000 07:54:03 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id HAA19754
	for <rsvp@zephyr.isi.edu>; Mon, 5 Jun 2000 07:54:02 -0700 (PDT)
Received: from exch-staff.livjm.ac.uk (exch-staff.livjm.ac.uk [150.204.254.54])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id HAA20006
	for <rsvp@ISI.EDU>; Mon, 5 Jun 2000 07:54:34 -0700 (PDT)
Date: Mon, 5 Jun 2000 07:54:34 -0700 (PDT)
Message-Id: <200006051454.HAA20006@venera.isi.edu>
Received: from euler.cms.livjm.ac.uk (cmssmahf.livjm.ac.uk [150.204.48.41]) by exch-staff.livjm.ac.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id LTVHB46A; Mon, 5 Jun 2000 15:54:21 +0100
X-Sender: cmssmahf@staff-mail.livjm.ac.uk
X-Mailer: Windows Eudora Pro Version 2.1.2
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: rsvp@ISI.EDU
From: Saeed Mahfooz <S.Mahfooz@livjm.ac.uk>
Subject: unsbscribe
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

unsbscribe



From rsvp-owner@ISI.EDU  Wed Jun  7 07:49:21 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09300
	for <rsvp-archive@lists.ietf.org>; Wed, 7 Jun 2000 07:49:21 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id BAA16909
	for rsvp-outgoing; Wed, 7 Jun 2000 01:39:09 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id BAA16904
	for <rsvp@zephyr.isi.edu>; Wed, 7 Jun 2000 01:39:08 -0700 (PDT)
Received: from csi-admin1.cisco.com (csi-admin1.cisco.com [144.254.91.12])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id BAA04885
	for <rsvp@ISI.EDU>; Wed, 7 Jun 2000 01:39:40 -0700 (PDT)
Received: from nitsan-8000 (telaviv3-dhcp13.cisco.com [144.254.93.141]) by csi-admin1.cisco.com (8.8.4-Cisco.1/8.6.5) with SMTP id LAA22480; Wed, 7 Jun 2000 11:39:09 +0300 (IDT)
Reply-To: <nitsan@cisco.com>
From: "Nitsan Elfassy" <nitsan@cisco.com>
To: "'Andrew Smith'" <andrew@extremenetworks.com>,
        "'rap (E-mail)'" <rap@iphighway.com>,
        "'rsvp@isi. edu (E-mail)'" <rsvp@ISI.EDU>
Cc: "'Scott Bradner'" <sob@harvard.edu>, "'Bert Wijnen'" <bwijnen@lucent.com>,
        "'Randy Bush (E-mail)'" <randy@psg.com>, <mankin@ISI.EDU>
Subject: RE: Editorial snafus in RFC 2751 and RFC 2752
Date: Wed, 7 Jun 2000 11:41:19 +0200
Message-ID: <001501bfd064$898f4c40$8d5dfe90@nitsan-8000.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
In-Reply-To: <808F64DDB492D3119D3C00508B5D8D733EC90F@SOL>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-rsvp@ISI.EDU
Precedence: bulk
Content-Transfer-Encoding: 7bit

Andrew,

We support changing the PE types back to the original assignment.
Cisco is among those vendors that worked together to gain field experience,
which contributes so much to the standard success.
Since some of our colleague vendors, as you have noted, already shipped a
product that supports the original assignment, I second helping everybody
avoid those "headaches" you described.

As for the IETF procedures to support such a change, I guess the co-authors
will not have to cross the Rubickon, will they ?

Nitsan

Nitsan Elfassy - QPM-COPS PDP - Dev Mgr.
mailto://nitsan@cisco.com
Direct Line: 972-9-9700066
Cisco Israel
Herziliya Business Park,
4 Maskit St., P.O.B 12497,Herziliya
46766, ISRAEL




From rsvp-owner@ISI.EDU  Wed Jun  7 10:44:48 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11871
	for <rsvp-archive@lists.ietf.org>; Wed, 7 Jun 2000 10:44:47 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id FAA00365
	for rsvp-outgoing; Wed, 7 Jun 2000 05:33:08 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id FAA00360
	for <rsvp@zephyr.isi.edu>; Wed, 7 Jun 2000 05:33:06 -0700 (PDT)
Received: from mailhub2.shef.ac.uk (mailhub2.shef.ac.uk [143.167.2.154])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id FAA12492;
	Wed, 7 Jun 2000 05:33:34 -0700 (PDT)
Received: from qosnet1.shef.ac.uk ([143.167.12.131] helo=qosnet2)
	by mailhub2.shef.ac.uk with smtp (Exim 3.02 #2)
	id 12zf1g-0000B3-00; Wed, 07 Jun 2000 13:33:40 +0100
Message-ID: <001301bfd0be$f9a6b900$850ca78f@qosnet2>
From: "X Chen" <elp99xc@sheffield.ac.uk>
To: <rsvp@ISI.EDU>
Cc: "mankin" <mankin@ISI.EDU>, "rap" <rap@iphighway.com>, <nitsan@cisco.com>
Subject: Implementation RSVP in Windows 2000
Date: Wed, 7 Jun 2000 13:28:43 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0010_01BFD084.4D2C42B0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0010_01BFD084.4D2C42B0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I am doing a project about implementating RSVP in the Windows 2000. Now =
I have built a test beds with all the computers using window 2000 Sever =
and all the NICs are 802.1p supported. But are there some applications =
QoS-enabled which I can use to do the test in the test bed? Or I must =
write the QoS enabled application which can generate RSVP messages =
myself?

Please help me
Thanks a lot

X Chen
The university of Sheffield

------=_NextPart_000_0010_01BFD084.4D2C42B0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I am doing a project about =
implementating RSVP in=20
the Windows 2000. Now I have built a test beds with all the computers =
using=20
window 2000 Sever and all the NICs are 802.1p supported. But are there =
some=20
applications QoS-enabled which I can use to do the test in the test bed? =
Or I=20
must write the QoS enabled application which can generate RSVP messages=20
myself?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Please help me</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Thanks a lot</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>X Chen</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The university of=20
Sheffield</FONT></DIV></BODY></HTML>

------=_NextPart_000_0010_01BFD084.4D2C42B0--



From rsvp-owner@ISI.EDU  Wed Jun  7 12:14:14 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14673
	for <rsvp-archive@lists.ietf.org>; Wed, 7 Jun 2000 12:14:13 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id GAA06005
	for rsvp-outgoing; Wed, 7 Jun 2000 06:55:25 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id GAA06000
	for <rsvp@zephyr.isi.edu>; Wed, 7 Jun 2000 06:55:23 -0700 (PDT)
Received: from dfssl.exchange.microsoft.com ([131.107.88.59])
	by venera.isi.edu (8.9.3/8.9.3) with SMTP id GAA14834
	for <rsvp@isi.edu>; Wed, 7 Jun 2000 06:55:56 -0700 (PDT)
Received: from 172.30.236.11 by dfssl.exchange.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 07 Jun 2000 06:47:57 -0700 (Pacific Daylight Time)
Received: from STAY.platinum.corp.microsoft.com ([172.30.236.91]) by yuri.dns.microsoft.com with Microsoft SMTPSVC(5.0.2195.2023);
	 Wed, 7 Jun 2000 06:41:00 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.4384.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFD084.73105958"
Subject: RE: Implementation RSVP in Windows 2000
Date: Wed, 7 Jun 2000 06:29:47 -0700
Message-ID: <078292D50C98D2118D090008C7E9C6A60F35796D@STAY.platinum.corp.microsoft.com>
Thread-Topic: Implementation RSVP in Windows 2000
Thread-Index: Ab/Qfd3rL71R2LBARTersA8PyiN8JQABxJpw
From: "Yoram Bernet" <yoramb@Exchange.Microsoft.com>
To: "X Chen" <elp99xc@sheffield.ac.uk>, <rsvp@ISI.EDU>
Cc: "mankin" <mankin@ISI.EDU>, "rap" <rap@iphighway.com>, <nitsan@cisco.com>
X-OriginalArrivalTime: 07 Jun 2000 13:41:00.0678 (UTC) FILETIME=[0458B260:01BFD086]
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

This is a multi-part message in MIME format.

------_=_NextPart_001_01BFD084.73105958
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

You can start Phone Dialer (Start-->Programs-->Accessories-->Phone
DIaler). Or, Netmeeting
(Start-->Programs-->Accessories-->Communications-->Netmeeting). Either
app will get you going, out of the box, in generating RSVP signaling and
in DiffServ/802 marking based on the results of signaling. Also - see
the Admission Control Server in Win2K server.
=20
Good luck. Let me know if you need additional info.
=20
Yoram

-----Original Message-----
From: X Chen [mailto:elp99xc@sheffield.ac.uk]
Sent: Wednesday, June 07, 2000 1:29 PM
To: rsvp@ISI.EDU
Cc: mankin; rap; nitsan@cisco.com
Subject: Implementation RSVP in Windows 2000


I am doing a project about implementating RSVP in the Windows 2000. Now
I have built a test beds with all the computers using window 2000 Sever
and all the NICs are 802.1p supported. But are there some applications
QoS-enabled which I can use to do the test in the test bed? Or I must
write the QoS enabled application which can generate RSVP messages
myself?
=20
Please help me
Thanks a lot
=20
X Chen
The university of Sheffield


------_=_NextPart_001_01BFD084.73105958
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D623173313-07062000>You=20
can start Phone Dialer (Start--&gt;Programs--&gt;Accessories--&gt;Phone =
DIaler).=20
Or, Netmeeting=20
(Start--&gt;Programs--&gt;Accessories--&gt;Communications--&gt;Netmeeting=
).=20
Either app will get you going, out of the box, in generating RSVP =
signaling and=20
in DiffServ/802 marking based on the results of signaling. Also - see =
the=20
Admission Control Server in Win2K server.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D623173313-07062000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D623173313-07062000>Good=20
luck. Let me know if you need additional info.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D623173313-07062000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D623173313-07062000>Yoram</SPAN></FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px">
  <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> X Chen=20
  [mailto:elp99xc@sheffield.ac.uk]<BR><B>Sent:</B> Wednesday, June 07, =
2000 1:29=20
  PM<BR><B>To:</B> rsvp@ISI.EDU<BR><B>Cc:</B> mankin; rap;=20
  nitsan@cisco.com<BR><B>Subject:</B> Implementation RSVP in Windows=20
  2000<BR><BR></DIV></FONT>
  <DIV><FONT face=3DArial size=3D2>I am doing a project about =
implementating RSVP in=20
  the Windows 2000. Now I have built a test beds with all the computers =
using=20
  window 2000 Sever and all the NICs are 802.1p supported. But are there =
some=20
  applications QoS-enabled which I can use to do the test in the test =
bed? Or I=20
  must write the QoS enabled application which can generate RSVP =
messages=20
  myself?</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Please help me</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Thanks a lot</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>X Chen</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>The university of=20
Sheffield</FONT></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01BFD084.73105958--


From rsvp-owner@ISI.EDU  Thu Jun  8 12:29:34 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11202
	for <rsvp-archive@lists.ietf.org>; Thu, 8 Jun 2000 12:29:33 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id GAA10126
	for rsvp-outgoing; Thu, 8 Jun 2000 06:17:05 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id GAA10121
	for <rsvp@zephyr.isi.edu>; Thu, 8 Jun 2000 06:17:03 -0700 (PDT)
Received: from fsnt.future.futusoft.com ([203.197.140.35])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id GAA17697
	for <rsvp@isi.edu>; Thu, 8 Jun 2000 06:17:33 -0700 (PDT)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futusoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0000626150@fsnt.future.futusoft.com> for <rsvp@isi.edu>;
 Thu, 08 Jun 2000 18:57:50 +0530
Received: from narayananlr ([172.16.1.2]) by kailash.future.futsoft.com (8.7.1/8.7.1) with SMTP id SAA15835 for <rsvp@isi.edu>; Thu, 8 Jun 2000 18:48:17 +0530
Received: by localhost with Microsoft MAPI; Thu, 8 Jun 2000 18:48:25 +0530
Message-Id: <01BFD17A.20B1C600.narayananl@future.futsoft.com>
From: Lakshmi Narayanan R <narayananl@future.futsoft.com>
Reply-To: "narayananl@future.futsoft.com" <narayananl@future.futsoft.com>
To: "'rsvp@isi.edu'" <rsvp@ISI.EDU>
Subject: Unknown C-Type
Date: Thu, 8 Jun 2000 18:48:23 +0530
Organization: Future Software
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-rsvp@ISI.EDU
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,
I'm a newbie to the Rsvp world

Can anybody help me on these doubts: (Rfc -2205) (page 62)

1)
Is the Unknown C-type is required for Traffic Controller or                          
Is ths Traffic Controller is to do anything with the Unknown C -type?

2)
While receiving an Unknown C-type for the Known Class we are forming an Error message(PathErr or ResvErr)
Here the Known class means all the object classes or only the FlowSpec, AdSpec and Policy Objects ?

Thanks in advance


- Lakshminarayan  

 



From rsvp-owner@ISI.EDU  Thu Jun  8 12:40:13 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11488
	for <rsvp-archive@lists.ietf.org>; Thu, 8 Jun 2000 12:40:12 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id FAA09271
	for rsvp-outgoing; Thu, 8 Jun 2000 05:55:49 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id FAA09266
	for <rsvp@zephyr.isi.edu>; Thu, 8 Jun 2000 05:55:48 -0700 (PDT)
Received: from mailhub2.shef.ac.uk (mailhub2.shef.ac.uk [143.167.2.154])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id FAA17196
	for <rsvp@isi.edu>; Thu, 8 Jun 2000 05:56:14 -0700 (PDT)
Received: from qosnet1.shef.ac.uk ([143.167.12.131] helo=qosnet2)
	by mailhub2.shef.ac.uk with smtp (Exim 3.02 #2)
	id 1301r2-0006oN-00; Thu, 08 Jun 2000 13:56:12 +0100
Message-ID: <004d01bfd18b$51a720f0$850ca78f@qos.shef.ac.uk>
From: "X Chen" <elp99xc@sheffield.ac.uk>
To: "Ramesh Pabbati" <rameshpa@Exchange.Microsoft.com>
Cc: "rsvp" <rsvp@ISI.EDU>, "rap" <rap@iphighway.com>,
        "ivar" <ivar@iphighway.com>,
        "Gmeiner Harald" <Harald.Gmeiner@telekom.at>,
        "Yoram Bernet" <yoramb@Exchange.Microsoft.com>
References: <078292D50C98D2118D090008C7E9C6A60F2E7232@STAY.platinum.corp.microsoft.com>
Subject: Re: Implementation RSVP in Windows 2000
Date: Thu, 8 Jun 2000 13:51:27 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_004A_01BFD150.A4A663A0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

This is a multi-part message in MIME format.

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

Hi, Ramesh:
thanks for your information, I also have several questions to ask you.
1. Is NetMon you mentioned is Network monitor? If it is, I can access =
Network monitor.
2. In my test bed, I have 4 computers, 2 routers, one client and one =
sever. The NICs in the routers which are running ACS are 802.1p =
supported, is it nessesery that the NICs on client and server must =
802.1p supported?=20
3. You mentioned that "Description of the tracefiles can be found in the =
on-line help.", what is the on-line help you mean.

I said that the RSVP in Win2k is defferent with standard RSVP, what I =
mean is the application such as Netmeeting, I am not allowed to set the =
QoS parameters, it seems that thet are set automatically by Win2k( I =
can't find where I can set them.) Actually, I haven't really started =
using Netmeeting to do the test, I just worry about whether it can =
generate RSVP messages.
  ----- Original Message -----=20
  From: Ramesh Pabbati=20
  To: Yoram Bernet ; X Chen=20
  Sent: Wednesday, June 07, 2000 9:19 AM
  Subject: RE: Implementation RSVP in Windows 2000


  X Chen,
  =20
      Are you running a server with ACS? If yes you can not run =
NetMeeting on the server which is also ACS.=20
     =20
      Why did you say Windows 2000 RSVP is little different than =
standard RSVP?=20
  =20
      If you don't have access to NetMon you can turn on RSVP message =
tracing by creating the following registry key,=20
  =20
          EnableTracing
  =20
          under
  =20
          HKLM\SYSTEM\CurrentControlSet\Services\RSVP\Parameters
  =20
          of type REG_DWORD and set the value to 1
  =20
  this will generate text files containing RSVP message. These files are =
created in %WINDIR%\SYSTEM32\LogFiles directory. These text files =
contain the Tspec, FlowSpec etc. These files come very handy for you to =
see what RSVP messages are being received and sent out. Description of =
the tracefiles can be found in the on-line help.
  =20
      Ramesh
    -----Original Message-----
    From: Yoram Bernet=20
    Sent: Wednesday, June 07, 2000 9:04 AM
    To: X Chen
    Cc: Ramesh Pabbati
    Subject: RE: Implementation RSVP in Windows 2000


    X Chen:
    =20
    I just wanted to understand if you were building your own RSVP or =
using the one that is in Win2K. You are correct - RSVP operates as you =
describe in Win2K. It is standard RSVP.=20
    =20
    The QoS parameters of Netmeeting are automatically selected by the =
NetMeeting app. You should be able to use netmon to capture and study =
the messages.
    =20
    I have coipied Ramesh, who is our RSVP expert.
    =20
    Regards,
    Yoram
      -----Original Message-----
      From: X Chen [mailto:elp99xc@sheffield.ac.uk]
      Sent: Wednesday, June 07, 2000 4:55 PM
      To: Yoram Bernet
      Subject: Re: Implementation RSVP in Windows 2000


      Excuse me, can you explain to me what you mean "implementing " and =
native rsvp?
      As far as I know, the qos in Win2k is a little bit different with =
the standard rsvp, if the applications(receiver and sender) can generate =
RSVP messages, the QoS provider and ACS can reponse for those messages, =
and grants the bandwidth they want.

      BTW, I just configured the Netmeeting in the server and client in =
my testbed, but only one can access to Internet, and I checked the =
configuration of the Netmeeting, I can't find that where I can set the =
QoS parameters? If you know, please tell me in a little bit more detail.
      Original Message -----=20
        From: Yoram Bernet=20
        To: X Chen=20
        Sent: Wednesday, June 07, 2000 8:01 AM
        Subject: RE: Implementation RSVP in Windows 2000


        BTW - are you actually *implementing* RSVP? or are you using the =
native RSVP in Win2K?
        =20
        Yoram
          -----Original Message-----
          From: X Chen [mailto:elp99xc@sheffield.ac.uk]
          Sent: Wednesday, June 07, 2000 1:29 PM
          To: rsvp@ISI.EDU
          Cc: mankin; rap; nitsan@cisco.com
          Subject: Implementation RSVP in Windows 2000


          I am doing a project about implementating RSVP in the Windows =
2000. Now I have built a test beds with all the computers using window =
2000 Sever and all the NICs are 802.1p supported. But are there some =
applications QoS-enabled which I can use to do the test in the test bed? =
Or I must write the QoS enabled application which can generate RSVP =
messages myself?

          Please help me
          Thanks a lot

          X Chen
          The university of Sheffield

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi, Ramesh:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>thanks for your information, I also =
have several=20
questions to ask you.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>1. Is NetMon you mentioned is Network =
monitor? If=20
it is, I can access Network monitor.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>2. In my test bed, I have 4 computers, =
2 routers,=20
one client and one sever. The NICs in the routers which&nbsp;are running =
ACS are=20
802.1p supported, is it nessesery that the NICs on client and server =
must 802.1p=20
supported? </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>3. You mentioned that </FONT><FONT =
face=3DArial=20
size=3D2>"Description of the tracefiles can be found in the on-line =
help.", what=20
is the on-line help you mean.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I said that the RSVP in Win2k is =
defferent with=20
standard RSVP, what I mean is the application such as Netmeeting, I am =
not=20
allowed to set the QoS parameters, it seems that thet are set =
automatically by=20
Win2k( I can't find where I can set them.) Actually, I haven't really =
started=20
using Netmeeting to do the test, I just worry about whether it can =
generate RSVP=20
messages.</FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A href=3D"mailto:rameshpa@Exchange.Microsoft.com"=20
  title=3Drameshpa@Exchange.Microsoft.com>Ramesh Pabbati</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20
  href=3D"mailto:yoramb@Exchange.Microsoft.com"=20
  title=3Dyoramb@Exchange.Microsoft.com>Yoram Bernet</A> ; <A=20
  href=3D"mailto:elp99xc@sheffield.ac.uk" =
title=3Delp99xc@sheffield.ac.uk>X Chen</A>=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, June 07, 2000 =
9:19=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: Implementation =
RSVP in=20
  Windows 2000</DIV>
  <DIV><BR></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D574151216-07062000>X=20
  Chen,</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D574151216-07062000></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D574151216-07062000>&nbsp;&nbsp;&nbsp; Are you running a server =
with ACS?=20
  If yes you can not run NetMeeting on the server which is also ACS.=20
  </SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D574151216-07062000>&nbsp;&nbsp;&nbsp; </SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D574151216-07062000>&nbsp;&nbsp;&nbsp; Why did you say Windows =
2000 RSVP=20
  is little different than standard RSVP? </SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D574151216-07062000></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D574151216-07062000>&nbsp;&nbsp;&nbsp; If you don't have access =
to NetMon=20
  you can turn on RSVP message tracing by creating the following =
registry key,=20
  </SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D574151216-07062000></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D574151216-07062000>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  EnableTracing</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D574151216-07062000></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D574151216-07062000>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  under</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D574151216-07062000></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D574151216-07062000>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
HKLM\SYSTEM\CurrentControlSet\Services\RSVP\Parameters</SPAN></FONT></DIV=
>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D574151216-07062000></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D574151216-07062000>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
of type=20
  REG_DWORD and set the value to 1</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D574151216-07062000></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D574151216-07062000>this=20
  will generate text files containing RSVP message. These files are =
created in=20
  %WINDIR%\SYSTEM32\LogFiles directory. These text files contain the =
Tspec,=20
  FlowSpec etc. These files come very handy for you to see&nbsp;what =
RSVP=20
  messages are&nbsp;being received and sent out. Description of the =
tracefiles=20
  can be found in the on-line help.</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D574151216-07062000></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D574151216-07062000>&nbsp;&nbsp;&nbsp; </SPAN></FONT><FONT =
color=3D#0000ff=20
  face=3DArial size=3D2><SPAN =
class=3D574151216-07062000>Ramesh</SPAN></FONT></DIV>
  <BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px">
    <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
    size=3D2>-----Original Message-----<BR><B>From:</B> Yoram Bernet=20
    <BR><B>Sent:</B> Wednesday, June 07, 2000 9:04 AM<BR><B>To:</B> X=20
    Chen<BR><B>Cc:</B> Ramesh Pabbati<BR><B>Subject:</B> RE: =
Implementation RSVP=20
    in Windows 2000<BR><BR></DIV></FONT>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D994550716-07062000>X=20
    Chen:</SPAN></FONT></DIV>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
    class=3D994550716-07062000></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D994550716-07062000>I=20
    just wanted to understand if you were building your own RSVP or =
using the=20
    one that is in Win2K. You are correct - RSVP operates as you =
describe in=20
    Win2K. It is standard RSVP. </SPAN></FONT></DIV>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
    class=3D994550716-07062000></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
    class=3D994550716-07062000>The QoS parameters of Netmeeting are =
automatically=20
    selected by the NetMeeting app. You should be able to use netmon to =
capture=20
    and study the messages.</SPAN></FONT></DIV>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
    class=3D994550716-07062000></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D994550716-07062000>I=20
    have coipied Ramesh, who is our RSVP expert.</SPAN></FONT></DIV>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
    class=3D994550716-07062000></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
    class=3D994550716-07062000>Regards,</SPAN></FONT></DIV>
    <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
    class=3D994550716-07062000>Yoram</SPAN></FONT></DIV>
    <BLOCKQUOTE=20
    style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; =
MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
      <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
      size=3D2>-----Original Message-----<BR><B>From:</B> X Chen=20
      [mailto:elp99xc@sheffield.ac.uk]<BR><B>Sent:</B> Wednesday, June =
07, 2000=20
      4:55 PM<BR><B>To:</B> Yoram Bernet<BR><B>Subject:</B> Re: =
Implementation=20
      RSVP in Windows 2000<BR><BR></DIV></FONT>
      <DIV><FONT face=3DArial size=3D2>Excuse me, can you explain to me =
what you=20
      mean "implementing " and native rsvp?</FONT></DIV>
      <DIV><FONT face=3DArial size=3D2>As far as I know, the qos in =
Win2k is a=20
      little bit different with the standard rsvp, if the =
applications(receiver=20
      and sender) can generate RSVP messages, the QoS provider and ACS =
can=20
      reponse for those messages, and grants the bandwidth they=20
      want.</FONT></DIV>
      <DIV>&nbsp;</DIV>
      <DIV><FONT face=3DArial size=3D2>BTW, I just configured the =
Netmeeting in the=20
      server and client in my testbed, but only one can access to =
Internet, and=20
      I checked the configuration of the Netmeeting, I can't find that =
where I=20
      can set the QoS parameters? If you know, please tell me in a =
little bit=20
      more detail.</FONT></DIV>
      <DIV>Original Message ----- </DIV>
      <BLOCKQUOTE=20
      style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; =
MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
        <DIV=20
        style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
        <A href=3D"mailto:yoramb@Exchange.Microsoft.com"=20
        title=3Dyoramb@Exchange.Microsoft.com>Yoram Bernet</A> </DIV>
        <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20
        href=3D"mailto:elp99xc@sheffield.ac.uk" =
title=3Delp99xc@sheffield.ac.uk>X=20
        Chen</A> </DIV>
        <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, June 07, =
2000 8:01=20
        AM</DIV>
        <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: =
Implementation RSVP in=20
        Windows 2000</DIV>
        <DIV><BR></DIV>
        <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
        class=3D030160715-07062000>BTW - are you actually *implementing* =
RSVP? or=20
        are you using the native RSVP in Win2K?</SPAN></FONT></DIV>
        <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
        class=3D030160715-07062000></SPAN></FONT>&nbsp;</DIV>
        <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
        class=3D030160715-07062000>Yoram</SPAN></FONT></DIV>
        <BLOCKQUOTE=20
        style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; =
MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
          <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
          size=3D2>-----Original Message-----<BR><B>From:</B> X Chen [<A =

          =
href=3D"mailto:elp99xc@sheffield.ac.uk">mailto:elp99xc@sheffield.ac.uk</A=
>]<BR><B>Sent:</B>=20
          Wednesday, June 07, 2000 1:29 PM<BR><B>To:</B> <A=20
          href=3D"mailto:rsvp@ISI.EDU">rsvp@ISI.EDU</A><BR><B>Cc:</B> =
mankin; rap;=20
          <A=20
          =
href=3D"mailto:nitsan@cisco.com">nitsan@cisco.com</A><BR><B>Subject:</B> =

          Implementation RSVP in Windows 2000<BR><BR></DIV></FONT>
          <DIV><FONT face=3DArial size=3D2>I am doing a project about =
implementating=20
          RSVP in the Windows 2000. Now I have built a test beds with =
all the=20
          computers using window 2000 Sever and all the NICs are 802.1p=20
          supported. But are there some applications QoS-enabled which I =
can use=20
          to do the test in the test bed? Or I must write the QoS =
enabled=20
          application which can generate RSVP messages =
myself?</FONT></DIV>
          <DIV>&nbsp;</DIV>
          <DIV><FONT face=3DArial size=3D2>Please help me</FONT></DIV>
          <DIV><FONT face=3DArial size=3D2>Thanks a lot</FONT></DIV>
          <DIV>&nbsp;</DIV>
          <DIV><FONT face=3DArial size=3D2>X Chen</FONT></DIV>
          <DIV><FONT face=3DArial size=3D2>The university of=20
        =
Sheffield</FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE=
></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_004A_01BFD150.A4A663A0--



From rsvp-owner@ISI.EDU  Thu Jun  8 14:53:13 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14094
	for <rsvp-archive@lists.ietf.org>; Thu, 8 Jun 2000 14:53:13 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id JAA18827
	for rsvp-outgoing; Thu, 8 Jun 2000 09:22:31 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id JAA18802
	for <rsvp@zephyr.isi.edu>; Thu, 8 Jun 2000 09:22:27 -0700 (PDT)
Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id JAA25790
	for <rsvp@isi.edu>; Thu, 8 Jun 2000 09:23:00 -0700 (PDT)
From: zainprov@swbell.net
Received: from zainprov ([207.193.24.81]) by mta4.rcsntx.swbell.net
 (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9)
 with SMTP id <0FVU00AYMFED83@mta4.rcsntx.swbell.net> for rsvp@isi.edu; Thu,
 8 Jun 2000 11:06:17 -0500 (CDT)
Date: Thu, 08 Jun 2000 11:06:17 -0500 (CDT)
Date-warning: Date header was inserted by mta4.rcsntx.swbell.net
Subject: Shocking LOSE 10-100lbs. DESTINY
To: rsvp@ISI.EDU
Message-id: <0FVU00AYRFEE83@mta4.rcsntx.swbell.net>
MIME-version: 1.0
Content-type: text/plain; charset=unknown-8bit
Sender: owner-rsvp@ISI.EDU
Precedence: bulk


Hello From Destiny,

You will LOOSE 20-100 pounds easy!
Do to Such a high demand for Destiny, we are able
To Dramatically reduce our price for the entire System!
You will LOVE our incredible offer on this
Scientific Breakthrough in Weight Loss.
Now with a 105% Money Back Guarantee!   
LOOK! http://home.swbell.net/zainprov/destiny.htm



We hope things are going well for you.  Good luck, God Bless, and 
HAVE A GREAT DAY!



Either you are someone else subscribed to our list.  To be removed
Simply reply with a blank email.  

Thank you,

Sherry Wilson



From rsvp-owner@ISI.EDU  Thu Jun  8 17:31:38 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17288
	for <rsvp-archive@lists.ietf.org>; Thu, 8 Jun 2000 17:31:37 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id MAA02475
	for rsvp-outgoing; Thu, 8 Jun 2000 12:42:07 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id MAA02464
	for <rsvp@zephyr.isi.edu>; Thu, 8 Jun 2000 12:42:04 -0700 (PDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id MAA07059
	for <rsvp@isi.edu>; Thu, 8 Jun 2000 12:42:37 -0700 (PDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id PAA05740
	for <rsvp@isi.edu>; Thu, 8 Jun 2000 15:42:08 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id PAA21539
	for <rsvp@isi.edu>; Thu, 8 Jun 2000 15:42:09 -0400 (EDT)
Message-ID: <393FF72A.6DBA2EF7@marconi.com>
Date: Thu, 08 Jun 2000 15:42:34 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: rsvp@ISI.EDU
Subject: Re: Unknown C-Type
References: <01BFD17A.20B1C600.narayananl@future.futsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-rsvp@ISI.EDU
Precedence: bulk
Content-Transfer-Encoding: 7bit

Lakshmi Narayanan R wrote:
> 
> Can anybody help me on these doubts: (Rfc -2205) (page 62)
> 
> 1)
> Is the Unknown C-type is required for Traffic Controller or
> Is ths Traffic Controller is to do anything with the Unknown C -type?

The generation of unknown C-Type errors when object with unknown C-Types
are provided is a requirement.

The module of your RSVP code that actually generates the error is an
implementation detail.  Depending on your architecture, it might make
sense for various parts of your code (like traffic control, admission
control, policy control, etc.) to generate the error, depending on the
object class.  It might also make sense for one part of the code to have
knowledge about all classes and C-Types that are supported, so that the
error is always generated from one place.

> 2)
> While receiving an Unknown C-type for the Known Class we are forming
> an Error message(PathErr or ResvErr) Here the Known class means all
> the object classes or only the FlowSpec, AdSpec and Policy Objects ?

It is possible to receive an unknown C-Type for any class.  A
neighboring router might be using an RSVP extension that you do not
support, or your code might not support every single class and C-Type,
or the object might have become corrupted in transit.  An appropriate
error message should always be generated.

(Note, for example, that the MPLS extesions to RSVP add new C-Types to
many existing object classes - including session, sender-template, and
filterspec.  If a non-MPLS router receives an RSVP message with one of
these, it would be appropriate to send an unknown C-Type error.)

The reason certain kinds of objects are specifically mentioned in the
RFC is that some subsystems (like traffic control and policy control)
might be developed separately from the rest of the RSVP code.  Since
objects for those subsystems are not manipulated by the rest of RSVP, an
implementation may choose to leave c-type checking of those objects to
their corresponding subsystems.

-- David


From rsvp-owner@ISI.EDU  Thu Jun  8 19:29:29 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19031
	for <rsvp-archive@lists.ietf.org>; Thu, 8 Jun 2000 19:29:28 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id OAA09578
	for rsvp-outgoing; Thu, 8 Jun 2000 14:04:37 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id OAA09573
	for <rsvp@zephyr.isi.edu>; Thu, 8 Jun 2000 14:04:35 -0700 (PDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id OAA12272;
	Thu, 8 Jun 2000 14:05:05 -0700 (PDT)
Received: from wooly-booly.cisco.com (wooly-booly.cisco.com [171.69.167.33])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id OAA22412;
	Thu, 8 Jun 2000 14:04:44 -0700 (PDT)
Received: from p7020-img-nt.cisco.com (tokyo-ppp-dynamic12.cisco.com [144.254.188.140]) by wooly-booly.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) with ESMTP id QAA16036; Thu, 8 Jun 2000 16:04:29 -0500 (CDT)
Message-Id: <4.3.2.7.2.20000608075558.00dd1620@flipper.cisco.com>
X-Sender: fred@flipper.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 09 Jun 2000 04:51:00 +0800
To: "X Chen" <elp99xc@sheffield.ac.uk>
From: Fred Baker <fred@cisco.com>
Subject: Re: Implementation RSVP in Windows 2000
Cc: Yoram Bernet <yoramb@microsoft.com>, <rsvp@ISI.EDU>,
        "mankin" <mankin@ISI.EDU>, "rap" <rap@iphighway.com>,
        <nitsan@cisco.com>
In-Reply-To: <001301bfd0be$f9a6b900$850ca78f@qosnet2>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

At 01:28 PM 6/7/00 -0700, X Chen wrote:
>I am doing a project about implementating RSVP in the Windows 2000. Now I 
>have built a test beds with all the computers using window 2000 Sever and 
>all the NICs are 802.1p supported. But are there some applications 
>QoS-enabled which I can use to do the test in the test bed? Or I must 
>write the QoS enabled application which can generate RSVP messages myself?

pardon me, but wouldn't a representative from Microsoft be the logical 
person to ask this question?



From rsvp-owner@ISI.EDU  Thu Jun  8 19:47:04 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19223
	for <rsvp-archive@lists.ietf.org>; Thu, 8 Jun 2000 19:47:03 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id OAA14303
	for rsvp-outgoing; Thu, 8 Jun 2000 14:49:49 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id OAA14298
	for <rsvp@zephyr.isi.edu>; Thu, 8 Jun 2000 14:49:47 -0700 (PDT)
Received: from ertpg15e1.nortelnetworks.com (ertpg15e1.nortelnetworks.com [47.234.0.36])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id OAA14723
	for <rsvp@ISI.EDU>; Thu, 8 Jun 2000 14:50:14 -0700 (PDT)
Received: from zrtpd00y.us.nortel.com (actually zrtpd00y) 
          by ertpg15e1.nortelnetworks.com; Thu, 8 Jun 2000 17:48:59 -0400
Received: by zrtpd00y.us.nortel.com with Internet Mail Service (5.5.2650.21) 
          id <M1S2Y8PJ>; Thu, 8 Jun 2000 17:48:59 -0400
Message-ID: <C0B56FABBE35D311A7AF0000F81B1636014CAE5D@zlav0000.simi.baynetworks.com>
From: "Ralph Santitoro" <rsantito@nortelnetworks.com>
To: Andrew Smith <andrew@extremenetworks.com>
Cc: "'Scott Bradner'" <sob@harvard.edu>, "'Bert Wijnen'" <bwijnen@lucent.com>,
        "Randy Bush (E-mail)" <randy@psg.com>,
        "'mankin@east.isi.edu'" <mankin@ISI.EDU>,
        "rap (E-mail)" <rap@iphighway.com>,
        "rsvp@isi. edu (E-mail)" <rsvp@ISI.EDU>,
        Yoram Bernet <yoramb@microsoft.com>
Subject: RE: Editorial snafus in RFC 2751 and RFC 2752
Date: Thu, 8 Jun 2000 17:48:55 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01BFD193.5A16F578"
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01BFD193.5A16F578
Content-Type: text/plain;
	charset="iso-8859-1"

Andrew,

Given the nature of this assignment change in the RFC (an editorial
mistake), we support changing the P-Types back to their original assignment
as defined in the Internet draft, namely:

1 = PREEMPTION_PRI
2 = AUTH_USER
3 = AUTH_APP


Ralph Santitoro
QoS and Policy Architecture
Nortel Networks
Tel: 805-527-3024
rsantito@nortelnetworks.com


-----Original Message-----
From: Andrew Smith [mailto:andrew@extremenetworks.com]
Sent: Thursday, June 01, 2000 11:33 AM
To: rap (E-mail); rsvp@isi. edu (E-mail)
Cc: 'Scott Bradner'; 'Bert Wijnen'; Randy Bush (E-mail);
'mankin@east.isi.edu'
Subject: Editorial snafus in RFC 2751 and RFC 2752



It has come to our attention that there was an editorial snafu that occurred
sometime last summer during the various edits of the Internet Drafts from
the RAP WG that became RFC 2751 and RFC 2752. At that time, we had an
informal co-ordination of the P-Type assignments within the POLICY_DATA RSVP
object and we messed up and these got switched around before WG and IETF
approval and RFC publication.
 
Unfortunately, people have been implementing these drafts for a while now
and, in fact, there have been significant numbers of copies of
implementation shipped to customers using the original assignments which are
incompatible with the assignments in the RFCs. This leads to headaches.

The assignments in question are as follows:
================================================================
RFC 2752            Identity Representation for RSVP        January 2000

  P-Type (Identity Type)
       Type of identity information contained in this Policy Element
       supplied as the Policy element type (P-type). The Internet
       Assigned Numbers Authority (IANA) acts as a registry for policy
       element types for identity as described in the [POL-EXT].
       Initially, the registry contains the following P-Types for
       identity:

       1   AUTH_USER       Authentication scheme to identify users

       2   AUTH_APP        Authentication scheme to identify
                           applications
=================================================================

RFC 2751      Signaled Preemption Priority Policy Element   January 2000

   P-Type: 16 bits
      PREEMPTION_PRI  = 3

=================================================================

The original assignments, prior to last summer, were as follows:

1  PREEMPTION_PRI
2  AUTH_USER
3  AUTH_APP

===============================================================

So, what to do about this? The "correct" answer is to say that people were
stupid to ship product before the RFCs were out and that they should fix
things themselves. However, this would cause serious deployment headaches
that could easily affect the larger choice of whether or not to deploy
RSVP-based products in a customers network. And it is a bad way to reward
the implementers whose early experiences led to *significantly* better
protocol-definition documents.

It is up to the RAP WG, as the sponsor of these RFCs, to determine what the
best course of action is, in consultation with the RSVP WG of course. If we,
the WG, were to recommend to change the RFCs back to the original P-Type
values (and re-issue these 2 RFCs) then I hope that the IESG would be
sympathetic (I guess we should ask them first really ... I did ask Scott
Bradner and he suggested that the WG should first come to a decision as to
what it wants to do).

So, please express your opinions ASAP to the RAP mailing list on this
potential change. We will try to gauge the consensus to determine our next
steps, if any.

Thank you,

Andrew Smith
RAP WG co-chair


------_=_NextPart_001_01BFD193.5A16F578
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2651.65">
<TITLE>RE: Editorial snafus in RFC 2751 and RFC 2752</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Andrew,</FONT>
</P>

<P><FONT SIZE=3D2>Given the nature of this assignment change in the RFC =
(an editorial mistake), we support changing the P-Types back to their =
original assignment as defined in the Internet draft, =
namely:</FONT></P>

<P><FONT SIZE=3D2>1 =3D PREEMPTION_PRI</FONT>
<BR><FONT SIZE=3D2>2 =3D AUTH_USER</FONT>
<BR><FONT SIZE=3D2>3 =3D AUTH_APP</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Ralph Santitoro</FONT>
<BR><FONT SIZE=3D2>QoS and Policy Architecture</FONT>
<BR><FONT SIZE=3D2>Nortel Networks</FONT>
<BR><FONT SIZE=3D2>Tel: 805-527-3024</FONT>
<BR><FONT SIZE=3D2>rsantito@nortelnetworks.com</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Andrew Smith [<A =
HREF=3D"mailto:andrew@extremenetworks.com">mailto:andrew@extremenetworks=
.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, June 01, 2000 11:33 AM</FONT>
<BR><FONT SIZE=3D2>To: rap (E-mail); rsvp@isi. edu (E-mail)</FONT>
<BR><FONT SIZE=3D2>Cc: 'Scott Bradner'; 'Bert Wijnen'; Randy Bush =
(E-mail);</FONT>
<BR><FONT SIZE=3D2>'mankin@east.isi.edu'</FONT>
<BR><FONT SIZE=3D2>Subject: Editorial snafus in RFC 2751 and RFC =
2752</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>It has come to our attention that there was an =
editorial snafu that occurred</FONT>
<BR><FONT SIZE=3D2>sometime last summer during the various edits of the =
Internet Drafts from</FONT>
<BR><FONT SIZE=3D2>the RAP WG that became RFC 2751 and RFC 2752. At =
that time, we had an</FONT>
<BR><FONT SIZE=3D2>informal co-ordination of the P-Type assignments =
within the POLICY_DATA RSVP</FONT>
<BR><FONT SIZE=3D2>object and we messed up and these got switched =
around before WG and IETF</FONT>
<BR><FONT SIZE=3D2>approval and RFC publication.</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>Unfortunately, people have been implementing these =
drafts for a while now</FONT>
<BR><FONT SIZE=3D2>and, in fact, there have been significant numbers of =
copies of</FONT>
<BR><FONT SIZE=3D2>implementation shipped to customers using the =
original assignments which are</FONT>
<BR><FONT SIZE=3D2>incompatible with the assignments in the RFCs. This =
leads to headaches.</FONT>
</P>

<P><FONT SIZE=3D2>The assignments in question are as follows:</FONT>
<BR><FONT =
SIZE=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>
<BR><FONT SIZE=3D2>RFC =
2752&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Identity Representation for =
RSVP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; January 2000</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp; P-Type (Identity Type)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type of =
identity information contained in this Policy Element</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; supplied as the =
Policy element type (P-type). The Internet</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Assigned =
Numbers Authority (IANA) acts as a registry for policy</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; element types =
for identity as described in the [POL-EXT].</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Initially, the =
registry contains the following P-Types for</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
identity:</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp; =
AUTH_USER&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Authentication scheme to =
identify users</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp; =
AUTH_APP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Authentication =
scheme to identify</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; applications</FONT>
<BR><FONT =
SIZE=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>
</P>

<P><FONT SIZE=3D2>RFC 2751&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Signaled =
Preemption Priority Policy Element&nbsp;&nbsp; January 2000</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; P-Type: 16 bits</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PREEMPTION_PRI&nbsp; =
=3D 3</FONT>
</P>

<P><FONT =
SIZE=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>
</P>

<P><FONT SIZE=3D2>The original assignments, prior to last summer, were =
as follows:</FONT>
</P>

<P><FONT SIZE=3D2>1&nbsp; PREEMPTION_PRI</FONT>
<BR><FONT SIZE=3D2>2&nbsp; AUTH_USER</FONT>
<BR><FONT SIZE=3D2>3&nbsp; AUTH_APP</FONT>
</P>

<P><FONT =
SIZE=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>
</P>

<P><FONT SIZE=3D2>So, what to do about this? The &quot;correct&quot; =
answer is to say that people were</FONT>
<BR><FONT SIZE=3D2>stupid to ship product before the RFCs were out and =
that they should fix</FONT>
<BR><FONT SIZE=3D2>things themselves. However, this would cause serious =
deployment headaches</FONT>
<BR><FONT SIZE=3D2>that could easily affect the larger choice of =
whether or not to deploy</FONT>
<BR><FONT SIZE=3D2>RSVP-based products in a customers network. And it =
is a bad way to reward</FONT>
<BR><FONT SIZE=3D2>the implementers whose early experiences led to =
*significantly* better</FONT>
<BR><FONT SIZE=3D2>protocol-definition documents.</FONT>
</P>

<P><FONT SIZE=3D2>It is up to the RAP WG, as the sponsor of these RFCs, =
to determine what the</FONT>
<BR><FONT SIZE=3D2>best course of action is, in consultation with the =
RSVP WG of course. If we,</FONT>
<BR><FONT SIZE=3D2>the WG, were to recommend to change the RFCs back to =
the original P-Type</FONT>
<BR><FONT SIZE=3D2>values (and re-issue these 2 RFCs) then I hope that =
the IESG would be</FONT>
<BR><FONT SIZE=3D2>sympathetic (I guess we should ask them first really =
... I did ask Scott</FONT>
<BR><FONT SIZE=3D2>Bradner and he suggested that the WG should first =
come to a decision as to</FONT>
<BR><FONT SIZE=3D2>what it wants to do).</FONT>
</P>

<P><FONT SIZE=3D2>So, please express your opinions ASAP to the RAP =
mailing list on this</FONT>
<BR><FONT SIZE=3D2>potential change. We will try to gauge the consensus =
to determine our next</FONT>
<BR><FONT SIZE=3D2>steps, if any.</FONT>
</P>

<P><FONT SIZE=3D2>Thank you,</FONT>
</P>

<P><FONT SIZE=3D2>Andrew Smith</FONT>
<BR><FONT SIZE=3D2>RAP WG co-chair</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BFD193.5A16F578--


From rsvp-owner@ISI.EDU  Thu Jun  8 23:54:27 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23579
	for <rsvp-archive@lists.ietf.org>; Thu, 8 Jun 2000 23:54:27 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id SAA25853
	for rsvp-outgoing; Thu, 8 Jun 2000 18:51:02 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id SAA25848
	for <rsvp@zephyr.isi.edu>; Thu, 8 Jun 2000 18:51:01 -0700 (PDT)
Received: from public.fhnet.cn.net ([202.99.8.1])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id SAA25485
	for <rsvp@isi.edu>; Thu, 8 Jun 2000 18:51:04 -0700 (PDT)
Received: from x ([210.72.252.70])
	by public.fhnet.cn.net (8.9.2/8.9.2) with ESMTP id JAA23036;
	Fri, 9 Jun 2000 09:25:17 +0800 (CST)
Message-Id: <200006090125.JAA23036@public.fhnet.cn.net>
From: "www.001.com.cn" <j1986@sina.com>
Reply-To: j1986@sina.com
Subject: 这是封将改变您一生命运的EMAIL
To: 朋友的朋友@public.fhnet.cn.net
X-Mailer: Microsoft Outlook Express 4.05.1712.3
X-MimeOLE: Produced By Microsoft MimeOLE V羞D.1712.3
Mime-Version: 1.0
Date: Fri, 09 Jun 2000 09:05:37 +0800
Content-Type: multipart/mixed; boundary="----=_NextPart_000_007F_01BDF6C7.FABAC1B0"
Content-Transfer-Encoding: 7bit
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

This is a MIME Message

------=_NextPart_000_007F_01BDF6C7.FABAC1B0
Content-Type: multipart/alternative; boundary="----=_NextPart_001_0080_01BDF6C7.FABAC1B0"

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

***** This is an HTML Message ! *****


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

<span lang=3D"EN-US" style=3D"font-size:18=2E0pt;mso-bidi-font-size:
12=2E0pt"><a href=3D"http://www=2E001=2Ecom=2Ecn/">http://www=2E001=2Ecom=2E=
cn</a></span><span style=3D"font-size:16=2E0pt;mso-bidi-font-size:12=2E0pt;=

font-family:=BA=DA=CC=E5;color:red">=BD=AB=B8=C4=B1=E4=C4=FA=D2=BB=C9=FA=C3=
=FC=D4=CB</span>
<span lang=3D"EN-US" style=3D"font-size:18=2E0pt;mso-bidi-font-size:   
12=2E0pt"><a href=3D"http://www=2Eworld001=2Ecom/">http://www=2Eworld001=2E=
com</a></span><span style=3D"font-size:16=2E0pt;mso-bidi-font-size:12=2E0pt=
;   
font-family:=BA=DA=CC=E5;color:red">=BD=AB=B8=C4=B1=E4=C4=FA=D2=BB=C9=FA=C3=
=FC=D4=CB</span>   
<span lang=3D"EN-US">001=CD=B6=D7=CA=B0=D9=CD=F2=A3=AC=C6=B8=C7=EB=C8=AB=C7=
=F2=B8=F7=D0=D0=D2=B5=D7=A8=BC=D2=D4=DA=CF=DF=C3=E2=B7=D1=D7=C9=D1=AF=A1=A3=
</span>   
=C4=FA=C9=FA=BB=EE=D6=D0=B5=C4=D2=BB=C7=D0=B7=B3=C4=D5=BD=AB=D4=DA<a href=3D=
"http://www=2E001=2Ecom=2Ecn"><font size=3D"5" color=3D"#FF0000">001=C8=AB=C7=
=F2=BB=A5=D6=FA=CD=F8</font></a>=D3=AD=C8=D0=B6=F8=BD=E2=A1=A3=C4=E3=BD=AB=B5=
=C3=B5=BD=CE=D2=C3=C7=BA=CD=C8=AB=CA=C0=BD=E7=D7=A8=BC=D2=BA=CD=C8=C8=D0=C4=
=C8=CB=B5=C4=B6=A6=C1=A6=B0=EF=D6=FA=BA=CD=D7=C9=D1=AF                 
&nbsp;          
<p>                
=C3=E2=B7=D1=C8=A8=CD=FE=D0=C4=C0=ED=D7=A8=BC=D2=D7=C9=D1=AF&nbsp;</p>    =
      
<p>                
=C3=E2=B7=D1=C8=A8=CD=FE=D2=C6=C3=F1=BC=D3=C4=C3=B4=F3=D7=C9=D1=AF=A3=AC=CA=
=A1=C8=A5=C4=FA=B0=BA=B9=F3=B5=C4=CA=FD=CD=F2=D4=AA=B5=C4=D2=C6=C3=F1=C2=C9=
=CA=A6=B7=D1=A1=A3=A3=A8=D7=EE=C8=C8=BB=B0=CC=E2=A3=AC=B1=BE=BF=C6=A3=AC=D2=
=BB=C4=EA=B9=A4=D7=F7=BE=AD=D1=E9=A3=AC=B4=F3=D1=A7=D3=A2=D3=EF=CB=C4=BC=B6=
=D2=D4=C9=CF=A3=AC=D7=EE=BA=C3=D1=A7=B5=E7=C4=D4=B5=C4=BA=CD=C6=E4=CB=FB=B8=
=F7=C0=E0=B9=A4=B3=CC=CA=A6=D7=A8=D2=B5=A3=AC=BC=B4=BF=C9=B0=EC=C0=ED=A1=A3=
=A3=A9</p>             
=C3=E2=B7=D1=B5=E7=C4=D4=D3=B2=BC=FE=A3=AC=C8=ED=BC=FE=A3=AC=B1=E0=B3=CC=CE=
=CA=CC=E2=D7=C9=D1=AF,=C3=E2=B7=D1=D4=DA=CF=DF=D2=BD=C1=C6=D7=A8=BC=D2=D5=EF=
=B6=CF=D1=B0=D2=BD=CE=CA=D2=A9,               
=C3=E2=B7=D1=C8=AB=C7=F2=D5=F7=BB=E9,<p>            
=C3=E2=B7=D1=B9=C9=C6=B1=CD=B6=D7=CA=D7=C9=D1=AF=BA=CD=CC=D6=C2=DB ,=C3=E2=
=B7=D1=B7=A2=B2=BC=BD=F4=BC=B1=C7=F3=BE=C8,=C3=E2=B7=D1=B7=A2=B2=BC=B9=E3=B8=
=E6,=D7=D4=D1=A7=BF=BC=CA=D4=D7=C9=D1=AF,=CB=F9=D3=D0=C9=FA=BB=EE=C4=D1=CC=E2=
=D7=C9=D1=AF=BB=A5=D6=FA=A3=A1=A3=A1=A3=A1          
=CE=D2=C3=C7=B8=FC=BB=B6=D3=AD=C4=FA=D4=DA=D5=E2=C0=EF=CE=DE=CB=BD=B5=D8=B0=
=EF=D6=FA=C6=E4=CB=FB=D0=E8=D2=AA=B0=EF=D6=FA=B5=C4=C8=CB=A3=A1=D5=E2=D1=F9=
=D2=BB=C0=B4=C4=FA=BD=AB=B5=C3=B5=BD=CE=D2=C3=C7=CD=F8=D5=BE=B5=C4=B9=C9=B7=
=DD=A3=AC=BA=CD=B9=E3=B8=E6=CA=D5=C8=EB=B7=D6=B3=C9=A3=AC=D3=D0=BF=C9=C4=DC=
=B3=C9=CE=AA=D5=E6=D5=FD=B5=C4=B0=D9=CD=F2=B8=BB=CE=CC=A3=A1=CE=D2=C3=C7=CF=
=E0=D0=C5<span lang=3D"EN-US">:           
=D6=FA=C8=CB=D5=DF=B1=D8=D7=D4=D6=FA=A3=A1=BB=B6=D3=AD=B7=C3=CE=CA<font si=
ze=3D"5" color=3D"#FF0000">www=2E001=2Ecom=2Ecn =BA=CD   www=2Eworld001=2Ec=
om</font>                
</p>          
<font SIZE=3D"2">(=B9=E3=D6=DD=B5=E7=D3=CA=CD=F8=D6=C2=D0=C5=CF=E4=CB=F9=D3=
=D0=D5=DF=A3=BA          
=B4=D3=C5=F3=D3=D1=B4=A6=B5=C3=B5=BD=C4=FA=B5=C4EMAIL=B5=D8=D6=B7=A3=AC=C8=
=E7=B9=FB=C4=FA=B8=D0=BE=F5=B1=BE=D3=CA=BC=FE=B8=F8=C4=FA=B4=F8=C0=B4=B2=BB=
=B1=E3=A3=AC=C7=EB=BD=D3=CA=DC=CE=D2=C3=C7=C9=EE=C9=EE=B5=C4=C7=B8=D2=E2=A3=
=AC=B2=A2=C7=EB=C1=A2=BC=B4=BB=D8=B8=B4=A3=BAj1986@263=2Enet          
=CE=D2=C3=C7=BD=AB=BB=E1=D4=DA=D3=CA=BC=FE=C1=D0=B1=ED=D6=D0=C9=BE=B3=FD=C4=
=FA=B5=C4=D3=CA=CF=E4=A1=A3 </font>         
<font SIZE=3D"2"></font>                
                
<p>           
             
      210-9 ; 9

------=_NextPart_001_0080_01BDF6C7.FABAC1B0--

------=_NextPart_000_007F_01BDF6C7.FABAC1B0
Content-Type: text/html; name="001全球互助网.htm"
Content-Transfer-Encoding: quoted-printable
Content-Description: 001全球互助网.htm
Content-Disposition: inline; filename="001全球互助网.htm"
Content-Transfer-Encoding: quoted-printable

<!-- saved from url=3D(0022)http://internet=2Ee-mail -->
<html>
<script language=3D"JavaScript">
<!--
function NewWinAbc(){
    var attribution =3D "toolbar=3Dyes,location=3Dyes,directories=3Dyes,st=
atus=3Dyes,menubar=3Dno,ScrollBars=3Dyes,resizable=3Dyes";
    var urlname =3D "http://www=2E001=2Ecom=2Ecn/";
    window=2Eopen(urlname,"OpenNewWindows",attribution);
}
NewWinAbc();
// -->
</script>
<head>
<meta http-equiv=3D"Content-Language" content=3D"zh-cn">
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dgb2312">=

<meta name=3D"GENERATOR" content=3D"Microsoft FrontPage 4=2E0">
<meta name=3D"ProgId" content=3D"FrontPage=2EEditor=2EDocument">
<title>001=C8=AB=C7=F2=BB=A5=D6=FA=CD=F8</title>
</head>

<body>

<p>http://www=2E001=2Ecom=2Ecn/</p>

</body>

</html>


------=_NextPart_000_007F_01BDF6C7.FABAC1B0--





From rsvp-owner@ISI.EDU  Fri Jun  9 06:27:09 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08169
	for <rsvp-archive@lists.ietf.org>; Fri, 9 Jun 2000 06:27:08 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id BAA09198
	for rsvp-outgoing; Fri, 9 Jun 2000 01:19:32 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id BAA09193
	for <rsvp@zephyr.isi.edu>; Fri, 9 Jun 2000 01:19:31 -0700 (PDT)
Received: from x1.webuy.com.tw ([203.69.153.106])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id BAA09743
	for <rsvp@isi.edu>; Fri, 9 Jun 2000 01:19:48 -0700 (PDT)
Message-Id: <200006090819.BAA09743@venera.isi.edu>
Received: from user ([202.145.35.75]) by x1.webuy.com.tw
          (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35)
          with ESMTP id tw; Fri, 9 Jun 2000 14:55:35 +0800
From: "pipi" <pipi@tranbon.com.tw>
Reply-To: denden@mail.intellect.com.tw
Subject: 狥﹁璶籔狟ねだㄉ
To: is4j7a@isong.com.tw
X-Mailer: DiffondiCool V3,1,6,0 (W95/NT) (Build: Oct 18 1999)
Mime-Version: 1.0
Date: Fri, 09 Jun 2000 13:12:00 +0800
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

崩滤竒ㄥ獁难呼

硂琌и禦筁谋眔痷呼  

砯痷基龟    荡癸綼

Ω崩眖瞷祘Αи常Τ

稱穝砯呼ね碞パ秈........

「「「http://beam.at/jessy 「「「「







From rsvp-owner@ISI.EDU  Mon Jun 12 10:09:55 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02410
	for <rsvp-archive@lists.ietf.org>; Mon, 12 Jun 2000 10:09:53 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id FAA23917
	for rsvp-outgoing; Mon, 12 Jun 2000 05:24:33 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id FAA23912
	for <rsvp@zephyr.isi.edu>; Mon, 12 Jun 2000 05:24:32 -0700 (PDT)
Received: from mailhub2.shef.ac.uk (mailhub2.shef.ac.uk [143.167.2.154])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id FAA11034
	for <rsvp@isi.edu>; Mon, 12 Jun 2000 05:25:04 -0700 (PDT)
Received: from qosnet1.shef.ac.uk ([143.167.12.131] helo=qosnet2)
	by mailhub2.shef.ac.uk with smtp (Exim 3.02 #2)
	id 131THG-0001XB-00
	for rsvp@ISI.EDU; Mon, 12 Jun 2000 13:25:14 +0100
Message-ID: <002a01bfd4ab$cb21cf70$850ca78f@qos.shef.ac.uk>
From: "X Chen" <elp99xc@sheffield.ac.uk>
To: "rsvp" <rsvp@ISI.EDU>
Subject: RSVP Enabled Devices
Date: Mon, 12 Jun 2000 13:21:29 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0027_01BFD471.1E397C20"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

This is a multi-part message in MIME format.

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

Hi,=20

I am doing a project in which I need implement RSVP into Win2k client =
using Internet protocol. I was using Win2k as the routers in my testbed, =
but I found Win2k is not qos-aware, so I need to replace the Win2k =
router with other router which is QoS Enabled.=20
If someone is  doing the similar thing with me, can you give some =
imformation about what kinds of router can be the replacement?=20


Regards
X.Chen


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi, </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I am doing a project in which I need =
implement RSVP=20
into Win2k client using Internet protocol. I was using Win2k as the =
routers in=20
my testbed, but I found Win2k is not qos-aware, so I need to replace the =
Win2k=20
router with other router which is QoS Enabled. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>If someone is&nbsp; doing the similar =
thing with=20
me, can you give some imformation about what kinds of router can be the=20
replacement? </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Regards</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>X.Chen</FONT></DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0027_01BFD471.1E397C20--



From rsvp-owner@ISI.EDU  Mon Jun 12 13:30:47 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07442
	for <rsvp-archive@lists.ietf.org>; Mon, 12 Jun 2000 13:30:46 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id JAA03059
	for rsvp-outgoing; Mon, 12 Jun 2000 09:00:25 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id JAA03054
	for <rsvp@zephyr.isi.edu>; Mon, 12 Jun 2000 09:00:23 -0700 (PDT)
Received: from dfssl.exchange.microsoft.com ([131.107.88.59])
	by venera.isi.edu (8.9.3/8.9.3) with SMTP id JAA18211
	for <rsvp@isi.edu>; Mon, 12 Jun 2000 09:00:55 -0700 (PDT)
Received: from 172.30.236.11 by dfssl.exchange.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 12 Jun 2000 08:52:57 -0700 (Pacific Daylight Time)
Received: from STAY.platinum.corp.microsoft.com ([172.30.236.91]) by yuri.dns.microsoft.com with Microsoft SMTPSVC(5.0.2195.2023);
	 Mon, 12 Jun 2000 09:01:30 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.4390.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFD486.6B016D28"
Subject: RE: RSVP Enabled Devices
Date: Mon, 12 Jun 2000 08:53:57 -0700
Message-ID: <078292D50C98D2118D090008C7E9C6A60D94CA94@STAY.platinum.corp.microsoft.com>
Thread-Topic: RSVP Enabled Devices
Thread-Index: Ab/UaZBEP6ONtTzmRQukj7RSv+3AkAAHa5Ng
From: "Ramesh Pabbati" <rameshpa@Exchange.Microsoft.com>
To: "X Chen" <elp99xc@sheffield.ac.uk>, "rsvp" <rsvp@ISI.EDU>
X-OriginalArrivalTime: 12 Jun 2000 16:01:30.0414 (UTC) FILETIME=[78ED14E0:01BFD487]
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

This is a multi-part message in MIME format.

------_=_NextPart_001_01BFD486.6B016D28
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Small correction=20

-----Original Message-----
From: X Chen [mailto:elp99xc@sheffield.ac.uk]
Sent: Monday, June 12, 2000 1:21 PM
To: rsvp
Subject: RSVP Enabled Devices


Hi,=20
=20
I am doing a project in which I need implement RSVP into Win2k client
using Internet protocol. I was using Win2k as the routers in my testbed,
but I found Win2k[Ramesh Pabbati]  router  is not qos-aware, so I need
to replace the Win2k router with other router which is QoS Enabled.=20
If someone is  doing the similar thing with me, can you give some
imformation about what kinds of router can be the replacement?=20
=20
=20
Regards
X.Chen
=20


------_=_NextPart_001_01BFD486.6B016D28
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D527525915-12062000>Small=20
correction </SPAN></FONT></DIV>
<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px">
  <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> X Chen=20
  [mailto:elp99xc@sheffield.ac.uk]<BR><B>Sent:</B> Monday, June 12, 2000 =
1:21=20
  PM<BR><B>To:</B> rsvp<BR><B>Subject:</B> RSVP Enabled=20
  Devices<BR><BR></DIV></FONT>
  <DIV><FONT face=3DArial size=3D2>Hi, </FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>I am doing a project in which I need =
implement=20
  RSVP into Win2k client using Internet protocol. I was using Win2k as =
the=20
  routers in my testbed, but I found Win2k<SPAN =
class=3D527525915-12062000><FONT=20
  color=3D#0000ff>[Ramesh Pabbati]&nbsp; router&nbsp;</FONT></SPAN> is =
not=20
  qos-aware, so I need to replace the Win2k router with other router =
which is=20
  QoS Enabled. </FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>If someone is&nbsp; doing the similar =
thing with=20
  me, can you give some imformation about what kinds of router can be =
the=20
  replacement? </FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Regards</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>X.Chen</FONT></DIV>
  <DIV>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01BFD486.6B016D28--


From proms@saturn.kt.agh.edu.pl  Mon Jun 12 15:37:30 2000
Received: from uci.agh.edu.pl (root@galaxy.uci.agh.edu.pl [149.156.96.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09588
	for <rsvp-archive@odin.ietf.org>; Mon, 12 Jun 2000 15:37:26 -0400 (EDT)
Received: from saturn.kt.agh.edu.pl (proms@saturn.kt.agh.edu.pl [149.156.114.3])
	by uci.agh.edu.pl (8.9.3/8.8.7/rchk1.20) with SMTP id VAA08275
	for <rsvp-archive@odin.ietf.org>; Mon, 12 Jun 2000 21:36:03 +0200 (MET DST)
Received: by saturn.kt.agh.edu.pl (AIX 3.2/UCB 5.64/5.1)
          for rsvp-archive@odin.ietf.org id AA48970; Mon, 12 Jun 2000 21:35:11 +0200 
Date: Mon, 12 Jun 2000 21:35:11 +0200
From: proms@saturn.kt.agh.edu.pl (Piotr Pacyna)
Message-Id: <10006121935.AA48970@saturn.kt.agh.edu.pl>
Organization: University of Mining and Metallurgy
Address: Mickiewicza 30, 30-059 Krakow, POLAND
To: rsvp-archive@ietf.org
Subject: PROMS2000 - last Call for Papers

Dear Sir, Dear Madam,

Please find enclosed the Protocols for Multimedia Systems conference CfP.
We do apologise if you receive multiple copies of this.
Thank you for your attention.

With best regards,
Piotr Pacyna OC Chair

++++++++++++++++++++++++++++++++++++++++++++++++++++++

(We do apologize, if you receive multiple copies of this CfP)

                       Announcement and Call for Papers

                  PROTOCOLS FOR MULTIMEDIA SYSTEMS - PROMS2000

                       Cracow, Poland, October 22-25, 2000
Sponsored by IEEE Poland Sect. and Cracow Communications Soc. Chap.
Lucent Technologies, ZWUT a Siemens Company,
                         http://PROMS2000.kt.agh.edu.pl/

After past successful PROMS conferences held in Berlin, Salzburg,
Madrid, and Santiago de Chile now we cordially invite you to
Cracow/Poland, a lovely university city, with a 1000 year history, today
one of cultural capitals of Europe.

Emerging broadband interactive applications along with a development of
different networking technologies should draw telecom operators' and
service providers' attention to protocols supporting multimedia systems
as an interface between these two environments that has to be still
investigated and modified.

The PROMS2000 conference is intended to contribute to a scientific,
strategical and practical cooperation between research institutes and
industrial companies in the area of distributed multimedia applications,
protocols, and intelligent management tools, with emphasis on their
provision over broadband networks.

PROMS2000 will cover papers and demonstrations on research and
achievements related to the following topics:

TOPICS
* design and implementation of multimedia protocols for public switched
telephony networks, mobile networks, data networks, and satellite
networks using IP, ATM or other connectivity techniques;
* application, media, and protocol integration: synchronization of media
streams;
* multiparty and group communication protocols;
* mobile networking and routing: multimedia communication architectures
for mobile networks;
* multimedia applications: video-on-demand, digital video libraries,
video games, virtual community, teleworking, teleteaching, e-commerce,
telemeeting, virtual reality simulations;
* content based searching and querying;
* techniques for the specification of communication services required by
multimedia applications;
* methods for real-time testing and analysis of service implementations;
* integration of media storage and communication mechanisms, operating
system and high-performance issues;
* experiences with service provisioning using distributed multimedia
applications, eg. voice over IP;
* performance of protocols, such as TCP, and applications: modeling, simulation and optimization in different networks;
* definition, provisioning, and supervision of QoS parameters for
networked applications and services, eg. in IntServ/DiffServ networks;
* multimedia traffic engineering;
* applications and platforms for service management and provisioning;
* intelligent management tools pertaining to costs and quality of
service, network access, accounting, security, and system resilience;
* service access - security, authentication, privacy;
* accounting and tariff policing for multimedia teleservices.

IMPORTANT DATES
* Full papers due                     June 26, 2000
* Authors notified                    July 24, 2000
* Full paper camera ready due         September 25, 2000

CONFERENCE TIMETABLE
* 1st day       October 22      full-day sightseeing tour (optional)
* 2nd day       October 23      tutorials, welcome reception
* 3rd day       October 24      invited talks, sessions, panel, banquet
* 4th day       October 25      invited talks, sessions

VENUE
Its history rooted deep in the Middle Ages, Cracow, is the most
celebrated city in Poland. UNESCO has added its architectural complex to
the World Heritage List. Cracow's appeal today, however, is no longer
attributable solely to the beauty of its medieval architecture, but to
its strong scientific potential for applied research and development.

The PROMS2000 Conference will be held on the modern premises of the
Department of Telecommunications within walking distance of both the
downtown area and hotels. Direct flights to Cracow are available to and
from Chicago, Copenhagen, New York, Toronto, Frankfurt, London, Paris,
Rome, Tel Aviv, Vienna and Zurich.

SUBMISSION
Submit a full manuscript to the PROMS chair in an electronic form
(MSWord, Postscript or pdf file); editorial requirements can be found at
http://PROMS2000.kt.agh.edu.pl/.

PROCEEDINGS
1. Each participant will receive Proceedings from the conference.
2. Two best papers will be considered for publication in the IEEE Communications
   Magazine (March 2001 issue) in a feature topic "Protocols for Multimedia
   Systems".

CONFERENCE CHAIR
Zdzislaw PAPIR
Department of Telecommunications
University of Mining and Metallurgy
Al. Mickiewicza 30
30-059 Cracow, Poland
E-mail: papir@kt.agh.edu.pl
Phone: +48 12 634 55 82
Fax: +48 12 634 23 72

PROGRAM COMMITTEE
Koichi Asatani, Univ. Kogakuin, asatani@sin.cc.kogakuin.ac.jp
William Atwood, Univ. Concordia, Bill@cs.Concordia.ca
Arturo Azcorra, Univ. Carlos III de Madrid, azcorra@it.uc3m.es
Stanislaw Budkowski, INT-Evry, stan@int-evry.fr
Andrew Campbell, Univ. Columbia, campbell@ctr.columbia.edu
Michel Diaz, LAAS-CNRS, diaz@laas.fr
Wolfgang Effelsberg, Univ. Mannheim,
effelsberg@informatik.uni-mannheim.de
Paolo Fasano, CSELT, Paolo.Fasano@cselt.it
Francisco Fontes, Portugal Telecom, fontes@ptinovacao.pt
Nicolas D. Georganas, Univ. Ottawa, georgana@mcrlab.uottawa.ca
Per Gunningberg, Univ. Uppsala, Per.Gunningberg@docs.uu.se
Ibrahim Habib, Univ. New York
Ulrich Hofmann, Univ. Salzburg, ulrich.hofmann@fh-sbg.ac.at
David Hutchison, Univ. Lancaster, dh@comp.lancs.ac.uk
Yuji Inoue, NTT, yuji@rd.nttdata.co.jp
Andrzej Jajszczyk, Univ. Mining and Metallurgy, jajszcz@kt.agh.edu.pl
Pedro Lizcano, Telefonica Labs, lizcano@tid.es
John C. S. Lui, Chinese Univ. Hong Kong, cslui@cse.cuhk.edu.hk
Andrzej R. Pach, Univ. Mining & Metallurgy, pach@kt.agh.edu.pl
Sergio Palazzo, Univ. Catania, palazzo@iit.unict.it
Thomas Plagemann, Center for Technology, plageman@unik.no
Radia Perlman, SUN, radia.perlman@sun.com
Radu Popescu-Zeletin, GMD, zeletin@fokus.gmd.de
Marten J. van Sinderen, Univ. Twente, sinderen@cs.utwente.nl
Kazem Sohraby, Lucent, sohraby@lucent.com
Joan I. Solana, Nokia Telecom R & D, juan.solana@nokia.com
Eduardo Vera, Univ. of Chile, evera@accessnova.cl
Johan Zuidweg, Tecsidel, johan.zuidweg@ieee.org

ORGANISING COMMITTEE
Chair: Piotr PACYNA, proms@kt.agh.edu.pl
K. Juszkiewicz, juszkiew@kt.agh.edu.pl
J. Gozdecki, gozdecki@kt.agh.edu.pl
J. Roman, roman@kt.agh.edu.pl


From rsvp-owner@ISI.EDU  Mon Jun 12 18:08:58 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12133
	for <rsvp-archive@lists.ietf.org>; Mon, 12 Jun 2000 18:08:58 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id NAA17270
	for rsvp-outgoing; Mon, 12 Jun 2000 13:30:38 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id NAA17265
	for <rsvp@zephyr.isi.edu>; Mon, 12 Jun 2000 13:30:34 -0700 (PDT)
Received: from public8.sta.net.cn (public8.sta.net.cn [202.96.199.68])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id NAA28979
	for <rsvp@isi.edu>; Mon, 12 Jun 2000 13:31:05 -0700 (PDT)
Received: from Virgo7 (branch-1-c18.sta.net.cn [61.129.14.18])
	by public8.sta.net.cn (8.9.3/8.9.3) with SMTP id EAA08152;
	Tue, 13 Jun 2000 04:22:51 +0800 (CST)
Message-Id: <200006122022.EAA08152@public8.sta.net.cn>
From: webmaster <xbctd@hotmail.com>
To: 058 <xbctd@hotmail.com>
Date: Tue, 13 Jun 2000 04:42:51 +0800
Subject: 快来领取！！！
Reply-To: webmaster@myvirgo.com
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=XX73FE73BC-12CE73FEXX
Content-Transfer-Encoding: 7bit
X-Priority: 3
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

This is a Multipart MIME message. Since your mail reader
does not understand this format, some or all of this message may not be legible.

--XX73FE73BC-12CE73FEXX
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

=C7=D7=B0=AE=B5=C4=C5=F3=D3=D1:
=C4=FA=B5=C4=BA=C3=D3=D1=CF=F2=C4=FA=B3=CF=D2=E2=CD=C6=BC=F6MyVirgo.com.
=D4=DA=B5=DA=B6=FE=C2=D6=BB=EE=B6=AF=D6=D0=A3=AC=D2=D1=BE=AD=D3=D050=C3=FB=
=BB=E1=D4=B1=BB=F1=B5=C3=CE=D2=C3=C7=B5=C4=B4=F3=BD=B1=A3=A1=A3=A1=A3=A1
=C4=FA=B5=C4=C5=F3=D3=D1=D2=D1=BE=AD=CE=AA=C4=FA=D4=DA=CE=D2=C3=C7=BE=D9=B0=
=EC=B5=C4=B5=DA=C8=FD=C2=D6=B7=E8=BF=F1=B4=F3=B3=E9=BD=B1=BB=EE=B6=AF=B1=A8=
=C1=CB=C3=FB
=C4=FA=D6=BB=D0=E8=D2=AA=B5=BD
http://www.myvirgo.com/register/regform2.html
=D7=A2=B2=E1=A3=AC=BE=CD=BF=C9=D2=D4=B2=CE=BC=D3=A1=A3
=BD=B1=C6=B7=B7=E1=BA=F1=A3=AC=D3=D0=A3=BA
Apple iBOOK G3 =CA=D6=CC=E1=B5=E7=C4=D4
SONY PlayStation 2
JVC White Magic MD=CB=E6=C9=ED=CC=FD
CASIO G-Shock =D0=C2=BF=EE=CA=D6=B1=ED
=B9=FA=BC=CA=D6=AA=C3=FB=BB=AF=D7=B1=C6=B7
=C8=E7=B9=FB=C4=FA=B6=D4=B1=BE=BB=EE=B6=AF=D3=D0=C8=CE=BA=CE=D2=C9=CE=CA,=
=BB=B6=D3=AD=B8=F8=CE=D2=C3=C7=C0=B4=D0=C5:
webmaster@myvirgo.com

------------------------------------------
This message was sent to you by
Name: webmaster
Email Address: xbctd@hotmail.com
IP Address: VIRGO7
------------------------------------------

Using Aureate Group Mail Free Edition
Find out more about this product and try it=20
for free at: http://www.group-mail.com/1

--XX73FE73BC-12CE73FEXX--



From rsvp-owner@ISI.EDU  Tue Jun 13 09:14:21 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06722
	for <rsvp-archive@lists.ietf.org>; Tue, 13 Jun 2000 09:14:20 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id EAA22271
	for rsvp-outgoing; Tue, 13 Jun 2000 04:03:30 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id EAA22266
	for <rsvp@zephyr.isi.edu>; Tue, 13 Jun 2000 04:03:29 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id EAA27755
	for <rsvp@isi.edu>; Tue, 13 Jun 2000 04:04:00 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02500;
	Tue, 13 Jun 2000 07:04:10 -0400 (EDT)
Message-Id: <200006131104.HAA02500@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rsvp@ISI.EDU
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-rsvp-refresh-reduct-05.txt
Date: Tue, 13 Jun 2000 07:04:10 -0400
Sender: owner-rsvp@ISI.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 Resource Reservation Setup Protocol Working Group of the IETF.

	Title		: RSVP Refresh Overhead Reduction Extensions
	Author(s)	: L. Berger,  D. Gan,  G. Swallow, P. Pan,   
                          F. Tommasi, S. Molendini
	Filename	: draft-ietf-rsvp-refresh-reduct-05.txt
	Pages		: 34
	Date		: 12-Jun-00
	
This document describes a number of mechanisms that can be used to
reduce processing overhead requirements of refresh messages,
eliminate the state synchronization latency incurred when an RSVP
message is lost and, when desired, refreshing state without the
transmission of whole refresh messages.  The same extensions also
support reliable RSVP message delivery on a per hop basis.  These
extension present no backwards compatibility issues

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rsvp-refresh-reduct-05.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-rsvp-refresh-reduct-05.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-rsvp-refresh-reduct-05.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:	<20000612121200.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rsvp-refresh-reduct-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rsvp-refresh-reduct-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20000612121200.I-D@ietf.org>

--OtherAccess--

--NextPart--




From rsvp-owner@ISI.EDU  Tue Jun 13 14:03:53 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17855
	for <rsvp-archive@lists.ietf.org>; Tue, 13 Jun 2000 14:03:53 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id JAA16696
	for rsvp-outgoing; Tue, 13 Jun 2000 09:25:07 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id JAA16688
	for <rsvp@zephyr.isi.edu>; Tue, 13 Jun 2000 09:25:05 -0700 (PDT)
Received: from web1906.mail.yahoo.com (web1906.mail.yahoo.com [128.11.23.67])
	by venera.isi.edu (8.9.3/8.9.3) with SMTP id JAA12250
	for <rsvp@isi.edu>; Tue, 13 Jun 2000 09:25:34 -0700 (PDT)
Received: (qmail 6968 invoked by uid 60001); 13 Jun 2000 16:25:45 -0000
Message-ID: <20000613162545.6967.qmail@web1906.mail.yahoo.com>
Received: from [128.42.22.105] by web1906.mail.yahoo.com; Tue, 13 Jun 2000 09:25:45 PDT
Date: Tue, 13 Jun 2000 09:25:45 -0700 (PDT)
From: Ping Yuan <yuanpinghh@yahoo.com>
Subject: Questions about netperf
To: rsvp-test@ISI.EDU
Cc: rsvp@ISI.EDU
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

Hi,

Now, I am doing some test on scrapi and ISI version of
netperf. I tried to run a shell like this:

netperf -H 192.168.10.1 -p 12866 -t UDP_STREAM -- -s
48K -S 48k -m 48K -b 20K &
netperf -H 192.168.10.1 -p 12866 -t UDP_STREAM -- -s
48K -S 48k -m 48K -b 30K &
netperf -H 192.168.10.1 -p 12866 -t UDP_STREAM -- -s
48K -S 48k -m 48K -b 40K &
netperf -H 192.168.10.1 -p 12866 -t UDP_STREAM -- -s
48K -S 48k -m 48K -b 50K &
netperf -H 192.168.10.1 -p 12866 -t UDP_STREAM -- -s
48K -S 48k -m 48K -b 60K &

It gave the reult like this:

netperf: RSVP reservation failed: Request timed out
netperf: RSVP reservation failed: Request timed out
netperf: RSVP reservation failed: Request timed out
netperf: RSVP reservation failed: Request timed out
netperf: RSVP reservation failed: Request timed out

But, if I run a single process of netperf, it can get
a better result, but still with a big delay: 

RSVP reservation setup time = 5079 ms

Is it caused by the delay of scrapi or something else?
Is there anyone who also have this kind of problem?

Thanks for the help in advance,

Ping


__________________________________________________
Do You Yahoo!?
Yahoo! Photos -- now, 100 FREE prints!
http://photos.yahoo.com


From rsvp-owner@ISI.EDU  Wed Jun 14 14:32:08 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01436
	for <rsvp-archive@lists.ietf.org>; Wed, 14 Jun 2000 14:32:08 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id JAA23408
	for rsvp-outgoing; Wed, 14 Jun 2000 09:46:19 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id JAA23400
	for <rsvp@zephyr.isi.edu>; Wed, 14 Jun 2000 09:46:17 -0700 (PDT)
Received: from ganymede.or.intel.com (ganymede.or.intel.com [134.134.248.3])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id JAA09293
	for <rsvp@ISI.EDU>; Wed, 14 Jun 2000 09:46:49 -0700 (PDT)
Received: from SMTP (orsmsxvs02-1.jf.intel.com [192.168.65.201])
	by ganymede.or.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.30 2000/06/08 18:25:35 dmccart Exp $) with SMTP id JAA12001;
	Wed, 14 Jun 2000 09:46:52 -0700 (PDT)
Received: from orsmsx29.jf.intel.com ([192.168.70.29]) by 192.168.70.201
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Wed, 14 Jun 2000 16:46:52 0000 (GMT)
Received: by orsmsx29.jf.intel.com with Internet Mail Service (5.5.2448.0)
	id <M6KZG2BL>; Wed, 14 Jun 2000 09:46:50 -0700
Message-ID: <4A043A1FE4B2D111AC3F00A0C96B5133048410C2@fmsmsx37.fm.intel.com>
From: "Fenger, Russell J" <russell.j.fenger@intel.com>
To: rap@iphighway.com, rsvp@ISI.EDU, policy@raleigh.ibm.com
Subject: Intel COPS Client SDK
Date: Wed, 14 Jun 2000 09:46:47 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-rsvp@ISI.EDU
Precedence: bulk


The Intel COPS Client SDK is available under an open source
distribution license.  The first version provides support
for COPS-RSVP extensions and was designed to allow support
for additional COPS extensions in the future.  Support for
COPS-PR will be available after the next interop.

The SDK was also designed to be portable to any environment
by simply creating an environment-specific portability layer
usable by the other layers of the SDK.  A fully functional
Win32 portability layer is provided for reference.  Other
portability layers are under development.

The SDK also includes a COPS-RSVP server simulator binary
for test purposes.

The SDK is available at http://www.intel.com/ial/cops/. 

Russ



From rsvp-owner@ISI.EDU  Wed Jun 14 14:44:41 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01744
	for <rsvp-archive@lists.ietf.org>; Wed, 14 Jun 2000 14:44:40 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id KAA25362
	for rsvp-outgoing; Wed, 14 Jun 2000 10:08:05 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id KAA25356
	for <rsvp@zephyr.isi.edu>; Wed, 14 Jun 2000 10:08:04 -0700 (PDT)
Received: from mailout1.hananet.net (mailout1.hananet.net [210.220.163.34])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id KAA10593
	for <rsvp@isi.edu>; Wed, 14 Jun 2000 10:08:35 -0700 (PDT)
Message-Id: <200006141708.KAA10593@venera.isi.edu>
Received: from thrunet.thrunet.com ([211.117.12.76]) by
          mailout1.hananet.net (Netscape Messaging Server 4.15) with SMTP
          id FW5M5C01.U1Q for <rsvp@isi.edu>; Thu, 15 Jun 2000 02:05:36 +0900 
From: 捞泅快<olk01@hananet.net>
To: rsvp@ISI.EDU
Subject: 康绢,老绢 积劝雀拳 公丰 mailing service 救郴!!
Date: Thu, 15 Jun 00 02:07:28 鸥捞海捞 钎霖矫
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=AD_2000_PART_BOUNDARY_19990606
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

This is a multi-part message in MIME format.

--AD_2000_PART_BOUNDARY_19990606
Content-Type: text/plain
Content-Transfer-Encoding: 7Bit

⑽ 概老 罐酒焊角 康绢,老绢 积劝雀拳 抗巩.⒑⒑ 公丰 辑厚胶
ΜΜΜΜΜΜΜΜΜΜΜΜΜΜΜΜΜΜΜΜΜΜΜΜΜΜΜΜ
   A school teacher was taking a shower in her apartment 

   when the earthquake hit.

   Terrified, she rushed out into the hall and went down 

   the stairs pausing not even for bathrobe.

   One of the calmer tenants stopped her and hinted, 

  "Haven't you forgotten something?"

   She looked at him for a moment, then dashed back towards 

   her room.

  "Good God, my purse!"

* terrified : 疤俊 龙妨辑
* pause : 泪矫 肛眠促, 赣沟芭府促.
* Good God! : 具窜车匙!
* purse : (固惫) 勤靛归

咯急积捞 酒颇飘俊辑 箕况甫 窍绊 乐绰单 瘤柳捞 老绢车促.
去厚归魂茄 急积篮 固贸 啊款阑 吧摹绰 巴炼瞒 镭篮 盲 汗档肺 
顿媚唱客 拌窜阑 郴妨艾促.
弊锭 鞍篮 酒颇飘俊 混绊乐绰 粱 魔馒茄 荤恩捞 急积阑 力瘤窍
搁辑 惩瘤矫 茄付叼沁促.
"购啊甫 镭栏继唱 毫夸?"
咯急积篮 弊 巢磊甫 泪矫 官扼焊歹聪 金混鞍捞 规栏肺 登倒酒
啊哥 家府闷促.

"酒瞒, 郴 勤靛归!"
 
⒛ 坷疵狼 康绢 茄付叼 ⑴

⒙ There's a call for you.

A : Mr. Jinwoo, there's a call for you. 
B : Who's on the line?
A : Mr.Lee from Online Korea Co.
B : All right. Put him through.

⒘ 傈拳甫 官层临 锭 '傈拳 吭绢夸' 扼绰 钎泅篮 There's a call for
   you. 扼绊 且 荐 乐绢夸. 
   捞锭 '穿备茄抛辑 吭绢夸?' 窍绊 汞绰 钎泅篮 Who is it? 肚绰 
   Who's on the line? 殿栏肺 富且 荐 乐翠聪促.

⒙ 傈拳 吭嚼聪促.

A : 柳快揪, 傈拳 吭嚼聪促.
B : 穿备脚啊夸?
A : 柯扼牢内府酒狼 Mr.府涝聪促.
B : 亮酒夸. 楷搬矫难 林技夸.

⑾ 磊林 荤侩登绰 钎泅

ㄧ You have a phone call on line three. 
ㄨ You are wanted on the phone.
ㄩ Will you answer the phone?
 Who wants to speak with me?

ㄧ 3锅栏肺 傈拳 吭嚼聪促.
ㄨ 傈拳 吭嚼聪促.
ㄩ 傈拳 罐酒 焊矫摆绢夸?
 穿备茄抛辑 吭唱夸?

⒛ 坷疵狼 老绢  茄付叼 ⑴

   ∝老绢档 康绢客 鞍篮 屈怕肺 备己 登绢
乐嚼聪促.
------------------------------------------------------------------------------------------
=====================================================
救崇窍技夸? 

历锐绰 傈拳甫 捞侩秦辑 碍荤客 1:1肺 寇惫绢 切嚼阑 且 荐 乐绰 
⒛ Online Korea[ http://www.d-day.co.kr ] ⑴扼绊 钦聪促.

倾遏 绝捞 祈瘤 靛妨 了价钦聪促. 
菊栏肺绰 倾遏 绝绰 祈瘤绰 靛府瘤 臼摆嚼聪促.
窍坷聪, 何叼 呈弊矾款 侩辑甫......

历锐 雀荤俊辑绰 积劝 雀拳俊 包缴 乐绰 匙萍琉 咯矾盒俊霸
概老(岿-陛), 角 积劝俊 鞘夸茄 积劝雀拳 茄 巩厘究阑 
公丰肺 焊郴 靛府绊 乐绢夸.

辑厚胶 郴侩篮 困客 鞍捞 备己 登坷聪 罐酒焊辨 盔窍矫绰 盒篮 
§ olk@olk.co.kr №肺 "yes"扼绰 mail阑 林矫搁 等翠聪促.

弊府绊, 历锐 傈拳 寇惫绢 碍狼啊 泵陛窍脚 盒甸阑 困秦 
⒙矫裹碍狼⒙甫 
1雀俊 茄秦辑 公丰肺 角矫窍绊 乐栏聪 腹捞 脚没秦 林技夸.

公丰 矫裹碍狼 脚没 规过篮 ⒑ www.d-day.co.kr ⒏ 俊 立加窍脚 饶 
"碍狼家俺"鄂阑 努腐窍脚促澜 "碍狼脚没"鄂阑 焊矫搁 矫裹碍狼甫 
脚没窍角 荐 乐绢夸. 傈拳 02-588-0510 栏肺档 脚没且 荐 乐翠聪促.

酒公律废 捞 切嚼 过栏肺 雀拳 角仿 氢惑俊 累篮 焊牌捞 登菌栏搁 钦聪促.

皑荤钦聪促.

阂鞘夸茄 沥焊看促搁 措窜洒 了价钦聪促.
--AD_2000_PART_BOUNDARY_19990606--



From rsvp-owner@ISI.EDU  Thu Jun 15 04:07:39 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24907
	for <rsvp-archive@lists.ietf.org>; Thu, 15 Jun 2000 04:07:38 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id WAA12995
	for rsvp-outgoing; Wed, 14 Jun 2000 22:56:52 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id WAA12990
	for <rsvp@zephyr.isi.edu>; Wed, 14 Jun 2000 22:56:51 -0700 (PDT)
Received: from bgcanet.org (pc129.bgcanet.org [152.101.134.129])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id WAA12726;
	Wed, 14 Jun 2000 22:57:03 -0700 (PDT)
From: cory_alan@angelfire.com
Received: from angelfire.com by bgcanet.org (8.8.7/BGCA-HK)
	id NAA12229; Thu, 15 Jun 2000 13:49:22 +0800 (HKT)
Date: Thu, 15 Jun 2000 13:49:22 +0800 (HKT)
Message-Id: <200006150549.NAA12229@bgcanet.org>
Reply-To: cory_alan@angelfire.com
To: cory_alan@angelfire.com
Subject: Start Your Own E-Commerce Store with NO COSTS
Sender: owner-rsvp@ISI.EDU
Precedence: bulk



Name Your SHOPPING MALL

Yes, your own e-commerce site

Choose the name, design, stores, and even the products you feature!

ALL at Absolutely no cost -- FREE!

No credit card needed to open your mall, just an address to mall your sale 
checks & commissions to:

HURRY before the name you want for YOUR SHOPPING MALL is taken!

Reply NOW to receive YOUR access code. mailto:cory_alan2@angelfire.com

-------------------------------------------
Please read below for more information.
You can open an e-commerce store of your very own on the Internet and have 
it making
money for you in a matter of minutes.  Better still, it costs you 
absolutely nothing to open it.

This is a turnkey operation.  You can choose the design of you store from 
several templates (all functions will be available after the pre-launch 
phase is completed very shortly), pick a color for your store, name your 
store, and decide what products your store will carry.

Setup is simple: just click on the template options and they will be added 
to your store.

Add Products: you will be able to offer a comprehensive variety of 
categories as well as a vast selection of brands and items and they all be 
constantly growing All with the best competitive pricing possible.

You can select from individual categories, open several stores, or open one 
or more superstores with multiple products. What you choose is what will be 
built for you.

With this new breakthrough product, you will never have to maintain 
inventory or find products to fill your store.  It will all be done for 
you. You an never have to worry about filling or processing order, handling 
returns or refunds. That will be done for you too! In fact, you won't have 
to deal with many of the headaches commonly associated with having your own 
business.

Once the store is opened, when people make purchases from your store, you 
get paid. Tell your friends who are buying CDs to do it online at your 
store! Tell your family where they can get their next movie video your 
story Share Your store Address with
co-workers or even advertise it.
This is your choice..............
You are in control..............	

Ready to open your store? Simply reply to this email requesting your Access 
code.

An access code will be provided, along with the link to the site where you 
will need to follow simple instructions on your computer screen. It takes 
only a few minutes to become an e-commerce storeowner.

REPLY NOW to get an access code. mailto:cory_alan2@angelfire.com

And begin thinking of the name you want to reserve
to be removed from future mailings reply to this email
 >Under Bill s.1618 TITLE III passed by the 105th U.S. Congress
 >this letter can not be considered spam as long as we include:
 >Contact information & a Remove Link, mailto:cory_alan1.bangkok.com




From rsvp-owner@ISI.EDU  Thu Jun 15 09:57:42 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02112
	for <rsvp-archive@lists.ietf.org>; Thu, 15 Jun 2000 09:57:42 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id EAA29284
	for rsvp-outgoing; Thu, 15 Jun 2000 04:59:40 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id EAA29272
	for <rsvp@zephyr.isi.edu>; Thu, 15 Jun 2000 04:59:38 -0700 (PDT)
Received: from ssmtp01.melange.isp (smtp.landsraad.net [212.59.199.83])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id FAA23402
	for <rsvp@isi.edu>; Thu, 15 Jun 2000 05:00:08 -0700 (PDT)
From: Internet-Drafts@ietf.org
Received: from ssmtp01.melange.isp ([127.0.0.1]) by
          ssmtp01.melange.isp (Netscape Messaging Server 4.15) with SMTP
          id FW72JX03.I0X for <rsvp@isi.edu>; Thu, 15 Jun 2000 13:57:33 +0200 
Received: from growl.pobox.com ([208.210.124.27]) by
          ssmtp02.melange.isp (Netscape Messaging Server 4.15) with SMTP
          id FW3HXG07.W0U for <mvillada@arrakis.es>; Tue, 13 Jun 2000
          15:39:16 +0200 
Received: from loki.ietf.org (loki.ietf.org [132.151.1.177])
	by growl.pobox.com (Postfix) with ESMTP id 8BF7911297
	for <miguel@VILLADA.NET>; Tue, 13 Jun 2000 09:41:54 -0400 (EDT)
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id JAA26345
	for ietf-123-outbound.09@ietf.org; Tue, 13 Jun 2000 09:15:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id HAA25218
	for <all-ietf@loki.ietf.org>; Tue, 13 Jun 2000 07:04:11 -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 HAA02500;
	Tue, 13 Jun 2000 07:04:10 -0400 (EDT)
Message-Id: <200006131104.HAA02500@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rsvp@ISI.EDU
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-rsvp-refresh-reduct-05.txt
Date: Tue, 13 Jun 2000 07:04:10 -0400
Sender: owner-rsvp@ISI.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 Resource Reservation Setup Protocol Working Group of the IETF.

	Title		: RSVP Refresh Overhead Reduction Extensions
	Author(s)	: L. Berger,  D. Gan,  G. Swallow, P. Pan,   
                          F. Tommasi, S. Molendini
	Filename	: draft-ietf-rsvp-refresh-reduct-05.txt
	Pages		: 34
	Date		: 12-Jun-00
	
This document describes a number of mechanisms that can be used to
reduce processing overhead requirements of refresh messages,
eliminate the state synchronization latency incurred when an RSVP
message is lost and, when desired, refreshing state without the
transmission of whole refresh messages.  The same extensions also
support reliable RSVP message delivery on a per hop basis.  These
extension present no backwards compatibility issues

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rsvp-refresh-reduct-05.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-rsvp-refresh-reduct-05.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-rsvp-refresh-reduct-05.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:	<20000612121200.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rsvp-refresh-reduct-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rsvp-refresh-reduct-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20000612121200.I-D@ietf.org>

--OtherAccess--

--NextPart--





From rsvp-owner@ISI.EDU  Thu Jun 15 19:16:24 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17507
	for <rsvp-archive@lists.ietf.org>; Thu, 15 Jun 2000 19:16:23 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id OAA01120
	for rsvp-outgoing; Thu, 15 Jun 2000 14:27:44 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id OAA01115
	for <rsvp@zephyr.isi.edu>; Thu, 15 Jun 2000 14:27:43 -0700 (PDT)
Received: from mtc.mitac-mtc.com.tw ([210.71.195.1])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id OAA22304
	for <rsvp@isi.edu>; Thu, 15 Jun 2000 14:28:13 -0700 (PDT)
Received: from mtchc1.mitac-mtc.com.tw (mtchc1.mitac-mtc.com.tw [210.71.195.9])
	by mtc.mitac-mtc.com.tw (8.9.1/8.9.1) with ESMTP id FAA00528;
	Fri, 16 Jun 2000 05:17:00 +0800 (CST)
Message-Id: <200006152117.FAA00528@mtc.mitac-mtc.com.tw>
Received: from user (as5po169.ht.ficnet.net.tw [202.145.67.169]) by mtchc1.mitac-mtc.com.tw with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id MZ0TY49P; Fri, 16 Jun 2000 05:28:58 +0800
From: "aklet" <aklet@ms6.hinet.net>
Reply-To: alen@ttk.com.tw
Subject: 狥﹁璶籔狟ねだㄉ
To: is4j7a@isong.com.tw
X-Mailer: DiffondiCool V3,1,6,0 (W95/NT) (Build: Oct 18 1999)
Mime-Version: 1.0
Date: Fri, 16 Jun 2000 04:24:18 +0800
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

崩滤竒ㄥ獁难呼

硂琌и禦筁谋眔痷呼  

砯痷基龟    荡癸綼

Ω崩眖瞷祘Αи常Τ

稱穝砯呼ね碞パ秈........

「「「 http://www.geocities.com/a2000616/net001.htm 「「「「







From rsvp-owner@ISI.EDU  Fri Jun 16 06:36:12 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08263
	for <rsvp-archive@lists.ietf.org>; Fri, 16 Jun 2000 06:36:12 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id BAA14841
	for rsvp-outgoing; Fri, 16 Jun 2000 01:29:01 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id BAA14836
	for <rsvp@zephyr.isi.edu>; Fri, 16 Jun 2000 01:29:00 -0700 (PDT)
Received: from dns.lago.com.tw (IDENT:root@[211.72.145.66])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id BAA24055
	for <rsvp@isi.edu>; Fri, 16 Jun 2000 01:29:25 -0700 (PDT)
Received: from user (as5po169.ht.ficnet.net.tw [202.145.67.169])
	by dns.lago.com.tw (8.9.3/8.9.3) with ESMTP id AAA20965;
	Sat, 17 Jun 2000 00:35:32 +0800
Message-Id: <200006161635.AAA20965@dns.lago.com.tw>
From: "aklet" <aklet@ms6.hinet.net>
Reply-To: alen@ttk.com.tw
Subject: 狥﹁璶籔狟ねだㄉ
To: is4j7a@isong.com.tw
X-Mailer: DiffondiCool V3,1,6,0 (W95/NT) (Build: Oct 18 1999)
Mime-Version: 1.0
Date: Fri, 16 Jun 2000 04:24:18 +0800
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

崩滤竒ㄥ獁难呼

硂琌и禦筁谋眔痷呼  

砯痷基龟    荡癸綼

Ω崩眖瞷祘Αи常Τ

稱穝砯呼ね碞パ秈........

「「「 http://www.geocities.com/a2000616/net001.htm 「「「「







From rsvp-owner@ISI.EDU  Fri Jun 16 13:31:14 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18012
	for <rsvp-archive@lists.ietf.org>; Fri, 16 Jun 2000 13:31:13 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id JAA10137
	for rsvp-outgoing; Fri, 16 Jun 2000 09:02:21 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id JAA10132
	for <rsvp@zephyr.isi.edu>; Fri, 16 Jun 2000 09:02:20 -0700 (PDT)
Received: from mail.ahbbptt.net.cn ([202.102.200.67])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id JAA06148
	for <rsvp@isi.edu>; Fri, 16 Jun 2000 09:02:59 -0700 (PDT)
Received: from zlx (ppp441.bb.ah163.net [202.111.201.186])
	by mail.ahbbptt.net.cn (8.8.8/8.8.8) with ESMTP id XAA10955;
	Fri, 16 Jun 2000 23:52:49 +0800 (CST)
Message-Id: <200006161552.XAA10955@mail.ahbbptt.net.cn>
From: "chineseinformation" <chinamarketok@sohu.com>
Reply-To: chinamarketok@sohu.com
Subject: Re:480元国际域名注册
To: chinamarketok2@mail.ahbbptt.net.cn
X-Mailer:  V3,1,6,1 (W95/NT) (Build: Oct 18 1999)
Mime-Version: 1.0
Date: Fri, 16 Jun 2000 23:18:43 +0800
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

此信若给您带来麻烦,在此表示由衷地歉意!
中国民建网推出域名注册特惠价!
480元=国际域名两年+虚拟主机20M两年
并提供独立的CGI-BIN目录,10个域名式电子信箱,格式为
useid@yourdomain.
中国民建网让您以最实惠的价格连入INTERNET.
http://www.cndem.net;
http://www.cndem.com.





From rsvp-owner@ISI.EDU  Fri Jun 16 15:13:52 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21635
	for <rsvp-archive@lists.ietf.org>; Fri, 16 Jun 2000 15:13:51 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id KAA19475
	for rsvp-outgoing; Fri, 16 Jun 2000 10:39:20 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id KAA19468
	for <rsvp@zephyr.isi.edu>; Fri, 16 Jun 2000 10:39:19 -0700 (PDT)
Received: from public8.sta.net.cn (public8.sta.net.cn [202.96.199.68])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id KAA10667
	for <rsvp@isi.edu>; Fri, 16 Jun 2000 10:39:57 -0700 (PDT)
Received: from Virgo7 (branch-2-c129.sta.net.cn [61.129.74.129])
	by public8.sta.net.cn (8.9.3/8.9.3) with SMTP id BAA21951;
	Sat, 17 Jun 2000 01:39:52 +0800 (CST)
Message-Id: <200006161739.BAA21951@public8.sta.net.cn>
From: webmaster <xbctd@hotmail.com>
To: 072 <xbctd@hotmail.com>
Date: Sat, 17 Jun 2000 02:46:00 +0800
Subject: 快来领取！！！
Reply-To: webmaster@myvirgo.com
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=XX477E461A-0774477EXX
Content-Transfer-Encoding: 7bit
X-Priority: 3
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

This is a Multipart MIME message. Since your mail reader
does not understand this format, some or all of this message may not be legible.

--XX477E461A-0774477EXX
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

=C7=D7=B0=AE=B5=C4=C5=F3=D3=D1:
=C4=FA=B5=C4=BA=C3=D3=D1=CF=F2=C4=FA=B3=CF=D2=E2=CD=C6=BC=F6MyVirgo.com.
=D4=DA=B5=DA=B6=FE=C2=D6=BB=EE=B6=AF=D6=D0=A3=AC=D2=D1=BE=AD=D3=D050=C3=FB=
=BB=E1=D4=B1=BB=F1=B5=C3=CE=D2=C3=C7=B5=C4=B4=F3=BD=B1=A3=A1=A3=A1=A3=A1
=C4=FA=B5=C4=C5=F3=D3=D1=D2=D1=BE=AD=CE=AA=C4=FA=D4=DA=CE=D2=C3=C7=BE=D9=B0=
=EC=B5=C4=B5=DA=C8=FD=C2=D6=B7=E8=BF=F1=B4=F3=B3=E9=BD=B1=BB=EE=B6=AF=B1=A8=
=C1=CB=C3=FB
=C4=FA=D6=BB=D0=E8=D2=AA=B5=BD
http://www.myvirgo.com/register/regform2.html
=D7=A2=B2=E1=A3=AC=BE=CD=BF=C9=D2=D4=B2=CE=BC=D3=A1=A3
=BD=B1=C6=B7=B7=E1=BA=F1=A3=AC=D3=D0=A3=BA
Apple iBOOK G3 =CA=D6=CC=E1=B5=E7=C4=D4
SONY PlayStation 2
JVC White Magic MD=CB=E6=C9=ED=CC=FD
CASIO G-Shock =D0=C2=BF=EE=CA=D6=B1=ED
=B9=FA=BC=CA=D6=AA=C3=FB=BB=AF=D7=B1=C6=B7
=C8=E7=B9=FB=C4=FA=B6=D4=B1=BE=BB=EE=B6=AF=D3=D0=C8=CE=BA=CE=D2=C9=CE=CA,=
=BB=B6=D3=AD=B8=F8=CE=D2=C3=C7=C0=B4=D0=C5:
webmaster@myvirgo.com

------------------------------------------
This message was sent to you by
Name: webmaster
Email Address: xbctd@hotmail.com
IP Address: VIRGO7
------------------------------------------

Using Aureate Group Mail Free Edition
Find out more about this product and try it=20
for free at: http://www.group-mail.com/1

--XX477E461A-0774477EXX--



From rsvp-owner@ISI.EDU  Fri Jun 16 16:00:21 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22749
	for <rsvp-archive@lists.ietf.org>; Fri, 16 Jun 2000 16:00:20 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id LAA22871
	for rsvp-outgoing; Fri, 16 Jun 2000 11:18:11 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id LAA22865
	for <rsvp@zephyr.isi.edu>; Fri, 16 Jun 2000 11:18:06 -0700 (PDT)
Received: from sol.extremenetworks.com (sol.extremenetworks.com [216.52.8.2])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id LAA12762
	for <rsvp@ISI.EDU>; Fri, 16 Jun 2000 11:18:49 -0700 (PDT)
Received: by SOL with Internet Mail Service (5.5.2650.21)
	id <M3SKDPF7>; Fri, 16 Jun 2000 11:14:44 -0700
Message-ID: <808F64DDB492D3119D3C00508B5D8D733EC9F7@SOL>
From: Andrew Smith <andrew@extremenetworks.com>
To: "rap (E-mail)" <rap@iphighway.com>
Cc: "rsvp@isi. edu (E-mail)" <rsvp@ISI.EDU>
Subject: RE: Editorial snafus in RFC 2751 and RFC 2752
Date: Fri, 16 Jun 2000 11:14:41 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

Well, I've seen several messages in suport of this change and none against
it: would the authors of RFC 2751 and 2752 please submit some revised drafts
that incorporate these 3 changes? Hopefully this can be done before the next
Internet-Draft deadline (July 14th) - we can then issue WG last calls.

Thanks,

Andrew Smith
RAP WG co-chair

> -----Original Message-----
> From: Andrew Smith [mailto:andrew@extremenetworks.com]
> Sent: Thursday, June 01, 2000 11:33 AM
> To: rap (E-mail); rsvp@isi. edu (E-mail)
> Cc: 'Scott Bradner'; 'Bert Wijnen'; Randy Bush (E-mail);
> 'mankin@east.isi.edu'
> Subject: Editorial snafus in RFC 2751 and RFC 2752
> 
> 
> 
> It has come to our attention that there was an editorial 
> snafu that occurred
> sometime last summer during the various edits of the Internet 
> Drafts from
> the RAP WG that became RFC 2751 and RFC 2752. At that time, we had an
> informal co-ordination of the P-Type assignments within the 
> POLICY_DATA RSVP
> object and we messed up and these got switched around before 
> WG and IETF
> approval and RFC publication.
>  
> Unfortunately, people have been implementing these drafts for 
> a while now
> and, in fact, there have been significant numbers of copies of
> implementation shipped to customers using the original 
> assignments which are
> incompatible with the assignments in the RFCs. This leads to 
> headaches.
> 
> The assignments in question are as follows:
> ================================================================
> RFC 2752            Identity Representation for RSVP        
> January 2000
> 
>   P-Type (Identity Type)
>        Type of identity information contained in this Policy Element
>        supplied as the Policy element type (P-type). The Internet
>        Assigned Numbers Authority (IANA) acts as a registry for policy
>        element types for identity as described in the [POL-EXT].
>        Initially, the registry contains the following P-Types for
>        identity:
> 
>        1   AUTH_USER       Authentication scheme to identify users
> 
>        2   AUTH_APP        Authentication scheme to identify
>                            applications
> =================================================================
> 
> RFC 2751      Signaled Preemption Priority Policy Element   
> January 2000
> 
>    P-Type: 16 bits
>       PREEMPTION_PRI  = 3
> 
> =================================================================
> 
> The original assignments, prior to last summer, were as follows:
> 
> 1  PREEMPTION_PRI
> 2  AUTH_USER
> 3  AUTH_APP
> 
> ===============================================================
> 
> So, what to do about this? The "correct" answer is to say 
> that people were
> stupid to ship product before the RFCs were out and that they 
> should fix
> things themselves. However, this would cause serious 
> deployment headaches
> that could easily affect the larger choice of whether or not to deploy
> RSVP-based products in a customers network. And it is a bad 
> way to reward
> the implementers whose early experiences led to *significantly* better
> protocol-definition documents.
> 
> It is up to the RAP WG, as the sponsor of these RFCs, to 
> determine what the
> best course of action is, in consultation with the RSVP WG of 
> course. If we,
> the WG, were to recommend to change the RFCs back to the 
> original P-Type
> values (and re-issue these 2 RFCs) then I hope that the IESG would be
> sympathetic (I guess we should ask them first really ... I 
> did ask Scott
> Bradner and he suggested that the WG should first come to a 
> decision as to
> what it wants to do).
> 
> So, please express your opinions ASAP to the RAP mailing list on this
> potential change. We will try to gauge the consensus to 
> determine our next
> steps, if any.
> 
> Thank you,
> 
> Andrew Smith
> RAP WG co-chair
> 


From rsvp-owner@ISI.EDU  Fri Jun 16 20:16:03 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28348
	for <rsvp-archive@lists.ietf.org>; Fri, 16 Jun 2000 20:16:03 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id LAA23125
	for rsvp-outgoing; Fri, 16 Jun 2000 11:20:17 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id LAA23114
	for <rsvp@zephyr.isi.edu>; Fri, 16 Jun 2000 11:20:11 -0700 (PDT)
Received: from public8.sta.net.cn (public8.sta.net.cn [202.96.199.68])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id LAA12863
	for <rsvp@isi.edu>; Fri, 16 Jun 2000 11:20:48 -0700 (PDT)
Received: from Virgo7 (branch-2-c129.sta.net.cn [61.129.74.129])
	by public8.sta.net.cn (8.9.3/8.9.3) with SMTP id BAA21941;
	Sat, 17 Jun 2000 01:39:40 +0800 (CST)
Message-Id: <200006161739.BAA21941@public8.sta.net.cn>
From: webmaster <xbctd@hotmail.com>
To: 072 <xbctd@hotmail.com>
Date: Sat, 17 Jun 2000 02:41:00 +0800
Subject: 快来领取！！！
Reply-To: webmaster@myvirgo.com
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=XX37FD32C9-077437FDXX
Content-Transfer-Encoding: 7bit
X-Priority: 3
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

This is a Multipart MIME message. Since your mail reader
does not understand this format, some or all of this message may not be legible.

--XX37FD32C9-077437FDXX
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

=C7=D7=B0=AE=B5=C4=C5=F3=D3=D1:
=C4=FA=B5=C4=BA=C3=D3=D1=CF=F2=C4=FA=B3=CF=D2=E2=CD=C6=BC=F6MyVirgo.com.
=D4=DA=B5=DA=B6=FE=C2=D6=BB=EE=B6=AF=D6=D0=A3=AC=D2=D1=BE=AD=D3=D050=C3=FB=
=BB=E1=D4=B1=BB=F1=B5=C3=CE=D2=C3=C7=B5=C4=B4=F3=BD=B1=A3=A1=A3=A1=A3=A1
=C4=FA=B5=C4=C5=F3=D3=D1=D2=D1=BE=AD=CE=AA=C4=FA=D4=DA=CE=D2=C3=C7=BE=D9=B0=
=EC=B5=C4=B5=DA=C8=FD=C2=D6=B7=E8=BF=F1=B4=F3=B3=E9=BD=B1=BB=EE=B6=AF=B1=A8=
=C1=CB=C3=FB
=C4=FA=D6=BB=D0=E8=D2=AA=B5=BD
http://www.myvirgo.com/register/regform2.html
=D7=A2=B2=E1=A3=AC=BE=CD=BF=C9=D2=D4=B2=CE=BC=D3=A1=A3
=BD=B1=C6=B7=B7=E1=BA=F1=A3=AC=D3=D0=A3=BA
Apple iBOOK G3 =CA=D6=CC=E1=B5=E7=C4=D4
SONY PlayStation 2
JVC White Magic MD=CB=E6=C9=ED=CC=FD
CASIO G-Shock =D0=C2=BF=EE=CA=D6=B1=ED
=B9=FA=BC=CA=D6=AA=C3=FB=BB=AF=D7=B1=C6=B7
=C8=E7=B9=FB=C4=FA=B6=D4=B1=BE=BB=EE=B6=AF=D3=D0=C8=CE=BA=CE=D2=C9=CE=CA,=
=BB=B6=D3=AD=B8=F8=CE=D2=C3=C7=C0=B4=D0=C5:
webmaster@myvirgo.com

------------------------------------------
This message was sent to you by
Name: webmaster
Email Address: xbctd@hotmail.com
IP Address: VIRGO7
------------------------------------------

Using Aureate Group Mail Free Edition
Find out more about this product and try it=20
for free at: http://www.group-mail.com/1

--XX37FD32C9-077437FDXX--



From rsvp-owner@ISI.EDU  Sun Jun 18 01:16:45 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27235
	for <rsvp-archive@lists.ietf.org>; Sun, 18 Jun 2000 01:16:44 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id UAA22176
	for rsvp-outgoing; Sat, 17 Jun 2000 20:12:44 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id UAA22171
	for <rsvp@zephyr.isi.edu>; Sat, 17 Jun 2000 20:12:43 -0700 (PDT)
Received: from pchome.com.tw (122.c150.ethome.net.tw [202.178.150.122])
	by venera.isi.edu (8.9.3/8.9.3) with SMTP id UAA05344
	for <rsvp@isi.edu>; Sat, 17 Jun 2000 20:13:25 -0700 (PDT)
Message-Id: <200006180313.UAA05344@venera.isi.edu>
From: "Gofly" <newgofly@pchome.com.tw>
Subject: =?big5?B?p0Gmbrbcfg==?=
Date: Sat, 17 Jun 2000 17:53:57 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Unsent: 1
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-rsvp@ISI.EDU
Precedence: bulk
Content-Transfer-Encoding: 8bit


顿 
и琌 Gofly パиヘ玡產︽痁狦ΤヴΤ闽瓣ず笴戈
癟快瞶帽靡拜肈┪琌稱т基窥ゑㄤウ︽稧τ珇借獶盽ぃ岿笴
刮舧糶 E-Mail 拜ии穦鲸и┮狝叭
и边ノ筿福戮Μ蔼禬筁フぱ痷и
獶盽骸ìτ硂琌戳┦埃獶ぃ稱暗狦盽呼稱寥翴窥
琌刚刚糶 E-Mail 倒ии穦禗冈灿薄



Gofly,17,June,2000










From rsvp-owner@ISI.EDU  Sun Jun 18 06:10:41 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06661
	for <rsvp-archive@lists.ietf.org>; Sun, 18 Jun 2000 06:10:40 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id BAA04027
	for rsvp-outgoing; Sun, 18 Jun 2000 01:16:26 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id BAA04022
	for <rsvp@zephyr.isi.edu>; Sun, 18 Jun 2000 01:16:24 -0700 (PDT)
Received: from mlist.netease.com ([202.103.134.7])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id BAA12744
	for <rsvp@isi.edu>; Sun, 18 Jun 2000 01:17:02 -0700 (PDT)
Received: from asong (unknown [202.96.159.246])
	by mlist.netease.com (Postfix) with ESMTP
	id 8102A4E2E0; Sun, 18 Jun 2000 16:21:12 +0800 (CST)
From: "luck" <luck@163.net>
Reply-To: luck@163.net
Subject: downloading
To: downloading@mlist.netease.com
X-Mailer: DiffondiCool V3,1,3,0 (W95/NT) (Build: Sep 24 1999)
Mime-Version: 1.0
Date: Sun, 18 Jun 2000 13:03:36 +0800
Content-Type: multipart/mixed; boundary="----=_NextPart_000_007F_01BDF6C7.FABAC1B0"
Content-Transfer-Encoding: 7bit
Message-Id: <20000618082112.8102A4E2E0@mlist.netease.com>
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

This is a MIME Message

------=_NextPart_000_007F_01BDF6C7.FABAC1B0
Content-Type: multipart/alternative; boundary="----=_NextPart_001_0080_01BDF6C7.FABAC1B0"

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

***** This is an HTML Message ! *****


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

<script language=3D"JavaScript">
window.open('http://hbyaya.yeah.net');
</script>

=D3=C9=E6=AB=E6=AB=D3=E9=C0=D6=D7=CA=D1=B6=CE=AA=CA=D7=D7=E9=BD=A8----=CF=C2=
=D4=D8=C1=AA=C3=CB http://downloading.yeah.net

=C4=DA=C8=DD=B0=FC=C0=A8=A3=BA
=D2=BB=A1=A2=D3=E9=C0=D6=CF=C2=D4=D8
1=A1=A2=B5=E7=D3=B0=C6=AC=B6=CF=CF=C2=D4=D8
2=A1=A2=B5=E7=D3=B0=BA=A3=B1=A8=CF=C2=D4=D8
3=A1=A2=D2=F4=C0=D6mp3=CF=C2=D4=D8=A3=A8=B0=FC=C0=A8mp3=A1=A2real=BA=CD=B8=
=E8=B4=CA=A3=A9
4=A1=A2=D7=C0=C3=E6=CF=C2=D4=D8
=B6=FE=A1=A2=CA=E9=BA=A3=CF=C2=D4=D8=A3=A8=BD=FC3G=B5=C4=CA=E9=BF=E2=CC=E1=
=B9=A9=CF=C2=D4=D8=A3=A9
1=A1=A2=CD=F8=C2=E7=D4=AD=B4=B4=D7=F7=C6=B7
2=A1=A2=CE=E4=CF=C0=BF=C6=BB=C3=D0=A1=CB=B5
3=A1=A2=B5=E7=C4=D4=CD=F8=C2=E7=CE=C4=BF=E2=B5=C8=B5=C8
=C8=FD=A1=A2=CF=C2=D4=D8=CD=F8=D3=D1=BB=E1
=CB=C4=A1=A2=CF=C2=D4=D8=C2=DB=CC=B3
=CE=E5=A1=A2=CF=C2=D4=D8=C1=C4=CC=EC

=B3=CF=D1=FB=BA=CF=D7=F7=D5=DF=A3=BA=D2=AA=C7=F3a=A1=A2=BE=AB=CD=A8=CD=F8=D5=
=BE=C9=E8=BC=C6=D6=C6=D7=F7b=A1=A2=BE=AB=CD=A8=CD=F8=C2=E7cgi/asp/php=B1=E0=
=B3=CC=A3=AC
internet c/s=B3=CC=D0=F2=BF=AA=B7=A2c=A1=A2=C9=C3=B3=A4=CD=F8=C2=E7=B2=DF=BB=
=AE=BA=CD=CD=C6=B9=E3d=A1=A2=CD=F8=C2=E7=CE=AC=BB=A4=BA=CD=CD=F8=B9=DC=A3=BB=
=D2=D4
=C9=CF=C8=CB=D4=B1=C3=BF=C0=E0=D0=E8=D2=AA=D2=BB=B5=BD=C1=BD=C3=FB=A1=A3

=BA=CF=D7=F7=D5=BE=B5=E3=A3=BA=D2=AA=C7=F3=CC=E1=B9=A9=CF=C2=D4=D8=B7=FE=CE=
=F1=B5=C4=D5=BE=B5=E3=A3=AC=C8=E7=A3=BA=C8=ED=BC=FE=CF=C2=D4=D8=A3=BB=BD=CC=
=B3=CC=CF=C2=D4=D8=A3=BB=B5=C8=B5=C8=A1=A3

=B1=BE=D5=BE=D0=E9=C4=E2=D3=F2=C3=FB http://downloading.yeah.net


------=_NextPart_001_0080_01BDF6C7.FABAC1B0--

------=_NextPart_000_007F_01BDF6C7.FABAC1B0--





From rsvp-owner@ISI.EDU  Sun Jun 18 18:15:26 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10640
	for <rsvp-archive@lists.ietf.org>; Sun, 18 Jun 2000 18:15:25 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id MAA28517
	for rsvp-outgoing; Sun, 18 Jun 2000 12:37:19 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id MAA28512
	for <rsvp@zephyr.isi.edu>; Sun, 18 Jun 2000 12:37:18 -0700 (PDT)
Received: from csa.iisc.ernet.in (IDENT:root@csa.iisc.ernet.in [144.16.67.8])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id MAA28378
	for <rsvp@ISI.EDU>; Sun, 18 Jun 2000 12:37:59 -0700 (PDT)
Received: from helios.csa.iisc.ernet.in (IDENT:prasanna@helios.csa.iisc.ernet.in [144.16.67.46])
	by csa.iisc.ernet.in (8.9.3/8.9.3) with ESMTP id BAA04267
	for <rsvp@ISI.EDU>; Mon, 19 Jun 2000 01:09:11 +0530
Received: from localhost (prasanna@localhost)
	by helios.csa.iisc.ernet.in (8.9.3/8.9.3) with SMTP id BAA25158
	for <rsvp@ISI.EDU>; Mon, 19 Jun 2000 01:07:52 +0530
X-Authentication-Warning: helios.csa.iisc.ernet.in: prasanna owned process doing -bs
Date: Mon, 19 Jun 2000 01:07:51 +0530 (IST)
From: Gaitonde Anandprasanna <prasanna@csa.iisc.ernet.in>
To: rsvp@ISI.EDU
Subject: RSVP support for dynamic bandwidth?
Message-ID: <Pine.LNX.3.96.1000619010259.25099B-100000@helios.csa.iisc.ernet.in>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-rsvp@ISI.EDU
Precedence: bulk




For any VoIP kind of apllications where we require to reserve resources
along the path RSVP can be used. But lets say a call sessions is
in progress  and we need to increase the bandwidth along the path. Then
does RSVP have support for such dynamic adjustments of bandwidth
during a call session ?



  

                 
                     _____________________________                  
                   _ |ANANDPRASANNA GAITONDE     | _ 
                  / )|COMP. SCIENCE & AUTOMATION |( \
                 / / |D-7,IISc HOSTEL            | \ \
                / /  |INDIAN INSTITUTE OF SCIENCE|  \ \
              _( (_  |BANGALORE-560012.          |  _) )_
              (((\ \>|_/->___________________<-\_|</ /)))
              (\\\\ \_/ /LAB Ph.(080)3092906  \ \_/ ////)
               \       /HOSTEL Ph.-            \       /  
                \    _/     (080)3092452        \_    /     
                /   /-----------------------------\   \                  
               /  Email Id-                            \ 
              /      prasanna@csa.iisc.ernet.in         \
	     ---------------------------------------------
            -----------------------------------------------

--------------------------------------------------------------------------------
		
*************************************************************************  
| | | | __ ___   _____     __ _    _ __ (_) ___ ___     __| | __ _ _   _
| |_| |/ _` \ \ / / _ \   / _` |  | '_ \| |/ __/ _ \   / _` |/ _` | | | |
|  _  | (_| |\ V /  __/  | (_| |  | | | | | (_|  __/  | (_| | (_| | |_| |
|_| |_|\__,_| \_/ \___|   \__,_|  |_| |_|_|\___\___|   \__,_|\__,_|\__, |
*************************************************************************





From rsvp-owner@ISI.EDU  Sun Jun 18 21:13:37 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11533
	for <rsvp-archive@lists.ietf.org>; Sun, 18 Jun 2000 21:13:37 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id QAA09948
	for rsvp-outgoing; Sun, 18 Jun 2000 16:35:51 -0700 (PDT)
Received: from localhost (berson@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) with SMTP id PAA08655;
	Sun, 18 Jun 2000 15:55:48 -0700 (PDT)
Date: Sun, 18 Jun 2000 15:55:48 -0700 (PDT)
From: Steven Berson <berson@ISI.EDU>
To: Gaitonde Anandprasanna <prasanna@csa.iisc.ernet.in>
cc: rsvp@ISI.EDU
Subject: Re: RSVP support for dynamic bandwidth?
In-Reply-To: <Pine.LNX.3.96.1000619010259.25099B-100000@helios.csa.iisc.ernet.in>
Message-ID: <Pine.SUN.3.93.1000618155247.21032A-100000@zephyr.isi.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

On Mon, 19 Jun 2000, Gaitonde Anandprasanna wrote:

> For any VoIP kind of apllications where we require to reserve resources
> along the path RSVP can be used. But lets say a call sessions is
> in progress  and we need to increase the bandwidth along the path. Then
> does RSVP have support for such dynamic adjustments of bandwidth
> during a call session ?

RSVP supports dynamic adjustments of bandwidth at any time (as long as
they pass admission control).

Steve



From rsvp-owner@ISI.EDU  Sun Jun 18 21:26:50 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11577
	for <rsvp-archive@lists.ietf.org>; Sun, 18 Jun 2000 21:26:50 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id RAA11222
	for rsvp-outgoing; Sun, 18 Jun 2000 17:07:31 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id RAA11217
	for <rsvp@zephyr.isi.edu>; Sun, 18 Jun 2000 17:07:29 -0700 (PDT)
Received: (from braden@localhost)
	by boreas.isi.edu (8.9.3/8.9.3) id RAA00396;
	Sun, 18 Jun 2000 17:08:15 -0700 (PDT)
Date: Sun, 18 Jun 2000 17:08:15 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Message-Id: <200006190008.RAA00396@boreas.isi.edu>
To: rsvp@ISI.EDU, prasanna@csa.iisc.ernet.in
Subject: Re: RSVP support for dynamic bandwidth?
X-Sun-Charset: US-ASCII
Sender: owner-rsvp@ISI.EDU
Precedence: bulk


  *> From rsvp-owner@ISI.EDU Sun Jun 18 12:43:02 2000
  *> X-Authentication-Warning: helios.csa.iisc.ernet.in: prasanna owned process doing -bs
  *> Date: Mon, 19 Jun 2000 01:07:51 +0530 (IST)
  *> From: Gaitonde Anandprasanna <prasanna@csa.iisc.ernet.in>
  *> To: rsvp@ISI.EDU
  *> Subject: RSVP support for dynamic bandwidth?
  *> MIME-Version: 1.0
  *> Sender: owner-rsvp@ISI.EDU
  *> Precedence: bulk
  *> X-Lines: 41
  *> 
  *> 
  *> 
  *> 
  *> For any VoIP kind of apllications where we require to reserve resources
  *> along the path RSVP can be used. But lets say a call sessions is
  *> in progress  and we need to increase the bandwidth along the path. Then
  *> does RSVP have support for such dynamic adjustments of bandwidth
  *> during a call session ?
  *> 
  *> 

Yes.

Bob Braden


From rsvp-owner@ISI.EDU  Mon Jun 19 06:12:53 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28364
	for <rsvp-archive@lists.ietf.org>; Mon, 19 Jun 2000 06:12:52 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id BAA01755
	for rsvp-outgoing; Mon, 19 Jun 2000 01:09:49 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id BAA01750
	for <rsvp@zephyr.isi.edu>; Mon, 19 Jun 2000 01:09:47 -0700 (PDT)
Received: from qsibdc.qsi.com.tw ([211.75.17.86])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id BAA16566
	for <rsvp@isi.edu>; Mon, 19 Jun 2000 01:10:20 -0700 (PDT)
Message-Id: <200006190810.BAA16566@venera.isi.edu>
Received: from user (as16po94.ht.ficnet.net.tw [202.145.35.94]) by qsibdc.qsi.com.tw with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3)
	id NGQF0WQG; Mon, 19 Jun 2000 16:15:52 +0800
From: "HW" <HW001@HWENYA.COM.TW>
Reply-To: BMWR@TOMAIL.COM.TW
Subject: ㄉ
To: asiajy@ms.accnet.com.tw
X-Mailer: DiffondiCool V3,1,6,0 (W95/NT) (Build: Oct 18 1999)
Mime-Version: 1.0
Date: Mon, 19 Jun 2000 15:49:07 +0800
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

崩滤竒ㄥ獁难呼

硂琌и禦筁谋眔痷呼  

砯痷基龟    荡癸綼

Ω崩眖瞷祘Αи常Τ

稱穝砯呼ね碞パ秈........

「「「 http://welcome.to/jessycd 「「「「







From rsvp-owner@ISI.EDU  Mon Jun 19 11:24:55 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10490
	for <rsvp-archive@lists.ietf.org>; Mon, 19 Jun 2000 11:24:54 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id GAA18163
	for rsvp-outgoing; Mon, 19 Jun 2000 06:38:35 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id GAA18157
	for <rsvp@zephyr.isi.edu>; Mon, 19 Jun 2000 06:38:34 -0700 (PDT)
Received: from pmesmtp02.wcom.com (pmesmtp02.wcom.com [199.249.20.2])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id GAA25142
	for <rsvp@ISI.EDU>; Mon, 19 Jun 2000 06:39:17 -0700 (PDT)
Received: from CONVERSION-DAEMON by firewall.mcit.com (PMDF V5.2-32 #42257)
 id <0FWE00901LWJDF@firewall.mcit.com> for rsvp@ISI.EDU; Mon,
 19 Jun 2000 13:38:43 +0000 (GMT)
Received: from pmismtp04.wcomnet.com ([166.38.62.39])
 by firewall.mcit.com (PMDF V5.2-32 #42257)
 with ESMTP id <0FWE001FVLWI4L@firewall.mcit.com>; Mon,
 19 Jun 2000 13:38:42 +0000 (GMT)
Received: from CONVERSION-DAEMON by pmismtp04.wcomnet.com (PMDF V5.2-33 #42258)
 id <0FWE00G01LPKKP@pmismtp04.wcomnet.com>; Mon,
 19 Jun 2000 13:34:32 +0000 (GMT)
Received: from pmismtp04.wcomnet.com by pmismtp04.wcomnet.com
 (PMDF V5.2-33 #42258) with SMTP id <0FWE00G01LPFJO@pmismtp04.wcomnet.com>;
 Mon, 19 Jun 2000 13:34:32 +0000 (GMT)
Received: from omzexch006.mcit.com ([166.37.194.37])
 by pmismtp04.wcomnet.com (PMDF V5.2-33 #42258)
 with ESMTP id <0FWE00DCELP8AH@pmismtp04.wcomnet.com>; Mon,
 19 Jun 2000 13:34:21 +0000 (GMT)
Received: by omzexch006 with Internet Mail Service (5.5.2651.58)
 id <MWJZB69T>; Mon, 19 Jun 2000 13:38:30 +0000
Content-return: allowed
Date: Mon, 19 Jun 2000 13:38:21 +0000
From: "Rawlins, Diana" <Diana.Rawlins@wcom.com>
Subject: RE: RSVP support for dynamic bandwidth?
To: "'Gaitonde Anandprasanna'" <prasanna@csa.iisc.ernet.in>, rsvp@ISI.EDU
Message-id: <75C79E507864D3118AFC00805FEAB7D85B4E21@ripexch001.mcit.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-type: text/plain; charset=ISO-8859-1
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

Re-issue the RSVP PATH. However, there's no "guarantee" that a reservation
will be made at the new level.

-----Original Message-----
From: Gaitonde Anandprasanna [mailto:prasanna@csa.iisc.ernet.in]
Sent: Sunday, June 18, 2000 2:38 PM
To: rsvp@ISI.EDU
Subject: RSVP support for dynamic bandwidth?





For any VoIP kind of apllications where we require to reserve resources
along the path RSVP can be used. But lets say a call sessions is
in progress  and we need to increase the bandwidth along the path. Then
does RSVP have support for such dynamic adjustments of bandwidth
during a call session ?



  

                 
                     _____________________________                  
                   _ |ANANDPRASANNA GAITONDE     | _ 
                  / )|COMP. SCIENCE & AUTOMATION |( \
                 / / |D-7,IISc HOSTEL            | \ \
                / /  |INDIAN INSTITUTE OF SCIENCE|  \ \
              _( (_  |BANGALORE-560012.          |  _) )_
              (((\ \>|_/->___________________<-\_|</ /)))
              (\\\\ \_/ /LAB Ph.(080)3092906  \ \_/ ////)
               \       /HOSTEL Ph.-            \       /  
                \    _/     (080)3092452        \_    /     
                /   /-----------------------------\   \                  
               /  Email Id-                            \ 
              /      prasanna@csa.iisc.ernet.in         \
	     ---------------------------------------------
            -----------------------------------------------

----------------------------------------------------------------------------
----
		
*************************************************************************  
| | | | __ ___   _____     __ _    _ __ (_) ___ ___     __| | __ _ _   _
| |_| |/ _` \ \ / / _ \   / _` |  | '_ \| |/ __/ _ \   / _` |/ _` | | | |
|  _  | (_| |\ V /  __/  | (_| |  | | | | | (_|  __/  | (_| | (_| | |_| |
|_| |_|\__,_| \_/ \___|   \__,_|  |_| |_|_|\___\___|   \__,_|\__,_|\__, |
*************************************************************************




From rsvp-owner@ISI.EDU  Mon Jun 19 11:27:31 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10661
	for <rsvp-archive@lists.ietf.org>; Mon, 19 Jun 2000 11:27:30 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id GAA18795
	for rsvp-outgoing; Mon, 19 Jun 2000 06:46:11 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id GAA18785
	for <rsvp@zephyr.isi.edu>; Mon, 19 Jun 2000 06:46:09 -0700 (PDT)
Received: from csa.iisc.ernet.in (IDENT:root@csa.iisc.ernet.in [144.16.67.8])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id GAA25377
	for <rsvp@ISI.EDU>; Mon, 19 Jun 2000 06:46:47 -0700 (PDT)
Received: from helios.csa.iisc.ernet.in (IDENT:prasanna@helios.csa.iisc.ernet.in [144.16.67.46])
	by csa.iisc.ernet.in (8.9.3/8.9.3) with ESMTP id TAA11194
	for <rsvp@ISI.EDU>; Mon, 19 Jun 2000 19:18:00 +0530
Received: from localhost (prasanna@localhost)
	by helios.csa.iisc.ernet.in (8.9.3/8.9.3) with SMTP id TAA27973
	for <rsvp@ISI.EDU>; Mon, 19 Jun 2000 19:16:43 +0530
X-Authentication-Warning: helios.csa.iisc.ernet.in: prasanna owned process doing -bs
Date: Mon, 19 Jun 2000 19:16:42 +0530 (IST)
From: Gaitonde Anandprasanna <prasanna@csa.iisc.ernet.in>
To: rsvp@ISI.EDU
Subject: RSVP support for dynamic reservation
Message-ID: <Pine.LNX.3.96.1000619191421.27912B-100000@helios.csa.iisc.ernet.in>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-rsvp@ISI.EDU
Precedence: bulk


  Can u suggest any references or material which discusses the issue of
dynamic bandwidth reservation in RSVP i.e. changing the already reserved
bandwidth when the call session is in  progress.







                 
                     _____________________________                  
                   _ |ANANDPRASANNA GAITONDE     | _ 
                  / )|COMP. SCIENCE & AUTOMATION |( \
                 / / |D-7,IISc HOSTEL            | \ \
                / /  |INDIAN INSTITUTE OF SCIENCE|  \ \
              _( (_  |BANGALORE-560012.          |  _) )_
              (((\ \>|_/->___________________<-\_|</ /)))
              (\\\\ \_/ /LAB Ph.(080)3092906  \ \_/ ////)
               \       /HOSTEL Ph.-            \       /  
                \    _/     (080)3092452        \_    /     
                /   /-----------------------------\   \                  
               /  Email Id-                            \ 
              /      prasanna@csa.iisc.ernet.in         \
	     ---------------------------------------------
            -----------------------------------------------

--------------------------------------------------------------------------------
		
*************************************************************************  
| | | | __ ___   _____     __ _    _ __ (_) ___ ___     __| | __ _ _   _
| |_| |/ _` \ \ / / _ \   / _` |  | '_ \| |/ __/ _ \   / _` |/ _` | | | |
|  _  | (_| |\ V /  __/  | (_| |  | | | | | (_|  __/  | (_| | (_| | |_| |
|_| |_|\__,_| \_/ \___|   \__,_|  |_| |_|_|\___\___|   \__,_|\__,_|\__, |
*************************************************************************





From rsvp-owner@ISI.EDU  Mon Jun 19 13:01:44 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15131
	for <rsvp-archive@lists.ietf.org>; Mon, 19 Jun 2000 13:01:43 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id IAA29684
	for rsvp-outgoing; Mon, 19 Jun 2000 08:29:44 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id IAA29677
	for <rsvp@zephyr.isi.edu>; Mon, 19 Jun 2000 08:29:43 -0700 (PDT)
Received: from dibbler.ne.mediaone.net (IDENT:root@dibbler.ne.mediaone.net [24.218.56.247])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id IAA29924
	for <rsvp@isi.edu>; Mon, 19 Jun 2000 08:30:26 -0700 (PDT)
Received: (from rodrigc@localhost)
	by dibbler.ne.mediaone.net (8.9.3/8.9.3) id LAA06487
	for rsvp@isi.edu; Mon, 19 Jun 2000 11:30:23 -0400
Date: Mon, 19 Jun 2000 11:30:23 -0400
From: Craig Rodrigues <rodrigc@mediaone.net>
To: rsvp@ISI.EDU
Subject: Status of Internet drafts for RAPI and SCRAPI?
Message-ID: <20000619113023.A6482@mediaone.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1us
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

Hi,
 
What is the status for the RAPI and SCRAPI Internet
drafts?  The Internet draft for SCRAPI seems to have been
deleted from the IETF ftp site in March, and I couldn't
find the one for RAPI there.
 
Thanks.                  
-- 
Craig Rodrigues        
http://www.gis.net/~craigr    
rodrigc@mediaone.net          


From rsvp-owner@ISI.EDU  Mon Jun 19 14:14:22 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19300
	for <rsvp-archive@lists.ietf.org>; Mon, 19 Jun 2000 14:14:21 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id JAA06071
	for rsvp-outgoing; Mon, 19 Jun 2000 09:41:43 -0700 (PDT)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id JAA06065
	for <rsvp@zephyr.isi.edu>; Mon, 19 Jun 2000 09:41:41 -0700 (PDT)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id JAA06990;
	Mon, 19 Jun 2000 09:42:18 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id QAA01245;
	Mon, 19 Jun 2000 16:42:17 GMT
Date: Mon, 19 Jun 2000 16:42:17 GMT
Message-Id: <200006191642.QAA01245@gra.isi.edu>
To: rsvp@ISI.EDU, prasanna@csa.iisc.ernet.in
Subject: Re: RSVP support for dynamic reservation
X-Sun-Charset: US-ASCII
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

  *> 
  *> 
  *>   Can u suggest any references or material which discusses the issue of
  *> dynamic bandwidth reservation in RSVP i.e. changing the already reserved
  *> bandwidth when the call session is in  progress.
  *> 
  *> 

Hmmm.  I could swear that the RSVP spec said it clearly up front, but
that wording seems to have disappeared from the final RFC 2205.  I
guess that dynamic adaptation to changing reservation parameters is so
fundamental a property of RSVP that the RSVP WG members must assume it
goes without saying ;-).

The best we can point to is a paragraph buried in section 2.3
of RFC 2205:

	The state maintained by RSVP is dynamic; to change the set of
	senders Si or to change any QoS request, a host simply starts
	sending revised Path and/or Resv messages.  The result will
	be an appropriate adjustment in the RSVP state in all nodes
	along the path; unused state will time out if it is not
	explicitly torn down.

Bob Braden



From rsvp-owner@ISI.EDU  Mon Jun 19 14:21:37 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19433
	for <rsvp-archive@lists.ietf.org>; Mon, 19 Jun 2000 14:21:36 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id JAA07075
	for rsvp-outgoing; Mon, 19 Jun 2000 09:53:51 -0700 (PDT)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id JAA07062
	for <rsvp@zephyr.isi.edu>; Mon, 19 Jun 2000 09:53:50 -0700 (PDT)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id JAA09820;
	Mon, 19 Jun 2000 09:54:34 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id QAA01263;
	Mon, 19 Jun 2000 16:54:34 GMT
Date: Mon, 19 Jun 2000 16:54:34 GMT
Message-Id: <200006191654.QAA01263@gra.isi.edu>
To: rsvp@ISI.EDU, rodrigc@mediaone.net
Subject: Re: Status of Internet drafts for RAPI and SCRAPI?
X-Sun-Charset: US-ASCII
Sender: owner-rsvp@ISI.EDU
Precedence: bulk


  *> From rsvp-owner@ISI.EDU Mon Jun 19 08:36:10 2000
  *> Date: Mon, 19 Jun 2000 11:30:23 -0400
  *> From: Craig Rodrigues <rodrigc@mediaone.net>
  *> To: rsvp@ISI.EDU
  *> Subject: Status of Internet drafts for RAPI and SCRAPI?
  *> Mime-Version: 1.0
  *> X-Mailer: Mutt 1.0.1us
  *> Sender: owner-rsvp@ISI.EDU
  *> Precedence: bulk
  *> X-Lines: 12
  *> 
  *> Hi,
  *>  
  *> What is the status for the RAPI and SCRAPI Internet
  *> drafts?  The Internet draft for SCRAPI seems to have been
  *> deleted from the IETF ftp site in March, and I couldn't
  *> find the one for RAPI there.
  *>  
  *> Thanks.                  
  *> -- 
  *> Craig Rodrigues        
  *> http://www.gis.net/~craigr    
  *> rodrigc@mediaone.net          
  *> 

They are doubtless timed out.  However, we keep copies of all
RSVP-pertinent Internet Drafts under "Publications" on the RSVP WG web
page (www.isi.edu/rsvp).  Both RAPI and SCRAPI I-Ds are there.  However,
the RAPI I-D has really been superseded by the OpenGroup version.

Bob Braden


From rsvp-owner@ISI.EDU  Mon Jun 19 17:18:38 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23685
	for <rsvp-archive@lists.ietf.org>; Mon, 19 Jun 2000 17:18:37 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id MAA22359
	for rsvp-outgoing; Mon, 19 Jun 2000 12:23:01 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id MAA22354
	for <rsvp@zephyr.isi.edu>; Mon, 19 Jun 2000 12:23:00 -0700 (PDT)
Received: from public7.sta.net.cn (public7.sta.net.cn [202.96.199.67])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id MAA11187
	for <rsvp@isi.edu>; Mon, 19 Jun 2000 12:23:38 -0700 (PDT)
Received: from virgo2 (branch-2-b2.sta.net.cn [61.129.73.2])
	by public7.sta.net.cn (8.9.1a/8.9.1) with SMTP id DAA22260;
	Tue, 20 Jun 2000 03:23:32 +0800 (CST)
Message-Id: <200006191923.DAA22260@public7.sta.net.cn>
From: webmaster <xbctd@hotmail.com>
To: 038 <xbctd@hotmail.com>
Date: Tue, 20 Jun 2000 03:36:35 +0800
Reply-To: webmaster@myvirgo.com
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=XXFBFEF8BC-135EFBFEXX
Content-Transfer-Encoding: 7bit
X-Priority: 3
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

This is a Multipart MIME message. Since your mail reader
does not understand this format, some or all of this message may not be legible.

--XXFBFEF8BC-135EFBFEXX
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable



------------------------------------------
This message was sent to you by
Name: webmaster
Email Address: xbctd@hotmail.com
IP Address: VIRGO2
------------------------------------------

Using Aureate Group Mail Free Edition
Find out more about this product and try it=20
for free at: http://www.group-mail.com/1

--XXFBFEF8BC-135EFBFEXX
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<title>Myvirgo=D0=E9=C4=E2=C9=E7=C7=F8---=D3=C3=BB=A7=D7=A2=B2=E1</title>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dgb2312">
<META NAME=3D"Keywords" CONTENT=3D"food restaurant cafe kindergarten women =
clinic hospital beverage drinks gown wedding bridal store shopping mall tra=
ining center school beauty saloon entertainment gym sports club health fitn=
ess career book registration office reader user=20city member service sex roma=
nce love relationship mom parenting baby child children toy icecream chips =
snack seafood meat fish vegetable diet wine cocktail coffee tea masterpiece=
 teacher growth fairy tales expertise adolescence pregnancy discussion coup=
le ritual custom etiquette manners quote quotation heroine classics dress c=
lothes utensils stationery gift present fashion style housekeeping housewor=
k finance investment stock share future credit bank money computer IT pet d=
og sew hair skincare makeup cosmetice image design expert cinema movie thea=
ter drama CD VCD DVD LD game tape cassette MTV play star yoga new review ex=
ercise magazine newspaper astrology constellation puding aerobatics taste f=
lavour sweet candy cook chef intercourse groom man woman mother father boy =
girl husband wife marry marriage divorce seperate buy auction sell chat job=
 postcard wallpaper office rich plantation virgo virgin community my virtua=
l city building prize independent lady gentleman desktop tool beautiful pre=
tty cute fair slender slim audio video multimedia">
<meta name=3D"=B8=B5=E1=BF=E1=C9=D6=C6=D7=F7" content=3D"Arwen">
<meta name=3D"=C1=AA=CF=B5=B7=BD=CA=BD" content=3D"Arwenmax@yahoo.com.cn">
<link rel=3D"stylesheet" type=3D"text/css" href=3D"http://www.myvirgo.com/c=
oco.css">
</head>

<body bgcolor=3D"#FFFFFF" topmargin=3D"0" leftmargin=3D"0" background=3D"ht=
tp://www.myvirgo.com/service/image/backround.gif">
<table width=3D"750" border=3D"0" cellspacing=3D"0" cellpadding=3D"0" align=
=3D"center">
  <tr>=20
    <td width=3D"472" valign=3D"top">=20
      <table width=3D"750" border=3D"0" cellspacing=3D"0" cellpadding=3D"0"=
>
        <tr bgcolor=3D"69C08E">=20
          <td height=3D"60" colspan=3D"4">=20
            <div align=3D"center"><a href=3D"http://www.myvirgo.com"><img s=
rc=3D"http://www.myvirgo.com/banner/banner.gif" width=3D"468" height=3D"60"=
 border=3D"0"></a></div>
          </td>
        </tr>
        <tr bgcolor=3D"69C08E">=20
          <td colspan=3D"4" height=3D"30" valign=3D"bottom">=20
            <div align=3D"center"><img src=3D"http://www.myvirgo.com/servic=
e/image/title.gif" width=3D"472" height=3D"66"></div>
          </td>
        </tr>
        <tr bgcolor=3D"69C08E">=20
          <td colspan=3D"4">=20
            <div align=3D"center"></div>
          </td>
        </tr>
        <tr bgcolor=3D"69C08E">=20
          <td colspan=3D"4"></td>
        </tr>
        <tr bgcolor=3D"69C08E">=20
          <td colspan=3D"4"></td>
        </tr>
        <tr bgcolor=3D"69C08E">=20
          <td colspan=3D"4"></td>
        </tr>
      </table>
      <table width=3D"750" border=3D"0" cellspacing=3D"0" cellpadding=3D"0"=
 height=3D"100%">
        <tr bgcolor=3D"C8E3CE" valign=3D"top">=20
          <td>=20
            <p>MyVirgo.com=C8=C8=B3=CF=D1=FB=C7=EB=C4=FA=BC=D3=C8=EB=CE=D2=
=C3=C7=B5=C4=D0=E9=C4=E2=C9=E7=C7=F8=A3=AC=CF=D6=D4=DA=D7=A2=B2=E1=A3=AC=C4=
=FA=BD=AB=A3=BA <br>
              1=A3=AE =C1=A2=BC=B4=BC=D3=C8=EBMyVirgo=B7=E8=BF=F1=B4=F3=B3=
=E9=BD=B1=B5=DA=C8=FD=C2=D6=A3=AC=BD=B1=C6=B7=B7=E1=BA=F1=A3=AC=B0=FC=C0=A8=
 <br>
              =A1=A1=A1=A1Apple iBook=CA=D6=CC=E1=B5=E7=C4=D4 <br>
              =A1=A1=A1=A1Sony PlayStation2 =D3=CE=CF=B7=BB=FA=B8=BD=D5=FD=
=B0=E6=B9=E2=C5=CC <br>
              =A1=A1=A1=A1JVC White Magic MD=CB=E6=C9=ED=CC=FD <br>
              =A1=A1=A1=A1CASIO G-Shock =D0=C2=BF=EE=CA=D6=B1=ED <br>
              =A1=A1=A1=A1=B9=FA=BC=CA=D6=AA=C3=FB=BB=AF=D7=B1=C6=B7=B5=C8=
=B5=C8 </p>
            <p>2=A3=AE =C3=E2=B7=D1=D3=B5=D3=D0=BF=E7=CA=C0=BC=CD=B5=E4=B2=
=D8----MyVirgo=BB=E1=D4=B1=BF=A8=A3=AC=B2=CE=D3=EB=CD=F8=D5=BE=CD=C6=B9=E3=
=BB=EE=B6=AF=A1=A3 </p>
            <p>3=A3=AE =CF=ED=CA=DC=D3=E2=B0=D9=BC=D2MyVirgo=CC=D8=D4=BC=C9=
=CC=BB=A7=CC=E1=B9=A9=B5=C4=D5=DB=BF=DB=A3=AC=C8=C3=C4=FA=CA=B5=BB=DD=B5=BD=
=BC=D2=A1=A3 </p>
            <p>4=A3=AE =C1=EC=C8=A1MyVirgo=B8=F7=B4=F3=D4=DE=D6=FA=C9=CC=CC=
=E1=B9=A9=B5=C4=CF=FB=B7=D1=B5=D6=D3=C3=C8=AF=A1=A3 </p>
            <p>5=A3=AE =CF=ED=D3=C3=CD=F8=D5=BE=D3=C3=BB=A7=C7=F8=B5=C4=C1=
=C4=CC=EC=A1=A2=CA=B5=CA=B1=C5=C4=C2=F4=B5=C8=C9=E8=CA=A9=A3=AC=CB=D1=B9=BA=
=C4=E3=CF=F2=CD=F9=D2=D1=BE=C3=A1=A2=C8=AB=C7=F2=D7=EE=D0=C2=D7=EE=BF=E1=B5=
=C4=C9=CC=C6=B7=A1=A3 </p>
            <p>=C8=E7=B4=CB=BE=AB=B2=CA=B7=D7=B3=CA=A3=AC=BB=B9=B2=BB=C7=C0=
=CF=C8=D7=A2=B2=E1=A3=BF=C9=E7=C7=F8=C8=AB=CC=E5=C5=AE=D0=D4=B9=AB=C3=F1=BB=
=B6=D3=AD=C4=D0=CA=BF=BC=D3=C8=EB=A1=A3 <br>
              <br>
              MyVirgo.com=CA=C7=D6=D0=B9=FA=B5=DA=D2=BB=B6=C0=C1=A2=C5=AE=
=D0=D4=D0=E9=C4=E2=C9=E7=C7=F8=A1=A3 =CE=D2=C3=C7=B3=E4=C2=FA=C7=E9=C8=A4=
=B5=C4=D0=E9=C4=E2=B3=C7=CA=D0=C4=DC=CE=AA=D6=D0=B9=FA=B5=C4=CD=F8=C2=E7=C5=
=AE=D0=D4=CC=E1=B9=A9=BB=A5=B6=AF=CA=BD=B5=C4=D7=CA=D1=B6=BA=CD=B9=BA=CE=EF=
=B7=FE=CE=F1=A3=AC=D3=AA=D4=EC=CE=C2=DC=B0=B5=C4=C9=E7=C7=F8=BB=B7=BE=B3=A3=
=AC=C2=FA=D7=E3=CB=FD=C3=C7=B5=C4=B8=F7=D6=D6=D0=E8=C7=F3=A1=A3=20
              =CE=D2=C3=C7=B5=C4=D7=DA=D6=BC=CA=C7=B0=EF=D6=FA=D0=C2=D2=BB=
=B4=FA=B5=C4=D6=D0=B9=FA=C5=AE=D0=D4=B7=A2=BE=F2=D7=D4=C9=ED=C7=B1=C4=DC=A3=
=AC=BE=A1=CF=ED=CF=D6=B4=FA=C9=FA=BB=EE=C0=D6=C8=A4=A3=AC=C8=D5=D2=E6=CC=E1=
=B8=DF=D4=DA=CD=F8=C2=E7=C9=E7=C8=BA=D6=D0=B5=C4=B5=D8=CE=BB=A1=A3</p>
          </td>
        </tr>
        <tr bgcolor=3D"69C08E" valign=3D"top">=20
          <td>&nbsp;</td>
        </tr>
        <tr bgcolor=3D"C8E3CE" valign=3D"top">=20
          <td>=20
            <form method=3D"post" action=3D"http://www.myvirgo.com/register=
/reg1.php3" name=3D"">
              <p align=3D"center">=D3=C3=BB=A7=C3=FB=A3=BA=20
                <input type=3D"text" name=3D"nick">
                <br>
                =C3=DC=C2=EB=A3=BA(=B1=D8=D0=EB=CA=E4=C8=EB6=CE=BB=D2=D4=C9=
=CF=C3=DC=C2=EB=A3=A9=20
                <input type=3D"password" name=3D"pass1">
                <br>
                =C3=DC=C2=EB=C8=B7=C8=CF=A3=BA=20
                <input type=3D"password" name=3D"pass2">
                <br>
                e-mail=B5=D8=D6=B7=A3=BA=20
                <input type=3D"text" name=3D"email">
                <br>
                (=C7=EB=CA=E4=C8=EB=D5=E6=CA=B5=B5=C4e-mail=B5=D8=D6=B7=A3=
=AC=D2=D4=B1=E3=B1=BE=B4=CE=BB=EE=B6=AF=B5=C4=C1=AA=CF=B5=A3=A9<br>
                =D0=D4=B1=F0=A3=BA=20
                <select name=3D"sex">
                  <option value=3D"M">=C4=D0</option>
                  <option value=3D"F">=C5=AE</option>
                </select>
                <br>
                =C9=FA=C8=D5=A3=BA=20
                <input type=3D"text" name=3D"bd1" size=3D"4">
                =C4=EA=20
                <input type=3D"text" name=3D"bd2" size=3D"2">
                =D4=C2=20
                <input type=3D"text" name=3D"bd3" size=3D"2">
                =C8=D5 =A3=A8=C0=FD=C8=E7=A3=BA1980=C4=EA6=D4=C220=C8=D5=A3=
=A9 <br>
                <br>
                (=C8=E7=B9=FB=C4=FA=CA=C7=C9=CF=BA=A3=B5=D8=C7=F8=BB=E1=D4=
=B1=A3=AC=B2=A2=CF=A3=CD=FB=C9=EA=C7=EB=BB=E1=D4=B1=BF=A8=A3=AC=C7=EB=CE=F1=
=B1=D8=CC=EE=D0=B4=D5=E6=CA=B5=B5=C4=D0=D5=C3=FB=A1=A2=B5=D8=D6=B7=BA=CD=D3=
=CA=D5=FE=B1=E0=C2=EB)<br>
                =D5=E6=CA=B5=D0=D5=C3=FB=A3=BA=20
                <input type=3D"text" name=3D"fullname">
                <br>
                <br>
                =C1=AA=CF=B5=B5=D8=D6=B7=A3=BA=20
                <input type=3D"text" name=3D"address" size=3D"40">
                <br>
                =D3=CA=D5=FE=B1=E0=C2=EB=A3=BA=20
                <input type=3D"text" name=3D"postcode" size=3D"40">
              </p>
              <p align=3D"center">&nbsp; </p>
              <div align=3D"center">=20
                <input type=3D"submit" name=3D"Submit" value=3D"=CC=E1=BD=
=BB">
                =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=20
                <input type=3D"reset" name=3D"Submit2" value=3D"=C7=E5=B3=
=FD">
              </div>
              <p>&nbsp;=20
            </form>
          </td>
        </tr>
      </table>
      <table width=3D"750" border=3D"0" cellspacing=3D"0" cellpadding=3D"0"=
 height=3D"60">
        <tr bgcolor=3D"69C08E">=20
          <td>=20
            <div align=3D"center"><a href=3D"http://www.myvirgo.com"><img s=
rc=3D"http://www.myvirgo.com/banner/banner.gif" width=3D"468" height=3D"60"=
 border=3D"0"></a></div>
          </td>
        </tr>
      </table>
    </td>
  </tr>
  <tr bgcolor=3D"69C08E">=20
    <td valign=3D"top">=20
      <div align=3D"center"><img src=3D"http://www.myvirgo.com/service/imag=
e/copyright.gif" width=3D"750" height=3D"30" usemap=3D"#Map2" border=3D"0">=
<map name=3D"Map2"><area shape=3D"rect" coords=3D"103,3,127,28" href=3D"htt=
p://www.myvirgo.com/englishaboutus.htm" alt=3D"=B9=D8=D3=DA=CE=D2=C3=C7/abo=
ut us"=20title=3D"=B9=D8=D3=DA=CE=D2=C3=C7/about us"><area shape=3D"rect" coor=
ds=3D"70,3,94,28" href=3D"mailto:webmaster@myvirgo.com" alt=3D"e-mail" titl=
e=3D"e-mail"><area shape=3D"rect" coords=3D"37,4,61,29" href=3D"http://www.=
myvirgo.com/contact.htm" target=3D"_parent" alt=3D"=C1=AA=CF=B5=B7=BD=CA=BD=
" title=3D"=C1=AA=CF=B5=B7=BD=CA=BD"><area shape=3D"rect" coords=3D"4,3,28,=
28" href=3D"http://www.myvirgo.com/help.htm" alt=3D"=CD=F8=D5=BE=BD=E1=B9=
=B9" title=3D"=CD=F8=D5=BE=BD=E1=B9=B9"></map>=20
      </div>
    </td>
  </tr>
</table>
</body>
</html>=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00

--XXFBFEF8BC-135EFBFEXX--



From rsvp-owner@ISI.EDU  Mon Jun 19 23:56:27 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00344
	for <rsvp-archive@lists.ietf.org>; Mon, 19 Jun 2000 23:56:26 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id TAA20373
	for rsvp-outgoing; Mon, 19 Jun 2000 19:02:42 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id TAA20368
	for <rsvp@zephyr.isi.edu>; Mon, 19 Jun 2000 19:02:42 -0700 (PDT)
Received: from game99.fs.gnet.gd.cn (www.foshan.gd.cn [202.103.160.22])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id TAA29313
	for <rsvp@isi.edu>; Mon, 19 Jun 2000 19:03:15 -0700 (PDT)
Received: from houfeng ([202.98.73.126]) by game99.fs.gnet.gd.cn  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Tue, 20 Jun 2000 09:15:52 +0800
From: "82" <GkQXOnrPtL@FSyxjmUYkc.LbNvvatM3M.com>
Reply-To: a@ss.net
Message-ID: {BB76AEC2-4688-11D4-AC56-444553540000}@houfeng
Subject: 网上游云南
To: 82@ISI.EDU
X-Mailer:  V3,1,6,1 (W95/NT) (Build: Oct 18 1999)
Mime-Version: 1.0
Date: Tue, 20 Jun 2000 08:56:56 +0800
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by zephyr.isi.edu id TAA20369
Sender: owner-rsvp@ISI.EDU
Precedence: bulk
Content-Transfer-Encoding: 8bit

网上游云南 
http://fmyn.yeah.net   <-(较快)
http://yntn.yeah.net







From rsvp-owner@ISI.EDU  Tue Jun 20 14:16:36 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00914
	for <rsvp-archive@lists.ietf.org>; Tue, 20 Jun 2000 14:16:35 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id JAA27299
	for rsvp-outgoing; Tue, 20 Jun 2000 09:15:33 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id JAA27293
	for <rsvp@zephyr.isi.edu>; Tue, 20 Jun 2000 09:15:32 -0700 (PDT)
Received: from smtprch1.nortel.com (smtprch1.nortelnetworks.com [192.135.215.14])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id JAA29373
	for <rsvp@ISI.EDU>; Tue, 20 Jun 2000 09:16:15 -0700 (PDT)
Received: from zcard00n.ca.nortel.com (actually zcard00n) 
          by smtprch1.nortel.com; Tue, 20 Jun 2000 11:14:54 -0500
Received: from zcard00p.ca.nortel.com ([47.141.0.104]) 
          by zcard00n.ca.nortel.com 
          with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) 
          id N2WJ01M8; Tue, 20 Jun 2000 12:15:56 -0400
Received: from americasm01.nt.com (philwang-1.ca.nortel.com [47.23.83.18]) 
          by zcard00p.ca.nortel.com 
          with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) 
          id N2LHF35B; Tue, 20 Jun 2000 12:15:53 -0400
Message-ID: <394F98DB.6FA5F31C@americasm01.nt.com>
Date: Tue, 20 Jun 2000 12:16:27 -0400
X-Sybari-Space: 00000000 00000000 00000000
From: "Phil Wang" <pywang@nortelnetworks.com>
Organization: Nortel Networks
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: zh-CN,zh,en
MIME-Version: 1.0
To: tccc@ieee.org, diffserv@ietf.org, rsvp@ISI.EDU
Subject: CFP: IEEE P1520 Programmable Networks Meeting
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-rsvp@ISI.EDU
Precedence: bulk
Content-Transfer-Encoding: 7bit

Please accept our apologies for multiple copies.


-------- 	Call for Participation -----------

The IEEE P1520 working group is developing standard APIs for
Programmable Networks. The next meeting of IEEE P1520 will be held in
Santa Clara (Silicon Valley), California on July 18-19, 2000.

More info and registration: http://www.ieee-pin.org/

Marriott hotel bulk reservation (at a reasonable rate) is available
until June 26th.

Please forward this email to whom you think might be interested.

Thanks,
-- 
Phil Wang, Ph.D.
Nortel Networks Corporation
Webiste:www.openetlab.org
Email:	pywang@nortelnetworks.com
Tel:(613)765-6607 (ESN 395) Fax:(613)765-4962 (ESN 395)


From rsvp-owner@ISI.EDU  Tue Jun 20 14:57:37 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01630
	for <rsvp-archive@lists.ietf.org>; Tue, 20 Jun 2000 14:57:36 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id JAA00315
	for rsvp-outgoing; Tue, 20 Jun 2000 09:59:20 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id JAA00309
	for <rsvp@zephyr.isi.edu>; Tue, 20 Jun 2000 09:59:19 -0700 (PDT)
Received: from sol.extremenetworks.com (sol.extremenetworks.com [216.52.8.2])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id KAA02020
	for <rsvp@isi.edu>; Tue, 20 Jun 2000 10:00:00 -0700 (PDT)
Received: by SOL with Internet Mail Service (5.5.2650.21)
	id <M3SK1BZ1>; Tue, 20 Jun 2000 09:55:52 -0700
Message-ID: <808F64DDB492D3119D3C00508B5D8D733ECA33@SOL>
From: Andrew Smith <andrew@extremenetworks.com>
To: rap@iphighway.com
Cc: "'rsvp@isi. edu (E-mail)'" <rsvp@ISI.EDU>
Subject: RE: I-D ACTION:draft-ietf-rap-rsvp-newidentity-00.txt
Date: Tue, 20 Jun 2000 09:55:51 -0700
X-MS-TNEF-Correlator: <808F64DDB492D3119D3C00508B5D8D733ECA33@SOL>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01BFDAD8.64211406"
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01BFDAD8.64211406
Content-Type: text/plain;
	charset="iso-8859-1"

As an FYI, this draft contains *proposed* modified codepoints for use inside
RSVP POLICY_DATA objects, returning them to the codepoints that were
originally included in early drafts of what became RFC2752.

We would like to do a WG last call of this document as soon as we have a new
draft of the "Preemption Priority" document (currently RFC2751)  that
relinquishes one of these codepoints.

Andrew
RAP WG co-chair

> -----Original Message-----
> From:	Internet-Drafts@ietf.org [SMTP:Internet-Drafts@ietf.org]
> Sent:	Tuesday, June 20, 2000 3:47 AM
> Cc:	rap@iphighway.com
> Subject:	I-D ACTION:draft-ietf-rap-rsvp-newidentity-00.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Resource Allocation Protocol Working
> Group of the IETF.
> 
> 	Title		: Identity Representation for RSVP
> 	Author(s)	: S. Yadav,  R. Yavatkar,  R. Pabbati,
>                           P. Ford, T. Moore,  S. Herzog,
> 	Filename	: draft-ietf-rap-rsvp-newidentity-00.txt
> 	Pages		: 17
> 	Date		: 19-Jun-00
> 	
> This document describes the representation of identity information 
> in POLICY_DATA object [POL-EXT] for supporting policy based 
> admission control in RSVP. The goal of identity representation is to 
> allow a process on a system to securely identify the owner and the 
> application of the communicating process (e.g. user id) and convey 
> this information in RSVP messages (PATH or RESV) in a secure manner. 
> We describe the encoding of identities as RSVP policy element. We 
> describe the processing rules to generate identity policy elements 
> for multicast merged flows. Subsequently, we describe 
> representations of user identities for Kerberos and Public Key based 
> user authentication mechanisms. In summary we describe the use of 
> this identity information in an operational setting.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-rap-rsvp-newidentity-00.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-rap-rsvp-newidentity-00.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-rap-rsvp-newidentity-00.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. << Message: Untitled Attachment >> 

------_=_NextPart_000_01BFDAD8.64211406
Content-Type: application/ms-tnef
Content-Transfer-Encoding: base64

eJ8+IjUQAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQWAAwAOAAAA0AcGABQACQA3ADMAAgBmAQEggAMADgAAANAHBgAU
AAkANwAzAAIAZgEBCYABACEAAAA5NkU0REQ1RDlGNjVCQzRCQTg5OUQ4MDY1NjJDMkExMgBRBwEE
gAEANgAAAFJFOiBJLUQgQUNUSU9OOmRyYWZ0LWlldGYtcmFwLXJzdnAtbmV3aWRlbnRpdHktMDAu
dHh0AA0SAQ2ABAACAAAAAgACAAEDkAYA/A4AADAAAAALAAIAAQAAAAMAJgAAAAAAAwAuAAAAAAAD
ADYAAAAAAB4AcAABAAAAMgAAAEktRCBBQ1RJT046ZHJhZnQtaWV0Zi1yYXAtcnN2cC1uZXdpZGVu
dGl0eS0wMC50eHQAAAACAXEAAQAAABsAAAABv9q9O7iGMvjqRogR1J1YAFCLXY1zAARTlAAAHgAx
QAEAAAAHAAAAQVNNSVRIAAADABpAAAAAAB4AMEABAAAABwAAAEFTTUlUSAAAAwAZQAAAAAACAQkQ
AQAAAGAJAABcCQAA3RAAAExaRnW3+9ZOAwAKAHJjcGcxMjXSMgD7MzYB6CACpAPjCQIAY2gKwHNl
dDAeIAcTAoMAUBBWcHJx3jIRWQ5QA9URZX0KgAjIbCA7CW8OMDUCgAqBdT5jAFALAwzQAcEMwTE0
MjQX4jIxD0AYYjg4JxfiDzEX4jQzF9M1MMkYQzU3GLM2NBkjAcG1G2M5F9M4GzAX4jkPMb8X8hmQ
GSMdYBkgF+MxDkDZF+MyMhhDDiA5HRQPMLcdlBgxF+M1DiAgpDgfFPw2NR0UAcAdlB4BIqQXxfo5
GDUwGKUdgBkjGJIYU24yGfQl8BpiYwBBC2BukQ4QMDMzDGBsbgIgHmULphFQBCADkUZZSRAsIHRo
BAAgZHJ6YQGAIAWgAjALcQQgKhESoG9wbxEQZCog9wRhBpAIkGQp0QEAKrALgK50BCACEAXAdREQ
ICoxBmkBAAfwU1ZQIFAAT0xJQ1lfREHAVEEgb2JqBZAsMHspEAlwdAhwAwAnICkhZbptKSBvL4Ir
qikwYQVAzncEkCzABbBpZwuAB0D0bHks0WMKQAEAK5ALgDwgZQrAMiEpgwQgb2ZrMUAxEmIFkGEH
gAfwRuhDMjcOQC4KogqECoAqVyzAdwhgbCuQbGkWayzAL+FkL/BhIFfyRzaQYXMpwTIBM9IpNHhv
Y3UHgAIwKKAEIHOubwIgOUIxUCAQ4HYswD83UCfQB+AphDhDLMAiUPUJ0W0FMGk5oTvAPDAFEKh0
eSI4uCg44HIJcMcCMDIhNNQxKSAw9Alw8TagbnF1BAAvoDPBJ9DPOzUssSu4NUtBbimAB9C5NVRS
QS2AN3EFoC0Q0fxpcjVaCvQ2oB0CJsABQJ0qgXQukRHkGKAgLUbCDk8xtQXQB5BzYWdlP0bDNVZF
1EWhCxNF1mktbxgjNqAi4hf2YijQA2E6dQyDYhFASQIwBJERIC3aRDODQAiQADAuBbAvcMBbU01U
UDpMj02Vvl01VUuQBmACMEv3VApQkHNkYXkpEEp1QCEPAdApEBuxEUAzOjQ3ZRFQTVAHQ2NL9ymQ
cEVNcHApQGdod1GwLvUFoG1QCHUuc0v4TQARUEBDVElPTjopgy3NTYItVIFYcHN2WKA6odctEQIw
PMEtGZAuDNBGIP9If0mJRSQTgwwBQgQHs058+yzQKJF2C3ALYAJgLMADUvswAwIgLT9hLMBOfSlw
Q+DvLpExoQeQNUVUKUhegjYxvHJrLNBF8C/AO0VSB5D1CGFjLMBBMhA40DEgPDS/ReA40AbwN2Bj
kS9SRwNghHVwOzZJRVRGNUu/DIJRUDzAXyAMhGjhOkxw/1lVZIESoEChKgE8IyxiLVIZaGlBdSkw
BbAocylBaaVTLiBZYVGgds8pEAfwbdJewHRrCsBuROpQAaBiZXEsNVQ+0HB/VXD1UG3QRgWwZCkQ
VL1t0E05kAlwbkFtwUgEkNh6b2dv9WjDRgMQCfD/NJFppVffWO9Z+WjSb4BH8O8QoGl4ImBoaUQx
IGlaI+D+LVHxWcFoaGIqONYBAATy/zRgMOIswAlwassz4Xb2LNF/LGEAwDwjNVQy4S2vBUBbQYGh
LUVYVF0sU3O/ZxAqsAAgL1IqsDagYzIw72+wKtGBBW4AbQQBPDIp4n8DYAMgMuEtUm3QYoAswGf+
b0dxf5p+rSlRL+GFNWUxfwfgN1AqgWTwBBE5ojlweX83wC+0ERA9sT9QMjF3A2b7MjBfo3cn0AXA
AHArkDASn4U1g9CEgX83MBRtbVIAh48ThDKK1ShlLmdt0P8soQXALRA+wI3yKeE6UDIwfzVUKTOA
Woa1KxBHtJFBUO0uIEgxkQfwRS1gPsAy4f+LcYxDKxAAcI2xbdA1t33G/zADCfArsS9Sf5hh4TlC
LVP/hGU/UC+wORFt0DYRNVSYS/uKxS9ScieQfjIv8EfwjbF/enF/uJsMBCE1YyxikDBsvzwgNIA3
wQeATeArgWaKYf9BcFYSERA/kD3zKRA6AZhHvzVUfqwzw5HFmfcsYksEkO80YANgKJIrkFBWMISB
p0H7hLyRw2Fs0XcSZWUHgBDR+QMAc22isU5wg6GQIArA/zIwo8owEiyiM+GTCn/flET/A5EqoJ7S
PDFHcRERhBJBjPAgVVJMLFMpM12fS/AfNWQmwieQOiACQHA6L9Qvd7VwLk2GLywRTqT9M3QvdY92
n1nzRYInlTVpt2BuCsA6YWw5gF6pYjIw3wBwAiAGwAhgBCBGTkBt0P5Mc7Ay4QPwKTCs9gSgdOL9
NWMivXc88I3yiqE3sAPg23JBM9J5CGEzAC0AwAMR724AQnEEEG3QQQGAjcEJAP5nMdEvcAuAb/U8
0LAgO6C+YzLCtmvA1KoCaGkiR/DvfaG3X7hvWgEisU02oDfB/zPhYG9heDfhA6CYoQIQUgC/MsK0
L7U/P8BuAIpwLs9g/m0JULm4PtA1VAWxzuYBgE/PktMxtalNkS8x0KQt/wCQRfBBcLl/RDu6/82D
vFP/mKEuYCoSK4G9QcJkNUtQkX/BEpT1L9G0FmjSwoKR0XbfTXc1RauRMBIG4GSNMcThgdxaIkZJ
TEUgtj8Px//JD8obfFdOT1RF/0vzhzPCg91SjcJeYU2WzZIfLvQwAzjHzmdo0k1JTfxFLZkTokKA
gb0yLKAvVfc7oDwAANBrPPBs0AMQPMG/bdBRUC/wLKIpMmhpZjMQfy8RcwEqMQSQBUCPxo3yIoBF
TkNPRElON4B/hbAHgDzwNGAsYZi04FMiv2hp76Xs1AWCLSF+ZHMqsP/vAW0hKRDCEb6xOBEn0CuB
/+vgUgDsBAWwaGk3UOnzVWH/jvEAcKHhwpIJcG4Al3J6UD8GkO5gPeL3n/io7apleP0pQGI8wGFR
+ZY0YDoxPJH/KRD0cQWQBzEyITQQCfB9sf8HQC9SvsLG+qFjCrHKQOnj+ZTpaS6RcDi3OeEpQBDQ
/zokNGD/AfSA7JFoaWcRLBH/L/AAtF8hlPb1AbxxENCCkP9jsMITZULCsDjGfzXG6mzw94qABZKr
EXAnkJ7yQISU9vfkOnxXDGxCP1CKcYmC6GL/MSBjYQNT9XN0wb0C94SP8v/6n0P18NAGEQiIL+Gp
4e+wf2VxN/KIcoZgmkA6UTASQeBTQ0lJIOahheM7RGfXPymhbdA8PEeWafBVt3ciXyArkEGw8PZg
aDkDVD4+l6V9RKAAGsADAPE/CQQAAEAAOQDgh+xj2Nq/AR4AQhABAAAAIQAAADwyMDAwMDYyMDEw
NDYuR0FBMTY0NzZAaWV0Zi5vcmc+AAAAAAsAH4AIIAYAAAAAAMAAAAAAAABGAAAAAAOFAAAAAAAA
AwAhgAggBgAAAAAAwAAAAAAAAEYAAAAAEIUAAAAAAAADAByACCAGAAAAAADAAAAAAAAARgAAAABS
hQAA8xUAAB4AHYAIIAYAAAAAAMAAAAAAAABGAAAAAFSFAAABAAAABQAAADguMDQAAAAAAwAegAgg
BgAAAAAAwAAAAAAAAEYAAAAAAYUAAAAAAAALACCACCAGAAAAAADAAAAAAAAARgAAAAAOhQAAAAAA
AAMAIoAIIAYAAAAAAMAAAAAAAABGAAAAABGFAAAAAAAAAwAjgAggBgAAAAAAwAAAAAAAAEYAAAAA
GIUAAAAAAAAeACSACCAGAAAAAADAAAAAAAAARgAAAAA2hQAAAQAAAAEAAAAAAAAAHgAlgAggBgAA
AAAAwAAAAAAAAEYAAAAAN4UAAAEAAAABAAAAAAAAAB4AJoAIIAYAAAAAAMAAAAAAAABGAAAAADiF
AAABAAAAAQAAAAAAAAADAP0/5AQAAAMA3j+vbwAAAwCAEP////8CAUcAAQAAADcAAABjPVVTO2E9
IDtwPUV4dHJlbWUgTmV0d29ya3M7bD1TT0wtMDAwNjIwMTY1NTUxWi0xMzU1NjkAAAIB+T8BAAAA
UwAAAAAAAADcp0DIwEIQGrS5CAArL+GCAQAAAAAAAAAvTz1FWFRSRU1FIE5FVFdPUktTL09VPUVY
VFJFTUUvQ049UkVDSVBJRU5UUy9DTj1BU01JVEgAAB4A+D8BAAAADQAAAEFuZHJldyBTbWl0aAAA
AAAeADhAAQAAAAcAAABBU01JVEgAAAIB+z8BAAAAUwAAAAAAAADcp0DIwEIQGrS5CAArL+GCAQAA
AAAAAAAvTz1FWFRSRU1FIE5FVFdPUktTL09VPUVYVFJFTUUvQ049UkVDSVBJRU5UUy9DTj1BU01J
VEgAAB4A+j8BAAAADQAAAEFuZHJldyBTbWl0aAAAAAAeADlAAQAAAAcAAABBU01JVEgAAEAABzCW
2+dj2Nq/AUAACDAGFCFk2Nq/AR4APQABAAAABQAAAFJFOiAAAAAAHgAdDgEAAAAyAAAASS1EIEFD
VElPTjpkcmFmdC1pZXRmLXJhcC1yc3ZwLW5ld2lkZW50aXR5LTAwLnR4dAAAAB4ANRABAAAALQAA
ADw4MDhGNjREREI0OTJEMzExOUQzQzAwNTA4QjVEOEQ3MzNFQ0EzM0BTT0w+AAAAAAsAKQAAAAAA
CwAjAAAAAAADAAYQ11MxawMABxBCCgAAAwAQEAAAAAADABEQAgAAAB4ACBABAAAAZQAAAEFTQU5G
WUksVEhJU0RSQUZUQ09OVEFJTlMqUFJPUE9TRUQqTU9ESUZJRURDT0RFUE9JTlRTRk9SVVNFSU5T
SURFUlNWUFBPTElDWURBVEFPQkpFQ1RTLFJFVFVSTklOR1RIRU0AAAAAAgF/AAEAAAAtAAAAPDgw
OEY2NEREQjQ5MkQzMTE5RDNDMDA1MDhCNUQ4RDczM0VDQTMzQFNPTD4AAAAAYaA=

------_=_NextPart_000_01BFDAD8.64211406--


From rsvp-owner@ISI.EDU  Tue Jun 20 19:57:21 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06479
	for <rsvp-archive@lists.ietf.org>; Tue, 20 Jun 2000 19:57:20 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id PAA19870
	for rsvp-outgoing; Tue, 20 Jun 2000 15:23:18 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id PAA19864
	for <rsvp@zephyr.isi.edu>; Tue, 20 Jun 2000 15:23:16 -0700 (PDT)
Received: from dfssl.exchange.microsoft.com (dfssl.exchange.microsoft.com [131.107.88.59])
	by venera.isi.edu (8.9.3/8.9.3) with SMTP id PAA18543
	for <rsvp@isi.edu>; Tue, 20 Jun 2000 15:24:02 -0700 (PDT)
Received: from 172.30.236.11 by dfssl.exchange.microsoft.com (InterScan E-Mail VirusWall NT); Tue, 20 Jun 2000 15:15:40 -0700 (Pacific Daylight Time)
Received: from STAY.platinum.corp.microsoft.com ([172.30.236.91]) by yuri.dns.microsoft.com with Microsoft SMTPSVC(5.0.2195.2023);
	 Tue, 20 Jun 2000 15:24:36 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.4397.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFDB05.347C9504"
Subject: RE: RSVP support for dynamic reservation
Date: Tue, 20 Jun 2000 15:16:39 -0700
Message-ID: <078292D50C98D2118D090008C7E9C6A60FC64C9E@STAY.platinum.corp.microsoft.com>
Thread-Topic: RSVP support for dynamic reservation
Thread-Index: Ab/a9ieMDobNGKf3RuGnJkIUeFo2tgAD8zwQ
From: "Yoram Bernet" <yoramb@Exchange.Microsoft.com>
To: "Gaitonde Anandprasanna" <prasanna@csa.iisc.ernet.in>, <rsvp@ISI.EDU>
X-OriginalArrivalTime: 20 Jun 2000 22:24:36.0159 (UTC) FILETIME=[50CD6CF0:01BFDB06]
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

This is a multi-part message in MIME format.

------_=_NextPart_001_01BFDB05.347C9504
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

This should just work. I expect it's in RFC2205. From an end system
perspective, we allow an application to change its requested bandwidth
(or any other flowsepc characteristics) at any time. As a result, we
change the contents of the PATH or RESV messages sent and expect the
network to either accommodate or reject the modified requests...

Yoram

> -----Original Message-----
> From: Gaitonde Anandprasanna [mailto:prasanna@csa.iisc.ernet.in]
> Sent: Monday, June 19, 2000 6:47 AM
> To: rsvp@ISI.EDU
> Subject: RSVP support for dynamic reservation
>=20
>=20
>=20
>   Can u suggest any references or material which discusses=20
> the issue of
> dynamic bandwidth reservation in RSVP i.e. changing the=20
> already reserved
> bandwidth when the call session is in  progress.
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>                 =20
>                      _____________________________                 =20
>                    _ |ANANDPRASANNA GAITONDE     | _=20
>                   / )|COMP. SCIENCE & AUTOMATION |( \
>                  / / |D-7,IISc HOSTEL            | \ \
>                 / /  |INDIAN INSTITUTE OF SCIENCE|  \ \
>               _( (_  |BANGALORE-560012.          |  _) )_
>               (((\ \>|_/->___________________<-\_|</ /)))
>               (\\\\ \_/ /LAB Ph.(080)3092906  \ \_/ ////)
>                \       /HOSTEL Ph.-            \       / =20
>                 \    _/     (080)3092452        \_    /    =20
>                 /   /-----------------------------\   \      =20
>           =20
>                /  Email Id-                            \=20
>               /      prasanna@csa.iisc.ernet.in         \
> 	     ---------------------------------------------
>             -----------------------------------------------
>=20
> --------------------------------------------------------------
> ------------------
> 	=09
> **************************************************************
> *********** =20
> | | | | __ ___   _____     __ _    _ __ (_) ___ ___     __| |=20
> __ _ _   _
> | |_| |/ _` \ \ / / _ \   / _` |  | '_ \| |/ __/ _ \   / _`=20
> |/ _` | | | |
> |  _  | (_| |\ V /  __/  | (_| |  | | | | | (_|  __/  | (_| |=20
> (_| | |_| |
> |_| |_|\__,_| \_/ \___|   \__,_|  |_| |_|_|\___\___|  =20
> \__,_|\__,_|\__, |
> **************************************************************
> ***********
>=20
>=20
>=20

------_=_NextPart_001_01BFDB05.347C9504
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4397.0">
<TITLE>RE: RSVP support for dynamic reservation</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>This should just work. I expect it's in RFC2205. From =
an end system perspective, we allow an application to change its =
requested bandwidth (or any other flowsepc characteristics) at any time. =
As a result, we change the contents of the PATH or RESV messages sent =
and expect the network to either accommodate or reject the modified =
requests...</FONT></P>

<P><FONT SIZE=3D2>Yoram</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>

<BR><FONT SIZE=3D2>&gt; From: Gaitonde Anandprasanna [<A =
HREF=3D"mailto:prasanna@csa.iisc.ernet.in">mailto:prasanna@csa.iisc.ernet=
.in</A>]</FONT>

<BR><FONT SIZE=3D2>&gt; Sent: Monday, June 19, 2000 6:47 AM</FONT>

<BR><FONT SIZE=3D2>&gt; To: rsvp@ISI.EDU</FONT>

<BR><FONT SIZE=3D2>&gt; Subject: RSVP support for dynamic =
reservation</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; Can u suggest any references or =
material which discusses </FONT>

<BR><FONT SIZE=3D2>&gt; the issue of</FONT>

<BR><FONT SIZE=3D2>&gt; dynamic bandwidth reservation in RSVP i.e. =
changing the </FONT>

<BR><FONT SIZE=3D2>&gt; already reserved</FONT>

<BR><FONT SIZE=3D2>&gt; bandwidth when the call session is in&nbsp; =
progress.</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT>

<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
_____________________________&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT>

<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; _ |ANANDPRASANNA =
GAITONDE&nbsp;&nbsp;&nbsp;&nbsp; | _ </FONT>

<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; / )|COMP. SCIENCE &amp; =
AUTOMATION |( \</FONT>

<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; / / |D-7,IISc =
HOSTEL&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
| \ \</FONT>

<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; / /&nbsp; |INDIAN INSTITUTE OF =
SCIENCE|&nbsp; \ \</FONT>

<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; _( (_&nbsp; =
|BANGALORE-560012.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp; _) )_</FONT>

<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; (((\ =
\&gt;|_/-&gt;___________________&lt;-\_|&lt;/ /)))</FONT>

<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; (\\\\ \_/ /LAB Ph.(080)3092906&nbsp; \ \_/ =
////)</FONT>

<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
/HOSTEL =
Ph.-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
\&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /&nbsp; </FONT>

<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \&nbsp;&nbsp;&nbsp; =
_/&nbsp;&nbsp;&nbsp;&nbsp; =
(080)3092452&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
\_&nbsp;&nbsp;&nbsp; /&nbsp;&nbsp;&nbsp;&nbsp; </FONT>

<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /&nbsp;&nbsp; =
/-----------------------------\&nbsp;&nbsp; =
\&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT>

<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; </FONT>

<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /&nbsp; Email =
Id-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; \ </FONT>

<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; /&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
prasanna@csa.iisc.ernet.in&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; \</FONT>

<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp; =
---------------------------------------------</FONT>

<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; -----------------------------------------------</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; =
--------------------------------------------------------------</FONT>

<BR><FONT SIZE=3D2>&gt; ------------------</FONT>

<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT>

<BR><FONT SIZE=3D2>&gt; =
**************************************************************</FONT>

<BR><FONT SIZE=3D2>&gt; ***********&nbsp; </FONT>

<BR><FONT SIZE=3D2>&gt; | | | | __ ___&nbsp;&nbsp; =
_____&nbsp;&nbsp;&nbsp;&nbsp; __ _&nbsp;&nbsp;&nbsp; _ __ (_) ___ =
___&nbsp;&nbsp;&nbsp;&nbsp; __| | </FONT>

<BR><FONT SIZE=3D2>&gt; __ _ _&nbsp;&nbsp; _</FONT>

<BR><FONT SIZE=3D2>&gt; | |_| |/ _` \ \ / / _ \&nbsp;&nbsp; / _` |&nbsp; =
| '_ \| |/ __/ _ \&nbsp;&nbsp; / _` </FONT>

<BR><FONT SIZE=3D2>&gt; |/ _` | | | |</FONT>

<BR><FONT SIZE=3D2>&gt; |&nbsp; _&nbsp; | (_| |\ V /&nbsp; __/&nbsp; | =
(_| |&nbsp; | | | | | (_|&nbsp; __/&nbsp; | (_| | </FONT>

<BR><FONT SIZE=3D2>&gt; (_| | |_| |</FONT>

<BR><FONT SIZE=3D2>&gt; |_| |_|\__,_| \_/ \___|&nbsp;&nbsp; \__,_|&nbsp; =
|_| |_|_|\___\___|&nbsp;&nbsp; </FONT>

<BR><FONT SIZE=3D2>&gt; \__,_|\__,_|\__, |</FONT>

<BR><FONT SIZE=3D2>&gt; =
**************************************************************</FONT>

<BR><FONT SIZE=3D2>&gt; ***********</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BFDB05.347C9504--


From rsvp-owner@ISI.EDU  Thu Jun 22 02:38:42 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21823
	for <rsvp-archive@lists.ietf.org>; Thu, 22 Jun 2000 02:38:31 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id VAA09853
	for rsvp-outgoing; Wed, 21 Jun 2000 21:50:59 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id VAA09840
	for <rsvp@zephyr.isi.edu>; Wed, 21 Jun 2000 21:50:56 -0700 (PDT)
Received: from gocpe.com (dt0a0na4.tampabay.rr.com [24.92.23.164])
	by venera.isi.edu (8.9.3/8.9.3) with SMTP id VAA11910;
	Wed, 21 Jun 2000 21:51:35 -0700 (PDT)
Date: Wed, 21 Jun 2000 21:51:35 -0700 (PDT)
From: sales@gocpe.com
Message-Id: <200006220451.VAA11910@venera.isi.edu>
Reply-To: sales@gocpe.com
To: sales@gocpe.com
Subject: Microsoft at 82% OFF Retail - Education Software Discounts
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

SOFTWARE AT EDUCATION DISCOUNT PRICES - 
EXCLUSIVELY FOR K-12 TEACHERS, STAFF & SCHOOLS
 
Dear School Teachers, Staff, and Administrators, 
 
COMPUTER PRODUCTS FOR EDUCATION (CPE) is offering MICROSOFT and other major-brand software at enormous education discounts* - up to 82% OFF retail prices.  Here are some examples: 
                                      Retail       CPE
                                       Price       Price     Disc
 
MICROSOFT Office 2000 Standard        $499.95     $142.95     71%
MICROSOFT Office 2000 Professional    $599.95     $182.95     70%
MICROSOFT Office 2000 Premium         $799.95     $299.95     63%
MICROSOFT Visual Studio Pro 6.0       $1079.95    $239.95     78%
MICROSOFT Visual Basic Pro 6.0        $549.95     $ 99.95     82%
MICROSOFT Office 98 for Macintosh     $499.95     $172.95     65%
MICROSOFT Windows 2000 Pro            $319.95     $117.95     63%
    
For a list of the hundreds of other software products available from CPE at similar discounts, click onto www.goCPE.com or call us at 800-679-7007. 
 
For school purchases of five(5) or more units, please call 800-679-7007 for even deeper discounts on license packs. 
 
Academic Edition software is exactly the same as the Full-Retail Versions.  It is discounted for qualified education buyers. You must be a current K-12 teacher or staff member to purchase software from CPE.  All purchasers must provide fax-verification of status as teacher or staff.  After placing your order, you simply fax to CPE either: (a) a copy of a current picture School I.D. Card or, (b) a current paycheck stub with an alternative picture I.D. (drivers license, etc.).  School purchases require a valid school purchase order.  For more details, visit our web site at www.goCPE.com.
 
* CPE is an authorized Education Reseller for Microsoft, Corel, Symantec, Macromedia and many other major software manufacturers. CPE is the only national software distributor committed to providing the lowest prices EXCLUSIVELY to the Education community.
 
 
 
___________________________________________________________
If you wish to be removed from this advertiser's future mailings, please reply
with the subject "Remove" and this software will automatically block you 
from their future mailings.




From rsvp-owner@ISI.EDU  Fri Jun 23 08:32:50 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08392
	for <rsvp-archive@lists.ietf.org>; Fri, 23 Jun 2000 08:32:49 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id DAA04034
	for rsvp-outgoing; Fri, 23 Jun 2000 03:46:31 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id DAA04029
	for <rsvp@zephyr.isi.edu>; Fri, 23 Jun 2000 03:46:29 -0700 (PDT)
Received: from uni-paderborn.de (uni-paderborn.de [131.234.22.30])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id DAA25577
	for <rsvp@isi.edu>; Fri, 23 Jun 2000 03:47:13 -0700 (PDT)
Received: from hiddensee.c-lab.de ([131.234.81.161]:1789 "EHLO
        uni-paderborn.de") by mail.uni-paderborn.de with ESMTP
	id <S38230AbQFWKrN>; Fri, 23 Jun 2000 12:47:13 +0200
Message-ID: <3953402A.EC931A99@uni-paderborn.de>
Date:   Fri, 23 Jun 2000 12:47:06 +0200
From: Simon Schneider <atteln@uni-paderborn.de>
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: rsvp@ISI.EDU
Subject: TSpec Sum
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-rsvp@ISI.EDU
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,
to do some analysis, I need to sum up sender TSpecs of multiple streams.
Is it correct if I use

- the sum of the rate values
- the sum of the burst values
- the sum of the peak values (or infinity)
- the max of the M's
- the min of the m's

?

Thanks for help,
cheers, Simon



From rsvp-owner@ISI.EDU  Fri Jun 23 15:08:21 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17758
	for <rsvp-archive@lists.ietf.org>; Fri, 23 Jun 2000 15:08:20 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id KAA04284
	for rsvp-outgoing; Fri, 23 Jun 2000 10:43:37 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id KAA04279
	for <rsvp@zephyr.isi.edu>; Fri, 23 Jun 2000 10:43:36 -0700 (PDT)
Received: from 255.255.255.255 ([202.97.100.69])
	by venera.isi.edu (8.9.3/8.9.3) with SMTP id KAA13720
	for <rsvp@isi.edu>; Fri, 23 Jun 2000 10:44:12 -0700 (PDT)
Date: Fri, 23 Jun 2000 10:44:12 -0700 (PDT)
From: Hang Cheong <no@body.com>
To: <rsvp@ISI.EDU>
Message-Id: <419.436701.06812095no@body.com>
Subject: 筿秎 の 肚痷 約綪
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-rsvp@ISI.EDU
Precedence: bulk
Content-Transfer-Encoding: 7bit

                                        瓣悔
                        HANG CHEONG INTERNATIONAL

穝Θカ初︽綪:

      眤琌竒盽┹甶︽綪恨笵端福惮?
祅厨,馒粁約┪秎盚⒁③ (Direct Mail)琌竒礚猭笷Θ眤箇戳約狦?
籔ㄤ盢丁㎝窥禣Θぃ裹侣Τ︽綪よΑ,某眤话候碝穝よ猭ㄓ
瞷︽約︽綪よΑ.肚参約︽綪よΑ禣びτ約禣ノ㎝約
痲┕┕ぃΘタゑ,砛そ竒筁糵稸蝶︳常э蹦程竒蕾е硉狦
"⒂⌒③⑾⒆②約︽綪 の 肚痷約︽綪" 碞琌--呼悔呼隔⒁③祇癳約,
ウ絋龟竒蕾е硉τだΤ

    竒厨陪跌呼隔︽綪–1000癸 1.5 .
ョ,30000000窾虫 0.0015单45000
碞琌窾きめ穦蛤眤禦,眤砯珇瞓50じ,ê寥
50’45000∽2250000,κ窾!!!!!

叫拜ネ材κ窾璶寥,瞷碞Τる碞寥κ窾.
柬硅蛤┮竒綪玻珇Τ闽.璶т癸玻珇.淮肞寥窥⊿拜肈.
__________________________________________________________________________
甅︽綪ㄣ扳,3000窾めE-MAIL.琵跑ōΘSUPER SALESMAN.

盡穨蔼硉祇筿秎硁ン.(ぃ斗璶硓筁ヴISPMAIL SERVER,р筿福讽盡穨
MAIL SERVER Ч磷筁ISPCUT獺玒参,硉禬е).ㄏノ虏虫.

*翠窾めE-MAIL獺絚.
*芖κ窾めE-MAIL獺絚.
*嘲き窾めE-MAIL獺絚.
*窾めE-MAIL獺絚.
*禬筁30跋だ摸の贺︽穨だ摸筿秎:
*砋-Bag *麓珇-Textile *︾狝-Garment *らノ竟ㄣ-Furniture *筿福-Computer....
 (程穝ら戳20006る1腹)

*Τ6る禣穝戈(–る窾)*

*(硈翠2000坝穨25窾め肚痷腹絏(だ︽穨,跋,そ,硈硁ン)*

硈 *癳砯   *紇钩毙厩    *硁ン穝   *戈穝

*ㄏノCD-ROM盒杆更.(ㄏノCD-AutoRunの垫虫匡兜ざ)
 
(甅扳$500) ッ礚Ωㄏノ

500じぃ筁琌щ戈砛瞷ぃ惠璶螟玂璶崩綪
玻珇┪狝叭惠璶
**************************************************************************
セそ局Τ狝竟盡だ摸Μ栋︽穨 Email Address
惠璶︽穨だ摸 Email Address叫繦羛蹈и
**************************************************************************
ぃ璶淮筁硂寥窥诀穦翅

(璹潦荐絬)-(852)-23488365 ネ

:翠纒à﹁瑅垫刁玭5腹辨à稨18加1810(κρ蹲栏皘癸).
ADD :Room 1810,Good Hope Building,No.5-7 Sai Yeung Choi ST,Mongkok.HK





From rsvp-owner@ISI.EDU  Fri Jun 23 20:06:43 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23200
	for <rsvp-archive@lists.ietf.org>; Fri, 23 Jun 2000 20:06:42 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id PAA00567
	for rsvp-outgoing; Fri, 23 Jun 2000 15:41:23 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id PAA00562
	for <rsvp@zephyr.isi.edu>; Fri, 23 Jun 2000 15:41:21 -0700 (PDT)
Received: from postal.redback.com (postal.redback.com [155.53.12.9])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id PAA26548
	for <rsvp@isi.edu>; Fri, 23 Jun 2000 15:42:06 -0700 (PDT)
Received: from malt.redback.com (malt.redback.com [155.53.12.41])
	by postal.redback.com (Postfix) with ESMTP
	id 185342AA0F; Fri, 23 Jun 2000 15:41:38 -0700 (PDT)
Received: (from rahul@localhost)
	by malt.redback.com (8.9.3-LCCHA/8.9.3/null redback solaris client) id PAA01898;
	Fri, 23 Jun 2000 15:40:50 -0700 (PDT)
Date: Fri, 23 Jun 2000 15:40:49 -0700
From: Rahul Aggarwal <rahul@redback.com>
To: lberger@labn.net, swallow@cisco.com
Cc: rsvp@ISI.EDU
Subject: operation subobject in an EXPLICIT_ROUTE object
Message-ID: <20000623154049.D14229@malt.redback.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

Lou et al.,
draft-ietf-mpls-rsvp-lsp-tunnel-05.txt says (4.3.2):

  "The explicit route is encoded as a series of subobjects contained in
   an EXPLICIT_ROUTE object.  Each subobject may identify a group of
   nodes in the explicit route or may specify an operation to be
   performed along the path."

The text on processing of the explicit route object also talks about an 
'operation suboject' in a few places e.g: (4.3.4.1)

   "If the first subobject is an
   operation subobject, the message is in error and the system SHOULD
   return a "Bad EXPLICIT_ROUTE object" error. "

I haven't been able to find a definition of the operation subobject. There 
is no specified value for an 'operation subobject' in the type field of an ERO
subobject either. Is the definition of such an object a matter of local
policy? 

I will appreciate it if you could shed some light on the usage, definition and
format of this subobject. 

thanks,
rahul



From rsvp-owner@ISI.EDU  Sat Jun 24 19:37:44 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16037
	for <rsvp-archive@lists.ietf.org>; Sat, 24 Jun 2000 19:37:44 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id PAA28552
	for rsvp-outgoing; Sat, 24 Jun 2000 15:03:51 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id PAA28546
	for <rsvp@zephyr.isi.edu>; Sat, 24 Jun 2000 15:03:49 -0700 (PDT)
Received: from postal.redback.com (postal.redback.com [155.53.12.9])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id PAA09554
	for <rsvp@ISI.EDU>; Sat, 24 Jun 2000 15:04:26 -0700 (PDT)
Received: from malt.redback.com (malt.redback.com [155.53.12.41])
	by postal.redback.com (Postfix) with ESMTP
	id B4E3A2AA04; Sat, 24 Jun 2000 15:03:48 -0700 (PDT)
Received: (from rahul@localhost)
	by malt.redback.com (8.9.3-LCCHA/8.9.3/null redback solaris client) id PAA24239;
	Sat, 24 Jun 2000 15:03:01 -0700 (PDT)
Date: Sat, 24 Jun 2000 15:03:01 -0700
From: Rahul Aggarwal <rahul@redback.com>
To: rsvp@ISI.EDU
Cc: rahul@redback.com
Subject: operation subobject
Message-ID: <20000624150301.C20798@malt.redback.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

Lou et al.,
draft-ietf-mpls-lsp-tunnel-05.txt says: (4.3.2)

" The explicit route is encoded as a series of subobjects contained in
   an EXPLICIT_ROUTE object.  Each subobject may identify a group of
   nodes in the explicit route or may specify an operation to be
   performed along the path."

The 'operation subobject' is also mentioned a few times in the section on 
processing of the explicit route object (4.3.4). Eg:

 "If the first subobject is an
   operation subobject, the message is in error and the system SHOULD
   return a "Bad EXPLICIT_ROUTE object" error"

I have not been able to find encodings etc of the operation subobject. No
value has been assigned for an operation subobject in the type field of
an ERO subobject. Are the details of this object a matter of local policy?

I will appreciate it if you could shed some light on the usage, definition and
format of the operation subobject.

Thanks,
rahul



From rsvp-owner@ISI.EDU  Mon Jun 26 11:29:29 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08482
	for <rsvp-archive@lists.ietf.org>; Mon, 26 Jun 2000 11:29:28 -0400 (EDT)
Received: (from majordom@localhost)
	by zephyr.isi.edu (8.9.3/8.9.3) id GAA20994
	for rsvp-outgoing; Mon, 26 Jun 2000 06:32:28 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id GAA20984
	for <rsvp@zephyr.isi.edu>; Mon, 26 Jun 2000 06:32:26 -0700 (PDT)
Received: from rambo.globespan.net (p1.globespan.net [209.191.59.250])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id GAA16614
	for <rsvp@ISI.EDU>; Mon, 26 Jun 2000 06:33:11 -0700 (PDT)
Received: from globespan.net (ROHIT [192.168.25.21]) by rambo.globespan.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id NN0415T1; Mon, 26 Jun 2000 09:31:55 -0400
Message-ID: <39575B68.AEC525E@globespan.net>
Date: Mon, 26 Jun 2000 09:32:24 -0400
From: Rohit Chhapolia <rohit@globespan.net>
Organization: Globespan, Inc.
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Rahul Aggarwal <rahul@redback.com>
CC: rsvp@ISI.EDU
Subject: Re: operation subobject
References: <20000624150301.C20798@malt.redback.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-rsvp@ISI.EDU
Precedence: bulk
Content-Transfer-Encoding: 7bit

Rahul,

There used to be an operational sub-object in the previous
versions of this draft which has been removed after much
discussion on the mailing list and the conclusion that it
is not being used. The text in these sections has not been
updated accordingly. I guess it will get updated in the next
version.

Rohit

Rahul Aggarwal wrote:
> 
> Lou et al.,
> draft-ietf-mpls-lsp-tunnel-05.txt says: (4.3.2)
> 
> " The explicit route is encoded as a series of subobjects contained in
>    an EXPLICIT_ROUTE object.  Each subobject may identify a group of
>    nodes in the explicit route or may specify an operation to be
>    performed along the path."
> 
> The 'operation subobject' is also mentioned a few times in the section on
> processing of the explicit route object (4.3.4). Eg:
> 
>  "If the first subobject is an
>    operation subobject, the message is in error and the system SHOULD
>    return a "Bad EXPLICIT_ROUTE object" error"
> 
> I have not been able to find encodings etc of the operation subobject. No
> value has been assigned for an operation subobject in the type field of
> an ERO subobject. Are the details of this object a matter of local policy?
> 
> I will appreciate it if you could shed some light on the usage, definition and
> format of the operation subobject.
> 
> Thanks,
> rahul

-- 
Rohit Chhapolia
Globespan, Inc.
mailto:rohit@globespan.net
http://www.globespan.net


From rsvp-owner@ISI.EDU  Mon Jun 26 11:37:19 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08726
	for <rsvp-archive@lists.ietf.org>; Mon, 26 Jun 2000 11:37:19 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id HAA23058
	for rsvp-outgoing; Mon, 26 Jun 2000 07:02:42 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id HAA23052
	for <rsvp@zephyr.isi.edu>; Mon, 26 Jun 2000 07:02:40 -0700 (PDT)
Received: from saragosso.telin.nl (mail.telin.nl [195.169.17.170])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id HAA17939
	for <rsvp@ISI.EDU>; Mon, 26 Jun 2000 07:03:24 -0700 (PDT)
Received: from telin.nl ([195.169.16.130])
          by archief.telin.nl (Lotus Domino Release 5.0.3 (Intl))
          with ESMTP id 2000062616033955:13 ;
          Mon, 26 Jun 2000 16:03:39 +0200 
Message-ID: <395762C2.1AA04784@telin.nl>
Date: Mon, 26 Jun 2000 16:03:46 +0200
From: Cristian Hesselman <hesselman@telin.nl>
Organization: Telematica Instituut
X-Mailer: Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: rsvp@ISI.EDU
Subject: unsuscribe
References: <38DA5014.994A7B3A@tid.es>
X-MIMETrack: Itemize by SMTP Server on ARCHIEF/SRV/TELIN/NL(Release 5.0.3 (Intl)|21
 March 2000) at 06/26/2000 04:03:39 PM,
	Serialize by Router on TELINEXT/SRV/TELINDMZ/NL(Release 5.0.3 (Intl)|21
 March 2000) at 06/26/2000 04:07:21 PM,
	Serialize complete at 06/26/2000 04:07:21 PM
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
Sender: owner-rsvp@ISI.EDU
Precedence: bulk
Content-Transfer-Encoding: 7bit

unsuscribe


From rsvp-owner@ISI.EDU  Mon Jun 26 12:37:04 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10328
	for <rsvp-archive@lists.ietf.org>; Mon, 26 Jun 2000 12:37:03 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id HAA25962
	for rsvp-outgoing; Mon, 26 Jun 2000 07:44:27 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id HAA25954
	for <rsvp@zephyr.isi.edu>; Mon, 26 Jun 2000 07:44:25 -0700 (PDT)
Received: from newman.gte.com ([132.197.8.26])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id HAA20293
	for <rsvp@ISI.EDU>; Mon, 26 Jun 2000 07:45:09 -0700 (PDT)
Received: from beakman.gte.com (BEAKMAN.gte.com [132.197.135.175])
	by newman.gte.com (8.9.1/8.9.1) with ESMTP id KAA21792
	for <rsvp@ISI.EDU>; Mon, 26 Jun 2000 10:44:42 -0400 (EDT)
Message-Id: <4.3.1.2.20000626104704.00dc2e10@pophost.gte.com>
X-Sender: llc0@pophost.gte.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Mon, 26 Jun 2000 10:47:38 -0400
To: rsvp@ISI.EDU
From: Lynn Chen <lchen@gte.com>
Subject: unsuscribe
In-Reply-To: <395762C2.1AA04784@telin.nl>
References: <38DA5014.994A7B3A@tid.es>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

unsuscribe

--- Lingrong (Lynn) Chen, 781-466-4130, Pager 
800-393-3504/3933504@skytel.com, <lchen@gte.com>



From rsvp-owner@ISI.EDU  Mon Jun 26 16:55:28 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15660
	for <rsvp-archive@lists.ietf.org>; Mon, 26 Jun 2000 16:55:26 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id MAA17562
	for rsvp-outgoing; Mon, 26 Jun 2000 12:05:05 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id MAA17511
	for <rsvp@zephyr.isi.edu>; Mon, 26 Jun 2000 12:05:01 -0700 (PDT)
Received: from mail.bb.ah163.net ([202.102.200.76])
	by venera.isi.edu (8.9.3/8.9.3) with SMTP id MAA03142
	for <rsvp@isi.edu>; Mon, 26 Jun 2000 12:05:44 -0700 (PDT)
Message-Id: <200006261905.MAA03142@venera.isi.edu>
Received: from zlx([202.111.200.197]) by aimc.com(JetMail 2.5.3.0)
	with SMTP id jm393957c60e; Mon, 26 Jun 2000 19:05:24 -0000
From: rsw@ISI.EDU
Reply-To: soft2000ok@netease.com
Subject: Re:480元国际域名注册
To: 朋友6@ISI.EDU
X-Mailer:  V3,1,6,1 (W95/NT) (Build: Oct 18 1999)
Mime-Version: 1.0
Date: Tue, 27 Jun 2000 02:43:48 +0800
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

This message is only introduced for chinese,
if you are foreign ,you may delete it immediately,and i'm sorry for you
此信您若不感兴趣，请立即删除,并在此表示由衷地歉意!
中国民建网推出域名注册特惠价!
480元=国际域名两年+虚拟主机20M两年
并提供独立的CGI-BIN目录,10个域名式电子信箱,格式为
useid@yourdomain.
中国民建网让您以最实惠的价格连入INTERNET.
中国民建网面对国内中小型企业强档推出100M空间上网超值服务
    中国中小型企业近千万，现上网的不到2%，面对中国即将加入WTO，
国际经济一体化格局的变化，势必推动企业上网，用最有效的成本投
入直面新的市场竞争，由此对互联网服务商提出了更多更新的需求。 

    本网站现面向企业上网推出1200元超值服务，
    1200元＝国际域名2年＋100M空间2年＋无限个电子邮箱， 价格极具优势。另提供广告服务：为客户免费添加首页右侧图标、文字链接。网站互动推广、定期为客户发布相关网站信息，400个全球搜索引擎(200元）加驻等多项定制服务。本站是专业性域名网站有庞大的固定客户和点击率。让您的网站花最少的钱得到最大的宣传）
  
　联系办法：电话：0552-2081025 传真：0552-2056294
            E-mail:webmaster3@cndem.net
        中国民建网　　网络发展部   >>>>现在递交 

http://www.cndem.net;
http://www.cndem.com.





From rsvp-owner@ISI.EDU  Tue Jun 27 13:06:21 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18423
	for <rsvp-archive@lists.ietf.org>; Tue, 27 Jun 2000 13:06:20 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id IAA28986
	for rsvp-outgoing; Tue, 27 Jun 2000 08:11:59 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id IAA28980
	for <rsvp@zephyr.isi.edu>; Tue, 27 Jun 2000 08:11:57 -0700 (PDT)
Received: from mail.estg.iplei.pt (mail.estg.iplei.pt [193.137.239.2])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id IAA28625
	for <rsvp@ISI.EDU>; Tue, 27 Jun 2000 08:12:32 -0700 (PDT)
Received: from spock1 ([192.168.5.47])
	by mail.estg.iplei.pt (8.9.0/8.9.0) with SMTP id QAA05905
	for <rsvp@ISI.EDU>; Tue, 27 Jun 2000 16:12:16 +0100
From: "Paulo Loureiro" <loureiro@estg.iplei.pt>
To: <rsvp@ISI.EDU>
Subject: unsuscribe
Date: Tue, 27 Jun 2000 16:11:30 +0100
Message-ID: <NEBBKIJEALEIBGLAPAJLEEHJCAAA.loureiro@estg.iplei.pt>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
In-Reply-To: <395762C2.1AA04784@telin.nl>
Sender: owner-rsvp@ISI.EDU
Precedence: bulk
Content-Transfer-Encoding: 7bit

unsuscribe



From proms@saturn.kt.agh.edu.pl  Tue Jun 27 15:36:03 2000
Received: from uci.agh.edu.pl (root@galaxy.uci.agh.edu.pl [149.156.96.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22728
	for <rsvp-archive@odin.ietf.org>; Tue, 27 Jun 2000 15:36:01 -0400 (EDT)
Received: from saturn.kt.agh.edu.pl (proms@saturn.kt.agh.edu.pl [149.156.114.3])
	by uci.agh.edu.pl (8.9.3/8.8.7/rchk1.20) with SMTP id VAA06477
	for <rsvp-archive@odin.ietf.org>; Tue, 27 Jun 2000 21:35:57 +0200 (MET DST)
Received: by saturn.kt.agh.edu.pl (AIX 3.2/UCB 5.64/5.1)
          for rsvp-archive@odin.ietf.org id AA32119; Tue, 27 Jun 2000 21:35:09 +0200 
Date: Tue, 27 Jun 2000 21:35:09 +0200
From: proms@saturn.kt.agh.edu.pl (Piotr Pacyna)
Message-Id: <10006271935.AA32119@saturn.kt.agh.edu.pl>
Organization: University of Mining and Metallurgy
Address: Mickiewicza 30, 30-059 Krakow, POLAND
To: rsvp-archive@ietf.org
Subject: PROMS2000, deadline extended

Dear Sirs,
Due to numerous requests for deadline extension
we will keep accepting papers until 7th July 2000.

Piotr Pacyna OC Chair

++++++++++++++++++++++++++++++++++++++++++++++++++++++
(We do apologize, if you receive multiple copies of this CfP)

                  PROTOCOLS FOR MULTIMEDIA SYSTEMS - PROMS2000
                            DEADLINE EXTENDED

                       Cracow, Poland, October 22-25, 2000
Sponsored by IEEE Poland Sect. and Cracow Communications Soc. Chap.
Lucent Technologies, ZWUT a Siemens Company,
                         http://PROMS2000.kt.agh.edu.pl/

After past successful PROMS conferences held in Berlin, Salzburg,
Madrid, and Santiago de Chile now we cordially invite you to
Cracow/Poland, a lovely university city, with a 1000 year history, today
one of cultural capitals of Europe.

Emerging broadband interactive applications along with a development of
different networking technologies should draw telecom operators' and
service providers' attention to protocols supporting multimedia systems
as an interface between these two environments that has to be still
investigated and modified.

The PROMS2000 conference is intended to contribute to a scientific,
strategical and practical cooperation between research institutes and
industrial companies in the area of distributed multimedia applications,
protocols, and intelligent management tools, with emphasis on their
provision over broadband networks.

PROMS2000 will cover papers and demonstrations on research and
achievements related to the following topics:

TOPICS
* design and implementation of multimedia protocols for public switched
telephony networks, mobile networks, data networks, and satellite
networks using IP, ATM or other connectivity techniques;
* application, media, and protocol integration: synchronization of media
streams;
* multiparty and group communication protocols;
* mobile networking and routing: multimedia communication architectures
for mobile networks;
* multimedia applications: video-on-demand, digital video libraries,
video games, virtual community, teleworking, teleteaching, e-commerce,
telemeeting, virtual reality simulations;
* content based searching and querying;
* techniques for the specification of communication services required by
multimedia applications;
* methods for real-time testing and analysis of service implementations;
* integration of media storage and communication mechanisms, operating
system and high-performance issues;
* experiences with service provisioning using distributed multimedia
applications, eg. voice over IP;
* performance of protocols, such as TCP, and applications: modeling, simulation and optimization in different networks;
* definition, provisioning, and supervision of QoS parameters for
networked applications and services, eg. in IntServ/DiffServ networks;
* multimedia traffic engineering;
* applications and platforms for service management and provisioning;
* intelligent management tools pertaining to costs and quality of
service, network access, accounting, security, and system resilience;
* service access - security, authentication, privacy;
* accounting and tariff policing for multimedia teleservices.

IMPORTANT DATES
* Full papers due                     July 7, 2000
* Authors notified                    July 24, 2000
* Full paper camera ready due         September 25, 2000

CONFERENCE TIMETABLE
* 1st day       October 22      full-day sightseeing tour (optional)
* 2nd day       October 23      tutorials, welcome reception
* 3rd day       October 24      invited talks, sessions, panel, banquet
* 4th day       October 25      invited talks, sessions

VENUE
Its history rooted deep in the Middle Ages, Cracow, is the most
celebrated city in Poland. UNESCO has added its architectural complex to
the World Heritage List. Cracow's appeal today, however, is no longer
attributable solely to the beauty of its medieval architecture, but to
its strong scientific potential for applied research and development.

The PROMS2000 Conference will be held on the modern premises of the
Department of Telecommunications within walking distance of both the
downtown area and hotels. Direct flights to Cracow are available to and
from Chicago, Copenhagen, New York, Toronto, Frankfurt, London, Paris,
Rome, Tel Aviv, Vienna and Zurich.

SUBMISSION
Submit a full manuscript to the PROMS chair in an electronic form
(MSWord, Postscript or pdf file); editorial requirements can be found at
http://PROMS2000.kt.agh.edu.pl/.

PROCEEDINGS
1. Each participant will receive Proceedings from the conference.
2. Two best papers will be considered for publication in the IEEE Communications
   Magazine (March 2001 issue) in a feature topic "Protocols for Multimedia
   Systems".

CONFERENCE CHAIR
Zdzislaw PAPIR
Department of Telecommunications
University of Mining and Metallurgy
Al. Mickiewicza 30
30-059 Cracow, Poland
E-mail: papir@kt.agh.edu.pl
Phone: +48 12 634 55 82
Fax: +48 12 634 23 72

PROGRAM COMMITTEE
Koichi Asatani, Univ. Kogakuin, asatani@sin.cc.kogakuin.ac.jp
William Atwood, Univ. Concordia, Bill@cs.Concordia.ca
Arturo Azcorra, Univ. Carlos III de Madrid, azcorra@it.uc3m.es
Stanislaw Budkowski, INT-Evry, stan@int-evry.fr
Andrew Campbell, Univ. Columbia, campbell@ctr.columbia.edu
Michel Diaz, LAAS-CNRS, diaz@laas.fr
Wolfgang Effelsberg, Univ. Mannheim,
effelsberg@informatik.uni-mannheim.de
Paolo Fasano, CSELT, Paolo.Fasano@cselt.it
Francisco Fontes, Portugal Telecom, fontes@ptinovacao.pt
Nicolas D. Georganas, Univ. Ottawa, georgana@mcrlab.uottawa.ca
Per Gunningberg, Univ. Uppsala, Per.Gunningberg@docs.uu.se
Ibrahim Habib, Univ. New York
Ulrich Hofmann, Univ. Salzburg, ulrich.hofmann@fh-sbg.ac.at
David Hutchison, Univ. Lancaster, dh@comp.lancs.ac.uk
Yuji Inoue, NTT, yuji@rd.nttdata.co.jp
Andrzej Jajszczyk, Univ. Mining and Metallurgy, jajszcz@kt.agh.edu.pl
Pedro Lizcano, Telefonica Labs, lizcano@tid.es
John C. S. Lui, Chinese Univ. Hong Kong, cslui@cse.cuhk.edu.hk
Andrzej R. Pach, Univ. Mining & Metallurgy, pach@kt.agh.edu.pl
Sergio Palazzo, Univ. Catania, palazzo@iit.unict.it
Thomas Plagemann, Center for Technology, plageman@unik.no
Radia Perlman, SUN, radia.perlman@sun.com
Radu Popescu-Zeletin, GMD, zeletin@fokus.gmd.de
Marten J. van Sinderen, Univ. Twente, sinderen@cs.utwente.nl
Kazem Sohraby, Lucent, sohraby@lucent.com
Joan I. Solana, Nokia Telecom R & D, juan.solana@nokia.com
Eduardo Vera, Univ. of Chile, evera@accessnova.cl
Johan Zuidweg, Tecsidel, johan.zuidweg@ieee.org

ORGANISING COMMITTEE
Chair: Piotr PACYNA, proms@kt.agh.edu.pl
K. Juszkiewicz, juszkiew@kt.agh.edu.pl
J. Gozdecki, gozdecki@kt.agh.edu.pl
J. Roman, roman@kt.agh.edu.pl


From rsvp-owner@ISI.EDU  Tue Jun 27 20:35:01 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27784
	for <rsvp-archive@lists.ietf.org>; Tue, 27 Jun 2000 20:35:00 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id PAA09323
	for rsvp-outgoing; Tue, 27 Jun 2000 15:49:18 -0700 (PDT)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id PAA09317
	for <rsvp@zephyr.isi.edu>; Tue, 27 Jun 2000 15:49:17 -0700 (PDT)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id PAA29636;
	Tue, 27 Jun 2000 15:50:03 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id WAA03795;
	Tue, 27 Jun 2000 22:50:03 GMT
Date: Tue, 27 Jun 2000 22:50:03 GMT
Message-Id: <200006272250.WAA03795@gra.isi.edu>
To: rsvp@ISI.EDU, atteln@uni-paderborn.de
Subject: Re: TSpec Sum
X-Sun-Charset: US-ASCII
Sender: owner-rsvp@ISI.EDU
Precedence: bulk


  *> From rsvp-owner@ISI.EDU Fri Jun 23 04:00:08 2000
  *> Date:   Fri, 23 Jun 2000 12:47:06 +0200
  *> From: Simon Schneider <atteln@uni-paderborn.de>
  *> X-Mailer: Mozilla 4.72 [en] (WinNT; U)
  *> X-Accept-Language: en
  *> MIME-Version: 1.0
  *> To: rsvp@ISI.EDU
  *> Subject: TSpec Sum
  *> Content-Transfer-Encoding: 7bit
  *> Sender: owner-rsvp@ISI.EDU
  *> Precedence: bulk
  *> X-Lines: 15
  *> 
  *> Hi,
  *> to do some analysis, I need to sum up sender TSpecs of multiple streams.
  *> Is it correct if I use
  *> 
  *> - the sum of the rate values
  *> - the sum of the burst values
  *> - the sum of the peak values (or infinity)
  *> - the max of the M's
  *> - the min of the m's
  *> 
  *> ?
  *> 
  *> Thanks for help,
  *> cheers, Simon
  *> 
  *> 
Please see RFC2212, the section "Ordering and Merging".

Bob Braden


From rsvp-owner@ISI.EDU  Wed Jun 28 09:29:17 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22411
	for <rsvp-archive@lists.ietf.org>; Wed, 28 Jun 2000 09:29:17 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id EAA16960
	for rsvp-outgoing; Wed, 28 Jun 2000 04:30:12 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id EAA16955
	for <rsvp@zephyr.isi.edu>; Wed, 28 Jun 2000 04:30:10 -0700 (PDT)
Received: from griffin.host4u.net (griffin.host4u.net [209.150.128.163])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id EAA09543
	for <rsvp@ISI.EDU>; Wed, 28 Jun 2000 04:30:53 -0700 (PDT)
Received: from nfloat.labn.net (labn.net [209.204.240.82])
	by griffin.host4u.net (8.8.5/8.8.5) with ESMTP id GAA08530;
	Wed, 28 Jun 2000 06:30:35 -0500
Message-Id: <4.3.2.7.2.20000627205125.00b8ae10@mail.labn.net>
X-Sender: lberger@mail.labn.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 27 Jun 2000 20:52:52 -0400
To: Rohit Chhapolia <rohit@globespan.net>
From: Lou Berger <lberger@labn.net>
Subject: Re: operation subobject
Cc: Rahul Aggarwal <rahul@redback.com>, rsvp@ISI.EDU
In-Reply-To: <39575B68.AEC525E@globespan.net>
References: <20000624150301.C20798@malt.redback.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

I believe this is correct.

Lou

At 09:32 AM 6/26/00 -0400, Rohit Chhapolia wrote:
>Rahul,
>
>There used to be an operational sub-object in the previous
>versions of this draft which has been removed after much
>discussion on the mailing list and the conclusion that it
>is not being used. The text in these sections has not been
>updated accordingly. I guess it will get updated in the next
>version.
>
>Rohit
>
>Rahul Aggarwal wrote:
> >
> > Lou et al.,
> > draft-ietf-mpls-lsp-tunnel-05.txt says: (4.3.2)
> >
> > " The explicit route is encoded as a series of subobjects contained in
> >    an EXPLICIT_ROUTE object.  Each subobject may identify a group of
> >    nodes in the explicit route or may specify an operation to be
> >    performed along the path."
> >
> > The 'operation subobject' is also mentioned a few times in the section on
> > processing of the explicit route object (4.3.4). Eg:
> >
> >  "If the first subobject is an
> >    operation subobject, the message is in error and the system SHOULD
> >    return a "Bad EXPLICIT_ROUTE object" error"
> >
> > I have not been able to find encodings etc of the operation subobject. No
> > value has been assigned for an operation subobject in the type field of
> > an ERO subobject. Are the details of this object a matter of local policy?
> >
> > I will appreciate it if you could shed some light on the usage, 
> definition and
> > format of the operation subobject.
> >
> > Thanks,
> > rahul
>
>--
>Rohit Chhapolia
>Globespan, Inc.
>mailto:rohit@globespan.net
>http://www.globespan.net



From rsvp-owner@ISI.EDU  Wed Jun 28 19:16:48 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06318
	for <rsvp-archive@lists.ietf.org>; Wed, 28 Jun 2000 19:16:48 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id OAA14924
	for rsvp-outgoing; Wed, 28 Jun 2000 14:22:24 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id OAA14919
	for <rsvp@zephyr.isi.edu>; Wed, 28 Jun 2000 14:22:23 -0700 (PDT)
Received: from postal.redback.com (postal.redback.com [155.53.12.9])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id OAA06539
	for <rsvp@isi.edu>; Wed, 28 Jun 2000 14:23:07 -0700 (PDT)
Received: from malt.redback.com (malt.redback.com [155.53.12.41])
	by postal.redback.com (Postfix) with ESMTP
	id 711C72AA32; Wed, 28 Jun 2000 14:22:34 -0700 (PDT)
Received: (from rahul@localhost)
	by malt.redback.com (8.9.3-LCCHA/8.9.3/null redback solaris client) id OAA02353;
	Wed, 28 Jun 2000 14:21:47 -0700 (PDT)
Date: Wed, 28 Jun 2000 14:21:46 -0700
From: Rahul Aggarwal <rahul@redback.com>
To: lberger@labn.net, rsvp@ISI.EDU
Cc: Rahul Aggarwal <rahul@redback.com>
Subject: Srefresh messages..
Message-ID: <20000628142146.J24613@malt.redback.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

Lou et al.,
I have a question regarding draft-rsvp-refresh-reduct-05.txt:

Section 5.3 on Srefresh Message Usage, page 27 :

 "The secondary method for identifying which Path state may be.........
   .............................. When the outgoing
   interface is a point-to-point link, all Path state associated with
   sessions advertised out the interface SHOULD be included in the same
   Srefresh message.  When the outgoing interface is not a point-to-
   point link, all unicast session Path state SHOULD be included in the
   same Srefresh message. "

I am wondering why all the Path state in the above two cases, should be included
in the same Srefresh message? Different Path messages may be 
scheduled for refresh at different times. It may be possible to refresh
some of these in the same Srefresh. However depending on the implementation, 
some others may be sent in a different Srefresh at a different time. 

Maybe I am mis-interpreting the above text. Will appreciate your comments
on this.

thanks,
rahul
 






From rsvp-owner@ISI.EDU  Wed Jun 28 20:44:39 2000
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06891
	for <rsvp-archive@lists.ietf.org>; Wed, 28 Jun 2000 20:44:39 -0400 (EDT)
Received: by zephyr.isi.edu (8.9.3/8.9.3) id PAA21015
	for rsvp-outgoing; Wed, 28 Jun 2000 15:56:29 -0700 (PDT)
Received: from venera.isi.edu (venera.isi.edu [128.9.176.32])
	by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id PAA21009
	for <rsvp@zephyr.isi.edu>; Wed, 28 Jun 2000 15:56:27 -0700 (PDT)
Received: from postal.redback.com (postal.redback.com [155.53.12.9])
	by venera.isi.edu (8.9.3/8.9.3) with ESMTP id PAA11074
	for <rsvp@ISI.EDU>; Wed, 28 Jun 2000 15:57:11 -0700 (PDT)
Received: from malt.redback.com (malt.redback.com [155.53.12.41])
	by postal.redback.com (Postfix) with ESMTP id 2CB802AA36
	for <rsvp@ISI.EDU>; Wed, 28 Jun 2000 15:56:46 -0700 (PDT)
Received: (from rahul@localhost)
	by malt.redback.com (8.9.3-LCCHA/8.9.3/null redback solaris client) id PAA04457
	for rsvp@ISI.EDU; Wed, 28 Jun 2000 15:55:57 -0700 (PDT)
Date: Wed, 28 Jun 2000 15:55:57 -0700
From: Rahul Aggarwal <rahul@redback.com>
To: rsvp@ISI.EDU
Subject: Srefresh messages..
Message-ID: <20000628155557.M24613@malt.redback.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
Sender: owner-rsvp@ISI.EDU
Precedence: bulk

Lou et al.,
I have a question regarding draft-rsvp-refresh-reduct-05.txt:

Section 5.3 on Srefresh Message Usage, page 27 :

 "The secondary method for identifying which Path state may be.........
   .............................. When the outgoing
   interface is a point-to-point link, all Path state associated with
   sessions advertised out the interface SHOULD be included in the same
   Srefresh message.  When the outgoing interface is not a point-to-
   point link, all unicast session Path state SHOULD be included in the
   same Srefresh message. "

I am wondering why all the Path state in the above two cases, should be included
in the same Srefresh message? Different Path messages may be 
scheduled for refresh at different times. It may be possible to refresh
some of these in the same Srefresh. However depending on the implementation, 
some others may be sent in a different Srefresh at a different time. 

Maybe I am mis-interpreting the above text. Will appreciate your comments
on this.

thanks,
rahul