Subject: RE: [Ecrit] WG: Review (part 1) of I-D:draft-schulzrinne-ecrit-requirements-00.txt

From: "Stastny Richard" <[email-masked]>
Date: Wed, 18 May 2005 10:09:31 +0200

Short comment:

Regarding A reqs: I need to see the new text.

Regarding L reqs: a basic question about the new
Informational RFC: Some of the moved reqs are currently
musts and shalls: how can these be in an Informational
document?

regards

Richard Stastny
OeFEG
+43 664 420 4100
callto://fordprefect

> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]] On Behalf Of
> Roger Marshall
> Sent: Wednesday, May 18, 2005 4:17 AM
> To: [email-masked]
> Subject: RE: [Ecrit] WG: Review (part 1) of I-D:draft-schulzrinne-ecrit-
> requirements-00.txt
> 
> All:
> See listed below, a summary of the initial disposition of requirements,
> produced at today's interim ecrit meeting.  These results were based on a
> working group review of the 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
> 
> Note:
> Original requirement numbers (e.g. L1, L2, L3, etc.) which may get deleted
> or moved, will not be reused.  This means that there may be gaps in the
> numbered sequence, (which is OK), and that any 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)
> L22 - Delete
> L23 - Delete
> L24 - Move (to (Hannes) security I-D)
> 
> [end of discussion for 5/17 - will resume on 5/18]
> 
> Please discuss any corrections/changes to above in tomorrow's meeting.
> 
> 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