AW: [Ecrit] Rechartering Discussion
"Tschofenig, Hannes" <hannes.tschofenig@siemens.com> Thu, 20 April 2006 08:03 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FWU8O-0002Xh-RM; Thu, 20 Apr 2006 04:03:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FWU67-0001bg-5Q for ecrit@ietf.org; Thu, 20 Apr 2006 04:01:07 -0400
Received: from gecko.sbs.de ([194.138.37.40]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWU0L-0006wD-R1 for ecrit@ietf.org; Thu, 20 Apr 2006 03:55:13 -0400
Received: from mail2.sbs.de (localhost [127.0.0.1]) by gecko.sbs.de (8.12.6/8.12.6) with ESMTP id k3K7t73N005240; Thu, 20 Apr 2006 09:55:07 +0200
Received: from fthw9xpa.ww002.siemens.net (fthw9xpa.ww002.siemens.net [157.163.133.222]) by mail2.sbs.de (8.12.6/8.12.6) with ESMTP id k3K7t3Sn030429; Thu, 20 Apr 2006 09:55:06 +0200
Received: from MCHP7IEA.ww002.siemens.net ([139.25.131.145]) by fthw9xpa.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.1830); Thu, 20 Apr 2006 09:55:05 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: AW: [Ecrit] Rechartering Discussion
Date: Thu, 20 Apr 2006 09:54:21 +0200
Message-ID: <A5D2BD54850CCA4AA3B93227205D8A30420035@MCHP7IEA.ww002.siemens.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Ecrit] Rechartering Discussion
Thread-Index: AcZjHoDHs0ywPyz2ToyZkOt5wehbuwAmhpYQAAImwPA=
From: "Tschofenig, Hannes" <hannes.tschofenig@siemens.com>
To: "McCalmont, Patti" <Patti.McCalmont@intrado.com>, Hannes Tschofenig <Hannes.Tschofenig@gmx.net>, ecrit@ietf.org
X-OriginalArrivalTime: 20 Apr 2006 07:55:05.0077 (UTC) FILETIME=[BC499250:01C6644F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc:
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ecrit.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
Errors-To: ecrit-bounces@ietf.org
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 > Ecrit@ietf.org > https://www1.ietf.org/mailman/listinfo/ecrit > > _______________________________________________ > Ecrit mailing list > Ecrit@ietf.org > https://www1.ietf.org/mailman/listinfo/ecrit > _______________________________________________ Ecrit mailing list Ecrit@ietf.org https://www1.ietf.org/mailman/listinfo/ecrit
- AW: [Ecrit] Rechartering Discussion Tschofenig, Hannes
- AW: [Ecrit] Rechartering Discussion Tschofenig, Hannes