Subject: RE: [Ecrit] WG: Updated Req Review of I-D:draft-schulzrinne-ecrit-requirements-00.txt

From: "Roger Marshall" <[email-masked]>
Date: Wed, 18 May 2005 12:22:21 -0700

All:
RE: ECRIT REQUIREMENTS REVIEW UPDATE:

Below is a completed disposition status listing of ALL ecrit (I-D) requirements, based on continued (5/18) interim ecrit meeting this morning.

These results are associated with review of requirements listed in: 

draft-schulzrinne-ecrit-requirements-00.txt

3 categories (with qualifiers) of disposition are:
1. Keep (as written, or with required changes to text)
2. Move (into another <named> document)
3. Delete (remove, possibly merge into other requirement)

Note:
Original requirement numbers will not be reused.  New requirements will be added onto the end of each section (in the next revision of the I-D).

3.  High-Level Requirements
R1 - Keep
R2 - Keep
R3 - Keep
R4 - Keep
R5 - Keep (Henning Schulzrinne to rewrite text)
R6 - Keep (Ted Hardie to send candidate text as replacement for R6)
R7 - Delete

4.  Emergency Address
A1 - Keep (possible reword of A1, may split into two separate requirements)
A2 - Move (Jon Peterson will advise Henning on destination for A2)
A3 - Keep (reword along with A1 into two separable requirements)
A4 - Keep
A5 - Delete
A6 - Keep (possible reword per Ted Hardie composed text)
A7 - Delete

5.  Identifying the Caller Location
L1 - Move (L1, L2, & L3 to be put into a new document (to be created by James Polk) with the goal of becoming an Informational RFC
L2 - (see L1)
L3 - (see L1)
L4 - Move (into the Information doc)
L5 - Move (Patti McCalmont to rewrite, consolidate with L11, move into the Information doc)
L6 - Keep (Nadine Abbott to supply additional text)
L7 - Delete (out of scope)
L8 - Delete (out of scope)
L9 - Keep (Nadine to rewrite, for clarity to say "as input to the mapping protocol"
L10 - Keep (Hannes Tschofenig to lead further investigation w/Nadine, Ted)
L11 - Move (see L5)
L12 - Delete (out of scope)
L13 - Move (into the Information doc)

Note: based on discussion around L13, Brian Rosen to write a new requirement to say that mapping function must be independent of the call (and at the time of the call)

L14 - Delete (out of scope)
L15 - Delete (out of scope)

Note: based on discussion around L15, Brian Rosen to write a new requirement re: default routing

L16 - Delete (out of scope), (geopriv)
L17 - Delete (out of scope)
L18 - Delete (out of scope), (geopriv)
L19 - Delete (out of scope), (geopriv)
L20 - Delete (already discussed)
L21 - Move (into Informational doc)

[start of 5/18 discussion]

L22 - (Change to:) Move (to Informational doc/BCP) 
L23 - Delete
L24 - (Change to:) Move (to Informational doc/BCP)
L25 - Move (into Informational doc)
L26 - Delete (out of scope)
L27 - Delete (out of scope)
L28 - Keep (James Polk to provide reworded text)
L29 - Delete (out of scope)
L30 - Delete (out of scope, covered elsewhere)

6.  Identifying  the Appropriate Emergency Call Center

Note 1: Delete following paragraph from text block:
   "Note that the first proxy, the ESRP, doing the translation may not be
   in the same geographic area as the UA placing the emergency call."

Note 2: Consolidate following terms (throughout document):  ECC; iPSAP, IP-PSAP all become one term, PSAP.

I1 - Keep (reword as "Calls Must be routed to the PSAP responsible for this particular geographic area")
I2 - Move (into Informational doc)
I3 - Keep (rewrite, Henning will send text)
I4 - Keep (rewrite, Henning and Patti McCalmont to collaborate on text)
I5 - Delete (out of scope)
I6 - Delete (out of scope)
I7 - Keep (rewrite, Brian Rosen to send text)
I8 - Keep (rewrite, Henning to send text)
I9 - Keep (rewrite, Henning to send text)
I10 - Keep (Brian to rewrite as standalone requirement)
I11 - Delete (out of scope)
I12 - Move (to Informational doc)
I13 - Delete (out of scope)
I14 - Delete (redundant, mapping can be done based on any PIDF-LO field (see L9)
I15 - Move (to Informational doc)
I16 - Move (to Informational doc)
I17 - Move (to Informational doc)
I18 - Move (to Informational doc)
I19 - Move (to Informational doc)
I20 - Move (to Informational doc)
I21 - Delete (per rewritten I3/I4 by henning)
I22 - Move (to Informational doc)
I23 - Delete
I24 - Delete
I25 - Keep (to be rewritten by Henning)
I26 - Move (to Informational doc)
I27 - Move (to Informational doc)
I28 - Move (to Informational doc)
I29 - Delete
I30 - Move (to security document as an update)
I31 - Keep (rewrite, Ted Hardie to send text)
I32 - Delete
I33 - Delete
I34 - Move (to Informational doc)
I35 - Delete (merged into I31)
I36 - Move (to Informational doc, merge with Traceability)
I37 - Delete (out of scope)
I38 - Delete
I39 - Delete (merge with L13)

7.  Emergency Address Directory
D1 - Keep (rewrite, Henning to send text)
D2 - Move (to security doc)
D3 - Move (to security doc)
D4 - Delete (out of scope)
D5 - Keep (rewrite, Marc Linsner to send text as, "to specify minimize number of round trips rather than minimizing time")
D6 - Delete (already covered in rewritten I3/I4 by Henning)
D7 - Keep (rewrite, Henning to send text)
D8 - Move (combine with D9) & Delete Motivation text
D9 - Keep (rewrite to include D8)

8.  Identifying the Caller
C1 - Move (to Informational doc)
C2 - Move (to Informational doc)
C3 - Move (to Informational doc)

9.  Call Setup and Call Features
S1 - Move (to security doc)
S2 - Move (to informational doc)
S3 - Delete
S4 - Move (to security doc)
S5 - Move (to informational doc)
S6 - Delete
S7 - Move (to informational doc)
S8 - Move (to informational doc)
S9 - Delete (collapses into tracking and tracing I7)

10.  Supplemental Information
SD1 - Keep (rewrite, Tom Taylor to send extensibility requirement)
SD2 - SD9 Delete (merge into rewritten SD1, above)

11.  Security Considerations
SEC1 - Move (to security document/discussion)
SEC2 - Move (to security document/discussion)
SEC3 - Move (to security document/discussion)

[end of ecrit requirements I-D discussion for 5/18]

Per chairs' instruction, please post rewrites (where noted) onto the list for discussion by wg.

Regards,

Roger Marshall

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] On Behalf Of Tschofenig Hannes
Sent: Friday, May 06, 2005 1:39 PM
To: [email-masked]'
Subject: [Ecrit] WG: I-D ACTION:draft-schulzrinne-ecrit-requirements-00.txt

hi all, 

this document is an attempt to consolidate the requirements of the
individual documents into a single document. as indicated at the ecrit
working group meeting henning's document was used as the starting point. 
the draft authors of the other requirements documents have tried to
determine whether their requirements are already covered by henning's
document. roger incorporated them if they weren't. roger also clean up the
terminology and removed non-relevant parts. thanks for the good work, roger.

please review the document carefully. we will spend some time at the interim
meeting to discuss the open issues. 

ciao
hannes

-----Ursprüngliche Nachricht-----
Von: [email-masked] [mailto:[email-masked]] Im
Auftrag von [email-masked]
Gesendet: Freitag, 6. Mai 2005 21:44
An: [email-masked]
Betreff: I-D ACTION:draft-schulzrinne-ecrit-requirements-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories.

	Title		: Requirements for Emergency Context Resolution 
			  with Internet Technologies
	Author(s)	: H. Schulzrinne, R. Marshall
	Filename	: draft-schulzrinne-ecrit-requirements-00.txt
	Pages		: 38
	Date		: 2005-5-6
	
This document enumerates requirements for emergency calls placed by
   the public using voice-over-IP (VoIP) and general Internet multimedia
   systems, where Internet protocols are used end-to-end.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-schulzrinne-ecrit-requirements-00.
txt

To remove yourself from the I-D Announcement list, send a message to 
[email-masked] with the word unsubscribe in the body of the
message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-schulzrinne-ecrit-requirements-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-schulzrinne-ecrit-requirements-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

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

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