AW: [Ecrit] introduction section (<draft-schulzrinne-ecrit-requirements-01.txt>)

["Tschofenig, Hannes" <hannes.tschofenig at siemens.com>]

hi henning, 

> I agree that this can be shortened, but would like suggesting keeping 
> text that allows the reader to identify how our overall sequence of 
> steps work. This is far from obvious to most "bystanders" and 
> we don't 
> have another document to point to.
that's true. we don't have another document at the moment.

> Below, I trimmed stuff I think is 
> unncessary details and did some re-ordering.
good. 

ciao
hannes

> 
> Tschofenig, Hannes wrote:
> > hi all, 
> > 
> > please find my comments below (#). 
> > 
> > i think the introduction is too long and repeats requirements. 
> > 
> > 
> > 1.  Introduction
> > 
> >    Users of telephone-like services expect to be able to call for
> >    emergency help, such as police, the fire department or 
> an ambulance,
> >    regardless of where they are, what (if any) service 
> provider they are
> >    using and what kind of device they are using.  Unfortunately, the
> >    mechanisms for emergency calls that have evolved in the public
> >    circuit-switched telephone network (PSTN) are not quite 
> appropriate
> >    for evolving IP-based voice, text and real-time multimedia
> >    communications.  This document outlines the key 
> requirements that end
> >    systems and network elements such as SIP proxies need to 
> satisfy in
> >    order to provide emergency call services that offer at 
> least the same
> >    functionality as existing PSTN services, with the goal of making
> >    emergency calling more robust, cheaper to implement and 
> multimedia-
> >    capable.
> > 
> 
> > 
> >    This document only focuses on end-to-end IP-based calls, 
> i.e., where
> >    the emergency call originates from an IP end system, (Internet
> >    device), and terminates to an IP-capable PSAP, done 
> entirely over an
> >    IP network.
> > 
> > 
> > 
> > # ------ i would shorten the following paragraphs below by 
> just saying
> > something like. 
> > Section 2 defines terminology, Section 3 lists high-level 
> requirements,
> > etc... 
> > 
> >  
> >    This document identifies functional and security issues for
> > #                                          ^^^^^^^^^^^^^^^^
> > #  in fact this document does not specify security requirements. 
> > 
> >    determining the correct emergency identifier, for identifying the
> >    appropriate PSAP (emergency address) and for identifying 
> the caller
> >    and its current location.
> 
> [should be in section order]
> 
>  >    Emergency calls need to identify the location from 
> which the call is
>  >    initiated (Section 5).  The caller location needs to be 
> identified
>  >    for two purposes, namely to route the call to the 
> appropriate PSAP
>  >    and to display the caller location to the call taker to simplify
>  >    dispatching emergency assistance to the correct location.
> 
> 
> 
> 
> > 
> >    Emergency calls need to be identified (Section 6).  Emergency
> >    identifiers are used by the emergency caller to declare 
> a call to be
> >    an emergency call.  
> > 
> >    Emergency calls need to be routed to the appropriate PSAP (ref.
> >    Section 6).  
> 
> >    Emergency calls need to identify who placed the call 
> (Section 7). 
> 
> 

_______________________________________________
Ecrit mailing list
Ecrit at ietf.org
https://www1.ietf.org/mailman/listinfo/ecrit