Subject: [NSIS] NSIS Service Definition (not!)

From: Roland Bless <[email-masked]>
Date: Tue, 19 Mar 2002 23:01:04 +0100

Hi all,

to catch up the issue that Marcus had on one of his slides,
and, that caused much discussion, but for which there is 
IMO broad consensus in the WG: 

=> service definition is out of scope.
(just as others and I have stated before)
The NSIS protocol should be service-"agnostic" as much as 
possible:
- Which service or service parameter values are actually 
  signalled by the protocol should be transparent for
  the protocol carrying the information. (or as John said:
  not "what" but how is it signaled)
- One possible implementation is to carry a service
  object transparently. Later on, it might be required
  to identify objects of globally defined services by
  IANA assigned numbers.

What may be in the WG scope:
- How different services may influence the protocol 
  requirements (any suggestions?).

Regards,
 Roland

-- 
Roland Bless -- e-Mail: [email-masked]
Institute of Telematics, University of Karlsruhe, Germany  
Zirkel 2, D-76128 Karlsruhe -- Office: Bld. 20.20, 3rd floor, R 358
Phone: +49 721 608-6413 Fax: +49 721 388097

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