Subject: RE: [NSIS] [Requirements draft] Scenarios

From: [email-masked]
Date: Fri, 25 Oct 2002 12:49:34 +0300

Hi Bob,

I agree with you.  I think that after we do some basic
work on NSIS (Requirements & Framework last called &
a good start on the protocol work) discussing how to apply
NSIS for solutions or applying to networks would be
an appropriate time.

John

> -----Original Message-----
> From: ext Bob Braden [mailto:[email-masked]]
> Sent: 24 October, 2002 20:50
> To: [email-masked]; [email-masked]
> Subject: Re: [NSIS] [Requirements draft] Scenarios
> 
> 
>   *> 
>   *> I believe the Appendix of the [Requirements draft] could 
> be enhanced with
>   *> scenarios from the ISC Reference Arquitecture.
>   *> 
>   *> 
> http://www.softswitch.org/attachments/Reference_Architecture_5-02.pdf
>   *> 
> 
> Well, maybe yes, maybe no.  Voice over IP is certainly an important
> potential application of NSIS protocols, but by no means the only one,
> and in the long run it might not even be the most important.  (Ask
> me sometime about my success in predicting the future of the 
> Internet ;-))
> 
> However, I would note that driving NSIS from VoIP requiremetns would
> entangle the NSIS WG with a hugely complex
> telephone infrastructure.  Trying too hard to accommodate its
> complexities is likely to distort our efforts and lead us away from
> the more important goals of generality and extensibility.  I 
> have the same uneasy
> feelinga about the wireless material in the Appendix, BTW.  
> What we need
> is some abstraction of the requirements of VoIP and of 
> wireless.  In the
> Internet we want signaling protocols that are flexible, generel, and
> extensible.  As you penetrate deep into wireless networks or into the
> phone network, I would expect special-purpose signaling protocols to
> be used.  It seems to me that the right way to model these complex
> special environments is as individual link layers, with IP over top.
> Just as RSVP can invoke link layer signaling, e.g., ATM (RFC2382) or
> IEEE 802 (RFC 2814), so an Internet NSIS signaling protocol can invoke
> the wireless or phone network signaling protocol.
> 
> I would rather see much less emphasis on telephony in the Appendx,
> and a broader range of Internet signaling applications.
> 
> Bob Braden
> 
> 
>   *> Network Examples
>   *> 
> ..............................................................
> ..............
>   *> .......................13
>   *> Wireline Network
>   *> 
> ..............................................................
> ..............
>   *> ...................................................13
>   *> All-IP Network....14
>   *> VoIP Tandem
>   *> 
> Switching.....................................................
> ..............
>   *> .................................................16
>   *> POTS Carried over IP
>   *> 
> ..............................................................
> ..............
>   *> ...........................................16
>   *> Access Network (V5/ISDN) over
>   *> 
> IP............................................................
> ..............
>   *> .........................17
>   *> Cable Network (e.g. PacketCable(tm)) over
>   *> 
> IP............................................................
> ..............
>   *> ..........17
>   *> VoDSL and IAD over IP
>   *> 
> ..............................................................
> ..............
>   *> ........................................18
>   *> Wireless (3GPP R99 Special Case NGN)
>   *> 
> ..............................................................
> ..............
>   *> ............19
>   *> Wireless (3GPP R2000 General Case all IP)
>   *> 
> ..............................................................
> ..............
>   *> .......19
>   *> WCDMA Mobile Network
>   *> 
> ..............................................................
> ..............
>   *> ......................................20
>   *> 
>   *> Alejandro Avella
>   *> 
>   *> [Requirements draft]
>   *> http://www.ietf.org/internet-drafts/draft-ietf-nsis-req-04.txt
>   *> 
>   *> 
>   *> 
> **************************************************************
> ***********
>   *> This e-mail transmission, and any documents, files, or previous
>   *> e-mail messages attached to it may contain information that is 
>   *> confidential or legally privileged.  If you are not the intended 
>   *> recipient, or a person responsible for delivering it to the 
>   *> intended recipient, you are hereby notified that you must not 
>   *> read this transmission and that any disclosure, copying, 
> printing,
>   *> distribution, or use of any of the information contained in or 
>   *> attached to this transmission is strictly prohibited.  
> If you have 
>   *> received this transmission in error, please immediately 
> notify the 
>   *> sender by telephone or return e-mail and delete the original 
>   *> transmission and its attachments without reading or saving them 
>   *> in any manner.  Thank you.
>   *> 
> **************************************************************
> ***********
> _______________________________________________
> nsis mailing list
> [email-masked]
> https://www1.ietf.org/mailman/listinfo/nsis
> 
_______________________________________________
nsis mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/nsis