RE: [NSIS] Proposed NSIS charter
"Chaskar Hemant (NRC/Boston)" <Hemant.Chaskar@nokia.com> Tue, 30 October 2001 15:19 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03709 for <nsis-archive@odin.ietf.org>; Tue, 30 Oct 2001 10:19:40 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id KAA04831 for nsis-archive@odin.ietf.org; Tue, 30 Oct 2001 10:19:41 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04821; Tue, 30 Oct 2001 10:19:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04786 for <nsis@optimus.ietf.org>; Tue, 30 Oct 2001 10:19:24 -0500 (EST)
Received: from mgw-dax2.ext.nokia.com (mgw-dax2.ext.nokia.com [63.78.179.217]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03698 for <nsis@ietf.org>; Tue, 30 Oct 2001 10:19:18 -0500 (EST)
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87]) by mgw-dax2.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f9UFJuQ24838 for <nsis@ietf.org>; Tue, 30 Oct 2001 09:19:56 -0600 (CST)
Received: from daebh001.NOE.Nokia.com (unverified) by davir04nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id <T56e9508f43ac12f257079@davir04nok.americas.nokia.com>; Tue, 30 Oct 2001 09:19:18 -0600
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966); Tue, 30 Oct 2001 09:19:17 -0600
content-class: urn:content-classes:message
Subject: RE: [NSIS] Proposed NSIS charter
Date: Tue, 30 Oct 2001 10:19:21 -0500
Message-ID: <E320A8529CF07E4C967ECC2F380B0CF90890E9@bsebe001.NOE.Nokia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Thread-Topic: [NSIS] Proposed NSIS charter
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Thread-Index: AcFhUhbZOwOx6M1FEdWBTgBQi2X+DwAAYIdQ
From: "Chaskar Hemant (NRC/Boston)" <Hemant.Chaskar@nokia.com>
To: nsis@ietf.org
Cc: "Loughney John (NRC/Helsinki)" <john.loughney@nokia.com>, fu@ee.tu-berlin.de
X-OriginalArrivalTime: 30 Oct 2001 15:19:17.0973 (UTC) FILETIME=[3E150050:01C16156]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id KAA04787
Sender: nsis-admin@ietf.org
Errors-To: nsis-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Next Steps in Signaling <nsis.ietf.org>
X-BeenThere: nsis@ietf.org
Content-Transfer-Encoding: 8bit
Hi: > Hi John, > > > 1) I didn't quite understand, whether the WG would define a new > > > signalling protocol or not? Would, for example, an enhancement / > > > modification to RSVP be considered in or out of scope? > > > The intention is not to define a new protocol, but to enhance or > > modify an existing one, such as RSVP. > Could this "existing one" be interpreted as "approaches which have been > already presented (perhaps under development)"? [HC] I was thinking as to what modifications to RSVP can actually be done. For that, it may be worthwhile to look at some core RSVP characteristics. There are as follows: 1. One pass with advertisement approach, 2. A way to define packet filter based on source and dest IP addresses and port numbers, 3. A way to define flow's traffic characteristics via RSVP Flowspecs. 4. Use of explicit refresh messages. Now modifying RSVP might account to 1. Allowing for forward reservations. 2. Expanding the scope of defining packet filters by inclusion of additional parameters + some optimizations based on IPv6 flow label. For example, IPv6 flow label can be used to identify the flow in the router. This will get rid of problems with chaning CoA in Mobile IP. 3. In addition to using RSVP Flowspecs to describe nitty gritty details of flow, provide an option for describing some simple QoS requirement, for example, QoS class and average rate. 4. Arrival of flow's data packet at the router can be used as an indication of live connection. This will avoid reliance on explicit refresh messages. Are there any other core modifications to RSVP that we can think of. May be we can create a list of possible modifications, evaluate their need and elaborate on those which will be agreed upon by the WG. That way, we can get the task of RSVP modifications completed quickly. > > > 2) If the goals include some sort of new QoS signalling, would > > > that include eg. bandwidth broker functionality, if needed, or just a > > > signalling mechanism? So, more entities concerned by the > > > signalling than just routers and end hosts? > > > > One goal is to define the architecture. This may include signaling > > to a proxy or to a bandwidth broker. > Do we have any "proxy" or "bandwidth broker" in existing protocols? IMO the > answer depends on my previous question. > > > 3) Would the signalling be limited to a separate QoS signalling > > > protocol, or could the QoS signalling be part data packets, > > > so be in-band, as the DSCP in DiffServ or the INSIGNIA scheme. A > > > new IPv6 extension header for QoS? > > > > I think those could be possibilities. One could (though I won't) > > make a point that one result would be to create a use for the IPv6 > > flow label. > Fine with me. However I think taking advantage of IPv6 extension header option, > would be beneficial compared with only an IPv6 flow label since it can carry > more information. In fact the ID > www.ietf.org/internet-drafts/draft-ietf-mobileip-qos-requirements-01.txt > did present such an approach. [HC] I think Xiaoming meant http://ietf.org/internet-drafts/draft-chaskar-mobileip-qos-01.txt. Thanks. Hemant > Thanks > Xiaoming _______________________________________________ nsis mailing list nsis@ietf.org http://www1.ietf.org/mailman/listinfo/nsis _______________________________________________ nsis mailing list nsis@ietf.org http://www1.ietf.org/mailman/listinfo/nsis
- [NSIS] Proposed NSIS charter john.loughney
- Re: [NSIS] Proposed NSIS charter Jukka Manner
- RE: [NSIS] Proposed NSIS charter john.loughney
- RE: [NSIS] Proposed NSIS charter Kappler Cornelia
- RE: [NSIS] Proposed NSIS charter Chen, Weijing
- RE: [NSIS] Proposed NSIS charter john.loughney
- Re: [NSIS] Proposed NSIS charter Xiaoming Fu
- RE: [NSIS] Proposed NSIS charter Chaskar Hemant (NRC/Boston)
- Re: [NSIS] Proposed NSIS charter Xiaoming Fu
- RE: [NSIS] Proposed NSIS charter Georgios Karagiannis (ELN)
- RE: [NSIS] Proposed NSIS charter Zheng Haihong (NRC/Dallas)
- RE: [NSIS] Proposed NSIS charter john.loughney
- RE: [NSIS] Proposed NSIS charter Georgios Karagiannis (ELN)
- RE: [NSIS] Proposed NSIS charter john.loughney
- RE: [NSIS] Proposed NSIS charter Scott Bradner
- RE: [NSIS] Proposed NSIS charter Chen, Weijing
- RE: [NSIS] Proposed NSIS charter jussi.ruutu
- RE: [NSIS] Proposed NSIS charter Jukka Manner
- RE: [NSIS] Proposed NSIS charter john.loughney
- RE: [NSIS] Proposed NSIS charter john.loughney
- RE: [NSIS] Proposed NSIS charter Georgios Karagiannis (ELN)
- [NSIS] Initial ID on Signalling Requirements Jukka Manner
- [NSIS] Initial ID on Signalling Requirements Jukka Manner
- RE: [NSIS] Proposed NSIS charter jussi.ruutu
- RE: [NSIS] Proposed NSIS charter Georgios Karagiannis (ELN)
- RE: [NSIS] Proposed NSIS charter Chen, Weijing
- Re: [NSIS] Proposed NSIS charter Brian Williams
- RE: [NSIS] Proposed NSIS charter Georgios Karagiannis (ELN)
- RE: [NSIS] Proposed NSIS charter Georgios Karagiannis (ELN)
- RE: [NSIS] Proposed NSIS charter john.loughney
- RE: [NSIS] Proposed NSIS charter john.loughney
- RE: [NSIS] Proposed NSIS charter jussi.ruutu
- RE: [NSIS] Proposed NSIS charter john.loughney
- RE: [NSIS] Proposed NSIS charter Georgios Karagiannis (ELN)
- RE: [NSIS] Proposed NSIS charter john.loughney
- RE: [NSIS] Proposed NSIS charter Georgios Karagiannis (ELN)
- RE: [NSIS] Proposed NSIS charter Georgios Karagiannis (ELN)
- RE: [NSIS] Proposed NSIS charter john.loughney
- RE: [NSIS] Proposed NSIS charter Georgios Karagiannis (ELN)
- RE: [NSIS] Proposed NSIS charter Georgios Karagiannis (ELN)