RE: [Ecrit] Rechartering Discussion

["James M. Polk" <[e-mail]>]

Patti

This ECRIT Architecture document is the IETF's take on how we developed the 
LoST protocol, Emergency Call Identification and the PhoneBCP - under what 
conditions, what we looked at, what we discounted and why, etc.  That is 
not the job of NENA or ESIF or ETSI or PacketCable.  Of course each of 
those SDOs can do their take on emergency calling too.  But for anyone just 
looking at the IETF, to figure out what this WG was thinking, this concept 
needs to be captured in an overarching document.

I prefer a doc title of "ECRIT Architecture" to what you have below.

At 08:34 AM 4/20/2006 -0500, McCalmont, Patti wrote:
>Then perhaps the charter task should be - ECRIT protocol Interaction and
>Consideration document. IMO, architecture means a lot more.
>
>Patti
>
>-----Original Message-----
>From: Tschofenig, Hannes [mailto:[e-mail]]
>Sent: Thursday, April 20, 2006 2:54 AM
>To: McCalmont, Patti; Hannes Tschofenig; [e-mail]
>Subject: AW: [Ecrit] Rechartering Discussion
>
>Hi Patti,
>
>the document that is going to be produced by the design team should
>provide information about the interation between the different
>protocols/extensions we are developing and reusing (e.g., Geopriv and
>SIP stuff).
>
>For example, draft-polk-newton-ecrit-arch-considerations-02.txt already
>describes the different steps that might need to be executed. We
>essentially describe these steps in more detail.
>
>Another example can be found in the protocol interactions we discussed
>at the ECRIT session at IETF#65 as part of Henning's presentation:
>(slide 3 - slide 5)
>http://www3.ietf.org/proceedings/06mar/slides/ecrit-3/sld1.htm
>
>A document with such a content is, in my view, an 'architecture'
>document. We could also call it 'framework' if this is a less overloaded
>term.
>
>Although the details of the document are for further study we are
>basically going to capture what we discussed during the last year (plus
>a number of new things that will come up with the ongoing work). There
>is currently no document that describes the big picture.  Several
>working group members repeately asked for such a document and hence we
>are going to work on it.  I think it is a very reasonable to capture
>these discussions and we have support from our AD todo it.
>
>Ciao
>Hannes
>
>PS: The design team might also want to take a look at the work done by
>the 3GPP and other organizations, for example.
>
> > Hi Hannes,
> >
> > On the item listed below, how do you think this will relate to work
> > going in other organizations such as 3GPP(already have a
> > draft started),
> > ESIF, PTSC and others? Is it really an architecture document since
> > IETF's focus is on defining protocols? Should this really be an item
> > addressed here? The other SDOs are looking at using protocols defined
> > within ECRIT but working out the architectures of how they fit into
> > their own networks.
> >
> > Guess I'm wondering if this item should really be part of
> > this charter.
> >
> > Patti
> >
> >
> > >TBD TBD           An Informational document describing the ECRIT
> > >Architecture
> >
> > >(Example documents are
> > draft-schulzrinne-sipping-emergency-arch-02.txt
> > >and draft-polk-newton-ecrit-arch-considerations-02.txt)
> >
> >
> >
> > Please note that the milestone date is missing for the last 3
> > items. I
> > would like to solicit input from the group: When can we finish these
> > documents?
> >
> > Ciao
> > Hannes
> >
> > _______________________________________________
> > Ecrit mailing list
> > [e-mail]
> > https://www1.ietf.org/mailman/listinfo/ecrit
> >
> > _______________________________________________
> > Ecrit mailing list
> > [e-mail]
> > https://www1.ietf.org/mailman/listinfo/ecrit
> >
>
>_______________________________________________
>Ecrit mailing list
>[e-mail]
>https://www1.ietf.org/mailman/listinfo/ecrit

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