Subject: [NSIS] Updated charter proposal

From: [email-masked]
Date: Thu, 22 May 2003 13:31:20 +0300

Hi all,

Just to refresh everyone's memory, the proposed charter update is as follows. Note that some dates on the goals & milestones need to be updated.

John

Next Steps in Signaling (nsis) Charter

Chair(s):
J. Loughney <[email-masked]>

Transport Area Director(s):
S. Bradner <[email-masked]>
A. Mankin <[email-masked]>

Transport Area Advisor:
A. Mankin <[email-masked]>

Mailing Lists:
General Discussion: [email-masked]
To Subscribe: [email-masked]
In Body: (un)subscribe
Archive: www.ietf.org/mail-archive/working-groups/nsis/current/maillist.html

Description of Working Group:

The Next Steps in Signaling Working Group is responsible for standardizing an IP signaling protocols with QoS signaling as the first use case.  This working group will concentrate on a two-layer signaling paradigm.  The intention is to re-use, where appropriate, the protocol mechanisms of RSVP, while at the same time simplifying it and applying a more general signaling model.  

The existing work on the requirements, the framework and analysis of existing protocols will be completed and used as input for the protocol work. 

NSIS will develop a transport layer signaling protocol for the transport of upper layer signaling. In order to support a tool box or building block approach, the two-layer model will be used to separate the transport of the signaling from the application signaling.  This allows for a more general signaling protocol to be developed to support signaling for different services or resources, such as NAT & firewall traversal and QoS resources.  The initial NSIS application will be an optimized RSVP 	QoS signaling protocol.  The second application will be a middle box traversal protocol.  It may be that a rechartering of the working group occurs before the completion of this milestone.

Security is a very important concern for NSIS. The working group will study and analyze the threats and security requirements for signaling. Compatibility with authentication and authorization mechanisms such as those of Diameter, COPS-PR, and RSVP-PR auth-session, will be addressed.

It is a non-goal of the working group to develop new resource allocation protocols. Resource reservation and traffic engineering are out of scope of this working group.  Additionally, third party signaling is out of scope of this working group.  Mobility protocols and AAA work are out of scope of the working group. The work produced in this Working Group should work with existing IETF mobility and AAA protocols, including (but not limited to) Mobile IP, SeaMoby Context also welcomes participation and expression of requirements from non-IETF standards organization members, for instance 3GPP, 3GPP2 and ITU-T. 

Goals and Milestones:

MAR 03	Submit "Requirements for Signaling Protocols" to IESG for 
		publication as Informational RFC
APR 03	Submit "RSVP Security Properties" to IESG as Informational RFC
MAY 03	Submit "NSIS Threats" to IESG as Informational RFC
JUL 03	Submit "Analysis of Existing Signaling Protocols" to IESG as
		Informational RFC
SEP 03	Submit "Next Steps in Signaling: Framework" to IESG for publication 
		as Informational RFC
FEB 04	Submit "NSIS Transport Protocol" to IESG for publication for 
		Proposed Standard
MAR 04	Submit "NSIS QoS Application Protocol" to IESG for publication 
		for Proposed Standard
SEP 04  	Submit "NSIS Middle Box Signaling Application Protocol" to 
		IESG for publication for Proposed Standard
_______________________________________________
nsis mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/nsis