From nsis-admin@ietf.org  Mon Oct 22 04:02:57 2001
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 EAA08708
	for <nsis-archive@odin.ietf.org>; Mon, 22 Oct 2001 04:02:56 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA12993;
	Mon, 22 Oct 2001 04:02:55 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA12963
	for <nsis@ns.ietf.org>; Mon, 22 Oct 2001 04:02:54 -0400 (EDT)
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08705
	for <nsis@ietf.org>; Mon, 22 Oct 2001 04:02:50 -0400 (EDT)
From: john.loughney@nokia.com
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f9M83Tf21382
	for <nsis@ietf.org>; Mon, 22 Oct 2001 11:03:29 +0300 (EET DST)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T56c07c83dcac158f24077@esvir04nok.ntc.nokia.com>;
 Mon, 22 Oct 2001 11:02:53 +0300
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <V2YXBM79>; Mon, 22 Oct 2001 11:02:30 +0300
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF5D8E69@esebe004.NOE.Nokia.com>
To: nsis@ietf.org
Cc: sob@harvard.edu, mankin@isi.edu
Date: Mon, 22 Oct 2001 11:02:25 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [NSIS] Proposed NSIS charter
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

Hi all,

I have been exchanging some emails with the Transport Area Directors about a
proposed Working Group charter.  This is what I have come up with.  I'd
appreciate feedback on this.  

thanks,
John Loughney


Next Steps in Signaling

Quite a bit of work has been done on Quality of Service and resource
reservation for the Internet.  For a number reasons, however, QoS has been
primarily limited to best effort service.  

There are concerns about existing QoS solutions - scalability and simplicity
being primary concerns. Additionally, interworking between different QoS
solutions is problematic. Mobility and next-generation wireless networks
complicate this. This creates a need for a simplified solution of signaling
QoS, one that reuses parts of existing methods.  

This work group will work on the requirements, architecture and protocols
for signaling QoS. The working group will use existing IETF signaling
protocols as the basis for this work.  Additionally, this work group will
consider a simplified set of QoS parameters for use with the signaling
protocols.  As input to the working group, the Mobile IP QoS Requirements
document (draft-mobileip-qos-requirements) will be considered by the working
group.

Resource allocation mechanisms are out of scope for this working group, as
resource allocation is a network administrative concern.  This work group
will focus on providing (QoS) signaling functioning to a local access
network and end-to-end signaling.  It is not the intention of this working
group to invent new signaling protocols.  Additionally, mobility protocols
and AAA work is out of scope of the working group.  The work produced in
this Work Group should work with existing IETF mobility and AAA protocols.

This work group will provide the framework for interworking with existing
resource allocation methods.  It is a non-goal of the working group to
develop new resource allocation protocols.  

Goals and Milestones:
=====================

Dec 01	Initial ID on Analysis of existing signaling protocols

Dec 01	Initial ID on Signaling Requirements

Mar 02  	Initial ID on Framework signaling architecture

Mar 02	Initial ID on Simplified QoS parameters / datatypes

Jul 02  	Submit 'Analysis of existing signaling protocols' to IESG
for publication as an Information RFC.

Jul 02  	Submit 'Signaling Requirements' to IESG for publication as
an Information RFC.

Jul 02	Initial ID on Comparison of signaling protocol candidates

Sep 02	Initial Standards track ID on QoS signaling protocol

Sep 02  	Submit 'Framework signaling architecture' to IESG for
publication as an Information RFC.

Dec 02  	Submit 'Simplified QoS parameters / datatypes' to IESG for
publication as an Information RFC.

Mar 03  	Submit 'QoS signaling protocol' to IESG for publication as a
standards track RFC.

_______________________________________________
nsis mailing list
nsis@ietf.org
http://www1.ietf.org/mailman/listinfo/nsis


From nsis-admin@ietf.org  Wed Oct 24 06:23:33 2001
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 GAA20275
	for <nsis-archive@odin.ietf.org>; Wed, 24 Oct 2001 06:23:28 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA20544;
	Wed, 24 Oct 2001 06:23:25 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA20522
	for <nsis@optimus.ietf.org>; Wed, 24 Oct 2001 06:23:24 -0400 (EDT)
Received: from porsta.cs.Helsinki.FI (porsta.cs.Helsinki.FI [128.214.48.124])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20272
	for <nsis@ietf.org>; Wed, 24 Oct 2001 06:23:23 -0400 (EDT)
Received: from puuluoto.cs.Helsinki.FI (IDENT:jmanner@puuluoto.cs.Helsinki.FI [128.214.9.198])
	by porsta.cs.Helsinki.FI (8.11.6/8.11.6) with ESMTP id f9OANMk17833;
	Wed, 24 Oct 2001 13:23:24 +0300
Date: Wed, 24 Oct 2001 13:23:16 +0300 (EEST)
From: Jukka Manner <jmanner@cs.Helsinki.FI>
To: john.loughney@nokia.com
cc: nsis@ietf.org
Subject: Re: [NSIS] Proposed NSIS charter
In-Reply-To: <0C1353ABB1DEB74DB067ADFF749C4EEF5D8E69@esebe004.NOE.Nokia.com>
Message-ID: <Pine.LNX.4.40.0110241303070.10009-100000@puuluoto.cs.Helsinki.FI>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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


	Hi,

	The charter sounds pretty good, although a few thoughts came to my
mind while reading it:

	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?

	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?

	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?

	4) The text talks about mobility considerations to QoS? Is that
the primary goal or would the QoS signalling question be as important to
solve in fixed networks and especially in ad hoc networks?

	Just some thoughts,

	Jukka Manner

On Mon, 22 Oct 2001 john.loughney@nokia.com wrote:

> Hi all,
>
> I have been exchanging some emails with the Transport Area Directors about a
> proposed Working Group charter.  This is what I have come up with.  I'd
> appreciate feedback on this.
>
> thanks,
> John Loughney
>
>
> Next Steps in Signaling
>
> Quite a bit of work has been done on Quality of Service and resource
> reservation for the Internet.  For a number reasons, however, QoS has been
> primarily limited to best effort service.
>
> There are concerns about existing QoS solutions - scalability and simplicity
> being primary concerns. Additionally, interworking between different QoS
> solutions is problematic. Mobility and next-generation wireless networks
> complicate this. This creates a need for a simplified solution of signaling
> QoS, one that reuses parts of existing methods.
>
> This work group will work on the requirements, architecture and protocols
> for signaling QoS. The working group will use existing IETF signaling
> protocols as the basis for this work.  Additionally, this work group will
> consider a simplified set of QoS parameters for use with the signaling
> protocols.  As input to the working group, the Mobile IP QoS Requirements
> document (draft-mobileip-qos-requirements) will be considered by the working
> group.
>
> Resource allocation mechanisms are out of scope for this working group, as
> resource allocation is a network administrative concern.  This work group
> will focus on providing (QoS) signaling functioning to a local access
> network and end-to-end signaling.  It is not the intention of this working
> group to invent new signaling protocols.  Additionally, mobility protocols
> and AAA work is out of scope of the working group.  The work produced in
> this Work Group should work with existing IETF mobility and AAA protocols.
>
> This work group will provide the framework for interworking with existing
> resource allocation methods.  It is a non-goal of the working group to
> develop new resource allocation protocols.
>
> Goals and Milestones:
> =====================
>
> Dec 01	Initial ID on Analysis of existing signaling protocols
>
> Dec 01	Initial ID on Signaling Requirements
>
> Mar 02  	Initial ID on Framework signaling architecture
>
> Mar 02	Initial ID on Simplified QoS parameters / datatypes
>
> Jul 02  	Submit 'Analysis of existing signaling protocols' to IESG
> for publication as an Information RFC.
>
> Jul 02  	Submit 'Signaling Requirements' to IESG for publication as
> an Information RFC.
>
> Jul 02	Initial ID on Comparison of signaling protocol candidates
>
> Sep 02	Initial Standards track ID on QoS signaling protocol
>
> Sep 02  	Submit 'Framework signaling architecture' to IESG for
> publication as an Information RFC.
>
> Dec 02  	Submit 'Simplified QoS parameters / datatypes' to IESG for
> publication as an Information RFC.
>
> Mar 03  	Submit 'QoS signaling protocol' to IESG for publication as a
> standards track RFC.
>
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Thu Oct 25 05:00:08 2001
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 FAA11979
	for <nsis-archive@odin.ietf.org>; Thu, 25 Oct 2001 05:00:08 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA26417
	for nsis-archive@odin.ietf.org; Thu, 25 Oct 2001 05:00:13 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA26391;
	Thu, 25 Oct 2001 05:00:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA26371
	for <nsis@optimus.ietf.org>; Thu, 25 Oct 2001 05:00:09 -0400 (EDT)
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11975
	for <nsis@ietf.org>; Thu, 25 Oct 2001 05:00:03 -0400 (EDT)
From: john.loughney@nokia.com
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f9P90iA18395
	for <nsis@ietf.org>; Thu, 25 Oct 2001 12:00:44 +0300 (EET DST)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T56d023fa46ac158f231f3@esvir03nok.nokia.com>;
 Thu, 25 Oct 2001 12:00:06 +0300
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <VPYV307A>; Thu, 25 Oct 2001 12:00:06 +0300
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF09BBDE@esebe004.NOE.Nokia.com>
To: jmanner@cs.Helsinki.FI
Cc: nsis@ietf.org
Subject: RE: [NSIS] Proposed NSIS charter
Date: Thu, 25 Oct 2001 11:59:55 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Hi Jukka,

> 	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.
 
> 	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.

> 	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.

> 	4) The text talks about mobility considerations to QoS? Is that
> the primary goal or would the QoS signalling question be as 
> important to solve in fixed networks and especially in ad hoc 
> networks?

I would not say it is the primary goal, but mobility & roaming do
present challenges to existing QoS Signaling Mechanisms, therefore
I do think that the output of the group will be useful to fixed
networks as well as ad-hoc networks.

cheers,
John

_______________________________________________
nsis mailing list
nsis@ietf.org
http://www1.ietf.org/mailman/listinfo/nsis



From daemon@optimus.ietf.org  Thu Oct 25 05:14:27 2001
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 FAA12127
	for <nsis-archive@odin.ietf.org>; Thu, 25 Oct 2001 05:14:27 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA27141
	for nsis-archive@odin.ietf.org; Thu, 25 Oct 2001 05:14:32 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA27132;
	Thu, 25 Oct 2001 05:14:30 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA27097
	for <nsis@optimus.ietf.org>; Thu, 25 Oct 2001 05:14:28 -0400 (EDT)
Received: from beamer.mchh.siemens.de (beamer.mchh.siemens.de [194.138.158.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12121
	for <nsis@ietf.org>; Thu, 25 Oct 2001 05:14:22 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id LAA22861;
	Thu, 25 Oct 2001 11:14:26 +0200 (MET DST)
Received: from mchh273e.demchh201e.icn.siemens.de ([139.21.200.83])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id LAA03185;
	Thu, 25 Oct 2001 11:14:26 +0200 (MET DST)
Received: by MCHH273E with Internet Mail Service (5.5.2653.19)
	id <VRM9775D>; Thu, 25 Oct 2001 11:14:25 +0200
Message-ID: <4D486782CA36D4118A530000D11EA42A0126532D@blns204e.bln.icn.siemens.de>
From: Kappler Cornelia <Cornelia.Kappler@icn.siemens.de>
To: "'john.loughney@nokia.com'" <john.loughney@nokia.com>, nsis@ietf.org
Subject: RE: [NSIS] Proposed NSIS charter
Date: Thu, 25 Oct 2001 11:14:22 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
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


Hi John, 

	Jukka wrote:
> > 	4) The text talks about mobility considerations to QoS? Is that
> > the primary goal or would the QoS signalling question be as 
> > important to solve in fixed networks and especially in ad hoc 
> > networks?
> 
	John wrote:
> I would not say it is the primary goal, but mobility & roaming do
> present challenges to existing QoS Signaling Mechanisms, therefore
> I do think that the output of the group will be useful to fixed
> networks as well as ad-hoc networks.
> 
	Could you put this more concretely? Does the charter imply the resulting QoS signaling protocol would be designed such that it can easily (be extended to) inter-work with mobility?

	Thanks, Cornelia Kappler



_______________________________________________
nsis mailing list
nsis@ietf.org
http://www1.ietf.org/mailman/listinfo/nsis



From daemon@ns.ietf.org  Thu Oct 25 20:35:09 2001
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 UAA03296
	for <nsis-archive@odin.ietf.org>; Thu, 25 Oct 2001 20:35:07 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA25592
	for nsis-archive@odin.ietf.org; Thu, 25 Oct 2001 20:35:12 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA25583;
	Thu, 25 Oct 2001 20:35:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA25548
	for <nsis@ns.ietf.org>; Thu, 25 Oct 2001 20:35:05 -0400 (EDT)
Received: from howler.tri.sbc.com (howler.tri.sbc.com [205.173.58.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03274
	for <nsis@ietf.org>; Thu, 25 Oct 2001 20:34:47 -0400 (EDT)
Received: from sbctri.tri.sbc.com (sbctri [144.60.1.10])
	by howler.tri.sbc.com (8.11.0/8.11.0) with ESMTP id f9Q0Z7T05047;
	Thu, 25 Oct 2001 19:35:07 -0500 (CDT)
Received: from TRIMAIL2.tri.sbc.com (localhost [127.0.0.1])
	by sbctri.tri.sbc.com (8.11.0/8.9.3) with ESMTP id f9Q0X0P18036;
	Thu, 25 Oct 2001 19:33:16 -0500 (CDT)
Received: by TRIMAIL2.tri.sbc.com with Internet Mail Service (5.5.2653.19)
	id <VSSK9P61>; Thu, 25 Oct 2001 19:33:16 -0500
Message-ID: <905A1C4ABF353F4C8CC16FA9F53DD0D632238F@TRIMAIL2.tri.sbc.com>
From: "Chen, Weijing" <wchen@tri.sbc.com>
To: "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        jmanner@cs.helsinki.fi
Cc: nsis@ietf.org
Subject: RE: [NSIS] Proposed NSIS charter
Date: Thu, 25 Oct 2001 19:33:16 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Does it also include wireline beside wireless? e.g. Ethernet, DSL, etc
network.

Weijing Chen
SBC

 -----Original Message-----
From: 	john.loughney@nokia.com [mailto:john.loughney@nokia.com] 
Sent:	Thursday, October 25, 2001 4:00 AM
To:	jmanner@cs.helsinki.fi
Cc:	nsis@ietf.org
Subject:	RE: [NSIS] Proposed NSIS charter

Hi Jukka,

> 	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.
 
> 	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.

> 	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.

> 	4) The text talks about mobility considerations to QoS? Is that
> the primary goal or would the QoS signalling question be as 
> important to solve in fixed networks and especially in ad hoc 
> networks?

I would not say it is the primary goal, but mobility & roaming do
present challenges to existing QoS Signaling Mechanisms, therefore
I do think that the output of the group will be useful to fixed
networks as well as ad-hoc networks.

cheers,
John

_______________________________________________
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



From daemon@ns.ietf.org  Fri Oct 26 02:11:20 2001
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 CAA20881
	for <nsis-archive@odin.ietf.org>; Fri, 26 Oct 2001 02:11:20 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA11738
	for nsis-archive@odin.ietf.org; Fri, 26 Oct 2001 02:11:21 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA11723;
	Fri, 26 Oct 2001 02:11:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA11680
	for <nsis@ns.ietf.org>; Fri, 26 Oct 2001 02:11:15 -0400 (EDT)
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20868
	for <nsis@ietf.org>; Fri, 26 Oct 2001 02:11:13 -0400 (EDT)
From: john.loughney@nokia.com
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f9Q6BoA18083
	for <nsis@ietf.org>; Fri, 26 Oct 2001 09:11:50 +0300 (EET DST)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T56d4afb835ac158f24077@esvir04nok.ntc.nokia.com>;
 Fri, 26 Oct 2001 09:11:13 +0300
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <VPYVP5LX>; Fri, 26 Oct 2001 09:11:13 +0300
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF5D8EDF@esebe004.NOE.Nokia.com>
To: wchen@tri.sbc.com, jmanner@cs.helsinki.fi
Cc: nsis@ietf.org
Subject: RE: [NSIS] Proposed NSIS charter
Date: Fri, 26 Oct 2001 09:11:08 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Hi Weijing,

> Does it also include wireline beside wireless? e.g. Ethernet, DSL, etc
> network.

Yes.

John

_______________________________________________
nsis mailing list
nsis@ietf.org
http://www1.ietf.org/mailman/listinfo/nsis



From daemon@optimus.ietf.org  Tue Oct 30 09:54:10 2001
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 JAA02786
	for <nsis-archive@odin.ietf.org>; Tue, 30 Oct 2001 09:54:10 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA03484
	for nsis-archive@odin.ietf.org; Tue, 30 Oct 2001 09:54:14 -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 JAA03117;
	Tue, 30 Oct 2001 09:46:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA03080
	for <nsis@optimus.ietf.org>; Tue, 30 Oct 2001 09:46:36 -0500 (EST)
Received: from mail.zrz.tu-berlin.de (mail.zrz.TU-Berlin.DE [130.149.4.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02454
	for <nsis@ietf.org>; Tue, 30 Oct 2001 09:46:31 -0500 (EST)
Received: from ftsu07.ee.tu-berlin.de ([130.149.49.87] helo=ftmail.ee.tu-berlin.de)
	  by mail.zrz.tu-berlin.de with smtp (exim-3.33)
	  id 15ya9S-0000Ps-00; Tue, 30 Oct 2001 15:46:02 +0100
Received: from ee.tu-berlin.de (fu@sinope.ee.TU-Berlin.DE [130.149.49.127])
	by ftmail.ee.tu-berlin.de (8.11.3/8.11.3) with ESMTP id f9UEk1D05849;
	Tue, 30 Oct 2001 15:46:01 +0100
Message-ID: <3BDEBD29.6698478C@ee.tu-berlin.de>
Date: Tue, 30 Oct 2001 15:46:01 +0100
From: Xiaoming Fu <fu@ee.tu-berlin.de>
Reply-To: fu@ee.tu-berlin.de
Organization: Telecommunication Networks Group, TU-Berlin
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.9-686 i686)
X-Accept-Language: en-US, de, zh-CN
MIME-Version: 1.0
To: nsis@ietf.org
CC: john.loughney@nokia.com
Subject: Re: [NSIS] Proposed NSIS charter
References: <200110251600.MAA11294@optimus.ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

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)"? 

> >       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.

Thanks

Xiaoming

_______________________________________________
nsis mailing list
nsis@ietf.org
http://www1.ietf.org/mailman/listinfo/nsis



From daemon@optimus.ietf.org  Tue Oct 30 10:19:40 2001
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



From daemon@optimus.ietf.org  Tue Oct 30 10:41:30 2001
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 KAA04462
	for <nsis-archive@odin.ietf.org>; Tue, 30 Oct 2001 10:41:29 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA06167
	for nsis-archive@odin.ietf.org; Tue, 30 Oct 2001 10:41:34 -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 KAA06154;
	Tue, 30 Oct 2001 10:41:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA06122
	for <nsis@optimus.ietf.org>; Tue, 30 Oct 2001 10:41:14 -0500 (EST)
Received: from mail.zrz.tu-berlin.de (mail.zrz.TU-Berlin.DE [130.149.4.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04453
	for <nsis@ietf.org>; Tue, 30 Oct 2001 10:41:09 -0500 (EST)
Received: from ftsu07.ee.tu-berlin.de ([130.149.49.87] helo=ftmail.ee.tu-berlin.de)
	  by mail.zrz.tu-berlin.de with smtp (exim-3.33)
	  id 15yb0L-00027c-00; Tue, 30 Oct 2001 16:40:41 +0100
Received: from ee.tu-berlin.de (fu@sinope.ee.TU-Berlin.DE [130.149.49.127])
	by ftmail.ee.tu-berlin.de (8.11.3/8.11.3) with ESMTP id f9UFeeD07788;
	Tue, 30 Oct 2001 16:40:41 +0100
Message-ID: <3BDEC9F8.F271D16F@ee.tu-berlin.de>
Date: Tue, 30 Oct 2001 16:40:40 +0100
From: Xiaoming Fu <fu@ee.tu-berlin.de>
Reply-To: fu@ee.tu-berlin.de
Organization: Telecommunication Networks Group, TU-Berlin
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.9-686 i686)
X-Accept-Language: en-US, de, zh-CN
MIME-Version: 1.0
To: "Chaskar Hemant (NRC/Boston)" <Hemant.Chaskar@nokia.com>, nsis@ietf.org
CC: "Loughney John (NRC/Helsinki)" <john.loughney@nokia.com>
Subject: Re: [NSIS] Proposed NSIS charter
References: <E320A8529CF07E4C967ECC2F380B0CF90890E9@bsebe001.NOE.Nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hi Hemant,

>      Are there any other core modifications to RSVP that we can think
> of.

I think also there was an intention to avoid the "receiver-initiated"
way since a mobile generally could initiate the reservation in the new
path. The result is the reduced latency.

>         [HC] I think Xiaoming meant
> 
> http://ietf.org/internet-drafts/draft-chaskar-mobileip-qos-01.txt.
> 
>         Thanks.
> 
>       Hemant

Yes I meant that. The former link is the requirement draft. 

Sorry for the mistake,

Xiaoming

_______________________________________________
nsis mailing list
nsis@ietf.org
http://www1.ietf.org/mailman/listinfo/nsis



From daemon@optimus.ietf.org  Tue Oct 30 11:24:48 2001
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 LAA05862
	for <nsis-archive@odin.ietf.org>; Tue, 30 Oct 2001 11:24:48 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA08580
	for nsis-archive@odin.ietf.org; Tue, 30 Oct 2001 11:24:51 -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 LAA08509;
	Tue, 30 Oct 2001 11:24:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA08479
	for <nsis@optimus.ietf.org>; Tue, 30 Oct 2001 11:24:22 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05841
	for <nsis@ietf.org>; Tue, 30 Oct 2001 11:24:14 -0500 (EST)
Received: from esealnt409.al.sw.ericsson.se (ESEALNT409.al.sw.ericsson.se [153.88.251.32])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f9UGODf07025
	for <nsis@ietf.org>; Tue, 30 Oct 2001 17:24:13 +0100 (MET)
Received: FROM esealnt746.al.sw.ericsson.se BY esealnt409.al.sw.ericsson.se ; Tue Oct 30 17:24:12 2001 +0100
Received: by ESEALNT746.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <THN5KTS3>; Tue, 30 Oct 2001 17:16:42 +0100
Message-ID: <E244E44D6AB85E40AEEF7EAABE3545FA0C29DF@enleent104.nl.eu.ericsson.se>
From: "Georgios Karagiannis (ELN)" <Georgios.Karagiannis@eln.ericsson.se>
To: "'Chaskar Hemant (NRC/Boston)'" <Hemant.Chaskar@nokia.com>, nsis@ietf.org
Cc: "Loughney John (NRC/Helsinki)" <john.loughney@nokia.com>,
        fu@ee.tu-berlin.de
Subject: RE: [NSIS] Proposed NSIS charter
Date: Tue, 30 Oct 2001 17:23:57 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Hi Hemant

Before discussing possible modifications on 
RSVP, I think we should first discuss and 
agree on the charter.
In my opinion this charter is very much Mobile IP centric.
There are some other wireless QoS requirements that 
in my opinion should also be included in these discussions.
Such requirements are specified in:
http://search.ietf.org/internet-drafts/draft-westberg-rmd-cellular-issues-00.txt

Best regards,
Georgios

-----Original Message-----
From: Chaskar Hemant (NRC/Boston) [mailto:Hemant.Chaskar@nokia.com]
Sent: dinsdag 30 oktober 2001 16:19
To: nsis@ietf.org
Cc: Loughney John (NRC/Helsinki); fu@ee.tu-berlin.de
Subject: RE: [NSIS] Proposed NSIS charter


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 mailing list
nsis@ietf.org
http://www1.ietf.org/mailman/listinfo/nsis



From daemon@optimus.ietf.org  Tue Oct 30 14:58:48 2001
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 OAA13102
	for <nsis-archive@odin.ietf.org>; Tue, 30 Oct 2001 14:58:48 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA17793
	for nsis-archive@odin.ietf.org; Tue, 30 Oct 2001 14:58:52 -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 OAA17747;
	Tue, 30 Oct 2001 14:55:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA17718
	for <nsis@optimus.ietf.org>; Tue, 30 Oct 2001 14:55:13 -0500 (EST)
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13071
	for <nsis@ietf.org>; Tue, 30 Oct 2001 14:55:09 -0500 (EST)
Received: from davir01nok.americas.nokia.com (davir01nok.americas.nokia.com [172.18.242.84])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f9UJtGQ05160
	for <nsis@ietf.org>; Tue, 30 Oct 2001 13:55:16 -0600 (CST)
Received: from daebh002.NOE.Nokia.com (unverified) by davir01nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T56ea4d1f57ac12f2540ff@davir01nok.americas.nokia.com>;
 Tue, 30 Oct 2001 13:55:10 -0600
Received: from daebe005.NOE.Nokia.com ([172.18.242.203]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Tue, 30 Oct 2001 13:55:08 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
Subject: RE: [NSIS] Proposed NSIS charter
Date: Tue, 30 Oct 2001 13:55:08 -0600
Message-ID: <748E8123D183394982E32A511DB3E7360C8114@daebe005.NOE.Nokia.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [NSIS] Proposed NSIS charter
Thread-Index: AcFhVkUjvYgNPc1IEdWryQAIx6S5QwAIN6nQ
From: "Zheng Haihong (NRC/Dallas)" <haihong.zheng@nokia.com>
To: "Chaskar Hemant (NRC/Boston)" <Hemant.Chaskar@nokia.com>, <nsis@ietf.org>
Cc: "Loughney John (NRC/Helsinki)" <john.loughney@nokia.com>,
        <fu@ee.tu-berlin.de>
X-OriginalArrivalTime: 30 Oct 2001 19:55:08.0843 (UTC) FILETIME=[C72B57B0:01C1617C]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id OAA17719
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, Hemant,

> 
> 	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.

The IPv6 Flow-label FILTER-SPEC Class that carries the source address
and flow label has already been defined in the current RSVP. However
this may not get rid of the problems related to changing CoA in MIP.
This is because a flow is supposed to be uniquely identified by the
combination of the source address and the non-zero flow label. Thus when
CoA is changed, the flow identifier is changed unless all the router has
been informed by the change of CoA. 

We had an ID
http://www.ietf.org/internet-drafts/draft-shen-rsvp-mobileipv6-interop-0
0.txt. which proposed to use home address carried in the home address
option in the destination option header to identify the source of a
packet. The combination of home address and flow label can always
uniquely identifies a flow.  

> 	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.

Agree. 

>       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.

Agree.

BR,

Haihong

_______________________________________________
nsis mailing list
nsis@ietf.org
http://www1.ietf.org/mailman/listinfo/nsis



From daemon@optimus.ietf.org  Wed Oct 31 01:11:49 2001
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 BAA23783
	for <nsis-archive@odin.ietf.org>; Wed, 31 Oct 2001 01:11:49 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA06510
	for nsis-archive@odin.ietf.org; Wed, 31 Oct 2001 01:11:52 -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 BAA02837;
	Wed, 31 Oct 2001 01:07:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA02785
	for <nsis@optimus.ietf.org>; Wed, 31 Oct 2001 01:07:36 -0500 (EST)
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23230
	for <nsis@ietf.org>; Wed, 31 Oct 2001 01:07:32 -0500 (EST)
From: john.loughney@nokia.com
Received: from esvir02nok.nokia.com (esvir02nokt.ntc.nokia.com [172.21.143.34])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f9V68AA20759
	for <nsis@ietf.org>; Wed, 31 Oct 2001 08:08:10 +0200 (EET)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir02nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T56ee353a77ac158f22076@esvir02nok.nokia.com>;
 Wed, 31 Oct 2001 08:07:33 +0200
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <VPYVTP80>; Wed, 31 Oct 2001 08:07:33 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF5D8F3F@esebe004.NOE.Nokia.com>
To: Georgios.Karagiannis@eln.ericsson.se, nsis@ietf.org
Subject: RE: [NSIS] Proposed NSIS charter
Date: Wed, 31 Oct 2001 08:07:21 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Hi Georgios,

> Before discussing possible modifications on 
> RSVP, I think we should first discuss and 
> agree on the charter.
> In my opinion this charter is very much Mobile IP centric.

I'm sorry, but I don't see the Mobile IP centered-ness
of the charter.  We've been asked by members of the
IESG to consider one document as input to the discussion.

That being said, all parties are allowed & encouraged to
submit personal Internet Drafts for consideration. It might
be good if any drafts fit the first few work items:

Dec 01	Initial ID on Signaling Requirements.

Dec 01	Initial ID on Analysis of existing signaling protocols.

Mar 02 	Initial ID on 'Next Step QoS Signaling'.

I imagine that the 3rd work item would be some sort of framework
document.

best regards,
John

_______________________________________________
nsis mailing list
nsis@ietf.org
http://www1.ietf.org/mailman/listinfo/nsis



From daemon@optimus.ietf.org  Wed Oct 31 04:44:22 2001
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 EAA09383
	for <nsis-archive@odin.ietf.org>; Wed, 31 Oct 2001 04:44:22 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA10915
	for nsis-archive@odin.ietf.org; Wed, 31 Oct 2001 04:44:22 -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 EAA10904;
	Wed, 31 Oct 2001 04:44:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA10871
	for <nsis@optimus.ietf.org>; Wed, 31 Oct 2001 04:44:04 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09378
	for <nsis@ietf.org>; Wed, 31 Oct 2001 04:44:02 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f9V9i1f22776
	for <nsis@ietf.org>; Wed, 31 Oct 2001 10:44:01 +0100 (MET)
Received: FROM esealnt746.al.sw.ericsson.se BY esealnt461 ; Wed Oct 31 10:43:57 2001 +0100
Received: by ESEALNT746.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <THN5KWVN>; Wed, 31 Oct 2001 10:43:46 +0100
Message-ID: <E244E44D6AB85E40AEEF7EAABE3545FA0C29E2@enleent104.nl.eu.ericsson.se>
From: "Georgios Karagiannis (ELN)" <Georgios.Karagiannis@eln.ericsson.se>
To: "'john.loughney@nokia.com'" <john.loughney@nokia.com>, nsis@ietf.org
Subject: RE: [NSIS] Proposed NSIS charter
Date: Wed, 31 Oct 2001 10:43:44 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Hi John


Thank you very much for the reply. 
Please see my comments below.

[GK] = Georgios Karagiannis
[JL] = John Loughney


[GK] Before discussing possible modifications on 
[GK] RSVP, I think we should first discuss and 
[GK] agree on the charter.
[GK] In my opinion this charter is very much Mobile IP centric.

[JL] I'm sorry, but I don't see the Mobile IP centered-ness
[JL] of the charter. 
 
  Sorry John, but when I am  reading the following sentence,
  included in this charter, I really get the impression that 
  this charter is Mobile IP centric.

"As input to the working group, the Mobile IP QoS Requirements
document (draft-mobileip-qos-requirements) will be considered by the working
group."

[JL] We've been asked by members of the
[JL] IESG to consider one document as input to the discussion.

OK, but why then you have not considered the draft written 
by Scott Bradner and Allison Mankin entitled:
"Report of the Next Steps in Signaling BOF" and located at:      
http://search.ietf.org/internet-drafts/draft-bradner-nsis-bof-00.txt

This draft presents an initial set of
requirements for a next generation Internet signaling protocol.  
It is actually describing several requirements (briefly) 
presented by many people during the 50th IETF meeting.

Best regards,
Georgios


_______________________________________________
nsis mailing list
nsis@ietf.org
http://www1.ietf.org/mailman/listinfo/nsis



From daemon@optimus.ietf.org  Wed Oct 31 07:49:54 2001
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 HAA12166
	for <nsis-archive@odin.ietf.org>; Wed, 31 Oct 2001 07:49:54 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA15190
	for nsis-archive@odin.ietf.org; Wed, 31 Oct 2001 07:49:52 -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 HAA15170;
	Wed, 31 Oct 2001 07:47:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA15135
	for <nsis@optimus.ietf.org>; Wed, 31 Oct 2001 07:47:44 -0500 (EST)
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12074
	for <nsis@ietf.org>; Wed, 31 Oct 2001 07:47:44 -0500 (EST)
From: john.loughney@nokia.com
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f9VCmOA21185
	for <nsis@ietf.org>; Wed, 31 Oct 2001 14:48:24 +0200 (EET)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T56efa39ee2ac158f24077@esvir04nok.ntc.nokia.com>;
 Wed, 31 Oct 2001 14:47:45 +0200
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <VPYV4H26>; Wed, 31 Oct 2001 14:47:45 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF5D8F4F@esebe004.NOE.Nokia.com>
To: Georgios.Karagiannis@eln.ericsson.se, nsis@ietf.org
Subject: RE: [NSIS] Proposed NSIS charter
Date: Wed, 31 Oct 2001 14:47:41 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Hi Georgios,

> [JL] We've been asked by members of the
> [JL] IESG to consider one document as input to the discussion.
> 
> OK, but why then you have not considered the draft written 
> by Scott Bradner and Allison Mankin entitled:
> "Report of the Next Steps in Signaling BOF" and located at:      
> http://search.ietf.org/internet-drafts/draft-bradner-nsis-bof-00.txt
> 
> This draft presents an initial set of
> requirements for a next generation Internet signaling protocol.  
> It is actually describing several requirements (briefly) 
> presented by many people during the 50th IETF meeting.

This hasn't come up in the chartering discussion with 
our ADs (Scott & Allison). I think that they are on the
list & they can speak up , if it would be good to consider
this as part of the WG effort.

John

_______________________________________________
nsis mailing list
nsis@ietf.org
http://www1.ietf.org/mailman/listinfo/nsis



From daemon@optimus.ietf.org  Wed Oct 31 08:58:23 2001
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 IAA18599
	for <nsis-archive@odin.ietf.org>; Wed, 31 Oct 2001 08:58:23 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA17326
	for nsis-archive@odin.ietf.org; Wed, 31 Oct 2001 08:58:22 -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 IAA17310;
	Wed, 31 Oct 2001 08:58:06 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA17279
	for <nsis@optimus.ietf.org>; Wed, 31 Oct 2001 08:58:04 -0500 (EST)
Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18593
	for <nsis@ietf.org>; Wed, 31 Oct 2001 08:58:04 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.10.2/8.10.2) id f9VDsDP05440;
	Wed, 31 Oct 2001 08:54:13 -0500 (EST)
Date: Wed, 31 Oct 2001 08:54:13 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200110311354.f9VDsDP05440@newdev.harvard.edu>
To: Georgios.Karagiannis@eln.ericsson.se, john.loughney@nokia.com,
        nsis@ietf.org
Subject: RE: [NSIS] Proposed NSIS charter
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

a good point - that ID should be considered (that is why we wrote it)

Scott

_______________________________________________
nsis mailing list
nsis@ietf.org
http://www1.ietf.org/mailman/listinfo/nsis



From daemon@optimus.ietf.org  Wed Oct 31 11:17:12 2001
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 LAA23203
	for <nsis-archive@odin.ietf.org>; Wed, 31 Oct 2001 11:17:11 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA23764
	for nsis-archive@odin.ietf.org; Wed, 31 Oct 2001 11:17:12 -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 LAA23729;
	Wed, 31 Oct 2001 11:16:59 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA23701
	for <nsis@optimus.ietf.org>; Wed, 31 Oct 2001 11:16:57 -0500 (EST)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23173
	for <nsis@ietf.org>; Wed, 31 Oct 2001 11:16:55 -0500 (EST)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id RAA21953;
	Wed, 31 Oct 2001 17:16:56 +0100 (MET)
Received: from mchh247e.demchh201e.icn.siemens.de ([139.21.200.57])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id RAA17190;
	Wed, 31 Oct 2001 17:16:57 +0100 (MET)
Received: by MCHH247E with Internet Mail Service (5.5.2653.19)
	id <V0PX1N74>; Wed, 31 Oct 2001 17:16:56 +0100
Message-ID: <D73559B38D51D4119CB800508B9527B502779369@MCHH266E>
From: Ersue Mehmet <Mehmet.Ersue@icn.siemens.de>
To: "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        Georgios.Karagiannis@eln.ericsson.se
Cc: nsis@ietf.org
Subject: WG: [NSIS] Proposed NSIS charter
Date: Wed, 31 Oct 2001 17:16:56 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA23702
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 John, Georgios, 

the results from the NSIS BOF in Minneapolis are very 
useful for this WG because of the numerous and different 
requirements. There are also other sources for lightweight 
QoS signalling requirements for access networks. 
Especially we should also consider requirements for 
mobilty environments from 3G standardization and mobile 
Internet service providers (s. MORE BOF in London), in 
addition to the already mentioned I-Ds by Georgios and 
Hemant.

If we design a protocol by considering all of these 
requirements we will get something which is probably 
too complex and not scalable.
We have also to think on a framework definition in 
parallel, e.g. with a modular, extensible protocol 
suite which has a few well-defined optional extensions 
for specific scenarios. Implementors should be able to 
choose between the full suite or optimizing the 
implementation by using only a basic subset.

Are you planning to define design teams for the signaling 
requirements and framework architecture I-Ds in Salt 
Lake City? IMO both I-Ds could be developed more stable 
if the design teams would have a somehow parallel schedule 
or could be synchronized.

Best Regards,
Mehmet Ersü


-----Ursprüngliche Nachricht-----
Von: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
Gesendet: Mittwoch, 31. Oktober 2001 13:48
An: Georgios.Karagiannis@eln.ericsson.se; nsis@ietf.org
Betreff: RE: [NSIS] Proposed NSIS charter


Hi Georgios,

> [JL] We've been asked by members of the
> [JL] IESG to consider one document as input to the discussion.
> 
> OK, but why then you have not considered the draft written 
> by Scott Bradner and Allison Mankin entitled:
> "Report of the Next Steps in Signaling BOF" and located at:      
> http://search.ietf.org/internet-drafts/draft-bradner-nsis-bof-00.txt
> 
> This draft presents an initial set of
> requirements for a next generation Internet signaling protocol.  
> It is actually describing several requirements (briefly) 
> presented by many people during the 50th IETF meeting.

This hasn't come up in the chartering discussion with 
our ADs (Scott & Allison). I think that they are on the
list & they can speak up , if it would be good to consider
this as part of the WG effort.

John

_______________________________________________
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



From daemon@optimus.ietf.org  Wed Oct 31 11:54:14 2001
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 LAA24174
	for <nsis-archive@odin.ietf.org>; Wed, 31 Oct 2001 11:54:09 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA25622
	for nsis-archive@odin.ietf.org; Wed, 31 Oct 2001 11:54:10 -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 LAA25612;
	Wed, 31 Oct 2001 11:53:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA25578
	for <nsis@optimus.ietf.org>; Wed, 31 Oct 2001 11:53:56 -0500 (EST)
Received: from howler.tri.sbc.com (howler.tri.sbc.com [205.173.58.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24155
	for <nsis@ietf.org>; Wed, 31 Oct 2001 11:53:54 -0500 (EST)
Received: from sbctri.tri.sbc.com (sbctri [144.60.1.10])
	by howler.tri.sbc.com (8.11.0/8.11.0) with ESMTP id f9VGtJT01410;
	Wed, 31 Oct 2001 10:55:19 -0600 (CST)
Received: from TRIMAIL2.tri.sbc.com (localhost [127.0.0.1])
	by sbctri.tri.sbc.com (8.11.0/8.9.3) with ESMTP id f9VGrZK24342;
	Wed, 31 Oct 2001 10:53:35 -0600 (CST)
Received: by TRIMAIL2.tri.sbc.com with Internet Mail Service (5.5.2653.19)
	id <VWX2MQFQ>; Wed, 31 Oct 2001 10:53:51 -0600
Message-ID: <905A1C4ABF353F4C8CC16FA9F53DD0D632239A@TRIMAIL2.tri.sbc.com>
From: "Chen, Weijing" <wchen@tri.sbc.com>
To: "'john.loughney@nokia.com'" <john.loughney@nokia.com>,
        Georgios.Karagiannis@eln.ericsson.se, nsis@ietf.org
Subject: RE: [NSIS] Proposed NSIS charter
Date: Wed, 31 Oct 2001 10:53:50 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

John, Georgios,

If it is the case that NSIS is not limited to Mobile IP,  so we could
include signaling consideration for DSL, Ethernet on last mile, etc access
technology?

To simplifying the signaling protocol, we can focus on UNI function, which
could be independent of NNI function. For service provider point of view, we
see clearly need of separation of  UNI signaling and NNI signaling. Maybe
NSIS is the right platform for UNI only signaling?
 
--
Weijing Chen
SBC Technology Resources
9505 Arboretum Blvd.
Austin, TX 78759
512 372 5710
wchen@tri.sbc.com


 -----Original Message-----
From: 	john.loughney@nokia.com [mailto:john.loughney@nokia.com] 
Sent:	Wednesday, October 31, 2001 12:07 AM
To:	Georgios.Karagiannis@eln.ericsson.se; nsis@ietf.org
Subject:	RE: [NSIS] Proposed NSIS charter

Hi Georgios,

> Before discussing possible modifications on 
> RSVP, I think we should first discuss and 
> agree on the charter.
> In my opinion this charter is very much Mobile IP centric.

I'm sorry, but I don't see the Mobile IP centered-ness
of the charter.  We've been asked by members of the
IESG to consider one document as input to the discussion.

That being said, all parties are allowed & encouraged to
submit personal Internet Drafts for consideration. It might
be good if any drafts fit the first few work items:

Dec 01	Initial ID on Signaling Requirements.

Dec 01	Initial ID on Analysis of existing signaling protocols.

Mar 02 	Initial ID on 'Next Step QoS Signaling'.

I imagine that the 3rd work item would be some sort of framework
document.

best regards,
John

_______________________________________________
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



