Subject: [NSIS] Labeling NSIS requirements

From: "Georgios Karagiannis (ELN)" <[email-masked]>
Date: Tue, 25 Feb 2003 11:13:58 +0100

Hi Marcus

According to some discussions 
that took place during the NSIS interim meeting, 
there was a need of assigning "generic" and
 "QoS specific" labels to the NSIS requirements.

Please receive an attempt proposal of assigning 
 "generic" or QoS specific" 
labels to the NSIS requirements.

Best Regards,
Georgios

5.1 Architecture and Design Goals 
5.1.1 MUST be applicable for different technologies. 
[Georgios] Generic, but will probably  be removed!

5.1.2 SHOULD provide resource availability information on request  
[Georgios] QoS specific

5.1.3 NSIS MUST be designed modularly  
[Georgios] Generic

5.1.4 NSIS MUST decouple protocol and information 
[Georgios] Generic

 5.1.5 NSIS MUST reuse existing provisioning 
[Georgios] QoS specific, but it will probably be removed
    
5.1.6 NSIS MUST support independence of signaling and provisioning 
     paradigm 
[Georgios] QoS specific, but it will probably be removed

 5.1.7 NSIS MUST be application independent 
[Georgios] Generic
    
5.2 Signaling Flows 
5.2.1 The placement of NSIS Initiator, Forwarder, Responder MUST be 
     free 
 [Georgios] Generic, probably will be modified ??
    
5.2.2 No constraint MUST be posed the signaling and NSIS Forwarders to 
     be in the data path. 
[Georgios] Generic, but probably will be somehow modified
 
5.2.3 Concealment of topology and technology information SHOULD be 
     possible 
[Georgios] Generic
    
5.2.4 Transparent signaling through networks SHOULD be possible 
[Georgios] Generic
 
5.3 Messaging 
5.3.1 Explicit release of resources MUST be possible 
[Georgios] Generic if resources are replaced by transport 
 state; QoS specific if the release refers to reservations
    
5.3.2 Automatic release of resources after failure SHOULD be possible 
[Georgios] Generic if resources are replaced by transport 
  state; QoS specific if the release refers to reservations

5.3.3 NSIS SHOULD allow for sending notifications upstream 
[Georgios] Generic
 
5.3.4 Feedback about success of service request MUST be provided 
    [Georgios] Generic
 
5.3.5 NSIS MUST allow for local information exchange  
  [Georgios] Generic

5.4 Control Information 
5.4.1 Mutability information on parameters SHOULD be possible 
[Georgios] Generic
    
5.4.2 SHOULD possible to add and remove local domain information  
[georgios] Generic
    
5.4.3 State MUST be addressed independent of flow identification 
[Georgios] Generic
    
5.4.4 Modification of already reserved resources SHOULD be seamless 
[Georgios] QoS specific
    
5.4.5 Grouping of signaling for several micro-flows MAY be provided 
[Georgios] QoS specific
    
5.5 Performance 
[Georgios] I consider the performance requirements as Generic,
since they are applicable to all types of signaling   
5.5.1 Scalability  
[Georgios] Generic

5.5.2 NSIS SHOULD allow for low latency in setup 
 [Georgios] Generic

5.5.3 NSIS MUST allow for low bandwidth consumption for signaling 
     protocol 
[Georgios] Generic

5.5.4 NSIS SHOULD allow to constrain load on devices 
[Georgios] Generic

5.5.5 NSIS SHOULD target highest possible network utilization 
 [Georgios] Generic

5.6 Flexibility 
5.6.1 Flow aggregation 
[Georgios] QoS specific
    
5.6.2 Flexibility in the placement of the NSIS Initiator 
[Georgios] Generic
    
5.6.3 Flexibility in the initiation of re-negotiation 
[Georgios] QoS specific
    
5.6.4 SOULD support network-initiated re-negotiation 
[Georgios] QoS specific

5.6.5 Uni / bi-directional reservation 
[Georgios] QoS specific

5.7 Security 
 [Georgios] I consider the security requirements as Generic,
since they are applicable to all types of signaling   

5.7.1 Authentication of signaling requests  
[Georgios] Generic

5.7.2 Resource Authorization  
[Georgios] Generic

5.7.3 Integrity protection  
[Georgios] Generic

5.7.4 Replay protection 
 [Georgios] Generic
   
5.7.5 Hop-by-hop security 
  [Georgios] Generic
   
5.7.6 Identity confidentiality and location privacy 
  [Georgios] Generic
   
5.7.7 Denial-of-service attacks 
   [Georgios] Generic
 
5.7.8 Confidentiality of signaling messages 
   [Georgios] Generic

5.7.9 Ownership of a reservation 
   [Georgios] Generic

5.8 Mobility 
5.8.1 Allow efficient service re-establishment after handover 
[Georgios] Generic
    
5.9 Interworking with other protocols and techniques 
 [Georgios] Generic
   
5.9.1 MUST interwork with IP tunneling 
  [Georgios] Generic

5.9.2 The solution MUST NOT constrain either to IPv4 or IPv6 
   [Georgios] Generic
  
5.9.3 MUST be independent from charging model 
  [Georgios] Generic
   
5.9.4 SHOULD provide hooks for AAA protocols 
 [Georgios] Generic

5.9.5 SHOULD interwork with seamless handoff protocols 
 [Georgios] Generic

5.9.6 MAY interwork with non-traditional routing 
 [Georgios] Generic

5.10 Operational 
5.10.1 Ability to assign transport quality to signaling messages. 
[Georgios] Generic

5.10.2 Graceful fail over 
 [Georgios] Generic

5.10.3 Graceful handling of NSIS entity problems 
 [Georgios] Generic

_______________________________________________
nsis mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/nsis